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

This page walks through the day-to-day of curating the parts catalog: creating a new part, setting its core fields, revising it when the design changes, and archiving it when it’s no longer in use.

​
Prerequisites

  • Permission to create and edit parts in your organization.
  • A part number from your engineering team’s numbering scheme (or ION’s auto-numbering, if your org uses it).

​
Creating a part

  1. Navigate to Parts from the main nav.
  2. Click New Part.
  3. Fill in the required fields:
    • Part number — your org’s identifier for the part. Must be unique within the org for a given revision.
    • Revision — the engineering revision (typically a letter, e.g. A, or your org’s revision scheme).
    • Description — free-form description of what the part is.
    • Part type — Part for a buildable / purchasable item, or Tool for a tool used during builds.
    • Tracking type — Serial, Lot, or Untracked. See Serial and lot tracking before you pick.
  4. Optionally set:
    • Sourcing strategy — Make, Buy, or Dual source.
    • Purchase type — for parts that are purchased: receivable inventory, receivable non-inventory, or non-receivable non-inventory.
    • Cost, Lead time, Reorder min/max — planning fields.
    • Subtypes — categorization tags (see Attributes and custom fields).
    • Thumbnail — an image attached to the part for visual ID.
  5. Click Create. The part lands with status = Released.
Part number + revision is the unique identity. You can have two parts with the same partNumber only if they have different revisions. The catalog enforces this at create time.

​
Editing a part

Open the part from the catalog. Most fields are editable in place — change a value, save. Some fields have downstream consequences:
  • Tracking type — changing this after inventory exists is constrained. ION blocks switches that would invalidate existing inventory rows.
  • Sourcing strategy — flipping Buy → Make changes how procurement and MRP treat the part. Coordinate with the planning team.
  • Cost — propagates to BOM cost rollups and inventory valuation.
  • Lead time — feeds Autoplan and reorder logic.
Every save updates the part’s _etag for optimistic concurrency. If two people edit the same part simultaneously, the second save will be rejected with a 409 — re-load the part and re-apply.

​
Revisions

Engineering revisions create a new part record linked to the previous one. The lineage matters: historical runs and BOMs continue to reference the older revision, but new builds pick up the latest. To create a new revision:
  1. Open the existing part.
  2. Click New Revision.
  3. Confirm the new revision letter and what changed.
  4. ION creates the new part record, links it to the predecessor (revisedFromId), and copies forward editable fields. Edit anything that the design change requires.
The previous revision stays in the catalog but is typically not selected for new BOMs. Archive it when no in-flight builds reference it.

​
Archiving a part

When a part is out of production:
  1. Open the part.
  2. Click Archive.
  3. Confirm.
status flips to Archived. The part remains queryable and historical references stay intact, but it’s filtered out of “active part” pickers (BOM line creation, PO line creation, etc.) by default.
Don’t delete parts. ION uses soft-archive intentionally — runs, issues, BOMs, POs, and inventory all reference the part by ID. A hard delete would orphan years of history.

​
Bulk operations

For large-scale changes (importing a thousand parts from an ERP, reclassifying subtypes across a category, etc.) use Data Import under Manage Supply Chain. It’s idempotent and gives you a dry-run mode to preview impact before applying. For programmatic part management, see Common Queries → Create a Part.

​
Tips

  • Lock down the numbering scheme up front. Inconsistent part numbers (brkt-001 vs BRKT-001 vs BRKT001) are the most common catalog hygiene issue. Pick a convention and enforce it via Data Import validation.
  • Use revisions, not edits, for material changes. If the part’s geometry, fit, or function changed — that’s a new revision, not an edit. Editing the existing revision rewrites history.
  • Set the thumbnail. It’s a small thing that pays off every time someone scans a list of fifty parts and tries to find the right one.