The purpose of this activity is to analyze information requirements and group them into objectives based on commonality. This analysis is performed in preparation for development of the Enterprise Information Strategy.  

OVERVIEW

During this activity, Enterprise Engineering becomes familiar with all of the information requirements affected by the project. Specifically, the analyst studies the types of requirements (Policy, Control, and Operational), the timings of the requirements (Frequency, Offset, and Response Time), and the areas of the company involved (Functions and Positions receiving the information). Enterprise Engineering also determines what requirements are being implemented by any existing systems, in part or in full, and through what outputs (OD).

Information requirements are then grouped together into objectives (MI resources). This grouping could be random, but this may result in objectives with an inordinate scope and complexity. If properly organized, the objectives will be more compact and easier to evaluate.

There is not necessarily a one-to-one relationship between information requirements and objectives. One objective may satisfy many information requirements, and one requirement may be satisfied by many objectives.

There are fundamentally three considerations for grouping requirements:

1. By the Functional area being served by the information (e.g., Marketing, Manufacturing, Administration).

2. By information type (Policy, Control, and Operational). Obviously, Operational requirements must be satisfied before Control and Policy requirements.

3. By requirements being implemented by existing systems, versus those that are not.

After the information has been grouped into objectives, Enterprise Engineering performs a cost/benefit analysis for the information requirements in the grouping. The purpose of the cost/benefit analysis is to determine how the enterprise will benefit from having the information.  

STEPS IN EXECUTION

1. Enterprise Engineering collects all of the information requirements associated with the project. It is important that the engineer be reminded of the boundaries of the project. If not observed, the engineer may go beyond the scope and do more (or less) than is necessary.

2. Enterprise Engineering performs an analysis of each information requirement to determine what functions, positions, and existing systems (if any) are affected.

3. Enterprise Engineering groups information requirements based on commonality.

4. Enterprise Engineering defines objectives that will implement the requirements.

5. Enterprise Engineering prepares a cost/benefit analysis for the requirements for each objective. This analysis is posted to the objective. The result of this phase are formally documented Work Requests/Objectives (derived from MI resources in the IRM).