Abstract:
A reservations system for hotel chains in which matrix arrays defining maximum rooms for sale, protected inventory, and matrices derived from these two, all by room-type/rate-category combinations. The system provides for generalized control of inventory for sale for an arbitrary number of room-types, rate-categories, etc. The system also allows blocking or protecting inventory by rate-category, room-type, or any combination. The system of the invention allows for either a central or a distributed view of inventory, and allows inventory to be controlled by the property and sold at any location without over-selling. The system of the invention provides the level of control necessary to handle the four major inventory control strategies that the hotel industry will likely require over the next ten years: total control centrally, central indicators and distributed inventory, totally distributed inventory, or a mixed mode of operation utilizing any combination of central or distributed inventory. In each case, the system of the invention provide a common, effective and complete solution.

Description:
This is a continuation of application Ser. No. 07/439,253 filed on Nov. 20, 1989, now abandoned. 
    
    
     A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent &amp; Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. 
     BACKGROUND OF THE INVENTION 
     Existing inventory systems for hotels today offer a limited capability for managing inventory effectively. Most of these systems are either based on a derivative of an airline seat reservation system, or are scaled-up versions of single property reservations systems. The systems currently used by major hotel chains are basically limited-control, declining inventory systems. They have defined numbers of buckets or inventory counters available for each day of inventory. The systems are limited to less than one year of inventory for a number of technical reasons. Many companies have extended their existing systems to allow for more room-types, and to include additional software to provide some inventory control and inventory blocking. However, these systems cannot provide general inventory availability, but require inventory to be assigned to sub-categories where it remains until reassigned for general inventory use. In addition, the price and rate calculation in these systems is combined with the inventory records, so that physical room-type and rate for the room are directly linked. 
     Existing systems that derive from single property reservations systems have similar limitations, in that they tend to focus on physical room-types and assign rates to those physical room-types. Inventory is kept by room-type, and limits on number of rates available for sale are usually not provided, except in special cases. When provided, they require additional code customized to the rate-category or the offering, and do not employ a general approach. 
     Airline systems today have sophisticated yield-management and rate capacity control algorithms. Based on observation of airline rate control practices, the availability of rates is managed by an off-line yield-management system, and rate availability is changed either manually or semi-automatically based on output from the yield-management system. In practical terms, a very large yield-management and rate capacity control operation is required to effectively manage and control availability of rates. 
     Therefore, current practice for hotel reservations systems can be described as accounting and control of physical room-types, with limited control of rates available for sale for each room-type. There are no existing reservations or inventory control systems in use in hotels or in the travel industry that provide the degree of control by room-type, rate-category or both that the present invention offers. 
     Other perishable inventory systems where the present invention is applicable would include rental cars, cruise-lines, event-ticketing, and any other application where the combination of a physical item for sale is often secondary to the rate at which that item is sold and the control of the availability of that rate for sale. For instance, in event-ticketing, the price on certain tickets could be changed as the event approaches or as certain other thresholds are met. 
     SUMMARY OF THE INVENTION 
     The system of the present invention is ideally suited to an automated link with the yield-management system that recommends and specifies the exact numbers of rates to be made available for sale. Since most yield-management systems tend to focus on opening and closing available rates, reflecting the limitation of existing reservations systems, the present invention provides the best possible target for a sophisticated yield-management system. The information provided by the invention, namely the specific room-type and rate-category counts sold to date, could be passed at any time to a yield-management system, providing far better information about inventory status and maximization of profit. 
     The system of the invention also allows for either a central or a distributed view of inventory. Current systems tend to use open/closed indicators at the central site, or allocations of inventory from the property. This system allows inventory to be controlled by the property and sold at any location without over-selling. As an example, some hotel chains keep inventory with free sale indicators that are updated manually by the property. When inventory and/or room-types are no longer available for sale, they need to be changed manually by the property. Some chains control all inventory and process all inventory transactions centrally. This approach provides a higher level of control, but incurs very large central operating costs, as well as very high communications costs. 
     In summary, the system of the invention provides the level of control necessary to handle the four major inventory control strategies that the hotel industry will likely require over the next ten years: total control centrally, central indicators and distributed inventory, totally distributed inventory, or a mixed mode of operation utilizing any combination of central or distributed inventory. In each case, the system of the invention provides a common, effective and complete solution. 
    
    
     BRIEF DESCRIPTION OF THE DRAWING 
     The invention will be more readily understood with reference to the accompanying drawing, wherein: 
     FIG. 1A and 1B are flowcharts showing the initializing of inventory performed according to the system of the invention; and 
     FIG. 2 is a flow chart showing the logical steps performed by the system of the invention during the daily selling and updating of inventory of the hotel chain, or the like. 
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     In the following, references to the drawings, where applicable, will be indicated in parentheses next to the particular logical step described. The algorithms used to implement the reservation system of the invention utilize a set of matrix data arrays and a set of rules based on the matrix arrays. Each matrix array is composed of i rows representing rate-categories and j columns representing room-types. A different array exists for each inventory-date, and may be differently dimensioned, i.e., each date may have a different number of rate-categories defined, and each season may have different room-types. Six logical arrays are defined as follows: 
     AA is the maximum number of rooms authorized for sale 
     A is the number of rooms currently available for sale 
     S is the number of rooms sold 
     B is the number of rooms blocked or protected 
     RB is the number of rooms remaining in a block (still protected) 
     F is a table of availability flags showing &#34;Open,&#34; &#34;Request,&#34; or &#34;Closed&#34; 
     AA and B are set by the reservations-manager (FIG. 1, Block 20). S is updated as rooms are sold or cancelled. A is calculated from number of rooms authorized and number sold. In addition to setting the maximums available for sale in AA, the reservations-manager can protect inventory by specifying a minimum available for a room-type/rate-category combination. The array B contains these minimums. The array RB is calculated from arrays B and S, and indicates the number of rooms remaining to be sold to satisfy blocks. The array F is set automatically based on arrays A and RB. 
     An arbitrary number of rows may be defined in the arrays for each inventory-date, based on the number of rate-categories available. A rate-category may be a special rate available for a specific group or type of guest (qualified rate) or may be one of many rates generally available (unqualified rate). 
     Most hotels would have the same room-types year-round, and hence would have the same number of columns. In some cases, a hotel might have seasonal or other reasons to change the number of room-types defined. Recognition of a consistent number of room-types and a variable number of rate-categories is a key element of the system of the invention. This observation is also the key to utilizing relational database methods to manage inventory. 
     The second key element of the system of the invention is that it allows the reservations-manager to place maximums (limits) and minimums (blocks) on total rooms, rate-categories, room-types, and/or specific combinations of rate and room-type. The user may limit the total number of rooms available for all room-types in a rate-category to be less than the sum of rooms specified as available for all room-types in that rate-category. The user may also limit the number of rooms available for a room-type to be less than the sum of the rooms available for that room-type in all rate-categories. This flexibility allows a reservations-manager to specify maximums available for each rate/room-type combination, and maximums for each rate and room-type, and allow the system to prevent overselling. 
     The system also allows the reservation-manager to block inventory for specific rate-categories (such as groups or special packages) and specify which room-types may be sold to satisfy the block. Finally, the invention allows the user to set an overall limit on the number of rooms available for each day, which may override the total number of rooms available for all room-types in all rate-categories. 
     The reservations-manager can specify four levels of limitations or maximums: 
     AA ij  is the maximum that can be sold for a specific rate 
     AA i0  is the maximum that can be sold for rate category i 
     AA 0j  is the maximum that can be sold for a room-type j 
     AA 00  is the maximum that can be sold for that day 
     The availability matrix array A is calculated from the matrix arrays AA and S, and represents the number of rooms left to sell. According to the invention, the sum of all room-types available for sale in a given rate-category (matrix row-sum) may exceed the maximum allowed for the rate-category. The practical explanation is that many room-types may be sold in the same rate-categories to satisfy customer preference. The advantage of the invention is that the reservations-manager does not need to make a specific, rigid allocation of rooms by physical room-type to a rate-category. 
     In practice, a warning message would be issued if the reservation manager has not specified enough rooms available for a room-type, a rate-category, or for the day, as follows, it being understood that the term SUM in the following refers to the iterative process associated with matrix analysis: ##EQU1## 
     In general, the reservations-manager would maintain a balanced or slightly oversold condition, so that the following relations would hold: ##EQU2## 
     If these above-logical relations do not hold, then an error messages will be generated (FIG. 1, Blocks 30, 32). 
     The system also guards against blocking more inventory than is available. For instance, if a reservations-manager tried to block more inventory in individual rate-categories than was available for a room-type, an error message would be generated (FIG. 1, Block 28). The system forces the following relations to hold: ##EQU3## 
     Referring to FIG. 2, in order to satisfy a request for &#34;r&#34; rooms for a span of dates, for room-type i and rate-category j, the following availability-relations must be true for each day (FIG. 2, Block 40, 42): 
     A ij  &gt;r inventory available for this rate/room-type 
     A i0  &gt;r inventory available for this rate-category 
     A 0j  &gt;r inventory available for this room-type 
     A 00  &gt;r total inventory available 
     Once the general availability of the required number of rooms has been established, additional rules must be applied to ensure that this sale will not violate a block. A block is not considered satisfied until the number of rooms sold is greater than or equal to the number blocked. The elements of the table RB indicate which blocks are still outstanding by calculating remaining blocked inventory as follows: ##EQU4## 
     In practice, &#34;overblocking&#34; would not be allowed, so that last relation would be: ##EQU5## 
     In order to handle blocking in all cases, including overcommitting by rate-category (block B i0  rooms for rate-category, and also set B ij  to the same number for all room-types checked) the following rules must be applied: 
     If enough inventory is available for the day, then sell any rate-category; else only free to sell blocked rates. 
     If A 00  -RB 00  &gt;r Then free to sell any rate (FIG. 2, Block 44). 
     If enough inventory is available for the rate-category or room-type, then free to sell any room-type or rate-category respectively. Otherwise, only sell room-types or rates that have &#34;remaining blocked&#34; inventory (FIG. 2, Block 46). 
     If A i0  -RB i0  &gt;r (FIG. 2, Block 48), then free to sell any room-type for rate-category i; otherwise, can only sell blocked room-types in this rate-category (FIG. 2, Block 50). 
     Similarly, for room-type j. 
     If A oj  -RB 0j  &gt;r (FIG. 2, Block 52), then free to sell any rate-category in room-type j; otherwise only sell rates with &#34;remaining blocked&#34; inventory (FIG. 2, Block 54). 
     A request for &#34;r&#34; rooms for a span of days must satisfy all of the following rules for each day: 
     
         ______________________________________General Availability Rules (FIG. 2, Block 42)______________________________________1)   A.sub.oo &gt; r            Inventory available for total hotel for            this day2)   A.sub.io &gt; r            Inventory available for rate-category .sub.i for            this day3)   A.sub.oj &gt; r            Inventory available for room-type .sub.j for            this day4)   A.sub.ij &gt; r            Inventory available for the specific            combination of rate-category .sub.i and room-            type .sub.j for this day______________________________________Protected Inventory Rules (FIG. 2. Blocks 44-54)______________________________________5)  A.sub.oo - RB.sub.oo &gt; r             Unblocked inventory available for the             day    or A.sub.oo - RB.sub.oo = r             If not, then only blocked inventory             can be sold, so blocked             inventory must be avail-             able for the rate-category,             room-type, and combination    and RB.sub.io &gt; k    and RB.sub.oj &gt; k    and RB.sub.ij &gt; k    where k &lt; r -    (A.sub.oo - RB.sub.oo)6)  A.sub.io - RB.sub.io &lt; r             Unblocked inventory is available             for this rate category    or A.sub.io - Only blocked inventory available for this    RB.sub.io &gt; r rate category, so blocked             inventory must be available for             the rate/room-type combination    and RB.sub.ij &gt; r -    (A.sub.io - RB.sub.io)7)  A.sub.oj - RB.sub.oj &gt; r             Unblocked inventory for this room-type    or A.sub.oj - RB.sub.oj &gt; r             Only blocked inventory available for this             room type, so blocked inventory and             must be available for             the combination    and RB.sub.ij &gt; r -    (A.sub.oj - RB.sub.oj)______________________________________ 
    
     Availability Flag Process 
     In most reservation systems, checking for availability of rates and room-types occurs much more often than the inventory sale or cancel process. Therefore, a table can be created that represents the availability status of all rates and room-types which results in a simplified availability checking process. This table can also be used to simplify inventory-handling and availability-checking for distributed inventory and manual systems, while maintaining the advantages of the reservation process of the invention. 
     The array F contains flags or semaphores that represent the current availability-status determined from the arrays A and RB. Each entry in F indicates &#34;open&#34; or &#34;closed&#34; based on the result of applying availability-rules to A and RB. Certain restrictions are applied when using F to determine current availability. The &#34;open&#34; status indicates that inventory is available for sale, but that &#34;free sale&#34; would be limited to &#34;K&#34; rooms. The constant K represents the free sale limit, or the maximum number of rooms that can be sold against an &#34;open&#34; indicator for each transaction. 
     The additional status indicator &#34;Request&#34; is used to indicate that inventory may be available, but a complete check is required before a sale can be made. For centralized systems, a complete check means applying all availability rules. For distributed inventory systems, a request must be made to the distributed system. 
     The flag process provides two key advantages. First, it reduces the overhead associated with checking availability, since availability is checked more often than changed. Second, it provides a consistent view of inventory in a distributed system by maintaining only one copy of the inventory data base. Also, the inventory data base may be kept centrally or may be distributed. In that way, availability can be checked anywhere, in any combination of systems while maintaining a consistent view of inventory to users at all locations. 
     Since the system of the invention is not affected by the location of the inventory data base, this system could be used for the four typical inventory distribution cases in any combination, as follows: 
     Centralized--all inventory is kept centrally for all properties, and all transactions are processed centrally. 
     Central control--inventory is kept centrally, but distributed locations such as properties can process transactions against availability flags. 
     Distributed--inventory is kept at distributed locations (e.g. properties or regional reservations centers) and availability flags or inventory allocations are maintained at a central location. 
     Mixed--combinations of all three above based on individual property or chain requirements. 
     The last mode of operation is the most promising for large hotel chains in the future, where imposing one of the other three modes of operation on all properties would be difficult, time-consuming or expensive. For multi-chain operators, using the best mode of reservations-operation for each chain will reduce operating cost and the development cost associated with &#34;compromise&#34; system solutions. 
     The system utilizes any conventional mainframe computer system with sufficient memory capacity for the central portion of the system. Minicomputers, microcomputers and personal computers may be utilized for the distributed portion of the system of the invention. Any conventional on-line system may be used for a centralized mode of operation. Other modes could use public or dial networks to implement the system. 
     A source listing of the computer program that may be stored in the computer memory of the system of the invention is given by way of example in the following Table I. ##SPC1## 
     While a specific embodiment of the invention has been shown and described, it is to be understood that numerous changes and modifications may be made therein without departing from the scope, spirit and intent of the invention as set forth in the appended claims.