Entity Sizing and Scalability Guidelines
Use these guidelines to plan your CXone WFM deployment and configure WFM entities as your workforce grows. The guidelines describe supported scale, recommended configuration patterns, and considerations for large deployments.
Planning a Large Deployment
Start with your workforce size. Then review Scheduling Units, WEM skills, scheduling rules, and forecasting configuration. Use these guidelines to design an efficient deployment. Do not attempt to maximize every individual limit.
Quick Sizing Reference
Use these figures as a starting point when you plan your CXone WFM environment.
|
metric |
guideline |
|---|---|
| Agents per CXone WFM tenant | Up to 10,000 |
| Agents per Scheduling Unit | Up to 800 |
| WEM skills per tenant | Up to 125 |
| WEM skills assigned to an agent | Up to 12 |
Workforce and Skills
Use these guidelines to structure your workforce and skill model.
|
What you are sizing |
Guideline |
What this means |
|---|---|---|
| Agents per CXone WFM tenant | Up to 10,000 | Use this value as the overall workforce-size reference when you plan a CXone WFM tenant. |
| Agents per Scheduling Unit | Up to 800 | Keep the number of agents in each Scheduling Unit within the recommended size. |
| WEM skills per tenant | Up to 125 | Review your skill model regularly. Consolidate skills that represent the same workforce capability when appropriate. |
| WEM skills assigned to an agent | Up to 12 | Assign only the skills that an agent needs for forecasting, scheduling, and staffing. |
| ACD skills mapped to WEM skills | Up to 120 | Map multiple ACD skills to one WEM skill when those skills represent the same workforce capability. |
Forecasting Configuration
Use these guidelines when you configure historical data and generate forecasts.
|
configuration |
Guideline |
What this means |
|---|---|---|
| Historical data used for forecasting | 3–24 months | Select a historical period based on seasonality, data quality, and business requirements. |
| Forecast period | Use available forecast durations | Select a forecast duration that matches your planning horizon and the options available in CXone WFM. |
| Staffing parameters per forecasted skill | No fixed limit | Use the parameters required by your forecasting model. Avoid unnecessary complexity. |
| Forecast generation frequency | Plan workloads carefully for large environments | For large deployments, consider how often you generate forecasts and how many skills you include in each run. |
Scheduling Configuration
Use these recommendations to help manage schedule generation as your workforce grows.
|
configuration |
Guideline |
recommended approach |
|---|---|---|
| Weekly scheduling rules | Approximately 1 rule per 20 agents | For larger workforces, consolidate rules that have the same scheduling requirements. |
| Activity codes per daily rule | Up to 4 | Include activities such as breaks, lunch, meetings, or other scheduled activities in a rule. |
| Schedule start-time window | Limit to 2 hours | Keep the range of allowed shift start times within a focused window. This helps maintain efficient schedule generation. |
| Session-handling configurations | 1 | Use one session-handling configuration unless your business requirements require more than one. |
How to Use These Guidelines
-
Start with workforce size: Determine the number of agents that you expect to manage in CXone WFM.
-
Plan Scheduling Units: Distribute agents across Scheduling Units according to the recommended size.
-
Review your skill model: Keep WEM skills meaningful. Avoid unnecessary duplication.
-
Review scheduling rules: Consolidate rules that have the same requirements, especially in large deployments.
-
Plan forecasting workloads: Consider forecast frequency, historical data, and the number of skills included in each forecast.
Some values in this article are recommendations, not product limits. Use them as configuration guidelines to help maintain an efficient deployment. If your deployment exceeds these guidelines, contact NiCE for recommendations specific to your environment.