NNSA One Architecture Concept Common Services Repository NNSA

NNSA One. Architecture Concept & Common Services Repository NNSA Enterprise Architecture—One. EA Common Services: Framework & Repository Leon Cameron, NNSA/OCIO Principal Lead Architect

Topics • Part I: NNSA Enterprise Architecture Model, Framework, & Operational Concept • Part II: Common Services: Framework & the Repository • Part III: Questions • Part IV: Backup & Contact Information 1

Part I. Enterprise Architecture Concept & Framework

Part I Topics • NNSA One Enterprise Architecture Strategy • One. EA Structure • Con. Ops • Framework 3

Architecture Complete the Puzzle Business Models Applications Information Agency Mission LOBs • Enterprise-Wide Vision Federal & Agency Policy Stakeholders Enterprise Architect • Common Understanding • Collaboration & Communication Sustainment Systems Current & Emerging Technologies & Stds 4

A view of Architecture… Authority to Proceed IRB Infrastructure Security Technical Standards Framework Bu si ne Services ss Ca se Governance & Policy Business owners New Capabilities, New Business Case, New Requirements Enterprise Architect 5

Good Architecture Improves Final Product! 6

NNSA One. Architecture Strategy • A Single Enterprise Architecture across all of NNSA • Sites/M & O’s, Labs, sustained programs, new initiatives • Common set of core artifacts, common modeling (TOGAF, SOA, FEA), common business language • Strategic Technology/Business Alignment • Common set of technology standards; EA Policy • EA adding value throughout IT Lifecycle • DOE Strategic EA Partner—Early support of Key Initiatives Right. Path • Aligned with Federal Enterprise Architecture (FEA) v 2 • Federal Common Approach to Enterprise Architecture • Federal Shared Services • NNSA/DOE Represented on Federal-Level Working Groups 7

NNSA One. Architecture— One. EA Concept Artifact Repository DOE EA Site EA NNSA EA Segment EA Mission EA DOE Complex Policy & Standards E A L a n d. Governance scape Reference Library • • • Alignment Integration Federal EA Space Common Taxonomy Best Practices Adopted Standards IT Lifecycle 8

A view of Architecture…The STRUCTURE Authority to Proceed IRB Infrastructure Security Technical Standards Framework Services Governance & Policy Business owners New Capabilities, New Business Case, New Requirements Enterprise Architect 9

NNSA Enterprise Architecture: One. EA Notional Structure DRIVERs • Strategic Plans • Priority Goals • Common Approach Enabling Applications Infrastructure & Technology Applications Reference Model Technology Reference Model Governance & Policy Profile Information & Data Reference Model Technical Standards Profile Security Controls Business Services Business Reference Model Common Services & Repository/Catalog 10

Federal EA Management 11 Department EA Management C O L A L L A I B Agency EA Management G O N R M A E T N I T EA Development O N One. EA Concept of Operations NNSA Shared Services Align across DOE/NNSA/Federal Spaces Alignment • Federal/OMB • DOE • NNSA architecture artifacts and services Collaboration • • OMB/IRM OMB/SRM OMB/BRM OMB Shared Svcs EA Reference Models 11

A view of Architecture…The FRAMEWORK Authority to Proceed IRB Infrastructure Security Technical Standards Framework Services Governance & Policy Business owners New Capabilities, New Business Case, New Requirements Enterprise Architect 12

NNSA Enterprise Architecture Framework E n t e r p r. Technology i s e A r c h. EA itecture EAGC Standards and Collaboration Bus. AWG Svc. AWG Tech. AWG Enterprise Security RA Sec. AWG NEATR Architecture Integration Point Architecture Repository (TROUX) Work Streams penetrate all working level architectures NNSA “segment” Level Architecture Artifacts Data EA ARB IRB Governance G o v e r(EGMIT) nance, Services RA Business EA HQ. /Site/M&O Architectures NNSA Sustained Program S o l u t Level i o n Architecture A r c h i t e c. Artifacts tures NNSA Project Level Architecture Artifacts “Working level” architectures “plug-into” (i. e. integrate into) the enterprise for completeness Program Architectures New Starts Architectures 13

Part II. NNSA Common Service Framework & Repository

Part II Topics a) Common Service Framework • Federal Shared Services • Framework • Implementation Strategy b) Common Services Repository 15

Federal Shared Service Strategy • Shared‐First Mandate • Eliminate Duplicative Systems • Reduce Redundant IT resources • Shared Commodity IT Share First • Improve Transparency of Shared Services Commodities Minimize Redundancy 16

Common Services Framework (CSF) • CSF promotes interoperability, agility & service reuse. • CSF is an environment for managing the design, development & deployment of shared services • CSF Objectives: • Significantly Abstract Interfaces • Standardize Processes • Encourage Web-based solutions • Where Appropriate: Fosters • Reuse; Porting; Configurable Solutions • Data Model Independent • Trusted Communications • Strict Configuration Control. 17

Common Service Framework Stakeholders Notional Government Developers Architects Hosting Standards Delivery Standards XML Standards API Standards Notional Framework Configuration Management Security Controls & Monitoring Academia IT Staff Business Owners Industry Program Managers CIOs, CTOs, CFOs 18

How a Shared Service is Born… • Business Need • Modify Existing Service • New Initiative • Use Case Realize Shared Service Opportunity Identify Candidates • CSF Repository • [OMB Shared Service Catalog] • Embedded Service • New shared service? • Modify existing service • New Composite service? Conduct Alternative Analysis Implement • Development: • New or modify • Deploy service according to CSF 19

Shared Services Implementation Strategy We are here-Commodity IT Sharing: • Infrastructure • Enterprise IT systems • Business systems Walk Run Crawl DOE Right. Path Initiative 20

Common Service Repository

NNSA One. EA—Common Service Repository Concept • Available “on-demand” Common Service Repository Catalog • Common Services, Applications, Technology Interfaces • Service Catalog advertised to stakeholders • viewable by Role/PII • Services/Apps: downloadable or executable • Updates delivered autonomously • Access & transport security • End-user identification opens/restricts CSR catalog domains • Virtual Repository from end-user perspective CSR 22

CSR Architecture Common Service Repository App Requests CSR Users & Devices • Identification & Authentication • Role-based access • Secure Transport WAN/ LAN Delivery Services Notification Services Wireless Net App Requests Data Cloud Data Local 23

Common Service Repository “Service Store” SERVICE-ON-DEMAND Paradigm • Download “service” or “application” as needed from DOE/ NNSA Common Service Repository • Update Service/App when “notified” To-be Federal Shared Services COMMON SERVICES REPOSITORY Discovery Services Security Services App Update Services API Services Data Exchange Services Delivery Services CSR Advertising Documents • • • Role/PIV-based Search Facilities Catalog Views of available Apps based on Role/ID Svc/App updates—location, function, role, software DOE Shared Service User Community Solution architectures, IPTs, Architects, Wireless Users, programmers, etc. 24

Domain Access Control Service/App Update Control Security Services Communicat ion Services Infrastructur e Services Back-Office Apps Business Services/Ap ps Common Service Repository: Domains & Controls Service/App Delivery Control Data Exchange Control 25

Part III: Questions? Leon Cameron NNSA Principal Lead Architect 202 -586 -9764 (desk) leon. cameron@nnsa. doe. gov 202. 430. 2570 (mobile)

Part IV: Backup Slides

Service Access Philosophy: Any Service, at Any Time, from Any Place • Any authorized service requester (IT systems, end-user apps, other web services) can access any service at any time from anywhere • external service requesters must comply with more stringent security requirements Data Models Service Models • Federal Schema • Data Structures • Object Models • DB Schema • Allow service requesters to access & utilize web services: composite services and business processes • Exposing business processes as web services Process Models • Component Interfaces • Legacy Messages • App APIs • Process Re-Engineering • Partner Agreements • B 2 B Processes Service Consumers Service Platform User Roles Sys. MGT BPM Legacy Service-level Security Svc Registry & Lookup Service-level Mmgt Service-level Data Svcs OAP L/S XM Internal user XML Le Wr gacy app ers XML Legacy Composite Services Business Processes F I R E W A L L XML/SOAP 12 -Jan-22 External user 28

Multi-Channel Access 12 -Jan-22 Provisioning applications & services to be available via WEB & wirelessly 29

Part IV. Backup & Additional Information • One. EA Services Architecture Framework • Services Layer • Service Architecture Deployment Roadmap • One. EA Services Principles • Best Practices 30