The Definitive Guide toAI Data Centers
Ask the GuideAboutAccount

Chapter 6.6

In this chapter · 7 sections
Term help
Terms in this chapter (39)

Construction Execution, Sequencing & Phased Turnover

An AI data center earns nothing until megawatts are energized and accepted. The schedule that matters delivers turnover-sized blocks against a fast-depreciating GPU life, and is sequenced around whichever of civil work, equipment, utility power or acceptance controls the finish.

ThreadsPower-boundDensity ramp

What you'll decide here

  1. Hard-bid, CM-at-risk GMP or design-build/EPC: who carries schedule risk when owner-furnished gear is the long pole (retained custody and remedies: Chapter 2.4).
  2. Turnover block size (building, hall or pod): it sets how early you energize and earn, and how much commissioning runs beside live space.
  3. Where the critical path runs: civil and shell, long-lead switchgear and transformers, utility energization, or electricians and pipefitters at peak rough-in.
  4. How Cx Levels 1–5 fit the schedule, and what each proves: factory tests, surrogate and AI-emulating loads, injection/HIL, isolated scopes, a product-representative workload.
  5. Skilled-trades strategy (prefab, multi-shift, travel premiums, self-perform or subcontract): at GC selection, weigh package work hours against qualified crew hours available, before peak.

The design is frozen, the slab basis is set, the cooling plant is specified and the fire strategy is approved. None of it earns a dollar until megawatts are energized, accepted and handed to the cluster team. The interval that decides whether that happens on time runs from the agreed construction start to a GPU drawing its first watt. Steel, slab and skin are schedulable packages, but weather, ground conditions, inspections and access can still put them on the critical path. What kills AI-data-center schedules is a short, repeating list: long-lead electrical gear that does not show up, a utility energization date the owner does not control, a trades labor pool that cannot staff the peak, and, as of 2026, organized local opposition.

Opposition now has numbers. Data Center Watch counted ~$130B of US projects blocked or delayed in Q1 2026, and nearly $68B more across at least 45 projects in Q2. That is a tracker's project-value sum, and "delayed" is not "dead". Cities have also started pausing applications outright: Raleigh stopped accepting and reviewing data-center development applications for six months from October 6, 2026. A 16-month modular schedule is fiction if rezoning takes 18 (→ Chapter 3.11).

Pennsylvania made local consent a permit gate. Executive Order 2026-05, effective August 18, 2026, removes all data-center projects from Fast Track, and its NDA ban binds agencies under the governor's jurisdiction, not private parties. For DEP applications filed after that date for projects over 25 MW of peak demand, a developer who signs a project-specific GRID Consent Order and Agreement (COA) gets rolling review. DEP still cannot issue permits until local-plan consistency and the required subdivision and zoning approvals are documented. Without a COA, review itself waits for those local prerequisites and for any required water-withdrawal or wastewater-discharge authorization, and permits issue only after DEP has received and reviewed all the necessary applications. Execution is the work of sequencing around these constraints so that the parts you can control are never what you are waiting on.

The delivery-model fork (lump-sum, CM-at-risk or design-build/EPC) decides who eats schedule risk. The canonical sequence (civil → shell → MEP rough-in → equipment set → fit-out) has predictable bottlenecks. Phased turnover is a revenue lever: the turnover unit you choose sets how early the first block starts earning against a short GPU life. The trades shortage is a first-order schedule risk to mitigate at GC selection, alongside the quality and inspection regime that carries a hall from substantial completion into commissioning readiness.

The skilled-workforce program (recruiting, training, retention) lives in Chapter 14.11; here it is a construction-schedule input, and the hiring numbers are in the trades section below. The owners have started paying to train workers. Meta committed $115M for the first year of a program that starts with about 5,000 construction trainees, Google $50M across 14 labor unions and four trade and contractor associations, and BlackRock $100M over five years (NYT, Jul 2026). These are announced funding and targets, not completed training or staffed crews. The construction-safety program lives in Chapter 6.9; here it is an interface, not the subject.

The delivery-model fork: who carries schedule risk

Before a shovel moves, the owner picks how the build is contracted, and that choice allocates the two risks that dominate an AI build: schedule and trade coordination. The fork seldom turns on lowest first cost: on a fully contracted 200 MW block, six months of schedule outweighs the contractor's fee delta many times over (the phased-turnover section below sizes it). The question is who is on the hook when the switchgear slips and the electricians are double-booked across three concurrent campuses.

Lump-sum / hard-bid transfers price risk to the GC but assumes a complete, frozen design at bid time. That is almost never true for a fast-tracked AI build, where the rack generation is still moving under the design. Change orders become the battleground, and the owner discovers that a fixed price bought on incomplete documents is not actually fixed. Construction-management-at-risk (CMAR) with a guaranteed maximum price (GMP) suits fast-track projects where early contractor input and a firm cost cap both matter. The GC joins during design and prices a GMP against a still-developing set. The GMP is a price ceiling on included scope, not a split of schedule risk: completion dates, delay damages and any savings share are set separately in the contract, and exclusions, allowances and owner changes stay contract-specific. CMAR preserves the ability to start civil while the fit-out design matures. Integrated design-build / EPC collapses designer and builder into one contract and one schedule. It is the fastest path to a single throat to choke, favored when speed-to-power dominates and the owner will trade some price transparency for it. Choose wrong, with a hard-bid contract on a moving design, and the change-order war costs more schedule than the fixed price ever saved on fee.

Build-delivery model → risk allocation and fit
Delivery modelDesign completeness at startWho carries schedule riskTrade-coordination ownerBest fit
Lump-sum / hard-bidMust be ~complete & frozenGC (in theory); owner via change orders (in practice)GCStable, repeatable, fully-designed shells
CMAR + GMPDeveloping; priced at GMP setCM: contracted completion dates. Owner: retained OFE and utility dependencies, plus delay the owner causes. Relief and remedies follow the contractGC, with early owner inputFast-track work where early contractor input and a firm cost cap both matter
Design-build / EPCPerformance-spec; design proceeds in parallelSingle entity (designer+builder)EPC integratorSpeed-to-power-dominated; single-throat accountability
Owner-led multi-primeVaries by packageOwner (the integrator role)Owner / owner's CMSophisticated self-perform owners; max control, max risk
Practitioner framing for AI/hyperscale builds, 2026. "Owner-furnished equipment" (OFE) is switchgear, transformers, CDUs or GPUs that the owner buys directly to protect lead time. Under every model the owner keeps supplier and delivery exposure for its own equipment. The GC or supplier takes on receipt, storage, protection, installation, testing and warranty only where the contract assigns them.

The construction sequence and where it bottlenecks

The canonical sequence is linear on paper and overlapped in reality. Civil and earthwork (mass grading, stormwater, deep utilities, foundations) is weather-exposed and front-loaded. Shell (structural steel or tilt-up, roof, skin) makes the building watertight so interior trades can work year-round. MEP rough-in (electrical raceway, bus duct, mechanical piping, the liquid-cooling distribution backbone) is the labor-intensive heart of the schedule and the first place the trades shortage bites. Equipment set lands the switchgear, UPS/BESS, CDUs, chillers, generators and heavy mechanical plant. It is rigging-and-crane choreography gated by when the owner-furnished gear arrives. Fit-out (busway runs to the rack, manifold and quick-disconnect plumbing, containment, terminations, and the thousand small completions) is where substantial completion is won or lost.

How much overlap shortens delivery depends on which civil, equipment, utility or acceptance path controls. The worked case below shows how to find it. The path can run through the concrete when civil readiness slips past equipment delivery, and money cannot remove every predecessor. Civil and shell durations depend on weather, ground, curing, inspections and available crews. Other binding constraints sit downstream and outside the GC's direct control: the date the utility energizes the service, the date the owner-furnished switchgear and transformers land, and the number of qualified electricians and pipefitters available during rough-in and fit-out. Keep those three off the path of the things you control and you protect the schedule. Let the trades become the constraint at peak manpower and the whole back end slides, because fit-out and commissioning are where the shortage concentrates.

The cooling package changes critical path when civil readiness slips

22 weeks · assumedmodeled
Cooling package: assumed accepted-service milestone measured from release on the shared calendar
Scope & caveats

Assumed cooling-package sequence on one calendar from release. A separate self-powered rig flushes isolated piping; installed CDU startup and tests await utility. Chapter 6.6’s worked case states every input, civil/utility crossover and release owner; Chapter 2.1 owns the network method. No supplier duration range is established.

Use the network from Chapter 2.1. Installation finishes at max(12, 14) + 3 = week 17. The independent rig completes fluid acceptance at 17 + 2 = week 19. Energized startup finishes at max(19, 18) + 1 = week 20; functional and integrated acceptance then finish at 20 + 2 = week 22. Accepted service is max(22, 20) = week 22. Delivery is the controlling predecessor to installation; civil has two weeks before it reaches that gate. Pick the baseline package sequence and protect its cleaning and test windows.

The civil flip is explicit. Site readiness at week 18 gives installation at 21, readiness at 24 and accepted service at week 26. Civil becomes controlling above week 14, so paying to expedite an already-delivered CDU does not recover this slip. In the utility flip, utility at week 24 delays startup until then: max(19, 24) + 1 = week 25, followed by two test weeks, gives accepted service at week 27. Utility becomes controlling above week 19, when fluid acceptance is otherwise ready. Fix the delayed gate, not the test duration. This is why the concrete can own the finish even on a project famous for electrical lead times.

Release each step from its actual record. The GC confirms slab/access and supports. The installing contractor closes joints and installation inspection. The cooling specialist supplies the flush and fluid-quality records. The commissioning authority accepts the test scope, and the authority having jurisdiction grants the required use/occupancy permission. The owner accepts the block only after those gates close. GAO supplies the schedule method, Chapter 2.1 owns the integrated network, Chapter 5.13 owns hydraulic qualification, and Chapter 13.5 owns cooling acceptance.

Deep dive: the liquid-cooling backbone changes the sequence. Pipe before you can pull rack.

Chilled-water air halls already have facility piping to flush, pressure-test and accept before startup. A direct-to-chip liquid hall adds the CDU, technology-cooling-loop and rack interfaces on top of that. The facility-water and technology-cooling-loop distribution (risers, headers, the CDU gallery, in-rack manifolds and tray quick-connects) is heavy, code-governed charged piping (ASME B31.x / EN 13480). Its material and jointing method determine installation, weld/NDE scope, flushing and pressure testing before the racks it serves can be energized. A GB300 NVL72 rack has 27 liquid-cooled trays (18 compute, 9 switch) fed by quick-connects from the rear supply/return manifolds (Lenovo GB300 NVL72 product guide), so there are at least 54 tray-level connections (a supply and a return per tray) before counting any inside the trays. Each one is a leak-test point; get the rack maker's connection schedule for the exact rack revision.

That work lands squarely in the MEP rough-in and fit-out windows and competes for the same pipefitter and welder labor that is already short. Multi-stage flushing and fluid-quality acceptance, with a duration derived from loop volume, method, acceptance samples and retest allowance, gate the cooling acceptance that gates the GPU burn-in. Whether cooling distribution controls first-watt depends on the predecessor network, as the worked case shows, and in a liquid hall it can. Operators that prefabricate skidded CDU and manifold assemblies off-site (→ Chapter 6.4) pull this scope out of the congested on-site fit-out window and into a controlled factory, which is as much a labor-availability strategy as a quality one. The piping engineering itself is owned in Chapter 5.4 (DLC) and its pressure-system code basis in Chapter 5.13; here it is a schedule dependency that reorders the sequence.

Phased turnover: the unit you energize is the unit you earn on

The biggest schedule gain in the construction phase comes from not waiting for the whole building. AI campuses are built as repeated, near-identical units, a baseline pod or hall design stamped out across phases, so the first block can be energized, commissioned and producing while later blocks are still being poured. Mastt’s April 2026 practitioner estimate is 18–24 months for greenfield hyperscale-campus construction and 12–18 months for colocation. The decision is how big the turnover block should be: whole building, data hall, or pod/row. Smaller blocks energize earlier and start the revenue clock sooner. They also multiply the number of times you must commission and partially energize next to occupied, live space, which brings concurrent-maintainability constraints, arc-flash boundaries around energized gear, and life-safety separation between a construction zone and a running hall into the schedule as hard interfaces.

Abilene shows the first block and the campus ramp running on different clocks. Epoch AI’s site directory (updated July 2026) dates construction start to May 2024 and Building 1 fully operational to about September 2025, some 16 months later. Epoch’s estimate for late July 2026 is about 421 MW of IT power, and its projection for around November 2026 is about 843 MW of IT. In its November 2025 analysis Epoch expected the campus to reach 1 GW of facility power in July 2026; the ramp now trails that earlier projection by months. All of these rest on satellite imagery, a model of the cooling equipment, and company and regulatory filings, so they are estimates, not accepted or billed capacity. The first block sets when revenue starts and the rest of the campus ramps behind it; at Abilene, the ramp is where the dates have moved.

The economics are what make phasing dominate. Bringing a fully contracted 200 MW block into accepted service six months early moves about $1.2–1.3B of gross revenue forward; the derivation, built on SemiAnalysis’s June 2026 per-GW estimate, and its limits are in Chapter 2.2. Compare that with a GPU whose useful life the guide's contested bear case tests at 2–3 years, against published estimates of 4–6 years and book policies of 5–6 years. Every month a finished, un-energized hall sits dark burns a month of that short asset life at zero return. So measure the schedule in energized, accepted, GPU-ready megawatts per quarter, not in percent-complete.

Commissioning woven into the schedule, not bolted on at the end

The most expensive commissioning mistake is treating Cx as a phase that begins only when construction ends. The Cx Level ladder (L1–L5) runs through the entire build, and construction execution either creates the test and inspection records as it goes or pays to reconstruct them later. Level 1 (factory witness / FAT) happens at the manufacturer before equipment ships. The agreed FAT scope checks switchgear, UPS and CDUs against their specifications and gives the owner test results before site installation. Defects found late can land in the critical-path fit-out window and compete with energization for the same crews. Owner-witnessed FAT is separate from the manufacturer's routine factory testing. Level 2 (site acceptance / installation verification) is the pre-energization inspection work that overlaps directly with equipment set and fit-out. Level 3 (pre-functional, one system standalone and energized) and Level 4 (functional performance across the operating range, per discipline) cover energization, load-bank acceptance and redundancy-topology validation. They begin the moment a block's gear is set and its service is energized, well before the building as a whole is done. Level 5 (integrated systems testing, IST) is the approved integrated-scenario gate before handover.

Build the commissioning windows into the construction logic as named activities with durations, and protect them. Facility air-rejecting load banks do not cover every TCS or workload dynamic. Liquid-cooled and AI-emulating test loads show only what their surrogate setup was specified to represent. A staged product-representative workload then supplies whatever normal-operation results the commissioning plan requires beyond that. Protective functions stay in injection/HIL or an isolated controlled scope unless the approved risk plan explicitly requires otherwise. The full Cx program (levels, scripts, acceptance gates, and the load-realism problem) is owned in Chapter 13.1 and the cooling-acceptance specifics in Chapter 13.5. The construction job is to make the schedule honor them.

The skilled-trades shortage as a first-order schedule risk

Labor is the constraint most likely to be underestimated at GMP signing and most painful at peak manpower. In January 2026 ABC modeled the 2026 hiring need for all US construction at about 349,000 workers, mostly to replace retirees. A year earlier it had projected 499,000 for the same year. Either way it is a modeled national hiring need for all construction, not a data-center shortfall. IEC's 2023 Emerging Leaders survey of member contractors put electricians retiring at ~10,000 a year against ~7,000 entering the trade (IEC, 2023). It is a survey picture, not a national entry/exit census, so read it as direction, not as a deficit you can compound year on year. Electricians, MEP engineers, commissioning specialists and project managers are consistently named the hardest roles to fill. Schedule electrical equipment deliveries and qualified electrical crews separately, because switchgear that arrives on time still sits idle until a crew is free to set and terminate it. The shortage bites during the MEP rough-in and fit-out windows that already sit on the critical path.

Two measures price the delay differently. STL Partners models about $14M per month of delay for an indicative 60 MW US project (2025), a figure that combines lost revenue, cost overruns and contractual penalties. At ~$12–13B/GW/year of AI-capacity revenue, the same block represents roughly $60–65M per month of gross revenue, which is a different loss measure. The trades shortage is therefore a site-selection constraint: operators choose markets partly on the depth of the local skilled-labor pool, because a site you cannot staff is a site you cannot energize on schedule. Mitigation belongs at GC selection, not in a back-office HR plan. The main levers:

  • Prefabrication and modularization (→ Chapter 6.4) shifts skidded power and cooling assembly into a factory, which moves labor hours off the congested site into a controlled labor pool. Ask the GC to show the site installation, connection and testing hours that remain in this project's package scope and crew plan; there is no reliable portable percentage.
  • Self-perform vs subcontract. GCs that self-perform electrical and mechanical control their own crews instead of competing for them on the spot market. The delivery-model choice and the labor strategy are coupled.
  • Multi-shift and travel-crew premiums. Second shifts and imported traveling trades close the local gap at a cost premium. Data-center construction pays about 32% more than other construction projects in Skillit's hiring data, and Indeed puts the premium for hourly data-center installation and maintenance roles at about 42%. Neither prices second-shift or travel premiums, so price those per project.
  • Early trade-partner lock-in and stacked starts. Commit subcontractors during design and stagger trade peaks across a phased campus, so the same crews flow from block to block instead of all peaking at once.

The owner-side workforce program (apprenticeships, pipeline development, retention) is the subject of Chapter 14.11. The construction-execution point is narrower: if the trades strategy is not decided at GC selection, it will be discovered at peak manpower, and by then the only levers left are the expensive ones.

18–24 moestimate
Mastt’s April 2026 greenfield hyperscale-campus construction estimate; colocation has a separate 12–18-month estimate
Scope & caveats

Practitioner estimate for greenfield hyperscale construction; Mastt separately estimates colocation at 12–18 months. Define construction start and acceptance milestone in the IMS. This is not a measured cohort or a shell-to-MEP interval.

~10k vs ~7kestimate
electricians retiring vs entering the US trade per year (IEC 2023 member survey, not a national census)
Scope & caveats

Survey-derived observation from the IEC 2023 Emerging Leaders report's 'current state of industry' findings (Independent Electrical Contractors member survey, US): 7,000 new electricians join each year while 10,000 retire. Not a national entry/exit census, and the entrant, completion, retirement and exit definitions do not match — do not compound it into a running national deficit.

~$14M/momodeled
STL Partners’ modeled monthly cost of delaying a 60 MW US data center: lost revenue, cost overruns, contractual penalties
Scope & caveats

Consultant estimate for an illustrative 60 MW US project, combining lost revenue, cost overruns and contractual penalties. It is a delay-cost figure, not a rent quote.

The guide's roughly $60-65M per month for the same 60 MW block is gross AI-cloud revenue brought forward at ~$12-13B/GW/year. It measures something different and is not a like-for-like comparison.

>160 wk
Wood Mackenzie: US substation-transformer lead times beyond 160 weeks (reported May 2026), the OFE long pole
Scope & caveats

Reported market assessment for US substation transformers, not a universal minimum, survey mean, bounded order distribution or generator step-up lead time

An earlier Wood Mackenzie figure, the 128-week average in its Q2 2025 survey (published October 2025), measured a different period; use the 2026 assessment for current planning.

~$12–13B/GW-yrestimate
SemiAnalysis's estimate of AI-cloud contract revenue per GW-year of contracted critical IT
Scope & caveats

The denominator is contracted critical IT, not the facility's gross electrical capacity, and the figure is gross revenue brought forward, not profit or NPV. It is SemiAnalysis's rental/IaaS number, and it is contested. SemiAnalysis's Tokenomics model (Aug 2026) puts lab API inference revenue far higher, above $100B/GW/year on a GB300 cluster against about $12B/GW/year of rental cost. That figure comes from a model and moves with utilization and price mix, so keep the two numbers separate.

Quality, inspections, and the path to commissioning readiness

Between "the building is done" and "the cluster team can take it" sits a quality gauntlet that, run poorly, becomes the longest unplanned slip in the project. The path runs through inspections and authority-having-jurisdiction (AHJ) sign-offs (electrical, mechanical, fire, life-safety, occupancy), each of which can stop energization cold. It runs through quality-control verification of the trades' work: weld NDE on charged piping, megger and torque verification on electrical terminations, fluid-quality acceptance on the cooling loops. And it ends at substantial completion, the contractual milestone at which the owner can beneficially occupy. Substantial completion and commissioning readiness are separate gates whose order follows the contracted work and intended use. The gap between them is the punch list and the deficiency-tracking discipline that closes it.

For products supplied under UL Solutions' September 2026 certification programs, put the certification scope and approved configuration into submittals and turnover records. Both are UL Outlines of Investigation: UL 4501 covers eligible direct-to-chip liquid-cooling components and subassemblies, and UL 2140 covers factory-built prefabricated power distribution assemblies. Before shipment, agree which site connections, substitutions or changes the certificate covers and which need a separate evaluation or an AHJ inspection. A certificate does not replace checking the installation on site or formal acceptance. Chapter 5.11 covers component qualification.

The decision here is whether quality is verified continuously as the work is installed or audited at the end. Continuous in-line QA uses the digital Cx platform to capture installation verification and baseline "fingerprint" data as each subsystem is built (→ Chapter 13.2). It front-loads defect discovery into the construction window, where fixes are cheap. End-of-line auditing concentrates discovery into the handover window, where every defect is on the critical path to first-watt and every fix competes with the same short trades for attention. Handing over cleanly between contract completion and Cx readiness is won months earlier, by the QC regime written into the GC's execution plan, not by heroics at the finish. Run it sloppily and deficiencies surface during L4/L5 testing, where they read as commissioning failures, blow the IST window, and push the turnover block and its revenue into the next quarter.

Deep dive: substantial completion, the punch list, and why "done" is a defined term

"Done" is contractual, not intuitive. Substantial completion is the milestone at which the work is complete enough that the owner can use the facility for its intended purpose. It typically triggers the start of warranty periods, the transfer of certain risk and insurance, and the release of much of the retainage. It does not mean every item is finished: the remaining items (the punch list) just do not prevent beneficial use. Final completion comes later, when the punch list is closed.

For an AI build the seam that matters is the one between substantial completion and commissioning readiness, the point at which a block has enough verified, energized, accepted infrastructure for L3/L4/L5 testing to proceed. These are not the same milestone, and conflating them is a classic schedule trap. A hall can be "substantially complete" with a punch list that still contains items fatal to commissioning: an un-flushed cooling loop, an unproven protective-relay setting, an incomplete BMS point-list. The disciplined execution plan defines commissioning readiness as its own gate with its own checklist, sequenced against the contract package rather than by one universal order. On a shell-or-package contract, readiness can legitimately follow substantial completion. Where the accepted work is the operating hall itself, an un-flushed loop defeats the intended use the milestone certifies. Name construction completion, ready-for-startup, ready-for-FPT/IST, contract-specific substantial completion and acceptance as separate gates, and put commissioning readiness before the cluster team's GPU burn-in. The commissioning program that consumes that readiness is owned in Chapter 13.1. The construction job is to deliver a block that is genuinely ready, not merely substantially complete.

Release the block whose installation, cleaning, tests and authority permissions have all closed. Expedite the gate controlling that date and protect the test windows; squeezing commissioning to preserve a calendar promise moves defects into the occupied hall.

Construction execution is the hinge between the building and the cluster. The long-lead equipment it sequences around is registered in Chapter 2.3. The structural and slab basis it builds to is in Chapter 6.2. Prefabrication and its project-specific labor and schedule tradeoff is in Chapter 6.4. The fire and life-safety regime that gates partial-energization separation is in Chapter 6.5, and the construction-safety / arc-flash program it interfaces with is in Chapter 6.9. The liquid distribution that reorders the sequence is engineered in Chapter 5.4. The commissioning program it weaves in (levels, scripts, electrical and cooling acceptance, and Level-5 IST) is the whole of Chapter 13.1, Chapter 13.2, Chapter 13.5, and Chapter 13.6. The workforce program behind the trades it depends on is in Chapter 14.11.
Cite this chapter
Fehn, J. (2026). Construction Execution, Sequencing & Phased Turnover (Chapter 6.6). The Definitive Guide to AI Data Centers. https://aidatacenterguide.com/part-6-the-building-civil-structural-fire-life-safety-and-construction-execution/6-6-construction-execution-sequencing-and-phased-turnover (accessed 2026-10-25).
@misc{aidc-6-6,
  author       = {Fehn, Jacob},
  title        = {Construction Execution, Sequencing & Phased Turnover (Chapter 6.6)},
  howpublished = {The Definitive Guide to AI Data Centers},
  year         = {2026},
  url          = {https://aidatacenterguide.com/part-6-the-building-civil-structural-fire-life-safety-and-construction-execution/6-6-construction-execution-sequencing-and-phased-turnover},
  note         = {Accessed 2026-10-25}
}
Spotted an error? Suggest an edit