Integrations

Property Management Systems

Oracle Opera

Why
  • Integrating with Oracle Opera provides System Manager with critical information used in conditioning the room state, such as temperature setpoint, curtain position, power status etc.

  • Check-in messages move the room state to condition ready for new guests to arrive.

  • Check-out messages reset the room, removing customizations from previous guests such as DND or temperature setpoints, ready for cleaning and the next guest.

  • We send Privacy/DND and Make Up Room guest status requests to Opera to make them easily visible to operators assisting guests.

How
  • System Manager and Opera integrate over TCP/IP using the FIAS protocol encrypted with TLS 1.2; the firewall needs to allow this.

  • From Oracle, you need to order our interface for them to support integration.

  • From System Manager, the interface is included and can be simply configured when ready.

multiroom oracle to interact
Requirements Checklist
  • Firewall access opened

    • Real-time server <> Opera Server

    • Port to be assigned by Oracle

    • System Manager acts as a client of Opera

    • Certificate can be installed to provide a secure connection

  • Order the Interface

    • FIAS connectivity is included as standard with Multiroom System Manager, but you need to purchase an interface on the Opera side.

    • Contact your Oracle representative to order our interface, quoting product ID (FKT): IFC_PDH / FIAS_PDH

  • Versions

    • The integration is tested to be compatible with Oracle Opera v5 or later.

Certification

Architecture STR, powered by Philips Dynalite, is a 'Validated Integration' as certified by Oracle. You can verify our status on their website: https://www.oracle.com/us/partnerships/isv/ds-philips-dynalite-4414287.pdf

Infor HMS

Why
  • Integrating with Infor HMS provides System Manager with critical information used in conditioning the room state, such as temperature setpoint, curtain position, power status, etc.

  • Check-in messages move the room state to condition ready for new guests to arrive.

  • Check-out messages reset the room, removing customizations from previous guests such as DND or a temperature setpoint, ready for cleaning and the next guest.

  • We send Privacy/DND and Make Up Room guest status requests to Infor to make them easily visible to operators assisting guests.

How
  • System Manager and Infor integrate over TCP/IP using the FIAS protocol; the firewall needs to allow this.

  • You need to order our interface from Infor for them to support integration.

  • From System Manager, the interface is included and can be simply configured when ready.

multiroom infor to interact
Requirements Checklist
  • Firewall access opened

    • System Manager Server <> Infor Server

    • Port to be assigned by Infor

    • System Manager acts as a client of Infor

  • Order the Interface

    • FIAS connectivity is included as standard with System Manager, but you need to purchase an interface on the Infor side.

    • Contact your Infor representative to order our interface, quoting their SKU: HMS-EAI-L066DT-EMS.

Certification

Architecture STR, powered by Philips Dynalite, is a 'Certified Integration' as certified by Infor.

Access Control

dormakaba – Saflok

Why
  • By connecting to the Access Control server, the system can be made aware of occupancy type based on the key type used to enter the room.

  • This means that, as well as real-time occupancy, we know if it’s a guest or staff member in the room.

  • By knowing this we can condition the room differently for staff, such as brighter lighting to help inspection, as well as disregarding any changes they make from guest preferences such as temperature setpoint.

  • We can also save energy by using a shorter timeout after staff occupancy compared to guest occupancy.

How
  • System Manager subscribes to the APIs shared on dormakaba’s Saflok Messenger LENS server.

  • Upon room entry, they send us an event that includes the guest/staff key type.

multiroom saflok to interact
Requirements Checklist
  • Firewall access opened

    • System Manager Server <> dormakaba Messenger LENS Server

    • Port to be assigned by dormakaba

    • System Manager acts as a client of dormakaba

  • Credentials

    • You will need to authorize dormakaba to issue credentials for us to authenticate when connecting to their server.

Certification

Architecture STR has been tested and certified by dormakaba as an approved integration. You can contact them to verify our status via: https://www.dormakaba.com

ASSA ABLOY (VingCard)

Why
  • By connecting System Manager to the Access Control server, the Interact system can be aware of occupancy type based on the key type used to enter the room.

  • This means that, as well as real-time occupancy, we know if it’s a guest or a staff member in the room.

  • By knowing this we can condition the room differently for staff, such as brighter lighting to help inspection, as well as disregarding any changes they make from guest preferences such as temperature setpoint.

  • We can also save energy by using shorter timeouts after staff occupancy compared to guest occupancy.

How
  • System Manager subscribes to the APIs shared on the ASSA ABLOY VingCard server.

  • Upon room entry, VingCard sends us an event that includes the guest/staff key type.

multiroom vingcard to interact
Requirements Checklist
  • Firewall access opened

    • Real-time server <> VingCard Server

    • Port to be assigned by ASSA ABLOY (do not use 443)

    • System Manager acts as a client of ASSA ABLOY

  • Credentials

    • You will need to authorize ASSA ABLOY to issue credentials for us to authenticate when connecting to their server.

Certification

Architecture STR has been tested and certified by ASSA ABLOY as an approved VingCard integration.

API Connections

Housekeeping, Job Dispatch, and Guest Apps

Why
  • Interact can share guest requests such as Laundry Pickup with third-party systems to aid them in delivering guest services. These can be automatically deployed in their system to a runner near to the room for fast response times, automatically clearing the room status when the job is marked as complete.

  • Interact can share statuses such as real-time occupancy, Privacy/DND and Make Up Room requests. These are used in third-party systems to dynamically reprioritize housekeeper task allocations, optimizing efficiency by going first to rushed or vacant rooms.

  • In addition, some third-party systems accept room alerts to help dispatch runners that can support verifying occurrences of extended Privacy/DND status (e.g. over 48 hours) to ensure guest safety.

  • Third-party developers can create guest apps, enabling guests to control services in their room from a phone or tablet.

How
  • Third-party systems often have custom interfaces and business logic based on the Hotel Integration API.

  • These can be activated by the third-party system once firewall rules are enabled to allow communication.

  • Refer to the Interact Developer Portal for more information.

multiroom housekeeping to interact
Requirements Checklist
  • Firewall access opened

    • Real-time server <> Third-party server

    • Port 3260

    • Third-party server acts as a client of System Manager

  • Credentials

    • We will issue API credentials to third-party integrator for onsite integration.

Certification

Interact has tested and certified a number of API-based third-party integrators as 'Works with Architecture STR'.