Planning the engineering information lifecycle

Overview

Start by identifying the decision the engineering information must support: sizing, coordination, construction, operation or renewal. A model created for one purpose may lack the tolerances, attributes or ownership needed for another. Record the intended uses before selecting software.

Establish a requirements register with an accountable owner for each item. Define units, coordinate systems, revision conventions and review gates. Separate surveyed information from assumptions and mark confidence explicitly. Require a documented handover containing accepted files, exceptions and a change log.

Check how site changes return to the information model. A useful digital thread includes a route for corrections, review and publication rather than simply moving drawings into a new viewer. Measure information completeness and unresolved issues against agreed acceptance criteria.

A useful requirements register has one row per operating question. For example, an asset renewal question may need condition, service criticality, inspection date and failure history, while a drawing coordination question needs location, geometry and unresolved interfaces. Do not copy every attribute into every system. Describe the minimum information, who supplies it and what happens when it is missing.

At each review gate, compare the delivered information with that register. Keep rejected items separate from accepted information and record whether the issue is a missing source, an inconsistent unit, a geometry conflict or an unresolved engineering assumption. Assign the action to a person and include a due date. The final handover should explain these exceptions rather than silently presenting an apparently complete model.

For change control, distinguish a proposed revision from the accepted revision used by the operating team. Keep a stable asset ID while recording replacement or retirement as an event. Plan periodic checks of links, file versions and data ownership. These small governance decisions make the engineering record usable after the original design team has moved to another project.

Key considerations

• Define the operating question and asset boundary.
• Record input quality, units, ownership and revision.
• Agree review responsibilities and acceptance criteria.
• Verify project-specific requirements before implementation.

Related solutions

Integrated Civil & Infrastructure Design

Water & Wastewater Engineering

Utility & Corridor Engineering

Product capabilities

• Define the operating question and asset boundary.
• Record input quality, units, ownership and revision.
• Agree review responsibilities and acceptance criteria.
• Verify project-specific requirements before implementation.