Product Tour


Weavecentrix Desktop is an integration application for schedulers and planners who use SAP Plant Maintenance. It can help businesses and maintenance professionals to take their maintenance schedules to the next level by vastly simplifying the tasks involved in managing your maintenance schedule externally to SAP PM. By making the integration process a simple activity, Weavecentrix Desktop lets you make use of the full power of a dedicated scheduling tool.

Weavecentrix Desktop gives you a familiar Microsoft Windows desktop environment, complete with a simple representation of your work orders both in SAP and P3, designed to make managing your schedule easy.

The Weavecentrix Desktop Product Tour walks you through the stages a maintenance planner makes as they set up a new weekly schedule and then follows them as they progress the schedule. At the end of each stage, you will find navigation buttons to take you both to the next stage and the previous stage.

In each section, we demonstrate the basic functionality of Weavecentrix Desktop and how it helps you manage your schedule. We also highlight the additional functionality related to each section and give you pointers to the appropriate area of the help system where you can get more information.




Key Features


Key Benefits

Simple, out-of-the-box installation

Start creating your P3 schedules straight away

Fast return on your investment

Uses P3 to manage your SAP schedule

Lets you as the scheduler use the best tool for the job

Protect your investment in your scheduler’s training and get the best use out of their experience.

Twin-panel view give you a simple side-to-side comparison

Easy to understand dual system representation

Reduces the investment you need to make in staff training


Easy to use front-end on your desktop with well structured menus and toolbars representing the most commonly used tasks.

Use a familiar desktop environment

Extensive on-line help system, featuring context sensitive help

Help on demand, relevant to the task you are doing

Progress bars, status lights and status messages

Keep you in the loop as transfers between SAP and P3 are progressed, showing you clearly how long is still to go

Easily change the work order and activity fields you see on the screen through helpful wizards

See the work order information that means the most to you, letting the tool work for you

Spent more time optimising your maintenance schedule by quickly selecting work orders based on the priorities relevant to your business

Drill down on work orders and activities on the screen to see the detailed information

You don’t have to switch between multiple tools for more information

View work orders and activities on screen grouped by the same criteria by using the mapping wizard

Helps you build your schedule based on you’re the priorities that matter to you

Mapping Wizard to quickly and simple change the way SAP work orders are set up in P3.

Spend less time manipulating data into the way that you need it and reduce errors through entering data in to different systems.

More time spent using your schedule to increase your maintenance productivity and less time wasted getting information into the schedule in the first place

Automatically creates your activities in P3, coded the way you want them to be

Puts the information into your schedule that you need to manage the schedule priority

Flexible filters for extracting SAP work orders which you can change using a simple filter wizard

Quickly change the way that you extract work orders, reacting to the changes in maintenance priorities.

Improve maintenance agility through the ability to quickly reschedule as priorities change

Quickly change your schedule by changing the SAP work orders in your schedule and the priority that you schedule them

React quickly to manage changes in the priority of your maintenance activities

Use SAP’s actual dates, work and costs in your P3 schedule

Progress your P3 schedule using SAP’s progress.

Sets up work centre resources in P3 with capacity information from SAP

Lets you use resource levelling in your schedule

Optimise your resource utilisation, increasing your maintenance productivity

Automatically creates resource assignments in your P3 schedule

Show your resource loading on our schedule

Sets up PRT and component assignments against your P3 activities

Manage PRT and component availability as part of your P3 schedule

Reduce logistics delays by optimising your demands through driving them from your maintenance schedule

Update SAP schedule dates from your P3 schedule

Drive your SAP maintenance schedule from your P3 schedule

Optimise your SAP maintenance schedule by using best-of-breed scheduling techniques





The best way of understanding a product is to use it. That’s why we give you a free trail of Weavecentrix Desktop before you buy it. If you can see a product start to deliver benefits to you even before you have purchased it, then you can be sure that you are getting a good return on your investment.

To help you see how Weavecentrix Desktop can help you to deliver those benefits, this product tour walks you through a typical scenario for a maintenance planner setting up a weekly schedule and then working through it.

Planner Notes  Bill Thompson normally started his weekly schedule in his head whilst on the way to work. As a planner and scheduler for four work crews with 20 technicians, he usually has a good feel for the bigger jobs that fall due in the following week as well as an idea of how much carry-over is likely from the current week’s schedule. That gives him a starting point for the next weekly schedule. With around 150 hours of available time to schedule each day, the problem is getting the average 50 hours of preventative maintenance scheduled, fit in the bigger jobs and then progressively allocate jobs to each work crew to fill the schedule whilst making sure that any delays from tooling up, parts availability and travel time are kept to a minimum. All of this has to be done whilst maximising the operational availability of the plant.

By the time Bill has found a place to park his car in the car park, he knows that a good deal of his work will come from the outage due to the condenser line repair job. Bringing down the condenser means the acid scrubber and vacuum pump will have to be brought down. That gives an opportunity to look at bringing forward some maintenance work on those areas as well.Planner

After clearing his email, Bill starts up SAP and reviews the maintenance tasks lists that cover those functional locations. There are three maintenance jobs which have not been released yet: one monthly and two six-monthly jobs. Bill fires off a quick email to the maintenance engineer Fiona Cosgrove, asking her if he should call off these jobs early. Knowing that there is a line shut scheduled for early next year, Bill reckons that Fiona will get him to call off the monthly for this week and then delay the two six-monthly jobs until the shut next year.

Bill opens his notebook and jots down the priority for the weekly schedule. At Bill’s plant, the SAP work order types have been set up as follows: PM01 -Reactive maintenance work orders; PM02 - Proactive maintenance work orders; PM03 - Preventative work orders; PM04 - Capital works ; PM05 - Repair work orders.

The priority system is Urgent, High, Medium and Low. Only reactive work orders are given Urgent or High priority.

Bill knows that he has to work through the high priority reactive jobs first. The urgent jobs are not put into the schedule as they get done immediately when they are raised. He makes a note to include any medium jobs for the same system as the high priority job, especially for the condenser line.

After that, he can go through the medium proactive maintenance jobs. Bill remembers that there is an outstanding capital works order for upgrading the bund barrier at the acid scrubbers. The existing barrier kept getting damaged by containers being offloaded so someone came up with the idea of replacing it with 18" casing. He ever remembered the work order number for that one.

After going through the medium work orders, Bill will continue with the low priority work orders until he runs out of available hours on his work crews.




Once Bill has established the priority process he is going to use for this weekly schedule, he knows he is ready to start creating the schedule.

Forecast Availability The first thing Bill does is open P3 and creates a blank project set for a time unit of hours which he calls WK24 as it will be the 24th weekly schedule of the year. The only thing that Bill does in the project is to set up the global calendar for a Monday to Friday working week with 8 hour days. Bill knows that Weavecentrix Desktop will take care of everything else for him. That done, he shuts down P3.

Bill double-clicks on the Weavecentrix Desktop icon on his desktop. As it starts up, he quickly checks the man hour estimates that he was given by his crew supervisors and jots down the numbers into his notebook. He’ll be using these estimates as the basis of his weekly schedule.

There is some expected carry over work for both crews that he needs to take off his availability forecast.

He does a quick calculation in his head and comes up with a total of 730 hours that need to be scheduled. That’s about average for his week.

By this time, the Weavecentrix Desktop window has opened on Bill’s screen. The workspace is divided vertically into a SAP workspace and a P3 workspace. The SAP workspace is on the left and the P3 workspace on the right. This representation model clearly defines Bill’s tasks: left-to-right to transfer work orders from SAP to P3; right-to-left to update the dates in SAP with the dates from the P3 schedule.

The diagram below shows the different screen elements that Bill can see. You can click on a screen element to learn more about it and to be given a link to a detailed section about that screen element.

Bill clicks on the icon for logging in to SAP which is on the SAP toolbar. The login dialog pops up and Bill enters his SAP password. The rest of the information need for the dialog is saved from yesterday so he doesn’t have to enter it again.

Whilst it is logging in to SAP, Bill clicks on the icon for logging in to P3 which is on the P3 toolbar. By the time he has done that, Weavecentrix Desktop has finished logging on to SAP.

Weavecentrix Workspace



In this part of the tour, Bill is going to select a range of work orders from SAP which he wants to transfer into his weekly schedule. He knows that he doesn’t have to be exact here. If there aren’t enough work orders in the schedule, he can come back for more. If there are too much, he can just delete them from the schedule – they’ll still be there back in SAP but won’t interfere with his schedule.

Planner Notes Bill quickly glances at the priority notes he made in his notebook. His first pass will be for PM01 orders which are not the highest priority. He will be looking for open work orders in the date range up to the end of the week. He normally does a search for order up to 3 months prior to that.

In Weavecentrix Desktop, Bill clicks on the Filter toolbar icon on the SAP toolbar. His preferred filter layout is displayed on the dialog. Bill can switch between a number of different filter layouts that he has set up using the SAP Filter Template Wizard but this one is the one he uses for his day-to-day work. He has set up this filter layout to have three tabs. The first tab, which Bill called Main, is the one that contains the fields he uses the most to extract work orders out of SAP.

On the Main tab, there are the three SAP work order states: Outstanding; in process (which Bill has renamed to In Progress because it has always annoyed him) and Completed. There are the From and To dates that are used in the SAP work order list selection screen. Finally, Bill has added the work order number, order type and work order priority to this tab.

SAP Work Order Filter

Bill can set defaults for any of the fields on the filter so that he doesn’t have to keep adding them in each time. He hasn’t set up any defaults on the Main tab because he changes the values on it most time that he uses it.

However, on the next tab, the Group tab, Bill has set up a number of fields which are specific to his work area and he normally has these fields set up with defaults. These fields are Work Centre, Planning Plant and Planner Group. It is very unusual for Bill look at work orders which don’t have the same set of values for these fields so Bill has set them up as defaults.

Grouped SAP Work Order Filter

The rest of the fields on the Group tab are fields that Bill uses when he wants to look at grouping work orders together in a particular way. For example, when an outage is planned, work orders may be assigned a Revision Code. Bill’s usual method of using these fields is to rely on the Functional Location and Equipment field. Hence, when he wants to look for work orders in the same process train, he will use the Functional Location field.

The final tab, Extras, contains those fields that Bill finds useful to have available but doesn’t use on a frequent basis. One of the fields is the Created By field which Bill sometimes uses to look up his own work orders.

Bill fills in his selections based on his priority notes. On the Main tab sets the Outstanding and In process checkboxes to on and the Completed checkbox to off. He enters a date range which extends up to the last day of the next week and then goes back to 3 months prior to that. On this pass, he is just looking PM01 work orders but he knows that the result will be grouped by work order type because he set it up that way through the Mapping Wizard so he may as well get all the work order types in one hit.

Bill clicks on the OK button and Weavecentrix Desktop then requests SAP for the work orders. Whilst the work orders are being retrieved from SAP, a progress bar is show at the bottom right of the SAP window.


Filtered Work Orders


The SAP work orders are displayed in the Summary Screen on the SAP window. Although you can change the layout of the fields on the Summary Screen by using the SAP Summary Screen Wizard, Bill hasn’t felt a need to. If he needs more information about a work order, he usually just clicks on the work order entry and then looks down at the detail screen below where he can see all of the information for the work order. In this example, he has clicked on a work order and then scrolled down the detail screen to check the functional location. He can also click on the work order line to expand it out to show the operations, components and PRTs. He can also use the SAP Summary Screen Wizard to change what is shown on those lines as well.




Before starting transferring work orders across to next week’s schedule, Bill wants to have a quick check on last week’s schedule. He can’t remember off the top of his head the forecast end dates for a couple of jobs in the same condenser line as the scheduled outage for the repair job. Rather than start P3 and then open the project for that weekly schedule, Bill can open the project in Weavecentrix Desktop directly and look at the work orders there.

To open last week’s project, Bill clicks on the Open Project toolbar icon on the P3 toolbar. He selects the project called WK25 from the list and then clicks on the Open button. As the project for week 25’s weekly schedule loads, Bill keeps an eye on the progress bar and the status messages. Once the project is fully loaded, the status light on the P3 window changes to a green light. Bill looks at the summary screen in the P3 window and sees that the activities are grouped into work order types and then by work orders. Bill knows that he can quickly and easily change the way the activities are grouped by using the Mapping Wizard.

Bill scrolls down the list until he finds the first of the two work orders he wanted to have a closer look at. Finding it, he clicks on the plus icon at the work order level which expands the work order out to the activity level. Bill has used the P3 Summery Screen Wizard to arrange the displayed fields at the activity level so that he can see the forecast dates. This one looks OK so Bill moves on to the next work order and double checks that one as well.

After finishing his checks, Bill is now ready to start working on the week 26 weekly schedule.

Bill clicks on the Open Project toolbar icon again and opens the WK26 project this time. The WK25 project is closed and WK26 opens. Bill doesn’t see any activities yet but that’s because he hasn’t transferred any yet. That’s the next step on the tour.



Open P3 Project



As soon as Bill has opened his P3 project for his week 26 weekly schedule, he is ready to begin transferring work orders from SAP into his project.

Bill’s first step is to select the work orders to transfer.

From his notes on priority, Bill selects all the PM01 work orders. Just by looking, Bill knows that he needs a lot more work orders to fill his schedule so he selects all of the PM02 work orders as well. He does this by clicking on the first work order in the PM01 group and then, whilst holding down the shift key, clicks on the last work order in the PM02 group. This highlights all the work orders in his selection. Bill clicks on his spacebar to mark the work orders with a tick. It is the ticked work orders only that will be processed on a transfer.

Bill thinks that those work orders will be sufficient for the first pass but he will no doubt be back for more before his schedule is complete.

He now moves on to the second stage which is the transfer itself.

Bill looks at the SAP toolbar at the top of the SAP window. On of the toolbar icons that were greyed out before was the Transfer button. It is shaped like an arrowhead. It became active once Bill opened his P3 project.

Satisfied, for now, with the work orders that he wants in his project, Bill clicks on the Transfer button on the SAP toolbar.


Transferring Work Orders


As soon as he does this, progress bars and status messages on both the SAP and P3 status bars start showing the progress and Bill can see the activities being added on the P3 window. When the transfer is complete, both the SAP and P3 windows show the green status light, indicating that the processing is now finished.

Bill does a quick visual check on the line up of work orders in the SAP windows with the work orders now showing in the P3 window. The work orders are grouped by work order types in both windows. Under the work order types PM01 and PM02, the work orders match line for line. There are no work orders in the P3 window for order types PM03 and above as Bill hasn’t transferred any yet.

Happy with the transfer, Bill’s next step will be to go into P3 to build his schedule. Experience has taught him that he normally comes back to Weavecentrix Desktop to get more SAP work orders. Therefore, instead of shutting it down, he juts clicks on the Logout of P3 button on the P3 toolbar. This frees up his P3 license so that he can work in P3.


Bill starts P3 and opens up the week 26 project. The first thing that Bill sees is all the activities that have been transferred by Weavecentrix Desktop. His first task is to set up his layouts to use his activity codes.

Bill selects the Activity Codes item on the Data menu. This shows the activity codes for the project and their values. Bill clicks on the activity code for Functional Location, called FUNC, and scrolls down the values until he finds the one that he is looking for: DM-02 – Main 2 condenser line.

Activity Codes - Functional Location

Rather than create a new layout for this weekly schedule, Bill will copy his preferred layouts from last week’s schedule. Before he does that, he wants to set up an activity code which will show whether an activity is included in his weekly schedule or not as well as a filter based on this activity code. He uses these in each weekly schedule and his layouts refer to them so he needs to set them up before he copies the layouts. His activity code is called PLAN and he sets up a single value called WK26 which he will assign to activities in this weekly schedule. The filter Bill calls FL-51 and sets it up as all activities where the activity code PLAN has a value of WK26. That done, Bill copies the layouts from the previous week’s projects.

Activity Code - Plan

Once he has copied the layout, he selects his standard weekly scheduling layout which reformats the display into something that he can begin to work with.

Before he forgets, Bill grabs his notes on forecast availability and turns back to P3 to update the resource availability. Bill selects the Resources item on the Data menu. This displays the project resources. As Bill expected, the SAP work centres have been automatically added as resources with a default limits and prices set. Bill clicks on the first of his work centres, PMMECHA, and refers to his resource availability sheet. On Monday, he has 35 hours available out of a possible 44 hours for his 6 person crew. With an effective working day of 7.25 hours, this gives a normal limit of just over 4.8, down from the usual 6. In P3 terms, this is 4.8 man hours available for every planning unit for that day. As this project has a planning unit of hours, this means 4.8 hours per hour for the day. P3 rounds this up to 5 hours in the Normal Limit so Bill makes a mental note to suitably adjust any further rounding. He puts Monday’s date as the Through Date.


Bill continues down the resource availability list, adjusting the normal limits for his work centres to reflect their forecast availability for the coming week. With this information entered, Bill can perform accurate resource levelling on his work centres for his weekly schedule.

With his layout set to a work order view of his activities, Bill uses his knowledge and experience to best use by setting the relationships and constraints on the activities.

For example, three of the work orders are for jobs on the main feedstock receiving station. For the weekly production meeting, Bill learnt that a pig run is bring carried out over the Monday night but it is due to be docked and clear in the pig receiver bay by 8.00am. However, during the last two pig runs on that line, the production team had some problems at the pig receiver so Bill wants to give them an extra 4 hours to clear the area before scheduling the start of the jobs. He enters the starting constraints against these jobs.

After applying logic to the PM01 work orders, Bill wants to have a check on his crew total hours for these jobs. He tags the first activity with a PLAN activity code of WK26. He then fills down to the last activity in his PM01 work orders, marking them all as in the week 26 weekly schedule.

Schedule 1

At this stage, Bill isn’t too worried about durations as none of the work orders is that long. Rather, his emphasis is on making sure that his work crews have sufficient work for the coming week.

Bill switches his layout to the one that he uses for doing his rough cut work assignment. It shows the work grouped by the PLAN activity code values and then by the work crew. The layout also shows the totals for each grouping. Bill checks the total hours planned for each group and sees that he still has plenty to play with.

Schedule 2

Now that the PM01 work orders are in the schedule, Bill can start looking at the condenser line storage. He switches back to his standard view and adds the functional location column temporarily to his layout. This highlights that there are 5 PM02 work orders that fall into the condenser line functional location. Bill tags these work orders with a PLAN activity code of WK26 which puts them into his weekly schedule.

He then spends the next hour going over the job cards and their histories for the jobs currently selected for the condenser outage. He needs to fully understand the implications of each job. This involves a couple of phone calls and a quick meeting with Fiona Cosgrove, the maintenance engineer and, on her advice, he gets Derek Mason, one of the senior mechanical technicians, to drop by to clarify some clearance issues. Derek was the lead tech on the last outage to the condenser.

Bill and Derek walk over to the site of one particular job on the scrubber that needs a gas line purge. A contractor’s team will be doing the purge but Bill needs to know the extent of the assistance they need and any clearances they require. Derek worked with them last time so fills Bill in on the procedures they used last time. Bill makes some notes and takes a couple of digital pictures to add to the job card for this one.

After lunch, Bill is ready to have a look at the resource profiling for his crews. At this stage, the jobs that Bill has included in the week 26 weekly schedule have not been scheduled or levelled so Bill knows that the crew hours will be overloaded. Bill brings up the layout view that he uses for resource profiling of his work crews in his weekly schedule. As expected, the first of his four work crews is overloaded.

As a first cut, Bill decides to do a quick schedule and resource levelling. That will give him a rough cut where he can then have a closer look at the job scheduling and use his experience to optimise the job loading for the crews whilst keeping delays due to travel times, parts availability or access restrictions to a minimum.

Schedule 3

After the rough cut schedule and resource levelling, Bill sees that the crew work hours have been smoothed out to fit they available hours. He notes that he still has 250 hours still to schedule for the first work crew. Most of those hours will be used for proactive maintenance jobs. Bill is pleased because it looks like that will exceed the target for the KPI on the percentage scheduled proactive work vs reactive work. That’ll make it the 8th week in a row that they’ve beaten that particular target on the KPI.

At this stage of the tour, Bill is about half way through producing his detailed weekly schedule for 4 work crews. He is about to go back to Weavecentrix Desktop and get more work orders to put into his weekly schedule.

We’ll leave Bill here and come back to him on the next stage of the Weavecentrix Desktop tour where he has finalised his weekly schedule and is just about to update the work order dates in SAP directly from his P3 weekly schedule.


By now, Bill has finalised his weekly schedule for week 26 in P3. His next step is to load the work order dates from his P3 schedule into the SAP work orders.

Bill has ensured that his schedule provides sufficient work for each of his four work centres and that their work loading has been levelled over the week. Any parts requisitions or PRT requirements have been checked and, where availability could potentially cause a problem, appropriate constraints have been entered. To avoid delays, staging of equipment for the jobs has been arranged and scheduled as well.

The travel time between jobs has been accommodated in the schedule. External contractors and inter-trade assignments have been negotiated and the times locked down.

The condenser line outage has been reviewed by Fiona Cosgrove, the maintenance engineer, as well as the production supervisor. Although the outage is a small one which Bill feels doesn’t warrant its own specific schedule, Bill is aware of the higher level of scrutiny and resolves to keep a close eye on it.

At this point, Fiona walks into Bill’s office. She wants to look over the digital pictures that Bill took at the site of the gas line purge job, scheduled as part of the condenser line outage.

Whilst Fiona looks over his shoulder, Bill opens the relevant work order in SAP to look at the photos in the notes. His eye is immediately drawn to the work order header fields for the work order. Bill sees from the system status that someone, probably in production, has scheduled the work order, moving it out a week. He mentions this to Fiona who gets pretty irate at this interference with their maintenance schedule.

Bill calms her down, telling her that it isn’t a problem. Once the P3 schedule dates have been uploaded to SAP by Weavecentrix Desktop, the SAP work order schedule dates and nobody else can change them. Fiona wasn’t aware of this and asked Bill if she could see him doing the upload. As it only takes a few minutes, Bill agrees.

First though, they review the digital photos of the gas line purge job with Bill referring to his notes to brief Fiona on the access problems.

With the gas line purge job out of the way, Bill opens up a list view of work order in SAP for Fiona, indicating the forecast dates and the system status. He takes a printout for later, highlighting the gas line purge job with a yellow highlighter.

Next, Bill starts up Weavecentrix Desktop. He uses the SAP toolbar to login to SAP and then the P3 toolbar to login to P3. He opens the week 26 weekly schedule using a toolbar button on the P3 toolbar. Once the schedule loads, Bill points out the Transfer button on the P3 toolbar button to Fiona. This is the button he will use to update the SAP work orders with the dates from his schedule in P3.

For this schedule, Bill is happy with all of the activities so he can select all of them for uploading. Occasionally, Bill may upload a few in advance of the rest, particularly if the work orders have long lead times or complex logistical or subcontractor requirements. He does this so the new work order dates can flow through to the logistics modules in SAP, updating the purchase and service order required dates.

He clicks on the Select All button on the P3 toolbar which marks all of the work orders for inclusion in the transfer. Finally, Bill clicks on the Transfer button.

Fiona is impressed as she watches the progress bar climb whilst the work orders are processed and says as much to Bill. Only last year, it was taking over a day to update the work order dates in SAP and there was no guarantee that someone wouldn’t reschedule them afterwards. Bill smiles wryly. For Bill, this time saving has meant he can concentrate on the schedule and not the drudgery of shifting data between systems and checking for double entry errors. It has also meant an increase in his personal job satisfaction as his ability to focus on the schedule has progressively improved their performance against the schedule KPIs.

Once the progress bar finishes and the status light changes to green, Bill goes back to his list view in SAP and refreshes it. As Fiona watches on, the schedule dates change to the ones from the P3 schedule and the system status shows that the work orders are now locked. Bill hands the old work order list view over to Fiona so she can do a comparison.

After reviewing the list, Fiona asks Bill how easy is it to unlock the SAP schedule dates for a work order on the screen. Bill points out that the best way is to actually manage the work order schedule in the P3 schedule using Weavecentrix Desktop. However, if she absolutely needed to, there is a tool in Weavecentrix Desktop that clears the schedule lock for a work order.

Satisfied with Bill’s answer, she pats Bill on the back, complimenting him on doing an excellent job, before leaving for the monthly plant management planning meeting. She’ll recommend Bill’s system to her counterpart on the products part of the plant where they’re having trouble meeting the targets for their schedule compliance KPIs.

Bill goes back to his P3 schedule and starts a print run for schedule cards. He’ll put these on top of the job packs for the crew supervisors and then put the lot onto their crew job trays.

We’ll leave Bill as he finishes up his weekly schedule. In the next stage of the tour, we’ll revisit Bill as he begins progressing his schedule with the actuals from SAP.



It’s now Tuesday morning of week 26. Bill spent most of Monday in either management meetings or shutdown planning meetings. It was a long day.

The shutdown coordination meeting with the production team ran over schedule, as per usual, and Bill didn’t get a chance to have a chat with the maintenance team crew supervisors as he normally does. Usually, they come into the office to enter SAP confirmations for completed work. Recently, they’ve been entering partial confirmations as well for work orders started but not completed. This is because of a new schedule compliance KPI for work started on schedule which gives them credit for starting jobs on time.

Whilst the crew supervisors are entering their confirmations, Bill normally gets a chance to discuss any issue that have come up which are likely to impact the schedule and any concerns that they have over the job schedule for the rest of the week. Because he was tied up in meetings, Bill checks his in-tray for any notes from the crew supervisors. Kevin Harrington, who heads up the instrumentation techs, has left a note asking Bill to cal him about a panel circuit board that is being flown in from Germany.

Bill checks the tracking number on the UPS consignment, verifying that the shipment is on track to arrive on time for the alarm panel teardown. He gives Kevin a call, reassuring him that the part will be there on time. Whilst he has him on the phone, Bill checks with Kevin on the status of upgrades to the fuel gas heater booster panel which started on Monday morning. He makes a couple of notes but there doesn’t look like they will impact the schedule.

With no other messages from the crew supervisors, Bill starts up Weavecentrix Desktop. He’s going to get the actuals from Sap and put them into his P3 schedule. There’s normally something that drops out of that process that will need following up, even at this early stage of the schedule.

Bill logs into SAP by clicking on the button on the Sap toolbar. Whilst it is logging on, he clicks on the button on the P3 toolbar for logging in to P3. He then opens up the week 26 project using the Open Project toolbar button. Now he needs to get the work orders in his area that were started on Monday. He opens the filter dialog using the button on the SAP toolbar and enters Monday’s date as an actual start date. The fields which restrict the work orders to his work area are part of the defaults for this filter so he doesn’t have to enter them each time.

Weavecentrix Desktop downloads the work orders and Bill transfers them to his P3 project by selecting all of them and then clicking on the Transfer button on the SAP toolbar.

That done, he then opens P3 and loads the week 26 project, WK26, which contains his weekly schedule. He immediately sees by the different coloured bars on the Gantt chart that the actual dates have been loaded into his project.

After a few minutes looking at the progress, Bill spots what could be a problem. Brent Miller’s mechanical techs didn’t start one of the oil cooler jobs until the afternoon. They’d been scheduled to start mid-morning. Bill doesn’t have to reschedule to know that the knock on effect could make them unavailable for the start of the condenser line outage, jeopardising the tight schedule on that.

It looks like they probably had some more problems with the carryover work from Friday. Bill gives Brent a call and confirms that a problem hit them. They discuss what happened and Bill makes a couple of notes to add to the job history. Apparently, the emergency air compressor manufacturer’s manual is the wrong version for the equipment which meant that they had to keep going back for different sized tools. Eventually, they got the manufacturer to fax through the correct datasheets for the service but the job still overran by a few hours.

Because of the delays, Bill will need to reschedule their work so that they are available for the start of the condenser line outage. Bill and Brent discuss the options available to them and agree to bring forward a couple of smaller jobs which were originally scheduled for later in the week. One of the larger jobs will move back until after the end of the condenser line outage finish. There might be some minor reshuffling with the rest of the work but Bill agrees to doing the reschedule and having it available for Brent by lunchtime.

Bill goes back into P3 and quickly rearranges the jobs and does a reschedule. He spends a good 20 minutes, making sure that the confirmations so far are in line with projections. He uses the earned value graph on the resource profile view and even goes as far as to print off an earned value report. He also prints off schedule updates for the crew supervisors.

Once Bill is happy with his schedule, he goes back to Weavecentrix Desktop and opens up the P3 project again. He selects his work orders in the P3 window and clicks on the Transfer button on the P3 toolbar. This will make sure that the schedule in Sap is the same as the updates schedule he has in P3.

Bill will do this on a daily basis for the rest of the week.

Bill’s ability to quickly reschedule as situations develop and priorities change has helped his maintenance group lead the plant in schedule compliance. This maintenance agility has also improved their maintenance productivity. They have been recognised as significant contributors to the improvements in plant uptime.

We’ll conclude the product tour at this point. We hope it has helped you get a feel for how Weavecentrix Desktop can help you get the most out of your maintenance schedule.

For an overview of the steps that Bill used in this tour, take a look at the section called Basic Steps for Integration.

There are specific business scenarios which have been developed to let you see how Weavecentrix Desktop can be used and give you some ideas for how you can use it in your industry:

·      Weekly scheduling with Weavecentrix Desktop

·      Minor Shuts and Opportunity Outages with Weavecentrix Desktop

·      Shutdown Planning with Weavecentrix Desktop