Offshore oil-gas exploration and development data query method and tool
By building object-related links and full-professional asset directory trees, combining directory, business and topic query methods, the complexity and inefficiency of the offshore oil and gas exploration and development data query system are solved, and fast and accurate data query and extraction are achieved. , improves data utilization efficiency and accessibility.
Patent Information
- Application Number
- CN202410880278.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-02
- Publication Date
- 2024-11-08
AI Technical Summary
The existing offshore oil and gas exploration and development data query system has complex operations, low query efficiency and single dimensions, which cannot meet the combined query needs of multiple data resources and production objects, resulting in low information query efficiency.
Build object relationship links based on business logic, establish entity object relationships, build a full-professional asset directory tree, and develop data query tools through directory, business and topic query methods to achieve fast and accurate data query.
Improve the efficiency of data assets utilization, promote cross-departmental collaboration, enhance data-driven capabilities, provide an activated and organized knowledge base, meet the various data query needs of different business users, and improve data accessibility and utilization.
Smart Images

Figure CN118916401A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of offshore oil and gas development, and in particular to a method and tool for querying offshore oil and gas exploration and development data. Background Art
[0002] With the continuous development of enterprise informatization and the deepening of offshore oil and gas field exploration and development, a large amount of data resources have been generated and accumulated, including exploration, development, production, reserves, engineering construction, drilling and completion, etc. At present, all data are stored in the lake according to the data resource directory. Effective query and use in scientific research and daily work stages are of great significance and value to the exploration, development and production of offshore oil and gas fields. These data have become important assets of enterprises. The construction of large-scale comprehensive data aggregation platforms represented by data lakes has made great progress in data storage and data management. The large-scale aggregation of data has also made the effective use of data more and more important, and data query is one of them.
[0003] In the past, data queries were all conducted in a single business system with a single data scope, a single business object, and a small amount of data. For example, the integrated collaborative research platform for exploration and development, the intelligent exploration work platform, the reserve work platform, the development and production management platform, etc., had data queries scattered in various business systems. However, the current system and query tools have problems such as complex operation, low query efficiency, single query dimension, and lack of close fit with the business, and cannot meet the requirements of combined queries on multiple data resources and production objects at the same time. With the entry of all-professional and massive data into the lake, the data query service provided to users faces more complex processing logic. How to quickly and accurately query and extract information from a large amount of complex exploration and development data has become the focus and difficulty of the current information construction of the oil and gas industry. Summary of the invention
[0004] In view of the above problems, the purpose of the present invention is to provide a method, device and medium for querying offshore oil and gas exploration and development data, which can quickly and accurately query and extract information from a large amount of complex exploration and development data.
[0005] To achieve the above object, the present invention adopts the following technical solutions: In the first aspect, the present application is provided to solve the above-mentioned problems. The purpose of the present invention is to provide an offshore oil and gas exploration and development data query method and tool, which can quickly and accurately query and extract information from a large amount of complex exploration and development data. The specific technical solution is as follows: S1: Based on business logic, build object relationship links, fill in object entity data, and establish entity-object relationships; S2: Based on the exploration and development business standards, build a full-professional asset catalog tree and establish relationships with entity objects; S3: Build a subject catalog and data list based on business subject requirements; S4: Develop a set of data query tools. When a user clicks on a directory, business or subject query service, the query service is called to respond according to the defined query logic, and the corresponding data is obtained from the standard layer for display.
[0006] The beneficial effects of the present invention are as follows: by systematically organizing and constructing a data asset catalog with a clear structure, easy maintenance and effective support for exploration and development decisions according to three query methods: catalog, business and subject, and establishing an association relationship with business objects, it not only improves the utilization efficiency of data assets, but also promotes cross-departmental collaboration and enhances the data-driven capabilities of enterprises. The data asset catalog becomes an active and organized knowledge base, which not only facilitates the search and use of data, but also provides a solid foundation for data-driven decision-making. It can meet the needs of different business users and multiple data query methods to the greatest extent, and help improve the accessibility, traceability and utilization of data, thereby supporting more efficient decision-making.
[0007] The present invention adopts the above technical solution, which has the following advantages: 1. Comprehensiveness: By combining the full life cycle of objects with professional asset catalogs, users can quickly obtain full object data and data set data, providing a comprehensive perspective for data resource management and business personnel to better understand and grasp each link in the production process and its relationship with exploration assets.
[0008] 2. Flexibility: By defining topics, aggregating required data, and quickly querying required data packages, user query efficiency is greatly improved, helping users to conduct research faster and more conveniently.
[0009] 3. Richness: Combined queries allow users to filter, sort, and analyze data according to different needs, so as to obtain the data they need in specific situations, helping users better understand and analyze data.
[0010] 4. Efficiency: Users can obtain all the information they need in one query page, instead of querying production object relationships and exploration and development assets separately, which greatly saves query and analysis time.
[0011] 5. Utilization: Through combined queries, different disciplines or teams can have a clearer understanding of the data of other disciplines, promote cross-disciplinary collaboration, discover previously neglected or underutilized data, and improve overall data utilization. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1 It is a flow chart of the implementation of the present invention; Figure 2is a schematic diagram of the architecture of a tool provided by an embodiment of the present invention; Figure 3 is a schematic diagram of a service calling process in an embodiment of the present invention; Figure 4 is a flowchart of a directory query service in an embodiment of the present invention; Figure 5 is a business query business process diagram in an embodiment of the present invention; Figure 6 It is a flow chart of the subject query service in an embodiment of the present invention. DETAILED DESCRIPTION
[0013] In order to make the purpose, technical solution and advantages of the embodiment of the present invention clearer, the technical solution of the embodiment of the present invention will be clearly and completely described below in conjunction with the drawings of the embodiment of the present invention. Obviously, the described embodiment is a part of the embodiment of the present invention, not all of the embodiments. Based on the described embodiment of the present invention, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of the present invention.
[0014] The present invention will be described in detail below with reference to the accompanying drawings and embodiments. Figure 1 shown.
[0015] S1: Based on business logic, build the master data relationship link, fill in the object entity data, and establish the entity object relationship; S2: Based on the exploration and development business standards, build a full-professional asset catalog tree and establish relationships with entity objects; S3: Build a subject catalog and data list based on business subject requirements; S4: Develop a set of data query tools. When a user clicks on a directory, business or subject query service, the query service is called to respond according to the defined query logic, and the corresponding data is obtained from the standard layer for display.
[0016] Furthermore, the construction of the master data relationship link includes the following steps: S11: Create a master data model: Create a wide table logical model and edit basic entity information and attributes. Basic information includes: entity name, entity classification, entity code, physical table English name and entity description; attributes include: field name, type and length; fields include: various master data identifiers, names and relationships between master data in the wide table link; S12: Model approval: Submit the edited logical model for review. If the review fails, modify the basic information or attributes in the model and resubmit it after the modification is completed. If the review passes, the logical model needs to be projected (incremental projection) into the database. S13: Physical model projection: Project the created wide table logical model into the master data relational database and create the corresponding physical table. If the projection script is executed successfully, the master data wide table physical table is created successfully and can be verified in the database. If the projection fails, modify the logical model according to the failure prompt and re-execute the model approval and projection process. S14: Master data access: According to the structure of the master data wide table, write SQL scripts to access the master data relationship into the physical table of the relational database; S15: Build relationships between data objects, such as containment relationships, dependency relationships, etc. This helps understand how data flows in business processes.
[0017] S16: Entity data relationship check: Check the rationality of business logic and data integrity based on the master data entities that have been stored in the database.
[0018] Furthermore, the construction of the exploration and development data asset catalog and the establishment of the association relationship between the data set and the master data include the following steps: S21: Business process decomposition: It is necessary to deeply understand the business process of exploration and development and decompose the entire business chain into the smallest nodes. This may include geological research, seismic data acquisition and processing, drilling operations, production monitoring and other links.
[0019] S22: Data Source Identification: Identify and list all data sources generated or used by each business unit, including internally generated data such as drilling logs, geological models, etc.
[0020] S23: Data classification and subject domain determination: Data is classified into different subject domains according to its nature and purpose. Common subject domains may include geological information, geophysics, drilling engineering, production management, environmental impact, economic evaluation, etc. Each subject domain is further subdivided into subcategories to ensure the logic and searchability of the data.
[0021] S24: Asset catalog data set and master data association: Map the master data to the corresponding location in the catalog according to its business meaning and classification standards. This means associating each data object with a category or sub-category in the catalog to form a clear attribution relationship.
[0022] Furthermore, we build a subject catalog and data list, including: S31: Add a new subject directory: Configure the subject directory according to business needs, and manage subject types in different categories, such as exploration, reserves, drilling and completion, etc.
[0023] S32: Add new keywords: Configure keywords under the subject directory, which is similar to a work subject, such as reserve prediction, drilling design, etc. Keywords are closely related to business work.
[0024] S33: Add data list: Add related data sets under the keywords to associate keywords with data sets.
[0025] Furthermore, a set of data query tools based on the exploration and development asset catalogue will be designed and developed. Figure 2 , 3 As shown, the specific implementation scheme is: S41: Master data relationship service construction: This service is responsible for defining master data attributes and relationship structure, assembling entity data, and providing a set of master data relationship services.
[0026] { List <masterinfovo>list = new ArrayList<>(); / / Root query or full search String id = dto.getId(); if (CharSequenceUtil.isEmpty(id)) { throw new BizException("Full search is not supported without link id"); } / / Get well type parameters BotLineVO botLineVO = getBotLineVO(dto, id); String fetchBoName = dto.getFetchBoName(); if (CharSequenceUtil.isNotEmpty(fetchBoName)) { List <botcodevo>botCodeVOList = botLineVO.getBotCodeVOList(); / / Full - volume search PtLineDTO ptLineDTO = new PtLineDTO(); ptLineDTO.setId(id); String sourceBotIdCode = dto.getSourceBotIdCode(); if (CharSequenceUtil.isNotEmpty(sourceBotIdCode)) { ptLineDTO.setSourceBotIdCode(sourceBotIdCode); } else { ptLineDTO.setSourceBotIdCode(botCodeVOList.get(0).getIdCode()); } ptLineDTO.setSourceBoId(dto.getSourceBoId()); / / Remove branch node botCodeVOList.remove(0); ptLineDTO.setIsSearch(false); ptLineDTO.setFetchBoName(fetchBoName); ptLineDTO.setTableName(botLineVO.getTableName()); ptLineDTO.setTag(dto.getTag()); List<Map<String, String>>list1 = externalServer.queryMasterList(ptLineDTO, botCodeVOList); List <masterinfovo>masterInfoVOS = breakLineMasterList(list1,botCodeVOList); List <masterinfovo>masterInfoVOS1 = buildTreeBreakLine(masterInfoVOS); / / List <masterinfovo>masterInfoVOS = buildTreeByName(list1,botCodeVOList); / / List <masterinfovo>masterInfoVOS1 = buildTreeByNameOther(masterInfoVOS, botCodeVOList); / / / / Fuzzy search of broken link master data / / List <masterinfovo>masterInfoVOList = breakLineMasterCatch(dto); / / masterInfoVOS1.addAll(masterInfoVOList); / / Filter out data with empty id masterInfoVOS1 = masterInfoVOS1.stream().filter(masterInfoVO -> CharSequenceUtil.isNotEmpty(masterInfoVO.getId()) ).collect(Collectors.toList()); list = masterInfoVOS1; } else { / / Subordinate query if (config.isRedisCatchLazy()) { String sourceBoId = dto.getSourceBoId(); String fetchBotIdCode = dto.getFetchBotIdCode(); String key = CommonConstant.MASTER_LINK_LAZY_CACHE + id + ":" +sourceBoId + ":" + fetchBotIdCode; Boolean hasExit = redisListUtil.hasExit(key); if (hasExit) { list = (List <masterinfovo>) redisListUtil.get(key); } else { dto.setIsSearch(false); Page <masterinfovo>page = externalServer.queryMasterList(dto); list = page.getRecords(); / / Fuzzy search of broken link master data List <masterinfovo>masterInfoVOS = externalServer.breakLineMasterById(dto); list.addAll(masterInfoVOS); redisListUtil.set(key, list, 30L, TimeUnit.MINUTES); } } else { dto.setIsSearch(false); Page <masterinfovo>page = externalServer.queryMasterList(dto); list = page.getRecords(); / / Fuzzy search of broken link master data List <masterinfovo>masterInfoVOS = externalServer.breakLineMasterById(dto); list.addAll(masterInfoVOS); } } / / Only 1000 records are returned each time list = list.stream().skip(0l).limit(1000l).collect(Collectors.toList()); return list; } S42: Asset Directory Construction Service: This service is responsible for defining the data asset directory structure and returning entity data through the directory structure.
[0027] { List <string>userOrgId = userService.getUserOrgId(); log.debug("Asset catalog request user organization id: {}", JSONUtil.toJsonStr(userOrgId)); String cacheKey = CacheKeyConfig.RESOURCES_MENU_TREE_CACHE_KEY + ":"+ isAllTag + ":" + orgIdMD5(userOrgId); log.debug("hashCode:{}", cacheKey); if (config.isRedisCatch()&&redisListUtil.hasExit(cacheKey)) { long startTime = System.currentTimeMillis(); List <externalnodetreevo>nodeTrees = (List <externalnodetreevo>)redisListUtil.get(cacheKey); long endTime = System.currentTimeMillis(); } Boolean externalEnv = externalConfig.getExternalEnv(); String url = externalConfig.getTreeUrl(); log.debug("Asset catalog request address: {}", url); NodeTreeModel model = new NodeTreeModel(); / / If there is only one organization, pass the parameter. If there are multiple organizations, all organizations will be searched by default and no parameter will be passed.
[0028] if (CollUtil.isNotEmpty(userOrgId)&&userOrgId.size() == 1) { model.setFgsIdList(userOrgId); } String param = JSONUtil.toJsonStr(model); log.debug("Asset catalog request parameters: {}", param); String res = HttpUtil.postRequest(url, param, null); try { JSONObject jsonObject = JSONUtil.parseObj(res); Integer code = jsonObject.getInt("code"); if (200 == code) { JSONArray array = jsonObject.getJSONArray("data"); List <externalnodetreevo>nodeTrees = JSONUtil.toList(array, ExternalNodeTreeVO.class); nodeTrees = parseTree(nodeTrees, isAllTag); if (config.isRedisCatch() && CollUtil.isNotEmpty(nodeTrees)) { redisListUtil.set(cacheKey, nodeTrees, 1l, TimeUnit.DAYS); } return nodeTrees; } } catch (Exception e) { throw new BizException("http request result conversion failed: " + e.getMessage()); } return Collections.emptyList(); } public List <externalnodetreevo>parseTree(List <externalnodetreevo>nodeTrees, Integer count) { if (CollUtil.isNotEmpty(nodeTrees)) { if (count == 1) { nodeTrees = nodeTrees.stream().filter(nodeTree ->nodeTree.getCount()>0).collect(Collectors.toList()); } nodeTrees.forEach(nodeTree ->{ / / Tree node type conversion if (nodeTree.getMenuType() == 1) { / / log.info("Tree node type conversion: {}", nodeTree); nodeTree.setMenuType(2); } String format = nodeTree.getFormat(); if (CharSequenceUtil.isNotEmpty(format)) { switch (format) { case "Structured": nodeTree.setFormat("Structured data"); break; case "unstructured": nodeTree.setFormat("unstructured data"); break; default: nodeTree.setFormat(format); break; } } List <externalnodetreevo>treeList = nodeTree.getTreeList(); nodeTree.setTreeList(parseTree(treeList, count)); }); } return nodeTrees; } S43: Master data and asset catalog combined query service: Returns entity data by selecting master data and an asset catalog data set.
[0029] { Boolean externalEnv = externalConfig.getExternalEnv(); if (ObjectUtil.isNotEmpty(externalEnv)&&!externalEnv) { if (CharSequenceUtil.equals(dto.getUmd().get("pt") + "", "G0201010001002")) { MasterTestConstant masterTestConstant = new MasterTestConstant(); JSONObject jsonObject = masterTestConstant.getQueryJsonData(); return String.valueOf(jsonObject); } if (CharSequenceUtil.equals(dto.getUmd().get("pt") + "", "W0204010002003")) { MasterTestConstant masterTestConstant = new MasterTestConstant(); JSONObject jsonObject = masterTestConstant.getQueryJsonData2(); return String.valueOf(jsonObject); } } / / Get the dataset information List <string>sjjbhList = Lists.newArrayList(); / / ptCode, dataset number sjjbhList.add(dto.getUmd().get("pt") + ""); YwbzSjjDto ywbzSjjDto = new YwbzSjjDto(); ywbzSjjDto.setSjjbhList(sjjbhList); YwbzSjjDetailDTO ywbzSjjDetailDTO = new YwbzSjjDetailDTO(); ywbzSjjDetailDTO.setJsonObj(ywbzSjjDto); long startTimes = System.currentTimeMillis(); List <ywbzsjjdetailvo>ywbzSjjDetailVOList = getYwbzSjjDetailList(ywbzSjjDetailDTO); long endTimes = System.currentTimeMillis(); long resultTimes = endTimes - startTimes; log.info("Standard interface call time:{}", resultTimes); if (CollUtil.isEmpty(ywbzSjjDetailVOList)) { throw new BizException("Failed to obtain the business standard details interface"); } YwbzSjjDetailVO ywbzSjjDetailVO = ywbzSjjDetailVOList.get(0); List <ywbzsjxvo>ywbzSjxList = ywbzSjjDetailVO.getYwbzSjxList(); long startTimes2 = System.currentTimeMillis(); ZyxxDetailVO zyxxDetailVO = externalOtherServer.getStructProfessionHookInfo(dto.getUmd().get("pt") + ""); long endTimes2 = System.currentTimeMillis(); long resultTimes2 = endTimes2 - startTimes2; log.info("Dataset mapping relationship call time:{}", resultTimes2); if (ObjectUtil.isEmpty(zyxxDetailVO)) { throw new BizException("Data set mapping relationship not obtained"); } / / Get the partition name and table name String sjfqywm = zyxxDetailVO.getJghzyVO().getSjfqywm(); String sjbmc = zyxxDetailVO.getJghzyVO().getSjbmc(); List <externalmastermappingvo>zdysList = zyxxDetailVO.getJghzyVO().getZdysList(); ExternalAppData externalAppData = new ExternalAppData(); externalAppData.setPageNumber(dto.getCurrentPage()); externalAppData.setPageSize(dto.getPageSize()); externalAppData.setDatasetCode(ywbzSjjDetailVO.getSjjbh()); externalAppData.setColumns(dto.getResultFields()); / / Directory<String, String> sort = Maps.newHashMap(); List <Map<String, String> >sort = Lists.newArrayList(); if (CollUtil.isNotEmpty(dto.getSortList())) { dto.getSortList().forEach(sortByDto ->{ if (CharSequenceUtil.isNotEmpty(sortByDto.getColName())&&CharSequenceUtil.isNotEmpty(sortByDto.getSort()))) { Folder<String, String> map = Maps.newHashMap(); map.put("column", sortByDto.getColName()); map.put("order", sortByDto.getSort()); sort.add(folder); / / sort.put(sortByDto.getColName(), sortByDto.getSort()); } }); } S44: Catalog query module: Based on the professional asset catalog, search for the full amount of objects and data of the required data set, view the specific data sets and data items entering the lake, and verify the amount of data entering the lake, such as Figure 4 shown.
[0030] Asset catalog and public data list display: Based on the asset catalog service and master data service of the exploration and development data lake, the asset catalog is displayed in a tree-like structure, divided by profession, and users can search for relevant data sets according to the professional catalog, and multiple conditions are supported for fuzzy query. The asset catalog only displays the content with data by default, and supports the selection of full data display.
[0031] Filter condition settings: provide filtering by object and by lake entry time; ① Filter by object: After selecting the object relationship link, you can filter objects from surface to point, and also filter objects across levels (for example, you can directly query how many wells a branch has by crossing basins and depressions). You can gradually narrow the scope of objects based on your own query needs. At the same time, all levels of objects support fuzzy query and multiple selection. ②Filter by time: Provide the function of filtering data by entry time. Users can select "last three months", "last year" or a custom time range to filter data.
[0032] Data display and operation: provide data sorting, preview and download operations; ① Data sorting and filtering: supports sorting all fields in the table header in ascending or descending order; supports users to personalize the table to display or hide the header field information to meet the business needs of different users; the data filtering function supports users to set conditions for the current data through a single or multiple field combination to filter the result data.
[0033] ②Result data preview: query structured and unstructured data according to query conditions, and support online preview; ③Data download and collection: supports structured and unstructured data download, and supports the current user to collect the current filtering conditions and the result data under the filtering conditions, so as to facilitate quick query next time.
[0034] S45: Business query module: Based on the object directory tree, it provides the needs of querying the data of each business stage of the entire life cycle of the object, provides cross-professional data query services, and supports the daily work of business personnel, such as Figure 5 shown.
[0035] Master data selection: ①Master data directory The business query function provides multiple object chains. Users can select relationship chains according to the needs of the query work, and the system will generate a corresponding object directory tree based on the selected chain.
[0036] ②Select the object Users can select the required objects by expanding the directory tree level by level, and also support fuzzy search of objects by keywords. The system will automatically select all parent objects associated with the selected object based on the object relationship.
[0037] Filter condition settings: Supports multi-condition combination query filtering based on object type, data type, entry time, and file type.
[0038] Asset catalog selection: After the user selects an object, the user can select a dataset in the professional catalog column. The content in the professional catalog column will be filtered according to the object type of the selected object. By selecting the object type: data type, entry time, file type, you can filter the professional catalog content. After the user selects a single or batch dataset, you can query the list of datasets with data in combination with the selected object instance, and provide common operations such as data preview and download.
[0039] S47: Subject query module: Users can accurately locate the subject node they need to view based on the subject word list directory tree structure provided by the system, query the data set under the current subject, or quickly locate the subject word they need to view by fuzzy search keywords, such as Figure 6 shown.
[0040] Theme selection: ① My Topics: Supports users to subscribe to topics of interest based on actual work needs, allowing users to quickly locate and query a list of topics of interest.
[0041] ② Customized themes: Supports the addition, deletion, modification and grouping of user-defined themes, and supports users to add data sets to specified themes according to personal work needs to meet users' personalized business needs.
[0042] Filter condition settings: Supports multi-condition combination query filtering of dataset name, file type, and object type.
[0043] Data display and operation: Same as directory query and business query, supports data download, preview and other operations.
[0044] The embodiments of the present invention are described in detail above in conjunction with the accompanying drawings, but the present invention is not limited to the described embodiments. Without departing from the principles and spirit of the present invention, equivalent changes and improvements made on the basis of the technical solution of the present invention should not be excluded from the protection scope of the present invention.
[0045] The embodiment of the present application also provides a computer-readable storage medium, the storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the above method. The specific implementation process will not be repeated here.
[0046] The present application also provides an electronic device in an embodiment. The electronic device in this embodiment includes: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the aforementioned method in the embodiment is implemented. To avoid repetition, it is not described one by one here. Alternatively, when the computer program is executed by the processor, the functions of each model / unit in the device in the embodiment are implemented. To avoid repetition, it is not described one by one here.
[0047] The electronic device may be a computing device such as a desktop computer, a notebook, a PDA, a server, and a cloud server. The electronic device may include, but is not limited to, a processor and a memory. Those skilled in the art will appreciate that the electronic device may include more or fewer components than shown in the figure, or may combine certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.
[0048] The processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.
[0049] The memory can be an internal storage unit of an electronic device, such as a hard disk or memory of the electronic device. The memory can also be an external storage device of the electronic device, such as a plug-in hard disk, a smart memory card (SmartMedia Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device. Furthermore, the memory can also include both the internal storage unit of the electronic device and the external storage device. The memory is used to store computer programs and other programs and data required by the electronic device. The memory can also be used to temporarily store data that has been output or is to be output.
[0050] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here. In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
[0051] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (Processor) to perform some steps of the above-mentioned method of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.
[0052] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.< / externalmastermappingvo> < / ywbzsjxvo> < / ywbzsjjdetailvo> < / string> < / externalnodetreevo> < / externalnodetreevo> < / externalnodetreevo> < / externalnodetreevo> < / externalnodetreevo> < / externalnodetreevo> < / string> < / masterinfovo> < / masterinfovo> < / masterinfovo> < / masterinfovo> < / masterinfovo> < / masterinfovo> < / masterinfovo> < / masterinfovo> < / masterinfovo> < / masterinfovo> < / botcodevo> < / masterinfovo>
Claims
1. A method for querying offshore oil and gas exploration and development data, characterized in that: The method comprises: Obtaining a user's query request through the page layer, the query request including directory query, business query and subject query; For the catalog query, based on the pre-built exploration and development data asset catalog, the service corresponding to the catalog query is called to respond, and the data corresponding to the catalog query is obtained from the data layer for display; For the business query, according to the pre-established data resource directory of the business object, the service corresponding to the business query is called to respond, and the data corresponding to the business query is obtained from the data layer for display; For the subject query, based on the association relationship between the constructed data asset directory and the business object, the service corresponding to the subject query is called to respond, and the data corresponding to the subject query is obtained from the data layer for display.
2. The offshore oil and gas exploration and development data query method according to claim 1, characterized in that: According to the exploration and development business logic, a business object relationship model of offshore oil and gas resources, drilling operations, geological structures, and environmental parameters is constructed; wherein the relationship link of the business objects includes the various entities in the business process and their mutual relationships; the entity data corresponding to each entity is filled in through a data interface or manual entry, thereby establishing a complete entity object relationship.
3. The offshore oil and gas exploration and development data query method according to claim 1, characterized in that: Based on the standards and specifications of exploration and development business, we collect raw data from multiple preset sources such as offshore drilling platforms, seismic exploration, and geological analysis, and divide the sorted data into a full-professional asset directory tree by professional field to ensure the structure and traceability of the data and to ensure coverage of asset categories in all business areas.
4. The offshore oil and gas exploration and development data query method according to claim 1, characterized in that: The directory tree of the data asset directory is mapped and associated with the constructed business entity object relationship, so that the business object type can be located through the asset directory, and the asset directory can be located through the business object entity, thereby realizing refined management and rapid positioning of exploration and development business assets.
5. The offshore oil and gas exploration and development data query method according to claim 1, characterized in that: Based on business needs and user query habits, we create a set of subject directories, including drilled well evaluation, reserve research, and geological research while drilling. Under each subject, we define a detailed list of relevant data to facilitate quick location and query of business information.
6. An offshore oil and gas exploration and development data query tool, characterized in that: The query tool stores a computer program, and when the computer program is executed by a processor, it has the following functions: Receive the user's operation of clicking on a directory node, object link or inputting a subject query request through the interface; automatically call the background query service according to the preset query logic, which involves the matching rules of the object relationship link, the full professional asset directory tree and the subject directory; The query service obtains the corresponding data from the standardized data storage layer according to the request content, formats it, and returns it to the user interface for display, thus realizing fast retrieval and visual presentation of data.
7. The query tool according to claim 6, characterized in that: Provides a graphical user interface that displays the asset directory tree, theme directory, and data object relationships, and users can navigate through intuitive clicks.
8. The query tool according to claim 6, characterized in that: The integrated advanced search engine allows users to filter by combined conditions, including time range, data type, keyword preset and multiple query conditions to enhance the flexibility and accuracy of the query.
9. The query tool according to claim 2, characterized in that: Realize the real-time data retrieval function. When the user initiates a query request, the tool automatically calls the background service to retrieve and summarize relevant data from the distributed database.
10. The query tool according to claim 2, characterized in that: The visual display includes: query results are intuitively presented in the form of charts and reports, and support for data export and sharing.
Citation Information
Cited By
Electric power material reserve contract management method and device, medium and program product
CN119886688A
