Review and Q&A

Sheila Volante

Project Server 2007

Summary Bullet Points

Efforts on 11/14/08-11/15/08 Corrections and Security Setting Changes Overview of Workshops Refresh of System Status Usage of Project Web Access Help

Efforts on 11/14/08-11/15/08

Proposed Decision1. Recreate Master Templates 2. Remove unwanted Custom Fields3. Remove any unwanted Cube Settings4. Remove any Event Handling5. Create Separate Groups with Group Resources6. Remove unwanted Project Files7. Import All Project Files to Local Location8. Export Information to Excel 2003 or CSV File9. Remove All Projects From Local Cache and Drafts Files10. Re-Import Project Information to New Project Files11. Reassign Users to Access Project Files12. Re-Train all Manageable Users for Project Files

Efforts on 11/14/08-11/15/08

1. Copied All Projects in the (:S) shared drive under MS Projects2. All projects were in their own files3. Evaluate Project Status4. Evaluated Project Server Settings, Columns and Error Reporting5. Made Changes to the Security Settings for Users6. Created How to Guide Templates on Regaining Non-Issue Related Problems with Project Professional 2007

Queue Error Reporting

0

5

10

15

20

25

30

35

40

ProjectCheck In

ProjectPublish

Project SaveFrom Project

Pro

Reporting ResourceSync

StatusUpdate

WSSWorkspaceCreation

Series1

Reporting week of 11//3/08-11/7/08 Resource: PWA Queue Status Report

Queue Error Reporting

0

5

10

15

20

25

30

ProjectCheck In

ProjectPublish

ProjectSave FromProject Pro

Reporting ResourceSync

StatusUpdate

WSSWorkspace

Creation

Series1

Reporting week of 11/17/08-11/21/08 Resource: PWA Queue Status Report

Preventive Practices Double check if a file is checked out Make sure all changes are final before publishing Patiently wait until status bar is completed. Double clicking publishing will cause problems

FYI

Please enter in the proper information in the required fields when saving the project. This is very important for reporting and structure of projects

Brief Description Master Schedule ( If Applicable) NSA Requirement Owning Group Owning Manager PLC Type Project Status Release

Change in Security Settings

There will be approx. 15 people using client Program Managers will only access Master files There will be assigned Project Managers instead of

Resource Managers Project Managers will have the access to the OLAP

Reporting Manage Queue will be a access to all project and program

managers Timesheet managers will be project managers or Resource

Managers

Solution Workshops

E-mailed workshops Two days per week workshops On-line workshops* (TBD)

Workshop Review

Why Delay of Original Workshops

Major deadlines due Vacation scheduled for employees Conflict of time adjustment for schedule

Usage of Project Web Access Help

Tracks current help wants Informative for other help questions for other users Ticket Numbers will be distributed for tracking purposes Documentation Purposes

Master File

“ Many hands in the cookie Jar! Who ate all the cookies!”

Master Files should only be used for read only. The master files are typically used for viewing of other progress. If there are updates that will need to be made in one of the subproject, please simply close out of the master project and make the changes in the subproject.

If there is a change in the master file, please change ONLY information in the master file. The master file is assigned to the Program Managers at this point.

Thank You