1 / 10

Tools And Resources

Tools And Resources. Group Make Up. *=Election Tampering Evident. Reuse and Repositories & Visibility & Discovery Who pays to keep the content current (incentive/funded) Repository Access Too many repositories/not focused User Groups possible solution Contractual wording for the model

caelan
Download Presentation

Tools And Resources

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tools And Resources

  2. Group Make Up *=Election Tampering Evident

  3. Reuse and Repositories & Visibility & Discovery • Who pays to keep the content current (incentive/funded) • Repository Access • Too many repositories/not focused • User Groups possible solution • Contractual wording for the model • Trusted Sources • Tracking of User Experience • Technical Evolution • Industry may not be in a better position • Need contractual language to identify to use rights • PM Responsible for deposit • Policy • If model isn’t visible shouldn’t be funded/supported • Funding for specific reuse • More communication and interaction • Forums

  4. Methodology • Data IT developers need … • Professional M&S Developers (CMM) • Education for M&S Professionals (Developers and Users) • Repeatable • Easily Understood • Capability/Performance Based • Approach • Should be requirements driven • Tailorable to the requirements • Framework of models rather than one model (multiple simulations) • Fit the tool to the problem not the problem to tool • Scope the problem • Matching tool to problem and data issue • Combination of virtual and live/interactive approaches - some things cannot be simulated

  5. Cost Estimation of M&S • Standardizing CDRs • Cost over program life cycle • Dual Analyses • Need for parametric cost models that integrate with operational representations/models • Cost Avoidance/ROI/Savings

  6. Back Up

  7. Bucket List • Methodology • Data IT developers need … • Professional M&S Developers (CMM) • Education for M&S Professionals (Developers and Users) • Repeatable • Easily Understood • Capability/Performance Based • Approach • Should be requirements driven • Tailorable to the requirements • Framework of models rather than one model (multiple simulations) • Fit the tool to the problem not the problem to tool • Scope the problem • Matching tool to problem and data issue • Combination of virtual and live/interactive approaches - some things cannot be simulated

  8. Reuse and Repositories & Visibility & Discovery • Who pays to keep the content current (incentive/funded) • Repository Access • Too many repositories/not focused • User Groups possible solution • Contractual wording for the model • Trusted Sources • Tracking of User Experience • Technical Evolution • Industry may not be in a better position • Need contractual language to identify to use rights • PM Responsible for deposit • Policy • If model isn’t visible shouldn’t be funded/supported • Funding for specific reuse • More communication and interaction • Forums • Standard Tools and Registry • How much standardization do we need? • Standardization of Terminology, Interfaces, Data Standards, Metrics • Standard tools hinder innovation • What standards are mandatory • Accreditation Standards for use to specified standard

  9. Process Changes • Centers of Excellence needs to be funded @ OSD • Level of Analyses • Metrics Standardization across services and industry • Requirements Driven • Tailor to Requirements • Data Accuracy, Validity, Collection Issues, Availability • Institutional Changes • Fix Collection System • Automation • Right Data has to be collected • Data Context • Data Rights are appropriately purchased • Classification • Collaborative Environment • Authoritative Data Sources • Model and Simulation Integration • Micro Modular Architecture • Cross Resolution Models Aggregation/Deaggregation • Formal versus approach level of integration • Do totally integrated models make sense? • Documentation and VV&A • Levels of documentation and VV&A • Cost to VV&A should not cost more than the whole analysis especially for 1 time analysis • Few tools • Lack of understanding • Written for a different class of models

  10. Cost Estimation of M&S • Standardizing CDRs • Cost over program life cycle • Dual Analyses • Need for parametric cost models that integrate with operational representations/models • Cost Avoidance/ROI/Savings • Interoperability • Various levels of interoperability and integration • User Training • Programmatic Input • Other

More Related