W56HZV16R0188-0002.pdf
PDF 141 KB Posted
- Attached to
- Bradley A4 ECP2 Production Federal contract opportunity
- Solicitation number
- W56HZV16R0188
About this file
W56HZV-16-R-0188 Amd 02
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| W56HZV16R0188-0003.pdf | ||
| W56HZV16R0188_AMD_0001_Final.pdf | ||
| W56HZV16R0188.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
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)
0002 2017APR19
W56HZV
U.S. ARMY CONTRACTING COMMAND
WARREN, MICHIGAN 48397-5000
AMY HAHKA
EMAIL: AMY.K.HAHKA.CIV@MAIL.MIL
W56HZV-16-R-0188
2016DEC06
X
X
/SIGNED/
2 signed
SEE SECOND PAGE FOR DESCRIPTION
1 34
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: AMY HAHKA
Buyer Office Symbol/Telephone Number: CCTA-AHL-A/(586)282-3738
Type of Contract 1: Fixed Price Incentive (Cost Based)
Kind of Contract: Supply Contracts and Priced Orders
*** End of Narrative A0000 *** h 1. The purpose of Amendment 0002 to Solicitation W56HZV-16-R-0188 is to make the following revisions/additions/deletions:
2. Section B:
a. The following CLINs are updated with revised quantities and delivery schedules.
CLIN 0001AA
CLIN 0001AB
CLIN 0001AC
b. CLIN 3001AA is revised to remove reference to Spares Acquisition Integrated with Production (SAIP).
c. CLIN 3001AB is added for Base Year - SAIP Spares
3. Section C:
a. Section C, Narrative C0001, Scope of Work is hereby revised
4. Section E:
a. Section E, Narrative E0001, is hereby revised
5. Section F:
a. Section F, Delivery Schedules and Quantities are revised.
6. Section H:
a. Section H is revised to incorporate revised CLIN quantities.
b. CLIN numbers are revised.
c. H.1.2 Option Year Two (Third Production Year) is hereby removed.
7. Section J
a. CDRL A029 - The Title and Subtitle have been updated
b. The following Attachments are hereby revised:
Attachment 0001 Government Furnished Information
Attachment 0002 A4 Induction Delivery Schedule
Attachment 0004 Cost and Software Data Reporting Plan
Attachment 0007 MWO Baseline
Attachment 0018 ASL and SAIP List
Attachment 0019 STTE List
Attachment 0022 GFM Disposition List
Attachment 0023 GFM Schedule
c. The following Attachment is hereby incorporated into the solicitation:
Attachment 0030 CREW-2 DUKE V3 Tech/Operator Manual
Attachment 0031 CREW DUKE V2 Dwgs and Interface Control Document
Attachment 0032 SSP List
8. All other terms and conditions, except those addressed in this Amendment, remain unchanged and in full force and effect.
2 34
W56HZV-16-R-0188 0002
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
*** END OF NARRATIVE A0002 ***
3 34
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
SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS
0001 BRADLEY M2A3 TO M2A4
0001AA BRADLEY M2A3 TO M2A4 123 EA $ $ _____________________ ______________ __________________
COMMODITY NAME: BRADLEY M2A3 TO M2A4
CLIN CONTRACT TYPE:
Fixed Price Incentive (Cost Based)
Packaging and Marking _____________________
Inspection and Acceptance _________________________
INSPECTION: Origin ACCEPTANCE: Origin
Deliveries or Performance _________________________
DOC SUPPL
REL CD MILSTRIP ADDR SIG CD MARK FOR TP CD ______ ________ ______ ______ ________ _____
DEL REL CD QUANTITY DEL DATE __________ ______________ ___________
001 4 31-JAN-2019
002 12 28-FEB-2019
003 12 31-MAR-2019
004 12 30-APR-2019
005 12 31-MAY-2019
006 12 30-JUN-2019
007 12 31-JUL-2019
008 12 31-AUG-2019
009 13 30-SEP-2019
010 13 31-OCT-2019
011 9 30-NOV-2019
FOB POINT: Origin
SHIP TO:
(Y00000) SHIPPING INSTRUCTIONS FOR CONSIGNEE
(SHIP-TO) WILL BE FURNISHED PRIOR
TO THE SCHEDULED DELIVERY DATE FOR
ITEMS REQUIRED UNDER THIS
REQUISITION.
4 34
Page of
Name of Offeror or Contractor:
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
Reference No. of Document Being Continued
MOD/AMD
0001AB BRADLEY A3 BFIST TO M7A4 8 EA $ $ ________________________ ______________ __________________
COMMODITY NAME: BRADLEY A3 BFIST TO M7A4
CLIN CONTRACT TYPE:
Fixed Price Incentive (Cost Based)
Packaging and Marking _____________________
Inspection and Acceptance _________________________
INSPECTION: Origin ACCEPTANCE: Origin
Deliveries or Performance _________________________
DOC SUPPL
REL CD MILSTRIP ADDR SIG CD MARK FOR TP CD ______ ________ ______ ______ ________ _____
DEL REL CD QUANTITY DEL DATE __________ ______________ ___________
001 8 31-JAN-2019
002 DELETED
FOB POINT: Origin
SHIP TO:
(Y00000) SHIPPING INSTRUCTIONS FOR CONSIGNEE
(SHIP-TO) WILL BE FURNISHED PRIOR
TO THE SCHEDULED DELIVERY DATE FOR
ITEMS REQUIRED UNDER THIS
REQUISITION.
0001AC BRADLEY M2A2 ODS-SA TO M2A4 ERI BASE 15 EA $ $ ____________________________________ ______________ __________________
COMMODITY NAME: BRADLEY M2A2 ODS-SA TO M2A4
CLIN CONTRACT TYPE:
Fixed Price Incentive (Cost Based)
Packaging and Marking _____________________
Inspection and Acceptance _________________________
INSPECTION: Origin ACCEPTANCE: Origin
Deliveries or Performance _________________________
DOC SUPPL
REL CD MILSTRIP ADDR SIG CD MARK FOR TP CD ______ ________ ______ ______ ________ _____
DEL REL CD QUANTITY DEL DATE __________ ______________ ___________
001 4 30-NOV-2019
002 11 31-DEC-2019
003 DELETED
5 34
Page of
Name of Offeror or Contractor:
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
Reference No. of Document Being Continued
MOD/AMD
FOB POINT: Origin
SHIP TO:
(Y00000) SHIPPING INSTRUCTIONS FOR CONSIGNEE
(SHIP-TO) WILL BE FURNISHED PRIOR
TO THE SCHEDULED DELIVERY DATE FOR
ITEMS REQUIRED UNDER THIS
REQUISITION.
3001 ASL - BASE YEAR
3001AA BASE YEAR - AUTHORIZED STOCKAGE LIST 1 EA $ $ ____________________________________ ______________ __________________
COMMODITY NAME: ASL - BASE YEAR
CLIN CONTRACT TYPE:
Firm Fixed Price
Packaging and Marking _____________________
Inspection and Acceptance _________________________
INSPECTION: Origin ACCEPTANCE: Origin
3001AB BASE YEAR - SPARES ACQ INTEGRATED W/ PRODUCTION 1 EA $ $ _______________________________________________ ______________ __________________
COMMODITY NAME: SAIP - BASE YEAR
CLIN CONTRACT TYPE:
Firm Fixed Price
Reference Section C: DESCRIPTION/SPECIFICATIONS/WORK
STATEMENT for a description of the Scope of Work
(SOW) in C.12.
(End of narrative C001)
Packaging and Marking _____________________
Reference Section D for Packaging and Marking details.
(End of narrative D001)
Inspection and Acceptance _________________________
INSPECTION: Origin ACCEPTANCE: Origin
Deliveries or Performance _________________________
DOC SUPPL
6 34
Page of
Name of Offeror or Contractor:
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
Reference No. of Document Being Continued
MOD/AMD
REL CD MILSTRIP ADDR SIG CD MARK FOR TP CD ______ ________ ______ ______ ________ _____
DEL REL CD QUANTITY DEL DATE __________ ______________ ___________
001 1 30-SEP-2019
FOB POINT: Origin
SHIP TO:
(Y00000) SHIPPING INSTRUCTIONS FOR CONSIGNEE
(SHIP-TO) WILL BE FURNISHED PRIOR
TO THE SCHEDULED DELIVERY DATE FOR
ITEMS REQUIRED UNDER THIS
REQUISITION.
4001 FY 17 STTE
4001AA FY17 SPECIAL TOOLS AND TEST EQUIPMENT 1 EA $ $ _____________________________________ ______________ __________________
COMMODITY NAME: FY 17 STTE
CLIN CONTRACT TYPE:
Firm Fixed Price
Packaging and Marking _____________________
Inspection and Acceptance _________________________
INSPECTION: Origin ACCEPTANCE: Origin
7 34
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT
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. The contractor shall produce M7A4 vehicles from A3 Bradley Fire Support Team (BFIST) with Fire Support Sensor System (FS3) and
M7 BFIST-SA source vehicles. The contractor shall provide Authorized Stockage List (ASL) Spares and Spares Acquired in Production
(SAIP). The vehicles and spares shall be delivered in accordance with the delivery schedule in Section F. Converted and RESET vehicles shall meet performance specification 19207-12572339 as validated by completion of the FIR
(QF87T0196-M2A4_X0_) for M2A4 and FIR
(QF87T0198-M7A4_X0_) for M7A4 converted vehicles.
C.1.1 Data Deliverables are listed in Section J. Unless otherwise specified in the CDRL, contractor format is acceptable. The contractor shall use an editable format for all data deliverables.
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.2 Agendas, Presentation Materials and Minutes. The contractor shall deliver the agenda (CDRL A001), briefing materials (CDRL A002), and minutes (CDRL A003) of all meetings between the contractor and Government personnel to the Government. The minutes shall reflect the parties joint review, the identification of any major problem areas, the plans for their resolution with a projected timeline for resolution, and the assessment of the impact on the contract requirements.
C.2.3 Production Meeting. The contractor shall conduct a weekly Production meeting to provide the Government with status on the production of A4 vehicles and deliverables.
C.2.4 Start of Work Meeting. The contractor shall host a Start of Work meeting at the BAE York facility within thirty (30) calendar 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 thirty (30) calendar days in advance of the event. The contractor shall deliver presentation materials in accordance with CDRL A002. The contractor shall deliver meeting minutes in accordance with CDRL A003.
C.2.5 Production Readiness Review (PRR). The Government will conduct a PRR within six (6) months of contract award. The contractor shall host the PRR at the BAE York facility and assist in the development of the PRR by completing the PRR Checklist (Attachment 0003) and having available for Government review at the PRR. The contractor shall deliver an agenda in accordance with CDRL A001. The contractor shall deliver presentation materials in accordance with CDRL A002. The contractor shall deliver meeting minutes in accordance with CDRL A003 which will include corrective action plans and schedules. The contractor shall establish the Manufacturing Readiness
Levels (MRLs) for A4 production and have available for the Government to review at the PRR.
C.3 Program Management
C.3.1 The contractor shall conduct monthly meetings with the government to analyze the contractors progress to date.
C.3.2 Integrated Baseline Review (IBR). The contractor shall conduct a joint assessment, with the Government, of the Performance
Measurement Baseline to verify the baselines realism, accuracy, and technical content. The IBR shall take place at the contractors facility within 180 calendar days of contract award. The contractor shall provide access to all pertinent records and data requested by the Contracting Officer or duly authorized representative to adequately prepare for the IBR to include the detailed time-phased
Performance Management Baseline (PMB), Responsibility Assignment Matrix, Control Account Authorizations, and Work Package Authorizations and permit Government surveillance to ensure Earned Value Management System (EVMS) compliance. The PMB shall be detail-planned to the
MIL-STD-881-C, Level 3. Two weeks prior to the IBR, the contractor shall provide the Government Control Account Managers (CAM) with a read-ahead copy of the IBR topics to be covered at the IBR, focusing on its assigned Work Breakdown Structure (WBS) elements.
C.3.2.1 A 12-month rolling wave detailed Integrated Master Schedule (IMS) plan shall be presented at the initial IBR. The Government has the right to accept or reject the detailed IMS plan (CDRL A004). After the initial IBR, the contractor shall continue to provide a detailed IMS plan at a minimum of every 6 months in a Detail Plan Baseline Review (CDRL A004).
C.3.2.2 The contractor shall facilitate a 1-day joint IBR training at the contractors facility in Sterling Heights, Michigan at least 30 calendar days prior to the IBR. The contractors CAM and EVM employee(s) for this program shall attend the event. The contractor shall provide training material for up to thirty (30) Government employees. Training material shall cover the purpose, outcome, and goals of an IBR. Training material shall include sample documentation and demonstrations to include detailed integrated master schedule, Work
Breakdown Structure and dictionary, Work Package Authorization (WPA), Control Account Authorization (CAA), Control Account Plan (CAP) and Earned Value Criteria, dollarized responsibility assignment matrix and time phased performance measurement baseline (PMB) by work package.
8 34
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
C.3.3 Program Performance Management. The contractor shall meet all program cost, schedule, supportability, and technical requirements set forth in the contract and its related documents. The contractor shall monitor: (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). The contractor shall prepare and deliver an Integrated Program Management Report (IPMR) in accordance with CDRL A004. The contractor shall prepare the IPMR/IMP in accordance with DI-MGMT-81861, the DoD Integrated Master Plan and Integrated Master Schedule Preparation and Use
Guide, and MIL-STD-881C except where modified by the CDRL.
Format 1: Report date at Level 3 for Format 1. Additional reporting levels may be required for high-risk or high-dollar elements (final reporting levels to be discussed and agreed upon).
Format 2: Report date at Level 3 for Format 2. Actual level will be dependent on the contractors Organizational Breakdown Structure
(OBS), but will not generally be below level 3, unless additional reporting levels are required for high-risk, high-dollar, or high variance elements (final reporting levels to be discussed and agreed upon).
Format 3: The PMB and supporting WBS detail shall be included in a monthly IPMR submission (e.g., Winsight file).
Format 4: Report staffing data to the level agreed to in Format 2. Reporting will be based on the contractors ETC and will report on
Full Time Equivalents (FTE).
Format 5: Variance Analysis is required for the following Format 1 variances; current period cost or schedule variances exceeding +/-
$25k and 10%, cumulative cost or schedule variances exceeding +/- $50k and 10%, and variances at completion exceeding +/-$100K and 10%.
Explanations of schedule variances and the impact to the contract shall be performed in parallel with the monthly schedule analysis called out by the IPMR/IMP CDRL. In addition, the monthly Budget Change Request Log shall be included as an attachment to Format 5.
The contractor shall use COBRA as a reporting tool. Backup files shall be submitted in the native Deltek COBRA format including all auxiliary files (e.g., breakdown structures, code files, calendars, etc.).
Format 6: All monthly submissions will include a written schedule analysis to identify, document, and communicate changes of one (1) working day or greater to: The Project Critical Path, the next major milestone, and/or the Near Critical Path task/activity actual start and/or actual finish date variances from submission to submission. Work around and/or recovery schedules/plans, and associated impacts due to program changes shall also be provided. The schedule narrative shall address progress to date and discuss any significant schedule changes (i.e., added/deleted tasks, any significant logic revisions, and any/all programmatic schedule assumption change etc.).
The first narrative submission is to provide the Basis and Assumptions (B&A) of the IMS. The B&A shall outline the major program milestones and document all associated programmatic assumptions that were utilized in the development of the baseline plan. In addition to the monthly IMS, the contractor shall submit Detailed Work Schedules, when required and in accordance with the CDRL.
Detailed Schedules. If the contractors IMS does not include Level 3 Contract WBS elements, then the contractor shall prepare to provide, in addition to the IMS, Detailed Work Schedules necessary to track discrete tasks/activities at the Level 3 detail at the Governments request. The Detailed Work Schedules will be an integrated, logical networked-based schedule. The schedule shall have a numbering system that provides traceability to the IMP (if applicable) and Scope of Work. It shall contain contractual milestones, descriptions, display summary, intermediate, and detailed activities, and periodic analysis of progress to date. It shall include fields and data that enable the user to access the information by product, process, function, or organizational lines.
Schedule Risk Assessment. A schedule risk assessment predicts the probability of project completion by contractual dates. Three-point estimates shall be developed for remaining durations of remaining tasks/activities that meet any of the following criteria: (1) critical path tasks/activities, (2) near-critical path tasks/activities (3) high risk tasks/activities, as defined by the Government or contractor. These estimates include the most likely, best case, and worst case durations. They are used by the contractor to perform a probability analysis of key contract completion dates. The criteria for estimated best and worst case durations shall be applied consistently across the entire schedule and documented in the contractors schedule notes and management plan. The contractor shall prepare and submit SRAs and be prepared to participate in quarterly Schedule Risk Analysis (SRA) to identify and quantify milestone/event and task/activity level schedule risk. The contractor shall report optimistic, pessimistic, and most likely remaining durations for the designated (in this paragraph) Critical Path and Near Critical Path task/activity schedule risk. The contractor may employ tailored criteria for estimated best and worse durations and shall document these criteria in schedule notes and in the IMS Basis and Assumptions. The rationale used to establish the remaining durations should be documented. The SRA will be performed on the Program
Critical Path, the Critical Path, and Near Critical Paths.
Near Critical Path is defined to be the second longest path to each of the designated milestones.
Format 7: This format shall be submitted at the lowest level of the WBS, using the DoD- approved Time-Phased Cost XML Guideline and
9 34
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
schema. Format 7 shall be submitted in whole dollar units (no decimals) in accordance with the DoD-approved XML schema located in the
EVM Central Repository (EVM-CR) (http://www.acq.osd.mil/evm/). Time-phased cost projection shall consist of historical, time-phased
BCWS, BCWP, ACWP, plus future time-phased Estimate to Complete (ETC) values for all WBS elements. The total of the time-phased costs must reconcile with Format 1 values for the same reporting month.
C.3.3.1 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. The contractor shall initiate and complete corrective action for all inconsistencies reported (CDRL A004).
C.3.4 Incorporation of Baseline Changes. Upon Procuring Contracting Officer approval, new work shall be included in the contractors distributed budget with appropriate performance measurement techniques included in the work package.
C.3.4.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 Assistant Product Manager (APM).
C.3.5 Integrated Program Management Report (IPMR) Integrated Master Plan (IMP). The IPMR is a contractually required monthly report containing original baseline, performance data (earned value), and actual costs. From these three data points, cost and schedule variances can be determined and analyzed. Per the DoD 5000.02, EVM Policy Guidance, all 7 formats of the IPMR are required for contracts exceeding $50M: format 1 (Work Breakdown Structure); format 2 (Organizational Breakdown Structure); format 3 (Baseline); format 4
(Staffing); format 5 (Variance Analysis); format 6 (Integrated Master Schedule); and format 7 (Electronic History and Forecast File).
C.3.5.1 The IPMR shall be developed and submitted at Level 3 of the Contractor Work Breakdown Structure (CWBS), in accordance with CDRL
A004. Reporting at lower levels may be specified for high cost, high risk and/or high variance items at no additional cost to the
Government and may be required until the contract is complete. The Government and contractor shall periodically review and adjust the
Contractors Work Breakdown Structure (CWBS) reporting levels as necessary to ensure the contractor continues to provide appropriate visibility without providing excessive information. Thresholds for reporting Format 3 Variance Analysis shall also be periodically reviewed and adjusted as necessary by the Government. Format 6 shall be developed and maintained in an IMP. The IMP is an event based plan consisting of a hierarchy of program events, with each event being supporting 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 develop and maintain an IMS by logically networking detailed program activities. The schedule shall be consistent with the 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 Performance Measurement Baseline shall be consistent. The IMS shall be resourced loaded and clearly identify critical path activities and reflect those risks identified and documented in the contractors risk management plan. All IMS/IMP monthly submissions shall include written schedule delays (CDRL A004).
C.3.5.2 The contractor shall include issues identified by its subcontractors in the identification, tracking and management listing identified in the paragraph above.
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, the Integrated Program Management Report (CDRL A004), the contractors own documented
System Description and DFARs clauses 252.234-7001, 252.234-7002, 252.234-7003, and 252.7004. The contractor shall use an EVMS that has been formally reviewed and determined by the Defense Contract Management Agency (DCMA) to be in compliance with the EVMS guidelines in
ANSI/EIA-748. EVM shall be used as a tool to identify and track program risks, manage cost, schedule, and technical performance.
C.3.7 Application to Subcontractors. The contractor shall flow-down EVMS requirements to subcontractors exceeding $20,000,000. 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. 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.8 Contractor 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 IPMR when these documents are submitted in the same month. The contractor shall provide a reconciliation of the CFSR with the IPMR as an addendum to the IPMR.
C.3.9 Cost and Software Data Reporting (CSDR) Readiness Review. The Contractor shall conduct a post award conference within 45 calendar days after contract award to include a discussion of the contractors standard cost and software data reporting (CSDR) process that satisfies the guidelines contained in the DoD 5000.04-M-1, CSDR Manual, and the requirements in the Government-approved CSDR plan for the contract, DD Form 2794, and related Resource Distribution Table.
C.3.10 Contract Work Breakdown Structure (CWBS): The Contractor shall develop and maintain the CWBS and CWBS Dictionary in accordance with CDRL A006 for Cost and Software Data Reporting (CSDR) and Earned Value Management (EVM) purposes. The contractor shall extend the
CWBS down to the appropriate level required to provide adequate internal management, surveillance, and performance measurement. The contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule, and
10 34
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
technical performance status to the Government. The contractor shall update the CWBS and CWBS Dictionary throughout the life of the contract, in accordance with CDRL A006. The definitions provided by the contractor for each Level 3 WBS element must be traceable to the contract Scope of Work (SOW). Changes to the CWBS or associated definitions, at all reporting levels, require approval of the PCO prior to implementation.
C.3.10.1 Part I CWBS index. The contractor shall provide a matrix identifying the contract line item and SOW to the WBS elements. Per the DID, enter CWBS Code, Element Level and CWBS Name (CDRL A006).
C.3.10.2 The CWBS shall be reported by the contractor at Level 3. Additional reporting levels may be required for high risk, high dollar, or high variance elements (final reporting levels to be discussed and agreed upon) (CDRL A006).
C.3.10.3 Part II CWBS Dictionary. The Dictionary shall provide a description of the CWBS element and contractor tasks essential to fulfill the element description (at a reporting level consistent with DoD 5000.03 EVM Policy Guidance Format 1). The task description shall include summary identification of the functional/organizational resources to be applied (CDRL A006).
C.3.11 Cost Software Data Reporting (CSDR). The Contractor shall systematically collect and report to the Government actual contract costs in the following reports:
Title CDRL
Cost Summary Data Report A008
Functional Cost-Hour Report A009
Contractor Business Data Report A011
Contractor reports shall be prepared in accordance with the instructions contained in the above CDRLs and the OSD Deputy Director, Cost
Assessment (DDCA)-approved contract CSDR Plan (Attachment 0004).
C.3.11.1 Subcontractor Reporting. The contractor shall flow down CSDR requirements contained in their contracts to all subcontractors who meet the reporting thresholds specified in DoDI 5000.02. This includes requiring subcontractors to electronically report directly to the DCARC using the CSDR Submit-Review System. The contractor shall be required to work with the Cost Working Integrated Production Team
(CWIPT) and all appropriate subcontractors to prepare separate subcontract CSDR plans for submission to the DCARC for DDCA approval.
C3.11.2 Priced Indentured Bill of Material (BOM). The Contractor shall develop, maintain, and deliver a priced indentured BOM for both
Bradley M2A4 and M7A4 vehicles in accordance with CDRL A023. The indentured BOM shall include: CWBS Element and Structure Level of
Assembly (Hierarchy); Unit of Measure (each, pounds, inches, or other); Quantity or Value (count, weight, length, or other);
Nomenclature; Part Number (Contractor or Vendor as applicable); National Stock Number (NSN); Cost Source (quote, purchase order, estimate, or other); Make or Buy; Cost; Extended Cost; Vendor. The contractor shall supplement the indentured BOM with an analysis that provides traceability and linkage to the date submitted in the Cost Data Summary Report (CDRL A008) and Functional Cost-Hour Report
(CDRL A009). 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 develop and submit a Manufacturing Plan (CDRL A012) 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 develop 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 develop and submit all facility and facilitization plans to sustain production. The plans shall be broken out by contractor facility. The plans shall include plant and facility layout, and assembly tooling installation plans.
C.4.1.3 The contractor shall develop and submit 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 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). The contractor shall investigate issues discovered under this contract during production to determine if the issue is due to design or production. All issues due to production shall be worked and resolved under this contract. Issues due to design shall be transferred to the Bradley STS contract for resolution.
11 34
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
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.
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 A013). 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 these requirements to suppliers and 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 A013).
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). Changes to any Government controlled data in production shall be accomplished through a formal Engineering Change Proposal (ECP) process reflected in the contractors Configuration Management Plan. The contractor shall deliver ECP packages CDRL A014 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. Administrative changes shall be submitted as minor (Class 2) changes.
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 Government classification concurrence of any Major (Class I) and
Minor (Class II) ECPs. DCMA will be the designated representative for the concurrence of classification for Major (Class I) or Minor
(Class II) 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. All ECPs due to production issues shall be worked and resolved under this contract. ECPs due to design issues shall be transferred to another contract for resolution.
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 for the Configuration Item (CI) once the baseline has been approved/accepted by the PdM-BFV CCB.
C.5.1.3.3 Engineering Change Priorities. The Government uses the engineering change priority of emergency, urgent or routine to determine the time frame in which the ECP is to be- reviewed, evaluated, ordered and implemented. The contractor shall not assign an
Emergency or Urgent Engineering Change Priority to a Minor (Class II) ECP. The contractor shall use content in DD Form 1692, block 6 to determine Engineering Change Priority. The Government reserves the right to accept or reject and make final determination of the
Engineering Change Priority.
C.5.1.4 Engineering Release Record (ERR). The contractor shall deliver an Engineering Release Record (ERR) using DD Form 2617 in accordance with CDRL A015 for every ECP. The ERR package is defined as the ERR form submitted concurrently with the new and revised PCI for initial release or change release. The contractor shall prepare and submit an ERR Package for the release of each initial or changed product baseline IAW CDRL A015. The contractor shall use DD Form 2617 for all ERRs. The contractor shall prevent premature release of
PCI until the Government has approved the ERR. The ERR shall provide complete traceability of all PCI to the individual approved engineering change. ERRs must be approved by the Government before acceptance by the Government and all ERR deliverable data shall include the approved metadata attributes.
C.5.1.5 Request for Variance (RFV). The contractor shall deliver a Request for Variance in accordance with CDRL A016 anytime it is necessary to temporarily depart from specified technical baseline and request for variance shall be identified, documented, coordinated, evaluated and dispositioned with the Government before it can be applied to the baseline. The contractor shall use DD Form 1694 for all
RFVs. The contractor shall obtain Governments approval on any product that will be produced or has been produced as defective or nonconforming before delivery to the Government. If the Government determines the variance would be permanently acceptable, then the
12 34
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
contractor shall submit an ECP IAW A014 and an ERR IAW A015. Upon RFV disposition, the Contractor shall document in the Configuration
Status Accounting (CSA) system: RFV description, which defines the Non Conformance Material (NCM) addressed by the RFV is impacted including the impact to any additional product/part, the RFV stated corrective action to prevent recurrence, and the corrective action taken/accomplished by the contractor/Supplier to prevent RFV reoccurrence.
C.5.1.5.1 Recurring Variances. The contractor shall evaluate recurring variances for submittal of an ECP IAW CDRL A014 and an ERR IAW
CDRL A015. The Government reserves the right to request an ECP for all recurring variances.
C.5.1.5.2 Classifications of Variances. The DD Form 1694 will be prepared by the contractor who will assign a Critical/Major or Minor classification to an RFV. The contractor shall submit to the PdM Bradley CCB for final decision, any classification disagreements between the contractor and the Governments designated representative. The contractor shall provide an implementation timeline for corrective actions of all Critical and Major classified RFVs as part of RFV submittal to the Government.
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 Configuration Control Board (CCB). The contractor shall participate as a non-voting member within the Government Configuration
Control Board process to assess the impact of proposed ECPs and RFVs to vehicles listed under this contract.
C.5.3 ECP Co-User Requirements. The contractor shall coordinate change concurrence with the Design Authority of any PCI data.
C.5.4 Physical Configuration Audit (PCA). The Government will conduct a PCA for Bradley M2A4 and M7A4 unique items only as part of validating vehicle configuration during the production process and after initial vehicle delivery. The contractor shall facilitate the conduct of this PCA. EIA-649-1 shall be used as guidance.
C.5.4.1 The contractor shall develop a detailed PCA Plan for Bradley ECP2 unique items and submit for Government approval, IAW CDRL
A036. EIA-649-1 shall be used as guidance.
C.5.4.1.1 The Government will schedule the audit and notify the contractor not less than 30 calendar days prior to the conducting of any audit. The contractor shall provide an agenda IAW CDRL A001.
C.5.4.1.2 The PCA(s) shall be performed on the system selected by the Government. The Government may choose any drawing characteristics deemed necessary to verify during the PCA. The Government will compare selected vehicles against the design documentation (As Built
Configuration List (ABCL)) or Indentured Bill of Materials (IBOM) and TDP to assure the vehicle conforms to the documentation. Any findings that require corrective actions as a result of the PCA shall be the responsibility of the contractor.
C.5.4.1.3 All parts, assemblies, and subassemblies offered for PCA shall be produced using tooling, processing and inspection procedures utilized during production. Quality Assurance Provisions shall be audited to assure compatibility with the drawings.
C.5.4.1.4 Physical Configuration Audit Summary Report. The contractor shall submit a PCA Summary Report in accordance with CDRL A017 after the PCA to identify discrepancies found between hardware and contract requirements.
C.5.4.1.4.1 The contractor shall correct the errors and present corrective action through an ECP to the Government before PCA Summary
Report approval is considered. ECPs that provide PCA corrective actions shall be submitted to the Government for approval within 90 calendar days of the PCA.
C.5.4.1.4.2 The Government reserves the right to stop acceptance of all systems if the PCA is not completed within the schedule specified in the approved PCA plan until such time as the PCA is completed and any corrective actions resolved.
C.5.4.2 The contractor shall provide support for pre-audit, PCA, and post-audit activities. Support is defined in the following list.
The contractor shall have all resources and materials in place for the PCA on the scheduled PCA start date and time. The contractor shall:
a. Identify support personnel, establish and provide teams to conduct the PCA
b. Provide a safe, indoor physical location at the production facility for the Government to witness the PCA, as agreed upon between the Government and the contractor. Production or other shop floor activities shall not interfere with the audit. Indoor facility shall be climate controlled to maintain ambient conditions between 65 and 80 degrees Fahrenheit
c. Provide appropriate safety equipment such as safety glasses, hearing protection, etc.
d. Obtain all parts for the audit, deliver to the audit location, and return parts to their proper location after audit completion
13 34
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
e. Have parts to be audited readily available, disassembled, and in the audit location
f. Participate with the Government in kick-off, audit activities, and close-out meetings, adhere to ground rules, daily schedule, audit and close-out actions
g. Provide access to a copy machine for USG and contractor support personnel to utilize during the PCA
h. Provide adequate outlets and network connectivity for plugging in laptops
i. Provide access to CAD workstations, software, files, libraries, etc., as needed, for opening, viewing and measuring CAD models
j. Obtain and have available for Government review the following:
i. legible hard copies of 2D drawings, pre-printed for each part to be audited
ii. PCA Plan
iii. all variances and engineering changes and status of each
iv. parts manuals
v. part shortages list
vi. company manuals, specifications, standards
k. Provide appropriate, calibrated tools for use in verifying part dimensions
C.6 Technical Data
C.6.1 Engineering Drawings and Specifications. For any new ECPs developed under this contract, the contractor shall prepare and deliver
Product Drawings in accordance with MIL-STD-31000 (CDRL A018), and Technical Data Packages in accordance with CDRL A019 and the TDP
Option Sheet (Attachment 0006). Product drawings shall be complete to provide the information necessary to enable the Government to competitively procure, provision, and catalog an item identical to the original item, without additional engineering effort.
C.6.1.1 Revised Product Data. For any new 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.2 Specifications. For any new 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 A020). All new data must be submitted to the
Government for review/approval before an ERR is accepted.
C.6.2 Interface Control Documents (ICD). For any new ECPs developed under this contract, the contractor shall coordinate and evaluate 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 A021.
C.7 Software
C.7.1 The contractor shall purchase the following software licenses:
Software License________________ Vendor ______ License Type____________ No. of Copies_____________ SW Resident___________
(per copy)__________ per vehicle___________ Line_____ R_ eplaceable___________ Unit (LRU)__________
VxWorks OS WindRiver run time 1 CPU
Linux OS (BAE
Application, Black & Red) Redhat run time 4 CID (SLD/CTD)
TEE General Dynamic run time 2 CID
(SLD/CTD)
Crossing GuardXD General Dynamic run time 2 CID (SLD/CTD)
Ballistic Solution SW (BSS) GDC run time 1 CPU
14 34
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
C.7.2 Disk Duplication Needs_____________________________
C.7.2.1 The contractor shall perform disk duplication of CID2 hard drives from the master hard drive.
C.7.2.2 The contractor shall provide the following items to support duplicating CID2 hard drives during production:
\'b7 A4 CID2 Master Hard Drive
\'b7 Cross Domain Solution (CDS) Installer Disk
C.8 Vehicle Induction
C.8.1 The Government will provide vehicles for induction at Red River Army Depot (RRAD) in serviceable condition IAW Technical Manual
(TM) 9-2350-408-13&P on or before the dates specified in the schedule at Attachment 0002. The Government will provide vehicles configured to the Modification Work Order (MWO) baseline per Attachment 0007, ECP2 MWO Baseline.
C.8.2 The contractor shall ship vehicles between test site(s) and manufacturing site(s). The contractor shall arrange shipment to final destination site(s), including PVT/FPT test sites, per the Delivery Schedule in Section F.
C.8.3 Over and Above Requirements
C.8.3.1 Pursuant to DFARS 252.217-7028, the Government may modify these procedures as appropriate.
C.8.3.1.1 When requested by the Government, or when a need is identified by the contractor, the contractor shall submit a work request, in contractor format, to the ACO and the QAR, with a copy to the PM-AFV engineer, the PM-AFV Procurement Analyst and the PCO. At a minimum, the request shall include the following:
a. A description of the work to be performed;
b. Identification of the proposed repair procedure;
c. Replacement parts required (excludes GFP for pricing purposes only);
d. Estimated labor hours…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .