A woman holding a laptop and a man with glasses talk as they walk through a telecom lab lined with antenna test rigs and server racks.
心を動かす会話

GenAI for employee productivity & augmented engineering

Engineers remain accountable. Generative AI removes repetitive friction across modernization, testing and knowledge work so telecom teams can deliver faster without trading away quality, security or control.
会議のスケジューリング
ポッドキャストを聴く
-15
+15
0:00
/
0:00
Engineers remain accountable. Generative AI removes repetitive friction across modernization, testing and knowledge work so telecom teams can deliver faster without trading away quality, security or control.
WHY THIS "GENAI FOR EMPLOYEE PRODUCTIVITY & AUGMENTED ENGINEERING" CHALLENGE?
Software demand is accelerating. Engineering capacity is not

Telecom operators must modernize legacy applications, reduce technical debt and release new services across complex estates. Coding assistants can accelerate individual tasks, but unmanaged adoption can fragment tooling, weaken quality controls and unsettle the workforce. The real challenge is to redesign the software delivery lifecycle so engineers receive useful support, human accountability stays clear and every gain can be measured.

主なメリット
More capacity for the work only engineers can own
チェックアイコン
Move from backlog to flow

Reduce repetitive effort in code generation, refactoring, documentation and test creation, with engineers reviewing and deciding what moves forward.

チェックアイコン
Modernize with context

Connect AI assistance to codebases, architecture standards and telecom domain knowledge so modernization supports the target estate, not just the immediate task.

チェックアイコン
Build quality in earlier

Use testing and secure development practices throughout the workflow to surface defects, vulnerabilities and compatibility issues before certification.

チェックアイコン
Turn adoption into capacity

Measure cycle time, acceptance, quality and rework by role and workflow, then scale the patterns that create observable value.

NTTデータのサポート体制は?

01
Map the work before selecting the tool

Identifies where engineers spend time, where handoffs fail and which SDLC moments are suitable for augmentation. Use cases are prioritized by business value, feasibility and risk.

Overhead view of three colleagues reviewing network diagrams, sticky notes and project timelines on a workbench surrounded by telecom hardware.
02
Design a human-accountable delivery model

Defines how AI surfaces suggestions, drafts code or generates tests, and where architects, developers, security teams and product owners review, approve and remain accountable.

An engineer points at code on a monitor while a colleague holding a phone looks on, in a lab with test equipment and rooftop antennas behind them.
03
Build a secure, context-aware foundation

Connects approved models and engineering tools to the relevant code, standards and knowledge while applying access controls, traceability and responsible AI governance.

Engineer connects fiber cables in a network rack while a colleague works at a monitoring screen in the background.
04
Prove value in governed pilots

Starts with bounded workflows and clear baselines for cycle time, quality, coverage, acceptance and rework, then uses the evidence to decide what should scale.

Rows of smartphones connected to a test rig in a lab, while an engineer in a white coat monitors results on two screens.
05
Scale adoption through skills and measurement

Combines role-based learning, AI champions, workflow support and performance tracking so new ways of working become repeatable rather than dependent on isolated enthusiasts.

A senior engineer shows a radio unit to three young colleagues working with laptops and telecom hardware at a lab bench, with antennas on the skyline behind them.
Two technicians in hard hats and high-visibility vests work on a rooftop telecom mast, one checking a tablet and the other an open equipment cabinet, with the city skyline at sunrise.
実証済みの効果
Two months returned to delivery. Quality kept in view

An anonymized telecom operator in Latin America used generative AI to support the migration of a delivery application from Java to Kotlin. Engineers then corrected the code, performed unit testing and developed the required enhancements, keeping human review inside the modernization workflow.

重要な結果
チェックアイコン
7 to 5 months

The documented development timeline was reduced from seven months to five months.

チェックアイコン
96% coverage

The application reached 96% coverage before certification, as reported in the source case.

チェックアイコン
Architecture updated

The application was aligned with current standards and its architecture was updated.

チェックアイコン
Human review retained

Developers corrected generated code, carried out unit tests and completed subsequent enhancements.

Ready to turn engineering pressure into productive capacity?

Start the conversation that puts generative AI into the workflows where telecom engineers can use it, govern it and prove its value.

ドラッグ