13th European Conference on eGovernment – ECEG 2013 1 | Page 432

Denisa Popescu et al.
Information Management( EIM) program. These can be applied to enable information integration in government.
Figure
1: EIM conceptual reference architecture
Table 1: Enterprise information management roadmap with representative components and actions Building Block Description Actions Vision & Strategy
How is information perceived across ministries and agencies? How is information managed: ad hoc, departmental or enterprise wide?
Governance What are the decision rights and accountabilities for managing information? What is the service model for delivering common shared services?
Government Leadership recognizes information as a strategic asset, sponsors and champions the Enterprise Information Management strategy. There is high‐level sponsorship for an EIM program with the appropriate level of funding.
Policies and standards are defined to achieve standardization and consistency. Governance councils and steering committees work together to resolve cross‐functional management issues. Common Shared Services arrangements are defined and implemented. Data stewardship is mainstreamed.
1. Define, communicate and adopt an Enterprise Information Policy and Strategy. 2. Clearly define, communicate and adopt the data management roles and responsibilities of all staff and custodians of institutional information assets. 3. Increase internal awareness of data management. 4. Formalize and fund an EIM Program to address the needs of all stakeholders in a coordinated fashion. Information Management Policy, Guidelines and Procedures Periodic review and updates
Information Stewardship Program Information Stewardship role formalized in relevant job accountabilities across Ministries and Agencies Add responsibilities for information and data management to business and IT roles.
Process
How are the information lifecycle processes, such as stewardship, formalized?
Guidelines for archiving data and data retention periods are enforced. There is a process to collect metadata as part of a project reuse strategy. Policies and mandates are well documented and understood. Standards for information quality are defined and there are procedures in place to monitor quality on a regular basis. Content Management policies are defined and enforced at the time of document creation.
Mainstream IM in SDLC Data Management Plan developed for each project. Formalized data change management processes with clear accountabilities for QA, sign‐off and hand‐off. Provide training on data management to all staff. Mainstream change management processes with clear points for processes in place for hand‐off, sign‐off and QA. Audit and reporting tools in place to monitor compliance to standards and process deviations.
410