Elevator Code Update Gateway for Staged Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software updates in passenger conveyance systems like elevators can cause disruptions if performed ad-hoc and may lead to customer dissatisfaction, necessitating a more controlled and efficient method to minimize service interruptions.

Innovation Solution

A system and method involving a component management system (CMS) and an elevator system controller (ESC) with a gateway that manages the installation of updated code through preliminary and secondary installations, using a virtual system for testing and strategic deployment based on utilization patterns and locations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If software updates are performed ad-hoc, then updates can be applied quickly, but service disruptions occur and customer satisfaction decreases

Engineering Contradiction:
Improveupdate speedVSAvoidservice continuity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by installing the software update on a virtual system first, allowing testing and validation before actual deployment to physical components. This preliminary installation phase enables identification of potential issues without affecting live service, thus maintaining service continuity while still enabling timely updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The update process is segmented into distinct phases: preliminary installation on virtual system, testing phase, and secondary installation on physical components. This segmentation allows the update to be applied in controlled stages, preventing simultaneous disruption across the entire system while maintaining update efficiency.

Inventive Principle:
Principle #1Segmentation

2Productivity

If software updates are performed ad-hoc, then updates can be applied quickly, but more updates and disruptions may result from customer dissatisfaction

Engineering Contradiction:
Improveupdate deployment efficiencyVSAvoidupdate management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system incorporates feedback mechanisms where the ESC monitors the virtual system performance and customer satisfaction levels. Based on this feedback, the system can adjust update strategies, pause updates if dissatisfaction is detected, or proceed with secondary installation if satisfaction is confirmed, thereby managing complexity through informed decision-making.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The ESC automatically monitors update status, customer satisfaction, and system performance without requiring constant human intervention. The system self-regulates the update process by deciding when to proceed to secondary installation or when to pause based on predefined criteria, reducing management complexity while maintaining efficient update deployment.

Inventive Principle:
Principle #25Self-service

3Stability of the object's composition

If updates are installed on all components simultaneously, then updates are applied uniformly, but service disruptions occur

Engineering Contradiction:
Improveupdate consistencyVSAvoidservice continuity
Core Design Contradiction:
Stability of the object's compositionVSReliability

Solution Approach 1:

The system segments the component population into virtual system components and physical system components, and further divides physical components into subsets based on location or utilization patterns. Updates are applied first to virtual components, then progressively to physical components in segmented batches, ensuring consistency while preventing simultaneous disruption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies different update strategies to different subsets of components based on their specific characteristics such as location, utilization patterns, or criticality. Less critical or less utilized components may receive updates first or during off-peak times, while critical components are updated during maintenance windows, maintaining service continuity while ensuring uniform eventual coverage.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20260008651A1System and method for updating code in passenger conveyance systems
Publication Date: 2026.01.08 OTIS ELEVATOR CO
  • US20260008651A1 patent drawing
  • US20260008651A1 patent drawing
  • US20260008651A1 patent drawing

AI summary

An elevator system for installing updated code on elevator components in a building, the system having: a component management system (CMS); an elevator system controller (ESC) in the building, operationally coupled to the components; a gateway that communicates with the ESC and the components over a first network and with the CMS over a second network, wherein the gateway is configured to: receive a first signal from the CMS that includes a notification of the updated code for the components; receive a second signal from the ESC that includes instructions for a preliminary installation of the updated code, and thereafter execute the preliminary installation; and receive a third signal from the ESC that includes instructions for a secondary installation of the updated code on the components, and thereafter execute the secondary installation.