Tally.ERP9, Tally.Server 9
Overview
The Tally.Server 9 technology is built with multi-version concurrency capabilities for providing most efficient scalability. Requests from every user get equal priority and get solved in parallel with others, rather than sequentially. There is no queuing of access or modification requests and so every user will feel as if he were working with his own local copy or snapshot of data. Tally.Server 9 will ensure that the data access/modification by a user is isolated to his/her own snapshot, thus allowing other users to operate smoothly.
In other words, with Tally.Server 9, there is essentially no blocking of another user’s tasks, even as new users keep getting added to the system, or because of the types of tasks being performed. It also maintains very high data consistency in intense use environment. Overall it leads to lower cost of ownership, lower maintenance and higher efficiency of operations for any medium to large business needing an enterprise grade system.
Performing operations in a frictionless environment
| Multiple users will be able to simultaneously load companies, save transactions, export reports, print reports, import data, take backup and perform other data related activities without experiencing any downtime or wait state. Let us consider some examples - Suppose a user starts to take a report for the last month. Another user wants to update a bill for the same month. Normally one would have to wait for the other. Concurrent access will ensure that both users are able to do their activities at the same time. |
Similarly when a number of users open the company for loading, typically at the start of the day, it is loaded for each user one at a time. This means that the total time to load the company is actually the time taken by the last user to finish, and only after the last user has loaded, can the work of data entry start. However with concurrent data access, all users can load and open the company in parallel and thus get up-and-running in much less time. This frictionless access directly results in optimal utilization of man hours as the velocity at which a task gets completed on the system will increase significantly.
Thus, with greater speed of task completion and zero downtime, Tally.Server 9 helps ensure optimal utilization of man hours for your organization!
Keeping the data file safely invisible and providing controlled access
| The data files are now managed through Tally.Server 9. The physical location or path for the data on the server is not required to be made known or accessible to any user. The clients just require the name of the data server, which will be enough to access and operate Tally.ERP 9. Furthermore, operations for company data management like backup, restore etc. are also controlled with server level permissions. This will ensure that data managed by Tally.Server 9 is only available with necessary authorization. |
Minimizing instances of system unavailability
| Availability of the system is important for any business. Any time the system is unavailable; there is a loss of productive time. This can happen due to various reasons - For example – Maintenance operations like backup require that all users stop working so that a proper and consistent backup can be taken. This is often managed by doing such operations late at nights or at odd hours. With Tally.Server 9, backup can be taken anytime without affecting either the speed of access for the user or the consistency of data that is backed up. In other words users can continue entering transactions or operating reports while the backup is happening - There is zero downtime for backup. |
Analysing system usage and user activities to optimize the various processes and time spent on them
| Since the access is controlled through Tally.Server 9, the authorized users will be able to monitor who is currently logged in, which companies are open, track the activities and even disconnect users if such a requirement arises. Each business process or function requires users to perform certain activities and spend some time to input and/or analyse information. As an example, a user has to take data from bank statement and input it into the bank ledger on the system, for reconciliation of balances. A business may expect that this function will require 60 man hours to be spent a month however, it is taking 120 hours as per Tally.Server 9 reports. |
Security / Validation Customization
Negative Stock Blocking
Minimum / Maximum / Safety Reorder levels. ( Locking consumption if going below Minimum Order level )
P.O. rate locking for specific users
Locking of Terms conditions - Supplier-wise
P.O. raising authority ( User-wise - Amount-wise Authority )
Purchase Order Authorization ( Authorization for any document )
Multi-level authorization
GRN/ PO Rates Locking/ Qty Locking ( Qty or Rate should not be more than that of PO )
Locking of Sales Order rates for Invoices
Locking of Terms & conditions - Customer-wise or Customer-location-wise.
Restricting Debtors below Credit Limit ( credit-amount or credit days )
0 comments:
Post a Comment