27 applications. No suite to buy first.
Every application Zemerc builds has to be worth buying on its own. That single constraint decides almost everything else about the portfolio; including several things it gives up.
6 principles, each with something it costs.
A principle that costs nothing is a slogan. Each of these is stated with the consequence that makes it real; the thing it forces us to give up or to do differently.
- 01
Independently operable
Each application runs on its own, with its own users, data and release.
So: Nothing in the portfolio requires a suite to be bought first, and no application is crippled when it is the only one you have.
- 02
Commercially standalone
A customer can adopt one application for one team and stop there.
So: Widening to the next area is a commercial decision taken when that team is ready, never a technical dependency forced by the first one.
- 03
Connected where records relate
Applications share a record only where the work genuinely joins.
So: The gate reads the punch list; the barrier reads the inspection; the disclosure reads the measured production. Everywhere else, they stay out of each other’s way.
- 04
Computed, not declared
Statuses are read from the records rather than typed into a field.
So: Readiness, effectiveness and compliance are derived from the evidence held; so when the figure is wrong, the record beneath it is wrong, and that can be fixed.
- 05
Refusal is a feature
Where the evidence will not support a figure, the application declines to produce one.
So: An empty index with a stated reason is more use in an audit than a number nobody can defend, and far more use than a number nobody checked.
- 06
Claims follow evidence
What this website says about an application is what that application demonstrably does.
So: Capability that is mock-backed or unfinished is never described as live, here or in a demonstration.
A single platform is a real choice. This is the other one.
Buying one integrated system has genuine advantages, and pretending otherwise would be the kind of claim this portfolio exists to avoid. Here is what each side actually gives you.
What a single platform gives you
- One vendor relationship and one contract
- A single sign-on and one administrative surface
- Modules that cannot disagree, because they are the same application
What a portfolio of applications gives you
- A first adoption that commits you to nothing else
- Each application deep enough in its own discipline to be bought on its merits
- The freedom to keep the systems you already have in the areas they already serve
- Replacement of one application without replacing the rest
Zemerc takes the second one because industrial records are owned by different disciplines with different regulators, different evidence rules and different renewal cycles. A system deep enough for the integrity engineer is rarely the system the contracts manager needs, and forcing both into one application costs the depth that made either worth buying.
Somebody eventually reads the record itself.
Not the dashboard above it. When a figure is challenged; by an auditor, a regulator, a partner or a new engineer; what settles it is whether the record underneath can be produced, and whether it says what the figure claimed.
- Readings, approved revisions and audit trails are immutable, so the original survives
- Effective dating lets a closed period be re-run on the method that was in force then
- Approval is segregated on identity, so the record shows who actually accepted it
Three things this philosophy makes possible.
A first adoption with no lock-in
One team, one application, one record. If it does not earn the next one, nothing else was bought.
Depth where the discipline needs it
Each application can go as far as its discipline requires, because it does not have to stay consistent with twenty-six others.
Replacement without a programme
An application can be replaced on its own. Nothing else in the portfolio stops working when it goes.
Adopt one application and stop there.
That is a genuine option, not a trial. Bring the register with the clearest problem and we will show the application whose job it already is.