Mobile robot operations

Send eligible warehouse missions to the right robot fleet.

Ysend turns eligible warehouse work into robot missions under your rules, overlays live fleet state on warehouse maps and reconciles outcomes. The fleet manager and robot controller still own paths, braking and safe motion.

Review a fleet workflow

Mission intake

Start with work, not with a robot queue

A pick, move, replenishment or cell handoff becomes a mission only after location, inventory, resource and reservation checks.

Warehouse demand

The operational workflow identifies a physical move and its custody context.

Mission generation

Eligibility, priority and reservations determine each mission request.

Fleet resolution

Site, device binding and adapter capability select the target fleet path.

Controller acceptance

The external fleet controller accepts, rejects or schedules motion under its own safety rules.

Map and traffic

A live operational overlay, not a replacement navigation engine

Pose and mission state

Live positions, current mission, handoff state and alarms are shown on the warehouse map.

No-go zones and traffic rules

Maps, no-go zones, reconciliation and traffic constraints guide mission eligibility and operator decisions.

Charging and availability

Charging, readiness and fault state help prevent dispatch to an unavailable resource.

Fleet resolution

Protocol coverage carries an explicit maturity label

Dedicated paths

E300, HeLi HSAS and HRCS, SL100D2, VDA 5050, OKAGV ACI, SEER RDSCore, MiR and Reeman are represented by dedicated adapter paths.

Deployment evidence

A software adapter is not a live-site certification. Model, firmware, credentials, network and vendor test results are reviewed per fleet.

Simulation

The simulated adapter supports development and reference testing only; it is never listed as a physical fleet integration.

Legacy view

The legacy AMR task queue is a compatibility surface, not the current mission authority.

State handoffs

Every transition names the system that confirmed it

  1. Requested Ysend has issued intent

    No robot movement or custody completion is implied.

  2. Accepted The fleet system has accepted the mission

    Routing and motion remain under fleet-controller rules.

  3. At handoff Station and load checks meet

    Warehouse custody advances only against the expected location and asset.

  4. Completed Outcome is reconciled

    Mission completion, warehouse state and exceptions are compared before downstream work advances.

Alarm recovery

Operators see the work consequence of a fleet fault

Stale pose

The map labels old state as stale instead of presenting it as live.

Mission fault

The failed handoff remains attached to its warehouse task and reservation context.

Controlled intervention

Only approved actions allowed for the user’s role are offered; controller safety remains in force.

Fleet authority

Mission authority is not motion authority

The fleet controller owns safe travel

Ysend chooses and governs warehouse intent. The fleet manager, vehicle controller and safety systems determine whether and how the robot moves.

  • Vendor motion tests require a platform-controlled authorisation window.
  • A vendor cannot self-assign a fleet or approve its own movement.
  • If live status is lost, commands are stopped or paused.

Trace one mission from demand to handoff

Bring a site map, fleet protocol, controller owner, load handover and fault handling. We will identify adapter maturity and the authority boundary.

Review my fleet path