AMM3.0 compared with AMM2.0
With the introduction of objective-based maintenance, the Maintenance library and Maintenance planner have been succeeded by the Activity library and Activity planner. This section outlines the key differences between the previous and current methods of setting up planned maintenance in Planon ProCenter . This information provides guidance for users planning to implement the Activity planner in new installations. A migration tool and accompanying manual will be made available for users who wish to transition from the old to the new solution.
Business objects
The following tables provide more information about the differences between the two solutions.
Activity Library (Successor of Maintenance library)
Business object | Remarks | Shared between the two solutions? | ||
|---|---|---|---|---|
Maintenance libraries | The business object is not changed and is shared between AMM 2.0 and AMM 3.0. | Yes | ||
Standard service plans | The business object is shared between AMM 2.0 and AMM 3.0. Set ‘Activity service plan?’ to Yes to use the service plan for AMM 3.0, or No for AMM 2.0. | Yes | ||
Standard activity definitions | Replaces the Standard maintenance activity definition (SMAD). The field Scheduling method is moved to the Standard planning details business object. The following fields are no longer available: • Functionality class • Inspection regime • Maintenance free group 2 • Work type
Percentage to be completed is no longer available. Quantity and Unit of measurement are made optional in the library. Standard service plan is an optional field on the Standard activity definition, so you can have Standard activity definitions that are not part of a Standard service plan. Maintenance library is an optional field on the Standard activity definition. If you do not fill in a Standard service plan, you can fill in the Maintenance library directly via a Standard activity definition. | No | ||
Link Standard activity definition to Standard asset | You can directly link Standard activity definition(s) to a Standard asset. Useful if your Standard activity definition does not belong to a Standard service plan. | No | ||
Link Standard activity definition to Labels | Labels can be created in the Activity management TSI, which can be linked to standard activity definitions for easy filtering. | No | ||
Link Standard activity definition to Regulations | Regulations can be linked to standard activity definitions. | No | ||
Standard planning details | Replaces the scheduling actions. All schedules are time-based. (For condition-based and predictive based planning, you can use Standard activity workers). | No | ||
Standard activity costs | Renamed costs previously known as Additional costs (in the old solution) to General costs. The Produced quantity field is no longer available. Instead, all costs must be provided per single unit. An Index % can be provided, which can be used for indexation of costs. A Long term index can be provided, which is used in the calculation for Expected indexed costs for subsequent years. | No | ||
Standard checklist items | The functionality of the standard checklist items is unchanged. | No | ||
Standard activity scopes | New functionality that can be used to automatically create activity definitions based on search criteria. Can be used to create activity definitions for Assets, Properties, Spaces and Rentable units. (Activity definitions for Assets can also be generated by linking Standard activity definitions or Standard service plans to Standard assets). | No | ||
Standard activity workers | New functionality, acting as a plug-in point for custom implementations. The following functionality is now implemented as a system worker: • Copy replacement cost from the asset to the activity definition • Condition-based scheduling • Prediction based scheduling | No |
Activity planner (Successor of Maintenance planner)
Business object | Remarks | Shared between the two solutions? | ||
|---|---|---|---|---|
Activity definition | Successor of the Maintenance activity definition (MAD). The field Scheduling method is moved to the Planning details business object. The following fields are no longer available: • Functionality class • Inspection regime • Maintenance free group 2 • Work type
The field Percentage to be completed is no longer available. There is no service plan for activity definitions. To query based on the Standard service plan, filter Standard activity definitions with a certain service plan. | No | ||
Checklist items | Checklist items are available for Activity Definitions. When creating Activity definitions based on the standard, checklist items are created as a copy from standard checklist items. Checklist items now have a start and end date available. When there is a checklist items in the standard change, these changes can be applied to the Activity definition checklist items using the action Synchronize Standard (available for Action on Selection). | No | ||
Maintenance plan (Table PLN_PLAN) | You can now create a user-defined business object a maintenance plan. The content of the plan is not exclusive to Properties or Contracts. Instead, you can link any combination of Activity definitions. An activity definition can be linked to multiple plans, provided that the valid periods of those plans do not overlap. If you use only one plan for all your activity definitions, you can mark that plan as a default plan, so that new activity definition can be linked automatically. Orders can only be generated for Activity definitions linked to an active plan. | No | ||
Details - Planning details | See Standard planning details. | No | ||
Activity costs | Replaces the BO Activity definitions - Expected costs. (See also the description for the new BO Expected costs, which has a different purpose) Costs now have a start and end date available. See Standard activity costs for more changes. | No | ||
Related contract lines | The Contract activity definition no longer exists. If an activity definition is contract related, create a Related contract line to link the activity definition to the relevant contract line. If a contract ends and is replaced by another contract, the contract line of the new contract can be linked to the same activity definition. | No | ||
Activity workers | Business object to add specific functionality to an activity definition. For example: system workers for Condition-based or Predictive based maintenance. | No | ||
Cost overview periods | Read-only business object with all the periods for which cost overviews are available. Cost overview periods are generated automatically. They can be used for filtering Expected costs. | No | ||
Planned activities | Planned dates for the activity definitions, which will show on the planboard. They are generated for a maximum of three years ahead (for the further future (virtual) planned activities are calculated on opening of the planboard). Planned activities can be added manually if needed. When orders are generated for planned activities, the status of the planned activities follows the status of the Maintenance activity. If order handling is executed outside of Planon ProCenter , it is also possible to manually change the Planned activity statuses. | No | ||
Expected costs | Read-only business object with total costs per activity definition for a cost overview period. | No |
Relevant field definer settings on Activity definition
Setting | Description |
|---|---|
Period for order generation in the past | Set to restrict generating maintenance orders for Planned activities in the past. In a pop-up the user can select a period (Possible values: Minute, Hour, Day, Week, Month, Year, Unspecified) and a quantity. If Unspecified is selected, the quantity is read only. |
Generate orders on working days? | If Yes, orders generated outside working days are moved to the next working day. |
Prevent order generation outside contract line period? | If Yes, orders will not be generated for Planned activities that are not covered by a contract line. These will be ignored in order generation, if based on the settings for order generation no Planned activity is eligible for generation an error occurs. Default value is No. |
Fields selected as optional cluster criteria | Fields of the Activity definition, used as cluster criteria. |
No. of months to generate planned activities | Number of months for which Planned activities are generated. Minimum = 1, maximum = 36. Default = 12. |
No. of years for long-term cost overview | Number of years applicable to cost overview period of the type 'year'. Minimum = 0, Maximum = 50. Default = 30 When this setting is updated, the following message is shown: To create {BO expected costs} for the specified number of periods, please run the Generate expected costs batch. |
No. of Months for short-term cost overview | Number of months for cost overview period of the type 'month'. Minimum = 0, Maximum = 60. Default = 36 When this setting is updated, the following message is shown: To create {BO expected costs} for the specified number of periods, please run the Generate expected costs batch. |
Changed concepts
Concept | AMM3.0 | ||
|---|---|---|---|
Creating a plan with activity definitions | Activity definitions should be created first: • Manually, by using the Add button. • By applying a Standard activity definition in the wizard. • When creating an asset based on a standard asset with linked Activity definitions. • Generated, based on Standard activity scopes. Activity definitions can then be linked to a plan. If a default plan exists, they can be linked automatically. | ||
Create contract based maintenance activities | • Create Activity definitions as described above. • Create Linked contract line. A related contract line can be created: • Directly when selecting a contract line in the wizard for creating Activity definitions. • In the Activity Planner, using the Add button step Related contract lines at the details level. • Using the action Add related contract lines on the Activity definition layout (available for action on selection).
| ||
Condition based maintenance | • Create Activity definition with a planning detail and with a Fixed scheduling method. • Add Activity definition worker with classname DeteriorationCurvePlanning and fill in deteriorationCurve and topic to use. • Schedule the worker to run, or run manually.
| ||
Predictive based maintenance | • Create Activity definition (no planning detail required). • Add Activity definition worker with classname PredictionBasedPlanning and fill in consumptionThreshold, counter and counter definition. • Schedule the worker to run, automatically, using Alerts TSI. Use the following filter on Activity definition workers: Classname contains PredictiveBasedPlanning | ||
Generate orders | Generate orders with action on activity definition. Orders can be generated when: • The activity definition is Active. • Standard order is filled in. • Activity definition is linked to an active Plan. |