Skip to content
Shared platform · Data & intelligence

Simulation Framework

You cannot crash a satellite twice, and you should not learn about a control bug from a plant. The simulation framework carries the group's in-the-loop testing — software, processor and hardware in the loop — plus the physics models behind them, so a controller is exercised across its envelope before anything real is at risk.

How determinism shows up here

Timing violations are a first-class test case. A missed deadline is injected and its consequence observed, rather than assumed benign.

What it does

Inside the platform

01

SIL / PIL / HIL

The same control code tested against a model, then on the target processor, then against real hardware in the loop.

02

Physics & environment models

Vehicle dynamics, orbital mechanics, thermal and process models shared across programmes rather than rebuilt per project.

03

Fault injection

Sensor dropouts, link loss, actuator failure and timing violations exercised deliberately, in a rig, on purpose.

04

Regression on every change

Simulation suites run in CI, so a control change that breaks the envelope is caught before review, not after commissioning.

How it fits together

The shape of the work

The same control code, four times, with less and less pretend in it

Fidelity goes up left to right and so does the cost of being wrong. The point of the ladder is that a defect should be found in the cheapest column that can find it — which only works if the code is genuinely unmodified as it moves right.

SILSoftware in the loopPILProcessor in the loopHILHardware in the loopFIELDThe real thingThe control codeIdentical — not a port, not a rewrite, not “equivalent logic”Code runs onHost workstationThe target MCUThe target MCUThe target MCUPlant isA physics modelA physics modelReal I/O, modelled plantReal plantTiming isLogicalMeasured on targetReal-time, wiredReal-time, liveCost of a failureA re-runA re-runA rig, maybe a boardThe vehicle or the plantFAULT INJECTIONSensor dropout · link loss · actuator stuck · missed deadline — injected here, on purpose, in CINot here.A simulation you only run before a release is documentation. These suites run on every change, and a controlchange that leaves the envelope fails the build rather than the commissioning.
Who builds on it

Used across the group

  • Vyovrinda flight and attitude control
  • Industrial Automation control logic
  • Savithru pack management

Ownership

A shared platform. It has no natural home in any single unit, so the group funds it centrally and the shared engineering bench maintains it. Every company and division draws on the same version.

How we decide what is shared

Building something that needs Simulation Framework?

Tell us the constraints and we will come back with how this platform would carry them — or say plainly if it would not.