Configuration Management Based on Best Practices

1. CM Manchester, UK, FEB 2000 Europe Configuration ManagementBased on Best Practices Seminar A1 – Establishing Industry Best Practices Alan E. Lager MLR Associates 2801 Park Center Drive, #A1612, Alexandria, VA 22302, USA Voice: 1 703 5673280; 1 703 624 8857 Fax: 1 703 567-3279 E-Mail: alan_e_lager@email.msn.com http://www.mlrassociates.com

2. Agenda Configuration Management Based on Best Practices • What is CM -- Really? • What are Best CM Practices? • ANSI/EIA-649 Perspective • Fundamental CM Principles • Planning and Management • Configuration Identification • Configuration control • Configuration Status Accounting • Configuration Verification and Audit • Measuring and Benchmarking CM Practices

3. What is Configuration Management - Really?

4. IN OUT CM What is CM - Really! Updated Configuration Known Current Configuration • Change Requests • Improve design • Increase reliability • Enhance Maintainability • Reduce Cost • Etc. Status Controlling changes from idea inception to incorporation in all affected items

5. What is CM - Really? • CM makes sure that: • The configuration of a product is known and reflected in product information • Product change is beneficial and effected without adverse consequences • Change is managed from idea inception to incorporation in all items affected

6. What is CM - Really? • CM is an amalgamation of a set of best industry practices • Properly applied, CM • Serves both the provider (developer, producer, supplier) and the user (customer) of a product • Facilitates Logistic Support (Product Support) and product maintenance • Is a Cost Avoider NOT a Cost Driver!!!

7. What are Best CM Practices?

8. What are “Best Practices” • Practices that are the benchmark by which similar activities are judged • Methods that • Are effective and efficient • Meet customer requirements • Have rational performance goals • Include performance measurement standards • Align with corporate business objectives • Position the organization as a leader

9. Customer Environment Supplier Environment Applicable CM Principles AssessMeasure Benchmark Documented CM Process Integrated in Organizational Process What are Best CM Practices?

10. ANSI/EIA-649 Perspective ANSI/EIA 649 “National (US) Consensus Standard on Configuration Management”ANSI American National Standards Institute EIA Electronic Industries Alliance

11. ANSI/EIA-649 Perspective 649 View MIL-STD View Buyer imposed Requirements Industry“Best Practices” employing CM principles • EIA-649 Presents Industry View • EIA- 649 Rationale for Performing CM • Provides Benefit • Avoids Cost • Best Value

12. ANSI/EIA-649 Perspective Purpose Benefits • Allows common sense application of CM principles • De-fuses the terminology issue using Aliases • Sells CM on its Merits • Example: Product attributes are defined • Measurable Performance Parameters • Both Buyer & Seller have common basis for acquisition & use of the product

13. Fundamental CM PrinciplesCM Planning & Management

14. CM Planning & Management Purpose and benefits • To assure that the appropriate CM processes and activities are applied • To establish CM organizational responsibilities • To determine the necessary resources and facilities • To provide a basis for continuous improvement • To enhance the maturity of the enterprises process

15. Configuration Management Processes (ANSI/EIA 649) CM PLANNING & MANAGEMENT CONFIGURATION STATUS ACCOUNTING CONFIGURATION IDENTIFICATION Selection, tailoring, guidance, oversight Attributes, identifiers, baselines CM information & status CONFIGURATION CHANGE MANAGEMENT CM OF DIGITAL DATA CONFIGURATION VERIFICATION/AUDIT Manage changes Assure data integrity Verify performance & consistency

16. CM Planning & Management Be Prepared! EIA 649 - CM Principle #1 • Plan CM processesfor the context and environment in which they are to be performed and manage in accordance with the planning: • Assign Responsibilities/Document procedures • Train personnel • Measure Performance; and • Assess measurements/trends to effect process improvements

17. CM Planning & Management Consistent with ISO10007 - CM Plan • 7.7 Configuration Management Plan • A CMP provides the CM procedures that are to be used and states who will undertake these and when • 8. Configuration Management System Audit • Determine conformity of the applied CM practice to the procedures described in the CM plan 1. Plan 2. Document Procedures 3. Do what you plan

18. FundamentalCM Principles Configuration Identification

19. EIA 649 - CM Principle #8 Configuration Identification • Configuration identification is the basis from which the configuration of products are defined and verified; products and documents are labeled; changes are managed; and accountability is maintained. • Benefits are realized only if there is consistency between the product and the information about the product • Product attributes are • Defined in configuration documentation • Achieved in the product • Verified for consistency between productand documentation

20. Purpose and Benefits ofConfiguration Identification • Determines structure of the product & documentation • Defines performance, interface & other attributes • Provides unique identity to product, components and documentation • Prescribes identification marking • Modifies product and document identifiers to reflect incorporation of major changes

21. Purpose/Benefits, continued • Maintains release control and baseline definition • Provides reference for changes & corrective actions • Correlates document revision level to product configuration • Enables user to distinguish between product versions • Enables service person to correlate product to instructions • Correlates units to warranty/service life

22. Contract Provisions Systems Engineering -Reqmts/Functional Analysis -Allocation & Synthesis Product Structure Configuration Items selected and Requirements allocated Determine CIs Appropriate Configuration Document Types and Baselines selected Logistics Maintenance Plan Document and Item Identifiers assigned Configuration Documentation Approved, Released and Baselined for Change Control by the appropriate Configuration Control Authority Configuration Documentation CM Planning Documented CM Process Select Config. DocTypes/ Baselines Identify Documents & Items Approved Engineering Changes Approve, Release & Baseline Document-ation Configuration Identification Process Activity Model

23. EIA 649 - CM Principle #9 Configuration Identification • Configuration documentation defines the performance, functional and physical attributes of a product. Other product information is derived from configuration documentation. • Two major sets of product information are: • Configuration documentation • Operational Information • Configuration documentation is the product-defining documentation from which operational information and other product information is derived

24. The Product Information Universe Product Information Distribution Configuration Documentation Operational Information Sales Operate Maintain Reqmts Design Build & Test

25. Configuration Identification EIA 649 - CM Principle #15 • All documents reflecting product performance, functional, or physical requirements and other product information are uniquely identified so that they can be correctly associated withthe applicable configuration of the product. • Document identification enables retrieval • Common identifiers include: • Date • Assigned alpha numeric • Revision • Type of document • Title/subject • Originator/Organization • Customer’s contract or PO (if applicable)

26. Configuration Identification EIA 649 - CM Principle #11 • All products are assigned unique identifiers so that • One product can be distinguished from other products • One configuration of a product can be distinguished from another • The source of the product can be determined • The correct product information can be retrieved.

27. Configuration Identification EIA 649 - CM Principle #12 • Individual units of a product are assigned a product unit identifier when there is a need to distinguish one unit of the product from another unit of the product. • Typically by Serial Number • Units serialized, e.g., when: • Customer options • Warranties • Individual testing or screening

28. P/N XYZ, S/N 1??? Configuration Identification EIA 649 - CM Principle #13 • When a product is modified, it retains its original unit identifier even though it’s part identifying number is altered to reflect a new configuration. • It is essential that serialization take place using a non-changing identifier as a base • Nothing degrades CM as much as two products with the identical part numbers and identical serial numbers!!

29. Configuration Identification EIA 649 - CM Principle #14 • A series of like units of a product are assigned a product group identifier when it is unnecessary or impractical to identify individual units but nonetheless necessary to correlateunits to a process, date, event or test. • Typically, by batch or lot number; • In high production, a date code • Enables unit to be correlated totest or process records for the group • Also non-changing base

30. N E W S Configuration Identification EIA 649 Principle #16: • A baseline identifies an agreed-to description of the attributes of a product at a point in time and provides a known configuration to which changes are addressed. EIA 649 Principle #17: • Baselines are established by agreeing to the stated definition of a product’s attributes. • Baselines provide • Assurance of stability & consistency • Common communication of product definition • Ability to transfer authority

31. Requirements Requirements Baseline (Multi-Level) RequirementsImplemented in Design VerifiedProductConfiguration Design Release Baseline Product Configuration Baseline Configuration Identification EIA 649 Principle #18: • The configuration of any product, or any document, plus the approved changes to be incorporated is the current baseline.

32. Let’s interface Configuration Identification EIA 649 Principle #20: • For product interfaces external to the enterprise, establish an interface agreement and a mutually agreed-to documentation of common attributes. • In Buyer/Seller relationship, interface definition is part of purchase agreement • If no direct relationship exists, an interface agreement is negotiated • Documentation = ICD • Procedures may include an ICWG

33. System Interfaces SYSTEM A • Interfaces within CIs CI a • A-B Same Contract SYSTEM B Assembly Part 12 CI b • A-C Same Customer • Different Contract P1 P2 P3 P4 P4 SYSTEM C CI c • Interfaces Between CIs • Part from Supplier • CI from Supplier • A-D Different Customer Different Contract SYSTEM D CI c Supplier Interfaces Understanding the Levels of Interface

34. Fundamental CM Principles Configuration Control (Configuration Change Management)

35. Configuration Change Management EIA 649 Principle # 21 • Changes to a product are accomplished using a systematic, measurable change process. • Process includes • Identifying need for change • Documenting impact • Evaluation & Coordination • Incorporation of approved change • Verification • Also encompasses management of variances

36. Purpose and Benefits Enable change decisions to be based on knowledge of completechange impact Limit changes to those which are necessary or offer significant benefit Facilitate evaluation of cost, savings & trade-offs Ensure customer interests are considered Provide orderly communication of change information Preserve configuration control at product interfaces Maintain and control a current configuration baseline Maintain consistency between product and documentation Document and limit variances Facilitate continued supportability of the product after change EIA 649Configuration Change Management

37. Configuration Change Management Current Baseline New Current Baseline Change Identification Need for Change Approved Change Evaluation & Coordination Documented Change Request EIA 649 Change Management Process Model Implementation & Verification

38. Contractual Provisions Govt. Need for Change Request Government for ECP Configuration Control Current Initiation Configuration Control Authority Contractor- C Need for Responsible Change to Change Ident, Government Documentation Contractor Baseline & Disposition Contractor Need for Configuration Change Control ECPs, RFDs Approved ECPs, RFDs & C Implementing Direction/ CM Mgmt Government Authorization Communication Configuration Control Evaluation & Disposition (Fig. 4-4) Approved Configuration Documentation C (Current Status & Documented Baselines) Configuration CM Process Information C Configuration Control Process Activity Model

39. 1 23 4 Configuration Change Management EIA 649 Principle #22 • Each change is uniquely identified • Objectives of change identification • Description and impact sufficient for evaluation • Choose appropriate format • Provide unique identifier for the change

40. Configuration Change Management EIA 649 Principle #23 • Changes represent opportunities for improvement • Changes initiated to: • Provide new capabilities • Enhance product support • Insert technology • Effect improvements • Correct defects or deficiencies • Reduce cost, improve efficiency

41. Classify changes to aid in determining the appropriate levels of review and approval. Tabulated “best practice”factors differentiate between: Major & Minor changes Requirement for external customerreview in addition to internal review Configuration Change Management EIA 649 Principle #24

42. I thought I knew it all ! Configuration Change Management EIA 649 Principle #26 • Consider technical, support, schedule, and cost impacts of a requested change before making a judgment as to whether a change should be approved for implementation and incorporation in the product and its documentation. • Change evaluation and coordination process • Reviewing the preliminary impact assessments • Determining change effectivity • Establishing the cost/price • Dispositioning the change

43. Configuration Change Management EIA 649 Principle #27 • Determine all potential effects of a change and coordinate potential impacts with the impacted areas of responsibility. • Impact Assessment • Details what is affected • Ensures that all potential effects are known • Is essential to determine effectivity

44. Configuration Change Management • Change Boards are a common means of achieving coordination necessary for impact assessment and change evaluation • Change Board characteristics: • Chaired by someone with authority to commit the resources of the enterprise to implementing the change • Members represent functional activities or product development teams... and have authority to commit the group they represent • Agendas & documents ....distributed in advance • Board direction & decisions ...documented and disseminated • Board actions commonly accomplished electronically

45. I like this date, it’s my birthday. Where’s the instructions? Configuration Change Management EIA 649 Principle #28 • Change documentation delineates which unit(s) of the product are to be changed. Change effectivity includes production break-in and retrofit/recall, as applicable. • A changed product should not be distributed until its support and service areas are able to support it. • Effectivity determination requires • Knowledge of lead times • Balancing of many factors EIA 649 Principle #29

46. Configuration Change Management • Effectivity delineates which units are to be changed • Effectivity is commonly expressed by • Product unit identifying number (e.g., serial number) • Production date • Product group identifier (e.g., lot, batch) • Model Year • Model Designation • Version number

47. Configuration Change Management EIA 649 Principle #30 • The decision maker is aware of all cost factors in making the decision. • Prerequisites: • Impact assessment • Effectivity • CM process identifies • Immediate cost of change • Expected cost/savings in future • All cost factors are considered

48. Configuration Change Management EIA 649 Principle #31 • Change approval decisions are made at an appropriate organizational level with the authority to commit necessary resources to implement the change. • Approval authority delegated to different levels, based on classification • As the life cycle progresses, authority typically transitions toward higher fiscal responsibility • Each organization establishes its own change authority levels

49. Implement an approved change in accordance with documented direction approved by the appropriate level of authority. Planning for change implementation is Initiated during change evaluation Detailed after change is approved Implementation involves Release of new or revised configuration documentation and other affected product information Change incorporation into product Update of operation and support elements Configuration Change Management EIA 649 Principle #32

50. Product Product Information Configuration Change Management EIA 649 Principle #33 • Verify implementation of a change to assure consistency between the product, its documentation and its support elements. • Verification may be means of: • Detailed audit of product to documentation • Validation of installation or modification instructions • Validation of operation and maintenance instructions • Testing • or, a simple inspection