[Translation from Japanese to English ] The number of INC became fewer from the start. But from before or rather, eve...

Original text

INCの数は最初より少なくなりましたが、でもBプロジェクト以前よりかは依然として発生しています。
1週間にINCが発生しない週はありません。D/S/Kのいずれかの3PLで必ずINCがサブミットされます。
我々としてもなぜCIの問題がこんなに解決されず続いているのかを問いたい。
これは、我々に報告があがってきたINC件数であり、我々にに報告があがらず3PLとITが直接行っているものもあるかと思います。
3PLがINCを上げる際に必ずINTERCOを付けるように指示しています。

Translation / English

The number of INC became fewer from the start. But from before or rather, even now it is being generated since the B project.
There hasn't been a week that an INC has not been generated in a week. INC must be submitted for the 3 PL, either D/S/K.
For us, we want to ask why this problem has been going on without solution?
This is the number of cases of INC that has been brought to our attention. We think that there might be those that have been directly handled as 3 PL by IT and without being reported to us.
When 3 PL is escalated as INC it must be always displayed with INTERCO.

Translation / English

The number of ICN has been decreasing more than the beginning, but it has been occurred more before the project of B.
The occurrence of INC happened every week. INC must be submitted at either 3PL of D/S/K.
For us, we would like to ask why the problem of CI is continued without solving the problem.
This is the number of INC reported given out for us, there might be chance 3PL and IT without being reported directly .
We are designating to add INTERCO when submitting the INC by 3PL absolutely.

Translation / English

The INC volume has become fewer than the beginning, but it still is occurring more frequently than project Bz. Not a week goes by without INC incidents. An INC with either of these 3 PLs of D/S/K is submitted. We would like to know the reason why this CI issue haas been continuing still. This is the INC volume reported to us, but there must be other cases that are communicated between 3PL and IT directly, I guess.
We never instruct them without attaching INTERCO upon 3PL's raising INC.