At the core of ExaMIn’s many features and comprehensive integration are the many systems and sub-systems that go into making ExaMIn a true ERP product.  However, keeping in mind that once an ERP product (any product) has been installed and implemented, the serious task of keeping the product updated through a series of transactions as well as new master’s data entry is where most ERP users live.

The other side of the proverbial coin is the operational reporting obtainable from a well implemented ERP product. Although, here again, the onus lies on the (division, department, general or a team) manager’s ability to author and extract intelligent reporting information and that too, on a timely periodic basis.

In most cases operational reporting is for the purpose of confirmation of transactions that have taken place and maybe, even its effect on dependent systems. To give an example or two, the number of hours put into the completion of a maintenance job, the number of items that were sold within a time period through a particular location within a specific category of items, the personnel attendance within a department or even the number and value of transactions that will affect the cash flow of the company, all these operational transactions are reported and reviewed/scrutinized by a manager or three.

Management by Exception is exactly that, managing the exceptions and not looking through the norms for exceptions. And that is what ExaMIn does, help the management to design and define norm values across a number of operational activities and transactions, thereby allowing the manager/supervisor, the freedom of not constantly reading reports for the sake of locating an exception to address. ExaMIn, alerts the manager of the deviation in operations, be it a shortage of quantity in the receipt of a Purchase Order or alert the due time for AR collections etc.