System and method for organizing and sharing of process plant design and operations data

• US 7,367,018 B2
• Filed: 10/23/2003
• Issued: 04/29/2008
• Est. Priority Date: 10/25/2002
• Status: Expired due to Fees

• Current Assignee: Aspentech Corporation
• Original Assignee: Aspen Technology (Telefonaktiebolaget LM Ericsson)
• Inventors: Ward, Peter, McBrien, Andrew, Noble, Robert G., Laing, Douglas M.
• Primary Examiner(s): Zhen; Wei
• Assistant Examiner(s): Chen; Qing
• Application Number:
  US10/692,006
• Publication Number:
  US 20040133290A1
• Time in Patent Office: 1,650 Days
• Field of Search: 717100-105, 717120-123, 700/90, 700/105
• US Class Current: 717/120
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

Computer method and apparatus for managing process and plant engineering data for chemical or other engineering processes across applications. The method and apparatus include a respective class view for each of multiple software applications, a composite class view, a conceptual data model and a resulting consolidated multi-tier data model. The multi-tier data model enables sharing of engineering and other data from the multiple software applications with other process and plant engineering applications and programs. An amalgamator synthesizes the class views, composite views and conceptual data model into the multi-tier data model. In forming the multi-tier data model, there is a one-to-one mapping between an attribute in the class view and composite class view, and a one-to-one mapping between an attribute in the composite class view and a data path in the conceptual data model to corresponding software applications from which the attribute originated.

Claims

1. A computer apparatus for managing and sharing engineering data for chemical engineering processes and plants, comprising:

a digital processor;

an editor defining (i) class views and (ii) a composite class view of the defined class views, given one or more software applications of interest and each given software application having a respective data model or data view, for each said given software application, the editor providing a class view of the respective data model;

the editor consolidating said class views to form a composite class views, the consolidating of said class views resulting in the creation of said composite class view being an amalgamation and a rationalization of the individual class views, and the class views being retained in a given software application domain terminology for managing and sharing engineering data for chemical engineering processes and plants; and

a data server executed by the digital processor and instantiating a multi-tier data model, there being a core conceptual data model having a plurality of routes between attributes in the composite class view and attributes in the core conceptual data model;

the class views effectively being one tier of the multi-tier data model, the composite class view effectively being a second tier of the multi-tier data model and the core conceptual data model effectively being a third tier, the multi-tier data model having links between corresponding attributes across tiers, the multi-tier data model providing management and sharing of engineering data of the given software applications with other process and plant engineering applications, and enhancing process engineering and plant operations.

2. The computer apparatus as claimed in claim 1 further comprising an amalgamator that synthesizing the class views, composite class views and the core conceptual data model into a consolidated multi-tier data model.

3. The computer apparatus as claimed in claim 1 further comprising a mapper that links the core conceptual data model attributes to the composite class view and the composite class view attributes to class views, and provides a one-to-one mapping between an attribute in the composite class view and a route in the core conceptual data model to corresponding given software applications from which the attribute in the composite class view originated.

4. The computer apparatus as claimed in claim 3 wherein each class view is represented in terms from the respective given software application, and said given software application is able to access data from the core conceptual data model.

5. The computer apparatus as claimed in claim 1 wherein the class views, composite class views and the core conceptual data model are represented by object oriented programming elements.

6. The computer apparatus as claimed in claim 5 wherein certain object oriented programming elements are defined by classes;

and wherein

the editor enables user creation and editing of definitions of classes.

7. The computer apparatus as claimed in claim 6 wherein the editor employs an Extensible Markup Language.

8. A method of data modeling, comprising the computer implemented steps of:

(a) forming a multi-tier data model with links between corresponding attributes across tiers, a first tier being formed by;

for each of multiple given software applications of interest and having a respective data model, providing a practitioner'"'"'s view of the given software application using a respective class view of the respective data model;

a second tier being formed by consolidating class views into a composite class view, the consolidation of said class views resulting in the creation of said composite class view being an amalgamation and a rationalization of the individual class views, and the class views being retained in a given software application domain terminology for managing and sharing engineering data for chemical engineering processes and plants; and

a third tier being formed by forming a core conceptual data model having a plurality of routes between attributes in the composite class view and attributes in the core conceptual data model; and

(b) sharing, via the multi-tier data model, engineering data of the given software applications with other process and plant engineering routines, and enhancing process engineering and plant operations.

9. The method as claimed in claim 8 wherein the second tier is formed by synthesizing the class views into the composite class view.

10. The method as claimed in claim 8 wherein the step of forming a multi-tier data model further comprises producing a one-to-one mapping between an attribute in each class view to the composite class view, and a one-to-one mapping between an attribute in the composite class view and a route in the core conceptual data model to corresponding given software applications from which the attribute originated in the composite class view originated.

11. The method as claimed in claim 8 wherein the step of providing a practitioner'"'"'s view includes, in each class view, representing the respective data model in terms from the respective given software application.

12. The method as claimed in claim 8 further comprising the step of representing at least one of the class views, the composite class view and the core conceptual data model in terms of object oriented programming elements.

13. The method as claimed in claim 12 wherein certain object oriented programming elements are defined by classes;

and

enabling user creation and edition of definitions of classes.

14. The method as claimed in claim 13 wherein the step of enabling user creation and edition includes employing Extensive Markup Language interfaces.

15. A computer program product comprising:

(a) a computer readable medium that manages engineering data; and

(b) a set of computer program instructions encoded on the computer readable medium, the set of computer program instructions when executed on a computer causing the computer to;

provide a respective class view for each of plural given software applications of interest and having a respective data model, each class view being of the respective data model;

form a composite class view from the class views, the consolidation of said class views resulting in the creation of said composite class view being an amalgamation and a rationalization of the individual class views, and the class views being retained in a given software application domain terminology for managing and sharing engineering data for chemical engineering processes and plants;

form a conceptual model having a plurality of routes between attributes in the composite class view and attributes in the conceptual model;

form a consolidated multi-tier data model from the class views, the composite class view and the conceptual model, the class views effectively being one tier of the consolidated multi-tier data model, the composite class view effectively being a second tier of the consolidated multi-tier data model and the conceptual model effectively being a third tier, the consolidated multi-tier data model having links between corresponding attributes across tiers; and

via, the consolidated multi-tier data model, provide sharing of engineering data of the given software applications with other process and plant engineering applications, and enhancing process engineering and plant operations.

16. The computer program product of claim 15, wherein the consolidated multi-tier data model insulates the given software applications from changes in the conceptual model.

17. The computer program product of claim 15, wherein the consolidated multi-tier data model is insulated from changes in the given software applications.

18. The computer program product of claim 15, wherein the consolidated multi-tier data model provides an application independent and normalized data model where the composite class view is application independent.

19. The computer program product of claim 15, wherein the consolidated multi-tier data model comprises an editor and a class store, the class store providing an interface to the respective class views, the composite class view, and the conceptual model to share data between the consolidated multi-tier data model and the given software applications.

20. The computer program product of claim 19, wherein the editor and the class store use an Extensible Markup Language, and wherein the composite class view provides for the class views remaining in the given software application domain terminology.