Data Center Services: Colocation, Hosting, and Facility Management

Data center services encompass the physical infrastructure, operational frameworks, and managed functions that house, connect, and sustain computing equipment at scale. This page covers the structural classification of colocation, hosting, and facility management as distinct service categories, the operational mechanics through which each functions, and the regulatory and standards landscape governing facility performance. These distinctions matter because procurement decisions, contract structures, and compliance obligations differ substantially across service types.

Definition and scope

Data center services occupy the physical and operational layer of data systems infrastructure — the tier below software platforms and above raw network connectivity. The Uptime Institute's Tier Classification System, a widely recognized industry standard, defines four facility tiers based on redundancy and fault tolerance, ranging from Tier I (single path, no redundancy) to Tier IV (fully fault-tolerant, 99.995% availability). These classifications directly influence procurement decisions, pricing structures, and compliance posture.

The service landscape divides into three structurally distinct categories:

1. Colocation (colo) — A customer owns its hardware and leases physical space, power, cooling, and network connectivity from a third-party facility. The facility operator maintains the building infrastructure; the customer retains responsibility for servers, storage, and operating systems.
2. Hosted services — The facility operator owns and operates the hardware, delivering compute, storage, or network capacity as a managed service. The customer configures and uses resources without owning the underlying equipment.
3. Facility management — A contracted operator assumes operational responsibility for a customer-owned or customer-leased data center, including staffing, maintenance scheduling, vendor coordination, and compliance documentation.

The American National Standards Institute (ANSI) and TIA jointly publish ANSI/TIA-942, the Telecommunications Infrastructure Standard for Data Centers, which establishes structured cabling, space, and power requirements that operators and auditors reference when evaluating facility classification claims.

How it works

Colocation facilities operate on a power-density and space model. Customers contract for cabinet space (measured in rack units, where 1U equals 1.75 inches of vertical rack space), allocated power draw (measured in kilowatts per cabinet), and cross-connect ports that link customer equipment to carrier networks. Facilities bill on a combination of space, committed power, and bandwidth, with typical enterprise colocation contracts spanning 1 to 5 years.

Power and cooling are the two primary operational variables in facility management. The Power Usage Effectiveness (PUE) metric, defined by the Green Grid consortium, measures total facility energy consumption divided by IT equipment energy consumption. A PUE of 1.0 represents theoretical perfection; the U.S. Department of Energy's Better Buildings Initiative reported an average PUE of approximately 1.58 for U.S. data centers in its 2021 Data Center Energy Efficiency Report, reflecting the overhead cost of cooling, lighting, and power distribution.

Physical security at qualified facilities follows NIST Special Publication 800-53, specifically control family PE (Physical and Environmental Protection), which mandates access control points, visitor logging, surveillance, and environmental monitoring (NIST SP 800-53 Rev. 5). Federal contractors operating in or procuring colocation services must align facility controls with these requirements.

Data backup and recovery services depend heavily on facility-level redundancy — the physical layer directly determines recovery time objectives achievable by higher-level software solutions.

Common scenarios

Enterprise colocation applies when an organization operates proprietary hardware that cannot migrate to cloud platforms due to latency requirements, regulatory constraints, or licensing structures. Financial services firms frequently colocate trading infrastructure in carrier-neutral facilities to achieve sub-millisecond latency via direct cross-connects to exchange networks.

Managed hosting applies when an organization requires dedicated compute and storage capacity but lacks internal staff to maintain physical hardware. A healthcare organization subject to HIPAA's Security Rule may contract managed hosting specifically because the vendor provides documented physical safeguard controls under 45 C.F.R. § 164.310, transferring operational accountability without transferring data ownership.

Facility management contracts apply when a large enterprise or government agency owns its data center real estate but lacks the operational depth to maintain it continuously. Federal civilian agencies have contracted facility management under General Services Administration (GSA) schedules, specifically the IT Schedule 70 (now consolidated into the Multiple Award Schedule), to cover operations, maintenance, and energy optimization.

Data security and compliance services intersect with all three scenarios — compliance audits for SOC 2 Type II, ISO/IEC 27001, and FedRAMP each require documented physical access controls that the facility layer must satisfy before software-level controls are evaluated.

Decision boundaries

The structural boundary between colocation and managed hosting turns on equipment ownership. In colocation, the customer retains asset ownership and bears hardware refresh cycles, warranty management, and end-of-life disposal obligations under EPA guidelines for electronic waste. In managed hosting, the operator absorbs those lifecycle costs, which are amortized into service pricing.

The boundary between managed hosting and cloud data services turns on multi-tenancy architecture and provisioning elasticity. Managed hosting typically delivers dedicated, single-tenant hardware with fixed capacity; cloud services deliver virtualized, multi-tenant resources with dynamic scaling. Organizations with strict data residency requirements under regulations such as the California Consumer Privacy Act (CCPA, Cal. Civ. Code § 1798.100 et seq.) or sector-specific frameworks may find that dedicated hosted infrastructure provides cleaner audit boundaries than shared cloud environments.

Facility management contracts require clear scope delineation between the operator's responsibilities and the owner's. Standard contract structures divide accountability across 4 domains:

1. Civil and structural maintenance (owner)
2. Mechanical, electrical, and plumbing (MEP) systems (operator)
3. IT infrastructure operations (negotiated)
4. Regulatory compliance documentation (shared, with defined lead party per framework)

For organizations evaluating the full spectrum of infrastructure options, the data systems glossary defines key technical terms used in service agreements and procurement documents, while data services pricing and cost models covers the billing structures common to each service category. Organizations with constrained internal expertise can consult managed data services as a functionally adjacent category that extends operational support above the physical layer.

The datasystemsauthority.com reference network covers the full range of data systems service categories, from physical infrastructure through governance and analytics, structured for professional and procurement use.

References

• Uptime Institute Tier Classification System — Tier I through Tier IV facility standards for redundancy and availability
• ANSI/TIA-942 — Telecommunications Infrastructure Standard for Data Centers — ANSI/TIA joint standard for data center cabling, space, and power requirements
• NIST Special Publication 800-53 Rev. 5 — Security and Privacy Controls for Information Systems and Organizations — Physical and Environmental Protection (PE) control family
• U.S. Department of Energy — Data Center Energy Efficiency — Better Buildings Initiative energy benchmarking and PUE reporting
• GSA Multiple Award Schedule — Information Technology — Federal procurement vehicle for IT and facility management services
• California Consumer Privacy Act — Cal. Civ. Code § 1798.100 — State data privacy statute with data residency implications
• The Green Grid — PUE Metric Definition — Power Usage Effectiveness definition and methodology