Every engagement begins with a maturity assessment. We use a five-stage scale — ad-hoc, managed, defined, quantitatively managed, optimizing — adapted from the CMMI tradition and scored across four dimensions: data, process, people, and technology. The assessment is fact-based, not opinion-based: we walk the plant, interview operators and engineers, sample data sources, and review existing documentation. The output is a single page that tells the board exactly where the organization stands on each dimension, with the evidence underneath.

Roadmap design follows the assessment. A typical Industry 4.0 roadmap covers three years broken into six quarters, with explicit milestones, dependency maps, ROI projections, and gating decisions between phases. We refuse to ship a roadmap that promises a destination without enumerating the dependencies — too many programs derail because Phase 2 depends on a data layer that Phase 1 never built. The roadmap is the living spine of the program, revisited quarterly against actual project velocity.

OT/IT convergence is where most transformations stall, so we design it explicitly. Network architecture follows the Purdue Reference Model, security follows IEC 62443 with formal zones and conduits, and data governance defines who owns which dataset, who can access it, and how long it is retained. We have seen too many programs where the IT and OT teams negotiate this informally and then discover six months in that they had different mental models. Writing it down is unglamorous and indispensable.

Vendor selection is conducted with the customer, not for them. We define the customer-fit fingerprint — the technical, commercial, and support criteria that actually matter for this plant — then shortlist three to five vendors against it. Proof-of-concept criteria are written before any vendor demo, so success or failure is measured against the same yardstick. Most importantly, our shortlist is not constrained by reseller relationships: we have no preferred PLC brand, no preferred SCADA platform, no preferred cloud, because the right answer is whatever fits the customer's process and team.

Change management is the last 30 percent and we treat it as first-class engineering. Stakeholder maps, communication cadences, training curricula, SOP documentation, and shift-by-shift go-live plans are all delivered as part of the engagement. The technical implementation is a means to an end; the end is a plant where the new way of working is the easiest way of working, six months after the consultants leave.