• venu.atcha@vedyainfo.com
  • +91 9908652278
About Us

Case Studies

Case Study I – Documentum with SAP Integration

Client

HESS

Business Challenge

The main objective of the project is to integrate EMC Documentum with SAP to access process documents from SAP to Documentum using ASSAP and CSSAP.

  1. SAP is used as a Front end to access documents and Documentum will be the backend.
  2. Required to archive and store documents in Documentum from sap
  3. Documents metadata should be updated in sap from Documentum
  4. When the document is opened at sap, it should be fetch from Documentum and displayed at sap end
  5. Documents which are imported in sap should be automatically processed to Documentum.
  6. Documents will be in jpeg or pdf formats.

Solutions Offered

  1. Archiving services for SAP is used to integrate sap with Documentum. Documents are imported/uploaded to sap, those documents will be archived and stored in Documentum.
  2. CSSAP (Content Services for SAP) is used to update metadata in sap from Documentum.
  3. Required configurations are done at SAP end to process documents by running job automatically and manually for multiple and single documents.
Case Study 1

Technology Stack

EMC Docuemntum6.5,ASAP6.0,CSSAP6.0.

Case Study II – Proposal of Documentum Upgradation

Client

ITGI

Business Challenge

The main objective of the upgradation is to improve the performance of the all client applications storage and maintenance and making the process easier than previous process.so that the team members can work with more featured functionalities for better results.

  1. First of all reducing the number of servers to avoid miscommunication and making the whole Architecture as simple.
  2. Installing the test environment similar to production and making sure that all permissions given by the server team similar to administrator.
  3. Testing all client applications in test environment and bug fixing of all clients
  4. Checking the compatability of all softwares and making them as compatible.
  5. Finally upgrading the test environment to proposed target version.
  6. Repeating the same process in production and increasing no.of threads to improving performance.

Solutions Offered

  1. Proposed solution is based on arranging test environment with both documentum and database servers similar to the production server
  2. Installing the proposed software versions similar to production,Installing all client applications in test servers and checking the performance of clients.
  3. Testing all clients in all conditions and making sure all are working fine.
  4. Upgrading the test environment to the proposed target versions, installing the clients by doing appropriate changes and again test the client applications.
  5. Raising the proposal for production upgrade by taking down time and repeating the same process in production environment.

Technology Stack

Documentum , db2,Aix

Case Study III - Documentum Collaboration

Client (IREO)

Client is a Real Estate Organization in India.

Business Challenge

Businesshave different Locations, each and every location have their own folder structure, Business requires another folder structure in existing folder structure.

Existing documents are not displayed when user performed search operation based on metadata.

Bulk upload of documents, Hundreds of documents needs to be uploaded to different locations along with metadata at a time.

Solution Offered

  1. Implemented DFC script to Generate folder structure automatically in existing folder structure
  2. Documents are uploaded based on required document type along with metadata
  3. Employees get Authenticated access to the documents according to accessibility rights
  4. Jobs are created to automatically upload hundreds of documents at a time

Technology Stack

Documentum 6.7 SP1Suite of Products. Microsoft Windows 2008 Server, SQL, Apache Tomcat

Case Study IV - Documentum Implementation

Client (IREO)

Client is a Real Estate Organization in India.

Business Challenge

Implementing an automated solution for Document Storage, archival, retrieval, search (meta data) of documents across various departments.

Solution Offered

  1. Employees get Authenticated access to the documents and folders according to accessibility rights.
  2. Uploading of documents through custom applications where in the metadata fields will be populated from the folder structure.
  3. Automatically assigning metadata to common fields for all the documents in a particular folder to minimize the metadata entry.
  4. E-mail Notifications to the respective users whenever a document has been uploaded in the corresponding folders based on their departments.
  5. Well defined folder structure for easily accessing documents across various departments.
  6. Well Designed workflows through which the documents will be routed across different users.
  7. Classification of documents based on the type of the documents.
  8. Well defined naming structure for all the objects that are stored in the repository.
  9. Customized Search applications to easily search for documents based on metadata.
  10. Auto Number generation for creating Employee IDs for the Human Resource department.
  11. Validations and custom error messages wherever required.
  12. Speeding up of document retrieval process.
  13. Easy accessibility of documents from anywhere and anytime.
  14. Generating Reports.

Technology Stack

Documentum 6.6 SP1Suite of Products, Microsoft Windows 2008 Server, Oracle 11g, Apache Tomcat 6

Case Study V – Proposal Process Automation

Client

UNDP

Business Challenge

The main objective of the automation is to track it the process from the initiation till its closure, to provide the collaboration feature so that the team members can work on the same set of documents same time, to have a visual dashboard to get the status of each initiated RFP process.

  1. All the RFP related data like RFP Number, Title, and Date shall be stored in the SharePoint List.
  2. All the RFP templates shall be stored in the Document Library. we propose to leverage Document Set to store all the documents related to the RFP, RFP document and all the responses received against the RFP. There will be a single document set for each RFP.
  3. RFP Creation Form – SharePoint Hosted App will be used to prepare the RFP creation forms. Users can select a RFP template available in the system based on which a new RFP will be created.
  4. Once template RFP is selected, data for all the sections will be pre populated from the template
  5. RFP and the data from the form like RFP Number, Title, etc. Shall be populated in the RFP document.
  6. The team working on the RFP shall be given appropriate rights to access the documents and data.
  7. Once the RFP creation process is completed, read only access will be available on the RFP documents and data.
  8. A custom search form would be provided to search the RFP based on the RFP metadata, like the RFP ID, Submission Date, Project Title, Department, etc.
  9. Users can also search the RFP documents by leveraging the Full text search

Solutions Offered

  1. Proposed solution is based on SharePoint Online platform. We assumed that UNDP has the office 365 and SharePoint online subscription.
  2. Certain features of the website shall be developed using either SharePoint hosted Apps or Provider hosted Apps. UNDP shall provide the required infrastructure and access rights for the App deployments.
  3. PDF files cannot be generated automatically, a .Net program needs to be developed to generate PDF files once the RPF is approved for publishing.
  4. Clicking the Merge File button, all the documents will be merged and generates one merge document. .Net program needs to be developed to generate the merge file.
  5. Few features will be implemented as either SharePoint provided hosted apps needs to be deployed on an Azure server. Thus, a connection to Azure server is required.
case studies

Technology Stack

Sharepoint O365

Case Study VI – Captiva Capture Upgrade Solution

Client

IFFCO-TOKIO General Insurance Co. Ltd

Business Challenge

  1. The Captiva systems are not with the latest versions. The latest versions come with major performance and bug fixes.
  2. Existing environment is using three processes in production which do not have the source code. This makes it impossible for any bug fixes and any future enhancements.
  3. The current process does not support the latest versions of Captiva. So, a complete re implementation of all the three processes from scratch in the new version is required which also address the above issue of source code maintenance.
  4. Currently all the completed tasks in the systems are being deleted manually and this is a tedious job as the system gets hang if the number is too high. The new version supports the automatic deletion of completed tasks which will ease the administration work
  5. Currently there are too many uncleared tasks in the error state. A complete clean-up is required to delete all these tasks. Also there is no proper logging information about the error.
  6. Currently all the integrations with the third party applications are scattered and developed independently outside the system. This makes very difficult as the data is not real time. Also if the integration job fails there is no intimation to the user or administrator about the job failure.

Solutions Offered

  1. Analyzed of current interfaces for Documentum and Enterprise Software Applications.
  2. Analyzed of current interfaces for Documentum and Enterprise Software Applications.
  3. Prepared upgrade templates and required software documentation and project plans, consists of hardware and software specification of current and proposed upgrade system configuration.
  4. Ran Administration jobs such as consistency checker, clean up and file scan to resolve any inconsistencies and remove orphaned and inactive files.
  5. Took all Data and Application Backup.

Technology Stack

Documentum captiva components

Case Study VII – Support Service Solutions

Client

IFFCO-TOKIO General Insurance Co. Ltd

Business Challenge

  1. Analyzing and fixing of any production system related issues.
  2. Monitoring of third party integrations with respect to the Documentum and fixing any minor bugs.
  3. Integrations – Developing of new minor Third party custom applications and integrations with Documentum.
  4. Creating, modifing, or deleting users
  5. Creating, modifing, or deleting groups
  6. Adding users to groups or delete users from groups
  7. Creating, modifing, or deleting roles
  8. Creating a permission set.
  9. Viewing or modifying a permission set.
  10. Adding users to or deleting users from a permission set
  11. Deleting a permission set
  12. Documentum application support issues.

Solutions Offered

  1. The scope includes both support and development activities, as a “Documentum Application Support Project”.
  2. Handled day to day production maintenance activities and supported any immediate Documentum production issues.
  3. Any minor development and integration activities which will not consume much time (as support activates should go in parallel) were Handled.
  4. Handled new requirements by analysing and providing actual project design and time lines taking into support activities into consideration.
  5. Managed to handle production related issues and developments.
  6. Managed Documentum Administration related issues.
  7. Any major third party integration development activities like web services development and third party integration which will consume more time and man power are treated as separate project. All the major development activities are treated as projects and will follow the normal project execution life cycle.

Technology Stack

Documentum components

Copyrights © 2017 All Rights Reserved by Vedya Info Solutions