At Bell Mobility, a new service used to mean another rack.
Not just another cabinet. More power bars, fiber cables, and installation work.
But what if the space and connections they needed were already there?
That was the opportunity Bell Mobility’s infrastructure team uncovered with netTerrain. Instead of automatically expanding, the team could look at existing rack capacity, see which equipment belonged where, and find available fiber ports before deciding what to install next.
In Bell’s published customer interview, Power & Space Manager Marc-André Demers estimated that adding a new fiber panel with 24 fiber cables could cost approximately $30,000 in their environment.
Being able to use existing infrastructure instead of automatically adding more can make a substantial difference.
And that’s really what a good network rack diagram should help you do: make the right decision before anyone starts installing equipment.
Read Bell Mobility’s netTerrain story →
Could You Make That Decision With Your Current Rack Documentation?
Imagine a new switch is arriving tomorrow.
Your rack diagram shows six empty units. The switch needs four. Looks straightforward.
Then someone asks which PDU outlet it will use. Which ports are available? Where does the patch-panel connection go?
Now the answer is somewhere between an equipment spreadsheet, an old diagram, and the person who handled the last installation.
Maybe somebody has to walk into the equipment room just to confirm what should already be documented.
The rack may have room. The team just doesn’t have enough information to approve the work.
That’s the difference between a rack diagram that shows equipment and one that helps people work.
Four Things a Network Rack Diagram Should Help You Answer
- Will the equipment actually fit? Look beyond empty rack units. Check mounting depth, clearance, weight, reserved space, and what is already installed.
- Is the power available? Which PDU outlets and feeds will support the equipment? What do your power and load records show?
- Where will it connect? Which switch ports, patch panels, cables, and documented circuit paths are involved?
- Can someone else follow the record? Could the next technician understand the equipment, ownership, connections, and recent changes without tracking down the person who installed everything?
If those answers are scattered across multiple files and systems, even a simple equipment change can become a small investigation.
With netTerrain, rack diagrams are part of a larger visual infrastructure record. Teams can work with floor plans, equipment, capacity information, ports, cabling, circuits, and related network documentation instead of treating each as an isolated picture.
See the Rack-Planning Workflow in netTerrain →
Start With the Rack. See What’s Really There.
One of the useful things about netTerrain is that you can move from a room or floor-plan view into the individual racks and equipment that matter to the job.
For example, here’s an actual netTerrain demonstration rack with front and back views.
Front and back network rack views in netTerrain. Click to enlarge.
You can see where the equipment sits, which positions are occupied, and where additional equipment might go.
But you don’t have to stop at the drawing. netTerrain can also maintain information about the devices, their owners, the connections, and the capacity data your team needs to make installation and change decisions.
For many IT teams, that means less time piecing together answers from separate records.
When the Equipment Fits, You Still Need to Know What’s Connected
There’s another question I hear frequently when talking with IT teams about network documentation: can netTerrain discover all the ports and physical connections inside a rack?
If we had a telepathy protocol, that would certainly make life easier.
In practice, network discovery can identify supported devices and help populate network records. Passive patch panels and physical cable connections still need accurate source data or documentation.
That’s why combining discovery with rack, port, and cable and circuit management matters.
Patch-panel ports in netTerrain’s demonstration environment.
With properly documented connections, teams can follow a cable or circuit path instead of trying to reconstruct it when something changes or goes wrong.
And when the person making the next change isn’t the one who installed the original equipment, that information becomes even more valuable.
Rack Space Is Only Part of the Capacity Question
An empty position doesn’t necessarily mean the rack can support another device.
Power requirements, available outlets, existing loads, and redundancy may all affect the decision.
netTerrain helps teams document power equipment and relationships alongside the devices and racks they support. Depending on the data and monitoring integrations configured, teams can also work with additional capacity and operational information.
Server and power-distribution equipment in a sample netTerrain rack.
The point isn’t that a diagram can automatically approve an installation. It’s that accurate, connected records can give the team the information needed to make that decision with fewer unknowns.
What If You Already Have Spreadsheets, Visio, or a CMDB?
You probably do. Most IT teams have accumulated documentation in several places over time.
And those tools can still serve a purpose.
The challenge comes when someone needs an answer that crosses them all: where is the equipment, what is it connected to, how much capacity is available, and what changes if we move it?
netTerrain can bring supported information from discovery, existing records, and external systems into a connected visual infrastructure environment.
You don’t have to start by documenting every rack in every building to evaluate whether it’s useful.
Start with one rack. One proposed installation. One question your team currently finds difficult to answer.
So, Can You Approve the Next Installation?
Back to that new switch.
You’ve found the rack. You can see the equipment already installed. You can check the recorded capacity information and follow the documented connections.
And if something is missing, you know what still needs verification before the work begins.
That’s the outcome worth looking for in network rack documentation.
It’s also why Bell Mobility’s experience is so compelling. The team wasn’t simply looking for nicer rack diagrams. They were able to use the information in netTerrain to make better decisions about infrastructure they already owned.
Before your next installation, see whether netTerrain can help your team answer the same questions.
Request a netTerrain Rack & Connection Demo →
Want to see a specific workflow? Mention rack capacity, equipment changes, or connection tracing in the optional needs field.
Images show an illustrative netTerrain demonstration environment, not Bell Mobility’s infrastructure. Available capabilities and data depend on the netTerrain configuration and source records used.
