Fiber Management

RFI 10917-26
Fiber Management
Attachment A - Functional Requirements
1. Asset Management
1.1 Inventory all fiber related assets using unique IDs to ensure that every asset is
individually trackable. (Trench, Conduit, Innerduct, Buffer Tube, Strand, Splice,
Port, Distribution Panel, Fiber Structure, Slack Loop, Circuit etc.)
1.2 Enforce the parent-child hierarchy (Structure Conduit Cable Buffer Tube
Fiber) so that asset relationships stay structurally accurate.
1.3 Capture manufacturer, install date, fiber count, and cable type for each asset.
1.4 Track an asset's lifecycle stage and operational status to ensure it is auditable over
time.
1.5 Track asset maintenance and work order history natively or via 3rd party integration
(Lucity)
2. Network Management
2.1 Trace fiber-level continuity across splice points (A-end to Z-end) so that circuit
paths can be verified.
2.2 Record splice details with strand-to-strand mapping so that splice configurations
are documented accurately.
2.3 Run a path trace query on a single fiber or full circuit so that affected infrastructure
can be quickly identified.
2.4 Model ring, mesh, and point-to-point topologies so that the system reflects actual
network designs.
2.5 Track inbound and outbound FTP connection details including 'next hop' patches
to switches etc. beyond the fiber network boundary.
3. Patch Management
3.1 Assign ports to specific fibers/buffer tubes so that port-to-strand relationships are
documented.
3.2 Identify available vs. assigned ports so that open capacity can be quickly found.
RFI 10917-26 - Attachment A, Functional Requirements Page 1 of 4

3.3 Map cross-connects (patch cord A-end to Z-end) so that patching configurations
are traceable.
3.4 Track circuit assignment at the port/patch level so that patches can be tied to
specific circuits and customers.
4. Geospatial
4.1 Capture coordinates for all structures and cabinets so that assets are accurately
located on the map.
4.2 Compare as-built vs. as-designed layers so that discrepancies can be identified in
the field.
4.3 Render conduit and cable routes on a map so that the physical network can be
visualized.
4.4 Integrate with existing ESRI parcel/street layers so that fiber data aligns with the
city's broader GIS.
4.5 Generate a map showing where fiber/conduit is located so that 811/Locate
requests can be responded to.
4.6 Defined and documented GIS schema
5. Capacity Management and Planning
5.1 See real-time strand utilization counts per cable segment so that current capacity is
known at a glance.
5.2 Designate strands as reserved, available, or used so that capacity planning is
accurate.
5.3 Receive alerts on low-capacity segments so that upgrades can be planned
proactively.
5.4 Run what-if models for planned builds so that capacity impact can be assessed
before committing resources.
5.5 Display current state and planned state (i.e. anticipated new fiber runs/structures)
planned data
6. Field Mobility
6.1 Look up and edit asset information offline so that field work isn't interrupted by
connectivity gaps.
6.2 Scan barcodes/QR codes for asset ID entry so that data capture is fast and
accurate.
6.3 Attach photos from the field so that visual context is captured with the record.
RFI 10917-26 - Attachment A, Functional Requirements Page 2 of 4

6.4 Sync splice closure data over low bandwidth so that remote-area updates still get
through.
6.5 Conduct inspections (cabinets, patches, fiber) and capture this information in real
time, (7.3)
7. Documentation Management
7.1 Upload and version panel diagrams per structure so that documentation stays
current.
7.2 Generate splice sheets (auto or manual) so that splice records are consistently
documented.
7.3 Attach test results (OTDR traces, power readings) so that verification data is stored
with the asset.
7.4 Search documents (including photos) by asset ID so that relevant records can be
quickly retrieved.
7.5 Search documents (including photos) by location so that relevant records can be
quickly retrieved.
8. QA / Validation
8.1 Detect orphan fibers/buffer tubes so that incomplete records are flagged for
correction.
8.2 Check for duplicate IDs on import so that data integrity is maintained.
8.3 Flag continuity breaks so that circuit issues are caught early.
8.4 Enforce mandatory field validation on data entry so that records are never
incomplete.
9. Reporting / Analytics
9.1 Report utilization by region/cabinet/cable so that capacity trends can be identified.
9.2 Generate an aging asset report by install date threshold so that replacements can
be planned.
9.3 Generate an outage impact report by affected circuits/segment so that repairs can
be prioritized.
9.4 Supports Power BI integration
10. Integrations
10.1 Solution must fully integrate (OOTB) with ESRI ArcGIS
10.2 Support CentralSquare Lucity EAM integration for asset and work order
management
RFI 10917-26 - Attachment A, Functional Requirements Page 3 of 4

10.3 REST API available for custom integrations (PBI).
10.4 Solution must support Entra SSO integration including (preferably) provisioning
11. Access Control / Permissions
11.1 Role based access control (field tech, engineer, admin, viewer) so that access
matches job function.
11.2 Restrict field-level editing by role
11.3 View an audit log of changes by user so that accountability can be tracked.
11.4 CoR SSO authentication
RFI 10917-26 - Attachment A, Functional Requirements Page 4 of 4