When will I use ED Analyzer (EDA) with LAW?

Size: px

Start display at page:

Download "When will I use ED Analyzer (EDA) with LAW?"

Sabrina Taylor
6 years ago
Views:

This documentation describes how Early Data Analyzer (EDA) and LAW Prediscovery (LAW) work together and includes examples of when to use LAW alone versus LAW/EDA together.

1 This documentation describes how Early Data Analyzer (EDA) and LAW Prediscovery (LAW) work together and includes examples of when to use LAW alone versus LAW/EDA together. When will I use ED Analyzer (EDA) with LAW? Large sets of e-discovery are becoming more common, and users are looking for ways to cut costs, time and overhead. EDA and LAW work together to provide this solution. EDA culls the data first and then exports the culled data into LAW for processing. EDA only exports its culled data into LAW; however, LAW s batch processing (i.e., TIFF, OCR and Endorse) and export features can be used to provide load files in different review platforms (e.g., Concordance, Ringtail, CaseLogistix, Summation). Licensing All licenses reside on a USB dongle key which monitors usage of each LAW module. All licenses are listed in the LAW Profile Manager (screenshot below). This view can be accessed thru the Administrative mode of LAW s Profile Manager, LAW LAW is a desktop application that uses the technology of one instance per PC. The user checks out licenses from the dongle key via the LAW Profile Manager, and the application is launched. Users cannot

2 have multiple instances of LAW on one PC. Most PCs in the market today meet the hardware requirements for LAW. Processing speeds may be approximately the same whether single, dual, or quad core machines are used because LAW is a single-threaded, 32 bit application. Likewise, increasing RAM from 2GB to 8 GB per PC may not increase processing speeds. LAW Storage of cases, data and databases Data processed through LAW must be imported into a case repository location where a copy of the file is created as well as any additional files that need to reflect the database being used. SQL is the preferred database type. Since SQL is robust, multiple users can access the same case. LAW also supports Access databases for processing. Drawbacks for using Access databases are lack of support for full text searching and issues with distributive processing due to locking (lock files). Most clients use a SAN or shared file server to store the LAW cases, data and databases. ED Analyzer (EDA) EDA is a culling tool which will work in conjunction with LAW. It is currently developed in.net technology and will utilize more hardware components (CPU and RAM) than LAW will use. For example, EDA uses each CPU core, depending on how many agents are used. Each worker/agent will allocate one core of the CPU. Based on the amount of ED Analyzer User Interface licenses, the user can have multiple instances of EDA on one PC. A Windows Service is also installed to monitor the allocation of agents. EDA is a 32 bit application, but some of its components are coded to utilize the 64 bit components (e.g., Indexer). EDA Storage of cases, data and databases EDA s case repository has some differences from LAW s case repository. A copy of the file is not required by EDA. EDA will reference the source location of the file and SQL database, making data imported and analyzed through EDA approximately five times faster than data imported and ingested with LAW, not only saving time but also saving overhead (since another copy of the file is not generated). SQL is required when using EDA, and all EDA cases created will reside on the same SQL Server that LAW is using. Most users use a SAN or shared file server to store the EDA cases, index and databases. Importing speeds and how each PC is used when importing e-discovery LAW s ED Loader vs. ED Analyzer Worker/Agent EDA will import and cull data faster than LAW. LAW s ED Loader license averages 1-3GB per hour upon import. An ED agent averages 4-5GB per hour upon import because EDA and LAW are using different technologies. In the below example, the user has three different types of PCs.

A B A: Single core CPU with 1GB of RAM (100Mbps Network) 1 LAW ED Loader can be used 1 ED Analyzer agent cannot be used B: Dual core

Network) 1 LAW ED Loader can be used 4 ED Analyzer agents can be used C If A, B and C were all used in a LAW only environment for

3 A B A: Single core CPU with 1GB of RAM (100Mbps Network) 1 LAW ED Loader can be used 1 ED Analyzer agent cannot be used B: Dual core CPU with 4GB of RAM (GB Network) 1 LAW ED Loader can be used 2 ED Analyzer agents can be used C: Quad core CPU with 8GB of RAM (GB Network) 1 LAW ED Loader can be used 4 ED Analyzer agents can be used C If A, B and C were all used in a LAW only environment for importing e-discovery, up to three ED Loader licenses could be used for culling and processing using a SQL backend (3-6GB per hour for import speed). If A, B, and C were all used in an ED Analyzer and LAW environment, (24-30GB per hour for import speed) up to six agents for culling data, and three ED Loader licenses could be used to process the culled data into LAW using a SQL backend (3-6GB per hour for import speed).

4 EDA system requirements and running EDA in an existing LAW environment The LAW system requirements can be found in the help file for LAW. The recommended requirements for LAW can also be used if applying EDA in this same environment. Compare the examples from the previous page (LAW Workstation A, B and C) with the system requirements for EDA. System requirements for EDA Windows desktop OS (Windows 7, XP SP3, Vista x86 or x64) 4GB or Higher Single or multi-core CPU (2.5 GHz or higher per core) SQL Required: SQL 2005 SP4 or higher (will use the same SQL server as LAW) x86 or x64 SQL Express: SQL 2005 SP4 or higher (if running locally or will use the same SQL Express as LAW) x86 or x64.net 4.0 required install Gigabit network LAW Workstation A Even though the desktop meets all of the LAW system minimum requirements, it doesn t meet the EDA requirements. This PC can be used as a LAW Workstation. EDA/LAW Workstation B This desktop meets the requirements to run EDA or LAW and can be used as a LAW Workstation or two cores can be used for two EDA agents. EDA/LAW Workstation C This desktop meets the requirements to run EDA or LAW. This PC can be used as a LAW Workstation or four cores can be used for four EDA agents. Using the same SQL Server for LAW and EDA LAW and EDA are designed to use the same SQL server. A SQL database will be created for every EDA case created. For every export from EDA into LAW, a LAW SQL database is created by default or exported into an existing LAW SQL database. Speed digressions may occur if both applications are running large productions at the same time. Below is an example where production workflow might be affected. In this example, we will use the six PCs from the previous example. Four of the PCs have the requirements of EDA/LAW Workstation B. The remaining two have the requirements of EDA/LAW Workstation C. We will also use the LAW Profile manager from page one as an example of licenses that are available. User 1 has 100GB of data that needs to be culled down on a short timeline. Since the user has enough agents, the user will use EDA to cull through the data quickly before processing it in LAW. The user decides to use the two PCS that have the requirements of EDA/LAW Workstation C to start the import process in EDA for culling. The user decides to use eight agents on this 100GB. EDA Priority while importing:

5 1. Network (good connection between SQL and Agents) 2. Network (SAN or DAS (ISCSI) source location, fast read speed) 3. RAM (the more RAM the PC has, the better) 4. CPU (the more cores the PCs have, the better the agents can be allocated) User 2 wants to use LAW for another project where batch processing needs to be done on a large set of documents. Since there are four PCs available, User 2 decides to distribute the processing across all four PCs. As the user is batch processing, the user notices that speeds are slower than normal. LAW Priority while batch processing: 1. Local hard drive (fast read and write) 2. Network (good connection between LAW case directory (SAN) and SQL) 3. CPU (most CPU processing happens on the local workstation level) 4 RAM Possible reasons for digression in speed are highlighted in red. As stated previously, EDA runs five times faster than LAW, and it will utilize the network and SQL environments five times more than in a LAW only environment. Possible resolutions include the following: Assign X amount of agents per EDA case: Instead of eight agents, perhaps four can still meet the timeline while processing can continue on the other batch processing project. This can also work in reverse if User 1 wants to add more agents to this EDA case to finish faster so User 2 can continue the batch processing project in LAW. Suspend the EDA case: EDA processing can be suspended temporarily so other processes can be accomplished whether it is in this case for LAW or even another EDA case. In this scenario, User 2 can use all six PCs to finish the batch processing project. Building the EDA/LAW workflow: EDA is available in two different bundles: Basic EDA Bundle 1 ED Analyzer User Interface license: The user interface for case creation and data import. The user interface allows for filtering and full text searching culling the data set for export to LAW. 4 ED Analyzer Agents: Agents that allocate one core per agent. The user can control which agents are running from case to case. Export EDA Bundle: This bundle is available for users who do not have LAW s Admin and ED Loader modules which are required to export from EDA into LAW. Additional user interface licenses and agents can be added to optimize the EDA/LAW workflow as described below: Examples of environmental setups for LAW Possible LAW or EDA/LAW environments are illustrated in the following examples.

6 Example 1 This example is for a small LAW work environment. The user wants a cost-effective environment where small sets of e-discovery can be easily processed. This workflow can vary based on amount of licenses purchased. SQL Express File Server (Case data) LAW Stations Example 2 This example is for users who desire file storage for all LAW case data as well as a separate SQL server for all LAW cases. This workflow can vary based on amount of licenses purchased. File Server/SAN/NAS LAW SQL Server LAW Stations Example 3 This example is for a Virtual Machine (VM) environment for users who do not wish to purchase muliple hardware desktops. VMware must have USB support for the license dongle key. File Servers/SAN/LAW SQL Server/VMs reside Virtual Servers for hosting each VM LAW Processing Benchmarks These benchmarks were tested on the following PC:

7 Windows 7 X64 Quad Core at 2.66GHz 8 GB of Ram 40 GB SATA Hard Drive (7200RPM) SQL Database (Case data stored on the network) Gigabit network Importing EDD into LAW case (SQL Preferred) 1 to 3 GB per Hour (tested on both mail stores and e-docs) TIFF Conversion Converting to Black and White Tiffs = pgs. per hour Converting to Color Tiffs = pgs. per hour OCRing (Using Expervision Engine) Black and White tiffs = pgs. Per hour Color tiffs = pgs. Per hour OCRing (Using ABBYY Engine) Black and White tiffs = pgs. Per hour Color tiffs = pgs. Per hour Endorsing Black and White tiffs = pgs. per hour Color tiffs = pgs. per hour The following adjustments may result in an increase in performance benchmarks: Faster CPU (3.0 GHz or higher) Faster hard drives (LAW relies heavily on local temp directory for read/write function) Network configuration and connection to file server/san (Gigabit network) Updates on operating system, Office and LAW Prediscovery The following conditions may result in a decrease in performance benchmarks: Windows Indexer running (Windows 7 and Windows XP) Large documents (Importing EDD, Endorsing, OCRing or Tiffing) Large archives or attachments (Importing EDD) Quality of Images (Color or poor compression) Additional options applied for ED loader, Tiffing and OCRing Browsing and downloading from internet (MySpace, ITunes) Anti-Spying Software (Microsoft Security Essentials/McAfee/Symantec) Workflow suggestions

8 Use IP address as an alternative vs. the computer name: This alternative is preferred over the default computer name on the network. Use an IP address in LAW when: 1. Using LAW Management Console (SQL Server IP) 2. License Server IP Address (PC where LAW dongle key resides) 3. Creating a SQL case in LAW (SQL Server IP) Common applications required with LAW Microsoft Office 2010 or 2007 or 2003 (x64 not supported) Internet Explorer 8 or 9 (required for HTM files) Adobe Acrobat (required for PDF files) Lotus Notes Client Version 6.5 or higher (for processing NSF files) Optional source applications supported with LAW Autovue (optional for use for MS Office apps replacement) E-Drawings (optional for AutoCAD files) LAW Native Viewer (additional module for purchase) Quick View Plus version 9 (versions higher than 9 are not supported by LAW) Non-LAW source applications (for use with shell printer) Fox It PDF reader Open Office/Libre Office Configuring source applications to tiff with LAW Method One: 1. Launch ED-Loader>Settings>File Types The File Type management database will show the path to an Access database (EDloader.ftm.mdb) in which ED Loader recognizes the file type and the associated source. 2. Click on Edit. Enter the file extension hit <ENTER> and associate the source application to the file type. Method Two: Go to the <InstallDIR>\LAW50\EDLoader\edfiletypemanager.exe and launch. PLEASE NOTE: This database can be shared for all machines by redirecting the location to a share location (e.g., G:\LAWShared\EDloader.ftm.mdbBy default). Source applications used for tiff conversion: Using Microsoft Outlook (msgs or psts processing): An profile is required for use with LAW. Using Internet Explorer (converting htm to tiff using this source application): Ensure that the home page is a blank page. Have Internet Explorer to Work Offline. Lotus Notes Client: Versions 6.5 or higher. Lotus must be installed when converting native NSF files to tiff. Choosing a source application to process certain documents:

9 Primary = this should be set on all types. Secondary= Use as a backup for QC or another type of source. MSG files: Microsoft Outlook primary, shell printer secondary. HTM files: Internet Explorer primary; Microsoft Word secondary; alternatively, Quick View plus 9. PDF files: Adobe Acrobat primary; shell printer secondary. XLS\DOC\PPT\PUB: Already assigned by default source application (Word, PowerPoint, Excel, and Publisher); secondary is shell printer. Additional notes about shell printer in LAW: The shell printer in LAW uses the Windows Explorer API for printing. Associate the file type with the selected application in Windows. The shell printer now can be used as the source application. The shell printer has limited function since it supports a small amount of applications, and it also ignores all additional tiff options for Word/PowerPoint/Excel/Publisher. Switches /su and /debug: These settings allow the user to run SQL statements in the LAW case or to remove existing image endorsements. Distributive batch processing or loading: Crossing different versions of software when using these features is not recommended.

LAW PreDiscovery and Early Data Analyzer Virtual Machine Recommendations

LAW PreDiscovery and Early Data Analyzer Virtual Machine Recommendations Virtual Machine Recommendations Virtual Machine Recommendations No part of this work may be reproduced or transmitted in any form