Repair Management in AX 2012

My point is if you or others can share .. :)

Well they are different for each business depending upon what the business wants. What industry are you applying it to? I find customers with this requirement already have these values for you.

IT Company.

Selling IT products and Service Company (Repair/Replace)

There is a wide product set to be all encompassing. You wont analyse and repair some elements I presume? The nature of the product and process define them.

So without knowing what you do specifically within the wide IT product set you could look at:
Conditions; Broken, Noisy, Hot, Error Codes i.e. 404, No Memory, No Sound, etc.
Symptom Areas; Fan, Hard Drive, Monitor, CPU. It is basically a breakdown of where the person believes the issue is as they log it, which depends upon the product.
Diagnosis Areas; Could be same as sympton, could be wider or a different category, depends how the engineer approaches it.
Resolution; Component replaced, Engineer adjustment, Customer adjustment, Unit replaced, User Error, etc.
Repair Stages; Logged, Open, Waiting for Customer, Assessment, Part Ordered, In Progress, Resolved, etc.

Ultimately it depends how the business sees the analysis, definition and progress of the repair.