Boris A.

**• Run & Incidents**: Qualification of Topdesk/Jira tickets, functional and technical analysis, prioritization based on operational impact, SQL investigation, and coordination with the Application Management and Support (AMS)/technical lead until the fix or recovery is secured.
**• Data & BI**: Consistency checks, data flow reconciliations, analysis of rejections and reporting discrepancies; reliability of SQL extractions, SSRS reports, Excel/Power Query files, and KPIs for business teams.
**• Monitoring & Steering**: End-to-end management of Grafana dashboards: production process supervision, sales and stock trend monitoring by zone, import control, anomaly detection, and providing an operational view of the run.
**• Coordination**: Interface between international users, central functions, service providers, and IT teams; formalization of findings, action plan tracking, and capitalization of procedures in Confluence.
**• Impact**: Improved production observability, more objective incident analysis, common business/IT understanding, reduced investigation times, and more reliable activity steering by zone.
**Tools**: SQL Server/SSMS, Power BI, Power Query, SSRS, Excel, Grafana, JAMS, Topdesk, Jira, Confluence

**• Data Quality**: Control of incoming flows, SQL/Oracle analysis, cross-source reconciliations, anomaly qualification, and data securing before transmission to the billing system.
**• Recoveries & Testing**: Monitoring data recoveries with external SSAs, verifying corrections, non-regression testing, and validating production deployments for valuation incidents.
**• Steering**: Production of valuation KPIs, weekly incident reporting, and structuring monitoring via Jira Kanban to make progress, risks, priorities, and blocking points visible.
**• Communication**: Summarizing anomalies, arbitrating priorities, and reporting impacts to business/IS stakeholders to facilitate recovery or correction decisions.
**• Impact**: More traceable valuation chain, better qualified discrepancies, more secure corrections, and reinforced communication between business, IS, and developers.
**Tools**: Oracle SQL, Jira/Kanban, GitLab, Excel, UNIX/scripts.

**• Context**: Functional exploitation and level 2 support for B2B finance processes: subscriptions, payments, customer portfolios, business applications, and operations supervision.
**• Data & Support**: SQL analysis of successful/failed payments, data catch-ups after incidents, tracking application fixes, account/portfolio administration, and contribution to asset/performance supervision and reporting tools.
**• Impact**: Secured finance operations, better traceability of data catch-ups, documentation of operating procedures, and contribution to incident/operations monitoring committees.
**Tools**: SQL Oracle/MySQL, Control-M, MongoDB, Elasticsearch, Excel, finance business tools.