Fiber As-Builts, GIS and Asset Handover

What the scope can include

Select the work and handoff your project needs. The agreement identifies the included deliverables and responsibilities.

• Reconcile installed conditions

  Compare supported redlines, surveys, photographs, structure records and change approvals with the design. Identify missing evidence and locations that still need verification.

• Connect route and network identifiers

  Align cable, duct, structure, splice, terminal, port and service records. Consistent identifiers help the operations team trace a connection and understand the assets affected by a fault or change.

• Prepare owner-standard CAD and GIS

  Coordinate layers, schemas, coordinate systems, attributes and file formats. Check geometry and relationships against the agreed source information while preserving stated accuracy limits.

• Label verification and unresolved items

  Separate certified survey information, supported field records and assumptions. An unchanged design drawing must not be represented as a verified as-built.

Prepare for the assignment

You can start with incomplete records. Tell us what is available and what still needs to be established.

• Information to bring

  Supported field redlines, final locations, splice/asset IDs, survey certification and GIS schema. Provide the current versions and identify information that remains unverified.

• The agreed handoff

  A coordinated as-built/GIS and asset-record package, source/verification notes and an unresolved-data register.

Decisions, fees and timing

Scope and dependencies determine the proposal. No universal price or approval date is assumed.

1. Confirm the basis and responsibility

   Review the available records, intended endpoint and authority to use the information. Assign missing inputs, technical decisions and the parties who can authorize changes.

2. Coordinate and review the work

   Prepare the included documents from agreed inputs, resolve interfaces with responsible specialists and track revisions. Record external decisions and conditions separately from work prepared for review.

3. Account for project-specific dependencies

   Missing field evidence, format conversion, asset reconciliation and owner standards. The proposal separates professional work, outside charges and review dependencies.

4. Deliver the defined milestone

   Provide the controlling documents and remaining-action record. Identify what is accepted, what still requires a decision and what belongs to a separately contracted next stage.

Agree the GIS handoff before conversion

A file extension does not establish accuracy, complete attributes or compatibility with an owner’s asset system. Share the required schema and sample records before the deliverable is agreed.

• KML, KMZ, shapefile and GeoJSON

  KML supports geographic visualization; KMZ packages KML and associated resources in a compressed file. A shapefile dataset and GeoJSON are other geospatial exchange formats with different structures and constraints. These are possible requested formats to evaluate, not a promise that every conversion is supported. Confirm the receiving system, required fields, sample import and the agreed delivery arrangement before committing to a specific format.

• CAD-to-GIS conversion and GIS as-builts

  CAD-to-GIS conversion maps drawing geometry and labels into the agreed asset layers and attributes. Establish units, coordinate reference system, source accuracy, asset IDs and connection rules. Validate geometry, missing fields, duplicate identifiers and sample imports against the source records. GIS as-builts must identify the supported installed condition and remaining unknowns; converting a design file does not verify where the cable was installed.

Service locations and acquired-network records

Location records must connect addresses and units to evidence about the network. Keep map preparation separate from a provider’s service commitment or certified filing.

• Serviceability mapping and location reconciliation

  Broadband service-location records reconcile addresses, units, location identifiers and the distribution assets that may serve them. Serviceability mapping compares those records with the operator’s stated connection criteria and current capacity information. Record source dates, conflicting addresses and unresolved unit counts. The FCC’s Broadband Serviceable Location Fabric is a reference location dataset; inclusion there is not proof that a specific provider currently offers service.

• Inherited records and reporting support

  For acquired-network records, inventory inherited drawings, permits, access agreements, attachments, splice/port schedules and tests. Trace each conclusion to its supplied source. Reconcile conflicting asset IDs and keep unknown conditions visible. Provider reporting support can prepare agreed datasets and exception registers for the operator’s authorized reporting team. That team decides availability, filing rules, certification and submission. Transferring records does not itself validate acquired rights or network condition.

Before you begin

Common questions