Hi,

This mapping will not happen all the times. I assume the PSO Activity is allocated. At this stage, allocation details are recorded in DSE_ALLOCATION table if DSE broadcast is enabled, but TASK table won’t be updated with this data. Therefore, FSM TASK status will be Open.
After the activity is committed, FSM task status will update accordingly to PSO task status (say accepted, in progress etc.). Also, manual changes done at allocation stage (say datetime fix or resource fix) will change the FSM Task Status according to the status mapping in TASK_STATUS table. This is because manual changes are going to FSM as SWB broadcasts, not DSE broadcasts.
 

Regards,

Sajith

Thank you for your reply. 

Is the DSE_ALLOCATION table supposed to be updated continously? We’re currently experiencing that the table has not been updated for 5 days, and seems like there is a large gap between the updated intervals. 

If you need to enable this, give DSE_BROADCAST_ENABLED Scheduling App Param as “Y’.

Update interval will be determined from MAXIMUM_FREQUENCY scheduling app parameter.

Enabling DSE broadcast have a performance impact in FSM side. So the frequency should be determined in a manner that FSM performance is not impacted.

Thanks for all the answers for this question. We have a plan in PSO with lots of allocations. When we enabled DSE_BROADCAST_ENABLED all these allocations was removed from PSO. What can cause this behavior?

I don’t think it is due to enabling the DSE Broadcast. Check in the PSO event log whether you are seeing any DSE Optimization errors.

Follow up question, is enabling DSE_BROADCAST_ENABLED starting additional processes in PSO? Or is it just enabling the broadcast to FSM?

Obviously it is more work to Broadcast Manager of PSO, since the DSE plans are broadcasted.

Ok, so it should not alter the plans in any way?

No. It should not. It is just communicating what DSE has provided.

I am not able to check the event log, since this happened some weeks ago. But another theory, when DSE updates FSM, could some data fra FSM sent back to PSO be the reason for all the soft allocated tasks being removed in PSO?

Anyone has any input here? What could be sent from FSM that overwrites what PSO has already planned?

we have the same problem since may 2022 and up to now no solution from IFS. Opened a support case today. If some news i like to post,

Hey @Sajith Anushan  ,

I am having the same problem. Can you clarify on what you meant that DSE Broadcasts would not update the FSM task ? 

We are getting the DSE Allocation received, and we are getting the Scheduling output history also being received by FSM. We have the task status workflow and app params already aligned. 

But indeed, what happens here is what you mentioned about only after we change to Accepted in PSO manually , it will change the status of the Task in FSM to “Assigned.” 

Therefore my question is , if we are using FSM to manage the tasks and not the PSO but its optimization, if PSO is making allocations we receive the DSE allocations and updates on the DSE_Allocation table in FSM but the status in FSM does not changed to allocated or even Assigned.

Is this the correct behaviour ? is this a technical limitation ? 

When we receive the DSE allocation, should not the status in FSM go to the corresponding Allocated status in FSM defined on the Task status Code Table?

Hi @FredericoM - 

From FSM6 UPD6 onwards, FSM Task table is not updated with content of the DSE broadcast. Allocation details can be changed by DSE over time so in general, when FSM should know about the allocation is at the point it would dispatch to technician. Updating FSM Task table with each and every DSE broadcast may have performance implications too and that is why it is changed.

But I agree that there can be requirements to update Task table with DSE broadcast. I have seen plenty of customers who are having this requirement. In such cases, you can implement a Business Rule to get the changes in DSE_ALLOCTION table and update the TASK table.