Planned Tier III data center design: what buyers should check
A Tier III data center is defined by how it is maintained, not by how it looks on a brochure. Uptime Institute’s Tier III standard means the facility is concurrently maintainable: each capacity component and distribution path that supports the IT load can be removed from service for planned work without shutting down the load. That is the industry language buyers already know. The harder question on a Colorado data center development site is whether that standard is a design basis for a build-to-suit data center, or a claim about a building that already exists.
This note separates design basis from built facility, and lists what to verify when an energized data center Colorado site offers a planned Tier III path.
Design basis vs built facility
“Tier III” on a site packet can mean three different things. First, a finished facility that has been designed, constructed, and in some cases certified to the Tier III standard. Second, a design package that targets concurrent maintainability for a building that has not been built yet. Third, marketing shorthand that confuses redundancy language with a specific Tier outcome.
Buyers should ask which of those three is on offer. A planned Tier III path is a real product when the developer can show how power and cooling will be laid out for concurrent maintenance, how the building shell and equipment pads will support that layout, and what remains to be engineered after a tenant’s load and density are known. It is not the same as walking into a finished hall.
On a build-to-suit data center, that distinction matters for schedule and for underwriting. The land and utility service can be ready while the Tier outcome is still a design commitment. Treat “concurrently maintainable design available” as a design basis until the facility is actually built and commissioned to that intent.
What concurrently maintainable actually requires
Concurrent maintainability is about paths, not only about spare parts. In plain terms, there must be an N+1 path for power and for cooling so that planned maintenance on one side does not take the IT load offline. Dual-corded IT equipment, redundant UPS capacity, redundant cooling capacity, and distribution that can be isolated without a shutdown are the usual building blocks. The exact topology is an engineering choice; the test is the same: can each critical path be worked on while the load stays up.
That is why Tier III language belongs next to single-line diagrams and cooling schematics, not only next to a marketing headline. Ask for the intended maintainable paths, the planned failure domains, and which systems are shared versus dedicated. Do not invent a certification timeline from a design basis alone. Certification, when a buyer wants it, is a separate process that follows design and construction; it is not automatic because the words “Tier III” appear in a deck.
Questions that separate design from claim
- Is concurrent maintainability a design basis for a future build, or a statement about a finished facility?
- Which power and cooling paths are intended to stay online during planned maintenance?
- What density and cooling method are assumed in the design (air, direct-to-chip liquid, or both)?
- What must still be engineered after the tenant’s IT load and redundancy choices are fixed?
- Who owns commissioning, and what evidence will be available at ready-for-service?
Build-to-suit on an energized site
Build-to-suit data center projects often start with powered land: utility service at the site, switchgear and distribution that can accept IT load, fiber paths into the property, and room for a building and equipment pads. The tenant may bring pods or containers first, then move to a purpose-built hall. A concurrently maintainable design fits naturally in that second step, because the shell, mechanical yards, and electrical rooms can be sized for the Tier outcome the tenant is buying.
Energized utility service matters here because Tier design is useless without power that can actually feed the redundant paths. A data center site Colorado buyers evaluate should make clear what is already live at the utility interface, what IT capacity that supports under different cooling and redundancy choices, and what expansion still depends on a utility upgrade. Fiber diversity belongs on the same list: concurrent maintainability inside the building does not replace the need for diverse paths out of it.
Colorado context for planned Tier III work
Colorado data center development outside the densest metro campuses often pairs secondary-market land with utility service that is already in place. That combination can shorten the path from signing to ready-for-service when the site is energized and the building program is known. It does not, by itself, deliver a Tier III facility. Climate, water strategy, staff access, and interconnection still have to be checked the way they would be checked on any site.
For buyers comparing primary markets to Front Range options, the useful frame is: what is energized today, what is design basis for the build-to-suit option, and what remains contingent on tenant design. Keep those three layers separate in the diligence folder.
Front Range Compute in Larkspur
Front Range Compute is a site being developed by Frost River Capital LLC in Larkspur, Colorado, about 30 minutes south of Denver off I-25. The site has about 3 MW of energized utility service from CORE Electric at 480V, outside Xcel’s data-center tariff, with existing switchgear and 415/240V distribution. IT capacity is roughly 2–2.5 MW depending on cooling and redundancy design, with an expansion path of about 9 MW via utility upgrade. Two diverse 100 Gbps fiber paths are available from Comcast, with additional carriers available. The parcel is about 2.8 acres, with about 12,000 sq ft of building and equipment pads in the program, and a target of about six months from signing to ready-for-service.
Powered land is the first offer; build-to-suit colocation is second. For the build-to-suit option, concurrently maintainable design is available as a projected design basis. That is planned Tier III development language, not a claim that a finished Tier III facility already stands at Larkspur. Projected density is 40+ kW/rack with direct-to-chip liquid cooling, or air at lower densities. Pricing is on request.
A buyer checklist for planned Tier III
Start with what is live: utility service, switchgear, fiber entries, and land. Then read the Tier language as design intent for the build-to-suit scope. Ask for the maintainable power and cooling paths, the density and cooling assumptions, and the commissioning plan. Keep certification claims out of the conversation until design and construction catch up to them.
A planned Tier III data center is a design commitment buyers can diligence. A finished Tier III facility is a different asset. For a one-page view of Front Range Compute, start at the site overview, request the spec sheet, or write rob@frostrivercapital.com.