That part's only record is a traveller in a binder.

Inspection entries sit in the QMS, the traveller in a binder, the revision in PLM. We read all three where they sit, so the lot history already exists when someone asks, and the systems you certified stay as they are.

Book a demo See the platform
  • LOT-7731Lot history, built from the record Ready

The picture today

The lot history is assembled by hand

Inspection entries live in the QMS. The traveller lives on paper. Assembling a lot history means someone stitching both together by hand.

Your shop's systems stay exactly where they are

  • ERP Work orders, part numbers and due dates. Every job carries the order it belongs to.
  • Quality system (NCRs, first article inspection) Non-conformances, deviations and first article results. A hold is tied to the part, lot and job it touches.
  • PLM Drawings and engineering revisions. The record shows which revision built the part.
  • Inspection and CMM data Measurement results against the print. A reading is stored with the part and who took it.
  • Travellers and paper records The router that rides with the job. The paper trail becomes a form nobody re-keys.
  • Supplier portals or spreadsheets Supplier certifications and the schedule kept in Excel. Read in place until you're ready to retire them.

What happens the next time someone asks

A deviation above the limit waits for a person's yes.

Authority Matrix + Governance + Approval Queue

The Authority Matrix sets what an Agent may do alone. Governance stops anything past it before it runs. The Approval Queue holds it for a person and keeps who decided and when.

See how it works

Connected

  • CMM
  • Quality system
  • ERP

The modules, in order

  1. Authority MatrixSets what an Agent may do alone.
  2. GovernanceStops anything past it before it runs.
  3. Approval QueueHolds it for a person and keeps who decided and when.

What you see

  • Deviation approvalQuality Manager and above On
  • Concession request: DEV-0217 Above the Agent's authority Waiting 1d 4h
  • Approved by M. Laurent 10:12

A non-conformance closes only when the fix is verified.

Investigation Engine + Historian

The Investigation Engine records the cause and the countermeasure. The case can’t close until each countermeasure is signed. The Historian keeps the readings the case points back to.

See how it works

Connected

  • CMM
  • Quality system
  • MES

The modules, in order

  1. Investigation EngineRecords the cause and the countermeasure. The case stays open until each one is signed.
  2. HistorianKeeps the readings the case points back to.

What you see

  • NCR-0932 Issue Cause established Countermeasure 2 of 3 signed
  • Similar past case: burr on bore, Cell 4

The lot history is ready before the audit asks.

Integration Hub + Historian + Form Builder

The Integration Hub reads the ERP, quality system and PLM in place. Inspection entries become a form instead of a binder page. When the prime asks, you send the file instead of building it.

See how it works

Connected

  • ERP
  • Quality system
  • PLM

The modules, in order

  1. Integration HubReads the ERP, quality system and PLM in place.
  2. HistorianKeeps every reading, state and count with its timestamp.
  3. Form BuilderTurns inspection entries into a form instead of a binder page.

What you see

  • Lot 4471 Plant 2 Machining Cell 4 WO-118390
  • Lot 4471 record Traveller signed CMM logged NCR closed
  • 212 readings, 3 forms, 1 NCR
  • Orders received today 17

Inbound orders

Read the ERP, the QMS, the PLM and the traveller in place

The Integration Hub reads the systems where they are, and the inspection record in the binder becomes a form. Nothing is migrated and nothing is re-keyed.

  • Every inspection entry stored with the part, lot and work order
  • Set up with your team, one system at a time
  • Deviation above threshold, needs a person
  • RULE-014 change history Escalate after changed to 4h Value threshold changed Rule created, active

Audit trail

Set who can act, and keep every decision on record

The Authority Matrix sets what each Agent may do alone. Role access sets what each person can reach. Governance checks every Agent action before it runs and keeps the decision.

  • Agent authority set per action, with conditions like a line or shift
  • Anything past it waits in the Approval Queue for a person's yes
  • Every check recorded with who, when and what was decided
  • INV-0311, weld porosityClose blocked, Severity 2 8d 0h
  • 3 sign-offs still open

Case close-out

Trace a non-conformance to its cause and carry the fix

The Investigation Engine records causes and countermeasures with their evidence. The case moves stage by stage and can’t close until the countermeasures are signed.

  • Past causes and countermeasures pulled up for the case
  • Closure gated on the countermeasure being verified
  • The case stays open until the effectiveness check passes
  • Same history, every Module

Lot history

Produce the lot history on demand

The Historian keeps every reading, state and count with a timestamp, so the record an audit asks for already exists.

  • Every reading kept by time, asset and run
  • The same history read by every Module
  • Start with one shop, usually with the record and investigations

Add the next Module when this one pays for itself.

The Modules aerospace and defence runs on

They collect and keep what your shop knows.

  • Historian: every reading, state and count, kept by time, asset and run.
  • Integration Hub: the connections to your ERP, quality system and PLM, wired with your team, with every exchange logged.
  • Governance: every Agent action checked against the authority you set, with the decision kept.
  • Form Builder: the inspection entries and checks that used to live in the binder.

So what: the traveller, the NCR and the inspection result sit on the same part record.

See the Foundational Modules

/01

Built and owned in Canada

If your prime carries Industrial and Technological Benefits obligations, where the work is placed counts.

Your data stays in the country you choose, Canada or the US. Every Agent action and every sign-off stays on record for a regulator.

How we'd work with you

Start with a conversation, one Module, or the whole operation. The same team stays from the Scorecard to go-live and after.

  1. Step 1

    The Scorecard

    Two to four weeks with access to your systems, and no platform purchase. You see where your data lives, where it doesn't, and what the gaps cost.

  2. Step 2

    Connect and lay the foundation

    Foundational Modules go in first. We connect the systems you already run, one at a time, starting with the one the roadmap says pays first.

  3. Step 3

    Turn on the engines

    Workflow Modules start working on that record: the investigation, the corrective action.

  4. Step 4

    Add the Agents

    Agents take on the routine work, inside the authority you set. Anything outside it waits for a person.

  5. Step 5

    We stay

    Your people run it on their own screens. We stay for the next problem, and what your senior inspectors and machinists know gets written down along the way.

FAQ

Bring the lot history you dread pulling.

30 minutes on your systems and the record you have to prove. We'll show you where we'd start.

Book a demo