Ocems: Online Continuous Effluent Monitoring Software
Ocems: Online Continuous Effluent Monitoring Software
Ocems: Online Continuous Effluent Monitoring Software
(04/2024)
OCEMS
Online continuous Effluent
Monitoring software
By
Pratyush Gupta
Area of application
1. Common Effluent Treatment Plants (CETPs) [15-25 MLD]
2. Sewage Treatment Plants (STPs) [25-50 MLD]
3. Municipal wastewater treatment [5-10 MLD]
4. Chemical manufacturing plants [10-15 MLD]
Problems
leads to inefficiency.
7. Inefficient method to collect the payment and keep track of the paid bills,
Team Hierarchy
Management
Officers
Only Departmental
Access as assign by Admin
Operators
Only Particular Department
access as assign by Admin and Officer
Features
Team
Management
Industry Side
Plant Side
• Admin can add staff working
in the plant and assign roles
and responsibilities.
Features
Industry
Management
• Realtime Monitoring of the data from
online analyzer like PH meter, TDS
analyzer, flow meters etc.
• Realtime Monitoring of the treated
water consumption quantity and
quality of discharged effluent from
industries.
Features
Notices and Bills
Management
Process
Monitoring and
Management
Features
Chambers
Management
Features
Sludge
Management
• Online monitoring of sludge
generation and disposal at
STP/CETP campus.
• Billing of different type
sludges and record keeping
of bills
Features
Inventory
Management
• Interface to update inventory
daily and get all the available
item quantities and their
usage.
• View to see different
consumables used on
daily/monthly/yearly basis.
Features
Report Section
• Online report generation of all
industries including payment defaulter,
any type of upgradation of industry
etc as per requirement.
• Online reports for consumptions of
chemicals etc and repair and
replacement of equipments etc.
• Online report generation for Power
consumptions, solar power
generations and PNG consumptions
under the contract and penalty.
Development Contribution
1. Software Architecture Designing Design criteria
- The software targets the B2B market.
- Here the clients are industries, which are generally 2000 to 3000 in
numbers for the normal 10 MLD plant.
- Frequency of data read and write is per 15 minutes for one plant.
- Size of incoming data from one plant per 15 minutes is 10 Kb.
- Incoming data is categorized in three major categories: - data from the
plant instrument like sensors and analysers, data from the onboarded
industries (COD, BOD, TSS, PH etc. parameters, general data collected
from different features like notices, bills & payment, inventory, team
management etc.
- Data backup of 1 year duration.
- Implementation of a separate Modbus server for instrument data
retrieval and storage (last 7 days). This Modbus Client server actually
performs the corn job at a particular frequency as assigned, it reads the High level software architecture model
analog/digital register of the instruments and sensors whose fixed
addresses are stored into the database
Development Contribution
1. Software Architecture Designing Design criteria
Main Server (NodeJS):- The main server is an Ubuntu System of 64 bits,
1VCPU, 1GB storage, 25 GB SSD Disk and 1000 GB Transfer. This server is
hosted upon Digital ocean platform. The communication from the remote
system is made through SHA key generated by PUTTY gen software.
All the backend logics like routing, authentication, middleware,
payment handling etc are implemented in the Main server.
Modbus Client Server:- functionality of this server is to fetch the data from
the on-premise plant local server through port forwarding. This Modbus
Client server actually performs the corn job at a particular frequency as
assigned, it reads the analog/digital register of the instruments and
sensors whose fixed addresses are stored into the database.
Database:- NoSQL Firebase database cluster is used in the development. High level software architecture model
Different models corresponding to different features based on their
designed schemas are created in the database.
Development Contribution
2. Sludge Management Architecture
Main server will trigger any general event whereas Modbus Time
Scheduled server will trigger the process events, both will report to the High level architecture of alerts/notification feature
cloud messaging server. The cloud messaging server will fetch the FCM
(Firebase Cloud Messaging) token from the databas and will send
Alert/notification to the recipients. Based on severity of the trigger’s
payload is decided by the cloud messaging server.
Development Contribution
4. Controlling Plant Operations
Backend logic is designed through which user can control the working of Modbus TCP/IP registers block diagram
plant remotely i.e., the logic to control different analog/digital sensors and
instruments installed at different chambers by overriding the register
logics in memory area through Modbus client server communication.
Development Contribution
5. Database Schemas 7. Backend Coding
Design an efficient database schemas for OCEMS to ensure easy For backend coding NodeJS framework is used. I have developed the Apis collection,
accessibility and minimal latency. Created an Entity Relationship (ER) routes and middleware for the billing, notices, process, sludge, chambers and inventory
diagrams of various software features like process, inventory, billing, management features.
notices, reports, team, chambers and sludge management. Postman Api: - https://documenter.getpostman.com/view/21883208/2s9YeD8DSa
6. Data Preprocessing
The cluttered data of plant like instrument list, P&ID list, Sludge calculation
list, industries list, Mass balance-chambers list, operations list, various
bills, inventory item list etc. are collected and pre-processed for its better
understanding. Through the understanding of these lists decision is taken
over database and software architecture designing.
In future these pre-processed data together with the collected data will
be used for implementing optimization feature.
Benefit
1 2 3 4
Plant operations streamlining, Alerts operators about the Ensures adherence to Provides continuous, real-
reducing manual deviations of instruments from environmental regulations time data on plant
interventions and human optimal conditions which and effluent standards, performance and effluent
errors. allows for immediate action. reducing the risk of non- quality, enabling proactive
compliance penalties. decision-making.
THANK
YOU