> 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/dragen-protein-quantification/get-started/prerequisites/somaseq-automation-system-output-files.md).

# SomaSeq Automation System Output Files

The SomaSeq Automation System Output File (SomaSeqAS output file) is a .csv file that is produced after automated library prep is completed. The output file is saved on the Tecan PC in C:\OutputFiles with the filename format: `BatchID_PlateBarcode_output_OutputDate.csv`.

It contains the following fields:

<table><thead><tr><th width="264">Column Header</th><th>Description</th></tr></thead><tbody><tr><td>Lanes</td><td>Optionally contains information about lane splitting. Values are left blank by default. Refer to <a href="/dragen-protein-quantification/run-setup/lane-splitting-and-project-splitting.md">Lane Splitting and Multi-Analysis</a> by Project for more detail.</td></tr><tr><td>Sample ID</td><td>Identifier per sample. Specified in Sample Manifest prior to automation. For controls (QC, Blanks, Calibrators), the sample ID is pre-filled in the template files. ILASS appends a GUID to control Sample IDs to ensure uniqueness when combining plates.</td></tr><tr><td>Well Position</td><td>Well position of the sample with UDI set appended. Format: {Set}-{Well} (e.g., A-A01, B-H12). UDI set (A, B, C, or D) is determined by the barcode on the index plate scanned by the SomaSeq Automation System.</td></tr><tr><td>Project</td><td>Optionally contains information about what project the output file should contain. Multiple values are allowed and this field can be blank for all or some samples. Refer to <a href="/dragen-protein-quantification/run-setup/lane-splitting-and-project-splitting.md">Lane Splitting and Multi-Analysis</a> by Project for more detail.</td></tr><tr><td>PlateBarcode</td><td>Barcode associated with sample plate. Specified in Sample Manifest prior to automation. Min 8, max 36 alphanumeric characters. Dashes and underscores are permitted but cannot be the first or last character.</td></tr><tr><td>InputType</td><td>Sample input type. Permitted values: Blank, Plasma, Serum, CSF, or MultiMatrix-&#x3C;tissuetype> where &#x3C;tissuetype> is an alphanumeric string (max 36 characters). Specified in Sample Manifest prior to automation.</td></tr><tr><td>Control</td><td>The control type for the sample. Permitted values: Blank, Calibrator, QC, or empty (for non-control samples). If Control = Blank, then InputType must be Blank. For Plasma/Serum/CSF, if Control = QC or Calibrator, then InputType must match the respective sample type.</td></tr><tr><td>ControlID</td><td>Lot number for associated calibrator, QC, or blank sample. Generated by ILASS from information supplied on the Scan or Type Consumables screen. Expected format: NNNNNN.</td></tr><tr><td>KitType</td><td>The kit type associated with the sample plate. Permitted values: Plasma, Serum, CSF, or MultiMatrix. Generated by ILASS from the Kit Type selected on the Define Batch screen.</td></tr><tr><td>BatchID</td><td>User-provided batch identifier. Generated by ILASS from the Batch ID supplied on the Define Batch screen. No commas or asterisks allowed.</td></tr><tr><td>ProbePlate</td><td>Proteomics Probe Plate barcode scanned during library prep. The last two characters indicate the Probe Pool Lot (e.g., "-AA" or "-AB").</td></tr><tr><td>SOMAmerBeadPlate</td><td>SOMAmer Bead Plate barcode scanned during library prep. For Plasma/Serum/CSF sample types, this is the SOMAmer-Bead Plate 11K v5.0 Dil1 barcode (format: SBP1-XXXXXXXXXX). For MultiMatrix sample types, this is the SOMAmer-Bead Plate 11K Single Dilution barcode (format: MBP-XXXXXXXXXX).</td></tr><tr><td>MatrixTubeBarcode</td><td>Barcode associated with matrix tube. Specified in Sample Manifest prior to automation. Min 5, max 36 alphanumeric characters. This field is optional.</td></tr><tr><td>ScriptsVersion</td><td>Version of automation scripts referenced by ILASS (e.g., 3.1.5, 3.1.6).</td></tr></tbody></table>

The SomaSeq output file is accepted as an input by the Run Planning tool or local DRAGEN server, which populates information required to generate the sample sheet.


---

# 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/dragen-protein-quantification/get-started/prerequisites/somaseq-automation-system-output-files.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.