Outside Plant Mapping Services
Draftech turns field observations and legacy records into an attributed GIS map of your aerial and underground network. One accountable team carries the asset record through design and as-built updates.
Get an asset record your next project can use
Draftech delivers outside plant mapping services for operators who need to know where their infrastructure is, what each asset carries, and which records still need verification. We map poles, strand, cable, splice points, vaults, handholes, and conduit into connected GIS layers, with attributes and source documentation that make the records usable beyond the initial handoff.
A cable route without structure identifiers leaves the next engineer matching drawings by eye. A vault shown in conflicting locations can send a survey team back to the field. We reconcile those discrepancies as part of the mapping scope, so unresolved questions stay visible and verified information reaches the people making design decisions.
OSP mapping is the asset inventory discipline within our broader GIS mapping services. Draftech's engineering is 100% in-house. Field collection, mapping, and engineering review share a single point of accountability, with a defined path for resolving gaps before they become design assumptions.
Match the mapping scope to your network
The right scope starts with the decision your team needs to make. An ISP extending fiber along an existing route needs cable, structure, and connection records it can reconcile with proposed work. An electric cooperative planning a broadband build needs a usable pole inventory with ownership and attachment information tied to the route under evaluation.
Carriers consolidating legacy plant records need consistent asset identifiers across drawings, spreadsheets, and GIS exports. BEAD subgrantees need infrastructure records that can support their project's reporting and closeout deliverables. We define the required fields and export structure against the client's supplied requirements at intake.
Each engagement separates existing infrastructure from proposed assets and identifies which records require field confirmation. That distinction helps buyers scope the actual work: collecting missing data, reconciling conflicting sources, building asset relationships, or updating a mapped network after construction.
Define the data model before collecting more points
An OSP inventory needs agreed rules for naming assets, recording their attributes, and connecting them. We establish the coordinate reference system, feature classes, required fields, and accepted attribute values before building the dataset. Your existing asset identifiers remain useful references when records move into the agreed structure.
The scope defines which attributes can be populated from supplied records and which require observation. Unknown ownership, missing cable counts, and uncertain conduit paths remain identifiable gaps. Filling an empty field with an unsupported value only moves the problem into the next project.
Aerial plant records
Pole features carry identifiers and available ownership, class, height, and attachment information. Strand segments connect the supporting structures, while cable records identify the plant carried along the route. Keeping strand and cable distinct makes it possible to document different cables using the same support path without merging their attributes.
Underground plant records
Vaults and handholes provide structure references for conduit segments and cable routes. Duct configuration, occupancy, and depth information are included where the source records or scoped field work support them. The dataset distinguishes a documented underground path from a route inferred between visible structures, so the apparent precision of a line does not conceal uncertainty.
Splice points and transitions
Splice identifiers connect location records to available cable and splice documentation. Aerial-to-underground transitions retain their relationship to the supporting pole, underground structure, and connecting segments. Mapping a splice location and documenting individual fiber assignments are different levels of detail; we establish the required level before production.
Reconcile legacy records with field conditions
We review the available GIS exports, CAD drawings, scanned maps, spreadsheets, photographs, and construction records together. Intake identifies overlapping coverage, inconsistent identifiers, missing attributes, and disagreement between sources. A newer drawing may still show proposed work, so its date alone does not establish what exists.
That review shapes the field survey scope. Collection targets the structures, attachments, route conditions, and attributes needed to resolve the inventory. Field observations stay associated with the relevant assets, making it possible to trace a correction back to the supporting record.
When sources disagree, we identify the affected feature and the evidence needed to settle it. A duplicate pole number may need record reconciliation; conflicting vault locations may require a field check. Items that remain unresolved are documented with their limitations for client review, rather than silently treated as verified plant.
Check geometry, attributes, and asset relationships
A map can look continuous while its records contain disconnected segments or duplicate structures. Our QA review checks both the spatial layout and the information attached to it. The checks follow the agreed data model and the intended engineering or operational use.
- Geometry checks identify misplaced features, duplicate geometry, route gaps, and segments that do not meet their intended structures.
- Attribute checks review required fields, accepted values, ownership references, and consistency between related cable and structure records.
- Identifier checks find duplicate asset IDs and references that point to missing records.
- Relationship checks confirm that mapped cables, strand, conduit, structures, and splice points connect as documented.
- Source checks compare mapped features with field observations, available as-builts, and design records, preserving distinctions between existing and proposed plant.
- Export checks compare the delivered files with the source dataset for missing features, altered attributes, and coordinate problems.
Review findings guide corrections or additional verification. The handoff identifies remaining limitations, so your team understands where the dataset supports a decision and where more evidence is needed.
Receive more than a map export
The deliverable package is defined around your GIS environment and the asset detail your team needs to maintain. It includes the mapped network and the documentation needed to interpret its fields and limitations.
- Attributed plant layers covering the agreed aerial and underground assets, cable routes, and splice locations.
- A field dictionary describing attribute names, meanings, accepted values, and identifier conventions.
- Source and verification information distinguishing observed conditions, supplied records, and unresolved items.
- QA findings and documented corrections, with outstanding data gaps identified for review.
- GIS files in the agreed delivery format, with review maps where needed for project coordination.
ArcGIS Pro and QGIS workflows support delivery in formats such as File Geodatabase, GeoPackage, shapefile, and GeoJSON. We confirm the receiving system's requirements during scoping, including which attributes and relationships must survive the export. A review map can accompany the data, while the editable dataset remains the basis for future updates.
Keep the inventory current through design and as-built
A mapped inventory becomes unreliable when design revisions and installed changes stop reaching it. We establish how new structures, reroutes, cable changes, and revised splice locations enter the dataset during the project. Existing, proposed, and installed conditions remain distinguishable as work advances.
Our CAD and GIS documentation service produces the drawings and documentation used for design, permits, and construction. OSP mapping supplies and maintains the attributed plant inventory those deliverables reference. This page's scope centers on asset records; drawing production is defined separately when your project needs both.
After installation, as-built documentation supplies the verified construction changes used to update the inventory. The closeout review reconciles those changes with the mapped assets and identifies outstanding discrepancies. Your next project can start from the updated plant record instead of reconstructing what changed during the last build.
Outside Plant Mapping Services FAQ
Can you start with incomplete legacy records?
Yes. Send the records you have, including partial drawings and inconsistent GIS exports. We assess their coverage and condition, then define the reconciliation and field collection needed to complete the agreed inventory.
How is mapping accuracy specified?
We establish positional and attribute requirements around the dataset's intended use before collection begins. Source quality and field methods must support those requirements. The handoff documents limitations where available evidence does not support the required confidence.
Will a mapped conduit route show available capacity?
Only when the supporting records or scoped verification establish duct configuration and occupancy. A route line alone does not establish usable capacity. We identify missing information so planning does not treat undocumented space as available.
Can you update an existing GIS instead of replacing it?
Yes. We review your current layers, identifiers, and required attributes to define the update scope. The delivery structure follows the agreed receiving environment, with checks for duplicate features and conflicting records.
What determines cost and schedule?
Route extent, asset density, record quality, field access, and required verification drive the work. Detailed connectivity requirements and the receiving system's data structure also affect scope. We review these inputs before defining the deliverables and schedule for your project.
Scope your outside plant mapping project
Send your route boundary, sample records, GIS requirements, and the decision or project milestone the mapping must support. Include known gaps and whether the scope ends at inventory delivery or continues through design and as-built updates. Draftech will use those inputs to define the collection, reconciliation, QA, and handoff work.
Contact our engineering team to scope your OSP mapping project.
info@draftech.com | 305-306-7407 | Miami Lakes, FL