EKI Sample Development Planner

1 · Load data

SCHED API

Employee codes

SG API payload (.json)

Machine master (.xlsx)

Merchandiser export (.xlsx)

Work Flow Report (.xlsx) — optional, built from the SG API

Allocation instructions (.xlsx)

STATUS.CSV

INV.CSV

PODET.CSV

Skill register (.json)

Plan overrides (.json)

Bulk load — pick the export folder

or several files at once

Nothing loaded.

2 · Run parameters

Plan run

not run yet

Master efficiency % (people)

Machine efficiency % (knitting)

Person hrs/day

Machine hrs/day

Failure report: commitment locks at (h)

At-risk SGs: compress hand-off days

Paused work (retired option)

Held-date overload: day ends at (h)

After fetching SG data

Frozen window (working days)

Move threshold (days)

SG statuses in scope

Machines per knit task

Machines per knitter — day

… day, covering an absence

Machines per knitter — night

Cheap-finish tier

… at or above % complete

… and at or below (hr) left

Rank inside a tier on

Ancient overdue

… past (days late)

Lead-time target (working days)

Borrow across groups

Portal's assignee

Hand-over when free capacity is× the continuity person’s

Levelling

no plan yet

Machines per knit task: 1 is the standard — a sample knits on one machine, so an 18-hour knit occupies that machine for two days. A knitter may attend several machines at once (set separately), but one SG's knitting is never split across them. Raise it only to model a deliberate split; 0 lets the operation use every machine of its type in the pool. Raw hours = earned hours ÷ efficiency. Efficiency scales the WORK, not the resource: a person still has their hours per day and a machine still runs its hours per day. Completed operations are never scheduled; each SG resumes at the operation after the highest completed or started one.

Working…