Hotel Technology Next Generation

Conformance Statement Questionnaire

HTNG Web Services

Version 2010B


Referenced Documents

  1. HTNG Distribution Content Management Specifications 2009B Version 1.0
  2. HTNG Guest & Room Status Messaging Specification 2010B Version 1.1
  3. HTNG Kiosk Integration Specifications 2010B Version 2.0
  4. HTNG Open Data eXchange Query Specification 2010B Version 1.0
  5. HTNG Payment Systems & Data Security Specifications 2010A, Data Proxy Specification Version 1.1
  6. HTNG Payment Systems & Data Security Specifications 2010B, Payment Processing Specification Version 2.0
  7. HTNG Product Distribution Specifications 2010B – Part 1:  Reservations, Version 2.4
  8. HTNG Product Distribution Specifications 2010B – Part 2:  Availability, Version 2.2
  9. HTNG Product Distribution Specifications 2010B – Part 3:  Statistics, Version 2.0
  10. HTNG Product Distribution Specifications 2010B – Part 4:  Groups, Version 1.2
  11. HTNG Product Distribution Specifications 2010B – Part 5:  Rates, Version 1.2
  12. HTNG Product Distribution Specifications 2010B – Part 6:  Inventory, Version 1.0
  13. HTNG Product Distribution Specifications 2010B – Part 7:  Seamless Shop/Book, Version 1.1
  14. HTNG Property Web Services Specifications 2009B – Part 1: Web Services Framework Version 2.1.1
  15. HTNG Property Web Services Specifications 2009B – Part 2:  Single Guest Itinerary Version 2.2.1
  16. HTNG Property Web Services Specifications 2009B – Part 3:  Digital Signage Version 1.0
  17. HTNG Property Web Services Specifications 2009B – Part 4:  Open Data eXchange Basic Version 1.4.2
  18. HTNG Property Web Services Specifications 2009B – Part 5:  Back Office Integration Version 2.0
  19. HTNG Property Web Services Specifications 2009B – Part 6:  Guest Self Service Version 1.0.3
  20. HTNG Property Web Services Specifications 2009B – Part 7:  Food and Beverage Ordering Version 1.0
  21. HTNG Web Services Product Specification 2010B

The following ancillary documents are also referenced in some of the technical specifications:

1.    WS-I Basic Profile 1.0

2.    WS-Security 1.0 Specification

3.    WS-Addressing 1.0, Core W3C Working Draft, 2006-05-09

4.    PCI Data Security Standard

5.    OpenTravel Alliance Specifications

Instructions to applicants are given in blue text.

Note to submitter: Your completed form should be submitted as input to the web certification system. Please ensure that you use the current version of the questionnaire (available on the certification website) for your submission. See the Guide to HTNG Certification for more information. Please note that all information in this conformance statement will appear on the public register of certified products. Revision History showing the changes in this Conformance Statement from prior versions is contained at the end of this document.

Submitter Information

 

 

 

Organization Name

 

Q

1

Please enter your company name.

 

A

1

FCS Computer Systems Sdn Bhd

 

 

 

Contact Information

 

Q

2

Please enter the name of the individual completing this conformance statement questionnaire.

 

A

2

Hoo Chong Kee

 

Product Information

 

Note to submitter: The information provided in this section must match the name and version information provided on the registration form when registering this product for certification. Please refer to section 3 of the Guide to HTNG Certification.

 

 

 

Product Name

 

Q

3

Please enter the name of the product for which this application is being made.

 

A

3

FCS UBIS

 

 

 

Product Version/Identifier

 

Q

4

Please enter the version number (or other identifier) of the product for which this application is being made.

 

A

4

3.20.0

 

Scope of Certification

 

Guide to Completing the Conformance Statement Questionnaire

 

Do I need to complete this entire document? No – this document includes all possible HTNG Web Services certifications and it is likely that only a few sections will apply to you.  All certifications require the implementation of at least one technical specification, and some may require multiple. 

 

For each technical specification implemented, you must complete the questions listed in the table below. For example, if you are certifying to the Back Office Integration technical specification, you must complete questions 66-75. 

 

Many technical specifications define two or more identified roles that systems may play in an interface transaction.  However, most systems will typically implement only one (or a subset) of the available roles.  Select the appropriate role(s) for the functionality you are looking to certify and only complete the questions pertaining to that/those role(s).

 

 

 

 

 

 

 

 

Specifications Implemented – Required

 

Q

5A

The Product Specification requires conformance to at least one of the following technical specifications:

 

1.         HTNG Distribution Content Management Specifications 2009B Version 1.0

2.         HTNG Kiosk Integration Specifications 2010B Version 2.0

3.         HTNG Payment Systems & Data Security Specifications 2010A, Data Proxy Specification Version 1.1

4.         HTNG Payment Systems & Data Security Specifications 2010B, Payment Processing Specification Version 2.0

5.         HTNG Product Distribution Specifications 2010B – Part 1:  Reservations, Version 2.4

6.         HTNG Product Distribution Specifications 2010B – Part 2:  Availability, Version 2.2

7.         HTNG Product Distribution Specifications 2010B – Part 3:  Statistics, Version 2.0

8.         HTNG Product Distribution Specifications 2010B – Part 4:  Groups, Version 1.2

9.         HTNG Product Distribution Specifications 2010B – Part 5:  Rates, Version 1.2

10.        HTNG Product Distribution Specifications 2010B – Part 6:  Inventory, Version 1.0

11.        HTNG Product Distribution Specifications 2010B – Part 7:  Seamless Shop/Book, Version 1.1

12.        HTNG Property Web Services Specifications 2009B – Part 1:  Web Services Framework Version  2.1.1

13.        HTNG Property Web Services Specifications 2009B – Part 5:  Back Office Integration Version 2.0

 

You must answer ‘YES’ to at least one of the following.

 

A

5A

HTNG Distribution Content Management Specifications 2009B Version 1.0  (Questions 6 - 11)

NO

HTNG Kiosk Integration Specifications 2010B Version 2.0  (Questions 15 - 17)

NO

HTNG Payment Systems & Data Security Specifications 2010A, Data Proxy Specification Version 1.1  (Questions 21 - 23)

NO

HTNG Payment Systems & Data Security Specifications 2010B, Payment Processing Specification Version 2.0  (Questions 24 - 26)

NO

HTNG Product Distribution Specifications 2010B – Part 1:  Reservations, Version 2.4  (Questions 27 - 45)

NO

HTNG Product Distribution Specifications 2010B – Part 2:  Availability, Version 2.2  (Questions 27 - 45)

NO

HTNG Product Distribution Specifications 2010B – Part 3:  Statistics, Version 2.0  (Questions 27 - 45)

NO

HTNG Product Distribution Specifications 2010B – Part 4:  Groups, Version 1.2  (Questions 27 - 45)

NO

HTNG Product Distribution Specifications 2010B – Part 5:  Rates, Version 1.2  (Questions 27 - 45)

NO

HTNG Product Distribution Specifications 2010B – Part 6:  Inventory, Version 1.0  (Questions 27 - 45)

NO

HTNG Product Distribution Specifications 2010B – Part 7:  Seamless Shop/Book, Version 1.1  (Questions 27 - 45)

NO

HTNG Property Web Services Specifications 2009B – Part 1:  Web Services Framework Version  2.1.1  (Questions 46 - 49)

YES

HTNG Property Web Services Specifications 2009B – Part 5:  Back Office Integration Version 2.0  (Questions 66 - 75)

NO

 

 

 

Specifications Implemented – Optional

 

Q

5B

In addition, if conformance to the Web Services Framework Version 2.1.1 technical specification is chosen above, the Product Specification optionally includes conformance to one or more of the following technical specifications:

 

1.         HTNG Guest & Room Status Messaging Specifications 2010B Version 1.1 

2.         HTNG Open Data eXchange Query Specification 2010B Version 1.0

3.         HTNG Property Web Services Specifications 2009B – Part 2:  Single Guest Itinerary Version 2.2.1

4.         HTNG Property Web Services Specifications 2009B – Part 3:  Digital Signage Version 1.0

5.         HTNG Property Web Services Specifications 2009B – Part 4:  Open Data eXchange Basic Version 1.4.2

6.         HTNG Property Web Services Specifications 2009B – Part 6:  Guest Self Service Version 1.0.3

7.         HTNG Property Web Services Specifications 2009B – Part 7:  Food and Beverage Ordering Version 1.0

 

A

5B

HTNG Guest & Room Status Messaging Specifications 2010B Version 1.1  (Questions 12 - 14)

YES

HTNG Open Data eXchange Query Specification 2010B Version 1.0  (Questions 18 - 20)

NO

HTNG Property Web Services Specifications 2009B – Part 2:  Single Guest Itinerary Version 2.2.1  (Questions 50 - 57)

YES

HTNG Property Web Services Specifications 2009B – Part 3:  Digital Signage Version 1.0  (Questions 58 - 62)

NO

HTNG Property Web Services Specifications 2009B – Part 4:  Open Data eXchange Basic Version 1.4.2  (Questions 63 - 65)

NO

HTNG Property Web Services Specifications 2009B – Part 6:  Guest Self Service Version 1.0.3  (Questions 76 - 78)

NO

HTNG Property Web Services Specifications 2009B – Part 7:  Food and Beverage Ordering Version 1.0  (Questions 79 - 81)

NO

 

HTNG Distribution Content Management Specifications 2009B Version 1.0

 

 

 

Roles

 

Q

6

Please check all roles for which the product is being certified. At least one role must be supported.

 

A

6

Role

Publisher

Subscriber

Usage Profile

Hotel Descriptive Content

YES/NO

YES/NO

 

 

 

Functionality

 

Q

7

Please indicate the functionality implemented. Shaded cells indicate mandatory functionality.

 

A

7

 

Publisher

Subscriber

Receiving

Sending

Receiving

Sending

Hotel Descriptive Content

OTA_HotelDescriptiveContentNotifRQ

 

YES/NO

YES/NO

 

OTA_HotelDescriptiveContentNotifRS

YES/NO

 

 

YES/NO

Text Descriptions Supported

 

YES/NO

YES/NO

 

ImageItems supported

 

YES/NO

YES/NO

 

VideoItems supported

 

YES/NO

YES/NO

 

Multiple Property Updates per message

 

YES/NO

YES/NO

 

 

 

 

Mandatory Elements and Attributes

 

Q

8

Does the product support all the mandatory message Elements and Attributes applicable to the Hotel Descriptive Content Usage Profile functionality identified in A7?

 

A

8

YES

NO

Not Applicable

 

 

 

Optional Elements and Attributes

 

Q

9

Please indicate all optional Elements and Attributes supported.

 

A

9

 

 

 

 

Multilanguage Restrictions

 

Q

10

Please indicate any restrictions related to multilingual metadata handling.

 

A

10

 

 

 

 

Communications Types

 

Q

11

Please indicate all communication type supported by the product. At least one communication type must be supported.

 

A

11

SOAP/HTTP (Sync)

YES/NO

SOAP/HTTP (Async)

YES/NO

HTTP

YES/NO

HTTPS

YES/NO

File Drop

YES/NO

TCP/IP Socket

YES/NO

FTP

YES/NO

 

HTNG Guest & Room Status Messaging Specifications 2010B Version 1.1

 

 

 

Roles

 

Q

12

Please check all roles for which the product is being certified.  If you are certifying to the Guest & Room Status Messaging Specification, you must select at least one of the following roles.

 

A

12

Role

Room Stay Information Provider

NO

Room Stay Information Consumer

YES

 

 

 

Room Stay Information Provider

 

Q

13

If the product performs the role of a Room Stay Information Provider, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

13

Message Description

Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Send Guest Check-In Notification Message

HTNG_CheckInNotification

Mandatory

 

NO

Send Guest Check-Out Notification Message

HTNG_CheckOutNotification

Mandatory

 

NO

Send Guest Room-Move Notification Message

HTNG_RoomMoveNotification

Mandatory

 

NO

Send Stay Update Notification Message

HTNG_StayUpdateNotification

Mandatory

 

NO

 

 

 

Room Stay Information Consumer

 

Q

14

If the product performs the role of a Room Stay Information Consumer, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

14

Message Description

Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Receive Guest Check-In Notification Message

HTNG_CheckInNotification

Mandatory

YES

 

Receive Guest Check-Out Notification Message

HTNG_CheckOutNotification

Mandatory

YES

 

Receive Guest Room-Move Notification Message

HTNG_RoomMoveNotification

Mandatory

YES

 

Receive Stay Update Notification Message

HTNG_StayUpdateNotification

Mandatory

YES

 

 

HTNG Kiosk Integration Specifications 2010B Version 2.0

 

 

 

Roles

 

Q

15

Please check all roles for which the product is being certified. At least one role must be supported.

 

A

15

Role

Kiosk Application

YES/NO

PMS Application

YES/NO

 

 

 

Kiosk Application

 

Q

16

If the product performs the role of a Kiosk Application, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

16

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Find Booking

OTA_ReadRQ

Mandatory

 

 YES/NO

Modify Booking

OTA_HotelResNotifRQ

Optional

 

YES/NO

Authorize Card

HTNG_ PaymentCardProcessingRQ

Optional

 

YES/NO

Check-In

OTA_HotelResNotifRQ

Mandatory

 

YES/NO

Cut Key Request

HTNG_HotelKeyEncodeRQ

Optional

 

YES/NO

Retrieve Folio

HTNG_HotelFolioRQ

Mandatory

 

YES/NO

Charge Card

HTNG_ PaymentCardProcessingRQ

Optional

 

YES/NO

Check Out

OTA_HotelResNotifRQ

Mandatory

 

YES/NO

Shop

OTA_HotelAvailRQ

Optional

 

YES/NO

Book

OTA_HotelResRQ

Optional

 

YES/NO

Upsell

HTNG_HotelRoomTypeUpsellRQ

Optional

 

YES/NO

Create Sharewith

OTA_HotelResNotifRQ

Optional

 

YES/NO

Define Multiple Names

OTA_HotelResRQ

Optional

 

YES/NO

Request Room List

OTA_HotelAvailRQ

Optional

 

YES/NO

Change / Update Room

OTA_HotelResNotifRQ

Optional

 

YES/NO

Display Guest Messages

HTNG_ProfileMessageRQ

Optional

 

YES/NO

Change Guest Message Status

HTNG_ProfileMessageStatusRQ

Optional

 

YES/NO

 

 

 

PMS Application

 

Q

17

If the product performs the role of a PMS Application, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

17

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Find Booking

OTA_ReadRQ

Mandatory

 YES/NO

 

Modify Booking

OTA_HotelResNotifRQ

Optional

 YES/NO

 

Authorize Card

HTNG_PaymentCardProcessingRQ

Optional

YES/NO

 

Check-In

OTA_HotelResNotifRQ

Mandatory

YES/NO

 

Cut Key Request

HTNG_ HotelKeyEncodeRQ

Optional

YES/NO

 

Retrieve Folio

HTNG_ HotelFolioRQ

Mandatory

YES/NO

 

Charge Card

HTNG_ PaymentCardProcessingRQ

Optional

YES/NO

 

Check Out

OTA_HotelResNotifRQ

Mandatory

YES/NO

 

Shop

OTA_HotelAvailRQ

Optional

YES/NO

 

Book

OTA_HotelResRQ

Optional

YES/NO

 

Upsell

HTNG_HotelRoomTypeUpsellRQ

Optional

YES/NO

 

Create Sharewith

OTA_HotelResNotifRQ

Optional

YES/NO

 

Define Multiple Names

OTA_HotelResRQ

Optional

YES/NO

 

Request Room List

OTA_HotelAvailRQ

Optional

YES/NO

 

Change / Update Room

OTA_HotelResNotifRQ

Optional

YES/NO

 

Display Guest Messages

HTNG_ProfileMessageRQ

Optional

YES/NO

 

Change Guest Message Status

HTNG_ProfileMessageStatusRQ

Optional

YES/NO

 

 

HTNG Open Data eXchange Query Specification 2010B Version 1.0

 

 

 

Roles

 

Q

18

Please check all Open Data Exchange Web Service roles for which the product is being certified. At least one role must be supported.

 

A

18

Role

Requesting System

YES/NO

Provider System

YES/NO

 

 

 

Requesting System

 

Q

19

If the product performs the role of a Requesting System, please indicate which functions and messages are supported. At least one of the two Function/Message Names must be supported.  Black cells are not applicable.

 

A

19

Function/Message
Description

Function/Message
Name

Mandatory/
Optional

Can provide these

Can initiate these 

Query

HTNG_StatisticsRQ

Mandatory

 

YES/NO

 

 

 

Provider System

 

Q

20

If the product performs the role of a Provider System, please indicate which functions and messages are supported. At least one of the two Function/Message Names must be supported.  Black cells are not applicable.

 

A

20

Function/Message
Description

Function/Message
Name

Mandatory/
Optional

Can provide these

Can initiate these 

Query

HTNG_StatisticsRQ

Mandatory

YES/NO

 

 

HTNG Payment Systems & Data Security Specifications 2010A, Data Proxy Specification Version 1.1

 

 

 

Roles

 

Q

21

Please check all Data Proxy roles for which the product is being certified. At least one role must be supported.

 

A

21

Role

Business Logic System

YES/NO

Proxy Vault

YES/NO

 

 

 

Business Logic System Role

 

Q

22

If the product performs the role of a Business Logic System, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

22

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Request Data Proxy

HTNG_PaymentCardProxyRQ

Mandatory

 

 YES/NO

Request Payment Card

HTNG_PaymentCardRQ

Mandatory

 

YES/NO

 

 

 

Proxy Vault Role

 

Q

23

If the product performs the role of a Proxy Vault, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

23

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Request Data Proxy

HTNG_PaymentCardProxyRQ

Mandatory

YES/NO 

 

Request Payment Card

HTNG_PaymentCardRQ

Mandatory

YES/NO

 

 

HTNG Payment Systems & Data Security Specifications 2010B, Payment Processing Specification Version 2.0

 

 

 

Roles

 

Q

24

Please check all Payment Processing roles for which the product is being certified. At least one role must be supported.

 

A

24

Role

Business Logic System

YES/NO

Payment Processing System

YES/NO

 

 

 

Business Logic System Role

 

Q

25

If the product performs the role of a Business Logic System, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

25

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Balance Inquiry

HTNG_PaymentCardProcessingRQ

Mandatory

 

YES/NO

Authorization

HTNG_PaymentCardProcessingRQ

Mandatory

 

 YES/NO

Incremental Auth

HTNG_PaymentCardProcessingRQ

Optional

 

YES/NO

Auth Reversal

HTNG_PaymentCardProcessingRQ

Mandatory

 

YES/NO

Settlement

HTNG_PaymentCardProcessingRQ

Mandatory

 

 YES/NO

Sale

HTNG_PaymentCardProcessingRQ

Optional

 

 YES/NO

Void Settlement

HTNG_PaymentCardProcessingRQ

Mandatory

 

 YES/NO

Return

HTNG_PaymentCardProcessingRQ

Mandatory

 

 YES/NO

 

 

 

Payment Processing System Role

 

Q

26

If the product performs the role of a Payment Processing System, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

 

 

 

 

 

 

 

A

 

 

 

 

 

 

 

26

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Balance Inquiry

HTNG_PaymentCardProcessingRQ

Mandatory

 YES/NO

 

Authorization

HTNG_PaymentCardProcessingRQ

Mandatory

 YES/NO

 

Settlement

HTNG_PaymentCardProcessingRQ

Mandatory

 YES/NO

 

Sale

HTNG_PaymentCardProcessingRQ

Optional

 YES/NO

 

Incremental Auth

HTNG_PaymentCardProcessingRQ

Mandatory

 YES/NO

 

Auth Reversal

HTNG_PaymentCardProcessingRQ

Mandatory

 YES/NO

 

Void Settlement

HTNG_PaymentCardProcessingRQ

Mandatory

 YES/NO

 

Return

HTNG_PaymentCardProcessingRQ

Mandatory

 YES/NO

 

 

HTNG Product Distribution Specifications 2010B

 

 

 

Roles

 

Q

27

The Product Specification references 7 Usage Profiles and Business Processes which identify three roles. The Product Standard identifies mandatory functionality appropriate to each role/Usage profile combination. Please indicate which roles the product implements.

 

A

27

Role

Reservation Broker

 Reservation Server

Control System

Usage Profile

Reservations

YES/NO

YES/NO

YES/NO

Availability

YES/NO

YES/NO

YES/NO

Statistics

YES/NO

YES/NO

YES/NO

Groups

YES/NO

YES/NO

YES/NO

Rates

YES/NO

YES/NO

YES/NO

Inventory

YES/NO

YES/NO

N/A

Seamless

YES/NO

YES/NO

N/A

 

 

 

Functionality

 

Q

28

Please indicate the functionality implemented. Shaded cells indicate mandatory functionality.

 

A

28

 

 Reservation Broker

 Reservation Server

Control System

Receiving

Sending

Receiving

Sending

Receiving

Sending

Reservations
Usage Profile

(Push)

Update Reservations

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Profile Matching

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Share Handling
with explicit cancel

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Share Handling
without explicit cancel

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Handling of advanced deposits with notification

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Reservations
Usage Profile

(Pull)

Get Reservations

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Update Reservations

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Profile Matching

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Share Handling
with explicit cancel

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Share Handling
without explicit cancel

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Handling of advanced deposits with notification

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Availability
Usage Profile

(Push)

Room Type Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Rate Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Room/Rate Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Segment Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Segment Room Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

House Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Hurdle Rate

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

BAR Rate

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Availability
Usage Profile

(Pull)

Get Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Room Type Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Rate Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Room/Rate Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Segment Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Segment Room Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

House Availability

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Hurdle Rate

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

BAR Rate

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Statistics
Usage Profile

Current Daily Totals Report

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Current Categorized Totals Report

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Past Daily Totals Report

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Past Categorized Totals Report

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Groups
Usage Profile

(Push)

Creation of brand new block 

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Modification of block with pick up information

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Groups
Usage Profile (Pull)

Get Blocks

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Creation of brand new block 

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Modification of block with pick up information

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Rates Usage Profile

(Push)

Update Rates

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Rate Category

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Yieldable Indicators

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Confidential Rates

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Booking Restrictions

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Rate Restrictions

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Day of the Week Patterns

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Total Pricing

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Rate Policy

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Group Rate

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Rates Usage Profile

(Pull)

Get Rates

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Update Rates

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Rate Category

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Yieldable Indicators

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Confidential Rates

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Booking Restrictions

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Rate Restrictions

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Day of the Week Patterns

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Total Pricing

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Rate Policy

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Group Rate

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Inventory Usage Profile

(Push)

Update Inventory 

YES/NO

YES/NO

YES/NO

YES/NO

N/A

N/A

Inventory Usage Profile

(Pull)

Get Inventory

YES/NO

YES/NO

YES/NO

YES/NO

N/A

N/A

Update Inventory 

YES/NO

YES/NO

YES/NO

YES/NO

N/A

N/A

Seamless

Shop 

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Update Reservations

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

Retrieve Reservations

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

YES/NO

 

 

 

Mandatory Elements and Attributes - Part 1:  Reservations, Version 2.4

 

Q

29

Does the product support all the mandatory message Elements and Attributes and all the mandatory behavior applicable to the Reservations Usage Profile functionality identified in Q28?

 

A

29

YES/NO/Not Applicable

 

 

 

Optional Elements and Attributes - Part 1:  Reservations, Version 2.4

 

Q

30

Please indicate all optional Elements and Attributes supported in the Reservations Usage Profile.

 

A

30

 

 

 

 

Mandatory Elements and Attributes - Part 2:  Availability, Version 2.2

 

Q

31

Does the product support all the mandatory message Elements and Attributes and all the mandatory behavior applicable to the Availability Usage Profile functionality identified in Q28?

 

A

31

YES/NO/Not Applicable

 

 

 

Optional Elements and Attributes - Part 2:  Availability, Version 2.2

 

Q

32

Please indicate all optional Elements and Attributes supported in the Availability Usage Profile.

 

A

32

 

 

 

 

Mandatory Elements and Attributes - Part 3:  Statistics, Version 2.0

 

Q

33

Does the product support all the mandatory message Elements and Attributes and all the mandatory behavior applicable to the Statistics Usage Profile functionality identified in Q28?

 

A

33

YES/NO/Not Applicable

 

 

 

Optional Elements and Attributes - Part 3:  Statistics, Version 2.0

 

Q

34

Please indicate all optional Elements and Attributes supported in the Statistic Usage Profile.

 

A

34

 

 

 

 

Mandatory Elements and Attributes - Part 4:  Groups, Version 1.2

 

Q

35

Does the product support all the mandatory message Elements and Attributes and all the mandatory behavior applicable to the Groups Usage Profile functionality identified in Q28?

 

A

35

YES/NO/Not Applicable

 

 

 

Optional Elements and Attributes - Part 4:  Groups, Version 1.2

 

Q

36

Please indicate all optional Elements and Attributes supported in the Groups Usage Profile.

 

A

36

 

 

 

 

Mandatory Elements and Attributes - Part 5:  Rates, Version 1.2

 

Q

37

Does the product support all the mandatory message Elements and Attributes and all the mandatory behavior applicable to the Rates Usage Profile functionality identified in Q28?

 

A

37

YES/NO/Not Applicable

 

 

 

Optional Elements and Attributes - Part 5:  Rates, Version 1.2

 

Q

38

Please indicate all optional Elements and Attributes supported in the Rates Usage Profile.

 

A

38

 

 

 

 

Mandatory Elements and Attributes - Part 6:  Inventory, Version 1.0

 

Q

39

Does the product support all the mandatory message Elements and Attributes and all the mandatory behavior applicable to the Inventory Usage Profile functionality identified in Q28?

 

A

39

YES/NO/Not Applicable

 

 

 

Optional Elements and Attributes - Part 6:  Inventory, Version 1.0

 

Q

40

Please indicate all optional Elements and Attributes supported in the Inventory Usage Profile.

 

A

40

 

 

 

 

Mandatory Elements and Attributes - Part 7:  Seamless Shop/Book, Version 1.1

 

Q

41

Does the product support all the mandatory message Elements and Attributes and all the mandatory behavior applicable to the Seamless Shop/Book Usage Profile functionality identified in Q28?

 

A

41

YES/NO/Not Applicable

 

 

 

Optional Elements and Attributes - Part 7:  Seamless Shop/Book, Version 1.1

 

Q

42

Please indicate all optional Elements and Attributes supported in the Seamless Shop/Book Usage Profile.

 

A

42

 

 

 

 

TPA Extension Usage

 

Q

43

Please indicate if any TPA extensions are used.

 

A

43

YES/NO

 

 

 

TPA Extension Usage Description

 

Q

44

If Q43 was answered Yes, applicants may also optionally describe how they are used:

Applicants are expected to describe the use of TPA extensions in their submission if these extensions are used to implement functionality that is:

  • currently being reviewed by HTNG (or the OpenTravel Alliance) for possible inclusion in a future release of the specification
  • is expected to be submitted to HTNG (or the OpenTravel Alliance) for consideration for inclusion in a future release of the specification
  • is available  to 3rd parties in the public domain to use freely in their interfaces to this and other products

Applicants are advised not to describe, in detail, use of TPA extensions for functionality that they consider to be intellectual property of their own or partner organizations; or where such description would violate partnership agreements or applicable copyright laws. They should, however, still indicate that they are using TPA extensions (in Q43 above).

 

A

44

 

 

 

 

Communications Types

 

Q

45

Please indicate all communication type supported by the product. At least one communication type must be supported.

 

A

45

SOAP/HTTP (Sync)

YES/NO

SOAP/HTTP (Async)

YES/NO

HTTP

YES/NO

HTTPS

YES/NO

 

HTNG Property Web Services Specifications 2009B – Part 1: Web Services Framework 2.1.1

 

 

 

 

Identify the Web Services that utilize Web Services Framework 2.1.1

 

Q

46

Please identify each Web service supported. The majority correspond to published HTNG Specifications. The last entry allows for proprietary services to be referenced.
Interoperability must be demonstrated by providing one of the following:

  1. The name of other companies with whom you have successfully interoperated.
  2. A test report from internal testing. These can be either a URL on your own website or as inline text in the Supporting Document Table below.
  3. Other evidence of a successful implementation.

At least one web service must be implemented unless conforming ONLY to Back Office Version 2.0 or Kiosk Integration Version 2.0.

 

A

46

Web Services Implemented

Web Service Name

Interoperable Vendors, Test Report URL, or Supporting Document Number (see table below)

HTNG Guest & Room Status Messaging Specifications 2010B Version 1.1

YES

HTNG XML

HTNG Kiosk Integration Specifications 2010B Version 2.0

NO

 

HTNG Open Data eXchange Query Specification 2010B Version 1.0

NO

 

HTNG Payment Systems & Data Security Specifications 2010B, Payment Processing Specification Version 2.0

NO

 

HTNG Product Distribution Specifications 2010B – Part 1:  Reservations, Version 2.4

NO

 

HTNG Product Distribution Specifications 2010B – Part 2:  Availability, Version 2.2

Note: Release 2010A and 2009B is identical and acceptable

NO

 

HTNG Product Distribution Specifications 2010B – Part 3:  Statistics, Version 2.0

Note: Releases 2010A, 2009B, 2009A and 2008A are identical and acceptable

NO

 

HTNG Product Distribution Specifications 2010B – Part 4:  Groups, Version 1.2

NO

 

HTNG Product Distribution Specifications 2010B – Part 5:  Rates, Version 1.2

Note: Release 2010A is identical and acceptable

NO

 

HTNG Product Distribution Specifications 2010B – Part 6:  Inventory, Version 1.0

Note: Release 2010A is identical and acceptable

NO

 

HTNG Product Distribution Specifications 2010B – Part 7:  Seamless Shop/Book, Version 1.1

NO

 

HTNG Product Distribution Specifications 2010A - Part 1: Reservations Version 2.3

NO

 

HTNG Product Distribution Specifications 2010A - Part 2: Availability Version 2.2

Note: Release 2009B is identical and acceptable

NO

 

HTNG Product Distribution Specifications 2010A - Part 3: Statistics Version 2.0

Note: Releases 2009B, 2009A and 2008A are identical and acceptable

NO

 

HTNG Product Distribution Specifications 2010A - Part 4: Groups Version 1.1

Note: Release 2009B is identical and acceptable

NO

 

HTNG Product Distribution Specifications 2010A - Part 5: Rates Version 1.2

NO

 

HTNG Product Distribution Specifications 2010A - Part 6: Inventory Version 1.0

NO

 

HTNG Product Distribution Specifications 2010A - Part 7: Seamless Shop/Book Version 1.0

NO

 

HTNG Property Web Services Specifications 2009B - Part 2: Single Guest Itinerary Version 2.2.1
Note: Releases 2009A and 2008B are identical and acceptable

YES

Micros, Certification of FCS 2 Way HTNG Interface to Opera

HTNG Property Web Services Specifications 2009B - Part 3: Digital Signage Version 1.0
Note: Releases 2009A, 2008B and 2008A are identical and acceptable

NO

 

HTNG Property Web Services Specifications 2009B - Part 4: Open Data Exchange Version 1.4.2

Note: Release 2009A is identical and acceptable

NO

 

HTNG Property Web Services Specifications 2009B - Part 6: Guest Self Service Version 1.0.3

Note: Release 2009A is identical and acceptable

NO

 

HTNG Property Web Services Specifications 2009B - Part 7: Food and Beverage Ordering Version 1.0

Note: Releases 2009A and 2008B are identical and acceptable

NO

 

HTNG Property Web Services Specification 2009B – Part 8: Guest & Room Status Messaging Version 1.0

NO

 

HTNG Property/Distribution Specifications 2009B - Part 1: Reservations Version 2.2

NO

 

HTNG Property/Distribution Specifications 2009B - Part 2: Availability Version 2.2

NO

 

HTNG Property/Distribution Specifications 2009B - Part 3: Statistics Version 2.0

Note: Releases 2009A and 2008A are identical and acceptable

NO

 

HTNG Property/Distribution Specifications 2009B - Part 4: Groups Version 1.1

NO

 

HTNG Property/Distribution Specifications 2009B - Part 5: Rates Version 1.2

NO

 

HTNG Property/Distribution Specifications 2009A - Part 1: Reservations Version 2.1

NO

 

HTNG Property/Distribution Specifications 2009A - Part 2: Availability Version 2.1

NO

 

HTNG Property/Distribution Specifications 2009A - Part 4: Groups Version 1.0

Note: Release 2008A is identical and acceptable

NO

 

HTNG Property/Distribution Specifications 2009A - Part 5: Rates Version 1.1

NO

 

HTNG Property Web Services Specifications 2008B - Part 4: Open Data Exchange Version 1.4.1

NO

 

HTNG Property Web Services Specifications 2008B - Part 6: Guest Self Service Version 1.0.1

NO

 

HTNG Property Web Services Specifications 2008A - Part 2: Single Guest Itinerary Version 1.0

Note: Release 2007A is identical and acceptable

NO

 

HTNG Property Web Services Specifications 2008A - Part 4: Open Data Exchange Version 1.0

NO

 

HTNG Property Web Services Specifications 2008A - Part 6: Guest Self Service Version 1.0

NO

 

HTNG Property/Distribution Specifications 2008A - Part 1: Reservations Version 2.0

NO

 

HTNG Property/Distribution Specifications 2008A - Part 2: Availability Version 2.0

NO

 

HTNG Property/Distribution Specifications 2008A - Part 5: Rates Version 1.0

Note: Release 2007A is identical and acceptable

NO

 

HTNG Property/Distribution Specifications 2007A - Part 1: Reservations Version 1.0

NO

 

HTNG Property/Distribution Specifications 2007A - Part 2: Availability Version 1.0

NO

 

Proprietary System(s)

NO

 

 

 

 

Details of Proprietary Systems

 

Q

47

Please provide a summary description of any proprietary systems identified in A6.
Add rows to the table as required.

 

A

47

System Name

Version Number

Summary of System Details

Contact Name

Date of Implementation

FCS UBIS

 3.20.0

Call Accounting & PMS Interface System 

 Chong Kee HOO (Mr)

 

 

 

 

Supporting Documents

 

Q

48A

The table below defines six possible supporting documents which provide evidence of conformance. Four of these are mandatory (denoted by shading). The Published API Specification should be used to reference the published HTNG specification that is supported. These documents may be provided either as a URL to an external site or as inline text in the Supporting Document Table below.

Replicate this table for each Web Service supported.

 

A

48A

HTNG Property Web Services Specifications 2009B - Part 2: Single Guest Itinerary Version 2.2.1

Documentation Provided

Mandatory/
Optional

HTNG Specification Reference, URL, or Supporting Document Number (see table below)

WSDL

Mandatory

 HTNG Property Web Services 2009B Specifications, Activity.wsdl

Schemas externally referenced in WSDL

Mandatory

 HTNG Property Web Services 2009B Specifications,

Activity.xsd, Common.xsd, Name.xsd, PmtPosting.xsd, Reservation.xsd

SOAP Packet Trace

Mandatory

 FCS_Initiate_Message, FCS Provides Web Service Functions

Published API Specification

Mandatory for HTNG defined Web Services

  HTNG Property Web Services 2009B Specifications,

Write-up on WS Security Implementation

Optional

 

Write-up on WS Addressing Implementation

Optional

 

HTNG Guest & Room Status Messaging Specification 2010B Version 1.1

Documentation Provided

Mandatory/
Optional

HTNG Specification Reference, URL, or Supporting Document Number (see table below)

WSDL

Mandatory

HTNG Guest & Room Status Messaging 2010B Specifications, GRSMAPI.wsdl

Schemas externally referenced in WSDL

Mandatory

HTNG Guest & Room Status Messaging 2010B Specifications,

GRSMAPI.xsd, schema1.xsd, schema2.xsd, schema3.xsd

SOAP Packet Trace

Mandatory

HTNG XML

Published API Specification

Mandatory for HTNG defined Web Services

HTNG Guest & Room Status Messaging 2010B Specifications,

Write-up on WS Security Implementation

Optional

 

Write-up on WS Addressing Implementation

Optional

 

 

Q

48B

The following table is provided for supporting documents. If the document cannot be referenced as a URL, please insert the contents of the document into a row of the table below, adding an appropriate title and referencing it in A 46 or A 48A above. Insert additional table entries as required.

 

A

48B

 

Document Title

1

For Q46  <insert web service name> - Interoperability Test Report
or
for Q48A  <insert web service name> - <insert document title>

Certification of FCS 2 Way HTNG Interface to Opera

 

 

 

Communication Style

 

Q

49

Indicate which communication methods the product supports. At least one communication style must be supported.

 

A

49

Communication Style

Synchronous

YES

Asynchronous

NO

 

HTNG Property Web Services Specifications 2009B – Part 2: Single Guest Itinerary Version 2.2.1

 

Indicate which communication methods the product supports. At least one communication style must be supported.

 

 

Roles

 

Q

50

Please check all Single Guest Itinerary Web Service roles for which the product is being certified. At least one role must be supported.

 

 A

50 

Role

Activity Reservation System

YES

Accommodation Reservation System

NO

Posting System

YES

Folio System

NO

Customer Profile System

NO

Itinerary Consolidation System

NO

Itinerary Display System

NO

 

 

 

Activity Reservation System Role

 

Q

51

If the product performs the role of an Activity Reservation System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

 A

51 

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Lookup Activities for matching guests

ActivityLookup

Mandatory

YES

 

Create Activity

CreateActivity

Mandatory

 

YES

Update Activity

UpdateActivity

Mandatory

 

YES

Cancel Activity

CancelActivity

Mandatory

 

YES

List Activities for a specific guest

FetchActivities

Mandatory

YES

 

Lookup Matching Guest Profiles

ProfileLookup

Mandatory

NO

YES

Fetch detailed information for a specific guest profile

FetchProfile

Mandatory

NO

YES

Create new profile

NewProfile

Optional

NO

YES

Modify existing profile

UpdateProfile

Mandatory

YES

YES

Notify when appointment time is outside of stay dates

OutOfScopeNotification

Mandatory

YES

 

Notification of status change

GuestStatusNotification

Mandatory

YES

 

Link new profile ID to another system

Subscription

Mandatory

NO

YES

Lookup matching reservations

ReservationLookup

Optional

 

YES

Fetch specific reservation details

FetchReservation

Optional

 

YES

Notify of guest location

LocationNotification

Optional

 

YES

Send guest message

GuestMessage

Optional

 

YES

Merge guest profile

MergeProfile

Mandatory

NO

YES

 

 

 

Accommodation Reservation System Role

 

Q

52

If the product performs the role of an Accommodation Reservation System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

 A

 52

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Notify when reservation stay date range with scheduled appointment is moved outside of appointment date

OutOfScopeNotification

Mandatory

 

YES/NO

Notification of status change

GuestStatusNotification

Mandatory

 

YES/NO

Lookup matching reservations

ReservationLookup

Mandatory

YES/NO

 

Fetch specific reservation details

FetchReservation

Mandatory

YES/NO

 

Notify of guest location

LocationNotification

Mandatory

YES/NO

 

Send guest message

GuestMessage

Mandatory

YES/NO

 

 

 

 

Posting System Role

 

Q

53

If the product performs the role of a Posting System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

 A

53 

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Post charge

PostPayment

Mandatory

 

YES

Retrieve details of a POS check

FetchCheckDetails

Optional

NO

 

 

 

 

Folio System Role

 

Q

54

If the product performs the role of a Folio System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

 A

 54

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Post charge for related activity

PostPayment

Mandatory

YES/NO

 

Retrieve details of a POS check

FetchCheckDetails

Optional

 

YES/NO

 

 

 

Customer Profile System Role

 

Q

55

If the product performs the role of a Customer Profile System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

 A

55 

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Lookup Matching Guest Profiles

ProfileLookup

Mandatory

YES/NO

YES/NO

Fetch detailed information for a specific guest profile

FetchProfile

Mandatory

YES/NO

YES/NO

Create new profile

NewProfile

Optional

YES/NO

YES/NO

Modify existing profile

UpdateProfile

Mandatory

YES/NO

YES/NO

Link new profile ID to another system

Subscription

Mandatory

YES/NO

YES/NO

Merge guest profile

MergeProfile

Mandatory

YES/NO

YES/NO

 

 

 

Itinerary Consolidation System Role

 

Q

56

If the product performs the role of an Itinerary Consolidation System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

56 

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Lookup Activities for matching guests

ActivityLookup

Mandatory

YES/NO

YES/NO

Create Activity

CreateActivity

Mandatory

YES/NO

 

Update Activity

UpdateActivity

Mandatory

YES/NO

 

Cancel Activity

CancelActivity

Mandatory

YES/NO

 

List Activities for a specific guest

FetchActivities

Mandatory

YES/NO

YES/NO

 

 

 

Itinerary Display System Role

 

Q

57

If the product performs the role of an Itinerary Display System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

57

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

List Activities for a specific guest

FetchActivities

Mandatory

 

YES/NO

Lookup matching reservations

ReservationLookup

Mandatory

 

YES/NO

 

HTNG Property Web Services Specifications 2009B – Part 3: Digital Signage Version 2.2

 

If the product performs the role of an Itinerary Display System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

 

Roles

 

Q

58

Please check all Digital Signage Web Service roles for which the product is being certified. At least one role must be supported.

 

A

58

Does the Product function as an Event Information Display Manager?

YES/NO

Does the Product function as an Event and Meeting Space Manager?

YES/NO

 

 

 

Event Information Display Manager Role

 

Q

59

If the product performs the role of an Event Information Display Manager please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

59

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate/consume these messages

Request Reserved Meeting Space

MeetingSpaceRequest

Mandatory

 

YES/NO

MeetingSpaceResponse

Mandatory

 

YES/NO

Request Meeting Space Characteristics

MeetingSpaceCharacteristicsRequest

Mandatory

 

YES/NO

MeetingSpaceCharacteristicsResponse

Mandatory

 

YES/NO

 

 Q

60 

If the product performs the role of an Event Information Display Manager please indicate which message parameters are supported.

 

A

60

Request Message / Request Event Information By:

Parameter Name

Mandatory/
Optional

 

Start Time

startTime

Optional

YES/NO

End Time

endTime

Optional

YES/NO

Event Identifier

eventKey

Optional

YES/NO

Exhibit Flag – Y/N

isExhibit

Optional

YES/NO

Postable Flag – Y/N

isPostable

Optional

YES/NO

Room Grouping

roomGrouping

Optional

YES/NO

 

Parameter Description

Parameter Name

Mandatory/
Optional

 

Group logo URL or pathname

logoURL

Optional

YES/NO

Meeting Name and related identifier

meetingName

Optional

YES/NO

Meeting “Post As” Name

meetingPostAs

Optional

YES/NO

Host Event Identifier

hostEventKey

Optional

YES/NO

Exhibit Flag – Y/N

isExhibit

Optional

YES/NO

Postable Flag – Y/N

isPostable

Optional

YES/NO

Backup Meeting Room Space Name

backupMeetingRoomName

Optional

YES/NO

Overflow Meeting Room Space Name

overflowMeetingRoomName

Optional

YES/NO

Response Complete – Y/N

isResponseComplete

Optional

YES/NO

 

 

 

Event and Meeting Space Manager Role

 

Q

61

If the product performs the role of an Event and Meeting Space Manager please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

61

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate/consume these messages

Request Reserved Meeting Space

MeetingSpaceRequest

Mandatory

YES/NO

 

MeetingSpaceResponse

Mandatory

YES/NO

 

Request Meeting Space Characteristics

MeetingSpaceCharacteristicsRequest

Mandatory

YES/NO

 

MeetingSpaceCharacteristicsResponse

Mandatory

YES/NO

 

 

Q

62

If the product performs the role of an Event and Meeting Space Manager please indicate which message parameters are supported.

 

A

62

Parameter Description

Parameter Name

Mandatory/
Optional

 

Floor Number

floorNumber

Optional

YES/NO

Floor Description

floorDescription

Optional

YES/NO

Room Grouping

roomGrouping

Optional

YES/NO

Directions

directions

Optional

YES/NO

Is Room Divisible – Y/N

isDivisible

Optional

YES/NO

Parent Room Identifier

parentRoomKey

Optional

YES/NO

Map Reference Number

mapReferenceNum

Optional

YES/NO

 

 

 

 

Response Complete - Y/N

isResponseComplete

Optional

YES/NO

 

HTNG Property Web Services Specifications 2009B – Part 4: Open Data eXchange Basic Version 1.4.2

 

If the product performs the role of an Event and Meeting Space Manager please indicate which message parameters are supported.

 

 

Roles

 

Q

63

Please check all Open Data Exchange Web Service roles for which the product is being certified. At least one role must be supported.

 

A

63

Does the Product function as a Data Receiver?

YES/NO

Does the Product function as a Data Sender

YES/NO

 

 

 

Data Receiver

 

Q

64

If the product performs the role of a Data Receiver, please indicate which functions and messages are supported. At least one of the two Function/Message Names must be supported.  Black cells are not applicable.

 

A

64

Function/Message
Description

Function/Message
Name

Can provide these

Can initiate these 

Push Files

PushFile

YES/NO  

 

Pull Files

PullFile

 

YES/NO

 

 

 

Data Sender

 

Q

65

If the product performs the role of Data Sender, please indicate which functions and messages are supported. At least one of the Function/Message Names must be supported.

 

A

65

Function/Message
Description

Function/Message
Name

Can provide these

Can initiate these 

Push Files

PushFile

 

YES/NO

Pull Files

PullFile

YES/NO  

 

 

HTNG Property Web Services Specifications 2009B – Part 5 Back Office Integration Version 2.0

 

If the product performs the role of Data Sender, please indicate which functions and messages are supported. At least one of the Function/Message Names must be supported.

 

 

Roles

 

Q

66

Please check all Back Office Integration roles for which the product is being certified. At least one role must be supported.

 

A

66

Role

Service Implementer

YES/NO

Service Caller

YES/NO

 

 

 

Service Implementer

 

Q

67

In order to post an entry into an Accounting Application, it is typically required that the entry be balanced (debits equal credits), but it is realized that many Service Callers do not have mechanisms in place to perform or ensure such balancing.  As such, we are requiring the Service Implementer to ensure that any balancing requirements are met.

 

A

67

Please indicate whether your application includes balancing functionality.

Mandatory

YES/NO

 

Q

68

Data transformations (e.g. Account Code Mapping, Transaction Analysis, Appending…) is not a function of the Specification but is a known requirement to send data to a Back Office Destination. 

 

A

68

Please indicate whether your application will include transformation functionality.

Optional

YES/NO

 

Q

69

Understanding that many service callers cannot accommodate destination Attributes, it will be the responsibility of Service Implementer to ensure the proper Attributes required by the Destination system are present.

 

A

69

Please indicate whether your application includes functionality to accommodate Destination System Attributes.

Optional

YES/NO

 

Q

70

If there is a desire to ensure that payloads received are not processed multiple times, the service implementer can utilize and track a combination of the SourceID and MessageID elements of the PostGeneralLedgerData element. This will be the responsibility of the destination Service Implementer but it can only be implemented if the source ensures that the SourceID and MessageID elements are used correctly.

 

A

70

Please indicate whether your application ensures that payloads with unique combinations of SourceID and MessageID are not processed multiple times.

Optional

YES/NO

 

 

 

Service Caller

 

Q

71

There is a desire to ensure that payloads received are not processed multiple times.  The service implementer can utilize and track a combination of the SourceID and MessageID elements of the PostGeneralLedgerData element. The source ensures that the SourceID and MessageID elements are used correctly.

 

A

71

Will you ensure that MessageID elements will be unique for every service call?

Mandatory

YES/NO

 

Q

72

Statistical entries such as Hours Worked should be transmitted in the form of GLJournalLine and the statistical value should be stored as the Amount.

 

A

72

Please indicate whether your application includes statistical values.

Mandatory

YES/NO

 

Q

73

Accounting Applications have specific Account Types, such as Revenue for which a positive number must be indicated as a Credit, as compared to an Expense for which a positive number is a Debit.  In addition, Accounting Applications require non-statistical entries to balance.

 

A

73a

Please indicate whether your Debit/Credit indicators will be in line with the GAAP principles.

Optional

YES/NO

 

A

73b

Please indicate whether you will be providing a balanced file (Debits equal Credits) for non-statistical amounts.

Optional

YES/NO

 

Q

74

Data transformations (e.g. Account Code Mapping, Transaction Analysis, Appending…) is not a function of the Specification but is an expected requirement to send data to a Back Office Destination. 

 

A

74

Please indicate whether your payload will provide data using the destination accounting systems scheme (will you provide account code mapping?).

Optional

YES/NO

 

Q

75

Back Office Specification 2.0 covers only generic General Ledger Transactions, and additional specifications will be provided regarding specific transaction types in the future.  Below, we have proposed Attribute Names by Role.   Service Callers should indicate the attributes they will be providing:

 

A

75

GLAttribute Name

GLAttribute Value

Parent of GLAttribute

Example

Mandatory/ Optional

Will Provide

RETAIL

RevenueCenter

String

GLJournalLine

Specific code, name of outlet

Optional

Yes/No

Shift

String

GLJournalLine

Time Period (am, pm)

Optional

Yes/No

CustomerType

String

GLJournalLine

Resident, Non-Resident

Optional

Yes/No

F&B

RevenueCenter

String

GLJournalLine

Specific code, name of outlet

Optional

Yes/No

Revenue CenterType

String

GLJournalLine

Bar, Self Service

Optional

Yes/No

MealPeriod

String

GLJournalLine

Breakfast, Lunch, Dinner

Optional

Yes/No

CustomerType

String

GLJournalLine

Resident, Non-Resident

Optional

Yes/No

HOTEL PMS

Department

String

GLJournalLine

Front Office, Housekeeping

Optional

Yes/No

MarketSegment

String

GLJournalLine

Luxury, Business

Optional

Yes/No

BookingSource

String

GLJournalLine

Email, Phone, Walk-in, Internet

Optional

Yes/No

RoomType

String

GLJournalLine

Single, Double, Suite

Optional

Yes/No

CustomerType

String

GLJournalLine

Resident, Non-Resident

Optional

Yes/No

SPA

RevenueCenter

String

GLJournalLine

Specific code or name

Optional

Yes/No

ActivityType

String

GLJournalLine

Massage, Peeling

Optional

Yes/No

ProviderType

String

GLJournalLine

Internal, External, Therapist Qualification

Optional

Yes/No

FacilityType

String

GLJournalLine

Pool, Sauna

Optional

Yes/No

Package

String

GLJournalLine

Specific code or name

Optional

Yes/No

GOLF

GolfClub

String

GLJournalLine

Specific code or name

Optional

Yes/No

GolfCourse

String

GLJournalLine

Specific code or name

Optional

Yes/No

CustomerType

String

GLJournalLine

Resident, Non-Resident

Optional

Yes/No

Package

String

GLJournalLine

Specific code or name

Optional

Yes/No

FeeType

String

GLJournalLine

Green fee, Member fee

Optional

Yes/No

LABOR OR PAYROLL

Employee

String

GLJournalLine

Code, Name, Number

Optional

Yes/No

Position

String

GLJournalLine

Front Office Manager, Bartender

Optional

Yes/No

Department

String

GLJournalLine

Marketing, Finance, Front Office

Optional

Yes/No

Increment

String

GLJournalLine

Daily, Weekly, Monthly

Optional

Yes/No

 

HTNG Property Web Services Specifications 2009B – Part 6: Guest Self Service Version 1.0.3

 

Back Office Specification 2.0 covers only generic General Ledger Transactions, and additional specifications will be provided regarding specific transaction types in the future.  Below, we have proposed Attribute Names by Role.   Service Callers should indicate the attributes they will be providing:

 

 

Roles

 

Q

76

Please check all Guest Self Service Web Service roles for which the product is being certified. At least one role must be supported.

 

A

76

Role

Self Service Frontend

YES/NO

Services Scheduling System

YES/NO

 

 

 

Self Service Frontend

 

Q

77

If the product performs the role of a Self Service Frontend please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

77

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Create new profile

NewProfile

Optional

YES/NO

YES/NO

Modify existing profile

UpdateProfile

Mandatory

YES/NO

YES/NO

Merge guest profile

MergeProfile

Mandatory

YES/NO

YES/NO

List template categories

TemplateCategory

Mandatory

 

YES/NO

List templates

TemplateInfo

Mandatory

 

YES/NO 

List payment conditions

PaymentCondition

Optional

 

YES/NO

Request availabilities

Availability

Mandatory

 

YES/NO

Create booking

Create

Mandatory

 

YES/NO

Delete booking

Delete

Optional

 

YES/NO 

Pay bookings

Sale

Optional

 

YES/NO

List bookings

FetchBooking

Optional

 

YES/NO

 

 

 

Services Scheduling System

 

Q

78

If the product performs the role of a Services Scheduling System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

78

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Create new profile

NewProfile

Optional

YES/NO

YES/NO

Modify existing profile

UpdateProfile

Mandatory

YES/NO

YES/NO

Merge guest profile

MergeProfile

Mandatory

YES/NO

YES/NO

List template categories

TemplateCategory

Mandatory

YES/NO

 

List templates

TemplateInfo

Mandatory

YES/NO 

 

List payment conditions

PaymentCondition

Optional

YES/NO

 

Request availabilities

Availability

Mandatory

YES/NO

 

Create booking

Create

Mandatory

YES/NO

 

Delete booking

Delete

Optional

YES/NO 

 

Pay bookings

Sale

Optional

YES/NO

 

List bookings

FetchBooking

Optional

YES/NO

 

 

HTNG Property Web Services Specifications 2009B – Part 7: Food and Beverage Ordering Version 1.0

 

If the product performs the role of a Services Scheduling System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

 

Roles

 

Q

79

Please check all Food and Beverage Ordering Web Service roles for which the product is being certified. At least one role must be supported.

 

A

79

Role

Device (Kiosk, Touch Screen, In-Room TV, IP Phone, etc)

YES/NO

Food and Beverage POS System

YES/NO

 

 

 

Device Role

 

Q

80

If the product performs the Device Role please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

80

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Gets configuration information

GetConfigurationInfo

Mandatory

 

YES/NO

Calculates transaction totals

CalculateTotals

Mandatory

 

YES/NO

Gets a transaction

GetTransaction

Mandatory

 

YES/NO

Gets a transaction delivery status

GetTransactionDeliveryStatus

Mandatory

 

YES/NO

Post new transaction

PostNewTransaction

Mandatory

 

YES/NO

Spit a transaction into multiple transactions

SplitTransaction

Mandatory

 

YES/NO

 

 

 

Food and Beverage POS System

 

Q

81

If the product performs the role of a Food and Beverage POS System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

 

A

81

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Gets configuration information

GetConfigurationInfo

Mandatory

YES/NO

 

Calculates transaction totals

CalculateTotals

Mandatory

YES/NO

 

Gets a transaction

GetTransaction

Mandatory

YES/NO

 

Gets a transaction delivery status

GetTransactionDeliveryStatus

Mandatory

YES/NO

 

Post new transaction

PostNewTransaction

Mandatory

YES/NO

 

Spit a transaction into multiple transactions

SplitTransaction

Mandatory

YES/NO

 

 

Certification Summary

 

 

 

 

The Trademark License Agreement allows for a Product Specification to require display of a Certification Summary along with the Trademark. For this Product Specification, no summary is required.

 


Revision History

2010B, Issue 1.0 – October 22, 2010

2010B, Issue 2.0 – May 6, 2011

·       Updated the table in question 46 to include the following specifications (due to error in previous issue):

o   HTNG Guest & Room Status Messaging Specifications 2010B Version 1.1

o   HTNG Kiosk Integration Specifications 2010B Version 2.0

o   HTNG Open Data eXchange Query Specification 2010B Version 1.0

o   HTNG Payment Systems & Data Security Specifications 2010B, Payment Processing Specification Version 2.0

o   HTNG Product Distribution Specifications 2010B – Part 3:  Statistics, Version 2.0

§  Includes note that Releases 2010A, 2009B, 2009A and 2008A are identical and acceptable

o   HTNG Product Distribution Specifications 2010B – Part 4:  Groups, Version 1.2

o   HTNG Product Distribution Specifications 2010B – Part 5:  Rates, Version 1.2

§  Includes note that Release 2010A is identical and acceptable

o   HTNG Product Distribution Specifications 2010B – Part 6:  Inventory, Version 1.0

§  Includes note that Release 2010A is identical and acceptable

o   HTNG Product Distribution Specifications 2010B – Part 7:  Seamless Shop/Book, Version 1.1

o   HTNG Product Distribution Specifications 2010A - Part 1: Reservations Version 2.3

o   HTNG Product Distribution Specifications 2010A - Part 2: Availability Version 2.2

§  Includes note that Release 2009B is identical and acceptable

·       Replaced any mention of “Guest and Room Status Messaging” with “Guest & Room Status Messaging”

 


Copyright © 2010 HTNG, All Rights Reserved