Skip to content
Snippets Groups Projects
Commit c3626291 authored by Yurkovich, Daniel (Maj)'s avatar Yurkovich, Daniel (Maj)
Browse files

Update README.txt - "warfighter"

parent 428e2d25
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
assignments/src/MV3500Cohort2019JulySeptember/projects/Boron_Yurkovich - UDPs for MAJ Furr/README.txt
+ 65
− 65
View file @ c3626291
1. Purpose - The purpose of this project was to incorporate Distributive
Interactive Simulation (DIS) protocol data units (PDU) into MAJ John Furr's
thesis work. His project models a specific aspect of ground combat communications,
producing data that may influence and change how ground units conduct tactical
communications while in close contact with the enemy. As such, there is great
benefit to adding a networking capability to his simulation that will allow it to
interact with other combat models.
2. Background - MAJ Furr programmed a discrete event simulation (DES) of the
call-for-fire process from the forward observation positions through battalion
level fires using java and SimKit. His simulation covers multiple forms of radio
frequencies and means of communication. Consequently, his results show how an
enemy capable of monitoring the electromagnetic spectrum can intercept conventional
omni-directional frequency modulation waveforms and exploit this information to
disrupt our kill chain. What was lacking from his program was the ability to
integrate his simulation with other combat models.
3. Process - Capt Jonathan Boron and Maj Daniel Yurkovich utilized an incremental
model process to incorporate the DIS PDUs into MAJ Furr's simulation. The approach
began with understanding MAJ Furr's code and how java classes interacted with each
other and populated events onto the event list. With this understanding, a PDU
Constructor class was developed to provide a blueprint that supports the creation
of all required PDUs. At this point, the following PDUs deemed necessary for proof
of concept were: CreateEntity, EntityState, Fire, Detonation, Transmitter, Receiver,
and Signal PDUs. A major breakthrough that enabled quick, seamless implementation of
PDU construction into the simulation was found in MAJ Furr's creation of the
SimpleMover3D class. All moving elements, both enemy and friendly, were subclassed
from this SimpleMover3D class. Within the SimpleMover3D class we placed the primary
PDUConstructor object, as well as methods that allowed Transmitter, Signal, and
Receiver PDUs to be sent. Moreover, with further refinement of the program, the
CreateEntity and EntityState PDUs were completely integrated into 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 and broadcasted in the DES portion of
the program.
4. How to use - DIS was implemented in the simulation such that no other additional
files need to be explicitly run for PDUs to be constructed and sent. A PduReceiver
class was programmed, as well, in order to assist in monitoring the state of the
program and debugging. Thus, to observe and track the PDUs being sent, simply run
this file prior to executing MAJ Furr's main program.
5. Future work - The intricacies subordinate to the main 72 PDUs identified in
the MOVES Institute's open-dis7-source.jar need improvement if a more effective
and thorough implementation is desired. 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. Moreover,
the simulation itself, while an effective model of the call-for-fire process,
lacked certain, minute details to fully populate all parameters of the PDUs. This
included specific information, such as the type and number of transmission
tower arrays and the frequency and model of radios employed. Subsequently, some
data requires refinement in each PDU. Lastly, this project showed that DIS can
seamlessly interoperate with SimKit programs. Although outside of the scope of
this project, it would be beneficial for a more thorough integration of the
PDUConstructor and PDUSender classes into the SimKit package.
6. Conclusion - The modular structure of SimKit and DES allowed for the seamless
implementation of DIS PDUs into MAJ Furr's call-for-fire combat simulation. The
classes taught in the first year of the MOVES curriculum, specifically Java and
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
MV3500.
1. Purpose - The purpose of this project was to incorporate Distributive
Interactive Simulation (DIS) protocol data units (PDU) into MAJ John Furr's
thesis work. His project models a specific aspect of ground combat communications,
producing data that may influence and change how ground units conduct tactical
communications while in close contact with the enemy. As such, there is great
benefit to the warfighter by adding a networking capability to his simulation
that will allow it to interact with other combat models.
2. Background - MAJ Furr programmed a discrete event simulation (DES) of the
call-for-fire process from the forward observation positions through battalion
level fires using java and SimKit. His simulation covers multiple forms of radio
frequencies and means of communication. Consequently, his results show how an
enemy capable of monitoring the electromagnetic spectrum can intercept conventional
omni-directional frequency modulation waveforms and exploit this information to
disrupt our kill chain. What was lacking from his program was the ability to
integrate his simulation with other combat models.
3. Process - Capt Jonathan Boron and Maj Daniel Yurkovich utilized an incremental
model process to incorporate the DIS PDUs into MAJ Furr's simulation. The approach
began with understanding MAJ Furr's code and how java classes interacted with each
other and populated events onto the event list. With this understanding, a PDU
Constructor class was developed to provide a blueprint that supports the creation
of all required PDUs. At this point, the following PDUs deemed necessary for proof
of concept were: CreateEntity, EntityState, Fire, Detonation, Transmitter, Receiver,
and Signal PDUs. A major breakthrough that enabled quick, seamless implementation of
PDU construction into the simulation was found in MAJ Furr's creation of the
SimpleMover3D class. All moving elements, both enemy and friendly, were subclassed
from this SimpleMover3D class. Within the SimpleMover3D class we placed the primary
PDUConstructor object, as well as methods that allowed Transmitter, Signal, and
Receiver PDUs to be sent. Moreover, with further refinement of the program, the
CreateEntity and EntityState PDUs were completely integrated into 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 and broadcasted in the DES portion of
the program.
4. How to use - DIS was implemented in the simulation such that no other additional
files need to be explicitly run for PDUs to be constructed and sent. A PduReceiver
class was programmed, as well, in order to assist in monitoring the state of the
program and debugging. Thus, to observe and track the PDUs being sent, simply run
this file prior to executing MAJ Furr's main program.
5. Future work - The intricacies subordinate to the main 72 PDUs identified in
the MOVES Institute's open-dis7-source.jar need improvement if a more effective
and thorough implementation is desired. 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. Moreover,
the simulation itself, while an effective model of the call-for-fire process,
lacked certain, minute details to fully populate all parameters of the PDUs. This
included specific information, such as the type and number of transmission
tower arrays and the frequency and model of radios employed. Subsequently, some
data requires refinement in each PDU. Lastly, this project showed that DIS can
seamlessly interoperate with SimKit programs. Although outside of the scope of
this project, it would be beneficial for a more thorough integration of the
PDUConstructor and PDUSender classes into the SimKit package.
6. Conclusion - The modular structure of SimKit and DES allowed for the seamless
implementation of DIS PDUs into MAJ Furr's call-for-fire combat simulation. The
classes taught in the first year of the MOVES curriculum, specifically Java and
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
MV3500.
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment