• Rapid and systematic derivation, investigation and optimization of distributed system and system-of-systems models
  • Highest performing, scalable, multi-core simulation engine in the world
  • Enabled the empirical research that first demonstrated that V2V DSRC communication, in its current form, is insufficient to guarantee the safety of vehicles in traffic.

Integral to the design of the ESSE System Workbench for modelling and simulation of networked, real-time systems and systems-of-systems was that it be able to incorporate:

  • ANY MODEL - discrete or continuous and of various fidelities
  • ANY SIMULATOR - discrete or continuous
  • ANY TOOLSET - compilers, editors, debuggers, monitors, optimizers, analyzers

EST Information Brief

Home > Technology > EST Simulation Technology > Modelling and Simulation Features and User Benefits

Modelling and Simulation Features and User Benefits

EST has designed its modelling, simulation and supporting technologies with the features and benefits necessary to service a broad spectrum of people engaged in the engineering of real-time systems and systems-of-systems, including:

Provides, for the first time, a single simulation technology and modeling environment that can be used to model and simulate systems from the simple to the most complex (e.g. the real-time control system of many cars cooperating) that preserves accuracy, is scalable, and guarantees simulation performance near to the maximum theoretically possible.

Incorporates all levels of models - from abstract ODE models to operational models, from many 3rd party vendors, in the same simulation. Preserves your investment in existing models and tools by enabling them to be used with the EST simulation technology.

Concurrent design and verification of systems - for the first time, the ability to verify the complex control and plant structures of systems and systems-of-systems as models against their executable specifications during the design stage and prior to commitment to their physical realization.

Supports the complete engineering cycle - from executable specification, architecture, optimization, detailed design, hardware and software development and debugging and validation. Verification is performed concurrently with models created in each stage of the engineering cycle, beyond executable specification, being directly compared with the executable specification.

Enables, for the first time, the optimization of the control architecture of systems and systems-of-systems.

Who Should Use It?

System Architects – to (a) derive the set of Executable Specifications from the Requirements of a system or system-of-systems (SoS) that are correct in function and timing; (b) demonstrate that the executable specifications are consistent with the system’s Requirements; (c) create various equivalent forms that reflect partitionings made according to Function (control, plant), Composition (hierarchy, polyarchy (parallel)) and Communication (function, message); (d) investigate the aggregate architectural space formed by elaborating the parameters – as though they are independent dimensions - of each structurally elaborated system or SoS; (e) find those feasible architectures that meet the constraints imposed by objective functions defined also in the Requirements; (f) choose the best of the feasible architectures as candidates for realization, and (g) verify that the candidate architectures are equivalent in function and timing to their executable specifications.

System Engineers – to (a) take the verified candidate architectures and map them via physical modelling technologies (mechanical, electronic, software) to proximal-physical models – having separated control and plant - with idealized network connections; (b) verify that the proximal physical models are equivalent in function and timing to their executable specifications; (c) map the idealized networks to proximal-physical network models that will guarantee correct, reliable and safe communications between controllers and plant and between controllers, subsystems and systems; (d) semi-generate and/or prototype control software for each controller specification; (e) specify ECUs, or proximal physical models of these ECUs, that are sufficient to execute control software that will guarantee the correct, reliable and safe control of plant operating in the context of the whole system; and (f) verify that these physical controllers (via Hardware in the loop), or proximal-physical, models of controllers, are equivalent in function and timing to their executable specifications.

Software Engineers - to (a) install operating systems/kernels, and create/install device drivers required to support the control software and peripheral devices of the designated ECUs; (b) develop, debug and verify well-engineered software that, as required, replaces prototype software and possibly semi-generated functional control software, and integrate it into the operating systems and device environments of the controllers associated with the control software; and (c) join with Hardware Engineers to verify that these physical, or proximal physical models of, controllers with their full software are equivalent in function and timing to their executable specifications.

Hardware Engineers - to (a) design, acquire and verify, where required, physical hardware to implement the electronic, ECU and network models constructed by the System Engineers and (b) join with Software Engineers to verify that the physical controllers connected with plant (physical or modelled) and to other controllers, execute their well-engineered software to achieve equivalent function and timing as their executable specifications.

System Validation Engineers – to (a) independently validate that the fully integrated physical subsystems and entire system match in function and timing their original executable specification; (b) identify discrepancies in function and timing, identify the source, and collaborate with Engineering to resolve the problem; and (c) iterate a-b until all discrepancies are resolved.

System Calibration Engineers - to (a) tune the physical system to accommodate usability (drivability) and other perceived improvements; (b) compare the calibrated vehicle with its original specification and determine, for each discrepancy, its nature and impact on safety, performance, etc.; (c) resolve discrepancies with the Engineers and, if required, Architects; and (d) iterate a-c until the discrepancies between the physical system and its specification + models + software + verification suites are resolved.

Diagnosis Engineers - to help diagnose faults in physical systems. EST's technology enables the systematic determination of function, timing, synchronization and communication faults in distributed cyber-physical systems.

Traffic Engineers – tasked with optimizing traffic flow, minimizing emission and fuel consumption, maximizing safety, and maximizing the utilization of traffic infrastructure.

Supply Chain Engineers - to facilitate communication and cooperation throughout the supply chain, the systematic deployment of model-based design by OEMs, Tier 1s and some Tier 2s (for example, semi-conductor device suppliers) is a necessity.  The relevant Requirements, relevant verification suites and results are necessarily integral elements of each model.  No longer should natural language specifications be acceptable, nor components and subsystems returned without models, full validation and verification suites, and results.

Continue on EST Modelling and Simulation Technology: