TAILORING THE CM2 MODELRachel Holyoak

WHAT IS TAILORING?

• Modifying a requirement such that the intent of the requirement is met but the method of meeting the requirement is unique or different than prescribed• Does not eliminate the requirement• Maintains verification of the requirement intent• Defines a unique method to meet a requirement

WHY DO WE TAILOR?

• Capability (or lack thereof) with the existing tools, processes, or people• Commonality with standards• Consumer request• Contractual requirements

Remember what you are playing with

CORE CM2 BUSINESS PROCESSES

• As-Planned / As-Released Baselines• 4-Tier, 9-Step Development Process• Naming, Numbering, and Reuse• Data and Record Integrity• Validation and Release Records• Changes and Revision Records• As-Built Records

WHAT HAPPENS WHEN WE FORGET WHY WE ARE TAILORING?

SO WHAT IS SAFE TO TAILOR?

• Safety Zones• Areas that are usually safe to tailor or make individual adaptations

• Rip Tides• Areas that when tailored, quickly carry one away from the desired location• Wear out even the best CM person trying to get back to the previous location• Requires great effort to overcome the mistake once in the flow

SO WHAT IS SAFE TO TAILOR?

• As Planned / As-Released Baselines• Purpose: Maintain configuration definition • Safety Zones:

• Reporting format, including extra items displayed• Effectivity type (Serial number, lot number, end item, date, etc.)

• Rip Tides:• Failure to have a single location for the report• Manually maintaining if using a PLM tool to review/approve data• Failure to address effectivity

SO WHAT IS SAFE TO TAILOR?

• 4-Tier, 9-Step Development Process• Purpose: Minimize cost of the product lifecycle• Safety Zones:

• Timelines• Number of iterations between any two steps• Method for design iterations (rapid learning cycles, prototypes, etc.)

• Rip Tides:• Moving forward to the next step while still iterating on a previous step• Starting up the right side of the “V” before finishing the left side of the “V”

SO WHAT IS SAFE TO TAILOR?

• Naming, Numbering, and Reuse• Purpose: Allow each item (requirement, drawing, specification, document, part,

etc.) to be uniquely identified and that identification signifies interchangeability• Safety Zones:

• Numbering scheme (Smart numbers vs. not)• Naming convention• Revision Scheme

• Rip Tides:• Interchangeability• Failure to identify the item “master”• Intermingling preliminary, prototype, and production identifiers

SO WHAT IS SAFE TO TAILOR?

• Data and Record Integrity• Purpose: Data can be trusted, is reliable, and provides traceability• Safety Zones:

• Clearly defining what needs traceability and to what level• MIL/Industry Standard Parts?• Commercial off the Shelf Items?• Raw Material Lots?

• Allowing multi entry points• Transparent system

• Rip Tides:• Allowing multiple sources to manipulate the data once it’s started validation• Ability to modify released data without revision

SO WHAT IS SAFE TO TAILOR?

• Validation and Release Records• Purpose: Data is owned by a person and validated by the user of the data with

a clear status to communicate when it is valid for use and cannot be modified without another validation / approval process

• Safety Zones:• Adding contractually driven signatures

• Rip Tides:• Removing an owner or user and replacing it with a contractually driven signature that

is an expert or independent verifier• Not requiring released items to manufacture• Allowing “open” changes (meaning no formal release until after the product is built)

SO WHAT IS SAFE TO TAILOR?

• Changes and Revision Records• Purpose: A closed-loop change process is used to update and revalidate items

previously released• Safety Zones:

• Classification• Fast Track Criteria• Details of board review – how, when, where• Standardized Forms Format

• Rip Tides:• Failure to have a closed-loop system• Details of board review – why and what• Change content, including use of an impact Matrix• Details of change specialist review

SO WHAT IS SAFE TO TAILOR?

• Data and Record Integrity• Purpose: A record or set of records exists for each item requiring traceability that

provides clear evidence that the item conforms to it’s given requirements• Safety Zones:

• Reporting format• Requirements validation method

• Rip Tides:• Lack of traceability when items are reused or repurposed• Lack of ability to concisely tie the associated validation to a given item

DON’T LOSE SIGHT OF THE END GOAL –FINAL PRODUCTS OR SERVICES MEET ALL

REQUIREMENTS, ON-TIME, AND ON-BUDGET

QUESTIONS?