before its senior personnel retire. SLAD would greatly benefit from a strong professional development program that is rich in training opportunities and participation in workshops, conferences, and continuing education (e.g., modeling and simulation workshops). SLAD would also benefit from hosting conferences and workshops in its areas of expertise. Although it has demonstrated improved knowledge of the literature and more collaboration, SLAD is still not a leader in most of the relevant technical areas. Active leadership in the greater technical community would serve to enhance SLAD’s reputation both within and outside the Army and its ability to recruit bright scientists and engineers.
Other possibilities for professional development exist within current SLAD programs. For example, the program on developing a metric to predict mild traumatic brain injury represents a new line of endeavor for SLAD; it may not culminate in a fielded metric, but it adds to the scientific knowledge base. The program is impressive in terms of its collaboration and participation in the broader research community.
SLAD traditionally has been successful in shifting emphasis as appropriate to address the changing demands and requirements of technology and DoD strategy. Information operations and cyberwarfare are examples of recent changes that significantly affect SLAD. SLAD has extended its portfolio to include assessment of vulnerability of communications, networks, and information processing on the battlefield. Current and future focus will have to include more modeling and simulation applications, integrated with physical testing and evaluation, to include more predictive capabilities and risk analyses in these areas.
SLAD continues to extend its suite of analytical tools by building on successful collaborations and by capitalizing on the success of customer-driven, short-turn-around-time assessment programs to identify technical gaps that would benefit from enhanced tool development. The overarching umbrella for tool development is SLAD’s system-of-systems analysis (SoSA) tool, S4. Most of the tools being developed within SLAD can be used as stand-alone tools, but most are also slated for use within the model library of the S4 code. The many challenges that surround this plan of action are discussed separately at the end of this chapter. This section discusses the challenges and opportunities associated with enhancing individual programs and tools.
In certain programs, such as the one examining lethality and vulnerability for the ground Combat Vehicle Program, SLAD estimates and assesses the impact of changes against known and projected threats. SLAD’s record in meeting such challenges is good. The challenges include delivering results as quickly as possible. Any improvements in responsiveness would be appreciated by developers and decision makers.
The question of whether to buy or develop software is often faced by SLAD analysts. In assessing the vulnerability of various electronic weapons, the challenge is to come up with a code to convert from commercially supplied solid geometry models (supplied by contractors) directly into SLAD vulnerability models to achieve radio frequency fidelity commensurate with model requirements. SLAD should examine the commercially available software for providing this conversion.
MUVES 3 is the next-generation ballistic vulnerability/lethality model software code developed to replace the well-used MUVES-S-2 code. MUVES-S-2 will eventually be retired, which will require that all users transition to use of the newer MUVES 3 code. The plan for transitioning from MUVES-S-2 to MUVES 3 does not appear to demonstrate involvement of current MUVES-S-2 users outside of SLAD but still within the Army—specifically the Army Materiel Systems Analysis Activity (AMSAA) and the Center for Army Analysis and the Training and Doctrine Command Analysis Center (TRAC). These organizations depend on data produced by MUVES-S-2 and need to be considered in the transition to MUVES 3. This transition program should be expanded to support all organizations that depend on MUVES-S-2 output.