RL Think Tank Instrument
Digital Twin Readiness

Diagnostic

Is the twin a live system or a presentation layer?

Score the operating disciplines behind the model, each from 0 (absent) to 5 (owned and consistent). The point is not visual quality. The point is whether site state reaches the decision workflow in time to matter. The lens follows the information-management discipline of ISO 19650; latency gates the result, so a slow twin cannot rate as a live system however strong the other layers look.

Data owners iNamed accountability for each data stream: capture, model update, RFIs, progress, and schedule status.
Capture cadence
Processing pipeline
Schedule integration iWhether twin outputs enter the CPM, progress, RFI, or constraint workflow instead of living in a separate dashboard.
Action ownership
Median update latency iMedian time from observed field condition to a usable model or progress-state update. This gates the result: a slow twin cannot rate as a live system.
Read the note
48 readiness

Current state

Pilot System

The model has useful ingredients, but the workflow still depends on manual handoffs and late updates.

72 hr field event to model
Integration weakest control
Under 24 hr control target

Layer health

Next controls to write down

    Foundations

    The layers and the latency gate in this diagnostic draw on:

    • ISO 19650 — information management for BIM and digital delivery
    • Four-layer twin architecture — capture, process, integrate, act
    • UAV pose-estimation & computer-vision progress capture — Author's Research
    • Common Data Environment (CDE) — single source of project truth

    Diagnostic use only. Scores are directional and should be calibrated against the project's actual schedule, RFI log, capture plan, and decision cadence.