Add modules in E-Ticket System (Computerized Maintenance Management System)

Link: [login to view URL] CURRENT STRUCTURE Roles: 1. Admin 2. Client 3. Staff Admin Admin can manage tickets, staff, clients and departments. He can change the status of tickets. Client and Staff Client and staff can open new tickets and can delete them. REQUIRED STRUCTURE Application should be in multi-language. Supporting LTR and RTL. Three main Modules: 1. Open/Close Tickets 2. Assets Management 3. Analytics and Reports Roles: 1. Admin 2. Complainer 3. Department Controller 4. Technician 5. Assets Manager Admins Admin will create buildings and departments. For buildings, admin will create the complainers. One building can have multiple complainers or one complainer can open trouble ticket for multiple buildings. Admin can assign complainers to buildings. Admin will create the departments and controller for each department. Same possibility that each department can have multiple controllers or controller can control multiple departments. Complainers Complainers can open trouble tickets only for their buildings (which are assigned by admin) and can delete them. Request will be for specific department. While making a ticket, complainer will select to which department they want to complain. Department Controllers Respective department controller will be notified about the ticket through the email and in top header notification center.. The controller will study the ticket and forward the task to technician. Controller will create the use accounts for technicians. Technicians Technicians will be notified about the task by controller through email in top header notification center.. Technician will go to building to investigate the problem. After investigating, technician will give feedback to controller. The department controller will check history to see if there is any previous complaint for the same problem or not. Depending upon the situation, the item maybe fixed by technician or maybe replaced. After solving the problem, the technician will enter the solution with cost in to the system and also request controller to close the ticket. The controller will be notified through email about the closing request in top header notification center.. The controller will confirm with complainer and if complainer is satisfied then controller can close the ticket and if not then re-open the ticket. Asset Managers Admin will be responsible to create asset managers. Admin can assign two roles to one user e.g. a user can be department controller and asset manager at a same time. Or a user can be complainer and asset manager at a same time. Or asset managers can be for specifically for multiple buildings or departments. Asset Managers will be responsible to manage all the assets of the department. ANALYTICS AND REPORTS We need comprehensive reports of assets and complains. For example, how much asset available in stock, on which building was used, who took the asset, at what day/time? Similarly, for building what are the assets, incoming assets, used assets, stock etc. Admin can view reports for all the buildings and departments. Others can see for their specific building or department. We have one option in menu called Reports.