Look, I'm an office administrator for a mid-sized company—about 200 employees across two locations. I'm the person who handles the phone system, the printers, the coffee machine, and yeah, when IT says they need a new network cabinet, they come to me. And when they say 'we need an enclosure for the new server gear,' my first thought wasn't 'great, a rittal panel cooler question I can answer.' It was more like 'great, another thing I'm going to screw up if I'm not careful.'
If you're in a similar spot—someone who manages purchasing for IT, facilities, or operations, and you're staring down a network cabinet order for the first time—this checklist is for you. I've been through this maybe 4 or 5 times now in the last 3 years, and I've made enough mistakes to have a pretty good idea of what to watch for. Let me save you some of those headaches.
Step 1: Figure Out What's Actually Going Inside (And How Much Space They Need)
This sounds obvious, but you'd be surprised how often people skip it. When our IT team asked for a new cabinet, they just said 'something standard.' I said 'standard how?' We ended up with a 42U rack when we only needed 18U. We had to eat the return shipping.
Here's what I've learned to ask now:
- Count the units: How many servers, switches, patch panels, and other gear. Each one takes up 'U's (rack units). 1U is 1.75 inches. Add it all up.
- Leave room for growth: We usually add 20-30% on top of the current count. That way, when they add a new switch next year, you're not out buying another cabinet.
- Check depth requirements: This is the one I missed the first time. Some switches are deeper than others. Make sure the cabinet depth (standard is 600mm or 800mm, but it varies) can handle the deepest piece of gear you're putting in.
I now keep a simple spreadsheet for this. I ask our IT lead to list every item with its U height and depth. It takes 10 minutes and saves a lot of hassle. (Note to self: I really should turn that into a template for the whole company.)
Step 2: Think About Cooling—Before You Order
Everything I'd read about rack cooling said 'just make sure there's airflow.' In practice, for our server room that doesn't have dedicated HVAC, that advice was almost useless. The conventional wisdom is that a standard fan panel is enough. My experience with a 24U rack full of active gear? It got hot enough to cause an intermittent failure on a switch. That cost us a morning of downtime and a very unhappy VP.
Here's what I check now:
- Heat load: Ask IT to estimate the total heat output in BTUs or watts. For a basic rule of thumb, a typical switch might be 50-100W. A small server could be 200-500W. Add it up.
- If it's over 1000W of heat in a small room, you're probably going to need more than just vents. That's where a rittal panel cooler or a dedicated cooling unit for the rack comes in. It's a mounted air conditioner for the cabinet, basically.
- Check the room: Is the cabinet in a climate-controlled server room, or a warm-ish storage closet? That makes a huge difference. Our second cabinet went into a storage closet. It would have fried without the active cooling.
I asked our IT guy, 'Do we need a cooling unit?' He said 'probably not.' I got quotes anyway, and for the specific room we were using, the rittal panel cooler quote was surprisingly affordable compared to the cost of a fried switch. We installed it. No issues since. (Maybe I'm over-recommending cooling now, but I'd rather over-cool than under-cool and have to explain a failure.)
Step 3: Don't Forget the Power and Cable Management
This one is about vendor coordination. When I ordered our first cabinet, I just bought the box itself. I didn't order the power strips or the cable management arms. I assumed they came with it. They do if you order a 'bundle.' If you order a bare cabinet, they don't.
I said 'standard cabinet.' The vendor heard 'empty box.' Result: two-day shipping for PDU (power distribution units) and vertical cable management panels. Cost us an extra $120 in expedited fees. I ate that out of my department budget—no, wait, I got it approved, but it was annoying.
Checklist for this step:
- PDU (power strip): How many outlets? Do you need a basic strip or a switched one you can control remotely? Our IT team needed the latter for rebooting devices.
- Cable management: Horizontal or vertical? Brush panels or finger duct? I've found that having vertical cable managers on both sides of the rack makes the cabling techs much happier. A happy tech is a fast tech.
- Grounding kit: Especially for network gear. Make sure the rack has a proper ground point. Our electrician pointed this out after the cabinet was installed. We had to add a grounding bar later.
Step 4: Verify the Vendor's Ordering Process (Trust Me on This)
This is the step nobody talks about but is essential for an admin buyer. After 5 years of managing these vendor relationships, I've come to believe that the 'best' vendor quote means nothing if they can't execute on the order and invoicing properly.
What I check now:
- Lead times: When I ordered a rittal cabinet from a specific distributor, the online system said 'in stock.' It wasn't. It was a 3-week lead time. I had to call three different suppliers to find one that had it on the floor. Now I ask for confirmed stock before I place a PO.
- Invoicing process: Do they provide a standard invoice (the kind my accounting system can read), or do they send a handwritten receipt? I had a vendor once—not for a cabinet, but for office supplies—who couldn't provide proper invoicing. It cost our accounting team $2,400 in rejected expense reports and two hours of my time sorting it out. Now I verify invoicing capability before placing any order over $500.
- RMA policy: If it arrives damaged or it's the wrong size, can you return it easily? Get this in writing.
Step 5: Plan the Delivery and Installation
A network cabinet is big. It's heavy. Our first one arrived on a pallet, and the delivery driver left it on the loading dock. I had to call our facilities team to move it. They weren't happy. It took three people and a dolly to get it to the server room. (We counted it as a team-building exercise.)
Checklist:
- Delivery location: Can the delivery truck get close to the door? Do you have a loading dock? Make sure the receiving area knows it's coming on a pallet.
- Path to the installation room: Measure doorways and hallways. A standard 600mm-wide cabinet should fit through a standard door, but an 800mm one might not. We measured. I'm glad we did. We had to take a door off its hinges for the 800mm one.
- Installation help: The vendor may offer installation services. For our second cabinet, we paid a local IT contractor $200 to rack it, install the power, and cable it. Money well spent. Took them 3 hours. Would have taken me 6 and it would have looked sloppy.
Step 6: Document Everything (The Boring but Essential Step)
This is the step I'm bad at. We've been meaning to document our network cabinet setup for two years. I really should do that. But here's what I've learned matters:
- Plan of record: A simple diagram of what's in each U slot. It doesn't need to be fancy. A marked-up photo works.
- Serial numbers and warranty info: Keep a copy of the purchase order and the serial numbers for the cabinet and the cooling unit. If a rittal panel cooler fails under warranty, you'll need that.
- Vendor contacts: Who did you talk to for the order? Who handles service? Write it down. I keep a simple Google Doc. It's saved me hours when we needed a replacement fan for a cooling unit 18 months later.
Common Mistakes I've Seen (And Made)
Mistake #1: Buying the cheapest cabinet from an unknown vendor. The savings aren't worth it if it's flimsy, doesn't have proper ground points, or the doors don't align. We ordered a generic one once. The door didn't close flush. We sent it back. The restocking fee was painful.
Mistake #2: Ignoring the cooling until it's too late. I've covered this, but it's worth repeating. If your room is above 80°F (27°C), get a quote for a rittal panel cooler or a similar unit. Get a quote even if you think you don't need it. It's better to have the information than to be caught off guard.
Mistake #3: Assuming the IT team has already specified everything. They often assume you know the technical details. You don't. That's why the checklist exists. Ask the questions. You'll look more competent, not less.
Mistake #4: Not checking the vendor's stock. I said this before, but it's the single biggest cause of delays I've seen. Confirm lead times before you place the order. A 3-week delay on a cabinet means a 3-week delay on the entire project.
Per industry standards for equipment reliability: ambient temperature for most network gear should be maintained between 68°F and 77°F (20°C to 25°C). If your rack environment exceeds this, active cooling is recommended.
In summary: plan the sizing, plan the cooling, don't forget the accessories, verify your vendor's processes, coordinate delivery, and document the setup. It's not exciting, but it keeps the gear running and keeps the VP off your back.
