What can RTLS track without automating the equipment?
For carts and other unpowered equipment, a common approach is to attach a small wireless tag. Receivers installed around the site detect its signals, and location software calculates where the tagged asset is. The cart keeps its existing function; an employee can still push it between workstations.
Manually operated forklifts can also be tracked. Depending on the selected system, this can use tags or vehicle-mounted sensors. Laser-based systems, for example, locate a forklift against a map of its surroundings. The driver continues to operate the vehicle; the additional equipment makes its position available to software.
The table shows which information is useful for each asset.
| Asset | What tracking helps the site establish | What the operating process can do with that information |
|---|---|---|
| Cart or trolley | Which area it is in and how long it has been there | Find it, reserve it for a job or arrange collection |
| Manually operated forklift or pallet truck | Its current position and movement history | Combine location with availability and assign a suitable transport job |
| Reusable carrier or container | Its identity and location between workstations | Follow its progress and organise the next handover |
The last column requires more than a location feed. A cart's position does not establish that it is empty. A forklift's position does not establish that its driver is available. Those facts need to come from the task system, an operator confirmation or another connected source.
How do BLE, UWB and Wi-Fi RTT locate carts and forklifts?
Bluetooth Low Energy (BLE) and ultra-wideband (UWB) are two radio technologies used to locate tagged equipment. Both can make the position of a cart or a manually operated forklift available to the software coordinating the work. Neither makes that equipment autonomous.
The choice starts with a practical question. Is it enough to know which area an asset is in, or must the system distinguish between neighbouring pickup positions?
Locating equipment by area or position with BLE
A BLE tag attached to a cart sends out a wireless signal containing its identifier. Fixed receivers detect that signal and pass the observations to the location software.
Basic BLE tracking uses signal strength to estimate proximity or identify an area. For example, it can help establish whether a trolley is near packing or dispatch. Signal strength is not a direct measurement of distance. Racks, loads and other obstructions can affect the reading.
BLE direction finding adds a different method. Compatible tags transmit signals that receivers with multiple antennas use to estimate the direction from which the signal arrives. This is called angle of arrival. A system built around these measurements can provide more detailed positioning than basic signal-strength tracking, but it needs the appropriate hardware and installation.
“BLE tracking” therefore does not describe one fixed level of accuracy. Ask which method the proposed system uses and whether it can reliably distinguish the areas relevant to your process.
Locating equipment through signal timing with UWB
A UWB tag sends very short radio pulses. Fixed devices known as anchors are installed at known positions around the site. The location system uses timing measurements, such as differences in when the same signal reaches several anchors, to calculate the tag's position.
UWB is worth considering when the workflow needs a more precise position than basic proximity tracking can provide. An example is distinguishing whether a cart is at one pickup bay or the next, rather than merely somewhere in dispatch. The required accuracy must still be checked at those locations.
Anchor placement, tag mounting and obstructions matter. A tag on the exposed edge of a cart can have different visibility from one hidden behind a metal load. Location updates also need to arrive frequently enough for the movement being tracked.
Measuring distances with Wi-Fi RTT
Wi-Fi RTT (Round-Trip Time) is another positioning option. It measures signal travel time between a compatible device and RTT-capable Wi-Fi access points to determine distances. Measurements to multiple access points at known locations can be used to calculate a position. Both the devices and access points need RTT support; an existing Wi-Fi network alone is not enough.
Feeding location technologies into SyncroBot
With the relevant interfaces connected, BLE, UWB and Wi-Fi RTT location data can feed into the same SyncroBot workflow. The location system supplies the asset identity, its position or zone, and the time of the observation. SyncroBot can combine that information with task status and robot availability to coordinate the next movement.
A cart tracked through BLE and a forklift tracked through UWB can therefore be represented alongside robots in one operating view. Their identifiers and locations must be aligned, but the site manager should not need separate processes simply because the tracking technologies differ. A location update still needs a readiness or completion signal before it can release the next job.
How does tracking become one orchestration system?
A tracking screen answers “Where is it?” An orchestration system also answers “What should happen next?”
The connection brings together three kinds of information, namely locations from RTLS, operating status from robots and manual tasks, and transport demand from the business process. That demand might come from a warehouse management system (WMS), an enterprise resource planning system (ERP), a button or an employee's request.
RTLS data reaches the platform through a software connection, often called an application programming interface (API). For example, published RTLS interfaces allow other software to receive live positions and use defined areas, such as a packing pickup zone, in its own workflow. The tracking supplier provides the location feed; the orchestration system uses it to make task decisions.
SyncroBot's published platform capabilities include shared operational maps, task assignment, route planning and transport requests triggered manually or by sensors. These provide the robot-management side of a combined workflow. The RTLS feed, driver instructions and completion signals need to be included in the agreed project scope.
Managing a manual asset means managing its work, not making it autonomous. A robot receives a task through its supported control connection. A forklift driver can receive a job through a connected terminal or application and confirm completion. A cart is reserved or assigned for transport; it does not receive a driving command. Digital task assignment for human-operated forklifts is an established approach to managing mixed manual and automated transport.
What would this look like during a normal shift?
Consider a process in which packing staff prepare goods, a robot moves them to dispatch, and a forklift driver completes the final movement. The following is an illustrative workflow, using a pallet-bearing cart designed for both robot transport and forklift unloading.
Packing releases a cart
An employee places a pallet on the cart and moves it into the collection area. RTLS reports the cart's identity and position. A scan or operator confirmation links the pallet to that cart and marks the load ready.
The shared workflow now has the information needed for collection, including which load is ready, where it is and where it must go. Merely passing through the collection area would not release a transport task.
A robot performs the repeated transport
The platform assigns a compatible robot to collect the cart and take it to dispatch. It checks that the receiving position is available before releasing the movement. The employee does not need to walk to a separate robot terminal and enter the job again.
When the robot has delivered the cart and completed its handover, the same workflow advances to the next step.
A forklift driver completes the manual movement
The platform issues the next job through the connected driver interface. The driver is asked to collect the pallet from the dispatch handover point and take it to the required destination.
The assignment takes account of a suitable forklift, an available driver and the task priority. RTLS helps locate the vehicle; it does not replace those availability checks. The driver accepts the job, moves the pallet and confirms delivery.
The empty cart returns to work
Once unloading is confirmed, the cart can be marked empty and released for return. A robot or employee then moves it back to packing, according to the configured process.
The site manager follows one sequence from preparation to delivery and return. Each stage has a clear status and an assigned resource, even though some movements are manual and others are automated.
What can a site manager optimise in one place?
Finding and reusing equipment
Instead of asking several departments where a cart was left, staff can look up its latest position. Combined with its recorded empty or loaded status, that helps identify equipment available for the next job. It also makes it easier to distinguish a shortage of carts from carts waiting in the wrong area.
Assigning work across the whole operation
When manual vehicles and robots share task information, allocation can consider both. A repetitive floor-level movement may suit a robot, while a different load or destination requires a forklift driver. The choice should reflect capability, availability and priority, rather than simply sending whichever vehicle is closest. Digital forklift guidance systems use task assignment and scheduling to support this kind of mixed operation.
Reducing waiting and unnecessary journeys
Location histories can show where vehicles spend time and how material moves between areas. When combined with task and load records, they can help distinguish productive transport from empty travel or waiting. The benefit comes from acting on those findings by changing collection priorities, matching return jobs or coordinating arrivals at a busy handover point.
For example, a dispatch buffer that is already full should not receive another robot delivery merely because a robot is free. A shared workflow can hold that request until the receiving stage has capacity. This is a process rule to configure, not an automatic consequence of attaching tags.
Understanding whether more robots are needed
A completed-transport record should cover the whole movement, including the manual stages. Consider a robot that waits for packing to release its next load, then waits again for a forklift to clear dispatch. Adding another robot would not remove either delay. The combined view helps the manager decide whether to change staffing, handovers, priorities or transport capacity.
What has to be connected for this to work?
The systems need to agree on asset identities, operating locations and task status. The cart shown at “Packing 2” in RTLS must correspond to the same cart and pickup point in the transport workflow. Tracking maps may need to be aligned with the site's existing map; localisation products provide facilities for this kind of alignment.
Keep location and readiness separate. A useful asset record combines the latest position and its observation time with the relevant work status, such as available, assigned, being moved or awaiting unloading. The contents of a cart must also be associated with that cart through the process, rather than inferred from the tag alone. When a location update becomes too old, the system should show that uncertainty instead of silently treating it as current.
The driver interface is equally important. Manual jobs need a way to be accepted, completed or reported as blocked. Those updates allow the next robot movement to start at the right point. The WMS and ERP integration guide explains the same principle for connecting physical work to business-system records.
A shared orchestration layer also provides a platform for reusing business-system and process integrations. Adding a compatible robot or another tracked asset need not mean rebuilding the WMS or ERP interface. New equipment connections and changed process rules still need configuration and testing, as explained in the deployment cost guide.
Where to start with SyncroBot
Start with one process that already includes both manual and robotic work, such as moving carts from packing to dispatch, replenishing a production station or returning empty carriers. Define the equipment involved, the handover points and the signals that confirm each stage is finished.
For a SyncroBot project, that can mean one robot working with a small group of existing manual assets. Connect the relevant location data and manual-task updates, then extend the workflow to more vehicles, areas and processes over time. There is no need to make every cart or forklift autonomous before bringing it into the same operating view.
The starting question is practical. Where does the transport process currently lose track of an asset, wait for a handover or require someone to re-enter a task? That is the connection to build first.
Location tracking and task coordination do not by themselves provide a safety-rated collision-prevention function. The mixed-traffic safety concept and protective measures must be assessed separately for the site and equipment.