13 Reporting

MADE contains several report designs used to generate results from different analyses conducted on the system model. Report categories include Criticality, Data Quality Analysis, Maintainability, Mission Profile Definition, Reliability & Availability, Reliability-Centered Maintenance (RCM) and Prognostics and Health Management. More information about each report is displayed in the Report Wizard description.

The reporting wizard provides the user with the following options:

• Selecting a report type
• Selecting a report output format (PDF or XLS)
• Selecting an item/end-effect item, mission profile, library item, maintenance action or analysis
• Setting the propagation method (FCM (default) or Bond)
• Setting Output Options (i.e. nominal & exclusive paths, exclusive paths, ignore injected failures or only consider system failure)
• Report Page Formatting
• Inclusion of organization details (e.g. logos and contact details)

To generate a report from the Report Wizard:

• Select Reports → Report Wizard from the main menu
• Select a report type from the reporting list
• Select Next to continue to the next page or Finish to generate the report

The Report Wizard's report list (Criticality category, PDF output selected) includes: CA (MIL-STD-1629A, Quantitative Standard), FMECA (MIL-STD-1629A, Custom), FMECA (Fuzzy, PHMT), FMECA (HRI, Custom), FMECA (HRI, PHMT), FMECA (RPN, PHMT), FMECA – Maintainability Combined (MIL-STD-1629A), FMECA (MIL-STD-882E), FMECA (ISO26262, HARA ASIL), FMECA (AIAG, FMEA 4th Ed.), FMECA (SAE J1739, Rev. AUG2002), FMECA (SAE ARP4761, Functional), Design Potential FMECA (RPN, Custom); Data Quality Analysis category: Annotation Report; Failure Mode Effects Analysis category: FMEA (MIL-STD-1629A), FMEA (AIAG, FMEA 4th Ed.), FMEA (SAE J1739, Rev. AUG2002), FMEA (SAE ARP4761, Functional); General category: System Information Report.

For example, a FMEA report will allow the user to output the results of effects for each potential failure mode with respect to its local, next and end-effects. These effects, defined in accordance to the MIL-STD-629A FMEA standard, are:

1. Local effect: the consequences of a functional failure mode on the operation, function or status of the system, resulting from a failure path in a model item failure diagram (if created) – otherwise it is the failure mode of the model item.
2. Next effect: the consequences of a functional failure mode on the operation, function or status of model item(s) (e.g. component or subsystem) in the next higher level of system hierarchy/indenture above the system item from which the failure mode originated.
3. End effect: the consequences of a functional failure mode on the operational or functional output of the system (end-effect item) at the highest level of indenture.

To set the end-effect item:

• Select (Right-click) the item display name from the Project Explorer viewer
• Select End-effect Item from the right-click menu to designate the item as an end-effect

(The Project Explorer right-click menu on the top-level system item also includes: New, System Model, Failure Diagram, Bond Graph, Functions, Requirements, Functional Diagram, Mission Profiles, Hazard Diagram, Maintenance Actions, Cut, Copy, Paste, Delete, End Effect Item, Fault Tree, Response Paths, Hazard Path Analysis, Save to Library, Advanced Properties.)

Generating a FMEA Report — Worked Example

To generate a FMEA report:

1. Select Report → Report Wizard from the main menu (menu items: Report Wizard, Report History, Report Filtering, Report Preferences, HTML Reports, Chart Analysis...)
2. Select FMEA (MIL-STD-1629A) from the list of reporting templates. The description panel states: "The Failure Mode and Effects Analysis (MIL-STD-1629A) or FMEA (1629A) report is based on the MIL-STD-1629A standard. Specifically the report is based on Task 101, Figure 101.3 'FAILURE MODE AND EFFECTS ANALYSIS'. The report lists the Failure Mode for each item in the system model that leads to the selected End Effect. The report depends on functions, flows, failure diagrams (if provided) and criticality data (severity classification)."
3. Select Next to advance to the Analysis Options page.
4. Select a model item from the system model tree then select the Set End Effect Item button. End-effect items will show a blue flag icon.
5. Set Propagation Method (default FCM – Functional Concept Mapping; alternative Bond).
6. Set Output Options (checkboxes: Ignore injected failures, Include nominal paths, Root causes only, System failures only) and Path Control Number (checkbox: Show Path Control Number).
7. Select a Criticality Profile from the dropdown (e.g. "PHMT 1629A Criticality").
8. Select Next to advance to the Report Body Customization page.
9. Enter Report Body customization options: Page size (Format e.g. "Letter", Width/Height fields), Orientation (Landscape/Portrait), Cover Page Footer Message, Body Footer Message ("For best results keep the message limited to two lines.").
10. Select Next to advance to Cover Page - Organization Details. Enter organization details for the cover page: Organization Name, Postal address, Phone number, Fax number, Email address, Website. Select Browse to upload an Organization Logo (default shown: MADE logo).
11. Select Next to advance to the Export Report page. Select the checkbox Export to Directory and Browse to a target folder (e.g. "C:\Users\Public") to include a copy of the report there.
12. Select Finish to generate the Report.

The finished FMEA report is generated in a new window within MADE and contains navigation and exporting options. The FMEA (MIL-STD-1629A) report layout includes header fields: System, Indenture Level, Reference Drawing, Mission (e.g. "Vehicle System", Level 1, "New Group"), Date/Sheet/Compiled By/Approved By; and body columns: Identification Number, Item / Functional Identification (Nomenclature), Function, Failure Modes and Causes, Mission Phase / Operational Mode, Failure Effects (Local Effects, Next Higher Level, End Effects), Failure Detection Means, Compensating Provisions, Severity Class.

Example report row (Vehicle System, Item VS1): Function = "Convert Mechanical - rotational Angular velocity"; Failure Modes and Causes = "High Angular velocity of the Driveline" / "Low Angular velocity of the Driveline" / "High Torque of the Power Generation" / "Low Torque of the Power Generation"; Mission Phase/Operational Mode = enumerated mission phases ("1: Start-up 100%, 2: Acceleration 100%, 3: Cruise 100%, 4: Turning 100%, 5: Crusie 2 100%, 6: Deceleration 100%, 7: Shut-down 100%" — repeated per row per phase-percentage breakdown); Local/Next Higher Level/End Effects = "Convert Mechanical - rotational Angular velocity" (High/Low as applicable); Severity Class = 1 for each row.