Company
How we work.
Two things worth knowing before you start: how an engagement runs, and how a change to the platform reaches your plant.
Engagement
From the first call to the second module.
A platform engagement runs in four steps. You are live on one module before you commit to the rest.
Discovery
We agree which modules you start with, which plant they run on, and whether the system sits on your own server or on a dedicated European cloud.
Master data
We set up the plant model with your people. Lines, machines, materials, shifts and roles are entered once, and every module reads them.
First module live
One module goes into daily use on a real line. Operators enter real shifts. We fix what the floor tells us before anything else is switched on.
Expand
The next module joins the same plant model. Nothing is set up twice, and each step is small enough that production never waits on us.
Release
How a change reaches your plant
Every change to Phasis takes the same path, from an idea to your factory floor. A small fix can skip the design step. A new feature goes through all eight. Nothing lands on a production plant until the plant asks for it.
- 01
Request
A change starts as a written request. It can come from your plant or from our own team. We write down what the change has to do before any work starts.
- 02
Design
A small fix goes straight to build. A new feature gets a written plan first, saying what it does and what it does not do. We agree that plan with you before anyone writes code.
- 03
Build
Our engineers write the change against one set of written standards, so one part of Phasis behaves the same way as every other part.
- 04
Check
A second person reads every change before it moves on, and it is never the person who wrote it. Anything touching login, user roles or how data is protected also gets a security check, and anything touching a standard your industry follows is checked against that standard.
- 05
Test
Automatic checks run on every change. A full test then runs on a copy of the system with sample data, the way a real user would work. A release-wide test runs before anything ships, so the whole system is checked, not only the one change.
- 06
Release
The checked and tested changes are bundled into a release. One last full check runs on the release itself before it is fit to send to a plant.
- 07
Install
An update reaches your system only when you choose to install it. We agree the time with you, so an update never interrupts production.
- 08
Support
After the update we keep watching for problems and keep collecting requests. We keep a record of every change that ever reached your system, and that record can support your own audits. A new request goes back to step one.
Phasis runs on a server at your site or on a cloud provider based in Europe. Either way it runs on hardware set aside for you alone, never shared with another customer.
See it on your own plant.
Thirty minutes with an engineer. We walk the modules you care about against your own lines and shifts.