# Integration checklist

The integration process for RG Bridge with third-party software (CRS/PMS/others) typically involves a number of critical steps. This checklist is not for integration of new channels on RG but exclusively for integration with CRS, PMS & other third-party software that the hotel wishes to integrate RG with. Use the checklist as a general guide to find out what the process involves & track where you are in the integration process.

<table data-header-hidden><thead><tr><th width="100"></th><th></th></tr></thead><tbody><tr><td><strong>Step</strong></td><td><strong>Check-point</strong></td></tr><tr><td>1.</td><td><p><strong>Vision of Integration</strong></p><p> </p><p>Establish and document a high-level vision of the proposed integration including</p><p> </p><p>•       Expected number of customers (Business Case)</p><p>•       Expected list of channels for integration?</p></td></tr><tr><td>2.</td><td><p><strong>Information/Data flow</strong></p><p> </p><p>Document whether this is One-way or two way integration? Reservations into RG or out of RG (And vice versa for ARI)?</p></td></tr><tr><td>3.</td><td><p><strong>Business Requirements</strong></p><p> </p><p>Understand and document business requirements for the RG Integration.</p><p> </p><p>•    Can your application update Property additions, deletions and reactivation?</p><p> </p><p>•    Can your application accept reservations for default rooms and rate types?</p><p> </p><p>•     Do you require credit card information, especially CVV?</p></td></tr><tr><td>4.</td><td><p>Documentation requirements</p><p> </p><p>RateGain would supply the following documents</p><p> </p><p>•       Integration specifications document</p><p>•       Contract terms &#x26;conditions</p><p> </p><p> </p><p>RateGain would need the following documents</p><p> </p><p>•       Technical design document</p><p>•       Contract terms &#x26;conditions</p><p>•       Third party application (CRS/PMS) user manual</p><p>•       Third party application test account details with a functionalities demo</p></td></tr><tr><td>5.</td><td><p><strong>Technical feasibility study</strong></p><p> </p><p><em>Technical Requirements –</em> Obtain a copy of the RG integration specification. Advanced working knowledge of web services and Rest are required to consume RG web services and to expose services.</p><p> </p><p> </p><p><em>Application Architecture</em> – Review and document your own service architecture.</p><p></p><p>Identify the following:</p><p>·         Is your application available online?</p><p>·         Is your application always-on available?</p><p>·         Can your application serve and consume web services?</p><p> </p><p>Update mode – Batch processing versus real-time update generation</p><p> </p><p>Any other technical requirements?</p></td></tr><tr><td>6.</td><td><p><strong>Initiate project</strong></p><p> </p><p>Please email your requests to pmg@rategain.com. Please include a brief profile of your product and organization.</p></td></tr><tr><td>7.</td><td><p><strong>Project Schedule</strong></p><p> </p><p>Determine activities and timeline for the integration. Typical integration projects take about three months from initiation to release.</p></td></tr><tr><td>8.</td><td><p><strong>Contract</strong></p><p> </p><p>Sign contract with RG. Include project schedule, business case, scope of work, list of</p><p>channels and agreed service level agreements (SLAs).</p></td></tr><tr><td>9.</td><td><p>Setup</p><p> </p><p>For RG Bridge, all setup would be done using the RG user interface. This would also</p><p>include automation of PRS (Property Requirement Specifications)</p></td></tr><tr><td>10.</td><td><p>Testing phases &#x26; preparations</p><p> </p><p><strong>Service Account/password</strong> – Obtain a service account and password for each application integrating with RG. The service account will allow you to integrate with</p><p>RezGain in the RG SIT environment.</p><p> </p><p><strong>Test Accounts for SIT</strong> – Obtain one or more test RG accounts for testing your integration in the SIT environment.</p><p></p><p><strong>ServiceAccount/passwordfortheProduction Environment</strong> –Obtain a service account and password for each application integrating with RG. The service account will allow you to integrate with our production version.</p></td></tr><tr><td>11.</td><td><p><strong>Certification by RateGain</strong></p><p></p><p>Obtain a copy of the test cases required for the certification of the integration with RG. The RG team will check the following:</p><p>•       Reliability</p><p>•       Security</p><p>•       Availability</p><p>•       Stability</p><p>•       Error handling</p></td></tr><tr><td>12.</td><td><p>Sales</p><p> </p><p>Price the integrated product. Engage launch customers for alpha &#x26; beta phase.</p></td></tr><tr><td>13.</td><td><p><strong>Monitoring &#x26; After Sales Support</strong></p><p> </p><p>RG Bridge would be integrated with the existing ticketing system (IMS/OTRS)</p><p> </p><p>Format for the Channel Availability Reports(CAR), Channelhealthreports(CHR) and other reports would be decided and published by RateGain. Agreed service levels would be implemented by RateGain and monitored for third-party compliance.</p><p>Additionally, account management and customer training requirements would be</p><p>handled by RateGain account management.</p></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.rategain.com/our-products/channel-manager/rg-bridge-supply-push/integration-overview/integration-checklist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.