Transfer Database Distribution in Multi Branches of Information Systems 1.

Transfer Database Distribution in Multi Branches of Information Systems 1.
In a business that has multiple branches scattered in separate places, an information system is required that can monitor each transaction. The easy solution is to create a web-based information system with real time transactions.
Web-based advantages with centralized databases are Real time transactions so that instantly known data updates
Weaknesses include:
Must be internet connection guaranteed,
if there is a disconnected connection when the transaction is potentially invalid data
Fast internet connection
If there is a transaction delay will make uncomfortable users and consumers
Additional cost to buy and rent domain + hosting
The cost for internet access is fast

Information systems with centralized database and Real time transactions, suitable for established companies and are in locations with fast internet connection.

Our products have solutions for medium-sized enterprises that have many branches spread across many cities and are located far away in the suburbs.
Features:
Each transaction does not require an internet connection.
The transaction is stored in the local database or on the hardisk of that PC.
Only undelivered transactions will be transferred to the Center
Delivery of branch transactions every day and only done at end of office hours, with internet connection.
Center can automatically LOAD or enter branch transfer data from certain hours, eg at 17.00 s, d at 07.00 the following day
The center will always check the shipment per 10 minutes from the specified clock range.
Data in the Center will always be the same as the data in the branch, although there is a change or addition of transactions or any parent data.
This feature is similar to sync at a networking store in Indonesia

Restaurant Software, Unique Stock Design

In the culinary business, especially the type of "fast food" or fast food, management will count the number of side dishes served. Similarly, culinary business in restaurants or in lesehan. On the basis of the quantity of the side dishes, there will be a roughly obtained turnover.
However, in designing an information system, can not use the general retail system, in full. There is a fundamental difference in restaurant / restaurant management, related to stock validation. (stock here is the amount of side dishes earlier).
For example in the general retail, "a goods with different types will be made different product codes. When sold, it will automatically reduce the stock of the item ".

In fast food restaurants, eg padang restaurant, there are times when one will buy vegetable rendang only and rice plus vegetable rendang. There are 2 different stock data, so we must make different item code. Uniquely, is the 2 data earlier, should reduce the same 1 type of stock that is RENDANG. Because, management only count the number of side dishes, namely meat in rendang earlier.