succeeding at ediscovery what you need to know gregory trosset – erm project program manager...
TRANSCRIPT
Succeeding at eDiscoveryWhat you need to knowSucceeding at eDiscoveryWhat you need to know
Gregory Trosset – ERM Project Program Manager
Department of Executive Services Records and Licensing Services DivisionArchives and Records Management Section
Why is it importantWhat you need to know
Why is it importantWhat you need to know
• Federal Rules of Civil Procedure (revised)– Parties need to discuss (early on) the discovery aspects of ESI1, provide for timely
production (in native format), preserve ESI with metadata intact, and provide for a verifiable chain of custody
• Successful eDiscovery starts with good records management– Provide staff with a way to comply (tools)– Set expectations (policy)– Communicate (education)– Conduct oversight (compliance)
• Federal Rules of Civil Procedure (revised)– Parties need to discuss (early on) the discovery aspects of ESI1, provide for timely
production (in native format), preserve ESI with metadata intact, and provide for a verifiable chain of custody
• Successful eDiscovery starts with good records management– Provide staff with a way to comply (tools)– Set expectations (policy)– Communicate (education)– Conduct oversight (compliance)
The Records Management ShiftWhat you need to know
The Records Management ShiftWhat you need to know
Low
High
Managed
Use
r Part
icip
ati
on
Managed - Well defined, centralized control, structured schema, few participants
UnmanagedContent
Tim
e
60’s
TodayRecords created electronically – 90%
Enterprise data growth over the next five years – 650% 2
Unmanaged - Undefined, decentralized, flexible schema, many participants
AnalysisWhat you need to know
AnalysisWhat you need to know
2007 Electronic Records Management Survey – Cohasset Associates
• Are we ready?– 14% - Organizations consistently following their retention schedules– 55% - Organizations addressing retention for email and Web 2.0– 56% - Organizations with a formal discovery plan
• Most organizations..– Are not retaining everything they should– Lack policies and procedures– Are at risk for significant sanctions/costs
• Are we ready?– 14% - Organizations consistently following their retention schedules– 55% - Organizations addressing retention for email and Web 2.0– 56% - Organizations with a formal discovery plan
• Most organizations..– Are not retaining everything they should– Lack policies and procedures– Are at risk for significant sanctions/costs
The costs of not being readyWhat you need to know
The costs of not being readyWhat you need to know
• Discovery– 35% - eDiscovery portion of the total cost of litigation 3
– $1,800 to $2,500 – Legal review cost per gigabyte 4
– $11M – DuPont study over 5 years (50% of record reviewed needlessly) 5
• Sanctions– $1.45B – Coleman Holdings v. Morgan Stanley (inability to produce records) 6
– $29M – Zubulake v. UBS Warburg (Spoliation presumption) 7
– $6.2M – Murphy Oil USA v. Fluor Daniel (failure to follow policy) 8
– “State orders City Hall computers secured in email dispute” 9
– King County agrees to pay $255,000 to settle public records lawsuit” 10
• Discovery– 35% - eDiscovery portion of the total cost of litigation 3
– $1,800 to $2,500 – Legal review cost per gigabyte 4
– $11M – DuPont study over 5 years (50% of record reviewed needlessly) 5
• Sanctions– $1.45B – Coleman Holdings v. Morgan Stanley (inability to produce records) 6
– $29M – Zubulake v. UBS Warburg (Spoliation presumption) 7
– $6.2M – Murphy Oil USA v. Fluor Daniel (failure to follow policy) 8
– “State orders City Hall computers secured in email dispute” 9
– King County agrees to pay $255,000 to settle public records lawsuit” 10
ToolsWhat you need to know
ToolsWhat you need to know
• ERMS – Electronic Records Management System– Not document management– Compliance tool– Complex retention requirements (ie. Govt.)– DoD 5015.2 (defacto standard)
• Features– Categories (what to keep)– Standardization (category level)– Built-in retention policies (how long)– Auto-profile (simplify end user interaction)– Metadata preservation– Auditing– Chain of custody & authenticity (trustworthy)– Rich security (access controls)– De-duplication (control copies)
• ERMS – Electronic Records Management System– Not document management– Compliance tool– Complex retention requirements (ie. Govt.)– DoD 5015.2 (defacto standard)
• Features– Categories (what to keep)– Standardization (category level)– Built-in retention policies (how long)– Auto-profile (simplify end user interaction)– Metadata preservation– Auditing– Chain of custody & authenticity (trustworthy)– Rich security (access controls)– De-duplication (control copies)
Tools (cont.) What you need to know
Tools (cont.) What you need to know
• Questions and cautions– Upfront costs (pay me now)– Scope (electronic, paper, imaging, web)– DM integration– DoD Certification (do you really need this?)– Executive support– Ongoing support– Significant lead time to deploy– File plan development– Big bucket approach (keep it simple for end users)– End-users (must be in the equation)
• Questions and cautions– Upfront costs (pay me now)– Scope (electronic, paper, imaging, web)– DM integration– DoD Certification (do you really need this?)– Executive support– Ongoing support– Significant lead time to deploy– File plan development– Big bucket approach (keep it simple for end users)– End-users (must be in the equation)
Other tools – Use with caution What you need to know
Other tools – Use with caution What you need to know
• Automated policy (auto-delete)– Ignores retention– All records are not created equal– Lost institutional knowledge
• Archiving tools (pay me later)– Keep it all– If you have it, you may have to produce it (review $$)– Storage acquisition $$ are decreasing as TCO continues to rise. [11]
– Ignores retention (migration issues)
• Disaster recovery tapes
• Allow users to manage retention (“just in case”)
• Allow pst files to proliferate (personal archives)
• Automated policy (auto-delete)– Ignores retention– All records are not created equal– Lost institutional knowledge
• Archiving tools (pay me later)– Keep it all– If you have it, you may have to produce it (review $$)– Storage acquisition $$ are decreasing as TCO continues to rise. [11]
– Ignores retention (migration issues)
• Disaster recovery tapes
• Allow users to manage retention (“just in case”)
• Allow pst files to proliferate (personal archives)
Policies What you need to know
Policies What you need to know
• Email Management– Appropriate use (we all have this)– It’s a record (but not a record series)– Provide guidelines (How to manage)– PST issues– Former employees (the black hole)
• Web 2.0– It may be a record– Challenges
• Ownership• Control• Retention
– Your staff are using it• Provide guidance• Encourage vs. discourage• Insert yourself into the discussion
• Email Management– Appropriate use (we all have this)– It’s a record (but not a record series)– Provide guidelines (How to manage)– PST issues– Former employees (the black hole)
• Web 2.0– It may be a record– Challenges
• Ownership• Control• Retention
– Your staff are using it• Provide guidance• Encourage vs. discourage• Insert yourself into the discussion
Policies (cont.) What you need to know
Policies (cont.) What you need to know
• Legal Hold– Define roles
• Everyone– Communicate– Suspend destruction– Compile
• Attorney– Describe, Issue, Remove– Periodic review/reminder communications– Coordinate
• Department head/delegate– Internal procedures– Communicate hold– Document (everything)– Compile index– Coordinate
– Media neutral– Native format (preferred)
• Legal Hold– Define roles
• Everyone– Communicate– Suspend destruction– Compile
• Attorney– Describe, Issue, Remove– Periodic review/reminder communications– Coordinate
• Department head/delegate– Internal procedures– Communicate hold– Document (everything)– Compile index– Coordinate
– Media neutral– Native format (preferred)
Policies (cont.) What you need to know
Policies (cont.) What you need to know
• Records Management– What should you be retaining?– How long should you keep it?– Be consistent (follow your own policy)– Document what you do (ie destruction)– Replication (primary/secondary copies)– Metadata issues (native format)– Media neutral
• Records Management– What should you be retaining?– How long should you keep it?– Be consistent (follow your own policy)– Document what you do (ie destruction)– Replication (primary/secondary copies)– Metadata issues (native format)– Media neutral
Policy considerations What you need to know
Policy considerations What you need to know
• Involve the right players– Records Management– IT– Legal– Risk Management– End users?
• It must be practical– Employees must have the right tool to comply– No policy could be better then a unenforceable policy– Shouldn’t negatively impact line of business
• It must be consistently employed– Media neutrality– Everyone must play
• Involve the right players– Records Management– IT– Legal– Risk Management– End users?
• It must be practical– Employees must have the right tool to comply– No policy could be better then a unenforceable policy– Shouldn’t negatively impact line of business
• It must be consistently employed– Media neutrality– Everyone must play
Education & Oversight What you need to know
Education & Oversight What you need to know
• Education– Senior Management
• Informed decision-making• Champion for your program
– New employee (more then just the 5 minute sound bite)– Ongoing (reinforce)
• Brownbag lunches
• Website
• Quick tips
• Oversight– Performance appraisals
• Hold employees accountable
– Service Level Agreement– On-demand audits
• When is it appropriate
• Don’t become the records police
• Education– Senior Management
• Informed decision-making• Champion for your program
– New employee (more then just the 5 minute sound bite)– Ongoing (reinforce)
• Brownbag lunches
• Website
• Quick tips
• Oversight– Performance appraisals
• Hold employees accountable
– Service Level Agreement– On-demand audits
• When is it appropriate
• Don’t become the records police
What is King County doingWhat is King County doing
• Scope– Five year project– Electronic, paper, imaging, web– $4.9M budget– Approximately 9,000 end-users
• Phase I – Planning (2006 & 2007)– Business case– Educate senior leadership, identify sponsor, funding, etc.– RFP and selection process
• Phase II – Pilot for eRecords (2008)– Human Resources Division (75 users)– Installation, configuration, training curriculum, etc..– Identify policy needs
• Scope– Five year project– Electronic, paper, imaging, web– $4.9M budget– Approximately 9,000 end-users
• Phase I – Planning (2006 & 2007)– Business case– Educate senior leadership, identify sponsor, funding, etc.– RFP and selection process
• Phase II – Pilot for eRecords (2008)– Human Resources Division (75 users)– Installation, configuration, training curriculum, etc..– Identify policy needs
What is King County doing (cont.)What is King County doing (cont.)
• Phase IIIa – Deployment and additional modules (2009)– Configure and deploy eRecords (Core agencies)– 800 end-users– Implement Physical Records module– Policy development
• Phase IIIb – Deployment and additional modules (2010)– Continue eRecords deployment (Core agencies)– 1,200 end-users– Implement Digital Imaging– Implement Web Records management
• Phase IIIc – Common Records deployment (2010 & 2011)– Rapidly deploy eRecords countywide (existing categories)– 7,000 users– Address 70% of records needs (by volume)– Limited development work
• Production support (2011 and beyond)– Address remaining categories on an ongoing basis
• Phase IIIa – Deployment and additional modules (2009)– Configure and deploy eRecords (Core agencies)– 800 end-users– Implement Physical Records module– Policy development
• Phase IIIb – Deployment and additional modules (2010)– Continue eRecords deployment (Core agencies)– 1,200 end-users– Implement Digital Imaging– Implement Web Records management
• Phase IIIc – Common Records deployment (2010 & 2011)– Rapidly deploy eRecords countywide (existing categories)– 7,000 users– Address 70% of records needs (by volume)– Limited development work
• Production support (2011 and beyond)– Address remaining categories on an ongoing basis
SummarySummary
• Success at eDiscovery – Starts with RM– Is a collaborative effort
• Policy and tools go hand-in-hand
• Upfront investments can pay off down the road
• Explore all options, but be cautious
• Success at eDiscovery – Starts with RM– Is a collaborative effort
• Policy and tools go hand-in-hand
• Upfront investments can pay off down the road
• Explore all options, but be cautious
RecordsManagement
Thank YouThank You
Questions?
Gregory A. TrossetElectronic Records Project ManagerArchives and Records Management
Records and Licensing Services DivisionDepartment of Executive ServicesGBB-ES-0210416 Occidental Avenue South, Suite 210 206-296-3488Seattle, WA 98104-2836 Fax 206-205-1067
AppendixAppendix
1 – ESI = Electronically Stored Information2 – Top 10 IT Management trends for the next five years – Gartner Group Inc., Computerworld, Oct
20093 – “Minimizing the Pain of eDiscovery with a Proactive Strategy” – Osterman Research, Aug 20094 – Brian Dirking and Raghu R. Kodali, “Strategies for Preparing for E-Discovery”, The Information
Management Journal, May/June 20085 – Julie Gable, “What CIO’s Should Know About Records,” CIO Decisions, November 20056 – Coleman Holdings, Inc. v. Morgan Stanley & Co.7 – Zubulake v. UBS Warburg8 – Murphy Oil v. Fluor Daniel9 – The Boston Globe, Sep 14, 200910 – King County, WA v. Sharkansky
11 – Alan Pelz-Sharpe “Storage costs for ECM and DAM Systems” CMSWatch, Aug 13 & 24, 2009
Reasons for complianceReasons for compliance
California Records Management Act Government Codes 14740-14774As used in this chapter "record(s)" means all paper, maps, exhibits, magnetic or paper tapes, photographic films and prints, and other documents produced, received, owned or used by an agency, regardless of media, physical form or characteristics….”
California Public Records Act (PRA)"Public Records" includes every means of recording or communication or representation: any writing, photograph, drawing, sound or symbol, whether paper, film, magnetic media "computer" data or other document -- which relates to the public business, and which is prepared, owned, used, or retained by the agency.
The Federal Rules of Civil ProcedureParties need to discuss (early on) the discovery aspects of ESI 1, provide for timely production (in native format), preserve ESI with metadata intact, and provide for a verifiable chain of custody.