UNCLASS JAIWG Data Federation Sub-Working Group Planning Meeting

UNCLASS JAIWG Data Federation Sub-Working Group Planning Meeting Phase 2 Mtg #3 September 3, 2009 Use following Teleconference Numbers for Voice. Telcon for voice Phone # 877 -714 -4577 Pass code: 2692256 Slides on JKO Portal https: //www. us. army. mil/suite/page/596533 1 UNCLASS

UNCLASS Agenda • Portal Design Requirements • Phases to Development • Meeting Schedule 2 UNCLASS

UNCLASS Federation Partners • Current Partners: – – – JACAE (USJFCOM) MCAE (MCSC) CADIE (Army TRADOC/AIMD) AFMC (AF Wright-Patterson) SADIE (Navy) • JFCOM Internal/JACAE Users – JCCD, J 892, JTF – J 7, J 9, JTC-I, J 3/4, J 6 – STRATCOM, CENTCOM, USFK • Potential External Architecture Development Environments – JIAMDO – JPEO-CPD – TRANSCOM J 6 • Knowledge Sources – – ADS Registry DISR JCAMS/UJTL Database C 2 -Pedia/Registry? • Other Architecture Information Sources – – – DARS** (OASD-NII/CIO) NARS** (Navy) MCASE** (MC) NAERG (Navy) E-ISP (OASD-NII/CIO) 3 UNCLASS

UNCLASS Website Planning The absolute basics we all need to know before starting portal development 4 UNCLASS

UNCLASS The Process • • • Determine the goal of the portal Identify the Standards Organize the basic structure Create the Design (look and feel) Plan and Gather Assets 5 UNCLASS

UNCLASS Goals of Portal (Critical Customer Needs) • Federation Catalog of Reusable Architecture Objects (including JCSFL) • Discoverability of Federated Architecture Products • Authoritative Library Sources • Links to other important sources • Link for access to JACAE • Customized reports to support decision makers • Others? ? ? 6 UNCLASS

UNCLASS Standards • We must meet current and emerging standards i. e. : – PKI (NIPR)/DKO/JKO Pass Through – Browser compatibility – CSS • Web 2. 0 Technologies • Accessibility 7 UNCLASS

UNCLASS Organize • USER-CENTERED DESIGN • Level 0 – What is critical to be on the home page • Level 1 – Most important, frequently used information that can be accessed in 1 click • Level 2+ – Layers of depth in priority/customer need 8 UNCLASS

UNCLASS Organize • Organize by categories of information • Flowchart out moving through the portal • Do we need a News Feed/Blog/Wiki (Web 2. 0)? • Plan for Phases of implementation – What do we need to have now? – In 6 months? – 1 year? – Long-Term? 9 UNCLASS

UNCLASS Design • Same look and feel across pages • Transition from portal should be almost seamless • Consistent (Same buttons in same locations on all pages) • User Friendly – Visitors need to know where they are in the navigation – Search Features readily available – Feedback button in case errors are detected or questions 10 UNCLASS

UNCLASS Plan and Gather • Already started • Need to have location to gather and CM all information for portal 11 UNCLASS

UNCLASS Other Considerations • Design Document is critical to ensure scope and purpose are clearly defined (and for reuse) • Maintenance of the Portal and Content • Plans for Back-Ups • Contact/About Us/Leadership Pages • Sizing? 1124/768 or 800/600 etc… • Speed of Loading 12 UNCLASS

UNCLASS 13 UNCLASS

UNCLASS 14 UNCLASS

UNCLASS Phase 1 November 2009 15 UNCLASS

UNCLASS Task 1 • List of Architecture Development Efforts and Associated Products – Collect Information – Develop User Interface/Matrix (Front-End) Requirements – Back End Requirements (Web Service or Static View? ) 16 UNCLASS

UNCLASS Task 2 • Catalog of Reusable Architecture Elements • JFCOM – Key Elements of Capability Mapping Baseline and associated mappings – JTF Templates • • Army MC Navy (NAERG) Air Force 17 UNCLASS

UNCLASS Deliverables September 1, 2009 • Documentation – CONOPS/Business Plan-Include plans for future development spirals • • System Requirements Documentation (Draft) Configuration Management Plan (Draft) Data Management Strategy (Draft) Action Plan to accomplish each deliverable • Comprehensive List of Architecture Development Efforts and associated architecture products held in each repository • Storyboard of Portal Interface for accessing Architecture Products and Catalog/Rough Working Model (Use Cases for Portal Interface) 18 UNCLASS

UNCLASS Deliverables November 15, 2009 • Automated DARS registration of AV-1’s contained in the federated repositories** • Standardized interface (portal) for viewing federated data • Joint Standard for sharing system information in the federated environment – Data under Configuration Management – Authoritative Source Traceability • Data Model and XSD’s publication – DM 2 mapping and information exchange standard implementation commenced – Web Services • Use of NCES messaging and security services – Pass through authentication using DKO – Meet all Information Assurance Guidelines 19 UNCLASS

UNCLASS Other Milestones • Federation with: – Navy Sources: SADIE/NAERG/NARS – DISR – ADS Registry 20 UNCLASS

UNCLASS Takeaways • All – Architecture Projects, Products Available, Location • Army • JFCOM/JHU-APL – ? ? • MC – ? ? • OASD-NII – ? ? 21 UNCLASS

UNCLASS Backups 22 UNCLASS

UNCLASS Goals, Objectives, Tasks 23 UNCLASS

UNCLASS The Goals • Establish the capability to discover authoritative data in federated Joint/Service repositories in order to access, visualize, and use/reuse the data in support of the Warfighter (our original goal). • Provide the necessary framework, standards and governance for a federated, joint, architecture information sharing and development environment by adhering to the principles contained in the Do. D Information Sharing Strategy. • Become a key contributing factor for Joint Architecture Excellence in support of development of Joint, Interoperable, Capability Solutions • Leverage partnerships with mature Do. D architecture development efforts in order to maximize use of existing resources. 24 UNCLASS

UNCLASS Objectives • Assist decision makers across the Do. D by providing the ability to search, discover and visualize integrated, authoritative data and products from a secure, Joint/Service federated environment in support of Warfighter capability development. • Provide a secure, federated Joint/Service repository of reusable architecture products and reports to enable architecture developers to improve speed of development, reduce or eliminate duplication of effort, and create more efficient, collaborative architecture development and analysis processes in support of developing Joint, interoperable solutions for the Warfighter. • Provide a common infrastructure that is agile, scalable and reusable so that other architecture development efforts can easily integrate into the federation. • Reduce resource requirements through use/reuse of already existing technical expertise and previously developed architecture products and services. 25 UNCLASS

Capability Mapping Baseline UNCLASS “Periodic Table” for Operational DOTMLPF-P Analysis Architectures Joint Capability Areas (JCAs) Systems Functions Joint Common System Functions List (JCSFL) USN USMC USAF NCES/NECC Other CPMs JCAs Technical C 2 Portfolio* - Programs of Record - Systems - Sub-systems - New Capabilities Operational Activities Standards Policy Standards Analysis Tier I Joint Staff J 7 Mapping CPM Areas Policy Accreditations Policy Standards Policy Platforms/Weapons Standards ADS & Data Models Applications/Services Policy Standards Policy UJTL SN X. X ST X. XX OP X. X. X TA X. X Networks/Comms JTF Operational Activities / Tasks / Sub-tasks Assessments Joint Tasks Operational AUTLs, MCTL, NTTL, AFTL Service Tasks Op Nodes Authoritative Sources: UNCLASS Joint Warfighter Billets Policy Standards Documentation Concepts/Plans Operational Nodes & Billets Standards Programmatic Policy Standards JCAs- to- PECs PA&E Mapping JCAs Joint Integration & Interoperability Recommendations via Detailed 26 DOTMLPF Analysis

UNCLASS 27 UNCLASS

UNCLASS Timeline • Phase 1 – November 2009 – Matrix of Architecture Products – First Phase Reusable Catalog of Joint Architecture Elements linked to Service Architecture Elements • Phase 2 – May 2010 (EA Conference) – Integrated (Dare I say Federated? ) Architecture Products and Reports • Use Cases include JAIMDO and JCAS 28 UNCLASS

UNCLASS Phase 2 May 2010 29 UNCLASS

UNCLASS Use Cases • AV-1 • AV-2 • Desired Outcome: Traceability through Architecture Products developed in various environments 30 UNCLASS

UNCLASS Timeline - Milestones Sep 09 Documentation Nov 09 Phase 1 Tasking Completed May 10 Phase 2 Tasking Completed 2010 EA Conference 31 UNCLASS

UNCLASS Deliverables September 15, 2009 • AV-1 for Use Cases for Integration (May 2010) 32 UNCLASS