FAQ - Automatic update of generated logistic needs to a path

The automatic generated logistic needs consider the defined paths on Drake. However, not all the automatically generated needs attendances will be served by the suppliers exactly as requested.

Drake is capable of identify those generated differences while the attendance and spread this information to the generated subsequent needs for a path. Below an example of this explanation.

Example: Changing destination airport of a generated need for a path that has car travel on the sequence.

Drake initially generated automatically two logistic needs for the worker (an airplane from X to Y and a car from Y to Z).

When requesting for flight transportation, the requester informed specifically the destination airport being “Y”, however there was not an available flight from “X” to “Y”. Instead, a flight from “X” to “W” (a different airport in the same region).

If the supplier attends and informs the destination airport as “W”, Drake will automatically update the car need from “W” to the final destination (the city the worker will stay to perform a duty). However, the supplier can only make this update if the car need is with status “Informed”. If the need is Confirmed, Drake will adjust only the time of arrival. On other statuses, Drake will not perform any changes on car need.

Important Observation:

Drake will automatically update the needs only if it has been automatically created by Drake itself.

Besides, if an user has done any changes on needs schedule after automatically creation, Drake will not update the schedule if, as an example, the previous attendance of a need has a different scheduled time than customer requested to supplier.