# Simulation, SIL and HIL

Canonical URL: https://babadook.tech/sub-modules/maxacor-sim-sil-hil
Entity: sub-modules
Content hash: 5123c99721bc668a70b78b409f72ce82105b6b479e00ce77767a02fcb7bb8280

Keep simulated, software-in-the-loop and hardware-in-the-loop evidence separate from live operation.

A controller passes SIL but fails when HIL introduces real timing and sensor noise. Promotion decisions can see which environment produced each result.

## What changes

A controller passes SIL but fails when HIL introduces real timing and sensor noise. Promotion decisions can see which environment produced each result.

### data Viz

### data View

section: operating-scene

## Operational boundary

- **What it does:** Keep simulated, software-in-the-loop and hardware-in-the-loop evidence separate from live operation.
- **What the team gains:** Promotion decisions can see which environment produced each result.
- **What it does not own:** Lab success cannot become production readiness automatically.
- **section:** operational-boundary

## Simulation, SIL and HIL

action: Keep simulated, software-in-the-loop and hardware-in-the-loop evidence separate from live operation.

mechanism: A controller passes SIL but fails when HIL introduces real timing and sensor noise.

workflow role: A controller passes SIL but fails when HIL introduces real timing and sensor noise.

operational outcome: Promotion decisions can see which environment produced each result.

maturity: specified

evidence: MAXACOR Part 10, §§5–7; Part12 §4.6A.

### Section 1

Operations team

### Section 2

Engineering team

### Section 1

Qualified physical state

### Section 2

Current work context

### Section 1

Evidence-bearing operational disposition

### Section 1

Lab success cannot become production readiness automatically.

## Relationships

### products

- MAXACOR — https://babadook.tech/products/maxacor

### modules

- Operational Twin, Simulation and Validation — https://babadook.tech/modules/maxacor-operational-twin-simulation