View all solutions
Equipment/Infrastructure

Digital Twin

Creates a perfect virtual replica of physical manufacturing sites and equipment for real-time simulation and data visualization.

ISO 23247 (Manufacturing Digital Twin)
01

Are you facing these challenges?

As you pursue smart factory initiatives, digitalization of equipment and processes has emerged as a critical priority. But in reality, the following difficulties keep recurring.

Commissioning new equipment or lines takes too long

When introducing equipment or modifying a line, on-site commissioning takes weeks to months before actual operation begins. Various operating conditions must be tested one by one on physical equipment, and when unexpected issues arise, corrections and retesting are repeated. During the commissioning period, production stops and costs rise.

By the time anomalies are detected, it is already too late

When anomalies are detected in equipment, the equipment is usually on the verge of failure or quality issues have already occurred. Sensor data is being collected, but early-stage deviations from normal ranges are not captured. Sometimes too many alarms sound, causing critical alerts to be missed.

You cannot know equipment status without visiting the shop floor

To check current equipment status, you must physically visit the site. For companies operating multiple plants, there is no way to get a consolidated view of key equipment status across all locations. When problems occur during nights or holidays, response time is delayed and the situation is only assessed upon arrival.

There is plenty of sensor data but it is not being utilized

Data streams from vibration, temperature, pressure, current, and other sensors, but there is no systematic framework for analyzing this data and converting it into meaningful insights. Data accumulates, but predictions and optimizations based on that data are not happening.

The cost and complexity of digital twin adoption is a barrier to entry

Global digital twin platforms cost hundreds of thousands of dollars or more to implement and take months to deploy. Specialized development personnel are required, and integration with existing systems must be conducted as a separate project. It is difficult to be confident in the return on investment, making the adoption decision itself challenging.


02

Here is how we solve it

Reduce on-site commissioning time with virtual commissioning

When equipment and processes are implemented in a digital twin, various operating conditions can be tested in a virtual environment before operating the physical equipment.

6 types of simulation scenarios (physics-based, data-driven, hybrid, finite element analysis, computational fluid dynamics, discrete event simulation) are supported, with integration to external engines (ANSYS, COMSOL, SIMIO, FlexSim, AnyLogic, etc.) for precision simulation.

What-If analysis is possible by changing parameter sets for repeated execution and comparing results against baseline. Simulation results are linked to KPIs, enabling quantitative comparison of productivity, energy consumption, and quality impact under each condition.

Detect anomalies at the earliest stage

5 types of anomaly detection methods (statistical, machine learning-autoencoder, machine learning-Isolation Forest, rule-based, ensemble) are combined to capture subtle anomaly patterns that a single method might miss.

Alarm management is designed per the ISA-18.2 standard. Shelving (temporary suppression) and Suppression (conditional suppression) reduce unnecessary alarms, and an alarm rationalization workflow periodically reviews the appropriateness of each alarm. Chattering (frequently repeating) alarms and Nuisance (meaningless) alarms are statistically identified, creating an environment where operators can focus on truly important alerts.

Hysteresis (deadband) settings prevent repeated alarms near threshold values, and escalation rules automatically notify senior personnel if no action is taken within a specified time.

Monitor equipment status in real time from anywhere

Real-time operational data from equipment is reflected in the digital twin, enabling intuitive understanding of current equipment status on 3D visualization screens. 4 types of 3D engines are supported (Unity, Unreal Engine, WebGL, custom renderer), with 8 types of data-to-visualization mapping (color, position, size, rotation, transparency, text, gauge, animation) to visually represent sensor data.

LOD (Level of Detail) settings enable zooming from plant-wide overview down to individual component level. DTDL (Digital Twins Definition Language) v3 compatible schemas are supported, keeping the path open for Azure Digital Twins integration.

Leverage sensor data for prediction and optimization

Based on collected sensor data, 7 types of ML algorithms (linear regression, random forest, XGBoost, LSTM, GRU, Transformer, ensemble) are applied to perform 6 types of predictive analytics: remaining useful life prediction, energy consumption prediction, quality prediction, process optimization, failure prediction, and demand forecasting.

Feature Store manages feature data, and the model registry handles model version management and A/B testing. XAI (Explainable AI) functionality supports 6 explanation methods including SHAP and LIME, enabling understanding of why a model made a particular prediction.

The entire MLOps pipeline is built into the solution, enabling prediction model construction and operation without a separate data science platform.

Build digital twins with No-Code

Design tables, screens, and workflows on the canvas, and DDL, API, and UI are automatically generated. There is no need to conduct a separate development project for digital twin construction.

While global digital twin platforms take months to deploy, VEXPLOR Digital Twin can launch a basic digital twin within hours to days with just data source connection and model configuration. Simulation, predictive analytics, and 3D visualization can be progressively added as needed.


03

Global standards this solution follows

ISO 23247 -- Manufacturing Digital Twin Framework

Why does this standard matter?

While the term "digital twin" is widely used, ISO 23247 is the international standard that defines "what specific components a digital twin should have." This standard defines manufacturing digital twins as 4 sub-entities, clarifying the roles and relationships of the physical entity, virtual entity, data collection layer, and user interface. Following this framework ensures that a digital twin goes beyond simple visualization to achieve a complete loop of data collection-modeling-analysis-decision making.

How is this applied in VEXPLOR Digital Twin?

ISO 23247 Sub-EntitySystem ImplementationWhat it means for your operations
Observable Manufacturing Elements (OME)Physical equipment and assets are modeled in equipment_assets, data_tags, and data_sources tables. Includes 5-level hierarchy (plant -> process -> line -> equipment -> component), GPS location, health score, and degradation ratePhysical shop floor equipment has 1:1 digital correspondence, enabling systematic management of what data is collected from which equipment
Data Collection & Device Control (DCDC)collector_configs, collected_data, and dt_edge_devices collect data via 6 protocols (OPC-UA/MQTT/Modbus/PLC/REST/Sparkplug-B) and manage edge devicesShop floor sensor/PLC/instrument data is collected in a standardized manner, enabling unified management of equipment with different protocols in one system
Digital Twin Entity (DTE)twin_models, twin_data_mappings, and twin_sessions manage the digital twin virtual models. Includes 3D visualization (4 engine types, 8 mapping types) and DTDL v3 compatible schemasEquipment virtual models connected to real-time data enable intuitive understanding of current equipment status on screen
User EntityUsers interact with the digital twin through management screens, dashboards, and POP (shop floor) screensExecutives see the overall picture on dashboards; shop floor personnel check individual equipment status on POP screens
Cross-domain Integrationdt_cross_solution_mappings and dt_digital_thread_nodes connect data with EAM/MES/QMS/FEMS and othersThe digital twin does not exist in isolation but integrates with maintenance/production/quality/energy data for comprehensive analysis

Digital Twin Consortium (DTC) Framework

Why does this standard matter?

The Digital Twin Consortium is a digital twin industry standardization body with participation from global companies including Microsoft, Dell, Ansys, and Lendlease. The DTC framework defines digital twin components across 6 layers: Physical Entity, Virtual Entity, Connection, Analytics, Integration, and Security. While ISO 23247 is manufacturing-specific, the DTC framework is a reference architecture spanning all industries.

How is this applied in VEXPLOR Digital Twin?

DTC LayerSystem ImplementationWhat it means for your operations
Physical EntityPhysical assets modeled via equipment_assets and data_sourcesEquipment physical properties (specifications, location, status) are accurately reflected in the digital world
Virtual EntityVirtual models managed via twin_models, dt_scene_3d_instances, and dt_dtdl_schemasDigital replicas of physical equipment are implemented with real-time data and 3D visualization
Connection LayerPhysical-virtual data flow managed via collector_configs, dt_streaming_configs, and dt_edge_protocols10 industrial protocols supported for reliable data collection from diverse equipment
Analytics LayerPredictive and anomaly detection analysis performed via dt_prediction_models and dt_anomaly_detection_configsCollected data goes beyond simple monitoring to be used for prediction and optimization
Integration LayerCross-solution integration supported via dt_cross_solution_mappings and dt_digital_thread_nodesThe digital twin exchanges data with EAM, MES, QMS, FEMS, and other solutions
Security LayerSecurity managed via dt_tenant_edge_policies and network zones (IEC 62443-based)Data is isolated in multi-tenant environments with OT network security applied

IEC 62443 -- Industrial Cybersecurity

Why does this standard matter?

Digital twins connect OT (Operational Technology) and IT networks. This connection improves productivity but simultaneously increases cybersecurity risk. IEC 62443 is the international standard for Industrial Automation and Control Systems (IACS) cybersecurity, defining requirements for network zone separation, encryption, authentication, access control, and audit trails. IEC 62443 compliance is spreading as a supply chain requirement in major manufacturing industries such as automotive and semiconductor.

How is this applied in VEXPLOR Digital Twin?

IEC 62443 ElementSystem ImplementationWhat it means for your operations
Network Zone SeparationNetwork zones are modeled based on the Purdue Model from OT Level 0 (field devices) to cloud. The Network Topology Graph screen visually manages security zones and device placementOT and IT network boundaries are clearly defined, limiting the blast radius in case of security incidents
Data EncryptionTLS encryption and AES-256 encryption are applied to data source connections and edge policiesSensor data is not transmitted in plaintext, protecting against network eavesdropping
Authentication4 authentication methods can be configured for data source connections: None/Basic/Certificate/TokenAppropriate authentication methods are applied based on each data source's security level to block unauthorized access
Audit LogTag change history and digital thread change history are automatically recordedData changes can be traced by timestamp and user, enabling security audit response
Access ControlMulti-tenant data isolation is ensured via 4 tenant isolation modes (Dedicated/Shared/Namespace/VLAN)Data is completely separated even when multiple organizations use the same system

ISA-18.2 -- Alarm Management Standard

Why does this standard matter?

When too many alarms sound on the manufacturing floor, critical alerts get missed. This is called "Alarm Flood." ISA-18.2 covers the entire alarm lifecycle from design, implementation, management, monitoring, change management, to audit. Through Alarm Rationalization, the necessity and appropriateness of each alarm is periodically reviewed to maintain alarm system reliability.

How is this applied in VEXPLOR Digital Twin?

ISA-18.2 ElementSystem ImplementationWhat it means for your operations
Alarm Shelving (temporary suppression)Specific alarms can be suppressed for a defined period and automatically released when the period expiresUnnecessary alarms can be temporarily suppressed during equipment maintenance to allow focus on work
Alarm Suppression (conditional suppression)Alarms are automatically suppressed under specific conditions (e.g., equipment in normal shutdown state)Unnecessary alarms do not sound when equipment is normally shut down, reducing alarm fatigue
Alarm Rationalization WorkflowA built-in workflow periodically reviews the appropriateness of each alarmAlarms set pro forma or no longer needed are systematically cleaned up to maintain alarm system reliability
Alarm Statistical AnalysisChattering (frequently repeating), Nuisance (meaningless), and Standing (persistent) alarms are statistically identifiedData reveals which alarms sound most frequently and which are ignored without action, enabling improvement
HysteresisDeadband settings prevent repeated alarms near threshold valuesPrevents repeated alarms when temperature oscillates around a threshold
EscalationSenior personnel are automatically notified if no action is taken within a specified timePrevents important alarms from being neglected, ensuring the right personnel respond at the right time

Sparkplug B v3.0 -- IIoT Standard Protocol

Why does this standard matter?

MQTT is a lightweight messaging protocol widely used in IoT, but industrial use requires standards for topic structure, payload format, and device state management. Sparkplug B defines industrial data exchange conventions on top of MQTT, enabling standardized data exchange between heterogeneous equipment. It is an open standard managed by the Eclipse Foundation with growing adoption in the IIoT ecosystem.

How is this applied in VEXPLOR Digital Twin?

Sparkplug B MessageSystem ImplementationWhat it means for your operations
BIRTH (Device Registration)Edge devices are automatically registered when connected to the network and metadata is transmittedNew equipment is automatically recognized by the system when connected, reducing manual registration work
DEATH (Device Disconnection)Device status is automatically updated upon disconnectionEquipment communication loss is immediately detected, enabling quick identification of data collection gaps
DATA (Data Transmission)Sensor data is transmitted in a standardized payload formatData from sensors/PLCs of different manufacturers can be collected in the same format, facilitating integrated analysis
COMMAND (Command Transmission)Structure for sending commands to devices via MQTT broker is implementedProvides the foundation for future bidirectional digital twins (remote equipment control)

DTDL v3 -- Digital Twins Definition Language

Why does this standard matter?

If digital twin model definitions differ by platform, all models must be redefined from scratch during cloud migration or platform changes. DTDL v3 is a modeling language developed by Microsoft for Azure Digital Twins that defines digital twin properties, telemetry, relationships, and commands in JSON-LD format.

How is this applied in VEXPLOR Digital Twin?

DTDL v3 compatible schemas are supported, ensuring a migration path for VEXPLOR-defined digital twin models to Azure Digital Twins. If you start on-premises now and plan to expand to the cloud in the future, models can be migrated without redefinition.


04

How this differs from existing systems

Integrated data model

Most digital twin platforms have data collection, 3D visualization, simulation, predictive analytics, and alarm management as separate modules or products. VEXPLOR Digital Twin integrates these 14 areas (data collection, asset modeling, 3D visualization, simulation, predictive analytics, anomaly detection, edge computing, protocol management, event processing, alarm management, digital thread, network security, energy management, XR/AR/VR) into a single solution with 62 tables.

There is no need to spend time and cost on data linkage between distributed modules -- everything operates on a single data model from the start.

Multi-protocol support for industrial standards

All core protocols actually used on manufacturing floors are supported: OPC-UA, MQTT, Modbus, PLC drivers, REST API, database connections, and Sparkplug B. Three data collection modes (polling, subscription, event trigger) and tag-level data preprocessing including scaling, deadband, and interpolation are available.

Edge computing framework

A complete management framework for edge device registration, monitoring, software deployment, and rollback is provided. Store & Forward functionality ensures no data loss during network outages (4 buffer strategies, 5 compression methods), and OTA (Over-The-Air) deployment workflows enable remote edge software updates.

Digital thread

Across the entire equipment lifecycle (design -> manufacturing -> installation -> commissioning -> operation -> maintenance -> modification -> decommissioning -> disposal), data from 14 source systems (CAD, PLM, ERP, MES, CMMS, IoT, SCADA, QMS, SPC, DCS, Historian, BMS, FEMS, SCM) is connected. With 8 link types and change management/impact analysis capabilities, the impact of changes in one system on other systems can be traced.

Implementation cost and time

Global digital twin platforms (Siemens MindSphere, PTC ThingWorx, etc.) cost hundreds of thousands of dollars in licensing alone and take months to deploy. VEXPLOR Digital Twin reduces deployment time to hours or days with a No-Code approach and significantly lowers licensing costs compared to alternatives.


05

How does it compare to global solutions?

The digital twin market has global platforms including Siemens MindSphere/Xcelerator, PTC ThingWorx, Azure Digital Twins, and AWS IoT TwinMaker. The table below compares each platform's approach and VEXPLOR's coverage across key areas.

Comparison by functional area

Functional AreaSiemens MindSphere/XceleratorPTC ThingWorxAzure Digital TwinsAWS IoT TwinMakerVEXPLOR DTWhat it means for you
Data Collection (Protocols)10+150+ (Kepware)Depends on Azure IoT HubDepends on AWS IoT Core7 core protocols (OPC-UA/MQTT/Modbus/PLC/REST/DB/Sparkplug)All core manufacturing protocols are supported. Cannot match Kepware's 150+ drivers, but focuses on the most frequently used protocols in practice
Edge ComputingIndustrial EdgeThingWorx KepwareAzure IoT EdgeAWS GreengrassEdge device/OTA deployment/Store&Forward/protocol managementComplete edge management framework from device registration through OTA deployment and automatic rollback
3D VisualizationNX + TeamcenterVuforia/Creo3D ScenesMatterport/TwinMaker SceneUnity/Unreal/WebGL + DTDL v3 compatible4 3D engine types and 8 mapping types supported. DTDL v3 compatibility keeps the path open for Azure Digital Twins integration
SimulationSimcenter (proprietary engine)LimitedLimitedNot supported6 scenario types + 7 external engine integrations (ANSYS/COMSOL/SIMIO/FlexSim/AnyLogic, etc.)Siemens Simcenter has a strong proprietary engine, but VEXPLOR integrates with 7 external engines for broader selection
Predictive Analytics/MLMindSphere AnalyticsThingWorx AnalyticsAzure ML (separate service)SageMaker (separate service)7 ML algorithms + Feature Store + Model Registry + A/B Testing + XAI (SHAP/LIME and 4 others)The entire MLOps pipeline is built into the solution. Azure ML and SageMaker require separate service subscriptions
Alarm ManagementISA-18.2 compliantBasic alarmsEvent GridIoT EventsISA-18.2 Shelving/Suppression + rationalization workflow + chattering/nuisance statisticsAlarm management depth matches Siemens level, with rationalization workflow and statistical analysis as differentiators
Digital ThreadTeamcenter + MendixThingWorx NavigateAzure Digital TwinsNot supported14 source systems + 9-stage lifecycle + change management/impact analysisEquipment data from design through disposal is connected in a single thread across the full lifecycle
No-Code/Low-CodeMendix (separate product)ThingWorx ComposerNot supportedNot supportedCanvas-based full No-CodeDDL, API, and UI are automatically generated. Mendix and Composer are separate products at separate cost, but VEXPLOR has this built in

Quantitative comparison

MetricSiemensPTCAzure DTAWS TwinMakerVEXPLOR DTWhat it means for you
Table/Entity count100+ (distributed)50+DTDL model-basedScene-based62 (integrated)14 areas integrated in a single data model with no inter-module linkage costs
Protocol support count10+150+Depends on Azure IoTDepends on AWS IoT10 (including edge protocols)Focuses on core industrial protocols. Separate gateways may be needed for environments with many specialized legacy equipment
Predefined workflowsCustom configurationCustom configurationLogic AppsStep Functions10 predefinedKey processes from equipment monitoring to event handling are predefined, reducing deployment time
Simulation engine integrationSimcenter (proprietary)LimitedLimitedNot supported7 external enginesANSYS, COMSOL, SIMIO, and other simulation tools already in use at your company can be integrated
Built-in MLOpsMindSphere AnalyticsThingWorx MLAzure ML (separate)SageMaker (separate)Feature Store + Registry + XAI built inPrediction models can be built and operated without subscribing to a separate data science platform
Deployment timeMonthsWeeks to monthsWeeksWeeksHours to days (No-Code)Start with key equipment without a large initial project and progressively expand
Price levelVery highHighMedium (usage-based)Medium (usage-based)Low (license)Small and mid-sized manufacturers can overcome the digital twin adoption barrier

Where VEXPLOR Digital Twin is particularly strong

  • No-Code Digital Twin: Design DT solutions on the canvas without coding and auto-generate DDL/API/UI. Deployment time reduced from months to hours or days.
  • 62-table integrated data model: Covers 14 areas from data collection to XR in a single solution. Competitors typically distribute across 3-5 modules.
  • Full-stack MLOps built in: Feature Store, model registry, A/B testing, and XAI (SHAP/LIME and 4 others) are included in the solution, enabling operation without a separate ML platform.
  • ISA-18.2 alarm rationalization: Alarm Shelving/Suppression + rationalization workflow + chattering/nuisance statistics represent the standard for manufacturing alarm management.
  • DTDL v3 + Sparkplug B v3.0: Native support for Azure Digital Twins compatible schemas and IIoT standard protocols secures the cloud migration path.
  • Cross-solution mapping: Flexible integration with EAM/MES/QMS/FEMS and others through a generic mapping table.

Honestly stated weaknesses

Areas requiring enhancement compared to global platforms exist.

  • Protocol diversity: Cannot match PTC ThingWorx Kepware's 150+ drivers. Core protocols (OPC-UA, MQTT, Modbus, PROFINET, EtherNet/IP) are covered, but specialized legacy equipment drivers require separate gateways.
  • Device Control (command transmission): Sensor data collection (read) is complete, but the write layer for sending commands to equipment is not explicitly modeled. Planned for future addition for bidirectional digital twins.
  • Time-series DB native integration: No direct integration with TimescaleDB, InfluxDB, etc. yet, so large-scale sensor data environments rely on historian connections.
  • Edge-level ML inference: ML inference is performed server-side, which may be limiting in environments sensitive to network latency.
  • Co-Simulation: Multi-model simultaneous execution (FMU/FMI standard) is not yet supported.
  • XR/AR/VR maturity: Advanced XR features such as AR work instructions and Remote Assistance are at basic framework level, with enhancement planned.
  • Network security depth: IEC 62443 zone-based topology is implemented, but device-level granular security policies and Zero-Trust models have not yet been applied.

06

Expected benefits after implementation

Reduced commissioning time

Pre-testing and optimizing operating conditions in a virtual environment reduces trial and error during actual commissioning. The impact of parameter changes can be verified through simulation, reducing the number of repeated tests on the shop floor.

Early anomaly detection

Multiple anomaly detection algorithms continuously analyze sensor data to capture anomalies before they develop into failures or quality issues. ISA-18.2-based alarm management enables focus on meaningful alerts, improving response accuracy.

Reduced response time through remote monitoring

Real-time remote visibility of equipment status enables situation assessment and response preparation before dispatching to the site. Night/holiday emergency response time is reduced, and integrated monitoring of key equipment across multiple plants becomes possible.

Data-driven decision making

When sensor data connects through predictive analytics and simulation results, major decisions such as equipment replacement, process changes, and line expansion can be made with data-backed evidence. XAI capabilities enable understanding of AI model reasoning, supporting trustworthy decision support.

Progressive expansion

With a No-Code foundation, start by monitoring a few key pieces of equipment and progressively add simulation, predictive analytics, and 3D visualization. A phased expansion approach is possible -- confirming results without large upfront investment.


07

Solution configuration summary

ComponentScaleDescription
Data Model62 tables14 areas including data collection, asset modeling, 3D visualization, simulation, predictive analytics
Workflows10Equipment monitoring, anomaly response, alarm rationalization, OTA deployment, event processing, etc.
Protocol Support10 typesOPC-UA, MQTT, Modbus, PLC, REST, DB, Sparkplug B, etc.
Simulation Engine Integration7 typesANSYS, COMSOL, SIMIO, FlexSim, AnyLogic, OpenFOAM, Custom
ML Algorithms7 typesLinear regression, Random Forest, XGBoost, LSTM, GRU, Transformer, Ensemble
Global Standards4 built inISO 23247, IEC 62443, ISA-18.2, Sparkplug B v3.0

Features not provided in the current version

For transparent information, the limitations of the current version are also shared.

  • Device Control (command transmission): Sensor data collection (read) is complete, but the write layer for sending commands to equipment is not yet explicitly modeled. Planned for future addition based on OPC-UA PubSub or MQTT v5.
  • Time-series database direct integration: Native integration with TimescaleDB, InfluxDB, and other time-series databases is not yet provided. Currently addressed through historian connections.
  • Co-Simulation (multi-model simultaneous execution): Current simulation supports single model execution only. FMU/FMI standard-based Co-Simulation is included in the development plan.
  • Edge-level ML inference: ML inference is performed server-side; real-time ML inference on edge devices is planned for future support.
  • XR/AR/VR maturity: Advanced XR features such as AR work instructions and Remote Assistance are at basic framework level, with enhancement planned.

08

Integration with other solutions

VEXPLOR Digital Twin integrates flexibly with other solutions through cross-solution mapping tables.

  • EAM Integration: Connects real-time equipment status data with maintenance history for comprehensive equipment health assessment within the digital twin. Used to improve predictive maintenance (PdM) model accuracy.
  • MES Integration: Connects production process data with the digital twin to enable process optimization simulation and real-time process monitoring.
  • FEMS Integration: Reflects energy consumption data in the digital twin for energy simulation and equipment energy efficiency analysis.
  • QMS Integration: Combines quality data and process data in the digital twin for quality anomaly root cause tracing and process condition optimization.
  • SCM Integration: Integrates supply chain data into the digital twin to simulate the impact of supply chain changes on production in advance.

Full lifecycle connection through digital thread

Through the digital thread capability, data from the equipment design phase (CAD/PLM) through the operational phase (MES/SCADA), maintenance phase (CMMS/EAM), and quality management (QMS/SPC) is connected in a single thread across the full lifecycle. Changes at one stage can be traced for their impact on other stages, ensuring data continuity across the entire equipment lifecycle.

Try it yourself

Apply the Digital Twin template on the canvas, and data models to screens are auto-generated.

VEXPLOR — Install an OS in Your Factory | Manufacturing AI Operating System