Systems and methods for elevator fire suppression and standpipe system

Abstract

An emergency response system stages firefighting from an elevator. An elevator car includes a robot-dedicated compartment separate from a passenger compartment for transporting an autonomous robotic device. A shaft standpipe extends along the elevator shaft and includes a fluid nozzle positioned to align with a car-side receptacle to supply firefighting agent to equipment carried by the car or the robot. A control platform coordinates operation of the elevator car and the autonomous robotic device for deployment within a building, including positioning the car at a landing, authorizing coupling to the standpipe, and initiating robot egress. The integrated arrangement reduces response time and enables agent delivery sourced from the building standpipe while maintaining passenger isolation and controlled deployment from the elevator environment.

Description

SYSTEMS AND METHODS FOR ELEVATOR FIRE SUPPRESSION AND STANDPIPE SYSTEMCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application Serial No. 63 / 713,937, filed October 30, 2024, entitled ELEVATOR FIRE SUPPRESSION AND STANDPIPE SYSTEM, which is hereby incorporated in its entirety by reference herein.FIELD OF THE DISCLOSURE

[0002] The disclosure relates to building systems and automation, and more specifically to vertical transportation and life safety operations in structures.BACKGROUND

[0003] High rise buildings typically lack a fast and reliable path to deliver water or agents at incident floors. Standpipe hookups are manual, elevator recall competes with egress traffic, and transfer paths are unreliable in smoke and heat. Typical elevator controls are built for attended human use and do not natively support autonomous platforms. Devices cannot authenticate, place car calls, or coordinate precise door indexing, and hoist ways attenuate radio signals which degrade command, telemetry, and auditability.

[0004] Coupling alignment and downstream pressure and mix control vary widely, making it difficult to hold stable nozzle pressure or verified agent concentrations. Building subsystems such as the fire alarm control panel, the building management system, the elevator controller, and robotic platforms often use different protocols without clear priority or preemption, which limits alarm correlation, pre-staging, and safe behavior, especially in banked or multi car shafts with complex standpipe layouts. Post event purge, drain capture, and readiness checks are labor intensive and inconsistently recorded, which slows return to service and hinders after action analysis.BRIEF DESCRIPTION OF THE DISCLOSURE

[0005] This brief description is provided to introduce a selection of concepts in a simplified form that are further described in the detailed description below. This brief description is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Other aspects and advantages of the present disclosure will be apparent from the following detailed description of the embodiments and the accompanying figures.

[0006] In various aspects, an emergency response system is provided. The system, includes a multi-compartment elevator system. The multi-compartment elevator system includes an elevator car disposed in an elevator shaft and a shaft standpipe extending along the elevator shaft. The elevator car includes a robot-dedicated compartment configured to carry an autonomous robotic device. The shaft standpipe includes a fluid nozzle positioned along the shaft standpipe. The system also includes a control platform coordinating operation of the elevator car and the autonomous robotic device for deployment within a building. The robot-dedicated compartment includes a receptacle that aligns with the fluid nozzle of the shaft standpipe, an agent delivery system fluidly coupled to the receptacle, and a hose interface fluidly coupled to the agent delivery system and connectable to the autonomous robotic device.

[0007] In various aspects, an agent delivery system is provided. The agent delivery system is configured for installation in a robot-dedicated compartment of an elevator system. The agent delivery system includes a receptacle that aligns with a fluid nozzle of a shaft standpipe, a pressure-reducing valve downstream of the receptacle, a proportioning assembly downstream of the pressure-reducing valve, a pressure transducer, a flowmeter, a booster pump, and a hose reel terminating in a coupling latch assembly.

[0008] In various examples, a method is provided. The method includes providing an elevator car having a passenger compartment and a robot-dedicated compartment. The method also includes staging the autonomous robotic device within the robot-dedicatedcompartment. Additionally, the method includes routing the elevator car to a target landing. Furthermore, the method includes aligning a receptacle positioned in the robot-dedicated compartment to a fluid nozzle of a shaft standpipe and supplying fluid from the shaft standpipe through an agent delivery system in the lower robot-dedicated compartment. In addition, the method includes regulating one or more of a nozzle pressure and flow setpoint. Moreover, the method includes deploying the autonomous robotic device via a hose interface from the robot-dedicated compartment.

[0009] In various aspects, a non-transitory computer-readable medium (CRM) is provided. The SRM stores instructions that, when executed by one or more processors of a controller, cause the controller to compute a target landing and a transfer path. The controller also routes the elevator car to the target landing by issuing one or more elevator routing commands. Furthermore, the controller verifies alignment between a fluid nozzle of a shaft standpipe and a receptacle of a robot-dedicated compartment. The controller also authorizes hydraulic coupling and regulate one or more of a nozzle pressure and flow setpoint. Additionally, the controller actuates a subset of door panels of the robot-dedicated compartment to form a monitored transfer path while passenger doors remain closed and locked. The controller also maintains autonomous robotic device corridor positive pressure. Moreover, the controller deploys the autonomous robotic device via a hose interface from the robot-dedicated compartment.

[0010] In various embodiments, a multi-structure coordination system is provided. The coordination system includes a communication network including an edge-cloud framework and one or more of a satellite link and a government emergency services network. The coordination system also includes a plurality of elevator-mounted firefighting nodes coupled in communication via the communication network. The coordination system aggregates telemetry, dispatches elevators, and allocates autonomous robotic devices across multiple structures according to tenability and propagation risk.

[0011] In example embodiments, an elevator-mounted flow compliance apparatus is provided. The apparatus includes a reservoir disposed in a robot-dedicated compartmentof an elevator system. The apparatus also includes a weighted baseplate sensor positioned under the reservoir. Furthermore, the apparatus includes a controller configured to infer a delivered fluid flow from mass change over time, and compare the inferred delivered fluid flow to a predefined threshold value.

[0012] A variety of additional aspects will be set forth in the detailed description that follows. These aspects can relate to individual features and to combinations of features. Advantages of these and other aspects will be apparent to those skilled in the art from the following description of the exemplary embodiments which have been shown and described by way of illustration. As will be realized, the present aspects described herein may be capable of other and various aspects, and their details are capable of modification in various respects. Accordingly, the figures and description are to be regarded as illustrative in nature and not as restrictive.BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The figures described below depict various aspects of systems and methods disclosed therein. It should be understood that each figure depicts an embodiment of a particular aspect of the disclosed systems and methods, and that each of the figures is intended to accord with a possible embodiment thereof. Further, wherever possible, the following description refers to the reference numerals included in the following figures, in which features depicted in multiple figures are designated with consistent reference numerals.

[0014] FIG. 1 is a block diagram of an emergency response system using an elevator car with a passenger compartment, a robot compartment, a control platform, building systems, and supporting networks, in accordance with an aspect of the invention;

[0015] FIG. 2 is a schematic of the elevator car of FIG. 1, depicting structure showing the passenger compartment and a robot-dedicated compartment with agent delivery system features;

[0016] FIG. 3 is a block diagram of the agent delivery system of FIG. 2;

[0017] FIG. 4 is a schematic diagram showing data exchange among the control platform, building systems, and supporting networks of FIG. 1; and

[0018] FIG. 5 is a flowchart of a method for firefighting staged from the multicompartment elevator of FIG. 1.

[0019] Unless otherwise indicated, the figures provided herein are meant to illustrate features of embodiments of this disclosure. These features are believed to be applicable in a wide variety of systems comprising one or more embodiments of this disclosure. As such, the figures are not meant to include all conventional features known by those of ordinary skill in the art to be required for the practice of the embodiments disclosed herein.DETAILED DESCRIPTION OF THE DISCLOSURE

[0020] The following detailed description of embodiments of the invention references the accompanying figures. The embodiments are intended to describe aspects of the invention in sufficient detail to enable those with ordinary skill in the art to practice the invention. The embodiments of the invention are illustrated by way of example and not by way of limitation. Other embodiments may be utilized, and changes may be made without departing from the scope of the claims. The following description is, therefore, not limiting. The scope of the present disclosure is defined only by the appended claims, along with the full scope of equivalents to which such claims are entitled.

[0021] Referring to FIGs. 1-4, an emergency response system 100 includes a multicompartment elevator system 102. The multi-compartment elevator system 102 includes a multi-compartment elevator car 104 having a passenger compartment 106 and a robot- dedicated compartment 108. As used herein, a “multi-compartment elevator car” refers to an elevator car having at least two distinct compartments. In various examples, the at least two distinct compartments are vertically arranged relative to each other. In variousexamples, the at least two distinct compartments may be laterally arranged. In various examples, passenger compartment 106 may be positioned beneath or laterally adjacent to the robot-dedicated compartment 108. In various examples, laterally adjacent compartments may include an automated access panel between them to allow ingress and egress between the compartments.

[0022] An elevator control unit 110 is communicatively coupled to the multi - compartment elevator car 104 and coordinates car movement and door operations. The elevator control unit 110 communicates with a building management system (BMS) 112 and a control platform 114 over a communication network 116. In various examples, the BMS 112 includes building automation systems (e.g., BACnet, LONworks, API-accessible platforms). The control platform 114 represents local edge and / or cloud services providing orchestration, monitoring, artificial intelligence (Al) and machine learning (ML) functions, and optional teleoperation over wired and wireless transports (e.g., Ethernet, TCP-1P, MQTTZHTTP(S), Wi-Fi, Bluetooth, Zigbee, cellular, 5G, and / or satellite bridges). In various examples, the control platform 114 includes a processor, memory, and a transceiver. Firmware stored in the memory instructs the processor to perform orchestration, artificial intelligence or machine learning, data logging, and supervisory networking, as discussed further herein.

[0023] In various examples, a landing multi-panel door system 118 installed at each building landing cooperates with an elevator multi-panel door system 120 mounted to the robot-dedicated compartment 108 to form a secured transfer aperture for ingress / egress of an autonomous robotic device (also referred to herein as ground robot(s) and / or aerial robot(s)) while isolating the passenger compartment 106. The two multi-panel door systems 118, 120 are mechanically and logically interlocked to cooperate during aligned opening and closing for ingress and egress while maintaining isolation from the passenger compartment 106, as discussed herein.

[0024] In various examples, a shaft standpipe 150 extends along an elevator shaft 144. The shaft standpipe 150 includes a fluid nozzle(s) 156, generally located proximateeach landing. The fluid nozzle 156 is positioned to align with a region of the robot- dedicated compartment 108 when the elevator car 104 is at the landing. A car-mounted receptacle 158 is fixed to the robot-dedicated compartment 108 and aligned with the fluid nozzle 156. In various examples, a booster pump 170 is located within the robot-dedicated compartment 108. The booster pump 170 may be energized, for example, via a compartment controller 224 (shown in FIG. 2), to meet a commanded hose nozzle pressure or flow setpoint.

[0025] In various examples, the elevator control unit 110 includes a microprocessor, memory, power regulation, and input and output interfaces. The microprocessor executes firmware that implements, for example, car positioning, door actuation, safety interlocks, and communications with the BMS 112 and the control platform 114. The memory stores door profiles, mission schedules, and configuration parameters. The input and output interfaces support communication via the communication network 116, for example. The communication network connections may include, for example, Ethernet or serial buses. The connections connect to motor drives for hoisting and leveling, brake solenoids, door motors, and encoder feedback from doors and car movement. The elevator control unit 110 also receives status signals from the elevator multi-panel door system 120 and from the landing multi-panel door system 118. The feedback may include, for example, whether each door panel is closed, locked, or obstructed.

[0026] A command center 130 supervises deployments of an autonomous robotic device(s) 132 via the control platform 114. One or more gateways or application programming interfaces (APIs) 136 connect to building systems, such as the BMS 112. A satellite bridge 140 is optional and may be provided for system resiliency. In various arrangements, one or more wireless access points (not shown) may be mounted on a roof of the multi-compartment elevator car 104 and at the elevator shaft head, with a point-to- point wireless bridge linking them to maintain backhaul through the elevator shaft.

[0027] High-rise structures may include multiple multi-compartment elevator cars 104 per shaft 144 or adjacent shafts sharing a landing. In such examples, the emergency response system 100 provisions multiple standpipes 150 or branch connections aligned with respective multi-compartment elevator car 104 and landings. A bank controller (not shown) selects an available multi-compartment elevator car 104 based on car location, service status, and standpipe pressure availability, then coordinates landing selection to minimize travel time and hose run. Landings may incorporate duplicated quick-connect panels so either of two cars on the same landing can couple to the same standpipe 150 when permitted by code and hydraulics.

[0028] In various examples, the platform 114 may employ publish / subscribe messages on a communication network 142 (e.g., via MQTT / HTTPS) to orchestrate elevator / door / robotic device actions in real time across one or multiple buildings. Controllers participating on the communication network 142 may include, for example the compartment controller 224, a door / interlock controller 300 (See FIG. 3) that actuates the elevator multi-panel door system 120 and the landing multi-panel door system 118, and autonomous robotic device controller(s) 414 that bridge, via one or more RF links over a wireless communication network 418 (e.g., Wi-Fi, cellular, 5G, and / or the satellite bridge 140), to one or more endpoint devices including autonomous robotic device(s) 132. As an alternative medium, a projected light (optical) interface may be used for short-range data exchange at the door interfaces where RF is constrained.

[0029] The command center 130 includes user interfaces such as touch screen displays, joysticks, keyboards, and haptic devices to enable remote operators to control autonomous devices when necessary. Optional audio systems provide two-way voice communication with building occupants or first responders. The command center 130 may also host virtual or augmented reality interfaces for immersive telepresence.

[0030] The control platform 114 executes mission planning software that allocates the autonomous robotic devices 132 to tasks, monitors mission progress via a robotic device / status message 426 (see FIG. 4), and adjusts mission parameters based on sensordata and operator input. Gateways or APIs 136 connect the control platform 114 to the BMS 112 using one or more communication protocols, such as REST APIs, BACnet, LONworks, Modbus, and the like. The optional satellite bridge 140 provides wide-area connectivity when terrestrial networks fail or are congested, as discussed further herein.

[0031] In various examples, the communication network 142 operates as a publish / subscribe bus over Internet Protocol (IP). For example, controllers and endpoints publish status messages and subscribe to command topics described, for example, in FIG. 4. Quality-of-Service (QoS) parameters (e.g., acknowledgement, at least once delivery, etc.) ensure delivery of critical messages. Transport security includes encryption using, for example, transport layer security (TLS) and mutual authentication. The autonomous robotic device controller(s) 414 maintains mission plans, sensor data logs, and failover logic. Each autonomous robotic device controller 414 operates autonomously when disconnected from the control platform 114 by executing preloaded mission scripts and synchronizing state after connectivity is restored. The control platform 114 manages mission queues and ensures that life-safety missions pre-empt non-critical tasks.

[0032] In some embodiments, the emergency response system 100 includes a building alarm interface 134 configured to exchange alarm, supervisory, and control signals with a fire alarm control panel (FACP) and / or intelligent alarm network of the protected structure. The building alarm interface 134 provides a deterministic, priority pathway for initiating and controlling fire suppression elevator operations upon verified alarm detection, independently of, or in coordination with, the BMS 112 and the remote command center 130.

[0033] The building alarm interface 134 may include, for example, (i) an VO stage including supervised dry-contact inputs and relay outputs; (ii) a data stage supporting one or more digital protocols (e.g., BACnet / IP, BACnet MS / TP, Modbus TCP / RTU, CAN, or a secured message bus such as MQTT over TLS); and (iii) a safety controller executing a state machine that enforces alarm priorities, timing constraints, and safe states. In certain embodiments, the building alarm interface 134 includes an AI / ML inference module thatperforms classification and correlation of multi-sensor events (e.g., smoke, heat, sprinkler flow, video analytics) to refine alarm confidence and to pre-stage the multi-compartment elevator car 104 for accelerated response while filtering nuisance events.

[0034] Upon receipt of an alarm condition (e.g., general alarm, floor-indexed alarm, waterflow, or confirmed video smoke / flame detection) and a minimum confidence threshold, the building alarm interface 134 asserts elevator-priority control by issuing a takeover command to the elevator control unit 110 for a designated suppression mode. In suppression mode: (i) the control platform 114 commands the multi -compartment elevator car 104 to a pre-selected staging landing proximate the alarm floor; (ii) coordinates the door systems 118, 120 to secure a robot transfer corridor; (iii) authorizes standpipe coupling and agent delivery interlocks; and (iv) publishes a deployment request to the control platform topics for robotic dispatch.

[0035] The building alarm interface 134 manages priority arbitration between local alarm-initiated control, BMS requests, and remote operator commands. A priority table assigns the highest preemption to life-safety alarm states. Operator commands may be granted only when alarm preemption is released or explicitly transferred under supervised conditions. The building alarm interface 134 enforces timeouts (e.g., elevator arrival, door alignment, coupling) and guards (e.g., passenger compartment unsecured, over-pressure, misalignment), and returns the system to a safe state when a guard is tripped.

[0036] In various examples, the building alarm interface 134 may be implemented on redundant compute (hot standby) with dual power sources (e.g., life-safety 24 VDC and building UPS) and dual communications (e.g., alarm loop + IP). Message authentication (e.g., mTLS) and sequence counters prevent replay. All decisions, alarms, and actuator outcomes are event-logged with timestamps for post-incident analysis.

[0037] Optionally, the building alarm interface 134 integrates with jurisdictional incident command systems to expose read-only status (elevator location, door states, coupling status, agent pressure / flow) and a gated set of remote commands in suppressionmode (e.g., “Advance,” “Purge,” “Retract,” etc.). Where applicable, the building alarm interface 134 is adapted to local code requirements and vendor-specific FACP cabinets via listed modules or listed relay assemblies.

[0038] The direct AI-FACP integration reduces manual coordination delay, enables pre-staging based on correlated alarms, and ensures the multi-compartment elevator car 104 is controlled by the emergency response system 100 with clear preemption and interlocks, improving time-to-agent at the incident floor while maintaining passenger isolation.

[0039] Various examples disclose life-safety services, such as firefighting and emergency medical response. In various examples, the same infrastructure supports cleaning, maintenance, housekeeping, security, humanoid, and quadruped autonomous vehicles. These examples are non-limiting and illustrate the diversity of missions supported by the emergency response system 100. Staging autonomous vehicles within the multicompartment elevator car 104 reduces response time by pre-positioning mission-ready units proximate to operational places.

[0040] In various examples, life-safety robots staged in the robot-dedicated compartment 108 may include a firefighting robot with one or more thermal imaging cameras, visible light cameras, gas detectors (e.g., smoke, CO, CO2), a LiDAR or radar sensor for mapping, an inertial measurement unit for dead reckoning, and a pump connected to onboard extinguishing agent reservoirs or to building standpipes via quick-connect couplings. The firefighting robot may carry a hose and adjustable nozzle to deliver a fire extinguishing agent and may include couplings sized to connect to floor standpipe outlets or sprinkler risers. An emergency medical robot may include one or more microphones, speakers, cameras, vital-sign sensors, and compartments for automated external defibrillators and first aid supplies. The robots are configured to perform self-diagnostics to verify sensor and actuator health and report status to the control platform 114 via the robotic device / status message 426 (See FIG. 4). The robots are configured to monitor battery state of charge, battery temperature, and environmental conditions, forexample, and may autonomously reposition within the robot-dedicated compartment 108 to facilitate charging or cooling.

[0041] In various examples, the control platform 114 applies artificial intelligence or machine learning to classify events, allocate missions, and verify completion reports received from the elevator control unit 110 and the autonomous robotic device controller 414.

[0042] Referring FIG. 2, the elevator car 104 includes structural frame members (not shown) joined by welded, bolted, or riveted connections. A floor defining the passenger compartment 106 also forms a fire-rated divider panel 226 that separates the upper passenger volume from the lower robot-dedicated compartment 108. One or more walls include metallic or composite skins, insulation, and a fire-resistant liner 228 to contain and isolate heat within the robot-dedicated compartment 108. The robot-dedicated compartment 108 provides a service cavity 246 that houses an agent delivery system 248. The service cavity 246 is positioned such that doors systems 118, 120 remain unobstructed during autonomous robotic device transfer. In various examples, the service cavity 246 is positioned beneath the compartment holding the autonomous robotic device(s) 132. In various examples, the service cavity 246 may be positioned above, behind, and / or adjacent to the compartment holding the autonomous robotic device(s) 132.

[0043]

[0044] The elevator system 102 may be traction or hydraulic, with hoist, brake, and leveling drives controlled by the elevator control unit 110.

[0045] As shown in FIG. 3, in various examples, the agent delivery system 248 is positioned within the service cavity 246 of the robot-dedicated compartment 108. The agent delivery system 248 may include, for example, one or more of the following components: the receptacle 158 configured to align with and receive fluid from the shaft fluid nozzle 156; a pressure-reducing valve 364 located downstream of the receptacle 158 and rated for one hundred and seventy-five (175) pound per square inch (psi) to threehundred (300) psi static pressure while maintaining a downstream operating setpoint of about ninety-five (95) psi to about one hundred and twenty-five (125) psi; and a proportioning assembly 366 operable across a ratio range between and including one tenth (0.1) percent to about ten (10) percent. The proportioning assembly 366 may include, for example, an eductor 330, mass-based metering system 332 (e.g., via load cells 334), or volumetric metering system 336 (e.g., via dual flowmeters), with a control valve 340. In various examples, the proportioning assembly 366 is agent-agnostic, supporting Class A foam, Class B foam, wetting agents, or other code-approved concentrates. Selection and concentration of mixing agents can be programmatically set by the control platform 114 based on incident type and tenability.

[0046] The agent delivery system 248 also includes the booster pump 170 that activates to pressurize the agent to the autonomous robotic device 132. Additionally, the agent delivery system 248 may include a hose interface 372. The hose interface 372 may include a hose reel 374, swivel 376, and strain-relief 378. The hose reel 374 may include a hose 380 having a length in a range between and including twenty -five (25) feet (ft) and one hundred and fifty (150) ft. In various examples, the length of the hose 380 may be any length that enables the system 100 to function as described herein. In various examples, the hose interface 372 is electrically powered and configured to output and uptake the hose 380 at a rate substantially equivalent to the movement of the autonomous robotic device 132. This enables the autonomous robotic device 132 to more easily navigate the structure, without the need for additional power or loss of time to pull the hose 280 from the hose reel 374.

[0047] Additional components may include a backflow check valve 368 to prevent backflow toward the reservoir 288 and a drain / purge valve 382 for post-mission flushing. The agent delivery system 248 is enclosed within a thermal and splash-resistant housing 260.

[0048] Referring to FIG. 2, within the robot-dedicated compartment 108, a charging interface 206 can include an inductive pad 208. In various examples, the charginginterface 206 includes one or more conductive docking connectors 210 located on a floor, wall, or ceiling surface as alternates. In various examples, one or more alignment aids (e.g., guides, bumpers, fiducials) facilitate coupling and charge initiation and termination.

[0049] In various examples, the inductive pad 208 integrates near-field communication (NFC) circuits for negotiation of charging parameters. In some examples, the conductive docking connectors 210 are shielded and biased to accommodate misalignment and to protect against short circuits. Electrical isolation and ground-fault detection ensure that power is applied only when the autonomous robotic device is fully docked.

[0050] The robot-dedicated compartment 108 may include one or more environmental sensors, such as temperature, humidity, and gas sensors, connected to the compartment controller 224 to monitor environmental conditions and to alert if water ingress or contaminant levels exceed thresholds. All sensors and power devices within the robot-dedicated compartment 108 are rated to operate under vibration, shock, and elevated temperature conditions typical of elevator operations.

[0051] In various examples, the thermal / splash containment housing 260 includes a fire-suppression subsystem 214 and the fire-resistant liner 228. One or more environmental sensors 218 and / or cameras 220 trigger suppression. Suppression devices may be placed within the robot-dedicated compartment 108 and / or in adjacent connected locations. In various examples, the multi-compartment elevator car 104 may include an embedded disinfecting system (e.g., UV-C or chemical mist) for decontamination of the robot-dedicated compartment 108 surfaces under control of the compartment controller 224.

[0052] The fire-suppression subsystem 214 may discharge water or water-mist for knock-down and continued cooling, and may employ clean agents, inert gas, foam concentrate, or condensed aerosol generators as appropriate. Discharge nozzles are positioned to saturate the robot area. The fire-resistant liner 228 lines the interior surfacesand may include intumescent, ceramic, and / or multilayer composite materials to contain and insulate heat. Embedded temperature sensors in the liner can trigger secondary suppression if wall temperature increases.

[0053] In various examples, sensor events initiate coordinated response by the elevator control unit 110 and the control platform 114. For robotic devices using lithium- ion batteries, the containment housing 260 supports early detection and suppression tailored to such hazards, including water or water-mist cooling for knock-down and propagation mitigation with continued post-suppression cooling.

[0054] The environmental sensors 218 may include thermocouples, resistance temperature detectors, thermistors, smoke detectors (photoelectric or ionization), optical particle counters, carbon monoxide sensors, carbon dioxide sensors, hydrogen sensors, volatile organic compound sensors, and the like. Cameras 220 may include visible, infrared, thermal, and / or multispectral imagers, and the like.

[0055] Referring to FIG. 3, in exemplary embodiments, the fluid nozzle 156 extends from the vertical standpipe 150 toward the rear or rear-side of the robot-dedicated compartment 108. An alignment sensor 304 confirms axial and angular alignment for fluid coupling alignment. In various examples, the emergency response system 100 relies on standpipe pressure as the motive force to the agent delivery system 248, reducing complexity and avoiding additional water supply risers.

[0056] The pressure-reducing valve 364 maintains a commanded nozzle pressure setpoint (e.g., about one hundred (100) psi) for typical one (1) to one and a half (1-1 / 2) inch hose, such as the hose 380, and nozzle configurations suitable for the autonomous robotic device(s) 132. The nozzles may include, for example, fog, straight-stream, automatic, combination, Compressed Air Foam Systems (CAFS) capable, and portable monitor types. The booster pump 170 provides pressure and flow to achieve the commanded nozzle pressure setpoint. The backflow checkvalve 368 prevents reverse flow into the reservoir 288.

[0057] Optionally, in some embodiments, the multi-compartment elevator car 104 includes a multi-port agent manifold fluidly coupled to the standpipe fluid nozzle 156. The manifold may provide two or more independently valved dispensing ports, each port having an isolation valve, a check valve, and an inline flow sensor. Ports may be assigned to distinct autonomous robotic devices 132 (e.g., a hose-handling robot and nozzle robot) and may operate simultaneously or sequentially under control of the control platform 114. The pressure-reducing valve 364 maintains a downstream window (e.g., 95-125 psi) per active port. Allocation logic limits combined flow to a configured maximum to stay within standpipe capacity. Quick-release couplings at each port enable rapid connect / disconnect of hoses or hardlines mounted on the robot deck.

[0058] In various embodiments, the hose reel 374 is mounted low and rearward to avoid door sweep areas. A fairlead 354 facilitates providing strain relief. In some examples, the agent discharge terminates in a robot-side quick-disconnect 358 with a latch assembly 360 and proximity switch to confirm coupling. In such examples, the autonomous robotic device(s) 132 may include one or more nozzles 362, including, for example, a fog, straightstream, automatic, combination, portable monitor, or CAFS-capable nozzle. The control platform 114, via the compartment controller 224, is configured to halt hydraulic pressurization on uncoupling or excessive tension and to command door closure if the corridor becomes obstructed.

[0059] As depicted in FIG. 3, various examples include a weighted baseplate sensor 340 installed beneath a fluid reservoir 388 of the agent delivery system 248 (broadly a elevator-mounted flow compliance apparatus). The weighted baseplate sensor 340 may include one or more sensors 342, 344, such as load cells, strain-gauge transducers, or piezoelectric force sensors. The sensors 342, 344 may be arranged between a lower frame structure 346 of the service cavity 246 and the fluid reservoir 388. The weighted baseplate sensor 340 supports one or more of the hydraulic components of the agent delivery system 248 and / or collects discharge fluid during testing and operation, permitting thecompartment controller 224 to determine a real-time mass change (Am) associated with water or agent flow.

[0060] The compartment controller 224 may be configured to sample the weighted baseplate sensor 340 at a rate of at least one hertz (1 Hz) and to compute a mass change rate (Am / t). Using stored density values for the delivered fluid (p), the compartment controller 224 converts the computed mass change rate to volumetric flow (Q) according to:

[0061] Where Q is expressed in gallons per minute (GPM) or liters per second. The compartment controller 224 thereby infers actual flow through the agent delivery system 248 and compares the inferred flow to stored reference thresholds representing NFPA 14 (National Fire Protection Association’s Standard for the Installation of Standpipe and Hose Systems) performance criteria for the highest fluid outlet.

[0062] In various examples, during commissioning or scheduled maintenance of the agent delivery system 248, the compartment controller 224 may execute a flow test mode in which the pressure-reducing valve 364 and the proportioning assembly 366 are cycled through known states while the weighted baseplate sensor 340 measures accumulated discharge mass over a timed interval. The compartment controller 224 integrates mass over time, applies temperature compensation from a co-located temperature sensor, and generates a pass / fail result when inferred flow satisfies or fails to satisfy the expected NFPA 14 range (for example, sixty-five (65) to one hundred (100) gallons per minute at a designated pressure).

[0063] Optionally, for retrofit scenarios, the multi-compartment elevator car 104 can mount a modular reservoir assembly comprising a primary fixed reservoir (e.g., Class A / Wetting agent) and a secondary removable reservoir in a quick-latch frame. A manifolded proportioner accepts flow from either or both reservoirs. A selector valve andcheck valves prevent backflow between chemistries. Level sensors (e.g., ultrasonic or loadcell based) and temperature compensation stabilize concentration calculations. The removable reservoir can be swapped at a staging floor without removing the elevator car 104 from service. In some embodiments, the secondary reservoir is a cartridge pack prefilled to a known mass; the controller computes mix ratio by mass-flow correlation (reservoir mass change over time) or by dual-flow metering.

[0064] Calibration may be accomplished using one or more reference weights placed on the weighted baseplate sensor 340 and a stored calibration curve that compensates for temperature, humidity, or structural flexure. In some implementations, four or more load cells may be arranged in a square array beneath the reservoir cavity to maintain a plus or minus three percent (±3%) accuracy across the twenty-five (25) to one hundred and fifty (1 0) GPM range. The calibration constants may be stored in non-volatile memory and verified during periodic self-checks.

[0065] The weighted baseplate sensor 340 enables automatic compliance verification without manual flow measurement, allowing the emergency response system 100 to satisfy building code testing requirements through software-controlled sequences. The compartment controller 224 may inhibit booster pump enablement or proportioning activation when inferred flow remains below threshold for a programmed interval. The same mass change data may also be logged to the building record or transmitted via the communication network 116 for audit and maintenance purposes.

[0066] FIG. 3 shows the door / interlock controller 300 that supervises the elevator multi-panel door system 120 and the landing multi-panel door system 118. Car position sensors 302, such as proximity or limit switches, confirm that the multi-compartment elevator car 104 is aligned with the landing before either door system 118, 120 opens. Doorstate encoders 308a and 308b confirm that the door systems 118, 120 are closed or open as expected.

[0067] An autonomous robotic device corridor 314 may be provided as a monitored path for autonomous robotic device transfer. The alignment sensors 304 and interlock lines 316 are used for verified transfer. The interlock lines 316 ensure that one door set 118 or 120 does not open unless the other door set 120 or 118, respectively, is in a locked state. After an autonomous robotic device transfer is completed, both the elevator door system 120 and the landing door system 118 close and lock. Collectively, the door systems 118, 120, together with the door / interlock controller 300, interlock lines 316, car position sensors 302, alignment or photoelectric sensors 304, door-state encoders 308a and 308b, and any corridor sensors defining the autonomous robotic device corridor 314, are referred to herein as an “access control assembly” configured to verify alignment and selectively actuate a subset of aligned panels to create a monitored transfer path while the passenger compartment remains closed and locked.

[0068] In various examples, the door / interlock controller 300 includes a microcontroller or microprocessor, memory, and input and output interfaces for a plurality of sensors and actuators. The door / interlock controller 300 connects to the car position sensors 302 to confirm a position of the multi-compartment elevator car 104, the alignment sensors 304 to verify fluid coupling alignment, the door-state encoders 308a, 308b to measure door panel movement, and one or more optional safe corridor sensors (not shown).

[0069] In various examples, the door / interlock controller 300 runs a state machine with states such as idle, align, unlock, open, transfer, close, and lock. Each state transition depends on one or more sensor readings and confirmation from the elevator control unit 110. The door / interlock controller 300 publishes door status on a doors / state channel 422 (See FIG. 4) and publishes transfer completion on a transfer / verify channel 424 (See FIG. 4). If a misalignment, obstruction, or fault is identified or found, the door / interlock controller 300 halts door motion, locks the doors, and notifies the elevator control unit 110 and the control platform 114.

[0070] During autonomous robotic device passage, the system maintains a positive corridor pressure in a range between and including five (5) pascals (Pa) and twenty -five(25) Pa using one or more fluid moving devices 310. After transfer completion, both multipanel door systems 118, 120 close and lock, preserving passenger isolation.

[0071] The autonomous robotic device corridor 314, when included, defines a monitored path between the robot-dedicated compartment 108 and the landing. The autonomous robotic device corridor 314 may be marked with floor stripes, rails, or bollards, and may use photoelectric beams, pressure mats, ultrasonic sensors, or infrared sensors to detect objects. If the path is blocked while an autonomous robotic device enters or exits, the door / interlock controller 300 halts the doors and alerts the elevator control unit 110 and the control platform 114. The autonomous robotic device corridor 314 may include lights or alarms to warn nearby people when an autonomous robotic device is moving.

[0072] In some examples, the autonomous robotic device corridor 314 extends beyond the elevator landing via protected passageways (e.g., short tunnels, rigid tubes, or shielded raceways) to adjacent rooms or lobbies. Each autonomous robotic device corridor 314 includes smoke control, thermal shielding, and fire curtains or rolling shutters forming additional interlocked barriers. Service apertures with quick-connect panels allow the autonomous robotic devices 132 to receive agent or power at intermediate nodes.

[0073] In various examples, autonomous robotic devices may be allowed to operate during a fire service mode when authorized by a local authority having jurisdiction. In various examples, the emergency response system 100 allows incident command to recall or disable autonomous robotic devices immediately through the control platform 114 and the elevator control unit 110.

[0074] FIG. 4 is a schematic diagram of a messaging topology 400 for the exchange of data and information among the controllers and platforms described herein. In various examples, the elevator control unit 110, the door / interlock controller 300, the building alarm interface 134, and the autonomous robotic device controller(s) 414 interoperate with the control platform 114 and the BMS 112 (via the gateway / APIs 136). The controllers and platforms 108, 110, 112, 134, 136, 300, and 414 communicate over the communicationnetworks 116, 142 and the wireless communication network 418 (e.g., Wi-Fi, Bluetooth, cellular, 5G). The optional satellite bridge 140 provides resiliency.

[0075] In various examples, the messaging topology 400 is a publish / sub scribe communication model. It is contemplated, however, that any communication model that enables the emergency response system 100 to function as described herein may be used. In the example embodiment, the controllers and platforms 108, 110, 112, 134, 136, 300, and 414 exchange data over one or more structured messaging channels, or topics (like subjects or categories). Each topic is a named subject that carries a defined set of fields (e g., elevator / position, doors / state, robot / status). The controllers and platforms 108, 110, 112, 134, 136, 300, and 414 publish data on topics relevant to their function. Other nodes subscribe to the topics to receive the associated data. The publish / sub scribe approach allows the elevator control unit 110, the door / interlock controller 300, the building alarm interface 134, the autonomous robotic device controller(s) 414, the control platform 114, and the BMS 112 (and its gateway / APIs 136) to exchange information without point-to- point wiring between each device. Table 1 includes representative messaging topics as shown in FIG. 4. Each topic is a publish / subscribe channel with a defined set of data fields.TABLE 1

[0076] The control platform 114 enforces a priority-sequence protocol that, upon confirmed alarm via the building alarm interface 134, for example, preempts non-critical traffic and authorizes elevator routing, hydraulic coupling, and autonomous robotic device deployment with bounded command latency (for example, less than two hundred (200) milliseconds) under nominal conditions. Transport layer encryption with mutual authentication and rotating keys secures signaling loop circuit (SLC) and Internet Protocol (IP) messaging. Controllers fail over to local autonomy and maintain elevator routing, door interlocks, PRV / pump control, and data logging upon loss of external connectivity.

[0077] Telemetry (e.g., pressure, flow, temperature, smoke, leak, coupling, door state, pump and valve positions, agent ratio, corridor pressure, etc.) may be sampled at greater than or equal to one (1) Hz, buffered locally, and published to a building log and to an edge-cloud service. Transport layer encryption, mutual authentication, and rotating keys secure controller communications. On loss of wide-area connectivity, the control platform 114 maintains local autonomy and later performs a conflict-free merge of buffered records with the cloud so that a single authoritative timeline is retained.EXEMPLARY COMPUTER-IMPLEMENTED METHODS

[0078] FIG. 5 is a flowchart illustrating an exemplary computer-implemented method 500 for an exemplary sequence of operations for firefighting staged from an elevator-mounted robot compartment, including standpipe coupling, monitored transfer, hose deployment, pressure and flow regulation, proportioning, purge / flush, resupply, return, and fleet coordination, according to various aspects of the present disclosure. The operations described herein may be performed in the order shown in FIG. 6 or, accordingto certain inventive aspects, may be performed in a different order. Furthermore, some operations may be performed concurrently as opposed to sequentially, and / or some operations may be optional, unless expressly stated otherwise or as may be readily understood by one of ordinary skill in the art.

[0079] The computer-implemented method 500 is described below, for ease of reference, as being executed by exemplary devices and components introduced with the embodiments illustrated in Figures 1-5. In various examples, the computer-implemented method 500 relates to novel techniques for deploying an autonomous robotic device for firefighting from a multi-compartment elevator car, including mating a receptacle to a standpipe quick-connect. While operations within the computer-implemented method 500 are described below regarding the controllers and platforms 110, 112, 114, 136, 300, 424, and 414, according to some aspects of the present disclosure, the computer-implemented method 500 may be implemented using any other computing devices and / or systems through the utilization of processors, transceivers, hardware, software, firmware, or combinations thereof. A person having ordinary skill will also appreciate that responsibility for all or some of such actions may be distributed differently among such devices or other computing devices without departing from the spirit of the present disclosure.

[0080] One or more computer-readable medium(s) may also be provided. The computer-readable medium(s) may include one or more executable programs stored thereon, wherein the program(s) instruct one or more processors or processing units to perform all or certain of the steps outlined herein. The program(s) stored on the computer- readable medium(s) may instruct the processor or processing units to perform additional, fewer, or alternative actions, including those discussed elsewhere herein.

[0081] In various examples, at operation 502, the elevator control unit 110 powers the compartment controller 224. The compartment controller 224 polls environmental sensors 218 and cameras 220. The compartment controller 224 verifies links with the door / interlock controller 300 and the autonomous robotic device controller 414 over the communication network 142. The compartment controller 224 checks the charginginterface 206, the inductive pad 208, and the docking connectors 210. The control platform 114 opens a secure session and collects diagnostics. The control platform 114 blocks dispatch on anomaly.

[0082] In various examples, at operation 504, the autonomous robotic device 132 is staged in the robot-dedicated compartment 108. Controller instructions on non-transitory computer-readable media compute a target landing and a transfer path. The elevator control unit 110 routes the car 104 by issuing elevator routing commands. The control platform 114 supervises motion.

[0083] In various examples, at operation 506, the control platform 114 pre-stages the car 104 at a risk-weighted floor. The building management system 112 provides alarm, occupancy, and context inputs. The control platform 114 uses historical flow and pressure information.

[0084] In various examples, at operation 508, the elevator control unit 110 moves the car 104 to the designated floor. The position sensors 302 confirm landing alignment. The door / interlock controller 300 holds the elevator door system 120 and the landing door system 118 closed and locked. The control platform 114 stops motion on abnormal conditions.

[0085] In various examples, at operation 510, the standpipe 150 presents a fluid nozzle 156 on the shaft sidewall. The receptacle 158 resides in the robot-dedicated compartment 108. The alignment sensor 304 check axial and angular alignment. The door / interlock controller 300 confirms an interlock state on interlock lines 316 before dispensing fluid from the fluid nozzle 156 through the receptacle 158.

[0086] In various examples, at operation 512, the compartment controller 224 commands the solenoid-operated, normally-closed fluid nozzle 156 to dispense fluid through the receptacle 158. The compartment controller 224 actuates the fluid nozzle 156 after alignment checks from the alignment sensor 304 pass. The compartment controller 224 confirms engagement. The control platform 114 logs the coupling state.

[0087] In various examples, at operation 514, controller instructions on non- transitory computer-readable media authorize hydraulic coupling. The compartment controller 224 evaluates alignment, fluid pressure, and interlock signals. The compartment controller 224 establishes a hydraulic path from the standpipe 150 to the compartment agent delivery system 248. The compartment controller 224 continues to monitor for fault conditions.

[0088] In various examples, at operation 516, flow proceeds from the fluid nozzle 156 through the receptacle 158 and into the reservoir 288. Flow then proceeds to the pressure-reducing valve 364. The pressure-reducing valve 364 maintains a downstream operating band of ninety-five (95) psi to one hundred and twenty-five (125) psi. Downstream devices include the check valve 368, the booster pump 170, and the hose interface 372. The hose interface 372 includes the hose reel 374, the swivel 376, and the strain-relief 378. The drain / purge valve 382 manages purge and test discharge. The thermal and splash-resistant housing 260 encloses the assembly.

[0089] In various examples, at operation 518, the control platform 114 and / or the compartment controller 224 adjust an agent proportioning ratio, via the proportioning assembly 366, between and including one tenth percent (0.1%) and ten percent (10%). Options include the eductor 330, the mass-based metering system 332 with the load cell 334, and the volumetric metering system 336 with dual flowmeters. The control valve 340 sets concentration. The proportioning assembly 366 is agent-agnostic. The reservoir 388 and the weighted baseplate sensor 340 support delivered volume validation by mass change over time.

[0090] In various examples, at operation 520, the door / interlock controller 300 actuates only the subset of the elevator door system 120 panels aligned to the landing door system 118. The position sensors 302, the alignment sensor 304, and the encoders 308a / 308b verify the opening sequence. The door / interlock controller 300 keeps passengeraccess panels closed and locked. The control platform 114 records the event.

[0091] In various examples, at operation 522, the door / interlock controller 300 maintains the autonomous robotic device corridor 314 at a positive pressure of five (5) Pa to twenty-five (25) Pa during transfer. The fluid moving device 310 provides airflow. The door / interlock controller 300 ties ventilation control to door state and corridor sensing.

[0092] In various examples, at operation 524, the door / interlock controller 300 verifies a monitored transfer. The cameras 220 and beam sensors monitor the path. The autonomous robotic device controller 414 reports motion and pose. The control platform 114 cross-checks transfer progress. The door / interlock controller 300 closes and locks the elevator door system 120 and the landing door system 118 after the autonomous robotic device 132 clears the path.

[0093] In various examples, at operation 526, the autonomous robotic device 132 deploys via the hose interface 372. The robot-side quick-disconnect 358 with the latch assembly 360 and a proximity switch may confirm coupling with the autonomous robotic device 132. The control platform 114 and the autonomous robotic device controller 414 monitor hose tension and payout. The compartment controller 224 halts pressurization on uncoupling or excessive tension.

[0094] In various examples, at operation 528, the compartment controller 224 enables the booster pump 170 to provide pressurized fluid to the autonomous robotic device 132 via the hose interface 372. The compartment controller 224 may increase a delivered pressure by staged pump speeds or valve adjustments.

[0095] In various examples, at operation 530, the compartment controller 224 regulates a nozzle pressure and / or a flow setpoint. Pressure feedback is taken at the hose interface 372. The pressure-reducing valve 364 maintains the downstream operating pressure within ninety-five (95) psi to one hundred and twenty-five (125) psi. The compartment controller 224 records one or more setpoints and measured values. The control platform 114 stores telemetry data in a data log.

[0096] Optionally, in various examples, at operation 532, the compartment controller 224 asserts an agent-delivery interlock. Interlock events include, for example, one or more of the following: hose uncoupling, over-pressure, coupling misalignment, passenger-door unlock, and the like. The compartment controller 224 withholds flow authorization. The compartment controller 224 keeps actuators de-energized until the system returns to a safe state. The interlock lines 316 add feedback report status. The control platform 114 logs the event in the data log.

[0097] In various examples, at operation 534, the compartment controller 224 purges and flushes one or more fluid lines of the agent delivery system 248. The drain / purge valve 382 routes discharge, for example, to the reservoir 388. The compartment controller 224 retracts and stows the hose 380 at the hose reel 374. The control platform 114 logs service intervals in the data log.

[0098] In various examples, at operation 536, the autonomous robotic device 132 may be resupplied in the robot-dedicated compartment 108. The control platform 114 logs consumable replenishment and pressures. The reservoir 388 and the weighted baseplate sensor 340 support flow testing during maintenance. The control platform 114 updates readiness.

[0099] In various examples, at operation 538, the autonomous robotic device 132 returns to the robot-dedicated compartment 108. The door / interlock controller 300 repeats the aligned and interlocked opening sequence in reverse. The door / interlock controller 300 closes and locks the elevator door system 120 and the landing door system 118. The control platform 114 stores the session record.

[0100] In various examples, at operation 540, the autonomous robotic device 132 recharges at the charging interface 206. The control platform 114 logs mission outcomes, consumable usage, and faults, for example, in the data log. The control platform 114 updates readiness. The control platform 114 publishes status to queues and dashboards on the communication network 142.

[0101] Optionally, in various examples, at operation 542, the control platform 114 coordinates fleets across multiple car 104 installations and buildings. The compartment controller 224, the door / interlock controller 300, and the autonomous robotic device controller 414 continue locally and buffer data if the cloud is unavailable. A satellite bridge 140 used by the control platform 114 may provide an alternate backhaul path. The control platform 114 prioritizes life-safety missions.

[0102] In various examples, components and setpoints are implemented to conform with applicable NFPA requirements and authority-having-jurisdiction rules.

[0103] In various examples, any or all of the foregoing operations are implemented by controller instructions on non-transitory computer-readable media. The controller instructions on non-transitory computer-readable media include computing a route, verifying alignment, authorizing hydraulic coupling, regulating pressure and flow, actuating a subset of door panels, maintaining corridor positive pressure, deploying via a hose interface, enabling a booster on error, adjusting proportioning, asserting an agentdelivery interlock, purging and flushing and retracting, pre-staging, and coordinating fleet deployments.

[0104] As described above, the emergency response system provides technical advantages in safety, reliability, and scalability by coupling elevator-based staging with a standpipe quick-connect and a compartment receptacle that achieve rapid, sensor- verified hydraulic hookup. A pressure-regulation stage holds a narrow downstream operating band, while booster logic automatically raises delivered pressure when nozzle feedback indicates sustained shortfall, improving flow stability across elevation and friction losses. An agentproportioning module supports low-to-high mix ratios under closed-loop control, and a dedicated purge / flush path shortens turnaround and reduces contamination between missions. A hose interface with managed payout, swivel, strain relief, and coupling verification improves deployment control and reduces uncoupling risk. During transfer, subset actuation of multi-panel doors combined with active corridor pressurization maintains a positive pressure bias that limits smoke infiltration and protects occupantswhile minimizing landing dwell time. Safety is further enhanced by an agent-delivery interlock that withholds flow authorization on defined events (including over-pressure, misalignment, door faults, or hose uncoupling) until the system returns to a confirmed safe state. Mass-based flow verification at the reservoir enables code-aligned test modes, supports predictive maintenance, and provides auditable delivery records. Risk-weighted pre-staging, monitored transfer using multi-sensor confirmation (with optional fiduciary guidance), and automated purge / flush collectively reduce response latency and cycle time. A publish / sub scribe messaging fabric allows controllers to exchange only relevant topics, enabling graceful degradation with local buffering and optional alternate backhaul. Fleet scheduling across multiple cars and buildings prioritizes life-safety tasks, reduces contention at doors and landings, and increases throughput without increasing floor area. Together, these features reduce false positives, enhance occupant safety, and raise mission reliability and tempo relative to manually staged approaches.ADDITIONAL CONSIDERATIONS

[0105] In this description, references to “one embodiment,” “an embodiment,” or “embodiments” mean that the feature or features being referred to are included in at least one embodiment of the technology. Separate references to “one embodiment,” “an embodiment,” or “embodiments” in this description do not necessarily refer to the same embodiment and are also not mutually exclusive unless so stated and / or except as will be readily apparent to those skilled in the art from the description. For example, a feature, structure, act, etc. described in one embodiment may also be included in other embodiments but is not necessarily included. Thus, the current technology can include a variety of combinations and / or integrations of the embodiments described herein.

[0106] Although the present application sets forth a detailed description of numerous different embodiments, the legal scope of the description is defined by the words of the claims and equivalent language. The detailed description is to be construed as exemplary only and does not describe every possible embodiment because describing everypossible embodiment would be impractical. Numerous alternative embodiments may be implemented, using either current technology or technology developed after the filing date of this patent, which would still fall within the scope of the claims.

[0107] Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order recited or illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein. The foregoing statements in this paragraph shall apply unless so stated in the description and / or except as will be readily apparent to those skilled in the art from the description.

[0108] Certain embodiments are described herein as including logic or a number of routines, subroutines, applications, or instructions. These may constitute either software (e.g., code embodied on a machine-readable medium or in a transmission signal) or hardware. In hardware, the routines, etc., are tangible units capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as computer hardware that operates to perform certain operations as described herein.

[0109] In various embodiments, computer hardware, such as a processor, may be implemented as special purpose or as general purpose. For example, the processor may comprise dedicated circuitry or logic that is permanently configured, such as anapplication-specific integrated circuit (ASIC), or indefinitely configured, such as a field- programmable gate array (FPGA), to perform certain operations. The processor may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement the processor as special purpose, in dedicated and permanently configured circuitry, or as general purpose (e.g., configured by software) may be driven by cost and time considerations.

[0110] The processor may comprise one or more processors that include electronic hardware components such as microprocessors (single-core or multi-core), microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), analog and / or digital application-specific integrated circuits (ASICs), artificial intelligence circuitry, graphics processing units (GPUs), neural processing units (NPUs), artificial intelligence (Al) accelerators, tensor processing units (TPUs), or the like, or combinations thereof. The processor may further include system on a chip (SoC) architectures. In various embodiments, the processor may include multiple computational components and functional blocks that are packaged separately but function as a single unit. In various embodiments, the processor may further include multiprocessor architectures, parallel processor architectures, processor clusters, and the like, which provide high performance computing. The processor may be in electronic communication with the other electronic components of a computing device through serial or parallel links that include universal busses, address busses, data busses, control lines, and the like. In addition, the processor may include analog to digital converters (ADCs) to convert analog electronic signals to digital data values in binary form (such as by sampling), or streams of digital data values, and / or digital to analog converters (DACs) to convert digital data values, or streams of digital data values, to analog electronic signals.[OHl] The processor generally executes, processes, or runs algorithms, instructions, code, code segments, code statements, software, firmware, programs,applications, apps, processes, services, daemons, or the like. The processor is operable, configured, programmed, and / or trained to perform the previously listed items by utilizing hardware, software, firmware, or combinations thereof. Other components of a computing device, such as the communication element and the memory element, may be utilized as well. In certain embodiments, the processor may also have access to, and be in electronic communication with, cloud computing services, wherein a portion of the functions, operations, processes, methods, and / or algorithms of the processor are performed by computing resources off-site. Additionally, or alternatively, the processor may include components, such as cloud computing components, that are physically located in a plurality of different geolocations but are able to function as a single unit.

[0112] The processor may further be configured to host and operate a large language model (LLM) or generative pretrained transformer (GPT) to implement generative Al. The LLM or GPT may include, or be formed by, neural networks such as artificial neural networks (ANNs), autoencoders, convolutional neural networks (CNNs), feedforward neural networks (FNNs), recurrent neural networks (RNNs), transformer architectures, and the like, or combinations thereof.

[0113] Accordingly, the term “processor” or equivalents should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which the processor is temporarily configured (e.g., programmed), each of the processors need not be configured or instantiated at any one instance in time. For example, where the processor includes a general-purpose processor configured using software, the general-purpose processor may be configured as respective different processors at separate times. Software may accordingly configure the processor to constitute a particular hardware configuration at one instance of time and to constitute a different hardware configuration at a different instance of time.

[0114] Computer hardware components, such as transceiver elements, memory elements, processors, and the like, may provide information to, and receive information from, other computer hardware components. Accordingly, the computer hardware components described may be regarded as being communicatively coupled. Where multiple such computer hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the computer hardware components. In embodiments in which multiple computer hardware components are configured or instantiated at separate times, communication between such computer hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple computer hardware components have access. For example, one computer hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further computer hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Computer hardware components may also initiate communications with input or output devices, and may operate on a resource (e.g., a collection of information).

[0115] The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor- implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor- implemented modules.

[0116] Similarly, the methods or routines described herein may be at least partially processor implemented. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented hardware modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processors may be located in a specific location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.

[0117] Unless specifically stated otherwise, discussions herein using words such as “processing,” “computing,” “calculating,” “determining,” “presenting,” “displaying,” or the like may refer to actions or processes of a machine (e.g., a computer with a processor and other computer hardware components) that manipulates or transforms data represented as physical (e g., electronic, magnetic, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.

[0118] As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a nonexclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.

[0119] Although the disclosure has been described with reference to the embodiments illustrated in the attached figures, it is noted that equivalents may be employed, and substitutions made herein, without departing from the scope of the disclosure as recited in the claims.

[0120] Having thus described various embodiments of the disclosure, what is claimed as new and desired to be protected by Letters Patent includes the following:

Claims

IN THE CLAIMS1. An emergency response system comprising: multi-compartment elevator system including: an elevator car disposed in an elevator shaft, the elevator car including a robot- dedicated compartment configured to carry an autonomous robotic device; a shaft standpipe extending along the elevator shaft, the shaft standpipe including a fluid nozzle positioned along the shaft standpipe; and a control platform coordinating operation of the elevator car and the autonomous robotic device for deployment within a building, the robot-dedicated compartment including: a receptacle that aligns with the fluid nozzle of the shaft standpipe; an agent delivery system fluidly coupled to the receptacle; and a hose interface fluidly coupled to the agent delivery system and connectable to the autonomous robotic device.

2. The emergency response system of claim 1, the receptacle being mounted proximate a rear wall of the robot-dedicated compartment.

3. The emergency response system of claim 1, the agent delivery system including a pressure-reducing valve configured to maintain a downstream operating pressure in a range between and including ninety-five (95) pounds per square inch (psi) and one hundred and twenty-five (125) psi.

4. The emergency response system of claim 1, the agent delivery system including a proportioning assembly adjustable in a range between and including one tenth of a percent (0.1%) and ten percent (10%)..

5. The emergency response system of claim 1, further comprising: a booster pump configured to increase a delivered downstream operating pressure.

6. The emergency response system of claim 1, further comprising: a plurality of sensors disposed in the robot-dedicated compartment, the plurality of sensors including one or more of the following: pressure, flow, temperature, smoke detector, leak, and coupling engagement sensors; and a weighted baseplate sensor configured to infer a delivered flow from a change in mass over time.

7. The emergency response system of claim 1, the hose interface including: a strain relief and swivel adjacent a latch assembly, and a hose reel positioned in the robot-dedicated compartment.

8. The emergency response system of claim 1, the autonomous robotic device being attachable to a nozzle selected from one or more of the following: fog, straight stream, automatic, combination, Compressed Air Foam System (CAFS), and portable monitor nozzles.

9. The emergency response system of claim 1, further comprising: an autonomous robotic device corridor extending between the robot-dedicated compartment and a landing, the autonomous robotic device corridor including a fluid moving device configured to maintain a positive pressure in a range between and including five (5) pascals (Pa) and twenty-five (25) Pa.

10. The emergency response system of claim 1, the control platform being configured to coordinate deployment of a fleet of autonomous robotic devices staged in the robot-dedicated compartment.

11. An agent delivery system for installation in a robot-dedicated compartment of an elevator system, the agent delivery system comprising: a receptacle that aligns with a fluid nozzle of a shaft standpipe; a pressure-reducing valve downstream of the receptacle; a proportioning assembly downstream of the pressure-reducing valve; a pressure transducer; a flowmeter; a booster pump; and a hose reel terminating in a coupling latch assembly.

12. The agent delivery system of claim 11, the proportioning assembly including one or more of the following: an eductor, a massbased metering system having a load cell, and a volumetric system including two (2) flowmeters.

13. The agent delivery system of claim 11, further comprising: a plurality of sensors including one or more of the following: temperature, smoke detector, leak, and coupling engagement sensors.

14. The agent delivery system of claim 11, further comprising: a thermal barrier; and a splash-containment housing enclosing the pressure-reducing valve, the proportioning assembly, and the hose reel.

15. The agent delivery system of claim 11, the booster pump including a centrifugal pump assembly configured to track one or more of a nozzle pressure and a flow setpoint.

16. The agent delivery system of claim 11, the hose reel including a hose having a length in a range between and including twenty- five (25) feet (ft) and one hundred and fifty (150) ft.

17. The agent delivery system of claim 11, further comprising: a check valve positioned to restrict reverse flow toward the shaft standpipe.

18. A method comprising: providing an elevator car having a passenger compartment and a robot-dedicated compartment; staging the autonomous robotic device within the robot-dedicated compartment; routing the elevator car to a target landing; mating a receptacle positioned in the robot-dedicated compartment to a fluid nozzle of a shaft standpipe; supplying fluid from the shaft standpipe through an agent delivery system in the lower robot-dedicated compartment; regulating one or more of a nozzle pressure and flow setpoint; and deploying the autonomous robotic device via a hose interface from the robot-dedicated compartment.

19. The method of claim 18, further comprising: adjusting an agent proportioning ratio in a range between and including one tenth of a percent (0.1%) and ten percent (10%).

20. The method of claim 18, further comprising: maintaining an autonomous robotic device corridor positive pressure in a range between and including five (5) pascals (Pa) and twenty-five (25) Pa.

21. The method of claim 18, further comprising: asserting an agent delivery interlock in response to one or more of the following detected events: hose uncouple, over pressure, coupling misalignment, and passenger door unlock.

22. The method of claim 18, wherein regulating the nozzle pressure includes maintaining a downstream operating pressure in a range between and including ninety-five (95) pounds per square inch (psi) and one hundred and twenty-five (125) psi.

23. The method of claim 18, further comprising: purging and flushing one or more lines; and retracting a hose.

24. The method of claim 18, further comprising: pre-staging the elevator car at a risk-weighted floor according to one or more risk- associated rules.

25. The method of claim 18, further comprising: increasing a delivered downstream operating pressure.

26. The method of claim 18, further comprising: coordinating deployment of a fleet of autonomous robotic devices staged in the robot- dedicated compartment.

27. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a controller, cause the controller to: compute a target landing and a transfer path; route the elevator car to the target landing by issuing one or more elevator routing commands; verify alignment between a fluid nozzle of a shaft standpipe and a receptacle of a robot- dedicated compartment; authorize hydraulic coupling; regulate one or more of a nozzle pressure and flow setpoint; actuate a subset of door panels of the robot-dedicated compartment to form a monitored transfer path while passenger doors remain closed and locked; maintain autonomous robotic device corridor positive pressure; and deploy the autonomous robotic device via a hose interface from the robot-dedicated compartment.

28. The non-transitory computer-readable medium of claim 27, wherein regulating one or more of the nozzle pressure and flow setpoint includes enabling a booster pump.

29. The non-transitory computer-readable medium of claim 27, further comprising instructions that cause the controller to: adjust an agent proportioning ratio in a range between and including one tenth of a percent (0.1%) and ten percent (10%).

30. The non-transitory computer-readable medium of claim 27, wherein maintaining the autonomous robotic device corridor positive pressure comprises maintaining the positive pressure in a range between and including five (5) pascals (Pa) and twenty-five (25) Pa.

31. The non-transitory computer-readable medium of claim 27, further comprising instructions that cause the controller to: assert an agent delivery interlock in response to one or more of the following detected events: hose uncouple, over pressure, coupling misalignment, and passenger door unlock.

32. The non-transitory computer-readable medium of claim 27, wherein regulating the nozzle pressure includes maintaining a downstream operating pressure in a range between and including ninety-five (95) pounds per square inch (psi) and one hundred and twenty-five (125) psi.

33. The non-transitory computer-readable medium of claim 27, further comprising instructions that cause the controller to: purge and flush one or more lines; and retract a hose.

34. The non-transitory computer-readable medium of claim 27, further comprising instructions that cause the controller to: pre-stage the elevator car at a risk-weighted floor according to one or more risk-associated rules.

35. The non-transitory computer-readable medium of claim 27, further comprising instructions that cause the controller to: coordinate deployment of a fleet of autonomous robotic devices staged in the robot- dedicated compartment.

36. A multi-structure coordination system comprising: a communication network including an edge-cloud framework and one or more of a satellite link and a government emergency services network; and a plurality of elevator-mounted firefighting nodes coupled in communication via the communication network, the coordination system aggregating telemetry, dispatching elevators, and allocating autonomous robotic devices across multiple structures according to tenability and propagation risk.

37. The coordination system of claim 36, each elevator-mounted firefighting node buffering data locally upon communication loss with the communication network and synchronizing to the edge-cloud framework upon reconnection to the communication network using conflict-free merging of one or more event logs.

38. The coordination system of claim 36, each elevator-mounted firefighting node including a communication interface conforming to an Incident Command System (ICS) schema, enabling multi-agency command and cross-jurisdictional access control.

39. The coordination system of claim 36, the coordination system pre-planning elevator staging across the multiple structures using predictive analytics derived from historical flow and pressure profiles and environmental context.

40. An elevator-mounted flow compliance apparatus comprising: a reservoir disposed in a robot-dedicated compartment of an elevator system; a weighted baseplate sensor positioned under the reservoir; and a controller configured to: infer a delivered fluid flow from mass change over time, and compare the inferred delivered fluid flow to a predefined threshold value.

41. The flow compliance apparatus of claim 40, the controller configured to gate proportioning and pump enablement when the inferred delivered fluid flow is below the threshold value for a predefined interval.

42. The flow compliance apparatus of claim 40, the controller configured to achieve, based on reference weights and temperature compensation, a mass-to-flow accuracy of plus or minus three (3) percent over a flow in the range between and including twenty-five (25) gallon per minute (GPM) to one hundred and fifty (1 0) GPM.

Images