Functional scope
Identify the existing screens, operations and functions that need to be carried over.
Web HMI Migration
Desktop to Web HMI Migration for Semiconductor Equipment – ARIS’s Real-World Experience
Full HMI MigrationLegacy HMI ModernizationReactJS & TypeScriptRuntime Configurable UI
In the semiconductor industry, equipment typically has a long operating life and is upgraded across several product generations. While the equipment control software may still meet operating requirements, an HMI (Human-Machine Interface) developed earlier on a desktop platform can gradually become difficult to maintain, extend with new functions or customize.
For equipment makers, HMI modernization is not just a change of display technology. The more important task is to migrate the interface platform, carry over existing functions, maintain integration with the control software, and make room for future changes as well as compatibility with AI.
ARIS has experience co-developing software for semiconductor equipment, including HMI, Equipment Control, Host Communication and Simulator.
In particular, ARIS was directly involved in migrating an entire HMI system from a Desktop Application to a Web Application using ReactJS and TypeScript, and implemented a mechanism to configure the interface at runtime without rebuilding the application.
This article shares the technical capabilities ARIS has delivered, along with the issues to consider when migrating and modernizing HMIs for industrial equipment.
Full HMI Migration
1. Full HMI Migration – Moving the entire HMI from desktop to web
An HMI system is not just a set of display screens. It is also where operators monitor equipment status, perform operations and interact with functions provided by the control software.
Migrating a desktop HMI to a web HMI is therefore not simply rebuilding the interface with new technology.
Issues to consider during the migration include:
Interaction with Equipment Control
Review the connection points and the information-exchange mechanism between the HMI and the control software.
Behavioural consistency
Assess the ability to keep the necessary operating functions when moving to the new platform.
Integration and testing
Verify HMI functions and how they work with automation and AI software components.
ARIS took part in a Full HMI Migration, moving the entire HMI system from a Desktop Application to a Web Application rather than only developing or replacing a few individual screens.
In the migration project, ARIS used ReactJS and TypeScript to develop the web HMI.
This experience lets ARIS approach Legacy HMI Modernization from the perspective of the whole interface system, rather than focusing only on frontend technology.
The scope of changes to Equipment Control needs to be assessed separately for each system’s architecture. Migrating the HMI does not by default require rewriting the entire control software.
Web-based HMI
2. Web-based HMI – ReactJS, TypeScript and communication with Equipment Control
A semiconductor equipment HMI needs to exchange information with the control software to support status display and operational interaction.
In the web HMI system ARIS helped develop, ReactJS and TypeScript were used for the interface layer, while REST API and WebSocket were used to communicate with Equipment Control.
The components have different responsibilities:
Web HMI
Provides the display interface, receives user operations and presents equipment-related information.
Equipment Control
Handles the equipment control functions.
REST API and WebSocket
Provide the communication mechanisms between the web HMI and Equipment Control.
Using web technology for the HMI does not mean moving real-time control logic into the browser.
In industrial equipment software development, responsibilities between the interface and control components must be clearly defined, while also considering requirements for communication, integration and stable operation.
ReactJS and TypeScript offer one technology option for developing a web HMI interface. However, the suitability of the solution still needs to be assessed against each system’s real requirements, including maintainability, equipment lifecycle and specific operating conditions.
Everything Configurable
3. Everything Configurable – Changing HMI configuration at runtime without a rebuild
One challenge in HMI development is the need to change the interface by equipment model, product version or purpose-specific requirements such as maintenance, operation and setup.
In traditional development, interface changes can require modifying source code, rebuilding the application and releasing a new software version.
ARIS implemented Everything Configurable in a real HMI system, allowing the interface configuration to change at runtime without rebuilding the application, for components designed to support configuration.
The interface architecture uses the following component groups:
WidgetsComponentsPages
These components are used to organize and develop the HMI interface. The specific configuration scope depends on the system design.
The System Owner decides which interface configuration to apply. Specific operating roles, permission to make changes and the configuration management process need to be defined according to each project’s requirements.
What sets Everything Configurable apart is the ability to change configuration at runtime, rather than only reusing interface components during programming.
Two cases need to be clearly distinguished:
Changes within the supported configuration scope
Can be made without rebuilding the application.
Requests outside the configuration scope
May require source code changes or new functionality.
In other words, Everything Configurable does not mean every HMI function can be changed without programming.
HMI Customization
4. HMI Customization and Next-Generation HMI – Built to carry forward and extend
Equipment makers may need to change the interface for various requirements, such as developing a new model, adding functions or meeting each customer’s operating needs.
If every change requires developing and maintaining a separate HMI system, the maintenance workload can grow with the number of product versions.
An HMI architecture that supports runtime configuration makes it possible to reuse existing interface components and meet customization requirements within the designed scope.
Drawing on its Everything Configurable implementation, ARIS can approach HMI Customization in two ways:
Use existing configuration capabilities
Assess whether a change request can be met through the components and configuration mechanisms already supported.
Develop additions when needed
Identify new requirements that fall outside the configuration scope and need to be implemented through software development.
This approach distinguishes between customization through configuration and extending functionality through programming.
For Next-Generation HMI projects, ARIS’s Full HMI Migration and Runtime Configurable UI experience is a technical foundation to draw on when designing interfaces for future equipment generations.
The goal is not only to use new technology, but to build a system that can be maintained, inherited and developed in line with the equipment lifecycle.
Development & testing
5. Experience developing and testing semiconductor equipment software
HMI development for semiconductor equipment requires coordination with related software and hardware components.
Besides HMI, ARIS has experience co-developing Equipment Control, Host Communication and Simulator, along with technical requirements related to SEMI Standards.
During equipment software development, fully reproducing a large machine with many hardware modules in a lab environment may not be feasible.
To support development and testing, ARIS works with clients and technical partners to build lab environments using simulated or functionally equivalent hardware modules combined with automation tools and AI.
One example of integration capability is the joint setup of an EtherCAT Master connected to Slaves to control and test various types of motors automatically.
This environment helps verify suitable software functions before integration with the real equipment.
However, simulators and lab environments do not fully replace testing and verification on the real machine.
Experience developing multiple components of an equipment software system lets ARIS approach HMI Migration, Modernization and Customization projects with attention not only to the interface but also to the integration of the whole system.
FAQs
FAQs on HMI Migration and Web HMI
Not necessarily.
If the existing system has, or can be given, a suitable communication interface, migrating the HMI layer can be considered without rewriting all of Equipment Control.
The actual scope of change depends on each system’s architecture and requirements.
No.
Changes within the runtime configuration scope the system was designed to support can be made without rebuilding the application.
New functions or requests outside the configuration scope may still need additional development.
The System Owner decides which configuration to apply.
Operating permissions, approval processes and configuration management are defined according to the system’s specific requirements.
They can be suitable for the display and interaction layer.
ARIS has used ReactJS and TypeScript in real web HMI development.
However, each system needs to be evaluated for communication requirements, performance, stability and long-term maintenance. Real-time control functions need to be handled in the appropriate software components.
Yes, for suitable functions.
Simulators or lab environments can support testing of part of the interface functions, communication and software integration.
Final verification on the real equipment still needs to be carried out as the project requires.
Talk to ARIS
Talk to ARIS about your HMI project
If your company is considering migrating a legacy desktop HMI to a web HMI, upgrading an equipment interface or developing an HMI configurable at runtime, ARIS is ready to discuss technical requirements and implementation options.
Initial discussions can include:
Technical Discussion
Clarify goals, functional scope and technical issues in the current system.
HMI Technical Assessment
Review the interface architecture, the communication mechanism with Equipment Control and the scope to migrate.
Proof of Concept (PoC)
Discuss a trial implementation of a suitable functional scope before deciding on full-scale development.
ARIS respects clients’ information security requirements. Both parties can sign a non-disclosure agreement (NDA) before exchanging system documents, architecture or other sensitive technical information.