OMS ontology

URL

https://sites.google.com/site/smartappliancesproject/ontologies/oms.ttl

Description

The Oms ontology is a taxonomy of the devices supported by the Open Metering System (OMS) specification. The Device class represents these devices. Each device has a corresponding code (hasCode property). There are two type of devices: the devices that are actually supported (SupportedDevice class) and the devices that are not certifiable (NotCertifiableDevice class). The OMS specification covers the devices under the SupportedDevice class, which are further classified in OMSMeter and OMSDevice. The OMSMeter class covers the meter type of devices, such as ElectricityMeter, GasMeter, HeatMeter and WaterMeter, among others. The OMSDevice class covers other types of devices, such as Breaker, BidirectionalRepeater and CommunicationController, among others. The devices under the NotCertifiableDevice class may also be integrated in the Open Metering System. However these devices cannot be approved by the OMS-Compliance Test. Therefore the interoperability for the devices under the NotCertifiableDevice class cannot be guaranteed.

The Oms ontology also provides a taxonomy of the DataPoints according to the OMS-Data Point List (OMS-DPL), such as, for example, the current in Ampere (CA class), the energy in Joule or Watt hour (EJ and EW classes, respectively), the temperature in °C (TC class), the volume in cubic meters (VM class) and the voltage in Volt (VV class).

Observations

• The Oms ontology focuses on the type of metering devices and does not consider the architecture of the Open Meter System, such as the Multi Utility Communication Controller (MUC), which is the hardware system is used to readout different metering devices and to transfer subsets of this data to AMM back office systems for billing, servicing or other purposes.
• The DataPoint classes are “open” classes, i.e., these classes are defined in the ontology, but they may be further detailed. As future work, the ontology can be extended to take into account the separation of OMS-Datapoints in M-Bus tags and VIB-type lists.