Today's enterprise web portals are complex beasts. Leading portals deliver fresh and relevant personalized experiences to multiple audiences, each with their own branding, content, and interactions. They aggregate content from multiple sources and present it using components, some of which are are reused across audiences. They make users productive by interacting with core transactional systems, and secure themselves with role-based access control. Web portals require careful management to ensure they deliver robust, personal, agile, and sustainable experiences in the face of continuous change. The ArchiMate language is ideal for elucidating the structure and function of web portal applications and infrastructure, and linking them to the consumer experiences and internal operations they support. Modelers can also link critical business stakeholders, drivers, and goals to requirements for new investments, link these requirements to changes in applications and infrastructure that satisfy them, and show how these changes can be implemented over time. Join practicing Enterprise Architect and ArchiMate Forum Vice Chair Iver Band and portal expert Ryan Kennedy to learn how to use the TOGAF Framework and the ArchiMate language to depict complex architectures and the changes they require.

1. 1
Modeling and Evolving a Web Portal
with the TOGAF Framework and the
ArchiMate Language
Iver Band and Ryan Kennedy
Open Group Conference, San Francisco, California
January 27, 2016
© 2016 Cambia Health Solutions, Inc.

2. 2
2 © 2016 Cambia Health Solutions, Inc.
Iver Band
• Enterprise Architect at Cambia Health Solutions
• Web, mobile, analytics, campaign management, consumer data
• Architecture methods and tools
• Vice Chair, Open Group ArchiMate Forum
• TOGAF and ArchiMate certified, CISSP, AHIP Certified IT Professional, Certified
Information Professional
iver.band@cambiahealth.com
http://www.linkedin.com/in/iverpdx
http://www.cambiahealth.com/
http://www.twitter.com/iverband

3. 3
3 © 2016 Cambia Health Solutions, Inc.
Ryan Kennedy
• Digital Solutions Architect at Cambia Health Solutions
• Over a decade experience designing and implementing portal solutions
ryan.kennedy@cambiahealth.com
http://www.cambiahealth.com/
https://www.linkedin.com/in/rykennedy

4. 4
4
Agenda
•Background
•Case Study: Integrated Healthcare Delivery
•Conclusion and Discussion
© 2016 Cambia Health Solutions, Inc.

5. 5
5
BACKGROUND
© 2016 Cambia Health Solutions, Inc.

6. 66
About Cambia
22 companies
and growing
© 2016 Cambia Health Solutions, Inc.
A tax-paying nonprofit
headquartered in
the Pacific Northwest
Nationally recognized:
Top 100 Healthiest
Workplaces
5,300 employees
in 30 states
100 million people
touched nationwide

7. 77 © 2016 Cambia Health Solutions, Inc.

8. 88
Cambia Health Solutions
© 2016 Cambia Health Solutions, Inc.
Senior
Services
Health
Insurance
Retail
Enablement
Provider
Enablement

9. 9
9
What is a Horizontal Web Portal (“Portal”)?
• A personalized point of access to relevant information,
business processes and people
• Supports a wide range of vertical markets and business
activities
• Addresses various audiences, including employees, customers
and partners, and citizens
• Delivers content to users of industry-standard web browsers
• Reuses, adapts and personalizes content and features for
different audiences
• The “Swiss Army knife” of enterprise software
© 2016 Cambia Health Solutions, Inc.
Adapted From Gartner Group: Magic Quadrant for Horizontal Portals, 15 Sep 2016

10. 10
10
What Are the Advantages of Portals?
Standardized Management of Segmented Experiences
User Experience Enabling Services
Personalization & Context Awareness Identity and Access Management
Navigation, Search and Discovery Content Management
Collaboration and Knowledge Mgmt Transaction & Commerce Support
Mobility and Multichannel Support Integration and Interoperability
Analytics and Experimentation
Standardized Architecture and Development
© 2016 Cambia Health Solutions, Inc.
Adapted From Gartner Group: Critical Capabilities for Horizontal Portals, 10 Dec 2015

11. 11
11
What Are the Disadvantages of Portals?
© 2016 Cambia Health Solutions, Inc.
Disadvantage Mitigation Strategy
Business Process Overhead Ensure retirement of legacy architectures
and the processes that support them.
IT Process Overhead
Technical Complexity Use layered, component-based
architecture that matches intended
usage.
Technical Talent Requirements Maximize reliance on predominant web
standards, open-source components, and
preferred products and services.
Apply standards to abstract proprietary
interfaces.
Product Lock-In

12. 12
12
Portal Architectures Must Increasingly Meet Market
Demands for Always-On Services
Legacy Websites Market Demands
Availability Regular Maintenance
Windows
Always Available
Scalability Thousands of Users
Predictable Peaks
Millions of Users
Unpredictable Bursts
Response Time Keep Users Productive No Wait
Identity and Access
Management
Internal User Base with
Centralized
Administration
Infinite User Base with
Multiple Identity
Providers
Data Normalized for Integrity Cached for Performance
and Availability
Integration Batch ETL and File
Transfer
Lightweight, standards-
based APIs
© 2016 Cambia Health Solutions, Inc.

13. 13
13
CASE STUDY
© 2016 Cambia Health Solutions, Inc.

14. 14
14
Fictitious Case Study: OmniHealth 365
• Integrated Delivery System
• Hospitals, Clinics, Urgent Care
Centers
• Separate Websites for Each
Audience
• Public, Providers, Consumers,
Administrative Staff
• Challenges
• Expense and complexity of
maintaining separate websites
• Experience consistency across
websites
• Difficulties for users of multiple
websites
• Goals
• Improve user experience
• Introduce new experiences
more quickly
• Improve overall quality
• Share underlying services with
emerging mobile applications
• Focus resources on developing
features rather than overhead
© 2016 Cambia Health Solutions, Inc.

15. 15
15
The TOGAF ADM Provides a Systematic
Approach to Portal Architecture
© 2016 Cambia Health Solutions, Inc.
P
Preliminary Phase

16. 16
16
The ArchiMate Language Complements
TOGAF With Standard Visual Modeling
© 2016 Cambia Health Solutions, Inc.
P
Preliminary Phase

17. 17
17
Language Elements & Specializations
© 2016 Cambia Health Solutions, Inc.
P
Preliminary Phase
The ArchiMate language can be adapted

18. 18
18
Vision
© 2016 Cambia Health Solutions, Inc.
Delighted Web Audiences
Integrated Content, Technology & Lifecycles
Shared Data & Infrastructure
Agility Cost
Savings
A
Architecture Vision

19. 19
19
Stakeholder Motivation & Goals
© 2016 Cambia Health Solutions, Inc.
A
Architecture Vision
ArchiMate modeling can capture politics and strategy

20. 20
20
Principles, Requirements, & Services
© 2016 Cambia Health Solutions, Inc.
A
Architecture Vision
ArchiMate notation can connect motivations and the elements that realize them

21. 21
21
Baseline Business Architecture
© 2016 Cambia Health Solutions, Inc.
B
Business Architecture
Unique web processes with basic functionality

22. 22
22
Target Business Architecture B
Business Architecture
Common web processes with advanced functionality

23. 23
23
Baseline Data Architecture
© 2016 Cambia Health Solutions, Inc.
C
Information Systems Architecture
Four data silos

24. 24
24
Target Data Architecture
© 2016 Cambia Health Solutions, Inc.
C
Information Systems Architecture
One shared data store

25. 25
25
Baseline Application Architecture
© 2016 Cambia Health Solutions, Inc.
C
Information Systems Architecture
Redundant login component example

26. 26
26
Target Application Architecture
© 2016 Cambia Health Solutions, Inc.
C
Information Systems Architecture
Standard portal login component

27. 27
27
Baseline Technology Architecture
© 2016 Cambia Health Solutions, Inc.
D
Technology Architecture
Four unique web stacks

28. 28
28
Target Technology Architecture
© 2016 Cambia Health Solutions, Inc.
D
Technology Architecture
One common web stack

29. 29
29
Solution Decisions
© 2016 Cambia Health Solutions, Inc.
E
Opportunities & Solutions

30. 30
30
Implementation and Migration Plan
© 2016 Cambia Health Solutions, Inc.
F
Migration Planning
Phased implementation beginning with public experience

31. 31
31
Work Plan
© 2016 Cambia Health Solutions, Inc.
F
Migration Planning
Each plateau is realized by specific deliverables

32. 32
32
Driving Agile Delivery
© 2016 Cambia Health Solutions, Inc.Work is broken down into story cards & assigned to Agile teams
G
Implementation Governance

33. 33
33
CONCLUSION AND
DISCUSSION
© 2016 Cambia Health Solutions, Inc.

34. 34
34
Conclusion
• Horizontal web portals address complex user experience challenges in healthcare
and many other industries
• Organizations must understand the needs of each of their audiences before
embarking on transformation projects
• Portal solutions are complex because portals have multifaceted and
interconnected responsibilities.
• Organizations should therefore develop portals incrementally as they build their
planning and implementation capabilities
• Architects can use the TOGAF framework and the ArchiMate language for
clarifying portal strategy, developing architecture and roadmaps, and driving agile
delivery
• The ArchiMate language can be adapted for different modeling challenges and
audiences
© 2016 Cambia Health Solutions, Inc.

35. 35
35
Your Turn
© 2016 Cambia Health Solutions, Inc.