Documentum Specialist

Seshikiran Gupta

Phone: 704-***-****

Email/Skype: *****.**********@*****.***

LinkedIn: https://www.linkedin.com/in/seshikiran/

Professional Summary:

15+ years of IT experience (including 4yrs at onsite client location in US) in implementing Enterprise Content Management (ECM) solutions with a consistent record of accomplishment in driving & delivering increased levels of productivity, internal/external client satisfaction with good relationship.

Highly energetic and skilled technical leader, experienced in enterprise and systems architecture, application design and mentoring development teams in design, performance, and process.

Strong customer-facing presence, development and administration experience.

My works comprise of different key activities in different projects as a Documentum Developer, Administrator and Support Engineer, also involved in application architecture.

Installation, Configuration, Administration of Documentum Suite of Products like Content Server, D2, D2-Config, Webtop, Documentum Administrator, Records, Composer, Process Builder, Web publisher, xPlore.

Extensive working experience in Development and customization of Documentum based applications using D2, D2-Config, Webtop, Documentum Administrator, xPlore, Composer, WDK, DFC, DQL, API, DFS and Business Objects Framework development (BOF).

Experience in Documentum - D2 4.5 (Worked on Application, Workspace and Widget Configuration, Property Page Configuration, Auto Naming, Auto Linking, Security Model, Template Creation and Configuration, Defining Configuration Matrix).

Experience in Java, JSP, Servlets, JavaScript, Struts, AWT, JDBC, HTML, XML, XSLT, Tag Libraries, SQL and PL/SQL.

Configuring High Availability (HA) and Load Balancing setup.

Have excellent skills on preparing of Technical design documents, and System architecture documents, Training materials, Business Process documents, Data Flow, Architecture, UML diagrams, Process Models and data mapping documents.

Experience in handling Major Release for Mission Critical environment and Incident Management for Production Support.

Plan and manage assigned projects or tasks, including progress reporting and issue/risk management. Organizing resources and establishing priorities.

Good Team player with excellent trouble shooting and problem solving skills.

Managed team of 10 people onsite/offshore developers and support administrators, including team building sessions, KT and self-planned training.

Technical Skills

Content Management Tools (Documentum)

Content Server 7.2, Webtop, DA, Composer, Forms Builder, Process Builder, DAB 5.3 SP3, BPM, DFC, WDK, DQL, IAPI

Programming Languages

Java

Java IDEs

Eclipse IDE, Composer

Java Servers

Tomcat, JBoss (Wildfy)

Framework Technologies

Documentum, J2EE – STRUTS 1.2.7

Web Technologies

Servlets 2.2, JSP 1.2, JavaScript, HTML, XML, XSLT

Versioning Tools

SVN, WinCvs 1.3.17

Other Tools

Samson, dqMan, Toad 9.0

Operating Systems

Windows 10/Windows 7/2003/2000/XP

DBMS Packages

MS-SQL Server 2000, Oracle 10i/9i/8i

Academics:

MSc (Information Systems) from Sri Krishnadevaraya University, AP, India.

Bachelor of Computer Applications (BCA) from Sri Venkateswara University, AP, India.

Project Profile

Project #1

Project : Documentum Implementation

Client : Wells Fargo Securities, Charlotte, NC, USA

Employer : Wipro Technologies, New Jersey, USA

Duration : Feb 2015 – Till Date

Description: The goal of this project is to enhance Wells Fargo Securities (WFS) capabilities in protecting confidential client information and efficiently managing, storing and collaborating documents through the implementation of an Enterprise Content Management (ECM) solution. This system is for specific Securities Wells Fargo team members who work with Deal and Pitch records, have emails or files with business values and sensitivity which need controls to migrate any access violations and records retentions to meet SEC guidelines. This ECM application will be built using Documentum Platform which is an object-oriented system and thus the functionality will be created using what is provided by Documentum software capabilities from Open Text. The solution to be designed for Investment Banking and Capital Markets (IBCM) and Corporate Banking Group (CBG).

WFS currently manages information related to various business activities in shared network drives. While information is categorized in folders and protected through standard user access controls, there are opportunities to improve the organization and management of such documents to improve collaboration and protection of such information.

Responsibilities:

Implementing the Documentum development requirements for the Investment Banking and Capital Markets (IBCM) and Corporate Banking Group (CBG), analyzing the requirements, participate and lead design & development sessions across teams.

Duties also include hands-on programming, making design and architecture decisions from a delivery standpoint, build mock-ups and demonstrate them to the business users and others on the technology team.

Support and maintenance of existing system, mentoring and onboarding of new resources.

Works directly with IBCM & CBG business users and business support with limited or no supervision, and coordinates with various teams in software development and delivery.

Provide on-going support and maintenance on a daily basis and help trouble-shoot production issues and participates in Business Continuity Plan (BCP) related activities.

Effectively co-ordinate development team releases with the BA (Business Analyst), QA (Quality Analyst), Release Manager and Technology Managers.

Support technology managers on assessing and supporting all of the risks associated with Enterprise wide security requirements in alignment with LOB objectivities.

Identify, assesses and solve complex business problems, where analysis of situations or data requires an in-depth evaluation of variable factors.

Follow the strategic direction set by senior management when establishing near term goals, although having some latitude in decision-making.

Candidate would act independently to determine methods and procedures on new assignments taking in consideration the diverse integration points with other systems and Documentum components - decisions have a major day to day impact on area of responsibility.

To provide technical leadership to the onshore and offshore teams.

Installation and configuration of the various Documentum products such as D2, DA, Composer, xPlore, Content Server.

Configuration of the various third party tools with Documentum products such as COSI Insight, Salesforce, Bloomberg, and FactSet.

Interacting with multiple teams to trouble-shoot the issues related to environment OS/Network/Firmware/AD-ENT/NAS as well as with product vendor (Open Text) for the Documentum platform related challenges

Troubleshooting the RAC (Root Cause Analysis) for application related issues and fixing them, if required, by engaging cross functional teams and tracking till the issue is completely resolved and closed.

Environment: Java 1.8.0_40, Content Server 7.1, Tomcat 7.0.42, JBoss 7.1.1, D2 4.2, DFC, DQL, API.

Project #2

Project : BIP Digital Archive for CJL

Client : CITIBank, Bangalore, India

Employer : Wipro Technologies, Bangalore, India

Duration : Jul 2014 – Oct 2014

Description: The purpose of BIP (Business Improvement Plan) project is to digitalize the unified standards for all of the materials related to the historical FSA inspections that have been organized to date, by archiving them into Documentum content repository. Also provides an environment that allows for constant and ongoing usage within the bank, mainly by the CAP (Corrective Action Plan) owners. To improve practical preventive measures, retaining effective and persistent 'organizational records and memory'.

Responsibilities:

Access to this application is limited to particular users (cjl_bu_role, cjl_bspd_role, etc

Developed Bulk Upload utility to import the documents along with setting the metadata.

oExports the metadata (in excel format, Sheet names as custom object type and column names as the custom attributes) and content (in zip format) to temp folder.

oExtracts the zip file and uploads the documents by traversing the excel sheet for the folder path and metadata to set.

oIf the document with the same name already exists, it creates a minor version. Also updates the version label as "Under Review".

oOnce all documents are uploaded

Deletes the temporary objects created in the local file system and the metadata sheet in the docbase.

Sends an email to requester about the status of execution along with mail attachment

Sends an email to the approver with the list of documents and their DRLs to approve all these documents so as to make them available to the application users.

Reports – Generates (in excel format) and disposition the old report

oMetadata Reports - Generates on daily basis

5 reports based on the custom object types by querying the custom attributes

oMatrix Reports - Generates on monthly basis

Group name with users list report from dm_user & dm_group

Open files report (User name, Document opened/viewed) from dm_audittrail

Change Request report from cjl_change_request (New docs or metadata change)

Developed a custom component to manage Ambiguity Words for the Xplore search engine. The component facilitates to send an email request with the list of words to add or delete to/from the Ambiguity list.

Customized the Advance Search to facilitate

oLimited the access scope to cjl_bu_role and cjl_bspd_role

oObject type limited to only custom object types

oProperties limited to custom attributes and populates based on the object type

oSearch results page to display only the custom attributes based on the object type

Customized the Smart Navigation to add the custom attributes (default attributes are Author, Owner and Modified) in the clusters.

Environment: Java 1.5.0_22, Content Server 6.7, Webtop 6.7, Tomcat 6.0.28, DFC 6.5.0.225 SP2, DQL, WDK.

Project #3

Project : Invoice migration to ECM

Client : Thames Water, Hyderabad, India

Employer : Wipro Technologies, Bangalore, India

Duration : Jan 2014 – Jun 2014

Description: The invoice images are currently stored in database server (from Bottomline) and are available for retrieval by Thames Water employees. The database server is de-commissioned and these invoices are required to be migrated to Thames Water’s content server which is ECM. Some of the invoices have links to SAP and those has to be migrated to the existing ECM repository and the remaining 3 million invoices has to be moved to new repository along with updating the meta-data. The invoices are provided in an external hard disk and meta-data is provided in CSV format. The invoices with SAP links has to be accessed from SAP GUI and other invoices from Webtop. All the invoices are accessible through navigating to the folder path and from Advance Search. All the invoices are Read-only as they are historical data.

Responsibilities:

Involved in requirements gathering and understood how this application suits their business

Created a new repository (ECM_LEGACY) to store all the invoices as they are Read-only nature

Created a new cabinet and a folder to store the invoices

Created a new object type and an ACL to reflect the Read-only permission

Developed the DFC code to import the invoices into ECM_LEGACY, on successful import applied the meta-data by reading from the CSV file provided by the business

Prepared all the technical and functional documents as per the business requirements

Environment: Java 1.5.0_22, Content Server 6.7, Webtop 6.7, Tomcat 6.0.28, DFC 6.5.0.225 SP2, DQL, WDK.

Project #4

Project : BaxEDGE (Electronic Documents for a Global Environment) DMS

Client : Baxter, Bangalore, India

Employer : Wipro Technologies, Bangalore, India

Duration : Jun 2013 – Jan 2014

Description: BaxEDGE is a new solution for managing global content for electronic/paper submission to FDA, EMEA etc... This application is designed to provide the complete solution from content creation to publishing submission implementing the latest technologies (eCTDXPress, ISIPublisher, ISI Submission, A4L, ALiCE) available for the submission purpose. BaxEDGE DMS is the document management component of the BaxEDGE suite. BaxEDGE DMS also referred as FirstDoc is a web based application that provides users the ability to upload, download and manage documents directly from a web browser. FirstDoc provides users the ability to manage their submission related electronic documents via a central secure repository with version control to maintain document integrity and predefined workflows to optimize the authoring, reviewing and approval process. All documents that has been submitted or a correspondence received from/sent to the regulatory agencies are imported into BaxEDGE DMS.

Responsibilities:

Clearing of the working data created (documents, inbox items, searches, home cabinets) by the training users under the training cabinets.

Restore of staged documents for all the training users in training environment.

Created the saved searches (custom & quick search) listing all "staged" documents to all users.

Facilitating to view the staged document(s) under 'My Files' and 'My Views' (10 views).

Facilitating to view the Workflow item(s) in their Inbox.

Create staged document(s) under pre-determined cabinets.

Email notification(s) for intimation and on the success/failure of the cleanup and baseline restore.

Updating the custom attributes specific to application as per the business scenario.

Environment: FirstDoc 6.2, Java 1.5.0_22, Content Server 6.7, Webtop 6.7, Tomcat 6.0.28, DFC 6.5.0.225 SP2, DQL, WDK.

Project #5

Project : IMMS 5.0 (International Module Management System 5.0)

Client : GSK (GlaxoSmithKline), Bangalore, India

Employer : Wipro Technologies, Bangalore, India

Duration : Jul 2012 – April 2013

Description: The proposed solution is a Document Management application for the GSK module management. IMMS manages (creation, approval, archival and removal) modules (a file of any type) for regulatory and non-regulatory business groups. Each business group has its own top level cabinet containing folders and modules. Modules are created from standard templates. This application is having integration with the different documentum (ADA, PIER, etc.) and non-documentum applications (Liquent, iSign, etc.).

Responsibilities:

Assigning the work to the team.

Making the team understand the requirements.

Enabling the team to work on the task as per the requirements.

Ensuring not to have any knowledge gap for team while working on the requirements.

Arranging the daily and weekly status calls with onsite and offshore.

Preparing the required artifacts/documents related to the project management and application management.

Environment: Java 1.5.0_22, Content Server 6.7, Webtop 6.7, Tomcat 6.0.28, DFC 6.5.0.225 SP2, DQL, WDK.

Project #6

Project : WCC BPaaS (POC)

Client : Wipro BPO, Bangalore, India

Employer : Wipro Technologies, Bangalore, India

Duration : May 2012 – Jul 2012

Description: The proposed solution is a Case Management application for the HR BPO Process (New Hire Process). The initiation of the process is based on FTP (Offline form) or HTTP (Online request) or SMTP (email). Once the application is received the Lead can see the details of the application and also monitors the case status. Agent has to explicitly get the task into his inbox (only 1 at a time) and once he acquires, the case opens in a frame with metadata (left frame) along with the submitted form (right frame). Agent can approve the task or escalate to lead. Lead can either provides clarification on the escalated task or he himself can acquire it and approves it. Once the lead provides clarification the escalated task again it moves back to the queue and the next available agent will get this task. Once Agent/Lead approves the tasks some of the submitted tasks go to QC for quality review and once the QC reviews and approves the Offer letter is generated and a notification email is send to Recruiter, HR and candidate.

Responsibilities:

Configuring the SMTP and POP3 for inbound and outbound emails.

Configuring the Process Data Mapping with the package elements.

Customized the agent login screen to select the customer and process.

Developed the business process using the Process builder based on business requirement.

Developed different Forms (Document View, Folder Contents, Tasks, Task List) to display the UI relevant to Case Management application.

Created and configured the tabs in taskspace with forms created using form builder.

Environment: xCP 1.5 (which includes Taskspace, Process Builder, Form Builder, PRS, BAM, DA)

Project #7

Project : OPR Presales (Opportunities and Projects)

Client : EMC2, Bangalore, India

Employer : Wipro Technologies, Bangalore, India

Duration : Nov 2011 – Apr 2012

Description: Opportunity data from Salesforce.com (SFDC) will be migrated over to ECM once an Opportunity is submitted to quote. The migration will bring over the final version of all documents attached to the Attachment’s section of the Opportunity. While migrating the data, ECM will create an Opportunity level folder with the same name as the Opportunity in SFDC. These documents will be non editable and non delete-able.

The proposed application is customized layer on top of default Webtop with a collection of custom and new components like Project Folder Creation, Managing Many to Many Relations, Attribute Inheritance. TS delivery users will use ECM to store project related documents and to collaborate on documents. Project Managers will be able to create multiple project folders associated with Opportunities.

Responsibilities:

Developed a new component for Smart Navigation functionality to manage the relationships between projects and opportunities.

New component is developed to modify/manage relationship objects among projects and opportunities.

New document, folder and import components are customized to limit object type selection.

Import rendition component is customized to change drag and drop functionality; if a user drops a file over a file with same name then new file will be imported as new version.

Docbase object configuration component is customized to enable the show discussion checkbox by default in the property page.

Delete folder component is customized to update the attributes of the project_doc or opportunity_doc if a link is deleted in the sub folder.

Advsearch component is customized to restrict the object types to prj_form, opr_folder, opr_doc and dmc_comment.

Environment: Java 1.5.0_22, Content Server 6.5.0.038, Webtop 6.5.0.221, Composer 6.5 SP2 (eclipse 3.4.0), Tomcat 6.0.28, DFC 6.5.0.225 SP2, DQL, WDK.

Project #8

Project : RADAR Plus

Client : Biogen IDec

Employer : Wipro Technologies, Bangalore, India

Duration : June 2011 – Nov 2011

Description: RADAR is an electronic repository for Central Clinical Files (CCF) built on top of Documentum. The current RADAR system relies on the scanning of paper records along with attributing and indexing using the Kofax Ascent Capture application, with a combination of free text and pick list entries. The proposed new solution helps to converts business critical information from paper or electronic sources into digital content and delivers it to RADAR back-end systems.

Responsibilities:

Developed a new component to add, delete and update all Pick List values.

Developed a new component to enable and disable user entry fields based on the selected transmittal type (Input Type like Protocol, Investigator and Program).

Worked on renditions to convert documents to PDF before sending for QC Testing.

Unique Record Id’s are created for each record that gets created in the system.

Involved in developing a component to duplicate an existing transmittal so that a new transmittal can be created from existing transmittal without entering values again.

Users can print the transmittal cover page for each document with attribute values.

Users can print all transmittal cover pages at a time.

Audit trail entry is made for every document imported, uploaded (electronic) including emails / bulk import and also for QC check pass / fail step.

Environment: Java 1.5.0_22, Content Server 6.5.0.038, Webtop 6.5.0.221, Composer 6.5 SP2 (eclipse 3.4.0), Tomcat 6.0.28, DFC 6.5.0.225 SP2, DQL, WDK.

Project #9

Project : Policies & Procedures Framework

Client : World Bank Group (International Finance Corporation)

Employer : Mphasis Limited, Bangalore, India

Duration : Dec 2010 – June 2011

Description: The Policies and Procedures Application is an IFC Legal department’s initiative aimed at providing Documentum based content management and storage capabilities to manage the IFC normative documents (policies, directives, rules, procedures, guidelines), and supporting documents (forms, templates, spreadsheets etc) throughout their lifecycle from authoring to approval, publishing, expiration and archival. The current processes pose certain control risks because of the fact that currently, IFC documents are stored on shared drives and in e-mails. The access control, version control and change audit rely on manual processes and the document state is not centrally tracked.

The new application will centralize and standardize the content management and storage process across the Legal department by providing common repository to store all IFC normative documents and templates, also has the integrated document lifecycle and ability to track the document status. Also provides ability to track document versions and audit document changes.

Responsibilities:

The drag-and-drop of documents between folders is disabled. The only way to move documents between folders must be via the document lifecycle state change.

Drag and Drop would only be enabled for ‘Supporting Documents’ folder and its sub folders.

Disabled the clipboard option to avoid use of copy, move and link menu options.

The attributes of a subfolder under 'Supporting Documents' folder can only be modified by members of P&P Unit group.

The attributes of all folders/sub-folders under the ‘Policies and Procedures’ Cabinet can’t be modified by any users.

No user would have the permission to create sub folders except under 'Supporting Documents’ folder and is restricted to type 'pp_folder'.

As a repository level restriction, the ‘cabinet creation’ under ‘Policies and Procedures’ cabinet is disabled for all users.

In the document creation/import process on save, it converts automatically into a virtual document and then the implementation memo template would be attached to the virtual document. Also, the naming convention of the attached memo template will change as <Main Document Name>_<Implementation Memo>.

Users are restricted to create/import documents only under Draft folder.

The document names should be unique and shall not be editable once the document reaches Approved state. Components customized are – Create, Import and Document Properties Component.

During a new document creation, selecting ‘Format’ option is not needed before showing the list of templates to be selected. Set default format to MS Word 2007.

In case of a supporting document, ‘owner’ attribute value should be ‘P&P Unit’ but the ‘creator’ attribute should be ‘Sponsoring Unit’.

Whenever a document is moved in Published folder, application logic checks for and moves any previous versions of the document available in ‘Published’ folder to ‘Archived’ folder i.e. at anytime, no two versions of the same document should be available inside ‘Published’ folder.

Once any document is in ‘Published’ or ‘Archived’ state, a snapshot should be taken and that should be frozen. And the original document should be hidden from the users.

Once user selects the ‘Create New Version’ option on the snapshot in ‘Published’ or ‘Archived’ state, a new major version of the parent virtual document (parent document, attached memo document and any attached supporting documents) is created and moved to Draft folder, while old version’s location is still in ‘Published’ or ‘Archived’ folder.

On moving a Document across folders, User should be prompted with a Dialog box asking for confirmation with a mandatory field for comments. Custom attribute ‘pp_user_comments’ would be used for this purpose.

On moving a Document across folders, application send the automatic email notifications on specific events (create/import/move to/return to) to corresponding users.

Environment: Java 1.5.0_22, Content Server 6.5.0.038, Webtop 6.5.0.221, Composer 6.5 SP2 (eclipse 3.4.0), Tomcat 6.0.28, DFC 6.5.0.225 SP2, DQL, WDK.

Project #10

Project : Livelink to EDM Migration

Client : Cisco Systems, Inc.

Employer : Mahindra Satyam, Hyderabad, India

Duration : Mar 2010 – Nov 2010

Description: This migration approach is for the replacement of the Livelink with EDM system. The migration is based on the batches created using the Livelink Migration Tool. This tool is specifically designed for the Livelink users to create the batches of data they want to migrate to EDM. Once the batch is created, using the framework the content, meta-data and versions are moved to the EDM along with the user permissions on the data. Only the in-scope-objects (workspaces, folders, documents, compound documents, aliases & urls) will be considered for migration and the rest are treated as out-of-scope objects for migration. The migration scripts are supposed to move around 700GB of data. Considering the number of pre and post processing required on the content as it involves calling SBO for customization of rooms.

The migration database is populated with the objects that need to be migrated from Livelink along with the meta-data and keep the migration database in sync with regular updates on the Livelink based on the livelink base tables (Dtree, Dtreeacl, Dversdata, Kuaf, Kuafchildren, and Kmproviderdata).

Responsibilities:

Involved in developing the GUI for Livelink users to create batches of data to migrate to EDM called Livelink Migration Tracking Tool.

This tool is used to create new batches, edit/delete the existing batches; also we can check the status of the existing batch (Not Started, In Progress, and Completed).

If the migration status is “Not Started” then user can Edit or Delete the batch which makes the application user friendly.

The tool gives the option to the user to exclude a project workspace or a folder from the migration batch. All the excluded content gets purged after migration.

Developed the validation code for the migrated data to check whether the users with permissions in Livelink are migrated correctly or not.

Implemented the Session management for handling the checkbox validations throughout the application.

Involved in developing the framework code.

Coded the validation module which is to be used at each step of the migration for testing the user permissions applied using the SBO method.

Environment: Content Server 6.5, Composer 6.5, DFC, DQL, API, Java, JSP, Struts 1.2.7, Samson, Toad for oracle 9.0 and Oracle 10i.

Project #11

Project : QTC - iFAX – SAJO (Scientific Atlanta Joint Orderability)

Client : Cisco Systems, Inc.

Employer : Mahindra Satyam, Hyderabad, India

Duration : Sep 2009 – Feb 2010

Description: The goal of this project is to allow the Scientific Atlanta (SA) orders received via Fax and EDI orders received as email to be processed just as the Cisco fax/email orders which are as processed in iFax application currently. Processing of SA fax orders in iFax involves the receiving of fax orders in inbound queues, assigning key attributes, routing to team queues manually, assigning folder attributes and filing(archiving) the orders. The Fax or EDI orders will be processed as per the current process in iFax, using the existing functionality that exists in iFax.

Responsibilities:

Created Work Queues, Priorities, and Categories and assigning them to relevant Queues.

Created Users, Groups, Roles, adding Roles to Work Groups and the mapping of the Work Queue tasklist with custom form (using TaskSpace)

Involved in the designing of the workflow routing using Process Builder.

Configured different activities (FTP Inbound Initiate, Email Inbound Initiate) for picking up and routing the documents (Fax or eMail) from Fax Server and eMail Server to the relevant Work Queues.

A workflow is started once there is a document or eMail found in Fax/eMail server

The Fax is routed to relevant Queue based on Fax numbers

The eMails are routed to relevant Queues based on the Mailer Alias and the subject line.

Some of the attributes of the document can be edited and the document is manually moved from Inbound Queues to Team Queues based on the CSR Team attribute.

All the deleted documents in the Queues are moved to Trash (Inbound/Team) Queue and can be retrieved back within 7 business days otherwise they are deleted from the system.

For the Inbound Queues the split option is available only for .tiff files and those split documents are moved to the same Queue and a separate workflow is started so that we can see a new entry in the Queue.

For the Team Queues the split option is available only for .tiff files and those split documents are placed under the same folder and no workflow is started.

The document is moved to archive once the document is processed in the Team Queue.

Designed some forms for the inbound queues and team queues using Form Builder.

Environment: Content Server 6.5 SP1, TaskSpace 6.5, Composer 6.5, Process Builder 6.5, Forms Builder 6.5, J2SE 1.6.0.

Project #12

Project : QTC - iFAX - Migration (Phase-2)

Contact this candidate