7fa54d8fc9
Per-step audit caught real enforcement bugs across all 9 WO kinds.
Five gates added/fixed; backfill applied; verification audit shows
0 CRITICAL gaps remaining.
**1. Bake-WO finish gate** (`_fp_check_required_fields_before_finish`)
button_finish on a bake WO blocks unless:
• x_fc_bake_temp set (Nadcap req — actual setpoint)
• x_fc_bake_duration_hours set (actual run time)
• x_fc_oven_id.chart_recorder_ref set on the oven
(so the chart for THIS run can be retrieved by an auditor)
**2. Rack-WO start gate** added to button_start.
**3. Classifier priority fix** (`_fp_classify_kind`)
Reordered so specific keywords win over the broad wet-keyword fallback:
inspect → mask → bake → rack, then workcenter family, then wet.
"Post-plate Inspection" now → inspect (was wrongly → wet).
"Oven bake (Post de-rack)" now → bake (was wrongly → rack).
**4. Auto-populate** target_thickness + dwell_time at WO generation.
Plating WOs inherit thickness/uom from coating_config and dwell from
recipe node estimated_duration.
**5. Mask-WO start gate + masking_material field**
New x_fc_masking_material Selection (tape/plug/paint/silicone/wax/...).
Required to start mask/de-mask WO. Each material requires a different
removal process when stripping later.
**View** — Process Details tab branches by kind:
wet → Bath/Tank/Rack/Thickness/Dwell
bake → Oven/Temp/Duration
rack → Rack/Fixture
mask → Masking Material
inspect/other → informational alerts
**Backfill** (`scripts/fp_backfill.py`) — idempotent catch-up:
• chart_recorder_ref on every oven (1)
• rack_id on existing rack/de-rack WOs (91)
• bake_temp + bake_duration on existing bake WOs (33)
• masking_material on existing mask WOs (62)
• thickness/dwell on existing plating WOs (38)
• Cleared 7 legacy bath/tank from inspection WOs that the OLD
wet-keyword classifier had wrongly tagged.
**Per-step audit** (`scripts/fp_per_step_audit.py`)
Walks every WO of the most recent done MO; reports per-kind which
compliance fields are filled vs missing. Re-runnable for regressions.
**Final verification** on freshly-run MO:
• 0 CRITICAL gaps across all 9 WO steps
• 2 IMPORTANT (dwell_time + rack_id on E-Nickel Plating — both
inherited from recipe node data, not enforcement bugs)
• Classifier correct for all 9 step types
12 negative tests still passing.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
76 lines
2.7 KiB
Python
76 lines
2.7 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
# Part of the Fusion Plating product family.
|
|
|
|
{
|
|
"name": "Fusion Plating — MRP Bridge",
|
|
'version': '19.0.6.7.0',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': 'Bridge Fusion Plating facilities, baths and tanks to Odoo MRP work orders.',
|
|
'description': """
|
|
Fusion Plating — MRP Bridge
|
|
============================
|
|
|
|
Part of the Fusion Plating product family by Nexa Systems Inc.
|
|
|
|
Links Fusion Plating infrastructure (facilities, work centres, baths, tanks)
|
|
to Odoo's native MRP manufacturing orders and work orders so shops can:
|
|
|
|
* Assign a plating facility and FP work centre to an MRP work centre.
|
|
* Tag each work order with the specific bath, tank, rack/fixture, target
|
|
thickness, and dwell time for traceability.
|
|
* Attach a customer specification and facility to a manufacturing order.
|
|
* Create an MRP work centre directly from a Fusion Plating work centre.
|
|
* Link a portal job to a manufacturing order for customer visibility.
|
|
|
|
Copyright (c) 2026 Nexa Systems Inc. All rights reserved.
|
|
""",
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://www.nexasystems.ca',
|
|
'maintainer': 'Nexa Systems Inc.',
|
|
'support': 'support@nexasystems.ca',
|
|
'license': 'OPL-1',
|
|
'price': 0.00,
|
|
'currency': 'CAD',
|
|
'depends': [
|
|
'fusion_plating',
|
|
'fusion_plating_portal',
|
|
'fusion_plating_quality',
|
|
'fusion_plating_logistics',
|
|
'fusion_plating_batch',
|
|
'fusion_plating_shopfloor',
|
|
'fusion_plating_configurator',
|
|
'hr',
|
|
# hr_attendance gives us the standard hr.attendance model
|
|
# (check_in / check_out). fusion_clock builds on the same model
|
|
# so this works whether the shop runs vanilla attendance or the
|
|
# full Fusion Clock T&A. Bringing the dep into the bridge keeps
|
|
# the Manager Desk's "show only clocked-in workers" filter
|
|
# working out of the box.
|
|
'hr_attendance',
|
|
'mrp',
|
|
'mrp_workorder',
|
|
'mrp_account',
|
|
'sale_mrp',
|
|
'account',
|
|
],
|
|
'data': [
|
|
'security/ir.model.access.csv',
|
|
'data/fp_work_role_data.xml',
|
|
'wizard/fp_recipe_config_wizard_views.xml',
|
|
'views/mrp_workcenter_views.xml',
|
|
'views/mrp_workorder_views.xml',
|
|
'views/mrp_production_views.xml',
|
|
'views/sale_order_views.xml',
|
|
'views/fp_quality_hold_views.xml',
|
|
'views/fp_batch_views.xml',
|
|
'views/fp_workorder_priority_views.xml',
|
|
'views/fp_job_consumption_views.xml',
|
|
'views/fp_work_role_views.xml',
|
|
],
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': False,
|
|
}
|