Find your job below and it will show you the screens you use and the buttons you press. Or ask a question in the box - it answers from the live system where it can. If what you want is the shape of the whole thing - every place an order can be and what moves it - open the order flow.
Try a how-to question, or ask about stock. It only answers from the real system - if it does not know, it says so rather than guess.
Press the one that matches what you do. It takes you straight to your part and skips everyone else's.
Everything in the next section applies to everybody, whatever your job.
There are no passwords in PhoenixOS, and since 11 August there is one way in for everybody - the floor, the office, every screen. You type your 3-digit employee number and you are in.
It was in the email PhoenixOS sent you, with a button that opens the sign-in. If you cannot find it, ask Michael Holt.
It is the only thing needed to sign in as you, and every tap you make at a machine is recorded under your name. Treat it the way you would treat a password.
A tablet that worked yesterday afternoon will want your number again this morning. That is normal and nothing is wrong. Office sign-ins last 30 days on that device.
If your station screen jumps to Sign in by itself, sign in again and you come straight back to the same screen. Nothing you already tapped is lost.
Every screen you are signed in to shows your name and a LOG OUT button in the top bar. On a shared tablet that name is how the next person knows the screen is still yours.
Press LOG OUT at the end of your shift. It ends your session properly, so nobody can pick the tablet up and act as you.
If the name at the top is not yours, the last person did not log out. Press it and sign in as yourself before you touch anything. Everything you do is recorded against whoever is signed in.
The wall TV and the shared truck tablet show no name and no LOG OUT. They are screens, not people.
Everyone has a level from 1 to 4, and it decides which boards you can open. Your launchpad only shows the boards you can actually use, so if you see four tiles and someone else sees eleven, that is correct and nothing is hidden from you by mistake.
| Level | Boards you can open | What you can change |
|---|---|---|
| 1 | My Station, TV Wallboard, Deliveries, Dispatch | Work jobs at your machine, and count deliveries in at Goods In. |
| 2 | the above + Factory Operations | the above + confirm a delivery as delivered, with who signed for it. |
| 3 | the above + Stock, Projects, and the Console (read it, not change it) | the above + stock triggers and silos, and machine queues on Factory Operations. |
| 4 | every board, plus Analytics, Prices and the Flow Library | Everything, including Process Order, purchasing and staff. Console changes stay with the listed staff only. |
If you open a board above your level it says NOT AUTHORISED and stays put. Signing in again will not help. Ask David or Mick if you need it.
A change to your level takes effect the next time you sign in.
The launchpad is the grid of large buttons, one per board. Press the small star on any board to make it the screen you land on when you sign in.
Most boards carry a row of counts across the top - Open Jobs, New Orders, Awaiting Board, In Production, In Deliveries, Current SOH and DIFOT. They refresh by themselves and each one is a shortcut: press it to jump to that list.
The Home in the row of counts always goes to the launchpad.
The Home in the menu strip goes to the Order Book on some boards and the launchpad on others. If Home does not go where you expected, that is why.
You are looking at practice data, not the factory, and nothing you do is
recorded. Look at the web address: if it ends in ?demo or ?live,
delete that part and reload.
It follows you - every link keeps you in practice mode until you edit the address. One shared or bookmarked link can keep a whole shift on it.
If you see Feed stopped or Feed failing, the screens are showing the last information that arrived and nothing is updating. If you see something offline, one part of the system is down but orders and deliveries are still coming through.
Either way, what is on screen may be out of date. Tell the office. Do not assume a job has gone because it is not there.
Your session ran out. Sign in again - nothing is lost. On the floor this normally happens first thing in the morning, because the sign-in ends at midnight.
You are signed in, but that board is not part of your level. Signing in again will not help. Ask David or Mick.
It almost certainly has an open query, which moves it out of New Orders and onto the Order Book's Queries tab until the question is answered. Look there first.
In Production and In Deliveries overlap on purpose. One order, two views. It is not a duplicate.
Tell someone rather than pressing more buttons. Most things the office can put right - a removed order restored, a job moved back to a machine, a delivery moved to another run.
Two things cannot be undone from any screen: finishing an operation on the wrong job, and marking the wrong order delivered. Both are fixable, but a person has to do it, so say so straight away.
This is for you if you run a machine - die cutting, stripping, laminating, Solarco, or any other machine on the floor - and the jobs you work on come to you in a queue.
You have your own 3-digit employee number. Nobody else has it, and it is yours for as long as you work here. You never type an email address into the tablet.
You land straight on your station screen. That is your screen for the shift - you do not have to find it. There is no password and no code to wait for.
It is the only thing needed to sign in as you, and every tap you make is recorded under your name. If you think somebody else has been using it, tell Michael Holt.
Your sign-in lasts until midnight. Next morning the tablet will ask for your number again, and that is normal, not a fault.
Along the top of the station screen is a strip of machine names, each with a number next to it - that number is how many jobs are queued there. Slide the strip sideways to see them all. Tap your machine. It turns yellow, and the list underneath becomes that machine's queue.
The tablet remembers your choice. Next time you sign in on the same tablet, it comes back on the same machine. Some tablets are fixed to one machine and will tell you so in a blue line under the strip.
Every job in the queue is one card. From the top of the card down:
| What you see | What it means |
|---|---|
| Job number, in blue | The job's number. This is the number you quote to anyone about this job. |
| A short code beside it | The customer's short code. |
| PRIORITY | The office has pinned this job to the top. Do it first. |
| REWORK (sometimes with a number) | This card is rework, not the original job. The number says which rework it is. |
| #3 in queue (top right) | Where this job sits in the queue. The office sets that order deliberately - work down the list. |
| The description line | The item you are making. |
| Qty | The order quantity. |
| Something like 3/7 - 43% | How far through its route the job is: three of seven operations done. -/- means the route is not known yet - see the note below. |
| Due | The production due date - when this job needs to be finished, not when it ships. |
Under that sit the reference chips: small grey boxes for the drawing, artwork, knife, pallet and any notes. Where a chip is blue, tap it and the document opens in a new tab. Check the knife and the drawing before you start setup - that is what the chips are there for.
Its route is not readable yet, so the tablet will not let you tap anything on it. That is deliberate: a tap that cannot say which operation it finished is worse than no tap. Tell your supervisor and move to the next job.
The card is split into two panels: Setup on one side, Manufacturing on the other. The next tap you need is always the yellow one. The others stay on the screen but go quiet.
The state line in the middle of the card tells you where you are: Waiting to start setup, then Setup in progress, then Manufacturing in progress. If the job is paused it says Paused setup or Paused manufacturing with the reason.
After a pause the yellow button is Resume setup or Resume manufacturing - whichever phase you paused. It always puts you back in the same phase you stopped in, never the other one.
Press the one you are up to. If you never pressed Start setup, the operation still records as finished - Phoenix simply says honestly that it does not know how long the setup took. It will not invent a number, and it will not stop you working. Tell your supervisor so the figure can be explained later.
Open QA check on the card. Three things to fill in:
Then press Record QA.
Record the fail honestly. Phoenix stops the clock, holds the job at your machine and puts it on the office board straight away. You cannot restart it yourself and you are not meant to - the hold is lifted by a manager, who has to give a reason. Do not carry on running product you have just failed.
Open Quantity / waste. This is available while you are running, which is when the output exists.
Press Record quantity. You can record as many times as you like through a run - a few entries across a shift is normal and more useful than one guess at the end.
The running totals appear at the bottom of the card: Good, Waste, Rework, and your Latest QA.
Pause whenever the work genuinely stops. A pause keeps the stopped time out of your machine's figures, so pausing protects you - an unpaused lunch break makes your machine look slow.
Open Pause, pick the reason and press Pause this phase. The reasons are:
When you are going again, press the yellow Resume button on the card.
If something is wrong but you are not stopping the job for it, record it. Open Report issue:
Press Record issue. Your last few issues stay listed in amber at the bottom of the card, so the next person on the machine can see them.
Recording a safety issue is not the same as reporting it. If anything is unsafe, stop, make it safe and tell your supervisor in person. Then record it.
When work has to be done again at your machine, open Create rework job:
Press Create rework at this process.
It creates a new job for the one operation, at your machine, and puts it in your queue. It carries a REWORK badge and the same job number so it stays tied to the customer's order. It does not rewind the original job and it does not undo anything you have already recorded. Rework is extra work, and Phoenix records it as extra work.
You will see up to three separate numbers, and they are never added together, because they are three different problems:
| Number | What it is |
|---|---|
| Setup total | Time spent setting up. A long setup is a changeover problem. |
| Run total | Time spent running. A long run means the expected rate is wrong. |
| Waiting between machines (amber) | Time the job sat in a queue, not at any machine. That belongs to the schedule, not to you. |
While you are working you also see a live counter - Setup 25m on the clock, or Run 1h 10m on the clock. "On the clock" means plain wall clock: it ticks, and it keeps ticking through lunch and overnight. The settled totals underneath are working minutes off the shift calendar, which is why a job left overnight shows a big number on the clock and a sensible total the next day. Both are true. They are measuring different things.
Press a button twice, or press it again because the tablet felt slow, and Phoenix records it once. Every button goes grey for the moment it takes to save, and each tap carries a marker so a repeat is recognised as the same tap and ignored. You will never create two starts, two finishes or two counts by tapping twice.
Nothing on this screen can be taken back - not a tap, not a QA result, not a quantity, not a rework job. If you record something wrong, or on the wrong job, tell your supervisor straight away. It can be corrected properly, with a record of who corrected it and why. Do not try to cancel it out with another entry.
If the tablet loses the wi-fi it will say offline at the top right, and any tap will tell you the action was not recorded. Not saved, not queued, not sent later - nothing happened. Get the wi-fi back and do the tap again. Never walk away from a tap that did not confirm.
A confirmed action shows a short green line on the card - "Setup started", "Quantity recorded", and so on. Green means saved. Red means it did not happen.
Your name is at the top of the screen with LOG OUT next to it. Press it at the end of your shift, or any time you walk away from a shared tablet.
Every tap is filed against the person signed in. If you leave yourself signed in and someone else uses the tablet, their work goes down as yours. Log out.
This is for you if you work at the hand benches - assembling, inserting, gluing, packing by hand rather than running a machine.
Your screen is the same station screen the machine operators use, and everything in the operator section above applies to you exactly as written: signing in with your 3-digit number, reading a job card, the three taps, QA, quantity and waste, pausing, issues, rework, no undo, offline, and logging out. Read that section - this one only covers what is different.
On the machine strip along the top, your section is Hand Work. Tap it and you get the hand bench queue, in the order the office has set it, with pinned PRIORITY jobs first.
Hand Work is one queue for the whole bench area. Several of you may be working out of the same list at once, so before you tap Start setup on a card, make sure nobody else has already picked it up - the card will already say Setup in progress or Manufacturing in progress, with the name of whoever started it.
Otherwise the taps mean the same as they do on a machine. Start setup is getting the bench ready - stock, tooling, sample, first-off. Setup complete is when you are actually producing. Finish operation is when the operation is done and the job moves on.
The leading hand is service level 2, one above the bench, and gets one extra thing: a Factory Ops link in the bar at the top of the screen. That opens Factory Operations - every machine queue in the factory on one board, not just Hand Work. Use it to see what is coming toward the bench and what the bench is holding up.
Everything else is identical. Level 2 does not change what you may record on a job, and it does not let you lift a quality hold.
This is for you if a truck has pulled up and you are counting what came off it. Any operator can do this - you do not need a special sign-in.
Sign in as normal, then slide the machine strip at the top all the way to the right. The last chip is Goods In, with a number showing how many deliveries are outstanding. Tap it.
Each delivery still to be counted is one card. When you have finished, tap your machine back on the strip and you are back at your queue.
| What you see | What it means |
|---|---|
| The PO number, in blue | The purchase order this delivery is against. Check it matches the supplier's paperwork. |
| The supplier name | Who it is from. |
| exp and a date | The date the delivery was expected. Cards are listed oldest expected first. |
| Exp: a number, or not set | The quantity the purchase order says is coming. |
| Dock: a number, or not counted | What the dock has actually counted. Blank until you enter it. |
The number on the delivery docket is what the supplier says they sent. Your number is what is on the dock. They are not the same fact, and Phoenix wants yours. Count the pallets, count the sheets, and type what you counted.
| Button | Press it when |
|---|---|
| All here | The order is complete. Nothing further is coming for this PO. |
| Partial - more coming | Part of the order arrived. The PO stays open for the balance and the card stays on your screen. |
Phoenix does not work this out from your numbers. It is your call, and you make it by choosing the button.
All here does not just tick off a delivery. It releases every job that was waiting on that board straight into production. Operators start setting up on material you have just said is here. If it is not all here - if one pallet is still on the truck, or a bundle is short - press Partial - more coming. There is no undo on either button.
Check the number on the card against the number on the supplier's paperwork before you count anything - a delivery counted against the wrong order releases the wrong jobs.
You will see purchase order numbers in three shapes, and all three are ours. PO8534 is an older one. PSP000142 is a Phoenix one raised before job numbers were switched on. 001260011 is the shape from now on: it is the JOB number 00126001 with one more digit on the end saying which purchase order it is on that job - so 001260012 is the second board order for the same job. Nine digits, and the first eight tell you the job at a glance.
If your count differs from the quantity on the purchase order, the card turns red and says so. That is the system working. The office picks it up and sorts out which is right.
A mismatch is information the business needs - a short delivery, a wrong quantity on an order, or a miscount that gets checked. Changing your number to match the paperwork destroys the only independent count anyone has, and Phoenix then pays for stock that never arrived. Enter what you counted. Let it flag.
Half-typed counts survive the screen refreshing, so you will not lose a number you are partway through entering.
This is for you if you load the truck and run the deliveries - Andrew, this section is yours.
Start your day at a screen and sign in with your own employee number. The screen is headed Sign in. Type your number and press Sign in. That is the whole thing.
You sign in as you, not as "the truck". Every drop you confirm is recorded against your name, which is what makes the record worth having when the office is asked three weeks later who delivered what.
The shared tablet is there so you can see the run while you are out. It is not a sign-in. Sign in as yourself on the Driver page to confirm a drop, and sign out again - do not sign yourself in on the shared tablet and leave it in the cab.
Open Deliveries. The board is the working week, Monday to Friday, one column per day, with today's column marked. Each column heading says which run leaves that day - Local on Mon and Fri, Sydney on Tue and Thu, Newcastle on Wed - and how many drops are on it.
| Column | What it is |
|---|---|
| Mon to Fri | The five days of the week you are looking at. A drop sits in the day its run leaves. |
| A greyed day | A public holiday. The heading says which day that run has moved to. |
| Unassigned | Drops with no run day yet - usually a suburb the map does not know. They are never guessed onto a truck. The office sorts them. |
The arrows either side of the week name step to last week and next week; press the week name itself to come back to this week. Along the top, All runs and Truck only switch between the whole picture and just what goes on a truck. Beside those are filter tabs - Complete List, Next 7 Days, Unassigned and one per zone - each with its own count.
They never go on your truck, so they are not on a truck timetable. You will find them on Dispatch, each on its own tab.
A card with a green left edge has already been confirmed delivered.
You have your own page for this. Open Driver, signed in as yourself. It lists today's truck drops, biggest thing on the screen first, and each one has a Confirm delivered button. The office confirms from Dispatch the same way.
Nothing is written until you have given a name. The button then reads Saving while it goes through, and the drop leaves your list.
Saving that name is the only thing in Phoenix that marks an order delivered. Nothing else does it - not a date passing, not the job finishing on the floor, not a card disappearing from Asana. So it is worth getting the name right, and worth doing it at the drop rather than back at the yard.
You get one go at it. A second proof on the same drop is refused rather than written over the first one, because the first one is the record of what actually happened. If it is wrong, ring the office.
Confirming closes the order. Check the job number on the card against the paperwork in your hand first. One card looks much like another on a phone screen in a loading bay, and closing the wrong order sends the wrong job off the board.
You confirm. The office schedules. You can say a drop happened; you cannot move a job to a different day, put it in another lane, or change a delivery date. If a run is wrong, ring the office and they will re-lane it.
On the truck tablet you get short codes, not customer names, and no suburb. That is deliberate. The tablet sits in a cab and gets handed around, so it carries what you need to match a card to a pallet and nothing that identifies a customer to whoever else picks it up. Your own sign-in on a floor screen is where the full detail lives.
This is for you if you decide what leaves the building and in what order - David, this section is yours.
The dock has its own tablet, set up from its own card like the machine tablets. It is not a machine: nothing on it says Start Setup. Sign in with your employee number and it opens the Dispatch board below, laid out for a tablet - the word Despatch across the top, your name beside Log out, the tabs large, and one big button on every card.
Open Dispatch. It is a grid of cards, one per order ready to go, with four tabs across the top and a live count on each:
| Tab | Shows |
|---|---|
| All | Everything waiting to dispatch, whatever the method. |
| Truck | Going on our truck. |
| Courier | Going by courier. |
| Pickup | The customer is collecting. |
| Direct Delivery | Supplier straight to customer. It never touches our dock. |
The method on a card comes from the Customer Deliveries card the office already fills in - Phoenix reads it every ten minutes and never guesses one. A card whose method nobody has set shows as unassigned; that is a card to chase, not a card to load.
If the board says nothing is waiting to dispatch, that is the answer, not a fault. Cards arrive on their own.
A card appears on Dispatch once the job has passed QA or has reached Despatch as a station. That is the whole rule. You do not have to fetch anything onto this board and nothing sits here waiting for you to notice it - the board is the queue.
A card leaves the board the moment it is confirmed. Anything closed, cancelled or already delivered never appears.
Each card carries its method badge, its current state, the job number, the description, the customer short code and the quantity. Direct deliveries - supplier straight to customer - are drawn in grey and show short codes only.
The button on the card is Mark delivered, or Mark collected on a pickup. It asks two things: who signed for it, which is required, and a photo or docket reference, which is not. Give the name and Phoenix records the delivery, closes the order and stamps today's date on it.
Marking a drop closes the order, and there is no undo button on Dispatch. If you confirm the wrong card, it is a correction back through the office, not a second click. Check the job number first.
A second proof on the same order is refused, not written over the first. The first signature is the record of what happened.
The order then appears on Ready to invoice for the office, with the name that signed for it beside the customer's own PO number.
Dispatch tells you what is ready. Deliveries tells you where it is going and on which day. Work them together: Dispatch to see the pile, Deliveries to see the week - Mon to Fri, with Local on Mon and Fri, Sydney on Tue and Thu, Newcastle on Wed, and Briestar kept in its own lane.
Courier, Cust Pick-Up and Direct Delivery are not on the Deliveries board at all: they never go on a truck, so they live here on Dispatch as their own tabs. They go when the courier comes, when the customer arrives, or straight from the supplier.
A greyed day on the Deliveries board is a public holiday. The heading says which working day that run has moved to, and the drops have moved with it.
You can also move a delivery to a different run or nudge its delivery date from the Deliveries card, using the Move button, then Save. A move you make sticks: nothing reschedules it back behind you.
You also have Factory Ops. It is the machine board with the office detail on it, and for despatch it answers the question the Dispatch board cannot: not "is it ready" but "how close is it".
Use it the afternoon before a run. If three Newcastle jobs are still two machines away on a Tuesday, you know that on Tuesday rather than at 7am on Wednesday.
This is for you if you run a section of the floor and set what the machines do next - Angelique and Jayden, this section is yours.
Open Factory Ops. It is the same board the factory sees on the TV - same columns, same order, same cards - with the office detail added back on. That matters: two screens side by side never tell you two different stories.
What you get here that the wallboard does not carry:
The board scrolls sideways through the machines and holds its place when it refreshes, so watching one machine does not mean being dragged back to the left every minute.
Top to bottom, a card gives you four things.
The traffic light. A coloured chip with a word beside it, top left. That is the job's stage in one glance.
The routing track. A row of short segments, one per step of the job's routing. Filled segments are behind it, the highlighted one is where it sits now, and empty segments are still to come. A track that looks wrong is one press from being fixed.
The step line. Underneath the track, in words: the step running now, then an arrow list of what follows, then the position - "3 of 5". If nothing has started yet it reads Not started and lists the whole routing. A job with no routing at all says No routing and offers a Fix press. Where a station like Hand Work covers more than one step of the routing, the card says so and offers a Check - it will not pretend to know which of them is live. You are the person who knows.
The due chip. Bottom right, beside the quantity. It shows the production due date in plain words - the day and month, and how it sits against today: "today", "1d", or "3d late". It turns orange as the date closes in and red once it has passed. Hover it and you get the delivery due date as well.
| Light | Means |
|---|---|
| Awaiting board | The job is on the board but the material is not here yet. Nothing to run. |
| Board received | The board has landed. The job is ready to be worked. |
| On machine | It is in production, on the machine whose column it sits in. |
| Complete | Its processes are finished. It is on its way to despatch. |
A card also badges Part rec'd when only some of the material has arrived, and Rush when the office has pinned it as urgent.
The cards in a machine column are in the order that machine should work them, top to bottom. The small figure beside the job number - "2/7" - is the job's position and the length of the queue.
To change it, use the controls along the bottom of the card:
The arrows grey out at the ends of the queue, so you cannot push a job above the top or below the bottom. Every reorder saves the whole queue, not just the one card, which is why the order you see is the order that holds. The wallboard picks it up on its next refresh, and the change is recorded with your name on it.
On the same row you have Station to move the job to a different machine, Hold to stop it, Routing to correct its process list, and Detail to open the full job.
A job on hold is still on this board. It stays in its machine column, dimmed, badged On hold, and it carries the reason on the card - "On hold: waiting on board". You can see exactly why it is stopped and who is waiting on what.
To take it off hold, the button on the card reads Release. Press it and the job rejoins the queue.
A job held by a failed quality check is different, and the card shows it differently - badged QA hold, with the reason reading "Quality hold: ...". Release does not appear on it at all. In its place is Waive QA, which only a level 4 can press, and it asks you to type why. Your name, the time and that reason stay on the job for good. A passing re-check does not clear a quality hold - only the waiver does.
The operator's tablet shows that the job is held and which of the two kinds it is, and locks every button until it is lifted. On a quality hold it also shows the note from the check that failed, because that is the operator's own words. Your free-typed office reason is never sent to the floor.
This is for you if you set up jobs, chase where they are, and keep the board stock straight - Georgia and Lilli, this section is yours.
Open Factory Operations. There used to be a separate Queue screen; its whole control set lives on the Factory Operations card now, so there is one board for placing, bumping, holding and routing a job. Each machine is a column, each job is a card, and the card carries chips where they apply - On hold, Rush, No routing.
Press Station on the card. A box opens asking for the station and, if you want it, a reason - "Green die-cutter down" is the kind of thing worth typing. Press Save and the job moves to that column.
Use Top and the up and down arrows on the card to walk a job through its machine's queue. They grey out at the top and the bottom of the column, and every card in the column renumbers as soon as the change saves.
Press Hold and type the reason - "waiting on board", "artwork query with the customer". Press Save. The card dims and carries an On hold chip.
The reason is for the office. The TV wallboard shows that the job is held and never why, so you can write what you actually mean.
To start it again, the same button now reads Release. One press, no dialogue. A job held by a failed quality check shows Waive QA instead, and only level 4 can press it.
A job carrying a No routing chip arrived without a process list. Press Routing and pick or type the steps, one per line, in the order they run:
Press Save. The card immediately grows a proper routing track on Factory Ops and the wallboard, and the system stops trying to find one for itself. You can use the same button to correct a routing that is simply wrong.
Every one of these - the station, the queue position, the hold, the routing - is recorded as a decision with your name on it, and it stays until a person changes it. Nothing re-sorts your queue overnight and nothing overwrites a routing you typed.
Open Projects. This is the answer to the phone call. One row per open job, and the columns are the ones you get asked about: Item Description, Project #, Material Date, Prod. Date, Order Qty, Prod Qty, Processes, Current Process, Delivery Date and Notes.
The search box, top right, is the quickest way in. Type a description, a project number, a customer or a process and the list narrows as you type. Every column heading sorts - press once for ascending, again to reverse - and blanks always fall to the bottom.
A Material Date reading SOH means the stock is already on hand: nothing to wait for. Delivery dates go orange as they close in and red once they have passed. Click a row to open the full job detail.
Each row says its state in words, in the progress column. It used to be a coloured bar with a legend above the table, which meant looking up from the row to find out what your row meant. The words are on the row now; the colour only repeats them.
| It says | Means | What to do |
|---|---|---|
| Blocked | Something is stopping this job. | Read the Notes column. Deal with it or get it to the person who can. |
| Needs attention | Not stopped, but it will not look after itself. | Have a look today. A date is tight, or a quantity does not add up. |
| On track | Running as it should. | Nothing. Leave it alone. |
Scan that column first. On a busy morning it tells you which five of eighty jobs are worth your time, and it tells you in words you can read straight off the row.
Open Stock. The page is headed Stock on hand - one row per product, with the tabs above the table filtering by silo.
The columns are grouped so that each one answers a single question: Product, Silo, On the shelf now, On order from a supplier, Reorder settings and What is happening.
On the shelf now is the physical count and nothing else - what you would find if you walked out and looked. A product that has never been counted says so; it does not show as zero. Zero and "not counted" are different answers and the screen keeps them apart.
On order from a supplier is separate, because it is not on your shelf yet. It names the quantity ordered and not yet arrived, the supplier, the supplier purchase order and the expected arrival. A product below its trigger with stock inbound is a different problem from one with nothing coming, which is why the two are never added together in one figure. The arrival date is honest about what it does not know: a date already gone says it is overdue and wants chasing or closing off, and an order with no date says so rather than guess.
Reorder settings is deliberately its own group, away from the count, because neither number in it is a stock level. The reorder trigger says WHEN to reorder - it is a threshold, not a level to climb back to. The reorder quantity says HOW MUCH to order. With no reorder quantity set, the buy comes from the recorded price breaks by cheapest total cost, and the supplier's minimum order is the floor.
What is happening says it in words, on the row. It names the basis it judged: whether the line is above or below its trigger on the shelf alone, or counting stock already on order. Where a line has never been counted, or has no trigger set, it says that instead - because there is nothing to judge it against, and a screen that answered "above the trigger" there would be telling you something untrue.
The Silo column on each row is a picker: Stock Board, Stock Cartons, ECB and the rest, plus Misc for anything that belongs nowhere. Choose the right silo from the list and it saves as you pick it - no separate save. Rows a person has set carry a small Linked mark, so you can tell your own decisions from the ones the system guessed from the product name.
Getting silos right pays off immediately: the tabs above the table count by silo, so once a silo is clean you can look at just that stock and nothing else. If something was filed wrong, pick again - including back to Misc.
This is for you if you open the Order Book first thing and live in it all day - Sarah and Erica.
The Order Book is at Order Book on the launchpad. Every order Phoenix has, from the moment it lands to the moment it goes out, is on this one screen. Across the top are the lifecycle tabs, and each tab carries its own count so you can see the size of the day without clicking. Click any row to open the full job panel.
An order sits in exactly one stage, and it only changes stage because somebody did something or because a fact arrived. Nothing drifts.
| Tab | What is in it | How an order leaves |
|---|---|---|
| New Orders | Everything that has arrived and has not been dealt with yet. Typed in, or emailed in. | Two exits, and only two: you process it, or you remove it. |
| Awaiting Board | Processed orders waiting on material. The board is ordered and a promised date is known. | The board is received, and the order moves into production. |
| Awaiting supplier date the sub-list under Awaiting Board |
Processed orders where the board is on order but the supplier has not promised a date yet. They are counted inside Awaiting Board as well, so the parent number is always the whole picture. | You record the supplier's date. |
| In Production | Jobs the factory is working, with the current process and the percentage complete. | The last step is finished on the floor. |
| In Deliveries | Finished work with a delivery date, a suburb and a produced quantity. | It is despatched and delivered. |
| Removed | Orders taken out of New Orders without being processed. Not a lifecycle stage, and deliberately not folded into any of the counts above. | You restore it, and it goes back into New Orders. |
The Awaiting Board columns and the Awaiting supplier date columns are identical on purpose - it is the same work, filtered.
One door (24 Aug 2026), and it lands in New Orders.
Quantities and items are never read out of a customer's email. Phoenix takes the sender, the subject and the attachment names, and nothing else - the row is there to tell you a customer has written in. You open the email, you read it, and you supply the facts. That is why an email row starts sparse and why nothing downstream will act on it until you have processed it.
The blank + New Order button is gone with the one-door change, but the form itself lives on - it opens pre-filled from inside the system: Re-order on a job panel, Raise order on Photo Create, and Review & raise on Purchasing.
Start in Customer Name. The list drops open alphabetically with + New customer pinned at the top. Pick a customer and their board prefix and Phoenix order history become available.
For a Re-Order, choose Past Product, then Clone From. Phoenix copies the exact product identity, last quantity, supply method, supplier, material, layout and routing. Change the quantity if needed, then confirm the production facts. The product identity stays locked because a Re-Order is the same product.
For Batch-1, the history choice is optional and is labelled Base Product and Copy Setup From. It copies only the manufacturing setup as a starting point. The new product description and stock code stay editable, and Phoenix refuses the old product code because that would be a Re-Order. Preview and Create order do not raise or send a supplier PO. After Create, Send PO opens the separate reviewed purchase step with the supplier, material and correct purchase quantity pre-filled. Stock Sale has no supplier PO action.
On a Re-Order, Phoenix checks the quantity against their last one. If what you type is more than half as much again as the last order of that item, the form stops and asks - "qty 11000 vs 1100 on their last order of this item - are you sure?" This is the 11,000-for-1,100 typo, caught at the door. It is a question and not a refusal: if the number is right, press Create order again to confirm and the order is made. It only ever asks when the quantity goes up - a smaller order is a normal thing and passes in silence. If you retype the item description after copying a history row, the check follows the description you actually typed, not the row you copied.
If you type a name that is not on the list, Phoenix takes that as a new customer and opens the contact row: a customer code of two to four letters, plus contact name, email and phone. Capture the contact while you have them. The code goes on the boards, so make it readable at a glance - the form tells you straight away whether the letters you picked are free, and the account number is assigned for you.
The form is David's own template, in two blocks. The top block is compulsory, every field of it: Date Received, Assignee, Order Type (Re-Order, Batch-1 or New Customer), Supply Method, Customer Name, Item Description, Order Qty and Cust PO - plus Delivery Suburb and Confirmation Date (the date confirmed back to the customer) from the second block. The customer must be picked from the registry or created inline; their code and account number fill themselves in.
Supply Method decides the rest. Stock Sale needs nothing more. Buy F/C also wants the Supplier and the Raw Material. W/Order also wants Number Up and the Routing No - and, under Number Up, Pieces per box, which is already 1 and only needs changing for a box built from more than one piece. Stock Purchase is Phoenix buying stock sheets or cartons for its own shelves: the customer locks to Phoenix Packaging, you name the Raw Material and the Supplier, and the order is done when the goods arrive at the dock - it never goes to the factory floor and never creates a delivery. If the quantity is under the supplier's minimum order, the form says so and asks you to confirm. The starred fields follow your choice, so the form always shows exactly what this kind of order needs. Press Create order.
Sending the purchase order to the supplier - for now. Raising a PO in Phoenix records it; the email to the supplier does not send itself yet. Open the PO on the Purchasing screen, press Copy to email on the preview, paste it into an email from your own mailbox and send it to the supplier's usual orders address. The preview shows the right address for each supplier. This is the one manual step left, and it comes off this page when the send leg goes live.
The moment the order is created its job number appears on the form - reserved for this order - and four buttons appear with it: Send PO raises the board purchase order pre-filled from the raw material and quantity, Query Order hands it to a department, Process Order makes the number permanent and moves the order on, and Remove Order takes the order out with a reason - and its number retires with it, never to be re-used.
An order you create carries its own Phoenix reference straight away, and it never changes and never disappears. Its job number is reserved when you create it and shown on the form; Process Order makes that same number permanent. If the order is removed instead, the number retires with it - recorded with your reason, never handed to another job. Two orders for the same customer always get different numbers, even before either is processed.
A job number reads CCCYYSSS: the customer's own 3-digit number, then the 2-digit year, then that customer's count for the year. Photo Create is customer 001, so their 2026 jobs are 00126001, 00126002, 00126003. Every customer counts separately, so two orders processed one after another for two different customers both end in 001. A job number is never changed and never re-used.
The job number starts with the customer's number, so an order that is not linked to a customer has nowhere to take one from. Processing refuses, and the pop-up says so rather than half-doing it.
The fix is two taps away, not in the Process order form: a customer name that is not in the registry carries a small flag chip in the Status column. Click the order to open its detail panel and press Add as alias… there. Link it, wait a minute, then process the order normally.
On any New Orders row, press Process order. The pop-up is titled Process order and it names the order at the top so you can see you are on the right one.
What is compulsory here follows the order's Supply Method, exactly as it did at entry: a Stock Sale asks for nothing beyond what the intake already captured; Buy F/C requires the supplier and raw material; W/Order requires the routing number and number up, and only a W/Order asks where the board is coming from. Starred fields are refused empty. There is one requirement that is not a field on this form - the order must be linked to a customer, because the job number begins with the customer's number.
| Field | What it means |
|---|---|
| Order Type | Three choices. Re-Order is a repeat of something Phoenix has
made before. Batch-1 is a first run of a new product for a
customer already on the books. New Customer is both at once -
a new product and a customer we have not made for before, and
it is the one that carries the payment checks. Pick it and Process
Order asks you about the deposit; see the box below. You can change the type here even if the order was typed in as something else. That is deliberate - the order often comes in before anyone knows it is a first order for a new customer - and the change is recorded against the job. |
| Assignee | The person who owns this order. Same staff list as the intake form, so the two can never drift apart. |
| Routing Number | The machine route from the catalogue. Type to search - the list is
approved set, numbered 01 to 102, and each entry
shows the machines it runs through, in order. David's review closed at
87; 88 and 89 came from his later emails, and
90 to 102 complete the recorded David and Mick edits
approved by Brad on 12 August.
Pick from the list.
When you do, the box fills with the system's own code for that routing:
the display number plus 200. Pick 13 and the box reads
213; pick 100 and it reads 300. Same routing, two
ways of writing it - the display number and the number the system stores. Two routings can
run the same machines and differ only by a setup; where that happens
the list spells the setup step out, so no two entries read alike. An order taken in before the review, and still sitting in New Orders, opens with an older three-digit number already in the box - one that is not on the list. That is correct - leave it alone and process the order. The old number still names its own route and the job runs exactly as before. Once an order has been processed its routing number is not shown again anywhere, so this is the only screen it appears on. Typing one of those older numbers onto a NEW order is refused, on purpose: they are not current routing codes. 013 is an old route, and it is not display routing 13 - the machines are different. The refusal says one of two things, and they need different answers. Sometimes it names the routing to use - "the routing stored as 124 is now 213". Use that one. Sometimes it says the routing retired with no replacement - David's review dropped it and put nothing in its place, and about half the old numbers are in that group. Then pick the entry from the list whose machines match the job: the machine names beside each number are there for exactly this. If nothing on the list matches, record a routing correction and raise it with Brad rather than inventing a number to get past the box. One more thing to read carefully. The refusal may also say "routing display 18 is stored as 218". That answers "if you meant display 18" - it is not a replacement for the old routing, and the machines are not the same. Take it only if David's 18 is genuinely the route you wanted. |
| Raw Material | What it is being made from. |
| Number Up | Finished items per sheet. This is what lets Phoenix compare sheets received against units ordered, so a 4-up job is not flagged as short. |
| Pieces per box | How many pieces of board make ONE box. Nearly always 1. A box built from a base and a lid is 2. Sitting directly under Number Up because they are the pair people mix up - see the box below. |
| Customer PO | The customer's own order number. An emailed or phone order often arrives without one, so you can supply it here. |
There is also an optional Supp PO # if the board order already has a number, and an optional notes box. The supplier PO is only ever added, never removed.
They sound alike and they are different facts. Number Up is how many pieces fit across a sheet - 4-up means four come off one sheet. Pieces per box is how many pieces make one finished box - and for almost every job that is 1, which is why the field arrives already showing 1. Leave it alone and nothing changes.
Set it to 2 for a base-and-lid box. That box is one thing the customer buys and two pieces off the sheet, so 1,000 of them need 2,000 pieces of board - double what the same order would need if the box were one piece. Phoenix now works that out for you: the board it expects to arrive, the sheets it issues to production and the time it allows on every sheet-fed machine all double.
If you type 0.5 into Number Up, Phoenix will not take it. It says "sheet_no_up must be a whole number of boxes per sheet - for a two-piece box set Pieces per box to 2". That is the same message pointing you at the same answer: Number Up stays a whole number, and the halves-and-pairs fact goes in Pieces per box. Half a box is not a layout.
You can set it in either place - on the new order when you already know, or on Process Order when you find out reading the order back. Leaving the box empty on Process Order changes nothing; it never wipes a value already there.
Press Mark processed on an order whose type is New Customer and Phoenix does not process it straight away. A red message appears on the pop-up - "Has the deposit been paid? Check bank account." - and the button changes to Confirm - deposit checked.
Go and look at the bank account. The question is asked once, at the one moment the order becomes real work, and it is asked because this is a customer Phoenix has not made for before.
If the deposit is there, press the button again and the order processes normally. If it is not, close the pop-up and chase it - nothing has been written and the order is still sitting in New Orders, exactly where you left it. Nothing is stuck either way: the question can always be answered, and answering it always lets the order through.
On a Stock Purchase that is also under the supplier's minimum you will be asked twice - the deposit first, then the minimum order quantity. The minimum-order question counts in sheets of board, and on a W/Order that is not the number you keyed: the form converts your boxes into the sheets they need and shows its working, so "qty 500 sheets below MOQ 693 - confirm (2000 boxes at 4-up)" is one order counted two ways, not two numbers that disagree. Two different questions, one press each.
The moment you enter it, the job gets its machine steps. It reaches the floor already knowing the sequence it has to run - nobody types the steps again.
Exactly one of these, never none and never two. This is the choice that decides where the order goes next.
| Choice | Where the order goes |
|---|---|
| Board is on order | Straight to Awaiting Board. If you already have a confirmed date from the supplier, put it in the Supplier promised date box underneath and the dates cascade immediately. If you do not, leave it blank and the order lands on the Awaiting supplier date sub-list until a date arrives. |
| Board is already in stock | Straight to In Production. Nothing is being waited on. |
| Stock Sheet - no supplier purchase | Records the supplier as Stock Sheet with no supplier PO, skips Awaiting Board altogether and goes to machine allocation. Production is due seven days after you process it. |
Then press Mark processed. The order leaves New Orders and the queue clears - that is the whole point of the step.
A handful of older orders came across carrying a supplier date written the wrong way round - 15/08/2026 rather than 2026-08-15. Phoenix cannot count seven days forward from a date it cannot read, so it stops and says so rather than guessing.
Fix it here, in this pop-up: put the real date in the Supplier promised date box and press Mark processed again. The date you type replaces the bad one outright. If you do not have a date from the supplier, choose Board is already in stock or Stock Sheet instead if either is actually true - never to get past the message.
This is the only screen that can correct it. The Supplier date button further down the Order Book only works on an order that has already been processed, so there is no point going looking for it.
The pop-up tells you plainly that it does not know whether the order went through, and that pressing Mark processed again is safe. It is - the retry carries the same key and Phoenix will not process the same order twice.
On the Awaiting supplier date sub-list, each row carries a Supplier date button. Press it, a date box opens in the row, pick the date the supplier has promised and press Save.
Entering that one date sets the whole tail of the job:
If you enter a date that has already passed, Phoenix says so and tells you the two dates it has worked out instead, so you are never left wondering why the screen shows something other than what you typed. When the board is actually received, the clock restarts from the receipt date - the same 7 and 2 - because receipt is the honest anchor.
A supplier's own promised date is theirs. Phoenix will not silently overwrite one that has come in from the supplier's own report.
If an order has moved past New Orders and never picked up a supplier PO, the row offers Attach PO#. Type the number in the row, press Save. It is offered on Awaiting Board, Awaiting supplier date and In Production, wherever the fact is still live.
This is clerical. It records a document number and moves no stage, changes no date and starts no clock.
Sometimes you cannot process an order because you need an answer from somebody else. Press Query on the row, pick the department, type the question, and press Raise query.
Four departments:
While a query is open, that order is not in New Orders at all. It is not hidden, not greyed out - it is gone from the queue and it cannot be processed by anyone, because it belongs to the department you handed it to. Your queue only shows what is actually yours to do.
The department answers on the Order Book's Queries tab with Answer and return. The order comes straight back to New Orders with the answer attached to the row, so you read the reply where you are working. From there you can process it, or send a further query.
If a question landed on the wrong desk, Re-route hands the same query to a different department, with an optional note saying why. The clock is not reset by a re-route.
Not everything that arrives is an order. A lead, a price enquiry, a duplicate. Press Remove on the row, pick a reason, and press Remove order.
Five reasons, and one of them is compulsory:
There is an optional note as well - use it for things like "duplicate of job 41822", which is what makes the Removed tab readable in a month's time.
The order moves to the Removed tab and stays there with the date, the reason, the note and the name of whoever removed it. The reasons are a fixed list precisely so the question "why did New Orders clear?" has a countable answer.
To bring one back, press Restore on the Removed tab. It changes to Confirm restore - press it again and the order goes back into New Orders. Two clicks, because an accidental restore quietly puts work back in your queue. If you walk away, the button disarms itself.
Click any New Orders row to open its detail panel, then press Edit order details (on an order with no customer yet, the same button reads Link customer). A small pop-up opens with the board prefix and the raw material - those, and the customer link when the order still needs one; everything else on the order is changed where it was entered. Leave a box as it is and it is left alone; the prefix box starts empty, so typing nothing there changes no prefix.
The commonest change is FC to SC. An SC is an FC going into stock - the same box, made the same way, but going onto our shelf instead of straight out to the customer - so the order should not be carrying a delivery. That is the whole reason this is worth changing rather than leaving. An unrecognised prefix is accepted and stored as you typed it, and the order simply shows Awaiting classification until the prefix is a known one; nothing is guessed.
The prefix can only be changed while the order is still in New Orders. Once you press Process Order the button is gone, and so is the edit - the order has been given its number, its route and, on some classes, its delivery, and changing the prefix underneath all that would leave a delivery card nobody can clear. The same applies to an order that has been removed: restore it first, then edit it. If you need a prefix changed after processing, it is a job for whoever runs the system, not a screen you can do it on.
Every change is recorded - what it was, what it became, who changed it and when.
Every row says what is happening in words. There is no colour bar down the left any more, and nothing on this screen asks you to remember what a colour meant. The old red/yellow/green rail was removed because it answered a different question from the stage - a green row could still be waiting for board - and it had no explanation beside it.
What to read instead: the What is happening column on the waiting lists, the Current process and progress column in production, and the words in Actions and notes. A waiting order says which kind of wait it is - Waiting for board, Waiting for finished stock or Board from stock - so you can tell the two apart without opening anything. Where colour is still used it only repeats what the words already say.
Beside those words is a compact row of small status chips - on New Orders they sit under the value in the Status column, so the Notes column stays a clean action row; on later stages they sit in the Notes column as before. Hover any chip for the full sentence. The ones you will see most are:
A customer name that is not in the registry carries a flag chip in the Status column. Click the order to open its detail panel and press Add as alias... there: pick the account the name belongs to, press Add alias, and the job links itself within the minute - no config, no waiting on anyone.
An alias only helps when the customer is already on the books. When they are not - a forwarded order, or a first order from somebody Phoenix has never made for - the same detail panel offers Set customer. It opens a list with the accounts the email itself names at the top, every active customer below them, and + New customer pinned first. Pick an existing account and the order links to it. Pick + New customer and two boxes open: their name, and a customer code of two to four letters - the form says straight away whether the letters are free, and the account number is assigned for you. Press Create and set customer and the account is created and the order linked in one go, so a first order from a new customer no longer has to be typed again in the New Order form. The code goes on the boards and every product they order is named after it, so make it readable at a glance. The customer can only be set before Process Order, because the job number starts with their account number.
For an order that arrived by email, its detail panel (click the row) can offer Prepare AI draft. Phoenix reads the email, its attachments, the customer registry and similar past orders, and proposes values for the order. When it is done the row itself offers Review AI draft as its first button - reviewing the draft is the fastest way to process the order.
The review screen puts the evidence on the left and the suggested order on the right. Every suggestion carries a confidence, the reason behind it, and a reference to the evidence it came from. Fields the AI could not fill are marked amber as your input, with a count up front so you know the size of the job before you scroll. You can open the original email or any attachment from the same panel.
If an amber notice at the top of the review screen says Shadow mode, the draft is evidence only: its fields are locked, nothing on that screen can be saved or applied, and the order itself is untouched. Read it, close it, and enter the order's details through the order form as normal.
Otherwise, edit anything that is not right, then press Apply to this New Order. Or press Reject - continue manually and carry on by hand. There is a review note box for recording why you changed or rejected something.
When one email contains several products, the review shows one card for every New Order it will create. Check the Phoenix product, the customer's wording and the whole-number quantity on every card. A customer item reference appears underneath the Phoenix product only when that customer supplied one; it is supporting evidence and is never required. Press Review and split into orders, recheck the full list, then press the confirmation button to create the separate orders.
Applying a draft updates the New Order and nothing more. There is no Process control anywhere on the AI screen - the AI cannot process an order, cannot move a stage, and cannot write a supplier date. Moving an order onward stays your decision, taken in the Process order pop-up like every other order.
This is for you if you raise the board orders and watch what has not come back - Emma, and anyone else raising POs.
Open Purchasing. The screen is in two halves: the order you are raising on the left, the jobs waiting on board on the right. Two tabs over the job list - Awaiting board, which is the default and is usually the question you are answering, and All open orders.
Phoenix mints the number itself. You do not type a number and you do not go anywhere else to get one. The screen tells you what it raised.
Until job numbers are switched on the number is PSP000001, ascending. After that it is built from the job: the job number plus one digit for which purchase order it is on that job, so job 00126001 gives 001260011 then 001260012. A job can carry nine purchase orders; the tenth is refused rather than given a number that means something else.
If you tick more than one job, the number is built from the lowest job number of the ones you ticked. The order still covers every job you ticked - the number is a label for the order, not a claim that it belongs to only one job. An order with no job ticked cannot be given a number at all once job numbers are on.
The stock code and quantity on each line are what connect this order to the stock ledger. Without them the board you have just ordered will not appear in the Incoming column on Stock, and the P.O. and ETA columns there will stay empty. The stock code list on this form is the same list Stock matches against, so a code you pick from it will always resolve. A code typed from memory that is not on the list will not.
The button goes down while the order is in flight, and each order carries a key of its own. If the network drops, the screen says it does not know whether the order was raised and tells you to press again - the retry is safe. You are then told which of the two happened: either "Already raised", naming the PO and supplier and confirming nothing was ordered twice, or that the earlier attempt was a different order and this one has not been sent yet. A purchase order is a commitment to a supplier, so the screen never guesses.
Below the order form is the Suppliers list - every supplier on record, with their email, credit terms where the WorkGuru capture recorded them (today that is only the two ABBE suppliers - a dash means not captured, not "no terms"), and whether they are active or dormant. The one thing you can change here is the default PO recipient: the address a purchase order raised in Phoenix will be emailed to once Phoenix starts sending them itself. It does not send them yet - the order still reaches the supplier the way it always has - but the address you set here is the one that will be used the day it does. A supplier wearing the no default recipient chip cannot be sent to at all, so filling those in now is what makes that day uneventful. Press Save on the row; saving an empty box clears the default.
Open Stock. One row per product, with sub-filter tabs for the silos across the top.
| Column | What it tells you |
|---|---|
| Product | The ledger code. |
| Description | What it is. |
| Silo | Which silo the item belongs to. This is a dropdown - change it on the screen and it saves. An item filed by a person rather than by the standing map shows Linked beside it. |
| On the shelf now | The physical count, and only that. A line nobody has counted says so - it never shows as zero. A counted zero shows as 0. |
| On order from a supplier | What has been ordered and has not arrived: the quantity, the supplier, the supplier purchase order and the expected arrival. Never added to the shelf count. If the purchase order does not state a quantity, it says so rather than showing 0. |
| Reorder settings | Two numbers, and neither is a stock level. The reorder trigger is WHEN - a threshold, not a level to climb back to. The reorder quantity is HOW MUCH. |
| What is happening | In words: whether the line is above or below its trigger, and what that was judged on. If it has never been counted, or has no trigger set, it says that - there is nothing to judge it against. |
This is for you if you want the state of the business in one look, and you answer the questions the office sends up - David, Vanessa, Michael and Brad.
Signing in lands you on Boards - every screen in the system as one big pressable tile, in four shelves: Orders and customers, Factory, Stock and buying, and Office. Each tile carries a line saying what it is for, and every board has a Home button that brings you back here. You only see the tiles your level can open.
In the corner of each tile is a star. Star the board you want to open on, and from then on signing in on that device takes you straight there. The star is per device, so the tablet on the floor and the machine in the office can each open on something different. Press it again to clear it.
Under the top bar on every screen is the same strip of numbers, and every tile is a link to the screen behind it.
| Tile | What it counts |
|---|---|
| Open Jobs | Everything live. This is New Orders plus Awaiting supplier date plus Awaiting Board plus In Production - it always adds up, because it is worked out once, on the server. |
| New Orders | Arrived, not yet processed. |
| Awaiting Board | Waiting on material, with Awaiting supplier date shown smaller underneath as its own filter. |
| In Production | On the floor now. |
| In Deliveries | Made, going out. |
| Current SOH | Stock on hand across the ledger. |
| DIFOT | Delivered In Full On Time. |
DIFOT is the share of jobs Phoenix produced inside the seven days the factory gets. The clock starts when the board is actually received, not when it was ordered - so a supplier who is three weeks late cannot drag the factory's number down. Hover the tile for the detail: the percentage, how many jobs it is measured over, and the trailing window. Jobs still inside their seven days are pending, not failures, and they are not counted either way. Until there are enough measured jobs to say something honest, the tile shows a dash rather than a percentage built on three jobs.
On the Order Book the five lifecycle tiles are left off the strip - the tabs on that page already are the filter.
Factory Operations is the management view of the board: machine columns and job lights, with the office data on the card - customer names, hold reasons, late jobs - and reorder, reroute, hold and routing available on the card itself. This is the screen to open when you want to know what the floor is actually doing.
TV Wallboard view is the same board stripped for the unattended screen in the factory: short codes only, no customer names. It navigates nowhere - it is a display, not a console - and it carries the same counts strip, including the honest note when the feed has stopped moving. That matters most on the screen a room full of people is trusting.
The bottom shelf of the launchpad is the office's master data and cost base. Analytics, Prices and the Flow Library are level 4 only - they carry margins, sell prices and machine rates.
The Console is where master data gets decided: buy facts (MOQ, lead time, price) on supplier offers, sell families, stock bindings, customer accounts - and a journal of every change with the person's name on it. Level 3 and above can open it and read everything. Changing anything in it stays with the listed staff only, whoever's level says what - approval of master data is a name-by-name grant, not a level.
Open the Order Book and press the Queries tab. When the office cannot move an order without an answer, they hand the whole order to a department - Operations, General Manager, Sales or Deliveries - and it appears here. (There used to be a separate Order Queries screen; its old address brings you to this tab.)
The department chips across the top filter the list, and each chip shows how many are waiting, so you never click into an empty screen. The filter rides the address, so you can bookmark your own queue and never think about it again. Each card shows the order, the question, who raised it and how long ago in working days.
Press Answer and return, type the answer in your own words, and the order goes back to Sarah or Erica with your answer attached to the row. If it is not really yours, Re-route sends it to another department with an optional note.
| Age chip | When it appears |
|---|---|
| Chasing | After 2 business days. |
| Overdue | After 4 business days. |
The clock is not reset by a re-route, so a re-route cannot clear an overdue chip. An order with an open query is out of New Orders the whole time it is with you - the office cannot work around it, which is exactly why answering it is the thing that unblocks the order.
Open Photo Create. This is Glen Innes stock against the reorder points agreed with the client. The stock-on-hand lands automatically on a schedule from the i4query pull, and the stock-on-hand date sits above the table so nobody reads an old number as today's. If the pull breaks, Upload i4query export takes the same file by hand as a fallback.
One row per product, with the code, description, stock on hand, reorder point and MOQ, and a status:
| Status | Means |
|---|---|
| ORDER | Stock on hand has reached or dropped below the agreed reorder point. Time to order. These sort to the top. |
| GOOD | Above the reorder point. Nothing to do. |
| NO DATA | A product being managed that was not in the upload. Phoenix will not guess a number for it - it tells you it is missing. |
| FORECAST | The screen is in forecast mode for the agreed pre-supply cycle. The numbers stay live; the order flags are stood down. The chip at the top of the screen says which mode you are in. |
An ORDER row carries a Raise order button. It opens the Order Book intake with the customer, the item and the MOQ quantity already filled in - one reorder, one product.
Open Projects. Every open job, one row each, with its machine and its dates. This is the screen for the phone call that starts "where is my job" - one list, no tabs to choose between, no hunting.
Every action anyone takes on any screen is written down against the person who took it, with what it was before and what it was after. The Removed tab shows who removed an order and why. A query shows who raised it and who answered it. A stock item filed into a silo by hand is marked as a person's decision, not the system's. Nobody has to remember what happened, and nobody has to be asked.