Jack's point is not bad!
But also I found there're 2 articles Microsoft announce
they will integrate Accounting system & HR with Project
2002.
By the classification of ERP software which APICS books
ever mentioned, a "project Manufacturer" industry which
earn big money from project management like Boeing, A/E/C
industry, US DoD,etc. Such industries are Project-oriented
industry.
We need more integrated feature in a project software. Not
only can offer limited features for some common purposes.
We have to consider it with MS's strategic view point, not
only from a company or an industry. News from C|Net, MS
want to raise the importance of MS Project in their office
products and MS office will be the front end AP of ERP
system.
You can search 'accounting "project 2002" msdn' in Google
[PPT]Project 2002
Microsoft Powerpoint 97 - HTML
... Interactive project guides assist users to utilize
Project 2002. ... Challenge: Combined views and data
integration
for all project information, including accounting, HR
information, MRP systems, and other project data
(emails, contacts, docs, etc.). ... Usual suspects.
http://msdn.microsoft.com/project. ...
http://www.microsoft.com/usa/presentations/PacWest-
MTAF.ppt -
[PPT]Introduction to Project 2002
: Microsoft Powerpoint 97 - HTML
... MPUG. MSDN. Partner Activity. ... Office XP full
installation with Web Components. Project 2002 Web Access:
Internet Explorer 5.5 and above. ... Functions
traditionally distant from project management can be
influenced
and involved. Accounting can have visibility. Financial
planning can source their own info. ...
http://www.microsoft.com/uk/technet/learning/
downloads/evenings/Project_2002.ppt -
[
www.microsoft.com ]
-----Original Message-----
Lawrence,
Note that the second paper was written in early 2002 before Proj2002 was in
widespread use. The other paper also mentions that Proj2002 is under
evaluation.
Having been involved in similar tool evaluations I find that the approach
they use is not sufficient to make a proper tool choice.
It is more of a feature comparison rather than an evaluation.
To be honest, some features are not worth having if they are not implemented
well so this sort of feature comparison results in inconclusive or even
incorrect conclusions.
To me the real "features" of a scheduling tool are how well it fits my
specific needs, not all needs, just the ones I really need.
Project has many faults, but fortunately it has a pretty comprehensive API
so I can usually get it to do what I want and can get information in and out
of it easily. That enables me to do what I need to do.
I think that in many cases tight integration with financial systems etc. is
detrimental to optimal use of a schedule. The need to satisfy financial
requirements can lead to creation of a schedule model which is overly
complex or just wrong. The objective of most of the schedules I am familiar
with is to help complete the project as quickly as possible. I do not see
how integrating with a financial system helps in this regard.
Finally, though NASA put a man on the moon, it may not be the type of
organization that your company should try and model itself upon. Different
types of organizations have different types of management and different
scheduling needs.
-Jack
--
Please try to keep replies in this group. I do check e- mail, but only
infrequently. For Macros and other things check
http://masamiki.com/project
-Jack Dahlgren, Project MVP
+++++++++++++++++++
.