Loading the campus, scanned materials and rigged people.
Follow the story at your pace
01 / 12
Stage 1 · Greenfield
01
An open field. A connected future.
Before there is a building, there is a business need. Maya works with the chief information officer and application owners to plan a twelve-megawatt enterprise data center. One company will own the campus and use it for its own applications, data and private cloud. The first decision is whether the workload forecast and resilience needs justify investigating a dedicated facility.
MayaDevelopment lead
“Our first job is to prove a need, before we fall in love with a site.”
An internal workload forecast, security and resilience requirements, alternatives analysis and a bounded investigation budget.
Make the call · one quick decision
Meet your project team
Every stage has people behind it.
Select a person to explore their role.
Maya · Development lead. Brings internal workload demand, land, corporate capital and community commitments into one workable project.
Beyond the project team · Norfolk, Nebraska
There’s a person behind every review.
Meet the people who help protect neighbors, public infrastructure and the people who will use this building.
Norfolk city limits Madison County · Nebraska
An authority having jurisdiction (AHJ) reviews a defined part of the project. Juniper Ridge is a fictional site inside Norfolk city limits. These named reviewers and conversations are fictional teaching roles, not actual government staff or quotations. Their agency responsibilities follow the official sources linked below.
Local · land useFictional reviewer · real agency
Meet Nina, your city planner.
City of Norfolk · Planning and Development
“Help me understand how this campus will fit beside its neighbors, not just inside its property lines.”
Bring to the conversation
A concept site plan, proposed use, access, buffers and neighboring uses. Ask staff to confirm the parcel’s zoning and how a data center would be classified.
What this review does
Site-plan and zoning review. At 120,000 SF, this example exceeds Norfolk’s additional site-plan review thresholds for both industrial and office/commercial development.
Across the table: Maya explains the project; Morgan and Eli turn concerns into a coordinated layout.
When it applies: Confirm the land-use path first. A conditional-use permit, rezoning or plat is not automatic. If a CUP is needed, the Planning Commission considers it after a hearing; City Council handles an appeal.
Try the conversation
The team likes the parcel, but no one has confirmed that its zoning allows this proposed use.
The parcel and equipment determine these additional paths. A Norfolk pre-application conversation should confirm which ones apply.
Nebraska Department of Transportation
If access touches a state highway: Eli coordinates the applicable driveway, approach-road or right-of-way permission with NDOT. A city approval does not authorize work in state highway right-of-way.
If work affects regulated waters or wetlands: Confirm jurisdiction and any Section 404 or Section 10 permit path before the relevant work. The fictional field is not assumed to have—or be free of—regulated waters.
If crane or structure location and height trigger airspace notice: Screen the proposal for FAA notice and aeronautical review. Include temporary cranes; an FAA determination is separate from a building permit.
If the parcel lies in a regulated floodplain: Confirm the applicable floodplain development review with the city before deciding site levels or disturbing the land. No floodplain location is assumed here.
If an on-site groundwater well is proposed: Confirm well-permit and groundwater-management requirements with the district before construction. Municipal water service does not imply that a separate campus well is approved.
One decision does not replace another: land-use approval, a building permit, utility service and permission to occupy are separate milestones. Exact zoning classification, permits and sequencing require a real parcel and coordinated design. Sources checked October 13, 2026.
Juniper Ridge · enterprise decision lab
Capacity serves the business. Ownership has a lifecycle cost.
Juniper Ridge is owned and operated by one enterprise for its applications, data and private cloud. The capital committee evaluates business need, resilience and total cost of ownership. All figures below are fictional teaching assumptions.
Allocation reserves capacity for application teams. Actual measured load, installed IT capacity and planned allocation are different measures. Unallocated capacity is not a certified resilience reserve.
Ten operating years, constant annual IT load and PUE, initial capital at time zero and year-end operating payments. Operating costs escalate at 3.0% annually; the year-six refresh is an explicit nominal amount. Present cost discounts cash outflows at 8.0%. The baseline $140M facility budget comprises $4M land, $8M site works, $102M construction and systems, $10M soft costs and $16M contingency. Initial IT is $48M; facilities operations $4.2M/year and IT operations $2.4M/year exclude the separately calculated electricity.
Excludes financing structure, tax, depreciation, residual value, decommissioning, software licensing, network carrier charges, migration cost and business benefits. Scope these for an actual capital decision. Allocation alone does not reduce the fixed capital or operating budget.
The sequence illustrates a development story; real approvals, design, procurement and migration planning overlap. The orbitable campus uses physically based materials and licensed rigged human models. Equipment quantities and visible routes are schematic and do not imply a reliability tier, certified redundancy or engineering design. Costs, dates, workloads and capacity are fictional assumptions.
1. An open field. A connected future.
Before there is a building, there is a business need. Maya works with the chief information officer and application owners to plan a twelve-megawatt enterprise data center. One company will own the campus and use it for its own applications, data and private cloud. The first decision is whether the workload forecast and resilience needs justify investigating a dedicated facility.
Decision: Does the enterprise need its own capacity here?
2. The site must connect.
Eli checks access, neighboring uses, fiber routes and possible electrical service. A nearby power line does not prove that usable capacity will be delivered when needed. Noor works with the utility on capacity, connection scope and timing while the team compares site alternatives and community impacts.
Decision: Can power, connectivity and access support this use?
3. Look beneath the surface.
Surveyors mark boundaries while investigators examine soils, water, environmental conditions and title. The sponsor seeks site control with investigation rights and clear deadlines. A difficult finding can change the design, the price or the decision to proceed. The land remains unbuilt while this evidence is assembled.
Decision: Can the team accept or resolve the site constraints?
4. Design the system, not just the shell.
A concept rises from the field. Morgan, the project architect, brings the data halls, staff spaces, safe circulation and building envelope into one coordinated design. Eli shapes the site and drainage. Noor plans power and cooling around the enterprise workloads. Together, they make room for maintenance, security and future change, test resilience against business needs, and prepare drawings that reviewers and builders can understand.
Decision: Does the coordinated concept satisfy the brief and budget?
5. Earn permission to build.
In Norfolk, Nebraska, Maya and Morgan meet city planners, building reviewers, the fire marshal and the public works team. Eli coordinates drainage and utility connections. State environmental reviewers assess stormwater coverage and any permits triggered by the equipment. Each reviewer protects a different public interest. The team records decisions and conditions, because land-use support, a building permit and permission to occupy are separate milestones.
Decision: Are the applicable approvals and start-work conditions satisfied?
6. Commit capital. Secure the long leads.
The capital committee reviews the business case: one hundred forty million dollars for the facility, plus forty-eight million for enterprise IT equipment in this teaching example. Sam aligns the approved funding, construction sequence and long-lead orders. The enterprise also funds operations, equipment refresh and the migration plan. A finished shell alone cannot deliver the business service.
Decision: Has the enterprise approved a funded, deliverable business case?
7. From greenfield to building platform.
The authorized site work begins. Excavators grade the platform, crews install below-ground services, and the team controls runoff and protects the retained buffer. Foundations start to trace the future data halls. Early work is inspected before later construction covers it.
Decision: Are the groundworks verified for the next work package?
8. The building rises.
A crane swings over the new frame. Columns, roof steel and envelope panels turn the platform into a building. Sam coordinates safe lifting and weather-tightness with the teams preparing equipment installation. Physical progress, approved changes and the forecast to complete are reviewed together.
Decision: Can the shell safely receive the next systems?
9. Give the building its working systems.
Open the roof to see the data halls. Crews install distribution, backup power, cooling, controls and cabinets for the enterprise IT team. Inside, the company prepares its network, storage and compute platforms. Facilities and IT share the same acceptance plan. Visible equipment and routes illustrate the system; they are not an engineered redundancy design.
Decision: Are the installed systems complete and ready to test?
10. Make the systems prove themselves.
Alex leads the commissioning team through equipment tests and integrated systems testing. Facilities operators rehearse alarms, transitions and recovery procedures before enterprise workloads depend on the building. Unresolved failures remain on the issues register. Regulatory permissions, facilities acceptance and IT service readiness are separate gates that must align.
Decision: Are the facility and operating team ready for controlled IT deployment?
11. Bring the enterprise workloads online.
Jo coordinates the move with enterprise IT. The company installs its servers, storage and network equipment, then migrates applications in controlled waves. Each wave has verified backups, acceptance checks and a rollback plan. Nine megawatts are allocated to internal teams in this example, but the average actual IT load is six megawatts. A capacity allocation is not a meter reading.
Decision: Can the next workload wave move safely into service?
12. An occupied building. An ongoing responsibility.
The enterprise campus is working. Facilities technicians maintain the infrastructure while IT teams operate the applications. Jo reviews service availability, security, actual load, energy and total operating cost. Capacity planning, equipment refresh and recovery exercises continue throughout the building’s life. Success means dependable service for the business, supported by evidence and a funded operating plan.
Decision: Is the campus delivering the enterprise’s service and cost commitments?
