Skip to main content

Extends preventive maintenance planning

Project description

Beta License: AGPL-3 OCA/maintenance Translate me on Weblate Try me on Runboat

This module extends the functionality of Odoo Maintenance module by allowing an equipment to have different preventive maintenance kinds.

Table of contents

Installation

Install the module.

Should you already use the maintenance module and have equipments with field ‘Preventive Maintenance Frequency’ defined, a new maintenance plan will be automatically created on these equipments with maintenance kind ‘Install’.

Moreover if a Request of type ‘preventive’ exists, whose stage isn’t marked as ‘Request done’, and has a Request Date matching the equipment’s ‘Next Preventive Maintenance’, the request will be updated with the ‘Install’ maintenance kind.

Make sure you don’t have multiple ‘preventive’ requests at a stage which isn’t marked as ‘Request done’ and on the same ‘Request date’ as the equipment or the module installation will fail with a User Error.

Usage

Instead of defining a period and duration for only one preventive maintenance per equipment, you can define multiple preventive maintenance kind for each equipment.

Maintenance Kinds have to be defined through the configuration menu. Their name have to be unique and can be set as active or inactive, should these not be used anymore.

On any equipment over the maintenance tab, the maintenance plan be accessible, allowing to add different maintenance kind with their own frequency and duration. The next maintenance date will then be computed automatically according to the start’s date and the frequency defined, but the maintenance request won’t be created automatically as is the case in Odoo’s Maintenance module. In the plan there’s also a field allowing the user to set the maintenance horizon, insert the instructions to follow on the maintenance that will be forwarded to the maintenance request generated from the plan.

This module uses the original Cron job of Odoo’s Maintenance module to generate maintenance requests. To do so, it takes into account the planning horizon and generates all maintenance requests whose schedule date would fall inside that planning horizon. Therefore, the maintenance manager can have a proper planning of how many maintenance requests are programming for the future. Leaving planning horizon to 0 will only create those maintenance request that are scheduled for today.

We can also create maintenance requests from a plan using a domain for selecting the equipments. This way, we might have a single plan that will generate all the requests. In order to use it, we need to mark the Generate with Domain field.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Camptocamp SA

  • ForgeFlow

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/maintenance project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

File details

Details for the file odoo14_addon_maintenance_plan-14.0.1.6.5-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo14_addon_maintenance_plan-14.0.1.6.5-py3-none-any.whl
Algorithm Hash digest
SHA256 e74afcb8edcfb95767137d002100abaaeba12e0b6d16361514aee439c80fa43f
MD5 313e37fb69b8deaca562b62c9b21ae3b
BLAKE2b-256 224e8abe123f3d84681407272384eb253f9a028ae6fc13eed74ff62e399e391a

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page