Hotel Technology Next Generation

Conformance Statement Questionnaire

Property Web Services

Version 2010A

Referenced Documents

HTNG Property Web Services Product Specification 2010A
HTNG Property Web Services Specifications 2009B

Part 1: Web Services Framework Version 2.1.1
Part 2: Single Guest Itinerary Version 2.2
Part 3: Digital Signage Version 1.0
Part 4: Open Data Exchange Version 1.4.2
Part 5: Back Office Integration Version 2.0
Part 6: Guest Self Service Version 1.0.3
Part 7: Food and Beverage Ordering Version 1.0
Part 8: Guest and Room Status Messaging Version 1.0

HTNG Kiosk Integration Specifications 2010A
WS-I Basic Profile 1.0
WS-Security 1.0 Specification

Instructions to applicants are given in blue text.

Note to submitter: This form contains a series of questions that need to be answered. Please complete ALL the fields in the questionnaire below to produce a conformance statement for your product. 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

Please enter your company name.

Contact Information

Please enter the name of the author of this conformance statement questionnaire.

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

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

Product Version/Identifier

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

Scope of Certification

Specifications Implemented

The Product Specification requires conformance to either the Framework 2.1.1, the Back Office 2.0 Specification, or the Kiosk Integration 1.0 Specification. If conforming to anything other than Back Office 2.0 or Kiosk Integration 1.0, conformance to Framework 2.1.1 is mandatory. Please indicate to which specifications the product conforms; at least one of the lines below must be answered ‘yes.’

HTNG Web Services Framework Version 2.1.1 (mandatory unless conforming ONLY to Back Office 2.0 or Kiosk Integration 1.0)	YES/NO
HTNG Single Guest Itinerary Version 2.2 (optional)	YES/NO
HTNG Digital Signage Version 1.0 (optional)	YES/NO
HTNG Open Data Exchange Version 1.4.2 (optional)	YES/NO
HTNG Back Office Integration Version 2.0 (optional)	YES/NO
HTNG Guest Self Service Version 1.0.3 (optional)	YES/NO
HTNG Food and Beverage Ordering Version 1.0 (optional)	YES/NO
HTNG Guest and Room Status Messaging Version 1.0 (optional)	YES/NO
HTNG Kiosk Integration Version 1.0 (optional)	YES/NO

Web Services Framework 2.1.1 Conformance (mandatory unless conforming ONLY to Back Office 2.0 or Kiosk Integration 1.0)

Identify the Web Services that utilize Web Services Framework 2.1.1

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

The name of other companies with whom you have successfully interoperated.
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.
Other evidence of a successful implementation.

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

Web Services Implemented
Web Service Name		Interoperable Vendors, Test Report URL, or Supporting Document Number (see table below)
HTNG Product Distribution Specifications 2010A - Part 1: Reservations Version 2.3	YES/NO
HTNG Product Distribution Specifications 2010A - Part 2: Availability Version 2.2 Note: Release 2009B is identical and acceptable	YES/NO
HTNG Product Distribution Specifications 2010A - Part 3: Statistics Version 2.0 Note: Releases 2009B, 2009A and 2008A are identical and acceptable	YES/NO
HTNG Product Distribution Specifications 2010A - Part 4: Groups Version 1.1 Note: Release 2009B is identical and acceptable	YES/NO
HTNG Product Distribution Specifications 2010A - Part 5: Rates Version 1.2	YES/NO
HTNG Product Distribution Specifications 2010A - Part 6: Inventory Version 1.0	YES/NO
HTNG Product Distribution Specifications 2010A - Part 7: Seamless Shop/Book Version 1.0	YES/NO
HTNG Property Web Services Specifications 2009B - Part 2: Single Guest Itinerary Version 2.2 Note: Releases 2009A and 2008B are identical and acceptable	YES/NO
HTNG Property Web Services Specifications 2009B - Part 3: Digital Signage Version 1.0 Note: Releases 2009A, 2008B and 2008A are identical and acceptable	YES/NO
HTNG Property Web Services Specifications 2009B - Part 4: Open Data Exchange Version 1.4.2 Note: Release 2009A is identical and acceptable	YES/NO
HTNG Property Web Services Specifications 2009B - Part 6: Guest Self Service Version 1.0.3 Note: Release 2009A is identical and acceptable	YES/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	YES/NO
HTNG Property Web Services Specification 2009B – Part 8: Guest and Room Status Messaging Version 1.0	YES/NO
HTNG Property Web Services Specifications 2008B - Part 4: Open Data Exchange Version 1.4.1	YES/NO
HTNG Property Web Services Specifications 2008B - Part 6: Guest Self Service Version 1.0.1	YES/NO
HTNG Property Web Services Specifications 2008A - Part 2: Single Guest Itinerary Version 1.0 Note: Release 2007A is identical and acceptable	YES/NO
HTNG Property Web Services Specifications 2008A - Part 4: Open Data Exchange Version 1.0	YES/NO
HTNG Property Web Services Specifications 2008A - Part 6: Guest Self Service Version 1.0	YES/NO
HTNG Property/Distribution Specifications 2009B - Part 1: Reservations Version 2.2	YES/NO
HTNG Property/Distribution Specifications 2009B - Part 2: Availability Version 2.2	YES/NO
HTNG Property/Distribution Specifications 2009B - Part 3: Statistics Version 2.0 Note: Releases 2009A and 2008A are identical and acceptable	YES/NO
HTNG Property/Distribution Specifications 2009B - Part 4: Groups Version 1.1	YES/NO
HTNG Property/Distribution Specifications 2009B - Part 5: Rates Version 1.2	YES/NO
HTNG Property/Distribution Specifications 2009A - Part 1: Reservations Version 2.1	YES/NO
HTNG Property/Distribution Specifications 2009A - Part 2: Availability Version 2.1	YES/NO
HTNG Property/Distribution Specifications 2009A - Part 4: Groups Version 1.0 Note: Release 2008A is identical and acceptable	YES/NO
HTNG Property/Distribution Specifications 2009A - Part 5: Rates Version 1.1	YES/NO
HTNG Property/Distribution Specifications 2008A - Part 1: Reservations Version 2.0	YES/NO
HTNG Property/Distribution Specifications 2008A - Part 2: Availability Version 2.0	YES/NO
HTNG Property/Distribution Specifications 2008A - Part 5: Rates Version 1.0 Note: Release 2007A is identical and acceptable	YES/NO
HTNG Property/Distribution Specifications 2007A - Part 1: Reservations Version 1.0	YES/NO
HTNG Property/Distribution Specifications 2007A - Part 2: Availability Version 1.0	YES/NO
Proprietary System(s)	YES/NO

Details of Proprietary Systems

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

System Name	Version Number	Summary of System Details	Contact Name	Date of Implementation

Supporting Documents

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.

<insert Web Service name>
Documentation Provided	Mandatory/ Optional	HTNG Specification Reference, URL, or Supporting Document Number (see table below)
WSDL	Mandatory
Schemas externally referenced in WSDL	Mandatory
SOAP Packet Trace	Mandatory
Published API Specification	Mandatory for HTNG defined Web Services
Write-up on WS Security Implementation	Optional
Write-up on WS Addressing Implementation	Optional

Communication Style

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

Communication Style
Synchronous	YES/NO
Asynchronous	YES/NO

Single Guest Itinerary Conformance (optional)

Roles

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

Role
Activity Reservation System	YES/NO
Accommodation Reservation System	YES/NO
Posting System	YES/NO
Folio System	YES/NO
Customer Profile System	YES/NO
Itinerary Consolidation System	YES/NO
Itinerary Display System	YES/NO

Activity Reservation System Role

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.

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
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
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
Notify when appointment time is outside of stay dates	OutOfScopeNotification	Mandatory	YES/NO
Notification of status change	GuestStatusNotification	Mandatory	YES/NO
Link new profile ID to another system	Subscription	Mandatory	YES/NO	YES/NO
Lookup matching reservations	ReservationLookup	Optional		YES/NO
Fetch specific reservation details	FetchReservation	Optional		YES/NO
Notify of guest location	LocationNotification	Optional		YES/NO
Send guest message	GuestMessage	Optional		YES/NO
Merge guest profile	MergeProfile	Mandatory	YES/NO	YES/NO

Accommodation Reservation System Role

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.

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

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.

Function/Message Description	Function/Message Name	Mandatory/ Optional	Can provide these web service functions	Can initiate these messages
Post charge	PostPayment	Mandatory		YES/NO
Retrieve details of a POS check	FetchCheckDetails	Optional	YES/NO

Folio System Role

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.

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

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.

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

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.

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

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.

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

Digital Signage Conformance (optional)

Roles

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

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

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.

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
Request Reserved Meeting Space	MeetingSpaceResponse	Mandatory		YES/NO
Request Meeting Space Characteristics	MeetingSpaceCharacteristicsRequest	Mandatory		YES/NO
Request Meeting Space Characteristics	MeetingSpaceCharacteristicsResponse	Mandatory		YES/NO

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

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

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.

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
Request Reserved Meeting Space	MeetingSpaceResponse	Mandatory	YES/NO
Request Meeting Space Characteristics	MeetingSpaceCharacteristicsRequest	Mandatory	YES/NO
Request Meeting Space Characteristics	MeetingSpaceCharacteristicsResponse	Mandatory	YES/NO

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

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

Open Data Exchange (optional)

Roles

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

Does the Product function as a Data Receiver?	YES/NO
Does the Product function as a Data Sender	YES/NO

Data Receiver

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.

Function/Message Description	Function/Message Name	Can provide these	Can initiate these
Push Files	PushFile	YES/NO
Pull Files	PullFile		YES/NO

Data Sender

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.

Function/Message Description	Function/Message Name	Can provide these	Can initiate these
Push Files	PushFile		YES/NO
Oull Files	PullFile	YES/NO

Back Office Integration (optional)

Service Implementers

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.

Please indicate whether your application includes balancing functionality.

Mandatory

YES/NO

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.

Please indicate whether your application will include transformation functionality.

Optional

YES/NO

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.

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

Optional

YES/NO

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.

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

Optional

YES/NO

Service Callers

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.

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

Mandatory

YES/NO

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

Please indicate whether your application includes statistical values.

Mandatory

YES/NO

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.

32a

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

Optional

YES/NO

32b

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

Optional

YES/NO

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.

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

Optional

YES/NO

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:

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

Guest Self Service (optional)

Roles

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

Role
Self Service Frontend	YES/NO
Services Scheduling System	YES/NO

Self Service Frontend

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.

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

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.

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

Food and Beverage Ordering (optional)

Roles

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

Role
Device (Kiosk, Touch Screen, In-Room TV, IP Phone, etc)	YES/NO
Food and Beverage POS System	YES/NO

Device Role

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.

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

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.

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

Guest and Room Status Messaging (optional)

Roles

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

Role
Room Stay Information Provider	YES/NO
Room Stay Information Consumer	YES/NO

Room Stay Information Provider

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.

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
Send Guest Check-Out Notification Message	HTNG_CheckOutNotification	Mandatory
Send Guest Room-Move Notification Message	HTNG_RoomMoveNotification	Mandatory
Send Stay Update Notification Message	HTNG_StayUpdateNotification	Mandatory

Room Stay Information Consumer

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.

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
Receive Guest Check-Out Notification Message	HTNG_CheckOutNotification	Mandatory
Receive Guest Room-Move Notification Message	HTNG_RoomMoveNotification	Mandatory
Receive Stay Update Notification Message	HTNG_StayUpdateNotification	Mandatory

Kiosk Integration (optional)

Roles

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

Role
Kiosk Application	YES/NO
PMS Application	YES/NO

Kiosk Application

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.

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

PMS Application

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.

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

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.

Supporting Document Table

The following table is provided for supporting documents identified in Q6 and Q8. 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 A6 or A8 above. Insert additional table entries as required.

	Document Title
1	For Q6 <insert web service name> - Interoperability Test Report or for Q8 <insert web service name> - <insert document title>
1	<insert document text>

Revision History

Issue 1.0 November 24, 2008, First Release
Issue 2.0 April 10, 2009, First Release (Updated Open Data Exchange, added Back Office)
Issue 3.0 September 24, 2009, First Release (added Guest and Room Status Messaging)
Issue 4.0 April 23, 2010, First Release (added Kiosk Integration)