Intelligent logging construction method and system based on data center mode
Through the smart well recording construction method using the data middle platform model in oil exploration, the shortcomings of traditional data tool platforms have been solved, data integration and standardization have been realized, data utilization and business synergy have been improved, and well recording business has been supported. efficient decision making and scaling.
Patent Information
- Application Number
- CN202411185236.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-27
- Publication Date
- 2024-12-06
AI Technical Summary
In traditional oil exploration, there is a lack of data tool platforms, dispersed data, inconsistent structure, and weak analysis capabilities, resulting in the inability to exert data value and it is difficult to achieve data sharing and cross-system correlation.
Adopt a smart well recording construction method based on the data middle platform model, and collect basic data, analyze data relationships, establish data standards, and build business projects on the middle platform system to realize data integration and standardization, break data silos, and support business decision-making .
It realizes data integration and standardization, improves data usage and business synergy, reduces duplicate development, enhances the decision-making ability and insight of the well recording business, and supports vertical and horizontal scaling.
Smart Images

Figure CN119088786A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of petroleum exploration, and in particular relates to a smart logging construction method and system based on a data middle platform model. Background Art
[0002] The oil industry is in a critical period of transformation and upgrading. Accelerating digital transformation and promoting high-quality development of the industry are important tasks at present. However, digital transformation of traditional industries is easier said than done. There is an urgent need to sort out the needs of digital transformation and fill the gap between traditional business scenarios and digital technology applications. The problems that cause the gap are multifaceted, mainly from two aspects: one is the standardization and coordination of business processes, and the other is the standardization and integration of underlying data.
[0003] In traditional business, data is a byproduct. Business personnel conduct business based on industry experience and existing processes. Data is mainly used to monitor business progress and gain insights into certain patterns, and business personnel make final decisions. In traditional business scenarios, a series of problems are reflected, including a lack of data tool platforms, decentralized data construction, inconsistent data structures and standards, weak data analysis capabilities, inability to realize data value, data silos, and difficulties in pulling data together.
[0004] The existing technology collects offline single-well logging data and manually adds it to the logging interpretation software to form an access database for data processing, logging interpretation analysis, etc. However, there are problems such as the inability to automatically access data and the need to manually create and add data; there is no account role and permission control system, and data and results cannot be shared conveniently.
[0005] The existing technology also connects the existing logging historical data, logging real-time data, drilling data, interpretation results data, etc. to an integrated platform to conduct real-time monitoring of well information, data query, data statistics, data download, etc. However, there are problems such as incomplete data categories and lack of automated data cleaning and processing processes. Summary of the invention
[0006] In view of the above problems, the present invention discloses a smart logging construction method based on a data middle station model, comprising:
[0007] Collect basic data of target wells;
[0008] Analyze the data relationship between basic data and build a data relationship model;
[0009] Abstract the basic data, then extract and remove duplicates;
[0010] Based on the basic data after deduplication, establish data standards and obtain standard data;
[0011] Build business engineering on the middle office system based on standard data.
[0012] Furthermore, the basic data includes basic well information, well logging data, well logging data, oil testing data and analytical test data.
[0013] Furthermore, the specific steps of analyzing the data relationship between the basic data and constructing the data relationship model are as follows:
[0014] Analyze the basic data and identify the data relationship types between the basic data;
[0015] According to the actual needs of mud logging business, sort out the business logic relationship between various basic data;
[0016] Verify the consistency and accuracy of the same basic data in different data sources through data matching technology;
[0017] Use logical judgment statements or algorithms to verify whether the logical relationship between basic data conforms to business logic;
[0018] Conduct integrity checks on basic data;
[0019] Design the database entity relationship diagram, i.e. the data relationship model, based on the verified data relationship;
[0020] Map the data relationships in the entity relationship diagram to the actual database structure, and define the database objects of primary keys, foreign keys, and indexes;
[0021] Optimize and adjust the entity relationship diagram according to business needs and data characteristics;
[0022] Verify the constructed data relationship model to ensure that the data relationship model reflects the data relationship in the actual business;
[0023] Test the data relationship model in a test environment to check the accuracy and stability of the data relationship.
[0024] Furthermore, the specific steps of establishing the data standard are as follows:
[0025] Analyze the needs of mud logging services and clarify the goals of data standard formulation;
[0026] According to the logging business requirements, the required data elements are defined, and the data elements are classified according to business logic and data characteristics to form different data categories;
[0027] Formulate data standards and specifications; data standards and specifications include naming specifications, coding specifications, format specifications and quality specifications;
[0028] Establish a data standard management mechanism;
[0029] Data standards promotion and training;
[0030] Establish a supervision mechanism for the implementation of data standards and regularly evaluate the implementation of data standards.
[0031] Furthermore, the specific construction steps of the middle platform system are as follows:
[0032] Clarify the business scenarios, functional requirements, and non-functional requirements that the middle office system needs to support;
[0033] Design the overall architecture of the middle office system based on the results of demand analysis;
[0034] Design according to the overall architecture and build the servers, networks and storage of the middle office system;
[0035] Conduct integration testing on each module of the middle office system to verify whether the collaboration and interaction between modules are normal;
[0036] After the middle office system passes the test, it will be deployed to the production environment, and the production environment will be monitored and managed;
[0037] Improve the middle office system according to business development and user needs.
[0038] Furthermore, the specific steps of building a business project on the middle platform system based on standard data are as follows:
[0039] Identify the business requirements that business engineering needs to support;
[0040] Design business processes, data structures and business rules based on business needs analysis results;
[0041] Build business engineering on the middle office system through coding development, interface docking and data migration;
[0042] Conduct functional testing, performance testing, and security testing on business projects to ensure the correctness of business logic and the stability of the middle office system;
[0043] After the business project passes the test, it is deployed to the production environment, and the production environment is monitored and managed.
[0044] The present invention also discloses a smart logging construction system based on a data middle platform mode, including:
[0045] A collection unit, used to collect basic data of the target well;
[0046] An analysis unit, used to analyze the data relationship between basic data and build a data relationship model;
[0047] The processing unit is used to abstract the basic data and then extract and remove duplicates;
[0048] The data standard unit is used to establish data standards based on the basic data after deduplication to obtain standard data;
[0049] The business engineering unit is used to build business engineering on the middle office system based on standard data.
[0050] Furthermore, the analysis unit is specifically used for:
[0051] Analyze the basic data and identify the data relationship types between the basic data;
[0052] According to the actual needs of mud logging business, sort out the business logic relationship between various basic data;
[0053] Verify the consistency and accuracy of the same basic data in different data sources through data matching technology;
[0054] Use logical judgment statements or algorithms to verify whether the logical relationship between basic data conforms to business logic;
[0055] Conduct integrity checks on basic data;
[0056] Design the database entity relationship diagram, i.e. the data relationship model, based on the verified data relationship;
[0057] Map the data relationships in the entity relationship diagram to the actual database structure, and define the database objects of primary keys, foreign keys, and indexes;
[0058] Optimize and adjust the entity relationship diagram according to business needs and data characteristics;
[0059] Verify the constructed data relationship model to ensure that the data relationship model reflects the data relationship in the actual business;
[0060] Test the data relationship model in a test environment to check the accuracy and stability of the data relationship.
[0061] Furthermore, the data standard unit is specifically used for:
[0062] Analyze the needs of mud logging services and clarify the goals of data standard formulation;
[0063] According to the logging business requirements, the required data elements are defined, and the data elements are classified according to business logic and data characteristics to form different data categories;
[0064] Formulate data standards and specifications; data standards and specifications include naming specifications, coding specifications, format specifications and quality specifications;
[0065] Establish a data standard management mechanism;
[0066] Data standards promotion and training;
[0067] Establish a supervision mechanism for the implementation of data standards and regularly evaluate the implementation of data standards.
[0068] Furthermore, the business engineering unit is specifically used for:
[0069] Clarify the business scenarios, functional requirements, and non-functional requirements that the middle office system needs to support;
[0070] Design the overall architecture of the middle office system based on the results of demand analysis;
[0071] Design according to the overall structure and build the server, network and storage of the middle office system;
[0072] Conduct integration testing on each module of the middle office system to verify whether the collaboration and interaction between modules are normal;
[0073] After the middle office system passes the test, it will be deployed to the production environment, and the production environment will be monitored and managed;
[0074] Improve the middle office system according to business development and user needs.
[0075] Compared with the prior art, the embodiments of the present invention have at least the following advantages: based on the advantages of the data middle platform, the data and business of logging are integrated, and innovations are made in data usage and business convergence, achieving an integrated connection of data first and business standardization; it is used to decouple the business in a data-based manner, and restrict the business based on data standards and usage specifications, so that the business of logging at all levels can enter this process by transforming the information system or adding interfaces. The human, financial and material resources invested will be significantly reduced compared to repeated development, increasing the possibility of subsequent vertical or horizontal expansion.
[0076] 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 implementing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures pointed out in the description and the drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0077] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0078] Figure 1 A flow chart of a smart logging construction method based on a data middle platform mode according to an embodiment of the present invention is shown;
[0079] Figure 2 A schematic diagram of a business project according to an embodiment of the present invention is shown;
[0080] Figure 3 A schematic diagram of an intelligent logging construction system based on a data middle platform model according to an embodiment of the present invention is shown. DETAILED DESCRIPTION
[0081] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0082] In the process of digital transformation, data has become a new means of production. It has become a consensus to mine the value of data and improve the management and decision-making level of organizations, which has promoted the entire industry into the era of data intelligence. In the era of data intelligence, the core is data. Based on the middle platform, enterprises have the ability to manage, govern and mine the value of all data and the entire life cycle of data, thereby driving business decisions.
[0083] The data middle platform is a platform for data governance, connection and sharing. Its advantage lies in the controllable business based on data. There are many logging data and complex business, which requires the data middle platform to complete the data integration and break the individual independent business system. There is a lot of logging data, the growth rate is fast, the business is independent and changes quickly, so data needs to have stronger decision-making capabilities, insight discovery and process optimization. Based on the massive, diverse, timely, homogeneous and heterogeneous data, it is necessary to cross-domain association to form a scientific paradigm and established conceptual form. Afterwards, based on the data architecture business, it is suitable for combination innovation and micro-innovation to achieve the purpose of information management.
[0084] Figure 1 The flowchart of the intelligent logging construction method based on the data middle platform mode according to an embodiment of the present invention is shown. Figure 1 As shown, the present invention proposes a smart logging construction method based on a data middle station mode, comprising the following steps:
[0085] Step 1: Collect the basic information of the target well, including the unit, well number, well depth, construction unit, logging unit, core filling height, drilling date, drilling completion date, completion date, etc.
[0086] Step 2: Collect logging data of the target well. The core of logging data is "a logging map", which is a vector map that records the business attributes of logging, such as QL (total hydrocarbon content), C1 (methane), C2 (ethane), C3 (propane), NC4 (n-butane), IC4 (isobutane), NC5 (n-pentane), IC5 (isopentane), H2, H2S, CO2, etc.
[0087] Among them, "Mud Logging One Picture" is a vector diagram used to display key information and data in the mud logging business. This map not only contains the basic information of the well (such as well number, well depth, drilling date, etc.), but also integrates various data generated during the mud logging process, such as mud logging curves, formation information, lithology description, oil and gas display, etc. Its main functions are information integration, intuitive display, and decision-making assistance.
[0088] Step 3: Collect logging data of the target well. The logging data includes GR (natural gamma), SP (spontaneous potential), CAL (well diameter), AC (acoustic time difference), DEN (density), RT (true formation resistivity), RI (shallow resistivity), RXO (flushing zone resistivity), CNL (compensated neutron), etc.
[0089] Step 4: Collect the oil test data of the target well. The oil test data includes the layer position, top boundary depth, bottom boundary depth, daily oil production, daily gas production, daily water production, production increase measures, oil test results, etc.
[0090] Step 5: Collect analytical data of the target well. The analytical data include pyrolysis data, light hydrocarbon data, pyrolysis gas phase data, one-dimensional fluorescence, three-dimensional fluorescence, XRD (X-ray diffraction), XRF (X-ray fluorescence), nuclear magnetic resonance, etc.
[0091] Step 6: Collect other data of the target well, including image data, text data, table data, files, etc.
[0092] Step 7: Verify data relationship. Analyze the data relationship between step 1 and the basic data of steps 2 to 5, and build a data relationship model. The specific implementation process is as follows:
[0093] ① Preliminary analysis: First, conduct a preliminary analysis of the basic data collected in steps 1 to 6 to identify possible data relationship types, such as one-to-one, one-to-many, many-to-many, etc.
[0094] ② Business logic sorting: sort out the business logic relationship between basic data items according to the actual needs of the logging business. For example, there may be a direct correspondence between the basic well information and the logging data and well logging data.
[0095] ③ Data matching: Verify the consistency and accuracy of the same or similar basic data items in different data sources through data matching technology. For example, compare whether the well number in the basic information of the well is consistent with the well number in the logging data.
[0096] ④Logical relationship verification: Use logical judgment statements or algorithms to verify whether the logical relationship between basic data items conforms to business logic. For example, verify whether the logging data matches the business attributes in the "logging map".
[0097] ⑤ Data integrity check: Ensure that all required basic data items have been collected without omission or missing. For key basic data items, integrity checks are also required to ensure the integrity and availability of basic data.
[0098] ⑥ER diagram design: Based on the verified data relationship, design the database entity relationship (ER) diagram, that is, the data relationship model. In the ER diagram, entities represent data objects (such as basic well information, logging data, etc.), and relationships represent the connections between entities (such as one-to-one, one-to-many, etc.).
[0099] ⑦ Relationship mapping: Map the data relationship in the ER diagram to the actual database structure, define database objects such as primary keys, foreign keys, indexes, etc. to ensure the accuracy and stability of data relationships.
[0100] ⑧ Model optimization: According to business needs and data characteristics, optimize and adjust the ER diagram to improve data query efficiency, reduce data redundancy, etc. Data characteristics refer to the specific nature, characteristics or attributes of data, such as data scale, data update frequency, data redundancy, data integrity, data relevance, data life cycle, etc.
[0101] ⑨Model verification: Verify the constructed data relationship model to ensure that the data relationship model can accurately reflect the data relationship in the actual business. This can be done by simulating business scenarios, generating test data, etc.
[0102] ⑩Model testing: Test the data relationship model in the test environment to check the accuracy and stability of the data relationship. Make timely adjustments and optimizations for any problems found.
[0103] Through the above steps, it can be ensured that reasonable and accurate relationships can be established between various basic data collected in the construction of smart logging, providing strong support for subsequent data processing, business mapping and decision support.
[0104] Among them, the specific steps for optimizing and adjusting the ER diagram are as follows:
[0105] ①Identify redundant relationships:
[0106] Carefully examine the entities and relationships in the ER diagram to find out if there are any redundant relationships. For example, if there are multiple identical or similar relationships between two entities, you may need to merge or eliminate these redundant relationships.
[0107] ②Analyze entity attributes:
[0108] Evaluate the attributes of each entity to determine if all attributes are necessary and if there are any duplicates or attributes that can be merged. Eliminate unnecessary attributes to reduce data redundancy and storage space.
[0109] ③ Standardization:
[0110] Apply database normalization theory to decompose the ER diagram into higher normalization levels to reduce data redundancy and update anomalies. Common normalization levels include the first normal form (1NF), the second normal form (2NF), the third normal form (3NF) and higher normal forms.
[0111] ④Merge or split entities:
[0112] If two or more entities are very close or closely related logically, consider merging them into one entity. On the contrary, if an entity contains too many attributes or relationships, resulting in excessive complexity, consider splitting it into multiple smaller entities.
[0113] ⑤Optimize relationships:
[0114] Evaluate the relationship types between entities (one-to-one, one-to-many, many-to-many, etc.) and determine if adjustments are needed to better reflect the business logic. If there are unnecessary many-to-many relationships, consider converting them to two one-to-many relationships by introducing new entities.
[0115] ⑥ Index and primary key optimization:
[0116] Determine which properties should be set as primary keys to ensure entity uniqueness. Identify which properties should be indexed to improve query performance.
[0117] ⑦ Consider inheritance relationship:
[0118] If there are inheritance relationships between entities (such as specialization and generalization), consider using specialization / generalization structures in ER diagrams to represent these relationships.
[0119] ⑧Data integrity constraints:
[0120] Identify and define data integrity constraints, such as uniqueness constraints, referential integrity constraints, etc., to ensure data accuracy and consistency.
[0121] ⑨Performance considerations:
[0122] Evaluate the performance impact of ER diagram design, including query performance, insert / update / delete performance, etc. Optimize ER diagrams to improve performance based on business requirements and data access patterns.
[0123] ⑩Feedback and iteration:
[0124] Communicate with business users, database administrators, and other stakeholders to collect their feedback and suggestions. Iterate and optimize based on the feedback until the ER diagram meets business needs and achieves the best design effect.
[0125] Step 8: Sort out the credibility of basic data. Abstract and extract the basic data, remove duplication, and construct data with high feasibility. This is a management behavior of data use, which includes organization, system, and process. This management behavior is reflected in determining the target data, determining the data source, the mapping relationship between source data and target data, data extraction rules, data cleaning and conversion rules, and table building plans. This management behavior enables the subsequent addition of the data middle platform to evaluate and measure the integrity, timeliness, and authenticity of the data, so that the data can generate value, avoid the entry and output of junk data, and finally form a data mart.
[0126] The specific steps of abstract processing are as follows:
[0127] ①Data understanding
[0128] First, we need to have an in-depth understanding of the basic data collected, including the source, type, structure, format, content, etc. Understanding the data is the premise of abstract processing. Only when we have a clear understanding of the data can we conduct effective abstraction.
[0129] ② Identify commonalities
[0130] On the basis of understanding the data, it is necessary to identify the commonalities in the data. These commonalities may be a field, an attribute, a pattern, etc. The purpose of identifying commonalities is to classify data with similar characteristics and prepare for subsequent abstract processing.
[0131] ③Define the abstraction layer
[0132] Based on the identified commonalities, different abstraction layers can be defined. The abstraction layer is a summary and refinement of the original data, and each abstraction layer represents a degree of abstraction of the data. For example, fields such as date and time can be abstracted into timestamps, and fields such as user ID and user name can be abstracted into user IDs, etc.
[0133] ④Data Mapping
[0134] After defining the abstraction layer, you need to map the original data to the corresponding abstraction layer. This process may require some conversion and formatting of the original data to ensure that the data can be correctly mapped to the abstraction layer.
[0135] ⑤Verify the abstract results
[0136] Finally, the abstraction results need to be verified. The purpose of verification is to ensure that the data after abstraction still maintains the integrity and accuracy of the original data. This can be achieved by comparing the original data with the abstracted data.
[0137] The steps for data extraction are as follows:
[0138] ①Determine extraction requirements
[0139] Before extracting data, you need to clarify the extraction requirements. This includes which fields and data need to be extracted, as well as the conditions for extracting data. Clarifying the extraction requirements is the prerequisite for ensuring the accuracy of the extraction process.
[0140] ②Write extraction rules
[0141] Based on the extraction requirements, corresponding extraction rules can be written. The extraction rules can be SQL (Structured Query Language) query statements, regular expressions, etc., which are used to extract data that meets the requirements from the original data.
[0142] ③Execute extraction operation
[0143] After writing the extraction rules, you can perform the extraction operation. This process is usually implemented by writing a script or program, which will extract the data that meets the requirements from the original data according to the extraction rules.
[0144] ④Verify the extraction results
[0145] After the extraction operation is completed, the extraction results need to be verified. The purpose of verification is to ensure that the extracted data meets the extraction requirements and there are no omissions or errors. This can be achieved by comparing the extraction results with the original data.
[0146] Step 9: Establish data standard data. Establish data standards for the basic data after deduplication in step 8 to obtain standard data. The data used in the data standard must meet the minimum external range that can support the logging background and business. In the process of establishing data standards, considering reusability and scalability, it is best to define new standards based on national standards. If there is no suitable national standard, consider local standards. The specific process is as follows:
[0147] ① Clarify the data standard objectives: First, conduct an in-depth analysis of the needs of the logging business and clarify the role and importance of data in the business. Based on business needs, clarify the goals of data standard formulation, such as improving data quality, promoting data sharing, and supporting business decisions.
[0148] ② Develop a data standard framework: Define the required data elements according to the logging business needs, including the data name, definition, data type, value range, etc. Classify the data elements according to business logic and data characteristics to form different data categories, such as basic well information, logging data, logging data, etc. Set the level of data standards according to the importance and frequency of use of the data, such as core data standards, auxiliary data standards, etc.
[0149] ③ Formulate data standard specifications: a. Naming specifications: Formulate naming specifications for data elements to ensure the consistency and readability of data names. b. Coding specifications: For data elements that need to be coded, formulate unified coding specifications, such as using national standards, industry standards or custom coding rules. c. Format specifications: Formulate data format specifications, including format requirements for date, time, number, text, etc. d. Quality specifications: Formulate data quality specifications to clarify requirements for data accuracy, completeness, consistency, timeliness, etc.
[0150] ④ Establish a data standard management mechanism: a. Standard review: Establish a data standard review mechanism and invite relevant business departments and experts to review and provide feedback on the formulated data standards. b. Standard release: After review and modification, the data standards are officially released and notified to relevant departments and personnel. c. Standard implementation: Require all departments and personnel to operate and implement in accordance with the released data standards to ensure data consistency and accuracy. d. Standard maintenance: Establish a data standard maintenance mechanism to regularly update and maintain data standards to adapt to business development and changes.
[0151] ⑤ Promotion and training: Popularize the importance and usage of data standards to employees through internal publicity and training. Provide necessary training and support to help employees understand and master the specific requirements and operation methods of data standards.
[0152] ⑥ Supervision and evaluation: Establish a supervision mechanism for the implementation of data standards to ensure that all departments and personnel operate and implement in accordance with data standards. Regularly evaluate the implementation of data standards, collect feedback and suggestions, and make timely adjustments and optimizations.
[0153] Step 10: Build a middle office system and build business engineering on the middle office system based on standard data. Figure 2As shown in the figure, the business engineering uses the standard data sorted out in steps 1 to 9. These standard data construct the data mart and provide it to the business engineering for calling through the API interface. Business engineering includes business integration content and integration methods. Business integration content includes existing business systems and self-built systems. Existing business system integration includes data integration, page integration and application association. Self-built system integration includes system reconstruction, key data integration and business function integration. The integration method includes two parts, namely business association demand integration and information display integration. Among them, business association demand integration includes the above-mentioned system association processing, business strong association integration, IoT equipment information integration, function reuse processing and new demand horizontal upgrade suggestions. Information display integration includes unified portal display integration, comprehensive display integration, statistical report integration management, application platform integration and data information archiving integration management.
[0154] The specific construction process of the middle platform system is as follows:
[0155] ① Requirements analysis and planning: Communicate in depth with the business department to clarify the business scenarios, functional requirements, and non-functional requirements (such as performance, security, stability, etc.) that the middle office system needs to support. Develop a detailed project plan and schedule to ensure that the project is completed on schedule. Among them, functional requirements refer to the various functions or service capabilities that the middle office system needs to achieve. Such as: basic data management, business process management, service interface management, authority and security management, etc.
[0156] ②Architecture design: Based on the results of demand analysis, design the overall architecture of the middle platform system, including technology selection, system module division, interface design, etc. Consider the scalability, maintainability and reusability of the middle platform system to ensure the rationality of the architecture design.
[0157] ③ System implementation: According to the overall architecture design, the basic environment of the middle platform system is built, including the configuration of resources such as servers, networks, and storage. Coding development is carried out to realize the functions of each module of the middle platform system. During the development process, coding specifications and testing specifications are followed to ensure code quality and system stability.
[0158] ④ Integration test: Carry out integration test on each module of the middle office system to verify whether the collaboration and interaction between modules are normal. Carry out performance test and security test on the middle office system to ensure that the middle office system meets business requirements and non-functional requirements.
[0159] ⑤ Deployment and launch: After the test environment passes the test, the middle platform system is deployed to the production environment. Monitor and manage the production environment to ensure the stability and availability of the middle platform system.
[0160] ⑥Continuous optimization: Continuously optimize and upgrade the middle office system according to business development and changes in user needs. Collect user feedback and opinions, fix problems and improve functions in a timely manner.
[0161] The specific construction process of business engineering based on the middle platform system is as follows:
[0162] ① Business demand analysis: deeply understand the actual needs of the business department, clarify the business scenarios and functional requirements that the business engineering needs to support, etc. Fully understand the middle office system to ensure that the business needs match the capabilities of the middle office system.
[0163] ② Business model design: Based on the results of business demand analysis, design the business model, including business processes, data structures, business rules, etc. The scalability and flexibility of the business model should be considered to cope with future business changes.
[0164] ③ System implementation: Based on the middle office system, the functions of business engineering are realized. This includes coding development, interface docking, data migration and other work. During the development process, the coding specifications and testing specifications of the middle office system are followed to ensure seamless integration of business engineering and the middle office system.
[0165] ④Test verification: Conduct functional testing, performance testing, security testing, etc. on business engineering to ensure the correctness of business logic and the stability of the middle office system. Verify the integration effect of business engineering and the middle office system together with the middle office system.
[0166] ⑤ Deployment and launch: After the test environment passes the test, the business project is deployed to the production environment. The production environment is monitored and managed to ensure the stability and availability of the business project.
[0167] ⑥ User training and support: Provide business engineering training to business departments to ensure that users can master the usage and operation procedures of the middle office system. Provide technical support and maintenance services for the middle office system to promptly resolve problems encountered by users during use.
[0168] A smart logging construction method based on the data middle platform model. The process emphasizes data and integrates business. The data mainly includes basic well information, logging data, logging data, oil test data, analytical test data, image data, and other structured and unstructured data. After processing the basic data, standards and specifications are formed, and then the standard data is used to map the business and the core business data for inversion business and computing efficiency. Finally, the logging interpretation is scientific and rational, and it is scalable.
[0169] The intelligent logging construction method based on the data middle platform mode of the present invention has the following advantages:
[0170] Break through the limitations of the data fortress. In logging operations, different companies use different instrument manufacturers and equipment models, resulting in different data collection and processing interpretation specifications. The non-standardized data collection, processing and storage make the data of each unit independent and irrelevant, making it difficult to achieve unified and centralized management, and it is impossible to effectively develop the comprehensive application of data. A large amount of available information contained in the data has not been discovered. In addition, multiple independent business systems have been generated in various links of oil exploration and development, such as drilling business systems, logging business systems, analysis and testing business systems, etc. The data of each business system cannot be interoperable, forming data islands, making data standards inconsistent, unable to associate data across systems, unable to uniformly manage data, inconvenient to use, and difficult to mine data value. After investigating the actual situation of each business category, extract the data required by the business entity, which can fully reflect a certain business. These data are formed into data standards or data specifications to meet the needs of data exchange, reporting, and distribution, so as to achieve unified and intelligent management of logging. The data middle platform is a product of the IT industry. It is suitable for business liberation of data, while abstracting business capabilities and sinking them into data, feeding back the business with standardized data sets, and providing data and business to the outside in a unified manner. For oil logging, a relatively traditional industry, the middle platform concept essentially builds a data sharing mechanism and service asset library for logging, effectively supporting the homogenization of logging services at different levels. Secondly, logging business is not an innovative business. Its technological evolution is relatively slow, and its business processes are similar, with high abstract completeness. On this basis, the middle platform concept integrates the scattered, messy, repeated, and non-uniform data in logging, turning the data from a messy presentation into an asset for decision-making, breaking the data fortress.
[0171] Break through the constraints brought by business experience. Different new and old logging workers have different experiences. For example, when judging the value layer and the non-value layer, experienced people only need to simply look at the single well curve chart to judge a relatively accurate result. If the experience is insufficient, artificial intelligence or expert systems will be used, or even field work will be done directly. Based on this invention, the business is reflected by data, and the data is defined in dimensions. The business of logging can achieve experience integration, and the experience will be upgraded after expansion. The logging business is relatively traditional, and its main function is to provide data support for the logging interpretation business. On the data middle platform that connects data and business, the quality of data can be higher, and higher requirements can be put forward for data quality when combing data, so that it is more accurate in the macro and more precise in the micro. In addition, data quality will be exposed when combing and integrating data, and the root cause is in the source business. Control data quality and continuously conduct quality verification and monitoring. In the early stage of data integration, due to different business experiences, the data may differ too much or be inaccurate. After attribution analysis of the problem, promoting business collaboration and sharing to form a business closed loop is a means to solve data quality and business differences. Guided by the middle platform thinking, a data quality control system covering the three stages before, during and after the business is established. Through data quality management, the integrated connection from data to business is promoted, breaking the independence of each logging business experience and processing method.
[0172] Achieve scientific results. The logging business is not a step-by-step assembly line. Many factors will affect the logging business, such as instruments and equipment, block location, drilling depth, etc. In this invention, the data in the data first is not only the background data of logging, but also includes the data of the three stages before, during and after the business and other data, such as drilling, logging, logging, oil testing, analysis and testing data. With the mutual assistance of various types of data, experience optimization and evaluation fairness can be achieved, and the results can be scientifically credible in the end. In the logging business, there are many business systems, such as remote logging integration system, logging analysis and testing data standardization management and application system, reservoir evaluation system, etc. However, the logging business management department cannot timely and effectively understand the overall business operation of the entire drilling process, and cannot make scientific evaluations based on various reports. Temporarily, the data is "qualified" based on various reporting documents or reports. The essence is the lack of a unified business operation caliber and technical indicators, and there is cross-repetition of management information. The units are not flexible enough in reporting the operation and management of the superior department, and the collection of subordinate units is not timely and accurate. Under the coordination of the middle platform thinking, the scientific nature of any result lies in mining the essence behind the data. The description of the result by the data must be the result of data output. In the middle platform, the mining of business results or problems of a certain dimension is divided into three steps. The first step is the individual; the second step is to capture individual characteristics; the third step is to supplement individual data, so as to characterize the problem of uncertainty as a problem of accuracy. Combining indicators, dimensions, and calibers, the data middle platform outputs data that can assist users in making decisions, and the results obtained are scientific.
[0173] like Figure 3 As shown, based on the above-mentioned smart logging construction method based on the data middle station mode, this embodiment proposes a smart logging construction system based on the data middle station mode, including:
[0174] A collection unit, used to collect basic data of the target well;
[0175] An analysis unit, used to analyze the data relationship between basic data and build a data relationship model;
[0176] The processing unit is used to abstract the basic data and then extract and remove duplicates;
[0177] The data standard unit is used to establish data standards based on the basic data after deduplication to obtain standard data;
[0178] The business engineering unit is used to build business engineering on the middle office system based on standard data.
[0179] In some embodiments, the analysis unit is specifically used to:
[0180] Analyze the basic data and identify the data relationship types between the basic data;
[0181] According to the actual needs of mud logging business, sort out the business logic relationship between various basic data;
[0182] Verify the consistency and accuracy of the same basic data in different data sources through data matching technology;
[0183] Use logical judgment statements or algorithms to verify whether the logical relationship between basic data conforms to business logic;
[0184] Conduct integrity checks on basic data;
[0185] Design the database entity relationship diagram, i.e. the data relationship model, based on the verified data relationship;
[0186] Map the data relationships in the entity relationship diagram to the actual database structure, and define the database objects of primary keys, foreign keys, and indexes;
[0187] Optimize and adjust the entity relationship diagram according to business needs and data characteristics;
[0188] Verify the constructed data relationship model to ensure that the data relationship model reflects the data relationship in the actual business;
[0189] Test the data relationship model in a test environment to check the accuracy and stability of the data relationship.
[0190] In some embodiments, the data standard unit is specifically used to:
[0191] Analyze the needs of mud logging services and clarify the goals of data standard formulation;
[0192] According to the logging business requirements, the required data elements are defined, and the data elements are classified according to business logic and data characteristics to form different data categories;
[0193] Formulate data standards and specifications; data standards and specifications include naming specifications, coding specifications, format specifications and quality specifications;
[0194] Establish a data standard management mechanism;
[0195] Data standards promotion and training;
[0196] Establish a supervision mechanism for the implementation of data standards and regularly evaluate the implementation of data standards.
[0197] In some embodiments, the business engineering unit is specifically used to:
[0198] Clarify the business scenarios, functional requirements, and non-functional requirements that the middle office system needs to support;
[0199] Design the overall architecture of the middle office system based on the results of demand analysis;
[0200] Design according to the overall structure and build the server, network and storage of the middle office system;
[0201] Conduct integration testing on each module of the middle office system to verify whether the collaboration and interaction between modules are normal;
[0202] After the middle office system passes the test, it will be deployed to the production environment, and the production environment will be monitored and managed;
[0203] Improve the middle office system according to business development and user needs.
[0204] The present invention also discloses an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the above-mentioned intelligent logging construction method based on the data middle station model is implemented.
[0205] The present invention also discloses a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned intelligent logging construction method based on the data middle station model is implemented.
[0206] Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent substitutions for some of the technical features therein; and these modifications or substitutions do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A smart logging construction method based on a data middle platform model, characterized in that: include: Collect basic data of target wells; Analyze the data relationship between basic data and build a data relationship model; Abstract the basic data, then extract and remove duplicates; Based on the basic data after deduplication, establish data standards and obtain standard data; Build business engineering on the middle office system based on standard data.
2. According to claim 1, the intelligent logging construction method based on the data middle platform mode is characterized in that: The basic data include basic well information, well logging data, well logging data, oil testing data and analytical test data.
3. The intelligent logging construction method based on the data middle platform mode according to claim 1 is characterized in that: The specific steps of analyzing the data relationship between the basic data and building the data relationship model are as follows: Analyze the basic data and identify the data relationship types between the basic data; According to the actual needs of mud logging business, sort out the business logic relationship between various basic data; Verify the consistency and accuracy of the same basic data in different data sources through data matching technology; Use logical judgment statements or algorithms to verify whether the logical relationship between basic data conforms to business logic; Conduct integrity checks on basic data; Design the database entity relationship diagram, i.e. the data relationship model, based on the verified data relationship; Map the data relationships in the entity relationship diagram to the actual database structure, and define the database objects of primary keys, foreign keys, and indexes; Optimize and adjust the entity relationship diagram according to business needs and data characteristics; Verify the constructed data relationship model to ensure that the data relationship model reflects the data relationship in the actual business; Test the data relationship model in a test environment to check the accuracy and stability of the data relationship.
4. The intelligent logging construction method based on the data middle platform mode according to claim 1 is characterized in that: The specific steps of establishing data standards are as follows: Analyze the needs of mud logging services and clarify the goals of data standard formulation; According to the logging business requirements, the required data elements are defined, and the data elements are classified according to business logic and data characteristics to form different data categories; Formulate data standards and specifications; data standards and specifications include naming specifications, coding specifications, format specifications and quality specifications; Establish a data standard management mechanism; Data standards promotion and training; Establish a supervision mechanism for the implementation of data standards and regularly evaluate the implementation of data standards.
5. According to claim 1, the intelligent logging construction method based on the data middle platform mode is characterized in that: The specific construction steps of the middle platform system are as follows: Clarify the business scenarios, functional requirements, and non-functional requirements that the middle office system needs to support; Design the overall architecture of the middle office system based on the results of demand analysis; Design according to the overall architecture and build the servers, networks and storage of the middle office system; Conduct integration testing on each module of the middle office system to verify whether the collaboration and interaction between modules are normal; After the middle office system passes the test, it will be deployed to the production environment, and the production environment will be monitored and managed; Improve the middle office system according to business development and user needs.
6. The intelligent logging construction method based on the data middle platform mode according to claim 1 is characterized in that: The specific steps for building a business project on the middle platform system based on standard data are as follows: Identify the business requirements that business engineering needs to support; Design business processes, data structures and business rules based on business needs analysis results; Build business engineering on the middle office system through coding development, interface docking and data migration; Conduct functional testing, performance testing, and security testing on business projects to ensure the correctness of business logic and the stability of the middle office system; After the business project passes the test, it is deployed to the production environment, and the production environment is monitored and managed.
7. A smart logging construction system based on the data middle platform model, characterized in that: include: A collection unit, used to collect basic data of the target well; An analysis unit, used to analyze the data relationship between basic data and build a data relationship model; The processing unit is used to abstract the basic data and then extract and remove duplicates; The data standard unit is used to establish data standards based on the basic data after deduplication to obtain standard data; The business engineering unit is used to build business engineering on the middle office system based on standard data.
8. The intelligent logging construction system based on the data middle platform mode according to claim 7 is characterized in that: The analysis unit is specifically used for: Analyze the basic data and identify the data relationship types between the basic data; According to the actual needs of mud logging business, sort out the business logic relationship between various basic data; Verify the consistency and accuracy of the same basic data in different data sources through data matching technology; Use logical judgment statements or algorithms to verify whether the logical relationship between basic data conforms to business logic; Conduct integrity checks on basic data; Design the database entity relationship diagram, i.e. the data relationship model, based on the verified data relationship; Map the data relationships in the entity relationship diagram to the actual database structure, and define the database objects of primary keys, foreign keys, and indexes; Optimize and adjust the entity relationship diagram according to business needs and data characteristics; Verify the constructed data relationship model to ensure that the data relationship model reflects the data relationship in the actual business; Test the data relationship model in a test environment to check the accuracy and stability of the data relationship.
9. The intelligent logging construction system based on the data middle platform mode according to claim 7 is characterized in that: The data standard unit is specifically used for: Analyze the needs of mud logging services and clarify the goals of data standard formulation; According to the logging business requirements, the required data elements are defined, and the data elements are classified according to business logic and data characteristics to form different data categories; Formulate data standards and specifications; data standards and specifications include naming specifications, coding specifications, format specifications and quality specifications; Establish a data standard management mechanism; Data standards promotion and training; Establish a supervision mechanism for the implementation of data standards and regularly evaluate the implementation of data standards.
10. The intelligent logging construction system based on the data middle platform mode according to claim 7 is characterized in that: The business engineering unit is specifically used for: Clarify the business scenarios, functional requirements, and non-functional requirements that the middle office system needs to support; Design the overall architecture of the middle office system based on the results of demand analysis; Design according to the overall structure and build the server, network and storage of the middle office system; Conduct integration testing on each module of the middle office system to verify whether the collaboration and interaction between modules are normal; After the middle office system passes the test, it will be deployed to the production environment, and the production environment will be monitored and managed; Improve the middle office system according to business development and user needs.
Citation Information
Patent Citations
Data processing method based on big data
CN112231315A
Multi-body data space interoperation method for multi-source heterogeneous data
CN117931913A
Shaft geological logging big data analysis method and platform
CN118093683A
