Must OCEMS data go to both CPCB and SPCB servers?

Both regulators must see the data, but how depends on the architecture. On CPCB's new central portal (cems.cpcb.gov.in) the industry pushes once and the platform shares the data with the State Pollution Control Board. Where a state board operates its own server (each state has one — for Tamil Nadu it is TNPCB), the guidelines require a simultaneous direct push to both. The Wiman CPCB Gateway is integrated and deployed on the new central portal today; direct SPCB server transmission is in active development for states that require their own feed.

What happens to CPCB data during a network failure?

CPCB guidelines require at least 85% data availability and support delayed-data submission: readings buffered during an outage must be uploaded marked as delayed data, with their original timestamps. The CPCB Gateway does this automatically — its inbuilt logger stores every reading and back-fills the server history when connectivity returns.

Why does a CPCB gateway need failover?

A data gap is a compliance failure even when the plant is running clean — CPCB has issued show-cause and closure notices to units whose data stopped flowing due to connectivity loss. A dual-path gateway (wired LAN/leased line primary with automatic 4G failover) removes the single point of failure, and the inbuilt logger covers the case where both paths fail.

How do analyzers connect to the CPCB Gateway?

CEMS and effluent analyzers typically expose readings over RS-485 Modbus RTU or 4-20 mA outputs. The CPCB Gateway polls Modbus analyzers directly as an RS-485 master. A single 4-20 mA sensor connects directly to the gateway's inbuilt IO channel with no external card; for more channels the WT36I analog input card adds 6 channels on the same bus.

Can the gateway also send data to my own SCADA or cloud?

Yes — alongside the regulator push, the gateway can deliver the same timestamped readings to your own SCADA or cloud portal, so plant operations always sees exactly what the regulator sees.

Is OCEMS the same as OCMMS?

No. OCEMS is the Online Continuous Emission/Effluent Monitoring System — live analyzer data streaming to the regulators, which is what this gateway does. OCMMS is the Online Consent Management and Monitoring System — the portal for Consent to Establish / Consent to Operate applications, renewals and fees. The gateway serves OCEMS; consent applications go through OCMMS separately.

Which hardware is the CPCB Gateway based on?

The Wiman WT460M — the flagship MAX Series industrial gateway with Ethernet plus 4G LTE dual upstream, automatic failover, dual-server push, HTTPS/SSL transport, an inbuilt FIFO data logger and support for up to 3,000 field tags on a DIN-rail form factor.

Platforms · MAX Series

CPCB Gateway

Q: What is CPCB OCEMS and who must install it?

OCEMS (Online Continuous Effluent/Emission Monitoring Systems) is mandated by India's Central Pollution Control Board through its February 2014 directions: the 17 categories of highly polluting industries — plus CETPs, STPs and common waste incinerators — must stream emission and effluent data to CPCB and their State Pollution Control Board in real time, 24x7. For new units it is a Consent-to-Operate condition; non-compliance can attract closure directions.

OCEMS-ready data push for India’s pollution-control mandate — simultaneous transmission to CPCB and State Pollution Control Board (SPCB) servers, LAN-to-4G failover, and an inbuilt logger that back-fills delayed data. Built on the WT460M, our flagship MAX Series gateway.

Why CPCB monitoring exists

The Central Pollution Control Board (CPCB) is India’s apex statutory pollution-control body — constituted in 1974 under the Water Act and working under the Ministry of Environment, Forest and Climate Change. In February 2014, CPCB issued directions under the Water and Air Acts requiring the 17 categories of highly polluting industries — plus CETPs, STPs and common waste incinerators — to install Online Continuous Effluent/Emission Monitoring Systems (OCEMS) and stream their emission and effluent data to the regulators in real time, 24×7. If a parameter crosses its limit, the central software alerts the industry, the State Pollution Control Board (SPCB) and CPCB automatically. Every state has its own board — for Tamil Nadu units the SPCB is TNPCB — and the data must reach both the state board and CPCB.

This is not optional instrumentation. For units commissioned after February 2017, a working OCEMS connection is a condition of the Consent to Operate; for existing units, boards were directed to issue closure directions where OCEMS was missing — powers that extend to stopping a plant’s electricity and water supply.

What the mandate demands from your data pipeline

The analyzers measure — but compliance is decided by whether the data actually reaches the regulators. CPCB’s guidelines and portal API set precise requirements for the transmission side:

Both regulators must see the dataOn the new central portal (cems.cpcb.gov.in) the gateway pushes once and the platform shares the data with your SPCB. Where a state board runs its own server, the guidelines require a simultaneous direct push to both — the gateway supports either architecture.

Secure REST + JSON over HTTPSThe mandated transport is an open REST API with JSON payloads; the current CPCB portal requires HTTPS/TLS transport with strong encryption and token-based authentication.

Timestamped, flagged readingsEvery reading carries parameter, value, unit, original timestamp and a data-quality flag — the server files each record against the time it was measured.

15-minute averages, logged rawAll monitored values are recorded locally; 15-minute average values are transferred to the regulator's server on schedule.

At least 85% data availabilityThe CPCB guidelines are explicit: the industry must ensure at least 85% data availability from the installed system — connectivity failures count against you.

Delayed-data backfillWhen transmission is interrupted, the guidelines require the buffered records to be submitted marked as delayed data — store & forward is written into the mandate itself.

The real risk is a data gap — not a reading

A data gap means the regulator’s server did not receive a packet for a timestamp — a transmission failure, not a pollution event. Yet it lands on the industry: CPCB has issued closure and show-cause notices to over a thousand units for missing OCEMS data, including failures caused purely by lost connectivity. Extended gaps can escalate to stop-operation orders. Independent studies have found real-world data availability running well below the 85% requirement across states and sectors — and connectivity is a failure mode you can actually engineer away.

THE POINT

Your compliance is only as strong as the weakest link between your analyzers and the CPCB server. One connectivity path is a single point of failure; a gateway with failover and a logger removes it.

Failover, animated

primary link fails · data never stops

Analyzers stream into the gateway over RS-485 Modbus and 4-20 mA. The gateway delivers every timestamped reading to the regulators — one encrypted push to the new central portal, or a parallel push where your state board takes a direct feed — normally over the wired LAN / leased-line path. Watch what happens when that path fails: the 4G path takes over in seconds, and if both are ever down, the inbuilt logger holds every reading and back-fills it as delayed data. The 85% availability number stays protected through all of it.

ANALYZERSpH · COD · TSSPM · SO₂ · NOₓFLOW

CPCB GATEWAYWT460M

LAN / LEASED LINE

4G FAILOVER

CPCB SERVER

SPCB SERVERIN DEVELOPMENT

PRIMARY LINK OK — pushing to CPCB + SPCB in parallelLAN DOWN — failover to 4G · data still flowing, no gapLAN RESTORED — back on the primary path · logger idle

Today: one encrypted push to the CPCB portal covers both regulators, and the same stream can also feed your own SCADA or cloud portal. The direct SPCB fork shown is in development for states that take their own feed. Either way, when the LAN chip goes red the same packets ride the 4G path — the regulators never see a gap. Total loss of both paths hands over to the logger (see the Store & Forward guide).

GOOD NEWS

Along with the regulator push, the gateway can send the same data to your own SCADA / client server — your operations team sees exactly what the regulator sees.

4-20 mA

A single 4-20 mA sensor connects directly to the inbuilt IO channel — no external card required. Need more channels? The WT36I analog input card adds 6 channels on the same bus.

Why the WT460M is the right base

✓

Dual upstream with auto failoverEthernet/LAN primary + 4G LTE standby on one device — the cellular path takes over the moment the wired path fails, and hands back when it returns.

✓

New CPCB portal — integrated & deployedSingle encrypted push to cems.cpcb.gov.in, live in the field today. Direct SPCB server feed is in active development for states that take their own feed.

✓

Inbuilt data loggerFIFO logging with original timestamps; when connectivity returns, records are forwarded as delayed data and history back-fills with no gaps.

✓

Secure transportHTTPS/SSL with token headers — matches the portal's encrypted, authenticated API requirements.

✓

Analyzer-side connectivityRS-485 Modbus RTU master polls CEMS/effluent analyzers directly. A single 4-20 mA sensor lands on the inbuilt IO channel — no external card; the WT36I analog card adds 6 channels for larger stations.

✓

Your SCADA gets a copy tooAlongside the regulator push, the same timestamped readings can be sent to your own SCADA or cloud portal — operations sees exactly what the regulator sees.

✓

Industrial buildDIN-rail mount, industrial-grade design, up to 3,000 field tags — runs unattended at the plant, 24×7.

The CPCB Gateway is a WT460M configured for the OCEMS role — same industrial hardware, provisioned for regulator push, failover and delayed-data logging. Wiman has already integrated the new CPCB portal’s API in a live deployment — encrypted signature authentication, device and station IDs, and the full registration flow (portal sign-up, station and analyzer details, device tokens) handled during commissioning.

Who needs this

The 17 mandated categories of highly polluting industries, plus common treatment and incineration facilities:

Pulp & PaperDistilleriesSugarTanneriesThermal PowerIron & SteelCementOil RefineriesFertilizerChlor-AlkaliDyes & IntermediatesPesticidesZincCopperAluminiumPetrochemicalsPharmaceuticalsCETPsSTPsCommon Incinerators

Put it on your stack

WT460MThe flagship MAX Series gateway underneath — full specs, LED indications and datasheet.View the WT460M →How Store & Forward WorksThe delayed-data mechanics, animated — logger modes, FIFO order and timestamped back-fill.Open the guide →Discuss your CPCB projectTell us your parameters, analyzers and state board — we will spec the full pipeline with you.Talk to us →

Loading…

CPCB Gateway