Digital Oilfield (i-field) technology is based on both new and existing IT platforms. Development of new tools that require a new approach to architecture has presented numerous pilot project opportunities. These pilot projects have uncovered at least one common theme revolving around the quality and completeness of local information management solutions and the difficulty of integrating new solutions into legacy applications and work processes.

Chevron's Global Upstream (Chevron) has initiated an IT program, named Level 0, to provide the technology platform for integration to drive performance improvements prescribed by i-field, base business and reservoir management initiatives. In many cases, current state information stores, applications solutions and field infrastructure are aligned with traditional functional requirements but do not easily integrate to provide a broad perspective for full asset management. The Level 0 effort is taking an approach to provide an enterprise solution through distributed efforts coordinated through corporate IT support functions.

Oil and gas production environments are diverse. Requirements in a heavy oil environment are vastly different from i-field deliverables in an offshore setting; however, they may interact with core IT systems in a similar manner. To maximize re-use of common functions and allow for priority functionality development, Level 0 teams are building a consistent information architecture, web service/interoperability architecture and real-time data architecture. Details of these architectures are being built independently by the co-located project teams but are using common technology and philosophical approaches.

Chevron Upstream Europe (CUE) and San Joaquin Valley Strategic Business Unit (SJVSBU) are the first two business units to engage in this program. CUE has proven the technology solutions and information architecture are sound. SJVSBU is widening the scope to provide additional functionality. The next wave of Level 0 projects are starting up in our Gulf of Mexico and Mid Continent business units. Agile Scrum methodology, a methodology based on short development intervals called sprints, is being utilized by both current projects. This methodology allows scoping and delivering architectural extensions or application functionality every 30 days. Processes to insure evergreen alignment of extensions are being formalized.

You can access this article if you purchase or spend a download.