Configure Instrument Run Options for Analysis Codes

For context, see Configure Analysis Codes Options.

Activity Steps

  1. On the Profile ribbon tab, click Analysis Code.

    The Analysis Codes screen displays.

  2. Select the Analysis Code.
  3. On the menu, click Setup » Options.

    The Edit Analysis Code screen displays in the Client Job Options category group.

  4. In the Category list, click the Instrument Run Options category group.

    The Instrument Run Options screen displays.

  5. Complete the following field as required for the top quadrant:
    • Create Instrument Runs—Enables automatic creation of instrument runs after the samples batch have been created. You can select this for analyses that do not require initial measurements, where final results can be obtained immediately after logging samples; for example, solution samples.
    • Use Templates—Applies a predefined instrument run template if one is assigned to the analysis code or package.
    • Use Data Entry Grid—Displays a grid format for entering instrument results manually. If selected, the Rows and Cols fields to the right enable to enter the number of rows and columns for the grid
    • Ignore Scheme Replicate Settings—Overrides replicate settings defined in analyte schemes; treats all results individually.
    • Use all Scheme Names in Lists—Displays every scheme name in selection lists, regardless of filtering.
    • Auto-Update Client Analytes—Updates the client’s analyte list automatically based on the run’s assigned schemes.
    • Add Methods to Code in Job Book—Links the method to the analysis code in the Job Book for traceability or reporting.

      Note: In most cases, you can leave the default options unchanged.

  6. In the second quadrant (Run Due Dates), select from the following fields as required:
    • Never update automatically
    • Update automatically when Batch Due Date is earlier—Default.
    • Always update automatically
  7. In the third quadrant (Blank Aliquots), select from the following fields as required:
    • Add to Run and Show—(Default) Includes blank aliquots from the laboratory job in the instrument run.
    • Add to Run but do not Show—Includes blank aliquots in the run but hides them from view (useful for background or internal checks).
    • Do not Add to Run—Excludes blank aliquots entirely from the instrument run.
  8. In the first quadrant on the right (Run Description From), select from the following:
    • Lab Job Description—(Default) Uses the description from the laboratory job for the instrument run.
    • Analysis Method—Uses the method name as the run description.
    • Update Descriptions—Updates the description for the instrument run automatically if you change the lab job description manually.
  9. In the second quadrant on the right (Splits Run), select from the following:
    • None—All samples are included in a single run.
    • By Rack—Creates separate runs for each rack.
    • By Sample—Creates separate runs for each individual sample.
  10. In the third quadrant on the right (Use Client Analytes for Setup), select from the following:
    • No— (Default) Uses the default setup, not influenced by the client’s analyte selection.
    • Yes—Applies client-specific analyte selection for the instrument run, based on the configuration made in the Client Job Setup screen. For more information, see Update Sample Options. This setting does not affect the analytes configured in the analysis code, but it is useful when assigning specific analytes to individual samples—rather than applying all analyte schemes to every sample in the batch. Enabling this option ensures the system respects the client-defined analyte setup in the client jobs during the instrument run. Only apply for series.
    • Adjust from Selected—Starts with the client selection and allows adjustments during setup.
  11. Select the Approval Level from:
    • Tech 1
    • Lead Crew
    • Supervisor
    • Approval Procedure—Optional field to document or enforce a specific approval process.
      Note: These are the different approval levels that come pre-configured in the system. These levels can be modified, removed, or expanded according to your operation’s requirements during implementation.

    Note: When a higher approval level is required, the approval process must follow a cascade approach, meaning the lower-level approval must be completed first before going to the next level. Tech 1 is the lowest approval level in the hierarchy. The user account must have the corresponding approval level assigned in order to approve. All users have Tech 1 level rights.

  12. Click OK.