Basis of Analysis
DCFR does not treat feasibility as a single score or an AI-generated opinion. Each site is evaluated through a structured chain of evidence, planning assumptions, calculated infrastructure demand, physical site-fit tests, development constraints, and confirmation requirements. The result is a traceable early-stage decision showing not only what DCFR concludes, but what that conclusion is based on.
Architect-led planning logic
Built by Jeehee Hong, a New York State Registered Architect with 20+ years of experience across architecture, infrastructure, logistics, master planning, and mission-critical development in the US, Asia, and EMEA. DCFR structures that experience into repeatable planning questions, explicit assumptions, and clear next actions.
New York State Registered Architect
AIA Member · NCARB Record Holder · Data Center Certified Associate · LEED Green Associate
Jeehee’s background includes 100+ completed projects across high-rise mixed-use, residential portfolios, institutional and healthcare facilities, adaptive reuse, hospitality, commercial office, global retail, and large-scale integrated infrastructure — including AI-enabled smart logistics city developments totaling 16M SF / approximately $6B.
Across her career, she has contributed to more than $10B in accumulated project portfolio value, working across multidisciplinary teams, program governance, feasibility strategy, cost and schedule constraints, and technical coordination.
Expertise shapes the framework. Standard reports are software-generated. No individual architect or engineer review, seal, or approval is included.
See the methodologyDecision chain
Every material conclusion remains traceable to its evidence, assumption, calculation, or confirmation requirement.
Six analysis layers
01
Target IT capacity, rack-density basis, redundancy, cooling strategy, phasing intent, parcel information, schedule objectives, and available project documents establish the program DCFR is testing.
02
Available parcel, access, surrounding-use, utility, environmental, entitlement, hazard, and infrastructure information is assembled into an evidence register. Material items are identified by source and evidence status.
03
DCFR converts the intended program into planning quantities: estimated racks, data-hall modules, building footprint, electrical and generator infrastructure, cooling demand, parking, loading, circulation, stormwater allowance, buffers, and expansion reserve.
04
Calculated development demand is tested against the parcel's buildable envelope, access, geometry, infrastructure interfaces, sensitive edges, circulation requirements, development constraints, and future expansion needs.
05
Every material conclusion is classified by what supports it. Unknowns are not silently converted into facts. Utility deliverability, final code interpretation, environmental conditions, civil design, geotechnical conditions, acoustics, and authority approvals remain explicit confirmation items where required.
06
DCFR converts the combined evidence and constraint tests into an Advance / Backup / Watch / Reject decision, identifies conditions that could change that decision, and defines the next diligence actions before additional capital is committed.
Evidence status
A nearby transmission line is not the same as utility-confirmed capacity. A calculated building footprint is not a stamped design. DCFR preserves those distinctions instead of collapsing them into one confidence-free score.
VERIFIED
Supported by authoritative or project-specific evidence.
OBSERVED
Supported by available public or client-supplied information.
CALCULATED
Generated from explicit DCFR planning assumptions and calculation logic.
ASSUMED
A planning assumption used because project-specific information is unavailable.
UNCONFIRMED
Material information that still requires external professional, utility, or authority confirmation.
Example: power
Power infrastructure — OBSERVED: nearby transmission or substation infrastructure identified from available information.
Deliverable MW — UNCONFIRMED: utility engagement, study, schedule, and commercial confirmation required.
Example: physical fit
Building footprint — CALCULATED: derived from target IT load, rack-density basis, data-hall modules, support-space assumptions, and selected geometry.
Parcel fit — CALCULATED: tested against the planning envelope and identified site constraints; final civil and professional confirmation remains separate.
Planning-grade by design. Transparent about certainty.
DCFR is designed to determine whether a site merits deeper diligence, not to replace utility studies, surveys, engineering, environmental investigation, legal opinions, or authority approvals. Where project-specific confirmation is unavailable, DCFR identifies the uncertainty rather than presenting it as fact.
