MENTARA
Industries

Plant autonomy is why central standardisation keeps failing.

Manufacturing programmes are designed centrally and defeated locally, because plants are measured on output. MENTARA designs for that reality, not against it.

The sector's actual constraint

Central manufacturing IT programmes have a consistent failure pattern: a standard MES or data platform is designed, rollout begins, and each plant negotiates enough local variation that the standard stops being one. Five years later there are eleven implementations of the standard system.

This is not obstruction. Plant managers are measured on output, quality and safety, and a central programme that threatens any of those is a risk they are accountable for and the programme team is not. Any approach that does not account for that asymmetry will fail regardless of its technical merit.

The failure mode

OT and IT have different definitions of an acceptable risk.

The convergence of operational technology and IT is usually described as a technical integration challenge. It is more accurately a collision between two risk cultures. IT patches quickly because unpatched systems are the risk. OT does not patch quickly because unplanned downtime and safety consequences are the risk, and a control system that has run correctly for eleven years is not touched without a compelling reason.

Both positions are correct within their own frame, and security programmes that impose IT assumptions on OT environments are rejected — sometimes formally, more often by quiet non-implementation. Progress comes from segmentation, monitoring and compensating controls that respect the operational constraint rather than from patch mandates.

The second pattern is data that never leaves the plant usefully. Machine and process data exists in volume, sits in historians and local systems, and is not comparable between sites because tag naming, units, sampling and context differ. Central analytics then produce comparisons that plant engineers know are wrong, and credibility is lost early.

Priorities

Where the work usually sits.

01Standardisation that survives rolloutDeciding what genuinely must be identical across sites and what can vary — and designing the standard so local needs are met inside it rather than around it.
02OT/IT convergence and segmentationSecurity improvement that respects operational risk: segmentation, monitoring and compensating controls rather than patch mandates that will not be followed.
03Industrial data foundationsContextualised, comparable data across sites — tag naming, units and process context resolved before analytics, not after credibility is lost.
04MES and ERP integrationExplicit contracts between shop floor and enterprise systems rather than accumulated interfaces nobody owns.
05Supply chain visibilityWorking with the data partners actually provide, including its gaps, rather than a model that assumes data quality nobody supplies.
06Connected product platformsTelemetry, update mechanisms and the long-term support obligations that come with a product that phones home for a decade.
Questions

What buyers ask.

Do you work directly with control systems?

No. We do not configure PLCs, SCADA or safety instrumented systems, and we would not want a supplier without deep controls engineering experience doing so on your plant either.

We work at the layer above: segmentation architecture, data contextualisation, MES and enterprise integration, and the security design around OT rather than inside it.

Can you help with a multi-site rollout?

We can design the standard and prove it at one or two sites. Executing a rollout across thirty plants simultaneously is a scale requirement we do not meet, and a larger partner would serve it better — potentially with us holding the architecture and standard.

05

Where MENTARA fits best.

Scope

We fit standardisation design, OT/IT security architecture, industrial data foundations and integration — the design and first-proof work rather than the volume rollout.

Control systems engineering, safety system work and multi-site rollout execution are better served by specialists in those disciplines.

MENTARA was incorporated in July 2026 and has no published client work in this or any sector, so the quality of the thinking on this page — and in a first conversation — is what there is to judge us on.

Where this connects

Bring the standard that keeps getting negotiated away.

Share the business context, constraints and expected outcome. MENTARA will identify the relevant accountable route.

One partner. One plan. Measurable outcomes.