Oilfield operations, such as surveying, drilling, wireline testing, completions and production, are typically performed to locate, gather, store and transport valuable downhole fluids. As shown in
A formation is a distinctive and continuous body of rock that it can be mapped. Spaces between the rock grains (“porosity”) of a formation may contain fluids such as oil, gas or water. Connections between the spaces (“permeability”) may allow the fluids to move through the formation. Formations with sufficient porosity and permeability to store fluids and allow the fluids to move are known as reservoirs. A structure is a geological feature that is created by deformation of the Earth's crust, such as a fold or fault, a feature within the rock itself (such as a fracture) or, more generally, an arrangement of rocks. The above definitions are taken from Schlumberger's Oilfield Glossary (www.glossary.oilfield.slb.com), but in the industry, the terms formation and structure may be loosely used synonymously.
The complex operations of drilling and completing wells are well known by those of skill in the art and the description here is a simplified view. As shown in
After the drilling operation is complete, the well may then be prepared for production. As shown in
During the oilfield operations, data is typically collected for analysis and/or monitoring of the oilfield operations. Such data may include, for example, subterranean formation, equipment, historical and/or other data. Data concerning the subterranean formation is collected using a variety of sources. Such formation data may be static or dynamic. Static data relates to formation structure and geological stratigraphy, which defines the geological structure of the subterranean formation. Dynamic data relates to fluids flowing through the geologic structures of the subterranean formation. Such static and/or dynamic data may be collected to learn more about the formations and the valuable assets contained therein.
Sources used to collect static data may be seismic tools, such as a seismic truck that sends compression waves into the earth as shown in
Sensors may be positioned throughout the oilfield to collect data relating to various oilfield operations. For example, sensors in the wellbore may monitor fluid composition, sensors located along the flow path may monitor flow rates and sensors at the processing facility may monitor fluids collected. Other sensors may be provided to monitor downhole, surface, equipment or other conditions. The monitored data is often used to make decisions at various locations of the oilfield at various times. Data collected by these sensors may be further analyzed and processed. Data may be collected and used for current or future operations. When used for future operations at the same or other locations, such data may sometimes be referred to as historical data.
The processed data may be used to predict downhole conditions, and make decisions concerning oilfield operations. Such decisions may involve well planning, well targeting, well completions, operating levels, production rates and other configurations. Often this information is used to determine where to drill new wells, how to re-complete or stimulate existing wells, or alter wellbore production.
Data from one or more wellbores may be analyzed to plan or predict various outcomes at a given wellbore. In some cases, the data from neighboring wellbores, wellbores into the same formations or wellbores with similar conditions or equipment is used to predict how a well will perform. There are usually a large number of variables and large quantities of data to consider in analyzing wellbore operations. It is, therefore, often useful to model the behavior of the oilfield operation to determine the desired course of action. During the ongoing operations, the operating conditions may need adjustment as conditions change and new information is received.
Techniques have been developed to model the behavior of geological structures, downhole reservoirs, wellbores, surface facilities as well as other portions of the oilfield operation. Examples of modeling techniques are shown in patent/application/Publication Nos. U.S. Pat. No. 5,992,519, WO2004/049216, WO1999/064896, U.S. Pat. No. 6,313,837, US2003/0216897, US2003/0132934, US2005/0149307, and US2006/0197759. Typically, existing modeling techniques have been used to analyze only specific portions of the oilfield operation. More recently, attempts have been made to use more than one model in analyzing certain oilfield operations. See, for example, patent/application/Publication Nos. U.S. Pat. No. 6,980,940, WO2004/049216, US2004/0220846, and US10/586,283.
Techniques have also been developed to predict and/or plan certain oilfield operations, such as drilling operations. Examples of techniques for generating drilling plans are provided in patent/application/Publication Nos. US2005/0236184, US2005/0211468, US2005/0228905, US/2005/0209886, and US2005/0209836. Some drilling techniques involve controlling the drilling operation. Examples of such drilling techniques are shown in patent/application Nos. GB2392931 and GB2411669. Other drilling techniques seek to provide real-time drilling operations. Examples of techniques purporting to provide real time drilling are described in patent/application Nos. U.S. Pat. Nos. 7,079,952, 6,266,619, 5,899,958, 5,139,094, 7,003,439, and U.S. Pat. No. 5,680,906.
A variety of technologies may be used to perform oilfield operations. In order to ensure efficiency in the oilfield operations, a company may implement methodologies for evaluating the effectiveness of the technologies. For example, information related to various aspects of the technologies may be collected and processed in a data repository.
Typically, a user of a particular technology may provide an evaluation based on his or her use of the technology. In some cases, a company may have a standard evaluation used to evaluate technologies based on a variety of factors such as: cost, ease of use, support, effectiveness, or some other factor related to the overall efficiency of the technology. In addition, a company may perform research and preliminary trials of potential technologies to evaluate the potential efficiency of the technologies.
As the number of utilized technologies increase, a more formal method may be adopted to manage the volume of information. For example, a spreadsheet may be used to consolidate information related to a variety of technologies. In another example, a business plan or method may include a specific technology adoption plan.
In general, in one aspect, the invention relates to a method for measuring technical maturity index (TMI) for oilfield operations of an oilfield, the oilfield having a subterranean formation with geological structures and reservoirs therein. The method includes sending an assessment including a listing of a number of capabilities to at least one user associated with a first oilfield operation, where each of the number of capabilities is associated with a technology for the oilfield operations, and receiving a first number of responses in response to the assessment for the first oilfield operation, where each of the first number of responses specifies one of the number of capabilities and a level of adoption corresponding to the one of the number of capabilities. The method further includes obtaining a TMI for the first oilfield operation using the first number of responses and presenting the TMI for the first oilfield operation.
In general, in one aspect, the invention relates to a system for measuring technical maturity index (TMI) for oilfield operations of an oilfield, the oilfield having a subterranean formation with geological structures and reservoirs therein. The system includes an assessment manager configured to send an assessment including a listing of a number of capabilities to at least one user associated with a first oilfield operation, where each of the number of capabilities is associated with a technology for the oilfield operations, and receive a first number of responses in response to the assessment for the first oilfield operation, where each of the first number of responses specifies one of the number of capabilities and a level of adoption corresponding to the one of the number of capabilities. The system further includes a technology maturity manager configured to obtain a TMI for the first oilfield operation using the first number of responses. The system further includes a technology maturity reporting tool operatively connected to the assessment manager and the technology maturity manager and configured to present the TMI for the first oilfield operation.
In general, in one aspect, the invention relates to a computer readable medium including computer program code embodied therein for causing a computer system to measure technical maturity index (TMI) for oilfield operations of an oilfield, the oilfield having a subterranean formation with geological structures and reservoirs therein. The computer program code includes program instructions to send an assessment including a listing of a number of capabilities to at least one user associated with a first oilfield operation, where each of the number of capabilities is associated with a technology for the oilfield operations, and receive a first number of responses in response to the assessment for the first oilfield operation, where each of the first number of responses specifies one of the number of capabilities and a level of adoption corresponding to the one of the number of capabilities. The computer program code further includes program instructions to obtain a TMI for the first oilfield operation using the first number of responses and present the TMI for the first oilfield operation.
Other aspects of the invention will be apparent from the following description and the appended claims.
Specific embodiments of the invention will now be described in detail with reference to the accompanying figures. Like elements in the various figures are denoted by like reference numerals for consistency.
In the following detailed description of embodiments of the invention, numerous specific details are set forth in order to provide a more thorough understanding of the invention. However, it will be apparent to one of ordinary skill in the art that the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid obscuring the invention.
In general, embodiments of the invention relate to providing a method and a system for measuring technology maturity. More specifically, embodiments of the invention relate to obtaining technology maturity indexes for oilfield operations based on responses to assessments for the oilfield operations. A response may specify the level of adoption of capabilities for generating the technology maturity index of an oilfield operation. Embodiments of the invention also include functionality to increase the technology maturity index of an oilfield operation.
The invention involves applications generated for the oil and gas industry.
The received sound vibration(s) (112) are representative of different parameters (such as amplitude and/or frequency). The data received (120) is provided as input data to a computer (122a) within the seismic recording truck (106a), and responsive to the input data, the recording truck computer (122a) generates a seismic data output record (124). The seismic data (within the seismic data output record (124)) may be further processed as desired, for example by data reduction.
A surface unit (134) is used to communicate with the drilling tool and offsite operations. The surface unit (134) is capable of communicating with the drilling tool to send commands to drive the drilling tool, and to receive data therefrom. The surface unit (134) is preferably provided with computer facilities for receiving, storing, processing and analyzing data from the oilfield (100). The surface unit (134) collects data output (135) generated during the drilling operation. Computer facilities, such as those of the surface unit (134), may be positioned at various locations about the oilfield (100) and/or at remote locations.
Sensors (S), such as gauges, may be positioned throughout the reservoir, rig, oilfield equipment (such as the downhole tool) or other portions of the oilfield (100) for gathering information about various parameters, such as surface parameters, downhole parameters and/or operating conditions. These sensors (S) preferably measure oilfield parameters, such as weight on bit, torque on bit, pressures, temperatures, flow rates, compositions, measured depth, azimuth, inclination and other parameters of the oilfield operation.
The information gathered by the sensors may be collected by the surface unit (134) and/or other data collection sources for analysis or other processing. The data collected by the sensors (S) may be used alone or in combination with other data. The data may be collected in a database and all or select portions of the data may be selectively used for analyzing and/or predicting oilfield operations of the current and/or other wellbores.
Data outputs from the various sensors positioned about the oilfield (100) may be processed for use. The data may be may be historical data, real time data or combinations thereof. The real time data may be used in real time, or stored for later use. The data may also be combined with historical data or other inputs for further analysis. The data may be housed in separate databases, or combined into a single database.
The collected data may be used to perform analysis, such as modeling operations. For example, the seismic data output may be used to perform geological, geophysical and/or reservoir engineering simulations. The reservoir, wellbore, surface and/or process data may be used to perform reservoir, wellbore, or other production simulations. The data outputs from the oilfield operation may be generated directly from the sensors, or after some preprocessing or modeling. These data outputs may act as inputs for further analysis.
The data is collected and may be stored at the surface unit (134). One or more surface units may be located at the oilfield (110), or coupled remotely thereto. The surface unit (134) may be a single unit, or a complex network of units used to perform the necessary data management functions throughout the oilfield (100). The surface unit (134) may be a manual or automatic system. The surface unit (134) may be operated and/or adjusted by a user.
The surface unit (134) may be provided with a transceiver (137) to allow communications between the surface unit (134) and various portions of the oilfield (100) and/or other locations, such as a remote office. The surface unit (134) may also be provided with or functionally linked and/or coupled to a controller for actuating mechanisms at the oilfield (100). The surface unit (134) may then send command signals to the oilfield (100) in response to data received. The surface unit (134) may receive commands via the transceiver or may itself execute commands to the controller. A processor (not shown) may be provided to analyze the data (locally or remotely) and make the decisions to actuate the controller. In this manner, the oilfield (100) may be selectively adjusted based on the data collected. These adjustments may be made automatically based on computer protocol, or manually by an operator. In some cases, well plans and/or well placement and/or well equipment (subsurface or production equipment) may be adjusted to select optimum operating conditions, or to avoid problems.
The wireline tool (106c) may provide data to a surface unit (134) of
Sensors (S), such as gauges, positioned about the oilfield are operatively connected to a surface unit (142) for collecting data therefrom. During the production process, data output (135) may be collected from various sensors and passed to the surface unit and/or processing facilities. As shown, the sensor (S) may be positioned in the production tool (106d) or associated equipment, such as the christmas tree (129), gathering network (146), surface facilities (142) and/or the production facility, to measure fluid parameters, such as fluid composition, flow rates, pressures, temperatures, and/or other parameters of the production operation.
While only one wellsite is shown, it will be appreciated that the oilfield (100) may cover a portion of land that hosts one or more wellsites. One or more gathering facilities may be operatively connected to one or more of the wellsites for selectively collecting downhole fluids from the wellsite(s).
Throughout the oilfield operations depicted in
While
The oilfield configuration of
Wellbore production equipment (164) extends from a wellhead (166) of wellsite and to the reservoir (104) to draw fluid to the surface. The wellsite is operatively connected to the gathering network (146) via a transport line (161). Fluid flows from the reservoir (104), through the wellbore (136), and onto the gathering network (146). The fluid then flows from the gathering network (146) to the process facilities (154).
As further shown in
One or more surface units (e.g., surface unit (134)) may be located at the oilfield (100), or linked remotely thereto. The surface unit (134) may be a single unit, or a complex network of units used to perform the necessary data management functions throughout the oilfield (100). The surface unit (134) may be a manual or automatic system. The surface unit (134) may be operated and/or adjusted by a user. The surface unit (134) is adapted to receive and store data. The surface unit (134) may also be equipped to communicate with various oilfield equipment. The surface unit (134) may then send command signals to the oilfield (100) in response to data received.
The surface unit (134) has computer facilities, such as memory (220), controller (222), processor (224), and display unit (226), for managing the data. The data is collected in memory (220), and processed by the processor (224) for analysis. Data may be collected from the oilfield sensors (S) and/or by other sources. For example, oilfield data may be supplemented by historical data collected from other operations, or user inputs.
The analyzed data may then be used to make decisions. A transceiver (not shown) may be provided to allow communications between the surface unit (134) and the oilfield (100). The controller (222) may be used to actuate mechanisms at the oilfield (100) via the transceiver and based on these decisions. In this manner, the oilfield (100) may be selectively adjusted based on the data collected. These adjustments may be made automatically based on computer protocol and/or manually by an operator. In some cases, well plans are adjusted to select optimum operating conditions, or to avoid problems.
A display unit (226) may be provided at the wellsite and/or remote locations for viewing oilfield data (not shown). The oilfield data represented by a display unit (226) may be raw data, processed data and/or data outputs generated from various data. The display unit (226) is preferably adapted to provide flexible views of the data, so that the screens depicted may be customized as desired. A user may determine the desired course of action during production based on reviewing the displayed oilfield data. The production operation may be selectively adjusted in response to the display unit (226). The display unit (226) may include a two dimensional display for viewing oilfield data or defining oilfield events. For example, the two dimensional display may correspond to an output from a printer, plot, a monitor, or another device configured to render two dimensional output. The display unit (226) may also include a three-dimensional display for viewing various aspects of the production operation. At least some aspect of the production operation is preferably viewed in real time in the three-dimensional display. For example, the three dimensional display may correspond to an output from a printer, plot, a monitor, or another device configured to render three dimensional output.
To facilitate the processing and analysis of data, simulators are typically used by the processor to process the data. Specific simulators are often used in connection with specific oilfield operations, such as reservoir or wellbore production. Data fed into the simulator(s) may be historical data, real time data or combinations thereof. Simulation through one or more of the simulators may be repeated or adjusted based on the data received.
As shown, the oilfield operation is provided with wellsite and non-wellsite simulators. The wellsite simulators may include a reservoir simulator (149), a wellbore simulator (192), and a surface network simulator (194). The reservoir simulator (149) solves for petroleum flow through the reservoir rock and into the wellbores. The wellbore simulator (192) and surface network simulator (194) solves for petroleum flow through the wellbore and the surface gathering network (146) of pipelines. As shown, some of the simulators may be separate or combined, depending on the available systems.
The non-wellsite simulators may include process and economics simulators. The processing unit has a process simulator (148). The process simulator (148) models the processing plant (e.g., the process facility (154)) where the petroleum is separated into its constituent components (e.g., methane, ethane, propane, etc.) and prepared for sales. The oilfield (100) is provided with an economics simulator (147). The economics simulator (147) models the costs of part or all of the oilfield (100). Various combinations of these and other oilfield simulators may be provided.
In one or more embodiments of the invention, each of the user(s) (302A, 302P) may correspond to a specialist associated with a technology. More specifically, each of the user(s) (302A, 302P) may correspond to an operator of a technology in an oilfield operation (304A, 304P). Alternatively, each of the user(s) (302A, 302P) may correspond to a consumer associated with the oilfield operation (304A, 304P). For example, a consumer may correspond to a supervisor of an oilfield operation (304A, 304P). In this example, the supervisor may indirectly interact with a technology associated with the oilfield operation (e.g., viewing reports created using the technology, directing a specialist associated with the technology, etc.). Those skilled in the art will appreciate that a technology may correspond to a variety of devices or methods that are used in an oilfield operation (e.g., data collection, remote monitoring, diagnostics, remote operation, modeling tools, etc.).
In one or more embodiments of the invention, the user(s) (302A, 302P) may interact with oilfield operations (304A, 304P). An oilfield operation (304A, 304P) may correspond to a production operation, an exploration operation, or a drilling operation as described with respect to
In one or more embodiments of the invention, the user(s) (302A, 302P) may interact with the TMS Interface (306). For example, the user(s) (302A, 302P) may access the TMS Interface (306) over the Internet (or other Wide Area Network or Local Area Network) using a web browser (or other interface for communicating over a network). Alternatively, the user(s) (302A, 302P) may interact with the TMS Interface (306) using an application running natively on a user's (302A, 302P) local computer (not shown). Further, in one or more embodiments of the invention, the TMS Interface (306) may interact with the user(s) (302A, 302P) through use of notifications. The notifications may be conveyed by electronic mail, short message service (SMS), or some other form of electronic correspondence.
In one or more embodiments of the invention, the TMS interface (306) may be configured to present assessments of technology maturity to the user(s) (302A, 302P). For example, the TMS interface (306) may be configured to present an assessment of technology maturity to a user (302A, 302P) through a web browser. Alternatively, the TMS interface (306) may be configured to transmit an assessment of technology maturity to a user (302A, 302P) by electronic mail or some other form of electronic correspondence. In one or more embodiments of the invention, the TMS interface (306) may be further configured to receive assessment responses from the user(s) (302A, 302P). In this case, the TMS interface (306) may be configured to interact with the TMS (308) in order to process the assessment responses. More specifically, the TMS (308) may be configured to extract and store technology maturity information in the assessment responses. In one or more embodiments of the invention, the user(s) (302A, 302P) may submit assessment responses based on activities performed as part of an oilfield operation (304A, 304P).
Those skilled in the art will appreciate that technology maturity information may be obtained using an assessment by a variety of collection methods (e.g., physical surveys, email surveys, through a web interface, some other collection method, or some combination thereof).
Continuing with the discussion of
In one or more embodiments of the invention, the TMS (308) may b e configured to store information in the TMS data source (310). In one or more embodiments of the invention, the TMS data source (310) is a data store (e.g., a database, a file system, one or more data structures configured in a memory, an extensible markup language (XML) file, some other medium for storing data, or any suitable combination thereof), which may include information (e.g., technology characteristics, adoption levels of capabilities, etc.) related to technologies.
In one or more embodiments of the invention, the TMS (308) may be configured to process assessment responses from user(s) (302A, 302P). More specifically, the TMS (308) may be configured to generate a technology maturity index based on the assessment responses. Further, the TMS (308) may be configured to use technology maturity indexes to measure the industry's adoption of technologies. More specifically, the TMS (308) may be configured to allow for structured measurement of progress in adopting capabilities, for comparison of the progress with business indicators, and for planning and measurement of the effectiveness of implementing the capabilities. For example, the system for measuring technology maturity may be configured to quantify capabilities associated with technologies and then compare capabilities across individual technology segments and within the segments across geographic areas.
In one or more embodiments of the invention, the technology maturity index may correspond to the adoption of technologies in an industry associated with the technologies. More specifically, the adoption of the technologies may be derived from adoption levels associated with a variety of capabilities associated with the technologies. Each capability may describe characteristics (e.g., amount of automation, monitoring, diagnostics, collaboration, etc.) of a corresponding technology. In one or more embodiments of the invention, the technology maturity index for an oilfield operation increases as the adoption level of capabilities increase for the oilfield operation. In this case, technology maturity index may describe the relative efficiency of an oilfield operations where the efficiency of the oilfield operation increases as capabilities are adopted at the oilfield operation. For example, an oilfield operation that has fully adopted each of the capabilities may be fully automated.
Examples of capabilities include, but are not limited to, data acquisition and transmission, monitoring activities, surveillance with warning capabilities, diagnostics and analysis, extended team and expertise, remote actuation and operation, model-centric diagnostics, global collaboration, model-based corrective action, and automation and autonomous action. Those skilled in the art will appreciate that any number of capabilities may be specified.
Those skilled in the art will appreciate that two or more of the capabilities may be cumulative. For example, the “monitoring activities at the well-site” capability may not be practiced until the “data acquisition and transmission from the wellsite” capability is adopted. In this example, an assessment may not allow the adoption level of the “monitoring activities at the well-site” capability to increase until the “data acquisition and transmission from the wellsite” capability is specified as fully adopted.
In one or more embodiments of the invention, the TMS (308) may be configured to quantify the adoption level of real-time capabilities and/or asynchronous capabilities. A real-time capability may be a capability that requires a response to an event by a deadline. For example, monitoring activities at a wellsite may be considered a real-time capability if information associated with the activities is provided simultaneously, or within a specified period of time, as the activities occur at the wellsite. An asynchronous capability may be a capability that does not require a response to an event by a deadline. For example, monitoring activities at a wellsite may be considered an asynchronous capability if the information associated with the activities is batched and provided based on a configurable schedule (e.g., hourly, daily, weekly, etc.).
In one or more embodiments of the invention, TMS (308) may be configured to generate a proactive action plan for implementing technologies to perform an oilfield operation. More specifically, the TMS (308) may be configured to generate the proactive action plan based on a target technology maturity index specified by user(s) (302A, 302P). The proactive action plan may account for the current adoption level of capabilities associated with the technologies in the oilfield operation, describing the relative efficiency of the oilfield operation. Further, the proactive action plan may accelerate the adoption of technologies in the oilfield operation. More specifically, the proactive action plan may allow for the adoption of technologies in the oilfield operation to be managed based on the adoption levels of the capabilities. The target technology maturity index may specify a target adoption level of capabilities. In this case, the proactive action plan may be configured to increase the adoption levels of capabilities until the target technology maturity index is achieved.
Those skilled in the art will appreciate that the proactive action plan may include a number of steps for increasing the adoption level of some of the capabilities. For example, a proactive action plan for a well production operation may include a step to increase the adoption of a model-based corrective action capability to a specific percentage (e.g., at least 75% adoption). Further, those skilled in the art will appreciate that the steps of the proactive action plan may be associated with any type of oilfield operation (e.g., well production operation, well construction operation, or some other oilfield operation). In one or more embodiments of the invention, once the proactive action plan has been defined, the proactive action plan (or some portion of the proactive action plan) may be implemented.
In one or more embodiments of the invention, the TMS interface (306) is configured to provide user(s) access to the TMS (308). More specifically, the TMS interface (306) may be configured to receive assessment responses from the user(s). Further, the TMS interface (306) may be configured to present technology maturity information to the user(s).
In one or more embodiments of the invention, the TMS interface (306) may interact with an assessment manager (404). More specifically, the assessment manager (404) may be configured to present an assessment to user(s) using the TMS Interface (306). For example, the assessment manager (404) may present an assessment, including requests for adoption levels of capabilities, to a user through a web browser. In one or more embodiments of the invention, an assessment may correspond to a survey related to the capabilities of an oilfield operation. For example, an assessment may include any number of inquiries related to the adoption levels of capabilities in an oilfield operation. In one or more embodiments of the invention, the inquiries may be answered by selecting yes or no. In this case, a number of inquiries may be used to ascertain the adoption level of a single capability. Alternatively, the inquiries may be answered by selecting a numerical value corresponding to the adoption level.
In one or more embodiments of the invention, the assessment manager (404) may be configured to process assessment responses from the user(s). For example, the assessment manager (404) may extract adoption levels for capabilities from the assessment responses. In this example, an adoption level may correspond to a numeric value (e.g., percentage, value on scale from 1 to 10, etc.). Those skilled in the art will appreciate that assessment responses may further include a variety of information associated with a technology (e.g., free-form comments, cost information, etc.).
In one or more embodiments of the invention, the TMS interface (306) may interact with a technology maturity reporting tool (402). More specifically, the technology maturity reporting tool (402) may be configured to present technology maturity information to the user(s) using the TMS interface (306). For example, the technology maturity reporting tool (402) may interact with the TMS data access system (406) to generate a technology maturity report. The technology maturity report may include graphical and/or textual representations of a technology maturity index of a technology. In one or more embodiments of the invention, the technology maturity index may be graphically represented as a combination of adoption levels of capabilities. For example, the valuation of each adoption level may be represented by a color (e.g., red representing low adoption, green representing high adoption, etc.). In this example, the technology maturity index may be represented as the sum of the adoption levels and similarly represented by a color. Alternatively, the adoption levels and technology maturity index may be represented by numerical values.
Those skilled in the art will appreciate that a technology maturity report may be associated with multiple technologies. Similarly, in this case, the technology maturity index of the technologies may be graphically represented and/or textually represented in a table.
In one or more embodiments of the invention, the technology maturity manager (410) may be configured to obtain technology maturity information. More specifically, the technology maturity manager (410) may be configured to obtain a technology maturity index based on assessment responses from user(s). For example, the technology maturity manager (410) may be configured to calculate a technology maturity index for a technology based on the adoption level of capabilities included in assessment responses associated with the technology. Further, the technology maturity index may be calculated based on the assessment responses from multiple users. Alternatively, the technology maturity manager (410) may be configured to obtain a technology maturity index based on assessment responses retrieved from the TMS data source (310). In this case, assessment responses associated with user(s) may be stored in the TMS data source (310).
In one or more embodiments of the invention, the technology data provider (408) may be configured to retrieve and store technology maturity information from the TMS data source (310). For example, the technology data provider (408) may be configured to retrieve technology maturity information for use by the technology maturity reporting tool (402). In this example, the technology data provider (408) may be configured to use the technology maturity manager (410) to obtain technology maturity indexes based on the technology maturity information.
In ST 502, responses to an assessment of technology maturity are received. In one or more embodiments of the invention, each response may specify an adoption level of a capability of the technology. Those skilled in the art will appreciate that each response may further specify a variety of information associated with the technology (e.g., relevant component of the technology, capability comments related to the technology, etc.). In one or more embodiments of the invention, the responses may be submitted by the user using a user interface (e.g., web browser, application running natively on the user's machine, etc.). Alternatively, the responses may be submitted by the user using some form of electronic correspondence (e.g., electronic mail, short message service, etc.)
Next, a technology maturity score may be obtained based on the responses (ST 504). Those skilled in the art will appreciate that the technology maturity score may be calculated using a variety of formulas (e.g., summation, product, average, etc.). In one or more embodiments of the invention, the technology maturity score may be calculated based on numerical values associated with each of the responses. For example, the technology maturity score may correspond to a weighted summation of the numerical values associated with the responses. In this example, each response may be weighted by a factor based on the capability associated with the response. Those skilled in the art will appreciate that each factor may be determined based on a variety of information (e.g. extent of automation of the capability, difficulty of implementing the capability, sequential order of typical implementation of the capability, and/or some other information associated with the capability).
In one or more embodiments of the invention, the responses to the assessment may correspond to adoption levels including, but not limited to, the following: infrequently or rarely practiced, occasionally practiced, and systematically practiced. In this case, each response may be associated with a numerical value as discussed above based on the adoption level (e.g., 0—infrequently or rarely practiced, 1—occasionally practiced, 2—systematically practiced).
The technology maturity score may then be incorporated into a technology maturity index (TMI) (ST 506). In one or more embodiments of the invention, the TMI may correspond to the average of a number of technology maturity scores. In this case, the technology maturity scores received in response to the assessment may be averaged to calculate the TMI.
At this stage, a determination may be made as to whether more responses to the assessment have been received (ST 508). In one or more embodiments of the invention, responses to the assessment may be received from a number of users. Those skilled in the art will appreciate that the responses may be received by a variety of methods (e.g., electronic mail, web application interface, advanced program interface, etc.). In one or more embodiments of the invention, the TMI may be updated as the responses to the assessments are received. Alternatively, the TMI may be calculated based on a schedule (i.e., allowing a certain period of time for responses to be received) and/or after a certain number of responses are received. For example, the TMI may be calculated after responses to the assessment are received from all the users that received the assessment. In another example, the TMI may be calculated after responses to the assessment are received from a percentage (e.g., 50 percent, 75 percent, etc.) of the users that received the assessment.
Optionally, the TMI may be normalized (ST 510). In one or more embodiments of the invention, the TMI calculated in ST 506 may be based on an abnormal numerical range (e.g., 0 to 110, 0 to 22, etc.). In this case, the TMI may be normalized to convert the TMI to a standard numerical range. For example, a TMI based on an abnormal numerical range may be normalized to range from 0 to 100. In this example, the TMI may be normalized to range from 0 to 100 using the following formula:
where S(n) is the factor of each capability, ten capabilities are used to calculated the TMI, and the abnormal numerical range is 0 to 110.
The TMI may be stored in a data source (ST 512). Those skilled in the art will appreciate that a variety of information related to the TMI may also be stored (e.g., responses to the assessment, user information, capability information, etc.).
In ST 602, a request for technology maturity information may be received from a user. In one or more embodiments of the invention, the request may include criteria selected by the user. For example, the criteria may specify that only technology information associated with a specific business unit should be retrieved. Those skilled in the art will appreciate that any number of criteria may be specified related to a variety of attributes (e.g., business unit, technology area, geographic region, etc.).
In response to receiving the request, technology maturity information may be retrieved (ST 604). In one or more embodiments of the invention, the technology maturity information may be retrieved using criteria specified by the user. Those skilled in the art will appreciate that the technology maturity information may include a variety of information related to the technology (e.g. technology information, capability information, technology maturity index (TMI), responses to assessments, or some other information associated with technology maturity).
At this stage, output may be generated using the technology maturity information (ST 606). In one or more embodiments of the invention, the output may be generated in a tabular format. Those skilled in the art will appreciate that the technology maturity information included in the tabular format may be filtered by a variety of attributes (e.g. oilfield operation, geographic region, date and/or time, business group, area of technology, TMI value, or some other attribute). For example, the tabular format may include the technology maturity information associated with a group of oilfield operations. In another example, the tabular format may include the technology maturity information associated with an oilfield operation at multiple time intervals. In another example, the tabular format may include technology maturity information associated an oilfield operation in a geographic region. In another example, the tabular format may include technology maturity information associated with a single oilfield operation.
Alternatively, in one or more embodiments of the invention, the output may be generated in a graphical format. For example, the graphical format may depict a map of geographical regions displaying technology maturity information on a geographic-region basis. Further, in one or more embodiments of the invention, the graphical format may allow the user to restrict the technology maturity information displayed to a specific graphical region including more detailed technology maturity information. For example, the graphical format may depict a map of geographical regions that allow the user select a geographic region in order to view technology maturity information associated with sub-regions associated with the geographic region. Alternatively, the graphical format may allow the user to view the tabular format of the technology maturity information associated with a selected geographic region. In another example, the graphical format may depict a three-dimensional representation of technology maturity information based on a variety of characteristics (e.g., capabilities, oilfield operations, geographic regions, business units, technology area, etc.). In this case, each axis of the three-dimensional representation may correspond to one of the aforementioned characteristics.
Next, the output may be presented to the user (ST 608). Those skilled in the art will appreciate that presenting of the technology maturity information may allow for comparison between different oilfield operations. For example, the adoption level of the “model-based corrective action” capability may be presented as systematically practiced at a first oilfield operation and rarely practiced at a second oilfield operation. In this example, the user may allocate resources between the oilfield operations based on a comparison of the capabilities of the oilfield operations.
In ST 702, technology maturity information associated with an oilfield operation may be obtained. Those skilled in the art will appreciate that a variety of information associated with technology maturity may be obtained (e.g. technology information, capability information, technology maturity index (TMI), responses to assessments, or some other information associated with technology maturity). For example, technology maturity information may be obtained as described with respect to
At this stage, a target TMI may be specified for the oilfield operation (ST 704). In one or more embodiments of the invention, the target TMI may correspond to a target adoption level of technological capabilities. For example, the target TMI may specify target adoption levels for capabilities (e.g., monitoring activities, surveillance with warning capabilities, diagnostics and analysis, extended team and expertise, etc.) in an oilfield operation.
Those skilled in the art will appreciate that the target TMI and adoption levels for capabilities may be specified based on a variety of considerations. For example, the target TMI and adoption levels may be specified based on the requirements of the company associated with the oilfield operation. In another example, the target TMI and adoption levels may be specified based on assessments of oilfield operations performed by competing companies. In this example, a competing TMI for an oilfield operation of a competing company may be calculated and then used to specify the target TMI and adoption levels for the proactive action plan.
The proactive action plan to increase the TMI to the target TMI may be generated (ST 706). In one or more embodiments of the invention, the proactive action plan may specify steps for achieving target adoption levels for each of the capabilities in order to increase the TMI to the target TMI. For example, the proactive action plan may specify that the ability to operate a drilling bit from a remote location must be adopted in order to reach the target TMI.
Optionally, the TMI associated with the oilfield operation may be monitored (ST 708). In one or more embodiments of the invention, the TMI may be monitored for changes in the TMI. In this case, the proactive action plan may be modified based on the changes to the TMI. For example, a step of the proactive action plan may be removed once a certain TMI has been reached. Those skilled in the art will appreciate that other information associated with technology maturity may be monitored (e.g., capability information, technology information, etc.). For example, a step of the proactive plan may be associated with an alternate capability if the cost associated with the original capability increases past a threshold.
The following is an example of a progressive adoption of capabilities for an oilfield operation as described with respect to
Specifically, the example shows the progressive adoption of adopted processes in a well construction operation, where each adopted process is followed by the capability corresponding to the adopted process:
In this example, the technology maturity index of the well construction operation increases as each of the processes is adopted. Assuming that all the processes are systematically practiced, the well construction operation may now have the highest technology maturity index because each of the required capabilities has been adopted in the processes.
In another example, the current technology maturity index of a well construction operation that has not fully adopted each process may be obtained based on the factors and adoption level of the capability corresponding to each process. The following table specifies adoption levels of each capability for the well construction operation:
The adoptions levels included in Table 1 specify that (1) the processes corresponding to capability levels 1-4 are systematically practiced at the well construction operation; (2) the processes corresponding to capability levels 5-6 are occasionally practiced at the well construction operation; and (3) the processes corresponding to capability levels 7-10 are infrequently or rarely practiced at the well construction operation.
Using the values included in Table 1, the technology maturity index may be calculated as discussed with respect to
At this stage, the technology maturity index may be evaluated in comparison to a target technology maturity index. More specifically, a proactive action plan may be generated to increase the technology maturity index to the target technology maturity index. The following table (Table 2) shows adoption levels and technology maturity indexes for a current well construction operation compared to an exemplary proactive action plan:
The proactive action plan of Table 2 specifies capabilities that require an increase in adoption level in order to achieve the target technology maturity index. More specifically, the adoption levels for the proactive action plan of Table 2 specify that the processes corresponding to capability level 7 (i.e., model-centric diagnostics) and capability level 8 (i.e., global collaboration) should be increased to occasionally practiced and that the process corresponding to capability level 5 (i.e., extended team and expertise) should be increased from occasionally practices to systematically practiced. In this case, the implementation of the proactive action plan would increase the technology maturity index of the well construction operation to 46.
In another case, the technology maturity index may be compared to the technology maturity index of other well construction operations. For example, technology maturity indexes may be compared based on the geographic region of the well construction operations. The following table (Table 3) shows adoption levels and technology maturity indexes for well construction operations in multiple geographic areas:
The technology maturity indexes of Table 3 may be used to compare the technology maturity of Area A and Area B. More specifically, the values of Table 3 may be used to efficiently allocate resources between both areas.
The following is an example of a progressive adoption of capabilities for an oilfield operation as described with respect to
In this example, the technology maturity index of the well production operation increases as each of the processes is adopted. The well production operation may now be calculated based on the factors and the adoption level of the capabilities adopted on the processes.
The assessment (800) includes a list of geographic regions (802) for the user to specify a geographic region for the assessment (800). The selected geographic region may be used to categorize data associated with the assessment to allow technology maturity indexes to be compared on a geographic-region basis. The assessment (800) further includes a list of oilfield operations (804) for the user to specify an oilfield operation for the assessment (800). The oilfield operations may correspond to, for example, production operations, exploration operations, and/or drilling operations as described with respect to
The assessment (800) further includes a listing of capabilities (806). The assessment (800) allows the user to specify a level of adoption (808) for each capability. Each specified level of adoption may correspond to a response to the assessment (800) as discussed above with respect to
The three-dimensional output (900) includes three axes corresponding to three characteristics (e.g., capabilities, oilfield operations, geographic regions, business units, technology area, etc.) for presenting technology maturity. In this example, the three-dimensional output (900) includes an axis corresponding to the capabilities (902) used for calculating technology maturity, an axis corresponding to the operations (i.e., oilfield operations) (904) of the technology maturity, and an axis corresponding to the geographic regions (906) of the technology maturity. The three-dimensional output (900) may present technology maturity indexes (not shown) associated with specific operations (904) and geographic regions (906). Further, the presentation of a technology maturity index (not shown) for a specific operation (904) and geographic region (906) may show the adoption levels of each of the capabilities (902). The three-dimensional output (900) may be used to efficiently allocate resources between the various operations (902) and geographic regions (904) included in the three-dimensional output (900).
Those skilled in the art will appreciate that output in a tabular format may be generated to include similar information as the three-dimensional output (900). In this case, one of the axes of the three-dimensional output (900) is not included in order to allow the information to be presented in a two-dimensional tabular format as shown in the following table (Table 4):
The technology maturity indexes of Table 4 may be used to compare the technology maturity of numerous operations and geographic regions. Further, the geographic regions included in a tabular format may be of a variety of granularities (e.g., continent, country, county, state, etc.). For example, Table 4 includes five continents as well as nested countries for the continent of Europe. Those skilled in the art will appreciate that output in a tabular format as shown in Table 4 may include any number of geographic regions.
The values of Table 4 may be used to efficiently allocate resources between the operations and geographic regions included in Table 4. For example, the values for technology maturity in Europe may be compared to the technology maturity in other continents in order to determine whether resources should be allocated to specific countries in Europe.
Those skilled in the art will appreciate that output including a map of geographic regions may be generated to include similar information as the three-dimensional output (900). In this case, each geographic region (e.g., continent, country, county, state, etc.) may be depicted such that the technological maturity of the geographic region is represented. For example, each geographic may be depicted in a particular color specifying a technology maturity index.
The invention may be implemented on virtually any type of computer regardless of the platform being used. For example, as shown in
Further, those skilled in the art will appreciate that one or more elements of the aforementioned computer system (1000) may be located at a remote location and connected to the other elements over a network. Further, the invention may be implemented on a distributed system having a plurality of nodes, where each portion of the invention (e.g., assessment manager, TMS data source, TMS data access system, etc.) may be located on a different node within the distributed system. In one or more embodiments of the invention, the node corresponds to a computer system. Alternatively, the node may correspond to a processor with associated physical memory. The node may alternatively correspond to a processor with shared memory and/or resources. Further, software instructions to perform embodiments of the invention may be stored on a computer readable medium such as a compact disc (CD), a diskette, a tape, a file, or any other computer readable storage device.
While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as disclosed herein. Accordingly, the scope of the invention should be limited only by the attached claims.
This application claims priority, pursuant to 35 U.S.C. §119(e), to the filing date of U.S. Patent Application Ser. No. 60/925,102, entitled “Method and System for Measuring Technology Maturity,” filed on Apr. 18, 2007, which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4794534 | Millheim | Dec 1988 | A |
5058012 | Hinchman et al. | Oct 1991 | A |
5139094 | Prevedel et al. | Aug 1992 | A |
5444619 | Hoskins et al. | Aug 1995 | A |
5680906 | Andrieux et al. | Oct 1997 | A |
5899958 | Dowell et al. | May 1999 | A |
5992519 | Ramakrishnan et al. | Nov 1999 | A |
6176312 | Tubel et al. | Jan 2001 | B1 |
6266619 | Thomas et al. | Jul 2001 | B1 |
6313837 | Assa et al. | Nov 2001 | B1 |
6810332 | Harrison | Oct 2004 | B2 |
6980940 | Gurpinar et al. | Dec 2005 | B1 |
7003439 | Aldred et al. | Feb 2006 | B2 |
7079952 | Thomas et al. | Jul 2006 | B2 |
7142986 | Moran | Nov 2006 | B2 |
7878268 | Chapman et al. | Feb 2011 | B2 |
20030132934 | Fremming | Jul 2003 | A1 |
20030216897 | Endres et al. | Nov 2003 | A1 |
20040220846 | Cullick et al. | Nov 2004 | A1 |
20050119911 | Ayan et al. | Jun 2005 | A1 |
20050149307 | Gurpinar et al. | Jul 2005 | A1 |
20050209836 | Klumpen et al. | Sep 2005 | A1 |
20050209886 | Corkern | Sep 2005 | A1 |
20050211468 | Veeningen et al. | Sep 2005 | A1 |
20050228905 | Veeningen et al. | Oct 2005 | A1 |
20050236184 | Veeningen et al. | Oct 2005 | A1 |
20060197759 | Fremming | Sep 2006 | A1 |
20070061180 | Offenberg | Mar 2007 | A1 |
20070112547 | Ghorayeb et al. | May 2007 | A1 |
Number | Date | Country |
---|---|---|
2392931 | Mar 2004 | GB |
2411669 | Sep 2005 | GB |
9964896 | Dec 1999 | WO |
2004049216 | Jun 2004 | WO |
Entry |
---|
International Search Report dated Aug. 22, 2008 (3 pages). |
Number | Date | Country | |
---|---|---|---|
20080262886 A1 | Oct 2008 | US | |
20090119139 A2 | May 2009 | US |
Number | Date | Country | |
---|---|---|---|
60925102 | Apr 2007 | US |