MADE Requirements import template schema

This is a sample Excel template (MADE_Requirements.xlsx) bundled with MADE 3.9.1's help data, demonstrating the exact column structure MADE expects when importing a requirements hierarchy (see also the Requirement Import Configuration workflows: wf43-set-the-requirement-import-configuration.md, wf44-importing-new-requirements.md, wf45-synchronizing-requirements.md, wf46-requirements-verification.md).

Columns

Column	Purpose
Requirement ID	A hierarchical identifier (e.g. 1, 1.1, 1.2.1) — the dot-notation encodes parent/child requirement structure directly in the ID.
Requirement Name	Human-readable requirement label.
DID No.	Data Item Description number — a document/specification reference the requirement traces back to.
DID Title	The title of that DID reference.
Description	The requirement's actual text/content.
Classification	A requirement category tag — sample data shows values like Performance, Design, Mission Critical, Safety Critical.
Pre-Requisite	A free-text dependency note (e.g. Electrical power, Fuel, 3 DOF, Drive Test) — appears to capture an informal precondition rather than a structured link to another requirement ID.

Sample rows (template placeholder data, not a real requirements set)

The bundled file contains illustrative placeholder rows only ("Requirement 1", "Description 1", etc.) rather than a real project's requirements — its purpose is purely to demonstrate the column layout and the ID-based hierarchy convention (1 -> 1.1, 1.2 -> 1.2.1, 1.2.2) that MADE's import parser expects.

Key takeaway

The hierarchy is expressed entirely through the dot-delimited Requirement ID column (e.g. 1.2.1 is a child of 1.2, which is a child of 1) — there is no separate parent-ID column. Classification is optional (blank in one sample row) and Pre-Requisite is sparsely populated even in the example, suggesting it is an optional annotation field rather than a required one.