Industry 04Energy
Hikari Blue operates in energy where IT meets OT, programs run for years, and the system carries safety-critical responsibility. Reliability is not a metric. It is the contract. Utilities, renewables, grid operators all share one operating reality: the platform must outlive the program that built it.
What makes this sector hard
Five structural pressures shape every engagement we accept in energy. Each one breaks platforms that were designed only for IT, or only for OT.
SCADA, ICS, control rooms operating alongside corporate IT, cloud workloads and remote operations. The threat model and the patching cadence are radically different. A single architectural error compromises both.
Energy is in the first tier of NIS2 enforcement. The reporting, evidence and incident timelines are non-negotiable. Most legacy operating models cannot produce the artifacts the directive requires.
Five to ten years between board approval and production reality. Regulation evolves underneath. The operating model must accept policy change as a continuous input, not as a project amendment.
Grid topology, asset performance, demand response data all carry national security weight. Residency, processing and transfer mechanisms must match the strategic posture, not the cheapest cloud region.
The talent profile shifts under the program. Predictive operations, AI on grid, renewables orchestration: the team that started the program is not the team that operates it. The architecture must support the handover.
How we operate here
Four engagement types we accept in energy. Each respects the long horizon and the safety-critical responsibility of the sector.
Twelve to twenty-four weeks. We design the boundary, the evidence chain and the operating model that lets OT and IT coexist under one defensible cybersecurity posture. NIS2-ready.
Signed by Gilles MischlerSixteen to thirty-two weeks. We structure the program governance, the milestone architecture and the policy-input cadence so a five-year program survives the policy changes that will happen during it.
Signed by Franck OhrelTwelve to twenty weeks. AI on grid topology, asset condition, demand response, with audit trail, model registry, kill switch by architecture. EU AI Act-defensible.
Signed by Xavier de MaillardEight to sixteen weeks. We design the platform-level evidence emission that lets the operator answer NIS2 between cycles, not in the week before the inspection.
Signed by Gilles MischlerSolutions mobilized here
Predictive operations on grid and assets, with governance defensible at board register.
OT-IT modernization under reversibility, without breaking what keeps the lights on.
Delivery posture defensible to NIS2 and national OT cyber, continuously.
Continuous operations across a multi-year program horizon. Cost discipline and reliability balanced.
Bring the long-cycle question
Thirty minutes with a senior partner. We listen to your IT / OT perimeter, your NIS2 exposure, and your program horizon, then we tell you what we would engineer first.
