GEIA-TB-0002-2008 System Configuration Management I mplementation Template (Oriented for a US Military Contract Environment) (Formerly TechAmerica GEIA-TB-0002)《系统配置管理I执行模板(以美国军方合同.pdf

《GEIA-TB-0002-2008 System Configuration Management I mplementation Template (Oriented for a US Military Contract Environment) (Formerly TechAmerica GEIA-TB-0002)《系统配置管理I执行模板(以美国军方合同.pdf》由会员分享，可在线阅读，更多相关《GEIA-TB-0002-2008 System Configuration Management I mplementation Template (Oriented for a US Military Contract Environment) (Formerly TechAmerica GEIA-TB-0002)《系统配置管理I执行模板(以美国军方合同.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 c

2、alls 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 Ms

3、. 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 personnel

4、 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 listin

5、g 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 app

7、ropriate 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, p

8、erformance, 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 suf

9、ficient 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, extend

10、 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 shou

12、ld 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 fo

13、r 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 conside

14、rations 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 M

15、IL-HDBK-881Author control9Technology Development PhaseASR CM 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 ExchangeNo Industry St

16、d 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 7Higher Tier CCB control12Technology Development PhaseSRREstimate CM Labor Reqd -Se

17、t 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 review 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

18、labor categories, CM knowledge, CM skills EIA-HDBK-649 Section 5.1.3; MIL-HDBK-61A, Paragraph 4.3.1Author + Supervisor control13Technology Development PhaseSRR Draft Part/Doc Number SchemaCM, in concert with program (project) Systems Engineering and Data Architecture, will produce a draft product id

19、entification 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 changes were made in

20、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 controlSystem Development Config Ident considerations can include but are not limited to - product structure EIA-STD-649A

21、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 Development CMMIHigher Tier CCB control23System Development these items come under configuration control per the program CM Plan and are stored according t

22、o 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 status of baselined items and documen

23、tation 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 of changes per original release

24、“ metric. A special Software Development EIA-STD-649A;EIA-HDBK-649;NAVAIRINST 4130.1DHigher Tier CCB control27System Development define which Configuration Items (CIs) are under Change Board Control, define the levels of change boards (if applicable), and define what baselines your program intends t

25、o use, when and IEEE-STD-828-1998 (for SW CM Plans)CCB + Customer control11Copyright 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 all program personnel for use in their ass

26、ociated program activities.MIL-STD-1521 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 + Su

27、pervisor control46System Development andEIA-HDBK-649 App A 5.4.2Author + Supervisor control47System Development MIL-STD-1521 Sect 3.10; AFSCR 84-2;NAVAIRINST 4355.19CAuthor + Supervisor control14Copyright Government Electronics SW Metrics SEI Curriculum Module SEI-CM-12-1.1;EIA-HDBK-649 Sect 5.1.6 I

28、EEE 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 reference, the material the selected functional characteristics for production

29、 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 be included. The Product Baseline is the agreed-to technical depar

30、ture 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.4;EIA-STD-836AAuthor + Supervisor control53Production EIA-STD-649A: andEI

31、A-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 Reviews (Software CM)Author + Supervisor control5960 Operation plus any appro

32、ved 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 + Customer control63 Operation & Support Phase N/AMonitor CM Metrics & Sugge

33、st 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 with the area responsible to prepare corrective action plan(s).Best busines

34、s 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 actions on the program (project). CM can treat Mod & Retrofit activities as

35、“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 Phase17Copyright Government Electronics & Information Technology Association Provided by IHS under license wit

36、h GEIA Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-System CM Implementation TemplateGEIA-TB-0002DoDI 5000 Acq Phaseor Specific MilestoneClosest or Most-Relevant Program or Tech ReviewCM Product(s) & Activities Product / Activity Description Ref. Source DataLeve

37、l of CM Control65 Operation & Support Phase OTRRReview the TDPfor any changes(not a “traditional CM“ task,but something 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 Evaluat

38、ion (IOT&E) and is typically only held when it is contractually required. Whether a formal review is held or not, the Technical 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.

39、 Changes to the TDP may include hardware, software, logistics, drawings, specifications any element of the approved TDP. 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

40、as preparation for the PCA or FCA.MIL-STD-973 5.3.4.2Author + Supervisor control18Copyright Government Electronics & Information Technology Association Provided by IHS under license with GEIA Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-System CM Implementation

41、Template* * 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 Ca

42、pability Maturity 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 Asso

43、ciation (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 Electronics a

44、nd Information-Technology AssociationGFE Government Furnished EquipmentGFP Government Furnished PropertyHHDBK HandbookHW HardwareIIBR Integrated Baseline ReviewICD Interface Control DocumentIDE Integrated Data EnvironmentIOT&E Initial Operational Test and EvaluationITAA Information Technology Associ

45、ation of America (new parent of GEIA)ISR In-Service ReviewITAR International Traffic in Arms Regulations19Copyright Government Electronics & Information Technology Association Provided by IHS under license with GEIA Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-S

46、ystem CM Implementation Template* * Acronyms List * *GEIA-TB-0002ITR Initial Technical ReviewIUID Item Unique IDentificationLLRIP Low Rate Initial ProductionMMIL MilitaryMOA Memorandum Of AgreementMOU Memorandum Of UnderstandingO O&S Operations & SupportOTRR Operational Test Readiness ReviewPPCA Phy

47、sical Configuration AuditP&D Production & DeploymentPDM Product Data Manager (function provided by a computer tool)PDR Preliminary Design ReviewPMO Program Management OfficePO Purchase OrderPRR Production Readiness ReviewSSCM Software Configuration ManagementSDD System Development and DemonstrationS

48、DL Software Development LibrariesSFR System Functional ReviewSOO Statement of ObjectivesSOW Statement of WorkSRR System Requirements ReviewSVR System Verification ReviewS/W SoftwareTTD Technology DevelopmentTDP Technical Data PackageTRA Technology Readiness AssessmentTRR Test Readiness ReviewUUID Un

49、ique IDentification20Copyright Government Electronics & Information Technology Association Provided by IHS under license with GEIA Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ITAA Document Improvement Proposal If, in the review or use of this document, a potential change is made evident for safety, health, or technical reasons please fill in the appropriate information below and mail or FAX to: Information Technology Asso