Documentation Index
Fetch the complete documentation index at: https://docs.firstresonance.io/llms.txt
Use this file to discover all available pages before exploring further.
Overview
A part in ION is the catalog entry — the design intent. It carries a unique part number, a revision, a description, and a set of properties that govern how the part is purchased, tracked, and built. Parts are not physical units on the shelf; that’s part inventory. A clean parts catalog is the foundation everything else stands on:- Bills of materials are graphs of parts.
- Procedures assemble parts into other parts.
- Runs consume parts and produce parts.
- Purchase orders buy parts.
- Issues can attach to parts and to inventory of parts.
What’s in this section
| Page | What it covers |
|---|---|
| Creating and managing parts | Add a part, edit it, archive it, and how revisions work |
| Attributes and custom fields | Built-in attributes (cost, lead time, sourcing strategy) plus org-defined custom fields |
| Serial and lot tracking | Pick the right tracking type and what each one means downstream |
| Inventory and search | Find parts in the catalog and reach their inventory |
The mental model
Three concepts to keep straight:- Part — the catalog row.
BRKT-001 Rev Bis a part. It has a part number, a revision, a description, attributes, and zero-or-more subtypes. - Part inventory — a physical instance of a part. A serial-tracked unit, a lot, or a quantity at a location. Inventory references a part; one part has many inventory rows.
- Part subtype — a categorization tag attached to a part. Parts can have multiple subtypes (e.g. “critical-to-quality”, “long-lead-time”). Subtypes are how you group parts that share routing, inspection, or planning behavior.
Subtype is not the same as revision. A new revision creates a new part (linked to its predecessor via a revision lineage); a subtype just tags an existing part.
Where parts surface in the app
Parts show up everywhere:- Parts page — the catalog browser. Search, filter, create new parts, manage existing ones.
- Bill of materials — every BOM line is a part requirement.
- Procedure step — steps can require parts to be installed during execution.
- Run — runs build a target part and consume input parts.
- Purchase order line — every PO line is a part to be purchased.
- Issue — issues can be filed against a specific part or part inventory.
Tips
- Decide tracking type before creating inventory. Switching a part from untracked to serial after units exist is painful; pick the right type at part-creation time. See Serial and lot tracking.
- Use revisions for design changes, subtypes for categorization. A new revision means the design intent changed; a subtype means the part fits a category (commodity code, criticality, etc.). Don’t conflate them.
- Set realistic lead times. Lead time on the part record drives planning and reorder behavior across procurement, MRP, and Autoplan. A wrong number propagates.
- Archive instead of delete. Parts that are out of production should be
archived, not removed — historical runs and BOMs reference them.