Attachment_01_141105_-_MASTER_SOW_-_For_RFP_First_Draft_Release.docx
DOCX document 462 KB Posted
- Attached to
- Amphibious Combat Vehicle (ACV) 1. 1 Federal contract opportunity
- Solicitation number
- M67854-15-R-0001
- Issued by
- United States Marine Corps
About this file
Attachment 1 SOW
View the file
Other files for this federal contract opportunity
Show all 50
Amphibious Combat Vehicle (ACV) 1. 1 has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
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.2 5 Nov 2014
DISTRIBUTION A: Approved for public release: distribution unlimited.
| Revision |
| Date |
| Summary of Changes |
ACV-SOW-03001
This page blank
| 1 | SCOPE | 1 |
| 1.1 | BACKGROUND | 1 |
| 1.2 | INTRODUCTION OF THE STATEMENT OF WORK | 2 |
| 2 | APPLICABLE DOCUMENTS | 2 |
| 2.1 | GOVERNMENT DOCUMENTS | 2 |
| 2.1.1 | Specifications, Standards, and Handbooks | 2 |
| 2.2 | OTHER GOVERNMENT DOCUMENTS, DRAWINGS, AND PUBLICATIONS | 4 |
| 2.2.1 | Regulations, Federal Acquisition Regulations, Defense Federal Acquisition Regulation Supplements, Manuals, Directives, Instructions, and Forms | 4 |
| 2.3 | NON-GOVERNMENT DOCUMENTS | 6 |
| 2.3.1 | Standards and Guidebooks | 6 |
| 2.4 | AVAILABILITY OF DOD DOCUMENTS | 8 |
| 3 | REQUIREMENTS | 8 |
| 3.1 | GENERAL REQUIREMENTS OVERVIEW | 9 |
| 3.1.1 | Resource Requirements | 9 |
| 3.1.2 | Security | 9 |
| 3.1.3 | Operations Security Plan | 9 |
| 3.1.4 | Program Protection Implementation Plan | 9 |
| 3.1.5 | Government Furnished Information | 13 |
| 3.2 | PROGRAM MANAGEMENT | 13 |
| 3.2.1 | Assignment of Responsibility and Authority | 13 |
| 3.2.2 | Conferences, Reviews, agendas, and meeting minutes | 13 |
| 3.2.3 | Monthly Progress Status Reports | 14 |
| 3.2.4 | Integrated Master Planning/Integrated Master Scheduling/Schedule Risk Assessment | 15 |
| 3.2.5 | Contractor Work Breakdown Structure | 16 |
| 3.2.6 | Earned Value Management | 16 |
| 3.2.7 | Integrated Baseline Review | 17 |
| 3.2.8 | Cost Estimating and Analysis | 18 |
| 3.2.9 | Contractor Controlled Cost | 19 |
| 3.2.10 | Life Cycle Cost Estimate | 20 |
| 3.2.11 | Bill of Material Pricing Report | 20 |
| 3.2.12 | Time Series Lot Size Pricing Data | 20 |
| 3.2.13 | Financial Management | 21 |
| 3.3 | SYSTEMS ENGINEERING | 21 |
| 3.3.1 | Technical Reviews | 21 |
| 3.3.2 | Systems Engineering Management | 22 |
| 3.3.3 | Quality | 23 |
| 3.3.4 | Requirements Management | 23 |
| 3.3.5 | Interface Control Diagrams | 23 |
| 3.3.6 | Product Drawings/Models | 24 |
| 3.3.7 | Open Systems | 24 |
| 3.3.8 | Configuration Management | 25 |
| 3.3.9 | Vehicle Configuration Data | 26 |
| 3.3.10 | Configuration Audits | 26 |
| 3.3.11 | Configuration Control | 28 |
| 3.3.12 | Contractor Verification Report | 28 |
| 3.3.13 | Technology | 28 |
| 3.3.14 | Environmental, Safety, and Occupational Health | 28 |
| 3.3.15 | Software Requirements Specification | 31 |
| 3.3.16 | Calibration Updates | 32 |
| 3.3.17 | Data Rights | 32 |
| 3.3.18 | Diminishing Manufacturing Sources and Material Shortages | 33 |
| 3.3.19 | RESERVED | 33 |
| 3.3.20 | Ballistic Protection Test and Analysis | 33 |
| 3.3.21 | Force Protection and Vulnerability Reduction | 34 |
| 3.3.22 | NATO Reference Mobility Model Analysis | 35 |
| 3.3.23 | NATO Reference Mobility Model Ride Quality Analysis | 35 |
| 3.3.24 | Seaworthiness Analysis | 36 |
| 3.3.25 | Corrosion Prevention and Control Plan | 37 |
| 3.3.26 | Thermal Analysis Requirements | 37 |
| 3.3.27 | Launching from Amphibious Ships Analysis | 37 |
| 3.3.28 | Watertight Integrity Analysis | 38 |
| 3.3.29 | Human Systems Integration | 39 |
| 3.3.30 | Weight Control and Reporting | 40 |
| 3.3.31 | Load Plan | 41 |
| 3.3.32 | Reliability Program Management | 42 |
| 3.3.33 | Failure Reporting, Analysis, and Corrective Action System | 43 |
| 3.3.34 | Corrective Action Period | 45 |
| 3.4 | MANUFACTURING OF THE EMD/LRIP/FRP VEHICLES | 46 |
| 3.4.1 | Manufacturing Plan | 46 |
| 3.4.2 | Manufacturing Readiness Assessment for EMD/LRIP/FRP | 46 |
| 3.4.3 | Critical Process | 47 |
| 3.4.4 | Process Failure Modes and Effects Analysis | 47 |
| 3.4.5 | Vehicle Assembly and GFE Integration | 47 |
| 3.4.6 | Break-In Operations | 48 |
| 3.4.7 | Contractor Acceptance Test | 48 |
| 3.4.8 | Reset LRIP IOT&E Vehicles | 49 |
| 3.5 | TEST AND EVALUATION | 49 |
| 3.5.1 | Management and Support | 49 |
| 3.5.2 | Government Test and Evaluation on EMD Vehicles | 56 |
| 3.5.3 | Government Test and Evaluation on LRIP Vehicles | 60 |
| 3.5.4 | Transportation | 62 |
| 3.6 | LOGISTICS | 62 |
| 3.6.1 | Logistics Management Information | 62 |
| 3.6.2 | Supportability Analysis | 63 |
| 3.6.3 | Supply Support | 65 |
| 3.6.4 | Packaging, Handling, Storage, and Transportation for LRIP and FRP CLINS | 66 |
| 3.6.5 | Training Products and Services for EMD Build and LRIP Clins | 67 |
| 3.6.6 | Technical Manuals | 72 |
| 3.7 | GOVERNMENT PROPERTY | 74 |
| 3.7.1 | Schedule of Government Furnished Property | 74 |
| 3.7.2 | Government Property Management | 74 |
| 3.8 | DISPOSITION OF EMD VEHICLES | 76 |
| 3.9 | CROSSWALK MATRIX | 77 |
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-32216A |
| Evaluation of Commercial Off the Shelf Manuals and Preparation of Supplemental Data1 |
| 12 Aug 2011 |
MIL-PRF-29612-2
Instructional Systems Development/Systems Approach to Training and Education
30 Jul 1999
DEPARTMENT OF NAVY
| ACV-SPE-02003 |
| Amphibious Combat Vehicle Phase I, Increment 1 System Performance Specification |
| Draft |
STANDARDS
DEPARTMENT OF DEFENSE
| MIL-STD-129-R |
| Military Marking for Shipment and Storage |
| 18 Feb 2014 |
| MIL-STD-130-N, Change 1 |
| Identification Marking of U.S. Military Property |
| 16 Nov 2012 |
| MIL-STD-464C |
| Electromagnetic Environmental Effects Requirements for Systems |
| 1 Dec 2010 |
| MIL-STD-882E |
| System Safety |
| 11 May 2012 |
| MIL-STD-961E(2), Note 3 |
| Defense and Program Unique Specifications Format and Content |
| 9 Jan 2014 |
| MIL-STD-2073-1E, Change 1 |
| Standard Practice for Military Packaging |
| 7 Jan 2011 |
| MIL-STD-3018, Change 1 |
| Parts Management Program |
| 27 Oct 2011 |
| MIL-STD-31000A |
| Technical Data Packages |
| 26 Feb 2013 |
| MIL-STD-881C |
| Work Breakdown Structures for Defense Materiel Items |
| 03 Oct 2011 |
GUIDEBOOKS
DEPARTMENT OF DEFENSE
| DoD Guide |
| Integrated Management Plan and Integrated Master Schedule Preparation and Use Guide |
21 Oct 2005
| DoD Guide |
| Risk Management Guide for DoD Acquisition, Sixth Edition (Version 1.0) |
| Aug 2006 |
| DoD MRA Deskbook |
| DoD Manufacturing Readiness Assessment Deskbook, Version 7.1 |
| 2 May 2009 |
| DoD MRL Deskbook |
| DoD Manufacturing Readiness Level Deskbook, Version 2.21 |
| Oct 2012 |
| DoD 4140.1-R |
| Supply Chain Materiel Management Regulation |
| 23 May 2003 |
| SD-22 |
| Diminishing Manufacturing Sources and Manufacturing Shortages (DMSMS) Guidebook |
| 13 Jun 2012 |
DEPARTMENT OF ARMY
| TARADCOM R&D Laboratory Technical Report 12503 |
| NATO Reference Mobility Model, Edition II User’s Guide Volume 1 |
Oct 1979
| Department of the Army Pamphlet (DA PAM) 73-1 |
| Test and Evaluation in Support of Systems Acquisition |
| 30 May 2003 |
| OPNAVI 5513.11 Enclosure 093 |
| Amphibious Combat Vehicle (ACV) Security Classification Guide |
| 19 April 2012 |
| NAVMC 1553.1 |
| Systems Approach To Training User's Guide, Short Title: SAT User Guide |
| 27 Oct 2010 |
| NAVSEA S9310-AQ-SAAF-010 |
| U.S. Navy Lithium Battery Safety Program Technical Manual: Responsibilities and Procedures |
| 15 Jul 2010 |
HANDBOOKS
DEPARTMENT OF DEFENSE
| MIL-HDBK-419A |
| Grounding, Bonding, and Shielding for Electronic Equipment’s and Facilities, Volumes I & II |
20 Feb 2014
| MIL-HDBK-61A |
| Configuration Management Handbook |
| 7 Feb 2001 |
OTHER GOVERNMENT DOCUMENTS, DRAWINGS, AND PUBLICATIONS
Regulations, Federal Acquisition Regulations, Defense Federal Acquisition Regulation Supplements, Manuals, Directives, Instructions, and Forms
REGULATIONS
DEPARTMENT OF ARMY
| AR 73-1 |
| Army Regulation T&E Policy |
| 1 Aug 2006 |
DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENTS
| DFARS 252.211-7003 |
| Item Unique Identification |
| Dec 2013 |
| DFARS 252.234-7003 |
| Notice of Cost and Software Data Reporting System |
| Nov 2010 |
MANUALS
DEPARTMENT OF DEFENSE
| DoD 5000.04–M–1 |
| Cost and Software Data Reporting Manual |
4 Nov 2011
| DoD 5220.22-M |
| National Industrial Security Program Operating Manual |
28 Feb 2006
| NAVSEA S9310-AQ-SAAF-010 |
| U.S. Navy Lithium Battery Safety Program Technical Manual: Responsibilities and Procedures |
| 15 Jul 2010 |
DEFENSE LOGISTICS AGENCY
| DLM 4000.25-M |
| Military Standard Requisitioning and Issue Procedures |
13 Jun 2012
DIRECTIVES
| DoDD 8570.01 |
| Information Assurance Training, Certification, and Workforce Management |
| 15 Aug 2004 |
INSTRUCTIONS
| DoDI 5000.02 (Interim) |
| Operation of the Defense Acquisition System |
| 26 Nov 2013 |
| DoDI 5200.39, Change 1 |
| Critical Program Information Protection within DoD |
| 28 Dec 2010 |
| DoDI 8510.01 |
| Risk Management Framework for DoD Information Technology |
| 12 Mar 2014 |
| DoDI 8520.2 |
| Public Key Infrastructure and Public Key Enabling |
| 24 May 2011 |
| DoDI 8582.01 |
| Security of Unclassified DoD Information on Non-DoD Information Systems |
| 6 Jun 2012 |
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
| MCO 4790.25 |
| Ground Equipment Management Program |
| 12 Jan 2014 |
| OPNAVINST 3000.1A |
| Operational Availability of Equipment’s and Weapon Systems |
| 2 Sep 2003 |
| OPNAVINST 3432.1A |
| Operations Security |
| 4 Aug 2011 |
FORMS
| DD254 |
| Contract Security Classification Specification, Department of Defense |
| Dec 1999 |
| DD1423 |
| Contract Data Requirements List |
| Aug 1996 |
| DD1586 |
| Contract Funds Status Report |
| Aug 1996 |
| DD2734/1 |
| Contract Performance Report, Format 1, Work Breakdown Structure |
| Apr 2005 |
| DD2734/2 |
| Contract Performance Report, Format 2, Organizational Categories |
| Apr 2005 |
| DD2734/3 |
| Contract Performance Report, Format 3, Baseline |
| Apr 2005 |
| DD2734/4 |
| Contract Performance Report, Format 4, Staffing |
| Apr 2005 |
| DD2734/5 |
| Contract Performance Report, Format 5, Explanations and Problem Analyses |
| Apr 2005 |
| DD2794 |
| Cost and Software Data Reporting Plan |
| May 2011 |
GSA Optional Form
| OF 346 |
| U.S. Government Motor Vehicle Operators Identification Card |
Nov 1985
NON-GOVERNMENT DOCUMENTS
Standards and Guidebooks
STANDARDS
| SAE GEIAHB0007 Rev B |
| Logistics Product Data Handbook |
| 10 Feb 2014 |
| ANSI/EIA 748-A-1998 |
| Standard for Earned Value Management Systems Intent Guide |
| January 2005 |
| ASME Y14.24 |
| Types and Application of Engineering Drawings |
| 1 Jan 2012 |
| ASME Y14.34 |
| Associated Lists |
| 1 Jan 2013 |
| ASME Y14.35 |
| Revision of Engineering Drawings and Associated Documents |
| 8 Dec 1997 |
| ASME Y14.41 |
| Digital Product Definition Data Practices |
| 14 May 2012 |
| ASME Y14.5-2009 |
| Geometric Dimensioning and Tolerancing |
| 9 Feb 2009 |
| ASME Y14-100 |
| Engineering Drawing Packages |
| 30 Jul 2013 |
| ASTM-D-3951 |
| Standard Practice For Commercial Packaging |
| 2004 |
| ISO 9001:2008 |
| Quality Management Principles |
| 2008 |
| NAS 411-1:2013 |
| National Aerospace Standard: Hazardous Materials Target List |
| 30 Sep 2013 |
| NISTIR 7622 |
| National Institute of Standards and Technology Interagency Report 7622, “Notional Supply Chain Risk Management Practices for Federal Information Systems: Piloting Supply Chain Risk Management for Federal Information Systems” |
Oct 2012
| SAE JA1011 |
| Evaluation Criteria for Reliability-Centered Maintenance Processes |
| Aug 1999 |
| SAE JA1013 |
| A Guide to the Reliability-Centered Maintenance Standard |
| Jan 2002 |
GUIDEBOOKS
International Society of Weight Engineers, Inc, Recommended Practice Number 5
| Mass Properties Control System for Wheeled and Tracked Vehicles, Revision A |
| 26 May 2007 |
| National Defense Industrial Association System Assurance Committee |
| Engineering for System Assurance Version 1.0 |
| 2008 |
MANUALS
| Automotive Industry Action Group FMEA Manual |
| 4th Edition of Industry Standards |
| 2008 |
AVAILABILITY OF DOD 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 Contractors 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 performance, 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:
· 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 unclassified controlled technical and administrative data associated with the ACV from unauthorized access or disclosure according DoDI 8582.01, "Security of Unclassified DoD Information on Non-DoD Information Systems."
Operations Security Plan
The Contractor shall develop and implement an Operations Security Plan (OPSEC) as defined in the DD Form 254. OPNAVINST 3432.1A, “Operations Security” and Marine Corps Order (MCO) 3070.2A “The Marine Corps OPSEC Program” provides additional information for guidance. The OPSEC Plan shall define the processes and procedures the Contractor will use to protect ACV classified and/or sensitive unclassified program information and material at all levels of classification through all stages of Contractor-managed product design and development. 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 in accordance with CDRL A002. 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 |
| Description |
| Level I: Total Mission Failure |
| Function/component failure is a failure that results in total compromise of mission capability |
Level II: Significant/Unacceptable Degradation Function/component failure is a failure that results in unacceptable compromise of mission capability or significant mission degradation
| Level III: Partial/Acceptable |
| Function/component failure is a failure that results in partial compromise of mission capability or partial mission degradation |
| Level IV: Negligible |
| Function/component failure is a failure that results in little or no compromise of mission capability |
Table (1) Protection Failure Criticality Levels
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) The application of supply chain risk management best 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, “Notional Supply Chain Risk Management Practices for Federal Information Systems: Piloting Supply Chain Risk Management (SCRM) for Federal Information Systems,” and the National Defense Industrial Association System Assurance Committee, “Engineering for System Assurance Version 1.0.”
2) For potential suppliers of critical components to be solicited, the Contractor shall identify and enumerate relevant cost, schedule, and performance information to be used to choose between alternates. The Contractor shall define associated risks and work with the Government to develop mutually-agreeable risk management plans.
3) The 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) Contractor shall establish and maintain 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 and that processes and requirements for genuine components are levied upon subcontractors. The process and practices should address detecting and avoiding the use or inclusion of counterfeit electronic parts or suspect counterfeit electronic parts; use of trusted suppliers, and requirements for subcontractors to report counterfeit electronic parts and suspect counterfeit electronic parts.
5) The process used to protect unclassified DoD 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
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 Assessment identifying Critical Program Information or Critical Technology (CT) (defined by DoDI 5200.39, July 16, 2008 Incl Change 1 Dec 28, 2010, Critical Program Information (CPI) Protection within the DoD)
· A classified session for the Contractor’s Anti-Tamper Plan and status of the Anti-Tamper Solution’s implementation
Each meeting will be a one (1) day event. After the event, the Government will provide a Procuring Contracting Officer (PCO) letter to the Contractor validating the Critical Program Information/Critical Technology (CPI/CT) is properly identified for the program.
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 shall 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 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), and System Verification Review (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 Contractor testing to include any prototypes. The Contractor shall deliver the detailed Anti-Tamper solution as an Anti-Tamper Plan in accordance with CDRL A004 and shall incorporate the solution into the ACV design.
Government Furnished Information
The Government will furnish Government Furnished Information (GFI) as deemed necessary by the Government to assist the Contractor in the performance of the contract requirements. GFI will be provided to the Contractor within 30 days of receipt of Contractor’s written request to the Program Manager Advanced Amphibious Assault (PM AAA) Government Property Manager. The Contractor shall provide for accountability, security, and storage of the GFI provided. GFI provided after contract award will be listed per Attachment 10, Government Furnished Equipment (GFE)/GFI.
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), PCO and Contracting Officer Representative (COR). The Contractor shall provide and maintain a Program Management Plan (PMP) for the EMD contract and the LRIP (Option, if exercised) and FRP (Option, if exercised) CLINs, in accordance with CDRL A005.
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 identify the approach to be implemented and shall provide a detailed status for tailoring of these organizational processes for the ACV Program.
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 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 meeting minutes
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 will be conducted at Contractor or Government facilities as indicated in Attachment 03, Meeting List. Reviews associated with test readiness testing will be conducted at the locations specified in the Meeting List, Attachment 03. Reviews shall be included in the IMS, and multiple reviews will be held concurrently with the Government’s approval.
The Contractor shall prepare agendas for Government approval, prior to each review, unless waived by the Government, in accordance with CDRL A006. The Contractor shall provide meeting minutes 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 estimated 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 conference 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 performance. A PAC shall be conducted within 20 calendar days after contract award, per Attachment 03, Meeting List. The PAC shall include representatives of the Contractor, the cognizant Contract Administration Office, and the PCO and shall be held at the Contractor’s U.S. facility. The Contracting Officer, or designated representative, initiating the conference, will designate or act as the chairperson. The Contracting Officer or their designee will provide the agenda.
Contract Option Post-Award Conference
A contract Option PAC shall be held at the Contractor’s U.S. facility within 20 calendar days after exercise of the LRIP and FRP (Options, if exercised) per Attachment 03, Meeting List. The attendees shall include Contractor and Government contracting, management, and technical personnel. The Contractor shall participate with the Government to arrange a schedule and agenda for the PAC prior to the meeting.
Program Management Reviews
The Contractor shall conduct PMRs during the EMD, and the LRIP (Option, if exercised) and FRP (Option, if exercised) Phases 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 (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
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 or CDR). 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 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 taskings.
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.
reserved
Earned Value Manangement Program Management Reviews
The Contractor shall conduct monthly reviews 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 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.
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. If, for subcontracts that exceed $50 million, the Contractor changes subcontractors or makes new subcontract awards, the Contractor shall notify the Government.
3) CSDR PAC:
A CSDR PAC, per Attachment 03, Meeting List will be held 20 days after contract award to include a discussion of the CSDR process that satisfies the guidelines contained in the DoD 5000.04-M- 1, “CSDR Manual,” and the requirements in the Government-approved CSDR Plan for the contract, DD Form 2794, and related Resource Distribution Table.
The required reports will be in the form of CDRLs as follows:
· CDRL A013 CDSR (DD Form 1921)
· CDRL A014 FCHR (DD Form 1921-1)
· CDRL A015 PCR (DD Form 1921-2)
· CDRL A016 CBDR (DD Form 1921-3)
· CDRL A017 SRDR: Initial Developer Report and Data Dictionary
· CDRL A018 SRDR: Final Developer Report and Data Dictionary
The CCDR requirements are outlined per Attachment 06, CSDR Plan (DD Form 2794). Inclusive in the plan is the information required by CWBS for the respective Subcontractor and Prime Contractor, schedule for report submission, and specific information as to format, address to send the information, and other pertinent facts.
Contractor Controlled Cost
Contractor Controlled Research, Development, Test and Evaluation Cost
The Contractor shall develop, maintain, and update cost model(s) in Microsoft Excel and provide the Contractor Controlled Research, Development, Test, and Evaluation (CCRDT&E) actuals (as incurred), plus estimates for the program. The Contractor shall provide a Semi-Annual Contractor Controlled Cost Report in accordance with CDRL A019. Detail data to the fourth level of the CWBS shall be provided. The Contractor shall provide CCRDT&E Quarterly Cost Model Reports in accordance with CDRL A019. The CCRDT&E estimate shall incorporate:
1) Designs and changes implemented by the Contractor, subcontractors, and suppliers under the ACV Contract.
2) Design changes approved for implementation by the Government
3) Business base changes at the Contractor’s major subcontractors and suppliers
4) Program Acquisition Strategy changes
5) Contractor manufacturing changes
Contractor Controlled Procurement Cost
The Contractor shall develop, maintain, and update unit cost model(s) in Microsoft Excel and provide the Semi-Annual Contractor Controlled Procurement Cost (CCPC) Report for the program to the Government in accordance with CDRL A019. CCPC includes the costs of all materials, labor, and other direct costs incurred in the fabrication, checkout, and processing of parts, subassemblies, major assemblies, and subsystems needed for the final system, and associated burden (overhead, general and administrative, cost of money, and profit/fee) necessary to…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .