About this file

Attachment 2 Statement of Work

View the file

Other files

File Type Posted
ASPFE-DC.wsdl WSDL file
LRIT_ASP_Solicitation_Questions_and_Responses_052715.docx DOCX document
DC-ASPFE.wsdl WSDL file
A3Tech-Requirements_Revision_1.docx DOCX document
LRIT_ASP_Solicitation_Questions_and_Responses_052115.docx DOCX document
SynopsisSolicitation_LRIT_ASP_Revision_1.docx DOCX document
A2SOW_Revision_1.docx DOCX document
A3Tech-Requirements.docx DOCX document
A1_Pricing_Spreadsheet.xlsx XLSX spreadsheet
A4PPQ.DOC DOC document
SynopsisSolicitation_LRIT_ASP.docx DOCX document
Show all 11

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

HSCG23-15-R-PCI035

TECHNICAL SUPPORT SERVICES FOR THE

U.S. COAST GUARD OFFICE OF C4 AND SENSOR CAPABILITIES

LONG RANGE IDENTIFICATION AND TRACKING

APPLICATION SERVICE PROVIDER

Statement of Work

1.0 GENERAL

1.1 BACKGROUND

The International Maritime Organization (IMO) Maritime Safety Committee (MSC), at its eighty-first session in May 2006, adopted amendments to Chapter V of the Safety of Life at Sea (SOLAS) convention in relation to Long Range Identification and Tracking (LRIT). This LRIT regulation, which entered into force on January 1, 2008, requires all ships subject to SOLAS Chapter V/19-1 to transmit LRIT. All U.S. flag vessels will be required to transmit/provide LRIT position reports, at a minimum four (4) times daily, to the U.S. National Data Center (NDC) via a U.S. “recognized” Application Service Provider (ASP). At the present time, the U.S. estimates that there are approximately 800 U.S flag vessels subject to LRIT regulations. The maximum frequency of LRIT reports is every 15 minutes. The LRIT system provides for the global identification and tracking of ships. Regulations issued by IMO, to include but not limited to the Performance Standards and Functional Requirements, Technical Specifications, and Circular 1307, detail aspects of ASP responsibilities and roles within the LRIT system. They include: messaging format between LRIT components, data security throughout the network, protocols required for transporting data from one network point to another, and conformance testing details and requirements.

1.2 SCOPE

The purpose of this firm-fixed priced contract is to obtain data services for the U.S. Coast Guard (USCG) LRIT system. The services shall include: (1) conformance tests for all U.S. flag vessels subject to the regulation, (2) integration of vessels into the LRIT system (U.S. NDC), (3) data services (position reports) for all U.S. flag vessels subject to LRIT carriage requirements, (4) 24 hours, 7 days a week ASP customer support to vessels and the USCG to include position transmission failure reporting and LRIT system / equipment troubleshooting and a phone number where the U.S. NDC or U.S. vessels may call, (5) system status messages every thirty (30) minutes between the ASP and U.S. NDC to verify component status and (6) a testing environment so that NDC and ASP software changes, or other testing instances, may be tested prior to moving them to production.

1.2.1 LRIT System Operation

Tracking of any applicable ship begins with LRIT positional data being transmitted from shipborne equipment. The LRIT information transmitted includes the ship’s Global Navigation Satellite System (GNSS) position (based on the WGS84 datum), time, and identification, as described in resolution MSC.263 (84).

The Communication Service Provider (CSP) hired by the Contractor provides the communication infrastructure and services necessary for establishing a communication path between the ship and the ASP. The LRIT information transmitted from the ship will travel across the communication path set up by the CSP to the ASP. The ASP, after receiving the LRIT information from the ship, will add information to the LRIT message and pass the expanded message to its associated LRIT NDC. The Contractor shall arrange all applicable service level agreements and financial agreements with all associated CSPs. The Contractor shall have disaster recovery and CSP failure mitigation strategies, to include a minimum of two (2) CSPs.

Functionality required for the programming and communicating of commands to the shipborne equipment is provided by the ASP. The LRIT data, along with all the parameters added by the various LRIT components, is described in the messaging section of the MSC Communications document. LRIT Data Centers store all incoming LRIT information from ships instructed by their Administrations to transmit LRIT information. LRIT Data Centers disseminate LRIT information to LRIT Data users according to the Data Distribution Plan (DDP). The LRIT DDP will contain the information required by the Data Centers for determining how LRIT information will be distributed to various Contracting Governments. The DDP will contain information such as standing orders from Contracting Governments and geographical polygons relating to Contracting Governments’ coastal waters, ports, and port facilities.

LRIT Data Centers will process all LRIT messages to and from the International LRIT Data Exchange (IDE). The IDE will process all LRIT messages between LRIT Data Centers. The IDE will route the message to the appropriate Data Center based upon the address in the message and the Internet Protocol (IP) addresses in the DDP. LRIT Data users may be entitled to receive or request LRIT information in their capacity as a Flag State, Port State, Coastal State, or Search and Rescue (SAR) services.

1.3 CONTRACTOR PERSONNEL

1.3.1 Project Manager The Contractor shall provide a Project Manager who shall be responsible for all Contractor work performed under this contract. The Project Manager is further designated as Key by the Government (see SOW 1.4).

`The Project Manager shall be a single point of contact for the Contracting Officer and the Contracting Officer’s Representative (COR) or designee. It is anticipated that the Project Manager shall be one of the senior employees provided by the Contractor for this work effort. The name of Project Manager, and the name(s) of any alternate(s) who shall act for the Contractor in the absence of the Project Manager, shall be provided to the Government. During any absence of the Project Manager, only one alternate shall have full authority to act for the Contractor on all matters relating to work performed under this contract. The Project Manager and all designated alternates shall be able to read, write, speak and understand English fluently.

1.3.1.2 The Project Manager shall be available to the COR or designee via telephone between the hours of 0730 and 1630 Eastern Time (ET), Monday through Friday, and shall respond to a request for discussion or resolution of technical problems within 12 hours of notification.

1.3.2 Qualified Personnel The Contractor shall provide qualified personnel to perform all requirements specified in this contract.

1.3.3 Employee Identification Contractor employees visiting Government facilities shall wear an identification badge that, at minimum, displays the Contractor name, the employee’s photo, name, clearance-level and badge expiration date. Visiting Contractor employees shall comply with all Government escort rules and requirements. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent and display all identification and visitor badges in plain view above the waist at all times.

1.3.4 Employee Conduct Contractor employees shall present a professional appearance while working under this contract and their conduct shall not reflect discredit upon the U.S., the Department of Homeland Security and the USCG.

1.4 KEY PERSONNEL

Before replacing any individual designated as Key by the Government, the Contractor shall notify the Contracting Officer no less than 15 business days in advance, submit written justification for replacement, and provide the name and qualifications of any proposed substitute(s). All proposed substitutes shall possess qualifications equal to or superior to those of the Key person being replaced. The Contractor shall not replace Key Contractor personnel without acknowledgment from the Contracting Officer. The Government may designate additional Contractor personnel as Key at the time of award.

1.5 SECURITY

Contractor access to classified information is not required under this contract. The vessel data / position information is sensitive but unclassified (SBU).

1.6 PERIOD OF PERFORMANCE

The period of performance for this contract is one (1) year from the date of award, with four (4) one (1) year option periods.

1.7 PLACE OF PERFORMANCE

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

2.0 REQUIREMENTS

All ASP service and functional requirements shall be performed as defined and in accordance with all applicable regulatory documents listed in section 7.0. Other applicable LRIT related documents that may also apply to the ASP service requirements including MSC Regulations and Circulars. The Contractor shall maintain copies of all current ASP related documents and provide them to the COR upon request. The Contractor shall perform all ASP service changes in accordance with any updates or changes within the LRIT system.

2.1 WEB-BASED INTERFACE WITH GEOGRAPHICAL DISPLAY CAPABILITY

The Contractor shall provide to the Government a password-protected web-based interface to access all available ASP information and data on U.S. Flag vessels. The display shall include, at a minimum, status (including current polling rate) of each vessel reporting at any given time. The web interface shall update automatically and provide basic tools to assist with technical troubleshooting of the connectivity between the ship, the Communication Service Provider (CSP), the ASP, and the U.S. NDC. The web interface shall be available no later than 60 days after contract award. This item is mandatory in the base period and optional in each option period.

2.2 CONFORMANCE TESTS AND REPORTS

2.2.1 Initiate Conformance Testing The Contractor shall begin conformance testing, in accordance with MSC.1307, no later than 5 days after the award of the contract. Testing shall be done in accordance with the USCG furnished list of ships required to undergo LRIT testing. Requests for conformance tests are received from vessel owners or operators and reviewed by the watch stander at the USCG Navigation Center. The Contractor shall perform conformance testing on U.S. flag vessels only after initial approval by the USCG Navigation Center (i.e. the watch stander).

2.2.1.1 The Contractor shall initiate conformance testing with all U.S. flag vessels at the earliest opportunity.

2.2.1.2 USCG will provide the list of ships no later than 3 days after the award of the contract.

2.2.1.3 The Contractor shall contact U.S. vessel owners, agents or operators via email or telephone calls; receive and process applicable vessel data and manage calls from U.S. flag vessels. For U.S. flag vessels that do not successfully complete conformance tests, the Contractor, to the maximum extent possible, shall identify the failed sections of the conformance test and notify the ship owner/operator/agent and the COR of its findings and recommendations. After the ship has corrected the problem with their existing equipment, if possible, or after the installation of new, upgraded or after identifying another separate piece of LRIT capable equipment installed onboard the vessel, the ASP shall re-test the same vessel at least two additional times. After three failed attempts, the ship owner/operator/agent will be responsible for any future ASP testing, unless otherwise instructed by USCG LRIT Management. Once the ship successfully completes the conformance test, a record of the report shall be sent to the COR.

2.2.2 Complete Conformance Tests The Contractor shall initiate and complete a vessel conformance test within a period of 36 hours. If the vessel is unable to pass the initial polling stage then the owner/operator is advised to seek technical assistance before trying again. If the vessel has problems in the second stage, the Contractor will continue to assist the vessel owner until the end of the 36 hours. If the test exceeds 36 hours then the owner/operator is advised to seek technical assistance before trying again. If a vessel is not ready to test or cannot complete a successful conformance test as specified in this section, the ASP shall notify the COR. The Contractor shall conduct all conformance testing, including up to three total tests per vessel during the period of performance.

2.2.3 Issue Conformance Test Reports to vessels on behalf of the U.S. The Contractor shall provide a conformance test report within 3 business days after each vessel completes a conformance test and send a copy of the report to the COR. Report shall be on ASP letterhead and contain verbiage agreed on by both the Contractor and the Government. The report shall be signed by an appropriate ASP representative that is verified by the Government. USCG will recognize the Contractor as the U.S. testing ASP with the IMO. Based on that authority, the Contractor will issue Conformance Test Reports for the USCG. The Contractor will accept previous conformance tests completed by vessels, primarily in the case of re-flagging or other similar situations, for tests completed by any U.S. Recognized ASP or testing ASP. This will include any tests conducted under previous USCG contracts until such time that the U.S. no longer recognizes the ASP or testing ASP. The Government will notify the Contractor of any changes in ASP or testing ASP recognition(s) by the U.S.

2.2.4 Position Reports Accounting U.S. vessel reporting; The Contractor shall allow for position reports with a frequency of 4 times daily under normal circumstances. Unless requested by USCG LRIT management, excessive reporting will not be billable to the U.S. Government. Additionally, testing and communication failures will not be billed to the U.S. Government under any circumstances.

2.3 ASP FUNCTIONS

The Contractor shall provide all ASP functions, adhere to all system requirements and processes as identified in the ASP Technical Requirements and in accordance with all LRIT regulations and documents provided to the Contractor.

2.3.1 The Contractor shall report position data for all U.S. flag vessels four (4) times daily with no more than 1 minute in delay from receipt of the shipboard position to the time of delivery to the NDC. On a daily basis, the Contractor shall identify over-reporting of vessels (i.e. exceeds the standard of four (4) times per day) via LRIT Message #7 (RECEIPTS). The USCG is not responsible for payment of additional position reports unless pre-approved by the COR.

2.3.2 The Contractor shall provide XML formatted ship positional data as set out in ASP requirements (See SOW 7.1, 7.2, 7.3, 7.4 and 7.7).

2.3.3 The Contractor shall translate the Shipborne Equipment Identifier, the identifier used by the shipborne equipment, and correlate that identifier to the ship’s IMO number.

2.3.4 The Contractor shall provide positional data (the GNSS position (latitude and longitude) of the ship (based on the WGS84 datum) as prescribed by Regulation V/19-1, without human interaction onboard the ship.

2.3.5 The Contractor shall provide on-demand position reports. The equipment utilized for LRIT shall be capable of responding to a request to transmit LRIT information on demand without human interaction onboard the ship, irrespective of where the ship is located. The position reports are expected to be received at the U.S. NDC at intervals ranging from 15 minutes to 6 hours. Only the COR or the designated LRIT sponsor’s representative at USCG Headquarters may request on-demand position reports and changes to the frequency of vessel position reporting.

2.3.6 The Contractor shall interact with U.S. Flag ships/CSPs through a communications protocol provided by an ASP to enable the following minimum functionality:

· remote integration of the ship borne equipment into the IDC;

· automatic configuration of transmission of LRIT information;

· automatic modification of the interval of transmission of LRIT information;

· automatic suspension of transmission of LRIT information;

· on demand transmission of LRIT information; and

· automatic recovery and management of transmission of LRIT information.

2.3.7 The Contractor shall connect to the NDC (TEST and PRODUCTION) using Public Key Infrastructure (PKI).

2.3.8 The Contractor shall provide a TEST environment for connection to the U.S. NDC TEST environment. This hardware and software suite will be used by both the Contractor and the Government to test software upgrades and other system changes. It shall be available from 0700 to 1700 ET, Monday through Friday.

2.3.9 The Contractor shall provide appropriate gateways between all associated CSPs in order to integrate all LRIT capable equipment installed on U.S. vessels, as described in SOW 2.6.6. These gateways shall be capable of receiving LRIT information transmissions from all commercially available GMDSS and SSAS LRIT capable terminals, as well as all Chapter V SOLAS (LRIT stand-alone) terminals which are type approved by the USCG Networks required to meet the gateway requirements include Inmarsat (C and D+/IsatM2M) and Iridium.

2.4 ASP TO NDC DATA FEED

The Contractor shall provide a data connection between the ASP and the U.S. NDC via the internet no later than 15 days after contract award. This connection shall be used to provide the U.S. NDC with data (LRIT Information), including data sent to/received from participating LRIT vessels, or test data if vessels have not successfully completed conformance testing. The Contractor shall, upon request, provide a dedicated private data link between the U.S. NDC and the ASP. All LRIT data sent must be in accordance with all LRIT Regulations, Circulars and U.S. ASP Requirements. In addition to the LRIT formatted and compliant data stream, the Contractor shall also provide a data feed containing all data elements received from U.S. flag vessels. The data feed for each vessel shall commence no later than the compliancy date of each vessel. Vessels that have already passed their compliancy dates should be integrated as soon as possible, but no later than 3 business days after completion of a successful conformance test.

2.5 INTEGRATE VESSELS INTO ASP AND U.S. NATIONAL DATA CENTER

The Contractor shall begin sending messages to/from vessels after each vessel has successfully completed conformance testing. Transmission should be established within 5 business days after the successful completion of the conformance test but no later than the vessel’s next annual radio survey date for that calendar year, or as directed otherwise by the COR. In addition, the Contractor shall seamlessly transition the current fleet of U.S. vessels reporting LRIT information from the current ASP. This transition must occur with the outgoing Contractor in order to ensure all U.S. vessels remain in compliancy with the automatic reporting of LRIT information. All associated vessel information, including, but not limited to, the vessel name, call sign, IMO number, International Maritime Satellite Organization (IMARSAT) number (IMN) or associated Iridium number details, will be provided by the Government.

2.5.1 Integration of newly documented vessels into LRIT system: Contractor shall provide service to accommodate additional vessels that are newly documented or re-flagged into the U.S. and must comply with LRIT regulations.

2.5.2 Deletion of vessels from the LRIT system: In the event a vessel changes flags or requires removal from the LRIT system in accordance with the LRIT regulations, the Contractor shall manage all technical issues required to terminate or change vessel as needed. The Contractor shall not begin any such action unless notified by the COR and shall communicate, via e-mail, when such action(s) have been completed.

2.6 SYSTEM/OPERATIONAL AVAILABILITY AND TROUBLESHOOTING

2.6.1 The Contractor shall provide data to the LRIT system 24 hours per day 7 days per week with better than 99.9% availability measured annually, 99% measured monthly and better than 95% availability on any day.

2.6.2 The Contractor shall be capable of receiving and forwarding at least 5 reports per second.

2.6.3 The Contractor shall process LRIT ship position report messages as defined in the “Technical Specifications for the LRIT System” (MSC LRIT Technical Specifications).

2.6.4 The Contractor shall send the LRIT position request message to the NDC after receiving a position request message received from the NDC via the NDC interface and process LRIT position request messages based on the value of the request duration parameter. The message shall be relayed to the NDC if it is a poll, periodic or stop request.

2.6.5 The Contractor shall provide 24 hours per day 7 days per week support for all aspects related to ASP services and shall notify the LRIT Business Help Desk when ships are not responding (reporting their positions) at the specified time interval. The USCG LRIT Business Help Desk is operated at the USCG Navigation Center and can be contacted via phone at 1-866-944-5748 toll free, 703-313-5788 commercial phone, 703-313-5899 fax or TIS-SG-LRIT@USCG.mil e-mail.

2.6.6 The Contractor shall respond to all inquiries from the Business Help Desk regarding all matters related to the ASP service within 6 hours. This includes troubleshooting of vessels that are not properly sending their position reports in order to determine the cause of the missed position reports.

2.7. OPERATIONAL PROBLEM RESOLUTION

The Contractor shall provide a 24 x 7 phone number for reporting and resolution of problems.

The USCG requires the Contractor, depending on the agreed service response class (Critical, Serious, Low), to respond interruptions in daily system processing, system failures or responses to incidents according to an agreed upon Solution Time.

2.7.1 Interruption Classification The Interruption classifications below will be used by the USCG for the Service Response:

Critical: Service interruption (over 2 hours); the performance and/or service of the server, platform or application which are the object of the Service are unstable; application, process or server is halted; Services are so unstable that normal operations cannot be conducted. If the interruption concerns numerous users or an entire function, an interruption is classified as critical.

Serious: Interruption disturbs significantly the U.S. ability of the Service; application or platform are repeatedly unstable or do not answer normally to service requests.

Low: Interruption is stochastic and does not substantially impede user interruption concerns rarely used special services and/or a work around is available. Other interruption which does not risk the customer’s activities.

2.7.2 Solution Time The USCG requires the Contractor, depending on the Interruption/Response Classification (Critical, Serious, Low), to respond to the incident according to the agreed upon Solution Time (the time period which is calculated from the point in time when an incident or problem is detected and during which the Contractor shall correct the interruption or problem or otherwise normalize the Service.)

The Contractor will correct the fault(s) and return the normal operability (incidents) within the Solution Times, depending on the Service Response class, as follows:

Response Class
Solution Time
Critical
6 hours
Serious
12 hours
Low
24 hours

3.0 ADMINISTRATIVE INFORMATION

The Contractor shall attend a post-award conference with the Contracting Officer and the COR not later than five (5) business days after the date of award. The purpose of the post-award conference is to discuss technical and contracting objectives of this contract and review the Contractor's draft project plan. The post-award conference may be held via teleconference.

3.1 PROJECT PLAN

The Contractor shall provide a draft Project Plan at the post-award conference for Government review and comment. The Contractor shall provide a final Project Plan to the COR not later than fifteen (15) business days after receipt of the Government’s comments.

3.2 REPORTS

The Project Manager shall provide monthly status reports to the Contracting Officer and COR via electronic mail. These reports shall include a summary of all Contractor work performed to include but not limited to: U.S. transactions (messages/data transactions) into/out of the ASP, status report on each vessel undergoing testing and overall test progress. Status reports shall include an assessment of technical progress, schedule status, and any Contractor concerns or recommendations for the previous month.

3.3 PROGRESS MEETINGS

The Project Manager shall be available to hold teleconferences with the Contracting Officer and COR upon request to present deliverables, discusses progress, exchange information and resolve emergent technical problems and issues.

3.3.1 The Project Manager shall meet with the COR on a monthly basis to discuss progress, exchange information and resolve emergent technical problems and issues. These meetings shall take place by teleconference.

3.3.2 At a minimum, the Project Manager shall review the status and results of Contractor performance with the COR during the monthly meeting.

3.3.3 GENERAL REPORT REQUIREMENTS

The Contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with Coast Guard Standard Workstation (Windows Server 2003 and Microsoft Office Applications).

3.3.4 INTELLECTUAL PROPERTY

All Contractor developed processes and procedures and other forms of intellectual property first developed under this contract shall be considered Government property. All documentation, photography and electronic data and information collected by the Contractor and entered into or generated in support of this contract shall be considered Government property, and shall be returned to the Government at the end of the performance period.

3.3.5 PROTECTION OF INFORMATION

Contractor access to proprietary information is required under this contract. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive but Unclassified (SBU) Information. SBU includes information categorized by DHS or other Government agencies as: For Official Use Only (FOUO); Official USE Only (OUO); Sensitive Homeland Security Information (SHSI); Limited Official Use (LOU); Law Enforcement Sensitive (LES); Safeguarding Information (SGI); Unclassified Controlled Nuclear Information (UCNI) and any other identifier used by other Government agencies to categorize information as sensitive but unclassified. The Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a non-disclosure agreement (DHS Form 11000-6).

3.3.6 SECTION 508 COMPLIANCE

The Contractor shall ensure that Section 508 of the Rehabilitation Act is complied with for this contract. Section 508 of the Rehabilitation Act (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998, requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, they must ensure that it is accessible to people with disabilities, unless it would pose an undue burden to do so. Federal employees and members of the public who have disabilities must have access to and use of information and services that is comparable to the access and use available to non-disabled Federal employees and members of the public. For additional information, please refer to FAR 39.2 or http://www.section508.gov.

4.0 GOVERNMENT DEFINITIONS

4.1 DEFINITIONS

Archived Position Report – past position report (up to 1 year old).

Chapter - a chapter of the Convention.

Committee - the Maritime Safety Committee.

Convention - the International Convention for the Safety of Life at Sea, 1974, as amended.

High-speed craft - a craft as defined in regulation X/1.3.

International Routing Rules - a list of all Data Centers with their associated IP addresses as identified in the DDP.

LRIT Data user - a Contracting Government or a Search and Rescue (SAR) service that opts to receive the LRIT information it is entitled to.

LRIT information - the information specified in SOLAS regulation V/19-1.5.

Mobile offshore drilling unit - a mobile offshore drilling unit as defined in regulation XI-2/1.1.5.

Organization - the International Maritime Organization.

Regulation - a regulation of the Convention.

Periodic Position Report – real time data on the locations of vessels subject to LRIT carriage requirements. The standard rate or interval (i.e. the period) is 6 hours.

Periodic Rate Change - Variance in the frequency of reporting. Rate is the interval between position reports. The periodic rate can be changed to as frequently as every 15 minutes. Following a period rate change, position reports are considered regular periodic position reports – just the reporting interval changes. Any change to more frequent reporting is temporary and will be changed back to the standard interval.

Polled Position Report – position report as a result of a ship position request or poll request.

Ship - when used in the present Performance standards and functional requirements for long-range identification and tracking of ships, includes mobile offshore drilling units and high-speed craft as specified in SOLAS regulation V/19-1.4.1 and means a ship that is required to transmit LRIT information.

Vessel Monitoring System - a system established by a Contracting Government or a group of Contracting Governments to monitor the movements of the ships entitled to fly its or their flag. A Vessel Monitoring System may also collect from the ships information specified by the Contracting Government(s) that has established it.

4.2 ABBREVIATIONS

ASP – Application Service Provider COR – Contracting Officer’s Technical Representative CSP –Communication Service Provider DC – LRIT Data Center DDP – LRIT Data Distribution Plan IDE – International LRIT Data Exchange NDC – National Data Center SOLAS – International Convention for the Safety of Life at Sea USCG – United States Coast Guard

5.0 GOVERNMENT FURNISHED RESOURCES

The Government will provide the following property and information to the Contractor for work required under this contract:

5.1 LIST OF U.S. FLAG VESSELS SUBJECT TO THE LRIT REGULATION

The list will include all pertinent information required by the ASP in order to initiate contact with the ship owner/operator/agent in order to commence conformance testing, integrate the vessel into the LRIT system, and continue ongoing LRIT services with each vessel. As vessels that may not be included on the current list or are newly documented vessels or vessels re-flagging into the U.S., the COR or designee will provide the information as it is obtained on the individual vessel or vessels. The Contractor will be expected to maintain a current list of vessels. The Contractor is also expected to de-register any vessels in the case of vessels re-flagging out of the U.S. or if other circumstances arise, as directed by the Government.

5.2 U.S. ASP TECHNICAL REQUIREMENTS

This document will be provided to the Contractor and specifies the U.S. ASP Technical Requirements for sending and receiving messages to and from the U.S. NDC. This document aligns with the current LRIT Regulations and specifications for the International LRIT system.

6.0 CONTRACTOR FURNISHED PROPERTY

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

7.0 REFERENCES

7.1 MSC 202(81), Regulation V/19-1

7.2 MSC 263(84) (Performance Standards and Functional Requirements)

7.3 MSC.1/Circ.1259 (Technical Document Part I (current revision))

7.4 MSC.1/Circ.1294 (Technical Document Part II)

7.5 MSC.1/Circ.1295

7.6 MSC.1/Circ.1298

7.7 MSC.1/Circ.1307

7.8 33 CFR Part 169, LRIT, Final Rule

7.9 U.S. ASP Technical Requirements dated December 19, 2014

8.0 DELIVERABLES

ITEM
SOW
DELIVERABLE / EVENT
DUE BY
1
3.0
Post-Award Conference
Not Later Than (NLT) 5 business days after award.
2
3.1
Draft Contractor Project Plan
NLT Post-Award Conference
3
3.1
Final Contractor Project Plan
NLT 15 business days after receipt of Government’s comments
4
3.2,

3.3.1

Status Reports
Monthly
5
3.3
Progress Meetings
Upon request/Monthly/Quarterly
6
2.3
ASP to NDC data feed
NLT 15 calendar days after award
7
2.1
Web Interface
NLT 60 days after contract award
8
2.2.1
Initiate Conformance Testing
NLT 5 calendar days after award
9
2.2.2
Complete Conformance Tests
NLT 90 days prior to the date of the next required annual radio survey date inspection (for each vessel) or as specified.
10
2.2.3
Issue Conformance Test Reports
Issued NLT 3 business days after the completion of a successful conformance test
11
2.4
Integrate Vessels into ASP and U.S. NDC
NLT 21 calendar days after award for existing U.S. vessels and NLT 5 business days after the completion of a successful conformance test for newly tested vessels or as instructed by the COR
12
3.3.4
Intellectual Property and Transition Data
NLT one (1) week before contract completion date. Format in accordance with standard industry practice.

File details come from the government source that posted it. Updated .