their implementation. The ICM Core System shall H Corridor Will be part of vendor conduct a rules test, Management supplied CMS evaluation and exercising the rules using test acceptance criteria. data on a regular basis and providing a pass/fail check for the results of each rule execution. The Corridor Technical M Corridor Not part of system testing. Manager shall conduct Management Will be evaluated during post weekly and quarterly implementation review. evaluations of the rules and their execution. Rule Documenting and Archiving The ICM Core System shall H Corridor Will be part of vendor provide a means for users to Management supplied CMS evaluation and archive rules within the acceptance criteria. system. All developed rules shall be H Data Hub Testing to be defined when stored in a format usable by the requirement is addressed. the DSS rules engine. The ICM Core System shall M Corridor Will be part of vendor utilize a configuration Management supplied CMS evaluation and management system to acceptance criteria. manage rules. Post-Incident/Event Analyses The Corridor Manager shall H Institutional Not part of system testing. conduct a post-incident Job Tasks Will be evaluated during post analysis review with all implementation review. affected agencies within one week of each significant event. Quarterly Operational Reviews The Corridor Manager shall H Institutional Not part of system testing. conduct a quarterly review of Job Tasks Will be evaluated during post the operational effectiveness implementation review. of the ICM Environment. As part of the quarterly M Institutional Not part of system testing. effectiveness evaluation, the Job Tasks Will be evaluated during post Corridor Manager shall assign implementation review. a score to the observed effectiveness of response planning activities. The Corridor Manager shall H Institutional Not part of system testing. use results from quarterly Job Tasks Will be evaluated during post operational assessments of implementation review. decision support operations
their implementation. The ICM Core System shall conduct a rules test, exercising the rules using test data on a regular basis and providing a pass/fail check for the results of each rule execution. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. The Corridor Technical Manager shall conduct weekly and quarterly evaluations of the rules and their execution. M Corridor Management Not part of system testing. Will be evaluated during post implementation review. Rule Documenting and Archiving The ICM Core System shall provide a means for users to archive rules within the system. H Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. All developed rules shall be stored in a format usable by the DSS rules engine. H Data Hub Testing to be defined when the requirement is addressed. The ICM Core System shall utilize a configuration management system to manage rules. M Corridor Management Will be part of vendor supplied CMS evaluation and acceptance criteria. Post-Incident/Event Analyses The Corridor Manager shall conduct a post-incident analysis review with all affected agencies within one week of each significant event. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. Quarterly Operational Reviews The Corridor Manager shall conduct a quarterly review of the operational effectiveness of the ICM Environment. H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. As part of the quarterly effectiveness evaluation, the Corridor Manager shall assign a score to the observed effectiveness of response planning activities. M Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review. The Corridor Manager shall use results from quarterly operational assessments of decision support operations H Institutional Job Tasks Not part of system testing. Will be evaluated during post implementation review.
i-210_verification_plan_v1.0_final.docx