Durations For Activities Need To Be Estimated By Task Type. (Doc ID 3077487.1)

Last updated on MARCH 18, 2025

Applies to:

Goal

1. Regarding the functionality of the OFS / CCS Accelerator 24B (CCS-OFS integration) that the Energy and Water Division currently supports.

The duration of an activity needs to be known so that OFS routing can plan an efficient route for the technician. In OFS the duration is defaulted to a value that is configured in the task type table if the duration is not passed down to OFS from the host system.

It was noticed that the admin sync logic is passing down the activity type info to OFS but is not distinguishing duration or any other attributes on the basis of task type, so each task type default duration in the task type table seems to get the same value, which is not useful.

Currently they are seeing that the duration being passed to use from CCS seems to be a default value which is the same for every task type and not useful for OFS because it does not reflect the differences in duration based on task type.

Would like to see:

OFS needs to get a duration based on the task type that the activity is associated with.
It can be done in two different ways, I think.
Either getting a duration in minutes from the accelerator that accurately reflects the different potential duration based on task type or not getting a duration at all and OFS will used the default duration that is in the task type table in OFS....but if doing this it would be needed to enhance how the accelerator creates the task type tables in OFS via the admin sync which does not set duration correctly. It uses a DVM that sets all of the task type attributes the same. there is a need to change this.

Could you please assist ?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.