The document discusses the key capabilities and needs of an Executive Information System (EIS), including consolidating data from multiple sources, capturing human feedback, correlating and analyzing data, providing visibility into key performance indicators (KPIs) through reporting and dashboards, and acting as a repository for performance data. It also outlines common issues with EIS solutions such as patchwork systems and rigid implementations. Additionally, it presents an ideal development approach for an EIS that allows for rapid, low-cost, and adaptable implementations without heavy reliance on IT resources. Finally, examples are provided of how the AMI approach can dramatically reduce development time and costs for sample EIS solutions in project management and auditing/compliance.

1. The Executive Information System
An EIS must address the following needs:
Consolidation of operational data from multiple
sources What is an EIS?
What is it to do?
Capture of human feedback and opinion whatdo that. address
THEN
to
it must
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
1

2. EIS Solution Classes & Capabilities
Lets walk through a typical
project and how the EIS
solution helps.
2

3. Common EIS Issues
Patchwork systems All these issues… again how doe
they play in A Day In The Life.
Cumbersome reports and dashboards should be first then
Probably
solution.
Rigid implementations
Poor communication between business
stakeholders and IT
Data lacks context and credibility
3

4. Typical Development Cycle
 The majority of development effort is in building core
application components
Are we talking about the
EIS itself or the projects
created under it?
Security Workflow Transaction
Component Component Component
Presentation Base
Component Application
Business
Reporting/BI Database
Logic
Component Component
4

5. Typical Development Cycle
Conventional application development cycles
are time consuming and costly
Everyone knows development is
Require highly skilled team members look at these issues
difficult. Just
and steps.
Hard to adapt to changing business needs
Prone to failure and cost overruns
5

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.
6

7. Conceptual Requirements
What would ideal EIS development look
like?
 Rapid implementation
So just Imagine…
 Low cost of ownership
 Highly adaptable without dependency on IT staff and skillsets
 Low maintenance burden
7

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!
8

9. AMI Development Cycle
Dramatically reduce development effort
No dependencies on IT
Wow! Even I could do that!
Right now!
9

10. Five steps to building an AMI solution
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.
Lets build a simple project
3. Determine the key performance indicators you want to
together
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.
10

11. Solution 1: Horizon BCBS
• Solution Type:
Project Management
• Business Objective: Now, for a more complex example.
Provide consistent and early visibility into problems to project
We’ve done it here!
managers
• Capabilities:
– Distribution of weekly role-specific assessments to distributed project team
members
– Analysis and presentation of results to project managers
11

12. Solution 1: Horizon BCBS
• Traditional Development vs AMI
Total Function Points: 343
Traditional AMI-based
Development Development
And boy, did we save time
Estimate* Actual and money! That solution
Development 834 40 was up and running
Effort (hrs) QUICKLY!
Test Effort (hrs) 167 7
Total Effort 1001 47
95.3% Reduction
*Based on 7 devlopers @ 84 FPMonth. C. Jones Software Methodologies
2011. Table 1: Software Schedules, Staff, Effort, Productivity
12

13. Solution 2: Lundbeck Pharmaceuticals
• Solution Type:
Auditing/Compliance
• Business Objective:
Provide an auditable, reliable record of communications do it in any
We can with
hospitals and clinics industry… because the
concept is the same!
• 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
13

14. Solution 2: Lundbeck Pharmaceuticals
• Traditional Development vs AMI
Total Function Points: 162
Traditional AMI-based
Development Development
Estimate* Actual Once again… speed to market
and a competitive advantage
Development 554 350 for YOU!
Effort (hrs)
Test Effort (hrs) 111 33
Total Effort 665 383
42.3% Reduction
*Based on 7 devlopers @ 84 FPMonth. C. Jones Software Methodologies
2011. Table 1: Software Schedules, Staff, Effort, Productivity
14