How to calculate the number of Altitude uCI Server processes

Calculate the number of required Altitude uCI Server processes depending on the workload of your contact center.

Attention

The following calculated number of Altitude uCI Server processes are guides for small contact centers with simple activity. For example, simple inbound and outbound campaigns. For large contact centers or contact centers with complex activities, for example, workflow processes, integrations with the Integration Server, or complex routing, please contact Enghouse Customer Support for a better tuning of the Altitude uCI Server processes.

DOCM

Calculate the number of DOCM processes as follows:

n_DOCM = 2 + max ( n_agents_n_conn n_conn_factor , n_working_agents script_change_factor ) + n_reports 5

  • n_agents_n_conn: Maximum number of working agents handling email, instant messaging, workflow tasks, or other non-connected interactions.
  • n_conn_factor: A number between 15 and 20. Select 20 for a low number of concurrent non-connected interactions or 15 for a high number of concurrent non-connected interactions.
  • n_working_agents: Maximum number of simultaneous working agents.
  • script_change_factor: A number between 30 and 50. Select 30 if the scripts of the contact center campaigns change frequently, and 50 if the scripts of the contact center campaigns do not change frequently.
  • n_reports: Maximum number of concurrently generated reports.

LPTS

Calculate the number of LPTS processes as follows:

n_LPTS = 2 + n_reports + n_sup_operations

  • n_reports: Maximum number of concurrently generated reports.
  • n_sup_operations: Maximum number of concurrent bulk operations. For example, resubmit contacts, update contacts, or load contacts.

SAM

Calculate the number of SAM processes as follows:

n_SAM = 3 + n_working_agents n_agents_factor

  • n_working_agents: Maximum number of simultaneous working agents.
  • n_agents_factor: A number between 10 and 20. Select 20 for a low number of concurrent interactions and small complexity agent scripts and 10 for a high number of concurrent interactions or complex agent scripts.

SQL

Calculate the number of SQL processes as follows:

n_SQL = 2 + max ( 3 * n_working_agents 2 * n_agents_factor , 3 * n_working_supervisors n_supervisors_factor )

  • n_working_agents: Maximum number of simultaneous working agents.
  • n_agents_factor: A number between 5 and 10. Select 10 if the agent script has a low usage of SQL queries and cursors, and 5 if the agent script has a high usage of SQL queries and cursors.
  • n_working_supervisors: Maximum number of simultaneous working supervisors.
  • n_supervisors_factor: A number between 3 and 5. Select 5 for a low number of entities that supervisors monitor and 3 for a high number of entities that supervisors monitor.

SS

Calculate the number of SS processes as follows:

n_SS = 2 + n_working_supervisors n_supervisors_factor

  • n_working_supervisors: Maximum number of simultaneous working supervisors.
  • n_supervisors_factor: A number between 5 and 10. Select 10 for a low number of entities that supervisors monitor and 5 for a high number of entities that supervisors monitor.

TMAN

Calculate the number of TMAN processes as follows:

n_TMAN = 5 + n_working_agents n_agents_factor + n_working_supervisors n_supervisors_factor

  • n_working_agents: Maximum number of simultaneous working agents.
  • n_agents_factor: A number between 10 and 15. Select 15 for a low number of concurrent interactions and 10 for a high number of concurrent interactions.
  • n_working_supervisors: Maximum number of simultaneous working supervisors.
  • n_supervisors_factor: A number between 3 and 5. Select 5 for a low number of entities that supervisors manage or monitor and 3 for a high number of entities that supervisors manage or monitor.

TSRV

Calculate the number of TSRV processes as follows:

n_TSRV = max ( n_cores_cpu , n_trace_processes trace_factor )

  • n_cores_cpu: Number of physical cores of one CPU on the Altitude uCI Server machine.
  • n_trace_processes: Number of Altitude uCI Server processes with enabled trace files.
  • trace_factor: A number between 5 and 10. Select 10 if the Altitude uCI Server writes trace files with a low detail trace level (Medium and High importance or High importance), and 5 if the Altitude uCI Server writes trace files with a high detail trace level (All debugging importance or Low, medium and high importance).