Process-Methods-Tools-Environment (PMTE) paradigm, where the TGM prescribes the Process and Methodology, supported by the Test-bed technical infrastructure (Tools)..
The Common Information and Simulation Space allow the exchange of well-structured, informative messages.
Test-bed reference implementation: the components inside the yellow rectangle are being developed as open source tools in the DRIVER+ project.
High-level overview of the technical infrastructure needed for a Trial.
Test-bed composer's home page.
Test-bed composer: Selecting a solution.
Test-bed composer: Downloading the docker-compose.yml file.
Conceptual diagram of gateways translating messages back and forth between CIS and CSS.
Selecting a different configuration in the Admin tool.
Exonaut timeline example.
Edit a scenario, including specifying start and end time and creating checklists.
A scenario timeline is comparable to a project manager's Gantt chart.
A running scenario can be paused, and certain messages require manual confirmation.
Observer Support Tool: Left, an overview of available observation templates. Right, one of the observation templates is selected.
In the AAR, messages can be filter, inspected and made visual on the timeline.
AAR sequence diagram, showing the interaction between filtered systems.
In case no TMT is running, the Test-bed time-service GUI can also be used to start/stop/pause a Trial, as well as set the simulation speed.
Screenshot of Landoop's Kafka topics UI, which is part of our test-bed.
Screenshot of Landoop's AVRO schema registry, which is part of our test-bed.
Screenshot displaying the Replay service's GUI interface.
State diagram of the time service.