Digital Asset Management & Operational Support

Project context

Help the operator find an asset, understand its records and use the information in day-to-day asset management. The starting point is the required operational task and available data—not a dashboard or 3D viewer in isolation.

Inputs & requirements

• Accepted asset register, model and handover records, including unresolved information limitations.
• Operational use cases, selected platform, user roles, data ownership and update responsibilities.
• Available BMS, IoT, asset-management or CMMS interfaces, licences and authorised access.
• Agreed data points, units, timestamps, refresh expectations and exception-handling requirements.

Share a non-confidential requirements summary first. Restricted project information should only be exchanged through an agreed secure route.

Technical method

1. Define the operational information model and map asset identities before model optimisation.
2. Prepare lightweight model content for the agreed browsing environment. Test object selection, search, properties and asset relationships.
3. Configure asset records, documentation links, permissions and agreed external data mappings.
4. Test normal and failure conditions with the receiving team; document the configuration and train users for the agreed workflows.

Deliverables

Review criteria

• Asset identity remains stable or reliably mapped through conversion and later model updates.
• Users can find the agreed assets and retrieve the correct properties and documents.
• Status information shows its source, timestamp, units and freshness. Missing or stale data is not presented as a normal condition.
• Role permissions, interface interruptions and maintenance-record workflows behave as agreed.

Information & application

From 6D handover to operational use

The 6D handover scope prepares and verifies the asset information. This 7D scope maps that information into the receiving platform and supports its continued use. Asset IDs and field requirements should therefore be coordinated before handover, not reconstructed afterwards.

Equipment status and maintenance records

Where suitable interfaces exist, an asset can be associated with BMS or IoT readings, historical information or a maintenance-system record. We agree what is available, how it is mapped and who maintains the connection. Live data is optional; a documentation and asset-management platform can be useful without it.

Platform capabilities vary. For example, the Autodesk Tandem Data API supports model data and integrations with asset, work-order and IoT systems. This is a technology reference, not a claim that SBT owns that platform or has delivered the illustrated integrations.

Inspection and work-order records can be linked within the agreed workflow. The operator remains responsible for creating, validating and acting on maintenance information unless a different responsibility is expressly appointed.

Responsibilities

This is digital information and platform support, not an SBT-owned SaaS product or a physical maintenance contract. Sensors, subscriptions, 24-hour operations, predictive-maintenance guarantees, automatic equipment control and safety-critical control are not included by default. Integration depends on system capabilities, permissions and the agreed scope.

Common questions