Second_Draft_Attachment_01.1_-_MASTER_SOW_-_150108.docx

M67854-15-R-0001 Section J, Attachment (1) Statement of Work

UNCLASSIFIED

Statement of Work (SOW) For the Amphibious Combat Vehicle (ACV)

M67854-15-R-0001 Section J, Attachment 01

ACV-SOW-03001

Version 0.3 8 Jan 2014

DISTRIBUTION A: Approved for public release: distribution unlimited.

ACV-SOW-03001

This page blank

TABLE OF CONTENTS

ACV-SOW-03001 Unclassified

SCOPE

This Statement of Work (SOW) describes the work scope associated with the Amphibious Combat Vehicle (ACV) Phase 1, Increment 1, Program hereafter referred to as the ACV Program. It includes all efforts associated with the Engineering and Manufacturing Development (EMD) vehicle production and testing, Low Rate Initial Production (LRIP) (Option, if exercised) Build, and Full Rate Production (FRP) (Option, if exercised) Build. It includes the associated Program Management, Systems Engineering (SE), Test and Evaluation (T&E), and Integrated Product Support planning requirements.

BACKGROUND

The ACV Program will continue to build upon the preparatory work of the Marine Personnel Carrier (MPC) Program efforts conducted from 2006 to 2013. In 2006, the Office of the Secretary of Defense (OSD) provided strategic planning guidance to the United States Marine Corps (USMC) to maintain a two (2) Marine Expeditionary Brigade (MEB) forcible entry capability and propose a mix of vehicles suitable for Irregular Warfare (IW) to provide a mobility portfolio that better balanced our maneuver/mobility capability for Major Contingency Operations and IW. In response, the USMC proposed a combination of a light vehicle and a medium vehicle designed for the threats seen in IW. Both maintain a capability to maneuver with formations while conducting Major Contingency Operations. A medium personnel carrier was assessed as necessary to provide the full protection required in a high Improvised Explosive Devices (IED) environment, and the multi-axle wheeled configuration was assessed as the most suitable platform for high cross country speed, combined with the ability to transit urban infrastructure in a non-threatening and non-destructive manner. The Marine Requirements Oversight Council (MROC) convened on 4 February 2008 for a decision brief on the MPC material solution and operational fielding placement, based on the MPC Analysis of Alternatives (AoA) dated December 2007. The Ground Combat Tactical Vehicle Strategy was finalized in August 2008, setting the fundamental MPC capacities (Acquisition Objectives), strategic lift envelope, protection, payload, and performance required of the MPC as a system.

After the Expeditionary Fighting Vehicle (EFV) Program cancellation in January 2011, a Systems Engineering Operational Planning Team (SE-OPT) convened to conduct engineering and cost analysis of EFV requirements to identify those parameters driving complexity in design, identify trade-space, and develop requirement generation options for an EFV replacement, called the ACV. The SE-OPT analyzed 11 system concepts against capabilities delivered, cost, and schedule of delivery. The SE-OPT fully developed four (4) of the system concepts with various capabilities and costs that represented a range of capability from Assault Amphibious Vehicle (AAV)-based system concepts to new developmental ACV-based system concepts. All four (4) system concepts were low water speed capable. The SE-OPT determined and recommended that the most affordable solution was to develop a modern low water speed capable AAV replacement.

Concurrently with the efforts of the SE-OPT, the Government awarded four (4) MPC Demonstrations and & Studies (D&S) Contracts on 6 August 2012 to better understand the capabilities of Non-Developmental Items (NDIs) to meet water performance, survivability, and human factors/stowage capacity requirements. The promising results of testing these demonstrator vehicles led to a re-invigorated ACV Program in late 2013 using the type of NDI vehicles tested during the D&S Contracts as a baseline. In January 2014, the MPC initiative was reprioritized and repurposed to be the material approach for the Phase 1 Program of the ACV. The MPC Program was then re-designated as the ACV Phase 1 Increment 1 (i.e., ACV 1.1) and an acquisition strategy was selected with a NDI Armored Personnel Carrier (APC).

In April 2014, the MROC approved the ACV Capability Development Document (CDD) which will be followed by a Joint Requirements Oversight Council (JROC) approval once the AoA is finalized, setting the stage for development of programmatic and contractual documentation. The Materiel Development Decision (MDD) was received on 4 June 2014 to formally initiate the ACV Program. The current requirement for the USMC is 12 infantry battalion lift equivalents via APCs. The ACV capability along with the AAV Survivability Upgrade will provide the USMC ten (10) infantry battalion lift equivalents through 2035. After which time, the future phase(s) of the ACV Program will provide for the entirety of the USMC armored lift capacity requirement.

INTRODUCTION OF THE STATEMENT OF WORK

The purpose of this contract is to procure NDI ACV Personnel (P) Vehicles from EMD to FRP (Option, if exercised). This EMD contract will include scope associated with the following: Design/Development; Program Management Support; Tooling Development; Manufacturing ACVs; Logistics Management Information (LMI) Data development; Training Materials development; Technical Manual development; Pre-Milestone (MS) C Test Support; Corrective Action Mods.

This SOW will also include Options (if exercised) to manufacture LRIP and FRP Vehicles, after the down-select decision is completed by the Government. Tasking for these contracts will include: Post MS C Test Support; Design/Development; Program Management Support; Training Materials development; Technical Manual development; Support Equipment development; Manufacturing ACVs; LMI Data; Test Support; Test and Initial Spares; Refurbishment of Test Vehicles, Field Service Representative (FSR) and Training Support for fielding.

APPLICABLE DOCUMENTS

The following documents form a part of this SOW to the extent specified herein. Unless otherwise noted, in the event of a conflict between the SOW and the references cited herein (except for related specification sheets) the text of this SOW takes precedence. All second tier and below references cited shall be considered as guidance only. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

GOVERNMENT DOCUMENTS

Specifications, Standards, and Handbooks

SPECIFICATIONS

DEPARTMENT OF DEFENSE

MIL-PRF-29612-2A

Instructional Systems Development/Systems Approach to Training and Education

31 Aug 2001

DEPARTMENT OF NAVY

STANDARDS

DEPARTMENT OF DEFENSE

GUIDEBOOKS

DEPARTMENT OF DEFENSE

21 Oct 2005

DEPARTMENT OF ARMY

Oct 1979

15 Jul 2010

27 Oct 2010

HANDBOOKS

DEPARTMENT OF DEFENSE

20 Feb 2014

OTHER GOVERNMENT DOCUMENTS, DRAWINGS, AND PUBLICATIONS

Regulations, Federal Acquisition Regulations, Defense Federal Acquisition Regulation Supplements, Manuals, Directives, Instructions, and Forms

REGULATIONS

DEPARTMENT OF ARMY

DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENTS

MANUALS

DEPARTMENT OF DEFENSE

DoD 5000.04–M–1

Cost and Software Data Reporting Manual

4 Nov 2011

28 Mar 2013

DEFENSE LOGISTICS AGENCY

13 Jun 2012

DIRECTIVES

INSTRUCTIONS

COMNAVSURFLANT/

COMNAVSURFPAC INSTRUCTION 3340.3D

MCO 1553.2B

Wet Well Operations Manual

Management Of Marine Corps Formal Schools and Training Detachments 9 Oct 2012

1 Apr 2011

MCO 3070.2A

The Marine Corps Operations Security Program 2 Jul 2013

FORMS

GSA Optional Form

Nov 1985

NON-GOVERNMENT DOCUMENTS

Standards and Guidebooks

STANDARDS

Oct 2012

GUIDEBOOKS

International Society of Weight Engineers, Inc. Recommended Practice Number 5

REPORTS

National Institute of Standards and Technology (NIST) Interagency Report 7622

MANUALS

AVAILABILITY OF Department of Defense DOCUMENTS

Department of Defense (DoD) Directives, Manuals, Instructions, and Publications are available online at http://www.dtic.mil/whs/directives/ or from the National Technical Information Services (NTIS), 5301 Shawnee Rd, Alexandria, VA 22312.

DoD Federal Acquisition Regulations (FAR) and Defense Federal Acquisition Regulations Supplement (DFARS) are available online at http://farsite.hill.af.mil/.

DoD Forms are available online at http://www.dtic.mil/whs/directives/infomgt/forms/.

Department of Navy (DON) Issuances (e.g., Office of the Chief of Naval Operations (OPNAV) Instructions) are available online at http://doni.daps.dla.mil/allinstructions.aspx.

General Services Administration (GSA) Optional Forms (OF) are available by ordering from http://www.gsa.gov/portal/forms/download/116942

Military Specifications, Military Standards, Military Handbooks, and Data Item Descriptions (DIDs) are available online at http://quicksearch.dla.mil/ or from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094.

If a DoD document cannot be acquired, they may be provided by the Government upon the Contractor’s request.

REQUIREMENTS

This SOW encompasses the EMD and the Production and Deployment (PD) Phases of the ACV acquisition program. The ACV performance requirements are fully described in Attachment 02, ACV System Performance Specification ACV-SPE-02003. Vehicle quantities are detailed in Section B - Supplies or Services and Prices of the Request for Proposal (RFP).

The EMD Phase will include the following type of efforts:

· Base Contract Line Item Numbers (CLINs) for Pre-MS C production of EMD ACV-P vehicles will include Design/Development; Program Management Support; Tooling Development; Manufacturing ACVs; LMI Data development; Training Materials development; Technical Manual (TM) development; Pre-MS C Test Support; and Corrective Action Mods.

· Corrective action modifications to the EMD vehicles will be in support of system Reliability Growth Testing (RGT). The corrective action modifications are in response to safety and reliability failures discovered during system developmental testing. The corrective action modifications will be implemented during the planned Corrective Action Periods.

The PD Phase will include the following type of efforts:

· EMD Vehicles Continued Testing (Option, if exercised): CLINs for corrective action modifications to the EMD vehicles in support of system Reliability Growth Testing (RGT). The corrective action modifications are in response to safety and reliability failures discovered during system developmental testing. The corrective action modifications will be implemented during the planned Corrective Action Periods.

· LRIP (Option, if exercised) CLINs for Post MS C production of ACV-P LRIP (Option, if exercised) vehicles and ACV-P Full-Up System-Level (FUSL) vehicles. This effort will include Post MS C Test Support; Design/Development; Program Management Support; Training Materials development; TM development; Support Equipment development; Manufacturing ACVs; LMI Data; Test Support; Test and Initial Spares; Refurbishment of Test Vehicles, FSR and Training Support for fielding.

· FRP (Option, if exercised) CLINs for production of ACV-P vehicles. This effort will include Program Management Support; Training Materials development; TM updates; Support Equipment delivery; Manufacturing ACVs; LMI Data; Initial Spares; Development of Depot Support Products, Vehicle Fielding Support.

GENERAL REQUIREMENTS OVERVIEW

Resource Requirements

The Contractor shall provide all necessary personnel, resources and facilities to execute the requirements, and provide deliverables within the identified schedules. All personnel attending demonstration events at the test sites shall speak fluent English, and submit visit requests to applicable test agencies.

Security

The Contractor shall safeguard controlled unclassified information and administrative data and classified program information and material at all levels of classification through all stages of the contract associated with the ACV from unauthorized access or disclosure in accordance with DoDI 8582.01, "Security of Unclassified DoD Information on Non-DoD Information Systems."

The Contractor shall comply with the security requirements imparted by the DD Form 254, per Attachment 23, and the National Industrial Security Program Operating Manual (NISPOM), DoD 5220.22-M (current version). Additional information can be found in the National Industrial Security Program Library on the Defense Security Service web site: http://www.dss.mil/isp/fac_clear/download_nispom.html.

Operations Security Plan

The Contractor shall develop an Operations Security Plan (OPSEC). The OPSEC plan shall;

1) Describe the OPSEC environment to include identification of critical information, the OPSEC threat, and vulnerabilities an adversary might exploit to acquire critical information,

2) Document the OPSEC risk analysis,

3) Identify proposed and actual OPSEC measures,

4) Define and assign specific OPSEC responsibilities and tie the OPSEC Plan to the contractor's corporate OPSEC Program, and

5) Serve as a repository of the OPSEC history of the contract. Additional guidance can be found in the OPNAVINST 3432.1A, "Operations Security" and Marine Corps Order (MCO) 3070.2A "The Marine Corps OPSEC Program". The Contractor shall prepare and submit the Contractor's OPSEC Plan in accordance with Contract Requirements Data List (CDRL) A001.

Program Protection Implementation Plan

The Contractor shall provide a Program Protection Implementation Plan (PPIP) that includes a criticality analysis, vulnerability assessment, risk assessment, and countermeasure selection and implementation, with assumptions, rationale, and results. For each Level I and Level II component with the following Protection Failure Criticality Levels, Table (1), the Contractor shall identify the associated logic-bearing hardware, software, and firmware that implements critical functions or introduces vulnerability to the associated components (designated as critical components).

Level II: Significant/Unacceptable Degradation Function/component failure is a failure that results in unacceptable compromise of mission capability or significant mission degradation

Table (1) Protection Failure Criticality Levels

The Contractor shall demonstrate visibility into its supply chain for critical components, understanding of the risks to that supply chain, and shall implement or provide plans for implementation of risk mitigation efforts to counter those risks.

The Contractor shall plan for and implement countermeasures which mitigate foreign intelligence, technology exploitation, supply chain and battlefield threats, and system vulnerabilities that result in the catastrophic (Level I) and critical (Level II) protection failures, including:

1) Application of supply chain risk management key practices, applied as appropriate to the development of the system. Supply chain risk management key practices are found in the National Institute of Standards and Technology Interagency Report 7622, Piloting Supply Chain Risk Management (SCRM) for Federal Information Systems, and the National Defense Industrial Association Guidebook, Engineering for System Assurance, both publicly available.

2) Identification and recording of the relevant cost, schedule, and performance information used to choose between alternates as a part of the selection of critical components. The Contractor shall define associated program protection risks with the selected critical component(s) and work with the Government to develop mutually-agreeable risk management plans.

3) Implementation of processes to control access by foreign nationals to program information, including system design information, DoD-unique technology, and software or hardware used to integrate commercial technology.

4) Establishment and maintenance of a Counterfeit Electronic Part Detection and Avoidance System. The processes and practices employed to ensure that genuine hardware, software and logic elements will be employed in the solution. The Contractor shall ensure flow down requirements necessary for the Contractor’s Counterfeit Electronic Part Detection and Avoidance System are levied upon subcontractors.

5) Implementation of processes for safeguarding unclassified controlled technical information in the development environment.

The Contractor shall develop a set of secure design and coding practices to be followed for implementation of Level I and II critical components. Top 10 Secure Coding Practices (https://www.securecoding.cert.org/confluence/display/seccode/Top+10+Secure+Coding+Practices) and the Common Weakness Enumeration (CWE)/SysAdmin, Audit, Network, Security (SANS) top 25 most dangerous software errors (http://cwe.mitre.org/top25/index.html) may be used as guidance.

The Contractor’s PPIP shall address the following areas:

· Section 2: Identifying what to protect

· Section 4: Vulnerabilities

· Section 5: Countermeasures

· Section 7: Program Protection Risks

· Section 8: Managing and Implementing PPP

· Section 9: Process for Management and Implementation of PPP

· Section 10: Process for Monitoring and Reporting Compromises

· Appendix C: Criticality Analysis

The Contractor shall prepare and submit the Contractor’s PPIP in accordance with CDRL A002. The Government will provide a Contracting Office letter to the Contractor validating that the Critical Program Information/Critical Technology (CPI/CT) is properly identified for the program.

Program Protection Review Meetings

The Contractor shall host three (3) Program Protection Review Meetings in accordance with the Attachment 03, Meeting List. Each of the three (3) meetings shall include:

· The Contractor’s Critical Program Information (CPI) Assessment identifying CPI or Critical Technology (CT) (defined by DoDI 5200.39, July 16, 2008 Incl Change 1 Dec 28, 2010, CPI Protection within the DoD)

· A classified session for the Contractor’s Anti-Tamper Plan and status of the Anti-Tamper Solution’s implementation

For planning purposes, each meeting will be a one (1) day event.

Information Assurance

The Contractor shall designate an Information Systems Security Manager (ISSM) who shall meet the training and certification requirements as defined in DoDD 8570.01, “Information Assurance Training, Certification, and Workforce Management,” dated 15 Aug 2004.

The Contractor shall ensure that Contractor Information Assurance Workforce (IAW) personnel comply with Contractor IAW certification standards and security background investigation requirements, as defined in the DoDD 8570.01.

The Contractor shall ensure that Contractor IAW personnel comply with the identification, tracking and assignment reporting requirements, as defined in the DoDD 8570.01. Contractor IAW personnel shall meet the same standards for IAW certification, system access, management, training and reporting requirements as Government IAW personnel, as defined in DoDD 8570.01.

The Contractor shall comply with and provide Information Assurance (IA) supporting activities and functions for the requirements, processes, reporting activities, reviews, certification and accreditation, security design, and assessment activities as defined in the DoDI 8510.01, “Risk Management Framework (RMF) for DoD Information Technology (IT),” dated 12 Mar 2014.

The Contractor shall ensure that ACV IA designated contract deliverables and activities are in compliance with DoDI 8510.01.

The Contractor shall ensure that deliverables comply with applicable United States (U.S.) Government and DoD IA, Directives, Regulations, and Standards that are applicable to the ACV Program’s Security Classification Level (SCL).

The Contractor shall provide an IA status at each of the identified Program Management Reviews (PMRs) per Attachment 03, Meeting List. The Government may require the Contractor to provide quarterly IA program status reports at the PMR to ensure IA is fully integrated and compliant with:

1) Federal Information Security Management Act of 2002, Title III-Information Security

2) National Institute of Standards and Technology (NIST) Special Publication 800-53A- Guide for Assessing the Security Controls in Federal Information Systems

3) DoDI 8510.01- Risk Management Framework for DOD IT, dated 12 Mar 2014

4) Interim DoDI 5000.02 – Operation of the Defense Acquisition System, dated 25 November 2013

5) The ACV Program’s designated SCL implementation requirements as defined by DoDI 8510.01

6) The Government’s Integrated Master Schedule (IMS)

The Contractor ISSM shall ensure the ACV design is reviewed for IA and Anti-Tamper Compliance at the Preliminary Design Review (PDR)/Critical Design Review (CDR), Vehicle Acceptance Review (VAR), and the Production Readiness Review/System Verification Review (PRR/SVR).

The Contractor shall provide support to the Government to successfully achieve an Authority to Operate (ATO) as defined in DoDI 8510.01.

The Contractor shall provide the IA Assessment in accordance with CDRL A003.

Anti-Tamper Plan

The Contractor’s Anti-Tamper Plan shall provide countermeasures to protect CPI and Critical Technologies in accordance with DoDI-5200.39, “Critical Program Information with DoD, Change 1,” dated 28 Dec 2010 to address the following:

1) Deter countermeasure development that would decrease U.S. warfighting capabilities

2) Prevent the unauthorized or out of baseline augmentation or change of capabilities in Direct Commercial Sales (DCS), Foreign Military Sales (FMS), and International Cooperative Development Programs

3) Prevent unauthorized technology changes on CPI or any released capability

4) Protect U.S. critical design knowledge and manufacturing processes from unauthorized transfer

5) Protect U.S. investment in weapon system capabilities, and avoid additional unplanned investment to regain the U.S. advantage

The Contractor’s Anti-Tamper countermeasures shall be verified by the Contractor testing to include any prototypes. The Contractor shall deliver the detailed Anti-Tamper solution as an Anti-Tamper Plan submission in accordance with CDRL A004 and the ACV Security Classification Guide, Attachment 25, and shall incorporate the solutions into the ACV design.

PROGRAM MANAGEMENT

The Contractor shall provide a qualified Program Manager (PM) that shall be responsible for the accomplishment of all tasks in this SOW. The Contractor’s PM shall plan, organize, manage, schedule, implement, control, analyze, and report on all elements of the SOW. The Contractor’s PM shall have resources and authority to efficiently and effectively execute tasks necessary to complete the requirements. The Contractor’s PM shall be prepared to present and discuss the status of contract activities, requirements, and issues with the PM AAA ACV Product Manager (PdM), the Contracting Officer, and the Contracting Officer Representative (COR).

The Contractor shall execute the program with established, defined, and repeatable organizational processes, procedures, and policies unless otherwise directed within this SOW or other Government regulations, policies, and/or direction.

The Contractor shall deliver all Unclassified/Classified CDRLs in accordance with each DD Form 1423 and the CDRL Submission Instructions, per Attachment 04.

Assignment of Responsibility and Authority

The Contractor shall identify clear lines of authority, within their organization, of the personnel who shall be responsible for conducting all activities delineated in this SOW. Those individuals shall be responsible for determining and controlling the resources necessary to satisfy each element of this SOW.

Conferences, Reviews, Agendas, And Reports

The Contractor shall plan, host, attend, coordinate, provide administrative support and conduct meetings, formal reviews and events, conferences, and audits (hereinafter called "reviews") in conjunction with the Government. The reviews shall be conducted at the Contractor’s or Government’s facilities, as indicated in Attachment 03, Meeting List. The reviews shall be included in the IMS, and multiple reviews may be held concurrently with the Government’s approval.

Prior to each review, the Contractor shall prepare agendas for Government approval, unless waived by the Government, in accordance with CDRL A006. The Contractor shall provide Conference Reports following each review, in accordance with CDRL A008. Action item documentation, assignment of responsibility for completion and due dates will be determined by the Government Chairperson prior to adjournment of all reviews. A summary of all action items, responsible parties, and completion dates shall be included with the meeting minutes.

Post-Award and Contract Option POST-Award Conferences

Post-Award Conference

The Post-Award Conference (PAC) is the first meeting of key Contractor and Government personnel. This PAC is to achieve a clear and mutual understanding of all contract requirements between the Government and the Contractor, and identify and resolve potential problems to ensure successful contract performance. The PAC shall be conducted within 20 calendar days after contract award, per Attachment 03, Meeting List. The PAC shall include Contractor representatives, the cognizant Contract Administration Office and the Contracting Officer. The Contracting Officer, or designated representative, initiating the conference, will designate or act as the chairperson. The contractor shall participate with the Government to draft an agenda for the PAC, prior to the meeting.

Contract Option Post-Award Conference

A contract Option PAC shall be held within 20 calendar days after exercise of the LRIP and FRP CLINs (Options, if exercised) per Attachment 03, Meeting List. The attendees shall include the Contractor, contracting representative, Government Contracting Officer, management, and technical personnel from both the Government and the Contractor. The Contractor shall participate with the Government to arrange a schedule and agenda for the PAC prior to the meeting.

Program Management Plan

The Contractor shall develop a Program Management Plan (PMP). The PMP shall describe the approach, resources, and needs of the Contractor to perform the effort. The PMP shall encompass technical, management, schedule, and cost data. The Contractor shall prepare and submit the PMP in accordance with CDRL A005.

Program Management Reviews

The Contractor shall participate in PMRs during EMD, LRIP (Option, if exercised) and FRP (Option, if exercised) to assess program cost, schedule, performance, process implementation, risk, and status related to the execution of the ACV Program per Attachment 03, Meeting List. The PMRs may be held in conjunction with other reviews and conferences for efficiency. The Contractor shall summarize the following during each PMR:

1) Work completed (inclusive of meeting action items)

2) Work planned for upcoming quarter

3) Contract tasks not completed

4) Significant accomplishments

5) Problems or delays

6) Corrective actions

7) Schedule updates and Critical Path Analysis

8) Other program or personnel changes

9) Risk Management Status (Cyber Security and Safety included)

10) Configuration Management

11) IMS review with critical path and supporting metrics

12) Schedule Risk Assessment (SRA) review with supporting metrics

13) Contractor Cost Data Reporting (CCDR) with most recent cost estimates

14) Status Report for each Integrated Product Team (IPT) or Team

15) Project Metric Status

16) Technical Performance Measures (TPMs)

Monthly Progress Status Reports

The Contractor shall provide a Monthly Progress Status Report for the EMD CLINs, and the LRIP (Option, if exercised) and FRP (Option, if exercised) CLINs in accordance with CDRL A009.

Integrated Master Planning/Integrated Master Scheduling/Schedule Risk Assessment

Contract Integrated Master Plan

The Contractor shall develop and deliver a Contract Integrated Master Plan (IMP) in accordance with the Integrated Program Management Report (IPMR), CDRL A010. The Contract IMP shall be traceable to the Government Program IMP, provided in Attachment 05, Program IMP, and shall include all accomplishments and criteria necessary to achieve each identified Program IMP event. The Contractor shall maintain the IMP throughout the PoP and if changes occur, obtain written Government approval. The Contract IMP shall be statused by the Contractor to the third level of the Government Work Breakdown Structure (WBS). The IMP shall comply with the “DoD Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide.” If the Contract IMP requires additional IMP accomplishment criteria to be added to the Program IMP, the Contractor can request a change to the Program IMP. The Government will use an established internal process to evaluate the proposed change prior to approval. The Contractor shall liaison with the COR to facilitate the integration of all Contract IMP events, accomplishments, and criteria into the ACV Program IMP.

Contract Integrated Master Schedule

The Contractor shall decompose the Contract IMP into a time-based IMS showing the detailed tasks required to accomplish the work effort contained in the Contract IMP. The Contractor shall develop and deliver the Contract IMS in accordance with IPMR, CDRL A010. The Contractor shall liaison with the COR to facilitate the integration of key Contract IMS milestones and tasks into the Program IMS. The Contractor shall develop task definitions that include task durations and dependencies with other Contract IMS Tasks. The Contractor shall maintain the Contract IMS and the Government will ensure key Contract IMS milestones and tasks are fully integrated into the Program IMS. The Contractor shall provide an IMS Narrative Report and Analysis to reflect changes in the Contract IMS, in accordance with IPMR, CDRL A010. In addition, the Contractor shall perform system critical path and near-critical path analyses to the closest major acquisition MS (e.g., MS C) and to each key system-level technical review (e.g., PDR/CDR, VAR). The Contractor shall provide the results of the analyses and Corrective Action Plans in the IMS Narrative Report and Analysis to resolve those efforts negatively impacting the critical path, in accordance with the IMPR, CDRL A010.

The Contract IMS shall meet the below listed requirements:

1. Define all tasks required to execute the Government-approved Contract IMP. Define all internal and external schedule dependencies necessary to execute the Contract IMS.

1. Incorporate material order, material delivery, fabrication, assembly, and test for vehicle production and delivery into the IMS (e.g., EMD CLINs, LRIP (Option, if exercised) CLINs, and FRP (Option, if exercised) CLINs).

1. Include Contractor tasks required to accomplish each IMP event and relevant subcontractor scheduled milestones necessary for the achievement of each Contract IMS event.

1. Include all CDRL deliveries and events as defined by the IMP.

1. Be vertically traceable to the Contract IMP, the Contract Work Breakdown Structure (CWBS), and the Contract SOW and horizontally traceable to all dependent project tasks, identifying the relationships and constraints between project tasks.

Schedule Risk Assessment

A probabilistic SRA shall be developed and submitted in accordance with IPMR CDRL A010. The SRA will provide the Government with an understanding of the potential schedule impacts associated with existing or emerging program risks. These analyses shall compute the probability of completing key milestones, events, and tasks/activities by specific dates. The Contractor shall report optimistic, pessimistic, and most likely remaining durations and rationale for the values in accordance with the Contract IMS for each task/activity on the following paths: critical path to contract completion, critical path to the next Major MS (e.g. MS C), and the next three (3) near-critical paths to the next Major MS. Global weighting values and rationale shall also be provided by the Contractor. In addition, the Contractor technical team members shall be asked to provide pessimistic, most likely, and optimistic durations for moderate to high risk activities identified in the Program Risk Database (generally identified through a risk cube) that are associated with IMS tasks.

Contractor Work Breakdown Structure

The Contractor shall refine the WBS Index and Dictionary developed by the Government at an appropriate level to make the resulting structure program specific, and to facilitate effective Program Management; in accordance with MIL-HDBK-61A, Work Breakdown Structures for Defense Materiel Items. The Contractor shall establish the CWBS definition at a level necessary to identify work progress and enable effective management, regardless of the CWBS level reported per Attachment 06, Cost and Software Data Reporting (CSDR) Plan, for program oversight. The Contractor shall be responsible for periodic updates and maintenance of the CWBS at the level below the required reporting level established per Attachment 06, CSDR Plan, according to the provisions set forth in the CWBS. Changes to the reporting level CWBS, as specified per Attachment 06, CSDR Plan, require a contractual modification before incorporation; however, the Contractor has complete flexibility to extend the CWBS below the reporting level to reflect how work is accomplished. The CWBS shall not be influenced by the Contractor’s organizational structure. For reporting purposes, the CWBS is required to be the same for CCDR and IPMR, though reporting levels may be different for each report. The Contractor shall prepare and deliver the CWBS Index and Dictionary in accordance with CDRL A011.

Earned Value Management reserved

Earned Value Management System Requirements – Subcontractors

The Contractor shall flow down EVMS requirements to subcontractors as follows:

1) Those subcontractors valued at or greater than $50M in then-year dollars shall have an EVMS that has been formally validated and accepted by the cognizant Administrative Contracting Officer (ACO) and submit all IPMR formats.

2) Those subcontractors valued at or greater than $20M in then-year dollars shall be required to submit IPMR formats 1, 5, 6 and 7 in accordance with CDRL A010.

3) The Contractor shall identify the subcontractors to whom the EVMS requirements shall apply. The Contractor and the Government shall agree to the subcontractors or the subcontracted effort selected for application of the EVMS requirements. The Contractor shall be responsible for ensuring that the selected subcontractors comply with the requirements of the EVMS clause of the contract.

The Contractor shall fully integrate cost, schedule, and technical performance information reported by the subcontractors into the Contractor’s EVMS. The Contractor shall be responsible for reviewing and assuring the validity of all reporting subcontractors.

Earned Value Management System Access and Reports

The Contractor shall provide the Government electronic access at all times to the EVMS information and supporting documentation, within the IPMR, in accordance with CDRL A010. The Contractor shall include complete data, in a format compatible with Deltek’s “wInsight” Earned Value Management (EVM) software as part of each report. Retroactive changes to records pertaining to work performed that would change previously reported amounts for direct costs, indirect costs, or budgets, except for correction of errors and routine accounting adjustments, are prohibited.

Earned Value Management System Acceptance

The Contractor shall provide a copy of Government acceptance of its EVMS if the system has already been accepted as compliant with the EVMS Guidelines of ANSI/EIA-748-A-1998 (R2002). Otherwise, the Defense Contract Management Agency (DCMA) will perform system surveillance, review, and validation of the Contractor’s EVMS process during contractual performance. The Contractor shall implement its previously accepted EVMS upon contract award; or if not previously accepted, upon Government acceptance. The EVMS, tailored to the requirements of the ACV EMD contract, shall be prepared by the Contractor for Government review at the Integrated Baseline Review (IBR). The Contractor shall prepare and deliver the EVMS Description and the IPMR in accordance with CDRLs A012 and A010 (DD Forms 2734/1, 2734/2, 2734/3, 2734/4, 2734/5, Format 6, Format 7)

Earned Value Manangement Program Management Reviews

The Contractor shall conduct monthly reviews, during EMD, of the IPMR data with the Government per Attachment 03, Meeting List. The Contractor shall conduct quarterly EVM PMR meetings with the Government, per Attachment 03, Meeting List. During these reviews, the Contractor shall present integrated cost, schedule, and technical performance status. IPT leads or functional managers shall include cost information in discussions of schedule status, technical performance, and risk using earned value as an integrating tool. The following shall be addressed (including subcontract efforts): Cost/schedule trends, significant cost/schedule/technical variances, projected impacts, quantified risk assessments, and Corrective Action Plans.

Over Target Baseline/Over Target Schedule/Restructure

During EMD contract performance, the Contractor may conclude the baseline no longer represents a realistic plan in terms of budget/schedule execution. In the event the Contractor determines an Over Target Baseline (OTB)/Over Target Schedule (OTS)/Restructuring action is necessary, the Contractor shall obtain Government approval prior to implementing an OTB/OTS/Restructuring action. The Contractor’s request shall also include detailed implementation procedures as well as an implementation timeframe. The Contractor shall not implement the OTB/OTS/Restructuring prior to receiving written approval from the Contracting Officer.

Integrated Baseline Review

The Government will verify during the IBR that the Contractor has established and maintains a reliable PMB, which includes the entire contract technical scope of work for which earned value measurement is applicable. Tasks shall be planned by CWBS element and cross referenced against SOW paragraphs. The Contractor shall perform a self-assessment of cost and schedule risk for the IBR. The Contractor shall participate in an IBR, per Attachment 03, Meeting List.

Cost Estimating and Analysis

Contractor Cost and Software Data Reporting

The Contractor shall systematically collect and report actual contract costs to provide DoD cost analysts with needed data to estimate future costs. The Contractor shall prepare the Cost Data Summary Report (CDSR), Functional Cost Hour Report (FCHR), Progress Curve Report (PCR), and Contractor Business Data Report (CBDR) in accordance with CDRLs: A013, A014, A015, and A016.

In accordance with DoDI 5000.02 (Interim) and DFARS 252.234-7003, “Notice of Cost and Software Reporting System”:

1) The scope of effort includes:

a) The Government-approved CSDR Plan for the contract, DD Form 2794; and

b) The preparation of the related Resource Distribution Table.

2) In the performance of this contract, the Contractor shall use:

a) A documented standard CSDR process that satisfies the guidelines contained in the DoD 5000.04–M–1, CSDR Manual;

b) Management procedures that provide for generation of timely and reliable information for the CCDRs and Software Resources Data Reports (SRDRs) required by the CCDR and SRDR data items of this contract;

c) The Government-approved CSDR Plan for this contract, DD Form 2794, and the related Resource Distribution Table as the basis for reporting according to the required CSDR DIDs;

d) The Contractor shall require and flow down the requirement for CSDR reporting from subcontractors regardless of tier with a subcontract that exceeds $50 million or subcontracts valued between $20 million and $49 million that are designated by the Government as being high risk, high value, or high technical interest.