Issued: July 1, 1994

Effective: Agencies and information resource communities must comply by October 31, 1994.

Applicability: Who cares about this standard? All agency and information resource community executives, managers and information resource management personnel. When does it apply? Always.

Audience (general, technical, executive, etc.): Agency and information resource community executives, managers and information resource management personnel.

Purpose of Standard: A distribution model is critical to illustrating the physical distribution of data stores among the major business locations.

Standard Requirements: Before beginning any project, agencies and information resource communities must create a high level distribution model for the project. The distribution model must show the physical distribution of project data entities among the major business locations. The model must show the geographic locations of project data entities and user organizations.

Locations can be broad in coverage. For example, Duluth may contain multiple facilities, but could be considered a single business location.

Examples of entity distribution are:

• Centralized: Entities are resident at one location; one form and one content will be at one location.
• Replicated: Entities are physically duplicated at two or more locations; same form and content will be in all places.
• Partitioned: Entities are separated and distributed to two or more locations; same form will exist in each location, but content will differ.

Compliance: What constitutes compliance? Agencies and information resource communities must have readily available for examination:

• A chart or diagram showing geographic locations of project data entities and users.

How will compliance be measured? Evidence of compliance will be subject to examination.

References: Source of Standard: Minnesota Office of Technology Statewide Information Resource Management Policies
Source of more information: Minnesota Office of Technology

Public Policy: Not applicable.