Unassigned loops notification

[sync-by-unito[bot]]

Which platform is this for?: Command Centre

• Is this improvement to an existing feature in the platform or a new feature?: New Feature - something that does not yet exist on the system

What problem is this feature or improvement solving?: On command centre, under "trips", because loops that not linked to an operator still have to be manually assigned, operations has to be notified of unassigned loop to eliminate incidents where trips are not fulfilled.

Please describe the feature you want and how you see it working.: Similar to the "ops-unassigned-charters" slack channel. Any (loop) trips that has not been assigned after a period of time should be flagged and then come through a slack channel that would notify the operations team. Ideally the notification would come through 4 hours after the loop's cut off time. (Please note that the time frames might need further discussion)

Please rate the urgency of this feature request/improvement:: Should have, for effective use of the platform.

What positive impact will having this feature have to LULA and our users?: The feature will prevent any (loop) trips from being missed. Similarly to how the "ops-unassigned-charters" slack channel prevents any charter from being missed.

Feature Requested by:: Mushra Hartley

┆Issue is synchronized with this Clickup task by Unito

[sync-by-unito[bot]]

➤ Xabiso Nodada commented:

@Nate Noels @Mushra Hartley I'm going through the comments and feedback. I need some clarity to fully understand the problem we are trying to solve. I'm going to summerise my understanding below

It seems to me that there two problems or use cases to solve here for unassigned loops. Use Case 1: The loops are for organisations linked to LULA logistics Use Case 2: The loops are for organisations linked to one of our operator partners @Mushra Hartley as the Ops Team you want to have visibility when trips have not been assigned and you want to be notified about these trips when they have not been assigned after they have been generated.

Am I correct in my summary so far?

[sync-by-unito[bot]]

➤ Mushra Hartley commented:

Hi @Nate Noels checking in if any more info is required following my last feedback?

[sync-by-unito[bot]]

➤ Mushra Hartley commented:

Good Morning. Independent drivers who are not linked to an official operator are listed under LULA logistics as an Operator.

In order to ensure distribution of work between independents and bigger operators we assign some loops to independent drivers and this rotates. eg. Raw Foods, Allan Grey etc. There are also loops created for events that are signed to LULA Logistics drivers.

So even though an operator is linked to a loop, manual assignment is required.

Would assigning the Org default operator to all unassigned loops not resolve this issue? This is an automated way of resolving this issue. - Please demo this so I can answer

Is this feature request supporting a manual process, if yes, is the frequency of this action enough to build for a manual process? - Yes and Yes

I believe a session is needed

[sync-by-unito[bot]]

➤ Nate Noels commented:

@Mushra Hartley Please advise on the above solution and if it will work. It aligns more with building automation instead of manual processes. Please advise.

@Joël Samuel Kapepula please note the feedback above. If agreed this becomes an Organisation dashboard ticket.

[sync-by-unito[bot]]

➤ Nate Noels commented:

Hi @Mushra Hartley When a loop is created, does the process not include assigning an operator?

Would assigning the Org default operator to all unassigned loops not resolve this issue? This is an automated way of resolving this issue.

Is this feature request supporting a manual process, if yes, is the frequency of this action enough to build for a manual process?

Please respond or setup a session to discuss this further.