Enterprise-wide data standardization structure and method

• US 20080288269A1
• Filed: 05/18/2007
• Published: 11/20/2008
• Est. Priority Date: 05/18/2007
• Status: Abandoned Application

• Current Assignee: Siemens Energy Incorporated (Siemens AG)
• Original Assignee: Siemens Power Generation, Inc.
• Inventors: Herwig, Volker
• Application Number:
  US11/804,403
• Publication Number:
  US 20080288269A1
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/0633 Workflow analysis

Abstract

A method and structure for data standardization as a basis for a service-oriented architecture in an enterprise. A logical business model (30) defines processes and organization of an enterprise. An implementation model (40) defines an information technology to support the business model (30). Standard core language elements (60) communicate and transition reliably between the business and implementation models, and are understandable in the same way by all responsible parties in a business. Business object types (60) and technical term models (66) define core elements with semantics, synonyms, and interrelationships of this standard language. The models (30, 40) as encoded in a database coordinate the parties and departments in implementing a product life cycle in the enterprise.

Claims

1. A data structure embodied in a computer-readable medium, comprising:

a logical business model that defines processes and organization of an enterprise;

an implementation model that defines an information technology supporting the business model;

a plurality of business object types that define core elements of the business model and the implementation model;

a plurality of business objects, each comprising an instance of one of the business object types;

a data structure embodied in a computer database that stores a representation of the business model, the implementation model, and, for each of the business object types, a business object type definition and respective business objects or instantiations of the business object type, the database accessible to a plurality of departments in an enterprise;

the data structure and the database defining structural and functional interrelationships between the business model and the implementation model via logical and physical linkages among the business object types and the models; and

wherein human-readable representations of structured data from the database coordinate the departments in implementing a product life cycle in the enterprise.

2. The data structure of claim 1, further comprising in the business model:

a value-added chain level that models core processes in the business model, and an event-driven process chain level that models process chains in the business model.

3. The data structure of claim 2, further comprising:

a function allocation diagram linked to a function in an event-driven process chain in the event-driven process chain level to further describe the function.

4. The data structure of claim 1, wherein the business object type definition comprises a technical term model with links that indicate semantic relationships among the business object types.

5. The data structure of claim 4 wherein the definition of a given business object type comprises a primary object type name and a list of synonyms, and each synonym refers only to the given business object type without duplication of business object types for different terms of usage with the same meaning in the enterprise.

6. The data structure of claim 5, further comprising:

a logical problem domain model based on the business object types, their respective definitions, and their respective technical term models, wherein the implementation model defines and supports information technology projects conforming to the logical problem domain model.

7. A method of modeling and implementing an information technology product in a business, comprising:

creating a logical business model that defines processes and organization of an enterprise;

creating an implementation model that defines an information technology product supporting the business model;

creating a plurality of business object types that define core elements of the business model and the implementation model;

creating a computer database that stores a representation of the business model, the implementation model, and, for each of the business object types, a business object type definition and respective business objects or instantiations of the business object type, the database being accessible to a plurality of departments in an enterprise, the database defining structural and functional interrelationships between the business model and the implementation model via logical and physical linkages among the business object types; and

presenting human-readable representations of structured data from the database that coordinate the departments in implementing the information technology.

8. The method of claim 7, further comprising:

establishing multiple levels of model development comprising a value added chain modeling level that models core processes in the logical business model, and an event-driven process chain level that models process chains in the logical business model.

9. The method of claim 8, further comprising:

linking a function allocation diagram to a respective function in an event-driven process chain to further describe the function.

10. The method of claim 9, wherein the business object type definition comprises a technical term model with links that indicate semantic relationships among the business object types.

11. The method of claim 10 wherein the definition of a given business object type comprises a primary object type name and a list of synonyms, and each synonym refers only to the given business object type without duplication of business object types for different terms of usage with the same meaning in the enterprise.

12. The method of claim 11, further comprising:

creating a logical problem domain model based on the business object types, their respective definitions, and their respective technical term models, and wherein the implementation model defines and supports information technology projects conforming to the logical problem domain model.

13. The method of claim 12, further comprising developing information technologies based on the implementation model to support the processes and organization of the enterprise.