A09_W912DR-17-T-0079_0002.pdf

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

The purpose of this amendment is to respond to the Requests For Information (RFI). All other terms and conditions remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

1 14

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 14-Jul-2017

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 W912DR-17-T-0079

X 9B. DATED (SEE ITEM 11)

21-Jun-2017

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

14-Jul-2017

CODE

USACE, BALTIMORE DISTRICT

10 S. HOWARD ST

ROOM 7000

BALTIMORE MD 21201

W912DR 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W912DR-17-T-0079

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been added by full text:

REQUESTS FOR INFORMATION

Next Generation Hurricane Decision Support Platform

Q1. In accordance with paragraph IV, a demonstration of the HVX prototype user interface and features is requested.

A1. A webinar was held 06 July 2017 at 2PM EST. It was captured and can be viewed here:

https://mit.webex.com/mit/lsr.php?RCID=76abcac642a74629ab48fc4aa09ea5fc

Q2. Request HVX prototype documentation and source code A2. All technical information that can be provided is in the above webinar or the below supllemental files.

Q3. Request two week extension to analyze demo and documentation A3. No extention of the solicitation period will be provided at this time.

Q4. Confirm an unlimited number of past performances can be submitted with no page length restrictions.

A4. Past performance must be in the format in the instruction to offerors and limited to 5.

Q5. Confirm there is an unlimited page count for tech approach.

Q5. The technical approch is now limted to 25 pages.

Q6. RFP has numerous deliverables e.g., software documentation, small business subcontracting plan, which are not addressed in deliverable table provided in paragraph XII. To facilitate accurate cost estimate request government provide a complete list of deliverables for this contract, including specific software documentation desired?

A6. All pre-award requirmenst are listed in the instructions to offorers. All post award requierments and deliverables are listed in the SOW document. Please refer to those documents.

Q7. What is governments budget and/or estimated level of effort for this work?

A7. The government does not divulge the estimates or budgets in the solicitation phase. The awarded price will be made public.

Q8. Can contractors propose labor categories not included in the provided price schedules?

A8. Yes, as long as they are industry standard labor categories.

Q9. Task 1b states contractor shall stand-up software on new set hardware in contractors environment. Task 1c implies testing at scale will be executed with software stood up on Amazon Web Services (AWS). Is the intent for users to access HVX software from the contractors data center or Amazon Web Services?

A9. The intent was to allow the contractor flexibility in their response – It is assumed most vendors will choose AWS but they might have compelling reasons to maintain their own system. A vendor could use AWS, which would allow scaling OR they could decide it is best to maintain control over the whole system (or even a mix of the two).

The decision is up the venor and accouted for in the proposal

Q10. Is contractor responsible for cost of hosting HVX software?

A10. Yes

Q11. Page 22 states "Utilization of open-source third party applications for common GUI and algorithmic processes (Ext.js, D3.js, etc.). A sample listing is given at the end of this document." Can you please provide that referenced list of technologies?

A11. Please see the file HVX-System Mainfest.xlsx provided with this amendment.

Q12. The price schedule contains space for entries in three categories: Labor, Materials, and Travel. Are server and cloud services costs intended to be fit into the Materials category or be built into overhead of Labor?

A12. Add it to the category you feel most appropiate.

Q13. What are the specifications of the machines currently being used to run all of the servers?

A13.

Role Name vCPU vRAM Disk (GB) Disk Used (GB)

Web/RabbitMQ NHP-Sandbox-Web1 4 16 100 70

Database NHP-Sandbox-DB1 4 16 200 170

Data NHP-Sandbox-Data1 4 16 40 30

Mapserver NHP-Sandbox-Mapserver1 4 16 40 30

OpenAM NICS6-Identity1 2 8 40 30

RtePM rtepm.nhp 4 16 100 58

Q14. Does the software require a FedRamp certification?

A14. No, the location where HVX is hosted is required to have the FedRAMP certification, not the actual software code itself. There is a listing of hosting services that already have the certification located at https://marketplace.fedramp.gov/#/products?status=Compliant&sort=productName. Any vendor can of course pursue certification as well.

Q15. The RFP states "The contractor will meet and must submit proof of compliance with FedRAMP requirements regarding use of cloud based services." Does this mean FedRAMP certification of the infrastructure (e.g., Amazon GovCloud) or will the vendor be required to go through the FedRAMP process for the HVX product/service itself?

A15. There is a listing of infrastructure hosting services that already have the certification located at https://marketplace.fedramp.gov/#/products?status=Compliant&sort=productName. Any vendor can of course pursue certification as well

Q16. What are the server specs of the HVX prototype which successfully supported 50 concurrent users? How many more concurrent users does the developer believe could be supported within this lone instance? Please provide application resource usage data (CPU, memory, size of database, etc) to assist in the assessment of scaling needs. A TCP dump of a standard login session would also be useful in this regard.

A16. – Please see the file HVX_ServerUsage.zip provided with this amendment

Q17. Please provide a list of all the dynamic inputs required for HVX (forecast and observational data) with details of which ones a) are externally sourced and used as-is by the application versus b) require parsing, aggregating, and/or hosting by the contractor. Have parsers been built to handle text-based products such as forecast advisories from NHC, CPHC, JTWC, and WPC? Please provide a list of parsers.

A17. – Please see the file DataingestDetails_hvx.xlsx provided with this amendment

The following have been modified:

SCOPE OF WORK (SOW)

Scope of Work (SOW) Next Generation Web-Based Hurricane Evacuation Decision Support Platform

April 2017

I. PURPOSE:

The next generation Hurricane Evacuation Decision Support Platform, currently referred to as the Hurrevac Extended (HVX) prototype, is a restricted-use web-based software program funded by the Department of Homeland Security Science and Directorate, the Federal Emergency Management Agency (FEMA) and the United States Army Corps of Engineers (USACE) for government emergency managers to plan, train and execute tropical cyclone decisions and evacuations. The software, access to which is available free of charge to government emergency managers, supports the ability to view and interpret tropical cyclone observations and forecasts, track hurricanes, support evacuation decision making, and provides data and information to support hurricane emergency management planning, training, and decision making. This real-time data analysis tool allows state and local emergency management officials to make prudent and informed decisions based on information developed during the National Hurricane Program (NHP) Hurricane Evacuation Studies (HES) process and real-time forecast data distributed by the National Weather Service (NWS) National Hurricane Center (NHC), the Central Pacific Hurricane Center (CPHC) and the Joint Typhoon Warning Center (JTWC).

HVX was developed starting in 2013 as an improvement and expansion of the previous decision support tool, HURREVAC, which is owned by the Federal Government through the USACE and FEMA and operated/maintained via a private contractor. Massachusetts Institute of Technology, Lincoln Labs (MIT-LL) was the prototype developer. The NHP technological gap analysis (2013) formed the basis of the technological upgrades and the expansion included in the new web based version, to cover not only the real-time evacuation decision process but also embedding both the HES process itself and the training on the tools and decision-making skills.

At the core of the planning are the detailed HES developed for state, local and tribal communities. The purpose of the HES is to assist government emergency managers in understanding risk and vulnerability to hurricanes, defining potential evacuation zones, and determining the length of time it will take to evacuate the public in various scenarios (called the “clearance time”). The clearance time is combined with the forecasted movement, growth, and potential severity of hazards associated with an approaching storm to help determine when an emergency manager may need to start an evacuation in order to complete it prior to the arrival of hazardous conditions.

The legacy HURREVAC system has over 18,000 registered government users at all levels and serves as the primary evacuation decision support tool for Emergency Managers threatened by tropical systems. It is expected that next generation web-based platform, because it will be web-accessible and covers a wider breadth of emergency manager services, will exceed the current user levels.

II. HVX Platform Overview:

The goal of the NHP Technology Modernization effort with respect to the integrated HVX prototype platform is to create a flexible system with new and updated technology that enables Emergency Managers (EMs) to make timely and accurate evacuation related decisions. The new system will be applicable in a variety of contexts, including evacuation studies, planning, training, and operational response and evacuation decision support. The ability to utilize HVX as a multi-purpose tool allows users to become more familiar with the interface, reducing the need for training on multiple tools and processes. Here are some of the key architecture and programmatic features of the HVX prototype:

Utilization of a Web-based thin client architecture built with open-source software components;

increasing ease of use, data collaboration and deployment and allowing for operation on mobile devices.

Offline capabilities that enable the EM to utilize some decision support capabilities when the system does not have connectivity to the internet. Features that will be available include:

o The last downloaded set of hurricane tracks and forecasts (and related products such as wind rings, wind swath, watches/warnings, etc.)

o The ability to display storm surge Maximum of Maximums (MOM)/ Maximum Envelope of Water (MEOW) risk mapping products/data o The ability to see the most recent downloaded data for their base location that allows the EM to see the potential storm surge (if produced by NHC), radar, satellite, flood outlook, rain/river/tide gages, etc.

Creation of open-source geospatial data sharing services to maximize the available data sources and minimize the overhead of integrating new data.

Utilization of open-source third party applications for common GUI and algorithmic processes (Ext.js, D3.js, etc.). A sample listing is given at the end of this document.

Institution of a series of navigation aids that assist the user in seamlessly accessing, analyzing and viewing data temporally and spatially.

Incorporation of decision analytics to enable users to better assess impacts and uncertainty.

Creation of a storm surge explorer for viewing both planning and operational storm surge flood risk data, including the ability to view storm surge risk areas for applicable combinations of Maximum Envelopes of Water, which allows for improved understanding of storm surge risk from an approaching hurricane prior to the availability of probabilistic storm surge data and products.

Integration with a modular HES process that will allow not only integration of the HES components, but also the ability to utilize sub-modules of HES within the decision-making and training processes.

Integration of serious gaming capabilities into the HVX platform, including automated simulation capabilities, decision-focused training modules and feedback mechanisms for improved decision-making.

Creation of a simplified storm track simulation and advisory generator to enable EMs to create new training and scenarios on their desktop.

A repository of HES Reports and other NHP Documents and a file sharing system to enable collaboration between users.

III. TASKS:

In executing these tasks, the Contractor shall not depart from, nor perform beyond, the tasks described in this scope of work and its referenced criteria without the written approval of the Contracting Officer’s Representative (COR).

TASK DESCRIPTIONS:

TASK 1: HVX Prototype and Transition (To be completed 12 months after contract award):

a. Project Management The Contractor is responsible for providing the project management oversight, up to and including contractual deliverables and financial controls. The Contractor’s Project Manager is one of the primary points of contact with USACE. The Contractor’s Project Manager shall establish and maintain close coordination with the USACE points of contact for this SOW.

Coordination may be in the form of in-person meetings, written correspondence, webinars, or telephone calls. Coordination will include a monthly In Progress Review (IPR) teleconference meeting to discuss the status of all tasks. A kickoff meeting will be held between the USACE and the Contractor within 2 weeks of the Date of Award. The Contractor shall maintain a record of all project coordination actions and shall provide copies of this record to the USACE POCs, upon request.

b. Transferring HVX prototype system to vendor’s servers The Contractor shall obtain the HVX code-base provided by FEMA and stand-up that software on a new set of hardware in the Contractor’s environment. The government reserves the right to inspect the contractor’s data center and workspace. The contractor shall verify that the embedded unit tests pass and that external Selenium-based test procedures also pass. Once all tests pass, this verifies that the USACE HVX prototype functions as-is.

c. Testing HVX At Scale

The HVX prototype operated in an environment of up to 50 concurrent users with limited lag or database issues. However, as noted in the introduction the total user base is expected to exceed 18,000 users. The Contractor shall ensure that the operational HVX platform is able to handle a potential user base in excess of 25,000 and a concurrent user experience of at least 5,000 users.

While the HVX prototype did not have the full user base, the software has been integrated with Amazon Web Services, which should allow the system to be scaled readily. The Federal Risk and Authorization Management Program, or FedRAMP, is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. The contractor will meet and must submit proof of compliance with FedRAMP requirements regarding use of cloud based services. More information is available at: https://www.fedramp.gov/participate/csps/. During the initial transition year, the contractor will be required to add beta users (names to be provided by

USACE) who will test the system and functionality, and provide feedback for the contractor and USACE to address. The contractor will also be required to provide technical user support to these beta testers. Nine months after the award of the base tasks, the contractor will be required to have an operational HVX platform that can support 5,000 concurrent users.

d. Continual Verification of Input Data Sources HVX utilizes a wide variety of input data streams. The nature of real-time streaming data and the rapidly changing dissemination techniques, formats and accessibility is such that the sources of specific data may need to be modified over time. In this initial transfer phase, the Contractor will be responsible for verifying that any web-based input data is still providing the expected service and that the data is injecting properly into HVX. If services or products have changed or are unavailable the Contractor will be required to find alternatives.

e. System Control, Monitoring & Recovery The HVX prototype is outfitted with limited capabilities to monitor and recover instantaneously from server, algorithmic or other unexpected errors. The contractor shall build a monitoring system that allows USACE and the O&M operator to detect, alert, and recover from unexpected failures. This includes monitoring of all data feeds to ensure that the injected data is being received and processed in a timely manner. The system requirement for uptime during hurricane season is 99% with a recovery buffer of 5 minutes.

f. OpenAM for user authentication OpenAM is an open source access management, entitlements and federation server platform. It is sponsored by ForgeRock (https://forgerock.org/openam/ ). HVX has a current set of credentials for existing users, including levels of authorization to allow restricted access to some portions of HVX. The Contractor will be provided the current database of users that are managed in OpenAM and be expected to transition the current user database into their HVX operational system. While the Contractor is strongly recommended to continue OpenAM, it may propose an alternative that USACE would have to evaluate and approve.

g. Terms and Conditions The contractor will be responsible for developing terms and conditions that users will need to accept to access HVX. These terms and conditions should include, but are not limited to :user rights and responsibilities, proper or expected usage, potential misuse, accountability for online actions, behavior, and conduct, and a Disclaimer/Limitation of Liability clarifying the site's legal liability for damages incurred by users. Terms and conditions will need to be approved by USACE and FEMA counsel.

h. OpenStreetMaps server/configuration OpenStreetMaps (OSM) is an open-source effort that builds editable maps and an API to access map tiles for display (https://www.openstreetmap.org/about ). The HVX prototype utilized the OSM server as a way to provide highly detailed and modern maps as a base layer for the HVX map.

However, the operational HVX platform will require a dedicated server in order to allow HVX to have control over the reliability, stability and customization of the maps provided. The Contractor shall stand-up an OSM dedicated server for HVX and configure the map options to meet the requirements specified by USACE/FEMA.

i. Readiness for Transition to Operational Status

By June 1, 2018, the contractor must demonstrate that the HVX prototype has been successfully transitioned from MIT-LL (the developer) to the contractor, that Task 1 has been successfully completed, and that the system is ready to be fully operational and made available to the full user base of 18,000 users. This task includes a requirement that the contractor will develop a plan, approved by USACE, to efficiently provide access to registered HURREVAC users who do already have access through the beta system. MIT-LL will be available to provide technical guidance and support to assist the contractor with the execution of tasks and will assist the USACE in the evaluation of whether Task 1 can be considered complete. The contractor must ensure full functionality within the following internet browsers: Microsoft Internet Explorer, Microsoft Edge, Apple Safari, Google Chrome, and Mozilla Firefox.

TASK 2 (Optional): Integration planning for new National Hurricane Center, FEMA, and other hurricane decision support products The NHC is the primary provider of archived, current and forecast products that support hurricane evacuation decision-making and most of the weather products utilized by NHP and HVX. The NHC is steadily analyzing, piloting, and transitioning new products and updates to existing products relative to hurricanes. The Contractor will meet with NHC and others, as directed by USACE to analyze potential new products and provide recommendations on how and whether they might be transitioned to the system and the user interface. USACE reserves the right to accept/request algorithm development from other sources to provide updates to HVX components or product integration. Known products that are already in the development with NHC, but will not have been integrated into the HVX prototype, but will be required to be integrated once available, are:

Storm surge watch and warning graphics High resolution storm surge risk area grids for MOMs and MEOWs, to be used in the surge viewer and the MEOW blender.

Wind-timing graphic

The Contractor shall be required to integrate these products into in preparation for real-time operations (provided that the products become available from NHC).

TASK 3 (Option Year 1): Annual Systems Operation and Maintenance Base Period

a. Continual Verification of Input Data Sources

The web based platform utilizes a wide variety of input data streams. The nature of real-time streaming data and the often rapidly changing dissemination techniques, formats and accessibility is such that the sources of specific data may need to be modified over time. Each year and during operations, the Contractor will be responsible for verifying that any web-based input data is still providing the expected service and that the data is injecting properly. The Federal Risk and Authorization Management Program, or FedRAMP, is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. The contractor will meet and must submit proof of compliance with FedRAMP requirements regarding use of cloud based services.

More information is available at: https://www.fedramp.gov/participate/csps/

b. System Control, Monitoring, Reporting & Recovery The Contractor shall monitor system performance through the contractor-built monitoring system and be responsible for real-time recovery of the system to normal operations. The system requirement for uptime during hurricane season is 99% with a recovery buffer of five minutes.

The system will also be required to be up during training courses outside of hurricane season, the dates and times of which will be provided to the contractor. The contractor must ensure full functionality within the following internet browsers, for the most recently released version and versions released within the last three years: Microsoft Internet Explorer, Microsoft Edge, Apple Safari, Google Chrome, and Mozilla Firefox.

c. Updates to Database Files Prior to the start of hurricane season, the contractor shall be required to update parameters and files that are critical to HVX operations. A table of the required updates is shown below:

Description Producing agency Location within HVX Hurricane tracking error values NHC, CPHC, JTWC

<tbp>

Hurricane Evacuation Study Update – PDF document

USACE <tbp> (HES Library)

Hurricane Evacuation Study Update – Clearance time tables

USACE (must be extracted from the PDF document)

<tbp>

Hurricane Evacuation Study – Evacuation zone updates

USACE (GIS files) <tbp>

Analysis and recommendations for integration of NHC products

NHC NA

User database for OpenAM credentialing

MIT-LL initially and then maintenance

<tbp>

User database of configuration settings

MIT-LL initially and then maintenance

<tbp>

d. Operations and Maintenance of user authentication

The Contractor will be responsible for ensuring that new users are pre-approved by USACE for access to the system and at what level of authorization the user will be given. OpenAM is currently HVX’s credentialing service. All users will be required to accept terms and conditions developed by the contractor and approved by the federal government to access HVX.

e. Real-time monitoring operations

During the hurricane/typhoon season in the northern hemisphere and the cyclone season in southern hemisphere, the Contractor is responsible for ensuring continuous operation of HVX input and output products, including training, simulation, gaming, and HES components. When errors directly related to tropical cyclone impacts (forecast tack, intensity, storm history, discussions, wind probability fields, etc.) occur, the Contractor must provide alternatives and/or capabilities within 5 hours during an active threat, and 24 hours when there is not an active threat.

Hurricane/Typhoon Seasons requiring heightened response:

The NHC in Miami is responsible for Atlantic, Caribbean and Gulf of Mexico and the Eastern Pacific east of 140 degrees west.

o Hurricane season in the Atlantic and Central Pacific (140W to 180W) runs from June 1st to November 30th.

o Hurricane season in the Eastern Pacific (E of 140W) runs from May 15 to Nov 30th.

The CPHC in Honolulu is responsible for Pacific from 140 W to 180 W.

o Typhoon season in the Western Pacific is essentially year round but usually active only from March through December.

The JTWC is responsible for Northwest Pacific west of 180 W (dateline), South Pacific and Indian Ocean.

o Cyclone season in the South Pacific is generally from October through March (reverse of North hemisphere).

Products under the “Conditions” tab in HVX are generally less critical to real-time operations but they are used throughout the year and should be restored as soon as practically possible.

f. User Technical Support During active tropical systems that are a threat to the United States and its Territories (within 120 hours of a potential impact), the contractor will be required to staff a 24 hour technical support system that will respond to technical assistance requests submitted to the contractor by users via email, phone, or through the system itself within one hour.

When no active tropical systems exist that are a threat to the United States and its Territories, the contractor will provide technical support during normal business hours to resolve to support requests submitted by users via email, phone, or through the system itself within 48 hours. This includes technical support to ongoing exercises and training as needed.

Any technical issues raised by users, the USACE, or discovered by the contractor that will require changes to the system should be enabled via the web immediately as they are completed as to appear seamless to the end user. If the incident isn’t resolved in the specified amount of time the contractor must submit a plan for how to resolve the request, an explanation for why the incident is not resolved, and an expected timeline for resolution.

g. Production of HVX Operations & Maintenance Manual The O&M Vendor shall provide an electronic PDF document detailing the operations and maintenance procedures that have been established for the operational hurricane decision support system and updated annually by the end of the calendar year. This document will be property of the federal government and should be based off the general content of the legacy HURREVAC operations and maintenance manual and will include, but is not limited to the following detailed sub-sections:

a) Overview of the program and role of this platform in evacuation decision support

b) Key Operational contacts, web sites relative to hurricane forecasts and advisories

c) Description of operational support for users

d) Details of the data ingest types and sources

e) User configuration settings and management

TASK 4 (Option Year 2): Annual Systems Operation and Maintenance

The same requirements as outlined in Task 3.

TASK 5 (Option Year 3): Annual Systems Operation and Maintenance

The same requirements as outlined in Task 3.

TASK 6 (Option Year 4): Annual Systems Operation and Maintenance

The same requirements as outlined in Task 3.

IV. ASSUMPTIONS:

To support development of proposals, potential bidders may request technical information on the HVX code and architecture, which would be responded to as appropriate within contracting rules, and also request a one-hour demonstration of the HVX prototype user interface and features.

V. GOVERNMENT OWNERSHIP

The HVX software as provided to and as amended by the O&M vendor is owned by the FEMA, except for those portions of the software that have explicit open-source or other copyrights. Any and all amendments made by the contractor to create the operational HVX platform are also owned by the FEMA. The USACE and FEMA reserve the right to ask for and receive a complete download of the HVX software and documentation and to transfer and or utilize said download as they see fit at any time.

All data, reports, and materials related to this project are the property of the U.S. Government and shall not be released by the Contractor or sub-consultants without prior written approval.

VI. GOVERNMENT FURNISHED ITEMS

The government will provide, at a minimum, the following items within 2 weeks of award:

The HVX prototype software, documentation and supporting scripts and tools for monitoring and verification.

The 2013 NHP Technology Gap Analysis Report Initial databases of GIS shapefiles for hurricane evacuation zones, storm surge basins, counties, states, countries, FEMA regions, and forecast regions.

Initial database of MOMs and MEOWs for storm surge.

PDFs of HES documents for each locality to be utilized as part of the HVX Library for disseminating Hurricane Evacuation Studies Database of current database of OpenAM authorized users A listing of all open-source, third-party applications used within HVX and/or used for testing, authentication or monitoring (there are no proprietary third-party applications utilized within

HVX)

Access to the HVX prototype developers for questions and support Operations and Maintenance Manual for the legacy HURREVAC system.

The list of registered HURREVAC users.

DIAGRAM of Input Data Sources.

VII. SECURITY

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.

VIII. SUBMITTAL AND DELIVERABLES

1. The Contractor shall document all coordination and consultation with Federal, State or other agencies either through correspondence or records of conversation. Coordination of these agencies shall be documented in the report submittals.

2. The Contractors’ names and/or company logos will not appear in any of the products without approval from the USACE.

3. Electronic transmission of these documents, review comments, and meeting minutes, to all parties will be accomplished wherever possible to expedite the progress of the project.

4. The Contractor shall be responsible for the professional and technical accuracy of all work or services rendered. The products submitted shall fully meet the requirements of the delivery order. Submittals shall be reviewed for technical accuracy.

5. Data gathered during the project shall not be used or distributed by the Contractor without special written government permission. The Study Manager shall review and approve all documents before they are released to any party outside the USACE.

6. The contractor is required to execute all aspects of the scope within the United States.

7. During the period of performance of the contract, the contactor shall be transparent in design and practice; the system will be capable to be seamlessly handed over to a successor contractor skilled in the art of computer programming, maintenance, and upgrading; and that ensure the system is contemporaneously archived to ensure stability and the ability to survive outages. This further requires the offeror to present a plan to meet the evaluation criterion.

IX. COORDINATION AND WORKMANSHIP

The Contractor shall maintain close coordination with the study manager, via telephone, meetings, E-mail and other correspondence during the order period. All contacts and requests for information from State and Local governments will be documented. The Contractor will furnish the USACE with copies of all pertinent correspondence.

X. PERIOD OF PERFORMANCE

Base Period – 12 months from date of award 04 option periods of 12 months each.

XI. PROJECT SCHEDULE

The contractor will prepare a draft project schedule for discussion at the kick-off meeting.

The contractor provide a final project schedule for USACE approval within 3 weeks after kick-off meeting.

Work on this contract shall be started immediately upon receipt of the written notice from the Contracting Officer Representative (COR), Michael Schuster to proceed.

XII. PAYMENTS

Mandatory monthly invoices shall be submitted to Ms. Ellen Maguire, Planning Division, Baltimore District, 10 South Howard Street Room 11430, Baltimore, Maryland 21201 on the 15th of the month for review and certification. Monthly invoices are mandatory; however, the total cumulative amount shall not exceed the percentage or stage of work that has been completed.

A monthly invoice should be sent showing zero amount due when no work has been completed.

Each invoice shall include the contract number, amount of the contract (including any mods), percent complete, value of percent complete, amount paid to date, and remit address. Each invoice will be audited by USACE staff to ensure that sufficient progress has been made to support payment. A completed Release of Claims form (attached) is to be attached to the final invoice.

The Contractor shall include a progress report along with the invoice as justification for the amount of payment requested.

Each progress report shall include:

* A brief description of activities that occurred over the payment estimate time period;

* A brief description of upcoming activities that are expected to occur in the current month;

* Estimated percentage complete

The original invoice, with no attachments, shall be submitted to Ms. Ellen Maguire, Planning Division, Baltimore District, Attn: CENAB-PL, U.S. Army Corps of Engineers, 10 South Howard Street, Baltimore, Maryland 21201 and by email to ellen.d.maguire@usace.army.mil, and to Carla Quinn, Baltimore District, Planning Division at carla.m.quinn@usace.army.mil.

The Contractor shall not depart from, nor perform beyond, this scope of work and its referenced criteria without the written approval of the Contracting Officer’s Representative (COR).

Deliverable Due Date Kick off Meeting 2 weeks from date of award Identify E-verify candidates 3 business days from date of award Draft project schedule 3 weeks from date of award Platform fully operational 12 Months from date of award

(End of Summary of Changes)