feat(promote-customer-spec): Phase A — recipe + spec foundation

- Add fp.recipe.thickness model (replaces fp.coating.thickness, scoped to recipe root)
- Add spec metadata + bake-relief fields to fusion.plating.process.node (recipe root):
  phosphorus_level, thickness_min/max/uom, thickness_option_ids,
  requires_bake_relief + bake_window_hours/temperature/duration
- Add recipe_ids M2M + print_on_cert to fusion.plating.customer.spec
- Add applicable_spec_ids reverse M2M as inherit in fusion_plating_quality
  (avoids circular dep — core can't reference customer.spec which lives in quality)
- Surface new fields on recipe form ("Specification & Bake" notebook page)
- Surface recipe linkage on customer spec form

Pure additive. Foundation for Phases B-E.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
gsinghpal
2026-05-15 00:50:17 -04:00
parent 13fd0712d9
commit 406cac1362
13 changed files with 266 additions and 2 deletions

View File

@@ -5,7 +5,7 @@
{
'name': 'Fusion Plating',
'version': '19.0.18.15.16',
'version': '19.0.19.0.0',
'category': 'Manufacturing/Plating',
'summary': 'Core plating / metal finishing ERP: facilities, processes, tanks, baths, jobs, operators.',
'description': """
@@ -99,6 +99,7 @@ Copyright (c) 2026 Nexa Systems Inc. All rights reserved.
'views/fp_facility_views.xml',
'views/fp_bath_views.xml',
'views/fp_process_node_views.xml',
'views/fp_recipe_thickness_views.xml',
# Sub 14b — fp.step.kind catalog. MUST load before
# fp_step_template_data.xml (templates reference kinds via
# kind_id) AND before fp_step_template_views.xml (the form

View File

@@ -18,6 +18,7 @@ from . import fp_bath_log_line
from . import fp_bath_parameter
from . import fp_bath_replenishment_rule
from . import fp_process_node
from . import fp_recipe_thickness
from . import fp_rack
from . import fp_job
from . import fp_job_step

View File

@@ -336,6 +336,68 @@ class FpProcessNode(models.Model):
# NB. `pricing_rule_ids` lives in fusion_plating_configurator
# (added there so this core module doesn't depend on the configurator).
# ---- Spec-derived metadata (recipe-root only — Promote Customer Spec) ----
# These were on fp.coating.config (since retired). They describe the
# PROCESS the recipe runs, not the customer-facing specification —
# specs live on fusion.plating.customer.spec.
phosphorus_level = fields.Selection(
[('low_phos', 'Low Phosphorus (2-5%)'),
('mid_phos', 'Mid Phosphorus (6-9%)'),
('high_phos', 'High Phosphorus (10-13%)'),
('na', 'N/A')],
string='Phosphorus Level',
default='na',
help='EN-specific. Set to N/A for non-EN processes (chrome, '
'anodize, black oxide). Drives certificate annotation and '
'hydrogen-embrittlement risk assessment for bake-relief.',
)
thickness_min = fields.Float(string='Min Thickness', digits=(10, 4))
thickness_max = fields.Float(string='Max Thickness', digits=(10, 4))
thickness_uom = fields.Selection(
[('mils', 'mils'), ('microns', 'microns'), ('inches', 'inches')],
string='Thickness UoM', default='mils',
)
thickness_option_ids = fields.One2many(
'fp.recipe.thickness',
'recipe_id',
string='Thickness Options',
help='Discrete thickness values offered to the estimator on the '
'order line for jobs running this recipe.',
)
# ---- Bake relief — AMS 2759/9 hydrogen embrittlement (recipe root) ----
requires_bake_relief = fields.Boolean(
string='Requires Bake Relief',
help='Hydrogen embrittlement relief bake required (high-strength '
'steel ≥ HRC 31 in conjunction with this chemistry). When '
'set, finishing the job auto-creates a bake-window record '
'and blocks shipment until bake is complete.',
)
bake_window_hours = fields.Float(
string='Bake Window (hours)', default=4.0,
help='Maximum time between plate exit and bake start. Typical 4h '
'per AMS 2759/9.',
)
bake_temperature = fields.Float(
string='Bake Temperature', default=375.0,
help='Relief bake temperature. Default 375 (°F per AMS 2759/9 for '
'steel ≥ HRC 40).',
)
bake_temperature_uom = fields.Selection(
[('F', '°F'), ('C', '°C')],
string='Bake Temp Unit',
default='F',
)
bake_duration_hours = fields.Float(
string='Bake Duration (hours)', default=23.0,
help='Minimum bake hold time at temperature. Typical 23h.',
)
# NB. `applicable_spec_ids` (reverse of customer.spec.recipe_ids) is
# defined as an inherit in fusion_plating_quality (the module that
# owns fusion.plating.customer.spec). Core can't reference it
# directly without a dependency inversion.
# ---- Computed fields -----------------------------------------------------
display_name = fields.Char(

View File

@@ -0,0 +1,54 @@
# -*- coding: utf-8 -*-
# Copyright 2026 Nexa Systems Inc.
# License OPL-1 (Odoo Proprietary License v1.0)
# Part of the Fusion Plating product family.
from odoo import api, fields, models
class FpRecipeThickness(models.Model):
"""Discrete thickness option offered for a recipe.
Replaces fp.coating.thickness. The thickness picker on the SO line
is scoped to the chosen recipe, so the operator only sees values
that match what the recipe actually produces.
"""
_name = 'fp.recipe.thickness'
_description = 'Fusion Plating — Recipe Thickness Option'
_order = 'recipe_id, sequence, value'
recipe_id = fields.Many2one(
'fusion.plating.process.node',
string='Recipe',
required=True,
ondelete='cascade',
domain="[('node_type', '=', 'recipe'), ('parent_id', '=', False)]",
)
sequence = fields.Integer(default=10)
value = fields.Float(
string='Thickness',
required=True,
digits=(10, 4),
)
uom = fields.Selection(
[('mils', 'mils'), ('microns', 'microns'), ('inches', 'inches')],
string='UoM',
required=True,
default='mils',
)
label = fields.Char(
string='Display Label',
compute='_compute_label',
store=True,
help='Auto-formatted "0.0005 mils" string for the picker dropdown.',
)
note = fields.Char(string='Note')
active = fields.Boolean(default=True)
@api.depends('value', 'uom')
def _compute_label(self):
for rec in self:
rec.label = f'{rec.value:g} {rec.uom}' if rec.value else ''
def name_get(self):
return [(rec.id, rec.label or '?') for rec in self]

View File

@@ -94,3 +94,6 @@ access_fp_job_step_move_manager,fp.job.step.move.manager,model_fp_job_step_move,
access_fp_job_step_move_input_value_operator,fp.job.step.move.input.value.operator,model_fp_job_step_move_input_value,group_fusion_plating_operator,1,1,1,0
access_fp_job_step_move_input_value_supervisor,fp.job.step.move.input.value.supervisor,model_fp_job_step_move_input_value,group_fusion_plating_supervisor,1,1,1,0
access_fp_job_step_move_input_value_manager,fp.job.step.move.input.value.manager,model_fp_job_step_move_input_value,group_fusion_plating_manager,1,1,1,1
access_fp_recipe_thickness_user,fp.recipe.thickness.user,model_fp_recipe_thickness,base.group_user,1,0,0,0
access_fp_recipe_thickness_supervisor,fp.recipe.thickness.supervisor,model_fp_recipe_thickness,group_fusion_plating_supervisor,1,1,1,0
access_fp_recipe_thickness_manager,fp.recipe.thickness.manager,model_fp_recipe_thickness,group_fusion_plating_manager,1,1,1,1
1 id name model_id:id group_id:id perm_read perm_write perm_create perm_unlink
94 access_fp_job_step_move_input_value_operator fp.job.step.move.input.value.operator model_fp_job_step_move_input_value group_fusion_plating_operator 1 1 1 0
95 access_fp_job_step_move_input_value_supervisor fp.job.step.move.input.value.supervisor model_fp_job_step_move_input_value group_fusion_plating_supervisor 1 1 1 0
96 access_fp_job_step_move_input_value_manager fp.job.step.move.input.value.manager model_fp_job_step_move_input_value group_fusion_plating_manager 1 1 1 1
97 access_fp_recipe_thickness_user fp.recipe.thickness.user model_fp_recipe_thickness base.group_user 1 0 0 0
98 access_fp_recipe_thickness_supervisor fp.recipe.thickness.supervisor model_fp_recipe_thickness group_fusion_plating_supervisor 1 1 1 0
99 access_fp_recipe_thickness_manager fp.recipe.thickness.manager model_fp_recipe_thickness group_fusion_plating_manager 1 1 1 1

View File

@@ -226,6 +226,44 @@
<page string="Notes" name="notes">
<field name="notes" placeholder="Internal notes..."/>
</page>
<page string="Specification &amp; Bake"
name="spec_metadata"
invisible="node_type != 'recipe' or parent_id">
<group>
<group string="Spec Metadata">
<field name="phosphorus_level"/>
<field name="thickness_min"/>
<field name="thickness_max"/>
<field name="thickness_uom"/>
</group>
<group string="Bake Relief (AMS 2759/9)">
<field name="requires_bake_relief"/>
<field name="bake_window_hours"
invisible="not requires_bake_relief"/>
<field name="bake_temperature"
invisible="not requires_bake_relief"/>
<field name="bake_temperature_uom"
invisible="not requires_bake_relief"/>
<field name="bake_duration_hours"
invisible="not requires_bake_relief"/>
</group>
</group>
<group string="Thickness Options">
<field name="thickness_option_ids" nolabel="1">
<list editable="bottom">
<field name="sequence" widget="handle"/>
<field name="value"/>
<field name="uom"/>
<field name="label" readonly="1"/>
<field name="note" optional="hide"/>
<field name="active" optional="hide"/>
</list>
</field>
</group>
<!-- Applicable Specifications group is added
by fusion_plating_quality via an inherit
view (the field lives there too). -->
</page>
</notebook>
</sheet>
<chatter/>

View File

@@ -0,0 +1,25 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright 2026 Nexa Systems Inc.
License OPL-1 (Odoo Proprietary License v1.0)
Part of the Fusion Plating product family.
-->
<odoo>
<record id="view_fp_recipe_thickness_list" model="ir.ui.view">
<field name="name">fp.recipe.thickness.list</field>
<field name="model">fp.recipe.thickness</field>
<field name="arch" type="xml">
<list string="Thickness Options" decoration-muted="not active" editable="bottom">
<field name="sequence" widget="handle"/>
<field name="recipe_id"/>
<field name="value"/>
<field name="uom"/>
<field name="label" string="Display"/>
<field name="note" optional="hide"/>
<field name="active" optional="hide"/>
</list>
</field>
</record>
</odoo>

View File

@@ -5,7 +5,7 @@
{
'name': 'Fusion Plating — Quality (QMS)',
'version': '19.0.4.14.0',
'version': '19.0.5.0.0',
'category': 'Manufacturing/Plating',
'summary': 'Native QMS for plating shops: NCR, CAPA, calibration, AVL, FAIR, '
'internal audits, customer specs, document control. CE + EE compatible.',
@@ -90,6 +90,7 @@ Copyright (c) 2026 Nexa Systems Inc. All rights reserved.
'views/fp_calibration_views.xml',
'views/fp_avl_views.xml',
'views/fp_customer_spec_views.xml',
'views/fp_process_node_inherit_views.xml',
'views/fp_audit_views.xml',
'views/fp_fair_views.xml',
'views/fp_doc_control_views.xml',

View File

@@ -9,6 +9,7 @@ from . import fp_calibration
from . import fp_calibration_event
from . import fp_avl
from . import fp_customer_spec
from . import fp_process_node_inherit
from . import fp_audit
from . import fp_fair
from . import fp_doc_control

View File

@@ -74,6 +74,22 @@ class FpCustomerSpec(models.Model):
notes = fields.Html(
string='Notes',
)
recipe_ids = fields.Many2many(
'fusion.plating.process.node',
'fp_customer_spec_recipe_rel',
'spec_id', 'recipe_id',
domain="[('node_type', '=', 'recipe'), ('parent_id', '=', False)]",
string='Applicable Recipes',
help='Recipes that can produce work to this specification. '
'Many-to-many — one spec can cover multiple processes; '
'one recipe can satisfy multiple specs.',
)
print_on_cert = fields.Boolean(
string='Print on Certificate',
default=True,
help="When enabled, this spec's code+revision appear on the CoC "
'when the spec is selected on the SO line.',
)
company_id = fields.Many2one(
'res.company',
string='Company',

View File

@@ -0,0 +1,26 @@
# -*- coding: utf-8 -*-
# Copyright 2026 Nexa Systems Inc.
# License OPL-1 (Odoo Proprietary License v1.0)
# Part of the Fusion Plating product family.
from odoo import fields, models
class FusionPlatingProcessNode(models.Model):
"""Add the reverse M2M from recipe → applicable specifications.
The forward M2M lives on fusion.plating.customer.spec.recipe_ids.
Defined here (in the quality module) because customer.spec is owned
by quality and core can't reference it without a circular dep.
"""
_inherit = 'fusion.plating.process.node'
applicable_spec_ids = fields.Many2many(
'fusion.plating.customer.spec',
'fp_customer_spec_recipe_rel',
'recipe_id', 'spec_id',
string='Applicable Specifications',
help='Customer / industry specifications this recipe is qualified '
'to satisfy. Set on the spec record; mirrored here for '
'navigation.',
)

View File

@@ -50,6 +50,13 @@
<group string="Applicable Processes" name="applicable_processes">
<field name="process_type_ids" widget="many2many_tags" nolabel="1"/>
</group>
<group string="Applicable Recipes" name="applicable_recipes">
<field name="recipe_ids" widget="many2many_tags" nolabel="1"
options="{'no_create_edit': True}"/>
</group>
<group>
<field name="print_on_cert"/>
</group>
<notebook>
<page string="Notes">
<field name="notes"/>

View File

@@ -0,0 +1,29 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright 2026 Nexa Systems Inc.
License OPL-1 (Odoo Proprietary License v1.0)
Part of the Fusion Plating product family.
Adds the "Applicable Specifications" group to the recipe form
(defined in core under the "Specification & Bake" notebook page).
Lives here because the field applicable_spec_ids is added by an
inherit in this module.
-->
<odoo>
<record id="view_fp_process_node_form_quality_inherit" model="ir.ui.view">
<field name="name">fusion.plating.process.node.form.quality.inherit</field>
<field name="model">fusion.plating.process.node</field>
<field name="inherit_id" ref="fusion_plating.view_fp_process_node_form"/>
<field name="arch" type="xml">
<xpath expr="//page[@name='spec_metadata']" position="inside">
<group string="Applicable Specifications">
<field name="applicable_spec_ids" nolabel="1"
widget="many2many_tags"
options="{'no_create': True}"/>
</group>
</xpath>
</field>
</record>
</odoo>