Objective: Generate a resource flow diagram for a Ghost Kitchen operations and scaling model, configured where 1 Step = 1 Minute. The model must test kitchen capacity against manual B2B brand acquisition and daily rush hours. Please use standard Machinations nodes. 1. The Growth Engine (Interactive Stress Test): Create a Pool named 'Active Brands'. Set it to be Interactive (clickable) so the user can manually add 1 brand at a time to stress-test the system. Start with an initial value of 1. 2. Base Order Intake (1 Step = 1 Minute): Create a Source named 'Incoming Orders'. Draw a State Connection (dashed line) from the 'Active Brands' Pool to the 'Incoming Orders' Source. Set the Resource Generation formula on 'Incoming Orders' to: 0.115 * ActiveBrands. (This represents 5,000 orders/month broken down into minute-by-minute flow). Connect the 'Incoming Orders' Source via a Resource Connection to a Pool named 'KDS Ticket Queue'. 3. Rush Hour Modifier (The Daily Spike): Create a Source named 'Time of Day'. Have it generate 1 resource per step into a connected Pool called 'Clock'. Create a State Connection from the 'Clock' Pool to the 'Incoming Orders' Source. Configure the State Connection logic: When the 'Clock' pool reaches between 1080 and 1200 (representing a 2-hour dinner rush), multiply the incoming order formula by 3 (so it becomes 0.345 * ActiveBrands). 4. Prep Station (2-Minute Processing): Connect the 'KDS Ticket Queue' to a Pool named 'Prep Station' using a Resource Connection. Add a Delay node of 2 (or set the transfer rate to 0.5 per step) to represent a 2-minute prep time. 5. Cooking Station (The Primary Constraint): Connect the 'Prep Station' to a Pool named 'Cook Station'. Set the 'Cook Station' Pool capacity to 4 (simulating maximum oven/grill space). Add a Delay node of 5 (or set the transfer rate to 0.2 per step) to simulate a 5-minute cook time. 6. Packaging & Dispatch: Connect the 'Cook Station' to a Pool named 'Packaging' with a transfer rate of 1 resource per step (1 minute to pack). Create a separate Source named 'Driver Arrivals' generating resources (Drivers) into a Pool named 'Waiting Drivers' at a steady rate. Connect both the 'Packaging' Pool and the 'Waiting Drivers' Pool into an AND Gate. Connect the Gate to a Drain named 'Successful Dispatch'. 7. Analytics Dashboard: Add a Chart node. Connect State Connections from 'Active Brands', 'KDS Ticket Queue' (the backlog), and 'Successful Dispatch' (throughput) to the chart to visualize exactly when the 5-minute cook time causes the queue to fail as new brands are manually added.
