DRAFT_NGCV-OMFV_RFP_(W56HZV-18-R-0174).pdf

Draft Section A

W56HZV-18-R-0174

Section A, Page 1

Note: FAR 52.215-3 Request for Information or Solicitation for Planning Purposes (Oct 1997)

(a) The Government does not intend to award a contract on the basis of this solicitation or to otherwise pay for the information solicited except as an allowable cost under other contracts as provided in subsection 31.205-18, Bid and proposal costs, of the Federal Acquisition Regulation.

(b) Although “proposal” and “Offeror” are used in this Request for Information, your response will be treated as information only. It shall not be used as a proposal.

(c) This solicitation is issued in DRAFT form for planning purposes only. ACC- WRN intends to review and consider all feedback from Industry submitted in response to this DRAFT solicitation regarding the NGCV-OMFV requirement.

NOTE: The Government is only releasing the following attachments with this draft solicitation:

- Attachment 0001, DD 254, Revision 1

- Attachment 0005, OMFV Security Classification Guide

- Attachment 0009, Government Furnished Property List

- Attachment 0021, Government’s Detailed Test Schedule

- Attachment 0040, VATEP Workbook*

- Attachment 0043, Bid Sample Evaluation Plan (BSEP)

- Attachment 0045, Requirements Compliance Matrix

* The VATEP credit values will be provided at a later date.

Note: This Executive Summary is provided as a convenience to highlight the program requirements contained within the RFP. In the event of any inconsistencies, the RFP requirements take precedence.

Optionally Manned Fighting Vehicle (OMFV) Executive Summary

1) OMFV Program Overview:

a. The Optionally Manned Fighting Vehicle (OMFV) vehicle is a new combat vehicle that will be designed for and used by military forces to maneuver Soldiers in the future operating environment (FOE) to a position of advantage, in order to engage in close combat and deliver decisive lethality during the execution of combined arms maneuver.

The NGCV-OMFV must exceed current capabilities while overmatching similar threat class systems. It must be optimized for dense urban areas while also defeating pacing threats on rural (open, semi-restricted and restricted) terrain and be characterized by the ability to spiral in advanced technologies as they mature.

Section A, Page 2

b. Since its inception, the NGCV-OMFV program has represented an innovative approach to Army acquisition by focusing on delivering an essentially new capability to the Armor Brigade Combat Teams (ABCTs) while under a significantly reduced timeline, as compared to traditional acquisition efforts. This will be achieved by leveraging existing material solutions with proven capabilities coupled with new technologies to meet the requirements. This approach allows the program to enter at Engineering, Manufacturing, and Development (EMD) and alleviate a 2 to 3 year Technical Development phase. The EMD phase will be followed by production and fielding. It is envisioned that upon fielding, the vehicles will be Soldier-maintained and repair parts must be available through the Army Supply System.

c. The Government intends to require follow-on production of the NGCV-OMFV to occur in the United States.

2) Solicitation

a. This solicitation covers only the EMD Phase, which will be solicited on a Firm- Fixed-Price basis.

b. Offerors shall submit proposals in five separate volumes in accordance with paragraph L.2.1. Offerors shall submit Armor Coupons and a Bid Sample to support the proposals in accordance with L.2.1.1 and L.2.1.2, respectively, no later than 01OCT2019.

The Bid Sample and Armor Coupons will be evaluated as substantiating data to the proposals in accordance with Attachment 0043 (Bid Sample Evaluation Plan).

c. Information in this solicitation takes precedence over any information shared by the Government preceding the solicitation release, including but not limited to, information shared at Industry Day, one-on-one sessions, or through Q&As released on the draft

RFP.

d. Assertion of Restrictions: The Offeror shall include in its EMD proposal submission, its Assertion of Restrictions within Attachment 0055 (License Identification and Assertions). Additionally, any proposed special license(s) shall follow the format prescribed within Attachment 0056 (Special License Requirements).

e. Availability of Funding and Affordability: Funds are not presently available for this acquisition. No contract award will be made until appropriated funds are made available.

3) EMD Proposal Evaluation

a. The Government will conduct a full and open competition using Best Value Source Selection procedures for the award of up to two contracts for the EMD phase.

b. The Government will evaluate Offerors’ proposals based on the evaluation criteria as stated within Section M.4 of the RFP. Although not yet fully implemented in this draft solicitation, the Government intends to evaluate Intellectual Property Rights through the VATEP Factor, and intends to conduct a Soldier Assessment as part of the Proposed Performance Factor.

Section A, Page 3

4) EMD Phase:

Up to two EMD contracts are targeted for award during the second quarter of FY20. Each contractor is required to deliver 14 pre-production vehicles in accordance with the Statement of Work and Purchase Description. In addition, the contractor(s) will deliver two Ballistic Hull and Turrets (BH&T) during EMD.

5) Administrative:

a. Eligibility requirements for award and Rejection Criteria are included in the RFP.

Offerors should carefully review the RFP to ensure all requirements for award are met.

b. Access to Classified, FOUO, and Export Controlled Documents: All Offerors must have a valid facility clearance of SECRET or higher in order to respond to this RFP. See the DD Form 254 (Attachment 0001) for security requirements. For Export Controlled information, it is the responsibility of the Offeror, not the Government, to obtain the appropriate export licenses, or process the appropriate export license exemption, necessary for authorization to share information with foreign vendors. Offerors who have not had prior access to FOUO attachments shall send their request to the general mailbox identified in paragraph d. below. Your request shall include the following:

-Your Company's name and address -Your Name, Title, Office phone number and email address -Copy of the approved DD2345

c. Points of Contact:

Corey Richards Procuring Contracting Officer 586-282-5057 usarmy.detroit.peo-gcs.mbx.ngcv-omfv-contracting@mail.mil

Tom Zavela Contract Specialist 586-282-1221 usarmy.detroit.peo-gcs.mbx.ngcv-omfv-contracting@mail.mil

James Giacchina Contract Specialist 586-282-8079 usarmy.detroit.peo-gcs.mbx.ngcv-omfv-contracting@mail.mil mailto:usarmy.detroit.peo-gcs.mbx.ngcv-omfv-contracting@mail.mil

Draft Section C

C.1 Engineering and Manufacturing Development (EMD) The Next Generation Combat Vehicle - Optionally Manned Fight Vehicle (NGCV-OMFV) program will procure a vehicle that provides Armor Brigade Combat Teams (ABCTs) a protected, long range, cyber resilient, precision direct fire capability for early/forcible entry operations. ABCTs require this capability to be employed in austere and unpredictable locations allowing them to avoid the enemy’s strengths and rapidly transition to offensive operations and exploit the initiative. The contractor’s NGCV-OMFV, hereafter referred to as the system, shall meet the requirements of the Contractor’s Purchase Description, Attachment 0097.

C.1.1 Program Management

C.1.1.1 Data Deliverables

C.1.1.1.1 Contract Data Requirements List (CDRL) Data Deliverables The contractor shall deliver data in accordance with (IAW) the Department of Defense (DD) Form 1423, Contract Data Requirements List (CDRLs), as set forth in Section J and as called out in the statement of work (SOW). The days specified in the CDRL are calculated as calendar days unless otherwise specified in a specific CDRL. If a CDRL delivery date falls on a Saturday, Sunday, or Federal Government holiday, the contractor shall deliver the CDRL on the next business day. All data specified in this contract shall be provided using the Government’s CDRL Delivery Tool accessible at https://gcscdrl.tacom.army.mil, unless otherwise specified in the CDRL(s). Within 10 calendar days after contract award, the contractor shall provide the Government with a list of personnel requiring access to the CDRL Delivery Tool. Personnel are required to have either a Government-issued Common Access Card (CAC), Government-approved External Certificate Authority (ECA), or an Army Knowledge Online (AKO) account in order to be provided access to the CDRL Delivery Tool. CDRL Delivery Tool user instructions and training will be provided at the Start of Work Meeting (SOWM).

The contractor shall deliver CDRLs without encryption, locks, passwords, or other security protection features which would prevent the Government from editing, sorting, merging, or otherwise manipulating the data for Government purposes.

C.1.1.1.2 Information Exchanges The contractor shall utilize industry best practices in data management throughout performance of this contract. In conjunction with its data management system, the contractor shall utilize the Government’s NGCV-OMFV SharePoint folder for secure Government exchanges that can be used to facilitate information transmission between the Government and contractor for controlled, distributed access of project information, both released and in-work. Within 10 calendar days after contract award, the contractor shall provide the Government with a list of personnel requiring access to the NGCV-OMFV SharePoint folder. Contractor personnel are required to have either a Government-issued CAC, Government-approved ECA, or an AKO account in order to be provided access to the NGCV-OMFV SharePoint Folder. The SharePoint user instructions and training will be provided to the contractor at the SOWM.

C.1.1.1.3 Classified Data Deliverables All classified information shall be sent via registered mail to the NGCV-OMFV classified mailing address or another secure data transfer environment identified by the Government at the

SOWM.

https://gcscdrl.tacom.army.mil/

C.1.1.1.4 Data Accession List (DAL) The contractor shall provide and update a Data Accession List (DAL) IAW CDRL A001. The contractor shall flow down the DAL requirements to its subcontractors.

C.1.1.2 Support for Meetings, Conferences, and Reviews The contractor shall conduct and administer meetings, reviews, and events. The contractor shall coordinate with the Government to determine the location for meetings. The contractor shall submit an agenda IAW CDRL A002, a read-ahead package IAW CDRL A003, and meeting minutes IAW CDRL A004 for all meetings, Integrated Product Teams (IPTs) (reference SOW paragraph C.1.1.7), and major program reviews (reference SOW paragraph C.1.1.3). The contractor shall track the status and resolution of all action items generated in performance of this SOW in a single action item database and present the status at each meeting. All reviews, meetings, and events administered by the contractor, except for meetings where classified data is discussed, shall have a virtual-based option using the Defense Collaboration Services (DCS) conferencing tool. The contractor shall schedule face-to-face meetings to occur at mutually agreeable time(s) and location(s), and maximize web conferencing to the highest extent possible to minimize personnel resources and travel expenses. The contractor's administrative duties and responsibilities shall include all functions (e.g., providing facilities, sending invitations, media resources, security, minutes, hard copy materials) related to the preparation and execution of the meetings, reviews, and events.

C.1.1.2.1 Meeting Facilities The contractor's facilities shall be multi-media capable; to include a conference room speaker phone, and a large screen with computer projection capabilities that the planned number of attendees can see. The contractor shall coordinate with the Government to determine facility seating requirements for all meetings. Unless otherwise stated, the contractor shall be able to accommodate no less than 10 Government attendees. The contractor shall ensure appropriate Subject Matter Experts (SMEs) are available to advise and answer questions. The contractor shall coordinate with the Government to determine the location for meetings.

The contractor shall be capable of hosting classified meetings at the designated classification level specified in the DD Form 254, Attachment 0001, at a location that shall accommodate no less than 10 Government attendees. The Government will provide larger classified meeting facilities on an as-needed basis for joint Government and contractor classified meetings.

C.1.1.3 Major Program Reviews Major program reviews are defined as follows: SOWM; Program Management Reviews (PMRs);

Design Maturity Review (DMR); Manufacturing Maturity Review (MMR); and Test Readiness Reviews (TRRs).

C.1.1.3.1 Start of Work Meeting (SOWM) The contractor shall host and conduct a SOWM at its facility within 30 calendar days after contract award. The purpose of the SOWM is to discuss and clarify the Government’s expectations for performance during the effort covered by the SOW, meet with the contractor's program team, and align the contractor and Government teams. The contractor shall present key program objectives and risks; provide an overview of its approach; and present key elements of the contract, including the SOW, financial planning, Integrated Master Plan (IMP),CDRL A007, Integrated Master Schedule (IMS), CDRL A008, and all other CDRLs due at

SOWM IAW Exhibit A CDRLs. . The contractor shall present its starting technical baseline, illustrating the technical solution proposed to meet the contract requirements.

C.1.1.3.2 Program Management Reviews (PMR)

C.1.1.3.2.1 The contractor shall host and conduct PMRs every six months, beginning six months after DMR. The PMRs shall include contractor senior-level program management personnel, and shall alternately be held at or near the Government’s location or at or near the contractor's facility. The contractor shall present its current and projected cost, IMS, and performance metrics, along with the risk status at each PMR. The contractor shall also present a list of non-value added CDRLs and/or processes.

C.1.1.3.2.1.2 The final PMR shall be conducted no sooner than XX months after contract award.

In addition to the items in the IMP the following shall be Exit Criteria for the final PMR:

(a) All final CDRL submittals accepted

(b) A final physical inventory of Government Property using Attachment 0006 shall be performed and the resulting report submitted to the COR.

(c) Condition of each test asset described and presented

(d) Contractor and contractor equipment vacated from test sites

(e) All major reviews closed out

C.1.1.3.3 Design Maturity Review (DMR) The contractor shall host and conduct a DMR within six months of contract award. The DMR shall demonstrate how the system design will meet suitability, performance, affordability, supportability, manufacturability, and schedule goals.

The contractor shall provide a Computer Aided Design (CAD) model of the technical solution IAW CDRL A061. The contractor shall provide status on the following items at DMR:

(a) Overall project cost and IMS performance and impacts of the DMR design.

(b) Unit Manufacturing Cost (UMC) estimates.

(c) Project risk assessment and mitigation plans.

(d) The functional, allocated, and initial product baselines.

(e) The Bill of Material (BOM).

(f) The set of system elements comprising the detailed system design, including internal and external interfaces.

(h) Assessment of hardware and computer software hazards associated with the system design.

(i) The detailed designs for external interfaces.

(j) The verification requirements demonstrating achievement of all specified allocated performance characteristics.

(k) Technologies have been demonstrated in a relevant environment and can be integrated into a system with acceptable risk.

(l) Contractor testing, modeling, and simulation results that support the design.

(m) Critical manufacturing processes that affect the system’s key characteristics have been identified and their capability to meet design tolerances has been demonstrated in a production-representative environment.

(n) System hardware element physical architectures and detailed designs.

(o) Detailed designs for Critical Safety Items (CSI) and Critical Application Items (CAI).

(p) Computer software architectures and detailed design.

(q) Cybersecurity approaches.

(r) Program Protection planning.

(s) Management of the 12 Integrated Product Support (IPS) elements.

(t) Provisioning and technical manual conferences.

C.1.1.3.4 Test Readiness Reviews (TRRs) The contractor shall attend and participate in Government-led TRRs for Armor Coupon Testing, Ballistic Hull and Turret (BH&T) testing and Pre-Production Prove-out Testing (PPT), and for the Limited User Test (LUT). The contractor shall present design maturity of the configuration test articles and provide resolution of discrepancies and actions assigned to the contractor. The contractor shall provide access to all pertinent records and data requested by the Government to adequately prepare for the TRR. Reviews will be held at a Government test location within the Continental United States (CONUS).

C.1.1.3.5 Manufacturing Maturity Review (MMR) The contractor shall host a MMR at its facility. The Contractor shall complete the MMR Checklist, Attachment 0003 and have all artifacts available for Government review. Additional MMRs are possible if all items on the MMR Checklist are not answered to the Government’s satisfaction during the initial review.

C.1.1.4 Government Furnished Property (GFP) GFP for this contract includes Government Property (as defined in Federal Acquisition Regulation (FAR) clause 52.245-1), Government Furnished Material (GFM), and Government Furnished Equipment (GFE). The GFP available to the contractor for performance of this contract is identified in Attachment 0009.

C.1.1.4.1 The contractor shall develop and implement an Inventory Control Plan (ICP) and process that accounts for GFP IAW Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7007. The contractor shall maintain a GFP list IAW FAR 52.245-1. The contractor shall utilize a Property Management System, approved by the Defense Contract Management Agency (DCMA) Property Administrator for the delivery and storage of GFP. The contractor shall provide property accountability reports IAW CDRL A005. Each piece of GFP shall be accounted for under a National Stock Number (NSN) NSN. If a NSN is not available, the contractor shall request and utilize a Management Control Number (MCN) from the Accountable Property Officer (APO) for GFE, special tools, and Test Equipment.

Report of Shipping Item and Packaging Discrepancy shall be provided to the Government by the contractor when GFP is received which does not agree with information on the shipping documents IAW CDRL A006.

C.1.1.4.2 The contractor shall request a determination of unserviceability and authorization from the PCO for the replacement or repair of GFP deemed unserviceable by the contractor and no longer usable for intended purposes during the execution of current efforts. Requests shall be made to the PCO as soon as a determination can be made. The contractor shall obtain written authorization from the PCO prior to shipping unserviceable assets to the repair location. The contractor shall notify the PCO and Contracting Officers Representative (COR) when shipped.

C.1.1.4.3 The contractor may transfer property across any approved DODAAC in the performance of this contract without additional COR approval. All transfers and movement shall be in accordance with an approved Government Property system.

C.1.1.4.4 RESERVED

C.1.1.4.5 RESERVED

C.1.1.4.6 RESERVED

C.1.1.4.7 External Agreements The contractor shall establish Non-Disclosure Agreements (NDAs) and Memorandums of Agreement (MOAs) with required Government and commercial organizations, as required, to receive GFP and GFI. The contractor’s failure to obtain the required external agreement may necessitate the Government to deviate from the delivery schedule of GFP, GFM, and GFI.

C.1.1.5 Design-to-Cost

C.1.1.5.1 Unit Manufacturing Cost (UMC) The contractor shall manage its NGCV-OMFV design to ensure that the vehicle’s production costs meets the Government’s UMC affordability target of $XX million per vehicle (expressed in base year 2018 constant dollars).

UMC is defined as the fully burdened costs of all material, labor, overheads, General and Administrative (G&A) expenses, fee/profit, and other direct and indirect expenses incurred by the contractor and all subcontractors necessary for the manufacture of a complete and useable vehicle. UMC includes fully burdened costs of subcontractors, purchased parts and equipment, costs to integrate and assemble subassemblies into the working system, costs to install special and general equipment when completed by the contractor or one of its subcontractor, and any costs to paint the system prior to shipment to its acceptance destination. UMC does not include the costs of any GFP provided to the contractor necessary for manufacturing and assembly of the vehicle nor does UMC include costs for any applique kits which are separately priced from the vehicle (e.g., armor kits) other than the costs incurred by the contractor or its subcontractors necessary to install the GFP or kits onto the vehicle prior to acceptance.

C.1.1.5.2 Affordability Assessment The contractor shall present and deliver its affordability management process and its UMC estimate IAW CDRLs A009, A010, and A011. The contractor shall base its UMC estimate on actual historical costs incurred. In addition to the requirements within CDRLS A009, A010, and A011 the contractor shall also include the following Affordability Assessment and UMC information within its presentations:

(a) An affordability assessment, which is a written description of the contractor’s manufacturing plan for the NGCV-OMFV in a full-rate production (FRP) environment which would meet the program's affordability target.

(b) A UMC estimate, which represents the contractor’s estimated average unit cost to manufacturing NGCV-OMFV in a full-rate production environment based on its proposed design solution. The UMC shall provide a breakdown of costs in the CSDR Work Breakdown Structure (WBS) and utilizing the standard DD Forms 1921 and 1921-1 formats. The DD 1921 and DD

1921-1 shall be prepared and delivered as if they were an annual submission during the FRP phase. No costs or quantities shall be listed under the "to-date" section of the deliverable (as no costs will have been incurred).

(c) A listing of any and all ground rules, assumptions, and facts utilized to perform the affordability assessment and UMC estimate.

(d) Special consideration shall be given to facts, ground rules, and assumptions related to learning and rate curves utilized to perform the assessment.

(e) The contractor shall provide sensitivity analysis against rate and learning curves to identify at what levels of rate and learning the NGCV-OMFV will become unaffordable.

(f) A description of risks that may impact the ability to meet the UMC target.

(g) A description of the data sources and methodologies utilized to estimate the UMC.

(h) The contractor shall identify cost reduction opportunities that would result in incremental overall UMC reductions of 5%, 10%, and 15%.

(i) The contractor shall perform a production rate analysis whereby the relationship between UMC and alternative production rates are defined, specifically assessing production durations from five to 15 years in length.

(j) The contractor shall recommend the optimal economic order quantity rate of production by year and identify facility and tooling costs required to achieve this rate.

C.1.1.6 Program Planning, Scheduling, and Cost Reporting

C.1.1.6.1 Integrated Master Plan (IMP) The contractor shall update, implement, and submit the IMP IAW CDRL A007. The IMP is an event-based plan consisting of a hierarchy of program events, with each event being supported by specific accomplishments, and each accomplishment associated with specific criteria to be satisfied for its completion. The IMP is part of the contract and all events, accomplishments, and criteria identified in the approved submittal will be contractually binding. Any changes to the IMP after it has been submitted as a CDRL will require written approval by the COR. Definitions of events, accomplishments, and criteria are based on the Department of Defense (DoD) "Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide" and MIL- STD-881D. The contractor shall include events, accomplishments, and criteria in its IMP, but may include additional lower levels if desired. The contractor shall identify each IMP event and accomplishment with a unique identification number and provide a textual description of all criteria. The contractor shall include the IMP events and accomplishments in the IMS on a word-for-word basis.

C.1.1.6.2 Integrated Master Schedule (IMS) The contractor shall develop, implement, and submit the IMS IAW Format 6 of CDRL A008.

C.1.1.6.3 Contract Work Breakdown Structure (CWBS) and CWBS Dictionary The contractor shall develop and maintain, and keep current throughout the life of the contract, a CWBS and CWBS Dictionary IAW CDRL A009. The contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government. The CWBS shall be product oriented. The contractor shall extend the CWBS down to the appropriate level required to provide adequate internal management, surveillance, and performance measurement. The contractor shall ensure all CWBS oriented reporting will be, at a minimum, in compliance with the lowest WBS level(s) identified by the Contract Cost and Software Data Reporting (CSDR) Plan, Attachment 0004.

C.1.1.6.4 Application to Subcontractors The contractor shall flow-down CSDR requirements to subcontractors meeting the applicable thresholds in DFARS 252.234-7001 and 252.234-7002). This responsibility includes requiring Subcontractors to electronically report directly to the Defense Cost and Resource Center (DCARC). The Contractor shall ensure that Subcontractors meeting CSDR reporting thresholds collect data in sufficient detail to meet the CSDR Plan, Attachment 0004. For Subcontractors not meeting CSDR reporting thresholds, the Contractor shall collect and deliver Subcontractor data to comply with the Resource Distribution Table requirements, CDRL A131 and Attachment 0004.

C.1.1.6.5 Program Budget and Cost Reporting

C.1.1.6.5.1 Contractor Cost and Software Data Reporting (CSDR) The contractor shall systematically collect and report actual contract costs in accordance with the following:

Report Title CDRL Cost and Software Data Reporting Dictionary A009 Cost Summary Data Report 1921 A010 Functional Cost-Hour Report 1921-1 A011 Progress Curve Report 1921-2 A012 Contractor Business Data Report 1921-3 A013 Software Resources Data Report (SRDR) Development A014 Software Resources Data Report (SRDR) Maintenance A015 Resource Distribution Table A131

The contractor’s reports shall be prepared IAW the referenced CDRLs and the Attachment 0004.

C.1.1.6.5.1.1 Cost Data Summary Report The Contractor shall prepare and submit the Cost Data Summary Report (DD Form 1921) IAW CDRL A010 which reports direct and indirect actual cost data on both a recurring and non-recurring basis by CWBS level as specified in CSDR plan, Attachment 0004.

C.1.1.6.5.1.2 Functional Cost-Hour Report The Contractor shall prepare and submit a Functional Cost-Hour Report (DD Form 1921-1) IAW CDRL A011 which reports information on resources including labor hours, overhead costs, material costs, and other direct and indirect cost data on both a recurring and non-recurring basis by CWBS level as specified in the approved CSDR plan, Attachment 0004.

C.1.1.6.5.1.3 Progress Curve Report The Contractor shall prepare and submit the Progress Curve Report (DD Form 1921-2) IAW CDRL A012 which reports production cost and hours data specified in the approved CSDR plan, Attachment 0004.

C.1.1.6.5.1.4 Contractor Business Data Report The Contractor shall prepare and submit the Contractor Business Data Report (DD Form 1921-

3) IAW CDRL A013 which provides the means to facilitate estimating and analysis of indirect contract costs as specified in the approved CSDR Plan, Attachment 0004.

C.1.1.6.5.1.5 Software Resources Data Report (SRDR) - Development The Contractor shall prepare and submit the Software Resource Data Report (SRDR) IAW CDRLs A014 and A015 which provides expectations and actual results of software development and upgrade efforts as specified in the approved CSDR Plan, Attachment 0004.

C.1.1.6.5.1.6 Lot Size Pricing Data The contractor shall collect Lot Size Pricing Data (LSPD) from subcontractors on all components which are classified either as a Major End Item (MEI) or Component of Interest (CoI), and deliver the LSPD to the Government IAW CDRL A132. A MEI is defined as: a component procured by the Contractor wherein the cost to the Prime Contractor before burden or profit/fee is greater than $100,000 per unit. A Component of Interest (CoI) is defined as: a component part for which the Government determines there is a significant technical, cost, or schedule risk implication. The list of the CoI will be identified by the Government within 30 days of acceptance of the Contractor’s Initial Design BOM, CDRL A016 and will be modified into the LSPD Workbook, Attachment 0075. For planning purposes, the Contractor shall assume approximately 15 components will be considered CoI. The purpose of the LSPD Report, CDRL A132 is to provide data on how changes in lot/production quantity may effect unit price (i.e., when higher quantities are ordered, how much does unit price change). The contractor shall use Attachment 0075 as the template for its LSPD Report submission, CDRL A132. The contractor shall deliver the LSPD Report in Microsoft (MS) Excel format, without encryption, locks, passwords, or other security protection features which would prevent the Government from editing, sorting, merging, or otherwise manipulating the data for Government purposes.

The contractor shall provide lot size pricing data for supplier components which are determined by the Government to be either a Major End-Item (MEI) or a Component of Interest (CoI). The intent of the LSPD CDRL requires that the prime contractor obtain (at a minimum) Rough Order Magnitude (ROM)-level pricing information from its suppliers based on the procurement buy quantities provided by the Government within the LSPD (Attachment 0075). The notional list of components that could be included in the LSPD Report CDRL A132 includes, but is not limited to, the following subsystems:

1. Hull weldment

2. Suspension system

3. Hydraulic system

4. Environmental control system

5. Hull armor

6. Automotive drive shafts/differentials

7. Dressed engine

8. Transmission

C.1.1.6.5.1.7 Resource Distribution Table The Contractor shall prepare and submit a Resource Distribution Table (RDT) IAW CDRL A131 which identifies the value of work assigned to the Contractor and any subsidiaries and subcontractors. The RDT shall be based on the WBS used in the CSDR Plan, Attachment 0004.

C.1.1.6.5.1.8 Cost and Software Data Reporting (CSDR) Readiness Reviews The Contractor shall host a Cost and Software Data Reporting (CSDR) Readiness Review with the Government within 30 days of the SOWM at the contractor’s facility where CSDRs are prepared. The purpose of the CSDR Readiness Review is to review the contract’s CSDR requirements and prepare for the Post Award CSDR Conference. The CSDR Readiness Review will review how the contractor’s accounting system can be utilized to satisfy the CSDR requirements found in DoD 5000.04-M-1, the CSDR Plan, Attachment 0004, and related Resource Distribution Table, CDRL A131. At the CSDR Readiness Review, the contractor shall demonstrate how it collects cost data in its accounting system and how, that data can be utilized to provide actual cost transactions and not cost allocations when preparing CSDR data deliverables; describe how recurring vs. nonrecurring costs are segregated; and demonstrate how the data from its accounting system will be mapped into the reporting categories in the CSDR Plan. The review should resolve any reporting issues and identify proposed changes to the CSDR Plan in order to tailor it to the contractor’s accounting system, to include recommendation of the final CWBS elements. The contractor and government shall also discuss the option of converting from the CSDR Plan currently on contract to the alternative “FlexFile” format of cost reporting.

C.1.1.6.5.1.9 Post-Award Cost and Software Data Reporting Review The contractor shall attend and participate in a post award CSDR conference which will be held with the Government Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoD 5000.04-M-1 (CSDR Manual). Prior to this conference, the Contractor shall make any adjustments or corrections identified during the Post-Award CSDR Review.

During this meeting, the CWIPT and contractor will review the Contractor's process for data collection and reporting in order to ensure it satisfies the guidelines contained in the DoD 5000.04-M-1, CSDR Manual, and the requirements in the approved CSDR Plan (Attachment 0004). In contractor format, the Contractor shall demonstrate how costs will be based, to the maximum extent possible, upon actual cost transactions and not cost allocations; describe how recurring vs. nonrecurring costs will be segregated; demonstrate how the data from its accounting system will be mapped into the reporting categories in the approved CSDR plan.

The contractor shall present the methodologies used for mapping internal cost accounts to the agreed upon WBS, specifically showing how individual WBS elements and functional element codes will be populated. Within 30 days of completing the SOWM, the Government will inform the Contractor of the exact date and location of the Cost and Software Data Reporting (CSDR) Readiness Review. This meeting is expected to take one (1) business day and will be held in the Metropolitan District of Columbia (DC) area. The contractor and government shall be prepared to discuss the option of converting from the CSDR Plan currently on contract to the alternative “FlexFile” format of cost reporting.

The contractor shall deliver a meeting agenda IAW CDRL A002, read-ahead package IAW CDRL A003, and meeting minutes IAW CDRL A003 in support of this meeting.

C.1.1.6.5.2 Bills of Material (BOMs)

C.1.1.6.5.2.1 Initial Design Bill of Material (BOM) The contractor shall provide an Initial Design BOM IAW CDRL A016 for its NGCV-OMFV design, which shall be current as of the date of contract award. The Initial Design BOM shall represent the planned manufacturing BOM and shall be based on or include a one-to-one crosswalk of every part number (P/N) to its applicable CSDR WBS element. The Initial Design BOM shall be a complete, indentured list of material, including all levels of assembly (regardless of component item type) required to build and assemble a complete vehicle. The Initial Design

BOM shall include an analysis that provides traceability and linkage to the data submitted in the Cost Data Summary Report, CDRL A010 and Functional Cost-Hour Report, CDRL A011.

C.1.1.6.5.2.2 Final Design BOM The contractor shall provide a Final Design BOM IAW CDRL A016 30 calendar days prior to MMR for its NGCV-OMFV design which shall identify any and all changes to its NGCV-OMFV design made during the life of this contract. The Final Design BOM shall represent the planned manufacturing BOM and shall be based on or include a one-to-one crosswalk of every P/N to its applicable CSDR WBS element. The Final Design BOM is a complete, indentured list of material, including all levels of assembly (regardless of component item type) required to build and assemble a complete vehicle. The Final Design BOM shall include an analysis that provides traceability and linkage to the data submitted in the Cost Data Summary Report, CDRL A010 and Functional Cost-Hour Report, CDRL A011.

C.1.1.7 Integrated Product Teams (IPTs) The contractor shall establish IPTs to serve as the primary contract management tool and key method of communication for this contract. The contractor shall allow access for Government personnel to participate in the IPTs. The Government will only be a participant in these meetings. The contractor maintains decision making authority. Government discussion shall not be construed as contractual guidance.

Contractor IPTs and IPT leaders shall be identified no later than the SOWM. Throughout the life of this contract, contractor IPT members shall propose new or modified IPTs when needed to focus efforts or improve effectiveness.

Each IPT shall be responsible for the following activities within the domain and scope of the IPT:

risk management, issue tracking and resolution, and technical performance measure reporting and management.

The contractor shall establish the following IPTs: Systems Engineering and Integration Team (SEIT); Product Assurance and Test (PA&T), Manufacturing, and Product Support Manager (PSM). The IPTs are further defined in subsequent sections.

C.1.1.7.1 Systems Engineering and Integration Team (SEIT) The SEIT provides a forum for discussing the program's technical planning and management to achieve user requirements, and acts as the technical authority in establishing the program's technical strategy. The SEIT will also act as the technical conflict resolution authority.

The contractor shall administer, support, and conduct SEIT meetings every other week to enhance communication between the contractor and the Government, as well as document decisions made that affect the technical baseline. The first SEIT shall be 30 days after SOWM.

The contractor shall establish a clear decision making processes to address and document decisions related to the development of the NGCV-OMFV and present it for comment at the first SEIT meeting. The contractor shall ensure that all tradeoffs and modifications are documented against the baseline, and presented through the SEIT prior to implementation. The contractor shall also review progress towards the next major program milestone or review.

At the SEIT meetings, the contractor shall review any changes that impact SWAP-C growth margin to integrate pre-planned product improvements (P3I), along with the contractor’s plan to meet any unmet thresholds (if applicable) within the Contractor’s Purchase Description, Attachment 0097. See Attachment 0094 for a list of P3I.

C.1.1.7.2 Product Assurance and Test (PA&T) IPT The contractor shall host and conduct PA&T IPT meetings bi-weekly with the Government to address quality assurance; test planning and conduct; Reliability and Maintainability (R&M) efforts; and quality engineering planning.

C.1.1.7.3 Manufacturing IPT The contractor shall host and conduct monthly Manufacturing IPT meetings with the Government, beginning one month after the DMR to address pre-production prototype build schedules and planning for the Manufacturing Maturity Review (MMR).

C.1.1.7.4 Product Support Manager (PSM) IPT The contractor shall establish a monthly PSM IPT to cover the 12 Product Support Elements as called out in Army Regulation (AR) 700-127. The PSM IPT shall incrementally monitor logistics data development and supportability design factors, thereby enabling the contractor to manage the Integrated Logistics Support (ILS) program in order to influence design and reduce the logistics footprint. The contractor shall provide the status of its expected system specification’s performance to the supportability performance requirements.

C.1.1.8 Program Protection The contractor shall develop and update mission 1) criticality analysis(es) to determine the most critical functions of the system, 2) vulnerability assessment(s) to recognize and identify vulnerabilities in the design, in any commercial off-the-shelf (COTS) products, and supply chains, 3) risk assessment(s), and 4) identify, select, and implement security countermeasures (risk mitigations) based on a cost-benefit trade-off analysis IAW DoD Guidance titled, “Trusted Systems and Networks (TSN) Analysis,” dated June 2014, https://www.acq.osd.mil/se/docs/trusted-systems-and-networks-tsn-analysis.pdf; “Software Assurance Countermeasures in Program Protection Planning,” dated March 2014, https://www.acq.osd.mil/se/docs/swa-cm-in-ppp.pdf; and DoDI 5200.39, “Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E),” dated May 28, 2015, https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520039p.pdf.

Program Protection shall be integrated to manage risks to technology and mission-critical system functionality from foreign collection, design vulnerability, supply chain exploitation, and battlefield loss throughout the acquisition lifecycle IAW DoDI 5200.44, “Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN),” dated November 5, 2012, https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520044p.pdf.

C.1.1.8.1 Program Protection Implementation Plan (PPIP) The contractor shall develop, implement, and maintain a PPIP IAW CDRL A017. The PPIP shall include the identification of Points of Contact (POCs) for each countermeasure in each contractor location. The contractor’s Supplier Quality Requirements for subcontractors shall be included in the PPIP. The information used to create this PPIP shall be available to the Government and discussed at SEIT meetings as well as design reviews. The contractor shall support the requirement of ensuring all personnel meet contract clearance and access https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520039p.pdf requirements by defining how they will integrate security into its overall systems engineering process.

The contractor’s PPIP shall address integration of all security disciplines, System Security Engineering (SSE), counterintelligence, Operations Security (OPSEC), inspections, and program protection surveys of the contractor’s acquisition program protection. The PPIP shall explain how acquisition program protection ensures coordination of systems, data, and products during the acquisition process with SSE efforts to build life-cycle security features into acquisition systems and products covered by this contract. Additionally, the PPIP shall demonstrate the visibility into supply chain and computer software assurance for critical components.

C.1.1.8.2 Program Protection Working Group (PPWG) The contractor shall host a PPWG within 30 calendar days after contract award concurrent with the SOWM. A second PPWG shall be held 30 calendar days prior to DMR with quarterly meetings thereafter throughout the period of performance of the contract. The agenda shall include Critical Functional Analysis (CFA), Critical Components (CC), Critical Program Information Assessments (CPIA), and Supply Chain Risk Management (SCRM). It is expected that each of the PPWGs will be a one day event.

C.1.1.8.2.1 Criticality Analysis

C.1.1.8.2.1.1 The contractor shall define each failure, IAW the MIL-STD-882E System Safety Program definitions of criticality to mission criticality, to the following criticality levels for assessment of mission-critical component functionality. The contractor shall conduct a Critical Functional Analysis (CFA) for the purpose of identifying Critical Components (CCs) that can lead to total mission failure (level 1) or significant and unacceptable mission degradation (level 2). This CFA shall be reviewed at each PPWG meeting to assess any changes since the last review. The CFA shall assess CC for the following war fighting functions: movement and maneuver, intelligence, fires, protection, sustainment, command and control, casualty evacuation and treatment. The CFA shall assess both Organic CC as well as the integration of Inherited CC. The CFA shall identify all logic bearing critical components as well as the hardware and computer software suppliers for the logic bearing components. The contractor shall host a review with the Government team to discuss and review the results of the CFA. The CCs shall be prioritized, assessed for supply chain risk, and based on risk. The contractor shall develop mitigations or countermeasures to minimize the risk posed from supply chain. The CFA, supply chain risk, and mitigation or countermeasures for risks shall be included in the meeting minutes IAW CDRL A004.

For each Level 1 and Level 2 Mission-Critical Function identified by the contractor in the criticality analysis(es), the contractor shall identify the critical components, or associated logic-bearing system components (e.g., hardware, firmware, and software) that implement, protect, or introduce vulnerability to that function. Logic-bearing components are the components used to implement mission critical functions in systems. A field programmable gate array (FPGA) is an example of a logic-bearing component.

C.1.1.8.2.1.2 The contractor shall ensure that updated assumptions, rationale, and results related to the criticality analyses, vulnerability assessments, risk assessments, supply chain risk information, and risk mitigations are provided for Government review at each Systems Engineering Technical Reviews (SETR).

C.1.1.8.2.1.3 The contractor shall support the CFA in identifying any Information and Communications Technology (ICT) as defined in DoDI 5200.44. The contractor shall identify the associated logic-bearing system components (e.g., hardware, firmware, and software) that implement, protect, or introduce vulnerability to that function (hereafter referred to collectively as the “critical components (CC).” The contractor shall identify the suppliers for the CCs. The CC shall be prioritized, assessed for supply chain risk, and based on risk the contractor shall develop mitigations or countermeasures to minimize the risk posed from supply chain. The CFA shall assess both Organic CC as well as the integration of Inherited CC IAW DoDI 5200.39, “Critical Program Information (CPI) Identification and Protection within Research, Development, Test, and Evaluation (RDT&E),” dated May 28, 2015. The contractor shall ensure that rationale and results related to the CFA, Critical Program Information Assessment (CPIA), and supply chain risk information and mitigation are made available for Government review at formal technical reviews.

C.1.1.8.2.2 Countermeasures The contractor shall plan for and implement countermeasures identified by the PPWG which mitigate foreign intelligence, technology exploitation, supply chain threats, battlefield threats, and system vulnerabilities that result in catastrophic (Level 1) and critical (Level 2) protection failures, including:

(a)The contractor shall apply Supply Chain Risk Management SCRM best practices in the development and production of the system. SCRM key practices are located in the DRAFT Notional Supply Chain Risk Management Practices for Federal Information Systems (National Institute of Standards and Technology (NIST) Interagency Report (IR) 7622) and the National Defense Industrial Association (NDIA) System Assurance Committee Guidebook (Engineering for System Assurance) which are both publicly available.

(b) The contractor shall enumerate potential suppliers of critical components, as they are identified, including cost, schedule, and performance.

(c) The contractor shall develop and document the processes IAW CDRL A017 to control access by foreign nationals to program information, system design information, DoD-unique technology, and computer software or hardware used to integrate commercial technology.

(d) The contractor shall implement processes and procedures to ensure that it uses genuine Information and Communications Technology (ICT) in the end product. The contractor shall levy these requirements for genuine ICT to its subcontractors.

(e) The contractor shall develop and implement a process used to protect unclassified DoD information in the development environment.

C.1.1.8.2.3 Component Control The contractor shall certify IAW CDRL A017 that the underlying computer software, firmware, and hardware, which in totality constitute the managed service, have been controlled, evaluated, and tested to ensure that the service delivers what it is designed to deliver. The contractor shall not provide functionality, additions, or enhancements to CCs unless explicitly requested and approved by the Government. The contractor shall not knowingly create the capability for unauthorized access to the system or knowingly introduce such capability into the Army network. All contractor-developed source code shall be provided for independent system assurance testing. The contractor shall test all CC code against the top 25 Common Weakness Enumerator (http://cwe.mitre.org).

C.1.1.8.3 RESERVED

C.1.1.8.4 Critical Technologies The contractor, in conjunction with the Government, shall analyze its system specifications against the Acquisition Security Database (ASDB), the Horizontal Protection Guide (HPG) also hosted on the ASDB homepage, and the Low Observable, Counter Low Observable (LO/CLO) provisions in DODI S-5230.28 which can be accessed via the SIPR IntelDocs and/or Intellipedia portals to identify technologies as Critical Program Information (CPI) or Critical Technologies (CT). See Attachments 0091, 0092, and 0093 for information on how to access the ASDB.

Should the assessment result in identification of CPI or CT, the contractor, in…