Business Digital Twin Architect

Lightweight Business Twin Specification — Meal-Kit Order Cycle

Purpose: Help owners identify what evidence is needed to evaluate a possible volume increase.

Scope: Weekly cycle from website order receipt through courier handoff. This is a portable design specification, not a live or synchronized twin. No operating performance has been measured.

Boundary and entities

Actors: customer, menu planner, purchasing owner, packing team, courier contact. Roles are fictional placeholders; assign real owners internally.

• Objects: menu, order, ingredient, supplier, purchase, packed box, delivery, issue, decision, metric.
• Systems: website/order record and any inventory or planning tools are unknown and must be inventoried.

Provisional flow and relationships

Customer submits order → order is included in weekly demand plan → menu/ingredient requirements are calculated → purchasing secures ingredients → team packs boxes → courier receives handoff → delivery issue or completion is recorded. Link each order to menu, required ingredients, procurement, packing batch, handoff, and outcome where evidence supports those relationships. Exceptions to investigate: late order changes, ingredient substitution, supplier shortfall, packing error, missed pickup, address issue, refund, and unavailable labor. Do not assume these occur; record them as questions.

Evidence register

Metric definitions to validate

On-time handoff rate: orders handed to courier by the committed pickup cutoff ÷ orders due that cycle. Define exclusions and timestamp source.
2.

Ingredient availability rate: planned ingredient units available by pack start ÷ planned units; substitutions tracked separately.
3. Packing throughput: completed boxes per staffed packing hour, with quality/rework reported alongside it.
4. Order exception rate: orders with at least one documented exception ÷ orders in scope.

Conditional +20% scenario

If weekly orders increase by 20%, demand for ingredients may rise proportionally only where menu mix and portion requirements stay constant. This is a modeled assumption, not a forecast. Test supplier lead times, purchasing cutoffs, cold storage, packing stations, staff hours, courier volume commitments, and exception handling. No bottleneck or probability can be inferred without baseline measurements. Compare a base, constrained-supplier, and added-capacity scenario after owners supply data.

Guardrails and next steps

Keep an as-of date and evidence state for every important field; distinguish observed, calculated, assumed, simulated, and unknown. Do not infer causality from correlation. Request (1) anonymized weekly order history, (2) recipe/ingredient mapping, (3) supplier lead times and commitments, (4) packing staffing and throughput observations, and (5) courier pickup/delivery records. Owners validate the model and approve any operational change.