LRIT RFI FINAL 2-12-20.docx

REQUEST FOR INFORMATION NOTICE

INFORMATION SOUGHT REGARDING THE LONG RANGE

IDENTIFICATION AND TRACKING DATA SERVICES REQUIREMENT

DISCLAIMER: THIS IS A MARKET SURVEY FOR WRITTEN INFORMATION ONLY. THIS IS NOT A SOLICITATION FOR PROPOSALS AND NO CONTRACT WILL BE AWARDED FROM THIS ANNOUNCEMENT. RESPONDANTS ARE ADVISED THAT THE U.S. GOVERNMENT WILL NOT PAY FOR ANY INFORMATION OR COSTS INCURRED IN RESPONSE TO THIS REQUEST FOR INFORMATION NOTICE. NO BASIS FOR CLAIM AGAINST THE GOVERNMENT SHALL ARISE AS A RESULT FROM A RESPONSE TO THIS NOTICE NOR GOVERNMENT USE OF ANY INFORMATION PROVIDED. ALL COSTS ASSOCIATED WITH RESPONDING TO THIS REQUEST WILL BE SOLELY AT THE RESPONDING PARTY’S EXPENSE.

I. PURPOSE

The purpose of this request for information notice is solely for informational, market research, and planning purposes, that may be of interest to the United States Coast Guard (USCG). The result of this market research will contribute in determining viable sources who can meet the requirements of the procurement. Pursuant to FAR Part 10 (Market Research), the purposes of this notice is to: (1) determine if source’s capable of satisfying the agency’s requirements exist; (2) determine if the source is currently recognized by the International Maritime Organization (IMO) as a registered Applications Services Provider (ASP) on the behalf of the U.S. or could be by February 2020; (3) determine if the source has a minimum of 5 years National Data Center (NDC) support experience; (4) determine if the source utilizes a “blended feed” (5) determine the company’s commercial practices when providing the needed service; (6) determine the source’s current utilization of FEDRAMP Cloud environment capabilities and U.S. data hosting; (7) determine the source’s ability for data integration; and (8) determine the company’s small business status for small business programs.

Please be advised that all submissions become Government property and will not be returned. Not responding to this request does not preclude participation in any further request for proposals (RFP), if any is issued. In accordance with FAR 15.201 (e), responses to this notice are not offers and cannot be accepted by the United States (U.S.) Government to form a binding contract. Pursuant to set-aside decisions may be based on the results of market research. This notice in no way obligates the Government to any further action.

After the review of the responses to this sources sought announcement, if the USCG plan to proceed with the acquisition competitively, a solicitation announcement will be published in the beta.SAM.gov website. It is the responsibility of the interested parties to monitor the beta.SAM.gov website. A response to this RFI notice is not adequate response to any future solicitation announcement. All interested offerors will have to respond to any solicitation in addition to responding to this notice.

Respondents are advised that the Government is under no obligation to acknowledge receipt of the information received or to provide feedback to respondents with respect to any information submitted. No proprietary, classified, confidential, or sensitive information should be included in your response to this notice. The Government reserves the right to use any information provided by respondents for any purpose determined appropriate, including using technical information provided by respondents in any resultant solicitation. No solicitation exists at this time; therefore, any request for a copy of the solicitation is premature.

II. REQUIREMENT

The USCG has a need for a NDC/ASP and associated LRIT/ Vessel Data Services. The services shall include providing: (1) NDC/ASP User Interface (UI); (2) conformance testing for all U.S. flagged vessels subject to the LRIT regulation; (3) integration of vessels into a hosted FEDRAMP certified cloud environment U.S. NDC; (4) data services (position reports) for all vessels subject to carriage requirements; (5) 24-hour, 7-day a week MDA/NDC watch and customer support to vessels and the USCG, to include position transmission failure reporting, LRIT system / equipment troubleshooting, and a phone number where the U.S. vessel(s) may call; and (6) management of all receipt and reconciliation of Data Center to Data Center (DC to DC) data agreements on behalf of the U.S. for foreign flag position purchases, capabilities, and invoicing.

The USCG requests all respondents please provide the following information and answer the following questions:

1. Company name, address, phone number and point of contact.

2. Company's DUNS number and socioeconomic status.

3. Can your company provide the services listed in this RFI and the attached draft statement of work (SOW)?

4. Is your company a registered Applications Services Provider (ASP) on the behalf of the U.S.?

5. Is your company currently hosting a U.S FEDRAMP compliant certified NDC? If so, can you submit a copy of your FEDRAMP Security Policy?

6. What are your company’s commercial practices when providing the service listed in this RFI and draft SOW?

7. How would your company utilize “FEDRAMP Cloud” capabilities for this requirement?

Responses to this notice along with any capability statements, company literature, brochures should be emailed to the Contracting Officer, Allen A. Tillman II at Allen.A.Tillman@uscg.mil in the subject line, please insert the following ("Your Company name" - 70Z02320IMLQ00100). Telephone responses will not be accepted. The USCG respectfully requests that written responses be limited to 10 pages or less. This 10 page limit does not include commercial brochures or product literature.

Written responses are requested by 27 February 2020 to help expedite this market research for a strategy decision.

February 12, 2020 Page 3

DRAFT STATEMENT OF WORK (SOW)

U.S. COAST GUARD LONG RANGE IDENTIFICATION AND TRACKING (LRIT) DATA SERVICES

Dated 1-23-20 V 1.0

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 information on a phased-in schedule beginning December 31, 2008. Subject to any future changes in the regulation, all U.S. flagged vessels are required to transmit/provide LRIT position reports, at a minimum four (4) times daily, to the U.S. National Data Center (NDC) via a United States (U.S.) “recognized” Application Service Provider (ASP). Now, the U.S. estimates that there are approximately 850 U.S. Flag vessels subject to the LRIT regulations. Subject to any future regulation changes, the maximum frequency of LRIT data 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 NDC/ASP responsibilities and roles within the LRIT system to 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.

The LRIT system with advanced vessel data services has allowed the U.S. to enhance its maritime security via improved Maritime Domain Awareness (MDA). The goal of LRIT is to implement a maritime security system that will enhance U.S.’ ability to track U.S. SOLAS Vessels, identify foreign vessels that are transiting within U.S. coastal waters and for vessels who have intended to enter U.S. port.

An active and accurate MDA system also has clear safety benefits, most notably for maritime Search and Rescue (SAR). Accurate information on the location of the ship in distress as well as ships in the vicinity that could lend assistance will save valuable response time to affect a timely rescue. This initiative is clear in outlining the importance of Maritime Domain Awareness.

LRIT involves four (4) primary missions:

1. Maritime Security: To ensure Contracting Governments (CGs) are aware of SOLAS-class vessels transiting within 1,000NM off their coastlines or intending to enter their ports;

2. Safety of Shipping: To enhance U.S. SOLAS and NON-SOLAS class Flag coverage;

3. Search and Rescue: To enhance SAR services; and

4. Environmental Response: To enhance the ability to track and identify SOLAS and NON-SOLAS class vessels who may be involved in an environmental response incident.

LRIT carriage requirements reflect the international requirements adopted by the IMO for the carriage of LRIT equipment on board SOLAS-class vessels. LRIT in U.S. will be implemented according to international standards and USCG LRIT Technical Specifications (issued by the U.S. Coast Guard Operations Systems Center) and the U.S. LRIT regulations, ensuring U.S. remains consistent with international SOLAS CGs in maritime security.

This (SOW) details the full requirements and the tasks to be performed by the Contractor to deliver and manage a complete U.S. NDC service. A detailed description of the system and system requirements.

The Contractor shall be established and recognized as the USCG LRIT Data Centre (ASP). Reference IMO Circular No. MSC.1/Circ.1377/Rev.5.

1.2 SCOPE

The purpose of this procurement is to obtain NDC/ASP and associated LRIT/ Vessel Data Services for the Coast Guard (CG). The services shall include providing: (1) NDC/ASP User Interface (UI); (2) conformance testing for all U.S. flagged vessels subject to the LRIT regulation; (3) integration of vessels into the MDA/LRIT system (U.S. NDC); (4) data services (position reports) for all vessels subject to carriage requirements; (5) 24-hour, 7-days a week MDA/NDC customer support to vessels and the USCG, to include position transmission failure reporting. LRIT system / equipment troubleshooting, and a phone number where the U.S. vessel(s) may call; (6) system status messages every thirty (30) minutes between the ASP and U.S. NDC to verify component status; (7) a separate pre-production LRIT testing environment to facilitate new and update system releases and software testing of the NDC and ASP instance prior to moving them into production; and (8) management of all receipt and reconciliation of DC to DC data agreements on behalf of the U.S. for foreign flag position purchases. The Contractor shall manage and confirm DC to DC data purchasing arrangements with all foreign NDC’s and contracting governments to enable foreign flag data transfer capabilities and invoicing.

All ASP/NDC service and functional requirements shall be performed as defined and in accordance with all applicable regulatory documents listed in this document. Other applicable LRIT related documents that may also apply to the ASP/NDC service requirements including MSC Regulations and Circulars. The Contractor shall maintain copies of all current IMO related documents and provide them to the COR upon request.

The Contractor shall perform all maintenance of the NDC/ASP including any standard service changes or updates in accordance with the requirements as specified by the IMO and within the obligations of the LRIT system.

The Contractor will, upon task order by the USCG, provide support for potential upgrades to the geospatial viewer (UI) for data requirements of the USCG to include processing and display of data associated with programs to include Automated Mutual-Assistance Vessel Rescue System (AMVER), Authoritative Vessel Identification Service (AVIS), Nationwide Automatic Identification System (NAIS), Search and Rescue (SAR) and Optical Imagary, Vessel Sanctions and Port State Control Screening, and other associated vessel data requirements.

The Contractor shall have a comprehensive understanding of the SOLAS Chapter V 19-1 LRIT regulatory framework including the performance standards, functional requirements and technical specifications of the NDC, ASP, and CSP, including DC/DC billing arrangements, and supplemental data services requirements.

The Contractor must be directly responsible for ensuring the accuracy, timeliness and completion of all tasks assigned under this statement of work. The Contractor must demonstrate their ability to fulfill all the items listed as “must” and “shall” in this SOW and in the USCG LRIT Technical Specifications.

1.3 OBJECTIVE

The USCG requires the services of the U.S. Authorized ASP that will fulfill the requirements of the U.S. and the IMO mandate can provide the technical communication infrastructure and data services necessary for establishing a communication path between SOLAS class compliant vessels. The Contractor must understand the LRIT system architecture, the Data Distribution Plan (DDP) and secure using Public Key Infrastructure (PKI) allowing entities to securely communicate over the internet and reliably verify the identity of a user via digital signatures.

1.4 APPLICABLE DOCUMENTS

(Reference Section 1.4.2)

1.4.1 COMPLIANCE DOCUMENTS

The following documents provide specifications, standards, or guidelines that must be complied with in order to meet the requirements of this SOW:

(Reference Section 1.4.2)

1.4.2 REFERENCE DOCUMENTS

The following documents may be helpful to the Contractor in performing the work described in this document:

MSC 202(81), Regulation V/19-1 MSC 263(84) (Performance Standards and Functional Requirements) MSC.1/Circ.1259 (Technical Document Part I (current revision)) MSC.1/Circ.1294 (Technical Document Part II) MSC.1/Circ.1295 MSC.1/Circ.1298 MSC.1/Circ.1307 33 CFR Part 169, LRIT, Final Rule U.S. ASP Technical Requirements dated July 8, 2009

2.0 SPECIFIC REQUIREMENTS/TASKS

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

The Communication Service Provider (CSP) hired or performed by the Contractor provides the communication infrastructure and services necessary for establishing a communication path between the ship and the NDC/ASP. The LRIT information transmitted from the ship will travel across the communication path set up by the CSP to the NDC/ASP. The NDC/ASP, after receiving the LRIT information from the ship, will add additional 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 ship borne 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 will store all incoming LRIT information from ships instructed by their Administrations to transmit LRIT information. LRIT Data Centers will 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 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.

All ASP/NDC service and functional requirements shall be performed as defined and in accordance with all applicable regulatory documents, listed in section 1.4.2 of this document. The Contractor shall perform all ASP/NDC service changes in accordance with any updates or changes within the LRIT system.

2.1 TASK ONE. FEDRAMP Cloud Hosted NDC Web Administrators Interface with Geographical Display Capability

2.1.1 Display all classes of vessels collected

2.1.2 Display IHS vessel data

2.1.3 Display vessel details

2.1.4 Display vessel imagery when available from IHS

2.1.5 See operator Contact Information

2.1.6 Provide LRIT ships List

2.1.7 Sort via LRIT ship Types

2.1.8 Manual entry of ship information capability

2.1.9 On Demand polling capability

2.1.10 Grouping of ships for reporting and map viewing

2.1.11 Searchable map feature to seek vessel on map

2.1.12 Track vessel activity on map

2.1.13 View on LRIT foreign vessels under Coastal orders

2.1.14 Sort vessels via flag

2.1.15 Full LRIT specifications functionality

2.1.16 Search and Rescue Query capability

2.1.17 Search and Rescue polygon plotting capability

2.1.18 Blended Track display and full functionality

2.1.19 Filter to view via source data

2.1.20 Identify ship source by ICON

2.1.21 Display multiple ship tracks/trails

2.1.22 Export ship position data from polygon

2.1.23 Export multiple ship data from query

2.1.24 Data stored 90 days, with Enhanced query capability to extract data for 3 year

2.1.25 Map Refresh

2.1.26 Vessel playback capability

2.1.27 Search engine by, name, IMO, MMSI, call sign, equip ID, reporting interval, reporting status, vicinity search, complex search

2.1.28 Port Activity Dashboard

2.1.29 Trail/Chart Analysis

2.1.30 Local Time Zone

2.1.31 Piracy overlay and filtering

2.1.32 Create Upload and Export Zones/Polygons

2.1.33 Zone Entry and exit alerts

2.1.34 Modify reporting requirements when ship enter a zone (Change of frequency reporting)

2.1.35 Alerts to e mail, text, on screen window

2.1.36 Reports exportable via .csv, kml, kmz, xml, excel, pdf

2.1.37 Shall be expandable to enable USCG and DHS task order requirements supporting additional enhanced vessel data and sensors for provisioning within associated programs to include AMVER, AVIS, SANS, NAIS, SAR/OPTICAL Satellite Imigary, Vessel Sanctions and Port State Control Screening.

2.2 TASK TWO. Conformance Tests and Reports

2.2.1 Initiate Conformance Testing: If required, the Contractor shall begin conformance testing, in accordance with MSC.1307, no later than fifteen (15) days after the award of the contract. Testing shall be done in accordance with GFE list of ships required to undergo LRIT testing. Conformance testing on U.S. flagged vessels shall only be completed after approval by the Government. The Contractor, to the maximum extent possible, shall initiate the conformance testing with all U.S. flagged vessels at the earliest opportunity of the Contractor. The Coast Guard will provide the list of ships, if any, as GFE no later than three (3) days after contract kickoff meeting.

The Contractor shall contact the ships and shall receive, process, and manage calls from U.S. flagged vessels. For U.S. flagged 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 (2) additional times, if required. After three (3) failed attempts, the ship owner/operator/agent will be responsible for any future ASP testing, unless otherwise instructed; however, 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 complete conformance tests as soon as possible after the award of the contract. If a ship 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 (3) total tests per vessel during the contract.

2.2.3 Issue Conformance Test Reports; Reports to vessels on behalf of the U.S.: The Contractor shall provide a conformance test report within a period of three (3) business days after each vessel that has completed a conformance test and send a copy of the report to the COR. Report shall be typed 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. The Conformance Test Reports will be issued on behalf of the U.S. and the Government will recognize the Contractor as the U.S. ASP and testing ASP with the IMO. 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.

2.3 TASK THREE. Data Services

The Contractor shall provide a data connection to the USCG via the internet UI no later than 60 days after contract award. This service shall be comprised of two (2) separate connections, (1) one to be known herein as raw data feed, which comprises of raw National Marine Electronics Association (NMEA) sentences, globally collected, reporting at near real time not to exceed thrity (30) minutes in latency, and (2) a blended data feed, which will be standard/updated LRIT messages conforming to regulation and format as provided in IMO specifications. These connections are used to provide the U.S. with not only data for enhance MDA, but also for U.S. flag compliance data, including test data if vessels have not successfully completed conformance testing. All LRIT data sent must be in accordance with all LRIT Regulations, Circulars, and U.S. NDC/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. flagged 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 data should be integrated as soon as possible but no later than three (3) business days after completion of a successful conformance test.

2.4 TASK FOUR. Integrate Vessels into ASP and National Data Center

Begin sending messages to/from vessels after each vessel which has successfully completed conformance testing. Transmission should be established within five (5) business days after the successful completion of the conformance test but no later than the vessels 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 U.S. vessels reporting LRIT information from the ASP to NDC. All associated vessel information, including, but not limited to, the vessel name, call sign, IMO number, IMN or associated Iridium number details, will be provided by the Government.

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

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

2.5 TASK FIVE. System/Operational Availability and Troubleshooting

2.5.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 over a year, 99% per month and better than 95% availability per day.

2.5.2 The Contractor shall be capable of receiving and forwarding at least five (5) reports per second.

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

2.5.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 UI 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.5.5 The Contractor shall provide 24-hours per day 7-days per week support for all aspects related to ASP/NDC services and shall notify the LRIT Program Manager when ships are not responding after all corrective measures from the watch have been exhausted and vessels is not reporting at the specified time internal. The Contractor’s NDC watch will send notification via e-mail to. TIS-SG-LRIT@uscg.mil.

2.5.6 The Contractor shall respond to all inquiries from the Coast Guard LRIT PM regarding all matters related to the ASP/NDC service. This includes troubleshooting of vessels that are not properly sending their position reports to determine the cause of the missed position reports.

2.6 TASK SIX. NDC/ASP Functions

The core software design of the U.S. NDC/ASP must be an IMO LRIT Data Center that is currently registered, reporting, and successfully operating within the production environment of the international LRIT system, and currently connected to the U.S. NDC via the certified and appointed U.S. ASP. Thus, the core software design of the U.S. NDC must have already successfully passed the IMO testing and certification process that is required for any NDC to be accepted within the production environment of the international LRIT system to include Flag, Port, State, Coastal, DDP, and SAR requirements.

The Contractor shall provide all NDC/ASP functions in accordance with all LRIT regulations and documents provided to the Contractor including, but not limited to:

2.6.1 The Contractor shall be capable of reporting positional data for all U.S. flagged vessels four (4) times daily with no more than one (1) minute in delay from receipt of the shipboard position to the time of delivery to the NDC.

2.6.2 The Contractor shall be capable of providing XML formatted ship positional data as set out in ASP requirements.

2.6.3 The Contractor shall be capable of translating the Ship borne Equipment Identifier, the identifier used by the ship borne equipment, and correlate that to the ship’s IMO number.

2.6.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 on board the ship.

2.6.5 The Contractor shall provide on-demand position reports. The equipment utilized for LRIT will 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 a minimum of fifteen (15) minutes to maximum period of six (6) hours. A 24-hour position report may be requested on U.S. flagged vessels during the transitional arrangements period.

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

a. Remote integration of the ship borne equipment into the IDC;

b. Automatic configuration of transmission of LRIT information;

c. Automatic modification of the interval of transmission of LRIT information;

d. Automatic suspension of transmission of LRIT information;

e. On demand transmission of LRIT information; and

f. Automatic recovery and management of transmission of LRIT information.

2.6.7 The Contractor shall provide PKI access to the U.S. NDC.

2.6.8 The Contractor shall provide a 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 Eastern Time, Monday through Friday.

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

2.6.10 The Contractor shall maintain the U.S. LRIT NDC capabilities per IMO technical specifications.

2.6.11 The Contractor shall have the capability to operate and maintain watch support for ASP/NDC/AMVER and maintain/operate within a FEDRAMP certified cloud data storage enviorement subject to standard FEDRAMP certification requirements and procedures at an IL4 level or above.

The Contractor shall work with the LRIT Program manager to maintain U.S. data receipt, delivery, and data distribution of all LRIT and other vessel messages.

The Contractor shall manage all receipt of DC to DC data agreements on behalf of the U.S. for foreign flag position purchases.

The Contractor shall ensure the DDP is managed for the U.S. to include coastal and special polygon activation/removal.

With task order, the Contractor UI will communicate with process AMVER and SANS data and identify vessel reports received from AMVER. Participating vessels position reports will be forward to AMVER for processing. Additionally, with task order, the Contractor, shall assist the USCG with upgrading the UI to support future vessel data requirements for associated programs of AMVER, SANS, AVIS, NAIS, SAR/OPTICAL Satellite Imigary, Vessel Sanctions and Port State Control Screening, and associated vessel identiciation information and data.

The U.S. NDC, as per IMO requirements, must be readily accessible for audit by the international LRIT Coordinator (IMSO). Furthermore, the Contractor must comply with all requests by the LRIT Coordinator for data and knowledge pertaining to the operation of the U.S. NDC.

2.6.12 The Contractor will upon receipt of task order by the USCG, provide support for upgrades to the UI for USCG data requirements to include hosting, archiving, processing, and display of data associated with programs to include: AMVER, SANS, AVIS, NAIS, SAR/OPTICAL Satellite Imigary, Vessel Sanctions and Port State Control Screening, associated vessel indetification information, and data systems.

2.7 TASK SEVEN. DC to DC data agreements.

2.7.1 The Contractor shall manage all receipt and reconciliation of DC to DC data agreements on behalf of the U.S. for foreign flag position purchases. The Contractor will manage and confirm DC to DC data purchasing arrangements with all foreign NDC’s and CGs to enable foreign flag data transfer capabilities and invoicing. As LRIT permits CGs to access ship information on foreign flags, the Contractor must establish and manage Data Centre-to-Data Centre (DC-to-DC) billing arrangements on behalf of the Government.

2.7.2 The Contractor must establish a financial clearing house arrangement which will consolidate and validate all purchased DC-to-DC Automatic Position Reports (APRs) to ensure that what has been requested by both U.S. NDC and other Flag DC’s have been received as well as invoiced appropriately.

2.7.3 The Contractor must pay all invoices for Data Centre APR’s at the IMO agreed cost model as identified in document MSC 89/25.

2.7.4 Once the Contractor has paid the Data Centre from which the U.S. NDC has requested the APR’s, then the Contractor must invoice the U.S. NDC for all fees incurred from other contracting governments (using the IMO 1x2x6 cost model).

2.7.5 The Contractor must establish a set fee for the establishment of the financial clearing house (DC to DC) arrangement which is to be invoiced monthly per the terms and conditions of the contract.

2.7.6 Based on the DC to DC billing agreement, the Contractor must consolidate and validate all APR’s purchased by other Data Centers as well as data purchased on behalf of the U.S. NDC and invoice directly with the outstanding balance:

2.7.7 The Contractor shall produce a billing invoice in conjunction with its record of all LRIT message transactions through the U.S. NDC to verify that the invoices issued to government are correct.

2.7.8 The Contractor shall supply the USCG with an LRIT message transaction list for all Port and Coastal state requests contained within the billing invoice. The transaction list will clearly identify which LRIT data user is responsible for initiating the request.

2.7.9 The USCG shall directly pay the Contractor based on the difference between data purchased and data sold between U.S. NDC and the other Contracting Government/LRIT administrations.

2.7.10 The Contractor and the USCG must both have responsibilities and duties pertaining to the billing of LRIT data requests from other data centers or administrations as follows:

a. The Contractor must issue billing invoices directly to the data center or administration that issued the request for LRIT data associated with a vessel registered to the U.S. NDC.

2.7.11 Billing Services: The Contractor must manage the following DC billing service agreements / contracts on behalf of all NDC’s. This section details the requirement of the Contractor to manage all invoices individually irrespective of Contracting Government and therefore without any form of bought / sold reconciliation, USCG direct payment, or credit applied to future bills.

In order to facilitate the effective operation of the International LRIT system, the Contractor shall manage a comprehensive billing system that maintains a transaction record for all LRIT messages transmitted and received from the USCG NDC (to / from the IDE, DDP, as well as internal ASP / CSP interfaces).

The billing system must determine the invoice value to other Governments for the purchase of U.S. Flag LRIT data and conversely reconciles the invoice value from other Governments for the purchase of LRIT data by the U.S.

(Fifty-three (53) NDCs in total and six (6) DC’s providing services to other SOLAS CGs)

Data Exchange Arrangement:

1. Pole Star Space Applications Limited – on behalf of Albania, Algeria, Australia (including the Cook Islands, New Zealand, Palau, and Papua New Guinea), Bahrain (including Kuwait, Oman, and United Arab Emirates), Bangladesh, Bolivia, Brunei Darussalam, Canada, Colombia, Dominica (including Belize, Guyana and Jamaica), Gabon, Honduras, Isle of Man (including Bermuda, Cayman Islands, and Faroe Islands), Indonesia, Israel, Jordan, Kenya, Liberia, Marshall Islands, Morocco, Nauru, Nigeria, Pakistan, Panama, Philippines, Qatar, Saudi Arabia, Sierra Leone, South Africa (including Cape Verde, Ethiopia, Gambia, Ghana, Mozambique, and Seychelles), United Kingdom – and also including British Virgin Islands, Falkland Islands, and Gibraltar, Jersey (all UK) (1 CDC); and Yemen (53 NDCs in total and 6 DC’s providing services to other SOLAS Contracting Governments);

2. CLS – on behalf of Chile, Egypt, Japan, Mexico, Singapore and Vanuatu (5 DCs);

3. Fulcrum – on behalf of Antigua and Barbuda, Barbados, Bahamas, Comoros, Ecuador, Mongolia, Mauritius, St. Kitts & Nevis, Saint Vincent and the Grenadines, Switzerland and Tanzania (11 DCs);

4. MCS – on behalf of Kiribati, Niue and Tuvalu (1 CDC);

5. EMSA – on behalf of Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Egypt, Estonia, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Montenegro, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Aruba (Netherlands), Greenland (Denmark), Netherlands Antilles (Netherlands).

6. National Administrations – Brazil, India, Republic of Korea, Ukraine, Turkey, Vietnam, Argentina.

2.7.12 The Contractor shall provide FEDRAMP certified Cloud environment U.S. data storage for vessel tracking.

3.0 CONTRACTOR PERSONNEL

3.1 Qualified Personnel: The Contractor shall provide qualified personnel to perform all requirements specified in this SOW.

3.2 Continuity of Support: The Contractor shall ensure that the contractually required level of support for this requirement is maintained at all times. The Contractor shall 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 shall provide e-mail notification to the Contracting Officer’s Representative (COR) prior to employee absence. Otherwise, the Contractor shall provide a fully qualified replacement.

3.3 Key Personnel: Before replacing any individual designated as Key by the Government, the Contractor shall notify the Contracting Officer no less than fifteen (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, unless otherwise approved by the Contracting Officer. The Contractor shall not replace Key Contractor personnel without approval from the Contracting Officer. The following Contractor personnel are designated as Key for this requirement. Note: The Government may designate additional Contractor personnel as Key at the time of award.

The position designated as Key Personnel for this requirement is the Contractor’s Project Manager.

3.3.1 Contractor Key personnel shall not be assigned by the Contractor to more than one key position for this requirement.

3.4 PROJECT MANAGER

The Contractor shall provide a Project Manager who shall be responsible for all Contractor work performed under this SOW. The Project Manager shall be a single point of contact for the Contracting Officer and the COR. It is anticipated that the Project Manager shall be one of the senior level employees provided by the Contractor for this work effort. The name of the 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 as part of the Contractor's proposal. The Project Manager is further designated as Key by 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. Additionally, the Contractor shall not replace the Project Manager without prior approval from the Contracting Officer.

3.4.1 The Project Manager or designee shall be available to the LRIT Program Manager when necessary Monday through Friday during established core hours and weekends during emergent/casualties and shall respond to a request for discussion or resolution of technical problems within twelve (12) hours of notification.

3.5 EMPLOYEE IDENTIFICATION

On occasion, Contractors may visit government facilities. Visiting Contractor employees shall comply with all Government escort rules and requirements.

3.5.1 Contractor employees visiting Government facilities shall wear an identification badge that, at a 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.

3.5.2 Contractor employees working on-site at Government facilities shall wear a Government issued identification badge. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent (in meetings, when answering Government telephones, in e-mail messages, etc.) and display the Government issued badge in plain view above the waist at all times.

3.6 EMPLOYEE CONDUCT

Contractor’s employees shall comply with all applicable Government regulations, policies and procedures (e.g., fire, safety, sanitation, environmental protection, security, “off limits” areas, wearing of parts of DHS uniforms, and possession of weapons) when visiting or working at Government facilities. The Contractor shall ensure Contractor employees present a professional appearance at all times and that their conduct shall not reflect discredit on the U.S. or the Department of Homeland Security. The Project Manager shall ensure Contractor employees understand and abide by Department of Homeland Security established rules, regulations and policies concerning safety and security.

3.7 REMOVING EMPLOYEES FOR MISCONDUCT OR SECURITY REASONS

The Government may, at its sole discretion (via the Contracting Officer*), direct the Contractor to remove any Contractor employee from DHS facilities for misconduct or security reasons. Removal does not relieve the Contractor of the responsibility to continue providing the services required under the contract. The Contracting Officer will provide the Contractor with a written explanation to support any request to remove an employee.

4.0 OTHER APPLICABLE CONDITIONS

4.1 SECURITY

Contractor access to classified information is not currently required under this SOW. However, the Government at a later date may require all Contractor personnel to have security clearances. Accordingly, all Contractor employees provided for this requirement will be eligible for a Secret Clearance.

4.2 PERIOD OF PERFORMANCE

The period of performance for this requirement is anticipated for five (5) years with options, starting August 2020.

4.3 PLACE OF PERFORMANCE

The primary place of performance will be the Contractor’s facilities hosted within the CON-US. This performance may be conducted remotely.

4.4 HOURS OF OPERATION

Contractor employees shall generally perform all work between the hours of 0630 and 1700 EST, Monday through Friday (except Federal holidays). However, there may be occasions when Contractor employees shall be required to work other than normal business hours, including weekends and holidays, to fulfill requirements under this SOW.

4.5 TRAVEL

Contractor travel shall not be required for this requirement.

4.6 POST AWARD CONFERENCE

The Contractor shall attend a Post Award Conference with the Contracting Officer and the COR no later than (5) 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 draft project plan. The Post Award Conference will be held at the Government’s facility, via teleconference.

4.7 PROJECT PLAN

The Contractor shall provide a draft Project Plan at the Post Award Conference for Government review and comment. The plan, at a minimum, shall include: (a) list of work to be performed;(b) project schedule; (c) description of intended results; (d) role of key personnel, if applicable and (e) how quality of service (project) will be maintained throughout life of contract. The Contractor shall provide a final Project Plan to the COR not later than 15 business days after the Post Award Conference.

4.8 PROGRESS REPORTS

The Project Manager shall provide a monthly progress report to the Contracting Officer and COR via electronic mail. This report shall include a summary of all Contractor work performed, including a breakdown of labor hours by labor category, all direct costs by line item, an assessment of technical progress, schedule status, any travel conducted and any Contractor concerns or recommendations for the previous reporting period.

Status reports will be delivered compatible with Microsoft Office products. The content required in the reports are subject to change. Any change of status reports will be done via letter to/from the contracting officer and with a minimum of 30 days in advance of next report.

4.10 PROGRESS MEETINGS

The Project Manager shall be available to hold teleconferences with the Contracting Officer and COR upon request to present deliverables, discuss progress, exchange information and resolve emergent technical problems and issues. These meetings shall take place by teleconference. The Project Manager shall meet with the COR as required to discuss progress, exchange information and resolve emergent technical problems and issues. These meetings shall take place by teleconference.

At a minimum, the Project Manager shall review the status and results of Contractor performance with the COR on a quarterly basis by telephone.

4.11 GENERAL REPORT REQUIREMENTS

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

4.12 INTELLECTUAL PROPERTY

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

4.13 PROTECTION OF INFORMATION

Contractor access to information protected under the Privacy Act is required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with the law and Government policy and regulation.

Contractor access to proprietary information is required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with the law and Government policy and regulation.

Contractor access to proprietary information is required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive But Unclassified (For Official Use Only) Information. 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).

4.14 SECTION 508 COMPLIANCE

Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105-220) (codified at 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.

1. All products, platforms and services delivered as part of this work statement that, by definition, are deemed ICT or that contain ICT shall conform to the revised regulatory implementation of Section 508 Standards, which are located at 36 C.F.R. § 1194.1 & Apps. A, C & D, and available at https://www.gpo.gov/fdsys/pkg/CFR-2017-title36-vol3/pdf/CFR-2017-title36-vol3-part1194.pdf. In the revised regulation, ICT replaced the term electronic and information technology (EIT) used in the original 508 standards.

Item that contains Information and Communications Technology (ICT): Data Services Applicable Exception: N/A Authorization #: N/A

Applicable Functional Performance Criteria: All functional performance criteria in Chapter 3 apply to when using an alternative design or technology that results to achieve substantially equivalent or greater accessibility and usability by individuals with disabilities than would be provided by conformance to one or more of the requirements in Chapters 4 and 5 of the Revised 508 Standards, or when Chapters 4 or 5 do not address one or more functions of ICT.

Applicable 508 requirements for electronic content features and components (including Internet and Intranet website; Electronic documents; Electronic forms; Electronic document templates): Does not apply

Applicable 508 requirements for software features and components (including Electronic content and software authoring tools and platforms; ): All requirements in Chapter 5 apply, including all WCAG Level AA Success Criteria, 502 Interoperability with Assistive Technology, 503 Application

Applicable 508 requirements for hardware features and components (including Video Displays and Monitors): All requirements in Chapter 4 apply

Applicable 508 requirements for support services and documentation: All requirements in Chapter 6 apply

1. When developing or modifying ICT for the government, the Contractor shall ensure the ICT fully conforms to the applicable Section 508 Standards. When modifying a commercially available or government-owned ICT, the Contractor shall not reduce the original ICT Item’s level of Section 508 conformance.

2. When developing or…