Opens in a new tab
NEXUSHOTELCONNECT24

NEXUS / SERVICE LEVELS & AVAILABILITY

Reliable operations.
Clear expectations.
Accountable service.

Hotel technology supports daily reservations, room availability, channel coordination and business operations.

Clear service expectations help hotels understand how incidents, maintenance and support enquiries should be managed.

Explore the NEXUS approach to service availability and operational readiness.

Service commitments must be verified. This page does not establish a guaranteed uptime percentage, fixed response time, 24/7 support availability or contractual service credit. Any binding service levels must be expressly agreed in the applicable terms.

Service expectations Defined by applicable agreements
Incident management Impact-based prioritisation
Availability reporting Requires verified monitoring data
Maintenance Planned and documented procedures

CLEAR SERVICE EXPECTATIONS

An SLA must describe what is actually supported.

A Service Level Agreement defines applicable service commitments, measurements and responsibilities.

A useful agreement should be specific about the services covered, how service availability is measured and which commitments apply.

It should also distinguish service incidents, scheduled maintenance and issues caused by separate third-party systems.

The actual support model and contractual commitments must be confirmed before publication as guaranteed service levels.

01

Define the covered service

Identify which production applications, features and interfaces are included in the agreement.

02

Measure availability consistently

Document the monitoring method, reporting period, service boundaries and applicable exclusions.

03

Classify incidents fairly

Prioritise issues using their actual operational impact, affected scope and available workarounds.

04

Explain support arrangements

Clarify support channels, relevant service hours, communication procedures and escalation responsibilities.

05

Support operational recovery

Define how incidents are investigated, resolved where possible and verified before closure.

SLA DESIGN FRAMEWORK

Six foundations of accountable service.

These subjects should be addressed when developing a formal NEXUS Service Level Agreement.

Their inclusion here does not establish a binding service commitment.

01 / COVERAGE

Service Scope

Clearly identify the applications, connections and production services covered by specific commitments.

SCOPE REQUIRES CONFIRMATION
02 / MEASUREMENT

Availability Definition

Define the measurement interval, data sources, calculation method and treatment of maintenance periods.

METRIC REQUIRES VALIDATION
03 / INCIDENTS

Severity Classification

Describe how operational disruption affects incident priority and when further escalation is appropriate.

PRIORITY MODEL TO VERIFY
04 / COMMUNICATION

Support & Updates

Establish appropriate support channels, acknowledgement procedures and customer communication rules.

SUPPORT HOURS TO CONFIRM
05 / MAINTENANCE

Planned Changes

Explain how planned updates, emergency interventions and customer impact are assessed.

MAINTENANCE RULES TO DOCUMENT
06 / ACCOUNTABILITY

Reporting & Remedies

Identify relevant reporting obligations and any remedies expressly established by the agreement.

NO SERVICE CREDITS PROMISED HERE

INTERACTIVE INCIDENT PRIORITY EXPLORER

Understand the impact.
Determine the priority.

A technical incident is not defined by a single error message.

Select an affected service, the operational impact, the number of affected properties and whether a workaround exists.

The demonstration suggests a fictional incident priority and shows relevant response considerations.

NEXUS / Incident Priority Explorer Illustrative classification · No real incidents created
BROWSER SIMULATION
NOT A LIVE TICKET

Configure the scenario

Choose the example conditions for a fictional service incident.

This is a proposed decision-support model. Actual incidents require qualified human assessment, and relevant security events may require a separate response procedure.

Suggested Classification

Review the example priority and response path.

ILLUSTRATIVE PRIORITY READY TO EVALUATE

Select a fictional incident scenario and evaluate its priority.

Affected service Channel Manager
Classification status Simulated / Not Contractual
01 / RECEIVE Capture the issue

Record the affected service and symptoms.

02 / ASSESS Validate the impact

Check the reported operational scope.

03 / RESPOND Coordinate action

Apply the appropriate response procedure.

04 / VERIFY Confirm the outcome

Verify service restoration or the remaining issue.

Priority Illustrative meaning Suggested response approach
P1 / CRITICAL Severe production disruption across multiple properties, with no available workaround, or a particularly serious suspected security incident. Immediate escalation through the applicable incident-response procedure, subject to the actual operating arrangements.
P2 / HIGH Significant disruption affecting important production functionality. Prioritised investigation, coordination and customer communication under the applicable process.
P3 / MEDIUM Limited operational issue or significant degradation with a usable workaround. Structured troubleshooting and appropriate corrective action.
P4 / LOW Cosmetic issue, low-impact defect or routine demonstration environment concern. Planned review and correction according to the applicable service process.
Important: P1–P4 are illustrative classifications only. They do not establish contractual response times, resolution deadlines, support availability or automatic escalation to a real operations team. Actual incidents must be classified according to the applicable NEXUS support arrangement.
OPERATIONAL RELIABILITY

A priority describes urgency.
It does not guarantee a resolution.

Clear classification helps teams coordinate investigation and communication. Actual commitments must be supported by operational capability and contractual terms.

INTERACTIVE AVAILABILITY CALCULATOR

Understand the numbers behind availability.

Availability percentages are useful only when the measurement method is clearly defined.

A percentage alone does not explain which services were measured, how monitoring works or which periods are included.

This calculator shows a simple mathematical relationship between total calendar minutes and downtime.

It does not use actual NEXUS operational data.

Any formal SLA requires its own agreed measurement and exclusion rules.

NEXUS / Availability Calculator

Enter hypothetical downtime to calculate gross calendar availability.

HYPOTHETICAL GROSS AVAILABILITY 99.8958%

This result is based on a fictional 30-day period and 45 minutes of downtime.

Total period 43,200 min
Hypothetical downtime 45 min
Formula: Availability = (Total Minutes − Downtime Minutes) ÷ Total Minutes × 100.

This is a simplified gross-calendar calculation. It does not apply any contractual maintenance exclusions, monitoring thresholds or service-specific definitions. It is not a NEXUS uptime measurement or availability guarantee.

MAINTENANCE & SERVICE CONTINUITY

Maintenance should be planned around operational impact.

Software updates, infrastructure changes and security maintenance may affect hotel technology.

Clear processes help distinguish planned changes, emergency interventions and third-party service disruptions.

01 / PLANNED MAINTENANCE

Scheduled Changes

Appropriate maintenance procedures should define change scope, operational risk, testing and relevant communication.

The treatment of scheduled maintenance under an SLA must be expressly defined.

NOTICE TERMS TO VERIFY
02 / EMERGENCY ACTION

Urgent Interventions

Some security or operational problems may justify urgent corrective action.

The applicable procedure should address authorisation, impact assessment and relevant notifications.

ESCALATION PROCEDURE TO VERIFY
03 / DEPENDENCIES

Connected Services

External APIs, distribution partners and other providers may affect some hotel workflows.

The parties' respective obligations and any SLA exclusions must follow the actual agreements.

SUPPLIER RESPONSIBILITIES TO DEFINE

UNDERSTANDING SERVICE BOUNDARIES

Different disruptions require different responsibilities.

Not every technical problem has the same origin.

Appropriate service agreements should explain how responsibility is assessed when several independent systems participate in a hotel workflow.

01 / NEXUS SERVICES

Platform Operations

Problems involving NEXUS-operated applications or infrastructure should be assessed against the actual service scope and agreed obligations.

02 / EXTERNAL SERVICES

Independent Providers

An external distribution channel, payment service or other provider may have separate operational responsibilities and contractual commitments.

03 / HOTEL ENVIRONMENT

Local Connectivity

Hotel internet access, local hardware, individual devices and other hotel-controlled systems may influence the user's experience.

Important: These categories identify relevant operational boundaries. They do not automatically exclude any incident from contractual coverage. The applicable agreement must determine the actual scope, responsibilities and any lawful exclusions.

INCIDENT COMMUNICATION & SUPPORT

Every support process should have a clear path.

The following workflow illustrates how NEXUS service requests should be managed.

It is a proposed service-management model, not a promise of fixed acknowledgement or resolution times.

01 / REPORT

Submit the Issue

Identify the affected hotel, service, symptoms and relevant supporting information.

02 / VERIFY

Assess the Impact

Determine the affected scope, operational urgency and relevant technical context.

03 / ASSIGN

Route Appropriately

Direct the issue to the appropriate responsible team or external provider.

04 / RESPOND

Investigate & Communicate

Coordinate appropriate investigation, corrective action and relevant updates.

05 / CLOSE

Verify the Outcome

Confirm the reported issue has been addressed or document remaining limitations.

SERVICE COMMITMENT READINESS

A formal SLA should be supported by evidence.

Before publishing binding service guarantees, actual technical capability and contractual conditions should be verified.

The following checklist identifies information required for that review.

SLA Subject Evidence Required Current Public Position
Covered production services Confirmed service inventory and contractual scope. DEFINE BEFORE CONTRACTING
Availability guarantee Reliable measurement, monitoring evidence and agreed calculation. NO UPTIME GUARANTEE STATED
Support coverage Confirmed staffing, support hours and escalation channels. NO 24/7 PROMISE STATED
Response times Operational capacity and approved service commitment. NO FIXED TIMES STATED
Resolution targets Defined measurement and suitable contractual limitations. NO RESOLUTION GUARANTEE STATED
Planned maintenance Approved maintenance windows, communication and accounting rules. PROCEDURE TO VERIFY
Backup and recovery Verified backup coverage, restoration tests and operational procedures. EVIDENCE REQUIRED
Service credits Approved contractual remedy provisions and eligibility rules. NO CREDITS PROMISED

This table identifies areas requiring verification. It is not a technical audit report and does not establish contractual service levels.

BOOKING CONTINUITY

Preserve reservations.
Preserve responsibilities.

Hotel technology must account for reservations created through different booking sources.

Genuine hotel-direct, independent OTA and BM24 Travel Network bookings may involve different systems and contractual obligations.

An incident response process should recognise those distinctions when assessing affected reservations.

01

Hotel-Direct Reservations

Preserve the original direct-booking relationship and relevant hotel operational responsibilities.

02

Independent OTA Reservations

Preserve external booking references, original channel attribution and relevant provider terms.

03

BM24 Travel Network

Maintain the separate BM24 distribution relationship and applicable booking-source records.

04

Supplier Transition

Existing LiteAPI bookings must retain their original arrangements when future inventory moves to direct NEXUS distribution.

SERVICE LEVEL QUESTIONS

Better expectations.
Better decisions.

Understand how service availability, incident priorities and operational commitments should be defined.

What is a Service Level Agreement?

A Service Level Agreement defines the applicable service commitments between the relevant parties.

It may address service coverage, availability, support conditions, measurement and contractual remedies.

Does NEXUS guarantee 99.9% uptime?

This page does not make a 99.9% uptime guarantee or promise any other fixed availability percentage.

Binding commitments must be expressly established by the applicable approved agreement.

Does NEXUS offer guaranteed 24/7 support?

No universal 24/7 support commitment is announced here.

Actual support channels, operating hours and any special coverage must be confirmed in the applicable service terms.

What is the difference between response time and resolution time?

A response time usually describes the interval before an appropriate initial response.

A resolution time concerns the correction or restoration of an affected service.

The exact definitions and any commitments must come from the actual SLA.

What are P1, P2, P3 and P4?

They are common-style incident priority labels used in this educational model to distinguish different levels of operational impact.

The precise meaning of each priority must be defined in the actual service-management process.

Does the Priority Explorer create a support ticket?

No.

The Explorer uses local browser JavaScript.

It does not contact NEXUS, create an incident, notify an engineer or submit any hotel information.

How is availability calculated?

The example calculator uses a simple gross-calendar formula:

Availability = (Total Minutes − Downtime Minutes) ÷ Total Minutes × 100.

A real SLA may define a different contractual calculation.

Is the calculator showing actual NEXUS uptime?

No.

All inputs and results are hypothetical.

The calculator is not connected to production monitoring or historical service data.

Is planned maintenance always excluded from an SLA?

Not automatically.

Whether and how planned maintenance affects an availability calculation depends on the applicable contractual definition.

Are external OTA outages covered by the NEXUS SLA?

The scope depends on the actual service agreement and the respective responsibilities of the parties.

A third-party disruption is not automatically included or excluded without reviewing the contractual terms.

Does NEXUS provide automatic financial service credits?

No automatic service-credit commitment is announced on this page.

Any contractual remedies require approved terms, conditions and eligibility rules.

What information should I include when reporting a problem?

Where appropriate, identify the affected hotel, service, observed symptoms and the approximate incident period.

Do not share passwords, secret API keys or unnecessary guest personal data through general support channels.

Can I report a suspected security incident?

Suspected security or personal-data incidents should be communicated through the appropriate verified incident reporting process.

The public Priority Explorer is not a security reporting channel.

Does an SLA change the commercial terms of BM24 bookings?

No general change is implied.

Genuine hotel-direct, independent OTA and BM24 network bookings retain their respective commercial relationships.

Any additional contractual commitments must be expressly agreed.

Is this page itself a binding SLA?

No.

This page explains operational principles and contains educational simulations.

It is not a signed or accepted Service Level Agreement.

SERVICE & SUPPORT ENQUIRIES

Operational clarity begins with accurate information.

Hotels should understand which services are covered by their agreements and how support is requested.

For questions about NEXUS service conditions, contact HotelConnect24 using the published communication channels.

PLATFORM OPERATOR

BIGMEDIA24 Dynamics Ltd.

Registered Office
51 Bracken Road
Sandyford
Dublin D18 CV48
Ireland

Company Registration
673777

General Enquiries
support@bigmedia24.com

This general contact address is not presented as a guaranteed 24-hour incident hotline. Actual emergency contact procedures must be confirmed separately.

Reliable hotel technology deserves clear service expectations.

Discuss your hotel's operational needs, technical dependencies and the applicable NEXUS service arrangements.

Discuss Service Requirements