Files

gsinghpal f340c87b6a feat(bridge_mrp): shop-role auto-routing + tablet worker mode (CHUNK 4/4)

Completes the worker-access story. Handoffs now route themselves.

New model fp.work.role with 8 seeded defaults (noupdate so shops can
rename/prune):
  masking · racking · plating_op · demask · oven · derack ·
  inspection · rework

Each one has a code, icon, description, sequence, active flag.
Config menu: Configuration → Shop Roles (manager-only).

Field additions:
  hr.employee.x_fc_work_role_ids (Many2many) — tag workers with the
    roles they perform. One-person shop: one employee, every role.
    Specialised shop: one role per employee. Cross-trained: multiple.
  fusion.plating.process.node.x_fc_work_role_id (Many2one) — tag
    each recipe operation with the role that performs it.
  mrp.workorder.x_fc_work_role_id (Many2one) — copied from the recipe
    operation on WO generation.

Auto-assignment on WO generation:
  _generate_workorders_from_recipe() now copies the operation's role
  onto the WO, then calls _fp_pick_worker_for_role() which picks the
  least-loaded employee (active WO count) with that role. WO lands in
  their Tablet "My Queue" the moment the MO is confirmed. No manual
  routing needed for the common case.

Tablet Station — worker mode:
  /fp/shopfloor/tablet_overview now filters to WOs where
  x_fc_assigned_user_id == env.user when the field is populated.
  KPIs (WOs Ready / In Progress) reflect the logged-in worker's load,
  not shop-wide totals. "My Queue" rows carry wo_state + can_start +
  can_finish so inline Start/Finish buttons appear.
  New JS handlers onStartWo / onFinishWo call /fp/shopfloor/start_wo
  and /fp/shopfloor/stop_wo (finish=true). One-tap progression.

Views:
  hr.employee form gets a "Shop Roles" notebook page with many2many_tags.
  Process node form gets x_fc_work_role_id inline after work_center_id.
  Work Order form shows role + assigned worker.

Smoke-tested end-to-end on WH/MO/00010:
  Masking      → Administrator (masking role)
  Racking      → Administrator (racking role)
  E-Nickel     → Andrew (plating_op, least-loaded tiebreaker)
  Demask       → Administrator (masking)
  Oven bake    → Andrew (oven)
  Derack       → Administrator (racking fallback)
  Post-plate QA → Administrator (inspection)

80 existing WOs backfilled with role + worker via name-match.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-17 20:08:23 -04:00

controllers

feat(bridge_mrp): shop-role auto-routing + tablet worker mode (CHUNK 4/4)

2026-04-17 20:08:23 -04:00

data

folder rename

2026-04-16 20:53:53 -04:00

models

folder rename

2026-04-16 20:53:53 -04:00

security

folder rename

2026-04-16 20:53:53 -04:00

static/src

feat(bridge_mrp): shop-role auto-routing + tablet worker mode (CHUNK 4/4)

2026-04-17 20:08:23 -04:00

views

feat(shopfloor): Manager Desk — assign workers, swap tanks, take over (CHUNK 2/4)

2026-04-17 20:03:01 -04:00

__init__.py

folder rename

2026-04-16 20:53:53 -04:00

__manifest__.py

feat(shopfloor): Manager Desk — assign workers, swap tanks, take over (CHUNK 2/4)

2026-04-17 20:03:01 -04:00

README.md

folder rename

2026-04-16 20:53:53 -04:00

README.md

Fusion Plating — Shop Floor

Tablet / operator ergonomics layer for the fusion_plating core.

What this module adds

Feature	Model
Tablet station registration	`fusion.plating.shopfloor.station`
Bake oven master + chart recorder ref	`fusion.plating.bake.oven`
Hydrogen embrittlement bake-window enforcer	`fusion.plating.bake.window`
First-piece inspection gate	`fusion.plating.first.piece.gate`
Operator next-up queue (transient)	`fusion.plating.operator.queue`

Bake-window enforcer

When a high-strength-steel part exits the plating tank, a clock starts. Customer specification dictates the window (typically 1-4 hours) inside which the relief bake must begin. Missing the window requires scrap or rework — there is no retroactive fix.

The module models this as a first-class entity with:

plate_exit_time — clock start
window_hours — customer spec
bake_required_by — computed deadline
state — awaiting_bake -> bake_in_progress -> baked, with missed_window / scrapped exit paths
A 5-minute cron that flips records past their deadline to missed_window automatically
A kanban board grouped by state with theme-aware status colours

Tablet client

A backend OWL component (Odoo 19 conventions) registered as the fp_shopfloor_tablet client action. It hosts:

QR scan input (wedge scanner or on-screen keyboard friendly)
Live tank / bath / job preview cards
One-tap Start Bake / End Bake buttons
Live operator next-up queue

JSON-RPC endpoints (Odoo 19 type='jsonrpc'):

POST /fp/shopfloor/scan
POST /fp/shopfloor/log_chemistry
POST /fp/shopfloor/start_bake
POST /fp/shopfloor/end_bake
POST /fp/shopfloor/queue

QR code conventions

Prefix	Resolves to
`FP-TANK:<code>`	`fusion.plating.tank`
`FP-BATH:<name>`	`fusion.plating.bath`
`FP-STATION:<code>`	`fusion.plating.shopfloor.station`
`FP-JOB:<name>`	`fusion.plating.bake.window`
`FP-OVEN:<code>`	`fusion.plating.bake.oven`

Security

Reuses the four core Fusion Plating groups (operator, supervisor, manager, admin) defined in fusion_plating. No new groups, no new privilege block. ACLs are graded operator (read/write logs), supervisor (create), manager (full).

Theme

All styling is theme-aware: CSS custom properties + color-mix() against Bootstrap / Odoo tokens. No hex codes, no media queries — works in light and dark mode out of the box.

Install / update

docker exec odoo-dev-app odoo -d fusion-dev -u fusion_plating_shopfloor --stop-after-init