SCOPIO LABS · RMS

Scopio RMS

Scopio RMS

Scopio RMS

Built for remote management of medical hardware. Designed to be trusted.

Role:

Role:

Product Designer & Product Owner

Built for remote management of medical hardware. Designed to be trusted.

Role:

Product Designer & Product Owner

OVERVIEW

Where remote management meets medical-grade responsibility

Where remote management meets medical-grade responsibility

Scopio Labs builds digital cell morphology scanners used in medical labs worldwide. Their distributors, such as Beckman Coulter, manage hundreds of these scanners across Europe and the US, performing remote operations such as opening tunnels, running commands, and updating software.

My Role

I acted as both product designer and product owner, managing two very different user bases simultaneously while also maintaining the core diagnostic application.

I acted as both product designer and product owner, managing two very different user bases simultaneously while also maintaining the core diagnostic application.

THE BUSINESS MANDATE

A $100k problem hiding in plain sight

A $100k problem hiding in plain sight

Distributors used Rport, an open CLI tool, to perform remote operations on Scopio's scanners. The core issue: they had unrestricted access to the system, including the ability to edit update scripts directly.

This wasn't a configuration fix. Scopio needed a purpose-built frontend that could lock down access, enforce protocols, and give users the confidence to operate independently.

RISK 01

Uncontrolled script access

Scripts could be unintentionally modified, causing deployment failures on live medical hardware.

RISK 02

Low system adoption

The lack of guardrails made users reluctant to operate independently, pushing routine tasks to Tier-2 support.

UX CHALLENGES

Operating in the dark

Operating in the dark

Through interviews with both user types, three design challenges emerged.

01

Identity Loss in Tab Overload

Every action opens a new browser tab. Users quickly lose context of which machine they're operating on, risking catastrophic misconfigurations.

David Ron

Age 36 · Scopio Technical Support

"Juggling 15 browser tabs just to track updates and active operations is exhausting."

02

The Context Blind Spot

Navigating away from an active software update means losing all visibility of its progress and terminal output, creating severe operational blind spots.

John Carter

Age 52 · Beckman Coulter distributor

"Navigating away from the deployment tab means losing the progress and logs."

03

Unguided & Cluttered Workflows

Rport provides no structured update flow and no guardrails. Each user followed their own understanding of the process, with no shared protocol, which causes errors.

David Ron

Age 36 · Scopio Technical Support

"We keep getting the same calls. Different users, same errors."

Logic Mapping

Logic Mapping

Before defining any solution, I mapped the complete system flows to identify how operations connect and where risk concentrates. The software update flow emerged as the highest-risk path, requiring manual verification both before and after deployment.

Three solutions, one coherent system

Three solutions, one coherent system

SOLUTION 01

To CHALLENGE 01 - tab overload

Centralized Architecture

Centralized Architecture

After reviewing Rport's existing architecture, I kept the persistent device list.
I enriched it with status tags that surface active operations in real time, tunnels, software updates, commands, visible from anywhere in the system.

After reviewing Rport's existing architecture, I kept the persistent device list. I enriched it with status tags that surface active operations in real time, tunnels, software updates, commands, visible from anywhere in the system.

Overview screen: the device entry view

Overview screen:
the device entry view

The main hub where every operation starts and all active statuses are visible.

Enriched device tags show all active operations per device, SU, Remote Access: SSH, and Remote Access: HTTPS, replacing the need for multiple browser tabs. The user always knows which operations are active on which device, regardless of where they are in the system. No tab switching, no lost context.

Enriched device tags show all active operations per device, SU, Remote Access: SSH, and Remote Access: HTTPS, replacing the need for multiple browser tabs.

The user always knows which operations are active on which device, regardless of where they are in the system. No tab switching, no lost context.

Access application screen: full view

The Scopio application is accessed via an HTTPS tunnel directly within the RMS, with no external tabs.

The Scopio application opens via HTTPS / SSH tunnel directly inside the RMS. The device name is always visible, the user always knows which scanner they are connected to.

SOLUTION 02

To CORE CHALLENGE - Unrestricted Script Access

Governed Execution

Governed Execution

Scripts are locked and read-only across all operations. Whether running commands or updating software, users have full visibility into what is happening with no ability to modify the underlying process.

Commands screen

The Commands screen contains predefined operations with live output, replacing direct script access

Commands are labeled by the trigger users already recognize. I added a description that explains exactly what each command performs.

Software Update screen

The Software Update screen is where the update runs live, progress is tracked in real time, and the full log is recorded and stored upon completion.

The update terminal is locked - users observe every step in real time with no ability to interfere with the running script.

Even after navigating away, users can return to an active update without losing context.

The update terminal is locked - users observe every step in real time with no ability to interfere with the running script.

Even after navigating away, users can return to an active update without losing context.

SOLUTION 03

To CHALLENGE 02 & 03 -
Context blind spot & Unguided workflows

To CHALLENGE 02 & 03

Guided Update Flow

Guided Update Flow

A structured wizard replaces guesswork with a clear, enforced protocol. Every step of the software update process is defined, sequenced, and tied directly to Scopio's deployment guidelines.

PHASE 01

Pre-Update Wizard

Pre-Update Wizard

Two mandatory checks: verify the system is idle, export current settings. Next unlocks only when both are confirmed. State persists if the modal is closed and reopened.

PHASE 02

Software Update

Software Update

The user can navigate freely while the update runs. The SU tag in the device list acts as a live progress bar, and the full log remains available upon return to the update screen.

PHASE 03

Post-Update Steps

Post-Update Steps

Guided next steps based on update status. Advisory, not enforced. Users can dismiss and access the full log at any time.

BEFORE & AFTER

From a risky CLI to a governed system

From a risky CLI to a governed system

The same operation, two completely different experiences.

BEFORE, RPORT

AFTER, SCOPIO RMS

EXPECTED IMPACT

Designed for trust, built for independence

Designed for trust, built for independence

The system was designed to reduce dependency on Tier-2 support and enable confident, independent operation.

Reduced Support Escalations

By guiding users through every critical operation, the system eliminates the ambiguity that drove routine tasks to Tier-2 support.

Zero Human Errors in Updates

Locked scripts and a mandatory pre-check wizard remove the conditions that caused deployment failures and hardware damage.

Full Operational Visibility

Persistent logs and real-time status indicators mean users are never operating blind, regardless of where they are in the system.

Increased System Adoption

A governed, trustworthy interface gives users the confidence to operate independently, reducing both friction and fear.

Get in touch!

Get in touch!

If you have any questions, feedback or would like to discuss my work further, feel free to get in touch :)

View Project

Bat Chen Ben Arza 2025 Ⓒ

BEFORE & AFTER

From a risky CLI to a governed system

The same operation, two completely different experiences.

BEFORE, RPORT

AFTER, SCOPIO RMS