205560 jeppesen’s upgrade to primavera p6 release 8.2 agile approach
1. Jeppesen’s Upgrade to Primavera P6 Release 8.2
Paves Way for Agile, Global Capabilities
Martina Mauzy
Sr. Manager, Enterprise Process Solutions
Carl Meilahn
Primavera Technical SME
Jeppesen Sanderson, Inc., a Boeing Company
8 April 2013
Copyright @Jeppesen 2013
Session ID: 205560
2. 2
Transforming Global Transportation
Through the power of intelligent
information solutions and
integrated services
Aggregated and layered aeronautical
and marine information
www.jeppesen.com
Copyright @Jeppesen 2013
3. 3
Jeppesen by the Numbers
Journey
Planning
2,400,000 Travelers benefiting from Jeppesen
real-time optimization, daily
Aviation
200 Countries with pilots using Jeppesen
650 Airlines served by Jeppesen
48,000 Pilots trained , annually
70,000 Jeppesen flight plans provided, daily
83,000 Jeppesen weather briefs provided, daily
300,000 Crew managed with Jeppesen tools, daily
1,000,000 Pilots worldwide using Jeppesen
Marine
6,500 Commercial vessels using Jeppesen data
27,000 Digital navigation charts in Jeppesen library
1,500,000 Leisure boat customers
Global
41 Jeppesen locations in 22 countries
220 Countries providing source data
3,200 Jeppesen employees
150,000 Jeppesen charts (air & sea)
1,400,000 NavData records in our database
5,000,000 Unique pages of documents
800,000,000 Sheets printed, annually
Copyright @Jeppesen 2013
4. 4
Primavera Version
prior to Upgrade PV
6.2.1 8.1 8.2.1
Integrations to Oracle
eBusiness Suite
(Projects, HRMS) and
Kronos
Implementation
Included: Primavera
Progress Reporter, P6
EPPM Web, P6
Professional Client, BI
Publisher
Existing user base:
• ~175 Project Manager
licensed users
• ~1000 Timesheet
license users in global
locations
Supporting ~200
software development
projects
Jeppesen Primavera Overview
Current State
Methodologies in use:
Iterative Development,
Agile, Waterfall
Copyright @Jeppesen 2013
5. A Changing Environment
Driving Forces for Primavera Deployment
Transformation – become project driven
Process Changes – moving towards agile
Easier Scalability - for global deployment
Enterprise Resource Management – global view
5
Copyright @Jeppesen 2013
6. Agile Integration Need
What is in our plan
Current Pain
Points
• Multiple time entry
• Time entry does not
match between
systems
• No definition of what
lives in Primavera vs.
Agile Tool
• Lack of business
process definition
between systems
Integration with
Progress Reporter
• Definition of levels in each
system – integrated
schedule process
• Agile Tool to be used for
detailed task tracking
• Primavera to be used for
project forecasting and
integrations
6Copyright @Jeppesen 2013
7. P6 Web
Benefits for Jeppesen
7
Portfolio Analysis
• Status snapshot of a portfolio of projects
• Customized portfolio view capabilities
• Global portfolio indicators
Resource Analysis
• Use visibility to identify over / under allocated resources
• Focus on Enterprise Resource Capacity Planning
• Resource Team Analysis (Charts or Spreadsheets)
Portfolio Dashboards
• Portfolio views created real time in one easily accessible location
• Spreadsheets can be eliminated
• Custom user-defined performance indicators
Copyright @Jeppesen 2013
8. Custom
Training
Materials
Training
Delivery
Lessons
Learned
Primavera Training
Lessons Learned
8
Organize content by
functional area
Conduct role based
training
Allow enough time for
pilot feedback
Customize UPKs for
Jeppesen need
Create in-depth
classes on specific
topics
Don’t underestimate time
for customized training
materials
Create quick reference
guides
Perform web
application training
Adoption rate is slow for
users comfortable in
Windows Client
Create wiki page as
point of entry
Focus training on tool
capabilities
Copyright @Jeppesen 2013
9. BI Publisher
Lessons Learned
9Copyright @Jeppesen 2013
BI Publisher
Training Security Testing Patches
Obtain advance
training prior to
install
Choose the right
Security Model
for report access
Allow sufficient
time for testing
Various errors
are bugs in the
tool
Create BI training Consider
installing BI on
separate server
Evaluate report
failures
Double check to
see if it is human
error or a bug in
the tool
Check for new
patches
10. Resolution:
• Installing application in Citrix environment reduced
installs from over 100 to 4.
• Creates standard installs allowing us to delegate RAM
for the session to the users independent of their local
desktop environment.
• Resulted in 90% reduction in support tickets for Client
installs.
Problem:
Over 100 Desktop user installs during
upgrades became time intensive and
support was expensive.
10
Primavera Implementation Issues
P6 Primavera Client via Citrix
Copyright @Jeppesen 2013
11. Resolution:
• Single point of entry for new users via Oracle
eBusiness HRMS solution maintained by HR.
• Increased integration to all business systems by
utilizing one source of truth.
• Improved user satisfaction as it resulted in one less
password to remember.
Problem:
Users were maintaining separate logins for
Primavera vs their network login resulting in
complaints from users and IT.
11
Primavera Implementation Issues
Utilizing Active Directory for Authentication
Copyright @Jeppesen 2013
12. Resolution:
• Turn off Job Services in the web client configuration.
• Create another configuration of just P6 Job Services.
• Install the P6Services.jar Java application on
additional dedicated private cloud servers.
• Group by EPS and schedule jobs in Parallel to
maximize server utilization and locate issues faster.
Problem:
Job Services impacted P6 Web application
performance.
12
Primavera Implementation Issues
Speeding Up Scheduled Jobs
Copyright @Jeppesen 2013
13. Resolution:
• Previous bug in Primavera was resolved in 8.2.
• Manual time entry will be recalculated to the sum of
related timesheet entries when the Apply Actuals
process is run.
• Requires users to enter time for tasks via Progress
Reporter.
Problem:
Manual update of assignment actual hours
was used for timesheet users on projects.
13
Primavera Implementation Issues
Manual Time Entry
Copyright @Jeppesen 2013
14. Resolution:
• The manual database upgrade process results in a lot
of wasted effort debugging application.
• Database upgrade tool provides immediate notification
of database upgrade failure
• Impact: upgrade team to know where to look for
upgrade failures.
Problem:
Database upgrade tool was not utilized
during first 8.2 upgrade attempt causing a
reschedule of the upgrade.
14
Primavera Implementation Issues
Database Upgrade Tool
Copyright @Jeppesen 2013
15. Resolution:
• Save your data queries from BI 10g to easily re-create
the data model in BI 11g.
• Improve your report templates and layouts in BI 11g
due to additional capabilities.
Problem:
Unable to convert report files from BI
Publisher 10g to 11g.
15
Primavera Implementation Issues
BI Publisher Upgrade to 11g
Copyright @Jeppesen 2013
16. Resolution:
• Implemented Weblogic clustered environment.
• Added additional external servers dedicated to running
Services.
• Standardized PM user desktop configuration (64-bit
Windows 7 and 8 MB RAM).
• Provisioned Internet Explorer browser access via Citrix
for non-local users and Professional for all PM users.
Problem:
After initial upgrade to R8.x User experience
and system performance was poor.
16
Primavera Implementation Issues
System Performance
Copyright @Jeppesen 2013