Bonus Assignments

If you have some time left, you can work on the following bonus assignment.

Bonus 1: Swimmin' in SKUs

Mark is looking rather intently at the screen with the model of Order Amount opened.

"And you said we will perform this every time an item is checked out of the warehouse, once we have those fancy pants scanners in place and linked up to the WMS?"

The WMS is the Warehouse Management System which Loes' team introduced about a year and a half ago.

"Yeah, that’s the plan, " Loes replies, "we expect those scanners to be installed in about three weeks time."

"Then I think you’ve missed something." Mark points to the output column of the decision table. "You’ll order 250 T1’s when their level drops below 100? We’ll be needing a bigger warehouse. Or people will be taking them home."

He smiles, but doesn’t continue, allowing you to think.

"Oh, shoot!", you exclaim and fake banging your head against a wall.

Did you notice the problem with the current decision model?

Think of a way to prevent Bolt Bike’s employees from a deluge of SKUs and adjust the model.

In a DMN Decision Table, an input entry that’s irrelevant in a rule contains the value of a dash (-).

When you’re done (or if you just peek head wink), the following request will make sense and after you’ve adjusted it for any name mismatches with your updated model, you can use it to test the updated model, after you deploy it.

Message 2.7: Evaluate decision `order_amount`; T1, Below threshold, Ordered, Expected outcome: 0
{
  "decisionId": "order_amount",
  "variables": "{ \"warehouse_stock_level\": 132, \"orders\": 20, \"spare_parts_reserve\": 20, \"storage_tier\": \"T1\", \"order_placed\": true }"
}