ML50-QR

The introduction of LED lighting in urban and street lighting has opened up many new areas of activity. However, both improved dimming capabilities and simpler control systems present new challenges for operations management. For many years, it was sufficient to simply document the luminaire model and the type of lamp used. In the early years, LEDs were an insignificant component in street lighting operations due to their low failure rates. By their tenth anniversary, however, the first significant failures began to occur. This immediately raised the question: Which ballast is installed? Which lens determines the light distribution? And how can I find the correct replacement for the defective components? Although it was possible to consult the database, the quality and completeness of the documented information were not always sufficient to make informed decisions regarding replacements. In discussions with luminaire manufacturers, programmers, and operators, there was a consensus: a standardized format for luminaire information and a clear interface to the database are desirable.

The ML50-QR was developed to meet these needs. The QR code, which stands for "Master Light with 50 data records in the QR format," serves as the basis for standardized documentation of the most important parameters of streetlights.

Providing the light fixture data as a QR code

The data must be provided in a specified order in the form of a clearly legible QR code. A QR code must be visibly placed near the LEDs so that it is easy to scan (either inside or outside the lamp cover). In addition, another scannable code must be attached to the end of the cable. A third code must be included in the packaging. A QR code must be printed on the cardboard box (if feasible, this may be on adhesive film so that it can be removed and reapplied—in which case the adhesive patch inside the box is not necessary). The following specifications must be followed:

• The QR code must be able to contain uppercase and lowercase letters, numbers, special characters, and control characters such as <Return> or <Tab>. Numeric values must be written in Arabic numerals.
• Each data record or row ends with a line break.
• A line break consists of CR and LF (Windows standard).
• All decimal numbers must be written with a decimal point.
• There must be a digit on both sides of the decimal point, for example, “1.0,” “15.0,” or “11.8.”
• If the absolute value of a number is less than 1, there must be a zero before the decimal point, for example, “0.7.”
• Thousands separators are not allowed.
• If no value can be entered for a required field, you must enter “--”.
• All text must be encoded in UTF-8.
• Use error correction level "H" for the QR code.
• All fields must be displayed, even if they are not required and cannot be filled in.
• Each field is terminated with <CR+LF>, even if it is left blank.
• The image below—or at least the label "ML50"—should be placed directly in or next to the QR code in an appropriate size.

Lighting Data Overview

Options via the QR code

The QR code can be scanned directly using luxData products, and all 50 data points are then recorded in the luxData database. There are several customizable options for processing the data in the database. One option is to compare the scanned data with the planned data for the task, so that the technician receives feedback on whether the most important values match. For example, if the lumen value does not match, the technician receives an error message stating “Incorrect lumens installed.” The goal is to ensure that, through a standardized sequence—e.g., “number ‘1’ is always the manufacturer’s designation,” etc.—clear mappings of the data to the corresponding database fields are possible. This eliminates the need for each manufacturer and operator to program their own interface. Furthermore, all parties involved would then have more time to focus on the new opportunities offered by optimized operations management.