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.

SUGGESTED TRAVELER FAMILY PO 87041 · LINE 10
REVIEW
REQUIRED
TOPJOB# 22980-01

PUMP BRACKET ASSY

10ASSEMBLEWaits on 02
20FINAL INSPECTGO / NO-GO
MAKEJOB# 22980-02

BODY, MACHINED

10MILL0.8 / 0.12 hr
20EDGE BREAKBefore anodize
30ANODIZEOutside
BUY / BOM ONLY 4× PEM NUT · install after anodize
Sparks suggestionNOT RELEASED
01

TWO SCREENS ONLY

Start the work. Watch the trouble.

RustNet stays narrow on purpose. No jobs board. No quoting screen. No capacity chart.

SCREEN 1LOCAL DOCUMENTS

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.

SCREEN 2READ-ONLY ERP

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.

HEATEXCEPTIONDUE
SUGGESTION

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.

02

HOW A PACKET MOVES

Four stops. The clerk still releases the job.

  1. 01PO + printDrop the shop packet
  2. 02Confirm make / buyOne decision at a time
  3. 03Review travelersOne per make-item
  4. 04Release in the ERPThe clerk owns release
03

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.

SHOP KNOWLEDGE

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.

Suggested traveler family for PO 87041
ERP jobLevelItemResult
22980-01TOPPump bracket assyTraveler
22980-02└─ MAKEMachined bodyTraveler
22980-03  └─ MAKEClamp blockTraveler
—  └─ BUYPEM nut, zincBOM only
—└─ STOCK6061 plateBOM only
HOLD 22980-01 waits until 22980-02 and 22980-03 are complete.
04

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.

LOCAL SHOP MACHINE RUSTNET

Reads the packet.
Suggests the work.
Reads ERP exceptions.

REVIEWED HANDOFF JSON · CSV · PDF
SYSTEM OF RECORD YOUR ERP

Owns job numbers.
Clerk imports.
Clerk releases.

NO direct SQL writes

NO invented job numbers

NO automatic release

NO second dispatch board

05

FOR THE SHOP

Less retyping. Fewer surprises. Same ERP.

01

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.

02

CLERK

ERP job numbers. No invented jobs.

Review the handoff. Import what belongs. Release in the ERP when the packet is ready.

03

OWNER

Exceptions instead of another board.

See the late work, the almost-late work, and the vendor promise that needs a call. Hottest first.

06

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.

WHAT WE COVER
  • Your packet and traveler flow
  • Make / buy and assembly handling
  • The exceptions worth watching

Running an ERP today?

A person from Rustforge follows up. No trial funnel.