Fact Sheet: Open Simulation Interface (OSI)

PDF Download


Short description/
Transmitted information
  • Open Services for Lifecycle Collaboration (OSLC) is a set of specifications that enable integration of software development. It has evolved, and continues to evolve, to areas such as Application Lifecycle Management (ALM), Product lifecycle Management (PLM), IT Operations and more. 
Normative documents
Version / Release state
  • Version 3.0
Release date
  • August 26, 20021
Application scope
  • Software and Systems Engineering
  • Provide uniform access to heterogeneous data sources without vendor dependency

  • Enable technological, syntactical and semantic interoperability

  • Enable interlinking of data artefacts of different types, disciplines and along the product life cycle

  • Integrate user interfaces from different tools (e.g. delegated UIs)

  • Support generic engineering processes like cross-tool configuration & change management

Promoting bodies
  • prostep ivip Association
  • OSLC
  • ASAM
  • OMG
  • CRYSTAL, CP-SETIS (Europe)
  • OASIS Technical Committees

  • Lightweight standard for tool interoperability

  • Minimalistic specification

IT Standard classification
  • open Specification
Data format
  • RDF, http
Additional available resources
Relevant prostep ivip project groups

Positioning of OSI in V-Model


  • The Open Simulation Interface (OSI) defines an interface for the connection between the simulation environment and the automated driving functions in virtual scenarios.
  • Version 3.1.2 released Jan. 2019 of OSI was published as an Open Source Project on Github and was transferred to the ASAM association. The current version from ASAM is 3.2.0.
  • OSI uses the message format by Google's protocol buffers for structuring data
  • One message for the simulation environment interface (osi::GroundTruth), which describe the simulated objects in a global coordinate system
  • OSI since V3.0 distinguishes between Sensor View (osi::SensorView) and Sensor Data (osi::SensorData) as input and output of a sensor
  • Application areas are o automated and autonomous driving irtual scenarios based testing o sensor and environment simulation
  • Sensor data and ISO 23150 are harmonized. ISO 23150 is the standard for sensor output
  • Actual developments standardise e.g. commands for the control of further traffic participants within traffic scenarios (osi::TrafficCommand and osi::TrafficUpdate)

Relevance and Benefit for MBSE

Interoperability between Environmental Models, Scenarios, Systems under Test (SUT), and other Traffic Participants within simulations during runtime

Risks and Impediments

  • Naming convention: always talk about Open Simulation Interface, the abbreviation OSI is already used for the ISO 7-layer-model of interprocess communication
  • many stakeholders with different requirements
  • dependance on protocol buffers which don't guarantee performance in different programming languages and in all application areas