W56HZV-16-R-0086_Amendment_0001_(released_Feb_23,_2018).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

0001 2018FEB23

W56HZV

U.S. ARMY CONTRACTING COMMAND

WARREN, MICHIGAN 48397-5000

MATTHEW FITZSIMMONS

EMAIL: MATTHEW.T.FITZSIMMONS.CIV@MAIL.MIL

W56HZV-16-R-0086

2018JAN16

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 48

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: MATTHEW FITZSIMMONS

Buyer Office Symbol/Telephone Number: CCTA-HSW-S/(586)282-3596

Type of Contract 1: Cost Plus Fixed Fee

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

1. The purposes of Amendment 0001 to solicitation W56HZV-16-R-0086 are to revise sections C, E, I, J, L, and M as follows:

a. Section C, "Description/Specifications/Work Statement" ______________________________________________________

i. Paragraph C.3.2 has been revised as follows:

FROM: When required by a Task Order, the contractor shall develop engineering changes to be applied to PdD 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 PdD 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.1 and C.3.2.2) shall be completed for all engineering changes unless otherwise directed by a Task Order. The rest of the process (C.3.2.3 thru C.3.2.6), when required, will be specified in the applicable Task Order.

TO: When required by a Task Order, the contractor shall develop engineering changes to be applied to PdD 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 PdD 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.1 and C.3.2.2) shall be completed for all engineering changes unless otherwise directed by a Task Order. The rest of the process (C.3.2.3 thru C.3.2.5), when required, will be specified in the applicable Task Order. _______

b. Section E, "Inspection and Acceptance" ______________________________________

i. Paragraph E.3 has been revised as follows:

FROM: The contractor shall have a subcontractor/supplier quality assurance program that requires its subcontractors and suppliers to be compliant with ISO 9001-2000, at a minimum. The contractor's subcontractor/supplier quality assurance program shall assure each subcontractor and supplier has a documented quality system, which includes development, implementation, and maintenance of control plans for all components produced under this contract. The contractor's subcontractor/supplier quality assurance plan shall be available for Government review.

TO: The contractor shall have a subcontractor/supplier quality assurance program that requires its subcontractors and suppliers to be compliant to ISO 9001:2015 or an industry recognized ___________________________________________ equivalent standard, at a minimum. The contractor's subcontractor/supplier quality assurance____________________ program shall assure each subcontractor and supplier has a documented quality system, which includes development, implementation, and maintenance of control plans for all components produced under this contract. The contractor's subcontractor/supplier quality assurance plan shall be available for Government review.

c. Section I, "Contract Clauses" _____________________________

i. Removed clause 52.222-41, SERVICE CONTRACT LABOR STANDARDS

ii. Removed clause 52.222-43, FAIR LABOR STANDARDS ACT AND SERVICE CONTRACT LABOR STANDARDS--

PRICE MAY/2014 ADJUSTMENT (MULTIPLE YEAR AND OPTION CONTRACTS)

2 48

W56HZV-16-R-0086 0001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

iii. Revise clause 52.216-19, ORDER LIMITATIONS:

FROM: (a) Minimum order. When the Government requires supplies or services covered by this contract in an amount of less than -1-, the Government is not obligated to purchase, nor is the

Contractor obligated to furnish, those supplies or services under the contract.

(b) Maximum order. The Contractor is not obligated to honor --

(1) Any order for a single item in excess of $15M;

(2) Any order for a combination of items in excess of $45M; or

(3) A series of orders from the same ordering office within 30 days that together call for quantities exceeding the limitation in subparagraph (b)(1) or (2) of this section. (c) If this is a requirements contract (i.e., includes the Requirements clause at subsection 52.216-21 of the

Federal Acquisition Regulation (FAR)), the Government is not required to order a part of any one requirement from the Contractor if that requirement exceeds the maximum-order limitations in paragraph (b) of this section. (d) Notwithstanding paragraphs (b) and (c) of this section, the

Contractor shall honor any order exceeding the maximum order limitations in paragraph (b), unless that order (or orders) is returned to the ordering office within 15 days after issuance, with written notice stating the Contractors intent not to ship the item (or items) called for and the reasons. Upon receiving this notice, the Government may acquire the supplies or services from another source.

TO: (a) Minimum order. When the Government requires supplies or services covered by this contract in an amount of less than $10,000, the Government is not obligated to purchase, nor is _______ the Contractor obligated to furnish, those supplies or services under the contract.

(b) Maximum order. The Contractor is not obligated to honor --

(1) Any order for a single item in excess of $47M; ____

(2) Any order for a combination of items in excess of $47M; or ____

(3) A series of orders from the same ordering office within 30 days that together call for quantities exceeding the limitation in subparagraph (b)(1) or (2) of this section. (c) If this is a requirements contract (i.e., includes the Requirements clause at subsection 52.216-21 of the

Federal Acquisition Regulation (FAR)), the Government is not required to order a part of any one requirement from the contractor if that requirement exceeds the maximum-order limitations in paragraph (b) of this section. (d) Notwithstanding paragraphs (b) and (c) of this section, the

Contractor shall honor any order exceeding the maximum order limitations in paragraph (b), unless that order (or orders) is returned to the ordering office within 15 days after issuance, with written notice stating the Contractors intent not to ship the item (or items) called for and the reasons. Upon receiving this notice, the Government may acquire the supplies or services from another source.

d. Section J, "List of Attachments" ________________________________

i. Attachment 0003 - Pricing Matrix was revised and posted to FBO.gov on February 16, 2018 under the filename

"Attachment 0003 Pricing Matrix - 1_Feb_2018"; cells B3 and B10 were unlocked on the Task Order 1 tab.

e. Section L, "Instructions, Conditions, and Notice to Offerors" _____________________________________________________________

i. Paragraph L.2.2.3 (and its subparagraphs) on page 97 has been revised as follows:

FROM: L.2.2.3 Proposal Information Instructions for Direct Submission On Behalf of the Prime

Offeror Note: These instructions are for a third party who declines to provide proposal information directly to the prime offeror for its proposal submission. A third party is defined as a party other than the Government contract agency issuing this solicitation and the prime offeror.

L.2.2.3.1 If a third party is willing to submit proposal information to the PCO on behalf of the prime offeror, that proposal information may be submitted using the same submission instructions noted above. In doing so, the third party is agreeing to the information submitted to be used as proposal information.

L.2.2.3.2 The Government contract agency for this solicitation will not communicate with any third party directly. Failure of the third party to submit the necessary proposal information, at or prior to the solicitation close date, may result in rejection of the prime offeror's proposal.

L.2.2.3.3 The third party shall submit a cover letter to clearly identify the prime offeror that the proposal submission relates to.

3 48

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

TO: L.2.5 Proposal Information Instructions for Direct Submission On Behalf of the Prime _____

Offeror Note: These instructions are for a third party who declines to provide proposal information directly to the prime offeror for its proposal submission. A third party is defined as a party other than the Government contract agency issuing this solicitation and the prime offeror.

L.2.5.1 If a third party is willing to submit proposal information to the PCO on behalf of the_______ prime offeror, that proposal information may be submitted using the same submission instructions noted above. In doing so, the third party is agreeing to the information submitted to be used as proposal information.

L.2.5.2 The Government contract agency for this solicitation will not communicate with any third_______ party directly. Failure of the third party to submit the necessary proposal information, at or prior to the solicitation close date, may result in rejection of the prime offeror's proposal.

L.2.5.3 The third party shall submit a cover letter to clearly identify the prime offeror that the_______ proposal submission relates to.

ii. Paragraph L.4.1.2 has been revised as follows:

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

TO: In order to substantiate technical experience in Watercraft vessel subsystem design and _________________ development, the offeror shall submit up to three recent contracts to demonstrate comparable technical experience. For each contract submitted, the offeror shall provide:

iii. Paragraph L.4.1.2.2 has been revised as follows:

FROM: A narrative discussion of how the recent contract's scope of work is comparable, indicating where the applicable Army Watercraft vessel subsystem design and development are located in the provided statement of work the section(s) (i.e., paragraph number, page number, etc.). If providing the recent contracts as individual files, Attachment 0010 shall specify the location in the proposal where statement of work information can be found (e.g., filename, document reference, etc.)

TO: A narrative discussion of how the recent contract's scope of work is comparable, indicating where the applicable Watercraft vessel subsystem design and development are located in the _________________ provided statement of work the section(s) (i.e., paragraph number, page number, etc.). If providing the recent contracts as individual files, Attachment 0010 shall specify the location in the proposal where statement of work information can be found (e.g., filename, document reference, etc.)

iv. Paragraphs L.4.2.5(c), L.4.2.5(e), L.4.2.5(f), and L.4.2.5(g) has been revised as follows:

FROM: c) Definitions of Engineering Levels I, II, III:

Engineering Level I: Minimum of a bachelor's degree and 0-4 years of experience

Engineering Level II: Minimum of a bachelor's degree and 5-9 years of experience

Engineering Level III: Minimum of a bachelor's degree and 10+ years of experience

e) Definitions of Logistics Levels I, II, III:

Logistics Level I: Minimum of a bachelor's degree and 0-4 years of experience

Logistics Level II: Minimum of a bachelor's degree and 5-9 years of experience

Logistics Level III: Minimum of a bachelor's degree and 10+ years of experience

f) Definition of FSR:

Minimum of a bachelor's degree and 5+ years of experience

g) Definition of OCONUS FSR:

Minimum of a bachelor's degree and 5+ years of experience

TO: c) Definitions of Engineering Levels I, II, III:

Engineering Level I: Minimum of a bachelor's degree and 0-4 years of related experience or ________ ___ employees with no bachelor's degree with at least 8 years of related experience_______________________________________________________________________________

4 48

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Engineering Level II: Minimum of a bachelor's degree and 5-9 years of related experience _______

Engineering Level III: Minimum of a bachelor's degree and 10+ years of related experience _______

e) Definitions of Logistics Levels I, II, III:

Logistics Level I: Minimum of a bachelor's degree and 0-4 years of related experience or employees _______ _____________ with no bachelor's degree with at least 8 years of related experience_____________________________________________________________________

Logistics Level II: Minimum of a bachelor's degree and 5-9 years of related experience _______

Logistics Level III: Minimum of a bachelor's degree and 10+ years of related experience _______

f) Definition of FSR:

Minimum of 5+ years of related experience ___ _______

g) Definition of OCONUS FSR:

Minimum of 5+ years of related experience __ _______

Supporting information for the completed Attachment 0003 - Pricing Matrix shall include the following:

v. Paragraph L.5 has been revised as follows:

FROM: Volume V - Administrative

TO: Volume IV Administrative __

f. Section M, "Evaluation Factors For Award" _________________________________________

i. Paragraph M.1.2 has been revised as follows:

FROM: Award will only be made to an offeror who is eligible for award. To be eligible for award:

a) The offeror must be determined responsible (See Section M.3.5); and

b) The offeror must have an adequate Cost Accounting System (See Section L.4.4.6); and

c) The proposal must not contain a Deficiency(s) (per FAR Part 15.001); and

d) The offeror shall be registered in the System for Award Management (SAM) - see provision 52.204-

7; and

TO: Award will only be made to an offeror who is eligible for award. To be eligible for award:

a) The offeror must be determined responsible (See Section M.3.5); and

b) The offeror must have an adequate Cost Accounting System (See Section L.5.5); and _____

c) The proposal must not contain a Deficiency(s) (per FAR Part 15.001); and

d) The offeror shall be registered in the System for Award Management (SAM) - see provision 52.204-

7; and

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

*** END OF NARRATIVE A0002 ***

5 48

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 Directorate (PdD) 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.____________________

PdD 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

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

c) Towing and terminal operations: Large Tug (LT-800), Small Tug (ST-900), and Barge Derrick (BD-115T); 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 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

Independence Day

Labor Day

Columbus Day

Veteran's Day

Thanksgiving Day

Christmas Day

C.1.0.6 Hours of Operation.___________________________

The contractor shall conduct business no more than 40 hours per workweek per employee inclusive of any day of the week (seven days) with no premium, except Federal holidays or when any Government facility required for contract performance closes due to local or national emergencies, administrative closings, or similar Government-directed facility closings. The contractor will not be reimbursed when the government facility is closed for the above reasons. Additionally, lunch, rest periods, and union time are not considered productive time and are not billable. If the contractor is unable to fulfill the hours required in a billing period, due to a Government-created

6 48

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

circumstance, the contractor, COR, and Contracting Officer will discuss an alternate billing arrangement on a case-by-case basis. If overtime is deemed necessary, all requests must be coordinated in advance and approved in writing by the Contracting Officer or COR.

The contractor shall maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS and individual Task Orders. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

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

Tampa, Florida

Baltimore, Maryland

Fort Eustis, Virginia

Tacoma, Washington

Moorehead City, North Carolina

Fort Belvoir, Virginia

OCONUS:

Okinawa, Japan

Kuwait City, Kuwait

Pearl Harbor, Hawaii

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: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the

Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states 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 will be required to travel CONUS and OCONUS during the performance of this contract. The contractor may be required to

7 48

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 to be acceptable solely at the discretion of the Contracting Officer, and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may effect other remedies he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which 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, Safety of Life At Sea

(SOLAS) requirements, Code of Federal Regulations (CFR) Title 46, 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)

IAW CDRL A002 (Integrated Program Management Report (IPMR)) for each Task Order, to include development of an IMP and an IMS for various

PdD AWS programs. The contractor shall use Microsoft Project 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. 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. 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 unclassified/FOR OFFICIALL USE ONLY (FOUO) 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

8 48

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Government will provide these details at the SOWM. The Government can only sponsor accounts for U.S. Citizens. All contractor and sub-contractor employees requiring access to these accounts must successfully complete the Department of Defense (DoD) Cyber Awareness

Challenge Training awareness training; this must be accomplished before approval will be given to access these accounts. The DoD Cyber

Awareness Challenge Training awareness 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 PdD 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) Automated Contractor Verification System.________________________________________________________________________

C.1.6.1 Common Access Card (CAC) Applications.______________________________________________

The contractor shall appoint an Information Assurance Officer to process CAC applications for its employees and subcontractor employees

IAW 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 the personnel and job titles, via email to the COR.

C.1.6.3 Contractor Verification System (CVS)._____________________________________________

The Government will establish a CVS 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 CVS 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 two years or the contract performance completion date (inclusive of all options), whichever is earlier. If a requirement for a CAC exists beyond two 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, PdD AWS representatives, the COR and the Contracting

Officer. The contractor shall coordinate a mutually acceptable meeting date with the COR. The contractor shall prepare and submit a proposed agenda (CDRL A002), 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 PdD AWS personnel overseeing the Task Order. The contractor shall hold Kickoff Meetings by

9 48

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

phone within 15 calendar days of award of a Task Order, unless otherwise agreed to by PdD AWS. With the Government's approval, the contractor may hold Kickoff Meetings in conjunction with other regularly scheduled PdD 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,

f) components, and assemblies,

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.

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).

10 48

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 PdD 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 PdD 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.1 and C.3.2.2) shall be completed for all engineering changes unless otherwise directed by a Task Order. The rest of the process (C.3.2.3 thru C.3.2.5*), when required, will be specified in ________ the applicable Task Order.

C.3.2.1 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.2 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.3 Preliminary Engineering Change Proposal (PECP) and Configuration Control Board (CCB) Review.______________________________________________________________________________________________________

When required by the Task Order, the contractor shall prepare a PECP and present it at the PdD AWS CCB. The PECP shall reflect the outcome of the PDR. PECPs shall be prepared IAW CDRL A005 (ECP), except that submission of Notice of Revision (NOR) and Technical Data

Packages (TDPs) are not required with PECPs. PECPs do not satisfy the requirement for a formal Engineering Change Proposal (ECP).

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.10 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.3 Technical Report._________________________

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

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, subsystems, or parts), 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 Testing.__________________

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

11 48

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.