《NAVAIRINST 4355.doc》由会员分享，可在线阅读，更多相关《NAVAIRINST 4355.doc（151页珍藏版）》请在三一办公上搜索。
1、 NAVAIRINST 4355.19D AIR-4.0/5.0/6.0NAVAIR INSTRUCTION 4355.19DFrom: Commander, Naval Air Systems Command Subj: SYSTEMS ENGINEERING TECHNICAL REVIEW PROCESSRef: (a) DoDD 5000.1, The Defense Acquisition System, of 12 May 03 (b) DoDI 5000.2, Operation of the Defense Acquisition System, of 12 May 03 (c
2、) USD(AT&L) Memorandum, Prototyping and Competition, of 19 Sep 07 (d) USD(AT&L) Memorandum, Policy Addendum for Systems Engineering in DoD, of 20 Feb 04 (e) USD(AT&L) Memorandum, Policy for Systems Engineering, of 22 Oct 04 (f) SECNAVINST 5000.2D, Implementation and Operation of the Defense Acquisit
3、ion System and the Joint Capabilities Integration and Development System, of 16 Oct 08 (g) Defense Acquisition Guidebook, of 8 Oct 04 (h) Naval Systems Engineering Guide, of Oct 04 (i) NAVSO P-3690, of Sep 01 (NOTAL) (j) DoD Systems Engineering Plan Preparation Guide, Version 2.01, of Apr 08 (k) NAV
4、AIRINST 3960.2C, of 9 May 94 (l) NAVAIRINST 5000.21A, of 2 Nov 05 (m) USD(AT&L) Memorandum, Competitive Source Selection, of 24 August 07 (n) NAVAIRINST 4200.36C, of 2 Jun 04Encl: (1) Systems Engineering Technical Review Process Handbook (2) Systems Engineering Technical Review Timing1. Purpose. To
5、establish policy, outline the process, and assign responsibilities for the planning and conduct of Systems Engineering Technical Reviews (SETRs) of Naval Air Systems Command (NAVAIR) programs.2. Cancellation. This instruction supersedes and cancels NAVAIRINST 4355.19C, of 10 Apr 06. Since this is a
6、major revision, individual changes are not indicated. 3. Scope. This instruction applies to all personnel supporting all NAVAIR and Aviation Program Executive Officer (PEO) programs involved with the design, development, test and evaluation, acquisition, in-service support, and disposal of naval avi
7、ation weapon systems and equipment. 4. Discussion a. References (a) and (b) provide policies and principles applicable to all Department of Defense (DoD) acquisition programs. Among other things, these references require that acquisition programs be managed by application of systems engineering (SE)
8、 that optimizes operational capability, total system performance, and minimizes total ownership costs. Additionally, cost realism and knowledge-based risk management are mandated. Specifically, knowledge about key aspects of a system shall be demonstrated by the time decisions are to be made. Approp
9、riate Modeling and Simulation (M&S) will be performed to validate Capability Based Assessments and to verify system performance and interoperability requirements. A proactive approach to bridging the transition process between capability gap identification and capability gap solutions will be applie
10、d. This requires a broad assessment of the war fighting environment, strategies, and processes as well as materiel solutions. Technology risk shall be reduced and critical technology elements shall have been demonstrated in a relevant environment, with alternatives identified, prior to program initi
11、ation. Joint interoperability requires that critical information sharing is defined and documented in a Net-Ready Key Performance Parameter. Integration risk shall be reduced and product design demonstrated prior to the Critical Design Review (CDR). Manufacturing risk shall be reduced and producibil
12、ity demonstrated prior to full-rate production. Reference (c) directs that DoD Services “formulate all pending and future programs with acquisition strategies and funding that provide for two or more competing teams producing prototypes (of key system elements) through Milestone (MS) B.” It also sta
13、tes “that this acquisition strategy should be extended to all appropriate programs below ACAT 1.” Reference (d) mandates that programs develop a Systems Engineering Plan (SEP) for Milestone Decision Authority (MDA) approval in conjunction with each Milestone review. The SEP shall describe the progra
14、ms overall technical approach, and detail the timing, conduct, and success criteria of technical reviews. Additional policy was established by reference (e) which requires each PEO to have a lead or chief systems engineer on staff responsible to the PEO for the application of SE, review of assigned
15、programs SEPs, and oversee SEP implementation across the PEOs portfolio of programs. This reference also states that technical reviews of program progress shall be event driven (vice schedule driven), be conducted when the system under development meets the review entrance criteria as documented in
16、the SEP, and include participation by SMEs who are independent of the program. Reference (f) established a Navy (2 pass/6 gate) review process to improve governance and insight into the development, establishment, and execution of Department of the Navy (DON) acquisition programs. Reference (g) is a
17、 comprehensive guide to be used for best practices, lessons learned, and expectations. It is accessible at http:/akss.dau.mil/dag. b. The SETRs are an integral part of the SE process and life cycle management, and are consistent with existing and emerging commercial/industrial standards. These revie
18、ws are not the place for problem solving, but to verify that problem solving has been accomplished. Reference (h) provides SE processes for use in support of the acquisition of NAVAIR systems. As a part of the overall SE process, SETRs enable an independent assessment of emerging designs against pla
19、ns, processes and key knowledge points in the development process. An integrated team consisting of Integrated Product Team (IPT) members and independent competency SMEs conducts these reviews. Engineering rigor, interdisciplinary communications, and competency insight are applied to the maturing de
20、sign in the assessment of requirements traceability, product metrics, and decision rationale. These SETRs bring to bear additional knowledge to the program design/development process in an effort to ensure program success. Overarching objectives of these reviews are a well-managed engineering effort
21、 leading to a satisfactory Technical Evaluation, which will meet all of the required technical and programmatic specifications. This, in turn, will ensure a satisfactory Operational Evaluation (OPEVAL), and the fielding of an effective and suitable system for the warfighter. c. Additionally, Referen
22、ce (a) requires that Program Managers (PMs) develop and implement performance-based logistics (PBL) strategies that optimize total system availability while minimizing costs and logistics footprint. Reference (i), “Acquisition Logistics for the Rest of Us”, states as fundamental principles that logi
23、stics planning is part of the SE process, cannot be accomplished independently, and that reliability and maintainability (R&M) engineering are cornerstones of a successful logistics program. d. To completely assess the system under review, the SETR process also reviews warfare analysis, logistics, t
24、est and evaluation, and engineering initiatives. These initiatives include, but are not limited to, the Joint Service Specification Guide (JSSG), the Technology Readiness Assessment (TRA), “Section 804” software acquisition initiative, Defense Information Technology Standards Registry (DISR), and th
25、e DoD Architecture Framework (DoDAF). The JSSG is a DoD initiative that provides guidance in the form of tailorable templates utilized in the preparation of aviation performance specifications. The TRA is a requirement of reference (b) that consistently assesses the maturity of critical technology e
26、lements (CTEs) associated with enabling technologies for all DoD Acquisition Category (ACAT) programs. Section 804 of the National Defense Authorization Act for Fiscal Year 2003 mandates improvement of the DoDs software acquisition processes. The DISR provides information technology standards, and t
27、he DoDAF defines a standard way to organize the system architecture into complementary and consistent views. e. In addition, the SETR process will review the systems conformance and performance relative to its Joint Warfare Capability; Preferred System Concept; Concept of Operations (CONOPS); Inform
28、ation Assurance; Interoperability; Integrated Architecture; and Net Centric Warfare; and Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel and Facilities (DOTMLPF) Requirements. 5. Policy a. Assistant Program Managers for Systems Engineering (APMSEs), Assistant Program
29、Managers for Test and Evaluation (APMT&Es) and Assistant Program Managers for Logistics (APMLs), as part of Program Teams, shall ensure that planning for SETRs is fully integrated with the overall program plans for all PEO and NAVAIR managed acquisition programs in ACATs I through IV. Programs alrea
30、dy in progress should comply, to the maximum extent possible, within the constraints of their existing budget and contract(s). This SETR planning shall be coordinated with the Program Manager, Air (PMA), the cognizant Assistant Program Executive Officer for Engineering (APEO(E), the cognizant Assist
31、ant Program Executive Officer for Logistics (APEO(L) and the cognizant Assistant Program Executive Officer for Test and Evaluation (APEO(T&E). The SETRs should form the technical basis for establishing: (1) operational capability and program definition in terms of (cost, schedule, and performance);
32、(2) an independent NAVAIR cost estimate of the program; and, (3) program milestone reviews. The SETRs may also be applied to Abbreviated Acquisition Programs (AAPs) and other non-ACAT programs as determined and tailored by the cognizant PEO and/or Program/Project Manager. Programs already in progres
33、s should comply, to the maximum extent possible, within the constraints of their existing budget and contract(s). Joint and other external organization programs should incorporate these policies, as applicable. b. The SETRs provide the PEOs, and PMAs with sound analytical basis for the systems acqui
34、sition and confidence that the system will satisfy its Joint Capability requirements. The SETRs provide the PMA with an integrated technical (e.g., logistics, engineering, test and evaluation (T&E), in-service support) baseline evaluation, and confidence that the technical baseline is mature enough
35、for the next stage of development. This is accomplished via a multi-discipline, engineering assessment of the programs progress towards demonstrating and confirming completion of required accomplishments as defined in the program SEP. These SETRs include an overall technical assessment of cost, sche
36、dule, and performance risk, which forms the basis for an independent NAVAIR cost estimate. End products of these SETRs include a capability assessment, technical baseline assessment, an independent review of risk assessments and mitigation options, Request for Action (RFA) forms, and minutes. A TRA
37、Report with the determination on the CTEs, if any, and their Technology Readiness Level (TRL) maturity level is provided from TRAs. c. Program APMSEs shall ensure naval aviation acquisition programs include a SEP as part of program documentation. Reference (d) establishes SE policy, and mandates a S
38、EP for all programs. An extract from this reference states, “All programs responding to a capabilities or requirements document, regardless of acquisition category, shall apply a robust SE approach that balances total system performance and total ownership costs within the family-of-systems, systems
39、-of-systems context. Programs shall develop a SEP for MDA approval in conjunction with each Milestone review, and integrated with the Acquisition Strategy. This plan shall describe the programs overall technical approach, including processes, resources, metrics, and applicable performance incentives
40、. It shall also detail the timing, conduct, and success criteria of technical reviews.” Additionally, reference (e) requires that technical reviews of program progress shall be event driven (vice schedule driven), be conducted when the system under development meets the review entrance criteria as d
41、ocumented in the SEP, and include participation by SMEs who are independent of the program. The policies mandated by these memoranda will be incorporated in the next update to reference (b). d. References (h) and (j) are valuable tools in preparing the SEP, which should define the overall plan (who,
42、 what, where, when, how, etc.) for SETRs and the SE processes to be employed by the program. The following essential SETRs should be conducted, as applicable, on all ACAT programs: (1) Initial Technical Review (ITR); (2) Alternative Systems Review (ASR); (3) System Requirements Review I (SRR-I); (4)
43、 System Requirements Review II (SRR-II); (5) System Functional Review (SFR); (6) Software Specification Review (SSR); (7) Preliminary Design Review (PDR); (8) Critical Design Review (CDR); (9) Integration Readiness Review (IRR); (10) Test Readiness Review (TRR); (11) Flight Readiness Review (FRR) (f
44、or airborne systems); (12) System Verification Review/Production Readiness Review (SVR/PRR); (13) Physical Configuration Audit (PCA); and, (14) In-Service Review (ISR) At a minimum, SRRs, PDRs, CDRs and SVRs should be conducted on all non-ACAT acquisition programs. For acquisition programs with mult
45、iple software increments, the program should conduct a SSR, CDR, and IRR for each increment. In addition to SETRs, programs conduct Integrated Baseline Reviews (IBRs) and Operational Test Readiness Reviews (OTRRs) in accordance with references (g) and (k) respectively. AIR-4.0 personnel do not norma
46、lly chair these reviews, but they do provide technical elements and support as detailed in enclosure (1). The Program SEP should provide the technical elements of the IBR and OTRR. e. Enclosure (1) describes the objective of each SETR, IBR, OTRR, and provides additional information concerning implem
47、entation of this instruction, and guidelines for compliance. Elimination of reviews should be coordinated with the APEO(E), APEO(L), and APEO(T&E), and must be approved by the MDA as documented in the Programs approved SEP. For any review not held, the SEP shall document when the critical work elements, products, and maturity metrics associated with that phase of development will be approved. Programs need not conduct SETRs that do not apply given the structure of the program, i.e., where in the acquisition cycle the program will enter. Functional and/or
