WEBSERVICE ARCHITECTURE FOR VEHICLE HEALTH MAINTENANCE

• US 20090326758A1
• Filed: 06/30/2008
• Published: 12/31/2009
• Est. Priority Date: 06/30/2008
• Status: Abandoned Application

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Menon, Sunil, Nwadiogbu, Emmanuel Obiesie, Ramanathan, Jijji, Iyer, Vidhyashankaran Ramamoorthy, Nunn, Larry J.
• Application Number:
  US12/165,503
• Publication Number:
  US 20090326758A1
• Time in Patent Office: Days
• US Class Current: 701/33
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

A webservice architecture for vehicle health maintenance is provided. A core module is in communication with a webservice provider, a webservice consumer, and a webservice registry over an internet protocol (IP) backbone. The core module is adapted for registering and discovering the webservice provider using a universal description, discovery, and integration (UDDI) communications open standard, receiving a request from the webservice provider using a simple object access protocol (SOAP), the webservice provider accepting the request from the webservice consumer, and extracting a data structure based on the webservice request in a format according to the webservice registry using a web services description language (WDSL).

Claims

1. A webservice architecture for vehicle health maintenance, comprising:

a core module in communication with a webservice provider, a webservice consumer, and a webservice registry over an internet protocol (IP) backbone, the core module adapted for;

registering and discovering the webservice provider using a universal description, discovery, and integration (UDDI) communications open standard,

receiving a request from the webservice provider using a simple object access protocol (SOAP), the webservice provider accepting the request from the webservice consumer, and

extracting a data structure based on the webservice request in a format according to the webservice registry using a web services description language (WSDL).

2. The webservice architecture of claim 1, wherein the core module is further adapted for consulting a database in communication with the core module for equipment data and troubleshooting references.

3. The webservice architecture of claim 1, wherein the database is adapted for storing equipment model and parameter data in a metadata format, the metadata maintaining a relationship between at least two of a symptom, test procedure, repair, part, and reference document of the vehicle.

4. The webservice architecture of claim 3, wherein the core module is further adapted for:

identifying a model detail based on the equipment model and parameter data, and

extracting the equipment model and parameter data from the database.

5. The webservice architecture of claim 1, wherein the core module is further adapted for validating the request prior to creating a new workplan or opening an existing workplan for the request.

6. The webservice architecture of claim 5, wherein the core module is further adapted for:

validating a uniqueness of a parameter vector containing fault code, and

downloading a time stamp of a vehicle file.

7. The webservice architecture of claim 1, wherein the core module is further adapted for:

providing a document reference for a recommended isolation or repair procedure coincident with creating a workplan for the request to the webservice consumer.

8. The webservice architecture of claim 1, wherein the core module is further adapted for providing a ranked list of isolation or repair procedures for each of an available plurality of classified fault conditions of the vehicle to the webservice consumer, the ranked list at least partially based on a feedback received from the webservice consumer.

9. The webservice architecture of claim 1, wherein the web services description language (WSDL) is compatible with an extensible markup language (XML) open standard.

10. A method for communication over a webservice architecture for providing health maintenance for a vehicle, the webservice architecture including a core module in communication with a webservice provider, a webservice consumer, and a webservice registry over an internet protocol (IP) backbone, comprising:

registering and discovering the webservice provider using a universal description, discovery, and integration (UDDI) communications open standard;

receiving a request from the webservice provider using a simple object access protocol (SOAP), the webservice provider accepting the request from the webservice consumer; and

extracting a data structure based on the webservice request in a format according to the webservice registry using a web services description language (WDSL).

11. The method of claim 10, further including consulting a database in communication with the core module for equipment data and troubleshooting references.

12. The method of claim 10, further including storing equipment model and parameter data on the database in a metadata format, the metadata maintaining a relationship between at least two of a symptom, test procedure, repair, part, and reference document of the vehicle.

13. The method of claim 12, further including:

identifying a model detail based on the equipment model and parameter data, and

extracting the equipment model and parameter data from the database.

14. The method of claim 10, further including validating the request prior to creating a new workplan or opening an existing workplan for the request.

15. The method of claim 14, further including:

validating a uniqueness of a parameter vector containing fault code, and

downloading a time stamp of a vehicle file.

16. The method of claim 10, further including:

providing a document reference for a recommended isolation or repair procedure coincident with creating a workplan for the request to the webservice consumer.

17. The method of claim 10, further including providing a ranked list of isolation or repair procedures for each of an available plurality of classified fault conditions of the vehicle to the webservice consumer, the ranked list at least partially based on a feedback received from the webservice consumer.

18. A computer program product for communication over a webservice architecture for providing health maintenance for a vehicle, the webservice architecture including a core module in communication with a webservice provider, a webservice consumer, and a webservice registry over an internet protocol (IP) backbone, the computer program product comprising a computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

a first executable portion for registering and discovering the webservice provider using a universal description, discovery, and integration (UDDI) communications open standard;

a second executable portion for receiving a request from the webservice provider using a simple object access protocol (SOAP), the webservice provider accepting the request from the webservice consumer; and

a third executable portion for extracting a data structure based on the webservice request in a format according to the webservice registry using a web services description language (WDSL).

19. The computer program product of claim 18, further including a fourth executable portion for consulting a database in communication with the core module for equipment data and troubleshooting references.

20. The computer program product of claim 19, further including a fifth executable portion for storing equipment model and parameter data on the database in a metadata format, the metadata maintaining a relationship between at least two of a symptom, test procedure, repair, part, and reference document of the vehicle.

21. The computer program product of claim 20, further including a sixth executable portion for at least one of:

identifying a model detail based on the equipment model and parameter data,

extracting the equipment model and parameter data from the database,

validating a uniqueness of a parameter vector containing fault code,

downloading a time stamp of a vehicle file,

providing a document reference for a recommended isolation or repair procedure coincident with creating a workplan for the request to the webservice consumer, and

providing a ranked list of isolation or repair procedures for each of an available plurality of classified fault conditions of the vehicle to the webservice consumer, the ranked list at least partially based on a feedback received from the webservice consumer.