Know what’s inside every robot.

Connect the robot you design to the machines you build and service. Review current fitment, record unit and component hours together, and preserve inspected maintenance and operating history.

Opens ManyRows setup. Sign in or create an account, create a project, then review and apply the selected starter.

7-day free trial · No card requiredView plans and trial limits

The design stayed the same. The drive didn’t.

Compare a robot’s saved configuration with what is installed today. See the changed serial, manufacturing lot and fitted date, then follow the removed and replacement components back to their records.

ManyRows compares R1-0001 before and after a drive replacement, with serial DRV-R1-001 changed to DRV-R1-004 and eight unchanged build linesClick to enlarge ↗
R1-0001 · One replaced drive. Eight unchanged build lines. A retained configuration to compare.
01

One design. Each machine’s own record.

Keep the design BOM separate from each unit’s installed structure, customer, site and firmware. The first-product build review brings physical serials, serviceability and hours into view, and flags design mismatches, duplicate fitments and reached component limits.

Explore BOMs and configurations
ManyRows RoboArm A1 record showing the robot-arm engineering drawing and product attributesClick to enlarge ↗
RoboArm A1 · The robot’s drawing, specifications and engineering records in one place.
02

A replacement starts its own history.

Record operating hours against physical components as well as the robot. Keep a removed drive’s accumulated usage, find a fitted battery over its maintenance limit, and distinguish an unused spare from a part already in service.

Explore connected service records
ManyRows shows battery BAT-R1-003 at 1,250 operating hours against a 1,200-hour limit, 50 hours over its illustrative maintenance limitClick to enlarge ↗
The fitted battery has 1,250 hours. Its unused spare has zero.
03

See what is fitted right now.

Open the unit’s Maintenance tab to review its current fitted serials, serviceability and independent unit and component hours. Find mismatched designs or serials, duplicate fitments, holds and reached limits. An unset hour limit keeps recorded usage visible and remaining life unknown.

Explore current condition and service records
ManyRows Maintenance tab showing a fitted drive at 7.5 operating hours and a unit with 7 hours whose limit is unsetClick to enlarge ↗ManyRows Maintenance tab showing a fitted drive at 7.5 operating hours and a unit with 7 hours whose limit is unsetClick to enlarge ↗
Current readings follow operating usage. Saved maintenance evidence keeps its original inputs.
04

Put the checks behind the release.

Review the engineering change, then record the required inspections on the approved revision. Protective-stop and hardware/firmware evidence stays connected to the decision to certify an internal release.

Explore release control
RoboArm A1 approved revision blocked from release until its protective-stop and hardware/firmware inspections passClick to enlarge ↗
Approval is recorded. Two required inspections still block certification.
05

Keep a failed unit visible.

A released design can still produce a unit that needs attention. Keep the pilot’s failed connector inspection, open nonconformance and Down status connected so engineering and service can review the same evidence.

Explore quality and follow-up
ManyRows quality check for the Rover pilot unit with a Rejected verdict and an open nonconformanceClick to enlarge ↗
The pilot’s design is released. Its physical unit remains Down.
06

Record the work that actually happened.

After the approved declaration is inspected and internally certified, record the actual replacement against its work order. Confirm the fitting date and serviceability decisions; save the installed serial and firmware, completed work and before/after configurations together. Unit and component hours keep their histories.

Explore release and inspection evidence
ManyRows completed maintenance receipt for a fictional rover, showing its fitting date, In service unit status, Quarantined removed drive, saved fitment comparison and JSON downloadClick to enlarge ↗ManyRows completed maintenance receipt for a fictional rover, showing its fitting date, In service unit status, Quarantined removed drive, saved fitment comparison and JSON downloadClick to enlarge ↗
A recorded replacement. One retained maintenance receipt.
07

Keep proof of the replacement.

Compare the saved before and after fitments to see what changed. Later fleet changes leave these configurations intact. Download a JSON maintenance record with the receipt, approval evidence and both saved configurations for engineering and service to review.

Explore configuration comparisons
ManyRows compares saved configurations before and after maintenance on a fictional rover, showing one changed drive line and its removed and replacement serialsClick to enlarge ↗ManyRows compares saved configurations before and after maintenance on a fictional rover, showing one changed drive line and its removed and replacement serialsClick to enlarge ↗
The saved fitments remain available after later service.
08

Find the work behind each replacement.

Review recorded completions from the unit or its matching work order. Load older replacements, then open the original declaration, receipt, retained fitments and evidence download. New visits leave older history pages stable, and field permissions protect the captured evidence.

Explore recorded maintenance
ManyRows unit Maintenance tab showing a recorded replacement and a link to its original completion receiptClick to enlarge ↗ManyRows unit Maintenance tab showing a recorded replacement and a link to its original completion receiptClick to enlarge ↗
Unit and work-order history lead back to the same retained maintenance receipt.
09

One interval. Each serial’s own hours.

Enter the actual service date and unit hours, select the fitted physical serials that ran, and give each its own hours. A mapped interval note follows native field rules. Save the configured visit and selected component usage entries together. Changed fitment or usage requires a fresh review before a new interval is recorded.

Explore the operating-hour workflow
ManyRows operating-hour recorder with 7 unit hours, the selected replacement drive at 7.5 component hours, and an interval noteClick to enlarge ↗ManyRows operating-hour recorder with 7 unit hours, the selected replacement drive at 7.5 component hours, and an interval noteClick to enlarge ↗
Seven unit hours and 7.5 drive hours are recorded together and accumulated separately.
10

Resume an interval after a lost response.

The exact pending interval is saved on this device before submission, scoped to your signed-in account, project and unit. Close, reopen or reload, then explicitly retry that interval. A confirmed retry returns the original records without counting the same interval twice. Clearing browser data can remove the saved request.

Explore interval recovery
ManyRows after reloading a pending operating interval, showing hidden saved inputs and an explicit Retry this interval buttonClick to enlarge ↗ManyRows after reloading a pending operating interval, showing hidden saved inputs and an explicit Retry this interval buttonClick to enlarge ↗
A real committed interval with a lost response, recovered through an explicit exact retry.
11

Follow each interval back to its records.

Review service dates, notes, unit hours and linked component usage on the unit’s Maintenance tab, including serials removed from current fitment. Open the service, component usage or physical serial record. Native edits appear on refresh; archived, draft and trashed entries are excluded.

Explore operating history
ManyRows operating history with a 7-hour unit interval, 7.5 hours on its linked drive serial, notes and native record linksClick to enlarge ↗ManyRows operating history with a 7-hour unit interval, 7.5 hours on its linked drive serial, notes and native record linksClick to enlarge ↗
Live operating history shows independent amounts and the serial linked to each usage entry.

Bring your first robot into view.

Use the Robotics Factory starter to create a project and preview its model. Start with the structure or include the fictional examples, then adapt the fields, relationships and checks to your team. For operating hours on an existing project, connect your own types in Project settings → Operating hours.

17
record types
254
optional example records
2
commissioning inspection plans

Connect design, build and service

  • Current fitted serials, serviceability and operating life
  • Operating intervals, explicit retries and native history
  • Robot designs, assemblies and manufacturing BOMs
  • Built units, installed serials and firmware releases
  • Component usage and inspected maintenance completion
  • Return-to-service declarations, approvals and inspections
  • Retained fitment comparisons and maintenance record downloads
First steps after applying
  1. Follow a design to its physical units

    Open a Robot and expand its engineering BOM, then follow its Robot Units. In the unit’s Maintenance tab, review current fitted serials, firmware, serviceability and independent unit and component hours.

  2. Review the battery return-to-service candidate

    Open the draft Commissioning Declaration for the R1-0003 battery replacement. Confirm the fitted battery, unused spare, approved firmware and remaining component life, then approve the intended revision and complete its required inspections before internal certification.

  3. Record the work and operating interval

    After the physical replacement, use Record maintenance completion to retain the fitting date and before/after configurations. Use Record operating hours for an actual service interval, then follow the native records in Operating history.

Read the robotics service guide

Common questions

Where do I find the next task?

Open Project Home’s Work queue tab. Focus on work assigned to you, overdue, unassigned or blocked tasks, then open the native record or next planned milestone. A linked unfinished prerequisite opens its exact card. Loading more records expands the assessed scope; completing a planning step does not approve commissioning or return to service.

How are a robot design and a physical unit connected?

The design record holds the model and its engineering BOM. A Robot Unit represents one serial-numbered machine with its own installed structure and service history. Serialized Component records identify the physical drives and batteries used by those machines.

Does replacing a component reset the robot’s operating hours?

Unit hours come from service events. Component hours come from separate usage events linked to each physical serial. The removed component keeps its history, and the replacement accumulates its own usage while the robot retains its total hours.

Can I review firmware compatibility?

The template links a unit’s firmware release to its robot model’s approved firmware list. This makes unlisted firmware visible alongside installed configuration and service records for your team to review.

What is checked before commissioning approval?

The removed serial must be fitted to the declared unit. The replacement must match its design, be serviceable, have known positive remaining life and be unfitted elsewhere. Proposed firmware must be on the model’s approved list. Approval captures that physical evidence; changed inputs require fresh approval and inspections before certification or completion.

What is included in the starter template?

There are 17 record types, a full optional set of 254 fictional example records, and two inspection plans for commissioning declarations. The reusable template includes a draft return-to-service candidate. Screenshots show the prepared demo, including a staged design approval and a pilot quality hold.

Does certification install a spare or return a robot to service?

Certification records the reviewed declaration and inspection evidence. After certification, use Record maintenance completion to record the work that was actually performed: fitting date, replacement, firmware and serviceability decisions. This explicit step updates the installed configuration and work order, retains before/after fitments and preserves all usage histories.

Can I keep the replacement evidence after later maintenance?

Each completion receipt links its work order, approved declaration, release certificate and saved before/after configurations. Compare saved fitment uses those retained configurations. Download maintenance record exports the receipt, approval evidence and both snapshots as JSON, with access checked when you download.

Do I need the Robotics Factory template to track operating hours?

No. Open Project settings → Operating hours → Set up workflow and connect your machine, physical-component, fitted-component, service-visit and component-usage types. Use five separate record types with the required Life Limit and Usage Amount fields. Names and keys can change after setup. Robotics Factory supplies these bindings automatically; commissioning and certified maintenance completion still require their native robotics schema.

How do I record unit and component hours together?

Open Maintenance → Current fitted components → Record operating hours. Enter the actual service date, positive unit hours and each selected fitted serial’s own hours. All selected records save together. Earlier or removed-serial usage can be entered through native service and component usage records.

What if saving an interval loses its response?

The exact request is saved on this device before submission for the same signed-in account, project and unit. Choose Review saved interval after closing or reloading, even while recording is paused or current fitment is unreadable, then choose Retry this interval. Saved inputs stay hidden and retry still requires current access. Nothing is retried automatically. A successful exact retry returns the original records; clearing browser storage can remove local recovery.

Where can I review history, and what does an unset limit mean?

Maintenance shows recorded replacement receipts and live operating history. Receipts keep their captured before/after fitments. Operating history follows native edits and links the serial used for each entry. It pages 25 intervals and displays up to 100 component entries per interval with an explicit notice when more exist. An unset limit preserves recorded usage without claiming remaining life or displaying a percentage gauge.

Can I keep using my fleet monitoring system?

Yes. Keep live telemetry in your monitoring system and use ManyRows for the engineering configuration, recorded usage, service history and review evidence.

Connect the next change to the robot it affects.

Give engineering and service a shared record of what was designed, what is installed, and what has been reviewed.

Screenshots and operating limits use fictional demo data. Your team defines its maintenance limits and inspection policy, records actual work, and makes return-to-service decisions.