Prepare
Confirm the load and selected operating profile.
Dedicated produce-cleaning machineDisciplined cleaning control
for vegetables and fruit.
VeggieMaster applies the KleanKontrol I/O sequencing model to fresh-food preparation, with application-specific treatment, circulation, dwell, drain, and rinse profiles.
Purpose-built equipmentProfile-driven workflowsBuilt on a configurable control foundation
Product brief
Built on a configurable control foundationApplication-specific sequence and Process mapping on a reusable control engine.
Fresh-food cleaning with repeatable machine discipline.
VeggieMaster is a separate equipment product for vegetable and fruit cleaning applications. Hardware, basket design, water movement, treatment method, timing, and handling requirements are selected around the target produce and operating workflow.
The shared control foundation brings ordered states, configurable timing, protected profiles, output interlocks, operator clarity, and service access into the application.
Built on a configurable control foundationApplication-specific sequence and Process mapping on a reusable control engine.Illustrative workflow
Produce profiles built from defined phases.
Final sequence design depends on produce type, treatment method, equipment geometry, throughput, and the validated operating procedure.
Fill / treat
Run the selected preparation phase.
Clean / circulate
Apply the configured process action.
Dwell
Hold for the configured application phase.
Drain
Transition through the configured completion path.
Rinse
Complete the workflow and return to a ready condition.
Application profiles
Different produce calls for different handling.
Profiles are engineering inputs—not universal sanitation claims. Final settings require process validation for the actual food, equipment, chemistry, and operation.
Leafy produce
Lower-impact water movement, controlled dwell, basket handling, and rinse behavior designed around delicate product.
Gentle handlingFirm vegetables
Profiles can support longer circulation, different agitation, or staged rinse behavior where the equipment design permits.
Defined movementFruit and mixed loads
Application design considers buoyancy, surface characteristics, loading method, cross-contact controls, and rinse requirements.
Application specificApplication model
The profile may change. Process authority does not.
Defined states
Each application phase carries a clear operating purpose and transition condition.
Allowed outputs
Water, treatment, circulation, drain, and rinse functions run only in assigned states.
Interlocked motion
Conflicting actuator directions and incompatible outputs are excluded by the application logic.
Profile retention
Timing and process values can be protected and retained for the selected produce workflow.
Operator clarity
Current phase, time, prompts, pause, stop, and completion remain visible and consistent.
Serviceability
Technician access supports diagnostics, output tests, profile review, identity, and records.
Machine design inputs
Application engineering starts with the food and workflow.
Produce characteristics
Fragility, geometry, buoyancy, surface texture, soil load, and batch size.
Process action
Fill depth, flow pattern, circulation, spray, agitation, drain path, and rinse coverage.
Treatment method
Approved chemistry, concentration approach, dosing equipment, dwell, and verification needs.
Operating workflow
Loading, unloading, baskets, throughput, cleaning between loads, and operator responsibilities.
Development path
Designed and commissioned as a real machine application.
Define use
Document produce groups, throughput, validated process goals, utilities, and site constraints.
Engineer hardware
Select vessel, baskets, water path, treatment delivery, drain design, enclosure, and service access.
Configure control
Build the application sequence, I/O map, profiles, interlocks, interface, and records.
Validate operation
Bench test, wet commission, calibrate profiles, verify abnormal states, and record acceptance.
VeggieMaster FAQ
A distinct machine built on shared control logic.
No. VeggieMaster is a separate machine product. The products share KleanKontrol I/O as a control foundation, but hardware, loading, water movement, treatment, profiles, and acceptance criteria are application-specific.
No. Produce groups can require different handling, water movement, contact time, chemistry, and rinse conditions. Profiles must be tied to the actual validated operating process.
The reusable engine supports the same principles—protected profiles, diagnostics, event records, identity, timing, and I/O tests—while application details remain specific to VeggieMaster.
Yes. Physical layout, batch size, utilities, loading, treatment method, rinse path, operator interface, and service access are part of the project definition.
VeggieMaster
Start a projectBuild produce cleaning around a defined, repeatable workflow.
A VeggieMaster project starts with produce groups, validated process requirements, throughput, utility limits, handling, and commissioning criteria.