How Bastion Hotels rebuilt their infrastructure in five months, delivered around every operational calendar.

Chapter 01 · The situation

The infrastructure Bastion ran on came from 2014. At the time it was ambitious: WiFi covering every hotel, controlled from one central point at Sbit. For eight years it did what it was built to do. But hotels do not stay still. Guests started streaming everything. Meetings moved onto laptops in the room. The one device per guest became four. The corridor access points that made sense in 2014 could not deliver the in room experience guests now expect as baseline.

Three problems ran in parallel, and each one made the other two harder to solve on its own.

The 2014 access points were in the corridors, not the rooms. Coverage existed on paper. Reality was that streaming a film from bed dropped signal, video calls stuttered, and guest reviews started to notice.

The room TVs could not run Netflix, could not cast from a phone, could not do what a guest’s own screen at home does without thinking. Guests brought HDMI cables. Most did not.

All 33 hotels ran through one physical WLAN controller at Sbit. It worked. It was also aging, tied to one location, and the wrong architecture for cloud native operations across a growing portfolio.

Chapter 02 · The strategic design

The temptation in a project this size is to solve the loudest problem first and get to the others later. We designed against that instinct. WiFi, telephony, television and central management would be rebuilt as one connected system. Every room its own foundation. Every hotel manageable centrally. Every element replaceable without touching the others. This is where Strategy earns its keep: before the first cable gets pulled.

Chapter 03 · Delivery

The implementation window ran across five months. The team who designed the architecture in Chapter 02 was the same team who delivered it on the ground. That is not a coincidence. It is how you deliver a transformation at this scale without discovering things in production, and it is the operating principle of how Sbit runs Strategy & Project Services.

The plan divided responsibility clearly: Bastion’s Technical Department pulled every cable and mounted every access point, TV and phone. Sbit designed the network, configured everything, installed the switches on site, and validated each location.

This division works because both sides know what they are good at. Bastion’s TD moves through their own buildings faster than any external team. Sbit’s engineers configure Zyxel and Philips systems in their sleep. Neither team steps on the other.

Each of the twenty five properties moved through the same sequence, timed against the hotel’s own operational calendar so the project moved with the property, not through it.

Per hotel walkthrough, timing agreed with the Hotel Manager. Every property has its own rhythm and its own peak season. The plan started with respecting that.

All equipment ordered in one batch by Sbit for volume pricing. Delivery slots pre booked against the property schedule.

Cables pulled to every room before equipment arrival on site. Bastion’s team moved through the buildings on their own timeline, which is faster than any external contractor because they know the buildings.

Hardware delivered from distributor to hotel in one shipment. No warehousing detour. Reduces handling, reduces damage risk, and lands equipment where it needs to be installed.

Sbit installs switches. Bastion TD mounts access points, TVs and phones. Configuration happens in parallel on the Nebula cloud dashboard rather than at each access point manually.

Sbit validates every location, decommissions old equipment, closes out the property. The old controller stays running until the last hotel is validated, then goes offline as one clean cutover.

Twenty five hotels were completed in the project window. The remaining properties were either already on newer WiFi from earlier upgrades, or scheduled for full renovation where the ICT upgrade would happen alongside the building work. The scope was defined by what made sense for the guest experience, not by what looked biggest on paper.

Chapter 04 · What changed

For guests, staff and finance, the outcomes look different. All three sit on the same foundation.

Netflix runs on the room TV. Casting from a phone works first time. The WiFi covers the whole room, not just the hallway. The phone rings when reception calls. None of this is exciting. All of it should have been true five years ago. Now it is.

No more calls saying “the WiFi is down on the second floor.” The Nebula dashboard sees it before the guest does. No more escalation chains between the phone vendor, the TV vendor and the network vendor. One system. One accountable partner. Managed 24/7 by Sbit.

The capital investment rolls into a long term managed services agreement. Monthly managed services fit inside a predictable operating budget. Nebula subscriptions are the only variable line, and they scale linearly with hotels added. No surprise capex on the horizon.

Chapter 05 · The partnership

Bastion has been an Sbit client since 2014. This project moved on this schedule because both teams had eight years of shared context. We knew every hotel. We knew every anomaly. We knew where the risk was buried and where the wins would come from.

That context does not exist with a new provider. It has to be built. In hospitality, where downtime is expensive and guest experience is everything, that context is the reason a project like this can move on this schedule. It is also the reason why the extension of the partnership was signed alongside the project close, not after it.

Every long partnership eventually gets tested by a project of this size. The test either strengthens it or ends it. In this case, the eight year foundation held, and the next eight are already booked.