Presentation on theme: "Delivering an Information Advantage"— Presentation transcript:
1Delivering an Information Advantage Architecture Policy, Processes and ToolsIntegrated EA Conference 2009Brian WilczynskiDirectorEnterprise Architecture and StandardsOffice of the DoD Deputy Chief Information Officer
2DoD CIO IM/IT Strategic Plan Delivering an Information Advantage VisionLead The DoD Enterprise To Achieve An Information Advantage For Our People And Mission PartnersMissionLead the information age transformation to enhance the Department of Defense’s effectiveness and efficiencyStrategic EndAn agile enterprise empowered by access to and sharing of timely and trusted information2
3Integrated Enterprise Architecture VERSION 153/25/ :44Integrated Enterprise ArchitectureArchitecture Policy/Mandates“Develop, maintain, and facilitate theimplementation of a sound and integratedIT architecture for the executive agency” – Clinger-Cohen ActOffice of Management and Budget Circular A-130“Management of Federal Information Resources”DoD Directive“ASD NII / DoD CIO”DoD Directive“Management of the DoD Information Enterprise”NAFFJAWGFederation StrategyReference Model Maintenance ProcessSD-106 Policy DocumentsDoD Directive 8210.x“Architecture in the Department of Defense”Defense Acquisition SystemInteroperability and SupportabilityJoint Capability Integration33
4Enterprise Architecture & Standards Supporting the CIO Mission Lead The DoD Enterprise To Achieve An Information Advantage For Our People And Mission PartnersCIO Vision &MissionNet-Centric TransformationInformation as a Strategic AssetInteroperable InfrastructureCIO StrategicGoalsReturn on InvestmentIT Work Force DevelopmentAssured Information AccessDoD Architecture Frameworkv2.0 (DoDAF)Federated Joint Architecture Working Group (FJAWG)DoDD 8200Architecture within DoDDoD Architecture Registry System (DARS)Core Enterprise Services to the Tactical EdgeDoDI 8210.xxArchitecting DoD EnterpriseDoDM 8210.xxDoD Architecture FederationDoD Information Enterprise Architecture v1.1International Defense Enterprise Architecture Specification (IDEAS)InitiativesOutreachEA Conferences * Summit * Vendors * DKOMaritime Domain AwarenessDoD Architecture Strategy4
5Delivering an Information Advantage Architectural and Decision Making ProcessesJointCapabilitiesIntegration andDevelopment(JCIDS)IT Architecturesare required and areessential parts of each decision-making processDEFINECJCSI C, CJCSMDefine the Force andForce CapabilitiesPlanningProgrammingBudgetingExecution(PPBE)DefenseAcquisitionBUILDDODD ,DODIBUILDDODD ,DODIAcquire and Equipthe Force andForce CapabilitiesAllocate Resources forthe Force andForce CapabilitiesInteroperability andSupportabilityAssess and Certify System InteroperabilityDODD , DODI , CJCSI E55
6Delivering an Information Advantage Provide an Integrated Compliance ToolsetDARSFederated CatalogData SourcesDoDAFMetaModel (DM2)Tuple TypeTuple TypeFederal &Local GovtObj ExchgExchangeSpecificationDoDDataTagsDoDAFFEAWeb ServicesOO / UML, UPDM, IDEFCoalitionXML, XMIToolsUSAFDISRDatabasesARMYNAVYIDEASJCME(JFCOM)USMCDITPRFSAME-ISPVUE-ITExternalData StandardsData MiningExchange StandardsModeling Tools6
8DoDAF 2.0 Viewpoints Capability Viewpoint Operational Viewpoint VERSION 153/25/ :44DoDAF 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 ViewpointCT88
11IEA PrioritiesData and Services Deployment (DSD) – Decouple data and services from the applications and systems that provide them, allowing them to be visible, accessible, understandable and trusted. Lay the foundation for moving the DoD to a Service-Oriented Architecture (SOA).Secured Availability (SA) – Ensure data and services are secured and trusted across DoD. Allow users to discover data and services and access them based upon their authorization.Computing Infrastructure Readiness (CIR) – Provide the necessary computing infrastructure and related services to allow the DoD to dynamically respond to computing needs and to balance loads across the infrastructure.Communications Readiness (CR) – Ensure that an evolvable transport infrastructure is in place that provides adequate bandwidth and end-to-end, seamless net-centric communications capability across all GIG assets.NetOps Agility (NOA) – Enable the continuous ability to easily access, manipulate, manage and share any information, from any location at any time.
12DoD Architecture Federation DoD Enterprise ArchitectureToolsRef ModelsTech StdsArch GuidanceLaws, Regs, and PolicyDITPRDoD EA RMDISRDODAFLawsRegsPolicyForce ApplicationTAMDBuilding PartnershipsBEAJoint Capability AreasCommand & ControlGLOBAL C2JIAMDO C2Net-centricNC CPM ArchIEAGIG IA ArchitectureBattlespace AwarenessProtectionLogisticsRP&ILMMS&SMJDDA-EForce SupportHRMHRM ArchitectureCorporate Management & SupportWSLMFMSOCOMDISADLANSANRONGADIAOtherDept of ArmyDept of NavyDept of Air ForceArmyArchitectureDONArchitectureAir ForceArchitectureSolution Architectures
13Lessons LearnedArchitecture must be a senior-level leadership priority.Architecture becomes relevant when it is integrated into the major decision-making processes of an organization.Architecture needs to be described within the terms of the consumer.Complexity needs to be understood and managed.