PWS AIS Trasmit 2020.docx

PERFORMANCE WORK STATEMENT

SUPPORT FOR U.S. ARMY CORPS OF ENGINEERS

AIS Transmit Development

1.0 BACKGROUND

The U.S. Army Corps of Engineers (USACE) provides navigation safety information to vessels operating on waterways where the Corps manages, maintains, and operates infrastructure (e.g., structures, channels, locks & dams). Much of this information is of a dynamic nature, and dissemination to vessels is difficult through traditional means (e.g., paper products, charts, radio notices, etc.). USACE also needs to monitor various conditions on the waterways in which it has responsibilities, including meteorological and hydrological information, navigation chart discrepancies, and anomalies in other navigation systems (e.g., GPS). The Automatic Identification System (AIS) provides the ability for information to be exchange between USACE systems (such as the Lock Operations Management Application (LOMA)) and vessels via wireless and digital means. This effort is intended to continue development and deployment of capabilities to maximize the exchange of navigation related information using AIS.

2.0 SCOPE

This effort will focus on 4 general areas:

a. AIS transmit capability operationalization

· Navigation data access and message creation

· System monitoring and reliability assurance

b. AIS Standards development

c. AIS equipment and software evaluation

d. Advanced ship-shore data communications via AIS

· Automatic weather observations via AIS

· Leveraging AIS to detect and communicate GPS spoofing and jamming

3.0 SPECIFIC REQUIREMENTS AND TASKS

3.1 AIS transmit capability operationalization

3.1.1 Incorporation in the LOMA system: Integrate existing and new AIS transmit tools (e.g., ASMManager, GN and AtoN Creation tools) into the LOMA system. Evaluate new ASM including weather observations, Geographic Advisory, and others developed domestically or internationally. Work with CNS Systems (LOMA contractor) to determine best integration method, including evaluation of including capabilities in the CNS LOMA software, connection to external applications, or web services integration.

3.1.2 Transmit capability procedures: Evaluate current and draft procedures used for AIS transmissions, e.g., AIS AtoN establishment, geographic notice transmission. Develop recommendations for procedural changes or establishment of new procedures. Identify any policy issues affecting USACE, USCG or other agencies. Include developing procedures/tools to monitor field use of AIS transmit (e.g., "approval" process and tools to document/monitor). Test all software in the lab environment. Once debugged install and test in at least one lock site.

3.1.3 Transmit monitoring capabilities: Investigate existing tools for and capabilities for monitoring AIS transmissions from USACE transceivers to verify actual transmission and accuracy of transmitted data. Evaluate the probability of reception of transmitted massaged from a specified receiver in a geographic area. Develop procedures/capabilities to monitor all scheduled transmissions to ensure they are actually going out accurately; e.g., permanent AIS AtoNs; GNs only effective during a designated time period, etc. Provide a "dashboard" capability, integrated into the LOMA Admin Console to continuously monitor and identify problems. This should include a logging function to log for auditing and availability purposes.

3.1.4 Develop a system for monitoring USACE AIS transmit operations. Assess the current locations of transmit sites and recommend options for monitoring sites to ensure that all transmissions can be monitored both from the transmit site itself as well as from a receiver site (which could be another transmitter if coverage overlaps). Identify a method for measuring and monitoring "success" of transmissions as well as monitoring VDL usage. Develop software to implement this method including a GUI with “dashboard” view for the operator

3.2 AIS standards development

3.2.1 Provide technical information for USACE participation in various bodies developing AIS-related standards and guidelines, e.g. the Radio Technical Commission for Maritime Services (RTCM), International Associations of Marine Aids to Navigation and Lighthouse Services (IALA), International Electrotechnical Commission (IEC), and the Permanent International Association of Navigation Congresses (PIANC). This support may include review of pre-meeting documents, preparation of input papers, analysis of existing and proposed standards and guidelines in comparison with USACE priorities and requirements, and development of technical recommendations in support of USACE priorities.

3.3 AIS equipment and software evaluation

3.3.1 Assist ERDC-CHL technicians in evaluation of new AIS hardware and software for use in the LOMA system. This will include evaluation of LOMA AIS transceiver units, LOMA system software, third party software, and new AIS transceiver equipment against identified USACE requirements.

3.3.2 USACE-USCG interoperability: Develop and test procedures and configurations for direct connections to allow two-way exchange of AIS messages between USACE and USCG production systems. Work will include identification of any issues to be addressed such as routing of acknowledgement messages, avoidance of duplication of messages, assurance of message delivery, latency minimization, conformance with cybersecurity and information assurance requirements, and similar considerations. Prepare a tech note to document issues identified, configuration recommendations, and other information needed to implement direct connection in the production environment.

3.4 Advanced ship-shore data communications via AIS

3.4.1 Automatic weather observations via AIS: Continue development and deployment of equipment and software to support the automatic collection of weather observations from commercial vessel for transmission from installed AIS equipment and reception by satellite and shore AIS networks. Work with identified receivers of this information including the National Weather Service, and private entities to deliver the parsed messages in a usable format and to database or databases for archive and dissemination. Capture information on costs for equipment, software and maintenance, requirements for long-term operation, and development of requirements. Prepare documentation of tests and results, including lessons learned, recommendations for additional research, and an evaluation of the feasibility of wide-spread deployment of this capability, including potential for changes to AIS or other standards and national and international carriage requirements.

3.4.2 Leveraging AIS to detect GPS spoofing and jamming: Evaluate the feasibility of using existing AIS and GPS equipment aboard commercial vessels (including equipment installed in support of 3.4.1 above) to detect and communicate GPS spoofing and jamming. Conduct proof-of-concept and feasibility tests on appropriate vessels. Document findings and make recommendations regarding feasibility, and costs.

3.4.3 Investigation of other opportunities for ship-shore communication: Based on the experience gained in 3.4.1, investigate the feasibility of using AIS to communicate other information from vessels to stakeholders ashore, including electronic chart (ENC/IENC) discrepancies, collection of crowd-sourced bathymetry, and other applications of opportunity.

3.4.4 VDES development: Monitor the development of VHF Data Exchange System (VDES) developments at IALA, IEC, and other involved bodies. Conduct VDES tests as appropriate, taking into consideration USACE-defined data communications requirements, national and international radio policies and regulations.

4.0 SCHEDULE

4.1 Within 15 days of the notice to proceed, a kickoff meeting will be held to review the task list, identify additional information needs and begin prioritization and level or effort determinations. Within 30 days of the kickoff meeting a schedule will be developed for delivery of identified capabilities.

5.0 DOCUMENTATION

5.1 Unless otherwise specified or directed, all documentation delivered should be in the appropriate USACE ERDC format (e.g., Technical notes and Technical Reports), and appropriate for capturing and transferring capabilities developed in this PWS.

5.2 Documentation specified in section 9.1 of this PWS.

5.3 Any documentation required for information assurance (IA) certification and ACE-IT requirements.

6.0 PERIOD OF SERVICE

6.1 The period of performance is one year, with two one-year options.

7.0 GUIDANCE

7.1 The Contractor is cautioned to take no guidance regarding interpreting specific requirements of the Contract during the course of services rendered from any source other than the contracting officer (KO). As a result of this contract, any technical papers, conference proceedings, advertisements, articles, etc., on behalf of the contractor generated as the result of this effort must be approved in advance by the Corps of Engineers.

8.0 PROJECT MANAGEMENT

8.1 The contractor is required to provide a project plan and work break down structure to include schedule, milestones and resources within 30 days of NTP

8.2 The contractor is required to provide a change management plan within 30 days of NTP.

8.3 Periodic IPRs will be conducted with the Corps project manager and technical team. Details on how best to accomplish this will be developed with the contractor within the first 30 days following contract award.

9.0 DELIVERABLES

9.1 Software and other products as described in section 3.0 Specific Requirements and Tasks, including:

9.1.1 Updated ASMManager, GNCreator, VACT, and other software and documentation.

9.1.2 Lock and Dam Status Message Fetcher/Formatter software and documentation for installation, configuration and use.

9.1.3 USACE-USCG interconnection documentation for installation, configuration and use.

9.1.4 Report of evaluation of any AIS equipment tested, including assessment of its ability to meet USACE-identified requirements

9.1.5 Technical reports and Technical notes for the Wx via AIS project; specifically report of test aboard TS Kennedy and initial commercial vessel deployments between October 2018 and April 2020; interim test of installations aboard commercial vessels between August 2019 and January 2021.

9.2 Journal articles and conference presentations, including Transportation Research Board 2021 paper, and other conferences as identified.

9.3 Monthly progress reports including details on budget burn rate, percentage complete, anticipated spend plan, etc.

9.4 Documentation per Section 5 of this Scope of work (SOW).

10.0 Contracting Officer’s Representative

Doyle Jones 601-634-2069 Doyle.L.Jones@usace.army.mil

11.0 SECURITY REQUIREMENTS.

11.1 U.S. Citizens. Contractor personnel must be U. S. citizens. All Contractor personnel are required to sign in with Security to obtain and wear security identification badges. A picture ID is required. Contractor personnel shall follow all sign-in and security regulations as directed by the ERDC Security Office and the TPOC.

11.2. Access and General Protection Policy and Procedures. Access and General Protection/Security Policy and Procedures: The contractor and all associated subcontractors’ employees shall comply with applicable installation, access and local security policies and procedures. Policies and procedures will be provided by the ERDC Security Office. The contractor workforce must comply with all personal identity verification requirements as directed by DoD, HQDA, and local policies. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

11.3. iWATCH and/or CorpsWatch Training. The contractor and all associated subcontractors shall brief all employees on the USACE iWATCH program. This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 45 calendar days of contract award and within 45 days of new employees commencing performance on the contract. The contractor shall provide certification of completion to the COR within 10 days of training completion. Training documents will be provided by the Security Office.

11.4. Subcontractor Access/Deliveries. The Contractor shall notify the COR the day before or as soon as possible when subcontractors are to arrive or deliveries of equipment and supplies are to occur. This will facilitate access on to the installation and prevent delays at the security gates.

11.5 Personnel Security Screening. The Contractor must pre-screen Candidates using the E-verify Program (http://www.uscis.gov/everify) website to meet the established employment eligibility requirements. The Vendor must ensure that the Candidate has two valid forms of Government issued identification prior to enrollment to ensure the correct information is entered into the E-verify system. An initial list of verified/eligible Candidates must be provided to the COR no later than 3 business days after the initial contract award.