| Decision | Status | Stakeholders | Outcome | Due Date | Owner |
|---|---|---|---|---|---|
| DD_11 Graphical User Interface | STARTED | ||||
| DD_14 UML modelling of flecsimo | STARTED | ||||
| DD_9 MQTT Message Structure | DECIDIED | See Factory Communication Protocol and flecsimo base.msg.py module | |||
| DD_8 MQTT Topics on Site Level | DECIDED | MQTT topics will expand dynamically "upwards", i.e. topics from "area" and "cell" level will be re-written on upper level. Example: area1/cell4/status on area1-level will be extended to siteX/area1/cell4/status on siteX. | |||
| DD_7 MQTT Topic-Structure | DECIDED |
| |||
| DD_6 Inter-Process Communication | DECIDED | MQTT will be used as messaging backbone all over the solution | |||
| DD_5 Meta-Model of flecsimo | DECIDED | The middle-tier in the meta-model is called area | |||
| DD_4 Style Guide | DECIDED | Python coding shall follow PEP-8 and PEP-257 guidelines (using google-style for docstrings) | |||
| DD_3 Top Level Package Name | DECIDED | The top-package in Python development will be named flecsimo. | |||
| DD_2 Project name | DECIDED | The project name is flecsimo | |||
| DD_1 Programming Language for flecsimo Project | DECIDED | The IT-components will be developed in the Python language, version 3.8. | |||
| DD_10 Development Environment | DECIDED | The development environment for the IT-solution is
| |||
| DD_12 Cell Types | DECIDED | The flecsimo system will support the following cell types:
| |||
| DD_19 Should we use double-floor-design for flecsimo cells? | DECIDED | Double-floor-layout will get standard for flecsimo models | |||
| DD_18 To src/ or not to src/ ? | DECIDED | The packages will use the src/ layout | |||
| DD_15 License | DECIDED | Use GPLv3+ license | |||
| DD_17 Suport of multi-site use cases in data model | DECIDED | Front-end Designer, Integration Designer, App Designer | The data model will reflect multi site use of components by storing the site id in every transactional data object | ||
| DD_13 Cell Status Promotion | DECIDED | The cell status will be promoted using retained MQTT messages. The status message will contain the following information:
| |||
| DD_16 MQTT topic name all upper or lower case? | IN PROGRESS |
Überblick
Inhalte
Apps