OMS in the GIS Family
OMS in the GIS Family John Long
Scott Koehler
Presentation Focus • Design Objectives • Integration Requirements • Implementation Highlights • Implementation Hurdles • Current Production Environment • Next Steps • Words to the Wise
Outage Management in GIS ***Benefits*** • No Data Conversion – One Network Data Model • Familiarity with Environment – Standardize on ArcMap • Improve Enterprise GIS Data – Dispatcher Feedback • Tap Existing Skill Set – GIS Admins/Users are Very Passionate
Outage Management in GIS ***Obstacles*** • Resistance to Change – Change Management: Key to Success • Burger King Mentality – “I Want it My Way” • OMS vs Operations Management – Ralph-isms • Data Integrity – Better Data, Better OMS
Project Objectives • Reduce Dispatch Center Call Volume • Improve Network and Crew Management • Minimize Restoration Time • Improve Safety and Customer Satisfaction • Leverage Enterprise GIS • Integrate Utility Systems – IVR, SCADA, CIS, Web • Track History and Generate Reports
Required Functionality • Switch Order Management • Crew Management • History Tracking • Tagging (Lock-out/Tag-out) • Cuts and Jumpers • Audible Alerts (“Wake Up!”) • Call Entry Source (IVR or CSR)
ArcMap UI • Visualize Outage and Switching Info – Group Layer (Cached) – Table Views and Layer Joins Calls • Affected Load Points • Outage/Switching Devices • Crew Assignments •
– Tracing • Circuit Sources • Outage Severity
Management UI • View Outage Info – Customers, Devices, Load Points – Start time, Restoration Time • Outage Management • Switch Order Management • Crew Management • Integrated with ArcMap • Independent of ArcMap
Web Access • Outage Summary Statistics – Calls, Customers, Crews, Outages • Historical Reporting – SAIDI, SAIFI, CAIDI, CAIFI • Call Entry – Customer Account – Trouble Type (No Power, Flickering, etc…) • Callback Requests – Specified Phone Number – Upon Outage Restoration
Outage Summary Statistics
CIS / OMS Interface • Customer Account Information • 2 Part 1-way Interface – Part 1 (Real-time CIS View) Oracle View to multiple CIS tables provides account status data – Part 2 (OMS Customer Table) Nightly update to customer account data stored in OMS Oracle table for improved performance
CIS / OMS Interface • Provide Data to Customer Service
Representatives – “Disconnected for Non-Payment” – “Member of Existing Incident” – “Estimated Time of Restoration” – “Critical Customer” – Specify Callback Phone Number
CIS / OMS Interface • Improved GIS Service Point Data with
“Unlinked Customers” Report – Accounts with No Spatial Reference – Service Points with No Associated Account
• GIS edit warning when deleting a service
point with an Associated CIS Account • Crew Member and Truck Data Manually Updated by Dispatch Manager
IVR / OMS Integration • Incoming Customer Outage Calls and
Customer Callbacks • 2-way Interface (IVR Account Number Incident Status Submit Call Get Next Callback Callback Info Callback Result
OMS)
IVR / OMS Integration • IVR and OMS on Independent Servers • IVR Operates on Multiple Telephony Ports • IVR Sends Requests to Executable • •
Program via Command Line Executable Makes Appropriate Calls to OMS .Net Methods Executable Sends Responses to IVR via Command Line
Outage Calls
SCADA / OMS Integration • Trip and Close Status of Circuit Breakers
and Load Break Switches • 1-way Interface (SCADA
OMS)
Breaker Trip (Lock-outs only) Breaker Close • SCADA ODA Interface Sends Breaker Status Data to Oracle Table in OMS Oracle instance • Table Triggers Make Appropriate Calls to OMS .Net Methods
Talking Maps
Bad Data
Where is the Fuse???
Better Management • Outage – Ability to Roll-up, Prediction • Switching – Switch Orders in Advance, On the Fly • Crews – Assignments, Availability, Visual Reference • Tags – Placement Info (Safety)
Reporting Key Reliability Indicator (Better Reporting might not be Pretty!)
Issues • Message Queue Permissions (Security) • Multicasting on all Routers/Data Switches • Delays with Vendor Coordination • Training a 24hr Shift Department • Lack of Test Environment • “Network I/O Error” • Oracle Performance Tuning (Analyzing)
Next Steps • Short Term – Replication (One-way) – SCADA Outage Restoration – “Cause of Outage” Info to CSRs – Future Work Required • Long Term – Prediction on Steroids (Geography/Volume) – Work Management/AMR/AVL Integration – Dispatcher Editing – Get Ralph to be an Expert
Words to the Wise • Get Commitment from All Software • • • •
Vendors for Full System Integration Get Buy-in from Operations Group Provide Dispatchers Access to GIS prior to OMS implementation (i.e. Wall Map) Create Trust with Operations Group by Correcting Data Promptly Work to Validate GIS Geometric Network Data and Ensure Proper Traceability
?
?
? Questions
? ? ?
? ?
[email protected] [email protected]
?
Scott Koehler
Presentation Focus • Design Objectives • Integration Requirements • Implementation Highlights • Implementation Hurdles • Current Production Environment • Next Steps • Words to the Wise
Outage Management in GIS ***Benefits*** • No Data Conversion – One Network Data Model • Familiarity with Environment – Standardize on ArcMap • Improve Enterprise GIS Data – Dispatcher Feedback • Tap Existing Skill Set – GIS Admins/Users are Very Passionate
Outage Management in GIS ***Obstacles*** • Resistance to Change – Change Management: Key to Success • Burger King Mentality – “I Want it My Way” • OMS vs Operations Management – Ralph-isms • Data Integrity – Better Data, Better OMS
Project Objectives • Reduce Dispatch Center Call Volume • Improve Network and Crew Management • Minimize Restoration Time • Improve Safety and Customer Satisfaction • Leverage Enterprise GIS • Integrate Utility Systems – IVR, SCADA, CIS, Web • Track History and Generate Reports
Required Functionality • Switch Order Management • Crew Management • History Tracking • Tagging (Lock-out/Tag-out) • Cuts and Jumpers • Audible Alerts (“Wake Up!”) • Call Entry Source (IVR or CSR)
ArcMap UI • Visualize Outage and Switching Info – Group Layer (Cached) – Table Views and Layer Joins Calls • Affected Load Points • Outage/Switching Devices • Crew Assignments •
– Tracing • Circuit Sources • Outage Severity
Management UI • View Outage Info – Customers, Devices, Load Points – Start time, Restoration Time • Outage Management • Switch Order Management • Crew Management • Integrated with ArcMap • Independent of ArcMap
Web Access • Outage Summary Statistics – Calls, Customers, Crews, Outages • Historical Reporting – SAIDI, SAIFI, CAIDI, CAIFI • Call Entry – Customer Account – Trouble Type (No Power, Flickering, etc…) • Callback Requests – Specified Phone Number – Upon Outage Restoration
Outage Summary Statistics
CIS / OMS Interface • Customer Account Information • 2 Part 1-way Interface – Part 1 (Real-time CIS View) Oracle View to multiple CIS tables provides account status data – Part 2 (OMS Customer Table) Nightly update to customer account data stored in OMS Oracle table for improved performance
CIS / OMS Interface • Provide Data to Customer Service
Representatives – “Disconnected for Non-Payment” – “Member of Existing Incident” – “Estimated Time of Restoration” – “Critical Customer” – Specify Callback Phone Number
CIS / OMS Interface • Improved GIS Service Point Data with
“Unlinked Customers” Report – Accounts with No Spatial Reference – Service Points with No Associated Account
• GIS edit warning when deleting a service
point with an Associated CIS Account • Crew Member and Truck Data Manually Updated by Dispatch Manager
IVR / OMS Integration • Incoming Customer Outage Calls and
Customer Callbacks • 2-way Interface (IVR Account Number Incident Status Submit Call Get Next Callback Callback Info Callback Result
OMS)
IVR / OMS Integration • IVR and OMS on Independent Servers • IVR Operates on Multiple Telephony Ports • IVR Sends Requests to Executable • •
Program via Command Line Executable Makes Appropriate Calls to OMS .Net Methods Executable Sends Responses to IVR via Command Line
Outage Calls
SCADA / OMS Integration • Trip and Close Status of Circuit Breakers
and Load Break Switches • 1-way Interface (SCADA
OMS)
Breaker Trip (Lock-outs only) Breaker Close • SCADA ODA Interface Sends Breaker Status Data to Oracle Table in OMS Oracle instance • Table Triggers Make Appropriate Calls to OMS .Net Methods
Talking Maps
Bad Data
Where is the Fuse???
Better Management • Outage – Ability to Roll-up, Prediction • Switching – Switch Orders in Advance, On the Fly • Crews – Assignments, Availability, Visual Reference • Tags – Placement Info (Safety)
Reporting Key Reliability Indicator (Better Reporting might not be Pretty!)
Issues • Message Queue Permissions (Security) • Multicasting on all Routers/Data Switches • Delays with Vendor Coordination • Training a 24hr Shift Department • Lack of Test Environment • “Network I/O Error” • Oracle Performance Tuning (Analyzing)
Next Steps • Short Term – Replication (One-way) – SCADA Outage Restoration – “Cause of Outage” Info to CSRs – Future Work Required • Long Term – Prediction on Steroids (Geography/Volume) – Work Management/AMR/AVL Integration – Dispatcher Editing – Get Ralph to be an Expert
Words to the Wise • Get Commitment from All Software • • • •
Vendors for Full System Integration Get Buy-in from Operations Group Provide Dispatchers Access to GIS prior to OMS implementation (i.e. Wall Map) Create Trust with Operations Group by Correcting Data Promptly Work to Validate GIS Geometric Network Data and Ensure Proper Traceability
?
?
? Questions
? ? ?
? ?
[email protected] [email protected]
?
