Cable Ledger — how the math works

Every number the app shows, and where it comes from.

The app is a planning and tracking tool. Each section below gives the rule, the defaults and the standard it follows, so you can check any result by hand and know where a real job may differ.

Cable length

cable length = run length × (1 + allowance ÷ 100) + closet slack + outlet slack

The run length is what you measure or read off the plan, from the panel to the outlet. The cable length adds a routing allowance for the up, over and around the plan doesn't show, and the slack left at each end. The outlet slack is the fiber value for fiber cable and the copper value for everything else. A drop with no run length has no cable length: it's left out of the footage and listed in Checks as "No length yet".

SettingFeet jobMeter jobWhere it comes from
Closet slack10 ft3 mBICSI's TDMM recommends at least 3 m (10 ft) in the telecom room
Outlet slack, copper and coax1 ft0.3 m30 cm (12 in) at the outlet for twisted pair
Outlet slack, fiber3 ft1 m1 m (3.3 ft) at the outlet for fiber, rounded to 3 ft
Routing allowance10 percent10 percentRouting the plan doesn't show; set it to 0 when runs are measured along the real route

Project specs often ask for more slack than the defaults; change them under Job settings → Lengths. Every length is kept in meters and shown in the job's unit: feet as whole numbers, meters to one decimal, rounded half away from zero.

The 90 m check

Under TIA-568, horizontal cable (the permanent link) is at most 90 m (295 ft); the channel can be 100 m, which includes the patch cords. The app checks the cable length, because the slack loops are part of the cable between the terminations.

StatusWhenShown as
Overcable length > 90 mred, "Over 90 m (295 ft)", ▲ on the PDF
Near81 m ≤ cable length ≤ 90 morange, "Within 10 percent of 90 m", △ on the PDF
OKbelow 81 mnothing

Only copper is checked: fiber, coax and other cables never are. The check shows on the drop's row, in the editor, in Checks, on the pull sheet PDF and in the as-built CSV's "Length check" column. Example: a 300 ft run with the defaults is 300 × 1.1 + 10 + 1 = 341 ft (104 m), over; a 240 ft run is 275 ft (84 m), near.

Cable to order

For each cable product, the app counts the drops that have a length and shows the number of drops, the total cable length, the longest drop and the boxes. Boxes are packed by first-fit decreasing: sort the drops' cable lengths from longest to shortest, put each in the first box that still has enough cable, and open a new box when none has. Each drop is one piece of cable, so a drop never comes from two boxes.

Example: seven Cat6 drops at 1,408 ft of cable in all pack into 2 boxes of 1,000 ft with 592 ft left over. It's a planning number: crews who pull from several boxes at once end up with different leftovers.

Labels

Each drop gets one label, for both ends of its cable: the outlet and the panel port. TIA-606 has each end of a cable marked. A label is built from a template of text and tokens:

TokenGivesExample
{closet}The closet of the drop's port; with no port, the closet serving its room1A
{rack}The rack of the port's panel (can be empty)1
{panel}The port's panel codeB
{port}The port number, padded to the panel's digits, at least 2: a 24-port panel gives 02, a 144-port panel 00702
{room}The room's name101
{drop}The drop's number in its room3
{dropLetter}The drop's number as letters: 1 = A … 26 = Z, 27 = AAC
{seq}The drop's job-wide sequence number7
{type}The cable's label code (can be empty)CAT6A

{port:3}, {drop:N} and {seq:N} pad to at least N digits (1 to 6): D{seq:3} gives D007. For {port} the width is the larger of N and the panel's own, so every port on a panel has the same width.

PresetTemplateExample
TIA-606 style (default){closet}-{panel}{port}1A-B02
Rack style{closet}-{rack}{panel}{port}110-1A01
Room style{room}-{drop}101-3
SequentialD{seq:3}D007
Customany text with the tokensCAT6A110-1A01

TIA-606-A's horizontal link identifier is fs-an: f the floor, s the letter of the telecom space, a the patch panel (one or two characters) and n the port (two to four digits), so 2B-B23 is panel B, port 23, in telecom room B on floor 2. Later editions add rack and cabinet identifiers for bigger systems, and real project specs vary (one city's spec marks outlets 110-1A01: room 110, rack 1, panel A, port 01), which is why the template can be edited.

Progress

Each drop has five steps: pulled, panel end, outlet end, labeled, and tested (which counts only when the test is Pass). A drop is done when all five are.

job percent = floor( steps done × 100 ÷ (5 × drops) )

A job with no drops shows 0 percent. Rooms show "4 of 6 done"; steps show "Pulled 48 of 60". A failed test marks the row red, and the drop stays not done.

Checks

Checks is a list of eight lines, each with a count and each a tap away from its drops; a line at zero is hidden, and when every count is zero the job says "All clear". The Job screen's Checks row counts the drops behind at least one line.

  1. Over 90 m
  2. Within 10 percent of 90 m
  3. No label yet (with the reason: no port, or no closet)
  4. Duplicate labels
  5. Labels changed since printing
  6. Failed tests
  7. No length yet
  8. Longer than a box

The files

Pull sheet PDF. By room: a heading per room ("101 · served from 1A · 4 of 6 done") and a table of Label, Location, Cable, Length, Port and the steps, with empty boxes for the crew to tick and ticked boxes for steps done; lengths over 90 m print in red with ▲ and near ones in orange with △, so neither relies on color alone. By closet: every port of every panel in order, empty ones included, then the drops with no port. Letter or A4, in the language you pick, with "Page 2 of 5 · Cable Ledger" on every page.

As-built CSV. One row per drop in room order: Label, Room, Location, Cable, Kind, Run length, Cable length, Length check, Closet, Rack, Panel, Port, the five steps as Yes or No, Test, Tested length and Notes. The headers are always English, so one spreadsheet fits every job; numbers use "." for decimals and no grouping; the file is UTF-8 with a byte-order mark, CRLF line endings and RFC 4180 quoting, and a cell that starts with =, +, - or @ gets a leading apostrophe so a spreadsheet doesn't run it as a formula.

Labels CSV. Label, End (Panel or Outlet), Room, Location, Cable, Closet, Panel, Port: one row per label end, or one per drop. Drops with no label are left out and the sheet says how many. No formula guard, because label software would print the apostrophe.

Every export is named for the job, the export and the app ("Suite 200 - Labels - Cable Ledger.csv"), so no two overwrite each other.

Where the real world differs

Sources