Executive Summary:
This document outlines the Online Automated Alerts Generation Protocol for OCEMS Emission Effluent, implemented by the Central Pollution Control Board (CPCB) Delhi in July 2025. The protocol uses SMS alerts based on data from online monitoring equipment to enhance compliance. It defines alert triggers and corrective actions based on exceedances, connectivity status, and consistent/stable values, categorizing compliance using a color-coded scale (Yellow, Orange, Red).
Key Points / Main Content:
* **Online SMS Alerts Mechanism:**
* Data from effluent/emission monitoring equipment is transmitted to CPCB servers at 15-minute intervals.
* The server generates automated SMS alerts to registered mobile numbers when one-hour average values exceed prescribed limits.
* **Data Transmission Categories:**
* Live
* Delay (no data transmission for four hours)
* Offline (no data transmission for 48 hours)
* **Alert Generation Basis:**
* Exceedances of prescribed limits
* Consistent and stable values
* Connectivity status
* **Color-Coded Compliance Grading:**
* Yellow Alert (Level I)
* Orange Alert (Level II)
* Red Alert (Level III)
* **Alert Triggers and Actions for ETP Parameters:**
* **Yellow Alert (Level I):**
* Trigger: 02 consecutive or non-consecutive SMS alerts in a day (00:00-24:00 Hrs) for registered parameters, or connectivity failure for four hours, or consistent and stable values (excluding pH) without 5% deviation for 48 hours.
* Action: Industry to take corrective measures immediately and maintain records for SPCB/CPCB.
* **Orange Alert (Level II):**
* Trigger: 04 consecutive SMS alerts in a day, or 27 yellow alerts generated during any 30-day moving period, or continuous connectivity failure for 48 hours, or 12 yellow alerts for connectivity failure during any 30-day moving period, or consistent and stable values (excluding pH) without 5% deviation for 72 hours.
* Action: Industry to take corrective measures immediately and notify SPCB/CPCB, and maintain records for SPCB/CPCB.
* **Red Alert (Level III):**
* Trigger: 08 consecutive SMS alerts in a day, or 54 yellow alerts generated during any 30-day moving period, or continuous connectivity failure for 96 hours, or 18 yellow alerts for connectivity failure during any 30-day moving period, or consistent and stable values (excluding pH) without 5% deviation for 144 hours.
* Action: Industry must immediately impound any further discharge of effluents and take corrective measures, record observations on effluent characteristics, submit a report to SPCB/CPCB, and may be prioritized for inspection by SPCB/CPCB.
* **Alert Triggers and Actions for Stack Parameters:**
* **Yellow Alert (Level I):**
* Trigger: 02 consecutive or non-consecutive SMS alerts in a day (00:00-24:00 Hrs) for registered parameters, or connectivity failure for four hours, or consistent and stable values without 5% deviation for 48 hours. Exclude alerts due to plant, boiler, or equipment start/stop (record in logs and notify SPCB/CPCB).
* Action: Industry to take corrective measures immediately and maintain records for SPCB/CPCB.
* **Orange Alert (Level II):**
* Trigger: 04 consecutive SMS alerts in a day, or 27 yellow alerts generated during any 30-day moving period, or continuous connectivity failure for 48 hours, or 12 yellow alerts for connectivity failure during any 30-day moving period, or consistent and stable values without 5% deviation for 72 hours.
* Action: Industry to take corrective measures immediately and notify SPCB/CPCB, and maintain records for SPCB/CPCB.
* **Red Alert (Level III):**
* Trigger: 08 consecutive SMS alerts in a day, or 54 yellow alerts generated during any 30-day moving period, or continuous connectivity failure for 96 hours, or 18 yellow alerts for connectivity failure during any 30-day moving period, or consistent and stable values without 5% deviation for 144 hours.
* Action: Industry must immediately impound any further emissions and take corrective measures, record observations on emission characteristics, submit a report to SPCB/CPCB, and may be prioritized for inspection by SPCB/CPCB.
Impact Analysis:
* **Industries:**
* *Impact:* Industries will be monitored for compliance based on the alerts generated by the OCEMS. They are subject to corrective actions and potential inspection based on the color-coded alert levels.
* *Action Required:* Industries must monitor SMS alerts, take immediate corrective actions for exceedances and connectivity failures, maintain records of incidents, and notify SPCB/CPCB as required. They must also ensure proper operation and maintenance of Effluent/Emission Monitoring Systems.
* **State Pollution Control Board (SPCB) / Central Pollution Control Board (CPCB):**
* *Impact:* SPCBs/CPCB will receive notifications and reports from industries regarding exceedances and corrective actions. They can use the alert system to prioritize inspections and ensure environmental compliance.
* *Action Required:* SPCBs/CPCB must review reports submitted by industries, prioritize inspections based on alert levels, and take appropriate regulatory actions as necessary.
Key Entities Referenced
Central Pollution Control Board: A governmental organization responsible for pollution control, mentioned in the context of data transmission from monitoring equipment.
Online Effluent/Emission Monitoring Systems (OCEMS): A system used for real-time monitoring of industrial emissions and effluents.
State Pollution Control Board (SPCB): A state-level agency responsible for pollution control, mentioned in the context of reporting exceedances.
Data Loggers/IoT Devices: Devices used to transmit data from online effluent/emission monitoring equipment to the CPCB servers.
Effluent Treatment Plant (ETP): A system designed to treat industrial wastewater, mentioned in the context of corrective measures for exceedances.
Air Pollution Control Devices (APCDs): Equipment used to control air pollution, referenced with emission deviations.
SMS Alerts Mechanism: Automated system to send alerts based on real-time data from monitoring equipment.
Delhi: Union territory and the location of Central Pollution Control Board.
Online Automated Alerts Generation
Protocol for OCEMS (Emission & Effluent)
Central Pollution Control Board
Delhi
July 2025Online SMS Alerts Mechanism
Online effluent/emission monitoring equipment are connected to
Data Loggers/IoT Devices to transmit data to CPCB Servers.
CPCB Server receives data at 15 min intervals through Data
Loggers/IoT Devices. Server generates auto SMS Alerts to the
registered mobile numbers.
SMS Alerts: System would receive 15-min average values from the
analyzers, based on which, the hourly SMS alerts may be transmitted
when one-hour average value exceeds the prescribed limit, thereafter
the next SMS alert may get generated if the average hourly value
exceeds the limit. The yellow alerts may be assessed according to the
number of such hourly SMS alerts.Proposed Framework for Monitoring Compliance through OCEMS
Hourly SMS alerts will be sent to industries for exceedances, as
outlined in Online SMS Alerts Mechanism Section.
Online data transmission categorized as – live, delay (no data
transmission since last four hours), and offline (no data transmission
since last 48 hours)
Considering the online monitoring data, this monitoring protocol is
being devised to enhance compliance level.
Alerts to be generated based on exceedances, consistent and stable
value, and connectivity status.
These alerts are used for grading compliance by industries based on
color coded scale as given below. The objective is to ensure proper
operation & maintenance of Effluent/Emission Monitoring System.
Yellow Alert -> Orange Alert -> Red AlertAlert Trigger Alert Code Action
ETP Parameters
⮚
Corrective measures
❑
Exceedance: For every 02
must be taken by industry
SMS Alerts (consecutive or non-
immediately.
consecutive) generated in a day
(between 00:00 Hrs to 24:00 Hrs)
Yellow (Level-I) ⮚
for the registered parameters. Industry to record the
incidence and maintain
❑ Connectivity Failure: When the record for reference
there is connectivity failure due to for SPCB / CPCB.
Internet / power connectivity
/sensor error / equipment failure,
for four hours (consecutive or non-
consecutive), in a day (between
00:00 Hrs to 24:00 Hrs) for the
registered parameters.
❑
Consistent and Stable
Values: When parameter values,
excluding pH, are consistent and
stable, without any deviation (of
+/- 5%) for 48 hours continuously.Alert Trigger Alert Code Action
Stack Parameters
⮚
Corrective measures
❑ Exceedance: For every 02
must be taken by industry
SMS Alerts (consecutive or non-
immediately.
consecutive) generated in a day
(between 00:00 Hrs to 24:00 Hrs)
Yellow (Level-I) ⮚
for the registered parameters. Industry to record the
incidence and maintain
the record for reference
Alerts for exceedance due to plant,
for SPCB / CPCB.
boiler or equipment’s start or stop
must be excluded (logs must be
recorded and special note to be
sent to SPCB / CPCB in this regard
after generation of yellow alert)
❑ Connectivity Failure: When
there is connectivity failure due to
Internet / power connectivity
/sensor error / equipment failure,
for four hours (consecutive or non-
consecutive), in a day (between
00:00 Hrs to 24:00 Hrs) for the
registered parameters.
❑ Consistent and Stable
Values: When parameter values,
are consistent and stable, without
any deviation (of +/- 5%) for 48
hours continuously.Alert Trigger Alert Code Action
ETP Parameters
⮚
Corrective measures
❑ Exceedances (Continuous):
must be taken by industry
For every 04 consecutive SMS
immediately.
Alerts generated in a day (between
Orange (Level-II)
00:00 Hrs to 24:00 Hrs) for the
⮚
registered parameters. Industry to record the
incidence and maintain
❑ Exceedances (Discrete): For the record for reference
every 27 Yellow Alerts (For for SPCB / CPCB.
Exceedance) generated during any
30-day moving period (7.5% of
⮚
Industry to notify SPCB
maximum possible yellow alerts in
30 days, i.e. 360). /CPCB about the
incidence and corrective
❑ Connectivity Failure measures taken.
(Continuous): When there is
Internet / power connectivity
/sensor error / equipment failure
continuously for 48 hours.
❑ Connectivity Failure
(Discrete): When Internet / power
connectivity /sensor error /
equipment failure results in 12
Yellow Alerts (For Connectivity
Failure) during any 30-day moving
period.
❑ Consistent and Stable
Values: When parameter values,
excluding pH, are consistent and
stable, without any deviation (of
+/- 5%) for 72 hours continuously.Alert Trigger Alert Code Action
Stack Parameters
⮚
Corrective measures
❑ Exceedances (Continuous): must be taken by industry
For every 04 consecutive SMS
immediately.
Alerts generated in a day (between
00:00 Hrs to 24:00 Hrs) for the
registered parameters. Orange (Level-II) ⮚ Industry to record the
incidence and maintain
❑ Exceedances (Discrete): For the record for reference
every 27 Yellow Alerts (For for SPCB / CPCB.
Exceedance) generated during any
30-day moving period (7.5% of
⮚
Industry to notify SPCB
maximum possible yellow alerts in
/CPCB about the
30 days, i.e. 360).
incidence and corrective
❑ Connectivity Failure measures taken.
(Continuous): When there is
Internet / power connectivity
/sensor error / equipment failure
continuously for 48 hours.
❑ Connectivity Failure
(Discrete): When Internet / power
connectivity /sensor error /
equipment failure results in 12
Yellow Alerts (For Connectivity
Failure) during any 30-day moving
period.
❑ Consistent and Stable
Values: When parameter values,
are consistent and stable, without
any deviation (of +/- 5%) for 72
hours continuously.Alert Trigger Alert Code Action
ETP Parameters
⮚
Industry must
❑ Exceedances (Continuous):
immediately impound any
For every 08 consecutive SMS
further discharge of
Alerts generated in a day (between
effluents and corrective
00:00 Hrs to 24:00 Hrs) for the
Red (Level-III) measures must be taken
registered parameters.
immediately by industry.
❑ Exceedances (Discrete): For ⮚ Industry to record the
every 54 Yellow Alerts (For incidence and maintain
Exceedance) generated during any
the record for reference
30-day moving period (15% of
for SPCB / CPCB.
maximum possible yellow alerts in
⮚
30 days, i.e. 360). Industry to notify SPCB
/CPCB about the
❑ Connectivity Failure incidence and corrective
(Continuous): When there is measures taken.
Internet / power connectivity ⮚
Record the
/sensor error / equipment failure
observations on the
continuously for 96 hours.
effluent characteristics
❑ Connectivity Failure during the past 24 hours
(Discrete): When Internet / power and submit a report along
connectivity /sensor error / with reasons for deviation
equipment failure results in 18 in the ETP/Processes.
Yellow Alerts (For Connectivity ⮚
Industry may be
Failure) during any 30-day moving
prioritized for inspection
period.
by SPCB. CPCB may also
❑ Consistent and Stable prioritize the industry for
Values: When parameter values, inspection.
excluding pH, are consistent and
stable, without any deviation (of
+/- 5%) for 144 hours continuously.Alert Trigger Alert Code Action
Stack Parameters
⮚
Industry must
❑ Exceedances (Continuous):
immediately impound any
For every 08 consecutive SMS
Alerts generated in a day (between further emission and
Red (Level-III)
00:00 Hrs to 24:00 Hrs) for the corrective measures must
registered parameters. be taken immediately by
industry.
❑ Exceedances (Discrete): For ⮚
Industry to record the
every 54 Yellow Alerts (For
incidence and maintain
Exceedance) generated during any
the record for reference
30-day moving period (15% of
maximum possible yellow alerts in for SPCB / CPCB.
30 days, i.e. 360). ⮚ Industry to notify SPCB
/CPCB about the
❑ Connectivity Failure
incidence and corrective
(Continuous): When there is
measures taken.
Internet / power connectivity
⮚
/sensor error / equipment failure Record the
continuously for 96 hours. observations on the
emission characteristics
❑ Connectivity Failure during the past 24 hours
(Discrete): When Internet / power and submit a report
connectivity /sensor error /
alongwith reasons for
equipment failure results in 18
deviation in the
Yellow Alerts (For Connectivity
APCDs/Processes.
Failure) during any 30-day moving
⮚
period. Industry may be
prioritised for inspection
❑ Consistent and Stable by SPCB. CPCB may also
Values: When parameter values, prioritize the industry for
are consistent and stable, without
inspection.
any deviation (of +/- 5%) for 144
hours continuously.