◆ Table of Contents
- What is the scheduling function?
- Two "termination rules" tailored to your operational style
- [Type A] Operations that involve staying in one place (greetings, reception, etc.)
- [Type B] Operations involving travel (patrols, inspections, etc.)
- Summary of setting rules by operating style
- Important Note: Regarding the "actual measurement" of the scheduled end time (Type B only)
- Let's move on to the next step .
◆ What is the scheduling function?
The scheduling function allows you to pre-book ugo processes on the ugo Portal and have ugo automatically execute them at set times.
Start automating ugo operations to meet your specific needs, such as "starting reception work at 9 AM every day" or "patrolling a fixed route at night."
◆ Two "termination rules" tailored to your operational style
The preparation process and the behavior upon completion differ significantly depending on the Flow that ugo executes.
First, please select which category your operation falls under.
| Item | [Type A] Operation that stays in place | [Type B] Operation involving movement |
| Main uses | Standing guard, greeting, reception, event promotion, AI automated conversation | Facility patrol and inspection |
| Key points for the settings | Complete the workflow on time. | Complete the Flow to the end. |
| Automatic shutdown settings | Available | Unavailable |
| Meaning of "end time" | The time to "end" Flow | This is merely an estimate of the "scheduled end date" for Flow. |
◆ [Type A] Operations that involve staying in one place (greetings, reception, etc.)
This operation involves repeating (looping) a flow of greetings and other verbal utterances without moving from a specific location (such as a charging station or reception area).
Features: Flow's "on-time departure" and smooth transition
Traditionally, if a Flow was running, it was difficult to stop it and execute the next scheduled Flow. Therefore, an operation such as "ending Flow1 at a specific time and then starting Flow2" required a "start position guarantee function."
This new "Stop at Flow end time" feature will make operations smoother.
Rules for settings:
On the schedule settings screen, check "Stop at Flow end date and time".
For secure operation, only Flows that meet the following criteria can be configured.
- Flows that do not contain commands of the command type "Move" or "ELV"
*If the "Call Flow" command is included, the target Flow will also be checked automatically.
- Flows that do not contain "Flow invocation" commands spanning four or more levels
The biggest advantage (continuous operation of Flow):
Because I can reliably complete Flow 1 (e.g., morning greetings) by 12:00, I can then schedule Flow 2 (afternoon work or charging/returning home) at 12:00, enabling seamless scheduling.
Behavior:
When the specified time arrives, the currently running Flow will be judged as "completed" and automatically terminate, and ugo will return to a clean state, waiting for the next scheduled Flow.
If the end time of Flow1 and the start time of Flow2 are set to be the same, it is also possible to operate in a way that seamlessly connects Flow1 to Flow2.
*The "Stop at Flow End Date and Time" function does not implement the process of returning ugo's arm posture, facial expressions, etc., to their default state after the Flow is completed.
Therefore, be sure to include the commands to return ugo's state to its default at the beginning of the Flow to be executed with the next scheduling function.
◆ [Type B] Operations involving travel (patrols, inspections, etc.)
This operation involves driving on a map and patrolling a predetermined route that passes through multiple locations.
For operations involving movement, "forced termination at a specified time" cannot be set for safety reasons.
Basic approach (aiming to finish movement):
Even after the scheduled "Flow end time" has passed, ugo will continue working on the task at hand (command) until it reaches a "safe place (the end point of the Flow)". If ugo were to suddenly stop in place when it reaches the scheduled end time during its run, it could block the path, obstruct pedestrians, or cause an accident.
Therefore, Type B prioritizes "safe completion" over "time".
⚠️ Note: If an error occurs, the program will stop immediately.
If the path is blocked by an obstacle or any error occurs during operation, the vehicle will stop immediately for safety reasons, regardless of the scheduled end time.
In this case, ugo will not automatically resume Flow or return to the charging station.
Either someone on-site manually returns the ugo to the charging station, or an operator remotely restarts the Flow process.
Operating schedule:
The "Flow End Time" set when registering a schedule is treated merely as an estimate (operational schedule) of "the time by which it is expected to finish." Even if the "Flow End Time" is exceeded, ugo will always attempt to complete the Flow by executing the final command (e.g., returning to charging) while checking the safety of the surroundings.
Therefore, for operations involving movement (Type B), it is necessary to set a schedule ("Flow End Time") with ample leeway.
This is similar to creating a bus timetable (operating schedule).
The start and end times set in the schedule represent an operating schedule such as, "This bus is scheduled to depart at 13:00 and arrive at its final destination at 14:00."
If the roads are congested and the bus is delayed past its scheduled arrival time of 14:00, the bus will not suddenly stop in the middle of an intersection or on a bridge by turning off its engine.
Even if it is running late, it will always continue on to its final bus stop.
◆ Setting rules by operating style: Summary
| Operation style | How to think about the end time | Accuracy of completion time |
| A: Greetings and reception | "Scheduled" termination of Flow (execute the command at the scheduled termination time to complete the process) |
High (because it stops in place) |
| B: Movement/touring | Continue until the Flow is complete (even if the end time is reached during the Flow, it will continue to run until the end). |
It fluctuates (depending on surrounding conditions such as the presence of crowds or obstacles along the route). |
◆ Notes: Regarding the "actual measurement" of the scheduled end time (Type B only)
ugo Portal does not have a function to automatically calculate and estimate the duration of the created Flow.
Therefore, the following preparations are essential when performing Type B: operations involving travel.
For Type B (with movement): Please be sure to take actual measurements.
For Flows that involve movement, you need to accurately estimate the [Flow End Date and Time] that you enter when registering the schedule.
Before registering the schedule, be sure to run the Flow from start to finish once and measure how many minutes it takes to complete one cycle using a stopwatch or similar device.
Arrival times will vary depending on whether there are no people or if it is crowded, due to obstacle avoidance and other factors.
To account for delays caused by crowds and obstacle avoidance, enter the time as the [Flow End Date and Time], adding a buffer of approximately 10-15 minutes to the actual time .
For Type A (no movement): Measurement is not required.
In Type A, since Flow is "forcefully terminated" according to the time, there is no need to measure the operating time of Flow.
Please enter the time that matches your business schedule, such as "The office closes at 18:00, so stop at 18:00," and then check the box for "Stop at Flow end time."
◆ Let's move on to the next step.
Let's review the specific setup procedures based on your operational type.
- Schedule Function Guide: [Type A] Operations that require staying in one place (greetings, reception, etc.)
- Schedule Function Guide: [Type B] Operations involving travel (patrols, inspections, etc.)
- Schedule Function Guide: [Practical Guide] Automating ugo Operation by Combining Greetings and Patrols