As machines and technical systems become more complex, engineering teams increasingly rely on simulations and tests distributed across different tools and platforms. Yet connecting those environments can require substantial, time-consuming integration work. The Distributed Co-Simulation Protocol (DCP), developed through the ACOSAR project, addresses this challenge with a non-proprietary approach to communication and control between simulation and test systems.
Although ACOSAR focused primarily on automotive engineering, the underlying problem is relevant wherever teams need to coordinate models, real-time systems and test equipment. DCP provides a common protocol specification, while a related integration methodology helps teams plan how components fit together in mixed virtual and physical validation environments.
Why distributed co-simulation needs a common approach
Simulation is an established part of developing technical devices and machines. Increasing computing power and memory have made it possible to run detailed models across a range of engineering domains. Co-simulation extends this work by allowing multiple simulation components or systems to participate in a shared setup.
The difficulty is that tools and infrastructure may use different ways to exchange data and coordinate their operation. Without a standardised method for integrating distributed simulation and test environments, each connection can demand bespoke engineering effort. This can slow modular system integration and consume time that teams could otherwise spend on development and validation.
ACOSAR set out to create a protocol for exchanging data and controlling co-simulation, along with a methodology for integration. Rather than replacing the underlying communications infrastructure, DCP is designed to work on top of existing transport protocols. This separates the protocol’s co-simulation functions from the transport mechanisms used to carry communications.
What the Distributed Co-Simulation Protocol provides
DCP formally describes how simulation tools and testbeds can be integrated in a distributed setup. A shared specification gives implementers a common basis for connecting systems and exchanging information about their behaviour. The intent is to make integrations more systematic and less dependent on individually designed interfaces.
The ACOSAR work went beyond defining the protocol. It also produced a reference implementation and a test suite intended to verify DCP slave implementations against the specification. This kind of conformance testing can help identify implementation issues before components are brought together in a larger integration effort.
ACOSAR reported that the test suite enables testing across different implementations and supports front-loaded testing—that is, checking compliance earlier in the development and integration process. Finding discrepancies sooner can reduce the risk of discovering them only after multiple systems have been assembled. The suite is therefore an important complement to the protocol itself, not simply an additional technical document.
Connecting virtual models with real-time systems
A key outcome of ACOSAR was an integration methodology for combining simulation tools with real-time systems to create mixed virtual and real validation environments. Such setups can involve software models alongside physical or real-time components. Bringing them together requires decisions about system configuration, interfaces and the way components are coupled.
The project’s methodology handbook provides a compact overview of development processes, requirements and interfaces, as well as system-integration design considerations. It also describes the use of model-based systems engineering (MBSE) techniques. In this context, MBSE can support the derivation of coupling configurations and enable system configurations to be generated more automatically.
For engineering teams, the practical value of a defined methodology is consistency: integration becomes a planned part of system development rather than a series of disconnected interface tasks. DCP supplies the communication specification; the methodology helps teams address how a complete co-simulation environment is structured.
Potential impact on engineering effort
The automotive sector provided the main application context for ACOSAR. Vehicle functions increasingly involve multiple systems and subsystems, while development budgets face constraints. In this environment, reducing repeated integration work can have meaningful implications for engineering schedules and resources.
Based on project partners’ and use-case providers’ estimates, an automotive original equipment manufacturer could potentially save 13,000 hours of integration effort over the following five years. The project associated this estimate with an equivalent value of €5–7 million. These figures are a project estimate, not a guaranteed outcome for every organisation; actual results depend on how DCP and related practices are adopted in a particular environment.
ACOSAR also reported interest in DCP beyond automotive, including from semiconductor, aerospace and maritime companies, as well as organisations in Europe, the United States and Asia. This points to a broader potential application: any sector working through interoperability challenges among simulation tools, real-time systems and test equipment may have reason to evaluate a common integration approach.
Standardisation and adoption
To support continued development beyond the project, DCP was taken forward by the Modelica Association. The association accepted the protocol as a Modelica Association Project, and DCP specification 1.0 was released as a Modelica Association Standard in March 2019. The specification and accompanying materials are described as non-proprietary and vendor-neutral, with relevant project outputs made available under open-source licensing.
ACOSAR also reported a growing community around DCP and a range of prototype implementations. These are development-stage outcomes rather than evidence that every tool or test environment is already interoperable. Teams considering adoption should assess the available implementations, their required interfaces and the role of DCP within their existing integration architecture.
Practical considerations for engineering teams
For system integrators and technical decision-makers, DCP is most relevant when distributed co-simulation creates recurring connection and coordination challenges. An evaluation can begin with a few practical questions:
- Which simulation tools, real-time systems or testbeds need to exchange information?
- Where are custom interfaces or repeated integration tasks creating effort?
- How will implementations be checked against the DCP specification?
- What system configurations and coupling decisions should be addressed through an MBSE-supported process?
Answering these questions helps distinguish the protocol’s role from broader integration responsibilities. DCP specifies a common approach to communication and control; it does not remove the need to design the overall system configuration or determine how the participating components should be used.
Conclusion
The Distributed Co-Simulation Protocol offers engineering organisations a standardised foundation for integrating distributed simulation and test environments. Combined with a reference implementation, a conformance-focused test suite and an MBSE-supported integration methodology, it can help teams approach system connections more systematically and identify compatibility issues earlier. For organisations managing complex validation setups, the practical implication is to treat interoperability as an architectural and process concern—not just a collection of individual tool connections.