[gpl_list] Response Requested: gauging interest in Velocity product

[STOELB Daniel * OEM]

Good morning again everyone,

This is a gentle reminder about the request below. If you are interested in the Velocity product, please let me know by the end of this week. See original information below for details. Thanks!


[Logo  Description automatically generated]<https://www.oregon.gov/oem>
Daniel Stoelb (he/him) | GIS Program Coordinator
Information Technology Section
Oregon Department of Emergency Management
Cell 971-719-0917 (talk/text)
daniel.stoelb at oem.oregon.gov<mailto:daniel.stoelb at oem.oregon.gov>
[cid:image008.png at 01DAED4F.DD4A6310]<https://www.facebook.com/OregonOEM>[Icon  Description automatically generated]<https://twitter.com/oregonoem>[Image result for youtube icons]<https://www.youtube.com/c/OregonOEM>

OEM GIS Hub: https://oregon-oem-geo.hub.arcgis.com<https://oregon-oem-geo.hub.arcgis.com/>

From: STOELB Daniel * OEM
Sent: Friday, August 2, 2024 7:32 AM
To: gpl_list at omls.oregon.gov
Cc: SMITH Rachel L * DAS <Rachel.L.SMITH at das.oregon.gov>; MATHER David * DAS <David.MATHER at das.oregon.gov>
Subject: Response Requested: gauging interest in Velocity product
Importance: High

Good morning GIS Program Leaders,

As many of you know, we have been activated for the wildfires for the last three weeks. As a part of this activation, we worked through the Esri Disaster Response Program and received a temporary license for the ArcGIS Velocity product. This gives us the ability to have a real-time feed of data converted into a hosted feature service on ArcGIS Online. As many of our solutions are revolving around ArcGIS Online, this was a critical component for us to utilize, without requiring us to do anything on our own local infrastructure. Specifically, we are taking a feed of data from a web feature service (OGIC WFS type) from a new software implementation for evacuations called Genasys and mapping fields and data to our statewide evacuation service that we've had up and running since 2017. This allows our partners to still access the same end feed of data that they've been pointing to for the last 7 years, but now it is automatically updated for counties that have implemented the Genasys product, while still offering an opportunity for our partners to edit the original service the traditional way.

With that all said, we are looking to possibly partner with other agencies to see about getting a cost share set up for this product moving forward. We certainly have a need and a desire to utilize this moving forward, but we would like to see if there's the possibility of partnering with other agencies to get a cost share set up and reduce the cost for the licensing for the state implementation of ArcGIS Online.

As it stands, to implement this solution, the recommendation is to aim for the highest tier solution, which would be the dedicated product (screenshot below):
[cid:image011.png at 01DAED4F.DD4A6310]

The cost for us to implement this product is $90k annually. You can find out more information about Velocity here: https://www.esri.com/en-us/arcgis/products/arcgis-velocity/overview.

If you are interested and would have funding available for this product moving forward, please reach out to both me and Rachel Smith. We'd like to see if anyone is interested in the next two weeks if at all possible. I'm also happy to walk through anyone that is interested to see what things are looking like for us currently with our data feed setup.

[Logo  Description automatically generated]<https://www.oregon.gov/oem>
Daniel Stoelb (he/him) | GIS Program Coordinator
Information Technology Section
Oregon Department of Emergency Management
Cell 971-719-0917 (talk/text)
daniel.stoelb at oem.oregon.gov<mailto:daniel.stoelb at oem.oregon.gov>
[cid:image008.png at 01DAED4F.DD4A6310]<https://www.facebook.com/OregonOEM>[Icon  Description automatically generated]<https://twitter.com/oregonoem>[Image result for youtube icons]<https://www.youtube.com/c/OregonOEM>

OEM GIS Hub: https://oregon-oem-geo.hub.arcgis.com<https://oregon-oem-geo.hub.arcgis.com/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omls.oregon.gov/pipermail/gpl_list/attachments/20240813/f2210144/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 37333 bytes
Desc: image002.png
URL: <https://omls.oregon.gov/pipermail/gpl_list/attachments/20240813/f2210144/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 28219 bytes
Desc: image007.png
URL: <https://omls.oregon.gov/pipermail/gpl_list/attachments/20240813/f2210144/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 268 bytes
Desc: image008.png
URL: <https://omls.oregon.gov/pipermail/gpl_list/attachments/20240813/f2210144/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 957 bytes
Desc: image009.png
URL: <https://omls.oregon.gov/pipermail/gpl_list/attachments/20240813/f2210144/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 3259 bytes
Desc: image010.png
URL: <https://omls.oregon.gov/pipermail/gpl_list/attachments/20240813/f2210144/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 138514 bytes
Desc: image011.png
URL: <https://omls.oregon.gov/pipermail/gpl_list/attachments/20240813/f2210144/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 28227 bytes
Desc: image012.png
URL: <https://omls.oregon.gov/pipermail/gpl_list/attachments/20240813/f2210144/attachment-0013.png>