Connecting through the OMS
•Download as PPTX, PDF•
1 like•124 views
CoServ has been preparing for the future by adding several connections to their OMS. These connections have evolved over the years and now include: SCADA-initiated device status, outage creation and status through IVR, and web-based outage tools for reporting and status. This session will cover the evolution and future plans for utlizing the information from OMS and the business value the existing tools have made for CoServ and their customers.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Connecting through the OMS
Similar to Connecting through the OMS (20)
More from SSP Innovations
More from SSP Innovations (20)
Recently uploaded
Recently uploaded (20)
Connecting through the OMS
- 1. 2106 Esri GeoConX Conference Connecting through the OMS October 19, 2016
- 2. Mike Young | CoServ • GIS Analyst III • ArcGIS and ArcFM • GIS Data/Business Analysist • GIS Workflow Analysist Jeff Mertz | SSP Innovations • Director of Technology • Principal Consultant • GIS Integrations Introductions
- 3. About CoServ, MAY 1937: Denton County Electric Cooperative is chartered. JANUARY 1998: Denton County Electric begins doing business as CoServ, an abbreviation of “Cooperative Services.” JULY 1998: CoServ Gas established. APRIL 2004: 100,000th meter installed, making CoServ the second- largest electric cooperative in Texas. SEPTEMBER 2015: Official dedication ceremony held for CoServ Solar Station. CoServ begins offering Members a solar rate option. In July this year: we set a combined total of 300,000 electric and gas meters. • Established in 1937 • Headquarters: Corinth, TX • Serve several Counties in North Central Texas
- 4. Mike Young | CoServ • GIS Analyst III • ArcGIS and ArcFM • GIS Data/Business Analysist • GIS Workflow Analysist Jeff Mertz | SSP Innovations • Director of Technology • Principal Consultant • GIS Integrations Introductions
- 5. About Us…. • Eleven-year old GIS consulting company • Back-to-back Esri EPC Award Winner • Work exclusively in the U.S. utility/telecom industries • 100+ years of combined utility & telecom experience • 100% aligned with Esri platform strategy • Over 80 clients and growing • Industry-leading reputation for quality, successful solutions to requirements
- 6. Business Drivers • Expanding the use of OMS data to better serve internal and external customers • Upgrade older systems • With the new system, system planners can monitor and manage system without overloading, use the new web interface.
- 7. The Solutions • Existing file-based ingest system IVR Call input records IVR response records OMS Windows service
- 8. The Solutions • New interface introduced in 2014 IVR IVR OMS Web service • Account Lookup • Report Outage • Outage Status
- 9. The Solutions • Public-facing Outage Map – 2015 • Shows high-level outage and affected customer counts • OMS extract and push to 3rd party service • Customer portal - 2016 • Report new outages • Leverages existing IVR to OMS interface Outage Visualization and Reporting
- 10. 10 Forward Progress - 2016
- 11. The Solutions • Old system – circa 2010 • Based on database triggers and Windows-based polling process. (Processed only 1 outage per minute) • Complicated device lookup routines SCADA Device Status to OMS Device status file OMS Windows polling service SCADA database
- 12. The Solutions • New system - 2016 • MultiSpeak 4.1 based web service SCADA Device Status to OMS SCADA OMS Web service SCADADeviceUpdateStatus PingURL
- 13. Benefits • Increased productivity • Increased consumer satisfaction • Better communication • With consumers • With dispatchers • Quick access to pertinent, detailed information • Less applications to train on and maintain
- 14. The Future • OMS to SCADA Integration • Sending device status information to the SCADA system to complete the two-way communication • Non-SCADA controlled devices • Fuses • Switches • Elbows • Gang-operated by phase
Editor's Notes
- Mike
- Mike
- Jeff
- Jeff
- Mike Customers like – System planners, engineers that use Milsoft, Responder, Coserv Members. New web interface that can pick up multiple incidents and report form other sources. In the future smart meters can communicate with directly with the web interface and create a ticket just a small amount of modifications.
- Jeff – the older interface was file based, which Mike mentioned previously about antiquated interfaces The calls were written to a file with customer and outage information Windows service picked up the file and processed it to the OMS Windows service wrote out a file to be picked up by the IVR system
- Jeff – Web Services Customer outage reporting Existing outage status Extensible for future methods
- Mike
- Jeff What were the Antiquated System Interfaces? – Originally all events were written to a table. The table would be exported to a location. The old system would go through and look at that table every 60 seconds. The system could only process one event at a time and only one per minute. So if 2 events happened at the same time the trigger was only able to pick up one and would have to wait a full minute to go back a pick up the second one. Now imagine if you had 60 events or outages, it would take a full 60 minutes (hour) just for all of those to be processed one minute at a time. Complicated look-up logic -> the code had to make several calls into the GIS to retrieve the feature id and object id of the device in order to pass it to the OMS. The new interface is passed both key pieces of information and now just sends to the OMS without additional lookup
- Jeff What were the Antiquated System Interfaces? – Originally all events were written to a table. The table would be exported to a location. The old system would go through and look at that table every 60 seconds. The system could only process one event at a time and only one per minute. So if 2 events happened at the same time the trigger was only able to pick up one and would have to wait a full minute to go back a pick up the second one. Now imagine if you had 60 events or outages, it would take a full 60 minutes (hour) just for all of those to be processed one minute at a time. Complicated look-up logic -> the code had to make several calls into the GIS to retrieve the feature id and object id of the device in order to pass it to the OMS. The new interface is passed both key pieces of information and now just sends to the OMS without additional lookup
- Mike
- Mike – get more info from Matt / Joshua ?