Relative Performance Specification for System Design

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing system design methods often neglect performance goals or rely on inadequate specifications, failing to account for relative changes in the business environment and technological advancements, making it difficult to ensure system performance meets evolving demands.

Innovation Solution

A computer-implemented method that receives a relative performance specification for a system, using a database of relative performance data to determine a system design that meets the specified performance level, allowing for interpolation or extrapolation between existing designs, and incorporating benchmarking and user interface features for optimal performance and cost considerations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If explicit performance goals are specified, then system design precision is improved, but the difficulty of determining appropriate performance goals increases

Engineering Contradiction:
Improvesystem design precisionVSAvoiddifficulty of determining performance goals
Core Design Contradiction:
Manufacturing precisionVSDifficulty of detecting and measuring

Solution Approach 1:

The patent uses readily available benchmark data from existing systems as a disposable reference point. Instead of requiring complex analysis to determine performance goals, the system leverages easily obtainable data from current running systems, treating this baseline information as a starting point that can be quickly updated as new benchmarks become available.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Solution Approach 2:

The patent transforms the performance specification from absolute values to relative changes. By expressing performance goals as percentages of improvement over existing systems rather than requiring precise absolute target values, the system allows designers to specify meaningful improvements without needing to determine exact performance targets.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If absolute performance values from existing systems are used as specifications, then ease of operation is improved, but adaptability to changing business environment deteriorates

Engineering Contradiction:
Improveease of specifying performance goalsVSAvoidadaptability to business environment changes
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent makes the performance specification dynamic by expressing it as a relative improvement percentage rather than a fixed absolute value. This allows the specification to automatically adapt to changing business environments - as existing systems improve over time, the same percentage improvement represents different absolute performance levels, keeping the system adaptable without requiring frequent manual updates to performance targets.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent performs preliminary analysis by establishing a baseline from existing system performance data before designing the new system. This preliminary benchmarking action provides a foundation for setting performance goals that is both easy to obtain and inherently adaptable, as it is based on current real-world performance rather than theoretical or historical absolute values.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If best effort performance approach is used, then ease of operation is improved, but manufacturing precision of system design deteriorates

Engineering Contradiction:
Improveease of system designVSAvoidsystem performance specification
Core Design Contradiction:
Ease of operationVSManufacturing precision

Solution Approach 1:

The patent changes the performance specification parameter from vague qualitative terms to quantitative relative improvement percentages. Instead of using best effort approaches with undefined performance targets, the system requires specifications expressed as measurable percentages of improvement over benchmark systems, maintaining ease of specification while achieving precise performance targets.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent introduces feedback by comparing the new system design against benchmark data from existing systems. This feedback mechanism ensures that performance specifications are not merely best efforts but are grounded in actual measured performance from comparable systems, providing a reference point that improves design precision while maintaining operational simplicity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9367647B2Method of providing system design
Publication Date: 2016.06.14 HEWLETT PACKARD ENTERPRISE DEV LP
  • US9367647B2 patent drawing
  • US9367647B2 patent drawing
  • US9367647B2 patent drawing

AI summary

An embodiment of a computer implemented method of providing a design of a system receives a relative performance specification for the system. A particular system design is returned that is expected to perform at about the relative performance specification.