This Briefing is UNCLASSIFIED

1. EYexsY+3KMJiBCd9owwix9LoGwQ= GIG AOR Decision Support System (GADSS): Path to Web Services Mr. Miguel Hoffman USSTRATCOM/J663 Global NetOps Control Center Mr. Hank Weverka, MITRE USSTRATCOM/J865 C2 Systems Support 20 October 2009 This Briefing is UNCLASSIFIED

2. Overview • GADSS Evolution • Current GADSS Operational Flow • New and Emerging Requirements • Web Services Development • Web Services Way Ahead

3. GADSS Evolution • Developed in-house • Created by watch standers using Microsoft Access database • Based on authoritative data available per DISA Circular 310-65-1 • Fulfilled need for quick analysis and warehousing of C4 event data • Expanded for Authorized Service Interruption (ASI) management • GADSS Web (Interim solution on STRATCOM Intranet) • Web-based display of NetOps events in Access DB using DHTML • Linked GADSS events to associated Strategic Knowledge Integration Web (SKIWeb) posts and blogs • Allowed drill down through event details and knowledge base (KB) • GADSS (Enhanced) development • Part of Command and Control (C2) Modernization Program • Produced using Oracle 10g database with Java web user interface • Available via SIPRNet to users external to STRATCOM domain

4. GADSS Capabilities • Maps the C2 Support Infrastructure • Relational knowledge base of circuits, systems, and locations • Organizations and missions • Mission Correlation • Rapid, non-linear analysis of NetOps events • Identifies impacted missions and alternate C2 means • Automated NetOps Reporting • Generates Communications Reports (COMSPOTs) and notifications • Expanded for Authorized Service Interruption (ASI) management • Expanded Cyber Awareness • Links to SKIWeb; updates posts/blogs via web services automation • Default, read-only view of NetOps events and KB data available to users world wide via SIPRNet

5. GADSS Capabilities • Knowledge Base (KB) • Provides comprehensive information on circuits, systems, and organizations • Searches archived NetOps events during analysis of active events and provides historical perspective on mission impact • Track and trend outages by circuit, system, location, and mission • Master Station Log (MSL) • Allows more efficient collaboration among watch standers on shift • Provides user-configurable search of audit logs for actions taken on events and KB records; results filtered by user or work center • Quality Assurance • Evaluate overall work center performance and quality of work • Ensures accurate and timely assessments and notifications

6. GADSS Supports NetOps Info Needs • Automated, non-linear analysis of events • Simultaneous analysis of multiple circuits, systems, locations, organizations, and missions • Operational Mission Impact • Missions affected • Decisions made; Courses of Action (COAs) executed Circuit System Location Organization Mission

7. Current GADSS Operational Flow GIG Network System Events 4 Submit Publishable Events to SKIWeb 3 Analyze and Track Events • Global network alarms and outages • Theater scheduled and unscheduled outage tickets GADSS SKIWeb Analysis Data Event Data Reference Data 2 Monitor Events GIG Network Configuration Systems and Contacts • Circuit/Trunks/Links, Nodes • Systems • Locations • Organizations • Mission dependencies • POCs 1 • Manage Configuration, Contacts, etc. • Map C/T/L, System, Location, Org, Mission dependencies • Manages approximately 16K of the total 80K + circuits provisioned by DISA • SIPRNet only application RIMS I3Tel WWOLS-R

8. Network Configuration Data Sources • Primary data sources • World Wide Online System-Replacement (WWOLS-R) • Network management tool used for provisioning data for the Defense Information Systems Network (DISN) • DISA telecommunications asset database • Contains data on circuits, trunks, and links that comprise the DISN • Intelligent Integrated Information for Telecommunications (I3Tel) • Database management tools used for provisioning data (current status and customer circuit requirements) for the ATM network (both black and red sides) • Mostly written in Microsoft Access • Resources Integrated Management System (RIMS) • Multiple copies of the database designed for specific purposes; not connected nor synchronized • Example: RIMS 6.0 for Promina legacy and data circuits; RIMS-O for Optical Related circuits • Other sources • COMSPOT; ASI Notification (ASIN); Regional Computer Emergency Response Team (RCERT) notification, and Operations Briefs

9. Data Maintenance Flow • Monthly configuration updates generated by request from WWOLS-R; downloaded from I3Tel and RIMS source sites • WWOLS-R files sent as email attachment to GNCC • GNCC reformats and uploads flat files into GADSS • Other configuration updates are handled manually • Periodic data calls • Established points-of-contact (POCs) • POCs are managed through self-correcting processes • GADSS outage reports to POCs generate calls for corrections

10. Event Management Flow • Integrated Network Management System (INMS) continuously monitored for network system outages • Impact check performed for events affecting networks supporting STRATCOM mission • Events impacting or of interest to STRATCOM missions are entered into GADSS • Events classified by type • U.S. - Level 1 • Nebraska – Level 2 • STRATCOM HQ – Level 3 • Events occurring within STRATCOM HQ recorded in local TMS by ITCC contractor are also monitored and entered into GADSS depending on impact • INMS alarming circuits and REMEDY tracking numbers are included with GADSS events as applicable

11. Event Analysis Flow • Analysis performed on events entered into GADSS • Based on recorded network configuration • Reviewed in context of: • Other related reported outages • Previous outages if this is network system component • Analysis documented within GADSS • Related events linked within GADSS event entries • Reports generated and sent to POCs recorded in GADSS • Status of outage is monitored and changes are recorded in original GADSS event entry

12. GADSS to SKIWeb Event Flow • Critical system network outages posted to SKIWeb via SKIWeb Event Web Service • GADSS event data mapped to SKIWeb and entered as SKIWeb event • Event in SKIWeb linked to GADSS event • Event in GADSS linked to SKIWeb event • GADSS event status changes added as comments (blogs) to SKIWeb event

13. New and Emerging Requirements • Automate injection of configuration data from WWOLS-R following DoD net-centric guidance for Service Oriented Architecture (SOA) -- Work In Progress • Automate screening and collection of circuit alarms from INMS based on community business rules • Expand visibility into and support for military and leased satellite communications (SATCOM) based networks • Enable Community of Interest (COI) support and extend GADSS functionality to COCOMs, Services, Agencies • Enable selective, releasable NetOps event exchange with Coalition Partners following SKIWeb model • Expose GADSS knowledge base, event, and analysis data elements to other DoD systems via web services

14. Service Inventory Web Service DISA/NS83 OASD/NII • Goal • Automate the transfer and update of DISA Service Inventory data (WWOLS-R) within GADSS C/T/L cache Governance USSTRATCOM/J663 NSWCDD/Z33 • Approach • Partnership/Governance • Service producer – DISA/NS83 • Service consumers • USSTRATCOM/J663 – Global NetOps Command Center (GNCC) • Naval Surface Warfare Center Dahlgren Division (NSWCDD)/Z33 – Mission Assurance Division • Guidance – OASD/NII (Solers Inc.) • Incremental • Focus on current data content (GADSS) • Identify future data requirements (Real-Time Network Operations and Mission Impact [RNOMI])

15. Service Inventory Engineering Approach • USSTRATCOM Requirements Document • GADSS today • GADSS/RNOMI future • Base XML schema on Operations Support Service for Java (OSS/J) • Extend only when necessary • Request/response interaction pattern • Get C/T/L changes based on selection criteria  Beginning and ending date range • Get all C/T/L data • Scheduled initial operational capability November 2009

16. Service Inventory Way Ahead • Governance • Establish service level objective/agreement • Schema change control and versioning process • Approach for using the standard Universal Core (UCore) XML schema • Reference data management • Current data coding/encoding standards drive many of GADSS internal data relationships; which enable its event analysis capability • Issues • Change control • Enable new WWOLS-R follow-on system

17. Other Web Services • GADSS as a service consumer • NetOps alarm automation (INMS) • Ticket management linkage automation (Remedy) • GADSS as a service producer • GADSS NetOps event reporting • GADSS C2 support infrastructure mapping • Knowledge base for circuits, systems, and locations • GADSS mission correlation • Analysis of NetOps event’s impact on missions SOA governance and management are key to enabling critical services

18. Summary • GADSS Perspective: Web services are critical to warfighter efficiency and effectiveness • Continue relationship with NII Engineering Support • Pursue NetOps alarm automation • Standardize format of data entered into Remedy Ticket Management System (TMS) • Expose GADSS data in coordination with internal USSTRATCOM Nuclear Command and Control Integration (NC2I) initiative Your interest and support of future GADSS capability enhancements is appreciated

19. EYexsY+3KMJiBCd9owwix9LoGwQ= Questions/Comments? This Briefing is UNCLASSIFIED

20. EYexsY+3KMJiBCd9owwix9LoGwQ= For More Information GADSS https://gadss.stratcom.smil.mil/GADSS/ SKIWeb https://skiweb.stratcom.smil.mil/skiweb-web/ Mr. Miguel Hoffman USSTRATCOM/J663 Global NetOps Control Center 402-294-8265 / DSN 271-8265 michael.hoffman@stratcom.mil Mr. Hank Weverka, MITRE USSTRATCOM/J865 C2 Systems Support 402-294-1326 / DSN 271-1326 hweverka@mitre.org This Briefing is UNCLASSIFIED

21. EYexsY+3KMJiBCd9owwix9LoGwQ= Background Slides This Briefing is UNCLASSIFIED

22. Integrated Network Management System • Network management tool used to monitor real time alarms on the GIG • Collates all the alarm information from various managed and unmanaged network elements either directly or from their management systems • Applies advanced fault management functions • Generates alarms for service affecting faults • Provides up down status of elements operating on the Defense Information Systems Network (DISN) INMS

23. Notional Alarm Integration Process 4 D GADSS (Core) GADSS (Web Services) 2 • Monitoring performed by GADSS Alarm Web Service • GADSS subscribes to INMS Web Service • INMS pushes events to GADSS Alarm Web Service • GADSS Alarm Web Service preprocesses each alarm • Determines each COI’s applicability • Proposes GADSS events for qualifying alarm(s) • When available, uses alarm’s trouble ticket information to • Merge alarms onto single GADSS event • Update existing GADSS event if trouble ticket matches event’s trouble tickets • Places actions on appropriate COI’s Work List 3 Alarm Preprocess Add to log Run COI applicability Propose event /queue Update COI work list A Analysis Data INMS 1 B B C Event Data D C Reference Data Work Queue C Alert Log A 1 2 3 Analyze 4

24. Trouble Management System (TMS) • Ticket processing system (Remedy – COTS product) • Theater focused (e.g. STRATCOM) • Record planned and unplanned system component outages • INMS events impacting theater recorded and linked to INMS ID# Remedy

25. Circuit Alarm Processing • May generate proposed new events or extend existing open events • Based on filtering, matching, and auto-analysis rules • Parameterized to meet COI needs IF … THEN …

26. COI Event Work Queue • Work queue lists proposed new or appended events based on COI rule execution • Watch officers may take alternative actions against work queue entries • Selection of work queue button or link launches corresponding analysis reports • Selection of report button launches GADSS add or update event actions with prefilled data