How do I configure my Document Headers?

Document headers are required in FMEA releases to provide essential information such as worksheet name, version, author, and release date, ensuring consistency, traceability, compliance, and clear communication across all released documents.


How it works:

When choosing to “Export” or “Create a Release” for a worksheet, the “Configure Document Headers” option will appear in the workflow. 


Document headers are required when creating a release. Simply select the menu option, complete the relevant details, and once configured, confirm by checking the “Yes, I have configured document headers” box to proceed. .


Note: 
Modify or adjust the document headers as needed for each export or release.


What appears on an exported or released document

Each exported or released worksheet is an Excel (.xlsx) file. The top of the sheet shows:

  • The worksheet type as the title, for example Process FMEA, Control Plan, Process Flow or Design FMEA.
  • Your Document Header fields, each shown as "Label: value".
  • The worksheet rows follow underneath.


Exports don't add a cover page, revision log, signature or approval block, or charts, such as a bar chart of risks by Action Priority. To share the history of changes, use the Change Log. It shows changes grouped by release, and you can export the change history. For an in-app overview of risk, use the Analysis Matrix in the Risk Management menu. Approvals for customer submissions are managed outside the system.


Header fields for each worksheet type


  • Process Flow: Part Number / Alias, Part Name / Alias, Part Rev / ECL, Prepared By, Date.
  • PFMEA: Company Name, Subject, Model Year(s) / Program(s), Manufacturing Location, PFMEA Start Date, PFMEA ID Number, Customer, PFMEA Revision Date, Confidentiality Level, Process Responsibility, Cross-Functional Team.
  • Control Plan: Stage, Control Plan Number, Date (Orig.), Part Number / Alias, Organization / Plant, Date (Date Rev.), Part Name / Alias, Organization / Supplier (Code), Organization / Plant Approval Date, Part Rev / ECL, Key Contact / Phone, Customer Engineering Approval Date, Core Team, Other Approval Date, Customer Quality Approval Date.
  • DFMEA: Company Name, Subject, Model Year(s) / Program(s), Engineering Location, DFMEA Start Date, DFMEA ID Number, Customer, DFMEA Revision Date, Confidentiality Level, Design Responsibility, Cross-Functional Team.

Note: All fields for the worksheet type are printed, including any you leave blank.


 

Approval dates when no approval is needed

The approval date fields, such as Customer Engineering Approval Date, are optional. If no approval is needed, leave them blank, or remove a date with the clear (x) button. Date fields only accept a date picked from the calendar, so you can't type text such as "N/A".


Team members who aren't users

In Cross-Functional Team or Core Team, select existing users or type custom names for contributors who are not system users.