This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
There is not a simple way to disable as the function is to create task workorders..
I have seen companies create 1 task and use the task longdescription to populate the actual steps, this will only use to wonums per pm generated..
Other option are to attach pdf task list to a taskless job plan.. Then let the attached print with the workorder..
There are a few options to lower the amount of workorders created, but if your worried about using up workorder numbers, i doubt that would ever happen.. You could always say every few months restart the wonum seed and prefix with say 01-, 02-,...etc.. This would keep your numbers low..
Shannon Sutton
Cell: 571-970-7965
On May 4, 2012, at 9:20 PM, "haiyanchen" <chenthy@gmail.com> wrote:
> Our Work Order numbers are being used up very fast because PM Work order generation create all job plan tasks as individual work orders.
>
> Even we understood that those PM Work Orders have their own wonum numbering scheme/range, the WorkOrder table is growing very fast. We have around 1:20 ratio of normal work orders (istask =0) and the task-based work orders (istask=1)
>
> Yes, we read the IBM explanation that this is ok, but we still like a way to disable generating task based WOs since we almost never need to schedule at the task level.
>
> Any suggestion or input is welcomed!
>
>
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.
I don’t know of a way to stop the task creation either, short of the ways that (the other – lol!) Shannon just listed.
However: you can also set the task work orders to number differently from the regular work orders, ie T1001, T1002, etc. if you don’t want to use work order numbers. There’s a procedure for that I could dig up if you want it.
Shannon (Rotz)
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Shannon Sutton
Sent: May-04-12 6:30 PM
To: MAXIMO@yahoogroups.com
Cc: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Is there a way to disable generating task-based Work Orders from PM?
There is not a simple way to disable as the function is to create task workorders..
I have seen companies create 1 task and use the task longdescription to populate the actual steps, this will only use to wonums per pm generated..
Other option are to attach pdf task list to a taskless job plan.. Then let the attached print with the workorder..
There are a few options to lower the amount of workorders created, but if your worried about using up workorder numbers, i doubt that would ever happen.. You could always say every few months restart the wonum seed and prefix with say 01-, 02-,...etc.. This would keep your numbers low..
Shannon Sutton
Cell: 571-970-7965
On May 4, 2012, at 9:20 PM, "haiyanchen" <chenthy@gmail.com <mailto:chenthy%40gmail.com> > wrote:
> Our Work Order numbers are being used up very fast because PM Work order generation create all job plan tasks as individual work orders.
>
> Even we understood that those PM Work Orders have their own wonum numbering scheme/range, the WorkOrder table is growing very fast. We have around 1:20 ratio of normal work orders (istask =0) and the task-based work orders (istask=1)
>
> Yes, we read the IBM explanation that this is ok, but we still like a way to disable generating task based WOs since we almost never need to schedule at the task level.
>
> Any suggestion or input is welcomed!
>
>
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.
After reading the replies, it seems that disabling task-based WO generation is not easy unless JAVA program changes are made which we do not want to do.
I am thinking of having a SQL job to remove the task-based WOs regularly.
Before we even try that, does anyone know of any obvious negative consequences from doing that?
Are you talking about deleting the task work orders from the DB?
I would not suggest this approach, but if you decide to move in that
direction just make sure you remove all reference of that work order.. It
could reside in many tables and having orphan records in the DB are not
fun..
Shannon Sutton
CMMS Specialist
EMCOR Government Services
Office: 571-403-8940
Cell: 571-970-7965
From: "haiyanchen" <chenthy@gmail.com>
To: MAXIMO@yahoogroups.com
Date: 05/07/2012 09:18 AM
Subject: Re: [MAXIMO List] Is there a way to disable generating
task-based Work Orders from PM?
Sent by: MAXIMO@yahoogroups.com
After reading the replies, it seems that disabling task-based WO generation
is not easy unless JAVA program changes are made which we do not want to
do.
I am thinking of having a SQL job to remove the task-based WOs regularly.
Before we even try that, does anyone know of any obvious negative
consequences from doing that?
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.
Why not prevent them from being created in the first place, by moving your
Job Plan tasks to a linked document instead? The link gets automatically
copied over to the work order, and there would be no tasks (OK, maybe 1 task
saying: "Refer to the attached document").
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
haiyanchen
Sent: May-07-12 6:17 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Is there a way to disable generating task-based
Work Orders from PM?
After reading the replies, it seems that disabling task-based WO generation
is not easy unless JAVA program changes are made which we do not want to do.
I am thinking of having a SQL job to remove the task-based WOs regularly.
Before we even try that, does anyone know of any obvious negative
consequences from doing that?
Thanks for the job plan as attachment approach, which we can not adopt at this moment.
Main reason is well, we prefer to have Job Plan and Job Plan tasks in the tables and being reportable.
I guess we will try deleting the task-based WOs at our own risk if we want to. At this moment, the Workorder table size is still ok, but as more sites go live, we may have to do something based on performance situation.
Thanks to all.
Hi,
Why not just create a separate autonumber sequence for WOACTIVITY ? That way you won't use up your main Workorder number sequence. We had the same problem, and gave the WOACTIVITY view its own sequence called WOTASKNUM. The WOACTIVITY sequence(s) can have their own prefixes (we use "T" for task)
We did this in Version 6, and are also using this in version 7.1
--- In MAXIMO@yahoogroups.com, "haiyanchen" <chenthy@...> wrote:
>
> Thanks for the job plan as attachment approach, which we can not adopt at this moment.
>
> Main reason is well, we prefer to have Job Plan and Job Plan tasks in the tables and being reportable.
>
> I guess we will try deleting the task-based WOs at our own risk if we want to. At this moment, the Workorder table size is still ok, but as more sites go live, we may have to do something based on performance situation.
>
> Thanks to all.
>