I review about 200+ industrial lighting installations every year. Emergency lighting, specifically ABB systems, probably accounts for a third of those. And I’ve seen the same handful of mistakes repeated more times than I care to count. Mistakes that, frankly, cost time and money.
This checklist is for anyone specifying, receiving, or commissioning an ABB emergency lighting system for a commercial or industrial project. It’s not a theoretical guide. It’s the five steps I run through on every single inspection. Follow it, and you’ll catch 90% of the issues that normally slip through—the kind that cause a $22,000 redo (yes, that happened).
Step 1: Verify the Model Number Against the Bill of Materials (BOM)
This sounds trivial. It’s not. In Q1 2024 alone, we rejected 12% of first deliveries because the model number on the box didn’t match the approved BOM. An ABB emergency lighting fixture might look identical across three model numbers, but the difference could be in the battery chemistry (NiCd vs. NiMH), the lumen output, or the control interface for the IoT platform.
What I do: I pull the BOM before the shipment arrives. As each pallet comes in, I cross-check the model number on the outer carton against the line item. If there’s a mismatch, I flag it immediately. Don’t assume the packing list is correct—I’ve seen a perfectly packed pallet of the wrong Model S that got through, because the picker grabbed the wrong shelf.
Watch out for: Look for suffixes. ABB’s model numbers often have revision suffixes (like -R1 or -R2) that indicate a firmware or component revision. These might not be interchangeable if they affect the system’s compatibility with your ABB Ability control system.
Step 2: Check the Battery Date Code—Don’t Get Stuck with Dead Stock
Here’s one most people skip. Emergency lighting batteries are consumables. They start aging the day they’re manufactured. An ABB emergency lighting fixture might sit in a distributor’s warehouse for six months before it reaches your site. If the battery is already six months old from the manufacturer, you’ve lost a year of its rated life before installation.
What I do: I check the date code printed on the battery itself (not the fixture’s outer box). I look for the manufacturing week and year. My rule of thumb: I reject any battery older than six months from the date of delivery. Is that strict? Maybe. But I was burned once with a batch of 50 units that had batteries already two years old. We had to replace 12 of them within the first year. That cost us the margin on the entire project.
ABB specifics: ABB’s battery packs usually have a YYWW format (year and week). For example, 2427 means the 27th week of 2024.
Step 3: Run a 90-Minute Discharge Test—On the Ground
The sticker on the box says the unit can run for 90 minutes. The brochure says it can run for 90 minutes. But I’ve tested units fresh out of the box that failed at 67 minutes. The cause? A shipping vibration that had loosened a connection, or a minor manufacturing defect in the driver. The only way to know is to test it.
What I do: Before I install a single fixture permanently, I take a random sample (usually 5% or 10 units, whichever is more) and run a full 90-minute discharge test on the bench. I note the exact time to failure. I also check the light output at the 90-minute mark. Some units that “pass” might be dimming significantly, which could still be a code violation depending on your exit light requirements.
The mistake I made: I used to trust the factory test sticker. I don’t anymore. A whole batch of units had “tested OK” stickers on them, but the test had been run on a pre-production sample, not on the production run. We only caught it because a junior engineer decided to retest one fixture. It was dead at 52 minutes.
Step 4: Validate the IoT Commissioning Report (ABB Ability)
If you’re using ABB’s IoT-enabled emergency lighting, the lights are supposed to report their health status to the central platform. But “supposed to” and “actually is” are two different things. I’ve walked into control rooms where the platform showed 100% green for emergency lighting, but physically, half the lights were on the wrong network segment and were effectively invisible to the system. The platform was checking itself, not the lights.
What I do: I take the commissioning report from the system integrator and I spot-check it physically. I pick five random fixtures from the report and go to their physical location. I check that the fixture’s serial number on the tag matches the serial number in the ABB Ability dashboard. I then verify that the last health check timestamp updated within the last 24 hours. If the timestamp is three days old, the light might not be communicating.
A quick fix: If the communication dropped, it’s often a power line coupling issue. The electrician might have skipped the ferrite core on the data line. It’s a $2 fix that a non-expert crew wouldn’t think of.
Step 5: The ‘Night Shift’ Visual Walkthrough
You can’t test emergency lighting effectively during the day in a warehouse with skylights. I learned this the hard way. We had a project where the emergency lighting path was technically “lit,” but the light level was so low that the path was virtually invisible under the wash from the high-bay lighting. The test passed on paper, but it was a failure in practice.
What I do: I schedule a walkthrough with the facility manager after sundown or with the high-bay lights turned off. We walk the egress path and visually confirm that the illuminated path is obvious. I also check for shadows cast by racking or machinery that might create dark holes during a power failure. You can have perfectly functioning lights and a dangerous egress path if the fixture placement wasn’t designed around the actual floor layout.
Final Thought: The Redo That Paid for This Checklist
I’m passing this on because I don’t want anyone else to go through our fiasco in 2023. We commissioned a $180,000 emergency lighting retrofit for a distribution center. We followed the spec. We ticked the boxes. The ABB system was installed. The discharge tests were run—in the warehouse, during the day. Everyone signed off. Then the first real power test happened during a night shift, and the facility manager called me in a panic. You could barely see the path. The IoT logs showed everything was green, but there was a database error that was overriding the actual light sensor data—a software bug in the commissioning script. The system was reporting a lie.
That quality issue cost us a $22,000 redo and delayed the launch by three weeks. The root cause wasn’t the hardware. It was the verification process. We fixed the process. Now I run this checklist. You should too.