CableOS

Why contractors use CableOS

Structured cabling installs in data centers run on spreadsheet pull sheets, paper termination sheets, and weekly meetings to reconstruct production status. Certification test results live in a tester's proprietary software on a separate laptop. The closeout package gets assembled by hand from three different silos the week before turnover — and something is always missing.

CableOS closes that gap:

• Real-time field capture — techs mark runs Pulled, Terminated, and Tested from their phone, with as-built lengths and photos, eliminating the daily re-keying of paper into a spreadsheet
• Live production board — the foreman's kanban updates the moment a tech taps a status; no more morning stand-up to find out where yesterday ended
• Test reconciliation — import certification test results; CableOS matches cable IDs, records Pass / Pass* / Fail with worst-case margin, auto-advances status, and computes first-pass yield
• Gated acceptance — a run can only reach Accepted after it has a passing test result; the PM is the sole authority to accept, so the closeout count is always trustworthy
• Owner readiness gate — the exec dashboard shows the six % gates (Pulled / Terminated / Tested / Passed / Accepted / open punch) that a commissioning authority needs to authorize turnover

The status lifecycle

Every cable run moves through nine discrete states, each timestamped and attributed to the actor who made the change:

Planned → Piped → Pulled → Terminated-From → Terminated-To → Tested → Passed → Accepted

A failed test routes to Failed-Rework, auto-creates a punch item, and re-enters the queue at Tested on retest. No status can be skipped; the PM's Accept gate enforces that a passing test result must exist before a run counts as complete.

What's in each app

| App | Audience | Key screens | |-----|----------|-------------| | Field Tech | Cable technicians | My Runs (by status), Run Detail (advance status, as-built length, photo, flag issue), My Day (daily log) | | Foreman | Foremen / leads | Production Board (kanban + stat tiles), Crew Assignments, Daily Log, Punch List, Materials / BOM | | PM | Project managers | Cable Schedule (filterable, dense table), Status Rollup (% progress bars), Test Reconciliation (import test results), RFIs, Punch List | | Owner Dashboard | GC / owner / CxP | Readiness Gate (6 % bars), Test Certification, Outstanding Issues, Production Trend (14-day chart), Portfolio |

Data model highlights

• 14 base tables covering projects, locations, racks, panels, ports, pathways, reels, cable runs, test results, RFIs, punch items, daily logs, BOM, and users
• 3 live SQL views — ct_run_status_rollup, ct_test_summary, ct_productivity — feed every dashboard without any manual aggregation
• Copper and fiber — Cat6/Cat6A, OM3/OM4/OM5, OS2; LC/MPO connectors; T568A/B enforcement per project; MPO polarity method (A/B/C) stored per run
• TIA-606 label discipline — machine-printed label status tracked per run; label-not-printed warnings surfaced in the Foreman's Labeling QA view
• Standards-aware: TIA-568, TIA-942, TIA-606-D, BICSI TDMM fields throughout

Who this is for

• Cabling and low-voltage subcontractors running data-center new-build or fit-out scopes
• GC Div 27/28 leads who need per-run visibility without paying for a DCIM platform
• RCDDs and RTPMs who already live in spreadsheets and want mobile field sync without ripping them out

Positioning

CableOS targets the documented gap between three incumbent silos — cable documentation tools, construction project management platforms, and certification test management software — none of which track install production at the cable-run level in real time. The per-team (not per-seat) pricing model makes it accessible to the cabling subcontractor, not just the owner-operator.