Background & Definitions
In Consibio Cloud a project is an environment in which data is organised and controlled.
We sometimes refer to it as a “data sandbox”, where you can manage information, users, roles etc. about the data and also run specific tasks / features like Alarms, Controllers and so on.
An example of a project, could be “Consibio Office”. In this project, the members of can see information from sensors placed in the physical office and get access to all of the features available from Consibio Cloud.
Another example could be “My Greenhouse 11”, where all information from my greenhouse would be accessible and I could control who in my company should be able to see it.
Inside a Consibio Cloud Project
From the home screen, a user can tap into a project by clicking on the project name from the project overview table.
Once inside a project, the user can access everything related to this specific projects under the various tabs/sections presented (On mobile-version, these can be accessed by tapping the “More” button).
The tabs available inside a Consibio Cloud Project are:
The Dashboard, Controllers and Alarms sections are described in their respective documentation pages, since they are features requiring detailed descriptions, but the project Members and project Settings are described below.
In the Members section / tab, all members associated with the project can be seen in the members table.
Their respective roles can also be seen. Depending on the role, the user has certain permissions and features available. As an example, a user with a viewer-role cannot edit the controllers within a project.
Currently, there are three types of roles that a user can have within a project:
The exact differences between each role is described in the table below:
|Feature / Permission||Owner||Editor||Viewer|
|Download data in a .csv format||X||X||X|
|View status and settings of controllers and alarms||X||X||X|
|Create, edit or delete private and/or shared alarms||X||X||–|
|Create, edit or delete controllers||X||X||–|
|Toogle Batch mode on or off||X||X||–|
|Change payment details||X||–||–|
This setting can be changed to two different states – true or false.
By default, the batch mode in a project is set to false.
When the batch mode is set to false, all the controllers inside a project will run continuously and not at a specific starting point.
However, when the batch mode is set to true, a new object (i.e. Batch Controls) will appear on the dashboard of the project.
This object can control the starting point of all controllers within the project. In other words, once a project is in batch mode, the user has to click the “start batch” button in order for the production / research / experiment to start and thus run all the user-defined controllers.
Let’s imagine you have a production schedule with several different controllers for multiple process parameters (e.g. temperature, humidity, CO2-level, H2S-level). Furthermore, each of these controllers also have dynamic setpoints, so the starting point of the controller suddenly matters.
Instead of activating each individual controller, the batch mode enables you to start all of your controllers at the same time. This enables you to run your production efficiently and consistently every time.
Once you have pressed start batch, the batch time will be shown and all subsequent controllers and actuators will then begin running: