ABB Annual Users’ Group Meeting © ABB Ltd. - 1 - August 27 – 31, 2006 Crew Dispatch Martin Bass Crew Dispatch Topics © ABB Inc. - 2 - Review existing functionality (2006 Release 3) Voice radio dispatch Mobile crew integration Functionality under development Mobile crew integration Dispatch Scheduling Existing Crew Dispatch Functionality © ABB Inc. - 3 - Crew must be manually identified by dispatcher, either From OMI Crews - Status list From OMI Available Crews list From netCADOPS Available Crews list © ABB Inc. - 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 © ABB Inc. - 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 How Crews Are Tied to Login Login determines sub area Crew tied to operations center - © ABB Inc. - 6 See sub area diagram See operations center diagram Sub Area Hierarchy – Set at Ormap Login Highest Level Sub Area e.g Entire Area Child Sub Area 1 e.g. South © ABB Inc. - 7 - Grandchild Sub Area 1 e.g. South East Child Sub Area 2 e.g. North East Grandchild Sub Area 2 e.g. South West Child Sub Area 3 e.g. North West Feeder/Substation/Operations Center Crew has Home Operations Center Crew has Work Operations Center Region 1 © ABB Inc. - 8 - District 1 Operations Center 1 District 2 Operations Center 2 Crew 1 Work Op Center Substation 1 Substation 2 Substation 3 Feeder 1 Feeder 2 Feeder 3 Feeder 4 Feeder 5 Feeder 6 District 3 Crew 1 Home Op Center Crew 2 Home Op Center Operation Center Can Have a Sub Area Highest Level Sub Area e.g Entire Area Child Sub Area 1 e.g. South Grandchild Sub Area 1 e.g. South East Child Sub Area 2 e.g. North East Grandchild Sub Area 2 e.g. South West Region 1 District 1 North West Op Center District 2 South West Op Center Crew 1 Work Op Center Substation 1 Substation 2 Substation 3 Feeder 1 Feeder 2 Feeder 3 Feeder 4 Feeder 5 Feeder 6 © ABB Inc. - 9 Child Sub Area 3 e.g. North West District 3 Crew 1 Home Op Center Crew 2 Home Op Center © ABB Inc. - 10 - Crew Status Dialog Set Operation Center Work operation center can be set in netCADOPS Work operation center can be changed in OMI © ABB Inc. - 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 © ABB Inc. - 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 © ABB Inc. - 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 © ABB Inc. - 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 © ABB Inc. - 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 © ABB Inc. - 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 © ABB Inc. - 17 - Dispatch From netCADOPS Available Crews netCADOPS Available Crews List filters out suspended crews automatically User can filter list by work operations center © ABB Inc. - 18 - Dispatch From netCADOPS Available Crews User can also filter list by any other criteria, such as Crew Type Multiple filter criteria are supported © ABB Inc. - 19 - netCADOPS Available Crews - Summary No distance calculation currently Size of list can be reduced by multiple filtering criteria List automatically excludes suspended crews © ABB Ltd. - 20 - Possible Enhancements Crew Dispatch Possible Enhancements © ABB Inc. - 21 - 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? Possible Enhancements, continued Available Crews Filtering What criteria to use? Operations Center Other (crew region, crew department?) Backup geographical area needed out of hours © ABB Inc. - 22 - Combination of several geographical areas to widen coverage Backup Op Centers North Northwest Northeast Southwest Southeast © ABB Inc. - 23 - South Available Crews Filtering © ABB Inc. - 24 - 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) © ABB Ltd. - 25 - Overview of Mobile Integration done at PG&E and CPS Crew Dispatch 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: © ABB Inc. - 26 - Phone number, meter number and customer name Assignment Status © ABB Inc. - 27 - Receive assignment status updates from MDT: MDT Queued (PG&E only) WAITRESP REJECTED DEASSIGNED ASSIGNED ENROUTE ARRIVED COMPLETE 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 © ABB Inc. - 28 - One order modify is sent to MDT with new location of one of the outages 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 © ABB Inc. - 29 - 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 Trouble Call and Non-Cust Call Completion © ABB Inc. - 30 - New functionality added to trouble reports and noncustomer calls Ability to add cause codes and equipment codes to trouble reports Ability to add cause codes and equipment codes to noncustomer calls Cause/equipment codes can be entered from MDT for these calls Cause/equipment codes can also be entered from OMI detail dialogs © ABB Inc. - 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 © ABB Inc. - 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) 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 Unavailable - © ABB Inc. - 33 If suspended, crew status reverts to correct value (Unavailable in MDS). Crew status is unavailable. All orders sent to these crews will be NACKED Create Order from MDT © ABB Inc. - 34 - MDT user can create Customer Call, if customer exists. If trouble report exists for customer, trouble report will be updated Non-customer Call © ABB Ltd. - 35 - Functionality Under Development Crew Dispatch Crew Scheduling R&D Goal: Approach: © ABB Inc. - 36 - Provide scheduling and supporting data structures to manage outages and service work 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 Crew Scheduling R&D Orders Appointments Resources Scheduler Schedule Auto Dispatch © ABB Inc. - 37 - Manual Dispatch Crew Assignments Constraints Scheduling – Building on Existing Functions Orders: Outages Non-customer calls Appointments: Resources: Crews Vehicles Equipment Constraints: - © ABB Inc. - 38 Service calls (aka referrals) Crew rosters (new) Scheduler © ABB Inc. - 39 - 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 © ABB Inc. - 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 Crew Scheduling - Dispatch © ABB Inc. - 41 - 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 © ABB Inc. - 42 - Crew Rosters Shifts Overtime Crew assembly Crew callout Moving employees between crews © ABB Inc. - 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 © ABB Inc. - 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 Example Shifts Shift Day Start Time End Time Day Mon-Fri 8:00 am 5:00 pm Night 1 Mon-Thurs 5:00 pm 6:00 am Night 2 Fri-Sun 5:00 pm 6:00 am Shifts will also honor holidays, in separate holiday schedule © ABB Inc. - 45 - Does this give you the flexiblity needed? For example, do shifts work 4 days on, 4 days off? Example of Employee Roster Employee Shift Type Start End Martin Day Working January 1, 2006 December 31, 2006 Nonworking August 11, 2006, 5:00 pm August 20, 2006, 8:00 am Working January 1, 2006 January 4, 2006 NonWorking January 5, 2006 January 7, 2006 Working January 8, 2006 January 11, 2006 Martin Rafael Night 1 Rafael © ABB Inc. - 46 - Rafael Night 1 © ABB Inc. - 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 Other Issues © ABB Inc. - 48 - Do rosters need to be integrated into ETR system, or should they be maintained separately? Mobile Crew Map Presentation Project Goal: 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: - © ABB Inc. - 49 Provide fully integrated OMS and Mobile Workforce Management System, with tabular and geographical mobile data user interface Provide more information to field crews to improve their productivity Mobile Data Integration Approach Outage Management API Mobile Dispatch Store and Forward Wireless WAN Store and Forward Mobile Adapter Tabular User Interface © ABB Inc. - 50 - API Mobile Map User Interface Mobile Data R&D Project Scope Provide capability to view assignment information on geographic display on mobile laptop © ABB Inc. - 51 - MDT user can see their assignments in geographic view Force outage upstream/downstream from MDT Outage assignment form will show upstream protective device. Downstream devices can change dynamically and may not show these? Add button to force outage upstream/downstream from MDT Order modify will be sent back to MDT Show location of other crews on mobile laptop MDT user will zoom into area of interest and press button Current position of crews will be sent from server to MDT for display Mobile Data R&D Project Scope © ABB Inc. - 52 - Show current switch status and tags on mobile laptop MDT user will zoom into area of interest and press button Server will send list of tags and switches in abnormal state for display on geographical viewer Allow entry of damage assessment on mobile laptop User will select location of damage using GPS User enters damage information into tabular MDT display: Damage type (pole down, transformer replacement, etc) Quantity damaged Similar entry forms will be provided in NM DMS