Waste collection analysis layer

The Waste Collection solver is a use-case-specific Vehicle Routing Problem (VRP) algorithm designed for a fleet of vehicles that are collecting curbside residential waste and disposing of it at the landfill or transfer station. It is intended for planning a single district to collect from every household for a specific collection day.

For the households (stops) that need to have their waste collected in a municipality, the waste collection solver determines which truck (route) will collect the location and the sequence to visit them. The goal is to best service the stops by producing geographically clustered routes and minimize the overall operating costs for the fleet of vehicles.

The Network Analyst Vehicle Routing Problem solver and Waste Collection solver both allow a fleet of vehicles to pick up at customer locations and empty the vehicles as needed throughout the day. The Vehicle Routing Problem solver has lots of flexibility and can model many different constraints, but the algorithm is also limited by this flexibility. The Waste Collection solver supports a subset of the constraints, but those capabilities are targeted toward residential waste collection for better quality and performance.

Note:

Minimum requirements for Waste Collection solver are one stop, one depot, and one route. Each stop, depot, and route needs a unique name. The start time and maximum total time are required for each route and can be specified using the StartTime and MaxTotalTime attributes on the Routes feature class. These two values can alternatively be specified as Default Route Start Time of Day and Max Total Time layer properties on the Waste Collection Layer tab. Additionally a route must specify the Start Depot Name and End Depot Name fields. Similarly, the collection mode is required for each stop and can be specified using the CollectionMode attribute on the Stops feature class, or specifying the Collection Mode layer property on the Waste Collection Layer tab.

Note:

Pay particular attention to the travel mode for the Waste Collection solver. Garbage trucks have a unique set of requirements that should be considered when setting the travel mode. These decisions can influence if residential locations are reachable or not.

Learn more about creating a network analysis layer

Learn more about the Waste Collection solver

Stops

The Stops feature class stores the stops that are part of a waste collection analysis layer. These are the residential locations where waste is collected, whether garbage, recycling, yard waste, and so on.

The stops can track the quantity to be picked up for two separate fractions at a time such as yard waste and paper. These two fractions can be tracked by the number of bins at the location, the weight of the waste, or the volume of the waste.

A stop can have a service time, which is the time needed to complete the work for collecting the waste. The service time can be the same for all stops, or it can be unique for each stop. For example, it could take twice as long to collect a stop that has two bins verses a stop that has a single bin.

Although we allow modeling of stops for every household separately, internally we aggregate them per street edge to require the entire edge to be collected by the same route. See collection edges for a more detailed description of collection edges. This is particularly important when preassigning stops to routes and adjusting the collection mode at the stop level.

Stops: Input fields

The input fields for the Stops feature class are described in the following table:

Input fields	Description	Data type
Name	The name of the stop. This is a required field The name must be unique. Stop names are case sensitive and cannot be empty, even if the stop is excluded from the solve operation.	Text
ServiceTime	This property specifies the amount of time that will be spent at the network location when the route visits it; that is, it stores the impedance value for the network location. A zero or null value indicates that the network location requires no service time. The unit for this field value is specified by the Time Units property of the analysis layer.	Double
Bins_1	The number of waste bins for fraction 1 to collect at this network location.	Double
Weight_1	The physical weight of the waste for fraction 1 to collect at this network location. Any weight units can be used for this value as long as the same units are used for all weight fields.	Double
Volume_1	The volume of waste for fraction 1 to collect at this network location. Any volume units can be used for this value as long as the same units are used for all volume fields.	Double
Bins_2	The number of waste bins for fraction 2 to collect at this network location.	Double
Weight_2	The physical weight of the waste for fraction 2 to collect at this network location. Any weight units can be used for this value as long as the same units are used for all weight fields.	Double
Volume_2	The volume of waste for fraction 2 to collect at this network location. Any volume units can be used for this value as long as the same units are used for all volume fields.	Double
CollectionMode	Specifies if the location is picked up by a vehicle servicing both sides of the street at once or by a vehicle servicing the two sides separately with different passes down the street edge. The possible values are listed below (use the name, not the code in parenthesis): Null—The stop does not have a specified collection mode. This is the default value. (1) One side—The two sides of the street on which this stop is located are collected separately with different passes down the street edge. (2) Both sides—Both sides of the street on which this stop is located are collected at once with a single pass down the street edge. Either this field or the layer property Collection Mode must be populated. If this field is left null the Collection Mode will be used for the stop. All stops on a street edge must have the same CollectionMode value.	Long
AnchorRule	Specifies the anchoring rule for the stop, indicating that it must be the first or last stop on a route. The possible values are listed below (use the name, not the code in parenthesis): Null—The stop does not have an anchor constraint and can be sequenced first, last, or anywhere in between. This is the default value. (1) First—The stop must be the first stop on the route. (2) Last—The stop must be the last stop on the route. If the stop is additionally constrained to a specific route, that can be controlled using the AssignmentRule field. A single stop on a collection edge is sufficient to indicate the edge should be collected first/last. If more than one stop on a collection edge indicates first/last, they must match.	Long
AssignmentRule	Specifies the rule for assigning the stop to a route. The possible values are listed below (use the name, not the code in parenthesis): Null—The solver ignores the route preassignment (if any) for the stop during the solve operation. It assigns a route to the stop to minimize the overall value of the objective function. This is the default value. (1) Preserve route and relative sequence—The solver must always assign the stop to the preassigned route at the preassigned relative sequence during the solve operation. If this assignment rule can't be followed, it results in a violation. With this setting, only the relative sequence is maintained, not the absolute sequence. For example, there are two stops: A and B. They have sequence values of 2 and 3, respectively. The sequence values for A and B may change after solving because other stops and renewal visits can be sequenced before, between, or after A and B. However, B cannot be sequenced before A. (2) Preserve route—The solver must always assign the stop to the preassigned route during the solve operation. If a sequence value is provided, it will be used for the initial construction of the route. If the stop cannot be assigned to the specified route, it results in a violation. (3) Unassign—The stop will be removed from the assigned route. A single stop on a collection edge is sufficient to indicate the edge should follow the Assignment Rule. If more than one stop on a collection edge indicates an Assignment Rule they must match.	Long

Stops: Input/output fields

The input/output fields for the Stops feature class are described in the following table:

Input/output fields	Description	Data type
RouteName	The name of the route to which the network location is assigned. As an input field, this field is used to preassign a stop to a specific route. It can contain a null value, indicating that the location is not preassigned to any route, and the solver determines the best possible route assignment for the location. If this is set to null, the sequence field must also be null. The RouteName field is a foreign key to the Name field in the Routes sublayer. After a solve operation, if the location is routed, the RouteName field contains the name of the route that the location is assigned to.	Text
Sequence	The sequence of the location on its assigned route. As an input field, this field is used to specify the relative sequence for a location on the route. This field can contain a null value specifying that the location can be placed anywhere along the route. The input sequence values are non-negative and unique for each route (shared across renewal visits and stops) but do not need to start from 1 or be contiguous. After a solve operation, the Sequence field contains the sequence value of the location on its assigned route. Output sequence values for a route are shared across renewal visits and stops. The sequences start from 1 for the first stop on the route.	Long
Network location fields SourceID SourceOID PosAlong SideOfEdge SnapX SnapY SnapZ DistanceToNetworkInMeters	Together, these fields describe the point on the network where the object is located. Learn more about locating inputs on a network	Long Long Double Long Double Double Double Double

Stops: Output fields

The output fields for the Stops feature class are described in the following table:

Output fields	Description	Data type
Status	Indicates the status of the point with respect to its location on the network and the outcome of the analysis. The possible values are the following (use the name, not the code in parenthesis): (0) OK—The point was located on the network. (1) Not Located—The point was not located on the network and was not included in the analysis. (2) Network element not located—The network element identified by the point's network location fields cannot be found. This can occur when a network element where the point should be was deleted, and the network location was not recalculated. (3) Element not traversable—The network element that the point is located on is not traversable. This can occur when the element is restricted by a restriction attribute. (4) Invalid Field Values—Field values fall outside a range or coded-value domain. For example, a negative number exists where positive numbers are required. (5) Not reached—The point cannot be reached by the solver. The point may be on a separate, disconnected area of the network from the other inputs, or barriers or restrictions prevent travel to or from the point. (6) Time window violation—The point could not be reached within the designated time windows. This status only applies to network analysis types that support time windows. (7) Not located on closest—The closest network location to the point is not traversable because of a restriction or barrier, so the point has been located on the closest traversable network feature instead. If time windows are used and the route arrives early or late, the value changes to (6) Time window violation.	Long
ViolatedConstraint_1 ViolatedConstraint_2 ViolatedConstraint_3 ViolatedConstraint_4	These fields contain a summary of violated constraints and are set after a solve operation. Each field will contain one violation. If a stop has more than one violation, the next ViolatedConstraint_* field will be used. The possible values are the following (use the name, not the code in parenthesis): (1) Capacities exceeded —The preassigned stops cannot be assigned to the route since assigning the stops will exceed the total route capacity as specified by the route's TotalBin_*, TotalWeight_*, and TotalVolume_* field values. (2) MaxTotalTime exceeded—The travel time from the start depot to the end depot, plus the service and wait times at both depots, plus any break exceeds the total time for the route as specified by the route's MaxTotalTime field value. (4) MaxTotalDistance exceeded—The travel distance from the start depot to the end depot exceeds the total travel distance for the route as specified by the route's MaxTotalDistance field value. (10) Unreachable—A preassigned stop is located on a network element that cannot be reached by the route. (12) Cannot insert required renewal—A route exceeds its capacity and needs to visit a route renewal; however, the associated route renewal has a null sequence value in the presence of preassigned stops and cannot be inserted anywhere without introducing other violations. Note: The violated constraint field value of an unrouted stop may or may not describe all its violations. If the violation is severe enough to immediately exclude the stop from further consideration, the solver does so, which prevents any other violations from being discovered for that stop. If a violation is encountered that doesn't automatically stop a solution from being generated, the violation is noted in violated constraint fields, and the solver continues to consider the stop. Any further violations such as these are added to the violated constraint fields until either the solver finds a violation that prematurely stops the solve process for that particular stop, or the solver finds an overall solution to the problem.	Long
RouteLineID	The travel distance from the previous stop to the current stop. The unit for this field value is specified by the Distance Units property of the analysis layer.	Long

Depots

The Depots feature class stores the depots that are part of a given waste collection analysis layer.

A depot is a location that a vehicle departs from at the beginning of its workday and returns to at the end of the workday. For the Waste Collection solver, the routes must all start at the same depot location and must all end at the same depot location. However, the start and end depot locations can be different.

Depots: Input fields

The input fields for the Depots feature class are described in the following table:

Input fields	Description	Data type
Name	The name of the depot. This is a required field. The StartDepotName and EndDepotName fields on the Routes sublayer reference the names you provide here. Depot names are case sensitive and must be nonempty and unique.	Text

Depots: Input/Output field

The input/output fields for the Depots feature class is described in the following table:

Input/Output fields	Description	Data type
Network location fields SourceID SourceOID PosAlong SideOfEdge SnapX SnapY SnapZ DistanceToNetworkInMeters	Together, these fields describe the point on the network where the object is located. Learn more about locating inputs on a network	Long Long Double Long Double Double Double Double

Depots: Output fields

The output fields for the Depots feature class is described in the following table:

Output fields	Description	Data type
Status	Indicates the status of the point with respect to its location on the network and the outcome of the analysis. The possible values are the following (use the name, not the code in parenthesis): (0) OK—The point was located on the network. (1) Not Located—The point was not located on the network and was not included in the analysis. (2) Network element not located—The network element identified by the point's network location fields cannot be found. This can occur when a network element where the point should be was deleted, and the network location was not recalculated. (3) Element not traversable—The network element that the point is located on is not traversable. This can occur when the element is restricted by a restriction attribute. (4) Invalid Field Values—Field values fall outside a range or coded-value domain. For example, a negative number exists where positive numbers are required. (5) Not reached—The point cannot be reached by the solver. The point may be on a separate, disconnected area of the network from the other inputs, or barriers or restrictions prevent travel to or from the point. (6) Time window violation—The point could not be reached within the designated time windows. This status only applies to network analysis types that support time windows. (7) Not located on closest—The closest network location to the point is not traversable because of a restriction or barrier, so the point has been located on the closest traversable network feature instead. If time windows are used and the route arrives early or late, the value changes to (6) Time window violation.	Long

Routes

The Routes feature class stores the routes that describe vehicle and driver characteristics.

A route must specify the start time and the maximum work time and can optionally also specify start or end depot service times, operating constraints, vehicle capacities, and various constraints on a driver's workday.

Note:

The Waste Collection solver tries to minimize the number of routes used instead of distributing the work evenly among all provided routes.

Routes: Input fields

The input fields for the Routes feature class are described in the following table:

Field	Description	Data type
Name	The name of the route. This is a required field. This field is the primary key and is used as a foreign key in the Stops, Route Lines, Route Renewals, and Renewal Visits sublayers. Route names are case sensitive and cannot be empty, even if the route is not part of the solve operation. The name must be unique.	Text
StartDepotName	The name of the starting depot for the route. This field is a foreign key to the Name field in the Depots sublayer. This is a required field.	Text
EndDepotName	The name of the ending depot for the route. This field is a foreign key to the Name field in the Depots sublayer. This is a required field.	Text
StartDepotServiceTime	The service time at the starting depot. This can be used to model the time spent loading the vehicle. This field can contain a null value; a null value indicates zero service time. The unit for this field value is specified by the Time Units property of the analysis layer. The service times at the start and end depots are fixed values (the StartDepotServiceTime and EndDepotServiceTime field values) and do not take into account the actual load for a route. For example, the time taken to load a vehicle at the starting depot may depend on the size of the stops. The depot service times can be assigned values corresponding to a full truckload or an average truckload, or you can make a time estimate.	Double
EndDepotServiceTime	The service time at the ending depot. This can be used to model the time spent unloading the vehicle. This field can contain a null value; a null value indicates zero service time. The unit for this field value is specified by the Time Units property of the analysis layer. The service times at the start and end depots are fixed values (the StartDepotServiceTime and EndDepotServiceTime field values) and do not take into account the actual load for a route. For example, the time taken to load a vehicle at the starting depot may depend on the size of the stops. The depot service times can be assigned values corresponding to a full truckload or an average truckload, or you can make a time estimate.	Double
StartTime	The starting time for the route. Either this field or the layer property Default Route Start Time of Day must be populated. If this field is left null, the default value set in the Default Route Start Time of Day will be used for the route.	Time Only
MaxBins_1	The maximum number of waste bins for fraction 1 the vehicle can collect before it must be emptied. If using renewals, this is a constraint on the capacity of the vehicle and not the route. When this limit is reached, the route will go to the renewal location and empty the vehicle. If there is still time in the driver's workday, then the route will continue collecting after the renewal visit.	Double
MaxWeight_1	The maximum physical weight for fraction 1 the vehicle can collect before it must be emptied. Any weight units can be used for this value as long as the same units are used for all weight fields. If using renewals, this is a constraint on the capacity of the vehicle and not the route. When this limit is reached, the route will go to the renewal location and empty the vehicle. If there is still time in the driver's workday, then the route will continue collecting after the renewal visit.	Double
MaxVolume_1	The maximum volume for fraction 1 the vehicle can collect before it must be emptied. Any volume units can be used for this value as long as the same units are used for all volume fields. If using renewals, this is a constraint on the capacity of the vehicle and not the route. When this limit is reached, the route will go to the renewal location and empty the vehicle. If there is still time in the driver's workday, then the route will continue collecting after the renewal visit.	Double
MaxBins_2	The maximum number of waste bins for fraction 2 the vehicle can collect before it must be emptied. If using renewals, this is a constraint on the capacity of the vehicle and not the route. When this limit is reached, the route will go to the renewal location and empty the vehicle. If there is still time in the driver's workday, then the route will continue collecting after the renewal visit.	Double
MaxWeight_2	The maximum physical weight for fraction 2 the vehicle can collect before it must be emptied. Any weight units can be used for this value as long as the same units are used for all weight fields. If using renewals, this is a constraint on the capacity of the vehicle and not the route. When this limit is reached, the route will go to the renewal location and empty the vehicle. If there is still time in the driver's workday, then the route will continue collecting after the renewal visit.	Double
MaxVolume_2	The maximum volume for fraction 2 the vehicle can collect before it must be emptied. Any volume units can be used for this value as long as the same units are used for all volume fields. If using renewals, this is a constraint on the capacity of the vehicle and not the route. When this limit is reached, the route will go to the renewal location and empty the vehicle. If there is still time in the driver's workday, then the route will continue collecting after the renewal visit.	Double
OvertimeStartTime	The duration of regular work time before overtime computation begins. This field can contain null values; a null value indicates that overtime does not apply. The unit for this field value is specified by the Time Units property of the analysis layer. For example, if the driver is to be paid overtime when the total route duration extends beyond eight hours, OvertimeStartTime is specified as 480 (8 hours * 60 minutes/hour), given the time units are minutes. The OvertimeStartTime value should be greater than zero and less than the MaxTotalTime value.	Double
MaxTotalTime	The maximum allowable route duration. The route duration includes travel times as well as service and wait times at stops, depots, and renewals. Either this field or the layer property Max Total Time must be populated. If this field is left null, the default value set in the Max Total Time property will be used for the route. The unit for this field value is specified by the Time Units property of the analysis layer.	Double
MaxTotalDistance	The maximum allowable travel distance for the route. This field can contain null values; a null value indicates that there is no constraint on the maximum allowable travel distance. The unit for this field value is specified by the Distance Units property of the analysis layer.	Double
AssignmentRule	Specifies whether the route can be used when solving the problem. This field is constrained by values listed below (use the name, not the code in parenthesis): Null—The route is open to new stops. This is the default value. (1) Closed—The route will not accept new stops, but it can be re-sequenced or have the outputs updated. (2) Exclude—The route is excluded from the solve operation. The output for this route will not be updated. The stops with the corresponding route will also be excluded from the route, and the output from those stops will not be updated.	Long

Routes: Output fields

The output fields for the Routes feature class are described in the following table:

Output fields	Description	Data type
ObjectID	The object ID of the feature.	ObjectID
ViolatedConstraint_1 ViolatedConstraint_2 ViolatedConstraint_3 ViolatedConstraint_4	Describes constraints violated by the route. The constraints are described below. (1) Capacities exceeded—The preassigned stops cannot be assigned to the route since assigning the stops will exceed the total route capacity as specified by the route's TotalBin_*, TotalWeight_*, and TotalVolume_* field values. (2) MaxTotalTime exceeded—The travel time from the start depot to the end depot plus the service and wait times at both depots exceeds the total time for the route as specified by the route's MaxTotalTime field value. (4) MaxTotalDistance exceeded—The travel distance from the start depot to the end depot exceeds the total travel distance for the route as specified by the route's MaxTotalDistance field value. (10) Unreachable—A preassigned stop is located on a network element that cannot be reached by the route. (12) Cannot insert required renewal—A route exceeds its capacity and needs to visit a route renewal; however, the associated route renewal has a null sequence value in the presence of preassigned stops and cannot be inserted anywhere without introducing other violations.	Long
StopCount	The number of stops serviced by this route.	Long
RenewalCount	The number of renewal visits needed by this route.	Long
TotalBins_1	The total number of bins for fraction 1 serviced by this route.	Double
TotalWeight_1	The total physical weight of waste for fraction 1 collected by this route.	Double
TotalVolume_1	The total volume of waste for fraction 1 collected by this route.	Double
TotalBins_2	The total number of bins for fraction 2 serviced by this route.	Double
TotalWeight_2	The total physical weight of waste for fraction 2 collected by this route.	Double
TotalVolume_2	The total volume of waste for fraction 2 collected by this route.	Double
TotalTime	The total route duration. This includes travel times as well as service and wait times at stops, renewals, and starting and ending depots. The value is in the units specified by the Time Units property of the analysis layer. This includes the travel time as well as the service time for stops, depots, and renewals.	Double
TotalTravelTime	The total travel time for the route. The value is in the units specified by the Time Units property of the analysis layer.	Double
TotalStopServiceTime	The total service time spent at all stops on the route. The value is in the units specified by the Time Units property of the analysis layer.	Double
TotalDistance	The total travel distance for the route. The value is in the units specified by the Distance Units property of the analysis layer.	Double
EndTime	The ending time of the route. The route ends upon completion of service at the ending depot. This end time reflects the travel times that were used during the optimization by the solver.	Time Only

Renewals

The Renewals feature class stores the renewals that are a part of a given waste collection analysis layer.

A renewal is where the vehicle is emptied allowing the route to continue collecting such as a landfill or transfer station. If using renewals the location will be visited at the end of the work day before returning to the depot. For the Waste Collection solver, each route must be assigned to a single renewal location. Visiting different renewal locations for fraction one and two is not yet supported.

Renewals: Input fields

The input fields for the Renewals feature class are described in the following table:

Input fields	Description	Data type
Name	The name of the renewal. This field is a primary key and is used as a foreign key in the RouteRenewals and RenewalVisits sublayers. Renewal names are case sensitive and must be nonempty and unique.	Text
Fraction	Indicates the fraction this renewal location accepts. This is not yet supported. If a value other than null is indicated it will be ignored with a warning that fractions are not yet supported for Renewal locations.	Long

Renewals: Input/Output fields

The input/output fields for the Renewals feature class are described in the following table:

Input/Output fields	Description	Data type
Network location fields SourceID SourceOID PosAlong SideOfEdge SnapX SnapY SnapZ DistanceToNetworkInMeters	Together, these fields describe the point on the network where the object is located. Learn more about locating inputs on a network	Long Long Double Long Double Double Double Double

Renewals: Output fields

The output fields for the Renewals feature class are described in the following table:

Output fields	Description	Data type
Status	Indicates the status of the point with respect to its location on the network and the outcome of the analysis. The possible values are listed below: (0) OK—The point was located on the network. (1) Not Located—The point was not located on the network and was not included in the analysis. (2) Network element not located—The network element identified by the point's network location fields cannot be found. This can occur when a network element where the point should be was deleted, and the network location was not recalculated. (3) Element not traversable—The network element that the point is located on is not traversable. This can occur when the element is restricted by a restriction attribute. (4) Invalid Field Values—Field values fall outside a range or coded-value domain. For example, a negative number exists where positive numbers are required. (5) Not reached—The point cannot be reached by the solver. The point may be on a separate, disconnected area of the network from the other inputs, or barriers or restrictions prevent travel to or from the point. (6) Time window violation—The point could not be reached within the designated time windows. This status only applies to network analysis types that support time windows. (7) Not located on closest—The closest network location to the point is not traversable because of a restriction or barrier, so the point has been located on the closest traversable network feature instead. If time windows are used and the route arrives early or late, the value changes to (6) Time window violation	Long

RouteRenewals

The Route Renewal table specifies the renewal location that the route in a waste collection analysis layer can visit to empty the vehicle.

Route renewals pairs the routes with the renewal locations they are able to visit. Specifically, a route renewal analysis object links a route object to a renewal object. The relationship indicates the route can be emptied at the associated renew location.

Consider the following rules and options when working with route renewals:

• The renewal location can be different from the start or end depot.
• Each route can have exactly one renewal location.
• A renewal location may be used up to three times by a single route.
• If given, a renewal location, it will always be visited at the end of the workday before returning to the depot.

RouteRenewals: Input fields

The input fields for the RouteRenewals table are described in the following table:

Input fields	Description	Data type
RouteName	The name of the route this renewal applies to. This field can't contain a null value and is a foreign key to the Name field in the Routes sublayer.	Text
RenewalName	The name of the renewal where the truck can be unloaded. This field can't contain a null value and is a foreign key to the Name field in the Renewals sublayer.	Text
ServiceTime	This property specifies the amount of time that will be spent at the network location when the route visits it; that is, it stores the impedance value for the network location. A zero or null value indicates that the network location requires no service time. The value is in the units specified by the Time Units property of the analysis layer. The time taken to unload a vehicle at a renewal depot may depend on the size of the vehicle and how full or empty the vehicle is. However, the service time for a route renewal is a fixed value and does not take into account the actual load. As such, the renewal service time should be given a value corresponding to a full truckload, an average truckload, or another time estimate of your choice.	Double

RenewalVisits

A renewal visit is created every time the route goes to the renewal location to empty the vehicle. The quantity of waste unloaded from a vehicle at the renewal is recorded in the properties of a renewal visit. Additional information that is useful in interpreting a waste collection problem solution is also included.

If you want to fully define a route's sequence of stops and renewals, set the AssignmentRule field in the Stops sublayer to Preserve route and relative sequence and set a value for the RouteName, RenewalName, and Sequence fields for row in the RenewalVisits sublayer. Only three renewal visits per route is supported. If more are provided the solve will fail.

RenewalVisits: Input/Output fields

The input/output fields for the Renewal Visits table are described in the following table:

Input/Output fields	Description	Data type
RouteName	The name of the route that this renewal applies to. This field can't contain a null value and is a foreign key to the Name field in the Routes sublayer.	Text
RenewalName	The name of the renewal where the truck was unloaded. This field can't contain a null value and is a foreign key to the Name field in the Renewals sublayer.	Text
Sequence	The sequence of the visited renewal along the route.	Long

RenewalVisits: Output fields

Field	Description	Data type
ObjectID	The object ID of the feature.	ObjectID
ArriveTime	The arrival time at the renewal.	Time Only
DepartTime	The departure time from the renewal.	Time Only
UnloadedBins_1	The number of bins collected for fraction 1 unloaded at the renewal.	Double
UnloadedWeight_1	The physical weight of waste for fraction 1 unloaded at the renewal.	Double
UnloadedVolume_1	The volume of waste for fraction 1 unloaded at the renewal.	Double
UnloadedBins_2	The number of bins collected for fraction 2 unloaded at the renewal.	Double
UnloadedWeight_2	The physical weight of waste for fraction 2 unloaded at the renewal.	Double
UnloadedVolume_2	The volume of waste for fraction 2 unloaded at the renewal.	Double

RouteLines

The Route Lines describe the paths taken through the network to visit the stops. These lines indicate for each segment if it is for collecting or just traversing to the next location.

Note:

This is an output-only network analysis sublayer. Route lines are created strictly during the solve operation; therefore, the sublayer is always empty before the solve process.

RouteLines: Output fields

The output fields for the Route Lines feature class are described in the following table:

Field name	Description	Data type
ObjectID	The object ID of the feature.	ObjectID
RouteName	The name of the route with which this route segment is associated. The RouteName field is a foreign key to the Name field in the Routes sublayer.	Text
CollectionSequence	The sequence of the route's collection segments.	Long
Activity	Indicates whether the driver collected bins while traversing the route segment. The constraints are described below. (1) Collect Both Sides—The driver collects bins from both sides of the street while traversing the route segment. (2) Collect Left Side—The driver collects bins from the left side of the street while traversing the route segment. (3) Collect Right Side—The driver collects bins from the right side of the street while traversing the route segment. (4) Stem—The driver traverses the route segment going from the depot to the first stop, from a stop to the renewal, or from the renewal to a stop or a depot. (5) Traverse—The driver traversed the route segment to get from one place to another without collecting bins.	Long
ArriveTime	The time the route starts traversing this route segment. Times are shown in the local time of the start depot location.	Time Only
DepartTime	The time the route finishes traversing this route segment. Times are shown in the local time of the start depot location. For collection segments the depart time will also include the service time of stops that are visited on this route segment. However, for stem segments the service time at the renewal or depot is not included because that is accounted for at the location and not on the route segment.	Time Only
StopCount	The number of stops from which to collect waste on this route segment. Null if no waste is to be collected.	Long
Bins_1	The number of bins for fraction 1 to collect on this route segment. If the route traverses this route segment without collecting waste, this field will be null.	Double
Weight_1	The physical weight of waste for fraction 1 to collect on this route segment. If the route traverses this route segment without collecting waste, this field will be null.	Double
Volume_1	The volume of waste for fraction 1 to collect on this route segment. If the route traverses this route segment without collecting waste, this field will be null.	Double
Bins_2	The number of bins for fraction 2 to collect on this route segment. If the route traverses this route segment without collecting waste, this field will be null.	Double
Weight_2	The physical weight of waste for fraction 2 to collect on this route segment. If the route traverses this route segment without collecting waste, this field will be null.	Double
Volume_2	The volume of waste for fraction 2 to collect on this route segment. If the route traverses this route segment without collecting waste, this field will be null.	Double
ReportGrouping	It is used to group RouteLines in the report to allow for close up maps for each group. It has no relevance on the solution.	Long

Point, line, and polygon barriers

Barriers temporarily restrict, add impedance to, and scale impedance on parts of the network. When a new network analysis layer is created, the barrier classes are empty. They are populated only when you add objects into them—but adding barriers is not required.

Barriers are available in all network analysis layers and are described in a separate topic.

Learn more about barriers

Waste collection analysis layer properties

The following subsections list parameters you can set on the analysis layer. They are on the Waste Collection Layer tab, which is available only if the waste collection analysis layer or one of its sublayers is selected in the Contents pane.

Analysis

Perform analysis on the waste collection layer using the Run tool.

Run

Once you load input features and set analysis properties, click the Run button to run the analysis. indicates the network analysis layer is referencing a local network data source.

Input Data

Use the options in the Input Data section to import the input features to participate in the analysis.

Import Stops

Click the Import Stops button to load features from another data source, such as a point feature layer, into the Stops feature class.

Import Depots

Click the Import Depots button to load features from another data source, such as a point feature layer, into the Depots feature class.

Import Routes

From the drop-down list, you can choose to import the routes or add routes.

Note:

By default, the Import Routes tool is visible on the ribbon. If you select Add Routes from the drop-down menu, the selected tool will be shown on the ribbon.

• Import Routes —Use this to load features from another data source, such as a line feature layer or a stand-alone table, into the Routes feature class.
• Add Routes —Use this to create multiple routes at once using the Add Fleet Routing Routes geoprocessing tool.

Import Barriers

Use the Import Point Barriers , Import Line Barriers , or Import Polygon Barriers buttons to load features from another data source, such as another feature layer, into one of the barriers feature classes (point barriers, line barriers, or polygon barriers).

Import Renewals

From the drop-down list, you can choose to import the renewals, route renewals, or renewal visits.

Note:

By default, the Import Renewals tool is visible on the ribbon. If you select any other tool to use from the drop-down menu, the selected tool will be shown on the ribbon.

• Import Renewals—Use this tool to load features from another data source, such as a point feature class, into the Renewals sublayer.
• Import Route Renewals—Use this tool to load features from another data source, such as a feature class or a stand-alone table, into the Route Renewals table.
• Import Renewal Visits—Use this tool to load features from another data source, such as a point feature class, into the Renewal Visits sublayer.

Create Features

Use the Create Features button to open the Create Features pane. Select from the available templates to create features in the current map.

Travel Settings

Use the options in the Travel Settings section to specify the travel mode.

Mode

Use the Mode drop-down list to specify a travel mode, which is a group of settings that model the movement of pedestrians, cars, trucks, or another travel mode. The choices available in the drop-down list depend on the travel modes that are configured on the network data source that the network analysis layer is referencing.

This is particularly important for Waste Collection as garbage trucks are often allowed to travel on streets that are not advisable for personal vehicles, such as private roads, through traffic prohibited, and traversing gates. Often the U-turn policy is to only allow a garbage truck to make a U-turn at the end of a dead-end street.

Note:

Only the travel modes that have a time-based impedance attribute are shown for a waste collection analysis layer. The travel mode must also allow making a u-turn at a dead-end.

Time Units

These are the time units used by the temporal fields of the analysis layer's sublayers and tables. The following options are available from the drop-down list:

• Seconds
• Minutes
• Hours
• Days

Distance Units

These are the distance units used by distance fields of the analysis layer's sublayers and tables. The following options are available from the drop-down list:

• Meters
• Kilometers
• Feet
• Miles
• Nautical Miles
• Centimeters
• Millimeters
• Decimeters
• Yards
• Inches

Time

Use the options from the Time section to specify the start time to be used in the analysis.

Default Route Start Time of Day

This property defines the starting time for the route. If this property is left null, the StartTime field must be populated for each route in the Route sublayer.

Max Total Time

This property can be used to specify the maximum allowable route duration. The route duration includes travel times as well as service and wait times at stops, depots, and renewals. If this property is left null, the MaxTotalTime field must be populated for each route in the Route sublayer.

Drawing

Use the Symbology button to access the symbology pane for the active network analysis layer. You can configure the symbology for the sublayers of the active network analysis layer by choosing one of the following options:

• Single Color—This option is available for all network analysis layer types. All feature sublayers in the active network analysis layer except barriers will use the same single symbol with the specified color. For example, choosing a single color of blue for a Route layer will convert all the Stops and Routes features to the same color of blue.
• Color Linked—This option is available for Route, Last Mile Delivery, Vehicle Routing Problem, and Waste Collection analysis layers. It applies a color scheme to the sublayers such that related features are symbolized with the same color. This symbology configuration symbolizes related features with the same color, making it easier to visually distinguish different routes and their associated features in the map. For example, for a Route layer with multiple routes, each route and the stops assigned to that route will be assigned matching colors.

Learn more about network analysis layer symbology

Filtering

You can filter the network analysis sublayers to only show features related to the selected features in the primary layer.

• Add Filters —Applies filters to sublayers of the network analysis layer to only show features related to the selected feature of the primary sublayer. Definition queries are automatically created and applied on the relevant sublayers. Every time the Add Filters button is clicked, a new definition query is created with the same name replacing the previous definition query.

  When a feature is selected in the primary sublayer Routes, a definition query called Routes is created on the Routes sublayer (primary layer) and the related Stops, Route Lines, and Renewal Visits sublayers.

• Remove Filters —Deletes the definition query on the primary and the related sublayers.

Advanced

Use the option in the Advanced section to specify the collection mode.

Collection mode

This property can be used to specify if the location is picked up by a vehicle servicing both sides of the street at once or by a vehicle servicing the two sides separately with different passes down the street edge.

The following options are available from the drop-down list:

• No default—No default collection mode is specified. This means that the CollectionMode field in the Stops feature class must be specified for all stops. This is the default property value.
• One side at a time—The two sides of the street on which this stop is located are collected separately with different passes down the street edge.
• Both sides together—Both sides of the street on which this stop is located are collected at once with a single pass down the street edge.

Reports

Use the options in the Reports section to generate a report that can be distributed to the drivers and generate directions for each route.

Route Report

Click the Route Report button to generate a report for each route in the solution. The report contains an overview of the analysis with statistics about each route and details for each route with insert maps to trace through the route lines.

Show Directions

Click the Show Directions button . The Directions pane appears with turn-by-turn directions for each route in the solution.