Cleaning system and controller integrating treated solutions with surface treatments

Abstract

A cleaning system comprising a water treatment module, a persistent surface treatment dispenser, and an analytics controller. The water treatment module produces a treated solution from mains water an

Description

[0001] FIELD OF THE INVENTION The present invention relates to cleaning systems, controllers and methods. It concerns the production and dispensing of treated aqueous cleaning solutions from on-site or reclaimed water sources, the application of persistent surface treatments, and data-driven control of dispensing, scheduling and reapplication in managed cleaning operations.

[0002] BACKGROUND OF THE INVENTION Cleaning operations across diverse built environments, from industrial and commercial sites to public, healthcare, transport and educational facilities, generally combine multiple processes. Water is supplied as mains water or prepared on site using utilities such as filtration or softening, and may be used directly or combined with detergents or disinfectants. In some facilities protective surface treatments or coatings are also applied. These activities are carried out in separate workflows with little systematic linkage.

[0003] Task scheduling and logging are commonly performed in software or by manual records. Such systems often operate as standalone scheduling and reporting tools, with limited or no direct integration to dosing equipment, application devices or product use data. Consequently, information about when, where, how and by whom products or treatments are applied is not tied directly to the devices that dispense them and integrated into a unified cleaning system, so the process does not operate under closed-loop control. This leads to duplication of effort, wasted product and variable hygiene outcomes.

[0004] More specialised technologies have also been developed. On-site systems generate disinfectant or cleaning solutions from water using electrolytic or ozone processes, and persistent coatings are marketed to reduce re-soiling of treated surfaces. Such technologies are deployed as standalone measures without coordinated control or feedback, and supervisory tools associated with them provide reporting and monitoring rather than providing closed-loop control that spans treated solution generation, persistent surface treatment application and task execution.

[0005] Building services such as heating, ventilation and air conditioning produce blowdown water that is normally discharged as waste. Known practice does not repurpose this stream on site as a source for producing a Treated Solution suitable for cleaning or disinfection, leaving potential reductions in water consumption and chemical use unrealised.

[0006] There is therefore a need for a unified cleaning system that integrates treated solution generation, surface treatment application and task execution under data-driven control.

[0007] DISCLOSURE OF THE INVENTION According to a first aspect there is provided a system for managing cleaning operations, the system comprising: a water treatment module configured to produce a Treated Solution from mains water, HVAC blowdown, or a combination thereof, and optionally from other on-site sources such as rainwater, greywater or condensate; a delivery arrangement coupled to Dispensing Nodes for dispensing the Treated Solution to Designated Areas; and an arrangement for application of a Persistent Surface Treatment to the Designated Areas. Each dispense event of the Treated Solution and each application event of the Persistent Surface Treatment is associated with Assignment Parameters for a Cleaning Assignment and recorded as Operational Input Data. An Analytics Controller is configured to derive a per-area Cleaning Load in dependence on both Treated Solution usage and Persistent Surface Treatment usage, and to generate executable Technical Control Outputs to operate Dispensing Nodes, schedule Cleaning Assignments and plan reapplication of the Persistent Surface Treatment, thereby maintaining a Target Hygiene Standard while aligning with prioritised Performance Objectives in accordance with Weighting.

[0008] According to a second aspect there is provided an Analytics Controller configured to ingest Operational Input Data, including Assignment Parameters associated with dispense events of the Treated Solution and application events of the Persistent Surface Treatment, to derive the Cleaning Load for each Designated Area, to apply Weighting among Performance Objectives, and to generate the Technical Control Outputs for execution by the Dispensing Nodes or other equipment so as to govern dispensing, scheduling and reapplication.

[0009] According to a third aspect there is provided a method of operating a cleaning system, the method comprising: producing the Treated Solution; dispensing the Treated Solution and applying the Persistent Surface Treatment to Designated Areas; recording the associated Assignment Parameters as Operational Input Data; deriving the Cleaning Load; applying Weighting among Performance Objectives; and issuing the Technical Control Outputs for execution to maintain the Target Hygiene Standard while aligning with prioritised Performance Objectives. The foregoing balance is referred to herein as the Scheduling Objective.

[0010] According to a fourth aspect there is provided a computer-readable medium storing instructions which, when executed by processing circuitry, cause the Analytics Controller to ingest Operational Input Data, derive the Cleaning Load and generate the Technical Control Outputs.

[0011] According to a fifth aspect, there is provided a computer program comprising instructions which, when executed by processing circuitry, cause the Analytics Controller to ingest Operational Input Data, derive the Cleaning Load, apply Weighting among Performance Objectives, and generate the Technical Control Outputs as described herein.

[0012] In some embodiments the Operational Input Data further includes Equipment Usage Data, hygiene or cleanliness test results, technical audit results, historical and deployed system data, external contextual data and Operative inputs, enabling the Analytics Controller to re-derive the Cleaning Load, adjust the Weighting, and adapt schedules in response to context and equipment state.

[0013] In some embodiments the Dispensing Nodes require Operative authentication prior to dispensing. In some embodiments when either the Treated Solution or the Persistent Surface Treatment is dispensed into an Applicator Tank, the Assignment Parameters record an equipment identity and a tank capacity, a preset filling metric is used to terminate dispensing at capacity, a manual override or stop / start override is available, and any adjusted volume is recorded.

[0014] In some embodiments, the delivery arrangement dispenses untreated mains water in addition to the Treated Solution, with dispense events for both being logged as Operational Input Data associated with Cleaning Assignments. The Treated Solution may also be delivered in combination with additional dosing components comprising detergents, surfactants, or fragrances under control of the Technical Control Outputs.

[0015] In some embodiments, surplus Treated Solution is conveyed to an external authorised site and may be subject to data-based verification of water quality, system authorisation of the release, or both, prior to discharge, with the release logged using chain-of-custody records.

[0016] In some embodiments the controller detects anomalies and generates maintenance related Technical Control Outputs including filter replacement, pump servicing, purge operations, equipment lockout, usage alerts or service scheduling; the Operational Input Data further includes Operative data relating to workload and assignment; and alerts may be escalated automatically to remote support services.

[0017] BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a schematic overview of a cleaning system comprising a Water Treatment Module for producing a Treated Solution from one or more on-site sources, Dispensing Nodes for delivery to Designated Areas, an arrangement for dispensing a Persistent Surface Treatment, sensors and Interface Inputs for capturing and logging dispense and application events, and an Analytics Controller coupled by a Controller Data Backbone to manage Operational Input Data and generate Technical Control Outputs.

[0018] Fig. 2 is a block diagram of the Analytics Controller (700) configured to ingest Operational Input Data including Interface Inputs, Telemetry Inputs and External Telemetry Inputs, to derive a Cleaning Load in dependence on Treated Solution and Persistent Surface Treatment usage together with contextual data, to apply Weighting among Performance Objectives with enforcement of the Target Hygiene Standard, to perform comparative benchmarking, and to generate Technical Control Outputs for dispensing, scheduling and reapplication.

[0019] Fig. 3 is a flow chart of a method performed by the Analytics Controller to operate the cleaning system in a closed loop, including ingesting and validating Operational Input Data, deriving a Cleaning Load, applying Weighting among Performance Objectives, planning and orchestrating dispensing and reapplication operations, analysing feedback including comparative benchmarking, and continuously adapting Technical Control Outputs to maintain the Target Hygiene Standard.

[0020] Fig. 4 illustrates comparative scheduling examples generated by the Analytics Controller, showing baseline fixed-interval scheduling, data-driven adaptive scheduling derived from Operational Input Data, and weighted scheduling prioritising resource efficiency while maintaining the Target Hygiene Standard.

[0021] Fig. 5 is a schematic of an optional conditional external release arrangement in which surplus Treated Solution from a buffer passes through a Quality Verification Unit to an External Release Port for delivery to an Authorised External Site, with release events recorded by a Chain-of-Custody Logger and enablement or inhibition governed by the Analytics Controller.

[0022] DETAILED DESCRIPTION OF THE EMBODIMENTS

[0023] Definitions and terminology

[0024] Treated Solution As used herein, “Treated Solution” means water that has undergone at least one treatment step so as to render it suitable for use as a Cleaning Solution, a Disinfectant Solution, ora Combined Cleaning and Disinfectant Solution, the suitability of the Treated Solution being verifiable by routine measures known to the skilled person, including, for example, limits on turbidity, conductivity, particulate load, microbial count, oxidation-reduction potential (ORP), or residual active concentration.

[0025] Cleaning Solution As used herein, “Cleaning Solution” means a Treated Solution that is capable of loosening, dissolving, or removing, for example, soils, dirt, grease, or other non-microbial contaminants from a surface, with or without antimicrobial action, thereby maintaining visual or functional cleanliness.

[0026] Disinfectant Solution As used herein, “Disinfectant Solution” means a Treated Solution that itself exhibits antimicrobial activity sufficient to achieve a hygiene performance threshold. The antimicrobial activity may be imparted by chemical or biological means, and is verifiable by routine measures known to the skilled person, including, for example, oxidation-reduction potential (ORP), microbial log-reduction testing, or residual active concentration.

[0027] Combined Cleaning and Disinfectant Solution As used herein, “Combined Cleaning and Disinfectant Solution” means a Treated Solution that provides both cleaning activity and disinfectant activity in a single application, such that, for example, soils, dirt, or grease are removed while microbial contamination is simultaneously reduced or eliminated.

[0028] Dispensing Node As used herein, “Dispensing Node” means a controlled dispensing point configured, under control of the system, to deliver a Treated Solution or an alternative water source for cleaning, for example untreated mains water, any of the foregoing being deliverable individually or in combination. A Dispensing Node incorporates at least a mechanism for controlled release and functionality enabling association of dispense events with Assignment Parameters for inclusion in the Operational Input Data, whether implemented locally at the node or by other components of the system.

[0029] Surface Treatment Dispenser As used herein, “Surface Treatment Dispenser” means a controlled dispensing arrangement configured, under control of the system, to deliver a Persistent Surface Treatment into an Applicator Tank for subsequent application to a Designated Area, the Surface Treatment Dispenser incorporating functionality enabling association of dispense events, recorded within the system as application events of the Persistent Surface Treatment, with Assignment Parameters for inclusion in the Operational Input Data. The Surface Treatment Dispenser may further include features for dilution with water and purge cycles, whether implemented locally at the dispenser or by other components of the system.

[0030] Assignment Parameters As used herein, “Assignment Parameters” means contextual data linked to (i) each dispense of Treated Solution or alternative water source, (ii) each application of a Persistent Surface Treatment, and (iii) any Cleaning Assignment executed without a dispense. Such parameters may include Operative identity, Operative Location, Designated Area, equipment identity where applicable, task type, and timing markers comprising initiation, acceptance, pausing, and completion. The Assignment Parameters form part of the Operational Input Data for processing by the Analytics Controller and may reference associated Equipment Usage Data for the relevant Cleaning Assignment.

[0031] Equipment Usage Data As used herein, “Equipment Usage Data” means data indicative of operation of system components or external cleaning equipment relevant to cleaning operations, ingested as part of the Operational Input Data. Such data may be obtained from assignment-derived inputs, such as equipment identity, task type, or timing markers, from telemetry signals generated by system components or external equipment, such as runtime, power consumption, or filter life, or from both sources in combination. Equipment Usage Data encompasses equipment operated by an Operative or by an autonomous device. Where a Cleaning Assignment is performed without equipment, Equipment Usage Data need not be present.

[0032] Operational Input Data As used herein, “Operational Input Data” means data ingested by the Analytics Controller, including Assignment Parameters; Equipment Usage Data; hygiene or cleanliness test results; quality verification outcomes and chain-of-custody records; audits and inspections; Operative inputs and feedback, or availability indicators including Operative absence; external contextual data; historical or deployed system data; and, where available, aggregated data from multiple deployments, for use in analysis by the Analytics Controller to generate and adjust Technical Control Outputs.

[0033] Analytics Controller As used herein, “Analytics Controller” means a processor-implemented control component operatively coupled to the Dispensing Nodes, the Surface Treatment Dispenser, sensors, or Operative inputs and configured to ingest Operational Input Data and, responsive thereto, to generate Technical Control Outputs for operation of the system. The Analytics Controller may be realised in software executed on general-purpose processors, in embedded firmware, as a distributed or cloud-based service, or as any combination thereof, and may be centralised or implemented across multiple devices or modules without departing from the scope of this definition.

[0034] Technical Control Outputs As used herein, “Technical Control Outputs” means control signals generated by the Analytics Controller that correspond to operating parameters of the system. These include dosing adjustments; scheduling and reapplication changes; adaptations to cleaning task parameters such as timing, frequency or sequencing; water source prioritisation; and initiation of machine-readable maintenance instructions or alerts. The Technical Control Outputs are executable at the Dispensing Nodes, external cleaning equipment, or other system components, consistent with the Scheduling Objective.

[0035] Persistent Surface Treatment As used herein, “Persistent Surface Treatment” means a treatment that remains active on a surface for an extended duration, the treatment providing one or more of: (i) antimicrobial activity, protection against contamination, or facilitation of subsequent cleaning; (ii) reduction in cleaning frequency, chemical consumption, or time to clean; and (iii) maintenance of hygiene standards or asset protection.

[0036] Cleaning Assignment As used herein, “Cleaning Assignment” means a task or set of tasks to be carried out in a cleaning operation, defined in relation to a Designated Area, schedule, or event, and linked to one or more dispense events of Treated Solution or application events of Persistent Surface Treatment.

[0037] Designated Area As used herein, “Designated Area” means a spatially defined portion of a site identified for cleaning or treatment, the association of dispense events of the Treated Solution and application events of the Persistent Surface Treatment with Designated Areas enabling accountability and scheduling control of cleaning operations.

[0038] Operative As used herein, “Operative” means a human cleaning staff member, autonomous cleaning agent, or other authorised user or agent of the system who performs cleaning or treatment tasks. The Operative’s identity is associated with Assignment Parameters, and the Operative’s inputs or feedback may form part of the Operational Input Data.

[0039] Cleaning Load As used herein, “Cleaning Load” means a derived parameter representing the aggregate intensity of cleaning or treatment activity for a Designated Area, the Cleaning Load being derived from the Operational Input Data including, for example, dispensed volumes of Treated Solution, application events of Persistent Surface Treatment, number of Operatives assigned, spill-response or spot-clean records, hygiene or cleanliness test results, and related variables. Once derived, the Cleaning Load is itself treated as part of the Operational Input Data for subsequent analysis by the Analytics Controller.

[0040] Site Maintenance Data As used herein, “Site Maintenance Data” means information indicative of maintenance activity or access restrictions affecting a Designated Area, including for example scheduled works, shutdowns, or temporary closures, such information being ingestible by the Analytics Controller to condition scheduling or adjustment of Cleaning Assignments. Site Maintenance Data may be treated as a subset of External Contextual Data forming part of the Operational Input Data. [0041 ] Applicator Tank As used herein, “Applicator Tank” means a vessel or reservoir into which a Persistent Surface Treatment is dispensed for application, for example, a pump-sprayer tank, a handheld electric sprayer reservoir, or a machine-feed tank, the Applicator Tank serving as the working container from which the treatment is applied to a Designated Area.

[0042] Weighting As used herein, “Weighting” means an adjustment applied by the Analytics Controller when generating Technical Control Outputs, the adjustment establishing the relative importance of multiple Performance Objectives, whether complementary or competing. The Weighting may be implemented using fixed coefficients, rule-based adjustments, machine-learning models, or other computational methods, and may be configured at different levels of scope including, for example, across deployments, at deployment level, per site, per Designated Area, or per Cleaning Assignment.

[0043] Performance Objectives As used herein, “Performance Objectives” means configured targets and priorities for cleaning operations that define desired outcomes, including maintaining a Target Hygiene Standard, protecting asset condition and appearance, improving efficiency of labour or resource use, and achieving sustainability goals such as reduced water, energy, or chemical consumption. Performance Objectives may be set based on regulatory standards, hygiene or cleanliness testing, audit results, sustainability targets or operational efficiency metrics. Performance Objectives are applied by the Analytics Controller, in combination with Weighting, to guide generation of the Technical Control Outputs.

[0044] Target Hygiene Standard As used herein, “Target Hygiene Standard” means a configured baseline hygiene threshold for a site or Designated Area, established by system operation using the Treated Solution and the Persistent Surface Treatment in accordance with the Cleaning Assignments. The Target Hygiene Standard may be increased in accordance with configured thresholds derived from hygiene or cleanliness testing, audit results, or configured Performance Objectives, but is not reduced below the baseline except where the Designated Area is classed as vacant. The Target Hygiene Standard is enforced by the Analytics Controller when generating the Technical Control Outputs.

[0045] Scheduling Objective As used herein, “Scheduling Objective” refers to the configurable control parameter applied by the Analytics Controller when generating or adjusting Cleaning Assignments and related Technical Control Outputs, representing the balance between maintaining the Target Hygiene Standard and aligning with prioritised Performance Objectives according to any configured Weighting.

[0046] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings. It will be understood that the drawings are diagrammatic and not to scale, and that features from different embodiments may be combined unless technically incompatible.

[0047] Fig. 1 - System Overview As shown in Figure 1, a cleaning system comprises a Water Treatment Module (106) configured to produce a Treated Solution suitable for use as a Cleaning Solution, a Disinfectant Solution, or a Combined Cleaning and Disinfectant Solution. Water may be received from mains water (101), HVAC blowdown (102), greywater (103), rainwater (104) or condensate (105). Intake from these sources may be managed by a Source Selector (107) provided with an Automatic Source Switch (108), enabling prioritisation of on-site streams with automatic fallback to mains water (101). The Treated Solution may be passed through a Treated Solution Buffer (109) arranged downstream of the Water Treatment Module (106) and conveyed by a Treated Solution Pipeline (111). A Dosing Module (110) may be provided to regulate or augment the Treated Solution with additional dosing components under control of the system.

[0048] One or more Dispensing Nodes (113) receive the Treated Solution via the Treated Solution Pipeline (111) and deliver it to Designated Areas (900). Each Dispensing Node (113) includes a controlled Dispense Valve (114) and may incorporate a Flow Meter (115) and a Metered Fill function (116) to permit controlled delivery through an Outlet (124), to a receiving vessel or directly to the point of use. In some embodiments an Untreated Mains Dispense Line (112) is provided so that untreated mains water (101) can be dispensed under system control, with such dispense events logged as part of the Operational Input Data.

[0049] The system may further include an arrangement for application of a Persistent Surface Treatment. A Surface Treatment Dispenser (122) delivers the treatment, for example into an Applicator Tank (119), for subsequent application to the Designated Areas (900). The Surface Treatment Dispenser (122) may include a Dispense Valve (114), a Flow Meter (115), a Metered Fill function (116) and an Outlet (124), and may provide dilution with water and purge operations as required.

[0049] Operational sensing and logging are provided by telemetry sources including the Water Treatment Module (106), Source Selector (107), Automatic Source Switch (108), Dosing Module (110), Untreated Mains Dispense Line (112), Treated Solution Buffer (109), Dispensing Node (113), Dispense Valve (114), Flow Meter (115), Metered Fill (116), Level Sensor (117), Waste Monitor (118), Quality Verification Unit (120) and Chain-of-Custody Logger (121). External sensing and context may be provided via External Telemetry Inputs (200), which can include Application-site Sensors (201), Equipment Usage Signals (202) and External Contextual Signals (203).

[0050] User and supervisory interaction may be provided by an Interface (800). Interface Inputs (300) may include Assignment Parameters (301), Hygiene or Cleanliness Test Results (302), Technical Audit Results (303), Historical or Deployed Data (304), Operative Inputs and Authentication (305) and Stop or Start Override (306). Interface Outputs (500) may include Cleaning Assignment Scheduling Control (501), Surface Treatment Scheduling Control (502), Lockouts and Management Holds (503), Acknowledgement and Recovery (504), Verification Requests (505), Adaptive Updates (506) and Alerts and Prompts (507).

[0051] Control signalling to field equipment may include Telemetry Outputs (400) such as Dispensing Node Control (401), Surface Treatment Control (402), Dosing Module Regulation Control (403), Source Selection and Switching Control (404), Buffer Refill Enable or Inhibit Control (405) and Untreated Mains Dispense Control (409). These signals act on the physical apparatus to execute the required operations.

[0052] An Analytics Controller (700) is shown centrally and is operatively coupled by a Controller Data Backbone (770) to receive Operational Input Data from the telemetry sources and Interface Inputs (300) and to issue Technical Control Outputs, including the Telemetry Outputs (400) and Interface Outputs (500). Through these connections, dispense events of the Treated Solution and application events of the Persistent Surface Treatment are associated with Assignment Parameters for each Cleaning Assignment and are recorded for analysis, planning and execution consistent with the Scheduling Objective and Target Hygiene Standard.

[0053] In certain embodiments, the Analytics Controller (700) is realised as a modular component within the same inventive system architecture. It is functionally integral to the apparatus but may be deployed in different configurations according to site or operational needs. Through the Controller Data Backbone (770) it may interface with the Treated Solution apparatus, with the Surface Treatment Dispenser (122), or with both concurrently. When connected to one apparatus family only, it governs that subsystem within the unified control framework, delivering partial system functionality derived from the same inventive principles. When connected to both, it coordinates dispensing, reapplication and scheduling functions to achieve full closed-loop operation consistent with the Scheduling Objective. This configurability allows phased installation and adaptive integration across sites while maintaining a single inventive system that operates as a coherent whole.

[0054] Arrows in the drawing distinguish between fluid flow, shown as solid lines with arrows; data inputs to the Analytics Controller (700), shown as dashed lines; and control signals from the Analytics Controller (700), shown as dot-dash lines, as indicated in the legend. Telemetry Inputs shown in Figure 1 are schematic and encompass all Operational Input Data, including data from additional apparatus not individually depicted.

[0055] Fig. 2 - Analytics Controller Internals As shown in Figure 2, Operational Input Data (106-399) are received from three groupings: Interface Inputs (300) comprising Assignment Parameters (301), Hygiene or Cleanliness Test Results (302), Technical Audit Results (303), Historical or Deployed Data (304), Operative Inputs and Authentication (305) and Stop or Start Override (306); Telemetry Inputs from apparatus including the Water Treatment Module (106), Source Selector (107), Automatic Source Switch (108), Treated Solution Buffer (109), Dosing Module (110), Dispensing Node (113), Dispense Valve (114), Flow Meter (115), Metered Fill (116), Level Sensor (117), Waste Monitor (118), Applicator Tank or application monitor (119) and Quality Verification Unit (120); and External Telemetry Inputs (200) including Application-site Sensors (201), Equipment Usage Signals (202) and External Contextual Signals (203).

[0056] External Telemetry Inputs (200) may further include Site Maintenance Data, comprising notifications of repair works, access restrictions, or area shutdowns. Such data enable the Analytics Controller (700) to coordinate or defer Cleaning Assignments in affected Designated Areas, maintaining safe and efficient operation while upholding the Target Hygiene Standard.

[0057] Operational Input Data are ingested by the Analytics Controller (700) via the Controller Data Backbone (770) from one or more sensors, devices, or data channels associated with the apparatus and environment. These include Interface Inputs (300) originating from an Interface (800) that provides the communication point between the Analytics Controller (700) and human operators or supervisory systems. The Interface (800) may be implemented as a local terminal or a remote, network-connected interface, depending on site configuration, and may be configured for operative use or supervisory management. Functionally, it distributes cleaning assignments and receives controls and confirmations such as operative acknowledgements, audit inputs or overrides, forming the bidirectional feedback mechanism that sustains closed-loop operation.

[0058] The Analytics Controller (700) functions as the intelligent core of the system. It continuously transforms raw Operational Input Data into executable Technical Control Outputs that maintain and optimise cleaning operations in real time. By evaluating sensor, user and contextual inputs against the Scheduling Objective, Performance Objectives and Target Hygiene Standard, the controller determines when, where and how cleaning or reapplication events should occur. This enables autonomous scheduling, adaptive dosing and performance correction without human recalibration, forming the technical basis of the system’s closed-loop control. The layers described below represent successive processing stages that collectively deliver this continuous optimisation.

[0059] Within the Analytics Controller (700), input handling begins at a Telemetry Layer (710) that ingests and normalises signals for processing, for example through Telemetry Ingestion and Normalisation (711) and communication handling by Gateway functions (712). A Safety and Fault Layer (720) monitors for hazards and abnormal conditions with Fault Detection and Safety Interlocks (721), permitting safe handling or early intervention before or in parallel with higher-level decisions.

[0060] An Analytical and Decision Layer (730) interprets the Operational Input Data using configured objectives and learned context. Sub-components include a representation of the Target Hygiene Standard (731), a Weighting Layer (732) to establish relative priorities among Performance Objectives (733), a Cleaning Load Layer (734) that derives a Cleaning Load per Designated Area, Treated Solution Usage monitoring (735) and Persistent Surface Treatment Usage monitoring (736), and a Comparative Benchmark Layer (737). The Comparative Benchmark Layer (737) enables evaluation of relative performance among Designated Areas and across comparable deployed systems operating under the same architecture, supporting optimisation through analysis of usage, hygiene and operational efficiency patterns. Output from this layer forms the basis for control decisions.

[0061] A Scheduling and Planning Layer (740) translates decisions into time-based plans, comprising a Cleaning Assignment Scheduler (741) and a Persistent Surface Treatment Reapplication Planner (742). Execution timing and multi-signal coordination are handled by a Control Orchestration Layer (750), which includes a Control Orchestrator (751) and a Time Base and Event Clock (752) to sequence Technical Control Outputs deterministically.

[0062] Reporting and data retention are implemented by an Outbound Information and Reporting Layer (760) that includes an Outbound Information and Data Manager (761) and a Controller Data Store (762). These components manage storage, generation and export of Outbound Information and Reporting Data (600, 601) where required.

[0063] The controller issues Technical Control Outputs (400-601) back over the Controller Data Backbone (770) as indicated by the Operational Output Data Flow. These outputs include Telemetry Outputs (400) such as Dispensing Node Control (401), Surface Treatment Control (402), Dosing Module Regulation Control (403), Source Selection and Switching Control (404), Buffer Refill Enable or Inhibit Control (405) and Untreated Mains Dispense Control (409); Interface Outputs (500) including Cleaning Assignment Scheduling Control (501), Surface Treatment Scheduling Control (502), Lockouts and Management Holds (503), Acknowledgement and Recovery (504), Verification Requests (505), Adaptive Updates (506) and Alerts and Prompts (507); and Outbound Information and Reporting Data (600, 601) for supervisory or external systems.

[0064] The arrangement operates in a closed loop. As Technical Control Outputs are executed by field equipment and users, the resulting dispense events of the Treated Solution and application events of the Persistent Surface Treatment, together with Equipment Usage Data, hygiene or audit results, Site Maintenance Data, and other contextual information, are captured as new Operational Input Data. The Analytics Controller (700) continuously re-derives the Cleaning Load, applies Weighting among Performance Objectives, and adapts scheduling, dispensing and reapplication while enforcing the Target Hygiene Standard, thereby maintaining continuous, data-driven control of cleaning operations.

[0065] In the legend for this figure, dashed lines denote Operational Input Data entering the Analytics Controller and dot-dash lines denote Technical Control Outputs issued from the Analytics Controller.

[0066] Fig. 3 - Method Flow Figure 3 is a flow diagram illustrating a method performed by the Analytics Controller (700) to operate the cleaning system in a closed loop. The method is expressed as sequential steps S10 - S100 for clarity; steps may be executed continuously, periodically, or in parallel, and the order is not limiting. Data and control signals are exchanged via the Controller Data Backbone (770).

[0067] S10 - Ingest Operational Input Data The Analytics Controller (700) ingests Operational Input Data (106 - 399) from one or more sensors, devices or data channels associated with the apparatus and its environment. These include Interface Inputs (300) such as Assignment Parameters (301), Hygiene or Cleanliness Test Results (302), Technical Audit Results (303), Historical or Deployed Data (304), Operative Inputs and Authentication (305) and Stop or Start Override (306); Telemetry Inputs from apparatus including the Water Treatment Module (106), Source Selector (107), Automatic Source Switch (108), Treated Solution Buffer (109), Dosing Module (110), Dispensing Node (113) with Dispense Valve (114), Flow Meter (115), Metered Fill (116), Level Sensor (117), Waste Monitor (118) and Applicator Tank (119); and External Telemetry Inputs (200) including Application-site Sensors (201), Equipment Usage Signals (202), External Contextual Signals (203) and Site Maintenance Data, which may indicate repair works, access restrictions or area shutdowns.

[0068] S20 - Normalise and validate inputs Incoming data are normalised and validated, for example by a Telemetry Layer (710) with Telemetry Ingestion and Normalisation (711) and Gateway functions (712). A Safety and Fault Layer (720) with Fault Detection and Safety Interlocks (721) monitors for hardware faults, communication loss or unsafe states and may initiate safe handling or isolation before higher-level decisions are applied.

[0069] S30 - Derive Cleaning Load The controller derives a Cleaning Load (734) for each Designated Area (900) in dependence on the Operational Input Data, including usage of the Treated Solution and the Persistent Surface Treatment, each being processed as applicable within the same analytical framework, together with contextual data such as occupancy, environmental readings, equipment operation and any Site Maintenance Data.

[0070] S40 - Apply Weighting against objectives The controller evaluates the Target Hygiene Standard (731) and applies Weighting (732) among Performance Objectives (733) to establish priorities for timing, frequency and intensity of tasks across the Designated Areas.

[0071] S50 - Plan assignments and reapplication A Scheduling and Planning Layer (740) generates time-based plans comprising a Cleaning Assignment Scheduler (741) and a Persistent Surface Treatment Reapplication Planner (742), each operating within the unified scheduling framework and active according to the deployed configuration.

[0072] Plans are issued as Interface Outputs (500) including Cleaning Assignment Scheduling Control (501), Surface Treatment Scheduling Control (502), Lockouts and Management Holds (503), Acknowledgement and Recovery (504), Verification Requests (505), Adaptive Updates (506) and Alerts and Prompts (507).

[0073] The Interface (800) may be realised as a mounted terminal, a network-connected computer interface, or a mobile application, and may be configured for operative or supervisory use depending on the user profile.

[0074] S60 - Orchestrate field execution A Control Orchestration Layer (750) receives the time-based plans produced by the Scheduling and Planning Layer (740) and converts them into executable control sequences.

[0075] It incorporates a Control Orchestrator (751) and a Time Base and Event Clock (752) to coordinate the scheduling, timing and multi-signal execution of the Technical Control Outputs (400 - 601) across the apparatus.

[0076] Telemetry Outputs (400) may include Dispensing Node Control (401), Surface Treatment Control (402), Dosing Module Regulation Control (403), Source Selection and Switching Control (404), Buffer Refill Enable or Inhibit Control (405) and Untreated Mains Dispense Control (409).

[0077] These outputs govern dispensing and application operations at the field apparatus. Where a cleaning task requires untreated water, the Untreated Mains Dispense Line (112) may be selected under controller instruction to provide the necessary supply for that task.

[0078] S70 - Perform dispense or application event Under controller control, the Water Treatment Module (106) and Dosing Module (110) prepare and deliver the Treated Solution through the Treated Solution Pipeline (111) and Treated Solution Buffer (109) to one or more Dispensing Nodes (113).

[0079] Dispense events are metered by the Flow Meter (115) and validated by the Level Sensor (117) or Waste Monitor (118) as applicable.

[0080] For the Persistent Surface Treatment, the Surface Treatment Dispenser (122) may fill the Applicator Tank (119) and perform dilution or purge operations under controller command.

[0081] Quality verification of the Treated Solution for external release may be performed in separate embodiments, as described with reference to Figure 5.

[0082] S80 - Capture confirmations and outcomes Operatives provide confirmations, audit inputs or overrides through the Interface (800). Assignment Parameters are recorded for each Cleaning Assignment, and Equipment Usage Data, meter readings, level measurements and test or audit results are logged as Operational Input Data.

[0083] The Technical Audit Results may include quantitative surface-performance measurements such as surface wear indices, friction or slip coefficients, gloss or reflectance values, and coating durability scores, which are processed by the Analytics Controller (700) to recalibrate the Cleaning Load, adjust Weighting, and update Performance Objectives in accordance with the applied Weighting to optimise the Performance Objectives and to enforce the Target Hygiene Standard.

[0084] Where maintenance restrictions are active, the controller records deferrals or rescheduling in accordance with the Site Maintenance Data.

[0085] S90 - Analyse feedback and adapt The Analytics Controller (700) analyses feedback to detect operational anomalies such as abnormal task durations, unexpected solution consumption, or divergence from expected hygiene or audit patterns.

[0086] The analysis may further include comparative benchmarking performed by a Comparative Benchmark Layer (737) within the controller, enabling evaluation of relative performance among Designated Areas or operational periods.

[0087] In dependence on this analysis, the controller may re-derive the Cleaning Load, adjust Weighting, or adapt Technical Control Outputs to optimise performance.

[0088] Outbound Information and Reporting Data (600, 601) are generated by an Outbound Information and Reporting Layer (760) including an Outbound Information and Data Manager (761) and Controller Data Store (762).

[0089] Such information may be retained locally or transmitted to supervisory or external information systems for further analysis or reporting.

[0090] S100-Loop The method repeats continuously or periodically to maintain the Target Hygiene Standard while aligning with prioritised Performance Objectives, thereby providing closed-loop, data-driven control of dispensing of the Treated Solution and the Persistent Surface Treatment, each managed within the same operational framework according to the deployed configuration, together with scheduling and task optimisation across the Designated Areas.

[0091] Legend In the flow diagram, dashed connectors denote Operational Input Data received by the Analytics Controller (700) and dot-dash connectors denote Technical Control Outputs issued from it. Steps and connectors are schematic and may represent combined, parallel or iterative operations.

[0092] Fig. 4 - Comparative Scheduling

[0093] Figure 4a - Baseline schedule - fixed-interval, no controller adjustment.

[0094] Figure 4a illustrates a baseline schedule for a Designated Area (900) in which Cleaning Assignments are issued at fixed intervals and Persistent Surface Treatment reapplications, where present, follow a fixed cadence. No adjustment by the Analytics Controller (700) is applied. The rectangles indicate Cleaning Assignments; hatched rectangles indicate Persistent Surface Treatment reapplications. The horizontal axis represents Scheduling Time.

[0095] Figure 4b - Data-driven schedule - adaptive timing using Operational Input Data and derived Cleaning Load 734.

[0096] Figure 4b shows controller-driven adaptive scheduling for the same Designated Area (900). The Analytics Controller (700) ingests Operational Input Data (106-399) and derives a Cleaning Load (734), producing variable timing and, where applicable, variable duration or metered quantity for Cleaning Assignments and Persistent Surface Treatment reapplications. Dashed connectors indicate Operational Input Data entering the Analytics Controller (700) and dot-dash connectors indicate Technical Control Outputs issued from it to effect the adapted schedule.

[0097] Figure 4c - Weighted schedule - prioritising resource or labour efficiency while maintaining the Target Hygiene Standard 731.

[0098] Figure 4c depicts application of Weighting (732) among Performance Objectives (733), for example to prioritise resource or labour efficiency while maintaining the Target Hygiene Standard (731). Relative timing and / or duration of Cleaning Assignments and Persistent Surface Treatment reapplications are adjusted accordingly by the Analytics Controller (700), using the same closed-loop process shown in Figure 4b.

[0099] Legend Hollow rectangle = Cleaning Assignment; hatched rectangle = Persistent Surface Treatment reapplication; solid arrow = Direction of Time; dashed connectors = Operational Input Data to the Analytics Controller (700); dot-dash connectors = Technical Control Outputs from the Analytics Controller (700).

[0100] Fig. 5 - External Release with Chain-of-Custody As shown in Figure 5, an embodiment provides for controlled release of Treated Solution to an Authorised External Site (950) under supervision of the Analytics Controller (700). Treated Solution may be supplied from a Treated Solution Buffer (109) fed by a Treated Solution Pipeline (111). In some arrangements, a portion of the buffered flow is directed through a Quality Verification Unit (120), which may analyse one or more quality parameters of the Treated Solution before external release. When the verification conditions are satisfied, the Quality Verification Unit (120) may generate a pass signal permitting release through an External Release Port (123) for delivery to the Authorised External Site (950). In alternative arrangements, release control may rely on telemetry or data verification without an active quality-checking device.

[0101] A Chain-of-Custody Logger (121) records each release event, which may include time, volume, verification status and destination identifiers. The Chain-of-Custody Logger (121) is actuated by Chain-of-Custody Logging Trigger Control (408) issued by the Analytics Controller (700) and provides recorded release data to the Analytics Controller (700) as part of the Operational Input Data. Where present, the Quality Verification Unit (120) operates in response to Quality Verification Trigger Control (407) and may also transmit a quality verification signal to the Analytics Controller (700).

[0102] As shown in Figure 5, the Analytics Controller (700) generates Technical Control Outputs governing the External Release Port (123), including Enable I Inhibit Control (406), enabling or inhibiting external release in dependence on received verification or custody data and associated control logic. Through this interaction, the External Release Port (123) is interlocked with the required verification or logging conditions so that release occurs only when authorised according to the applied configuration. When enabled, Treated Solution is delivered to the Authorised External Site (950); when inhibited, release may be delayed, quarantined or otherwise restricted until required conditions are met.

[0103] This arrangement may be implemented in addition to, or separately from, dispensing operations to Designated Areas as previously described, and may be adapted to differing verification or data-logging configurations without departing from the inventive concept.

[0104] In the drawing, solid arrows represent the direction of Treated Solution flow, dashed lines represent data inputs to the Analytics Controller (700), and dot-dash lines represent control signals issued from the Analytics Controller (700), as indicated in the legend.

[0105] INDUSTRIAL APPLICABILITY The invention is susceptible of industrial application in managed cleaning operations, including commercial, transport, healthcare and education facilities.

Claims

1. A cleaning system comprising a water treatment module configured to receive water from mains water, HVAC blowdown water, or a combination thereof, the water treatment module comprising at least one treatment process, thereby rendering a Treated Solution suitable for use as a Cleaning Solution, a Disinfectant Solution, or a Combined Cleaning and Disinfectant Solution; a delivery arrangement configured to convey the Treated Solution to one or more Dispensing Nodes; one or more sensors, Operative inputs, or a combination thereof, configured to capture dispense events of the Treated Solution and application events of a Persistent Surface Treatment applied to a Designated Area; and an Analytics Controller implemented by one or more processors and operatively coupled to the Dispensing Nodes and to the sensors and Operative inputs; wherein each dispense event of the Treated Solution and each application event of the Persistent Surface Treatment is associated with Assignment Parameters obtained in relation to a Cleaning Assignment, the Assignment Parameters being incorporated into the Operational Input Data; wherein the Analytics Controller is configured to ingest the Operational Input Data and to derive a Cleaning Load for each Designated Area in dependence on both Treated Solution usage and Persistent Surface Treatment usage; and wherein the Analytics Controller is further configured to generate Technical Control Outputs in dependence on the Cleaning Load to govern operation of the Dispensing Nodes, to control scheduling of Cleaning Assignments, and to schedule reapplication of the Persistent Surface Treatment, the Technical Control Outputs being executable at the Dispensing Nodes or other system components and configured to enforce the Target Hygiene Standard and to optimise the Performance Objectives according to an applied Weighting.

2. The system of claim 1, wherein the water treatment module is configured to receive HVAC blowdown water as a primary source and to automatically switch to mains water when the HVAC blowdown water is unavailable.

3. The system of claim 1, wherein the water treatment module is configured to receive water from one or more reclaimed sources selected from rainwater, greywater, or condensate, and to switch to mains water as a fallback when the reclaimed source is unavailable.

4. The system of claim 1, wherein the Analytics Controller is configured to apply Weighting when generating the Technical Control Outputs, the Weighting establishing relative priorities among Performance Objectives so as to enforce the Target Hygiene Standard during generation of the Technical Control Outputs.

5. The system of claim 1, further comprising a Surface Treatment Dispenser configured to dispense a Persistent Surface Treatment into an Applicator Tank, the Surface Treatment Dispenser being operatively coupled to the Analytics Controller for control and logging of application events.

6. The system of claim 5, wherein the Surface Treatment Dispenser comprises a dilution inlet, and the Analytics Controller is configured to determine a target dilution ratio and to sequence dispensing of concentrate of the Persistent Surface Treatment and water via the dilution inlet to fill the Applicator Tank at that ratio.

7. The system of claim 1, wherein the delivery arrangement is configured to convey a surplus of the Treated Solution to an external authorised site, and wherein the system is configured such that release of the Treated Solution is subject to data-based verification of water quality, system authorisation of the release, or both, prior to release, and release is logged with chain-of-custody records.

8. The system of claim 1, wherein the Treated Solution is delivered in combination with one or more additional dosing components comprising detergents, surfactants or fragrances, the additional dosing being governed by Technical Control Outputs generated by the Analytics Controller.

9. The system of claim 1, wherein the delivery arrangement is further configured to dispense mains water in addition to the Treated Solution, such dispense events being logged by the system as part of the Operational Input Data associated with Cleaning Assignments.

10. The system of claim 1, wherein each Dispensing Node is configured with an authentication mechanism that requires an Operative to present identification or credentials prior to dispensing, the authentication being incorporated into the Operational Input Data.

11. The system of claim 1 or claim 5, wherein the Analytics Controller is configured, in dependence on the Operational Input Data and the derived Cleaning Load for a Designated Area, to determine a target dispensed quantity of the Treated Solution or the Persistent Surface Treatment for a Cleaning Assignment and to generate Technical Control Outputs executable by the Dispensing Node and, where provided, the Surface Treatment Dispenser of claim 5, to meter delivery of the target dispensed quantity.

12. The system of claim 1, wherein a measurement arrangement is configured to quantify waste or return outflow of the Treated Solution or the Persistent Surface Treatment associated with a Designated Area, a resulting measurement being supplied to the Analytics Controller as Operational Input Data associated with a Cleaning Assignment, the Analytics Controller being configured, in dependence on the measured waste quantity, to determine actual usage of the Treated Solution or the Persistent Surface Treatment per Cleaning Assignment or per Designated Area.

13. The system of claim 1, wherein either the Treated Solution or the Persistent Surface Treatment is dispensed into an Applicator Tank for application to a Designated Area, the corresponding event being recorded in the Assignment Parameters with an equipment identity for the Applicator Tank and a capacity value, the recorded data forming part of the Operational Input Data; wherein dispensing into the Applicator Tank is performed in accordance with a preset filling metric corresponding to the Applicator Tank capacity and is automatically terminated when the preset capacity is reached; and wherein a manual override or stop / start override operable by an Operative permits adjustment of the dispensed volume, the adjusted volume being recorded in the Assignment Parameters.

14. An Analytics Controller comprising one or more processors and a memory storing instructions which, when executed by the one or more processors, cause the controller to: ingest Operational Input Data, the Operational Input Data including Assignment Parameters associated with dispense events of a Treated Solution and application events of a Persistent Surface Treatment, each corresponding to a Cleaning Assignment; derive a Cleaning Load for each Designated Area in dependence on the Operational Input Data, including usage data of one or both of the Treated Solution and the Persistent Surface Treatment as applicable; apply Weighting to establish relative priorities among Performance Objectives; and generate Technical Control Outputs in dependence on the Cleaning Load and the applied Weighting, the Technical Control Outputs being executable at the Dispensing Nodes or other system components and configured to control scheduling of Cleaning Assignments and, where a Persistent Surface Treatment is present, to schedule its reapplication, so as to enforce the Target Hygiene Standard and to optimise the Performance Objectives according to an applied Weighting.

15. The controller of claim 14, wherein the controller is configured to ingest Equipment Usage Data included in the Operational Input Data, the Equipment Usage Data being obtained from components of the system and from external cleaning equipment used in Cleaning Assignments; to detect anomalies in the Equipment Usage Data; and, in dependence on the Equipment Usage Data or the detected anomalies, to re-derive the Cleaning Load, to generate maintenance-related Technical Control Outputs, a maintenance work order, or both, the Technical Control Outputs comprising instructions for filter replacement, pump servicing, or purge operations, an equipment lockout, a usage alert, or service scheduling.

16. The controller of claim 14, wherein the controller is configured to process hygiene or cleanliness test results included in the Operational Input Data and, in dependence on the results, to recalibrate the Target Hygiene Standard, to re-derive the Cleaning Load, to adjust Weighting applied by the Analytics Controller when generating the Technical Control Outputs, or to perform any combination thereof, thereby adapting cleaning parameters in accordance with an applied Weighting to optimise the Performance Objectives and to enforce the Target Hygiene Standard.

17. The controller of claim 14, wherein the controller is configured to process technical audit results included in the Operational Input Data, the technical audit results comprising surface wear indices, measurements of friction or slip, measurements of gloss or reflectance, or coating durability scores, and, in dependence on the processed results, to re-derive the Cleaning Load, to recalibrate one or more of the Performance Objectives, to adjust Weighting applied by the Analytics Controller when generating the Technical Control Outputs, or to perform any combination thereof, thereby adapting cleaning parameters in accordance with an applied Weighting to optimise the Performance Objectives and to enforce the Target Hygiene Standard.

18. The controller of claim 14, wherein the controller is configured to process historical and deployed system data included in the Operational Input Data and, in dependence on patterns identified from the data, to re-derive the Cleaning Load, to adjust Weighting applied by the Analytics Controller when generating the Technical Control Outputs, to adapt the Technical Control Outputs, or to perform any combination thereof, thereby adapting cleaning parameters in accordance with an applied Weighting to optimise the Performance Objectives and to enforce the Target Hygiene Standard.

19. The controller of claim 14, wherein the controller is configured to process external contextual data included in the Operational Input Data, the external contextual data comprising occupancy data, environmental data, or site condition data, and, in dependence on the processed data, to derive the Cleaning Load, to adjust Weighting applied by the Analytics Controller when generating the Technical Control Outputs, to adapt the Technical Control Outputs, or to perform any combination thereof, thereby adapting cleaning parameters in accordance with an applied Weighting to optimise the Performance Objectives and to enforce the Target Hygiene Standard.

20. The controller of claim 14, wherein the controller is configured to process Site Maintenance Data included in the Operational Input Data, the Site Maintenance Data comprising notifications of repair works, access restrictions, or area shutdowns, and, in dependence on the processed data, to adapt scheduling of Cleaning Assignments, to suspend or defer dispensing operations, or to generate Technical Control Outputs coordinating with the maintenance activity, thereby adapting system operation in accordance with the processed Site Maintenance Data to maintain safe coordination with maintenance activities and to enforce the Target Hygiene Standard.

21. The controller of claim 14, wherein the controller is configured to detect anomalies in relation to a Designated Area by identifying divergence from expected patterns of Operational Input Data associated with the area, and, in dependence on a detected anomaly, to re-derive the Cleaning Load, to adjust Weighting, to adapt Technical Control Outputs governing scheduling of Cleaning Assignments, dispensing parameters for the Treated Solution, or reapplication intervals of the Persistent Surface Treatment, or to perform any combination thereof, thereby adapting cleaning parameters in accordance with an applied Weighting to optimise the Performance Objectives and to enforce the Target Hygiene Standard.

22. The controller of claim 14, wherein the controller is configured to generate alerts or reports in dependence on analysis of the Operational Input Data, the analysis comprising anomalies in Assignment Parameters associated with Operatives, anomalies in Equipment Usage Data, or anomalies in hygiene or audit results, the alerts or reports being generated in parallel with the Technical Control Outputs and being communicable to an Operative, a manager, or a remote support service, thereby adapting system operation and communication pathways in accordance with detected anomalies to enable responsive intervention and to enforce the Target Hygiene Standard.

23. A method of operating a cleaning system, the method comprising: producing, by a water treatment module, a Treated Solution suitable for use as a Cleaning Solution, a Disinfectant Solution, or a Combined Cleaning and Disinfectant Solution from at least one source of water; dispensing the Treated Solution via one or more Dispensing Nodes and logging dispense events as Operational Input Data including Assignment Parameters associated with a Cleaning Assignment; recording, as part of the Operational Input Data, application events of the Persistent Surface Treatment applied to a Designated Area together with Assignment Parameters associated with a corresponding Cleaning Assignment; ingesting, by an Analytics Controller implemented by one or more processors, the Operational Input Data; deriving, by the Analytics Controller, a Cleaning Load for each Designated Area in dependence on the Operational Input Data; applying, by the Analytics Controller, Weighting among Performance Objectives when generating the Technical Control Outputs; and generating, by the Analytics Controller, Technical Control Outputs in dependence on the Cleaning Load and the applied Weighting, the Technical Control Outputs being executable at the Dispensing Nodes or other system components, to control scheduling of Cleaning Assignments, and to schedule reapplication of the Persistent Surface Treatment, so as to enforce the Target Hygiene Standard and to optimise the Performance Objectives according to an applied Weighting.

24. A computer program comprising instructions which, when executed by one or more processors of an Analytics Controller, cause the Analytics Controller to carry out the method of claim 23.

25. A computer-readable storage medium storing the computer program of claim 24.T +44(0)30 0300 2000A

Images