<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="14065" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/14065?output=omeka-xml" accessDate="2026-04-29T10:32:21+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93780">
              <text>Development of smart energy monitoring using NB-IOT and cloud</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93781">
              <text>Cloud; NB-IOT; Network; Smart energy; Smart power monitoring system</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93782">
              <text>IoT-based applications are growing in popularity nowadays because they offer effective answers to numerous current problems. In this research, With the aim of decreasing human efforts for monitoring the power units and increasing users' knowledge of excessive electricity usage, an IoT-based electric metre surveillance system utilising an Android platform has been developed. With the help of an Arduino Uno and an optical sensor, the electric analyser pulse is captured. To reduce human mistake and the expense of energy usage, a low-cost wireless network of sensors for digital energy metres is implemented alongside a smartphone application that can autonomously read the metre of the unit. In this research, an intelligent power monitoring system with effective communication modules has been developed to make wise use of the electricity. The controller, NB-IoT connection module, and cloud are the three main components of an IOT-based smart energy metre system. The controller is essential for maintaining the functionality of each component. This solution reduces the need for human involvement in electricity maintenance by connecting energy metres to the cloud using an NB-IoT communication module. The IoT-based metre reading system in the proposed work is created to monitor and analyse the metre reading, and the service provider can cut off the source of electricity whenever the customer fails to pay the monthly bill. It also eliminates the need for human intervention, provides accurate metre reading, and guards against billing errors. The proposed SPM improves the overall accuracy ranges of 7.42, 27.83, and 20% better than DR, OREM, and SLN respectively.  2023</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93783">
              <text>Siva Balan R.V.; Gouri M.S.; Senthilnathan T.; Gondkar S.R.; Gondar R.R.; Loveline Zeema J.; Jothikumar R.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="93784">
              <text>Measurement: Sensors, Vol-29</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="93785">
              <text>Elsevier Ltd</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93786">
              <text>2023-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="93787">
              <text>&lt;a href="https://doi.org/10.1016/j.measen.2023.100884" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1016/j.measen.2023.100884&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85170416869&amp;amp;doi=10.1016%2Fj.measen.2023.100884&amp;amp;partnerID=40&amp;amp;md5=58379b44390ae5a8b9eb6f379ecbbf29" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85170416869&amp;amp;doi=10.1016%2fj.measen.2023.100884&amp;amp;partnerID=40&amp;amp;md5=58379b44390ae5a8b9eb6f379ecbbf29&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93788">
              <text>All Open Access; Gold Open Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="93789">
              <text>ISSN: 26659174</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93790">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93791">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93792">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="93793">
              <text>Siva Balan R.V., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India; Gouri M.S., Department of Computer Science and Engineering, Baselios Mathews II College of Engineering Lake View, Muthupilakadu, Sasthamcotta, Kerala, Kollam, 690 520, India; Senthilnathan T., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India; Gondkar S.R., Department of Electronics and Communication and Engineering, BMS Institute of Technology and Management, Bengaluru, 560064, India; Gondar R.R., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India; Loveline Zeema J., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India; Jothikumar R., Department of Computer Science and Engineering, Shadan College of Engineering and Technology, Peeran Cheru, Hyderabad, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
