Products News & Events Success Stories Partners Pricelist & Orders Download Members Section Support & FAQ Training Contact 
Features & Benefits of Reliance 3
Reliance 3 consists of these software modules:
Development Environment - Reliance Design
Runtime Software - Reliance Runtime, Reliance Server, Reliance Runtime Server
Web Client - Reliance J
Communication Drivers
Development Environment | ||
| Features & Benefits | Reliance Design Desktop More info | Reliance Design Enterprise More info |
| visual development of applications (visualization projects) |  | |
| adding ready-to-use components (i.e. visual objects) selected from the Component palette into visualization windows | | |
| managing components placed into visualization windows, visual configuration of components' properties, modifying properties of any number of components at a time (even for components of different types), duplicating components, intelligent component alignment and layout, grouping components, moving components onto another layer | | |
| defining and using (selecting, locking, showing, hiding) layers in visualization windows | | |
| duplicating visualization windows with optional substitution of components' links to variables | | |
| managing visualization windows | | |
| managing pictures imported into a visualization project | | |
| managing the Picture library | | |
| managing (defining, modifying, duplicating, deleting, etc.) objects of different types (devices, databases, etc.) via visual tools with uniform appearance and control, so-called Managers; arranging objects into folders (optional), modifying properties of any number of objects at a time, duplicating objects, substitution of objects' links to other objects when duplicating, exporting/importing objects to/from a CSV file | | |
| managing a visualization project's structure (control areas, computers, users, devices, databases, etc.), configuring computer-specific properties, configuring the behavior and functionality of the runtime environment for individual computers | | |
| managing devices, variables, communication zones and alarms | | |
| managing databases and database fields | | |
| managing historical trends to display historical data | | |
| managing real-time trends to display most recent data | | |
| managing historical reports to display historical data | | |
| managing print reports based on templates in TXT or HTML format | | |
| managing recipes for recipe-based control | | |
| managing scripts written in VB Script | | |
| defining access rights | | |
| securing access to specific operations by access rights | | |
| assigning users a specific set of access rights and restrictions | | |
| support for room control modules IRC manufactured by Teco | | |
| support for embedding ActiveX controls in visualization windows, linking an ActiveX control's property to a variable defined in the visualization project, linking an ActiveX control's event to a script defined in the visualization project | | |
| exporting a visualization project to the Web format for Web clients | | |
| development of network applications with TCP/IP communications between computers, including support for redundancy; defining network connections (primary and standby) and a list of devices whose data and alarms should be transferred through the connections | | |
Runtime Software | ||||
| Features & Benefits | Reliance Runtime View | Reliance Runtime Control | Reliance Server | Reliance Runtime Server |
| loading and running a visualization project | | | | |
| acquisition of data from the communication drivers of the connected devices (i.e. automation/control devices) | | | | |
| OPC client | | | | |
| DDE client | | | | |
| DDE server | | | | |
| generating and processing alarms | | | | |
| logging data and alarms to databases | | | | |
| network (TCP/IP) communications to other instances of the runtime software through network connections, including support for redundancy | | | | |
| acquisition of data and alarms (real-time and historical) from other instances of the runtime software through network connections | | | | |
| providing other instances of the runtime software with data and alarms (real-time and historical) through network connections | | | | |
| executing scripts | | | | |
| processing recipes | | | | |
| sending e-mail messages | | | | |
| sending and receiving SMS messages (SMS driver required) | | | | |
| multi-language support | | | | |
| logging Postmort records (recording changes in real-time data and logging them into special data files) | | | | |
| passing commands for devices to communication drivers | | | | |
| passing commands for devices to other instances of the runtime software through network connections | | | | |
| executing commands for devices received from other instances of the runtime software through network connections | | | | |
| controlling the industrial process through the visualization | | | ||
| displaying visualization windows with real-time data | | | | |
| displaying and acknowledging current alarms, filtering alarms by a device (optional), user-definable sorting | | | | |
| displaying, printing and exporting historical alarms, user-definable filtering and sorting | | | | |
| displaying most recent data as real-time trends | | | | |
| displaying and printing historical data as historical trends | | | | |
| displaying, printing and exporting historical data as historical reports | | | | |
| displaying, printing and exporting data (real-time and/or historical) as print reportsv | | | | |
| replaying and stepping Postmort records (replaying the visualization of the industrial process and stepping data changes) | | | | |
| managing users | | | | |
| managing (defining, modifying, duplicating, deleting, etc.) objects of different types (historical trends and reports) via visual tools with uniform appearance and control, so-called Managers; arranging objects into folders (optional), modifying properties of any number of objects at a time, duplicating objects, substitution of objects' links to other objects when duplicating, exporting/importing objects to/from a CSV file | | | | |
| managing historical trends to display historical data | | | | |
| managing historical reports to display historical data | | | | |
| logging users on and off the program | | | | |
| verifying access rights when performing access right-protected operations | | | | |
| saving user-defined settings to user profiles | | | | |
| data server for Web clients | | | ||
| providing Web clients with data and alarms (real-time and historical) | | | ||
| executing commands for devices received from Web clients | | | ||
| verifying users logging on to Web clients | | | ||
Web Client | |
| Features & Benefits | Reliance J |
| loading and running a visualization project in the Web format | |
| network (TCP/IP) communication to a data server (Reliance Server or Reliance Runtime Server) | |
| acquisition of data and alarms (real-time and historical) from a data server | |
| controlling the industrial process through the visualization and passing commands for devices to a data server (optional feature configured when exporting the visualization project to the Web format) | |
| displaying visualization windows with real-time data (supported components) | |
| displaying and acknowledging current alarms | |
| displaying historical alarms, filtering alarms by a device (optional) | |
| displaying most recent data as real-time trends | |
| displaying historical data as historical trends of any single variable including a simple tabular representation of the data | |
| logging users on and off the program | |
| verifying access rights when performing access right-protected operations | |
| saving user-defined settings to user profiles | |
| multi-language support (including switching at runtime) | |
Communication Drivers - More info | ||
| Driver | Devices/Models | More info |
| Teco | Tecomat, Tecoreg, Tecoreg IRC, Tecomax | |
| Modbus | devices supporting the Modicon - Modbus communication protocol (serial link, Ethernet) | |
| Sauter EY2400 | EY2400 | |
| Rittmeyer wsr3000 | wsr3000 | |
| Johnson Controls | Johnson Control communication drivers | |
| AMiT | control systems manufactured by AMiT | |
| Elgas | ELCOR-94, DATCOM | |
| QMD | telemetric devices supporting the QMD communication protocol | |
| MPC | telemetric devices supporting the MPC communication protocol | |
| DMB | telemetric devices supporting the DMB communication protocol | |
| TMC | telemetric devices supporting the TMC communication protocol | |
| DIO3000 | telemetric devices DIO3000 manufactured by Starmans | |
| SMS | GSM modems Siemens M20, TC35, MC35, Wavecom WMOD2B | |
| External Communicator | devices supporting communication via a serial link; the actual communication must be programmed in scripts (communication protocol knowledge required) | |
_______________________________
SCADA/HMI = Supervisory Control And Data Acquisition/Human Machine Interface
Visualization project = an application developed in Reliance
Components = visual objects (e.g. texts, pictures, shapes, buttons, etc.)
Non-visual objects = objects such as computers, users, devices, databases, trends, etc.
Computer = a non-visual object representing the actual computer on which a visualization project will run at the end-user site
Device = a non-visual object representing a hardware device (PLC or another similar industrial automation/control device) or a fictional device (so-called virtual device)
Script = a piece of program code written in the Visual Basic script language
