Zorile: Adaptive Mixed-Use Development with Data Center Integration
Continuation of the DAUF/LICA Analysis
1. Introduction: From Static Planning to Adaptive Urban Logic
In the previous part of the analysis, we established a key premise: the traditional генеральный план (master plan) is no longer capable of managing the complexity of contemporary urban development. Instead, the city must be understood as a dynamic system, where each intervention is evaluated not as a fixed prescription, but as a scenario within a continuously evolving framework.
The Zorile site provides an ideal test case for this approach. Located within a sensitive urban fabric, influenced by historical morphology, transport constraints, and infrastructural limitations, it requires a solution that is not only formally acceptable but systemically efficient.
This article continues the analysis by examining a specific scenario: a mixed-use development combining residential, office, and a data center function.
2. The Existing Building as a Symbolic Anchor
One of the most critical aspects of the site is the presence of the existing three-story perimeter building — the former footwear factory.
Although it is not officially listed as a heritage monument, its urban significance cannot be reduced to formal status.
2.1. Architectural Uniqueness
The building possesses a rare and highly recognizable feature: a rounded corner geometry that is unique within the city of Chișinău. This element is not merely decorative — it defines spatial perception at the intersection and creates a memorable urban identity.
In a city where much of the historical silhouette has been lost or transformed, such elements become disproportionately valuable.
2.2. Urban Memory and Continuity
The structure functions as a carrier of urban memory. Its scale, rhythm, and materiality establish a dialogue with the surrounding context, particularly with mid-20th century development layers.
Demolition of such a structure would not simply remove a building — it would erase a fragment of the city’s spatial narrative.
2.3. Strategic Role in the Scenario
In the proposed solution, the building is preserved and repurposed:
Ground floor: active functions (retail, services)
Upper floors: mixed residential and office use
This approach allows the project to:
Maintain continuity with the existing urban fabric
Reduce embodied carbon compared to full demolition
Provide immediate functional activation without requiring full new construction
3. Spatial Strategy: Division of the Plot
The core spatial decision is the division of the plot into two approximately equal parts:
Perimeter block (existing + adaptive reuse)
Inner courtyard (new construction – data center)
This division is not arbitrary — it reflects a deeper urban logic.
3.1. Perimeter as Public Interface
The perimeter block addresses the city:
It defines the street edge
It ensures active ground floors
It maintains human-scale interaction
3.2. Courtyard as Technological Core
The inner zone hosts the data center — a function that:
Does not require active street frontage
Benefits from controlled access
Can operate independently of daily urban rhythms
This separation allows coexistence of fundamentally different urban functions without conflict.
4. Morphology and Height Compliance
One of the key evaluation criteria is compliance with the historical morphology and height regulations.
4.1. Allowed Heights
The analysis defines the following thresholds:
Front: ~16 m
Corner: ~20 m
Inner zones: up to ~31–34 m depending on setback
4.2. Projected Heights (FAR = 3.5)
The proposed scenario produces:
Front: 16 m (fully compliant)
Corner: 16 m (below allowed)
Inner 36 m setback: ~30 m
Inner 54 m setback: ~36 m
This indicates that:
The project respects the street scale
Height increases are absorbed within the inner block
Visual impact on the historical environment is minimized
4.3. Interpretation
Unlike typical speculative development, where height is pushed to the perimeter, this scenario reverses the logic:
Maximum volume is placed where it has minimal urban impact.
This is a key principle of adaptive morphology.
5. Functional Structure and FAR Logic
The selected FAR of approximately 3.5 represents a balanced scenario.
5.1. Distribution of Functions
Residential: perimeter upper levels
Office: part of perimeter + flexible spaces
Data center: inner block
5.2. Why FAR 3.5 Works
It allows sufficient density for economic viability
It remains within morphological limits
It avoids exponential growth of transport demand
Increasing FAR further (e.g., to 5) would:
Add volume primarily to the data center
Not proportionally increase transport load
But would increase engineering loads and risk imbalance
Thus, FAR 3.5 represents an optimal equilibrium point.
6. Energy Infrastructure: A Critical Advantage
One of the most important findings of the analysis concerns power availability.
6.1. Current Capacity
Available: ~50,000 units
Project demand: ~14,372 units
Remaining capacity: ~35,628 units
6.2. Interpretation
This scenario uses only a fraction of the available capacity.
This is highly unusual for central urban areas, where power constraints often become the limiting factor.
6.3. Strategic Implication
The data center function:
Converts excess electrical capacity into economic value
Does not require proportional increases in water or transport infrastructure
This makes it one of the most efficient ways to utilize existing networks.
6A. Numerical Model for Data Center Power: W/m² → MW → Tier Class
To make the scenario analytically complete, it is important to add a clear numerical model that translates building area into electrical demand and then connects that demand to possible data center formats and Tier ambitions.
6A.1. Basic Conversion Formula
At the earliest planning stage, power for a data center can be estimated through a simple intensity model:
IT load (kW) = IT area (m²) × specific IT power density (W/m²) / 1000
Then the total facility power can be estimated through PUE:
Total facility power (kW) = IT load (kW) × PUE
Where:
IT area = net white-space / server-room area actually occupied by racks and supporting IT rooms
specific IT power density = planned IT load per square meter
PUE = Power Usage Effectiveness, the ratio between total facility energy and IT energy
At the concept stage, this is the simplest and most transparent model.
6A.2. Practical Density Ranges
For urban planning and pre-feasibility studies, a convenient working scale is:
300–600 W/m² — light colocation / edge / telecom-oriented format
600–1200 W/m² — medium-density commercial data center
1200–2000 W/m² — high-density cloud / AI-ready halls
2000+ W/m² — very high density specialized halls
This does not mean that the whole building consumes this load uniformly. It refers mainly to the active IT area. The gross built area will usually have a lower average intensity because it also includes circulation, technical rooms, structural zones, security spaces, loading areas, and engineering infrastructure.
6A.3. From Area to MW: Example Logic
A practical reference table for concept design can be written as follows.
Example A — edge / low-density format
IT area: 4,000 m²
Density: 500 W/m²
IT load:
4,000 × 500 / 1000 = 2,000 kW = 2.0 MW
If PUE = 1.45:
2.0 × 1.45 = 2.9 MW total facility load
Example B — medium-density format
IT area: 4,000 m²
Density: 1,000 W/m²
IT load:
4,000 × 1,000 / 1000 = 4,000 kW = 4.0 MW
If PUE = 1.40:
4.0 × 1.40 = 5.6 MW total facility load
Example C — high-density format
IT area: 4,000 m²
Density: 1,500 W/m²
IT load:
4,000 × 1,500 / 1000 = 6,000 kW = 6.0 MW
If PUE = 1.35:
6.0 × 1.35 = 8.1 MW total facility load
This shows an important principle: the same building envelope may represent very different electrical realities depending on the operational model.
6A.4. Gross Area vs IT Area
For this project it is especially important not to confuse total GFA with actual IT area.
A data center usually includes:
server halls
UPS and battery rooms
cooling plant areas
switchgear rooms
loading and service spaces
security and monitoring rooms
circulation and fire separation zones
Therefore, only part of the total built area becomes active IT white-space.
At concept level, a rough ratio can be used:
35–50% of GFA as IT area for compact urban schemes
50–60% only in more optimized technical layouts
This means that a building with 8,000 m² GFA may contain only 3,000–4,500 m² of true IT area.
6A.5. Fast Planning Formula for Urban Scenarios
For quick scenario comparison, the following shortcut is useful:
Total DC power (MW) ≈ GFA × IT share × IT density × PUE / 1,000,000
Where:
GFA in m²
IT share as a decimal (for example 0.40)
IT density in W/m²
PUE typically 1.3–1.5 for modern facilities
Example
Suppose:
GFA = 10,000 m²
IT share = 0.40
IT density = 1,000 W/m²
PUE = 1.40
Then:
10,000 × 0.40 × 1,000 × 1.40 / 1,000,000 = 5.6 MW
This formula is very convenient because it links urban form directly to engineering demand.
6A.6. Interpreting the Zorile Capacity Figure
In the current analytical scheme, the power chart shows:
available power: 50,000
projected demand: 14,371.96
remaining gap: 35,628.04
If these values are interpreted as kW of available connected capacity, then the project demand corresponds to roughly:
14,371.96 kW ≈ 14.37 MW
That is a very substantial electrical envelope for an inner-city project.
Under that interpretation, the remaining reserve of about 35.63 MW means that the location has unusually strong power potential compared with most central urban sites.
This is exactly why the data center scenario becomes strategically important here: it is one of the few functions capable of converting such electrical capacity into high economic productivity without proportionally increasing population or social infrastructure demand.
6A.7. What 14.37 MW Means in Spatial Terms
To understand the scale, we can reverse the calculation.
Scenario 1 — medium density
Assume:
IT density = 1,000 W/m²
PUE = 1.40
Then IT load would be:
14.37 / 1.40 = 10.26 MW IT
Required IT area:
10.26 MW / 1.0 kW/m² = 10,260 m² IT area
That is a very large operational footprint and would normally imply either:
a larger multi-level technical building,
very efficient floor stacking,
or phased implementation.
Scenario 2 — high density
Assume:
IT density = 1,500 W/m²
PUE = 1.35
IT load:
14.37 / 1.35 = 10.64 MW IT
Required IT area:
10.64 MW / 1.5 kW/m² ≈ 7,093 m² IT area
This is more realistic for a compact urban data center.
Scenario 3 — edge / lighter format
Assume:
IT density = 600 W/m²
PUE = 1.45
IT load:
14.37 / 1.45 = 9.91 MW IT
Required IT area:
9.91 MW / 0.6 kW/m² ≈ 16,517 m² IT area
This would likely be too area-intensive for the given urban parcel unless developed in several stages or with a reduced actual load.
6A.8. Planning Conclusion on Power
From these reverse calculations, an important conclusion emerges:
If the site really has access to a power envelope on the order of 14 MW+ for the project itself, then the most realistic and economically strong data center model is not a low-density telecom room, but a medium- to high-density urban facility.
This aligns well with current trends:
edge-cloud infrastructure near demand centers
sovereign/localized hosting requirements
AI and accelerated computing demand
hybrid city-based digital infrastructure nodes
In other words, the available electricity is not simply sufficient — it suggests a future-oriented specialization.
6A.9. Tier Class: What It Changes and What It Does Not
It is also necessary to clarify an important methodological point: Tier is not a measure of electrical demand.
Tier describes reliability and redundancy topology, not sheer megawatt size.
A 3 MW facility may be Tier III, and a 15 MW facility may be Tier II. These are different questions.
The classic four-tier logic is:
Tier I — basic capacity
Tier II — redundant components
Tier III — concurrently maintainable
Tier IV — fault tolerant
In practical urban terms:
Tier I is too weak for this type of strategic investment
Tier II may fit small telecom or budget colocation formats
Tier III is the most balanced target for a serious commercial urban data center
Tier IV is possible but usually much more expensive and spatially demanding
6A.10. Why Tier III Is the Most Rational Benchmark Here
For the Zorile scenario, Tier III is the most logical reference point because it offers:
high market credibility
maintainability without shutdowns
better fit for enterprise and cloud tenants
strong balance between resilience and cost
Tier IV would require additional fault-tolerant topology, more duplicated systems, more space reservation, and significantly higher capex. For a compact city-center site, this often reduces efficiency unless there is a very specific business case.
6A.11. Simple Rule-of-Thumb Matrix
A practical conceptual matrix for the site may be summarized this way:
2–4 MW total facility power — edge / telecom / local cloud node, likely Tier II or Tier III
4–8 MW — strong urban colocation / enterprise / regional node, best aligned with Tier III
8–15 MW — major urban digital infrastructure asset, likely requiring phased implementation, stronger cooling strategy, and very careful grid and backup design
15 MW+ — large strategic platform, feasible only if electrical, acoustic, fire-safety, and logistics constraints are fully integrated from the start
Under this logic, the Zorile scenario sits not at the lower edge of viability, but in a range that can support a genuinely strategic digital function.
6A.12. Strategic Meaning for the Investor
Adding this power model strengthens the investment argument.
The value of the site lies not only in the possibility to build floor area, but in the rare combination of:
compliant morphology
preserved symbolic perimeter building
minimal additional social burden
relatively low incremental transport impact
and, crucially, a large usable electrical reserve
That combination is uncommon.
For a conventional residential or office project, much of this electrical potential would remain underused. For a data center-led hybrid scheme, the site can monetize exactly the resource that is hardest to create from scratch in a dense city: reliable power access.
7. Transport Impact: The Limiting Constraint
Transport remains the most sensitive parameter.
.png){kind=spacer}
7.1. Current Situation
Limit: ~3200 units
Existing load: ~-11518 (already overloaded)
Project addition: ~-1067
7.2. Interpretation
The area is already significantly overloaded.
Any development must therefore be evaluated not by absolute neutrality, but by relative impact.
7.3. Comparative Advantage of the Scenario
The proposed mixed-use + data center model:
Generates significantly less traffic than purely residential or office scenarios
Concentrates activity in functions with low mobility demand
Among all tested scenarios, this one produces the minimal additional burden.
7.4. Key Insight
The goal is not to eliminate impact (which is impossible), but to minimize marginal degradation.
This scenario achieves exactly that.
8. Social Infrastructure: Neutral Impact
Unlike residential-heavy scenarios, this model:
Does not significantly increase population
Does not create additional demand for schools or kindergartens
This eliminates one of the most common sources of urban imbalance.
9. Economic Model and Investor Logic
Although the scenario may appear more complex and slightly more expensive at the initial stage, it offers strong long-term advantages.
9.1. Diversified Revenue Streams
Residential income n- Office leasing
Data center operations (high-value, stable)
9.2. Risk Distribution
The combination of functions reduces dependency on a single market sector.
9.3. Future-Proofing
Data centers represent a rapidly growing sector, driven by:
Cloud infrastructure
AI workloads
Digitalization of services
This ensures long-term relevance of the project.
10. Urban Strategy: A New Typology
This scenario introduces a new urban typology for Chișinău:
Hybrid block with hidden technological core
Key characteristics:
Historical perimeter preserved
Active street interface maintained
High-intensity function internalized
This model can be replicated in other similar sites.
11. Conclusion: Why This Scenario Works
The proposed solution satisfies all key criteria:
Morphology
Fully compliant with height and form
Preserves urban identity
Infrastructure
No overload of engineering networks
Efficient use of electrical capacity
Transport
Minimal additional impact compared to alternatives
Social
No additional burden on public services
Economy
High long-term profitability
Alignment with global trends
Final Statement
In the logic of adaptive urban planning (DAUF/LICA), this scenario is not simply acceptable — it is optimal.
It demonstrates that the future of the city does not lie in maximizing volume, but in maximizing compatibility between functions, infrastructure, and urban form.
The Zorile project, in this configuration, becomes not just a development proposal, but a prototype for a new generation of urban interventions.
