Pre-Incident Planning ( PIP )

Transcription

1 Pre-Incident Planning ( PIP )

2 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

3 1) General Web GIS Terminology Front End (Website or app) Web GIS (ArcGIS & Web Server) Back-End Allows the user to make requests to data to answer questions Handles requests from user and sends back results (data) Where data lives RDBMS 3

4 1) General Web GIS Terminology Front-End Web App Builder Mobile Apps Template Apps Web Maps (The UI used for editing) GIS Server ArcGIS Online ArcGIS Server Geo-Server Web Server ArcGIS Online Portal IIS / IIS Express* Apache Tomcat* * Self Hosting Applications (.NET / JAVA = GIS usually) Back-End ArcGIS Online SQL Server* Oracle* PostgreSQL* Data Store * SDE / Enterprise GDB 4

5 1) General Web GIS Terminology Front-End Web App Builder Template Apps Web Maps (The UI used for editing) GIS Server ArcGIS Online Creates REST-end Point Services from GIS data Permissions Web Server ArcGIS Online Allows communication between Web requests (client) and GIS data (back-end) Back-End ArcGIS Online Hosted Feature Layers Cached Imagery 5

6 2) Technical Details of PIP Front-End Web Server GIS Server Back-End Web App Builder ArcGIS Online ArcGIS Server Enterprise GDB 6

7 2) Technical Details of PIP Front-End Web App Builder Smart Editor Widget GIS Server ArcGIS Server Token Based Security Custom Users / Roles permissions (tracking) ArcServer (REST) Public Service Web Server ArcGIS Online Cached Tiles Back-End SQL Server ( E-GDB) 8 Feature Classes Editor Templates Easier to manage Less Data Editor Tracking 7

8 2) Technical Details of PIP Front-End Web App Builder Smart Editor Widget 8

9 2) Technical Details of PIP GIS Server ArcGIS Server GIS Server ; 2012 R2 ; 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 9

10 2) Technical Details of PIP Back-End SQL Server ( E-GDB) 8 Feature Classes Editor Templates Easier to manage Less Data Editor Tracking Enabled Archiving Enabled Versioned 10

11 2) Technical Details of PIP Python Generation when a broken hydrant is collected using X, Y and closest parcel. Automated Map Changes when a commercial property is inspected Generation for Bad Addresses and Suspected Property Violations Automation 11

12 3) The Start of PIP 1. Replaced Paper Process 2. Makes content accessible 3. Less long-term maintenance 4. Standards could be followed! 12

13 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

14 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

15 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

16 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

17 17

18 4) Improving PIP & General Maintenance 1. Additional Functionality Collect New Things 2. Automated Tasks Auto- s Auto Map View Changes 3. Performance! 4. Reporting (Dashboards) 18

19 4) Improving PIP & General Maintenance 1. Additional Functionality Collect Vacant Land Collect Broken Hydrants Collect Ancillary Structures 19

20 4) Improving PIP & General Maintenance 2. Automated Tasks Auto-update Map view Automated s Broken Hydrants Property Issues Addressing Issues 20

21 4) Improving PIP & General Maintenance 3. Performance! Cached Services Custom Zoom Scales Pooling / Service Configuration 21

22 4) Improving PIP & General Maintenance 4. Dashboards Accessible Reporting Monitor Progress Accountability 22

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 23

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 24

25 25

26 26

27 5) Future Improvements & ROI 1) 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. 27

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 28

29 Pre-Incident Planning ( PIP )