Opens in a new tab
NEXUSHOTELCONNECT24

NEXUS / SYSTEM STATUS & MAINTENANCE

Operational transparency.
When it matters most.

Hotels depend on connected technology to manage reservations, room availability and distribution.

A useful status centre should explain which services are affected, what is being investigated and whether important workflows require attention.

Explore the proposed NEXUS approach to service status, incident communication and planned maintenance.

Current public status: not independently verified. This page does not connect to live NEXUS monitoring systems. All scenarios and maintenance notices shown in the interactive sections are fictional examples.

Status information Must be based on verified telemetry
Incident communication Clear impact and affected services
Maintenance information Approved schedules and notifications
Current interface Educational preview only

INTERACTIVE SYSTEM STATUS EXPLORER

See how service conditions affect hotel operations.

This interactive preview demonstrates how a future NEXUS Status Centre could explain the condition of individual platform services.

Select a fictional scenario to explore operational impact, affected services and example status updates.

None of the displayed scenario states represent real NEXUS system health.

NEXUS / Status Centre Five service categories · Example operational scenarios
TRAINING MODE
NO LIVE TELEMETRY
DEMONSTRATION ONLY — NOT CURRENT SYSTEM STATUS.
The service indicators below are generated from predefined browser scenarios. They do not represent verified production availability, active incidents, provider acknowledgements or actual maintenance.
FICTIONAL SCENARIO

Example: Normal Operations

A fictional scenario in which the example services are behaving normally.

SELECTED SERVICE / TRAINING VIEW

Channel Manager

Select a service card to examine its fictional condition and operational implications.

Data source Browser Scenario
Live verification Not Connected

A real service status should distinguish request transmission, provider acknowledgement, successful processing and eventual reconciliation.

Example Event Timeline

Illustrative events only. No actual dates, system logs or monitoring records are shown.

  1. Fictional scenario initialised.
  2. Example service state evaluated.
  3. No real telemetry was retrieved.
Technical boundary: This dashboard does not fetch a live API, query the BM24 Server Center, check Hetzner or Dell, read production logs, create incidents or update actual hotel availability.

UNDERSTANDING STATUS INDICATORS

A status should explain what has been verified.

A professional status page should avoid reducing complex technical conditions to a misleading single green indicator.

These are example state definitions for a future monitoring implementation.

01 / NORMAL

Service Operating

A verified monitor indicates that the defined service is meeting its operational health criteria.

This state must be supported by current measurement data.

02 / DEGRADED

Partial Disruption

The service may remain accessible, while one or more important functions are affected.

The affected workflows should be described clearly.

03 / DELAYED

Processing Pending

A request may have been transmitted without being fully acknowledged or applied.

Delayed synchronisation must not be presented as confirmed completion.

04 / MAINTENANCE

Planned Intervention

An authorised maintenance activity may affect a defined service for a specified period.

A real notice must come from an approved schedule.

INTERACTIVE MAINTENANCE IMPACT PLANNER

Plan the change.
Explain the impact.
Communicate clearly.

Maintenance information should tell hotels which services could be affected and what they may need to check.

Use the fictional Maintenance Impact Planner to build a sample operational notice.

Select the service, maintenance type, proposed date, estimated duration and expected impact.

The resulting notice is a browser preview. It is not published or sent to any hotel.

NEXUS / Maintenance Planner

Create a fictional maintenance notice and review its potential impact.

FICTIONAL MAINTENANCE NOTICE

Draft Notice Preview

Choose the example maintenance conditions and generate a preview.

Proposed start Not Scheduled
Estimated duration Not Confirmed
Potentially affected workflow

No impact assessment has been generated.

Demonstration boundary: The planner does not access production systems, schedule maintenance, send customer messages, save entered dates or publish status updates. Dates are shown as entered locally. No authoritative service timezone is assigned.

MAINTENANCE & INCIDENT COMMUNICATION

Useful updates answer the questions hotels actually have.

Hotels need more than a technical error identifier.

A relevant status notice should explain the operational impact without revealing sensitive infrastructure information.

01 / WHAT

Affected Service

Identify which functional component is affected, such as reservation processing or channel synchronisation.

USE CONFIRMED SERVICE NAMES
02 / WHO

Affected Scope

Explain whether the event affects selected properties, a defined integration or a wider production service.

VERIFY IMPACT BEFORE PUBLISHING
03 / WHEN

Time Information

State relevant start times, update times and maintenance windows with an explicit timezone where appropriate.

AVOID AMBIGUOUS TIMESTAMPS
04 / EFFECT

Operational Consequences

Describe whether bookings, inventory, prices or administrative access may be affected.

DISTINGUISH KNOWN FROM POSSIBLE IMPACT
05 / PROGRESS

Investigation & Updates

Provide appropriately verified information about investigation, mitigation and relevant changes.

DO NOT INVENT RESOLUTION TIMES
06 / CLOSE

Recovery Confirmation

Confirm the affected workflows are functioning again before presenting an incident as fully resolved.

VALIDATE BEFORE CLOSURE
STATUS INFORMATION MUST BE TRUSTWORTHY

A green indicator is not evidence of a healthy service.

Trustworthy status information depends on actual monitoring, valid measurements, clear service boundaries and responsible publication.

FROM CONCEPT TO LIVE STATUS

Before going live, verify every signal.

A public status page should not rely on manually invented service conditions.

The following areas must be implemented and tested before this concept becomes an actual NEXUS operational status service.

01

Real Service Monitoring

Connect status reporting to verified monitors covering the actual production services.

NOT CONNECTED HERE
02

Accurate Service Boundaries

Define which components are externally visible, which processes depend on each other and what constitutes a meaningful service failure.

VERIFY SERVICE MODEL
03

Source Freshness & Unknown States

Monitor the age of incoming status data. Missing or outdated telemetry must not automatically appear as healthy.

IMPLEMENT VALIDATION
04

Verified Incident Publication

Establish an authorised process for incident creation, customer-facing updates and confirmed resolution.

DEFINE APPROVALS
05

Approved Maintenance Schedule

Use actual authorised maintenance records with clear dates, timezones, affected services and communication rules.

CONNECT WHEN READY
06

Resilient Status Publication

Ensure the public status information remains accessible during relevant incidents wherever feasible. A status page should not depend exclusively on the failing service.

TEST INDEPENDENCE

INCIDENT COMMUNICATION LIFECYCLE

From detection to verified recovery.

A structured communication process helps distinguish an initial symptom from a confirmed technical diagnosis.

The following sequence is a proposed operating model.

01 / DETECT

Identify a Signal

Receive a report or monitoring alert indicating a possible service problem.

02 / VERIFY

Confirm the Impact

Evaluate whether the issue is genuine, which services are affected and how hotels may be impacted.

03 / COMMUNICATE

Publish an Update

Explain the confirmed situation and any relevant operational guidance.

04 / RESTORE

Resolve & Reconcile

Investigate and correct the issue, then verify relevant processing and synchronisation.

05 / CLOSE

Confirm Recovery

Close the event only after appropriate checks support the recovery conclusion.

HOTEL CONNECTIVITY MATTERS

A successful request is not always a completed update.

Hotel connectivity often involves multiple independent systems.

Operational status must distinguish a submitted update from an accepted and successfully processed update.

01 / CHANNEL MANAGER

Rates & Availability

A rate change may be submitted to a connected channel without receiving immediate confirmation that the new value has been applied.

A real monitoring system should recognise pending and rejected updates.

ACKNOWLEDGEMENT MATTERS
02 / RESERVATIONS

Booking Processing

Reservation workflows require careful handling of booking references, modifications, cancellations and source attribution.

Technical recovery should include appropriate reconciliation of affected records.

PRESERVE BOOKING INTEGRITY
03 / BM24 NETWORK

Network Distribution

Direct BM24 network distribution requires separate publication approval and clear tracking of network inventory and booking sources.

A restored technical connection must not bypass required commercial or operational approvals.

APPROVALS REMAIN REQUIRED

SYSTEM STATUS QUESTIONS

Clear answers.
No invented status.

Understand the difference between a live status page, a technical simulation and a contractual service commitment.

Does this page show actual NEXUS system status?

No. The interactive status cards currently use predefined fictional scenarios.

They do not contain live monitoring results or production incident information.

Why is live monitoring marked as not connected?

A production monitoring integration has not been established for this webpage.

Until verified telemetry is available, the page does not claim that any service is currently operational or unavailable.

What is the difference between degraded and unavailable?

Degraded generally describes a service that remains partly accessible while some functionality is affected.

Unavailable generally indicates that an identified service cannot perform its defined function.

Actual definitions require a verified monitoring policy.

Can a synchronisation request succeed while a channel is still out of date?

Yes.

A request may be transmitted successfully without the receiving provider having accepted and applied the update.

A meaningful connectivity status should consider acknowledgements and reconciliation.

Does this page show real maintenance dates?

No.

The Maintenance Planner creates fictional notice previews from the visitor's local inputs.

It does not display an approved NEXUS maintenance schedule.

Can I subscribe to real incident notifications?

This page does not currently provide a live subscription or incident-notification service.

Any future subscription feature should be connected to a verified status publication and notification system.

Is there a public status API?

This page does not advertise an operational public status API.

An API should be announced only after its authentication, availability, data definitions and deployment have been verified.

Does a normal status guarantee every booking will succeed?

No.

A service-level health indicator cannot guarantee every individual transaction.

Booking outcomes can depend on availability, supplier systems, payment processing and other conditions.

Are third-party outages included?

Independent providers may affect particular hotel workflows.

The actual service responsibilities and contractual treatment of external disruptions depend on the relevant agreements.

Does NEXUS guarantee a fixed uptime percentage?

This page does not make any guaranteed uptime commitment.

A binding availability target must be established through the applicable approved service terms.

Does NEXUS guarantee 24/7 incident response?

No universal 24/7 response promise is made on this page.

Actual support hours and escalation channels require separate verification.

Does selecting a scenario report a real outage?

No.

Selecting a scenario only changes the fictional information displayed in this browser.

It does not contact NEXUS or create an incident ticket.

Does generating a maintenance notice schedule real work?

No.

The planner does not connect to any maintenance calendar, send notifications or affect production systems.

Where can I report a genuine technical issue?

Use an approved NEXUS support or communication channel applicable to your service.

The general HotelConnect24 contact page can be used for enquiries.

It is not represented as a guaranteed emergency hotline.

SERVICE INFORMATION & ENQUIRIES

Clear communication supports operational confidence.

Hotels should know where to ask about service availability, maintenance and technical requirements.

For general NEXUS enquiries, contact HotelConnect24 through its 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

The general enquiry address is not advertised as a guaranteed emergency support or 24-hour incident response channel.

Better visibility. Better communication. Better preparation.

Learn more about NEXUS operational principles and discuss your hotel's technical requirements.

Discuss Your Requirements