1. Upgrade experience to Maximo v7
Upgrade experience to Maximo v7.6 – Moving from Customisation to Configuration
29th November 2018

2. Premier Oil Upgrade Journey
Introductions
Project Background
Aims & Objectives
Project Team
High Level Plan/ Timeline
Communication Plan
Upgrade Steps
Rollout - Familiarisation Sessions
Go-Live
Project Acceptance
Lessons Learned
IBM Watson and IoT & IBM Knowledge Centre
Q&A

3. Introductions
Catherine Brown – UK Business Systems Team Lead (UK IS Team)
Joined Premier Oil in 2011 as Information Systems Analyst for the Maximo 7.1 Implementation project working alongside BPD Zenith and Barrachd to help support the delivery of Maximo 7.1 as the UKBU ERP solution to replace MP5 and PIMS.
Currently lead a team of 3 to deliver systems implementations and upgrades for Premier Oil in the UK, whilst ensuring these and other business critical systems are maintained and supported.
Chris Brown – Maximo Engineer
Joined BPD Zenith in 2007 as a Maximo Engineer. Currently carrying out upgrades, development, interfaces, data loading and report writing.
Experience of Maximo version 4 to 7.6, on all Windows platforms, multiple Linux operating systems and managing cloud environments in AWS.
Worked with all the main Database Platforms including SQL Server, DB2 and Oracle DBA.
Integrated into 3rd party applications such as P6, Oracle Financials, BizTalk and tailor made mobile solutions.

4. Key Project Aims & Objectives
Phase 1
Keep system up to date, Maximo 7.1 support discontinued and no longer supported.
New standard functionality in 7.6 that will be of benefit to the business – improved user interface, PO revisions and multi-browser compatibility
Opportunity to rationalise existing v7.1 customisations and where possible, replace these customisations with standard functionality or configurations in v7.6, or make a decision to remove them.
Upgrade Cognos reporting as Maximo 7.6 includes license to use Cognos v10 instead of Cognos v8 which was previously licensed to use in Maximo 7.1.
Develop a new “Maximo to P6” planning interface to replace the existing “Maximo to MS Project” interface in 7.1 which wasn’t fit for purpose.
Phase 2
Business process improvements & recommendations

5. Project Team Executive Sponsor Project Steering Committee
Project Execution Team
Onshore & Offshore Operations
Finance
Supply Chain
Logistics
Inventory & Materials
Information Systems
Premier Oil Representatives
Executive Sponsor
Project Steering Committee
Project Execution Team
Project Team members covering, Onshore & Offshore Operations, Finance, Supply Chain Management (SCM), Logistics, Inventory & Materials Management and Information Systems (IS) functions.
3rd Parties
BPD Zenith
Barrachd
MaxMeta

6. High Level Plan Timeline
Initial upgrade conversations with vendors held - January 2016
Internal discussion held on how we would proceed based on E.ON UK E&P scope of work - January 2016
E.ON UK E&P Integration – February to July 2016
Provisioning of Infrastructure & Server Software installations – Early December 2016
Official Project Kicked Off – 13th January 2017
DEV Testing – 3rd April 2017
User Acceptance Testing (UAT) – 14th April 2017
Dry Run – 19th April 2017
Go-Live – 24th April 2017
Post Go-Live
HOTS & Phase 1 Project Close Out – 5th June 2017
Solan Maisy to Maximo Migration – Oct to Nov 2017
Phase 2 & Manifesting for UCC - Present

7. Communication Plan
Monthly Project Team updates via or meeting changing to Fortnightly as the upgrade date got closer – this replaced our Business Process Group (BPG) meetings
Liaising with key business users regarding decisions on customisations
Frequent Super User Group (SUG) meetings
Balmoral Asset Planner liaising with Offshore regularly
Familiarisation Sessions, onshore & offshore
Premier Connect (SharePoint Intranet) – Maximo Information Centre
Weekly updates with BPD Zenith – issues log and bug fixes shared via Premier Oil Extranet site

8. System Pre-Upgrade Steps
Infrastructure – new servers built for Maximo 7.5, 7.6 OOB, 7.6 DEV, 7.6 UAT, 7.6 PROD and Cognos 10 environments
Customisation Review – 7.1 customisations were not going to be recompiled or added straight back into 7.6:
Replaced with standard OOTB functionality in 7.6
Converted into standard configuration e.g. automation scripting
Removed if no longer required
Left as customisation
Manifesting – business decision to remove as it wasn’t being used.

9. System Upgrade Steps
The following steps were carried out, tested and signed off in 4 environments (BPD AWS, DEV, UAT and PROD):
Clean installation of Maximo 7.5 and 7.6
Standard IBM Maximo Upgrade tools used to upgrade the data and configurations from 7.1 > 7.5 > 7.6
Replace 7.1 customisations with configurations in 7.6 or re-create the customisations in 7.6 as identified during customisation review.
Develop new P6 interface (currently inactive)
Upgrade Cognos reporting to version 10 (Barrachd)

10. Rollout - Familiarisation Sessions
User list was exported from Maximo to group users into the following familiarisation sessions depending on their role within the system:
Requisitioner
Accounts Payable
Finance (Joint Venture Accountants)
Supply Chain
Onshore Ops
Offshore Ops
Anyone not grouped into any of the above (mainly Receipters & Approvers) received an prior to the upgrade informing them about the new version and updated guides
Premier Connect (SharePoint Intranet) – Maximo Information Centre

11. Go-Live Weekend Maximo 7.1 taken offline Friday 21st April @ 6pm
Export of 7.1 production database carried out by MaxMeta the same evening
BPD Zenith kicked off upgrade and deployed migration packages/customisations to the new 7.6 environment on Saturday 22nd April
Interfaces – existing MaxiSun interface repointed from 7.1 to 7.6
Finals checks
Sunday 23rd April was used for contingency
Maximo 7.6 available 24th 8:30am.

12. Project Acceptance & Close Out
Maximo successfully upgraded to v7.6 and Cognos to v10
New standard functionality introduced, rolled out and working successfully
Rationalise customisations
Maximo 7.1 Custom folder: 367 files, 61 folders
Maximo 7.6 Custom folder: 44 files, 21 2/3/17
Maximo 7.6 Custom folder: 50 files, 22 30/3/17
Maximo 7.6 Custom folder: 26/4/17
Classes removed – Chris to talk about

13. User Acceptance Testing (UAT) Testing Upgrade Sign-Off Matrix
Lessons Learned (2017)
Lesson Title
Lesson Description
Action
User Acceptance Testing (UAT)
Some business users identified for UAT had carried out positive testing well, as per the written test plans, however more negative testing was required. More thorough testing required from the business for both Maximo and Cognos Reports.
Evidence to be given from Business users that they have carried out negative testing scenarios via free-play. Tried to break it!
Testing Upgrade Sign-Off Matrix
Review of testing matrix to sign-off on.
Further evidence of UAT recorded in PMO testing folder i.e. Purchase Order with attachments.
Go-Live
Configuration
DNS configuration/redirect, doc links and PO s/attachments issues.
Future Pre Go-Live discussions to challenge the detail of each task so everyone is clear on the approach.
Start Centres
Notification prior to upgrade to advise Maximo approvers to clear their assignments.
Add this as a prerequisite so it is communicated that old notifications links will not work post upgrade.

14. Lesson Learned (continued)
Lesson Title
Lesson Description
Action
Communication
Project Team to improve communication within functional team and departments.
Ensure effective communication from project team members filters to all interested parties.
Post Go-Live Support
Bubble support in place with vendors post Go-Live for agreed time.
Include bubble support for future upgrades in agreements with vendors.

15. Solan Maisy to Maximo Lessons
No  
Lesson Title  
Description  
Mitigation  
Owner  
What went well: 1
Teamwork
Project team members worked well together, despite multi locations and remote 3rd party vendors.
Support from steering committee team members.
N/A
All 2
Delivery
Project team delivered on time and within budget.
There were savings noted on Maximo license user costs. IS 3
Scope
Project team managed scope changes well as per the project analysis.
Cognos was agreed as out of scope for delivery. 4
Knowledge
Good Maximo and Maisy knowledge held within the project team ensured success. 5
Dedication
Dedication of the project team members i.e. long hours during testing, addressing issues.
Agreed dedicated resource from maintenance department.
Maintenance resource had back up during illness, which kept project moving. 6
Communications
Project communication was managed well by all:
s (project, vendors, Premier staff).
Weekly project meets held by core project team.
Bi-weekly steering committee support and decisions.
Newsletters shared with Solan team.
Training delivered to Solan personnel on Maximo.

16. Solan Maisy to Maximo Lessons
No  
Lesson Title  
Description  
Mitigation  
Owner  
What could be improved: 7
Project Location
The IS project manager felt that working remotely from London was challenging and face to face meets is preferred – all the key stakeholders were based in Aberdeen, however, cost was a project constraint.
PM to kick off project with on-site presence. IS 8
Full commitments from departments – with agreed roles and responsibilities
To ensure delivery expectations were met with by all team members could be better. Lesson learned: (a) to agree with line managers on staff commitment and (b) agree dedicated resource effort for a set duration i.e. 3 days a week etc.
Role and Responsibilities clearly communicated with all members. Two way feedback and acceptance.
All 9
Project Control
Cognos reporting was not in scope for 6 Dec delivery; the steering committee agreed existing standard reports would suffice as short term, however, the project was not in control of a parallel activity to develop specific Cognos reports.
Agree as out of scope, from the offset to set expectations. 10
Data
The effort to upload all the Maisy data into Maximo as planned was under estimated (size, complexity, gaps) as it took longer to complete.
Added contingency for future data export / import. 11
Resource Changes
There were changes in project team members which were unforeseen.
Delegates identified where possible in advance. 12
Quality assure the data
A lot of effort was spent testing the data i.e. testing the workflow and structure. A key lesson is to focus more on the quality and contents of the Maximo migrated data.
Additional testing focus on data content / quality.
Business

17. IBM Watson IoT Badges & Knowledge Center
IoT Academy What's new in IBM Maximo Asset Management 7.6

18. Q&A