120 likes | 409 Views
Mission Readiness Assessment System (MRAS). Duane ‘Chip’ Morris ManTech Security Solutions Group Enterprise Integration Center (e-IC) 304-368-4221 morrisd@mantech-wva.com. Overview. Project Description Development Strategy Design Required and Produced Content Schedule and Transition.
E N D
Mission Readiness Assessment System(MRAS) Duane ‘Chip’ Morris ManTech Security Solutions Group Enterprise Integration Center (e-IC) 304-368-4221 morrisd@mantech-wva.com
Overview • Project Description • Development Strategy • Design • Required and Produced Content • Schedule and Transition
MRAS-NG GOAL • A software shell application that: • Resides on the DS2 server • Provides users with situational awareness based on material and personnel readiness • Allows subject matter experts to create and manage the knowledge applied by the system to generate the operational assessments across a variety of ship classes and joint weapon system platforms
MRAS-NG Concept Manual Input
MRAS-NG Development Strategy • Address Equipment/Systems Availability and operator training content areas first • Situational Awareness • Work up from report data to more timely availability data/info • CASREP • 2KILO • 3M Database • SORTS messages • Legacy monitoring/expert systems • Manual input
MRAS-NG Design • Software Shell • Modular • Agent based • User managed external configuration files • User tool set • Development Tools • Application Tools • Accessible through DS2
MRAS-NG Design • Data Sources • IT-21 LAN resident databases • Sensor readings • DS2 databases • Archive files • Manual Input
MRAS-NG Focus Areas • Addresses four (4) aspects of Readiness Assessment – each with required and produced content • Missions • Processes • Entities • Views
MRAS-NG Content • Missions • Required • Mission Definitions, Capabilities, Critical Equipment • Produced • Assessments and Situational Awareness • Processes • Required • Business Rules • Sequence of process steps execution • KIM (Knowledge Instance Model) construction and maintenance • Produced • Findings of Equipment/Systems monitored
MRAS-NG Content • Entities • Required • Training Status, Equipment Status/Availability Data (CASREP, 2KILO, ICAS, TRAREP, etc.) • Produced • Operational Status/Availability, Assessments and Situational Awareness • Views • Required • User Preferences • Produced • Customized Presentation • Custom Report generation
MRAS-NG Transition • Oct 2003 – Mar 2005 • Redesign, develop, certify, and field test • Incorporate field test findings • Additional equipments • Prep for fielding • NAVSEA to submit MRAS in POM for FY06 • Apr 2005 – Sep 2007 • Refresh – sources, systems, capabilities • Oct 2007 – Mar 2009 • Refresh 2 of the MRAS
MRAS-NG Transition • Milestones • Jan/Feb 2004 Design Review and Demonstration • IPRs at 4-6 week intervals • May/Jun 2004 Pre Test Review • Jun-Aug 2004 • Factory Acceptance Test (Fairmont, WV) • DS2 Acceptance Test (NSWC Crane) • Certification Testing (SPAWAR Chesapeake) • Sep 2004 = Field Test with DS2 in Sea Warrior • Sep-Dec 2004 = Refactoring and Expansion of Application sources • Feb 2005 = Acceptance Testing • March 2005 = Deployment Preparations