oracle primavera p6 r8.2 and cm14 on exa platform using oracle fusion middleware and oracle business...
TRANSCRIPT
REMINDER
Check in on the
COLLABORATE mobile app
Primavera Integrated on EXA – P6 R8.2, CM14, OFM & BI Publisher
Prepared by:
Verghese Kochummen
Principal Solutions Architect
Insynchro USA
Challenges, Benefits and Lessons Learned of Deploying an Integrated Primavera Solution
Session ID#: 15447
Product & Service Profile
■ NAME: Insynchro USA
■ CORE: Project Management
Products and Services
■ Primavera Service Portfolio
▪ Consulting, Functional &
Technical Support
▪ Remote Installation
▪ Development of Project
Workflows (BPM)
▪ Configure Project Libraries
(UCM)
▪ Development of Project
Reporting (BI Publisher)
■ inSynchro Integration Manager
▪ ERP Systems: Primavera P6
and CM to ERP [SAP, E-
Business Suite, PeopleSoft,
Ellipse, Computron, …etc]
▪ Asset Management System:
Primavera P6 to Maximo
■ Partial List of Clients
▪ Australia: Yarra Valley Water,
Talisman, RailCorp, Blue Scope
Steel,
▪ Malaysia: Shell, Petronas,
Talisman, Telekom Malaysia
Profile: Yarra Valley Water
■ Water Utility Company
■ Operating in Melbourne, Australia
■ Major award winners for Operational Efficiencies and Customer Support Services
■ Known for IT Investments that increase productivity and efficiencies
■ Primavera @ YVW
▪ User of Primavera P6 and CM since 2008
▪ Integrated P6, CM with their ERP Application (Computron)
▪ Integration facilitated by Insynchro Integration Manager
middleware
▪ Facilitated heavy corporate governance requirements
Profile: Yarra Valley Water (Cont’d)
■ Applications Procured
▪ Primavera P6.0
▪ Primavera Contract Manager
11
▪ Insynchro Integration
Manager
▪ Primavera Timesheets
▪ iManage project workflows
(bundled with P6.0)
▪ Sybase Infomaker (bundled
with Contract Manager 11)
■ Upgrade Resistance Factors
▪ iManage upgrade not
available
▪ Infomaker application is
phased out by Oracle (post-
acquisition)
▪ Cessation of support for P6.0
▪ Cost of Process and Report
Redevelopment
■ Risk of Not Upgrading
▪ Costly Support
▪ High Risk of Low SLA
▪ Threatens Quality of Service
Alignment with IT Architecture & Strategy
■ Unified Technology Platform
■ Single Enabling Technology per Functional Area
■ “In-Sourced” Skills for each Enabling Technology
■ Push Legacy or Application not in-line with IT Strategy to End-Of-Life
■ Mandate to Procurement
▪ New Applications “pressured” to use Enabling Technologies
▪ New Applications must not use in-built functional enabling
technologies
Unified Technology Platform
■ Strategic Investment on Oracle Technologies
▪ Server Hardware: Exalogic / Exadata
▪ Security: Oracle Identity Management / Oracle Access
Manager
▪ Database: Oracle DB
▪ Application Server: Oracle Weblogic Server
▪ Middleware: Oracle Fusion Middleware
— Service Oriented Architecture
— Business Process Management
— Webcenter Content
— Webcenter Portal
▪ Business Intelligence: Oracle Business Intelligence
Enterprise Edition
Single Enabling Technology Per Functional Area
■ Servers
▪ Oracle Exadata / Exalogic
■ Security
▪ Oracle Identity Management /
Oracle Access Manager
■ Database
▪ Oracle DB
■ Application Server
▪ Oracle Weblogic Server
■ Document Management
▪ Oracle Webcenter Content
■ Service Oriented Architecture
▪ Oracle SOA
■ Business Process
Management
▪ Oracle Business Process
Management
■ Business Intelligence &
Reporting
▪ Oracle Business Intelligence
Ent. Ed.
■ Learning Management
System
▪ Oracle User Productivity Kit
IT Strategies: Applications
■ Prioritize native coupling to
enabling technologies
▪ IT participation in
Procurement activities
▪ Gain More Value from Unified
Technology Investment
▪ Minimize Room for
Introduction of New
Technologies
■ Deploy or Upgrade to latest
application version
▪ Maximize support lifespan
▪ Access to the latest and
greatest application features
■ Applications Procured:
▪ Oracle Customer Care
and Billing (CC&B)
▪ Oracle Primavera
— Project Manager P6 R8.3
— Contract Manager CM14
— Progress Reporter
— P6 Analytics
Architecture Review Board
■ Subjected to any new
Applications procured
■ Verify new application do not
use in-built features that
overlap Unified Technology
Enablers
■ Explore Unified Technology
Enablers within context of
new Application usage
■ Define Integration Scope /
Data Ownership
■ Pre-requisite approval before
proceeding with regular
project work
■ Impact Consideration
— Make in-built overlapping
features non-functional /
redundant
— Cost to develop integration
of new Application to
Unified Technology
Enablers stack
Contract Work Packages
■ Shift from Wintel to EXA servers
■ Upgrade Oracle DB version from
9i to 11g
■ Standardize on Oracle Weblogic
Server
■ Applications deployed as
Managed Servers
■ LDAP Oracle Identity
Management
■ Four Environments
(Development, Test, Pre-
Production, Production)
■ Exhaustive Data Migration
Validation and Verification
▪ Database Migration
▪ Project File
▪ iManage Workflow Attachments
■ iManage Processes Oracle
BPM Processes
■ Infomaker Reports Oracle BI
Publisher Reports
■ DB Configured as RAC
Contract Work Packages
■ P6.0 Upgrade to P6 R8.2
▪ DB Upgrade from Oracle 9i to
11g
▪ DB Migration from P6.0 to P6
R8.2
▪ Deployment of P6 Application
Server as Managed Servers
■ CM13 Upgrade to CM 14
▪ DB Upgrade from Oracle 9i to
11g
▪ DB Migration from CM 13 to CM
14
▪ Deployment as Managed Server
■ P6 Analytics
▪ Creation of DB for P6 Analytics
▪ Deployment to OBIEE
▪ ETL from PMDB to P6 Analytics
DB
▪ Scheduling of ETL Services
■ BI Publisher
▪ Contract Management Reports
■ UPK
▪ Business Reporting Monthly
▪ Procurement Lifecycle
Risk List
■ Zero Reference Sites on EXA
■ RAC DB Configuration
■ Mandatory Webcenter Content metadata
■ Shared Infrastructure
■ Multi-disciplinary Skill Sets
■ Primavera - Fully Integrated
■ Exploit All Integration Avenues
Challenges
■ Shared Environment
▪ Frequent & Un-informed
Reboots
▪ Conflicting Configurations
■ Non-Compliant Metadata
Requirements
▪ Native P6 Integration to UCM
does not allow users to
specify metadata
▪ Develop new process to
ingest documents into UCM
but is tagged to project in P6
■ Conflict: OFM / P6 Versions
▪ Unable to integrate BPM
directly into P6 due to
different version of P6
■ CM Conflict Points
• RAC and Domain
Benefits
■ Asset Creation Division
▪ Access to richer and up-to-
date functionalities
▪ Robust BPM-based
workflows
▪ Sophisticate Analysis via BI-
Publisher and P6 Analytics
■ IT Division
▪ Maintain Unified Technology
Platform
▪ Single Support and
Development Team
■ Increase Project Controls for
better cost, schedule and
labor usage outcome
■ Increase usage of BPM layer
for non-Project user
participation
■ Increase Analytics for
Forecasting and What-If
Analysis
■ Better estimation for planning
next iteration of projects
Business Entities Moving Forward