IM Planning Template - Services publics et ...



Information Management Planning Template

For Project, Service or Product

Prepared by: Knowledge & Information Management Directorate (KIMD)

Organization: OCIO, ITSB

Date: April 2010

English version EDRM #: 556160-v4

French version EDRM #: 1159975

Table of Contents

1. Introduction 1

Executive Overview 1

Objectives of the Project/Service/Product 1

Purpose 1

Scope 1

Organizational Capacity 1

2. Information Management Roles and Responsibilities 2

3. Information Management Plan 3

Information Management 3

3.1.1 Data, record & document management 3

3.1.2 Information flow 3

3.1.3 Metadata 3

3.1.4 Document versioning 4

3.1.5 Classification and naming 4

3.1.6 Storage medium 4

3.1.7 Access & Security 4

3.1.8 Retention 5

3.1.9 Disposal 5

Knowledge Management (KM) 5

3.1.10 Strategy and Tools 5

3.1.11 Mitigation Practices 5

3.1.12 Migration Plans 6

4. Considerations and Processes 6

Corporate or Legislative Considerations 6

4.1.1 Considerations 6

4.1.2 Other? 6

Document Scanning 6

4.1.3 Requirements & Process 6

5. Performance Indicators 7

Risk Management Strategy for Information Management 7

Performance Indicators for Successful Information Management 7

Appendix 1 - Policies, Acts and Directives: 8

Appendix 2 – Roles and Responsibilities: 9

Appendix 3 - Definitions 11

Appendix 4 – Storage Medium 12

Document Change Control

|Revision Number |Date of Issue |Author(s) |Brief Description of Change |

|Draft vs I |July 2008 |Rachel Bergeron |Initiation |

|Draft vs II |November 09 |Mario Charette |Alignment with NPMS PM Framework |

|Draft vs III |April 2010 |Mario Charette |Minor modifications |

| | | | |

| | | | |

| | | | |

| | | | |

| | | | |

| | | | |

Information Management Plan review and approvals

|Prepared by: |

| |

| |

|Submitted by: |

| |

| |

|Input received from/reviewed by: |

| |

| |

|Accepted by: [Director level or above.] |

| |

| |

|Document submitted to the Knowledge and Information Management Directorate (at kimd.dgci@tpsgc-pwgsc.gc.ca) on: [date.] |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

Introduction

Executive Overview

The Government of Canada (GC) creates vast amount of information that enables the delivery of programs, services and products to Canadians or on behalf of Canadians, supports the reporting of results to Parliament, and ensures accountability and transparency of actions. As these information resources are valuable and critical factors in the success of any endeavor, structured planning of their management must occur to meet corporate goals and to successfully deliver programs and services.

This document describes the information management processes that will be used within the (name of project/product/service). These processes are drawn from federal legislation, policies, directives, standards and practices that apply to the administration and management of information and technology across government and within PWGSC.

[Insert a paragraph specifically covering the executive overview/summary of the project/product/service.]

This is a living document and will be reviewed and updated on an ongoing basis for projects or semi-annually for programs and services to ensure consistency with IM standards and to take into consideration new storage mediums, tools and IM solutions.

Objectives of the Project/Service/Product

[Define the objectives by providing any additional information on the project/program/service and provide the reference to the information source where the project/program/service is described e.g. Project Charter, web site link.]

Purpose

The purpose of this document is to:

• Identify all information assets related to the (name of project/product/service);

• Facilitate compliance with government policy and standards, using best IM practices and Library and Archives Canada requirements for the disposition of GC records;

• Facilitate the safeguarding, storage and retrieval of information resources generated in the performance of this project; and

• Establish a balanced IM solution for the (name of project/product/service).

Scope

Only information assets concerning the (name of project/product/service) will be defined within this document. Information assets consist of documents that describe the delivery of a project/program/service; records decisions and actions; provides evidence of financial and legal transactions; has policy, program and procedure implications; is needed to account to Parliament and to the public; or may have historical value. This information can take on many forms including paper, electronic, photographs and film, digital images, video, audio, and microfiche.

Organizational Capacity

[Describe the organization’s current capacity to manage the information assets, which will be generated from this project/service/product. Discuss: IM capacity, awareness, organizational culture, changes management and external influences.]

Information Management Roles and Responsibilities

[Provide context. Include governance structure, org chart and/or project reporting matrix.

Define roles and responsibilities of committees and/or working groups and link into the PWGSC governance structure.]

Because we all create, collect and receive information as part of our day-to-day work, we are all responsible for effectively managing that information while it’s in our care and custody. Employees/Team members will need to:

▪ Document business activities and decisions.

▪ Comply with institutional Information Management (IM) policies and standards, using approved tools, systems and procedures.

▪ Organize, file and store information, ensuring it’s easily accessible when needed to make decisions and to support program and service delivery.

▪ Share and re-use information to support collaboration and facilitate business operations, respecting all legal and policy requirements.

▪ Protect sensitive information, providing or restricting its access in accordance with law and policy.

▪ Manage information with long-term or historical value to support legislative and policy requirements that govern its retention and disposal.

▪ Protect and preserve information critical to business resumption.

▪ Comply with official languages and privacy requirements.

See appendix 2 for the key roles and their responsibilities

Information Management Plan

Information Management

The following key principles of Information Management promote the efficient use of institutional resources, make information easier to find in the future, and ensure its protection and preservation – all in accordance with business, legal and policy requirements:

▪ Avoid collecting duplicate information.

▪ Share and re-use information, respecting legal restrictions.

▪ Information should be complete, accurate, current, relevant, and understandable.

▪ Support access to information, respecting privacy, policy and legal requirements.

▪ Safeguard information against unlawful access, loss and damage.

▪ Preserve information of historical value.

The following diagram illustrates the seven (7) stages comprising the life cycle of information. [pic]

Only information, which has been deemed an asset (of business value), will be documented as part of this IM Plan and managed throughout its lifecycle.

Reference documents and information of a transitory nature will not be documented as part of this IM Plan. These include: information that has no business or service delivery value; has no legal, fiscal administrative, operational or historical value; and is needed only for a limited period of time. Examples of transitory information include: duplicate documents used for reference; external publications; emails of an informative nature (FYI…); generic broadcast messages; and personal information.

This plan has been segregated into several elements relevant to information management. Each requirement will identify parts of the management plan.

The workbook which houses all of the defining elements related to our information assets is located in Appendix [_X_] . The points below describe how each element will be actionned and managed over time.

3.1.1 Data, record & document management

[Define all the data, records and documents produced during the life of the project, service or product.

Link to the Appendix __X__.]

2 Information flow

[Define the flow of each information type and/or element (i.e. data, records and documents), ensuring that the point of creation and the point of storage as well as the entire flow is clearly identified (recommend using a flow diagram).]

3 Metadata

Define the metadata elements for each data set, records and documents listed above, including:

• a brief description

• ownership

• storage medium

• date of creation

• last edited date

• linkages between each elements

• source of origin

• usage

• target audience

• target date for archival

• target date for disposition

Note: Link to Appendix __X__ – Document Description Chart for all required metadata elements.

Please see the Government of Canada Records Management Metadata Standard (GC RMMS) at to help populate this table.]

4 Document versioning

[Define the approach and method that will be used to manage documents/records versioning.

Link to the Appendix __X__.]

5 Classification and naming

[Identify the classification plan that will be used.

Define the methodology used to name files (including databases, applications, documents and records).

Example: (for EDRM documents) Subject-Type_Specifics_Reference Period (if applicable)

Concrete example: PRJ-Project Charter_CLF 2.0 Project_June 2008

Note: Web based applications/databases must confirm to Common Look and Feel requirements.

Note: File naming convention must conform to Recordkeeping and Official Language policies.

Refer to DP044-Records Management & Information Holdings]

6 Storage medium

[Define the storage medium, which will be used in the context of this Project/Service/Product‘s lifecycle.

|Storage Medium |Rational for use |Location |Resumption Plan Identified|Other Information |

|Example 1: Web site |Provides information on our |PWGSC-ITSB hosted |Internet City provides | |

| |product/service | |12X5 support at 99.5% | |

|Example 2: EDRM |Used to house and provide |PWGSC-ITSB hosted |Part of service provision |Available via Web from: |

| |access to all draft and final| |– 12X5 support at 99.5% | |

| |version of documents | | | |

|Example 3: Filing Cabinet | |PWGSC-ITSB | | |

|Example 4: E-mail | | | | |

| | | | | |

| | | | | |

| | | | | |

7 Access & Security[1]

Information law and policy define the right of access to government held information and its exemptions (i.e.: The Access to Information and Privacy Acts). Beyond being available, information must be easily and conveniently accessible with appropriate controls in place to ensure access is authorized and to protect privacy and confidentiality. It should be available for access in alternate formats and through channels responsive to user needs and consistent with government communications requirements, such as official languages and federal identity.

[Provision must be made to ensure information remains available and accessible over time. This may include migration strategies to provide for changes to technology. Define the measures that will be taken and any mitigation strategy – key elements to describe: information holdings, channel & access options, access rights & limitations, user interface, discovery tools, disseminating information and usability over time.

Refer to: PWGSC – DP002-Policy on Access to Information and Privacy Acts

You may also wish to refer to the SAS on Best Practices - Access Rights and User Security at .]

In addition, information must be protected against unauthorized access, modifications, and disclosure. Provisions must be made to ensure that the integrity of information is not lost or compromised through accident, error, or malicious intent and that access is not inhibited through denial of service or other attacks. Audit trails and controls are required to provide a history of events so that parties may not deny participating in a transaction and so that information may be recovered in the event of loss or corruption. All public servants must comply with the Government of Canada Security Policy.

[Define security requirements and access rights in terms of who has access to information what information and for what purposes.

Define where and how to get the information, including the necessary workflow;

Define data integrity measures and mitigation.

Define recovery measures in the event of accident, service denial, attack or other.

Identify Business Resumption Plan and where this document can be found, who has access to it, who is responsible for updating it and its current lifecycle.

Recommend working with IM Specialists to ensure essential information can be made available and business resumed in the event of information loss or compromise.

Refer to:

PWGSC – DP052-Corporate Security Program

PWGSC – DP051-Departmental Security Program

PWGSC – DP014-Protection of Personal and Private Information in the Workplace

Key Elements: Availability & Integrity, Accessibility, and Confidentiality.]

8 Retention

[Having identified the required information, determine:

• How long the information will be required to directly support delivery activities;

• Protection of essential records so that if information critical to running government suffers loss or is compromised, it may be recovered and business can resume.

• How to preserve and protect it so that it is available when needed. This may include environmental controls to ensure preservation of the media on which the information is recorded, and redundant storage strategies, such as off-site storage. This information may be required for disaster recovery and business resumption purposes.

Information created or obtained through collection, capture or receipt must include metadata that provides important business context to associate the information with the business activity(s), function(s), and transaction(s) to which it pertains. Information should be organized to provide clarity, context, and convenient and timely access. Generally, an institution-wide information classification scheme will be in place to support this. Define the classification scheme addresses the full breath of the information access requirements and that mechanisms are in place to tag information with the appropriate classification(s).

Refer to DP044-Records Management & Information Holdings

Key Elements: Information Collection & Classification, Information Storage and Preservation, Information Protection, Information Retention]

9 Disposal

[Define approach, processes, disposition authority and schedule for each data type, records and document. Consider the business and historical value for each document as part of the disposition schedule. Identify documents/records that will be transferred to another entity. Summarize the document in this section and link to the details in Appendix A – Document Description Chart.

Official documentation such as documents of business or historical value should be submitted to the departmental library, to be considered as corporate assets.

Surplus publications should be forwarded to Library and Archives Canada – contact PWGSC Library Services for assistance (refer to DP066-Departmental Library Services).

** Refer to your Branch’s Record Disposition Authority and Retention Schedule(s) - contact PWGSC Records Management for assistance.]

Knowledge Management (KM)

Knowledge Management (KM) comprises a range of practices used by organizations to identify, share and document knowledge.

[Define the context that will apply.]

1 Strategy and Tools

[Define the KM strategy, practices and tools that will be used to manage the knowledge. Consider the knowledge requirements of new and existing employees – what should they know before they can be productive members of the team; what should happen when an employee/contractor leaves the team?

Define communication mechanisms and strategy. Link to the Communication Plan and the Overall Unit Learning Plan.]

3 Mitigation Practices

[Define KM practices to mitigation knowledge gaps or loss. Define plans for succession and resourcing backfills. Link to Detailed Human Resources Plan.

During the project lifecycle, the organization needs to focus on sharing and utilizing all available knowledge. The following knowledge sharing practices are especially helpful in the case of employee turnover, or even to quickly bring external resources up to speed on the project.

Direct Learning: “Hands-on” experience and/or cross-training.

Knowledge visualisation: Diagrams, flow charts, storyboards, and dynamic presentations.

Seminars and Webinars: Formal event geared towards knowledge delivery. The latter can deliver the message in an ongoing fashion and allow recorded discussion (on the web).

Newsletters & Journals: Typical communication channels that allow the transfer of knowledge in smaller, incremental units that are easier to absorb and retain.]

4 Migration Plans

[Define the strategy and action plan for tacit documentation of knowledge to allow for sharing and management purposes.]

Considerations and Processes

[Define overall processes and standards that will be applied.]

Corporate or Legislative Considerations

[Provide context.

Example: Official Languages.]

1 Considerations

[Define Project/Service/Product based considerations.

Example: context of Official Language policies and requirements.]

2 Other?

[Provide context and rationale for considerations.]

Document Scanning

[Provide context.]

1 Requirements & Process2

[Define necessity and process to follow. Link back to section 2 above concerning storage and lifecycle.

Example: Items that could be scanned include paper copies and signed documents. The process involves sending the document to the Branch/Unit “Information Management Group”. The Branch/Unit “Information Management Group” will scan the document to convert it to PDF format. The PDF electronic version will be stored in E-DRM. The hard copy will be considered as the authoritative source and will be kept in the filing cabinet under the management of __________________________.

Note: Both the electronic and the paper versions must be documented and managed as part of an IM Plan.]

Performance Indicators

[Define the strategy that will be used to measure success against the IM Plan.]

Risk Management Strategy for Information Management

[Define the Risk Management Strategy.]

|Risk No. |Risk Name |Controllable or |Risk Statement |Response (Avoid/Control/ |Probability and Impact |Action Plan |

| | |Uncontrollable | |Assume/Mitigate/ |(Low/Med/High and | |

| | | | |Watch/Escalate/ Transfer)|Minor/Mod/Significant) | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

Performance Indicators for Successful Information Management

[Provide context.]

|Indicator No. |Outcome Desired |Performance Indicator |Performance Indicator |Success Factor(s) |Performance Measure |Approval Authority |

| | |Name |Description | |Timeline | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

| | | | | | | |

Appendix 1 - Policies, Acts and Directives:

TBS – IM Strategic Direction for Government – documents the approved strategic directions in the area of information management for the Government of Canada.

TBS – Policy on Information Management – establishes the value of information resources to the GC and the requirement for all employees to be involved in their management.

TBS – Directive on Information Management Roles and Responsibilities – establishes accountabilities for IM of different levels of civil servants.

TBS – Information Management Guidelines – establishes guidelines on departmental planning of IT and IM.

TBS - Enhanced Management Framework - provides solutions to project management concerns experienced in the federal government. It comprises principles, best practices, methodologies, tools, templates, handbooks, guides and standards.

Justice – Access to Information Act

Justice – Privacy Act

Justice - Personal Information Protection and Electronic Documents Act

Library and Archives Canada Act – Section 12 (1) No government or ministerial record, whether or not it is surplus property of a government institution, shall be disposed of, including by being destroyed, without the written consent of the Librarian and Archivist or of a person to whom the Librarian and Archivist has, in writing, delegated the power to give such consents (this includes destruction through inattention).

PWGSC - DP(tbd): Information Management Policy (currently in development)

PWGSC – DP092-Policy on Official Languages

PWGSC – DP083-Verbal Enquiries from Parliamentarians

PWGSC – DP068-Ministerial Correspondence

PWGSC – DP067-Management of Electronic Mail

PWGSC – DP066-Departmental Library Services

PWGSC – DP062-PWGSC Management Framework for Communications on the Internet and Intranet

PWGSC – DP061-Forms Management

PWGSC – DP052-Corporate Security Program

PWGSC – DP051-Departmental Security Program

PWGSC – DP044-Records Management & Information Holdings

PWGSC – DP014-Protection of Personal and Private Information in the Workplace

PWGSC – DP002-Policy on Access to Information and Privacy Act

Appendix 2 – Roles and Responsibilities:

Project Champion or Service/Product Authority[2]

• Overseeing compliance with all federal legislation and departmental policies and directives (see appendix 1);

• Championing the principles espoused in the Treasury Board ‘Policy on Information Management, including facilitating the use of electronic systems for creating, using and managing information resources throughout their life cycle;

• Overseeing the strategic planning and resourcing activities related to the management of information resources;

• Ensuring that information management requirements (including records management, systems development, etc) are identified and addressed at an early stage of any operational program design; and

• Designating a senior manager who will be an active member of a committee on the management of records and information holdings and an advocate of the records management principles.

Project/Service/Product Director2

• Appointing resources to develop the Information Management plan;

• Appointing an Information Manager to carry out assigned duties on a day-to-day basis; and

• Ensuring that the Information Management Plan is agreed upon, in place and being followed.

Project/Service/Product Manager2

• Ensuring all employees and persons engaged under contract comply with federal legislation and departmental policies and directives for the management of information (reference section 6 of this document);

• Ensuring all employees and per sons engaged under contract receive the required training in the management of information resources;

• Planning, resourcing and implementing activities related to the management of information resources, including the use of automation;

• Identifying and addressing requirements for information resources at an early stage of any program design; and

• Co-operating with departmental records management specialists on the efficiency and effectiveness of plans and activities related to the management of information resources.

Information Manager2

The Information Manager is responsible for establishing and supporting the Information Management practices for the _________ Project/Program/Service. Specific duties include:

• Preparing an Information Management Plan, in coordination with the Project Director and the Project Manager and the appropriate Information Management Specialists;

• Updating the IM Plan, as required and as new issues emerge;

• Advising Project Team Members on issues related to the IM plan;

• Co-ordinating the Implementation of the IM Solution for the Project;

• Co-ordinating Training on any IM Solution Tools as required; and

• Liaising with Departmental Information Specialists or Departmental IM Advisors.

Information Management Specialist2

Information Management Specialists - including librarians, archivists, access to information and privacy officials, records management specialists, Web management specialists, forms management specialists, and security specialists will support information management efforts by:

• Providing IM advice, tools, procedures, standards, and guidelines, consistent with direction provided by the Treasury Board of Canada Secretariat and Library and Archives Canada;

• Aiding the Information Manager in the implementation of the IM Plan;

• Identifying enterprise level information requirements to information technology personnel to support the development and operation of IT processes, systems, standards, and tools; and

• Assessing specific IM resource and training requirements and working with the Information Manager to implement these needs.

Information Management Advisors2

Information Management Advisors are the resources under the Knowledge and Information Management Directorate (KIMD) and will support information management efforts by:

• Providing IM advice and support on all aspects of managing the information resource;

• Providing advice and guidance on information architecture;

• Providing feedback on the IM Plan;

• Aiding the Information Manager in the implementation of the IM Plan;

• Identifying enterprise level information requirements to information technology personnel to support the development and operation of IT processes, systems, standards, and tools; and

• Assessing general IM training requirements and working with the Information Manager to implement these needs.

Teams members2

• Applying effective principles, standards, guidelines and practices for managing information resources in the ongoing performance of their duties, including the ‘Policy on Information Management’,;

• Managing information resources throughout their life cycle and complying with federal legislation and departmental policies, directives, standards and guidelines regarding the management of information (refer to section 6 of this document for details);

• Maintaining audit trails by documenting activities and decisions, particularly with respect to electronic mail messages;

• Supporting program development by identifying information resource requirements and issues to their manager and departmental IM and IT specialists;

• Participating in training offered on information management, as appropriate, and

• Using electronic systems for creating, using and managing records and information holdings.

Clients

• [Define roles and responsibilities of Clients];

• Managing information resources throughout their life cycle and complying with federal legislation and departmental policies, directives, standards and guidelines regarding the management of information (refer to section 6 of this document for details); and

• Maintaining audit trails by documenting activities and decisions, particularly with respect to electronic mail messages.

Other Stakeholders

• [Define roles and responsibilities of other Stakeholders];

• Managing information resources throughout their life cycle and complying with federal legislation and departmental policies, directives, standards and guidelines regarding the management of information (refer to section 6 of this document for details); and

• Maintaining audit trails by documenting activities and decisions, particularly with respect to electronic mail messages.

Appendix 3 - Definitions

Classification / Record Classification:

• Definition: The Departmental Subject File Classification Plan is a comprehensive and structured system used to organize and locate records throughout their life cycle. At PWGSC, records are organized numberically under two main subject categories: administrative and operational.

• Note: Employees are not responsible for assigning numbers to records from different categories. For assistance in this area contact your Branch Record Centre or the Records Management Directorate.

Data:

• Definition[3]: Data is a set of discrete facts about events. Most organizations capture significant amounts of data in highly structured databases such as Service Management and Configuration Management tools/systems and databases.

Document:

• Definition[4]: A document can be a work processing file, a spreadsheet, a project management schedule, a graphics file, a CAD or engineering drawing, paper scanned as an image, a slide show presentation, audio and even video, or any similar item that can be contained in an electronic file.

Information:

• Definition3: Information comes from providing context to data. Information is typically stored in semi-structured content such as documents, e-mail, and multimedia.

The key Knowledge Management activity around information is managing the content in a way that makes it easy to capture, query, find, re-use and learn from experiences so that mistakes are not repeated and work is not duplicated.

Knowledge:

• Definition3: Knowledge is composed of the tacit experiences, ideas, insights, values and judgements of individuals. People gain knowledge both from their own and from their peers’ expertise, as well as from the analysis of information (and data). Through the synthesis of these elements, new knowledge is created.

Knowledge is dynamic and context based. Knowledge puts information into an “ease of use” form, which can facilitate decision-making. In Service Transition, this knowledge is not solely based on the transition in progress, but is gathered from experience of previous transitions, awareness of recent and anticipated changes and other areas that experienced staff will have been unconsciously collecting for some time.

Metadata:

• Definition[5]: Data about data. Metadata describes how and when and by whom a particular set of data was collected, and how the data is formatted. Metadata is essential for understanding information stored in data warehouses (databases) and has become increasingly important to Web-based applications and sites.

Record:

• Definition[6]: Any documentary material other than a publication, regardless of medium or form. Records include any correspondence, memorandum, book, plan, map, drawing, diagram, pictorial or graphic work, photograph, film, microform, sound recording, videotape, machine readable record and any documentary material regardless of physical form or characteristic and any copy thereof. A record that does not exist but can be produced from machine-readable records (subject to regulations) is also included in the definition of a record.

Transitory Records:

• Records of temporary usefulness that are not an integral part of an administrative or operational record series, that are not regularly filed with standards records or filing systems, and that are only required for a limited period of time for the completion of a routine action or the preparation of an ongoing record.

Appendix 4 – Storage Medium

|Storage Medium |Characteristics |

|Shared Drives |-Easy to store and access files. |

|(not recommended) |-Familiar to everyone (no training required). |

| |-Backed up regularly. |

| |- Need to impose an organizational structure and ensure the documents are captured in a formal recordkeeping repository at |

| |some point in order that retention and disposition schedules can apply. |

| |- Need to ensure access/security restrictions are adequate. |

| |- Can cause difficulties when searching and retrieving documents if unstructured. |

|E-DRM |-Requires license to store and retrieve files. |

|(departmental tool) |-Provides version control. |

| |-Backed up regularly. |

| |- Documents are filed properly into the classification system with retention and disposition schedules applied automatically |

| |- Retrieving information is easy based on the classification system |

| |- Makes complying with Access to Information and Privacy requests simple. |

|Filing Cabinet |-Provides paper based (not electronic) storage. |

|(used to store reference|-Can hold Protect B materiel if classified as a secure cabinet. |

|documents) |- Corporate documentation should be filed into the recordkeeping repository. |

| |- If sole source of corporate information, can cause issues with regards to Access to Information and Privacy requests (i.e.:|

| |information may not be disclosed as appropriate). |

| |- If sole source of corporate information, knowledge transfer can be difficult – lack of a formal classification structure, |

| |interested parties do not necessarily know files exist, etc. |

|Databases |- Used to house data captured from applications. |

| |- IT provides lifecycle support. |

| |- Lifecycle management rules need to apply (i.e.: classification and eventual disposition must be decided). |

-----------------------

[1] As per TBS’ Framework for the Management of Information: IM Compendium of Checklists

[2] As per the ITIL Service Transition document

[3] As per the AB Gov. Services EIM Business Case

[4] As per DP 002 (Policy on Access to Information and Privacy Act)

[5] As per TBS’ Policy on Information Management

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download