Platform
Foundation
One plant model under every module.
Platform at a glance
These are not license lines. They apply to every module. You describe the plant once and Maintenance, Calibration, HSE, Permit to Work, Quality, Shifts, Production and Utilities all read the same description. The same login, the same permission check, the same audit trail and the same signature rule run underneath all of them.
| Shared plant model | One plant hierarchy, five levels deep. Every module hangs off it. |
|---|---|
| Documents | Standard operating procedures (SOPs) and drawings, versioned, approved, read and understood. |
| Numbering | Every record gets a number the plant can quote, in a pattern the plant picks. |
| Per-record history | Every regulated record names who did what and when. |
| Central audit log | The database itself records every insert, change and deletion. |
| Login, SSO and MFA | People sign in with the company account. We store no passwords. |
| Roles and permissions | Read, write or approve, per module. The server enforces it. |
| Electronic signature | A real password check at the moment of approval. Off until the plant switches it on. |
| Notifications | Bell, email, SMS and WhatsApp, to the people the plant names. |
| Integrations and API | Other systems read and write through the same endpoints the screens use. |
| Deployment | On site, or on a European cloud, on hardware set aside for the customer. |
Every line above is included. None of them is priced, and none of them can be switched off. What you choose is which modules run on top of them, and a module that is off is absent from the system rather than hidden on a screen.
Master Data
The plant, the products, and the codes. Entered once.
One place holds the things every module needs. Products, recipes, units, shift patterns, the plant calendar, reason codes, defect codes, and the plant itself.
The plant hierarchy has five levels: site, area, line, section, unit. You describe the plant once. Maintenance, Calibration, HSE (health, safety and environment), Permit to Work, Quality, Shifts, Production and Utilities all read the same description. There is no second equipment list to keep in step.
Add a new line in Master Data and a draft asset appears in Maintenance at once. A calibration tag starts with its area, taken from the same tree. An incident, a permit and an energy meter all point at the same machine, so a question about that machine has one answer.
Documents
Controlled procedures and drawings. Versioned, approved, read and understood.
This is the controlled register for SOPs, drawings and the files like them. A document is numbered, typed and versioned, and it moves draft, review, approved, effective. The author cannot approve their own document.
People on the distribution list record that they have read and understood the effective version. A revision starts that clock again, so a reworded SOP does not quietly keep the old signatures. At the point of use the reader is offered the effective version and nothing else. Downloads are watermarked and logged.
Other modules store their evidence files in the same place. A qualification protocol, a calibration certificate and an SOP sit in one store, with one fingerprint and one backup. The plant does not end up with a second file pile.
What it does not do
- It does not search inside the body of a PDF.
- It does not connect to an outside document system such as SharePoint.
- There is no legal hold and no retention policy engine.
- An approval route has no per-step due date and no escalation.
Access & Audit
Company login, roles per module, and a record of every insert, change and deletion.
Login is handled by Keycloak, an identity product used widely in enterprises. We did not write it. Your IT team keeps the company login, the single sign-on (SSO), the multi-factor authentication (MFA), the password rules and the lockout policy. We store no passwords. Every request is checked, not only the login screen. IT disables a leaver in one place and access to every module stops.
A user gets a role, and a role carries a level on each module: read, write or approve. Approve is the strongest. It covers ordinary write plus the decisions, such as approving a calibration, releasing a work order or closing an NCR. The server checks the level on every action. Hiding a button is not the guard.
Even with the right level, nobody approves their own work. Quality, Calibration, HSE, Permit to Work and Documents all refuse it, and they refuse it when one person holds both roles. Access is granted per module, not per record and not per line. Someone with write on Quality can act on any NCR, not only the ones they raised.
The history on the record
Every regulated record carries who did what and when, on the record itself. An NCR keeps the reporter, the investigator and the approver. A maintenance job keeps who started it, who submitted it and who closed it. The name is a snapshot, so the record still says who did the work two years after they left.
The central log
On top of that, the database itself records every insert, change and deletion: who, when, and which fields. A module cannot forget to log. Nothing in that log can be edited or deleted, and Settings reads the same table.
Regulated records are not deleted
Every type has a named way out, and the original stays where the auditor can see it.
| Record | How you withdraw it |
|---|---|
| NCR (non-conformance report) | Cancel. There is no delete. |
| Certification | Revoke, with a reason. |
| Inspection reading | Void, with a reason. The original stays. |
| Issued permit | Close. A draft can be canceled. |
| Calibration record | Reject. The correction is a new record. |
| Risk assessment | Revise. The old version is superseded. |
| SOP version | Supersede or retire. |
E-signature
The approver types their password at the moment they approve. Off by default, switched on per action.
The signer re-enters their credentials at the moment of signing. It is a real password check against your login system. The system records the name, the date, the time and the meaning of the signature, tied to the exact state of the record. Edit the record later and the old signature does not quietly carry over.
It is off until you turn it on, and you turn it on for the approvals your quality system needs. A food or automotive plant with no such obligation runs with it off and never sees a signing dialog.
This is what FDA 21 CFR Part 11 and EU GMP (good manufacturing practice) Annex 11 ask the software to do. Those are the US and EU rules for electronic records and signatures in regulated plants. No software is Part 11 compliant on its own, and we will not tell you otherwise. Compliance is your validated system, your procedures and what you file with the regulator. The part the platform owns, the signature, the audit trail and the permission check, is built and working, and we support the validation around it.
Notifications
Inbox, email and SMS when a record needs someone.
The platform notices when a record needs a person. An overdue calibration, a tool past its life, a meter that has gone stale, a handover nobody acknowledged, a document still waiting to be read. It puts that in front of the right person.
The bell sits on every screen and is a real inbox. Email goes out when the plant has mail configured. SMS and WhatsApp are there when the plant wants a phone to ring, and both are opt-in, because each message costs money. Who hears about what is configurable, by role or by named person.
It does not nag. The same overdue instrument does not land fresh every morning.
What it does not do
- No escalation. Nothing tells a manager because the first person never looked.
- No quiet hours and no digest mail.
- Teams, Slack and webhook delivery are not built. Ask us and we will tell you the same thing.
Integrations & API
Other systems read and write the same way the screens do.
Every action on a screen is an API (application programming interface) call. There is no hidden channel. Integrators get one description file of every endpoint and every field, generated from the code, and the portal itself is built from that file. The API cannot drift away from the product.
The style is ordinary HTTPS and JSON. Your ERP can write to the same endpoints the portal uses. Power BI can read, or your team can read the database directly if they prefer that. Grafana ships with the deployment, so dashboards do not wait on a separate project.
Machines send readings in over MQTT, the common shop-floor messaging protocol. Output counts and meter readings already take that path, so OEE (overall equipment effectiveness) and energy figures come from what the line actually did.
The backend also exposes its routes as tools an AI assistant can call, over MCP, the current standard for that. A plant manager can ask which instruments are overdue in packaging and get live data. Licensing and permissions still apply. We do not ship a chatbot in the product. What we offer is that an assistant you already use can be pointed at the live API.
Deployment
On site, or on a European cloud, on hardware set aside for the customer. Updates land when the plant chooses.
Phasis runs on a server at your site, or on a European cloud provider. Either way it runs on hardware set aside for you alone. It is never shared with another customer. Data can stay on site, which settles the question for pharmaceutical, defense and any strict data policy.
An update reaches your system only when you choose to install it. We agree the time with you, so an update never interrupts production.
On site, the plant keeps running when the internet drops. Shop-floor screens do not wait for a round trip to another country. The design assumption is around 30 people using the system at once, per plant.
The commercial model is per module, per plant, with no per-user fee. See pricing .
See it on your own plant.
Thirty minutes with an engineer. We walk the modules you care about against your own lines and shifts.