Reference · built on requestOperator by FibricEnergy & demand

Generator Test

Reads the generator run log, the CMMS test interval, air-quality forecasts, and occupancy, and proposes a test slot with its work order.

Request accessPricing ↗

About

An emergency generator has to be exercised on a schedule, and the hours it runs are counted. Under 40 CFR 63.6640(f), an emergency stationary engine may run for maintenance checks and readiness testing up to 100 hours per calendar year. A test on a bad-air day or during a full house draws complaints and, in some districts, a notice.

Generator Test reads run hours, starts, and alarms from the generator controller over Modbus TCP, the scheduled maintenance interval and meter readings in your CMMS, the daily AirNow forecast and OpenAQ readings near the site, and the occupancy schedule. It proposes a test slot that satisfies the interval, avoids forecast poor-air days, and lands in a quiet hour, with the work order and the hours budget attached. Approving it files the work order, and the run is confirmed from the controller afterwards.

This is a reference listing. It documents what Fibric would read from Generator 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

  • Run state, run hours, start count, and active alarms from the generator controller over Modbus TCP
  • ScheduledMaintenance jobs and their triggers in Fiix, or meters and meter triggers with their work order templates in MaintainX
  • Past test work orders and MeterReading rows on the generator asset, so the last completed test is known
  • The AirNow forecast for the site's reporting area, issued once per day, and the latest OpenAQ readings from monitors nearby
  • Occupancy schedules and door events from your access control platform, to find the quiet hours
  • Hours run this calendar year against the testing allowance, kept from the controller's own counter

Proposed actions

  • Target capability: propose a test slot and the work order for it in Fiix or MaintainX, with the controller readings attached
  • Target capability: propose moving a scheduled test when the AirNow forecast for that day is poor, and name the next clear slot
  • Target capability: propose a MeterReading of run hours against the generator asset once the controller shows the test ran
  • Target capability: propose closing the work order with the run's start time, duration, and alarms for the technician to confirm
  • Target capability: propose an early review when hours run this year approach the testing allowance

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

What you can build

  • Keep the exercise off bad-air days

    Read the Fiix scheduled job and the AirNow forecast, and get a proposed slot that meets the interval and skips forecast poor-air days. Approve it and the work order is filed with the controller's readings.

    With Fiix, Air Quality, Modbus TCP

  • Confirm the run from the controller

    After the slot, run hours and starts from the controller over Modbus TCP become a proposed MeterReading and a proposed closure in MaintainX, so the record matches what the engine did.

    With Modbus TCP, MaintainX

  • Test when the building is empty

    Door events and schedules from Brivo show the quiet hours. The proposed slot lands in one, and the work order says why that hour was chosen.

    With Brivo Access, Fiix

Requirements

  • A Modbus TCP connector reaching the generator controller, with run state and run hours in the point map
  • A CMMS connector such as Fiix or MaintainX with the generator listed as an asset and its test interval as a scheduled job
  • The OpenAQ air-quality signal with the site's location, and an AirNow API key for the forecast
  • An access control connector or a written occupancy schedule, for the hours a test should avoid
Authentication
Reads the controller through the Modbus connector's register allow-list, files work orders and readings through the account your CMMS connector holds, reads AirNow and OpenAQ with their free API keys, and reads access schedules read-only.

Limits

  • It reads hours from the controller's counter. A controller replaced mid-year, or one without a run-hours register, breaks the tally.
  • AirNow issues its forecast once a day and OpenAQ monitors may sit some distance from the site. Both inform the slot; neither is a permit.
  • Your permit may cap hours below the federal allowance or require notice. The operator applies the figure you give it, not one it assumes.
  • It proposes a slot and a work order. It never starts the engine, and it does not declare a test passed.

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 Generator Test ↗

Questions and answers

What do you approve before a test is scheduled?
The slot and the work order: the date and hour, the interval it satisfies, the AirNow forecast and OpenAQ readings for that day, the occupancy it avoids, the hours used this year, and the draft work order. You can move the slot or change the assignee before it is filed.
What record is left after the test?
A receipt with the proposed slot, the work order id, the controller's start time, duration, and alarms for the run, the MeterReading filed, who approved each step, and the hours tally after. A test that never ran is recorded as missed, with the reason.
Does it ever start the generator?
No, and it cannot. It reads the controller and writes nothing to it. The technician on the work order starts the engine, and the operator only confirms afterwards what the controller recorded.
Ask about Generator 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