PWS N6817123Q0004.docx

PERFORMANCE WORK STATEMENT (PWS)

Civil Maritime Vessels Characteristic and Performance Data

1.0 Background

The U.S. Navy is heavily engaged in providing support to all U.S. Government counter-proliferation of weapons of mass destruction, counter-drug, sanctions enforcement, anti-piracy plans, maintaining open sea lanes, programs, and operations. In order to effectively support all of these efforts, the U.S. Navy has the requirement to obtain and maintain a database on all International Maritime Organization (IMO)-registered vessels and companies. To assist the U.S. Navy in maintaining this database a daily automated, bulk data feed from the organization responsible for maintaining the list of IMO-registered vessels is required. This XML-formatted feed shall contain characteristics and performance (C&P) and maritime company data (required fields are listed in APPENDIX A) (for this PWS a record shall be defined as all the data for a specific vessel, while a field shall be made up of each individual piece of data making up a record) on all vessels and companies currently registered by the IMO and all new vessels and companies to be added during the term of the contract. The daily XML feed shall also contain all modifications made to that data during the previous business day. The U.S. Navy also requires the ability to directly query key analysts responsible for the maintaining the IMO fleet list. In addition, the U.S. Navy shall need to ensure that all new data being provided is processing correctly into its systems and that it is in sync with all current data by having the ability to query a commercial online systems linked to the contractor’s database.

2.0 Scope

This PWS covers the acquisition of the complete official list, with all the fields listed in appendix A, of all IMO-registered merchant vessels and companies, to include the daily bulk data updates on all vessels and companies modified, deleted, or added during the previous business day formatted in a mutually agreed upon XML file(s) format. Data shall be gathered from multiple sources to include flag registrations and classification societies and be validated at the contractor’s facility before being provided to the U.S. Navy. The bulk data update shall consist of all required fields on any/all IMO-registered vessels and companies where at least one of those fields was modified during the previous business day. In addition, any vessels added to the list of IMO-registered vessels and companies will be included in the daily bulk data update. The U.S. Navy will also require, at an agreed upon point shortly after the start of the contract, a complete list of all under construction, active, inactive, broken-up, and laid-up IMO registered vessels to insure the US Navy’s and contactor’s data is in sync at contract initiation; (additional complete downloads may be required during the contract life, any such request will be coordinated in advance with the contractor). In addition in order to assist with quality control and to verify the data received, the U.S. Navy requires the following in addition to the bulk data:

1) Up to six remote online access accounts to the contractor’s commercial data tool to be used to assist in the quality control of provided bulk data after processing into U.S. Navy systems. In addition to the standard access to a commercial customer, these accounts shall provide access to any analyst comments or annotations related to the IMO vessels contained within the system. Online access will also be used as an emergency backup in the event of loss of bulk data transfer capability.

2) The ability to submit to analysts ad-hoc queries relating to the bulk data and IMO fleet list. These queries shall enable U.S. Navy to de-conflict any data issues that may arise and provide a deeper understanding of the data being provided.

3.0 Requirements

3.1 Bulk Data Services: (CLIN 0001) The contractor shall provide within 4 weeks of contract award or at the start of the period of performance, whichever is later:

3.1.1 All requested IMO data elements, not to exceed elements identified in APPENDIX A, for the entire IMO vessel list in a mutually agreed upon XML format.

3.1.2 It is understood that some of the required fields are ship type specific and will not contain data for all ships; however, all records shall contain, to the maximum extent possible, data from the fields (indicated in Appendix A). After the initial file is received, the contractor shall provide daily (business days) updates to the data. When providing updates, the entire record shall be resent, even if only one field within that record has changed.

3.1.3 This update shall be in the mutually agreed upon XML format and shall be made available daily on the contractor’s owned, secure file transfer protocol (SFTP) server.

3.1.4 The contractor shall maintain, in soft copy, a data dictionary which defines all data fields being provided to include:

· Field complete name

· Data field character length

· Data field type

· Unit of measure (feet or meters).

3.1.5 In addition to the data dictionary, the contractor shall provide and maintain a list of all fields containing coded data along with a complete explanation of each of the codes.

3.1.6 The contractor shall notify contracting officer’s representative (COR) or designated points of contact (POC) at the U.S. Navy of any planned changes to data schema which would affect required characteristics data provided under this contract.

3.2 Remote Access: (CLIN 0002) The contractor shall provide no more than 6 logins to remotely access its database system. This system shall access the same data set used for the bulk data download and shall include access to contractor’s analysts’ notes (annotations). The U.S. Navy desires a system that is currently commercially available from the contractor and requires no additional development. The contractor shall provide subscriptions and administrative support for the system. This support shall include ensuring that the remote access is available to authorized users twenty-four (24) hours a day, seven (7) days a week and providing, maintaining, and resetting user passwords. Access to, and use of, this remote access shall be via official Government computers by official Government personnel or official Government sponsored personnel. The primary use of this system is to verify contractor’s data that has been uploaded and processed into US Navy systems and to provide an emergency backup in the event of an interruption to bulk data upload. No users will automatically download data or employ any screen scraping techniques to obtain bulk data from these systems. All data shall be accessed via the tools provided within the service software. Use of the system shall be consistent with normal commercial user agreements as published by the contractor.

3.2.1 This remote access shall, at a minimum, allow query access to the same dataset and fields as provided in the bulk data download. It shall be available to authorized user twenty-four (24) hours a day, seven (7) days a week.

3.2.2 It is expected that any/all vessel characteristics within the online system will reflect up to date changes within the contractor data repository as provided in the daily updated data feed.

3.3 Ad Hoc queries: (CLIN 0003) The contractor shall respond to the COR or designated U.S. Navy POC on ad-hoc queries requiring near-real-time response. These queries shall be related to the IMO data being provided by the contractor. These queries shall be used to assist the U.S. Navy in getting a better understanding of the IMO merchant fleet and industry data being provided by the contractor in the daily bulk feed. They shall help to quality control the data and de-conflict any issues that may arise within the data. These queries shall be designed to be a quick turn-around and in general take less than a day to complete and no query shall take more than five (5) days. Queries shall relate directly to the IMO data being provided by the contractor. The queries shall be submitted by the COR or designated U.S. Navy POC in writing via email to the contractor’s POC. The contractor shall respond within one working day with the response or if unable to get a final answer, provide an estimate on how many days it will take. Based on this information, the COR shall assign the service level of the query. The service level will indicate to the contractor the time that has been allotted to the complete the task. Once completed, the contractor shall respond to the COR and designated ONI POC with a written response.

3.4 Data Specifications: The U.S. Navy requires that all data received from the contractor meet the following criteria:

3.4.1 All data provided to the U.S. Navy shall be provided in agreed upon industry standard XML format.

3.4.2 The U.S. Navy requires current information on the ever changing worldwide civil maritime fleet. To achieve this, the contractor shall continually update its data and provided a daily file (each business day) containing all changes since the last update. The contractor must also make available when the data element change actually took place on the individual vessel and the date the change was made within the contractor’s data repository.

3.4.3 All data shall be made available to the Government electronically via a contractor-supplied and maintained, SFTP server, using an approved naming convention (naming convention shall be coordinated between the contractor and U.S. Navy Technical Lead through the COR prior to the start of data delivery). Access to the SFTP server shall be made available 24 hours a day, 7 days a week. ONI will evaluate the contractor monthly to ensure data is arriving within the parameters outlined in this PWS.

3.4.4 The contractor shall provide data in the agreed upon XML format, beginning within 4 weeks after contract award or at the start of the period of performance whichever is later (access to a remote data access capability shall begin on the first day of the period of performance) and continue each business day throughout the remainder of the period of performance or as designated by the contracting officer. The number of formats and format specifications may periodically change or be updated during the period of performance for this PWS. The contractor shall be provided, by the Technical Representative through the COR, any format changes and shall be allowed 60 days to reconfigure and test the file format prior to the required start date.

3.5 Bulk Data Sharing Requirements: In accordance with DFARS 252.227-7015 and DFARS 227.7103-16, the U.S. Navy shall be able to share integrated data, not the entire raw data, from the bulk data feed with all national U.S. Government and Foreign Government agencies as controlled but unclassified data only. In addition, the U.S. Navy shall allow access to assimilated data contained within U.S. Navy systems to U.S. Government and Foreign Government agencies at a controlled but unclassified level or higher. The U.S. Navy will share no data supplied directly from the contractor.

4.0 Monthly Status Reports, Technical Reports, and Task Reviews

4.1 The contractor shall provide to the U.S. Navy monthly statistics and data reports outlining the number and type of daily updates provided. (CLIN 0004)

4.2 The contractor shall immediately report issues or events that will impact the contractor’s performance and services under this PWS. Situations that warrant the contractor to submit a report to the COR and Technical Representative includes, but is not limited to, the following:

4.2.1 An error or issue with accuracy has been detected, and updates to previous transmissions must occur.

4.2.2 Remote data access capability will be undergoing maintenance or due to other reasons, not be available for access by users

4.2.3 Any situation that could potentially disrupt the contractor’s ability to perform any work needed to satisfy the requirements of this PWS.

4.3 The Government will allow for short term fluctuations (some useful data must be delivered during this time) due to factors outside the contractor’s control (i.e., natural disaster, political instability). However, these fluctuations shall be deemed unacceptable if they continue longer than one calendar week. The Government will also use the following method to ensure that the data remains consistent and within specifications:

4.4 The Government shall monitor the daily data delivery and over the first month of the period of performance develop an average number of updates per day. All subsequent months will be compared with the baseline month to determine performance.

4.5 The Government will conduct an analysis on data processed each month. Periodic checks shall be made between data being provided via the update files and data accessible via remote login to ensure both are in agreement. The Government will also compare the monthly reports provided by the contractor with observer totals.

4.6 A monthly performance number shall be derived by comparing the observed totals with the baseline totals.

4.7 If the contractor monthly performance number fails to be within 25%, as calculated by the Government, of the baseline performance number, the contractor will be warned to either rectify the shortfall within the next month or inform the Government as to the reason for the shortfall.

4.8 If the data source has a second calendar month of performance that fails to be within 25% of the baseline performance number, the Government shall deem the contractor’s performance unacceptable. If the contractor cannot bring the performance back within specification, the government shall take additional steps, up to and including, termination of the contract.

5.0 Reference Documents

5.1 This effort does not require strict contractor adherence to military specifications and standards governing hardware, formal testing programs, technical data and handbooks, or other standard practices normally applied to the design, development and acquisition of military systems except as otherwise directed by the particular task or Government representative. The contractor must, however, always adhere to best commercial practices concerning systems, personnel safety, service quality, data integrity, and task performance. The COR or other agencies as required must identify documentation on systems or information analysis processes when appropriate.

6.0 Subcontractor Support

6.1 Subcontractor support may be required in the performance of individual requirements of this PWS in which the prime contractor does not have either the direct access to the data or the technical capability to accomplish the tasks. Subcontractor support must be determined on a case-by-case basis and as proposed in the relevant requirement. The use of a particular subcontractor is subject to approval by the contracting officer.

Appendix A Required Data Fields Required data fields (Not all Vessels will have data in all Fields)

Appendix B Required Ship Types

Bulk Single Product Carrier Combination Bulk/Other Carrier Intergraded Tub Barge/Bulk Unit Ore Carrier River-sea Bulk Vessel

Break Bulk, Dry Cargo Vessel Container Vessel General Cargo River-sea Vessel Heavy Lift Vessel Intergraded Tug and Barge units Large Unit Carriers Vessel Livestock Carrier Vessel Passenger Cargo Vessel Railcar Carrier Refrigerated Cargo Vessel Roll-on/Roll-off Vessel Vehicles Transport Vessel

Fish Base Vessel Fish Factory Vessel Fish Factory Trawler Refrigerated Processed Fish Transport Vessel Seal Catcher Seiners Shrimp Trawler Trawlers Tuna Clipper Whale Catcher Whale Factory Vessel

Depot Vessel Hospital Vessel Military Auxiliaries in Merchant Service Unidentified Vessel type

Non-Displacement Hovercraft Passenger Vessel Passenger Vessel River Sea Passengers Vessel Short Sea Passenger/Car/Rail Vessel

Hydro-meteorological Research Vessel Oceanographic Research Vessel Space Event Support Vessel Weather Ship

Cable Vessel Construction Vessel Crane Vessel Crew/Supply Vessel Deep-sea Mining Vessel Diving/Submersible Support Vessel Dredge Drill Rig or Platform / Jackup, Semi Submersible, Drill Barge Lighthouse and Buoy Tender Offshore Supply Vessel Pilot Vessel Pip Laying Vessel River/sea Service Craft Salvage Vessel Self Propelled Drill Ship Standby Vessel Tank Cleaning Vessel Tug/Supply Vessel Waste Disposal Vessel

Chemical Tanker Combination Ore/Bulk/Oil Vessel Combination Ore/Oil Vessel Crude Tanker Edible Products Tanker Fuel Oil/Bunkering Tanker General Tanker Intergraded Tug and Barge/Tanker unit Liquefied Gas Tanker Liquid Cargo Carriers River/Sea Products Tanker Shuttle Tanker Water Tanker

Training Vessel

Intergraded Tug Barge/Tug Only Ocean or Seagoing Tug

Multi hull Yacht Sailing Yacht Sport Fisher