Handbooks of those "old powerfull PMS" available?

>Not so many years ago, there existed numerous
>software tools that were vastly more powerful
>than even the most capable contemporary tools
>today. Those tools ran on the mainframe and they
>did an incredibly good job of baselining and
>tracking the time, resources, and cost dimensions
>of large projects of great complexity - and of
>multiple small projects. The names of those tools
>were MSCS/COPES (Management Scheduling and
>Control System by McDonnell Douglas), Project/2
>by Project Software Development Inc., CIPREC by
>IBM, PREMIS/PICOM by ???, PMS-4 by IBM was
>probably the first of the truly powerful systems.

If you look at the Handbooks, you could tell us
what specific feature you did like most (from the perspective of
a power plant constructor or a public contractor)

Then we could find out what would be the feature
set what would be needed to support that certain feature.

That could lead to a description what would say:

"For a power plant builder the following feature set would
be needed for first-level-of-usefullness. A, B, C, D".

First-level-of-usefullness would mean: "a powerplant builder could use
mrProject productive, even when a lot of additional features
are missed and other payware application offer more, but at least
for a powerplant builder it is attractive because it is free and
it is easier to learn because it is not so feature-overloaded (for other
user types)".

Second-level-of-usefullness would mean:
"the amount of minimum features also implemented in other applikation
plus this certain feature minus some minor features not implemented
would make it a killer applikation for powerplant builder"

It would be a good aproach to select a user type with a small needed
featureset and implement first-level-of-usefullness.

I offer to work on this minimum-feature-list with real-experienced-users.

Edmund Humenberger