Page History

How-to → Examples → Feature → Application → MCP DesignerBytePizza AI Designer Example

Summary

BytePizzaSBaT BytePizza is a simulating a fast-food pizza restaurant operation. It demonstrates real-time order processing, inventory management, machine state simulation, alarm monitoring, trend visualization, and revenue tracking — all built with FrameworX and AI-assisted engineering via MCP.

The solution showcases how FrameworX can model a complete operational workflow: a customer places an order, production machines process each item through realistic state sequences, inventory is consumed, revenue is accumulated, and operators can monitor all KPIs through a polished multi-page HMI.

Image Added

Architecture Summary

Unified Namespace (UNS) — Tag Structure

All tags are organized under the Restaurant/ root hierarchy with clear separation between server-side shared data and client-side UI state.

Inventory (Integer)

Machines

Revenue

Client Tags (Per-Session UI State)

Scripts

MachineStateCycler (Server Task): The core simulation engine. Runs cyclically on the server and advances each machine through its preparation states every 3 ticks when the machine's Active flag is set to 1.

Pizza Machine States: Stretching Dough → Spreading Sauce → Mozzarella → Pepperoni → Oven → Baking → Slicing → Boxing → Pizza Ready

Breadsticks Machine States: Preparing Dough Sticks → Oven → Baking → Garlic Butter → Breadsticks Ready

Soda Machine States: Placing Cup → Adding Ice → Dispensing Soda → Placing Lid → Soda Ready

CodeBehind — OrderInterface Display

Client-side logic embedded in the OrderInterface display handles the full order lifecycle:

• DisplayOpening(): Resets all order quantities, totals, and flags to zero

• DisplayIsOpen(): Cyclically recalculates order total and checks machine readiness

• BtnStartOrder_Click(): Activates machines for ordered items

• BtnLetsEat_Click(): Finalizes order — adds to revenue, subtracts inventory, resets machines

CodeBehind — InventoryManagement Display

• ResetAll_Click(): Resets all 6 inventory items to 50 units

• ResetRevenue_Click(): Resets total revenue to $0

Alarms

All alarm items are configured as Low (Lo) condition alarms in the Warning group with a threshold of 5 units.

Alarm Groups: AuditTrail, Critical (requires acknowledgment), Warning (no ack required).

Historian

7 tags are logged to Table1 for historical trending:

• All 6 inventory tags (DoughInventory, SauceInventory, BoxInventory, DoughSticksInventory, CupInventory, LidInventory)

• TotalRevenue

Displays (HMI)

All content pages follow a unified light theme design language:

• Light gray background (#FFF0F2F5)

• Dark header bar (#FF1A1A2E) with red accent line (#FFE63946) and "BYTEPIZZA" branding

• White content cards (#FFFFFFFF) with light borders and colored accent strips per category

• Color coding: Gold for Pizza, Brown for Breadsticks, Blue for Soda, Red for critical actions, Green for success/trends

Page List

Visual Dynamics Used

• FillColorDynamic: Inventory status bars change color based on stock level (red/yellow/green thresholds at 0/5/10)

• VisibilityDynamic: Production progress bars visible only when machine is active

• ActionDynamic: Add-to-order buttons use RunExpressions to increment quantities; Start Order and Let's Eat buttons use RunScript to trigger CodeBehind methods

• SecurityDynamic: "Let's Eat" button disabled until all ordered items reach Ready state

Security

How to Run

1. Open the solution in FrameworX Designer

2. Start Runtime

3. Navigate to OrderInterface to place an order

4. Add items (Pizza, Breadsticks, Soda) using the + buttons

5. Click START ORDER to activate production machines

6. Watch machines cycle through states in the Production Line panel

7. When all machines show "Ready", click LET'S EAT! to complete the order

8. Check InventoryManagement to see updated stock levels

9. Monitor TrendPage for inventory consumption over time

10. View AlarmPage when inventory drops below 5 units

In this section...