Variations - Changes to the Network Model

Transcription

1 Variations - Changes to the Network Model CIM University topic Kendall Demaree, GE CIM Users Group Amsterdam, NL 1-3, June 2016 CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

2 Some ongoing work will be tagged Draft! = not yet reached IEC WG consensus CIM Users Group Meeting Amsterdam, NL 1-3 June

3 Everywhere so hard to grasp CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

4 Model variations are everywhere Updates and versioning of a model Comparing alternative construction choices Different representations for different purposes Reduced models HV only models Detailed inter-machine dynamics studies Outages, especially planned outages Integrating a new updated external neighbor model Edit of a model Operations on a model Contingencies System Integrity Protection Schemes (SIPS), Remedial Action Schemes (RAS)

5 Goal: Manage model updates and alternatives Manage for business purposes means: Assemble into cases Schedule changes Test/verify Communicate content of cases or ingredients to cases Trace or provide audit-trail for model changes Structure alternatives to avoid duplication Avoid duplication within alternatives Describe and relate model changes Workflow of designing and approving outages, construction, or simply model improvements

6 Alternate models Possible 6 th BIG point about network models Alternate models of same physical network are often desired Examples of alternate models: HV only to 345KV Network detail until distribution (radial) Network reduction for performance (e.g. Ward reduction.) Equivalent generator models for dynamics Others Alternate models often derived from other alternates Derivations may be complex various equivalent reductions sometimes based on rules or reasoning not in the given data May desire to track and manage each alternate independently CIM Users Group Meeting Amsterdam, NL 1-3 June

7 Change Modeling - Background Simple algebra for models CIM history, philosophy, and status regarding variations IEC and Difference Model verbs Warm up with examples

8 Notation for model updates Start with model M A Specific change to any model is D AB (aka Difference Model ) Note AB is just a naming convention Use + to apply the change The result when applied to M A is model M B M A + D AB = M B

9 Difference Model creation Given full model M A and full model M B The specific difference model D AB can be determined Use - to represent difference operation from: gives: M A + D AB = M B D AB = M B - M A

10 CIM background regarding variations CIM (network models) mainly represent one point in time, one alternative, one case Resisted adding effective dates to all classes (good move) Some exceptions such as: RegularIntervalSchedule and other forms of schedules ActivityRecord, metering changes and events, Outages and Contingencies commonly accepted IEC (CIM RDF XML) and IEC (XSD verbs)

11 IEC Title: Implementation Profiles for IEC Defines XSD message patterns and envelope structures Header denotes CRUD style (and several other) verbs: create change delete Verbs can be nested to any depth Best if payloads avoid nested containment as in flat CIM RDF XML Not the focus here, but also capable to describe change

12 IEC DifferenceModel Title: CIMXML Model Exchange Format The CIM/RDF/XML flavor of describing model differences InterOp tested and used in many active systems Initially designed to simply stream a set of changes to be copied in another system Can be (and often is) used in other scenarios Describes a forward, reverse, and precondition Contains header with limited context information

13 Simple example of Difference Model CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

14 Reverse (undo) CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

15 Apply Difference Model elsewhere Model C not Model A

16 Network example on the EQ profile Equipment profile of IEC CPSM specification Add a tap load on line between station A and B New tap station named T. Split original impedance 50/50 Add load one conforming load in tap station. Retain the original terminal locations (for measurements) Classic: M A + D AB = M B

17 Initial EQ model A drawing CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

18 Final EQ model B drawing CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

19 Initial EQ model A CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

20 Initial EQ model A objects Substation MRID=1 name=a Substation MRID=4 name=b VoltageLevel MRID=2 name=345 VoltageLevel MRID=5 name=345 ConnectivityNode MRID=3 name=a345 ConnectivityNode MRID=6 name=b345 Terminal MRID=9 ACLineSegment MRID=8 name=ab x=10 Terminal MRID=10 Line MRID=7 name=ab

21 Final EQ model B CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

22 Final EQ model B Substation MRID=1 name=a Substation MRID=11 name=t Substation MRID=4 name=b VoltageLevel MRID=2 name=345 VoltageLevel MRID=12 name=345 VoltageLevel MRID=5 name=345 ConnectivityNode MRID=3 name=a345 ConnectivityNode MRID=13 name=t345 ConnectivityNode MRID=6 name=b345 Terminal MRID=9 Terminal MRID=14 Terminal MRID=18 Terminal MRID=16 Terminal MRID=10 ACLineSegment MRID=8 name=ab x=5.0 ConformLoad MRID=17 name=t ACLineSegment MRID=14 name=ab2 x=5.0 Red = new Line MRID=7 name=ab CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

23 Example Network Difference Model Reverse Differences DifferenceModel Forward Differences Substation MRID=11 name=t VoltageLevel MRID=12 name=345 Terminal MRID=10 ACLineSegment MRID=8 name=ab X=10.0 Terminal MRID=14 ACLineSegment MRID=8 name=ab1 x=5.0 ConnectivityNode MRID=13 name=t345 Terminal MRID=18 ConformLoad MRID=17 name=t Terminal MRID=16 Terminal MRID=10 ACLineSegment MRID=14 name=ab2 x=5.0 Line* MRID=7 * = proxy CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

24 header information Some context information, but limited Contains: Model identity Model Authority Set Created date Scenario time Profile Version DependentOn relationship to other models Supercedes relationship to other models

25 Header model relationships CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

26 Timeline for EQ profile CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

27 Timeline for EQ + SSH profile CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

28 Power System Projects Communicate planned changes Describe schedule Describe dependencies Describe steps or phases within the project Give business lifecycle state specification for network change

29 Power System Projects status Draft CIM UML now Adds effective date Adds recursive containment (projects contain projects) To add: User defined business states Description of the changes (ChangeSet models) Tentative plan: Model, profile, and exchange as CIM data

30 Present informative Projects model Informative! Informative! Informative! Informative! CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

31 Differential Model detailed modeling WG13 presently considering best approach All WG s could optionally could adopt same approach Options: Reference an existing style difference file Model explicitly (does not work well for complex changes) Express directly in model using property objects

32 Outage profile explicit UML model WG14 has developed an outage profile based on limited changes, like generic de-rating and open/close a switch Straight forward and simple approach for basics Duplicates modeling and descriptions Practically limited to small scope of model changes No clear rules, pattern, or style developed yet Would be similar to property objects approach

33 Draft! WG14 explicit Outage model Draft! Draft! CIM Users Group Meeting Amsterdam, NL 1-3 June 2016 Draft!

34 Draft! Property objects to express change Model in UML and borrow domain classes but not their MRID. Property objects: Effectively reference normal model MRID s Contain their own identity (could be payload local) Shaped like normal profile classes, all properties optional Classic references only to other Proxy objects in payload Could serialize just like any other data Analogy with DiagramLayout strategy Use existing serialization and profiling techniques Explicit association to IdentifiedObject for generality

35 Class diagram for property objects Draft! Draft! Draft!

36 Instance diagram for property objects Renames VoltageLevel.name to MyNewName on object VL1. Draft! Draft! Draft!

37 Example change ACLineSegment with Registry Draft!

38 Outage as SSH change Outage CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

39 Outage change specification With explicit WG14 planned outage profile Domain logic understands Outage/SwitchAction/Switch Implies change to Switch.open in SSH data With incremental difference model reference, apply it Requires jump to different content, heavy for context change Profile should be defined instance content would be to change Switch.open With properties object, generically read changes and apply Profiles to be defined Requires new but reusable processing logic Described in native domain objects along with Outage object instance content could change Switch.open and more CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

40 Frames and full models When changes are too numerous use full model replacement Organize full models so never include duplicates Frames and ModelPartSpec provide a means to select Alternative models organized and described Apply this approach at macro or micro level (macro here). We ignore profiles here for simplicity (right)

41 Basic frames example CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

42 Frame with a CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

43 Alternates also have s CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

44 Frames with s CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

45 Boundaries also have s CIM Users Group Meeting Amsterdam, NL 1-3 June 2016

46 Generic Change Modeling Task Force Formed June 2014 IEC TC57 WG 13 (mainly), with 14 and 16 interest Objective: Define a modeling approach for expressing a collection of changes to a CIM dataset as an Incremental Dataset Goals: construction, outages, SIPS, audit trail, proposed plans, Grouped changes, and augmented with context information Target of change is unknown or varies Narrow or constrain the allowed changes (like a profile) Works well with RDF, XSD, or other serialization technologies Model operations and audit trails Resulting draft CIM17 canonical model available to describe changes and model parts.

47 Early conceptual - Frameworks, operations, & datasets Operation Sequence Description Classes (AuditTrail, Procedure, ) Operation Sequence Operation Operation Type Draft! Full Dataset Description Classes (Model Parts, etc.) Argument Reference Incremental Dataset Description Classes (Projects, etc.) Argument Type Draft! Draft! Full Dataset CIM Dataset Inc Dataset CIM Dataset Type Model Content Classes (e.g. Power System Equipment)

48 Draft! Draft CIM17 UML models

49 Draft! Draft CIM17 UML DataSet models Draft! Draft!

50 Draft! Draft CIM17 DataSet models 2 Parts Draft!

51 Draft! Draft CIM17 CRUD via ChangSet Draft!

52 Usage of ChangeSet in Draft candidate Draft! Draft! Draft! CIM Users Group Meeting Amsterdam, NL 1-3 June

53 ChangeSet summary Using normal techniques for modeling, profiling Can use typical model driven approach to storage and serialization Same basic capabilities of DifferenceModel Can be used with any well defined CIM serialization approach Can also link with more complex domain specific models Domain models starting to provide context for changes For example: PowerSystemProject CIM Users Group Meeting Amsterdam, NL 1-3 June

54 Take aways Change and variations are ubiquitous Our goal is to manage network model variations Fundamentals are in place for network case semantics Change and part specifications exist Working on giving changes and alternate models context Frames and PowerSystemProject models in CIM17 draft model Your feedback is welcome

55 Questions or feedback M A + D AB = M B kendall.demaree@ge.com