Draft Section C - SOW(3).docx

TABLE OF CONTENTS.

C.1 GENERAL

C.1.1 SYSTEM REQUIREMENT

C.1.2 DATA

C.1.3 MEETINGS/AUDITS/ASSESSMENTS/REVIEWS

C.1.4 BUSINESS MANAGEMENT

C.1.5 PROGRAM PROTECTION

C.1.6 INFORMATION SECURITY AND SECURITY REQUIREMENTS

C.1.7 GOVERNMENT FURNISHED EQUIPMENT (GFE) AND INTEGRATION AND GOVERNMENT FURNISHED INFORMATION (GFI).

C.2 PRODUCTION

C.2.1 SYSTEMS ENGINEERING

C.2.2 RELIABILITY, AVAILABILITY, AND MAINTAINABILITY (RAM) PROGRAM

C.2.3 INTEGRATED PRODUCT SUPPORT (IPS)

C.2.4 VERIFICATION AND VALIDATION ACTIVITIES

C.2.5 TEST DEFICIENCIES AND FAILURES

C.2.6 TECHNICAL DATA PACKAGE PURCHASE OPTION

C.2.7 TIRE AGE REQUIREMENTS

C.2.8 MAKE OR BUY

C.3 SYSTEM TECHNICAL SUPPORT

C.3.1 GENERAL

C.3.2 SYSTEM ENGINEERING AND TECHNICAL EFFORT DESCRIPTION

C.3.3 GENERAL FIELD SERVICE REPRESENTATIVE

C.4 TOTAL PACKAGE FIELDING

C.4.1 GENERAL

C.4.2 CONTRACTOR PROVISIONS

C.4.3 MEETINGS

C.4.4 REPORTING

C.4.5 GOVERNMENT FURNISHED ITEMS

C.4.6 CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES

C.4.7 MATERIAL AND EQUIPMENT

C.4.8 TPF TASKS

C.4.9 NEW EQUIPMENT TRAINING

C.5 DESIGN FOR MANUFACTURABILITY REQUIREMENTS

C.6 SUPPLIER AGREEMENTS

C.7 INCORPORATION OF CHANGES TO THE JLTV DESIGN PROPOSED DURING THE SOURCE SELECTION

C.7.1 NEXT GENERATION VEHICLE ARCHITECTURE

C.8 FREE ON BOARD (FOB) ORIGIN SHIPPING

C.8.1 OTHER GOVERNMENT EQUIPMENT SHIPMENT (KITS, ASL, SAIP, SPECIAL TOOLS, GFE, ETC.)

C.8.2 SHIPPING REPORT/S

C.8.3 SHIPPING MEETING/S

C.8.4 SHIPPING INSTRUCTIONS

C.8.5 COMMERCIAL SHIPPING

C.1 GENERAL

This Statement of Work (SOW) encompasses the Production and Deployment phase requirements of the Joint Light Tactical Vehicle (JLTV) Family of Vehicles (FoV) program for the period of performance.

This SOW consists of the supplies and services required for production (including vehicles, trailers, kits, test assets, refurbishment of test assets, Authorized Stockage List (ASL) and Spares Acquisition Integrated with Production (SAIP)), Program Support (including Program Management, Configuration Management, Integrated Product Support (IPS), and Test Support), System Technical Support (STS), Field Service Representative Support, Total Package Fielding (TPF), Storage and Maintenance of hardware procured, and an option to procure a Technical Data Package (TDP) and Computer Software Package (CSP) specific to the technology enhancements for JLTV FoV.

The contractor, as an independent contractor and not as an agent or employee of the US Government, shall furnish all data, supporting labor, supplies, services, facilities and equipment as required under this contract.

The term “day” referenced throughout means a calendar day, unless otherwise specified.

C.1.1 SYSTEM REQUIREMENT

The contractor shall produce the JLTV FoV in conformance with the JLTV FoV TDP and CSP (Attachment 0112). The contractor shall build the vehicles, trailers, and kits as described on the drawings in the JLTV FoV TDP and CSP and the technology enhancements documented in Attachment 0169 - Proposed Source Control Drawing and Tech Enhancement Changes.

C.1.1.1 ORDER OF PRECEDENCE FOR TECHNICAL REQUIREMENTS

In the event of a conflict between the JLTV FoV TDP and CSP, the Purchase Description (PD), or any other Attachments or Exhibits related to the JLTV FoV TDP and CSP or PD, the order of precedence for documents in this contract that fall within paragraph (d) of the standard FAR 52.215-8, Order of Precedence clause is as follows:

In the event of no conflict, all requirements shall apply as written.

C.1.1.2 JLTV FOV DEFINITION

The term "JLTV FoV" is defined as including two variants (a four-seat and a two-seat variant), a companion trailer (JLTV-T) and chassis, and associated kits. The four-seat variant has two base vehicle platforms: the General Purpose (GP) platform (which includes the Heavy Guns Carrier (HGC) mission package) and the Close Combat Weapons Carrier (CCWC) platform. The two-seat variant has one base vehicle platform: the Utility (UTL).

C.1.1.2.1 TRAILER CONFIGURATION:

- M1289 JLTV Trailer (JLTV-T)

- JLTV Trailer Chassis (JLTV-TC)

C.1.1.2.2 MISSION PACKAGE

Each base vehicle platform will be configured as a Mission Package Configuration through the installation of Mission Packages as defined in Annex K of Attachment 0101 - JLTV Purchase Description (JLTV PD).

C.1.1.2.3 JLTV MISSION PACKAGE CONFIGURATIONS:

- M1280 A0/A1/A2 General Purpose (JLTV- GP)

- M1278 A0/A1/A2 Heavy Guns Carrier (JLTV-HGC)

- M1281 A0/A1/A2 Close Combat Weapons Carrier (JLTV-CCWC)

- M1279 A0/A1/A2 Utility (JLTV-UTL)

C.1.1.2.4 JLTV ASSOCIATED KITS CONFIGURATIONS:

The contract includes requirements for the Government to procure Contractor Furnished Equipment kits for integration into the vehicles. The contractor shall install kits into the vehicles prior to vehicle delivery and acceptance by the Government in accordance with (IAW) Attachment 0110 - JLTV Vehicle Kit Matrix and Attachment 0112 - JLTV FoV TDP and CSP. The contractor shall package and prepare for shipment the packaged kits procured by the government and deliver the kits to the Government IAW the Attachment 0110 - JLTV Vehicle Kit Matrix and Attachment 0112 - JLTV FoV TDP and CSP.

C.1.1.2.5 GROSS VEHICLE WEIGHT RATING (GVWR):

For the purposes of interpreting requirements in this contract, GVWR for the M1278, M1279, M1280, and M1281 is defined as 24,000 lbs. The vehicle data plates in the JLTV TDP and CSP may specify a lower value to provide for future growth, but the vehicles are designed to a GVWR of 24,000 lbs. Changes to the GVWR shall be managed through the ECP process.

C.1.2 DATA

C.1.2.1 INTERNET-BASED COLLABORATION

The JLTV Integrated Data Environment (IDE) consists of internet-based collaboration tools (defined below) that shall be used to facilitate information sharing and collaboration within a secure Government server environment that provides controlled, distributed access to JLTV program information, both released and in-work. The contractor shall process and maintain the following types of documents within the IDE consistent with the JLTV Security Classification Guide (reference Attachment 0102, Security Classification Guide (DD254)): JLTV program documents; reports, program management data; meeting-related information; modeling and simulation analysis data; pertinent manufacturing information; and Government and contractor test data. Any posting to the IDE is considered a data deliverable in the context of DFARS Data Rights clauses including, but not limited to, 252.227-7013 Rights in Technical Data – Noncommercial and 252.227-7014 Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation and 252.227-7015 Technical Data–Commercial Items. The IDE shall be used only for sharing unclassified or Controlled Unclassified Information (CUI) information. When submitting classified information, follow the National Industrial Security Program Operating Manual (NISPOM) Chapter 5 instructions and Department of Defense (DD) Form 254 (reference Attachment 0102, Security Classification Guide (DD254)) using the below mailing address:

SFAE-CSS-JL

6501 E. 11 Mile Rd, MS 640 Attn: JLTV Security Officer Detroit Arsenal, MI 48397-5000

Unless otherwise directed, the contractor shall notify the Government personnel (Procuring Contracting Officer (PCO) or Contracting Officer Representative (COR)), via e-mail when new or updated documents are posted to a collaboration environment. The notification email shall include a hyperlink to the location of the posted content. Correspondence to the PCO or organizations outside Joint Program Office Joint Light Tactical Vehicle (JPO JLTV) shall not be submitted via an internet-based collaboration tool without prior authorization.

IDE collaboration tools: The contractor shall use the JLTV SharePoint server to facilitate unclassified, secure internet-based information sharing between JLTV program participants. SharePoint will also serve as the primary means of submitting unclassified, CUI Contract Data Requirements List (CDRL) items, unless otherwise stated within a specific CDRL item. The contractor shall conduct contractor-Government internet conferencing (web meetings) using Government approved systems. The contractor shall use the Versatile Information Systems Integrated On-Line Nationwide (VISION) Digital Library System (VDLS) to access unclassified data from Government testing. The Government will provide details on specific IDE tools, requirements for access, and approach for use at the Contract Start of Work Meeting (SOWM).

The Government will sponsor Army Knowledge Online (AKO), SharePoint, Defense Collaboration Services (DCS), VDLS, and other required accounts for contractor use. Details will be provided at the Contract SOWM. The Government can only sponsor accounts for United States (U.S.) Citizens. The contractor shall provide names, contact information, and level of access (upload or download) for personnel requiring access to these tools no later than (NLT) Contract SOWM, for all systems except VDLS. The list of contractor personnel requiring VDLS access shall be provided to the Government 60 days prior to the Test Readiness Review (TRR). In order to access these systems, the contractor shall have or obtain External Certification Authority (ECA) Certificates, Federated Bridge Certificates, and/or DoD Common Access Cards (CAC) for appropriate personnel. For details on CACs, reference SOW section C.1.2.2. Details on the ECA program and authorized ECA vendors can be found at: https://public.cyber.mil/eca/ and details on the Federated bridge program can be found at: https://public.cyber.mil/pki-pke/interoperability/ . Request for access to any other Government systems shall go through the PCO.

C.1.2.2 CAC AUTOMATED CONTRACTOR VERIFICATION SYSTEM

C.1.2.2.1 CAC APPLICATIONS

The contractor shall appoint an Information Assurance Officer to process CAC applications for its employees and subcontractor employees in accordance with FAR 52.204-9, Personal Identity Verification of Contractor Personnel, DoD Directive 8190.3 Smart Card Technology and DoD Instruction 8520.2 Public Key Infrastructure and Public Key Encrypt.

C.1.2.2.2 REQUESTS FOR CAC

The contractor shall submit requests for CAC when required, via email to the COR.

C.1.2.2.3 CONTRACTOR VERIFICATION SYSTEM

The Government will establish a Contractor Verification System (CVS) application account for each CAC request and provide each contractor and subcontractor employee a User I.D. and Password via email.

C.1.2.2.4 CVS ACCESS

The contractor’s and subcontractors’ employees shall access the CVS account and complete the CAC application.

C.1.2.2.5 CAC REQUEST STATUS

The Government will inform the contractor’s and subcontractors’ employee via email the status of the CAC request. The status will be one of the following: (1) Approved; contractor shall proceed to nearest Real-Time Automated Personnel Identification System (RAPIDS) Defense Enrollment and Eligibility Reporting System (DEERS) location to obtain CAC. (2) Returned; additional information or correction to application required by contractor employee. (3) Rejected; Government in separate correspondence will provide reason(s) for rejection.

C.1.2.2.6 APPROVED AND REJECTED APPLICATIONS

The contractor shall maintain records of all approved and rejected CAC applications.

C.1.2.2.7 CAC PERIOD OF PERFORMANCE

Issued CACs may be for a period of performance not longer than three (3) years or the contract performance completion date (inclusive of all options), whichever is earlier. If a requirement for a CAC exists beyond three years, the contractor shall submit a new request.

C.1.2.2.8 CAC RETURN

The contractor shall return issued CACs to the DEERS office IAW FAR 52.204-9, Personal Identity Verification of Contractor Personnel. The contactor shall notify the Government of all CACs returned to the DEERS Office.

C.1.2.3 DATA DELIVERABLES

The contractor shall deliver to the Government all information, technical data and software required under this SOW as identified by Orders issued by the Government. Unless otherwise specifically provided, the contractor shall deliver, mark, and grant rights in all such Technical data and software deliverables IAW DFARS 252.227-7013, Rights in Technical Data—Noncommercial Items; 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation; 252.227-7015, Technical data –Commercial Items; and 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions.

All CDRLs requiring data related to Mission Package Configurations shall specifically address any unique differences in the Mission Package Configurations. One CDRL submission may address all Mission Package Configurations.

The contractor shall deliver all data in the English language.

All electronic data submitted shall be in an editable Microsoft (MS) Office Suite and Windows compatible format unless specified otherwise in the CDRL.

The contractor shall annotate the following information in the electronic cover letter for the submission:

(a) Contract Number

(b) CDRL, Revision Number, and Item (A001-002 TRANS RPT)

(c) Delivery Type (Draft, Initial, Subsequent, or Final)

(d) Due Date

(e) Submittal Date

(f) Contractor Name

The contractor shall include a revision record that identifies the corresponding revision annotation, the due date, and the description of the change For example: A001-002 is the second submission of CDRL A001.

All electronic data shall be submitted via SharePoint, unless specified differently in the CDRL (see Internet-Based Collaboration section for details).

The contractor shall use the following naming convention for electronic files submitted:

(a) CDRL Number

(b) Revision Number

(c) Delivery Type (Draft, Initial, Subsequent, or Final)

(d) Due Date

(e) For example: A001-001_Draft_01Aug2012.doc

The PCO or assigned COR is the approving authority for all CDRLs delivered under this contract.

The contractor shall be prepared to brief and display information used to create each CDRL at Integrated Product Team (IPT) meetings, Program Management Reviews (PMR), as well as major reviews.

C.1.2.4 INTEGRATED MASTER SCHEDULE (IMS)

The contractor shall develop, maintain, and deliver an IMS that tracks and reports all activities and tasks leading up to the start of production and critical production activities after, including but not limited to production facility construction, development, and validation activities, supplier and contractor production launch activities and part approval (Production Part Approval Process (PPAP))(to include successful completion of all Component First Article Test (CFAT) requirements), contractor production process validation activities, the implementation of the contractor’s proposed production process as defined in E.38 and Attachment 0171 – Proposed JLTV Production Process, and all activities related to the Manufacturing Readiness Assessment (MRA) review (reference C.1.3.6). The IMS shall be directly traceable to the contractor’s Integrated Master Plan (IMP) and be consistent with the Contract Work Breakdown Structure (CWBS) and time-phasing of the Performance Measurement Baseline (reference C.3.1.5.1). The IMS shall be compatible with Microsoft Project v2016 or later version and contain logically networked, detailed program activities encompassing contract milestones, events, decision points, critical subcontract tasks or hand-offs, external dependencies, vehicle production, Government Furnished Equipment (GFE), Government Furnished Information (GFI), exit criteria, discrete tasks and activities (as described in DI-MGMT-81861B within CDRL A001, IMS), and planning packages to budget for early baseline planning. Progress on this IMS shall be reported in the PM-IPT and PMR meetings.

The Contractor shall also develop, maintain, and deliver an IMS that tracks and reports for the System Technical Support (STS) scope of this contract. The IMS shall be directly traceable to the contractor’s IMP and be consistent with the CWBS and time-phasing of the Performance Measurement Baseline (reference C.3.1.5.1). The IMS shall be compatible with Microsoft Project v2016 or later version and contain logically networked, detailed program activities encompassing contract milestones, events, decision points, critical subcontract tasks or hand-offs, external dependencies, vehicle production, GFE, GFI, exit criteria, discrete tasks and activities (as described in DI-MGMT-81861B within CDRL A001, IMS), and planning packages to budget for early baseline planning.

The IMS shall also incorporate all data for subcontractors (as described in DI-MGMT-81861B within CDRL A001, IMS) in the prime IMS for components that equal or exceed 10 percent of the value of the individual STS Work Directive(s). The IMS shall clearly identify critical path activities and reflect risk mitigation tasks. (CDRL A001, IMS)

C.1.3 MEETINGS, AUDITS, ASSESSMENTS AND REVIEWS

C.1.3.1 PARTICIPATION AND ADMINISTRATION

Unless otherwise specified in the paragraphs below, all meetings, audits, assessments, and reviews shall be hosted by the contractor. The contractor's hosting duties and responsibilities shall consist of all functions related to the preparation and execution of the meetings, audits, assessments, and reviews to include providing facility, sending invitations, media resources, security, minutes, and materials.

C.1.3.1.1 AGENDA AND READ-AHEAD PACKAGES

The contractor shall submit an agenda and read-ahead package for all meetings, audits, assessments, and reviews in section C.1.3 IAW CDRL A002, Agenda and Read-Ahead Package.

C.1.3.1.2 MINUTES

The contractor shall record and provide minutes for all meetings, audits, assessments, and reviews in section C.1.3 and otherwise called out in this contract. The contractor's recorder shall be identified at the beginning of each event. (CDRL A003, Minutes)

C.1.3.1.3 INVITATIONS

Government participants will be identified by JPO JLTV. The contractor shall send invitations for all meetings, audits, assessments, and reviews in section C.1.3 and otherwise called out in this contract not less than seven (7) days prior to the event. Invitations are not required for daily and weekly meetings.

C.1.3.2 START OF WORK MEETING

The contractor shall conduct a Contract Start of Work Meeting (SOWM), at the contractor's facility within 30 days after Contract Award. This meeting will introduce and align the Government and contractor teams. The Contract SOWM shall consist of a SOW review. For planning purposes, this meeting is anticipated to be an up to five (5) consecutive day event.

The contractor shall review all contract requirements, the detailed contract schedule, the contractor’s production processes (fabrication, final assembly, finishing (paint), test, inspection, presentations for acceptance, and shipping, at a minimum) shall be presented. The contractor’s plan to design, build, and validate its production and supply chain processes (to include tooling, facilities, personnel, and any other factor impacting the ability to produce the deliverables per the delivery schedule) shall be presented. The contractor shall also present their organizational Key Roles at the Contractor SOWM and shall discuss the plan for communicating and transitioning personnel changes.

C.1.3.3 PROGRAM MANAGEMENT LEVEL IPT MEETINGS

The contractor shall conduct, at a minimum, monthly Program Management (PM) Level IPT Meetings. The PM Level IPT Meetings shall commence one month following the Contract SOWM. The monthly PM Level IPT meetings shall not be conducted on the months when a Program Management Review (PMR) is held. The meetings shall include contractor program management personnel and working level IPT personnel to address cost, schedule, performance, risk status, and the contractor shall be prepared for detailed discussion with the Government. Technical issues shall be presented in terms of performance requirements, design, production status and issues, exit criteria, schedule progress, risk and mitigation, and cost impact. Prior to the Manufacturing Readiness Assessment, the contractor shall brief all status, schedule, and issues pertaining to its production process. For planning purposes, these meetings are anticipated to be at a minimum a one (1) day event.

C.1.3.4 PROGRAM MANAGEMENT REVIEW

The contractor shall conduct quarterly PMRs, beginning with the first quarter after contract award. The PMRs shall include contractor senior-level program management personnel. The contractor shall present, at each PMR, cost, schedule, performance, and risk status and address the following in a mutually agreed upon format:

(a) Program Overview and Status

(b) Business Management and Contract Review

(c) System Engineering

(d) Configuration Management (CM)

(e) Supportability & Logistics Review including IPS and TPF.

(f) System Technical Support (STS)

(g) Schedule Reviews

(h) Test Verification and Validation Activities

(i) Foreign Military Sales

The contractor shall be prepared for a detailed discussion with the Government. Issues shall be presented in terms of performance goals, exit criteria, schedule progress, risks and mitigation, and cost impact. For planning purposes, these meetings are anticipated to be a two (2) day event.

C.1.3.5 SYSTEMS ENGINEERING (SE) REVIEWS

C.1.3.5.1 SYSTEMS ENGINEERING INTEGRATED PRODUCT TEAMS

The contractor shall conduct annual SE IPTs. The first meeting shall be held following the Final Design Review per C.1.3.5.2. The SE IPT shall include all functional and vehicle element engineering. The contractor shall present the following:

(a) Process and Plan status

(b) Configuration Control Board (CCB) status

(c) Manufacturing status

(d) System Technical Support (STS) status

(e) Software status

(f) Cybersecurity status

(g) System safety status

(h) Human Systems Integration status

(i) Technical Risk status

The contractor shall be prepared for a detailed discussion with the Government. Issues shall be presented in terms of performance goals, exit criteria, schedule progress, risks and mitigation, and cost impact. For planning purposes, these meetings are anticipated to be a one (1) day event.

C.1.3.5.2 DESIGN REVIEWS

The contractor shall conduct an Initial Design Review (IDR) as part of the Contractor SOWM. The purpose of this review is to enable the Government to assess the Contractor’s strategy for the design and testing of planned Engineering Change Proposals (ECPs) to the JLTV TDP and CSP for Technology Enhancements and Source Control Content as defined in Attachment 0169 - Proposed Source Control Drawing and Tech Enhancement Changes. The Contractor shall also present an overview of design, performance goals, exit criteria, planned schedule and, risks with mitigation. For all requirements defined in Attachment 0101 - JLTV PD, where compliance is assessed as medium or high risk by the Government or contractor due to integration of technology enhancements or changes to source control content, the contractor shall identify those impacts and present a plan to remedy the performance gap. The contractor shall also demonstrate how it has achieved compliance to the design for manufacturability requirements identified within Section C.5. Detailed entrance and exit criteria is defined in Attachment 0137 - Design Review Checklist. This meeting serves as the decision point for the Government to authorize the initiation of contractor changes that will be subsequently approved using the Engineering Change Proposal (ECP) process. For planning purposes, this meeting is anticipated to be a two (2) day event.

The contractor shall host a Final Design Review (FDR) 75 calendar days after contract award. The purpose of the design review is to formalize any changes made to the product baseline, assess design maturity, and evaluate risks. The contractor shall present all design changes incorporated in the product baseline, a detailed description of how the production vehicle meets the requirements in Attachment 0101 - JLTV PD, and a draft ECP for each change. Detailed entrance and exit criteria is defined in Attachment 0137 - Design Review Checklist. This meeting serves as the decision point for the Government to allow the contractor to begin production of the JLTV upon approval of the FDR. For planning purposes the FDR is anticipated to be up to a two-day event.

C.1.3.5.3 ISSUE TRACKING AND REPORTING

The contractor shall utilize the TEAMS CAPA module as the single authoritative programmatic issue tracker and management tool. The contractor shall immediately enter, manage, track, and remedy (with corrective actions and root cause) all JLTV FoV issues (at a minimum including component, sub-system, system, vehicle/trailer, CFE, GFE, hardware, software, kits, JLTV FoV TDP and CSP, cyber, human factors, repair, and sustainment) to include: failures and/or anomalies discovered during design, development, testing (including contractor, supplier, and Government), production (contractor and supplier), fielding (supported by PQDR), and sustainment. The contractor shall present the status of all existing and new entries at each IPT and program management meeting or as requested. The Government may directly enter new issues into TEAMS CAPA module and the contractor shall also manage and remedy these issues.

C.1.3.6 MANUFACTURING READINESS ASSESSMENT REVIEW

The contractor shall conduct a Manufacturing Readiness Assessment (MRA) review at the contractor manufacturing facility 30 days prior to the start of production at each manufacturing facility. At the MRA review the Government will review, at a minimum, the implementation of the proposed production process (Attachment 0171 – Proposed JLTV Production Process), the contractor’s work instructions, Design Failure Modes and Effects Analyses (DFMEAs), Process Failure Modes and Effects Analyses (PFMEAs), process maturity/capabilities (especially as they relate to special characteristics), tooling maturity/capability/calibration, error proofing, traceability, Control Plans, and in process inspection and testing for alignment to the JLTV FoV TDP and CSP and contract requirements. The contractor shall correct all issues identified by the Government during this review, and shall also provide all materials, facilities, information, and tools necessary to accommodate this review.

In the event the contractor does not fully implement its proposed production process prior to the start of production in accordance with E.38 and Attachment 0171, an additional MRA in accordance with the requirements specified above will be required to validate that the process has been fully implemented as proposed. The contractor shall identify any deltas between the production process in place at the time of the first MRA and the proposed production process in Attachment 0171, as well as the detailed schedule for closure of all of the deltas identified per the requirements of E.38. The contractor shall notify the Government when it has fully implemented its proposed production process and is ready for the subsequent MRA to occur.

C.1.3.7 LOGISTICS REVIEWS

The Contractor shall host weekly a Logistic Leadership IPT to discuss all Integrated Product Support (IPS) related work efforts. The Contractor shall brief and display portions of work accomplished to date for initial meeting and work accomplished since last IPT, answer questions about Contractor work processes, present records of quality assurance reviews, and respond to Government comments regarding publications processes or work samples. The Contractor shall also present metrics to the Government for development of logistics products that include the Technical Publication work packages, provisioning data, training data, and packaging data with supporting data.

C.1.3.7.1 LOGISTICS START OF WORK MEETINGS

The contractor shall host a Logistics Start of Work Meeting for IPS to include Technical Manual Validation, Technical Publications and Provisioning Guidance, Provisioning Conferences and Technical Manual Verification. The purpose of the Technical Publications and Provisioning Guidance is to review publications contract objectives, establish lines of communications, and address contractor's questions. The Logistics Start of Work Meeting shall occur NLT 90 days after contract award. The Logistics Start of Work Meeting shall introduce and align the Government and contractor Logistics teams, and consist of a SOW review and schedule review. For planning purposes, this meeting is anticipated to be a three (3) day event.

C.1.3.7.2 PSM IN-PROCESS REVIEWS

The Contractor shall host monthly Product Support Manager (PSM) Reviews to discuss all IPS related work efforts. The Contractor shall brief and display portions of work accomplished to date for initial meeting and work accomplished since last PSM review, answer questions about Contractor work processes, present records of quality assurance reviews, and respond to Government comments regarding publications processes or work samples. The Contractor shall also present metrics to the Government for development of logistics products that include the Technical Publication work packages, provisioning data, training data, and packaging data in graph form with supporting data. For planning purposes, this meeting is anticipated to be a one (1) day event each month.

C.1.3.7.3 PROVISIONING CONFERENCE AND LOGISTICS SUPPORT ANALYSIS RECORDS REVIEW

The contractor shall host the first Provisioning Conference and Logistics Support Analysis Records (LSAR) Review 90 calendar days after the Provisioning Guidance Conference to verify the Logistics Support Analysis (LSA) 036 report (CDRL C004, Logistics Product Data), Engineering Data for Provisioning (EDFP), Repair Parts and Special Tools List (RPSTL) and part screening data, and any other contactor related data used to support the LSAR. The contractor shall host subsequent Provisioning Conferences and LSAR Reviews once per quarter, or on dates mutually agreed to by the parties. The contractor shall conduct a quarterly reconciliation of the Provisioning Master Record & Logistics Product Data (LPD) database and update the provisioning records (reference C.2.3). For planning purposes the initial provisioning conference is anticipated to last four (4) weeks. Subsequent provisioning conferences are anticipated to a one (1) week event each quarter.

C.1.3.8 QUALITY REVIEWS

C.1.3.8.1 PRODUCTION AND PRODUCT QUALITY MANAGEMENT INTEGRATED PRODUCT TEAM MEETINGS The contractor shall conduct monthly Production and Product Quality Management Integrated Product Team (PQM-IPT) meetings to coordinate overall Quality Planning and execution with the Government. The contractor and Government shall establish the date, time, and duration of the PQM-IPT meetings at the Contract SOWM.

The contractor shall develop all agendas (Reference CDRL A002, Agenda) and meeting minutes (Reference CDRL A003, Minutes).

C.1.3.8.2 JLTV QUALITY MANAGEMENT REVIEW MEETINGS

The contractor shall conduct quarterly JLTV Quality Management Review (QMR) meetings at the contractor's facility. The contractor shall coordinate the meeting agenda issues, topics and schedules with the Government. The contractor shall prepare and deliver minutes of the Quality Council meetings (reference CDRL A003, Minutes). The minutes shall contain, at a minimum: schedules; detailed results and proceedings of discussions, assessments, and guidance; action items; an attendee’s roster; and all presentations. Action items shall be assigned prior to the close of the meeting. Detailed meeting requirements are found in Attachment 0140 – JPO JLTV Quality Management Review.

C.1.3.8.3 CORRECTIVE ACTION REVIEW TEAM MEETINGS

The contractor shall attend weekly Corrective Action Review Team (CART) meetings that shall commence with the start of Government testing (reference C.2.4.2). The CART is the Government group responsible for reviewing the contractor's Failure Analysis Corrective Action Reports (FACARs) (reference CDRL D001, FACAR), including root cause analysis and proposed fixes. The CART may provide feedback to the contractor regarding its root cause analysis methodology. The JPO JLTV will chair the CART meetings. The CART meetings will be weekly, one day events. The contractor shall develop and implement preventive measures to reduce identified nonconformance performance, and the contractor shall establish corrective protocols to mitigate risks and prevent recurrence.

The Government will provide official notification of planned meeting times to the contractor for all CART Meetings at the inception of each test. The contractor shall identify a corrective action team membership to attend CART meetings. The contractor’s team shall include members to correlate to the Government CART members, and include functions relevant to CART including, but not limited to: Quality; Reliability, Availability, and Maintainability (RAM); Test; Logistics; Maintenance; Systems Engineering; Safety; Transportability; and Manpower and Personnel Integration (MANPRINT) Human Factors. CART meeting agendas shall be established by the contractor and approved by the Government. Meeting agendas shall include a list of all Test Incident Reports (TIRs) numbers to be discussed by category.

C.1.3.9 TEST REVIEWS

C.1.3.9.1 CONTRACTOR CONDUCTED PRE-TEST READINESS REVIEW

The contractor shall conduct a Pre-Test Readiness Review (Pre-TRR) to present to the Government the readiness of the vehicles to enter into Government system level testing. The Pre-TRR shall be held at or near the contractor build site, at least seven days prior to the Government TRR. The Pre-TRR shall address the content detailed in the Pre-TRR Checklist (Attachment 0153 - Pre-TRR Checklist). For planning purposes, this meeting is anticipated to be a two (2) day event.

C.1.3.9.2 GOVERNMENT CONDUCTED TEST READINESS REVIEW

The contractor shall attend the Government TRR, conducted at or in the vicinity of Aberdeen Proving Ground (APG), and be prepared to present the information prepared for the Pre-TRR. The Government TRR is anticipated to be held no more than seven (7) days prior to the first vehicle delivery and will assess both the contractor's and the Government's test readiness. For planning purposes, this meeting is anticipated to be a one (1) day event.

C.1.3.9.3 RELIABILITY, AVAILABILITY, AND MAINTAINABILITY (RAM) SCORING CONFERENCES The contractor shall attend and participate in the Government RAM Scoring Conference meetings by presenting information, evidence, or opinions that the Government will consider when scoring test incidents. The Government will provide contractor notification of the Scoring Conference at least 21 business days prior to the event. Each Scoring Conference is anticipated to be two days in duration. The contractor shall develop and deliver a RAM Scoring Conference Package (CDRL D002, RAM Scoring Conference Package). This information shall be reviewed with the Government 14 days prior to each Scoring Conference.

C.1.3.9.4 RAM ASSESSMENT CONFERENCES

The contractor shall attend and participate in a Government RAM Assessment Conference, which will occur during Government testing. The contractor’s participation shall consist of presenting information detailed in CDRL D003, RAM Assessment Conference Package. The Government will provide contractor notification of the Assessment Conference at least 14 business days prior to the event. For planning purposes, it is expected that one Assessment Conference will be held, for a duration of two days. Prior to the Assessment Conference, the contractor shall prepare and deliver an Assessment Conference Package (CDRL D003, RAM Assessment Conference Package).

C.1.3.10 BUSINESS MANAGEMENT REVIEWS

C.1.3.10.1 POST AWARD COST AND SOFTWARE DATA REPORTING CONFERENCE

The contractor shall host a Post-Award Cost and Software Data Reporting (CSDR) Conference with the Government’s Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoD 5000.04-M-1 (CSDR Manual). The contractor shall host the Post-Award CSDR Conference at the contractor’s facility where CSDRs are prepared. The purpose of the Post-Award CSDR Conference is to review the contract’s CSDR requirements and assess how the contractor’s accounting system satisfies the CSDR requirements found in DoD 5000.04-M-1, “CSDR Manual” and Attachment 0108 - CSDR Plan. In a briefing presented by the contractor in its own format, the contractor shall:

(a) Demonstrate how it collects cost data in its accounting system and how that data will be utilized to provide actual cost transactions and minimize cost allocations when preparing CSDR data deliverables;

(b) Describe how recurring vs. nonrecurring costs are segregated in its accounting system and for the purpose of CSDR reporting;

(c) Demonstrate how the data from its accounting system will be mapped into the CSDR reports required by Attachment 0108 - CSDR Plan and associated CDRLs;

(d) Present the methodologies used for mapping internal cost accounts to the Work Breakdown Structure (WBS), specifically showing how individual WBS elements and functional element codes will be populated;

(e) Propose any changes to Attachment 0108 - CSDR Plan in order to tailor the plan to the contractor’s accounting system, to include any contractor recommended changes or additions to the WBS elements. These changes may include adjustments to the submission events and submission timelines, particularly in the case of a direct-reporting subcontractor performing against a different delivery schedule than the associated prime contractor;

The contractor and CWIPT will also review the initial submission of the “Resource Distribution Table (RDT)” (CDRL A004), in order to finalize which subcontractors will be required to provide CSDR reporting and electronic submission of deliverables directly to the Defense Cost and Resource Center (DCARC) and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver.

The Post-Award Cost and Software Data Reporting Conference shall be held within 60 days of the Start of Work Meeting on a date mutually agreed to by the CWIPT and the contractor. This meeting has an anticipated duration of one (1) business day.

C.1.3.10.2 CSDR MAPPING REVIEW(S)

The contractor shall host a CSDR Mapping Review with the Government CWIPT at least 60 days before the initial CSDR report submission or the second CSDR report submission if the initial submission is due within 60 days of contract award. The contractor shall host the Mapping Review at the contractor’s facility where CSDRs are prepared. The purpose of a CSDR Mapping Review is to ensure that all contractor internal control accounts and all part numbers identified in the CDRL A009 - Bill of Materials (BOM) are mapped to the appropriate CSDR WBS elements in accordance with MIL-STD-881E and as required by CDRL A005 - Cost and Hour Report and Attachment 0108 - CSDR Plan. The meeting has an anticipated duration of up to three (3) business days. In the event that new control accounts or part numbers are created after the initial CSDR Mapping Review, the contractor shall review the updated mappings with the Government prior to follow-on CSDR submissions either via phone or email.

C.1.3.11 AD-HOC REVIEWS

The contractor and Government may meet on an ad-hoc basis to discuss issues, including and not limited to: contract execution and problem resolution for engineering, quality, logistics, test, risk, manufacturing, configuration management, production, business, and cyber and program management topics. Meetings will be conducted via telecom and web conference or at a location mutually agreed upon between the contractor and Government.

C.1.3.12. GOVERNMENT AND CONTRACTOR COLLABORATION

The contractor and Government shall collaborate to resolve issues as quickly as possible. The contractor shall permit the Government to participate in any internal discussions relating to design reviews, process reviews, root cause analysis, and corrective action discussions, that are specific to the JLTV design or process changes so that a path forward can be mutually agreed upon as quickly as possible. In addition, the contractor shall permit the Government to participate in and attend any contractor-initiated or contractor-led events that are related to the JLTV FoV.

C.1.3.13 REGULARLY SCHEDULED IPTS

The contractor and Government may meet on a regularly scheduled basis to discuss contract execution and problem resolution for engineering (including in-depth reviews for: hardware and software design; design margin; design robustness; component and system D/PFMEAs; testing planning and results with DVP&R; failure analysis; human factors; software lifecycle sustainment; maintenance and repair – not all inclusive), quality, logistics, test, risk, manufacturing, configuration management, production, and program management. Meetings will be conducted via telecom and web conference or at a location mutually agreed upon between the contractor and Government. Required meetings include, but are not limited to:

1. Manufacturing IPT: Expected frequency: 1 meeting per week

2. Production/Acceptance IPT: Expected frequency: 1 meeting per day

3. Product Improvement IPT: Expected frequency: 2 meetings per week

4. Continuous Improvement IPT: Expected Frequency: 1 meeting per week

5. Product Support Manager IPT: Expected Frequency: 1 meeting per month.

6. Logistics Leadership IPT: Expected Frequency: 1 meeting per week.

7. Systems Engineering IPT: Expected frequency: 2 meetings per week

C.1.4 BUSINESS MANAGEMENT

C.1.4.1 COST AND SOFTWARE DATA REPORTING (CSDR)

Cost and Software Data are the primary means by which the Department of Defense (DoD) collects data on the costs that contractors incur on DoD programs. Reliable and comprehensive cost data is essential to produce credible cost estimates as required in both statute and regulation. The Government’s goals and use of CSDR data is to improve the quality of cost estimates; ensure proper resource allocation occurs within the DoD; and enable data driven decision making by program and department leadership.

The contractor shall systematically collect and report actual contract costs in accordance with the following CDRLs and Attachment 0108 - CSDR Plan:

Report Title CDRL

C.1.4.1.1 APPLICATION TO SUBCONTRACTORS

The Contractor shall flow-down CSDR requirements referenced in section C.1.4.1 and its sub-paragraphs to subcontractors (regardless of subcontractor tier) when the subcontract value is expected to exceed $50 million using the maximum allowable contract quantities, hours, or options (as applicable), as required by Department of Defense (DoD) 5000.04-M-1 - CSDR Manual. The contractor shall require subcontractors to electronically submit CSDR deliverables directly to the Defense Cost and Resource Center (DCARC). The contractor shall ensure that subcontractors subject to CSDR reporting thresholds collect data in sufficient detail to meet Attachment 0108 - CSDR Plan requirements. The contractor shall collect and deliver data on all subcontractors to comply with Attachment 0108 - CSDR Plan requirements, Attachment 0109 – Resource Distribution Table (RDT), and CDRL A004 - Resource Distribution Table. A “subcontract,” per DoDM 5000.04 M-1 Cost and Software Data Reporting Manual, is any agreement, purchase order, or instrument other than a prime contract calling for work or for the material required for the performance of one or more prime contracts. A “subcontract” usually covers procurement of major components or subsystems that require the subcontractor to do extensive design, development, engineering, and testing to meet a prime contractor’s procurement specifications.

C.1.4.1.2 RESOURCE DISTRIBUTION TABLE

The Contractor shall prepare and deliver the “Resource Distribution Table (RDT)” in accordance with CDRL A004. The “Resource Distribution Table (RDT)” identifies the value of work assigned to the contractor and its subcontractors for each WBS element listed in Attachment 0108 - CSDR Plan, and is the primary means of identifying subcontractors who qualify for CSDR reporting.

C.1.4.1.3 COST AND HOUR REPORT (FLEXFILE)

The contractor shall prepare and submit the “Cost and Hour Report (Flex File)” in accordance with CDRL A005. The “Cost and Hour Report (Flex File)” reports incurred and forecasted costs and hours related business data in order to perform this contract.

C.1.4.1.4 QUANTITY DATA REPORT (DD FORM 1921-Q)

The contractor shall prepare and submit the “Quantity Data Report (DD Form 1921-Q)” in accordance with CDRL A006. The “Quantity Data Report (DD Form 1921-Q)” reports quantity information to provide context to the data reported in Flex File submissions and in order to derive accurate unit cost information.

C.1.4.1.5 TECHNICAL DATA REPORT (TDR, DD FORM 1921-T)

The contractor shall prepare and submit the “Technical Data Report (DD Form 1921-T)” in accordance with CDRL A007. The “Technical Data Report (DD Form 1921-T)” reports technical parameter data to provide context to the data reported in Flex File submissions and in order to derive parametric cost estimating relationships.

C.1.4.1.6 CONTRACTOR BUSINESS DATA REPORT (CBDR, DD FORM 1921-3)

The contractor shall prepare and submit the “Contractor Business Data Report (DD Form 1921-3)” in accordance with CDRL A008. The “Contractor Business Data Report (DD Form 1921-3)” reports data to facilitate estimating and analysis of indirect contract costs and rates.

C.1.4.2 OTHER COST REPORTS

The contractor shall systematically collect and report actual costs, performance, and any other required data in sufficient detail to prepare and submit the following reports in accordance with the following Contract Data Requirements Lists (CDRLs):

Report Title CDRL

C.1.4.2.1 BILL OF MATERIALS (BOM)

The contractor shall prepare and submit the “Bill of Materials (BOM)” in accordance with CDRL A009 for its JLTV design. The “Bill of Materials (BOM)” reports a complete list of material (e.g., part numbers, software, fluids) including all levels of assembly required to build, assemble, and sustain a complete JLTV end-item to include any kits or appliqué equipment. The first submission of the BOM shall identify the contractor’s JLTV design as of the date of contract award and the final submission shall identify the JLTV design current as of the end of the contract.

C.1.4.2.2 PROJECT EXPENDITURE REPORT (PER)

The Contractor shall prepare and submit the “Project Expenditure Report (PER)” in accordance A010. The “Project Expenditure Report (PER)” reports data on funding requirements, costs expended, and estimates at completion for work directives and other service efforts.

C.1.5 PROGRAM PROTECTION

The contractor shall comply with the security requirements imparted by Attachment 0102, Security Classification Guide (DD254), the National Industrial Security Program Operating Manual (NISPOM) DoD, 5220.22-M), and Army Regulation (AR) 70-77.

The contractor shall develop, document, and update the Program Protection Plan (PPP) with software assurance plans and actual values in accordance with the table description provided in the Defense Acquisition Guidebook. (Defense Acquisition Guidebook (dau.edu)).

C.1.5.1 PROGRAM PROTECTION WORKING GROUP AND CRITICAL PROGRAM INFORMATION ASSESSMENT The contractor shall host a Program Protection Working Group (PPWG) not less than annually. The first PPWG shall be held as part of the Contract SOWM. Each PPWG will be chaired by the Government Systems Engineer and co-chaired by the contractor's System Security Engineer. The co-chair shall develop the agenda and action items (reference CDRL A002, Read Ahead Agenda and CDRL A003, Minutes). The agenda shall include a Critical Program Information Assessment (CPIA) that will identify Critical Program Information (CPI) 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 Department of Defense). Each PPWG will be a one (1) day event.

C.1.5.2 CRITICAL FUNCTIONAL ANALYSIS (CFA)

The contractor shall conduct a CFA for the purpose of identifying Critical Components that can lead to Criticality Level I and Level II protection failures (as defined in DoDI 5200.44 and within the Defense Acquisition Guidebook (DAG)). The CFA shall assess critical components for the following war fighting functions: movement and maneuver; intelligence; fires; protection; sustainment; command and control; casualty evacuation, and treatment. The CFA shall identify all logic bearing critical components as well as the hardware and software suppliers for the logic bearing components.

The contractor shall host a one (1) day review NLT 60 days after contract award with the Government Program Protection team to discuss and review the results of the CFA. The critical components shall be prioritized, assessed for supply chain risk (as defined in DoDI 5200.44). The contractor shall develop mitigations or countermeasures to minimize the risk posed from supply chain. The contractor shall develop meeting minutes and action items (CDRL A003 Minutes) for the CFA review. The CFA, supply chain risk, and mitigation or countermeasures for risks shall be included in the meeting minutes. The CFA shall assess both Organic critical components as well as the integration of inherited critical components.

The contractor shall develop and deliver a mission criticality analysis(es),…