Method and system for managing well data

Abstract

The invention discloses a method and a system for managing well data, which are characterized by comprising the following steps of: creating a three-level data model consisting of a well, a borehole belonging to the well and an operation activity belonging to the borehole; along with the promotion of well business activities, the three-level data module is continuously updated according to operation results of various business activities of wells at different positions, and a well data management database is formed.

Description

Technical Field

[0001] The present invention relates to the technical field of oil engineering data acquisition and storage, and in particular to a method and system for managing well data. Background Art

[0002] During the construction process of an oil engineering well site, it is necessary to collect the data of each specialty and transmit it back to the rear base in real time for real-time drilling support and in-depth later data applications.

[0003] Existing data acquisition and storage technologies generally design the data logical structure of each construction team for each construction team. When storing data, all the data of this construction team are stored by newly creating a well number and transmitted back to the rear base. When each construction team conducts construction operations, data acquisition and remote transmission are carried out in this way, and finally the data are stored in different specialized companies at the rear. In this way, for all professional operation activities, a new well number needs to be created, which easily leads to inconsistent well numbers, and there may be duplicate well numbers in different regions and different clients. It is necessary for the client unit to set it as a combined primary key, resulting in difficulties in the process of data management and application.

[0004] Secondly, in the case where a well needs to conduct multi-wellbore construction, the existing technology needs to manage multiple wellbores of a well as multiple wells, so that the associated information between wellbores will be lost. Moreover, for the case of multiple construction operations in the same depth section, such as multiple analyses of sampling samples, the existing technology can only save the construction data of the same depth section once, resulting in data loss.

[0005] In summary, at an oil engineering well site, there are often multiple professional construction teams (operation activities) such as drilling, logging, well logging, directional well, and geological steering. There is also an on-site analysis and testing team for sample analysis during drilling. Each construction team and each instrument and equipment will generate corresponding data, and all the data are gathered together to form all the data of this well. Therefore, how to effectively organize all types of data of a well is an urgent problem to be solved by the existing technology. Summary of the Invention

[0006] The purpose of the present invention is to provide a technical solution for effectively fusing the data collected in different construction teams (operation activities), different construction times, different construction sites, etc. involved in the same major production task.

[0007] To solve the above technical problems, an embodiment of the present invention provides a method for managing well data, including: creating a three-level data model composed of a well, a wellbore subordinate to the well, and an operation activity subordinate to the wellbore; along with the progress of well business activities, continuously updating the three-level data module according to the operation results of various business activities of wells at different positions to form a well data management database.

[0008] Preferably, in the process of creating the three-level data model, it includes: establishing a model framework with the well, wellbore, and operation activity as the main bodies, and defining each level of the main body by configuring corresponding basic information tables for each level of the main body. Among them, the primary key of the well basic information table is configured with a well identifier having a globally unique representation property; additional information tables are configured for each level of the main body.

[0009] Preferably, the well basic information table at least includes: the well identifier, well number, and well characteristic information, and the well characteristic information includes but is not limited to: well type, well category, well classification, wellhead coordinates, structural unit, affiliated oil and gas field, and geographical location basic information; the wellbore basic information table at least includes: wellbore identifier, wellbore name, wellbore number, and parent wellbore identifier; the operation activity basic information table at least includes: operation identifier, the wellbore identifier, operation classification type, operation name, and operation organization information table, where the information recorded in the operation organization information table includes but is not limited to: operation unit, operation personnel, instrument information, and operation start and end times.

[0010] Preferably, the well additional information table at least includes: well position measurement data table and well location design data table; the wellbore additional information table at least includes: formation layering table and completion data table; the operation activity additional information table at least includes: operation result data tables for each operation activity during each operation, and the operation activities include but are not limited to conventional logging operations, gas logging operations, core logging operations, analysis and testing operations, logging while drilling operations, measurement while drilling operations, directional operations, geosteering operations, and various types of logging operations.

[0011] Preferably, each additional data table at the well level contains a well identifier field; each additional data table at the wellbore level contains a wellbore identifier field associated with the affiliated well; each additional data table at the operation activity level contains an operation activity identifier field associated with the affiliated wellbore.

[0012] Preferably, the well identifier, the wellbore identifier, and the operation activity identifier are defined using the GUID type, and the corresponding identifiers are generated by taking the identifier numbers on the network card and the processor clock numbers.

[0013] Preferably, during the process of creating a new job activity, it includes: searching for the corresponding well from the well data management database according to the well number of the well to which the job activity to be created currently belongs; automatically generating and inputting the basic information table of the job activity for the current new job under the well and wellbore to which the currently to-be-created wellbore belongs, so as to create a new job, and then, configuring the additional information table of the current new job according to requirements. Among them, if the well to which the currently to-be-created wellbore belongs is not searched, a new well is created.

[0014] Preferably, during the process of creating a new well, it includes: automatically generating and inputting the basic information table of the well, and among them, while inputting the well number, a well identifier with a globally unique property is automatically generated.

[0015] Preferably, during the process of creating a new wellbore, it includes: searching for the corresponding well from the well data management database according to the well number of the well to which the currently to-be-created wellbore belongs; automatically generating and inputting the basic information table of the wellbore for the current new wellbore under the well to which the currently to-be-created wellbore belongs, so as to create a new wellbore, and then, configuring the additional information table of the current new wellbore according to requirements. Among them, if the well to which the currently to-be-created wellbore belongs is not searched, a new well is created.

[0016] On the other hand, an embodiment of the present invention further provides a system for managing well data, and the system is used to implement the method as described above. Among them, it includes: a three-level data model creation model configured to create a three-level data model composed of a well, a wellbore subordinate to the well, and a job activity subordinate to the wellbore; a database formation module configured to continuously update the three-level data module according to the job results of various business activities of wells at different positions as the well business activities progress, so as to form a well data management database.

[0017] Compared with the prior art, one or more of the above embodiments may have the following advantages or beneficial effects:

[0018] The present invention proposes a method and system for managing well data. The method and system are based on a business-driven three-layer data model, and the definition of three data levels is achieved by establishing a "well basic information table", a "wellbore basic information table" and a "job basic information table". The logical relationship between the relevant professional data of each item and each operation activity corresponding to each well can be transmitted through the well mark field, the wellbore mark field and the operation activity mark field, and one well mark data can lead all the data of the well. In addition, the present invention can also flexibly add wellbores and operation items, and flexibly realize the allocation and data storage of new construction tasks by adding new operations, thereby realizing the integrated data fusion of business data of different professions and different time periods. In this way, the present invention uses the well identifier to lead all the data of the well, and the data of various professions are organically integrated, all belonging to the data of the well. It is of great significance for the later well data asset management and the integration and in-depth application of multi-professional data. It can comprehensively record various well data, improve the efficiency of well data management, and ensure the effective retention of data.

[0019] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. Brief Description of the Figures

[0020] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings:

[0021] Figure 1 This is a schematic diagram of the steps of the method for managing well data in an embodiment of the present application.

[0022] Figure 2 This is a schematic diagram of the three-level data principle in the method for managing well data in an embodiment of the present application.

[0023] Figure 3 This is a schematic diagram of the basic information table and additional information table at each level in the method for managing well data in an embodiment of the present application.

[0024] Figure 4 This is a schematic diagram of the structure of a system for managing well data according to an embodiment of the present application. Specific implementation method

[0025] The embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings and embodiments, so as to fully understand how the present invention uses technical means to solve technical problems and achieve the implementation process of technical effects and implement accordingly. It should be noted that as long as there is no conflict, the various embodiments in the present invention and the various features in each embodiment can be combined with each other, and the formed technical solutions are all within the protection scope of the present invention.

[0026] In addition, the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. And although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0027] The terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms "a" and "an" used herein are also intended to include the plural. It should also be understood that the terms "comprises" and / or "comprising" used herein specify the presence of the stated features, integers, steps, operations, units and / or components, and do not preclude the presence or addition of one or more other features, integers, steps, operations, units, components and / or combinations thereof.

[0028] During the construction process of an oil engineering well site, it is necessary to collect the data of each specialty and transmit it back to the rear base in real time for real-time drilling technology support and in-depth application of the data in the later stage.

[0029] In the existing data collection and storage technology, generally, the data logic structure of each construction team is designed for each construction team. When storing data, all the data of this construction team are stored by newly creating a well number and transmitted back to the rear base. When each construction team conducts construction operations, data collection and remote transmission will be carried out in this way, and finally the data will be stored in different specialized companies at the rear. In this way, for all professional operation activities, new well numbers need to be created, which easily leads to inconsistent well numbers, and there may be problems of duplicate well numbers in different regions and different clients, and the client unit needs to set it as a combined primary key, resulting in difficulties in the process of data management and application.

[0030] Secondly, in the case where a well needs to carry out multi-wellbore construction, the existing technology needs to manage the multiple wellbores of a well as multiple wells, so that the associated information between wellbores will be lost. Moreover, for the case of multiple construction operations in the same depth section, such as multiple analyses of sampling samples, the existing technology can only save the construction data once in the same depth section, resulting in data loss.

[0031] In summary, in an oil engineering well site, there are often multiple professional construction teams (operation activities) such as drilling, logging, well logging, directional drilling, and geosteering. There is also an on-site analytical and testing team following the drilling to conduct sample analysis. Each construction team and each piece of instrument and equipment generate corresponding data, and all the data is aggregated to form all the data of this well. Therefore, how to effectively organize all types of data of a well is an issue urgently to be solved in the existing technology.

[0032] Therefore, to solve one or more of the above technical problems, the present application proposes a method and system for managing well data. The method and system establish operations based on oil engineering business activities, use operations as the basic organizational unit, and organize all the business data of the well site through a three-layer data model of "well" - "borehole" - "operation".

[0033] Figure 1 It is a schematic diagram of the steps of the method for managing well data according to an embodiment of the present application. The following refers to Figure 1 to illustrate the specific step process of the method for managing well data (also referred to as the "well data management method") described in the embodiments of the present invention.

[0034] Step S110 creates a three-level data model based on business activities. The three-level data model consists of a well, boreholes subordinate to the well, and operation activities subordinate to the boreholes.

[0035] In step S110, a (three-level) model framework with the well, boreholes, and operation activities as the main bodies is established, and each level of the main body is defined by configuring a corresponding basic information table for each level of the main body.

[0036] Based on the design concept of the data model of business activities in the embodiments of the present invention, the single well is used as the first-level data, a second-level data with the single well as the object main body is established, and finally, according to different business activity types, operation activities with the borehole as the main body are established, so as to organize all the business data of the well site through a three-level structure data model of "well" - "borehole" - "operation" with the operation (activity type) as the basic organizational unit.

[0037] Figure 2 It is a schematic diagram of the three-level data principle in the method for managing well data according to an embodiment of the present application. As Figure 2 shown, multiple borehole-level data are established under the single well level, and under the borehole data level, multiple operation activities of different operation types are also established (for example: drilling operation, well logging operation, logging operation, etc.). Table 1 is a specific example of the three-level data model framework based on the three-level hierarchical structure.

[0038] Table 1 Example of the hierarchical structure of the three-level data model framework

[0039]

[0040] In the embodiments of the present invention, the various operation activities include but are not limited to: conventional mud logging operations, gas logging operations, core logging operations, analysis and testing operations, logging while drilling (LWD) operations, measurement while drilling (MWD) operations, directional operations, geosteering operations, and various types of logging operations.

[0041] In the embodiments of the present invention, in addition to establishing a three-level data model framework, it is also necessary to design various types of data tables belonging to each level for each level. The tables representing the well level include a well basic information table, a well position measurement data table, a well location design data table, etc.; the tables representing the wellbore level include a wellbore basic information table and data tables expressing wellbore-related information such as a formation stratification table and a well completion data table; the tables representing the operation activity level include an operation basic information table and other data tables reflecting the actual construction of this operation. In the actual application process, a well can include multiple wellbores, and a wellbore can include multiple operation activities.

[0042] After the establishment of the three-level data model framework is completed, the embodiments of the present invention also define each level of the main body by configuring corresponding basic information tables for each level of the main body. Among them, the primary key of the well basic information table is configured with a well identifier (JID) with a globally unique representation property.

[0043] Figure 3 It is a general recording schematic diagram of the basic information tables and additional information tables for each level in the method for managing well data according to the embodiments of the present application. As Figure 3 shown, in one embodiment, the well basic information table at least includes: a well identifier (JID), a well number, and well characteristic information. The well characteristic information includes but is not limited to: well type, well pattern, well category, wellhead coordinates, tectonic unit, affiliated oil and gas field, and geographical location basic information.

[0044] Refer to Figure 3 , in one embodiment, the wellbore basic information table at least includes: a wellbore identifier (JYID), a wellbore name, a wellbore number, and a parent wellbore identifier (this parent wellbore identifier (FJYID) represents the identifier of the well to which the wellbore belongs or the identifier of the upper-level wellbore).

[0045] Continuing to refer to Figure 3 , in one embodiment, the operation activity basic information table at least includes: an operation identifier (ZYID), a wellbore identifier (JYID), an operation classification type (operation activity type), an operation name (operation sequence), and an operation organization information table. Among them, the information recorded in the operation organization information table includes but is not limited to: operation unit, operation personnel, instrument information, and operation start and end times.

[0046] In addition, step S110 will also configure additional information tables for each level of the main body.

[0047] In one embodiment, the well additional information table at least includes: a well position measurement data table and a well position determination design data table.

[0048] In one embodiment, the wellbore additional information table at least includes: a formation layering table and a well completion data table.

[0049] In one embodiment, the operation activity additional information table at least includes: an operation result data table for each operation activity during each operation.

[0050] In addition, not only does the basic information table of each level contain the identification field of the corresponding level, but the additional information table of each level also contains the identification field of the corresponding level. Specifically, each additional data table at the well level contains a well identification field; each additional data table at the wellbore level contains a wellbore identification field associated with the well to which it belongs; and each additional data table at the operation activity level contains an operation activity identification field associated with the wellbore to which it belongs.

[0051] In this way, the three-level data model in the embodiment of the present invention is built using three levels: well, wellbore, and operation activity, and there are several data tables at each level. The data tables at the well level all contain the "JID" field, the data tables at the wellbore level all contain the "JYID" field, and the data tables at the operation level all contain the "ZYID" field. In this way, for a well constructed by multiple professional teams, the logical relationships of all relevant professional data can be transmitted through "JID", "JYID", and "ZYID". Thus, all the data of the well can be led by a "JID" mark.

[0052] To ensure the non-repetitiveness of each well constructed, the well identification, wellbore identification, and operation activity identification described in the embodiment of the present invention are all defined using the GUID type. Among them, for various identifications (well identification, wellbore identification, and operation activity identification) created at different times, the identification numbers on the network card are directly taken and combined with the processor clock numbers to generate.

[0053] In the embodiment of the present invention, various identifications generated at different creation times can be a 16-byte binary data.

[0054] After the construction of the three-level data model is completed, it enters step S120.

[0055] In step S120, along with the progress of the actual well operation activities, according to the operation results of various operation activities of wells at different positions, the three-level data module is continuously updated to form a well data management database.

[0056] In step S120, as the single well construction continues to advance, operation items can be flexibly added, and the allocation and data storage of new construction tasks can be flexibly realized by adding new operations, thereby realizing the integrated data fusion of business data of different professions and different time periods.

[0057] In the process of creating a new operation activity, it includes: first, according to the well number of the well to which the current operation activity belongs, search for the corresponding well from the well data management database; then, under the well and well to which the current wellbore to be created belongs, automatically generate and enter the basic information table of the operation activity of the current new operation, so as to create a new operation, and then configure the additional information table of the current new operation according to the needs. Among them, when entering the operation type, it also automatically generates a globally unique operation activity identifier, so that the newly created operation activity identifier is used as the primary key of the basic information table of the current operation activity.

[0058] In addition, if the well to which the wellbore to be created belongs is not found, a new well needs to be created immediately.

[0059] In this way, when a new construction operation begins, a new operation activity needs to be created. When creating a new operation activity, it is necessary to first determine the well number to which it belongs. The specific process can be: select the well number or wellbore number from the well site database. If there is no well number, create a new well. Therefore, since the operation activity basic information table contains the operation activity identification field, it is automatically generated when a new operation is created and included in the wellbore range to which the current operation activity belongs.

[0060] Furthermore, in the process of creating a new well, it includes: automatically generating a well basic information table and entering it. Among them, when entering the new well number, a well identifier with global uniqueness is also automatically generated, so that the newly created well identifier is used as the primary key of the current well basic information table.

[0061] In this way, the well basic information table contains a well identification field, which is automatically generated when a new well is created. It serves as the basis for managing all the data of this well, thus avoiding data conflicts caused by repeated well numbers.

[0062] A new borehole must be created immediately after a new well is created. In the process of creating a new borehole, it includes: first, according to the well number of the well to be created, the corresponding well is searched from the well data management database; then, under the well to be created, the well basic information table of the current new borehole is automatically generated and entered, so as to create a new borehole, and then, the additional information table of the current new borehole is configured according to the needs. Among them, when entering the well number, a wellbore identifier with global uniqueness is also automatically generated, so that the newly created wellbore identifier is used as the primary key of the current wellbore basic information table.

[0063] In addition, if the well to which the current wellbore to be created belongs is not found, a new well is created according to the above method.

[0064] In this way, since the wellbore basic information table contains the wellbore identification field, it is automatically generated when a new wellbore is created, and the well to which it belongs and the parent wellbore information can be found. In addition, other wellbore-level tables also contain the same wellbore identification and well identification fields, thus showing the logical relationship between the wellbores and the wells to which they belong.

[0065] On the other hand, based on the above-mentioned well data management method, an embodiment of the present invention also provides a system for managing well data (also called "well data management system").

[0066] Figure 4 is a schematic diagram of the structure of the system for managing well data in an embodiment of the present application. Figure 4 As shown in FIG. 1 , the well data management system includes: a three-level data model creation model 410 and a database formation module 420.

[0067] Specifically, the three-level data model creation model 410 is used to create a three-level data model consisting of a well, a wellbore subordinate to the well, and an operation activity subordinate to the wellbore; the database generation module 420 is used to continuously update the three-level data module according to the operation results of various business activities of wells in different locations as the well business activities progress, thus forming a well data management database.

[0068] The present invention discloses a method and system for managing well data. The method and system are based on a business-driven three-layer data model, and define three data levels by establishing a "well basic information table", a "wellbore basic information table" and a "job basic information table". The logical relationship between the relevant professional data for each item and each operation activity corresponding to each well can be transmitted through the well mark field, the wellbore mark field and the operation activity mark field, and one well mark data can command all the data of the well. In addition, the present invention can also flexibly add wellbores and operation items, and flexibly realize the allocation and data storage of new construction tasks by adding new operations, thereby realizing the integrated data fusion of business data of different professions and different time periods. In this way, the present invention commands all the data of the well by the well identifier, and the data of various professions are organically integrated and all belong to the data of the well. It is of great significance for the later well data asset management and the integration and in-depth application of multi-professional data. It can comprehensively record various well data, improve the efficiency of well data management, and ensure the effective retention of data.

[0069] The above is only a preferred specific implementation of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by any person familiar with the technology within the technical scope disclosed by the present invention should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims. ​​​

[0070] In the description of the present invention, unless otherwise specified, "a plurality of" means two or more; the orientation or positional relationship indicated by terms such as "upper", "lower", "left", "right", "inner", "outer", "front end", "rear end", "head", "tail", etc. is based on the orientation or positional relationship shown in the drawings, and is only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be construed as a limitation to the present invention. In addition, terms such as "first", "second", "third", etc. are only used for descriptive purposes and cannot be construed as indicating or implying relative importance.

[0071] In the description of the present invention, it should be noted that, unless otherwise clearly specified and defined, the terms "connected" and "coupled" should be understood in a broad sense. For example, it may be a fixed connection, a detachable connection, or an integral connection; it may be a mechanical connection or an electrical connection; it may be directly connected or indirectly connected through an intermediate medium. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0072] It should be understood that the embodiments disclosed in the present invention are not limited to the specific structures, processing steps or materials disclosed herein, but should extend to equivalent alternatives of these features understood by those of ordinary skill in the relevant art. It should also be understood that the terms used herein are only for the purpose of describing specific embodiments and do not imply any limitation.

[0073] The "one embodiment" or "embodiment" mentioned in the specification means that the specific features, structures or characteristics described in connection with the embodiment are included in at least one embodiment of the present invention. Therefore, the phrases "one embodiment" or "embodiment" that appear throughout the specification do not necessarily all refer to the same embodiment.

[0074] Although the embodiments disclosed in the present invention are as above, the content described above is only an embodiment adopted for the convenience of understanding the present invention and is not used to limit the present invention. Any person skilled in the technical field to which the present invention pertains may make any modifications and changes in the form of implementation and details without departing from the spirit and scope disclosed by the present invention. However, the scope of patent protection of the present invention shall still be subject to the scope defined by the appended claims.

Claims

1. A method for managing well data, characterized in that include: Creating a three-level data model consisting of wells, wellbores subordinate to the wells, and operations subordinate to the wellbores; As well business activities progress, the three-level data modules are continuously updated according to the operational results of various business activities of wells in different locations to form a well data management database.

2. The method according to claim 1, characterized in that The process of creating the three-level data model includes: A model framework with wells, wellbores and operation activities as the main body is established, and each level of subject is defined by configuring a corresponding basic information table for each level of subject, wherein the primary key of the well basic information table is configured with a well identifier with a globally unique representation property; Configure additional information tables for entities at each level.

3. The method according to claim 2, characterized in that The well basic information table includes at least: the well identification, well number and well characteristic information, and the well characteristic information includes but is not limited to: well type, well type, well category, wellhead coordinates, structural unit, oil and gas field and geographical location basic information; The wellbore basic information table includes at least: wellbore identification, wellbore name, wellbore number and parent wellbore identification; The basic information table of the operation activity includes at least: the operation identification, the wellbore identification, the operation classification type, the operation name and the operation organization information table, wherein the information recorded in the operation organization information table includes but is not limited to: the operation unit, the operation personnel, the instrument information and the start and end time of the operation.

4. The method according to claim 3, characterized in that The well additional information table includes at least: well location measurement data table and well location design data table; The wellbore additional information table shall at least include: stratigraphic stratification table and completion data table; The additional information table of operation activities at least includes: the operation results data table of each operation activity at each operation, and the various operation activities include but are not limited to conventional logging operations, gas logging operations, core logging operations, analytical and testing operations, while drilling logging operations, while drilling measurement operations, directional operations, geological guidance operations and various types of logging operations.

5. The method according to claim 3 or 4, characterized in that: The additional data table at each well level contains a well identification field; Each additional data table at the wellbore level contains a wellbore identification field associated with the well to which it belongs; The additional data table for each activity level contains an activity identification field associated with the wellbore to which it belongs.

6. The method according to any one of claims 3 to 5, characterized in that: The well identifier, the borehole identifier and the operation activity identifier are defined using a GUID type, wherein the corresponding identifier is generated by taking an identifier number on a network card and a processor clock number.

7. The method according to any one of claims 2 to 6, characterized in that: In the process of creating a new job activity, include: According to the well number of the well to which the current operation activity to be created belongs, searching for the corresponding well from the well data management database; Under the well and wellbore to which the wellbore to be created currently belongs, the basic information table of the operation activity of the current new operation is automatically generated and entered, thereby creating a new operation. Then, the additional information table of the current new operation is configured according to the needs, where: If the well to which the current wellbore to be created belongs is not found, a new well will be created.

8. The method according to claim 7, characterized in that The process of creating a new well includes: automatically generating a well basic information table and entering the information, wherein a well identifier having a globally unique property is automatically generated while the well number is entered.

9. The method according to claim 8, characterized in that The process of building a new wellbore includes: According to the well number of the well to which the wellbore to be created belongs, searching for the corresponding well from the well data management database; Under the well to which the well to be created currently belongs, the well basic information table of the current new well is automatically generated and entered, thereby creating a new well. Then, the additional information table of the current new well is configured according to the requirements, where: If the well to which the current wellbore to be created belongs is not found, a new well will be created.

10. A system for managing well data, characterized in that: The system is used to implement the method according to any one of claims 1 to 9, wherein the method comprises: A three-level data model creation model configured to create a three-level data model consisting of a well, a wellbore subordinate to the well, and an operation activity subordinate to the wellbore; The database forming module is configured to continuously update the three-level data module according to the operation results of various business activities of wells in different locations along with the advancement of well business activities to form a well data management database.

Images