RobotAtom decision tool
Assess the deployment path, not just the robot.
Use one shared record to separate provider statements, reviewed evidence, agreed exclusions and open responsibilities before an overseas robotics supplier enters an Australian pilot.
Eight evidence areas
Turn supplier interest into a reviewable next decision
This tool is useful to both sides. Adopters can show exactly which deployment questions remain unresolved. Providers can respond against a defined system, evidence request and responsible owner instead of an open-ended promise to be “ready”.
Boundary: this record does not certify a supplier, determine legal compliance, approve an import, assess machinery safety or approve cybersecurity. Route each material decision to the responsible qualified specialist.
Complete system
Robot, tooling, sensors, software, safeguards, utilities and interfaces are named.
Delivery responsibility
Manufacturer, local integrator and adopter responsibilities are explicit.
Remote access
Every external connection has a purpose, approval owner, log and revocation route.
Data and hosting
Collected data, storage locations, retention, export and service-exit access are defined.
Updates and software
Firmware, software, licensing, support period and update authority are documented.
Import and local requirements
The importer and owners of customs, biosecurity and applicable product checks are named.
Local support
Territory, hours, escalation, spares, language and recovery responsibilities are confirmed.
Pilot evidence
The task, configuration, conditions, exceptions, acceptance measures and decision owner are agreed.
Pre-agreement boundary
Assign each exclusion and operator input
Use one row for each included, excluded or unresolved interface. A critical boundary stays open until its owner and evidence are recorded; this worksheet cannot approve safety or acceptance.
0 critical boundaries unresolved. Do not describe the scope as complete while these remain open.
Boundary 1
Change control
Keep changes tied to the agreed baseline
Record a proposed change before treating a new configuration, test or price as part of the original scope.
Change 1
Ask the provider to answer one deployment question
Record the request before the session. A demonstration can justify a next step without becoming production acceptance.
Your entries stay in this browser tab and are not submitted to RobotAtom.
Which conclusion does the supplier evidence support?
Trace one claim to the buyer's exact requirement. Record what remains outside its scope before using it in a shortlist decision. Entries stay in this tab and local download; analytics receives aggregate events, not typed values.
6 fields remain open
- Buyer requirement and exact installed configuration
- Supplier claim, document reference, revision and date
- What the evidence actually covers
- Excluded conditions and untested assumptions
- Next evidence request, responsible owner and due date
- Qualified review, date, restrictions and next decision
A filled record may still withhold progression. No supplier ranking, certification, compliance finding or deployment approval is issued.
Trace a replacement spare to its approval boundary
Record one proposed spare against one installed system. Use document references, not passwords, confidential programs or sensitive site details. Entries stay in this tab; only generic interaction events are measured.
Missing references: 6. Record remains OPEN.
- Installed asset and configuration reference
- Proposed spare identity and revision
- Compatibility evidence and its limits
- Reviewer, authority and dated disposition
- Required post-work verification and owner
- Exceptions, restrictions and next review
This does not verify compatibility, approve substitution, authorize fitting a part or permit restart. Record a withheld or rejected disposition and unresolved restrictions explicitly, even when every field is filled.
Comparing two bids? Start with the same-task supplier comparison record before ranking price or performance claims.
Need help turning the open items into a pilot brief? Describe the physical work to RobotAtom →