ertms solutions - semantic railways presentation october 2016

Download ERTMS Solutions - Semantic Railways Presentation October 2016

If you can't read please download the document

Post on 18-Jan-2017

246 views

Category:

Data & Analytics

5 download

Embed Size (px)

TRANSCRIPT

Slide 1

The Fast Track to ERTMSGMS / ODASE in GMS10/27/20161CONFIDENTIAL

10/27/2016Company Presentation CONFIDENTIAL#

1

10/27/20162Presentation of ontologiesSummary of POC objectivesPresentation of POCNext steps discussionAgendaCONFIDENTIAL

Semantic RailwaysNew business line at ERTMS Solutions since 20/12/2015

One first customer = Siemens for INFRABEL ETCS2 maintenance system Ontologies POC

Three pillarsODASE: a proven-in-use software platform to deploy ontologiesA reusable existing railway ontologyA methodology: ontology-based software integration10/27/2016310/27/20163

CONFIDENTIAL

3

Ontology = Executable Business ModelFormalMachine processable

Understandable by Business and IT expertsConsensual knowledge, shared by all stakeholders

Explicit specification, using the vocabulary of the Business Concept Person, Man, Woman, Organization, Country...PropertiesDate of birth, Gender...AxiomsMan and Woman are disjoint conceptsRulesA young driver is a driver whose age is under 25

Based on formal logic - ReasoningIf (X brother of Y) and (Y parent of Z) then (X uncle of Z)

Independent of any implementation technology (COBOL, Java...)10/27/2016410/27/20164

CONFIDENTIAL

4

3 Dimensions, 3 standards

10/27/20165CONFIDENTIAL

5

Test, Explain, Change... Early

Mainstream ODASEWhatDefinedTestedExplainedUnderstoodValidatedbefore programming

10/27/20166CONFIDENTIAL

6

The Tools & Platform to build Ontology-Centric Systems

10/27/2016710/27/20167

CONFIDENTIAL

7

Case #1 AVIVA

Direct sales insurance, multi-channels (web, comparators, call center)Trigger: extreme agility required by comparatorsOntology = products, bundles, rating, scoring, risk acceptance, dynamic UI Digital transformation phase 1: keep what doesn't change (accounting)Semantic integration with mainframe (IBM, COBOL, DB2, MQ)Result: sales doubled in 2 years

Changes in 1 dayNot in 3 months

10/27/20168CONFIDENTIAL

8

Ontology = Business DefinitionOntology = Comprehensive Model of Car Insurance208 concepts (defining the vocabulary)598 concepts properties (attributes, relations)607 rules70% = Business definition30% = Integration (AS/400 legacy)

OntologistsTwo COBOL programmers, trained in 8 weeks to become ontologistsFinding: easier to learn ontologies (logic, set theory) than Java (OOP) ConciseCompleteValidated10/27/20169CONFIDENTIAL

9

Metric (Railways Traffic Management example)65 Rules87 ConceptsDramatic impact in terms of cost, quality, flexibility and time

130 000 LOC(Forte)4 623 LOC(Java)10/27/201610CONFIDENTIAL

10

Summary of initial POC objectivesOntology expert service days 20 days

ScopeINPUTINFRABEL GMS 300 requirementsGMS data sources + data dictionnaryINFRABEL top 3 user stories

OUTPUTDraft GMS ontology (OWL concepts + SWRL rules)Live demonstrationExecutable example with user storiesDemonstration of root cause analysisDemonstration of evolutivity: live rule change + recalculation/effectDemonstration of integration (e.g. SQL schema generation to support Siemens GMS DB design)10/27/201611

CONFIDENTIAL

Presentation of POC - architecture10/27/201612

CONFIDENTIAL

Presentation of POC - metricsGMS Ontology80 concepts90 properties70 rules 35 business19 data integration, 18 User Interface(720 LOCS total)

Plumbing LOCS1200 LOCS Java370 LOCS Javascript40 LOCS HTML10/27/201613CONFIDENTIAL

Presentation of POC GSM OntologyTrack objects10/27/201614

CONFIDENTIAL

Presentation of POC GSM OntologyLog events10/27/201615

CONFIDENTIAL

Presentation of POC GSM OntologyMessages and alarms10/27/201616

CONFIDENTIAL

Presentation of POC GSM OntologyPeriods10/27/201617

CONFIDENTIAL

Presentation of POC visual overview10/27/201618

CONFIDENTIAL

Short term: 4 months 1/6/2016 30/9/2016User stories implement the most relevant

Un systme dalimentation lectrique dfaillant cause la perte de communication avec des objets dinterlocking comme des circuits de voie ou des aiguillages. On a dun ct une alarme donne par le systme dalimentation et de lautre une alarme au niveau interlocking. Dduire que le problme est uniquement ct alimentation, supprimer lalarme InterlockingDeux systmes schangent des informations (e.g. des autorisations de blocage de sens), celui qui doit les recevoir ne les reoit pas. En vrifiant le ct metteur, on peut facilement voir si linformation est mise. Si elle est bien mise, on peut en conclure que linformation est perdue entre les deux. Un aiguillage subit des pertes de contrle, si on a des informations sur le circuit de voie qui lui est li (home track-circuit), on peut en dduire que le problme survient au passage dun train ou non. Avec des informations sur le numro de train, on peut en dduire si tous les trains posent le problme de d-contrle ou si ce sont seulement ceux qui font un certain tonnage ou une certaine longueur. Linformation sur le train peut venir de lEBP ou de lA173.On mesure les temps doccupation des circuits de voie. Un temps doccupation trop court caractrise gnralement un problme sauf si loccupation est cause par un train court et rapide. Cette information peut tre connue si on connait le numro de train via lEBP.10/27/201619CONFIDENTIAL

Implemented user stories detailsUn systme dalimentation lectrique dfaillant cause la perte de communication avec des objets dinterlocking comme des circuits de voie ou des aiguillages. On a dun ct une alarme donne par le systme dalimentation et de lautre une alarme au niveau interlocking. Dduire que le problme est uniquement ct alimentation, supprimer lalarme Interlocking

If an LX reports RA/Ra 0 then raise an alarm

In IXL log, LX 15L44 sends a RA(15L44) at 09:15:02.310. This is translated into an alarm, displayed on the LX

10/27/201620

CONFIDENTIAL

Implemented user stories detailsOn mesure les temps doccupation des circuits de voie. Un temps doccupation trop court caractrise gnralement un problme sauf si loccupation est cause par un train court et rapide. Cette information peut tre connue si on connait le numro de train via lEBP.If an LX is on alarm, and a TC nearby is occupied for more than a minute, link the alarms10/27/201621

CONFIDENTIAL

Implemented user stories detailsOn mesure les temps doccupation des circuits de voie. Un temps doccupation trop court caractrise gnralement un problme sauf si loccupation est cause par un train court et rapide. Cette information peut tre connue si on connait le numro de train via lEBP.US3 : LX occupied to long, links to neighbouring LX occupied too long (more than 2.5 mins)7L44 and 6L44 are open for too long10/27/201622

CONFIDENTIAL

Implemented user stories detailsUn aiguillage subit des pertes de contrle, si on a des informations sur le circuit de voie qui lui est li (home track-circuit), on peut en dduire que le problme survient au passage dun train ou non. Avec des informations sur le numro de train, on peut en dduire si tous les trains posent le problme de d-contrle ou si ce sont seulement ceux qui font un certain tonnage ou une certaine longueur. Linformation sur le train peut venir de lEBP ou de lA173.05/18 A Track Circuit (V-511) is occupied for too long (2M6S). The train on that track section (S511) was the 749410/27/201623

CONFIDENTIAL

Implemented user stories detailsUn systme dalimentation lectrique dfaillant cause la perte de communication avec des objets dinterlocking comme des circuits de voie ou des aiguillages. On a dun ct une alarme donne par le systme dalimentation et de lautre une alarme au niveau interlocking. Dduire que le problme est uniquement ct alimentation, supprimer lalarme Interlocking#power failure at 9:01 am on UM(23)#which controls PN3 - causing an alarm on PN3#and on TREADLE CVC(A3+A4)

NOTE: we had to inject a dummy power failure, as there were no power failure in source data

10/27/201624

CONFIDENTIAL

10/27/201625CONFIDENTIAL

Thank you for your attention!www.ertmssolutions.com

Recommended

View more >