SERVICE ORIENTED ARCHITECTURE BASED DECISION SUPPORT SYSTEM

• US 20090327796A1
• 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,480
• Publication Number:
  US 20090327796A1
• Time in Patent Office: Days
• US Class Current: 714/2
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A service oriented architecture (SOA) based decision support system for a vehicle is provided. A database is provided for storing a workplan of the vehicle. A webservice provider is in communication with the database for integrating applications using a variety of open standards of an internet protocol backbone. A core is connected between the database and webservice provider. The core is adapted for analyzing fault conditions, creating the workplan to overcome the fault conditions, and generating a response for a webservice request. An enterprise service bus is connected to the webservice provider for providing loose connectivity between webservice enabled functions, a service customer, and the core.

Claims

1. A service oriented architecture (SOA) based decision support system for a vehicle, comprising:

a database for storing a workplan of the vehicle;

a webservice provider in communication with the database for integrating applications using a variety of open standards of an internet protocol backbone;

a core connected between the database and webservice provider, the core adapted for;

analyzing fault conditions,

creating the workplan to overcome the fault conditions, and

generating a response for a webservice request; and

an enterprise service bus connected to the webservice provider for providing loose connectivity between webservice enabled functions, a service customer, and the core.

2. The system of claim 1, wherein the webservice enabled functions include at least one portal services and admin services.

3. The system of claim 1, wherein the core is further adapted for providing metadata, the metadata defining one of a capability and a constraint of the decision support system.

4. The system of claim 3, wherein the metadata is stored in a metadata repository in communication with the core.

5. The system of claim 1, wherein the core is further adapted for retrieving an existing workplan from the database.

6. The system of claim 1, wherein the core is further adapted to opening and closing a workplan from the database.

7. The system of claim 1, wherein the core is further adapted for:

collecting feedback from a user through the enterprise service bus, and

storing the feedback on the database for future analysis.

8. A method for implementing a service oriented architecture (SOA) based decision support system for a vehicle, comprising:

configuring a database for storing a workplan of the vehicle;

configuring a webservice provider in communication with the database for integrating applications using a variety of open standards of an internet protocol backbone;

configuring a core connected between the database and webservice provider, the core adapted for;

analyzing fault conditions,

creating the workplan to overcome the fault conditions, and

generating a response for a webservice request; and

configuring a enterprise service bus connected to the webservice provider for providing loose connectivity between webservice enabled functions, a service customer, and the core.

9. The method of claim 8, wherein configuring an enterprise service bus connected to the webservice provider for providing loose connectivity between webservice enabled functions, a service customer, and the core includes providing loose connectivity between the enterprise service bus and at least one portal services and admin services.

10. The method of claim 8, wherein configuring a core connected between the database and webservice provider includes adapting the core for providing metadata defining one of a capability and a constraint of the decision support system.

11. The method of claim 10, wherein configuring a core connected between the database and webservice provider includes adapting the core for storing the metadata in a metadata repository in communication with the core.

12. The method of claim 8, wherein configuring a core connected between the database and webservice provider includes adapting the core for retrieving an existing workplan from the database.

13. The method of claim 8, wherein configuring a core connected between the database and webservice provider includes adapting the core for opening and closing a workplan from the database.

14. The method of claim 8, wherein configuring a core connected between the database and webservice provider includes adapting the core for:

collecting feedback from a user through the enterprise service bus, and

storing the feedback on the database for future analysis.

15. A computer program product for implementing a service oriented architecture (SOA) based decision support system for a vehicle, 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 configuring a database for storing a workplan of the vehicle;

a second executable portion for configuring a webservice provider in communication with the database for integrating applications using a variety of open standards of an internet protocol backbone;

a third executable portion for configuring a core connected between the database and webservice provider, the core adapted for;

analyzing fault conditions,

creating the workplan to overcome the fault conditions, and

generating a response for a webservice request; and

a fourth executable portion for configuring a enterprise service bus connected to the webservice provider for providing loose connectivity between webservice enabled functions, a service customer, and the core.

16. The computer program product of claim 15, wherein the fourth executable portion for configuring an enterprise service bus connected to the webservice provider for providing loose connectivity between webservice enabled functions, a service customer, and the core includes a fifth executable portion for providing loose connectivity between the enterprise service bus and at least one portal services and admin services.

17. The computer program product of claim 15, wherein the third executable portion for configuring a core connected between the database and webservice provider includes a fifth executable portion for adapting the core for providing metadata defining one of a capability and a constraint of the decision support system.

18. The computer program product of claim 17, wherein the third executable portion for configuring a core connected between the database and webservice provider includes a sixth executable portion for adapting the core for storing the metadata in a metadata repository in communication with the core.

19. The computer program product of claim 15, wherein the third executable portion for configuring a core connected between the database and webservice provider includes a fifth executable portion for adapting the core for retrieving an existing workplan from the database.

20. The computer program product of claim 15, wherein the third executable portion for configuring a core connected between the database and webservice provider includes a fifth executable portion for adapting the core for:

opening and closing a workplan from the database.

collecting feedback from a user through the enterprise service bus, and

storing the feedback on the database for future analysis.