Amendment 0001_W912HZ20R0035.pdf
PDF 415 KB Posted
- Attached to
- AIS Transmit Development
- Solicitation number
- W912HZ20R0035
About this file
This amendment modifies a solicitation for Automatic Identification System (AIS) transmit development services. The U.S. Army Corps of Engineers seeks a contractor to operationalize AIS transmit capabilities, develop AIS standards, evaluate AIS equipment and software, and advance ship-to-shore data communication via AIS. The contractor will integrate AIS tools into the Lock Operations Management Application, develop transmit procedures, and monitor transmissions. Additional tasks include providing technical input to AIS standards bodies, assisting with AIS hardware and software evaluations, and investigating opportunities to transmit weather observations, detect GPS spoofing, and exchange other data between vessels and stakeholders using AIS. The period of performance is one base year with two optional one-year extensions. The contractor must begin work within 30 days of the notice to proceed and provide regular progress and financial reports. The designated NAICS code is 541519 with no set-aside. The solicitation number is W912HZ20R0035.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Solicitation_W912HZ20R0035.pdf | ||
| Attachment 1 - Past Performance Questionnaire.pdf |
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
W81EWF01180813
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER (Type or print)
30-105-04EXCEPTION TO SF 30
APPROVED BY OIRM 11-84
STANDARD FORM 30 (Rev. 10-83)
Prescribed by GSA
FAR (48 CFR) 53.243
Amendment 0001 is being issued to include Questions/Answ ers. Section G - General Information is being deleted in its entirety. See Section L for Instructions.
1. CONTRACT ID CODE PAGE OF PAGES
J 1 9
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 02-Sep-2020
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W912HZ20R0035
X 9B. DATED (SEE ITEM 11)
25-Aug-2020
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE
RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN
REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
01-Sep-2020
CODE
ERDC CONTRACTING OFFICE
3909 HALLS FERRY ROAD
VICKSBURG MS 39180-6199
W912HZ 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
W912HZ20R0035
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION SF 30 - BLOCK 14 CONTINUATION PAGE
The following have been added by full text:
QUESTIONS AND ANSWERS(0001)
QUESTION: Is there any anticipated travel? If travel is anticipated, please describe. If travel is anticipated, will it be funded separately or is it to be part of the FFP?
ANSWER: Yes, contractor travel is anticipated for installation of equipment at test locations and should be part of the FFP.
QUESTION: Re: General Information section #7 reads:
“COMPLETE APPLICABLE INFORMATION ON THE FRONT OF THIS FORM
(STANDARD FORM 1449), THE BID SCHEDULE, ATTACHMENT A, AND THE
ATTACHED REPRESENTATION AND CERTIFICATIONS INCLUDING 52.212-3,
OFFEROR REPRESENTATIONS AND CERTIFICATIONS – COMMERCIAL ITEMS
(NOV 2017). SEE SECTION L FOR ADDITIONAL REQUIREMENTS.”
Is there a separate ATTACHMENT A to be completed?
ANSWER: There is no ATTACHMENT A. The only attachment is ATTACHMENT 1 – Past
Performance Questionnaire.
SECTION C - DESCRIPTIONS AND SPECIFICATIONS
The following have been modified:
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. One trip to Vicksburg, MS will be required to develop these procedures and coordinate with ERDC personnel.
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. Travel to install equipment aboard commercial vessels. These visits will all be to large port cities in the Continental US;
previous visits were to Jacksonville, FL; Charleston, SC; and Los Angeles, CA. Two trips are anticipated. 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. To be determined.
11.0 SECURITY REQUIREMENTS.
Access and General Protection/Security Policy and Procedures. All contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation/facility access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any installation or facility change, the Government may require changes in contractor security matters or processes.
For contractors who do not require CAC, but require access to a DoD facility or installation. Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative, as NCIC and TSDB are available), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.
Suspicious Activity Reporting Training (e.g. iWATCH, CorpsWatch, or See something, Say Something). The contractor and all associated sub-contractors shall receive a brief/training (provided by the RA) on the local suspicious activity reporting 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 project manager, security representative or law enforcement entity. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 5 calendar days after the completion of the training.
Pre-screen candidates using E-Verify Program. The contractor must pre-screen Candidates using the E-verify Program (http://www.uscis.gov/e-verify) 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.
http://www.uscis.gov/e-verify
12.0 PERFORMANCE METRICS.
Statements Standards Incentive/Remedy
AIS transmit capability operationalization a)Incorporation in the LOMA system
b) Transmit capability procedures
c) Transmit monitoring capabilities d)System Monitoring
Monthly written progress reports on status of the task. Technology transfer will primarily be accomplished through incorporation of new capabilities into existing systems, such as LOMA. Appropriate documentation will be provided for configuration and use of the capabilities.
Technical reports and notes, journal articles, conference papers and presentations, and other publications will be prepared as appropriate to advertise and share the capabilities developed.
EXCEPTIONAL 100% are done within the allotted time with 25% exceed the allotted.
VERY GOOD- 90-99% are done within the allotted time.
SATISFACTORY 80-89% are done within the allotted time.
MARGINAL- 70-79% are done within the allotted time.
UNSATISFACTORY-Below 70%.
Contractor will provide all output files or the contact will be non-complaint and resulting action will require completing the missing input files at a no cost extension.
AIS Standard Development
Monthly written progress reports on status of the task. Technology transfer will primarily be accomplished through incorporation of new capabilities into existing systems, such as LOMA. Appropriate documentation will be provided for configuration and use of the capabilities.
Technical reports and notes, journal articles, conference papers and presentations, and other publications will be prepared as appropriate to advertise and share the capabilities developed.
EXCEPTIONAL 100% are done within the allotted time with 25% exceed the allotted.
VERY GOOD- 90-99% are done within the allotted time.
SATISFACTORY 80-89% are done within the allotted time.
MARGINAL- 70-79% are done within the allotted time.
UNSATISFACTORY-Below 70%.
Contractor will provide all output files or the contact will be non-complaint and resulting action will require completing the missing input files at a no cost extension.
AIS Equipment and Software Evaluation
Monthly written progress reports on status of the task. Technology transfer will primarily be accomplished through incorporation of new capabilities into existing systems, such as LOMA. Appropriate documentation will be provided for configuration and use of the capabilities.
Technical reports and notes, journal articles, conference papers and presentations, and other publications will be prepared as appropriate to advertise and share the capabilities developed.
EXCEPTIONAL 100% are done within the allotted time with 25% exceed the allotted.
VERY GOOD- 90-99% are done within the allotted time.
SATISFACTORY 80-89% are done within the allotted time.
MARGINAL- 70-79% are done within the allotted time.
UNSATISFACTORY-Below 70%.
Contractor will provide all output files or the contact will be non-complaint and resulting action will require completing the missing input files at a no cost extension.
Advanced ship-shore data communications via AIS
Monthly written progress reports on status of the task. Technology transfer will primarily be accomplished through incorporation of new capabilities into existing systems, such as LOMA. Appropriate documentation will be provided for configuration and use of the capabilities.
Technical reports and notes, journal articles, conference papers and presentations, and other publications will be prepared as appropriate to advertise and share the capabilities developed.
EXCEPTIONAL 100% are done within the allotted time with 25% exceed the allotted.
VERY GOOD- 90-99% are done within the allotted time.
SATISFACTORY 80-89% are done within the allotted time.
MARGINAL- 70-79% are done within the allotted time.
UNSATISFACTORY-Below 70%.
Contractor will provide all output files or the contact will be non-complaint and resulting action will require completing the missing input files at a no cost extension.
SECTION G - CONTRACT ADMINISTRATION DATA
The following have been deleted:
GENERAL INFORMATION
(End of Summary of Changes)
File details come from the government source that posted it. Updated .