WF66: Develop Control Measures

Pre-Requisites

• A. FBD Model: Enables FMECA analysis that includes control measures (see WF04).
• B. Failure Diagram: Enables ability to create control measures (see WF06).
• C. Criticality Editing: Profile defines visible concepts in the failure matrix; criticality values required as a baseline before control measure effect (see WF09).

Detailed Steps

1. Open MADE Model — open an existing MADE project.
2. Decision — Custom Taxonomy? Determine whether the default control measure taxonomy meets the organisational requirements. If not (Yes to custom), proceed to Step 3. If default suffices (No), skip to Step 7.
3. Access Control Measure Taxonomy — go to the toolbar and select Preferences -> Taxonomy Editor (Customize Taxonomy).
4. Create Custom Control Categories — create new custom control categories and define their descriptions.
5. Create Custom Control Types — create new custom control types and define their descriptions.
6. Save Control Measure Taxonomy to Project — save the control measures taxonomy to the project by selecting the save-to-project button.
7. Select Component — navigate to the component of interest using the project explorer or criticality editor.
8. Select Failure Concept — navigate to the failure concept the control measure is acting on using the criticality editor.
9. Access Control Measure Set — access the control measure set by clicking the control measure icon at the top right hand corner of the criticality editor.
10. Decision — More Control Measures? Determine if more control measures need to be added to the control measure set. If yes, proceed to Step 11.
11. Create Control Measure Instance — right-click the "add new control measure" icon to add an instance to the set, using the taxonomy as a guide.
12. Define Criticality Effect using Barrier Matrix — click "Barrier Matrix" and open the Barrier Matrix Editor to model the effect of control measures on failure concept criticality (Effect on Controllability, Effect on Severity, Effect on Occurrence, Effect on Detectability). Select the plus icon at the corresponding qualitative criticality parameter and enter the delta effect that the control measure has on criticality.
13. Decision — More failure Concepts need Control? Add more failure concepts to component as required (loop back to Step 8).
14. Control Measure Set / Control Measure created.

Screen-by-screen detail (from embedded screenshots)

• Step 3: Access Control Measure Taxonomy — Main menu: Preferences > Customize Taxonomy. "Custom Taxonomy" editor, "Control Measures" tab shows a "Control Measures Taxonomy" tree (Compensating Provision, Detection Methods, Prevention Controls, Substantiation Actions) with a "Control Measures Entry" panel (Name, Description, Example, Category Description). Icon legend: blue shield = Default Control Measure Item; green shield = Custom Control Measure Item (stored at application level); red shield = Custom Control Measure Item (stored at project level).
• Step 4: Create Custom Control Measure Categories — Click the "Add new Control Measure Category" icon. "New Control Measure Category" dialog: "Create a root category?" checkbox, Name (e.g. "Custom Control Measure Category 1"), Description (e.g. "Custom Category created for demonstration purpose."). New category appears nested under "Compensating Provision" in the taxonomy tree.
• Step 5: Create Custom Control Measure Types — Click "Add new Control Measure" icon. "New Control Measure" dialog: Name (e.g. "Custom Control Measure 1"), Description, Example fields. New item appears under the custom category in the tree.
• Step 6: Save Taxonomy to Project — Additional example items created: "Cold Start" (with description and example about aircraft engine cold start) and "Hot Start" (abnormal engine start with rising EGT). Click the "Save Taxonomy to Project" icon; "Save Taxonomy to Project" dialog lists checkboxes for each Control Measure Item to save into the project (e.g. Compensating Provision > Custom Control Measure Category 1 > Cold Start, Custom Control Measure 1, Hot Start; Observation; Redundancy). Click OK — items become project-level (red shield) entries in the Control Measures Taxonomy.
• Steps 7-9: Access Control Measure Set Window of Component — Main menu: Analyses > Criticality & Reliability Editor. In the R/C Properties Editor, select an Item/Failure (e.g. "Fractured" under Driveline), view "Failure Criticality" panel: Selected Profile (e.g. "PHMT RPN Criticality"), Criticality Method (e.g. "Risk Priority Number (RPN)"), sliders for Difficulty of Detection, Occurrence, Controllability (each 1-10, e.g. showing 10.0/10.0/10.0 with labels Highest/Very High/Controllability), and a Software Control on/off slider. Click the Control Measures icon to open the "Control Measures" dialog: "Control Measures - Fractured (Driveline)" table (Enabled/Name, Type, Mitigation, Narrative) with an "Add" button and a "Barrier Matrix" button at bottom.
• Step 11: Create Control Measure Instance — Click "Create a new Control Measure" icon. Right pane shows the Control Measures taxonomy tree (Compensating Provision > Custom Control Measure Category 1, Observation, Redundancy > Abort Mission [selected], Change System Configuration, Modify Mission, Modify Sensor Set, Override System, Procedures, Redesign Component, Relief Devices, Safety Devices; Detection Methods > Equipment Testing, Inspection, On Demand, Operator Observation, Sensing Device, Warning Device; Prevention Controls > Benchmarking studies, Breakdown Repair). Name field (e.g. "Abort Recon Mission"), Narrative field (e.g. "If fracture occurs during a reconnaissance mission, abort and return to base"). Click Add.
• Step 12: Define Criticality Effect using Barrier Matrix — Control Measures table now lists enabled measures (e.g. "Abort Recon Mission" / Type "Abort Mission" and "Warning Alarm" / Type "Safety Devices", each with Narrative). Click "Barrier Matrix" to open the Barrier Matrix view: a left-to-right flow diagram per failure concept ("Fractured (Driveline)") with columns No Control -> Abort Recon Mission -> Warning Alarm -> Revised Control, and rows for Difficulty of Detection and Probability/Occurrence. Each control measure step shows an editable delta value (e.g. -2.5 for Difficulty of Detection at Abort Recon Mission, -1.9 for Probability/Occurrence at Warning Alarm) with resulting revised criticality values (e.g. 10.0 -> 7.5 for Difficulty of Detection; 10.0 -> 8.1 for Probability/Occurrence). Click Back to return to Control Measures, then OK.