How do I manage bulked up loads in Mandalay CS for use in my regulatory reporting?
Bulked up loads refer to waste loads that include multiple waste streams. These generally occur in the following scenarios.
- Waste collection routes that cover both commercial and municipal waste.
- Waste transfer from a transfer station to a landfill where the transfer station received both commercial and municipal waste.
The following article explains how to apply a % split between waste streams to transactions recorded in Mandalay CS that are based on the above scenarios, retrospectively during the submission process.
Bulked Up Transactions
Transactions that match the bulked up load scenarios above will need to be recorded correctly so that the submission process will identify these transactions and apply the necessary expansion to a specific % split. These transactions must be recorded with the following regulatory classifications.
Waste Class : Bulked Up (BU)
Waste Stream: Bulked Up (BU)
The other classification codes should be based on your state regulators data classification pack but the submission process will fail if a transactions doesn't have BU in both the class and stream categories.
Customers affected by the QLD levy requirements should refer to section 3.2.2 of the detailed data file specifications for examples of these scenarios
For each possible source of a bulked up load a locations should be defined. For collections routes a location for each route should be established. For waste from transfer stations the source locations can either be a location within the specific CS site or from an external site. Using an external site for waste transfers is usually required where a site is setup in the Mandalay CS system.
Defining the bulked up loads by source is important for the next step where a contract is used to manage the split of a bulked up load.
Bulked Up Contracts
Currently the method for determining the split of the bulked up loads is to define a specific type of contract that includes the breakdown of the bulked up loads. These contracts do not need to be collected against the bulked up load transactions but need to match the transaction details for the the correct contract to be matched against the transactions.
The submission process will look for a matching contract based on the following detailed in the transaction:
- Client
- Source Location
- Destination Location
- Transaction Date Out
If the submission process locates more than one contract that meets a transactions setup, it will raise an error and the contracts will need to be reviewed and corrected to ensure only one contract matches the requirements.
To create a contract for the purpose of processing bulked up loads use the following steps.
Create a new contract from the contract tab in Administration
Set the contract type to Bulked-Up Load Contract
If you wish to make use of a time based contract that refer to the section below.
Set the client, source and destination for the transactions this contract should be matched against.
Define the split of the load using the products ordered section of the contract. You will need to define the product, waste stream, waste class, waste stream, material type and % portion for each component of the bulked up load.
Each value in the products ordered section is required and the submission process will validate these contracts when being run. The proportion is defined as a % value and the sum of all proportions need to equate to 100.
To help define the proportion of waste in a bulked up load from a transfer station a report split on waste into the source transfer stations based on waste stream would be beneficial.
Note: It is possible to have only one product but its proportion must equal 100.
Press apply to save the contract.
Note: These contracts should not be used directly against a transaction. They are only used for the submission process in triggering a transaction to be split based on the defined values.
Time Based Contracts
The submission process will look for contracts that are either non time based or if they are effective for the date of the transaction (date out).
Bulked Up Load Expansion
Because the bulked up contract is only used to expand a bulked up load at the time of the submission, these contracts only need to be defined when the submission process begins.
The submission process will expand the transaction for the purposes of reporting to the state regulator.
At this stage the expansion is not saved back against the Mandalay CS transaction so reports run against the CS database in WBR will not reflect the expanded result of a bulked up load. This may change in a future release of the naus Regulatory Management application.