New DLC Policy: DLC Surveillance Testing Policy
The DLC is pleased to release the 2018 update of the DLC Surveillance Testing Policy, effective Monday, September 10, 2018. Below is a high-level summary of clarifications and changes to the policy.
Summary of Changes:
Product Selection and Procurement:
- Products will be procured directly from the manufacturer rather than through a distributor.
- A manufacturer that has three (or more) selections in two consecutive rounds, all of which yield passing results, is exempt from having another product selected in the following round. This exemption is expected to be equivalent of 6-12 months. Please note that this applies on a “go forward” basis – results from rounds prior to this policy’s effective date will not count.
- By accepting a selection, manufacturers indicate that the product can be procured within eight weeks (unless otherwise agreed upon).
- All user accounts who submit applications for an organization will be notified that a product has been selected. The organization will then designate two main contacts for that selection, as they have done in the past.
- The DLC may select products randomly for testing as a baseline control group.
- The policy provides increased guidance to manufacturers about voluntarily de-listing products from the QPL.
Product Testing and Evaluation:
- Table 2 has been revised to only include light output, system wattage, and CRI.
- Products requiring testing in a reference housing will have the housing selected by the DLC from the approved reference housing list. Manufacturers may provide a preferred listed reference housing at their own cost.
- “Dual Mode” products (UL Type A and B) will be tested using a ballast.
- A product must fall within the same ANSI CCT bin from qualification to be considered compliant with Table 1. Flexible binning is allowed, per the standard.
- The Table 1 efficacy requirement has changed from -3% to -4%.
Consequences and Appeals:
- The policy clarifies general intent and limitations of consequences from the program.
- The policy specifies consequences for non-compliance outside of product testing (e.g. missing published deadlines, declining selection, etc.).
- The policy provides guidance on re-listing products.
- The timeframe to submit an update application (when a product fails Table 2) has changed from 10 business days to 15.
Safety Certification Verification:
- A new section of the policy addresses compliance of safety coverage documentation resulting from the SSL V4.3 Technical Requirements changes.