1 / 38

JAIWG Data Federation Sub- Working Group Federation Planning Meeting

JAIWG Data Federation Sub- Working Group Federation Planning Meeting. IPR #7 April 16, 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. Agenda.

mproctor
Télécharger la présentation

JAIWG Data Federation Sub- Working Group Federation Planning Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JAIWG Data Federation Sub- Working Group Federation Planning Meeting IPR #7 April 16, 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

  2. Agenda • Review Old Business • Status Reports on Efforts • Web Service development • Enterprise Portal • Development Server • Results of GIG ISS Brief

  3. JAIWG Data Federation Sub Working Group Goal The ability to discover authoritative data in each federated repository in order to visualize, connect to or reuse that data. 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.

  4. Scope June 2009 Demo The scope is limited to an initial proof of concept demonstration to be conducted in June 2009. This proof of concept demonstration shall be conducted with two use cases: • Use Case 1 (Search, Discovery, Visualize): An anticipated user open an enterprise level dashboard/ web portal and connect to web service endpoints provided by the each of the following service providers: (MCAE), (JACAE), and (CADIE); search for specific data held by the service providers by conducting various queries of the data and generate reports based on integrated data query results in order to be able to display the following products in a standardized format: • Systems Information Threads (i.e. AFATDS) to include: • Nodes/Activities • System Functions (JCSFL)/Applications • System Information • System Interoperability • Use Case 2 (Horizontal Integration): An anticipated user identifies an architecture end point that horizontally integrates to other service providers and using a web service, moves across service providers to follow architecture data thread.

  5. Takeaways From Last Meeting • Provide XML schema to DM2 team to start work on DM2 alignment • Portal Page Storyboard Development • Update Storyboards for Use Cases • Set up location store for xml files • Develop interface to call and expose xmls • Use Case 2 • Decide on system • Position data for use • Test MCAE Laptop for feasibility as server

  6. Status Reports on Development Efforts • JHU-APL • Army • MC • JFCOM

  7. Use Case 1 Search, Discover, Visualize data in the federated repositories from a standardized portal interface

  8. Storyboard Use Case 1 • Enterprise interface leverages off of work already done • USMC Navigator • CADIE • JHU-APL work on JCSFL exposure

  9. Use Case 1 • Log into JAIWG Federation Web Page • User selects AFATDS system, repositories, and data types and activates search • Call System Query from JACAE • Execute web service to discover CADIE data • Call System Query from MCAE or executes web service (TBD) • Displays integrated data set from JACAE, CADIE, and MCAE in Federation Webpage

  10. AFATDS

  11. Use Case 2 Horizontally Integrated Mission Threads:Search, Discover, Visualize, data across the federated repositories from within a User’s Environment

  12. Use Case 2 • Log into JACAE • Locate AFATDS system in Catalog and execute menu command to search external data sources • Generate JACAE Thread Report and store as tab delimited file • Call Federation Webpage (JSP) and pass file location • Execute web service to discover CADIE data • Display integrated data set from JACAE and CADIE in Federation Webpage (JSP) • Provide option for user to download data of their choice in a specified format for reuse (not operable)

  13. AFATDS

  14. AFATDS

  15. AFATDS

  16. AFATDS

  17. AFATDS

  18. System Updates • Authentication • DKO/JKO use • Server Status • Cross-Domain Sharing

  19. Data Exchange Standard Questions • Is DM2 being mapped to UCore V 2.0? • What is the relationship of DM2 to BTA’s Common Core?

  20. Universal Core (UCore) (Interagency) Department of Defense Architecture Framework (DoDAF) MetaModel (DM2) (OASD/NII) Data Strategy & Architecture Dependencies Extended By Extended By DoD EA Summit ExtendedBy ExtendedBy DoD-DOJ DNI-DHS Intelligence Mission Area Warfighting Mission Area Business Mission Area Architecture Federation Web Services (Joint) Command and Control (C2) Core (Joint) Joint Architecture Integration WG (JAIWG) Cross-Walk Needed Common Core Cross-Walk Needed C2 Data Steering Committee Business Transformation Agency DoD Mission Areas

  21. Takeaways • Next Meeting May 5, 2009 1000-1200 • Army • JFCOM • JHU-APL • MC

  22. Backups

  23. Desired Outcome for June 2009 Demo • LTG Vane: • On track with his guidance/ showing progress to “Data standards” • MG Kennedy/Mr. Whitehead: • Architecture Data standards addressed. • USJFCOM J87 involvement • DDMS/GFMIED-M/C2-Core implications considered • Capabilities thread demonstrated w/ JCA, JCSFL, GCCS-J thread • OSD-NII: • DARS • Alignment with DM2/UCore • Leverage and build upon work already completed by Marine Corps, Army, JFCOM • Get USJFCOM, MC and Army in forefront of federation issues. • Advance our group toward Federation. • Advance DOD architectures toward Federation. • Attract other architecture data holders/developers to our ideas. • Identify governance shortfalls, conflicts and gaps

  24. Participants USJFCOM J89/J87* Army AIMD* Marine Corps MCSC* Johns Hopkins University Applied Physics Laboratory Siemens Government Services ASD(NII)/DoD-CIO DoDAF MetaModel (DM2) Team Advisory Defense Architecture Registry System User Group Federated Joint Architecture Working Group Department of Defense Architecture Framework Core Management Group USJFCOM J3/4 Force Management Improvement Program Architecture Team Federation Sub-WG Members Navy RDA-CHENG Mission Architecture IPT representative sits on SWG meetings Air Force Aeronautical System Center (Wright Patterson) engaged with J89 to become participant post June 2009 demo * Indicates data repositories to be used for Proof of Concept Demonstration

  25. Technical Requirements • Use Citrix box located at JFCOM for access authentication services • Use current JACAE Application server to host presentation server data (Enterprise Portal) Apache Tomcat • For proof of concept demonstration will use consumer services to directly connect to service provider endpoints. • Future development, once impact on system performance and speed is assessed, may require use of caching/Master Data Management.

  26. Attendees

  27. Federation Pilot Concept Data Consumer Architect • User Searches for Data • Directory Service Returns Search Results from Registered Services to User • User Connects to Service Provider Through Data Translation Services • Service Provider Authenticates User and Returns Data to User (Use DKO/JKO) • User Displays Required Data Web Service Interface Search Discover Retrieve Data AV 1 ' s DARS

  28. Vision Implementation

  29. Project Governance Local Policies and Guidance Security Available Resources and Capabilities Infrastructure Requirements Staffing Level to support Level of Risk Return on Investment (ROI) Measurement and Data Quality Communication Training Configuration Control Interdependency on Other Organizations Legal Issues? Organizational Considerations

  30. Data Security Data Latency Source Data Volatility Data Consistency and Quality Data Availability Impact of Model Changes Frequency of Transactions Transaction Occurrence (Concurrent Users) Performance with regards to Transaction Processing times Create – Read – Update – Delete or Read Only? Data Volume per Transaction Delivery Time Skill Set and Experience of Users Reusability of Data Cost of Development Cost of Maintenance Target Model definition Assured Delivery Requirements Resource Utilization Transformation Interfaces Source Models, Interfaces, adaptors, protocols Scope/Size of source model (how many mappings to the integrated view need to be created) Impact of Federation Server on Local Services Technical Considerations

  31. Timeline • 20 Nov 2008: JKO Portal site established https://www.us.army.mil/suite/page/596533 • 20 Nov-10 Dec 2008: Derive requirements from documents • 10 Dec 2008: Tech WG meeting to discuss group requirements. • 12 Dec 2008: AIMD demo • 17 Dec 2008: Tech WG to develop plan, OV-1, goals etc. • 14 Jan 2009: Tech WG Meeting • 21 Jan 2009: OSD-NII Brian W; LTG Vane brief • 29 Jan 2009: DM2 Discussions with OSD-NII DM2 Developers • 05 Feb 2009: JAIWG Brief • 12 Feb 2009: Tech WG Meeting • 05 Mar 2009: Tech WG Meeting • 26 Mar 2009: Tech WG Meeting • 15 Apr 2009 GIG ISS Brief • TBD: Pre demo to JAIWG (may be moved to post demo) • June 1-4, 2009: DoD EA Conference • ??? FJAWG Brief

More Related