Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
971 views

Time (date and time) within HPSM Change

Jump to solution

Good afternoon team,

I'm new to HPSM and I have very little experience in working with the product. I was wondering if someone could help or point me in the right direction on an issue that I'm currently having.

I have a task of creating a template that will open and have the requested end time 24 hours after the open time.

This may be simple but I'm new to the entire process. Thank you in advance for any and all help.

0 Likes
1 Solution

Accepted Solutions
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Time (date and time) within HPSM Change

Jump to solution

Dear Sir/Madam,

 

My understanding here is that you would like to create a calculation time that will let the ticket opened for 1 hour, longer than that, the ticket will be breached. My suggestion here is to use SLA module for your requirement. The dcument below is for you to refer how SLA works and how to set up the SLA in Change module.

 

Example: Enabling Service Level Agreement alerts

The following example shows you how to generate response Service Level Targets (SLTs) for Change Management requests and to generate alerts for SLTs. At the end of this example, you will be able to complete the following tasks:

  • Create a Service Level Agreement (SLA)
  • Add a Service Level Target (SLT)

Note: To enable Service Level Agreement alerts for Change Management, you must perform the entire sequence of example tasks. You must be a System Administrator, or have equivalent system privileges, to perform tasks 1 through 7.

Task 1: Ensure the background processes are running

  1. Click Menu Navigation > System Status.
  2. If the processes are not running, click Start Scheduler.
  3. In the Name field, double-click startup to start all the background processes.

Task 2: Enable the SLM application

  1. Click Service Level Management > Administration > Edit Control Record.
  2. Select Enable SLM Application.
  3. Click Save.
  4. Log off Service Manager, and then log back on for the changes to take effect.

Task 3: Configure Change Management

  1. Click Service Level Management > Administration > Configure Application.
  2. In the Table Name field, type cm3r, and then click Search.

    The SLA module control form for cm3r opens. Ensure the Enable SLM in this application check box is selected.

  3. Select Run in Foreground.
  4. Click Save.
  5. Click OK.

Task 4: Create an SLA

  1. Click Service Level Management > Agreements > New Agreement.
  2. Click Service Level Requirement.
  3. In the Type field, select the contract type Customer.
  4. In the Customer field, select a customer name from the list of records.
  5. In the Title field, type SLA for change requests.
  6. In the Effective From field, choose today's date in the calendar options for the SLA start date.
  7. In the Expiration Date field, choose a date one year from today in the calendar options for the SLA end date.
  8. Add an optional Description for the new SLA.
  9. Click Save.

    You receive a message that states the service level agreement has been added. Service Level Management assigns an Agreement ID number to the record. Make note of the new agreement ID.

  10. Click Review to move the record into the Review phase.
  11. Click the Agreed By tab and specify the people who agreed to the SLA.
  12. Specify appropriate values for the Next Agreement Review Date, Service Review Frequency, and Next Service Review Date fields.
  13. Click Agree to move the record into the Agreed phase.

    The category of the SLA is moved from Service Level Requirement to Service Level Agreement.

  14. Click Save or Save&Exit.
  15. Log off Service Manager, and then log back on to see that the new SLA is available in the selection lists.

Task 5: Add an SLT

Note: You can add a service level target immediately after you add a service level agreement, or you can add it later.

  1. Click Service Level Management > Agreements > Search Agreement.
  2. Type the Agreement ID, and then click Search.

    The SLA record opens.

  3. In the Process Targets tab, click Add SLT(s).
  4. In the Service Area field, select Change Requests, and then click Next.
  5. Fill in the following fields to add the SLT. Make sure you click Next, as required.

    Field Value
    SLT NameResponse SLT for change requests
    DescriptionAdd an (optional) description.
    Schedule24x7
    Priority1-Critical
    CategoryDefault
    Initial StateRegistration and Categorization
    Final StateClosure
    Duration TypeInterval
    DurationThe format should be DDD HH:MM where DDD is the number of days, HH is the number of hours, and MM is the number of minutes. Type 00 01:00
    AlertsClick Fill, and then select SLA-50% from the list of records.
  6. Click Finish.

    You receive a message that states a record has been added to Process Target. Make sure the record is displayed in the Process Targets tab.

  7. Click OK.
  8. Log out, and then log in again for your changes to take effect.

Task 6: Select the SLA definition for an ESS user

  1. Click System Administration > Base System Configuration > Contacts.
  2. In the Contact Name field, type the user's name, and then click Search.

    The user record opens.

  3. Place your cursor in the Dept Name field, and then click Find.

    The department data form opens.

  4. In the SLA field, select an SLA definition. For this example, select SLA for change requests.
  5. Click Save.
  6. Click OK.

Task 7: Service Desk Agent creates a change from a user interaction

As a Service Desk Agent, you can escalate an interaction to a change record.

To create a change request from a user interaction, follow these steps:

  1. Click Service Desk > Interaction Queue or select Interaction from your To Do queue.
  2. From the record list, double-click the Open-Idle interaction that you want to escalate to a change.
  3. Click Fill for the Category field.
  4. Double-click Request for Change and select the subcategory.
  5. Click Escalate. The Escalation Details wizard appears.
  6. Click the list fields to select the Location, Assignment, and Requested End Date for the change.

    Note: A Change Coordinator is automatically assigned based on your selections.

  7. Click Finish. A notification message with the change number displays above the interaction detail fields and the Service Desk application notifies the original end user of the actions taken.
  8. Click OK.

Task 8: Change Coordinator goes to the change queue to review the upcoming alerts

After the Service Desk Agent escalates an interaction to a change, the change request moves to the Change Review phase. The Change Coordinator can then review the change request.

The Change Coordinator reviews the SLA and the Process Targets associated with the change. For this example, the duration was 1 hour, and the alert was 50%. The alert is 30 minutes from the time displayed on the Open Time in the History section.

  1. Click Change Management > Changes > Change Queue.
  2. From your To Do queue, select Change from the Queue list and My Open Changes from the View list.
  3. Expand Phase: Change Review from the record list, and then click the change request to review it. Determine if it is complete and verify that the change is assigned to the correct support group. If more information is needed or the support group is incorrect, send the request back to the Service Desk Agent.
  4. Open the SLT section. The new SLA definition is displayed.
  5. Select the Upcoming Alerts subsection in the SLT section. the listed alert should be 30 minutes from the time displayed in Open Time, in the History section.

    The duration was one hour and the alert was 50%.

"

Hope it helps!

 

Thank you and Best regards,

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.

View solution in original post

1 Reply
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Time (date and time) within HPSM Change

Jump to solution

Dear Sir/Madam,

 

My understanding here is that you would like to create a calculation time that will let the ticket opened for 1 hour, longer than that, the ticket will be breached. My suggestion here is to use SLA module for your requirement. The dcument below is for you to refer how SLA works and how to set up the SLA in Change module.

 

Example: Enabling Service Level Agreement alerts

The following example shows you how to generate response Service Level Targets (SLTs) for Change Management requests and to generate alerts for SLTs. At the end of this example, you will be able to complete the following tasks:

  • Create a Service Level Agreement (SLA)
  • Add a Service Level Target (SLT)

Note: To enable Service Level Agreement alerts for Change Management, you must perform the entire sequence of example tasks. You must be a System Administrator, or have equivalent system privileges, to perform tasks 1 through 7.

Task 1: Ensure the background processes are running

  1. Click Menu Navigation > System Status.
  2. If the processes are not running, click Start Scheduler.
  3. In the Name field, double-click startup to start all the background processes.

Task 2: Enable the SLM application

  1. Click Service Level Management > Administration > Edit Control Record.
  2. Select Enable SLM Application.
  3. Click Save.
  4. Log off Service Manager, and then log back on for the changes to take effect.

Task 3: Configure Change Management

  1. Click Service Level Management > Administration > Configure Application.
  2. In the Table Name field, type cm3r, and then click Search.

    The SLA module control form for cm3r opens. Ensure the Enable SLM in this application check box is selected.

  3. Select Run in Foreground.
  4. Click Save.
  5. Click OK.

Task 4: Create an SLA

  1. Click Service Level Management > Agreements > New Agreement.
  2. Click Service Level Requirement.
  3. In the Type field, select the contract type Customer.
  4. In the Customer field, select a customer name from the list of records.
  5. In the Title field, type SLA for change requests.
  6. In the Effective From field, choose today's date in the calendar options for the SLA start date.
  7. In the Expiration Date field, choose a date one year from today in the calendar options for the SLA end date.
  8. Add an optional Description for the new SLA.
  9. Click Save.

    You receive a message that states the service level agreement has been added. Service Level Management assigns an Agreement ID number to the record. Make note of the new agreement ID.

  10. Click Review to move the record into the Review phase.
  11. Click the Agreed By tab and specify the people who agreed to the SLA.
  12. Specify appropriate values for the Next Agreement Review Date, Service Review Frequency, and Next Service Review Date fields.
  13. Click Agree to move the record into the Agreed phase.

    The category of the SLA is moved from Service Level Requirement to Service Level Agreement.

  14. Click Save or Save&Exit.
  15. Log off Service Manager, and then log back on to see that the new SLA is available in the selection lists.

Task 5: Add an SLT

Note: You can add a service level target immediately after you add a service level agreement, or you can add it later.

  1. Click Service Level Management > Agreements > Search Agreement.
  2. Type the Agreement ID, and then click Search.

    The SLA record opens.

  3. In the Process Targets tab, click Add SLT(s).
  4. In the Service Area field, select Change Requests, and then click Next.
  5. Fill in the following fields to add the SLT. Make sure you click Next, as required.

    Field Value
    SLT NameResponse SLT for change requests
    DescriptionAdd an (optional) description.
    Schedule24x7
    Priority1-Critical
    CategoryDefault
    Initial StateRegistration and Categorization
    Final StateClosure
    Duration TypeInterval
    DurationThe format should be DDD HH:MM where DDD is the number of days, HH is the number of hours, and MM is the number of minutes. Type 00 01:00
    AlertsClick Fill, and then select SLA-50% from the list of records.
  6. Click Finish.

    You receive a message that states a record has been added to Process Target. Make sure the record is displayed in the Process Targets tab.

  7. Click OK.
  8. Log out, and then log in again for your changes to take effect.

Task 6: Select the SLA definition for an ESS user

  1. Click System Administration > Base System Configuration > Contacts.
  2. In the Contact Name field, type the user's name, and then click Search.

    The user record opens.

  3. Place your cursor in the Dept Name field, and then click Find.

    The department data form opens.

  4. In the SLA field, select an SLA definition. For this example, select SLA for change requests.
  5. Click Save.
  6. Click OK.

Task 7: Service Desk Agent creates a change from a user interaction

As a Service Desk Agent, you can escalate an interaction to a change record.

To create a change request from a user interaction, follow these steps:

  1. Click Service Desk > Interaction Queue or select Interaction from your To Do queue.
  2. From the record list, double-click the Open-Idle interaction that you want to escalate to a change.
  3. Click Fill for the Category field.
  4. Double-click Request for Change and select the subcategory.
  5. Click Escalate. The Escalation Details wizard appears.
  6. Click the list fields to select the Location, Assignment, and Requested End Date for the change.

    Note: A Change Coordinator is automatically assigned based on your selections.

  7. Click Finish. A notification message with the change number displays above the interaction detail fields and the Service Desk application notifies the original end user of the actions taken.
  8. Click OK.

Task 8: Change Coordinator goes to the change queue to review the upcoming alerts

After the Service Desk Agent escalates an interaction to a change, the change request moves to the Change Review phase. The Change Coordinator can then review the change request.

The Change Coordinator reviews the SLA and the Process Targets associated with the change. For this example, the duration was 1 hour, and the alert was 50%. The alert is 30 minutes from the time displayed on the Open Time in the History section.

  1. Click Change Management > Changes > Change Queue.
  2. From your To Do queue, select Change from the Queue list and My Open Changes from the View list.
  3. Expand Phase: Change Review from the record list, and then click the change request to review it. Determine if it is complete and verify that the change is assigned to the correct support group. If more information is needed or the support group is incorrect, send the request back to the Service Desk Agent.
  4. Open the SLT section. The new SLA definition is displayed.
  5. Select the Upcoming Alerts subsection in the SLT section. the listed alert should be 30 minutes from the time displayed in Open Time, in the History section.

    The duration was one hour and the alert was 50%.

"

Hope it helps!

 

Thank you and Best regards,

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.