Browse Prior Art Database

Distributed Tasks Scheduling

IP.com Disclosure Number: IPCOM000114979D
Original Publication Date: 1995-Feb-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 4 page(s) / 160K

Publishing Venue

IBM

Related People

Speiser, A: AUTHOR [+2]

Abstract

Disclosed is a method enabling Project Management (PM) systems to automatically treat external dependencies from/to activities which are not under the control of the Local Scheduler. Benefits are that multiple local PM systems define inter dependencies and a messaging API that enables automatic local scheduling to synchronize with the global network in a process independent of the actual PM package used by the organization.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 40% of the total text.

Distributed Tasks Scheduling

      Disclosed is a method enabling Project Management (PM) systems
to automatically treat external dependencies from/to activities which
are not under the control of the Local Scheduler.  Benefits are that
multiple local PM systems define inter dependencies and a messaging
API that enables automatic local scheduling to synchronize with the
global network in a process independent of the actual PM package used
by the organization.

      Project Management systems have become acceptable as management
tools for scheduling activities.  Current existing tools provide
Schedulers that will schedule the identified activities under the
resource constraints as defined in the system.  But, in a large
organization, there are usually multiple systems that handle the
scheduling for the local (department/group) activities which do not
recognize one another.  When activities are scheduled in one system
which are dependent on activities that are scheduled in another, then
those relations can not be defined and so are unscheduled or ignored.
Distributed scheduling defines a method of recognizing external
dependencies between systems.  Each system has its own local
scheduler.  A messaging API is defined to enable the system to
synchronize the local schedules with their external dependencies.
The concept of Scheduling Distributed Projects has been approached
before by systems like: AS-PME, APM & RMFE using different approaches
and do not cover the Distributed Scheduling that is offered here.
Current Project Management systems have a common approach to
scheduling multiple projects under resources constraints.  In essence
these systems provide one PM system for the organization and the
company defines a hierarchy of super projects that are then
segregated into subprojects, sub-subprojects etc. to the level
required.  As a result, to get the global picture of the company, the
company super project which is the aggregation of all subprojects has
to be analyzed.

      Distributed scheduling is a different approach where each
department/location can own its PM system unit which will then "talk"
with the other LAN (or other networks) connected PM units.  Each unit
will schedule its local Projects and allow external links to other PM
units defined.  During the schedule there is check on External
Predecessors links and the scheduler will take account of the
external constraints they create on the local projects.  After the
local schedule is done, there is a check on all External Successors
links and message the responsible PM unit to refresh its schedule if
necessary.   This could be done automatically or under control.  The
benefits are: smaller Projects are scheduled with faster response,
multiple location handling becomes simpler and better control on
Scheduling because of the smaller number of activities and resources
constraints.  Also it provides an implementation solution to multiple
environments.  PM un...