Best Practices for Oracle Primavera Upgrades/Migrations Don McNatty, PSP Certified P6 Trainer/Consultant Business Process Outsourcing
Thank you for joining today s technical webinar Mute all call in phones are automatically muted in order to preserve the quality of the audio for all attendees. Questions during the session, questions can be submitted through the Questions Box on the right side of the screen. We will try to address your questions at the end of the presentation, time permitting. Follow up all registrants will receive an Excel file listing all questions and responses along with a link to the recorded webinar. 2
Twenty-five + years experience with Primavera Oracle Primavera Software Oracle Certified Training Oracle Certified Implementation Support Project Support Services administrators, schedulers Managed Hosting Services through MLM Project Services Primavera Portfolios, P6 (web), P6 Pro, Contract Management, BI Publisher, Documents, Risk Hard Dollar, Acumen Fuse, Ecosys, Prism G2 Subscription (SaaS) based Oracle Primavera solutions Business Process Outsourcing dmcnatty@drmcnatty.com Tel. 877.367.7990 3
Agenda Why Upgrade or Migrate? Important Features of New Releases Should You Upgrade or Migrate? Important Considerations Before You Start Licensing Requirements Develop Your Plan Execute Your Plan Where to get Help? Questions 4
Why Upgrade or Migrate? Newer versions of P6/Contract Management may have desired functionality Web Services (can reduce license cost/improve access) BI Publisher Reports replace Infomaker P6 6.x support ends November 2013 Current versions may have a limited life-cycle P3 support has ended CM 13.x support ends June, 2013. 12 ended November 2011 A new project may require using a new version Some owners now require contractors to provide their own licenses for access to the owner/cm s project database You can migrate your licenses to latest version but may still be able to use your present version internally. You need to support 64 bit 5
Important Features in New Releases P6 (Pro) Time Scaled Logic Diagrams Line Numbering Import/Export capabilities P6 EPPM (web) Risk Register Enhanced Resource Management Schedule Checker Contract Management BI Publisher instead of Infomaker Content Repository & Versioning Approval Workflows 6
Should you Upgrade, Migrate or Buy? Depends on where you are (version) If you have P6 version 6 or earlier Migrate If you have Concurrent licenses Migrate (2 for 1) If you have P3 Buy new (no migration/upgrade options) If your support expired more than a couple years ago? Buy? PCM 10, 11, 12, 13 you can Upgrade to 13.1 PCM 10, 11, 12, 13.x you have to Migrate to 14 If you have current maintenance & license Upgrade to 14 SureTrak or Contractor no options, Buy New P6 Pro ver 7 Upgrade to P6 Pro 8.2 P6 Pro ver 7 Migrate to P6 EPPM 8.2 P6 Pro 8.2 no Migration to P6 EPPM 8.2 (Buy EPPM) 7
Upgrade Process Maintenance Up to date? Go to edelivery.oracle.com No Yes Pay Maintenance up to date Download current version Install & use Upgrades are simple just download the software. Trial software is the same as full software. CD s available with new orders only. Maintenance is direct with Oracle, not Oracle Partners. 8
Migration Process Contact Oracle Partner Provide necessary information to Partner Partner submits to Oracle Manager Oracle Manager researches & resolves issues +/- 2 weeks Oracle Manager submits to Migration Dept. Migration Dept. provides price & expiration date Partner provides complete pricing Customer Issues PO Partner Invoices Oracle issues OLSA to customer Go to edelivery.oracle.com Download current version Install & use 9
Information Needed for Migrations Company name. Contact name(s), email and telephone information. Physical address including country. Serial or CSI Numbers. A clear understanding of what you currently have. A clear description of what you expect. Also.. A clear understanding of your own procurement process because the price has an expiration date. An expectation that you will be paying first year maintenance with the order. 10
Important Considerations Before You Start P6 Pro Do you want to run stand-alone, centralized or both? Have you been importing a lot of P3 files? P6 EPPM Do you have the capability to self deploy. Is hosting an option? Are you comfortable with centralized administration on the web? Do you understand the difference between the web & client? Be prepared to resolve data migration issues PCM Do you think that BI Publisher will be easier than Infomaker? Do you want versioning? It requires UCM or Sharepoint Be prepared to resolve data migration issues 11
Available Resources before you migrate Best Practices Whitepaper for P6 8.2 Migrations My Support link for P6 Migrations: Note 338.1 My Support link for CM 14 Migrations: Note 341.1 DRMcNatty Support Consultants Dan Beck, dbeck@drmcnatty.com, +1(716) 597-4094 12
Licensing Requirements P6 EPPM, P6 Pro, Contract Management, Analytics and Risk are all licensed by Application User Similar to a named user. Has to be an individual, not a group. An Application User can use a single license on multiple servers. Example, a P6 Pro user can connect to a server database to run in a multi-user environment and disconnect and run in one or more local databases. Primavera has not supported concurrent licenses since 2008. If you have an older, concurrent license, you can only upgrade to a certain point (P6 v7, CM13.1) If you migrate a concurrent license you can receive up to 2 named for each 1 concurrent. 13
Develop Your Plan Take the time to understand licensing requirements. Upgrades are usually no cost, migrations usually have a cost to them, mostly related to maintenance. Understand the infrastructure requirements P6 Pro is still relatively simple but many people still have a problem deploying it stand alone. P6 EPPM and CM14 are very complex. They both require a serious, well planned and maintained infrastructure. Installation is 1/3 the effort. Continuous operation is 2/3. If you do not have an Oracle Primavera (just Oracle is not enough) Subject Matter Expert (SME), (or two), on staff self deployment will be expensive and painful Hosting deployments can and should be quick (2 weeks max), painless, and cost efficient (if you know your real costs). 14
Develop Your Plan Migrations are projects, plan your project Hardware requirements and deployment SME and Oracle technical support A dependable environment for web deployments Get the new system deployed before starting a migration Start with a test migration of databases and thoroughly review Create, test and deploy critical forms and reports Start with a small pilot to do final testing and form/report setup Finalize all procedures and documentation Do not start a rollout until all elements have been tested Understand that that the new system will be different, will require some processes to change, and there may be some ongoing issues while the new version is being supported Do a phased rollout to all users 15
Execute Your Plan Get professional, experienced help up front. Try and take the infrastructure (hardware) out of the critical path so you can focus on the tool deployment. Have a backup plan if some feature doesn t work exactly as you thought it would. Do not move off your existing system until the new system has been proofed. Never attempt a big bang migration unless that s what you want (a big bang!). The real test of a good deployment is if it keeps working, day in and day out with low levels of user frustration. 16
Where to Get help My Oracle Support https://support.oracle.com/ Questions on pricing and deployment Charlie Sanchez, +1 949 297 4057 Questions on Training and Implementation Support Dan Beck, +1 716 597 4094 Questions on this presentation Don McNatty, dmcnatty@drmcnatty.com 17
Upcoming Events AACE International s 56 th Annual Meeting July 8-11 in San Antonio Booth 205 & 207 18
Questions? Don McNatty Principal Consultant T. (877) 367-7990 x4053 E. dmcnatty@drmcnatty.com W. www.drmcnatty.com 19 32