NATIONAL CUSTOMER RECOGNITION SYSTEM AND METHOD

Abstract: A system and method for implementing a customer tracking and recognition program that encompasses customers' gaming and non-gaming activity alike at a plurality of affiliated casino properties. Customer information is accumulated at each affiliated casino through one or more LAN-based management systems, updated to a central patron database (CPDB) that is coupled to each casino LAN through a WAN, and made available to each affiliated casino property as needed. Customer accounts are automatically activated and provided with data from the CPDB when a customer from one casino property first visits an affiliated casino property. Customer accounts are updated with new activity data whenever a management system associated with the casino receives customer data from input devices, such as card readers, workstations, and dumb terminals, located at various venues throughout the casino. Customers are awarded points, based on their tracked activity at all affiliated casino properties. The point awards have a monetary value and are redeemable for gifts, meals, cash and the like, at any of the casino properties. The point awards may embody different promotional schemes in which point awards are adjusted to target different casino properties or different venues within a casino. Summary customer data, including point levels, is regularly updated to reflect ongoing customer activity at the casino property. This data is made available to employees at any affiliated casino property, as needed, to personalize customer services.

Description: NATIONAL CUSTOMER RECOGNITION SYSTEM AND METHOD Background of the Invention Technical Field This invention relates to the field of systems for tracking customer activity at casinos, and in particular, to systems for tracking customers' gaming and non-gaming activity across affiliated casino properties, for use in customer recognition and marketing programs. Background Art Substantially all casinos have implemented some form of customer tracking to identify and reward their valuable customers. These tracking programs often use the betting activity of a customer as the basis for awarding the customer complementary rooms, meals, event tickets, and the like ("comps"). Typically, these tracking programs are implemented by providing each customer with a casino membership card which includes a machine readable identification number specific to the customer. Each identification number has an associated customer account that is stored in the casino's computer system and updated to reflect customer activity. Customers need only insert their cards in slot machines or card readers associated with gaming tables or give their cards to a casino employee to have their betting activity monitored and reflected in their accounts. Customer cards may also be used to track customer activity at casino venues, such as special events, showrooms, and hotels, through card readers and computer terminals manned by casino employees. The growth of the gaming industry has created new challenges to the way in which customer tracking programs are implemented. Many states and territories have recently legalized casino gambling, and companies have built casino properties at these new gaming locations to meet the demand for gaming facilities. Despite the increased number of casino properties affiliated with a company, conventional casino management practices continue to treat these casino properties as autonomous, decentralized entities that compete with each other for valuable customers. In particular, customer tracking at each casino property is typically controlled by local management, and few if any attempts have been made to coordinate customer information across affiliated casino properties. For example, each casino has its own system that tracks betting data on the casino's customers. The property treats this betting data as confidential, in order to prevent competing casinos, including those affiliated with the property, from luring away valuable customers. Thus, customer tracking programs at affiliated properties remain fragmented, and conventional management practices provide little incentive to coordinate data accumulated by these tracking programs. Even if a casino company was to attempt some coordination of customer tracking programs at its affiliated casinos, the systems currently in place at various casino properties are too localized to integrate easily. Casino management systems are typically custom designed for each casino property, the customer data is limited to selected customer activity at the specific casino property, and the customer data accumulated by different computer systems within the same casino is often in different, incompatible formats. Thus, while each casino has useful data for its regular customers, there is no ready means for consolidating this data or making it available conveniently for use at other casinos. In short, there are both operational and technical barriers to coordinating customer tracking programs at individual casino properties into national, company-wide tracking and marketing programs. Summary of the Invention The present invention is a system and method for implementing a customer tracking and recognition program that encompasses customers' gaming and non-gaming activity alike at all casino properties affiliated with a casino company. Customer information is input to a management system associated with each affiliated casino property, updated to a patron database, and made available to each casino property as needed. This provides casino employees at each property with on-line access to the customer data necessary to implement cross-property incentive programs and to provide personalized services to customers, independent of which casino property the customer regularly visits. Marketing personnel have access to a more complete database of customer activity for developing and monitoring marketing programs, including offer management and redemption programs. The present invention allows customer data to be accumulated across all casino properties and made available at any casino property without overburdening the individual casino properties' computer systems with unnecessary data. A system in accordance with the present invention comprises a local area network (LAN) at each affiliated casino property and a wide area network (WAN) for coupling data among the casino LANs. A management system associated with each casino LAN receives customer data from card readers, workstations, and dumb terminals, located at various venues throughout the casino and couples the received data to a database that is accessible to all affiliated casino properties. In a preferred embodiment of the invention, a central patron database (CPDB) comprising customer accounts from all of the casino properties is supported on a central LAN that is coupled to the casino LANs through the WAN. In this embodiment, the management system may be a single, centralized system supported on the central LAN, a distributed system comprising local management systems associated with each casino LAN, or a hybrid system including both centralized and distributed components. The preferred configuration for the management system will depend on the data capacity of the WAN and the sizes of the various casino properties. In the preferred embodiment of the invention, the management system further comprises a casino management system to handle the day to day gaming transactions at various casino venues and hotel and event management systems to handle transactions relating to lodging and events, respectively. Data accumulated by the management system is updated to the CPDB, where it may be accessed by personnel at any of the casino properties through the WAN. When customer information is required at a casino property, the management system first checks a data store associated with the property, and if the data is not available there, it is retrieved from the CPDB. On-line access to a customer's activities at all of its casino properties allows the casino company to implement cross-property incentive programs, manage customer offer programs more effectively, and provide more personalized services to its customers. Data is available for a customer's gaming and non-gaming activities, giving the casino a more complete picture of the customer's expenditures while at the casino. For example, the system of the present invention facilitates and expands comping. By tracking customers' gaming activities at all of the company's casino properties, the present invention provides more complete data on which to base comps and provides the same, complete data to each casino employee, regardless of how frequently the customer visits their property. This allows valued customers to be recognized at any casino property affiliated with the company, regardless of which casino they patronize regularly. It also makes comping more consistent across different casino properties. In addition to comping, the present invention implements a point system that awards points to customers based on their tracked activity at all casino properties. Customer points earned at any of the affiliated casino properties may be redeemed for gifts or services at any of the affiliated casino properties. In effect, a customer's points represent a monetary value of the customer's activity, and may be used in place of cash at any affiliated casino, independent of where the points were earned. The point system may be used to target various properties or venues by weighting point awards according to the venue, the time period, or the casino property at which the points are generated. This allows new casino properties or venues at existing casino properties to be promoted by awarding extra points to customers who visit the targeted property or venue. The term "affiliated casinos", as it is used throughout this disclosure, is intended to indicate any of a number of different relationships between casino properties. For example, casinos may be affiliated through common ownership by a parent company, they may be owned by different companies operating under a cooperation agreement, or they may be under contract with the same provider for customer tracking services. Brief Description of the Drawings Fig. 1 is an overview of a national customer recognition system in accordance with the present invention. Figs. 2A, 2B, and 2C are block diagrams of the various system modules supported in the central database server and a casino property LAN, respectively, for different configurations of the customer recognition system. Fig. 3 is an overview of a casino LAN, indicating connections between the various input devices and distributed management systems supported on the casino LAN. Fig. 4. is a flow chart representing a method for tracking customer activity across all affiliated casino properties in accordance with the present invention. Fig. 5 is a block diagram of the system modules supported on casino LANs where a distributed patron database and management systems are employed. Detailed Description of the Invention The present invention is described in detail for a configuration of the national customer recognition system comprising a central patron database (CPDB) on a central LAN that is coupled to local management systems associated with each casino LAN. This configuration is particularly useful for companies that have already invested significant capital in local management systems for their casino properties, because it leverages these systems into a company-wide network through the addition of a CPDB. The system configuration employing a centralized management system with a CPDB and the system configuration employing distributed management and database systems are discussed in conjunction with Figs. 2C and 5, respectively. Referring first to Fig. 1, there is shown an overview of a computer network 100 for implementing the system and method of the present invention. Computer system 100 is shown comprising a central database LAN 110 and casino LANs 120(l)-120(n), each of which is associated with one of the affiliated casino properties. Central database LAN 110 and casino LANs 120(l)-120(n) are coupled through a wide area network (WAN) 102. Typically, central database LAN 110 will be located at a central facility of the casino company. In the following discussion, LAN 120 designates any one of casino LANs 120(l)-120(n) unless otherwise noted. Similar notation, i.e. unindexed reference numbers, is used for the various components of LANs 120(l)-120(n). It is understood that in a typical application, computer system 100 includes one or more LANs 120 for each casino property affiliated with the parent casino company, and all LANs 120 communicate with central database LAN 110 through WAN 102. This configuration allows each LAN 1 10, 120 to operate in a substantially independent manner until it requires access to data available on a different network. In the disclosed embodiment, central database LAN 1 10 comprises an ethemet 106 to which a central database server 1 12 and a marketing support server 1 14 are connected. An optional server 116 on LAN 110, supports a centralized management system (CMS 284, Fig. 2C) m the fully centralized configuration of the national customer recognition system A token ring 108 is also shown connecting ethernet 106 to WAN 102 Token ring 108 typically includes additional nodes, such as workstation 1 18, for marketing and local processing. Central database server 112 includes a central patron database (CPDB 220, Fig 2A), comprising customer accounts based on data originating at each casino property affiliated with the company For the embodiment employing distributed management systems (CMS 234, Fig 2B), central database server 1 12 is the only essential node on LAN 1 10. However, it is likely that in most implementations, other nodes such as workstations 118 and marketing support server 1 14 will be available for marketing analysis using data derived from CPDB 220 In the preferred embodiment of the invention, marketing support server 1 14 includes customer data from CPDB 220 stored in a manner that facilitates its use for marketing purposes For example, customer data may be sorted and stored in server 1 14 according to customer groups segmented by profitability, principal gaming location (property), or other marketing criteria On the other hand, customer data in server 1 12 is stored in a manner that facilitates rapid access by customer ID or name Referring now to Fig. 2A, there is shown a block diagram of various systems supported on central database server 112 These include an operating system (OS) 212, a database management system (DBMS) 214, a transaction management system 216', and central patron database (CPDB) 220 Transaction management system 216' supports messaging between casino LANs 120 and services on central LAN 110, such as CPDB 220, allowing them to exchange data as necessary In the disclosed embodiment, central database server 112 is an NCR 3555 computer, OS 212 is Unix SVR4, DBMS 214 is Informix 7 1, and transaction management system 216' is TOP END, available from AT&T/NCR. Central LAN 1 10 employs TCP/IP communication protocol for communications among the nodes of ethernet 106 and token ring 108. Referring again to Fig. 1, each casino property LAN 120 is shown with the same basic structure For purposes of illustration, LAN 120 is shown comprising a token ring 122 to which are connected computers 124, 144, 154, a gateway server 126, and workstations 128, 148. Dumb terminals 132 and PCs 172, which are connected directly to computer 124, are typically associated with gaming tables (Fig 3), and slot machines 130 are coupled to computer 124 through a slot computer 154 and token ring 122. Thus, all gaming-related activity is routed to computer 124 A person skilled m the art will recognize that LANs 120 associated with different properties may vary from this structure in order to accommodate special needs at different casino properties, without altering the nature of the present invention For example, a casino property lacking a hotel or event venue would not include computer 144 or workstation 128 and their associated lodging and event management systems, respectively. In addition, other LAN protocols, including ethernet and the like, may be used instead of token ring 122. Referring now to Fig. 2B, there is shown a detailed block diagram of LAN 120, indicating a casino management system (CMS) 234, lodging management system (LMS) 238, and event management system (EMS) 240, associated with various LAN nodes (computers 124, 144, and workstations 128, respectively), for monitoring, tracking, and controlling different areas of casino operations. In a preferred embodiment of the invention, CMS 234 includes Report Program Generator (RPG)-based programs for on-line transaction processing (OLTP) applications. These applications consolidate activity data at the casino property related to gaming, and access CPDB 220 to retrieve or store data, as necessary. For example, dumb terminals 132 and PCs 172 communicate customer gaming activity data from gaming tables to CMS 234. Dumb terminals 132 and PCs 172 may also be used for tracking customers' currency and marker transactions and for accessing gaming activity that is tracked through a slot computer 154. Automatic bet tracking at slot machines 130 is monitored by a slot monitoring system (SMS) 262 on computer 154, which couples accumulated bet tracking data to CMS 234 through token ring 122. In the preferred embodiment, bet tracking is accomplished through a card reader (not shown) associated with slot machine 130. A customer inserts his or her identity card in the card reader to initiate bet tracking and removes it to terminate bet tracking. A customer's betting activity at slot machine 130 is accumulated in SMS 262 until the session is terminated or an account status is requested by CMS 234, at which time the data is transferred to CMS 234 via LAN 120. LAN 120 may optionally include a pit tracking system (PTS) 258 to automatically track customer activity at gaming tables 134. PTS 258 is shown supported on a computer 174, which couples customer activity data to CMS 234 through LAN 120. PTS 258 uses card readers associated with player positions at gaming tables to track customers' betting activity. Estimates of betting activity are based on a player's time at a gaming table and the minimum bet at the table. Systems for automatically tracking betting activity at slot machines and gaming tables are well known in the art and are not described in greater detail here. In the preferred embodiment of the invention, a lodging management system (LMS) 238 is maintained on computer 144. However, there is no reason that CMS 234, LMS 238 and any other management systems could not be supported on the same computer or some different combination of computers. LMS 238 comprises the software necessary for managing hotel operations within the casino, including reservations, room service, and other activities associated with hotel operations. In a preferred embodiment of the invention, LMS 238 communicates with CMS 234 to search locally for selected customer information available on that system. However, LMS 238 may include its own local data store for customer data. Also shown in Fig. 2B is an event management system (EMS) 240 on workstation 128 and a restaurant/retail point of sale system (POS) 244 coupled to workstation 148. EMS 240 comprises software for handling ticketing information, reservations, and sales. POS 244 comprises accounting software for operating restaurants and retail venues within the casino property as well as software for transmitting charge information to other management systems. For example, data relating to meals charged to rooms or redeemed meal comps are coupled from POS 244 to LMS 238 and CMS 234, respectively, through LAN 120. The primary role of gateway server 126 is to provide a link between selected nodes of LAN 120 and central database server 112 through WAN 102 and LAN 110. For this purpose, gateway server 126 includes a LAN/WAN interface 280 that couples data packets between the communication protocols of LAN 120 and WAN 102 and another instance of transaction management system 216 that routes data packets between management systems 234, 238, 240 and selected services in CPDB 220. In the preferred embodiment of the invention, CMS 234 on computer 124 accesses CPDB 220 through transaction management system 216', 216, while LMS 238 and EMS 234 access CPDB 220 through CMS 234, as discussed below. An interface module 235 in CMS 234 provides communication links with transaction management system 216, as discussed below. In the disclosed embodiment of the invention, computers 124, 144 are IBM AS/400 computers, computer 154 is an IBM RS6000, gateway server 126 is an NCR 3410, workstations 128, 148 are based on '486 or better processors, and transaction management system 216, 216' is AT&T's TOP END. WAN 102 employs TCP/IP, an open communication protocol, while LANs 120 employ an IBM communication protocol, LU6.2. LU6.2 allows direct communication between LAN nodes, but it is not the preferred protocol for communications on WAN 102. In the preferred embodiment of system 100, LAN/WAN interface 280 includes the software necessary to couple message packets between LU6.2 and TCP/IP protocols for communications between central LAN 1 10 and casino property LANs 120. In particular, LAN/WAN IF 280 operates in conjunction with transaction management system 216, 216' to provide CMS 234, LMS 238, and EMS 240 with rapid access to customer accounts for all customers who have visited any casino property affiliated with the casino company and obtained a customer ID card. For this purpose, each customer ED card includes a unique ID number that is associated with a customer account in CPDB 220. In the preferred embodiment of the invention, the RPG applications of CMS 234 are implemented in the AS400 environment of computer 124. In order to facilitate fast, real-time communication between CMS 234 and CPDB 220, a messaging system is implemented as part of interface module 235 of computer 124 and transaction management system 216' of server 112. The messaging system functions as an application program interface (API) that allows the RPG applications of CMS 234 to communicate with CPDB 220 via transaction management system 216, 216', with LAN/WAN interface 280 coupling messages between the different communications protocols. In the preferred embodiment of system 100, customer data is transferred between LAN 120 and LAN 110 by means of message packets comprising header and data segments, the attributes of which are specified in a data dictionary associated with the messaging system. The data segments reflect the database schema of CPDB 220 and the header segments correspond to user provided service applications (not shown) accessed through transaction management system 216. These user provided service applications implement functions for coupling data to and from CPDB 220 in response to requests from CMS 234. A utility associated with the messaging system reads the data dictionary and defines data structures in the AS400 system environment suitable for passing data between the RPG applications of CMS 234 and the messaging system. A message building/parsing module uses data provided through the defined data structures to build message packets for transmitting requests to transaction management system 216, 216', which directs the request to the appropriate service application. A message building/parsing module associated with the service applications provides analogous services for communications with DBMS 214. The messaging system is described in greater detail in Appendix A. As noted above, the optimal architecture for system 100 will be determined in part by the volume of data traffic that WAN 102 can handle, i.e. the "bandwidth" of WAN 102. The embodiment of Figs. 1, 2A, and 2B, in which each casino LAN 120 includes CMS 234 for handling day to day transactions and communicating data to CPDB 220, balances the advantages of centralized computing systems with the bandwidth limitations of typical WANs 102. Where WAN 102 has sufficient bandwidth to handle real-time data transactions between CPDB 220 and a plurality of casino properties, local CMS 234 at each of the plurality of casino properties may be eliminated in favor of a centralized CMS 234 implemented on central LAN 110. Referring now to Fig. 2C, there is shown a simplified block diagram of an alternative, centralized configuration for system 100. In the configuration of Fig. 2C, local CMSs 234 associated with selected casino LANs 120' have been eliminated in favor of a central CMS 284 supported on server 116 on central LAN 110. In this embodiment of the invention, each casino LAN 120' includes one or more computers 124' for communicating with central CMS 284 over WAN 102. Since computers 124' merely provide access to central CMS 284, they may be workstations or PCs. Central CMS 284 handles day to day transactions for each of casino LANs 120', maintaining a separate data store for each LAN 120' under its management. The data stores of central CMS 284 for LANs 120' are periodically updated to CPDB 220 to maintain the centralized data current. Where the data capacity of WAN 102 is sufficiently, it may be possible to eliminate local CMS 234 from all LANs 120, 120'. Similar hybrid and fully centralized configurations may also be set up for LMS 238 and EMS 240. Another alternative to the configurations of Fig. 2A, 2B, and 2C is a fully decentralized configuration in which CPDB 220 is eliminated in favor of a distributed database. This configuration is discussed in greater detail in conjunction with Fig. 5. Unless otherwise indicated, the following discussion assumes system 100 is configured as indicated in Figs. 2A and 2B. Referring now to Fig. 3, there is shown the embodiment of system 100 including CPDB 220 and local CMS 234, with communications links between different nodes explicitly indicated. In the disclosed embodiment, for example, CMS 234 receives customer activity input directly from gaming tables 134, kiosks 136, and a customer information center 138. CMS 234 also receives customer activity data from slots 130 through SMS 262. Kiosks 136 are terminals located around the casino property that allow customers to check on their activity points or comp availability by inserting their customer ID cards. Customer information center 138 provides services to casino patrons such as membership information and arranging for "comps", as described in detail below. CMS 234 also provides data to each of these input devices. For example, casino employees at gaming tables 134 receive customer data summaries so they can determine whether the customer qualifies for a "comp" or simply greet the customer by name. LMS 238 receives customer data from a hotel desk 178 and reservations clerks 176 and provides customer account summaries to these locations for use by casino employees. EMS 240 also exchanges customer data with reservations clerks 176 and, in addition, exchanges customer data with events venues 174. In the disclosed embodiment, both LMS 238 and EMS 240 communicate with gateway server 126 through CMS 234, and gateway server 126 handles the data translation necessary to communicate with CPDB 220 via WAN 102. This communication topology facilitates searching among different management systems 234, 238, 240 for customer data, but it is not essential to the present invention. The same system could be operated with EMS 240 and LMS 234 communicating with gateway server 126 directly. In addition, where UNK-based casino, lodging, or event management systems are available, they may communicate directly with WAN 102. Also shown in Fig. 3 is a teleservices module 298 coupled to CPDB 220 through WAN 102. Teleservices module 298 represents a telephone-based system that allows customers to arrange travel plans at some or all of the affiliated casino properties. By connecting teleservices module 298 to WAN 102, operators can access customer data in CPDB 220 in real-time. This allows operators to determine, for example, whether a customer arranging a trip to one of the affiliated casino properties qualifies for a comp room, a room upgrade, or the like. Customer accounts in CPDB 220 include detailed information on the customer's preferences, interests, credit rating, win profiles, and accumulated activity points. Win profiles are determined according to gaming data accumulated at any of the casino properties affiliated with the parent company through input devices such as slot machines 130 and dumb terminals 132 associated with gaming tables 134. Activity points are determined in part by gaming activity but may also be augmented by sweepstakes and various other promotional programs. Other customer data relating to non-gaming activity may be tracked through various input devices, including workstations 128, 148 supporting EMS 240 and POS 244, and made available to the marketing department for evaluation and analysis. These features of customer accounts are discussed in greater detail below. In order to provide rapid access to essential customer data while minimizing data storage requirements for casino properties, each CMS 234 maintains accounts for regular customers in a local data store. With this configuration, CMS 234 accesses CPDB 220 whenever a customer registers activity in any of the casino venues and no customer account data is available locally. For example, when a customer presents his or her membership card to check into the hotel at the casino property, LMS 234 checks with CMS 234 for a local customer account. Currently, LMS 238 does not maintain a local data store, but if expanded to do so, LMS 234 would check its local data store before checking that of CMS 234. In general, customer data may already be available locally from CMS 234 if the customer has visited the casino property before or if, for instance, a new customer played slot machines 130 before checking in to the hotel. In the first case, static customer data, including the customer's name, address, credit rating and the like, would be maintained in CMS 234 from the previous visits. In the case of a new customer, CMS 234 will have already retrieved a summary of the customer's account data from CPDB 220, as described below, and LMS 238 may access the data from CMS 234. If the customer data is not available locally, as when a customer new to the casino property checks into the hotel first, LMS 238 will send a data request to CMS 234, which forwards it to CPDB 220 using the messaging system and transaction management system 216, 216'. This transaction is carried out on-line in order to provide rapid access to a summary of basic customer information such as the customer's address, credit status, gaming points, theoretical win profile, and recent trip activity. Ready access to this customer data allows casino employees to make the check-in process both more efficient and more personalized for the customer, enhancing the customer's overall experience and making him or her more likely to return. Throughout the customer's stay at the casino property, the customer's account will be updated to reflect the customer's activities at the various casino venues. For example, when the customer inserts his or her ID card into a slot machine 130, the ID number is read, the customer's betting activity is monitored, and the account updated to reflect the activity. Similarly, if the customer purchases an event ticket or redeems customer activity points for a meal, workstations 118, 148, respectively, provide the ID number and transaction data to CMS 234, which updates the customer account to reflect the transaction. LAN 120 thus allows all of the customer's activity at the associated casino property to be tracked, which in turn provides a more accurate picture of the customer's value to the casino. The cross-property nature of system 100 makes the accumulated customer data available at whichever casino property the customer decides to visit. In order to maintain all account data up to date, all data processed by local management systems CMS 234, LMS 238, and EMS 240 is periodically updated to CPDB server 112 in a batch process. This update synchronizes data in all storage locations, i.e. CPDB 220 and local stores associated with CMSs 234, to ensure that employees at any casino property have access to the latest data. When this configuration is employed with a WAN 102 having limited bandwidth, data synchronization is typically done when traffic on WAN 120 is low, in order to minimize any interference with on-line data access transmissions. Data must also be synchronized in the configuration of Fig. 2C, with central CMS 284 periodically updating CPDB 220 from the data stores associated with LANs 120'. However, data traffic generated by these updates is limited to central LAN 120 and does not impact the data traffic on WAN 120. The seamless flow of data supported by the present invention reinforces the customer's perception of the national brand associated with the parent company and the activity point system provides additional incentives for the customer to patronize the casino's properties in different locations. In the absence of the method of the present invention, there is no record of the customer's activities at other casino properties and, consequently, there is no opportunity to leverage the data already accumulated on the customer to affirm the corporate links between the properties. Referring now to Fig. 4, there is shown a flow chart of method 400 in accordance with the present invention for tracking customer activity data and accumulating activity points across casino properties. For purposes of illustration, the discussion assumes that the customer activity data is being directed to CMS 234, i.e. gaming activity of some sort is being tracked. Method 400 is initiated when a triggering event, such as insertion of an ID card into a slot machine 130 or entry of an ID number or name into a dumb terminal 132 is detected 410. The customer ID number (or name) is read 420 by CMS 234, which determines 430 whether it has already activated the associated customer account. If the account has not yet been activated by CMS 234 at the current casino property, the customer account is activated 434 in CMS 234, a request for summary data from the customer's account is forwarded 438 to CPDB 220, and the activated account is updated 442 with the summary data from CPDB 250. If, on the other hand, it is determined 430 that an account is already activated, the summary data is already available and the customer account is thereafter updated 444 to reflect any new activity. π It is noted that in the centralized configuration of system 100 (Fig. 2C), central CMS 284 maintains data stores for each LAN 120 it handles. Consequently, the checking process described above occurs with centralized CMS 284 as well. Gaming and non-gaming activities are treated differently, and updates occurring at step 444 typically include non-wagering activities related to gaming. For example, a customer's account may be updated at this point to reflect redemption of activity points, redemption of a comp voucher, or currency or marker transaction (credit advance). In addition, some wagering related data may be updated 444 at this time. For example, the start time of a betting session or the venue at which a wagering activity is occurring may be reflected to the customer's account. As noted above, activity point awards are based on a number of criteria and these may be adjusted to target different casino properties or venues. At step 448, method 400 determines whether the monitored activity is one for which any points are awarded. In the preferred embodiment of the invention, non-gaming activity, such as hotel and event activity, may be tracked for accounting and marketing purposes. Once non-gaming activity has been reflected in the customer account, method 400 returns to await 410 the next triggering event. In the current embodiment of the invention, points are awarded for gaming activities, but this may be readily expanded to include point awards for non-gaming activities. With respect to gaming activities, points awards are determined when the activities are completed or an account status is requested. For example, when a customer initially inserts an ID card into a slot machine 130, method 400 will be triggered 410 to record the event. However, the activity points awarded are based in part on how much the customer wagers, and this is not determined until the customer removes his or her card from the slot machine 130 or an update request is received by SMS 262. If the current triggering event is, for example, a card removal or status request, the customer account is updated 450. Otherwise, method 400 returns to step 410 to await the next triggering event. For this reason, SMS 262 (Fig. 1 , 2B) maintains betting data until one of these events trigger it to forward the data to CMS 234 for updating the appropriate customer account. Referring again to Fig. 4, points are updated 450 when a betting session is completed or an account status requested, and method 400 checks 452 a table to determine the number of points to be awarded. For example, the company may promote a new casino property by awarding bonus points for all gaming activities at the new property, or the casino may award bonus points for gaming at a new venue that is being promoted. In any case, method 400 determines 452 the appropriate point level and adjusts 454 the point tally in the customer's account accordingly. Betting activity is also reflected 458 in a separate field for purposes of determining a customer's comps. Unlike activity points, comp data is based solely on the historical amount of wagering done by the customer and does not reflect point weighting or other promotional schemes. When any point and comp adjustments have been made, method 400 returns to await 410 the next triggering event. CPDB updates 460 are required to synchronize data in the embodiment of system 100 employing distributed CMSs 234 and centralized CMS 284 (Figs. 2A and 2B, and Fig. 2C, respectively). In the former configuration, these updates periodically transfer accumulated data from all accounts in local management systems (typically, CMS 234) to CPDB 220. In the preferred embodiment of this configuration, updates to CPDB 220 are scheduled at least once every twenty four hours at time periods when activities on casino LANs 120, central LAN 1 10, and WAN 102 are low. Where WAN 102 has a high bandwidth, data updates may be made without regard to other traffic on WAN 102. For the reasons discussed above, CPDB updates from the data store of central CMS 284 do not impact data traffic on WAN 102 and may be scheduled more flexibly. Method 400 balances the casino company's need for rapid on-line access to customer information from all of its casino properties with the personnel and monetary costs of maintaining multiple large databases. Instead of duplicating all customer accounts at all casino properties, copies of a customer's account are maintained only on central database server 112 and in data stores of CMS 234, CMS 284 associated with those casino properties visited by the customer. On the other hand, the data is available from central database server 1 12 whenever it is requested by another casino property. In the preferred embodiment of the invention, static customer data is maintained on local CMS 234 for a period of between six months and two years, depending on each casino's policy. If no activity is registered by a customer during this period, the local account may be purged. Computer system 100 and method 400 provide the infrastructure for a national customer recognition program for attracting and retaining customers. They also provide the raw customer data on which the casino company can base its marketing decisions and through which the company can launch new marketing programs. Customer recognition awards may be based on different subsets of customer data accumulated through and stored on system 100. The customer recognition program based on activity points has already been mentioned. A customer accumulates points in his or her customer account according to his or her activity at all venues of all casino properties and according to any promotions currently being run by the casino or its parent company. The accumulated points represent a monetary value associated with the customer's activities and may be used in place of cash within any of the affiliated casinos. Thus, in addition to the already noted benefits of the point system, it contributes to the establishment of a cashless, paperless business environment. In order to provide an incentive for customers to accumulate points, points may be earned at any casino property affiliated with the company. The cross-property nature of point accumulation encourages customers to visit casino properties affiliated with the parent company when they travel, since this activity contributes to their rewards no matter which casino property is the source of the points. Point awards may be structured in a variety of ways to target specific activities. For example, bonus points may be awarded to customers who visit at least two affiliated casino properties within a given time period. Point awards may also be based on a tiered system, under which customers accumulate points for their gaming activities at rates that increase as their point totals increase. In general, point awards may be instituted for different time periods and for different properties, according to the marketing goals of the casino and the parent company. Accumulated points may also be redeemed at any casino property affiliated with the casino company. Using system 100, a casino employee can call up data indicating the accumulated points of any casino customer, regardless of the property at which the points were earned and regardless of whether the customer is a regular at the casino property. For example, a customer who has been accumulating points through regular visits to a Las Vegas casino can visit an affiliated casino in New Jersey and redeem his or her accumulated points for goods or services at the New Jersey casino. Point awards also encourage customers to use their ID numbers at any of casino venues of the affiliated casino properties that offer customer tracking. This enhances customers' interest in participating in tracking programs and provides the casino company with more data on which to base its marketing decisions. Thus, the point system can be used to both recognize customers for their patronage and to market different facilities of the company. Comping is another customer recognition program that is supported by system 100 and method 400. Comps are awarded to a customer according to the customer's average daily theoretical win, which is an estimate of the casino's average daily winnings from the customer. The level of comps available to a customer is based on the casino's theoretical win from different gambling activities and the customer's historic level of these gambling activities. For example, on average a casino will win a statistically determinable amount of money, i.e. the theoretical win, from a customer who bets an average of $5000 per trip on blackjack. If the customer's theoretical win profile is large enough, the casino may "comp" the customer a free night's lodging, allowing the customer an additional day of gaming. Customer betting activity accumulated by system 100 is crucial to comping customers at a level commensurate with their expenditures, since it provides the raw data on the customer's betting activity. Casino employees have some discretion in awarding comps and the practice may vary from one casino property to another. System 100 helps eliminate some of the vagaries introduced by the discretionary nature of comping by providing the same customer data to employees at all casino properties visited by a customer. This ensures that comping decisions will at least be based on consistent estimates of the customer's average theoretical win profile. Regular customers at one casino property of the company who visit a new casino property of the company are more likely to be "comped" at a level consistent with their play at their regular casino property. The national character of the present tracking system also means that the average daily wager figure will include a larger number of data points, since the customer's gaming activities at all casino properties are included. Estimates based on this data should be that much more accurate. Customer data accumulated by system 100 is also used in tracking customer offers to determine the validity of outstanding offers and the profitability of those offers for the casino. These offers can be entered into a customer's account to indicate their availability to the customer, and the customer's account can be updated as necessary when an offer is redeemed. In addition, data accumulated in CPDB 220 during the visit in which the customer redeems the offer can be used to determine whether or not it is profitable for the casino to repeat the offer or make additional offers. For example, the casino may send to selected customers offers for a free nights lodging at one of its properties if the customer stays for at least two nights. In certain cases, the customer's incremental expenditures for the extra day's stay may not justify repeating the offer to that customer. Information gathered on customer activity associated with an offer may also allow the marketing department to better target their offers. Referring now to Fig. 5, there is shown a simplified block diagram of an alternative embodiment of system 100, in which both management system processing and database operations are distributed among LANs 120. This embodiment is illustrated using four LANs 120(1)- 120(4) coupled to WAN 102, but the number of LANs 120 may be greater or less than this. LANs 120(1)- 120(4) include local CMS 234(1 )-234(4), respectively, each of which has an associated local data store. The local data stores of CMS 234(1) - 234(4) form the distributed database for this embodiment of the present invention. Each local data store comprises a local guest master list for the corresponding casino property and a local cross- reference list that includes selected customer data from every other affiliated casino property. For example, the local guest master list of CMS 234(1) comprises data for all casino customers who received their identity cards at the associated casino property (property 1 ). The local cross- reference list of CMS 234(1) includes data sections for properties 2, 3, and 4, which comprise customer data for any customer that received their identity card at property 2, 3, or 4, respectively, and subsequently visited property 1. CMS 234(1) also includes virtual files 2, 3, and 4 for properties 2, 3, and 4, respectively, through which data on customers who are not listed in either the local master list or local cross-reference list may be accessed. In effect, virtual files 2, 3, 4 on CMS 234(1) represent local master lists residing on CMS 234(2), CMS 234(3), and CMS 234(4), respectively, that are accessed by CMS 234(1) through WAN 102. In this embodiment of the invention, a customer of a casino is assigned an identification number including a property field that indicates the casino at which the customer's account originated, i.e. where the card was issued. When a customer of property 1 uses his or her card at property 1, the property field indicates to CMS 234(1) that the customer's account data is accessible through the local master list of CMS 234(1). On the other hand, when this customer visits property 3, the property field signals that CMS 234(3) should check the data segment associated with property 1 in the local cross-reference list for the customer's account. If it is the customer's first visit to property 3, there will be no account data in the property 1 data segment of the local cross-reference list and CMS 234(3) will use virtual file 1 to access the local master list of CMS 234( 1 ). When the data is retrieved from CMS 234( 1 ), it is stored in the property 1 data segment of the local cross-reference list of CMS 234(3), where it is updated with the customer's activity during his or her visit to property 3. In the system of Fig. 5, where a distributed database configuration is employed, data synchronization is particularly important to ensure that all activity data, including points and comp availability, is reflected in a customer's account and is available at any of the affiliated casino properties. For example, when a customer from property 1 visits property 3, the data on the customer's activity at property 3 is added to his or her account in the property 1 segment of the local cross reference list of CMS 234(3). Data synchronization ensures that this new data, including points or comps that are earned or redeemed during the visit, is available when the customer visits any other property. Synchronization may be accomplished in a number of ways. For example, the customer's accounts at each casino property may be periodically updated to reflect any activity recorded by the customer at any of the affiliated properties, so that each property visited by the customer has a complete set of the latest data. Alternatively, all changes to a customer's account on any guest master list may be periodically updated to the customer's principal account, i.e. the account at the issuing property. In this case, each visit to a different property requires updating of the customer account on the guest master list with the account data from the customer's principal account. Provided these or similar procedures are implemented to ensure the coherency of the distributed database, the point and comp system may be implemented in the manner described above. There has thus been disclosed a system and method for collecting customer data across all of the casino properties of a company, accumulating the collected data in a patron database, and making the accumulated data available at any casino property when triggered by a customer visit to the casino property. The system provides an infrastructure for implementing across all affiliated casino properties a point system that rewards customers for the gaming activities and allows targeting of different casino properties and venues for marketing purposes. The system also makes available to casino employees the same customer data, independent of which casino property the customer visits regularly. This allows customers to receive personalized service and to be rewarded in accordance with their value to the casino even when visiting new casino properties. What is claimed is: Appendix A This appendix describes the messaging system employed in the preferred embodiment of computer system 100 (Fig. 1). A numbering scheme is employed in the appendix which is different from that employed in the body of the specification. Correspondence between different elements may be determined from Table Al. In addition, corresponding elements serving comparable functions in the specification and appendix are indicated in Table Al . Referring first to Fig. Al, there is shown a block diagram of a networked computer system A 100 that includes a messaging system A 120 for communications between application programs on proprietary and open system platforms. Computer system A100 comprises a first computer Al 12 based on a proprietary system architecture, a server A 192 based on an open system architecture, and a gateway server A 152 for connecting the different system architectures. The proprietary system architecture of first computer A 112 is represented by network protocol A 130, and the open system architecture of server A 192 is represented by network protocol A160. In the disclosed embodiment of system A100, the open system architecture is UNIX, Windows, or the like, the network protocol A 160 is TCP/IP, the proprietary system architecture is IBM's System Network Architecture (SNA), and network protocol A 130 is IBM's SNA LU6.2 First computer Al 12 includes an RPG application Al 10, messaging system A 120, and network protocol A 130. Messaging system A 120 acts as an application program interface (API) between RPG application Al 10 and a transaction management system A 150 on gateway server 152. Transaction management system 150, in turn, provides access to transaction services A 170 on open system server 192. Transaction services 170 represents the different services that may be accessed by RPG application Al 10 and the means for accessing these services. Gateway server A 152 includes a network services module A 140, transaction management system A150, and an interface module A142. When triggered by messaging system A120, network service module A140 allocates a conversation between messaging system A 120 and transaction management system A 150 by means of interface module A 142. A conversation is a logical connection that allows communications between applications on different nodes to proceed, while hiding the details of the underlying communication protocol from the communicating applications. In the disclosed embodiment, the allocated conversation carries message packets between messaging system A120 and transaction management system A150 using network protocol 130. The communication link between RPG application Al 10 and transaction services A170 is completed by a dialogue between transaction management system A 150 and transaction services A 170 based on network protocol 160. The message packets generated by messaging system A 120 include parameters, i.e. data and control information, necessary to activate one of transaction services A 170, carry on communications with the activated service, and terminate it. Referring now to Fig. A3, there is a block diagram of a transaction service A 170, which comprises an instance of transaction management system A 150, including a client-server interface (CSI) A 154, a service application A310, a message conversion system A304, and a database management system (DBMS) A380. Service application A310 is a user provided module that includes functions for accessing data from DB A390 through DBMS A280. In the disclosed embodiment, DBMS A380 is Informix 7.0, and transaction management system A 150 is AT&T's TOP END, both of which conform to the X/Open distributed transaction processing (DTP) XA interface. Transaction management system A 150 also conforms to the DTP TX interface for communications with service application A310. Referring now to Fig. A2, there is shown a block diagram of messaging system A 120 comprising a MSG module A210, a MSG Build/Parse module A220, a List_Build module A230, a memory management module A240, an inbound/outbound message buffer A218, and defined data structures A250 for coupling data between messaging system A 120 and RPG application Al 10. In order to make messaging system A 120 portable between platforms, component modules A210, A220, A230, and A240 are written in the C programming language. MSG module A210 includes a MSG API A212 through which RPG application Al 10 accesses functions A214 for initiating and terminating conversations with transaction management system A 150 and for requesting transaction processing services from server applications A310 accessed through transaction management system A 150. In the disclosed embodiment, MSG module A210 also includes registered functions A216, which manipulate data between defined data structures A250 and MSG buffer A218 as described below. Build/Parse module A220 comprises a Build/Parse API A222, a data dictionary (DD) A228, message building/parsing functions A224, and a registered function (RF) API A226. Build/Parse API A222 provides MSG module A210 with access to platform independent message building/parsing functions A224. DD A228 specifies the fields and field attributes of data segments that are recognized by an open system resource being accessed by RPG application Al 10. As discussed in greater detail below, DD A228 contributes to the flexibility of messaging system A 120, by providing a mechanism for altering its message building capabilities without requiring recoding of RPG application Al 10 or server applications A310. RF API A226 provides Parse/build module A220 with access to registered functions A216, which manipulate RPG data in defined data structures A250. Registered functions A216 are specific to the data types of a platform, and including registered functions A216 in MSG module A210 removes any platform-dependence from Build/Parse module A220. For example, a substantially identical build/parse module A322 (Fig. A6) is employed by server application A310 on the open system platform. Build/Parse module A320 parses request message packets from RPG application Al 10 and builds response message packets to RPG application Al 10. List_build module A230 and MMS module A240 provides linked list building and memory allocation functions, respectively, for MSG module A210 and Build/Parse module A220. For example, when RPG application Al 10 is initialized, it identifies to MSG module A210 all defined data structures it employs. MSG module A210 checks that the defined data structures have the proper number of parameters and calls List_build module A230 to generate a linked list of pointers to the defined data structures. List_build module calls on MMS module A240 as needed to allocate memory for the linked list. List_Build module A230 and MMS module A240 are also used by MSG module A210 to eliminate the linked list when RPG application A 1 10 is terminated. Typical service applications A310 provide RPG application Al 10 with functions for searching and writing data to database A390 (Fig. A3). In order for RPG application Al 10 to communicate with database A390, messaging system A 120 must employ in its data packets, data having attributes consistent with the columns of database A390. Since RPG application A 110 is the ultimate source of data, messaging system A 120 must include some means of ensuring consistency between the attributes of the data segments employed by RPG application Al 10 and those of database A390. This is the function of defined data structures A250 and DDs A228, A328. Messaging system A120 provides utilities for generating DD A228 and DD A328 (Fig. A6) and defined data structures A250 from a single source that includes attribute definitions consistent with those of database A390. This ensures that messaging system A 120 and service application A310 support the same vocabulary, which in turn ensures that RPG application Al 10 and database A390 can communicate. The single source from which DDs A238, A328 and defined data structures A250 are generated is ASCII definition file (ADF) A260. Referring now to Fig. A4, there is shown a block diagram indicating the relationship among ADF A260, DDs A228, A328, and defined data structures A250. ADF A260 is a human-readable file that includes descriptions of the attributes of every field of every data segment in the system. As noted above, the attributes of a segment correspond to the columns (attributes) of the database A390. ADF A260 also includes a header segments, which are used to indicate which service application A310 is being requested by RPG application Al 10. Header segments include control information for error codes and messages, and those header segments associated with service applications A310 that require data input from RPG application Al 10, have appended the data segments corresponding to the required data. ADF A260 also includes a list of restricted segments, which are segments that may only be used by selected service applications A310. ADF A260 is typically generated through a GUI design tool, which in the preferred embodiment of the invention, is Visual Builder Tool (VBT). In essence, ADF A260 specifies the vocabulary understood by database A390. Also shown in Fig. A4 is a Data_Structure Utility (DSU) A270 which is used to generate defined data structures A250 from ADF A260 whenever ADF A260 has been modified. In particular, DSU A270 reads ADF A260 and uses List_Build module A230 to generate a linked list of fields and a linked list of segments from the entries in ADF A260. For every segment in the segment linked list, DSU A270 retrieves attributes of the component fields from the field linked list and writes the information to a DDS A250. Defined data structures A250 are then written to a file, which is linked to RPG application Al 10 and messaging system A 120 as an externally defined data structure. There are two defined data structures for each data segment defined in ADF A260. Application request data structures (ARDS) A252 are loaded with data by RPG application Al 10 to provide messaging system A 120 with the data it needs to a build a message to a service application A310. Application response data structures (ASDS) A254 are written by messaging system A 120 to communicate a response from service application A310 to RPG application Al 10, following parsing by Build/Parse module A220. An single application control data structure (ACDS) A256 is used by RPG application Al 10 to communicate service application requests to messaging system A 120. Also shown in Fig. A4 is a utility, DDBLN A280, that reads ADF A260 and generates DD A228 as a binary file sorted by segment names. DDBIN A280 also creates a summary information field for DD A228, including the total number of segments, offsets into DD A228 for alphabetically sorted segment groups, and an offset into the file for a restricted segment file (RSF). DD A228 may be linked into Build/Parse module A220 as an include file. Alternatively, the contents of DD A228 may be read into a segment cache A325 (Fig. A6) associated with Build/Parse module A220, as needed, to facilitate access to segment information. This latter alternative is employed in messaging conversion module A304 (A3) which is used for message packet building/parsing by service application A310. Referring now to Fig. A5, there is shown a representation of an ACDS A256 that is used by RPG A 1 10 to request services of messaging system A 120. ACDS A256 is also used by messaging system A 120 to provide information on the status of requested services to RPG application Al 10. A single ACDS A256 is used by RPG application Al 10 to indicate which of transaction services A 160 is being requested. Details of the requested service are provided in the following fields of ACDS A256: (1) Request Service Name, (2) Sending Segments, and (3) Hold Context Flag. Request Service Name is a field in which the name of a service application A310 available through transaction management system A 150 is specified. A corresponding header segment defined in ADF A260 is used by messaging system A 120 to indicate to transaction management system A 150 the type of service being requested. As noted above, some service applications A310 require that RPG application Al 10 provide data along with the service request. In these cases, the Sending Segments field is used by RPG application to specify which ARDSs A252, if any, contain the required data. Each such ARDS A252 is specified in the Sending Segments field by the Segment Name of the data it contains. In the preferred embodiment of the invention, the name of each data segment to be sent is concatenated and delimited by a pipe ("I"). For example, where data from three ARDSs A252 corresponding to a name (NAME), business address (BUS), and home address (HOME) will be sent to service application A310 specified by ACDS A256, the Sending Segments field will be NAMEIBUSIHOME. Data provided in response to a service request is sent from service application A310 to messaging system A 120 as data segments. Messaging system A 120 makes any necessary data conversions and forwards the converted data segments to RPG application Al 10 using the corresponding ASDSs A254. Hold Context Flag is set when RPG application Al 10 will retain an on-going conversation with a service application A310 as, for example, when RPG application Al 10 will submit sequential service calls to service application A310. The Results Services fields of ACDS A256 comprises Return Status Code, Initialized Flag, and Control Flag fields. Messaging system A 120 uses these to indicate to RPG application A 110 the status of a service request. Return Status Code is zero, unless an error has occurred in the Service Request. Initialized Flag is set when messaging system A 120 is properly initialized and is zero otherwise. Control Flag indicates the status of messaging system A 120. It is zero by default, four when a service application A310 is currently holding context, and some non-zero value other than four when a failure occurs in messaging system A 120. The interactions between RPG application Al 10 and messaging system A 120 will now be described from initialization through termination of RPG application Al 10. As noted above, messaging system A 120 is initialized through a function call from RPG application Al 10 during its initialization. The initializing function call includes a parameter list specifying the segment name, segment address, and number of occurrences of each ARDS A252 and ASDS A254 used by RPG application Al 10 to send data to and receive data from MSG module A210. The parameter list also specifies the name and address of ACDS A256 used by RPG application Al 10 to communicate control information to MSG module A210. Addresses for ARDS A252, ASDS A254, and ACDS A256 (collectively, DDSs A250) are in shared memory location Al 14. On initialization, MSG module A210 first checks that DDSs A250 are specified properly (3 parameters for each ARDS A252 and ASDS A254 and 2 parameters for ACDS A256). MSG module A210 then calls initializing functions in Build/Parse module A220, List_build module A230, and MMS module A240, initializes a conversation with transaction management system A 150 via network services A 140 and IF A 142, and waits for a verification message that the conversation has been established. At this time, transaction management system A 150 establishes a dialogue with transaction services A 160 on open system server A 192. MSG module A210 then calls List_Bιιild module A230 to generate a linked list of pointers to DDSs A250, and List_Bιιild module A230 calls MMS module A240 as needed to allocate memory for the linked list. Once conversation/dialogue links have been established between messaging system A120 and transaction management system A150, RPG application Al 10 accesses a requested service application A310 of transaction services A 160 through transaction management system A 150, using messaging system A 120 as an application program interface (API). RPG application Al 10 initiates a request for services by loading the Request Service Name and Sending Segments List fields of ACDS A256 with the segment name of the service being requested and the segment names of any data being sent to the requested service. RPG application Al 10 also loads each ARDS A252 named on the Sending Segments List with the data to be sent. When ARDSs A252 and ACDS A256 are loaded, RPG application Al 10 calls the request function in MSG module A210, including the names of ACDS A256 and ARDS A252 in a parameter list associated with the function call. MSG module A210 use the request function to clear the Results Services fields of ACDS A256 and read the Request Service Names and Sending Segments List fields of ACDS A256. MSG module A210 writes a control/status header (see below) to message buffer Al 18, specifying Request Service Name, a user identification (userid), and status data for transaction management system A 150. MSG module A210 also calls the Build MSG function in Build/Parse module A220 with the parameter list specifying the names of the data segments and the location of message buffer A218. Build/Parse module A220 handles the conversion and manipulation of data between the DDSs A250 identified in the parameter list and message buffer A218. As noted above, the Build/Parse MSG functions of module A220 use registered functions A216 to accomplish the actual data manipulation between DDSs A250 and message buffer A218. For outbound messages, the Build MSG function uses DD A228 to determine the required form for each segment to be included in the message packet and makes the necessary format conversions. DD A228 is also used on inbound message packets to convert data to a format appropriate to the operating system of the AS/400. The addresses of DDSs A250 are determined from the link list generated on initialization. The message packet generated by messaging system A 120 has the following form: (I) I error I control I function code 1 userid 1 data I. < control/status > I < — application data — > The header, comprising error, control, function code, and userid fields, provides the routing and status information necessary to transfer the service request and associated data of RPG application Al 10 from messaging system A 120 to requested service application A310. In particular, the error field includes error codes for tracking purposes, the control field specifies the status of communications with transaction management system A 150, the function code field specifies which service application A310 is being requested, and for security checking purposes, userid identifies the person(s) using RPG application Al 10. The data field comprises the service name and any application data, suitably formatted, that is being transferred between RPG application Al 10 and service application A310. As discussed above, this data is loaded by messaging system A 120 using Parse/Build module A220. Once the message packet has been completed, MSG module A210 calls a send/receive function to forward message packet to transaction management system A 150 in gateway server A 152, using the conversation allocated on initialization. Interface module A 142 maps the conversation to the dialogue established between transaction management system A 150 and transaction services A 160, determines from the function code in the header of message packet (I) which service application A310 is targeted, and uses transaction management system A 150 to call targeted service application A310. Referring now to Fig. 6A, there is shown a detailed block diagram of message conversion module A304 comprising a message build/parse module A320, a list_build module A330, and a memory management system (MMS) module A340, which perform functions for the open system platform of server A 192 that build/parse module A220, list_bιιild module A230, and MMS module A240 perform on the proprietary platform of AS/400 Al 12. In the case of server A 192, however, transaction management system A 150 operates in conjunction with CSI A154 to handle routing and control information. In particular, these components ensure that the data portion of message packet (I) is routed to service application A310. Consequently, there is no need for a counterpart of MSG module A210 on server A192. On the other hand, the data portion of message packet (I) must be converted into a format suitable for the open system platform, and this is the function performed by modules A320, A330, A340. As indicated in Fig. 6A, service application A310 has associated registered functions A316 that isolate platform-independent, build/parse module A320 from platform specific message (MSG) buffers A314, A318. In this case, MSG buffer A214 includes data structures for coupling data between message conversion module A304 and DBMS A380 in a format consistent with that of database A390. MSG buffer A218 provides a buffering function for message packets inbound from transaction management system A 150 and outbound to transaction management system A150. List_build module A330 and MMS A340 also provide essentially the same functions as their counterpart modules A230, A240 on AS/400 Al 12. Message conversion module A304 also differs from messaging system A 120 in that it uses a segment cache A354 and segment cache interface structure (SCIS) A352 to facilitate access to the information data dictionary (DD) A326 without including the entire file in Build/parse module A220. SCIS A352 includes information for tracking accessed data segments in segment cache A354. This is an alternative configuration to that employed on AS/400 Al 12, but it requires sufficient memory for segment cache A354. While the configuration of computer system A100 shown in Fig. Al provides the necessary communication between an RPG application Al 10 and transaction services A 170, it does not provide security or accounting functions where transaction management system A 150 is TOP END (TE) and IF A142 is an inbound agent (IA) spawned by network services module A 140 when messaging system A 120 is initialized. In particular, IA A 142 is configured to map all conversations/dialogues having the same transaction program name (TE sign-on name) and transaction code (Request Service Name) to a generic userid. Consequently, all users of a given service application 310 will be assigned the same userid, independent of which user(s) of RPG application Al 10 actually initiated the transaction. If not addressed, this circumstance effectively eliminates security checking and accountability for transactions to server A 192. In order to ensure both security checking and accountability for transactions to server A 192, the preferred embodiment of system A 100 incorporates a security service (SIGNON SECURITY SERVICE, SSS) A 154 in the TE transaction management system A 150 on gateway server A 152. Referring now to Fig. A7, there is shown a block diagram of a preferred configuration for gateway server A 152, in which transaction management system A 150 is coupled to transaction services A 160 through SSS A 154. SSS A 154 comprises a TE client A 156 and a TE server A 156' coupled back-to-back through a client/server interface (CSI) provided by transaction management system A 150. IA A 142 incorporates an integral client which accesses SSS A 154 through transaction management system A 150 on behalf of messaging system A 120. On initialization of messaging system A 120, network services module A 140 spawns IA A 142, which forwards a SIGNON message, including a non-generic userid to transaction management system A150. IA A142 establishes a dialogue with SSS A 154 by passing a request for SSS services through transaction management system A 150, using the generic userid provided in the configuration file of IA A142. Transaction management system A150 forwards the request to SSS A154, establishing a dialogue between TE server A 156 and RPG application Al 10 (via messaging system A 120). TE server A 156 then triggers TE client A 156' to sign onto transaction management system A 150 using the non-generic userid embedded in the signon message. SSS A 154 confirms to messaging system A 120 that the dialogue has been established, and sets a flag holding the dialogue open. Thereafter, transaction services A170 are accessed by TE client A156' in response to message packets (I) from messaging system A 120. TABLE A 1 Specification Appendix transaction management system 116, 116' transaction management system 150, 150' gateway server 126 gateway server 152 database server 112 open system server 192 computer 124 computer 112 DBMS 214 DBMS 380 CPDB 220 DB 290 LAN/WAN IF 280 network services 140, 1 A 142 TCP/IP protocol module 160 SNA LU6.2 protocol module 130 A100 Fig. A1 A210 Fig.A2 Fig. A3 Ftg. A4 ACDS Request Services Request Service Name A256 Sending Segments Hold Context Flag Results Services Return Status Code Initialized Flag Control Flag Fig. A5 A310 Fig. A6 Fig. A7

Claims: Claims 1. A method for rewarding customer patronage at a plurality of casino properties, the method comprising the steps of: assigning an identification number and an associated account to a customer; monitoring the customer's betting activity at each of the plurality of casino properties; accumulating points in the associated account according to the monitored betting activity; and accessing the customer's account at any of the plurality of casino properties to determine the points accumulated. 2. The method of claim 1, comprising the additional substep of redeeming the accumulated points for awards determined by a number of accumulated points. 3. The method of claim 2, wherein the step of redeeming accumulated points comprises redeeming accumulated points for gifts or services provided by the casino property. 4. The method of claim 1, wherein the step of accumulating points comprises the subsets of: assigning point values to betting activities according to selected criteria; determining which of the selected criteria are met by the customer's betting activity; and accumulating points in the customer account according to the determination. 5. The method of claim 4, wherein the step of assigning point values comprises the step of assigning points values to a betting activity according to at least one of a time, a venue, and a casino property at which the betting activity occurs. 6. The method of claim 1 , including the additional step of recording the 'customer's monitored betting activity separately for each visit to one of the casino properties for use in determining a theoretical win profile for the customer. 7. The method of claim 6, including the additional step of displaying the customer's theoretical win profile when prompted by a casino employee. 8. A method for tracking customer activity at a plurality of casino properties wherein each casino property includes a computer-implemented management system and at least one input device coupled to the management system for transferring customer activity data from a casino venue to the management system, the management system of each casino property being further coupled to a central database server, the method comprising the steps of: assigning a customer ID and a corresponding customer account to each customer of the plurality of casino properties; forming a database of customer accounts in the central database server, each customer account being accessed through the corresponding customer ID; monitoring the input device at a casino property for customer activity data, including a customer ID; when a customer ID is detected, determining whether the corresponding customer account has been activated in the management system of the casino property; when the associated customer account is activated, updating the activated customer account with the customer activity data from the input device; and when the customer account is not activated; copying selected customer activity data from the corresponding customer account in the central database to activate the customer account in the management system; and updating the activated customer account with customer activity data from the input device. 9. The method of claim 8, wherein each step of updating the activated customer account comprises updating activity fields of the activated customer account according to the customer activity data from the input device. 10. The method of claim 9, wherein the step of updating activity fields comprises the subsets of: identifying an activity characteristic from the customer activity data; determining a number of activity points from the activity characteristic; and adding the determined number of activity points to a field of the customer account associated with the activity type. 11. The method of claim 10, wherein the activity characteristic comprises an activity type and an activity level. 12. The method of claim 9, wherein the copying step comprises the subsets of: retrieving selected customer activity data from the corresponding customer account in the central database; and writing the selected customer activity data to an account in the management system indexed by the corresponding customer LD. 13. The method of claim 8, including the additional step of periodically updating the central patron database with customer account data in the management system of the casino property. 14. The method of claim 8, comprising the additional steps of; determining whether a display device is associated with the monitored input device; and transmitting the selected customer activity data from the activated customer account to the associated display device when such a device is present. 15. A method for making customer account data collected at one or more casino properties of a company available at another casino property of the company, wherein each casino property is coupled to a management system for tracking customer activity data accumulated through at least one input device in the casino property and wherein the management system is further coupled to a central database, the method comprising the steps of: issuing to each customer of the company a customer ID number for identifying an associated customer account; adding the customer accounts to the central database; retrieving selected customer activity data from a customer account when the associated customer LD number is input to the management system; and adding any new customer activity data input to the customer account associated with the customer ID through the management system. 16. The method of claim 15, comprising the additional step of assigning activity points to the customer account associated with the customer ID when the customer activity is gaming activity. 17. The method of claim 16, wherein the assigning step comprises the substeps of: determining a type of gaming activity; and assigning a number of activity points according to the type of gaming activity. 18. A system for tracking customer activity at a plurality of casino properties associated with a casino company using customer accounts indexed by customer IDs, the system comprising: a local computer system at each of the casino properties; at least one input device at each casino property and coupled to the local computer system for transmitting customer activity data, including a customer ID, to the computer system; a management system coupled to each of the local computer systems for receiving customer activity data from the coupled input devices, the management system being further coupled to a central database for retrieving selected customer activity data from the central database when necessary, and updating the selected customer activity data with the received customer activity data from the coupled input device; and the central database comprising customer accounts for the customers of the casino company and a database management program for receiving customer activity data from the management system, updating the central customer accounts of the central database to reflect customer activity data at any of the casino properties, and providing selected customer activity data to a local computer system through the management system coupled to the local computer system. 19. The system of claim 18, wherein there are a plurality of input devices located at various venues of at least one casino property and the venues include slot machines, gaming tables, restaurants, retail sales locations, hotel check-in locations, and other service locations associated with the casino property. 20. The system of claim 19, wherein the plurality of input devices include card readers, dumb terminals, and work stations. 21. The system of claim 18, wherein the customer activity data includes activity type data. 22. The system of claim 21 , wherein the customer account includes fields to reflect different types of customer activity. 23. The system of claim 22 wherein each customer account includes a gaming field in which customer activities associated with slots, gaming tables, and other gaming sites are tracked separately. 24. The system of claim 23, wherein each customer account includes an activity points field to which points are added when customer activity is registered in the gaming field.

Inventors: BOUSHY JOHN MICHAEL, BOUSHY, JOHN, MICHAEL
Applicants: HARRAH S OPERATING COMPANY INC, HARRAH'S OPERATING COMPANY, INC.
Application year: 1997
Main classification: G06F17
IPC codes: G06Q30, G07F17