A Customer Success Story

The Challenge

As part of an IT department transformation in 2009/10, the Cathay Pacific Information Management Team (IMT) reestablished the enterprise and solution architecture capability with the ambition of moving from ‘architecture by luck’ to ‘architecture on purpose’.

The federated organization structure created inefficiencies in delivery and prevented long-term enterprise IT planning. The cyclical nature of the industry required long term planning and diligent cost control. The need for a strong architecture process, a clear vision for the future and the path to achieving it were evident.

The company selected Orbus Software’s iServer as its Architecture Repository tool for this initiative, to rebuild the architecture function as part of the reorganized IT department.

Selecting iServer

Selecting and implementing an Architecture Repository tool was an early step for the team. Cathay Pacific wanted a ‘fit for purpose’ tool to facilitate representation and communication of the Enterprise Architecture strategies, blueprints and reference architecture as well as standardised delivery of solution architecture and design.

After assessing EA tool vendors and products, Cathay Pacific selected the full product suite of iServer, developed by Orbus Software, because it met the airline’s key architecture requirements, its functional fit, its alignment to principles (i.e. Open Standards - TOGAF 9) and its cost comparison.

iServer is an enterprise architecture repository and modeling environment for Microsoft Office and Visio users where Visio shapes (such as business services, applications, technology components, organizational units, etc.) and Office document components are stored and managed as Repository objects.

The key concepts that determined the selection of iServer as the EA tool at Cathay Pacific included:

• Use of familiar Microsoft Office and Visio ensured minimal user resistance from the architecture team.
  
• Support for Office documents meant TOGAF® 9 deliverables could be managed in the same central environment as the architecture building blocks.
  
• Flexibility of the system allowed Cathay to quickly customize the system to implement only the aspects of TOGAF 9 which were useful and to extend as necessary (i.e. CXAF).
  
• Production of extremely high quality EA deliverables which were visually appealing to stakeholders, an essential requirement due to the need to ‘sell’ the benefits of architecture to the business.
• Dependency analysis tools ensured the Cathay team could interrogate the architecture to answer key business questions such as which applications are affected by particular project(s).