Project data is fragmented
CriticalDesigners, contractors, supervisors and clients work in different environments.
- Consequences
- Solutions and versions are difficult to trace.
How to connect BIM, GIS, project controls, construction as-built and long-term infrastructure asset management
In this business area, the greatest value will be created by a seamless infrastructure data chain. It is recommended to start with a clearly bounded first process and expand the solution in phases.
Infrastructure projects manage linear and point assets, coordinates, design models, actual measurements, quantities and future asset attributes. Data value depends on whether the same object remains recognisable as the stage and organisation change.
Data must remain useful from feasibility study through decades of operation.
Design solutions, existing networks, plots and actual construction geometry must be visible in a common spatial context.
Information passes through different contracts, responsibilities and technological environments.
An unstructured project archive is insufficient if the operator requires asset hierarchy, attributes and maintenance data.
Infrastructure digitalisation is expanding from design models to a whole-lifecycle data chain. The link between BIM, GIS, surveying, progress and asset register is becoming important both for investment control and for reliable asset handover to the operator.
Need, alternatives, sites, existing networks, permits and funding constraints are assessed.
Technical models are created, geometry, environmental constraints and utility networks are coordinated.
Work packages, information requirements, schedule and contractor responsibilities are established.
Quantities, work locations, geodetic measurements, changes and quality evidence are recorded.
The contractual outcome, funding conditions, documents and actual asset condition are verified.
Design and actual data are converted into a useful asset register, GIS layers and maintenance information.
Drawings, maps, measurements, quantities and asset information are stored separately, so relationships for the same infrastructure asset are reconstructed manually.
Designs, drawings, GIS layers and reports are stored in separate environments, and relationships are reconstructed manually.
Design and territorial data are digital, but object identity and changes between systems are not linked.
Models, documents, spatial data and approvals are managed according to common statuses and information requirements.
Project object linked to actual geometry, quantity, asset attributes and handover status.
Portfolio history, condition and spatial data are used to forecast investment, risk and maintenance scenarios.
The greatest risk arises when the design object, geographical location, geodetic as-built and asset register do not share a common identifier. A single-asset design-to-as-built scenario allows this chain to be validated in practice before the entire project is completed.
First priority is the chain connecting the design model, GIS location, as-built geometry, quantities and handover attributes for a single infrastructure asset.