The Illumina NovaSeq 6000 Integration Package v3.6.0 supports the integration of Clarity LIMS to NovaSeq 6000 instruments. This documentation describes the integration and includes the following information:
Preconfigured workflows, protocols, steps, and automations
Installed components
Configuration requirements, rules, and constraints
The configuration provided in this integration has been established to support NovaSeq 6000 lab processes. Any configuration changes to protocols or workflows - including renaming protocols, steps, and fields - could break process.
Prerequisites and Assumptions
It is assumed that samples enter the NovaSeq 6000 v3.8 workflow as normalized libraries. It is assumed that the following steps have completed before samples are assigned to the workflow:
Samples have been accessioned into the Clarity LIMS.
Samples have been run through QC and library prep.
Samples have been normalized, and the value is captured in a field called Normalized Molarity (nM).
The Illumina NovaSeq 6000 Integration Package v3.6.0 includes the following workflows:
Library Prep Validation v2.3.1 (optional, but recommended for validation purposes)
NovaSeq 6000 v3.8
Library Prep Validation v2.3.1 Workflow
Protocol: Library Prep Validation v2.3.1
Purpose:
Included for validation purposes only, this protocol models the library prep steps required to advance samples to the Run Format (NovaSeq 6000 v3.8) protocol.
The protocol contains a single step - Library Prep Validation v2.3.1. After this step, a routing script sends the samples to the first step of the NovaSeq 6000 v3.8 workflow - Define Run Format (NovaSeq 6000 v3.8).
Steps:
Library Prep Validation v2.3.1
NovaSeq 6000 v3.8 Workflow
Protocol 1: Run Format (NovaSeq 6000 v3.8)
Purpose:
Allows for the assignment of per sample values for:
Loading Workflow Type: Select either NovaSeq Standard or NovaSeq Xp.
Normalized Molarity: Enter a value for each sample.
Flowcell Type: Select from options SP, S1, S2, or S4.
Final Loading Concentration (pM): Select from options 225 (PCR-free workflows) or 400 (Nano workflows), or enter a different value.
Compares the Normalized Molarity value of each sample with the Minimum Molarity value.
Routing script sends samples to the NovaSeq Standard or NovaSeq Xp protocol, according to the selected Loading Workflow Type.
Samples with Normalized Molarity less than Minimum Molarity are removed from the workflow.
Steps:
Define Run Format (NovaSeq 6000 v3.8)
Protocol 2: NovaSeq Standard (NovaSeq 6000 v3.8)
Purpose:
Samples are pooled and added to the library tube in preparation for the NovaSeq run. The run setup information is validated and a sample sheet is generated.
Routing script sends the library tube to the AUTOMATED - NovaSeq Run (NovaSeq 6000 v3.8) protocol.
Steps:
Make Bulk Pool for NovaSeq Standard (NovaSeq 6000 v3.8)
Dilute and Denature (NovaSeq 6000 v3.8)
Protocol 3: NovaSeq Xp (NovaSeq 6000 v3.8)
Purpose:
Samples are pooled and added to lanes on the NovaSeq flow cell. The option selected in the Define Run Format (NovaSeq 6000 v3.8) step determines the flow cell type. The run setup information is validated and a sample sheet is generated.
Routing script sends flow cell to the AUTOMATED - NovaSeq Run (NovaSeq 6000 v3.8) protocol.
Steps:
Make Bulk Pool for NovaSeq Xp (NovaSeq 6000 v3.8)
Dilute, Denature & ExAmp (NovaSeq 6000 v3.8)
Load to Flowcell (NovaSeq 6000 v3.8)
Protocol 4: AUTOMATED - NovaSeq Run (NovaSeq 6000 v3.8)
Purpose:
All samples complete the workflow by going through this protocol.
This protocol contains one fully automated step.
⚠ Do not add samples to the Ice Bucket or start the step. The integration starts the step automatically.
This protocol sets the Loading Workflow Type and allows the choice of the appropriate Flowcell Type and Final Loading Concentration (pM). After the protocol, a routing script sends the normalized libraries to either the NovaSeq Standard (NovaSeq 6000 v3.8) or the NovaSeq Xp (NovaSeq 6000 v3.8) protocol.
This protocol contains one step: Define Run Format (NovaSeq 6000 v3.8).
Step 1. Define Run Format (NovaSeq 6000 v3.8)
Step input: NTP (normalized libraries)
Step output: None
Register Step Started Automation¹
Automatically triggered on entry to the step, this automation registers the start time of the step by publishing messages to Clarity LIMS Product Analytics (CLPA) through Illumina Connected Analytics:
Checks Normalized Molarity value. For samples with no Normalized Molarity value (e.g., empty value, not including 0), it generates an error message informing that the field cannot be empty:
if (!input.hasValue(::Normalized Molarity (nM)::)) {
fail(::The Normalized Molarity cannot be empty.::) ;
}
Compares each sample Normalized Molarity value with the Minimum Molarity value. If the Normalized Molarity value is lower than the Minimum Molarity value, it sets the samples Loading Workflow Type to [Remove from workflow]. The automation also records a message in the Warning field for the sample:
else if (input.::Normalized Molarity (nM):: < input.::Minimum Molarity (nM)::) {
input.::Warning:: = ::The Normalized Molarity is too low.:: ;
input.::Loading Workflow Type:: = ::[Remove from workflow]:: ; }
else { input.::Warning:: = ::not applicable:: }
At this point there are two options:
Correct the Normalized Molarity value on the Record Details screen. Edit the Loading Workflow Type field and set it to NovaSeq Standard or NovaSeq Xp, as applicable.
Complete the protocol without correcting the Normalized Molarity value. In this case, those samples are removed from the workflow.
Automatically triggered on exit of the step, this automation invokes the changeWorkflow script, which routes step inputs appropriately.
Samples with Loading Workflow Type field value = NovaSeq Standard are routed to the NovaSeq 6000 v3.8 workflow. Then, the samples are queued for the Make Bulk Pool for NovaSeq Standard (NovaSeq 6000 v3.8) step.
Samples with Loading Workflow Type field value = NovaSeq Xp are routed to the NovaSeq 6000 v3.8 workflow. Then, the samples are queued for the Make Bulk Pool for NovaSeq Xp (NovaSeq 6000 v3.8) step.
This automation also registers the completion time of the step by publishing messages to CLPA through Illumina Connected Analytics. This is only used for CLPA support.
