Recommended
More Related Content
Similar to EPRI Field Force Data Visualization V 3.0
Similar to EPRI Field Force Data Visualization V 3.0 (20)
EPRI Field Force Data Visualization V 3.0
- 1. Field Force Data Visualization Leveraging Augmented Reality and The Common Information Model John Simmins Senior Project Manager May 10, 2012
- 2. Traditional Point-to-Point Integration Characteristics • Complex environment • High integration costs • High maintenance costs • Message tracking – non- existent • Guaranteed delivery – non-existent • Frequent “broken” interfaces There is no “leverage” of the information being exchanged © 2012 Electric Power Research Institute, Inc. All rights reserved. 2
- 3. Typical Standards Base Integration Characteristics • Enterprise semantic model • Little or no custom code • Lower integration cost • Lower maintenance costs • Message tracking • Guaranteed delivery • Reliable Messages are agnostic of their origins © 2012 Electric Power Research Institute, Inc. All rights reserved. 3
- 4. EPRI’s Polaris Program – Driving Technology Innovation Report Number - 1024696 “Withsuitable application code and or input signal conditioning, PED’s have the potential for:” • Power quality monitoring • Demand response management • Locating arcing utility hardware • Magnetic and electric field sensing • Handheld multi-meter applications • Hardware condition and security monitoring • Vibration and thermal noise measurement • Vehicle charging station mapping • Asset tracking and GPS locating • Data acquisition/storage/transmittal • Training and portal of instructional documents to the field © 2012 Electric Power Research Institute, Inc. All rights reserved. 4
- 5. Field Force Data Visualization The Issue: • Access to real-time data has not progressed • Getting data to the field is too expensive • Getting the data from the field is too cumbersome • The applications don’t interop • Data is not accurate The Impact: • Potentially dangerous situation. • SAIDI/SAIFI numbers unnecessarily high. Multiple applications in the field isn’t a great leap forward © 2012 Electric Power Research Institute, Inc. All rights reserved. 5
- 6. Field Force Data Visualization EPRI Solution: • Build on a light weight, inexpensive platform. • Leverage augmented reality capabilities. • Messaging using CIM to multiple systems. • Two way communications to back office systems. Value: • Lower cost of field force automation. • Puts accurate data where it needs to be. • Correct inaccurate GIS data. • Spurs CIM development. © 2012 Electric Power Research Institute, Inc. All rights reserved. 6
- 7. Putting it all Together - Supplemental Goal • Empower the field work force with better information than currently available • Port back-office data to the field workers Deliverable • Proof of Concept • Design Specification Benefits • Open source application of CIM and MultiSpeak • Faster diagnostics at lower costs Developing the Concept and Technology © 2012 Electric Power Research Institute, Inc. All rights reserved. 7
- 8. Field Force Data Visualization - Features Crew location and Asset Information graphic circuit •Identify asset representation •Maintenance •Create work request •Call SOPs One line circuit Links to other tools diagram Create work request Status assigned work in the field in the field Other Potential Features: RFID, Bar Code, shape recognition © 2012 Electric Power Research Institute, Inc. All rights reserved. 8
- 9. Open Source Layered Approach • Work tasks are broadly defined • With CIM / MultiSpeak, the data may be obtained from multiple data repositories and server locations • Open Source primary layer • Can be used across department Tiered Approach Means More Power and Flexibility © 2012 Electric Power Research Institute, Inc. All rights reserved. 9
- 10. What About Security? • Platform (iOS) Security – Low level system calls not allowed – App isolation – each app in its own “sandbox” – Library randomization – Encrypted drive – Password protected • Network Security – SSL/TLS with X.509 certificates • Application Security – Encrypted data exchanges – Strong log in © 2012 Electric Power Research Institute, Inc. All rights reserved. 10
- 11. Benefits • Inexpensive to deploy • Inexpensive to maintain • Applications – Damage assessment – Asset information access – Switching communications – Work-order information flow – Real-time system status validation – Visualizing faults in the field Field Work Becomes Easier and More Efficient © 2012 Electric Power Research Institute, Inc. All rights reserved. 11
- 12. View the YouTube Video! http://www.youtube.com/watch?v=Jnnq8V92rtw © 2012 Electric Power Research Institute, Inc. All rights reserved. 12
- 13. Contact John J. Simmins, Ph.D. Sr. Project Manager Smart Grid | IntelliGrid Power Delivery and Utilization Electric Power Research Institute 942 Corridor Park Blvd. Knoxville, TN 37932 jsimmins@epri.com www.epri.com © 2012 Electric Power Research Institute, Inc. All rights reserved. 13
- 14. Together…Shaping the Future of Electricity © 2012 Electric Power Research Institute, Inc. All rights reserved. 14
Editor's Notes
- Traditionally, integration technology has not been a strategic program at most utilities. Integration was done on a “per project” basis, with little thought to an overall approach. The result is what is know as “accidental architecture” and is illustrated by the “spaghetti and meatballs” diagram on the right that was an actually system. This type of architecture is characterized by interfaces that are written to address a specific data exchange between two systems with little or no regards to the overall context of the enterprise. It is not uncommon to find 4, 5 or more different programming languages or messaging technologies in an enterprise such as this. The result is that the code is overly complicated and difficult to maintain. The number of staff to care and feed this type of architecture is needless high. When an interface “Breaks”, it can take a significant amount of time to identify and fix the problem – if the interface involves billing, this can negatively impact cash flow. The point to point interface typically does not have any facilities for tracking the status of a message, reporting on the failure (it just doesn’t show up) or guarantee the delivery of a message. Typically, one only knows when an interface has not worked when someone cannot perform a mission critical function.
- What many utilities are moving to is a planned architecture that takes advantage of technologies that other industry segments have been using for some time. This architecture takes advantage of a message broker or enterprise service bus to manage, track, visualize and re-use information. It facilitates the development of a system of record for each type of utility data. This reduces the amount of effort needed to maintain data and reducing errors at the same time. By looking at all the messages exchanged in a back office environment, an enterprise semantic model can be developed. An enterprise semantic model is a common understanding of data elements across a utility IT environment. For example, ensuring that all applications have a common understanding of customer information such as address (this is more complicated than it looks), phone number, service location, and an identifier that uniquely defines a customer. When the data in an enterprise is viewed across applications, then combining and re-using messages becomes possible. As an example, a change in phone number may be entered via the IVR and be propagated to the CIS, OMS and other systems. Bills may be paid on line, at a kiosk, through an agency such as social services, over the IVR, etc. and a single message structure is used to deliver the information to the CIS. The result is lower costs for integration, maintenance and the ability to more inexpensively swap out applications or vendors.
- Here you can talk about how this is nothing new, it is a continuation of the research that you were doing on a TI project. Mention that all these can be on the same, low cost device.
- Use CasesCrew locationAsset historySingle line GISUpstream/downstream tracingDevice taggingFault/outage locationWork order creationWork order statusingPhase identificationLocating underground equipmentCorrecting GIS informationStorm assessment
- Operational AdvantagesTighter control over crew activities.Better, near real time information in the field.Combine information from Asset Management and Operations to make decisions that support both.Can help enforce safety procedures and operating procedures by controlling the actions of field crews better.Can have SOP, Bronze Book, Red Book, etc. on line.Can have multimedia versions of EPRI reference books.The application has a crew member’s perspective. They don’t have to worry about which application they are in (mobile GIS, OMS, MWM, etc.)Can have the same “look and feel” with back office and field devicesIT AdvantagesLower cost of hardware – typically save $4-6K per truck.Better communications – iPADs move from 3G networks to WiFiseemlessly.Lower cost of ownership – Do not need seats for mobile GIS, Mobile Workforce Management, Asset Management, etc.Lower cost of upgrades – Do not have to bring in all the mobile devices for each upgrade on multiple applications. There will be an “app store” and the iPAD will handle the upgrades.Leverages the Common Information Model to lower cost of integration and total cost of ownership of interfaces.
- Stress were are NOT selling software. We are creating technology. We are trying to understand the issues with getting information to and from field personnel. Make things easier for the folks in the field to do their jobs.WE ARE TRYING TO DRIVE STANDARDS (CIM).The Issue:Access to real-time data has not progressed.Getting data to the field is too expensive.Getting the data from the field is too cumbersome.The applications don’t interop.Data is not accurate.The Impact:Potentially dangerous situation.SAIDI/SAIFI numbers unnecessarily high.EPRI Solution:Build on a light weight, inexpensive platform.Leverage augmented reality capabilities.Messaging using CIM to multiple systems.Two way communications to back office systems.Value:Lower cost of field force automation.Puts accurate data where it needs to be.Correct inaccurate GIS data.Spurs CIM development.Stress that there are many use cases:Crew locationAsset historySingle line GISUpstream/downstream tracingDevice taggingFault/outage locationStorm damage assessmentWork order creationWork order statusingSwitching ordersPhase identificationLocating underground equipment
- Mention bringing SOP to the fieldMention switching orders.Mention updating and adding data to GISMention (again) your tools and the ability to have all this on the same device.Facilitate information flow fromGISAsset ManagementOMSOMSDMS
- Open source, open standards. Open source, open standards. Open source, open standards. Open source, open standards.Go through the steps from the bottom.
- Stress that we are addressing information access issues (standards, visualization technology)We would facilitate information flow for: Power Quality - Program 1Energy Storage - Program 94IntelliGrid - Program 161Distribution Systems – Program 180Integration of Variable Generation and Controllable Loads - Program 173Grid Operations - Program 39Overhead Transmission – Program 35Underground Transmission – Program 36Substations – Program 37