Implementation
of the interface in "mixed operation" |
Operators of more than one hotel can
sometimes ask themselves whether or not the interface can also
be used in one of the hotels of the MPE group, e.g., because out
of three hotels only one hotel is a Best Western member. Technically
speaking, this is not a problem because the BWI interface can
be separately activated for each MPE hotel. However, because all
of the MPE hotels access a common pool of data, many of the limitations
specific to Best Western also effect the entire hotel chain:
Guest profiles sent from Best
Western are subject to special protection based in Best Western's
Business Rules and are therefore also blocked for MPE hotels
who no longer work with the interface. For all hotels, the
respective limitations when working with Best Western guest
profiles apply: Restrictions
when working with Best Western guest profiles.
If the MPE hotels work by
means of the HQ, a differentiation between Best Western reservations
and "local" hotel reservations must be made. For
Best Western reservations the usual Restrictions
apply. Additionally, reservations are not permitted to be
moved from one Best Western hotel to another hotel.
MPE hotels with BWI interface
must work based on the PCI DSS 3.0 standard. Credit card data
will therefore be encrypted with a replacement number in this
hotel. Should hotels in the MPE group not be working without
conforming to PCI, the credit card data will continue to be
saved there without being encrypted. Because all of the hotels
have access to a mutual database, even the hotel with the
BWI interface cannot completely fulfill the required standards.
These points will need to be discussed
with the client before putting the BWI interface into operation
within one member of an MPE group.
Please make sure
that the XSetup "bwi, enabled, 1" is only allowed
to be set for BWI hotels and never for other hotels or
the headquarters!
|
|