Browse Prior Art Database

System and method for ad-hoc resource reservation loan process within an automation environment

IP.com Disclosure Number: IPCOM000180403D
Original Publication Date: 2009-Mar-09
Included in the Prior Art Database: 2009-Mar-09
Document File: 2 page(s) / 44K

Publishing Venue

IBM

Abstract

Disclosed is a process for providing ad-hoc resource reservation within an automation environment. The process enables maximum resource utilization by using specific attributes of automation jobs and available resources to provide ad-hoc loans required for the automation execution.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 81% of the total text.

Page 1 of 2

System and method for ad-hoc resource reservation loan process within an automation environment

The disclosed process allows a user to request a "reservation loan" from the owner of a resource already reserved or privately maintained. This temporary loan will enable the user to perform a given task on a resource, after which the reservation will immediately be returned to the original owner. This system maintains the traditional resource reservation processes and concepts, but integrates a simple process that increases resource availability and utilization.

The ad-hoc reservation process begins when an automation system user selects a task for execution, but requires a resource that is not currently available.

User is presented with a list of eligible target machines, including those that have

1.

been reserved but are currently available (no current task execution), and those that are owned privately.

If user selects a machine that is reserved or privately owned, the task execution

2.

goes into a pending state while a notification is sent to the owner or current reservation holder.

The owner or current reservation holder receives the notification for the "reservation

3.

loan" request. The owner can view the requestor and task they would like to execute.

If the owner can spare the target machine for the given task, they can approve the

4.

reques...