WO2009124256A1 - Systems and methods for correlating meta-data model representations and asset-logic model representations - Google Patents

Systems and methods for correlating meta-data model representations and asset-logic model representations Download PDF

Info

Publication number
WO2009124256A1
WO2009124256A1 PCT/US2009/039480 US2009039480W WO2009124256A1 WO 2009124256 A1 WO2009124256 A1 WO 2009124256A1 US 2009039480 W US2009039480 W US 2009039480W WO 2009124256 A1 WO2009124256 A1 WO 2009124256A1
Authority
WO
WIPO (PCT)
Prior art keywords
stakeholder
asset
model representation
meta
data
Prior art date
Application number
PCT/US2009/039480
Other languages
French (fr)
Inventor
Rajpaul Singh Bal
Mark Lochmann
Chaminda Peries
Laurence Reid
Original Assignee
Landmark Graphics Corporation, A Halliburton Company
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Landmark Graphics Corporation, A Halliburton Company filed Critical Landmark Graphics Corporation, A Halliburton Company
Priority to CN200980112469.1A priority Critical patent/CN101990659B/en
Priority to BRPI0906540A priority patent/BRPI0906540A2/en
Priority to CA2719937A priority patent/CA2719937C/en
Priority to MX2010010785A priority patent/MX2010010785A/en
Priority to AU2009231624A priority patent/AU2009231624B2/en
Priority to EP09727609.1A priority patent/EP2266021A4/en
Publication of WO2009124256A1 publication Critical patent/WO2009124256A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/80Management or planning

Definitions

  • the present invention generally relates to correlating meta-data model representations and asset-logic model representations in a system model.
  • the present invention therefore, meets the above needs and overcomes one or more deficiencies in the prior art by providing systems and methods for correlating only approved manipulations of meta-data-model representations and asset-logic model representations in a system model.
  • the present invention includes a computer implemented method for correlating meta-data model representations and asset-logic model representations, which comprises: i) manipulating a system model, the system model comprising a meta-data model representation controlled by only a stakeholder and an asset- logic model representation controlled by only the stakeholder or another stakeholder; ii) notifying only at least one of the stakeholder and the another stakeholder of a manipulation of at least one of the meta-data model representation and the asset-logic model representation; iii) recording each manipulation approved or rejected by the at least one of the stakeholder and the another stakeholder; and iv) transforming the system model on a computer system by Attorney Docket No. 33849-270
  • the present invention includes a program carrier device for carrying computer executable instructions for correlating meta-data model representations and asset-logic model representations.
  • the instructions are executable to implement: i) manipulating a system model, the system model comprising a meta-data model representation controlled by only a stakeholder and an asset-logic model representation controlled by only the stakeholder or another stakeholder; ii) notifying only at least one of the stakeholder and the another stakeholder of a manipulation of at least one of the meta-data model representation and the asset-logic model representation; iii) recording each manipulation approved or rejected by the at least one of the stakeholder and the another stakeholder; and iv) transforming the system model by correlating only each approved manipulation between the meta-data model representation and the asset-logic model representation.
  • the present invention includes a computer system for correlating meta-data model representations and asset-logic model representations, which comprises: i) a system model, the system model comprising a meta-data model representation controlled by only a stakeholder and an asset-logic model representation controlled by only the stakeholder or another stakeholder; ii) a notification module for notifying only at least one of the stakeholder and the another stakeholder of a manipulation of at least one of the metadata model representation and the asset-logic model representation; iii) a recording module for recording each manipulation approved or rejected by the at least one of the stakeholder and the another stakeholder; and iv) a transformation module for transforming the system model by correlating only each approved manipulation between the meta-data model representation and the asset-logic model representation.
  • FIG. 1 is a block diagram illustrating a system for implementing the present invention.
  • FIG. 2 illustrates the collaborative network matrix model of the present invention in relation to a wider system for collaboration.
  • FIG. 3 is a block diagram illustrating the collaborative network matrix model in FIG. 2.
  • FIG. 4 is a block diagram illustrating the collaborative network matrix model in FIG. 2 after a system change.
  • FIG. 5 is a block diagram illustrating the collaborative network matrix model in FIG. 2 as a transformation.
  • FIG. 6 illustrates the development and change of a collaborative network matrix model over time.
  • FiG. 7 is a flow diagram illustrating one embodiment of a method for implementing the present invention.
  • step may be used herein to describe different elements of methods employed, the term should not be interpreted as implying any particular order among or between various steps herein disclosed unless otherwise expressly limited by the description to a particular order. While the following description refers to the oil and gas industry, the systems and methods of the present invention are not limited thereto and may also be applied to other industries to achieve similar results.
  • the present invention provides a model based solution to select the appropriate level of model detail for the preferences of dissimilar users, also referred to herein as clients or stakeholders. Unlike the prior art, the present invention correlates different models. Thus, the present invention permits moving between models with different levels of detail. Moreover, while different models with various levels of detail may be known in the art, the present invention, instead, provides the opportunity to utilize different models in a single application with each model related to a common system model.
  • the present invention may be implemented through a computer-executable program of instructions, such as program modules, generally referred to as software applications or application programs executed by a computer.
  • the software may include, for example, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types.
  • the software forms an interface to allow a computer to react according to a source of input.
  • DecisionSpace® which is a commercial software application marketed by Landmark Graphics Corporation, may be used as an interface application to implement the present invention.
  • the software may also cooperate with other code segments to initiate a variety of tasks in response to data received in conjunction with the source of the received data.
  • the software may be stored and/or carried on any variety of memory media such as CD-ROM, magnetic disk, bubble memory and Attorney Docket No. 33849-270
  • semiconductor memory e.g., various types of RAM or ROM.
  • the software and its results may be transmitted over a variety of carrier media such as optical fiber, metallic wire, free space and/or through any of a variety of networks such as the Internet.
  • the invention may be practiced with a variety of computer-system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable-consumer electronics, minicomputers, mainframe computers, and the like. Any number of computer-systems and computer networks are acceptable for use with the present invention.
  • the invention may be practiced in distributed-computing environments where tasks are performed by remote- processing devices that are linked through a communications network.
  • program modules may be located in both local and remote computer-storage media including memory storage devices.
  • the present invention may therefore, be implemented in connection with various hardware, software or a combination thereof, in a computer system or other processing system.
  • FIG. 1 a block diagram of a system for implementing the present invention on a computer is illustrated.
  • the system includes a computing unit, sometimes referred to as a computing system, which contains memory, application programs, a client interface, and a processing unit.
  • the computing unit is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention.
  • the memory primarily stores the application programs, which may also be described as program modules containing computer-executable instructions, executed by the computing unit for implementing the present invention described herein and illustrated in FIGS. 2-7.
  • the memory therefore, includes a CNMM Module, which enables the method illustrated and described in reference to FIG. 7.
  • the CNMM Module includes a Attorney Docket No. 33849-270
  • collaborative-network-matrix model also known as a system model, which is illustrated and described in reference to FIGS, 2-7.
  • the CNMM Module also may interact with DecisionSpace ® , AssetObserverTM, AssetSolver ⁇ u and AssetConnectTM as further described in reference to FIG. 2.
  • the systems and methods of the present invention are thus, based on a system model that correlates meta-data-model representations of a production asset with the various asset-logic model representations (or taxonomies) to provide a collaborative, consistent, and relevant representation of the asset to the different stakeholders.
  • the system model performs the correlations between different meta-data model representations using the various asset-logic model representations for common data items and attributes shared across the system thus, addressing the many key activities relating to the asset that may have different meta-model representations representing their pertinent data requirements. In this manner, effective interoperability is achieved.
  • the computing unit typically includes a variety of computer readable media.
  • computer readable media may comprise computer storage media and communication media.
  • the computing system memory may include computer storage media in the form of volatile and/or nonvolatile memory such as a read only memory (ROM) and random access memory (RAM).
  • ROM read only memory
  • RAM random access memory
  • a basic input/output system (BIOS) containing the basic routines that help to transfer information between elements within the computing unit, such as during start-up, is typically stored in ROM.
  • the RAM typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by the processing unit.
  • the computing unit includes an operating system, application programs, other program modules, and program data.
  • the components shown in the memory may also be included in other removable/nonremovable, volatile/nonvolatile computer storage media.
  • a Attorney Docket No. 33849-270 is shown in other removable/nonremovable, volatile/nonvolatile computer storage media.
  • hard disk drive may read from or write to nonremovable, nonvolatile magnetic media
  • a magnetic disk drive may read from or write to a removable, non-volatile magnetic disk
  • an optical disk drive may read from or write to a removable, nonvolatile optical disk such as a CD ROM or other optical media.
  • Other removable/non-removable, volatile/non-volatile computer storage media may include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like.
  • the drives and their associated computer storage media discussed above therefore, store and/or carry computer readable instructions, data structures, program modules and other data for the computing unit.
  • a client may enter commands and information into the computing unit through the client interface, which may be input devices such as a keyboard and pointing device, commonly referred to as a mouse, trackball or touch pad.
  • input devices may include a microphone, joystick, satellite dish, scanner, or the like.
  • These and other input devices are often connected to the processing unit through the client interface that is coupled to a system bus, but may be connected by other interface and bus structures, such as a parallel port or a universal serial bus (USB).
  • a monitor or other type of display device may be connected to the system bus via an interface, such as a video interface.
  • computers may also include other peripheral output devices such as speakers and printer, which may be connected through an output peripheral interface.
  • system model 2114 a collaborative-network-matrix model (system model 214) is illustrated within a wider system 200 for collaboration among multiple clients Attorney Docket No. 33849-270
  • Additional system components typically associated with a production asset may include, for example, different types of data 202 (e.g. operations data, business data and engineering data), a data analytics engine 204, a data integration platform 206, a data environment 208, a workflow integration platform 210, a software applications environment 212 and a collaborative environment 216.
  • the various components of the system 200 enable specific inter-related functions and therefore, must interact with each other seamlessly in order to avoid discontinuities and/or errors.
  • the role of the system model 214 is to provide interoperability across the various diverse applications and datasets within the overall system 200. Thus, the system model 214 functions as a common base model for collaboration among the stakeholders 218.
  • Other components of the system 200 may include interfaces to and from an Enterprise Resource Planning System (e.g. SAP) or a computerized Maintenance Management System, or a computerized Work Management System controlling work in the physical asset and necessary status of equipment and system isolations.
  • SAP Enterprise Resource Planning System
  • a computerized Maintenance Management System e.g., computerized
  • the data analytics engine 204 allows data to be manipulated to produce numerous reports and analysis using simple to complex proprietary and industry standard algorithms. It typically supports data filtering and cleaning as well as appropriate visualization technologies to present data in meaningful, relevant and insightful ways into the viewing or collaborative environment 216 for use by the stakeholders 218.
  • the data integration platform 206 typically provides data connectors appropriate to each data language and database. This component allows the stakeholders 218 to map to particular data sets such as asset equipment tags or unique well identifiers, thus enabling data flow throughout the system 200.
  • the data environment 208 typically interfaces with some regulatory or distributed control system incorporating data to and from instruments, meters, and control devices, such as actuators, valves and the like, across the asset. Considering the typical Attorney Docket No. 33849-270
  • the data environment 208 typically includes multiple types of data 202, each designed to best suit particular types of data.
  • data for example, a relational database for business data, a data historian for high frequency operations data and a data warehouse for engineering data such as well tables and production allocation tables.
  • the data will exist in one or more data languages, such as, for example, OPC, ODBC, HTML, WITSML, and PRODML, which are well known in the art and conform to respective corresponding data standards.
  • the workflow integration and orchestration platform 210 spans the various IT operating environments, connects to the numerous software applications, maps to the respective data tags and items used by the software applications and interfaces with some viewing or shared collaborative environments to interface and interact with numerous stakeholders 218 involved across the workflows.
  • the workflows are numerous but might include frequent and infrequent activities such as; for example, well test validation, production allocation, production surveillance, production optimization and others more particularly described in U.S. Patent Application Serial No. 12/266,766, which is incorporated herein by reference.
  • the software applications environment(s) 212 includes different IT operating environments such as Windows and Linux, appropriate to the range of applications used across the asset.
  • the software applications environment(s) 212 may also include well known, proprietary applications for providing diverse, complex, and relatively simple functionality. These applications, for example, may include petro-technical and geoscience applications common to the industry as well as more common software applications commonly used such as MS Office. These applications may also be used for, but not limited to, reservoir and well simulation, modeling of hydraulic networks and facilities systems, material balance, nodal analysis, production allocation, production surveillance, hydrocarbon accounting, regulatory Attorney Docket No. 33849-270
  • the function of the system model 214 is to manage the numerous interfaces and interactions between the data items and their correct and consistent usage within the various logic schemes that are representative of the system 200 and its architecture. It does so in a dynamic operating environment where all or many of the components may be used simultaneously and/or continuously by the stakeholders 218, which may be given specific and varying access and authority rights to control the components.
  • the collaborative environment 216 typically represents a web-based (intranet or internet) access and viewing environment that can be used by a diverse range of potential geographically located stakeholders 218, which will provide secure access and bandwidths appropriate to the range of data and software applications included in the system 200.
  • the use of portals will typically allow diverse stakeholders 218 to have relevant custom views of only the information they require from the system 200 and also may provide effective communications via e-mail, instant messaging, net meetings and the like.
  • DecisionSpace ® for Production may be used to provide the system architecture, component integration and set of functionality illustrated in FIG. 2.
  • the system model 214 interacts with AssetObserver ⁇ M , AssetConnectTM and AssetSolverTM to achieve overall functionality.
  • Asset ⁇ bserverTM provides the data integration platform 206 and also the collaborative environment 216 for data organization and visualization within the overall system 200.
  • AssetConnectiM provides the software application environment(s) 212 and also the workflow integration platform 210, which, together, enable orchestration or technical workflows that utilize both technical applications and related data 202.
  • AssetSolverTM provides the data analytics engine 204, which is capable of handling both high volume and real-time data about operations and aggregate historical data used for engineering purposes. Each of the components jointly and separately benefit from the functionality provided by the system model 214.
  • FIG. 3 a block diagram of the collaborative-network-matrix model in FIG. 2 (system model 214) is illustrated.
  • the system model 214 is static, meaning at rest, when transformations and manipulations are not occurring.
  • the system model 214 acts purely as a data router - providing the flow of appropriate information to different organizational stakeholders and/or applications.
  • the system model 214 includes several com p onents such as the vertical co ⁇ vonents Ll-LN the horizontal components Ml-MN, transformations and manipulations.
  • the vertical components Ll-LN may include logical representations of the various taxonomies representative of the asset such as, for example, business logic, operations logic, engineering logic, scientific logic and organizational logic, among others. As illustrated in FIG. 3, the taxonomies include scientific logic and business logic.
  • the horizontal components Ml-MN are meta-data model representations of specific key activities or stakeholder domains or other manifestations of meta-data model representations appropriate to the asset such as, for example, production data, business data, engineering data and equipment data, among others.
  • the meta data model representations include operations, design, regulatory, meter, flow and physical network-
  • the meta-data model representations comprise numerous data items and their attributes.
  • Transformations are the routines for definition, identification and correlation of data items and attributes within the meta-data model representation layers, which are shared across the various asset-logic model representations. This might include, for example, Attorney Docket No. 33849-270
  • Routines may include, for example, initial screening, searching, comparison and matching of the data items and attributes across the various components of the system model 214. Screening is an activity undertaken by proprietary software in order to identify the range of data attributes in the system model 214. Searching may involve a search engine to find the locations of such attributes and a comparison may utilize artificial intelligence (such as a neural network or expert system) in order to determine correlations and interrelationships between meta-data model representations and asset-logic model representations, across the system model 214. This function allows translation of common data items and attributes between one meta-data model representation layer and others.
  • Artificial intelligence such as a neural network or expert system
  • Manipulations are automatically initiated at occurrence of an event and may include, for example: a) the various and multiple uses of data items and attributes across the asset by the multiple stakeholders using the diverse data sources, applications and programs common to a production asset, b) the control or subsequent change of those relatively static asset-logic model representations and meta-data model representations and/or the correlations or attributes of data items therein such as, for example: i) a permanent or temporary physical change to the production system configuration by insertion or removal of an item of equipment, ii) a change on the organization structure and/or individuals in a given role or to their approval authority or iii) modification to an engineering algorithm, and c) the control or subsequent change of the asset-logic model representations, the meta-data model representations and/or the correlations or attributes of data items therein such as, for example: i) a change to a valve brought about by, and consistent with, well testing operations or shutdown of an item of equipment for planned maintenance routines, or ii) the routine change to
  • FIG. 4 a block diagram of the collaborative-network-matrix model in FIG. 2 (system model 214) is illustrated after a system change.
  • a first stakeholder such as, for example, a production engineer may manipulate several horizontal components to reflect a system change that has occurred.
  • a system change reflects a manipulation of the operations, flow and physical network meta-data model representations.
  • the system model 214 is able to determine which stakeholder or stakeholders need to be informed of the changes to the horizontal components and/or vertical components and who initiated the change(s). This is achieved through an event notification service. The status of the components may be tracked during periods of change to ensure appropriate adjustment according to outcome of the system change controls.
  • the system model 214 may be housed within a data repository with real time audit control. This mechanism is utilized to track component changes. Components of the system model 214 may be designated more or less critical at the establishment of the system model 214 such that risk can be determined and communicated with alerts to the system stakeholders.
  • the system model 214 may record rejected and approved changes and Attorney Docket No.33849-270
  • Approval's are generated either by human interaction with the system or by a logic based expert system.
  • Changes can include changes to stakeholders, asset-logic model representations, meta-data model representations and/or data items and attributes.
  • FIG. 7 a flow diagram illustrates one embodiment of a method 700 for implementing the present invention.
  • a system model is created, which comprises one or more metadata model representations and one or more asset-logic model representations.
  • the system model may include, for example, the same meta-data model representations and/or asset logic model representations described in reference to FIGS. 2-5. Furthermore, the system model may operate, for example, in the same manner as the system model described in reference to FIGS. 1-6.
  • Each meta-data model representation may be controlled by one or more respective stakeholders and each asset-logic model representation may be controlled (owned) by one or more respective stakeholders. In other words, each meta-data model representation may be controlled by a respective stakeholder and each asset-logic model representation may be controlled by a respective stakeholder.
  • any respective stakeholder may control more than one meta-data model representation and/or more than one asset-logic model representation.
  • each meta-data model representation and each asset-logic model representation should not be controlled by more than one respective stakeholder however, may be controlled by more than one stakeholder under exceptional circumstances.
  • Each meta-data model representation may include at least one data item and an attribute.
  • each asset-logic model representation may include at least one data item and an attribute.
  • the system model is manipulated using a GUI or other means well known in the art.
  • a collaborative environment and/or API may be utilized within a wider system to facilitate manipulation of the system model.
  • the system model may be manipulated, for example, by a manipulation of one or more of the meta-data model representations and/or one or more of the asset-logic model representations. A manipulation therefore, may represent a change to at least one of the meta-data model representations and the asset-logic model representations.
  • the system model may be manipulated on a computer system by any stakeholder. Each stakeholder therefore, may access the system model through a collaborative environment to manipulate the system model on the computer system.
  • Each stakeholder therefore, may control one or more meta-data model representations and/or asset-logic model representations, while having access to the system model through a collaborative environment for purposes of manipulating the system model.
  • Each stakeholder however, having access to the system model through a collaborative environment for purposes of manipulating the system model may not have control of one or more meta-data model representations and/or asset-logic model representations.
  • each stakeholder in control of the one or more meta-data model representations and/or the one or more asset-logic model representations is notified of a manipulation of each respective meta-data model representation and/or each respective asset- logic model representation controlled by each respective stakeholder.
  • a collaborative environment and/or API may be utilized within a wider system to facilitate notification of each manipulation.
  • a stakeholder may manipulate one or more of the meta-data model representations and/or one or more of the asset-logic model representations, which it does not control, and only each stakeholder in control of each respective manipulated meta-data model representation and/or asset-logic model representation is notified of the manipulation.
  • each manipulation approved or rejected by each respective stakeholder in control of the manipulated meta-data model representation(s) and/or asset- logic model representation(s) is recorded by the system model.
  • Each approved manipulation therefore, may represent a change to a data item and/or an attribute in one or more of the meta-data model representations and/or one or more of the asset-logic model representations.
  • step 710 the system model is transformed on a computer system based on the approved manipulation(s) by correlating each approved manipulation between the metadata model representation(s) and the asset-logic model representation(s).
  • Transforming the system model comprises using at least one routine for correlating each approved manipulation between the meta-data model representation(s) and the asset-logic model representation(s) .
  • step 712 the method 700 determines whether to repeat. If the method 700 is repeated, then the method 700 proceeds to step 704. If the method 700 does not repeat, then the method 700 ends.
  • the system model may be deployed in conjunction with a production allocation application whereby data pertaining to allocation changes to the production system might be more readily identified and for differing purposes such as technically correct allocation and fiscal allocation for operations, engineering and/or business uses.
  • Other applications utilizing the system modei may include, for example, production loss reporting, whereby the various causes of lost production might be attributed as they are reported, understood and associated with relevant operations, engineering and business data and uses.

Abstract

Systems and methods for correlating meta-data model representations and asset-logic model representations in a system model.

Description

Attorney Docket No. 33849-270
SYSTEMS AND METHODS FOR CORRELATING
META DATA MODEL REPRESENTATIONS AND
ASSET-LOGIC MODEL REPRESENTATIONS
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] The priority of U.S. Patent Application No. 61/042,542, filed on April 4, 2008, is hereby claimed, and the specification thereof is incorporated herein by reference. STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH
[0002] Not applicable.
FIELD OF THE INVENTION
[0003] The present invention generally relates to correlating meta-data model representations and asset-logic model representations in a system model.
BACKGROUND OF THE INVENTION
[0004] Understanding and operating an oil and gas production asset as a single holistic system has been frustrated by significant impediments. For any asset, there are typically multiple applications, multiple data sets, multiple taxonomies and multiple stakeholders, some or all of which may be sharing common data across the asset. Interoperability among these programs, persons, and structures as a single system, while desired, has been frustrated by the lack of an underlying framework for handling the necessary transformations, translations, and definitions required between and among the various system components.
[0005] Attempts to provide this understanding and operation have previously focused on providing data replication, where each stakeholder group develops or receives its own version of the logical network and data model that includes all of its requirements. In these attempts, the act of transforming the data model by correlating changes between the data model representations has not been done or has been done crudely. Although some level of interoperability has been achieved by point to point integration, it is largely limited to Attorney Docket No. 33849-270
supporting single workflows. Moreover, changes to the data model representations cannot be effectively controlled when each stakeholder can decide whether such changes should be applied (accepted) and communicated to the other stakeholders. Previous approaches thus, have been unable to account for reconciliation and data integrity issues in a systematic and/or system- wide way.
[0006] There is therefore, a need for systems and methods that provide uninterrupted interoperability among the various data sets, applications, taxonomies and stakeholders sharing data across a production asset. In other words, there is a need for transforming a system model by correlating only approved manipulations of meta-data model representations and asset-logic model representations in the system model.
SUMMARY OF THE INVENTION
[0007] The present invention therefore, meets the above needs and overcomes one or more deficiencies in the prior art by providing systems and methods for correlating only approved manipulations of meta-data-model representations and asset-logic model representations in a system model.
[0008] In one embodiment, the present invention includes a computer implemented method for correlating meta-data model representations and asset-logic model representations, which comprises: i) manipulating a system model, the system model comprising a meta-data model representation controlled by only a stakeholder and an asset- logic model representation controlled by only the stakeholder or another stakeholder; ii) notifying only at least one of the stakeholder and the another stakeholder of a manipulation of at least one of the meta-data model representation and the asset-logic model representation; iii) recording each manipulation approved or rejected by the at least one of the stakeholder and the another stakeholder; and iv) transforming the system model on a computer system by Attorney Docket No. 33849-270
correlating only each approved manipulation between the meta-data model representation and the asset-logic model representation.
[0009] In another embodiment, the present invention includes a program carrier device for carrying computer executable instructions for correlating meta-data model representations and asset-logic model representations. The instructions are executable to implement: i) manipulating a system model, the system model comprising a meta-data model representation controlled by only a stakeholder and an asset-logic model representation controlled by only the stakeholder or another stakeholder; ii) notifying only at least one of the stakeholder and the another stakeholder of a manipulation of at least one of the meta-data model representation and the asset-logic model representation; iii) recording each manipulation approved or rejected by the at least one of the stakeholder and the another stakeholder; and iv) transforming the system model by correlating only each approved manipulation between the meta-data model representation and the asset-logic model representation.
[0010] In yet another embodiment, the present invention includes a computer system for correlating meta-data model representations and asset-logic model representations, which comprises: i) a system model, the system model comprising a meta-data model representation controlled by only a stakeholder and an asset-logic model representation controlled by only the stakeholder or another stakeholder; ii) a notification module for notifying only at least one of the stakeholder and the another stakeholder of a manipulation of at least one of the metadata model representation and the asset-logic model representation; iii) a recording module for recording each manipulation approved or rejected by the at least one of the stakeholder and the another stakeholder; and iv) a transformation module for transforming the system model by correlating only each approved manipulation between the meta-data model representation and the asset-logic model representation.. Attorney Docket No. 33849-270
[0011] Additional aspects, advantages and embodiments of the invention will become apparent to those skilled in the art from the following description of the various embodiments and related drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The present invention is described below with references to the accompanying drawings in which like elements are referenced with like reference numerals, and in which:
[0013] FIG. 1 is a block diagram illustrating a system for implementing the present invention.
[0014] FIG. 2 illustrates the collaborative network matrix model of the present invention in relation to a wider system for collaboration.
[0015] FIG. 3 is a block diagram illustrating the collaborative network matrix model in FIG. 2.
[0016] FIG. 4 is a block diagram illustrating the collaborative network matrix model in FIG. 2 after a system change.
[0017] FIG. 5 is a block diagram illustrating the collaborative network matrix model in FIG. 2 as a transformation.
[0018] FIG. 6 illustrates the development and change of a collaborative network matrix model over time.
[0019] FiG. 7 is a flow diagram illustrating one embodiment of a method for implementing the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0020] The subject matter of the present invention is described with specificity, however, the description itself is not intended to limit the scope of the invention. The subject matter thus, might also be embodied in other ways, to include different steps or combinations of steps similar to the ones described herein, in conjunction with other present or future Attorney Docket No. 33849-270
technologies. Moreover, although the term "step" may be used herein to describe different elements of methods employed, the term should not be interpreted as implying any particular order among or between various steps herein disclosed unless otherwise expressly limited by the description to a particular order. While the following description refers to the oil and gas industry, the systems and methods of the present invention are not limited thereto and may also be applied to other industries to achieve similar results.
[0021] The present invention provides a model based solution to select the appropriate level of model detail for the preferences of dissimilar users, also referred to herein as clients or stakeholders. Unlike the prior art, the present invention correlates different models. Thus, the present invention permits moving between models with different levels of detail. Moreover, while different models with various levels of detail may be known in the art, the present invention, instead, provides the opportunity to utilize different models in a single application with each model related to a common system model.
System Description
[0022] The present invention may be implemented through a computer-executable program of instructions, such as program modules, generally referred to as software applications or application programs executed by a computer. The software may include, for example, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. The software forms an interface to allow a computer to react according to a source of input. DecisionSpace®, which is a commercial software application marketed by Landmark Graphics Corporation, may be used as an interface application to implement the present invention. The software may also cooperate with other code segments to initiate a variety of tasks in response to data received in conjunction with the source of the received data. The software may be stored and/or carried on any variety of memory media such as CD-ROM, magnetic disk, bubble memory and Attorney Docket No. 33849-270
semiconductor memory (e.g., various types of RAM or ROM). Furthermore, the software and its results may be transmitted over a variety of carrier media such as optical fiber, metallic wire, free space and/or through any of a variety of networks such as the Internet.
[0023] Moreover, those skilled in the art will appreciate that the invention may be practiced with a variety of computer-system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable-consumer electronics, minicomputers, mainframe computers, and the like. Any number of computer-systems and computer networks are acceptable for use with the present invention. The invention may be practiced in distributed-computing environments where tasks are performed by remote- processing devices that are linked through a communications network. In a distributed- computing environment, program modules may be located in both local and remote computer-storage media including memory storage devices. The present invention may therefore, be implemented in connection with various hardware, software or a combination thereof, in a computer system or other processing system.
[0024] Referring now to FIG. 1, a block diagram of a system for implementing the present invention on a computer is illustrated. The system includes a computing unit, sometimes referred to as a computing system, which contains memory, application programs, a client interface, and a processing unit. The computing unit is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention.
[0025] The memory primarily stores the application programs, which may also be described as program modules containing computer-executable instructions, executed by the computing unit for implementing the present invention described herein and illustrated in FIGS. 2-7. The memory therefore, includes a CNMM Module, which enables the method illustrated and described in reference to FIG. 7. The CNMM Module includes a Attorney Docket No. 33849-270
collaborative-network-matrix model, also known as a system model, which is illustrated and described in reference to FIGS, 2-7. The CNMM Module also may interact with DecisionSpace®, AssetObserver™, AssetSolverπu and AssetConnect™ as further described in reference to FIG. 2. The systems and methods of the present invention are thus, based on a system model that correlates meta-data-model representations of a production asset with the various asset-logic model representations (or taxonomies) to provide a collaborative, consistent, and relevant representation of the asset to the different stakeholders. The system model performs the correlations between different meta-data model representations using the various asset-logic model representations for common data items and attributes shared across the system thus, addressing the many key activities relating to the asset that may have different meta-model representations representing their pertinent data requirements. In this manner, effective interoperability is achieved.
[0026] Although the computing unit is shown as having a generalized memory, the computing unit typically includes a variety of computer readable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. The computing system memory may include computer storage media in the form of volatile and/or nonvolatile memory such as a read only memory (ROM) and random access memory (RAM). A basic input/output system (BIOS), containing the basic routines that help to transfer information between elements within the computing unit, such as during start-up, is typically stored in ROM. The RAM typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by the processing unit. By way of example, and not limitation, the computing unit includes an operating system, application programs, other program modules, and program data.
[0027] The components shown in the memory may also be included in other removable/nonremovable, volatile/nonvolatile computer storage media. For example only, a Attorney Docket No. 33849-270
hard disk drive may read from or write to nonremovable, nonvolatile magnetic media, a magnetic disk drive may read from or write to a removable, non-volatile magnetic disk, and an optical disk drive may read from or write to a removable, nonvolatile optical disk such as a CD ROM or other optical media. Other removable/non-removable, volatile/non-volatile computer storage media that can be used in the exemplary operating environment may include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The drives and their associated computer storage media discussed above therefore, store and/or carry computer readable instructions, data structures, program modules and other data for the computing unit.
[0028] A client may enter commands and information into the computing unit through the client interface, which may be input devices such as a keyboard and pointing device, commonly referred to as a mouse, trackball or touch pad. Input devices may include a microphone, joystick, satellite dish, scanner, or the like.
[0029] These and other input devices are often connected to the processing unit through the client interface that is coupled to a system bus, but may be connected by other interface and bus structures, such as a parallel port or a universal serial bus (USB). A monitor or other type of display device may be connected to the system bus via an interface, such as a video interface. In addition to the monitor, computers may also include other peripheral output devices such as speakers and printer, which may be connected through an output peripheral interface.
[0030] Although many other internal components of the computing unit are not shown, those of ordinary skill in the art will appreciate that such components and their interconnection are well known.
[0031] Referring now to FIG. 2, a collaborative-network-matrix model (system model 214) is illustrated within a wider system 200 for collaboration among multiple clients Attorney Docket No. 33849-270
referred to as stakeholders 218. Additional system components typically associated with a production asset may include, for example, different types of data 202 (e.g. operations data, business data and engineering data), a data analytics engine 204, a data integration platform 206, a data environment 208, a workflow integration platform 210, a software applications environment 212 and a collaborative environment 216. The various components of the system 200 enable specific inter-related functions and therefore, must interact with each other seamlessly in order to avoid discontinuities and/or errors. The role of the system model 214 is to provide interoperability across the various diverse applications and datasets within the overall system 200. Thus, the system model 214 functions as a common base model for collaboration among the stakeholders 218. Other components of the system 200 may include interfaces to and from an Enterprise Resource Planning System (e.g. SAP) or a computerized Maintenance Management System, or a computerized Work Management System controlling work in the physical asset and necessary status of equipment and system isolations.
[0032] The data analytics engine 204 allows data to be manipulated to produce numerous reports and analysis using simple to complex proprietary and industry standard algorithms. It typically supports data filtering and cleaning as well as appropriate visualization technologies to present data in meaningful, relevant and insightful ways into the viewing or collaborative environment 216 for use by the stakeholders 218.
[0033] The data integration platform 206 typically provides data connectors appropriate to each data language and database. This component allows the stakeholders 218 to map to particular data sets such as asset equipment tags or unique well identifiers, thus enabling data flow throughout the system 200.
[0034] The data environment 208 typically interfaces with some regulatory or distributed control system incorporating data to and from instruments, meters, and control devices, such as actuators, valves and the like, across the asset. Considering the typical Attorney Docket No. 33849-270
functions of each component, the data environment 208 typically includes multiple types of data 202, each designed to best suit particular types of data. For example, a relational database for business data, a data historian for high frequency operations data and a data warehouse for engineering data such as well tables and production allocation tables. The data will exist in one or more data languages, such as, for example, OPC, ODBC, HTML, WITSML, and PRODML, which are well known in the art and conform to respective corresponding data standards.
[0035] The workflow integration and orchestration platform 210 spans the various IT operating environments, connects to the numerous software applications, maps to the respective data tags and items used by the software applications and interfaces with some viewing or shared collaborative environments to interface and interact with numerous stakeholders 218 involved across the workflows. The workflows are numerous but might include frequent and infrequent activities such as; for example, well test validation, production allocation, production surveillance, production optimization and others more particularly described in U.S. Patent Application Serial No. 12/266,766, which is incorporated herein by reference.
[0036] The software applications environment(s) 212 includes different IT operating environments such as Windows and Linux, appropriate to the range of applications used across the asset. The software applications environment(s) 212 may also include well known, proprietary applications for providing diverse, complex, and relatively simple functionality. These applications, for example, may include petro-technical and geoscience applications common to the industry as well as more common software applications commonly used such as MS Office. These applications may also be used for, but not limited to, reservoir and well simulation, modeling of hydraulic networks and facilities systems, material balance, nodal analysis, production allocation, production surveillance, hydrocarbon accounting, regulatory Attorney Docket No. 33849-270
reporting, and economics. These applications may be proprietary or customized and will invariably incorporate and use a multitude of algorithms, units, and annotations. These applications will also manipulate and transform existing data and generate further data in ways unique to the applications.
[0037] The function of the system model 214 is to manage the numerous interfaces and interactions between the data items and their correct and consistent usage within the various logic schemes that are representative of the system 200 and its architecture. It does so in a dynamic operating environment where all or many of the components may be used simultaneously and/or continuously by the stakeholders 218, which may be given specific and varying access and authority rights to control the components.
[0038] The collaborative environment 216 typically represents a web-based (intranet or internet) access and viewing environment that can be used by a diverse range of potential geographically located stakeholders 218, which will provide secure access and bandwidths appropriate to the range of data and software applications included in the system 200. The use of portals will typically allow diverse stakeholders 218 to have relevant custom views of only the information they require from the system 200 and also may provide effective communications via e-mail, instant messaging, net meetings and the like.
[0039] DecisionSpace® for Production may be used to provide the system architecture, component integration and set of functionality illustrated in FIG. 2. The system model 214, however, interacts with AssetObserverτM, AssetConnect™ and AssetSolver™ to achieve overall functionality. Assetϋbserver™ provides the data integration platform 206 and also the collaborative environment 216 for data organization and visualization within the overall system 200. AssetConnectiM provides the software application environment(s) 212 and also the workflow integration platform 210, which, together, enable orchestration or technical workflows that utilize both technical applications and related data 202. Attorney Docket No.33849-270
AssetSolver™ provides the data analytics engine 204, which is capable of handling both high volume and real-time data about operations and aggregate historical data used for engineering purposes. Each of the components jointly and separately benefit from the functionality provided by the system model 214.
[0040] Referring now to FIG. 3, a block diagram of the collaborative-network-matrix model in FIG. 2 (system model 214) is illustrated. Initially, the system model 214 is static, meaning at rest, when transformations and manipulations are not occurring. During this time period, the system model 214 acts purely as a data router - providing the flow of appropriate information to different organizational stakeholders and/or applications. The system model 214 includes several components such as the vertical coπvonents Ll-LN the horizontal components Ml-MN, transformations and manipulations.
[0041] The vertical components Ll-LN may include logical representations of the various taxonomies representative of the asset such as, for example, business logic, operations logic, engineering logic, scientific logic and organizational logic, among others. As illustrated in FIG. 3, the taxonomies include scientific logic and business logic.
[0042] The horizontal components Ml-MN are meta-data model representations of specific key activities or stakeholder domains or other manifestations of meta-data model representations appropriate to the asset such as, for example, production data, business data, engineering data and equipment data, among others. As illustrated in FIG. 3, the meta data model representations include operations, design, regulatory, meter, flow and physical network- The meta-data model representations comprise numerous data items and their attributes.
[0043] Transformations are the routines for definition, identification and correlation of data items and attributes within the meta-data model representation layers, which are shared across the various asset-logic model representations. This might include, for example, Attorney Docket No. 33849-270
algorithms, rules, units, logic and data transfer language, among others. Routines may include, for example, initial screening, searching, comparison and matching of the data items and attributes across the various components of the system model 214. Screening is an activity undertaken by proprietary software in order to identify the range of data attributes in the system model 214. Searching may involve a search engine to find the locations of such attributes and a comparison may utilize artificial intelligence (such as a neural network or expert system) in order to determine correlations and interrelationships between meta-data model representations and asset-logic model representations, across the system model 214. This function allows translation of common data items and attributes between one meta-data model representation layer and others.
[0044] Manipulations are automatically initiated at occurrence of an event and may include, for example: a) the various and multiple uses of data items and attributes across the asset by the multiple stakeholders using the diverse data sources, applications and programs common to a production asset, b) the control or subsequent change of those relatively static asset-logic model representations and meta-data model representations and/or the correlations or attributes of data items therein such as, for example: i) a permanent or temporary physical change to the production system configuration by insertion or removal of an item of equipment, ii) a change on the organization structure and/or individuals in a given role or to their approval authority or iii) modification to an engineering algorithm, and c) the control or subsequent change of the asset-logic model representations, the meta-data model representations and/or the correlations or attributes of data items therein such as, for example: i) a change to a valve brought about by, and consistent with, well testing operations or shutdown of an item of equipment for planned maintenance routines, or ii) the routine change to a modeled asset component, such as an inflow production ratio (IPR) curve, used routinely by production engineering. Attorney Docket No. 33849-270
[0045] Referring now to FIG. 4, a block diagram of the collaborative-network-matrix model in FIG. 2 (system model 214) is illustrated after a system change. A first stakeholder such as, for example, a production engineer may manipulate several horizontal components to reflect a system change that has occurred. In other words, a system change reflects a manipulation of the operations, flow and physical network meta-data model representations.
[0046] Referring now to FIG. 5, a block diagram of the collaborative-network-matrix model in FIG= 2 (system model 214) is illustrated as a transformation. Between each horizontal component and across the asset-logic model representations (vertical components), proprietary transformation routines are applied to appropriately account for the first stakeholder's manipulation-resulting in a system change across the system model 214. A change in any horizontal component may also effect change to other horizontal components and/or vertical components affected by. the change, subject to agreement and approval of the designated owner (stakeholder) in control of the impacted logic, meta-data model representation or data item. Variable data attributes will not initiate change controls, which apply to only fixed or determined data items and attributes. The system model 214 is able to determine which stakeholder or stakeholders need to be informed of the changes to the horizontal components and/or vertical components and who initiated the change(s). This is achieved through an event notification service. The status of the components may be tracked during periods of change to ensure appropriate adjustment according to outcome of the system change controls. The system model 214 may be housed within a data repository with real time audit control. This mechanism is utilized to track component changes. Components of the system model 214 may be designated more or less critical at the establishment of the system model 214 such that risk can be determined and communicated with alerts to the system stakeholders. The system model 214 may record rejected and approved changes and Attorney Docket No.33849-270
effect resulting necessary transformations across the system model 214. Approval's are generated either by human interaction with the system or by a logic based expert system.
[0047] Referring now to FIG. 6, the development and change of a collaborative network matrix model over time is illustrated. Each iterative change is captured by the system and is fully auditable. Changes can include changes to stakeholders, asset-logic model representations, meta-data model representations and/or data items and attributes.
Method Description
[0048] Referring now to FIG. 7, a flow diagram illustrates one embodiment of a method 700 for implementing the present invention.
[0049] In step 702, a system model is created, which comprises one or more metadata model representations and one or more asset-logic model representations. The system model may include, for example, the same meta-data model representations and/or asset logic model representations described in reference to FIGS. 2-5. Furthermore, the system model may operate, for example, in the same manner as the system model described in reference to FIGS. 1-6. Each meta-data model representation may be controlled by one or more respective stakeholders and each asset-logic model representation may be controlled (owned) by one or more respective stakeholders. In other words, each meta-data model representation may be controlled by a respective stakeholder and each asset-logic model representation may be controlled by a respective stakeholder. Optionally, any respective stakeholder may control more than one meta-data model representation and/or more than one asset-logic model representation. Conversely, each meta-data model representation and each asset-logic model representation should not be controlled by more than one respective stakeholder however, may be controlled by more than one stakeholder under exceptional circumstances. Each meta-data model representation may include at least one data item and an attribute. Likewise, each asset-logic model representation may include at least one data item and an attribute. Attorney Docket No. 33849-270
[0050] In step 704, the system model is manipulated using a GUI or other means well known in the art. A collaborative environment and/or API may be utilized within a wider system to facilitate manipulation of the system model. The system model may be manipulated, for example, by a manipulation of one or more of the meta-data model representations and/or one or more of the asset-logic model representations. A manipulation therefore, may represent a change to at least one of the meta-data model representations and the asset-logic model representations. The system model may be manipulated on a computer system by any stakeholder. Each stakeholder therefore, may access the system model through a collaborative environment to manipulate the system model on the computer system. Each stakeholder therefore, may control one or more meta-data model representations and/or asset-logic model representations, while having access to the system model through a collaborative environment for purposes of manipulating the system model. Each stakeholder however, having access to the system model through a collaborative environment for purposes of manipulating the system model may not have control of one or more meta-data model representations and/or asset-logic model representations.
[0051] In step 706, each stakeholder in control of the one or more meta-data model representations and/or the one or more asset-logic model representations is notified of a manipulation of each respective meta-data model representation and/or each respective asset- logic model representation controlled by each respective stakeholder. A collaborative environment and/or API may be utilized within a wider system to facilitate notification of each manipulation. In this manner, for example, a stakeholder may manipulate one or more of the meta-data model representations and/or one or more of the asset-logic model representations, which it does not control, and only each stakeholder in control of each respective manipulated meta-data model representation and/or asset-logic model representation is notified of the manipulation. Attorney Docket No. 33849-270
[0052] In step 708, each manipulation approved or rejected by each respective stakeholder in control of the manipulated meta-data model representation(s) and/or asset- logic model representation(s) is recorded by the system model. Each approved manipulation therefore, may represent a change to a data item and/or an attribute in one or more of the meta-data model representations and/or one or more of the asset-logic model representations.
[0053] In step 710, the system model is transformed on a computer system based on the approved manipulation(s) by correlating each approved manipulation between the metadata model representation(s) and the asset-logic model representation(s). Transforming the system model comprises using at least one routine for correlating each approved manipulation between the meta-data model representation(s) and the asset-logic model representation(s) .
[0054] hi step 712, the method 700 determines whether to repeat. If the method 700 is repeated, then the method 700 proceeds to step 704. If the method 700 does not repeat, then the method 700 ends.
[0055] The system model may be deployed in conjunction with a production allocation application whereby data pertaining to allocation changes to the production system might be more readily identified and for differing purposes such as technically correct allocation and fiscal allocation for operations, engineering and/or business uses. Other applications utilizing the system modei may include, for example, production loss reporting, whereby the various causes of lost production might be attributed as they are reported, understood and associated with relevant operations, engineering and business data and uses.
[0056] While the present invention has been described in connection with presently preferred embodiments, it will be understood by those skilled in the art that it is not intended to limit the invention to those embodiments. It is therefore, contemplated that various alternative embodiments and modifications may be made to the disclosed embodiments Attorney Docket No.33849-270
without departing from the spirit and scope of the invention defined by the appended claims and equivalents thereof.

Claims

Attorney Docket No. 33849-270CLAIMS
1. A computer implemented method for correlating meta-data model representations and asset-logic model representations, comprising: manipulating a system model, the system model comprising a meta-data model representation controlled by only a stakeholder and an asset-logic model representation controlled by only the stakeholder or another stakeholder; notifying only at least one of the stakeholder and the another stakeholder of a manipulation of at least one of the meta-data model representation and the asset-logic model representation; recording each manipulation approved or rejected by the at least one of the stakeholder and the another stakeholder; and transforming the system model on a computer system by correlating only each approved manipulation between the meta-data model representation and the asset-logic model representation.
2. The method of claim 1, wherein the manipulation of the at least one of the meta-data model representation and the asset-logic model representation represents a change to at least one of the meta-data model representation and the asset-logic model representation.
3. The method of claim 2, wherein the meta-data model representation comprises at least one of a data item and an attribute, and the asset-logic model representation comprises at least one of the data item and the attribute.
4. The method of claim 1, wherein transforming the system model comprises using at least one routine for correlating each approved manipulation between the meta-data model representation and the asset-logic model representation.
5. The method of claim 1, wherein each approved manipulation of the at least one of the
20 Attorney Docket No. 33849-270
meta-data model representation and the asset-logic model representation represents a change to at least one of a data item and an attribute in at least one of the meta-data model representation and the asset-logic model representation.
6. The method of claim 1, further comprising: manipulating the system model, the system model comprising another meta-data model representation controlled by only a new stakeholder and another asset-logic model representation controlled by only the new stakeholder or another new stakeholder; notifying only at least one of the stakeholder, the another stakeholder, the new stakeholder and the another new stakeholder of a manipulation of at least one of the meta-data model representation, the asset-logic model representation, the another meta-data model representation and the another asset-logic model representation; recording each manipulation approved or rejected by the at least one of the stakeholder, the another stakeholder, the new stakeholder and the another new stakeholder; and transforming the system model by correlating only each approved manipulation between the meta-data model representation, the another meta-data model representation, the asset-logic model representation, and the another assεt- logic model representation.
7. The method of claim 1, wherein the system model is manipulated by a new stakeholder and only the stakeholder is notified of a manipulation of the meta-data model representation and only the stakeholder or the another stakeholder is notified of a manipulation of the asset-logic model representation.
8. The method of claim 1, wherein the system model is manipulated on the computer
21 Attorney Docket No.33849-270
system by a new stakeholder.
9. The method of claim 8, wherein the stakeholder, the another stakeholder and the new stakeholder access the system model through a collaborative environment.
10. A program carrier device for carrying computer executable instructions for correlating meta-data model representations and asset-logic model representations, the instructions being executable to implement: manipulating a system model, the system model comprising a meta-data model representation controlled by only a stakeholder and an asset-logic model representation controlled by only the stakeholder or another stakeholder; notifying only at least one of the stakeholder and the another stakeholder of a manipulation of at least one of the meta-data model representation and the asset-logic model representation; recording each manipulation approved or rejected by the at least one of the stakeholder and the another stakeholder; and transforming the system model by correlating only each approved manipulation between the meta-data model representation and the asset-logic model representation.
11. The program carrier device of claim 10, wherein the manipulation of the at least one of the meta-data model representation and the asset-logic model representation represents a change to at least one of the meta-data model representation and the asset-logic model representation.
12. The program carrier device of claim 11? wherein the meta-data model representation comprises at least one of a data item and an attribute, and the asset-logic model representation comprises at least one of the data item and the attribute.
13. The program carrier device of claim 10, wherein transforming the system model
22 Attorney Docket No. 33S49-270
comprises using at least one routine for correlating each approved manipulation between the meta-data model representation and the asset-logic model representation.
14. The program carrier device of claim 10, wherein each approved manipulation of the at least one of the meta-data model representation and the asset-logic model representation represents a change to at least one of a data item and an attribute in at least one of the meta-data model representation and the asset-logic model representation.
15. The program carrier device of claim 10, further comprising: manipulating the system model, the system model comprising another meta-data model representation controlled by only a new stakeholder and another asset-logic model representation controlled by only the new stakeholder or another new stakeholder; notifying only at least one of the stakeholder, the another stakeholder, the new stakeholder and the another new stakeholder of a manipulation of at least one of the meta-data model representation, the asset-logic model representation, the another meta-data model representation and the another asset-logic model representation; recording each manipulation approved or rejected by the at least one of the
new stakeholder; and transforming the system model by correlating only each approved manipulation between the meta-data model representation, the another meta-data model representation, the asset-logic model representation, and the another asset- logic model representation.
16. The program carrier device of claim 10, wherein the system model is manipulated by
23 Attorney Docket No. 33849-270
a new stakeholder and only the stakeholder is notified of a manipulation of the metadata model representation and only the stakeholder or the another stakeholder is notified of a manipulation of the asset-logic model representation.
17. The program carrier device of claim 10, wherein the system model is manipulated by a new stakeholder.
18. The program carrier device of claim 17, wherein the stakeholder, the another stakeholder and the new stakeholder access the system model through a collaborative environment.
19. A computer system for correlating meta-data model representations and asset- logic model representations, comprising: a system model, the system model comprising a meta-data model representation controlled by only a stakeholder and an asset-logic model representation controlled by only the stakeholder or another stakeholder; a notification module for notifying only at least one of the stakeholder and the another stakeholder of a manipulation of at least one of the meta-data model representation and the asset-logic model representation; a recording module for recording each manipulation approved or rejected by the at least one of the stakeholder and the another stakeholder; and a transformation module for transforming the system model by correlating only each approved manipulation between the meta-data model representation and the asset-logic model representation.
20. The computer system of claim 19, wherein the system model is manipulated on the computer system by a new stakeholder and the stakeholder, the another stakeholder and the new stakeholder access the system model through a collaborative environment.
24
PCT/US2009/039480 2008-04-04 2009-04-03 Systems and methods for correlating meta-data model representations and asset-logic model representations WO2009124256A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CN200980112469.1A CN101990659B (en) 2008-04-04 2009-04-03 Systems and methods for correlating meta-data model representations and asset-logic model representations
BRPI0906540A BRPI0906540A2 (en) 2008-04-04 2009-04-03 devices and methods for correlating metadata model representations and logical model representations of assets
CA2719937A CA2719937C (en) 2008-04-04 2009-04-03 Systems and methods for correlating meta-data model representations and asset-logic model representations
MX2010010785A MX2010010785A (en) 2008-04-04 2009-04-03 Systems and methods for correlating meta-data model representations and asset-logic model representations.
AU2009231624A AU2009231624B2 (en) 2008-04-04 2009-04-03 Systems and methods for correlating meta-data model representations and asset-logic model representations
EP09727609.1A EP2266021A4 (en) 2008-04-04 2009-04-03 Systems and methods for correlating meta-data model representations and asset-logic model representations

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US4254208P 2008-04-04 2008-04-04
US61/042,542 2008-04-04

Publications (1)

Publication Number Publication Date
WO2009124256A1 true WO2009124256A1 (en) 2009-10-08

Family

ID=41134217

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/039480 WO2009124256A1 (en) 2008-04-04 2009-04-03 Systems and methods for correlating meta-data model representations and asset-logic model representations

Country Status (8)

Country Link
US (2) US8229938B2 (en)
EP (1) EP2266021A4 (en)
CN (1) CN101990659B (en)
AU (1) AU2009231624B2 (en)
BR (1) BRPI0906540A2 (en)
CA (1) CA2719937C (en)
MX (1) MX2010010785A (en)
WO (1) WO2009124256A1 (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10552391B2 (en) 2008-04-04 2020-02-04 Landmark Graphics Corporation Systems and methods for real time data management in a collaborative environment
WO2009124256A1 (en) 2008-04-04 2009-10-08 Landmark Graphics Corporation, A Halliburton Company Systems and methods for correlating meta-data model representations and asset-logic model representations
US9191266B2 (en) 2012-03-23 2015-11-17 Petrolink International System and method for storing and retrieving channel data
US9518459B1 (en) 2012-06-15 2016-12-13 Petrolink International Logging and correlation prediction plot in real-time
US9512707B1 (en) 2012-06-15 2016-12-06 Petrolink International Cross-plot engineering system and method
US9460403B2 (en) 2012-07-31 2016-10-04 Landmark Graphics Corporation Methods and systems related to hydrocarbon recovery strategy development
US10590761B1 (en) 2013-09-04 2020-03-17 Petrolink International Ltd. Systems and methods for real-time well surveillance
US10428647B1 (en) 2013-09-04 2019-10-01 Petrolink International Ltd. Systems and methods for real-time well surveillance
US10614048B2 (en) 2013-09-20 2020-04-07 Oracle International Corporation Techniques for correlating data in a repository system
CN105940417A (en) 2014-02-26 2016-09-14 界标制图有限公司 Production engineering networks
CN107315776B (en) * 2017-05-27 2020-06-23 国网安徽省电力公司信息通信分公司 Data management system based on cloud computing

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030050807A1 (en) 2001-03-23 2003-03-13 Restaurant Services, Inc. System, method and computer program product for a gas station supply chain management framework
US20030188863A1 (en) * 2002-04-05 2003-10-09 Eugene Hooper And Britt Gilbert Carbon dioxide pipeline

Family Cites Families (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5710918A (en) 1995-06-07 1998-01-20 International Business Machines Corporation Method for distributed task fulfillment of web browser requests
US5745754A (en) 1995-06-07 1998-04-28 International Business Machines Corporation Sub-agent for fulfilling requests of a web browser using an intelligent agent and providing a report
US5930786A (en) 1995-10-20 1999-07-27 Ncr Corporation Method and apparatus for providing shared data to a requesting client
US5821925A (en) 1996-01-26 1998-10-13 Silicon Graphics, Inc. Collaborative work environment supporting three-dimensional objects and multiple remote participants
US6425016B1 (en) 1997-05-27 2002-07-23 International Business Machines Corporation System and method for providing collaborative replicated objects for synchronous distributed groupware applications
US6621505B1 (en) 1997-09-30 2003-09-16 Journee Software Corp. Dynamic process-based enterprise computing system and method
US6338086B1 (en) 1998-06-11 2002-01-08 Placeware, Inc. Collaborative object architecture
US6304864B1 (en) 1999-04-20 2001-10-16 Textwise Llc System for retrieving multimedia information from the internet using multiple evolving intelligent agents
US7698160B2 (en) 1999-05-07 2010-04-13 Virtualagility, Inc System for performing collaborative tasks
US6678882B1 (en) 1999-06-30 2004-01-13 Qwest Communications International Inc. Collaborative model for software systems with synchronization submodel with merge feature, automatic conflict resolution and isolation of potential changes for reuse
US6266619B1 (en) 1999-07-20 2001-07-24 Halliburton Energy Services, Inc. System and method for real time reservoir management
US6853921B2 (en) 1999-07-20 2005-02-08 Halliburton Energy Services, Inc. System and method for real time reservoir management
US6539396B1 (en) 1999-08-31 2003-03-25 Accenture Llp Multi-object identifier system and method for information service pattern environment
MXPA02003545A (en) 1999-10-08 2002-10-23 Schlumberger Technology Corp Training method using industry and university collaboration.
US6826483B1 (en) 1999-10-13 2004-11-30 The Trustees Of Columbia University In The City Of New York Petroleum reservoir simulation and characterization system and method
AU1928701A (en) 1999-11-22 2001-06-04 Accenture Llp Technology sharing during asset management and asset tracking in a network-basedsupply chain environment and method thereof
US6980940B1 (en) 2000-02-22 2005-12-27 Schlumberger Technology Corp. Intergrated reservoir optimization
US6792431B2 (en) 2001-05-07 2004-09-14 Anadarko Petroleum Corporation Method, system, and product for data integration through a dynamic common model
US8412746B2 (en) 2001-05-25 2013-04-02 International Business Machines Corporation Method and system for federated querying of data sources
US7673282B2 (en) 2001-05-25 2010-03-02 International Business Machines Corporation Enterprise information unification
US20030033179A1 (en) 2001-08-09 2003-02-13 Katz Steven Bruce Method for generating customized alerts related to the procurement, sourcing, strategic sourcing and/or sale of one or more items by an enterprise
GB0123403D0 (en) 2001-09-28 2001-11-21 Tamesis Ltd Publish subscribe system
US7424473B2 (en) * 2001-12-26 2008-09-09 Centricmedia, Inc. System and method for asset tracking with organization-property-individual model
US7043521B2 (en) 2002-03-21 2006-05-09 Rockwell Electronic Commerce Technologies, Llc Search agent for searching the internet
US7987491B2 (en) 2002-05-10 2011-07-26 Richard Reisman Method and apparatus for browsing using alternative linkbases
US7243093B2 (en) 2002-11-27 2007-07-10 International Business Machines Corporation Federated query management
US7146356B2 (en) 2003-03-21 2006-12-05 International Business Machines Corporation Real-time aggregation of unstructured data into structured data for SQL processing by a relational database engine
US20040230571A1 (en) 2003-04-22 2004-11-18 Gavin Robertson Index and query processor for data and information retrieval, integration and sharing from multiple disparate data sources
US7269607B2 (en) 2003-09-29 2007-09-11 International Business Machines Coproartion Method and information technology infrastructure for establishing a log point for automatic recovery of federated databases to a prior point in time
US7287048B2 (en) 2004-01-07 2007-10-23 International Business Machines Corporation Transparent archiving
BRPI0513195A (en) 2004-07-09 2008-04-29 Matsushita Electric Ind Co Ltd systems for administering user authentication and authorization, and for user support, methods for administering user authentication and authorization, for accessing services from multiple networks, for the authentication controller to process an authentication request message, to select the combination of authentication controllers. search result authentication, authenticating a user, and finding the way to a domain having business relationship with the home domain, for the authorization controller to process the service authorization request message, and perform service authorization for a domain controller. authentication and authorization perform authentication and service authorization, to protect the user token, and for the user's home domain access control authority to provide the authentication controller with a limited user signature profile information, to achieve authentication and authorize fast access, and to achieve single registration to access multiple networks, and formats for subscription capability information, for a user symbol, for a domain having business relationship with a user's home domain to request authentication and authorization assertion , and for a user terminal to indicate their credentials for accessing multiple networks across multiple administrative domains.
US7707249B2 (en) 2004-09-03 2010-04-27 Open Text Corporation Systems and methods for collaboration
US20060074980A1 (en) 2004-09-29 2006-04-06 Sarkar Pte. Ltd. System for semantically disambiguating text information
US7461052B2 (en) 2004-12-06 2008-12-02 International Business Machines Corporation Abstract query plan
US20060167868A1 (en) * 2005-01-27 2006-07-27 Weijia Zhang Universal and extensible packaging process for computer system software integration and deployment
US7610264B2 (en) 2005-02-28 2009-10-27 International Business Machines Corporation Method and system for providing a learning optimizer for federated database systems
US7469248B2 (en) 2005-05-17 2008-12-23 International Business Machines Corporation Common interface to access catalog information from heterogeneous databases
FR2886030B1 (en) 2005-05-19 2007-08-10 Airbus Sas METHOD AND DEVICE FOR GENERATING A PARAMETRIC MODEL RELATING TO 3D GEOMETRY
US20070073674A1 (en) 2005-09-26 2007-03-29 Bea Systems, Inc. System and method for providing federated events for content management systems
CA2524527A1 (en) 2005-10-26 2007-04-26 Ibm Canada Limited - Ibm Canada Limitee Systems, methods and tools for facilitating group collaborations
US7984389B2 (en) 2006-01-28 2011-07-19 Rowan University Information visualization system
US7523118B2 (en) 2006-05-02 2009-04-21 International Business Machines Corporation System and method for optimizing federated and ETL'd databases having multidimensionally constrained data
US7865487B2 (en) 2006-07-14 2011-01-04 Raytheon Company System and method for providing remote access to events from a database access system
US8572633B2 (en) 2006-07-31 2013-10-29 Sap Ag Exception handling for collaborating process models
US7580946B2 (en) 2006-08-11 2009-08-25 Bizweel Ltd. Smart integration engine and metadata-oriented architecture for automatic EII and business integration
US8527502B2 (en) 2006-09-08 2013-09-03 Blade Makai Doyle Method, system and computer-readable media for software object relationship traversal for object-relational query binding
US7933921B2 (en) 2006-11-29 2011-04-26 Netapp, Inc. Referent-controlled location resolution of resources in a federated distributed system
US8250583B2 (en) 2006-12-04 2012-08-21 International Business Machines Corporation Workflow processing system and method with federated database system support
US8136124B2 (en) 2007-01-18 2012-03-13 Oracle America, Inc. Method and apparatus for synthesizing hardware counters from performance sampling
US7519503B2 (en) 2007-02-15 2009-04-14 Epsis As Data handling system
US20080255892A1 (en) 2007-04-11 2008-10-16 The University Of Southern California System and Method for Oil Production Forecasting and Optimization in a Model-Based Framework
CN102007504A (en) 2007-11-10 2011-04-06 兰德马克绘图国际公司,哈里伯顿公司 Systems and methods for workflow automation, adaptation and integration
US10552391B2 (en) 2008-04-04 2020-02-04 Landmark Graphics Corporation Systems and methods for real time data management in a collaborative environment
WO2009124256A1 (en) 2008-04-04 2009-10-08 Landmark Graphics Corporation, A Halliburton Company Systems and methods for correlating meta-data model representations and asset-logic model representations

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030050807A1 (en) 2001-03-23 2003-03-13 Restaurant Services, Inc. System, method and computer program product for a gas station supply chain management framework
US20030188863A1 (en) * 2002-04-05 2003-10-09 Eugene Hooper And Britt Gilbert Carbon dioxide pipeline

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2266021A4 *

Also Published As

Publication number Publication date
MX2010010785A (en) 2010-11-09
CA2719937C (en) 2017-03-28
BRPI0906540A2 (en) 2015-09-22
AU2009231624A1 (en) 2009-10-08
US8554778B2 (en) 2013-10-08
CN101990659A (en) 2011-03-23
US8229938B2 (en) 2012-07-24
EP2266021A1 (en) 2010-12-29
US20100005111A1 (en) 2010-01-07
EP2266021A4 (en) 2014-01-01
AU2009231624B2 (en) 2014-07-03
CA2719937A1 (en) 2009-10-08
US20120323943A1 (en) 2012-12-20
CN101990659B (en) 2014-08-20

Similar Documents

Publication Publication Date Title
US8554778B2 (en) Systems and methods for correlating meta-data model representations and asset-logic model representations
AU2010222952B2 (en) Systems and methods for real time data management in a collaborative environment
US9536225B2 (en) Aggregating business analytics architecture and configurator
CA2858060A1 (en) System for collaboration and meeting management
US20050267771A1 (en) Apparatus, system and method for integrated lifecycle management of a facility
Onggo Symbiotic simulation system (S3) for industry 4.0
AU2014233592B2 (en) Systems and methods for correlating meta-data model representations and asset-logic model representations
US7822796B2 (en) Method and system for electronically qualifying supplier parts
AU2013200561B2 (en) Systems and methods for real time data management in a collaborative environment
Kuryanti et al. Company Asset Management Information System (Case Study: Branch Office Bpjs Ketenakerjaan, Bogor)
Möller Continuous simulation in material flow networks
Green Configuration Management-An Automated Solution
Neely et al. SYNERGE: A Tool for Managing System Engineering Information

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980112469.1

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09727609

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2719937

Country of ref document: CA

Ref document number: 2009231624

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: MX/A/2010/010785

Country of ref document: MX

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2009727609

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2009727609

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2009231624

Country of ref document: AU

Date of ref document: 20090403

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: PI0906540

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20101004