1 / 53

A Prototype of an Emergency Resource Management System Based on EDXL and OWL

A Prototype of an Emergency Resource Management System Based on EDXL and OWL. Alessandro Triglia sandro@oss.com OSS Nokalva, Inc. Semantic Community Workshop Falls Church, VA 2009-02-17. About OSS Nokalva. Software company based in Somerset, NJ (founded in 1988)

nam
Télécharger la présentation

A Prototype of an Emergency Resource Management System Based on EDXL and OWL

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. A Prototype of an Emergency Resource Management System Based on EDXL and OWL Alessandro Triglia sandro@oss.com OSS Nokalva, Inc. Semantic Community Workshop Falls Church, VA 2009-02-17

  2. About OSS Nokalva • Software company based in Somerset, NJ (founded in 1988) • Main current product lines: • ASN.1 tools (compilers, encoder/decoders, utilities) • Biometric tools (middleware components, CTS) • Commitment to open standards • Actively involved in standardization in multiple areas: • ASN.1 (JTC 1/SC 6, ITU-T SG 17) • Biometrics (INCITS M1, JTC 1/SC 37) • Emergency management (OASIS EM TC – Alessandro is one of the editors of the EDXL-RM specification) • Geospatial (Open Geospatial Consortium)

  3. ERMS Prototype • We are developing a prototype of an Emergency Resource Management System(ERMS) • Supports the decisions of incident managers and EOC managers relative to the use of emergency response resources (requisition, assignment, commitment, release, etc.) • Completely based on open standards (EDXL-Resource Messaging, EDXL-Distribution Element, OWL 1.0)

  4. ERMS Prototype Characteristics • It is a Web application (even local users will use a Web browser to access the PC where the application runs) • Its concepts and data model were inspired by the OASIS EDXL-RM specification • Includes an ontology based on the NIMS Resource Typing system, which facilitates the assignment of resources according to needs (more on next slide) • Can play the role of resource supplieror the role of resource consumer(or both) • as a supplier, it manages a database of owned resources (including their assignment to consumers), and exchanges standard EDXL-RM messages with one or more consumers • as a consumer, it manages a database ofresource needs andborrowed resources, and exchanges EDXL-RM messages with one or more suppliers

  5. Emergency Response Resource Ontology • Work in progress • Based on the NIMS Resource Typing system • 120 major resource classes (e.g., GroundAmbulance, BackhoeLoader, EvacuationCoordinationTeam) and over 340 subdivisions (“types”) • Main classes in the ontology: • EmergencyResponseResource(large subtree) • Situation(large subtree) • SituationAspect(set of individuals) • A SituationAspect instance is similar to a “keyword” (e.g., buildingCollapsed) • Each Situation subclass is defined in terms of a logical expression of situation aspects • … and takes advantage of one or more emergency response resource subclasses

  6. Sample Screen Sequence • The next slides show a sample sequence of screenshots captured from the ERMS prototype, simulating the following scenario: • The resource supplier is San Francisco Emergency Operations Center • The resource consumer is a local Emergency Operations Center • There was an earthquake in the county. Debris removal resources as well as firefighting resources are needed • Two instances of the ERMS prototype were running, one playing the role of supplier and the other playing the role of consumer • The supplier assigned a resource to the consumer (BackhoeLoader) based on the keywords selected by the consumer

  7. Supplier switch to Consumer switch to Consumer switch to Consumer

  8. Consumer click

  9. select select

  10. scroll down

  11. click

  12. click

  13. click

  14. click

  15. click

  16. click

  17. click

  18. click

  19. back

  20. switch to Supplier switch to Supplier switch to Supplier

  21. Supplier click

  22. click

  23. click

  24. click

  25. click

  26. switch to Consumer

  27. Consumer refresh

  28. click

  29. back

  30. click

  31. click

  32. click

  33. switch to Supplier

  34. Supplier refresh

  35. click

  36. select type

  37. click

  38. switch to Consumer

  39. Consumer refresh

  40. click

  41. click

  42. click

  43. end of screen sequence

  44. ERMS Prototype • An early version of the ERMS prototype is currently running at the following URLs: • http://216.86.58.182/erms_consumer/ • http://216.86.58.182/erms_supplier/ • This is being provided to members of the emergency management community for the sole purpose of conveying our current ideas behind the ERMS and (hopefully) receiving feedback • We will use any feedback received to make sure that the final ERMS will meet the needs of the community

  45. Service Oriented Architecture – Service Description

More Related