spin-off de la Universidad de
Valencia

Xpose Mobile
Improve the Incident Management Chain

Leo van den Berg
ESAM S.L.

Copyright © 2014 ESAM S.L.

All rights reserved. No part of this document may be reproduced, stored in a retrieval system or transmitted in any f orm or by any means,
without the prior written approval of ESAM S.L. except in the case of brief quotations in which case ref erence to the copyright owner
should be made.
Xpose-Mobile
Introduction #1






Incident Management (IM) is a complex process involving
different [human] resources divided over different
organizations and locations.
Each organization has its own “view of the reality” based on
their own data
To achieve organizational interoperability the semantic and
technical interoperability must be solved first!




A common “domain language” should be used to
unambiguously describe IM data items like: Location (BPS),
Incident types, Measures, Tasks etc. etc.
A set of services should be available to access and exchange
data independent of used [mobile] device and location.
Xpose-Mobile
Introduction #2


The rapidly increasing quality and coverage of mobile networks
enables the inclusion of “mobile intelligence” (APP’s) in the IM-chain:






Mobile functionality should be seamlessly integrated with the IM-chain
to unlock its full potential. Functionality:






Android and iOS based smartphones and Tablets,
Other “wearable” technology is under development

should take in account the environmental restrictions of the mobile user
(light, sound, driving a car etc.)
should provide maximum usability and quality

Ruggedized devices are already available for “hostile” environments
(and users).
Xpose-Mobile
Introduction #3


Xpose is an extensible data processing
and distribution platform for fast
development of ITS applications,



… the domain [data] model is based on
[international] standards related to Trafficand Incident Management entities.



… uses an industry standard object
relational mapper for storage of all the
managed entities in a relational database,



… uses web-services [SOAP/Rest] for
the exchange of data with mobile
devices,
Xpose-Mobile
Applications


The already available APP’s can be divided in:






One-way messaging (ex: Simple Incident Notification),
Bi-directional messaging (ex: Incident Chat)
Full interaction (ex: Incident/Damage registration),

All APP’s fully integrated with the Xpose-platform and
IM-application
Xpose-Mobile
Incident Notification


Traffic Operator (OP) sends message Notification to
Roadside Assistance (RA),



Notification received on mobile device
Notification triggers chat APP
Xpose-Mobile
Incident Chat


Live interaction between Operator (OP) and Roadside
Assistance (RA),




RA has access to relevant Incident data and full lncident
log
RA can send short messages and images to the OP
OP receives RA-messages and images in Incident log,
Xpose-Mobile
Damage registration


Live Interaction between Operator (OP) and
Roadside Assistance (RA),





RA identifies [different] damage[s] at the Incident
Location,
RA has access to relevant Incident Data,
OP receives direct feedback
OP can request additional data with the Chat
functionality
Xpose
Software availibility


Xpose core is available as open-source software under
version 2.0 of the Apache Software License



Our SaaS - platform will support an expanding set of
services for (Incident) Management:









Registration ,
Data enrichment,
Data Exchange,
Data Export,
Decision Support,
Reporting,
Messaging Etc. etc.
spin-off de la Universidad de
Valencia

Contact me for further information!

Leo van den Berg
ESAM S.L.
l.vdberg [at] esam.uv.es
Tel: +34 96 354 3552

10

24/02/2014

Xpose Mobile

  • 1.
    spin-off de laUniversidad de Valencia Xpose Mobile Improve the Incident Management Chain Leo van den Berg ESAM S.L. Copyright © 2014 ESAM S.L. All rights reserved. No part of this document may be reproduced, stored in a retrieval system or transmitted in any f orm or by any means, without the prior written approval of ESAM S.L. except in the case of brief quotations in which case ref erence to the copyright owner should be made.
  • 2.
    Xpose-Mobile Introduction #1    Incident Management(IM) is a complex process involving different [human] resources divided over different organizations and locations. Each organization has its own “view of the reality” based on their own data To achieve organizational interoperability the semantic and technical interoperability must be solved first!   A common “domain language” should be used to unambiguously describe IM data items like: Location (BPS), Incident types, Measures, Tasks etc. etc. A set of services should be available to access and exchange data independent of used [mobile] device and location.
  • 3.
    Xpose-Mobile Introduction #2  The rapidlyincreasing quality and coverage of mobile networks enables the inclusion of “mobile intelligence” (APP’s) in the IM-chain:    Mobile functionality should be seamlessly integrated with the IM-chain to unlock its full potential. Functionality:    Android and iOS based smartphones and Tablets, Other “wearable” technology is under development should take in account the environmental restrictions of the mobile user (light, sound, driving a car etc.) should provide maximum usability and quality Ruggedized devices are already available for “hostile” environments (and users).
  • 4.
    Xpose-Mobile Introduction #3  Xpose isan extensible data processing and distribution platform for fast development of ITS applications,  … the domain [data] model is based on [international] standards related to Trafficand Incident Management entities.  … uses an industry standard object relational mapper for storage of all the managed entities in a relational database,  … uses web-services [SOAP/Rest] for the exchange of data with mobile devices,
  • 5.
    Xpose-Mobile Applications  The already availableAPP’s can be divided in:     One-way messaging (ex: Simple Incident Notification), Bi-directional messaging (ex: Incident Chat) Full interaction (ex: Incident/Damage registration), All APP’s fully integrated with the Xpose-platform and IM-application
  • 6.
    Xpose-Mobile Incident Notification  Traffic Operator(OP) sends message Notification to Roadside Assistance (RA),   Notification received on mobile device Notification triggers chat APP
  • 7.
    Xpose-Mobile Incident Chat  Live interactionbetween Operator (OP) and Roadside Assistance (RA),    RA has access to relevant Incident data and full lncident log RA can send short messages and images to the OP OP receives RA-messages and images in Incident log,
  • 8.
    Xpose-Mobile Damage registration  Live Interactionbetween Operator (OP) and Roadside Assistance (RA),     RA identifies [different] damage[s] at the Incident Location, RA has access to relevant Incident Data, OP receives direct feedback OP can request additional data with the Chat functionality
  • 9.
    Xpose Software availibility  Xpose coreis available as open-source software under version 2.0 of the Apache Software License  Our SaaS - platform will support an expanding set of services for (Incident) Management:        Registration , Data enrichment, Data Exchange, Data Export, Decision Support, Reporting, Messaging Etc. etc.
  • 10.
    spin-off de laUniversidad de Valencia Contact me for further information! Leo van den Berg ESAM S.L. l.vdberg [at] esam.uv.es Tel: +34 96 354 3552 10 24/02/2014