This is the first category in the Counts area and used to identify and hold an entire Roster Count strategy.
Important: A Count Strategy is attached to every position and sometimes also attached to the Region level of the organizational structure to include unassigned personnel in the count.
The minimum requirement is one strategy. The number of Count Strategies configured depend on your business requirements.
Separate count strategies must be configured when Counts within Count Groups change based on the day of the week, holiday, months, cycles, and so on. Because only one Count Group within a Count Strategy can be active before the application can move to the next Count Group.
For example, the application may contain Patrol and Traffic resources, Patrol’s manpower changes on Fridays and Saturdays, and Traffic’s manpower remains the same throughout the week.
In this example, use one Count Strategy with two Count Groups to denote a change in peak for Patrol. Use one Count Strategy and one Count Group that activates everyday of the week for Traffic.
Additional Count Strategies can be created to separate additional groups or nest a new Count within a Count Group that encompasses the same days of the week. Be sure not to nest a Count that is active on Fridays inside a Count Group that is only active on weekends because the system will not activate a false alarm.