1 / 33

JIXEL

JIXEL. The first web 2.0 Joint Control room Massimo Cristaldi, CTO IES Solutions m.cristaldi@iessolutions.eu. Agenda. What is it? How it was conceived High level components Technical Deployment Stress test and performances How to use it. What is it?.

stanleydhoward
Download Presentation

JIXEL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JIXEL The first web 2.0 Joint Control room Massimo Cristaldi, CTO IES Solutions m.cristaldi@iessolutions.eu

  2. Agenda • What is it? • How it was conceived • High level components • Technical Deployment • Stress test and performances • How to use it

  3. What is it? • The first STANDARD based Joint Control ROOM Web 2.0 • EDXL-CAP compliant • EDXL-DE enabled • A suite of software components, that realize a Service Oriented Architecture • Web 2.0 based, Open Source, • Deployable online as a set of loosely coupled services (Jixel Online) or as a single appliance, with standard interfaces for interoperability with external systems (Jixel appliance) • CREATED MAINLY TO DISTRIBUTE CAP and EDXL-DE messages

  4. Brief History • Kick-off: 2006 • EU Project REACT • Adopted the CAP Protocol • Suggested the use of this protocol in PSAP-to-PSAP interop • Paved the way for the adoption in ITALY • Commercial Deployment • Aquila Earthquake 2009 • Calabria Region Fire management (2010-2011) • Emilia Romagna quake 2012 • Fully adoption by Italian Fire Fighters

  5. JIXEL Components

  6. JIXEL Components

  7. JIXEL Components

  8. JIXEL Components

  9. JIXEL Components

  10. JIXEL Components PSCE Forum– Brussels 19/11//09

  11. Conceptual Components • Input (CAP Generator / C&C systems) • Web & GIS GUI • Web Service interfaces • EDXL-CAP messages • Distribution (CAP Router) • EDXL-CAP validation • Loosecoupling • FAST delivery • Output (CAP Retriever & CAP Viewer / C&C systems / Feedviewers) • Web & GIS GUI • EDXL-CAP messagesAggregation and Storage

  12. Layout SENDER Generator RECIPIENT1 Viewer WS WS Router RECIPIENT2 Atom Viewer RECIPIENT2 Feed Reader

  13. CAP Generator

  14. Other Generators • The m-JIXEL APP • Mainly targeted to DEAF people

  15. CAP ROUTER • Concepts • Validation and ingestion of incoming CAPs • Publication / Distribution of CAPs via public and private (password protected) ATOM feeds • Technology • Web Service interfaces • CAPs storing using Apache Hadoop • ATOM feeds implementation using the Apache Abdera framework

  16. CAP ROUTER – Sample Feed (Browser View)

  17. ROUTER delivery TIME & ReliabilityLoose coupling performances • Test objectives • To measure the time for an incident update (a new CAP message) to be delivered to the intended recipient [it is expected that it pulls information from different feed channels (different sources)] • To evaluate the impact of the CAP Router loadon the time needed for retrieving a single feed • To assess the system reliability (CAP success/loss ratio) • Test scenario: • One feed is configured for each sender/recipient pair • 25 producers generate and send CAP messages to the CAP Router: average input rate is 10 CAPs per second • the CAP Router validates the received CAPs and publishes them onto 25 different feeds • one single consumer (CAP retriever) reads continuously and sequentially from the 25 populated feeds

  18. ROUTER delivery TIME & ReliabilityTotal time for reading and handling 25 feeds • Average time for completing a cycle: 21.5 seconds • No CAP losses on all cycles

  19. ROUTER delivery TIME & ReliabilityTime for reading one single feed • Average time for reading one single feed circa 683 milliseconds • No CAP losses on all cycles

  20. ROUTER delivery TIME & ReliabilityTime for reading one single feed on different CAP Router load conditions • the average time for reading one feed does not depend on the number of feeds handled by the CAP Router

  21. Functional elements: Incident API • Web Service which receives the incident details in CAP format from the CAP sources • Validates the received CAP message using rules based on the CAP standard • Sends the CAP message to the next component in the chain (CAP Publisher) • Supports EDXL-DE messages.

  22. Functional elements: CAP Publisher • Receives CAP messages from the Incident API • Creates AtomPub based feed entries • Sends a publish request to the CAP Feed Server

  23. Functional elements: CAP Feed Server • The component in charge of publishing the CAP Feed to the right feed URL • Receives the new feed entry • Checks the originator and recipients of the event (looking at the information carried inside the CAP message) • Stores the new feed entry into the file system, in order to make it accessible at specific URLs • If the originator of the event is PSAP1 and one of the recipients is PSAP2, the specific URL for that recipient will be something like: https://capfeed.originator.org/PSAP1/PSAP2

  24. Functional elements: CAP Recipients • The client level components able to get the event details sent by the originator • Feeds generated for a given recipient can be read by using a common Feed Reader or from the browser at specific URLs • It is also possible to get and visualize event information, extracted from the CAP message, by using additional components

  25. Functional elements: CAP Retriever • Java service used to get the feeds at specific URLs • Each read feed entry is translated again in CAP format and sent to the next receiving component in the chain, i.e. the Datastore

  26. Functional elements: Datastore • The Datastore Web Service: • receives the event details in CAP format • stores the received CAP into an incidents database

  27. Functional elements: CAP Viewer • The CAP Viewer is an online service implemented to integrate the traditional legacy C&C system: • it gets incidents information from the incidents database • it allows the C&C operator to visualize the incidents sent by the originator PSAP, and to analyze its location, severity, and act accordingly

  28. CAP Viewer

  29. Physical Deployment in Italy

  30. JIXEL Online • JIXEL online is deployed as a set of Web Services and Web Sites in the CLOUD • JIXEL components and data storages can be deployed in different servers, and in the cloud SaaS (Software as a Service) based architecture

  31. JIXEL Appliance • JIXEL appliance is deployed in a server, with all the JIXEL software components on board • A server that can be installed at Emergency Services premises and offer all JIXEL applications • configuration components that made the solution highly and easily customizable • web software interfaces for connecting the appliance to the external world, realizing the interoperability with other legacy systems

  32. http://demo.jixel.eu REGISTER to DEMO.JIXEL.EUas a single or as a group

More Related