Skip to:

Implementation Planning Standard

Date Issued: July 1, 1994

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

Applicability: Who cares about this standard? All agencies and information resource community executives, managers and information resource management personnel.

When does it apply? Always

Audience (general, technical, executives, etc.):

Purpose of Standard: Planning must be conducted from agency, information resource community and project perspectives. The agency-wide and information resource community perspectives ensure that the right projects are done in the right sequence. The project perspective ensures that the projects are done properly.

The agency-wide and information resource community perspectives are provided by an implementation plan that takes into account business priorities and ensures that projects are completed in a rational sequence. The agency-wide and information resource community implementation plans determine priorities, and explain what will be added, replaced, modified or interfaced, and in what order.

Standard Requirements: Agencies and information resource communities must develop a one-to two- year implementation plan that identifies all projects, priorities and the sequence in which projects will be implemented.

Agencies and information resource communities must develop and manage government data consistent with the public information policies and requirements of the Minnesota Government Data Practices Act, to ensure public access to government data, and the protection of rights of subjects of government data. Identification of the classification of data and issues of statutory compliance shall begin during the early stages of strategic planning.

Agencies and information resource communities are responsible for ensuring that data is developed and managed consistent with the Minnesota Official Records and Records Management Acts. Identification of the retention and disposition requirements of data and what data are needed for public accountability shall begin during the early stages of strategic planning.

Agency funding strategies shall not conflict with statutory requirements and public information policy. At least annually, agencies and information resource communities shall review the sequence and purpose of the plans and, if necessary, modify them to account for changes in statutory policy that affect access to and dissemination of the organization's information resources.

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

  • The agency-wide information resource community implementation plan.
How will compliance be measured? Evidence of compliance will be subject to examination.

References: Source of Standard: Minnesota Office of Technology

Source of more information: Minnesota Office of Technology

Public Policy: Minnesota Statutes Chapter 13 (Minnesota Government Data Practices Act); Chapter 15.17 (Official Records Act); Chapter 138.17 (Government Records Act); and all other state and federal statutory requirements relating to data practices and records management.