ME.11:5 - Archetypal Grounding - SSFD Workplace Projects
The automotive SSFD programme supplies reports and review evidence about actual workplace projects without supplying a universal effectiveness claim. More than 300 engineers participated in a three-year transfer programme; training was followed by supported four-to-six-month workplace projects. Seventy-two of the first 100 reviewed project reports recorded SSFD use, and 41 contained enough detail for deeper analysis. Across those 41, the study reports 95 examples of evidenced individual benefits while distinguishing direct and indirect contribution.
The published paper is an evidence source, not an occurrence registry. A local application may admit a particular project Work occurrence only when its records recover the actual performer Systems and A.13 bases, action history, enacted admitted Method, temporal extent, and containing-System relation required by A.15.1. Otherwise retain the published project account as report evidence and return the missing occurrence or performer basis. The slices below show how the reported evidence can distinguish between possible answers to the later questions; they do not admit Work by citation.
ME.11:5.1 - Preserve the Status Branch
Before using the replay, establish whether SSFD is an admitted Method for the current FPF use. If it is, each supported project occurrence may be tested for its own obtaining enactsMethod relation. If it is not, admit the workplace Work independently, retain the SSFD account as a candidate, and name only separately admitted constituent Methods as enacted. The report statement “used SSFD” does not perform either admission automatically.
ME.11:5.2 - Representative and Discriminating Slices
| Slice | Reported project facts used | Evidence returned | Stop retained |
|---|---|---|---|
| Project 11 | The report concerns functional analysis of a new by-wire steering system and records 48 failure modes for four system functions, 44 new requirements and design rules, 44 test cases for individual systems, and 33 requirements and test cases for the overall system. | One bounded application account for checking whether description, representation, and support claims were usable in that project situation, plus the reported results and burdens available from the source. | Do not infer that this project caused or preceded Project 32, that every programme participant had the same capability, or that the reported benefits came from SSFD alone. |
| Project 32 | The report exposes difficulty representing the relation between a closed-loop sensor and controller. | A discriminating representation difficulty for ME.12 and an ME.13 unlike-situation comparison. ME.12 can return it to ME.9 only when several unlike Method-related actions are current, the affected action has a complete C.37 claim group, and the profile makes its shared source, correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions for reconsidering several selections recoverable. Otherwise the difficulty stays with C.37 or the direct FPF representation governor. | Do not turn the difficulty into general Method failure or claim that Project 11 supplies the counterfactual. |
| 41-report evidence set | The review identifies 95 examples of evidenced individual benefits across business results, process improvement, and product-development-team capability improvement, while separating direct and indirect contribution. | Bounded report and review evidence for later comparison of results, burdens, and evidence strength in ME.14. | Counts and source classifications do not establish causality, universal superiority, transfer, or current capability for every participant. |
The useful ME.11 result is therefore not “SSFD works”. It is a set of reported workplace-project accounts, situation and support conditions, observed representation difficulties, reported results and burdens, evidence-source qualifications, and explicit gaps for three separate later judgments.
ME.11:5.3 - APP-ME-01 Early Stop
In APP-ME-01, the three-release statement remains a WorkPlan. The three named-user retrieval, tailoring, and selection-support occurrences from ME.10 establish only those support tasks; they do not perform a release or enact the candidate whole C-EC-Release-v2.
Add a release trial occurrence only after its release Work, actual performers and their A.13 bases, enacted admitted constituent Methods, participating Systems, Agent-performed Work, relied-on capabilities and direct relations, conditions, domain result, burdens, deviations, temporal extent, containing System, and authority facts are recovered. Until then return missing-performed-work. Even after a release is admitted, keep C-EC-Release-v2 as a candidate and send the occurrence evidence separately to ME.12–ME.14.