OPERATIONAL TEAM GUIDE IN SLA RESPONSE TIMES Hotel, Spa & Restaurant Operations
Protect the guest experience. Restore operation quickly. Communicate with discipline.
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
How to use this guide Working presentation to classify, respond to, communicate and close incidents consistently.
1 · CLASSIFY
2 · RESPOND
3 · COORDINATE
4 · VALIDATE
Assess impact, urgency, security, privacy, revenue, guests and workaround quality.
Meet acknowledgement, intervention, restoration and update targets according to P1-P4.
Define a single owner, escalate on time and activate the vendor or incident management.
Do not close until the business confirms the full transaction and reconciliation.
2
LOCANDA | GUÍA OPERATIVA SLA
01 OPERATING FRAMEWORK Purpose, scope, principles, definitions and SLA clock rules.
3
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Scope and objectives SCOPE
OBJECTIVES
Employees, contractors, managed vendors and manufacturers. Includes OPERA Cloud PMS and interfaces, Simphony POS, Book4Time, payments, network, Wi-Fi, telephony, identity, endpoints, servers, cloud, door locks, room technology, CCTV dependencies, digital services and integrations.
• Restore service while protecting life, guests, revenue, data and compliance. • Classify using consistent, auditable criteria. • Define measurable, backed expectations. • Authorize containment, failover, workaround and escalation. • Generate evidence for improvement, audit, insurance and reporting.
4
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Six non-negotiable principles Guests and safety first
Restore before addressing the root cause
Safety, room access, payment integrity, privacy, VIPs or events can raise priority, even if they affect few users.
Incident management restores service; problem management determines and eliminates the underlying cause.
The assigned group coordinates until the receiver formally accepts the handover.
No silent breaches
Close with evidence
Continuous improvement
SLA risk, impact changes, vendor delays and lack of ETA are communicated before expiry.
Validation, timestamps and resolution notes are required.
P1s and repeated events generate corrective actions with an owner and due date.
One ticket, one owner
5
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Glossary and SLA clock rules Term
Operational definition
Acknowledgement
Ticket logged, classified and assigned an owner; P1/P2 require human contact.
Intervention
Qualified resolver starts diagnosis or containment.
Restoration
Acceptable service, even with a controlled workaround.
Final resolution
Permanent fix verified; workaround removed or accepted.
Incident / Request / Problem
Interruption / predefined request / potential or actual cause.
Major incident
P1 or P2 designated with coordinated command and executive visibility.
Business hours / Calendar
08:00-20:00 daily for operations; calendar includes nights, weekends and holidays.
SLA pause
Only documented requester wait, approved window or formal exclusion; P1 is not paused for vendors.
The clock starts when the ticket enters the ticket portal. A call, chat or email must be converted into a ticket immediately. It is not paused for internal waits or vendors. Restoration ends once the service is stabilized and validated. 6
LOCANDA | GUÍA OPERATIVA SLA
02 PRIORITY AND TIMING How to decide P1-P4 and which operational commitment applies.
7
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Impact and urgency matrix Impact / Urgency
High
Medium
Low
Entire property
P1
P2
P2
Department, floor, outlet, event or multiple guests
P2; P1 with no workaround or serious risk
P2
P3
User, room or device
P2 if VIP, security, payment or imminent impact
P3
P4
Do not classify by system name. Classify by real consequence and workaround quality.
8
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Incident levels P1 · CRITICAL Total outage or severe degradation; no safe workaround; cyberattack, cards, safety, regulation or brand. Incident Manager, bridge, Management/Operations, every 30 min, continuous work.
P2 · HIGH Critical service degraded, important area, limited workaround, many guests or revenue/event at risk. Resolver + vendor, every 2 h, escalation at 70%.
P3 · MEDIUM Limited scope and reasonable workaround; no material risk. Business hours, daily update, review recurrence.
P4 · LOW / REQUEST No immediate impact: access, equipment, information, standard change or improvement. Catalog, planned date and change approval.
9
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Service level objectives Pri.
Acknowledge
Interv.
Restore / workaround
Final resolution
Update
Coverage
P1
15 min
30 min
4 calendar h
1 business day or approved Problem
Every 30 min
24/7/365
P2
30 min
1h
8 operating h
2 business days
Every 2 h
08:00-20:00 daily; on-call if critical
P3
2 bus. h
4 bus. h
2 business days
5 business days
Daily
Business hours
P4
4 bus. h
1 bus. day
Planned date / 5 days
Per change/fulfillment
By milestones
Business hours
10
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Quick reference by area Area
P1 / P2
P3 / P4
Front Office
PMS, mass key failures, payments/posting, blocked arrivals
Workstation, printer, routine correction, training
F&B / Simphony
Multiple outlets, widespread kitchen printing, revenue interface
Single terminal/printer with workaround, menu/report
Rooms
Door locks, widespread Wi-Fi/TV/controls, safety
Single-room device or Wi-Fi
Spa / Book4Time
Bookings/check-in/payment down; multiple devices
Individual iPad/printer; access
Network / Identity
Property outage, firewall/switch/identity, active compromise
Port/device; group change
Cyber / Privacy / PCI
Ransomware, exfiltration, credentials, cards
Contained phishing may trigger security
Events / VIP
Failure threatens imminent event or VIP service
Planned AV setup, account or rehearsal
11
LOCANDA | GUÍA OPERATIVA SLA
03 LIFECYCLE AND ESCALATION Mandatory logging, major incident, contacts, validation and closure.
12
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Ticket lifecycle 1
2
3
4
5
6
7
Detect
Triage
Acknowledge
Diagnose
Restore
Close
Learn
Time, reporter, location, service, symptoms, affected users and flags.
Incident/request; impact, urgency, priority; security or major.
Owner, priority, next update and workaround.
Tests, evidence, changes, isolation, vendor and risk.
Validate with monitoring and the business; report limits and observation.
Cause, solution, change, confirmation, code and evidence.
Problem, review and action follow-up.
13
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Mandatory ticket fields 01
02
Number, date/time, channel, requester and contact.
Property, building, floor/room/outlet and department.
03
04
Service, CI, vendor and contract.
Impact, urgency, priority and justification; VIP/event.
05
06
Privacy, cybersecurity, PCI, physical security, legal and regulation.
History, timestamps, evidence, communications, vendor case and changes.
07 Workaround, restoration, solution, closure and validation.
14
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Major incident: mandatory timeline Time
Required action
0-15 min
Declare P1; Incident Manager and technical lead; bridge; evidence; log.
15-30 min
Notify IT Director, Operations, owner and vendor; first communication.
30-60 min
Recovery strategy, fallback, guest, communication; activate Security/Privacy/PCI/PR/Legal.
Every 30 min
Status, impact, actions, plan, risks, ETA confidence and decisions.
On restoration
Validate stability; communicate; observe 30-60 min or defined period.
2 business days
Preliminary review and timeline.
5 business days
PIR, Problem/RCA, actions, owners and dates.
15
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Escalation matrix Trigger
Functional
Business / management
External
P1 on creation
Service Desk → Infra/Systems/Cyber/Support
Assistant Director / IT Director; Operations; manager
Critical vendor; Security/PR/Legal/DPO/PCI
P1 with no plan at 60 min
Senior engineer; alternative; DR/BCP
Managing Director; possible CMT
Vendor executive; insurance/forensics/acquirer/authority
P2 at 70%
Technical lead + vendor; revalidate
Assistant Director + affected manager
Vendor Service Manager
P3 with no update in 1 day
Group lead
Requester's manager if material
Vendor
P4 past due date
Catalog owner
Manager at weekly review
Account Manager
Security/cyber/card/data/regulati on
Immediate specialist process
IT Director + relevant executive
Legal/DPO/Security/acquirer/regulator
16
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Contact directory and notification Purpose
Primary contact
Use
Phones
Help Desk / Helpdesk
Helpdesl.lpe@cipriani.com
All incidents and requests
+598 99 560 324
IT Operations
abrito@cipriani.com
IT team coordination and awareness
+598 99 819 007
IT Director
jgiraldo@cipriani.com
P1, major P2, executive vendor, cyber/privacy/PCI
+598 98 011 925
Executive Committee
excom.pde@cipriani.com
Approved executive updates
N/A
Validate on-call memberships, aliases and phone numbers quarterly, and whenever staff change.
17
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Operational criticality and protected windows Service
Window / trigger
Response rule
Mandatory fallback
Front Office / OPERA / keys
Arrivals, departures, night audit; blocked check-in/out, billing or access
Property without workaround: P1; controlled manual: P2
Contingency kit, manual folio/registration, key control; Finance reconciles
Restaurants / Simphony / kitchen
30 min before opening to close; events
Multiple points or kitchen stopped: P1/P2; one device with fallback: P3
Manual orders, kitchen, checks, exceptions, avoid duplicates
Spa / Book4Time
Opening to last treatment; groups/VIP
Booking/check-in/payment blocked with guests: P2; one device with alternate: P3
Current extract, numbered forms, board and charge queue
Payments
All service hours
Multiple terminals or uncertain status: P1/P2; isolated: P3
Do not retry; record reference/amount/time/terminal; reconcile
Wi-Fi / telephony
24/7; emergency, VIP or event
Property: P1; area/floors: P2; room: P3
Guest Relations communicates; separate guest and operations/payments networks
18
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Business validation and closure
• P1/P2 require express confirmation from the duty manager of Front Office, F&B, Spa or Operations. • Evidence must include an end-to-end transaction: check-in/posting, order to kitchen, authorization and settlement, or spa booking/check-in/charge. • With queues, unreconciled manual records or unstable monitoring, keep status Monitoring or Restored. • Open a linked Problem on recurrence, unknown cause, workaround dependency or any P1. Do not close when “the screen comes back”. Close when the full operation is validated and reconciled.
19
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Triage questions before restarting or escalating Area
Initial questions
Hotel / Front Office
Arrivals, departures, access, folios or night audit blocked? Device, interface or service? Last successful transaction?
Restaurants
Login, order, kitchen, receipt, network, Internet or payment? Which outlets/revenue centers? Will resending duplicate?
Spa
Schedule, therapists/rooms, profiles and payment/charge visible? Workstation or approved printed schedule?
Payments
Declined, approved, pending or unknown? Capture reference and do not charge again.
Interfaces
Source works but postings are queued? Record age, quantity, last transfer and reconciliation owner.
20
LOCANDA | GUÍA OPERATIVA SLA
04 PRACTICAL CASES Priority is assigned with the initial information and reassessed when the risk changes.
21
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
E.1 · OPERA Cloud unavailable 15:30, 24 group rooms; no workstation responds and keys have no assignments; last report 14:00.
INITIAL PRIORITY
WHY
RESTORE / CLOSE
P1 with no safe workaround; P2 with controlled manual process. 15/30 min/4 calendar h; update every 30 min.
Blocks reservations, rooms, folios and arrivals; risk of double assignment and missed charges.
OPERA stable, lookup, check-in and key working; inventory and forms controlled. Closure: Arrivals, changes, payments and postings reconciled; Front Office confirms; timeline and evidence.
Expected operating sequence
• Record arrivals, devices, last transaction and Internet. • Service Desk isolates the cause and assigns an owner; bridge if P1. • Front Office activates contingency; Housekeeping confirms rooms via an alternate channel. • IT opens an Oracle case and tests check-in, key and posting end-to-end.
AVOID: Closing when the screen opens without validating inventory, keys, folios and manual records. 22
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
E.2 · Simphony and kitchen printing down 21:00, orders accepted but not printing in the kitchen of two outlets; resends begin.
INITIAL PRIORITY
WHY
RESTORE / CLOSE
P1 if multiple outlets with no alternative; P2 with manual flow. P1 15/30 min/4 h; P2 30 min/1 h/8 h.
Revenue, guest, kitchen and risk of losses or duplicates.
Order, modifier and cancellation arrive without duplication. Closure: Manager and Finance confirm no pending manual tickets, checks, charges or duplicates.
Expected operating sequence
• Stop resends and establish a single point of control. • Identify the failed function and last confirmed order. • Numbered manual tickets with allergies; kitchen acknowledges receipt. • IT checks printers, queues, network, addressing and logs; reconcile voids, discounts and payments.
AVOID: Repeated reprint/resend without checking queues. 23
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
E.3 · Book4Time unavailable 10:00, two reception PCs without access; VIP couple, six treatments, profiles and payment not visible.
INITIAL PRIORITY
WHY
RESTORE / CLOSE
P2; P1 if it expands with no fallback. 30 min/1 h/8 h; update at least every 2 h.
Affects check-in, schedule, resources, forms, payments and room charges.
Schedule, resources, profiles, booking/check-in and payment/charge validated. Closure: Spa reconciles schedule, resources, payments, memberships and charges with no duplicates.
Expected operating sequence
• Record time, devices, network, users and last appointment. • Activate extract and numbered manual board. • Separate health, preference and payment data. • IT rules out device/browser/identity/Internet and opens a vendor case; reconcile changes.
AVOID: Recreating bookings without comparing the restored schedule. 24
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
E.4 · Payment with unknown outcome Terminal stays on processing and loses connection; PMS/POS not responding, guest receives a bank notification.
INITIAL PRIORITY
WHY
RESTORE / CLOSE
P3 isolated with alternative; P2 multiple/blocking; P1 widespread unavailability or compromised cards.
A timeout is not a decline; retrying may duplicate the authorization or charge.
Status known and terminal processes an approved test. Closure: Finance validates authorization, capture, posting, settlement and folio/account.
Expected operating sequence
• Do not retry; record terminal, time, amount, reference and message. • Check history/gateway/processor. • Apply only the approved alternative; do not record the full card number. • Determine terminal/network/gateway/integration; reconcile before closing.
AVOID: Charging again without checking the processor or history. 25
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
E.5 · Keys rejected on one floor Eight third-floor rooms reject keys; other floors work; five guests arrive in 20 min.
INITIAL PRIORITY
WHY
RESTORE / CLOSE
P2; P1 if widespread, with no safe access or with compromise. 30 min/1 h/8 h.
Prevents access, creates a queue and a security risk.
Key issuing and reading stable; assisted access available until validated. Closure: Front Office and Security confirm; door openings logged and temporary keys cancelled.
Expected operating sequence
• Record rooms, encoder, key and users; inform Security. • Do not hand out master keys or improvise access. • Check encoder, integration, permissions, synchronization, controllers and power. • Assisted access with logging; test a sufficient sample of the floor.
AVOID: Access based on visual recognition without identity and logging. 26
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
E.6 · Wi-Fi down in one room Room 214 has no connection; hallway works; alternative in common areas.
INITIAL PRIORITY
WHY
RESTORE / CLOSE
P3; P2 for VIP, event, multiple rooms or no alternative. 2 h/4 h/2 days.
Initial scope is limited, but it requires a disciplined response and communication.
Stable connection, authentication and satisfactory browsing. Closure: Guest or Guest Relations confirms; cause and follow-up documented.
Expected operating sequence
• Record room, devices, SSID, time and error. • Check portal/credential, device, coverage, AP, DHCP/DNS or port. • Guest Relations offers an alternative without promising an ETA. • If more rooms appear, reassess immediately.
AVOID: Keeping P3 when the impact widens. 27
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
E.7 · Single kitchen printer Dessert printer is not printing; the rest work; tickets can be rerouted to expo.
INITIAL PRIORITY
WHY
RESTORE / CLOSE
P3 with rerouting; P2 if it is the only route in service. P3 2 h/4 h/2 days.
The same failure changes priority depending on the actual flow and fallback.
New order and change print; rerouting is removed in a controlled way. Closure: No pending jobs or duplicates; kitchen and outlet confirm.
Expected operating sequence
• Confirm paper, cover, power, cable/network, IP, queue and self-test. • Manager authorizes rerouting and the person responsible for delivery. • Mark reprints as copies and notify the kitchen. • Test order, change and cancellation; review remakes and shortages.
AVOID: Clearing the queue without reviewing pending jobs. 28
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
E.8 · User setup or planned installation Spa requests a Book4Time user for next week and a standard installation.
INITIAL PRIORITY
WHY
RESTORE / CLOSE
P4. Acknowledge 4 business h; intervention 1 day; planned date or up to 5 days.
No immediate interruption; requires approval and catalog.
Account and equipment available and tested on the agreed date. Closure: Approval, assignment, delivery and acceptance documented.
Expected operating sequence
• Record date, approver, role, location, system and equipment. • Validate license, segregation, least privilege and prerequisites. • Communicate date and dependencies. • Test login, instruct and keep evidence.
AVOID: Inflating to P1/P2 just to speed things up. 29
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
E.9 · Phishing with credentials submitted Employee opens a link, enters a password and reports a fake page.
INITIAL PRIORITY
WHY
RESTORE / CLOSE
Immediate security process; P2/P3 depending on evidence; P1 if widespread active compromise.
May be raised even if it affects one person; depends on data, execution and propagation.
Sessions revoked, account and device secured, indicators blocked. Closure: Cyber validates; evidence and privacy decisions documented.
Expected operating sequence
• Record user, time, device, link and actions without mass forwarding. • Revoke sessions, change credentials, review MFA, email and activity. • Involve Legal/DPO if data is involved; preserve logs. • Assess rules, downloads, apps, data and lateral movement.
AVOID: Closing as a simple password change. 30
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
E.10 · VIP or event raises urgency Slow workstation; a VIP group arrives in 30 min and it is the only one configured for the special flow.
INITIAL PRIORITY
WHY
RESTORE / CLOSE
P2 when it threatens an event or VIP service; not automatically P1.
Brand, revenue and time window justify a proportional, documented escalation.
Workstation stable or manual process tested before arrival. Closure: Event completed; failure resolved or under follow-up; changes auditable.
Expected operating sequence
• Document event, schedule, guests, dependency and alternative. • Restore or move the flow; prepare manual logging. • Set a decision time to activate the fallback. • Reclassify when the risk changes and keep the history.
AVOID: Assigning P1 solely because of the guest's identity. 31
LOCANDA | GUÍA OPERATIVA SLA
CONFIDENCIAL · USO INTERNO
Short classification exercises Situation
Class
Reason
Back-office printer; another is available
P3
Limited with a workaround
Financial report for upcoming close
P4
Planned work
Room telephony down across the property
P1
Scope and emergency
Book4Time slow on one PC; another works
P3
Immediate alternative
Book4Time slow on both; 10 treatments
P2
Protected window and revenue
POS at one outlet; another terminal and kitchen available
P3
Proven fallback
All POS at two outlets and payments down
P1
Multiple areas with no alternative
Restaurant → PMS backlog
P2
Risk of missed charges
32
LOCANDA | GUÍA OPERATIVA SLA
LEARNING RULE
Classify by real impact. Restore with control. Close with evidence.
• Priority can go up or down, but each change must explain the new fact. • A controlled workaround can stop the restoration clock, not the permanent cause. • Do not close when the screen comes back; close after a full transaction and reconciliation. • Data, cards, credentials or an attack immediately trigger the specialist process.
33
GUESTS FIRST. ALWAYS.
One ticket · One owner · Disciplined communication · A closure with evidence