Initial commit: Odoo 18.0-20251222 extra-addons

maintenance_plan/readme/CONTEXT.md

@@ -0,0 +1,8 @@
+Despite Odoo's built-in recurrence functionality included in the maintenance
+requests themselves (since 17.0), this module could be needed for some reasons:
+- Odoo implementation is javascript only
+- Some companies already work with the existing "Maintenance Plan" workflow
+- Some modules are depending on this one
+
+For reference, this module was initially set deprecated when migrated to 17.0:
+https://github.com/OCA/maintenance/pull/414#issuecomment-2668929617

maintenance_plan/readme/CONTRIBUTORS.md

@@ -0,0 +1,9 @@
+- Akim Juillerat \<<akim.juillerat@camptocamp.com>\>
+- Matteo Mazzoni \<<matteo@appcademy.tech>\>
+- David Alonso \<<david.alonso@solvos.es>\>
+- Adrià Gil Sorribes \<<adria.gil@forgeflow.com>\>
+- Jordi Ballester Alomar \<<jordi.ballester@forgeflow.com>\>
+- Lois Rilo \<<lois.rilo@forgeflow.com>\>
+- Enric Tobella \<<enric.tobella@dixmit.com>\>
+- Alexei Rivera \<<arivera@archeti.com>\>
+- Yann Papouin \<<ypa@decgroupe.com>\>

maintenance_plan/readme/DESCRIPTION.md

@@ -0,0 +1,2 @@
+This module extends the functionality of Odoo Maintenance module by
+allowing an equipment to have different preventive maintenance kinds.

maintenance_plan/readme/INSTALL.md

@@ -0,0 +1,15 @@
+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.

maintenance_plan/readme/USAGE.md

@@ -0,0 +1,30 @@
+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.