Commander4j - User contributions [en-gb]

Case Label

2024-08-20T08:37:14Z

5.64.222.137:

[[file:Case_Label.png|600px]]

The above screen is used to print Case Labels.
 
There are two methods to print a label depending on the type or printer/labeller that you want to use and this is described in the [[Pallet Label Printing]] page.

{| class="wikitable" style="margin:auto"
|+ Case Label
|-
! Field !! Description
|-

| 1 || Process Order or Works Order Number can be typed in or picked using the lookup button.
|-
| 2 || Process Order Status is shown in RED if the order is closed.
|-
| 3 || Date of Manufacture will default to the computers system clock but you can amend it manually if necessary. The expiry date of the pallet is calculated by adding the shelf life to the date of manufacture.
|-
| 4 || The screen determines what a full pallet quantity would contain by reference to [[Material UOMs]]
|-
| 5 || Expiry Date is calculated by adding the Shelf Life settings found in the [[Materials]] screen to the Date of Manufacture but you can override if necessary.
|-
| 6 || Preview is only applicable for "Standard" reports which are created for any printer. If you change the PALLET_LABEL module to use a Zebra ZPL compatible Label then you won't be able to preview the label on screen.
|-
| 7 || Number of labels.
|-
| 8 || The Label button is used to generate a label and sent it do the printer from the desktop client and is subtly different to the Assign to Labeller button (10) which is used to drive external labelling applications such as the [https://github.com/C4J/Commander4j-AutoLab/releases AutoLab4j] application.
|-
| 9 || This is the name of the print queue that you want the label to be sent to when using the Label button (8). It is important to understand the difference between the type types of label printing mechanisms and the print queue requirements. See [[Printer Queues]]
|-
| 10 || See [[Process Order Assign to Labeller]]
|-
| 11 || The structure - content of the [[Batch Number]] gets its default format from the [[System Keys]] screen. However you can override it on the [[Customers]] screen. This allows the content of the label to be different depending on which customer id is assigned to the [[Process Orders]]
|}

[[file: Case_Label_Preview.png|600px]]

Requirements

2024-08-19T16:33:25Z

5.64.222.137:

== Operating System ==
* Windows 10 or 11 (32bit or 64bit)
* MacOS (Intel or Apple Silicon)
* Linux (Separate install of Java 17 required)

== Database (Required) ==
* [https://github.com/C4J/Commander4j/wiki/Installation#mysql mySQL]
* [https://github.com/C4J/Commander4j/wiki/Installation#ms-sql MSSQL]
* [https://github.com/C4J/Commander4j/wiki/Installation#oracle Oracle]
* [https://github.com/C4J/Commander4j/wiki/Installation#mysql MariaDB]

== Web Server for Mobile Scanners ==
* [https://tomcat.apache.org/index.html Apache Tomcat]

== Java (Optional) ==
* [https://www.azul.com/downloads/#zulu Java JDK]

== Barcode Scanner (Optional) ==
* [https://www.zebra.com/us/en/products/mobile-computers/handheld.html?page=1 Zebra Mobile Scanner]
* [https://www.zebra.com/us/en/software/mobile-computer-software/enterprise-browser.html Zebra Enterprise Browse]

== Barcode Printer ==
* [https://www.zebra.com/us/en/products/printers/industrial.html?page=1 Zebra ZPL Compatible Printer]

System Keys

2024-08-19T16:32:41Z

5.64.222.137:

[[file:System Keys1.png|600px]]

System Keys are a set of global settings used by the application to determine how certain functions work. These settings will include such items as :-

{| class="wikitable" style="margin:auto"
|+ System Keys
|-
! System Key !! Typical Value !! Description
|-
| BATCH EXPIRY TIME || || A flag which is used to determine how the time portion of the Expiry Date is calculated. Can be - = or +
|-
| BATCH FORMAT || {YEAR1}{JULIAN_DAY}{PLANT} || Used to construct the batch number when creating/printing new Pallet Tickets (SSCC's)
|-
| BATCH REGEX || - || Optional Regular Expression which can be used to validate the Batch Number after user has edited by hand.
|-
| COMPANY NAME || My Company || Text that you want to appear at the top of reports.
|-
| DEFAULT BATCH STATUS || Restricted || Deprecated - no longer used. Now held in Material Master record.
|-
| DEFAULT HELPSET ID || || Deprecated - no longer used. Help now linked to Wiki pages.
|-
| DEFAULT PALLET STATUS || Unrestricted || Deprecated - no longer used. Now held in Process Order record.
|-
| DEFAULT_LOCATION || MYLOCATION || Should be a valid Location Id from the locations screen and is used by the Despatch function
|-
| DESPATCH NUMBER || 1 || Used to determine the numeric element of the next despatch number.
|-
| DESPATCH NUMBER FORMAT || XX{NNNNNN} || Defines the structure of the Despatch Number. {NNN} indicates the number above. XX is a literal prefix.
|-
| EXPIRY DATE MODE || BATCH || Can be either BATCH or SSCC. This value should be set before go-live and not changed. BATCH will store the Expiry Date in the Batches table using the MATERIAL/BATCH NUMBER as the key. All production which shares the same Material and Batch will therefore have the same Expiry (Best Before End) date. The format of the Batch Number is defined above and can include a Julian Date component so that it automatically changes at midnight. SSCC mode will store the Expiry Date in the PALLET record and as such allow you to change the expiry date independently of the Batch Number.
|-
| HELPSET FILENAME || help/helpset.hs || Deprecated - no longer used. Help now linked to Wiki pages.
|-
| INTERFACE LOG ID || 1 || Sequential Unique ID used to record all Interface activity (Inbound and Outbound).
|-
| INTERFACE REQUEST ID || 1 || Sequential Unique ID used by outbound interface queue.
|-
| LABEL_HEADER_COMMENT || Free Format Text || Optional free format text than can appear on Finished Goods Label.
|-
| MAIL_POP_AUTH_PWD || password || Not currently used.
|-
| MAIL_POP_AUTH_USER || user || Not currently used.
|-
| MAIL_POP_HOST_NAME || host.com || Not currently used.
|-
| MAIL_SMTP_AUTH_PWD || password || SMTP password.
|-
| MAIL_SMTP_AUTH_REQD || true || Indicates if SMTP server requires authentication.
|-
| MAIL_SMTP_AUTH_USER || user || SMTP username
|-
| MAIL_SMTP_FROM_ADDRESS || user@me.com || Specifies SMTP sending email address.
|-
| MAIL_SMTP_HOST_NAME || host.com || SMTP Host Name
|-
| MAIL_SMTP_MSG_TYPE || text/plain || Format of mail message
|-
| MAIL_SMTP_PORT || 25 || SMTP Port Number
|-
| MHN INITIAL DECISION || Pending || Master Hold Notice default/starting decision for Pallet.
|-
| MHN NUMBER FORMAT || XX{NNNNNN} || Defines the structure of the Master Hold Notice Number. {NNN} indicates the numeric element. XX is a literal prefix.
|-
| PASSWORD ATTEMPTS || 3 || Maximum number of invalid password attempts before an account is locked out.
|-
| PASSWORD EXPIRY || 30 || Number of days before a users password expires and they are prompted to change it.
|-
| PLANT || 1234 || Deprecated - no longer used.
|-
| PROCESS ORDER NUMBER || 1 || Used to determine the numeric element of the next Process Order number (when created manually).
|-
| PROCESS ORDER NUMBER FORMAT || {NNNNNN} || Defines the structure of the Process Order Number. {NNNNNN} indicates the number above.
|-
| PROGRAM VERSION || 3.63 || Stores the current version of the Application. Users are warned if they attempt to connect with different version.
|-
| REPORT REQUEST ID || 3.63 || Used internally for queuing report requests generated by user of the web interface on RF Barcode Scanners.
|-
| RESOURCE LIST || \01\02\03\04\ || Delimited list of values. User can select these values when using the Process Order Barcode printing facility.
|}

Downloads

2024-08-19T16:32:09Z

5.64.222.137:

{| class="wikitable" style="margin:auto"
|+ Downloads
|-
! Name !! Description
|-
| [https://github.com/C4J?tab=repositories All Projects] || Overview of all Projects
|-
| [https://github.com/C4J/Commander4j/releases Commander4j] || Commander4j Core Application
|-
| [https://github.com/C4J/Commander4j-Middleware/releases Middleware] || Middleware for message translation to external systems
|-
| [https://github.com/C4J/Commander4j-AutoLab/releases AutoLab4j] || Automatic Label Application triggered by MODBUS
|-
| [https://github.com/C4J/Commander4j-LabelServer/releases LabelServer] || Service to send Label Data to Labellers
|-
| [https://github.com/C4J/sftpSend/releases SFTP Send] || Utility to send files automatically via SFTP
|-
| [https://github.com/C4J/sftpGet/releases SFTP Get] || Utility to collect files automatically via SFTP
|}

Waste Recording

2024-08-19T15:21:26Z

5.64.222.137:

The Waste Module is designed to allow you to record where waste is being generated in a manufacturing environment and then report on it so that you can easily determine which areas might benefit from improvement.

This module is part of Commander4j version 8.02 or newer and some example data has been included to illustrate how it can be configured. By default, the Waste module/options will be assigned to a new user group called WASTE. If you don't see these options when you logon to Commander4j you will need to be added to this group and then logon again.

===Example Factory===

In order to understand the demo data, you should review the diagram below. This diagram represents a totally fictitious factory so don't worry if it does not make any kind of sense from a manufacturing perspective.

[[file:Waste_virtual_factory.png|600px]]

===Physical Location IDs===

The first thing you should notice is that some physical waste recording points have been marked in red and yellow. These physical locations have been defined within the database and will subsequently be linked/grouped to logical reporting id's.

These physical locations are recorded in the Waste Locations screen which you can see below. When creating a new location in the database you will find that certain special characters that cannot be represented in a barcode will be automatically replaced with underscores. You can edit an existing entry by double-clicking on a row, or selecting a row and clicking on the edit button.

[[file:Waste_location_1.png|600px]]

When you define a location you can specify which types of waste can be recorded in this location. You may, for example, have a location (bin) which is for putting only recyclable cardboard in. You can also indicate if the operator needs to record the current Process Order and/or the Reason of why waste has been generated. The permitted types shown on this screen can be defined within the application.

[[file:Waste_location_2.png|600px]]

===Location Barcode===

To make recording waste simple to do there is a web application for use with Zebra Scanners / Enterprise Browser. This function prompts the user to select the location where they are working and this can be accomplished either manually on screen or quickly by scanning one of the barcodes produced by the label report shown below.

[[file:Waste_location_barcode.png|600px]]

===Logical Reporting IDs===

After the physical locations have been defined you should then create the logical locations. In the example layout, these are shown as "PREP 1", "LINE 1" etc. So what is a logical location? Let us look at the factory layout. You will see a location B004 and B008 - they are both related to LINE_1. For reporting purposes, you might decide that when reporting on the waste generated by LINE 1 you would prefer to select the data using an easily rememberable criterion such as Reporting ID: LINE_1 rather than trying to recall that you need to report on Location B004 and B008 and then add the values together.

[[file:Waste_location_3.png|600px]]

The Reporting ID's can also be collated into Reporting Groups. You may decide that you want to generate a report on ZONE_2 which includes production lines LINE_1, LINE_2, LINE3, and LINE_4. Reporting Groups are defined in another screen shown later.

[[file:Waste_location_4.png|600px]]

===Link Physical Location ID to Reporting ID===

This screen allows you to associate a physical Location ID with one or more logical Reporting ID's. You should note that any physical location will probably want to be included in more that one reporting ID. In the screen below you can see that physical location B003 will be included in reports for PREP_3, ZONE_1 and of course the top level FACTORY.

[[file:Waste_location_5.png|600px]]

===Link Reporting ID to Physical Location ID===

This screen allows you to associate a logical Reporting ID with one or more physical Location ID's. This is the easiest method to check that any particular reporting ID has all the associated locations included.

[[file:Waste_location_6.png|600px]]

===Waste Types===

When we looked that the properties of a Waste Location we could see that the location could be identified as being suitable for certain types of waste only. The screens used for recording waste will validate that the material code used by the operator is consistent with the material types permitted at that location.

[[file:Waste_location_7.png|600px]]

The Waste Type record include certain attributes which can indicate if the waste can be recycled, if it is hazardous and if PPE is required.

[[file:Waste_location_8.png|600px]]

===Waste Reasons===

When we looked at the properties for a location, one of the options which could be selected was a checkbox to indicate that the operator needs to specify the reason for the waste being logged. The following screen allows you to specify any number of reason codes

[[file:Waste_location_10.png|600px]]

[[file:Waste_location_11.png|600px]]

===Reason Barcode===

If the operator needs to provide a reason for the waste being generated then this can also be scanned to save time. Below is an example barcode report from the reason screen.

[[file:Waste_reason_barcode.png|600px]]

===Reporting Groups===

[[file:Waste_location_12.png|600px]]

[[file:Waste_location_13.png|600px]]

===Waste Materials===

[[file:Waste_location_14.png|600px]]

[[file:Waste_location_15.png|600px]]

===Material Barcode===

[[file:Waste_material_barcode.png|600px]]

===Process Order Barcode===

[[file:Waste_process_order_barcode.png|600px]]

===Waste Transactions===

[[file:Waste_location_16.png|600px]]

===Wireless Mobile Computer Screens===

[[file:Waste_location_scan1.png|600px]]

[[file:Waste_location_scan2.png|600px]]

===Log Admin and Enquiries===

[[file:Waste_location_17.png|600px]]

[[file:Waste_location_17a.png|600px]]

===Log Report===

[[file:Waste_location_21.png|600px]]

===Reporting===

[[file:Waste_location_18.png|600px]]

Summary 1 - By Group
[[file:Waste_location_19.png|600px]]

Summary 2 - By Material
[[file:Waste_location_20.png|600px]]

Summary 3 - By Reason
[[file:Waste_location_22.png|600px]]

Waste Recording

2024-08-19T15:19:49Z

5.64.222.137:

The Waste Module is designed to allow you to record where waste is being generated in a manufacturing environment and then report on it so that you can easily determine which areas might benefit from improvement.

This module is part of Commander4j version 8.02 or newer and some example data has been included to illustrate how it can be configured. By default, the Waste module/options will be assigned to a new user group called WASTE. If you don't see these options when you logon to Commander4j you will need to be added to this group and then logon again.

===Example Factory===

In order to understand the demo data, you should review the diagram below. This diagram represents a totally fictitious factory so don't worry if it does not make any kind of sense from a manufacturing perspective.

[[file:Waste_virtual_factory.png|600px]]

===Physical Location IDs===

The first thing you should notice is that some physical waste recording points have been marked in red and yellow. These physical locations have been defined within the database and will subsequently be linked/grouped to logical reporting id's.

These physical locations are recorded in the Waste Locations screen which you can see below. When creating a new location in the database you will find that certain special characters that cannot be represented in a barcode will be automatically replaced with underscores. You can edit an existing entry by double-clicking on a row, or selecting a row and clicking on the edit button.

[[file:Waste_location_1.png|600px]]

When you define a location you can specify which types of waste can be recorded in this location. You may, for example, have a location (bin) which is for putting only recyclable cardboard in. You can also indicate if the operator needs to record the current Process Order and/or the Reason of why waste has been generated. The permitted types shown on this screen can be defined within the application.

[[file:Waste_location_2.png|600px]]

===Location Barcode===

To make recording waste simple to do there is a web application for use with Zebra Scanners / Enterprise Browser. This function prompts the user to select the location where they are working and this can be accomplished either manually on screen or quickly by scanning one of the barcodes produced by the label report shown below.

[[file:Waste_location_barcode.png|600px]]

===Logical Reporting IDs===

After the physical locations have been defined you should then create the logical locations. In the example layout, these are shown as "PREP 1", "LINE 1" etc. So what is a logical location? Let us look at the factory layout. You will see a location B004 and B008 - they are both related to LINE_1. For reporting purposes, you might decide that when reporting on the waste generated by LINE 1 you would prefer to select the data using an easily rememberable criterion such as Reporting ID: LINE_1 rather than trying to recall that you need to report on Location B004 and B008 and then add the values together.

[[file:Waste_location_3.png|600px]]

The Reporting ID's can also be collated into Reporting Groups. You may decide that you want to generate a report on ZONE_2 which includes production lines LINE_1, LINE_2, LINE3, and LINE_4. Reporting Groups are defined in another screen shown later.

[[file:Waste_location_4.png|600px]]

== Link Physical Location ID to Reporting ID==

This screen allows you to associate a physical Location ID with one or more logical Reporting ID's. You should note that any physical location will probably want to be included in more that one reporting ID. In the screen below you can see that physical location B003 will be included in reports for PREP_3, ZONE_1 and of course the top level FACTORY.

[[file:Waste_location_5.png|600px]]

=== Link Reporting ID to Physical Location ID ===

This screen allows you to associate a logical Reporting ID with one or more physical Location ID's. This is the easiest method to check that any particular reporting ID has all the associated locations included.

[[file:Waste_location_6.png|600px]]

=== Waste Types ===

When we looked that the properties of a Waste Location we could see that the location could be identified as being suitable for certain types of waste only. The screens used for recording waste will validate that the material code used by the operator is consistent with the material types permitted at that location.

[[file:Waste_location_7.png|600px]]

The Waste Type record include certain attributes which can indicate if the waste can be recycled, if it is hazardous and if PPE is required.

[[file:Waste_location_8.png|600px]]

=== Waste Reasons ===

When we looked at the properties for a location, one of the options which could be selected was a checkbox to indicate that the operator needs to specify the reason for the waste being logged. The following screen allows you to specify any number of reason codes

[[file:Waste_location_10.png|600px]]

[[file:Waste_location_11.png|600px]]

=== Reason Barcode ===

If the operator needs to provide a reason for the waste being generated then this can also be scanned to save time. Below is an example barcode report from the reason screen.

[[file:Waste_reason_barcode.png|600px]]

=== Reporting Groups ===

[[file:Waste_location_12.png|600px]]

[[file:Waste_location_13.png|600px]]

=== Waste Materials ===

[[file:Waste_location_14.png|600px]]

[[file:Waste_location_15.png|600px]]

=== Material Barcode ===

[[file:Waste_material_barcode.png|600px]]

=== Process Order Barcode ===

[[file:Waste_process_order_barcode.png|600px]]

=== Waste Transactions ===

[[file:Waste_location_16.png|600px]]

=== Wireless Mobile Computer Screens ===

[[file:Waste_location_scan1.png|600px]]

[[file:Waste_location_scan2.png|600px]]

=== Log Admin and Enquiries ===

[[file:Waste_location_17.png|600px]]

[[file:Waste_location_17a.png|600px]]

=== Log Report ===

[[file:Waste_location_21.png|600px]]

=== Reporting ===

[[file:Waste_location_18.png|600px]]

Summary 1 - By Group
[[file:Waste_location_19.png|600px]]

Summary 2 - By Material
[[file:Waste_location_20.png|600px]]

Summary 3 - By Reason
[[file:Waste_location_22.png|600px]]

Waste Recording

2024-08-19T15:17:50Z

5.64.222.137:

__FORCETOC__

{|align=right
|__TOC__
|}

* [Example Factory](#example-factory)
* [Physical Location IDs](#physical-location-ids)
* [Location Barcode](#location-barcode)
* [Logical Reporting IDs](#logical-reporting-ids)
* [Link Reporting ID to Physical Location ID](#link-reporting-id-to-physical-location-id)
* [Waste Types](#waste-types)
* [Waste Reasons](#waste-reasons)
* [Reason Barcode](#reason-barcode)
* [Reporting Groups](#reporting-groups)
* [Waste Materials](#waste-materials)
* [Material Barcode](#material-barcode)
* [Process Order Barcode](#process-order-barcode)
* [Waste Transactions](#waste-transactions)
* [Wireless Mobile Computer Screens](#wireless-mobile-computer-screens)
* [Log Admin & Enquiries](#log-admin-and-enquiries)
* [Log Report](#log-report)
* [Reporting](#reporting)
=first=

==second==

The Waste Module is designed to allow you to record where waste is being generated in a manufacturing environment and then report on it so that you can easily determine which areas might benefit from improvement.

This module is part of Commander4j version 8.02 or newer and some example data has been included to illustrate how it can be configured. By default, the Waste module/options will be assigned to a new user group called WASTE. If you don't see these options when you logon to Commander4j you will need to be added to this group and then logon again.

===Example Factory===

In order to understand the demo data, you should review the diagram below. This diagram represents a totally fictitious factory so don't worry if it does not make any kind of sense from a manufacturing perspective.

[[file:Waste_virtual_factory.png|600px]]

===Physical Location IDs===

The first thing you should notice is that some physical waste recording points have been marked in red and yellow. These physical locations have been defined within the database and will subsequently be linked/grouped to logical reporting id's.

These physical locations are recorded in the Waste Locations screen which you can see below. When creating a new location in the database you will find that certain special characters that cannot be represented in a barcode will be automatically replaced with underscores. You can edit an existing entry by double-clicking on a row, or selecting a row and clicking on the edit button.

[[file:Waste_location_1.png|600px]]

When you define a location you can specify which types of waste can be recorded in this location. You may, for example, have a location (bin) which is for putting only recyclable cardboard in. You can also indicate if the operator needs to record the current Process Order and/or the Reason of why waste has been generated. The permitted types shown on this screen can be defined within the application.

[[file:Waste_location_2.png|600px]]

===Location Barcode===

To make recording waste simple to do there is a web application for use with Zebra Scanners / Enterprise Browser. This function prompts the user to select the location where they are working and this can be accomplished either manually on screen or quickly by scanning one of the barcodes produced by the label report shown below.

[[file:Waste_location_barcode.png|600px]]

===Logical Reporting IDs===

After the physical locations have been defined you should then create the logical locations. In the example layout, these are shown as "PREP 1", "LINE 1" etc. So what is a logical location? Let us look at the factory layout. You will see a location B004 and B008 - they are both related to LINE_1. For reporting purposes, you might decide that when reporting on the waste generated by LINE 1 you would prefer to select the data using an easily rememberable criterion such as Reporting ID: LINE_1 rather than trying to recall that you need to report on Location B004 and B008 and then add the values together.

[[file:Waste_location_3.png|600px]]

The Reporting ID's can also be collated into Reporting Groups. You may decide that you want to generate a report on ZONE_2 which includes production lines LINE_1, LINE_2, LINE3, and LINE_4. Reporting Groups are defined in another screen shown later.

[[file:Waste_location_4.png|600px]]

== Link Physical Location ID to Reporting ID==

This screen allows you to associate a physical Location ID with one or more logical Reporting ID's. You should note that any physical location will probably want to be included in more that one reporting ID. In the screen below you can see that physical location B003 will be included in reports for PREP_3, ZONE_1 and of course the top level FACTORY.

[[file:Waste_location_5.png|600px]]

=== Link Reporting ID to Physical Location ID ===

This screen allows you to associate a logical Reporting ID with one or more physical Location ID's. This is the easiest method to check that any particular reporting ID has all the associated locations included.

[[file:Waste_location_6.png|600px]]

=== Waste Types ===

When we looked that the properties of a Waste Location we could see that the location could be identified as being suitable for certain types of waste only. The screens used for recording waste will validate that the material code used by the operator is consistent with the material types permitted at that location.

[[file:Waste_location_7.png|600px]]

The Waste Type record include certain attributes which can indicate if the waste can be recycled, if it is hazardous and if PPE is required.

[[file:Waste_location_8.png|600px]]

=== Waste Reasons ===

When we looked at the properties for a location, one of the options which could be selected was a checkbox to indicate that the operator needs to specify the reason for the waste being logged. The following screen allows you to specify any number of reason codes

[[file:Waste_location_10.png|600px]]

[[file:Waste_location_11.png|600px]]

=== Reason Barcode ===

If the operator needs to provide a reason for the waste being generated then this can also be scanned to save time. Below is an example barcode report from the reason screen.

[[file:Waste_reason_barcode.png|600px]]

=== Reporting Groups ===

[[file:Waste_location_12.png|600px]]

[[file:Waste_location_13.png|600px]]

=== Waste Materials ===

[[file:Waste_location_14.png|600px]]

[[file:Waste_location_15.png|600px]]

=== Material Barcode ===

[[file:Waste_material_barcode.png|600px]]

=== Process Order Barcode ===

[[file:Waste_process_order_barcode.png|600px]]

=== Waste Transactions ===

[[file:Waste_location_16.png|600px]]

=== Wireless Mobile Computer Screens ===

[[file:Waste_location_scan1.png|600px]]

[[file:Waste_location_scan2.png|600px]]

=== Log Admin and Enquiries ===

[[file:Waste_location_17.png|600px]]

[[file:Waste_location_17a.png|600px]]

=== Log Report ===

[[file:Waste_location_21.png|600px]]

=== Reporting ===

[[file:Waste_location_18.png|600px]]

Summary 1 - By Group
[[file:Waste_location_19.png|600px]]

Summary 2 - By Material
[[file:Waste_location_20.png|600px]]

Summary 3 - By Reason
[[file:Waste_location_22.png|600px]]