Co-simulation¶

In co-simulation, the different subsystems that form a coupled problem are modeled and simulated in a distributed manner.

Version: v1 · 2026-09-28 · History
Domain-specific #: 8510
Domain group: Applied Sciences & Engineering
Origin domain: Engineering & Design (beyond software)
Subdomains: Modeling and Simulation, Multiphysics Simulation → Engineering & Design (beyond software)

Core Idea¶

Co-simulation is treated here as the recurring crossdomainmodelsstructuresrepresentations identity summarized by this source-grounded definition: In co-simulation, the different subsystems that form a coupled problem are modeled and simulated in a distributed manner. In co-simulation, the different subsystems that form a coupled problem are modeled and simulated in a distributed manner. Hence, the modeling is done on the subsystem level without having the coupled problem in mind. Furthermore, the coupled simulation is carried out by running the subsystems in a black-box manner. During the simulation, the subsystems will exchange data.

How would you explain it like I'm…

Team Pretend Machine

Imagine building a pretend car where one friend acts out the engine, another the wheels, and another the brakes. Each friend only knows their own part, and they keep calling out to each other what is happening. Put together, they act out the whole car. Co-simulation is computers doing this: each part gets its own computer model, and the models keep talking.

Simulations That Talk Together

Big machines have parts from different areas, like electronics, motors, and control software. In co-simulation, each part is modeled with its own special program, built without worrying about the whole machine. Then all the programs run together, each one like a closed box, and they pass numbers back and forth as the simulation goes. That way experts can keep using the tools they already trust for their own part, and still see how the whole system behaves.

Coupled Black-Box Simulation

Co-simulation is a way of simulating a coupled system by splitting it into subsystems that are modeled and simulated separately, in a distributed way. Each subsystem is modeled on its own terms, without the full coupled problem in mind, and runs with its own suitable solver. During the joint run, the subsystem simulators are treated as black boxes that exchange data with each other at intervals. This lets established tools from different fields be combined rather than rebuilding everything into one model. It is especially useful for checking multi-domain and cyber-physical systems, where physical parts and software interact.

Co-simulation is the joint simulation of a coupled problem in which the constituent subsystems are modeled and simulated in a distributed manner. Modeling happens at the subsystem level without the coupled problem in mind, and each subsystem runs with its own well-established tool, semantics, and suitable solver. The coupled simulation treats subsystems as black boxes: they expose inputs and outputs and exchange data during the run rather than being merged into one set of equations. This distinguishes it from monolithic simulation, where the whole system is assembled into a single model and integrated by one solver. The approach is valued for validating multi-domain and cyber-physical systems, where heterogeneous physics and software must be simulated together. A case counts as co-simulation only if the distributed, subsystem-level, black-box structure with runtime data exchange is actually present, not merely if several models are involved.

Scope of Application¶

Coupling methods. Co-simulation coupling methods can be classified into operational integration and formal integration, depending on abstraction layers.
Coupling methods. In general, operational integration is used in co-simulation for a specific problem and aims for interoperability at dynamic and technical layers (i.e. signal exchange).
Coupling methods. On the other hand, formal integration allows interoperability in semantic and syntactic level via either model coupling or simulator coupling.
Communication Patterns. The names of the first two methods are derived from the structural similarities to the numerical methods by the same name.
Communication Patterns. The reason is that the Jacobi method is easy to convert into an equivalent parallel algorithm while there are difficulties to do so for the Gauss-Seidel method.

Clarity¶

A clear use of Co-simulation names the carrier, the operative relation, and the conditions under which the source treats the identity as present. The minimal definition is In co-simulation, the different subsystems that form a coupled problem are modeled and simulated in a distributed manner.

Manages Complexity¶

Co-simulation compresses multiple crossdomainmodelsstructuresrepresentations details into a stable diagnostic relation. The source shows both the central mechanism—establishing a co-simulation framework can be a challenging and complex task, because it requires a strong interoperability among the participating elements, especially in case of multiple-formalism co-simulation.—and the practical consequence—from a dynamic and technical point of view, it is necessary to consider the synchronization techniques and communication patterns in the process.

Abstract Reasoning¶

Type the carrier. Identify the crossdomainmodelsstructuresrepresentations entities to which the claim applies.
State the relation. Use the source-grounded identity: In co-simulation, the different subsystems that form a coupled problem are modeled and simulated in a distributed manner.
Check operation and conditions. The generic layered structuration of co-simulation framework highlights the intersection of domains and the issues that need to be solved in the process of designing a co-simulation framework.
Demand recognition evidence.

Knowledge Transfer¶

Within the home domain. Knowledge about Co-simulation transfers literally when a new case preserves the same carrier type, relation, and recognition test. Co-simulation coupling methods can be classified into operational integration and formal integration, depending on abstraction layers. In general, operational integration is used in co-simulation for a specific problem and aims for interoperability at dynamic and technical layers (i.e. signal exchange). Beyond the home domain. No canonical parent is asserted for Co-simulation.

Neighborhood in Abstraction Space¶

Co-simulation sits in a sparse region of the domain-specific corpus (85^th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Computation Models & Complexity Classes (37 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08