Submission Number: 13376
Submission ID: 63840
Submission UUID: 57bead8c-d2c6-41e2-99c5-2ba92a7132ec

Created: Thu, 01/19/2023 - 18:10
Completed: Thu, 01/19/2023 - 18:10
Changed: Thu, 02/09/2023 - 14:50

Remote IP address: (unknown)
Submitted by: admin
Language: English

Is draft: No
Current page: webform_submission_import

Locked: Yes
TRANSPORTATION DEPT
Oracle Primavera
3000033430
P1414 Primavera Feasibility, Planning & Preparatio
99852
Oracle Primavera consultants were contracted to conduct feasibility on identified MnDOT applications that are aging or technically isolated and deliver estimates to replace these applications with tools in the Primavera suite. One of these projects planned to move to implementation in this first Phase, PPMS Replacement (1322). The consultants were tasked with creating an approach to pilot and evaluate P6, a Primavera tool, as a candidate to replace PPMS and create an estimate for our steering committee and committee staff to evaluate for implementation. Deliveries also included an end-to-end Transportation project workflow that identified processes, resources and tools used in the lifecycle. Finally, the consultants were contracted to support the implementation of P6 for Construction Scheduling and Support (P1417) and evaluate replacement of tools like TRACS with Primavera’s Contract Manager.
Project Duration
Wed, 12/21/2011 - 00:00
Fri, 12/21/2012 - 00:00
Tue, 05/22/2012 - 00:00
No
{Empty}
Contract Amounts
$944385
{Empty}
$944385
Yes
Division Directors’ Fund (2700/32303) $250,000
Yes
Oracle gave an Insight Study presentation to key decision-makers in October of 2011. This group determined Oracle’s Primavera tools were the best fit for our Agency’s need. Oracle required use of their time and materials contract template for purposes of this work and the single source approach was chosen.
Holly Samshal
holly.samshal@state.mn.us
Poor
Average
Very High
Average
Yes
The product quality and work performance was below average. Project documentation and deliverables, provided by the consultants, lacked understanding of the project scope and business objectives. For example, the vendor provided an introductory training to the project team. The training was very poorly managed. The trainer was late or ended the sessions early without reason. More importantly, the trainer did not demonstrate an understanding of the vendor’s system that MnDOT was evaluating.

The on-time of the deliverables and project-related cooperation is rated as poor. The consultants did not deliver feasibility study project artifacts, nor did the consultants complete project deliverables on-time. Even though the consultants jointly developed a project schedule with MnDOT, the consultants did not deliver project work based on this schedule. In some cases, the consultants delivered the same artifact repeatedly even though it was rejected by the project team. In one instance, an approach presentation was given three times and each time the consultants were told to present a different approach only to come back again with the same slide deck.

QA/QC Plan Conformance is not applicable in this situation. The QA/QC plan was a deliverable on the project schedule that the vendor did not deliver to MnDOT and, therefore, could not be evaluated.

Oracle was really difficult to enter into contract with. It took quite some time to negotiate a contract initially. We ended up using their forms for the contract because they would not agree to use MnDOT’s standard forms.
2 - dissatisfied