Microsoft Project 2002 Enterprise Project Management
Anonymous
Has anyone had experience with the package?
The white paper describes it as consisting of: "Microsoft Project Professional, Microsoft Project Web Access, and Microsoft Project Server. Together they provide an integrated enterprise project management solution that combines ease of use, a centralized project and resource database, and powerful reporting and analysis features. "
We are thinking of Proof of Concept and welcome any hints.
We have been using eLabor's Enterprise Project over the last year. (See related discussion re: ASP Contract Language Discussion.) Microsoft purchased Enterprise Project and it is my understanding that Enterprise Project was to be used by MS for the expanded features of MS Project 2002.
Enterprise Project works with MS Project but stores all the data into central database, allowing for centralized control of the Project Registry, shared resources and project related codes (account codes, classifications, designations.) Project Managers still use MS Project to build and update their project plans.
Enterprise Project allows for management of your resource pool across all projects or subset of projects. We have also been using the Web timesheets to collect time charged (actuals) to each project (have not gone down to the task level.) We have used Crystal Reports for extracting project data for custom reports.
Bottom line is that Enterprise Project has worked very well for us for managing our Project Portfolio. Sure there are improvements I would recommend, but it is a major step up for MS Project Community into the world of enterprise management of projects.
From the Beta users of MS Project 2002, I am being told that Microsoft has incorporated a lot of the look and feel of Enterprise Project, but moved it from a central application to web based application.
I saw PM 2002 demo'd at Project World in San Jose but have not had a chance to "kick the tires". I am looking forward to hearing from the early MS Project 2002 Implementers.
We tried this product for about 8 months and finally dropped it because of data integrity issues. In short, time entered via timesheets was not stable. The data changed depending upon where we were in the timesheet submission and approval cycle. It was not easy to spot the bug. We first noticed it by accident and then applied a thorough testing methodology to duplicate the results. At first ELabor refused to believe that it was happening. We had to get them to run our test procedures. This was in the spring of 2001 so it may be fixed by now. Saving Changes...
