Exact software agents in erlang

I then divide this by the annual available staffed days for an FTE e. The number of FTEs are then multiplied by avg annual salary plus benefits to yield total annual agent salary expense. This approach assumes large team efficiency, and I believe is inaccurate for small call centers. I know it is a long time, but no one appears to have answered this. I think I have a solution but would like some other opinions.

I had a calculator that determined the number of agents needed based on 30 minute intervals as that was the period the call data came out of our MIS system. It is important to use the net available time rather than gross time that includes breaks. If an agent is employed 7h. Thus you divide your annual calls Offered or expected by your working days less say 15 days annual leave and say 6 days for sickness or other absenteeism — or whatever your absenteeism rate is this then gives you the average calls per agent per day they have worked.

I am effectively saying, for any agent answering a call during their working day, call arrival has a uniform random distribution in the hours that the agent is available to answer calls. I have not proved that Erlang-C is still applicable when the problem is re-stated this way, but I can see no reason why it should not be a reasonable approximation.

Work in the cloud without any worries The Exact Cloud is essentially a unified cloud infrastructure that offers the following services to Exact customers: The Exact Online platform runs on the Exact Cloud and provides financial and operational services to small businesses and their accountants.

Many of our Exact Globe and Exact Synergy customers have chosen to have their implementations hosted and fully managed on the Exact Cloud rather than deploying these solutions themselves. Our advanced back-up and failover mechanisms ensure that any unforeseen incidents have minimal impact on systems and application availability.

We also aim to minimize the number of scheduled maintenance windows and provide a real-time dashboard to inform customers of the status of all Exact Cloud operational systems and processes. We ensure high availability of our Exact Cloud. Two-factor authentication Exact provides an additional security layer for Exact Online users with two-factor authentication.

For example, v2 MIBs can be loaded into an agent that speaks v1 only. In order for an implementation to make full use of the enhanced SNMPv2 error codes, it is essential that the instrumentation functions always return SNMPv2 error codes, in case of error.

These are translated into the corresponding SNMPv1 error codes by the agent, if necessary. The common practice in these situations is to simple ignore any Counter64 objects, when sending a reply or a trap to an SNMPv1 manager. The figures in this section illustrate the steps involved in the development of an SNMP agent. The actual instrumentation functions are not needed at MIB compile time, only their names.

The binary output file produced by the compiler is read by the agent at MIB load time see the figure Starting the Agent. The instrumentation is ordinary Erlang code which is loaded explicitly or automatically the first time it is called. The Master Agent can be seen as a special kind of sub-agent. It implements the core agent functionality, UDP packet processing, type checking, access control, trap distribution, and so on.

From a user perspective, it is used as an ordinary sub-agent. Sub-agents are only needed if your application requires special support for distribution from the SNMP toolkit. A sub-agent can also be used if the application requires a more complex set transaction scheme than is found in the master agent. The sequence of steps shown is probably more complex than normal, but it illustrates the amount of functionality which is available. The following points should be noted:.

Most applications only need the Master Agent because an agent can have multiple MIBs loaded at the same time. Since applications tend to be transient they are dynamically loaded and unloaded , the management of these applications must be dynamic as well. For example, if we have an equipment MIB for a rack and different MIBs for boards, which can be installed in the rack, the MIB for a card should be loaded when the card is inserted, and unloaded when the card is removed.

In this agent system, there are two ways to dynamically install management information. The most common way is to load an MIB into an agent. The other way is to use a sub-agent, which is controlled by the application and is able to register and unregister itself.

A sub-agent can register itself for managing a sub-tree not to be mixed up with erlang:register. The sub-tree is identified by an Object Identifier. When a sub-agent is registered, it receives all requests for this particular sub-tree and it is responsible for answering them. It should also be noted that a sub-agent can be started and stopped at any time.

Compared to other SNMP agent packages, there is a significant difference in this way of using sub-agents. Other packages normally use sub-agents to load and unload MIBs in run-time.

In Erlang, it is easy to load code in run-time and it is possible to load an MIB into an existing sub-agent. It is not necessary to create a new process for handling a new MIB. Refer to the chapter Advanced Agent Topics in this User's Guide for more information about these topics. The communication protocol between sub-agents is the normal message passing which is used in distributed Erlang systems.

A context is a collection of management information accessible by an SNMP entity. An instance of a management object may exist in more than one context. An SNMP entity potentially has access to many contexts. Each managed object can exist in many instances within a SNMP entity.

We looked at a range of systems, including the major players with ERP packages. However, we concluded that we are still very satisfied with Exact and in combination with a number of custom solutions, we can continue for a number of years to come. As we need to register more information, Exact Synergy ensures we keep the administrative avalanche under control. Since the implementation of Exact Globe and Exact Synergy, we've been able to save time equivalent to 1. This is how Yogi Tea manages millions of bags of tea around the world.

Exact helps us to meet the strict quality requirements set by the FDA and other authorities. Services Contact Partners Careers Events. Cloud business software for SMEs and their accountants Numbers are the key to any business. View our products or contact us.