## 5 Case Study 1--ITMI: Non-IoT  
In this case study, a rail robot needs to be implemented for a North Quebec Rail (NQR) project. To achieve it a set of tasks required to be implemented by a team. Figure 5 illustrates ITMI's local environment system architecture. To complete project tasks within the start and end dates, all users must be authenticated using passwords, fingerprints, or PIN codes to access the database or labs. Authenticated users are authorized, after checking the defined AC rules in the policy database, to access resources and perform operations according to their roles, groups, and other attributes of users.  
According to the project requirements, some users might be assigned to a certain role, while others may also be assigned to different groups, and some may share some tasks with each other. Access rights grant access to users with a certain role/group to some resources and allow them to perform some actions on the database (read, write, update...), and on machines (switching on/off, monitoring, modifying settings...). Access decisions could be allowed or denied based on the defined policy. However, in the following we describe the guidelines to perform the project tasks:  
Figure 4: The Case studies: The implementation phases and the used tools.  
Figure 5: The system architecture of ITMI: non-IoT environment.  
* The NQR project is administered by [PERSON], ITMI's director, who has full access to databases and labs. He manages the priority of project tasks and directs the manager in setting up the appropriate methodologies to implement them. Before running the project, he must confirm all details and tasks.
* According to the director's guidelines, [PERSON], the manager who supervises advisers and has access to the database tables Projects and Tasks, creates the project record and sets the necessary tasks. Also, he updates the status of each project task (in progress, completed, on hold...) depending on the project's performance.
* The advisers, [PERSON] and [PERSON], choose groups of specialists and technicians based on their expertise. Then they assign to each group the necessary tasks, and determine which machines or equipment are required. They have full access to both the GroupTasks and Requirements tables in the database.
* Specialists are researchers with specialized knowledge in a particular field who work with technicians to complete projects. Technicians perform technical tasks such as maintenance, machines/devices installation, etc. For the NQR project, specialists and technicians have access to the AI lab where the Rail Robot machine is located, and to the 3D lab where the 3D printing device exists. To perform some of the required tasks we have the following groups:
* GroupA: The specialists, [PERSON] and [PERSON], test the robot, then assess and write the obtained results into table Results. The technician, [PERSON], assists them in troubleshooting the robot and hardware/software problems.
* GroupB: The specialists, [PERSON] and [PERSON], read/analyze the results to check if any flaw(s) exist and might affect the rail robot's performance. The technician, [PERSON], operates the robot to match the analyzed results to the robot's performance.
* GroupC: The specialists, [PERSON] and [PERSON], redesign and implement another prototype for the flawed part(s). The needed part(s) are created using a 3D printer. The technicians, [PERSON] and [PERSON], help them replace damaged or flawed part(s), then verify robot system compatibility.  
Advisers, specialists, and technicians are allowed to access resources during the work hours via private network. Their access rights must be revoked once the project is over.