Don’t panic, ubidata’s experts are in regular contact with authorities to get answers to your questions.
We strive to have our solution validated by responding to your company’s constraints.
Below are some of the answers we received after our conversations with OVAM and LMB.
If you still can’t find the answer to your question… send us a message:
We will do everything we can to get you started!
Can the contents of an IDF be changed?
No, once the form is signed by the Dealer, it may no longer be modified.
This means that all modifications must be logged in a logbook that links the modification to a date + time and the person who made the modification.
This log is an integral part of the transport document.
There are two parties that can modify the content of the form (Dealer and carrier).
The processor can additionally modify the weight.
There are two parties that can make additions (processor and carrier).
The fields they can add are limited and known (geolocation and signatures + optional comments and photos).
This means that all modifications must be logged in a logbook that links the modification to a date + time and the person who made the modification.
This log is an integral part of the transport document.
There are two parties that can modify the content of the form (Dealer and carrier).
The processor can additionally modify the weight.
There are two parties that can make additions (processor and carrier).
The fields they can add are limited and known (geolocation and signatures + optional comments and photos).
What date should be included as the transport date if a transport is over several days?
Transports that take place over several days must include the departure date as the transport date. This is by analogy with the EVOA regulations.
What if multiple shipping addresses are used in one shipment?
A form must be prepared for each shipping address.
For non-hazardous waste, an IDF is not required for milk rounds. If this is drawn up anyway to serve as proof of deposit, a form is provided for each shipping address.
For hazardous waste, it is provided anyway that for milk rounds (collection via collection round) a separate form is provided per producer.
For non-hazardous waste, an IDF is not required for milk rounds. If this is drawn up anyway to serve as proof of deposit, a form is provided for each shipping address.
For hazardous waste, it is provided anyway that for milk rounds (collection via collection round) a separate form is provided per producer.
Can I add more than 1 waste type on a transport document?
When there is the same
– shipping address,
– dealer ,
– carrier
– and processor,
there can be several wastes added on one form.
This is analogous to the paper IDF.
– shipping address,
– dealer ,
– carrier
– and processor,
there can be several wastes added on one form.
This is analogous to the paper IDF.
Does the unique number of an form always remain the same, or does it change depending on who changed the form?
For example, are the first three letters then changed?
For example, are the first three letters then changed?
No, the unique number is always retained from the creation of the form and never
never changes. Moreover, it is the person who signs the form for the first time who is
responsible for the content and changes to the content of the form, not the
system.
So where can be seen who modified what?
That should be visible in the change log.
This does mean that the party initiating a document must always know who has made changes/additions to the form.
never changes. Moreover, it is the person who signs the form for the first time who is
responsible for the content and changes to the content of the form, not the
system.
So where can be seen who modified what?
That should be visible in the change log.
This does mean that the party initiating a document must always know who has made changes/additions to the form.
May the processor change EURAL codes after the completion of the transport?
It is not the intention of the processor to change the EURAL code yet.
It is the responsibility of the Dealer (or producer making its own arrangements) to ensure that
He must choose a carrier and processor on this basis that can transport and accept the waste.
If the EURAL code really does not match the content of the waste delivered, the
processor can always refuse the shipment, or hold the Dealer accountable.
OVAM does not allow the processor to change the EURAL after the arrival of the transport.
It is the responsibility of the Dealer (or producer making its own arrangements) to ensure that
He must choose a carrier and processor on this basis that can transport and accept the waste.
If the EURAL code really does not match the content of the waste delivered, the
processor can always refuse the shipment, or hold the Dealer accountable.
OVAM does not allow the processor to change the EURAL after the arrival of the transport.
Should the OVAM number of the Dealer site be on the form?
The OVAM number is listed as a mandatory field in the current legislation VLAREMA 8, but this fall the subsequent legislation VLAREMA 9 will come into effect.
In this, the OVAM number has been replaced by the identification number.
Therefore, OVAM has asked to develop the digital system immediately with identification number, to the new legislation, and not to include OVAM-nr.
To be precise, the current legislation states that the “registration number” must be specified for the Dealer. In the sample paper identification form, this is interpreted as the OVAM number, but this can also be interpreted as ‘identification number’.
In this, the OVAM number has been replaced by the identification number.
Therefore, OVAM has asked to develop the digital system immediately with identification number, to the new legislation, and not to include OVAM-nr.
To be precise, the current legislation states that the “registration number” must be specified for the Dealer. In the sample paper identification form, this is interpreted as the OVAM number, but this can also be interpreted as ‘identification number’.
WASTE PRODUCER who does not have an e-mail address…
You need to code a waste producer who is a private person but has no email address.
Without this email address, with ubidata solution, he cannot receive an email with the pdf document nor connect to ubiDOCS web platform to access the transport documents.
The WASTE DEALER has a duty to provide a copy a the producer.
The WASTE DEALER must be able to prove that the producer received a copy, if necessary of the pdf.
He can send it by mail if necessary.
ubidata provides a functionality for this purpose and it is not ubidata’s responsibility if one cannot/will not use this functionality, but that of the WASTE DEALER.
Without this email address, with ubidata solution, he cannot receive an email with the pdf document nor connect to ubiDOCS web platform to access the transport documents.
The WASTE DEALER has a duty to provide a copy a the producer.
The WASTE DEALER must be able to prove that the producer received a copy, if necessary of the pdf.
He can send it by mail if necessary.
ubidata provides a functionality for this purpose and it is not ubidata’s responsibility if one cannot/will not use this functionality, but that of the WASTE DEALER.
hazardous waste milk rounds: how do I enter weights at delivery ?
A driver is instructed to visit various collection sites to load small quantities of hazardous waste for which IHM may or may not provide a weight estimate.
They are picked up and are all weighed together at the weigh station.
How should transport documents be completed individually based on the total weight?
Indeed, it is not realistic to weigh each load individually, and the driver is unlikely to be able to split the different loads when unloading.
OVAM imposes at least 1 IDF per customer (if all actors involved are the same, multiple eural can be on 1 IDF).
The final weight may be estimated in this case.
OVAM says number of customers, number of recipients and volume of recipients should play a role in the estimate per customer. Same as for Matis notifications.
They are picked up and are all weighed together at the weigh station.
How should transport documents be completed individually based on the total weight?
Indeed, it is not realistic to weigh each load individually, and the driver is unlikely to be able to split the different loads when unloading.
OVAM imposes at least 1 IDF per customer (if all actors involved are the same, multiple eural can be on 1 IDF).
The final weight may be estimated in this case.
OVAM says number of customers, number of recipients and volume of recipients should play a role in the estimate per customer. Same as for Matis notifications.
Should the estimated weight at the end of the process be validated/corrected in our system if the COLLECTOR sends and processes the exact weight in another system?
OVAM would prefer that we do, but the legislation does not require it:
“So long as there is no interoperability, we understand that is difficult. Afterwards, it should be fairly easy to do that on IDF as well. As mentioned, the legislation allows the weight to be provided on a separate document. Because that document must remain with the IDF, we do ask that the reference (unique code) of the IDF then be provided on that separate document.”
“So long as there is no interoperability, we understand that is difficult. Afterwards, it should be fairly easy to do that on IDF as well. As mentioned, the legislation allows the weight to be provided on a separate document. Because that document must remain with the IDF, we do ask that the reference (unique code) of the IDF then be provided on that separate document.”