OBJECTIVE

• In recent assignments, his approach for access to basic content storage, library services, full-text search, and workflow has been more towards SOA using DFS.
• He has worked in all capacities/roles starting from Architect, Developer, Administrator and Tester for large Documentum based implementation projects.

Project 1

Project Objective

The aim of the project is to automate approval process of Investment Operations and Advisory Services projects.

Project Description

IFCDocs application provides Content and Business Process Management for IFC Business users. Scope of the project includes Development and Enhancements in quarterly releases and 24X7 support of the IFCDocs system. EMC Documentum product suite is used for both Content Business Process Management.

Roles and Responsibilities

• My responsibility as Onsite Technical Lead includes.

• Solution and Design of Business approval process, content management features and integration with external systems/applications iDesk, ASOP and Lotus Notes.

• Estimation for new enhancements.

• Enhancement in Mobile application developed in Sencha touch and Rest services.

• Requirement gathering and Impact analysis for quarterly maintenance release cycle.

• Deliverables Review Code, Documents .

• Project plan.

• Project Weekly Status.

• Onsite and Offshore coordination.

• Coordination with Quality assurance team.

• Problem Management Identify the recurring problem and propose permanent fix either as a hot fix release or as part of Enhancement release.

• Release management.

• Change management.

Project 2

Project Description

FME Migration Center tool is used to migrate documents from J-IMMS to G-IMMS. Both Source and Target repositories are EMC Documentum repositories. Migration scope includes Virtual documents. The number of documents to be migrated is around 4 lakhs. Any post migration issues are fixed by executing custom utilities.

Roles and Responsibilities

• Performing a gap analysis and assessment to determine completeness of server, storage and network equipment information.

• Developing the migration strategy, Data Migration and Test plan, sequencing, dependencies, timeline, and fallback strategies based on the association of physical and logical assets which support the Client's business functions.

• Design Mapping specification and transformational rules.

• Developing migration workbooks for each migration event which detail the necessary tasks for a successful migration.

• Set up and Configure FME-MC tool for migration sets.

• Coordination with GSK shared resources.

• Transition knowledge to the GSK support team.

Project 3

Project Description

• Provide an application that can operate in a GxP compliant environment including

• Module creation, importing, identification, editing, secure storage, review, status

• The International Module Management System IMMS provides the functionality to
• manage the preparation of Modules and Collections prior to submission.
• IMMS supports the following functions:
• change, searching and availability for publishing. The management of development
• project documents other than Modules is permitted where this does not impact the
• requirements of IMMS. Any system capable of generating text or graphic data
• reports could feed that information into IMMS in the form of a module.
• the provision of validation documentation. This will not specifically include provision
• for electronic signatures as required by FDA 21 CFR Part 11 this will be catered for
• by integration with GSK's iSign application.

Roles and Responsibilities

• Design and develop Bulk Loader engine consisting of two Documentum jobs scheduled to run on a daily basis for bulk uploading batches into the IMMS repository.

• Complete deployment executions as per GSK processes which include preparing Work Plan , Technical Installation Plan and Technical Installation Reports .

• High Availability tests of each system component.

• Coordination with GSK shared resources.

• Transition knowledge to the GSK support team.

• Architecting overall IMMS enterprise application performance improvement and resolving critical issues.

Project 4

Project Objective

Sign used to run on Tricipher's Vendor appliances which had very old version of Unix, Java, Tomcat, Web Server and Database MySQL running. The project objective is to

1. Design and implement iSign on a new GSK hardware Infrastructure by eliminating Tricipher's Vendor appliances.

2. Run it on new software components like Red Hat Linux 6, Oracle 11.2g, Apache Tomcat 6.0.35 and Apache Web Server 2.4.2.

3. Deploy latest 1.1.5 MySignatureBook and customize it for GSK.

4. Migrate data from MySQL to Oracle.

Project Description

iSign is an online digital signature workflow solution that manages the collection and application of digital signatures to PDF documents using Adobe Reader. The ability to leverage SAFE-BioPharma credentials for signing allows iSign to manage the signature process for many regulated and highly sensitive documents that are incredibly common to the life sciences industry. PDF Documents in iSign can be uploaded via the application itself or via IMMS, an EMC Webtop based solution using the available iSign Web Services interface. Once everybody signs the PDF document, it is put back into IMMS. Roles and Responsibilities

As Tech Lead, following were my roles and responsibilities.

• Prepare Solution Design Document for the

• iSign upgrade from 1.1.2 to 1.1.5.

• Hardware and Software infrastructure upgrades.

• Data migration from MySQL to Oracle.

• Prepare Work Plan, Technical Installation Plan and Technical Installation Report.

• Prepare Data migration plan from MySQL to Oracle.

• Configure F5 Load balancer and SSL setup.

• Install iSign on Dev, Val and Prod servers.

• Ensure Web Application Development Standard and Security Testing criteria are met.

• Coordination with the vendor Taigle.

• Transition knowledge to the GSK support team.

Project 5

Project Objective

The project objective is

• Installation of ISI Publication Suite 3.2.6.2 in the Development, Validation and Production environment. It was a fresh install as upgrading to both Windows Server 2003 and Citrix XenApp 5 required complete wipeout. This was an upgrade installation impacting all assets including Citrix, Web and Agent servers.

• Performance improvement by

• Introducing multiple local Session agents.

• Introducing multiple local DMS agents.

• Eliminating Web Server.

• Adding more Citrix servers to the Farm.

• Upgrade DFC to 6.5 SP2

Project Description

ISI eCTDXPress and Publisher in the ISI Regulatory Solutions Suite offers one integrated solution with the functionality to create any submission format eCTD, NeeS, ACTD and paper as well as comply with evolving country-specific guidelines from within the same application, accelerating the time to market. It is built on Microsoft.NET framework and integrated with EMC Documentum. Integration with EMC Documentum Server offers a central platform for global collaboration on all data and documentation during the submissions process, shortening the submissions cycle and time-to-market. In the current setup, there are 6 Citrix servers in the US Citrix farm and 9 Agent servers in US, 3 Agent servers in UK and 1 Agent server in Canada.

Roles and Responsibilities

• Install ISI 3.2.6.2 eCTDXPress, Publisher and ISM applications on a fleet of 6 Citrix servers.

• Implement multiple Local DMS and Session agents on the Citrix servers and eliminate Web servers in order to improve performance.

• Project and Timeline planning for the upgrades in Dev, Val and Prod.

• Perform impact assessment for each Citrix and Agent server thereby scaling if needed.

• Analyze performance metrics collected by Performance Testing team.

• Overall monitoring and resolving critical issues.

• Update existing IQ procedures based on any deviations noticed during installation.

• High Availability tests of each system component.

Project 6

Project Objective

Upgrade Documentum 5.3 SP3 and 6.0 SP1 based repositories and other Content Server components to 6.5 SP2.

Project Description

This project deals with the upgrade and cloning of Documentum Content Server and other Documentum suite of products. DCTM Upgrade includes upgrading DCTM 5.3 SP3 and 6.0 SP1 based repositories and other Content Server components to 6.5 SP2 platform. Upgrade will be done on each of the three environments maintained at AZ Dev, Test and Production.

This includes High availability setup for Content Server in Active/Active mode for Test and Production environment and High Availability setup for Java Method Server in Active/Active mode for Test and Production environment.

In AZ Re-hosting project, all the 4i and 5x Content Server and related applications will be installed and migrated. This includes the migration of server components as well as client applications like Webcache, CAS, PDF Fusion and PDF Aqua, RightSite and Intranet Client.

Roles and Responsibilities

• Perform upgrade impact assessment for each repository and prepare a report.

• Capture performance metrics of repositories before and after upgrade.

• Execute scripts to upgrade the Documentum Repositories.

• Verification of each upgraded repository.

• Update existing IQ procedures based on any deviations noticed during upgrade.

• High Availability tests of each system component.

• Coordination with AZ shared resources.

• Transition knowledge to the AZ support team.

• Complete all IQ executions per DCTM 6.5 upgrade and AZ ELC processes.

• Re-host AZ Content Server and other server components and client application.

• Overall upgrade monitoring and resolving critical issues.