Professional Documents
Culture Documents
EnviroConnect Server API For TSPCB Revised
EnviroConnect Server API For TSPCB Revised
OVERVIEW ................................................................................................................................................. 4
1.1. INTRODUCTION .......................................................................................................................... 4
1.2. SENDING DATA TO ENVIROCONNECT SERVER .................................................................................. 4
1.3. CONFIGURATION ........................................................................................................................ 5
1.1. Introduction
Telangana State Pollution Control Board (TSPCB) has implemented EnviroConnect as
central aggregator server software for real rime data acquisition and handling system for
CEMS, AAQMS and Water data monitoring in Telangana state.
EnviroConnect server accepts data from any authorized field client. This document
describes the method of uploading data to EnviroConnect server and will provides all
technical details required for implementing data transmission in client software.
In addition EnviroConnect has its own field client called EnviroConnect DAM which
provides all features described in this document and more.
1. Data must be acquired directly form the analyser without any other software ot
any other utility as an intermediate destination
2. Fool proof algorithms must be implemented to ensure that the data is not
tampered with in the process of acquisition
3. Local storage in case of failure of internet link must be secured storage without
any access to any user
1.3. Configuration
Before any client can start sending data to TSPCB EnviroConnect Production Server, the
particular Plant, Site within the plant and stack should be configured using
EnviroConnect Admin Tool. This will be taken care of by AIPL Team on instructions
from concerned authority within TSPCB.
Please go through the “Certification Process” section in the document below for more
details on configuration, testing of server API and certification.
This API provides full functionality including remote calibration. Following is a list of
supported functions
This is a RESTful API where clients communicate with server using HTTPS
requests. All request and response data is in the form of JSON objects.
Request Details
* If data of a particular parameter is not available on site due to any reason, its value
should be sent as “err”
All above details are sent to server as a JSON object. The structure is given in below
example
Example
'FunctionName': 53
'Name' : 'UserName'
'Password' : 'Password'
'DeviceID' : 1
'Datetime' : "2015-06-10 12:30:00"
'additionalInfo' : {
"LATITUDE","Value":'17.87‟,
"LONGITUDE","Value":'79.10',
"SOFWARENAME","Value":'fm varsion 1.0'
},
'Variables' : {
{"Variablename":"NO2","Value":12.2,”Flags”:””,"Unit":"mg/nm3"},
{"Variablename":"NOX","Value":122.2, ”Flags”:””,"Unit":"mg/nm3"},
{"Variablename":"SO2","Value":0.0,”Flags”:”C”,"Unit":"mg/nm3"},
Response Details
„ResultCode‟ : 1/2/3
'Message' : „Error Message if any‟
Code 1 indicates success. Other codes indicate error. An associated error message is
provided
*Multiple errors may get added. For ResultCode “1” i.e. success, there will be no
Message.
Request Details
* If data of a particular parameter is not available on site due to any reason, its value
should be sent as “err”
'functionName' : 54
'Name' : 'UserName'
'Password' : 'Password'
'DeviceID' : 1
'additionalInfo' : {
"LATITUDE","Value":'17.87‟,
"LONGITUDE","Value":'79.10',
"SOFWARENAME","Value":'fm varsion 1.0'
},
„Records‟:
{
„record‟ :{
'Datetime' : "2015-06-10 14:30:00"
'Variables' : {
{"Variablename":"NO2","Value":12.2,”Flag”:””, "Unit":"mg/nm3"},
{"Variablename":"NOX","Value":122.2, ”Flag”:””,"Unit":"mg/nm3"},
{" Variablename":"SO2","Value":23.2, ”Flag”:””,"Unit":"mg/nm3"}, {"
Variablename":"SOX","Value":43.2, ”Flag”:””,"Unit":"mg/nm3"}
}
},
„record‟ :{
'Datetime' : "2015-06-10 14:31:00"
'Variables' : {
{"Variablename":"NO2","Value":”err”, ”Flag”:””,"Unit":"mg/nm3"},
{"Variablename":"NOX","Value":122.2”Flag”:””,,"Unit":"mg/nm3"},
{"Variablename":"SO2","Value":23.2, ”Flag”:””,"Unit":"mg/nm3"},
{"Variablename":"SOX","Value":43.2, ”Flag”:””,"Unit":"mg/nm3"}
}
}
}
Response Details
„ResultCode‟ : 1/2/3
'Message' : „Error Message if any‟
*Multiple error may get added. For ResultCode “1” i.e. success, there will be no
Message.
Vendors have to send the “Check Command” request periodically to check any command
pending from server side. If any command is received from the server then its vendor‟s
responsibility to take appropriate action on the command.
Request Details
Example
'functionName' : 55
'Name' : 'UserName'
'Password' : 'Password'
'DeviceID' : 1
'Datetime' : "2015-06-10 12:30:00"
Response Details
*Multiple errors may get added. For ResultCode “1” i.e. success, there will be no
Message.
Request Details
Example
'functionName' : 56
'Name' : 'UserName'
'Password' : 'Password'
'DeviceID' : 1
'Datetime' : "2015-06-10 12:30:00"
„CalibrationID‟ : 12
„Calibration Result‟ : „success/failure‟
„Comment‟: „Comment if fail‟
Response Details
„ResultCode‟ : 1/2/3
'Message' : „Error Message if any‟
*Multiple errors may get added. For ResultCode “1” i.e. success, there will be no
Message.
Note:
1. Vendors should be responsible to use same software version which is certified, any
change in vendor software related to EnviroConnect API, needs re-certification.
2. The errors returned by EnviroConnect API should be handled and corrected by
vendor.
3. In production system, vendor software must have mechanism to log / display
errors returned by EnviroConnect API so that administrator of vendor software is
able to take corrective action
4. Remote Calibration user request sent from EnviroConnect API should be taken
care by Vendor to perform actual calibration and result should be shared with
EnviroConnect server using API.
support@sunshinetechno.com;
Email: sunshinetechnologies@yahoo.com.
TSPCB.EnviroConnect@aiplindia.com;
Email
amol.joshi@aiplindia.com
1. The data collection and transmission module should directly connect to the installed
analyzer and fetch the data directly from the analyser without any intermediary
software or conversions. The software should have no editing provision for
altering/correcting the data at the industry side.
2. No data shall be accepted as an output from OPC of Server or DCS or any other
intermediate software at Industry side.
4. The data collection and transmission module should wait for acknowledgement
from the' server and should retransmit the data if no acknowledgement is received
within the timeout period.
5. Each measurement should be associated with the data quality code inferred while
data collection and the data quality code should be transmitted along with the data.
The data quality code should indicate communication failures, calibration,
maintenance etc.
6. The data collection and transmission module should accept commands for calibration
(auto and manual) and able to perform calibration of the analyser locally.
7. The data collection and transmission module should be able to collect the
data directly from the analyser with a minimum scan interval of 10 seconds.
9. The data collection and acquisition software should be able to collect and encrypt the
data locally on the industry site. The data should archive the data locally on the client
machine for a period of 1 year.
10. The data collection and transmission module should communicate the status
periodically to the central server even when no analyser is connected or
when analyser is faulty with appropriate data quality code.
11. The data collection and transmission module should auto-restart on failure or
machine reboots.
13. The data collection and transmission module should support any analyser, make and
model based on the configuration and protocol specific extensions.(analyser
suppliers should be open enough to share their analyser output protocol for easy data
transmission digitally)
14. The data collection and transmission module should be customizable to support
any specific protocol required.