0:12 → 0:16
masculine_0In the last videos we have configured the nexy system so far
0:16 → 0:19
masculine_0that it can now be used to its full extent.
0:20 → 0:25
masculine_0All sensors can now transmit their data on the respective material situation,
0:25 → 0:32
masculine_0at the same time, information can be fed back to the shop floor or actions can be triggered.
0:32 → 0:37
masculine_0Very often, however, it is the case that different things happen at one location,
0:38 → 0:42
masculine_0that have nothing to do with each other or should have nothing to do with each other.
0:42 → 0:46
masculine_0These could be, for example, different halls,
0:46 → 0:48
masculine_0in which the nexy system is installed.
0:48 → 0:51
masculine_0Although managed via a common sensor bridge,
0:52 → 0:55
masculine_0but in the organization they should be considered separately.
0:57 → 0:59
masculine_0Or there are use cases in a hall,
0:59 → 1:02
masculine_0organized by different departments.
1:03 → 1:12
masculine_0For example, one department is responsible for all applications with tilting sensors, and another department uses all relay receivers.
1:13 → 1:22
masculine_0But if everyone can then look into the configuration and also reconfigure the corresponding devices from the other departments,
1:22 → 1:26
masculine_0this can easily lead to chaos.
1:27 → 1:33
masculine_0To avoid this, we have integrated multi-tenancy into the nexy system.
1:33 → 1:39
masculine_0This means that I can create different tenants in the Sensor Bridge,
1:39 → 1:43
masculine_0each of which can access different parts of the nexy system.
1:46 → 1:50
masculine_0I log in to the Sensor Bridge interface again as admin.
1:51 → 1:53
masculine_0Here in the upper right corner we can see the current tenant.
1:54 → 1:57
masculine_0There is always one tenant by default. The tenant steute.
1:58 → 2:07
masculine_0It cannot be deleted and it has super admin rights at the same time. As the tenant steute I can create additional tenants and configure their rights.
2:07 → 2:11
masculine_0To do this, I click on the user menu and the sub-item tenant administration.
2:12 → 2:14
masculine_0I'm going to create 2 new tenants now.
2:15 → 2:19
masculine_0A click on the plus button and a new tenant can be created.
2:19 → 2:28
masculine_0Let's call one tilting sensor user and the other relay user. In the real case, of course, more meaningful names are a good idea.
2:28 → 2:34
masculine_0For this example, however, we will simply name the tenants according to their use case for better clarity.
2:34 → 2:36
masculine_0You can give a login hint,
2:36 → 2:39
masculine_0for example, if the password has been forgotten.
2:39 → 2:41
masculine_0This will then appear on the login page.
2:41 → 2:46
masculine_0I'll write here "call the IT Service on 110".
2:47 → 2:52
masculine_0I can also leave a corresponding comment on the tenant.
2:52 → 2:55
masculine_0Here I take "application with tilting sensors".
2:56 → 2:58
masculine_0and I create another tenant,
2:58 → 3:00
masculine_0the tenant relay user.
3:00 → 3:08
masculine_0Again, "call the IT service on 110" and the remark is "application with relays".
3:09 → 3:12
masculine_0To register with one of these tenants afterwards,
3:12 → 3:15
masculine_0I must be registered as their authorized user.
3:15 → 3:19
masculine_0That's why I have to create users for these tenants.
3:19 → 3:23
masculine_0I am currently registered as admin in the steute tenant.
3:23 → 3:29
masculine_0As admin in the steute tenant, I have universal rights. I can therefore pretend that
3:29 → 3:32
masculine_0I were now the tenant tilting sensor user,
3:32 → 3:38
masculine_0can go to the user administration there, and I see as tenant tilting sensor user - up here it says,
3:38 → 3:40
masculine_0which tenant I am at the moment -
3:40 → 3:42
masculine_0there are no users yet.
3:43 → 3:45
masculine_0I'll create a user now.
3:45 → 3:49
masculine_0I call him tilting sensor user 1. For the tilting sensor user 1
3:50 → 3:52
masculine_0I can now assign different permission levels.
3:53 → 3:54
masculine_0I'll assign admin here,
3:55 → 3:58
masculine_0that means tilting sensor user 1 can do anything.
3:58 → 4:00
masculine_0Add new switches,
4:00 → 4:02
masculine_0configure and also delete them.
4:03 → 4:09
masculine_0There is also the Read and Write level, where he has only limited access rights, and even more interesting
4:09 → 4:16
masculine_0the Read only level. For example, perhaps a service technician should only have access to the switch list,
4:16 → 4:22
masculine_0to see where the battery level may be low and the batteries need to be replaced,
4:22 → 4:27
masculine_0without possibly being able to change anything fundamental in the configuration.
4:30 → 4:33
masculine_0I can assign separate rights for the REST API.
4:35 → 4:37
masculine_0Now the assignment of a password -
4:37 → 4:39
masculine_0at least 8 characters long -
4:39 → 4:43
masculine_0and I have created the user tilting sensor user 1 in the tenant tilting sensor user.
4:44 → 4:48
masculine_0I now also make this synonymous for the tenant relay user.
4:52 → 4:54
masculine_0Relay user 1 is also an admin,
4:56 → 4:59
masculine_0and I also assign a password for him.
5:00 → 5:05
masculine_0In total, I have now created 2 additional tenants, each with one user.
5:06 → 5:12
masculine_0If one of the users who have just been created now logs in to the Sensor Bridge with his access data,
5:12 → 5:15
masculine_0he sees everything that is available in his tenant.
5:15 → 5:17
masculine_0I'll do this now for illustration,
5:18 → 5:25
masculine_0open 2 more browser windows and log in once as tilting sensor user 1 in the tenant tilting sensor user and once as
5:25 → 5:29
masculine_0relay user 1 in the relay user tenant.
5:32 → 5:37
masculine_0The access points are visible as a common infrastructure in all tenants.
5:38 → 5:43
masculine_0However, a sensor or actor is only visible to each tenant
5:43 → 5:46
masculine_0as long as it is not assigned to a managed group.
5:47 → 5:51
masculine_0Since new devices are automatically assigned to the unmanaged default group,
5:51 → 5:55
masculine_0they appear in the list of sensors and actors of all tenants.
5:56 → 6:00
masculine_0However, if a device is assigned to a managed group,
6:00 → 6:06
masculine_0it only appears in the corresponding tenant and is therefore no longer visible to the users of the other tenants.
6:07 → 6:10
masculine_0We have not yet created any groups for the two new tenants.
6:10 → 6:13
masculine_0Let's do that now. In the tenant tilting sensor user
6:14 → 6:21
masculine_0let's create the group "Hall 1 tilting sensors", for the relay user the group "Hall 1 relays".
6:25 → 6:32
masculine_0Now we have created corresponding groups in the two new tenants and can now work with them.
6:32 → 6:40
masculine_0Let's see what happens if I as one of the tenants assign one of the previously unassigned sensors to my group.
6:46 → 6:51
masculine_0It disappears with the other tenants and is therefore no longer available to them.
6:52 → 6:56
masculine_0Basically, each sensor can only be assigned to one group.
6:57 → 7:04
masculine_0And this happens according to the first come - first serve principle. If a sensor is to work for another tenant,
7:05 → 7:08
masculine_0it must be released by the previous tenant.
7:08 → 7:12
masculine_0It is detached from the group and assigned to an unmanaged group,
7:12 → 7:15
masculine_0such as the default group.
7:16 → 7:23
masculine_0Only then is it visible to all other tenants and then, to put it bluntly, can be caught by another.
7:35 → 7:40
masculine_0The following procedure applies to the organization and group structuring of a tenant:
7:41 → 7:43
masculine_0A new device is activated,
7:43 → 7:47
masculine_0then appears for all tenants in the default group, and the tenant
7:47 → 7:49
masculine_0for whom the device is intended,
7:50 → 7:53
masculine_0can then incorporate this sensor into one of its groups.
7:53 → 7:56
masculine_0The result: the nexy system!
7:56 → 8:01
masculine_0One single wireless infrastructure and as many separate applications as you want.
8:02 → 8:07
masculine_0That's it for today. Have fun imitating it. See you!