Use Case Tutorial - Fleet Management (5/7)


Published on

Part 5 of 7 of the Use Case Tutorial presented at DEBS'2009 in Nashville, TN

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Use Case Tutorial - Fleet Management (5/7)

  1. 1. Fleet Management EPTS Use Case
  2. 2. Contents • Project Objectives • Context Diagram • Conceptual Architecture • Application of Architecture to Use Case • Use Case Questionnaire Extract
  3. 3. Project Objectives • Derive the state of a fleet of freight vehicles • Provide more timely maintenance • Reduce risk • Reduce vehicle downtime • Decrease costs
  4. 4. Context Diagram Te lem etr rt y Ale Risk ion Schedule Event mm endat Reco Processing Network Visualization ty labili Avai Wor k Ord er ng uti Ro
  5. 5. Conceptual Architecture Capture Process Respond Environmental Monitoring System Enterprise Service Bus Physical Devices Security Applications Configuration Management Health Monitoring Industrial Control
  6. 6. Application • Capture – Acquire events from various disparate sources including trucks and enterprise systems • Process – Apply rules to events to build state of fleet and identify ‘derived events’ • Respond – Transmit derived events to interested users and systems
  7. 7. How does this translate into a use case? QUESTIONNAIRE EXTRACT
  8. 8. Short Description • Maintaining a model of the state of a fleet of freight vehicles • Derived from disparate sources such as EDI, asset management systems, on board sensors… • Notifications to drivers, maintenance depots, asset management systems… • Initial objective is to provide more timely maintenance and so reduce risks and costs • Long term leverage the infrastructure to derive more value from the various flows of events, e.g. common component failures
  9. 9. Inputs, Outputs and Users Question Response Sources Web services, MOM, real-time GPS and sensors via onboard Vehicle Management System over mobile IP, RDBMS (for data not exposed via web services) Input: types of data Vehicle reference data, driver info., maintenance schedules, maintenance depot locations, depot availability, intended destination, route, location, vehicle health indicators Central Aasset management system, SMS, Email, Sinks Dashboards, Reports Output: types of data Alerts of imminent failures, less urgent maintenance requests, dashboards showing fleet health and current alerts, etc., map based views of geospatial data Channels From Web Service, MOM and File adapters to State Engine, Dashboards and SMS Adapter all internal transport Users Fleet experts add rules, drivers respond to alert SMS, system operators (monitor health of solution itself), fleet managers monitor health of system and maintenance cost trends
  10. 10. Event Processing Question Response Filter Irrelevant data from the engine management system Enrichment Some data types enriched with geospatial data Transform Various EDI and XML forms into a standard internal format and various to go from standard to file, SMS and web services Aggregation Both current and historical health aggregated across fleet by various measures
  11. 11. Patterns Question Response Specific sequences Identified issues (e.g. need for maintenance) must be actioned in time. Correct sequence and timeliness of such action events is monitored. Trends over sequences Identify trends in truck telemetry as indicators of possible truck health issues. Query the state stored in a Current alerts and other current state that drive rule dashboards. Rules over a state Reported traffic problems (event or state) correlated with latest position of truck (event or state) and its intended route (state) to suggest re-routing. Problem detected by Vehicle Management System (event) indicates maintenance needed – compare with intended route (state) and maintenance depots (state) to identify where to fix it.
  12. 12. Reactions Question Response Describe reactions SMS and email for urgent maintenance problems, email and web service notification for less urgent. Dashboards to show current alerts and overdue alerts and overall fleet health. Email for overdue alerts.
  13. 13. Operational Question Response Scale Hundreds to tens of thousands of vehicles. Latency Latency is not a particular issue so of the order of seconds rather than milliseconds is acceptable (guaranteed processing is more important). Patterns For every vehicle there may be tens of patterns being detected so this equates to tens to hundreds of thousands across all vehicles. Some patterns may be ‘live’ for months (more akin to state). Variable Load EDI transactions may tend to arrive in large batches. Systems Management System should notify operators of its own health and identify performance hotspots.
  14. 14. Questions Matthew Cooper VP Development Event Center and Greentrac Products Event Zero