DTScribe: Generating Models for Digital Twin Reporting using Local Large Language Models
Organizations: Département de Génie Informatique et Génie Logiciel, Polytechnique Montréal, 2500, chemin de Polytechnique, Montréal, H3T 1J4, Québec, Canada · Facultad de Ingeniería y Ciencias Básicas, Universidad Autónoma de Occidente, Carrera 25 #115-85, Santiago de Cali, 760030, Colombia
Abstract
The development of a digital twin brings together many stakeholders and technical components. We have previously investigated the reporting of the conceptual architecture for these digital twins as an artifact for discussion. However, we find that the activity of modeling the digital twin for visualization and consensus-building can be quite tedious and time-consuming. In this article, we explore the automation of model generation using large language models, targeting the model required for digital twin reporting. Our approach is designed to ingest digital twin documents and output both the conceptual architecture visualization and a reporting page for that digital twin. We first extract from the input the key details aligning with our twenty-one-characteristic Digital Twin Description Framework described in previous work. Then, we generate a description model in the Ontological Modeling Language, representing the digital twin as a constellation of models, data, enablers, and services. We utilize refinement loops with large language models acting as judges and ontological reasoning to increase artifact quality as measured by our metrics. We investigate how architectural and parameter choices affect artifact quality, such as how refinement loops enable local large language models to produce sufficiently high-quality results comparable to larger models. We also detail insights and lessons learned useful for practitioners, such that they can integrate our techniques to accelerate their digital twin reporting or for other model generation tasks. These insights include the use of medium-sized local models (around 20 billion parameters), the avoidance of large language models as judges and clustering for characteristic extraction, and the recommendation of at least two reasoner loops for Ontological Modeling Language refinement.
Figures & tables
| Extracted Description | |
| The DT synchronises with the Physical Twin through an event - driven RabbitMQ message bus. Sensor readings are streamed from the low - level driver to the broker and consumed by DT components (visualisation dashboard, Kalman filter, calibration module) in near - real - time, enabling sub - second latency for monitoring and control. Calibration can be triggered on - demand, and co - simulation can run on historical or live data streams. | |
| The architecture defines a single Digital Twin instance associated with one Physical Twin (the incubator). The hierarchy consists of the Physical Twin, a low - level driver, a controller, and the Digital Twin which contains the simulation models, calibration and monitoring services. No decentralized or multiple - twin coordination is described. | |
| The system follows a message - driven component architecture. Core components are: Low - level driver (sensor/actuator abstraction), Controller (bang - bang logic), Communication Server (RabbitMQ), Time - Series Database, Dashboard, Calibration service, Kalman - filter based anomaly detector, and co - simulation engine. RabbitMQ provides synchronization and decoupled communication; services subscribe to relevant topics, process data, and publish results, forming an orchestrated DT constellation. | |
| Integration with external systems is achieved via the RabbitMQ message broker, which exposes standard AMQP interfaces for data exchange. Sensor data and control commands are published/subscribed over this broker, allowing other enterprise applications or additional Digital Twins to connect. The time - series database and dashboard consume the same streams, providing interoperability through common messaging protocols. No specific enterprise standards (e.g., OPC UA) are mentioned. |
| Model | Parameter count | Precision | Min. VRAM | Size Category | Release Date | Ollama ID |
| EmbeddingGemma | 0.3B | BF16 | 0.6GB | Small | 2025-09-04 | 85462619ee72 |
| Ministral3 3B Instruct | 3B | INT4 | 3GB | Small | 2025-12-02 | f04aa1c738f6 |
| Ministral3 8B Instruct | 8B | INT4 | 6GB | Small | 2025-12-02 | 1922accd5827 |
| Ministral3 14B Instruct | 14B | INT4 | 9GB | Small | 2025-12-02 | 4760c35aeb9d |
| gpt-oss-20b | 20B | INT4 | 16GB | Medium | 2025-08-05 | 17052f91a42e |
| Qwen3-Next-80B-A3B | 80B | INT4 | 50GB | Medium | 2025-09-10 | b2ebb986e4e9 |
| Config. | P1 | P2 | P3 | P4 | P5 | Overall |
| +Judge | ||||||
| +Cluster |
| Configuration | Extract Time (s) | OML Gen. Time (s) | Total Time (s) |
| Base | 62.5 | 255.0 | 317.5 |
| +Cluster | 208.2 | 195.8 | 404.0 |
| +Judge | 647.9 | 257.2 | 905.1 |
| +Cluster+Judge | 2636.1 | 213.8 | 2849.9 |
| Paper ID | Configuration | Ministral3 (3B) | Ministral3 (8B) | Ministral3 (14B) | Qwen3-Next (80B) | gpt-oss (20B) | gpt-oss (120B) |
| P1 | Base | 85.7 7.7 | 84.6 3.7 | 82.7 7.4 | 90.5 6.0 | 96.2 5.3 | 90.1 4.1 |
| +Cluster | 73.5 10.5 | 73.9 4.2 | 62.3 4.3 | 45.3 10.9 | 41.7 6.6 | 64.0 16.7 | |
| +Judge | 89.1 5.6 | 84.0 4.7 | 83.4 8.1 | 92.6 5.5 | 96.6 3.5 | 92.2 3.0 | |
| +Cluster+Judge | 75.6 7.7 | 79.4 7.0 | 72.6 9.4 | 70.1 7.2 | 60.4 8.1 | 68.4 7.5 | |
| P2 | Base | 90.9 1.3 | 87.4 16.3 | 93.3 2.4 | 94.3 5.1 | 98.9 2.5 | 98.1 2.7 |
| +Cluster | 77.5 7.3 | 88.8 7.1 | 81.1 4.5 | 51.8 2.9 | 52.6 5.0 | 78.9 6.6 |
| Paper ID | Configuration | Ministral3 (3B) | Ministral3 (8B) | Ministral3 (14B) | Qwen3-Next (80B) | gpt-oss (20B) | gpt-oss (120B) |
| P1 | Base | 4 12 | 0 4 | 4 24 | 12 76 | 28 84 | 60 84 |
| +Cluster | 12 16 | 0 24 | 32 72 | 64 72 | 88 96 | 92 92 | |
| +Judge | 0 0 | 0 4 | 4 24 | 24 68 | 48 88 | 56 92 | |
| +Cluster+Judge | 0 4 | 4 24 | 20 56 | 56 76 | 72 92 | 76 92 | |
| P2 | Base | 0 0 | 4 4 | 4 32 | 4 52 | 40 92 | 64 76 |
| +Cluster | 0 0 | 4 28 | 20 52 | 20 60 | 56 96 | 72 96 |
Appendix figures & tables5 assets
Supplementary material from the paper’s appendix.
Appendix
| : Purpose Cluster | |
|---|---|
| : System under study | Describe the Physical Twin system being studied. Include the type of system, its main components, operational domain, and key characteristics that make it suitable for digital twinning. |
| : DT services | Detail the specific services that the Digital Twin provides to users and the physical system. Include service types (monitoring, optimization, prediction, control, visualization), target users, and service capabilities. |
| : Tooling and enablers | Describe the specific tools, technologies, frameworks, and enablers used to implement the Digital Twin. Include software platforms, development tools, simulation engines, databases, and any specialized technologies with their roles and functionalities. |
| : Orchestration Cluster | |
| : Twinning time-scale | Describe the temporal aspects of the Digital Twin including synchronization frequencies between physical and digital components, time scales for different services, latency requirements, and temporal granularity needs. |
| : Multiplicities | Describe the multiplicities and hierarchical structure including multiple digital twin instances, centralized vs decentralized architectures, coordination mechanisms between twins, and scope of responsibilities for each instance. |
| Cluster | RAG Querying Keywords |
| (Purpose) | System under study: system purpose and objectives, twin description, operational context, performance objectives, stakeholder goals. DT services: monitoring and simulation, prediction and optimization, decision-support tools, control and actuation, visualization and interaction. DT enablers: technologies, tools, data acquisition pipeline, modeling and simulation tools, AI/ML components. |
| (Orchestration) | DT temporal aspects: synchronization frequencies, time scales, and temporal requirements. System multiplicities: multiple twins, distributed architectures, coordination mechanisms. DT constellation orchestration: system-wide coordination, component integration, service orchestration. External integration: data exchange with other systems, interoperability, horizontal integration patterns. |
| (Components) | DT models and data: computational models, data sources, model types, data management, model validation. Physical acting components: actuators, control mechanisms, remote control capabilities, actuation systems. Physical sensing components: sensors, measurement systems, data collection mechanisms, sensing technologies. Fidelity and validation: accuracy requirements, validation methods, uncertainty quantification, verification processes. |
| (Connectivity) | Physical-to-digital flows: sensor data transmission, communication protocols, data preprocessing, event handling. Digital-to-physical flows: command transmission, control signals, feedback mechanisms, command validation. Network infrastructure: communication protocols, network topology, bandwidth requirements, connection reliability. Deployment infrastructure: hosting platforms, computational resources, cloud/edge deployment, scalability considerations. |
| (Life-cycle) | DT lifecycle phases: development stages, deployment phases, evolution processes, maintenance activities. Engineering processes: development methodologies, quality assurance, testing approaches, version control. Decision support: insight generation, analytics capabilities, decision making processes, user interactions. Standards and compliance: industry standards, certification requirements, compliance frameworks, interoperability standards. |
| (Governance) | Data governance: data ownership policies, privacy regulations, data protection measures, consent management. Security considerations: cybersecurity measures, access control, authentication, threat mitigation, security protocols. Safety requirements: safety-critical considerations, fail-safe mechanisms, risk assessment, hazard analysis. Compliance frameworks: regulatory compliance, data protection laws, industry regulations, audit requirements. |
Digital Twins
Digital twins are virtual models synchronized with real systems to support monitoring, prediction, simulation, and decision-making.
See all 253 papers