This document provides an overview of the Common Object Request Broker Architecture (CORBA) and Object Request Broker (ORB). CORBA allows distributed objects to interoperate across different operating systems and programming languages. An ORB acts as a broker between client requests and the completion of those requests, similar to a telephone exchange. Key functions of an ORB include separating client and server implementations and providing services like naming, transactions, and persistence. The document also discusses how CORBA can be used to implement simulation platforms and standards like IEC 61970 for power grid management applications.

1. Presented By
PROTIM PAUL

2. The Common Object Request Broker Architecture
(CORBA) is a standard architecture for a distributed objects
system.
CORBA is implemented by ORB(Object request breaker)
It adopt IEC61970 platform to implement
CORBA is designed to allow distributed objects to
interoperate in a heterogeneous environment, where objects
can be implemented in different programming language
and/or deployed on different platforms

3. What is ORB
Object Request Broker (ORB) is the programming that acts as
a "broker" between a client request for a service from a
distributed object or component and the completion of that
request.
“...like a telephone exchange, providing the basic
mechanism for making and receiving calls…”

4. What is the function of ORB
Separates Client and Server implementation.
Life cycle services, which define how to create, copy, move, and delete a
component.
Persistence service, which provide the ability to store data on object
database, and plain files
Naming service, which allows a component to find another component by
name and also supports existing naming systems or directories, including.
Event service, which lets components specify events that they want to be
notified of
Transaction service, which ensures that when a transaction is
completed, changes are committed
Relationship service, which creates dynamic associations between
components that haven't "met" before and for keeping track of these
associations
Externalization service, which provides a way to get data to and from a
component in a "stream"
Query service, which allows a component to query a database.

5. Client Requesting

6. Server Receiving

7. The Basic Architecture

8. CORBA Model Components
Object Request broker
Object Services
Common Facilities
Domain Interfaces
Application Interfaces

9. Object Management Architecture(OMA)

10. CORBA Features
Language independence
Location transparency
Reuse of facilities & services
OMG IDL defined interfaces
Stub & Skeleton generation
Server activation

11. IEC 61970 STANDARDS
It is basis of Application Program Interface (API)
project of US electric Power Research Institute.
The main aim is to REDUCE COST and time in
devoloping new EMS application.

12. IEC61970
CIM
CIM-301
CIM-302
CIM303CIS

13. SIMULATION PLATFORM BASED ON CORBA

14. Advantages of CORBA
Object Location Transparency
 Server Transparency
Language Transparency
Implementation Transparency
Architecture Transparency
 Operating System Transparency
Protocol Transparency

15. Disadvantages of CORBA
Firewall unfriendly
No standard to get the initial
reference for the naming service
No official perl mapping

16. Reference
Power System protection & communication by AKHTAR
KALAM & D.P.KOTHARI
Study of Applying CORBA-Based Distributed Object
Technology to Next Generation of Power Dispatching
Automation System BY Huang Haifeng, Yang Zhihong and
Zhang Shenming
power system simulation platform based on CORBA
technology BY Lai Xiaohua

17. PROTIM PAUL