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

Cost Plus Fixed Fee

0002 2022DEC20

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

JESSICA D. WITTENBERG

EMAIL: JESSICA.D.WITTENBERG.CIV@ARMY.MIL

W56HZV-22-R-0062

2022DEC02

X

X 2023JAN18 01:00pm

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 49

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: JESSICA D. WITTENBERG

Buyer Office Symbol/Telephone Number: CCTA-HTA-A/(586)282-4010

Type of Contract 1: Cost Plus Fixed Fee

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of Amendment 0002 to Solicitation W56HZV-22-R-0062 is as follows:

1. Extend the closing date to 18 January 2023 at 1:00PM Local Warren, MI time.

2. Revise the language in Section A.11.1 as follows:

FROM: Questions/comments regarding this solicitation shall be submitted to the email addresses listed below NLT close of business, Wednesday, January 04, 2023.

TO: Questions/comments regarding this solicitation shall be submitted to the email addresses listed below NLT close of business, Monday, January 16, 2023.

3. Revise Section C.1.0.7, and move Pearl Harbor from CONUS to OCONUS.

4. Revise Section L of the solicitation as follows:

FROM:

L.4.1.2 Subfactor 1: Watercraft Vessel Subsystem Design and Development.

In order to substantiate technical experience in Army Watercraft vessel subsystem design and development, the offeror shall submit one recent contract to demonstrate comparable technical experience. For each contract submitted, the offeror shall provide: ____

TO:

L.4.1.2 Subfactor 1: Watercraft Vessel Subsystem Design and Development.

In order to substantiate technical experience in Army Watercraft vessel subsystem design and development, the offeror shall submit one recent contract to demonstrate comparable technical experience. For the contract submitted, the offeror shall provide: ___

5. Add Section L.4.2.2.1 (a) as follows:

The offeror shall identify whether program management is treated as a direct or indirect cost in accordance with its accounting system.

If program management is treated as a direct cost, then incorporate the program management rates into each fully-burdened labor rate included in Attachment 0012 - GFPM.

6. Revise Attachment 0011 - Technical Experience Matrix as follows:

a. The Three citations have been corrected to one citation in the Subfactor 1 tab so that it is in accordance with the language in

Section L.4.1.2, which states to submit one recent contract.

b. The citations in the Subfactor 2 tab have been updated to include a fourth and fifth contract column so that it is in accordance with Section L.4.1.3.1.

7. Revise Attachment 0012 - GFPM as follows:

a. Labor Overhead columns are created for each Labor Category.

*Due to this revision, the instructions tab was updated as well.

b. The Minimum qualifications tab of the GFPM has been updated.

8. Remove Clause 52.222-41 Service Contract Labor Standards from the solicitation.

9. Except as provided herein, all other terms and conditions of this solicitation remain unchanged.

2 49

W56HZV-22-R-0062

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

*** END OF NARRATIVE A0003 ***

A.1 Background and Description of Action.

A.1.1 Executive Overview & Objectives.

The Product Directorate (PD) of Army Watercraft Systems (AWS) requires System Technical Support (STS) services to the current fleet of vessels within the Continental United States (CONUS) and Outside the Continental United States (OCONUS). The PD AWS Performance Work

Statement (PWS) requires the contractor to provide services on technical and programmatic issues. The contractor shall provide the qualified personnel, equipment, supplies, facilities, transportation, tools, materials, and supervision necessary to perform the services as defined in this PWS, except for those items specified as Government Furnished Property, Equipment, or Services.

A.1.2 Program Office Background.

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

- Landing Craft: Logistics Support Vessel (LSV), Landing Craft Utility (LCU-2000), Landing Craft

Mechanized (LCM-8) Mod I, Maneuver Support Vessel (Light) MSV(L)

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

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

- Watercraft operations support: LCM-8 Mod II.

These systems and sub-systems require continued support, including: design and application of development and correction of technical data; and configuration management.

A.2 Acquisition Approach and Structure.

A.2.1 U.S. Army Contracting Command Detroit Arsenal (ACC-DTA) intends to award a Cost-Plus-Fixed-Fee (CPFF), Single Award, Indefinite

Delivery, Indefinite Quantity (IDIQ) contract consisting of five ordering periods. This contract will provide for the execution of Task

Orders for requirements within the general scope of the IDIQ contract. The work awarded for each Task Order will be CPFF Term (also known as Level-of-Effort (LOE)) or Completion, based on individual requirements. Material and travel will be on a Cost, No Fee (CNF) basis only.

In accordance with (IAW) Federal Acquisition Regulation (FAR) 16.504(a)(4)(ii), the minimum quantity of services the Government will order against this contract is $10,000.00.

A.2.2 Contract Performance beyond Ordering Period Expiration.

Under this effort, there are five defined 12-month ordering periods. In the event that the Government issues a Task Order in the fifth

Ordering Period, the Period of Performance (PoP) for that effort may continue beyond the expiration of the fifth Ordering Period in accordance with FAR 52.216-22(d).

A.3 North American Industry Classification Systems (NAICS) Code.

The Government will use NAICS code 541330, Engineering Services except Marine Engineering and Naval Architecture, for this requirement as it encompasses the preponderance of the work expected under the contract.

A.4 Evaluation of Proposal(s).

A.4.1 Section L of this RFP provides information and instructions for proposal preparation.

A.4.2 Section M of this RFP describes how the Government will evaluate proposal(s) for award.

A.4.3 The Government will evaluate all offeror(s) responding to the RFP using the criteria stated in Sections L and M.

A.5 Warren Electronic Contracting.

(a) All ACC-DTA solicitations are publicized on The System for Award Management website (https://www.sam.gov ). Any additional attachments, including Technical Data Packages (TDPs) when available electronically, will be separate attachments or links embedded in the solicitation.

(b) Note to offerors: Please pay close attention to the solicitation closing date and time as stated on the cover page of this solicitation, local time for the Army contracting Command Detroit Arsenal , (ACC-DTA), Michigan. In accordance with FAR 15.208(a), 3 49

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

offerors are responsible for submitting proposals, and any revisions, and modifications, to be received by the Government office designated in the solicitation by the time specified. It is the responsibility of the offeror to ensure the proposal/quote is received by the date and time specified on the cover page of this solicitation. In accordance with FAR 15.208, if the proposal/quote was not received at the initial point of entry to the Government infrastructure by the exact date and time specified on the cover page of this solicitation, it will be determined late. Proposal/quote is defined to mean ALL volumes or parts required in the solicitation are included in the electronic submission.

(c) Any award issued as a result of this solicitation will be distributed electronically. In the event of a FOIA request for a copy of any award issued as a result of this solicitation, or any subsequent modifications to the contract, the contract and modifications will be released, including the awarded unit price. This is the notice required by Executive Order 12600 (June 23, 1987) of our intention to release unit prices in response to any request under the Freedom of Information Act (FOIA), 5 USC 552. Unit price is defined as the contract price per unit or item purchased as it appears in Section B of the contract and is NOT referring to nor does it include Cost or

Pricing data/information. If you object to such release in the base contract or contract modifications, and you intend to submit an offer, notify the contracting officer in writing prior to the closing date identified in this solicitation and include the rationale for your objection consistent with the provisions of FOIA. A release determination will be made based on rationale given.

(d) Questions pertaining to this solicitation should be directed to the Contract Specialist identified in Block 10 on the cover page of this solicitation. For technical assistance in doing business with the Government, and doing business electronically, please visit the

Procurement Technical Assistance Center (PTAC) website at http://www.aptac-us.org/ to locate a regional center.

A.6 ACC-DTA Ombudsperson.

Information regarding the Ombudsperson for this contract is located at the following website:

http://acc.army.mil/contractingcenters/acc-wrn/CompMgmtOffice.html .

A.7 Notice of Elevated Threat Level Force Protection Condition (FPCON).

Contractors are hereby notified that there is a potential impact on contractor performance during increased FPCON during periods of increased threat. During FPCONs Charlie and Delta, services may be discontinued/postponed due to higher threat. Services will resume when FPCON level is reduced to level Bravo or lower.

A.8 Notice of Random Antiterrorism Measures Program (RAMP).

In accordance with AR 525-13, Contractor personnel working on an Army installation, arsenal, base or other DoD facility (owned or leased by DoD/Department of the Army), are subject to participation in Installation RAMP security program (e.g. vehicles searches, wearing of

ID badges, etc.).

A.9 Acknowledgement of Amendments.

Acknowledge all the amendments you've received from us by identifying the amendment number and its issue date in the box below:

Amendment # Date

A.10 All or None.

Offers in response to this solicitation must be submitted for the total quantity of the items identified in the solicitation.

(1) ONLY ONE AWARD WILL BE MADE AS A RESULT OF THIS SOLICITATION.

(2) OFFERS SUBMITTED FOR LESS THAN THE TOTAL QUANTITIES OF ALL THE ITEMS IN THIS SOLICITATION ARE INELIGIBLE FOR AWARD.

A.11 Question-and-Answer Period.

A.11.1 Questions/comments regarding this solicitation shall be submitted to the email addresses listed below NLT close of business, Monday, January, 16, 2023. All questions must be in the body of the email. Any questions submitted via attachment to an email will not be accepted; questions submitted via attachment will be returned back to the sender to be resubmitted. Mail to

"brandon.a.labonty.civ@army.mil", nicole.m.gram.civ@army.mil, and "jessica.d.wittenberg.civ@army.mil".

A.11.2 Any questions/comments regarding the solicitation submitted after the above date may not be answered.

A .12 Overview of Section J Attachments.

A.12.1 Due to formatting restrictions within the Government's contract writing system, the Government is unable to physically

4 49

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

incorporate some attachments directly into the solicitation. Therefore, some attachments will be provided as a separate attachment, retrievable thru SAM.gov

A.12.2 An overview of all exhibits and attachments, and whether they are incorporated within or provided as an external attachment to the solicitation is as follows; additionally, the attachments that are for evaluation purposes only are annotated accordingly:

Exhibit A CONTRACT DATA REQUIREMENTS LIST

Attachment 0001 CONFIGURATION MANAGEMENT

Attachment 0002 TDP REQUIREMENTS*

Attachment 0003 HMMR FORMAT

Attachment 0004 FAILURE MODES EFFECTS AND CRITICALITY ANALYSIS*

Attachment 0005 NON-DISCLOSURE AGREEMENT

Attachment 0006 REQUEST FOR USE FOR PROHIBITED MATERIALS

Attachment 0007 PREP FOR SHIPMENT AND STORAGE (ATPD 2232)

Attachment 0008 PERFORMANCE REQUIREMENTS SUMMARY*

Attachment 0009 ACRONYM LIST

Attachment 0010 COPYRIGHT RELEASE LETTER TEMPLATE

Attachment 0011 TECHNICAL EXPERIENCE MATRIX*^

Attachment 0012 PRICING MATRIX*

Attachment 0013 SMALL BUSINESS PARTICIPATION WORKBOOK*^

Attachment 0014 SMALL BUSINESS PARTICIPTATION WORKBOOK INSTRUCTIONS*^

Attachment 0015 CERTIFICATION OF SB SIZE AND SOCIOECONOMIC STATUS FOR

PROPOSED SUBS NOT IN SAM*^

Attachment 0016 PREAWARD SURVEY OF PROSPECTIVE CONTRACTOR ACCOUNTING SYSTEM*^

Attachment 0017 SUMMARY SHEET FOR TASK ORDER 0001 AGAINST THE AWS STS

CONTRACT*^

Attachment 0018 TO 0001 ATTACHMENT 1, PERFORMANCE WORK STATEMENT (PWS)+

Attachment 0019 TO 0001 ATTACHMENT 2, CONTRACT DATA REQUIREMENTS LIST

(CDRLS)+

* Exhibit/Attachment is provided as an external attachment to the solicitation

^ Attachment is for evaluation purposes only and will not be incorporated into the awarded contract

+ Attachment will be incorporated into TO 0001

A.13 Clauses

AS7526 NOTICE OF ELEVATED THREAT LEVEL FORCE PROTECTION CONDITION (FPCON)

Contractor is hereby notified that there is a potential impact on contractor performance on during increased FPCON during periods of increased threat. During FPCONs Charlie and Delta, services may be discontinued / postponed due to higher threat. Services will resume when FPCON level is reduced to level Bravo or lower.

*** END OF NARRATIVE A0001 ***

5 49

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 technical data, when required. 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

6 49

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

OCONUS:______

Pearl Harbor, Hawaii

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;

7 49

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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, 8 49

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

9 49

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

10 49

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

11 49

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 deliver 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 deliver 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 deliver a formal ECP. Following the PRR, the contractor shall deliver meeting minutes IAW CDRL A003 (Report, Record of Meeting/Minutes). Following successful completion of the PRR, the contractor shall prepare and deliver 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 deliver 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 deliver an E3IA Report (E3IAR) IAW CDRL

A059 (E3IAR).

C. 3.3.2 Spectrum Supportability Risk Assessment (SSRA)

12 49

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 deliver 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 deliver 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 deliver 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 deliver 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 deliver an E3VR IAW CDRL A066 (E3VR).

C. 3.5.1.6 Electromagnetic Interference Survey (EMIS) Test Procedures.