Reorganizing Work Centers from distributed to centralized support crews

Helped a client this week change their work center organization from decentralized to centralized. This was for support groups only … contractor resources that augment the facilities area based employee/hourly crews. This was done for scheduling purposes and was a three step process and although the client had moved to central resources a while back had preventive maintenance data that still pointed towards the unit based resources.

As an example the Firewatch (FW) resource had work centers had FW01, FW02, FW03 … that represented the area that they were supporting. We created a FWGP (general plant) … I did propose FWCN for central but GP is a nomenclature used for other resources, and did this for the other CV, IS, ME, PT, PW, SF work center designations.

We also wanted to disable the use of the distributed work centers but could not flag them for deletion as they were in use in TECOed/CLSDed work orders. Google really helped with that one (see bullet 3 below).

For each resource group we then :

  1. Ran IA38 (list operations for task lists) for each resource group and mass changed them to their GP work center.

  2. Ran IW37 (list work order operations) for each resource group and mass changed them to their GP work center.

  3. For each unit based work center used IR02 and changed their usage from 004 (plant maintenance ) to 000 (no task list categories). This prevents them (point forward) from being assigned to task lists / notifications / work orders but does not impact them historically.

Finally, we performed positive / negative testing to

Screen prints from the process are shown below

IA38 being used to update the work center of the task list operation

IW37 to update the impacted operation work centers

IR02 to block work center usage

IW21, and other transactions, where used to positively / negatively test that the work center blocked without impacting historical data.