SOW CRS-CRNAV.docx

STATEMENT OF WORK (SOW)

FOR

CRS and CRNAV SOFTWARE ACCESS AND SUPPORT SERVICES

1.0 GENERAL

1.1 BACKGROUND

The purpose of this acquisition is to provide US Coast Guard access to data and specialized engineering software used in sustainment and acquisition of USCG Cutters and boats.

1.2 SCOPE

The contractor will provide US Coast Guard access to data and specialized engineering software used in sustainment and acquisition of USCG Cutters and boats. This access is provided through the Cooperative Research Navies (CRNAV) Dynamic Stability Joint Industry Government Project and Cooperative Research Ships (CRS) Joint Industry Government Project software suites.

The CRNAV dynamic stability software includes codes for nonlinear larger amplitude vessel motion predictions. The software products are used to apply stability criteria and provide operator guidance in heavy weather for both intact and damaged ships, including naval ships and Coast Guard cutters.

The CRS software provides applied naval architecture tools that address:

· SHIP STRUCTURE / FATIGUE LOADS

· COMPOSITE PROPELLERS

· MANEUVERING OPERATIONS REQUIREMENTS AND CRABBING ASSESSMENT IN EARLY DESIGN STAGE

· PROPELLER EFFICIENCY AND LOADS

· ADDED RESISTANCE IN WAVES

· IMPROVE FULL SCALE CFD PREDICTIONS BY ONCLUDING SURFACE ROUGHNESS.

· SCALE EFFECT ON TRAMSOM FLOW AND RESISTANCE.

· SREENING AND PREDICTION OF EXTREME CONDITIONS OF HEAVY SEAS IN CFD.

· ANTI ROLL TANK RESPONSE PREDICTION

1.3 OBJECTIVE

The specialized engineering software and validation data provided through this solicitation will support USCG acquisition and sustainment programs by improving analyses of vessel performance, lowering technical risks, and increasing efficiencies.

2.0 SPECIFIC REQUIREMENTS/TASKS

2.1 TASK ONE. CRNAV DYNAMIC STABILITY SOFTWARE ACCESS and SUPPORT

2.1.1 The contractor shall provide access to the CRNAV software suite, which includes FREDYN, Long Run Extreme Value Load Estimation Interactive (LORELEI), Flexible Analysis Method for Extreme Response (FAME), and FREDYN Database Viewer (FDBviewer).

2.1.2 The contractor shall maintain the software, including providing regular updates, technical support, bug fixes, and issue resolution.

2.2 TASK TWO. CRS SOFTWARE ACCESS AND SUPPORT

2.2.1 The contractor shall provide access to the CRS software suite, which includes Structural Loads (STRUC_R), Hull Pressure Calculation (PRECAL), Crabbing Near Quays (COGNAC), AMG Automatic Mesh Generator, Ship motion responcse in waves (SEACAL), Anti-Roll tank response prediction (ART), Seakeepng in high states including slamming/whipping response (PERTTI_R), manouering asseemnet in earlydesign stage (MPP), Maneuvering in Waves (MANWAV), Stress and Vibration analysis, of structures (TRIDENT-VAST), Acoustic Radiation and scattering in frequency domain (EXCALIBUR), Fluid Structure interaction analysis of flexible propellers (COMPPROPAPP), Scale single and twin screw ship wake (nominal & effective) to full scale (PIF-WAKE), and propeller analysis, design and optimization tol box (PROPART)

2.2.2 The contractor shall maintain the software, including providing regular updates, technical support, bug fixes, and issue resolution.

3.0 CONTRACTOR PERSONNEL

3.1 QUALIFIED PERSONNEL

The Contractor must provide qualified personnel to perform all requirements specified in this SOW.

3.2 CONTINUITY OF SUPPORT

The Contractor must ensure that the contractually required level of support for this requirement is maintained at all times. The Contractor must ensure that all contract support personnel are present for all hours of the workday. If for any reason the Contractor staffing levels are not maintained due to vacation, leave, appointments, etc., and replacement personnel will not be provided, the Contractor must provide e-mail notification to the Contracting Officer’s Representative (COR) prior to employee absence. Otherwise, the Contractor must provide a fully qualified replacement.

4.0 OTHER APPLICABLE CONDITIONS

4.1 SECURITY

Contractor access to unclassified, but Security Sensitive Information may be required under this SOW. Contractor employees must safeguard this information against unauthorized disclosure or dissemination.

4.2 PERIOD OF PERFORMANCE

The period of performance for this contract is one (1) 12- month base period and four (1) 12-month option periods (OY) from date of award (Contractor Phases 13-14).

4.3 PLACE OF PERFORMANCE

The primary place of performance will be the Contractor’s facilities.

4.4 HOURS OF OPERATION

There is no specific operational hour requirement for software access. The software shall be available for use 24 hours a day, 7 days a week, except during necessary maintenance periods. Any scheduled maintenance that may impact software availability should be communicated to the COR at least 48 hours in advance.

4.5 TRAVEL

Contractor travel is not required for the performance of this contract. All services, including software access, maintenance, and any necessary support, shall be provided remotely. If an unforeseen circumstance arises where travel might be considered, it must be approved in advance and in writing by the COR.

4.6 POST AWARD CONFERENCE

The Contractor must attend a Post Award Conference with the Contracting Officer and the COR no later than 10 business days after the date of award. The purpose of the Post Award Conference, which will be chaired by the Contracting Officer, is to discuss technical and contracting objectives of this contract and review the Contractor's project plan. The Post Award Conference will be held via teleconference.

4.7 PROJECT PLAN

The Contractor must provide a Project Plan after the Post Award Conference for Government. The plan, at a minimum, must include: (a) list of work to be performed;(b) project schedule; (c) description of intended results;. The Contractor must provide a final Project Plan to the COR not later than 20 business days after the date of award. An updated version of the proposal may meet the requirements of the project plan.

4.8 BUSINESS CONTINUITY PLAN

Not required.

4.9 PROGRESS REPORTS

The Project Manager must provide progress reports as deliverables are developed to the Contracting Officer and COR via electronic mail or posting to contrator’s sharepoint site. This report must include a summary of all Contractor work performed, including an assessment of technical progress, schedule status, and any Contractor concerns or recommendations for the previous reporting period.

4.10 PROGRESS MEETINGS

The Project Manager must be available to meet with the COR upon request to present deliverables, discuss progress, exchange information and resolve emergent technical problems and issues. These meetings must take place via teleconference.

4.11 GENERAL REPORT REQUIREMENTS

The Contractor must provide all written reports in electronic format with read/write capability using applications that are compatible with DHS workstations (Microsoft Office Applications).

4.12 INTELLECTUAL PROPERTY

The contractor shall provide the U.S. Coast Guard with a non-exclusive, non-transferable license to use the software specified in this Statement of Work for the duration of the contract period. This license shall permit use of the software by authorized U.S. Coast Guard personnel for official purposes related to vessel sustainment and acquisition.

The contractor shall provide documentation of all relevant software licenses, including any third-party software incorporated into the systems provided. Any limitations on use, number of users, or other relevant restrictions shall be clearly specified.

4.13 PROTECTION OF INFORMATION

The U.S. Coast Guard shall retain ownership of all data input into the software systems and any outputs generated using the software suite outlined in this Statement of Work. This includes analytical results, reports, and any derivative works created using the software.

The contractor shall not use, share, or distribute any U.S. Coast Guard data without explicit written permission from the authorized U.S. Coast Guard representative. This restriction applies during the contract period and continues after the contract’s conclusion.

The contractor shall implement appropriate safeguards to protect U.S. Coast Guard data from unauthorized access, use, or disclosure. Upon contract termination or expiration, the contractor shall return or securely destroy all U.S. Coast data in their possession, as instructed by the Contracting Officer’s Representative.

Any contractor personnel with access to the U.S. Coast Guard data shall be made aware of these requirements and shall handle the data in accordance with applicable U.S. Coast Guard security policies and procedures.

4.14 SECTION 508 COMPLIANCE

Section 508 of the Rehabilitation Act (classified to 29 U.S.C. § 794d) requires that when Federal agencies develop, procure, maintain, or use information and communications technology (ICT), it shall be accessible to people with disabilities. Federal employees and members of the public with disabilities must be afforded access to and use of information and data comparable to that of Federal employees and members of the public without disabilities.

All products, platforms and services delivered as part of this work statement that, by definition, are deemed ICT shall conform to the revised regulatory implementation of Section 508 Standards, which are located at 36 C.F.R. § 1194.1 & Appendixes A, C & D, and available at https://www.ecfr.gov/cgi-bin/text- idx?SID=e1c6735e25593339a9db63534259d8ec&mc=true&node=pt36.3.1194&rgn=div5. In the revised regulation, ICT replaced the term electronic and information technology (EIT) used in the original 508 standards. ICT includes IT and other equipment.

Exceptions for this work statement have been determined by DHS and only the exceptions described herein may be applied. Any request for additional exceptions shall be sent to the Contracting Officer and a determination will be made according to DHS Directive 139-05, Office of Accessible Systems and Technology, dated November 12, 2018 and DHS Instruction 139-05- 001, Managing the Accessible Systems and Technology Program, dated November 20, 2018, or any successor publication.

5.0 GOVERNMENT FURNISHED RESOURCES

The Government will not furnish any resources to the Contractor in support of this contract.

6.0 CONTRACTOR FURNISHED PROPERTY

The Contractor must furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract, except for the Government Furnished Resources specified in SOW 2.0 and SOW 5.0.

7.0 GOVERNMENT ACCEPTANCE PERIOD

The COR will review deliverables prior to acceptance and provide the contractor with an e-mail that provides documented reasons for non-acceptance within ten (10) business days. If the deliverable is acceptable, the COR will send an e-mail to the Contractor notifying it that the deliverable has been accepted within 10 business days

7.1 The COR will have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the Contractor’s accepted proposal. In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection within 10 business days. The Contractor may have an opportunity to correct the rejected deliverable and return it per delivery instructions within 10 business days.

7.2 The COR will have 10 business days to review deliverables and make comments. The Contractor must have 10 business days to make corrections and redeliver.

7.3 All other review times and schedules for deliverables must be agreed upon by the parties based on the final approved Project Plan. The Contractor must be responsible for timely delivery to Government personnel in the agreed upon review chain, at each stage of the review. The Contractor must work with personnel reviewing the deliverables to assure that the established schedule is maintained.

8.0 DELIVERABLES

DISTRIBUTION

Updates

COR

COR

2.1, 4.11 CRNAV Working Group Reports, Minutes of Meetings, Presentations, and other related documents

14 calendar days after meetings

2.1, 4.11

COR

2.2, 4.11 CRS Working Group Reports, Minutes of Meetings, Presentations, Measurements, and other related documents

14 calendar days after meetings

2.2, 4.11

COR

8.1 METHOD AND PLACE OF DELIVERY-DESTINATION

(a) All deliverables must be delivered by one of the following two methods: Electronic mail to:

Michael.M.Nader@USCG.MIL

(b) FOB destination by traceable means on a Digital Versatile Disc (DVD) to: USCG SFLC ESD 707 E. Ordnance Rd. Baltimore, MD 21226 ATTN: Michael Nader

LAST UPDATED: 06/10/2025 PAGE 8/17