assetTable is contains all assets and their location.
We are using the database TimescaleDB, which is based on PostgreSQL and supports standard relational SQL database work, while also supporting time-series databases. This allows for usage of regular SQL queries, while also allowing to process and store time-series data. Postgresql has proven itself reliable over the last 25 years, so we are happy to use it.
If you want to learn more about database paradigms, please refer to the knowledge article about that topic. It also includes a concise video summarizing what you need to know about different paradigms.
Our database model is designed to represent a physical manufacturing process. It keeps track of the following data:
- The state of the machine
- The products that are produced
- The orders for the products
- The workers’ shifts
- Arbitrary process values (sensor data)
- The producible products
- Recommendations for the production
Please note that our database does not use a retention policy. This means that your database can grow quite fast if you save a lot of process values. Take a look at our guide on enabling data compression and retention in TimescaleDB to customize the database to your needs.
A good method to check your db size would be to use the following commands inside postgres shell:
configurationTable stores the configuration of the UMH system.
countTable contains all reported counts of all assets.
orderTable contains orders for production.
processValueStringTable contains process values.
processValueTable contains process values.
productTable contains products in production.
recommendationTable contains given recommendation for the shop floor assets.
shiftTable contains shifts with asset, start and finish timestamp
stateTable contains the states of all assets.
uniqueProductTable contains unique products and their IDs.