TSG is happy to announce the Spring 2019 release, version 3.2, of the OpenContent Management Suite (OCMS)! For this post, we will take a look at some of the new features and notable enhancements included in the 3.2 release.
Amazon DynamoDB Support
The biggest addition to OCMS in the 3.2 release is our new support for utilizing Amazon DynamoDB as an ECM repository. As part of the initial development, we have successfully executed an 11 Billion document benchmark. Utilizing the power of OpenMigrate and NoSQL, we were able to achieve an ingestion rate of over 20,000 documents per second and have recently updated the benchmark environment to allow users to add documents through the OCMS interface. In our most recent post, we detailed our success with load and performance testing with 11,000 users.
With the addition of DynamoDB, the OCMS high level architecture is now:
The 3.2 release brought a number of new enhancements to OCMS around document redactions. Specifically, the ability to bulk redact documents across a case folder based on document metadata. For example, in a medical claim, OCMS can redact all documents containing the value of the case’s Claimant Name value. Another scenario would be to search for the claimant name across the repository and then bulk redact that value in documents across claim folders. See the blog posts linked for more details and to watch a video of the bulk redaction functionality in action.
In the TSG Compliance Solution, it can be helpful to quickly search to find documents that are impacted by a change to another document. For example, if a nuclear procedure document, PROC-1234, needs to be updated based on a plant change, it is helpful to see all other procedure documents that reference PROC-1234. This allows the document editor to efficiently verify which other documents in the repository, if any, need to be updated as part of the Change Request. Here’s how the impact assessment works:
In this Change Request, we’re making an update to the TSG-104 procedure document. Utilizing the Generate Impact Assessment action:
The system automatically searches for other procedure documents that reference ‘TSG-104’. The results are presented in a spreadsheet:
In the above spreadsheet, notice column K. This configuration allows the user to review the documents, mark whether or not the documents are acceptable as is (or not), and attach the spreadsheet as a supporting document to the Change Request form governing this change process.
When working with video, especially in insurance scenarios, it can be helpful to merge multiple videos into one. TSG worked with the Michigan State Capstone Experience to explore how users can efficiently capture and share video from multiple cameras. Part of this effort involved adding the ability to merge more than one video into on in OCMS. Read more about it on this blog entry from April 2019.
As part of our R&D efforts with Amazon Textract, we have enhanced the indexing capabilities within OCMS as well. While indexing a document into the repository, the user can now simply double click the document to automatically pull metadata values to the indexing form. Check out this blog post for more details, but here is a quick demo of it in action:T
Alfresco 6.1 Compatibility
As part of the 3.2 release, we’re happy to announce that OCMS is now compatible with Alfresco 6.1, while also maintaining backwards compatibility for Alfresco 5.1 and above.
While not an exhaustive list, here are a few other notable enhancements made to OCMS during the 3.2 release:
- Workshare Compare Integration – Previously, OCMS allowed the user to choose two versions of a single document to compare. The 3.2 release adds the ability for the user to send two separate documents to Workshare Compare to generate redline differences.
- View All Documents – In OpenContent Case, typically the interface loads with displaying the case documents in the case folder. This works great when the repository has been organized where all documents related to a given case are stored in a single folder. However, we have run into situations where some case documents are spread out in the repository. With the 3.2 release, the View All Documents action can be configured to run a search across folders to address this scenario.
- Export Search Results – in the 3.2 release, search results can be exported to PDF as well as Excel
Thank you to all TSG clients who helped improve OCMS in the 3.2 release! Keep an eye on our blog for more information and insights into what is coming up in the 3.3 release, planned for Fall 2019. So far, we’re planning on expanding our support for DynamoDB, improving OpenContent Search on mobile devices, and continuing to leverage Machine Learning and Amazon Textract to improve document indexing. Let us know your thoughts below.
Leave a Reply