Labels
The UpBlue Platform uses labels as basis for collecting and reporting data. Labels are used all over UpBlue. Labels are used in the following steps;
- Creating connections
- Creating rules
- Creating dashboards
- Filtering
- calculations
- and much more
- Purging data
Each datapoint inserted into UpBlue contains;
- A tag name
- One or more labels
- A value
- Timestamp
Each label consist of a key and a value. The key can be for example be machine with a value of printing1.
One or more datapoints with the same labels and tag is called a time-serie.
Labels are extremely powerful for finding and filtering the right data.
For example a time-serie contains the following labels;
| Key | Value |
|---|---|
| Enterprise | UpBlue |
| Site | Factory1 |
| Area | Hall1 |
| Cell | Line1 |
| Unit | Step1 |
Tag name is temperature.
Let say there are multiple units and each Unit has one temperature sensor. In the dashboard you can list all the temperature sensors in Hall1 by filtering on Hall1 and tag equals temperature.
Working with labels has the advantage over a traditional tag tree is that timeseries are not restricted by a one dimension, that of the tree. The example above is hard to do with a tree. Grouping and filtering is much easier.
In UpBlue there are a number of predefined labels which are mandatory. Namely; Enterprise, Site, Area, Cell and Unit. This labels are based on ISA-88/ISA-95.
What is ISA-88 and ISA-95
ISA-88 and ISA-95 are both standards developed by the International Society of Automation (ISA), but they serve different purposes and focus on different aspects of industrial automation.
ISA-88 (Batch Control)
- Focus: ISA-88 is primarily concerned with batch process control. It provides a framework for designing and operating batch processes.
- Models: It defines models for physical and procedural control, including the physical model (enterprise, site, area, process cell, unit, etc.) and the procedural control model (recipe, procedure, operation, phase).
- Recipes: A key concept in ISA-88 is the use of recipes, which are sets of instructions for producing a batch of a product. These recipes can be general, site-specific, master, or control recipes1.
- Flexibility: ISA-88 aims to provide a flexible and consistent approach to batch process control that can be applied across various industries1.
ISA-95 (Enterprise-Control System Integration)
- Focus: ISA-95 focuses on the integration of enterprise and control systems. It aims to bridge the gap between business planning and logistics (ERP systems) and manufacturing operations (MES systems).
- Levels: It defines a hierarchical model with five levels:
- Level 0: The physical process
- Level 1: Sensing and manipulating the process
- Level 2: Monitoring and controlling the process
- Level 3: Manufacturing operations management (MES)
- Level 4: Business planning and logistics (ERP)
- Data Models: ISA-95 provides standard data models and terminology to facilitate communication and data exchange between different systems and layers within an organization2.
- Scope: While ISA-88 focuses on batch processes, ISA-95 covers both batch and continuous processes and is concerned with the overall integration of manufacturing and business systems2.
Key Differences
- Scope: ISA-88 is specific to batch process control, whereas ISA-95 covers a broader range of manufacturing processes and focuses on integrating enterprise and control systems.
- Models: ISA-88 provides detailed models for batch process control, while ISA-95 offers a hierarchical model for enterprise-control system integration.
- Application: ISA-88 is used for designing and operating batch processes, while ISA-95 is used for integrating and managing data across different levels of an organization2.
ISA-88 physical model
The ISA-88 physical model is the basis for UpBlue label. In ISA-88 this model is defined;
| # | Level | Description |
|---|---|---|
| 1 | Enterprise | Your company, the Business Entity |
| 2 | Site | The factory (site), the production location |
| 3 | Area | A place inside the factory, a hall or a specific area. |
| 4 | (Process) Cell | The production space. A production line. Multipurpose. |
| 5 | Unit | A part of the production line. Singlepurpose. |
| 6 | Equipment Module | set of components inside the machine. |
| 7 | Control Module | A valve, actuator |
Each level has a one to many relation. One Enterprise can contain one or more Sites, one Site can contain one or more Areas and so on. In UpBlue Level 6 and 7 are optional and can be added on a per rule basis. The user is also free to add extra labels when needed.
Enterprise and Site is prefilled at connection creation. This can be override at creation. Cell and Unit can be overruled on a per rule basis.
Labels are not meant for dynamic data. For example batch number of productionordernumber. The database is optimized for this kind of data to be in the value with its own timeserie.
The tag is in fact also a label with the label __name__
Think good about the labels you choose! Labels cannot be changed in the databases after they are stored. When changing labels in the connection, from that moment on, new data gets this new label. Old data keeps the old labels. In effect a new timeserie is created. When changing labels, check if your dashboards keep on functioning.