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 data model is critical to sharing information and ensuring that data support the information needs of the organization. High-level data models help an agency or information resource community manage and share its data effectively. Models collectively describe project data and how they are used to support business functions.
Standard Requirements: Before beginning any project, agencies and information resource communities must create a high level data model that shows the project's data entities and relationships. An entity is a person, place, thing, concept or event about which data are or can be recorded. A relationship is an important association between one or more entities that provides some relevant business information.
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 advance during data modeling. The effects of the data's classification and attention to compliance with statutory requirements shall continue through design, installation and maintenance.
Organizations 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 advance during data modeling and continue through design, installation and maintenance.
The high level data model must address legislative policies on public accountability, public access to government data, the rights of subjects of government data, and records management.
Compliance: What constitutes compliance? Agencies and information resource communities must have readily available for examination:
A high level entity/relationship diagram for the project.
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: 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.