The primary OEH category for recording on all transactions is the waste stream.

POEO 2015: In the previous data pack offered, two additional streams were available. These streams are no longer available as a specific waste stream but are derived:

• Other Waste Facility - This will be used in place of any existing waste streams if an external location is used as a source for an inbound transaction or as the destination of an outbound transaction and that location has a a valid EPL number assigned to it.
• Record Not Reportable - If a valid approval number has been collected for the transaction.

 

Waste Stream can be linked to various items via Favourites in Administration:

• Products
• Clients

Tip: If your products can be cleanly grouped by waste stream, you would associate one waste stream to the product, and it would then automatically be selected in ticketing, and recorded on the ticket.

If the product is only used by a subset of waste streams (eg, C&I or C&D) you can associate both with the product, and then the ticketing operator will only need to select between the two option.

The Municipal waste stream waste needs to be further refined by sub-stream. Non-municipal waste streams need to use the “N/A” (not applicable) was sub-stream.

POEO 2015: There are no changes to the sub streams available. Only the name of the category has changed from Waste Sub Streams to Municipal Sub Streams.

Municipal Sub-Stream can be linked to various items via Favorites in Administration:

• Products
• Clients

Tip: If your products can be cleanly grouped by municipal sub-stream, you would associate one sub-stream to the product, and it would then automatically be selected in ticketing, and recorded on the ticket.

As all non-municipal sub streams are all “N/A”, it may be possible to simply link ‘Not Municipal” as the sub-stream for commercial only clients.

 

Material Composition can be linked to various items via Favorites in Administration:

• Products
• Clients
• Vehicles

Tip: If your products can be cleanly grouped by material composition, you would associate one material composition to the Product, and it would then automatically be selected in ticketing, and recorded on the ticket.

POEO 2015: This category was previously called Material Composition and is now called Waste Type. The items available have also changed in the new legislation and you should contact OEH directly for assistance in understanding the changes to your existing material compositions classifcaitons.

Vehicle Types are only required to be captured if you are using vehicle type weight conversions (deemed weights). If not, this can be left blank, and it will default to the required “N/A” in the reports.

However, if you wish to record the OEH Vehicle types, simply link these in the vehicle tab in Administration.

POEO 2015: Local Government Areas are no longer required for reporting to the OEH so this has been removed.

There is a weight conversion table in Administration that contains the OEH weight conversions loaded by the data pack.

Warning: There is currently no need to edit this pre-loaded data, so do not use this tab, or give any users permissions to edit it.

This category is used to track purpose of outbound movements of waste from your site. This is recorded against the destination location. This information is also required when material is transfer between your own sites, so any locations that receive material from you other sites will need this category defined.

Note: If no destination purpose is recorded then it will be reported as N/A.

POEO 2015: This category is new in the POEO 2015 legislation.

In order to generate the Section 88 Report, all site facilities have to be identified. This is done by linking site locations to a Facility category.

Note: If your site has multiple facilities, you will need to setup your facilities. If you have multiple facilities and do not create the facilities for them, you will only be able to generate the OEH reports by site.

You can create the Facilities in the categories tab in Administration. Change the Category filter to Facility.

1. Set the name of the facility.
2. Enter the EPA license number in the Code field.

If your site only has a single licensed facility, you will only need to set the Facility at the top level location of the site. All locations underneath this location will inherit the facility ID of the parent.

Note: The defaulting of the facility will not show in the sub locations when your select them but any reporting will make use of the inheritance.

If your site has multiple facilities, you can set the default one at the top level (see the step above), and then override the facility for the sub facility.

Note: Note that the facility configuration can be done at any time prior to generation of the submission reports. The submission reports reflect the current configuration of the facilities.

As part of the POEO 2015 legislation all waste received or sent to an other licensed waste facility must be indicated against a transaction by capturing the sites EPA license number. This is managed the same way as your own EPA license number, by using the Facility categories.

You will need one external location for each site and EPA license number that you engage with. If a site that you use has two possible EPA license numbers then a separate location for each will need to be created.

Note: As with internal site facilities it is possible create child locations that will default to their parents Facility code. However you will only see this occurring in reporting and will not appear in the ticketing system.

POEO 2015: This requirement is new in the POEO 2015 legislation.

There are two attributes of vehicles that you may wish to configure.

1. Vehicle Type - If you are using weight conversions for net weight determination, you will need the vehicle type configured.
2. Actual License Plate - If you are using asset numbers as shortcuts for the license plates used in ticketing so they sort differently, you may wish to configure the Actual License Plate in administration. This will then appear on the Export EPA Data report.

There are three exemptions in effect that require a Deduction Identification Number (DIN):

• Approved community services exemptions
• Approved emergency incidents exemptions
• Approved usage deductions

These are handled by exemption events. Generic exemption types have been included in the data pack for community services, emergency incidents, and approved usage.

However, for emergency incidents, you may wish to create your own events for the specific incidents.

It is a requirement that all vehicle movements on a site be recorded. This includes visitors and service vehicles arriving at the site. These transactions are managed as levy exemptions and can be applied to:

• Locations
• Clients
• Products

It is also possible for the operator to apply the exemption at the time of the transactions (see below for further instruction on recording exemptions at the time of the transactions)

Note: No code is required for these exemptions.

POEO 2015: This requirement is new in the POEO 2015 legislation.

Community services exemptions are typically against a client. It is simplest to configure these in admin against the client. To do this, go to the Clients tab in admin, and select the default “Community Services” event, and enter their EPA Approval Number in the Levy Exemption Code field. Then, when tickets are generated for this client, the exemption will automatically be applied, and their approval number recorded.

For emergency incidents, you may wish to create new events for each incident, and record the specific Approval Number in the default code for that event. That specific event can be linked to either a location, a product, or manually selected in ticketing.

For Approved Usage recording, the default loaded “Approved Usage” event must be used.

This should then be recorded against an “Onsite Usage” location as a Destination Exemption Event, and the DIN entered. A Levy Exemption Note should also be set here to populate the “Approved Purpose” note required for the Section 88 report.

1. Select the Approved Usage event for the destination on site
2. Enter the DIN number
3. Enter the purpose

Note: You cannot create and use your own events for Approved Usage as the OEH reports need to be able to make the distinction between the exemptions and the Approved Usage Deductions.

The operator can select the exemption in ticketing and manually enter the DIN. The notes are the notes that will show on the section 88 report as the “approved purpose"

1. Select the Approved Usage event for the destination on site
2. Enter the DIN number
3. Enter the purpose

When a contract is created that uses a product with a levey the system will require an EPA Permit number. This EPA Permit number can be used for an approval number or if not levy exempt then use NA. The WARRP report will then include these products in the standard waste received section.