Council Wide Digital PlatformNo Code Service CreationGCloud Information

Request a Bin Configuration

The configuration for the Request a Bin form is fairly significant owing to the high level of configuration in the form.

But can be broken down into the following areas:

Yotta Specific Sections

Back Office Mapping

This section tells us which attribute to check for the property type with. I.e. in the Area section you can indicate which type of properties can have which bins. This setting says what the parameter is in Yotta Alloy that holds the collection of different areas. This exists because these can be different from one Yotta Alloy customer to another.

  <BackOfficeMapping>
    <Mapping 
    
    Key="PremisesCustomAreaCode" 
    Value="attributes_nlpgPremisesServiceType_5f9beae0a198dd0064e02c1a"
    />
    
  </BackOfficeMapping>

You only need the above if you support different bins for different property categories.

Address Search Filter

This section tells the Missed Bin form's address look up which addresses to look for and has the primary purpose of excluding commercial addresses. The only parameter that really matters if the 'Value', which says only show addresses where the class of them starts with an R. You could change this to RD (residential) but generally R is suffice:

Mandatory Container Conditions

  • The Mandatory Container Conditions enables a council to stipulate conditions that must be met for certain container types to be request. There are three of these built in:

    • Large family where you can control:

      • What constitutes a large family by changing the value 'NumberConstraint'. The default is 5 constitutes a larger family but could be changed to 10 etc.

    • Children in nappies where you can control:

      • The number of children that need to be in nappies for the condition to be met by changing the value 'NumberConstraint'. The default is 2.

    • Medical Condition

      • Which uniquely has the ability to set whether proof is mandatory via an evidence upload i.e. UploadRequired="True" means they must upload evidence

    • All of the above scenarios have the ability to mandate (or not) that the customer:

      • Checks a box to confirm the condition to be true

        • ConfirmationRequired="True"

      • Provides details of them meeting the condition

        • ExplanationTextRequired="True"

Sample Mandatory Contained Conditions section

Once you have set up the conditions you need to set them against containers where it is appropriate as shown here:

E.g. in the example above if a person wants a larger 360 litre bin they need to meet one of the three conditions:

In Built Discounts

Some councils will log that the developer has already pre-paid for containers with an indicator in their system. This config enables you to set which attribute will result in a different price being set for bins being requested:

This is used in conjunction with a bin being requested. E.g. The below is an additional recycling bin where the normal cost would be 37.70 but is 0 where this marker is present.

Rounds

This allows to set which rounds (or put another way - waste streams) the council want to allow people to request a new/replacement bin for. The configuration simply needs the back office value for the round as well as the color. The description is what the customer will see when indicating the stream where they need a new/replacement bin.

The following is a sample section for Rounds:

Bin Types

It goes without saying that the configuration needs to hold the bin types that a person can order to ensure that payment references, where there's a cost, can be linked to them and so the waste operations team know which bin to deliver/replace etc.

For each bin type you can set the following attributes:

  • Value (the code for the container) as held in the back office waste system

  • The waste stream colour

  • The round type

  • The Payment system's Fund Code to link it to

  • The Payment system's Reference code to link it to

  • The Payment system's VAT Code to link it to

The above will show as a single line in the file we've added a line break before each editable parameter to make them easier to visualise.

There is one additional bin type parameter, which is specifically there for 'New Bin Sets' for people that have moved into a property and there are no bins - typically new builds:

Area

In some councils different types of property can request different types of bins. I.e. Flats can order / replace some types of bins and those properties with gardens can order others. Area is designed for that purpose.

The ability to have different Areas is currently only supported for Yotta Alloy. The element DOES still exist for all sites but the ability to distinguish between them is linked to a specific Yotta Alloy attribute.

For example, the following shows a Street Level property section commented because the codes in Yotta Alloy are long/unclear as to their purpose.

New Bin Set

When a citizen is requesting a new bin set the council needs to be able to indicate what falls into this. I.e. which bins does a bin set comprise. There is a dedicated element NewBinSet, which enables you to set:

  • The Price - £93.00 in the example below

  • The list of bins and their count included in a new bin set

The Option Value="NBSET" is built into our application to make it obvious when going through the file. I.e. you don't change this.

Replace a Bin

There is built in configuration for three different scenarios where a person wants a replacement bin within the form:

  • Damaged

  • Lost

  • A different bin is wanted - Exchange

Because a council might want to change the bins provided in each scenario there are dedicated sections in the file for each.

Damaged

Within the section every bin that they could report damage should be listed and within that you need indicate which bins they could get as a replacement, its price and whether there are any mandatory conditions for getting that bin type.

The following is an excerpt from the section:

This shows the:

  • ReplaceBin section is Damaged

  • First bin type they could currently have is 6523 (which is the back office code for the bin)

  • The options they can replace the damaged bin with i.e. if 6523 was a small black bin, the options might be:

    • 6507 = standard black bin

    • 6537 = large black bin for non-medical reasons

    • 6744 = large black bin for medical reasons

  • With a price and mandatory conditions for the larger bin for the non-medical reasons

  • No price and a different (medical) mandatory condition for the larger bin for medical reasons

Lost

Each type of replacement follows a common pattern so the above for damaged is also true below. I.e. what bin should they have and what are the options and price for the replacement.

The only difference is you're more likely to add the Developer Pre Paid 'Discount' to these as there is not a damaged bin but rather there are no bins.

Exchanged

With the format continuing for each type of bin that can be exchanged:

Additional / New Bins

Because a person might want a new or additional bin there is a separate section for this.

Within this section you can set beyond the standard content of the replace a bin above:

  • Round type (waste stream)

  • The Maximum Number of bins in a given permitted waste stream for a property - where this is used the form will check the number of bins for this round already at the property and only allow up to the maximum number to be ordered.

    • I.e. how many black bins - NOT how many bins of a certain type of bin

  • Single Item - where this is added to the config (instead of MaximumBinsAtProperty) a tick box is used to order the bin rather than a drop down list of numbers.

  • Where neither Maximum Number of bins or Single Item is used a drop down list is displayed allowing up to 4 bins to be ordered.

  • CurrentBin value supports a value of null i.e. I want a new bin where there is no bin held against the property in the waste management system

Container Event Actions

Container events are events that exist against the property that you want to prevent a person requesting a new bin for. I.e. the person is ordering a new bin but the council already knows the reason they have no bin is not because it is lost, it is because they damaged it or it fell into the wagon. So they've already instigated a process to deliver a replacement.

  • The configuration holds the event code to look for (Bartec's event-sub event is shown below e.g. 284-574)

Container Events

This configuration links to the above Container Event Actions. But this is to set out the message to present to customers for each message.

Full Example File (Bartec - Civica Pay Example)

PreviousSettingsNextBulky Waste Collection

Last updated

Was this helpful?