Modeling the Data Model functionaly representing your Industry

The Postit approach

The postit approach is a no-brain way to give functional meaning to the TSDB. It is functional simple and fast. Though it may not free from technically setting up the requesting environment (such as ElasticSearch engine).

The drawback being the lack of readability impairing the business commitment to the Information System functional coherence.

The conclusion is that the postit approach is suitable for IT-only driven initiatives, with little cost and no special organisation.

Data Model First : the one transformation path to support 360° vision

When it comes to address Hypervision ambitions, the functional contextualization data  on top of the whole TSDB becomes first-class in the enterprise.

The data composing the functional contextualization goes beyond the IT domain.

Definitely, this information is the property of the whole enterprise. And as such, it must be constructed by the IT with full business commitment.

The state-of-the-art of constructing enterprise-class information is to use the Entities-Attributes-Relationships UML tools to communicate and deliver the data.

As such, IngeniBridge software is fully data-model-centric.

In its data offer, Deagital promotes the data modeling as the first step in this initiative.

Our first example

Our first example is open public on GitHub. Click here to access the UML Data Model. It can also be viewed just down.


Before describing the contents of this UML Data Model, we must keep in mind the goal to functionally describe the time series stored in our TSDB database.



  1. The Asset and TimeSeries objects are entities provided in the IngeniBridge Framework. And, of course, any Asset may be associated to multiple times series
  2. The data of my company is created as MyCompanyData specializing the TimeSeries base class. MyCompanyData is qualified as a TypeOMeasure which contains the unit and is part of a Nomenclature.
  3. The actual time series in my company are AcquiredMeasure or ComputedMeasure.
  4. It is important to have a common container to be able to add information for all the assets in my company. That's why the MyCompanyAsset is the mother of all the types of assets in use in my company. MyCompanyAsset is not instanciable as is as it is abstract.
  5. The ProductionSite is the site of production of my company. It is associated to a set of equipments that specialize from the abstract Equipment class. Note that the production site is set on a Sector which is an influence zone.
  6. The sensors deployed are all of base class IOT. The telephone number will support distributing the data received in the SMS enveloppe in the right slots within the Time Series Database (TSDB).

So the modeling of all the entities and their attributes is set to support the functional contextualization of the time series in the TSDB.

The model is visible down: