Operational Resource Plan to track actual hours and costs for incidents / changes

[Luis Ataide]

Operational Resource Plan to track actual hours and costs for incidents / changes

This article describes best practice to track actual hours and costs for operational work (incidents / changes) leveraging Operational Resource Plans. 

This use case is based on the use of Timesheet Portal and Timecards, not Time Worked.

1 - Create operational resource plans to allocate people to operational activities (in this case, KTLO)

      For more details about Operational Resource Plan, please refer to this article:  Operational Resource Plan - All That You Need to Know

2 - When user is entering time to an incident/change request, select an available operational resource plan (operational resource plan on which the user is allocated and covering the timesheet week)

3 - The time card is associated to the Incident and operational resource plan. View from operational resource plan form:

4 - Once the time card is approved:

      4. 1 - Actual hours and actual costs roll up to resource allocation

     

      4.2 - Actual hours and actual costs roll up to the operational resource plan

     

[mikereaves]

Great Article Luis, thanks.

I have another question along these lines....

My client would like his employees to enter hours against operational resource plans, however I've noticed that until a time sheet is submitted, additional entries can't be made for work types that are already on the sheet.

For example:
User works 8 hours on Monday for KTLO resource plan RPLN00001.
User works 8 hours on Tuesday for KTLO resource plan RPLN00002.
The user is allocated on both (operational) resource plans.

It appears that the Time Sheet portal will not allow a user to make a second KTLO entry on their timesheet until it is submitted.  For a user who needs to report time against 5 different KTLO operational resource plans - that's a lot of clicks.  Why is this.  Is there a way around this.  Am I missing something.

Any comments would be greatly appreciated.

[Ryan S]

Hi @Luis Ataide, do you have a similar article that covers the use case of using the time_worked field for operational tasks?