W56HZV20R0021-0005.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name And Title Of Signer (Type or print)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

By (Signature of person authorized to sign) (Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Fixed Price Incentive (Cost Based)

0005 2022MAY26

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

DANIEL SAFFRON

EMAIL: DANIEL.J.SAFFRON.CIV@ARMY.MIL

W56HZV-20-R-0021

2020DEC18

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 41

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: DANIEL SAFFRON

Buyer Office Symbol/Telephone Number: CCTA-ALH-B/(586)282-2073

Type of Contract 1: Fixed Price Incentive (Cost Based)

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

1. The purpose of Amendment 0005 of RFP W56HZV-20-R-0021 is to make the following revisions:

2. SECTION B:

a). Section B, Narrative B0001, Section B.1.1 is hereby revised by removing reference to ordering periods 3-5.

b). Remove the following CLINs from Section B:

3001AA ORDERING PERIOD 3 BRADLEY M2A3 TO M2A4

3002AA ORDERING PERIOD 3 BRADLEY M2A2 OSD-SA TO M2A

3003AA ORDERING PERIOD 3 BRADLEY M2A2 OSD-SA TO M2A

3004AA ORDERING PERIOD 3 BRADLEY M7BFIST SA TO M7A4

3010AA ORDERING PERIOD 3 TRI-COLOR PAINT

3020AA ORDERING PERIOD 3 HEAT ABATEMENT KIT REPAIR

3030AA ORDERING PERIOD 3 LRU REPAIR AND REPLACE

3040AA ORDERING PERIOD 3 PRODUCTION BREAK

3050AA ORDERING PERIOD 3 OBSOLESCENCE REDESIGN

3100AA ORDERING PERIOD 3 FPT AND EFPT TEST SUPPORT

4001AA ORDERING PERIOD 4 BRADLEY M2A3 TO M2A4

4002AA ORDERING PERIOD 4 BRADLEY M2A2 OSD-SA TO M2A

4003AA ORDERING PERIOD 4 BRADLEY M2A2 OSD-SA TO M2A

4004AA ORDERING PERIOD 4 BRADLEY M7BFIST SA TO M7A4

4010AA ORDERING PERIOD 4 TRI-COLOR PAINT

4020AA ORDERING PERIOD 4 HEAT ABATEMENT KIT REPAIR

4030AA ORDERING PERIOD 4 LRU REPAIR AND REPLACE

4040AA ORDERING PERIOD 4 PRODUCTION BREAK

4050AA ORDERING PERIOD 4 OBSOLESCENCE REDESIGN

4100AA ORDERING PERIOD 4 FPT AND EFPT TEST SUPPORT

5001AA ORDERING PERIOD 5 BRADLEY M2A3 TO M2A4

5002AA ORDERING PERIOD 5 BRADLEY M2A2 OSD-SA TO M2A

5003AA ORDERING PERIOD 5 BRADLEY M2A2 OSD-SA TO M2A

5004AA ORDERING PERIOD 5 BRADLEY M7BFIST SA TO M7A4

5010AA ORDERING PERIOD 5 TRI-COLOR PAINT

5020AA ORDERING PERIOD 5 HEAT ABATEMENT KIT REPAIR

5030AA ORDERING PERIOD 5 LRU REPAIR AND REPLACE

5040AA ORDERING PERIOD 5 PRODUCTION BREAK

5050AA ORDERING PERIOD 5 OBSOLESCENCE REDESIGN

5100AA ORDERING PERIOD 5 FPT AND EFPT TEST SUPPORT

c). Update the total estimated quantity in Section B.1.5 from 211 vehicles to 106 vehicles.

d). Update CDRL A044 CLIN Description:

From: CDRL A044 Obsolescence Status Report Service Requested: Obsolescence Status Report

To: CDRL A044 Obsolescence Alert Notice Service Requested: Obsolescence Monitoring Report e). Add CDRL A048 CDRL Obsolescence Alert Notice Service Requested: Obsolescence Status Report

3. SECTION C:

a). Section C, Narrative C0001, Scope of Work Sections C.2.4, C.15 (and subsections), C.16.1, C.16.2.1, C.16.11.6, C.16.1.33.5, C.9.18.1, C.9.18.2 and C.9.18.3 are hereby revised.

4. SECTION E:

a). Section E, Narrative E0001, Inspection and Acceptance Sections E.1.1, and E.2.2 are hereby revised.

2 41

W56HZV-20-R-0021

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

5. SECTION H:

a). Section H, Narrative H0001, Section H.6 is hereby revised by removing reference to ordering periods 3-5.

b). Renumber Sections H.8, and H.9 (and subsections) as follows:

From: H.8 Ordering Authority

H.9 Misc. Conditions of Contract Execution

To: H.9 Ordering Authority

H.10 Misc. Conditions of Contract Execution c). Section H.5 Tri-Color paint is revised by removing CLINs 3010AA, 4010AA and 5010AA.

d). Section H.7.1 Production Break is revised by removing CLINs 3040, 4040 and 5040.

e). Add new Section H.8 as: The Government will attach the Obsolescence exceptions within CDRL A048 to the respective Delivery Order within 21 days of approval.

6. SECTION J:

a). Update Exhibit A

From: Exhibit A CDRLS (A001 - A047) dated 20-JAN-2022

To: Exhibit A CDRLS (A001 - A048) dated 25-MAY-2022 b). Update Title and Subtitle of CDRL A044

From: TITLE OF DATA ITEM: Obsolescence Status Report SUBTITLE: A4 Obsolescence Status Report

To: TITLE OF DATA ITEM: Obsolescence Alert Notice SUBTITLE: Obsolescence Monitoring Report c). Add CDRL A048 - TITLE OF DATA ITEM: Obsolescence Alert Notice SUBTITLE: Obsolescence Status Report d). Update Attachment 0008

From: Attachment 0008 (ENGINEERING CHANGE PROPOSALS) dated 23-SEP-2021

To: Attachment 0008 (ENGINEERING CHANGE PROPOSALS) dated 25-MAY-2022 d). Update Attachment 0026

From: Attachment 0026 (FAT MATRIX) dated 17-MAR-2021

To: Attachment 0026 (FAT MATRIX) dated 25-MAY-2022 e). Update Attachment 0039

From: Attachment 0039 (PRICING MATRIX) dated 23-SEP-2021

To: Attachment 0039 (PRICING MATRIX) dated 25-MAY-2022

7. All other terms and conditions, except those addressed in this Amendment 0005, remain unchanged and in full force and effect.

*** END OF NARRATIVE A0006 ***

3 41

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 CLIN Structure. In the four digit Contract Line Item Numbers (CLINS) that follow, the numbering system that is used is as follows:

B.1.1 The first digit signifies the ordering period:

1XXX represents ordering period one

2XXX represents ordering period two

B.1.2 The second digit signifies test support:

X1XX represents Follow-On Production Test (FPT) and Extended Follow-on Production Testing (EFPT) Test Support

B.1.3 The third digit signifies the vehicle add-ons, repairs and production break

XX1X represents Tri-Color Paint

XX2X represents Heat Abatement Kit Repair

XX3X represents LRU Repair and Replace

XX4X represents Production Break

XX5X represents Obsolescence Redesign

B.1.4 The fourth digit signifies the vehicle conversion:

XXX1 represents a M2A3 to M2A4

XXX2 represents a A3 BFIST to M7A4

XXX3 represents a M2A2 ODS-SA to M2A4

XXX4 represents a M7BFIST SA TO M7A4

B.1.5 Unless separately priced as laid out on the CLIN structure of the contract, all scope requirements are assumed to be priced within the vehicle unit price and range pricing represented in each CLIN.

The total Estimated Quantity for this requirement is 106 vehicles. Estimated quantities are listed for each ordering year in the Pricing

Attachment 0039.

IAW FAR 16.503(c): Government property furnished for repair. As a requirements contract is used to acquire work (e.g., repair, modification, or overhaul) on existing items of Government property, failure of the Government to furnish such items in the amounts or quantities described in the Schedule as "estimated" or "maximum" will not entitle the contractor to any equitable adjustment in price under the Government Property clause of the contract.

Accelerated delivery is authorized at no additional cost to the Government. If accelerated delivery is more than 60 days prior to the contractual delivery date, the contractor must notify the Government PCO in writing for authorization.

*** END OF NARRATIVE B0001 ***

4 41

PIIN/SIIN

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

3001AA DELETED _______

3002AA DELETED _______

3003AA DELETED _______

3004AA DELETED _______

3010AA DELETED _______

3020AA DELETED _______

3030AA DELETED _______

3040AA DELETED _______

3050AA DELETED _______

3100AA DELETED _______

4001AA DELETED _______

4002AA DELETED _______

4003AA DELETED _______

4004AA DELETED _______

4010AA DELETED _______

4020AA DELETED _______

5 41

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

4030AA DELETED _______

4040AA DELETED _______

4050AA DELETED _______

4100AA DELETED _______

5001AA DELETED _______

5002AA DELETED _______

5003AA DELETED _______

5004AA DELETED _______

5010AA DELETED _______

5020AA DELETED _______

5030AA DELETED _______

5040AA DELETED _______

5050AA DELETED _______

5100AA DELETED _______

9000 BASIC CLIN FOR ELIN ___________________

6 41

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

A044 CDRL A044 - OBSOLESCENCE ALERT NOTICE 1 LO $ ** NSP ** _____________________________________ __________________

SERVICE REQUESTED: OBSOLESCENCE MONITORING REP

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

A048 CDRL A048 - OBSOLECENCE ALERT NOTICE 1 LO $ ** NSP ** ____________________________________ __________________

SERVICE REQUESTED: OBSOLESCENCE STATUS REPORT

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

DLVR SCH PERF COMPL

REL CD QUANTITY DATE ________ ______________ __________

001 1 SEE DD FORM 1423

7 41

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 General. The contractor shall produce M2A4 vehicles from M2A3 and M2 Operation Desert Storm-Situational Awareness (ODS-SA) source vehicles and M7A4 vehicles from A3 Bradley Fire Support Team (BFIST) with Fire Support Sensor System (FS3) and M7 BFIST-SA source vehicles in accordance with (IAW) Section C.9.

C.1.1 Data Deliverables are listed in Section J, unless otherwise specified, contractor format is acceptable. The contractor shall use an editable format for all data deliverables.

C.1.1.2 All CDRLs with XX for dd250 will be Inspected and Accepted (I&A) by the Government in the CDRL delivery tool. BLOCK 7: XX means

CDRLS are submitted to CDRL delivery tool only and I&A will be approved in CDRL tool.

C.1.2 Review and Access.

The Procurement Contracting Officer (PCO) or the Contracting Officer Representative (COR) shall have the right to review, both in-process and upon completion, all project efforts, data and documentation expended and prepared under this contract. This includes, but is not limited to, design, fabrication, assembly, test, calibration, quality, inspection, and Integrated Logistics Support (ILS) documents.

Within 5 working days of a request, the contractor shall make available to the Government any associated records and data including those related to cost, schedule, and performance.

C.1.2.2.1 The contractor shall allow unescorted access to the Bradley A4 assembly and fabrication areas, at BAE facilities, to the

Contracting Officers Representative (COR).

C.2 Meetings, Conferences and Reviews:

C.2.1 The contractor shall participate and host the meetings, conferences, and reviews listed in this contract. Whenever possible, meetings shall be conducted virtually using Government agreed-upon technology.

C.2.1.1 Agendas, Presentation Materials and Minutes. Unless otherwise specified, the contractor shall deliver CDRL A001 Agenda, CDRL

A002 Presentation Materials , and CDRL A003 - Meeting Minutes for all meetings identified in Section C.2. Agendas, Presentation

Materials and Minutes shall reflect the identification of major problem areas, the plans for their resolution, and the assessment of the impact, if any, on the contract objectives.

C.2.2 Start of Work Meeting (SOWM). The contractor shall host a Start of Work meeting at a BAE facility within 40 business days after contract award to review all requirements of the contract. The contractor shall schedule the event with the Defense Contract Management

Agency (DCMA) office, the Procuring Contracting Officer (PCO), and Product Manager (PdM) Bradley office at least 20 business days in advance of the meeting. The contractor shall participate with the Government to arrange a schedule and agenda for the meeting. The contractor shall deliver an agenda in accordance with CDRL A001, presentation materials in accordance with CDRL A002, and meeting minutes in accordance with CDRL A003.

C.2.3 Production Status Meetings. The contractor shall conduct a weekly Production meeting via teleconference to provide the Government with status on the production of vehicles. The Contractor shall coordinate the Production meeting agenda issues, topics and schedules with the Government Production Integrated Product Team (IPT) members. The contractor shall discuss production risks, issues, and any resulting pending and approved Requests for Variance (RFVs) or design changes required to address these issues. The contractor shall track generated Engineering Support In Production (ESIP) requests status and the duration of each request. The presentation materials shall include the following items listed below:

(a) Vehicle status:

1. Current vehicle location

(b) Parts status:

1. Shortage list showing expected delivery date of each short part, and shortage impact to contractual DD 250 dates

(c) Production Issues

(d) Open Contracting action items

(e) Quality Concerns

(f) Failure Analysis and Corrective Action Report (FACAR) (reference section C.10.5)

The minutes shall contain schedules; detailed results and proceedings of discussions, assessments, and guidance; action items; an attendees roster; and all presentations. Action items shall be assigned prior to the close of the meeting.

C.2.4 Quality Council (QC) Meetings. The Contractor shall conduct a single day, semi-annual, Bradley Quality Council IPT meeting at the Contractor's York facility. The Contractor shall coordinate the Quality Council meeting agenda issues, topics and schedules with the Government. The presentation materials shall include the following items for all Contractor facilities including BAE Red River, BAE

Anniston, BAE Aiken and BAE York and major subcontractors:

8 41

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(a) Current BAE Quality Organizational Charts at each contractor facility

(b) The status of action from previous QQC meetings

(c) Changes in internal and external issues relevant to the Quality Management System (QMS)

(d) Information on the performance and effectiveness of the QMS, including trends in:

o Audit results, internal and external non-conformances, and corrective actions o Measures of process effectiveness o Measures of process efficiency o Process performance and product conformity o Assessments of manufacturing feasibility o Extent to which quality objectives have been met (Government satisfaction) o Review of performance against maintenance objectives o Warranty performance (where applicable) o Review of supplier performance o Identification of potential process or product failures identified through risk analysis (such as Failure Mode & Effects Analysis (FMEA), Control Plan) o Actual process or product failures and their impact

(e) The adequacy of resources

(f) The effectiveness of actions taken to address risks and opportunities

(g) RESERVED

(h) Weld Quality: Defects Per Unit (DPU) Weld, 100% Final Inspection DPU, In Process Inspection DPU at each station, Major

Structure Defect Data, Top Defect count by station, Corrective Actions for each station

(i) In Process and Final Inspection data by vehicle serial number

(j) Product Quality Deficiency Report (PQDR), corrective actions and response time

(k) Internal and Government Audit Findings

(l) First Article Inspection (FAI): Tracking Current Status Schedule, Issues, Corrective Actions

(m) Top 10 Problem Suppliers: Corrective Actions taken to address suppliers

(n) Top 5 defects at each facility: Corrective Actions taken to address defects

(o) Non-Conforming Material

(p) Continuous Process Improvement (CPI)

C.2.4.1 The minutes shall contain schedules; detailed results and proceedings of discussions, assessments, and guidance; action items;

an attendees roster; and all presentations. Action items shall be assigned prior to the close of the meeting.

C.2.5 Reserved

C.2.6 Post-Award Cost and Software Data Reporting Conference (CSDR)

The Contractor shall host a Post-Award CSDR Conference at the Contractors facility where CSDRs are prepared with the Governments Cost

Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoD 5000.04-M-1 (CSDR Manual). The purpose of the Post-Award

CSDR Conference is to review the contracts CSDR requirements and assess how the Contractors accounting system satisfies the CSDR requirements found in DoD 5000.04-M-1, CSDR Manual and Attachment 0002 - CSDR Plan. In a briefing presented by the Contractor in its own format, the Contractor shall:

- 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.

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

- Demonstrate how the data from its accounting system will be mapped into the CSDR reports required by Attachment 0002 - CSDR Plan and associated CDRLs.

- 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.

- Propose any changes to Attachment 0002 - CSDR Plan in order to tailor the plan to the Contractors accounting system, to include any

Contractor recommended changes or additions to the WBS elements. These changes may include adjustments to the submission events and/or submission timelines, particularly in the case of a direct-reporting subcontractor performing against a different delivery schedule than the associated prime contractor.

C.2.6.1 The Contractor and CWIPT will also review the initial submission of the Resource Distribution Table (RDT) (CDRL A007), 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.

C.2.6.2 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 business day.

C.3 Business Management

9 41

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.3.1 The contractor shall conduct monthly meetings with the Government to analyze the contractors Earned Value Management (EVM) status.

The contractor shall deliver CDRLs A001-A003 for these meetings.

C.3.2 Integrated Baseline Review (IBR). The Contractor and Government will engage in a joint IBR at the contractor's facility no later than 120 business days after contract award. The review will verify the Performance Measurement Baselines (PMB's) realism, accuracy, and technical content. The contractor shall provide all records and data required by the NDIA Guide to the Integrated Baseline Review

(IBR), as agreed to by the USG and contractor, fifteen (15) business days prior to the IBR. A 12-month rolling wave detailed Integrated

Master Schedule (IMS) plan shall be presented at the initial IBR. After the initial IBR, the contractor shall continue to maintain a minimum of a 6 month rolling wave detailed IMS. Subsequent IBRs shall be conducted throughout the life of the contract for initiation of significant follow-on change actions as defined in the NDIA Guide to the Integrated Baseline Review (IBR) dated February 6, 2015.

The contractor shall deliver CDRLs A001-A003 for these IBRs.

C.3.2.1 Joint IBR Training. The contractor shall facilitate joint IBR training at the contractors facility at least 20 business days prior to the initial IBR. The Government, the Contractors Program and Control Account Managers, and Planning, Monitoring, and Control

Resources for this program shall attend the event. Presentation materials shall be delivered IAW CDRL A002 Presentation Materials and shall cover the purpose, outcome and goals of an IBR and include sample documentation and demonstrations to include detailed IMS, Schedule Risk Assessment, Work Breakdown Structure (WBS) and dictionary, Control Account Authorization (CAA), Control Account Plan (CAP) and Earned Value Criteria, dollarized responsibility assignment matrix and time phased PMB by work package. The joint training is intended to level-set both the contractor's Control Account Managers (CAMs) and the Government Leads on what to expect in an IBR. The contractor may work with the Government BRADLEY EVM Lead for assistance. Training is anticipated to last one day at a BAE facility.

C.3.3 Program Performance Management. The contractor shall meet program cost, schedule, supportability, and technical requirements set forth in the contract and its related documents. The contractor shall monitor in support of CDRL A004 Integrated Program Management

Data and Analysis Report (IPMDAR) and Integrated Master Plan (IMP): (a) the attributes of the work products and tasks required under this contract (i.e., measure the actual attributes of the work products and tasks, such as size and complexity, the content or changes to contract or schedule requirements, comparing these changes to the baseline in order to identify significant deviations); (b) the resources used to perform the contract resources including physical facilities, computers, peripherals, software used in design, manufacturing, testing and operation, networks, security environment, project staff, processes; and (c) the knowledge and skills of program personnel (critical skills acquisition, actual training versus projected, and deviations from plan).

C.3.4 Integrated Program Management Data and Analysis Report (IPMDAR) and Integrated Master Plan (IMP). The contractor shall deliver

CDRL A004 IPMDAR and IMP. The contractor shall prepare the IPMDAR and IMP IAW DI-MGMT-81861B, the DoD Integrated Master Plan and

Integrated Master Schedule Preparation and Use Guide and MIL-STD-881C.

C.3.4.1 The IPMDAR shall be updated and delivered at the Control Account IAW CDRL A004 IPMDAR and IMP. The IMS shall be traceable to the IMP. 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 reinforced by specific criteria that must be satisfied. The IMS shall roll up directly to the

IMP and corresponding IMP event and criteria. The contractor shall update and maintain an IMS by logically networking detailed program activities. The schedule shall be consistent with the Contract Work Breakdown Structure (CWBS) and contain the planned events and milestones, accomplishments, exit criteria, and activities from contract award to the completion of the contract. The IMS and time-phasing of the PMB shall be consistent. The IMS shall be resource loaded and clearly identify critical path activities. All IMS monthly submissions shall include written schedule analysis.

C.3.4.2 The contractor shall identify, with supporting rationale, any deviations or changes to the program baseline, and review all program plans, activities, and work products for consistency with the baseline requirements and any approved changes made to them. The contractor shall document all changes, including those to be made to the plans and work products resulting from changes to the requirements baseline. Where applicable, the contractor shall initiate and complete corrective action for all inconsistencies reported in CDRL A004 IPMDAR and IMP.

C.3.5 Incorporation of Baseline Changes. The PMB shall be updated with any required work packages upon receipt of the modification implementing the change. Changes shall be incorporated in accordance with the Contractors Earned Value Management System (EVMS) System

Description.

C.3.5.1 Current Period and Retroactive Changes. The contractor shall use American National Standards Institute/Electronic Industries

Alliance Standard (ANSI/EIA) 748 and the approved System Description in complying with changes. Current period or retroactive changes must be approved by the Government EVM Manager.

C.3.5.1.1 The contractor shall identify, with supporting rationale, deviations or changes to the program baseline, and review program plans, activities, and work products for consistency with the baseline requirements and approved changes made to them. The contractor shall document changes, including those to be made to the plans and work products resulting from changes to the requirements baseline.

The contractor shall initiate and complete corrective action for inconsistencies reported in CDRL A004 IPMDAR and IMP.

C.3.5.1.2 The contractor shall include issues identified by its subcontractors in the identification, tracking and management documentation identified in the C.3.5.1.1.

10 41

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.3.6 Earned Value Management System (EVMS). The contractor shall use an EVMS that complies with the EVMS guidelines in DoD 5000.02, Defense Acquisition Guidebook, the ANSI/EIA-748, CDRL A004 IPMDAR and IMP, and the contractors own documented System Description. EVM shall be used as a tool to identify and track program risks, manage cost, schedule, and technical performance.

C.3.6.1 Application to Subcontractors. The contractor shall flow-down EVMS requirements to subcontractors exceeding $20M. Flow down of requirements to subcontractors of less the $20M (then-year dollars) is a risk-based decision and will be as mutually agreed between the contractor and the Government at the SOWM. The performance information reported by the subcontractors shall be incorporated and integrated in the contractors management system. The contractor shall be responsible for reviewing and assuring the validity of all subcontractors reporting through surveillance and other means.

C.3.7 Over-Target Baseline (OTB) or Over-Target Schedule (OTS). The contractor shall submit a request to the PCO for Government approval to initiate an OTB or OTS. An OTB or OTS may be initiated in exceptional circumstances indicated by contract performance (per the contractor's EVMS Description). The request shall include a top-level projection of cost or schedule growth, a recommendation of whether or not performance variances should be retained on record, and a schedule for implementing a new baseline. The contractor shall not implement the OTB or OTS restructuring prior to receiving written approval from the PCO.

C.3.8 Contract Funds Status Report (CFSR). The contractor shall submit the CFSR quarterly in accordance with CDRL A005. The contractor shall reconcile reporting elements in the CFSR with the IPMDAR when these documents are submitted in the same month. The contractor shall provide a reconciliation of the CFSR with the IPMDAR as an addendum to the IPMDAR.

C.3.9 Cost and Software Data Reporting (CSDR)

C.3.9.1 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 Governments 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 Contract Data Requirements

Lists (CDRLs) and Attachment 0002 Contract CSDR Plan:

Report Title____________ CDRL____

Resource Distribution Table A007

Cost and Hour Report (FlexFile) A008

Quantity Data Report (DD Form 1921-Q) A009

Technical Data Report (DD Form 1921-T) A011

Contractor Business Data Report (DD Form 1921-3) A012

Bill of Materials (BOM) A022

C.3.9.2 Application to Subcontractors. The Contractor shall flow-down CSDR requirements referenced in section C.3.9.1 and its sub-paragraphs to subcontractors (regardless of subcontractor tier) when the subcontract value is expected to exceed $50 million using the most likely 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 CSDRs 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 0002 - CSDR Plan requirements. The Contractor shall collect and deliver data on all subcontractors to comply with Attachment 0003 RDT and CDRL A007- Resource Distribution Table and Attachment 0002 - CSDR Plan requirements. A subcontract 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 contractors procurement specifications.

C.3.9.3 Resource Distribution Table (RDT). The Contractor shall prepare and deliver IAW CDRL A007 RDT, the Resource Distribution Table

(RDT) to identify the value of work assigned to the Contractor and its subcontractors by for each WBS element listed in Attachment 0002 -

CSDR Plan, and is the primary means of identifying subcontractors who qualify for CSDR reporting.

C.3.9.4 Contract Work Breakdown Structure (CWBS) & Dictionary. The Contractor shall utilize the CWBS identified in Attachment 0002 -

CSDR Plan, as the primary framework for contract budgeting and reporting of incurred costs and hours to perform the contract. The

Contractor shall extend the WBS to provide adequate internal management, surveillance, and performance measurement of the contract. The

Contractor shall ensure all WBS oriented reporting is compliant with at least the levels identified in Attachment 0002 - CSDR Plan. The

Contractor shall develop and maintain a Contract Work Breakdown Structure (CWBS) Dictionary throughout the life of the contract, and shall submit the CWBS Dictionary. The CWBS Dictionary reports a description of the technical, cost, and work content of each WBS element.

C.3.9.5 Cost and Hour Report (FlexFile). The Contractor shall prepare and deliver the Cost and Hour Report (FlexFile) IAW CDRL A008. The

Cost and Hour Report (FlexFile) reports incurred and forecasted costs and hours related business data in order to perform this contract.

11 41

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.3.9.6 Quantity Data Report (DD Form 1921-Q). The Contractor shall prepare and deliver the Quantity Data Report (DD Form 1921-Q)IAW

CDRL A009. The Quantity Data Report (DD Form 1921-Q) reports quantity information to provide context to the data reported in FlexFile submissions and in order to derive accurate unit cost information.

C.3.9.7 Reserved

C.3.9.8 Technical Data Report (TDR, DD Form 1921-T). The Contractor shall prepare and deliver the Technical Data Report (DD Form 1921-T)

IAW CDRL A011. The Technical Data Report (DD Form 1921-T) reports technical parameter data to provide context to the data reported in

FlexFile submissions and in order to derive parametric cost estimating relationships. Each submission of the TDR shall reflect a Full

Combat Configuration vehicle produced during the CSDR reporting period.

C.3.9.9 Contractor Business Data Report (DD Form 1921-3). The Contractor shall develop, maintain, and deliver the data item IAW CDRL

A012, the CSDR Manual (DoD 5000.04-M-1), and as tailored in this CDRL and Attachment 0002 - CSDR Plan. The CSDR Manual is available from the CADE website at https://cade.osd.mil/ . Contractors shall be required to submit 1921-3 Contractor

Business Data Report on an annual basis within 60 days subsequent to the end of the contractors fiscal year for the life of the contract

IAW CDRL A012 . Only one report is required to be completed and submitted by each Forward Pricing Rate (FPR) unit (e.g., plant, site, business unit) per year, independent of the number of contracts within the FPR unit which contain this CDRL item. The Contractor

Business Data Report is to be prepared by and for the business entity (e.g., plant, site, or business unit) responsible for submitting the Forward Pricing Rate Proposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the

Government. In the absence of a FPR requirement, the term FPR unit should be interpreted for reporting purposes as business unit as defined in the FAR.

C.3.9.10 Bill of Materials (BOM)

The Contractor shall develop, maintain, and deliver a priced indentured BOM for all Bradley variants and contract line items that incur material costs (e.g. LRU Repair/Replace, etc.) IAW CDRL A022 Priced Indentured Bill of Material. The indentured BOM shall include:

End Item, Variant/CLIN, Next Higher Assembly (NHA) Item, NHA Item Description, Level, WBS, WBS Description, Component Item, Component

Item Description, Make Buy Code, Component Item Type, Component Quantity, Extended Quantity, Unit of Measure (UOM), CMP Organization

Code, National Stock Number (NSN), BOM WIP Supply Type, End Assembly Pegging, "Discrete Receivable (Y/N)", Supplier, Average Unit Cost

(AUC) , Extended Average Unit Cost (EAUC), Extended Average Unit Price (EAUP). As part of the BOM delivery, CDRL A022, the contractor shall also deliver an adders matrix that identifies all component item types and which adders are applied to each component item type. A sample adders matrix is provided in Attachment 0044. The contractor shall format the BOM in a parent child format and include all of the components required to build the vehicles. The contractor shall provide an analysis that reconciles the BOM data with the data delivered in CDRL A008 Cost and Hour Report (Flexfile) and CDRL A009 - Quantity Data Report (DD Form 1921-Q). The contractor shall deliver CDRL A022 with data that reflects the vehicle configuration at the end of the base order and each option order the BOM delivery is linked to and provide deliverable notes and guides to explain the data represented in the deliverable. The contractor shall provide the information in 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.

C.4 Engineering

C.4.1 Manufacturing Plan. The Contractor shall update and submit the A4 Bradley Manufacturing Plan (CDRL A013) to include material flow plans, process control plans, assembly plans, calibration plans, and corrosion plans to sustain production.

C.4.1.1 The contractor shall update and make available all production plans including quality documents, production lay outs that identify locations for assembly tasks, tooling, fixturing, production equipment, material storage, and preservation and storage of tooling to sustain production.

C.4.1.2 The contractor shall update and submit, IAW CDRL A013, all facility and facilitation plans to sustain production. The plans shall be detailed by contractor facility. The plans shall include plant and facility layout, and assembly tooling installation plans.

C.4.1.3 The contractor shall update and submit, IAW CDRL A013, a Manufacturing Management Plan (MMP). The contractors MMP shall include provisions demonstrating the specific resources, capabilities, knowledge and skill sets required to complete the production effort. The contractor shall include provisions for staffing requirements.

C.4.2 Reserved

C.4.3 Production Support Engineering (PSE) and Engineering Support in Production (ESIP). The contractor shall conduct shop floor support, gathering documentation, generating Product Identification Information, documenting production changes and implementing the plan to the production line. The contractor shall conduct and provide root cause analysis, investigation and resolution of production build issues at the weekly Production meetings (paragraph C.2.3).

C.5 Configuration Management (CM)

C.5.1 The contractor shall manage the configuration of the M2A4 and M7A4 vehicle systems in production and adhere to the CM principle CM-

1 within EIA-649-1 Configuration Management Requirements For Defense Contracts (NOV2014).

12 41

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.5.1.1 Configuration Management Plan (CMP). The contractor shall prepare a CMP using CM principles from EIA-649-1 and submit to the

Government for approval (CDRL A014). The contractors CMP shall adhere to principles CMP-1 through CMP-8, sections 3.1 through 3.1.4(2) of EIA-649-1 and flow down of the requirements of this CMP to all subcontractors as part of the contractors subcontract or purchase order award. The contractor shall manage the configuration baseline of the M2A4 and M7A4 vehicles IAW the Government-approved contractors CMP. The contractor shall address Data Management (DM) in their CMP which shall contain a master list of managed data, data content, and data format descriptions, data requirements lists for all suppliers, privacy requirements, security requirements, and procedures. The contractor shall also provide the location or mechanism of data retrieval, reproduction, and distribution, as well as a listing of program data to be collected, and the schedule for its collection. The Government reserves the right to review contents and verify the accuracy of the contractors configuration control system at any time during the Contract. If the contractor makes any changes to its CM process, then the contractor shall submit an updated CMP to the Government for approval (CDRL A014).

C.5.1.2 Product Configuration Identification. All performance, product specifications, product drawings, Computer Aided Design (CAD) drawings, models, approved changes, remanufacture documents, RESET documents, software documentation, computer software used for design, production, and test and validation of a vehicle shall constitute the Product Configuration Identification (PCI) for that system.

C.5.1.2.1 Configuration Identification. The contractor shall use a documented process for configuration identification. This process shall adhere to EIA-649-1 through C1-12, sections 3.2 through 3.2.4.2 and be a part of CMP outlined in C.5.1.1.

C.5.1.3 Engineering Change Proposal (ECP). Any Changes to configuration shall be accomplished through the Engineering Change Proposal

(ECP) process reflected in the contractors Configuration Management Plan. The contractor shall deliver ECP packages (CDRL A015) consisting of DD FORM 1692 pages 1, 2, 3 and 4, STA FORM 1603, DD Form 1695 Notice of Revision(s) (NORs) and Logistics Impact Form

(Attachment 0005) for all ECPs. All minor (Class 2) ECPs are routine priority.

C.5.1.3.1 Classification and Authority of ECPs: Major (Class I) and Minor (Class II)

C.5.1.3.1.1 The contractor shall use content in DD Form 1692 for assigning a Major (Class I) or Minor (Class II) classification to an

ECP.

C.5.1.3.1.2 Concurrence in Classification. The contractor shall obtain DCMA concurrence of any (Class II) Minor ECPs. The contractor shall cancel a Minor (Class II) ECP if DCMA/Government disagrees with classification of the ECP. The contractor shall reprocess the proposed change as a Major (Class I) ECP. The Government reserves the right to make final determination of ECP Classification.

C.5.1.3.2 ECP Decisions. The PdM-Bradley Fighting Vehicles (BFV) Configuration Control Board (CCB) is the configuration approval authority for all Major (Class I) engineering changes.

C.5.1.3.3 Engineering Change Priorities. The contractor shall use content in DD Form 1692, block 6 to determine Engineering Change

Priority. The contractor shall not assign an Emergency or Urgent Engineering Change Priority to a Minor (Class II) ECP. The Government will make final determination of the Engineering Change Priority.

C.5.1.3.4 Assertions of Restriction for ECPs. Throughout the life of the contract, for each ECP with each ECP package submission, contractor must submit a complete Assertion of Restrictions IAW DFARS 252.227-7017, 7013, 7014, 7015, and 7028. The contractor shall not deliver or otherwise provide to the Government any technical data or computer software with restrictive markings (or otherwise subject to restrictions on access, use, modification, reproduction, release, performance, display, or disclosure) unless the technical data or computer software has been identified in the Assertion of Restrictions.

C.5.1.5 Request for Variance (RFV). The contractor shall deliver a DD Form 1694 Request for Variance (RFV) IAW CDRL A016 as soon as the need is identified to temporarily depart from the specified TDP in Sections C.9.1 through C.9.4. The contractor shall obtain Government approval prior to delivery of any product that will be produced, or has been produced, as defective or nonconforming. When completing block 15 of DD Form 1694, the contractor shall reference Bradley Performance Specification (Attachment 0016) to assess impacts to vehicle performance.

C.5.1.5.2 Classifications of Variances. The contractor shall use the content in DD Form 1694 for a assigning a Critical, Major, or Minor classification to an RFV.

C.5.1.5.3 RFV Decisions. The PdM-BFV CCB is the configuration authority for all Critical and Major RFVs. All Minor RFVs will be approved or rejected by DCMA. The contractor shall submit all Critical and Major RFVs to the PdM-BFV CCB for review and decision. The contractor shall submit all Minor RFVs to DCMA for review and decision.

C.5.2 ECP/RFV Co-User Requirements. Co-user is defined as two or more entities with shared use of a Bradley Configuration Item (CI).

The contractor shall initiate, coordinate, and support a Co-User CCB meeting with the Government to obtain change concurrence with the

Design Authority and Co-users of CI technical data prior to formal submissions of ECPs/RFVs.

C.6 Technical Data

13 41

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.6.1 Engineering Drawings and Specifications. For any ECPs developed under this contract, the contractor shall prepare and deliver a

Product level Technical Data Package (TDP), including new product level drawings, in accordance with MIL-STD-31000B, CDRL A018 and the

TDP Option Selection Worksheet (Attachment 0006). Product level is defined in MIL-STD-31000B, section 5.2.3. The Product level TDP shall be complete to provide the elements and information necessary to enable the Government to competitively procure, provision, and catalog an item identical to the original item, without additional engineering effort or recourse to the contractor or subcontractor.

ECPs for legacy components do not require new CAD models.

C.6.1.1 Legacy components. Legacy components are items which comprise the A3 and ODS-SA Bradley vehicles at the time of induction. Re-used legacy components are items which are required to produce the A4 level Bradley vehicles. Non-legacy components are new items specified in the Bradley A4 TDP that are not included in the A3 and ODS-SA TDP.

C.6.1.2 Revised Product Data. For any ECPs developed under this contract, the contractor shall revise existing Product Data in accordance with the drawing preparation standards that the drawings were originally prepared to, if changes are required to product data. If existing product data were originally created and released to the Government with CAD drawing(s), then the CAD drawing(s) shall be updated IAW with modeling preparation standards that the CAD drawing(s) was prepared to originally.

C.6.1.3 Specifications. For any ECPs developed under this contract, the contractor shall prepare specifications in accordance with MIL-

STD-961E-2008, Defense and Program Unique Specifications Format and Content (CDRL A019). All new data must be submitted to the

Government for review/approval before an Engineering Release Record (ERR) is accepted.

C.6.2 Interface Control Documents (ICD). For any ECPs developed under this contract, the contractor shall coordinate, evaluate, and modify changes to any other ICD/drawings on/for the vehicle system, subsystem, special purpose kits or in support of the vehicle operation. ICDs developed under this contract shall be delivered in accordance with CDRL A020.

C.7 Software

C.7.1 The contractor shall purchase the following software licenses for each vehicle produced:

Software License Vendor License Type No. of Copies SW Resident Line per vehicle Replaceable Unit (LRU)

VxWorks OS WindRiver run time 1 Computer

Processing

Unit (CPU)

Linux OS Redhat run time 6 Common

Intelligence

Display (CID)

(Squad

Leaders

Display(SLD)

/Commanders

Tactical

Display (CTD))

(BAE Application, Black & Red)

TEE General run time 2 CID (SLD/CTD)

Dynamic

Crossing GuardXD General run time 2 CID (SLD/CTD)

Dynamic (GD)

Ballistic Solution GD run time 1 CPU

SW (BSS)

C.7.1.1 The contractor is not required to keep configuration control on the licenses beyond vehicle acceptance.

C.7.1.2 The contractor shall transfer the runtime software license rights to the Government at vehicle acceptance.

C.7.1.3 The Government will identify the Government POC to receive the transferred license rights and assume responsibility for the renewals of the software subscriptions no later than 9 months after contract award.

C.7.1.4 The contractor shall supply vehicles with a software subscription valid for 12 months from vehicle acceptance date.

C.7.2 Disk Duplication Needs

C.7.2.1 The contractor shall perform disk duplication of Common Intelligent Display-2 (CID-2) external hard drives from the master hard drive, for use in production.

C.7.2.2 The contractor shall provide the following items to support duplicating CID-2 external hard drives during production:

14 41

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

- A4 CID2 Master Hard Drive

- Laptop with CDS installer SW loaded

- Apricorn Secure Hard Drive

- Instructions for extracting the Cross Domain Software (CDS SW) for loading onto the CID2 internal hard drive.

- Instructions for extracting the Black Virtual Machine Software (VM SW) for loading onto the CID2 External Hard Drive

C.8 Vehicle Induction

C.8.1 The Government will provide vehicles for induction at Red River Army Depot (RRAD) as follows:

C.8.1.1 Vehicles will be provided on or before the dates specified in the induction schedule provided under each order

C.8.1.2 Vehicles will be configured to the Modification Work Order (MWO) baseline per Attachment 0007, ECP2 MWO Baseline.

C.8.1.2.1 Vehicles inducted with M2 Bradley Common Hulls or M3-based BFIST hulls will not be converted to M2 hulls; these hulls will be accepted as configuration in / configuration out.

C.8.1.3 Vehicles may have engines and transmissions with defects and may be inoperable.

C.8.1.4 All inducted vehicles will be complete. The definition of complete means that all parts are provide with the inducted vehicle as determined by BAE Systems inspection completed on seed vehicles at receipt. The identification of missing parts may not be immediately identifiable at induction and may be discovered throughout the production process All inspections and equipment conditions recorded on the DA 2404 form will have been completed and determined in accordance with in the latest revisions of IETM 9-2350-408-23&P, M2A3 IFV ODS, SA and 9-2350-439-23&P M7A3 BFIST SA w FS3, to determine vehicle condition prior to induction.