Skip to content

Services

idataraya plans the rollout, installs the system in the operator's own environment, moves the property across in the shoulder season, and maintains it under one yearly agreement.

An engineer going through a document with a colleague at a desk

Rollout plan and proposal

Send the properties, the number of rooms and the booking channels and systems in use. An engineer replies with a rollout plan, an integration plan and a proposal. asasii stay runs at one front desk first, before a group commits every property to it, so what no specification captured comes out during real service rather than in a workshop.

Moving across in the shoulder season

asasii stay is installed in the operator's own cloud account or data centre, and the cutover is planned against the operator's calendar, not idataraya's. The previous system stays available until the new one is trusted, and staff are trained against the real counter. Nobody replaces a property management system the week before a long weekend.

Support and maintenance

One team looks after the system for the life of the agreement, staffed when the property is full.

  • Severity-based response times, measured monthly
  • Continuous monitoring from within the operator's environment
  • A drilled backup and restore
  • Releases, patches and incident response
  • Changes as the operator opens outlets and adds properties

The yearly agreement

Software updates, the customisations made for you, monitoring, severity-based response and restoration targets, and the changes needed as the operator opens outlets and adds properties. Hosting stays with you. It is a fee, not a subscription.

Security and Malaysian compliance

The questions owners, group finance and audit ask, answered in the system.

Security and data overview
PDPA 2010
Guest data stays in the operator's own environment.
Roles
Each role is scoped by property and function.
Single sign-on and MFA
On every console, with the operator's own identity provider.
Audit trail
Every action recorded with the previous value and kept for seven years.
The operator's records
Bookings, folios and guest records are held in the operator's own environment.
Card data
Card payments go through the operator's own acquirer, and card data stays with it.

See it at your own front desk

Send us the properties, the number of rooms and the booking channels and systems in use. An engineer replies with a rollout plan, an integration plan and a proposal.