Creating Time of Attendance

12 min

this feature provides a variety of actions, such as \including, changing, and deleting the attendance \ \time \ \of the following types\ global applicable to all services; customer applicable to the contract services; and incident/request/procedure applicable to a specific service ✅ rule standard slas are gold, silver, and bronze but other types can be created 🖊 note after creating the sla, the cost and price values will be presented for each service based on the sla created and this data will come from the financial process " financial cost calculation", on the " cost distribution " and " set price " tab according to the defined strategy (fixed and variable) before getting started it is necessary to register previously contract(s) and service catalog for the sla (portfolio/services/activities) procedure access the functionality time of attendance through the main menu processes > service level management > attendance time ; click on the desired tab ( \search\ / \register\ ) and action; function description save save the new sla delete delete the sla edited clear clear all form fields search 3\ select the type of sla to search for filter description global for global use, the time of attendance has no specific treatment client for a specific contract specific for a specific service sla title title to search grid sla searched with the criteria with a selection radio button, sla title, description and status “a” active or “i” inactive register 4\ choose the type of sla filter description global for global use, the time of attendance has no specific treatment client for a specific contract specific for a specific service 5\ complete the sla basic data basic data fields description title ( ) title of identification of the sla status ( ) the status between "active" or "inactive" impact define the sla impact between "high", "low" and "medium" urgency define the urgency of the sla between "high", "low" and "medium" change impact/urgency inform if the impact or urgency can be changed in an incident or service request registration seasonal select if this sla will be used from time to time start date ( ) set the start date of sla end date set the end date of sla ( mandatory if seasonal is checked) evaluates in set the date to evaluate this sla description the relevant description for using the sla scope scope to the sla contacts contact for the sla time of attendance by priority the service time of attendance, taking into consideration the priority defining time for capture and resolution hour enter the sla "capture" and "resolution" time minute enter sla "capture" and "resolution" minutes ( ) indicate mandatory field ✅ rule the priority is used to identify the time required for an action to be taken the priority goes from 1 to 5 , with 1 being the highest priority and 5 the lowest select the priority to define the time (in the sla) capture set the time of capture of the service request, according to the priority selected; resolution set the time of service resolution according to the priority selected ⚠️ attention ! before completing the fields in " automation ", it should be properly parametrized, it must be properly parameterized, so it is necessary to execute the steps in the knowledge creation escalation rule, except for parameter 190 that must be equal to 'n' in this context ; 6\ complete the automation fields ( if it is needed) automation fields description time of action time after a scenario is true for the execution of an automatic action e mail template e mail template used to send notifications priority the new priority that the service that will be scheduled will receive; group group to whom the assistance will be directed after the scheduling action; 7\ complete the target of the sla targets fields description treeview treeview with contracts / services / activities ( will be filled based on the type of sla, facilitate linking services to customers to show all the services used by a particular customer unit (only for "client" or "specific") ( ) unit and its permission for the sla, (select a contract, a unit, and the system will make a grid with the selected unit and the priority assigned ) employee (only for "client" or "specific") ( ) employee and its permission for the sla (select an employee and the system will make a grid with the selected employee and his priority assigned, defining vip attendance) requester's group (only for "client" or "specific")( ) requester group and its permission for the sla, (select a contract, a unit, and the system will make a grid with the selected unit and the priority assigned ) ( ) indicate mandatory field 🖊 note to calculate the sla, the system performs the following verifications if the \service x contract\ is in more than one type of sla, note that the specific sla type takes priority over the types customer and global ; the sla client type takes priority over the type global ; the system still considers for the sla assignment impact and urgency this attribute being identified for more than one type of \service x contract\ for the same type of sla, always takes into account the priority with the least impact, that is, note 5 ; the system considers for the sla assignment users, groups, or special units, known as vip in these cases, it is normal for the manager to register global sla with low priority and include users, units, and groups that can receive sla with higher priority a target is a place where the user will identify their main targets for using the sla the system will make a treeview (with contracts, the listing of services in the production environment, and its activities) all the customers' contracts linked with sla will be checked as well as portfolios, services, and activities this way, it is possible to identify which customer/contract is using which service from the service catalog (according to the permissions and service level agreement) when assigning activities to the sla the system enables the user to view / edit the financial value of the service the service hours refer to the working hours of the service level agreement used and will be referred for all services and activities linked the service level agreements monitor (slam) can be monitored against the agreed service level to control breaches and service exceptions appearing in the main screen of incidents and service requests, through the " sla status " field it is possible to do the same monitoring through the incident and service request dashboards both (main screen/dashboards) will monitor in real time 🖊 note the contracts types retrieved are associated olas, supplier / underpinning contracts of services ⚠️ attention ! if the attendance time does not allow the change of impact and urgency, the system automatically replaces what is sent via webservice to the impact, urgency, priority, and time of attendance defined in this register ✅ rule before the n minutes (informed in the time of action) and in case it does not have performed any action in the service request linked to this time of attendance, the system will attribute the priority and will escalate the execution group to the service request