RfS document for feeder level Solarization under PM-KUSUM-Component-C

C in UGVCL

ANNEXURE-1
Metering infrastructure Philosophy and Remote Monitoring System

A. Metering infrastructure Philosophy

1. Metering and grid connectivity of the projects would be the responsibility of the SPG in
accordance with the prevailing guidelines / practices of UGVCL and / or CEA. UGVCL may
facilitate in the process; however,the entire responsibility & cost lies only with the SPG.
2. Meters and metering equipment (CT
(CT-PT sets) specifications shall be
e complied with CEA metering
regulations and shall be tested as per provision of GERC order / directives and as per IS 14697 at
CPRI or at any NABL accredited / distribution licensee lab before installation at site at the cost of
SPG and should be properly sealed in thepresenceofdesignated authorityfromUGVCL
authorityfrom
atthetimeofinstallation.
3. The solar power generator shall install Metering infrastructure and Remote Monitoring
System as per the philosophy explained in this Annexure.
4. SPG to install 3 ABT meters (main, check and standby) with RMS connectivity and 2
CT-PT
PT sets (one for main & check meter and another for standby meter) indicated in
below layout: -:

(Indicative Diagram
Diagram: Metering Arrangement Lay out)

5. Installation and timely replacement of meters (main, check and standby) as

requiredtodirectlymeasureenergysuppliedbytheSolarPowerPlantshallbetheresponsibility
ofselected bidder.

6. The costof all requiredmeters at Substation end (main,check, standby meter)at

substation endalongwithMeter andassociatedCT
andassociatedCT-PTsets and RMS at Solar plant
siteshallbebornebytheSPG.

Page 1 of 27
 RfS document for feeder level Solarization under PM-KUSUM-Component-C in UGVCL

B. RemoteMonitoringSystem(RMS)
1. SPG shall also be responsible for installation of IoT Devices-RMS Set for Remote
Monitoring system connectivity of Inverters, String combiner box, Energy Meters at
Solar plant, Substation with State SEDM Portal www.pmkusum.guvnl.com
2. As per the MNRE guidelines for feeder level Solarization under Component C of PM-
KUSUM scheme, it is mandatory for DISCOMs to monitor solar power generation
andperformance of the solar power plant through online system on State-Portal
www.pmkusum.guvnl.com. The online data will beintegrated with central monitoring
portal of MNRE which will extract data from theStateportalsformonitoring ofthescheme.
3. In line with MNRE model guidelines for State Level SEDM Software Developmentissued
in July 2020, Gujarat DISCOMshave developed StateLevel Solar Energy Data
Management (SEDM) platform to integrate & monitor theperformance of all systems
installed under Component A, B & C (individual as well asfeeder levelSolarization)of PM-
KUSUM scheme.
4. Also,as per the Specifications for Remote Monitoring System for Component A& Cof the
scheme, issued by MNRE on 15 Jul 2020, the SPG under this RfS shall berequired to
install required remote monitoring systems for solar power plant to integrate with
State SEDM platform directlywhich in turn will have interface with National Level Solar
Energy Data ManagementPlatformofMNRE.
5. As part of National and State SEDM platform, various modules will be provided suchas
Consumer Management, Scheme Progress Management, Asset Management, LiveAsset
Monitoring, Performance Analysis, Complaint and Ticket Management,
DeviceIntegration/SCADAPlatform,Alarm/Events/Notification,MeterDataAcquisition
(MDAS) /Meter Data Management (MDM), Archiving and Historian, Report
Manager,Mobile application, SIA officer and EPC, Enterprise level user and
rolemanagement.
6. MNRE and DISCOMs will develop and host the of National and State Level
SEDMplatform which is excluded from the scope of the SPG but SPG needs to operate
anddovariousdataentriesrelatedtoapplicationprocessing,assetandworkflow mgmt .

Page 2 of 27
RfS document for feeder level Solarization under PM-KUSUM-Component-C in UGVCL

6. AsshowninabovediagramSPGneedstoprovidearemotemonitoringsystemfor:
(a) SolarPowerPlant Remote Monitoring system: To capture electrical
parametersfrommultipledevicessuchasABTMeter,Inverters,StringCombinerboxesorStrin
ginverters including meters at Sub-station
level.Remotemonitoringsystemwillcaptureimportant Electrical and Status parameters
such as AC/DC voltage, control, power,energyas wellasmonitoring ofBreakeretc andwill
transmitdata to StateLevelSolar Energy data management (SEDM) platform.
(b) CommunicationConnectivityforSolarPlantRMS:
i. Field Device Connectivity: RMS will connect to Inverter, String combiner boxes
orstring inverters using RS485 MODBUS communication protocol as well as
metersusingRS232DLMSprotocol.Bothprotocolsarewidelyusedbyequipmentmanufa
cturers.
ii. RemoteConnectivity:RMSwillconnecttoStateLevelSEDMServerusing2G/3G/4Gor
anyother suitablecellularcommunication.
iii. LocalConnectivity:Ethernet/Bluetooth/Wi-Ficonnectivitytoconfigureparameter,
notifications, communication intervals, set points, operation modeconfiguration
ortodownload locallystored data.
7. It is the responsibility of SPG to provide SIM card/Wi-fi connectivity, bear recurring
communication chargesand maintain communication connectivity of more than 96%
and data availability of99% for the 25 years (unless extended by both the parties on
mutual agreement) ofoperation&maintenance ofsolarpowerplant and
itsassociated11kVline failing bills of the Generator may not be processed.
8. Details of Communication Modes, Communication Protocols, Security and
Messageformats and equipment wise parameter details are enclosed as
“CommunicationArchitecturebetweenRMSand StateLevelServer” is described as below
write-up :-

Page 3 of 27
 RfS document for feeder level Solarization under PM-KUSUM-Component-C in UGVCL

Communication Architecture between RMS and State Level Server

RMS Communicationand
SecurityArchitecture-
PMKUSUMSEDMPlatform
Date: 14/07/2020

Page 4 of 27
Contents
RMSCommunication & SecurityArchitecture .......................................................................... 2
1. Security Architecture ........................................................................................................ 2
2. RMSRegistration .............................................................................................................. 3
3. MQTTTopicStructure ........................................................................................................ 3
4. CommunicationModes ...................................................................................................... 4
5. CommunicationProtocols.................................................................................................. 4
6. MQTTMessageStructure .................................................................................................. 5

Page 5 of 27
RMSCommunication&SecurityArchitecture

1. SecurityArchitecture(withreferencetoEESLTenderAnnexure8–clause4.d)
2. RMSRegistration (withreferencetoEESLTenderAnnexure8–clause4.d)
3. MQTTTopicStructure(withreferencetoEESLTenderAnnexure8– clause4.b,4.c)
4. MQTT MessageStructure(withreferencetoEESLTenderAnnexure8–clause4.e,4.f)
5. Annexure:JSONFormatswithparameterkeywords,samplevaluesanddescription
a. Annexure:PumpController
b. Annexure:EnergyMeter
c. Annexure:Inverter
d. Annexure:StringCombinerBox(SJB)
e. Annexure:Heartbeat
f. Annexure:DAQ

1. SecurityArchitecture

This section highlights the communication security architecture between RMS/DCU and
StateSWPS IoT Platform. With this security, architecture, third parties are unable to intercept or
“sniff”the encrypted data. This stops ISPs, employers, local network administrators and
cybercriminalsfrom being able to perform “packet sniffing” to access what the traffic contains. It
also protectsagainst man in the middle (MitM) attacks. This implements Private TLS/SSL VPN to
ensurehighestlevelofsecurity.
In additional to this, use of OTP in every message exchange shall help restrict spammers
andBots. Such OTP based mechanism will provide transaction level security which is
required forremoteoperations.

Identification
Encryption Authorization OTP
Identification Authentication
byTLS/SSL Access to Messages
certificate as onlyrestricted withvalid OTP are
AES-256 onlytakenintofurt
wellas EncryptedCom TLS/SSLClient topics,authorize
IMEIIdentificatio certificate d tothem herprocessing,
municationover restmessages
nduring TLS/SSL basedAuthentic
messageexchang ation arediscarded.
e

2 Page 6 of 27
2. RMSRegistration

This section details how individual RMS/DCU shall be registered and communicate
securelywithStateSWPSIoTPlatform.

 Everysupplier/vendormustRegisteralluniqueIMEI
(InternationalMobileEquipmentIdentity)ofRMS/DCUwithStateSWPS
 State SWPS will generate individual client certificate for RMS/DCU against unique
IMEIregisteredandsharewithsupplier/vendorthroughsecuredwebAPIinterface.
 Everysupplier/vendorshallbeable
toaccesswebAPIwithuniquecredentialssharedwiththem.
 WebAPIshallreturnindividualclientcertificate, DeviceBrokerurland“info”topic.
 After installation of client certificate relevant to IMEI of RMS/DCU, RMS/DCU
willconnect to Device Broker and get authenticated using client certificate and further
shallbe able to receive additional configuration details such as FTP credential,
MessageTopic structure etc.aftersubscribingtodefaulttopic.
 Afterclientcertificateexpiry,RMSwillconnecttoFTPusingavailablecredentialsanddownlo
adthe renewedcertificate

3. MQTTTopicStructure

ThissectiondefinesthedifferenttopicstructureforcommunicationbetweenRMS/DCUandStateS
WPSthroughDeviceBroker.
RMS/DCUwillpublishandsubscribetotheirrespectivetopicsonly,authorizationoftopicshallbedone
againstuniquecredentials.
Application Solution IMEI Message Publish/Subscribe
Version Type
Standalonesolarpump Info Subscribe
Gridconnectedsolarpump OTP Subscribe
SolarMW Heartbeat Publish
IIOT-1 {IMEI}
Ongridrooftop Data Publish
Offgridrooftop Ondemand Subscribe
Config Subscribe

Sample Topic structure for Stand-alone Solar Pump shall be: IIOT-
1/Standalonesolarpump/{IMEI}/info
Multiplesub-
topicswillbeformedforcommunicationbetweenRMS/DCUandsateSWPSIoTPlatform

 Info:DefaultTopicToexchangeRMS/DCUconfigurationdetails
 OTP:ToexchangeOTPateveryintervalof 15/30/60minutes
 Heartbeat:ToupdateRMS/DCUhealthindicatorsatfrequentconfigurableintervals.
 Data:ToexchangedatarelatedtoRMS/DCUMonitoringparametersin“pushmode”
o PushdataPeriodically
o PushdataonEvent/Notification
o HistoryMissingDataPushMode:Historydatawillbeidentifiedagainst“index”

3 Page 7 of 27
  Ondemand: To exchange data between RMS/DCU and Server in “Command
onDemand”Mode
o Each“OnDemand”messagewillhavetwotransactions:Commands,Response.
o Ondemandcommandandresponsewillbetrackedagainsta common
“MSGID”.
o Ondemandmessagecanbeusedtoreadandwritewithtwocommandtypes
 Command: “Read” - In json received from server replace each key
withvaluefromRMS/DCU andsendtheupdatedjsonbacktoserver.
 Command: “Write” - After executing the command based on key-
valuepairreceivedinjson,sendtheupdatedjsonbacktoserveronsuccessfule
xecution.
 Note:handshakingparameters suchas msgid,etchastosendback
toserverasis,withoutmodification
 Config: To update configurable parameters of Device, which is similar to Ondemand
butwill be used only for configurable parameters of Device, this implements
“Configurationover theair”
 Command: “Read” - In json received from server replace each key
withvaluefromRMS/DCU andsendtheupdatedjsonbacktoserver.
 Command: “Write” - After executing the command based on key-
valuepairreceivedinjson,sendtheupdatedjsonbacktoserveronsuccessfule
xecution.
 Note:handshakingparameterssuchas msgid,etchastosendback
toserverasis,withoutmodification
4. CommunicationModes

 Push on Periodic Interval: In this mode deployed RMS shall transmit data of Multiple
devicesandsensorsondifferentconfigurabletimeintervalssuchasInverterorpumpcontrollerdataat
every 5 minutes, Energy Meter data at every 15 minutes, String Combiner Box data at every
10minutes
 Push on Event: RMS shall detect various configurable alarm or event conditions such as
PumpOn/OffStatus,InverterOn/OffStatus,LowWaterFlowRate,FaultorTripstatusetc.andItshalltran
smitdataimmediatelytotheserver
 OnDemandRead:Inthismode,Userwill
sendcommandtoRMStogetdataasandwhenrequiredandRMSwill
sendtherequireddatatoserverimmediately
 OnDemandWrite:IncaseofRemoteOperations,Farmer/ConsumershallsendOnDemandWrite
Command to the RMS and RMS will send back the acknowledgement with change
inparametersafteroperationiscompleted
 Configuration read/write: Using this mode, user will be able to read and change
configurableparametersremotelysuchasupdatingperiodicinterval,alarmlimits,serverparamete
rsetc.

5. CommunicationProtocols

 Field Device Communication: RMS to Field Devices communication such as Inverter,

PumpController, Drive, String Combiner box, MFT/MFM, Data Acquisition System shall be
establishedusingMODBUSRTUprotocolsupportedbyallleadingmanufacturersglobally

4 Page 8 of 27
  EnergyMeterCommunication:RMStoEnergyMetercommunicationsuchasBiDirectional(Reve
nue) Meter, Solar Generation (Audit) Meter shall be established using
DLMS/Modbusprotocolsupportedbyall leadingMeterManufacturersinIndia
 RMS to Server Communication - Industrial IoT MQTT Protocol: RMS to Server
Communicationshall be established using MQTT protocol which is well accepted IoT protocol
across the globeandsupportedbyallleadingITaswellasOTcompaniesforSmartGrid,SmartREand
SmartCityApplications

6. MQTTMessageStructure

ThissectiondetailsmessagestructureexchangedbetweenRMS/DCUandstateSWPSIoTPlatformthr
oughDeviceBroker
keyword Description SampleValue
IMEI Unique Identification of RMS/DCU – required to 863287049443888
ensureregisteredsourceofdata
VD Virtual device/group – required for grouping 2
parametersbasedonupdateinterval/subsystems suchas
inverter/pumpcontroller/meter/stringcombinerboxetc.
MSGID Message Transaction Id - required 123456789
for“Ondemand”/”Config”messagetype
,
request/response/acknowledgement/feedback
COMMAND Read/Write - Read
Applicableonlyincaseof“Ondemand”/”C
onfig”messageType
TIMESTAMP RTCtimestampofRMS/DCUagainstallparametersof 2019-08-20
vd/group(YYYY-MM-DDHH:mm:SS) 20:15:08
STINTERVAL PeriodicintervalatwhichRMSshallstoreandtransmit 15
datato server. (inminutes)
DATE localstoragedate–requiredasa referencetofetch data 2020-06-15
fromlocalstorage(YYYY-MM-DD)
INDEX LocalstorageIndex–requiredasareferencetofetch 5
datafromlocalstorage
MAXINDEX Localstorage maximumindexof localstoragedate– 96
requiredtocalculatemissingindex
LOAD Localstorageretrievalcommand&status 0
POTP PreviousOneTimePassword 12345678
COTP CurrentOne TimePassword, StateSWPSBrokerwill 12345678
updateOTPatintervalof30/60minutes
Parameter- EquipmentwiseKeywordsformultipleParameters.
1Parameter-
2Parameter-
3Parameter-
1
……..
Parameter-n

5 Page 9 of 27
 CommunicationFormatAnnexure

Annexure–1(Revision-B)PumpController

MessageName :PeriodicPushPumpController(1)
MessageFormat :JSON
MessageType :Data
Message Command :NotApplicableforDataperiodicPush
FlowMessage response :RMS->StateSWPSIoTPlatform
FlowMessageMedium :GPRS

CommandMessage

NotApplicable

ResponseMessage
Message Description Unit
{
"VD":1 VirtualDeviceIndex/Group -
"TIMESTAMP":"2020-05-18 RTCtimestampofRMS/DCUagainstall -
17:58:00", parametersof vd/group
“MAXINDEX”:96 maximumindexoflocalstoragedate -
"INDEX":7, referenceof localstorage -
"LOAD":0, Localstorageretrievalcommand&status -
"STINTERVAL":15, PeriodicintervalatwhichRMSshallstoreand -
transmitdata toserver.(inminutes)
"MSGID":"", Message Transaction Id - required -
for“Ondemand”/”Config” message
type,request/response/acknowledgement/fe
edb
ack
"DATE":200518, YYMMD
localstoragedate D
"IMEI":"1234561234561234", IMEINo. ofFirstSimtobe -
consideredalwaysforuniqueidentityofD
CU
"ASN_11":"34123450", PumpControllerSerialNo. -
RMS 0
DAQ 1-9
PumpController 11-19
Meter 21-29
Inverter 31-39
StringCombinerBox 41-49
"POTP":"341234", PreviousOneTime Password -
"COTP":"341234", CurrentOneTime Password -

6 Page 10 of 27
"PMAXFREQ1":"50.00", MaximumFrequency Hz

7 Page 10 of 27
"PFREQLSP1":"50.00", LowerLimitFrequency Hz
"PFREQHSP1":"50.00", Upper LimitFrequency Hz
"PCNTRMODE1":"1", SolarPumpControllerControlModeSt -
VariableFrequencyControl atus
0 Mode
1 CVTModeforSolar
2 MPPTmodeforSolar
"PRUNST1":"2", SolarPumpControllerRunStatus -
0 Stop
1 Running
2 Sleep
3 Low SpeedProtection
4 DryRunProtection
5 Over CurrentProtection
6 MinimumPowerProtection
"PREFFREQ1":"50.00", SolarPumpControllerReference Hz
Frequency
"POPFREQ1":"50.00", SolarPumpControllerOutput Hz
Frequency
"POPI1":"20.00", OutputCurrent A
"POPV1":"230.00", OutputVoltage V
"POPKW1":"45.00", OutputActivePower KW
"PDC1V1":"550.00", DCInputVoltage DCV
"PDC1I1":"50.00", DC Current DCI
"PDCVOC1":"650.00", DCOpenCircuitVoltage DCV
"PDKWH1":"35.00", TodayGeneratedEnergy KWH
"PTOTKWH1":"120.00", CumulativeGeneratedEnergy KWH
"POPFLW1":"2.00", FlowSpeed LPM
"POPDWD1":"120.00", DailyWaterDischarge Litres
"POPTOTWD1":"220.00", TotalWaterDischarge Litres
"PMAXDCV1":"750.00", MaxDCVoltage DCV
"PMAXDCI1":"40.00", MaxDCCurrent DCI
"PMAXKW1":"650.00", MaxOutputActivePower DCKW
"PMAXFLW1":"650.00", MaxFlowSpeed LPM
"PDHR1":"8.00", PumpDayRunHours Hrs
"PTOTHR1":"8.00", PumpCumulativeRunHours Hrs
}

Reaction

NotApplicable

8 Page 11 of 27
 CommunicationFormatAnnexure

Annexure-2 EnergyMeter

MessageName :PeriodicPushMeter(1)
Message :JSON
FormatMessage :Data
Type :NotApplicableforDataperiodicPush
Message Command :RMS->StateSWPSIoTPlatform
FlowMessage response :GPRS
FlowMessageMedium
CommandMessage

NotApplicable

ResponseMessage
Message Description
{
"VD":2 VirtualDeviceIndex/Group
"TIMESTAMP":"2020-05-18 RTCtimestampofRMS/DCUagainstall
17:58:00", parametersof vd/group
“MAXINDEX”:96 maximumindexoflocalstoragedate
"INDEX":7, referenceof localstorage
"LOAD":0, Localstorageretrievalcommand&status
"STINTERVAL":15, PeriodicintervalatwhichRMSshallstoreand
transmitdatatoserver.(inminutes)
"MSGID":"", Message Transaction Id - required
for“Ondemand”/”Config”messagetype
,
request/response/acknowledgement/feedback
"DATE":200518, localstoragedate

9 Page 12 of 27
"IMEI":"1234561234561234", IMEINo. ofFirstSimtobe consideredalwaysfor
uniqueidentityof DCU
"ASN_21":12345678, AssetSerialNumber
RMS 0
DAQ 1-9
PumpController 11-19
Meter 21-29
Inverter 31-39
StringCombinerBox 41-49
"MTDET1":30012302, MeterDetail
"POTP":"34123450", PreviousOneTime Password
"COTP":"34123450", CurrentOneTime Password
"MTBLDATE1":18, Billing Dateformeter1
"DATE1":180606, Presentdateformeter1
"TIME1":105400, Presenttimeformeter1
"IR1":20.58, RPhaseCurrentinAmps
"IY1":20.65, YPhaseCurrent inAmps
"IB1":20.12, BPhase CurrentinAmps
"VRN1":240.12, RPhasetoNeutralVoltage inVolts
"VYN1":242.13, YPhase toNeutralVoltageinVolts
"VBN1":243.55, BPhasetoNeutralVoltageinVolts
"VRY1":420.18, PhasetoPhaseVoltage(R-Y)in Volts
"VYB1":419.38, PhasetoPhaseVoltage(Y-B)inVolts
"VBR1":421.5, PhasetoPhaseVoltage(B-R)inVolts
"PFR1":0.98, R PhasePowerFactor
"PFY1":0.97, YPhase PowerFactor
"PFB1":0.96, BPhasePowerFactor
"FRQ1":50.05, Grid Frequency
"POWR1":42.578, RPhaseActivePowerinKW
"POWY1":42.156, YPhase ActivePowerinKW
"POWB1":42.354, BPhaseActivePowerinKW
"POW1":42.185, TotalActive PowerinKW
"RPOWR1":22.123, RPhaseReactivePowerinKVAR
"RPOWY1":20.110, YPhase Reactive Powerin KVAR
"RPOWB1":22.310, BPhaseReactivePowerinKVAR
"RPOW1":65.610, TotalReactivePowerinKVAR
"APOWR1":55.610, RPhaseApparent PowerinKVA
"APOWY1":52.910, YPhaseApparentPowerinKVA
"APOWB1":53.911, BPhase ApparentPowerinKVA
"APOW1":14.198, TotalApparentPowerinKVA
"KWHNET1":98561.4, CumulativeNetEnergyinKWH
"KWHIMP1":98561.4, Cumulative ImportEnergyinKWH
"KWHEXP1":98561.2, CumulativeExportEnergyinKWH
"KVAHNET1":99100.3, CumulativeNetEnergyinKVAH
"KVAHIMP1":99105.1, Cumulative ImportEnergyinKWH
"KVAHEXP1":98999.1, CumulativeExportEnergyinKWH
"MDKWIMP1":100.3, RisingDemand(Import)inKW
"MDKWEXP1":98.6, RisingDemand(Export)inKW

1 Page 13 of 27
0
"POFF1":1020, GridPowerFailureinMinutes
"TC1":100, TotalTamperCounts
"PF1":0.99, AveragePF
"LBKWHNET1":98561, LastBillingCycleNetEnergyinKWH
"LBKWHIMP1":98561, LastBillingCycleImportEnergy inKWH
"LBKWHEXP1":98561, LastBillingCycleExportEnergy in KWH
"PMDKVAIMP1":22.50, PresentMDKVAImport
"PMDKVAEXP1":0.00, PresentMDKVAImport
"LBMDKWIMP1":7.07, LastBillingMDKWImport
"LBMDKWEXP1":0.00, LastBillingMDKWExport
"LBMDKVAIMP1":7.07, LastBillingMDKVAImport
"LBMDKVAEXP1":0.00, LastBillingMDKVAExport
"MDRSTC1":4 MDResetCount

Reaction

NotApplicable

11 Page 14 of 27
 CommunicationFormatAnnexure

Annexure –3Inverter

MessageName :InverterPeriodicPush(INVERTER-1)
Message :JSON
FormatMessage :Data
Type :NotApplicableforDataperiodicPush
Message Command :RMS->StateSWPSIoTPlatform
FlowMessage response :GPRS
FlowMessageMedium
CommandMessage

NotApplicable

ResponseMessage
Message Description
{
"VD":5 VirtualDeviceIndex/Group
"TIMESTAMP":"2020-05- RTC timestamp of RMS/DCU against
1817:58:00", allparametersofvd/group
“MAXINDEX”:96 maximumindexoflocalstoragedate
"INDEX":7, referenceof localstorage
"LOAD":0, Localstorageretrievalcommand&status
"STINTERVAL":15, PeriodicintervalatwhichRMSshallstoreand
transmitdatatoserver.(inminutes)
"MSGID":"", Message Transaction Id - required
for“Ondemand”/”Config”messagetype
,
request/response/acknowledgement/feedback
"DATE":200518, localstoragedate
"IMEI":"1234561234561234", IMEINo. ofFirstSimtobe
consideredalwaysforuniqueidentityofDCU
"ASN_31":"34123450", InverterSerialNo.
12 Page 15 of 27
 RMS 0
DAQ 1-9
PumpController 11-19
Meter 21-29
Inverter 31-39
StringCombinerBox 41-49
"POTP":"34123450", PreviousOneTime Password
"COTP":"34123450", CurrentOneTime Password
"IST1":1, InverterStatus
"IFREQ1":40, Frequency
"IPF1":0.8, PowerFactor
"IDC1V1":500, DC-1Voltage
"IDC1I1":200, DC-1Current
"IDC1KW1":200, DC-1 Power
"IDC2V1":243.55, DC-2Voltage
"IDC2I1":420.18, DC-2Current
"IDC2KW1":200, DC-2 Power
"IDC3V1":419.38, DC-3Voltage
"IDC3I1":421.8, DC-3Current
"IDC3KW1":200, DC-3 Power
"IDC4V1":0.98, DC-4Voltage
"IDC4I1":0.97, DC-4Current
"IDC4KW1":200, DC-4 Power
"IRPHV1":0.96, Rphase voltage
"IRPHI1":50.05, Rphasecurrent
"IRPHKW1":50.05, RphaseActivePower
"IYPHV1":42.578, Yphase voltage
"IYPHI1":42.156, Yphasecurrent
"IYPHKW1":50.05, YphaseActivePower
"IBPHV1":42.354, Bphase voltage
"IBPHI1":42.185, Bphasecurrent
"IBPHKW1":50.05, BphaseActivePower
"IKW1":22.123, ActivePower
"ITKWH1":20.110, TodayGeneratedEnergy
"ITON1":22.310, TodayOnTime ofInverter
"ILKWH1":65.610, LifetimeGeneratedEnergy
"ILON1":55.610, Lifetimerunninghours
"ITEMP1":52.910, InverterTemperature
"IFT11":53.911, Fault-1
"IFT21":14.198, Fault-2
"IFT31":98561.4, Fault-3
"IFT41":98561.4, Fault-4
"IFT51":98561.2, Fault-5
"IKVA1":99100.3, Apparentpower
"IKVAR1":99105.1 Reactivepower
}

13 Page 16 of 27
 Reaction

NotApplicable

CommunicationFormatAnnexure

Annexure- 4StringCombinerBox

MessageName :PeriodicPushStringCombinerBox
Message :JSON
FormatMessage :Data
Type :NotApplicableforDataperiodicPush
Message Command :RMS->StateSWPSIoTPlatform
FlowMessage response :GPRS
FlowMessageMedium
CommandMessage

NotApplicable

ResponseMessage
Message Description
{
"VD":9 VirtualDeviceIndex/Group
"TIMESTAMP":"2020-05- RTC timestamp of RMS/DCU against
1817:58:00", allparametersofvd/group
“MAXINDEX”:96 maximumindexoflocalstoragedate
"INDEX":7, referenceof localstorage
"LOAD":0, Localstorageretrievalcommand&status
"STINTERVAL":15, Periodic interval at which RMS shall store
andtransmitdatatoserver.(inminutes)
"MSGID":"", MessageTransactionId-requiredfor
“Ondemand”/”Config” message
type,request/response/acknowledgement/feedback
"DATE":200518, localstoragedate
"IMEI":"1234561234561234", IMEINo.ofFirstSimtobeconsideredalwaysfor
uniqueidentityof DCU
"ASN_41":"34123450", SJBSerialno
RMS 0
DAQ 1-9

14 Page 17of 27
 PumpController 11-19
Meter 21-29
Inverter 31-39
StringCombinerBox 41-49
"POTP":"34123450", PreviousOneTime Password
"COTP":"34123450", CurrentOneTime Password
"SI11":"3.00", SJB1,Channel1Current
"SI21":"5.00", SJB1,Channel2Current
"SI31":"5.00", SJB1,Channel3Current
"SI41":"5.00", SJB1,Channel4Current
"SI51":"5.00", SJB1,Channel5Current
"SI61":"5.00", SJB1,Channel6Current
"SI71":"5.00", SJB1,Channel7Current
"SI81":"5.00", SJB1,Channel8Current
"SI91":"5.00", SJB1,Channel9Current
"SI101":"5.00", SJB1,Channel10Current
"SI111":"5.00", SJB1,Channel11Current
"SI121":"5.00", SJB1,Channel12Current
"SI131":"5.00", SJB1,Channel13Current
"SI141":"5.00", SJB1,Channel14Current
"SI151":"5.00", SJB1,Channel15Current
"SI161":"5.00", SJB1,Channel16Current
"SI171":"5.00", SJB1,Channel17Current
"SI181":"5.00", SJB1,Channel18Current
"SI191":"5.00", SJB1,Channel19Current
"SI201":"5.00", SJB1,Channel20Current
"SI211":"5.00", SJB1,Channel21Current
"SI221":"5.00", SJB1,Channel22Current
"SI231":"5.00", SJB1,Channel23Current
"SI241":"5.00", SJB1,Channel24Current
"SDCV1":"635.00", SJB1,DCVoltage
"SDCTOTI1":"40.00", SJB1,TotalDC Current
"SDCTOTKW1":"28.00", SJB1,TotalDC Power
"SDI11":"1.00", SJB1,DigitalInput1
"SDI21":"1.00", SJB1,DigitalInput2
"ST11":"1.00", SJB1,Temperature1
"ST21":"1.00", SJB1,Temperature2
"ST31":"1.00" SJB1,Temperature3
}

Reaction

NotApplicable

15 Page 18 of 27
 CommunicationFormatAnnexure

Annexure–5RMS

MessageName :RMS
MessageFormat :JSON
MessageType :Heartbeat
Message Command :NotApplicable
FlowMessage response :RMS->StateSWPSIoTPlatform
FlowMessageMedium :GPRS

CommandMessage

NotApplicable

ResponseMessage
Message Description
{
"VD":0 VirtualDeviceIndex/Group
"TIMESTAMP":"2020-05-18 RTCtimestampofRMS/DCUagainstall
17:58:00", parametersof vd/group
“MAXINDEX”:96 maximumindexoflocalstoragedate
"INDEX":7, referenceof localstorage
"LOAD":0, Localstorageretrievalcommand&status
"STINTERVAL":15, Periodicintervalat which RMS shallstoreand
transmitdatatoserver.(inminutes)
"MSGID":"", Message Transaction Id - required
for“Ondemand”/”Config”messagetype
,
request/response/acknowledgement/feedback
"DATE":200518, localstoragedate
"IMEI":"1234561234561234", IMEINo. ofFirstSimtobe consideredalwaysfor
uniqueidentityof DCU
"POTP":"341234", PreviousOneTime Password
"COTP":"341234", CurrentOneTime Password
"GSM":1, DeviceconnectedtoGSMnetwork
"SIM":1, SIMdetected (1-detected)
"NET":1, Devicein Network(1-innetwork)
"GPRS":"1", GPRSconnected (1-connected)
16 Page 19 of 27
"RSSI":22, SignalStrength
"SD":"1", SDcarddetected(1 -detected)
"ONLINE":1, DeviceOnline (1-Online)
“GPS”:1, GPSModuleStatus(1-ON,0-OFF)
“GPSLOC”:1, GPSLocationLocked
“RF”:1, RFModuleStatus(1-ON,0-OFF)
"RTCDATE":180918, RTCDate
"RTCTIME":175800, RTCTime
“TEMP”:45.5, DeviceTemperature
“LAT”:19.06, Latitudefromgps
“LONG”:72.8777, Longitudefromgps
“SIMSLOT”:1, SimSlot(CurrentSimSlot:1or2)
“SIMCHNGCNT”:10, TotalSim SlotChange Count
“FLASH”:1, Device FlashStatus1:Detected0:Error
“BATTST”:0, BatteryInputStatus:1if onbattery powerelse0
“VBATT”:5.0, BatteryVoltage
“PST”:1 PowerSupply(1-Mains,2-Battery)
}

Reaction

NotApplicable

17 Page 20 of 27
 CommunicationFormatAnnexure

Annexure–6DAQSystem

MessageName :PeriodicPushDAQSystem
MessageFormat :JSON
MessageType :Data
Message Command :NotApplicableforDataperiodicPush
FlowMessage response :RMS->StateSWPSIoTPlatform
FlowMessageMedium :GPRS

CommandMessage

NotApplicable

ResponseMessage
Message Description
{
"VD":12 VirtualDeviceIndex/Group
"TIMESTAMP":"2020-05-18 RTCtimestampofRMS/DCUagainstall
17:58:00", parametersofvd/group
“MAXINDEX”:96 maximumindexoflocalstoragedate
"INDEX":7, referenceof localstorage
"LOAD":0, Localstorageretrievalcommand&status
"STINTERVAL":15, PeriodicintervalatwhichRMSshallstoreand
transmitdatatoserver.(inminutes)
"MSGID":"", Message Transaction Id - required
for“Ondemand”/”Config”messagetype
,
request/response/acknowledgement/feedback
"DATE":200518, localstoragedate
"IMEI":"1234561234561234", IMEINo. ofFirstSimtobe consideredalwaysfor
uniqueidentityofDCU
"POTP":"34123450", PreviousOneTime Password
"COTP":"34123450", CurrentOneTime Password
“AI11”:45.5, AnalogInput–1
“AI21”:45.5, AnalogInput–2
“AI31”:45.5, AnalogInput–3
“AI41”:45.5, AnalogInput–4
18 Page 21 of 27
“DI11”:1, DigitalInput–1
“DI21”:0, DigitalInput–2
“DI31”:1, DigitalInput–3
“DI41”:0, DigitalInput–4
“DO11”:1, DigitalOutput–1
“DO21”:1, DigitalOutput–2
“DO31”:1, DigitalOutput–3
“DO41”:1 DigitalOutput–4
}

Reaction

NotApplicable

19 Page 22 of 27
 Annexure-7

MessageName :OnDemandRead/WriteParameter/Keyword
Message :JSON
FormatMessage :Config
Type :CloudServer->RMS
MessageCommandFlow :RMS->Cloud Server
Message Response :GPRS

CommandMessage
Message Description
{
"timestamp":"2018-09-1817:58:00",
"type":"config",
"cmd":"write", Towriteconfig
"msgid":"130", ServerAutoGenerated
"APN1":“www” APNValueforsim1
"USR1":"string" sim1username
"PASS1":"string" sim1password
"APN2":“Internet” APNValueforsim2
"USR2":"string" Sim2username
"PASS2":"string" Sim2password
TorestartDCU,1:Execute
"RESTART":1
command
"UPDATEINTERVAL":15 Enterupdateintervalinmins.
HeartbeatUpdateIntervalin
"HEARTINTERVAL":5
mins
DCURTCDate(YYMMDD)
"URTCDATE":200622
Update
DCURTCTime(HH:MM:SS)
"URTCTIME":220312
Update-24 hourformat
Update RTC, 1:
"UPDATERTC":1 Executecommand,0
:Successful
execution
RTCautoGSMsynchronization,1
"GSMSYNC":1
:toexecutecommand
PumpRemoteON/OFF
"DO1":1
Operation(1-ON,0-OFF)
Engineering Zero Value (4
"AI1ZERO":1 mAdc)forAI1
E.G.0(LPM)
"AI1SPAN":100 EngineeringSpanValue(20mAd
c)forAI1
E.G.5000(LPM)
Engineering ZeroValue(4mA
"AI2ZERO":1
dc)forAI2

20 Page 23 of 27
"AI2SPAN":100 EngineeringSpanValue(20mA
dc)forAI2
EngineeringZeroValue(4mA
"AI3ZERO":1
dc)forAI3
"AI3SPAN":100 EngineeringSpanValue(20mA
dc)forAI3
EngineeringZeroValue(4mA
"AI4ZERO":1
dc)forAI4
"AI4SPAN":100 EngineeringSpanValue(20mA
dc)forAI4
"URL":”rms1.kusumiiot.co” URLofBrokerServer
"PORT":8883 PortofBrokerServer
"CID":"d:860906045525646$standalonesolarpump$27" UniqueClientidofdevice
"USERNAME":"860906045525646$standalonesolarpump$27" Usernamefordevice
authentication
"PASSWORD":"9e0baa73" Passwordfordevice
authentication
"FTPURL":"rms1.kusumiiot.co" URLforFTP
"FTPUSER":"866191037709301" UsernameforFTP
"FTPPASS":"908552f" PasswordforFTP
"FTPPORT":22 PortforFTP
"FTPDOWN":1 DownloadCertificatesfromftp1
:Toexecutecommand,
0: Command is
successfullyexecuted
}

ResponseMessage
Message Description
{
"timestamp":"2018-09-1817:58:00",
"type":"config",
"cmd":"write", Towriteconfig
"msgid":"130", ServerAutoGenerated
"APN1":“www” APNValueforsim1
"USR1":"string" sim1username
"PASS1":"string" sim1password
"APN2":“Internet” APNValueforsim2
"USR2":"string" Sim2username
"PASS2":"string" Sim2password
TorestartDCU,1:Execute
"RESTART":1
command
"UPDATEINTERVAL":15 Enterupdateintervalinmins.
HeartbeatUpdateIntervalin
"HEARTINTERVAL":5
mins

21 Page 24 of 27
 DCURTCDate(YYMMDD)
"URTCDATE":200622
Update
DCURTCTime(HH:MM:SS)
"URTCTIME":220312
Update-24 hourformat
Update RTC, 1:
"UPDATERTC":1 Executecommand,0
:Successful
execution
RTCautoGSMsynchronization,
"GSMSYNC":1
1:toexecutecommand
PumpRemoteON/OFF
"DO1":1
Operation(1-ON,0-OFF)
Engineering Zero Value (4
"AI1ZERO":1 mAdc)forAI1
E.G.0(LPM)
"AI1SPAN":100 EngineeringSpanValue(20mAd
c)forAI1
E.G.5000(LPM)
EngineeringZeroValue(4mA
"AI2ZERO":1
dc)forAI2
"AI2SPAN":100 EngineeringSpanValue(20mA
dc)forAI2
EngineeringZeroValue(4mA
"AI3ZERO":1
dc)forAI3
"AI3SPAN":100 EngineeringSpanValue(20mA
dc)forAI3
EngineeringZeroValue(4mA
"AI4ZERO":1
dc)forAI4
"AI4SPAN":100 EngineeringSpanValue(20mA
dc)forAI4
"URL":”rms1.kusumiiot.co” URLofBrokerServer
"PORT":8883 PortofBrokerServer
"CID":"d:860906045525646$standalonesolarpump$27" UniqueClientidofdevice
"USERNAME":"860906045525646$standalonesolarpump$27" Usernamefordevice
authentication
"PASSWORD":"9e0baa73" Passwordfordevice
authentication
"FTPURL":"rms1.kusumiiot.co" UrlforFTP
"FTPUSER":"866191037709301" UsernameforFTP
"FTPPASS":"908552f" PasswordforFTP
"FTPPORT":22 PortforFTP
"FTPDOWN":1 DownloadCertificatesfromftp1
:Toexecutecommand,
0: Command is
successfullyexecuted
}

22 Page 25 of 27
 CommandMessage

Command–
B.Incase,ifsomekeyincommandareinv
alid
Message Description
{
"timestamp":"2018-09-1817:58:00",
"type":"config",
"cmd":"write", towriteconfig
"msgid":"130, serverautogenerated
"APNN1":2 sendvalue"2"
"USR1":"xyz" sendvalue"xyz"
}

ResponseMessage
Message Description
{
"timestamp":"2018-09-1817:58:00",
"type":"config",
"cmd":"write", towriteconfig
"msgid":"130", serverautogenerated
"APNN1":0 invalidKey,valuewill bereturned '0'
"USR1":"xyz" actualvaluereceived
}

Reaction

NotApplicable

23 Page 26 of 27