Solutions / Manufacturing

AI automation for job shops and make-to-order manufacturers

The quote was built against one revision and the drawing in the operator hand is another, which is the defect this sector is built around.

A request to quote arrives as an archive of geometry files and drawings, or as a line in a customer portal, or as a scan. An estimator opens each one, decomposes the part into operations mentally, estimates setup and run times, and emails suppliers for material pricing before typing a number into a spreadsheet.

The traveller that follows is usually paper, and the paper is authoritative. Sign-offs, red-pen deviations and instructions to speak to a specific person before an operation exist only on that sheet. Nothing digital knows about them, and if the folder is at the wrong machine the job is invisible.

Traceability breaks at physical handling rather than in software. Material is cut and the remnant returns to the rack without its heat identifier attached. Months later a job needs a certificate tying material to a specific melt, and nobody can prove which one that remnant came from.


Figure 01 / the ground

What this work runs through

Systems / commonly in place Yours may differ, and that is the point of week one
  • JobBOSS2
  • Epicor Kinetic
  • Paperless Parts
  • MachineMetrics
  • Excel
  • EDI over a VAN

Artefacts that move through the business

  • Request to quote, arriving as geometry plus drawings
  • Traveller or router, which is usually paper and usually the master
  • Bill of materials and routing, both carrying revision levels
  • Material test report tying a batch to certified properties
  • First article inspection package, one row per drawing characteristic
quoting
Quoting and estimating
documents
Documents and records
compliance
Compliance and audit
scheduling
Scheduling and dispatch
reporting
Recurring reporting

Figure 02 / where it breaks

The specific things that go wrong here

The quote and the shop floor disagree about revision

An engineering change moves the part while a traveller printed weeks ago still carries the earlier drawing. The operator machines to the print in hand. It is a document control failure rather than a skill failure.

Estimated against actual never closes

Job costing exists in every one of these systems, but when operators write times in pen and somebody keys them in later, the comparison is fiction. The next quote for the same part then repeats the same wrong assumption.

Machine monitoring can observe but not command

The common shop-floor protocol is read only by design. You can watch a machine, not instruct it. Older controls predate it entirely and need sensors that infer state rather than report it.

Outside processing is a hole in the schedule

The job leaves the building for heat treat or plating and the system continues to show it sitting at an operation for the whole two weeks.


Figure 03 / candidates

What we would automate, and when we would not

cert package

Assembling a certificate package at shipment

Collecting material certificates for every heat used, outside process certificates, and the inspection record, then checking that the heat identifiers on the certificates match what was actually pulled from stock.

Runs against JobBOSS2 / Epicor Kinetic / Excel

mtr receiving

Filing a mill test report against the heat received

Bars arrive on Tuesday and the certificates arrive on Friday, as a PDF attached to a mail from the service centre, often covering several heats in one file.

Runs against Outlook / JobBOSS2 / Excel

downtime coding

Attaching a reason to every unexplained machine stop

The protocol that most controls speak is read only by design, which means it can report that the spindle stopped at eleven and not why.

Runs against MachineMetrics / JobBOSS2 / Google Sheets

outside process chase

Chasing parts sitting at the plater or heat treater

Parts leave on a Thursday with a purchase order for the service and a packing list, and the system keeps showing the operation as open until somebody receives them back.

Runs against JobBOSS2 / Outlook / Epicor Kinetic


Constraint / why a person stays in the loop Checked against your own jurisdiction

Quality certification is the constraint that shapes everything here. Document control requires that the current version is available where it is used, that changes are tracked, and that records are retained, so any automation which creates, moves or supersedes a controlled document has to preserve version history and an audit trail or it breaks the certification itself and not only the workflow. Aerospace work adds unique identification and documentation linking each item to its source material and production batch, and defence work adds export control, where technical data may not be accessible to foreign persons including through cloud storage and vendor support access. That last one decides which services may touch the files at all, and it is checked with the export control officer rather than assumed.

Related: Construction and contracting Logistics and freight. Or start from the four shapes of work instead of from an industry.