Skip to main content

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

Every part has two kinds of properties:
  • Built-in attributes — fields ION ships out of the box: part number, revision, description, cost, lead time, sourcing strategy, etc.
  • Custom fields — fields your org defines for your domain: criticality rating, RoHS status, customer-facing SKU, color, finish, anything that’s specific to how you run.
This page covers both, plus the subtype mechanism for tagging parts into categories that share routing, inspection, or planning behavior.

​
Built-in attributes

These ship with every part:
FieldNotes
Part numberOrg-unique within revision. Required.
RevisionEngineering revision letter or string. Required.
DescriptionFree text, up to 512 characters.
Part typePart or Tool.
Tracking typeSerial, Lot, or untracked. See Serial and lot tracking.
StatusReleased or Archived.
Sourcing strategyMake, Buy, or Dual source. Drives MRP and procurement.
Purchase typeReceivable inventory, Receivable non-inventory, or Non-receivable non-inventory.
CostOptional. Used for BOM rollups and inventory valuation.
Lead timeOptional. Drives reorder timing and planning.
Reorder min / max quantityOptional. Triggers reorder workflows when on-hand drops below min.
Maintenance intervalOptional. For tool parts that need scheduled maintenance.
Supplier part numberOptional. The vendor’s identifier for this part.
Export controlledBoolean. Controls whether the part is visible to users without export-control permission.
Revised fromReference to the part this revision was created from. Auto-set when you click New Revision.

​
Subtypes — categorization

A part subtype is a tag attached to a part. A part can have multiple subtypes. Subtypes are how you group parts that share an attribute or behavior:
  • “Critical-to-quality” — parts that drive a quality-tracking workflow.
  • “Long-lead-time” — parts that need extra planning.
  • “Mounting hardware” — parts that share an inspection routing.
  • “Customer-supplied” — parts that came from a specific customer’s inventory.
Subtypes are defined at the org level by an admin, then attached to parts on the part page or via Data Import.
Subtype is not the same as part family. ION doesn’t have a strict tree-shaped “family” concept. Subtypes are flat tags; a part can be in any number of subtypes simultaneously.

​
Creating a subtype

Admins create subtypes from Organization Settings → Part Subtypes:
  1. Click New Subtype.
  2. Give it a name and (optional) description.
  3. Save.
The subtype is now available for attachment from any part page.

​
Attaching subtypes to parts

From the part page, open the Subtypes section and select one or more subtypes from the picker. Subtypes can be attached and removed without affecting downstream BOMs or runs — they’re metadata.

​
Custom fields

When the built-in attributes don’t cover what you need, custom fields fill the gap. They’re org-defined, attach to parts, and behave like any other queryable property.

​
Defining a custom field

Org admins define custom fields:
  1. Navigate to Organization Settings → Custom Fields → Parts.
  2. Click New Custom Field.
  3. Set:
    • Name — what users see.
    • Type — text, number, date, single-select, multi-select, file, or boolean.
    • Required — should it block part creation if empty?
    • Default — optional default value at part creation.
  4. Save. The field now appears on every part page.

​
Setting a custom field value on a part

From the part page, scroll to the Custom Fields section. Each defined field renders an appropriate input. Save, and the value is stored on the part.

​
Custom fields vs subtypes — when to use which

You want to…Use
Tag the part with a category (no value, just membership)Subtype
Store a per-part value (a number, date, free-form text)Custom field
Group parts that share routing or inspectionSubtype
Capture a customer-specific SKU or revision identifierCustom field
Store a flag like “RoHS compliant”Custom field (boolean) — or a subtype if you’d rather pick from a controlled list
A rough rule: if every part needs a value for the property, custom field. If only some parts have the property and it’s binary membership, subtype.

​
Tips

  • Don’t recreate built-ins as custom fields. If Lead time is what you need, use the built-in field — it integrates with planning. Adding a custom Lead Time field bypasses MRP.
  • Keep subtypes few and meaningful. A subtype that applies to 90% of parts isn’t useful as a filter. Aim for subtypes that partition the catalog into actionable groups.
  • Mark customer-driven custom fields clearly. When custom fields exist primarily to satisfy one customer’s data needs, name them to indicate that context (e.g. Customer-X SKU) so future operators don’t get confused.