<xml>
<meter>
<serial>Meter's serial</serial>
<id>Meter's user defined name</id>
<before>
  <result>SUCCESS/ERROR:error message</result>
  <date>Date of this total. (The total before the given time)</date>
  <P1>Active import (kWh). Does not reclock. With secondary metering this is the value after the multiplier</P1>
  <P2>Active export (kWh). With secondary metering this is the value after the multiplier</P2>
  <Q1>Reactive energy register quadrant 1 (kvarh). Does not reclock.</Q1>
  <Q2>Reactive energy register quadrant 2 (kvarh)</Q2>
  <Q3>Reactive energy register quadrant 3 (kvarh)</Q3>
  <Q4>Reactive energy register quadrant 4 (kvarh)</Q4>
  <P1READING>Unmodified active import as read from the meter. Re-clocks. No multiplier</P1READING>
  <Q1READING>Unmodified reactive energy as read from the meter. Re-clocks. No multiplier</Q1READING>
  <STATUS>See Note 4</STATUS>
</before>
<after>
  <result>SUCCESS/ERROR:error message</result>
  <date>Date of this total. (The total after the given time)</date>
  <P1>Active import (kWh). Does not reclock. With secondary metering this is the value after the multiplier</P1>
  <P2>Active export (kWh). With secondary metering this is the value after the multiplier</P2>
  <Q1>Reactive energy register quadrant 1 (kvarh). Does not reclock.</Q1>
  <Q2>Reactive energy register quadrant 2 (kvarh)</Q2>
  <Q3>Reactive energy register quadrant 3 (kvarh)</Q3>
  <Q4>Reactive energy register quadrant 4 (kvarh)</Q4>
  <P1READING>Unmodified active import as read from the meter. Reclocks. No multiplier</P1READING>
  <Q1READING>Unmodified reactive energy as read from the meter. Reclocks. No multiplier</Q1READING>
  <STATUS>See Note 4</STATUS>
</after>
<on_time>
  <result>SUCCESS/ERROR:error message</result>
  <date>The date as close to the given time as possible, using profile.</date>
  <P1>Active import (kWh). Does not reclock. With secondary metering this is the value after the multiplier</P1>
  <P2>Active export (kWh). With secondary metering this is the value after the multiplier</P2>
  <Q1>Reactive energy register quadrant 1 (kvarh). Does not reclock.</Q1>
  <Q2>Reactive energy register quadrant 2 (kvarh)</Q2>
  <Q3>Reactive energy register quadrant 3 (kvarh)</Q3>
  <Q4>Reactive energy register quadrant 4 (kvarh)</Q4>
  <P1READING>Unmodified active import as read from the meter. Reclocks. No multiplier</P1READING>
  <Q1READING>Unmodified reactive energy as read from the meter. Reclocks. No multiplier</Q1READING>
  <STATUS>See Note 4</STATUS>
</on_time>
</xml>

<xml><meter>
<serial>Meter's serial</serial>
<id>Meter's user defined name</id>
<start_total>
  <result>SUCCESS/ERROR:error message</result>
  <date>Date of start total.</date>
  <P1>Active import (kWh). Does not reclock. With secondary metering this is the value after the multiplier</P1>
  <P2>Active export (kWh). With secondary metering this is the value after the multiplier</P2>
  <Q1>Reactive energy register quadrant 1 (kvarh). Does not reclock.</Q1>
  <Q2>Reactive energy register quadrant 2 (kvarh)</Q2>
  <Q3>Reactive energy register quadrant 3 (kvarh)</Q3>
  <Q4>Reactive energy register quadrant 4 (kvarh)</Q4>
  <P1READING>Unmodified active import as read from the meter. Reclocks. No multiplier</P1READING>
  <Q1READING>Unmodified reactive energy as read from the meter. Reclocks. No multiplier</Q1READING>
  <STATUS>See Note 4</STATUS>
</start_total>
<end_total>
  <result>SUCCESS/ERROR:error message</result>
  <date>Date of end total.</date>
  <P1>Active import (kWh). Does not reclock. With secondary metering this is the value after the multiplier</P1>
  <P2>Active export (kWh). With secondary metering this is the value after the multiplier</P2>
  <Q1>Reactive energy register quadrant 1 (kvarh). Does not reclock.</Q1>
  <Q2>Reactive energy register quadrant 2 (kvarh)</Q2>
  <Q3>Reactive energy register quadrant 3 (kvarh)</Q3>
  <Q4>Reactive energy register quadrant 4 (kvarh)</Q4>
  <P1READING>Unmodified active import as read from the meter. Reclocks. No multiplier</P1READING>
  <Q1READING>Unmodified reactive energy as read from the meter. Reclocks. No multiplier</Q1READING>
  <STATUS>See Note 4</STATUS>
</end_total>
<max_demand>
  <result>SUCCESS/ERROR:error message</result>
  <date>The date as close to the given time as possible, using profile.</date>
  <kVA>The calculated kVA</kVA>
</max_demand>
</meter></xml>

<xml>
<meter>
<serial>Meter's serial</serial>
<id>Meter's user defined name</id>
<profile>
<sample>
  <result>SUCCESS</result>
  <date>Date of this sample.</date>
  <P1>Active import (kW). Does not count up. With secondary metering this is the value after the multiplier</P1>
  <P2>Active export (kvar). With secondary metering this is the value after the multiplier</P2>
  <Q1>Reactive energy register quadrant 1 (kW). Does not count up.</Q1>
  <Q2>Reactive energy register quadrant 2 (kvar)</Q2>
  <Q3>Reactive energy register quadrant 3 (kvar)</Q3>
  <Q4>Reactive energy register quadrant 4 (kvar)</Q4>
  <STATUS>See Note 4</STATUS>
</sample>
... (more samples)
</profile>
</meter>
</xml>

<xml>
<result>SUCCESS</result>
<meter_account>
<id>Meter's serial</id>
<meter>
  <serial>Serial of meter</serial>
  <portion>Portion of meter in this account</portion>
  <period>Period in which meter's profile is stored in seconds (e.g. 1800 = half hour)</period>
</meter>
.. more meters
<profile>
<sample>
  <date>Date of this sample.</date>
  <P1>Active import (kW). Does not count up. With secondary metering this is the value after the multiplier</P1>
  <P2>Active export (kWh). With secondary metering this is the value after the multiplier</P2>
  <Q1>Reactive energy register quadrant 1 (kvarh). Does not reclock.</Q1>
  <Q2>Reactive energy register quadrant 2 (kvar)</Q2>
  <Q3>Reactive energy register quadrant 3 (kvar)</Q3>
  <Q4>Reactive energy register quadrant 4 (kvar)</Q4>
</sample>
... (more samples)
</profile>
</meter_account>
</xml>

<xml>
<result>SUCCESS</result>
<clas>
<id>The class ID</id>
<descr>Human readable name for class</descr>
<category>Categories of class.
Categories are:
<ul><li>TODO</li></ul></category>
<mports>
  <mport>
    <id>ID of import</id>
    <iid>ID of interface that this import refers to</iid>
    <num>Number of times that this import imports the interface</num>
    <descr>Description of import (If there are multiple imports)</descr>
  </mport>
  ... (more interfaces imported)
</mports>
<xports>
  <xport>
    <id>ID of export</id>
    <iid>ID of interface that this import refers to</iid>
    <descr>Description of export</descr>
  </xport>
  ... (more interfaces exported)
</xports>
<key1name>
what is key1 called for this class, e.g. ID
</key1name>
<key2name>
what is key1 called for this class, e.g. Name
</key2name>
</clas>
</xml>

<xml>
  <result>SUCCESS</result>
  <interf><id>Interface ID</id>
    <descr>Description of interface</descr>
  </interf>
</xml>

<xml>
  <result>SUCCESS</result>
  <ent>
    <id>id of entity</id>
    <cid>class id</cid>
    <key1>Entities first/system name</key1>
    <key2>Entities second/human name</key2>
    <mports>
      <mport>
        <mid>Interface ID imported</mid>
        <num>Number of times that interface is imported</num>
        <deid>
          ID of the entity imported with this interface.
          The depended Entity ID.
          e.g. A GPRS modem depends on a SIM.
          Calling getEntity on the modem, will then give the SIMs ID here once they are linked up.
        </deid>
        <xid>The export ID of the imported entity.
        This is required because some entities export interfaces multiple times.
        e.g. A SIM exports xid 2 (which points to the SIM interface) and a modem imports mid 1 (which points to the SIM interface)</xid>
      </mport>
      ... (more imports)
    </mports>
    <xports>
      <xport>
        <xid>Interface ID exported</xid>
        <num>Number of times that interface is exported</num>
        <eid>
          ID of the entity exported with this interface.
          The dependent Entity ID.
          e.g. A GPRS modem depends on a SIM.
          Calling getEntity on the SIM, will then give the modem's ID here once they are linked up.
        </eid>
        <mid>The import ID of the exported entity.</mid>
      </xport>
      ... (more exports)
    </xports>
  </ent>
</xml>

<xml>
  <result>SUCCESS</result>
  <clas><id>Class ID</id></clas>
  ... (more classes)
</xml>

<xml>
  <result>SUCCESS</result>
  <clas><id>Class ID</id></clas>
  ... (more classes)
</xml>

<xml><result>SUCCESS</result><entities>
  <entity><id>Entity ID</id></entity>
  ... (more entities)
  </entities>
  <len>Amount of entities passed</len>
</xml>

<xml>
  <result>SUCCESS</result>
  <classes>
    <clas><id>ID of class</id></clas>
    ...(more classes)
  </classes>
</xml>

<xml>
  <result>SUCCESS</result>
  <date>the last profile date</date>
  <meters>
    <meter>
      <p1>
        comma delimited string with 48 values ordered by time starting with 00:30. Units of Measure is kWh or kl
      </p1>
      <q1>
        comma delimited string with 48 values ordered by time starting with 00:30 – only included if parameter set to true. Units of Measure is kvarh
      </q1>
      <kVA>max demand in the 24hour period</kVA>
      <Status>
        The lower 7 bits are used to represent a NUMBER for the STATUS sample,
        that can mean different things for different meters.
        The higher bits after that have generic meanings, and can be
        simultaneously set to mean more than one thing at the same time:
        UNDER VOLTAGE            = 0x0080
        OVER VOLTAGE             = 0x0100
        REVERSE FLOW             = 0x0200
        OVER CURRENT             = 0x0400
        OVER ENERGY              = 0x0800
        CALC IMPORTED            = 0x1000
        CALC INTERPOLATED        = 0x2000
        CALC ALMOST INTERPOLATED = 0x4000
        GAPS                     = 0x8000
      </Status>
      <e1>total + profile up to the enddate (kWh)</e1>
      <f1>total +profile up to the enddate (kvarh)</f1>
      <cid>Class ID</cid>
      <primary>if primary metering "Y", else "N"</primary>
      <serial>Meter's serial</serial>
      <key2>Meter's user defined name</key2>
      <key3>Meter's Key3 (which may be null)</key3>
    </meter>
    ...next meter...
  </meters>
<xml>

<xml>
  <result>SUCCESS</result>
  <date>the last total date</date>
  <meters>
    <meter>
      <p1>
        comma delimited string with 48 values ordered by time starting with 00:30
      </p1>
      <q1>
        comma delimited string with 48 values ordered by time starting with 00:30 – only included if parameter set to true
      </q1>
      <kVA>max demand in the 24hour period</kVA>
      <Status>
        The lower 7 bits are used to represent a NUMBER for the STATUS sample,
        that can mean different things for different meters.
        The higher bits after that have generic meanings, and can be
        simultaneously set to mean more than one thing at the same time:
        UNDER VOLTAGE            = 0x0080
        OVER VOLTAGE             = 0x0100
        REVERSE FLOW             = 0x0200
        OVER CURRENT             = 0x0400
        OVER ENERGY              = 0x0800
        CALC IMPORTED            = 0x1000
        CALC INTERPOLATED        = 0x2000
        CALC ALMOST INTERPOLATED = 0x4000
        GAPS                     = 0x8000
      </Status>
      <e1>total + profile up to the enddate (kWh)</e1>
      <f1>total + profile up to the enddate (kvarh)</f1>
      <e1_start>total + profile up to the startdate (kWh)</e1_start>
      <f1_start>total + profile up to the startdate (kvarh)</f1_start>
      <consumtpion>e1 - e1_start(kWh)</consumtpion>
      <cid>Class ID</cid>
      <primary>if primary metering "Y", else "N"</primary>
      <serial>Meter's serial</serial>
      <key2>Meter's user defined name</key2>
      <key3>Meter's Key3 (which may be null)</key3>
    </meter>
    ...next meter...
  </meters>
<xml>

<xml>
<result>SUCCESS</result>
<meter>
  <serial>Serial</serial>
  <name>Name of meter</name>
  <total>
    <date>date of this total</date>
    <E1>Total Energy reading (Active import - this is the default of most meters) kWh</E1>
    <E2>Total Reverse Active Energy reading (this is left out if zero)</E2>
    <F1>Total Reactive Energy reading (Quadrant 1 - forward lagging) (this is left out if zero) kvarh</F1>
    <F2>Total Reactive Energy reading (Quadrant 2 - reverse leading) (this is left out if zero)</F2>
    <F3>Total Reactive Energy reading (Quadrant 3 - reverse lagging) (this is left out if zero)</F3>
    <F4>Total Reactive Energy reading (Quadrant 4 - forward leading) (this is left out if zero)</F4>
    <status>See Note 4</status>
  </total>
  next total...
next meter...
</meter>
</xml>

<xml>
<result>SUCCESS</result>
<meter>
  <serial>Serial</serial>
  <name>Name of meter</name>
  <fault>
    <faultid>Unique ID of fault</faultid>
    <init_date>Create date of Fault.</init_date>
    <initiator>Login of person that created the fault, followed by double colon, and then the first and last name</initiator>
    <cnumber>ID of linked Meter Account, if any</cnumber>
    <symptom>Free form description of symptom.</symptom>
    <technician>Login of technician assigned to fault, followed by double colon, and then the first and last name</technician>
    <finding>Free form description of finding</finding>
    <responsible>Login of person responsible to sort out fault, followed by double colon, and then the first and last name</responsible>
    <action>Free form description of action to take</action>
    <clear_date>Date Fault was cleared, or null</clear_date>
    <cleared>Y if fault has been cleared</cleared>
    <toinvoice>Y/N</toinvoice>
    <newwork>Y/N</newwork>
    <jobnum>Job number, or blank if none</jobnum>
  </fault>
  next fault...
next meter...
</meter>
</xml>

<xml>
<fault>
  <serial>Meter's serial</serial>
  <faultid>blank for new, or the ID of the fault to update</faultid>
  <initiator>login of person that made the fault, cannot be blank</initiator>
  <cnumber>ID of Meter Account</cnumber>
  <symptom>Free form description of sympton</symptom>
  <technician>full login of technician assigned, or blank for none</technician>
  <finding>Free form description of finding</finding>
  <responsible>full login of person responsible for following up on this fault, or blank for none</responsible>
  <action>Free form description of action</action>
  <cleared>Y if cleared</cleared>
  <clear_date>if cleared Y, then this is the date it was cleared</clear_date>
  <toinvoice>Y if this is to invoice for</toinvoice>
  <newwork>Y if new work</newwork>
  <jobnum>the job number or blank if none</jobnum>
</fault>
</xml>
  

<xml>
<xml>
  <fault>
    <faultid>id of fault added</faultid>
    <serial>serial number</serial>
    <result>SUCCESS</result>
  </fault>
  ...next fault
</xml>

<xml>
  <result>SUCCESS</result>
  <form>
    <type>text/hidden/checkbox/select/textarea</type>
    <value>The value of the input submitted by the form.</value>
    <flag>"checked" for checkboxes</flag>
  </form>
</xml>

<xml>
 <result>SUCCESS</result>
 <startdate>Start Date (YYYY-MM-DD HH:MM:SS)</startdate>
 <enddate>End Date (YYYY-MM-DD HH:MM:SS)</enddate>
 <published>P</published>
 <key1>Meter Account id</key1>
 <key2>Meter Account description</key2>
 <util>Utility of account, e.g. Electricity or Water</util>
 <currency>Currency Symbol of Bill</currency>
 <align>Is the symbol pre-pended or post-pended to the amount?</align>
 <tariff>the name of the tariff that was used</tariff>
 <taxtype>the description of the tax to add, e.g. VAT</taxtype>
 <taxperc>the percentage of the tax to add</taxperc>
 <items> amount of li items in bill</items>
 <bill>
  <li>
   <tname> Description of tariff line item</tname>
   <desc1> Description 1 of bill line item</desc1>
   <desc2> Description 2 of bill line item</desc2>
   <units> Quantity of units that is billed in this line</units>
   <rate> Price per unit</rate>
   <amount> Total amount (units multiplied by rate)</amount>
   <unitsunit> The unit in which this item is measured, e.g. kWh, kl, etc.</unitsunit>
   <type> An indication of what type of algorithm was followed to calculate the amount of this item</type>
   <compareId> this is used to be able to compare similar line item fields accross months, e.g. Peak (LS) and Peak (HS)</compareId>
   <tarifflineid> this is a unique identifier per tariff line item</tarifflineid>
  </li>
  ... next li ...
 </bill>
 <readings>
  <mr>
   <snumber>This is the meter serial number</snumber>
   <mtype>This is the meter type</mtype>
   <start>
    <date>date of the start reading for this meter for this bill</date>
    <E1>Total Energy reading (Active import - this is the default of most meters) kWh</E1>
    <E2>Total Reverse Active Energy reading (this is left out if zero)</E2>
    <F1>Total Reactive Energy reading (Quadrant 1 - forward lagging) (this is left out if zero) kvarh</F1>
    <F2>Total Reactive Energy reading (Quadrant 2 - reverse leading) (this is left out if zero)</F2>
    <F3>Total Reactive Energy reading (Quadrant 3 - reverse lagging) (this is left out if zero)</F3>
    <F4>Total Reactive Energy reading (Quadrant 4 - forward leading) (this is left out if zero)</F4>
    .. alternatively, if for example water, this could be ..
    <W1>Total Water reading (kl)</W1>
   </start>
   <end>The end reading... follows the same format as the start reading</end>
  </mr>
  ... next meter reading (mr) ...
 </readings>
</xml>

<xml>
  <result>Pls Specify startdate and enddate</result>
  <key1>Meter Account id</key1>
  <key2>Meter Account Name</key2>
  <util>Utility of account, e.g. Electricity or Water</util>
  <bills>
    <bill>
      <startdate>Start Date of Bill Run (YYYY-MM-DD HH:MM:SS.mmm)</startdate>
      <enddate>End Date of Bill Run (YYYY-MM-DD HH:MM:SS.mmm)</enddate>
      <brid>2126203</brid>
    </bill>
    ... repeated for each bill run
  </bills>
</xml>

<xml>
  <result>SUCCESS</result>
  <startdate>Start Date of Bill Run (YYYY-MM-DD HH:MM:SS.mmm)</startdate>
  <enddate>End Date of Bill Run (YYYY-MM-DD HH:MM:SS.mmm)</enddate>
  <key1>Meter Account id</key1>
  <key2>Meter Account Name</key2>
  <util>Utility of account, e.g. Electricity or Water</util>
  <brid>Bill Run ID</brid>
  <currency>Currency Symbol of Bill</currency>
  <align>Is the symbol pre-pended or post-pended to the amount?</align>
  <tariff>the name of the tariff that was used</tariff>
  <taxtype>the description of the tax to add, e.g. VAT</taxtype>
  <taxperc>the percentage of the tax to add</taxperc>
  <currency_decimals>is the amount of decimals in the currency, e.g. usually 2 for cents</currency_decimals>
  <items>amount of li items in bill</items>
  <bill>
    <li>
      <tname>Description of tariff line item</tname>
      <desc1>Description 1 of bill line item</desc1>
      <desc2> Description 2 of bill line item</desc2>
      <units>Quantity of units that is billed in this line</units>
      <rate>Price per unit</rate>
      <amount>Total amount (units multiplied by rate)</amount>
      <unitsunit>The unit in which this item is measured, e.g. kWh, kl, etc.</unitsunit>
      <type>An indication of what type of algorithm was followed to calculate the amount of this item</type>
      <compareId>this is used to be able to compare similar line item fields accross months, e.g. Peak (LS) and Peak (HS)</compareId>
    </li>
    ... more per bill line item
  </bill>
  <readings>
    <mr>
      <snumber>Serial of Meter</snumber>
      <mtype>This is the meter type</mtype>
      <start>
        <date>Start date</date>
        <E1>Total Energy reading and unit at time of bill start (Active import - this is the default of most meters)</E1>
        <F1>Total Reactive Energy reading and unit at time of bill start (Quadrant 1 - forward lagging) (this is left out if zero)</F1>
      </start>
      <end>
        <date>End date</date>
        <E1>Total Energy reading and unit at time of bill end (Active import - this is the default of most meters)</E1>
        <F1>Total Reactive Energy reading and unit at time of bill end (Quadrant 1 - forward lagging) (this is left out if zero)</F1>
      </end>
    </mr>
  </readings>
</xml>

<xml>
 <result>SUCCESS</result>
 <id>They key1 of the Meter Account</id>
 <name>They key2 of the Meter Account</name>
 <utility>The utility of the Meter Account, e.g. Electricity or Water</utility>
 <meters>
  <meter>
    <eid>Entity id of meter in meter account</eid>
    <key1>key1 of meter (the serial number)</key1>
    <key2>key2 of meter (the use defined name)</key2>
    <portion>multiplier, e.g. 1 or -1 or 0.3</portion>
  </meter>
  ... next meter ...
 </meters>
 <meterlen>The quantity of meters in this meter account</meterlen>
 <tariffs>
  <tariff>
    <eid>Entity id of tariff</eid>
    <key1>key1 of tariff (the id)</key1>
    <key2>key2 of tariff (the name)</key2>
    <tgidx>The tariff option number. Option 0 is the default tariff for this meter account, used for monthly bills. The others can be used for Provisional Bills, but not for Monthly Bills.</tgidx>
  </tariff>
  ... next tariff ...
 </tariffs>
 <tarifflen>The quantity of tariffs configured for this meter account</tarifflen>
 </xml>

<xml>
 <result>SUCCESS</result>
 <id>They key1 of the Ledger</id>
 <name>They key2 of the Ledger</name>
 <date_of_last_transaction>Date of last transaction</date_of_last_transaction>
 <balance>Current balance of the ledger multiplied by 100000.</balance>
</xml>

<xml>
 <result>SUCCESS</result>
 <id>The key1 of the tariff</id>
 <name>The key2 (name) of the tariff</name>
 <utility>The utility of the tariff, e.g. Electricity or Water</utility>
 <vfrom>Valid From date. If this is null, it has not been validated</vfrom>
 <vto>Valid To date. If this is null, it has not been validated</vto>
 <certifiedby>Indication of who validated this tariff</certifiedby>
 <certifiedon>When was it validated?</certifiedon>
 <taxtype>What is the name of the tax, e.g. VAT</taxtype>
 <taxperc>What is the percentage of the tax levied</taxperc>
 <currency>What is the currency symbol</currency>
 <currency_align>PRE or POST: is the currency symbol written before or after the amount</currency_align>
 <currency_decimals>is the amount of decimals in the currency, e.g. usually 100 for cents</currency_decimals>
 <calendars>
  <calendar>
   <eid>Entity id of a calendar that is referred to by the tariff. For these relationships to be set up correctly, the tariff should be validated first.</eid>
   <key1>key1 of calendar (id)</key1>
   <key2>key2 of calendar (name)</key2>
   <tourateperiods>
    <tourateperiod>
     <touid>Unique Time of Use ID for a specific tariff rate period in this calendar. This is unique over all calendars per server.</touid>
     <descr>Human readable description of the time of use tariff rate period</descr>
    </tourateperiod>
    ... next tourateperiod ...
   </tourateperiods>
   <tourateperiodlen>the amount of tourateperiods in this calendar</tourateperiodlen>
  </calendar>
  ... next calendar ...
 </calendars>
 <calendarlen>the amount of calendars in this tariff</calendarlen>
 <lineitems>
  <li>
   <tarifflineid>unique id for a specific line item on the tariff. This ties up with the field of the same name in getProvisionalBill.jsp</tarifflineid>
   <descr>The tariff line item description</descr>
   <type>Indication of the type of algorithm followed to calculate this line item</type>
   <compareId>Sometimes different tarifflineitems should be compared to each other for statistical comparisons accross seasons, e.g. between Peak (HS) and Peak (LS). Although their tarifflineid would be different, their compareId would be the same.</compareId>
   <color>This is an RGB value</color>
   <touid>If this is a Time Of Use tariff line item, the touid will be specified here. This can be cross referenced to touid in the calendars element.</touid>
  </li>
  ... next tariff line item (li) ...
 </lineitems>
 <lineitemlen>the amount of line items in this tariff</lineitemlen>
</xml>

<xml>
 <result>SUCCESS</result>
 <serialnumber>meter serial</serialnumber>
 <name>user defined meter name</name>
 <ctprim>CT primary value</ctprim>
 <ctsec>CT secondary value</ctsec>
 <vtprim>VT primary</vtprim>
 <vtsec>VT secondary</vtsec>
 <fullload>Breaker Size</fullload>
 <wires>Single Phase: 2 Wires, 3 Phase: Normally 4 Wires, sometimes 3 wires</wires>
 <place>Address 1 Freefrom</place>
 <site>Address 2 Freefrom</site>
 <zone>Address 3 Freefrom</zone>
 <primarymetering>If Y (default) we take the readings from the meter as is, if N, we apply CT and VT ratios by modifying UPP and PPU</primarymetering>
 <units_per_pulse>Number of kWh/kvarh/liters per pulse</units_per_pulse>
 <pulses_per_unit>Number of pulses per kWh/kvarh/liter</pulses_per_unit>
 <commissioned>Y/N is meter commisioned</commissioned>
 <disabled>Y/N is meter disabled</disabled>
 <password>The password for the meter, blank if the meter's default password is to be used</password>
 <comdate>Date the meter was installed/commissioned</comdate>
 <maxdate>The last profile data we have for the meter</maxdate>
 <maxdatenonzero>The last profile data we have for the meter that is not zero</maxdatenonzero>
 <maxdatenoninterp>The last profile data we have for the meter that was not interpolated. You can derive/inerpolate profile from totals, but it is not always useful profile.</maxdatenoninterp>
 <manualonly>Y/N is meter read manually only</manualonly>
 <utility>Electricity/Water</utility>
 <type>Type of meter</type>
</xml>

<xml>
 <result>SUCCESS</result>
 <id>They key1 of the Meter Account</id>
 <name>They key2 of the Meter Account</name>
 <utility>The utility of the Meter Account, e.g. Electricity or Water</utility>
 <meters>
  <meter>
    <eid>Entity id of meter in meter account</eid>
    <key1>key1 of meter (the serial number)</key1>
    <key2>key2 of meter (the use defined name)</key2>
    <portion>multiplier, e.g. 1 or -1 or 0.3</portion>
    <meteraccount>
      <eid>ID of Meter Account linked to meter</eid>
      <key1>Meter Account key</key1>
      <key2>Meter Account Name</key2>
      <accountnumber>Meter Account number</accountnumber>
    </meteraccount>
    ... next meter account ...
  </meter>
  ... next meter ...
 </meters>
 <meterlen>The quantity of meters in this meter account</meterlen>
 <tariffs>
  <tariff>
    <eid>Entity id of tariff</eid>
    <key1>key1 of tariff (the id)</key1>
    <key2>key2 of tariff (the name)</key2>
    <tgidx>The tariff option number. Option 0 is the default tariff for this meter account, used for monthly bills. The others can be used for Provisional Bills, but not for Monthly Bills.</tgidx>
  </tariff>
  ... next tariff ...
 </tariffs>
 <tarifflen>The quantity of tariffs configured for this meter account</tarifflen>
 </xml>

<xml>
 <result>SUCCESS</result>
 <entity>
 <id>They key1 of the Ledger</id>
 <name>They key2 of the Ledger</name>
 <date_of_last_transaction>Date of last transaction</date_of_last_transaction>
 <balance>Current balance of the ledger multiplied by 100000.</balance>
 </entity>
 ...next entity...
</xml>

<xml>
 <result>SUCCESS</result>
 <id>The key1 of the tariff</id>
 <name>The key2 (name) of the tariff</name>
 <utility>The utility of the tariff, e.g. Electricity or Water</utility>
 <vfrom>Valid From date. If this is null, it has not been validated</vfrom>
 <vto>Valid To date. If this is null, it has not been validated</vto>
 <certifiedby>Indication of who validated this tariff</certifiedby>
 <certifiedon>When was it validated?</certifiedon>
 <taxtype>What is the name of the tax, e.g. VAT</taxtype>
 <taxperc>What is the percentage of the tax levied</taxperc>
 <currency>What is the currency symbol</currency>
 <currency_align>PRE or POST: is the currency symbol written before or after the amount</currency_align>
 <currency_decimals>is the amount of decimals in the currency, e.g. usually 100 for cents</currency_decimals>
 <calendars>
  <calendar>
   <eid>Entity id of a calendar that is referred to by the tariff. For these relationships to be set up correctly, the tariff should be validated first.</eid>
   <key1>key1 of calendar (id)</key1>
   <key2>key2 of calendar (name)</key2>
   <tourateperiods>
    <tourateperiod>
     <touid>Unique Time of Use ID for a specific tariff rate period in this calendar. This is unique over all calendars per server.</touid>
     <descr>Human readable description of the time of use tariff rate period</descr>
    </tourateperiod>
    ... next tourateperiod ...
   </tourateperiods>
   <tourateperiodlen>the amount of tourateperiods in this calendar</tourateperiodlen>
  </calendar>
  ... next calendar ...
 </calendars>
 <calendarlen>the amount of calendars in this tariff</calendarlen>
 <lineitems>
  <li>
   <tarifflineid>unique id for a specific line item on the tariff. This ties up with the field of the same name in getProvisionalBill.jsp</tarifflineid>
   <descr>The tariff line item description</descr>
   <type>Indication of the type of algorithm followed to calculate this line item</type>
   <compareId>Sometimes different tarifflineitems should be compared to each other for statistical comparisons accross seasons, e.g. between Peak (HS) and Peak (LS). Although their tarifflineid would be different, their compareId would be the same.</compareId>
   <color>This is an RGB value</color>
   <touid>If this is a Time Of Use tariff line item, the touid will be specified here. This can be cross referenced to touid in the calendars element.</touid>
  </li>
  ... next tariff line item (li) ...
 </lineitems>
 <lineitemlen>the amount of line items in this tariff</lineitemlen>
 <periods>
  <period>
  <id>Period ID</id>
  <from>Period From Date</from>
  <to>Period End Date</to>
  </period>
 </periods>
 <rates>
  <rate>
  <tarifflineid>Tariff Line Item ID</tarifflineid>
  <periodid>Tariff Period ID</periodid>
  <value>Rate in rands (or percent for discount line items)</value>
  </rate>
 </rates>
</xml>

<xml>
 <result>SUCCESS</result>
 <serialnumber>meter serial</serialnumber>
 <name>user defined meter name</name>
 <ctprim>CT primary value</ctprim>
 <ctsec>CT secondary value</ctsec>
 <vtprim>VT primary</vtprim>
 <vtsec>VT secondary</vtsec>
 <fullload>Breaker Size</fullload>
 <wires>Single Phase: 2 Wires, 3 Phase: Normally 4 Wires, sometimes 3 wires</wires>
 <place>Address 1 Freefrom</place>
 <site>Address 2 Freefrom</site>
 <zone>Address 3 Freefrom</zone>
 <primarymetering>If Y (default) we take the readings from the meter as is, if N, we apply CT and VT ratios by modifying UPP and PPU</primarymetering>
 <units_per_pulse>Number of kWh/kvarh/liters per pulse</units_per_pulse>
 <pulses_per_unit>Number of pulses per kWh/kvarh/liter</pulses_per_unit>
 <commissioned>Y/N is meter commisioned</commissioned>
 <disabled>Y/N is meter disabled</disabled>
 <password>The password for the meter, blank if the meter's default password is to be used</password>
 <comdate>Date the meter was installed/commissioned</comdate>
 <maxdate>The last profile data we have for the meter</maxdate>
 <maxdatenonzero>The last profile data we have for the meter that is not zero</maxdatenonzero>
 <maxdatenoninterp>The last profile data we have for the meter that was not interpolated. You can derive/inerpolate profile from totals, but it is not always useful profile.</maxdatenoninterp>
 <manualonly>Y/N is meter read manually only</manualonly>
 <utility>Electricity/Water</utility>
 <type>Type of meter</type>
</xml>

<xml>
 <result>SUCCESS</result>
 <id>Same as the key1</id>
 <adminid>Id of role that administrates this organization</adminid>
 <organizationname>Name</organizationname>
 <postaladdrl1>Postal Address line 1</postaladdrl1>
 <postaladdrl2>Postal Address line 2</postaladdrl2>
 <city>CityPostal </city>
 <province>Postal Province</province>
 <postalcode>Postal Code</postalcode>
 <country>e.g. ZA</country>
 <telephonenumberdial>e.g. 27</telephonenumberdial>
 <telephonenumber>Telephone number</telephonenumber>
 <telephonenumberext>Extention</telephonenumberext>
 <faxnumberdial></faxnumberdial>
 <faxnumber>Fax number</faxnumber>
 <streetaddr>Physical Street Address</streetaddr>
 <vatnumber>VAT number</vatnumber>
 <subdomain>Subdomain that is pre-pended to .pnpscada.com e.g. sdg. (This is also used to determine the banner on the login page)</subdomain>
 <timezone>e.g. Africa/Johannesburg</timezone>
 <aid>-1</aid>
 <deleted>N if this Organization has been deleted</deleted>
 <hasbanner>N if this Organization has it's own banner</hasbanner>
 <loginnewpage>???</loginnewpage>
 <decimaldelimeter>e.g. .</decimaldelimeter>
 <thousandsdelimeter>e.g. [empty]</thousandsdelimeter>
 <unitsdelimeter>e.g. [empty]</unitsdelimeter>
 <domainserver>Main Server (if you have multiple servers)</domainserver>
 <bill_companyname/>Company to bill</bill_companyname>
 <bill_email/>billing email address</bill_email>
 <bill_email2/>second billing email</bill_email2>
 <adderorg>Id of org that added this organization</adderorg>
</xml>

<xml>
 <result>SUCCESS</result>
 <id>ID of this login</id>
 <firstname>First name</firstname>
 <lastname>Last name</lastname>
 <email>email address</email>
 <cellphone>Cellphone number</cellphone>
 <login>login name with subdomain. e.g. sdg.joe</login>
 <cellphonedial>e.g. 27</cellphonedial>
 <emailcontactme>Y if we can contact this person at this email address</emailcontactme>
 <verified>Y when the login has been verified (used mainly for first time top level organization registration)</verified>
 <deleted>Y if deleted</deleted>
 <inwiki>Not used anymore</inwiki>
 <j2meon>Not used anymore</j2meon>
 <pwddate>Date of last password change</pwddate>
 <oldmenu>Y if the old menu is used on this login</oldmenu>
</xml>

<xml>
 <result>SUCCESS</result>
 <id>Same as key1</id>
 <orgid>Key1 of organization</orgid>
 <rolename>Name of role</rolename>
 <addrestricted>Y if this role is restricted to which entities it may add</addrestricted>
 <interfrestricted>Y if this role is restricted to which screens it may access</interfrestricted>
 <entrestricted>Y if this role is restricted to which entities it may see in it's organization</entrestricted>
 <globl>e.g. Y</globl>
 <deleted>Y if deleted</deleted>
 <startpage>First screen after login, or null for overview screen</startpage>
 <pagrestricted>Y if restricted to which pages this role may access</pagrestricted>
 <smsdelay>e.g. 30</smsdelay>
 <emaildelay>e.g. 30</emaildelay>
 <smsdaystart>e.g. 7</smsdaystart>
 <emaildaystart>e.g. 0</emaildaystart>
 <smsdayend>e.g. 20</smsdayend>
 <emaildayend>e.g. 24</emaildayend>
 <smslimit>e.g. 10</smslimit>
 <emaillimit>e.g. 10</emaillimit>
 <smsatnight>Y if SMSes are to be sent at night</smsatnight>
 <emailatnight>Y if emails are to be sent at night</emailatnight>
 <custommenu>Customer Menu eid</custommenu>
 <smsparms>CommunitySMS login details or name of SMS connector</smsparms>
 <pwdregexp>Password expiry e.g. .*</pwdregexp>
 <pwddays>Password expiry e.g. 40000</pwddays>
 <pwdgracedays>Password expiry e.g. 0</pwdgracedays>
 <pwddescr>Password expiry e.g. Please specify a valid password</pwddescr>
 <lid>Ledger to charge for SMSes.</lid>
 <price>Price per SMS e.g. 0</price>
 <freesmspermonth>Number of free SMSs per month. e.g. 0</freesmspermonth>
</xml>

<xml>
 <result>SUCCESS</result>
 <roles>
  <role>
   <id>ID of Role</id>
   <descr>Descript of Role</descr>
   <tenant>Y if this role is under a tenant (as opposed to being a main incomer)</tenant>
  </role>
  ...more roles
 </roles>
 <meter_accounts>
  <meter_account>
   <id>entity id of meter account</id>
   <meter_account_id>id of meter account</meter_account_id>
   <multiplier>1</multiplier>
   <roleid>role of this account</roleid>
  </meter_account>
  ...more accounts
 </meter_accounts>
</xml>

<xml>
 <result>SUCCESS</result>
 <len>Number of entities returned</len>
 <entities>
 <entity>
 <id>eid of the meter</id>
 <cid>id of the meter's class</cid>
 <key1>The meter's serial</key1>
 </entity>
 more meters...
 </entities>
</xml>

<xml>
 <result>SUCCESS</result>
 <id>The key1 of the calendar (id)</id>
 <name>The key2 of the calendar</name>
 <certified>Has this calendar been certified, i.e. populated correctly in the database? Y/N</certified>
 <certifiedby>Indication of who certified it</certifiedby>
 <certifiedfrom>from when is the calendar valid</certifiedfrom>
 <certifiedto>until when is the calendar valid</certifiedto>
 <certifiedon>when was it certified?</certifiedon>
 <timezone>Time Zone of the calendar</timezone>
 <ignoredst>Should daylight savings time - if applicable to the time zone - be ignored?</ignoredst>
 <periods>
  <li>
   <ts>time stamp of period in calendar</ts>
   <touid>Time of Use unique id for that period</touid>
  </li>
  ... next period in time range (li) ...
 </periods>
 <periodlen>amount of periods in the calendar for the selected time range</periodlen>
</xml>

<xml>
  <result>SUCCESS</result>
  <date>the last profile date</date>
  <meters>
    <meter>
      <cid>Class ID</cid>
      <primary>if primary metering "Y", else "N"</primary>
      <serial>Meter's serial</serial>
      <key2>Meter's user defined name</key2>
      <key3>Meter's Key3 (which may be null)</key3>
      <Data>
        <TimeItem>
          <Time>hh:mm</Time>
          <Red>
            <I>current</I>
            <V>voltage</V>
            <Iangle>current angle</Iangle>
            <Vangle>voltage angle</Vangle>
            <S>Apparent Energy kVA</S>
            <P>Active Energy kW</P>
            <Q>Reactive Energy kvar</Q>
            <pf>Power Factor</pf>
            <lead_lag>leading or lagging</lead_lag>
          </Red>
          <White>
            <I>current</I>
            <V>voltage</V>
            <Iangle>current angle</Iangle>
            <Vangle>voltage angle</Vangle>
            <S>Apparent Energy kVA</S>
            <P>Active Energy kW</P>
            <Q>Reactive Energy kvar</Q>
            <pf>Power Factor</pf>
            <lead_lag>leading or lagging</lead_lag>
          </White>
          <Blue>
            <I>current</I>
            <V>voltage</V>
            <Iangle>current angle</Iangle>
            <Vangle>voltage angle</Vangle>
            <S>Apparent Energy kVA</S>
            <P>Active Energy kW</P>
            <Q>Reactive Energy kvar</Q>
            <pf>Power Factor</pf>
            <lead_lag>leading or lagging</lead_lag>
          </Blue>
          <Neutral>
            <I>Current</I>
            <Iangle>Current Angle</Iangle>
          </Neutral>
          <Total>
            <S>Apparent Energy kVA</S>
            <P>Active Energy kW</P>
            <Q>Reactive Energy kvar</Q>
            <pf>Power Factor</pf>
            <lead_lag>leading or lagging</lead_lag>
          </Total>
        </TimeItem>
        ...next time item...
      </Data>
    </meter>
    ...next meter...
  </meters>
<xml>

<xml>
  <result>SUCCESS</result>
  <meters_online>Number Of Meters Online since yesterday. Excluding Uncommissioned and manual meters.</meters_online>
  <meters_offline>Number Of Meters Offline</meters_offline>
</xml>

<xml>
  <result>SUCCESS</result>
</xml>

<xml>
  <result>SUCCESS</result>
  <meter>
    <serial>meter's serial e.g. ICP0000</serial>
    <id>meter's entity ID e.g. 4763</id>
    <vset>
      <id>instrumentation profile's ID e.g. 145</id>
      <cust_name>instrumentation profile's custom name in the context of this meter e.g. Heat</cust_name>
      <column>
        <id>first column in the instrumentation profile's ID e.g. 1203</id>
        <unit>unit of this column e.g. Celcius</unit>
        <description>standard description for this column e.g. Temperature Channel 0</description>
        <color>color on graph for this column in RRGGBB when converted to hex e.g. 16646144</color>
        <unitgraph>0=this value can not be graphed, 1=this value can be graphed</unitgraph>
        <custom_desc>custom description for this column in the context of this meter e.g. Cold</custom_desc>
      </column>
      more columns ...
    </vset>
    more vsets...
  </meter>
  more meters...
</xml>

<xml>
<result>SUCCESS</result>
<meter>
  <serial>meter's serial e.g. ICP0000</serial>
  <id>meter's entity ID e.g. 4763</id>
  <vset>
    <date>date and time of the reading e.g. 2012-08-14 00:05:00</date>
    <val>value of the reading e.g. 26.46</val>
    <id>vset column id (see vsetInfo.jsp) e.g. 1205</id>
  </vset>
  next columns and dates...
</meter>
</xml>

if quickbalance was specified:
<xml>
  <result>SUCCESS</result>
  <currentbalance>10000</currentbalance>
</xml>

normally:
  <xml>
  <result>SUCCESS</result>
  <eid>Entity ID of Ledger</eid>
  <key1>key1 of Ledger</key1>
  <key2>user defined name of Ledger</key2>
  <odate>Opening Date of Ledger</odate>
  <obal>Opening balance of Ledger</obal>
  <obalRAW>Opening balance of Ledger without formatting</obalRAW>
  <action>None</action>
  <cbal>Current Balance</cbal>
  <cbalRAW>Current Balance without formatting</cbalRAW>
  <hasprepaid>true if linked to a prepaid facility, false otherwise</hasprepaid>

when buying an STS token / garnish orders / debit orders:
<garnish>
	<gamtRAW>Garnish amount without formatting</gamtRAW>
	<gamt>Garnish amount</gamt>
</garnish>
<debit>
	<damtRAW>Debit amount without formatting</damtRAW>
	<damt>Debit amount</damt>
</debit>
<tokentrn>
  <tamtRAW>Token cost without formatting</tamtRAW>
  <tamt>Token cost</tamt>
  <token>20 digit token</token>
  <tdescr>transaction description</tdescr>
</tokentrn>

per prepaid facility:
  <prepaidfacility>
    <eid>Entity ID of n-th Prepaid Facility linked to ledger</eid>
    <key1>key1 of Prepaid Facility</key1>
    <key2>User defined name of Prepaid Facility</key2>
  </prepaidfacility>
  <breaker>
    <eid>Entity ID of Breaker linked to previous Prepaid Facility</eid>
    <key1>key1 of Breaker</key1>
    <key2>User defined name of Breaker</key2>
    <state>Current state, (Switched on/Switched off)</state>
    <date>Date of last state change</date>
  </breaker>
  <meteraccount>
    <eid>Entity ID of Meter Account linked to previous Prepaid Facility</eid>
    <key1>key1 of Meter Account</key1>
    <key2>User defined name of Meter Account</key2>
  </meteraccount>
  <tariff>
    <eid>Entity ID of default Tariff linked to previous Meter Account</eid>
    <key1>key1 of tariff</key1>
    <key2>User defined tariff name</key2>
  </tariff>
  ... (more [prepaid facility,breaker,meteraccount,tariff] - combos, if any)

  <hastrans>true if there are transactions returned in this request, false if there are no transactions returned in this request (dependant on start and end date)</hastrans>

if transactions available:
  <transactions>
    <partialtrans>true if transactions from the begging is returned, false if the first transaction in not returned</partialtrans>
    <startdate>Start date and time of transactions returned</startdate>
    <enddate>End date and time of transaction returned</enddate>
    <obal>Opening Balance at start date</obal>
    <obalRAW>Opening Balance without formatting</obalRAW>
    <cbal>Current balance as end date</cbal>
    <cbalRAW>Current balance without formatting</cbalRAW>
    <transactionlog>

per transaction:
      <transaction>
        <num>Sequence number of the transaction (starts from 0 per ledger)</num>
        <tdate>Date of transaction</tdate>
        <amt>Unformatted amount of transaction</amt>
        <descr>Description of transaction (text filled in by user or billing engine)</descr>
        <tpe>C=Credit Note ; D=Debit Note ; R=Receipt ; I=Invoice</tpe>
      </transaction>
      ... (more transactions if available)

    </transactionlog>
  </transactions>
</xml>

<xml>
 <result>SUCCESS</result>
 <id>eid of the meter account</id>
 <cnumber>Automatically assigned unique Meter Account ID</cnumber>
 <cname>Account Name</cname>
 <anumber>Account Number</anumber>
 <lnumbernme>Name for Lot Number (defaults to Lot Number)</lnumbernme>
 <lnumber>Lot Number</lnumber>
 <standnumbernme>Name for Stand Number (defaults to Stand Number)</standnumbernme>
 <standnumber>Stand Number</standnumber>
 <regionnme>Name for region (defaults to Region)</regionnme>
 <region>Region</region>
 <tariffs>
  <tariff>
  <eid>Entity ID of Tariff</eid>
  <option>0 for default tariff, used for billing, the others are used for recons and comparisons</option>
  <tariffcode>Tariff Code</tariffcode>
  <tariffname>Tariff Name</tariffname>
  </tariff>
  .. more tariffs
 </tariffs>
 <meters>
  <meter>
  <eid>Entity ID of Meter</eid>
  <serial>Meter's Serial</serial>
  <portion>Portion to which this meter contributes to this meter account's usage</portion>
  </meter>
  ...more meters
 </meters>
</xml>

<xml>
 <result>SUCCESS</result>
 <len>Number of entities returned</len>
 <meters>
 <meter>
 <meterresult>SUCCESS or ERROR: No New Readings</meterresult>
 (and if success:)
 <key1>The meter's serial</key1>
 <sets>
 <set>
 <period>energy minutes in one period</period>
 <readings>
 <reading><ts>YYYY-MM-DD HH:MM:SS (period end)</ts>
 <kWh>kWh used in this period</kWh>
 <kVAh>kVAh in this period</kVAh>
 <kvarh>kvarh in this period</kvarh>
 (not used yet:)<pf></pf><pf1></pf1><pf2></pf2><pf3></pf3><V1></V1><V2></V2><V3></V3>
 <V1deg></V1deg><V2deg></V2deg><V3deg></V3deg><I1></I1><I2></I2><I3></I3>
 <I1deg></I1deg><I2deg></I2deg><I3deg></I3deg><thd></thd>
 <P2>Reverse kWh in this period</P2>
 </reading>
 more readings...
 </readings>
 </set>
 </sets>
 </meter>
 more meters...
 </meters>
</xml>

<xml>
 <result>SUCCESS</result>
 <len>Number of entities returned</len>
 <entities>
 <entity>
 <id>eid of the meter</id>
 <cid>id of the meter's class</cid>
 <key1>The meter's serial</key1>
 </entity>
 more meters...
 </entities>
</xml>

<xml>
 <result>SUCCESS</result>
 <len>Number of entities returned</len>
 <entities>
 <entity>
 <id>eid of the meter</id>
 <cid>id of the meter's class</cid>
 <key1>The meter's serial</key1>
 </entity>
 more meters...
 </entities>
</xml>

<xml>
 <result>SUCCESS</result>
 <len>Number of entities returned</len>
 <entities>
 <entity>
 <id>eid of the meter</id>
 <cid>id of the meter's class</cid>
 <key1>The meter's serial</key1>
 </entity>
 more meters...
 </entities>
</xml>

<xml>
  <result>SUCCESS</result>
  <meter>
    <serial>Meter's Serial</serial>
    <name>Meter's Name</name>
    <events>
      <event>
        <result>SUCCESS</result>
        <class_id>Event Class ID</class_id>
        <event_id>Event Type ID</event_id>
        <phase>A/B/C or Space for all or n/a</phase>
        <start_date>Event Start Date</start_date>
        <end_date>Event End Date</end_date>
        <value>Additional values or comments logged with the event</value>
        <reservation>N for no reservation, Y if there was a reservation logged against this event</reservation>
        <validated>N if the event has still not been cleared for billing purposes, Y if the event has been cleared</validated>
        <fault_id>ID of fault reservation</fault_id>
        <read_at>Time this event was read from the meter</read_at>
      </event>
      ...next event
    </events>
  </meter>
</xml>

<xml>
  <result>SUCCESS</result>
  <types>
    <type>
      <id>Event Type ID</id>
      <class>Class ID</class>
      <desc>Description of event</desc>
      <short_desc>Short code for event</short_desc>
      <istimespan>Y for events that spans a time range, like power loss, N for events that are instantaneous like reprogram</istimespan>
      <isexternal>Y for events that do not come from the meter, like software or user logged events, N for events that come from the meter</isexternal>
      <invalidates>Y if it causes the meter's data to become invalid for billing purposes, N otherwise</invalidates>
    </type>
  </types>
  <classes>
    <class>
      <id>Class ID</id>
      <desc>Description of class</desc>
      <short_desc>Short code for class</short_desc>
    </class>
  </classes>
</xml>

<xml>
  <result>SUCCESS:success message</result>
  <retry>no</retry>
  <last_attempt>
    <date>Date of last token sent or none if there was no previous switch</date>
    <result>SUCCESS:success message or ERROR:error message</result>
    <retry>yes/no</retry>
  </last_attempt>
</xml>

<xml>
  <result>ERROR:error message</result>
  <retry>yes/no</retry>
  <last_attempt>
    <date>Date of last token sent or none if there was no previous switch</date>
    <result>SUCCESS:success message or ERROR:error message</result>
    <retry>yes/no</retry>
  </last_attempt>
</xml>

<xml>
  <result>SUCCESS</result>
    <action>on/off</action>
    <last_state>
      <date>Date of last switch or none if there was no previous switch</date>
    <state>Switched on/off or none if there was no previous switch</state>
  </last_state>
</xml>

<xml>
  <result>SUCCESS</result>
  <meter_account>
    <id>ID of meter account</id>
    <tariff>
    <id>ID of tariff</id>
      <calendar_id>ID of Calendar (if any)</calendar_id>
    </tariff>
    more tariffs...
    <meter>
      <id>ID of meter</id>
      <comms_dev>
        <id>ID of Communication Device</id>
        <sim_id>ID of SIM card (if any)</sim_id>
      </comms_dev>
      <breaker_id>ID of breaker</breaker_id>
      more breakers...
    </meter>
    more meters...
    <prepaid_facility>
      <id>ID of Prepaid Facility</id>
      <ledger_id>ID of Ledger</ledger_id>
      <breaker_id>ID of Breaker (could be connected to a different breaker than what is on the meter)</breaker_id>
    </prepaid_facility>
    more prepaid facilities...
  </meter_account>
  ... more meter accounts if specified
</xml>

<xml>
<meter>
  <serial>Meter's serial</serial>
  <profile>
    <sample>
      <date>End Date of this sample in the format: yyyy-MM-dd HH:mm. Profiles MUST be given in ascending order. Profile dated before last reading will be discarded</date>
      <P1>Active import (kWh). Does not count up. With secondary metering this is the value after the multiplier</P1>
      <P2>Active export (kWh). With secondary metering this is the value after the multiplier</P2>
      <Q1>Reactive energy register quadrant 1 (kvarh). Does not reclock.</Q1>
      <Q2>Reactive energy register quadrant 2 (kvarh)</Q2>
      <Q3>Reactive energy register quadrant 3 (kvarh)</Q3>
      <Q4>Reactive energy register quadrant 4 (kvarh)</Q4>
      <STATUS>See note 4</STATUS>
    </sample>
    more samples...
  </profile>
</meter>
more meters...
</xml>
  

<xml>
  <meter>
    <serial>Meter Serial</serial>
    <last_imported_date>Last imported date</last_imported_date>
    <max_date>Date meter is up to date to</max_date>
   [if there were errors:
    <errors>
      <error>Error 1</error>
      more errors...
    </errors>]
  </meter>
</xml>

<xml>
<meter>
  <serial>Meter's serial</serial>
  <total>
    <sample>
      <date>End Date of this sample in the format: yyyy-MM-dd HH:mm. Totals MUST be given in ascending order. Totals dated before last reading will be discarded</date>
      <E1>Active import (kWh). Does not count up. With secondary metering this is the value before the multiplier</E1>
      <E2>Reactive energy register quadrant 1 (kvarh). Does not count up.</E2>
      <F1>Active export (kWh). With secondary metering this is the value before the multiplier</F1>
      <F2>Reactive energy register quadrant 2 (kvarh)</F2>
      <F3>Reactive energy register quadrant 3 (kvarh)</F3>
      <F4>Reactive energy register quadrant 4 (kvarh)</F4>
      <STATUS>See note 4</STATUS>
    </sample>
    more samples...
  </total>
</meter>
more meters...
</xml>
  

<xml>
  <meter>
    <serial>Meter Serial</serial>
    <last_imported_date>Last imported date</last_imported_date>
    <max_date>Date meter is up to date to</max_date>
   [if there were errors:
    <errors>
      <error>Error 1</error>
      more errors...
    </errors>]
  </meter>
</xml>

<xml>
<meter>
  <serial>Meter's serial</serial>
  <events>
    <sample>
      <eventid>The id of the event. see: http://sdg.pnpscada.com/eventTypes.jsp</eventid>
      <startdate>Start date of event (optional if end date is specified and a previous "unclosed" event exists)</startdate>
      <enddate>End date of event (optional if start date is specified)</enddate>
      <value>Optional: Additional Text Information</value>
      <phase>Optional: Phase of the event: A, B or C</phase>
      <file name="file.jpg">Optional: file attachment in base64. If you want to attach an image to a meter reading, use eventid 685 (Manual Meter Read) and the start date and time must be exactly the same as the total</file>
    </sample>
    more samples...
  </events>
</meter>
more meters...
</xml>
  

<xml>
  <meter>
    <serial>Meter Serial</serial>
   [if there were errors:
    <errors>
      <error>Error 1</error>
      more errors...
    </errors>]
  </meter>
  <events_processed>Number of events processed<events_processed>
</xml>

curl --data "LOGIN=subdomain.testme&PWD=testme&xml=<xml><meter><serial>01234568</serial><events><sample><eventid>685</eventid><startdate>2018-02-14 13:00</startdate><file name=\"test.gif\">
R0lGODlhMgAyAPf/AACEvQCExghKcwhKewhShAhjnAiEvRA5UhBKcxBKexBScxBSexBShBBahBBajBBalBBjlBBjnBBrpRBzrRB7rRB7tRB7vRCEvRgxQhg5Shg5WhhCWhhKYxhKaxhKcxhScxhSexhahBhajBhjjBhjlBhrlBhrnBhrpRhzpRhzrRh
7rRh7tRiEtRiEvRiMvRiUvSExQiE5QiE5SiFCQiFCSiFCUiFSayFScyFSeyFaeyFahCFjjCFjlCFrjCFrlCFrnCFznCFzpSFzrSF7pSF7rSF7tSGErSGEtSGEvSGMtSGMvSGUvSlCSilCUilKWilSYylSaylaaylacylaeyljeyljhCljjClrjClrlC
lzlClznClzpSl7pSl7rSmErSmEtSmMtSmMvSmUvSmUximcxjFSWjFSYzFSazFaazFjezFjhDFrhDFrjDFzjDFzlDFznDF7nDF7pTGEpTGErTGEtTGMrTGMtTGUtTGUvTGcvTlaYzlaazljczljezlrhDlrjDlzjDlzlDl7lDl7nDl7pTmEpTmErTmMr
TmMtTmUtTmUvTmcvUJjc0Jre0JzhEJzjEJ7lEJ7nEKEnEKEpUKErUKMpUKMrUKMtUKUrUKUtUKctUKcvUKlxkKlzkKtzkpzhEp7hEp7jEp7lEqElEqEnEqMpUqMrUqUrUqUtUqctUqlvUqlxlKElFKEnFKMnFKMpVKUpVKUrVKcrVKctVKlvVKlxlK1
1lqMnFqMpVqUpVqUrVqcrVqctVqltVqlvVqtxlq91mOUpWOUrWOcpWOcrWOctWOltWOlvWOtxmO1zmO11mO91mO93mucpWucrWuctWultWulvWutxmu1xmu1znOlrXOltXOttXOtvXOtxnO1xnO1znuttXutvXu1xnvG3oStvYTG1oTG3oTO3oTO54y
9zozG1ozG3ozO3ozO55S9xpS9zpTO3pzG1pzO3pzW55ze76XGzqXO1qXW3qXe563O1q3O3q3W3q3W57XW1rXW57Xe573W3r3e58be55CYqCH5BAkKAP8ALAAAAAAyADIAQAj+AP8JHEiwoMGDCBMqXMjQYD113ZwJyxXKTIyGDc1Nm5XpUCA2g0z5On
aMlyxTkdBgwDiQmScxLlgoOZKEJpgvN8HM8aJFCxYrVaywceMm0CBClk5FUsMSIwIHJlIUOQImTBgwdrDa2Yqo66FMHd1AaUr24AcQO7R02bpJVS1EhazYKEu3rl268ZrdXVguW69YpPw0emVMlyiLdtElW4Vn69Y6Xi0h+mopEyZTp05N8vPkLgIGE
E4QOUKa9BecWLVuPZSIdeVMqCwNkrJ3IQgQIUwI8QJGNddEmhIZujK3tt0POq5sifMmh/Hn0DE+tHaLEZPoCdV5K+xK1CtXjZj+oMEu0Jw0Wagm/fEDiNSxctFe9Wni5Lm4ZKoUIUo02ZIlTJdchklmsUACRX11obNMJ2IkkURvvWXlGGSTTXaJf5T4
N4kaY5HFwAMRqMBCC0eYQIIII5BQwg9BbMFFF3PMYQeFXl2CSmyDpFFbAg2QgMJUSoAhRoRa1WEHa4dMBlYmlghCW3QNeJBbEEfg5JgdiNxx5H5gGSIWeQWBsMAIP3TxxVZ4JKKIKpsId0UHYCrkAQhYbOGFjIjEUcUNcWKkwwc53ABnn4QWaihBDwW
zx0WHDvRQRLl84kQTjd4DDjfF6JJLLq3wwWih62hjDGCPiAJLLo84cV2f5vh1Cin+6z0yCzi8kMKHDHGa5wsqlQTiRyCl8OINfLCkSgN25lCTSiZwvYHUgJdlZkopacjQh33JaKIIV5Dxl0hl/yVlCUpP3jWOMpzgAaFqrO33FWWYYJKUKYGMRxcwDM
6kxBdJoObbZHYYUggcbrDBxhptTGIJIFGQJcEEKYwoE4lIHEHEDz/soLEPWPjQUxxxyGHIIYdUJi8gHTa1AGgniJiCCTAHQUQXXqDmWIWufZUKr2ykXNZnoa1AkxJJhPGglVdiOVkimWiCySQ91/aZj6NVBaGEjy39FViFcPhcCAiIUEIQRfSmLtZGt
tv0JV2X+1wDCYygG05hNHZlkkwfMkhJFX2C8AGZZmJ1B393LInIIFMYOucIQJi5VSKb1KLJIW8k3uicPagFWZuUu90ooD68MUcdh2TBZ6MGIXcFFjoUh7pBOXDwOkYBAQA7</file></sample></events></meter></xml>" http://adam.pnpscada.com:8080/putEvent.jsp

<xml>
<meter>
  <serial>Meter's serial</serial>
  <instprof>
    <set>                           (instumentation profile sets are identified by the channels)
      <period>The period of the set in milliseconds. e.g. 1800000 for half hour. Use 0 for irregular intervals</period>
      <billing>Y if these values are used for billing (such as TOU off-peak register), N otherwise</billing>
      <channel>
        <name>name of this channel e.g. Voltage A</name>
        <phase>A,B,C or a space for all or not applicable</phase>
        <unit>unit of measurement e.g. kW,kvarh,kVA,m3,m³,DegC or °C</unit>
      </channel>
      more channels...
    </set>
    <sample>
      <date>Date of this sample in the format: yyyy-MM-dd HH:mm:ss.SSS e.g. 2019-02-22 10:57:43.000 Profile must be given in ascending order.</date>
      <channel>Channel value, numeric value. e.g. 23.01 If a channel does not have a value for this time, please leave empty</channel>
      more channels...              (channels must be given in the same order as in the set.)
    </sample>
    more samples...
  </instprof>
</meter>
more meters...
</xml>

curl --data "LOGIN=subdomain.testme&PWD=testme&xml=<xml>
<meter>
  <serial>91129004</serial>
  <instprof>
    <set>
      <period>0</period>
      <billing>N</billing>
      <channel>
        <name>Temp1</name>
        <phase> </phase>
        <unit>DegC</unit>
      </channel>
      <channel>
        <name>Temp2</name>
        <phase> </phase>
        <unit>DegC</unit>
      </channel>
    </set>
  </instprof>
  <sample><date>2019-02-22 11:41:10.000</date><value>40.0</value><value>25.1</value></sample>
  <sample><date>2019-02-22 12:41:10.000</date><value>41.0</value><value>27.1</value></sample>
</meter></xml>" http://adam.pnpscada.com:8080/putInstrProfile.jsp

<csv>
</csv>

<csv>
</csv>

<xml>
<communication>
<sim>SIM number</sim>
<modem_connected>modem connected date and time. e.g. 2017-02-03 08:32:09.554</modem_connected>
<last_read_attempt>last read attempt. e.g.2017-02-03 03:29:14.712</last_read_attempt>
<last_read_success>last successful read. e.g.2017-02-03 03:29:14.712</last_read_success>
</communication>
</xml>

<xml>
<result>ERROR:reason</result>
</xml>
  

<xml>
<billrun>
<brid>Bill Run ID of first bill</brid>
<start>Bill Run Start Date of first bill</start>
<end>Bill Run End Date of first bill</end>
</billrun>
...more bill runs...
<result>SUCCESS</result>
</xml>

<xml>
<result>ERROR:reason</result>
</xml>
  

<xml>
  <meter>Serial</meter>
  each value in it's own tag, meter dependant:
  <E1 - Accumulative Forward Active kWh
      F1 - Accumulative Forward Reactive kvarh
      E2 - Accumulative Reverse Active kWh
      F2 - Accumulative Reverse Capacitive kvarh
      F3 - Accumulative Reverse Inductive kvarh
      F4 - Accumulative Forward Inductive kvarh
      V1 - Volts Phase 1
      V2 - Volts Phase 2
      V3 - Volts Phase 3
      I1 - Currents Phase 1
      I2 -
      I3 -
      V1A -
      V2A -
      V3A -
      I1A -
      I2A -
      I3A -
      >
    <val>e.g. 114574.26369</val>
    <ts>e.g. 2011-04-14 17:11:01.036</ts>
  </E1>
  ... more values
</xml>

<xml>
<tou>
<start>Start time the TOU ID becomes applicable</start>
<end>End time the TOU ID stops being applicable after the assiciated start time</end>
</tou>
...more TOU entries...
<result>SUCCESS</result>
</xml>

<xml>
<result>ERROR:reason</result>
</xml>
  

<xml>
  <result>SUCCESS</result>
  <attempts>
    <attempt>
      <meter>Meter's serial</meter>
      <action>Action, e.g. token number</action>
      <whoid>Individual ID of person or negative eid of entity responsible</whoid>
      <datetime>Date and Time of attempted action</datetime>
      <success>Only appears if success.</success>
      <error>Only appears if error, and describe the error</error>
    </attempt>
    ...next attempt...
  </attempts>
</xml>

<xml>
  <server>
    <name>Server's unique name</name>
    <id>Server's unique PNPSCADA server id</id>
    <mac>server's MAC address</mac>
  </server>
<xml>

Start [start time] to [end time]
Start [comparable start] to [comparable end]
And the following columns:
-Code
-Name
-Total kWh Used
-Afterhours kWh Used
-% of Usage After Hours
-Total kWh Used
-Afterhours kWh Used
-% of Usage After Hours
-Total Usage Changed %
-Afterhours Usage Changed %
  

Has the following columns for each line:
name
Date of group 1 + P1 (if on)
Date of group 1 + P2 (if on)
Date of group 1 + Q1 (if on)
Date of group 1 + Q2 (if on)
Date of group 1 + Q3 (if on)
Date of group 1 + Q4 (if on)
Date of group 1 + S  (if on)
Date of group 1 + S time (if on)
...
Date of group n + P1 (if on)
Date of group n + P2 (if on)
Date of group n + Q1 (if on)
Date of group n + Q2 (if on)
Date of group n + Q3 (if on)
Date of group n + Q4 (if on)
Date of group n + S  (if on)
Date of group n + S time (if on)

If Comparable is switched on, contains another row, with Comparable in the name, and the same columns
If After Hours is switched on, contains another row, with After Hours in the name, and the same columns
  

Has the following columns for each line:
name
date
type
value

the previous table is written out in one column with many rows
  

<xml>
  <result>SUCCESS</result>
  <meters>
    <meter>
      <snumber>Meter's serial</snumber>
      <date>Date and Time of reading</date>
      <E1>Reading in system units</rssi>
    </meter>
    ...next meter...
  </meters>
</xml>

<xml>
  <result>SUCCESS</result>
  <meters>
    <meter>
      <snumber>Meter's serial</snumber>
      <err>meter specific Error code. Zero is success. -1 is meter not called in up to date. -2 is meter installed after date. -3 is Discrepancy. </err>
      <E1>Reading in system units</rssi>
    </meter>
    ...next meter...
  </meters>
</xml>

<xml>
  <result>SUCCESS</result>
  <recs>
    <rec>
      <meter>Meter's serial</meter>
      <conc>Concentrator serial</conc>
      <ts>Timestamp of signal sample</ts>
      <rssi>RSSI</rssi>
      <signal>Signal.</signal>
      <fail>Y/N usually N, except in case of some catastrophic failure</fail>
    </rec>
    ...next rec...
  </recs>
</xml>

<xml>
  <result>SUCCESS</result>
  <recs>
    <rec>
      <meter>Meter's serial</meter>
      <ts>Timestamp of latest packet for this meter</ts>
      <concentrators>[number of concentrators in which the meter was found]</concentrators>
      <count>[number of records for this meter]</count>
    </rec>
    ...next rec...
  </recs>
</xml>

<xml>
  <result>SUCCESS</result>
  <recs>
    <rec>
      <conc>Concentrator serial</conc>
      <ts>Timestamp of latest packet for this concentrator</ts>
      <meters>[number of meters found by this concentrator in the packets]</concentrators>
      <count>[number of records for this concentrator]</count>
    </rec>
    ...next rec...
  </recs>
</xml>

<xml>
  <result>SUCCESS</result>
  <eid>Entity's id </eid>
  <loci>
    <location>
      <ldate>Date of location setting</ldate>
      <lat>Latitude in degrees as a floating point value </lat>
      <lng>Longitude in degrees as a floating point value </lng>
      <hasl>Height above sea level in meters </hasl>
      <proximity>Proximity / Size / Accuracy of object location in meters (radius) </proximity>
      <user_id> Entity ID of user login who set it </user_id>
    </location>
    ...next location...
  </loci>
</xml>

<xml>
 <result>SUCCESS</result>
 <method>[coctinst/utilitiesdeviceid/serialid/materialid/parentinstpointid/liskey]</method>
 <value>[value specified for above method]</value>
 <meters>
      <snumber>[meter serial]</snumber>
     ...next meter...
 </meters>
 </xml>

<xml>
 <push>
      <pid>[push entity id]</pid>
      <meter>[meter serial number]</meter>
      <mask>[set mask pushed, e.g. 4 for events]</mask>
      <upto>[date and time up to which the last push was]</upto>
      <status>[for events this would be 1 for start and 0 for end of event]</status>
      <status_date_time>[date and time of last happening]</status_date_time>
 </push>
 ...next push record...
 <result>SUCCESS</result>
 </xml>