EiiIDS Scheer ArchitectureDriven Solution Selection Methodology Presented by Al Baharmast, Ph'D'

1
Eii/IDS ScheerArchitecture-Driven Solution
Selection Methodology Presented byAl
Baharmast, Ph.D.
2
Agenda

• Architecture-Driven Solution Selection A
  Methodology Overview
• Methodological Foundation
• An Expedient Approach to Developing a
  Solution-Focused Enterprise Architecture
• Distinctions Between the Applications of Gap-fit
  Analyses
• Solution Selection Methodology as a Derivative of
  Architecture Evolution Theory
• Architecture-Driven Solution Selection A
  Practical Review of Architecture Development
• A Two-Pronged Architecture Development Approach
• Function Decomposition Defining the Solution
  Scope
• Business Process Scenarios Testing the Breadth
  of Integrated Capabilities
• Three Supporting Elements of Solution Selection
  Analysis
• Building Architecture Outputs for Requests for
  Proposal and Scripted Demonstrations
• Conducting an Architecture-Centric Gap-Fit
  Analysis
• Transitioning to an Implementation Architecture

3
Architecture-Driven Solution Selection A
MethodologyOverview
4
General Approach and Applications of
Architecture-Driven Solution SelectionMethodolog
ical Foundation Standard Software Applications
execute business processes either explicitly or
implicitly increasingly becoming explicit!

• Definition of Standard Software
• A class of information systems that are modular
  (e.g., Financials, Human Resources,
  Manufacturing, etc.) but when implemented as a
  collection of modules, are integrated.
• Includes ERP, APS, SCM, CRM solutions

• The value of utilizing that this explicit
  expression of process as a means of conducting
  gap analysis, enabling solution implementation
  and developing a solution-based enterprise
  architecture, should be obvious.
• Organizations considering solution selection are
  looking for -
• An expedient architecture development approach
• Identify a select set of business processes and
  solution requirements
• Not reasonable to test a ten thousand set of
  requirements
• An architecture that will endure through the
  implementation
• Variations of this methodology used in and
  developed as a result of consulting engagements
  in complex organizations such as the U.S. Air
  Force and the U.S. Army

5
Gap-Fit Analyses

• Gap-Fit as a Proof of Concept Can Standard
  Software (e.g., ERP) solutions generally satisfy
  our operational requirements? To what extent?
  Where might they fall short? (High level)
• Gap-Fit as an Instrument for Product
  Differentiation/Selection Which solution meets
  most of our operational requirements? Where does
  it fall short? (Low level)
• Gap-Fit as Instrument for Defining Scope
  Extensions Can we extend the operational
  support footprint of the solution? Which new
  functional activities (beyond the original scope)
  can the solution support and which legacy
  applications can it replace? (Low level)

6
Architecture Evolution
Inputs
Inputs
As-Is Architecture
Strategic Goals Objectives
Policy Considerations
Solution Selection Methodology --- Derivative
of Well-Established Architecture Evolution Theory
Target Architecture
Standard Software-Enabled Best Practices
Industry Best Practices
Gap-Fit Analyses
SME Institutional Knowledge
Value/Cost Factors
Solution Selection
To-Be Architecture Conversion
Vendor Responses
Technology Economic Risk Factors
Implementer Selection
Manage To-Be Enterprise Architecture
Phasing Migration Plan
Policy Descriptive Compliance Architectures
7
Architecture-Driven Solution Selection A
PracticalMethodologyReview
8
Solution Selection Architecture Development

• Two-pronged architecture development approach
• Generic Standard Software Function Decomposition
• In terms vendors can readily understand
• Bounds the solution scope
• Equates well to application modularization
• Detailed Business Process (End-to-End) Scenarios
• More granular and in terms the clients Subject
  Matter Experts can understand and relate
• Expression of the customers functional
  requirements
• Requires best practices guidance (industry
  solution)

9
Function Decomposition
Defined in Generic Solution Terms
A generic function decomposition identifies all
the integrated solution capabilities available in
advanced ERP software suites. APS, CRM, SCM
solution capabilities are a sub-set of these
functions.
10
Function DecompositionTop-Level Functions
Defense Vertical Example
11
Resources Used in Developing Function
Decomposition

• Internal Eii and IDS-Scheer expert resources
• APICS Dictionary
• Oracle, PeopleSoft (JDEdwards), SAP, I2,
  Manugistics, and Xelus Solution Documentation
• Validated by industry experts

12
Example Functions/Definitions
13
Function Decomposition Scoping
The function decomposition bounds the scope of
the solution suite.
14
Function Decomposition and RFP Products
Decomposition
ERP Function Set
Scope
RFP Document
15
Develop ClientBusiness Process Scenarios

• Definition of Business Process Scenario
• A business process scenario traces the entire
  value-added chain of activities associated with
  the delivery of a specific service or product
  through all relevant processes in an enterprise.

Defined in Clients Operational Terms
Select core and unique business process scenarios
- Current state scenarios enriched by Subject
Matter Expert opinions on opportunities for
process improvement and expert recommendations
for introduction of best practices.
16
Scenario - DetailedView
Requisition, Acquisition and Contract Management
Scenario
17
Scenario - Detail Explosion
Requisition, Acquisition and Contract Management
Scenario
18
Scenario - RequirementsExample
Requisition, Acquisition and Contract Management
Scenario
19
Client-Specific Business Scenarios
Generic Scope Definition
20
Functional CapabilitiesThree Elements of Analysis
Assessing Functional Capabilities
1. Written RFx Responses
2. Scripted Demonstrations
3. Inference Testing
21
RFP Demo Products
Business Scenarios
Function Decomposition
RFP Response Required
RFP Response Required
Scripted Demo Required
22
RFPVendor Response Matrix
23
Distinguishing Solution Efficiency Drivers
24
Weighting Scoring
Good Resources for Weighting Analytic Hierarchy
Process (AHP) and Expert Choice
25
Scripted Demo Output
26
Scripted Demos

• Not a reliable resource if used as the primary
  criterion for selection
• Subject to a great deal of bias and mistaken
  impression
• Should be used primarily as a means of
  validating RFP responses
• Also useful in assessing applications ease of
  use and general chemistry

27
Evaluating Vendors RFPResponses Scripted Demo
Presentations
28
Gap-Fit Analysis Outputs
Architecture reports are generated in order to
present information on gaps and fits on multiple
levels, i.e. all models, per function area or per
scenario.
Graphical representation of the degree of match
between the software solution and the
requirements and functions is also presented
Color codes highlight problems
29
Transition to anImplementation
ArchitecturePost-Selection Tasks

• Upon Solution Selection
• Convert architecture to solution objects
• Produce implementer selection RFP outputs (where
  relevant)
• Requires that the implementer address the
  solution design in the same manner as the
  solution vendor
• Establishes a requirement for the implementer to
  commit to the architecture they are proposing
  the response to the RFP will create a
  contractually-defined baseline for which the
  implementer will be held responsible
• Expand architecture footprint beyond select
  scenarios
• Define all relevant processes
• Align across domains
• Use scenarios to validate application
  configuration and customizations (reports,
  interfaces, workflow)
• Foundation for integration testing
• Establish management and monitoring environment