Small-business network refresh: the inventory-to-BOM handoff
Turn a site inventory into an equipment list an installer can accept: port assignments, power assumptions, complete uplinks, named owners and a controlled substitution record.
By Uniqcli Team · · 5 min read
Key takeaways
- Give every required connection an inventory row and every ordered part a requirement it satisfies.
- Separate endpoint count, per-port PoE capability and the switch-wide power budget.
- Record substitutions against the approved design and accept the installed network against the same worksheet.
On this page
Start with the handoff the next team needs
A network refresh can quickly become complicated when the site inventory, supplier quote and installation plan don't match. The easiest way to keep everyone aligned is to use one shared requirements list that tracks each connection, from the equipment needed to the port where it's installed.
Start by assigning a site owner and a technical owner. The site owner confirms where employees work, when installation can take place and which business operations need to stay running. The technical owner handles network requirements such as IP addressing, security and management. Procurement tracks equipment orders, delivery dates and any issues. One person can handle multiple roles, but every important decision should have a clear owner and date.
Before selecting new equipment, document what's already in place. Include work areas, wired devices, wireless connections, important applications, existing cable labels and the internet or upstream network connection. If something hasn't been checked, such as a cable or ceiling installation location, add it to the site survey checklist with a deadline instead of making assumptions.
Copy these fields into the requirement register
- Requirement ID and location
- A stable identifier, room or rack, endpoint purpose, quantity and the person who confirmed the count.
- Connection and power
- Required access speed, copper or fiber, PoE standard and mode, documented switch-side power allocation, or local power requirement.
- Physical evidence
- Cable label and test status, measured route, mounting position, cabinet space, environmental restrictions and installation access.
- Approved implementation
- Switch and port assignment, complete uplink endpoints, proposed manufacturer part numbers, required software/support and evidence links.
- Delivery and acceptance
- Order line, planned arrival, staging result, installed serial number, acceptance check, owner and unresolved exception.
Keep credentials and sensitive configurations in the approved management system. The shared procurement register should reference those records without exposing secrets.
Make the assumptions visible before calculating quantities
Consider a hypothetical branch with 18 wired computers, four access points, six phones and two printers. Assume each needs a separate switch port, all access links use copper, and the design reserves dedicated uplink interfaces. That gives 30 occupied access ports. A locally chosen 20% expansion allowance adds six, producing a planning requirement of 36 access ports. The allowance is an example policy, not an industry requirement.
The phone assumption matters: a validated phone passthrough arrangement could change the count, while cameras or building devices omitted from the walk-through could increase it. A 48-port model may satisfy the arithmetic, but port speed, uplink layout, management and power still need checking. Use the existing Cisco and Aruba switch selection guide for those model-selection questions.
For a separate illustrative power calculation, assume documented switch-side allocations of 30 W for each AP and 10 W for each phone. Four times 30 plus six times 10 equals 180 W. If the project chooses 25% reserve, its target is 225 W. These are assumed allocations, not measured device consumption. Replace them with the exact device and switch requirements before ordering. Cisco’s Catalyst 1200 data sheet lists per-port capability separately from each model’s total PoE budget; both constraints must be satisfied.
Close each connection at both ends
Give each uplink its own row. Record the two device models, selected ports, required speed, transceiver or cable part numbers, fiber type and measured path. Attach the manufacturer evidence used to approve the combination. Cisco’s optics guidance distinguishes optics-to-device support from optics-to-optics interoperability. A matching connector alone does not settle either question.
For wireless, the handoff should identify the design’s evidence and the acceptance method. A count based on floor area can help establish a budget, but it does not demonstrate coverage for the actual clients and applications. Cisco distinguishes predictive planning from measured surveys and describes post-deployment validation. Record who will perform that work and which rooms, client types and applications must be checked.
Add the unglamorous dependencies to the same register: mounting hardware, patch leads, cable labels, management access, licenses, support entitlement and power availability. Specify whether each is supplied by the equipment vendor, installer or customer. A line marked customer supplied still needs a named owner and a ready-by date.
Treat a substitute as a design change
When a quoted item changes, preserve the original requirement ID and add a dated comparison. Ask whether the substitute changes power budget, supported optics, software features, mounting, licenses or the installation sequence. The technical owner approves the relevant differences before procurement releases the changed order.
Split delivery status from installation readiness. A switch can be physically present while its mounting kit, license or uplink remains missing. Track one readiness decision for the installation group, with explicit outstanding dependencies. Keep the prior configuration and equipment available according to the approved change plan until acceptance is complete.
Accept the installed network against the register
- Confirm delivered model numbers, accessories and entitlements against the approved revision; record any substitution before installation.
- Stage the agreed software and management configuration, and verify access using the organization’s authorized administration process.
- Match installed ports and cable labels to the endpoint register; investigate unused or unexpected connections.
- Check negotiated link speed and PoE operation with the intended devices active, and record the switch’s reported allocation and remaining budget.
- Validate wireless service and representative business tasks in the agreed locations; retain results with the requirement IDs.
- Have the technical and site owners accept the result, list remaining exceptions, and transfer the port map and support details to operations.
Frequently asked questions
Can the supplier build the BOM from a floor plan?
A floor plan can support an initial proposal. It still needs endpoint counts, cable and power evidence, application requirements and an agreed survey scope. Label an early BOM as provisional so it is not mistaken for an accepted design.
Does spare port count cover future growth?
Only one part of it. Added endpoints can also consume PoE budget, uplink capacity, licenses and physical space. Record the intended growth scenario and review each affected constraint.
What belongs in the final handoff?
The approved requirement register, as-installed port map, equipment and entitlement records, acceptance results, support ownership and open exceptions. Include references to secured configuration backups rather than placing credentials in the shared worksheet.
Build the equipment list around the approved requirements
Use the completed register to compare switches and identify the accessories and review work needed for the site. Preserve its requirement IDs in the quote.