Sequence
Run ordered states with controlled transitions, timers, pause/resume, stop routines, and completion behavior.
Licensable process-control softwareSequence logic built once.
Applied to many machines.
KleanKontrol I/O is the reusable software foundation behind BottleMaster and VeggieMaster—and a licensable engine for other defined, serviceable equipment sequences.
Configurable profilesProtected service toolsReusable Control architecture
KleanKontrol I/O · RuntimeConfigured profile · Online
Active stateActive process state
01:20
1Phase A
2Phase B
3Phase C
4Phase D
5Phase E
Output A
Output B
Output C
Output D
Output E
Output F
Product brief
A control foundation—not a single-machine program.
KleanKontrol I/O defines how a physical process moves from state to state, which outputs may run, which conditions take priority, how time is measured, and how operators and technicians interact with the equipment.
Machine-specific behavior is expressed through profiles, mappings, labels, and application modules rather than rebuilding the entire control structure for each use.
Map I/O
Connect logical functions to relays, valves, actuators, pumps, indicators, buttons, and sensors.
Enforce
Prevent conflicting outputs and give abnormal-state priorities authority over normal operation.
Software architecture
A layered foundation keeps each application consistent and adaptable.
The product is organized to support different applications without publishing application-specific implementation details.
01Execution
Workflow foundation
Defined phases, transitions, timing, and completion behavior.
02Configuration
Application profiles
Application settings and retained configuration.
03Hardware
Equipment interface
Application functions connected to the selected equipment interface.
04Integrity
Protected operating rules and priorities
Protected operating rules and response priorities.
05Access
User and service access
Clear operation paired with appropriate support and service access.
06Records
Records and connectivity
Selected records, status information, alerts, and integration options.
Interactive sequence model
Every process phase has a defined purpose.
Select a step to see how the same runtime structure can change physical behavior while retaining interlock discipline.
Example sanitation sequence
Active sequence state
00:18Phase A
OutputOutput A
OutputOutput B
OutputOutput C
OutputOutput D
OutputOutput E
OutputOutput F
Drain actuator closes through an protected output path.
Control capabilities
Designed for repeatable physical execution.
Deterministic states
Each application phase has a defined purpose and transition.
Configurable profiles
Application settings can be configured for the intended equipment.
Output interlocks
Protected operating rules help prevent incompatible actions.
Pause and resume
Pause and resume behavior is defined for the selected application.
Priority stop routines
Priority responses can move the application into a defined service state.
Service access
Appropriate service access supports maintenance and support work.
Machine identity
Selected application records can accompany the equipment.
Integration path
Interfaces and notifications can be selected for the project.
Commercial use
Three ways KleanKontrol I/O creates value.
KitchenKontrol machines
BottleMaster and VeggieMaster use the engine as the control foundation beneath their application-specific hardware and profiles.
Equipment-builder license
A defined license can support integration into another builder’s machine while preserving ownership and permitted use boundaries.
Custom process project
KitchenKontrol can configure a new sequence, I/O map, operator interface, and service layer for a specific equipment design.
Application package
What a configured control project can include.
| Deliverable | Function | Application-specific |
|---|---|---|
| Sequence definition | Defined workflow and completion behavior | Yes |
| I/O map | Application functions connected to equipment | Yes |
| Interlock matrix | Protected operating rules and priorities | Yes |
| Operator interface | Status, controls, and prompts | Yes |
| Service interface | Selected settings and support records | Yes |
| Acceptance test plan | Planned project acceptance | Yes |
KleanKontrol I/O FAQ
A reusable engine with defined boundaries.
No. Cleaning equipment is the first proven application family. The engine is intended for other defined sequences involving pumps, valves, actuators, heaters, dosing, indicators, and operator controls.
A license grants defined use rights under the applicable agreement. Product ownership, permitted machines, transfer rights, support, updates, and modification boundaries are established in the license terms.
Yes. The purpose of the I/O layer is to map logical functions to the selected controller, pins, relays, sensors, and actuators without changing the business identity of the engine.
Profiles, service credentials, identity records, application modules, and access boundaries can separate operator use from technician configuration and builder-level engineering work.
KleanKontrol I/O
Start a projectBuild the application on a control foundation designed to be reused.
Start with the physical sequence, I/O list, failure priorities, operator workflow, and service requirements.