SAE GEIA-TB-0002-2008 System Configuration Management I mplementation Template (Oriented for a US Military Contract Environment) (Formerly TechAmerica GEIA-TB-0002).pdf

《SAE GEIA-TB-0002-2008 System Configuration Management I mplementation Template (Oriented for a US Military Contract Environment) (Formerly TechAmerica GEIA-TB-0002).pdf》由会员分享，可在线阅读，更多相关《SAE GEIA-TB-0002-2008 System Configuration Management I mplementation Template (Oriented for a US Military Contract Environment) (Formerly TechAmerica GEIA-TB-0002).pdf（30页珍藏版）》请在麦多课文档分享上搜索。

1、 TechAmerica Engineering Bulletin System Configuration Management Implementation Template (Oriented for a US Military Contract Environment) GEIA-TB-0002 June 2008 GEIA-TB-0002NOTICE TechAmerica Engineering Standards and Publications are designed to serve the public interest by eliminating misunderst

2、andings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchasers in selecting and obtaining with minimum delay the proper product for their particular needs. Existence of such Standards and Publications shall not in any respect p

3、reclude any member or nonmember of TechAmerica from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TechAmerica members, whether the standard is to be used

4、 either domestically or internationally. Standards and Publications are adopted by TechAmerica in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TechAmerica does not assume any liability to any patent owner, nor does it assume any obligation whatever

5、to parties adopting the Standard or Publication. Technical Publications are distinguished from TechAmerica Standards in that they contain a compilation of engineering data or information useful to the technical community and represent approaches to good engineering practices that are suggested by th

6、e formulating committee. This Bulletin is not intended to preclude or discourage other approaches that similarly represent good engineering practice, or that may be acceptable to, or have been accepted by, appropriate bodies. Parties who wish to bring other approaches to the attention of the formula

7、ting committee to be considered for inclusion in future revisions of this publication are encouraged to do so. It is the intention of the formulating committee to revise and update this publication from time to time as may be occasioned by changes in technology, industry practice, or government regu

8、lations, or for other appropriate reasons. (Formulated under the cognizance of the TechAmerica G-33 Configuration/Data Management Committee.) Published by 2011 TechAmerica Standards and via several teleconference collaboration phone calls to accomplish the approach and technical content reflected in

9、 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 Ms. Marita Berg-Gustafsson Ericsson Ms. Deborah Cornelius US Army Mr

10、. 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 personnel to assess individual program CM achievement compared to an Indust

11、ry-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 listing of the acronyms used is provided. The information conveyed by th

12、e 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 Contract Award. The order of the information should be understood

13、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 appropriate for commercial, other US government (NASA or FAA) and/or

14、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, performance, and physical attributes; with its requirements, design

15、 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 sufficient to repeatably produce the product, and meet anticipated ne

16、eds 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, extend service life, reduce cost, and correct defects). CM also involves

17、 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 its Handbook for more details on CM. 1 GEIA-TB-0002 2 How to Use t

18、his Document This Bulletin is initially intended to be used to convey a combination of information to CM practitioners, both new and already skilled personnel alike. It provides the “what” of CM products and activities; with the “when” of CM correlated to DoD acquisition phases and milestones thereb

19、y giving a time-phased depiction. The document spreadsheet should be read from top to bottom. It shows both the CM activities and products that should 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 re

20、ference(s) to other sources of information to learn even more about how the activity or product should be accomplished. Also included is a column for suggested level of CM control to be applied to the activity/product, from an Industry perspective. Future iterations will include a more complete data

21、set covering columns for entry criteria, exit criteria and related products from other skillcodes/disciplines. This Bulletin also has future considerations 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

22、skill levels are involved. Pictorial Diagram This Bulletin is intended to “bridge” the CM standards and the DoD Acquisition milestones for WBS see MIL-HDBK-881Author control9Technology Development PhaseASR CM Tool in an Integrated Data Environment (IDE). Document the CM tools to be used in the CM Pl

23、an, describe how the CM tools will be integrated and the CM data exchange methodology to be used.See EIA-STD-836A for CM Data ExchangeNo Industry Std on CM tool usage, consult Industry CM Tool Sales Reps for features 3.8; Apps G require formal proposal, analysis, coordination, change board dispositi

24、on and negotiation/Purchase Order (PO) update.EIA-HDBK-649 Annex 7Higher Tier CCB control12Technology Development PhaseSRREstimate CM Labor Reqd -Set CM BudgetDuring a proposal effort for either this TD phase - but certainly in the planning for a SDD contract - the CM team must perform a thorough re

25、view of the contractual requirements for CM and for internal best practices to scope and estimate the budget needed by the CM team. Consider the CM labor categories, CM knowledge, CM skills EIA-HDBK-649 Section 5.1.3; MIL-HDBK-61A, Paragraph 4.3.1Author + Supervisor control13Technology Development P

26、haseSRR Draft Part/Doc Number SchemaCM, in concert with program (project) Systems Engineering and Data Architecture, will produce 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)

27、in the part/document numbering schemes. The selected scheme should be based upon established organizational policy unless some changes 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 S

28、W CM Plans)CCB + Customer controlSystem Development Config Ident considerations can include but are not limited to - product structure EIA-STD-649A Section 5.2; EIA-HDBK-649 Section 5.2Lower Tier Chg Bd control19System Development and EIA-HDBK-649 Section 5.2Lower Tier Chg Bd control20System Develop

29、ment CMMIHigher Tier CCB control23System Development these items come under configuration control per the program CM 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 b

30、aselined items listings and for officially vaulted documentation. CM should regularly communicate the official status 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 pres

31、sure), as once the original release has occurred, the Config Change Mgmt system engages. CM should monitor a “number of changes per original release“ metric. A special Software Development EIA-STD-649A;EIA-HDBK-649;NAVAIRINST 4130.1DHigher Tier CCB control27System Development define which Configurat

32、ion Items (CIs) are under Change Board Control, define the levels of change boards (if applicable), and define what baselines your program intends to use, when and IEEE-STD-828-1998 (for SW CM Plans)CCB + Customer control11System CM Implementation TemplateGEIA-TB-0002DoDI 5000 Acq Phaseor Specific M

33、ilestoneClosest or Most-Relevant Program or Tech ReviewCM Product(s) 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 all program personnel for use in their associated program activities.MIL-STD-1521

34、 Sections 3.7; 3.8; Apps G andMIL-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 4Author + Supervisor control44System Development andEIA-HDBK-649 App A 5.4.2Author + Supervisor control46System Development an

35、dEIA-HDBK-649 App A 5.4.2Author + Supervisor control47System Development MIL-STD-1521 Sect 3.10; AFSCR 84-2;NAVAIRINST 4355.19CAuthor + Supervisor control14System CM Implementation TemplateGEIA-TB-0002DoDI 5000 Acq Phaseor Specific MilestoneClosest or Most-Relevant Program or Tech ReviewCM Product(s

36、) SW Metrics SEI Curriculum Module SEI-CM-12-1.1;EIA-HDBK-649 Sect 5.1.6 IEEE STD-1044.1Not Applicable4950Production MIL-STD-1521 App H Sect 80; NAVAIRINST 4355.19CAuthor + Supervisor control51Production and the software, interface and database design documents for software. It also includes by refe

37、rence, the 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 wou

38、ld also 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 productioMIL-HDBK-61A Sect. 5.5.1 and MIL-STD-973 Sect 3.74CCB + Customer controlProduction EIA-HDBK-649 Sect 5

39、.4;EIA-STD-836AAuthor + Supervisor control53Production EIA-STD-649A: andEIA-STD-836ACCB + Customer control56Production EIA-HDBK-649 Sect 5.4; andEIA-STD-836AAuthor + Supervisor control57Production Sects 5.5.1 ANSI/IEEE STD-1028 Sect 8 Audits (software process and product);IEEE 1042 section 3.4.3 Rev

40、iews (Software CM)Author + Supervisor control5960 Operation plus any approved changes, non-conformances, or other alterations to the delivered technical configuration or data.Best business practiceCCB + Customer control62 Operation MIL-HDBK-61A Sect 6.1;EIA-HDBK-649 Sect 5.3;NAVAIRINST 4130.1DCCB +

41、Customer control63 Operation & Support Phase N/AMonitor 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 trend and work w

42、ith the area responsible to prepare corrective action plan(s).Best business practice Not Applicable64 Operation & Support Phase N/APerform CM activities associated with Mod Kits and Retrofit actionsPerform all or a subset of the CM tasks already listed herein for the modification kit and retrofit ac

43、tions 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.2Not ApplicableOperation & Support Phase17System CM Implementation Temp

44、lateGEIA-TB-0002DoDI 5000 Acq Phaseor Specific MilestoneClosest or Most-Relevant Program or Tech ReviewCM Product(s) & Activities Product / Activity Description Ref. Source DataLevel of CM Control65 Operation & Support Phase OTRRReview the TDPfor any changes(not a “traditional CM“ task,but something

45、 CM must atleast be aware of and maycontribute 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 T

46、echnical Data Package (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

47、. COTS products should 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.2Author + Supervisor control18System CM Implementation Template* *

48、Acronyms List * *GEIA-TB-0002AASME American Society of Mechanical EngineersASR Alternative Systems ReviewB B/L BaselineCCCB Configuration Control Board or Change Control BoardCDR Critical Design ReviewCI Configuration Identification or Configuration ItemCM Configuration ManagementCMMI Capability Mat

49、urity Model IntegratedCMP Configuration Management PlanCOTS Commercial Off-The-ShelfCR Change Request or Concept RefinementCSA Configuration Status AccountingCSCI Computer Software Configuration ItemD DoDI Department of Defense Instruction (e.g., DoDI-5000)E EIA Electronics Industry Association (predecessor to GEIA)ECN Engineering Change NoticeECP Engineering Change ProposalEVMS Earned Value Management SystemFFAI First Article InspectionFCA Functional Configuration AuditFRP Full Rate ProductionFRR Flight Readiness ReviewGGAO Government Accounting OfficeGEIA Government Ele