SERVICE MODEL
We build it. You run it. We keep it running.
A production system is not a thing you buy once. It needs patching, updating, monitoring, fixing and improving for as long as the plant depends on it - and most mid-sized manufacturers have no software team to do that. So we do it. You pay a one-off fee to build and commission the system, then a monthly fee that covers the right to run it and everything needed to keep it healthy.
Development & Deployment
A fixed-price engagement to design and build the system for your plant: tag survey, configuration, connectivity to your controllers, integration with your existing systems, installation on your infrastructure, commissioning on the floor and operator training.
Scoped from a short discovery, so the price is known before work starts.
System Operation & Support
The right to run and operate the complete system - the web application and the data-collection services - together with everything needed to keep it live: maintenance, monitoring, patching, backups, debugging, updates and upgrades.
Plus a defined block of development hours every month for changes, new reports and enhancements.
What the monthly fee includes
Three levels of cover
All three include the right to operate the full system and everything in the list above. They differ on how fast we respond, how often we update, and how many development hours are included. The fee scales with the size and scope of the deployment and is quoted after scoping.
Essential
Single site, day-shift dependence
Standard
Multi-shift plants where the system is relied on daily
Critical
Continuous operation, system of record
For groups running several plants, sites are covered under one agreement at group rates rather than negotiated individually. See multi-site roll-out.
Intellectual property, and what happens if we disappear
Two questions every procurement review asks. We would rather answer them here than have you wonder.
We keep the platform IP
Fluidika retains ownership of the platform, its source code and the software itself. That is what allows the core to be reused across clients - and it is the reason your deployment costs a fraction of building an MES from nothing, and why the second plant in a group costs less than the first.
You are never stranded
If Fluidika ceases trading or materially defaults, you retain a perpetual right to keep running your existing deployed system. It would be frozen and unsupported, but your plant would not stop and your production history would remain yours - on your own servers, where it already lives.
Being straight about the trade-off
This is a managed service, so there is a real dependency on us while the agreement is active - if you stop subscribing, the right to operate the system lapses and only the continuity right above survives. We would rather say that plainly than let you discover it in a contract.
What you are not exposed to is a third-party platform licence, per-seat or per-tag vendor fees, an annual renewal to a company with no interest in your plant, or your production data sitting on somebody else's infrastructure. Your data stays on your servers, inside the EU, throughout.
WHAT WOULD IT COST FOR YOUR PLANT?
Tell us the size of the plant, how many machines and which modules matter. We will come back with a scoped build price and a monthly figure.