First Steps

1. The hotel should read the Novohit manual on the Siteminder Connection and the management of master and derived seasons to become familiar with the equivalences of functions and terminology.
2. The hotel must have the SiteMinder production environment parameterized before requesting to create the test environment.
3. The hotel will create in SiteMinder a user for Novohit with the email soporte@novohit.com with Administrator permissions.
1. It is recommended that if the hotel has a Sales Manager or staff in charge of controlling sales in online channels, they should be actively involved in this process.
4. The hotel will contact SiteMinder and request the activation with Novohit.
5. SiteMinder will create the Clone (test environment) which will be the same as the production environment, this point is important since any later difference will prevent SiteMinder from migrating the Clone to production.

Interface Activation, Rates and Restrictions Upload

1. Novohit Support will perform the installation of the interface in Novohit and the corresponding updates to the modules involved.
2. The hotel should be guided by the following manuals:
1. Registration of Agencies (Channels).
2. Creation of Seasons.
3. Management of Master and Derived Seasons.
4. Connection of Novohit with SiteMinder.
3. Novohit will confirm via Ticket when activating the SiteMinder Clone connection.
1. As indicated in point 5 of the previous section, the Clone is the test environment that will be activated by SiteMinder where we will perform tests before moving to production, Novohit will perform the activation in Novohit so that there is communication between both platforms.
4. The hotel will have to do the following:
1. Register or modify the agencies and link them as indicated in the manual Connecting Novohit with SiteMinder.
2. Create and load the Master and Derived Seasons for 400 days in the future according to the Master and Derived Seasons Management manual and their respective restrictions.
3. The rates and restrictions must be the same in Novohit as in SiteMinder and have the same syntax in both platforms: "Rate Name - Rate Code".
5. When the rates and restrictions have been uploaded, you must notify Novohit via Ticket in order for Novohit to initiate tests to send the datasets to SiteMinder.

Information Review in SiteMinder

1. Novohit will notify via Ticket if the submission was successful or if there were errors that need to be corrected by the hotel. If necessary, this step will be repeated once the possible errors have been corrected.
2. The hotel must review the information sent to Siteminder and report in the corresponding Ticket any observations that may arise.
3. If necessary, the hotel makes adjustments or changes to the rates and restrictions, the information that exists in Novohit must be the same that remains in SiteMinder.
4. The time of this process will depend on the complexity of the rate structure and its restrictions, considering that data is being sent 400 days into the future, so it will be necessary to dedicate quality time to this review.

Steps to Production

1. Date and time will be agreed upon:
1. Novohit will connect to the Siteminder production server and send the initial data set:
1. Rates
2. Restrictions
3. Availability
2. The hotel will check all rates for all room types for the next 14 days, then they will be able to check the full seasons.
3. Hotel shall confirm via Ticket upon completion of review and send comments, questions or remarks.
2. The hotel must check:
1. If there were reservations during the migration process, these reservations should be automatically registered.
2. Make a reservation in any of the channels and check its entry in Novohit.
3. If necessary, adjustments or changes in rates and restrictions will be made, the information that exists in Novohit must be the same that remains in SiteMinder.