In short. Compliance is shown by records. Keep a file per generator with certificates, test reports, run-hour logs, fuel and reagent records and maintenance history, and be ready to show them. Where measurements are needed, use qualified testing.
Document set per generator
| Document | Purpose |
|---|---|
| Nameplate and type certificate | Identify category |
| Approvals and consents | Authority permissions |
| Stack or emission test reports | Measured performance |
| Run-hour and load log | Operation evidence |
| Fuel and reagent purchase and quality records | Consumables control |
| Maintenance and alarm records | System health |
Monitoring
Reading → trend → deviation → diagnosis → intervention → verification.
- Record hours, load and fuel.
- Track aftertreatment signals: differential pressure, temperature, reagent level.
- Investigate alarms promptly.
- Schedule emission tests as required.
- Review records periodically.
Audit readiness
- Single index of documents.
- Dated, signed records.
- Same names and numbers across documents.
Link with RECD operation, AMC and CPCB architecture.
Illustrative example
An inspection asks for last year’s test report. The site pulls it from a dated index in minutes; another site spends days finding scattered papers and cannot confirm the date.
A document index template
| No. | Document | Location | Last updated |
|---|---|---|---|
| 1 | Nameplate photographs | Set folder | Date |
| 2 | Certificate of conformity or type approval | Set folder | Date |
| 3 | Consent or permission from the authority, if any | Site folder | Date |
| 4 | Latest stack or emission test report | Set folder | Date |
| 5 | Run log | Site log | Monthly |
| 6 | Fuel and reagent purchase records | Stores | Per purchase |
| 7 | Maintenance reports | Service file | Per visit |
What a good run log records
- Date, start and stop time.
- Reason for running: outage, test, maintenance.
- Load level or kWh generated.
- Fuel used.
- Alarms and actions.
- Operator name.
Stack testing in outline
- Appoint a competent, recognised testing agency.
- Prepare the set to run at the load specified for the test.
- Provide safe access to the sampling port.
- Obtain the report with method, conditions and results.
- Compare with the applicable limits and file the report.
Using data to improve
Trends in fuel use per kWh, filter pressure and alarms reveal engine health problems early. Compare the run log with the maintenance record to see whether service intervals suit the real duty.
Audit readiness drill
Once a year, ask someone who did not compile the file to find specified documents. If they cannot find them within minutes, reorganise.
Digital options
Scanned documents in a shared, backed-up folder with a consistent naming scheme, and remote monitoring of the set, make records easier to maintain and share.
The master engineering question
Could we prove tomorrow, from our own records, that this set was compliant last month?
What to send us
Send your current records. Send your application details.
Questions engineers ask
How long to keep records?
Follow the applicable rules and your policy.
Who does stack tests?
Qualified, recognised testers.
Are logs on paper acceptable?
Check requirements; digital helps.
What if records are missing?
Reconstruct what you can and start proper records now.
General guidance only. Follow applicable regulations.