Tejal Chavan

• Working as an HWA (HCL Workload Automation / Tivoli Workload Scheduler) Administrator on 10.2.4 version, scheduling jobs and job streams based on application team requirements.
• Configured run cycles, calendars, earliest/latest start times, and repeat intervals using the Dynamic Workload Console (DWC).
• Set up job dependencies, including file, resource, and predecessor/successor conditions, to ensure correct execution flow.
• Analyzed job and job stream logs, performed corrective actions, and submitted job streams into the current plan.
• Monitored TWS workstations, ensured they were linked and operational, and verified that all TWS services were running.
• Provided L1/L2 support for TWS-related incidents, meeting strict SLA requirements, and participating in on-call support rotation.

• Managed P1, P2, and P3 incidents based on business impact, urgency, and priority, ensuring minimal service disruption.
• Led bridge calls during major incidents, coordinating cross-functional teams until full service restoration.
• Acted as the single point of contact between stakeholders and application teams throughout the incident lifecycle.
• Engaged application and infrastructure teams via Jira Service Management, using defined service catalogs.
• Utilized Five9 for inbound/outbound incident communications and real-time notifications.
• Sent incident alerts and regular updates using FireHydrant and StatusPage, ensuring stakeholder communication.
• Performed post-incident ticket cleanup, documenting key timelines (Start, Detection, Acknowledgment, Repair, Resolution) for audits and RCA.
• Posted real-time incident updates in Microsoft Teams channels and Jira tickets, ensuring clear and continuous stakeholder communication.
• Monitored servers and analyzed performance metrics using New Relic to proactively identify and escalate issues.

• Worked as a TWS Administrator, scheduling jobs and job streams according to the JIRA request for banking environments using third-party TWS.
• Creating and scheduling multiple IWS jobs as per the user's and business requirement.
• Specified the run cycle, time – latest/earliest start, repeat range, setting up calendars for runcycles and configured file, resource, job dependency as a part of scheduling jobs through DWC console.
• Hold, Release, Re-run of the jobs done in the current plan as per the requirement.
• Submitting jobs and job streams in the plan related to the banking regions all over the world.
• Analyzed the logs and perform actions on the job as per the logs or pre-written instructions.
• Assisting the monitoring team in taking action on the jobs and resolving their queries.
• Monitored daily batch job execution, analyzed failures, reducing job failure rate by 22% through analyzing job failures and reporting it to respective teams.
• Collaborated with application, infrastructure, and operations teams to onboard new jobs, update job schedules, and support change requests in alignment with ITIL standards.
• Taking action on the abend jobs according to the errors in the job logs, reaching out to the application team to fix the job in case it keeps getting into an error state.
• Reaching out to the Linux Team to fix issues on the Linux workstation which affect the jobs running on that workstation.
• Making sure that backup jobs are running and completed as per their schedule, reaching out to the Backup Team in case of errors or delays in backup jobs.
• Taking care of the jobs in three TWS environments - Production, Dev and Maintenance.
• Creating monthly reports for abend jobs in the Prod and Dev environments. Keeping a count of abend jobs every month for each site with valid reasons in case of a high count.
• Streamlining jobs to reduce the number of abend counts improving efficiency.
• Making sure TWS workstations are linked and running. Checking if TWS services are running.
• Performed TWS operations during DB refresh activity.
• Performed TWS operations during the Big Release upgrade every quarter.
• Maintained comprehensive job documentation, runbooks, and SOPs, improving knowledge transfer and reducing onboarding time for new team members.
• Provided L1/L2 support for TWS-related incidents, adhering to strict SLAs and participating in on-call rotation.

Project 1: Incident Management and Operations.

• Handled major incident processes as per the impact and with utmost priority, especially for P0 and P1 tickets. Setting up a conference bridge call and notifying the required teams, key stakeholders, and users regarding the issue.
• Driving the bridge call and providing required support until the services are restored and impact is minimal.
• Supported a 24x7 Command Center environment, including weekend and on-call rotations, ensuring uninterrupted service support across time zones.
• Kept an account of the troubleshooting on the major incident channel with the latest updates. Utilized tools such as ServiceNow, Slack/Teams, StatusPage to manage incident workflows, escalations, and communication across global teams.
• Maintained an up-to-date incident dashboard and sent regular communication on ongoing incidents to senior leadership, including business impact and resolution timelines.
• Maintaining consistent implementation of process activities with a strong emphasis on quality, in alignment with agreed Service Level Agreements (SLAs). Performing detailed root cause analysis on significant incidents, identifying primary issues and contributing factors.
• Providing technical and other resources as service restoration and recovery efforts for escalated incidents. Additionally, ensuring that technical staff updates tickets and that the IM process is followed correctly.
• Scheduled maintenance notifications and major incident notifications during critical incident troubleshooting and maintenance activity via the Status Page.
• This would notify the users of ongoing maintenance, outage, or an issue.
• Assigning and managing tickets through Service Now to appropriate teams. Notifying the teams through email/chat/calls in case of a high-severity ticket.
• Analysing the volume of incidents received, resolved tickets, pending incidents, and service tasks each week. Keeping track of the tickets, changes, and incidents by preparing reports and giving recommendations to the management on increasing efficiency.
• Monitored infrastructure and application health through dashboards (e.g.,Nagios, New-Relic,Thruk) to proactively detect and escalate potential major incidents. Keeping the hosts under downtime in these tools during an upgrade or a scheduled activity.
• Assigned IPs and decommissioned windows servers as a part of shift-left activity.
• Worked on the TWS application as part of Operations.

Project 2: TWS Administrator.

• Worked on Tivoli Workload Scheduler, created and scheduled TWS jobs as part of operations. Created jobs according to the given script, along with job streams
• Specified the run cycle, time – latest/earliest start, and repeat range as a part of scheduling jobs.
• Fetched job logs for job abends, creation and updating of calendars as per request, defining dependencies on the jobs - successor and predecessor.
• Configured job failure alerts through Putty to notify the teams.
• Monitored those jobs in CP (Current Plan), Hold, Release and Ad-hoc and re-run the jobs as per requirement.
• Made sure that TWS services were running by performing service checks through Putty after the monthly patching activity or maintenance on TWS Linux servers.