Method and apparatus for the delivery and integration of an asset management system into an existing enterprise network

• US 20030014537A1
• Filed: 07/12/2001
• Published: 01/16/2003
• Est. Priority Date: 07/12/2001
• Status: Active Grant

• Current Assignee: ABB Incorporated (ABB Limited)
• Original Assignee: ABB Incorporated (ABB Limited)
• Inventors: Argentieri, Paolo, Kupiec, Ronald A., Poorman, Anne F., Rochow, Jeff J.
• Granted Patent: US 7,194,529 B2
• Time in Patent Office: Days
• US Class Current: 709/238
• 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/10 Office automation; Time management
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

An asset management server for a network of an enterprise. The enterprise has one or more assets and two or more data sources and each source has a unique name for each asset. The server determines from an incoming message from the data sources about the assets which of the other data sources needs to receive the message and the unique name for the asset used by those sources. The server prepares the outgoing message to the sources.

Claims

1. A method for allowing an enterprise to manage one or more assets of said enterprise, said enterprise having a network based data management infrastructure and two or more data sources each of which have a unique name for each of said one or more assets, said method comprising the step of:

adding to said enterprise network an asset management server, said server capable of performing the steps of;

(a) determining from an incoming message to said server from one of said two or more data sources about one of said one or more assets which of the others of said two or more data sources needs to receive said incoming message and said unique name used for said one or more assets by each of said other of said two or more data sources;

(b) preparing a message for each of said other two or more data sources that need to receive said incoming message, said prepared message using said unique name used for said one or more assets by each of said other of said two or more data sources; and

(c) transmitting said prepared message to each of said other two or more data sources that need to receive said incoming message.

2. The method of claim 1 wherein said incoming message is in the HTTP protocol.

3. The method of claim 1 wherein said incoming message is in the XML format.

4. The method of claim 1 wherein said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

5. The method of claim 1 wherein said incoming message and said prepared message are both in the XML format and said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

6. The method of claim 1 wherein said asset management server further performs the step of allowing interaction of said enterprise network between said two or more data sources by using the XML over HTTP-Post protocol.

7. The method of claim 4 wherein said asset management server transmits said prepared message to each of said other two or more data sources and further performs the step of keeping said session connected while transmitting said prepared message.

8. The method of claim 5 wherein said asset management server transmits said prepared message to each of said other two or more data sources and further performs the step of keeping said session connected while transmitting said prepared message.

9. The method of claim 1 wherein said enterprise network includes a human machine interface to display information and said asset management server further performs the step of allowing said human machine interface to display information about said one of said one or more assets in said incoming message in a predetermined format.

10. The method of claim 9 wherein said predetermined format is a collection of asset oriented web pages.

11. A method for allowing an enterprise to manage a plurality of assets of said enterprise, said enterprise having a network based data management infrastructure and a plurality of data sources each of which have a unique name for each of said plurality of assets, said method comprising the step of:

adding to said enterprise network an asset management server, said server capable of performing the steps of;

(a) determining from an incoming message to said server from at least one of said plurality of data sources about at least one of said plurality of assets which of said plurality of data sources needs to receive said incoming message and said unique name used for said at least one of said plurality of assets by each of said plurality of data sources that need to receive said incoming message;

(b) preparing a message for each of said plurality of data sources that need to receive said incoming message, said prepared message using said unique name used for said at least one of said plurality of assets by each of said plurality of data sources that need to receive said incoming message; and

(c) transmitting said prepared message to each of said plurality of data sources that need to receive said incoming message.

12. The method of claim 11 wherein said incoming message is in the HTTP protocol.

13. The method of claim 11 wherein said incoming message is in the XML format.

14. The method of claim 11 wherein said incoming message is transmitted to said asset management server in a session and over a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

15. The method of claim 11 wherein said incoming message and said prepared message are both in the XML format and said incoming message is transmitted to said asset management server in a session and over a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

16. The method of claim 11 wherein said asset management server further performs the step of allowing interaction of said enterprise network between said two or more data sources by using the XML over HTTP-Post protocol.

17. The method of claim 14 wherein said asset management server transmits said prepared message to each of said other two or more data sources and further performs the step of keeping said session connected while transmitting said prepared message.

18. The method of claim 15 wherein said asset management server transmits said prepared message to each of said other two or more data sources and further performs the step of keeping said session connected while transmitting said prepared message.

19. The method of claim 11 wherein said enterprise network includes a human machine interface to display information and said asset management server further performs the step of allowing said human machine interface to display information about said at least one of said plurality of assets in said incoming message in a predetermined format.

20. The method of claim 19 wherein said predetermined format is a collection of asset oriented web pages.

21. An enterprise network for managing one or more assets of said enterprise comprising:

(a) two or more data sources each of which have a unique name for each of said one or more assets; and

(b) an asset management server;

said server for;

(i) determining from an incoming message to said server from one of said two or more data sources about one of said one or more assets which of the others of said two or more data sources needs to receive said incoming message and said unique name used for said one or more assets by each of said other of said two or more data sources;

(ii) preparing a message for each of said other two or more data sources that need to receive said incoming message, said prepared message using said unique name used for said one or more assets by each of said other of said two or more data sources; and

(iii) transmitting said prepared message to each of said other two or more data sources that need to receive said incoming message.

22. The enterprise network of claim 21 wherein said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

23. The enterprise network of claim 21 wherein said incoming message and said prepared message are both in the XML format and said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

24. The enterprise network of claim 21 wherein said asset management server is also for allowing interaction of said enterprise network between said two or more data sources by using the XML over HTTP-Post protocol.

25. The enterprise network of claim 22 wherein said asset management server transmits said prepared message to each of said other two or more data sources and is also for keeping said session connected while transmitting said prepared message.

26. The enterprise network of claim 23 wherein said asset management server transmits said prepared message to each of said other two or more data sources and is also for keeping said session connected while transmitting said prepared message.

27. The enterprise network of claim 21 further comprising a human machine interface to display information and said asset management server is also for allowing said human machine interface to display information about said one of said one or more assets in said incoming message in a predetermined format.

28. The enterprise network of claim 27 wherein said predetermined format is a collection of asset oriented web pages.

30. The enterprise network of claim 29 wherein said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said plurality of data sources that need to receive said incoming message during said session and over said connection and said protocol that transmitted said incoming message.

31. The enterprise network of claim 29 wherein said incoming message and said prepared message are both in the XML format and said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said plurality of data sources that need to receive said incoming message during said session and over said connection and said protocol that transmitted said incoming message.

32. The enterprise network of claim 29 wherein said asset management server is also for allowing interaction of said enterprise network between said plurality of data sources by using the XML over HTTP-Post protocol.

33. The enterprise network of claim 30 wherein said asset management server transmits said prepared message to each of said plurality of data sources that need to receive said incoming message and is also for keeping said session connected while transmitting said prepared message.

34. The enterprise network of claim 31 wherein said asset management server transmits said prepared message to each of said plurality of data sources that need to receive said incoming message and is also for keeping said session connected while transmitting said prepared message.

35. The enterprise network of claim 29 further comprising a human machine interface to display information and said asset management server is also for allowing said human machine interface to display information about said about said at least one of said plurality of assets in said incoming message in a predetermined format.

36. The enterprise network of claim 35 wherein said predetermined format is a collection of asset oriented web pages.

38. The asset management server of claim 37 wherein said enterprise has a network based management infrastructure and said asset management server is part of said enterprise network.

39. The asset management server of claim 37 wherein said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

40. The asset management server of claim 37 wherein said incoming message and said prepared message are both in the XML format and said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

41. The asset management server of claim 38 further comprising means for allowing interaction of said enterprise network between said two or more data sources by using the XML over HTTP-Post protocol.

42. The asset management server of claim 39 further comprising means for keeping said session connected while transmitting said prepared message.

43. The asset management server of claim 40 further comprising means for keeping said session connected while transmitting said prepared message.

44. The asset management server of claim 38 wherein said enterprise network comprises a human machine interface to display information and said asset management server further comprises means for allowing said human machine interface to display information about said one of said one or more assets in said incoming message in a predetermined format.

45. The asset management server of claim 44 wherein said predetermined format is a collection of asset oriented web pages.

47. The asset management server of claim 46 wherein said enterprise has a network based management infrastructure and said asset management server is part of said enterprise network.

48. The asset management server of claim 46 wherein said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

49. The asset management server of claim 46 wherein said incoming message and said prepared message are both in the XML format and said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

50. The asset management server of claim 47 further comprising means for allowing interaction of said enterprise network between said two or more data sources by using the XML over HTTP-Post protocol.

51. The asset management server of claim 48 further comprises means for keeping said session connected while transmitting said prepared message.

52. The asset management server of claim 49 further comprising means for keeping said session connected while transmitting said prepared message.

53. The asset management server of claim 47 wherein said enterprise network comprises a human machine interface to display information and said asset management server further comprises means for allowing said human machine interface to display information about said at least one of said plurality of assets in said incoming message in a predetermined format.

54. The asset management server of claim 53 wherein said predetermined format is a collection of asset oriented web pages.

29. An enterprise network for managing a plurality of assets of said enterprise comprising:

(a) a plurality of data sources each of which have a unique name for each of said plurality of assets; and

(b) an asset management server;

said server for;

(i) determining from an incoming message to said server from at least one of said plurality of data sources about at least one of said plurality of assets which of said plurality of data sources needs to receive said incoming message and said unique name used for said at least one of said plurality of assets by each of said plurality of data sources that need to receive said incoming message;

(ii) preparing a message for each of said plurality of data sources that need to receive said incoming message, said prepared message using said unique name used for said at least one of said plurality of assets by each of said plurality of data sources that need to receive said incoming message; and

(iii) transmitting said prepared message to each of said plurality of data sources that need to receive said incoming message.

37. An asset management server for an enterprise having two or more data sources and each of said two or more data sources having a unique name for each of one or more assets of said enterprise comprising:

(a) means for determining from an incoming message to said server from one of said two or more data sources about one of said one or more assets which of the others of said two or more data sources needs to receive said incoming message and said unique name used for said one or more assets by each of said other of said two or more data sources;

(b) means for preparing a message for each of said other two or more data sources that need to receive said incoming message, said prepared message using said unique name used for said one or more assets by each of said other of said two or more data sources; and

(c) means for transmitting said prepared message to each of said other two or more data sources that need to receive said incoming message.

46. An asset management server for an enterprise having a plurality of assets and a plurality of data sources each of which have a unique name for each of said plurality of assets comprising:

(a) means for determining from an incoming message to said server from at least one of said plurality of data sources about at least one of said plurality of assets which of said plurality of data sources needs to receive said incoming message and said unique name used for said at least one of said plurality of assets by each of said plurality of data sources that need to receive said incoming message;

(b) means for preparing a message for each of said plurality of data sources that need to receive said incoming message, said prepared message using said unique name used for said at least one of said plurality of assets by each of said plurality of data sources that need to receive said incoming message; and

(c) means for transmitting said prepared message to each of said plurality of data sources that need to receive said incoming message.

55. An enterprise comprising:

(a) a plurality of assets;

(b) an enterprise network for managing said plurality of assets comprising;

a plurality of data sources each of which have a unique name for each of said plurality of assets; and

an asset manager server, said server for;

(i) determining from an incoming message to said server from at least one of said plurality of data sources about at least one of said plurality of assets which of said plurality of data sources needs to receive said incoming message and said unique name used for said at least one of said plurality of assets by each of said plurality of data sources that need to receive said incoming message;

(ii) preparing a message for each of said plurality of data sources that need to receive said incoming message, said prepared message using said unique name used for said at least one of said plurality of assets by each of said plurality of data sources that need to receive said incoming message; and

(iii) transmitting said prepared message to each of said plurality of data sources that need to receive said incoming message.

56. The enterprise of claim 55 wherein said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said plurality of data sources that need to receive said incoming message during said session and over said connection and said protocol that transmitted said incoming message.

57. The enterprise of claim 55 wherein said incoming message and said prepared message are both in the XML format and said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said plurality of data sources that need to receive said incoming message during said session and over said connection and said protocol that transmitted said incoming message.

58. The enterprise of claim 55 wherein said asset management server is also for allowing interaction of said enterprise network between said plurality of data sources by using the XML over HTTP-Post protocol.

59. The enterprise of claim 56 wherein said asset management server transmits said prepared message to each of said plurality of data sources that need to receive said incoming message and is also for keeping said session connected while transmitting said prepared message.

60. The enterprise of claim 57 wherein said asset management server transmits said prepared message to each of said plurality of data sources that need to receive said incoming message and is also for keeping said session connected while transmitting said prepared message.

61. The enterprise of claim 55 further comprising a human machine interface to display information and said asset management server is also for allowing said human machine interface to display information about said at least one of said plurality of assets in said incoming message in a predetermined format.

62. The enterprise of claim 61 wherein said predetermined format is a collection of asset oriented web pages.

63. An enterprise comprising:

(a) one or more assets;

(b) an enterprise network for managing said one or more assets comprising;

two or more data sources each of which have a unique name for each of said one or more assets; and

an asset manager server, said server for;

(i) determining from an incoming message to said server from one of said two or more data sources about one of said one or more assets which of the other of said two or more data sources needs to receive said incoming message and said unique name used for said one or more assets by each of said other of said two or more data sources;

(ii) preparing a message for each of said other two or more data sources that need to receive said incoming message, said prepared message using said unique name used for said one or more assets by each of said other of said two or more data sources; and

(iii) transmitting said prepared message to each of said other two or more data sources that need to receive said incoming message.

64. The enterprise of claim 63 wherein said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

65. The enterprise of claim 63 wherein said incoming message and said prepared message are both in the XML format and said incoming message is transmitted to said asset management server in a session and over a connection and a protocol and said prepared message is transmitted to each of said other two or more data sources during said session and over said connection and said protocol that transmitted said incoming message.

66. The enterprise of claim 63 wherein said asset management server is also for allowing interaction of said enterprise network between said two or more data sources by using the XML over HTTP-Post protocol.

67. The enterprise of claim 64 wherein said asset management server transmits said prepared message to each of said other two or more data sources and is also for keeping said session connected while transmitting said prepared message.

68. The enterprise of claim 65 wherein said asset management server transmits said prepared message to each of said other two or more data sources and is also for keeping said session connected while transmitting said prepared message.

69. The enterprise of claim 63 further comprising a human machine interface to display information and said asset management server is also for allowing said human machine interface to display information about said one of said one or more assets in said incoming message in a predetermined format.

70. The enterprise of claim 69 wherein said predetermined format is a collection of asset oriented web pages.