SMP2 Developments in EuroSim
Robert de Vries
(1)
, Jeroen Moelands
(2)
(1)
Dutch Space B.V.
Mendelweg 30
2333 CS Leiden
The Netherlands
r.de.vries@dutchspace.nl
(2)
National Aerospace Laboratory NLR
Anthony Fokkerweg 2
1059 CM Amsterdam
The Netherlands
moelands@nlr.nl
INTRODUCTION
The Simulation Model Portability (SMP) standard is ESA’s standard for the interface between simulation models and
simulator infrastructures. The purpose of the standard is to promote portability of models among different simulation
environments and operating systems, and to promote the reuse of simulation models. SMP1 [1], the first version of the
standard, is still supported by EuroSim.
SMP2 [2] is the successor of SMP1. SMP2 is a complete revision of the standard, adopting state-of-the-art techniques
like component-based design and model driven architecture, and has a much wider impact on model and simulator
development than its predecessor. The way of working with this standard and its complexity demand tools for
specification, development, and integration of SMP2 models. EuroSim incorporates a set of tools to accomplish these
tasks.
A further iteration of the SMP standard is currently in the final draft stage as European Cooperation for Space
Standardization (ECSS) standard E-40-07. The EuroSim consortium has been involved in the process of specification of
the draft ECSS standard, like it was in SMP1 and SMP2 specification.
The simulation modelling platform (SMP) is a new standard invented from scratch. It needs to be tested in the field on a
real test bench. The EuroSim simulation infrastructure needs to be updated to comply with this standard. It can then be
used to verify that the new standard is suitable for the most demanding applications.
EUROSIM
EuroSim is a proven platform that contains a set of integrated tools to support all phases of a real-time simulation
project [3]. Model code is imported into the EuroSim environment using the Model Editor. Model code is scheduled
with the Schedule Editor. Simulators are executed using the Simulation Controller. These are just some key examples of
the dozens of tools that are available. Commonly used functionality of EuroSim is made available through user-friendly
graphical user interfaces. Most of EuroSim’s customers start modeling in MATLAB/Simulink. NLR’s tool MOSAIC
(Model Oriented Software Automatic Interface Converter) [4] allows users to automatically transfer
MATLAB/Simulink models to the EuroSim environment.
EUROSIM SMP2 IMPLEMENTATION
Generally, an SMP2 simulator is specified using the following types of XML files defined in the SMP2 Metamodel. The
Catalogue offers a variety of mechanisms to specify all kinds of data types in an object-oriented fashion, including
simulation models. A Package file represents, at an abstract level, a set of specific implementations of simulation
models that are specified in Catalogues. It is possible to develop multiple implementations of the same simulation
model using different Packages. The Assembly is a file type that specifies a simulator in the form of a hierarchy of
model instances, referring to their specification (in a Catalogue) and implementation (in a Package). It also contains
links to define their interaction with the other instances. Finally, the Schedule file offers a way to specify scheduling of
model instances in an assembly. SMP2’s C++ Mapping prescribes a mapping from type specifications in a Catalogue to
equivalent specifications in their language of implementation (C++). Finally, the interface between the SMP2 models
and the SMP2-compliant simulation environment is defined by the SMP2 Component Model.