![]() SharePoint has provided the flexibility, and KnowledgeLake auto-indexing has allowed the convenience. We have two dozen content types on auto-assist already. NET development staff could create web services to reach into SAP and pull out indexing values for auto-assist. He continued, “From an auto-assist perspective, because of SharePoint’s power, our own. Now SAP dumps thousands of documents in batch jobs into the Capture server, and Capture picks them up and puts them away,” said Michael Mead. Because of the easy way KnowledgeLake Capture works, our SAP developers could create PDFs with XML in the form the Capture server expects. “It was very critical that we could handle auto-assist and full auto indexing of content types exported from SAP. KnowledgeLake representatives demonstrated Capture, Connect, and Imaging tools while also discussing the benefits of making use of Dart’s existing investments in SharePoint First to a small group of Dart managers, and then to a wider user-base audience. The KnowledgeLake onsite demos showed the power of a flexible solution. In the project’s initial stages, Concurrency consultants worked with Dart staff to plan site collections and establish a detailed taxonomy of content types. “We decided to take the opportunity to learn about SharePoint and configure correctly for a true ECM environment,” said Michael. Michael and his team turned to Concurrency, Inc., both a Microsoft Partner and KnowledgeLake Partner, for assistance with designing and deploying the SharePoint-based solution, including preparation for integration with SAP, Dart’s chosen ERP platform. Dart requested KnowledgeLake to demonstrate its ECM solutions based on the SharePoint platform. As an alternative to standalone ECM platforms, Michael and his team investigated how Dart might extend its use of SharePoint, a product the company already owned. Also, those systems would have required additional servers dedicated to imaging. Michael and his team considered IBM’s FileNet and EMC’s Documentum but found these platforms to be limited in their potential for integration with ERP systems. Michael and his team sought an approach that would further reduce manual processes, establish workflows, accommodate additional documents types, and integrate with the company’s enterprise resource planning (ERP) system. Dart needed to ensure access to their documents for years to come and this was in jeopardy with the current IBM system. Dart brought in KnowledgeLake’s Professional Services team to migrate over 16,000,000 documents from their current IBM system into SharePoint. ![]() Another factor influencing Dart’s decision was that their current IBM CM environment was aging and their service contract was set to expire. The new system would need to handle over 16 million documents migrated from the old system and ongoing additions of 30,000-40,000 documents per month. Michael Mead, Manager of Emerging Technologies at Dart, led a strategic examination of upgrade paths. Dart’s legacy IBM system, which the company had used since the 1990s, saved images to an optical platter device that was no longer supported. ![]() Dart Container Corporation needed to replace a legacy imaging system used for wide-ranging document types such as payroll, benefits, sales, vendor records, and HIPPA-covered records. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |