The reflex is to write “Rated 3” (or “Tier III”) into the RFP and move on. That reflex is how regional banks end up signing a lease for a facility that advertises mission-critical availability — and then discover, after a single transformer maintenance window, that their core banking platform still went dark. Here is how to think about the rating properly, separate the standard from the marketing, and specify a number that actually survives contact with an outage.
1. Why “just specify Tier III” is the wrong starting point
Walk into any regional bank’s data center strategy meeting and the conversation almost always lands in the same place: “We’re a bank, so we need Tier III.” It feels safe. It sounds mission-critical. It mirrors what the big national banks advertise.
It is also a category mistake. A tier or rating is not a measure of size, capacity, or how modern a facility is. It classifies only the resilience and availability a facility is designed to deliver — and, crucially, the word designed is carrying most of the weight. A rating on a brochure is a design intent, not a guaranteed uptime SLA, and not even a complete description of how the building behaves in a real fault.
For a regional bank, the question is not “what is the highest rating we can afford?” It is: what availability does each of our workloads actually lose money without, and which combination of facilities, subsystems, and operating discipline buys that availability at a cost we can defend to the audit committee? That question forces you through three things most RFPs skip: the difference between the two dominant rating systems, the “weakest subsystem” rule that defines paper redundancy, and the gap between a designed rating and an operated one.
2. TIA-942 Rated 1–4 vs. Uptime Tier I–IV: two different ladders
Because both systems use four ascending levels, they are constantly conflated. They are not interchangeable.
The Uptime Institute Tier Classification is fundamentally a mechanical and electrical (M&E) topology standard. It asks how the power, cooling, and distribution paths are arranged — redundancy, concurrent maintainability, and fault tolerance. ANSI/TIA-942 (current revision TIA-942-C, published May 2024) starts as a telecommunications infrastructure standard but has grown to cover a much broader physical footprint: telecommunications cabling and pathways, architecture/structural, electrical, mechanical, fire safety, security, and operational considerations. TIA originally borrowed Uptime’s “Tier” labels; the confusion that resulted is why TIA renamed its levels to “Ratings.”
Table 1. Uptime Tier III vs. ANSI/TIA-942 Rated 3
The four TIA-942 levels, in plain terms:
·Rated 1 — Basic: a single path for power, cooling, and telecommunications. Any planned or unplanned interruption on that path can stop IT.
·Rated 2 — Redundant Components: N+1 capacity components (a spare UPS, a spare chiller), but still one distribution path. Survives a component failure; does not survive a path failure or path maintenance.
·Rated 3 — Concurrently Maintainable: at least one active (N) and one standby (+1) path. You can take any single path or any single component out for planned work without touching IT. The workhorse for banking and real-time trading.
·Rated 4 — Fault Tolerant: dual active (2N / N+N) paths. Survives both planned maintenance and a single unplanned fault on the active path, with compartmentalization and — uniquely — continuous cooling.
The availability figures below are Uptime design targets, not contractual uptime SLAs — and they are why the jump from Rated 2 to Rated 3 matters more than the jump from 3 to 4:
Table 2. Design availability targets by level
The move from Rated 2 to Rated 3 is where you go from “maintenance causes an outage” to “maintenance doesn’t.” The move from Rated 3 to Rated 4 only buys you resilience against unplanned faults on the active path — a tenth of a percent of uptime, but a step-change in cost and complexity.
3. The weakest-link rule: where “paper redundancy” actually lives
This is the single most important clause for a bank to understand, and the one most often hidden in a marketing deck. TIA-942 does not rate a building as a whole. It rates four subsystems independently on the Rated 1–4 scale — Telecommunications, Architectural/Structural, Electrical, and Mechanical — and the facility’s overall rating is capped by its lowest subsystem.
In practice, a data center that advertises “Rated 3” might have:
·Electrical at Rated 3 (dual UPS, dual switchgear, N+1 generators)
·Mechanical at Rated 3 (dual chillers, dual CRAH)
·Telecommunications cabling at Rated 2 — a single backbone cable tray, single entrance, no diverse second route into the MDA.
Under the weakest-link rule, that facility is Rated 2, no matter what the brochure says. Cut the one fiber path during pathway maintenance — or nick it during a wall cut — and “concurrently maintainable” goes out the window. This is paper redundancy: the topology on the one subsystem the sales team photographed meets Rated 3, while the subsystem that actually carries your traffic collapses to a single point.
A second, subtler form of paper redundancy is mixed certification depth. TIA-942 and Uptime certification comes in layers:
·Design Documents certification — the drawings look right on paper.
·Constructed Facility certification — someone physically walked the site and confirmed it was built to the design.
·Operational Sustainability — the procedures, staffing, maintenance, and testing routines actually deliver the availability the topology implies.
A facility with only a Design certificate has proven nothing about reality. As designers put it: if a building is built to the standard but the operational procedures, disaster-recovery plans, and maintenance/testing routines are not in place, you will not hit your availability targets no matter what the topology is.
Due-diligence checklist for a bank: ask the prospective colo (or your own build) to show, in writing, (1) the per-subsystem ratings, not just a headline number; (2) whether the certificate is Design, Constructed Facility, or Operational; (3) whether the telecom backbone has two physically diverse, separately risk-exposed routes into the computer room; and (4) what happens during a single active-path fault — because Rated 3 is not fault-tolerant.
This is where the “regional bank” specificity matters. A bank is not a monolith. Its workloads have very different pain thresholds, and collapsing them all into one Rated 4 building is usually how capital gets burned. A defensible tiering looks like this:
Table 3. Workload-aligned resilience tiering
The strategic point that surprises most CIOs: running the same IT across two geographically separate Rated 3 facilities usually delivers better total IT availability than piling all redundancy into one Rated 4 building. A single Rated 4 site is still exposed to whole-building and whole-site failures — a regional flood, a grid event, a campus-level fire — that a second, geographically diverse Rated 3 site survives. As mission-critical designers note, it is often more logical to operate IT from two concurrently-maintainable facilities than to concentrate all redundancy in one fault-tolerant box.
For a regional bank, that usually means: a primary Rated 3 colo or owned hall, plus a second Rated 3/2 DR site within realistic RTO/RPO distance, with live data replication. That architecture beats “one Tier IV flagship” on both resilience and price.
5. What to actually write into the RFP
Translate the above into clauses a vendor cannot quietly downgrade:
· State the rating and the certification depth. “Rated 3, Constructed Facility certificate, Operational Sustainability preferred” — not just “Tier III.”
· Demand per-subsystem ratings in the lease schedule. Telecom, electrical, mechanical, architectural — each Rated 3. Headline “Rated 3” with a Rated-2 telecom path is a reject.
· Diverse telecom routes are non-negotiable. Two physically separated entrance paths, routed through different risk corridors, into the MDA. Single-path fiber = Rated 2.
· State your workload and RTO/RPO, then ask for the topology to match. Do not let the facility price a Rated 4 for workloads that only need Rated 2.
· Verify operations, not just drawings. 24/7 on-site staff, documented maintenance windows, generator test cadence, and a tested DR plan. A designed-but-unrun Rated 3 behaves like a Rated 1 in practice.
· Plan for the second site now, even if you build it later. Leave the pathway space, fiber capacity, and power headroom to connect a second Rated 3 site without a rip-and-replace.
Bottom line
A regional bank should not reflexively specify “Rated 3” — and it almost never needs a single “Rated 4” flagship. It should specify Rated 3 across all four subsystems, certified as a built and operated facility, with physically diverse telecom paths, paired with a second geographically separate Rated 3/2 site for disaster recovery. Rated 3 is the sweet spot because it is where planned maintenance stops costing you outages; Rated 4’s incremental fault tolerance is rarely worth its capital cost when geographic diversity buys you more. The rating is only as good as its weakest subsystem and its operating discipline — and “paper redundancy” lives exactly in the gap between the brochure and the basement.
Top comments (0)