24
High-level Model Development
o
OVERALL SYSTEM PERFORMANCE
High-level
Entity Based Model
Reliability
discrete event
simulation models
Logistics
analytical
models
Sensors
physics based
models
C4ISR
analytical
models
OUTPUT
DATA
Trapezoid: Needs Analysis
Needs Analysis
Obj Analysis
Alt Generation
Modeling
Analysis
Conclusions
In order to compare and contrast competing system’s architectural solutions, SEA-8’s modeling goal was to create a high-level digital battle space. In order to quantify key performance parameters for each alternative, we used various types and combinations of models.  The outputs of these lower level models became the inputs for our higher level model to test overall system performance. Reliability, Logistics, C4ISR and Sensors were four major areas of focus for our modeling efforts. Of significant importance to the overall model was the timeline associated with getting Blue assets to the theater. (CLICK) Deployment team used inputs such as transit speed, distance, and payload capacity to produce outputs such as arrival time distributions. (CLICK) For C4ISR (CLICK) the inputs such as bandwidth available and required, processing and transmission time, and frequency were processed, and produced outputs such as data latency and fusion time that apply to recognized system metrics for C4ISR and the Command Function. (CLICK) For our sensor performance physics-based model, (CLICK) we used inputs such as time of year, bottom type, Red force expected noise level and other inputs to generate outputs of expected detection ranges and expected propagation loss within the Bass Straits which was the AOR we chose for our study. An example of the output we received from this model is shown, indicating the expected propagation loss of one area of the Bass Straits. (CLICK) These low-level models combined to provide inputs to the high-level entity based model used to simulate interactions between forces. (CLICK)