An oil and gas storage and transportation station project management business data integration method

Abstract

The application discloses an oil and gas storage and transportation station engineering project management business data integration method, which comprises the following steps: S1, identifying business processes and business activities in the business field of oil and gas storage and transportation station engineering project management, abstracting engineering project management business entities, and constructing an engineering project management business logic architecture; S2, obtaining associated business documents in each business activity; S3, extracting data items of the business documents, and abstracting engineering project management business data entities; S4, analyzing the association relationship between the business data entities and the business entities, and establishing an engineering project management business data architecture; and S5, according to the association relationship between the engineering project management business data entities and the business entities, identifying key identifiers of the engineering project management business data entities, constructing an engineering project management business data theme, and forming engineering project management data assets. The project engineering business management complexity is reduced, and the engineering project management business integration degree is increased.

Description

Technical Field

[0001] This invention relates to the field of oil and gas storage and transportation station business management technology, and in particular to a business data integration method for oil and gas storage and transportation station engineering project management. Background Technology

[0002] To enhance their core business competitiveness and upgrade their operations, oil and gas storage and transportation companies are gradually divesting themselves of non-core businesses. Among these, engineering and technical contractors are playing an increasingly important role in outsourcing services to projects. With the development of digitalization, oil and gas companies have leveraged information technology to positively impact various business operations, establishing information service support systems for management models and business scope. However, in oil and gas storage and transportation engineering management, problems remain, including a large number of contractors, extensive and complex data and implementation processes, heterogeneous business data, and low integration leading to business and data silos. These issues introduce uncertainties into the engineering management work of oil and gas storage and transportation companies, preventing standardized, systematic, and regulated pipeline engineering management, and posing risks and pressures to the company's safe production.

[0003] Compared to engineering operations in other industries, oil and gas storage and transportation station engineering operations have unique industry characteristics and challenges. First, both oil and gas are flammable and explosive hazardous materials; leaks during storage and transportation can easily lead to safety accidents. Second, oil and gas pipeline transportation is limited by external factors and the natural environment (such as the impact of extreme weather events like heavy rain, strong winds, and extreme temperatures), resulting in low safety during transportation and a high risk of disasters. Third, facing increased pipeline volume and production and operational pressures, oil and gas storage and transportation companies have needs for construction projects such as oil depot pipeline relocation, equipment maintenance, and hazard mitigation. These projects are mostly concentrated in oil and gas areas, involving varying degrees of special operations such as temporary power supply, fire use, and work at heights, resulting in high technical risks and involving multiple disciplines working together.

[0004] The operation of oil and gas storage and transportation stations is extremely complex, and most of the engineering work is carried out by contractors, involving design, construction, and supervision. Current work mainly focuses on pipeline relocation, station oil transportation process upgrades, and equipment maintenance and replacement. Therefore, proper and safe management of oil and gas storage and transportation stations is a crucial aspect of successful engineering operations. Summary of the Invention

[0005] To address the aforementioned issues, this invention provides a business data integration method for oil and gas storage and transportation station engineering project management. Based on the business characteristics of oil and gas storage and transportation station engineering operations, this method reconstructs the business of oil and gas storage and transportation station engineering project management from the perspective of business data integration, and constructs a station engineering project management business architecture. This aims to solve the current business management technical problems of multi-professional / multi-disciplinary integration, business data management, and project safety and quality supervision in station engineering project management, thereby improving the safety of oil and gas pipeline engineering operations.

[0006] This invention provides a method for integrating business data in the management of oil and gas storage and transportation station engineering projects. The specific technical solution is as follows:

[0007] S1: Analyze the business domain of oil and gas storage and transportation station engineering project management, identify the business processes and activities in this business domain, abstract the engineering project management business entities, and construct the engineering project management business logic architecture;

[0008] S2: Based on the business logic architecture of engineering project management, obtain the business documents associated with each business activity;

[0009] S3: Extract data items from business documents and abstract business data entities for engineering project management based on the business logic architecture of engineering project management;

[0010] S4: Analyze the relationships between business data entities and business entities in project management, and establish a business data architecture for project management.

[0011] S5: Based on the relationship between engineering project management business data entities and business entities, identify the key identifiers of engineering project management business data entities, construct engineering project management business data themes, and form engineering project management data assets.

[0012] Further, step S1 is as follows:

[0013] S101: Obtain the business processes in the business area of ​​oil and gas storage and transportation station engineering project management, including: contractor entry management and project quality and safety supervision;

[0014] S102: Identify the business activities performed during the business process, and based on the business activities, abstract the engineering project management business entities. The engineering project management business entities include four major categories of business entities: pre-construction data verification and safety training, pre-operation risk assessment and technical briefing, special operation management, and operation process management. Each major category of business entities includes several business entities.

[0015] S103: Based on the project business entity, construct the project management business logic architecture.

[0016] Further, step S2 is as follows:

[0017] S201: Based on the business logic architecture of engineering project management, analyze the business data flow corresponding to the two business processes of contractor entry management and project quality and safety supervision.

[0018] S202: Based on the business data flow, extract the business documents for each business process.

[0019] Further, step S3 is as follows:

[0020] S301: Analyze the composition structure and content of data items in each business document;

[0021] S302: Map the engineering project management business data entities based on the engineering project management business logic architecture and business entities.

[0022] Further, step S4 is as follows:

[0023] S401: Determine the business data domain based on the classification of business data entities in engineering project management;

[0024] S402: Analyze the data flow between business data domains;

[0025] S403: Based on the business data domains and current business data entities, construct the business data architecture for engineering project management.

[0026] Further, step S5 is as follows:

[0027] S501: Based on the data flow between various business data domains and the key identifiers of various business data entities, analyze the relationships between various business data entities.

[0028] S502: Based on the business logic architecture of engineering project management and the relationship between various business data entities, construct the business data theme of engineering project management to form the data assets of the engineering project management business domain.

[0029] Furthermore, the project management business data subject includes project management business entities and business data entities;

[0030] The project management business entity is a business object, and each business object corresponds to an attribute table.

[0031] The business data entities are the key information of the business documents, and all business data entities are stored in the same relational table.

[0032] Furthermore, the relationship between the various business data entities is a link between the key identifiers of each business data entity;

[0033] The key identifier links correspond to a relationship table that stores the relationships between each key identifier.

[0034] Furthermore, the data assets of the project management business correspond to a business data entity classification table;

[0035] The classification table is determined by the business data domain and contains the relationships between business data entities;

[0036] The classification table is a relational table that stores the data assets and data structure of engineering project management business.

[0037] The beneficial effects of this invention are as follows:

[0038] This invention organizes the business entities of engineering project management according to the logic of business data flow, and constructs the business architecture of engineering project management; it analyzes the relationships between business entities, identifies the business data entities of engineering project management based on business logic, and constructs the business data architecture of engineering project management; based on the key identifier relationships of business data entities, it summarizes the data themes of engineering project management business scenarios and forms data assets for engineering project management business; through the fusion analysis of business data of oil and gas storage and transportation station engineering project management, it removes a large amount of duplicate and redundant data in engineering project management business, solves the problem of difficult synchronization of information in oil and gas storage and transportation station engineering project management, reduces the complexity of project engineering business management, and increases the integration of engineering project management business. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of the overall process of the method of the present invention;

[0040] Figure 2 This is a schematic diagram of the business logic architecture for engineering project management;

[0041] Figure 3 This is a schematic diagram of the business data flow for contractor entry management;

[0042] Figure 4 This is a schematic diagram of the business data flow for project quality and safety supervision;

[0043] Figure 5 This is a diagram illustrating the data flow relationships between business data domains;

[0044] Figure 6 This is a schematic diagram of the business data architecture for engineering project management;

[0045] Figure 7 This is a schematic diagram of the data asset content architecture of the engineering project management business domain. Detailed Implementation

[0046] The technical solutions in the embodiments of the present invention are clearly and completely described in the following description. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0047] In the description of the embodiments of the present invention, it should be noted that the indicated orientation or positional relationship is based on the orientation or positional relationship shown in the accompanying drawings, or the orientation or positional relationship in which the product of the invention is conventionally placed during use, or the orientation or positional relationship in which those skilled in the art conventionally understand it during use. This is only for the convenience of describing the present invention and simplifying the description, and is not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, it should not be construed as a limitation of the present invention. Furthermore, the terms "first" and "second" are only used to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0048] In the description of the embodiments of the present invention, it should also be noted that, unless otherwise explicitly specified and limited, the terms "set" and "connection" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a direct connection or an indirect connection through an intermediate medium. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0049] Example 1

[0050] Embodiment 1 of the present invention discloses a business data integration method for oil and gas storage and transportation station engineering project management, such as... Figure 1 As shown, the details are as follows:

[0051] S1: Analyze the business domain of oil and gas storage and transportation station engineering project management, identify the business processes and activities in this business domain, abstract the engineering project management business entities, and construct the engineering project management business logic architecture;

[0052] Specifically as follows:

[0053] S101: Obtain the business processes in the business area of ​​oil and gas storage and transportation station engineering project management, including: contractor entry management and project quality and safety supervision;

[0054] S102: Identify the business activities performed during the business process, and based on the business activities, abstract the engineering project management business entities. The engineering project management business entities include four major categories of business entities: pre-construction data verification and safety training, pre-operation risk assessment and technical briefing, special operation management, and operation process management.

[0055] Each major business entity category includes several business entities, specifically:

[0056] Pre-construction document verification and safety training: verification of entry documents, confirmation of qualification compliance, safety education, and entry procedures;

[0057] Pre-operation risk assessment and technical briefing: Project coordination, on-site safety technical briefing, operational safety analysis, and pre-work inspection;

[0058] Special operations management: work application, work condition confirmation, pre-shift meeting, work approval;

[0059] Work process management: work supervision, project spot checks, work interruption, work extension, work cancellation, in-process meetings, rectification verification, resumption of work management, work closure, and pre-acceptance;

[0060] S103: As Figure 2 As shown, a business logic architecture for project management is constructed based on the project business entity.

[0061] S2: Based on the project management business logic, obtain the business documents associated with each business activity;

[0062] Specifically as follows:

[0063] S201: As Figures 3-4 As shown, based on the business logic architecture of engineering project management, the business data flow corresponding to the two business processes of contractor entry management and project quality and safety supervision is analyzed respectively.

[0064] S202: Based on the business data flow, extract the business documents for each business process.

[0065] The specific details of the business document are as follows:

[0066] The documents involved in pre-construction document verification and safety training include: "Construction Commencement Report", "Construction Organization Design (Plan) Submission Form", "Construction Liaison Form", "Contractor Safety Training Record", and "Personnel Information Form".

[0067] The forms involved in the pre-operation risk assessment and technical briefing include: "On-site Briefing Record", "Operation Safety Analysis Form" and "Risk Management Form";

[0068] The forms involved in special operations management include: Work Permit, Hot Work Permit, Excavation Permit, Working at Heights Permit, Lifting Permit, Automated Control Equipment Commissioning Permit, Temporary Power Supply Permit, Pipeline Opening Permit, Confined Space Entry Permit, X-ray Work Permit, Hydraulic Mobile Crane Appearance Inspection Checklist, Mechanical Mobile Crane Appearance Inspection Checklist, and Wire Rope and Hook Inspection Checklist.

[0069] The forms involved in risk control during the operation process include: On-site monitoring record, violation handling form, problem rectification feedback form, contractor penalty notice, and pre-acceptance record.

[0070] S3: Extract data items from business documents and abstract business data entities for engineering project management based on the business logic of engineering project management;

[0071] Specifically as follows:

[0072] S301: Analyze the composition structure and content of data items in each business document;

[0073] S302: Map the engineering project management business data entities based on the engineering project management business logic architecture and business entities.

[0074] S4: Analyze the relationships between business data entities and business entities in project management, and establish a business data architecture for project management.

[0075] Specifically as follows:

[0076] S401: Determine the business data domain based on the classification of business data entities in engineering project management;

[0077] S402: As Figure 5 As shown, the data information flow between business data domains is analyzed;

[0078] S403: As Figure 6 As shown, the business data architecture for engineering project management is constructed based on the business data domain and the current business data entities.

[0079] The business data domains and business data entities are as follows:

[0080] Pre-construction documentation verification and safety training data fields: commencement information, training information, and personnel entry information;

[0081] Pre-operation risk assessment and technical briefing business data domain: briefing information, safety information data, risk management information;

[0082] Special Operations Management Business Data Field: Operation Application Information;

[0083] Operational process risk management business data domains: monitoring information, rectification and verification information, and pre-acceptance information.

[0084] S5: Based on the relationship between engineering project management business data entities and business entities, identify the key identifiers of engineering project management business data entities, construct engineering project management business data themes, and form engineering project management data assets.

[0085] Specifically as follows:

[0086] S501: Based on the data flow between various business data domains and the key identifiers of various business data entities, analyze the relationships between various business data entities.

[0087] S502: As Figure 7 As shown, based on the business logic architecture of engineering project management and the relationships between various business data entities, business data themes for engineering project management are constructed, forming data assets of the engineering project management business domain.

[0088] In this embodiment, the project management business data subject includes project management business entities and business data entities, and the storage architecture in the database is as follows:

[0089] The project management business entity is a business object, and each business object corresponds to an attribute table.

[0090] The business data entities are the key information of the business documents, and all business data entities are stored in the same relational table.

[0091] The relationship between various business data entities is a link between the key identifiers of each business data entity.

[0092] The key identifier links correspond to a relationship table that stores the relationships between each key identifier.

[0093] The data assets of the engineering project management business correspond to a business data entity classification table;

[0094] The classification table is determined by the business data domain and contains the relationships between business data entities;

[0095] The classification table is a relational table that stores the data assets and data structure of engineering project management business.

[0096] This invention is not limited to the specific embodiments described above. The invention extends to any new feature or combination disclosed in this specification, as well as any new method or process step or combination disclosed herein.

Claims

1. A method for business data integration for oil and gas storage and transportation site engineering project management, characterized in that, The method comprises the following steps: S1: analyzing the engineering project management business field of an oil and gas storage and transportation station, identifying business processes and business activities in the business field, abstracting engineering project management business entities, and constructing an engineering project management business logic architecture; S2: obtaining business documents associated with each business activity according to the engineering project management business logic architecture; S3: extracting data items of the business documents, and abstracting engineering project management business data entities according to the engineering project management business logic architecture; S4: analyzing the association between the engineering project management business data entities and the business entities, and establishing an engineering project management business data architecture; S5: identifying key identifiers of the engineering project management business data entities, constructing an engineering project management business data theme, and forming an engineering project management data asset according to the association between the engineering project management business data entities and the business entities. The engineering project management business data theme comprises engineering project management business entities and business data entities. Each business object corresponds to an attribute table. All business data entities are stored in a same relationship table.

2. The business data integration method for oil and gas storage and transportation station engineering project management according to claim 1, characterized in that, Step S1 is specifically as follows: S101: obtaining business processes in the engineering project management business field of the oil and gas storage and transportation station, wherein the business processes comprise contractor access management and project quality and safety supervision; S102: identifying business activities performed in the business processes, and abstracting engineering project management business entities according to the business activities, wherein the engineering project management business entities comprise four business entity categories, i.e., pre-construction data verification and safety training, pre-operation risk evaluation and technical disclosure, special operation management, and operation process management, and each business entity category comprises a plurality of business entities; S103: constructing an engineering project management business logic architecture according to the engineering project management business entities.

3. The business data integration method for oil and gas storage and transportation station engineering project management according to claim 2, characterized in that, Step S2 is specifically as follows: S201: analyzing business data flows corresponding to the two business processes of contractor access management and project quality and safety supervision based on the engineering project management business logic architecture; S202: extracting business documents in each business process based on the business data flows.

4. The business data integration method for oil and gas storage and transportation station engineering project management according to claim 3, characterized in that, Step S3 is specifically as follows: S301: analyzing data item composition structures and contents in each business document; S302: mapping engineering project management business data entities according to the engineering project management business logic architecture and the business entities.

5. The business data integration method for oil and gas storage and transportation station engineering project management according to claim 4, characterized in that, Step S4 is specifically as follows: S401: determining business data domains according to engineering project management business data entity classification; S402: analyzing data information flow conditions between the business data domains; S403: constructing an engineering project management business data architecture according to the business data domains and the current business data entities.

6. The business data integration method for oil and gas storage and transportation station engineering project management according to claim 5, characterized in that, Step S5 is specifically as follows: S501: analyzing relationships between the business data entities based on data flows between the business data domains and key identifiers of the business data entities; S502: According to the project management business logic architecture, the correlation between each business data entity, the business data theme of the project management is constructed, and the data asset of the project management business domain is formed.

7. The business data integration method for oil and gas storage and transportation terminal engineering project management according to any one of claims 1-6, characterized in that, The relationship between each business data entity is linked through the key identifier of each business data entity; The key identifier link corresponds to a relationship table, which stores the relationship of the key identifier.

8. The business data integration method for oil and gas storage and transportation station engineering project management according to any one of claims 1-6, characterized in that, The data asset of the project management business corresponds to a business data entity classification table; The classification table is determined by the business data domain and contains the correlation between the business data entities; The classification table is a relationship table, which stores the data asset and data structure of the project management business.

Images