C4SCS / DSCSA-Trace-Interop-Pilot

Apache License 2.0
0 stars 0 forks source link

Simulation: Bad Actors #32

Open rceleste125 opened 1 year ago

rceleste125 commented 1 year ago

Simulation Request Summary

Used to propose a simulation or scenario. This is for the Trace Pilot Team work-START approval step. Discuss the proposed work or change.

Create a Simulation that includes Bad Actor(s).

#

Final Disposition Approval Summary

Used to present completed work to Trace Pilot Team for approval. Discuss the work that was completed in reference to the above proposal. Include any differences from the proposal and why. Show final state of documents along with pull requests (if needed). # Reference and Working Documents:

(C4SCS Trace Interoperability Pilot Google Folder)

(C4SCS Trace Interoperability Pilot - Steering Google Folder)

Image

Image


Details:

1. What will we use the scenario to test or exercise? [An explanation of why we want to build this simulation and generate supply chain data to test Traces against.]

2. Actors [What entities should be included in the scenario.]

3. What is unique about this scenario [Specify the unique properties of this scenario.]

4. Behavior: [Describe any behaviors you'd like to see that will affect the TI or Traces.]

5. Attachments: [If relevant, allow team members to attach screenshots, error logs, or any other supporting files that can help in understanding the scenario.]


Approvals needed for this work to begin:

Approvals needed for the output of the work to be published or executed:

Triage:

Affected Parties (help determine Sunrise/Sunset):

ewaldorf commented 8 months ago

In this scenario, did the legitimate W ship the same serialized item to D1 which BA1 also shipped to D1 with altered TI/TS data? What prompted D1 to initiate a trace? Is it because D1 detected that D1 received the same serialized item already?

ewaldorf commented 8 months ago

Did you intend to have Bad Actor Fake Wholesaler and Fake Authority to point to the same GitHub issue record?