Skip to content

Case Study: Norwegian Operator Redefines Well Maturation Through Smarter Ways of Working

Oct 2026 · Journal of Petroleum Technology
Reservoir Engineering and Simulation Methods

Abstract

_ Vår Energi's ambition is to accelerate well planning maturation while sustaining consistently top-quartile execution performance, from initiation through to a drill-ready well. Achieving that has demanded more than a new piece of software. It has required a shift in how subsurface, subsea, and project development, and drilling and wells business units work together. Rather than maturing a well trajectory through a sequence of discipline-by-discipline handoffs, the three teams now plan inside a shared, real-time environment, jointly maturing the same trajectory from the first sketch through to a drill-ready design. The intent is to plan faster and use that speed to test more of the design space per well and capture more value. One Environment, Multiple Domains The scope of the new shared environment is wide. On the subsea and site side, it covers infrastructure constraints, bathymetry, and shallow-hazard mapping, including pock marks, anchor scours, boulders, and shallow gas, alongside surface-location placement. On the subsurface side, it covers reservoir well placement and risk factors, such as pore pressure, shear failure gradient, and fracture gradient, that shape a safe design. On the drilling side, it covers drilling-corridor definition and wellbore-geometry optimization. Historically, each of those was effectively someone else's problem until a trajectory was far enough along to hand off. In the shared environment, all three are visible to everyone from the first sketch of a well (Fig. 1), which is what makes it possible to optimize reservoir exposure and design robustness together rather than resolving them one after another. The new environment is also not a single piece of software running in one place. Some of the applications it connects run on premises while others run in the cloud. Making that combination feel like one workflow took a purpose-built, synced-drive IT integration layer to bridge the two. This is a deliberately fit-for-purpose piece of infrastructure, assembled around what the team already had, rather than a single platform bought off the shelf to replace it. A Sequential Process Built for a Different Era Well planning within the operator was typical of the industry and had been organized as a sequence of discrete steps: data preparation, drafting a trajectory, a pore-pressure/fracture-gradient plot and shallow-hazards check, picking formation tops, well engineering, and a design reassessment before the cycle could close. Data preparation alone typically took 25 to 30 days, drawing on inputs from all three domains in turn. Each later step added 1 to 3 more days on its own, but if the reassessment surfaced a conflict, a target that didn't clear a wellbore-stability check, or a trajectory that fought with a subsea infrastructure or shallow-hazard constraint, the sequence looped back to drafting a new trajectory. That loop could add another 30 to 40 days, with the same six to eight people redoing analysis they had already done once (Fig. 2).

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.