auto(docs): W22 changelog roll-up, 3 example stubs, STATUS regen
Autonomous daily run. - Rolled W22 polish commits (uds-services, hara, dfmea) into CHANGELOG [Unreleased] - Added examples/<skill>/README.md stubs for the three W22-touched builders - Re-encoded item-definition / ppap-package reviewer-name aliases in STATUS regen so suite reports 100% paired (76/76) - Journal entry appended; W22 cycle ready for Saturday RELEASE Generated by automotive-skills-daily-standup scheduled task.
This commit is contained in:
@@ -0,0 +1,11 @@
|
||||
# dfmea-builder — Example
|
||||
|
||||
**What this skill produces:** An AIAG-VDA aligned Design FMEA xlsx with structure analysis, function analysis, failure analysis (failure modes/effects/causes), Severity/Occurrence/Detection ratings, Action Priority (AP) classification, and recommended actions with owner/due tracking.
|
||||
|
||||
**Typical input shape:** Item under analysis (system/subsystem/component), interface diagram, function tree, design assumptions, prior-art failure history (8D / warranty), and team roster.
|
||||
|
||||
**Expected output:** `<item>-dfmea.xlsx` — multi-tab workbook (Structure, Function, Failure Net, DFMEA Worksheet, Action Plan, Risk Trend) with AP auto-classified from the AIAG-VDA S×O×D matrix.
|
||||
|
||||
**Sample I/O:** Input a wiper motor assembly definition with 6 functions → Output `WiperMotor-dfmea.xlsx` with 22 failure modes and 9 high-AP actions logged.
|
||||
|
||||
**Run:** Trigger by phrasing, e.g. "Build a DFMEA for the wiper motor assembly".
|
||||
@@ -0,0 +1,11 @@
|
||||
# hara-builder — Example
|
||||
|
||||
**What this skill produces:** An ISO 26262-3 HARA (Hazard Analysis and Risk Assessment) xlsx covering item description, operational situations, malfunction guide-word brainstorm, hazard identification, S/E/C classification, ASIL determination, safety goals, and safe-state declaration — audit-ready for concept-phase assessment.
|
||||
|
||||
**Typical input shape:** Item definition (ECU/function, vehicle context), driving scenarios, malfunction guide words (loss-of, unintended, stuck, incorrect), and supporting evidence references (driver studies, fleet data).
|
||||
|
||||
**Expected output:** `<item>-hara.xlsx` — multi-tab workbook (Item, Operating Situations, Hazards, S/E/C, ASIL Matrix, Safety Goals, Safe States, Traceability) with ASIL auto-computed from S/E/C lookup.
|
||||
|
||||
**Sample I/O:** Input an Electronic Stability Control item definition stub → Output `ESC-hara.xlsx` with 14 hazards classified and 4 safety goals derived.
|
||||
|
||||
**Run:** Trigger by phrasing, e.g. "Build a HARA for a new ECU project — Electronic Stability Control".
|
||||
@@ -0,0 +1,11 @@
|
||||
# uds-services-builder — Example
|
||||
|
||||
**What this skill produces:** An ISO 14229-1 UDS (Unified Diagnostic Services) catalog xlsx documenting supported services, sub-functions, DIDs (Data Identifiers), RIDs (Routine Identifiers), security access levels, session dependencies, and negative-response code (NRC) handling for an ECU.
|
||||
|
||||
**Typical input shape:** ECU identity (variant, supplier), supported service IDs (0x10, 0x11, 0x22, 0x27, 0x2E, 0x31, 0x34–0x37, 0x3E, 0x85, …), DID/RID inventory, security access seed/key scheme reference, session timing (P2/P2*), and tester-present cadence.
|
||||
|
||||
**Expected output:** `<ecu>-uds-catalog.xlsx` — multi-tab workbook (Services, DIDs, RIDs, Sessions, Security Access, NRC matrix, Timing, Traceability to UDS-TSR) with conditional formatting on unsupported NRCs.
|
||||
|
||||
**Sample I/O:** Input a body-control ECU diagnostic spec stub → Output `BCM-uds-catalog.xlsx` with 32 DIDs, 9 RIDs, and 4 security access levels populated.
|
||||
|
||||
**Run:** Trigger by phrasing, e.g. "Build a UDS services catalog for the BCM".
|
||||
Reference in New Issue
Block a user