Post on 30-Jun-2015
transcript
1
The Executive Information System
An EIS must address the following needs:
Consolidation of operational data from multiple sources
Capture of human feedback and opinion
Correlation and intelligent analysis of this data
Visibility into meaningful KPIs through reporting and dashboards
A repository of performance data
The ability to transform data into insight
What is an EIS?What is it to do?
THEN what it must address to do that.
2
EIS Solution Classes & Capabilities
Lets walk through a typical project and how the EIS solution helps.
3
Common EIS Issues
Patchwork systems
Cumbersome reports and dashboards
Rigid implementations
Poor communication between business stakeholders and IT
Data lacks context and credibility
All these issues… again how doe they play in A Day In The Life. Probably should
be first then solution.
4
Typical Development Cycle
The majority of development effort is in building core application components
Security Component
Workflow Component
Transaction Component
Presentation Component
Base Application
Reporting/BI Component
Database Component
BusinessLogic
Are we talking about the EIS itself or the
projects created under it?
5
Typical Development Cycle
Conventional application development cycles are time consuming and costly
Require highly skilled team members
Hard to adapt to changing business needs
Prone to failure and cost overruns
Everyone knows development is difficult. Just look at these
issues and steps.
6
Typical Development Cycle
However, real value and insight comes from custom business logic, not the underlying platform
Programming is not the critical factor. The uniqueness of your business is the critical factor.
7
Conceptual Requirements
What would ideal EIS development look like?
Rapid implementation
Low cost of ownership
Highly adaptable without dependency on IT staff and skillsets
Low maintenance burden
So just Imagine…
8
Characteristics of an ideal EIS
A “black box” that allows you to define a range of EIS solutions without programming
We’ve created a machine to take your project from IDEAS to REALITY. And YOU are in
control!
9
AMI Development Cycle
Dramatically reduce development effort
No dependencies on IT
Wow! Even I could do that! Right now!
Five steps to building an AMI solution
10
1. Define the operational data and human feedback you want to capture.
2. Identify the checklists, best practices, rules, and boundaries your organization wants to enforce.
3. Determine the key performance indicators you want to measure and manage.
4. Design the report layout you would like and dashboards you need to maximize visibility.
5. Define the metrics to be stored in your performance repository.
Lets build a simple project together
Solution 1: Horizon BCBS
11
• Solution Type: Project Management
• Business Objective:Provide consistent and early visibility into problems to project managers
• Capabilities:– Distribution of weekly role-specific assessments to distributed project
team members– Analysis and presentation of results to project managers
Now, for a more complex example.
We’ve done it here!
Solution 1: Horizon BCBS
12
• Traditional Development vs AMITotal Function Points: 343
Traditional Development Estimate*
AMI-based Development Actual
Development Effort (hrs)
834 40
Test Effort (hrs)
167 7
Total Effort 1001 47
*Based on 7 devlopers @ 84 FP\Month. C. Jones Software Methodologies 2011. Table 1: Software Schedules, Staff, Effort, Productivity
95.3% Reduction
And boy, did we save time and money! That
solution was up and running QUICKLY!
Solution 2: Lundbeck Pharmaceuticals
13
• Solution Type: Auditing/Compliance
• Business Objective:Provide an auditable, reliable record of communications with hospitals and clinics
• Capabilities:– Weekly assessments for team members collecting actuals from each
person, aligned to person-to-person quotas– Sorted results by geography and program roll-up capabilities
We can do it in any industry… because the concept is the
same!
Solution 2: Lundbeck Pharmaceuticals
14
• Traditional Development vs AMITotal Function Points: 162
*Based on 7 devlopers @ 84 FP\Month. C. Jones Software Methodologies 2011. Table 1: Software Schedules, Staff, Effort, Productivity
42.3% Reduction
Traditional Development Estimate*
AMI-based Development Actual
Development Effort (hrs)
554 350
Test Effort (hrs)
111 33
Total Effort 665 383
Once again… speed to market and a
competitive advantage for YOU!