1 / 18

Application Background

e-Government Integration with Web Services and Alerts: A Case Study on an Emergency Route Advisory System in Hong Kong. Application Background. Many public organizations and governmental departments offering useful services over the Internet

raina
Download Presentation

Application Background

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. e-Government Integration with Web Services and Alerts: A Case Study on an Emergency Route Advisory System in Hong Kong

  2. Application Background • Many public organizations and governmental departments offering useful services over the Internet • Increasing support of programmatic interfaces to these resources through Web services • Web services orchestration in e-Government processes integration and services • Case study: Emergency Route Advisory System (ERAS) • complexity and urgency requirements • integrates information from disparate and heterogeneous sources • intelligent computations at the back-end • integrates with the processes of the emergency call centers at the front-end • reuse of existing software design and components • increasing demand of ambulance service in Hong Kong but inadequate ambulances

  3. Stakeholders of the Emergency Route Advisory System Collect patient records Provides traffic information Find shortest path to venue Provides traffic information Find shortest path to venue Provide basic information of the accident Provides hospital information, collect number of patient Input the information collected Provides ambulance information

  4. Conceptual Model for Alerts in ERAS

  5. Example Urgency Level Description

  6. Conceptual Model for Transportation Network

  7. Road Network Exampleand its Representations Road1: Road Road2: Road Road3: Road Stop1: Bus Stop2: Bus Road4: Road Road5: Road Road1: Road Road2: Road Road3: Road J1: Junction J2: Junction H1: Hospital Road4:Road Road5: Road J3: Junction J4: Junction Road6: Road

  8. Deployment Diagram of the Whole System Civil Users Call Center Process Management Emergency Route Advisory System (ERAS) Fire service Route Advisory System (RAS) Emergency Route Search Agent Search Agent Police Caller Agent Alert Monitor Route database Traffic/Location Knowledge Base Location Agent Hospital Alert Management System (AMS) Traffic / Location Knowledge base Log database Admin Module Traffic Information Agent Traffic Information Agent Route Information Agent Emergency Vehicles route information Traffic condition Public Transportation Transportation Department

  9. AMS Mechanism Alert Management System (AMS) Outgoing Alerts Outgoing Alert Monitor Outgoing Alert Responses Incoming Alert Monitor Incoming Alerts Role Matching Module Incoming Alert Responses Process Execution Module Service Provider Monitoring Module Process / Alert Definition Module Execute Alerts Handlers Create Alerts System Workflow and Application Logic Database

  10. Typical life cycle of a route alert

  11. Route Finding Algorithm • Based on our HICSS38 paper on Route Advisory System (RAS) • Route-based Dijkstra’s algorithm (RD-algorithm) • traveling time is used as the cost metric • Heuristics • Search Area Limit • Cost Bound • Knowledge Based Finding

  12. ERAS Enhancements • Add the traffic conditions for a more accurate estimation of the traveling time for civil use • Reuse the software modules from the ERAS and feed the traffic condition information directly from the Transport Department website • This will not affect the performance of the ERAS and helps scale up • RAS can also serve as a backup system in case of disastrous break down of the ERAS

  13. User request under authorization policy system XML instance base 4 Document presentation User request XML presentation details 5 XML schemas and instances XML instance generator Session management module 3 2 Access control module 1

  14. Workflow of Emergency Call Center

  15. Advantages of ERAS • Improve the integration and automation of the current emergency call centers for the provision of quality services effectively and efficiently • Increases the efficiency of the ambulance call service and helps the tightly staffed emergency call centers through process automation • Reuse existing design and software (AMS, RAS, etc.) • Web Services technology provides the underlying open platform for integration

  16. AMS Advantages • Handles urgent and error-prone conditions and possible exception cases • Mediates variety of parties and personnel to liaise with • Automates the required communications and integrates the processes to minimize the delay and costs involved in inefficient manual calls and retry calls • Keeps track and monitors alerts • Captures the knowledge and experiences of the call center staff

  17. Future Work • Detailed performance evaluation of the system • Compare the service response time to the existing practice • Effects of the tuning parameters inside the ERAS order processing and turnaround time • How detail heuristics could be best formulated • Use questionnaires to evaluate the satisfaction of various stakeholders • Simulations for the scalability and robustness

  18. Question and Answer Thank you!

More Related