Toward Innovative Model based
Enterprise IT Outsourcing
Vinay Kulkarni and Sagar Sunkle
NGEBIS Workshop at CAISE 2013
Overview – Problem
Business
Enterprise
Overview – Problem
Business
Enterprise
Business Silos for Ease
of Management and
Control
Overview – Problem – State of IT systems
Transactional IT needs : day-to-day operational
requirements
IT Need 1
Enterprise
IT Need 2
IT Need 3
…
Transformational IT needs : responding to
change; multiple change drivers active- dynamic
supply chains, mergers and acquisitions,
globalization and regulatory
compliances, cloud and mobile technology
Both kinds originate in strategic, tactical, and
operational goals of the enterprise
Overview – Problem – State of IT systems
Transactional IT needs : day-to-day operational
requirements
Enterprise
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Overview – Problem – State of IT systems
Transactional IT needs : day-to-day operational
requirements
Enterprise
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Only local context known (if at all);
enterprise-wide context unknown
Overview – Problem – State of IT systems
Transactional IT needs : day-to-day operational
requirements
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Enterprise
Implement or improve in
Specific
Contexts of Business Silos
Overview – Problem – State of IT systems
Transactional IT needs : day-to-day operational
requirements
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Enterprise
Locally Operational/Optimal
Overview – Problem – State of IT systems
Transactional IT needs : day-to-day operational
requirements
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Enterprise
Globally Optimal ?
Overview – Problem – State of IT systems
Transactional IT needs : day-to-day operational
requirements
Enterprise
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Overview – Problem – State of IT systems
Transactional IT needs : day-to-day operational
requirements
Enterprise
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Implementation of Functionalities servicing globally felt need may
overlap due to lack of knowledge about enterprise-wide context
Overview – Problem – State of IT systems
Transactional IT needs : day-to-day operational
requirements
Enterprise
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Specific contexts may also result in
Non-interoperable technologies
Overview – Problem – State of IT systems
Transactional IT needs : day-to-day operational
requirements
Enterprise
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Globally Sub-optimal design of operational
processes
Overlapping Functionalities
Non-interoperable Technologies
Overview – Problem- IT Outsourcing
Headcount-based model/harmonization of
software/ hardware etc. is insufficient
Enterprise
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Enterprises are expecting more- outcomebased pricing- enterprises focus on core
competencies, rest all as an end-to-end
solution by service provider
Overview – Toward Solution
Multiple IT Systems of an
Enterprise
Enterprise
1
IT Need 1
IT Need x
IT System 1
IT System x
Technology
Infra
Hardware
Infra
Technology
Infra
IT Plant
Hardware
Infra
Overview – Toward Solution
Multiple IT Systems of multiple
enterprises from same domain
Enterprise
1
IT Need 1
IT
System 1
Technology
Infra
Enterprise
2
…
IT Need 1
IT
System 1
Hardware
Infra
IT Plant 1
…
Technology
Infra
Hardware
Infra
IT Plant 1
Product Line of IT Plants
…
Overview – Problem – State of IT systems
Transformational needs addressed based on
experts’ knowledge
Enterprise
IT Need 1
IT Need 2
IT Need 3
…
IT System 1
IT System 2
IT System 3
…
Overview – Toward Solution
Transformational decisions do not view
enterprise holistically
Business
Enterprise
IT System
Infrastructure
Key Dimensions of Enterprise
MUST
represent
enterprise
in its
entirety
Overview – Toward Solution
Analysis World
Enterprise
Operational World
Overview – Toward Solution
reduce
Analysis World
Dependence on expert
knowledge
Address core issues
tackle
Enterprise
Operational World
Globally Sub-optimal design of
operational processes
Overlapping Functionalities
Non-interoperable
Technologies
Overview – Toward Solution
Analysis World
[Model-driven]
Enterprise
Operational World
[Model-driven]
Goals, operational
processes,
organizational
structure etc.
models closer to the
business domain;
questions regarding
efficacy of the as-is
state;
Path to desired to-be
state w.r.t given
property(ies)
Overview – Toward Solution
Analysis World
[Model-driven]
Enterprise
Operational World
[Model-driven]
Reduce
dependence on
expert knowledge
by
Enabling data and
model-driven
decision making
Overview – Toward Solution
Analysis World
[Model-driven]
Enterprise
Operational World
[Model-driven]
models of the
complete IT plant
that automate a set
of operational
processes through a
set of IT systems
ensuring correct
operation of the
enterprise both in
functional and nonfunctional sense
Overview – Toward Solution
Analysis World
[Model-driven]
Enterprise
Operational World
[Model-driven]
IT Plant product line
for multiple
enterprises in same
domain
Overview – Toward Solution
Analysis World
[Model-driven]
Enterprise
Operational World
[Model-driven]
IT Plant product line
for multiple
enterprises in same
domain
Overview – Toward Solution
Analysis World
[Model-driven]
Bidirectional
traceability;
use insights from
analysis world in
operational world;
Keep analysis
models updated
with operational
changes
Enterprise
Operational World
[Model-driven]
Overview – Toward Solution
Analysis World
[Model-driven]
Enterprise Specification
Enterprise Simulation
Enterprise
Research work
packages
IT Plant Specification
IT Plant Contract
Specification
IT Plant Testing
Operational World
[Model-driven]
IT Plant Deployment
Overview – Toward Solution
Analysis World
[Model-driven]
Enterprise
Enterprise Specification
Enterprise Simulation
Research work
packages
IT Plant Specification
IT Plant Contract
Specification
Operational World
[Model-driven]
IT Plant Testing
IT Plant Deployment
Overview – Toward Solution
Analysis World
[Model-driven]
Enterprise
Early
Results
Enterprise Specification
Enterprise Simulation
Ontological representation for
machine-processable and
analyzable enterprise models
Intentional and system
dynamics models for capturing
“Why” in enterprise
Operational World
[Model-driven]
Overview – Conclusion
Analysis World
[Model-driven]
Enterprise
Enterprises
Win-Win
Situation
Operational World
[Model-driven]
Service Provider
Thanks!!
Questions?
Questions
Products and Processes of Public Sector Bank
Specification & Analysis of
Enterprise Models
Enterprise Simulation
Domain
Models
Domain Models
IT Plant
Architecture
IT
Systems/Plant
Models
IT Systems
Architecture
Domain Model
Verification
IT Systems
Architecture
Reconstruction
IT Systems Models for
Change Agility
Adaptive Systems
Business Rule
Extraction
Operational World
[Model-driven]
Enterprise
Models
Analysis World
[Model-driven]
Research Challenges
Research Challenges
Analysis World
[Model-driven]
Specification and Analysis of Enterprise
Models
Goal
Machine-processable
enterprise models
Enterprise-wide analysis of
satisfaction of properties
Enterprise
Purpose
Enterprises are complex
interconnected systems of
systems
Use cases- directives,
objectives, policies and
regulatory compliances and so
on, scenarios of interaction
between enterprisesOutsourcing, M&A, etc.
Approach
Early results ontology
based enterprise
models, what-if/if-what
analyses
Techniques for
measuring properties,
quantification
Research Challenges
Analysis World
[Model-driven]
Enterprise Simulation
Goal
Capture behavior of Enterprise
Measure and Optimize the
effectiveness of Enterprise goals
by playing out what-if scenarios
Enterprise
Purpose
Optimize business process,
supply chains
Reduce risk , cost, improve
planning
Approach
Map Simulation Techniques w.r.t their
applicability
System Dynamics  Time
Petri Nets  workflows
State Machines  events
Simulate models in concert
Create mapping between simulation
models and EA models
Create DSL to simulate multiple models
in concert
Research Challenges
Domain [Functional] Models of IT Plant
Goal
Identify and define formal
modeling mechanism for IT
plant domain.
Enterprise
Purpose
Semantics
Traceability
Machine processing form
Multi organization context
Operational World
[Model-driven]
Approach
Identify model requirements
for IT Plant
Identify gaps between the
model requirements and
available Industry standard
models
Identify and define required
modeling elements based on
the assessment.
Pilot it with a suitable domain
Research Challenges
Domain Model Verification
Goal
Define formal mechanism to
maintain consistency of IT plant
modeling during refinement
Verify the IT plant model for specific
properties
Enterprise
Purpose
Consistent model refinement
Verification of desirable properties
of IT Plant specifications
Early detection of model bugs
Operational World
[Model-driven]
Approach
Examine the model refinement
requirement in IT plant
specification
Examine the existing model refine
techniques.
Adopt/enhance the existing
techniques to make them suitable
for IT Plant specification.
For model verification, define
formal mechanism to express
desirable properties of interest
Adopt/extend existing verification
techniques to verify IT plant specs
against desired properties
Research Challenges
IT Plant System Architecture
USP
Customer
Facing
Back office
Enterprise
X
√
Commoditized
√
√
Goal
Understand and model the
influence of business
products and processes on IT
plant architecture in SP
environment
Purpose
Approach
Improved IT Plant planning
Adaptive technology
architecture
Dynamic provisioning of
resources
Map a selected IT plant
landscape in the lines of its
products and processes.
Based on study arrive at the
impact of product and process
changes on the IT plant
architecture.
Operational World
[Model-driven]
Research Challenges
IT Plant Architecture
Goal
Enterprise
Arrive at IT plant architecture
catering to varying needs
Composition and decomposition
mechanisms for IT plant
architecture
Purpose
Varying needs of enterprises in
same domain
Customizations per enterprise may
increase app development and
management cost
Operational World
[Model-driven]
Approach
Investigate mechanisms,
techniques for
(de)composition for variability
capturing
Investigate effect of such
mechanisms on non functional
properties
Research Challenges
Architecture Reconstruction
Goal
Enterprise
Identifying predefined architectural
elements and relations among
them.
Re-construct architecture from the
source code using inputs from
system/application experts.
Purpose
IT plant Modernization
Most of the architecture/design
documents either outdated or unavailable
Operational World
[Model-driven]
Approach
Use program comprehension
techniques, refactoring, slicing, and
clustering to extract layers and
partitions from the source code.
Using machine learning techniques like
clustering embodied in Lattix tool or
other new techniques.
Research Challenges
Business Rule Extraction
Goal
IT plant Modernization
Extract inherent operational
and business Rules
Enterprise
Purpose
Enterprises are rule driven
Most these are legacy in nature.
To capture ever changing
regulatory policies and regulations
Operational World
[Model-driven]
Approach
Identify the constraints and calculation
from the legacy code
Formulate standard and application level
strategies
Apply data dictionary (meanings of
database variables)
Use comments to infer meanings to rules
Apply machine learning algorithms
Rules Representation
Variability
Visualization
Formal representation for verification
Extending SBVR kind of representation
Research Challenges
Models IT Systems
Goal
Model all aspects of IT systems
with inter-dependencies
Change Impact Analysis
Enterprise
Purpose
Approach
Change agility in IT systems
Multi-layered model
Correctness guarantees
Definition of change in terms
of model
Operational World
[Model-driven]
Realization thru Model
transformation
Research Challenges
Adaptive Enterprise IT Systems-
Goal
Enterprise
Monitor and adapt the functioning of
IT systems with respect to their nonfunctional requirements
Arrive at mechanism to implement
adaptation loop (MAPE)
Purpose
To meet SLAsTo reduce people
intervention
Approach
Modeling Adaptation for IT Systems
Construct reference architecture for IT
Systems using MAPE-k architectural pattern
Feedback Loops
Examine Execution Traces
Operational World
[Model-driven]
Investigate data logs and execution traces
to indentify what properties to monitor
and adapt
Language Support
Language to support adaptive software
development
Research Challenges
Using information
flows?
How to build enterprise
models ?
How to utilize/affect
transformation of IT systems?
Enterprise
How to model
business functions?
A language for modeling an
enterprise?
Which
abstractions? How
to verify that they
achieve intended
effect?
How to capture
combination of manual
AND automated steps of
business processes?
Domain-specific language
drawing on ideas from
event based paradigm,
multi agent systems
Globally Sub-optimal
design of operational
processes
Specification & Analysis of
Enterprise Models
Enterprise
Models
Enterprise Simulation
Domain
Models
Domain Models
IT Plant
Architecture
Overlapping
Functionalities
Non-interoperable
Technologies
Domain Model
Verification
IT Systems
Architecture
Reconstruction
IT Systems
Architecture
IT
Systems/Plant
Models
IT Systems Models for
Change Agility
Adaptive Systems
Business Rule
Extraction
Operational World
[Model-driven]
Dependence
on expert
knowledge
Analysis World
[Model-driven]
Summary
IT Plant Architecture
• What
– Arrive at an architecture for IT plant catering to varying needs of customers in
same domain
• Why
– Large enterprises needs plethora of applications to meet their needs.
– Needs of no two customers in same domain are exactly identical
– Various situations Service Providers need to service customer are
•
•
•
•
Deliver as-is solutions
Manage known , unknown configurations
Manage known , unknown extensions
Deliver parts and integrate existing systems
– Problems
•
•
•
•
Not designed to manage these scenarios
follow clone-n-own approach
Increased ADM cost
Customer not sure of certainty of meeting their needs
IT Plant Architecture
• How
– Modularity of IT plant
• Investigate mechanism, techniques for modular design for
– System of system scenario
– Multi-layer architecture
– Capturing Commonality and Variability
– Design time and Runtime variability
– Integration
• Investigate automation for COTS integration
• Evaluation of COTS for quality attributes
– Performance
– Reliability
– Configurabity
– Evaluation of NFR
Multiple IT Systems of multiple
enterprises from same domain
Product Line [Family] of IT Plants