Run the plant floor from one system.

A manufacturing operating system for packaged goods plants, which is what the MOS in the name stands for. It schedules production orders, weighs out batches against a formula, clears the line with a checklist, records every in-process check against the product’s specification, and takes every non-conformity through hold, disposition and corrective action, in one record. Operators and batchers use an iPad app at the line; supervisors, quality managers and admins use the web app in the office.

Yes, and the batch sheet and the pre-start checklist with it. The schedule is built from those records: a batch order and a session carry the same production order number, so the schedule shows the batch that fed the run and the checks the run recorded.

Packaged goods lines that run recurring checks against a per-product specification and weigh formulations out against a batch order. The built-in demo plants cover snack food, dairy, beverage and cosmetics; the products, formulas, checks and checklists are yours to define, from bag weight and seal integrity to residual oxygen and date codes.

The value is judged against the product’s limits the moment it is entered. An out-of-spec reading opens a non-conformity before the check can be closed, and the non-conformity, any hold, the AQL disposition, the corrective action and any CAPA are tracked in one register with the audit trail.

A batch order names the production order, the product and a quantity in litres or kilograms. The product’s formula turns that into the mass of every material, two people sign the sheet, and it keeps the formula it was struck from, so a revision next month cannot restate what was signed last month.

Five roles. Admins set the plant up; managers review everything, run dispositions and holds, and authorise checklists; operators run the line; mechanics record what they fixed; batchers weigh out and sign batch orders. Every gate is enforced by the API, not only hidden in the screen.

Yes. The iPad app is for the line and the web app is for the office. They are one system with the same records, so a check recorded at the bagger is on the supervisor’s desk the moment it is saved.

Yes. totalMOS comes in two editions built from the same code. In totalMOS Cloud, we host it and keep it up to date, and people sign in with an email address and a six-digit code. On site, it runs as a signed container image on a server inside your plant, with its own database and file storage, so records and photos never leave your network; people sign in with a login and a password, and your IT team decides when to upgrade. Both editions run the same web app and the same iPad app.

Yes, with the on-site edition. totalMOS reads products, formulas, machines and production orders from the ERP, so a batcher picks a job instead of typing it and the batch sheet carries the ERP’s formula. Out of the box the connection only reads: it uses a login with no write permission, every query is generated from the mapping and limited in time and rows, and a sync runs only when someone starts it. If you want totalMOS to write back to the ERP, such as completed orders or the material consumed, we build it for your project. It connects to Infor SyteLine, SAP S/4HANA, SAP Business One, Microsoft Dynamics 365, Oracle NetSuite, Epicor Kinetic, Sage X3, and Acumatica, and to other ERPs on request.

Yes, with a custom module on the on-site edition. We build what only your plant does, such as a rule checked before a batch order is created or signed, tables of your own or an endpoint your other systems call, as a module that loads beside totalMOS. It reads only your plant’s data, records what it changes in the same audit trail, and is switched on by your licence.

Nothing is lost. The reading is saved on the iPad with the time it was taken, the countdown resets, and the operator carries on. The app sends what it holds as soon as the connection returns, in the order it was taken, and the record keeps both times, when the check was made and when it reached the server, so an auditor sees that a reading arrived late rather than wondering.

In the cloud, with an email address and a six-digit code. There are no passwords, because a password on a shared tablet ends up written on the wall next to the machine. On site, where operators may have no work email, each person has a login and a password of at least twelve characters, set once by an admin and changed at the first sign-in.

Yes. It gives your plant the tools Québec’s Law 25 calls for: a person in charge of the protection of personal information shown to every member, a register of confidentiality incidents kept at least five years, preference cookies that stay off until accepted, a one-tap download of each person’s data, erasure and anonymisation that keep the plant’s legal records, scheduled purges of what no longer needs keeping, and a plain-language privacy policy in French and English. It helps you meet the law; compliance also depends on your own policies and practices.

It depends on the edition. On site, everything stays on your own server: the database, the photos and the backups. In totalMOS Cloud, with Neon (database and sign-in), Amazon Web Services (file storage and email delivery) and Vercel (application hosting). If a plant turns on Mozzie, the AI assistant, the questions asked and the records used to answer them are processed by Anthropic. Some of them may store or process information elsewhere in Canada or in the United States. Before information leaves Québec, we assess the privacy impact, and our contracts require protection equivalent to Québec law. The hosting region used for your plant is set out in its service agreement.