Comentários (13)

1 LizSchutz comentou às Link permanente

Thanks, David, good insight.

2 Venkataseshan comentou às Link permanente

Hi David, <div>&nbsp;</div> Good Information. <div>&nbsp;</div> In Multi assets, whether cost of WO is shared among multi assets equally?. How does it work? <div>&nbsp;</div> This info will be useful for my on-going project and would appreciate your valuable inputs.

3 DavidHavican comentou às Link permanente

Venkataseshan, <div>&nbsp;</div> Currently, there is no support for distributed costs on a work order. Even though you may list multiple assets in the 'multi' table - on a single work order - any financial charges are posted against the main workers GL account. There is no way to distribute that cost against each asset. If this is required, you cannot use the multi table. You must use either tasks or child work orders (which can have their own GL Accounts) to identify where costs are applied. <div>&nbsp;</div> Hope that helps.

4 Venkataseshan comentou às Link permanente

Hi David, <div>&nbsp;</div> Thanks. <div>&nbsp;</div> My Scenario: There are 100 locations in Routes for which I have individual Child WO. But I will report Labor Actuals against Main WO but costs should be equally distributed among 100 components WO. And this should be reflected in each individual Maintenance costs of the locations. <div>&nbsp;</div> Please clarify if there are any possible workaround for this.

5 DavidHavican comentou às Link permanente

Venkataseshan, this would require customization

6 callenb comentou às Link permanente

How would I model a task that requires Craft "A" for 5 hours and Craft "B" for just the first and last hour? Can you model resource requirement profiles using leads and durations in Maximo like you can in scheduling tools?

7 DavidHavican comentou às Link permanente

@callenb - If you need one laborer to work on one part of a work order and another laborer to work on a different part - Create one parent work order with multiple tasks. Each task can then be assigned out individually and scheduled individually. You can also define start time and lead times for the individual tasks in the schedule.

8 completeaim comentou às Link permanente

David, with each new version of Maximo, IBM appears to be making task work orders with all the functionality of stand alone work orders. You comment that tasks can not be added to Task work orders. Though, I can switch to the task work order (reference WO) and add additional tasks. The only difference appears to be the inability to change Work Type on tasks. Other reasons to simply use 'tasks'?

9 DavidHavican comentou às Link permanente

@completeaim When you bring a task up as the primary record in Work Order Tracking and add a task to it, it is no longer a task. Its ISTASK flag is set to N. Its WOCLASS does remain as a WOACTIVITY, but it is no longer treated like a task. It is treated like a stand alone work order. <br /> We did want to give pretty much all of the capabilities of work orders at the task level. This way they are as flexible as anyone might need them to be.

10 sunk818 comentou às Link permanente

If a WO w/ Tasks was generated from a PM with Routes. Will the WO change to complete when all the WO tasks are changed to COMP? I have Inherit Status Change for both the Route and PM, but I don't see the WO change to COMP.

11 DavidHavican comentou às Link permanente

@ swkim90049 - You would need to turn on flow control if you want the statuses to change automatically like that.

12 ArtGarrard comentou às Link permanente

David, quick question, multiple assets/Locations on a workorder are added to the underlying table MULTIASSETLOCCI table, where is the value for the 'isprimary' column of this table derived from and does it determine whether or not a record is entered in the table.

13 DavidHavican comentou às Link permanente

@ArtGarrard - The primary flag indicates the asset and location that are defined the work order header. You will not see these displayed in the multi asset/loc table window, but they are stored in the database table. This is for better search performance.