RGlobal - automation system of the restaurant network "Receptor"
Hi, we are Alexander Brailovsky, the owner of the network of Cafe Receptor and Pavel Smirnov, our IT Director. Now we have 4 institutions in Moscow, the last two have already opened in the thick of the crisis. We started and develop with our own money. As it turns out to grow in all financial and operational parameters even in the aforementioned hell of a crisis, we look to the future with optimism. Our goal is 100 restaurants in 5 years (both own and open in our franchise).
To our humble, but from some side and very impressive success, we owe much of our own ERP-system.
About her today we want to talk a little bit.
Although looking outside at the warm and lamp atmosphere of the “Receptors”, this is not true, but we rely as much as possible on IT and automation. We relied on this from the very beginning, so now we have 6 programmers working on RGlobal, a SaaS system for managing restaurants. Unlike many such decisions, ours was born and grew not in a fevered startup mind, but in a real restaurant. Therefore, it solves real everyday problems, not fictional ones. And it does this in the manner that a restaurateur is comfortable, and not a programmer, a startup, an interface designer, or anyone else. RGlobal is in the development stage, but it has already been implemented in all restaurants of the Receptor chain.
')
We will make this platform part of the “Receptor” franchise, so that buyers will get a very serious competitive advantage. This is not something brilliant and overturning the industry, but simply a product that works, rolls around and really helps us manage four restaurants.
Since restaurant automation systems perform almost the same role and have a fairly well-established set of features, I will not repeat and just describe the differences of the RGlobal system from all the others.
The backend is built on Ruby on Rails, the main feature is support for multi-tenancy at the database level. In our case, the tenant is not an isolated restaurant, but an enterprise that has a chain of restaurants. Users on the same page can see and compare various indicators of institutions in real time. It is also possible to bind a user to different tenants, switching between them takes place in two mouse clicks.
In addition to the banal functions for storing personnel information, recruitment, relocations, rate changes and staffing schedules, there are two very interesting modules in the personnel management section.
- Testing staff
Personnel on the site score different kinds of questions for tests on different topics: corporate culture, mnemonics, perfect service, menu knowledge, kitchen standards, etc. Those who are tested can not only take elective tests with a choice of options, but also write their answers. In the second case, handwriting recognition is used, since not all employees can own typing on the keyboard. The system gives confidence that all employees possess all the necessary information to work in a single “Receptor” team.
- Chekin system
A useful thing that saves the management from counting the spent shifts of employees and salaries. To develop this module, it was necessary to get an Apple Developer Enterprise account, with which we were able to publish an application for iPads located in each restaurant. Upon arrival or departure, each employee enters his personal code, after which the face is photographed with a front-facing camera and time is recorded. This is all sent to the server through the API, compared with the staffing table of the employee, delays, processing are calculated, the corresponding charges or write-offs occur. If you have questions about unrecorded shifts, it is enough to show the staff list in which all of his checks will be displayed. Such accounting is much more stable against particularly tricky employees, than the standard system of time accounting for the access control system.
The basis of the automation of the restaurant business is the nomenclature, and we have worked very well on it. As the “Receptor” is proud of the technological process of cooking, so the IT department is proud of the flow chart system. For a visual display of semi-finished products and ingredients, we have developed our multi-level tree subsystem. It also displays the ingredients that make up the semi-finished products, which can also consist of ingredients and semi-finished products. There are also videotech cards where kitchen staff learn how to cook dishes.
In developing the cloud storage system, we managed to overcome the need to store and process huge amounts of information. Here is an example: there are about 1000 ordered goods for cooking, which have their own value for each batch and shelf life. If you store information for each day at each restaurant warehouse for each tenant, then at the rate of 100 tenants * 10 restaurants * 1000 nomenclatures * 365 days * 5 years = 1,825,000,000 records. This problem was solved by packing all the information into one JSON record per day for each warehouse, which reduces the number of records by 1,000,000 times.
There are real-time elements in the system: for example, when selling dishes via the POS terminal, the RGlobal API is accessed, through which the necessary products are written off, which gives a real picture of the warehouse at any time.
RGlobal is integrated with the Alloka call tracking service. Restaurants often call, so the owner can both check the speed of responses (and that they pick up the phone at all) and listen to the recordings of conversations.
Convenient financial accounting. Conveniently, everything is visible in one interface, you can easily compare the performance of different restaurants - and even employees. You can look at the specific checks, the average checks of the waiters ... In general, we are very much confused by the analytics, so in RGlobal there are a lot of reports that reveal business figures in great detail.
Micro account of all transactions
Sales information - every waiter, every table, every check is visible
Favorite schedule :-)
Real-time statistics on the work of waiters
You can even look at paycharte, what dishes the waiter sells most successfully.
If you had seen what we started from (tables in Excel and hellish Filemaker), you would appreciate our progress. RGlobal likes us very much, although, of course, many things are simply not yet ready or not working as they should. But the system develops with our restaurants and adapts to the management that we implement and cultivate. If you are also working on similar systems or are simply interested in modern restaurant franchises with a strong IT component, I will be happy to answer your questions. And I invite everyone to the “Receptor” :)
To our humble, but from some side and very impressive success, we owe much of our own ERP-system.
About her today we want to talk a little bit.
We solve the real problems of restaurateurs
Although looking outside at the warm and lamp atmosphere of the “Receptors”, this is not true, but we rely as much as possible on IT and automation. We relied on this from the very beginning, so now we have 6 programmers working on RGlobal, a SaaS system for managing restaurants. Unlike many such decisions, ours was born and grew not in a fevered startup mind, but in a real restaurant. Therefore, it solves real everyday problems, not fictional ones. And it does this in the manner that a restaurateur is comfortable, and not a programmer, a startup, an interface designer, or anyone else. RGlobal is in the development stage, but it has already been implemented in all restaurants of the Receptor chain.
')
We will make this platform part of the “Receptor” franchise, so that buyers will get a very serious competitive advantage. This is not something brilliant and overturning the industry, but simply a product that works, rolls around and really helps us manage four restaurants.
Since restaurant automation systems perform almost the same role and have a fairly well-established set of features, I will not repeat and just describe the differences of the RGlobal system from all the others.
Database level multiplicity
The backend is built on Ruby on Rails, the main feature is support for multi-tenancy at the database level. In our case, the tenant is not an isolated restaurant, but an enterprise that has a chain of restaurants. Users on the same page can see and compare various indicators of institutions in real time. It is also possible to bind a user to different tenants, switching between them takes place in two mouse clicks.
Personnel Management
In addition to the banal functions for storing personnel information, recruitment, relocations, rate changes and staffing schedules, there are two very interesting modules in the personnel management section.
- Testing staff
Personnel on the site score different kinds of questions for tests on different topics: corporate culture, mnemonics, perfect service, menu knowledge, kitchen standards, etc. Those who are tested can not only take elective tests with a choice of options, but also write their answers. In the second case, handwriting recognition is used, since not all employees can own typing on the keyboard. The system gives confidence that all employees possess all the necessary information to work in a single “Receptor” team.
- Chekin system
A useful thing that saves the management from counting the spent shifts of employees and salaries. To develop this module, it was necessary to get an Apple Developer Enterprise account, with which we were able to publish an application for iPads located in each restaurant. Upon arrival or departure, each employee enters his personal code, after which the face is photographed with a front-facing camera and time is recorded. This is all sent to the server through the API, compared with the staffing table of the employee, delays, processing are calculated, the corresponding charges or write-offs occur. If you have questions about unrecorded shifts, it is enough to show the staff list in which all of his checks will be displayed. Such accounting is much more stable against particularly tricky employees, than the standard system of time accounting for the access control system.
Nomenclature
The basis of the automation of the restaurant business is the nomenclature, and we have worked very well on it. As the “Receptor” is proud of the technological process of cooking, so the IT department is proud of the flow chart system. For a visual display of semi-finished products and ingredients, we have developed our multi-level tree subsystem. It also displays the ingredients that make up the semi-finished products, which can also consist of ingredients and semi-finished products. There are also videotech cards where kitchen staff learn how to cook dishes.
Warehouse operations
In developing the cloud storage system, we managed to overcome the need to store and process huge amounts of information. Here is an example: there are about 1000 ordered goods for cooking, which have their own value for each batch and shelf life. If you store information for each day at each restaurant warehouse for each tenant, then at the rate of 100 tenants * 10 restaurants * 1000 nomenclatures * 365 days * 5 years = 1,825,000,000 records. This problem was solved by packing all the information into one JSON record per day for each warehouse, which reduces the number of records by 1,000,000 times.
There are real-time elements in the system: for example, when selling dishes via the POS terminal, the RGlobal API is accessed, through which the necessary products are written off, which gives a real picture of the warehouse at any time.
Calls (integration with Alloka)
RGlobal is integrated with the Alloka call tracking service. Restaurants often call, so the owner can both check the speed of responses (and that they pick up the phone at all) and listen to the recordings of conversations.
Accounting Finance
Convenient financial accounting. Conveniently, everything is visible in one interface, you can easily compare the performance of different restaurants - and even employees. You can look at the specific checks, the average checks of the waiters ... In general, we are very much confused by the analytics, so in RGlobal there are a lot of reports that reveal business figures in great detail.
Micro account of all transactions
Sales information - every waiter, every table, every check is visible
Favorite schedule :-)
Real-time statistics on the work of waiters
You can even look at paycharte, what dishes the waiter sells most successfully.
Conclusion
If you had seen what we started from (tables in Excel and hellish Filemaker), you would appreciate our progress. RGlobal likes us very much, although, of course, many things are simply not yet ready or not working as they should. But the system develops with our restaurants and adapts to the management that we implement and cultivate. If you are also working on similar systems or are simply interested in modern restaurant franchises with a strong IT component, I will be happy to answer your questions. And I invite everyone to the “Receptor” :)
Source: https://habr.com/ru/post/394155/
All Articles