Skip to main content

​
Steps

​
1. Navigate to Requirements Space

From the Home Dashboard, click Requirements in the space navigation sidebar. Locate the CUSTOMER-REQS document in the document inventory tree.
If the CUSTOMER-REQS document doesn’t exist, the RTM model will auto-create it when you first create a CustomerRequirement work item. The document is automatically placed in the Requirements/ folder.

​
2. Create a New Customer Requirement

Option A: From Document View
  1. Open the CUSTOMER-REQS document
  2. Click ➕ Add Work Item
  3. Select Customer Requirement from the type dropdown
  4. Fill in required fields (see Field Reference below)
Option B: From Requirements Dashboard
  1. Click ** Create Requirement** widget
  2. Select Customer Requirement type
  3. The system automatically assigns the work item to the CUSTOMER-REQS module

​
3. Fill Required Fields

FieldPurposeExample
TitleBrief requirement statement”Vehicle shall support ISO 26262 ASIL D safety integrity”
DescriptionDetailed requirement text with acceptance criteria”The vehicle’s braking system shall implement ASIL D-rated redundancy per ISO 26262-3:2018 clause 7.4.3…”
ClassificationSC (Special Characteristic) or CC (Critical Characteristic) if safety-relevantLeave blank for non-safety requirements; select SC for safety-critical; CC for cybersecurity-critical
Setting classification to SC or CC propagates safety obligations down through the V-model. SC/CC customer requirements require SC/CC system requirements, design requirements, and verification test cases. Leave unclassified unless mandated by safety analysis (HARA, HAZID).

​
4. Structure with Outline Numbering

TestAuto2 automatically assigns outline numbers based on document hierarchy: 
1.0  Functional Requirements
  1.1  Braking System
    1.1.1  Emergency Braking
    1.1.2  ABS Control
  1.2  Steering System
2.0  Performance Requirements
  2.1  Acceleration
  2.2  Top Speed
Use Document → Reorder to adjust outline structure. Outline numbers determine sort order in PowerSheet RTM views. Customer requirements can reference:
  • User Needs (upstream): Link via custom relationship if defined in your RTM model
  • External Evidence: Attach regulatory standards, customer specification documents, market analysis reports via Attachments tab

​
6. Set Document Workflow State

Navigate to Document → Properties and set workflow state:
StateMeaning
DraftWork in progress, editable by Safety Engineers
In ReviewSubmitted for stakeholder approval
ApprovedBaseline established, requires change management to modify
Refer to Document Workflow States for state transition rules.

​
Verification

You should now see:
  • Customer requirement appears in CUSTOMER-REQS document with assigned outline number
  • Requirement visible in Whole RTM PowerSheet (green Customer Requirements column group)
  • Traceability coverage metric updates on Requirements Space Dashboard
  • If classified SC/CC, requirement appears in Safety Readiness Scorecard gap analysis
After creating customer requirements, check the Requirements Space Dashboard → Customer Requirements → System Requirements coverage bar. Until you create system requirements that refine customer requirements, coverage will be 0%. This gap identifies unrefined customer needs.

​
See also