[RFC] Fleet Inspection Report

[brian10048]

Background

Some companies are required to complete inspection reports to ensure the ongoing safe operation of fleet vehicles. Typically these are performed every day prior to using a vehicle. Also known as Pre-Trip Inspection or Daily Vehicle Inspection Report (DVIR)

For example, common inspection points might include:

• Lights
• Mirrors
• Tires
• Windows

Since all organizations may have different requirements, a configurable list of inspection points (fleet.inspection.item) will be made available.

Technical Specifications

• fleet.inspection - New Model
  • vehicle_id many2one to fleet.vehicle
  • vehicle_odometer float
  • date_inspected
  • inspected_by many2one to internal user
  • inspection_line_ids one2many to fleet.inspection.line
  • note char
• fleet.inspection.line - New Model
  • inspection_item_id many2one to fleet.inspection.item
  • result boolean
• fleet.inspection.item - New Model
  • name text

[marcelsavegnago]

@brian10048 fleet.vehicle.inspection.note can it be an html field? (I think it’s easier to write a problem report) or do I create a new field to further detail the problems?

[marcelsavegnago]

@brian10048 I am also interested in adding photographs of the inspection and associating it with the inspection lines .. simple form. What do you think ?

[marcelsavegnago]

@brian10048 We can include in the roadmap the implementation of inspection templates that can be associated with vehicle models and include as a suggestion in the inspection form.

[brian10048]

@marcelsavegnago

I am OK with the HTML field

Photos would be an awesome addition. Also, I was thinking about the inspection lines more, and I wonder if we make each inspection line have a Pass and Fail button? Instead of just a checkbox for result, we can make the user choose to either pass or fail an individual inspection item. And later on, maybe an action that is triggered upon a failure.

Yes, I had thought about specific templates for specific models, or maybe even tags. This would be great

I also think we should add a smart button on the Vehicle form to go to that vehicle's inspections

[marcelsavegnago]

@marcelsavegnago

I am OK with the HTML field

Ok

Photos would be an awesome addition. Also, I was thinking about the inspection lines more, and I wonder if we make each inspection line have a Pass and Fail button? Instead of just a checkbox for result, we can make the user choose to either pass or fail an individual inspection item. And later on, maybe an action that is triggered upon a failure.

I liked the idea. I will make the other adjustments that we mentioned and if I can, I will see this issue today.

Yes, I had thought about specific templates for specific models, or maybe even tags. This would be great

Perfect.

I also think we should add a smart button on the Vehicle form to go to that vehicle's inspections

Yes, I will include the button now.

[mamcode]

Hello @brian10048 @marcelsavegnago I see this module very useful, I can give a hand with technical review when the PR is ready for review. Thanks.

[marcelsavegnago]

@brian10048 ready to review. Photographs and templates are not included but are on the roadmap file.

[marcelsavegnago]

Tests and demo data included

[marcelsavegnago]

@brian10048 and @mamcode Do you know if the synchronization of the repository with the OCA app store is OK?

[brian10048]

@brian10048 and @mamcode Do you know if the synchronization of the repository with the OCA app store is OK?

@marcelsavegnago I'm not sure

@sbidoul can probably answer questions about the OCA app store synchronization

[sbidoul]

@brian10048 The failing appstore sync is probably due the the bad development_status keys in manifests in this repo, such as

fleet/fleet_vehicle_service_kanban/__manifest__.py

Line 10 in 13abf88

"development_status": "Stable",

that should be Production/Stable instead.

There will soon be a pylint-odoo check for that.

[marcelsavegnago]

@brian10048 #24 (inspection template)