Overview
Assets is the register of physical things that exist (or will exist) on the project — switches, antennas, cabinets, cables. Every asset has a type, and every type has a schema of attributes you control. That schema is what makes downstream automation possible.
The register is project-scoped, but types and their attribute schemas live at the organisation level. Once you have defined what a "Layer-3 Switch" looks like in your standards, every project on the platform speaks the same language.
You can populate assets manually, paste from a spreadsheet, drop them in via Block Diagrams, or have the AI propose entries from your equipment catalogue.
When to use it
- Whenever a project needs an equipment list (which is most of them).
- Standardising attributes across projects — power draw, MTBF, vendor part numbers, etc.
- Driving auto-generated Datasheets from a single source of truth.
- Feeding BoQ rollups without keeping a parallel quantity sheet.
How it works
1. Define your types
In your organisation settings, set up the asset types you actually use. For each one, list the attributes that matter — make/model, ports, power, weight. These show up as columns later.
2. Add assets
From the project, open Assets and add new rows. Required attributes are highlighted; missing ones surface as warnings rather than blockers.
3. Auto-populate
Click AI fill on a row to have the assistant pull values from your catalogue or vendor docs in the Knowledge Base. The AI will not invent values — anything it cannot find is left as [TBC].
4. Bulk operations
Multi-select to update tags, change locations or duplicate batches. The grid behaves like a spreadsheet for users who prefer that.
Tips
- Resist the temptation to invent a new type for every variant — three or four well-defined types beat thirty fuzzy ones.
- Keep attribute names short and consistent; they end up as headings on auto-generated documents.
- Use the Location attribute religiously — many downstream views (BoQ by zone, schedule by floor) depend on it.