Results: As-Is data exchange table with detailed data specifications
Step 7: Definition of Future (To-Be) Use Cases – Static view of IT assets
Definition of a static IT network diagram of To-Be focus use cases (utilizing
Digital Twin) showing all relevant IT components (hardware, software), roles,
actors, and their data-input/output relations.
Methods: Design of a static use case entity-relationship-diagram
Results: Static IT network diagram: To-Be use case description
Step 8: Definition of Future (To-Be) Use Cases – Dynamic view of IT assets
Development of a workflow diagram of To-Be focus use cases (utilizing Digital
Twin) showing logical sequence of activities of roles or actors and their data
input/output relations
Methods: Design of a use case specific workflow
Results: Dynamic IT workflow diagram: To-Be use case description
Step 9: Definition of Future (To-Be) Use Cases – Data exchange view
Specification of data (e.g. data types, data attributes) exchanged by relevant
actors.
Methods: Interviews and workshops on further data concretization
Results: To-Be data exchange table with detailed data specifications
In summary, the collaboratively elaborated results of all steps of this systematic
approach provide a comprehensive and condensed basis (Big Picture, see Sect. 3.5)
for a systematic methodology from requirements engineering and data modeling to
the development of Digital Twin based software functions. Investment in infrastructure for digitalization must consider several highly ranked use cases: The return on
investment may be high, and the investment for implementing an additional use case
is usually not as significant as for establishing the infrastructure for the first use case.
Several attractive use cases can be achieved only if DT data is shared among
different stakeholders (Fig. 3).
3.3 Infrastructure Analysis
DTs are a sophisticated link between the virtual and the physical world, but their
implementation is application-specific [3]. However, the following are the minimum
requirements for the implementation:
– The digital environment (e.g., server and network structure)
– A standardized process
– Extent of automation level following the minimum requirements
– Definition of a minimum data structure for communication
– Expert, plant, machine, and product knowledge
136
R. Werner et al.
Step 7: Definition of Future (To-Be) Use Cases – Static view of IT assets
Definition of a static IT network diagram of To-Be focus use cases (utilizing
Digital Twin) showing all relevant IT components (hardware, software), roles,
actors, and their data-input/output relations.
Methods: Design of a static use case entity-relationship-diagram
Results: Static IT network diagram: To-Be use case description
Step 8: Definition of Future (To-Be) Use Cases – Dynamic view of IT assets
Development of a workflow diagram of To-Be focus use cases (utilizing Digital
Twin) showing logical sequence of activities of roles or actors and their data
input/output relations
Methods: Design of a use case specific workflow
Results: Dynamic IT workflow diagram: To-Be use case description
Step 9: Definition of Future (To-Be) Use Cases – Data exchange view
Specification of data (e.g. data types, data attributes) exchanged by relevant
actors.
Methods: Interviews and workshops on further data concretization
Results: To-Be data exchange table with detailed data specifications
In summary, the collaboratively elaborated results of all steps of this systematic
approach provide a comprehensive and condensed basis (Big Picture, see Sect. 3.5)
for a systematic methodology from requirements engineering and data modeling to
the development of Digital Twin based software functions. Investment in infrastructure for digitalization must consider several highly ranked use cases: The return on
investment may be high, and the investment for implementing an additional use case
is usually not as significant as for establishing the infrastructure for the first use case.
Several attractive use cases can be achieved only if DT data is shared among
different stakeholders (Fig. 3).
3.3 Infrastructure Analysis
DTs are a sophisticated link between the virtual and the physical world, but their
implementation is application-specific [3]. However, the following are the minimum
requirements for the implementation:
– The digital environment (e.g., server and network structure)
– A standardized process
– Extent of automation level following the minimum requirements
– Definition of a minimum data structure for communication
– Expert, plant, machine, and product knowledge
136
R. Werner et al.