Cabling, cameras and phones that stay up, because someone is watching them.

How we solve it

1. Map who needs whatProduction, ticketing and point-of-sale, press, vendors and guests each have different needs. We list them and decide what must never share a network.
2. Plan pathways, switching and addressingCable routes, switch locations, IP plan and uplinks, agreed with the other trades before load-in.
3. Build and testLabeled drops, tested uplinks and a port schedule that matches what’s on site.
4. Support the showTechnicians on site with an escalation list, and every change recorded.
5. Strike in an orderly wayEquipment is recovered against the asset list, with nothing left in a ceiling.

Want it watched live during the show? See Managed event operations.

How we solve it

1. Run readiness checksBefore the event we verify uplinks, switching, cameras and key systems against the plan.
2. Set roles and escalationWho is on call, who decides, and who gets called for what.
3. Oversee the network liveMonitoring and troubleshooting coordination during the event, with every change tracked.
4. Hand off between shiftsWritten handoffs so nothing is lost when people rotate.

How we solve it

1. Survey the routesWalk pathways with facilities and production staff to find what’s usable, what’s reserved and what’s a hazard.
2. Plan distributionFiber backbone, intermediate distribution points and endpoint locations laid out as one system.
3. Set one labeling standardEvery trade uses the same scheme, so any run can be traced from either end.
4. Verify each handoffTest and sign off each link before another team depends on it.

Photo: Wikimedia Commons contributor · CC licensed

How we solve it

1. Understand the workflowWho sits where, what they watch and what must keep working if one thing fails.
2. Lay out the roomWorkstations, displays, phones and equipment placed for sightlines and serviceability.
3. Cable and labelStructured cabling to every position, labeled at both ends.
4. Write the support stepsA short guide for what to check first when something stops working.

Photo: MTA Capital Construction · CC BY 2.0

How we solve it

1. Plan counts and routesStrand counts with spares, pathways, termination points and patching, designed for growth.
2. Install and terminateCable pulled with proper bend radius, terminated and protected in enclosures.
3. Test each linkLoss testing to the project requirement, with results kept for every strand.
4. Label and documentStrand schedules and endpoint labels that match the drawings.

Photo: ProjectManhattan · CC BY-SA

How we solve it

1. Plan the routes and outletsOutlet counts and locations for desks, Wi-Fi, cameras and phones, with room to grow.
2. Install and terminateCable run within length limits, terminated to a consistent standard at both ends.
3. Label everythingEach cable, outlet and patch-panel port gets a matching identifier.
4. Test every linkCertified or verified test results against the project requirement.

How we solve it

1. Plan the roomRack elevations, patch panels, switch positions, power and cooling, and room to work around the gear.
2. Build it neatlyCable management that survives a change, with serviceable access.
3. Document the layoutPatching and equipment location records that stay current.

How we solve it

1. Compare the optionsDistance, conduit availability, line of sight and budget, laid out for fiber versus wireless.
2. Add resilienceA second path or a wireless backup for the links that matter.
3. Install and measureThroughput tested and segmentation boundaries documented.

How we solve it

1. Define what it must doUsers, devices, applications, growth and downtime tolerance.
2. Design the coreSwitching, routing, VLANs, uplinks and wireless, sized for the load.
3. Plan Wi-Fi for capacityAccess-point placement, authentication and traffic separation, checked with a survey.
4. Install and acceptVerify core connectivity and wireless coverage against the agreed criteria.

How we solve it

1. Plan the network sidePoE, voice VLANs and quality-of-service for calls.
2. Map call flowsWho answers, where calls ring and what happens after hours, documented with the voice platform.
3. Deploy and testHandsets installed, inventoried and call workflows tested.

How we solve it

1. Define the goalIdentify, detect or just observe each area, which sets placement and resolution.
2. Plan power and dataCable routes, PoE switches and storage sized for the retention period.
3. Set permissionsAuthorized users only, with secure remote viewing.
4. Verify the viewsDay and night image checks before sign-off.

Photo: Wikimedia Commons contributor · CC licensed

How we solve it

1. Map doors and usersWhich doors, which people or groups, and when.
2. Coordinate hardwareReaders, controllers, locks and intercoms, with network and power requirements, working with the door and fire contractors.
3. Set up access rulesSchedules and groups, with a simple process for adding and removing people.
4. Train the administratorHandoff for whoever manages access day to day.

How we solve it

1. Verify the physical layerCopper and fiber test results on every link.
2. Verify the servicesDevice reachability, service paths and failover against acceptance criteria.
3. Capture the as-builtPort maps, cable schedules and rack records that match what’s actually installed.
4. Close the punch listOpen issues listed, fixed and signed off before handover.

How we solve it

1. Agree the sequencePathways, materials and who does what, in what order.
2. Track the detailsLabeling conventions, issue lists and progress visible to everyone.
3. Control the cutoverChanges made in agreed maintenance windows, with a way back.
4. Hand over cleanlyMilestones signed off and records delivered.

How we solve it

1. Decide what to watchNetwork devices, uplinks, cameras, phone systems and door controllers that the cabling serves.
2. Set meaningful alertsThresholds tuned so the right problems reach a person and noise does not.
3. Route by severityUrgent issues go to someone now, routine ones to a daily or weekly review.
4. Report regularlyA periodic health summary with trends and recommendations.

How we solve it

1. Define what is supportedSites, devices and systems in scope, and what is out of scope.
2. Set up intake and prioritiesHow issues are reported and what makes one urgent.
3. Troubleshoot remotely firstMost connectivity problems are solved without a visit.
4. Visit when it mattersScheduled and urgent on-site visits for repairs, replacements and changes in agreed windows.

How we solve it

1. Build the registerEquipment, locations, serial numbers and warranty dates in one list.
2. Back up configurationsCurrent backups and a change record for supported devices.
3. Plan the lifecycleFirmware updates and replacement priorities scheduled before they become emergencies.