After calculating agent requirement for each job, POM ensures efficient utilization of agents while attaching agents to jobs. The agent allocation algorithm performs following checks before attaching an agent to a job:

• Searches jobs with skills that match the skills of an agent.

• Calculates the agents requirement for each job.

• Checks the skill level of agents.

• Checks the priority of the job.

• Checks the job ID.

• Checks the action ID.

POM does not reserve agents for jobs and allows setting the minimum agents to 0. So, the agents are released when they are not required for a job ensuring efficient agent utilization when jobs are snoozed.

At the time of releasing agents from a job and assigning it to another job, POM considers the skills and proficiency of the agents. For example, if there are 2 agents in a job, and if the agent manager needs to release one agent, then the agent manager releases the least proficient agent. However, this behavior is not guaranteed in the system.

Also, the agent allocation algorithm gives preference to the priority of the job before attaching an agent to it. The job cannot acquire a license unless an agent is attached to it. For example, 2 jobs are started, job1 has priority 8 and job2 has priority 2. Each job has set a minimum of 1 agent and maximum of 30 agents as the default criteria. Agent allocation algorithm assigns the agents first. The agent allocation will be 8 agents for job1 and 2 agents for job2 as shown in the following table:

License allocation

POM allocates licenses to the job only when the agents are logged in and are attached to a job, and releases the licenses from the job whenever the agents are detached from the job. When the job snoozes, POM releases all the agents immediately along with the licenses. The license goes back to the license pool.