CBRNE Project Team Meeting 01 November, 2011 Checking Out Content CBRNE Project Team Meeting 01 November, 2011

CRTI Content More than 75% of listed projects in the CRTI archives are not relevant to our project The remainder all have some potential How to evaluate them?

Requirements Criterion system for scoring content Our website or programming needs must be well-defined At least one evaluator needs to have extensive programming and/or web design skills Where content is software or a website we need access to the programming team Ownership, copyright, privacy, security issues Financial issues (cost-sharing, fees, royalties)

Notes on Content Scoring Scale Keep it simple: Suitable or not suitable Training or operations or both Ready to use or needs development Internal score vs User score

Considerations in Evaluation Software or website robustness, scalability and capacity, failure issues, support issues Accessibility (PC, mobile devices) Ability to generate/host simulated content for training Interactive systems generate data for research, audit

Non-CRTI Content Issues Video/voice conferencing? Mobile apps Commercial (PinPoint for Blackberry) Free (Google Maps) Medical Messaging

What Users Get Buffet No turnkey solutions to operations or training Our opportunity to sell services and bespoke exercises Community and training opportunities Exposure to risk of comm failures in a crisis Our opportunity to market solutions with help of federal or commercial partners