Backlog jobs can be active and inactive works orders which are good and bad in nature respectively?

Active backlog jobs should be about 2 to 4 crewwweks so that your cratfmen always ahve jobs ready for execution ie front loading concept.

Inactive backlog jobs should be expedited and arised from 2 scenarios:
1) operational constraints like hot work permits or eqpt running & cannot be shutdown.
2) non-availability of resources and/opr services like materials, manpower, equipment, tools, technical expertise etc

How do you differentiate active and inactive backlog jobs in SAP PM so that we can track track them ie to optimise active jobs and to minimise inactive jobs where possible? TQ

We use Revisions to catagorise work orders.

Maybe you can explain how you use revisions to categorize work orders. In my case, we use revision nos to track shutdowns. Tq

Maybe you can explain how you use revisions to categorize work orders? We use revisions nos. to track work orders for shutdown/turnaround works. TQ

We assign revisions to all orders not just shutdown orders. The revisions used include WEEK0, WEEK1, ...WEEK4 to provide a simple 4 week lookahead (we don't use capacity planning). We also have revisions "BACKLOG" and "ONHOLD" which indicate active and inactive backlog jobs.

Nice to know how you do it differently over there. Well, we enter the work order status in the set/user status field on the right hand side of the system status. Examples of user status are AWEx for awaiting execution, INPR for Work in progress, CPLT for completed works, OPCT for operational constraints, AWSD for Awaiting shutdown, AWRC for awaiting resources etc. TQ

We use user defined status to classify orders.