Portable Data and Modeling for Electromagnetic Transient Analysis programs Jean Mahseredjian Ecole Polytechnique de Montreal 1

New IEEE Task Force Co-chairmen: Jean Mahseredjian and Taku Noda Portable Data and Modeling for Electromagnetic Transient Analysis programs Objectives – Explore the possibility to define a portable (common) input format (PIF) for all electromagnetic transient programs (EMTP- type programs) – Ultimately the format may be extended to modeling methods/definition in addition to modeling data – Ultimate goal: Establishment of a standard Participants: – Off-line and real-time EMTP-type software vendors – Universities – Utilities (important support due to predicted impact) 2

Subject Simulation and analysis of power system transients – EMTP-type applications: Capability to simulate electromagnetic transients Capability to simulate electromechanical transients (detailed) Time-domain simulations, circuit based Wideband models: from steady-state to switching transients and to lightning Time-steps: microseconds, rarely exceeds 0.5 ms Duration of simulation: 50 – 400 seconds – For very large networks, a simulation for 59 secs can take a day 3

Current Situation Modern EMTP-type packages include multiphase load- flow solvers By comparison, PSS/E does electromechanical transients and steady-state – EMTP can do the same, but with much higher precision. It simulates and finds the waveforms (exact) and includes harmonics – PSS/E will find phasors but does not include harmonics Current Situation – There are no portability standards between applications in the same field – CIM: needs to be augmented to include EMTP attributes

Importance of Portability 5

UML, XML, DTD, RDF, CIM/CPSM Unified Modeling Language – Defines notation and semantics for object-oriented models – Graphical representation XML: eXtensible Markup Language DTD: Document Type Definition Resource Description Framework – IEC : XML format for network model exchanges using RDF – CIM/XML: Translated into XML using the relational RDF syntax to describe instances of CIM objects and their relationships CPSM: Common Power System Model (IEC ) – XML data file transfer requirements, subset of classes – Adopted by NERC: standard for TSO data exchange 6

CIM/EMTP-RV Translation to a proprietary format – Topological data – Unique identifiers for devices – Device data – Specific model issues – Validation – Elimination of useless data for simulation Example: Extra breakers Usage of CIM/CPSM for filtering data – Object mapping ACLineSegment: PI-section ShuntCompensator: RLC EnergyConsumer: PQ load GeneratingUnits and SynchronousMachines: PV, PQ or slack – Graphical presentation Automatic drawing, positioning, positional data Various presentation aspects New requirements for existing applications 7

Challenges EMTP-type models are complex There are more differences between solution and modeling methods from various software vendors There is a strong requirement from vendors and users to maintain Graphical User Interface visualization of networks – The new standard must develop GUI portability – The GUIs are complex CIM-XML or just XML? – Establishing a new XML standard from scratch will simplify the standardization path. – Compatibility with CIM has many advantages: established standard, exchanging with traditional power system software packages, visibility 8