Hardware Resource Update Scheduling for Meeting Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In networked computer systems, scheduled maintenance of hardware resources often conflicts with scheduled meetings, leading to unavailability of resources and diminished meeting capacity, as existing communication methods, such as email exchanges, are inadequate for managing cross-referenced systems in large enterprises.

Innovation Solution

A method that retrieves the time, date, and location of future meetings requiring specific hardware resources, determines if those resources are scheduled for maintenance, assesses the level of detriment to the meeting if the resources are not updated, and adjusts the maintenance schedule to ensure resource availability by rescheduling updates or relocating resources as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hardware resources are scheduled for maintenance during meetings, then maintenance updates can be performed, but hardware resources become unavailable and meeting capacity is diminished

Engineering Contradiction:
Improvehardware resource availabilityVSAvoidmeeting capacity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by checking maintenance schedules against meeting schedules in advance and proactively rescheduling maintenance to times when hardware resources are not needed, preventing conflicts before they occur

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts maintenance schedules based on real-time meeting data and resource availability, making the maintenance timing flexible rather than fixed to resolve conflicts with meeting capacity

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If manual email exchanges are used to coordinate between meeting organizers and maintenance personnel, then communication can occur, but the process becomes inefficient and infeasible in large enterprises with numerous meetings and cross-referenced systems

Engineering Contradiction:
Improvecoordination processVSAvoidscheduling coordination time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system enables self-service by automatically detecting conflicts between meeting schedules and maintenance schedules, and autonomously rescheduling maintenance without requiring manual intervention from meeting organizers or maintenance personnel

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system acts as an intermediary by integrating with both meeting management systems and maintenance management systems, automatically coordinating between them and eliminating the need for direct manual communication between disparate groups

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If hardware resources are updated during meetings, then maintenance can be completed, but the hardware resource may need to be relocated or meetings may need to be rescheduled

Engineering Contradiction:
Improvehardware resource functionalityVSAvoidresource allocation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by identifying suitable alternative hardware resources in advance and pre-configuring them to replace the maintenance target resource, ensuring seamless substitution without disrupting meetings

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9881269B2Collaborative infrastructure update scheduling
Publication Date: 2018.01.30 LENOVO GLOBAL TECHNOLOGIES SWITZERLAND INTERNATIONAL GMBH
  • US9881269B2 patent drawing
  • US9881269B2 patent drawing
  • US9881269B2 patent drawing

AI summary

A method, system, and/or computer program product manages update operations for a hardware resource. A time, date, and location of the future meeting for which a predetermined feature from a hardware resource has been designated as being required for the future meeting is retrieved from a calendar. A determination is made as to whether or not the predetermined feature of the hardware resource is scheduled for updating during the time and date of the future meeting at said location. A level of detriment that will occur to the future meeting if the future meeting proceeds without the updating of the predetermined feature from the hardware resource is determined. A schedule for updating the hardware resource is then adjusted according to the level of detriment that will occur to the future meeting if the future meeting proceeds without the updating of the predetermined feature from the hardware resource.