Enterprise Integration Using the IEC CIM - CIMug - UCAIug

More documents

Recommendations

Info

CIM Name Class• Identified Objects can have many Names• Each Name.name instance can be associated with a differentNameType• NameTypes can be associated with a NameTypeAuthoritythat can be responsible for allocating Name.name valueswithin a NameType• IdentifiedObject.name preserved for legacy reasonsProprietary and Confidential
Names in Messages• Common usage of Name class in a message XSD• NameType often option, but should be provided by source ifmore than one Name instance provided• Target process will map the object using one of the names, asthe name is either used locally or defined within a bilateralmapping tableProprietary and Confidential
Page 1 and 2: EnterpriseIntegration Usingthe IEC
Page 3 and 4: What are we integrating?• Above i
Page 5 and 6: Documentation• Documentation is k
Page 7 and 8: Modeling Levels7Proprietary and Con
Page 9 and 10: Logical Models• The IEC CIM is th
Page 11 and 12: Canonicals• Canonical data models
Page 13 and 14: Tools• Process needs to be suppor
Page 15 and 16: CIMTool• Open source Eclipse plug
Page 17 and 18: Using the CIM• The CIM can be use
Page 19 and 20: CIM Extensions: Stereotypes• Use
Page 21 and 22: CIM Extensions: Extension Models•
Page 23 and 24: Traceability• Need to be able to
Page 25 and 26: CIM/XML• See IEC 61970-452/501/55
Page 27 and 28: Common Message Envelope• IEC 6196
Page 29 and 30: Basic Integration PatternsSynchrono
Page 31 and 32: Transports• IEC 61968 is by defin
Page 33: Names• Object naming is an import
Page 37 and 38: Common Services• Common services
Page 39 and 40: Security• Key terms: Authenticati
Page 41 and 42: Error Handling• Error handling is
Page 43 and 44: Data Warehouse Challenges• The IE
Page 45 and 46: ETL Pattern• Non-messaging integr

Enterprise Integration Using the IEC CIM - CIMug - UCAIug

Create successful ePaper yourself

Delete template?

Save as template?