The extensive procedural requirements of the U.S. courts for companies active on the American market were in place even before the recent Volkswagen exhaust scandal. However, the life sciences sector is affected by the e-discovery requirements just as much if not more so than the automotive industry that is currently the focus of attention. Plaintiffs were granted powers similar to those of state prosecutors with the amendment of the Federal Rules of Civil Procedure (FRCP) in 2006 – and not only in product liability lawsuits. Requests for information were expanded to include electronically stored information (ESI) which has far-reaching consequences for how information is handled in the company. A plaintiff (with the support of the courts) may demand the surrender of all relevant ESI from the defendant. This applies to standard e-mails as well as Office documents and text messages on smartphones, online content, and social media posts. Failure to deliver the information within the imposed deadlines or even the inability to identify relevant information and safeguard it against changes can lead to heavy penalties and the loss of the case, regardless of how the evidence may point. Public authorities and other jurisdictions are increasingly expecting compliance with e-discovery standards within the scope of requests and investigations as well. Only certain procedures are now being accepted for internal searches and the evaluations of documents. read more
Maintaining a silo with millions and billions of documents is a huge challenge. At some point the need to make changes to the system configuration, metadata and object model or even to the physical environment, either in terms of hardware or with software- version upgrades might arise.
Usually this does not seem to be a very big deal since there are plenty of migration tools and products out there specifically designed for such a task. The obvious way is to put the corresponding system in read-only mode, do necessary changes and/or upgrades, move documents from A to B and activate the new platform. (In fact this is not as easy as one may think- but that is another story)
But what happens if there is no option for a large maintenance time-frame? No option for a single system-downtime at all? There may be situations where the system must be up and running for nearly 24 hours a day, seven days a week…
Good news is there are two approaches how such requirements can be met. The first one, compared to the other, will take a lot of time but makes it theoretically possible to migrate without a single second of downtime. read more
Virtually every industry is currently facing the challenge of digital transformation, including the life sciences sector.
But what exactly does the digital transformation entail and what consequences does it have?
When it comes to digital transformation, we talk about the ‘third wave’ of IT. The first wave was the introduction of the server-client architecture which followed the mainframe principle. The second wave was Internet technology, and we are now talking about a third wave, that being smart, networked devices.
As I see it, digital transformation is based on two main pillars:
- On the one hand, we are finding that the pace of sensor development is gaining speed. They are becoming more accurate, more specialized, and more compact. But most of all, they are growing more affordable, meaning they can even be used as disposable products. Sensors are used everywhere, whether in industry, in cars, at home, or in the field of medicine. They measure sounds, vibrations, movements, temperature, pressure, humidity, and much more.
- The second factor is that IT is now readily available and easy to consume in any quality and quantity and at any time. The vast amount of data produced by sensors, mobile end devices, traffic management systems, and much more can nowadays easily be stored centrally and can be analyzed in a matter of seconds, in some cases even in real time. Correlations obtained from these data produce unprecedented findings about such matters as production processes, causes of illnesses, and the usage of wearables.
The digital transformation is driving industry change
These new findings are putting many companies in a position to rethink their business processes and models: read more
There are different ways of how to manage documents using Document Management Systems (DMS). Which one is the best for your company? This blog discusses the question if it makes sense to manage the full document lifecycle in the DMS, or if only the most important document versions should be stored in a DMS, having the other documents created, managed and stored in other places.
I vote for the full approach. Why?
It is the collaboration idea that requires multiple users to work with the same document and have a full version history of information for all previous versions. The benefit of using a transparent chain of document versions is often underestimated. Even SharePoint technology is using this feature.
Document Management Phases
In the creation phase, Document Management Processes have special document access rights, which need to be considered differently, as you do not want to distribute the document to a larger audience, but at the same time you like to collaborate with the group of authors.
At this stage the system must be very flexible and user-centric. The focus here is on user interactions, where you prepare all meta-information in an intuitive way. This changes, when the document itself needs to step into a higher status and when leaving the authoring phase.
Now, it is more important that the document is following a workflow process for reviewing the document using the 4-eyes principle. And last but not least now follows the approval of the document for a designated business reason decided by a group of persons – the Approvers. read more
DIFFERENT SOLUTION APPROACHES
When the URL consists of the physical host name
Assign the old physical host name additionally to the new hardware (host) and define a new virtual host in the JSP container handling the requests targeted to the old host name (Figure 1 ) or handle all requests to the old host names by a dedicated server (host). This dedicated server redirects the requests to the new web server host (Figure 2).
When the URL consists of a DNS alias (instead of a physical host name)
This DNS alias is switched from the old host to the new host (Figure 3). The DRL / link component inside the appropriate web application is subject to being updated. This new DRL / link component is able to identify »old« object IDs either by the repository ID portion of the object ID (the repository ID is part of the object ID) or by querying the Documentum repository for the old object ID.
Fig. 3 Redirections handled by a dedicated server
HANDLING OF COMPLEX CASES
When a single cabinet is moved from one repository into another
The redirection logic have to be handled by specific code. In case the object ID has not been found within the source repository, specific target repositories are queried for the old object ID.
A lot of complex cases and the cases are not homogenous
A centralized Oracle table could hold all information regarding old object IDs mapped to new object IDs. This Oracle table might be queried by the redirector code to obtain the new object ID. By the repository ID portion of the object IDs, the redirector might also be able to identify the repository holding the corresponding object.
fme now incorporates 17 years of project experience in the field of migrating applications, content and data. Our migration experts have developed best practice methods and various solutions which can be applied to different system architectures in order to fix broken links. If you need further Information please contact us – we welcome any challenge!
For detailed information see our technical white paper