Tag Archives: cost
Outsourcing Managed Document Review
Managed document review can aid you in your discovery process prior to a trial. As opposed to the discovery process after a trial, of course. Discovery is a critical part of any legal case, but in large corporate or class action cases, discovery can be extremely involved. If Bill Gates or Warren Buffet happen to be your client, cost isn’t an issue, but most of us aren’t fortunate enough to represent individuals with bottomless pockets. Inevitably the question arises, should you cut cost on discovery and allocate more resources to trying cases.
Cutting costs on discovery seems stupid, at least superficially. A single key piece of evidence can be the difference in a trial. Overlooking that piece of evidence can be catastrophic.
One problem in huge cases is that there are so many documents to assay that it is impossible to do if the client is billed at standard attorney rates.
Enter the managed document review process. You farm the task of reviewing documents to a third party source which bills at much lower rates. You specify parameters telling them exactly what they are looking for and what can be ignored. They separate the wheat from the chafe, leaving a much smaller pool of documents for you or your legal staff to review.
Managed document review is not infallible. If you are worried about extremely sensitive disclosures which may be highly damaging to a client, letting third parties examine documents is unwise. Smart reviewers must be used, but the smart the reviewers, the higher the cost.
For specialized subjects like science or accounting, cheap managed review is sometimes not possible. This is because only highly paid experts can even understand the documents. There is a duality in this situation. As even a lawyer can’t understand such documents, managed review by experts must be used.
There are document review companies in nations like India, where highly educated individuals accept low wages Americans never would. This can be a good option, but if be aware that if documents have not been scanned, then they must be shipped, which can be risky. Transferring documents electronically is far preferable.
More and more, converting documents to computerized files is preferred. High speed scanners rapidly convert documents into computer files, and then OCR is run. OCR stands for optical character recognition software, and it converts scanned images into readable text. Documents must still be read, but searches of documents using keywords is still very helpful.
Some lawyers view managed document review as a profit drain, and figure it is better to just have staff review documents and bill the client. A markup can be charged for the service. Also, the client doesn’t have to be told the task was farmed out, and can be unwittingly billed at standard legal prices.
Migrate Legacy Application To Multi-Tenant Cloud Based Application
Is the real future Multi-Tenant Cloud based application? What is the true path to illumination Multi-Tenant architecture or single-tenancy? Is Multi-Tenant architecture truly “faster-better-cheaper”?
The answers to all of these have been looked upon in this article. Let us first understand a few basics.
What is Multi-Tenant architecture?
Multi-Tenant architecture is a software architecture where a single instance of the software runs on a server and serving multiple client organizations (tenants). The architecture of the software is built as such that it separates software instances for different tenants or customers i.e. it virtually separates its data and configuration for each customer making it customized in nature. Its also an indispensable attribute of cloud computing.
How is Multi-Tenant architecture different from single-tenant systems?
In Single-Tenant architecture, as the name suggests, the software can be tailored for each tenant separately. The system houses the data for each company on a separate server. Each tenant runs its own copy of the software. The separation can be either virtual (virtual machines on a same server) or physical (running on separate machines).
In a Multi-Tenant Cloud based application, the data from multiple companies are placed on the same server generally separated from each other via a simple partition that prevents data to migrate from one company to another. As the data is housed on the same server, each company using the software is running the same basic application, with the same basic functionality and with the same limited configuration capabilities.
What are the potential challenges of migrating into Multi-Tenant architecture?
In many instances the capacity requirements of a small tenant could go below the minimum capacity database thats available. There is an invariable cost to a database and a smaller database does not perk up much in cost to provide benefits.
In cases of larger tenant count, organizing huge independent surfaces leads to issues. While handling thousands of tenants, thousands of databases needs to be created for them so operations scoped globally to address all the data such as schema deployments or queries that need to report size usage per tenant across all databases would take extremely longer durations to work out.
The applications compatible with much larger databases end up creating connection pool fragmentations. Since every server has a single connection in each pool pointing to the individual database that encloses every tenant, so these connections tend to go cold if every application server does not constantly get a request for each tenant recurrently. In such situations the application finds no connection in the pool and hence needs to start the connection all over again creating performance issues.
How does SaaS overcome the challenges?
SaaS loaded with numerous advantages over the legacy applications presents dramatic changes to both the migration and the delivery of the software solution. Some of the key benefits listed are:
SaaS dynamically allows adjusting the number of tenants per database at any moment in time.
Intense packaging of tenants is possible as one is not trapped with a stagnant tenant layout. With this an affordable and dynamic tenant model is available that can regulate increasing workloads in each tenant.
A major advantage with SaaS is it results in cost savings by merging IT resources into a single operation. Since an application incurs an amount of memory which is sizeable when in proportion to many customers, SaaS reduces this operating cost.
SaaS enables data mining. Instead of collecting data from several sources with diverse database schemas, all the data gets saved in a single database schema. As a result, managing queries across customers, mining data, and looking for trends is much simpler.
Improved usability, custom user Interface and branding.
SaaS abridges the release management process as packages containing code and database changes are required to be installed on a single server.
On the whole, SaaS provides an improved deployment of hardware resources and an enhanced simplicity of maintenance, resulting in lower overall application costs. This makes the technology smart for service providers aiming the small and medium enterprise (SME) business segment.
Migrate Legacy Application To Multi-Tenant Cloud Based Application
Is the real future Multi-Tenant Cloud based application? What is the true path to illumination Multi-Tenant architecture or single-tenancy? Is Multi-Tenant architecture truly “faster-better-cheaper”?
The answers to all of these have been looked upon in this article. Let us first understand a few basics.
What is Multi-Tenant architecture?
Multi-Tenant architecture is a software architecture where a single instance of the software runs on a server and serving multiple client organizations (tenants). The architecture of the software is built as such that it separates software instances for different tenants or customers i.e. it virtually separates its data and configuration for each customer making it customized in nature. Its also an indispensable attribute of cloud computing.
How is Multi-Tenant architecture different from single-tenant systems?
In Single-Tenant architecture, as the name suggests, the software can be tailored for each tenant separately. The system houses the data for each company on a separate server. Each tenant runs its own copy of the software. The separation can be either virtual (virtual machines on a same server) or physical (running on separate machines).
In a Multi-Tenant Cloud based application, the data from multiple companies are placed on the same server generally separated from each other via a simple partition that prevents data to migrate from one company to another. As the data is housed on the same server, each company using the software is running the same basic application, with the same basic functionality and with the same limited configuration capabilities.
What are the potential challenges of migrating into Multi-Tenant architecture?
In many instances the capacity requirements of a small tenant could go below the minimum capacity database thats available. There is an invariable cost to a database and a smaller database does not perk up much in cost to provide benefits.
In cases of larger tenant count, organizing huge independent surfaces leads to issues. While handling thousands of tenants, thousands of databases needs to be created for them so operations scoped globally to address all the data such as schema deployments or queries that need to report size usage per tenant across all databases would take extremely longer durations to work out.
The applications compatible with much larger databases end up creating connection pool fragmentations. Since every server has a single connection in each pool pointing to the individual database that encloses every tenant, so these connections tend to go cold if every application server does not constantly get a request for each tenant recurrently. In such situations the application finds no connection in the pool and hence needs to start the connection all over again creating performance issues.
How does SaaS overcome the challenges?
SaaS loaded with numerous advantages over the legacy applications presents dramatic changes to both the migration and the delivery of the software solution. Some of the key benefits listed are:
SaaS dynamically allows adjusting the number of tenants per database at any moment in time.
Intense packaging of tenants is possible as one is not trapped with a stagnant tenant layout. With this an affordable and dynamic tenant model is available that can regulate increasing workloads in each tenant.
A major advantage with SaaS is it results in cost savings by merging IT resources into a single operation. Since an application incurs an amount of memory which is sizeable when in proportion to many customers, SaaS reduces this operating cost.
SaaS enables data mining. Instead of collecting data from several sources with diverse database schemas, all the data gets saved in a single database schema. As a result, managing queries across customers, mining data, and looking for trends is much simpler.
Improved usability, custom user Interface and branding.
SaaS abridges the release management process as packages containing code and database changes are required to be installed on a single server.
On the whole, SaaS provides an improved deployment of hardware resources and an enhanced simplicity of maintenance, resulting in lower overall application costs. This makes the technology smart for service providers aiming the small and medium enterprise (SME) business segment.