OpenAI reported that NTT DATA Group, a large IT services and systems integration firm, has cut the time required for incident analysis to approximately 30 minutes by deploying Codex, OpenAI's coding agent, within its internal engineering workflows.
According to the report, incident analysis — the process of investigating system failures, identifying root causes, and preparing findings for engineering teams — previously required significantly more manual effort. NTT DATA integrated Codex into this workflow to automate portions of the log review and diagnostic process, with the coding agent handling initial analysis that engineers would otherwise perform by hand.
The specifics of NTT DATA's internal architecture — which systems Codex has access to, how outputs are validated before being acted on, and whether the 30-minute figure represents an average or a best case — were not fully detailed in the source material and should be treated as reported by OpenAI rather than independently verified.
What is notable here is not the raw time saved but the category of work being automated. Codex is built primarily as a coding agent, designed to read, write, and reason about code and codebases. NTT DATA's use case extends that capability into an adjacent but distinct task: reading system logs, correlating events, and producing a structured incident summary — work that overlaps with support and ops functions as much as with software engineering. This is consistent with a broader trend of coding agents being repurposed for operational analysis tasks that involve structured data and pattern recognition, rather than pure software development.
For enterprises the size of NTT DATA — a multinational with tens of thousands of engineers — a 30-minute incident analysis process represents a meaningful reduction against a baseline that likely involved coordination across multiple teams and systems. The infrastructure investment required to reach that outcome, including internal integration work, access controls, and validation layers, is not disclosed, and is almost certainly out of proportion to what a 10-200 person company would deploy.
The value of this case study for smaller operators lies in the proof of concept rather than the specific tooling. It confirms that coding agents, when pointed at operational data rather than only source code, can meaningfully compress diagnostic workflows. It does not confirm that equivalent gains are achievable without dedicated engineering resources, nor does it address error rates, false positives, or how frequently human review overturned the agent's initial analysis — details that matter more to a smaller team's risk tolerance than the headline time savings do.
Companies evaluating similar automation should treat this as directional evidence that the underlying capability exists, and scope their own pilots narrowly around a single recurring diagnostic bottleneck before expanding further.