Outage Coordinator Outage Profile CIM Canonical Model Profiling Process Conforms to Energy Market Production Schedule Profile TSO 1 CIM Payload TSO N CIM Payload Network Model Profile CIM Payload CIM Payload Derived From Payload Exchange Day-Ahead Security Analysis figure 11. A business process composing CIM data. conveniently by Identifiedobject. mrID when available. The Iec does not standardize internals of business process implementations, but the interface standards are designed such that a business process can implement a consistent composed model of the various input standards. The following examples show how this composition of various payloads functionally occurs at an object instance level. figure 12 shows how a receiver can compose new attributes on the same business object instance given the profiles share the same cIm class, aclinesegment in this case. such a case would be useful, for example, combining phase balanced power flow model (attribute "r") data for a line segment (Identifiedobject.mrID =1) with short circuit model data (attribute "r0") for the same line segment from another source. figure 13 shows how a receiver can compose references across payloads. This example shows how a shared Basevoltage object in payload 3 could be referenced from payload 4. Typically the referenced object (Basevoltage with mrID =3) would be consumed january/february 2016 Payload 1 class ACLineSegment mRID = 1 r = 10.0 Payload 2 Receiver class ACLineSegment mRID = 1 Unordered r = 10.0 r0 = 15.0 class ACLineSegment mRID=1 r0=15.0 figure 12. The composition of attributes on an object. Payload 3 Receiver class BaseVoltage mRID=3 Payload 4 "Proxy" class BaseVoltage mRID=3 class BaseVoltage mRID=3 Unordered Equipment to BaseVoltage class ACLineSegment mRID = 1 Equipment to BaseVoltage class ACLineSegment mRID = 1 figure 13. The composition of references among objects. ieee power & energy magazine 81