STEP 3: Understanding the different types of data
and the data flow
Configuration data:
|
This data is maintained in ORACLE (MASTER IS SQL) and automatically
synchronized into the RtDB whenever the data is changed. As data
is usually immediately transferred into RtDB (depending on the SYNC
configuration for the table), applications like drivers can trigger
for changes of configuration data and automatically reconfigure
themselves (hot-reconfiguration). |
Process data:
|
This data is generated by the process, maintained in RtDB (MASTER
IS RTDB) and synchronized into ORACLE whenever the data changes.
The interface between the process and RtDB is established via
specific process drivers. These drivers are usually written in
C or VB and have full access to RtVars and RtDB functions as well
as the process interface.
|
Time base archives:
|
Data from the process, the process image, is stored in time-based
archives in ORACLE (via RtDB) with time-stamp and meter-readings
using configurable sampling rates. Typical data would be e.g. temperatures,
forces or other readings with min, max, mean and average values. |
Event based archives:
|
Events from the process are stored in event-based archives in
ORACLE (via RtDB) with time-stamp and meter-readings. Events are
stored as they arrive. Typical data would be e.g. status changes
of subsystems, error messages, conditions etc.
|
Can I use all these nice RTA
features also in large systems?
|