The SLA assigned to the requirement determines the workflow options available for the requirement lifecycle. The enumerated workflows are assigned to the same SLA as the requirement. Before saving the requirement, the user can customize the workflow assigned by the system if there is more than one option. Within the system, SLAs are specific and time-based to monitor and correct performance. They can be applied to any of the following elements of the application: If a request is registered at the Service Desk, the requirement is supported by the SLA assigned to either the part, the customer, or the organizational unit. If none of these items have been assigned to an SLA, the SLA, which has been assigned as a system standard in the Admin>Setup>Privileges>Requests tab, will be automatically applied to the request. The system also provides SLA compliance reports that allow managers to set and pursue availability and performance goals that reflect business objectives. SLAs are used in all processes and are assigned when creating requirements. Individuals with privileged access must respect the rights of system users, respect the integrity of systems and associated physical resources, and comply with all relevant laws or regulations. Individuals are also required to keep abreast of the procedures, business practices and business management guidelines regarding the activities of their local department. Privileged access allows a person to take actions that may affect other users` computer systems, network communication, or accounts, files, data, or processes. Privileged access is typically granted to system administrators, network administrators, IT account management officers, or other staff whose professional duties require specific qualifications for an IT system or network.
SLAs are integrated into the support process when a new workflow is created. An SLA is assigned to a workflow and indicates the expected solution time for a request. To successfully meet SLA expectations, the system allows the Service Desk to assign each workflow status of a requirement to an operational level agreement (OLA) or underpinning (UC) contract. In particular, the principles of academic freedom, freedom of expression and data protection of information have a significant impact on the administration of IT systems at UBC. . . .