Reference · built on requestOperator by FibricSafety, security & compliance

Emergency Lighting Test

Reads self-test results from DALI emergency luminaires and proposes retests, replacement work orders, and the test log entry.

Request accessPricing ↗

About

Emergency Lighting Test is an operator for self-contained emergency luminaires on a DALI bus. Control gear built to IEC 62386-202 runs two tests on command or on a timer: a function test of the battery, charging circuit, driver, and lamp, and a duration test that runs the lamp for its rated time. The operator reads each result, the failure it reports, and when the next test falls due.

It proposes a retest for a failed function test, a work order for a luminaire that fails a duration test or fails twice, and one row in your test log for every result, pass or fail. A person approves each proposal. The operator never starts a test on its own and never marks a luminaire as passed.

This is a reference listing. It documents what Fibric would read from Emergency Lighting Test and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Function test and duration test results from DALI device type 1 control gear, with the failure each luminaire reports
  • Test due dates from the timer on each luminaire, or from the schedule you keep for manual and computer-based testing
  • Battery, charging circuit, driver, and lamp failures a luminaire reports between scheduled tests
  • Open work orders and asset records in UpKeep, MaintainX, Fiix, or Limble CMMS, so a failed luminaire already ticketed is not ticketed again
  • The test log you keep in Google Sheets, Microsoft Excel, or SharePoint, including the last recorded result for each luminaire
  • Luminaire addresses, locations, and rated durations from your DALI commissioning records

Proposed actions

  • Target capability: propose a retest of a luminaire whose function test failed, at a time you set, for your approval
  • Target capability: propose a CMMS work order for a luminaire that fails a duration test or two function tests, naming location and failure
  • Target capability: propose one row per result in your test log, with the luminaire, test type, time, outcome, and who approved it
  • Target capability: propose a due list of luminaires whose monthly or annual test is late, so a person can schedule it
  • Target capability: propose the start of a scheduled duration test on the luminaires that are due, which a person approves before any test runs

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Log every self-test without a clipboard

    Each function test result from the DALI bus becomes a proposed row in your Google Sheets log. Approve the batch once a month and the log stays current, with a receipt for each row.

    With DALI Lighting, Google Sheets

  • Turn a failed duration test into a work order

    A luminaire that cannot run its rated duration gets a proposed UpKeep work order naming the fitting, its location, and the failure. You approve it, and a retest is proposed once the work order closes.

    With DALI Lighting, UpKeep

  • Find the annual tests you are about to miss

    Before the 12-month window closes on a luminaire's last duration test, the operator proposes a due list and a test window. You approve, and the MaintainX work order carries the schedule.

    With DALI Lighting, MaintainX

  • Keep the record where the auditor looks

    Results and approvals land in the workbook on SharePoint your safety officer already opens, one row per test, so the paper trail matches what the bus reported.

    With Microsoft SharePoint, DALI Lighting

Requirements

  • A DALI Lighting connector reaching control gear built to IEC 62386-202, through a gateway that exposes test commands and results
  • One field service or CMMS connector such as UpKeep, MaintainX, Fiix, or Limble CMMS, with rights to create work orders
  • One files connector such as Google Sheets, Microsoft Excel, or SharePoint, holding the test log you already keep
  • A list of luminaires with their DALI address, location, and rated duration
Authentication
It uses the gateway credentials of your DALI Lighting connector to read results and the credentials of your CMMS and spreadsheet connectors to write, and keeps no credentials of its own.

Limits

  • It reads results the control gear reports. It cannot see a luminaire that is off the bus or a gateway that has dropped offline.
  • A DALI result is not an inspection. Someone still walks the route where your code requires a visual check.
  • Emergency units that are not DALI control gear are logged only from results a person enters by hand.
  • Test intervals and durations come from the code your jurisdiction applies, which you configure. The operator does not decide which code applies.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Emergency Lighting Test ↗

Questions and answers

What does a person approve before anything happens?
Every proposal: a retest, a work order, a log row, or the start of a scheduled test. You see the luminaire, its address, the result it reported, and the text that would be written. Approve, edit, or dismiss. No test starts and nothing is written until you do.
What record does a test leave?
One log row per result, with the luminaire, test type, time, outcome, and the approver. Every proposal keeps a receipt of what was written to the CMMS or the sheet, why, and how to undo it. Dismissed proposals are kept as well.
Does it ever start a test or clear a failure on its own?
No. It reads results and due dates. A test starts only when a person approves a proposed window, and a failure is cleared only in the CMMS by the person who closes the work order. It never marks a luminaire as passed.
Ask about Emergency Lighting Test

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy