4 new data models for WasteWater

4 new data models for datamodel.wasteWater Subject

  • Blower. This entity contains a harmonized description of a Blower made for the Wastewater treatment domain. The entity represents a Blower that is used for aeration purposes in the wastewater treatment process. Important parameters are measured to regulate and measure the amount of airflow is being provided to the aeration tank in the bioreactor. The energy consumption of a blower is also important information for real-time control and optimization of the wastewater treatment plant.
  • OffGasStack. This entity contains a harmonized description of a generic Off-gas Stack made for the Wastewater treatment domain. This entity represents stacks that are present in some wastewater treatment plants where the emissions, greenhouse gases included, are emitted.
  • WasteWaterJunction. This entity contains a harmonized description of a generic Junction made for the Wastewater treatment domain. Junctions could be in place in certain sections of the treatment plant. For wastewater treatment purposes, the junction is most useful if it is a location of a sensor that measures a specific variable.
  • WasteWaterTank. This entity contains a harmonized description of a generic Tank made for the Wastewater treatment domain. For a given type of tank, all possible variables that can be measured are listed as properties. In the description property, the type of tank (anaerobic, pre-dinitrification, nitrification, etc.)can be defined.

Don’t to these section in the contribution manual

In order to reduce the work for the contributors of the new data models, there is a new section on the contribution manual title ‘don’t do these’ with recommendations for the most common poor practices in the contribution process.

Although all contributions are welcomed it will save everybody’s time by reading this section once.

Additionally, the section can be improved so you can submit your recommendations/lessons learned here.

Updated all the data models (11) in subject WaterDistributionManagement EPANET

The data models of the subject WaterDistributionManagement EPANET have been updated with flow properties and other improvements. New properties are already available for search in the database.

Additionally, there is an alpha version of the German translation of the specification.

  • Curve. This entity contains a harmonized description of a generic curve made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Junction. This entity contains a harmonized description of a generic junction made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • Network. This entity contains a harmonized description of a generic network made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • Pattern. This entity contains a harmonized description of a generic pattern made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Pipe. This entity contains a harmonized description of a generic pipe made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Pump. This entity contains a harmonized description of a generic pump made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Reservoir. This entity contains a harmonized description of a generic Reservoir made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • SimulationResult. This entity contains a harmonized description of a generic simulation result made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • SimulationScenario. This entity contains a harmonized description of a generic simulation scenario made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • Tank. This entity contains a harmonized description of a generic tank made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Valve. This entity contains a harmonized description of a generic Valve made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.

You can answer our survey in order to know what more useful for you.

    Q1: What elements of a smart data model are useful for you?

    Examples of the options:
    1.-Json Schema
    2.-Examples
    3.-Specification
    Mark those relevant for you


    Optional. Other element useful. (Available or desired)

    Q2: What services do you use?

    1.- Search data models
    2.- Validation of payload
    3.-Validate schema before contribution
    4.-Generate a NGSI-LD payload out of a schema
    Search data modelsValidation of payloadValidate of json schema before contributionGenerate a NGSI-LD payload out of a schema
    Optional. Other service missing. (Available or desired)

    Membership

    Member of FIWARE FoundationMember of TMForumMember of IUDXNo membership

    New data model StorageBatteryMeasurement in dataModel.Battery subject

    1 new data model in the subject datamodel.Battery

    StorageBatteryMeasurement. Storage Battery Observed Data Model is intended to measure the remaining energy capacity in a battery, which can be redistributed in the form of electrical energy. These functions apply from a source that depends on the type of battery (a reference to the attribute ‘batteryType’ of the Data Model StorageBatteryDevice).

    Thanks to the contributors

    Contribution checklist

    There is a new option in the main menu Data Models -> Contribution Checklist

    It is strongly recommended to pass every element before submitting your new data model.

    See below the checklist

      schema.json

      1.-
      2.-

      3.-

      4.-

      Examples

      5.-
      6.-

      Optional documents

      7.-
      8.-
      9.-
      10.-

      Contribution

      11.-

      Comments






      By using this form you agree with the storage and handling of your data by this website.

      New data model in Energy subject InverterDevice

      1 new data model is available in the subject dataModel.Energy.

      InverterDevice. The data model is intended to describe the mechanical, electrical characteristics of an Inverter according to DC – Direct Current Information supplied as input and AC – Alternating Current Information returned as output. Remark: This Data Model can be used directly as the main entity to describe the device [Inverter] or as a sub-entity of the Data Model {DEVICE] using a reference by the [refDevice] attribute.

      Thanks to the contributors of the subject.

      New NGSI linked data generator for every data model

      Now the README file of every data model includes a link to the generator of NGSI-LD payloads compliant with the data model.

      As you can see in the image below there is a new section “Dynamic examples generation

      There the sentence “Link to the Generator of NGSI-LD payloads compliant with this data model. Refresh for new values”. By clicking the Generator link an example of payload appears on the web page. Refreshing (F5) generates new payloads.

       

      Updated interactive specification

      Now all data models have an interactive specification. (As long as they have examples)
      This is the first step to deeper interactive services for every data model contributed.
      See the example for weatherForecast.

      First Survey to users and contributors of Smart Data Models

        Q1: What elements of a smart data model are useful for you?

        Examples of the options:
        1.-Json Schema
        2.-Examples
        3.-Specification
        Mark those relevant for you


        Optional. Other element useful. (Available or desired)

        Q2: What services do you use?

        1.- Search data models
        2.- Validation of payload
        3.-Validate schema before contribution
        4.-Generate a NGSI-LD payload out of a schema
        Search data modelsValidation of payloadValidate of json schema before contributionGenerate a NGSI-LD payload out of a schema
        Optional. Other service missing. (Available or desired)

        Membership

        Member of FIWARE FoundationMember of TMForumMember of IUDXNo membership