[kplato] explenation from project managers please?

[Pedro Restrepo]

Hi,

I have sent this message yesterday, but it appears that the message did not arrive.

These terms are related with the CPM (critical path method) or logical network programming
technics. The logical network represents a project divided into discret works (activities)
linked by precedence (order of execution) relations.

I propose these explanations:

ASAP: (As soon as possible) To program activities (or tasks) for the ealier possible date.
ALAP: (As late as possible) To program activities for the later date that do not causes delay on other activities.

A network can be calculated in two ways: from the beginning of the net to the end
(progressive) or from the end to the beginning (regressive). The regressive calculation
needs an ending date previously defined. The progressive calculation will yield the ASAP
dates, the ALAP dates are calculated using the regressive calculation.

When an activity is conditioned by facts external to the network (other projects, climate,
government restrictions, etc), these facts must be represented using "constraints". The last
terms you are asking for, are constraints. The meanings are:

Start not earlier than: The activity can not begin on a date earlier than the fixed date.
Finish not later than: The activity can not finish later than the fixed date.
Must start on: The beginnig date for the activity is fixed.


Thomas Zander wrote:

> Hi,
>
> I got 2 replies that both told me a lot, thanx to you both!
>
> I am left with a feeling that not all is correct; Martin told me very
> well how a schedule will react if the scheduling type is set to either
> ASAP or ALAP.
> Chris talked about the influence of the starting options.
>
> The next question I have is if I should not select one of the ASAP/ALAP
> _and_ select on of the starting types. Since you currently have to select
> 1 of those 5.
>
> so two groups of radiobuttons:
>
> Project scheduling: (won't effect start/end time)
>     o ASAP
>     o ALAP
> Project start/end
>     o Start not earier then
>     o Finish not later then
>     o Must start on
>
> Right?
>
> On Sun, Feb 23, 2003 at 10:18:27PM -0500, Chris H wrote:
> > On February 23, 2003 03:06 pm, Thomas Zander wrote:
> > > Hi!
> > >
> > > I updates some stuff in kplato and we have a more user-friendly project
> > > management dialog.
> > >
> > > I want some 'texts' from the people that know most about project plannings
> > > to finish stuff.  Its in CVS, just start it up and you will see why I ask.
> > >
> > > - what is the influence of scheduling type on a project. (small 7 word
> > > sentence please). - please give me a 3 sentence explenation for each of the
> > > following scheduling types:
> >
> > IMHO only
> >
> > - ASAP  (as soon as possible)
> > - ALAP (as late as possible)
> > - Start not earier then ( project element cannot start until a specified date:
> > typically dependent on completion of another task)
> > -Finish not later then (time dependent completion date: ie: schedule
> > dependant)
> > - Must start on (time dependant start date -schedule dependant)
>
> On Mon, Feb 24, 2003 at 09:58:16PM +0100, Martin Fox wrote:
> > Hi Thomas
> ...
> > If every activity starts as early as possible the finish date is calculated using the so called "earliest start method" otherwise if as late as possible the "latest finish method".
> >
> > Clearly all the predecessors of an activity will have to finish as early as possible if the activity concerned is to be started on an "early start" basis. There is thus a range of dates for the start/finish of an activity, depending on what has happened in the past.
>
> --
> Thomas Zander
> _______________________________________________
> kplato mailing list
> kplato@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kplato