{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-vrt-001","code":"wm-vrt-001-digital-twin","url":"https://ver.cy/models/wm-vrt-001-digital-twin/","name":"Digital Twin","alternateNames":[],"kind":"world-model","status":"todo","version":"unversioned","language":"en","classifiers":{"family":"World Models","category":"Information and virtual systems","entryKind":"standalone-mm","plane":"","domain":["INF.VRT.TWN"],"industry":["Cross-industry"],"navPath":"NAV.INF.VRT.TWN","tags":["digital","twin","inf.vrt.twn"],"facets":{}},"whatItIs":"A digital twin is a virtual representation of a specific physical asset, process or system that is kept in sync with it through data at a stated frequency and fidelity, and used to monitor, analyse or predict its behaviour. It differs from a generic model or simulation by being bound to one real counterpart, and from the digital thread, which links lifecycle data rather than mirroring current state.","purpose":"Virtual representations kept in sync with a specific physical asset, process or system.","scope":{"in":[],"out":[],"boundaries":[]},"distinguishingFeatures":["It is bound to one real counterpart and kept in sync with it, unlike a generic model or simulation.","Its value depends on stated synchronization frequency and validated fidelity.","It may write back to the counterpart, which raises safety duties absent from passive models.","Distinct from the digital thread, which connects lifecycle records rather than mirroring current state."],"structure":{"bundles":[{"id":"VRT001-B1","name":"Twin and counterpart","description":"What is twinned.","layers":[{"id":"VRT001-B1-L1","name":"Binding","description":"The physical counterpart and the scope of the twin.","findings":[{"id":"VRT001-F01","name":"Counterpart","description":"The real asset, process or system the twin represents.","questions":[{"text":"Which real asset, process or system does the twin represent, and by which identifier?","id":"VRT001-Q01"},{"text":"Which parts or aspects of the counterpart are in scope?","id":"VRT001-Q02"}]},{"id":"VRT001-F02","name":"Purpose","description":"What the twin is used for.","questions":[{"text":"Is the twin used for monitoring, prediction, control or design?","id":"VRT001-Q03"},{"text":"Who relies on its outputs?","id":"VRT001-Q04"}]}]}]},{"id":"VRT001-B2","name":"Synchronization and fidelity","description":"How closely it mirrors reality.","layers":[{"id":"VRT001-B2-L1","name":"Data link","description":"Data sources, frequency and latency.","findings":[{"id":"VRT001-F03","name":"Synchronization","description":"How and how often the twin is updated.","questions":[{"text":"Which data sources feed the twin, and how often?","id":"VRT001-Q05"},{"text":"When was the twin last synchronized?","id":"VRT001-Q06"}]},{"id":"VRT001-F04","name":"Fidelity and validation","description":"How accurate the twin is and how that was checked.","questions":[{"text":"What fidelity does the twin claim, and how was it validated against the counterpart?","id":"VRT001-Q07"},{"text":"Which models and their versions does the twin use?","id":"VRT001-Q08"}]}]}]},{"id":"VRT001-B3","name":"Actuation and control","description":"Whether the twin can act on reality.","layers":[{"id":"VRT001-B3-L1","name":"Write-back","description":"Commands from the twin to the counterpart.","findings":[{"id":"VRT001-F05","name":"Control path","description":"Whether and how the twin sends commands back.","questions":[{"text":"Can the twin send commands to the counterpart, and through which interface?","id":"VRT001-Q09"},{"text":"Which safety interlocks and approvals apply to those commands?","id":"VRT001-Q10"}]}]}]}]},"agentConduct":{"may":["Query the twin for current and predicted state.","Run what-if analyses on a copy of the twin.","Flag divergence between twin and counterpart.","Report the twin's last synchronization time and fidelity."],"mustNot":["Send commands to the physical counterpart without the configured approvals and interlocks.","Present twin predictions as measured reality.","Use a twin whose synchronization is stale for safety decisions.","Expose the twin of critical infrastructure to unauthorized parties."],"requiresHuman":["Enabling write-back control from the twin.","Acting on twin predictions in safety-critical operations.","Accepting a twin as validated for a new purpose."]},"ethics":{"considerations":["Twins of buildings, cities or people can enable surveillance if they include personal data.","Over-trust in a twin can lead to unsafe decisions when it diverges from reality.","Twins of critical infrastructure are security-sensitive."],"affectedParties":["Operators of the physical counterpart","People in or near the twinned asset","Owners and maintainers"]},"owners":{"steward":"The owner or operator of the physical counterpart, who answers for the twin's fidelity and use.","roles":[],"masterSystems":["Asset management system","Industrial data platform","Building or city information model repository"]},"relations":[{"target":"wm-vrt-013-digital-thread","type":"neighbor","note":"The digital thread links lifecycle data that a twin may draw on."},{"target":"wm-vrt-003-simulation","type":"related","note":"Twins run simulations to predict behaviour."},{"target":"wm-obj-001-physical-item-instance","type":"references","note":"A twin is bound to a specific physical instance."}],"interaction":{"identity":{"applicability":"required","items":["A twin is identified by its own identifier together with the identifier of the counterpart it represents.","In industry the Asset Administration Shell gives globally unique identifiers to the shell and the asset."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A twin names its counterpart, its data sources and its synchronization frequency.","Often confused with a 3D model, a dashboard or a one-off simulation."]},"capabilities":{"applicability":"required","items":["A twin can be synchronized, queried, used for prediction and, where enabled, send commands.","It can be versioned as its models and data sources change."]},"hazards":{"applicability":"required","items":["Unsafe physical actions triggered from a wrong or stale twin.","Cyber attacks reaching physical assets through the twin's control path.","Decisions based on unvalidated predictions."]},"interfaces":{"applicability":"required","items":["Asset Administration Shell (IEC 63278) for industrial assets.","ISO 23247 digital twin framework for manufacturing.","OPC UA and OGC SensorThings for data links."]},"context":{"applicability":"required","items":["Used in manufacturing, energy, buildings, infrastructure, cities and health care.","Safety and cybersecurity rules of the counterpart's sector apply to any control path."]}},"sources":[{"title":"ISO 23247 Digital twin framework for manufacturing (ISO)"},{"title":"IEC 63278 Asset Administration Shell for industrial applications (IEC)"},{"title":"ISO/IEC 30173 Digital twin - Concepts and terminology (ISO/IEC)"}],"openQuestions":["Planned model: boundary questions, research and every section remain to be written."],"resources":{"spec":"https://ver.cy/models/wm-vrt-001-digital-twin/spec.yaml","agents":"https://ver.cy/models/wm-vrt-001-digital-twin/AGENTS.md"},"provenance":{"origin":"planned (registry candidate)","builtFrom":["models/runtime-index.json","ver-cy/world-models/card-supplements/wm-vrt-001-digital-twin.json"],"providers":[],"researchStatus":"todo","generatedAt":"","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"_":"Planned entry, hidden from the catalogue until researched.","interaction.properties":"A digital twin is an information or software construct; its measurable attributes are configuration and operational data, not physical properties.","_supplement":"Sections authored in card supplement 1.0.1 by Claude (Opus 5.5) (2026-10-06, unreviewed). Written from the card's existing content and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}