Model-based diagnostic interface

• US 20050080593A1
• Filed: 10/08/2003
• Published: 04/14/2005
• Est. Priority Date: 10/08/2003
• Status: Active Grant

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Blaser, Robert A.
• Granted Patent: US 8,180,610 B2
• Time in Patent Office: Days
• US Class Current: 702/183
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C

Abstract

Methods and apparatus are provided for a model-based diagnostic interface. An apparatus is provided for a diagnostic interface for a system having system data, system information, and a system model having a model nomenclature, the diagnostic interface comprising at least one computational object producing an output responsive to said system data, wherein said at least one object includes a binding of said system data to said system information, wherein said system data is mapped to said model nomenclature before being bound. A method is provided for making a model-based diagnostic interface for a system having system information and system data representing the status of said system, the method comprising the steps of modeling said system to create a system model having a system model nomenclature, mapping said system data into said system model nomenclature, and binding said system data mapped to said system model nomenclature to said system information.

Claims

1. A method for making a model-based diagnostic interface for a system having system information representing relationships within said system and system data representing the status of said system, the method comprising the steps of:

modeling said system to create a system model having a system model nomenclature; and

mapping said system data into said system model nomenclature.

2. The method of claim 1, further comprising the step of binding said system data mapped to said system model nomenclature to said system information.

3. The method of claim 2, wherein said step of binding comprises generating computational classes adapted for creating computational objects adapted for producing input data for at least one diagnostic engine from said system data.

4. The method of claim 3, further comprising the step of selecting at least one diagnostic engine from a plurality of diagnostic engines to receive inputs from said objects.

5. The method of claim 4, wherein the step of selecting said at least one diagnostic engine comprises the step of selecting a pass/fail diagnostic engine.

6. The method of claim 4, further comprising the step of selecting a subset of said system data based upon said selection of said at least one diagnostic engine.

7. The method of claim 1, wherein said system data has attributes, further comprising, prior to said mapping, the step of associating said system data with one or more said attributes.

8. The method of claim 1, wherein said system data comprises telemetry data of said system.

9. The method of claim 1, wherein said step of mapping comprises associating at least one item of said system data with at least one respective corresponding element of said model nomenclature.

10. The method of claim 1, wherein said system information comprises a system component hierarchy.

11. The method of claim 1, wherein said system information comprises a system network topology.

12. The method of claim 1, wherein the step of binding comprises the step of selecting a computational language.

13. The method of claim 12, comprising the step of generating functions in said computational language which are executable to generate inputs for at least one diagnostic engine based at least in part on said system data.

14. An apparatus for developing a model-based diagnostic interface for a system producing system data relating to a status of said system and having system information relating to relationships within said system, the apparatus comprising:

a processor;

a memory coupled to said processor configured to store;

a systems model development environment configured to enable a user to create a model of said system, wherein said model has a model nomenclature; and

at least one run-time diagnostic engine coupled to said systems model development environment; and

a source of said system data of said system coupled to said processor.

15. The apparatus of claim 14, wherein said model development environment is further configured to enable a user to map said system data to said model nomenclature to create mapped system data.

16. The apparatus of claim 15, wherein said model development environment is further configured to enable a user to bind said mapped system data to said system information in at least one class.

17. The apparatus of claim 16, further configured to bind said mapped system data to information relating to said at least one diagnostic engine.

18. The apparatus of claim 17, wherein said model development environment is further configured to create one or more objects of said at least one class, said one or more objects responsive to said system data to produce inputs adapted to said at least one diagnostic engine.

19. The apparatus of claim 16, wherein said model nomenclature is associated with said system information, said tool is further configured to automatically bind said mapped telemetry with said system information.

20. A diagnostic interface for a system having system data representing a status of said system, system information relating to relationships within said system, and having a system model having a model nomenclature, the diagnostic interface comprising at least one computational object producing an output responsive to said system data, wherein said at least one object includes a binding to said system information of said system data mapped to said model nomenclature.

21. The diagnostic interface of claim 20, wherein said system data is associated with data attributes before being mapped to said model nomenclature.

22. The diagnostic interface of claim 20, further comprising an input coupling to a source of said system data.

23. The diagnostic interface of claim 20, wherein said system data comprises telemetry.

24. The diagnostic interface of claim 20, wherein the model nomenclature comprises a language for expressing a system in a systems modeling environment, said language comprising tokens that can be manipulated by modeling software, wherein said tokens include at least one of an icon, a variable name, an element name, a component name, a format, and a relationship identifier.

25. The diagnostic interface of claim 20, wherein the model nomenclature comprises a language comprising tokens adapted to be manipulated by modeling software to represent a performance of said system.

26. A program product comprising:

a model-based diagnostic interface program comprising at least one object binding mapped system data to system information relating to relationships within said system, wherein said mapped system data includes system data that has been mapped to a model nomenclature of a model of said system, said at least one object executable to produce an input to a diagnostic engine responsive to system data; and

signal bearing media bearing said program.

27. The program product of claim 26, wherein said system data comprises telemetry data.

28. The program product of claim 26, wherein said at least one object is linkable to an integrated vehicle health management system.

29. The program product of claim 26, wherein the model nomenclature comprises a language for expressing a system in a systems modeling environment, said language comprising tokens that can be manipulated by modeling software, wherein said tokens include at least one of an icon, a variable name, an element name, a component name, a format, and a relationship identifier.

30. The program product of claim 26, wherein the model nomenclature comprises a language comprising tokens adapted to be manipulated by modeling software to represent a performance of said system.