1 / 9

Architecture Federation Update Ms. Takai DOD CIO 6 February 2012

Architecture Federation Update Ms. Takai DOD CIO 6 February 2012. Intent. Purpose

akimbrough
Download Presentation

Architecture Federation Update Ms. Takai DOD CIO 6 February 2012

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. Architecture Federation UpdateMs. TakaiDOD CIO6 February 2012

  2. Intent • Purpose • Establish an architecture federation supporting enterprise wide architecture data sharing and reuse enabling architectural analysis in order to focus resource investment on specific capability gaps required to procedurally and technically implement IT Enterprise solutions while meeting prioritized Warfighter requirements. • Method • Create and execute a POA&M outlining specific activities with definitive suspense's utilizing a “crawl, walk, run” approach facilitating IT Enterprise business model solutions using FMN as a “pacing item.” • Endstate • An executable DOD pathway to IT Enterprise solutions enabling secure data and information exchange horizontally and vertically across all mission areas, EIE and JIE (GIG).

  3. Reference Models Tech Stds Arch Guidance Laws, Regs, and Policy OMB FEA Tools DODAF Laws Regs Policy DISR DARS DITPR Solution Architectures Army DON Air Force The Joint Warfighting Mission Area The Architecture Federation effort enables the foundational capability to federate architecture DATA by: Business Warfighting Intelligence Enterprise Information Environment Dept of Air Force DISA DIA NGA NRO NSA DLA COCOMS Other Architecture Federation aligns to the IT Effectiveness effort and DoD EA Guidance and Vision Enabling discovery, accessibility and reuse of Joint Reference Architectures for all capability development and acquisition activities Exposure and reuse of JCIDS Architecture data to support AoA and DCR analysis and solution development Mission Thread and Architectural analysis informs cost, schedule, and performance trade off decisions relative to operational risk determination and mitigation decisions Leverage Component willingness to share approved integrated architecture products

  4. Architectural Analysis Example Architectures leveraged for Nunn-McCurdy Breach Analysis on JTRS GMR Architectural analysis identified operational risks and performance tradeoffs Discussions ultimately focused at enhancing joint and coalition interoperability • Analysis of JTRS GMR JCIDS documents and Information Support Plans (ISPs) indicated concerns with lack of technical standards, joint common systems functions, and dated capabilities • C2 On-the-Move (C2OTM) Reference Architecture identified capabilities, services, and standards for JTRS GMR • Tactical Information Classification Security (TICS) Solution Architectures and analysis (JROCM 184-09) provided Information Exchanges and Systems Data Throughput used for JTRS GMR analysis • RESULT: AT&L cancels JTRS GMR in favor of NDI solution

  5. Way Ahead Aggressively Attack and Execute!!! • Achieve success through phased development and iterative “wins” with WMA and FMN directed efforts as “pacing item” • Crawl phase: 30 Days • Analyze problem space, scope effort, create POA&M • Conduct technical assessment and feasibility • Walk phase: 90 to 120 Days • Commence WMA (FMN) and EIE architecture data sharing and integration • Capture and incorporate technical, procedural, and governance “lessons learned” • Run Phase: 150 until complete • Apply “lessons learned” through WMA (FMN) development • Horizontally and vertically share architectural data across all mission areas, the EIE and JIE (GIG)

  6. Summary • Architecture Federation processes directly support DoD IT Enterprise Effectiveness development by promoting reuse, cost savings, and access for portfolio and cross portfolio analysis • Federation requires DoD CIO guidance, policy, authority and enforcement • Partnering effectively uses existing, limited resources to achieve federation objectives while exploiting lessons learned and products already developed • Continued collaboration with DoD CIO critical to achieving the vision of Architecture Federation supporting the entire DoD Enterprise Carpe Diem!

  7. BackupSlides

  8. Architecture Federation Resource RequirementPost-Transition Scope (WMA Only)Dec 2011

  9. Challenges to Implementing a Federated DoD EA

More Related