Community-Positive Data Center Development
Design resilient data centers with low-water cooling, microgrids, grid services, and measurable community benefits. Learn a feasibility-to-commissioning methodology rather than relying on sustainability slogans.
Your course plan
Study format
8-12 minutes per lesson, with a 60-90 minute capstone. Estimates include practice and assessment. Estimated total: 4-5 hours including the capstone and quiz.
Prerequisites and scope
AI Data Center Development or equivalent infrastructure literacy; basic kW, kWh, and spreadsheet skills. This is development methodology, not a license to perform electrical or mechanical engineering.
Learning outcomes
- Load and thermal feasibility
- Closed-loop cooling evaluation
- Microgrid resilience modeling
- Utility export and benefit design
- Community accountability
Four modules, three lessons each
- Define demand and local impact
- Close the thermal loop
- Balance the microgrid and utility interface
- Deliver and verify community benefit
Completion and assessment
Complete all 12 lessons and the practice activities. Use the final-lesson rubric to review the capstone with an instructor or peer. The portal scores a separate 10-question final quiz; 80% or higher is required for the existing course-completion credential. Capstone work is not automatically graded by the portal. No academic credit or external license is implied.
Authoritative reference shelf
Technical and regulatory references reviewed October 8, 2026. Original teaching scenarios, assumptions, calculations, exercises, and rubrics are instructional examples. Verify current source requirements for an actual project or operation.
M1.1 | Start with the workload and the community
Learning objective
Translate digital-service demand and resident concerns into a measurable design basis.
Core lesson
A data center houses computing, storage, networking, power, and cooling systems that deliver digital services. AI training and inference can have different utilization and response-time requirements. Start with the service the facility must provide, not a desired building size. Create a design basis: initial and ultimate IT load, rack density, growth stages, uptime target, outage tolerance, and which workloads can move or pause. Separately record community conditions: existing utility constraints, residential energy burden, water availability, land use, and noise-sensitive neighbors. Treat these as design inputs with owners. A smaller first phase with reserved expansion can reduce the risk of building capacity before customer demand and power delivery are ready.
Instructor teaching guidance
Begin by establishing what the learner already knows about m1.1 | start with the workload and the community. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Worked example: a developer requests a 20 MW campus but has customers for only 2 MW. Define a 2 MW first phase and require evidence before expansion. Practice: write a one-page design basis for a 1 MW IT facility. Name three community concerns, their measurement methods, and the person responsible for resolving each.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
Success names the workload, capacity boundary, service requirement, affected residents, and evidence required before expansion.
Knowledge check
What evidence would justify expanding from the first phase, and what community constraint could stop it?
M1.2 | Build the energy and water baseline
Learning objective
Calculate a transparent baseline and identify what each environmental metric can and cannot show.
Core lesson
Power in kW describes an instantaneous rate; energy in kWh describes power accumulated over time. Annual energy for a constant load is power multiplied by hours. Power usage effectiveness, PUE, compares total facility energy with IT energy over the same period. It does not measure how useful the computing work is. For this original teaching case, 1 MW of constant IT load and a PUE of 1.20 imply 1.2 MW total average demand and 10,512 MWh per year. A proposed efficiency improvement must preserve service quality. Record actual meter boundaries, auxiliary loads, seasonal conditions, and uncertainty. Track on-site cooling water separately from indirect water associated with electricity supply. A single attractive metric can conceal a different environmental burden.
Instructor teaching guidance
Begin by establishing what the learner already knows about m1.2 | build the energy and water baseline. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Practice: calculate annual energy at PUE 1.35 and 1.20 for the same 1 MW IT load, then calculate the difference. Draft a meter schedule for IT, cooling, storage charging, exports, and site water. Explain why PUE alone cannot demonstrate low carbon emissions or lower neighborhood bills.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
The energy difference is 1,314 MWh per year under the stated constant-load assumptions; boundaries and assumptions remain explicit.
Knowledge check
If a facility reports lower PUE but doubles its IT load, what happens to its total energy demand?
M1.3 | Site selection and development gates
Learning objective
Choose and stage a project using documented site evidence and explicit decision gates.
Core lesson
Use a screened shortlist rather than choosing land solely by price. Score utility capacity and delivery dates, fiber routes, flood and climate exposure, geotechnical conditions, cooling climate, transport, workforce, emergency access, and proximity to heat users. Record disqualifying conditions separately from weighted preferences so a high total score cannot hide a fatal constraint. Use decision gates: demand confirmation, site feasibility, utility feasibility, concept selection, detailed engineering, investment approval, construction, and commissioning. Each gate needs evidence, an accountable decision-maker, unresolved risks, and a stop condition. Obtain local planning and utility input early. The methodology organizes professional studies; it does not substitute for permits, protection studies, or stamped engineering.
Instructor teaching guidance
Begin by establishing what the learner already knows about m1.3 | site selection and development gates. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Worked example: Site A has cheap land but no firm connection date; Site B has higher land cost and a credible phased utility offer. Practice: build a five-criterion scorecard with weights totaling 100, two disqualifiers, and an evidence checklist for the utility-feasibility gate.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
A defensible site recommendation identifies evidence quality, critical dependencies, and a condition that would reverse the decision.
Knowledge check
Why should an unresolvable flood or utility constraint remain outside a weighted score?
M2.1 | Trace the complete cooling loop
Learning objective
Evaluate a closed-loop claim by tracing all heat and water boundaries.
Core lesson
Trace heat from the chips to the ultimate environment. A direct-to-chip system can carry heat through a technology loop, a coolant distribution unit, a facility loop, and a final heat-rejection device. A recirculating chip loop does not prove the entire site is water-free: its downstream equipment may still evaporate water. Create a thermal boundary diagram and list initial fill, make-up, maintenance drainage, leakage, evaporation, and any emergency mode. Dry heat rejection can avoid evaporative cooling water, but fans, pumps, refrigerants, climate limits, and required backup still matter. Replace an absolute claim such as no water with a measurable statement tied to system boundaries and operating modes. Select coolant only from validated equipment and materials requirements; a water/glycol formulation is not automatically interchangeable with a dielectric immersion fluid.
Instructor teaching guidance
Begin by establishing what the learner already knows about m2.1 | trace the complete cooling loop. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Practice: sketch two paths from chips to ambient air, one ending in a dry cooler and one in an evaporative tower. Label every water input and discharge. Rewrite a vendor claim of closed loop, no water into a testable design requirement and request its supporting diagram.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
Success distinguishes recirculation from final heat rejection and identifies fill, losses, maintenance, and emergency water use.
Knowledge check
What additional evidence is needed when a vendor shows only the server-side loop?
M2.2 | Select cooling by conditions, not fashion
Learning objective
Compare cooling architectures using operational and lifecycle evidence.
Core lesson
Compare air containment, rear-door heat exchangers, cold plates, and immersion against the actual rack density, supported hardware, service procedures, climate, and cost. Direct liquid cooling moves heat close to its source; it does not remove the need to manage remaining air-cooled components. Immersion introduces different fluid compatibility, handling, and maintenance requirements. Use a technology decision sheet with design temperatures, pressure and flow ranges, heat-rejection capacity on the hottest design day, redundancy, leak detection, corrosion controls, service access, warranty support, and fluid lifecycle. Evaluate partial-load operation as well as peak performance. Pilot an unfamiliar approach on representative hardware before scaling. This course does not claim that a particular glycerol, glycol, refrigerant, or dielectric formulation is universally safe or optimal.
Instructor teaching guidance
Begin by establishing what the learner already knows about m2.2 | select cooling by conditions, not fashion. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Worked example: a mixed campus includes ordinary network racks and high-density accelerator racks. Practice: recommend two cooling zones and write five vendor acceptance questions. Include a loss-of-pump scenario and the information a qualified mechanical engineer must verify.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
The recommendation ties technology to heat density, supported hardware, operating conditions, maintenance, and failure response.
Knowledge check
Why can a technology that performs well on one rack fail when copied across a mixed campus?
M2.3 | Reuse heat and reduce environmental burden
Learning objective
Assess heat reuse and local environmental impacts across the operating lifecycle.
Core lesson
Heat reuse needs a recipient who wants heat at the available temperature, quantity, season, and location. Potential recipients include nearby buildings, district systems, greenhouses, or industrial processes. Assess distance, piping, metering, heat-pump electricity, maintenance ownership, and what happens if the recipient shuts down. Reuse does not eliminate the need for a backup heat-rejection path. Consider thermal storage and geothermal options as site-specific candidates, not guaranteed solutions. Evaluate noise at nearby receptors, stormwater, habitat, construction traffic, backup-generator emissions, embodied impacts, and equipment end of life. Use a comparative impact register with baseline, expected change, mitigation, uncertainty, and monitoring. An original project should state both the benefit and the remaining burden.
Instructor teaching guidance
Begin by establishing what the learner already knows about m2.3 | reuse heat and reduce environmental burden. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Practice: compare heat reuse for an adjacent greenhouse with a school two miles away. Name the measurements needed before selecting either. Create three mitigation commitments, each with an owner, a numerical target to be established through study, and a measurement schedule.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
A viable reuse concept has a credible recipient, a temperature and seasonal match, costed delivery, and backup rejection.
Knowledge check
What breaks the business case if a recipient needs heat only during a short winter season?
M3.1 | Size the microgrid with a time-series model
Learning objective
Estimate storage and test microgrid self-reliance using explicit time-based assumptions.
Core lesson
A microgrid coordinates local loads and energy resources within a defined electrical boundary; islanding requires the equipment and controls to operate safely when disconnected. Separate renewables, dispatchable supply, storage, control, protection, and critical loads. Batteries store energy; they do not create it. Use hourly or finer time steps to model demand, generation, storage state of charge, losses, imports, exports, and reserves. In this teaching case, a 1.2 MW critical load needs 14.4 MWh of delivered energy for 12 hours with no generation. At 80% usable capacity and 90% discharge-path efficiency, nameplate capacity is about 20 MWh before aging and additional reserves. Also verify discharge power in MW. Annual renewable matching does not establish continuous self-reliance through a multi-day low-generation period.
Instructor teaching guidance
Begin by establishing what the learner already knows about m3.1 | size the microgrid with a time-series model. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Practice: build a 24-hour spreadsheet with load, solar, battery, and grid columns. Include a cloudy outage and a minimum reserve. Calculate the battery capacity for six hours under the same assumptions, then state why a full-year and extreme-weather study is still needed.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
The six-hour teaching result is about 10 MWh; power, energy, losses, reserve, and extended outages must be evaluated separately.
Knowledge check
Why does a battery rated at 20 MWh still fail if its discharge-power limit is below the critical load?
M3.2 | Interconnect and export safely
Learning objective
Design the utility interface and separate physical surplus from authorized export.
Core lesson
Export is an electrical and commercial interface with the utility, not an automatic privilege of owning generation. Confirm import and export limits, metering, protection, studies, operating tariffs, communications, curtailment rules, and cost responsibility. An islanded system must not unintentionally energize a disconnected utility line. Qualified engineers and the utility define protection and synchronization requirements. In an original dispatch example, local production of 2.0 MW minus facility demand of 1.2 MW and scheduled battery charging of 0.3 MW leaves 0.5 MW available before other losses and limits. Actual export can be lower if the agreement or equipment imposes a cap. Record who can change a setpoint and how changes are authorized, monitored, and restored.
Instructor teaching guidance
Begin by establishing what the learner already knows about m3.2 | interconnect and export safely. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Practice: calculate available export if generation falls to 1.4 MW while load and charging remain unchanged. Draft a utility discussion sheet covering permitted export, interconnection milestones, study costs, metering, islanding, and who pays for network upgrades.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
Available export becomes negative 0.1 MW in the example, so imports or reduced charging are required; utility limits still govern.
Knowledge check
What contractual and technical conditions must be met before a campus can promise grid support?
M3.3 | Offer grid services without risking uptime
Learning objective
Develop a dispatch policy that balances grid value with facility reliability.
Core lesson
Separate flexible computing from service-critical computing. Some batch work can shift to another time or location; latency-sensitive services may require protected capacity. Storage can sometimes reduce peaks or support a grid-service commitment, but using its reserve changes outage readiness. Decide which resource is available, at what time, for how long, and under which service limits. Create dispatch priorities: protect people and critical services, maintain an explicit resilience reserve, honor approved grid obligations, then optimize economics. Test loss of communications, false price signals, forecast errors, and simultaneous cooling and grid stress. Demand-response revenue is an assumption until program eligibility, availability, settlement, and penalties are confirmed. Operators need a manual override and a documented rollback path.
Instructor teaching guidance
Begin by establishing what the learner already knows about m3.3 | offer grid services without risking uptime. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Worked example: an operator promises a 0.4 MW reduction during a heat wave while its battery is nearly depleted. Practice: classify four loads as protected, schedulable, or interruptible, set a reserve rule, and document a no-dispatch condition for the event.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
Grid support is bounded by workload service levels, validated resource availability, and an enforced resilience reserve.
Knowledge check
What should the controller do when a lucrative export event conflicts with minimum outage reserve?
M4.1 | Convert grid value into resident benefit
Learning objective
Translate project value into a measurable, funded household-benefit arrangement.
Core lesson
Electricity exported near homes does not automatically appear as a credit on those households bills. Design a lawful benefit mechanism with the utility, regulator where applicable, community representatives, and qualified advisers. Options to investigate include eligible community-solar arrangements, negotiated utility credits, an operator-funded affordability fund, efficiency upgrades, or support for shared resilience facilities. Define beneficiaries, eligibility, enrollment, privacy, funding source, delivery channel, reporting, and remedies. In this original case, 500 MWh exported at an assumed net payment of $50 per MWh produces $25,000 before any omitted costs. Allocating 40% provides $10,000; divided among 100 eligible homes, that is $100 per home annually before administration. State assumptions openly and prevent double counting of revenue, tax benefits, and avoided costs.
Instructor teaching guidance
Begin by establishing what the learner already knows about m4.1 | convert grid value into resident benefit. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Practice: create a benefit calculation using 300 MWh and an assumed $40 per MWh net payment with a 50% allocation. Specify how 60 eligible households actually receive the benefit. Explain why physical proximity alone does not establish eligibility or savings.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
The example yields $6,000 allocated and $100 per household annually before administration; delivery needs an agreed mechanism.
Knowledge check
What changes if export compensation is lower or program costs exceed the forecast?
M4.2 | Commission, finance, and publish performance
Learning objective
Plan commissioning and lifecycle accountability around the project assumptions.
Core lesson
A concept becomes credible when its equipment, contracts, finances, and controls are verified together. Build a lifecycle model covering capital cost, utility upgrades, energy, cooling, maintenance, insurance, staffing, replacement, financing, and decommissioning. Run downside cases for slower tenant demand, higher rates, delayed connection, battery degradation, and reduced export income. Commission normal operation, component failures, outage transitions, protection interfaces, alarms, manual override, and recovery through approved test plans. Publish a community dashboard with defined meter boundaries, actual versus promised performance, household benefits delivered, complaints resolved, and independent review. Protect operational security and resident privacy. A public promise needs a responsible owner, reporting cadence, corrective action, and an enforceable remedy.
Instructor teaching guidance
Begin by establishing what the learner already knows about m4.2 | commission, finance, and publish performance. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Practice: make a commissioning evidence register with six test scenarios, acceptance evidence, responsible specialists, and unresolved risks. Create a three-case financial sensitivity table and five public metrics. Explain what would trigger a pause in expansion.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
Delivery links engineering acceptance, downside economics, measured community outcomes, and corrective action.
Knowledge check
Why should measured resident benefits appear beside exports and cooling efficiency on the dashboard?
M4.3 | Capstone: defend a community-positive campus
Learning objective
Defend an integrated development concept with calculations, evidence, and accountable community benefit.
Core lesson
Assemble a concept feasibility package for a hypothetical 1 MW IT facility. Use the earlier teaching assumptions only as a starting case, then change at least two inputs and trace their effects. Include demand, phased capacity, site selection, thermal paths, water boundaries, microgrid dispatch, storage sizing, utility interfaces, noise and emissions, economics, resident benefits, and commissioning. Give a conditional go, revise, or no-go recommendation. Separate established technologies from emerging ideas and specify the pilot evidence required for any novel fluid or architecture. Make the promise testable: who benefits, how value reaches them, what the operator must deliver, and how performance is checked. The finished artifact is a concept package for professional review, not a construction design.
Instructor teaching guidance
Begin by establishing what the learner already knows about m4.3 | capstone: defend a community-positive campus. Teach the principle in plain language, define unfamiliar terms, then connect it to the course goal. Ask the learner to explain the idea back in their own words before moving to application.
Applied exercise
Spend 60-90 minutes preparing a six-page brief plus a 24-hour energy sheet and a benefit worksheet. Rubric: demand and site 20 points, cooling and water 20, microgrid and utility 25, economics and resident delivery 20, commissioning and evidence 15. Aim for 80/100 and resolve every unsupported self-reliance or household-savings claim. The portal final quiz is scored separately.
Facilitation sequence
Guide the learner through the application in five steps: describe the present situation, identify the lesson principle, choose an action, name the evidence to review, and define how success will be measured. Use follow-up questions when an answer is vague or unsupported.
Mastery standard
A credible recommendation survives a cloudy outage, a hot day, a reduced export payment, and a resident challenge using documented assumptions.
Knowledge check
Which assumption most affects feasibility, and what measurement or professional study should come next?