> For the complete documentation index, see [llms.txt](https://help.tillit.cloud/tillit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tillit.cloud/tillit/tools/aura/knowledge-base.md).
# Knowledge Base
The Knowledge Base is a collection of markdown notes that the Aura agents can use that is a structured, queryable, read+write knowledge base.
The internal markdown knowledge graph survives across cycles, captures your experts' feedback, and is browsable in the UI. It grows organically as agents and humans add notes.
## Initial Configuration - `facility_context.md`
Before Aura can run its first analysis cycle at your facility, one short configuration file needs to be filled in and returned to your Roima contact. Everything Aura needs to produce accurate, facility-specific findings depends on this file.
### What is it?
This is the most important file. Every Aura agent reads it before starting an analysis. It provides the facility-specific context that cannot be inferred from your MES data alone.
### What happens if I skip it?
Agents will still run, but their output will be generic rather than facility-specific. Specifically:
* The **CFO agent cannot calculate ROI accurately** without the Economics section - it will fall back to stated assumptions in each report.
* Agents won't know about **facility-specific exceptions** (e.g. a line that is intentionally idle on weekends) unless they are described in Analysis Guidelines
* **Quality thresholds** will fall back to generic OEE benchmarks (95% quality, 85% availability)
### Section-by-section guide
#### **Facility Overview**
A few bullet points describing your facility: what you produce, how many lines, shift pattern. This sets the scene for every agent.
#### **Line Capabilities**
A table listing each production line, its throughput, and what products it runs. Agents use this to put OEE numbers in context -- a 36,000 bph line losing 5% availability has a very different financial impact to a 6,000 bph line.
#### **Operation Flow**
The sequence of operations on each line from upstream to downstream, and which asset is the **pacemaker** (the asset that sets the rate for the whole line -- typically the Filler or primary processing machine). Agents use this to correctly attribute bottlenecks: is a downstream asset slow because it has a fault, or because the pacemaker is starving it?
#### **Economics (most critical for financial reports)**
This section drives every ROI calculation Aura produces.
* **Currency** - all financial figures in Aura reports will use this currency
* **Revenue per unit** - the customer-facing selling price (not manufacturing cost) for each product or product category. This is used to value lost production in every finding. For example: if the Filler runs at 36,000 bph and your average revenue is $14/bottle, a 30-minute unplanned stoppage equals 18,000 bottles of lost production - $252,000 of revenue opportunity lost to that single event.
* **Labour costs** - operator and technician hourly rates, used to estimate intervention costs
If you have many SKUs, a weighted average revenue per unit by category is sufficient.
#### **Analysis Guidelines**
Your chance to tell Aura what the data doesn't say. Common examples:
* "Line 3 does not run on weekends -- do not flag Saturday/Sunday downtime as unplanned"
* "The Filler 2 speed sensor was replaced on 2024-03-15; readings before that date are unreliable"
* "CIP cycles must be at least 45 minutes between product changes -- shorter cycles are a compliance risk, not a data error"
* "Line 1 Labeller has a known 5% reject rate pending a parts order (ETA 2025-08-01) -- exclude from reject rate trending"
The `facility_context.md` will then be split into structured documentation based on the sections above to give your agents a solid foundation to work on. Don't worry, these can be edited as part of the knowledge base!
## Questions?
Contact your Roima project lead for the `facility_context.md`. It will then be deployed into your Aura system and validation check can be run to see when your first cycle is ready. See more [here](https://www.roimaint.com/en/product/offering-by-product-aura-ai/aura-ai--aura).