A twin that stays consistent with the site
Ongoing model and data maintenance, metric iteration and scenario expansion
Under an annual engagement we maintain models and data, iterate metrics and expand scenarios, and incorporate twin updates into the site's change process, so the twin remains consistent with the site through modifications, equipment replacement and process adjustments.
Our approach
One team scopes, executes and retests; conclusions are delivered as evidence, not checklists.
Twin updates built into management of change (MOC)
Twin updates are a step in the MOC approval for site modifications and equipment changes; before a change is closed, model, tags and metrics are verified as synchronised.
Metrics and views iterated on usage
Usage data for each view and metric is reviewed regularly; long-idle items are retired and frequent needs added, keeping functionality aligned with actual use.
Expansion reuses existing assets
New scenarios build on existing models, data integration and interfaces without repeating the upfront modelling and integration work, so marginal cost decreases over time.
Deliverables
Annual operations service
Model updates, data integration maintenance, platform operations and incident response, including platform vulnerability and patch management and an annual security retest.
Quarterly operations report
Availability, data quality, usage and iteration recommendations. Each quarter, simulation and prediction models are checked against new data and recalibrated when deviation exceeds the agreed range.
Scenario expansion
New areas, equipment and functions delivered to the annual plan. Each expansion comes with acceptance records and updates to the modelling standard and interface documentation.
How we deliver
Four stages, each with defined inputs, outputs and a client sign-off.
Operations start
Handover, change-sync mechanism, operations metric baseline.
Day-to-day operations
Change response, incident handling, data quality monitoring.
Quarterly review
Operations report, usage analysis, iteration plan.
Annual expansion
New scenario requirements, implementation, acceptance.
Frequently asked questions
Notes on scope, execution and delivery standards. Contact us for anything not covered here.
The twin is treated as part of asset information and, following the ISO 55001 requirements for asset information, kept consistent with the EAM register and maintenance records: additions, retirements and modifications are synchronised on both sides, and the register code is the asset code in the twin. In audits or certification, the twin can support evidence of current asset state.
Start from where you stand
Security, data and AI each start with a review of where you stand. The report and its findings are yours, whether or not the engagement continues.