1) Working on CR and new UserStories.

2) Creatinn of LLDS.

3) Support SIT for Defect fixes

4) Production Support

Router Replacement Insights generates graphical reports and data visualization around router replacements based on different parameters. This provides the ability to track the firmware versions, number of devices connected and bandwidth usage of the CPEs sent to the customers, to view complete CPE history for each customer. This will be achieved by having single truth inventory Prevent Revenue leakage & better Customer experience: Multiple Router dispatches to same customer, but without an ability to track reasons. Non-return TV CPE tracking. Capabilities: 1. Out of the box capability to track. 2. Tracking age of router and software version. 3. Tracking forecast/actuals 4. Timeline view of a customer life cycle to understand specifics 5. Aim to have a single truth inventory. Background for this change: We are currently sending out approx. 1,700 replacement routers per week, which equates to 0.66% of the base size (monthly) which is above the target set of 0.52%.Current reporting shows volume and reason code selected for replacement only, which limits the ability to identify any patterns / issues etc. It is expected that this implementation will reduce the volumes by 19k per year. Component: WLMS2 Client: Parse the router request XML creating Customer and Router Object and do the post call to Block Chain and save all the data as Single source of truth. Block Chain: Here we are saving all the request in the orderly way and after successfully generation of transaction same message being pushed to Mongo DB which is further used to show the graphical reports.

CMC Portal is used by the EE (Everything Everywhere) agents to raise the issues and new Orders on behalf of UK broadband & STB Customer. Agents will generally go through two of the major Journeys those are L2C and T2R. Lead to cash: Lead to cash journeys are basically in which agent will select the options mentioned for Broadband and STB packages on behalf of Customer. Trouble to resolve: In this Journey Customer will complain for the Existing order which need to be troubleshoot and resolver as soon as possible.

Responsible for understanding client Requirement.

Design and Develop the feature.

Support the UAT and SIT for defect fixes

Production Support

Safety Monitoring Services Workbench (SMSW) is for Quintiles LCS and J&J Pharmacovigilance Center (PVC). It addresses the procedures and processes for assigning, monitoring and reporting workflow status for individual Case Safety Reports, generating and monitoring the workflow, allocating individual Case Safety Reports to the PV Operations and reporting the status based on the needs of PVC management. Quintiles users of this system are expected to perform, and have been trained on, Some core concepts of the products are. a) Case: A unit of work that flows through a workflow. Has an identifier. Have several properties – core, functional, custom b) Workflow, Activity A Workflow is an assembly of activities that is collectively identified and managed An Activity is an action/task that can be assigned to, and executed by a Resource. Workflows (and Activities) can be designed for a function. o Can be controlled (started and stopped). Instances of Workflows and Activities are created at runtime to manage operations, gather metrics, etc.… C) Resource An individual to whom activities of a workflow can be assigned to. Has capabilities that determine whether the resource can perform (and hence be assigned) an activity. Has availability as an attribute. D) Resource Pool A grouping of resources for organizational purpose Resource pools are hierarchical. Has a manager (who is also a Resource). Root Resource Pools are Resource Pools that are hierarchically at the root of a Unit. e) Case Pool A grouping of case with a pre-defined criteria for the unit Case Pools are aligned with the organization unit model Cases are routed to a Case Pools Case pools are hierarchical. Has a case pool manager Unit Pool is Case Pools that are hierarchically at the root of a Unit. Case Pools are assigned to resource pool for assigning cases f) Work Pool A grouping of cases with a specified criteria Providing capability to Line Managers to define work pools that will help optimize the resource management based on the case inventory and/or specific scenarios g) Unit A grouping of resource pools. The root of customizations for a product deployment. The top level of an organizational structure h) Rule Set, Rule A Rule is a pairing of an antecedent and a consequent. The Consequent occurs if the Antecedent is true in a given instance. IF THEN A Rule Set is a set of Rules that works towards a goal Routing, Prioritization, Assignment. A Rule Set is designed for a Function. A Rule Set is executed when a goal is to be achieved Core Engine Concepts: a. Routing: Moving the case to the right case pool or segment. b. Prioritization To calculate due date or Priority date for a case. c. Assignment The process of assigning a capable and available Resource to a case. Core Process: Case In take and Upload The Case Data is fetched from different configured views for every 30 minutes. The configuration details are currently in the database. The system will read and push the data to the database. The system is intelligent enough to validate if case details have changed or it is a new case or case has a new version etc. A detailed mail will be sent to all individuals who are configured to get the status of the upload process. The mail will also contain details of how many records have been uploaded, how many were rejected and why were they rejected. The Application is smart enough to know which case status to retain when the sync happens. It compares the timestamp of each of the cases where there is a mismatch in the status to know if View has the latest status or the application. When there are changes to the following attributes of a case, the system reconciles the cases Roles and Responsibilities . Written intake process by Using Core Java, Multithreading Design The Case Pool UI By using Vaadin And achieve the functionality by writing Service Classes Implemented Form Beans and their Validations. Written Service layer and Persistent classes by using JPA. Written Native, HQL Queries and Views. Design Exception Framework to throw Custom Exception with some meaningful Message, Understanding the Stories and write the Business Logics.

1) Worked as Backend Developer using ATG E-COMMERCE framework.

2) worked On Oracle SQL.

3) Creation of JSP'S