Design. Deploy. Understand.
Design control sequences, review equipment state and keep a useful operating history. The bootctrl platform brings these tasks into one workflow, with integration planned for bootctrl hardware.
How it could work in practice
Illustration only. This is not a live connection or the production application.
Define
Use the UI to connect control functions and describe equipment signals.
Validate & package
The backend checks and packages an application artifact for a supported target.
Deploy & run
The local MCR runtime owns the control loop; the service process handles communication.
Observe & recover
Review state and selected history. Retain and recover telemetry within the documented test boundary.
Equipment overview
A simple signal workflow
Scale a signal
Convert a measured value into a useful unit.
REALFactor6OutputREALPublish telemetry
Make the result available to the equipment view.
ANYSignalOUTPUTTelemetry & recoveryTelemetry & recovery
| Signal | Source variable | Configuration | Runtime state |
|---|---|---|---|
| FlowREAL · L/min | flow_sensor.VALUE | ConfigurationDeployed | Runtime stateLive |
| Pump speedREAL · % | pump_command.VALUE | ConfigurationDeployed | Runtime stateLive |
Demonstration of the current store-and-forward path.
Know what is connected
View devices and their reported state across an equipment fleet.
Define and deploy a control workflow
Explore the current MCR control-design and deployment path for a defined local application.
Keep useful operating history
Follow telemetry, runtime status and updates. The current runtime includes offline storage and recovery after reconnection.
Control design
This demo flow scales a signal and sends the result to telemetry. The blocks shown are real platform components.
Equipment overview
A simple signal workflow
Scale a signal
Convert a measured value into a useful unit.
REALFactor6OutputREALPublish telemetry
Make the result available to the equipment view.
ANYSignalOUTPUTTelemetry & recoveryTelemetry & recovery
| Signal | Source variable | Configuration | Runtime state |
|---|---|---|---|
| FlowREAL · L/min | flow_sensor.VALUE | ConfigurationDeployed | Runtime stateLive |
| Pump speedREAL · % | pump_command.VALUE | ConfigurationDeployed | Runtime stateLive |
Demonstration of the current store-and-forward path.
A working software path. A wider hardware roadmap.
The platform software supports control workflows and equipment records. Automated offline-history tests cover retention, reload and deduplication. Integration with bootctrl hardware is planned and still needs development and testing. Seven-day outages, repeated power cycles and long-duration endurance remain to be checked.
Local first. Cloud when it helps.
The local MCR runtime executes the defined control application. A separate service process handles connectivity, telemetry and history. The UI and backend support application design, validation, packaging and deployment. Network reconnection must not become the owner of local control decisions.
TechnologyApplications
Paper-mill auxiliary systems
A wash-water skid is waiting to run. The start command alone cannot explain whether a valve confirmed its position. A local command-and-feedback sequence gives maintenance a more precise question to investigate.
Explore this use caseThermal-skid manufacturers
A customer asks what happens if the connection disappears. Define which circulation steps belong to the local controller and which records belong to the optional connected platform.
Explore this use caseOil-immersed power transformers
Bring load, oil temperature and cooling history together so your team can prepare a more focused inspection. Start with a read-only pilot using existing, qualified monitoring interfaces.
Explore this use caseGood questions, clear answers
Can I see a demo now?
Request a walkthrough of control design, validation, deployment and equipment history. We can discuss the planned connection to bootctrl hardware. The illustrations use simulated data.
Is cloud access required for local control?
The local MCR runtime executes the defined control application. A separate service process handles connectivity, telemetry and history. The UI and backend support application design, validation, packaging and deployment. Network reconnection must not become the owner of local control decisions.
A working software path. A wider hardware roadmap.
The platform software supports control workflows and equipment records. Automated offline-history tests cover retention, reload and deduplication. Integration with bootctrl hardware is planned and still needs development and testing. Seven-day outages, repeated power cycles and long-duration endurance remain to be checked.
What would you like your machine to do better?
Bring a machine sequence, a movement challenge, a structural test or an equipment-service question. Let’s define a useful first evaluation.