1 / 44

Walt Okon Senior Architect Engineer for Standards Architecture and Interoperability Directorate

Walt Okon Senior Architect Engineer for Standards Architecture and Interoperability Directorate Deputy Assistant Secretary of Defense for Information Management, Integration, and Technology & DoD Deputy Chief Information Officer (703) 607- 0502 . walt.okon@osd.mil.

ronat
Download Presentation

Walt Okon Senior Architect Engineer for Standards Architecture and Interoperability Directorate

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. Walt Okon Senior Architect Engineer for Standards Architecture and Interoperability Directorate Deputy Assistant Secretary of Defense for Information Management, Integration, and Technology & DoD Deputy Chief Information Officer (703) 607- 0502 . walt.okon@osd.mil DoDAF Delivering Architectures to the WorldPresentation to GTRA Architecture GOV Symposium07 December 2008

  2. Strategy and Direction Discussions: • DoDAF Version 2.0 • Architecture Training - Architects Competencies • DoDAF Metamodel • “Fit for Purpose” Architecture • Defense-Industry Challenge – DoDAF + MODAF = UPDM • DoD IT Standards Registry (DISR) • IC & DoD IT Standards Integration • DoD GIG Technical Guidance (GTG) • Architects Career Path, Competencies & Certifications • DoD Information Sharing Environment

  3. Key Policies Requiring DoDAF Joint Staff • CJCSI 3170.01F, 1 MAY 2007, “JOINT CAPABILITIES INTEGRATION AND DEVELOPMENT SYSTEM” • CJCSM 3170.01C, 1 MAY 2007, “OPERATION OF THE JOINT CAPABILITIES INTEGRATION AND DEVELOPMENT SYSTEM” • CJCSI 6212.01D, 8 MAR 2006, “INTEROPERABILITY AND SUPPORTABILITY OF INFORMATION TECHNOLOGY AND NATIONAL SECURITY SYSTEMS” Direct support for the Warfighter

  4. (Published in 2003) (Published in 2007) DoDAF Evolution To Support “Fit For Purpose” Architecture • DoDAF 1.0 • CADM Separate • Baseline For DoDAF 1.5 • Removed Essential & Supporting Designations • Expanded audience to all of DoD • DoDAF 1.5 • Addresses Net-Centricity • Volume III is CADM & • Architecture Data Strategy • Addresses Architecture Federation • Baseline for DoDAF 2.0 • Shifted away from DoDAF mandating • a set of products • DoDAF 2.0 • Cover Enterprise and • Program Architecture • Emphasize Data versus • Products • Tailored Presentation • AV-1 to capture federation • metadata • Quality Support to Decision • Processes • FEA & Allied/Coalition • Support • Journal • - Errata & Interim Releases DoDAF 2.0 (To Be Published) (Late 2008)

  5. Architecture Views DoD Core Decision Processes FederatedArchitectures PPBE/PfM Cost View Capability View SE View Acquisitionetc. E JCIDS M DOTLMPF “Fit for Purpose” Acquisition C P Systems Eng E – Enterprise M – Mission Area C – DoD Component P - Program Governance Link Technology to Objectives Institutionalize IT Best Practices Protect digital assets Architecture IT Technology Focused on DoD Decisions

  6. Fit For Purpose Presentation Dashboards Fusion Products Reference Models Composite Products Graphical Depictions All View All AVs All “Systems” Versions of SV Products Systems View All TVs Standards View All “Service” Versions of SV Products Net-Centric View SV-11 OV-7 Rest of OVs Data & Information View Operational View Capability View System Engineering View Project View DoDAF Metamodel (DM2) Updated Moved New DoDAF V2.0 DoDAF V1.5

  7. Capability Viewpoint Articulate the capability requirement, delivery timing, and deployed capability Operational Viewpoint Articulate operational scenarios, processes, activities & requirements Project Viewpoint Describes the relationships between operational and capability requirements and the various projects being implemented; Details dependencies between capability management and the Defense Acquisition System process. Standards Viewpoint Articulate applicable Operational, Business, Technical, and Industry policy, standards, guidance, constraints, and forecasts Data and Information Viewpoint Articulate the data relationships and alignment structures in the architecture content All Viewpoint Overarching aspects of architecture context that relate to all views Services Viewpoint Articulate the performers, activities, services, and their exchanges providing for, or supporting, DoD functions Systems Viewpoint Articulate the legacy systems or independent systems, their composition, interconnectivity, and context providing for, or supporting, DoD functions DoDAF 2.0 Viewpoints 7

  8. Vision Statement To enable the development of architectures that are meaningful, useful, and relevant to the DoD Requirements, Planning, Budgeting, Systems Engineering, and Acquisition decision processes.

  9. DoDAF Metamodel

  10. DoDAF Conceptual Model

  11. “Fit for Purpose” Architecture Descriptions

  12. EA Conf 14-19 Apr Develop Writing Technical Editing Plenary 1 Apr Plenary 22 July Vwendor Tool Session Cood Validation EA Summit 23 Jan 08 PfM WS PPBE WS Feb 08 SPIRAL III 27 Jun 08 SPIRAL II 4 Apr 08 Notional DoDAF v2.0 Development Schedule (cont) 2nd QTR 08 3rd QTR 08 4th QTR 08 Feb Mar Apr May Jul Aug Sep Oct Jun Nov DoD CIO Approval Post to DARS SPIRAL IV 12 Sep 08 Phase I Phase II Phase III

  13. DODAF Version 2.0 in Coordination • Core Management Group - 10 December 2008 • Discuss DoDAF Version 2 Spiral 4 Draft. • Comment and adjudication • Next Step: OSD NII Informal coordination • Comment and adjudication • EA Summit – Services, Agencies, and COCOMs • DoD Executive Coordination Committee

  14. Register Provider View Provider Update Provider Register Metadata Search Holdings Metadata Registration Service Federation Client Services Menu DARS Federation Web Services DARS Federated Catalog SOAP DDMS + Metadata (XML) AV-1 metadata captured and extracted by repository/tool environment Federation Web services Federation Client Federation Repository Repository/Tool Environment

  15. DoD Architecture Federation DIA NGA NRO NSA DLA DISA Other DoD Enterprise Architecture Tools Ref Models Tech Stds Arch Guidance Laws, Regs, and Policy DITPR DoD EA RM DISR DODAF Laws Regs Policy Force Application TAMD Building Partnerships Joint Capability Areas Command & Control GLOBAL C2 JC2 COMMS & Transport Net-centric IEA Battlespace Awareness IA Architecture BEA Protection Logistics JDDA MS&SM Force Support RP&ILM HRM HRM Architecture Corporate Management & Support FM WSLM Dept of Army Dept of Navy Dept of Air Force Army Architecture DON Architecture Air Force Architecture Solution Architectures

  16. Defense-Industry Challenge: Synchronization of DoDAF-UPDM Lifecycles 2. Industry Produces Develops Generic Modeling & Engineering Standards • Governments • Produce Baselines • Develop, Evolve & • Harmonize • Defense Enterprise • Architecture • Frameworks • For Acquisition RFC 3. Vendors Produce Product Versions Defense Domain Tools “Just-In-Time” Leverages Vendors Standards- Based Tools & Government Frameworks

  17. UPDM – Unified Profile for DoDAF/MODAF UPDM RFC Group Lockheed Martin Co Mitre MOD No Magic Raytheon Rolls Royce Sparx Systems VisumPoint Adaptive Artisan Software ASMG BAE Systems DoD embeddedPlus Generic

  18. UPDM in General UPDM DNDAF DoDAF 1.5 MODAF 1.2 NAF UPDM is an OMG initiative to develop a modeling standard that supports both the USA Department of Defense Architecture Framework (DoDAF) and the UK Ministry of Defence Architecture Framework (MODAF) • Significantly enhance the quality, productivity, and effectiveness of architecture modeling • Promote architecture model reuse and maintainability • Improve tool interoperability and communications between stakeholders • Reduce training impacts due to different tool implementations and semantics • Improve the integration between system of systems modeling and system modeling to support post acquisition life cycle design modeling The UPDM Group was setup to:

  19. Motivation Significantly enhance the quality, productivity, and effectiveness associated with enterprise and system of systems architecture modeling, promote architecture model reuse and maintainability, improve tool interoperability and communications between stakeholders, and reduce training impacts due to different tool implementations and semantics. Improve the integration between system of systems modeling and system modeling to support post acquisition life cycle design modeling. UPDM fully supported by DoD, MOD, IDEAS Statement and slides available on OMG website Need for UPDM

  20. Federated ArchitecturesThe Connection

  21. What the Operator Sees Today

  22. What the Operator Expects to See

  23. A Federation of Data Producers Federation Strategy Reporting (OMB, GAO, etc) DARS DoD EA Reference Models • CADM • DoDAF • NCOW RM MILDEP COCOM AGENCY COI x COI y DATA REQTS. • COI = Community of Interest • CADM = Core Architecture Data Model • DoDAF = DoD Architecture Framework • NCOW RM – Net-Centric Operations & Warfare Reference Model • UPDM = UML Profile DoDAF & MODAF DoD Decision Processes

  24. DoD EA Federation Strategy Available on DARS Website: https://dars1.army.mil/IER/index.jsp

  25. DoD EA Federation Pilot Use • BTA/USTRANSCOM/Marine Corps: • Federate the BEA with JDDA and Marine Corps Logistic architectures and register in DARS to gain visibility into “end to end” logistics process • Army: • Create a “knowledge base” through architecture federation for Army communities. • Test tools and concepts through federation, i.e. social networking (ontology development, semantic indexing,) architecture data analysis, UPDM applicability • Air Force: • Establish interface and search capability between DARS and AFARS. Demonstrate search capability • Navy: • Implement and use procedures outlined in the GIG Enterprise Architecture Federation Strategy and DARS CONOPS to create a repeatable federation process • Joint Staff/J6I: • Identify interface points and alignment between Mission Area-level architectures to obtain enable a horizontal view across mission areas and drill down to Program level. • DARS: • Develop registration template for AV-1 and DDMS metadata

  26. DoD IT Standards Registry (DISR)IC/DoD IT Standards Registry

  27. DoD Sponsored Policy DoDI 4630.8 CJCSI 6212.01D DoDI 4630.8 DoDD 5000.1 CJCSI 3170.01C CJCSM 3170.01 • Maintain OASD(NII) JCIDS/ISP Assessment Capability(JCPAT-E Tool) • Maintain IT Standards and Profiles(DISRonline) • Certify Standards Conformance • ITS and NSS Interoperability Requirements Certification • Assessments of NR-KPP in JCIDS Docs • JCIDS Documents (ICD, CDD, CPD) ACAT I - III & Special Interest • J6 Interoperability Requirements Certification of All JCIDS Docs (JCPAT-E Tool) • ITS & NSS Predecessor Doc. System Profile Requirement • - IT Standards Profile (DISRonline) • - IIC Profile (LISI) JCPAT KM/DS JCPAT JCPAT JCPAT Joint Staff J-8 Joint Staff J-6 OASD(NII) Joint Staff J-6 Interoperability Requirements Certification Process JROC FCB J6 J6I JCPAT-E Interoperability Requirements Stage I, II & III ITS & NSS Certification Assessments Registration DISR Online JCPAT = = • • UAM / JCPAT- E System Registration LISI InspeQtor JCPAT JCPAT Technical View (CDD & CPD) • • JCPAT Interoperability & Interconnectivity Profile (CDD & CPD) • IT and NSS Interoperability and SupportabilityPolicy and Process Overview

  28. Objectives: Champion DoD’sRe-Engagement of the IT Standards Communities Online IT standards Registry Tri-Annual Update of IT Standards Registry Tied to JCIDS IT Standards Conformance and Compliance Process Intelligence Community Cross Coordination (ICSR) Improved DoD Visibility and Participation in IT Standards Development Organizations Develop and Register PM Standards Profiles (TV) Standing IT Standards Working Groups Aligned to GIG Portfolio Management Governance and General Information Area Policy FAQs CM Procedures User Guides Links SOP POCs Change Request Tool Software Voting Tool Software Collaboration Tool Software Profile Assistance Software Future Enhancements GIG Mission Area Management DISR Profile Registry Area Organization-Unique Bins - - - - - - - - - - Information / Guidance (I/G) Informational Standards Best Practices Procedures Policies Manuals Handbooks Other IT Documents PM System IT Standards Profiles TVs * Prescribed Technology Profiles * (IPv6, PKI etc.) Key Interface Profiles * (KIPs) DISR Mandated Standards Mandated “Net-Centric” & Mandated Sunset “Interoperability” Standards DoD IT Standards Registry (DISRonline) Lifecycle Tagged: Emerging and Retired Standards * May Contain Standards from Lifecycle Categories other than Mandated DISR and DISRonline Architecture View

  29. Lifecycle of a Standard • Emerging • Upgradeability Should be a Concern • May be Implemented but Not in Lieu of Mandated Standard • Expected to be Mandated within Three Years • Mandated • Essential for Interoperability and Net-Centric Services in DoD • Minimum Set of Essential Standards for the Acquisition of All DoD Systems that Produce, Use, or Exchange Info, and, When Implemented, Facilitates the Flow of Info in Support of Warfighter • Sunset Tag Identifies an Event and Date to Retire a Standard • Inactive / Retired • New Standards / Technology Now Available and Implemented • Require Waiver and Migration Plan • Remain in the Registry

  30. IT Standards Governance Organization Membership Technical Working Groups

  31. DoD GIG Technical Guidance (GTG) Walt Okon

  32. Capability Development Areas Structured and Unstructured Sources for Standards and Specifications (Notional) Mission Area Portfolios Standards Specifications DISR Query & Retrieve NCID Capability DARS Joint Capability Areas Standards Specifications GIG Technical Guidance DKO CADM Standards & Specifications For Interoperability 4630 Identified Interoperability Standard, Specifications, And Interfaces Detailed Interoperability Standards & Specifications Information 80XX GIG Governance Processes Standards Specifications XML Metadata Registry SFIS Taxonomy Community Of Interest Standards Specifications . . . DoD Technical Guidance Concept Technical Direction Query Technical Direction Query XML Schemas/ Components

  33. Architects Career Path Architects Competencies Architects Certifications

  34. IMPROVING DOD’S ARCHITECTURE • Guidance • DoDAF v2.0 • Federated Architecture Strategy • Tools • DoD Architecture Registry System (DARS) • DoD IT Standards Registry (DISR) • Type II – GIG Technical Direction • Education and Training • DoD Architecture Training Effort All this is nothing without Certified Architects!

  35. ARCHITECTURE TRAINING • Expanded need for architectures and their significance in achieving defense of our nation results in the need for qualified architects • Therefore, we are confronted with questions: • Is there a pool of qualified architects? • What are the competencies of an architect? • Is there a core body of knowledge? • What education and training courses exist? • DoD– IT Architects Career Path–Architects Series

  36. RECOMMENDED WAY AHEAD • Deliver an architect career plan • Establish architecture specialties in Office of Personnel Management (OPM) • Formalize a competency framework • Implement Certificates & Certification across architecture specialties • Work with academic and educational institutions to enhance their curricula

  37. ACCOMPLISHMENTS • WHITE PAPER - Phase I: A Competency Framework • Defines a path for a quality architecture workforce • Provides collected data on the competencies of an architect • https://www.us.army.mil/suite/doc/10757012 • Architecture Education and Training DKO Site • OPM Job Family Standard Review • Clinger-Cohen Core Competency Review for Architecture • Delivered two Architecture Training Tutorials at 2008 EA Conference

  38. DoD Information Sharing Environment Walt Okon Chief Architect, DoD Information Sharing Architecture & Interoperability Directorate Office of the DoD CIO/ASD NII

  39. Counter Terrorism Terrorist Actions Warfighter Operations Natural Disasters Humanitarian Operations Northeast PowerBlackout Pandemic Flu Coalition Operations Failed States (Haiti) Complexities of Information Sharing DoD is part of this complex, extended information sharing enterprise…

  40. DoD Information Sharing Environment Description: – Provide a DoD Information Sharing architecture and standards capability which will support cross-community, institutional approach to the sharing of information within DoD and can apply across Federal Departments, state, and local governments – Provide architecture and engineering guidance for DoD Information Sharing Executive and DoD Information Sharing – Provide PM-ISE DoD’s Shared Space architecture and standard guidance to enable cross-community sharing for identifying, planning, installing, and operating capabilities that will become the ISE.

  41. DoD Information Sharing Environment • FY08 Key Taskings: – PM-ISE Chief Architect Roundtable and the CTISS Committee – Design and deliver a CTISS Federated Standards Registry pilot – Develop a DoD ISE Shared Space use case and concept capabilities with Net-Centric direction – Partner with other ISE architects in the Federal Departments – Partnership with DISA on analysis and engineering.

  42. Bring It All Together DoD Enterprise Architecture Conference 2009

  43. DoD Enterprise Architecture Conference 2009 • DoD Enterprise Architecture Conference • All DoD Architecture Professionals • Only official Architecture Conference • Enterprise Architecture & Standards • Deliver Interoperability • 1 – 5 June 2009; DoD Enterprise Architecture Conference 2009 in St Louis, MO • Deliverables http://www.afei.org/brochure/9a05/index.cfm

  44. Questions/Wrap-Up Walt Okon Chief Architect, DoD Information Sharing Enterprise Architecture & Standards Directorate Office of the DoD CIO/ASD NII 07 December 2008 • walt.okon@osd.mil • 703-607-0502

More Related