Model-based view parts and reusable data source configurations

• US 8,566,781 B2
• Filed: 04/17/2008
• Issued: 10/22/2013
• Est. Priority Date: 04/23/2007
• Status: Active Grant

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: DeMesa, Jesse, Sjolander, Stephen, Nguyen, Thomas Ngoc, O'Heam, James Eric
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): APONTE, FRANCISCO JAVIER
• Application Number:
  US12/105,098
• Publication Number:
  US 20080263514A1
• Time in Patent Office: 2,014 Days
• Field of Search: 717105-109, 715/762, 370/396
• US Class Current: 717/104
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A first widget of a first view part associated with a component of a class model and with one or more members of the component, and a second widget of a second view part associated with the component of the class model and with the one or more members of the component are defined. A request for data associated with a first object instantiation of the component to populate the first widget is received, and a configuration is identified based on the first widget, the configuration specifying a data source, a data source interface, input parameters, and a mapping to one or more of the one or more members of the component.

Claims

1. A method comprising:

defining a first widget of a first view part associated with a component of a class model and with one or more members of the component;

defining a second widget of a second view part associated with the component of the class model and with the one or more members of the component;

providing a configuration file associated with the component, the configuration file including at least one configuration specifying a data source, a data source interface, input parameters, and a mapping to one or more of the one or more members of the component, accessible by multiple widgets in multiple different view parts for populating the widget with regard to the component with two widgets of different view parts, enabled to access the same configuration of the configuration file to retrieve data for the different view parts, as specified by the configuration, even when the data required by each view part may be different;

receiving a request for data associated with a first object instantiation of the component to populate the first widget;

identifying a configuration based on the first widget;

receiving the requested data based on the data source, the data source interface, the input parameters, and the mapping to one or more of the one or more members of the component specified by the configuration;

populating the first widget with the received data;

receiving a request for second data associated with a second object instantiation of the component to populate the second widget;

identifying the configuration based on the second widget;

receiving the requested second data based on the data source, the data source interface, the input parameters, and the mapping to one or more of the one or more members of the component specified by the configuration; and

populating the second widget with the second received data.

2. The method according to claim 1, further comprising:

defining a third widget of the first view part associated with the component of the class model and with the one or more members of the component;

receiving a request for third data associated with a third object instantiation of the component to populate the third widget;

identifying the configuration based on the third widget;

receiving the requested third data based on the data source, the data source interface, the input parameters, and the mapping to one or more of the one or more members of the component; and

populating the third widget with the received third data;

one or more of the foregoing steps being performed by a processor device executing processor-executable process steps.

3. The method according to claim 1, further comprising:

defining a third widget of the first view part associated with the component of the class model and with a second one or more members of the component;

receiving a request for third data associated with a third object instantiation of the component to populate the third widget;

identifying a second configuration based on the third widget, the second configuration specifying a second data source, a second data source interface, second input parameters, and a second mapping to one or more of the second one or more members of the component;

receiving the requested third data based on the second data source, the second data source interface, the second input parameters, and the second mapping; and

populating the third widget with the received third data.

4. The method according to claim 3, further comprising:

defining a fourth widget of the first view part associated with the component of the class model and with the one or more members of the component;

receiving a request for fourth data associated with a fourth object instantiation of the component to populate the fourth widget;

identifying the configuration based on the fourth widget;

receiving the requested fourth data based on the data source, the data source interface, the input parameters, and the mapping to one or more of the one or more members of the component; and

populating the fourth widget with the received fourth data.

5. The method according to claim 3, further comprising:

defining a fourth widget of the second view part associated with the component of the class model and with the second one or more members of the component;

receiving a request for fourth data associated with a fourth object instantiation of the component to populate the fourth widget;

identifying the second configuration based on the fourth widget;

receiving the requested fourth data based on the second data source, the second data source interface, the second input parameters, and the second mapping; and

populating the fourth widget with the received fourth data.

6. The method according to claim 1, further comprising:

defining a third widget of the first view part associated with the component of the class model and with a second one or more members of the component;

receiving a request for third data associated with a third object instantiation of the component to populate the third widget;

identifying a second configuration based on the third widget, the second configuration specifying the data source, a second data source interface, second input parameters, and a second mapping to one or more of the second one or more members of the component;

receiving the requested third data based on the data source, the second data source interface, the second input parameters, and the second mapping; and

populating the third widget with the received third data.

7. The method according to claim 6, further comprising:

defining a fourth widget of the second view part associated with the component of the class model and with a second one or more members of the component;

receiving a request for fourth data associated with a fourth object instantiation of the component to populate the fourth widget;

identifying the second configuration based on the fourth widget;

receiving the requested fourth data based on the data source, the second data source interface, the second input parameters, and the second mapping; and

populating the fourth widget with the received fourth data.

8. The method according to claim 1, wherein the class model represents tag-based data and non-tag-based data.

9. The method according to claim 8, wherein the tag-based data and non-tag-based data are derived from a continuous industrial process.

10. The method according to claim 9, wherein the industrial process comprises operations of facilities involved in at least one of manufacturing, assembly, natural resource procurement, natural resource refinement, chemical synthesis, water treatment, power generation, power transmission, food processing, beverage processing, raw materials processing, agricultural processing, and materials processing.

11. A non-transitory medium storing computer-executable program code, the program code comprising:

code to define a first widget of a first view part associated with a component of a class model and with one or more members of the component;

code to define a second widget of a second view part associated with the component of the class model and with the one or more members of the component;

code to define a configuration file associated with the component, the configuration file including at least one configuration specifying a data source, a data source interface, input parameters, and a mapping to one or more of the one or more members of the component;

accessible by multiple widgets in multiple different view parts for populating the widget with regard to the component with two widgets of different view parts, enabled to access the same configuration of the configuration file to retrieve data for the different view parts, as specified by the configuration, even when the data required by each view part may be different;

code to receive a request for data associated with a first object instantiation of the component to populate the first widget;

code to identify a configuration based on the first widget

code to receive the requested data based on the data source, the data source interface, the input parameters, and the mapping to one or more of the one or more members of the component specified by the configuration;

code to populate the first widget with the received data;

code to receive a request for second data associated with a second object instantiation of the component to populate the second widget;

code to identify the configuration based on the second widget;

code to receive the requested second data based on the data source, the data source interface, the input parameters, and the mapping to one or more of the one or more members of the component specified by the configuration; and

code to populate the second widget with the second received data.

12. The medium according to claim 11, the program code further comprising:

code to define a third widget of the first view part associated with the component of the class model and with the one or more members of the component;

code to receive a request for third data associated with a third object instantiation of the component to populate the third widget;

code to identify the configuration based on the third widget;

code to receive the requested third data based on the data source, the data source interface, the input parameters, and the mapping to one or more of the one or more members of the component; and

code to populate the third widget with the received third data.

13. The medium according to claim 11, the program code further comprising:

code to define a third widget of the first view part associated with the component of the class model and with a second one or more members of the component;

code to receive a request for third data associated with a third object instantiation of the component to populate the third widget;

code to identify a second configuration based on the third widget, the second configuration specifying a second data source, a second data source interface, second input parameters, and a second mapping to one or more of the second one or more members of the component;

code to receive the requested third data based on the second data source, the second data source interface, the second input parameters, and the second mapping; and

code to populate the third widget with the received third data.

14. The medium according to claim 13, the program code further comprising:

code to define a fourth widget of the first view part associated with the component of the class model and with the one or more members of the component;

code to receive a request for fourth data associated with a fourth object instantiation of the component to populate the fourth widget;

code to identify the configuration based on the fourth widget;

code to receive the requested fourth data based on the data source, the data source interface, the input parameters, and the mapping to one or more of the one or more members of the component; and

code to populate the fourth widget with the received fourth data.

15. The medium according to claim 13, the program code further comprising:

code to define a fourth widget of the second view part associated with the component of the class model and with the second one or more members of the component;

code to receive a request for fourth data associated with a fourth object instantiation of the component to populate the fourth widget;

code to identify the second configuration based on the fourth widget;

code to receive the requested fourth data based on the second data source, the second data source interface, the second input parameters, and the second mapping; and

code to populate the fourth widget with the received fourth data.

16. The medium according to claim 11, the program code further comprising:

code to define a third widget of the first view part associated with the component of the class model and with a second one or more members of the component;

code to receive a request for third data associated with a third object instantiation of the component to populate the third widget;

code to identify a second configuration based on the third widget, the second configuration specifying the data source, a second data source interface, second input parameters, and a second mapping to one or more of the second one or more members of the component;

code to receive the requested third data based on the data source, the second data source interface, the second input parameters, and the second mapping; and

code to populate the third widget with the received third data.

17. The medium according to claim 16, the program code further comprising:

code to define a fourth widget of the second view part associated with the component of the class model and with a second one or more members of the component;

code to receive a request for fourth data associated with a fourth object instantiation of the component to populate the fourth widget;

code to identify the second configuration based on the fourth widget;

code to receive the requested fourth data based on the data source, the second data source interface, the second input parameters, and the second mapping; and

code to populate the fourth widget with the received fourth data.

18. The medium according to claim 11, wherein the class model represents tag-based data and non-tag-based data.

19. The medium according to claim 18, wherein the tag-based data and non-tag-based data are derived from a continuous industrial process.

20. The medium according to claim 19, wherein the industrial process comprises operations of facilities involved in at least one of manufacturing, assembly, natural resource procurement, natural resource refinement, chemical synthesis, water treatment, power generation, power transmission, food processing, beverage processing, raw materials processing, agricultural processing, and materials processing.