THE MEDIA FOR AI THAT ACTUALLY HELPS.English edition · Understand & take action
Spotted on the web

Gathering changes, past incidents and resolution paths for P1 incidents at BNP Paribas' DSI

Use described publicly by CIO Online — Marc Camus (BNP Paribas) (2 December 2025), summarised by the desk. Not tested by iadujour.

The result to aim for

Marc Camus, DSI Group of BNP Paribas, has deployed an internal incident management assistant: in a significant incident, he aggregates changes in resources, precedents in the internal tool and already identified resolution paths. About 80% of criticality 1 events are already managed with this assistant.

What was done

IOC Online (2 December 2025). Tool developed internally. The ISD reports that it is beginning to see a reduction in resolution time for P1s without figures. Distinct from Developer Assistant CIB and chatbot Proximity Support Teams (same article). The IT budget (~€8 billion) and the €750 million value IA are the context, not the gesture.

Before you start

Tool cited by the source: Assistant incidents interne BNP Paribas; other tools cited: Assistant incidents BNP Paribas. Fill in the bracketed items: [symptôme, ressource, heure], [coller]. Strip confidential data that is not needed and check your tool’s access terms. Features and plans can change.

The method, in three steps.

  1. Gather the context

    Spot the bracketed items in the prompt ([symptôme, ressource, heure], [coller]) and prepare what they ask for.

  2. Adapt the prompt

    Copy the prompt below, replace the bracketed items, then paste it into the AI assistant you use. The cited tool (Assistant incidents interne BNP Paribas) is not necessarily available to the public..

  3. Reread before using

    Reread the result, correct it if needed and keep the final decision. Caveats are detailed below.

Your starting point.

Replace the bracketed items, then adapt the proposal to your situation. This prompt is written by the iadujour desk It is not a quotation from the source.

The prompt to customise
Incident (without secret): [symptôme, ressource, heure]. Changes already listed: [coller]. Close incidents: [coller].

Proposes 5 ordered leads, each linked to a glued fact. Don't make any changes.

What deserves your attention

A resolution track is not a validated runbook. Cross-check each change cited in the ITSM before acting on production.
Origin of the case. Use described publicly by CIO Online — Marc Camus (BNP Paribas) (2 December 2025).
Proof level: Testimony published by an identified source. Source checked on 11 November 2026. Use described by the source, not tested by the desk. Original summary written by iadujour.fr: figures and claims are the source’s; the prompt is a desk proposal, not a quotation.
TO GO FURTHER

Other ideas to put to work.

The whole Dev theme
Dev

Make a pull request by an agent before the human review

A first automated passage to identify probable bugs, missing tests and safety risks, so that the human review focuses on the essentials.

Tool: Claude CodeType: Practical case
DISCUSSION

Comments.

A field note, a question, a precision on this use case? Comments are reviewed before publication.

Published comments

Loading comments…

    Leave a comment

    Moderation charter. Every comment is reviewed before publication. We refuse hate speech, insulting or discriminatory language, advertising, spam and promotional links, off-topic posts and other people’s personal data.