Hotelecom Property Management System Integration

Hotelecom Property Management System Integration ..................................................1 Hotelecom PMS interface protocols ........................................................................2 HOBIC A .........................................................................................................2 HOBIC B .........................................................................................................4 LODGING LINK................................................................................................5 INTEGRATION .....................................................................................................6 PROCUREMENT ...................................................................................................6

TriVium Systems, Inc. Confidential

Hotelecom PMS interface protocols

Call tracking is vital in the hospitality industry to maintain precise billing to customers, improving margins and profits. Along with these benefits, PMS system users will experience stronger integration, efficiency, cost management, and monitoring for the best view of telephony activity. This integration recovers lost revenues and creates a seamless back-end to manage telecom billing through a single application. Hotelecom currently supports three widely used protocols to communicate with these systems and is described below.

HOBIC A
This Interface Protocol is based on the original AT&T* HOBIC-to-PMS Interface and is employed by more than 90% of Property Management Systems. Systems using Hobic A include: Amstar, CLS, Compass, Compu-solve, Dehan, Encore, Fabco, Holidex, HRGAS, HIS, InnSolutions, InnStar, Lodgemate, Logistix, Micros Fidelio, OPERA, Omron, Otto Clerk, Reserve 5, Resort Computer, RDP, Springer-Miller Systems, Star, and Stuart* to name a few.

With this protocol, records are sent in a typical Enquire-Acknowledge format (sometimes called ACK-NAK), with XOR checksum, as follows: HOTELECOM sends: <ENQ> <STX><record><ETX><BLKCHK> PMS responds: <ACK> <ACK> Where <ENQ> is the enquire character (05 hex, 5 decimal) <ACK> is the acknowledge character (06 hex, 6 decimal) <STX> is the start-of-text character (02 hex, 2 decimal) <record> is an ASCII text string with data about a single call <ETX> is the end-of-text character (03 hex, 3 decimal) <BLKCHK> is the XOR checksum of all characters in <record> plus <ETX> (but not <STX>). If the PMS does not reply with the <ACK> character when expected, or replies with some other character (such as <NAK>, 15 hex, 21 decimal), the send will be reattempted after a short 1-3 second delay; the total number of attempts is set with Hotelecom and has a default value of three. If the PMS does not reply to all attempts, an event message (NO RESPONSE FROM PMS) will be logged in HOTELECOM. If the PMS rejects the record on all attempts by responding with a character other than <ACK>, the message, PMS REJECTED RECORD will be logged instead.

TriVium Systems, Inc. Confidential

If either of these failure messages occur, it will be reported with cost in HOTELECOM reports; this record should be hand-posted to the guests folio. In the HOBIC A Interface Protocol, the ASCII text string (<record>) is sent in the following format: 1 2 3 4 5 123456789012345678901234567890123456789012345678901234 CCCC PPP MM/DD EEEE HH:MM MMMM $DDD.CC NNNNNNNNNNNN D Where the fields are: Field Field Name Width Default Position Empty Spaces Filled With CCCC Counter 04 01 0 (in front of the digits) PPP Property Code 03 06 MM/DD Date 05 10 0 (in front of any single digit) EEEE Extension 04 17 Space (in front of the digits) HH:MM Time 05 22 0 (in front of any single digit) MMMM Duration 04 28 0 (in front of the digits) $DDD.CC Cost 07 33 0 (in any empty space after $) NNNNNNNNNNNNNumber Dialed 12 41 Space (after the digits) D Description 1 54 Space (if no description)

Notes: 1. The Default Position shows the location of the first character in the field (the left edge of the field). 2. The counter field, CCCC, is a numeric counter in the first 3 positions, followed immediately (no space) by the letter A. When the counter rolls over to 000, the letter is incremented to B, and so on. 3. The Duration field is minutes only, 0 padded on the left, rounded up to the nearest whole minute. 4. The Cost field includes the dollar sign as part of that field. 5. The Description field is one character only and is taken from the PMS Interface field in the Rate Line. Sample Data using the HOBIC A Interface Protocol: 1 2 3 4 5 123456789012345678901234567890123456789012345678901234 001A PPC 09/21 101 10:25 0002 $000.50 3035552345 L 923A PPC 09/23 203 17:44 0006 $001.45 12125678900 028B PPC 10/05 405 06:30 0004 $000.50 18002221234 Note: The column number ruler shown above the sample data does not print; it is included as an aid in determining where each field starts and ends.

TriVium Systems, Inc. Confidential

HOBIC B
Also based on the original AT&T HOBIC-to-PMS interface, this Interface Protocol uses the same record layout and field formats as HOBIC A but uses a different set of handshaking characters. This protocol is used for Property Management Systems such as EECO and New Systems*, Inc.

With this protocol, records are sent as follows: HOTELECOM sends: <LF><record><CR> PMS responds: <ACK> Where <LF> is the line feed character (0A hex, 10 decimal) <record> is an ASCII text string with data about a single call <CR> is the carriage return character (0D hex, 13 decimal) <ACK> is the acknowledge character (06 hex, 6 decimal). If the PMS does not reply with the <ACK> character when expected, or replies with some other character (such as <NAK>, 15 hex, 21 decimal), the send will be reattempted after a short 1-3 second delay; the total number of attempts is set with HOTELECOM. If the PMS does not reply to all attempts, an event message (NO RESPONSE FROM PMS) will be logged in HOTELECOM. If the PMS rejects the record on all attempts by responding with a character other than <ACK>, the message, PMS REJECTED RECORD will be logged instead. If either of these failure messages is logged, HOTELECOM can report on these records; this record should be handposted to the guests folio. In the HOBIC B Interface Protocol, the ASCII text string (<record>) is sent in the format used for the HOBIC A Interface Protocol, as previously described.

TriVium Systems, Inc. Confidential

LODGING LINK
Based on the Comtrol Lodging Link system, Hotelecom is interoperable with over thirty - (30) of the most widely used PMS systems including Micros-Fidelio, Marriott, Visual One, Cenium, Choice Hotels International, Hilton Grand Vacations, Radiant, and Cendant Brilliant Pro.

Communication with Hotelecom and the PMS is based on the proprietary Universal Hospitality Language Layer (UHLL) used by Lodging Link. Based on this protocol, the PMS accepts information in this format and interprets it for reporting and billing purposes. To learn more about Comtrols Lodging Link product and the UHLL protocol used, please visit their website here. The Lodging Link system is installed as a service on a PC. After installation, the service must be configured to capture information from the Guest Services Systems (GSS) via the serial port or over an IP network. When using the serial port, information such as baud rate, data bits, parity, and stop bits must be defined. When sending information via the IP network, IP addresses and port numbers must be defined. The UHLL protocol communicates with Hotelecom via an ACK-NAK format similar to that of HOBIC A mentioned previously. If the Lodging Link system provides the ACK response when expected, Hotelecom will continue to send information. However, if Lodging Link responds with a NAK or no response, the information send will be reattempted 3 times. If the information is not successfully accepted after these attempts, an error log is created containing all call records, costs, and reason for error. Hotelecom will attempt to resend these call records during times where no new call records are being reported. Hotelecom will retain information about all call records regardless of Lodging Link acceptance of data.

TriVium Systems, Inc. Confidential

INTEGRATION

Obtaining Hotelecom is a straightforward procedure. Just follow these steps: 1. Procure Hotelecom from your TriVium reseller, or contact TriVium directly (see PROCUREMENT for more information). 2. Contact your PMS vendor and notify them of your choice to integrate Hotelecom. a. The information provided previously will aid in this process. 3. The TriVium reseller and PMS vendor will take the steps necessary to install and integrate the two systems. Dont hesitate to give TriVium a call if you have any additional questions at 877-439-9338.

PROCUREMENT
Procuring Hotelecom is a quick and easy process. If you have a TriVium reseller, please contact this dealer to get Hotelecom. If you do not have a TriVium reseller or heard about TriVium through another source, please contact TriVium directly. Our Account Managers will walk you through the Hotelecom procurement process, while our Technical Support Team will make sure your installation goes smoothly. If you have any questions feel free to call us at 877-439-9338, were happy to help! TriVium Systems Inc. 1865 NW 169th Place Suite 210 Beaverton, OR 97006 Phone: 503-439-9338 Fax: 503-439-1526 Web: http://www.triviumsys.com

* These names are copyrighted or trademarked by their respective owners.

TriVium Systems, Inc. Confidential