Define Asset Information Requirements Before Submittals Begin
How owners can define useful asset data, identifiers, files, validation rules, and delivery responsibilities before information starts arriving.
Digital turnover succeeds when the owner defines the information needed to operate the facility before design and submittal workflows begin. Otherwise, teams collect large quantities of inconsistent data that are expensive to normalize and difficult to trust.
Technical overview
Asset Information Requirements: field logic map
Start with owner use cases
Asset information requirements should answer practical questions: what equipment must be maintained, which spare parts are required, what warranty is active, where is the accepted submittal, which system serves the space, what alarm or setpoint applies, and what record supports future replacement planning? The required data follows those decisions.
Interview facility management, operations, maintenance, energy, information technology, security, and capital-planning stakeholders. Identify the systems of record and the capabilities they can actually support. Collecting fields that no owner system or work process will use adds cost without creating value.
Define the information structure
Establish naming conventions, unique asset identifiers, facility and space hierarchy, system relationships, classification, required attributes, units, allowed values, document types, file names, and links. Common equipment attributes may include manufacturer, model, serial number, capacity, electrical characteristics, warranty, parts, maintenance requirements, and commissioning status.
Document which values originate in design, submittal, fabrication, installation, testing, or turnover and which party is responsible for each. A data dictionary should define the meaning and format of every required field so that completeness is not confused with consistency.
Plan exchange, security, and acceptance
The project execution plan should identify exchange formats, common data environment, folder structure, permissions, security, backups, review workflow, milestone deliveries, and final migration. Open exchange structures such as COBie may help, but the owner must still define which information is required and how it will be used.
Acceptance criteria should cover required-field completion, valid formats, controlled vocabulary, unique identifiers, location and system relationships, document links, file integrity, and consistency with accepted equipment. Define how rejected records are corrected and resubmitted.
Pilot the workflow before scale
Choose several representative assets with different complexity—such as an air-handling unit, pump, electrical panel, control device, and plumbing fixture group—and process them through the full workflow. Load the sample into the owner's intended platform and ask actual users to retrieve the information.
The pilot exposes naming conflicts, missing required fields, inaccessible files, duplicate identifiers, unusable links, and import limitations while correction is still inexpensive. Update templates and instructions before applying them to the full project.
Control change through final turnover
Information requirements should remain traceable as equipment is substituted, tags change, spaces are renamed, systems are reconfigured, and deficiencies are corrected. Periodic validation prevents a large closeout surprise and gives trade partners time to correct recurring issues.
Final acceptance should compare delivered records with installed assets and approved documents, not merely count populated cells. Retain the validation report, exceptions, correction status, final export, native files, and instructions for maintaining the data after occupancy.
Field application
A practical review checklist
- 01
Interview owner stakeholders and document the decisions that asset information must support.
- 02
Define included asset classes, identifiers, hierarchy, required attributes, units, controlled values, documents, and links.
- 03
Assign each data field to its authoritative source, responsible party, delivery milestone, and reviewer.
- 04
Specify exchange format, common data environment, permissions, security, backups, naming, and migration method.
- 05
Pilot representative assets through collection, validation, owner-system import, retrieval, correction, and acceptance.
- 06
Perform periodic and final installed-asset validation and retain the accepted data set with maintenance instructions.
Related Free tools
Put the relationships to work.
Authoritative orientation
References and further reading
Use the current adopted or licensed edition applicable to the project. These links provide public orientation and do not reproduce protected standards.
Continue exploring
One article. 235 free engineering calculators.
Move from the concept to a transparent calculation, or return to the complete Insights collection.