diff --git a/assignments/src/MV3500Cohort2019JulySeptember/projects/Boron_Yurkovich - UDPs for MAJ Furr/README.txt b/assignments/src/MV3500Cohort2019JulySeptember/projects/Boron_Yurkovich - UDPs for MAJ Furr/README.txt
new file mode 100644
index 0000000000000000000000000000000000000000..272db7bec68555367b554d84f481516d4767a5eb
--- /dev/null
+++ b/assignments/src/MV3500Cohort2019JulySeptember/projects/Boron_Yurkovich - UDPs for MAJ Furr/README.txt	
@@ -0,0 +1,51 @@
+1.  Purpose - The purpose of this project was to incorporate Distributive 
+Interactive Simulations (DIS) protocol data units (PDU) into MAJ Furr's thesis 
+work.  His work supports the warfighter and reveals data that will wisely inform
+future decisions.  It was a pleasure to support his work and to make his work 
+more accessible to the Modeling & Simulations and Wargaming communities of 
+interest.
+
+2.  Background - MAJ Furr created a discrete event simulation (DES) of the 
+call for fire process from the forward observation points through battalion level
+fires.  The DES covers multiple forms of radio frequencies and concepts.  His DES
+shows how the broadcasting of conventional omni-directional frequency modulation
+waveforms can be intercepted by a near peer competitor.  What was lacking from 
+his work was the ability to integrate his work with other simulations.  
+
+3.  Process - Capt Jonathan Boron and Maj Daniel Yurkovich utilized an incremental
+model process to incorporate the DIS PDUs into MAJ Furr's DES.  The approach began
+with understanding MAJ Furr's code and which java classes placed elements onto 
+the event list.  With this understanding, a "PDU Constructor" class was created
+to house all of the required PDUs.  At this point, the following PDUs deemed 
+necessary as a proof of concept are:  CreateEntityPDU, EntityStatePDU, FirePDU,
+DetonationPDU, TransmitterPDU, ReceiverPDU, and SignalPDU.  A major break through
+that enabled quick implementation was MAJ Furr's creation of the "SimpleMover3D"
+class.  All moving elements, both enemy and friendly, were subclassed from the 
+SimpleMover3D class.  Within the SimpleMover3D class we placed the PDUConstructor,
+PDUSender, TransmitterPDU, and ReceiverPDU.  With more refinement of the process,
+the CreateEntityPDU,and EntityStatePDU should be in the SimpleMover3D class. 
+Since a large focus of MAJ Furr's work was how different radio procedures 
+influenced the battlefield, A struggle for Capt Boron and Maj Yurkovich was to 
+identify where radio messages were executed, broadcasted, in the DES portion of
+MAJ Furr's program.
+
+4.  How to use - Start "PduReceiver" prior to running MAJ Furr's main program.
+
+5.  Future work - The web of details subordinate to the main 72 PDUs identified
+in the MOVES Institute's open-dis7-source.jar needs improvement in our implementation.  
+The Capt Boron and Maj Yurkovich lack the scope and time to gather the full 
+details of enumerations for each time of radios, waveforms, and rounds being 
+used in the simulation.  A better understanding of how the Institute of Electrical 
+and Electronics Engineers Standard for DIS - Application Protocols (IEEE Std 
+1278.1-2012) and Simulation Interoperability Standards Organization Reference 
+for Enumerations for Simulation Interoperability (SISO-REF-010-2019) work 
+together would make future work easier to complete.  This data requires 
+refinement in each PDU.  
+
+6.  Conclusion - With a program written in the module/component structure SimKit 
+DES style, the implementation of DIS PDUs was a relatively simple process.  The 
+classes taught in the first year of the MOVES curriculum, specifically Java & DES, 
+establish a strong foundation for any second year MOVES student to continue to 
+improve MAJ Furr's simulation and broaden its impact with DIS implementation in 
+MV 3500.  
+