2026-08-01
Why most Digital Oil Field programmes stall - and what KwIDF did differently
Instrumenting an asset is the easy half. The programmes that hold are the ones that redesign who decides what, and when.
A digital oil field programme usually begins the same way. Sensors are specified, a data platform is procured, dashboards are commissioned, and a control room is fitted out. Two years later the asset has more data than it has ever had and the same decisions are being made, at the same speed, by the same people.
The reason is that the programme treated the problem as a data problem. It was a decision problem. Data arriving faster does not change an outcome unless someone's authority, workflow or attention changes with it.
KwIDF was constructed on a different premise: that the unit of design is collaboration, not instrumentation. Two collaboration models were specified up front - man-to-man, covering how disciplines and asset teams work a decision between them, and man-to-machine, covering what the system is trusted to do without a human in the loop and where it must hand back.
That ordering matters. When the collaboration model is defined first, the technology specification falls out of it - you know what latency the decision needs, which means you know what the data layer has to deliver. When the technology is specified first, the collaboration model is whatever the software happens to permit.
The practical test for any digital field programme is simple. Name a decision that is currently made monthly and will be made weekly when the programme lands. Name who makes it, and name what they will stop doing to make room. If the programme cannot answer that, it is a data project wearing a transformation label.
digital oil fieldKwIDFintegrated operationsoil and gas digital transformation
2026-06-15
Measuring the value of research when the payback is a decade away
Project-by-project justification kills research portfolios. Cluster-level value logic is what survives a budget review.
Every research group in the energy industry faces the same annual conversation. Finance asks what the return was. The group answers with a project list. The list contains successes that cannot be attributed cleanly and failures that were, technically, the point of doing research. The budget gets trimmed.
The flaw is the unit of measurement. Individual research projects have a high failure rate by design - if they did not, they would be engineering, not research. Measuring them individually guarantees a portfolio that looks like it is failing.
The cluster concept changes the unit. Projects are grouped into clusters aligned to an operational capability the business has already said it needs. Value is assessed at the cluster level: did the capability advance, is the organisation now able to do something it could not do before, and what did the whole cluster cost to get there.
This has two effects. It makes failure legible - a failed project inside a successful cluster is an expected cost, not a scandal. And it forces the portfolio to stay tethered to operational need, because a cluster that cannot name the capability it serves does not get formed.
The harder discipline is retiring clusters. A cluster that has delivered its capability should be closed, and the budget should move. Portfolios that only ever add clusters end up defending history.
research and technology valueR&D portfolio managementenergy R&Dtechnology roadmap
2026-04-20
What a ten-year alternative energy roadmap has to answer
Transition roadmaps for hydrocarbon-based national companies fail on structure, not ambition.
Alternative energy roadmaps produced inside hydrocarbon-based organisations tend to be ambitious and structurally silent. They set capacity targets and decarbonisation milestones, and they do not say which entity holds the asset, which balance sheet carries the risk, or who inside the organisation is measured on the outcome.
That silence is where roadmaps die. A solar programme originated inside an upstream organisation is competing for capital against barrels, under a return threshold calibrated to barrels, assessed by people whose careers were built on barrels. The roadmap will lose that competition every year unless the structure is changed alongside it.
So the structural questions come first. Is the new-energy portfolio held inside the existing corporate entity or beside it. What return threshold applies to it, and who has authority to set a different one. Which international partners are required, and what corporate form makes them investable.
Only then does the sequencing work mean anything: which projects go first because they are bankable, which go second because they build capability, and which stay on the list as options that are deliberately not being exercised yet.
A roadmap that answers the structural questions can survive a change of leadership. One that only sets targets tends not to survive the first bad quarter.
energy transitionalternative energy roadmapnational oil companysolar energy Kuwait