pre-incident planning using web gis - esri · 2018-05-09 · pre-incident planning using web gis,...

Pre-Incident Planning (“PIP”)

Presentation Overview

• 1) Web GIS Terminology Review

• 2) Technical Details of PIP

• 3) The Start of PIP

• 4) PIP & General Maintenance

• Currently 1 year old

• Dashboards & Python

• 5) Future Improvements & ROI

• 6) General Q & A

2

1) General Web GIS Terminology

Front End

(Website or app)

Web GIS

(ArcGIS & Web Server)

Back-End

Handles requests from user and sends back

results (data)

Allows the user to make requests to data to answer questions

Where data lives “RDBMS”

3


Front-End

• Web App Builder • Mobile Apps• Template Apps• Web Maps

(The UI used for editing)

• ArcGIS Online• Portal• IIS / IIS Express*• Apache Tomcat*

* Self Hosting Applications (.NET / JAVA

= GIS usually)

• ArcGIS Online• ArcGIS Server• Geo-Server

Web Server

GIS Server

Back-End

• ArcGIS Online• SQL Server* • Oracle*• PostgreSQL*• Data Store* SDE / Enterprise GDB

4


Front-End

• Web App Builder • Template Apps• Web Maps

(The UI used for editing)

• ArcGIS Online• Allows communication

between Web requests (client) and GIS data (back-end)

• ArcGIS Online• Creates REST-end

Point Services from GIS data

• Permissions

Web Server

GIS Server

Back-End• ArcGIS Online

• Hosted Feature Layers• Cached Imagery

5

2) Technical Details of PIP

Web Server

GIS Server

Back-End

ArcGIS Server

ArcGIS Online

Enterprise GDB

Front-EndWeb App

Builder

6


Front-End

• Web App Builder • Smart Editor

Widget

• ArcGIS Online• Cached Tiles

• ArcGIS Server • Token Based Security

• Custom Users / Roles permissions (tracking)

• 10.4.1 ArcServer (REST)• Public Service

Web Server

GIS Server

Back-End

• SQL Server (10.4.1 E-GDB)• 8 Feature Classes

• Editor Templates• Easier to

manage• Less Data

• Editor Tracking7


Front-End

8

• Web App Builder • Smart Editor

Widget


9

• ArcGIS Server• 10.4.1 GIS Server ; 2012 R2 ; 10.4.1 E-GDB• 3 Feature Services

• Main Editing Service = Cached• All have same pooling configuration (# of Instances)• All have same security settings (user / roles)

• Token Based Authentication• All services public, but protected

GIS Server


10

Back-End

• SQL Server (10.4.1 E-GDB)

• 8 Feature Classes• Editor Templates

Easier to manageLess Data

• Editor Tracking Enabled

• Archiving Enabled

• Versioned


11

• Python• Email Generation when a broken hydrant is collected using X, Y and closest parcel.• Automated Map Changes when a commercial property is inspected• Email Generation for Bad Addresses and Suspected Property Violations

Automation

3) The Start of PIP

1. Replaced Paper Process

2. Makes content accessible

3. Less long-term maintenance

4. Standards could be followed!

12

3) The Start of PIP

1. Replaced Paper Process• Old Process involved

hand drawn building footprints on paper

• Paper had to be indexed and reproduced so that it could be accessible in the field

13

3) The Start of PIP

2. Makes content accessible

• Digital content = accessible on any device that is connected to the internet.

• Centralized repository

• Standardized view

14

3) The Start of PIP

3. Less long-term maintenance

• Content doesn’t take up drawer space.

• It can be managed and scaled as the amount of content increases

• It can be backed up and collected in a manner that is “trackable”

15

3) The Start of PIP

4. Standards could be followed!

• Standard values for fields could be enforced and “required” fields could be implemented

• Standard symbology

• Standard way to collect information and retrieve it when needed.

16

18

4) Improving PIP & General Maintenance

1. Additional Functionality

• Collect New Things

2. Automated Tasks

• Auto-Emails

• Auto Map View Changes

3. Performance!

4. Reporting (Dashboards)

19


1. Additional Functionality

• Collect Vacant Land

• Collect Broken Hydrants

• Collect Ancillary Structures

20


2. Automated Tasks

•Auto-update Map view

•Automated Emails

• Broken Hydrants

• Property Issues

• Addressing Issues

21


3. Performance!

•Cached Services

•Custom Zoom Scales

•Pooling / Service Configuration

22


4. Dashboards•Accessible

Reporting

•Monitor Progress

•Accountability

23

5) Future Improvements & ROI

1. Future Improvements•Design PIP to be taken offline

•Permissions Management

2. Return on Investment (ROI)

•Lake County Fire Rescue Feedback

24

5) Future Improvements & ROI

Future Improvements•Design PIP to be taken offline

•Permissions Management

•Need to integrate with Active Directory if possible

•Cache at all zoom scales

• Integrate with Active 911

•Ready made PDFs of all PIPs

27

5) Future Improvements & ROI1) How many times has PIP data been utilized in a call?

PIP’s best moment involved a Hazmat call involving anhydrous ammonia. We used it in the field to respond to the call and know what we were walking into

2) How does management feel about PIP?Love it

3) What is the general feedback you’ve received from your crews in the field? Generally positive / negative?Positive- user friendly and is a practical pre-plan, collecting what is needed for a proper size up and what

tactics to deploy

4) Has PIP improved the Pre-Incident Information Process?Absolutely- more accurate real time data that can be continually updated. Once the initial is complete it is

maintenance and checking for changes. Crews do not have to start all over.

5) What would be the biggest return on investment, from a Fire Rescue perspective, of PIP?Identifies wrong addresses, discovered approximately 250K in improperly assessed parcels. Shows

progress and has measures in place to get as close as possible to 100% ISO compliance.

28

6) Questions / Answers?

1. Database / Service Designs

2. ArcGIS Online

3. Application Creation

4. REST services and AGO

5. Permissions

6. Training / Supporting an AGO Application

Pre-Incident Planning (“PIP”)

pre-incident planning using web gis - esri · 2018-05-09 · pre-incident planning using web gis,...

Documents