Hatchala Keo

Business IS migration project to AWS cloud as part of the 'Move To Cloud' initiative.

Migration of business flows from V-TOM scheduler to Control-M SaaS.

• Definition of the migration project scope for the production plan, existing system audit, implementation of a technical action plan and support for a team of 6 Production Engineers.

• Rewriting and/or migration of Shell scripts from V-TOM to Control-M Helix.

• Design and implementation of multi-environment application workflows on AWS infrastructure.

• Optimization and stabilization of application workflows.

• Definition of business and infrastructure processes between cross-functional teams (ESI, DEVOPS, others) to improve operational efficiency.

• Definition and implementation of the Control-M agent maintenance and upgrade schedule.

• Definition and implementation of job monitoring to Datadog and automatic JIRA ticket creation.

• Implementation of Control-M architecture monitoring to Datadog.

• Implementation of AI Jett and SSO/MFA.

• Training and support for Production teams on the use of Control-M SaaS (Technical Workshop).

• Control-M Technical Referent between client & BMC Software publisher.

• Definition of needs assessment workshops with application project teams.

• Writing of technical documentation (DAT, DEX, Training, specific PROC, and best practices).

Member of the SOC Operational Committee

• ESI Team Representative

Technological Environment:

AWS, Kubernetes, Datadog, Control-M SaaS, PagerDuty, JIRA, Confluence, Linux, secure transport CFT.

Technical management of IT projects – Management of Production and business flows

• Definition of project scope (SAP ECC → S/4HANA, client BU application redesign) and scoping of activities for the Operations team and the SAP TMA team (Mauritius).

• Facilitation of needs gathering workshops with business stakeholders and project managers, to ensure technical/functional alignment.

• Implementation of business flow management processes, in collaboration with cross-functional teams, reducing data transfer errors.

• Audit of the production plan under Control-M (over 1200 jobs analyzed) to prepare for migration to SAP S/4HANA and client BU application redesign.

• Control-M scheduler administration: deployment of agent servers, reconfiguration of user rights, incident resolution in conjunction with BMC support.

• Creation and integration of inter-system flows (SAP, BO, STL, BW…) via Control-M, Shell scripting, batch, job API, etc.

• Monitoring of operational KPIs: system availability rate (>99.9%), critical incident MTTR < 2h, reliability of consolidated sales figures in SAP by D+1.

• Control and monitoring of SAP Jobs & Process-Chains.

• Organization of weekly change management meetings (Change Advisory Board) with Infrastructure and Business teams, to streamline production deployments.

• Guarantee of production system availability (SAP, BW, STL, BO…), ensuring 24/7 business continuity for critical scopes.

• Reliability of daily/weekly/monthly sales figures in cash register tools and SAP, consolidation variance < 0.5% between systems.

Technological Environment:

SAP ECC application server, SAP BW, STORLAND, WINSTORE, Windows Server, Linux, Vmware, O365, Active Directory, Control-M, Power BI.

Operational Maintenance – OpCon Production Plan:

• Automated upgrade of OpCon agents (Testing & Production) via Ansible, environment standardization and reduction of human errors.

• Redesign of the production plan: rationalization of processing chains, reduction of unnecessary dependencies and design errors.

• Implementation of the Opcon Deploy module (repository BDD) to ensure centralized and traceable management of Production deployments.

• Implementation of cross-functional ITSM tool processes integrating operational requirements (patching schedule, server restarts, monitoring), in coordination with Infrastructure, Operations, and Application teams.

Opcon Business Workflow Integrator:

• Analysis of technical needs through workshops with business stakeholders and project managers, transformation into robust and scalable Opcon chains.

• Design, documentation, and delivery of functional and technical plans in Jira and Confluence, from design to production, including testing and validation phases.

• Implementation of business flow monitoring, with differentiated management based on criticality level (SLA, email alerting or on-call duty, incident recovery).

• Handling of ad-hoc requests (creation, modification, correction of jobs, integration of specific data).

• Monitoring of the production plan and resolution of production incidents, in coordination with N2 support.

• Training of internal teams on Opcon (operations & integration levels), support for tool adoption and best practices.

Technological Environment:

Windows servers, RedHat, Active Directory, Tanium, Vmware 7, Hycu, VEEAM, Easy Vista, Confluence, JIRA, GoAnywhere MFT, Nutanix Cloud, Azure, Opcon, Gitlhub, Foreman, Ansible, Centreon, Citrix XenApp 7, MFT, Office365, internal application.