InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

System and method to optimize cloud project priorities through a currency queueing system

IP.com Disclosure Number: IPCOM000239615D
Publication Date: 2014-Nov-19
Document File: 3 page(s) / 285K

Publishing Venue

The IP.com Prior Art Database


A system and method to optimize cloud project priorities through a currency queueing system is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 42% of the total text.

Page 01 of 3

System and method to optimize cloud project priorities through a currency queueing system

Disclosed is a system and method to optimize cloud project priorities through a currency queueing system.

Clouds often present the illusion of limitless resources but in reality these resources are finite. The demand for resources in many public and private cloud implementations can often exceed the resources that are actually available. There are two scenarios where the demand for cloud resources can exceed the available capacity.

Cloud providers often employ a self service capability that allow customers to request resources on demand.


Scalability functions in the cloud, increase resource utilization based off of workload demand.


This article describes a prioritization method for allocating limited cloud resources based on the value that the application consuming those resources brings to the company. This value which is calculated as:
value ratio = total value / resources allocated

The value ratio can be measured in a number of ways such as revenue, profit, or PR. The system works in a dynamic feedback loop

where an application's initial priority is decided with some seed amount of value. This is just to guarantee some resources in the Cloud.

After some time when the application starts to bring in value, lets say in the form of revenue, the application can then be funded directly by the value benefit. The magnitude of the benefit will then play a role when resources are tight and certain applications must be chosen over others.

The general scheme accommodates different definitions of value for the company, e.g. revenue, profit, return on investment (ROI).

Take for example a scenario where two lines of business (A and B) which each have their Software as a service (SaaS) applications running on their enterprise's private cloud. Over time each application grows to the point of reaching a cloud resource limitation. Over the last month application A brought in $1500K in revenue using 30 servers and application B brought in $900K also using 30 servers.

Based off the calculated value ratio:

Application A's = 50

Application B's = 30

As the demand for cloud resources grow and the capacity of available resources don't, the system would prioritize and give the limited

resources to application A since those resources will bring more value per unit hosting application A.

The disclosed system:

Prioritizes resources across all applications based on the total value generated for the company.


Propagates a portion of resource priority to shared services that an app depends on.


The key for resource prioritization is the value of an app, and this can be a concrete value such as revenue from a sale, or a perceived value such as brand exposure in a PR campaign. The perceived value can be difficult to quantify and many factors need to be considered. While revenue can be measured in dollars, a PR campaign may be measured in perhaps the number of cons...