Method, computer system and computer system network

• US 20040015409A1
• Filed: 01/07/2003
• Published: 01/22/2004
• Est. Priority Date: 07/07/2000
• Status: Abandoned Application

• Current Assignee: GF-X Operations Limited
• Original Assignee: GF-X Operations Limited
• Inventors: Ravech, David, Chittenden, Andrew, Zoppos, Demetrios, Patterson, Simon, Demetriades, Petros Andreas, Quinlan, Matthew, Morgan, Todd Howard
• Application Number:
  US10/332,405
• Publication Number:
  US 20040015409A1
• Time in Patent Office: Days
• US Class Current: 705/26
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

A computer system for providing a centralised register of transport provider permanent booking agreements between a plurality of transport providers and a plurality of forwarders is dislosed. The booking agreements relate to capacity on routes between stations in a transport system. The computer system includes a processing unit, an interface unit for communication with said processing unit, and a memory unit. The computer system is configured to receive one or more transport provider allotment templates from a plurality of transport providers. Each allotment template comprises template data representing a permanent booking agrement between a transport provider and a forwarder. The template data comprises data representative of one or more route leg instances and data representative of an agreement capacity value for at least one of said one or more route leg instances. The computer system is configured to store a record of said allotment templates in the memory unit. Access to the record is provided to a plurality of forwarders such that each forwarder can view at least part of the template data of each allotment template which represents a permanent booking agreement between the forwarder and one or more transport providers. Access to the template data of allotment templates representing a permanent booking agreement between another forwarder and said one or more transport providers is not provided.

Claims

1. A method of configuring a computer system including a processing unit, an interface unit for communication with said processing unit and a memory unit, for providing a centralised register of transport provider permanent booking agreements between a plurality of transport providers and a plurality of forwarders, the booking agreements relating to capacity on routes between stations in a transport system, the method comprising:

receiving one or more transport provider allotment templates from a plurality of transport providers, each allotment template comprising template data representing a permanent booking agreement between a transport provider and a forwarder, the template data comprising data representative of one of more route leg instances and data representative of an agreement capacity value for at least one of said one or more route leg instances;

storing a record of said allotment templates in the memory unit; and

providing access to said record to a plurality of forwarders such that each forwarder can view at least part of the template data of each allotment template which represents a permanent booking agreement between the forwarder and one or more transport providers, but not the template data of allotment templates representing a permanent booking agreement between another forwarder and said one or more transport providers.

2. A method according to claim 1, the method further comprising configuring the system to:

receive a request from a forwarder to search for a subset of the allotment templates which represent a permanent booking agreement between the forwarder and one or more transport providers;

search the record for the subset of allotment templates; and

provide a representation of at least part of the template data of the subset of booking templates to the forwarder.

3. A method according to claim 1 or 2, the method further comprising:

providing access to said record to said plurality of transport providers such that each transport provider can view at least part of the template data of each allotment template which represents a permanent booking agreement between the transport provider and one or more forwarders, but not the template data of allotment templates representing a permanent booking agreement between another transport provider and said one or more forwarders.

4. A method according to claim 3, the method further comprising configuring the system to:

receive a request from a transport provider to search for a subset of the allotment templates which represent a permanent booking agreement between the transport provider and one or more forwarders;

search the record for the subset of allotment templates; and

provide a representation of at least part of the template data of the subset of allotment templates to the transport provider.

5. A method according to any one of claims 1 to 4, the method further comprising:

allowing a transport provider to create, amend or delete one or more of its allotment templates

6. A method according to any one of claims 1 to 5, the method further comprising configuring the system to:

receive a single data set for creating, amending and deleting a plurality of allotment templates of a transport provider.

7. A method according to any one of claims 1 to 6, the method further comprising configuring the system to:

provide an event summary for the creation, amendment or deletion of the or each allotment template; and

send the event summary to the associated forwarder.

8. A method according to any one of claims 1 to 7, the method further comprising configuring the system to:

receive one or more forwarder allotment bookings from one of a plurality of forwarders, each allotment booking comprising booking data and relating to a permanent booking agreement between the forwarder and a transport provider, the booking data comprising data representative of a transport provider and one or more route leg instances.

9. A method according to claim 8, wherein a plurality of transport provider messaging modalities are provided, said participation modalities indicative of a messaging type used for each transport provider, the method further comprising configuring the system to:

determine the messaging modality of the transport provider associated with the or each allotment booking.

10. A method according to claims 8 or 9, the method further comprising configuring the system to:

optionally dependent on the transport provider messaging modality, send a message to the transport provider containing data representative of the forwarder together with the booking data for the or each allotment booking.

11. A method according to claims 8 or 9, the method further comprising configuring the system to:

optionally dependent on the transport provider messaging modality, search the record to find a corresponding allotment template for the or each allotment booking.

12. A method according to claim 11, wherein an operational window record for the transport provider is stored in the memory unit, the operational window record representative of a time period before a departure in which bookings can be sent to the transport provider, the method comprising configuring the system to:

calculate a booking operational window from the booking departure date and operational window record, the booking operational window representative of the time period before the booking departure date in which the booking can be sent to the transport provider; and

dependent on the allotment booking existing before the booking operational window, construct a pending booking request from the booking data and optionally the corresponding template data and store the pending booking request in a pending booking list.

13. A method according to claim 12, the method further comprising configuring the system to routinely check the pending booking list and, dependent on the pending booking being in the flight operational window, send the pending booking request to the transport provider as a booking request in a data format of the transport provider.

14. A method according to claim 11, wherein the booking data includes a requested capacity, the method further comprising configuring the system to:

check the requested capacity against the agreement capacity; and

dependent on the requested capacity being greater than the allotment agreement capacity, construct an in-review booking request from the booking data and optionally the corresponding template data and store the in-review booking request.

15. A method according to claim 14, the method further comprising configuring the system to:

receive from the transport provider an indication accepting the in-review booking request; and

send the in-review booking request to the transport provider as a booking request in a data format of the transport provider.

16. A method according to claim 11, the method further comprising:

storing an indication of an excess booking tolerance record for the transport provider in the memory unit, the excess booking tolerance record representative of an extra capacity acceptable by the transport provider; and

configuring the system to, dependent on the requested capacity being less than or equal to the combined allotment agreement capacity and extra capacity, construct from the booking data and corresponding template data a booking request in a data format of the transport provider, and send the booking request to the transport provider.

17. A method according to claim 11, further comprising configuring the system to:

construct from the booking data and corresponding template data a booking request in a data format of the transport provider; and

send the booking request to the transport provider.

18. A method according to any one of claims 8 to 17, the method further comprising:

allowing a forwarder to create or amend or cancel one or more of its allotment bookings.

19. A method according to any one of claims 8 to 18, the method further comprising configuring the system to:

receive a single data set for creating or amending or cancelling a plurality of forwarder allotment bookings with a plurality of transport providers.

20. A method according to any one of claims 1 to 19, wherein a milestone plan is associated with the allotment template, the milestone plan associating at least one pre-journey milestone with at least one of said one or more route leg instances.

21. A method according to claim 20 dependent on any one of claims 8 to 19, further comprising:

associating the milestone plan with the allotment booking.

22. A method according to claim 20 or 21, the method further comprising:

allowing a forwarder or transport provider to view the milestone plan associated with a template or booking.

23. A method according to any one of claims 20 to 22, the method further comprising:

allowing a forwarder or transport provider to search for allotment bookings with at least one approaching milestone.

24. A method according to claim 23, the method further comprising configuring the system to:

receive a request from a forwarder or transport provider to search for allotment bookings or templates which have at least one approaching milestone;

search the record for the or each allotment booking or template; and

provide a representation of the or each allotment booking or template and associated milestone.

25. A method according to claim 24, wherein a period of time is defined in which the approaching milestone occurs.

26. A method according to any one of claims 20 to 25, wherein the milestones represent one or more of the following:

a reminder; and

/or

an aspect of a contract; and

/or

a deadline for booking creations, amendments and/or cancellations.

27. A method according to any one of claims 1 to 26, the method further comprising configuring the system to provide reports concerning the utilisation of allotment bookings.

50. A method according to any one of claims 8 to 18, the method further comprising:

receiving a single data set for creating or amending a plurality of forwarder allotment bookings with a plurality of transport providers.

54. A method according to any one of claims 20 to 22, the method further comprising:

a forwarder or transport provider searching for allotment bookings with at least one approaching milestone.

55. A method according to claim 54, the method further comprising:

receiving a request from a forwarder or transport provider to search for allotment bookings or templates which have at least one approaching milestone;

searching the record for the or each allotment booking or template; and

providing a representation of the or each allotment booking or template and associated milestone.

56. A method according to claim 55, wherein a period of time is defined in which the approaching milestone occurs.

63. A method according to any one of the preceding claims wherein a route leg instance is a flight leg instance.

64. A computer program translatable into a form for configuring and/or operating a computer system in accordance with any one of claims 1 to 63.

65. A computer program for configuring and/or operating a computer system in accordance with any one of claims 1 to 63.

66. A carrier medium carrying a computer program according to claim 64 or 65.

28. A method of configuring a computer system including a processing unit, an interface unit for communication with said processing unit and a memory unit, wherein a centralised register of bookings is stored in the memory unit, each booking arranged between one of a plurality of transport providers and one of a plurality of forwarders and relating to booked capacity on a route between stations in a transport system, the method comprising:

associating a milestone plan with one or more of the bookings, the milestone plan associating at least one pre-journey milestone with the booking; and

allowing a forwarder or transport provider to view said at least one milestone associated with one or more bookings.

29. A method according to claim 28, the method further comprising:

providing access to said register to a plurality of forwarders such that each forwarder can view bookings between the forwarder and one or more transport providers, but not bookings between another forwarder and said one or more transport providers;

and/or providing access to said register to a plurality of transport providers such that each transport provider can view bookings between the transport provider and one or more forwarders, but not bookings between another transport provider and said one or more forwarders.

30. A method according to claims 28 or 29, the method further comprising configuring the system to:

receive a request from a forwarder or transport provider to search for any bookings which have at least one approaching milestone;

search the record for the or each booking; and

provide a representation of the booking and associated milestone.

31. A method according to any one of claims 28 to 31, wherein the milestones represent one or more of the following:

a reminder; and

/or

an aspect of a contract; and

/or

a deadline for booking amendments and/or cancellations.

95. A computer system according to claim 28, further configured to:

provide access to said register to a plurality of forwarders such that each forwarder can view bookings between the forwarder and one or more transport providers, but not bookings between another forwarder and said one or more transport providers; and

/or

provide access to said register to a plurality of transport providers such that each transport provider can view bookings between the transport provider and one or more forwarders, but not bookings between another transport provider and said one or more forwarders.

32. A method for operating a computer system including a processing unit, an interface unit for communication with said processing unit and a memory unit, for providing a centralised register of transport provider permanent booking agreements between a plurality of transport providers and a plurality of forwarders, the booking agreements relating to capacity on routes between stations in a transport system, wherein a record of one or more transport provider allotment templates from a plurality of transport providers are stored in the memory unit, each allotment template comprising template data representing a permanent booking agreement between a transport provider and a forwarder, the template data comprising data representative of one or more route leg instances and data representative of an agreement capacity value for at least one of said one or more route leg instances, the method comprising:

providing access to said record to a plurality of forwarders such that each forwarder can view at least part of the template data of each allotment template which represents a permanent booking agreement between the forwarder and one or more transport providers, but not the template data of allotment templates representing a permanent booking agreement between another forwarder and said one or more transport providers.

33. A method according to claim 32, the method further comprising:

receiving a request from a forwarder to search for a subset of the allotment templates which represent a permanent booking agreement between the forwarder and one or more transport providers;

searching the record for the subset of allotment templates; and

providing a representation of at least part of the template data of the subset of booking templates to the forwarder.

34. A method according to claim 32 or 33, the method further comprising:

providing access to said record to said plurality of transport providers such that each transport provider can view the at least part of the template data of each allotment template which represents a permanent booking agreement between the transport provider and one or more forwarders, but not the template data of allotment templates representing a permanent booking agreement between another transport provider and said one or more forwarders.

35. A method according to claim 34, the method further comprising:

receiving a request from a transport provider to search for a subset of the allotment templates which represent a permanent booking agreement between the transport provider and one or more forwarders;

searching the record for the subset of allotment templates; and

providing a representation of at least part of the template data of the subset of allotment templates to the transport provider.

36. A method according to any one of claims 32 to 35, the method further comprising:

a transport provider creating, amending or deleting one or more of its allotment templates

37. A method according to any one of claims 32 to 36, the method further comprising:

receiving a single data set for creating, amending and deleting a plurality of allotment templates of a transport provider.

38. A method according to any one of claims 32 to 37, the method further comprising:

providing an event summary for the creation, amendment or deletion of the or each allotment template; and

sending the event summary to the associated forwarder.

39. A method according to any one of claims 32 to 38, the method further comprising:

receiving one or more forwarder allotment bookings from one of a plurality of forwarders, each allotment booking comprising booking data and relating to a permanent booking agreement between the forwarder and a transport provider, the booking data comprising data representative of a transport provider and one or more route leg instances.

40. A method according to claim 39, wherein a plurality of transport provider messaging modalities are provided, said participation modalities indicative of a messaging type used for each transport provider, the method further comprising:

determining the messaging modality of the transport provider associated with the or each allotment booking.

41. A method according to claims 39 or 40, the method further comprising:

optionally dependent on the transport provider messaging modality, sending a message to the transport provider containing data representative of the forwarder together with the booking data for the or each allotment booking.

42. A method according to claims 39 or 40, the method further comprising:

for the or each allotment booking, optionally dependent on the transport provider messaging modality, searching the record to find a corresponding allotment template for the allotment booking.

43. A method according to claim 42, wherein an operational window record for the transport provider is stored in the memory unit, the operational window record representative of a time period before a departure in which bookings can be sent to the transport provider, the method comprising:

calculating a booking operational window from the booking departure date and operational window record, the booking operational window representative of the time period before the booking departure date in which the booking can be sent to the transport provider; and

dependent on the allotment booking existing before the booking operational window, constructing a pending booking request from the booking data and optionally the corresponding template data and storing the pending booking request in a pending booking list.

44. A method according to claim 43, the method further comprising routinely checking the pending booking list and, dependent on the pending booking being in the operational window, sending the pending booking request to the transport provider as a booking request in a data format of the transport provider.

45. A method according to claim 44, wherein the booking data includes a requested capacity, the method further comprising:

checking the requested capacity against the agreement capacity; and

dependent on the requested capacity being greater than the allotment agreement capacity, constructing an in-review booking request from the booking data and optionally the corresponding template data and storing the in-review booking request.

46. A method according to claim 45, the method further comprising:

receiving from the transport provider an indication accepting the in-review booking request; and

sending the in-review booking request to the transport provider as a booking request in a data format of the transport provider.

47. A method according to claim 42, wherein an indication of an excess booking tolerance record for the transport provider is stored in the memory unit, the excess booking tolerance record representative of an extra capacity acceptable by the transport provider, the method further comprising:

dependent on the requested capacity being less than or equal to the combined allotment agreement capacity and extra capacity, constructing from the booking data and corresponding template data a booking request in a data format of the transport provider, and sending the booking request to the transport provider.

48. A method according to claim 42, further comprising constructing from the booking data and corresponding template data a booking request in a data format of the transport provider, and sending the booking request to the transport provider.

49. A method according to any one of claims 39 to 48, the method further comprising:

a forwarder creating or amending one or more of its allotment bookings.

51. A method according to any one of claims 32 to 50, wherein a milestone plan is associated with the allotment template, the milestone plan associating at least one pre-journey milestone with at least one of said one or more route leg instances.

52. A method according to claim 51 dependent on any one of claims 39 to 50, further comprising:

associating the milestone plan with the allotment booking.

53. A method according to claim 51 or 52, the method further comprising:

a forwarder or transport provider viewing the milestone plan associated with a template or booking.

57. A method according to any one of claims 51 to 56, wherein the milestones represent one or more of the following:

a reminder; and

/or

an aspect of a contract; and

/or

a deadline for booking creations, amendments and/or cancellations.

58. A method according to any one of claims 32 to 57, the method further comprising providing reports concerning the utilisation of allotment bookings.

98. A computer system comprising:

a processing unit;

an interface unit for communication with said processing unit; and

a memory unit;

the computer system configured to operate in accordance with any one of claims 32 to 63.

59. A method of operating a computer system including a processing unit, an interface unit for communication with said processing unit and a memory unit, wherein a centralised register of bookings is stored in the memory unit, each booking arranged between one of a plurality of transport providers and one of a plurality of forwarders and relating to booked capacity on a route between stations in a transport system, one or more of the bookings having an associated milestone plan associating at least one pre-journey milestone with the booking, the method comprising:

allowing a forwarder or transport provider to view said at least one milestone associated with one or more bookings.

60. A method according to claim 59, the method further comprising:

providing access to said register to a plurality of forwarders such that each forwarder can view bookings between the forwarder and one or more transport providers, but not bookings between another forwarder and said one or more transport providers; and

/or

providing access to said register to a plurality of transport providers such that each transport provider can view bookings between the transport provider and one or more forwarders, but not bookings between another transport provider and said one or more forwarders.

61. A method according to claims 59 or 60, the method further comprising:

receiving a request from a forwarder or transport provider to search for any bookings which have at least one approaching milestone;

searching the record for the or each booking; and

providing a representation of the booking and associated milestone.

62. A method according to any one of claims 59 to 61, wherein the milestones represent one or more of the following:

a reminder; and

/or

an aspect of a contract; and

/or

a deadline for booking amendments and/or cancellations.

67. A computer system for providing a centralised register of transport provider permanent booking agreements between a plurality of transport providers and a plurality of forwarders, the booking agreements relating to capacity on routes between stations in a transport system, comprising

a processing unit;

an interface unit for communication with said processing unit; and

a memory unit;

the computer system configured to;

receive one or more transport provider allotment templates from a plurality of transport providers, each allotment template comprising template data representing a permanent booking agreement between a transport provider and a forwarder, the template data comprising data representative of one or more route leg instances and data representative of an agreement capacity value for at least one of said one or more route leg instances;

store a record of said allotment templates in the memory unit; and

provide access to said record to a plurality of forwarders such that each forwarder can view at least part of the template data of each allotment template which represents a permanent booking agreement between the forwarder and one or more transport providers, but not the template data of allotment templates representing a permanent booking agreement between another forwarder and said one or more transport providers.

68. A computer system according to claim 67, further configured to:

receive a request from a forwarder to search for a subset of the allotment templates which represent a permanent booking agreement between the forwarder and one or more transport providers;

search the record for the subset of allotment templates; and

provide a representation of at least part of the template data of the subset of booking templates to the forwarder.

69. A computer system according to claim 67 or 68, further configured to:

provide access to said record to said plurality of transport providers such that each transport provider can view at least part of the template data of each allotment template which represents a permanent booking agreement between the transport provider and one or more forwarders, but not the template data of allotment templates representing a permanent booking agreement between another transport provider and said one or more forwarders.

70. A computer system according to claim 69, further configured to:

receive a request from a transport provider to search for a subset of the allotment templates which represent a permanent booking agreement between the transport provider and one or more forwarders;

search the record for the subset of allotment templates; and

provide a representation of at least part of the template data of the subset of allotment templates to the transport provider.

71. A computer system according to any one of claims 67 to 70, further configured to:

allow a transport provider to create, amend or delete one or more of its allotment templates

72. A computer system according to any one of claims 67 to 71, further configured to:

receive a single data set for creating, amending and deleting a plurality of allotment templates of a transport provider.

73. A computer system according to any one of claims 67 to 72, further configured to:

provide an event summary for the creation, amendment or deletion of the or each allotment template; and

send the event summary to the associated forwarder.

74. A computer system according to any one of claims 67 to 73, further configured to:

receive one or more forwarder allotment bookings from one of a plurality of forwarders, each allotment booking comprising booking data and relating to a permanent booking agreement between the forwarder and a transport provider, the booking data comprising data representative of a transport provider and one or more route leg instances.

75. A computer system according to claim 74, wherein a plurality of transport provider messaging modalities are provided, said participation modalities indicative of a messaging type used for each transport provider, further configured to:

determine the messaging modality of the transport provider associated with the or each allotment booking.

76. A computer system according to claims 74 or 75, further configured to:

optionally dependent on the transport provider messaging modality, send a message to the transport provider containing data representative of the forwarder together with the booking data for the or each allotment booking.

77. A computer system according to claims 74 or 75, further configured to:

optionally dependent on the transport provider messaging modality, search the record to find a corresponding allotment template for the or each allotment booking.

78. A computer system according to claim 77, wherein an operational window record for the transport provider is stored in the memory unit, the operational window record representative of a time period before a departure in which bookings can be made with the transport provider, further configured to:

calculate a booking operational window from the booking departure date and operational window record, the booking operational window representative of the time period before the booking departure date in which the booking can be made; and

dependent on the allotment booking existing before the booking operational window, construct a pending booking request from the booking data and optionally the corresponding template data and store the pending booking request in a pending booking list.

79. A computer system according to claim 78, further configured to check the pending booking list and, dependent on the pending booking being in the operational window, send the pending booking request to the transport provider as a booking request in a data format of the transport provider.

80. A computer system according to claim 77, wherein the booking data includes a requested capacity, further configured to:

check the requested capacity against the agreement capacity; and

dependent on the requested capacity being greater than the allotment agreement capacity, construct an in-review booking request from the booking data and optionally the corresponding template data and store the in-review booking request.

81. A computer system according to claim 80, further configured to:

receive from the transport provider an indication accepting the in-review booking request; and

send the in-review booking request to the transport provider as a booking request in a data format of the transport provider.

82. A computer system according to claim 77, further configured to:

store an indication of an excess booking tolerance record for the transport provider in the memory unit, the excess booking tolerance record representative of an extra capacity acceptable by the transport provider; and

dependent on the requested capacity being less than or equal to the combined allotment agreement capacity and extra capacity, construct from the booking data and corresponding template data a booking request in a data format of the transport provider, and send the booking request to the transport provider.

83. A computer system according to claim 77, further configured to:

construct from the booking data and corresponding template data a booking request in a data format of the transport provider; and

send the booking request to the transport provider.

84. A computer system according to any one of claims 74 to 83, further configured to allow a forwarder to create or amend one or more of its allotment bookings.

85. A computer system according to any one of claims 74 to 84, further configured to:

receive a single data set for creating or amending a plurality of forwarder allotment bookings with a plurality of transport providers.

86. A computer system according to any one of claims 67 to 85, wherein a milestone plan is associated with the allotment template, the milestone plan associating at least one pre-journey milestone with at least one of said one or more route leg instances.

87. A computer system according to claim 86 dependent on any one of claims 74 to 85, further configured to:

associate the milestone plan with the allotment booking.

88. A computer system according to claim 86 or 87, further configured to:

allow a forwarder or transport provider to view the milestone plan associated with a template or booking.

89. A computer system according to any one of claims 86 to 88, further configured to:

allow a forwarder or transport provider to search for allotment bookings with at least one approaching milestone.

90. A computer system according to claim 89, further configured to:

receive a request from a forwarder or transport provider to search for allotment bookings or templates which have at least one approaching milestone;

search the record for the or each allotment booking or template; and

provide a representation of the or each allotment booking or template and associated milestone.

91. A computer system according to claim 90, wherein a period of time is defined in which the approaching milestone occurs.

92. A computer system according to any one of claims 86 to 91, wherein the milestones represent one or more of the following:

a reminder; and

/or

an aspect of a contract; and

/or

a deadline for booking creations, amendments and/or cancellations.

93. A computer system according to any one of claims 67 to 92, further configured to provide reports concerning the utilisation of allotment bookings.

99. A client computer system configured for remote communication with the computer system of any one of claims 67 to 98, said client computer system comprising:

a processing unit;

an interface unit for communication with said processing unit;

a memory unit; and

a display means for displaying information to a user, such as a forwarder or a transport provider, of said client computer system;

said processing unit comprising a user interface mechanism configured to receive user data input via said interface unit from said user, and to communicate said data to said computer system for processing thereby.

100. A computer system network comprising a plurality of client computer systems according to claim 99 and a computer system of any one of claims 67 to 98.

94. A computer system comprising

a processing unit;

an interface unit for communication with said processing unit; and

a memory unit;

wherein a centralised register of bookings is stored in the memory unit, each booking arranged between one of a plurality of transport providers and one of a plurality of forwarders and relating to booked capacity on a route between stations in a transport system, the computer system configured to;

associate a milestone plan with one or more of the bookings, the milestone plan associating at least one pre-journey milestone with the booking; and

allow a forwarder or transport provider to view said at least one milestone associated with one or more bookings.

96. A computer system according to claims 94 or 95, further configured to:

receive a request from a forwarder or transport provider to search for any bookings which have at least one approaching milestone;

search the record for the or each booking; and

provide a representation of the booking and associated milestone.

97. A computer system according to any one of claims 94 to 96, wherein the milestones represent one or more of the following:

a reminder; and

/or

an aspect of a contract; and

/or

a deadline for booking amendments and/or cancellations.

101. A method substantially as hereinbefore described with reference to respective embodiments and corresponding Figures of the Drawings.

102. A computer system substantially as hereinbefore described with reference to respective embodiments and corresponding Figures of the Drawings.

103. A computer program substantially as hereinbefore described with reference to respective embodiments and corresponding Figures of the Drawings.

104. A client computer system substantially as hereinbefore described with reference to respective embodiments and corresponding Figures of the Drawings

105. A computer system network substantially as hereinbefore described with reference to respective embodiments and corresponding Figures