GIS-based vegetation management at Swiss Federal Railways SBB Berlin 10.05.2017 Simon Haesler (overall project manager) Adrian Aschwanden (Esri Switzerland) simon.haesler@sbb.ch a.aschwanden@esri.ch
Agenda 1. Introduction 2. Product Demonstration - IVEG in action 3. Summary and lessons learned 2
Introduction
Introducing of nature and natural hazards at SBB Tasks Our safety specialist for railways are responsible for: Protection against gravitational hazards e.g. avalanches, rock fall, flood Protection along the tracks e.g. tree and branches Suppressing of the vegetation along the tracks and embankments Goal Interference-free operation of the SBB rail network for all trains and passengers. Aufgaben und Ziele 4
Introducing of nature and natural hazards at SBB 4 000 protective structures and 1 170 km tracks that are exposed to natural hazards 5
Introducing of nature and natural hazards at SBB 40 000 ha protective forest 6
Introducing of nature and natural hazards at SBB 4 500 ha wooded areas, 2 600 ha embankments, control of vegetation, neophytes and fence along the tracks. 7
Clearance Gauge based on the track category SBB Division Abteilung oder Bereich DD.MM.YY 8
The need for a new information system The current solution does not fulfill the state of the art technology- and business processes: Data quality: 12% of vegetation data in the database were not digitized Attributes are different used by region. Big differences of tracking level Missing functionalities in the existing application: No GIS functionality in the IVEG-Editor and WebGIS IVEG No mobile application No automized support of the Inventory collection Support of business processes Insufficient support of business processes 9
The Vision of the new Information system Vegetation Vision «All in one: monitoring, ordering and financing of the vegetation areas, planning, execution and accepting of the measure and last but not least the documentation of the vegetation Pros Minimal pre- and postprossessing (at the office) Self-collecting of Geodata (outdoor) Consistency of the System (platform conform) Cons Need more time outdoor (additional work e.g. Photos, collecting of more attributes) Complex system 10
Our Vision: Information system Vegetation Acceptance (2018) Monitoring (2017) Acceptance Sign of the reports Control/Check PLAN-TARGET- ACTUAL status GIS IVEG Status inspection Proposing measures Execution (2018) Funding (2017) Tenders (call for bids) Execution Reporting Request for measures Negotiate Financing of measures
Solution approach : automatization & repeatable of the ground cover classification
Solution approach: objective & repeatable clearance gauge inspection
Solution approach: mobile offline GIS App & browser GIS Application 14
Roadmap IVEG: 2013 2014 2015 2016 2017 IVEG Remote Sensing G# rough concept detail concept realization Tender Flight Classification study Concept work realization impleme ntation 15
16
IVEG in action
Introduction to the application
Ground Cover
Status inspection 33
Proposals for measures 37
Measures proposal
Funding measures
41
42
Preparation for tender 43
44
Execution 45
Acknowledge the measure state 46
SBB Division Abteilung oder Bereich DD.MM.YY 47
Working report SBB Division Abteilung oder Bereich DD.MM.YY 48
Working report (forest contractor) SBB Division Abteilung oder Bereich DD.MM.YY 49
Control /Check 50
51
conclusion
conclusion Increasing Data quality: The application forces the users to a uniform data tracking. The plausibility of the data can be checked at any time and transparently. Adding missing functionalities to the new IVEG application: The new IVEG is a pure and service-oriented GIS application The mobile application supports the users in the field with offline functionality Uniform and repeatable ground cover inventory with remote sensing Adding support of relevant business processes Almost real-time cost control (PLAN-TARGET-ACTUAL ) Ready ERP (SAP) Integration
Lessons learned: GIS platform parallel project start with IVEG and G-SHARP was suboptimal: hardly influenceable dependencies => project risk Minimum requirements for development start: two separate system environments => development & production development team with the right skills are essential: Esri development stack web development know-how the right hardware locally available (reserve server) SBB Division Abteilung oder Bereich DD.MM.YY 54
Lessons learned: Business Process Modelling nature is living: it was a challenge to bring all real conditions into IT information system testing first the new idea s about process support frequently meetings with the end-user reserve enough time for testing!!
Lessons learned: Ground Covering Classification the ground covering classification is a semiautomatic & iterative process control is time-consuming reserve enough time for unforeseen things (weather, flight permission) benefit with local air carrier (weather, flight permission ) be careful about the performance of your system you get very fast an amount of data = complex polygons SBB Division Abteilung oder Bereich DD.MM.YY 56
Lessons learned: Clearance Gauge Nevertheless fully digitized processes, we can say that the role of the human being is imperative. A profile deviation can not tell anything about the tree conditions. This is just a simple hazard map which only hints and does not state a real danger. SBB Division Abteilung oder Bereich DD.MM.YY 57
Lessons learned: Offline App pro: can be used in the mountains and protected forests can be used in neighboring foreign countries independent of mobile radio coverage No performance issues because of insufficient net connectivity contra: user has to follow to the synchronization process expensive development costs (two separate apps ipad and browser) advance complexity and additional sources of fault conclusion: clear the cost/benefits with your stakeholders
Feel free to ask any questions