The Impact Of e- Discovery On The CIO


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • The Impact Of e- Discovery On The CIO

    1. 1. The Impact of e-Discovery on the CIO : Recordkeeping Litigation Readiness Jean-Stéphen Piché Director General Government Records Branch Library and Archives Canada
    2. 2. Context <ul><li>E-Discovery </li></ul><ul><ul><li>Retrieving relevant information </li></ul></ul><ul><li>Litigation Readiness </li></ul><ul><ul><li>Ensuring that your key business activities are documented and linked to effective decision making, and accountability </li></ul></ul><ul><li>Business Risks </li></ul><ul><ul><li>Reducing risks to organizations and citizens in disposing of unnecessary records and keeping/preserving key evidentiary records </li></ul></ul>
    3. 3. CIO Concerns for e-discovery Long term preservation of Information Resources of Business Value Security And Privacy Search and Retrieval Digital Preservation Email Management E-Records Management Business intelligence and analytical tools Web 2.0 Institutional Capacity and Readiness Departmental Recordkeeping Requirements
    4. 4. Information Resources and ESI textual records films sound recordings photographs documentary art graphics maps portable devices filing cabinets electronically stored information
    5. 5. Problematique <ul><li>Information not or poorly managed / disposed </li></ul><ul><ul><li>Risk of destroying key records by accident </li></ul></ul><ul><ul><li>Risk of keeping too much information by fear of not destroying unnecessary records </li></ul></ul><ul><ul><li>Risk of not being able to FIND the most relevant information </li></ul></ul>
    6. 6. Recordkeeping Supports Litigation Readiness <ul><li>Establishes core-essential administrative and business coherence within government for: </li></ul><ul><ul><li>effective decision-making </li></ul></ul><ul><ul><li>development of policy </li></ul></ul><ul><ul><li>delivery of programs and services to Canadians </li></ul></ul><ul><ul><li>legal evidence of action </li></ul></ul><ul><li>Effective Recordkeeping </li></ul><ul><ul><li>Provides ready access to the right records and evidence. </li></ul></ul><ul><ul><li>Provides a rational disposal of unnecessary records. </li></ul></ul><ul><ul><li>Improves productivity and increased efficiencies </li></ul></ul><ul><ul><li>Satisfies accountability and stewardship requirements </li></ul></ul><ul><ul><li>Mitigates business risks – protection under audit, investigation and litigation </li></ul></ul><ul><ul><li>Leverages IT investments and rationalize costs </li></ul></ul>
    7. 7. RK Regime Context <ul><li>GC Policy Framework for Information Management and Information Technology </li></ul><ul><ul><li>Information Management Policy (2007) </li></ul></ul><ul><ul><ul><li>Recordkeeping Directive (in effect in March 2009) </li></ul></ul></ul><ul><ul><ul><ul><ul><li>Output: Departmental Recordkeeping Requirement </li></ul></ul></ul></ul></ul><ul><ul><ul><li>And other instruments </li></ul></ul></ul>
    8. 8. Benefits of an RK Regime <ul><li>Differentiates between the vast amounts of information created and focuses investments on information resources of business value to the institution </li></ul><ul><li>Combines business process and business needs analysis with recordkeeping practice </li></ul>
    9. 9. RK Directive <ul><li>Objective </li></ul><ul><ul><li>The objective of this directive is to establish departmental recordkeeping requirements that will help organizations create, acquire, develop, manage, and use information resources as a key business asset in line with performance, reporting and accountability requirements. </li></ul></ul><ul><ul><li>The directive requires the establishment of a management structure for assessing the business value of records, addressing the information life cycle, and establishing recordkeeping as a core resource management function that helps organizations manage information. </li></ul></ul><ul><li>Expected Results </li></ul><ul><ul><li>Departments have confidence that their employees create, acquire, capture, develop, manage, and use information resources in accordance with departmental and Government-wide recordkeeping direction and policies. </li></ul></ul><ul><ul><li>Departments create, acquire, capture, develop, manage, and use information resources as a business asset for decision-making and accountability purposes. Program and service activities are supported by readily accessible information resources which comprehensively documents the business activities. </li></ul></ul>
    10. 10. RK Directive (suite) <ul><li>The following requirements are to …assess the level of integration between recordkeeping and Information Management in terms of expected results over time, planning, implementation, and roles and responsibilities based on their unique circumstances: </li></ul><ul><ul><li>Establish department-wide conditions and infrastructure to support the recordkeeping needs of business units within the department. </li></ul></ul><ul><ul><li>Establish and implement key mechanisms and tools to support the department’s recordkeeping requirements throughout the information life-cycle </li></ul></ul><ul><ul><li>Delegating the authority to dispose of unnecessary records as per the delegation instrument issued under the Library and Archives Canada Act. </li></ul></ul><ul><ul><li>Communicating and engaging departmental stakeholders on the progress, challenges, responsibilities, and risks associated with the development of recordkeeping in the department and within the GC. </li></ul></ul>
    11. 11. Departmental Recordkeeping Requirements <ul><ul><li>Develop and maintain a Departmental Recordkeeping Requirements document that aligns departmental information resource management with business activities to better address accountability, stewardship, performance measurement, reporting and legal requirements. This document includes: </li></ul></ul><ul><ul><ul><li>a business process analysis of the business functions and activities carried out by a department. </li></ul></ul></ul><ul><ul><ul><li>documentation on the business functions and activities identified by the business process analysis. </li></ul></ul></ul>
    12. 12. RK Regime triggers for enabling litigation readiness <ul><li>Can you identify these possible risks relating to legal or regulatory ramifications for conducting business, any risks related to information resource capture, and any legal advice received, concerning the parameters of information resources? </li></ul><ul><li>Do you have Legal Risk Management or other Integrated Risk Management Function to identify and mitigate legal risks related to actual or reasonably anticipated litigation, investigation or audit? </li></ul><ul><li>Have you implemented a Departmental Recordkeeping Requirement for program and service areas? </li></ul><ul><li>Do you have signed Records Disposition Authorities, a current and enforced Retention and Disposition Schedules? </li></ul>
    13. 13. RK Regime triggers for enabling litigation readiness (suite) <ul><li>Can you immediately and confidently implement a preservation order? </li></ul><ul><li>Do you have accountable and auditable records destruction procedures? </li></ul><ul><li>Can you identify, manage and dispose of information resources of business value to the degree of sufficient levels of materiality or granularity required to conduct business activity, complete transactions, achieve results, and measure or assess performance? </li></ul><ul><li>Do you have a recordkeeping repository for your information resources of business value? </li></ul>
    14. 14. What is LAC specifically doing about it? <ul><li>Recordkeeping Directive Application Guide </li></ul><ul><li>RK assessment tool </li></ul><ul><li>Business and functional requirements for systems </li></ul><ul><li>Legacy Strategy </li></ul><ul><li>TDR </li></ul>
    15. 15. Problematique Addressed <ul><li>The establishment of an institutional regulatory regime helps mitigate litigation risks for organization by: </li></ul><ul><ul><li>Limiting your information requirements to support to your key business activities </li></ul></ul><ul><ul><li>Facilitate the disposition of unnecessary records </li></ul></ul><ul><ul><li>Help define recordkeeping requirements for systems </li></ul></ul>
    16. 16. Appendix
    17. 17. What is a Document? <ul><li>LAC Act </li></ul><ul><ul><li>Any documentary material, other than a publication, regardless of medium or form. (Source: Library and Archives of Canada Act, 2004 c. 11, s. 2.) </li></ul></ul><ul><li>Documentary evidence </li></ul><ul><ul><li>“ Electronic document” means data that is recorded or stored on any medium in or by a computer system or other similar device and that can be read or perceived by a person or a computer system or other similar device. It includes a display, printout or other output of that data. (Source: Canada Evidence Act, R.S.C. 1985, c. C-5,s. 31.8) </li></ul></ul><ul><ul><li>A record may comprise one or more documents (An act to establish a legal framework for information technology, R.S.Q. c. C-1.1). </li></ul></ul><ul><li>Professional definitions </li></ul><ul><ul><li>A record should correctly reflect what was communicated or decided or what action was taken. It should be able to support the needs of the business to which it relates and be used for accountability purposes. (Source: ISO 15489-1:2001) </li></ul></ul><ul><ul><li>A record is recorded information produced or received in the initiation, conduct or completion of an institutional or individual activity and that comprises content, context and structure sufficient to provide evidence of the activity. (Source: International Council of Archives (ICA), “Guide for Managing Electronic Records”, p. 7) </li></ul></ul><ul><ul><li>Record: A document made or received and set aside in the course of a practical activity as an instrument of a by-product of such activity and set aside for action or reference. (Source: L. Duranti, “Accountability in e-government: observations from InterPares2 case studies”, ICA, Kuala Lumpur, 2008) </li></ul></ul>