"PRIDE"-Enterprise Engineering Methodology (EEM)

PRIDE

-EEM

Enterprise Engineering Methodology
PHASE 4 - ENTERPRISE INFORMATION STRATEGY (EIS)
ACTIVITY D - PREPARE ENTERPRISE INFORMATION STRATEGY

EXAMPLES TOOLS & TECHNIQUES FUNCTIONAL MATRIX CHECKLIST SUPPORT FORMS

TRANSLATE THIS PAGE TO... Chinese (simple) Japanese Dutch French German Italian
Free Translation courtesy of ALS Chinese (traditional) Korean Portuguese Russian Spanish

CONTENTS

This section contains the following:

BUSINESS PURPOSE

OVERVIEW

STEPS IN EXECUTION

SUPPLEMENTAL INFORMATION (separate sections)
- Phase 4 Review Checklist

BUSINESS PURPOSE

The purpose of this activity is to develop an Enterprise Information Strategy (EIS) that will satisfy the needs of the enterprise. This represents the culmination of considerable effort and preparation by Enterprise Engineering.

OVERVIEW

The underlying rationale behind the development of the Enterprise Information Strategy is how the enterprise values information. When the requirements were grouped into objectives, a cost/benefit analysis and delivery date was developed. This became the basis for the cost/benefit analysis and delivery date for the resulting projects and will ultimately become the criteria for ranking objectives and projects.

Based on the delivery date and cost/benefit analysis, each objective is assigned a priority "weight" value. The weight defines how much the enterprise values the objective and is based on a scale from 01 (high) to 99 (low). Based on their "weight," the objectives are then ranked in priority sequence, using a scale from 001 (high) to 999 (low). This ranking becomes a part of the Enterprise Information Strategy.

The objective rankings are then used to determine the ranking of all projects. Here, the average ranking of all of the objectives that a project implements is used to establish the project ranking. For example:

OBJECTIVE RANKING AVG OBJ RANK PROJECT PROJECT RANK MI-00001 1 14 PD-00320 3 MI-00010 25 MI-00020 16 MI-00040 12 28 PD-01216 4 MI-00345 44 MI-00029 2 6 PD-01011 1 MI-00042 5 MI-00021 11 MI-00132 7 7 PD-01211 2

In this small example, you see that the objective rankings have a direct effect on how the projects are ranked. What this means is that as information requirements and objectives change in priority, the projects, in turn, will change. This concept promotes the fact that the Enterprise Information Strategy is a "living" document and is constantly undergoing change.

Both the proposed objective and project rankings are compared to existing priorities and the Business Plan. Adjustments to priority "weighting" and rankings are implemented accordingly.

A textual justification for the rankings is prepared by Enterprise Engineering. The text explains the rationale for the rankings, what effect it will have on the existing Enterprise Information Strategy (changes, additions, deletions), and how it will accommodate the Business Plan.

The Phase 4 Manual contains the following items:

Phase Cover Page - including a Table of Contents with a distribution/approval list.
Current Objective Ranking Report - listing the current ranking of MI priorities.
Current Project Ranking Report - listing the current ranking of PD priorities.
Business Plan - as specified in Phase 1.
Enterprise Information Strategy - a textual explanation of the proposed new EIS, supported by the new rankings.
Matrices - used to answer questions and show how the EIS was derived. Included are tables showing relationships between:
- Information Requirements/Systems (IR/Systems)
Printed descriptions are also available for reference:
- Work Requests/Objectives (as prepared in Activity B)
- Project Scopes (as prepared in Activity C)
Phase Review Checklists - specifying acceptance criteria to evaluate the deliverables mentioned above.

STEPS IN EXECUTION

Enterprise Engineering gathers all of the pertinent specifications for development of the Enterprise Information Strategy. This includes the current Business Plan, Work Requests/Objectives, Project Scopes, and the current Enterprise Information Strategy (MI and PD priority rankings).

Enterprise Engineering develops a series of supporting matrices showing the relationships between functions, positions, information requirements, objectives, projects, and systems.

Enterprise Engineering evaluates the current status of all objectives and priorities.

Enterprise Engineering develops a priority ranking of objectives. This is based on the "weight" of the objectives and due dates.

Enterprise Engineering develops a priority ranking of projects. This is based on the average ranking of the objectives that each project implements.

Enterprise Engineering evaluates the proposed objective and project rankings in view of the Business Plan and matrices. It is also reviewed with Project Management for consideration. Priority adjustments are implemented as required and the EIS justification is written.

Enterprise Engineering and Project Management verify that all of the elements of the Enterprise Information Strategy have been considered and assemble a preliminary Phase 4 manual for inspection.

The Phase 4 manual is reviewed by Quality Assurance who verifies that it has been prepared according to installation standards. Adjustments are implemented by Enterprise Engineering accordingly.

The Phase 4 manual is reviewed by Enterprise Resource Management for approval. Adjustments are implemented by Enterprise Engineering accordingly. Project Management and Enterprise Engineering brief Enterprise Resource Management in detail about the proposed EIS.

Project Management schedules a Phase 4 review meeting with Executive Management and Information Resource Management. Copies of the Phase 4 manual are distributed prior to the meeting.