The first release refuses a year-long finite schedule, an automatic sequencer, maintenance and payroll. It holds one week. The planner’s question on Monday is which line is full, and which job does not fit. That is the screen.
Week, line, the job that does not fit
The week is your shift calendar. The line is a real line you name. The job that does not fit is the one record placed on that week which the capacity will not take. It is an order line or a works order. The name is written in the scope. The screen asks for a decision on that job: hold, move, or split. A red cell with nobody’s name on it is not a decision.
Who moves it
The planning role writes the load. The line lead reads it and accepts the job that does not fit, or sends it back. If both roles quietly slide the same job, the wall lies again. HED Creative asks who updates the wall today. If nobody can say, the screen will not be updated either.
If a file is still the wall, which file deserves a first release is a separate decision: from a spreadsheet. The team that keeps the screen after go-live is written as a software partner. The code does not stay in a personal file.
How it sits next to the book of orders
The load is read from the system where the order or the works order is opened. The screen does not open a second book. When the day changes, the home record changes, or the screen only reads. Two days in two places means two promises to sales. Which record enters the ERP first is chosen separately.
Left out of the first release
A finite schedule for the year, automatic sequencing, maintenance, payroll and the quality file are out. A note may say the job is waiting on quality. The quality screen itself is not this release. The first release holds one week and the lines you name. Every line in the plant is not required. The line you argue about most is enough.
The wall to send
The file or the photo that shows this week’s load, the line names, what you call the job that does not fit, and the two roles. Discovery in Berlin or Ankara writes the decision words from that wall. No wall, and the screen becomes an imaginary schedule.
Write the screen into the web app development brief. The record that enters the ERP does not replace this week: production record.