The tank vs. bath distinction
- Tank = the physical vessel, bolted in place. It doesn't change.
- Bath = the chemistry currently in the tank. A tank can be dumped and refilled with new chemistry — same tank, new bath.
One tank → many bath records over time. Chemistry logs go against the bath, not the tank.
Menu: Plating → Configuration → Tanks.
Creating a tank
Click + New:
| Field | What to set |
|---|---|
| Name | Physical label (TK-EN-01) |
| Facility | Which plant |
| Work Centre | Which line |
| Volume (L) | Nominal working volume |
| Material | PVDF / poly / stainless — matters for chemistry compatibility |
| Heating | Steam coil / electric heater / none |
| Agitation | Air / mechanical / ultrasonic / none |
| QR Code | Auto-generated; print + affix |
| Permitted Chemistries | List of bath types this tank can hold (for accidental cross-contamination prevention) |
QR code
Every tank gets a QR sticker. When an operator scans it:
- On the tablet: opens the tank's chemistry-log entry form
- On a barcode gun: pulls the current bath's work order queue
Print QR codes from the tank form.
Permitted chemistries
A PVDF tank might be fine for hot acid and EN but never for chrome. Mark permitted chemistries so when someone tries to create a chrome bath in a PVDF tank, system blocks and explains.
Tank maintenance
Tab: Maintenance History:
- Cleaning (date, operator, notes)
- Liner inspection (visual, photos)
- Heater coil replacement
- Weld repairs
- Scrap / decommissioning
Maintenance cycles can be scheduled — next inspection due, next cleaning due.
Linking to baths
Plating → Operations → Baths — create a bath record that references a tank. Bath carries the chemistry. Tank just says "where".
Moving chemistry between tanks (rare but happens for maintenance):
- Dump bath A from tank 1.
- Clean tank 1.
- Decant bath B from tank 2 into tank 1 (if compatible).
- System tracks both transfers on the bath and tank histories.
What can go wrong
Chemistry added to wrong tank
Permitted-chemistries check should catch this. If it didn't: figure out how, update the tank's permitted list (or the bath-creation workflow), investigate as NCR if customer work was affected.
QR code illegible / scraped off
Generate a replacement from the tank form. Attach securely — not just a sticker on poly.
Tank taken out of service
Set status → Inactive. System warns if anyone tries to create a new bath in it. Don't delete — historical bath records need the tank reference.