Crew Callout Martin Bass

1. Crew CalloutMartin Bass ABB Annual Users’ Group Meeting August 27 – 31, 2006

2. Crew Callout • Crew Callout Module currently under development • Select an Outage and call up OMI Available Crews dialog • Select Create Callout action

3. OMI Crew Callout • Crew Callout dialog is displayed • Fill out required information: • Troubleman (determines type of callout) • If Troubleman checked, fill out • Substation • If Troubleman not checked, fill out • Crew Region (geographical area for assignment) • Department (type of work) • Crew type • Estimated work hours

4. Crew Callout • When callout is created, message is sent to IVR to initiate callout for each employee • Only one callout per crew region is performed at a time • Other callouts for the same region are queued • Callout status is monitored via netCADOPS displays

5. netCADOPS Menus • New netCADOPS menu for Crew Callout status • View callout in progress • Logging of callouts

6. Crew Callouts In Progress

7. New netCADOPS Crew Forms • New forms added to maintain crew callout tables

8. Crew Region • Defines a ‘dispatch area’ • Distinct from existing sub areas and operation centers (no relationship whatsoever)

9. Crew Department • Defines a further breakdown of crew region into one or more crew departments

10. Crew Department Alternates • Defines a backup department for a given department if an eligible employee cannot be found • Priority defines which order alternates should be used in, if multiple alternates for a given department • Current implementation only substitutes one department

11. Defining Skill Sets for Crew Types • Each crew type can be defined to require one or more employees with a given skill set • In example, Line crew needs: • 1 Crew Leader • 3 Linemen • 4 Helpers

12. Alternate Jobs • Each employee has a primary job • Primary job has one or more backup jobs, with a priority

13. Callout List • List of employees, with priorities, to be called out • Populated by utility, using stored procedure API • Contains • Crew Region • Crew Department • Substation ID • Primary employee skill • Callout Priority

14. Callout Process • When callout is created, message is sent to IVR to initiate callout for each employee • Only one callout per crew region is performed at a time • Other callouts for the same region are queued • Callout status is monitored via netCADOPS displays • Each employee is called in turn • Employees are no available to be called if they currently are working on an existing assignment • Calls are sent to the IVR via an EAI interface • The callout interface waits for a response from the IVR for a configurable amount of time

15. Callout Process • A netCADOPS status crew callout screen displays the current callouts and their time periods • If the callout response shows employee is unavailable • Employee will be marked in NM DMS as unavailable • Employee will not be called until the available state is changed back to available by an operator • A list of questions and answers will be received from the IVRU and stored in a DMS table for logging purposes • A user preference defines how many times the DMS calls an employee before doing department substitution

16. Callout Process • The result of each call to an employee is saved in the call log table • Substation callouts are performed based on pre-defined list of trouble men who will be called for each substation • If the callout crew is not successfully created, the callout is marked as incomplete and can be manually completed • When new members of the crew are manually found, the operator has the ability to manually add crew members and must manually mark the crew when it is completed from OMI

17. Crew Callout Message

18. Callout Response Message

19. Callout Auditing • Log tracks responses to callout requests