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

0004 2019JAN10

W56HZV

U.S. ARMY CONTRACTING COMMAND

WARREN, MICHIGAN 48397-5000

KYLE PAPKE

EMAIL: KYLE.Y.PAPKE.CIV@MAIL.MIL

W56HZV-18-R-0134

2018SEP18

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 28

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: KYLE PAPKE

Buyer Office Symbol/Telephone Number: CCTA-HCP-D/(586)467-6122

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

The purpose of Amendment 0004, to Solicitation W56HZV-18-R-0134, is to incorporate the following administrative changes:

SECTION C:

1. Revise the following language in Section C - Statement of Work in the Solicitation:

a. SECTION C.15.1

FROM: C.15.1 The contractor shall provide fielding support as defined in section C.15. The Government will provide a minimum of 45 days advanced notice for planned CONUS fielding dates and 90 days advanced notice for OCONUS fielding dates to allow for facilitation and coordination of all fielding support efforts. For CONUS fieldings, a minimum of 14 days from the contractual delivery date of a boat supporting that fielding and the agreed upon Required Delivery Date (RDD) set during the NMIB will be allotted to allow adequate time for shipment. For OCONUS fieldings, a minimum of 45 days from the contractual delivery date of a boat and the agreed upon Required

Delivery Date (RDD) set during the NMIB will be allotted to allow adequate time for shipment. These dates can be revised by mutual agreement of both parties.

TO: C.15.1 The contractor shall provide fielding support as defined in section C.15. The Government will provide a minimum of 45 days advanced notice for planned CONUS fielding dates and 90 days advanced notice for OCONUS fielding dates to allow for facilitation and coordination of all fielding support efforts. For CONUS fieldings, a minimum of 14 days from the contractual delivery date of a boat supporting that fielding and the agreed upon Required Delivery Date (RDD) set during the NMIB will be allotted to allow adequate time for shipment. For OCONUS fieldings, a minimum of 80 days from the contractual delivery date of a boat and the agreed upon Required

Delivery Date (RDD) set during the NMIB will be allotted to allow adequate time for shipment. These dates can be revised by mutual agreement of both parties.

SECTION J:

2. Revise Attachment 0024 - Authorized Stockage List dated 8 January 2019

SUMMARY

3. The RFP closing date of 23 October 2018 has not changed.

4. All other terms and conditions of this Solicitation remain unchanged and in full force and effect.

5. Offerors must acknowledge receipt of this Amendment Number in accordance with Solicitation paragraph A.5, entitled "Acknowledgement of Amendments."

*** END OF NARRATIVE A0005 ***

2 28

W56HZV-18-R-0134

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 Introduction

C.2 Hardware and Deliverables

C.3 Government Furnished Property (GFP)

C.4 Program Management

C.5 Environmental, Safety Engineering and Health Hazards

C.6 Configuration Management (CM) and Technical Data Package (TDP)

C.7 Warranty

C.8 Transportability Report

C.9 Provisioning Program

C.10 Packaging Data

C.11 Quality Assurance Management

C.12 Test Overview

C.13 Contractor Service Representative (CSR)

C.14 New Equipment Training

C.15 Fielding Support

C.16 Care and Storage of BEBs and CPKs

C.17 System Technical Support (STS)

C.18 Security

C.19 Obsolescence Management

C.20 Contractor Manpower Reporting

C.21 Anti-Terrorism (AT) Level I Training Requirement

C.22 Anti-Terrorism (AT) Awareness Training Requirement for Contractor Personnel Traveling Overseas

C.23 Access and General Protection/Security Policy and Procedures

C.24 Trusted Associate Sponsorship System (TASS) Program

C.25 iWatch Training

C.26 Contractor Employees Who Require Access to Government Information Systems

C.27 Information Assurance (IA)/Information Technology (IT) Training

C.28 Requirement for an OPSEC Standing Operation Procedure/Plan

C.29 OPSEC Training Requirement

C.30 Threat Awareness Reporting Program

C.1 Introduction

This Statement of Work (SOW) is for the production of the Bridge Erection Boat (BEB).

C.1.1 The contractor shall produce the BEB in conformance with the requirements of the Army Technical Purchase Description (ATPD) 2393

(Attachment 0001) and the BEB Technical Data Package (TDP) (Attachment 0002), and for providing support services as detailed in this

SOW.

C.1.2 Data

Unless otherwise stated, all data shall be submitted by email or by other electronic means mutually agreed to by both parties. Data submitted by email shall not exceed 10 megabytes (MB) in file size. Data over 10 MB shall be transmitted on a CD via regular mail or

AMRDEC Secure Access File Exchange (SAFE) Web application. Data delivery requirements are specified in each Contract Data Requirements

List (CDRL). All CDRLs are provided within Exhibit A of this contract.

C.2 Hardware and Deliverables

C.2.1 The contractor shall manufacture BEBs in accordance with (IAW) the requirements of the Attachment 0001, ATPD 2393, and Attachment

0002, BEB TDP. The Government will maintain configuration control of Attachment 0001, ATPD 2393 and Attachment 0002, BEB TDP.

C.2.1.1 Certifications to ATPD 2393 (Attachment 0001) Performance Requirements

In the event changes are made to the hardware and systems, the contractor shall provide all certifications required by ATPD 2393 in accordance with CDRL C001, Certification of ATPD Requirements.

C.2.2 Crew Protection Kit (CPK)

The contractor shall manufacture and deliver CPKs in accordance with Annex C of Attachment 0001, ATPD 2393.

C.2.3 Basic Issue Items (BII)

3 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The contractor shall provide BII for each production BEB. BII are the essential, ancillary items, required to place the equipment into operation and perform emergency repairs, enabling it to perform the mission and function according to design.

C.2.3.1 BII List

The contractor shall provide a BII list for all BII to include the BII required by Attachment 0001, ATPD 2393 in accordance with CDRL

C002, Basic Issue Items.

C.2.4 Initial Support Package (ISP)

The contractor shall provide an ISP for each production BEB. The ISP shall consist of all service parts/items required to meet service intervals during the first two years of service; excluding petroleum, oils and lubricants.

C.2.4.1 ISP List

The contractor shall provide an ISP list detailing all of the items to be included in the ISP in accordance with CDRL C003, ISP List. A complete ISP list shall include each item identified by nomenclature, part number and NSN (if assigned).

C.2.5 Authorized Stockage List (ASL) and Special Tools and Test Equipment (STTE): The contractor shall provide and over pack one ASL as defined in Attachment 0024, Authorized Stockage List and one STTE as defined in Attachment 0025, Special Tools and Test Equipment for each fielding.

C.2.6 Modifications for BEB Interface

If any modifications are required for the Common Bridge Transporter (CBT), Palletized Loading System Trailer (PLST) or Bridge Adapter

Ballet (BAP) to interface with the BEB IAW section 3.2.5 of Attachment 0001, ATPD 2393, the contractor shall provide an installation modification kit and installation instruction over-packed with each BEB.

C.3 Government Furnished Property (GFP)

C.3.1 The Government will provide GFP in accordance with Attachment 0003, Government Furnished Property.

C.3.2 Contractor Requirements for Operating Government Furnished Equipment (GFE)

The contractor shall have Operators/Maintainers who have an appropriate commercial drivers license to operate a CBT with and without the

PLST.

C.3.3 GFE Familiarization Training

Should the contractor require additional GFE familiarization training the Government will provide basic familiarization training to facilitate contractor operation of the GFE. Familiarization training will not exceed 40 hours.

C.3.4 Preventive Maintenance for GFP

The contractor shall perform Preventive Maintenance Checks and Services (PMCS) outlined in the appropriate operator manuals.

C.3.5 Contractor Request and Consumption of Government Furnished Material (GFM). The following procedures shall be used for GFP to be provided pursuant to Attachment 0001, ATPD 2393, section 3.4.4.1 SINCGARS Radio Capability.

C.3.5.1 Request for GFM

The contractor shall submit a request for GFM in accordance with CDRL C004, Request for GFM.

C.3.5.2 Receipt for GFM

The contractor shall use the GFM Request and Receipt form to acknowledge receipt of GFM within 10 days in accordance with CDRL C005, Receipt of GFM.

C.3.5.3 Transportation, Shipping and Packaging Discrepancy Report

The contractor shall perform an inventory and inspection within 10 days of receipt of GFM. The inspection shall determine if the items are in adequate condition and suitable for intended use, and that shipment received is in agreement with shipping documentation. The contractor shall document the results of the inspection and shall submit a report in accordance with CDRL C006, Transportation

Discrepancy Report, only if a discrepancy is found. The contractor shall obtain a SDR control number through the WEBSDR system in accordance with Attachment 0004, Contractor Accountability of GFM, and must include the SDR with the discrepancy report

4 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.3.5.4 GFM Consumption Report

Contractor shall submit a GFM consumption report in accordance with CDRL C007, GFM Consumption Report. The GFM Consumption report shall include categories to identify nomenclature, NSN or Part Number, quantity, and BEB ID number to which it is applied. The report shall reflect GFM consumed for each BEB delivered with the Final Inspection Report (FIR) in accordance with CDRL E001, FIR.

C.3.5.5 Remaining GFM

No later than 30 days after completion of the contract, the contractor is to inform the PCO on any remaining GFM and request disposition instructions. The contractor should indicate the quantity, type, and National Stock Number (NSN) of unused GFM remaining at the manufacturing/test facility and request disposition instructions.

C.4 Program Management

C.4.1 Participation

The contractor shall participate in the meetings and reviews required in this statement of work with Government attendance. The

Government will determine when meetings shall be held by electronic means (via tele-conferences, email, etc). Physical meetings shall be synchronized to minimize personnel resources and travel expenses.

C.4.2 Integrated Product Team (IPT)

An Integrated Product Team (IPT) shall be established to serve as the primary management tool and key method of communication for this contract. As part of the Start Of Work Meeting (SOWM), the Government and contractor will form IPTs. The Government IPT is detailed in

Attachment 0005, Government IPT List. IPTs and membership shall be assigned in the areas of contract and program management, engineering, Integrated Product Support (IPS), quality assurance, and safety. The contractor shall be prepared to address all schedule, performance, supportability and risk issues during IPT meetings.

C.4.3 Project Schedule

The contractor shall deliver a project schedule for the BEB Production phase. The project schedule shall include all milestones;

including but not limited to meetings, CDRL deliverable dates, production, and product support tasks required to complete the program, schedule, performance, and supportability requirements. The contractor shall maintain the project schedule. The project schedule shall be submitted quarterly IAW CDRL C008, Project Schedule, and explain all program slippages, and provide get-well plans within 30 days of discovery.

C.4.4 Agendas

The contractor shall submit an agenda and read-ahead package/briefing charts in contractor format for all meetings and reviews, with the exception of monthly IPT meetings, in accordance with CDRL C009, Meeting Agendas.

C.4.5 Meetings

The contractor shall prepare and submit meeting minutes for all meetings and reviews. Minutes shall include all issues, actions, CDRL progress, program decisions, and intention of the next meeting or technical review in accordance with CDRL C010, Meeting Minutes. The following meetings are a part of this effort:

a. SOWM

b. Program Management Reviews (PMR)

c. System Safety Working Group

d. Post Fielding Support Analysis (PFSA)

e. IPTs

C.4.5.1 Start of Work Meeting (SOWM)

Within 30 Days After Contract Award (DACA), a SOWM shall be held at the contractors production facility. Contractor attendees shall include contract administration personnel, management, engineering, quality, and logistics personnel. The agenda for the SOWM shall be delivered in accordance with CDRL C009, Meeting Agendas. The SOWM is projected to be one day in duration.

C.4.5.2 Program Management Reviews (PMR)

The contractor shall conduct annual Program Management Reviews (PMR). The final PMR shall occur 6-months prior to the completion of the final production boat. The PMRs shall be at the contractor's production facility and are projected to be one day in duration. The contractor shall present the schedule, performance, supportability status, and risk mitigation initiatives. Contractor attendees shall include contract administration personnel, management, engineering, quality, and logistics personnel.

C.4.5.3 Post Fielding Support Analysis (PFSA)

5 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The contractor shall participate in a Post Fielding Support Analysis (PFSA), conducted jointly with the Government. Each PFSA is projected to be three days in duration. The PFSAs will take place in Fort Leonard Wood, Missouri, Barling Arkansas, and Abbeville, SC during the first ordering year. The PFSA shall be supported by the fielding manager. The PFSA is a structured means of evaluating the readiness, supportability, and resource requirements for fielded materiel. It is not a specific methodology, but an integrated and detailed effort to continuously monitor the status of the entire IPS program for a fielded materiel. PFSA provides a mechanism to identify supportability-related problems, enhance readiness, optimize supportability, and reduce Life Cycle Cost.

C.4.5.4 Integrated Product Team (IPT)

The contractor shall participate in monthly IPT meetings. The meetings will be conducted via teleconference and are projected to be an hour in duration. A week prior to the meeting the COR and contractor will jointly develop an agenda. Participation in the IPT will be appropriate to support the agenda.

C.4.6 Risk Management

The contractor shall identify, monitor, and mitigate all program risks, and track risk elements to completion/closure in a Risk

Management Status Report in accordance with CDRL C011, Risk Management Status Report. Resolved risks shall be archived on the report after Government approval.

C.5 Environmental, Safety Engineering and Health Hazards

C.5.1 Environmental Compliance

The contractor shall ensure that all aspects of contract execution, including all BEB hardware, are in compliance with United States

Federal, State, and Local environmental regulations and requirements; including activities associated with design, build, test, storage and disposal. Hazardous materials usage shall be in accordance with Attachment 0001, ATPD 2393, 3.6.1. Hazardous materials restrictions shall apply to all components, parts, and materials provided under this contract, including items purchased through a subcontractor or supplier, Commercial Off-The-Shelf (COTS) components, Original Equipment Manufacturer (OEM) parts, and manufactured parts.

C.5.1.1 Hazardous Materials Management Program (HMMP) Report

The contractor shall submit a HMMP Report and update the report in the event of material/process changes in accordance with CDRL C012, HMMP Report. The HMMP report shall identify all hazardous materials required for system manufacture, assembly, operation and sustainment, including the parts/process that requires them; and hazardous waste produced as a result of demilitarization, disposal, and emergency situations. The report shall include a listing of hazardous materials prioritized for minimization or elimination.

C.5.1.1.1 Hazardous Materials Exceptions

The contractor shall submit formal waiver requests from the requirements of Attachment 0001, ATPD 2393, section 3.6.1, using Attachment

0006, Request for Use of BEB Prohibited Material, no later than 60 days after contract award and include detailed technical justification for the use of the prohibited hazardous materials. The contractor shall not use or deliver any prohibited hazardous materials without prior written PCO approval.

The following materials can be used without a written approval:

- Cadmium and hexavalent chromium on electrical connectors and back shells used to mate with cadmium electrical connectors on GFE

- Cadmium and hexavalent chromium on electrical connectors used in Automatic Fire Extinguishing Systems (AFES)

- Products listed under Priming and Topcoating in Chemical Agent Resistant Coating (CARC) primers and topcoats listed in

MIL-DDTL-53072, Table 1

- Lead-acid batteries

- Lead solder

- Leaded battery terminal adaptors/clamps

- Lead in engine bearings

- Steel containing up to 0.35% lead by weight

- Aluminum containing up to 0.4% lead by weight

- Copper and Brass alloys containing up to 4% lead by weight

- Beryllium and Beryllium alloys used in electrical components

- Nickel and Nickel alloys

- Mercury containing components compliant with European Union (EU) Directive 2011/65/EC (RoHS 2)

- Trace amounts of identified restricted materials contained in base materials and/or alloys. For the purposes of this contract, trace amounts are defined as <0.1% by weight for carcinogens and <1% by weight for all other materials.

C.5.3 Hazard Tracking System (HTS) (MIL-STD-882, Task 106)

6 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The contractor shall establish and maintain an HTS in accordance with CDRL C013, HTS, and Attachment 0007, HTS Template. The HTS supports risk management by providing the Government a database to capture identified hazards and lessons learned, track status of the hazard corrective action or acceptance, and provide a communication forum. The contractor shall develop and maintain a method or procedure to document and track hazards for identification until the hazard is eliminated or the associated risk is reduced to a level acceptable to the Government.

C.5.3.1 The HTS shall contain a description of each potential or actual environmental, safety and health hazard of the BEB, the cause and effects of the hazard, when the hazard may be expected to occur under usual and unusual operating or maintenance conditions, and status of each hazard. The contractor shall identify actions to mitigate the risk associated with the hazards and categorize the risk before and after mitigation in accordance with MIL-STD-882. The contractor shall identify if the hazard is software related.

Mitigation actions include recommended engineering controls, safety features or devices, warning devices and procedures and training.

The HTS shall also include the findings from an Environmental Hazards Analysis (EHA) (MIL-STD-882, Task 210).

C.5.3.2 Examples of hazards to be identified in the HTS include, but are not limited to: sharp edges, moving parts or rotating parts/assemblies, 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, noise, whole body vibration, compliance issues with regulatory organizations, generation of hazardous waste, biological hazards, fire prevention issues and ergonomic hazards.

C.5.4 The BEB System Safety Working Group (SSWG) is a PM Chartered advisory group that addresses safety issues and supports the Program

Manager in implementing the System Safety Program. The contractor shall provide representation at the BEB SSWG meetings. During SSWG meetings, the contractor shall present Safety and Hazardous Materials Management program status and updates, Hazard Tracking System

(HTS) status and updates, Hazardous Materials usage status and updates, and other Environmental, Safety, and Occupational Health (ESOH) data.

C.6 Configuration Management (CM) and Technical Data Package (TDP)

C.6.1 Configuration Management (CM) Program. The contractor shall establish a CM program for Configuration identification, control, status accounting, audit, and data management of the BEB. To maximize return on investment and reduce life cycle costs, the contractor shall use best practices to implement the technical and program management principles fundamental to CM. The contractor is encouraged to 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, as references for CM and DM. The contractor shall deliver a CM Plan in accordance with CDRL C014, CM Plan.

C.6.2 Configuration Baseline. The Product Baseline exists at contract award, and shall not be changed or updated without prior

Government approval. The contractor shall provide continuous maintenance of the product baseline documentation throughout the production contract performance period.

C.6.2.1 The Government has configuration control of the BEB baseline at contract award for both Major (Class I) and Minor (Class II) changes. The contractor shall not incorporate any change or variance without prior Government approval. The contractor shall document and submit all engineering changes as Engineering Change Proposals (ECPs). Value Engineering Change Proposals (VECPs) shall be submitted as a Major (Class I) ECP. Throughout the contract performance period, the contractor shall submit all variances in accordance with the

Variances section of the contract.

C.6.2.2 Configuration Status Accounting Information (CSAI)

The contractor shall submit a CSAI report and this information shall be recorded and maintained by the contractor for the term of this contract. CSAI reports shall include status of changes, status of resulting action items, effectivity, and incorporation status of approved changes. Approved changes shall not be recorded or reported as completed or closed until the new or revised documentation

(incorporating the approved change) has been delivered to the Government in accordance with CDRL C015, CSAI.

C.6.3 Engineering Changes. The contractor shall submit changes by Engineering Change Proposal (ECP) in accordance with CDRL C016, ECP.

The contractor shall prepare and submit all Class I and Class II ECPs-Notice of Revisions (NORs) in accordance with CDRL C017, and

Attachment 0008, NOR and the Data Delivery Description (DDD) for ECPs, VECPs, and NORs. The contractor shall deliver a NOR for each document affected by a change. Specification changes shall also be described on a NOR. Alternatively, a NOR form is not necessary if the documentation (all sheets or pages) is provided and electronically red-lined or otherwise marked-up to clearly show original information and proposed changes.

C.6.3.1 Major ECPs have any combination of the following:

a. A change that affects specified and approved requirements including safety, reliability, supportability, and quantitative requirements that result in product attributes that would be outside specified limits or specified tolerances.

b. A change that affects any approved acquisition baseline (i.e. Functional, Allocated, or Product Baselines).

c. A change that affects compatibility with interfacing products including such products as test equipment, support equipment, software, firmware, and products furnished by an Acquirer or that affects one or more of the following:

7 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

1. Delivered operation or servicing instructions.

2. Required calibration to the extent that product identification should be changed.

3. Interchangeability or substitutability of replaceable products, assemblies, or components.

4. User skills or user physical attributes.

5. Operator or maintenance training.

6. Requires retrofit of delivered products (e.g., by product recall, modification kit installation, attrition, replacement during maintenance using modified spares).

7. Performance.

8. Maintainability, durability, or survivability.

9. Weight, balance, or moment of inertia.

10. Electromagnetic characteristics.

11. Impact to logistical support requirements such as training, technical or operational manuals, spares, maintenance procedures or equipment, etc.

12. Re-qualification of the item.

13. Domain certification (e.g., airworthiness, seaworthiness).

14. Source (supplier of an item) listed on a Source Control Drawing (SCD).

15. Biomedical factors or human factors engineering.

16. Personnel manning.

17. Corrects deficiencies.

18. Adds or modifies interface or interoperability requirements.

19. Changes the operational capabilities or logistics supportability of the system or item and the change is significant and measurably changes the effectiveness.

20. Life cycle costs/savings.

21. Prevents slippage in an approved production schedule.

d. A change that does not meet the above criteria but does impact cost/price/delivery to customer(s), including incentives and fees, guarantees, warranties, and contracted deliveries or milestones.

C.6.3.2 Minor ECPs are those that do not impact the criteria above for Major (Class I) changes.

C.6.3.3 The contractor shall request numbers via e-mail to the Configuration Data Management (CDM) representative identified in

Attachment 0005, Government IPT List, and apply the Government assigned ECP number(s) to all ECPs requiring Government approval. The contractor shall use the Government-assigned 3-character prefix and the 5-character alpha-numeric suffix as the ECP number.

C.6.3.4 In the event the Government directs an engineering change, the PCO will notify the contractor by a request for technical and price proposal, which the contractor shall furnish at no additional cost to the Government. The contractor shall submit an ECP to allow the Government to clearly understand all areas of impact. The contractor's ECP submittal shall include sufficient supporting information, together with certified cost and pricing data.

C.6.3.5 Variances. If the contractor finds it necessary to temporarily deviate from the approved BEB requirements for a specific number of boats or for a specified period of time, the contractor shall seek written authorization from the Government by preparing and submitting a properly classified and documented Request for Variance (RFV) in accordance with CDRL C018, RFV. The contractor shall apply a unique RFV number to each variance. RFVs can only be dispositioned by the PCO or the PCOs designated Government representative.

C.6.3.6 Variance Classification.

a. Critical. Critical variances are not allowed. A critical variance is a departure from requirements affecting one or more of the following:

(1) safety

(2) human health

(3) environment, and

(4) security (local program or national)

b. Major. A major variance is a departure from requirements affecting one or more of the following:

(1) performance or operational limits,

(2) interchangeability, reliability, survivability, maintainability, or durability of the item or its repair parts,

(3) structural strength,

(4) effective use or operation,

(5) weight, moment, center of gravity

(6) appearance,

(7) limits on product use or operation,

(8) temporary use of alternate items, or

(9) when the configuration documentation defining the requirements for the item classifies the departure from the requirement as major.

c. Minor. A minor variance is a departure which does not involve any of the factors listed for critical or major or when the

8 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

configuration documentation defining the requirements for the item classifies the departure from the requirement as minor. Note:

Departures from the requirements that do not meet the definition of critical or major and are not classified in any configuration documentation (i.e. unlisted characteristic) are treated as minor.

C.6.3.7 Variances are for the benefit of the contractor and consideration offered for acceptance of the proposed RFV shall be attached as part of the RFV. Under no circumstances shall submission or approval of an RFV be the basis for a contract price increase.

C.6.3.8 ECPs and RFVs shall contain marked up copies of affected drawings and 3D models as well as impact statements and any other supporting data necessary to fully understand and disposition the ECP or RFV. The ECP or RFV shall be clear and comprehensive from technical, cost, and scheduling perspectives. All potential impacts, including technical, operational, support, schedule, and cost, shall be included with each change. The ECP submission shall include support to any meetings projected to be required based on the proposed change such as Configuration Control Boards, Provisioning Meetings, Publications In-Process Reviews, and Corrective Action

Review Boards (CARB).

C.6.3.9 The contractor shall be responsible for additional costs to the BEB, testing, or software associated with any changes due to deficiencies or non-compliance to the contract. Costs for contractor proposed changes to enhance the BEB or performance, will be handled through the ECP process and contract modification. Approved changes do not relieve the contractor from its responsibility to furnish all products in conformance with the contract requirements.

C.6.4 Engineering Release

C.6.4.1 Engineering Release Record (ERR)

An ERR is an action that formally approves configuration documentation and makes configuration documentation available for its intended use. The ERR is the vehicle by which the contractor initially delivers new product data to establish the product baseline (i.e., "initial release"), and delivers revised product data implementing approved changes to the existing Product Baseline (i.e., "change release"), subsequent to a Government-approved ECP. The contractor shall create, maintain, and revise product data and submit ERR packages. The ERR Package is defined as the ERR form submitted concurrently with the new or revised product change release. The contractor shall prevent premature release of product data related to an ECP until the Government has approved the ECP and subsequent

ERR. Multiple ECPs on one ERR is not allowed. The contractor shall submit ERRs concurrently with TDPs in accordance with CDRL C019, TDP and ERR.

C.6.4.2 ERR Number

The contractor shall request an ERR number from the Governments Configuration Manager as identified in Attachment 0005, Government IPT

List, prior to completion of drawings, models and associated lists and submission of any new or revised product data. The contractor shall add its Government-assigned 3-character prefix to the 5-character alpha-numeric ERR number furnished by the Government. The resulting 8-character ERR number shall be the engineering release authority number reflected on models and in the revision block of drawings/associated lists. The ERR number used for change release shall be the same as the ECP number.

C.6.4.3 ERR Submittal/Approval

The ERR package shall contain product data reflecting the complete, Government approved product baseline configuration (incorporating all approved changes) of the BEB TDP; there shall be no missing down parts, interface data, or other deficiencies. The ERR will be approved only after all required product data has been delivered as part of the ERR package and the data is accurate, complete, and approved for release by the Government.

C.6.4.4 As-Built Configuration List (ABCL)

The contractor shall submit an ABCL in accordance with CDRL C020, ABCL and Attachment 0009, ABCL Template. Additional fields are acceptable in the ABCL if they are thoroughly explained by the contractor. The ABCL shall be prepared in indenture level sequence down to the lowest component piece part level and include quantities for each. The contractor shall utilize the OEM part number and CAGE to identify parts. The contractor shall not re-identify or re-mark supplier or purchased parts or related product data with his own number and CAGE unless directed by the Government.

C.6.5 Windchill PDMLink

C.6.5.1 Windchill PDMLink is the Governments Product Data Management (PDM) System for CSA (e.g., PCI, TDPs).Wherever the term PDMLink is used in this contract, it shall mean the Governments instance of Windchill PDMLink, unless otherwise noted. Only unclassified data shall be created and maintained in PDMLink. The contractor shall adhere to these PDMLink requirements, which are in effect at contract award.

C.6.5.2 A Windchill 'object' is the general term for data that is added to and managed in PDMLink. There are different object types

(e.g., parts, documents, change objects, attachments), and each type has unique attributes (e.g., number, name). Objects have a two-way connection via relationships (e.g., usage, reference), and have actions (e.g., check-out, create, revise) performed on them. The

9 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

contractor shall create ECPs (i.e., Change Requests), RFVs (i.e., Variances), and ERRs (i.e., Change Notices) in PDMLink, attaching supporting files, drawings, models, specifications, and associated documents, to the applicable ECP, RFV, or ERR prior to submitting to the workflow.

C.6.5.3 The PDMLink workflow is the automation of a business process in whole or in part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules. A workflow instance coordinates user and system participants, together with appropriate data resources, to achieve defined objectives by set deadlines.

C.6.5.4 The contractor shall use the PDMLink workflow to submit ECPs and VECPs (with NORs), RFVs, and ERR Packages to the Government.

The Contractor shall notify the Configuration Management (CM) representative identified in Attachment 0005, Government IPT List, by e-mail that the ECP, VECP, RFV, or ERR has been submitted to the PDMLink workflow.

C.6.5.5 The contractor shall obtain a login and password to PDMLink for all contractor personnel responsible for either creating objects or submitting ECPs, VECPs, RFVs and ERRs to the Government using the automated workflow. Contractor personnel who may have a need to search, view, and print in PDMLink, should also obtain a login and password for read-only permissions. Contractor personnel who require access to PDMLink shall first coordinate with the BEB CM representative, who will determine approval and the applicable access permission level based on the role(s) of each individual. The ACE Support Team Representative will assist you in completing the forms to access the PDMLink System. Forms can be found at: https://ace2.tacom.army.mil/newuser/ . Complete the ACE Access

Request Form. A copy of Section C of the current awarded contract shall accompany each PDMLink request form.

C.6.5.6 The contractor shall adhere to the Government-provided Standard Operating Procedures (SOPs), User Guides, Policies, and

Procedures for Windchill PDMLink. The contractor shall attend PDMLink training as deemed necessary by the Government and comply with requirements of Windchill PDMLink. The contractor shall also request training, as needed, via a formal e-mail request to the BEB CM representative. The type and location of training will be at the Governments discretion. Initial training will be led by the Government at the contractor's facility and is projected to be one day in length. The contractor shall conduct subsequent trainings by implementing a train the trainer program.

C.6.5.7 The contractor shall notify the Helpdesk via e-mail message to: usarmy.detroit.rdecom.mbx.tardec-ace-support@mail.mil when

PDMLink work cannot be accomplished by the contractor due to access or permission issues, software deficiencies or bugs. The contractor shall courtesy copy the BEB CM representative on all helpdesk requests. The contractor shall notify the BEB CM representative by email when PDMLink or the data in PDMLink is not accessible.

C.6.6 Configuration Verification and Audits.

C.6.6.1 The contractor shall comply with contract requirements, AS 9100 Quality Management System (QMS), and SAE EIA-649-1, Configuration Verification and Audits.

C.6.6.2 The contractor shall implement internal verification and audit activities to insure product compliance with requirements and consistency between the product, its PCI, and support assets. The Government reserves the right to conduct one or more audits to verify the PCI reflects the validated BEB product. The contractor shall identify and resolve all discrepancies.

C.6.7 BEB Technical Data Package Requirements

When an engineering change is approved through the Government Configuration Control Board, the contractor shall prepare and deliver an incremental TDP with an ERR form reflecting the latest approved design in accordance with CDRL C019, TDP and ERR, and Attachment 0010, Government Format Production TDP. Each TDP package shall include 3D parametric solid models, associative 2D Computer Aided Design (CAD) drawings, 2D PDF drawings, and an indentured Bill of Material (IBOM). The IBOM shall reflect only the package product structure it accompanies.

The BEB TDP, Attachment 0002, has been developed utilizing Solidworks 2016 3D parametric solid models and associative 2D drawings. The contractor shall use Solidworks 2018 for the life of this contract unless otherwise approved by the Government. The contractor shall provide updates and revisions to existing solid model CAD files as well as new solid model CAD files using Solidworks 2018. The contractor shall obtain written or email concurrence from the PCO prior to usage of any other CAD format. The contractor shall not make changes to the BEB TDP without a Government approved ECP, VECP, or RFV.

C.6.8 Product Data Management

C.6.8.1 The contractor shall possess an authoritative product data, engineering or configuration management system and the processes to effectively manage, securely store, release, validate, and track multiple versions and iterations of the as-designed, as-integrated, as-built, and as-delivered configuration baselines; this includes management of product structures, product definition documents/data, contractor test and analysis data, Government-Furnished Information (GFI) and other related technical data.

C.6.8.2 The contractor shall develop, manage and maintain the product data throughout the contract performance period. The product data shall consist of product data that is fully defined and sufficient for competitive re-procurement. The product data shall include all product data, indentured product-structure (part-relationship / parent to child), associated lists, specifications, standards, product

10 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

related documents (e.g. engineering bill of material, special tools and materials, and test and calibration requirements), and all approved and implemented engineering changes.

C.6.8.3 Product Data shall be prepared to provide accurate design, engineering, manufacturing, and quality assurance requirements. Any

3D CAD models shall reflect the as built or assembled and tested baseline configuration. The models shall be used for the manufacture, assembly and configuration management of the materials, parts, subassemblies and assemblies of the equipment covered under this contract.

C.7 Warranty

C.7.1 Commercial Warranty

The contractor shall over pack (with the Technical manuals) a report of any commercial warranty, with all applicable pass through warranties, inside each BEB delivered to the Government in accordance with CDRL C021, Commercial Pass Through Warranty. The report shall include the following:

a. Warrantors name and address.

b. Component covered under warranty.

c. Component part number, serial number and CAGE code.

d. Original warranty period.

e. Remaining warranty period.

f. Contact information to submit a warrant claim.

The details of the warranty process shall be included in the technical manual.

C.7.1.1 Warranty Performance Report

The contractor shall submit a warranty performance report reflecting all the warranty claims processed on each BEB within the appropriate reporting period in accordance with CDRL C022, Warranty Performance Report. The report shall include the number of operational hours of each engine on the BEB at the time of fault. The report will be limited to the information below, as provided by the repairing dealer on the claim, for each warranty claim processed:

a. Parts required (by NSN), unit costs and quantities

b. Labor rates and hours

c. Travel times, distances, rates and cost, when appropriate

d. Shipping times, distances, rates and costs, when appropriate

e. Equipment hours at time of failure

f. Dates and times of equipment failure notification, manufacturer response, repair completion, and equipment return to service.

g. Total combined dollar amount per claim that includes the parts, labor, and travel time/mileage.

The dollar amount provided for each claim will be a total dollar amount at equivalent commercial dealer selling/list price rates for all expenses, including parts, labor, and travel time/mileage (TT/M).

C.8 Transportability Report

If configuration changes are made which impact the transportability requirements of Attachment 0001, ATPD 2393, the contractor shall submit revisions sheets for insertion in the transportability report in accordance with CDRL C023, Transportability Report.

C.9 Provisioning Program

C.9.1 The contractor shall develop a provisioning program for the BEB using GEIA-STD-0007, data worksheets found in Attachment 0011, Provisioning Requirements Worksheet, and guidelines found in MIL-HDBK-502, Logistics Management Information (LMI), for use in identifying content, delivery and related guidance for logistics data. The Government will use the guidance contained in the Quality

Assurance Provisioning Guidance Book (QAPG) and AMC PAM 700-25 for acceptance criteria of provisioning data delivered under the provisions of contract. The contractor shall identify any new parts and components of the BEB and input the data into the Provisioning

Parts List (PPL) accordingly in accordance with CDRL C024, PPL. Data shall be loaded into the database provided, using Provisioning

Contract Control Number (PCCN): CBRGBT and Usable On Code (UOC): BEB. The PPL/LMI will contain all data for the assemblies, sub-assemblies, spare parts, BII, Expendable Durables, Long Lead Time Items (LLTI), and kits, to include Components of the End Item (COEI), Additional Authorization List (AAL), and Special Tools required to support BEB. The final PPL must reflect all components, to ensure all parts in the PPLM reflect the total top-down breakdown structure, including all parent/child relationships.

C.9.2 The contractor shall submit an Engineering Data for Provisioning (EDFP) for each P source-coded part number being provisioned, not having a valid NSN in accordance with CDRL C025. EDPF. Illustrations shall be annotated with the PLISN and PCCN for the system. These illustrations may include parts lists, detail and assembly illustrations, interface control illustrations, performance characteristics, company illustrations, or commercial parts book pages that clearly identify each new item and its part number. EDFP submitted must

11 28

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

reflect the PPL submitted. Missing EDFP to support PPL in any submittal will render the PPL incomplete, and non-acceptable. A complete submission package will be used as the basic technical resource for the provisioning review.

C.10 Packaging Data

C.10.1 Packaging Data Development: The contractor shall develop and provide packaging data for all items identified during the provisioning process in accordance with C.9 with a Source, Maintenance & Recoverability (SMR) code beginning with P excluding PR and PZ.

Packaging data development priority shall be given to LLTI, repairable items, and any item classified as a Special Group Item.

Packaging data shall be developed in accordance with MIL-STD-2073-1 and classified in accordance with C.10.2. The contractor shall provide facilities, equipment, materials, and each P-coded item for packaging development. The contractor shall complete validation and provide support data with each data submittal. Validation support data shall include copies of any applicable Material Safety Data

Sheets for Hazardous Material items. The packaging data generated shall reflect one increment of the provisioned Unit of Issue. For packaging data development purposes, the Quantity per Unit Pack (QUP) shall equal 001.

C.10.2 Item Classification: Each provisioned P-coded item shall be classified as a Selective group item or a Special group item in accordance with MIL-STD-2073-1 and paragraphs C.10.2.1 and C.10.2.2.

C.10.2.1 Selective group item: Items classified as Selective group items shall not have a unit pack weight exceeding 40 pounds or shall not have a dimension greater than 40 inches. A Selective group item must not require disassembly for packaging. Reconfiguration for packaging of Selective group items is limited to folding or coiling. Items will not be classified as Selective if they are repairable, recoverable, contain hazardous material, or if assigned a shelf life. Packaging data output for Selective group items is in the form of

Logistic Product Data (see C.10.3).

C.10.2.2 Special group item: Items classified as Special group items often require sketches, figures, or narrative instructions to describe packaging requirements. Items excluded from the Selective group will be classified as Special group items. This includes kits, sets and items of separate parts, items requiring disassembly, repairable items, NMWR candidates, items requiring special handling or condemnation procedures, items classified as hazardous material or hazardous goods in transport, items assigned a shelf life, electrostatic discharge sensitive items, fragile, sensitive, and critical items. Packaging data output for Special group items consists of Special Packaging Instructions (see C.10.4) and Logistic Product Data (see C.10.3).

C.10.3. Logistic Product Data Packaging: The Contractor shall develop Logistic Product Data for each Selective and Special group item.

At the contractors request, the Government may provide a MS ACCESS application that provides data formatting and edit features for coding of packaging Logistic Product Data. The contractor shall develop, maintain and update packaging data in accordance with MIL-STD-

2073-1 and CDRL C026, Packaging Data.

C.10.4 Special Packaging Instruction (SPI): The contractor shall develop a SPI for each item classified as a…