Control software for manufacturing and automotive
Safety-critical operation, specialized devices and tools that have to last many years: we build control software and interfaces for labs and automotive.
What we have built in this industry
What we know from this industry
What we often find
- Safety-critical operation
- Specialized devices and proprietary interfaces
- Tools with a lifespan of many years
- Several partners in one project
- Consistency across a growing portfolio
What we make of it
- Control software with fail-safe mechanisms
- Real-time monitoring of critical parameters
- Component libraries for internal tools
- Windows, web and embedded interfaces
- Technical leadership in multi-partner projects
Interfaces that are part of workplace safety
In manufacturing and automotive, user interfaces are not a convenience. If a lab fume hood cannot be operated reliably, the work around it is affected. Internal tools run for years and have to stay consistent, maintainable and extensible.
For Waldner we built control software for explosion-proof lab fume hoods and a dashboard for lab management. For Alps Alpine, a component library on which internal tools for production and sales are built.
We combine frontend expertise with integration of specialized devices and industrial safety requirements.
The typical situation
In a lab there are often only a few control points from which several fume hoods are operated together. Clarity, robustness and the connection to the devices have to come together there. Internal tools such as configurators, dashboards and tools for production and sales run for years and, without a shared foundation, get rebuilt from scratch every time.
How we approach it
- Central control: For Waldner we built a control display that operates the lab fume hoods together, connected to the client's hardware.
- A shared component foundation: For Alps Alpine we built a React-based component library, documented in Storybook and safeguarded visually with Storyshots.
- Setup and pipeline from one team: build, test environment and deployment, for example with Jest and GitHub Actions.
- Built for handover: Both solutions keep running at the client after the project ends.
The component library for Alps Alpine was built in 12 months by 6 people. We developed the lab control system for Waldner from 2023 to 2025.
Common questions from this industry
What is different about user interfaces in the lab?
They are part of workplace safety. If a lab fume hood cannot be operated reliably, the work around it is affected. For Waldner we developed a central control display that operates the lab fume hoods together. The frontend architecture is designed for clarity in daily lab work. The display is connected to the client's devices and is not a generic industrial UI. It is in production use in Waldner's labs.
When is a component library for internal tools worth it?
When several tools run for years and need to stay consistent. At Alps Alpine that meant configurators, dashboards and tools for production and sales. There we built a React-based component library in 12 months with 6 people. It is documented in Storybook and safeguarded visually with Storyshots. Build, test environment and deployment ran on Jest and GitHub Actions. New tools are now built on a shared foundation.
Does the software keep running without you after the project?
In both manufacturing projects, yes. Internal teams carry the component library for Alps Alpine forward. Our setup was designed for handover from the start. We developed the lab control system for Waldner from 2023 to 2025. It is also still in operation after handover.