NTT DATA Group reduced its incident analysis duration to 30 minutes using Codex, according to reporting published by OpenAI on July 22, 2026.
OpenAI published the performance metric on July 22, 2026, but did not cite the baseline timeframe NTT DATA Group recorded prior to adopting Codex. The report did not state how many hours or days incident analysis required before the change. OpenAI provided no figures on the overall volume of incidents processed under the 30-minute workflow.
Version details for Codex were not specified in the release. OpenAI did not clarify which edition of Codex NTT DATA Group implemented or whether custom software models were involved. The release included no information on API infrastructure, server specifications, or data security measures established for the integration.
Licensing costs and internal expenses associated with the project were omitted from the reporting. OpenAI did not state the price NTT DATA Group pays to use Codex or the operational savings resulting from the shift. The reporting omitted details concerning how many software engineers or technical support staff actively use Codex for incident handling.
The July 22 release contained no information regarding operational conditions during incident handling. OpenAI did not clarify whether human engineers review the output generated by Codex or if incident resolution steps are automated. The report did not identify which categories of incidents, such as network outages or software defects, qualify for the 30-minute analysis timeframe.
NTT DATA Group gave no indication of whether it plans to deploy Codex across additional operational units or client services in the future. The report contained no statements or quotes from executive leadership at NTT DATA Group or OpenAI. OpenAI provided no geographic breakdown detailing which regional offices or data centers participated in the reported deployment.
