1 / 21

Project Management in the Solomon Environment

Project Management in the Solomon Environment. Project Manager orientation. AIM.

naif
Download Presentation

Project Management in the Solomon Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Management in the Solomon Environment Project Manager orientation

  2. AIM • To provide training/orientation for Project and Line managers relevant to the implementation of the MS Dynamics -SL system with particular reference to the production and use of project schedules and the role of project managers.

  3. Agenda • Introduction • The system • Use of M/S project • M/S project set up checks • Good scheduling practice • WBS chart Pro • Allocation of resources • Rates • Synchronising and up loading projects to Solomon • Reporting on effort and progress • Time card system • Reports • Organise out of session training as required

  4. Introduction – (Why is this training necessary?) • The MS Dynamics- SL system creates a “loose” integration of our financial and project management systems. • Maximum benefit requires schedules to be set up in a certain way • Synchronisation processes need to be understood • Data capture process needs to be understood

  5. The System • System components are: • M/S project • Project Server • M/S Dynamics -  SL • SQL Data bases

  6. System Diagram • High level diagram

  7. Use of Microsoft project • Microsoft project is the AAO wide scheduling tool. • This training will not cover how to use M/S project and arrangements should be made if any key project or line staff feel they need to develop skills and competency in this area

  8. MS project standard

  9. M/S project set up • We have set up our scheduling tool to work off a particular template and all schedules that we create for integration into Solomon must use the AAO template version. • We should always check to see that the default schedule is working on the correct setups

  10. Good Scheduling practice • Consider the aim of the schedule and the relationship of the schedule with the WBS • Ensure that the hierarchy set within the schedule enables appropriate management • Protect milestones with buffers • Use contingency properly • Ensure budgets set reflect the reality of the scheduled work • See notes on page 10

  11. WBS chart Pro • WBS Chart Pro is a Windows-based project management software application that is used to create and display projects using a Work Breakdown Structure (WBS) chart. • WBS Chart Pro is integrated in our M/S project software

  12. WBS chart Pro standard

  13. How to allocate resources • Resources are allocated to a schedule within M/S project and this must be done using the Enterprise Resource Pool. • The issue here is to ensure that the resource pool within M/S project remains consistent with the resource details recorded and maintained in Solomon. • We will use M/S project schedules for human resources and put non human resource costs directly into Solomon (i.e. travel, materials, sub contractors etc)

  14. Rates • Rates are set by the Executive Officer and input to the Solomon system by the Accountant. These rates are then available for transfer to our project schedules to enable our planning and to support estimating and budget setting. • Rates will be part of the resource pool content and it is important to ensure that the latest rates are being used. • A nominated PM will maintain our off line resource pool.

  15. How to - synchronize & upload project details into Solomon • See notes provided – these are also on ‘p’ drive at: P:\projects\Microsoft Dynamics_SL implementation\MSPtoSolomon_import procedures • Importing Offline Projects into Project Server p 11 • Importing Server Projects into Solomon p 23 • Importing Server Project budgets into Solomon p 34

  16. High Level Process – (human resources)

  17. Non Human Resources • Process is shown in notes at p 41 through 44. • The examples show how non human resources are posted to Solomon • Implications - budgets

  18. Reporting on effort and progress • All staff at the AAO are required to fill in time sheets (actually called time cards in the Solomon system) on a weekly basis unless otherwise requested. • The time card procedure is on our web at: http://www2.aao.gov.au/twiki/bin/view/BusinessPractices/WebTimesheet

  19. Time card system

  20. Reports • Our Microsoft Business Partner (Renown) has made examples of standard reports available to us, see: P:\projects\Microsoft Dynamics_SL implementation\Reports. • Our recommended approach is to look over the “standard reports” and use these initially until we are familiar and then move to an agreed suite of customised reports. • We are currently developing a WBS roll up report for work packages etc.

  21. Out of session training • MS project 2003 • Project Server • Time card procedures • Requisitions / Purchasing • Other (i.e. Travel, AGCC, Flexitime)

More Related