Elevator Component Tracking for Lifecycle Verification and Maintenance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing elevator maintenance systems lack detailed traceability and accuracy in monitoring the lifecycle of safety-related components, such as belts and ropes, necessitating improved documentation and verification to ensure the use of correct components and prevent overuse or misuse.

Innovation Solution

Implementing electronic information plates on elevator components that store data like operation cycles, manufacturing details, and safety thresholds, which are read by a fixed reader and transmitted to a controller for analysis and action when thresholds are exceeded, ensuring real-time monitoring and automated maintenance actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If manual book keeping and counter resetting is used for component lifecycle tracking, then device complexity is reduced, but measurement precision and reliability of component lifecycle monitoring deteriorate

Engineering Contradiction:
Improvemaintenance system complexityVSAvoidcomponent lifecycle monitoring accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent replaces manual mechanical book-keeping processes with an automated electronic information system. Electronic information plates containing component data are automatically read by reader devices, and the controller systematically processes this information to monitor component lifecycles, replacing manual counting and resetting operations with automated electronic tracking.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables self-service monitoring where the electronic information plates and reader devices automatically track component usage and lifecycle without requiring manual intervention. The controller autonomously compares threshold values with elevator counters and detects when components need replacement, eliminating the need for manual book-keeping and counter management.

Inventive Principle:
Principle #25Self-service

2Device complexity

If manual maintenance tracking is used, then device complexity is lower, but traceability and verification of component lifecycle deteriorate

Engineering Contradiction:
Improvemaintenance tracking system complexityVSAvoidcomponent traceability
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent replaces manual tracking methods with automated electronic information plates that systematically record component data. These plates contain encoded information about component identity, installation date, and lifecycle parameters, which are automatically read and stored by the controller, ensuring complete traceability without manual documentation.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system implements continuous feedback loops where the reader devices automatically read electronic information plates, the controller compares threshold values with actual usage data from elevator counters, and the system generates maintenance alerts when components approach their lifecycle limits, ensuring complete information tracking and verification.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If automated electronic monitoring is implemented, then measurement precision and reliability of component monitoring improve, but device complexity increases

Engineering Contradiction:
Improvecomponent lifecycle monitoring accuracyVSAvoidmaintenance system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the monitoring system into distinct functional modules: electronic information plates containing component data, reader devices for automatic data capture, and a controller for processing and analysis. This segmentation allows each component to perform its specific function efficiently while reducing overall system complexity through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The controller serves multiple functions within the system: it receives and processes data from reader devices, compares threshold values with elevator counters, detects when components need replacement, and generates maintenance alerts. This multi-functionality reduces the need for separate dedicated devices for each task, thereby managing system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Productivity

If automated reading and transmission of electronic information is implemented, then productivity of maintenance operations improves, but loss of time for system setup and configuration increases

Engineering Contradiction:
Improvemaintenance operation efficiencyVSAvoidsystem setup time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-configuring electronic information plates with component data before installation and pre-programming the controller with threshold values and monitoring parameters. This preliminary setup eliminates the need for manual data entry and configuration during maintenance operations, significantly improving productivity once the system is operational.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3519337B1Maintenance method of an elevator component
Publication Date: 2026.03.11 KONE OYJ
  • EP3519337B1 patent drawingFigure 1a
  • EP3519337B1 patent drawingFigure 1b
  • EP3519337B1 patent drawingFigure 2

AI summary

Elevator components can be equipped with an electronic information plate (105). The electronic information plate (105) is associated with a particular electronic information plate that can store different properties of the associated component. The content of each electronic information plate (105) is read manually or automatically and transmitted to a controller (110). The controller (110) analyzes the received content and launches a predetermined action if the content indicates a need for maintenance.