Solic Amend W56HZV-19-R-0118 0003.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

Firm Fixed Price

0003 2021MAR12

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

TYRONE MCCULLOM

EMAIL: TYRONE.MCCULLOM.CIV@MAIL.MIL

W56HZV-19-R-0118

2021FEB17

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 54

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: TYRONE MCCULLOM

Buyer Office Symbol/Telephone Number: CCTA-HCP-C/(586)282-7974

Type of Contract 1: Firm Fixed Price

Kind of Contract: System Acquisition Contracts

*** End of Narrative A0000 ***

The purpose of Amendment 0003 to Solicitation W56HZV-19-R-0118 is the following:

1. Revise Section J, List of Attachments, as follows:

A. Revise Attachment 0001, AT-PRF-0001 Type I FOATC PD

From: Attachment 0001, AT-PRF-0001 (Version 1.4) dated 03 February 2021

To: Attachment 0001, AT-PRF-0001 (Version 1.5) dated 01 March 2021

B. Add Attachment 0046, Army Built CBM Data (ABCD) Format.

2. Revise Scope of Work, Section C.2.7.2 PPMx SYSTEM, as follows:

From:

The contractor shall equip the Type I FOATC with the contractors PPMx system that consists of encrypted data storage and transfer through a cellular based device. The contractor's PPMx system shall have a secure data tunnel between the cellular provider and the contractor's corporation. The purpose of the contractor's PPMx system is to proactively plan maintenance actions and improve availability and safety.

To:

The contractor shall equip the Type I FOATC with the contractors PPMx system that consists of encrypted data storage and transfer through a cellular based device. The contractor's PPMx system shall have a secure data tunnel between the cellular provider and the contractor's corporation. The purpose of the contractor's PPMx system is to proactively plan maintenance actions and improve availability and safety. Encryption shall be in accordance with the current Federal Information Processing Standard (FIPS) 140-2.

3. Revise Scope of Work, Section C.2.7.3 PPMx DATA STORAGE, as follows:

From:

The Telematics module on the Type I FOATC shall use a cellular data transfer process or onboard storage depending on the network availability. The amount or the type of data transmitted shall be tailored based on the communication network availability. If there is no network connection near the Type I FOATC, the onboard data storage shall be retrieved by a DoD personnel and loaded through a secured portal to the contractors cloud. The data housed in the contractors cloud shall be cleaned, standardized, and stored in Army

Built CBM (Condition Based Maintenance) Data (ABCD) format for efficient data processing.

To:

The Telematics module on the Type I FOATC shall use a cellular data transfer process or onboard storage depending on the network availability. The amount or the type of data transmitted shall be tailored based on the communication network availability. If there is no network connection near the Type I FOATC, the onboard data storage shall be retrieved by a DoD personnel and loaded through a secured portal to the contractors cloud. The data housed in the contractors cloud shall be cleaned, standardized, and stored in Army

Built CBM (Condition Based Maintenance) Data (ABCD) format for efficient data processing. (Attachment 0046 - Army Built CBM Data (ABCD)

Format).

4. Revise Scope of Work, Section C.12.5.2 as follows:

From:

FSRs may be called up in one of two ways:

a. A CONUS Man-Day is 8 hours and the representative is to work no more than 40 hours per week.

2 54

W56HZV-19-R-0118

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

b. An OCONUS non-contingency Man-Day is 10 hours a day, regardless of the day of the week.

To:

FSRs may be called up in one of three ways:

a. A CONUS Man-Day is 8 hours and the representative is to work no more than 40 hours per week.

b. An OCONUS non-contingency Man-Day is 10 hours a day, regardless of the day of the week.

c. An OCONUS contingency Man-Day is 12 hours a day, typically six days per week but the maximum of 72 hours per week may be spread over seven days if necessary to support mission requirements.

5. Revise Scope of Work, Section C.15 DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES MANAGEMENT PROGRAM, as follows:

From:

The contractor shall establish and maintain a proactive Diminishing Manufacturing Sources and Material Shortages (DMSMS) program for the

Type I FOATC. The DMSMS Management Plan shall document the processes used by the contractor to implement a proactive DMSMS Management

Process. The plan will enable the identification, forecasting and management of piece part obsolescence impacts and mitigations and identify how application of cross platform commonality can reduce DMSMS issues. The contractor shall be responsible for any redesign costs resulting from obsolescence during the period of performance and support the systems parts for 20 years.

To:

The contractor shall establish and maintain a proactive Diminishing Manufacturing Sources and Material Shortages (DMSMS) program for the

Type I FOATC. The DMSMS Management Plan shall document the processes used by the contractor to implement a proactive DMSMS Management

Process. The plan will enable the identification, forecasting and management of piece part obsolescence impacts and mitigations and identify how application of cross platform commonality can reduce DMSMS issues. The contractor shall be responsible for any redesign costs resulting from obsolescence during the period of performance. In addition, the contractor shall support systems parts for 20 years.

6. Delete Sections L.4.1.3.5, and L.4.1.3.6 as follows:

Section, L.4.1.3.5

From:

U.S. Highway. Provide analysis (which includes, at a minimum, the proposed solutions height, width, length, weight, and axle load) to substantiate the proposed Type I FOATC meets the United States (US) highway legal limits.

The design limitations are from Attachment 0040 - TEA Pamphlet 70-1 page 43-50:

Height: 162 inches

Width: 96 inches

Length: 480 inches

Weight: 80,000 lbs.

Axle load: 20,000 lbs. for single axle load; or 34,000 lbs. for tandem axle group load

To: (RESERVED)

Section, L.4.1.3.6

From:

NATO Highway. Provide analysis (which includes, at a minimum, the proposed solutions height, width, length, weight, and axle load) to substantiate the proposed Type I FOATC meets the North Atlantic Treaty Organization (NATO) highway legal limits.

The design limitations are from Attachment 0040 - TEA Pamphlet 70-1 page 43-50:

Height: 157.5 inches

Width: 98.4 inches

Length: 393.7 inches

Axle load: 22,046 lbs. for single axle load; or 35,274 lbs. for tandem axle group load

To: (RESERVED)

3 54

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Purchase Description (PD) is revised as follows:

FOATC1-1418: The Type I FOATC shall meet the United States (US) and North Atlantic Treaty Organization (NATO) highway legal limits with permits.

FOATC1-1683: This was included by error and is deleted from the PD.

7. Revise Section F, Deliveries or Performance, FAR Clause, 52.211-8, Time of Delivery, as follows:

From: Quantity Every 30 Days of 13 EA

To: Quantity Every 30 Days of up to 13 EA

8. Except as specifically noted herein, all other terms and conditions of this solicitation remain unchanged and in full force and effect.

*** END OF NARRATIVE A0004 ***

4 54

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.0 DEFINITIONS

For purposes of this contract, day is defined as a business day unless otherwise specified in accordance with (IAW) Federal Acquisition

Regulation (FAR) Subpart 2.1 Definitions. Typically these are the days between and including Monday to Friday and do not include

Federal holidays or weekends. Any paragraph within this Statement of Work that has days referencing work or a task to be completed shall be calculated as business days.

C.1 SYSTEM DESCRIPTION

The Type I FOATC shall perform IAW the Type I Family of All Terrain Cranes (FOATC) Purchase Description (PD) AT-PRF-0001 (Version 1.5), dated 01 March 2021. (Attachment 0001 Type I FOATC PD AT-PRF-0001)

C.1.1 HARDWARE DELIVERIES

The contractor shall manufacture and deliver a Type I FOATC meeting all technical requirements set forth in Attachment 0001 Type I

FOATC PD AT-PRF-0001 . Delivery Orders will specify the quantity, delivery dates, destinations, packaging requirements and required paint color (34094 - Green or 33446 - Tan IAW FED-STD-595). Deliveries shall be IAW FAR 52.211-8 Time of Delivery. (Attachment 0001

Type I FOATC PD AT-PRF-0001 )

C.1.2 BASIC ISSUE ITEMS

The contractor shall provide Basic Issue Items (BIIs) for each production Type I FOATC, unless otherwise specified in the delivery order. BII are the minimum essential items required to place the Type I FOATC in operation, to operate it, and to perform emergency repairs. BII is select operator tools, operator publications, and safety equipment (i.e. fire extinguishers) authorized for the Type I

FOATC. BII must be with the equipment during operation and whenever they are transferred between property accounts. The BII shall consist of all items essential for an operator or crew to place the Type I FOATC into initial operation to accomplish its intended operational function. The contractor shall over-pack (box and strap) one complete BII for each production Type I FOATC. The contractor shall prepare and deliver the list of BII, by National Stock Number (NSN), in a separate appendix to the Operator's manual IAW

Contractor Data Requirements List (CDRL) A001 Basic Issue Items (BII) List. (CDRL A001 Basic Issue Items (BII) List)

C.1.2.1 INITIAL SERVICE PACKAGE

The contractor shall prepare and deliver an Initial Service Package (ISP) Inventory List IAW CDRL A002 Initial Service Package (ISP)

Inventory List for each production Type I FOATC, unless otherwise specified in the delivery order. The ISP consist of all service parts and items required to perform scheduled maintenance within the warranty period required to maintain warranty requirements. The contractor shall over-pack (box and strap) the ISP and its components with each production vehicle. The ISP shall consist of all service parts required to meet warranty service intervals and to perform the first scheduled maintenance. The contractor shall mark each item with the nomenclature, part number, Commercial and Government Entity (CAGE) code, and NSN (if and when assigned). (CDRL A002 Initial

Service Package (ISP) Inventory List).

C.1.2.2 SPARE PARTS KIT

The contractor shall develop and provide recommended initial spares to support the Type I FOATC. Spare parts are repairable components or assemblies used for maintenance replacement purposes in the end items of equipment. They are articles identical to or interchangeable with the components of end items on contract, which are procured over and above the quantity needed for initial installation for support of a system. In addition, the contractor shall prepare and deliver a recommended initial spares list of support items IAW CDRL A003

Initial Spares List. The contractor shall update the list of spare parts quarterly; updates shall be based on the number of cranes fielded in the year following production and account for any change. (CDRL A003 Initial Spares List)

C.1.2.3 SPECIAL TOOLS KIT

The contractor shall provide a Special Tools and Test Equipment (STTE) Kit with every third production Type I FOATC, unless otherwise specified by the delivery order. The STTE is a tool kit that contains the tools designed to perform specific tasks for use on a specific end item or a special Component of the End Item (COEI). COEI are components of the Type I FOATC that are removed and separately packaged and stored for military transportation. As part of the Type I FOATC, these items must be with the end item when transferred between property accounts. STTE is authorized by the repair parts and special tools list located within that end items Technical Manual (TM).

The STTE supports Field Level Maintenance. Special tools differ from common tools, which are used on multiple end items and are found in a set, kit, or outfit as authorized by a supply catalog.The kit shall contain all Government approved special tools for the Type I

FOATC. The contractor shall provide the kit a unique part number and CAGE code which encompasses all tools within the kit. The special tools shall be packed in hard plastic, weather resistant container(s) with custom foam inserts to meet the requirements in MIL-STD-2073-

1E with Change 4. The contractor shall prepare and deliver an itemized STTE list IAW CDRL A004 Special Tools and Test Equipment (STTE)

List. (CDRL A004 Special Tools and Test Equipment (STTE) List)

5 54

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.1.2.4 SLING LEGS

The contractor shall provide sling legs IAW Attachment 0001 Type I FOATC PD AT-PRF-0001 , section 3.9.3 for each production Type I

FOATC.

C.1.2.5 CONCRETE BARRIER LIFT

The contractor shall provide a concrete barrier lift IAW Attachment 0001 Type I FOATC PD AT-PRF-0001, section 3.9.5. for each production Type I FOATC.

C.1.3 PROGRAM SCHEDULE AND DATA

C.1.3.1 INTEGRATED MASTER SCHEDULE

The contractor shall develop, maintain, and deliver an Integrated Master Schedule (IMS) for the Type I FOATC program IAW CDRL A005

Integrated Master Schedule (IMS). The IMS is used to verify attainability contract objectives, to evaluate progress toward meeting program objectives, and to integrate the program schedule activities with all related components. The intent of the program IMS is to provide a time-based schedule containing the networked, detailed tasks necessary to ensure successful program/contract execution. The contractors IMS shall contain all the deliverables (including hardware and CDRLs) and events identified in this contract. The contractor shall also develop a Logistics-specific IMS detailing all deliverables with a Logistics focus such as logistics events (Validation, Verification, and Maintainability Evaluation), logistics-focused document generation, provisioning efforts, and publications. The two

IMS schedules shall correspond concurrently and shall be interoperable with Microsoft Project. (CDRL A005 Integrated Master Schedule

(IMS))

C.1.3.1.1 INTEGRATED PRODUCT SUPPORT

The contractor shall manage and develop a Product Support Package to support updates to the Type I FOATC system in current Department of the Army Technical Manuals (DATMs) and IAW the current version of MIL-STD 40051-2 at the time of contract award (CDRL A006 Product

Support Package). The contractor shall appoint an Integrated Product Support Manager (IPSM) responsible for the logistics package update. The contractor shall prepare and deliver the Integrated Product Support (IPS) schedule at the Start of Work Meeting (SOWM) IAW

CDRL A007 Integrated Product Support (IPS). The contractor shall appoint an IPSM before the Logistics Start of Work Meeting (LSOWM).

The IPSM shall participate in the initial LSOWM, and develop a Logistics Product Sequence Event Schedule/Logistics Integrated Master

Schedule (LIMS) in an electronic form. The IPSM shall participate in all necessary Type I FOATC Integrated Product Teams (IPTs) and shall establish a separate follow-on Logistics IPT, will be the contractor Logistics Lead, and shall be able to discuss all ongoing/current Logistics actions with the Government Logistics Team and the Government IPSM. (CDRL A006 Product Support Package; CDRL

A007 Integrated Product Support (IPS))

C.1.3.1.2 PRODUCT SUPPORT PLAN DEVELOPMENT

The IPSM shall reference Department of the Army Pamphlet (DA PAM) 700-127 to prepare and deliver a Product Support Plan (PSP) Logistics

Management Information (LMI) IAW CDRL A008 Product Support Plan (PSP), Attachment 0002 DD Form 1692 and Attachment 0003 DA Form 2028

Recommended Changes to Publications and Blank Forms after award of a delivery order that changes the current PSP. The IPSM shall discuss the ongoing and current PSP actions during the Logistics Integrated Product Teams (IPTs) and be ready to discuss the PSP actions with the Government IPSM. The PSP update shall consist of four primary areas (Maintenance, Equipment Publications, Packaging, and Training) and shall also address all 12 Integrated Logistics Support (ILS) elements:

- Product Support Management

- Supply Support

- Packaging, Handling, Storage, & Transportation

- Maintenance, Planning & Management

- Design Interface

- Sustaining Engineering

- Technical Data

- Information Technology (IT) Systems Continuous Support

- Facilities & Infrastructure

- Manpower & Personnel

- Support Equipment

- Training & Training Support

The contractor shall provide a PSP update using the following information:

a) All Engineering Change Proposals (ECPs) implemented by the contractor.

b) All DA Form 2028 Recommended Changes to Publications and Blank Forms provided by the Government.

c) Any ECPs initiated by the Government.

6 54

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(CDRL A008 Product Support Plan (PSP), Attachment 0002 DD Form 1692; Attachment 0003 DA Form 2028 Recommended Changes to

Publications and Blank Forms)

C.1.3.1.2.1 INTEGRATED PRODUCT SUPPORT DEVELOPMENT

The contractor shall use Society of Automotive Engineers (SAE) Government Electronic and Information Technology Association (GEIA) STD-

0007 Revision C. Performance Specification, and LMI for use in identifying content, delivery and related guidance for logistics data.

Additionally, the contractor shall develop any operation tasks (Operator COTS manual section), maintenance tasks/troubleshooting tasks

(maintainer COTS manual section to include all trouble shooting procedures), and Repair Parts and Special Tools List (RPSTL COTS manual section). Figures missing from the COTS TM sections, but deemed necessary for use by the Target Audience (Soldier) shall be considered supplemental data. All supplemental data shall be created using eXtensible Mark-up Language (XML), current Document Type Definitions

(DTDs) and Style Sheet and follow MIL-STD-40051-2C. Warranty information shall be included in the Operator section. (Attachment 0004

COTS Publications Requirements)

C.1.4 CONTRACT EXECUTION

C.1.4.1 GOVERNMENT-FURNISHED PROPERTY (GFP)

The Government may provide Government Furnished Property (GFP) as identified in Attachment 0005 Government Furnished Property (GFP)

List for performance of this contract IAW DFARS 245.103-72. GFP is any property in the possession of, or directly acquired by, the

Government and subsequently furnished to the contractor for performance of a contract. Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes contractor-acquired property if the contractor-acquired property is a deliverable under a cost contract when accepted by the

Government for continued use under the contract. All GFP shall be documented using the GFP List. (Attachment 0005 Government Furnished

Property (GFP) List)

C.1.4.1.1. GFP MANAGEMENT

The Government may provide the contractor with GFP to support efforts under this contract. This may include but may not be restricted to the series of GFP such as the General Mechanics Tool Kit (GMTK) tool box, the Forward Repair System (FRS, or FRESH) tool box and the

Maintenance Support Device (MSD) troubleshooting interactive tool, which are governed under the Sets, Kits, Outfits and Tools (SKOT).

All GFP under this contract shall be managed IAW FAR 52.245-1.

C.1.4.1.2.2 INVENTORY CHECKLIST REPORT

The contractors accountability extends from the initial acquisition and receipt of property, through stewardship, custody, and use until formally relieved of responsibility by authorized means, including delivery, consumption, expending, sale (as surplus property), or other disposition, or via a completed investigation, evaluation, and final determination for lost property. This requirement applies to all Government property under the contractors accountability, stewardship, possession or control, including its vendors or subcontractors. The contractor shall physically inventory the GFP in its possession using CDRL A009 Inventory Checklist Report;

subcontractors are required to do the same. A component hand receipt for the appropriate SKOT will be provided to the contractor. The contractor shall inventory the GFP list provided prior to an event such as the Maintainability Evaluation and Verification. Upon receipt if any deficiencies are found the contractor shall notify the Government in writing within seven days. (CDRL A009 Inventory Checklist

Report)

C.1.4.2 DATA PROTECTION

The contractor shall establish appropriate administrative, technical, and physical safeguards to protect all Government data, to ensure the confidentiality, integrity, and availability of Government data IAW DFARS 252.204-7012 and FAR 52.204-21.

C.1.4.3 DATA DELIVERABLES

The contractor shall deliver all data in English IAW the requirements established in each individual Contract Data List Requirements

(CDRL) by referencing Attachment 0006 Exhibit A, CDRL DD Form 1423. Distribution shall be IAW each CDRL and Attachment 0007 Type I

FOATC Point of Contact (POC) List. The contractor shall submit documentation on or before the required due date as detailed in each

CDRL. The contractor shall validate all documentation prior to submittal to the Government. Government receipt of data deliverables does not constitute acceptance. Government acceptance of data deliverables hinges on the completeness, accuracy, and compatibility of submitted documentation, and the applicable military standards and specifications as detailed in each Data Item. Government acceptance of data deliverables will be communicated to the contactor by the Contracting Officers Representative (COR) or as otherwise specified per individual CDRL Data Items. (Attachment 0006 Exhibit A, CDRL DD Form 1423; Attachment 0007 Type I FOATC Point of Contact (POC)

List)

C.1.5 MEETINGS

C.1.5.1 MEETINGS AND REVIEWS

7 54

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The contractor and Government will periodically have meetings and reviews during this contract's performance period. Meetings are used to review progress and provide guidance on technical, logistics, contractual or other issues that arise during contract performance.

Prior to meetings, the Government and contractor will jointly develop an agenda. Meetings may be be at the contractors facility, the

Detroit Arsenal or via approved conference channels as mutually agreed upon by both parties within 30days of the meeting or event except as otherwise provided. When meetings are at the contractors facility, the contractor shall deliverfor the Government's use: production or other required versions for the Type I FOATC needed for viewing; Quality Management System documentation and records, required technical, logistics or other documentation (including drawings, computer data bases, publications, and other data); and computer resources, as needed.

C.1.5.2 PARTICIPATION AND ADMINISTRATION

In the event a meeting is to be hosted by the contractor, hosting duties and responsibilities shall consist of all functions related to the preparation and execution of the meetings to include providing facilities, sending invitations, media resources, security, minutes, and hard copy materials. The contractor shall also make available personnel for Government scheduled meetings at no additional cost to the Government.

C.1.5.3 AGENDA AND READ AHEAD PACKAGES

The contractor shall prepare and deliver an agenda and read-ahead package for all contractor-led meetings identified in this contract

IAW CDRL A010 Agenda and Read-Ahead Package)

C.1.5.4 MINUTES

The contractor shall prepare and deliver minutes for all meetings, IPRs, conferences and reviews IAW with CDRL A011 Meeting Minutes for meetings described in section C.1.5 and otherwise called out in this contract. The contractor shall ensure the action items include the name or agency responsible and date to be completed, as agreed during the review. The contractor shall also add a copy of all material presented at the review. (CDRL A011 Meeting Minutes)

C.1.5.5 PROGRAM REVIEWS

C.1.5.5.1 START OF WORK MEETING

The contractor shall conduct a Contract SOWM within 30 calendar days after contract award IAW CDRL A012 Start of Work Meeting(s). This meeting will introduce and align the Government and contractor teams. The contractor shall, at a minimum, brief:

a. Scope of Work (SOW) Review

b. IMS Review

c. Organizational Key Roles

d. Maintainability Evaluation

e. Technical Manual (TM) Validation

f. TM Verification

g. Requirement Review

h. Test Schedule

i. Risk Status

The contractor shall present organizational key roles and discuss the plan for communicating and transitioning personnel changes. The contractor shall be prepared for a detailed discussion with the Government. For planning purposes, this meeting is anticipated to be between two to four business days. (CDRL A012 Start of Work Meeting(s))

C.1.5.5.1.1 REQUIREMENTS REVIEW

The contractor shall conduct a Requirement Review concurrent to the SOWM. The Requirement Review will be a line-by-line review of

Attachment 0001 Type I FOATC PD AT-PRF-0001. The Requirement Review is considered complete once all the requirements are reviewed and discrepancies are resolved. (Attachment 0001 Type I FOATC PD AT-PRF-0001)

C.1.5.5.2 PROGRAM MANAGEMENT REVIEW

The contractor shall conduct quarterly Program Management Reviews (PMRs) with the Government at the contractors production facility. The first PMR shall be concurrent with the SOWM. At each PMR, the contractor shall present the cost, schedule, performance, supportability status and risk assessment and risk mitigation initiatives. These meetings shall also include separate discussions for safety, engineering, logistics, production, contracting, test, and product assurance.

C.1.5.6 LOGISTICS REVIEWS

8 54

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.1.5.6.1 LOGISTICS START OF WORK MEETING

The contractor shall host a Logistics SOWM in conjunction with the contract SOWM referenced in C.1.5.5.1. This meeting shall be strictly a Logistics discussion, an in-depth review of contract requirements and CDRLs and a venue to discuss Product Support Package development. For planning purposes, the participants should anticipate this SOWM to be a one to two day event. In addition, the contractor shall discuss in-depth the logistics areas of TM Validation, TM Verification, and the Maintainability Evaluation IAW the

Logistics-specific IMS and overall program IMS. This Logistics SOWM event shall introduce and align the Government and contractor

Logistics teams. (CDRL A005 Integrated Master Schedule (IMS)); CDRL A012 Start of Work Meeting(s))

C.1.5.6.1.1 PROVISIONING AND PUBLICATIONS START OF WORK MEETINGS

The contractor shall host concurrently Provisioning and Publications SOWMs immediately following the Logistics SOWM referenced in

C.1.5.6.1. The purpose of the Provisioning SOWM is to ensure the contractor has a clear understanding of the contractual provisioning requirements and to identify and reinforce the requirement for accurate, complete, and timely submission of provisioning data and information. The contractor shall present a provisioning schedule for Government concurrence and input into the IMS IAW CDRL A005

Integrated Master Schedule (IMS). The purpose of this meeting is to review publications contract requirements, establish lines of communications, answer all questions, and develop a publications schedule based on the requirements of the program and the contract.

(CDRL A005 Integrated Master Schedule (IMS)).

C.1.5.6.1.1.1 PROVISIONING GUIDANCE CONFERENCE

The contractor shall host a Provisioning Guidance Conference IAW ANSI-TA-STD-0017 Activity 3.4.1 and Attachment 0008 Provisioning

Requirements Statement. Government representatives from the Tank-automotive and Armaments Command (TACOM) shall attend from the Program

Management (PM) office and the Integrated Logistics Support Center (ILSC). This Provisioning Guidance Conference may run concurrent/combined with the Provisioning and Publications SOWMs referenced in C.1.5.6.2. The ILSC will include subject matter experts

(SMEs) in the fields of Provisioning and Publications. (Attachment 0008 Provisioning Requirements Statement)

C.1.5.6.2 IN-PROCESS REVIEWS

In-Process Reviews (IPRs) shall be held after award of a delivery order requiring development or updates to the Type I FOATC LMI. The

Government anticipates conducting IPRs on a monthly basis. The Government reserves the right to combine IPRs or keep them separate.

C.1.5.6.2.1 LOGISTICS IN-PROCESS REVIEWS

The contractor shall host Logistics IPR which encompass the progress on all logistics and publications requirements under the purview of the Supportability Integrated Product Team (SIPT). The SIPT shall address all supportability issues concerning Publications, Training, and Maintenance, Operator procedutes and Supply Support. The contractor shall host IPRs at the contractors facility, making available adequate space, facilities, personnel and a production Type I FOATC. IPRs may also be accomplished via teleconference if approved by the Government. The Government will provide the initial draft agenda ten days prior to the first IPR. The contractor shall provide draft agendas for each subsequent Logistics IPR five business days prior to the review. The contractor shall make available all information necessary to address issues and concerns in the agenda. (CDRL A010 Agenda and Read-Ahead Package)

C.1.5.6.2.1.1 MAINTENANCE ANALYSIS REVIEW

The contractor shall participate in a joint Government-contractor Maintenance Analysis (MA) Review to review the maintenance planning and analysis results IAW the IMS. MA Reviews shall be held using the following planning schedule:

a. The Initial MA Review shall be held after contract award to review the draft MA.

b. The Intermediate MA Reviews shall be held IAW the IMS 45 calendar days after the conclusion of First Article Test (FAT).

c. The Final MA Review shall be held at the conclusion of the Government TM Verification.

The contractor shall update and deliver the MA and provide it for Government acceptance IAW CDRL A013 Maintenance Analysis. The contractor shall update the MA prior to all provisioning conferences. (CDRL A005 Integrated Master Schedule (IMS); Attachment 0009 LMI

Summary Worksheet Maintenance Analysis; CDRL A013 Maintenance Analysis)

C.1.5.6.2.1.1.1 MAINTENANCE AND SUPPLY SUPPORT IN-PROCESS REVIEW

During development and Analysis of Maintenance and Supply Support IPRs shall be held after award of delivery order requiring development or updates to the Type I FOATC LMI to clarify issues and concerns related to data received to support Maintenance Concept and Supply

Support development. The Maintenance and Supply Support IPRs are not a part of the Provisioning Conferences.

C.1.5.6.2.1.1.1.1 NATIONAL MAINTENANCE WORK REQUIREMENT (NMWR) CANDIDATES LIST

The contractor shall develop a NMWR Candidate List. The NMWR Candidate List shall consist of repairable assemblies. The NMWR candidate list shall be a product of the MA. All components coded for repair at the sustainment level of maintenance shall be a NMWR candidate.

9 54

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The contractor shall annotate these components on the MA and provide them as a separate list at each MA Review. The Government will review and approve the final list of NMWR candidates at the final MA Review. The contractor shall prepare and deliver a NMWR Candidate

List IAW CDRL A013 Maintenance Analysis. (CDRL A013 Maintenance Analysis)

C.1.5.6.2.1.1.1.1.1 TRAINING IN-PROCESS REVIEW

The contractor shall host a Training In-Process Review (TIPR) at the contractor facility IAW the schedule in the IMS. The contractor shall provide a comprehensive review of the status of training development and issues requiring Government intervention. The contractor shall make available at each TIPR all training documentation for Government review.

C.1.5.6.2.2 PUBLICATIONS IN-PROCESS REVIEW

The contractor shall schedule and attend five Publications IPRs, at the contractor's facility, IAW the key milestones identified in the

IMS. Frequency shall be coordinated with the COR. The meetings shall encompass the progress on all logistics requirements under the purview of the SIPT. The SIPT shall address all supportability issues concerning Publications, Maintenance, and Operator procedures. The contractor shall provide properly formatted representative samples of every deliverable required to address issues and concerns in the

Government agenda sent ten business days prior to the IPR. The contractor shall be prepared to answer questions from the Government about publications work processes, provide records of Quality Assurance (QA) reviews, and respond to Government comments regarding publications processes or work samples. The samples will be reviewed for compliance with the applicable standards for the deliverable as provided in this (CDRL A005 Integrated Master Schedule (IMS)); CDRL A014 Operatr Technical Manual; CDRL A015 Field Maintenance

Manual; Attachment 0005 COTS Publications Requirements).

C.1.5.7 PROVISIONING REVIEW

C.1.5.7.1 PROVISIONING CONFERENCES

Provisioning Conferences shall be separate and distinct events from the Provisioning SOWM referenced in C.1.5.6.2 and the Provisioning

Guidance Conference referenced in C.1.5.7.1. The number of Provisioning Conferences is based on 800 Provisioning Line Item Sequence

Numbers (PLISNs) of data, but no more than 1,200 PLISNs of data, in addition to the initial and cleanup conference.

The contractor shall host Provisioning Conferences at the contractors facility, or a suitable facility where a Type I FOATC is located and can be accessed for maintenance purposes. The contractor shall provide 30 days in advance of the Provisioning Conferences the following data to support the conferences: the Provisioning Parts List (PPL) (LSA-036) IAW CDRL A016 Provisioning Parts List (PPL) and

Reviews, CDRL A017 Provisioning Pre-Procurement Screening (PPS), and CDRL A018 Engineering Data for Provisioning (EDFP). The contractor shall also provide copies of technical data to include the Maintenance Allocation Chart (MAC) IAW CDRL A019 Maintenance

Allocation Chart (MAC) (reference C.4.3.2), Failure Modes, Effects and Criticality Analysis (FMECA) IAW CDRL A020 Failure Modes, Effects and Criticality Analysis (FMECA) (reference C.3.4), Repair Parts and Special Tools List (RPSTL) IAW CDRL A021 Repair Parts and

Special Tools List (RPSTL), and Level of Repair Analysis (LORA) IAW CDRL A022 Level of Repair Analysis (LORA) Report (reference C.3.5).

The contractor shall present its data, rationale, and supporting documentation to the Government team for each PLISN. (CDRL A016

Provisioning Parts List (PPL) and Reviews; CDRL A017 Provisioning Pre-Procurement Screening (PPS); CDRL A018 Engineering Data for

Provisioning (EDFP); CDRL A019 Maintenance Allocation Chart (MAC); CDRL A020 Failure Modes, Effects and Criticality Analysis (FMECA)

CDRL A021 Repair Parts and Special Tools List (RPSTL); CDRL A022 Level of Repair Analysis (LORA) Report)

C.1.5.8 QUALITY REVIEWS

C.1.5.8.1 CORRECTIVE ACTION REVIEW BOARD

The Government will schedule Corrective Action Review Board (CARB) meetings after the completion of testing (reference paragraph

C.1.5.9). CARB Meetings shall review the functional and performance failure data and contractor's Failure Analysis Corrective Action

Report. The contractor shall attend all CARB meetings via teleconference and present findings that the Government may consider when assessing corrective actions. The Government CARB, as applicable, reflects all relevant CARB functions which include Quality, Test, Logistics, Maintenance, Systems Engineering, Safety, Transportability and Manpower and Personnel Integration (MANPRINT) Human Factors.

(CDRL A023 FACAR)

C.1.5.9 TEST REVIEWS

C.1.5.9.1 CONTRACTOR PRE-TEST READINESS REVIEW

The contractor shall conduct a Pre-Test Readiness Review (Pre-TRR) to present to the Government the readiness of the Type I FOATC to enter into Government Testing and discuss contractor support. For planning purposes, this meeting will be a one day event and will take place at contractor's facility at least five days prior to the Government Test Readiness Review (TRR).

C.1.5.9.2 GOVERNMENT TEST READINESS REVIEW

The contractor shall attend the Government TRR to be held at or in the vicinity of Aberdeen Proving Ground, MD. The contractor shall be

10 54

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

prepared to present information from the Pre-TRR. The Government TRR is anticipated to be held no more than five days prior to delivery of the first test system. For planning purposes, this meeting is anticipated to be a one day event.

C.2 SYSTEMS ENGINEERING

C.2.1 CONFIGURATION MANAGEMENT

The contractor shall be responsible for maintaining configuration control of the Type I FOATC delivered under this contract. The contractor shall manage all configurations including documentation, electronic media, and parts representing or comprising the Type I

FOATC. The contractor shall apply Configuration Management (CM) functions, including process, responsibilities, resources, and metrics throughout the program lifecycle, and flow down these CM functions to the subcontractors and entire supply chain.

C.2.1.1 CONFIGURATION BASELINE

The Type I FOATC shall be baselined and put under formal CM after successful completion of FAT. This baseline will identify and formally document the functional and physical characteristics of the Type I FOATC. The Government shall be the approver of all changes to the configuration baseline through Engineering Change Proposal (ECP) process (reference Section C.2.1.3).

C.2.1.2 CONFIGURATION MANAGEMENT PLAN

The contractor shall make available to the Government an existing corporate Configuration Management Plan (CMP) upon request. The contractor may use Government Electronics and Information Technology Association (GEIA) EIA-649-A, National Consensus Standard for

Configuration Management; GEIA-859, Data Management (DM); and DoD MIL-HDBK-61, Configuration Management Guidance.

C.2.1.3 ENGINEERING CHANGE PROPOSAL

The contractor shall notify and receive approval from the Government prior to implementing any configuration change via preparation and delivery of an Engineering Change Proposal (ECP) IAW CDRL A024 - Engineering Change Proposal (ECP). Impact statements and supporting data sufficient to evaluate the change shall accompany each request to include engineering, safety, quality, cost, schedule, MANPRINT, packaging, provisioning, maintenance, TM, and training data. Government approval of the ECP does not constitute relief from Type I FOATC performance requirements. (CDRL A024 Engineering Change Proposal - ECP)

C.2.1.4 REQUEST FOR DEVIATION

The contractor may request to temporarily deviate from the Type I FOATC PD by submitting a Request for Deviation (RFD) IAW CDRL A025 -

RFD. All permanent changes shall require an ECP to the Type I FOATC. (Attachment 0001 Type I FOATC PD AT-PRF-0001; CDRL A025 Request for Deviation - RFD)

C.2.1.5 FAT AND LOGISITICS VEHICLES REFURBISHMENT

Upon successful completion of any required FAT and satisfying all logistics requirements the FAT Type I FOATC and the Logistics Type I

FOATC shall be refurbished and shipped as part of the production quantity. The contractor shall transport the FAT Type I FOATC assets used for testing from the Government test site at the contractors expense. The Logistics Type I FOATC assets shall be shipped from the logistics facility, at the contractors expense. The contractor shall completely inspect the refurbished Type I FOATC assets and submit a detailed proposal for refurbishment of the Type I FOATC to a full mission capable (FMC) condition. The proposal shall detail all repairs that are required. The proposal shall be submitted within 20 days after FAT approval. The Government will negotiate the refurbishment effort after contractor proposal submittal. The negotiated refurbishment effort will not include any configuration changes required as a result of test failures. These changes are the contractors responsibili. Upon PCO acceptance of the contractors proposal, the contractor shall make the repairs specified in the proposal. The cost for refurbishment as a result of a contractor initiated ECP shall be at no additional cost to the Government.

C.2.1.4.1 FULLY MISSION CAPABLE (FMC) DEFINITION

FMC is defined as vehicle and all components, BII, subassemblies, and systems are fully functional and meet all performance requirements for which they were originally designed, configured and delivered to the Army. Any missing items or items that are leaking, damaged, cut, defective, or expected to fail within 12 months after delivery are not acceptable and shall be replaced IAW applicable technical manuals and work packages. Vehicle paint shall be inspected by the contractor, all defects shall be repaired by the contractor IAW contractors approved paint process. Tires shall be inspected by the contractor and repaired or replaced IAW TM 9-2610-200-14.

C.2.2 RISK MANAGEMENT

The contractor shall perform Risk Management activities identified in this section.

C.2.2.1 RISK MANAGEMENT PLAN

11 54

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The contractor shall develop a risk management plan IAW CDRL A026 Contractor Risk Management Plan, the Type I FOATC Program Risk

Management Plan (reference Attachment 0010 - Type I FOATC Program Risk Management Plan (RMP)), and best commercial practices. The plan shall be used by the contractor to monitor management, cost, and schedule of the contract efforts and technical risks relative to contract performance. The contractor risks shall be briefed and displayed in all technical reviews, Program Management Reviews, and IPT meetings. (CDRL A026 Contractor Risk Management Plan; Attachment 0010 - Type I FOATC Program Risk Management Plan (RMP))

C.2.2.2 RISK TRACKING REPORTS

The contractor shall develop and deliver Risk Tracking Reports based on the scoring criteria and template in the Type I FOATC Template and Instruction (Attachment 0011 - Risk Management Scoring Criteria and Reporting Template). The contractor shall systematically identify and analyze all risks, and shall develop mitigation plans for all red and yellow risks scored IAW Attachment 0011 - Risk

Management Scoring Criteria and Reporting Template. (CDRL A027 - Risk Tracking Report)

C.2.3 SAFETY ENGINEERING

C.2.3.1 SYSTEM SAFETY PROGRAM

The contractor shall establish and implement a System Safety Program to identify, assess, and manage safety, health and environmental hazards IAW MIL-STD-882E to ensure the safety-related requirements specified in the Type I FOATC PD are met. (Attachment 0001 Type I

FOATC PD AT-PRF-0001)

C.2.3.2 HAZARD TRACKING SYSTEM

The contractor shall deliver a Hazard Tracking System (HTS), which includes the process to identify, document and track Environmental, Safety, and Occupational Health (ESOH) hazards until they are eliminated or the associated risk is reduced to a level acceptable to the

Government. The contractor shall identify ESOH hazards associated with the system to include any modifications. The HTS shall contain the fields identified in MIL-STD-882 Task 106 for each potential or actual ESOH hazard of the system and when the hazard may be expected to occur under both usual and unusual operating and maintenance conditions. The contractor shall categorize the risk before and after mitigation IAW MIL-STD-882E. The contractor shall identify if the hazard is hardware, software or environmental related. Mitigation actions include redesign, recommended engineering controls, safety features or devices, warning devices and procedures and training.

Hazards to be identified in the HTS include, but are not limited to: sharp edges/moving parts hazards, physical hazards (e.g. extreme temperatures, acoustical energy, ionizing and non-ionizing radiation), chemical hazards (e.g. flammables, corrosives, carcinogens), toxic fumes (exhaust emissions), electrical hazards, whole-body vibration, compliance issues with regulatory organizations, generation of hazardous wastes, air/water/soil pollution hazards, biological hazards, fire prevention issues, and ergonomic hazards. (CDRL A028

Hazard Tracking System - HTS).

C.2.3.3 SAFETY ASSESSMENT REPORT

The contractor shall deliver a Safety Assessment Report (SAR) for the Type I FOATC IAW MIL-STD-882E Task 301. The SAR shall include the results of a Software System Safety Assessment (SSSA). The SSSA shall be executed IAW MIL-STD-882E terms, definitions and risk matrices, unless tailored alternative matrices are formally approved IAW DoD Component policy, to assess the Software contribution to system risk.

Additional guidance on how to conduct required SSSAs are provided in the Joint Software System Safety Engineering Handbook and Software

System Safety Implementation Process and Tasks Supporting MIL-STD-882E. The SAR shall address safety impacts to maintenance, operation, installation, and removal. Safety Data Sheets (SDS) shall be included in each assessment. As an appendix to the SAR, the contractor shall identify and incorporate a Hazard Tracking System IAW MIL-STD 882E Task 106.2. The contractor shall provide a description and discussion of each potential or actual health hazard of concern for each subsystem/component/item/etc. The SAR, including the health hazards, shall identify all known safety and health features of the hardware, firmware, software, system design, and inherent hazards and shall establish operational and maintenance procedures and precautions to be observed by Government test agencies and system users.

(CDRL A029 Safety Assessment Report - SAR)

C.2.3.4 FUNCTIONAL HAZARD ANALYSIS

The contractor shall conduct a Functional Hazard Analysis (FHA) IAW MIL-STD-882E Task 208. The FHA shall identify failure conditions of each function (loss of function, malfunction, or degraded function), identify the effects of that failure condition, and identify the severity of the effects. The FHAs shall also identify the SwCI associated with each function, Computer Software Configuration Items

(CSCIs), Computer Software Units (CSUs) and each Package, software contributions to the system level hazards, and safety-critical software requirements to mitigate the identified hazards. The contractor shall document the results of the FHA in the Hazards Report

(contractor hazard log) of the SAR. The contractor shall deliver the FHA as an appendix to the Hazard Tracking System. (CDRL A028

Hazard Tracking System - HTS)

C.2.3.5 SOFTWARE SYSTEM SAFETY

The contractor shall conduct a Software System Safety (SSS) Program IAW MIL-STD-882E, the Joint Software System Safety Engineering

Handbook, and the Software System Safety Implementation Process and Tasks Supporting MIL-STD 882E. The contractor shall include SSS as an integral part of the system safety program. The contractor software technical specialists, to include system safety and SSS

12 54

Na…