CTV: UML Component Diagram.
ID | Name | Description | Azure Digital Twins | Eclipse Ditto | FIWARE |
---|---|---|---|---|---|
dtc1 | PhysicalTwin | A real-world asset to be replicated by the Digital Twin. | ❌ | ❌ | ❌ |
dtc2 | DataProvider | An intermediary facilitating the transmission of raw data from the physical to the Digital Twin. | ❌ | ❌ | ❌ |
dtc3 | DataReceiver | A receiver ensuring feedback, updates, or commands from the Digital Twin reach the physical twin. | ❌ | ❌ | ❌ |
dtc4 | P2DAdapter | A converter that translates physical system data into formats usable by the Digital Twin. | Event Route | Connectivity API | IoT Agent |
dtc5 | D2PAdapter | A translator that transforms Digital Twin outputs into formats usable by the physical twin. | Event Grid | Connectivity API | IoT Agent |
dtc6 | DataProcessor | A processing unit that filters and organizes raw data, preparing it for integration into the Digital Twin. | Azure Event Hub | Thing Management | Context Broker |
dtc7 | StorageManager | A component that organizes and manages a shared data repository for efficient storage and retrieval. | Azure Event Hub | Thing Management | Context Broker |
dtc8 | DataManager | A centralized component ensuring data consistency and availability, aggregating functionalities of the data processor and storage manager. | Azure Event Hub | Thing Management | QuantumLeap |
dtc9 | SharedStorage | A data accumulator, responsible for storing heterogeneous data from both physical and digital twins. | Azure Data Lake | MongoDB | TimescaleDB |
dtc10 | ShadowManager | Responsible for creating, managing, and overseeing the lifecycle of multiple digital shadows. | Model Management | Ditto Management | Context Broker |
dtc11 | ModelManager | A component responsible for creating and managing multiple digital models to simulate different aspects. | ❌ | ❌ | ❌ |
dtc12 | ModelEngine | A processing unit of digital models, responsible for executing simulations and generating results based on the modeled scenarios. | ❌ | ❌ | ❌ |
dtc13 | Simulator | A virtualizer of real-world systems, responsible for simulating the behavior of the physical system under various conditions. | ❌ | ❌ | ❌ |
dtc14 | TwinManager | An orchestrator synchronizing the functionalities of shadow and model managers with the service-related components for cohesive DT operations. | Twin Management | Ditto Management | Context Broker |
dtc15 | StateMonitor | A monitoring component, responsible for collecting and forwarding real/simulated states to other components for further analysis or action. | Azure Stream Analytics | Event Handling | FIWARE Cosmos |
dtc16 | DeviationDetector | A comparison unit, responsible for identifying deviations by comparing real or predicted states with expected states to detect any deviation. | Multivariate Detection toolkit | ❌ | FIWARE Perseo |
dtc17 | Predictor | A forecasting component, responsible for using current and historical data to anticipate potential future states of the physical system. | Azure ML and DL | ❌ | FIWARE Cosmos |
dtc18 | Analyzer | A detailed analytical component, responsible for analyzing real, predicted, and simulated states to extract meaningful insights. | Azure Stream Analytics | ∼ | FIWARE Perseo and Cosmos |
dtc19 | SolutionFinder | A component responsible for finding the best set of actions to return the system to a desired state after deviation detection. | ❌ | ❌ | ❌ |
dtc20 | ScenarioGenerator | A generator designed to create diverse scenarios, facilitating the preparation and execution of multiple simulations. | ❌ | ❌ | ❌ |
dtc21 | Planner | A planning unit, responsible for developing a solution plan to restore the system to a desired state when deviations or anomalies are detected. | ❌ | ❌ | ❌ |
dtc22 | FeedbackExecutor | A generator of alerts or actionable instructions into the physical system. | ❌ | ❌ | ❌ |
UML Component Diagram of TwinArch's component view is available in the twinarch.vpp file, which can be downloaded and opened using the Visual Paradigm modeling tool (version 16.2).