A modular AI data center proposal should give the buyer a schedule from design approval through usable IT capacity. Ask the supplier and site team to show what the module includes, what the parcel still needs, and how the two workstreams connect. Use those milestones when comparing powered-land opportunities.
Begin with the initial IT load, hardware requirements, cooling approach and target operating date. Have the engineering team confirm that the proposed module configuration supports the intended workload under the project’s operating conditions.
Define the delivery package
Request a scope schedule covering the module structure, racks, electrical distribution, cooling, controls, fire systems and other proposed equipment. Identify the supplier responsible for each item and the point where its scope ends. Ask the project team to identify any separate packages required to make the module operational.
Record whether the quote covers factory completion, shipment, placement onsite, utility connection or full acceptance. Link the proposed payment and delivery milestones to the supplier’s actual scope so the acquisition budget reflects the work still to complete.
Agree on the connection requirements before site selection
Have the supplier provide drawings and specifications for the module’s electrical, cooling, water, drainage and network interfaces. Ask the site engineers to review them against the available services and proposed layout. Document who supplies, installs and tests each connection.
For example, ask whether cooling equipment is included inside the delivered package or supplied separately on the parcel. Confirm the space, electrical demand and service access associated with that arrangement. Review the answers alongside the cooling and water diligence guide.
Build the site schedule beside the factory schedule
Request a factory schedule showing design release, equipment procurement, assembly, testing and shipment. On the site schedule, show surveys, design, applicable approvals, civil work, foundations, utility readiness and fiber activation. Identify which tasks can run concurrently and which require a completed predecessor.
Put delivery-route and unloading readiness into the same plan. Ask the responsible specialists to confirm the equipment delivery approach before fixing the shipment date. If a site dependency slips, have the team explain the storage, handling and schedule consequences.
Check what testing and certifications cover
Request the factory test plan and the proposed onsite commissioning and acceptance plan. Have the buyer’s engineering team identify the evidence needed to accept the assembled facility, including the systems provided by other contractors.
If the supplier references Uptime Institute TIER-Ready status, ask for the exact reviewed solution and confirm that the proposed configuration matches it. Uptime Institute’s terms tie the designation to a specific prefabricated or predesigned solution and distinguish it from site Tier Certification. Uptime Institute TIER-Ready scope and limitations
For later phases, ask how installation and testing will interact with operating equipment. Uptime Institute’s discussion of modular and phased construction highlights the need to coordinate shared systems and commissioning as capacity grows. Uptime Institute guidance on modular and phased construction
Test the proposed operating date
Consider a hypothetical supplier that can ship a module in week 16. The site plan expects the electrical connection in week 20 and final acceptance after connection and testing. The buyer should ask for the operating milestone supported by the combined schedule, then review the consequences of a later electrical connection. These invented dates describe no Ace Miners opportunity.
For each candidate site, retain a milestone register with scope, responsible party, supporting evidence and unresolved dependencies. Review the power delivery documents and total deployment cost on that same basis.
Browse the Ace Miners powered-land directory or send your modular deployment requirements. Include initial IT load, module configuration, service assumptions and target operating date so sites can be assessed against the full installation plan.
