Technology-neutral energy, electrical and fire safety
D07 selects the released branch applicable to the assessed vehicle: combustion, hybrid, battery-electric, hydrogen or another supported energy architecture. Combined architectures must address interacting hazards.
Credit is based on demonstrated vehicle-level safety performance, not on propulsion novelty or the presence of a particular technology.
| Criterion | Proposed scoring ownership | Points |
|---|---|---|
| D07.1 | Post-impact energy containment | 30 |
| D07.2 | Energy-specific fire or propagation protection | 25 |
| D07.3 | Charging or refuelling branch performance | 20 |
| D07.4 | Hazard warning and electrical or fuel isolation | 15 |
| D07.5 | Water exposure and recovery hazard branch | 10 |
| D07 total | 100 | |
Battery and hybrid systems
Installed chemistry, enclosure, controls, state of charge, temperature and mechanical history define applicability. Cell or different-pack evidence does not automatically establish vehicle-level performance.
Fuel and refuelling
Combustion and hybrid branches address retention, leakage, ignition, hazardous release, warning and the refuelling interface under the released method.
Hydrogen and pressure systems
Applicable evidence identifies containment, shut-off, pressure relief, leak detection, venting and possible secondary harm.
Charging and bidirectional power
Supported interfaces, insulation, contact heating, fault response, damaged connectors and bidirectional operation are included where they change the hazard boundary.
Water and recovery hazards
Shock risk, release operation, warning, communication and recovery require dedicated evidence. An ingress-protection rating alone does not establish immersion safety or escape performance.
Emerging architectures
A new energy system requires a validated branch with comparable safety objectives. If no appropriate branch is released, that vehicle profile is not operational for rating.
Methods are not yet released
Annex F lists the category branches, energy and rescue methods, scoring functions and emerging-energy methods as open release items. Test speeds, observation periods, penetration setups, IP ratings and other examples must not be presented as adopted AUTOSAFE acceptance criteria until a controlled protocol explicitly releases them.
Continue with the full technical document
Use IAF AUTOSAFE First Edition for the complete domain requirements, proposed point schedule, evidence rules, gates, certificate controls and Annex F release conditions.