Configuring Schedules and Waste Data

Created by Alfie Jennings, Modified on Mon, 14 Nov, 2022 at 4:03 PM by Alfie Jennings

Collection schedules can be added manually, either via file import or through the Contracts Module.

Importing Collection Schedules via File Import

Go to Waste -> Option -> Import

Click on the [Choose File] button, and select the CSV file you want to upload, and then click on [Submit]. The [Download Template] option will provide you with an example file with all the required fields. You can then go into Waste -> Action -> CSV upload result to check if the file was uploaded successfully.

- To 'ADD' new schedules, enter details as per table 'Parameters for file upload....' without a value in the <action> column.

- To 'AMEND' an existing schedule(s), you will need to know the schedule id(s) you are amending. enter the details as per table 'Parameters for file upload....' but ensure the the schedule ID which needs to be amended is included in the <action> column. As an example, if the end date of the schedule needs to be updated, 'Amend' the existing schedule with the same data as the upload, but include the schedule if in the <action> column and add the required end date to <end_date> value.

- To 'DELETE' a schedule, update the <end_date> value to specify the end or deletion date of the schedule using the 'AMEND' technique.

Alternatively, the 'Schedule Changes' functionality can be used to 'COPY', 'MOVE' , 'DELETE' and 'CHANGE END DATE' of schedules in Bulk on a scheduled basis.

Parameters for file upload .csv format are as follows:

Parameter	Required Value	Notes
<action>	Schedule number (if amendment only)	The number for the schedule. If adding a new schedule this is not required. If updating a schedule this is required.
<collection_type>	MCS Collection_type code	Alphanumeric - Code for collection type configured in 1.1
<round_number>	Round Number	Alphanumeric - Round Number
<container_type>	MCS container type code	Alphanumeric - Code for container type configured in 1.1
<no_of containers>	Numeric value	Number of the container type that needs to be added
<assisted>	Y or N	Y or N default
<start_date>	DD/MM/YYYY	Date Value as required, please note this will be determined by the Round allocated if Allocated From is set to ‘Round’
<end_date>	DD/MM/YYYY	Date Value as required, please note this will be determined by the Round allocated if Allocated From is set to ‘Round’
<round_type>	Round_type	Alphanumeric - Code for round type configured in 1.2
<uprn>	UPRN	UPRN for property
Auto Allocate Round	Yes or No	If Yes, will determine round from UPRN, co-ordinates and allocate Round according to ‘Area’. Or No, will use round_number.

Manually Adding Collection Schedules

Go to Waste -> Add, and fill in all mandatory fields. Selecting the “Auto take Round Number” option as ‘Yes’, when adding the collection schedule the system will use geospatial logic to allocate to the correct round (NOTE: this is if appropriate round is configured with ‘Area’.). If “Auto take Round Number ‘ is set to No, the appropriate round will need to be selected.

You can opt to add another Container Type, if applicable. Selecting “Add further collection?” will … Click on [Continue] to finish.

Searching for Collection Schedules

Go to Waste -> Options and select the appropriate filter criteria.

Search for this address, and the Collection Schedule will be displayed. If Rounds are configured for the Collection Type selected, the Day, Round, and Frequency will be specified. If not, this will need to be entered/selected

Creating a Collection Schedule from a Contract

Collection Schedules can be created on creation a Contract and further amended on renewal, amendment or termination of a Contract. This is configured using the following Rule options, and based on the location selected in the Contract:

1. When Contract Created - this will create a Collection Schedule for the location specified in the Contract, using the Collection Type specified. The number of containers created on the Collection Schedule is derived from the number of Items in the Contract. If Rounds have been configured for the Collection Type, the Round will be derived from the UPRN of the location in the Contract. If the Collection Type is configured to “Auto Create Task”, services will be created based on the Start and End Dates of the Contract, and the Round frequency.

2. Contract Terminated - this will update the End Date of the Waste Collection Schedule for the location, based on the date when the Contract is terminated. This will remove any related services that have been created.

3. Contract Cancelled - this will update the End Date of the Waste Collection Schedule for the location, based on the date when the Contract is terminated. This will remove any related services that have been created.

4. Contract Novated - this will update the End Date of the Waste Collection Schedule for the location, based on the date when the Contract is terminated for the location, due to the novation. This will remove any related services that have been created. A new Collection Schedule will then be created for the new location, using the Start Date from when the Contract was novated, and using the End Date of the Contract to populate the End Date of the Collection Schedule. Services will be created based on the Start and End Dates, and the Round frequency.

5. Contract Item Created - this will add new containers to the Collection Schedule, for the location specified in the Contract. This is typically used when the Contract is renewed. If the Collection Type is configured to “Auto Create Task”, services will be created based on the Start and End Dates of the Contract and Round frequency.

6. Contract Item Updated - this will amend any container numbers in the Collection Schedule, for the location specified in the Contract. If the Collection Type is configured to “Auto Create Task”, services will be amended based on the Start Date of the updated Item, and the End Date of the Contract and Round frequency.