Summary
This chapter provided a review of each of the different components of information governance, as follows:
- Information governance organizational component—The information governance organizational component is the “people” aspect of the discipline that sets the policies for information governance and maintains a staff to support those policies in managing the development and ongoing usage of corporate information.
- Data stewardship component—Data stewards support, maintain, and execute the policies and procedures instituted by the IGC.
- Data quality management component—Data quality management is the definition, supervision, and when necessary, renovation of data to the business and technical ranges.
- Metadata management component—The metadata management component is one of the process and technology aspects of information governance that captures, versions, and uses metadata to understand organization data.
- Privacy and security component—The privacy and security component covers all three of the people, process, and technology aspects of information governance to address who has create, read, update, and delete privileges of organizational data.
- Information life cycle management component—Information life cycle management covers the process and technology aspect of information governance that addresses the entire life cycle of a set of data, from creation, retention, and deletion.
Each of these components is threaded in each of the EIM functions, transactional processing, MDM, and BI.
The policies and requirements for each of the components must be instantiated to achieve the context and quality of the data needed for transaction and analytic processing within the organization.
This chapter defined each of the information governance components that need to be performed to achieve the context and quality of the data needed for transaction and analytic processing within the organization. Chapter 2, “Other Core EIM Functions,” reviews, at a high-level, the transaction, operational, and analytic functions of EIM so that you can understand where the requirements for the information governance components will interface.