RUSTNET A bolt-on. Not another ERP.
Two screens. A traveler from the print. A list of what will bite you.
Drop the PO and print. Confirm the traveler. Then see the few jobs and vendor POs that need a call today.
REQUIRED
BODY, MACHINED
TWO SCREENS ONLY
Start the work. Watch the trouble.
RustNet stays narrow on purpose. No jobs board. No quoting screen. No capacity chart.
INTAKE
A traveler from the packet.
Drop a customer PO and drawing. Or an RFQ and drawing. Sparks reads the packet and suggests how the shop could run it.
- Routing and machines
- Setup time versus cycle time
- BOM, buy items, and hardware
- Inspection and outside process
Multi-line POs and assemblies become one traveler per make-item. Buy, hardware, and stock stay on the BOM.
WATCH
The short list that needs a look.
Watch reads the ERP and puts the hottest exceptions first. It is not a dispatch board. It shows what may bite the due date.
Click an exception to see the next check.
Vendor email: draft + confirm. Never auto-send.RustNet never writes the ERP database. It never sends mail without a person confirming it.
HOW A PACKET MOVES
Four stops. The clerk still releases the job.
- 01PO + printDrop the shop packet
- 02Confirm make / buyOne decision at a time
- 03Review travelersOne per make-item
- 04Release in the ERPThe clerk owns release
ASSEMBLIES DONE STRAIGHT
The numbers come from the ERP. The family stays tied together.
A top assembly gets one traveler. Each make-item below it gets its own. The parent waits on the children.
GO/NO-GO and laser mark are inspection or process steps—not extra jobs. Edge break happens before anodize, paint, or plate. PEMs and helicoils go in after anodize.
| ERP job | Level | Item | Result |
|---|---|---|---|
| 22980-01 | TOP | Pump bracket assy | Traveler |
| 22980-02 | └─ MAKE | Machined body | Traveler |
| 22980-03 | └─ MAKE | Clamp block | Traveler |
| — | └─ BUY | PEM nut, zinc | BOM only |
| — | └─ STOCK | 6061 plate | BOM only |
HOW IT FITS YOUR ERP
A clean handoff. No SQL writes.
RustNet sits beside the ERP. It does not replace the system of record and does not write into its database.
Reads the packet.
Suggests the work.
Reads ERP exceptions.
Owns job numbers.
Clerk imports.
Clerk releases.
NO direct SQL writes
NO invented job numbers
NO automatic release
NO second dispatch board
FOR THE SHOP
Less retyping. Fewer surprises. Same ERP.
PLANNER
Travelers that match the way the floor runs.
Start from the print, then fix the suggestion. Machines, times, outside work, inspection, and the order they belong in.
CLERK
ERP job numbers. No invented jobs.
Review the handoff. Import what belongs. Release in the ERP when the packet is ready.
OWNER
Exceptions instead of another board.
See the late work, the almost-late work, and the vendor promise that needs a call. Hottest first.
REQUEST A WALKTHROUGH
Bring one packet. We’ll walk it like your shop does.
No canned demo. No fake pricing page. Tell us your role and where a PO-to-traveler handoff gets slow.
- Your packet and traveler flow
- Make / buy and assembly handling
- The exceptions worth watching