Executive Summary
Dometic’s chiller line suffers from reactive replenishment and mismatches between AS/400 records and actual WIP/lineside stock. Empty‑bin signals and a planning email alias trigger manual searches and cycle‑count walks; space limits push overflow “high,” adding forklift retrieval and ambiguity; daily production boards log material‑caused stops (e.g., a 21‑minute capacitor shortage).
Arda will install a lineside supermarket, two‑bin Kanban, standard tugger routes, and lightweight CSV touchpoints with AS/400 to stabilize flow across ~500 SKUs.
Solution Design
Physical: Right‑sized lineside supermarket; two‑bin Kanban; fixed‑cadence tugger routes.
Digital: Arda captures Kanban events, builds pick lists, timestamps replenishment; CSV export for AS/400 movements—no ERP change.
Objectives & Outcomes
Zero unplanned stockouts on pilot SKUs (steady‑state). ≥40% faster replenishment (trigger scan → full bin). Eliminate manual low‑stock emails for pilot SKUs. Less stockout-related downtime and inventory “hunt” time. Scope
Area: Chiller line (Pompano, FL). SKUs: ~500 high‑velocity items (fittings, harnesses, fasteners, electricals). Flows: Warehouse ⇄ lineside supermarket ⇄ line (two‑bin Kanban). System: Arda software; CSV export for AS/400 updates.
Implementation & Timeline
Design & Data Configuration
On‑Site Setup
Go‑Live & Training
Pilot Run
Evaluation
Sep 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Oct 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Nov 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Dec 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Jan 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Feb 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
Mar 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Apr 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
May 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Design & Data Configuration
KPIs & Measurement
Stockout Frequency: Count per SKU/day at point of use; source = Arda exceptions + supervisor confirmation + daily board. Target: <10 in Weeks 6–8. Replenishment Lead Time: Trigger scan → full bin placed; source = Arda timestamps. Target: ≥40% reduction. Material‑Caused Downtime: Minutes/shift from daily board. Target: ≥60% reduction. Inventory Fidelity: |System − physical| ÷ physical across warehouse/supermarket/line (weekly samples). Target: ≤5% median variance. Manual Low‑Stock Emails: Count to planning alias for pilot SKUs. Target: → 0 by Week 3.
Commercials & Terms
Billing principle: Dometic pays for on‑site labor and software during the pilot. Upon success, 100% of the on‑site fee is credited to a future software payment.
On‑Site Implementation (labor): $20,000
Includes: design, installation, supermarket setup, ~500 Kanban cards, software configuration, training, materials, travel. Credit: 100% of this on‑site fee is applied to Year‑1 software upon meeting success criteria and executing a 12‑month subscription within 30 days of pilot closeout. Pilot Software License: $5,000/month × 2 months = $10,000 (pilot period; non‑creditable).
Scope: up to 500 SKUs, 10 active users, dashboards/KPIs, CSV interface. Continuation: Payment continues at $5,000 per month for the chiller line, unless either party gives written notice. Total Pilot Cash Outlay: $30,000
Success criteria: Weeks 6–8 average achieves: <10 stockouts (pilot SKUs), ≥40% faster replenishment, ≥60% less material‑caused downtime, ≤5% median inventory variance, and elimination of manual low‑stock emails (pilot SKUs).
Payment terms: On‑site + first month software due at kickoff; month‑2 software at 30 days. Credit application to subsequent months of software fees
Data Requirements & IT Touchpoints (Pilot)
Dometic — Chiller Line (Pompano) × Arda
Purpose: Fast pilot launch, clean measurement, minimal IT lift (CSV‑based; AS/400 remains system of record).
One‑Time
Item master (pilot SKUs): part_number, description, UoM, pack_size, typical_supplier, lead_time_days. Locations map: warehouse location codes (e.g., B6/M6), work centers (e.g., chiller WC), lineside/shelf addresses; mark “high” storage. BOM excerpts (top families): note frequent substitutes (fittings/electrical) and allowed alternates. Material Movement Data: Any platform telemetry captured by scanning parts from one location to another Routing/shift data: planned takt, crew counts, line schedule snapshot. User list: operators, handlers, supervisors (role‑based access). Recurring During Pilot
Shop schedule snapshot (weekly): upcoming chiller build plan for min/max tuning. AS/400 transactions extract (daily or 2×/week): item_number, qty, from_location, to_location_or_wc, txn_code, txn_timestamp, user_id. Cycle‑count variance log (weekly): exceptions for pilot SKUs; note WIP finds and rework. Daily production board data (daily): photo or CSV capturing material‑caused downtime minutes. Planning alias count (weekly): number of low‑stock emails for pilot SKUs (item + timestamp only). Interfaces & File Formats
Arda → AS/400 (export for updates): replenishment.csv → item_number, qty, from_location, to_location_or_wc, reason_code (KANBAN), event_timestamp, user_id. AS/400 → Arda (import for analytics): transactions.csv → item_number, qty, from_location, to_location_or_wc, txn_code, txn_timestamp, user_id. Transport: Secure shared drive or SFTP per Dometic preference; browser‑based access (no VPN required). Security & Ownership
Operational data only (no PII). Least‑privilege access by role; Dometic retains system‑of‑record status (AS/400). Pilot data retained for KPI audit and closeout report; purge/retention per Dometic policy.