Using an Integrity-Licensed Instrument ControlUsing an Integrity-Licensed Instrument Control
Once an instrument has been set up with an Advantage Integrity license, it will become part of the Advantage Integrity system. Access will be controlled, data will be stored in the Oracle database, and an audit trail will record events. Once you are logged in to the instrument, the basic operation of an Integrity instrument is the same as its non-Integrity (standard) counterpart for calibrating, setting up experiments, and starting runs.
The few differences are noted here.
SUID#: Instead of defining the data storage path, the database will automatically assign a SUID# to the original, raw data record. This number can be seen on the Summary Page of the Experimental View.
NOTE: Each saved data record within the database will also be assigned a Record ID #, which is displayed on any saved images that are created.
Project Name: Each experiment is assigned to a Project. Project assignment provides a means to category the data in the database, and then later uses that assignment to sort the records in the database for easier retrieval. The available projects are those assigned to you by the TA System Manager. The TA System Manager is also responsible for defining the projects available in this system.
To assign a project to a run follow these steps:
Click
on the 
button to the right of the Project
Name field.
Select a project from those displayed and click OK.
Operator: The Operator field on the Notes Page will automatically display the User ID of the person creating the run and can not be changed. See the section "Handling Multiple Users for a Single Instrument" for rules that apply when there is more then one user.
Restricted or Unavailable Functions: Within the Advantage Integrity system the TA System Manager can define privileges (e.g., restrict actions) within each module of the system.
Within the Q Series™ instrument control program this list of controllable privileges includes items such as access to calibration parameters and analysis, modifying a running method, etc. Therefore, typical functions may not be available depending on the access groups(s) assigned to you. Consult with your TA System Manager to learn about your privilege list for instrument control.
In addition, a set of functions that are available in the standard version of instrument control, are not available when logged into the Integrity system. These functions include:
Run Reject
Network Drive
Autoanalysis.
Method, Procedures and Sequence Files: These files are not saved in the database, nor are the changes audited for these files in this system. They continue to be saved at the designated file location specified by the operator. However, file open and save for these file types are recorded in the audit trail. Moreover, the saved data record contains the details of the experimental conditions (e.g., method, calibration, and instrument parameters) within the parameter block of the saved data record. This information can be viewed in the Universal Analysis program by selecting View/Parameter Block.
Active Experiments: An experiment which is currently in progress may be viewed in Universal Analysis, but until the experiment is complete you can not save any results (e.g, saved analyses, pdf generation).
When there is more than one user accessing a single instrument, the following rules apply:
You can alter another user's run only when assigned access rights to the project associated with that run. You will receive a message asking if you wish to "take ownership" of that run. Select Yes to take ownership. Your name will now be assigned as the Operator on the Notes Page. Select No to deny ownership of that run, then you can click the Append button to create a new run.
You can still start another user's run, even if you do not have access rights to the project assigned to that run. In this case, your User ID will be recorded as the Run Operator in the data record's parameter block, which can be viewed through the Universal Analysis program's View/Parameter Block function. The operator name will remain as the User ID of the original owner.
You may delete any runs regardless of their assigned projects.
If you do not have access rights to the assigned run's project, you will get an Access Not Allowed message. In this case, you will need to select the Append button to create a new run.
When you load a saved sequence, the user currently performing this action is assigned as the operator for all runs. If any run in the saved sequence specifies a project that the current user does not have the right to access, then that run's project is marked Unassigned. Unassigned projects must be changed to a valid project before the start of that run.
See the Advantage Integrity Getting Started Guide or the online help for additional information.
