Component Twin View

It models the architecture of a DT software system by specifying its components and their connectors.
Artifacts attached in the blue box at the end of the page.
Component Diagram

CTV: UML Component Diagram.

ID Name Description Azure Digital Twins Eclipse Ditto FIWARE
dtc1PhysicalTwinA real-world asset to be replicated by the Digital Twin.
dtc2DataProviderAn intermediary facilitating the transmission of raw data from the physical to the Digital Twin.
dtc3DataReceiverA receiver ensuring feedback, updates, or commands from the Digital Twin reach the physical twin.
dtc4P2DAdapterA converter that translates physical system data into formats usable by the Digital Twin.Event RouteConnectivity APIIoT Agent
dtc5D2PAdapterA translator that transforms Digital Twin outputs into formats usable by the physical twin.Event GridConnectivity APIIoT Agent
dtc6DataProcessorA processing unit that filters and organizes raw data, preparing it for integration into the Digital Twin.Azure Event HubThing ManagementContext Broker
dtc7StorageManagerA component that organizes and manages a shared data repository for efficient storage and retrieval.Azure Event HubThing ManagementContext Broker
dtc8DataManagerA centralized component ensuring data consistency and availability, aggregating functionalities of the data processor and storage manager.Azure Event HubThing ManagementQuantumLeap
dtc9SharedStorageA data accumulator, responsible for storing heterogeneous data from both physical and digital twins.Azure Data LakeMongoDBTimescaleDB
dtc10ShadowManagerResponsible for creating, managing, and overseeing the lifecycle of multiple digital shadows.Model ManagementDitto ManagementContext Broker
dtc11ModelManagerA component responsible for creating and managing multiple digital models to simulate different aspects.
dtc12ModelEngineA processing unit of digital models, responsible for executing simulations and generating results based on the modeled scenarios.
dtc13SimulatorA virtualizer of real-world systems, responsible for simulating the behavior of the physical system under various conditions.
dtc14TwinManagerAn orchestrator synchronizing the functionalities of shadow and model managers with the service-related components for cohesive DT operations.Twin ManagementDitto ManagementContext Broker
dtc15StateMonitorA monitoring component, responsible for collecting and forwarding real/simulated states to other components for further analysis or action.Azure Stream AnalyticsEvent HandlingFIWARE Cosmos
dtc16DeviationDetectorA comparison unit, responsible for identifying deviations by comparing real or predicted states with expected states to detect any deviation.Multivariate Detection toolkitFIWARE Perseo
dtc17PredictorA forecasting component, responsible for using current and historical data to anticipate potential future states of the physical system.Azure ML and DLFIWARE Cosmos
dtc18AnalyzerA detailed analytical component, responsible for analyzing real, predicted, and simulated states to extract meaningful insights.Azure Stream AnalyticsFIWARE Perseo and Cosmos
dtc19SolutionFinderA component responsible for finding the best set of actions to return the system to a desired state after deviation detection.
dtc20ScenarioGeneratorA generator designed to create diverse scenarios, facilitating the preparation and execution of multiple simulations.
dtc21PlannerA planning unit, responsible for developing a solution plan to restore the system to a desired state when deviations or anomalies are detected.
dtc22FeedbackExecutorA 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).