Resource Allocation Plan for User Requirements

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing resource allocation systems primarily follow a first-come, first-served approach, lacking responsiveness to user requirements and preferences, and are limited to short-term planning, hindering efficient use of resources and compliance with safety-critical constraints.

Innovation Solution

A computer-implemented method that utilizes resource availability and user requirements data to generate a resource allocation plan, prioritizing users' needs, reducing computational complexity, and optimizing resource allocation while adhering to safety constraints, such as social distancing and fire safety rules, by allocating resources based on user preferences and contingency needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If resource allocation is done on a first come, first served basis, then the allocation process is simple, but the system does not respond to user requirements and preferences

Engineering Contradiction:

Improveallocation process simplicityVSAvoidresponsiveness to user requirements

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

Users submit their own resource requests with requirements and preferences through the system, allowing them to self-serve rather than relying on manual allocation. The system automatically processes these requests against availability data and constraints, resolving the contradiction by enabling user-driven allocation that is both simple to operate and responsive to requirements.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Users pre-submit their resource requirements and preferences before the allocation period begins. This preliminary action allows the system to plan allocations in advance based on known requirements rather than reacting to ad-hoc requests, improving responsiveness while maintaining systematic simplicity.

Inventive Principle:

Principle #10Preliminary action

2Speed

If resource allocation planning is limited to a short time horizon, then the allocation process is faster, but long term scheduling and capacity planning are hindered

Engineering Contradiction:

Improveallocation process speedVSAvoidplanning time horizon

Core Design Contradiction:

SpeedVSDuration of action of moving object

Solution Approach 1:

The allocation process is segmented into multiple time horizons: short-term allocations for immediate needs and long-term capacity planning for future needs. The system generates allocation plans at different levels (daily, weekly, monthly) allowing fast processing for immediate allocations while simultaneously performing strategic capacity planning for longer periods, thus resolving the speed-horizon contradiction.

Inventive Principle:

Principle #1Segmentation

3Productivity

If computationally expensive allocation and optimization methods are used, then resource allocation optimizes user requirements, but computational complexity and resource usage increase

Engineering Contradiction:

Improveresource allocation efficiencyVSAvoidcomputational complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The allocation process is divided into two segments: a static allocation phase that assigns resources based on user requirements without complex optimization, and a subsequent optimization phase that only processes remaining resources. This segmentation reduces computational complexity by avoiding expensive optimization methods for all allocations while still achieving overall optimization where needed.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of applying computationally expensive optimization methods to all resource allocations, the system applies them partially only to remaining resources after static allocation. This partial action achieves sufficient allocation efficiency while dramatically reducing computational complexity and resource usage.

Inventive Principle:

Principle #16Partial or excessive action

4Device complexity

If resources are allocated without considering safety constraints, then the allocation process is simpler, but compliance with safety-critical constraints is violated

Engineering Contradiction:

Improveallocation process complexityVSAvoidsafety constraint compliance

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

Safety constraints are pre-configured and embedded into the allocation system before the allocation process begins. The system automatically checks and enforces these constraints (such as social distancing requirements and fire safety rules) during allocation, making compliance automatic rather than manual, thus maintaining simplicity while ensuring reliability.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11409561B2System and method for schedule optimization

Publication Date: 2022.08.09 HUBSTAR INT LTD

AI summary

A computer-implemented method including: obtaining resource availability data indicative of a set of one or more resources available at a future time period, wherein the set of one or more resources are allocable to a plurality of resource users; obtaining requirements data indicative of a requirement for a subset of the plurality of resource users to have access to a subset of the set of one or more resources; and generating a resource allocation plan for the future time period based on the resource availability data and the requirements data. Generating the resource allocation plan includes allocating, to the subset of the plurality of resource users, the subset of the set of one or more resources; and allocating, to one or more other resource users of the plurality of resource users, at least a portion of the resources remaining from the set of one or more resources.