Ur Software Architecture - GE B30 UR Series Instruction Manual

1.2 UR OVERVIEW 1 GETTING STARTED
The direct inputs and outputs provide a means of sharing digital point states between a number of UR-series IEDs over
1
dedicated fiber (single or multimode), RS422, or G.703 interface. No switching equipment is required as the IEDs are con-
nected directly in a ring or redundant (dual) ring configuration. This feature is optimized for speed and intended for pilot-
aided schemes, distributed logic applications, or the extension of the input/output capabilities of a single relay chassis.

1.2.3 UR SOFTWARE ARCHITECTURE

Firmware is the software embedded in the relay and is designed in functional modules that can be installed in any relay as
required. This is achieved with object-oriented design and programming (OOD/OOP) techniques.
Object-oriented techniques involve the use of objects and classes. An object is defined as "a logical entity that contains
both data and code that manipulates that data". A class is the generalized form of similar objects. By using this concept,
one can create a protection class with the protection elements as objects of the class, such as time overcurrent, instanta-
neous overcurrent, current differential, undervoltage, overvoltage, underfrequency, and distance. These objects represent
completely self-contained software modules. The same object-class concept can be used for metering, input/output control,
software interface, communications, or any functional entity in the system.
Employing OOD/OOP in the software architecture of the B30 achieves the same features as the hardware architecture:
modularity, scalability, and flexibility. The application software for any UR-series device (for example, feeder protection,
transformer protection, distance protection) is constructed by combining objects from the various functional classes. This
results in a common interface across the UR series.
1-4 B30 Bus Differential System GE Multilin