RobotAtom installed-cell evidence tool

Can the site see and end vendor access?

A remote-support policy does not show what the commissioned robot cell permits. Record the actual path, authority, buyer-held trace and witnessed exit checks before accepting remote-write access.

Record what this cell actually permits

Use references to approved records, not passwords, tokens or private network details. The site's cyber, engineering and safety owners choose which tests can be run safely.

Keep proposed, authorized and closed separate

Record the site's decision, not an approval generated by this tool. An approved maintenance window alone does not show that this session was authorized or ended. Use redacted record references; do not enter credentials.

Trace revocation and session end separately

A revocation record does not establish what happened to an existing session. Keep the later-access result and the session-end evidence separate. Record redacted references, failed results and unresolved exceptions; the site's qualified owners decide which checks are safe.

6 missing closure-trace references. Complete fields can still describe failed checks or unresolved closure; they grant no access approval.

Separate documents from observed behaviour

Mark a failed boundary check as failed. A vendor policy or architecture diagram is useful context, but is not a witnessed result on the installed path.

Approved session and permitted action
Unknown identity or wrong role rejected
Unapproved tool or source rejected
Expired window or revoked access rejected
Customer can disable the path and end a session
Buyer-held log captures identity, target, time, action and outcome
Remote change tied to approval and post-change check

25 open or failed evidence checks

No automatic access approval is issued. A material failed or missing boundary check should hold remote-write access until the site's owners resolve it.

  • Installed cell and configuration version
  • Support purpose and allowed action (observe, diagnose, transfer, change or command)
  • As-built connection path and exact target assets
  • Named vendor identity, customer approver and access owner
  • Approved tool, source, time window and expiry
  • Buyer-controlled log/export location and reviewer
  • Customer disable/revocation owner and procedure
  • Change-ticket link and re-test trigger
  • Customer authorization reference for this session (not a proposed window)
  • Session-ended evidence and retained log reference
  • Approved session and permitted action: observed result, dated evidence or observer missing
  • Unknown identity or wrong role rejected: observed result, dated evidence or observer missing
  • Unapproved tool or source rejected: observed result, dated evidence or observer missing
  • Expired window or revoked access rejected: observed result, dated evidence or observer missing
  • Customer can disable the path and end a session: observed result, dated evidence or observer missing
  • Buyer-held log captures identity, target, time, action and outcome: observed result, dated evidence or observer missing
  • Remote change tied to approval and post-change check: observed result, dated evidence or observer missing
  • Named site owner for disposition missing
  • Session disposition: Not authorized; closure not evidenced
  • Closure trace: Access revocation record, scope and time missing
  • Closure trace: Later-access check result and dated evidence missing
  • Closure trace: Revocation reviewer, restrictions and next action missing
  • Closure trace: Existing-session end evidence and time missing
  • Closure trace: Customer-held session log reference and reviewer missing
  • Closure trace: Session-closure exceptions, owner and next action missing

Your entries stay in this browser tab. The file is generated locally; RobotAtom records aggregate tool-use events, not your answers.

Keep this a site-owned decision

ASD's September 2026 procurement guidance discusses approved provider tools, source addresses, windows and customer-controlled logs for systems including OT. Joint OT connectivity guidance recommends brokered and time-bounded access. These are requirements sources, not proof that any named robot or site complies.

Live connection, revocation and failed-path tests need site-authorised cyber, engineering and safety review. This record does not discover devices, handle secrets, control a robot or replace the site's access approval.

The closure trace added 9 October 2026 separates permission revocation from an existing session ending. Six local references expose missing evidence on each side and preserve failed results in the download. This is RobotAtom's coordination method, not a prescribed assurance form or an automated connection check.

Read the remote-access evidence guide · Ask RobotAtom to scope the evidence review