How the Optimizer uses locations

During Series25 data preparation, your implementation team used the 25Live Administration Utility to create locations that could be assigned to classes and events, and specified each location’s hours of availability, and possibly dates/times each location is unavailable for assignment, known as “blackout dates.”

The Optimizer uses only a subset of the information from each location. For Optimizer processing, locations must contain data in each of the required fields listed below, and may contain data in each of the optional fields.


This location data...	Is used by the Optimizer to...
Location Name (required)	Identify the location.
Max Capacity (required)	Determine the maximum event head count that can be accommodated by the location.
Partition (required)	Determine the campus partition the location is in.
Hours of Availability (required)	Determine when events can be placed in the location.
Blackout Dates (optional)	Determine dates/times when events can’t be placed in the location.
Features (optional)	Identify the physical attributes of the location.
This location data...	Is used by the Optimizer to...
Default Layout Capacity (optional)	Determine the event head count that can be accommodated by the location’s default layout. If a default layout is specified for a location, the Optimizer uses the default layout's capacity during processing. If no default layout is specified, the Optimizer uses the location's maximum capacity.
Fill Ratio (optional)	Limit placement to only those events whose expected or registered head count meets or exceeds this seat fill percentage.

Location with required information used by the Optimizer circled

The Optimizer also uses any blackout dates that have been defined for a location. Defining blackout dates for a location prevents the Optimizer from placing an event in the location during dates/times the location is unavailable, such as when it is closed for repairs.