Explainers
Raised Floors vs. Slab Floors: How Data Center Design Changed
For decades, data centers were built on raised floors. Many new facilities sit on concrete slab instead. Here is why the shift happened.
For decades, the image of a data center included a raised floor: square tiles set on metal pedestals a foot or more above the concrete, with perforated tiles here and there blowing cool air up into the room. Many newer facilities, especially large ones built for cloud and AI computing, have dropped the raised floor and sit directly on concrete slab. Understanding why says a lot about how data center design has evolved.
Why raised floors became standard
Raised floors date back to the mainframe era. They created a hidden space beneath the room that served several purposes at once:
- Air distribution. Cooling units pressurized the space under the floor with cool air, and perforated tiles released it where needed. Moving a tile was an easy way to redirect cooling.
- Cable routing. Power and data cables could run under the floor, out of sight and out of the way.
- Flexibility. Equipment could be rearranged without major construction.
For the computing loads of the time, this was an elegant solution.
The problems that emerged
As data centers grew and changed, raised floors revealed some drawbacks. Cables piled up underneath, blocking airflow. Abandoned cables were often left in place, making things worse. Tiles had weight limits, and heavy equipment required reinforcement. The underfloor space also had to be considered for fire detection and suppression, adding complexity.
Perhaps most important, the airflow could be hard to control precisely. Air pressure under the floor varied, so some tiles delivered more air than others, and dense racks could be starved while lighter racks were overcooled.
The move to slab
Many modern facilities place racks directly on a concrete slab. Cooling and cabling move overhead or into dedicated pathways:
- Cool air is delivered from the perimeter or from above, often into a contained aisle, or handled by in-row and rack-level cooling.
- Power runs through overhead busways that let racks plug in where needed.
- Network cables run in overhead trays, easy to inspect and change.
- Liquid cooling pipes may also run overhead, or in some designs below in trenches, depending on how operators want to manage leak risk.
Slab floors can carry heavy loads with less special engineering, which matters for dense AI racks that may weigh far more than traditional ones. They can also be faster and simpler to build.
Raised floors are not obsolete
Raised floors are still used, and they remain common in many enterprise and older colocation facilities. Some operators like them for routing liquid cooling pipes below the equipment, keeping any potential leaks away from overhead electrical systems. Others prefer them for the flexibility they offer in smaller, mixed-use rooms.
What the shift tells us
The move from raised floors to slab reflects broader trends: larger buildings, more standardized layouts, much heavier equipment, and cooling that is increasingly delivered close to the rack instead of through the room. Neither approach is universally better. Each facility chooses based on its loads, its cooling strategy and how often its equipment is expected to change.
The next time you see a photo of a data hall, glance at the floor. Tiles or concrete can tell you a surprising amount about when and how the building was designed.
Comparing the Two Approaches Side by Side
Because each floor type supports a different way of delivering air, power and cabling, the comparison is really about whole design philosophies.
- Air delivery. A raised floor distributes air through a pressurized plenum and perforated tiles. A slab design delivers air from the perimeter, from overhead, or through in-row units, often into contained aisles.
- Cable management. Raised floors hide cables below; slab designs place them overhead in trays where they can be seen, traced and changed more easily.
- Weight. Slab floors typically support heavy racks with less special engineering. Raised floors need pedestals, stringers and tiles rated for the load, and very heavy racks may require reinforcement.
- Construction. Slab designs can be simpler and quicker to build. Raised floors add materials, installation time and ongoing inspection of the underfloor space.
- Liquid piping. Raised floors offer a convenient space to run coolant pipes below equipment. Slab designs route pipes overhead or through trenches, each with its own approach to leak management.
- Flexibility. Raised floors make small layout changes easy by moving tiles. Slab designs rely on flexible overhead systems, such as busways with plug-in units, for similar adaptability.
Why overhead power busways mattered
One of the developments that made slab floors practical was the overhead busway, a continuous electrical channel running above the rows. Instead of pulling a new cable from a distant panel for each rack, technicians can plug a tap-off unit into the busway above the rack that needs power. That kind of flexibility, once a key advantage of raised floors, became available overhead.
Common Problems in Raised-Floor Halls and How Operators Address Them
Many raised-floor facilities remain in service and perform well. Where problems arise, operators have well-known fixes:
- Underfloor congestion. Removing abandoned cables and organizing remaining ones in trays restores airflow. Many operators make cable removal part of every decommissioning job.
- Uneven pressure. Adjusting the number and placement of perforated tiles, sealing cable cutouts with grommets, and closing unnecessary openings help balance airflow.
- Misplaced tiles. Perforated tiles in hot aisles or under no equipment waste cool air. Regular audits catch these.
- Bypass air. Adding aisle containment above the floor ensures cool air rising through tiles actually reaches server inlets.
- Load limits. Checking tile and pedestal ratings before installing heavier racks prevents structural problems.
Questions Readers Ask
Can a raised-floor hall host AI racks? In some cases, yes, with structural reinforcement, liquid cooling and careful planning. Very dense, heavy racks may be easier to accommodate on slab, but the answer depends on the specific building.
Do raised floors help with flooding? They lift equipment slightly above the slab, which can offer modest protection against small amounts of water, but they are not a substitute for proper site selection and flood protection.
Is one approach safer for liquid cooling? Opinions differ. Underfloor piping keeps liquid away from overhead electrical systems, while overhead piping keeps liquid visible and accessible. Good leak detection and drip protection matter in either case.
What should a reader take from a facility photo? Perforated tiles suggest a classic underfloor air design, while bare concrete with overhead busways and trays points to a newer slab design, often built for larger, more standardized deployments.
Latest stories
View allExplainers
The Commissioning Exception Log Deserves a Place Beside the Test Result
A successful test can still leave questions to resolve. Commissioning documentation is more useful when it records exceptions, temporary arrangements and unfinished actions alongside the activities that passed. Otherwise the handover can appear cleaner than the operating reality.
Photo: TECNIC Bioprocess Solutions / Unsplash
A successful test can still leave questions to resolve. Commissioning documentation is more useful when it records exceptions, temporary arrangements and unfinished actions alongside the activities that passed. Otherwise the handover can appear cleaner than the operating reality.
The operating distinction
Testing examines a defined configuration under defined conditions. A temporary sensor, bypassed sequence or unavailable component changes what that test establishes. An exception log preserves those boundaries and assigns follow-up work. It is a bridge between the construction team and the people who will run the facility.
An exception record is also a memory aid after the original project team leaves. Without it, operators can spend time rediscovering why an arrangement differs from the drawings or why a monitoring point behaves unusually. The record should preserve the reason, not only the observation.
A practical example
Imagine a hypothetical integrated test completed with one monitoring feed unavailable. The tested equipment may have performed as intended, while the missing visibility still matters for operations. Recording that distinction avoids turning a limited success into a broader claim about the complete system.
Questions worth asking
A useful exception record explains how the condition affects operation and what would resolve it. The number of open items alone cannot tell the receiving team which issues deserve attention before normal service begins.
- Which temporary conditions were present during the acceptance test?
- Who owns each remaining action and its operational consequence?
- What evidence is needed before the exception is marked closed?
What the evidence supports
An open item is not automatically a major defect, and a closed item is not automatically well resolved. The useful record explains its operational consequence, the evidence for closure and who accepted the result. That is more informative than counting entries alone.
A concise handover review can select the items that affect current operation and connect each one to its evidence. A cosmetic issue and a missing protection function should not be flattened into the same status description. Their consequences differ. Making that difference visible helps the receiving team understand what has actually been accepted and which assumptions still depend on follow-up work.
Read the conditions and unresolved work with the result, rather than treating a pass label as the whole account.
Quick check
How much did you catch? Tap a question to see the answer.
1. What does an exception log record?
Answer: Exceptions, temporary arrangements and unfinished actions.
2. Why does it matter after the project team leaves?
Answer: Operators don’t have to rediscover why something differs from the drawings.
3. What should the record keep besides the observation?
Answer: The reason.
What a Strong Exception Entry Contains
An exception log is only as useful as the individual entries in it. A short entry that says a sensor was offline tells the next reader very little. A stronger entry answers the questions an operator will ask months later when the original team is no longer on site.
- What was observed. A plain description of the condition, the equipment affected and the location.
- When and under which test. The test or activity during which the exception appeared, so the reader understands its context.
- Why it exists. The cause if known, such as a component awaiting delivery, a design change or a temporary arrangement.
- Operational consequence. What the condition means for running the facility today, including any reduced visibility or protection.
- Interim measure. Any temporary arrangement or added monitoring that compensates while the item is open.
- Owner and target. The role responsible for closing it and the expected milestone.
- Closure evidence. What will demonstrate resolution, such as a retest, a document update or a sign-off by the receiving team.
Running an Exception Review Before Handover
A handover review does not need to reopen every item. It needs to make sure the receiving team understands what they are accepting.
- Sort by consequence. Group entries by their effect on safety, protection, capacity, monitoring and appearance. Cosmetic items can be handled separately from items that affect how the facility responds to a fault.
- Confirm the interim measures. For each item that affects operation, verify that the temporary arrangement is in place and understood by operators.
- Agree on acceptance. Decide which items the receiving team accepts as open, with conditions, and which must close before service begins.
- Record who accepted what. Acceptance of an open item is itself a decision that deserves a name and a date.
- Carry the log forward. Make the log part of the operating record rather than a construction document that is archived at handover.
Common mistakes
Teams sometimes close items to reduce the count before a milestone, without strong evidence that the issue is resolved. Others merge unrelated items into one entry, which makes closure ambiguous. A third mistake is keeping the log in a format that only the commissioning party can access, so operators never see it. Finally, an exception closed by a later change can be reintroduced if the change is undone without anyone checking the history.
What This Means for Owners, Operators and Customers
For an owner, the exception log is a record of the conditions under which the facility was accepted. For an operator, it explains behavior that does not match the drawings. For a customer considering a new facility, the existence of a disciplined exception process can be a sign that the provider is willing to describe its systems honestly, including what remains unfinished. A clean summary page is reassuring only if the detail behind it supports it.
A pass result describes what was tested. The exception log describes what that result does not yet cover.
Questions Readers Ask
Is a long exception log a bad sign?
Not necessarily. A detailed log may reflect careful documentation. What matters is the consequence of the items and whether they have owners and closure plans.
Who should own the log after handover?
Usually the operating team, with clear arrangements for the construction or commissioning party to complete their remaining actions.
Can an item be closed without a retest?
Some can, such as documentation corrections. Items that affect system performance generally need evidence that matches the original concern.
How long should exception records be kept?
Long enough to explain the facility’s configuration to future operators, which often means keeping them with the permanent operating records.
AI infrastructure explainers and news on iPhone, iPad and Apple Watch.
Explainers
What Is a Hyperscaler? A Plain-English Explainer
The word shows up in nearly every story about AI infrastructure. Here is what it means and why these companies shape the build-out.
“Hyperscaler” is industry shorthand for the small group of companies that run cloud computing at enormous scale: they own and operate fleets of data centers around the world and rent computing power, storage and software to everyone else. Amazon Web Services, Microsoft Azure and Google Cloud are the names most people know, and Meta and Oracle are often included in the same conversation. If you follow business news for even a week, you will see the word attached to earnings reports, power deals, chip orders and real estate announcements. This explainer walks through what the term really means, why it carries so much weight, and how to read the signals these companies send.
What Makes a Company a Hyperscaler
There is no official membership list and no regulator that hands out the title. The word describes a business model and a size. A hyperscaler does three things at once: it builds and owns the physical infrastructure (land, buildings, power connections, cooling and servers), it runs that infrastructure as a global network, and it sells access to it as a service. Customers range from a two-person startup renting a single virtual server to a multinational bank moving its entire back office into the cloud.
The “hyper” part refers to the ability to scale up very quickly. A customer can ask for more computing capacity in the morning and have it running by lunch, because the hyperscaler has already built far more capacity than any single customer needs. That spare capacity, spread across many customers, is the heart of the business.
It helps to separate a few related ideas:
- Cloud providers rent computing resources over the internet. All hyperscalers are cloud providers, but not every cloud provider is large enough to be called a hyperscaler.
- Colocation and data center operators own buildings and rent space, power and cooling to companies that bring their own servers. They are often suppliers to, or landlords for, the hyperscalers.
- Large platform companies such as Meta run hyperscale infrastructure mainly for their own apps and services, which is why they are often grouped with the cloud giants even though they rent less of it to outside customers.
Why the Label Matters
Scale changes the economics. A company building dozens of data centers can design its own servers, negotiate long-term power contracts directly with utilities, and order chips years in advance. That buying power is why hyperscaler spending plans are watched so closely: when they raise or cut capital budgets, suppliers of chips, networking gear, cooling systems and electrical equipment feel it.
Think of it like a very large customer at a small supplier. When one buyer accounts for a meaningful share of a supplier’s orders, that buyer’s plans become the supplier’s forecast. Hyperscalers sit in that position for many industries at once. A single decision to accelerate or delay a group of data center projects can ripple through:
- Semiconductor makers that design and manufacture processors and accelerators
- Networking companies that sell switches, optical connections and cabling
- Makers of cooling equipment, from chillers to liquid cooling hardware
- Electrical equipment firms that supply transformers, switchgear and backup power
- Construction and engineering firms that design and build the facilities
- Utilities and power developers that supply the electricity
Because of this, analysts often treat hyperscaler budgets as a leading indicator. Spending plans are announced before the money flows to suppliers, so a change in guidance can show up in supplier results a quarter or more later.
Where AI Fits In
Training and running large AI models takes far more computing power than traditional web services. Hyperscalers are the main buyers of AI accelerators and the main builders of the facilities that house them, so much of the AI build-out flows through their budgets.
Two kinds of AI work drive that demand. Training is the process of building a model by running enormous amounts of data through specialized chips for weeks or months. Inference is the everyday use of a finished model, every time someone asks a question or a business runs an automated task. Training tends to come in large, concentrated bursts; inference grows as more people and companies use AI tools. Both need dense, power-hungry hardware, and both push data center design toward higher power per rack and more advanced cooling.
This is why the AI story and the hyperscaler story are so closely linked. Most companies that use AI do not buy their own accelerators. They rent them from a cloud provider. The hyperscalers, in turn, place the large orders, sign the power contracts and pour the concrete.
What to Watch
Three things tell you the most: capital expenditure guidance in quarterly earnings, announcements of new data center campuses and the power deals behind them, and any comments about how much of their capacity is already spoken for by customers.
1. Capital expenditure guidance
Capital expenditure, or capex, is money spent on long-lived assets such as buildings, servers and equipment. Hyperscalers usually discuss their capex plans on quarterly earnings calls. Listen for whether guidance is going up, holding steady or coming down, and for how management describes the mix between buildings, servers and chips. A raised outlook generally signals more orders ahead for suppliers; a cut signals the opposite.
2. New campuses and power deals
A data center campus can only run if it has electricity. Announcements of new sites often come paired with agreements to buy power from a utility or a new generation project. These deals reveal where capacity is being built, how quickly, and how much power the companies expect to need. Delays in grid connections can slow projects even when the money is ready.
3. Capacity already spoken for
Pay attention when executives describe customer commitments, backlogs or capacity constraints. If a company says demand is running ahead of available capacity, it suggests continued building. If it says customers are optimizing or pausing, the build-out may cool.
Common Misreadings to Avoid
- Treating all hyperscalers as one. Each has its own customers, chip strategy and balance sheet. A spending increase at one does not guarantee the same at another.
- Confusing announcements with spending. A campus announced today may take years to build and fill. Watch for progress, not just headlines.
- Ignoring power. Chips get attention, but electricity and grid access are often the real bottleneck.
- Assuming a straight line. Capital spending cycles can speed up and slow down. Suppliers can see sharp swings when hyperscalers change pace.
The Starting Point for the AI Supply Chain
Understanding the hyperscalers is the starting point for understanding nearly every other company in the AI supply chain. Once you know who is buying, how much they plan to spend and what is holding them back, the news about chips, cooling, networking and power starts to fit together into a single picture.
A simple way to keep learning this week:
- Pick one hyperscaler and read the capex section of its most recent earnings summary.
- Note one data center campus announcement and look for the power arrangement behind it.
- Write down one supplier category (chips, cooling, networking or electrical) and follow how its news connects back to hyperscaler budgets.
BOSSTOX publishes educational content, not investment advice. For decisions about your own money, talk with a qualified financial professional.
Explainers
NVIDIA’s Modular AI Factories Put the Clock on Infrastructure
AP reports that NVIDIA is urging Europe to accelerate AI infrastructure. BOSSTOX examines what modular AI factories could change—and what constraints remain.
The AI infrastructure race is shifting from “who has the chips?” to “who can get a working factory online?” The Associated Press reports that NVIDIA CEO Jensen Huang used the company’s Berlin developer conference to urge Europe’s AI sector to move faster, while presenting tools intended to help accelerate data-center construction.
The most consequential piece is infrastructure, not marketing language. NVIDIA says its new DSX POD reference design packages computing, networking, rack-level power and liquid cooling into modular units that can be integrated and tested before arriving at a prepared site. The company says deployment at a ready location could fall from roughly six months to as little as 14 days.
Why the schedule matters
AI capacity is constrained by more than GPU supply. Operators still need power, interconnection, cooling, fiber, permitting, specialized labor and a site that can accept a dense load. A modular approach does not remove those constraints, but it changes where the work happens: more integration moves into a factory, while the site becomes a connection and commissioning problem.
That distinction matters for developers, utilities and investors. A project that reaches “first tokens” weeks earlier can begin serving customers sooner, but only if the supporting infrastructure is actually ready. A container full of compute does not create capacity without electricity, thermal management, network access and a reliable operating model.
What NVIDIA is claiming
NVIDIA says DSX POD is designed for Vera Rubin AI factories and is being developed with partners including Bull, Dell Technologies, HPE, Lenovo, Schneider Electric and Vertiv. The company also says partners are working toward global deliveries in early 2027. Those are vendor announcements, not independent measurements, and the real test will be how quickly a prepared site can move from delivery to production under local grid, permitting and operating conditions.
What to watch next
- Power access: whether sites have firm capacity and a realistic interconnection path.
- Cooling: whether closed-loop liquid systems reduce water use without creating new maintenance bottlenecks.
- Deployment evidence: whether the promised weeks-long schedule holds outside demonstration environments.
- Revenue timing: whether faster installation translates into paid inference and training workloads.
BOSSTOX tracks the physical and financial systems behind AI: power and grid access, cooling, custom silicon, optical networking, data-center capacity, and capital. The NVIDIA announcement is a useful signal because it connects several of those lanes at once. The strategic question is no longer simply how many accelerators a region can buy. It is how quickly that region can turn electricity, equipment and sites into dependable compute that customers can use.
Sources
Read the Associated Press report and review NVIDIA’s DSX POD announcement. For related infrastructure context, visit BOSSTOX.
This BOSSTOX analysis is original and distinguishes reported facts from company claims and editorial interpretation.
Going Deeper: What “Factory-Integrated” Means for a Data Center Project
The idea behind modular AI infrastructure is not new in construction. Builders have long moved work off site when it can be done faster, more safely or with better quality control in a factory. Applied to dense computing, the logic looks like this as of late October 2026.
The traditional sequence
In a conventional deployment, servers, networking gear, power distribution and cooling components arrive at a site separately. Crews install racks, run cables, connect cooling loops, energize equipment and then test everything together. Problems discovered during testing must be fixed on site, where specialists may be scarce and every day of delay is a day without revenue.
The modular sequence
In a modular approach, much of that integration and testing happens before shipment. The site’s job shifts toward preparing a foundation, power feeds, cooling connections and network links that the arriving units can plug into. The promise is that commissioning becomes a shorter, more repeatable process. The risk is that any mismatch between what the factory built and what the site prepared can still cause delays.
A Checklist for Evaluating Speed Claims
When any vendor describes a dramatically shorter deployment timeline, a few questions help put the claim in context.
- What counts as the start? A schedule measured from delivery to a prepared site excludes the time needed to secure land, permits, power and cooling infrastructure, which can take far longer.
- What counts as the finish? “First tokens” or initial operation is not the same as full production with all units running reliably for paying customers.
- How many sites have done it? A timeline achieved once in a controlled setting may differ from results across many locations with different local conditions.
- Who did the measuring? Vendor-reported figures are useful but are not the same as independent results.
- What happens when something fails? Servicing and replacing components in tightly integrated units may require specialized support.
Why This Matters for Reading Financial Results
Faster deployment, if it holds up, can affect several numbers that BOSSTOX readers follow:
- Construction in progress. Equipment that moves from delivery to service more quickly spends less time as unfinished assets on the balance sheet.
- Depreciation timing. Assets placed in service sooner begin depreciating sooner, which is offset, ideally, by earlier revenue.
- Revenue timing. For cloud and AI service providers, shorter gaps between capital spending and paid workloads can improve the return on that spending.
- Supplier mix. Modular designs may shift more value toward partners that integrate power and cooling at the factory, a theme to watch in supplier commentary.
Questions Readers Ask
Does modular design solve the power problem? No. As the analysis above notes, a module still needs firm electricity, interconnection and heat rejection at the site. Those remain the long-lead items.
Is a modular unit the same as a shipping-container data center? The concepts are related, since both move integration off site, but modern AI designs are built around far denser power and liquid cooling than earlier containerized approaches.
Why would partners in power and cooling be involved? Because the limiting factors for dense AI racks are increasingly electrical and thermal. A design that integrates compute without matching power distribution and liquid cooling would simply move the bottleneck. Including those suppliers in a reference design reflects how tightly the layers now depend on each other.
What should site developers take from this? If deployment of the compute itself becomes faster, the relative importance of having power, cooling and permits ready in advance grows. Sites that are genuinely prepared may become more valuable.
What evidence would confirm the claims? Repeated, documented deployments at customer sites, along with operator comments on how long it took to reach reliable production. Those reports, rather than launch-day announcements, will show whether the timeline holds. This analysis is general education and not investment advice.
-
Power & Grid1 month agoTransformer Lead Times Are Becoming a Data-Center Schedule Risk
-
Power & Grid1 month agoGas Turbines on Data-Center Campuses
-
Cooling2 months agoWater Use and Dry Coolers: The Tradeoff AI Sites Cannot Avoid
-
Power & Grid1 month agoBattery Storage at AI Sites
-
Compute & Silicon1 month agoGPU Supply Chains: How AI Hardware Gets Made, Moved, and Bottlenecked
-
Power & Grid4 weeks agoFERC’s Large-Load Orders: The November 16 Grid Deadline Behind the AI Build-Out
-
Capital & Backlog4 weeks agoAI Infrastructure’s Rough Week: Chips Fall 6.7% as Meta Lifts Capex Floor
-
Cooling4 weeks agoLiquid-Cooling Leak Detection and Reliability
