A 144-count feeder that nobody assigned is not spare plant. It is a rumor. The mill already shipped the glass. The crew already lashed the sheath. Operations still cannot say which fiber they may cut over on a Saturday restoration, because the count worksheet never became an assignment schedule.
This guide starts after the count is frozen. How many fibers to order is a different worksheet. Here we write the assignment row: identity and path, then the endpoint, the circuit, plus the state. Messenger strand is out of scope. So is picking a cable size.
What a Fiber Strand Utilization Design Guide Records
A fiber strand utilization design guide is the assignment schedule written after cable strand count is frozen. Each glass fiber gets 6 fields: cable ID, tube/fiber ID, continuous splice path, endpoint, circuit assignment, plus one explicit state. Available, reserved, working, retired. Those fields must match the issued revision.
Fiber Strand Utilization Design Guide Worksheet
The count is the stock step the mill shipped. A 144-count feeder is a common input. That number is an input. It is not this sheet. Our fiber strand count design planning article owns take rate and the named spare pools, then rounding to a 12-fiber step. Once that row is frozen, this schedule names every glass fiber inside the sheath.
Messenger wire is a different object, and fiber strand here means a glass fiber inside the sheath, so we do not inventory aerial messenger on this assignment sheet.
Draftech's in-house fiber network design writes the assignment into the LLD. Engineering stays in-house. When construction is in scope, Draftech-managed subcontract crews deliver full turnkey under our QA/QC and safety program. We do not claim a self-perform construction crew today.
The Fiber Optic Association published FOA Standard for Installing Fiber Optic Cable Plants, 2025 V1. Section 13.1 of that standard requires the path of every fiber to be identified through intermediate connections, including cable identification and splice locations. That is a path rule. It is not a spare percent, and it is not a utilization ceiling the designer may invent.
ANSI/TIA-606-D, Administration Standard for Telecommunications Infrastructure, published October 5, 2021, specifies identifiers and records, plus linkages for infrastructure components that an OSP cable ID still has to map onto before the NOC can query it. Confirm whether the contract names that edition. A campus that adopted 606-D still has to map those identifiers onto OSP cable IDs the NOC can query.
This sheet does not pick a mill count, and inventory platforms are a different article, so a spare percent is not a field we will print on this assignment schedule. Those jobs already have their own pages. The only question here is whether each fiber in the frozen count can be found without calling the designer.
Six Fields Every Assigned Fiber Must Carry
A drawing layer named FIBER_FINAL is not an identity. The schedule has to join the mill-labeled sheath to the tube the splicer opens. The port the NOC will light is the third key on that same row. If any of those keys is missing, the row is not assigned. It is a placeholder.
We treat 6 fields as the minimum join, and the operator may add columns, but we do not drop these 6 to make the sheet fit a title block.
Cable ID and tube/fiber ID are governed keys
Cable ID is the sheath the mill tagged and the GIS record already uses. A stationing label on a plan sheet is useful context. It is a weak join when two laterals share a street. We write the cable ID that the inventory record will query, then we write the tube and fiber inside that cable so the splicer and the NOC are looking at the same keys.
Tube/fiber ID is not a house color lecture. ANSI/TIA-598-D, Optical Fiber Cable Color Coding, approved July 9, 2014, with addenda ANSI/TIA-598-D-1-2018 and ANSI/TIA-598-D-2-2018, is the identification scheme many U.S. OSP contracts name. Corning Optical Communications AEN029 Revision 13, published March 12, 2026, follows TIA/EIA-598. We record the edition the contract names. We do not reprint a 12-color sequence as Draftech policy.
RUS-financed plant is narrower. 7 CFR 1755.902, Minimum performance Specification for fiber optic cables, current on eCFR as of September 14, 2026, requires each fiber in the cable to be distinguishable, with buffer tubes and fibers identifiable. If the project is not RUS work, that section does not become our default. The contract still has to name the scheme the splicer will use.
| Field | What it answers | Failure if blank | Authority |
|---|---|---|---|
| Cable ID | Which sheath this glass lives in | Two cables share a color set and the wrong one is opened | Operator cable register on the issued revision |
| Tube/fiber ID | Which glass inside that sheath | The splicer guesses from color memory | The identification standard named in the contract |
| Continuous splice path | How this fiber stays one path through closures | A through-splice is treated as a drop | FOA Standard 2025 V1 Section 13.1; owner splice model otherwise |
| Endpoint | Where the path lands | A live circuit is lit on the wrong panel | Issued LLD structure and port schedule |
| Service or circuit assignment | Why the fiber exists | A reserved fiber is consumed as leftover | Operator service plan or equipment plan |
| State | What anyone may do with it today | GIS shows dark glass and a tech cuts it | Operator assignment policy on the issued revision |
The table is a preview map. Cable ID and tube/fiber ID are the join. The remaining fields still have to land on the same row even when one sheath carries working fibers next to reserved fibers in the same buffer tube. The schedule still keeps a row per fiber, because a dark fiber with no state is not available. It is unlabeled capacity.
The path has to land at a named endpoint
A continuous splice path is the same fiber through every closure it crosses, written so a reviewer can walk it without calling the designer. Endpoint is the structure and port where that path stops. That landing may be an FDH tray or a patch panel. It may also be a terminal, or a capped dead-end the owner accepted on the issued revision. Service or circuit assignment is the reason the fiber exists, taken from the operator service plan or the equipment plan, not from a leftover note on the title block.
If the equipment plan assigns port 4 on FDH-12 to circuit C-18, that assignment is the authority. A percentage we invent is not. We copy the named circuit onto the fiber row and we refuse a row that says "future" without a named owner for that future.
Spare is not a field and it is not a state. A leftover column labeled spare hides whether the fiber is available to cut over. It also hides a reserved later use and a circuit that is already working. Write the state. Then write who may change it.
Available, Reserved, Working, Retired
One thing I still reject in our own reviews: a leftover column labeled spare with no state. I have signed packages that carried it. The operator then asked which unused fiber they were allowed to cut over, and the drawing had no answer. That limitation is on us. We now refuse a row that cannot name its state.
The four states are explicit. They are not interchangeable, and they are not a spare percent.
- Available: the operator may assign this fiber now, under the issued revision.
- Reserved: a named later use owns it, and a Saturday cut may not take it.
- Working: a live service or circuit occupies it.
- Retired: it must not be reused until a new issued revision says otherwise.
Reserved is the state that saves the second-phase cabinet on the far side of a river crossing when a Saturday restoration would otherwise consume that glass. Available is the state that lets restoration proceed without a design call. Mixing them is how a named later use disappears into a Saturday cut, then reappears as an emergency order six months later.
Working is not lit on the day of splice; working means the service or circuit assignment is in effect on the issued revision that the NOC will query. A fiber spliced through and parked for a customer who has not taken service is reserved if the operator already committed it, or available if they did not. The operator assignment policy decides. We do not invent a growth allowance to cover the difference.
Retired is a controlled withdrawal. A cut fiber left in the sheath is still a fiber. If the owner has taken it out of service, the schedule has to say retired so GIS does not offer it as dark capacity. A blank where a state should be is how a retired fiber gets a new circuit ID.
We do not publish a utilization ceiling. If the operator, the contract, or the equipment plan names a hold point, we write that hold point on the same row. If they have not named one, we do not print 80 percent on the title block and call it engineering.
Keep One Continuous Splice Path
A fiber that changes identity at every closure is not a path. It is a chain of local guesses. The schedule has to carry one continuous splice path from the first endpoint to the last, even when the physical glass is fusion-spliced through a 288-count sheath into a 48-count lateral.
A cable-ID-only schedule still fails review. FOA Standard 2025 V1 Section 13.1 already requires the path through every splice location. The prints have to name which tube, then which fiber, before the fusion splicer is powered on a 288-count sheath that fans into laterals.
Through-splices and tap splices are different events on that path. A through-splice keeps the same assignment and the same state across every closure the fiber crosses, which is why a tap that feeds a terminal has to change the endpoint on the fibers that leave. If the diagram shows a tap and the schedule still shows a through path, the issued revision is already wrong. Hold it.
Dead-ends have to be explicit. A capped fiber with no endpoint is how a later designer treats the cap as available glass. Write the dead-end as the endpoint, write the state as available or reserved per the operator policy, and write the closure ID so the next crew can find the cap without opening every tray in the run. Whether that closure can physically sit at the candidate site is a later constructability sheet, covered in our fiber cable enclosure placement design guide.
That leftover spare column becomes a restoration problem at scale. The next section is where the four records have to agree, or the path is only true on one sheet.
Reconcile Schedule, Splice Diagrams, GIS, and Revision
Four records have to name the same fiber, and if they do not, the issued revision is not issued; it is a draft wearing a stamp that the splicer should not treat as authority.
- Fiber schedule: the assignment rows for every fiber in the frozen count.
- Splice diagrams: the path through each closure and tray on that same ID set.
- GIS or inventory: the same IDs and states the NOC will query.
- Issued revision: the stamped set that controls the other three.
The fiber construction package deliverables guide lists the assignment table as a package sheet. This post does not rebuild that package. It says what each row on that table must carry, and it says the table is not done until GIS and the splice diagrams use the same keys.
Platform choice is a different job. Our fiber network inventory management software comparison is where system fit belongs. Here the requirement is simpler: whatever system holds the inventory record must carry cable ID and tube/fiber ID. Path, endpoint, assignment, plus state must sit on the same row. Those values must match the issued revision.
The issued revision wins the mismatch. If GIS shows available and the schedule shows reserved, GIS is wrong until the stamped set is updated. Editing GIS first is how a reserved fiber becomes a working circuit with no design trail.
I would rather hold the issued revision than let GIS carry a working fiber that the schedule still shows as available. A one-day hold beats a cutover that lands on a circuit the operator thought was parked. Revision lineage is the proof. A GIS edit with no revision ID is not a design change. It is a rumor with coordinates.
Field redlines do not silently become states. A splicer who caps a fiber still leaves that fiber on the schedule until the owner issues the revision that records the cap. The as-built then copies the issued state. Copying the field guess into GIS before that revision is how available and retired swap places for the life of the plant.
Assignment Recommendations by Owner Type
Rural cooperative or single-state ISP under 5,000 passings: freeze the count, then freeze this schedule before anyone opens a closure. Use the four states on every row. Do not print spare. If the operator has no assignment policy yet, write available and reserved only, and name who may move a fiber from reserved to working. Hold GIS updates until the issued revision carries those states.
Overbuilder on a 2026 BEAD schedule: lock cable ID and fiber state at LLD, not at the HLD planning number. Tube/fiber ID belongs on the same row. Grant closeout will ask what was assigned. A substitution from a 144-count sheath to a 96-count sheath that never hit the schedule is a records failure, even if the glass in the ground is sound. Segment-based release lets one serving area splice while another is still in review.
Campus or municipal telecom owner with dedicated circuits: keep PON take-rate math off these rows. Assign by circuit ID from the equipment plan. A 12-count that carries eight working campus links, two reserved protection paths, and two available fibers is readable two years later. A 24-count labeled spare is not.
The useful outcome is a stamped set the NOC can query without a design call. GIS and the splice diagrams have to agree with the assignment table on the same keys before anyone opens a tray. A mismatch after hours is a hold nobody can staff.
That is the problem this service removes. A leftover spare column is the first failure we still catch in our own packages. GIS that disagrees with the stamped set is next. Splice diagrams that change a fiber ID at every closure keep showing up after that, and field redlines that never hit the issued revision sit beside them. Draftech keeps the assignment schedule in-house so those failures stay on the sheet, where they can still be fixed.
Active in 24 states. Available across all 50 U.S. states. If a live route needs the assignment schedule before splicing starts, start with a free 20,000-ft design review. For a schedule already in draft, reach out at info@draftech.com.
Talk to our fiber design team about your assignment schedule. Request a review of cable ID, splice path, and fiber state before the first closure is opened.
