Skip to content

Latest commit

 

History

History
36 lines (25 loc) · 2.28 KB

Kitchens.md

File metadata and controls

36 lines (25 loc) · 2.28 KB

Kitchens

image

Capability rationale and description

The kitchen orders and delivery must become automated to handle customer demand and to support the subscription capability. It should also allow admin interface to monitor kitchen loads, orders inflow and outflow, and manage relevant supplies purchases. It's like manufacturing Shop Flow Control for managing the various components of the manufacturing process. At some point of time we might want to introduce automated quality control systems too and sensors to manage temperature, humidity and other parameters in Kitchen appliances. Both, Shop Flow Control and Quality Control are areas that we would consider for buying vs. building as they are not specific business core (unless there are very specific and high priority requirements that are not supported by vendors or integration is complex/expensive). The Kitchen Capability begins with manual work order creation by the admins, an expands with the addition of Subscription Capablity to support automated work order creation. The capability interfaces with external services like ChefTech for Inventory Control, Nutritional Analysis, Purchasing & Ordering, Production, and Requisitioning & Transfer. Since Kitchen deals with food manufacturing, a sophisticated security controls are required at the very detailed level of the architecture as well as Role or Attribute Based Access capability.

Use cases

  • Creation of manual work orders.
  • Creation of automated work orders from subscription.
  • Order and manage supplies.
  • Manage kitchen operations.
  • Allows managing several kitchens in different locations.

Components

  • Kitchen Application for kitchen, orders and supplies management.
  • Kitchen Service API. List production orders, shift CRUD, meal prep time tracking, quality control parameters.
  • Work Order Creation engine. Creates work orders for the kitchen.
  • Material Order engine. Creates purchase orders for material and ingredients.
  • Kitchen DB. List production orders, shift CRUD, meal prep time tracking, quality control parameters.

Architectural characteristics

  • Interoperability.
  • Workflow.
  • Integration.
  • Single DB.
  • Domain partitioning.

Architectural choice

  • Microservices
  • Service-oriented and message driven.