Glossary entry (derived from question below)
Japanese term or phrase:
作業崩れ
English translation:
Operational failure
Added to glossary by
Lara Silbert
Feb 9, 2013 11:27
11 yrs ago
Japanese term
作業崩れ
Japanese to English
Other
Business/Commerce (general)
In a field entitled "作業くずれ項目", in a document evaluating worker performance issues. I'm trying to think of a natural-sounding way to translate this, as "work breakdown item" sounds awfully translatese. Any thoughts? Thanks :D :D :D
Proposed translations
(English)
3 | Operational failure |
David Gibney
![]() |
3 | uncompleted job |
Harry Oikawa
![]() |
3 | defective performance (factor) |
Marc Brunet
![]() |
2 | disordered assembly/work (line) |
cinefil
![]() |
Proposed translations
41 mins
Selected
Operational failure
I'd go with "operational failure" or "breakdown". It works better with "item" and 崩れ is used more broadly than "collapse" in English.
4 KudoZ points awarded for this answer.
Comment: "thanks very much!"
2 hrs
uncompleted job
As David said, it is indeed an operational failure but I think it has to be more specific.
In this context, this field looks to me for an auditor to specify the name of the job/work that has caused that operational failure.
In this context, this field looks to me for an auditor to specify the name of the job/work that has caused that operational failure.
13 hrs
disordered assembly/work (line)
a guess
1 day 13 hrs
defective performance (factor)
"defective performance" is found more commonly in contract law, rather than manufacturing /service provision specs.
Defined as:
(Complete or) incomplete (partial) performance that does not fully satisfy the requirements (of the contract)
Based on Lara's more detailed run down, would tend to treat "項目" as a 'cause/factor'
Using "performance' would enable using the same 'rating label' for any task item to be defined.
Defined as:
(Complete or) incomplete (partial) performance that does not fully satisfy the requirements (of the contract)
Based on Lara's more detailed run down, would tend to treat "項目" as a 'cause/factor'
Using "performance' would enable using the same 'rating label' for any task item to be defined.
Example sentence:
see below
Discussion
Line name:
Shift:
Operator Name:
Audit Date:
Auditor:
作業くずれ項目:
And then the file continues to list actions like 見る, 取る, 運ぶ, 置く. Then, under the individual categories of these actions, it goes into problems that can occur with the work done, causes of these problems, criteria by which one judges whether that was the cause of the problem, etc. Then, there's space to fill in possible countermeasures. I hope that helps :D