D -- International Long-Range Identification and Tracking (LRIT) system.

REQUEST FOR INFORMATION INTRODUCTION 1. The United States Coast Guard (USCG) is developing its requirements and technical specifications for communication between Application Service Providers (ASPs) and the U.S. National Data Center (NDC) within the international Long-Range Identification and Tracking (LRIT) system. 2. 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 LRIT. This new 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 will be required to provide their position to the U.S. NDC four (4) times daily. The LRIT system provides for the global identification and tracking of ships. Communication specifications within the international LRIT system detail the messaging format between LRIT components, data security throughout the network, and the protocols required for transporting data from one network point to another. The USCG desires to assess the current industry capabilities regarding the communication specifications for the U.S. portion of the system, including message format, data security, and protocols for transporting data. 2.1 General Description of the System and Definitions System Description: As described in resolution MSC.210 (81), sub-section 1.2, the LRIT system consists of the following components: 1. The shipborne LRIT information transmitting equipment 2. The Communication Service Provider(s) 3. The Application Service Provider(s) 4. The LRIT Data Centre(s), including any related Vessel Monitoring System(s) 5. The LRIT Data Distribution Plan 6. The International LRIT Data Exchange 7. LRIT Data Users. 2.2 LRIT System Operation Tracking of any applicable ship begins with LRIT positional data being transmitted from the shipborne equipment. The LRIT information transmitted includes the ship?s GNSS position (based on the WGS84 datum), time, and identification, as described in resolution MSC.210 (81). The Communication Service Provider (CSP) 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 additional information to the LRIT message and pass the expanded message to its associated LRIT NDC. 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 will store all incoming LRIT information from ships instructed by their Administrations to transmit LRIT information to that Data Centre. 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 the 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. 2.2.1 Definitions 1. Convention means the International Convention for the Safety of Life at Sea, 1974, as amended. 2. Regulation means a regulation of the Convention. 3. Chapter means a chapter of the Convention. 4. LRIT Data User means a Contracting Government or a SAR service that opts to receive the LRIT information it is entitled to. 5. Committee means the Maritime Safety Committee. 6. High-speed craft means a craft as defined in regulation X/1.3. 7. Mobile offshore drilling unit means a mobile offshore drilling unit as defined in regulation XI-2/1.1.5. 8. International Routing Rules means a list of all Data Centers with their associated IP addresses as identified in the DDP. 9. Organization means the International Maritime Organization. 10. Vessel Monitoring System means 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. 11. LRIT information means the information specified in SOLAS regulation V/19-1.5. 12. The term ?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. Terms not otherwise defined should have the same meaning as the meaning attributed to them in the Convention. 2.2.2 Acronyms The acronyms that appear within this document shall have the meanings assigned to them in this Article. 1. ASP Application Service Provider 2. CSP Communication Service Provider 3. DC LRIT Data Centre 4. DDP LRIT Data Distribution Plan 5. IDE International LRIT Data Exchange 6. NDC National Data Centre 7. SOLAS International Convention for the Safety of Life at Sea Communication within the LRIT System 2.3 Message Types: Communication within the LRIT system is based upon three types of messages passing between the various components of the LRIT system: LRIT request messages, LRIT ship position report messages, and other system messages. Request messages are those requesting specific LRIT information. LRIT ship position report messages are those containing LRIT ship positional data. Other messages managed by the system include: Billing and transaction messages, receipt messages, DDP related messages, costing and billing related messages, system status messages, and pricing messages. Figure 2 illustrates the LRIT system components as well as the various communications segments in the LRIT network. 3. PURPOSE OF REQUEST FOR INFORMATION The USCG is assessing whether ASP?s can provide XML formatted data to meet our IMO MSC LRIT requirements. In furtherance of this effort, respondents are encouraged to provide information about XML message formatting, or alternative methodologies that can help the USCG better understand the potential of exchanging positional information with U.S. flagged ships. The USCG also wishes to know if ASP?s are capable of meeting the requirement to provide positional information for all US flagged vessels within the performance specifications set by the International Maritime Organization (IMO). The USCG also desires to determine the estimated period of time it will take ASP?s to have the capability to provide properly formatted data from all US vessels subject to the regulations to the US NDC. 4. DESCRIPTION OF INFORMATION REQUESTED The USCG is seeking sources that are capable of producing XML formatted data to meet its IMO MSC LRIT requirements, preferably via GSA schedule contract holders. The USCG is seeking interest and capability of firms to discuss the ASP?s capabilities with regards to the requirements discussed in this RFI, the ASP?s system requirements, the ASP?s integration specifications (if available), and any other specific and pertinent information that would enhance the USCG?s understanding of the information submitted. Respondents should also complete the Potential Requirements Table which contains provisional requirements for the USCG?s LRIT positional data requirements. We recognize that not all requirements may be met by a single software system. Please indicate in your response which capabilities can be provided via commercial off the shelf software versus custom developed solutions. For requirements that are met by commercial off the shelf software, please also include the product name, release number, and release date of the software. Please indicate the ability of your ASP to provide positional information for all US flagged vessels (or alternatively for what portion of US flagged vessels). 5. DISCLAIMER This RFI is issued solely for information and planning purposes in accordance with (IAW) FAR Part 10, ?Market Research?, and does not constitute a commitment, implied or otherwise, that a procurement action will be issued. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of the submission of contractor's information. Respondents are solely responsible for all expenses associated with responding to this RFI, and are requested NOT to send proprietary information. Responses indicative of proprietary information will NOT be reviewed by the USCG and returned to the Respondent. Responses to this RFI will not be returned. Respondents will not be notified of the result of the review. 6. HOW TO RESPOND Firms who wish to respond to this RFI should include their business size, CAGE code, Dun and Bradstreet number and GSA schedule, should they hold one. Please submit information to include any pricing, GSA Schedule information that is applicable, comments on the specification and requirements via email to Mr. Todd W. Blose at contact@example.gov, phone +1 (555) 000-0000, by 12 Noon local time, Friday 21 March 2008.