Fleet Software Offers: Separate Robot Control From Service Terms

Published 2026-11-02 21:12:34 -05:00 (America/New_York). Sources checked 2 November 2026. This is an editorial engineering guide; suggested tests below are not reported product test results.

List the functions the operation needs

MiR’s software overview distinguishes software on the robot, centralized fleet management and operational visualization. It is a useful example of why a robot software offer should be broken into functions instead of treated as one undifferentiated package. The public overview is not a price list or a complete statement of licensing terms for an individual customer.

Write the intended workflow from job creation to confirmation of completion. Identify which component assigns work, manages traffic, handles station interfaces and supplies reporting. An application that displays fleet performance may not be the component that schedules jobs. Naming those responsibilities helps the purchasing team ask for the correct software and integration services without assuming every screen controls every function.

Specify deployment and supported combinations

Record the proposed robot models, fleet size, software releases and hosting arrangement. Ask whether the offer covers the buyer’s actual combination and which prerequisites the customer must supply. If a server or network service is customer-operated, assign responsibility for backups, monitoring, access management and capacity. If a service is supplier-operated, specify the service boundary and the customer’s dependencies.

Check the treatment of future robots, additional sites and integration interfaces in the written offer. These are questions about the contract, not claims that a particular vendor charges in a particular way. Make the answer explicit for the proposal under evaluation. A trial arrangement should also state which functions and capacity it includes so that the buyer does not mistake a temporary demonstration for the production entitlement.

Exercise normal and degraded operation

Use the agreed deployment to test job submission, completion reporting and an exception at a receiving station. Ask the integrator to preserve a trace that relates the business job to the fleet event and the actual robot action. Test a robot becoming unavailable and observe how queued work is presented to the operator. A report showing high availability should explain its denominator and any excluded periods.

In an approved environment, examine a server restart or loss of a required connection. Determine what continues locally, what stops and what must be reconciled on restoration. Do not assume that a dashboard reconnecting means every in-progress job has been correctly recovered. The site needs an operational procedure for uncertain task and load states, with named responsibility between software and equipment suppliers.

Make ongoing ownership visible

The final offer should identify update and support scope, response arrangements, configuration ownership and access to historical operational records. Ask how the customer receives a configuration export or other agreed recovery material and what happens when the service relationship ends. Where information is unavailable, retain an explicit action item instead of assuming the supplier will provide it later.

Compare proposals using the same function and service matrix. Mark exclusions, customer prerequisites and separately priced integrations. Include a controlled update and regression process, especially when several robot models share one fleet system. The purchasing decision should reflect a supported operating arrangement over time, rather than relying on a familiar product name, an attractive reporting screen or an unverified assumption about what a software subscription includes.

Source and next steps

Reference: MiR official software product overview. The recommendations in this guide are our proposed procurement and validation questions, not requirements attributed to that reference. Review available robot models, compare manufacturer profiles, or contact our team with the intended task and site constraints.