Author: maestro

No comments

New data models on Energy

  By ,

There are two data models coming for the Energy domain (ACMeasurement and InverterDevice). You can submit an issue on it if interested.

Once harmonized with the contributors and checking the interaction with other data models they will be incorporated into the Energy repository inside the domain of Smart Energy.

ACMeasurement

The Data Model intended to measure the electrical energies consumed by an electrical system which uses an Alternating Current (AC) for a three-phase (L1, L2, L3) or single-phase (L) and neutral (N). It integrates the initial version of the data Modem [THREEPHASEMEASUREMENT], extended to also perform single-phase measurements. it includes attributes for various electrical measurements such as power, frequency, current and voltage.

Additional Information about Attributes : For some attributes such as current and voltage the value is a structured value with properties for the Single-Phase (L) or three different phases (L1, L2 and L3). For some measurements such as the different power types (active, reactive and apparent power) there is an attribute for the total from all phases. The rules are defined as below : – Three Phase – Total = L1 + L2 + L3 – Single Phase – Total = L.

For most of the attributes, there are various ways they can be actually measured. For this purpose the measurementType Meta Data Attribute can be used. It can have the following values:

When using the values [average, rms, minimum, maximum], another metadata attribute called measurementInterval should be used to give the length of the measurement period in seconds. Also the Meta Data timestamp attribute should be the end time of the measurement period.

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.

Additional Information about Data Model: 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.

No comments

New harmonization repository

  By , , , , , , , , ,

In order to provide a more transparent and participative approach to the creation and maintenance of data models, here you can see the three stages for a usual data model to be part of the official list of data models.

1.- Pending is the ‘wild’ zone where developers share their thoughts and create their data models. When finished (ready) they can create a PR on the right Subject repository.

2.- Harmonization is the repository for those new accepted models while they are fine-tuned or completed

3.- Subject means the repository in which the data model is officially published. Once there they are versioned when necessary.

Pending Harmonization Subject
Control of contributions No Yes Yes
Scripts for checking No Yes (specific) Yes (only acceptance and on update)
Code inside json schema No Harmonizing Local standard

Global standard
Versioning No No Yes
Managed Each contributor Contributor + SDM control SDM control
In domain No No Yes
Accept issues Yes but not managed Yes Yes (Here the open ones)
First Access Anyone
  1. Anyone previous pending acceptance
  2. Members direct
 N/A

SDM: Smart Data Models initiative

No comments

Connection with European open data portal

  By , , , , , , , , ,

The European open data portal is possibly the biggest open data portal in the world with more than one million free datasets coming from 36 countries.

One of the mechanisms to access its data is the use of the standard of DCAT-AP standard 2.0 which defines its catalogue of resources.

Image

In the repository pending there are two data models, in progress to connect a dataset and a distribution as an additional resource by using NGSI. The idea is to create a script to map this resource into NGSI.

No comments

Updated the csv examples

  By , , , , , , , , ,

Every data model has a directory with examples of the payloads (json and jsonld) in key-values and normalized formats.

But it also includes examples of csv that it could help to connect the data models for other platforms.

Now, these examples are re-created automatically once a day.

The naming convention for these examples are the same name of the original payload plus a .csv suffix.

An example for the Battery data model examples.

Best.

No comments

Searchable descriptions of data models

  By , , , , , , , , ,

In the upper menu (option Search descriptions) there is a searchable database of the descriptions for all the properties across the different data models.
Try it out here.

This DDBB is updated daily.

No comments

Minor update on guidelines

  By

Included two new sections on the guidelines for the Smart Data Models

$ref

Whenever possible they will be absolute references in order to provide the ability to use the data models isolated from the rest of documents

and

definitions

The section definitions will be included in the subject-schema.json name of the subject.

 

 

No comments

Drafted Node data model

  By , ,

This data model, node, is not officially approved but is on the path for becoming a resource for simulation a node inside a digital twin model (See this video) receiving the measures from an array of sensors controlling different properties and to provide these data to several other nodes which can be connected to.

Remember that incubated repository is devoted to the design and test before submitting officially to the Smart Data Models initiative.

You can claim access to this repository in the issue form option access to the incubated repository.

 

No comments

Converted Global Data dictionary codes

  By , , , , , ,

What is Global Data Dictionary

The GS1 Global Data Dictionary (GDD) is a repository of the data elements defined across all GS1 Standards.

What is the scope of the Global Data Dictionary?

GS1 Business Message Standards (BMS) and their components with definitions for GDSN 3.1, 3.1.2 , 3.1.3 and 3.1.4, GS1 XML for EDI 3.0, 3.1, 3.2 and 3.3, TSD and EPCIS 1.0.1. Higher versions will be added upon ratification.

  • Business Messages
  • Business Information Entities – message components and the relationship between them
  • Business Data Types
  • Code Lists used in Business Messages

The Business Messages are composed of Business Information Entities that comprise classes of information and their attributes. The attributes, in turn, have data types that may contain code list

The Full Set of GDSN & Shared Code Lists, and the Full Set of EDI, EPCIS, CPV & Shared Code Lists is now in a structured format in json much easier to integrate with NGSI platform.

Soon there will be part of them integrated into the smart data models.