A02.12 PWS Vessel Data Registry Subscription.docx
DOCX document 43 KB Posted
- Solicitation number
- W912HQ23R0002
View the file
Other files
| File | Type | Posted |
|---|---|---|
| B08.03 Answers to Questions W912HQ22R0002 - Vessel Data Registry.docx | DOCX document | |
| B01.01 CSS - W912HQ22R0002 - Vessel Data.docx | DOCX document |
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
Acquisition of Commercial World Fleet Vessel Register Data & Information for Application to Data Verification & Analysis in Support of the Waterborne Navigation Program of the U.S. Army Corps of Engineers (USACE)
Acquisition of Subscription Service for World Fleet Ship or Vessel Register Data
Performance Work Statement (PWS) or Scope of Specifications
Basis Document for Request of Formal Quote from Vendor
December 2022
1.) Introduction
The content of this performance work statement (PWS) or statement of work is to provide background and needs pertaining to vessel register information needed by the Waterborne Commerce Statistics Center (WCSC, located in New Orleans, Louisiana) of the Institute for Water Resources (IWR) and the capital region and headquarters office of IWR (located in Alexandria, Virginia) of the U.S. Army Corps of Engineers (USACE). The requirements as set forth are for or in context of an openly competitive announcement and solicitation for fulfillment of requirements and specifications as described or set forth herein. If any interested vendor needs to pose any inquiry for clarification(s) of scope and requirements, they are encouraged to do so via the contact information listed for this posting of PWS requirements as described herein.
The Waterborne Commerce Statistics Center (WCSC, New Orleans, Louisiana) of the Institute for Water Resources (IWR) and the capital region office of IWR (Alexandria, Virginia) of the U.S. Army Corps of Engineers (USACE) compiles, processes, and analyzes data and information for waterborne transportation and associated trade, and affiliated services involved with the conduct of both domestic and foreign trade critical to the economy of the United States. The data and information assembled by WCSC and IWR are employed in the engineering and economic evaluation of Federally-sponsored waterway improvements for coastal harbors and deep-draft approach channels and waterways in addition to internal or inland waterway(s) systems. Such improvements include placement of new general navigation features (GNFs) such as channels or vessel maneuvering areas and enhancements to existing features. Enhancements may include deepening and enlargement of maneuvering areas to accommodate evolving changes in vessel or fleet characteristics and fleet service regime driven by trade and demand for supporting waterborne transport. In the same contexts of evaluation of new GNFs or related enhancements, subject data and information is also routinely employed to inform agency (USACE) decisions for management of operation(s) and maintenance (O&M) within the framework of budgetary and fiscal resource constraints of the agency’s waterborne navigation program.
Part of the information essential to waterway system evaluations includes the specifications of vessels including vessel type, physical dimensions, capacities, and other characteristics, including (but not necessarily limited to) age, powering and immersion. The WCSC employs this data and information to help verify the identity of vessels with linkage of vessel and trade tonnage movements to develop a more complete profile of trade statistics used for decision-making and evaluations of waterway system projects. Analysts at IWR and in the field use described information to conduct economic and engineering evaluations to assess the feasibility and economic return of new construction, physical improvements or enhancements, and O&M initiatives based on transportation cost efficiencies made possible by such measures, such as or including loading and operating vessels more efficiently than would otherwise be possible (without specified improvements or enhancements).
2.) Requirements\Specifications
The requirements outlined herein set forth description and specifications for contractual agreement and fulfillment by the vendor in terms of the following general technical requirements:
· 1.) Duration of time and frequency of provision or update of specified data and information over time.
· 2.) Coverage of the world fleet and respective data, with Individual data fields for physical specifications and descriptive characteristics (IMO hull number, DWT, etc.) needed with consideration to degree of fleet coverage and data fill for respective fields.
· 3.) Privileges for Distribution or Sharing of Data (internal to USACE).
1,) Duration of time and frequency for data provision. The duration for contractual services described herein shall be for one (1) calendar year (or 365 calendar days) with update of specified data fields on approximately a monthly basis providing for one initial download of vessel register data to be provided within five (5) calendar days of contract award or notice to proceed (NTP) followed by an additional twelve (12) downloads or postings of data at intervals of approximately 29 to 31 calendar days extending from the date of initial download for provision of data products. Data downloaded at each interval will be of the same or comparable specification but with update and accounting for more current information as compiled by the vendor for update and maintenance of its vessel register product over the corresponding time period. Each download or posting will be electronically facilitated with placement to agreed-to file transfer protocol (FTP) site address(es) or location(s) to be put in place or devised by the vendor employing vendor data storage assets and safeguarded by measures for controlled access.
2.) Individual Data Fields and Coverage - The specifications for coverage of the database downloads provided will extend to all commercial vessels of any or all sizes covered by the vendor’s vessel register. Three (3) general realms of coverage are specified for vessel data register acquisition. These are and extend to all vessels carried and inventoried, and to be made available:
- a.) the active\temporarily inactive or live vessel database (to be provided for both WCSC and IWR),
- b.) newbuilds as made available by corresponding monthly update (to be provided for both WCSC and IWR);
- c.) the database of vessels assessed as fully inactive or permanently withdrawn from service including those broken or lost (dead ships register database; all specified fields as applicable or to the extent available; to be provided only to IWR) and
- d.) the vessels on-order database (to be provided only to IWR)
· Specified data fields. The requirements for data to be provided includes fields for various vessel specifications and characteristics totaling108 unique data or information fields in number. Of these fields approximately 33 are required needed by the Waterborne Commerce Statistics Center (WCSC) for data verification and cross-referencing with additional fields needed by IWR for other applications relevant to waterway project analysis and evaluation. The data or information fields required according to technical needs of each organization (WCSC and IWR) are listed below in Table 1 as follows:
Table 1 – Listing of Vessel Register Data Fields as Identified for Needs of the Waterborne Commerce Statistics Center (Part of IWR located in New Orleans, Louisiana) and IWR Analytical Applications (Alexandria, Virginia)
FIELDS AS IDENTIFIED BY TYPICAL OR COMMON LABELING
WCSC
IWR
FIELD NAME ONLY
Needs
Needs
| 1 |
| Ship or Vessel Name |
x x
| 2 |
| Ship or Vessel Name Effective Date |
x
| 3 |
| Ship or Vessel Ex or Prior Name |
x
| 4 |
| LR IMO Ship No |
x x
| 5 |
| Maritime Mobile Service Identity (MMSI) Number |
x x
| 6 |
| Official Number |
x x
| 7 |
| Call Sign |
x
| 8 |
| Date of Build |
x x
| 9 |
| Death Date |
x x
| 10 |
| Ship Status |
x x
| 11 |
| Flag Name |
x x
| 12 |
| Flag Effective Date |
x
| 13 |
| StatCode5 |
x x
| 14 |
| Shiptype Level 5 |
x x
| 15 |
| Ship Type Group |
x
| 16 |
| Operator |
x x
| 17 |
| Registered Owner |
x x
| 18 |
| Shipbuilder |
x
| 19 |
| Group Beneficial Owner Country of Control |
x
| 20 |
| Group Beneficial Owner Country of Domicile Code |
x
| 21 |
| Country of Economic Benefit |
x x
| 22 |
| Country of Build |
x
| 23 |
| Bulbous Bow |
x
| 24 |
| Ice Classification \ Class Level |
x
| 25 |
| IMO Chemical Class I |
x
| 26 |
| IMO Chemical Class II |
x
| 27 |
| IMO Chemical Class III |
x
| 28 |
| Length Overall LOA |
x x
| 29 |
| Length Between Perpendiculars LBP |
x x
| 30 |
| Breadth Extreme |
x x
| 31 |
| Breadth Moulded |
x x
| 32 |
| Depth (or Moulded Depth) |
x x
| 33 |
| Draught or Maximum Summer Loadline Draught |
x x
| 34 |
| Parallel Body Length Ballast |
x
| 35 |
| Parallel Body Length Laden |
x
| 36 |
| Parallel Body Length Light |
x
| 37 |
| Keel to Mast Height |
x
| 38 |
| Displacement |
x
| 39 |
| Light Displacement Tonnage |
x x
| 40 |
| Deadweight |
x x
| 41 |
| Gross Tonnage |
x x
| 42 |
| Compensated Gross Tonnage CGT |
x
| 43 |
| Net Tonnage |
x x
| 44 |
| Panama Canal Net Tonnage PCNT |
x
| 45 |
| Suez Canal Net Tonnage SCNT |
x
| 46 |
| Tonnes Per Centimetre Immersion (TPCI) |
x
| 47 |
| Open Hatch ContainerShip (Indicator) |
x x
| 48 |
| TEU |
x x
| 49 |
| TEU Capacity 14t Homogenous |
x x
| 50 |
| Number of Refrigerated Containers |
x
| 51 |
| Reefer Points |
x
| 52 |
| Bale (Cubic) Capacity |
x
| 53 |
| Grain (Cubic) Capacity |
x
| 54 |
| Liquid (Cubic) Capacity |
x
| 55 |
| Gas (Cubic) Capacity |
x
| 56 |
| Insulated Capacity |
x
| 57 |
| Clean Ballast Capacity |
x
| 58 |
| Number of Tanks |
x
| 59 |
| Number of Cargo Tanks |
x
| 60 |
| Number of Holds |
x
| 61 |
| Passengers Berthed |
x
| 62 |
| Number of Cabins |
x
| 63 |
| Number of Cars |
x
| 64 |
| Number of Gears |
x
| 65 |
| Gearless |
x
| 66 |
| Pumping Capacity (Cubic Meteres) |
x
| 67 |
| Main Engine Designer |
x
| 68 |
| Main Engine Builder |
x
| 69 |
| Main Engine Model |
x
| 70 |
| Main Engine Type |
x
| 71 |
| Main Engine Stroke Type |
x
| 72 |
| Main Engine Number of Cylinders |
x
| 73 |
| Main Engine Bore |
x
| 74 |
| Main Engine Stroke |
x
| 75 |
| Main Engine RPM |
x
| 76 |
| Main Engine BHP |
x
| 77 |
| Main Engine KW |
x
| 78 |
| Auxiliary Engine Number |
x
| 79 |
| Auxiliary Engine Type |
x
| 80 |
| Auxiliary Engine Number of Cylinders |
x
| 81 |
| Auxiliary Engine Bore |
x
| 82 |
| Auxiliary Engine Stroke |
x
| 83 |
| Auxiliary Engine Max Power |
x
| 84 |
| Auxiliary Generators Number |
x
| 85 |
| Auxiliary Generators KW Each |
x
| 86 |
| Speed Maximum |
x
| 87 |
| Speed Service |
x
| 88 |
| Fuel Type (Propulsion) |
x
| 89 |
| Fuel Type Capacity (Propulsion) |
x
| 90 |
| Fuel Consumption Speed 1 |
x
| 91 |
| Fuel Consumption Speed 2 |
x
| 92 |
| Fuel Consumption Value 1 |
x
| 93 |
| Fuel Consumption Value 2 |
x
| 94 |
| Fuel Type (Auxiliaries) |
x
| 95 |
| Fuel Type Capacity (Auxiliaries) |
x
| 96 |
| Bunkers Descriptive Narrative |
x
| 97 |
| Total Bunker Capacity |
x
| 98 |
| Number of Propulsion Units |
x
| 99 |
| Propeller Type |
x
| 100 |
| Propeller Type Code |
x
| 101 |
| RPM Service |
x
| 102 |
| RPM Maximum |
x
| 103 |
| Number of Thrusters |
x
| 104 |
| Thrusters Position |
x
| 105 |
| Thrusters BHP |
x
| 106 |
| Scrubber Designer |
x
| 107 |
| Scrubber Retrofitted |
x
| 108 |
| Scrubber Type |
x
Total Fields
Fields Common to Needs of Both Organizations
Fields Not Common to Both Organizations
Total Number of Unique Fields
Verification
1.) It is recognized that not all field names are common to different registers of varying vendors. Field names as listed are based on past or prior experience with vessel registers. Any potential interested vendor may or is invited to inquire as to compatibility of field names or field name meaning in event they are concerned for comparable or equal data content relative to field names or varying labeling.
· The vendor will be required to provide separable costs for the filed listing as required only for WCSC and related conditions for use in addition to the total costs for all fields (needs for WCSC and IWR combined) and specified conditions for use, Coverage and related availability of valid data and information relative to cost will be the primary criteria for evaluation of vendor vessel register products or offerings. To additionally clarify the contexts of coverage, this includes the propensity for coverage of the world fleet largely based on the corresponding number of ships active in open trade world wide and included in the database as well as the completeness of data for each ship record or profile in the database. Additional or relevant interest extends to vessel types and size classes commonly or likely to be involved in transoceanic trade and serving ports of the coastal United States as well as the maintenance of record for vessels permanently withdrawn from or no longer in service (dead ships database). Accordingly, in response to specifications and needs for information set forth herein and to provide better insight as to the likely relevant vessel population covered for vendor product evaluation, any interested vendor will be required to provide in any proposal submitted the number of vessels covered or available in the database according to the following deadweight tonnage (DWT) and maximum summer load line draft delineations subject to one general grouping for all vessels and three (3) groupings or sub-groupings for the specified basic ship types:
1.) Number of vessels below 20,000 DWT; with counts for groupings of a.) all vessels combined, and b.) separately each for tankers (liquid bulk), (dry) bulk carriers, and fully cellular containerized carriers.
2.) Number of vessels ranging from 20,000 to 60,000 DWT; with counts for groupings of a.) all vessels combined, and b.) separately each for tankers (liquid bulk), (dry) bulk carriers, and fully cellular containerized carriers.
3.) Number of Vessels above 60,000 DWT; with counts for groupings of a.) all vessels combined, and b.) separately each for tankers (liquid bulk), (dry) bulk carriers, and fully cellular containerized carriers.
4.) Regarding a basic measure for completeness of field coverage, any interested vendor will be required to provide an estimate of valid data fill or entry for each individually requested field based on or measured as a percentage of all vessel entries in the database with DWT equal to and over 5,000 DWT.
5.) Respective to maximum summer load line draft, total counts will be provided for all vessels combined as an overall group according to whether Foreign and U.S. Foreign service registry combined and separably for U.S. flag domestic registry (Jones Act qualified) with each respective registry grouping delineated according to hulls with maximum summer load line drafts of less than 12 feet, equal to or greater than 12 feet but less than 20 feet, 20 feet to less than 46 feet, 46 feet and greater.
6.) Specific to passenger vessels; deep-draft or ocean-going in general classification of service, any interested vendor will be required to provide hull counts delineated by the following; all vessels with maximum summer load line drafts of less than 20 feet, 20 to less than 28 feet, 28 feet to 36 feet and more than 36 feet (if any applicable). Respective to each of these delineations or draft groupings the contractor will also provide average Gross or Gross Registered Tonnage (GRT) and the average capacity for (berthed) passengers.
3.) Privileges for Distribution, Sharing, and Retention of Data
The WCSC (New Orleans, Louisiana) and IWR (Alexandria, Virginia) have requirements for distribution or sharing of subject vessel register data and information to be acquired from the vendor. The data fields as identified specific to needs of the WCSC and IWR are listed separably in Table 1, preceding. Specific to all data fields acquired for the WCSC including those that also have common use to needs of IWR, required privileges for distribution and sharing include:
· the ability to share data at the detail or individual ship record level for the active vessel database with any organizational entity within or throughout the U.S. Army Corps of Engineers (USACE) to include District and Division Offices, and any other official organizational entity internal to USACE that acceptably substantiates valid and reasonable need for provision of subject data. Subject parties with whom detailed data is shared beyond WCSC and IWR will not share or disclose data at the detailed level outside the direct control of USACE, with any other entity whether Governmental (including state Federal governmental agencies or entities) or in the private sector, or of the public at large.
· Respective to fields identified for the active vessel database identified as unique to needs of IWR in Table 1, specified fields will only be distributed or shared within IWR and with the applicable centers of expertise for analysis of waterborne navigation (with centers located in Mobile, Alabama and Huntington, West Virginia). The centers for navigation studies will provide signatory concurrence for acceptance of these conditions before data and information are shared. Data identified as unique to needs of IWR will not be distributed or shared at the detailed or individual record level with any other entities internal or external to USACE. With further elaboration, detailed-level data will not be distributed to entities outside of USACE such as (and not necessarily limited to) other Governmental agencies (both Federal and non-Federal), commercial entities, regulatory bodies, public interest or research and non-profit organizations, the public at large, or any other entity or organization not expressly identified herein as having need or justification for sharing of subject data external to USACE. Internally to USACE, subject data will not be shared with any additional organizational elements outside of IWR or the designated centers for navigation studies. Such entities with which data will not be shared include (but are not necessarily limited to) any USACE District, Division, HQUSACE headquarters office, field office, laboratory, research entity or activity, contractor or affiliated organization, or any other administrative or technical work element not otherwise specifically and explicitly identified herein as having viable needs for provision of respective privilege(s) regarding distribution and sharing of subject data and information. Regarding provision of the permanently inactive or dead ships database and the ships on order database for contractual requirements described herein, associated data is to be provided only to IWR, with specifications and limitations on distribution and sharing of all associated data fields as described for active ship data and fields unique to needs of IWR (Alexandria, Virginia) and the applicable centers of expertise for analysis of waterborne navigation (Mobile, Alabama and Huntington, West Virginia).
While no further sharing of detailed data (at the individual ship record level) will be beyond that generally described, aggregated statistics (data averages or ranges, etc.) derived from the detailed statistical records database may be used or released to only the extent necessary in technical documentation and reporting sufficient to convey the context or framework of analytical methods, procedures, and findings or conclusions derived from project analyses and evaluations employing subject data of concern. Additionally, detailed data will be used to assemble statistical reports comprised of aggregated statistics such as averages and ranges for data which may be shared with other Federal agencies or outside the realm of Federal agencies as deemed to be in the public interest respective to the missions and duties of USACE.
In addition to the above description of privileges for distribution and sharing of data. USACE periodically has needs to make detailed information available for external independent technical review of project studies and evaluations. Typically, such reviews are performed by specialists in other governmental agencies or academicians affiliated with academic institutions with relevant knowledge, skills, and experience. Within these requirements as they arise, data at varying levels of detail employed or relevant to a given project evaluation and technical review sometimes needs to be made available to entities performing the review to independently determine the viability of evaluation methodologies or approach, findings, conclusions, and as applicable, any recommendations. Correspondingly, privileges for distribution and sharing of relevant data will be granted on an as needed basis and only with mandate of requirements for written signatory agreements for both non-disclosure (NDA) and non-alternative use of provided data and information (NAUA; precluding use or reference for any other purpose than as needed for the specified review tasking).
To reiterate and summarize consistent with the preceding generally described needs for distribution and sharing for both USACE technical or analytical use and technical review, data at the detailed or individual vessel record level will not otherwise be distributed or shared outside of USACE or internally beyond IWR and the navigation centers of study.
Any and all data and information once purchased for a given period or coverage through time shall remain the property of the Government in perpetuity for any applicable need to evaluate historical data or trends for vessel fleet structure(s) over time subject to the privileges for distribution and sharing set forth under this performance work statement.
4.) Summary Statement of Deliverables
Subject to the requirements and specifications as set forth herein, the vendor or contractor will provide the following:
1.) For a period of one year (via secure FTP websites or addresses), monthly releases with initial provision within five (5) calendar days of contract award and notice to proceed (or NTP), and every 30 to 31 days thereafter for an additional 12 releases or installments (over one calendar year) of the active\live vessels database for all commercial vessels contained in the vendor’s vessel register database, with specifications and privileges for distribution and use as described under preceding Sections 2 and 3 of the PWS as set forth herein. This requirement pertains to two generalized specifications of the database(s) to be provided:
a. The active\live ships database and newbuilds with ongoing periodic updates for all specified fields to be provided to or for both the WCSC and IWR with agreement between the vendor and Government for described privileges for distribution and sharing of associated data and information.
b. The permanently inactive or withdrawn (dead) ships and ships on-order databases only to IWR with agreement between the vendor and Government for described privileges for distribution and sharing of associated data and information.
In the interests of efficiency for USACE needs for download and use of provided data products, the preferred format for provision or transmittal of the initial and each periodic provision or release thereafter of vessel register database product(s) is a database structure contained within a single electronic file in CSV format readily importable and readable via electronic file format compatible with current versions of ORACLE\Apex and Microsoft Excel with appropriate formatting for full transfer of numerical versus text or non-numeric entries. It is requested that two FTP addresses or sites be set up for provision of data products with requirements for data and information specific to needs for the WCSC be downloaded to one FTP address while data and information as described specific to the needs of IWR be provided or made available via another FTP address or site.
Specific to the preceding and for purposes of costing it is requested that the vendor provide estimates for the grouping of fields respective privileges of use required only for WCSC and another estimate for the total number of all fields for both entities combined subject to considerations of privileges for distribution and sharing and frequency of update.
5.) Requirements for Operational Security (OPSEC)
Primary Contract Specifications for Compliance with Operational Security (OPSEC) Requirements
The requirements for acquisition of data and information as described herein primarily constitute procurement of a data service subscription for data and information as the vendor compiles and vends or sells it for a variety of clients and related needs. The contractor will not have access to any network, server, or computerized system operated or controlled by USACE. There is no requirement for contractor personnel to visit or enter any USACE or DoD facilities in fulfillment of this contract. The contractor will place or establish file transfer protocol (FTP) address(es) or website(s) from which provided data and information will be retrieved. The established FTP website(s) will have reasonable and sufficient measures to safeguard against unauthorized access or retrieval and infection or corruption from malicious code or software. The contractor will be required to detail or describe the specifications of measures applied for OPSEC of the FTP website(s) or address(es) and the procedures for USACE personnel to securely retrieve subscription data and information to be provided under the PWS specifications herein. The contractor will actively or periodically monitor FTP website(s) or address(es) for any unauthorized or suspicious activity or operation any of which should it occur is to be immediately reported to the designated technical points of contact (TPOCs) for this PWS via both telephone and email (Ian Mathis; 703-428-7257, ian.a.mathis@usace.army,mil, or Kevin Knight, kevin.p.knight@usace.army.mil, 703-428-7520). Upon any such occurrence of activity the contractor and the designated POCs for IWR will need to confer and agree on remedial measures or alternatives for safe and secure provision of subject data and information.
END – Performance Work Statement (PWS) Technical Specifications\Description; Acquisition of World Fleet Vessel Register
File details come from the government source that posted it. Updated .