Academy · VIDEO
Setting up Niyamis TMS in a GibbsCAM shop — a 10-step walkthrough
The technical on-ramp for GibbsCAM shops. Video walkthrough plus a 10-step checklist that takes you from installed GibbsCAM to a running Niyamis TMS instance with your assemblies imported.
Philippe, Niyamis · 10 min watch
Watch the walkthrough
10 minutes · narrated by Philippe, Niyamis
Who this is for
You already run GibbsCAM. You have assemblies defined, Gibbs ID sequences running (BT40, HSK63, or both), and a team that knows its way around the post. You want Niyamis TMS to complement that workflow, not replace it. This walkthrough is the shortest path from "installed GibbsCAM" to "TMS showing live scorecards on the assemblies your shop already uses."
The 10-step checklist
1. Confirm GibbsCAM version ≥ 14
Niyamis TMS's GibbsCAM integration reads the assembly + Gibbs ID metadata that version 14 formalised. If you're on v13 or older, upgrade first — we'll co-ordinate with your VAR if helpful.
2. Export a sample assembly
In GibbsCAM, export one representative assembly using the TMS post. The
export produces a .mac file plus a manifest that TMS can ingest. Pick an
assembly you run regularly — 20–30 parts/month is a good sanity-check
volume.
3. Stand up Niyamis TMS
Niyamis hosts your TMS instance. During the Diagnose phase we provision a
tenant for your shop and send you two URLs: app (the web UI) and api
(the REST endpoint and upload target). Both are HTTPS-only.
4. Upload the sample
Drop the .mac + manifest into the crib UI's Import tab. TMS parses
the assembly, creates the tool records with your Gibbs IDs preserved, and
renders the 3D geometry. A failed import gets you a specific error — not a
500. Ping Niyamis if anything looks off.
5. Reconcile IDs
Open the imported assembly. TMS's sidebar shows the GibbsCAM IDs alongside TMS's internal IDs. You shouldn't need to change anything here — the point is to verify the mapping is what you expect. Click through a few assemblies to sanity-check.
6. Import PO history
Upload your last 18 months of PO history as CSV (TMS provides a template matching the standard Xero / MYOB export shapes). The scorecards need this data; without unit prices and receive dates, cost-per-part math doesn't work.
7. Import transaction history
Upload the TAKE / RETURN / SCRAP / REFILL log from your current crib system. We support CribMaster, Zoller TMS, and plain Excel. TMS validates each row against the imported assemblies and flags any references to unknown tool IDs — which usually means either an ID drift between the crib and CAM, or a retired SKU that's no longer in the assembly set.
8. Configure alert thresholds
In the crib UI, for each location, set min / max / reorder-point values. Start with the numbers your current crib system uses; TMS will tune them after a few weeks of observed demand. The alert inbox is shared — your toolroom supervisor and the Niyamis consultant on your account both see the same list.
9. Set up the terminal
On the shop-floor terminal hardware, point the browser at the terminal URL Niyamis provides and log in as an ADMIN user. Walk through a TAKE, a RETURN, and a SCRAP using a real tool to verify the flow. If your shop uses RFID cards, pair one now — it's a two-step setup from the admin menu.
10. Turn on scorecards
Once a week of transaction data has landed, the Brand Scorecard begins populating. The Dashboard shows which SKUs have enough data to trust (green confidence) and which are still building history (amber). Expect two to three weeks before the scorecards are rich enough to drive PO decisions, and longer for low-volume SKUs.
What Niyamis does alongside these 10 steps
Every step above has a Niyamis-side equivalent. During the Diagnose and Deploy phases (weeks 1–6 of the engagement), a consultant is on your floor for a day or two each week, walking through these same steps with your team live. The checklist is the self-serve version for shops that want to move faster between our visits.
Troubleshooting
The most common hiccups:
- Gibbs ID collisions. If you have two BT40 sequences running (legacy + current), TMS will flag the duplicates on import. Merge them in GibbsCAM before continuing.
- CSV encoding. PO history exported from some older ERPs lands as Latin-1. TMS expects UTF-8. Re-save in Excel with "CSV UTF-8 (comma delimited)".
- Browser on the terminal. Chromium ≥ 114 works. Edge, Chrome, and Brave are all fine. The terminal is not supported on IE or very old Safari.
Next step
Book a thirty-minute call with Philippe once you've exported a sample assembly — we'll walk through the import live on your screen.
— Philippe, Niyamis