Appfy

See all cases

Hotel groups

In one QA operation, the API was interrupted for about 2 minutes. That observation is not time saved.

In a hotel restaurant, an update can leave everything switched on and still the order never reaches the kitchen.

The problem
In the restaurants of several hotel groups, every server was created one by one, with the settings repeated for each group, and a server switched on did not guarantee the order reached the kitchen. Estimate: 20 restaurants × 1 hour of dinner stopped × R$6k an hour (40 bills of R$150) ≈ R$120k for every update that stalls (figures: assumptions).
What Appfy did
Appfy built the path updates take from scratch: a written recipe sets up every server, in each hotel group's own setup, always in the same steps, and the last step checks that the order goes from table to kitchen. The team got the manuals.
The gain
Every new version follows the same steps, and replacing a server means setting up another from the recipe.

  1. Scene 1 of 8The company

    From table to kitchen, the order has to arrive right.

    Hotel groups run a till and kitchen system in their restaurants: the waiter enters the order, the kitchen sees it on screen, the bill is split and the receipt prints.

  2. Scene 2 of 8The problem

    A light on did not mean the order was getting through.

    Every server was created one by one, like cooking every dish from memory, and the settings were repeated for each hotel group. A server switched on did not guarantee the order reached the kitchen.

  3. Scene 3 of 8The goal

    Done is when the order goes through, not when the server switches on.

    Appfy took on the path that brings every new version to the servers. The goal: the same steps every time, like a conveyor belt, and done only when an order makes the whole trip.

  4. Scene 4 of 8The choice

    Instead of fixing each server, set up a new one from the recipe.

    Appfy wrote a recipe for each type of server. Every new version gets a new recipe: new servers are made from it and take the place of the old ones, which are switched off.

  5. Scene 5 of 8What Appfy did

    Every new server sets itself up when it starts.

    When it starts, the new server follows a script: it fetches the instructions, installs the versions and starts the system. The database got a step of its own, and the team got the manuals.

  6. Scene 6 of 8What Appfy did

    Four healthy replacements/PM2 processes. Only two of four refreshes complete at the snapshot.

    In one QA operation, the API was interrupted for about 2 minutes. That observation is not time saved. Four healthy replacements/PM2 processes. Only two of four refreshes complete at the snapshot. Later, the RCA handoff said the application still used the previous database.

  7. Scene 7 of 8What changed

    Every update ends with one question: did the order arrive?

    Now every version follows the same steps, replacing a server means setting up another from the recipe, the team has a manual in hand and the last question is always the same: did the order arrive?

  8. Scene 8 of 8And in your company?

    Updating systems while you are open? First define what done means.

    If the operation cannot stop, Appfy writes every step, checks them one by one and finishes on the customer's path, not on the light being on. Start with a free 30-minute conversation.