The Future of Enterprise ArchitectureTowards the Coherent

John GtzeImagine an enterprise that had not heard of EA.It is operational (sort of) It produces and uses information (there are artefacts) No enterprise wide coherence (at best accidental coherence) In the Beginning .ITBusinessExisting EnterpriseEA Not appliedInformation IndecisionToo much informationToo much complexityToo many challengesToo little timeBusiness Intelligence vs. Intelligent BusinessConditions The Constancy of Change Lewis Carolls Red Queen: in this place it takes all the running you can do, to keep in the same place.” Neuraths Boat ”We are like sailors who on the open sea must reconstruct their ship but are never able to start afresh from the bottom.”Disruption Alignment= 0”Remember Your Vector Math!”AgilityAssurance10 EA = ?Everything AlignedEnabled AgilityEmbedded Assurance.Occams RazorAll other things being equal, the simplest solution is the best.Ross, Weill & Robertson:“Enterprise Architecture as Strategy”Five elementsStrategic Initiatives Operating Model Enterprise ArchitectureEngagement ModelFoundation for executionThe IT infrastructure and digitized business processes automating a companys core capabilities. Operating ModelOperating ModelSingle point of contact Begins with customersSynergy and Responsiveness Begins with processes, customers and shared servicesScalabilityBegins with processes Economies of scaleBegins with shared servicesN=1 & R=GGeoffrey Moores Cycle of InnovationDeployInventOffloadCoreContextMission CriticalNon-Mission-CriticalManageFund next innovationIVIIIIII25TechnologyBusinessStrategyUse of EA to ensure Alignment of Business & ITCapture Understanding of Business Target: Systems Architecture and DesignValuable and the most practiced form of EAFoundation ArchitectureCapturedCaptured and DesignedNot appliedITBusinessExisting EnterpriseEA AdditionUnderstand the BusinessDesign SystemsEA 1.0EAFrameworkEA ArtifactsEABest PracticesEA MethodologyEA Tools &RepositoryA “complete” EA approach must have all of these elements, which are specifically designed to work together in the context of the (IT) governance process. (IT) Governance”Complete” EA ApproachCarnegie Mellon UniversityScott Bernards EA3 CubeScott Bernards EA3 CubeEA ArtifactsEABest PracticesEAMethodologyEA Tools &RepositoryDetailedDetailedViewViewMidMidLevelLevelViewViewHigh High LevelLevelViewViewCurrent EA Current EA ViewsViewsEnterprise Architecture RepositoryEnterprise Architecture RepositoryPerformancePerformanceMeasuresMeasuresStrategicStrategicPlanPlanGoals &Goals &InitiativesInitiativesInvestment Investment PortfolioPortfolioBusinessBusinessPlanPlanBusinessBusinessProcessesProcessesDataDataDictionaryDictionaryKnowledgeKnowledgeWarehouseWarehouseInformationInformationFlowsFlowsApplicationApplicationInventoryInventoryBusinessBusinessSystemsSystemsSupportSupportSystemsSystemsBuildingsBuildings& Equipment& EquipmentWide AreaWide AreaNetworkNetworkLocal AreaLocal AreaNetworkNetworkDataDataPrivacyPrivacySecuritySecurityProgramProgramSystemSystemCertificationsCertificationsGoalsGoals& Initiatives& InitiativesProductsProducts& Services& ServicesData &Data &InformationInformationSystems &Systems &ApplicationsApplicationsNetworks &Networks &InfrastructureInfrastructureSecuritySecuritySolutionsSolutionsSite MapSite MapEA TutorialEA TutorialEA Program EA Program Future EA ViewsFuture EA ViewsEA StandardsEA StandardsEA Management PlanEA Management PlanDetailedDetailedViewViewMidMidLevelLevelViewViewHigh High LevelLevelViewViewCurrent EA Current EA ViewsViewsEnterprise Architecture RepositoryEnterprise Architecture RepositoryPerformancePerformanceMeasuresMeasuresStrategicStrategicPlanPlanGoals &Goals &InitiativesInitiativesInvestment Investment PortfolioPortfolioBusinessBusinessPlanPlanBusinessBusinessProcessesProcessesDataDataDictionaryDictionaryKnowledgeKnowledgeWarehouseWarehouseInformationInformationFlowsFlowsApplicationApplicationInventoryInventoryBusinessBusinessSystemsSystemsSupportSupportSystemsSystemsBuildingsBuildings& Equipment& EquipmentWide AreaWide AreaNetworkNetworkLocal AreaLocal AreaNetworkNetworkDataDataPrivacyPrivacySecuritySecurityProgramProgramSystemSystemCertificationsCertificationsGoalsGoals& Initiatives& InitiativesProductsProducts& Services& ServicesData &Data &InformationInformationSystems &Systems &ApplicationsApplicationsNetworks &Networks &InfrastructureInfrastructureSecuritySecuritySolutionsSolutionsSite MapSite MapEA TutorialEA TutorialEA Program EA Program Future EA ViewsFuture EA ViewsEA StandardsEA StandardsEA Management PlanEA Management PlanNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworks &Networks &InfrastructureInfrastructureSystems &Systems &ApplicationsApplicationsData &Data &InformationInformationProducts &Products &ServicesServicesNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureGoals &Goals &InitiativesInitiativesLines of BusinessLines of BusinessC CO OMMP PO ON NE EN NT TS SSecurity, Standards, WorkforceSecurity, Standards, WorkforceTechnology Technology Business Business - -StrategyStrategyNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureNetworks &Networks &InfrastructureInfrastructureSystems &Systems &ApplicationsApplicationsData &Data &InformationInformationProducts &Products &ServicesServicesNetworkNetworkInfrastructureInfrastructureNetworkNetworkInfrastructureInfrastructureGoals &Goals &InitiativesInitiativesLines of BusinessLines of BusinessC CO OMMP PO ON NE EN NT TS SSecurity, Standards, WorkforceSecurity, Standards, WorkforceTechnology Technology Business Business - -StrategyStrategyStrategic LevelStrategic PlanFuture Operating ScenariosBalanced Scorecard Goals and MeasuresBusiness LevelBusiness Plan (E - Commerce Plan / E -Government Plan) Business Requirements Use CasesBusiness Case Investment PortfolioBusiness Process Management ApplicationsBusiness Process Reengineering / ImprovementTechnology LevelService Oriented ArchitectureObject-Oriented Data Modeling/Application DevelopmentNetwork - Centric Systems EngineeringEnterprise Resource Planning SystemsNetwork Management ApplicationsSecurity ArchitectureS+B+T-Provides Excellent Value-Some implementations are simply IT Architecture at the Enterprise Level-In some cases this is all you need for a particular investment.Foundation ArchitectureSaint- ExupryFEA Practice Guide, OMB 2006. http:/www.whitehouse.gov/omb/egov/documents/FEA_Practice_Guidance.pdfEA Transition PlanningAn enterprise architecture is in continual transition as implementation and upgrade projects are completed. Needs coordination, prioritization, and oversight. ”We need a plan”.Forward-Looking ArchitectureOne of the purposes of an EA program is to develop future views of the architecture Many stakeholders Many layers Big projects Money Time Extent A “discipline” Science PracticeEA is (like) Urban Planning39Enterprise Architecture 2.0Approaches can scale from local to global.CEO wants to own and use the architecture.Integrates Strategic, Business, and Technology Planning.Moving from Documentation to Analysis, to Design - supported by better tools/artifacts.More standards on terms and methods from international and national bodies.More case studies of good and bad EA in the public and private sector.Non-IT use of EASupport Coherence Generally (e.g. Policy Alignment) Enables Enterprise EngineeringLess practiced form but arguably more valuable than foundationExtended ArchitectureCapturedCaptured and DesignedNot appliedITBusinessExisting EnterpriseEA AdditionDesignBusinessDesign SystemsEA 2.0Traditional Business Architecture:Capturing business requirements to build systems Results in solutions aligned to businessNew Business Architecture:Design the business to achieve desired business outcomesResults in business aligned to purposeExtended ArchitectureThink business “Purpose” not just business “Process”The use of EA by non-IT and IT in normal processes.Architecture is already there, so an enterprises architecture should NOT be developed as a project. It should be leveraged.Find these key descriptive processes, apply EA structure to those artefacts and enable alignment.Embedded ArchitectureCapturedCaptured and DesignedStructuredITBusinessExisting EnterpriseEA AdditionAlign Those Doing Business DesignAlign Those Doing IT DesignEA 3.0Embedded ArchitectureImplications EA becomes the task of the CxO Leaders Alignment Support is the Chief Architects Responsibility Built-Out effort gets reduced because we get to reuse Built-In artefacts.Example: When starting transformation of a policy center because of new political direction we would:Previously Begin the process of properly capturing the “As Is”.Now We simply get the “As Is” from the artefacts updated through regular process (e.g. Annual Plans, Budgets).Motto: Find It, Structure It, and Align ItBalanced EA Ubiquitous, embedded architecture ”Way of Life” Living architecture, ever-green Solid foundation Strategic alignment Alignment, Agility AND AssuranceGary Hamel Management innovation Our enterprises have 21st-century, Internet-enabled business processes, mid-20th-century management processes, all built atop 19th-century management principles Management 2.0 New Management DNAMay 200850Alignment of Business & IT Foundation ArchitectureCapturedCaptured and DesignedNot appliedITBusinessExisting EnterpriseEA AdditionUnderstand the BusinessDesign SystemsEA 1.051Non-IT use of EA Extended ArchitectureCapturedCaptured and DesignedNot appliedITBusinessExisting EnterpriseEA AdditionDesignBusinessDesign SystemsEA 2.052The use of EA by non-IT and IT in normal processes Embedded ArchitectureCapturedCaptured and DesignedStructuredITBusinessExisting EnterpriseEA AdditionAlign Those Doing Business DesignAlign Those Doing IT DesignEA 3.0Coherency Management- Architecting the Enterprise for Alignment, Agility, and Assurance Doucet, Gtze, Saha, Bernard (forthcoming) www.coherencymanagement.orgEADesignLeadership & facilitationAssessmentAny investment or Whole enterprise Operational EnterpriseDESIGNERS-DESCRIBERSPlannersPolicy WritersOperations:HR, FM, TM, IMDECIDERSOwnersExecutivesManagersStaffEnterprise DescriptionDesigns (Business & Tech) Plans (Project, Annual) Reports, Org Charts, JobDescriptions, Prcis, Process MapsetcImprove Designs & DescriptionsContinuous Coherency ImprovementImproveFunctioning EnterpriseResourcesPeople, Money, Information, Technology, Property, AssetsStructuresPatternsFrameworksDesignsENTERPRISEARCHITECTUREASSESSMENTAny Investment or Whole EnterpriseDESIGNLeadership/FacilitationObservers Stakeholders PartnersADVICENew RulesMethods, ModelsDesignsADVICE Gaps / OverlapsFrom Strategy to OperationsCoherent ViewThe three aspects of coherencyCoherent Rules for DescriptionsCoherent DescriptionsCoherent Enterprise When the enterprise experiences coherent operation and execution. Alignment is very mature because the rules allow descriptions to be compared for alignment and adjusted accordingly. Agility is achieved because the designs are coherent, which includes a developed understanding and practice of loose coupling by design instead of tight coupling by accident. Assurance is gained through an ability to not only have all the information but also, through coherency, have the information provide real knowledge. ContactJohn Gtzehttp:/gotze.eujohngotzespace.dk