Overview
Datasheets renders one document per device using the attributes already captured in Assets. You define the template once — header, footer, attribute placement — and every datasheet on the project follows it.
The generation is deterministic: the same input produces the same output. There is no AI invention in the body of the datasheet; the AI only helps when you ask it to fill missing attributes from your knowledge base.
When to use it
- Submittals where the client wants one PDF per piece of equipment.
- O&M packs at handover.
- Anywhere your standards require formal datasheets but the underlying data already lives in the asset register.
How it works
1. Build a template
Upload a Word or PDF template with placeholders that map to attribute names — for example {{make}}, {{model}}, {{ports}}. Templates live at the organisation level so projects share them.
2. Pick assets
Multi-select assets in the register and choose Generate datasheets.
3. Review missing attributes
The system flags any asset that lacks a required attribute. You can fix the asset, accept a [TBC] placeholder, or have the AI propose a value from your catalogue.
4. Export
One datasheet per asset, packaged as a zip. PDF and DOCX are produced in the same run.
Tips
- Keep the template focused on what the client actually reads. A two-page datasheet beats an eight-page one almost every time.
- Use the same placeholder names as your attribute names — naming hygiene pays off here.
- Generate datasheets late; the asset data is rarely settled before then.