A Spreadsheet Guide to Robot Runtime and Fault Tracking
Using a spreadsheet for tracking robot runtime and faults gives small production teams a clear, low-cost view of equipment performance. It shows when a robot ran, stopped or handled material, which alarms recur and how long each interruption lasted. The result is more reliable than a maintenance anecdote: teams can compare shifts, machines and weeks before committing to repairs or new capital.
Shinagawa City’s digital-transformation program connects small and medium-sized businesses in Shinagawa Ward with vetted automation providers, offers subsidy support for qualifying implementations and runs seminars covering factory digitalisation, IT investment and online sales efficiency. These practices suit Australian firms operating Japanese equipment or considering an overseas supplier, although subsidy eligibility must be checked for the relevant jurisdiction.
Design one tracker around the operation
Start with one workbook containing separate tabs for runtime events, faults, master data and a dashboard. Give every robot a stable ID and every site a code that matches the asset register, rather than relying on a supplier’s nickname or a temporary spreadsheet title.
Store one event per row and use consistent columns for dates, timestamps, states, durations and fault categories. Keep calculated summaries on the dashboard sheet, and use drop-down lists for shift, production line, severity and cause. Frozen headers, date filters and a visible last-updated cell reduce errors when several people edit the file.
For a Shinagawa company evaluating Japanese technology, the program directory of vetted robotics companies offers a practical starting point. Australian businesses can apply the same verification discipline when comparing demonstrations, local support, spare-part commitments and total ownership cost.
Capture runtime with minimal operator effort
Define clear runtime states, such as running, setup, standby, fault stop and planned maintenance. “Running” should mean the robot was available to produce, rather than merely switched on. This distinction prevents standby time from inflating performance and keeps planned production time separate from unplanned downtime.
Record each state transition with a timestamp, robot ID and production line. Add cycle count, good units, scrap units and changeover time where available. For mobile robots, include travel, charging and waiting states; for robotic arms, include fault stops and operator intervention. Consistent definitions make different models comparable without pretending they are identical.
Australian plants often operate around the clock, particularly in mining, food processing and logistics. Teams in Melbourne, Sydney, Brisbane and Perth may also cover different time zones or long travel distances for specialist support. Simple drop-down entries, shift handover checks and a single daily review by a team leader are usually more sustainable than asking every operator to write a lengthy report.
Record faults from alarm to closure
Each fault should receive a unique ID linked to the robot, line and operating condition. Capture the controller or PLC alarm code, the exact message, detection time, severity and a short description. A photograph of the screen or physical damage can be stored as a link, while notes should describe what changed immediately before the alarm.
Track the fault as it moves from open to acknowledged, diagnosed, repaired and closed. Record when the first person responded, when work began, when production resumed and which parts or labour were involved. A separate root-cause field prevents a temporary reset from being recorded as a permanent repair.
Work Health and Safety laws in Australia are based on the Safe Work Australia model but administered by state and territory regulators, including SafeWork NSW and WorkSafe Queensland. Lockout, guarding, emergency stops and electrical isolation requirements still apply, and a maintenance log cannot replace required safety checks or incident reporting. Record isolation and return-to-service steps so the spreadsheet supports safe work rather than bypassing controls.
Turn spreadsheet data into useful metrics
Use elapsed-time calculations to convert timestamps into decimal hours. Availability can be calculated as running hours divided by planned production hours, with planned breaks clearly excluded. Mean time between failures equals operating hours divided by the number of failures, while mean time to repair equals corrective downtime divided by the number of closed faults.
Add measures that match operational decisions, such as unplanned downtime per week, faults per 100 operating hours and the percentage of faults that repeat within 30 days. A fault-frequency summary can reveal whether one alarm dominates, while a downtime summary can separate minor delays from production-threatening failures. Use formulas that reference the source tabs so every update flows through automatically.
Mining operations in Perth, Kalgoorlie and the Pilbara face long travel distances, dusty environments and demanding maintenance schedules. Teams can consult mining automation specialists when comparing equipment support, and should classify each fault as mechanical, electrical, software, communications, environmental or operator-related to avoid treating every alarm as the same problem.
Set up runtime and fault log structures
Use these compact structures as starting points and adjust them to the available sensors and controller data.
- Date, site, production line, robot ID and shift
- Start and end time, with elapsed hours
- Runtime state, cycle count and good or scrap output
- Operator identifier, stop reason and linked work order
Keep the fault register separate so each issue has a clear lifecycle and measurable downtime.
- Fault ID, detection time, robot ID, line and alarm code
- Severity, fault category, exact message and operating condition
- Assigned person, response time, repair time, parts used and downtime
- Root cause, corrective action, verification date and closure status
Start a two-week pilot and build the habit
A limited pilot makes adoption practical. Many Australian SMEs combine spreadsheets with manual work orders, cloud tools and equipment from several suppliers, so the first version should solve one defined problem rather than attempt a complete digital system. Select a robot with recurring faults or meaningful production impact, agree on the categories and appoint one person responsible for data quality.
Where the Privacy Act 1988 applies, operator names, diagnostic notes and attached images can contain personal information. Use staff identifiers where possible, restrict editing rights, set a retention period and follow the Australian Privacy Principles for access and correction. Technical downtime records should also be separated from payroll, performance management and disciplinary files.
Keep technical evidence and financial records connected but distinct. Retain invoices in Australian dollars, record GST treatment and depreciation decisions with an accountant, and preserve subsidy documentation under the grant’s own conditions. Before making an automation purchase, use the runtime and fault results to estimate realistic savings, downtime exposure and payback rather than relying on a supplier’s best-case calculation.
Create the two logs today, assign one owner and run the pilot on one robot during one shift. For Shinagawa firms, pair the findings with a city subsidy assessment and a factory-digitalisation workshop; Australian firms exploring Japanese equipment can contact vetted providers directly and apply the same evidence-based purchasing test.