External Tables
How They Benefit YOU!
Eric Jung
What are the External Tables?
•  A database(s), outside of WindMil, but connected to
WindMil Data
•  Multiple database types allowed in 8.2
–  Oracle
–  MS SQL Server
–  MySQL
•  Externals will run on an existing DB instance
What Can They Do? •  Not a Sta,c Data Silo •  Engineering Key to data integra,ons •  A highway that travels both direc,ons What Informa,on Can Be Exchanged? •  Model data External DB –  Standard model data –  ELUA calculated fields –  Polygon based fields •  External data WindMil –  Customer Data: Billing rates, Descrip,on, Member names etc. –  Equipment Data: Maintenance, purchase info etc. How To: A Setup Overview 1.  Database Connec/ons – Connected DB’s 2.  Linked External Tables – Connected Tables & Fields 3.  Table Uses – Connects WM Elements Types to Ext Tables 4.  Field Mappings – WM fields mapped to Ext fields Linked External Tables Tab •  “Used Fields” are available to WM –  Map WM fields to Ext –  Use Ext field in WM •  Primary Key should remain CMID – Must be unique! Table Uses Tab •  Connect WM element type to Ext table •  Note: Mul,ple connec,ons to “Consumer” elements Field Mappings Tab •  Table – External Table name •  Field – External Table fieldname •  WindMil Field – Maps WM field to External •  Example –WM field “max possible fault” mapped to “LL_Fault” field in External Tables Update All Fields •  Prompt to “update all” – Always Yes •  Updates ALL Mapped fields •  This takes ,me: Update to map Fault currents = 385,636 Opera,ons Shared Engineering Data -­‐ Outputs Three Major Categories –  Base Windmil fields Electrical data –  Polygon fields Geospa,al info –  ELUA based fields Custom calculated fields Useful Base Windmil fields •  Connec,vity –  Feeder –  Source •  Fault currents •  Equipment –  Specific equipment – Maintenance records link Polygon Fields •  Open ended – Any projected shape file •  Applies chosen fields from shape file to model elements •  Debate Windmil vs GIS import –  If u,lity has GIS, where should data be sourced? •  OPINION: experience shows this tends to be faster in WindMil than WMM ELUA Fields – Sky’s the Limit! •  Calculated fields based on ELUA script •  Limited only by one’s imagina,on and ability •  Examples: –  Further connec,vity – Upline OCR’s, Upline Regulator, Upline transformer KVA –  Nearest element of Type “____” Model Data Inputs •  Anything with one-­‐one rela,onship •  CIS info –  Metering mul,pliers –  Billing Rates •  AMI info –  Outage counts –  Signal strength Input limita,ons •  No criteria based searches –  IE. Pull load data for par,cular date and interval •  It is unrealis,c to avoid working in DB –  IE. Load import requires load be stored in table with one entry per element –  Calcula,ons/selec,ons must be done in DB applica,on Billing Story •  “I received this service order. It says it’s in my territory but it’s actually in Big Al’s territory. What’s going on?” •  “The town of <insert town name in need of addi,onal tax revenue here/> has just enacted a tax on electricity. What accounts should be coded with this new tax?” Examples – Useful for Billing •  Upline feeder –  SEIEC delineates territory by Feeder –  Model changes automa,cally update data in External tables –  Separate table Feeder2Territory automates excep,ons between CIS and WM. •  City limits –  Determines who is affected by local sales tax –  Automa,cally updated -­‐ Polygon generated field Examples – Useful with AMI •  Upstream opera,ng device –  ELUA field that finds the next upstream mul,ple opera,on device –  Link with AMI outage counts to find blinking zones •  Phasing –  Compare model phasing to AMI phasing –  Generate excep,on reports Examples – Asset Management •  OCR’s, Regulators & Transformers •  WM provides –  Loca,on – (X,Y) –  Loading info (thru KW) –  Specific Sekngs •  Maintenance data connec,on –  Import maintenance data into Externals –  Link based on element or equipment name Field Stories •  “I’m trying to call in to “one call” for an emergency. They’re asking for the township. We used to have this in our paper maps but these newfangled electronic maps don’t have this.” •  “I’ve got this fault that I just can’t find. The recloser at the sub says the fault is 1437A between C phase and ground. Where should I look?” Examples – Useful to Field Personnel •  Township name – Polygon sourced field –  Needed for Dig no,fica,ons –  Polygon manager links to elements –  External tables maps data out for all element •  Phasing •  Fault Currents •  Arc Flash Ra,ngs Engineering Stories “<insert Coop name/> had a shorted CT on the G&T metering at one substaIon. This went on for a year before it was found. They now owe over $300K in back billing due to the 2/3rds reading. How do we know this isn’t happening to us?” Load Reconcilia,on •  Requires import of load and G&T metering •  Using model connec,vity aggregate metering data back to substa,on – “KWH sold” •  Compare results to G&T – “KWH Purchased” •  Compare calculated losses to actual –  KWH Purchased-­‐ (KWH sold + un-­‐metered load) –  Security/yard lights = example of un-­‐metered load Engineering Stories “ Hey there all knowing engineer, we have to take out this substaIon tomorrow and back feed the load. I know the temperature is supposed to be a high of 33 degrees. How can we switch this and what OCR’s do we need to bypass to make this work?”…. “Oh yeah, sorry it’s already 4pm but I need to know by 6 am so I can direct the guys.” Engineering Stories “Last Saturday I was called out on this voltage issue at the “Happy Trails Campground.” They were running 107V and they had 15 of those big RV’s plugged into a 200A service. The rest of the 325 campsites looked like they were precy full too. Heck I even saw one guy in a pup tent with a window unit A/C s;cking out of it. What do we need to do here?” Load Import •  Shown at UC 2015. •  Build an accurate load model in < 30sec •  Requires load data housed in External tables –  Create a table specifically for load –  Populate this table with the load to import •  Very simple SQL script to select specific interval •  Requires a single entry per model element Final Thoughts •  Data silos –  System dependent silos –  Personnel dependent silos •  Vision –  Strategic plan –  Best source of data fields