Skip to main content

SIMIT Rapid Tester · Siemens Digital Industries

Simplifying industrial automation testing through graphical, reusable workflows

Validating control logic, interlocks and sequences involved substantial manual effort and coding knowledge.

As the sole UX designer, I worked with automation experts, stakeholders, product-line managers and engineers to understand the domain and structure an accessible end-to-end testing experience.

Company
Siemens Digital Industries
Product
SIMIT Rapid Tester
Role
Sole UX Designer
Platform
WPF desktop application
Domain
Industrial Automation
Users
Automation engineers and testing specialists
Overview

Precision for experts, accessibility for more engineers

SIMIT Rapid Tester lets engineers create automated tests, configure reusable scenarios, execute them and review results. The central problem was:

How could we simplify test creation without removing the precision required by automation experts?

Challenge

Repetitive validation, specialist knowledge

Industrial automation testing requires validating complex control logic, interlocks and operating sequences — repeatedly, as projects evolve.

Across the broader testing process, much of this work depended on manual effort and coding knowledge. The existing WPF editor already offered graphical editing controls, but structure, reuse and feedback across the full workflow needed to be clearer.

01

Create tests with confidence

Build test logic and technical conditions without writing every step from scratch.

02

Reuse existing work

Apply test definitions across different configurations.

03

Execute and investigate

Run repeated validations and understand failures.

Approach

Learning the domain, structuring the lifecycle

I worked closely with automation experts to understand how tests are planned, configured and reviewed, and with product-line managers and engineers to align on scope and feasibility.

I translated requirements into workflows, information architecture, wireframes and interactive prototypes, refining them through iterative feedback.

  1. Project overview
  2. Coupling setup
  3. Test Type
    Reusable logic
  4. Test Instance
    Configured parameters
  5. Test Set
    Ordered instances
  6. Execution
  7. Results
The testing workflow, simplified from the confirmed product sequence.
Information architecture connecting project setup, test design, execution and management.
Solutions

Key design decisions

Decision 01

Graphical test authoring

Problem
Engineers must define actions, signal values, conditions and timing precisely — and the logic has to stay readable.
Alternatives & constraints
The legacy WPF editor already had graphical controls; the gap was information hierarchy, reuse and interaction clarity rather than the absence of a visual editor.
Decision
A project hierarchy, central test editor and contextual action library. Engineers build sequences from predefined actions such as Set, Read, Wait and Verify, and configure each action in place.
Rationale
Visible, editable logic supports precision without requiring every step to be written from scratch. Inline validation flags problems such as a duplicated internal variable during creation.
The graphical editor makes test logic visible while keeping signal-level precision.
Earlier WPF test editor, which already supported graphical editing.
Early concept — test editor, action library and configuration workspace.
Decision 02

A reusable testing hierarchy

Problem
Projects need the same test logic with many different signals and values.
Decision
Test Type defines reusable logic. Test Instances represent configured scenarios and parameters, edited in a structured table with import/export. Test Sets organize instances into sequences, and execution and results provide feedback and traceability.
Rationale
Separating logic from parameters makes reuse the default instead of copy-and-edit.
Early concept — grouped test-instance configuration.
Structured parameter editing across test instances.
Decision 03

Repetition, scheduling and reuse

Problem
Research identified that many tests were executed repeatedly.
Status
Implemented: scheduling. Proposed: test libraries and templates.
Decision
I explored scheduling, libraries and templates to reduce repeated setup. Scheduling of test sets is part of the product; libraries and templates were proposed opportunities.
Decision 04

Technical trade-offs and developer collaboration

Problem
The product had to be delivered within WPF, which limited some modern interaction patterns.
Alternatives & constraints
I explored a web UI proof of concept with Siemens iX components and advocated for more modern interaction patterns.
Decision
The product remained on WPF. I collaborated with developers on feasible component patterns and implementation choices within that platform.
Rationale
Designing for what could actually ship kept the experience consistent and buildable.
Execution status and detailed results support review and failure investigation.

See SIMIT Rapid Tester in action

A public Siemens product overview shows how graphical test creation, reusable configurations and automated execution work together.

Public Siemens product overview video.Watch on YouTube (opens in a new tab)
Outcome

A connected testing workflow

What was delivered

  • Graphical test authoring.
  • Reusable test types, instances and test sets.
  • Test management and analytical results.

Feedback and recognition

  • Positive feedback on making testing accessible to a broader group of engineers.
  • Co-inventor on a published patent application, WO2026052547A1, covering validation of equipment and process behavior in a technical installation.

Reflection

Simplifying an expert workflow is not about removing advanced capabilities. It is about organizing them into understandable structures, interactions and feedback — and designing within the platform that will actually ship.

Brand and data points have been anonymised for confidentiality. Only a representative subset is shown here.

Next project

Grid Intelligence & Energy Analytics

Back

Selected Work