MaintMaster blog - 22 October 2020


Separation of planned parts and withdrawn parts on jobs

Separation of planned parts and withdrawn parts on jobs

Planning and withdrawing parts on jobs: 

This is a big change and a great improvement. Instead of depending on the job status, all withdrawals of parts to a job can be made much more explicit. In job card, we have separated the planned parts for a job, and the actual used parts. Those can be the same and it’s easy to confirm planned quantity, but thay might also differ and let you easily see that difference. If you make an explicit withdrawal to a job, it will always be withdrawn when you make the withdrawal. All parts explicitly used when using the Report guide will also always be withdrawn when reported. If you have planned parts on jobs, but not withdrawn those parts, there is a new setting letting you decide how to handle this and default is to ask the user if missing withdrawals should be made when completing the job. Please have a look at the new setting in System settings to make sure the system behaves as desired.

Return unused parts: 

A new function that will save you much time, and increase the quality of your balance in stock, is the new Return function. If you planned 10 pcs of a part for a job, but only needed 8 pcs you can now simply return the left-overs. The Return functionality is introduced in the job card tab Item/Spare parts.

 

 

Updating your MaintMaster system:

You need to be a registered Solution Admin if you want to update your MaintMaster system. If you are unsure who the Solution Admin in your company is, contact MaintMaster Support

  1. Go to portal.maintmaster.com
  2. Sign in
  3. Select “Systems”
  4. Click the “Apply update” button to open a dialog to help you update your system

Why can’t I update all systems?

Any release of MaintMaster goes through a series of stages. When we reach Release Candidate, the last step before Public Release, we make it available to all Sandbox and Training systems. That way, you can test the coming functionality before it is actually released. When we declare a release to be Public Release, it’s available to systems including your Production system.