1 / 22

Report on the Architecture Framework Advisory Committee

Report on the Architecture Framework Advisory Committee. Presentation to the Information Technology Infrastructure Roundtable June 17, 2013 Beno î t Long Chair, Architecture Framework Advisory Committee Senior Assistant Deputy Minister, Transformation, Service Strategy and Design. Outline.

verna
Télécharger la présentation

Report on the Architecture Framework Advisory Committee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Report on the Architecture Framework Advisory Committee Presentation to the Information Technology Infrastructure Roundtable June 17, 2013 Benoît Long Chair, Architecture Framework Advisory Committee Senior Assistant Deputy Minister, Transformation, Service Strategy and Design

  2. Outline • Architecture Framework Advisory Committee (AFAC)Agenda and Workplan • Shared Services Canada & Converged Communications • Objectives • Transport Models • Opportunities and Challenges • AFAC Feedback • Annex • Participants • Converged Communication Models Examined • Deployment Model Considerations

  3. AFAC Agenda and Workplan

  4. Conceptual End State • Security • All departments share one enterprise/common zone • Access to sensitive departmental data is secured through restricted zones • Developers do not have access to production infrastructure • Classified information below Top Secret • Consolidated, controlled, secure perimeters • Balance security and consolidation • Certified and Accredited infrastructure Internet Virtual Private Cloud Consolidation Principles As few wide area networks as possible All departments share network access in multi-tenant buildings Network equipment is shared Telecom hubs (call managers, videoconference (VC) bridges) located in enterprise data centres or common points of presence Inter-data centre connections should be diverse and fully redundant Scalable and flexible infrastructure Performance levels should be similar wherever possible Contracts/services will be consolidated Public Cloud Services C2G Dev2 B2G G2G Sci1 Dev1 Classified Data Confidential Several, highly-secure Internet access points Application Service Levels Secret GCNet International Carriers Regional Carriers Standard (3480 buildings) Enhanced Regional WANAccelerators Mission Critical Production Prod2 Production Prod3 Prod4 Prod1 ServiceLevel ServiceLevel … U U U A S U U WorkloadMobility S B B C B Development • Application Migration • Standard platforms and product versions • Migration guidance • Committed timeline for product evolution Protected Data Lifecycle A Protected A Enterprise Security B Protected B HPC • Characteristics • Integrated (single, common, secure GC network will link all service delivery points) • High performance • Secure • Cost-effective • Standardized (based on open standards, modularized design) • Mobile (wireless technology will be maximized where cost-effective) • Responsive and resilient Enterprise Security Stand-alone centre for GC super-computing (HPC) – e.g. Weather C Protected C C S GC Private Domain Converged Communications Mobility Contact Centre • Consolidated services • IP-based infrastructure • Higher speed, • Ubiquitous connectivity • Business Intent • Business to Government • Government to Government • Citizens to Government Data Voice Video • Modernize • IP Telephony • Increase security • Consolidate zones • Rationalized VC bridges • Shared VC boardrooms

  5. Telecommunications Services End State Converged Networks and Unified Capabilities Video Enterprise Network Convergence Contact Centres Conferencing Voice Data GC Unified Capabilities Enhance capabilities of partner departments to better serve Canadians

  6. Landscape of Converged Communication Services • Identity Mgmt • Authentication Services • Public Certificates • ICAM Element Collaboration Services Directory Services • Wikis • Blogs • RSS • Conferencing • Drop-boxes • Account Provisioning • Address Books • Distribution Lists • Routing • Aliasing • Notification • Calendaring • Public Folders Messaging Services Email Services Converged Communications • Email Archiving • Message Search • Public Folders • Attachments • Email Classification • Chat • Mobile Support Enterprise Content Management and Storage Services • Converged Voice/Data/Video • IP Telephony • Instant Messaging • Conferencing(Web/ Audio/Video) • Presence • FAX • Content Archiving • Records Mgmt • Enterprise Library • Enterprise Search • Data De-Duplication • Tiered Storage

  7. Converged CommunicationsComponents IP Telephony Instant Messaging Email & Calendaring CC Core Services IP network Videoconferencing (VC) CC Client Data Centre Web Conferencing CC User Can be on different devices (PC, Mobile, Tablet,…) Presence FAX Directory

  8. GC Converged Communications End State Single Government of Canada (GC) network capable of carrying all services with consistent functionality to all users Single simplified sign-on to all authorized converged communication (CC) functionality based on a single GC directory and credential Single presence store for all GC users Single non-proprietary standards based platform for all converged communications services

  9. GC Converged Communications Enterprise Requirements Available anytime, on any device, from anywhere Device independent look and feel Intuitive, simple user-interface that is presence and directory enabled Secure up to a Secret level of sensitivity Supports government to government (G2G), government to business (G2B) and government to public (G2P) multi-modal communications

  10. Key Challenges Collaboration services not in scope (i.e. not unified communications) Email and calendaring being implemented separately May be challenging to integrate with the other services Pockets of Internet Protocol (IP) telephony and Unified Communications-base already installed Multiple departmental implementations Leveraging existing multi-vendor VC infrastructure Interoperability limited between vendors Foundational services still in departmental silos (e.g. active directories, identity credential access management, etc) Multi-network environment for the next few years

  11. Converged CommunicationsThree-Tier Architecture Services/Applications Directory DNS IP Telephony Service IM/PresenceService Videoconferencing Service Core Services WebconferencingService Standard Protocols (SIP,H.264,G.711,SRTP,etc) Session Management Standard Protocols (SIP,H.264,G.711,SRTP,etc) Access/Connectivity/User Devices Networks

  12. Potential Deployment Models (Presented at AFAC) Option 1 • One winner takes all • Network and Services Network (Not recommended) Services Services Services Services Option 2 #2 • Network single provider • Services multi-provider Network Services Services Services Services Option 3 • Regional integration of Network and Services RegionalNetwork + Services RegionalNetwork + Services RegionalNetwork + Services RegionalNetwork + Services (Not recommended) #3 Option 4 • Network multi-provider • Services multi-provider • Most complex to manage Network Network Network Network Services Services Services Services

  13. Potential Deployment Models (Presented at AFAC) • Network multi-provider (potentially single provider) • Services single provider for each service type (eg. voice)(Recommended option) Option 5 #1 Network Network Network Network Service A Service B • IP Telephony Services • Videoconferencing Bridging • Web Conferencing • Audio Conferencing • Contact Centre Services • Toll Free Services Service C Service D Service E Option 6 • Network multi-provider • Services single provider for integrated national converged communications service (voice, video and contact center) Network Network Network Network National Integrated Converged Communications Solution (Not recommended)

  14. Converged Communications Service Architecture IaaS LAN PaaS Desktop IaaS Regional WAN Transport IaaS WiFI User Email Services IP Tel IaaS National Backbone Transport Converged Communications Scope IaaS Cloud LAN Not in Scope IaaS Regional WAN Transport Web Conf. Contact Ctr. In Scope Transport Video Conf. Presence PaaS Audio Conf. Broker Services/ Orchest. PaaS SEC1 Firewall PaaS Directory SaaS MyKey Future Services SaaS IPTel IaaS Net ISP1 IaaS I-Net Gate IaaS DC LAN Identity & Access Mgmt. SaaS Fax Services SaaS Contact Ctr. SaaS Instant Msg. SaaS Video Conf. SaaS Email IaaS x86 SaaS Web Conf. *GSM - Generic Service Model, A generic framework for describing a Service in terms of its systematic hierarchy of related service objects.

  15. Recommendations Consensus Additional Engagement Required Overall architectural approach is sound Three tier architectural framework is accepted Network should be decoupled from converged communications services from architectural and procurement perspective QoS on network will be important to deliver voice and videoconferencing services • Procurement approach for network and converged communications services? • Framework used for three-tier model needs further input? • Network services deployment model (e.g. national or regional)? • Bundling model for converged communications services? • Best way to deliver QoS over multi-vendor networks? • Bring Your Own Device approaches?

  16. Possible Upcoming Topics (Core/Foundational Services) • Core/foundational services • Enterprise identity credential access management (ICAM) • Directory services • Internet Protocol addressing (IPv4, IPv6) • DNS/DHCP • Network operations centre/security operations centre • Distributed and workplace computing environments (including devices) • Service management • Service catalogue

  17. Next Steps Government of Canada Network (wide area network) – industry consultation (planned for early July 2013) Converged communications/IP telephony industry engagement - in Fall 2013 (date to be confirmed) Next AFAC meetings – focused ICAM in July 2013

  18. Annex

  19. Deployment Model - Considerations

  20. Potential Service Bundling (for recommended option)

  21. AFAC Participants: Converged Communication

  22. AFAC Participants Continued: Converged Communication

More Related