Abstract
Contents
- Introduction
- 1. Relevance of the topic
- 2. Purpose and objectives of the study, planned results
- 3. Analysis of the modern application of order reservation systems
- 4. Review of existing restaurant automation systems
- 4.1 Jupiter restaurant automation system
- 4.2 R-Keeper System
- 5. Review and analysis of existing types of application architectures
- 5.1 Client-Server Architecture
- 5.2 File Server Architecture
- Conclusions
- List of sources
Introduction
1. Relevance of the topic
Real-time order reservation process - provides immediate data processing. As a result, the quality of service increases by reducing the time it takes to service customers, the volume and variety of services offered increases, as well as broader opportunities to ensure the optimization of service, the use of new management methods.
Due to the obvious advantages of centralized computer data processing, at the moment, reservation systems for pre-orders occupy an important place in the organization of institutions related to public catering: whether it be a restaurant or a canteen. For such enterprises, as a rule, it is important either information about the availability of vacancies in the service room, or those that relate to orders directly for the dishes themselves. The latter become necessary, since the organization, on the one hand, can more quickly satisfy the needs of customers, and on the other hand, it can optimally procure and distribute products. The products, thanks to the preliminary information generated by the system, are distributed for the preparation of dishes, which, in turn, are highly likely to be ordered.
2. Purpose and objectives of the study, planned results
The aim of the study is to increase the effectiveness of the process of booking orders in public organizations power supply through the development and implementation of an automated system.
To achieve this goal, the following tasks have been set:
- analysis of the scope of order reservation systems and existing types of application architectures;
- investigation of information flows of an object;
- study and analysis of existing methods and means of implementing the system for the selection of hardware and software for its development;
- development of the structure of the program and algorithms for solving problems;
- development of the system database structure;
- software implementation of system elements.
Object of research : the process of automating the reservation of orders in a catering enterprise.
Research subject : methods and tools for software development of order reservation systems.
3. Analysis of the modern application of order reservation systems
Doesn't call today doubt that a restaurant, cafe, or other similar enterprise of public food can no longer fully function without automated control.
Experienced restaurateurs do not need to explain what the implementation gives automation systems. The chef knows in advance what to cook, and the owner always has accurate information about the work of his institution. Analytics provided by program, will show reports on the sale of certain dishes and will allow you to understand that want to see customers in the restaurant. The control of employees is significantly facilitated by the system of differentiation of access rights. Job reports staff will help to identify ineffective employees, reduce the risk of fraud and virtually eliminate financial losses.
An institution equipped with an automation system has a number of advantages over a non-automated one:
- the speed and quality of service in such an establishment is much higher;
- the number of errors on the part of the staff is noticeably reduced;
- an order from a client is automatically sent to the chef;
- development of the structure of the program and algorithms for solving problems;
- the owner always has up-to-date data on the work of his establishment [ 1 ]
The automation system serves not only to reduce the amount of manual labor, but is also designed to analyze the results of this very labor. In addition to automating the current business processes at the enterprise, the restaurateur must remember how the chosen system will limit the opportunities for business development in the future. When choosing a system, it is important not to allow the business opportunities to outgrow the capabilities of the selected system, requiring its modernization or replacement. When automating an institution, the nature of the institution (cafe, bar, restaurant) also plays an important role. The chosen scheme of customer service significantly affects the set of functions required from the automation system. In addition, this also affects the commercial equipment, which should be used in the automation of the enterprise. For example, for enterprises operating according to the Fast-Food scheme, there is no need to purchase service-printing printers (printout of a job for a chef (brand) for preparing dishes to order) - all dishes are already ready. For the table-service visitor service scheme (with a waiter), on the contrary, such printers are required. There are no ready-made meals, they must be prepared in accordance with orders from visitors.
Thus, it is obvious that that this subject area offers a wide space for designing new systems for enterprises of a specific type and size.
4 Overview of existing restaurant automation systems
4.1 Jupiter Restaurant Automation System
The system consists of the following modules:
- cash desk (restaurant, bar, fast food);
- warehouse (accounting and control of the movement of inventory items at a public catering enterprise);
- staff management (formation of a schedule, accounting for hours worked, payroll, report);
- delivery (delivery system, driver management, maintaining a customer database);
- money (accounting and control of cash flows by storage locations, counterparties, currencies, financial responsibility centers and additional features).
The system is flexible. System modules can be combined into a single whole - so that they will use a single database. It is possible to allocate a separate information space for each module. This scheme makes it possible to increase the reliability of the system - the cash module can be installed directly at the cash register, the warehouse module - on the accountant's computer, the financial module - on the director's laptop. In this case, you can transfer the necessary data from one module to another.
System scalability. The system can run on a single computer - i.e. it is enough for a restaurant to buy a single computer to use all the functionality of the system - cash desk, warehouse and finance. It can also work in a local network (when all computers are constantly connected to each other), in a distributed network (when there is no permanent communication channel between some computers) - for example, a cash register system is installed in restaurants, and warehouse and financial accounting is kept in the central office. In this case, data exchange is carried out by transferring files in any available way - on a floppy disk, flash drive, by E-mail, etc.
The reliability of the system is manifested in the fact that the built-in backup technology regularly saves all information in the archive and allows you to quickly restore it if necessary. In the event of a local network failure, the restaurant's cash desk continues to work - you can take orders and close accounts. There is no strict division at the station of waiters and cashiers - any terminal can be made a cash desk, it is enough to connect a fiscal registrar to it. Those. if the cash register breaks down, you can quickly turn any other terminal into a cash register and close any accounts, regardless of which terminals they were opened at.
System security is expressed in the ability to flexibly configure user access rights. The reporting system allows you to track the most important aspects of the restaurant's work (cancellations, refunds, etc.).
System functionality:
- work with TouchScreen monitors (without using a keyboard); it is also possible to use ordinary monitors (work with a regular mouse);
- registration of an employee at the checkout using a code or a magnetic card;
- accepting an order from a client at a table (in a restaurant), in a bar or fast food (different interfaces for accepting an order);
- work with several rooms in one restaurant;
- dish modifiers, instructions on the specifics of cooking;
- order of preparation of dishes, change of order, restrictions on change of order;
- print kitchen receipts (print groups, print redirection for different restaurant halls);
- transfer of individual positions to another table;
- transferring the entire table to another waiter;
- printing guest invoice;
- acceptance of payment (various types of cash, non-cash, fiscal and non-fiscal types of payments are possible);
- closing an account, printing a fiscal receipt;
- built-in discount system, accumulative discount system, work with corporate clients and club cards.
The system allows performing functional improvements for an individual client as an addition to the standard solution. At the same time, no changes are made to the program code of the standard solution, due to which all contractual conditions (system maintenance, regular updates of the standard solution, technical support) are preserved [ 3 ]. P >
The system operation window is shown in Figure 1.
4.2 R-Keeper System
R-Keeper is used in more than 3000 restaurants, cafes, fast food outlets (FastFood), applied in 135 cities (including Moscow, St. Petersburg, Kiev, etc. R-Keeper is highly reliable multifunctional system, which includes a whole family of software products that meet the needs of enterprises in the service sectors of various forms (classic restaurant, cafe, fast food, entertainment center, etc.).
This is a powerful tool for comprehensive control of the hall, warehouse accounting and time attendance, excellent assistant for financial management. Multivariate analysis will allow reduce production costs through effective management flows of goods and optimal use of human resources.
It allows you to solve many problems that arise every day when working in a bar, bistro, cafe and restaurant. The most tangible results are achieved in the following areas:
- maximum speed and ease of work of staff when serving customers, which is achieved by the minimum time spent on ordering and organizing service printing in bars and kitchens;
- calculation errors are eliminated, documentary operations are maintained at all levels;
- availability of a reliable system of protection against unauthorized access, using modern means of identification and separation of powers at the program level;
- implementation of statistical calculations on sales;
- a database is created that can be used by programs for accounting for the movement of products in production, calculating staff salaries, etc.
For the functioning of the Back-Office system, it is desirable to use SQL Server. Operation guaranteed for InterBase (SCO UNIX or Windows NT). Supports Microsoft SQL, SyBase SQL, Informix, Oracle; everything is TCP / IP. The R-Keeper system operates on several cash registers, called stations, connected to a local area network. The maximum number of stations connected to one network is limited by the characteristics of the computer network.
An IBM PC - compatible computer is used as a manager station. The bartender's and cashier's stations are specialized IBM PC-compatible computers with as additional devices: readers from magnetic cards or electronic tablets, connectors for connecting receipt printers, interfaces for the cash drawer and customer display. The waiter's station includes a specialized computer with a magnetic card reader.
For large restaurants with a large number of workstations, it is recommended to use a file server (IBM PC-compatible computer with good speed characteristics). The additional costs are paid off by the significant acceleration of the system.
Detailed tutorials are included for learning R-Keeper. Experts provide support in mastering the system [ 4 ].
5 Review and analysis of existing types of application architectures
5.1 Client-Server Architecture
Currently, this is the most common architecture in which many working information systems are executed.
In the traditional sense, a system implemented in a client-server architecture is a set of interacting components of two types - clients and servers.
The client is the requesting machine (usually a PC), the server is the machine that responds to the request. Both terms (client and server) can be applied to both physical devices and software.
A client can make requests to multiple servers. Servers can also make requests to each other. Thus, a typical protocol for one fact of interaction can be represented in the form of two exchanges - a request to the server and a server response.
The interaction of the client and servers is shown in Figure 2.
The most common class of client-server applications are various database applications. In this case, the server is the DBMS that ensures the execution of client requests, which in turn implements the user interface [ 5 ].
The "client-server" architecture allows you to optimally distribute the computing load between the client and the server, which affects many characteristics of the system: cost, performance, support.
Advantages: allows you to organize a network with a large number of computers; Provides centralized account management and efficient access to network resources.
The disadvantages include the fact that the inoperability of the server can make the entire network inoperative.
5.2 File Server Architecture
When a network multiuser application is built according to the principle of a file-server architecture, data in the form of one or more files is located on the file server. The file server accepts requests from client computers over the network and transfers the requested data to them. However, this data is processed on client computers. Each computer runs a complete copy of the data processor. Any such copy independently manages the files containing the data. The only link between these independent actions is the lock file (a file that has the same name as the application file, but with the Idb extension), which is necessarily created for each database file with the mdb extension. At the same time, each copy of the data processor performs index changes, work with system tables and other functions that are within the competence of the DBMS [ 5 ].
Pros of architecture: low development cost; high development speed; low cost of software updates and changes.
The drawbacks of the file server architecture are obvious and stem primarily from the fact that data is stored in one place and processed in another. This requires their transmission over the network, which leads to very high loads on the network and, as a result, a sharp decrease in application performance with an increase in the number of concurrent clients. The second major drawback of this architecture is also a decentralized solution to the problems of data integrity and consistency and concurrent data access, which reduces the reliability of the application.
Conclusions
In the course of the master's thesis, options for existing automation systems for the restaurant business are considered at this stage, it was decided to create our own system, less costly and more fully meeting the requirements of the company for automate and improve the efficiency of the order reservation process.
The developed system will help improve interaction with customers to establish control and accounting of order fulfillment. Even if you lead history of calls and contacts on paper or in Excel - this can be an accounting scheme and control works and allows you to control all options for interaction with clients.
References
- «Автоматизация ресторанного бизнеса» [Электронный ресурс]. – Режим доступа: http://www.ivs-company.ru/services/restaurant/
- Рязанцев, А. CRM-система. Порядок в продажах за 6 недель / А.Рязанцев. – М.: 1000 Бестселлеров, 2019. – 200 с.
- «Система автоматизации ресторана «ЮПИТЕР»» [Электронный ресурс]. – Режим доступа: http://www.b-class.ru/fastfood.phtml
- «Система R-Keeper» [Электронный ресурс]. – Режим доступа: http://www.datakrat.ru/oborudovanie_i_po/r-keeper.html
- «Отличие архитектуры «клиент-сервер» от архитектуры «файл-сервер»» [Электронный ресурс]. – Режим доступа: http://books.kulichki.com/data/access/as1/Glava%2017/Index3.htm
- «Информационные потоки» [Электронный ресурс]. – Режим доступа: http://pravil.net.ua/plan3/2_2.html
- «Web-приложение» [Электронный ресурс]. – Режим доступа: http://ru.wikipedia.org/wiki/Веб-приложение
- «Ajax – новый подход к разработке web-приложений» [Электронный ресурс]. – Режим доступа: http://ajax-development.narod.ru/ajax-article.html
- «Функциональности Ajax при помощи Ajax4jsf» [Электронный ресурс]. – Режим доступа: http://www.ibm.com/developerworks/ru/edu/os-ag-jsf3/section2.html
- «Chapter 5. Basic concepts of the RichFaces Framework» [Электронный ресурс]. – Режим доступа: http://docs.jboss.org/richfaces/3.3.2.GA/en/devguide/html/Architecture Overview.html
- «Apache Tomcat» [Электронный ресурс]. – Режим доступа: http://ru.wikipedia.org/wiki/Apache_Tomcat