Implementation Services

There are typically two approaches to implementation:

  • Quick Start
  • More comprehensive configuration.

One of the key features of PMWeb is its high level of User-configuration. This allows an organization to undertake sufficient initial training to be able to use the system and then “take its time” to progressively configure the software to its exact requirements. This approach has the advantage of substantially reducing the initial cost of acquisition. We call this approach “Quick Start” for obvious reasons.

The advantages of a more comprehensive initial configuration are substantial in terms of user adoption/acceptance:

  • All the configured terminology will be consistent with the same terminology already used by the Client in the management of its processes
  • Drop-down menus will have the selection options already operating in the Client’s project management and administration
  • Existing Forms will have been incorporated, maintaining the familiarity of look and feel; but linked to a unified database
  • A Change Management strategy will have been fully developed in parallel with the configuration process.

More extensive configuration can delay the commencement of an organization-wide roll-out but can ultimately save time and underwrite user acceptance.

Our implementation methodologies incorporate years of hands-on experience with industry-accepted processes and procedures.

‘Quick Start’ can have the Client’s team up and running within two to three working weeks with a suite of modules custom-tailored to its key processes. 

Smaller implementations

We have a number of standard packages designed for use in smaller implementations of 5-25 users. Base packages start at $11,000 - read more.....

Standard Packages

More extensive Quick Start packages require at least 10 but preferably 15 man-days to implement. The standard Quick Start packages are delivered for a fixed price and involve the following stages:

Task Minimum Duration Recommended Duration
Installation and verification 1.0 day 1.0 day
Discovery/requirements clarification 2.0 days 3.0 days
Admin training on overall system 1.0 day 1.0 day
Set-up and initial configuration 2.0 days 3.0 days
Custom Reports developed and tested 1.5 days 3.0 days
User training 1.5 days 2.0 days
Post-implementation support 1.0 days 2.0 days
Total duration 10 days 15 days


One of our goals during implementation is to make our clients self-sufficient. The successful deployment of software in an organisation requires a client to have a few dedicated staff that learn the system in detail. In smaller organisations, this can come down to a single dedicated ‘PMWeb person’. It is also essential to have executive stakeholder involvement so the implementation goes smoothly and end user adoption is maximized.

More comprehensive implementation

A more comprehensive implementation is typically conducted more formally via a staged process. Our experience has shown that a successful implementation requires two key elements:

– We strongly believe in involving end users of the system immediately and often. By doing this they quickly begin to understand how the system works and provide intelligent feedback as to how it can be adjusted to better meet their needs. This requirement is met in a couple of ways:

  • The implementation team is largely made up of client staff and not consultants, because they understand their own needs better than anyone. This also ensures that once the implementation is complete and the consultants leave, the client will have a solid team in place to be able to mold and modify the system as their needs change.
  • Piloting - Super Users will begin using the system on one of their jobs as soon as possible to test and pilot the configuration and ensure that it will be appropriate for the eventual end users.

– We have found that it is extremely important for user adoption and satisfaction that the implementation team be able to receive feedback and quickly incorporate that feedback into the system. The best feedback cannot be given until a person is able to actually use an aspect of the system. We achieve this through an agile implementation approach. An implementation will typically flow as follows:

Configuration Sprints are a key element in this Agile approach. The key output for each Configuration Sprint is a fully functioning and configured feature or set of features in PMWeb. These features could be deployed to the user base, and should be used by the super users in their pilot projects. Where appropriate for the feature these configurations would include:

  • Report Modifications or creating new BI/PMWeb reports
  • Nomenclature and list changes
  • Workflow defined and configured
  • Process and/or training documentation created
  • Configurations tested by Super Users and PMWeb Owner

The chart below describes the make up the implementation team that has yielded the best results in the most effective and successful implementation projects. It is evident in the table below that the client has a large part of the execution and should fill several of the key roles.

Experience with multiple products                                                              Integration experience                                                                              
PMWeb
Oracle Contract Manager / Expedition
Oracle/Skire Unifier
Oracle Primavera P6
Trimble
Prolog
eBuilder
eDocs
EADoc
SharePoint



  SAP
  Oracle
  Timberline
  ViewPoint
  DB2
  Ellipse
  eCMS
  Epicor
  AS400
  SharePoint
  Objective
  Oracle Primavera P6
  Microsoft Project