Search

Digital Twin of the Organization (DTO) is a relatively new concept that emerged to help managers have a full understanding of their organization and realize their objectives. Indeed, DTO enables connecting all the elements of an organization virtually by providing monitoring, optimization, prediction, and other capabilities through continuous simulations. Creating a flexible and evolvable DTO that covers and supports the organization's business strategies is a complex and time-consuming task that requires engineering best practices. In this context, this paper presents and evaluates the EA Blueprint Pattern, which serves as an architectural reference for the development of a DTO by allowing for mapping well-known Enterprise Architecture concepts into software components defining the DTO software architecture. The evaluation is carried on by showing how to use the pattern for creating the DTO for a given organization. Then, a thorough discussion is conducted to analyze how the developed DTO should evolve to deal with vertical and horizontal integration. The lessons learned highlight the strengths and weaknesses along with practical implications for organizations that are eager to develop their DTO according to the EA Blueprint Pattern.

Digital Twin of the Organization (DTO) is a relatively new concept that emerged to help managers have a full understanding of their organization and realize their objectives. Indeed, DTO enables connecting all the elements of an organization virtually by providing monitoring, optimization, prediction, and other capabilities through continuous simulations. Creating a flexible and evolvable DTO that covers and supports the organization's business strategies is a complex and time-consuming task that requires engineering best practices. In this context, this paper presents and evaluates the EA Blueprint Pattern, which serves as an architectural reference for the development of a DTO by allowing for mapping well-known Enterprise Architecture concepts into software components defining the DTO software architecture. The evaluation is carried on by showing how to use the pattern for creating the DTO for a given organization. Then, a thorough discussion is conducted to analyze how the developed DTO should evolve to deal with vertical and horizontal integration. The lessons learned highlight the strengths and weaknesses along with practical implications for organizations that are eager to develop their DTO according to the EA Blueprint Pattern.

Digital Twin of the Organization (DTO) is a relatively new concept that emerged to help managers have a full understanding of their organization and realize their objectives. Indeed, DTO enables connecting all the elements of an organization virtually by providing monitoring, optimization, prediction, and other capabilities through continuous simulations. Creating a flexible and evolvable DTO that covers and supports the organization's business strategies is a complex and time-consuming task that requires engineering best practices. In this context, this paper presents and evaluates the EA Blueprint Pattern, which serves as an architectural reference for the development of a DTO by allowing for mapping well-known Enterprise Architecture concepts into software components defining the DTO software architecture. The evaluation is carried on by showing how to use the pattern for creating the DTO for a given organization. Then, a thorough discussion is conducted to analyze how the developed DTO should evolve to deal with vertical and horizontal integration. The lessons learned highlight the strengths and weaknesses along with practical implications for organizations that are eager to develop their DTO according to the EA Blueprint Pattern.

Digital Twin of the Organization (DTO) is a relatively new concept that emerged to help managers have a full understanding of their organization and realize their objectives. Indeed, DTO enables connecting all the elements of an organization virtually by providing monitoring, optimization, prediction, and other capabilities through continuous simulations. Creating a flexible and evolvable DTO that covers and supports the organization's business strategies is a complex and time-consuming task that requires engineering best practices. In this context, this paper presents and evaluates the EA Blueprint Pattern, which serves as an architectural reference for the development of a DTO by allowing for mapping well-known Enterprise Architecture concepts into software components defining the DTO software architecture. The evaluation is carried on by showing how to use the pattern for creating the DTO for a given organization. Then, a thorough discussion is conducted to analyze how the developed DTO should evolve to deal with vertical and horizontal integration. The lessons learned highlight the strengths and weaknesses along with practical implications for organizations that are eager to develop their DTO according to the EA Blueprint Pattern.

Digital Twin of the Organization (DTO) is a relatively new concept that emerged to help managers have a full understanding of their organization and realize their objectives. Indeed, DTO enables connecting all the elements of an organization virtually by providing monitoring, optimization, prediction, and other capabilities through continuous simulations. Creating a flexible and evolvable DTO that covers and supports the organization's business strategies is a complex and time-consuming task that requires engineering best practices. In this context, this paper presents and evaluates the EA Blueprint Pattern, which serves as an architectural reference for the development of a DTO by allowing for mapping well-known Enterprise Architecture concepts into software components defining the DTO software architecture. The evaluation is carried on by showing how to use the pattern for creating the DTO for a given organization. Then, a thorough discussion is conducted to analyze how the developed DTO should evolve to deal with vertical and horizontal integration. The lessons learned highlight the strengths and weaknesses along with practical implications for organizations that are eager to develop their DTO according to the EA Blueprint Pattern.