Skip to content
Snippets Groups Projects

Pamela's Merge Request: 10-26-2021

Merged Pamela's Merge Request: 10-26-2021
Pamela_Branch_4 into master
Merged Pamela Dyer requested to merge Pamela_Branch_4 into master
Compare
and
4 files
+ 15
− 81
Compare changes
  • Side-by-side
  • Inline
Files
4
models/Application_examples/Agile_Production_Platform_Customer_Interactions.mp
+ 8
− 74
@@ -21,74 +21,8 @@ agile production / building of alternative supply chains.
@@ -21,74 +21,8 @@ agile production / building of alternative supply chains.
Specifically in this model, the focus is on the delivered
Specifically in this model, the focus is on the delivered
quality of 5,000 medical face shields (a Customer placed
quality of 5,000 medical face shields (a Customer placed
the order using the APP). The narrative for this baseline
the order using the APP). Running this model at Scope 1
use case is as follows:
generates four event traces, described as follows:
Precondition: A Customer has an urgent need for 5,000
medical face shields.
1. Customer logs into the APP linkage platform.
2. APP authenticates valid customer credentials and prompts the Customer for the need.
3. Customer inputs a need for 5,000 units of a medical face shield with desired
attributes.
4. APP identifies the individual components of the needed item.
5. APP determines which Sector Resources to search for equivalent components (prepares
component search parameters).
6. APP searches Sector Resources for available component matches and their attributes
(e.g., availability, timeliness, cost, reliability, quality, quantity).
7. APP assembles combinations of available components having intersecting
attributes (find component matches).
8. The APP constructs a list of valid supply chain elements.
8a. If the supply chain for the order is complete, the APP displays the order options to the
Customer along with soonest delivery time, total cost, and component attributes for
each participant in the chain (e.g., participant reputation, material specifications,
product dimensions, suitability for certification).
8b. Otherwise if one or more components is unavailable, the APP reprocesses the order with
a new search for equivalent alternatives to the missing component(s) (back to step 5).
9a. If the supply chain is complete, the Customer receives the order options from the APP
and filters, sorts, and inspects the presented solutions, selects a solution, and places
the order.
9a-1. The order is delivered to the Customer and meets their expectations.(Favorable
Outcome)
9a-2. The order is delivered to the Customer and does not meet their expectations.
(Unfavorable Outcome)
9a-3. The order is not delivered to the Customer (Unfavorable Outcome).
9b. If no alternative supply chain can be found, the Customer is notified by the APP that the
order cannot be completed at this time. (Unfavorable Outcome)
Assumptions/Abstractions:
The "Data for supply chain" event that is included in the APP and the Data Services/
Resources root represents asynchronous and continuous data for support to the
alternative supply chain construction. The individual interactions involved here
are another level of refinement reserved for a separate MP model that can be elaborated
separately from this model which focuses on the Customer-APP interactions.
Known ways to get to an unfavorable outcome:
- Customer asks for a disproportionately large amount of product and the system is strained
for other users
- Allow for aggregation
Questions:
- Does the APP prioritize orders?
- Can a customer get orders with "some assembly required" or does it come assembled from
some service provider?
Postcondition: The Customer receives 5,000 face shields (not shown in the model yet).
Running this model at Scope 1 generates 4 event traces,
described as follows:
Trace 1: The order is delivered to the Customer and
Trace 1: The order is delivered to the Customer and
meets their expectations (Favorable Outcome).
meets their expectations (Favorable Outcome).
Trace 2: The order is delivered to the Customer and
Trace 2: The order is delivered to the Customer and
@@ -115,15 +49,15 @@ SAY statement; trace annotation; event sharing; table;
@@ -115,15 +49,15 @@ SAY statement; trace annotation; event sharing; table;
behavior, unexpected; behavior, emergent;
behavior, unexpected; behavior, emergent;
behavior, agile production platform
behavior, agile production platform
Instructions: Run for Scope 1. Reviewers of this model are
Instructions: Run for Scope 1. Reviewers of this model are
invited to provide feedback for better-named events, other
invited to provide feedback for better-named events, other
events that may occur normally or as a disruption to the
events that may occur normally or as a disruption to the
sequence, missing or incorrect interactions, and the
sequence, missing or incorrect interactions, and the
partitioning of the high level APP functions for architectural
partitioning of the high level APP functions for
cohesion. Lower-level (implementation) activities have been
architectural cohesion. Lower-level (implementation)
deliberately omitted for now in order to reach consensus on
activities have been deliberately omitted for now in order
intended use at the highest level of abstraction.
to reach consensus on intended use at the highest level
of abstraction.
Scope 1: 4 traces in less than 1 sec.
Scope 1: 4 traces in less than 1 sec.
==========================================================*/
==========================================================*/