Is Your Geodatabase Ready for Smart Grid? Ed Blair Telvent Utility Group

Transcription

1 Is Your Geodatabase Ready for Smart Grid? Ed Blair Telvent Utility Group

2 You Can t Have a Smart Grid with Dumb Data, Jeffery R. Meyers

3 Scope of the Discussion A Geodatabase-centric view of Smart Grid technologies Smart Grid has many moving parts. Smart Grid means many things to many people. How your Geodatabase can support SG apps Things you may need to consider

4 Three Key Things Your GIS can add more business value by supporting Smart Grid than nearly any other way. DMS in particular You may have preparation to do but it may not be backbreaking. ArcGIS has the right tools for this job.

5 What IS a DMS? Suite of real time and study mode applications to support online SCADA operations to: Dynamic network modeling and control Reduce losses and operations costs Improve quality of supply to customers

6 DMS Benefits Example Approx. 25,000 Customers Approx. 5,200 distribution transformers Approx. 460 mi primary conductor

7 DMS Benefits Example 266,400 MWh Annual Electricity Supplied (*) $60/MWh Per unit supply cost $15,984,000 Total supply cost 12.5% Total losses (btw 10% - 15%) $1,998,000 (*) Based on DOE estimate of 888 KWh usage per residential customer per month 25,000 Customers 5,200 transformers 460 mi primary

8 DMS Benefits Example (10 15%) Technical Commercial (5 8% ) Cause, location Theft and not measured energy (3 5%) Meters (1 2%) Billing system(1%) Supply Ss HV/MV (1%) Distr.tranasform. MV/LV (1 1.5%) MV network (1 3%) LV network (1 3%) Improvement methods (using DMS) Control of measurement devices and connections Anonymous denunciation DMS location of commercial losses Gauging, new meters Improvement of reading and billing system Short term DMS optimal network reconfiguration DMS Voltage/Var control Long term DMS Network development and reconstruction Very long term General network redesign

9 DMS Benefits Example Benefit from Reduction of Losses 266,400 MWh 266,400 MWh Annual Supplied $60/MWh $60/MWh Per unit supply cost $15,984,000 $15,984,000 Total supply cost 12.5% 11.8% Total losses $1,998,000 $1,886,112 $111,888 Saving Reduction of Technical and Commercial Losses Optimal Network Configuration Voltage Control Var Control (with controllable capacitor banks) Reduction of commercial losses (theft) Reduction in losses during outage events 0.7%* * Dr Nenad Katic, Telvent DMS Group

10 DMS Benefits Example Overall Benefits Overall savings as a percent of annual energy supply costs Application Savings * Reduction in Power Losses 0.7% Reduction in Operational Costs if utility 4.5% pays penalties for customer outages Reduction in Network Development 1.0% Increase from Improved Power Quality 1.0% * Dr. Nenad Katic, Telvent DMS Group

11 What does a DMS expect of the network? Accurate network data is crucial to obtain good performances and results very close to reality. Di Lembo, Petroni, Noce, Reduction of Power Losses and CO2 Emissions, CIRED, 20th International Conference on Electricity Distribution, Prague, 8-11 June 2009

12 What does a DMS expect of the network? to perform network calculations such as State Estimation or Load Flow quickly and precisely many inputs are needed; The precise Network Topology The electrical characteristics of elements (transformers, conductors, switches, ) Basic measures from the field Reliable evaluation of customers load and generation Di Lembo, Petroni, Noce, op cit.

13 Role of the Geodatabase in Smart Grid Solutions Distribution Management Geo- Database A Smart Grid application may: Operate directly on the Geodatabase Exchange data with the Geodatabase Rely on data maintained in the Geodatabase for an Outage authoritative network Manage- representation ment Conveyed via a standard definition such as Multispeak or CIM Geo- Database Engineering Analysis System Planning

14 Conceptual GIS-DMS Integration Workflow

15 Data Management Philosophies Geodatabase Source data may be of varying quality Powerful tools for validation and cleanup SG Apps Source data expected to be correct from the start If not correct, not loaded

16 Your Geodatabase May Be of a Rich and Diverse Heritage Synercom GFIS AutoCAD Smallworld ArcGIS

17 Geodatabase Content What Does the SG App Expect?

18 Importance of the Geometric Network There must be a geometric network and with connectivity that s an accurate representation. You can get business value from a Geodatabase without a complete or accurate network. You can t get value from supporting Smart Grid apps without one.

19 Phasing Breaker Breaker ABC A A A ABC A Unk A B B C Good C Bad Conductor record phases in sync with the feature phase

20 Phasing Breaker Breaker ABC A A A ABC A B B C Good C Bad

21 Voltage Consistency 12.5kV Step Step XFR XFR HV 12.5 kv LV 4.16 kv 120/240 v Good 4.16kV Distribution XFR HV 4.16 kv LV 120/240 v 12.5kV Step Step XFR XFR HV 12.5 kv LV Unk 120/240 v Bad 4.16 kv Distribution XFR HV 4.16 kv LV Unk

22 Equipment Catalog Examples: TransformerBank FuseBank SwitchBank CapacitorBank DynamicProtectiveDeviceBank BankDevice + ObjectID: Integer + FeederID: String + FacilityID: String + Phase: PhaseDomain + <other attributes> GIS Model 1 Unit + ObjectID: Integer + BankOID: Integer + Phase: PhaseDomain + Mfg: String + Model: String + <other attributes> *

23 DMS Model * Device + InstanceID: String + FeederID: String + FacilityID: String + Phase: String + CatID: String Equipment Catalog BankDevice + ObjectID: Integer + FeederID: String + FacilityID: String + Phase: PhaseDomain + <other attributes> GIS Model 1 1 Catalog + CatID: String + <properties> Where do we get the Catalog ID? - May be the same as the EquipmentID in the Multispeak model Unit + ObjectID: Integer + BankOID: Integer + Phase: PhaseDomain + Mfg: String + Model: String + <other attributes> *

24 1 Catalog + CatID: String + <properties> DMS Model * Catalog ID Option 1 Device + InstanceID: String + FeederID: String + FacilityID: String + Phase: String + CatID: String Add Catalog ID attribute to GIS device classes Define as default value associated with a subtype Maintain with edit events (auto-updaters) BankDevice + ObjectID: Integer + FeederID: String + FacilityID: String + Phase: PhaseDomain + CatID: String + <other attributes> GIS Model 1 Unit + ObjectID: Integer + BankOID: Integer + Phase: PhaseDomain + Mfg: String + Model: String + <other attributes> *

25 DMS Model * Catalog ID Option 2 Device + InstanceID: String + FeederID: String + FacilityID: String + Phase: String + CatID: String BankDevice + ObjectID: Integer + FeederID: String + FacilityID: String + Phase: PhaseDomain + <other attributes> GIS Model 1 1 Catalog + CatID: String + <properties> Correspondence + CatID: String + DeviceType: String + <Attr1>: String + <AttrN>: String Correspondence Table And custom interface code Unit + ObjectID: Integer + BankOID: Integer + Phase: PhaseDomain + Mfg: String + Model: String + <other attributes> *

26 Catalog Entry Definition for Overhead Transformer Transformer Catalog Entry Example

27 GIS/DMS Representations

28 With Detail from Catalog

29 Catalog Entry Definition for Padmount Equipment Padmount Transformer Definition

30 Expectations about States Likely that your DMS wants to know about soon to be constructed/energized

31 Linkage to load data Customer Loads

32 Geodatabase Quality

33 Increased Importance of Quality SG applications assume data from the GIS is both complete and correct.

34 Types of Errors Invalid feature geometries Multi-part geometries Closed polylines Self-intersecting polylines

35 Types of Errors Network Connectivity Errors Missing Network Element IDs Network features with multiple Element IDs Element ID that references a feature no longer in the geometric network Inconsistent connectivity

36 Types of Errors Invalid Network Configurations Islands Loops Multi-feeds

37 Types of Errors Invalid Feature Attributes Fields set by Auto-Updaters (that may not fire) as on operations that don t trigger events, like Connect and Disconnect FeederInfo and ElectricTraceWeight Plain old attribute errors Phase inconsistency Voltage inconsistency

38 Types of Errors Invalid Feature Attributes Plain old attribute errors Phase inconsistency Voltage inconsistency

39 Quality Methods All of us employ some manner of quality procedures (right?). Striving to provide the best quality within reason And when we find quality errors we generally correct them

40 QA Rules Create selection set Run QA Evaluate results

41 QA with a Geodatabase Manager QA can also be invoked as an action within an application such as a Geodatabase Manager.

42 Quality Methods Bit Twiddler s Toolbox Layers that interpret the FeederInfo field Identifies features that Feeder Manager considers anomalous Islands Multi-feeds Loops

43 Feeder Manager Debug Layers (Bit Twiddler s Toolbox) 2 No Open point 1 Expected normal opens Examination of of location Electric ArcFM One Examination number typical Identify Feeder Distribution 2 resolution of of Manager indicates location Network Debug feeders strategy: number Open Layers: point involved: 1 Migrated missing from Legacy View Likely Cedar Finds Yellow data an Source cause Valley an indicates open using of 3 of into point (CV3) multi- legacy a an an ArcFM Walnut multi-feed Circuit as as expected Geodatabase IDs 1 (WN1) -Walnut 1 (WN1) -Cedar Open Valley point 3 (CV3)

44 Pros Current Typical Quality Methods Pros and Cons Effective in evaluating issues with edited features Cons Data quality should get no worse than start of production use. No overall view of database quality No way to differentiate quality types E.g., distinguishing invalid asset rules from network connectivity rules No way to measure database-wide quality change over time

45 Measures of Quality Features with errors of significance per purpose Distribution Management Advanced Metering Engineering Network Analysis Outage Management Staking System Planning

46 Use Case Evaluating Data for Smart Grid Application Feature Geometry Phase Designation Connectivity Phase Consistency Is it valid? Is it in the Phase Domain? Island, Loop, Multi-feed Is the feature connected to features of the same phase? ABC A B A = Bad Bank-Unit Phase Consistency Voltage Consistency Braided Phases Does unit phase match bank phase? Especially at transformers Phases split then re-join

47 What now?

48 A (Modest) Proposal Acknowledge that anomalies exist in every database Store anomalies as features Non-Networked Non-Versioned Apply a routine process that re-creates anomalies on a regular basis (daily or weekly) Can we put a number on that?

49 Why Store Anomalies as Features? rather than discovering them at strategic points in time Allows numerical accounting Allows association with convenient units of measure Like Feeder Or like Region

50 Quality as an Ongoing Process You probably have issues. You re not going to solve them in a day. There needs to be a way to monitor Geodatabase quality. And manage it over time.

51 Feeder Concept Tool Feature/ Anomaly Counts Quality Measure Rules

52 Inspecting Anomaly Features Anomalies share the geometry of of feature they describe.

53 Overall View of Quality

54 Summarized by Region Region with anomaly count

55 Remember Your GIS can add great business value by supporting Smart Grid. You may have preparation. ArcGIS has the right tools for this job.

56 Next Make an assessment Representative pilot or the full Geodatabase Define steps to get out of the hole Define processes for staying out of the hole

57 Thank You!