The short answer is that we agree; keeping as much asset data out of the BIM model should be the focus.
As you say, the ability to persist an association back to an object ID is the key piece of the puzzle. Tandem, by default, ingests all the data from the source BIM files into our cloud-hosted database and maintains a link back via unique identifiers. By hosting this data in the cloud, we break away from managing a facility's BIM data in individual model files. If a subset of the asset data has already been captured in the source files and is meaningful to the owner/operator, it can be mapped to equivalent parameters in Tandem, unlocking the ability to edit and maintain the accuracy of that data over the lifecycle of the facility. This allows data to be cleaned, updated, or otherwise manipulated without expertise in BIM authoring tools like Revit. Once a BIM model is linked to Tandem as part of the facility twin, any subsequent updates are checked for changes, and only the updates are imported into the database. This allows the application to capture the complete history of edits against the asset data, regardless of whether that data is edited by individuals logged into Tandem on the web, API integrations, or any subsequent updates from linked BIM files.
For new builds with mature BIM processes and clear client requirements for downstream AM, asset information can be captured directly into Tandem in parallel to BIM development and delivery. Our vision is that at handover, the Asset Information Model in Tandem is the source of truth for standing up operational systems and processes that rely on this data downstream. In the future, our APIs will allow bidirectional integrations with AM Systems.
