Booking System
Case Study
BOOKING SYSTEM
Introduction
Company C currently use a Lotus Approach Database Application to control customers, quotes, bookings and supplier confirmations. Many parts of the system have no links and data has to be keyed several times. The requirement is for a system whereby they can control the booking process without re-entry of the data. Company C currently runs a ‘sister’ company, which has a web based enquiry and booking system.
Proposal
Currently Customer Data, Quote data and Enquiry data is stored in the Approach system. In future this will be stored within the website as this information is entered when creating a quote or enquiry. To ensure staff can always get access to the quote website, it will be replicated between the online website database and the office database using SQL replication. The office will use a intranet
(internal) website to gain access to the office database. The office website will be used for all customer interaction up to and including the order being placed.
It is suggested for payment that a virtual terminal is used, this means each user can enter credit card payments for deposits from their desktop. After processing through the terminal, the reply and confirmation will be recorded in the back office database. It is also suggested that an encrypted database for short term storage of credit card details and payments if it is not possible to connect to the virtual terminal due to broadband outage. A daily reminder will be send on payments due that are stored within this database. Once payment is made all details will be removed from the credit card database.
The back office system will be used to follow up after the booking has been made. This will include confirming bookings for hotels, golf, car hire and flights. Final costs, payments and exchange rates can also be added to the system to provide feedback on margins and profits for bookings. Reports as agreed will be included within the
BOOKING SYSTEM
Introduction
Company C currently use a Lotus Approach Database Application to control customers, quotes, bookings and supplier confirmations. Many parts of the system have no links and data has to be keyed several times. The requirement is for a system whereby they can control the booking process without re-entry of the data. Company C currently runs a ‘sister’ company, which has a web based enquiry and booking system.
Proposal
Currently Customer Data, Quote data and Enquiry data is stored in the Approach system. In future this will be stored within the website as this information is entered when creating a quote or enquiry. To ensure staff can always get access to the quote website, it will be replicated between the online website database and the office database using SQL replication. The office will use a intranet
(internal) website to gain access to the office database. The office website will be used for all customer interaction up to and including the order being placed.
It is suggested for payment that a virtual terminal is used, this means each user can enter credit card payments for deposits from their desktop. After processing through the terminal, the reply and confirmation will be recorded in the back office database. It is also suggested that an encrypted database for short term storage of credit card details and payments if it is not possible to connect to the virtual terminal due to broadband outage. A daily reminder will be send on payments due that are stored within this database. Once payment is made all details will be removed from the credit card database.
The back office system will be used to follow up after the booking has been made. This will include confirming bookings for hotels, golf, car hire and flights. Final costs, payments and exchange rates can also be added to the system to provide feedback on margins and profits for bookings. Reports as agreed will be included within the