Att_04_-_IMP.pdf

M67854-14-R-0001 Attachment 4

PM AAA

AAV Survivability Upgrade IMP

18-Nov-13

Assault Amphibious Vehicle (AAV) Survivability Upgrade Integrated Master Plan (IMP) Events

Event Number Event Name Contract Number Comments

AAV04 AAV MS C COMPLETED TBD

AAV05 AAV INITIAL OPERATIONAL CAPABILITY (IOC) COMPLETED TBD

AAV06 AAV FULL OPERATIONAL CAPABILITY (FOC) ACHIEVED TBD

Event AAV04: AAV MS C COMPLETED

Program

Event (PE) Significant

Accomplishment (SA) Accomplishment

Criteria (AC) Accomplishment/Criteria Nomenclature

Description

Comments

AAV04

AAV MS C - PDR / CDR Contract Activities Completed

Completion MS C for PDR/CDR Contract Activities Complete

02 Reserved

AAV MS C - System Readiness Review (SRR) Preliminary Design Review (PDR) Completed

MS C - SRR / PDR

Reserved

AAV MS C - Technology Readiness Assessment (TRA) Completed (Verify)

A Technology Readiness Assessment (TRA) is a Systematic, Metrics-based Process that Assesses the Maturity of, and the Risk Associated with, Critical Technologies to be Used

AAV MS C - Critical Design Review (CDR)

A Multi-disciplined Technical Review to Ensure that a System Can Proceed into Fabrication, Demonstration, and Test and Can Meet Stated Performance Requirements within Cost, Schedule, Risk, and Other System Constraints

AAV MS C - Prototype Build (8) Option

Exercised Prototype build option issued

Significant

Accomplishment (SA) Accomplishment

Criteria (AC)

AAV MS C -Gate 6 (Post CDR) Review

Completed Gate 6 (Post CDR) Review

AAV MS C - Test Readiness Review (TRR)

A test readiness review (TRR) assesses contractor’s readiness for testing configuration items, including hardware and software, regarding to the test objectives, procedures, resources and testing coordination

AAV MS C - Prototype Build Completed (8

Prototypes)

Prototype Build Complete

01 AAV MS C - Prototype Build #1 Completed N/A 02 AAV MS C - Prototype Build #2 Completed N/A 03 AAV MS C - Prototype Build #3 Completed N/A 04 AAV MS C - Prototype Build #4 Completed N/A 05 AAV MS C - Prototype Build #5 Completed N/A 06 AAV MS C - Prototype Build #6 Completed N/A 07 AAV MS C - Prototype Build #7 Completed N/A 08 AAV MS C - Prototype Build #8 Completed N/A

AAV MS C - DT Training Completed

DT Training Complete

AAV MS C - Live Fire Completed

Live Fire Complete

AAV MS C - Post DT / OA CDR Completed Post DT / OA CDR Complete

AAV MS C - LOG Demo VAL / VER Completed LOG Demo VAL / VER

AAV MS C - Development Testing Completed Development Testing

Significant

Accomplishment (SA) Accomplishment

Criteria (AC)

AAV04 16 AAV MS C - OA Training Completed OA Training Complete

AAV MS C - Operation Assessment (OA)

Completed Operation Assessment

AAV04 18 AAV MS C - (ILA) Completed

AAV MS C - Program Documents Completed MS C - Program Documents Complete

AAV MS C - Program Documents Start

MS C - Begin to Develop/Update Program Documents Start

AAV MS C - Affordability Assessment Completed

Affordability Assessment Updated from MS B

AAV MS C - Acquisition Decision Memorandum (ADM) Completed

ADM from the PIP Updated at Each Milestone

AAV MS C -Acquisition Program Baseline (APB)

APB Updated from MS B

AAV MS C - Acquisition Plan (AP) Completed Update of the Acquisition Plan

AAV MS C - Acquisition Strategy (AS) Completed Update of the Acquisition Strategy (AS)

AAV MS C -Capability Production Document (CPD)

The CPD is Prepared During the Engineering & Manufacturing Development Phase to Guide the Production and Deployment Phase and Is Used to Measure the Contractor’s Delivery

Significant

Accomplishment (SA) Accomplishment

Criteria (AC)

AAV MS C - Independent Logistics Assessment (ILA)

The ILA process provides the program manager, program logisticians, warfighting commands and the Milestone Decision Authority (MDA) with a confidence in the Integrated Logistics Support (ILS) planning and implementation

AAV MS C - Item Unique Identification (IUID) Implementation Plan Completed

Item Unique Identification Implementation Plan (IUID) Completed. IUID is a part of the compliance process mandated by the DOD requiring a permanent marking method used to give equipment a unique ID

AAV MS C - Program Life Cycle Cost Estimate (LCCE)

The total cost to the government of acquisition and ownership. It includes the cost of development, acquisition, operations, and support (to include manpower), and disposal.

Significant

Accomplishment (SA) Accomplishment

Criteria (AC)

AAV MS C -Life Cycle Sustainment Plan (LCSP)

The LCSP describes the approach and resources necessary to develop and integrate sustainment requirements into the system‘s design, development, testing, deployment and sustainment phases.

AAV MS C - Programmatic Environment, Safety and Occupational Health Evaluation (PESHE)

The PESHE documents the ESOH design consideration data produced by executing the ESOH planning described in the

SEP

AAV MS C - Program Protection Plan (PPP)

Baseline AAVP7 RAM/RS PPP is the milestone acquisition document that describes the plan, responsibilities, and decisions for all Program

Significant

Accomplishment (SA) Accomplishment

Criteria (AC)

AAV MS C - System Engineering Plan (SEP)

The SEP is a description of the program’s overall technical approach including processes, resources, metrics, applicable performance incentives, and the timing, conduct, and success criteria of technical reviews. The Contractor uses the SEP in support of the SEMP task and CDRL in the SOW

AAV MS C -System Threat Assessment (STA)

Describes the Projected Threat Environment for Amphibious Vehicles.

Combined ACV/AAV threat assessment completed by MCIA and validated by DIA

Significant

Accomplishment (SA) Accomplishment

Criteria (AC)

AAV MS C - Test and Evaluation Master Plan (TEMP) Completed

The TEMP documents the overall structure and objectives of the Test and Evaluation (T&E) program.

The TEMP identifies the necessary Developmental Test and Evaluation (DT&E), Operational Test and Evaluation (OT&E), and Live Fire Test and Evaluation (LFT&E) activities

Significant Accomplishment (SA)

Accomplishment Criteria (AC)

AAV MS C - Technology Readiness Assessment (TRA) Completed

A Technology Readiness Assessment (TRA) is a systematic, metrics-based process that assesses the maturity of, and the risk associated with, critical technologies to be used in Major Defense Acquisition Programs (MDAPs). It is conducted by the Pro- gram Manager (PM) with the assistance of an independent team of subject matter experts (SMEs). It is provided to the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) and will provide part of the bases upon which he advises the Milestone Decision Authority (MDA) at Milestone (MS) B or at other events designated by the MDA to assist in the determination of whether the technologies of the program have acceptable levels of risk-based in part on the degree to which they have been demonstrated (including demonstration in a relevant environment)-and to support risk-mitigation plans prepared by the PM.

Significant

Accomplishment (SA) Accomplishment

Criteria (AC)

AAV MS C - Training System Plan Completed

The System Training Plan (STRAP) is the Plan for Individual, Unit, Institutional and New Equipment Training

AAV MS C - Program Documents Completed Program Documents

AAV MS C - Production Readiness Review (PRR) Completed

Production Readiness Review (PRR) Complete

AAV MS C - MS C Program Review Completed MS C Program Review

Event AAV05: AAV INITIAL OPERATIONAL CAPABILITY (IOC) COMPLETED

Significant

Accomplishment (SA) Accomplishment

Criteria (AC)

AAV05

AAV Initial Operational Capability (IOC)

01 AAV IOC - Contract LRIP Build Option Exercised

AAV IOC - LRIP Build (2 Lots, Up To 52 Total Units)

03 AAV IOC - Production RFP Released 04 AAV IOC - FUSL (4) Completed

AAV IOC - Product Qualification Testing (PQT)

06 AAV IOC - PQT / RQT Completed (RQT=?)

07 AAV IOC - IOT&E Training Completed 08 AAV IOC - IOT&E Completed 09 AAV IOC - IOC Completed

Event AAV06: AAV FULL OPERATIONAL CAPABILITY (FOC) ACHIEVED

Significant

Accomplishment (SA) Accomplishment

Criteria (AC)

AAV06

AAV Full Operational Capability

(FOC)Achieved

AAV FOC - Full Rate Production (FRP) Review

02 AAV FOC - Product Contract Awarded

AAV FOC - FRP Build (4 Lots, 344 Total Units)

04 AAV FOC Completed

Standard Glossary of AAV Terms IMP Nouns Definitions Critical Design Review (CDR) NAVAIRINST 4355.19C: The CDR is a multi-disciplined product and process assessment to ensure that the system under review can proceed into system fabrication, demonstration, and test, and can meet the stated performance requirements within cost (program budget), schedule (program schedule), risk, and other system constraints. Generally this review assesses the system final design as captured in product specifications for each configuration item in the system (product baseline), and ensures that each product in the product baseline has been captured in the detailed design documentation.

Product specifications for hardware enable the fabrication of configuration items, and may include production drawings.

Product specifications for software (e.g., Software Design Documents) enable coding of a Computer Software Configuration Item (CSCI). Configuration items may consist of hardware and software elements, and include items such as airframe, avionics, weapons, crew systems, engines, trainers/training, etc.

Integrated Master Plan (IMP) AFMC CPAM 63-5: 2.2.1. Integrated Master Plan. The IMP is an event-driven program/project plan that provides top-level control and progress management through establishment of key events and associated accomplishments and criteria for each accomplishment. Unlike the IMS, the IMP is contractual.

Integrated Master Schedule (IMS) AFM CPAM 63-5: The IMS is an integrated, master schedule containing the networked, detailed tasks necessary to support the events, accomplishments, and criteria of the IMP. The execution IMS shall contain all of the contract IMP events, accomplishments, and criteria from contract award to completion of the contract. The IMS shall be a logical network-based schedule that is directly traceable to the contractor’s cost/schedule reporting instrument used to address variances (such as Cost Performance Report (CPR), Cost/Schedule Status Report (C/SSR), etc.).

Preliminary Design Review (PDR) NAVAIRINST 4355.19C: The PDR is a multi-disciplined product and process assessment to ensure that the system under review can proceed into detailed design, and can meet the stated performance requirements within cost (program budget), schedule (program schedule), risk, and other system constraints. Generally this review assesses the system preliminary design as captured in performance specifications for each configuration item in the system (allocated baseline), and ensures that each function in the functional baseline has been allocated to one or more system configuration items, or System of Systems (SoS)/Family of Systems (FoS) items as appropriate. Configuration items may consist of hardware and software elements, and include items such as airframe, avionics, weapons, crew systems, engines, trainers/training, etc.

Production Readiness Review (PRR) NAVAIRINST 4355.19C: The PRR is an examination of a program to determine if the design is ready for production and the producer has accomplished adequate production planning without incurring unacceptable risks that will breach thresholds of schedule, performance, cost, or other established criteria. The full, production configured system is evaluated to determine that it correctly and completely implements all system requirements, and whether the traceability of final system requirements to the final production system is maintained. At this review the IPT shall also review the readiness of the manufacturing processes, the Quality System, and the production planning, i.e., facilities, tooling and test equipment capacity, personnel development and certification, process documentation, inventory management, supplier management, etc. A successful review is predicated on the IPT's determination that the system requirements are fully met in the final production configuration, and that production capability form a satisfactory basis for proceeding into LRIP and FRP.

System Functional Review (SFR) NAVAIRINST 4355.19C: The SFR is a multi-disciplined product and process assessment to ensure that the system under review can proceed into preliminary design, and that all system requirements and functional performance requirements derived from the CDD (formerly ORD) are defined, aligned with the external environment (systems and infrastructure) and consistent with cost (program budget), schedule (program schedule), risk, and other system constraints. Generally this review assesses the system functional requirements as captured in system specifications (functional baseline), and ensures that all required system performance is fully decomposed and defined in the functional baseline. System performance may be decomposed and traced to lower level subsystem functionality that may define hardware and software requirements. SFR determines whether the systems functional definition is fully decomposed to its lower level, and that the IPT is prepared to start preliminary design.

System Requirements Review (SRR) NAVAIRINST 4355.19C: The SRR is a multi-disciplined product and process assessment to ensure that the system under review can proceed into the System Development and Demonstration (SDD) phase, and that all system and performance requirements derived from the CDD are defined, aligned with the external environment (systems and infrastructure), and consistent with cost (program budget), schedule (program schedule), risk, and other system constraints. Generally this review assesses the system requirements as captured in the system specification, and ensures that the system requirements are consistent with the preferred system solution as well as available technologies resulting from the Technology Development (formerly CAD) phase. Of critical importance to this review is the understanding of program technical risk inherent in the system specification and SDD phase program plan. Acceptable level of risk is key to a successful review.

System Verification Review (SVR) NAVAIRINST 4355.19C: The SVR is a multi-disciplined product and process assessment to ensure that the system under review can proceed into Low Rate Initial Production (LRIP) and Full Rate Production (FRP) within cost (program budget), schedule (program schedule), risk, and other system constraints. (A Functional Configuration Audit (FCA) may be conducted concurrent with SVR, if desired). Generally this review is an audit trail from the CDR, and assesses that the system final product, as evidenced in its production configuration, meets the functional requirements as derived from the Capability Production Document (CPD - formerly ORD) to the Functional, Allocated, and Product Baselines. The SVR establishes and verifies final product performance.

IMP Verbs Definitions

Agreed Upon An authorized party of the Contractor enters into an agreement with the customer, the customer’s government, the U.S.

government, other companies, or with organizations within the Contractor and the agreement is documented in writing and signed by all parties.

Allocated The subject parameter has been subdivided or apportioned into parts according to the appropriate product manager.

Analyzed The subject parameter has been technically evaluated through equations, charts, and reduced data.

Approved The subject configuration item, data, or document has been submitted to the appropriate authority, which has notified the team that it is acceptable.

Available The subject configuration item, tool, or process is in place or operational.

Baselined The subject design, parameter, concept, or configuration item has been finalized, received management approval and is under configuration control.

Compiled Information, dates have been gathered, cleaned up, and put together to form a definitive document and, or analysis.

Completed The subject configuration item, data, or document has been prepared and reviewed by contractor management.

Conducted The subject event or review has been held and minutes completed.

Defined The subject configuration item, data, or document has been described in an appropriate description document.

Delivered The subject configuration item, data, or document has been accepted in the form and at the location specified in the contract.

Demonstrated The subject configuration item, data, or document has been shown to be in accordance with contract requirements through measures where success or failure is determined by observation.

Developed The subject configuration item, data, or document has been produced through a sequence of activities that may include planning, design, test, and verification.

Documented The subject area has been compiled, edited, and put into a draft format for review or in final form.

Established The subject has been created and set in place in a manner consistent with its intended use (e.g., procedures, baselines established).

Evaluated A measured comparison of the subject with contract requirements has been completed.

Finalized The subject data or document is complete, has contractor management approval, and may not be changed without formal revision control.

Generated Data has been created or results have been established or information has been made available to satisfy a goal or expectation.

Identified The characteristics of a configuration item, process, or function have been made known for the first time.

Implemented The subject policy, approach, or procedure is being regularly executed.

Incorporated Information has been obtained and included, combined into subject document, data item.

Initiated The subject approach or procedure has been started.

Integrated The subject has been consolidated into an entity (e.g., data, requirement, document, configuration item) by appropriately combining all separate requirements, functional disciplines, and configuration item considerations.

Negotiated The subject item has been proposed by one party to another, exchanges between parties have taken place and the parties have arrived at an agreement which is documented in writing and sign by both parties.

Operational The intended item is capable of performing its intended function.

Performed A task or assignment has been carried out in accordance with directions, guidelines, and established processes.

Planned A description in the form of a document containing the objective, issues and questions to be addressed, the entrance and exit criteria for success, the sources of predecessor information or assumptions prior to beginning work, the artifacts to be acquired or produced, the approach to acquiring/producing the artifacts, and how the artifacts produced will be analyzed or reported.

Prepared The subject item has been created, documented, and transferred in acceptable format for review.

Provided The subject configuration item has been completed and delivered to the receiving agency.

Released The subject data or document has received all necessary Government and contractor IPT approvals.

Resolved Successful determination or solution to an issue or problem declared in writing Reviewed The subject data document has been examined critically and satisfies predefined requirements.

Revised The subject configuration item, data, or document has been updated to account for new requirements and, or facts.

Submitted Provided to the customer for information or for approval when approval is required beyond that of customer participation in IPT approvals.

Supported Prime activity has been supplemented and enhanced by providing data, information, or manpower.

Updated The subject process, data, or document has been reevaluated based on later information, and adjustments have been incorporated.

Validated The subject requirement, configuration item, data, or document has been reviewed for technical compliance by the contractor, using existing approved procedures, instructions, and checklists.

Verified The subject configuration item, data, or document has been proved to be in accordance with contract requirements by analysis, inspection, demonstration, or test.

Reconciled The discrepancies between the subject items have been accounted for.

Dispositioned The final status of the subject items has been determined.

Closed The final terms and conditions of the subject items have been completed.

IMP Adjectives Definitions

Initial The use of this adjective preceding a noun signifies that the item has a maturity level adequate to satisfy as the first submittal of a deliverable.

Preliminary The use of this adjective preceding a noun signifies that the item has reached a level of maturity where it is ready for limited use with caution, possibly under restricted conditions. For further definition of the preliminary state of a particular IMP item, see the definition provided in the Nouns section of this glossary for that particular item. Level of detail needed to approve initiation of preliminary design.

Reserved The use of this adjective signifies that the item is a placeholder for anticipated contract action pending definitization.

Final The use of this adjective preceding a noun signifies that the item has reached a level of maturity where it has been fully validated. For further definition of the final validated state of a particular IMP item, see the definition provided in the Nouns section of this glossary for that particular item.

Position Description

Owner/Leader Responsibility: The company/organization designated with the Owner/Leader (O) role for a given Accomplishment Criteria (AC) has lead responsibility for ensuring that said AC has been satisfied. The specific activities involved in fulfilling this responsibility may include (but are not limited to) preparing, coordinating, maintaining, updating, and (where appropriate) controlling changes to the product specified in the AC. Unless an Approver role (see below) is expressly identified for a given AC, the Owner/Leader shall also be responsible for approving the product specified in the AC.

These activities, in whole or in part, may be performed by the Owner/Leader or delegated to those in a Supporter role (see below). Those activities being performed by the Owner/Leader should be clearly identifiable in the Owner/Leader's Integrated Master Schedule (IMS).

Authority: This IMP, in conjunction with associated contracts, provides the authority and obligation for the Owner/Leader to perform its responsibility.

Accountability: The Owner/Leader will be held accountable for its obligation through the Integrated Master Schedule (IMS), associated subordinate schedules, and the Earned Value Management System (EVMS).

Supporter Responsibility: The company/organization designated with the Supporter (S) role for a given Accomplishment Criteria (AC) has supporting responsibility for ensuring that said AC has been satisfied. The specific activities involved in fulfilling this responsibility may include some subset of the Owner/Leader's responsibilities that have been delegated and accepted by the Supporter. Those delegated activities being performed by the Supporter should be clearly identifiable in the Supporter's Integrated Master Schedule (IMS).

Authority: This IMP, in conjunction with associated contracts, provides the authority and obligation for the Supporter to perform its responsibility.

Accountability: The Supporter will be held accountable for its obligation through the Integrated Master Schedule (IMS), associated subordinate schedules, and the Earned Value Management System (EVMS).

Reviewer Responsibility: The company/organization designated with the Reviewer (R) role for a given Accomplishment Criteria (AC) has an optional (non-obligatory) responsibility for reviewing and providing feedback to the Owner/Leader toward the satisfactory completion of said AC. If the reviewer chooses to fulfill this responsibility, the specific activities involved may include reviewing appropriate work products associated with the AC, documenting relevant comments, and providing them to the Owner/Leader. These activities may or may not be identifiable in the Reviewer's Integrated Master Schedule (IMS). If the reviewer chooses not to fulfill this responsibility, the Owner/Leader may assume that the Reviewer concurs with the satisfactory completion of the said AC.

Authority: This IMP, in conjunction with associated contracts, provides the authority for the Reviewer to perform its responsibility.

Accountability: There is no obligation for the reviewer to perform its responsibility, therefore no accountability is needed.

Approver Responsibility: The company/organization designated with the Approver (A) role for a given Accomplishment Criteria (AC) has responsibility for dispositioning said AC as either satisfied or not. The specific activities involved in fulfilling this responsibility may include reviewing appropriate work product(s) associated with the AC and making a determination. If the Approver determines that said AC has been satisfied, no further action need be taken. Otherwise, the Approver is obligated to document the disposition, the rationale, as well as discrete direction as to what must be submitted to satisfy the AC, and providing the Owner/Leader with a written response in a timely manner. In the absence of a formal written response, the Owner/Leader may assume that the AC has been satisfied. The activities involved in performing this responsibility may or may not be clearly identifiable in the Approver's Integrated Master Schedule (IMS). When an approver role is not expressly specified for a given AC, it shall be assumed that the Owner/Leader is also responsible for the approval of the product specified in the AC.

Authority: This IMP, in conjunction with associated contracts, provides the authority and obligation for the Approver to perform its responsibility.

Accountability: The Approver is accountable by virtue of the fact that a failure to act will be interpreted as acceptance by the Approver.

AAV Survivability Upgrade IMP Change Log Notes:

1. The AAV Survivability Upgrade IMP Change Log Sections are Identifiable as the Bold Items Below.

Change No. Change Description Reason 11/18/2013 To Remove IBR & Gate 6 (IBR Review) No IBR will be Conducted