©2014 Software AG. All rights reserved. 2 |
EA and BPA cooperation being driven by business reality,
e.g. “Age of the Customer”
• Getting the right customer experience will drive business growth
retain, service, upsell
• Top four technology priorities of business are all about the customer
• Harmonized systems of customer engagement need BPM and EA intersection
• Role of BPM is to design the processes that will actively support the envisioned
customer experience.
• Role of EAM is to define architecture principles as a basis for decisions and
govern how architecture solutions are designed for optimal customer
experience
Gartner Strategic Planning Assumption:
“By 2015, over 75% of EA and BPM constituencies will be jointly developing high-level function and process views of the enterprise, using a variety of
techniques. ”
©2014 Software AG. All rights reserved. 3 |
BPA & EA: Different perspectives on transformation and
alignment
Business BPA
IT EA
How do I deliver new
business models?
How can I reduce process costs?
How can I make business more
agile?
How can I measure process KPIs?
We don’t understand the impact
on IT!
How do I standardize to
reduce IT costs?
How do I make IT less complex
and more agile?
Poor input on requirements is
leading to expensive IT projects.
How do I align to business
strategy?
We don’t understand what
process teams are doing.
Project Focus Enterprise
Focus
©2014 Software AG. All rights reserved. 4 |
• Understand, analyze and transform
your business processes
• Measure & track process
performance KPIs
• Discover and analyze variations in
processes
• Provide the critical intelligence
needed to help you reduce process
costs and transform the business
• Reduce the costs of IT
implementation by clearly
documented processes
• Get reliable information on
applications, their integrations and
how they support business
• Identify redundancy in IT support for
business processes
• Plan IT consolidation which helps
reduce process costs and makes IT
more agile
• Move IT spending from operating
applications to investing in business
change
• Get more budget for your business
process transformation projects
Market-leading* solutions for Alignment and
Transformation
ARIS - Leader in BPA ALFABET - Leader in EA and ITPM
*Gartner: “Magic Quadrant for Business Process Analysis Tools”, 12th December 2011
“Magic Quadrant for Enterprise Architecture Tools”, 30th September 2014
“Magic Quadrant for Integrated IT Portfolio Analysis Applications”, 18th November 2014
©2014 Software AG. All rights reserved. 5 |
ARIS - Alfabet Repository Federation Layer
AR IS Des i gn Se rver
ALFABET Repos i to ry
" S y s t e ms "
" Pr oc e s s e s "
• Data maintained in either ARIS or Alfabet can be re-used in the other application to
ease data maintenance and to prevent data inconsistencies between the different
management tools
• The ARIS-Alfabet interoperability allows for the regular synchronization of data
between ARIS and Alfabet.
©2014 Software AG. All rights reserved. 6 |
UI Interoperability: Aligned User Experience
N a v i g a t e
t o Pr o c e s s
• User can easily traverse between the user interfaces of ARIS and Alfabet for a 360-
degree view of business processes and their corresponding application portfolios.
N a v i g a t e
t o S y s t e m
©2014 Software AG. All rights reserved. 7 | 7 |
Scenario 3: Repository Interaction Layer
• Rather than replicating all information between the two repositories the
products directly interact with one another’s repository
• This will not be used for all objects/models
• In a diagram in ARIS the user has the ability to place a shape that refers to an object
in Alfabet rather than ARIS
• Upon placing the shape on the diagram the user searches the Alfabet repository to
pick the object as desired
• While the object is placed it is also replicated into the ARIS repository with cross
linkage to the Alfabet object
• For an object in Alfabet the user can pick a diagram from ARIS and associate it with
that object
• While the diagram reference is established a reference to the object in Alfabet is
stored on the model in ARIS
• Equally the user can trigger the creation of an ARIS model from an object in Alfabet
and automatically be brought to that model in the ARIS UI to start design work
©2014 Software AG. All rights reserved. 8 | 8 |
Scenario 3: Repository Interaction Layer (cont.)
• Advantages
• Low cost for the customer
• Uses ARIS diagram filters to determine where to associate ARIS versus Alfabet objects
• High flexibility for the customer
• Adaptable to the customer‘s ARIS and Alfabet meta models
• Supports development of a coherent methodology between ARIS and Alfabet
• Lead customers can contribute to the development of such methodology
• Some guidance and direction to customers based on predefined ARIS diagram filters
and interactions in Alfabet views
• Disadvantages
• Limited guidance and direction to customers
• Reporting, integration, navigation, user management continue to be different for both
products
• Separated, non-synchronized repository content
©2014 Software AG. All rights reserved. 26 | 26 |
Scenario 3: Repository Interaction Layer (cont.)
• Next steps for customer discussions
• Define objects to be mastered in ARIS and objects to be mastered in Alfabet
• Define model types to be associated with objects in Alfabet
• Define Alfabet objects to be used on ARIS model types
• Define model filter rules for ARIS model types using Alfabet objects
• Next steps for internal discussions
• Define API interactions required to support Repository Interaction Layer
• Enhance ARIS model type filter definition to include Alfabet objects
• Enhance ARIS model type filter definition to allow selecting ARIS, Alfabet or both as
source for objects
• Enhance Alfabet to store associated ARIS models in an Alfabet object
• Enhance Alfabet to select ARIS model types to be associated with Alfabet objects
• Enhance Alfabet to trigger creation of an ARIS model with a specific type from Alfabet
• Enhance ARIS to store link to referencing Alfabet objects on ARIS models
• Enhance Alfabet to open an ARIS model directly from an Alfabet object