Jump to content

Search the Community

Showing results for tags 'sla'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Hornbill Platform and Applications
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Service Manager
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Configuration Manager
    • Timesheet Manager
    • Live Chat
    • Board Manager
    • Mobile Apps
    • System Administration
    • Integration Connectors, API & Webhooks
    • Performance Analytics
    • Hornbill Switch On & Implementation Questions
  • About the Forum
    • Announcements
    • Suggestions and Feedback
    • Problems and Questions
  • Gamers Club's Games
  • Gamers Club's LFT

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Organisation


Location


Interests


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 39 results

  1. If a job is closed/resolved/cancelled then it clears all sub-statuses. Therefore when trying to run reports, we are unable to see whether a job has been on-hold and how long for if it is now closed/resolved/cancelled. In some instances, a job has clearly been on hold, e.g. the SLA for the job was 5 days and says met, however the job was resolved 3 months after being logged. The only way to delve deeper and find out how long the job was on hold for it to search for the job itself in the analyst portal, which is impractical when looking at reports for thousands of jobs. I believe this was raised by another colleague on the Customer Support portal back in April/May, with the resolution stated as a product defect that will be rectified in a later update. Do you have any idea when this will be actioned as it is affecting our reporting?
  2. As a follow-on to my other post about additional reminder destination, it would be useful to have the ability to have the option to send the reminder as a notification message, as well as an email message to the same target recipients as currently supported and mentioned in the linked post. I am trying to reduce out teams dependance on emails and what them to focus on notifications and activities within Hornbill not start having to check their separate email as well. Cheers Martyn
  3. Along similar lines to @yelyah.nodrog , would it be possible to add the ability to send the reminder to the 'Team' the request is assigned too and also 'Members' linked to the request. I could also see a need in the future to be able to send the reminder to all 'Supporting Teams', but that would not be applicable to ourselves until there is the ability to add read-only supporting teams so they can view the requests but not action them, which would need to be excluded from the reminder. Cheers Martyn
  4. we have many time zone to manage at least 6, for each I've created a working calendar and a service level, now the issue I'm facing is that the SLA are not correctly assigned, the assumption is that the sla has to be choosen based on the company AND the site. Also consider that each service have potentially all the 6 sla; here are some example
  5. Hi, Is there anywhere in a request where it lists what the fix time was? In Supportworks, there was a field called "Fix Time" that calculated the time between the request being logged and resolved. Thanks Lauren
  6. We have the situation where our 1st Tier are responsible for the Response SLA and our 2nd Tier are responsible for the Resolution SLA. Reporting on the latter is simple as the 2nd Tier person is the owner of the request when the requested is resolved/closed. Before I go of and create a BPM process to store the owner of the request when the Response SLA is completed in a custom field, is this stored anywhere esle? i.e. who completes each timer? Cheers Martyn
  7. Hi We are currently looking to improve our incident business process. We utilise activities to capture why an incident has breached, using 6 outcomes (e.g. third party fix, delayed assignment etc.) and an additional "Reason" box to gather further info. Our current process is configured to allow the analyst to resolve a breached incident, prior to completing the breach activity. If the breach activity isn't completed, it will expire after a set time. The concern with this, is that the incident doesn't change from "Resolved" to "Closed" until after that breach activity is completed (the auto-close function is set to 5 days, therefore it won't close until the activity has been completed PLUS the 5 days). Is it possible - at the point the analyst presses "Resolve" after completing their resolution text/category - the system auto-generates a breach activity. This activity must then be completed by the analyst before they are able to resolve the incident fully. I am aware that at this point the actual resolution timers won't have been marked. If there was a mechanism to calculate whether or not at that point the fix time had been met, it could prompt the analyst as outlined above. This would also prevent the auto-close of the request (as mentioned above) being any longer than 5 days. I welcome any thoughts/suggestions with regards to this. Lauren
  8. Hi I have a service that is linked to two SLA's because one SLA follows a working day calendar so an 8 hour day for P3 priority calls and the second SLA follows a 24/7 calendar for P1 and P2 issues. When I now log calls for the service on a P3 is doesn't choose the right SLA. I have two questions, can you link a service to two SLA's? and why would it not follow the P3 SLA when selected? Thanks Chris
  9. Hi all, We have recently created a number of new Service Levels for 2019. We would now like to either delete or at least hide the old ones so they can no longer be used but we don't want all of our historic tickets to be left without a Service Level. Is there a way to do this?
  10. When printing the details of a request using the print icon, you get the options for content and timeline entries, but there is no mention of Priority/SLA. Priority, Service Level, Response/Resolution Targets and Values are not included at all. Can a new option be added to allow the inclusion of this crucial missing information. Cheers Martyn
  11. It would be useful to have the ability to copy an existing Service Level Agreement under the 'Services' section, rather than having to set them up from scratch each time. Cheers Martyn
  12. At the moment we only have a limited access to fields in order to specify SLM Service Level Agreement rules:- We would like access to additional fields, so that we can make the rules more useful and fit more users possible combinations Organisation Country Region (see linked post at the bottom) Industry Custom fields Customer Job Title Language Country Custom Fields Region (see linked post at the bottom) Request Service Summary Description Source External Ref No. Custom Fields Thanks Martyn
  13. When configuring SLA response and resolution targets and expiry times on certain BP nodes you might find the target being set differently than possibly expected. This is because a common oversight as these timers needs to be expressed in SLC (Service Level Calendar) times or working hours or business hours (which are usually X hours/day) rather than calendar time (which is 24 hrs/day). When configuring a target time of N days, the value needed to be set would be N working days rather than N calendar days. The value that needs to be set will be obtained by multiplying N with the number of working or business hours/day. We advise to always configure hours (rather than days) as it is easier to figure out the values required to be configured for SLA targets or expiry times on business process nodes. However, in certain areas (e.g. SLA timers), depending on the target, it might not be always possible to use hours exclusively. Below is a quick example of how to find out which values needs to be configured depending on the intended target: Let's say we need to configure a resolution time (or an expiry time) of 5 days. We need the target to be set in 5 days from now. Let's also say the working hours are 7.5 hours/day although this really depends on your SLC. Step 1 is to find out the number of working hours equal to the 5 days we need to set: 5 days * 7.5 hrs/day = 37.5 hours. You need to configure round values therefore if you don't have a round number of hours you also need minutes (seconds, etc.). The 37.5 hours equates to 37 hrs and 30 min. In conclusion, for a 5 day target, the configuration needs to be 37 hrs and 30 min. As mentioned above, for simplicity always use hours if possible. If you need to configure this value as days/hours/min then the 37.5 hours need to be divided by 24 (which is the number of calendar hours in a day) resulting in 37.5 / 24 = 1.56 days. The 1.56 days equates to 1 day and 13.50 hours. This further equates to 1 day 13 hours and 30 min. In conclusion: 5 day target in the context of 7.5 working hours/day is set as: 37 hours and 30 minutes or 1 day 13 hours and 30 min If you don't want to be bothered with the mathematical calculation, you can use this Excel sheet to find out what values you need to configure. Type in the desired target time and the number of working hours per day. The values you need to configure are in red: Hornbill_Timer_Targets.xlsx IMPORTANT: the above does not apply when configuring expiry times on human tasks. Human tasks do not account for Working Time Calendar and as such the above setup does not apply in this scenario.
  14. At the moment when you set up a SLA Escalation action such as send a reminder, only basic generic information is inserted into the timeline. It would be use to to include The Timer used , i.e. Response or Resolution. The target time value used, i.e. 2 hours before etc The escalation text used/ Board & List /Person Assigned The link to the email sent (when the Send Reminder action is used) At the moment these default to 'Team' visibility, which is fine for us at this time, but I can see where form some SLA/Customers you may want this to be 'Customer', so it would be good to have the option to set visibility of the timeline update on each individual escalation event. Cheers Martyn
  15. Hi, I have been asked to see if i can come up with a way to determine the average duration of incidents resolved over a given time period (the last 6 months) in minutes during working hours. Our Incident SLA timer for all priorities is fix within 9 hours 15 mins (8am to 5:15 pm) monday to friday. Our working time calendar is also set up for 8am to 5:15pm. Is there any easy way to do this in reporting? i need to be able to say "the average time to fix an incident during the period was ???? minutes" Any ideas? Thanks
  16. Heya, I've been testing the SLA escalation events with the email notifications and have a couple of issues: 1) Both the 'Summary' variable and the 'Subject' variable is all lower case when sent in the email 2) The 'Status' variable in the email template includes the full status name exactly as in the database. This means it says 'status.open' rather than 'Open' 3) Customer name variable comes across as blank Are these things that can be fixed?
  17. When linking multiple Service Level Agreements to a Service at the same time, the order they are selected is not honoured when they are inserted into the linked services list, but inserted in alphabetical order. This means you then have to then manually re-order them or add them individually in order. if they where added to the Linked Services list in the order they where selected, that would save these extra steps. Cheers Martyn
  18. Having a large number of Services and a growing number of different Service Level Agreements (SLA) where we need to add both different targets and escalation processes, it would really help save a lot of manual effort, it there was the ability to copy the Service Level Agreement setting from one Service to another or even better select a number of destination Services in one go. In terms of settings this would need to include linked Service Levels and the Rules. At the moment I updating about 40 Services where I am having to manually add each new Service Level Agreement and add the Rules, service by service, when the changes are identical for all the services in question. Cheers Martyn
  19. Along the lines of the Request List view you have under the Service option, it would be useful to have a Request List tab under the Service Level Agreements, which shows all requests linked to Service Level Agreement in question. Cheers Martyn
  20. Hi If I update a priority once a call is logged its doesn't change the SLA, i have to manually update the SLA, is that correct even though they are linked? Thanks Chris SLA.pdf SLA12.pdf
  21. Hi I'm see in the following error when resuming a call from paused, any ideas? 240556 2018-02-27 09:11:21 error perf 10852 apps:takeRequestOffHold() Method call results: failure (202137600 B, 461 ms, -2160 kB, 1 ms, 0 kB) 240555 2018-02-27 09:11:21 error scripts 10852 nodeName: Invoke Flowcode: Take response timer off hold; nodeId: 4b8db1a8-c819-4e8f-a86d-b91da1bc609d; At 307/1: "Uncaught EspMethodCall:invoke: Operation[apps/com.hornbill.servicemanager/Requests:takeResponseTimerOffHold] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold): Schema validation: Mandatory (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold/adjustedTime)" throw(e); _fc_node_exec_4b8db1a8_c819_4e8f_a86d_b91da1bc609d 240554 2018-02-27 09:11:21 error comms 10852 Operation[apps/com.hornbill.servicemanager/Requests:takeResponseTimerOffHold] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold): Schema validation: Mandatory (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold/adjustedTime) 240553 2018-02-27 09:11:21 error perf 9596 apps:takeResponseTimerOffHold() Method call results: failure (204374016 B, 112 ms, -64 kB, 0 ms, 0 kB) 240552 2018-02-27 09:11:21 error scripts 9596 nodeName: API Call: Query Timer; nodeId: 3d6f2ad2-d3f1-4646-8843-09e1e53cd6b6; "EspMethodCall:invoke: Operation[time:timerQuery] The specified timer [34215] was not found" 240550 2018-02-27 09:11:21 error comms 9596 Operation[time:timerQuery] The specified timer [34215] was not found 240548 2018-02-27 09:11:21 error perf 11044 time:timerQuery() Method call results: failure (206479360 B, 3 ms, -8 kB, 0 ms, 0 kB) 239427 2018-02-27 09:10:38 error perf 15428 apps:takeRequestOffHold() Method call results: failure (199073792 B, 379 ms, -40 kB, 0 ms, 0 kB) 239426 2018-02-27 09:10:38 error scripts 15428 nodeName: Invoke Flowcode: Take response timer off hold; nodeId: 4b8db1a8-c819-4e8f-a86d-b91da1bc609d; At 307/1: "Uncaught EspMethodCall:invoke: Operation[apps/com.hornbill.servicemanager/Requests:takeResponseTimerOffHold] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold): Schema validation: Mandatory (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold/adjustedTime)" throw(e); _fc_node_exec_4b8db1a8_c819_4e8f_a86d_b91da1bc609d 239425 2018-02-27 09:10:38 error comms 15428 Operation[apps/com.hornbill.servicemanager/Requests:takeResponseTimerOffHold] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold): Schema validation: Mandatory (com.hornbill.servicemanager/entities/Requests/fc_ops/takeResponseTimerOffHold/adjustedTime)
  22. Like 'Services' it would be useful to be able to group/filter Service Level Agreements by 'Service Category', as we use the category to differentiate between the different Service Desks we operate on the common platform. Cheers Martyn
  23. Hi First post of our new Hornbill era. So still learning! Trying to generate a graph for teams to show SLA's within fix, SLA's breached and ongoing tasks that are within the SLA but not yet resolved. I'm using the h_withinfix=0 and h_withinfix=1 parameters - however I cannot find a suitable 3rd measure which shows the number of "active jobs" that are still within the parameters of the SLA. Samples I've seen show the h_withinfix='' filter but this seems to duplicate the filter for h_withinfix=0. Any ideas?
  24. Automating SLA Selection For each service that you offer, you may find that you need to provide multiple Service Level Agreements. This video takes you through how Hornbill Service Manager works with SLA rules to automatically apply an appropriate SLA to each request. The Service Level Agreement Rules take away all the guess work that you have when manually selecting an SLA.  Rules can be built with a variety of conditions to ensure that the correct SLA is applied every time.    
  25. I am trying to create a widget that updates the average SLA times per team each month, I am aware I can do it as a measure and then put it into a widget however this will take me twice as long. Is there a way to create a widget so I can see the average SLA times for our p1, p2, p3 and p4 SLAS This is the SQL I have written so far: SELECT h_requesttype, h_dateresolved, h_resolvedby_team_id, h_status, h_fk_priorityname, h_withinfix, AVG(h_fixtime) as AverageResolveTime FROM h_itsm_requests WHERE h_fk_priorityname= 'p4' AND (h_status= 'status.closed' OR h_status= 'status.resolved') AND h_withinfix= '1' AND (h_dateresolved >= (CURDATE() - INTERVAL (Month(CURDATE())) DAY)) AND h_requesttype ='incident' GROUP BY h_fk_priorityname However I cannot get the Convert or Declare functions to work, I need to get a average resolve time (h_fixtime) result for all P4's in the month of December so far. However it is only giving me the average for the 06/12/2017 does anyone know what I can do so that it gives me a average resolve time for all p4's in December and for it to convert to HH:MM:SS instead of just seconds? Hayley.
×
×
  • Create New...