It fosters reuse of software components particularly the common support services that comprise a large portion of each model or simulation. There are better uses of scarce funds then rebuilding the same code and data descriptions for each new requirement. The answer is that models are limited in the type of questions that they help answer. The analytic community is faced with new missions, less resources, and new demands for system trade-offs. One area where reuse will save time and money in the future is in the verification, validation and accreditation of the models and simulations.
Analysis pervades all of the other communities.
The analytic community should evaluate what other communities are doing, pick what is useful, and focus its investment on what hasn't been done before and what is most useful to the analytic community. For developers - adaptable architectures with a full range of scale and complexity saving cost, schedule, and risk for the same level of requirements. For users - new federations to answer different questions with greater granularity. For resource sponsors - no need to fund as many upgrades to meet new requirements. For DoD leadership - development of fewer simulations and more capable and adaptable existing simulations.