Integration Solutions Manager

Job Responsibilities Actionable

Problem & Performance

Management Planning and execution of projects, tasks related to Application fine Tuning, Performance engineering, Root cause analysis, Process Improvement, Productivity, Cost saving, Operational excellence, Customer experience and provide solution for resolving problems effectively and ensure seamless implementation. Plan and Build Reliability, Availability and Serviceability (RAS) across critical applications. Perform Load Testing for critical changes.

Incident Management The person responsible for this role should be ensuring the uptime, availability, and performance of the WBO applications and its interfaces. The individual chosen for this role is expected to be technically sound and be able to Lead & Manage a team responsible for this activity. As part of Incident Management, while handling incident’s is the primary function, sustenance of the applications, performance improvements and optimal utilization of the system should also be the focus. · Keeping this in account, following are the few tasks which are expected the individual to deliver as part of his Job Role. The jobs are specifically distributed between Peace Time & War time

No. Task P/W 1 24*7 System Monitoring Peace 2 Recording of every Incident and tracking permanent closure with RCA War

3 PERMANENT Incident resolution War 4 Making incident report Peace 5 Validating the incident report Peace 7 Stakeholder communication with incident details, impact, workaround (if any) and resolution. War 8 Creation and usage of KEDB for incident resolution War + Validating Known Error Database(KEDB) Report Peace 11 DR Drill Runbook Annual Review wrt completeness, correctness Peace 12 Support BCP Drill incident faced during and post switchover and switchback War 13 Capture and analysis of key infrastructure telemetry (Server CPU/RAM/NIC, Storage IOPS/latency/etc.). This is mandatory to monitor the health of the application (end to end) and correlate this during incident. Peace 14 Tracking the remediation of problem tickets within timelines: · S1: 2 months · S2: 4 months · S3: 6 months Peace 15 Front ending and handling of Application audits with IA, Statutory, Regulatory Auditors Peace 16 Remediation of application audit observations and ensuring hygiene processes are followed to achieve ZERO REPEAT OBSERVATIONS Peace 17 Annual review of monitoring KPIs configured in the automation tools. The KPIs to be reviewed wrt: 1. Relevance 2. Thresholds to be recalibrated 3. Configure new KPI if required Peace 18 Conduct vendor reviews wrt · Performance wrt response and resolution SLA for SFR · Quality of releases wrt issues faced post deployment and rollbacks · Data patches Peace 1+ Creation of Read-only User ID to stop the access of generic privilege IDs for BAU tasks Peace 20 Autosys automation of critical application maintenance jobs and handing over to DPC Peace 21 Close long pending open change & release tickets. At any point not more than 5 tickets should be open in > 60 days bucket. Peace 22 Close data patch approval request in ServiceNow within 5 days Peace 23 Conducting technology trainings Peace 24 Integration of all privilege user id in CyberArk including web, app, app console, database, etc. Peace

Performance & Technology

Obsolescence Management Always be on latest & supported technology stack: