1. Define a Use Case
This module is about getting set up for success by clearly and accurately defining the use case you are trying to solve. Once you've defined the use case, you'll be able to identify the expertise you need to teach the system to learn well.
Learning Objectives
At the end of this module, you will be able to:
Identify the knowledge components that are key for defining a use case
Explain actions, sensors, KPI, benchmarks, and ROI
Identify actions, sensors, and KPI for a real use case
Video Lesson
Practice Activity
Read the production scheduling case study and think about these questions:
What are some individual control actions?
What are some sensor variables you would need to track?
What is the KPI?
Then read on for answers.
Here are some of the action variables from the case study. Do these match the actions you thought of?
Actions
Baker A mix cakes - action telling Baker A to start mixing cakes
Baker B mix cupcakes - action telling Baker B to start mixing cupcakes
Baker C bake from Mixer 1 - action telling Baker C to bake the product from Mixer 1
Baker A decorate from Oven 1 - action telling Baker D to decorate the product from Oven 1
Wait - action telling the system to do nothing for this action step
And so on for every baker, product, and action combination
Here are some of the sensor variables from the case study. Do these match the sensors you thought of?
Sensors
Baker A time remaining - sensor reporting how much time is left on Baker A's task
Mixer 1 recipe - sensor reporting which product is currently in Mixer 1
Mixer 2 time remaining - sensor reporting how much time is left on Mixer 2's recipe
Completed cakes - sensor reporting how many cakes have been bought so far
Cupcake cost to make - sensor reporting the ingredient cost of making a batch of cupcakes
Cookie demand - sensor reporting how many cookies are predicted to be sold
And so on for every baker, equpiment piece, and product
The KPI for this process is profit.
Profit is not directly measured, but it can be calculated by combining the measures of cost to produce the products, the number of products produced, and the demand.
Check Your Understanding
Read the oil blending use case and answer the following questions.
For questions 1-5, characterize each variable as a sensor or an action
Amount of crude oil #1 purchased
Yield of naphtha from distillation
Yield of kerosene from distillation
Amount of naphtha sent to reformer
Total naphtha available
What would you choose as the KPI for the process?
Throughput: maximize total product created
Waste: minimize unusable product created
Profit: maximize revenue minus costs
Demand satisfaction: minimize unsold product
What is the decision frequency for this process?
1 minute
1 hour
1 day
1 month
1 year
For questions 8-9: Measurements that define the characteristics of the different crude and finished oils (for example, density, sulfur, viscosity, wax, and metal content) are not included as variables in the system.
Why is it possible to control this process effectively without that information?
These qualities are not important for making decisions about oil blending
That information is assumed to be standard for each crude type and product
It is not possible to directly measure the physical characteristics of the oil stocks and products
This would provide too much information and slow the system down to the point of uselessness
The problem set-up assumes that physical properties are standard within the crude and product types. If in the real world there is variation within these categories, what challenging phenomenon would that represent?
Changing conditions
Different scenarios
Incomplete information
Noise
Funnel states
Last updated