G# in a nutshell · Nomen est Omen 4 Geodata SHARed Platform G-SHARP G# GIS According to music...

G# in a nutshell

Raoul Pärli (Swiss Federal Railways)

Rafael Brunner (Ernst Basler + Partner)

Presenters

SBB • Division • Abteilung oder Bereich • DD.MM.YY 2

[email protected]@sbb.ch

Agenda

1. What does G-SHARP mean and what has it to do with music?

2. Why G-SHARP?

▪ Requirements

▪ History

3. G-SHARP Architecture

▪ Components

▪ Operations Architecture

▪ Technologies

▪ Roles and Users

4. Results

▪ Built solutions

▪ Lessons learned

Nomen est Omen

4

Geodata SHARed Platform G-SHARP G# GIS

According to music theory

«In music theory, each tone can be tuned up or down by a half-tone step:

A # indicates tune up a b indicates down. Also the names are changing.

G becomes to G#, A becomes to Ab»

In german, G# is pronounced as Gis.

Duke Ellington wrote in his autobiography

«I really only understand music, as I understand the difference between G# and Ab.»

SBB • Informatik • G# • März 2017

G# = Ab

Why G-SHARP?

Requirements

6SBB • Informatik • G# • März 2017

Systematic, holistic analysis of Requirements over all departements A total of more than 600 Requirements had been gathered and Transformed into 57 Requirements used in the public tender

The most important: • Map Services, enabling the use of external geodata like

national map of switzerland, OpenStreetMap, etc.• Map Services, representing several internal data such as

railway tracks, stations, signals, power lines, etc.• Visualize and edit railway data objects in mobile applications• Technical basis for interoperability with Systems like SAP• Standardize and simplify the way of using and editing geodata

History

G-SHARPOperation

2013 2014 2015 2016 2017

Conceptwork Realisation

Duration of project

Duration of productive platform

Projectstart

Scope change and

renaming

Enhancement of geodata referencearchitecture and requirements

Prepare and run the tender

Concept for building the platform

Go live

Live cycle, support, consultance

Requirementanalysis

Building the platform,

Organisation for operation

Study

SBB • Informatik • G# • März 2017 7

Publish the tender

on SIMAP

G-SHARP Architecture

SBB • Informatik • G# • März 2017 9

Additional value by intelligent use of geodata

Geodata Infrastructure (GDI)

The GDI serves as the basis for G-SHARP and is used for running geobasis

services as well as providing the GDI in a shared mode like PaaS we call it

GDIaaS. It contains IT components like spatial databases, GIS server,

WebGIS application hosting, etc.

The most important technologies are:

▪ Esri ArcGIS technologies (Desktop, Web, Server)

▪ Esri Portal for ArcGIS as «SBB Geoportal»

▪ Esri SDKs for building GIS-Clients (Web, Desktop, Mobile) and serverside

extensions

▪ FME Desktop and FME Server for ETL processes

▪ MapProxy for «internalising» and the «proxification» of external geo

content e.g. services from swisstopo

▪ EXADATA Oracle Shared Plattform for geo-enabled databases


Geobasis Services

Geobasis services mainly consists of map services which provide external

geodata or geo services internally, ready to consume in a standardized way

External data sources could be the following: national map of switzerland,

aerial photos, boundaries, demographic borders, geopost, OpenStreetMap,

etc.

Internal data sources could be the following: track network, assets like

signals, power lines, buildings, but also organisational areas like ticket zones

etc.

Also geocoding and geoprocessing services are available in order to support

processes such as georeferencial storage of photos and documents.


Geoportal

The «SBB Geoportal» is a self-service geo content management system

including visualisation of the available geobasis services as base maps. Its

purpose is to fill up the gap between a full fledged GIS and no GIS at all.

The «SBB Geoportal» in it’s basic design is available for free to all

employees who have access to the intranet. It can be easily used as

collaboration plattform to share maps and geo content within groups and

across departments.


Team

The G-SHARP team is meant to be responsible for:

▪ Operate and live cycle of the geodata infrastructure (GDI)

▪ Operate and live cycle of the geobasis services

▪ Operate and live cycle of the geoportal

▪ Consulting projects

▪ Enable software engineers and –architects in using G-SHARP

technologies

▪ Create and maintain technology blueprints and best practices

▪ Supporting decision making in general GIS questions


Clients

14

G-SHARP consists of three Components. Therefore it also has

several different stakeholders

• IT-Systems with remarkable GIS-portion• Built with the G-SHARP technology and SDKs• Run on G-SHARP in GDIaaS mode, cloudbased variant

available for B2C | B2B solutions

• IT-Systems (legacy oder new) with a small GIS-portion, built

and run outside the G-SHARP environment

• Use of geobasis services

• Order of special geodata (e.g. engineering partners)

• Persons, Departments, Projects• Use of the geoportal functionality in self-service mode• Create and maintain there own geo content• Cloudbased variant for B2C | B2B solutions possible


Component Overview


Geodata Infrastructure (GDI)

Geobasis Services

ArcGIS FME MapProxy IIS

Technologies

Platforms

Applications

use

DiDok IVEG

GeoFA

GDIaaS Applications

Services / Products

SBB Geoportal

(S, M, L)

Geo-services

(S, M, L)

GDIaaS(S, M, L)

Data Service(S, M, L)

enabling

etc...

DfA UNO

«Legacy»

Other Applications

etc...

Geoportal

use

Operations Architecture


▪ ArcGIS for Server

▪ Portal for ArcGIS/ArcGIS Online

▪ ArcGIS Desktop (ArcMap und ArcGIS Pro)

▪ Map Proxy

▪ Map Caching

▪ FME Server

▪ FME Desktop

▪ Extract Transform Load (ETL) for geodata

Technologies


User Client Web Application Firewall

Request

Identity Store(eBiz)

Authentication(User)

G-SHARP

Requestauthenticated

Autorisation(Role)

UserAndRoles

Client

manage UserGroup

Client

UserGroup

UserGroup

UserGroup

ClientUserGroup

UserGroup

G-SHARP

Role

Role

Role

Role

Role

Client

manage UserGroup

Admin

manage Roles

manage Roles

eBiz Structure

connet UserGroup to RoleUser

User

User

Clients, Roles, User

18

?

?


Results

Projects built on G-SHARP

21

14 projects and proof-of-concepts already build on G-SHARP

technology or GDIaaS

3 of them are accompanying the G-SHARP project from the very

beginning

Themes like the following are the main players

▪ Managing nature risks along the railroad tracks

▪ Inventory for green areas (cutting trees and bushes)

▪ Master system for managing the inventory of all railway stations in

Switzerland

▪ Geospatial financial object mapping (aggregate SAP objects)

▪ Offline Tourist Information System for Gotthard panoramic express

▪ Proof of concept for

Multi modal routing

Batch plotting

Security within railway tracks SBB • Informatik • G# • März 2017

Web GIS Examples

22

Master for railway stations DiDokManaging nature risks NNRInventory for green areas IVEG


Lessons learned

It is important to know both, functional and non functional

requirements.

It’s worth, defining a reference architecture and do think in patterns.

A public tender has to be well prepared.

Big projects hide uncertainties and risks. A team with a good spirit

may handle it well.

«Depth first» - build deep, think broad

There is always another release after this release – nothing lasts

forever


Thank you for listening

Though SBB does not know the difference

between G# and Ab as well as Duke Ellington,

it is fully aware of the meaning of G#.

G# in a nutshell · Nomen est Omen 4 Geodata SHARed Platform G-SHARP G# GIS According to music...

Documents

Transcript of G# in a nutshell · Nomen est Omen 4 Geodata SHARed Platform G-SHARP G# GIS According to music...