:00Thu 24 Sep

System

Strict · version 14

Switch to Relaxed…Roll back to version 13…

About Policies

Policies are the rules every rack and station decides by. Each change is a new version: it shows its impact on open work first, and going back is one more version through the same review.

Presets

Strict or Relaxed sets every preset value at once, in one version. A value set for the site, a rack, an item or a station overrides the preset where it applies: the first matching rule wins, from the most specific scope to the site.

What never relaxes

Approvals are off until switched on per action and scope. Fixed safeguards never relax. Publishing needs the policy grant; switching the preset needs it site-wide.

About decision points

Each row is one decision a rack or station makes, with the value in force and where it comes from.

The light language is in Lights & sound. Commissioning qualification runs in Rack setup, at Follow the light. Floor-life evaluation is Later, not in R1.

Strict preset
Built-in
Confirm when sources disagree
Strict
Every conflict blocks until confirmed
Relaxed
Source order decides · the conflict is flagged
Source order: quantity from MES, then the label, then typed; date code from the label, then MES.Decision point DP2
Strict preset
Built-in
Free placement · any free bay
Strict
Guided placement · only the lit bay
Relaxed
Free placement · any free bay
Under guided placement another bay is an unattributed insertion to remove.Decision point DP6
  • Rack SR-03: Free placement · any free bay
  • Rack SR-01: Free placement · any free bay
Strict preset
Built-in
MES, then label, then typed · else Quantity not verified
Strict
Count or type it when neither MES nor the label has one
Relaxed
Receive without a quantity · flagged
Decision point DP7
  • Rack SR-01: MES, then label, then typed · else Quantity not verified
Built-in default

A choice, not a strictness: no preset changes it.

Decision point DP8
Built-in default

A choice, not a strictness: no preset changes it.

Decision point DP8
Built-in default

A choice, not a strictness: no preset changes it.

Decision point DP8
Strict preset
Built-in
A count, or an honest Not counted
Strict
A count is required
Relaxed
Not counted is allowed everywhere
Over-return tolerance is a proposed value.Decision point DP11
  • Station Station SMT-1: Not counted is allowed everywhere
  • Rack SR-01: A count, or an honest Not counted
Strict preset
Built-in
No · Identity not re-confirmed until its next scan
Strict
Yes · a scan is required
Relaxed
No · Identity not re-confirmed until its next scan
Its delays are timers: Alarm delay, Missing delay.Decision point DP12
  • Rack SR-01: No · Identity not re-confirmed until its next scan
Strict presetProposed value
Built-in
Yes, within the binding window at intake stations
Strict
No · scan first, then put in
Relaxed
Yes, within a longer binding window
Decision point DP13
Strict preset
Built-in
Any number · first in, first out
Strict
One per section or side · no automatic Cancel issue
Relaxed
Any number · longer windows
Its windows are timers: placement, pick, settle, undo, bridged gap, abandon.Decision point DP14
Built-in default

A choice, not a strictness: no preset changes it.

Decision point DP18
Strict preset
Built-in
A supervisor, with a reason
Strict
A supervisor, with a reason
Relaxed
Unverified is advisory · an operator’s release is recorded
Item unconfirmed is cleared only by an administrator completing or mapping the item. Enrichment pending never blocks.Decision point DP19
Built-in default

A choice, not a strictness: no preset changes it.

Decision point DP20
  • Item PN-0603-10K: Keep at line
Strict preset
Built-in
Presumed · the supervisor is asked to count
Strict
Unverified (blocks issue) · the supervisor is asked to count
Relaxed
Presumed · the supervisor is asked to count
Decision point DP21
Strict presetProposed value
Built-in
Per board: first and last bay, each merged and size-class boundary
Strict
Every bay of every board
Relaxed
Per board: first and last bay
Qualification is per rack, as a whole, by follow-the-light insertion, occupied racks too; a board that cannot sense goes live in manual operation. An acknowledgement never counts as a lit light.Decision point DP23
  • Rack SR-04: Per board: first and last bay, each merged and size-class boundary
Built-in default

A choice, not a strictness: no preset changes it.

Decision point DP22
Strict preset
Built-in
Pending until the settled read
Strict
Pending until the settled read
Relaxed
Tentative · booked on the offline scan
Decision point DP26
5 decisions with one answer in R1
  • When label formats overlap
    Overlapping formats are refused in every preset, even when readings agree. Order never decides a match.
    Stop and correct the formats
  • Receive a reel whose part neither Janus nor MES knows?
    Provisional Receive and a blocking Item unconfirmed in every preset.
    Receive · Item unconfirmed blocks issue
  • When stock is short for a demand line?
    Waiting for stock and the re-plan arbiter are later.
    Allocate what exists · close the rest short
  • What happens below a part’s minimum stock?
    An alert, per item
  • How does remote demand reach the rack?
    Nothing lights before a pull (Next, a list scan or Start); another collection context waits ready with its bays dark (0060).
    Station pull · one destination per rack side
What each order reads
  • Tails, then first received: Tails first, then the reel received earliest, then the smallest. A reel with no receipt time comes after those with one.
  • Tails, then first stored: Tails first, then the reel put in earliest, then the smallest. A reel with no put-in time comes last.
  • Smallest quantity: The smallest reel first. A reel of unknown quantity comes after every counted one.
  • Reel ID: By reel ID, lowest or highest first. Every reel has one.
  • Date code: By the date code on the label, oldest or newest first, then by reel ID. A reel with no readable date code comes last either way.
  • Customer lot: By customer lot, then the reel put in earliest, then the smallest. A lot that is not 8 characters sorts by its put-in date instead; a reel with no lot comes last.
  • Job and aged date code: Reels bound to the requested job first, then unbound ones; a reel bound to another job is never taken. In each group: date codes older than two years, oldest first, then tails, then the smallest. No binding counts as unbound; no date code as not aged.
  • Shipment: Reels of the requested part first, then by shipment number, then reel ID. A reel with no shipment number comes last.

A reel at or below the tail threshold is a tail; the predecessor counted only below it. Blocked, claimed, out-of-service and not-reporting reels are never taken, whatever the order; the take-out's own rack comes first.

Next take-outs of PN-0603-10K with this order
Next take-outs of PN-0603-10K at SR-01
OrderReelBayQuantityDate codeLot
1R-2026-0036SR-01-T4-L275 000——
2R-2026-0042SR-01-T3-L145 0002614LOT-2614-042
3R-2026-0165SR-01-T3-L025 000——
4R-2026-0166SR-01-T1-L115 000——
5R-2026-0167SR-01-T1-L125 000——
Why? · a decision record, as a supervisor sees it
Decision
Put-in refused · R-2026-0131 at SR-02-T2-L05
Decision point
Where may a reel be put in? (DP6)
Policy
version 14 · Strict
Matched rule
Site · Guided placement · only the lit bay
Reason
Only the lit bay SR-02-T2-L09 completes this put-away.
Candidates
SR-02-T2-L09

Supervisors and administrators see Why? on a refusal. An operator sees the rule in plain words and the permitted way through.

Versions · 14Every change, who published it, and a way back
  1. v14Eszter Szabó · Tue 16 Sep 10:40 · 2 changesIn use
  2. v13Eszter Szabó · Tue 2 Sep 09:12 · 2 changes
  3. v12Eszter Szabó · Mon 1 Sep 11:05 · Strict preset · 3 changes

Publish 0 changes as version 15?

New decisions use it at once; open work keeps its version. Online racks change on their next read; ST-01 gets it when it reconnects.

Changes
ValueNowAfter

Impact preview

    Switch the site to Strict as version 15?

    Every site-scope rule, grant template and approval switch changes at once: every command is decided under the whole old or the whole new preset, never a mix. Rules at a rack, item or station stay.

    No site value changes.

    Access that changes
    ActionStrictStrict
    Report issued; Report missing from Line or Receiving; Consume from Missing; Consume reversal; Adjust quantity by countSupervisor · approvals availableGranted to operators
    Void tentative issueSupervisorOperator at the recovery review; supervisor outside it
    Release a blocking condition (not Item unconfirmed)Supervisor, with a reasonA role the policy grants, with a reason
    Report missing from a bay by decision; Taken to line after an outageSupervisor · approvals availableGranted to operators
    Attestation: “Confirm all — nothing was touched”Supervisor with step-up; never the Unidentified operatorOperator, named sign-in only
    Take in for check; Cancel another person’s receipt or returnSupervisorGranted to operators
    Scrap; RestoreSupervisor · approvals availableSupervisor
    Issue from a Sensing disabled bay by decisionNot allowedSupervisor decision
    Switch a unit, tier or board into manual operationSupervisor with step-upUnchanged
    Approvals (maker–checker)Available per action and scope · offOff

    Impact preview

    • Open work
      Open tasks, removals and the SR-02 outage episode keep version 14. New ones use Strict.
    • Your draft
      Your unpublished edits stay on top of the new preset.

    Switching needs the policy grant and grant management over every affected scope, in this one command. A policy grant on a rack subtree publishes there, never a site-wide preset.

    Roll back to version 13?

    One step: version 15 gets the values of version 13. Version 14 stays in Versions. Open work keeps its version.

    Values that go back
    ValueNowAfter
    Soundwas Preset 2 · audiblenow Preset 1 · soft
    Buzzer forwas 3 snow 5 s

    Alerts

    Faults and blocked work stay here until fixed. Notices can be cleared.

    SR-02 is limited

    Bence Tóth is on itsince 09:41 · 4 h 51 min14:30 installation map v4 drafted by Dávid Horváth under permit · waiting to be applied

    Tier 3, bays 1–16 are Unknown. Blocks 2 take-outs for WO-260714-09 and hides 310 pcs of PN-QFN32-MCU7. The rest of SR-02 works.

    Troubleshoot SR-02Stays until fixed

    Label not recognised

    A Würth Elektronik label matched no code rule.

    Add label rule

    Put-in not finished

    Reel R-2026-0109 is waiting for the sensor at SR-01-T4-L31: finish putting it in, or cancel.

    Continue put-in

    Counter ReelSave is failing

    Owner: line counter vendorsince 13:48

    12 messages waiting. SMT Line 2 counters don't know about reels taken out since 13:48.

    Open Integrations

    Snapshot taken · 14:30

    Verified · off-host copy 14:30. Snapshots every 15 min while Janus is busy.

    Choose working rack

    Scans and bay lights on this station use the working rack. Opening another rack never switches it.

    Racks

    Help

    What the words mean

    Language

    Applies to this station only. Records keep the words they were written in.

    Prototype

    Policies · System

    Preview stateDraft with changes

    View as

    This page

    Purpose
    Presets, one row per decision, an impact preview and versions; tower lights.
    Release
    R1
    First viewport
    1 primary · 1 notice · 3 blocks