1

Non-Technical Requirements (NTR)Management in the Bid & Project

PhasesGiven by:

Adrian Armorer, eng, MPM, PMPQualtiy Assurance Manager, Development

Thales Canada Avionics

Adrian Armorer, eng, MPM, PMP

Aerospace/Avionics experience dating back to 2008Bachelor of Mechanical Engineering, ConcordiaUniversity, 2006Master’s of Project Management, UQAM, 2013

2

Agenda for the Conference:Introduction• What is a Non Technical Requirement?• Why do Non Technical Requirements need to be managed?

The Process• Bid Phase• Project Phase

Best PracticesDiscussion and Questions

3

What is a Non-TechnicalRequirement?

4

5

Technical Requirement are dealt with in a completedifferent way and are out of scope of this presentation

Sometimes known as a “Non-Functional Requirement

‘’Any requirement that does not directly impactthe fit, form or function of the product”Thales Avionics Definition

6

An NTR Example for the purposes of ourdiscussion:

The first 50 function changes between Joint DefinitionPhase (JDP) and Safety of Flight shall be free of charge tothe buyer. The first 25 function changes between FirstFlight and Certification shall be free of charge to thebuyer.

Why manage Non-TechnicalRequirements?

7

Why Manage Non-Technical Requirements?

8

• Varied, Complex and Far-Reaching

• Cost Drivers

• Required by AS9100

• Customer Satisfaction

NTRs are Varied, Complex and Far-Reaching• 3 Levels of Requirements can Easily be Flowed Down by

Airframers/Tier 1 firms

9

NTRs are Cost Drivers• Project/Bid teams reviewing NTRs can spot cost drivers

that generalists can overlook

• Will influence project planning

10

• Examples include: First Article InspectionSystem, Document Retention, SafetyStocks

Required by the Aerospace Quality Management Standard

• Sections 7.2.1 & 7.2.2 of AS9100C relate to requirementmanagement

11

NTRs Directly Impact Customer Satisfaction

12

PMBOK- From Chapter 5, Scope Management

13

Two Global Standards…

14

…Aligned

Non-Technical RequirementManagementThe Bid Phase

15

Bid and Project Lifecycle

16

Bid or No Bid Decision: Startof NTR Management

NTR Managementcontinues until projectclosure

Step 1: Capture and Allocate NTRs

• All potential NTRs (contract, SOW, Service Agreement,etc) are captured, and copied into the matrix

• Initial analysis of NTRs to distinguish from non-requirements, technical requirements, etc.

• Assigning of NTRs to project work package managers

17

18

PM has proposed this requirementresponsibility to these WPs. Qualityhas rejected at this point. Programswants to be informed only.

Supply Chain has acceptedresponsibility to investigatecompliance into this requirement

Non-Requirements are always“accepted” by Programs

Step 2: Determining the Nature of theRequirement

• All requirements must be categorized:• “in referential”• Specific NTR• Special NTR• Technical Req.

• “Special Requirements” and “Critical Items” are AS9100concepts that our industry is required to address.

• All requirements must be defined as “critical” or “not”.19

Step 2: Determining the Nature of theRequirement (cont’d)

20

Step 2: Determining the Nature of theRequirement (con’t)

• Technical Requirement• Requirement judged technical after analysis. Maintained in

the matrix for document integrity

• Special NTR• Based on AS9100C, chapter 3.2

• Critical Item• Based on AS9100C, chapter 3.3

21

Step 3: Compliance to the Requirement

• “in referential” requirements are by definition compliant

• Specific, Special NTRs are judged as compliant (C),partially compliant (PC) or non-compliant (NC) withjustification for the PC and NC.

• Preliminary risk register is populated with Special NTRsand Critical Items

22

Step 3: Compliance to the Requirement

23

Step 3: Compliance to the Requirement (cont’d)• First draft of NTR matrix is an input for project estimates.

• The Matrix iterates over the course of the bid!• Estimates need to be adjusted based on evolving

compliance

• Final compliance matrix frozen at project award.• Must reflect the contract signed

24

Non-Technical RequirementManagementThe Project Phase

25

26

Non-Technical RequirementManagementBest Practices

27

Best Practices• NTRs can be used as negotiating leverage during the

bid phase

• If a non-compliant requirement is accepted withouta scope change a risk should be raised

28

• Propose to the customer to contractualize anycompliance matrices from the bid phase

29

• Include NTR reviews in project schedules

• Include as a comment the justification ofcritical and special requirements.

30

31

• Any Suggestions???

32

Questions ?

33

Prochaine conférence24 novembre 2015

Gestion de requis des clients dansle développement d’un nouvel avion

avec

Monsieur André Blanchet

Spécialiste Programme et Chef de GroupeIngénierie Clientèle Avions C Series

34

Prochaine conférence24 novembre 2015

Gestion de requis des clients dansle développement d’un nouvel avion

avec

Monsieur André Blanchet

Spécialiste Programme et Chef de GroupeIngénierie Clientèle Avions C Series