Faq And Best Practices; Faq - Bosch rexroth ActiveShuttle System Manual

9.6 FAQ and Best Practices

9.6.1 FAQ

1.1. Network availability
Q: What happens to an ActiveShuttle that loses its network connection for a short time? Can it still localize
itself? Will it resume a started Job when the network comes back up?
A: The ActiveShuttle will still be able to localize itself since the map is stored locally (it will not get map
updates from the server though). It will be able to drive a few more meters but will stop if it is not able to
connect to traffic management and reserve further Nodes. Once the network is back up, the ActiveShuttle
will continue to execute the Job it was carrying out before the breakdown.
Notice
Be aware that connection problems are often a local phenomenon, so the ActiveShuttle will likely not be
able to get itself out of the situation. The automatically created Wi-Fi Heatmap can help identify areas with
weak connection and get them fixed.
Q: Will I get an error e-mail sent when an ActiveShuttle goes offline? (All ActiveShuttles are needed to cover
the transport load. That means that if one ActiveShuttle is not available, the transport capacity is too low.)
A: In the current system configuration, no e-mail is sent for an ActiveShuttle going offline.
The system should not be operated at full capacity, as traffic jams, obstacles, charging times and unplanned
failures lead to overload.
Q: What happens to the Job currently being executed by the ActiveShuttle if the AMS becomes unavailable?
A: The ActiveShuttles will go to an error state waiting for the AMS to come back. When it is back up, the
ActiveShuttles will continue to execute the Jobs started before.
Q: What happens if an ActiveShuttle cannot confirm a received Job or provide status updates for Jobs or
other information to the AMS because:
• the AMS itself or a required Docker-Container is not reachable (error state)
• the network is not available?
A: The ActiveShuttle will make only one attempt to confirm a received Job to the AMS. If no confirmation is
delivered to the AMS, it attempts to assign the same Job to the ActiveShuttle again, the ActiveShuttle
recognizes the same Job and updates the Job status accordingly.
If the ActiveShuttle does not provide any updates regarding about Job progress, a warning will be issued in
the VMS logs (e.g., extractable in Kibana, but not available in the UI notifications), the Job will not be
discarded or terminated, but rather the AMS will wait for the ActiveShuttle to continue. If the ActiveShuttle is
reported as being offline, the Job will be returned to the FMS as unsuccessful autonomously.
As a matter of principle, all Jobs that could not be completed autonomously must be reviewed by a member
of staff. The issue should be resolved within the framework of such review and the Job should be marked as
manually completed or as a failure in the AMS UI. If the problem occurred before or shortly after the Source,
the identical (including identical external ID) Job can be triggered again in the UI.
Q: How long will the AMS wait for a Job update from an ActiveShuttle before it considers it as offline?
A: An ActiveShuttle is generally considered as offline if it does not transmit any messages for 3 minutes (not
only limited to Job updates). Once this time elapses, the Job is considered failed by the AMS. You then need
to define in the UI whether you finished the transport manually or revert it. Depending on the choice made,
the Job is marked either as manually successful or as failed to external systems.
RA91390962 AB-V1.3.3, en
Service | ILS, ActiveShuttle | 171