Service jobs
Equipment in for inspection, testing or repair. Customer complaint, scope of work, assigned engineer, priority, fitness status and final conclusion — linked back to the quotation, sales order or delivery it belongs to.
The workshop floor and the service bay, with the measurements and the stock ledger that come out of them — built for work that has tolerances, materials and mileage.
Equipment in for inspection, testing or repair. Customer complaint, scope of work, assigned engineer, priority, fitness status and final conclusion — linked back to the quotation, sales order or delivery it belongs to.
Reusable specification, inspection and test templates per equipment type. Add an item to a job and its standard checklist instantiates itself, so two engineers test the same equipment the same way.
Entries are typed — assessment, inspection, test, progress, part, conclusion — and a test entry records method and tool, initial and final value, unit, tolerance and result. Before-and-after photos flag individually for inclusion, and the whole job prints as a consolidated service report.
Per machine, per shift, with downtime minutes and reason, and per-line quantity produced, waste quantity and rejection reason. Entries move Draft → Submitted → Locked.
A two-level parent-SKU to sub-SKU hierarchy with auto-generated codes, carrying size, material, pressure rating, length and unit of measure. Each sub-SKU maps to its raw materials through a versioned bill of materials.
Every movement is a row: goods received, production in, production out, sale out, adjustment, return in — each with quantity in, quantity out and the running balance after it. Reorder levels drive an out-of-stock, low-stock and in-stock view on the dashboard.
Machine register with status — active, inactive, under maintenance — and the parent and sub-SKUs each machine is capable of running.
Generic business software assumes you sell things off a shelf. Inspection, testing, fabrication and production create different records: a tolerance, a fitness status, a pressure rating, a rejected quantity and the reason for it. The Operations workspace has those fields because the work needed them.
Each equipment type carries its own specification, inspection and test templates, so booking an item in instantiates the checklist and two engineers test the same equipment the same way. Test entries record the method and tool, initial and final value, unit, tolerance and result, and the whole job prints as one branded service report. On the production side, entries are made per machine per shift, products carry a versioned bill of materials, and every stock movement is a ledger row with a running balance.
Yes. Templates are configured per equipment type in the application — no developer needed. Add an item to a job and its standard checklist appears automatically.
Yes. Each sub-SKU maps to its raw materials through a versioned bill of materials, carried to four decimal places, and a standing report compares raw material purchased with raw material consumed in production.
On the goods receipt, on production entries and on sales — never on the purchase order. Every movement is a ledger row (goods received, production in, production out, sale out, adjustment, return in) with the balance after it.
Tell us what your company does and which modules you would actually use. We will walk you through the system handling your work — not a slide deck.