Structured Configuration. Live Reconfiguration.
Why It Matters
Many thin film control systems still rely on:
- INI files
- Static text configuration
- Restart-required changes
- Manual edits
- Fragile migration workflows
Configuration should not feel like surgery.
It should feel like structure.
JSON-Based, Human-Readable
UnicornOne uses a structured JSON configuration model.
Clear hierarchy.
Logical grouping.
Machine-readable and human-readable.
You can:
- View the full system configuration in a structured tree
- Edit specific sections without touching the whole
- Enable or disable individual ports, devices, or control loops
- Add, edit, or remove components
No guesswork.
No brittle text edits.
GUI-Assisted Editing
Configuration is not buried in text files.
It is managed through an intuitive interface.
You see:
- Device groups
- Communication ports
- Control loops
- Tool bindings
- Dependencies
Changes are visual.
Transparent.
Immediate.
Live Reconfiguration
Apply changes to the live system.
Watch the system reconfigure in real time.
- Enable a new port
- Disable a device
- Add a simulated driver
- Modify loop parameters
No full reinstall.
No manual rewiring of software.
The system updates safely and predictably.
Safe by Design
Configuration changes are:
- Versioned
- Backed up
- Reversible
Accidental errors are prevented.
Malicious changes are detectable.
System integrity is preserved.
Coming Soon: Third-Party Configuration Migration
Upgrading control software is often blocked by migration fear.
“Will we have to rebuild everything?”
UnicornOne is developing a configuration generator that can:
- Parse legacy vendor configuration files
- Extract hardware mappings
- Generate structured JSON for UnicornOne
- Reuse existing hardware definitions
This removes friction.
It removes manual labour.
It accelerates modernization.
Proven in Practice
We have already implemented this internally:
EPIC → UnicornOne migration for PDI Berlin.
PDI are currently the only lab running EPIC.
But every system starts somewhere.
Migration does not need to be painful.
The Philosophy
Configuration should be:
- Structured
- Transparent
- Live
- Reversible
Not fragile.
Not hidden.
Not feared.
We do not sell AI while living in legacy architecture.
We modernize the foundation first.
So within.
As without.
Bizmuth 