Presentation on theme: "DoDAF Delivering Architectures to the World"— Presentation transcript:
1 DoDAF Delivering Architectures to the World DoDAF Delivering Architectures to the World Presentation to GTRA Architecture GOV Symposium 07 December 2008Walt OkonSenior Architect Engineer for StandardsArchitecture and Interoperability DirectorateDeputy Assistant Secretary of Defense for Information Management, Integration, and Technology & DoD Deputy Chief Information Officer(703)
2 Strategy and Direction Discussions:DoDAF Version 2.0Architecture Training - Architects CompetenciesDoDAF Metamodel“Fit for Purpose” ArchitectureDefense-Industry Challenge – DoDAF + MODAF = UPDMDoD IT Standards Registry (DISR)IC & DoD IT Standards IntegrationDoD GIG Technical Guidance (GTG)Architects Career Path, Competencies & CertificationsDoD Information Sharing Environment
3 Key Policies Requiring DoDAF Joint StaffCJCSI F, 1 MAY 2007, “JOINT CAPABILITIES INTEGRATION AND DEVELOPMENT SYSTEM”CJCSM C, 1 MAY 2007, “OPERATION OF THE JOINT CAPABILITIES INTEGRATION AND DEVELOPMENT SYSTEM”CJCSI D, 8 MAR 2006, “INTEROPERABILITY AND SUPPORTABILITY OF INFORMATION TECHNOLOGY AND NATIONAL SECURITY SYSTEMS”Direct support for the Warfighter
4 DoDAF Evolution To Support “Fit For Purpose” Architecture CADM SeparateBaseline For DoDAF 1.5Removed Essential & Supporting DesignationsExpanded audience to all of DoD(Published in 2003)DoDAF 1.5Addresses Net-CentricityVolume III is CADM &Architecture Data StrategyAddresses Architecture FederationBaseline for DoDAF 2.0Shifted away from DoDAF mandatinga set of products(Published in 2007)DoDAF 2.0Cover Enterprise andProgram ArchitectureEmphasize Data versusProductsTailored PresentationAV-1 to capture federationmetadataQuality Support to DecisionProcessesFEA & Allied/CoalitionSupportJournal- Errata & Interim ReleasesDoDAF2.0(To Be Published)(Late 2008)
5 Focused on DoD Decisions Cost ViewCapability ViewSE ViewAcquisition etc.ArchitectureViews“Fit for Purpose”DoD Core Decision ProcessesPPBE/PfMJCIDSDOTLMPFAcquisitionSystems EngMCEPFederated ArchitecturesE – EnterpriseM – Mission AreaC – DoD ComponentP - ProgramArchitectureITTechnologyGovernanceLink Technology to ObjectivesInstitutionalize IT Best PracticesProtect digital assets
6 DoDAF V2.0 DoDAF Metamodel (DM2) Fit ForPurposePresentationDashboardsGraphicalDepictionsReferenceModelsFusionProductsCompositeDoDAF V2.0DoDAF V1.5StandardsViewOperationalRest of OVsAll TVsAllAll AVsSystemsViewAll “Systems”Versions ofSV ProductsData &InformationViewOV-7Net-CentricSV-11All “Service”Versions ofSV ProductsDoDAF Metamodel (DM2)DoDAF 2.0 is a more focused approach to supporting decision makers than prior versions.In the past the decision maker would look at DoDAF offerings and decide which were appropriate to their decision process. An example is the JCIDS process architecture requirements inside their documentation (IDC, CDD, CPD, etc.).Additionally, older version architecture description products were “hard-coded,” so to speak, as to content and how they were visualized. Many times this lead to a lack of understanding and usefulness for the intended audience.DoDAF 2.0, based on process owner input, increased focus on architecture data, and a new approach for presenting architecture information has addressed the issues.BUILD ONE:The original views (OV, SV,TV, AV) have had their content reorganized to better address their purposeThe Services portion of the older “Systems and Services” view is now a net-centric view that addresses in more detail our net-centric or services oriented implementationsAll of the views of data, be they conceptual, logical, or physical, have been place in one view rather than spread out through all of the views.BUILD TWO:The new Systems view better accommodates our legacy system descriptions.The new Standards view can now describe technical, business, and commercial standards applicable to our systems and services.The operational view now can describe rules and constraints for any function (business, intelligence, warfighting, etc.) rather that just those derived from data relationships.The standards view also now contains standards that can be applied from a technical, business, doctrinal, or commercial perspective.BUILD THREE:The emphasis within the Department on Capability Portfolio Management and feedback from the Acquisition community, the Capability and Project Views have been added through a “best of breed” analysis of the MODAF and NAF constructs for both.Workshops with the Systems Engineering community have brought them and the architecture community closer together on defining the DoDAF architecture content that would be useful to the Systems Engineering process and has resulted in a new Systems Engineering View.There is also a approach to the presentation of architecture description content that moves away from analytic and narrowly focused architect portrayals for architects. The term we have coined (stolen from the Air Force) is “fit for purpose” presentation. Through various techniques and applications, the presentation of architecture description data will increase customer understanding and architecture’s usefulness to decision making by putting the data underlying the architectural models into the context of the problem space for each decision maker.CapabilityViewProjectSystemEngineeringNewUpdatedMoved
7 DoDAF 2.0 Viewpoints Capability Viewpoint Operational Viewpoint VERSION 154/15/ :47DoDAF 2.0 ViewpointsOverarching aspects of architecture context that relate to all viewsAll ViewpointArticulate the data relationships and alignment structures in the architecture contentData and Information ViewpointArticulate applicable Operational, Business, Technical, and Industry policy, standards, guidance, constraints, and forecastsStandards ViewpointSystems ViewpointArticulate the legacy systems or independent systems, their composition, interconnectivity, and context providing for, or supporting, DoD functionsServices ViewpointArticulate the performers, activities, services, and their exchanges providing for, or supporting, DoD functionsOperational ViewpointArticulate operational scenarios, processes, activities & requirementsCapability ViewpointArticulate the capability requirement, delivery timing, and deployed capabilityDescribes the relationships between operational and capability requirements and the various projects being implemented; Details dependencies between capability management and the Defense Acquisition System process.Project ViewpointCT77
8 Vision StatementTo enable the development of architectures that are meaningful, useful, and relevant to the DoD Requirements, Planning, Budgeting, Systems Engineering, and Acquisition decision processes.
12 Notional DoDAF v2.0 Development Schedule (cont) 2ndQTR 083rdQTR 08QTR 084thFebMarAprMayJunJulAugSepOctNovEA Summit23 Jan 08EA Conf14-19 AprApprovalDoD CIOPlenary22 JulyVwendorTool SessionDevelopWritingTechnical EditingCoodPlenary1 AprPfM WSPPBE WSFeb 08Post toDARSValidationSPIRAL II4 Apr 08SPIRAL III27 Jun 08SPIRAL IV12 Sep 08Phase IPhase IIPhase III
13 DODAF Version 2.0 in Coordination Core Management Group - 10 December 2008Discuss DoDAF Version 2 Spiral 4 Draft.Comment and adjudicationNext Step: OSD NII Informal coordinationEA Summit – Services, Agencies, and COCOMsDoD Executive Coordination Committee
14 Metadata Registration Service Federation ClientServices MenuDARSFederated CatalogDARS Federation Web ServicesRegister ProviderView ProviderUpdate ProviderRegister MetadataSearch HoldingsSOAPDDMS +Metadata(XML)AV-1 metadatacaptured and extractedby repository/toolenvironmentFederation Web servicesFederationClientFederationRepositoryRepository/ToolEnvironment
15 DoD Architecture Federation DoD Enterprise ArchitectureToolsRef ModelsTech StdsArch GuidanceLaws, Regs, and PolicyDITPRDoD EA RMDISRDODAFLawsRegsPolicyForce ApplicationTAMDBuilding PartnershipsJoint Capability AreasCommand & ControlGLOBAL C2JC2Net-centricCOMMS & TransportIEAIA ArchitectureBattlespace AwarenessBEAProtectionLogisticsMS&SMJDDAForce SupportRP&ILMHRMHRM ArchitectureCorporate Management & SupportWSLMFMOtherDISADLANSANRONGADIADept of ArmyDept of NavyDept of Air ForceArmyArchitectureDONArchitectureAir ForceArchitectureSolution Architectures
17 UPDM – Unified Profile for DoDAF/MODAF AdaptiveArtisan SoftwareASMGBAE SystemsDoDembeddedPlusGenericLockheed Martin CoMitreMODNo MagicRaytheonRolls RoyceSparx SystemsVisumPointUPDM RFC Group17
18 UPDM in General The UPDM Group was setup to: 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)The UPDM Group was setup to:Significantly enhance the quality, productivity, and effectiveness of architecture modelingPromote architecture model reuse and maintainabilityImprove tool interoperability and communications between stakeholdersReduce training impacts due to different tool implementations and semanticsImprove the integration between system of systems modeling and system modeling to support post acquisition life cycle design modelingDNDAFNAFUPDMDoDAF 1.5MODAF 1.2UPDM is an Object Management Group (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). The modeling standard is called the Unified Profile for DoDAF and MODAF (UPDM).The UPDM Group was setup to:Significantly enhance the quality, productivity, and effectiveness associated with enterprise and system of systems architecture modelingPromote architecture model reuse and maintainabilityImprove tool interoperability and communications between stakeholdersReduce training impacts due to different tool implementations and semanticsImprove the integration between system of systems modeling and system modeling to support post acquisition life cycle design modelingThe UPDM Group consists of fourteen companies distributed around the world. You can see a list of these companies in the member section on this web site.18
19 Need for UPDM 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, IDEASStatement and slides available on OMG website
23 A Federation of Data Producers StrategyReporting (OMB, GAO, etc)DARSDoD EAReference ModelsCADMDoDAFNCOW RMCOI xMILDEPCOCOMAGENCYCOI yDATAREQTS.COI = Community of InterestCADM = Core Architecture Data ModelDoDAF = DoD Architecture FrameworkNCOW RM – Net-Centric Operations & Warfare Reference ModelUPDM = UML Profile DoDAF & MODAFDoD Decision Processes
24 DoD EA Federation Strategy Available on DARS Website:
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 processArmy: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 applicabilityAir Force:Establish interface and search capability between DARS and AFARS. Demonstrate search capabilityNavy:Implement and use procedures outlined in the GIG Enterprise Architecture Federation Strategy and DARS CONOPS to create a repeatable federation processJoint 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 IT and NSS Interoperability and Supportability Policy and Process Overview DoD Sponsored PolicyJCIDS Documents (ICD, CDD, CPD) ACAT I - III & Special InterestJ6 Interoperability Requirements Certification of All JCIDS Docs (JCPAT-E Tool)ITS & NSS Predecessor Doc. System Profile Requirement- IT Standards Profile (DISRonline)- IIC Profile (LISI)Maintain OASD(NII) JCIDS/ISP Assessment Capability (JCPAT-E Tool)Maintain IT Standards and Profiles (DISRonline)Certify Standards ConformanceITS and NSS Interoperability Requirements CertificationAssessments of NR-KPP in JCIDS DocsKM/DSJoint StaffJ-8CJCSIDJoint Staff J-6 Interoperability Requirements Certification ProcessDoDI4630.8CCJCSMDoDD5000.1JROCFCBJCPAT-EITS & NSSRegistrationDISR OnlineLISI InspeQtorJ6Interoperability RequirementsCertification=•UAM / JCPAT- E System RegistrationTechnical View (CDD & CPD)Interoperability & InterconnectivityProfile (CDD & CPD)J6IStage I, II & IIIAssessmentsJCPATJCPATJoint Staff J-6 OASD(NII)
28 DISR and DISRonline Architecture View Objectives:Champion DoD’s Re-Engagement of the IT Standards CommunitiesOnline IT standards RegistryTri-Annual Update of IT Standards RegistryTied to JCIDS IT Standards Conformance and Compliance ProcessIntelligence Community Cross Coordination (ICSR)Improved DoD Visibility and Participation in IT Standards Development OrganizationsDevelop and Register PM Standards Profiles (TV)Standing IT Standards Working Groups Aligned to GIG Portfolio ManagementDoD IT Standards Registry (DISRonline)Lifecycle Tagged: Emerging and Retired StandardsProfile Assistance SoftwareOrganization-Unique BinsInformation /Guidance (I/G)Informational StandardsBest PracticesProceduresPoliciesManualsHandbooksOther IT DocumentsChange Request Tool SoftwarePM System IT Standards ProfilesTVs *Governanceand General Information AreaPolicyFAQsCM ProceduresUser GuidesLinksSOPPOCsGIG Mission Area ManagementVoting Tool Software Collaboration Tool Software* May Contain Standards from Lifecycle Categories other than MandatedDISR Mandated StandardsMandated “Net-Centric” & Mandated Sunset “Interoperability” StandardsDISR Profile Registry AreaKeyInterface Profiles *(KIPs)PrescribedTechnologyProfiles *(IPv6, PKI etc.)FutureEnhancementsTHIS SLIDE IS MORE OR LESS A NOTIONAL MODEL MEANT TO GIVE YOU IDEA OF BOTH THE FUNCTIONAL CAPABILITIES AND THE MANDATED CORE AND PROFILE REGISTRY AREAS WITHIN DISR.THE AREAS CODED IN BLUE PROVIDE THE MANDATED STANDARDS FROM WHICH PRESCRIBED STANDARDS PROFILES ARE BUILT, SUCH AS TECHNOLOGY PROFILES LIKE IPV6, KEY INTERFACE REFERENCE IMPLEMENTATIONS, AND INDIVIDUAL PM PROFILES MAKING USE OR TAKING ADVANTAGE OF THE OTHER BLUE AREAS.THE LEFT AND RIGHT WINGS IN THIS MODEL IDENTIFY THE OTHER CAPABILITIES OF DISR AND INFORMATION LINKS SUCH AS THE CHANGE REQUEST TOOL, THE VOTING AND COLLABORATION TOOL, AND STATIC DOCUMENTS SUCH AS THE SOP, USER GUIDE ETC.UNDER OBJECTIVES, YOU SEE SOME OF THE POINTS I MENTIONED BEFORE BUT I’D ALSO LIKE TO POINT OUT THAT WE RECENTLY HAVE PLACED A GREATER EMPHASIS ON COORDINATING I-T AND INTEL STANDARDS WHERE THEY APPLY TO BOTH COMMUNITIES. IN FACT, WE ARE IN THE PROCESS OF SUPPORTING THE IC CIO ON THE STAND UP OF A DISR LIKE STANDARDS TOOL TO BOTH SUPPORT THEIR UNIQUE INTEL STANDARDS REQUIREMENTS AND THAT LIKE IT STANDARDS ARE CONSIDERED.I WOULD ALSO NOTE THAT THE MANDATED SET OF STANDARDS STILL NEEDS TO ALLOW FOR A CERTAIN LEVEL OF LEGACY STANDARDS TO EXIST WITHIN THE CORE ALBEIT THEY MAY BE TAGGED AS A SUNSET STANDARD THUS SIGNALING TO OUR WORKING GROUPS THE NEED TO KEEP AN EYE ON EMERGING CANDIDATE STANDARDS.
29 Lifecycle of a Standard EmergingUpgradeability Should be a ConcernMay be Implemented but Not in Lieu of Mandated StandardExpected to be Mandated within Three YearsMandatedEssential for Interoperability and Net-Centric Services in DoDMinimum 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 WarfighterSunset Tag Identifies an Event and Date to Retire a StandardInactive / RetiredNew Standards / Technology Now Available and ImplementedRequire Waiver and Migration PlanRemain in the Registry
30 IT Standards Governance Organization Membership Technical Working Groups
32 DoD Technical Guidance Concept Query &RetrieveIdentifiedInteroperabilityStandard,Specifications,And InterfacesCapabilityDevelopment AreasJoint Capability AreasStandardsSpecificationsMission Area PortfoliosCommunity Of InterestGIG Governance ProcessesStructured andUnstructured Sourcesfor Standards and(Notional)DARS. . .DKOCADM463080XXXMLMetadataRegistrySFISTaxonomyDetailedStandards &InformationDISRNCIDTechnical Direction QueryTechnical Direction QueryCapabilityGIGTechnical GuidanceStandards &SpecificationsForInteroperabilityFrom the left side of the figure, the Type II Technical Direction detailed standards and specifications information are obtained from Structured and Unstructured sources such as DISR, DARS, DOL, CADM, 4630, etc. which provide the necessary content and references contributes to the Type II Technical Direction. From the right side of the figure, the identified interoperability standards and specifications that are applicable to the capability development area contribute to the Type II Technical Direction. These interoperability standards and specifications will have to be identified by system engineers and functional experts for each.As indicated by the green arrows in the figure, the “assembling” of the set of interoperability standards and specifications for the capability portfolio area, JCA, COI, and GIG Governance Processes that a developing capability touches becomes the Type II Technical Direction (for that developing capability). The mapping of these comprise the targeted Type II Technical Direction for the user.A portal for the delivery of Type II Technical Direction will allow a developer to determine the minimum interoperability standards and specifications. By querying on the capability portfolio area/JCA/COI that are drawn on for the capability to be developed, the portal can “assemble” the Type II Technical Direction. For example, A team building a Spend Analysis Capability under the acquisition portfolio needs to implement the following functions:1) provide financial information to users on the GIG2) publish the financial reporting service to the GIGUsing the Type II portal, the team can query for the capability portfolio/JCA/GIG Governance process/COI utilized. Based on the identified interoperability standards and specifications within the Business Mission Area portfolio to exchange financial information on the GIG, the portal (portlet, service) retrieves the detailed information from the standards source. Also, within the EIEMA Portfolio, the portal (portlet, can find the publication standards for the Enterprise Service Discovery Service.XML Schemas/ Components
33 Architects Career Path Architects Competencies Architects Certifications
34 IMPROVING DOD’S ARCHITECTURE GuidanceDoDAF v2.0Federated Architecture StrategyToolsDoD Architecture Registry System (DARS)DoD IT Standards Registry (DISR)Type II – GIG Technical DirectionEducation and TrainingDoD Architecture Training EffortAll 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 architectsTherefore, 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 frameworkImplement Certificates & Certification across architecture specialtiesWork 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 workforceProvides collected data on the competencies of an architectArchitecture Education and Training DKO SiteOPM Job Family Standard ReviewClinger-Cohen Core Competency Review for ArchitectureDelivered two Architecture Training Tutorials at 2008 EA Conference
38 Chief Architect, DoD Information Sharing Sharing EnvironmentWalt OkonChief Architect, DoD Information SharingArchitecture & Interoperability Directorate Office of the DoD CIO/ASD NII
39 DoD is part of this complex, extended information sharing enterprise… Complexities of Information SharingNortheast Power BlackoutCounter TerrorismFailed States (Haiti)TerroristActionsNatural DisastersWarfighterOperationsCoalitionHumanitarianPandemicFluDoD 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 DoD Enterprise Architecture Conference 2009 Bring It All TogetherDoD Enterprise Architecture Conference 2009
43 DoD Enterprise Architecture Conference 2009 All DoD Architecture ProfessionalsOnly official Architecture ConferenceEnterprise Architecture & StandardsDeliver Interoperability1 – 5 June 2009; DoD Enterprise Architecture Conference 2009 in St Louis, MODeliverables
44 Chief Architect, DoD Information Sharing Questions/Wrap-UpWalt OkonChief Architect, DoD Information SharingEnterprise Architecture & Standards Directorate Office of the DoD CIO/ASD NII07 December 2008