How to implement and operate Robo Claw in production at major tourism and accommodation companies
Organizes the operational framework for deploying tasks verified in Pilot into production, including execution environment, authentication, least privilege, trust boundaries for headquarters, facilities, regions, and contractors, monitoring, and exceptional operations during disasters, bad weather, and service suspensions.
In production operations, in addition to the normal and abnormal behaviors confirmed in Pilot, it is a premise to establish a system for monitoring, alerts, and incident response that can continue during business hours. In particular, explicitly documenting in advance the stop conditions and exceptional operations during disasters, bad weather, and service suspensions, as well as the procedures for switching to manual operations during incidents, affects the initial response to prevent incorrect reservations, pricing information reflections, or erroneous customer communications. The design does not assume execution of reservation confirmation, price changes, customer communications, or refund processing without approval.
Who This Is For
Who This Is For
This is targeted at the Information Systems Department, Reservation Department Managers, and Risk Management Officers who will deploy operations that have been verified in the Pilot phase to the production environment.
What You'll Decide
What You'll Decide in This Step
In Deploy & Operate, the authentication, permissions, and monitoring system in the production environment are finalized, the conditions for stopping and recovery procedures in case of a failure are determined, as well as exception operations in the event of disasters, bad weather, or service suspensions, and the approach to operations that can continue across multiple facilities and regions is decided.
Industry Challenges
Challenges unique to large tourism and accommodation companies.
Continuous response during business hours
Since lodging facilities generally continue operations at all times, a monitoring and alert system that operates without interruption is required.
Failure response across multiple facilities and regions
If reservation management and PMS configurations differ by facility or region, it takes time to isolate the cause in case of a failure.
Following changes on the reservation management, PMS, and CRS side
When there are specification changes in reservation management or PMS, change management for the linked parts is required.
Immediate suspension in case of disasters, bad weather, or service disruptions
When disasters, bad weather, or transportation service suspensions occur, a system that can immediately stop related automated processes is required.
Method
Implementation Steps
1. Prepare the Execution Environment
Prepare the production environment (cloud, etc.) and confirm the differences from the Pilot environment.
2. Determine authentication and minimum privileges
Finalize the authentication method for production users and agents, and the minimum permissions by facility and region.
3. Design trust boundaries for headquarters, facilities, regions, and contractors
Design trust boundaries so that data and permissions do not cross between multiple facilities and contractors.
4. Establish Secret Management
Establish a system to safely manage and rotate sensitive information such as API keys and tokens for reservation management, PMS, and CRS.
5. Design controls for external transmission of personal, location, and itinerary information
Control the transmission routes to prevent customer information, location data, and itinerary information from being unintentionally sent externally.
6. Establish a logging and audit system
Organize the storage locations, retention periods, and reference methods for operation logs during audits.
7. Define monitoring, alerts, and stop conditions
Monitor the operation status of agents, execution failures, and signs of abnormal misdelivery, and define automatic stop conditions when anomalies are detected.
8. Define exceptional operations during disasters, bad weather, and service suspensions
Define the procedures for automatic process suspension, escalation routes to the operational safety manager, and switching to manual operations in case of disasters, bad weather, or service suspensions.
Data & Systems
Data and Systems Used
Human-in-the-loop
Where Human Approval Is Required
- Final approval for migration to the production environment
- Approval for issuing and rotating secrets and authentication information
- Approval for Skill / Tool updates due to specification changes in reservation management, PMS, or CRS
- Approval for execution of recovery/resumption procedures in case of disasters, bad weather, or service suspensions
Measurement
KPI
Operating rate
Operating rate of Agents/Skills in production
Time from failure detection to recovery
Time taken from detecting an anomaly to recovery
Alert response time
Time from alert issuance to first response
Pitfalls
Common Pitfalls
Leaving it entirely to monitoring after introduction
If you operate without deciding the monitoring system after going live, detection of failures will be delayed.
No procedures prepared for stopping operations in case of disasters or bad weather
If there are no procedures to immediately stop related processes when an incident occurs, the risk of impact expansion increases.
Attempting to automate booking confirmations, price changes, and customer notifications without approval
Designing to automatically reflect operations with a large impact without approval increases the risk of incorrect updates or incorrect transmissions.
Checklist
Production Operation Checklist
- Authentication and least privileges in the production environment are confirmed
- Trust boundaries for headquarters, facilities, regions, and contractors are designed
- Procedures for secret management and rotation are established
- Controls for external transmission of personal, location, and itinerary information are designed
- The storage destinations and retention periods for operation logs are determined.
- The monitoring and alert targets and notification destinations are set.
- Conditions for stopping in abnormal situations and recovery procedures are documented.
- Procedures for exception operations and switching to manual operations during disasters, bad weather, or service suspensions are established
FAQ
Frequently Asked Questions
Who is responsible for monitoring during production operation?
It is common for the Information Systems Department to take the lead, and for responses to be coordinated with the Reservations or Risk Management Departments depending on the business content. Specific role assignments are designed individually.
Can reservation confirmations and customer notifications be automatically executed without approval?
No. Operations that have a large impact, such as confirming, changing, or cancelling reservations, changing rates, sending communications to customers, and processing refunds, are basically designed based on human approval.
What happens in the event of a disaster or bad weather?
It is recommended to immediately stop related automated processes and establish a route for escalation to the safety officer responsible for operations. The specifics of the procedure are designed individually.
Shall we organize the production configuration and operation together?
The production operation configuration, including authentication, reservation management, PMS/CRS connections, monitoring, incident response, and multi-facility operations, can be concretely established through consultations in the official LP.