Backlog and go-live process

The content of this page is specific to the Delphi product type only. If you are using the Delphi Core product type and want to learn more about the Delphi product type, contact your sales representative.

This topic applies to version R41 and lower. If your org is on version R42 or higher, see Backdating bookings. To view the release installed in your org, see Installed Packages.

When you purchase a new sales and catering system, your property might already have existing business. You need to enter all that information before you can use the system to check availability. This process is called backlog entry.

When you enter this information, you need to record accurate dates that reflect the true lead time and correct month the business went definite. Otherwise, the report results are skewed and can show business as booked on the backlog entry date.

For a limited time, users can backdate the following fields on the Booking page:

• Arrival and Departure Dates
• Booked Date – This is the date when the booking originated. The booked date needs to be before the arrival date.
• Last Status Date – This is the date when the booking turned to its current status. This date also needs to be before the arrival date, and cannot be blank.

When entering backlog, the tracking system that records important date changes, called Booking Day Snapshots, is unavailable. This means you cannot use any performance reports that compare your progress to making budget and goals. Amadeus recommends completing your backlog entry as soon as possible. When backlog entry is complete, your property can go live.

The following information describes the go-live process.

Scheduling

During your installation, your Amadeus training specialist works with you to estimate a target date for the completion of backlog entry. That date is communicated to Amadeus Support for go-live implementation. If your backlog entry takes longer than expected and the date for the go-live needs to be adjusted, tell Support as soon as possible. For scheduling purposes, Support requires a minimum notice of five business days.

Preparation

To prepare for the scheduled date, Support creates a view on the Bookings tab to verify that all bookings include a Last Status Date. You are notified of any missing data through email. If any missing dates are found on the scheduled go-live day, the go-live date needs to be rescheduled.

Day of go-live

Support contacts you to ensure all users are logged out, and begins turning on Booking Day Snapshots so performance reports can be used. Support also enables the validation rules that prevent the backdating of bookings. Based on the number of bookings entered, the process can take up to 60 minutes. You are notified when the process is complete.