Apply the channel map to ISP PoP service zones
For an ISP PoP, use a service-zone map to identify the owner, handoff, and controlling document for each part of the route. Add the zone ID and boundary owner to the channel record. Release or reuse a BOM only when the endpoint, route, mapping, acceptance, and revision records agree.
Treat the zone as a document lookup key. The approved interface source, route drawing, position map, and acceptance plan still control the cable decision.
Disclaimer
Use this addendum to control project records. It is a planning reference only, not a cable specification or proof of equipment compatibility. The equipment documents, complete route, site requirements, and project design authority govern the final assembly.
Record the owner and handoff for each service zone
Use the service-zone map below as an addendum to the main channel worksheet. The names are planning labels; adapt them to the actual facility and contract structure.
| ISP PoP service zone | Boundary to record | Accountable design input | MPO role to evaluate | Hold the path when |
|---|---|---|---|---|
| Carrier entrance or demarcation | Carrier facility interface to customer-controlled cabling | Carrier handoff document, facility rules, and the identified owner on each side | A transition or aggregation path may be evaluated; do not assume the carrier-facing interface | The demarcation, interface, responsibility, or permitted cable construction is unresolved |
| Meet-me room, ODF, or cross-connect | Provider-owned, colocation-managed, and customer-owned frames or panels | Cross-connect order, port assignment, panel map, and facility approval | Evaluate MPO only for the documented panel-to-panel or panel-to-equipment channel | The cross-connect record and the physical panel map disagree |
| Core or aggregation area | Network equipment ports to the first controlled distribution point | Current equipment or optical-interface document and approved port assignment | Evaluate a direct parallel channel or a structured trunk, depending on the endpoint and full route | The endpoint revision, lane assignment, or passive path is missing |
| Hosting or cloud data hall | Shared distribution to tenant or platform racks | Rack/row owner, tenant boundary, patching policy, and change-control record | Evaluate repeatable trunks or transitions where the interface map remains controlled | Shared infrastructure and tenant responsibility are not separated in the record |
| Inter-building or DCI boundary | Building exit, outside-plant segment, building entry, and inside-plant transition | Route owner, facility/code authority, transition design, and endpoint documents | Evaluate MPO only for the portions whose environment and interfaces support the selected assembly | One cable is assumed to cross different environments without an approved transition plan |
| Access, feeder, or outside-plant handoff | PoP distribution boundary to the access-network route | Access-network design authority, splice/closure plan, and handoff definition | Keep the access plant and indoor MPO channel as separate design records unless the project authority defines a controlled combined path | An indoor assembly is being used as a substitute for an unresolved outside-plant design |
Use each row to name the document owner, the physical handoff, and the condition that stops release. When different organizations control the two sides of a boundary, record carrier demarcation and fiber handoff responsibility in separate fields.
At an inter-building or access boundary, the route owner must approve the cable construction, rating, and any outside-plant to inside-plant transition. Do not infer tensile, crush, bend, flame, water, UV, or rodent requirements from the service-zone name. Record the applicable project and site requirements instead.
Use one record format across the PoP
A common record format can cover path IDs, endpoint names, source and BOM revisions, label syntax, approvals, exceptions, as-built updates, and the fields that suppliers must complete.
Apply that format across the facility, but make a separate physical decision for any path with different endpoints, route, environment, or acceptance requirements. A service term such as core uplink, cloud connection, DCI, or access handoff describes the function. It does not prove that two cable assemblies are interchangeable.
Check configuration equivalence before reusing a BOM
Compare the controlled records field by field before two service paths share an approved assembly or spare. Use the following MPO configuration equivalence check for the controlled MPO BOM.
| Equivalence field | What must match in the approved record | If it does not match |
|---|---|---|
| Endpoint interfaces | Interface type, optical-interface source and revision, port/position assignment, and any equipment-specific restriction | Create a separate channel decision and BOM line |
| Complete passive route | Every panel, adapter, cassette, splice, transition, and mated connection included in the design | Recalculate and approve the full channel separately |
| Physical construction | Fiber category, connector interface and polish, position count, gender/keying where applicable, cable rating, breakout, pulling eye, and length tolerance required by the project | Do not treat the assemblies as substitutes |
| Position and polarity map | End-to-end position mapping, orientation, patching state, and the approved polarity method for that exact channel | Issue a distinct map and part identity |
| Acceptance record | Project test method, reference method, limits, required file format, path ID, and exception authority | Keep acceptance and spare status separate |
| Document control | Drawing revision, BOM revision, approved supplier response, change owner, and as-built status | Hold procurement or replacement until the records agree |
Approve a spare against the full configuration record. Matching service names, nominal lengths, or connector-family labels are insufficient.
If any field is unresolved, record it as a question before requesting a quotation. Do not ask a supplier to replace a missing project input with its default.
Keep connector inspection and channel-performance evidence as separate records. IEC 61300-3-35:2022 covers visual inspection within its scope and states that inspection does not replace measurements such as attenuation and return loss. IEC 61280-4-5:2020 addresses attenuation measurement, polarity, and length for installed MPO-terminated cabling when the test setup and channel fall within that standard's scope. Neither citation makes one test instrument or acceptance limit universal. The project acceptance plan still has to name the applicable method, reference method, limits, file format, path ID, and exception authority.
Apply the ISP PoP addendum in five steps
- Assign the service-zone ID and path ID.
- Name the accountable party on both sides of every handoff.
- Link the endpoint, route, panel, and facility documents with their revisions.
- Run the configuration-equivalence check before reusing a BOM line or spare.
- If an owner, boundary, or source remains unresolved, mark the path as on hold. Otherwise, link the approved decision to the existing channel record.
Make a controlled release decision
| Record state | Decision | Required record action |
|---|---|---|
| All six equivalence fields agree and the controlling approvals are current | Reuse the approved BOM line or spare | Link the equivalence decision to the path ID and current source revisions |
| One or more equivalence fields differ | Separate the configuration | Create a distinct channel decision, position map, and BOM line for the affected path |
| A required owner, source, boundary, or revision is missing or conflicts with another record | Hold | Name the unresolved item and the party responsible for resolving it; do not apply a supplier default |
| An exception is proposed | Escalate | Record the approving authority, affected path, scope, conditions, and linked document revisions before release |
Do not reuse a previous equivalence decision after a controlling endpoint source, passive route, physical construction, position map, acceptance plan, or linked document revision changes. Run the check again against the current records.
Add these fields to the project record
For every path that crosses a service-zone boundary, extend the fiber path ownership record with:
- service-zone ID and path ID;
- facility, carrier, network, tenant, and installer responsibility at the handoff;
- the document that controls each endpoint and its revision;
- the last customer-controlled and first provider-controlled connection;
- the owner of the passive-route drawing and panel map;
- any environmental or route transition requiring separate approval;
- the person or role authorized to accept an exception;
- the drawing, BOM, position-map, and as-built revision that must remain linked.
If any of these fields lacks an owner or controlling source, mark the BOM line as on hold instead of applying a default cable rule.
Carry the service-zone ID and equivalence decision into the same supplier-response, buying-process, destination-control, and worksheet records used for the rest of the channel.
