AIR FORCE AFMC PAM 63-104-1994 IWSM CONFIGURATION MANAGEMENT IMPLEMENTATION GUIDE《IWSM技术状态管理执行指南》.pdf

《AIR FORCE AFMC PAM 63-104-1994 IWSM CONFIGURATION MANAGEMENT IMPLEMENTATION GUIDE《IWSM技术状态管理执行指南》.pdf》由会员分享，可在线阅读，更多相关《AIR FORCE AFMC PAM 63-104-1994 IWSM CONFIGURATION MANAGEMENT IMPLEMENTATION GUIDE《IWSM技术状态管理执行指南》.pdf（112页珍藏版）》请在麦多课文档分享上搜索。

1、BY ORDER OF THE COMMANDER AFMC PAMPHLET 63-104 AIR FORCE MATERIEL COMMAND II lWSM CONFIGURATION MANAGEMENT IMPLEMENTATION GUIDE 30 June 1994 Revis I- 44 4 lull I t.1 OPR: HQ AFMCIENP (Mr. Michael G. Ucchino) Pages: 113/Distribution: F;X Certified by: (Mr. Michael A. Delisio) AUUALDEA, Maxwell AFB AL

2、 361 12-5564-1 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-FOREWORD The Systems Engineering/Configwation Management (SE/CM) Process Action Team (PAT) developed an integrated, “lust-to-dust,“ SE/CM prows to support Integrated Weapons System Manage

3、ment (IWSM). As part of this effort, tlnee Configuration Management precesses were defined by process analysis papas (PAPS). PAPS #11, #14, and #24 defined the Technical Baseline Definition and Maintenance, the Configuration Control Board, and the Interface Management processes, respectively. Prepar

4、ed by the Coflguration Management SubPAT in conjunction with the SE/CM PAT, this pamphlet provides implementation midance for the three IWSM Confiuration aageknt PAPS. It delopient, but will be manag Command, Control, Computer, and Communications Systems: electronic countermeasures pods). Commodity

5、Types: Within each commodity category, then are two basic types of commodities: simple and complex. Both are managed cradle-to-grave. Simule Commodities: Are technically stable with aggregate management focus on procurement, stock, store, and issue. Comalex Comrnoditie2: Require con development and

6、acquisition, are usually high cost, are technically complex, and may have unique management requirements (e.g., engines, Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-munitions, life support, electronic warfare, automatic test equipment, and traine

7、rs/training systems). Complex commodities are subjected to the concepts and princiks of IWSM. 4. Configuration Baseline Data: A technical description of an item adequate for supporting an acquisition strategy, production, engineering, and logistics support The * Verify conformance to conb-act techni

8、cal requirements and change implementation direction: - - - - - . . w Control ihanges/departures to the configuration baselines and associated data; Record and report changeddcpartures fiom the configuration baseIinu: Coordinate all CCBnCWG activities: * Provide requirements traceability for complet

9、e system life cycle; Provide process to archive and maintain all Technical Baseline Data. 7. Decision Support Data: The documentation developed for use in each fife cycle phase to make prograndtechnical decisions. This includes design analysis, rovisioninn data, concet/anning/requuements data, sched

10、ules, test i.e., Milestone 1, 11, and Ill Data Packages, BDPs, MDRPs, and tow Cost TDPs. The data support acquisition, test and evaluation, operation, maintenance, repair, reprocurement, modification, and other actions. TECHNICAL EASELINE I I CONFIGURATION BASELINE DECISION SUPPORT DATA DATA Provide

11、d by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ACRONYMS I ST ART ACAT ACSN ADM ADP AELC AFMC AFOTEC AFSC APB ASP ASR BCD BDP BSD CAID CCB CCBD CCP CDR C/DR CM CMO CMP COEA COTS CRLCMP CRWG CSCI C/SCSC CVP CWBS DAE DIA DL.4 DMA DoD DODISS DOE DTitn Work Rre

12、akdowi Smcture Quality Assurdnce Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-QTP RCM RDT;! Bcssline includes b%e dzta that repse=t the systerrdCI at a ;ex pokt cf its life cycle. The Technical BDPs (i.e., Milestones I, TI, and Ill Data Packages,

13、BDPs, MRDPs and Low Cosflemporary MDPs) are identified in Table 1. The Technical Baseline includes Configuration Baseline Data and Decision Support Data. The Configuration Baseline Data describe functional and physical interface characteristics, performance requirements, design solutions, unique man

14、ufacnuing processes and materials. Cne Daisiun Support Data, data required to make program/technical decisions, evolve from and through the development process and become part of the Technical BDPs. The Technical Baseline Data support acquisition, test and evaluation, operation, maintenance, repair,

15、 reprocurement, modification, and other logistics actions. 3.3 WHY IS TBDM NECESSARY? TEDM is .n essential dixip!Lne used in idrntifying, hax!ining, and main?aLnjng Technical Baseline Data (i.e., data processed through the system for approval and/or archiving). The process used in the past for defin

16、ing and maintaining Technical Baseline Data resulted in incomplete or inaccurate baseline data. AFSC and AFLC had different baseline definiiions, used diiFcxni tcrrriliuiugy, alid employed iiiffeietit processes w ii-magc Configuration Baseline Data. These processes did not ensure proper tracking and

17、 accountability of data. Program Management Responsibility Transfer (PMRI) often caused Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-adisconnect in the maintenance of the Technical Baselines -use the process was not consistently defined or underst

18、ood outside the CM community. Therefore. CM was often not recognized as an important acquisition and logistics process. 3.4 WHEN DOES TBDM BEGIN? TBDM begins the pre-Concept and Exploration and Defiition Phase with defining the Technical Baseline and archiving the Decision Support Data. TBDM continu

19、es throughout all phases of the life cycle as the echnieiis evolve. Ihe volume of data comprising the TBDM, which must be maintained, grows as the system progresses toward deployment and operations. 3.5 WHAT IS THE CM ROLE IN TBDM? 3.5.1 General. Under JWSM, the CM organization is responsible for es

20、tablishing processes that ensure the definition and maintenance of the Technical Baseline Data. Standard terms have been defined in Chapter 2 for use in the development as well as in support for the life cycle management of the system. All technical data critical to life cycle management of the syst

21、em are basebed. Baselining occurs when the CCB or other approval authorities approve the data or when non-approval data are archived. Validation throughout the SE process and maintenance through the appropriate levels: of conaol provide an accurate and current Technical Baseline to facilitate manage

22、ment of the system. This process improves support for lWSM activities throughout the “system“ life cycle. CM is responsible for Baseline Definition Process Development Document Processing Baseline Maintenance 3.5.2 Specific. The specific CM responsibilities are identified in the following paragraphs

23、. 3.5.2.1 Baseline Definition. CM, in conjunction with SE and the implementation of an IFT, is responsible for defining the specific technical data critical to the life cycle management of the system that are to be baselined, controlled, and archived for each program. The TDPs, as shown in Table 1,

24、identify the types of data and suggested specific data that are candidates for inclusion in the Technical Baseline. The Technical Baseline is established for new programs, modification programs, and existing programs. The Baseline Definition for existing programs should be based upon availability an

25、d status of existing data. The Baseline Definition is initiated at the start of a program or modification. Early baseline definition is essential to ensure that the required data, both contractor and Air Force prepared. are provided to the archiving office. 3.5.2.2 Process Develupment. CM is respons

26、ible for managing the TBDM process. The responsibilities include (a) ensuring that new processes are developed or existing processes are acceptable for establishing and maintaining the Technical Baseline; (b) determining the most efficient method and location for archiving data; and (c) determining

27、the location for archiving data and defining acceptance processes for storage of data such as TOs and drawings. The processes must identify * How the technical data that require approval is processed through the approval cycle (CCB or other approval) How archived-only data are processedbaselined Pro

28、vided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-The requirements and data flow from receipt of data through final disposition and archiving Inputs to the status accounting function The organizations responsible for reviewing, disposing, and archiving th

29、e data - - lnterfkes with the SPUS - How elecaonic media are used 33.2.3 Document Processing, All data identified for inclusion in the Technical Baseline must be baselined. This means that data requiring approval have been processed by the CCB or other appropriate authority; other data not requiring

30、 formal approval has been finalized by the document preparer and submitted for archiving. Baselining of data occurs by the accomplishment of one of the following: - CCE prcxesskg ir? accsrdance %it! Cha* r- A . nf - this GnidPhnnk * Other approval processing of Contract Data Requirements List (CDRL)

31、 contractor data or Air Force data that requires approval prior to release and entry into the Technical Baseline Archiving of contractor and Air Force data that does not require tippr0val but does require mhiving Figure 3, Blocks 1 through 7, identify the CM document processing tasks. The erform Dat

32、a Assessment Block (Block 2) is where the data is reviewed for compliance with the requirements of the Data Item Description (DID). 3.5.2.4 TBDM. CM is responsible for the maintenance of the Technical Baseline Data which consist of archiving and status accounting. Part of the development of the main

33、tenance process is determining where and how the technical data should be archived. The Technical Baseline Data can be archived in various locations; however, there must be a single control point for maintenance and status accounting of the data. CM is responsible for the development of an accountin

34、g system that identifies the Technical Baseline Data and rracks the schedule and status of data in addition, the system must identify the current issue of each document in the Technical Baseline and the location where the document is archived. *k.“ !Xis systm. zx:t support the CCB proces by ppraiecc

35、ipt date of the information is logged into ther status accounting records. The date of receipt is important for several reasons: it starts the clock for contraha1 data items that must revid within a specified numba of calendar days mis applies to C/DRs as well, which must be processed within a certa

36、in number of days based an the assigned priority.) and it servts as the starting paint when evaluating CM processes for their effectivity. After the Technical Baseline Data have been logged in, it is then ready to begin the review process. Configuration Baseline Data (Specifications, Drawings, Softw

37、are Code) r C!Rs -.- - Planslprocedms Reiiii:w/Audi; Pommcndzria r Status Accounting ICDs - - Reports Suppon Documentation I Test and Evaluation Management Fians CiuiPsi TOs Etc m: The types of data are variable and are dependent upon the life cycle phase of the program. 1.4 OUTPW. Same as inputs. F

38、igure 3 (Continued) Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-2.0 PERFORM DATA ASSESSMENT 2.1 SCOPE: The Technical Baseline Data are reviewed for accuracy and completeness to provide recommended disposition. 22 DESCRIPTION: The Technical Baseli

39、ne Data are reviewed by the CM process. Conuactual data itcms are reviewed to dctcnninc if they comply with the DD Form 1423 requirements. They are also examined for timeliness (were contract submittal requirements met?). Non-submittals are also noted and aw identified as being delinquent. CmRs are

40、reviewed for accuracy and completeness. A recommendation is made regarding their readiness for CCB processing. Draft technical data submittals are reviewed to determine if they accurately reflect the configuration baseline requirements. Status accounting data are also reviewed for accuracy and compl

41、eteness. Decision Support Data are reviewed to ensure that CM has the latest version before it is added to the Tecluical Baseline. This pxwess continues throughout the life cycle. 2.3 INPUTS: Configuration Baseline Data (Specifications. Drawings, Software Code) mRs PlanslRocedures ReviewlAudit Recom

42、mendations Status Accounting lCDs Reports Support Documentation TEMPS TOs Etc. m: The types of data are variable and are dependent upon the life cycle phase of the program. 2.4 OUTPUTS: Same as inputs. Figure 3 (Continued) 19 Provided by IHSNot for ResaleNo reproduction or networking permitted witho

43、ut license from IHS-,-,-Balance approval are forwarded to the kt step in the Technical Baseline pro& to determihe if a CCB or another approval process is required. Configuration Baseline Data must use the CCB approval process. Decision Support Data that document decision rationale, provide documenta

44、tion on production units or various maintenance actions (i.e., statbs accounting), reflect program direction. or document historicaI information nonnallv do not reauire fomal aroval. These data provide inlportant technical information thst supportsthe system thkughout its life cycle. Decision Suppor

45、t Data not requiring approval are incorporated into the Technical Baseline and maintainedby the configurationldata management process. Figure 3 (Continued) 2 1 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-4.3 INPUTS: Configuration Baseline Data (s

46、pecifiiations, drawings. software code) ClDRs Plans/Procedures ReviewJAudit Recommendations Status Accounting ICDs Reporn Support Documentation TEMPS TOs Etc. w: The types of data are variable and are dependent upon the life cycle phase of the program. 4.4 OUTPUTS: Approval Required (“Yes“ Decision)

47、: Configuration Baseline Data (specification, drawings, software code) ECPs Deviatitions/waivers TOshnanuals Testeports * Conuaitual data items TEMPS Baseline Concept Document Approval Not Normally Required (“No“ Decision): Decision rationale data Approved Directives a Status accounting data Data previously approved by non-CCB approval processes Figure 3 (Continued) Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-