N e t wo r k A rc h i te c t u re C h a n g e - E n d o r s e
OverviewNetworking is introducing new architecture and funding models to support increased compliance andsecurity demands, while managing complexity, capability and cost.
ChangesA. Architectural:
1) Introduction of virtual campus network layers (Figure 1)
Utilizes technology known as Multi Protocol Labeled Switching (MPLS)
Due to the complexity, there must be a campus-wide need for another layer
2) Consolidation of equipment to more capable products that also support MPLS
Four Cisco product lines to one— will take years due to lifecycles
3) Implement shared infrastructure for small sites to reduce costs (Figure 2)
B. Funding:
1) Any new virtual layer requires recurring funding commitments:
Committed (~$200K/year): ITS-BACS, ITS-VoIP, Facilities and Utilities
Uncommitted: Medical, PCI (credit cards), 3rd Party ISP (non-UT network)
Common Good: UTnet (and its management networks)
2) Small sites move to rental model for building router (at lower annualized cost), or, optionally, compliant equipment at higher cost
Why Now Compliance/Security: audit finding for Facilities Network; medical school needs
Savings: Estimate 20% for small sites ($1M over 6 years) Maturity: maturation of MPLS; support across campus inventory; new vendor products Funding: UT System $500K grant to implement MPLS and requisite border firewall
IT Governance V 1.6 May 5, 2015
Figure 1
VoIPBACS
General General
Medical/HIPPA BuildingSystems
Single Layer Mul ple Layers
Figure 2
ASMP 2.0 SteeringStatus Update
June 24, 2015
Overall Program Status
Restructuring underway to ensure success More Workday involvement More scope assumed by UT team
Coordination with Shared Services andServiceNow activities
ASMP 2.0 | The University of Texas-Austin
PMO – Standards and Methodologies
Working Group Formed and Meeting Builds Upon ASMP Work Group 5 - Initiative 3.1
and Standards and Methodologies Task Force Objectives:
Review IBM Deliverable (August 2015 targetedcompletion)
Guidance on Rollout, Adoption, and Verification
ASMP 2.0 | The University of Texas-Austin
ERP Implementation
HCM/Payroll Wrapping up the Architecture Stage, and
beginning the Configuration and Prototype Stage
Configuring business processes Developing solutions to gaps identified Completing first true conversion of data Finalizing list of interfaces to be developed
ASMP 2.0 | The University of Texas-Austin
ERP Implementation
Financials Wrapping up the Planning Stage, and getting
ready to start Architect Stage Finalizing the work plan Preparing for initial design workshops starting
on July 14 Finalizing the Financial Data Model (FDM)
ASMP 2.0 | The University of Texas-Austin
Enterprise Readiness
Finalizing the Organizational Transition Strategy Defines how program will work with CSUs to
successfully transition to new systems
Working with HCM/Payroll team to identifychange impacts
We are here 1. Technical Architecture Implementation Project Initiation
0. Technical Architecture Design and Specification > COMPLETE!!!3
The New Technical ArchitectureOur Mission:
• Provide production and development environments that support cloud, package, and custom applications for Administrative units and their interfaces.
• Provide an Administrative Systems Technical Architecture that is component-based, flexible, predictable, resilient, secure, and scalable.
• Enable University developers to focus their IT skills on solving business problems, not figuring out architecture, tools, and environments.
• Follow ITIL and CMMI practices to build environments, processes, and tools that support these goals.
4
TEXAS-11r AUS1tN-
WHAT STARTS HERE CHANGES THE WORLD
The New Technical Architecture:
lfj f
II!J.,.r
"
Interim Administrative Systems Technical ArchitectureTAlInterim Systems Architecture
Th'! tollovvirg diagram shows a 1igh le'lel ·liew ot tnajor a j ministrat ve System.en:te-chnical arcl"ite-c ure a: VT a nd '''here they res :!e.I·:.om L<:IH, l11f.' d iogr em )howf u lu r)y.h:-m:. ll ro l :.Il l.' r w .\'f.'l ou liu.. lJL.t <!I f.' l.n: i u....:IIHtd.
Key Processes: Service Deployment MethodologyIdentify
Service CapacityManagement
AcquirePrepare
Define OperationalProcess
DefineInstitutionalization
Process DeployEarly Adopter
ImplementationSunset
11
Key Processes: Alpha Users
• Early Service Consumers that have a business need tobegin early use of service
• Service is not yet deployed nor fully supported:– Training may or may not be available– Incomplete/unstable environments– “Best Effort” support model– Effort matures over time and service nears deployment
readiness
• Reconfiguration or Refactoring may be needed as processes and standards are defined
• Required to collaborate, provide feedback and work closely with Service Owner
12
Next Steps:Major Upcoming Deliverables
Name StartTAI Begins 05/2015TAI Organizational Change Management Strategy 06/2015TAI Stakeholder Management Strategy 06/2015Service Deployment Playbook 06/2015Release Management Playbook 06/2015TAI Project Plan 06/2015TAI Organization Design Strategy 07/2015Release Deployment Training for UT 07/2015Service Deployment Training for UT 07/2015TAI Communications Strategy 07/2015App Mod Org Design Toolkit for TAI Release I 08/2015TAI Training Strategy 08/2015TAI Service Design Package - Enterprise Service Bus (ESB) 08/2015
Next Steps: Release 1
• Release 1 Implementation date – 01/2016• Services in scope
– IaaS - Compute and Storage– IaaS - System Administration– Application Lifecycle Management
• Requirements Management• Jama Product Pilot
– Integration Services• Enterprise Service Bus• Message Service• API Registry
