Requesting is two types that correspond to different business use cases :
Building on the previous requesting model, it is possible to stack the criterias. For example requesting all the datas of type electricity upon a functional sectorization.
Every entity, be time series or asset, is strongly typed. As such, it is possible to request upon those types. For example request all the assets of type ProductionSite. Of course, UML inheritance is applicable as regards super types.
The IngeniBridge database is built as a hierarchical tree. In this logic, the parent characteristics propagate down to the nodes in the tree. That is why it is possible to request all the time series that are put under nodes of type ProductionSite or all the time series that are put under nodes of type Equipment and those upon a functional sectorization.
The indexer engine has a generic behavior. But it is possible to enrich its behavior using special attributes set at design time into the object model. These special attributes are provided by the native IngeniBridge core of functions which is a public library (more on this in next chapters).
Every sigle node in the tree has a Begin and End time. Of course when the end time is expired, it means the node is not activated. It is possible to use the request engine at a specific date and time to see the picture at this very moment (more on this in the next chapter about historization).
It is possible to request the full Data Model of the operational IngeniBridge database. This link retrieves it. So, this way, it is possible to reuse it widely in the IT architecture.