20080222 Arma Sat Email

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    20080222 Arma Sat Email - Presentation Transcript

    1. Effective Email Management for the Organization Jesse Wilkins February 22, 2008
    2. Agenda
      • Email management drivers
      • Email management today
      • Managing the inbox
      • Capturing and classifying messages
      • Email management technologies
      • Elements of an email policy
    3. EMAIL MANAGEMENT DRIVERS
    4. Email – defining the issue
      • First email was sent in 1971
      • Today more email is sent every day than the USPS delivers in a year
        • 11 billion emails a day in the US alone
        • More than 57 billion a day world-wide
        • NOT including spam
      • 60% or more of business-critical information is stored within messaging systems
    5. Why are we sending so much email?
      • It’s easy
      • It’s asynchronous
      • It’s convenient
      • It’s less formal
      • It’s ubiquitous and platform-neutral
      • There’s a written record of communication
    6. Business issues
      • Email storage costs
        • Up to 200 GB email per month for 1,000-user company
        • Costs to add and manage storage
        • Costs to back up to tape
        • Costs to restore
      • Productivity costs
    7. Business issues cont’d
      • Email retrieval costs
        • It takes more than 11 hours to recover an email more than 1 year old from an archive
        • Typically have to restore the entire tape to a spare (!) server to find the desired message
        • 29% of organizations would not be able to restore an email message over 6 months old
    8. Legal issues
      • Electronic discovery for a Fortune 500 company averages $750,000 per case
      • 75% of demands for discovery are for email
      • Courts want discovery in native format…
      • … but may also require that it be provided in an accessible format
    9. Email and the FRCP
      • Email is ESI and must be produced
      • Litigation holds need to include email systems, clients, backups, and archives
      • Organizations need to know what they have and where it is located
      • Time to locate email is before litigation begins
    10. Legal considerations for messages
      • Messages are discoverable – whether they are records or not
      • Message archives are discoverable, regardless of the format or storage medium
      • The “deleted messages box” is discoverable
      • Personal copies are discoverable
    11. Regulatory and recordkeeping issues
      • Email messages might be records – but email is NOT a series!
      • Email has to be accessible today…and tomorrow
        • Email systems and formats
        • Attachments and their formats
        • Media and hardware issues
    12. When is an email a record?
      • When statutorily defined
      • When it documents a business transaction
      • When it supports a business decision
      • When the attachment
      • is a record
      • When it is the only written
      • record of something
    13. EMAIL MANAGEMENT TODAY
    14. Email management defined
      • According to AIIM, The ECM Association, the essence of email management is that
      • “ As the de facto standard for business communication, removing emails from the server and saving them to a repository isn't enough. Email must be classified, stored, and destroyed consistent with business standards-just as any other document or record.”
    15. Email management is NOT:
      • Saving all email messages forever
      • Saving all email messages in the messaging application
      • Setting mailbox time limits
      • Setting mailbox size limits
      • Declaring “email” as a record series
      • Doing nothing
    16. Approaches to managing email today
      • Policy approaches to retention:
      • Do nothing
      • Let users manage their own email
      • Keep everything forever
      • Delete all messages older than X
      • Limit mailbox size to X
      • Declare and manage email as records
    17. Approaches to managing email today
      • Technology approaches to retention:
      • Outsource it!
      • Server-based rules
      • Client-based rules
      • Decentralized – employees do it
        • Messages on the server
        • Messages in .PST/.NSF files
    18. MANAGING THE INBOX
    19. Managing the email messages
      • Messages themselves
      • Read receipts
      • Bounced messages
      • Attachments
      • All of these could be records
      • Even if they are not records
      • they must be managed
    20. Other information objects
      • Many others in the email environment
      • Calendar items and appointments
      • Task items
      • Notes
      • Contacts
    21. Where to find email on the client
      • In the Inbox
      • In personal folders in the Inbox
      • In Sent folder
      • In Deleted folder
      • In the Junk folder
      • As individual messages
      • on the PC
      • In .PST or .NSF files
    22. Where to find email on the server
      • In the email server itself
      • In an email archiving application
      • In an ECM or ERM system
      • On backup or archival media
      • On the J: drive
      • In other peoples’ email accounts
    23. Other email storage locations
      • Printed
      • On removable storage devices
      • On home PCs and laptops
      • On PDAs and smart phones
      • In home or personal email accounts
      • In commercial web-based email accounts
      • Outside the organization
    24. General principles
      • Email is a medium, not an action
      • Email should not be used for everything
      • Email should be kept as long as needed – and no longer
    25. Inbox management model
      • Set up rules for “important” vs. routine messages
      • Consider turning off alerts for incoming messages
      • Make rules about which messages have alerts
      • Define specific times to check email
    26. Reduce your email traffic
      • Lots of email traffic is external opt-in
        • “ Bacn”
      • Some is internal but unnecessary
        • “ Colleague spam”
      • Determine the value provided
      • Use other tools for transitory information
        • IM, phone, face-to-face
    27. CAPTURING AND CLASSIFYING MESSAGES
    28. Capturing email records
      • Capture messages that have value
        • Administrative, fiscal, historical, or legal
      • Not everything needs to be captured
      • Keep them according to retention
      • Remember that others may have copies
    29. Capturing email records
      • Capture and manage messages
      • Manage attachments
      • Capture metadata
        • Name of sender and addressees
        • Date/time sent
        • Other transmission data as necessary
      • May also need to capture
      • calendar items, receipts,
      • CC/BCCs…
    30. Who captures the message?
      • YOU have to capture an email:
        • You receive from outside the organization
        • You send, either internally or to someone outside the organization
      • Designate someone to
      • capture messages sent to groups/lists
    31. Emails that are not captured
      • Transitory messages that are not timely
      • Personal messages unrelated to business
      • “ Me-too” messages
      • Messages already captured by someone else
    32. Emails that are not captured
      • Messages that are not records and not supporting documentation can be deleted
      • Delete manually
        • Assumes users will do it
      • Delete automatically
        • By mailbox age
        • By mailbox size
    33. Classifying messages
      • Group messages according to some property
        • By sender/recipient
        • By topic
        • By date
      • Many different approaches to classification
    34. Benefits of classification
      • Providing linkages between individual records which accumulate to provide a continuous record of activity
      • Ensuring records are named in a consistent manner over time
      • Assisting in the retrieval of all records relating to a particular function or activity
      • Determining security protection and access appropriate for sets of records
    35. Benefits of classification cont’d
      • Allocating user permissions for access to, or action on, particular groups of records
      • Distributing responsibility for management of particular sets of records
      • Distributing records for action
      • Determining appropriate retention periods and disposition actions for records
      • Source: ISO 15489
    36. Classification structures
      • Automatic categorization
      • User-defined categories
      • Departmental- or process-defined categories
      • Enterprise taxonomy
      • Retention schedule
      • Roughly in order from least to most structure
    37. Classification approaches
      • Manually, into folders
      • Manually, using tags
      • Automatically, using rules
        • Client-side
        • Server-side
    38. EMAIL MANAGEMENT TECHNOLOGIES
    39. Technologies for managing email
      • Email messaging applications
      • Print & file
      • Backup tapes
      • Email management applications
      • ECRM solutions
      • Outsourced email solutions
    40. Messaging system
      • Not built to store massive amounts of messages
        • And attachments
        • And manage as records
      • Difficult to search across
      • inboxes
        • Discovery, auditing
    41. Print & file
      • Common approach
      • Challenges:
        • Loss of metadata
        • Attachments
        • Typical threaded email
        • message
        • Volume to print and to file
        • Authenticity (phishing)
    42. Backup tapes
      • Archival vs. backup
      • Backups store data, not files or messages
      • Multiple copies of data
      • Readability of older tapes
        • Format, media, hardware
    43. Email management applications
      • Move messages out of the messaging application
      • Typically use a rules engine
      • May provide simple retention management
      • Single instance storage
      • Many different capabilities available
    44. Email management technologies
      • Email archiving
      • Personal archive file management
      • Email encryption and digital signatures
      • Email compliance
      • Email discovery
      • Email security
      • Policy management
    45. ECRM solutions
      • Most systems support email management
      • May run at server or client
      • Many support single-instance storage
      • May allow declaration, management of messages as records
      • Varying support for attachment management, metadata management
    46. Outsourced solutions
      • Let someone else manage it!
        • Microsoft Exchange Hosted Services
        • Gmail, Yahoo, Hotmail
        • Many smaller/specialty providers
      • Security considerations
      • Privacy considerations
      • Recordkeeping and
      • discovery issues
    47. .PST and .NSF Files
      • Personal archive files
      • Used to store messages locally on PCs
      • .PST files present a number of issues
        • Lack of backup
        • Multiple .PST files!
        • Difficult to share, may have passwords
        • Inefficient storage
    48. Managing .PST and .NSF Files
      • Don’t allow them
      • Require them to be stored on a networked location that can be backed up
      • Use technology to ingest, de-duplicate, index, and manage messages in them
        • Or index them in place
    49. Email preservation issues
      • Format of information
        • HTML, RTF, text
      • Format of message
        • .msg, .eml, .txt, others
      • Format of attachment(s)
      • Format of backup
      • Format of archive
      • Media and hardware
    50. Selecting the right solution
      • Determine organizational requirements
      • Determine what is in place
      • Determine what technology is needed to address the gap
      • Research available solutions based on architecture, deployment model, pricing, and capabilities
    51. ELEMENTS OF AN EMAIL POLICY
    52. Email policy principles
      • Email belongs to the organization, not the individual
      • Email is not a records series unto itself
      • Email management program must comply with appropriate regulatory requirements
      • Policy has to be followed and enforced!
    53. Email policy elements
      • Acceptable/appropriate usage
      • Personal usage
      • Access to external messaging systems
      • Effective email usage
      • Ownership of email
    54. Elements of an email policy
      • Retention and disposition
      • Legal issues
        • Holds
        • Discovery and production
      • Mobile and web-based email
      • Backups
      • Archival
    55. Elements of an email policy
      • Privacy
      • Security
      • Retention and disposition
      • Training
      • Audit and compliance
    56. Questions?
    57. Conclusion
      • We have to manage messaging technologies better
      • It starts with policies and procedures
      • Technology can help
      • Communicate, communicate, communicate
      • Enforce the program
    58. Additional resources
      • E-Mail Rules , Nancy Flynn and Randolph Kahn Esq., ePolicy Institute
      • ANSI/ARMA 9-2004, Requirements for the Management of Electronic Messages as Records , ARMA International
      • ANSI/ARMA TR2-2007, Procedures and Issues for Managing Electronic Messages as Records , ARMA International
    59. Additional resources
      • AIIM Email Management Certificate Program
      • Policy Builder by Fortiva and The Electronic Communications Compliance Council (TEC3), http://www.policy-builder.com
    60. For more information
      • Jesse Wilkins
      • CDIA+, LIT, edp, ICP, erm m , ecm m , bpm s
      • Access Sciences Corporation
      • [email_address]
      • http://www.accesssciences.com
      • Blog: http://informata.blogspot.com
      • (303) 574-1455 direct

    + Jesse Wilkins, CRMJesse Wilkins, CRM, 11 months ago

    custom

    779 views, 0 favs, 0 embeds more stats

    Presentation at ARMA San Antonio, February 22, 2008 more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 779
      • 779 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 8
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories