《GEIA-TB-0002-2008.pdf》由会员分享，可在线阅读，更多相关《GEIA-TB-0002-2008.pdf（30页珍藏版）》请在三一文库上搜索。
1、 ITAA ENGINEERING BULLETIN GEIA-TB-0002 System Configuration Management mplementation Template I (Oriented for a US Military Contract Environment) GEIA-TB-0002 June 2008 INFORMATION TECHNOLOGY ASSOCIATION OF AMERCIA Copyright Government Electronics and via several teleconference collaboration phone
2、calls to accomplish the approach and technical content reflected in this Bulletin. Special acknowledgement goes to each of the following members of the working group: Mr. Mitch Kaarlela Lockheed Martin Mr. Dwayne Hardy DoD Systems Engineering Office Mr. Jason Baggett US Army Mr. Jerry Baldwin NASA M
3、s. Marita Berg-Gustafsson Ericsson Ms. Deborah Cornelius US Army Mr. Tom Giblin DRS S thus achieving a sequential, time-phased CM implementation template. The template is envisioned to be used by Industry to train new CM practitioners on what CM things to do in what order, and by Government personne
4、l to assess individual program CM achievement compared to an Industry-agreed upon time-phased template. Think of this template as another “tool” in the CM practitioners toolbox. The format of the resulting template naturally transitioned to a table to most efficiently convey the information. A listi
5、ng of the acronyms used is provided. The information conveyed by the Bulletin is provided for GUIDANCE. It is organized by the DoDI 5000 series acquisition phases of Concept Refinement, Technology Development, System Development and in some cases specifically lists acquisition milestones such as SDD
6、 Contract Award. The order of the information should be understood to be Top-Down in sequence, with not every activity applicable to every contract or situation depicted. Note: This first iteration is focused on a US military contract environment, with subsequent updates to consider adding detail ap
7、propriate for commercial, other US government (NASA or FAA) and/or other functional areas (e.g., Data Management and Systems Engineering). What is Configuration Management? Configuration Management (CM) is a process for establishing, controlling and maintaining consistency of a products functional,
8、performance, and physical attributes; with its requirements, design and operational information throughout the products life cycle. A primary objective of CM is to assure that a product performs as intended; and its physical attributes are adequately identified and documented to a level of detail su
9、fficient to repeatably produce the product, and meet anticipated needs for operation, quality management, maintenance, repair, and replacement. The CM process explicitly facilitates orderly management of product change (e.g., extend capability, improve performance/reliability/ maintainability, exten
10、d service life, reduce cost, and correct defects). CM also involves the recording and reporting of configuration information to assist in the support and maintenance of delivered products. The relative cost of implementing CM is normally offset many times over in cost avoidance. See EIA-STD-649A and
11、 its Handbook for more details on CM. 1 Copyright Government Electronics with the “when” of CM correlated to DoD acquisition phases and milestones thereby giving a time-phased depiction. The document spreadsheet should be read from top to bottom. It shows both the CM activities and products that sho
12、uld be performed and accomplished on a program or project. Next it provides a brief description of the CM activity or product and a column providing a reference(s) to other sources of information to learn even more about how the activity or product should be accomplished. Also included is a column f
13、or suggested level of CM control to be applied to the activity/product, from an Industry perspective. Future iterations will include a more complete dataset covering columns for entry criteria, exit criteria and related products from other skillcodes/disciplines. This Bulletin also has future consid
14、erations for a couple of specific examples regarding how to use the document (i.e., a day in the life), from start to finish, assuming different CM user skill levels are involved. Pictorial Diagram This Bulletin is intended to “bridge” the CM standards and the DoD Acquisition milestones for WBS see
15、MIL-HDBK-881 Author control 9 Technology Development Phase ASRCM Tool in an Integrated Data Environment (IDE). Document the CM tools to be used in the CM Plan, describe how the CM tools will be integrated and the CM data exchange methodology to be used. See EIA-STD-836A for CM Data Exchange No Indus
16、try Std on CM tool usage, consult Industry CM Tool Sales Reps for features 3.8; Apps G require formal proposal, analysis, coordination, change board disposition and negotiation/Purchase Order (PO) update. EIA-HDBK-649 Annex 7 Higher Tier CCB control 12 Technology Development Phase SRR Estimate CM La
17、bor Reqd - Set CM Budget During a proposal effort for either this TD phase - but certainly in the planning for a SDD contract - the CM team must perform a thorough review of the contractual requirements for CM and for internal best practices to scope and estimate the budget needed by the CM team. Co
18、nsider the CM labor categories, CM knowledge, CM skills EIA-HDBK-649 Section 5.1.3; MIL-HDBK-61A, Paragraph 4.3.1 Author + Supervisor control 13 Technology Development Phase SRRDraft Part/Doc Number Schema CM, in concert with program (project) Systems Engineering and Data Architecture, will produce
19、a draft product identification plan for CI/CSCIs, documents, drawings and digital data files for a program. Try to avoid building-in intelligence (significant numbering) in the part/document numbering schemes. The selected scheme should be based upon established organizational policy unless some cha
20、nges were made in SDD Contract negotiations after proposal submittal. EIA-HDBK-649 Section 5.1 plus NAVAIRINST.4130.1D and MIL-STD-973 App. A; and IEEE-STD-828-1998 (for SW CM Plans) CCB + Customer control System Development Config Ident considerations can include but are not limited to - product st
21、ructure EIA- STD-649A Section 5.2; EIA- HDBK-649 Section 5.2 Lower Tier Chg Bd control 19 System Development and EIA-HDBK-649 Section 5.2 Lower Tier Chg Bd control 20 System Development CMMI Higher Tier CCB control 23 System Development these items come under configuration control per the program CM
22、 Plan and are stored according to the program data management strategy (typically in electronic servers, vaults, libraries, etc.). CM typically is the control agent for the offiicial baselined items listings and for officially vaulted documentation. CM should regularly communicate the official statu
23、s of baselined items and documentation to the rest of the program (project). CM should CAUTION design groups not to release product designs prematurely (especially due to schedule pressure), as once the original release has occurred, the Config Change Mgmt system engages. CM should monitor a “number
24、 of changes per original release“ metric. A special Software Development EIA-STD-649A; EIA-HDBK-649; NAVAIRINST 4130.1D Higher Tier CCB control 27 System Development define which Configuration Items (CIs) are under Change Board Control, define the levels of change boards (if applicable), and define
25、what baselines your program intends to use, when and IEEE-STD-828-1998 (for SW CM Plans) CCB + Customer control 11 Copyright Government Electronics 3.8; Apps G and design release data from CDR. Update and designate the FCA/PCA Plan as officially released and baselined. Publish the FCA/PCA Plan to al
26、l program personnel for use in their associated program activities. MIL-STD-1521 Sections 3.7; 3.8; Apps G and MIL-STD-973 Section 5.6.2 5.5.1 ANSI/IEEE STD-1028 Sect 8 Audits (S/W process IEEE STD-1042 Sect 3.4.3 Reviews (Software CM); EIA-HDBK-649 Annex 4 Author + Supervisor control 44 System Deve
27、lopment and EIA-HDBK-649 App A 5.4.2 Author + Supervisor control 46 System Development and EIA-HDBK-649 App A 5.4.2 Author + Supervisor control 47 System Development MIL-STD-1521 Sect 3.10; AFSCR 84-2; NAVAIRINST 4355.19C Author + Supervisor control 14 Copyright Government Electronics SW Metrics SEI
28、 Curriculum Module SEI-CM-12-1.1; EIA-HDBK-649 Sect 5.1.6 IEEE STD-1044.1 Not Applicable 49 50 Production MIL-STD-1521 App H Sect 80; NAVAIRINST 4355.19C Author + Supervisor control 51 Production and the software, interface and database design documents for software. It also includes by reference, t
29、he material the selected functional characteristics for production acceptance testing; the production acceptance test reqts; and all allocated configuration documentation pertaining to the product/item, so that if the item were to be re-procured, the performance requirements for the item would also
30、be included. The Product Baseline is the agreed-to technical departure point which serves as a basis for defining and managing proposed future change(s) to the product as it enters productio MIL-HDBK-61A Sect. 5.5.1 and MIL-STD-973 Sect 3.74 CCB + Customer control Production EIA-HDBK-649 Sect 5.4; E
31、IA-STD-836A Author + Supervisor control 53 Production EIA-STD-649A: and EIA-STD-836A CCB + Customer control 56 Production EIA-HDBK-649 Sect 5.4; and EIA-STD-836A Author + Supervisor control 57 Production Sects 5.5.1 ANSI/IEEE STD-1028 Sect 8 Audits (software process and product); IEEE 1042 section 3
32、.4.3 Reviews (Software CM) Author + Supervisor control 59 60Operation plus any approved changes, non-conformances, or other alterations to the delivered technical configuration or data. Best business practice CCB + Customer control 62Operation MIL-HDBK-61A Sect 6.1; EIA-HDBK-649 Sect 5.3; NAVAIRINST
33、 4130.1D CCB + Customer control 63Operation & Support PhaseN/A Monitor CM Metrics & Suggest Corrective Action (as reqd) CM should monitor the meaningful metrics prepared by the program (project). If a negative trend(s) is observed, then prepare ideas for investigating the root-cause of the negative
34、trend and work with the area responsible to prepare corrective action plan(s). Best business practiceNot Applicable 64Operation & Support PhaseN/A Perform CM activities associated with Mod Kits and Retrofit actions Perform all or a subset of the CM tasks already listed herein for the modification ki
35、t and retrofit actions on the program (project). CM can treat Mod & Retrofit activities as “mini-programs“ such that many of the CM tasks are performed, just on a smaller scale or shorter turnaround timeline. EIA-HDBK-649 Sect 5.2.3.2 and 5.3.1.2.2 Not Applicable Operation & Support Phase 17 Copyrig
36、ht Government Electronics & Information Technology Association Provided by IHS under license with GEIA Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 04:02:56 MDTNo reproduction or networking permitted without license from IHS -,-,- System CM Implementation Template GEIA-TB-0002 DoDI 5000
37、Acq Phase or Specific Milestone Closest or Most- Relevant Program or Tech Review CM Product(s) & ActivitiesProduct / Activity DescriptionRef. Source Data Level of CM Control 65Operation & Support PhaseOTRR Review the TDP for any changes (not a “traditional CM“ task, but something CM must at least be
38、 aware of and may contribute toward) The Operational Test Readiness Review (OTRR) is a formal review to establish readiness for Initial Operational Test and Evaluation (IOT&E) and is typically only held when it is contractually required. Whether a formal review is held or not, the Technical Data Pac
39、kage (TDP) must be examined closely for any changes that have occurred since the TDP was baselined and if those changes have been properly captured and implemented. Changes to the TDP may include hardware, software, logistics, drawings, specifications any element of the approved TDP. COTS products s
40、hould be reviewed for obsolence issues. If no formal review is scheduled this activity may be done as a stand-alone activity or combined with another activity such as preparation for the PCA or FCA. MIL-STD-973 5.3.4.2 Author + Supervisor control 18 Copyright Government Electronics & Information Tec
41、hnology Association Provided by IHS under license with GEIA Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 04:02:56 MDTNo reproduction or networking permitted without license from IHS -,-,- System CM Implementation Template * * Acronyms List * * GEIA-TB-0002 A ASMEAmerican Society of Mecha
42、nical Engineers ASRAlternative Systems Review B B/LBaseline C CCBConfiguration Control Board or Change Control Board CDRCritical Design Review CIConfiguration Identification or Configuration Item CMConfiguration Management CMMICapability Maturity Model Integrated CMPConfiguration Management Plan COT
43、SCommercial Off-The-Shelf CRChange Request or Concept Refinement CSAConfiguration Status Accounting CSCIComputer Software Configuration Item D DoDIDepartment of Defense Instruction (e.g., DoDI-5000) E EIAElectronics Industry Association (predecessor to GEIA) ECNEngineering Change Notice ECPEngineeri
44、ng Change Proposal EVMSEarned Value Management System F FAIFirst Article Inspection FCAFunctional Configuration Audit FRPFull Rate Production FRRFlight Readiness Review G GAOGovernment Accounting Office GEIAGovernment Electronics and Information-Technology Association GFEGovernment Furnished Equipme
45、nt GFPGovernment Furnished Property H HDBKHandbook HWHardware I IBRIntegrated Baseline Review ICDInterface Control Document IDEIntegrated Data Environment IOT&EInitial Operational Test and Evaluation ITAAInformation Technology Association of America (new parent of GEIA) ISRIn-Service Review ITARInte
46、rnational Traffic in Arms Regulations 19 Copyright Government Electronics & Information Technology Association Provided by IHS under license with GEIA Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 04:02:56 MDTNo reproduction or networking permitted without license from IHS -,-,- System CM
47、 Implementation Template * * Acronyms List * * GEIA-TB-0002 ITRInitial Technical Review IUIDItem Unique IDentification L LRIPLow Rate Initial Production M MILMilitary MOAMemorandum Of Agreement MOUMemorandum Of Understanding O O&SOperations & Support OTRROperational Test Readiness Review P PCAPhysic
48、al Configuration Audit P&DProduction & Deployment PDMProduct Data Manager (function provided by a computer tool) PDRPreliminary Design Review PMOProgram Management Office POPurchase Order PRRProduction Readiness Review S SCMSoftware Configuration Management SDDSystem Development and Demonstration SD
49、LSoftware Development Libraries SFRSystem Functional Review SOOStatement of Objectives SOWStatement of Work SRRSystem Requirements Review SVRSystem Verification Review S/WSoftware T TDTechnology Development TDPTechnical Data Package TRATechnology Readiness Assessment TRRTest Readiness Review U UIDUnique IDentification 20 Copyright Government Electronics & Information Technology Association Provided by IHS under license with GEIA Licensee=