Skip to main content

​
What ION does for you

ION gives you data: engineering data (torques, voltages, dimensions captured during build), production data (shifts, machines, operators, sensors), and quality data (issues, dispositions, CAPAs), all in one model, all queryable. Instead of stitching exports from MES, QMS, and ERP every audit cycle, you point at one system. The same data is in the API, so you can build dashboards, reports, and statistical analyses without waiting on someone to extract a CSV. Day-to-day you’ll be working issues: triaging incoming NCRs, pushing parts through their disposition workflow, owning CAPAs, and feeding root-cause findings back into design and process.

​
Where to start

  1. Issues and NCRs: the heart of your day. Lifecycle, dispositions, resolutions.
  2. Containment: what to do the moment a defect surfaces.
  3. Further Actions (CAPA): corrective and preventive action, tracked through to verification.
  4. Quality reporting: yield, escape, NCR-by-cause analytics.

​
The handful of pages that matter most

PageWhy it matters to you
Issue LifecycleThe state machine your tickets live in
As-built BOM (aBOM)The traceability record. Every quality investigation starts here.
Redlines and DeviationsA leading indicator of defects, and a recurring one means a process problem
Reference DesignatorsPosition-coded installs make “wrong part in R7” detectable, not forensic
Further Actions (CAPA)The feedback loop into process and design
Analytics and DashboardsBuild the reports you need without IT involvement
API referenceWhen the dashboards aren’t enough and you need raw data
  • The aBOM is your forensic tool. Every field failure investigation starts at the as-built BOM of the failing unit. Get fluent with how to walk it from a serial number all the way down to lot codes of the components installed.
  • Watch redline rate, not just NCR rate. A high redline rate on a procedure means floor reality and the spec disagree, even if no NCRs have been filed yet. That’s a leading indicator.
  • Close the CAPA loop. Verification is the only step that proves the corrective action actually worked. Skipping it means the CAPA is theater.
  • Data lives in the API. When the built-in dashboards stop fitting, GraphQL is the next stop. See API reference → Common Queries.