Robot Initial Parameter Record: Why Day One Data Matters

Domain 1 Article Series · Part 2 of 6  |  RSF Whitepaper v1.0 · §3.2

Picture a service engineer in 2033, called out to a seven-year-old six-axis arm that has started throwing intermittent J3 overcurrent alarms. The first thing she wants to know: what did J3 current look like when this machine was new? She opens the equipment file. The commissioning records from 2026 list software versions and a TCP accuracy figure. Per-axis current baselines: not recorded.

Now she has a reading with nothing to compare it against. Is 8.2 amps normal for this machine under this program, or is it 30% above where it started? Nobody knows. Nobody can know — the machine's day-one state wasn't captured, and there is no way to go back and measure it.

The RSF Whitepaper calls Phase 1 (Delivery and Installation) the highest-risk-density phase of the robot lifecycle, and most of that risk works exactly like the missing J3 baseline: quality problems at installation rarely announce themselves at installation. They surface months or years later, as faults that resist root-cause analysis because the evidence needed to analyze them was never collected.

This article covers what RSF actually requires in Phase 1, and spends most of its time on one document — the Initial Parameter Record — that solves the problem the engineer in 2033 is having.

Who Does What: The RACI Matrix

A robot installation typically involves four parties working in the same space during the same week: the robot service engineer handling the body and commissioning, an electrical contractor on power and wiring, a system integrator on peripheral interfaces, and the customer's own engineers doing process confirmation and acceptance. The whitepaper identifies unclear responsibility boundaries among these parties as the most common root cause of installation delays and quality disputes — not technical difficulty, boundary confusion.

RSF's tool for this is a standard RACI matrix. The full version in the whitepaper covers ten work packages; the abbreviated version:

R = Responsible · A = Approves · C = Consulted · I = Informed. Abbreviated from RSF Whitepaper Table 3.2-1.

Note the two safety rows. For safety-circuit testing and safety-function verification, the customer engineer's entry reads “A (present)” — the whitepaper requires them physically on-site for these steps, not signing paperwork afterward. Safety verification happens with the customer watching, by design.

Unboxing: The Only Chance to Assign Shipping Damage

RSF's delivery acceptance procedure is four steps — photograph the packaging before opening, inventory against the packing list, visually inspect the body (joint interfaces, reducer outputs, cable entry points), then sign off or file a Goods Damage Record and stop. Nothing unusual there. What matters is the reasoning behind the formality, which the whitepaper states directly: once unboxing acceptance is signed without objection, later-discovered damage faces serious obstacles in liability attribution.

In other words, the acceptance signature is a legal boundary, not a formality. “Outer packaging intact” does not substitute for physical inspection, and if damage is found, installation stops until the OEM responds. An engineer who skips the photos to save twenty minutes is spending the customer's leverage.

Load Inertia: One Field, Ten Years of Consequences

During software initialization, the engineer enters the payload parameters — weight, center of gravity, and inertia values for the end-effector and workpiece. FANUC's documentation singles this out: entering correct Load Inertia is “one of the most important settings affecting robot life.”

Here is the mechanism. The servo controller uses the load-inertia value to estimate torque. If the entered value is wrong, the estimate is wrong, and the joint reducers absorb shock loading beyond specification on every motion cycle. The robot runs fine. The wear accumulates over thousands of hours where no inspection will see it, and eventually shows up as a reducer failure well before its rated life — at which point the actual root cause is a number someone typed during installation, years earlier, and probably never wrote down.

RSF's procedure closes both gaps: the values must come from the tool manufacturer's specification sheet rather than estimates, the automatic load-identification routine (where the controller supports it) must confirm entered and measured values agree within 10%, and the final values go into the Initial Parameter Record — which is where this article has been heading.

The Initial Parameter Record

The IPR is a structured snapshot of the machine at commissioning. The whitepaper specifies five categories:

Most equipment documentation can be reconstructed if it goes missing. Lost the wiring diagram? Trace the physical installation. Gaps in the PM history? The work-order system has most of it. The IPR is the exception, because what it records is not information about the machine — it is the machine's state at a point in time that only occurs once. Six months in, the axis currents already include early wear. The accuracy figures already include settling. The new-machine baseline is gone.

This is why the medical-record analogy fits. A physician interpreting a patient's numbers needs baseline vitals from when the patient was well. Same logic, same one-time window.

The Gate Out of Phase 1

Phase 1 ends at a Stage Gate, not at the engineer's departure. Three conditions: a safety-function verification report completed and signed by the customer, the IPR archived (load-inertia values included), and all wiring identification and grounding verified. The verification itself runs through a defined checklist — E-stop response, safety-door interlock timing, light-curtain triggering, teach-mode speed limit, cobot torque limits per ISO/TS 15066, STO — each with a test method, an acceptance criterion, and a record.

If the gate conditions aren't met, the whitepaper's instruction is one word: stop. Dynamic commissioning without verified safety functions violates ISO 10218. There is no engineering-judgement override on this one.

The closure package — Installation & Commissioning Report, the dual-signed safety verification report, the IPR, the Delivery Acceptance Certificate, and the training record — goes into the equipment passport. The safety report is kept permanently.

Two Takeaways

For engineers preparing for RSF Professional certification: Phase 1 competency is assessed at execution level — checklist completion, complete IPR recording, correct acceptance procedure, participation in safety verification. The IPR sections of the whitepaper (§3.2.5–§3.2.7) are worth close reading; the five parameter categories and their recording formats are testable material.

For customers taking delivery of a robot: before the installation team leaves, check the equipment passport for three documents — a complete IPR, a safety verification report with two signatures, a signed DAC. Missing any of them, Phase 1 isn't done, and the gap will belong to you long after the installer's warranty period ends.

Part 3 covers Phase 2 — run-in and commissioning — and takes a closer look at the Stage Gate mechanism, including the gate the whitepaper defends hardest: the one between commissioning and production.