SEEMPubs ontology

URL

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

Description

The Seempubs ontology describes the sensors and data that have been used in the use cases of the SEEMPubS project to control the building services, and monitor the indoor conditions and energy consumptions in some rooms of the Politecnico di Torino Campus and the Valentino Castle in Italy. The Sensor class represents the different type of sensors that have been used, namely Controller, IndoorTemperatureHumiditySensor, IndoorTemperatureSensor, LightSensor, OccupancySensor, OutdoorTemperatureSensor, PowerMeter4Lightingsystem, PowerMeter4Appliance, SuppliedAirTemperatureSensor, Switch and Thermostat. The data recorded in the use cases can be classified as related to indoor comfort conditions, related to energy consumption (electrical or thermal consumption), and related to the use of spaces and building services. Therefore, each sensor belongs to one of the categories: ComfortCondition, EnergyConsumption or UseOfSpaceAndBuildingService. Moreover, a sensor has a certain position in the room (hasPosition property) in which a number of sensors is positioned (hasSensorNumber property), is associated to a certain protocol, such as, for example, “EnOcean” or “BACnet” (hasProtocol property), and requires a certain communication time to transmits its data (hasCommunicationTime property).

Each sensor measures some quantity (MeasuredQuantity class). For example the IndoorTemperatureSensor measures Temperature , the OccupancySensor measures Presence or Absence, and the Controller measures FanCoilStatus1, FanCoilStatus2, or FanCoilStatus3. The MeasuredQuantity class can have a unit (UnitOfMeasure class), a mode (OperationMode class) and a status (Status class). For example, Temperature has unit CelsiusDegree, Presence has mode Present, and FanCoilStatus1 has status FanVelocity1. Each sensor processes data in certain terms, such as, for example, average values or individual single data, which are enumerated in the DataProcessingclass. Each sensor also represents data in a certain manner, for example, daily, monthly, according to an annual trend or a cumulative frequency, as enumerated in the DataRepresentation class.

The LightSensor class provides an example of how all the classes and properties mentioned above can be instantiated for a specific sensor.

Observations

• Only the LightSensor class is fully detailed with the values provided in the source of the ontology ('Deliverable D5.1, Data Format Definition'). The other type of sensors need to be detailed analogously (i.e., Controller, IndoorTemperatureHumiditySensor, IndoorTemperatureSensor, OccupancySensor, OutdoorTemperatureSensor, PowerMeter4Lightingsystem, PowerMeter4Appliance, SuppliedAirTemperatureSensor, Switch and Thermostat).