Search citation statements
Paper Sections
Citation Types
Year Published
Publication Types
Relationship
Authors
Journals
The current well planning process for operators is capital-intensive that takes time and has a lot of discrete, disconnected steps. Well planners and engineers dedicate a significant amount of time and effort to analyze sub-surface and offset well data for trajectory planning, casing policy selection, casing design, torque & drag, hydraulics, time & cost analysis etc. For development wells and unconventional wells, it is a common scenario for drilling engineers to have a very clear understanding of how the well design shall look like as the oil & gas field is extremely well familiar. As an initial step towards standardization, a review and study of several well design processes were performed by interviewing several engineers, all around the globe. The study revealed that even though every engineer had their own way of working, there was an inherent workflow that could be standardized. This standardized workflow was then outlined with user experience development techniques to cater to the generic steps that well planners, engineers and managers had described. With implementation of this standardized workflow and UI/UX supported process, the next step was to build a cloud native solution which supports micro-services-based engineering calculations in the backend. This allowed to implement speed and scalability in the solution which can cater to various personas in a team. The next step was to automate the process for a development field. This was achieved by applying checkpoints in the workflow to identify an exploratory well vs. a development well, before calling a microservice. For a development field, the microservice architecture identifies the design aspects of an existing well and incorporates similar well trajectory turn points, casing policy, casing design, BHA, fluids, operational parameters etc. while honoring the surface hole location, targets, and datum reference of the new wells to be planned. This technique helped to not only automate the engineering calculations but also speed up the entire process of designing each well in under a minute. Apart from engineering calculations, a planning workflow is never complete without team governance, approvals from peers and supervisors, testing various scenarios and creating reports. As these tasks are an inherent part of the planning cycle, they were also incorporated in the workflow. The UX design process techniques ensured that these supplementary tasks were a part of the main workflow and did not interfere with the calculations. The solution has shown a tremendous increase in the work efficiency of user by reducing the planning efforts from days to minutes. The users can now focus on wells using management by exception as the entire design process can be automated. This also eliminates any unnecessary data entry and avoids errors.
The current well planning process for operators is capital-intensive that takes time and has a lot of discrete, disconnected steps. Well planners and engineers dedicate a significant amount of time and effort to analyze sub-surface and offset well data for trajectory planning, casing policy selection, casing design, torque & drag, hydraulics, time & cost analysis etc. For development wells and unconventional wells, it is a common scenario for drilling engineers to have a very clear understanding of how the well design shall look like as the oil & gas field is extremely well familiar. As an initial step towards standardization, a review and study of several well design processes were performed by interviewing several engineers, all around the globe. The study revealed that even though every engineer had their own way of working, there was an inherent workflow that could be standardized. This standardized workflow was then outlined with user experience development techniques to cater to the generic steps that well planners, engineers and managers had described. With implementation of this standardized workflow and UI/UX supported process, the next step was to build a cloud native solution which supports micro-services-based engineering calculations in the backend. This allowed to implement speed and scalability in the solution which can cater to various personas in a team. The next step was to automate the process for a development field. This was achieved by applying checkpoints in the workflow to identify an exploratory well vs. a development well, before calling a microservice. For a development field, the microservice architecture identifies the design aspects of an existing well and incorporates similar well trajectory turn points, casing policy, casing design, BHA, fluids, operational parameters etc. while honoring the surface hole location, targets, and datum reference of the new wells to be planned. This technique helped to not only automate the engineering calculations but also speed up the entire process of designing each well in under a minute. Apart from engineering calculations, a planning workflow is never complete without team governance, approvals from peers and supervisors, testing various scenarios and creating reports. As these tasks are an inherent part of the planning cycle, they were also incorporated in the workflow. The UX design process techniques ensured that these supplementary tasks were a part of the main workflow and did not interfere with the calculations. The solution has shown a tremendous increase in the work efficiency of user by reducing the planning efforts from days to minutes. The users can now focus on wells using management by exception as the entire design process can be automated. This also eliminates any unnecessary data entry and avoids errors.
Casing design and the associated load assumptions have evolved considerably over the last 30 years. The objective of this paper is to trace the history, evolution and future of casing design by means of the type of load cases and the assumptions made for them as it evolved from the early 1960's to the modern load case requirements for wells drilled in the 2020's. The vast majority of tubular failures in oil & gas wells are not attributable to computational errors in calculating design loads, but rather are due to a shortfall in considering the appropriate load scenarios. One common shortfall includes making incorrect or oversimplified assumptions for the initial and final temperature and pressure conditions. There is no industry standard for casing or tubing design loads, but there is an industry accepted standard process for the calculation of the stress on tubulars once the load cases are determined. Each operating company may use a different set of load assumptions depending on the well type and risk assessment. This work also keeps in view the major computational tools used during each step change of the casing design evolution: slide rule/nomographs, HP 41C calculators, PC DOS and Windows programs, and the latest Cloud-Native paradigm with REST API's within a microservices architecture. A REST API (also known as RESTful API) is an Application Programming Interface (API) that conforms to the constraints of Representational State Transfer (REST) architectural style commonly used in current Cloud computing technology. The scope will also include ongoing research and development to address shortcomings of previous load case assumptions and calculations for extended reach and HPHT wells, closely spaced wells, and geothermal wells. Modern wells and modern casing design load cases are in a constant state of evolution and casing failures will occur unless engineers and their tools also evolve.
The Wells Front-End Loading (FEL) workflow is a critical phase in the planning and design of oil well projects, enabling efficient cost optimization and decision-making before project execution. However, the current FEL workflow suffers from inefficiencies caused by manual registration, localized record-keeping, repetitive iterations, and dynamic stakeholder expectations influenced by oil price uncertainties. Furthermore, fragmented data connectivity and the unavailability of legacy data hinder seamless data flow and digital adoption throughout the well life cycle. To address these challenges, this paper introduces Wells Front End Engineering Nexus (FENEX), a centralized web-based workflow platform that digitalizes the FEL workflow and offers anywhere and anytime accessibility. The FENEX application is supported by the Well Planning Suite (WPS) as the orchestrator to enable the execution of FEL workflow, perform detailed engineering design and ensure a smooth handover to the execution team. This manuscript presents FENEX as a comprehensive solution for improving the FEL workflow. It highlights the FENEX dashboard, critical roles of WPS and some enhancement features, i.e. introduction of features of "Campaign", workflow integration & approval process amongst the Field Development Plan (FDP) team & Technical Assurers (TA), guided workflow for well engineering and input for efficient project tracking & monitoring via FENEX. In the effort to realize FENEX, this paper will also discuss the key challenges in managing the segmented well databases between well design planning and well operational records which could impair the seamless data connectivity throughout the whole well life cycle. As such, a drastic reshaping of the data landscape was required to mitigate this where all data are consolidated into one Cloud database, wellSCAPE promoting a single source of truth for all well design, planning and operational records data. The implementation of FENEX addresses the limitations of the current FEL workflow, streamlining processes, enhancing efficiency, and reducing costs. By centralizing project data and promoting seamless data connectivity, FENEX overcomes the challenges of localized record keeping, fragmented data landscape, and the absence of legacy data. The platform empowers stakeholders to make informed decisions, optimize value extraction, and drive digital adoption in the oil and gas industry. The introduction of FENEX represents a significant step towards efficient collaboration, optimized value extraction, and enhanced evaluation efficiency. The findings of this study provide valuable insights for industry professionals seeking to streamline the FEL workflow and leverage digital tools to achieve project success in a rapidly changing energy landscape.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
customersupport@researchsolutions.com
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Copyright © 2025 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.