DRAFT Section C.docx

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1.0 General Information

This is a non-personal services contract to provide System Technical Support (STS) services in support of Product Manager (PdM) Army Watercraft Systems (AWS). The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government, regardless of the performance location.

C. 1.0.1 Description of Services/Introduction

The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform the STS services as defined in this Performance Work Statement (PWS) except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

C. 1.0.2 Background

PdM AWS serves as the Life Cycle Manager, primarily categorized as follows:

a) Landing Craft: Logistics Support Vessel (LSV), Landing Craft Utility (LCU-2000), Landing Craft Mechanized (LCM-8) Mod I, Maneuver Support Vessel (Light) MSV(L)

b) Ship-to-shore enablers: Modular Causeway System (MCS)

c) Towing and terminal operations: Small Tug (ST-900), and

d) Watercraft operations support: LCM-8 Mod II

These systems and sub-systems require continued support including design and application of modifications to address deficiencies, address obsolescence issues, and improve capability; development and correction of technical data, and configuration management.

C. 1.0.3 Scope

This PWS applies to services for engineering and safety analysis, design support, technical support, configuration management, maintenance engineering, quality assurance, integrated logistics support, test asset installation, program management, new equipment training, milestone documentation, obsolescence management, business case analysis, and related support efforts for AWS. Requirements include analysis of failures in fielded vessels, research, engineering analyses, design, and installation of test assets for vessel performance issues, all with limited to no technical data. Specialized watercraft design support and naval architecture experience are required to execute this contract.

C. 1.0.4 Period of Performance/Ordering Periods

The period of performance for any specific task(s) will be included at the task order level. At the IDIQ contract level, there will be five ordering periods, as follows:

a) 1st Ordering Period: Date of contract award - 364 days after contract award (DACA)

b) 2nd Ordering Period: 365 DACA - 729 DACA

c) 3rd Ordering Period: 730 DACA - 1,094 DACA

d) 4th Ordering Period: 1,095 DACA - 1,459 DACA

e) 5th Ordering Period: 1,460 DACA - 1,824 DACA

The total IDIQ contract ordering period is 60 months.

C. 1.0.5 Recognized Holidays

The contractor is not required to perform services on the following holidays:

New Year's Day Martin Luther King Jr.'s Birthday President's Day Memorial Day Juneteenth Independence Day Independence Day Labor Day Columbus Day Veteran's Day Thanksgiving Day Christmas Day

C. 1.0.6 Hours of Operation

Unless additional hours during the workday are coordinated in advance and approved in writing by the COR, the contractor is responsible for conducting business, no more than 10 work hours per day, 40 hours per work week per person, between the hours of 0600-1800, with personnel required to be present during the core hours of 0900-1500 local time, Monday through Friday, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. Lunch and rest periods may be taken during the core hours but are not considered productive time and are not billable. If the hours required in a billing period cannot be fulfilled because of a Government-created circumstance, the contractor, COR and contracting officer will discuss an alternate billing arrangement on a case-by-case basis. The contractor must at all times maintain an adequate workforce for the performance of all tasks defined within this PWS when the Government facility is not closed. Upon mutual agreement of the COR and the contractor, contractor personnel may shift work hours from the Monday to Friday schedule to weekends.

The contractor must comply with all labor laws, including the payment of Overtime to employees covered by the Fair Labor Standards Act, but the Government will not pay a separate labor rate for work that exceeds 40 Hours per week or that takes place on weekends.

C.1.0.7 Place of Performance

The contractor shall perform the work under this contract at the contractor's facility and/or onsite where vessels are located (CONUS and OCONUS), in accordance with the Task Orders. The contractor shall provide onsite support within PdM AWS located in Warren, MI, when directed under the specific Task Orders. Several vessels are located at Fort Eustis, VA; other vessels are located along the east and west coasts of the United States, and in Hawaii, Japan, and Kuwait.

The Government anticipates performance at, but not limited to, the following locations:

CONUS:

Oxnard, California San Diego, California Fort Eustis, Virginia Tacoma, Washington Pearl Harbor, Hawaii

OCONUS:

Okinawa, Japan Yokohama North Dock, Japan

C. 1.0.8 Type of Contract

The contract type for all task orders issued against this contract will be Cost Plus Fixed Fee in accordance with FAR 16.306; task orders can be issued in either a completion or term (also known as "level of effort" (LOE)) form. Material and travel will be on a Cost, No Fee (CNF) basis only.

C. 1.0.9 Physical Security

The contractor shall be responsible for safeguarding all government equipment, information, and property provided for contractor use.

C. 1.0.10 Special Qualifications

The contractor is responsible for ensuring its employees possess and maintain current Information Assurance Technician (IAT) Level I professional certification during the execution of this contract in accordance with the PWS herein. Additionally, the contractor shall provide an American Bureau of Shipping (ABS)-certified welder when welding is required at the task order level.

C. 1.0.11 Contracting Officer Representative (COR)

A qualified COR will be appointed by the Contracting Officer at the Task Order level. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions:

a) Observe that the Contractor performs the technical requirements of the contract;

b) Perform inspections necessary in connection with contract performance;

c) Maintain written and oral communications with the Contractor concerning technical aspects of the contract;

d) Issue written interpretations of technical requirements, including Government drawings, designs, specifications;

e) Monitor contractor's performance and notifies both the Contracting Officer and contractor of any deficiencies;

f) Coordinate availability of government furnished property; and provide site entry of contractor personnel.

A letter of designation is issued to the COR, with a copy sent to the contractor, stating the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates, or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

C. 1.0.12 Contract Manager

The contractor shall provide a contract manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer. The contract manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.

C. 1.0.13 Identification of Contractor Employees

All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

C. 1.0.14 Contractor Travel

Contractor shall be required to travel CONUS and OCONUS during the performance of this contract. The contractor may be required to travel to off-site training locations and to ship training aids to these locations in support of this PWS. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification to the COR.

C. 1.0.15 Other Direct Costs

All anticipated ODCs associated with performance shall have an estimated cost at the time of Task Order award. The Contracting Officer will review and approve all proposed ODCs prior to award.

C. 1.0.16 Markings on Data Deliverables

Markings on all deliverables shall be in accordance with DFARS clauses including but not limited to 252.227-7013 (ALT II), 252.227-7014, and 252.227- 7015 (ALT I).

C. 1.0.17 Organizational Conflict of Interest

Contractor and subcontractor personnel performing work under this contract may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services, which may create a current or subsequent Organizational Conflict of Interests (OCIs) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor's mitigation plan will be determined acceptable solely at the discretion of the Contracting Officer. In the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements that may be affected by the OCI.

C. 1.1 Specialized Watercraft Information

The contractor shall comply with all applicable regulations and standards including, Department of Defense (DoD) regulations:

· Army Regulations (AR),

· United States Coast Guard (USCG) standards,

· Environmental Protection Agency (EPA) regulations,

· Occupational Safety and Health Administration (OSHA) Regulations,

· Safety of Life At Sea (SOLAS) requirements,

· Code of Federal Regulations (CFR) Title 46 Shipping

· Code of Federal Regulations (CFR) Title 47, Telecommunications,

· American Bureau of Shipping (ABS) Rules,

· International Maritime Organization (IMO) requirements, and discharge standards.

C. 1.2 Task Scope

The specific scope of each Task Order will fall within the general scope of the overarching PWS.

C. 1.3 Schedule

The contractor shall create and maintain a key events Integrated Master Plan (IMP) in addition to an Integrated Master Schedule (IMS) in accordance with (IAW) CDRL A002 (Integrated Program Management Report (IPMR)) for each Task Order, to include development of an IMP and an IMS for various PD AWS programs. The contractor shall use Microsoft Project and Milestone Professional to create and maintain the IMS and IMP. The IPMR shall include the applicable title and Task Order number. Schedules shall specify all necessary tasks for the work prescribed by the Task Order. Schedules shall differentiate between duration and milestone tasks. Schedules shall include a timeframe for each task including a start, finish, duration, and percent complete for any task in process. The IMS shall identify the critical path through completion of each Task Order. In addition, the schedule shall state responsible parties for each task as a resource-loaded schedule. The contractor shall update and publish each schedule IAW CDRL A002 (Integrated Program Management Report).

C. 1.3.1 Schedule delays

The contractor shall notify the Contracting Officer's Representative (COR) and the Contracting Officer at least two (2) business days prior to any schedule slip in accordance with CDRL A002 (Integrated Program Management Report). Notification shall be provided via email. Within ten (10) business days of the notification email, the contractor shall detail, via email, the reasons for the schedule slip and the proposed corrective action to be taken, and submit a revised schedule to the COR and Contracting Officer. The Government reserves the right to approve or disapprove any contractor-proposed changes that affect contract and Task Order schedules. The contractor shall submit any necessary request for PoP extensions in advance of the completion date established in the Task Order. There will be no additional cost to the Government for PoP extensions for contractor-caused delays.

C. 1.4 Data Accession List (DAL)

The contractor shall provide and update a DAL in accordance with CDRL A039 (DAL). The contractor shall flow down the DAL requirements to its subcontractors.

C. 1.5 Government Systems

The contractor shall use Government Systems to facilitate unclassified, secure internet-based information sharing between STS program participants. SharePoint will also serve as the primary means of submitting Controlled Unclassified Information (CUI) CDRL items, unless otherwise stated within a specific CDRL item. The contractor shall notify appropriate Government personnel via email, as specified in the applicable CDRL, when it posts new or updated documents to a collaboration environment. The notification email shall include a hyperlink to the posted content. The Government will provide details on specific Government Systems, requirements for access, and approach for use at the contract Start of Work Meeting (SOWM).

C. 1.5.1 Government Sponsored Accounts

The Government will sponsor any required accounts. Personally Identifiable Information (PII) cannot be stored on SharePoint. The Government will provide these details at the SOWM. The Government can only sponsor accounts for U.S. Citizens. All contractor and subcontractor employees requiring access to these accounts must successfully complete the Department of Defense (DoD) Cyber Awareness Challenge Training; this must be accomplished before approval will be given to access these accounts. The DoD Cyber Awareness Challenge Training will be an annual requirement, thereafter. The Army Training Certification Tracking System (ATCTS), and required training, is located here: https://atc.us.army.mil/iastar/index.php. The contractor shall provide names, contact information, level of access (upload or download), and training required for personnel requiring access to these accounts no later than the SOWM. The contractor shall update this information throughout the life of the contract.

C. 1.5.2 Access to Government Systems

To access Government Systems, the contractor shall have or obtain an External Certification Authority (ECA) Certificate, or a DoD Common Access Card (CAC), for the appropriate personnel. Details on the ECA program and authorized ECA vendors can be found at:

http://iase.disa.mil/pki/eca/. Request for access to any other Government systems shall go through the PCO. The contractor shall designate an IA Officer to work with PdM AWS and the Government IA Manager in order to obtain and implement usage of the CAC program in compliance with DoD Directive 8190.3 Smart Card Technology, and DoD 8520.2, Public Key Infrastructure (PKI) and Public Key (PK) enabling.

C. 1.6 Common Access Card (CAC) and Trusted Associate Sponsorship System (TASS)

C. 1.6.1 Common Access Card (CAC) Applications

The contractor shall appoint an Information Assurance Officer to initiate Security Investigations of employees and subcontractors prior to requesting CAC applications Federal Acquisition Regulation (FAR) 52.204-9, Personal Identity Verification of contractor Personnel, DoD Directive 8190.3 Smart Card Technology and DoD Instruction 8520.2 PKI and PK Encryption.

C. 1.6.2 Requests for Common Access Card (CAC)

The contractor shall submit requests for CACs, with personnel information, via email to the COR.

C. 1.6.3 Trusted Associate Sponsorship System (TASS)

The Government will establish a TASS application account for each CAC request and provide each contractor and subcontractor employee a User Identification (ID) and password via email.

C. 1.6.4 Common Access Card (CAC) Access

Contractor and subcontractor employees shall access the TASS account and complete the CAC application within seven calendar days of notification of ID and password.

C. 1.6.5 Common Access Card (CAC) Request Status

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

C. 1.6.6 Common Access Card (CAC) Approved and Rejected Applications

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

C. 1.6.7 Common Access Card (CAC) Period of Performance

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

C. 1.6.8 Common Access Card (CAC) Return

The contractor and subcontractor(s) shall return issued CACs to the DEERS office IAW FAR 52.204-9. The contactor shall notify the Government of all CACs returned to the DEERS Office.

C. 2.0 Meetings

C. 2.1 Post Award Start of Work Meeting

The contractor shall host a SOWM at its facility, unless the parties agree to some other location, no later than 30 calendar days after contract award. The contractor shall, at a minimum, invite its leadership, PdM AWS representatives, the COR and the Contracting Officer. The contractor shall coordinate a mutually acceptable meeting date with the COR. The Government will have final approval of the meeting dates. The contractor shall prepare and submit a proposed agenda, CDRL A003 (Report, Record of Meeting/Minute), via email, for the SOWM at least three business days before the scheduled meeting date, to include an outline of how it will accomplish all awarded tasks.

C. 2.2 Task Order Kickoff Meeting

The contractor shall host a Kickoff Meeting for each Task Order. The Kickoff Meeting shall include the contractor personnel assigned to the tasks prescribed by the Task Order and PdM AWS personnel overseeing the Task Order. The contractor shall hold Kickoff Meetings by via Microsoft TEAMS within 15 calendar days of award of a Task Order, unless otherwise agreed to by PdM AWS. With the Government's approval, the contractor may hold Kickoff Meetings in conjunction with other regularly scheduled PdM AWS meetings.

C.2.3 Meeting Minutes

Following the SOWM and each Kickoff Meeting, the contractor shall provide meeting minutes within two business days IAW CDRL A003 (Report, Record of Meeting/Minutes).

C.2.4 Integrated Product Team (IPT) Meetings

When required by a Task Order, the contractor shall participate in all planning/implementation meetings (consisting of IPT and working group meetings). The contractor shall host design review meetings as required by a Task Order.

C.2.5 Program Management Reviews (PMR)

The contractor shall schedule and conduct joint contractor and Government quarterly PMRs that include participation from its senior level program management, senior-level technical management, and Subject Matter Experts (SME). PMRs shall focus on the full range of programmatic topics to include cost, schedule, performance, and risk. The contractor shall present program status at the PMRs based on its IMP, IMS, metrics, accomplishments, and risk management efforts. Risk management efforts shall follow the guidelines of the Risk Management Guide for DoD Acquisition (Sixth Edition, Version 1.0). The contractor shall provide status of all CDRL efforts. The contractor shall hold all PMRs either by telephone or at the contractor's facility. The Government estimates that each PMR will not exceed one business day. Following the PMR, the contractor shall submit meeting minutes IAW CDRL A003, (Report, Record of Meeting/Minutes).

C.3.0 Engineering Requirements

The Government will assign services for the contractor to perform under this contract, by a Task Order, and may include tasks from one or more sections of this PWS.

C.3.1 Analysis and Technical Investigation

When required by a Task Order, the contractor shall conduct a technical investigation. Technical investigations shall consist of one or more of the following:

a) analysis of failed components,

b) investigation of field incidents,

c) preparation of engineering calculations,

d) fabrication of test asset hardware for trial installation and/or testing,

e) structural analysis (e.g., stress analysis, finite element analysis, dynamic modeling) on parts, components, and assemblies,

f) Electromagnetic Interference (EMI) and Electromagnetic Environmental Effects (E3)

g) system/design trade-off studies,

h) observations of Government and/or third party tests,

i) attendance at technical meetings,

j) field review of modified and/or failed parts or systems,

k) failure analysis,

l) technology surveys,

m) Manufacturing Readiness Level (MRL) analysis,

n) architecture evaluations,

o) cost modeling,

p) engineering design review for life cycle cost reductions,

q) system requirement analysis,

r) development of Systems Engineering Plans (SEP), and/ or

s) general technical assistance on engineering matters.

t) Software documentation analysis and assistance with Cyber analysis

u) Thermal Analysis

v) Spectrum Supportability

In the Task Order, the Government will either assign specific tasks for the contractor to perform in the course of a technical investigation or identify the required end product(s) or deliverable(s). The contractor shall identify and conduct any specific tasks necessary to perform the technical investigation, and if applicable, complete and deliver the required end product(s) or deliverable(s). The contractor shall submit a technical report IAW C.3.3 and CDRL A004, (Technical Report) to document the results of a technical investigation, including identification of the purpose, methodology, results, and any other information required by the Task Order.

C.3.1.1 Regulatory Compliance

As part of each technical investigation, the contractor shall evaluate the compliance of systems identified in applicable Task Orders with laws and regulations identified by the CFR, International Convention on SOLAS, ABS, IMO, and any other applicable regulations identified in the Task Order. The contractor shall identify compliance or non-compliance of investigated in the technical report IAW CDRL A004 (Technical Report).

C.3.2 Engineering Change Development and AWS Engineering Process

When required by a Task Order, the contractor shall develop engineering changes to be applied to PdM AWS vessels or related assets (e.g., other vessel equipment that is issued with the vessel but not permanently attached, such as a rescue boat). For all projects resulting in a change to the configuration of a PdM AWS vessel or related asset, including design of vessel modifications, integration of new parts, and additions of new tools, accessories, or equipment, the contractor shall follow the AWS engineering process as defined in the subsequent paragraphs. Preliminary and Critical Design Reviews (C.3.2.2 and C.3.2.3) shall be completed for all engineering changes unless otherwise directed by a Task Order. The rest of the process (C.3.2.1 and C.3.2.4 thru C.3.2.6), when required, will be specified in the applicable Task Order.

C.3.2.1 System Requirement Review (SRR)

When required by Task Order, the contractor shall conduct a Requirements Review. The Requirements Review shall cover the system requirements, architecture overview, project overview, configuration management overview and initial system assessment. The contractor shall provide a draft A-kit IBOM IAW CDRL A041. The Requirements Review shall be included in the Meeting discussions and presentation material IAW CDRL A003, (Report, Record of Meeting/Minutes).

C.3.2.2 Initial Design Work and Preliminary Design Review (PDR)

Following the Kickoff Meeting, the contractor shall develop design concept(s) to meet the requirements of the Task Order and shall present the concept(s) to the Government at the PDR. The contractor shall present at least two potential design solutions at the PDR, with a recommendation of which design solution to select, unless otherwise directed by the Task Order. At the PDR, the Government will evaluate the design solutions and either select a design or require additional information or design solutions to be investigated. Following the PDR, the contractor shall submit meeting minutes within two business days IAW CDRL A003 (Report, Record of Meeting/Minutes).

C.3.2.3 Detail Design Work and Critical Design Review (CDR)

Following approval of a design solution at the PDR, the contractor shall complete detailed design work on the selected design(s) and hold a CDR, IAW with the Task Order IMS, to present the completed design to the Government. At the CDR, the Government will evaluate the completed design and either approve the design or require changes to the design. Following the CDR, the contractor shall submit meeting minutes within two business days IAW CDRL A003 (Report, Record of Meeting/Minutes).

C.3.2.4 Test Asset(s) and Proof.

When required by the Task Order, following approval of the design at the CDR, the contractor shall build at least one test asset of the selected design and install it on the vessel(s). The test asset shall demonstrate functionality, validate the technical data package IAW Section C.4.3, and validate the modification instructions. Upon completion of the test asset installation and functionality demonstration, the contractor shall hold a Test Asset Review (TAR). At the TAR, the contractor shall present status to the Government, identify any needed configuration changes, present an updated TDP, and obtain approval for a second test asset installation, if required. The second test asset, if required, will serve as a "proof" incorporating any necessary changes identified during installation or use of the first test asset, and will serve as verification of the Technical Data Package (TDP) and modification instructions. Any deviations from the TDP during the second test asset installation, or any subsequent test asset installation (if required), must be approved in advance by the COR, IAW with C.4.10 and CDRL A006 (Request for Variance).

C. 3.2.5 Production Readiness Review (PRR)

When required by the Task Order, the contractor shall hold a PRR to present status and outcomes of the test asset installation(s) to the Government and obtain approval to finalize the design and submit a formal ECP. Following the PRR, the contractor shall submit meeting minutes IAW CDRL A003 (Report, Record of Meeting/Minutes). Following successful completion of the PRR, the contractor shall prepare and submit an ECP IAW with C.4.1 and CDRL A005 (ECP). The contractor shall furnish all drawings and models of the new design to the Government IAW with CDRL A007 (Technical Data Package) and Attachment 0002 (TDP Requirements).

C.3.2.6 Engineering Drawing Revisions

When required by task order, the contractor shall revise existing engineering drawings. Unless otherwise stated in the task order, the revised drawings shall comply with C.4.3.

C. 3.3 Technical Report

When required by a Task Order, the contractor shall submit a technical report IAW CDRL A004 (Technical Report).

C. 3.3.1 Electromagnetic Environmental Effects Integration and Analysis (E3IA) Report

When required by a Task Order IAW C.3.1 (f) to report the results of E3IA, the contractor shall submit an E3IA Report (E3IAR) IAW CDRL A059 (E3IAR).

C. 3.3.2 Spectrum Supportability Risk Assessment (SSRA)

C.3.3.2.1 When required by a Task Order IAW C.3.1 (v), the contractor shall prepare a SSRA IAW CDRL A060 (SSRA).

C.3.3.2.2 When required by a Task Order IAW C.3.1 (v) to prepare a SSRA, the contractor shall provide a DD Form 1494 for each contractor furnished spectrum-dependent (S-D) equipment item referenced in the SSRA IAW CDRL A061 (Spectrum Certification Spectral Characteristics Data).

C. 3.3.3 Electromagnetic Interference Control Procedures (EMICP)

When required by a Task Order IAW C.3.1 (f) to provide data to evaluate design procedures and techniques for subsystems and equipment used to meet EMI control requirements based on paragraph 5.1 MIL-STD-461, the contractor shall submit Electromagnetic Interference Control Procedures (EMICP) IAW CDRL A062 (EMICP).

C.3.4 Trial Installations.

When required by a Task Order, the contractor shall conduct trial installations and tests of items (e.g., modified or replaced systems, sub systems, or parts) and test equipment, and test or evaluate the functionality of the item under consideration. The contractor shall supply all tools and parts required for the evaluation and shall restore the vessel to the original configuration at the conclusion of the test, unless otherwise specified in the Task Order.

C.3.5 Testing and Test Support

When required by the Task Order, the contractor shall perform testing or provide support to the testing of an existing, modified, or new vessel system(s), subsystem(s), and component(s).

C.3.5.1 Test Plans, Procedures and Reports

When required by a Task Order, the contractor shall develop detailed test plans IAW CDRL A017 (Test Planning). Test plans shall include the requirements tested, test procedures and processes, data collected during testing, method of data collection, and the required facilities and resources needed to execute the test plan. The contractor shall develop and maintain a test schedule as part of the project IMS IAW CDRL A002, (Integrated Program Management Report). The contractor shall provide all necessary testing support, including trained crew, maintenance personnel, and data collectors. If contractor conducts testing at a facility not owned or operated by the contractor, the contractor shall coordinate with any necessary outside facilities. Throughout testing, the contractor shall provide test progress reports at a frequency determined by the Government IAW CDRL A002, Integrated Program Management Report. At the completion or testing, the contractor shall develop a detailed Final Test Report IAW CDRL A034 (Test/Inspection Report).

C. 3.5.1.1 Government Witness of Contractor Testing

The Government reserves the right to witness any or all testing conducted IAW C.3.5.1. The contractor shall ensure that Government personnel can witness the testing, whether conducted at their facility or another facility arranged by the contactor. The contractor shall be responsible for ensuring Government personnel have access to witness the testing. The contractor shall notify the Government of contractor testing dates and schedules no less than 15 calendar days for testing conducted at a CONUS location and no less than 45 calendar days for testing conducted at an OCONUS location. If the contractor fails to provide notification within the required timeframes, the contractor shall repeat the test at no additional cost to the Government.

C. 3.5.1.2 Electromagnetic Immunity (EMI) Test Procedures. When required by a Task Order IAW C.3.1 (f) to conduct EMI testing, the contractor shall submit EMI Test Procedures (EMITP) IAW CDRL A063 (EMITP).

C. 3.5.1.3 Electromagnetic Interference (EMI) Test Report. When required by a Task Order IAW C.3.1 (f) to report the results of EMI testing, the contractor shall submit an EMI Test Report (EMITR) IAW CDRL A064 (EMITR).

C. 3.5.1.4 Electromagnetic Environmental Effects (E3) Verification Procedure (E3VP). When required by a Task Order IAW C.3.1 (f) to conduct E3 testing, the contractor shall submit an E3VP IAW CDRL A065 (E3VP).

C. 3.5.1.5 Electromagnetic Environmental Effects (E3) Verification Report (E3VR). When required by a Task Order IAW C.3.1 (f) to report the results of E3 testing, the contractor shall submit an E3VR IAW CDRL A066 (E3VR).

C. 3.5.1.6 Electromagnetic Interference Survey (EMIS) Test Procedures. When required by a Task Order IAW C.3.1 (f) to conduct an EMIS, the contractor shall submit EMIS Test Procedures IAW CDRL A067 (EMIS Test Procedures).

C. 3.5.1.7 Electromagnetic Interference Survey (EMIS) Test Report. When required by a Task Order IAW C.3.1 (f) to report data to evaluate the contractor's design procedures and techniques for subsystems and equipment used to meet EMI control requirements based on MIL-STD-461, the contractor shall submit an EMIS Test Report IAW CDRL A068 (EMIS Test Report).

C. 3.5.2 Test Support

When required by a Task Order, the contractor shall provide support to testing conducted by the Government or other directed testing entity in both CONUS and OCONUS. The contractor shall provide test support personnel, to include On-site Representatives (OSRs) and Technical Experts to provide technical, logistics and maintenance support for the vessels, subsystems, and components. The contractor shall provide logistics and maintenance support that includes, but is not limited to, special tools, diagnostic equipment, spare and repair parts, maintenance, and parts documentation.

C. 3.5.3 Test Deficiencies and Test Incident Reports

When required by a Task Order, the contractor shall be responsible to diagnose and respond to deficiencies and Test Incident Reports. In response to a test deficiencies and test incident reports, the contractor shall conduct an investigation, root cause analysis, and provide recommended corrective action. Upon Government approval, the contractor shall implement and verify all corrective and preventative action. Corrective action shall consist of interim corrective action that can be implemented immediately to continue testing, and final corrective and preventative action that are part of the final design configuration. The contactor shall document all investigation, root cause analysis, and corrective and preventative action and provide a final report to the Government IAW CDRL A035, (Failure Analysis and Corrective Action Report).

C.3.5.3.1 Test Readiness Review (TRR) The contractor shall support joint, Government and contractor TRRs at the contractors facility, or via telecom as applicable, NLT 21 calendar days prior to testing. Individual TRRs are not anticipated to exceed two business days. At each TRR, the contractor shall present a formal review of the contractor’s verification and validation efforts and results performed thus far, results to date, delivered IAW Test Readiness Reviews, CDRL A003 and a formal review of the contractor’s readiness to proceed to any additional testing. The Government will provide the contractor a listing of Government attendees NLT 15 calendar days prior to the event.

C.3.5.3.2 Test Readiness Review (TRR) Entrance Criteria The contractor shall address the following prior to scheduling the TRR:

a. Configuration of system under test, including computer software, has been defined and agreed to by the Government. All interfaces have been placed under CM.

b. All prior contactor efforts up to the TRR, including functional, unit level, subsystem, system, and qualification testing have been conducted successfully.

c. All known system discrepancies have been identified.

d. All previous design review exit criteria and key issues have been satisfied.

e. All contractor-required resources (including, but not limited to: Test Support Package, Repair Parts, Special Tools and Test Equipment, and Test Support Personnel) have been identified and are available to support required tests.

f. Roles and responsibilities of all test participants are defined and agreed to.

g. Test plans (Contractor Test Plans, CDRL A017 for all other testing) have been submitted and accepted. The testing portions of the IMS, CDRL A002 (Integrated Program Management Report), have been updated.

i. Identification and status of ESOH risks is defined and known.

j. Completed SAR, CDRL A055.

C.3.5.3.3 Test Readiness Review (TRR) Exit Criteria. The TRR is considered closed when the planned activity has been completed, all the critical Request for Action(s) (RFAs) are closed, and the following exit criteria have been met, as determined by the Government:

a. Test plans are based on traceable requirements and are complete and approved by the Government for the system under test

b. All contractor testing resources are ready and available

c. The hardware that is being tested and the entire test environment is configuration controlled as applicable

d. All lower level computer software and hardware testing has been successfully completed and documented e. The hardware metrics show readiness for testing

f. The required Cybersecurity scans have been conducted on the system

g. The risk level is identified and has been accepted by the Government. Identification and status of ESOH risks have been defined and known C.3.6 Environmental, Safety, and Occupational Health (ESOH).

C.3.6.1 Safety Engineering and Health Hazards.

C.3.6.1.1 Safety Engineering Principles. The contractor shall use Military Standard (MIL-STD)-882E to determine whether safety engineering objectives are met as required as result of any design changes. The contractor shall complete the following:

C.3.6.1.1.1 Identify hazards associated with the system by conducting safety analyses and hazard evaluations (shall include operational, maintenance, and transport aspects of the equipment along with potential interface problems with planned subsystems).

a. Eliminate or reduce significant hazards by appropriate design or material selection. If hazards to personnel cannot be avoided or eliminated, take steps to control or minimize those hazards.

b. Locate equipment components and controls so that access to them by personnel during operation, maintenance or adjustments shall not require exposure to hazards.

c. Ensure warning, caution, and notes are included in instructions for operation, maintenance, assembly and repairs IAW MIL-STD-40051 and that distinct markings are placed on hazardous components of equipment.

C.3.6.1.2 Safety Assessment Report (SAR). The contractor shall perform and document an assessment to identify the status, at the time of the report, of safety hazards, associated risks, mitigation measures, and formal risk acceptance decisions IAW CDRL A055, Safety Analysis Report (SAR). This SAR shall include hazards that were identified and eliminated, and specific procedural controls and precautions to be followed to mitigate the risks of hazards that could not be eliminated. The SAR shall be delivered IAW with MIL-STD-882E and DI-SAFT-80102C. The SAR shall address each vessel's STS systems and subsystems

C.3.6.1.3 Health Hazard Analysis (HHA). The contractor shall perform, document, and deliver a Health Hazard Analysis (HHA) IAW CDRL A056, HHA, that includes evaluations of the potential effects resulting from exposure to hazards, to evaluate proposed hazardous materials and processes using such materials, and to propose measures to eliminate the hazards or reduce the associated risks when the hazards cannot be eliminated MIL-STD-882E and DI-SAFT-80102C.

C.3.6.2 Environmental Compliance.

The contractor shall ensure that all aspects of contract execution in this agreement are in compliance with applicable International, United States Federal, State, interstate and/or local environmental regulations and requirements. Such regulations, conditions, or instructions in effect or prescribed by any International, Federal, State, interstate or local governmental agency are hereby made a condition of this Agreement. The contractor shall immediately notify the COR if the Government gives any instruction or direction the contractor believes may result in violation of applicable law(s) and/or regulation(s). For contractor activities conducted at a Government facility or installation, the contractor shall immediately notify the Government of any nonconformance and/or noncompliance related to this Performance Work Statement (PWS).

C.3.6.3 Hazardous Materials Management.

For the purposes of this contract, hazardous materials are defined by FED-STD-313. A Radioactive material is any source material, as defined by Title 10, Code of Federal Regulations, Part 40, “Domestic Licensing of Source Material”, in excess of 0.05 percent by weight. Specific prohibited hazardous materials are identified in section C.3.6.3.1. Prohibited materials requirements shall apply to all components, parts, and materials provided under this contract, including items purchased through a subcontractor or supplier, COTS components, OEM parts, and manufactured parts.

C.3.6.3.1 Prohibited Materials.

Prohibited materials (including alloys containing prohibited materials) shall not be present in or on any delivered STS systems, subsystems or support equipment, required for operation and sustainment, or used in final manufacture and assembly processes. The following are prohibited materials: asbestos, beryllium, Class I and Class II Ozone Depleting Substances (ODS), hydrofluorocarbons (HFCs), hexavalent chromium, cadmium, mercury, lead, radioactive materials, and other Group 1 Agents classified as "carcinogenic to humans" by the International Agency for Research on Cancer (IARC) Monographs.

The following exceptions are allowed without prior approval from the Government:

· Cadmium and hexavalent chromium on electrical connectors and back shells used to mate with cadmium electrical connectors on Government Furnished Equipment (GFE)

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

· Products listed under "Priming" and "Top-coating" in MIL-DTL-53072, Table I

· Lead-acid batteries

· Lead in engine bearings

· Lead solder

· Leaded battery terminal adaptors/clamps

· Silica used in adhesives and sealants

· Fuels specified for use in the requirements of this contract

· 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

· Mercury containing components compliant with European Union (EU) Directive

· 2011/65/EC (RoHS 2)

· HFCs in fire extinguishing systems in crew-occupied spaces

· 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.6.3.6.2 Prohibited Materials Waivers.

Waivers from the prohibited materials requirements shall not be permissible except where a suitable alternative does not exist. The Contractor shall provide a list of anticipated waiver requests at PDR. The Contractor shall submit waiver requests to the COR no later than the 30 days prior to CDR using Attachment 0006, Request for Use of Prohibited Materials. Waiver requests shall include detailed technical justification for the use of prohibited hazardous materials. The Government will make the final determination on whether sufficient justification has been provided to support approval of any waiver requests. Government response will be provided to the Contractor within 15 days of receiving sufficient justification for the waiver request. The Contractor shall not deliver any items containing prohibited materials without the Government approval of the waiver request. This includes purchased parts or components such as fasteners, electrical connectors, and lubrication fittings.

C.3.7 Human Systems Integration.

The contractor shall follow best human factors engineering practices during the design and/or modification of the system and/or its components including the application of established design standards contained in MIL-STD-1472H and MIL-STD-1474. The contractor shall perform and deliver a Human Factors Engineering Assessment (HFEA) of each vessels STS systems and subsystems IAW CDRL A057, Scientific and Technical Report. The HFEA shall describe the status of the system’s human factors engineering program and contain adequate data to support the contractor’s assertions that the system meets the human factors engineering specifications for the Milestone Decisions and Design Reviews.

C.3.8 Hazardous Materials Management Report (HMMR).

For Task Order required to follow the AWS engineering process per section C.3.2, the contractor shall prepare an HMMR IAW CDRL A058 (HMMR) and Attachment 0003 (HMMR Format). The contractor shall discuss status, changes, or issues with the HMMR as part of Program Management Reviews.

C. 4.0 Configuration Management

The contractor shall have a Configuration Management (CM) program implemented at contract award and shall comply with the requirements in SAE Electronics Industry Alliance (EIA)-649-1, this contract, corresponding CDRLS, Attachment 0001 (CM), and applicable Task Orders.

C. 4.1 Engineering Change Proposal (ECP)

When required by the Task Order, the contractor shall submit ECPs IAW CDRL A005, (ECP).

C. 4.2 Engineering Release Record (ERR)

When required by the Task Order, the contractor shall submit ERRs IAW CDRL A009 (Engineering Release Record).

C. 4.3 Government Format Production Level Technical Data Package (TDP)

When required by a Task Order the contractor shall prepare and deliver a Government Format Production Level TDP consisting of 3-D models, 2-D Computer-Aided Design (CAD) drawings, and pdf drawings, as described in MIL-STD-31000 (Level III) and IAW CDRL A007 (Product Drawings/Models & Associated Lists) and Attachment 0002 (TDP Requirements). Per this contract, the terms "technical data package" and "TDP" mean technical data and computer software and computer software documentation. Detail, subassembly and assembly drawings shall be completely delineated, directly or by reference to other documents. Prepared engineering drawings and associated lists shall provide the necessary design, engineering, manufacturing, and quality assurance information sufficient to procure or manufacture an item that duplicates the physical and performance characteristics of the original prototype, without additional design engineering effort or recourse to the original design activity. The contractor shall provide all CAD data in native AutoCAD format except when revising existing CAD originally created in a different format such as CREO. The CAD computer software version shall be mutually agreed upon by Government and the contractor at Start of Work meeting. The contractor shall obtain written or email concurrence by the PCO prior to usage of any other CAD format. The contractor shall provide CAD files which successfully pass the quality checks and the Windchill release process defined in the modeling standards documented in Attachment 0002 (TDP Requirements). The Government’s Product Lifecycle Management (PLM) computer software product, (https://ace2.tacom.army.mil/index.html), referred to as Windchill, contains the latest solid model associated CAD files and associated program support documents. All technical data delivered to the Government with asserted limited or restricted rights, the contractor shall deliver a version of the technical data with unlimited or unrestricted rights, to use, modify, reproduce, release, perform, display, or disclose the technical data, as well as permit others to do so, per C.1.0.16

C. 4.3.1 Product and Enterprise Identifiers and Drawings

The contractor shall adhere to the requirements for product and enterprise identifiers in accordance with EIA-649-1 for all products and their Product Configuration Documentation (PCD). The following paragraphs apply for all technical data and computer software to be delivered.

C. 4.3.1.1 Part or Identifying Numbers

The Government is the Original Design Activity for all products developed under this contract or any previous Government contract. For the Government Format Production Level TDP the contractor shall request a range of Government issued Part or Identifying Numbers (PINs), synonymous with Army Ordnance Part Numbers (AOPNs), from the PdM AWS Configuration Manager. The contractor shall report on their PIN usage in accordance with CDRL A011, Configuration Status Accounting Information Report. The CAGE code shall be 19207. The contractor shall request additional Government-issued PINs by e-mail as needed. The contractor shall request and assign a 7-character Government PIN (i.e., 87TXXXX) for the any end item and top level assembly model and drawing needed. The contractor shall obtain the 87TXXXX number prior to any provisioning, Tech Manual preparation, part marking, labeling, or other activity that utilizes an end item part number. The 87TXXXX number with CAGE code 19207, shall be the end item identifier used for all engineering, logistics and maintenance activities.

C. 4.3.1.2 Pre-Existing, New, and Modified Products

The contractor shall adhere to the product and enterprise identifier requirements to identify new and modified…