Primavera P6 can be implemented as a single-project scheduling tool or a complete Enterprise Project Management application serving hundreds or thousands of projects and users. Pinnacle’s largest implementation supported 7,000 users on 4 continents.
For a project-scheduling focused implementation some of the questions you need to consider are:
- What type(s) of resource management are required? Do you need to use resource calendars or resource shifts?
- Projects share a resource pool so how will the resource pool be organized?
- Will templates be used for building project plans? Will Methodology Manager be used?
- How will baselines and change control be implemented?
- How will rolling wave schedules be implemented?
- Do you need consistency in the project WBS’s that are used?
- Is there any standard coding of projects, activities, or resources that is needed?
For implementations with a broader focus, the following questions will come into play:
- Primavera’s scheduling engine is very sophisticated. Are your users ready to deal with the potential complexity? What type of training and support aids are needed?
- Will the Primavera timesheet application be used to status activities? What will the approval workflow be?
- How are projects organized into the Enterprise Project Structure? You may want to consider organizing projects into portfolios.
- Will you represent all work in the organization in P6? i.e. non-project work as well as project work? If so, how will non-project work be represented in the project scheduling application?
- How do user-roles map to the functionality of P6?
- If Primavera Web is going to be used what dashboards are going to be displayed for each user-role?
Pinnacle’s implementation approach has been refined over many years on large and small engagements. Our approach emphasizes user-participation, is adaptable, and will guide you through the pros and cons of alternatives to each of the questions above. The goal of our implementation approach is successful adoption of the new system.
Deploying software applications usually involves the following phases:
- Requirements/Architecture – agree the basic requirements and technical approach. Includes role definitions, user-scenario development and technical architecture.
- Prototyping/Configuration – building prototypes to support decision making
- Development – build any custom migration, integration or reporting that is required
- End to End Testing – test the applications from end to end
- Deployment, Documentation and Training– iteratively deploy functionality to the users
Learn more about our Oracle Primavera services.
Talk to a Pinnacle professional regarding an Oracle solution today - Give Us a Call or