Pollution Monitoring System
Updated: Sep 9, 2020
Real Time Data Acquisition and Handling of CAAQMS/CEMS/EQMS data through Client-Server System from Industries located across Chhattisgarh State
Orphius Technologies participated in the tender floated by West Bengal Electronics Industry Development Corporation Limited or more commonly known as WEBEL and won the bid to “Design, Develop, Implement and Maintain integration of CAAQMS/CEMS/EQMS data from various Polluting Industries”. The scope of work of the project is as follows:
The most fundamental requirement in establishing continuous online monitoring systems is to have a universal format of connectivity that can accept real-time data from any installed analyzers (make or model) (may be customized in accordance with analyzers already installed) in the industry. The industry should be able to choose any analyzer to make and model that is approved internationally or by the Central Pollution Control Board for monitoring the ambient, emission and effluent parameters, the existing investment in the equipment by the industry can be utilized.
The system should be a highly scalable client-server application where the client software resides in the industrial site and the central server software resides at the central location hosted on-premise at State Data Center and/or cloud.
Provide a highly scalable system that can connect more than 2000 analyzers simultaneously in real time with a non-proprietary back end database suitable for storing Time-Series Data. In addition to the analyzers, the system should be capable of live streaming of feeds from all IP-PTZ cameras installed in the industry for the purpose of pollution control.
Users should have the option of viewing analyzer data from a particular environmental monitoring system (e.g. AAQMS/CEMS/EQMS) along with the live footage from such cameras if installed.
The system should support multiple client software that are found suitable to the requirement and approved by Chhattisgarh Infotech Promotion Society, which can send data to the central server.
The central server software should expose authenticated Representational State Transfer (REST) based Application Programming Interface (API) for client software to transmit the data.
The client software should NOT be restricted to the requirement of static IP and should be able to connect to the server based on the exposed API.
During collection and transmission, the platform should utilize digital encrypted communication to ensure authentic data is received and data origination location (GPS coordinates) and source signature are also verified by the software.
The client software should be able to transmit the data to the server using minimal bandwidth using existing site Broadband LAN/GPRS/GSM connectivity or by using an external dongle as an alternative for establishing online connectivity.
The software should provide reporting capabilities to display trend graphs, configurable alerts in accordance with CECB SOP and otherwise, tabular data, charts and data validation interface.
The software should provide the ability to annotate the validated data with the industry comments (Industry would have to comment on the data if clarifications are raised by CECB) and data quality codes. Software should have the ability to make the annotations visible while viewing the data in the charts if chosen by the User.
The software also should provide the ability to develop custom made-on-demand reports with capabilities to export the data into PDF, CSV and Excel formats. The reports developed should be printable on any of the standard printers.
The entire Source code of the software will be the property of CECB and the board should have the authority to review any specific module to validate the business logic and the data handling process.
The ability to generate the encryption keys for the Client-side software should be provided to CECB so that the board can provide authorized keys to the individual sites for secured data transmission. There should not be any financial implication to CECB for generation of such keys and it should be a software feature.
Publishing of data shall be at the end of the regulator and should have necessary components in-built in the system to publish valid data only.
Should have provision to share the validated data with the CPCB server database as and when required.