EPSA Extension Reference
Human-readable reference for CGES EPSA transport, canonical JSON field names, and transitional compatibility aliases.
| Guide Type | Informative reference |
| Related Claims | CGES-EPSA-BOARD-0.1, CGES-EPSA-COMPONENT-0.1 |
| Legacy Alias | CGES-EPSA-0.1 is deprecated and retained only as a legacy component-payload compatibility alias. |
The core standard defines where EPSA data appears in CGES JSON and how extension declarations work. This page explains the extension in human-readable terms without putting source-tool or process policy back into the core standard body.
Transport Locations
CGES-EPSA-BOARD-0.1transports board-level EPSA metadata undermetadata.analysis_context.epsa_board.CGES-EPSA-COMPONENT-0.1transports component-level EPSA semantics undercomponents[].analysis_modules.epsa.- Declaring either extension requires the matching payload and matching
metadata.extensionstoken.
Board-Level EPSA Fields
| Canonical JSON Key | Required | Meaning |
|---|---|---|
enabled | Yes | Global EPSA enablement state. |
profile | Yes | Selected EPSA analysis profile. |
system | No | System or product context. |
owner | No | Responsible engineer or team. |
goal | No | Primary EPSA objective. |
risk_level | No | Program-level risk target. |
approval | No | Readiness or review state. |
Component-Level EPSA Fields
| Canonical JSON Key | Required | Meaning |
|---|---|---|
role | Yes | Functional role in the EPSA model. |
function | No | Additional functional description. |
value | Yes | Normalized component value or design identity. |
voltage_rating | Yes | Canonical operating or stress voltage rating. |
current_rating | No | Canonical current rating. |
power_rating | No | Canonical power rating. |
tolerance | No | Allowed component variation. |
criticality | Yes | Impact level if the part fails. |
failure_mode | No | Expected failure behavior. |
testpoint_required | No | Whether dedicated test coverage is needed. |
measurement | No | Preferred observables for analysis or validation. |
notes | No | Analyst notes and assumptions. |
Compatibility Aliases
Some exporters still read or emit short-form rating keys. These are accepted only for transition and are not canonical.
| Legacy Key | Canonical Key | Status |
|---|---|---|
v_rating | voltage_rating | Deprecated transitional alias |
i_rating | current_rating | Deprecated transitional alias |
p_rating | power_rating | Deprecated transitional alias |
- New exporters SHOULD emit the canonical long-form keys.
- Consumers SHOULD prefer canonical keys when both canonical and legacy aliases are present.
- Legacy aliases may still appear in transition-period payloads and should be treated as quality warnings, not as alternate canonical forms.
Source Mapping Note
Source CAD environments may use uppercase EPSA_* attributes, tool-native parameter names, or historical aliases. Exporter guides describe how those source-side names map into canonical CGES JSON keys.