Nicolas Ribiere

Within the IFIS department, in the Infrastructure / Data Center & Cloud Services entity

Contribute to the relevance of infrastructure requests made by projects or squads to service providers.

Monitor the application of technical architecture rules.

Act as a spokesperson for changes in infrastructure service offerings to projects and squads.

Act as a facilitator for technical requests from local teams involving central teams.

Write technical sheets for service orders.

Consult to create and manage tickets and/or changes via the ServiceNow interface.

Update the service order document which helps create service requests for all requesters.

It is intended to provide the keys and instructions for issuing service requests and/or changes via ServiceNow. But also useful advice and instructions for requests to be made under the best conditions.

Verify requests made by projects or squads (server orders, configuration changes (CPU, RAM), and storage upgrades (SAN/NAS).

Ensure compliance with architectural rules and correct technical sheets if necessary.

Support the change manager and contribute to change coordination if necessary.

Monitor the submission of tickets and/or changes, if applicable.

Advise the capacity manager and configuration management.

Technical Environment:

• Platform: VMWare, Hybrid Cloud, AWS, Azure

• OS: Linux REHL 8, AIX 7, Windows 2012 / 2016 / 2019, Mainframe, ZOS

• Exchange Platform: CFT 3.3 and 3.6

• Application Server: Websphere Application Server

• DB: Oracle 12, Oracle 19, Postgre, MongoDB, SQL Server, DB2

• Backup: Comvault

• Monitoring: Dynatrace

• ITSM: Service Now, SCCD

• Collaborative Platform: Confluence, Sharepoint

Within the BP²I Customers Service Management Client Unit, the main missions of the Customer Service Manager are:

Ensure monitoring of production quality.

Ensure monitoring of operational issues.

Coordinate action plans for complex operations and continuous improvement.

Lead task forces inherent to their domain.

Be the essential communication link during exceptional events.

Be the preferred interface between the client and BP²I technical teams.

Organization and writing of the Operational Monitoring Committee (COS) and the Steering Committee: Delivery Topics.

Share monthly activity monitoring through Steering Committees (COPIL).

Review and monitoring of BP²I-responsible P1/P2 incidents.

Review and monitoring of action plans (PIA: Post Incident Action).

Review and monitoring of complaints / acknowledgments.

Review and monitoring of changes.

Handle issues raised by OPS / APS / Business units.

Coordinate complex and cross-functional Change operations.

Coordinate the resolution of major incidents, alert, and communicate.

Challenge RCA (Root Cause Analysis) analyses.

Write PIR (Post Incident Report) within 2 working days.

Communicate PIRs within 3 working days.

Be proactive in proposing continuous improvement actions.

Be attentive to BP²I teams.

Have a cross-functional vision to detect any incidents within BP²I.

Technical Environment:

• Platform: VMWare, Cloud, Bare metal

• OS: Linux REHL 6.10 / 7 / 8, AIX 7, Windows 2012 / 2016 / 2019, Mainframe

• Exchange Platform: IBM MQ Series 9.1, CFT 3.3 and 3.6

• Application Server: Websphere Application Server

• DB: Oracle 12, Oracle 19, Postgre, MongoDB, SQL Server

• Backup: TSM, TVE

• Monitoring: Dynatrace, Netcool, Splunk

• ITSM: Service Now, Delphes, Dalia

• Collaborative Platform: Confluence, Sharepoint

Management of a team of 9 Middleware engineers responsible for RUN and Operational Maintenance across two hubs: Legacy & HIP.

Within the Operations and Technologies Directorate (DOT), the position covers responsibility for Middleware activity in production and the management of a team of 7 people.

Middleware activity is at the heart of data exchange between the different applications of the Les Mousquetaires Group.

Therefore, interactions with development teams, architecture/urbanization, security, study departments, DOT departments, STI (Technical and Industrialization Service) occur daily.

Ensure monitoring of the HIP platform's performance.

Provide support to application integrators in incident resolution.

Manage capacity.

Evolve standards, best practices, and communicate them.

Automate the installation of new technical components and routine administration tasks.

Ensure technological watch to optimize stability and security.

Be involved from the start of projects (architecture, security, etc. considerations).

Technical Environment:

• Application Server: Tomcat, JBoss, Websphere.

• Exchange Platform

• Legacy => MQ Series, EAI (Websphere Transformation Extender)

• HIP - Composed of 5 Exchange Platforms => API Gateway, MOM Solace, Kafka, iPaaS Boomi, MFT GoAnywhere

• CICD: TerraForm, Nexus, GitLab CI, GitLab, Jenkins