> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/features/parts-and-trace/trace-aboms/editing-abom-build-requirements.md).

# Editing aBOM build requirements

Edit the requirements of the aBOM called "build requirements"

## Adding and removing requirements

Build requirements can be added to the aBOM if additional parts are required to be installed. This is the equivalent of redlining for aBOMs.

<figure><img src="https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-ed826a8498d3e8a67c7790ca7490007dfcd7a77f%2F2024-01-08%2021.54.30.gif?alt=media" alt=""><figcaption></figcaption></figure>

As shown above, manually created build requirements can also be removed when editing the aBOM. If a build requirement is associated to a mBOM item, it cannot be deleted to help you compare the final aBOM state to the mBOM. You can, however, zero out the quantity of those build requirements you no longer need that are associated to mBOM items. Build requirements with a quantity of zero will not count towards the aBOM completion percentage.


---

# 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://manual.firstresonance.io/features/parts-and-trace/trace-aboms/editing-abom-build-requirements.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.