1 / 53

Crew Dispatch Martin Bass

Crew Dispatch Martin Bass. ABB Annual Users’ Group Meeting August 27 – 31, 2006. Crew Dispatch Topics. Review existing functionality (2006 Release 3) Voice radio dispatch Mobile crew integration Functionality under development Mobile crew integration Dispatch Scheduling.

ivy
Télécharger la présentation

Crew Dispatch Martin Bass

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. Crew DispatchMartin Bass ABB Annual Users’ Group Meeting August 27 – 31, 2006

  2. Crew Dispatch Topics • Review existing functionality (2006 Release 3) • Voice radio dispatch • Mobile crew integration • Functionality under development • Mobile crew integration • Dispatch • Scheduling

  3. Existing Crew Dispatch Functionality • Crew must be manually identified by dispatcher, either • From OMI Crews - Status list • From OMI Available Crews list • From netCADOPS Available Crews list

  4. Drag Outage and Drop Onto Crew to Assign • Left click outage on outage status dialog • Drag outage and drop onto crew status dialog • ‘Fast Assign’ is done automatically • But list contains many crews

  5. Crew Status Dialog Filter by Operation Center • Can Filter crew status dialog by Work Operation Center of crew • Operation center determined by Ormap login of user

  6. How Crews Are Tied to Login • Login determines sub area • See sub area diagram • Crew tied to operations center • See operations center diagram

  7. Sub Area Hierarchy – Set at Ormap Login

  8. Feeder/Substation/Operations Center • Crew has Home Operations Center • Crew has Work Operations Center

  9. Operation Center Can Have a Sub Area

  10. Crew Status Dialog Set Operation Center • Work operation center can be set in netCADOPS • Work operation center can be changed in OMI

  11. Crew Status Dialog Filter Logged Off Crews • Toggle to filter logged off crews • Requires login status from MDT • Only MDT-equipped crews will be filtered

  12. Filtering non-MDT Crews • Possible to change crew availability by suspend/resume from Ormap or OMI Status – Crews dialog • However, currently Status – Crews dialog not filtered by suspend/resume • Could potentially handle non MDT-equipped crews to filter out suspended crews due to logoff suspend reason

  13. Crews – Status Filter by Crew ID • Filter box in Crews – Status list allows list to be filtered by characters entered • Can set up crew IDs to reflect operation centers

  14. Crew Status Dispatch - Summary • Size of list can be reduced by logging into reduced area in Ormap • Not helpful if user always logs into every AOR • Filtering by logoff status can be useful with MDT • Can set up crew IDs to help with filtering this list • List can also be sorted by criteria such as: • Backlog • Feeder/Substation

  15. Dispatch From OMI Available Crews • Second method of dispatch is via OMI Available Crews • Dialog is populated dynamically • Shows distance of each crew from proposed assignment • Dispatcher can filter by crew ID • Dispatcher can sort by distance or any one column

  16. OMI Available Crews - Summary • Useful if used with distance calculation • Size of list can only be reduced by filtering by crew ID • Otherwise, shows all crews • Only one sort order

  17. Dispatch From netCADOPS Available Crews • netCADOPS Available Crews List filters out suspended crews automatically • User can filter list by work operations center

  18. Dispatch From netCADOPS Available Crews • User can also filter list by any other criteria, such as Crew Type • Multiple filter criteria are supported

  19. netCADOPS Available Crews - Summary • No distance calculation currently • Size of list can be reduced by multiple filtering criteria • List automatically excludes suspended crews

  20. Crew Dispatch Possible Enhancements

  21. Possible Enhancements • Automatically filter OMI Available Crews list to remove suspended crews • Should it show crews on a break (non-logoff suspend reason)? Yes • netCADOPS does not make this distinction currently • Based on suggestions from Focus Group: • Automatically filter OMI and netCADOPS available crews list by proposed assignment • Same filtering could not be applied to Status – Crews, unless an assignment is first selected • But do we need two Crews windows?

  22. Possible Enhancements, continued • Available Crews Filtering • What criteria to use? • Operations Center • Other (crew region, crew department?) • Backup geographical area needed out of hours • Combination of several geographical areas to widen coverage

  23. North South Backup Op Centers Northeast Northwest Southeast Southwest

  24. Available Crews Filtering • Could add filtering radio buttons (in order of increasing list size): • Filter to show op center crews for assignment (default) • Filter to show op center and backup op center crews • Do not filter by op center • Button to initiate callout if list is still empty (planned for Release 4)

  25. Crew Dispatch Overview of Mobile Integration done at PG&E and CPS

  26. Outage Assignments • Send outage assignments directly to Mobile Data Terminal (MDT) from NM DMS • Outages and non-customer calls dispatched to a specific crew in NM DMS, via OMI Crew Status dialog • Can also dispatch from available crews or netCADOPS • Crew list is maintained in two places – Advantex and NM DMS • Could be maintained in Advantex only, and use Crew API to synchronize systems • Order is sent to Advantex via MQ-Series queue • Order is created in Advantex and sent to MDT • Outage order includes the first five trouble reports: • Phone number, meter number and customer name

  27. Assignment Status • Receive assignment status updates from MDT: • MDT Queued (PG&E only) • WAITRESP • REJECTED • DEASSIGNED • ASSIGNED • ENROUTE • ARRIVED • COMPLETE

  28. Outage Rollup • Update assignments automatically to MDT as outage engine rolls outages up • If two outages are combined • One order modify is sent to MDT with new location • One order cancel is sent to MDT • If outage rolls down and splits • One order modify is sent to MDT with new location of one of the outages

  29. Outage Verify and Complete • Verify outages from MDT • User can verify an outage from the MDT directly • Verify operates device in NM DMS • Complete outages from MDT • User can enter completion information from MDT, including • Estimated restoration time • Cause codes • Equipment codes • Outage can be restored from MDT • Restore operates device in NM DMS, including removing line cuts • Partial restores not supported

  30. Trouble Call and Non-Cust Call Completion • New functionality added to trouble reports and non-customer calls • Ability to add cause codes and equipment codes to trouble reports • Ability to add cause codes and equipment codes to non-customer calls • Cause/equipment codes can be entered from MDT for these calls • Cause/equipment codes can also be entered from OMI detail dialogs

  31. Order Completion and Referrals • MDT user can complete assignment without restoring outage • MDT user can create a referral for follow-up work • MDT user can also reject an assignment and create a referral

  32. Login Status • Display/update crew login status in NM DMS, as entered from MDT • Status – Crews dialog shows: • MDT Enabled – yes/no • MDT Login Status • MDT Login Date • MDT In Range – yes/no (PG&E only) • MDT In Range Date (PG&E only)

  33. MDT Login Status • Status received from MDT • Sign On • MDT_LOGIN status field updated to Y • MDT_LOGIN_DATE changed to specified time. • Sign Off or Forced Logoff • MDT_LOGIN status field updated to N • MDT_LOGIN_DATE set to NULL. • Available • If suspended, crew status reverts to correct value (Unavailable in MDS). • Unavailable • Crew status is unavailable. All orders sent to these crews will be NACKED

  34. Create Order from MDT • MDT user can create • Customer Call, if customer exists. If trouble report exists for customer, trouble report will be updated • Non-customer Call

  35. Crew Dispatch Functionality Under Development

  36. Crew Scheduling R&D • Goal: • Provide scheduling and supporting data structures to manage outages and service work • Approach: • Develop key components that can be used either standalone or integrated with third party scheduling tools • Benefits: • More efficient utilization of crews • Faster assignment of crews to outages and service work

  37. Appointments Resources Constraints Orders Scheduler Schedule Manual Dispatch Auto Dispatch Crew Assignments Crew Scheduling R&D

  38. Scheduling – Building on Existing Functions • Orders: • Outages • Non-customer calls • Appointments: • Service calls (aka referrals) • Resources: • Crews • Vehicles • Equipment • Constraints: • Crew rosters (new)

  39. Scheduler • Scheduler accepts the following inputs: • Short term orders • Appointments • Resources • Constraints • Scheduler allocates orders and appointments to resources (crews), based on constraints, such as shifts, skill sets, etc. • Output from the scheduler is a schedule • Scheduler does not actually send the assignments to the crews • Schedule can be several days or even weeks into the future • Assignments only sent to crew on day that work is scheduled to begin

  40. Crew Scheduling – Schedule • The schedule is the output from the scheduling algorithm • The schedule is a list of orders and appointments that are allocated to resources • Crew assignments • Proposed dates and times

  41. Crew Scheduling - Dispatch • Manual crew dispatch: • Dispatcher manually selects an item from schedule • Dispatcher sends work to the crew, either via voice radio or by electronic means • Non-scheduled orders may also be directly sent to the crew by the dispatcher. • Automatic crew dispatch: • Items are automatically selected from the schedule and sent to the crew electronically • Non-scheduled orders may also be sent directly to the crew by the auto-dispatch module

  42. Crew Rosters • Shifts • Overtime • Crew assembly • Crew callout • Moving employees between crews

  43. Employee Rosters • Maintain employee roster in NM DMS • Could rely on MDT (or other) system for rosters • Either link directly as needed • Or update periodically

  44. Employee Rosters in NM DMS • For each employee, need a calendar • Need start time/date, end time/date for each work period (which may not be a day) • Tradeoff between flexibility and manageability • Assign employee to a shift for a period of time, with ability to override

  45. Example Shifts • Shifts will also honor holidays, in separate holiday schedule • Does this give you the flexiblity needed? • For example, do shifts work 4 days on, 4 days off?

  46. Example of Employee Roster

  47. Use of Employee Rosters for Manual Dispatch • NM DMS could update Status – Crews and Available Crews with employee roster, based on time • Could also use roster from external system to do same • If crew leader shift time has expired, available crews could filter out crew for new assignments

  48. Other Issues • Do rosters need to be integrated into ETR system, or should they be maintained separately?

  49. Mobile Crew Map Presentation Project • Goal: • Provide fully integrated OMS and Mobile Workforce Management System, with tabular and geographical mobile data user interface • Approach: • Use partners wherever possible to provide functionality • Expand upon initial work done for PG&E and CPS projects • Use APIs and middleware to allow different vendor functions to be plugged in • Benefits: • Provide more information to field crews to improve their productivity

  50. Outage Management API Mobile Dispatch Store and Forward Wireless WAN Store and Forward Mobile Adapter Tabular User Interface API Mobile Map User Interface Mobile Data Integration Approach

More Related