Our Oracle Primavera Implementation Methodology

We refer to our implementation approach as a "structured" approach. We carefully evaluate the client's implementation project needs and assemble a customised team of talented professionals, including a project/engagement manager, installation and integration specialists, project management and implementation consultants, data conversion experts and certified trainers. When appropriate, we also draw from a pool of Specialized Solution Providers with the proper mix of skills, knowledge and abilities.

Step 1: Readiness Assessment

The primary purpose of the Readiness Assessment step is to form an understanding of the client project management environment, processes, and business by assessing the client State-of-Readiness". In assessing the state of readiness the primary objectives are as follows:

  • Confirm client Top Management's Support (Support = Endorsement & Action & Follow-through
  • Set Expectations for the users and management
  • Focus on Business Need of stakeholders
  • Focus on Goals and Objectives
  • Discovery of Organizational & Cultural Factors
  • Initiate Preparation (Infrastructure / Staff)
  • Document Risks & Assumptions
  • Plan the Implementation (Scope/Schedule/Resources)

Step 2: Design

The purpose of this step is to create a Design Document or Role-Based user guide that completely details the software configuration, to include portfolio configuration, data structures, reports and procedures that must exist to support and operate the Oracle Primavera Software in a production environment.

In the Design step, we design the strategy to implement the recommended Oracle Primavera solution. Step 2 uses the following elements to create a customized implementation plan:

  • Definition of project management, project office, supporting data structures, departmental and resource management processes and roles to be modelled for the pilot
  • Identification of views and reports of project data to support each position within your company
  • Setup of test environment
  • Documentation of detail for how the system is installed, set up, structured and carried out to meet the needs outlined in step 1
  • Creation of a working model test plan consisting of test scenarios, hardware/software requirements, training requirements and a test schedule
  • Training curriculum and schedule for Oracle Primavera reporting solution proposed

To help you manage work most effectively, Oracle Primavera defines information needs and creates intelligent reporting packages. Working with your staff at every level, we design reports and checklists that clearly state the type and detail of every project throughout your organization.

Step 3: Prototype and Test

The Prototype and Test step is to be used as a demonstration of the configured system and the processes developed and recommended in the Design Document. The Prototype will be built with the client's sample project information. With familiar project information, the client is better able to concentrate on the features and functions of the system rather than the data.

  • Create the working model
  • Prepare testers
  • Conduct the test and document results
  • Develop custom training

By testing and debugging your project management environment with step 3, we identify and resolve any issues in structure and information flow. We also develop coding schemes for activities, resources, project structures and build code dictionaries to ensure consistency of data throughout your environment.

Step 4: Production Validation

During the production validation step, a small sample of users will begin using the system. The system will be configured with familiar data and terminology. Changes to the processes or data structures will be implemented and documented before completing the production validation.

A pivotal point in the implementation of any Oracle Primavera solution, the production validation test helps us determine a detailed plan for a successful rollout.

We will prepare and conduct a production validation operation that enables a targeted group of users to work with the software. We can train -- either on or off-site -- using your real projects and answer questions or solve problems as they arise. Using your real-world project data ensures that the software has been configured accurately and is performing to your standards.

Following your Production Validation Test, you will be provided with a customized procedure manual for using the software in your organization. Use this manual as support for existing procedures and policies

Step 5: Rollout

Rolling-out a complex project management solution will impact large numbers (and maybe all) of the employees in the organization. The impact may be minor for some, but for many it will involve a whole new way of doing their job. Planning the rollout by identifying the who, what, when, where, and how of the process and producing a detailed plan to manage it will contribute to its success. Rollout involves a series of steps that begin long before the day marking the start of the software use. Having the pilot experience to draw on and any lessons learned from problems or successes improves the chances of accomplishing a smooth transition. Rollout must follow the plan as created by the implementation team. Rollout will include the production server installation and configuration, user workstation configuration, project data input and/or migration, marketing of the new system, and training/mentoring of users.

The implementation consultant will fill the role of coach for the rollout and eventually transfer the coaching to the client's staff. The coach will have a constant presence with the users, solving problems and addressing concerns immediately to complete a successful implementation. The client may want to establish a project management office or help desk that would absorb a large percentage of the help requests.

Step 6: Assessment

At the end of or at a predetermined point during the rollout an evaluation is conducted to identify the successfulness of the implementation. The implementation team will review the critical success factors and scope of the implementation to ensure that all the required work has been accomplished. The implementation team, in coordination with the engagement manager, will prepare an Implementation Final Assessment report that will include the following:

  • Comparison of the original implementation scope and engagement objectives to the final implementation schedule and successes
  • Problems, those solved, those existing, and those anticipated should be identified and communicated to the implementation team, including technical problems or needs that have been identified
  • A copy of the original baseline schedule and the completed implementation schedule
  • Improvements that can be made to the current system
  • Discussion of new directions and capabilities of the system (the client may be interested in enhancements or new products)
  • If a phased approach is taken to adopt the Oracle Primavera solution, next steps can be identified and planned.
  • Lesson learned