Implementation of Maximo v7.5 and Maximo Mobile Rachel Dunn Systems Development Mgr, Heathrow Airport Andrew Anderson Principal Consultant, Vetasi George Ribeiro-Justo Solution & Integration Architect, Capgemini

14 May 2014 Contents

• Heathrow Airport and Maximo • Maximo v7.5 Upgrade Project • Mobile Maximo Development • Next Steps Heathrow Airport Maximo at Heathrow

A Long History

Increasing Asset Base Through Airport Upgrade to v7.5 Developments

Divestment of Airports Project Background

Jul to Nov 2011 Dec 2011 to Jul 2012 Aug 2012 to Feb 2013 Mar 2013 to Feb 2014

Viability Define Design Implementation

• High Level Requirements • Detailed requirement definition • As-Is assessment • Delivery of the data definition • Solution evaluation (cost • Building Case for Change • Mobile functionality challenge vs functionality) assessment • All assets identified by type and • Market review and • RFP for product implementer • Training for business champions location identification of • Detailed planning for design in core product • System developed Activities options • Review of Lessons Learnt • To-be design workshops • System and performance testing from previous project • Interface design • User acceptance testing • Assessment of completeness and • Data migration • Train the trainer accuracy of current asset data planning course • Training of all areas • Go live

• High Level cost • Product selected • Functional Specifications • Clean database • Shortlist of products • Product implementer • Data Mappings • New System • Case for change created selector • Workflow Designs • Trained individuals • Interface Design • Mobile pilot • Design phase plan developed • Plan for remaining phase • Business Requirements Definition completed Outcomes • Clarity of extent of business change required and associated costs • Clarity of scope of cost for design phase from external suppliers based on BAA requirements • Clarity and effort required (and therefore cost) to restructure, preparing and cleansing the asset data

‘Maximo Project’ retitled to Engineering Intelligence

Engineering Intelligence

Operational Asset Data System Readiness Delivered by Engineering, for Engineering

• Accountable Project Manager from Engineering • 70 end-users involved in requirements and design workshops • 13 people involved in User Acceptance Testing • 13 trainers from across the business • 23 representatives at Operational Readiness Working Group (ORWG) • 14 Super Users mobilised at go live supporting users on the ground • Maximo administration team are part of engineering

Asset Data

Engineering Intelligence

Operational Asset Data System Readiness Over time the quality of asset data had deteriorated due to a wide range of issues. The Engineering Intelligence Programme will support the key driver of improving our data quality

THE DATA CHALLENGE Last Updated: 22/10/13

Expected Requirement Asset Knowledge Standards Asset Data & Knowledge Document / Data Set 04-Sep 23-Oct 18-Oct % Change Completion at Maximo Data Location Date Go-live

Standards Heathrow Common Language v.1 (document)(issued for review) Common Language 75% 100% 100% 0% 01-Oct 100% Asset Classifications and Attributes Common Language 100% 100% 100% 0% 03-Sep 100% Location Classifications Common Language 80% 100% 100% 0% 16-Sep 100% Location Attributes Common Language 50% 100% 100% 0% 20-Sep 100% Unit Code Classifications Common Language 60% 100% 100% 0% 23-Sep 100% Unit Code Attributes Common Language 50% 100% 100% 0% 24-Sep 100% Revised common Inventory Classifications and Attributes Common Language 92% 100% 100% 0% 16-Sep 100% Asset Surveys based PCR Codes Location + Unit (Failure class only) Common Language 0% 100% 100% 0% 01-Dec 100% PCR codes Asset (Failure class only) Common Language 90% 100% 100% 0% 16-Sep 100% Labelling Standard (document) (issued for review) Labelling Standards 100% 100% 100% 0% 01-Oct 100% Asset Labelling Labelling Standards 100% 100% 100% 0% 22-Aug 100% language Engineering Information Management Specification EIMS 30% 30% 30% 0% 31-Dec 100% on common language Location Hierarchy EIMS 100% 100% 100% 0% 22-Aug 100% Maintenance Strategies (filter and sort) EIMS 50% 50% 50% 0% 31-Dec 100% PCR Codes Location + Unit (hierarchy definition) EIMS 0% 0% 0% 0% 01-Dec 100% PCR codes Asset (hierarchy definition) Maximo 60% 80% 80% 0% 01-Dec 100% User Security Roles EIMS 100% 100% 100% 0% 22-Aug 100% Craft/Labour EIMS 100% 100% 100% 0% 03-Sep 100% Qualification standards EIMS 0% 0% 0% 0% 31-Dec 100% Oracle Category codes EIMS 50% 100% 100% 0% 30-Sep 100% Service Request Classification EIMS 100% 100% 100% 0% 22-Aug 100%

Asset Data Population Re-align Classifications to Common Language v11 Maximo 90% 90% 90% 0% 30-Mar 100% Re-align Classifications to Common Language v12 Maximo 0% 0% 0% 0% 30-Mar 0% Asset Verification and Assignment of Location - Red Maximo 39% 48% 48% 0% 30-Mar 100% Asset Verification and Assignment of Location - Amber Maximo 60% 60% 61% 1% 30-Mar 100% Asset Verification and Assignment of Location - Green Maximo 36% 29% 31% 2% 30-Mar 100% New locational Asset Labelling - Red Maximo 35% 45% 45% 0% 30-Mar 100% Asset Labelling - Amber Maximo 60% 60% 59% -1% 30-Mar 100% Asset Labelling - Green Maximo 29% 29% 31% 2% 30-Mar 100% Location coding of HAL Relabeling - T5 Maximo 0% 0% 0% 0% 0% Relabeling - T2 Maximo 0% 0% 0% 0% 0% based hierarchy Asset Attributes Maximo 0% 0% 0% 0% 0%

Asset Condition Maximo 0% 0% 0% 0% 30-Mar 35% Re-aligning T5 - Classifications Maximo 90% 90% 90% 0% 01-Dec 100%

Re-aligning T2 - Classifications Maximo 95% 95% 95% 0% 01-Dec 100% Baggage Approach Maximo 5% 25% 25% 0% 01-Nov 100% HALOPSYS Approach Maximo 0% 5% 5% 0% 01-Nov 100% Airside Approach Maximo 0% 10% 10% 0% 01-Nov 100%

Inventory Data Population Inventory Classification Maximo 33% 33% 33% 0% 31-Dec 100% Inventory Attributes Maximo 33% 33% 33% 0% 31-Dec 100% Inventory Photos Maximo 33% 48% 48% 0% 31-Dec 100% map oracle codes to inventory items Maximo 50% 100% 100% 0% 01-Nov 100% Assignment of locations inventory location population Maximo 100% 100% 100% 0% 22-Aug 100% Asset Attributes Locations Unit Coding HAL - number Drawings 60% 82% 82% 0% 31-Dec 100% Unit Coding HAL - name and type Drawings 20% 62% 62% 0% 01-Feb 100% Re-aligning T5 - Location Drawings 100% 100% 100% 0% 22-Aug 100% to all assets Updating Maximo (T5) with new unit codes Maximo 0% 0% 0% 0% 0% Re-aligning T2 - Location Maximo 50% 50% 50% 0% 0% Updating Maximo (T2) with new unit codes 0% 0% 0% 0%

Unit Code Classification Maximo 10% 10% 10% 0% 01-Feb 100% Unit Code Attributes Maximo 0% 0% 0% 0% 0%

Engineering

Job Plan creation based on new Maint Strat Maximo 0% 3% 3% 0% 31-Dec 100%

Update PMs in accordance with Maintenance Strategy Maximo 0% 12% 12% 0% 31-Dec 100% PCR codes (Failure Class) assigned to locations Maximo 0% 0% 0% 0% 01-Feb 100% PCR codes (Failure Class) assigned to assets Maximo 30% 50% 50% 0% 01-Feb 100% Defined Failure Maximo ‘cleansed’ to SharePoint for RAMS SharePoint 20% 25% 25% 0% 01-Jan 100% People Application of User securities Maximo 100% 100% 100% 0% 22-Aug 100% Assignment of shifts and calenders Maximo 100% 100% 100% 0% 22-Aug 100% Assignment of Labour Craft Maximo 100% 100% 100% 0% 22-Aug 100% Hierarchies common language Assignment of Labour Qualification Maximo 0% 0% 0% 0% 31-Dec 100% Update of user details (email/phone numbers) Maximo 100% 100% 100% 0% 22-Aug 100% Population of customer details Maximo 100% 100% 100% 0% 22-Aug 100%

Contracts Population of PM Costs Maximo 0% 0% 0% 0% 5% Operational Readiness

Engineering Intelligence

Operational Asset Data System Readiness Engineering Intelligence changes – why they matter Nearly 1,000 training man days completed with average feedback score of 4.5 (out of 5!)

To be % Classroom Course Attended trained Trained

Core Day 1 486 474 98%

Core Day 2 (Techs) 390 336 86%

Materials and Stores (incl DHL) 5 5 100%

AI & Planners 17 16 94%

Contractors 66 52 79%

Engineering Help Centre 14 14 100%

System Admin Team 5 5 100%

“Very well presented, the trainers really helped me to engage” “Good, fun, but informative” “Getting a better understanding of the business” “Getting to use new Maximo” “Good to see fellow Techs used to share knowledge” “Interaction, interaction, interaction!” ‘Maximo Project’ retitled to Engineering Intelligence

Engineering Intelligence

Operational Asset Data System Readiness Examples of Configurations

AssetNet Heathrow - Maximo 7.5 “Existing Application” MaxiNet – “Projects” Maximo – “Operational”

Project 1 Project 2 Asset Project 3 Etc. Details Details Daily Work Management Project 2 Asset Project 3 Asset Integration Creation Creation

Project 1 Asset Asset Asset Integration & Integration & Integration & Draft Planning Draft Planning Draft Planning

Daily Asset Project 1 Asset Project 2 Asset Project 3 Asset Management Approval Approval Approval

Asset Transition from Project to Operational Integration MaxiNet Asset = Not Ready Status Maximo Asset = Operating Status with Active Directory

Automated Customer Feedback Mobilising Maximo

Early 2012 • Clear requirement for mobilising our workforce Define

Late 2012 • Syclo or IBM Product Selection

• Workshops with Users Feb – Mar 2013 • To-be Process Design • Functional Specifications

Apr – Oct 2013 • Alongside core product build Build • Technical infrastructure complexities of Heathrow Network

Nov – Dec 2013 • UAT of Software Test • Independent of Device

• Device Requirements / Selection From Jan 2014 • Technical Infrastructure Roll Out • Pilot followed by Full Roll Out Andy Anderson Vetasi Mobilising Maximo – Design & Build

• Work Management and Inventory Management applications • Workshops with Users Feb – Mar 2013 • To-be Process

Design • Functional Specifications

• Development in parallel with core product build • Unit Testing Apr – Oct 2013 • Technical infrastructure complexities of Heathrow Network Design Build Mobilising Maximo – Design Phase (Feb – Mar 2013)

• Individual Workshops for: • Work Management and Inventory Management

• Workshops with Users – So who were they? • Future users of the Mobile applications – YES • Had participated in the core product design – YES • Were empowered by the business to take ownership - YES Design • To-be Process Verification • Step through of the core product processes to be mobilised • Lets all start the workshop with the same vision of WHAT we Workshops mean by mobile working

“Who & What” Mobilising Maximo – Design Phase (Feb – Mar 2013)

• Meeting the Business Requirements:

• Design Principles! • Does it do it as standard? • If it does – show it • If it doesn’t – do we need it? Design • Business Rules should be the same as Core Maximo

Workshops • Keep it Simple! “HOW” Interesting Point ! At the time of the design workshops it was not possible to use the “Android” version!

Workshops and Design was completed using the “Windows” version

Mobilising Maximo – The Approach

• Fulfil the business requirements

• Align with “Core Maximo”

• High quality and easy data collection

• Sympathetic to a wide variety of user “Technical Abilities” Mobilising Maximo – The Design Challenges

Maximo Maximo Mobile

Work Flow & Status Mobile - Create Status Change Rules Matrix

Field Validations & Mobile - Create validation Conditional Mandatory rules Fields Mobile – Mandatory Fields

Product Gaps: Develop New – Shipment Shipment Receiving Receiving Application

New Fields / Sections Mobile – Add / Hide Fields

Results Set Based Mobile - Work Lists Work Allocation Mobilising Maximo – Design Outcomes

• Inventory Manager • New Application Development – Shipment Receiving • Key to the fulfilment of stock from Main to remote stores • Screen Layout • Prioritise Field Placement around business process

• Work Manager • New Screen Development – Permits • Bringing HAL Permits into the safety plans screen Design • Multiple Work Lists • My Work / My Teams Work / My Completed Work • Status Change Rules Workshops • Same Option as if using Work Flow in Maximo • Field Validation • EG Max allowable Labour Booking (16hrs) “What” Mobilising Maximo – Design Examples Inventory Manager – New “Shipment Receiving” Application Mobilising Maximo – Design Examples Start Centre Work Lists Various Field Changes

Conditional Validation – Status Memo

Conditional Validation – Max Labour Hours Mobilising Maximo – Build Phase (Apr – Oct 2013)

• Development Team: • Vetasi – Application Development • CapGemini – Network Enablement • IBM – Product Enablement Support

• Application Development • Platform – Local VM • Network – Localised Wi-Fi • Devices – Samsung Tablet / Samsung PDA Build • Maximo Mobile • Android Version Released – 7.5.1 Phase Brick wall?

Brick Wall or Steps?

• Collaboration and understanding the problems. • Working Group set up with input from Vetasi, CapGemini, IBM UK & US • Daily & Weekly progress updates (2 way) and shared screen sessions The Steps!

• Review: Are the configurations appropriate? – Collectively agreed YES • Confirm: Can the developments be completed on the “7.5.0 Windows Version” – YES • Confirm: Can the developments be completed on the “7.5.1 Android Version” – NOT INITIALLY

• So what's the key difference?

• 7.5.1 Android Release – Development steps / file structure was different!

• Now the issues could be resolved

The configurations – Work Lists

As-Designed

As-Built Complications! • Grouping by team was not as easy as it sounded • Completed Work – Really! The Configurations – Shipment Receiving

Complications! • Data Length • Synonym Domain Change Testing – Unit Testing • Sample Data Sets – Using 1st Pass upgraded data • Sample Devices • Local WiFi • No Maximo Integrations Testing – User Acceptance Testing • Heathrow Test Network • Upgraded Heathrow Data • One issue identified during UAT was that the test scripts were developed using the windows desk top version – The key steps were correct, but some of the menu driven steps were confusing. George Ribeiro-Justo Capgemin Heathrow Maximo 7.5 Architecture

New Complex New Platform Architecture Infrastructure Standards

New Common Many Architecture Services Environments Building Blocks Overview of Heathrow Maximo Environments Overview of Heathrow Maximo 7.5 Deployment

Key NFRs Sizing Model Proposed Hardware

. 400 Concurrent users . 8 instances for Maximo . 2 x 16 cores with business users (UI) to 96GB memory . 300 reports / day handle 400 concurrent users . 2 x Weblogic . 99.9 availability Application servers . 24 x 7 X 365 . 2 instances for (SLES 11 with 2 x 8 Integration (MEA for core CPU and 96GB Oracle/MIF) RAM) . 2 instances for reporting . 2 x Oracle database . 1 instance for cron tasks servers (SLES 11 with 2 x 8core CPU and . 3 instances for systems 64GB RAM)

x 8

F5 BigIP

x 2

x 1

Application Server 1 Application Server 2 APPs Share – General attachments

cluster heartbeat

x 2 Clustered Database Clustered Database 1 2

SAN – mirrored across data centres

The JVM Deployment

UI

Report

Integration

CRON

Primary Server Secondary Server Mobile Device Management

Heathrow supports a secure connectivity solution for mobile devices to connect to their corporate Wi-Fi network and VPN using certificates

The Heathrow Mobile Device Management (MDM) solution is based on AirWatch deployed as a SaaS providing mobile device registration, management, reporting and configuration enforcement The Overall Mobile Infrastructure Architecture Main Challenges with Android Devices

Maximo Mobile Android devices requirements:

Minimum of 1GB of RAM Gingerbread (2.3.4) level or higher Versions +2.3.x are supported with API Level 10 Screen sizes are not smaller than 4" Only medium, high, and extra high screen densities Min. Internal storage capacity 4GB

Only Android 4.3 devices could connect consistently to the Wi-Fi Results of our Tests

Device OS Version Test Results Samsung Android 4.1.2 Authenticated successfully to Wi-Fi but could not get IP Galaxy III Mini address. Samsung Android 4.1.2 Authentication to Wi-Fi fails. Galaxy Notes II

HTC phone Android 4.0.3 Authentication to Wi-Fi fails. HTC Phone Android 4.2 Authenticates and connects to Wi-Fi successfully. Note: Rooted device, so the test are inconclusive.

Lenovo Android 4.2 Authenticated successfully to Wi-Fi but could not get IP IdeaTablet address. A3000 Tablet Samsung Android 4.3 Authenticates and connects to Wi-Fi successfully. Galaxy Notes 3

Nexus Tablet Android 4.3 Authenticates and connects to Wi-Fi successfully. Mobile Deployment Lessons Learned

Many of the issues we have encountered were not related to Maximo mobile but the device and AirWatch

A problem with Android 4.3 leads to the certificates to The Maximo application look disappear and the AirWatch and feel, and navigation vary profiles must be re-applied to from different Android devices reinstall the certificates.

The AirWatch app is available The installation of the from the App Store but certificates is cumbersome, not Maximo is not. So installation user friendly and therefore not Maximo on the devices is not suitable for end users. user friendly for end users. 2013 saw the birth of the Engineering Intelligence Program

- Overhaul of Heathrow Common Language - Development of Labelling Standard - 80% Unit Coding of Heathrow - Commencement of Asset Validation Activities

2013 Commence - User Driven Design of New Maximo System Data - Development and testing of new system - One of the most successful Develop implementations of a critical system at Enhanced Heathrow System

- Commencement of EI communications Sow the seed - Commencement of Culture Change - Roll out of training

2014 will embed the basics of Engineering Intelligence

- Asset Integrity information correct - Inventory information correct - Transition data improvement into BAU - Development of an Asset Data Quality Dashboard

2014

Complete Data - Embed Maximo 7.5 into core practice Basics - User Governance Group Develop lag - Commence regular release cycle reporting - Pilot and deliver Maximo Mobile Embed new - Improved reporting capabilities System

Embed the change - Support leadership of data usage - Develop EI BAU comms program - Establish data quality auditing Any questions?

Rachel Dunn Systems Development Mgr, Heathrow Airport Andrew Anderson Principal Consultant, Vetasi George Ribeiro-Justo Solution & Integration Architect, Capgemini