Custom software for the inspection file per amusement ride
On 1 July 2023, the Dutch Decree on amusement rides and playground equipment 2023 (Warenwetbesluit attractie- en speeltoestellen 2023) replaced the old decree. If you operate rides or equipment, you need to show, per device, that the certificate is valid, when the next inspection is due and what has happened since the last one. That last part is called the current file, and it belongs to the device, not to the calendar year.
What the decree requires per device
The decree distinguishes by drive. An amusement ride moves people for entertainment or recreation using a non-human energy source. Playground equipment runs solely on gravity or on human physical force. That determines almost everything that follows: amusement rides are inspected periodically, playground equipment in principle only once. There is also the amusement ride of simple design, which stays below ten metres per second and below five metres in height.
Inspection is carried out by a designated body, appointed by the Minister of Health, Welfare and Sport. If the device complies, a certificate of approval follows and an approval mark is applied. The certificate for an amusement ride carries a final expiry date. The body determines which inspection regime applies when it issues the first certificate, using a matrix: annual, every two years or every three years.
A strict regime applies around that end date. You must apply for the inspection at least thirty days in advance. If the device cannot be inspected in time through no fault of your own, the certificate remains valid for a maximum of four more months. For playground equipment, validity only lapses after a major modification or a new standard. You also use a current file to show that the device has been properly installed, tested, inspected and maintained.
How we build this
The unit is the device, not the location and not the year. A device moves and passes to another operator, and its history should go with it.
Year of manufacture, type designation, serial number and the unique registration number from the designated body. Without that identification, a certificate is attached to a name.
Besides the final expiry date, we record when the application must be in progress. That is where things go wrong in practice, not on the end date itself.
You report a major modification or repair without delay to the body that inspected the device. The assessment that comes back belongs in the same file, because it can cause the certificate to lapse.
When a device is rented out, transferred or changes operator, the file goes with it. Whoever takes over without the history starts from zero.
What the software actually does
The device register with its deadlines carries the whole. The rest depends on the number of devices and whether you also rent them out.
One file per device
Identification, instructions for use, inspection reports, maintenance and incidents all in one place. That is the form in which a regulator asks for it.
End dates and the application deadline
The certificate's final expiry date and, before it, the point at which the application must be in progress. We build the same deadline monitoring for work equipment and lifting equipment.
Certificates and approval marks
Which certificate belongs to which device and from which body. A certificate that was altered after issue is invalid.
Modifications with the assessment attached
The modification or repair, the report to the inspection body and what it concluded. In the event of a negative assessment, a new inspection application follows.
The current file as a sequence
Inspections, maintenance, incidents and modifications in order. A file that only comes into being at the time of an inspection is a reconstruction.
Connecting to maintenance and planning
Work orders, engineers and parts are usually already held somewhere. We pull in what exists through integrations, rather than entering everything twice.
Who we build for
The number and type of devices vary widely. Four situations.
Parks with a fixed layout
Many devices on one site, with inspection regimes ranging from annual to every three years. The challenge here is deadlines that do not coincide, alongside your maintenance planning.
Device rental
With rentals, the hirer or operator reports a serious accident, and reports it to you as well. Your file therefore takes in information from outside your organisation. See also the inspection app.
Municipalities and playground operators
Many play devices with a certificate that has no end date, where attention goes to inspection and maintenance. The app for the inspection round is the counterpart to this.
Manufacturers and importers
You keep the technical construction file and the inspection report from the initial inspection: for amusement devices for the duration of their technical lifespan, for play equipment up to twenty years after production. Sharing is possible via a certification portal.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
Inspection regimes, standards and file formats change. Everything to do with device types, deadlines and document types should be configurable rather than hard-coded.
Why Appfront
The date before it counts
We set the alert at the point of application, not at the end date. The regulation requires the application at least thirty days earlier, and the grace period only applies where the delay is not your doing.
The file belongs to the device
We attach everything to the device's identification rather than to a location or a year. That way the history moves with the device.
We don't inspect anything ourselves
Inspection is reserved for a designated body. We build the file that your application and your accountability rely on.
A matrix determines the regime
Which inspection regime your device falls under is determined by the body at the first certificate, using the matrix. We adopt that outcome and do not recalculate it.
Security and privacy
A device file contains inspection reports, maintenance history and accident data. You show that to a regulator, but not to everyone who happens to be looking. We set access per role and per location, give an external inspection or maintenance company only its own devices, and log every access.
What matters most here is that a record cannot be quietly changed afterwards. An inspection entry updated after something happened is exactly the wrong evidence in an investigation. We record findings, inspection results and reports immutably with a timestamp and the person responsible, and make a correction a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy.
Frequently asked questions about the file for amusement devices
That abbreviation does not appear in the Dutch Commodities Act Decree on amusement and play devices 2023 or in the Commodities Act Regulation beneath it, so we do not use it substantively. The documents that matter are called the certificate of approval, the mark of approval, the inspection report and the current file.
Amusement rides fall into an annual, two-yearly or three-yearly regime. The designated body sets this at the first certificate, using a matrix based on accelerations, maximum speed and the number of dimensions in which the ride moves. Playground equipment is, in principle, inspected once, with a certificate that has no end date.
The drive. An amusement ride moves people using a non-human energy source; playground equipment works solely on gravity or human physical force. This results in differences in the inspection regime, in the period of validity and in the unique registration number, which applies only to amusement rides.
Who the manufacturer or importer is, the identification of the ride, the instructions for use, which inspections have taken place, maintenance, accidents and major modifications. The decree calls this the current file, which you use to demonstrate that the ride has been safely installed, tested, inspected and maintained.
You report a major modification or repair without delay to the designated body that inspected the ride or the type-representative sample. That body assesses whether the safety of people could be adversely affected. If so, the certificate ceases to be valid and you must submit a new inspection application.
The hirer or the operator notifies the Netherlands Food and Consumer Product Safety Authority without delay and, for a hired ride, the lessor as well. A serious accident is one that results in death, in permanent or other injury, or in immediate hospital admission.
No. The decree is based on the Commodities Act. The Minister of Health, Welfare and Sport designates the inspection bodies and the Netherlands Food and Consumer Product Safety Authority supervises. When siting a ride you may also have to deal with environmental law, but that is separate from the inspection.
That depends on the number of rides and locations, whether you also hire out rides and whether integrations with your maintenance system are needed. The register with deadline monitoring is usually quick to put to use and removes the biggest risk; integrations cost more. We give a well-founded estimate after the discovery phase.
Do you know when each ride is due?
Take three rides from your records and look up the certificate's expiry date, and the date by which the application must be under way. If that takes more than a few minutes, that is where the risk lies. We build this as a standalone application and as part of a broader custom software project.