> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/instruments-and-integrations/miseq-i100/miseqi100/miseqi100-v1.1.0.md).

# MiSeq i100 v1.1.0

The integration includes the following:

* New MiSeq i100 Series Sequencing v2.0 workflow that maps to lab protocols and instrument runs. The workflow is available in Illumina Preset Protocols v2.11 and consists of the following steps:
  * Assign Analysis Configuration Template (MiSeq i100 Series Sequencing v2.0)
  * Make Bulk Pool (MiSeq i100 Sequencing v2.0)
  * Load to Dry Cartridge (MiSeq i100 Series Sequencing v2.0)
  * AUTOMATED - Sequencing Run (MiSeq i100 Series Sequencing v2.0)
  * AUTOMATED - Analysis Run (MiSeq i100 Series Sequencing v2.0)
* Automatic validation of run setup information before sample sheet generation or planned run creation.
* Automated creation of planned run with or without analysis and generation of sample sheet. Generated sample sheet is attached to the Load to Dry Cartridge step.
* Automated tracking of the MiSeq i100 Series sequencing run and parsing of run and lane metrics into Clarity LIMS.
* Automated tracking of Analysis run


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/clarity-lims/instruments-and-integrations/miseq-i100/miseqi100/miseqi100-v1.1.0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.