Relay data transfer from linked OneLiner relays to the ASPEN Relay Database (RDB) is a two-steps process:
1) Execute the Store Setting command in OneLiner. OneLiner relay data will be stored in the RDB as separate setting requests (RDB terminology for relay-setting records). A relay object in RDB V9.7 or later can therefore have two types of setting requests: Requests that hold physical setting data, and requests that hold OneLiner relay parameters;
2) Execute the Import OneLiner setting Command in the Setting form of the ASPEN Relay Database program. The data translation in this update is done through scripting and is user modifiable.
These steps are designed to make sure that the data integrity of physical relay settings in the RDB, which represent the complete set of actual relay settings, is not being compromised by external action performed in the OneLiner program.
Note: If desired, the Relay Database Administrator can also set up a trigger to automatically invoke step 2 above when required conditions are met.
You can press the Store button in the relay properties dialog boxes to store OneLiner relay data to the linked relay record in the RDB. Details of these steps are found in section 5.2 OVERCURRENT GROUND RELAYS.
You can also use the button control in the Relay data link dashboard to store data for multiple OneLiner relays in a single run. Refer to Help section 5.2 OVERCURRENT GROUND RELAYS and RELAY DATA LINK DASHBOARD COMMAND for details.
It is often the case that a single relay in the RDB is linked to several OneLiner relays, one for each of the RDB relay protection elements. In those cases OneLiner is designed to automatically store as a single batch the data of all OneLiner relays that are found to be linked to the same relay in the RDB. Entire batch of stored OneLiner relay data will be made available for processing in the step 2 of the data transfer process described above to ensure consistency in updating settings of the RDB relay.