IT and OT are converging. But how do you organise that? Who owns what, which processes do you need? We answer those questions with a clear strategy, a fitting operating model, and the technical architecture as its foundation.
Strategy work is the right move when the decision is organisational, not technical: when the question isn't a product choice but how IT and OT operations should be structured across the company.
The two are growing together, but nobody has defined how they should be organised. Responsibilities overlap, processes are missing, decisions get stuck.
Who owns the OT network? Who decides on changes? Without clear mandates, things either don't get done, or get done twice.
NIS2 and the IKT-Minimalstandard require documented governance. You need a model that satisfies auditors and actually works in practice.
Before choosing products, you need to know the target. A strategy defines the architecture and operating model that technology decisions should serve.
Five steps, grounded in the technical reality of your network.
Where the organisation stands today: IT, OT, governance, processes. We map the reality.
A coordinated or integrated IT/OT operating model: whatever fits your organisation, size and constraints.
Who decides what, who is responsible for what: clear mandates that prevent conflicts and gaps.
The technical foundation: zone model, segmentation concept, infrastructure design that implements the strategy.
Concrete steps, priorities and sequencing: what comes first, what can wait, what depends on what.
Review first-hop redundancy across core and distribution: verify HSRP/VRRP group priorities, preemption and timers, confirm active and standby paths match the intended design, and retire overlapping or orphaned groups. Establishes a predictable failover baseline before segmentation touches the core.
In practice: a strategy only holds if it becomes a plan someone can follow — priorities, dependencies and owners, quarter by quarter.
An IT/OT convergence strategy for a Swiss utility: an overarching network and security architecture that set the direction, followed by Explorer for ongoing visibility and an OT Connect design for the distributed sites. The strategy wasn't a slide deck: it was backed by real network data and turned into infrastructure.
We ground everything in technical architecture: real network data, implementable designs, and products that turn decisions into infrastructure. We build what we recommend.
Not always. If the question is purely technical ("what's on our network?"), start with an assessment. If it's organisational ("how should IT and OT work together?"), start here. Both can run in parallel.
Typically 6–12 weeks from kickoff to roadmap, depending on organisation size and complexity. The work often overlaps with an assessment running in parallel.
IT and OT leadership, plus the teams that will implement and operate the result. The strategy needs buy-in from both sides. We facilitate that process.
How IT/OT strategy turns into roadmaps, standards and segmentation on real engagements.

How lightweight tools map to the Swiss ICT minimum standard for critical infrastructure.
Read →
Browser-based tools for zones, communication matrices and a realistic segmentation roadmap.
Read →
A regional energy utility's network, rebuilt around clear zones with a realistic migration path.
Read →The right structure makes every technical decision easier. Start with the strategy that gives your organisation direction.
Discuss your strategy