CRISES INFORMATION SYSTEM WITH ARCGIS SERVER Esri International User Conference 2011
Lechwerke AG 29.06.2011
Seite 1
CRISES INFORMATION SYSTEM WITH ARCGIS SERVER Who is the Lechwerke AG? Current Situation Underlying data and participating services Architecture and Workflow Demo Advantages and conclusion Lechwerke AG 29.06.2011
Seite 2
WHO IS THE LECHWERKE AG?
Lechwerke AG 29.06.2011
Seite 3
Lechwerke – Energy supplier in southern Germany Lechwerke > … are a company which provides energy in Bavaria and parts of Baden-Württemberg. > … generate their own environmentally friendly electricity mainly from hydropower. > … focus on regional identity, proximity to customers and customer liaison and support. > … are a driving force for economic development in the region. Germany LEW ruled area
> … are part of RWE AG group.
LEW shareholder > RWE AG:
89,87 %
> Public Authorities: 6,74 % > Widespread Shareholdings:
3,39 % Lechwerke AG 29.06.2011
Seite 4
Lechwerke – Distribution service organization Essential figures > High Voltage (110 kV) overhead line 1,818 km distribution station
112
> Medium Voltage (20 kV) overhead line cable Substation
3,382 km 3,828 km 9,166
> Low Voltage (0,4 kV) 380-kV line 220-kV line 110-kV line
overhead line cable
10,423 km 14,365 km
> Local Generators renewable energy plants cogeneration plants > Employees
42,700 289
106
Lechwerke AG 29.06.2011
Seite 5
CURRENT SITUATION
Lechwerke AG 29.06.2011
Seite 6
Current Situation > Crises events put a lot of pressure to the network control > Doing network operation > Handling outages > Giving information to the crises management > Different applications for – GeoKIS for outages – GeoAIS for network data
Lechwerke AG 29.06.2011
Seite 7
Aims > How can we improve the situation for network control? – Inform crises management automatically – Faster decisions for crises management – Take pressure from network control – Put applications together – Minimize effort to run multiple systems
Lechwerke AG 29.06.2011
Seite 8
UNDERLYING DATA AND PARTICIPATING SERVICES
Lechwerke AG 29.06.2011
Seite 9
Outages from network control > Medium Voltage (20 kV) outages are recorded by network control > Low Voltage (1kV) outages are directly recorded by the technicians on a web-application > Types of outages – planned, e.g. construction, maintenance – unplanned, e.g. component failures, weather events
> Severity – How many stations are affected in relation to the existing number of stations in that area – Higher Impact: 1 Station out of 2 is out of service – Lower Impact: 2 Stations out of 20 are out of service
Lechwerke AG 29.06.2011
Seite 10
ArcGIS Server Services > Cached ArcGIS Server Service – Overview •
data from open source project Open Street Map
•
CORINE Landusage from European Environment Agency
– Basemap •
data from local survey authority
> Dynamic ArcGIS Server Service – Medium voltage (20kV) – Outages from Time-Featureclass
Lechwerke AG 29.06.2011
Seite 11
Client / User Frontend > Web 2.0 Client based on AGS JavaScript API 2.2 > WebRaMSy (RapidMapSystem) > Why JavaScript? – Silverlight- or Flex-Plugins are not area-wide available on LEW-Browsers – More flexible for project work, no IDE or compiler needed – Better integration for other html-based application (in this case Oracle APEX) – Further improvements expected thru HTML 4.0 – Large development community
Lechwerke AG 29.06.2011
Seite 12
SYSTEM ARCHITECTURE AND WORKFLOW
Lechwerke AG 29.06.2011
Seite 13
Components & concept standard webbrowser
Network control
middle voltage outages (20kV)
APEX Reports
Web RaMSy based on AGS JavaScript API
Web application
low voltage outages (1kV)
German Weather Service
GIS server
Oracle APEX
lightning service Oracle
ArcGIS Server
AGS Cache
Lechwerke AG 29.06.2011
Seite 14
Data interchange Network Control → GIS DMZ
Network Control
ASCII
Oracle
Oracle
ASSET DB
ARC SDE
Linux
> Scheduled task with Linux crontab – Copy ASCII-File from Network Control to GIS Environment – Update every 3 minutes
Lechwerke AG 29.06.2011
Seite 15
Data interchange Network Control → GIS NST.txt
MS + 02.03. 13:04:00 650J MS + 02.03. 13:04:00 650H MS + 02.03. 13:00:00 650Q MS + 02.03. 12:58:00 686A
KARLSEBENE STEINGÄDELE VODERGRÜNDL HELMAU
oracle@le06681:/USR1/PSI_NTF> cat NST.txt L 49kVA Sn 100kVA NTF 4440 NTF nicht versorgt Geplant L 196kVA Sn 160kVA NTF 13718 NTF nicht versorgt Geplant L Sn 100kVA NTF 8918 NTF nicht versorgt Geplant L Sn 160kVA NTF 5603 NTF nicht versorgt Geplant oracle@le06681:/USR1/PSI_NTF>
SICAD 0402251528200067883473 SICAD 0402251525400034840911 SICAD 0402251533550121917978 SICAD 0402251531480104522733
> GIS is the leading system for substations – Unique identifier is the GIS-ID (OBJ-ID)
> Network Control provides list with outages of substations – Status planned or unplanned – Beginning of outage – Further descriptions, i.e. name of substation
Lechwerke AG 29.06.2011
Seite 16
Data interchange Network Control → GIS DMZ
Network Control
ASCII
Oracle
Oracle
ASSET DB
ARC SDE
Linux
> Import ASCII file to ORACLE
Lechwerke AG 29.06.2011
Seite 17
Data interchange Network Control → GIS external table
ASSET-DB
PL/SQL
table
ASCII
> Join ASCII-file as „external table“ to Oracle > Import into table by PL/SQL - procedure
Lechwerke AG 29.06.2011
Seite 18
Data interchange Network Control → GIS DATE_OFF 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00 03.02.2011 12:58:00
STATUS Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant Geplant
TRAFO_ID 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733 0402251531480104522733
DATE_INSERT 03.02.2011 15:58:46 03.02.2011 15:55:46 03.02.2011 15:52:46 03.02.2011 15:49:46 03.02.2011 15:46:45 03.02.2011 15:43:45 03.02.2011 15:40:45 03.02.2011 15:37:45 03.02.2011 15:34:45 03.02.2011 15:31:45 03.02.2011 15:28:45 03.02.2011 15:25:45 03.02.2011 15:22:45 03.02.2011 15:19:45 03.02.2011 15:16:45 03.02.2011 15:13:45 03.02.2011 15:10:45 03.02.2011 15:07:45 03.02.2011 15:04:44 03.02.2011 15:01:44 03.02.2011 14:58:44 03.02.2011 14:55:44 03.02.2011 14:52:44 03.02.2011 14:49:44 03.02.2011 14:46:44 03.02.2011 14:43:44 03.02.2011 14:40:44 03.02.2011 14:37:44 03.02.2011 14:34:44
STATION_ID 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499 0304091510270024712499
NAME HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU HELMAU
ORT Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem Prem
ORTSTEIL Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau Helmau
BETRIEBSSTELLE X Y AUSFUEHRUNG KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast KB 46 Schongau 4.410.418 5.284.688 Betoneinmast
> Resulting table after Oracle-import
Lechwerke AG 29.06.2011
Seite 19
Data interchange Network Control → GIS DMZ
Netzleitstelle
ASCII
Oracle
Oracle
ASSET DB
ARC SDE
Linux
> Import ORACLE table to ESRI Geodatabase
Lechwerke AG 29.06.2011
Seite 20
Data interchange Network Control → GIS ASSET DB table
TRIGGER
ARC SDE
before, update, delete, insert
(ST_GEOMETRY)
insert into fcl_outages values (sde.ST_PointFromText('point(52 24)',1));
feature class
15:02 15:05 15:08 15:11
start 15:02
end 15:11
> Status of substations is updated every 3 minutes via ASCII file – Many records per substation and outage
> Merge data when importing into Geodatabase – One record per substation and outage with start and endtime
> Insert via SQL and datatype ST_GEOMETRY Lechwerke AG 29.06.2011
Seite 21
Time-aware Layer in ArcGIS > To use time-aware layer – Enable Time-usage in ArcMap – Layer-properties, tab “Time” – Assign start time and end time to the corresponding fields
> Properties for display depend on client – Various setting are available for JS-API – Show all points of the last 3 minutes – WebRaMSy specific: refresh every 50s
Web RaMSy ArcGIS Server 15:02
15:11
Lechwerke AG 29.06.2011
Seite 22
LIVE DEMO
Lechwerke AG 29.06.2011
Seite 23
ADVANTAGES AND CONCLUSION
Thorben Wengert / pixelio.de
Lechwerke AG 29.06.2011
Seite 24
Advantages Inform crises management automatically Faster decisions for crises management Take pressure from network control > Easy to use web-application > Overview and detailed information for crises management > No longer request to network control for updated figures
Put applications together Minimize effort to run multiple systems > GeoKIS and GeoAIS use same technique > Before Oracle-Maps and SICAD/IMS now ArcGIS Server
Lechwerke AG 29.06.2011
Seite 25
Conclusion > ST_GEOMETRY gives strong ability to insert and edit feature data > JS-API is flexible and very integrative in web 2.0 applications > AGS Cache combined with dynamic service gives user responsive feeling > Time-aware functionality offers new possibilities to support existing tasks and workflows
Lechwerke AG 29.06.2011
Seite 26
THANK YOU FOR YOUR ATTENTION.
Lechwerke AG 29.06.2011
Seite 27