Designing digital experiences around how and where people actually work.

Spaceux
  • Home
  • Portfoilio
  • Agentic CRM
  • About
  • Dashboard Analytics
  • Architectural UX
  • More
    • Home
    • Portfoilio
    • Agentic CRM
    • About
    • Dashboard Analytics
    • Architectural UX
Spaceux
Resume
  • Home
  • Portfoilio
  • Agentic CRM
  • About
  • Dashboard Analytics
  • Architectural UX
Resume

AI-Assisted Smart Factory Operations

Overview: 

Modern manufacturing facilities depend on continuously operating systems that move materials between equipment, storage areas and production stages.


Operators, engineers and technicians need to understand equipment status, detect interruptions and make safe decisions without slowing production.


The existing experience distributed critical information across multiple screens, nested dialogs and data-heavy views. This increased cognitive load precisely when users needed clarity and speed.

Design Process Overview

My Role:

As Senior Product Designer, I contributed across the end-to-end product-design process:

  • Discovery and contextual research
  • Research synthesis and opportunity framing
  • Product and UX strategy
  • Information architecture
  • Multi-device workflows
  • Data visualization
  • Interaction and visual design
  • Enterprise design-system direction
  • Human-AI interaction concepts
  • Cross-functional design reviews

I collaborated with product managers, software engineers, factory-automation specialists, visited factory chambers and domain experts.



Rather than asking users only what features they wanted, I studied the sequence of information they looked for when beginning a shift, investigating an alert and escalating an issue.

User Research

Users

Researching Work in Context

Design Constraints

The platform supported several roles with different responsibilities:

  • Factory operators monitoring live operations
  • Floor technicians investigating equipment conditions
  • Process engineers analyzing performance
  • Maintenance engineers diagnosing failures
  • Shift supervisors coordinating response and handoffs

Design Constraints

Researching Work in Context

Design Constraints

The product had to operate within an unusually demanding environment:

  • Continuous 24/7 operations
  • Dense, real-time operational information
  • Safety and compliance requirements
  • Legacy system and integration constraints
  • Limited deployment windows
  • Wall-mounted terminals and tablets
  • Cleanroom gloves affecting touch accuracy
  • Experienced operators skeptical of automated recommendations

Researching Work in Context

Researching Work in Context

Researching Work in Context

I used a combination of research methods to understand both the interface and the operational environment:

  • Workflow shadowing
  • Contextual inquiry
  • SME workshops
  • Existing-product audit
  • Heuristic evaluation
  • Workflow and navigation analysis

Context nquiry

Research Synthesis

What We Learned

Information was available but difficult to locate

  • Users moved between nested screens and dialogs to assemble the context needed for one decision.


Critical information represented only a small portion of the interface

  • During an incident, users primarily needed equipment status, alarm priority, location, related material and the next safe action.


Spatial context was essential

  • Operators needed to understand not only what had failed, but where it was located and what neighboring equipment or workflows could be affected.


Status needed to remain continuously visible

  • Navigating to deeper information often removed the broader operational context.


Mobility changed the interaction model

  • Floor technicians required larger touch targets, simplified data density and rapid access to urgent actions while moving through operational areas.


Trust was more important than automation

  • Experienced users were willing to consider system recommendations only when the evidence and reasoning remained visible.




Synthesized research insight

Users were spending more effort locating information than interpreting it.


Jobs to Be Done

When material movement or equipment behavior becomes abnormal, I need to identify the affected area, understand the likely cause and choose a safe recovery path, so that operations can continue with minimal disruption.

Affinity

JTBD

Opportunity

Product Strategy

The research led to six guiding principles.

Simplify

  • Remove duplicate information and unnecessary interface noise.


Prioritize

  • Surface critical equipment conditions, operational impact and required actions first.


Preserve Context

  • Keep location, equipment and surrounding system status visible during investigation.


Progressive Disclosure

  • Present a clear operational summary first, then allow users to inspect detailed telemetry and configuration when required.


Design for Mobility

  • Adapt the experience for tablet use with larger touch targets, focused workflows and appropriate data density.

Keep Humans in Control

  • Use automation to assist judgment without removing operator authority.



Rules, AI and Human

Where AI Should - and Should Not - Act

  • A key product decision was not to apply AI to every operational task.


Deterministic System Responsibilities

  • Safety interlocks, equipment-state tracking, compliance controls and execution boundaries remain governed by predictable system rules.


AI-Assisted Responsibilities- AI can help:

  • Prioritize anomalies by operational impact
  • Correlate signals from multiple sources
  • Suggest possible causes
  • Summarize supporting evidence
  • Recommend next actions
  • Generate shift-handoff summaries
  • Support natural-language information retrieval


Human Responsibilities

Operators retain authority to:

  • Approve a recommendation
  • Modify the proposed action
  • Reject or override it
  • Escalate the incident
  • Confirm recovery


Human-AI Decision Flow

  • The system detects an abnormal condition.
  • The AI layer correlates available evidence.
  • The interface presents the recommendation, confidence and rationale.
  • The operator reviews alternatives and operational impact.
  • The operator approves, modifies or rejects the recommendation.
  • The deterministic system executes only an authorized action.
  • The outcome is recorded for audit and future learning.




Experience Architecture

I reorganized information around the equipment or device being investigated.


A selected device became the persistent context for:

  • Current status
  • Location
  • Active alarms
  • Related material
  • Connected ports
  • Recent activity
  • Available actions
  • Supporting diagnostic information

This device-centered model reduced the need to repeatedly move between unrelated system sections.


Design principles

Key Experience Concepts

Unified Operations Overview:

A single operational view brought together equipment health, spatial context, prioritized alerts and active material movement.

Design decision: Present critical status and exceptions first while keeping deeper details available on demand.


Detail Panel:

Recommendations displayed:

  • What the system detected
  • Why it mattered
  • Supporting evidence
  • Confidence level
  • Possible operational impact
  • Recommended next action
  • Alternative actions
  • Approve, modify and reject controls

Design decision: Allocate additional screen space to explanation because trust and safe decision-making were more important than interface compactness.



Mobile Incident Triage:

Tablet and mobile concepts allowed technicians and supervisors to review urgent conditions away from fixed terminals.

Design decision: Reduce chart density and emphasize priority, location, status and immediate actions.



Shift-Handoff Support:

Structured summaries preserved the investigation context, actions taken and unresolved issues across shifts.

Design decision: Support automated drafting while requiring human review before handoff completion.


Enterprise Design System:

The experience required a reusable visual language capable of supporting dense enterprise information without sacrificing clarity.

The system included patterns for:

  • Equipment and status cards
  • Critical alerts and warning states
  • Data tables
  • Contextual side panels
  • Operational charts
  • Recommendation and confidence states
  • Action confirmations
  • Empty, loading and disconnected states
  • Desktop and tablet layouts

Status was communicated through labels, iconography and hierarchy—not color alone.

Decisions and Tradeoffs

Data Density vs. Scanability

AI Assistance vs. Human Authority

AI Assistance vs. Human Authority

  • Operators required significant information, but presenting everything simultaneously increased cognitive load. 
  • Progressive disclosure preserved depth while improving initial comprehension.

AI Assistance vs. Human Authority

AI Assistance vs. Human Authority

AI Assistance vs. Human Authority

  • Automatic action could improve speed but introduce unacceptable risk. 
  • The design favored recommendation, explanation and explicit approval.

Explainability vs. Screen Space

AI Assistance vs. Human Authority

Explainability vs. Screen Space

  • Displaying evidence required more interface space. 
  • This was accepted because trust and verification were essential.

Desktop Depth vs. Mobile Usability

Real-Time Information vs. Interface Performance

Real-Time Information vs. Interface Performance

  • Desktop/Tablet views could be browser base, to save internal data & support detailed analysis. 
  • Mobile views focused on triage, status alerts popup rather than reproducing every desktop capability.

Real-Time Information vs. Interface Performance

Real-Time Information vs. Interface Performance

Real-Time Information vs. Interface Performance

  • Continuous updates were necessary, but they could not interfere with interaction responsiveness. 
  • The experience prioritized perceptual stability and clear update behavior.

Strategic Decisions: What We Did Not Design

Real-Time Information vs. Interface Performance

Strategic Decisions: What We Did Not Design

  • No fully automated operational overrides
  • No unfiltered raw-log dumps on primary operational screens
  • No gesture-heavy interactions for cleanroom use
  • No AI recommendation without evidence or human controls
  • No desktop interface scaled directly onto tablets

Validation and Success Measures

Validation and Success Measures

Validation and Success Measures

Validation and Success Measures

Concepts were refined through domain-expert reviews and scenario-based workflow walkthroughs.

Evaluation focused on whether users could:

  • Identify the most critical condition
  • Locate the affected equipment
  • Understand the operational impact
  • Interpret the recommendation and evidence
  • Select a safe next action
  • Recover from an incorrect or rejected recommendation
  • Complete a shift handoff without losing context

Success measures included:

  • Time to identify a critical alert
  • Navigation steps required for investigation
  • Task-completion rate
  • Incorrect-action rate
  • Handoff completeness
  • Recommendation acceptance and override rates
  • Operator confidence
  • False-positive and false-negative rates

Exact participant data, operational metrics and implementation outcomes are omitted for confidentiality.

Design Outcome

Validation and Success Measures

Validation and Success Measures

Design Outcome

The project established a unified experience direction for complex factory operations by:

  • Consolidating fragmented operational information
  • Clarifying alert priority and system status
  • Reducing unnecessary navigation
  • Preserving spatial and equipment context
  • Supporting floor-based tablet workflows
  • Defining safe patterns for explainable AI assistance
  • Creating reusable enterprise interface foundations

Exact product metrics and implementation details are omitted due to confidentiality.

Exact product metrics and implementation details are omitted due to confidentiality.

Exact product metrics and implementation details are omitted due to confidentiality.

Exact product metrics and implementation details are omitted due to confidentiality.

Exact product metrics and implementation details are omitted due to confidentiality.

Exact product metrics and implementation details are omitted due to confidentiality.

  • Home

SpaceUX.online

Copyright © 2025 rohanuplap - All Rights Reserved.

rohan.uplap@gmail.com

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

Accept