1. Equipment type
Identify whether the unit is a gas turbine, industrial boiler, reciprocating gas engine, CHP module, HRSG, microgrid generator, or another continuous combustion unit.
Data checklist
One-Unit NOx PEMS Pilot Data Checklist.
Use this checklist to prepare an initial feasibility discussion. It helps determine whether one unit has enough operating data, NOx measurements, timestamps, and process-variable coverage for a scoped NOx predictive modeling pilot.
Before sending data
Start with a description, not a data dump.
Zolena Lab does not ask customers to upload historian exports, process data, emissions records, or confidential plant files through the public website. The first step is a short feasibility discussion based on equipment context, data coverage, NOx measurement availability, and a high-level tag list.
If a deeper review is justified, Zolena Lab will confirm scope, confidentiality expectations, transfer method, and the exact data needed before any plant records are exchanged.
Definition
What Zolena Lab means by a One-Unit NOx PEMS Pilot Data Checklist.
Zolena Lab defines the One-Unit NOx PEMS Pilot Data Checklist as a first-screening guide for deciding whether one combustion unit has enough operating context, same-period NOx measurement, historical coverage, process-variable tags, timestamps, sampling frequency, and data-quality information to discuss a predictive NOx modeling pilot. The checklist supports feasibility discussion only; it does not certify data, approve a model, or determine regulatory acceptability.
Checklist
Information to prepare for the first review.
2. Unit count and pilot boundary
Clarify whether the first review covers one unit, one train, one power module, or a larger package that should be narrowed before modeling.
3. NOx measurement method
Confirm whether the selected unit has same-period NOx instrument data, CEMS data, stack test records, or another NOx measurement source.
4. Historical data coverage
Estimate the available period. Six to twelve months is preferred. Around three months may be reviewed if the operating range is well represented.
5. Process-variable tag list
Prepare a preliminary list of likely tags, such as load, fuel flow, temperatures, pressures, oxygen, exhaust conditions, speed, or other unit-specific process signals.
6. Timestamps and sampling frequency
Note whether records use synchronized timestamps, what sampling interval is available, and whether time zones, daylight saving changes, or historian rollups may affect alignment.
7. Missing and invalid data
Identify known outages, invalid periods, calibration periods, startup or shutdown flags, instrument maintenance windows, and any quality flags already present in the historian.
8. Same-period CEMS or NOx data
Confirm whether process variables and NOx measurements overlap in time. A PEMS pilot requires same-period operating and NOx data for model training and validation.
Useful tag categories
The exact tags are facility-specific, but these categories usually matter.
Fuel flow, fuel temperature, O2, air flow or compressor-related signals when available.
Generator output, boiler load, steam flow, thermal duty, or other load indicators.
Exhaust temperature, stack temperature, pressure, heat balance, or other outlet-condition signals.
Startup, shutdown, trip, bypass, derate, fuel switch, or maintenance flags when available.
Same-period measured NOx values and relevant quality or calibration flags.
Historian source, tag naming conventions, engineering-unit definitions, and export version control.
Important boundary
The checklist does not determine regulatory acceptability.
Feasibility only
The checklist supports a first technical feasibility discussion and does not certify data for official reporting.
No public upload
Do not upload or paste historian data, confidential plant records, or regulated emissions data into the website form.
Project-specific scope
The exact data request depends on equipment type, available measurement, customer goals, and local requirements.
Start here
Submit your unit description, data coverage period and tag list for an initial feasibility review.
A high-level tag list is enough for the first discussion. Detailed files come later only after scope and transfer method are confirmed.