WIXLIB

Delivering Enterprise Architecture Lean Methods(Maturity and Quality Disciplines)19 April 2012Pamela J. Wise-Martinez, NNSA Chief Architect

Agenda Introduction OneArchitecture concept, goals & alignment Enterprise Architecture Vision for Center of Excellence Road to the OneArchitecture Strategy Ensuring Architecture workgroup alignment with Mission Enterprise Architecture Maturity and Assessment NNSA’s Repository Proposal Accomplishments What’s Next1

IntroductionNNSA’s CIO coined the phraseOneArchitecture (One EA) approach todeliver the enterprise architecture. NNSAEnterprise Architecture (EA) team inpartnership and collaboration with theDepartment’s Enterprise Architects will providearchitecture guidance & support for NNSA’sand Department initiatives. As a result the EAteam developed a LEAN discipline forarchitecture.2

NNSA’s Enterprise ArchitectureCenter of ExcellenceService OrientedPlanning andDesignStrategic Alignmentof Business andTechnologyEngineeringQuality andStandardsMaturity andProcessOptimizationContext Driven,Communicationsand AbstractionValue AddedConsumer Servicesfor Mission SupportSecurity andInteroperabilityFocusedGovernance forEnterpriseInformationArchitectureCommon Business Language3

OneArchitecture DefinitionA Center of Excellence approach,OneArchitecture (One EA) is aLEAN Architecture developmentdiscipline delivering an AsEmerging Enterprise Architecture,Blueprints, Standards andReference Architecture guidancefor business and technologyinitiatives across the enterprise.4

NNSA OneArchitecture ConceptI.One Enterprise Architecture across all of NNSA Sites/M & O’s, Labs, sustained programs, new initiatives Common set of core artifacts, common modeling (TOGAF, SOA and FEA), disciplinesand common business languageII. DOE Strategic EA Partner—Early support of Key InitiativesIII. Aligned with Federal Enterprise Architecture (FEA) v2 Architecture based on Federal Common Approach to Enterprise Architecture(FEA replacement) Federal Shared Services alignmentIV. Align Strategic Investments in Technology to meetBusiness Objectives (CPIC)5

OneArchitecture 2012 GoalsI.Develop Mature EA Framework and RepeatableGovernance Model/ProcessII. Develop and Approve list of Artifacts and Blueprints forfuture projectsIII. Align all Architecture work to EA disciplines and principalsIV. Build EBRM, ETRM, ESRM, ESerRM Technical Standards, Functional Decomposition to Business Processes, Security Profiles and Risk Approach, Application design and engineering standards and Principles6

Delivering OneArchitecture Strategyand scriptiveArchitectureAs-EmergingArchitectureEA Principals,Goals andGuidance rdsManagementDataDescriptionsandDefinitions nologyand BusinessTransformationSOA, TOGAF,FEAJust 12 - 20137

Architecture Domain andWorkgroup ic Alignment(Business Case)DAA-related topicsAdministration oftechnologyApplication/ServicedevelopmentBusiness ProcessEngineeringSSM-related topicsSolution ArchitectureRest and WSDLContracts (Interfaces)Information AssetsAudit/control issuesChange ControlService CataloguesInvestment AlignmentEnterprise Role andContinuous MonitoringInfrastructureComponentsService OrientedArchitecture(Networks, Platforms,Facilities, Access)Performance MetricsPolicy EnforcementIT PortfolioService InventoryIdentity ManagementENTERPRISE LINES OF SITEMaster Data andWorkflow(BRM, DRM, PRM)Information Assurance(SRM)Virtualization(IRM)Shared Services andInformation Exchange(ARM)8

NNSA Enterprise Architecture FrameworkBusAWGSvcAWGServices RAEGMITEAGCTechAWGEnterprise SecurityRAData EABusiness EAIRBTechnology EASecAWGN E AT RArchitectureRepository(TROUX)Work Streams penetrate allworking level architecturesNNSA “segment” Level Architecture ArtifactsArchitectureIntegration PointHQ./Site/M&OArchitecturesNNSA Sustained Program Level Architecture ArtifactsNNSA Project Level Architecture Artifacts“Working level” architectures “pluginto” (i.e. integrate into) theenterprise for completenessProgramArchitecturesNew StartsArchitectures9

NNSA Enterprise Architecture FrameworkBusAWGSvcAWGServices RAEGMITEAGCTechAWGEnterprise SecurityRAData EABusiness EAIRBTechnology EASecAWGN E AT RArchitectureRepository(TROUX)Work Streams penetrate allworking level architecturesNNSA “segment” Level Architecture ArtifactsArchitectureIntegration PointHQ./Site/M&OArchitecturesNNSA Sustained Program Level Architecture ArtifactsNNSA Project Level Architecture Artifacts“Working level” architectures “pluginto” (i.e. integrate into) theenterprise for completenessProgramArchitecturesNew StartsArchitectures10

EA Maturity and Assessment11

Business Architecture WorkgroupGoal: Ensure Business Architecture alignmentwith the enterpriseStrategic Alignment of Business and Technology Identify existing business processes across the enterprise Identify future business processes that will align to mission Identify existing business use cases across the enterprise Identify future business use cases that will align with mission12

Service Architecture WorkgroupGoal: Ensure architecture services are alignedwith enterprise initiatives Applications will be defined in terms of services offered Identify application candidates at each site that can be consolidated orretired Map selected applications to future cloud-aware requirements for Ensure future Cloud aware applications satisfy criteria for Interoperability Performance and scalability Reliability and availability Application and technology insertion lifecycles Technological risks13

Technology ArchitectureWorkgroupGoal: Ensure Technical Architecture alignmentwith enterprise initiatives Primary focus areas include: Cloud Computing Mobility Social Computing Networking Identify existing network diagrams and topologies ateach site Identify Cloud Computing topologies that will align with future businessprocesses14

Security Architecture WorkgroupGoal: Ensure Security Architecture alignment withRightPath initiatives for all architectural domains Business Information Applications Data Technology15

Security Architecture WorkgroupEnsuring OneArchitecture alignment complieswith FedRAMPWhat is FEDRAMP?FedRAMP is a government-wide program that provides astandardized approach to security assessment, authorization,and continuous monitoring for cloud products and services. This approach uses a ―do once, use many times‖ frameworkthat will save cost, time, and staff required to conduct redundantagency security assessments.16

NNSA Enterprise ArchitectureTransformation Repository (NEATR)N E AT RProcesses, Activities, dataDocuments, reports, etcArchitectureArtifactsEG&PExecutionGovernance & Policy FileGovernance&PolicyTSPDiagrams, ical Standards Profile (TSP)StorehouseArchitectureof ALL s) Artifacts,Products, Documents17

OneArchitecture – Recommended Artifacts Artifacts are divided into architecturedomains to build the Enterprise Architecture Business Technology/Infrastructure Application/Service Security Data/Information18

Team Value-Add Accomplishments Developed NNSA OneArchitecture framework and (AsEmerging) Blueprinting Approach Developed list of Artifacts for (Business, Technical, Security,Applications and Data) and Intake process Developed Technical Reference Model- In Review Delivered Business Architecture Project Plan - Complete Delivered Business Architecture Strategy – In Review Developed PPBE IDEF0 Modeling - Collaboration Delivered Enterprise Business Functional Decomposition Complete SOA Assessment Strategy & Reference Model -

Next Steps Perform BA Assessment and discovery for all HQ Programs(SixSigma Assessments) Deliver Enterprise Reference Models and Technology Bricksand Patterns (ETRM, EBRM, SecRM) Deliver Enterprise Troux Strategy Meta-Models, DataMarts, Artifacts, Intake Continue to align with mission and business requirements Plan for Enterprise Architecture Day20

Thank You!Pamela J. Wise-Martinez, CGEITNNSA Chief ArchitectOffice of the Chief Information OfficerU.S. Department of EnergyNational Nuclear Security AdministrationP: a.doe.govNNSA Enterprise Architecture MailboxEAGC@nnsa.doe.gov21

BACKUP SlidesSample of Common FEA v2,TOGAF 9 Artifacts andEA Definitions

Business Architecture ArtifactsArtifactStandardDomainConditionOwner ***CommentBusiness ArchitectureBusiness Reference Model version 2FEA v2 - DeliverableBusinessRequiredEA TeamFederal Enterprise Architecture Reference Model version 2Functional Decomposition DiagramVisioTOGAF 9 Template - Request for Architecture TOGAF 9 - DocumentWorkBusinessBusinessRequiredRequiredEA TeamFunctionalDescribes the functions with the organizationAll IT investments requiring architecture reviewBusiness Process DiagramBusinessRequiredTOGAF 9 Template - Organizational Model for TOGAF 9 - DocumentEnterprise ArchitectureActor Role MatrixTOGAF 9 - DocumentBusinessRequiredBusinessRequiredUse Case Narrative and DiagramUML - VisioBusinessRequiredFunctional/ EA Team Business Process Model Notation version 2.0, OpenManagement Group (OMG)Functional/ EA Team Document to describe the organizational roles andresponsibilities from the enterprise perspectiveFunctional/ EA Team The matrix to describe the organizational roles andresponsibilitiesEA Teamuse case depicts the actors, scenario tied to process modelsTOGAF 9 Template - Business Principles Goals - DriversTOGAF 9 - DocumentBusinessOptional -ThresholdFunctionalTOGAF 9 Template - ArchitectureRequirements SpecificationBusiness Interaction MatrixTOGAF 9 - DocumentBusinessRequiredFunctionalTOGAF 9 - DocumentBusinessRequiredFunctionalInformation Exchange MatrixExcelBusinessRequiredFunctional/ EA Team Information exchange requirements express therelationships across three basic entities (activities,business nodes and their elements, and information flow),and focus on characteristics of the information exchange,such as performance and security. They identify whoexchanges what information with whom, why theinformation is necessary, and in what manner.As-emerging Business ArchitectureOneEA - DeliverableBusinessRequiredFunctional/ EA TeamAs-emerging Business Architecture Definition OneEA - DeliverableDocumentBusiness Inputs to the EAOneEA - DeliverableRoadmap/Transition Plan/Sequencing PlansBusinessRequiredFunctional/ EA TeamBusinessRequiredFunctional/ EA TeamBPMN 2.0Business principles, business goals, and business driversprovide context for architecture work, by describing theneeds and ways of working employed by the enterprise.Requirements Specification document to capture requiredfor the business needdescribes the business locations (nodes), the "needlines"between them, and the characteristics of the informationexchanged