Method and system for determining user fees incurred from the use of an automation system

• US 20030088524A1
• Filed: 10/01/2002
• Published: 05/08/2003
• Est. Priority Date: 11/03/2001
• Status: Abandoned Application

• Current Assignee: Phoenix Contact GmbH & Company KG
• Original Assignee: Phoenix Contact GmbH & Company KG
• Inventors: Bibelhausen, Volker
• Application Number:
  US10/261,176
• Publication Number:
  US 20030088524A1
• Time in Patent Office: Days
• US Class Current: 705/400
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0283 Price estimation or determination

Abstract

The present invention [relates to the] is a method and system for determination of user fees incurred from [the] use of [a] an automation system by [a] an automation system user for at least one automation system component made available by [the] a supplier. The [object of the] present invention [is to indicate] provides a way to easily determine such user fees[,] without running [the] a risk of having to disclose internal production data[,] and simultaneously [keeping the] keep number of actions required from the automation system user as low as possible. To this end, the present invention proposes that user data allocatable to the automation system component be acquired using a first data processor connected with the automation system[, the]. The acquired user data [be] is transmitted by the first data processor to a second data processor located on [the] a supplier side[, and the]. The user fees [be] are determined as a function of the transmitted user data using the second data processor.

Claims

1. (amended) A method for determining user fees incured by use of an automation system by an automation system user for at least one component of the automation systemprovided by at least one supplier, comprising the steps of:

a) determining user data to be allocated to the least one component of the automation system using a first data processor connected with the automation system so as to form acquired user data;

b) transmitting the acquired user data be the first data processor to a second data processor located at a component supplier side so as to form user data transmitted; and

c) determining the user fees as a function of the user data transmitted using the second data processor.

2. (amended) The method according the claim 1, wherein data concerning wear on the at least on component of the automation system are acquired as user data.

3. (amended) The method according to claim 2, wherein information about at least one of number of pulse, temperatures, weights, volumes, lenghts, revolutions, operating hours, machine downtimes, product numbers, liquid throughput, and number of spot weld is used as user data.

4. (amended) the method according to claim 3, wherein a data transfer connection running from the first data processor to the second data processor is established to transmit the user data.

5. (amended) the method according to claim 4, wherein the data transfer connection is established using a network to which the first data processor and the second data processor are linked.

6. (amended) The method according to claim 5, wherein the user data are transmitted at least one of in predefined time intervals and in response to a request previously conveyed to the first data processor by means of the second data processor.

7. (amended) The method according to claim 6, wherein an invoice based on the user fees is cyclically generated for the automation system user by means of the second data processor.

8. (amended) the method according to claim 7, wherein one of wear information and diagnostic information is obtained from the transmitted user data by means of the second data processor.

9. (amended) the method according to claim 8, wherein user data respectively allocated to the at least on component of the automation system provided by various supplier are acquired so as to form acquired user data, and the acquired user data transferred by the first data processor specific to the supplier to the second data processor located at a respective supplier side.

20. (added) The method according to claim 5, wherein the network is the Internet.

23. (added) The method according to claim 1, wherein information about at least one of number of pulses, temperatures, weight, volumes, lenghts, revolutions, operating hours, machine downtimes, product numbers, liquid throughputs, and number of spot weld is used as user data.

24. (added) The method according to claim 1, wherein a data transfer connection running from the first data processor to the second data processor is established transmit the user data.

25. (added) The method according to claim 2, wherein a data transfer connection running from the first data processor to the second data processor is established to transmit the user data.

26. (added) The method according to claim 1, wherein the user data are transmitted at least one of in predefined time intervals and in response to a request previously conveyed to the first data processor by means of the second data processor.

27. (added) The method according to claim 2, wherein the user data are transmitted at least one of in predefined time intervals and in response to a request previously conveyed to the first data processor by means of the second data processor.

28. (added) The method according to claim 3, wherein the user data are transmitted at least one of in predefined time intervals and in response to a request previously conveyed to the first data processor by means of the second data processor.

29. (added) The method according to claim 4, wherein the user data are transmitted at least one of in predefined time intervals and in response to a request previously conveyed to the first data processor by means of the second data processor.

30. (added) The method according to claim 5, wherein an invoice based on the user fees is cyclically generated for the automation system user by means of the second data processor.

31. (added) The method according to claim 4, wherein an invoice based on the user fees is cyclically generated for the automation system user by means of the second data processor.

32. (added) The method according to claim 3, wherein an invoice based on the user fees is cyclically generated for the automation system user by means of the second data processor.

33. (added) The method according to claim 2, wherein an invoice based on the user fees is cyclically generated for the automation system user by means of the second data processor.

34. (added) The method according to claim 1, wherein an invoice based on the user fees is cyclically generated for the automation system user by means of the second data processor.

35. (added) The method according to claim 6, wherein one of wear information and diagnostic information is obtained from the transmitted user data by means of the second data processor.

36. (added) The method according to claim 5, wherein one of wear information and diagnostic information is obtained from the transmitted user data by means of the second data processor.

37. (added) The method according to claim 4, wherein one of wear information and diagnostic information is obtained from the transmitted user data by means of the second data processor.

38. (added) The method according to claim 3, wherein one of wear information and diagnostic information is obtained from the transmitted user data by means of the second data processor.

39. (added) The method according to claim 2, wherein one of wear information and diagnostic information is obtained from the transmitted user data by means of the second data processor.

40. (added) The method according to claim 1, wherein one of wear information and diagnostic information is obtained from the transmitted user data by means of the second data processor.

41. (added) The method according to claim 7, wherein user data respectively allocated to the at least one component of the automation system provided by various supplier are acquired so as to form acquired user data, and the acquired user data are transferred by the first data processor specific to the supplier to the second data processor located at a respective supplier side.

42. (added) The method according to claim 6, wherein user data respectively allocated to the at least one component of the automation system provided by various supplier are acquired so as to form acquired user data, and the acquired user data are transferred by the first data processor specific to the supplier to the second data processor located at a respective supplier side.

43. (added) The method according to claim 5, wherein user data respectively allocated to the at least one component of the automation system provided by various supplier are acquired so as to form acquired user data, and the acquired user data are transferred by the first data processor specific to the supplier to the second data processor located at a respective supplier side.

44. (added) The method according to claim 4, wherein user data respectively allocated to the at least one component of the automation system provided by various supplier are acquired so as to form acquired user data, and the acquired user data are transferred by the first data processor specific to the supplier to the second data processor located at a respective supplier side.

45. (added) The method according to claim 3, wherein user data respectively allocated to the at least one component of the automation system provided by various supplier are acquired so as to form acquired user data, and the acquired user data are transferred by the first data processor specific to the supplier to the second data processor located at a respective supplier side.

46. (added) The method according to claim 2, wherein user data respectively allocated to the at least one component of the automation system provided by various supplier are acquired so as to form acquired user data, and the acquired user data are transferred by the first data processor specific to the supplier to the second data processor located at a respective supplier side.

47. (added) The method according to claim 1, wherein user data respectively allocated to the at least one component of the automation system provided by various supplier are acquired so as to form acquired user data, and the acquired user data are transferred by the first data processor specific to the supplier to the second data processor located at a respective supplier side.

10. (amended) A system for determining user fees incurred from use of an automation system by an automation system user for at least one component of the automation system provided by at least one supplier, comprising:

a) a first data processor connected with the automation system with at least one device for acquiring user data to be allocated to at least one component of the automation system so as form acquired user data; and

b) a second data processor situated at a supplier side, wherein the first data processor is designed for transmitted user data, and the second data processor is designed to acquire the user fees as a function of the transmitted user data.

11. (amended) The system according to claim 10, wherein detection devices are allocated to the at least one device to acquire data concerning wear on the at least one component of the automation system.

12. (amended) The system according to claim 11, wherein the first data processor encompasses means for establishing a data transfer connection toward the second data processor, and the second data processor encompasses means for receiving user data provided via the data transfer connection.

13. (amended) The system according to claim 12, wherein at least one of the first and the second data processors is at least one of allocated to a network and encompasses a networkable gateway.

14. (amended) The system according to claim 13, wherein the first and the second data processors are linked to a shared network.

15. (amended) The according to claim 14, wherein the first data processor is designed for independent transfer of the user data in predefined time intervals.

16. (amended) The system according to claim 15, wherein the first data processor is designed for transmitting the user data in response to a request previously conveyed to the first data processor by the second data processor.

17. (amended) The system according to claim 16, wherein the second data processor cyclically generates an invoice based on the user fees for the automation system user.

18. (amended) The system according to claim 17, wherein the second data processor is designed for obtaining at lest one of wear and diagnostic information from the transmitted user data.

19. (amended) The system according to claim 18, wherein the first data processor encompasses a device for a least one of temporarily storing the acquired user data and sequencing the acquired user data.

21. (added) The system according to claim 11, wherein the detection devices include at least one of sensors and actuators.

22. (added) The system according to claim 14, wherein the shared network is the Internet.

48. (added) The system to claim 10, wherein the first data processor encompasses means for establishing a data transfer connection toward the second data processor, and the second data processor encompasses means for receiving user data provided via the data transfer connection.

49. (added) The system according to claim 10, wherein at least one of the first and the second is at least one of allocated to a network and encompasses a networkable gateway.

50. (added) The system according to claim 11, wherein at least one of the first and the second data processors is at least one of allocated to a network and encompasses a networkable gateway.

51. (added) The system according to claim 10, wherein the first and the second data processors are linked to a shared network.

52. (added) The system according to claim 11, wherein the first and the second data processors are linked to a shared network.

53. (added) The system according to claim 12, wherein the first and the second data processors are linked to a shared network.

54. (added) The system according to claim 10, wherein the first data processor is designed for independent transfer of the user data in predefined time intervals.

55. (added) The system according to claim 11, wherein the first data processor is designed for independent transfer of the user data in predefined time intervals.

56. (added) The system according to claim 12, wherein the first data processor is designed for independent transfer of the user data in predefined time intervals.

57. (added) The system according to claim 13, wherein the first data processor is designed for independent transfer of the user data in predefined time intervals.

58. (added) The system according to claim 10, wherein the first data processor is designed for transmitting the user data in response to a request previously conveyed to the first data processor by the second data processor.

59. (added) The system according to claim 11, wherein the first data processor is designed for transmitting the user data in response to a request previously conveyed to the first data processor by the second data processor.

60. (added) The system according to claim 12, wherein the first data processor is designed for transmitting the user data in response to a request previously conveyed to the first data processor by the second data processor.

61. (added) The system according to claim 13, wherein the first data processor is designed for transmitting the user data in response to a request previously conveyed to the first data processor by the second data processor.

62. (added) The system according to claim 14, wherein the first data processor is designed for transmitting the user data in response to a request previously conveyed to the first data processor by the second data processor.

63. (added) The system according to claim 10, wherein the second data processor cyclically generates an invoice based on the user fees for the automation system user.

64. (added) The system according to claim 11, wherein the second data processor cyclically generates an invoice based on the user fees for the automation system user.

65. (added) The system according to claim 12, wherein the second data processor cyclically generates an invoice based on the user fees for the automation system user.

66. (added) The system according to claim 13, wherein the second data processor cyclically generates an invoice based on the user fees for the automation system user.

67. (added) The system according to claim 14, wherein the second data processor cyclically generates an invoice based on the user fees for the automation system user.

68. (added) The system according to claim 15, wherein the second data processor cyclically generates an invoice based on the user fees for the automation system user.

69. , (added) The system according to claim 10, wherein the second data processor is designed for obtaining at least one of wear and diagnostic information from the transmitted user data.

70. (added) The system according to claim 11, wherein the second data processor is designed for obtaining at least one of wear and diagnostic information from the transmitted user data.

71. (added) The system according to claim 12, wherein the second data processor is designed for obtaining at least one of wear and diagnostic information from the transmitted user data.

72. (added) The system according to claim 13, wherein the second data processor is designed for obtaining at least one of wear and diagnostic information from the transmitted user data.

73. (added) The system according to claim 14, wherein the second data processor is designed for obtaining at least one of wear and diagnostic information from the transmitted user data.

74. (added) The system according to claim 15, wherein the second data processor is designed for obtaining at least one of wear and diagnostic information from the transmitted user data.

75. (added) The system according to claim 16, wherein the second data processor is designed for obtaining at least one of wear and diagnostic information from the transmitted user data.

76. (added) The system according to claim 10, wherein the first data processor encompasses a device for at least one temporarily storing the acquired user data and sequencing the acquired user data.

77. (added) The system according to claim 11, wherein the first data processor encompasses a device for at least one temporarily storing the acquired user data and sequencing the acquired user data.

78. (added) The system according to claim 12, wherein the first data processor encompasses a device for at least one temporarily storing the acquired user data and sequencing the acquired user data.

79. (added) The system according to claim 13, wherein the first data processor encompasses a device for at least one temporarily storing the acquired user data and sequencing the acquired user data.

80. (added) The system according to claim 14, wherein the first data processor encompasses a device for at least one temporarily storing the acquired user data and sequencing the acquired user data.

81. (added) The system according to claim 15, wherein the first data processor encompasses a device for at least one temporarily storing the acquired user data and sequencing the acquired user data.

82. (added) The system according to claim 16, wherein the first data processor encompasses a device for at least one temporarily storing the acquired user data and sequencing the acquired user data.

83. (added) The system according to claim 17, wherein the first data processor encompasses a device for at least one temporarily storing the acquired user data and sequencing the acquired user data.