Pricing
Per module, per plant.
You pay for the modules you turn on, at the plant you turn them on at. There is no per-user fee. Tell us the plant and the modules and we come back with a figure and what it covers.
The model
How licensing works
You license modules, not seats.
A module is licensed per plant. Adding another operator, another supervisor or the night shift does not add a line to the invoice, so the system can go in front of everyone who needs it.
The foundation is included.
Master Data, Documents, numbering, login, roles, the audit trail, notifications and the API are not license lines. They come with any module you turn on.
A module that is off is absent.
It has no screens and no place in the interface. Nobody is browsing a tile they cannot use, and nothing half-licensed sits on the network.
Turning one on later is a configuration change.
Start with what hurts most this year. Add the next module the year after with no reinstall and no data migration. What you already recorded stays where it is.
Modules stand on their own.
Permit to Work runs without HSE, it simply loses the hazard list. Maintenance runs without Permit to Work, it simply loses the permit banner. Nothing breaks because a neighbour is off.
Deployment
Where it runs
Two options, and both of them are yours alone. Phasis is never run on hardware shared with another customer.
On a server at your site
The data never leaves the plant. That settles the question for defense work, for pharmaceutical sites and for any strict data policy. The plant keeps running when the internet drops, and a shop-floor screen does not wait for a round trip to another country.
On a European cloud host
On machines set aside for your plant, in Europe, with no other customer on them. This is the option for a plant that does not want a server room, or for a group that wants one place to look after several sites.
Either way, an update reaches the system only when you choose to install it. Nothing changes under a validated plant on a vendor's schedule.
Starter packs
Where plants usually start
Nobody turns on every module at once. These are the sets that put something useful in front of a shift within the first project, with the module most plants add next.
A plant that cannot see OEE
Open with
- Production
- Shifts & Labor
- Scheduling
Then add
- Capacity Planning
- Tools & Fixtures
Food and beverage
Open with
- Production
- Quality
- Calibration
- HSE
Then add
- Traceability In design
Documents is part of the foundation, so the specifications and the cleaning records come with it.
Pharmaceutical and other regulated plants
Open with
- Validation
- Calibration
- Quality
Then add
- In-Process & SPC
- Permit to Work
Documents and electronic signature are part of the foundation. Signature is switched on per action.
Automotive
Open with
- Production
- In-Process & SPC
- Skills & Training
- Calibration
Then add
- Quality
- Maintenance
Maintenance first
Open with
- Maintenance
- Spare Parts
- Calibration
Then add
- Permit to Work
- Tools & Fixtures
Safety first
Open with
- HSE
- Permit to Work
- Skills & Training
Then add
- Shifts & Labor
- Shift Handover
Included
What comes with every deployment
These are not license lines and they cannot be switched off. Turn on one module and you have all of them, plus the numbering that gives every record a number the plant can quote.
Next step
Request a quote
Name the plant, the modules you want first, and whether it runs on site or on a European cloud host. That is enough for us to put a figure and a scope in front of you. If you are not sure which modules, tell us what goes wrong most weeks and we will say which pack fits.
See it on your own plant.
Thirty minutes with an engineer. We walk the modules you care about against your own lines and shifts.