Operational IT Committee

Transcription

1 Operational IT Committee 3:00 4:00 p.m., March 25, FAC 228D I. Canvas Update (David Moss, Mario Guerra) II. Administrative Systems Modernization Program Technical Architecture Discussion (Julienne VanDerZiel, Eric Weigel) III. Administrative Systems Modernization Program Update (Renee Wallace) March April BSC 3/6, 1:30-3:00 *ASMP Tech Arch (Julienne VanDerZiel) *WiFi Change - Update (William Green) *Calendaring and Update (Sandra Germenis) *ASMP Monthly Report (Renee Wallace) *SME Salary Market Data Update (Debra Kress, John Moore) AIC 3/13, 9:00-10:30 *ASMP Tech Arch (Julienne VanDerZiel) *BACS to BSC Update (Brad Englert) R&E *NO MEETING* 3/19, 9:00-10:15 BSC 4/3, 1:30-3:00 *ASMP Update (Renee Wallace) *BACS Removal Strategy Charter (Mike Cunningham) *Training Management System (Kati Elliot) *ASMP Tech Arch (Julienne VanDerZiel) *AITL and ABL Updates AIC 4/10, 9:00-10:30 *UT Web Update (Dave Moss) *Infrastructure as a Service Charter (Cam Beasley, William Green) *ASMP Tech Arch (Julienne VanDerZiel) *WITI Update (Jennifer Chance) *TSC Certification Training Update (Sandra, Cam) *Commodity Server Update (Cam, William) R&E 4/16, 9:00-10:15 *TACC Research Support (How to Use TACC) Viz Lab *DAM TF Update (Angela Newell) *LIFT

2 OIT 3/25, 3:00-4:00 *Canvas Update (Dave Moss, Mario Guerra) *ASMP Tech Arch (Julienne VanDerZiel) *ASMP (Renee Wallace) *CCP Update (Kristi Fisher) *Committee Updates C-13 3/2, 2:15-3:15 *Ed Technology Roadmap Updates - Endorse (Brad Englert) *Canvas Update (Mario Guerra, Dave Moss) *Digital Preservation Network (Brad Englert) *LIFT Update (Brad Englert) C-14 3/13, 9-10am OIT 4/22, 3:00-4:00 *ASMP (Renee Wallace) *Service Retirements (Heath and Zero-Based Budget) *TSC Certification Program Update (Sandra Germenis, Cam Beasley) *Committee Updates C-13 Observe Pennebaker/Gosling Class *Steve Mintz C-14 4/7, 9-10am *Ed Tech Roadmap Updates (Brad Englert) *LIFT Update (Brad Englert) SITAB SITAB April 16, 2:00-3:00 p.m., Stark Library *Canvas Update (Mario Guerra, Dave Moss) *VoIP Update (William Green, John Lovelace) *TSC Certification Update (Sandra Germenis, Cam Beasley) *ASMP Update (Renee Wallace)

3 Canvas Learning Management System Update Background After a comprehensive evaluation led collaboratively by the Center for Teaching & Learning and Information Technology Services, Canvas was selected in June 2013 to replace Blackboard by a steering committee comprised of faculty, students, and staff. The Strategic IT Accountability Board (SITAB) subsequently endorsed this recommendation in July Please visit the Canvas login page for additional information: Migration Update Upon selection, a two-year migration plan was created that enabled a phased transition from Blackboard to Canvas. Canvas Adoption by Semester % Faculty Using Canvas (Goal)* % Faculty Using Canvas (Actual)* Number of Students Number of Canvas Courses Number of Bb Courses % Faculty using Bb * Fall 2013 N/A 15% 27, % Spring % 29% 33, % Fall 2014** 50% 85% % Spring % 92% % Fall % * Based on total number of faculty using Blackboard or Canvas. **Beginning Fall 2014, all courses were created in Canvas by default. Training and Support Opportunities Instructure 24x7 support Canvas Training Center Instructor-led workshops, weekly office hours and one-on-one consultations Migration support (over 500) Canvaspalooza (Fall 14) Spring Into Canvas Instructor Poster Session April 24thhttp://canvas.utexas.edu/events Fall 2014 Survey Results ~2300 Faculty responses o 76% either satisfied or extremely satisfied with Canvas o 57% reported using Canvas instructionally different than Blackboard Some differences include the use of Rubrics and Assignment feedback ~3000 Student response o 81% either satisfied or extremely satisfied with Canvas o Favorite tools in Canvas What-If grade, Dashboard, and notifications Canvas Learning Management System - Update

4 Instructor Counts by College Spring 2015 As of February 11, 2015 College/School Number Using Canvas Total Number of Instructors Number Not Yet Using Canvas Number Using Blackboard Architecture Business Communication Education Engineering Fine Arts Geosciences Information Intercollegial Programs Law Liberal Arts Natural Sciences Nursing Pharmacy Public Affairs Social Work Undergraduate Studies ,834 3, Total Campus 2,576 3, Notes: 1. The college/school designation is determined from the course being taught. 2. Count totals by college/school exceed campus totals due to instructors teaching courses in more than one college/school. 3. The number of instructors not using Canvas is calculated by subracting the number using Canvas from the total number of instructors. That it is greater than the number of instructors using Blackboard indicates that some instructors use neither Canvas nor Blackboard. 4. The number of instructors using Blackboard is a better indicator of the effort remaining in transitioning to Canvas than the number of instructors not yet using Canvas. 5. These counts have changed since the start of the semester as some instructors have decided to use Canvas, while others initially opting for Canvas have decided they are not quite ready.

5 ASMP 2.0 Technology Architecture Design and Specifications March, 2015

6 Presentation Agenda Background TADS Process recap Administrative systems technical architecture selections Updated technical architecture overview In-progress activities and next steps Resources and key contacts 2

7 Background 2004: The University of Texas at Austin s Commission of 125 Spoke to the need to actively pursue innovative solutions in all facets of IT: In a world increasingly dependent upon innovative information systems, it will be impossible to reach these goals unless the University maintains its leadership in information technology 2009: Recommendation 9.1 of the SITAC report initiated this effort to create an Administrative Systems Master Plan (ASMP) Creation of a Master Plan for campus wide administrative systems will clearly align resources and investments with the University s mission and goals. By providing a comprehensive roadmap for work ahead, the Master Plan will encourage coordination and collaboration between business areas and within the development community. 3 University of Texas at Austin & IBM Confidential 2014 IBM Corporation

8 Background 2012: Administrative System Master Plan (ASMP) Migrating the University s administrative systems to a modern infrastructure is vital in order to take advantage of new technologies, provide new services that are currently difficult to offer, and avoid the risks of depending on obsolete technologies. Requirement 2: Modernize the Administrative IT Infrastructure Initiative 2.1: Design and Build an Open Systems Technical Environment Requirement 3: Strengthen the Systems Development Processes Initiative 3.1: Adopt Common Software Development Methodology 4 University of Texas at Austin & IBM Confidential 2014 IBM Corporation

9 ASMP Original Vision We are Here: ASMP 2.0 must Define the Triangle 5 University of Texas at Austin & IBM Confidential 2014 IBM Corporation

10 Background 2014: Administrative System Modernization Program (ASMP 2.0) Business Services Committee asks Architecture Infrastructure Committee and Administrative IT Leaders to oversee governance of the new technology and standards portion of the program Technology Architecture team begins first project: Technology Architecture Design and Specification (TADS) Community and governance involvement through Subject Area groups, Customer Steering Committee, community updates and feedback session and representative selection committees. Outcomes 55 solution assessments 20 new approved solution selections 6 University of Texas at Austin & IBM Confidential 2014 IBM Corporation

11 TADS Process Recap We are here 1. Charter Sign Off 2. Requirements Document (3C1) 3. Technical Specifications (3S2] 4. Alternative Solutions (3S1) 5. Solution Selection (3F1) 6. Plan to Procure, Deploy, and Transition Staff (3T) Finalize the charter and get sign off from the SME Group. Business and IT context and requirements for technical architecture. Technical specifications for the new technology stack Identification and evaluation and budgetary estimates. Identify the selection criteria Selected architecture components documented against the UT Austin reference architecture. Plan for transitioning systems and staff to the new technology stack. 3

12 Administrative Systems Technical Architecture Layers and Components Reference Architecture Components Legend: Layer Components Development (Lifecycle) Services Business Modeling Architecture & Integration Processes Requirements Analysis & Design Test Configuration & Change Mgt Project Management Portfolio Management Business Innovation & Optimization Services Controls Interaction Services (View) Process Services (Controller) Information Services (Model) Transport (HTTP, JMS & WS) Event Correlation Partner Services Message Format Libraries Activity Monitoring Portal Server -Managed Services Collaboration Web Client Services Pervasive Hybrid Client Access Services Other Clients User Access Services Connectivity/Interaction/Message Types & Protocols Consumers Management & Invocation Role Based Consumers Providers Connectivity/Interaction/Message Types & Protocols Planning & Modeling Scenarios Human Workflow Support Compliance Business Operations Orchestration Technical Orchestration (incl WS-*, BPEL4WS..) Service Reg. & Discovery Security Services Identity & Access Connectivity/Interaction/Message Types & Protocols Consumers Providers Enterprise Services Bus (ESB) Consumers Providers Connectivity/Interaction/Message Types & Protocols Business Application Services HTTP, JMS & WS Logic/Transaction Warehouse Model/View/Controller Pattern and Architecture within Application & Web Servers Channel Integration Processing Performance Reporting Information integration, access, caching & metadata Data federation, replication, aggregation & publishing Messaging Content Based Routing Transform to Dashboard access to key process and transaction metrics, simulations, tests & audits of business processes & activities Content Management Business intelligence, data mining and analytics ILM ETL Connectivity/Interaction/Message Types & Protocols Consumers Providers Transformation Transaction Integrity Access Services Master Data Integration Single View of Consumers Providers Connectivity/Interaction/Message Types & Protocols Bridges, Adaptors, Access & Gateways Application Assets Information Assets Packages Data Warehouses Custom Applications Repositories & Files Core Host Systems Data Feeds IT Service Management Utility Business Services Metering Rating Billing Settlement Service Level Automation (QOS & QOP) & Policy Based Orchestration Availability zz Security Optimization Provisioning ITIL Processes Infrastructure Services Virtualization & Grid Services (Software, Hardware, Devices & Equipment) Compute Storage Database Physical Resources Facilities & Equipment Network (LAN, WAN, DC) Security & Resiliency Confidentiality Integrity & Availability (CIA) TADS: Selections & Confirmations 8

13 Reference Architecture: Product Mappings Layer Component/Subcomponent Product Development Lifecycle Configuration & Change GitHub (new), UTForge Services Management Processes: Continuous Thoughtworks Go! (new) Integration/Delivery Static Code Quality Assurance Sonar Source SonarQube Python Build Automation and UT PyPE Runtime Build Automation Apache Maven Load Generation Apache Jmeter Test and Quality Assurance Parasoft JTest Parasoft Parasoft Develop/ Load Test Test Platform Parasoft Parasoft SOA Test Virtualize Sauce Labs Selenium Purpose: Integrated Environment for design and creation of solution assets 9

14 Reference Architecture: Product Mappings Layer Component/Subcomponent Product Development Lifecycle Languages Python/Django Services Java Issue Tracking JIRA (enterprise support) Requirements Jama (new) 10

15 Reference Architecture: Product Mappings Layer Component/Subcomponent Product Business Innovation and Optimization Services Activity Monitoring New Relic (new) providing Application Performance Monitoring Activity Monitoring (basic) Infrastructure Monitoring Zenoss SaaS Cloud Service Monitoring ThousandEyes Exoprise Logging Splunk Purpose: Provide for better decision making with real-time information 11

16 Reference Architecture: Product Mappings Layer Component/Subcomponent Product IT Service Management Utility Business Services ServiceNow Metering Rating (ServiceNow will orchestrate business Billing processes calling on other systems to Settlement perform specific tasks) Service Level Automation Orchestration Business Process Management Provisioning ITIL Processes Service Catalog Purpose: Manage and secure services, applications and resources 12

17 Reference Architecture: Product Mappings Layer Component/Subcomponent Product Interaction Services Portal Services LookingGlass with Campus EAI (new) Collaboration Services Legacy: UT Direct Purpose: Enables collaboration between people, processes and information Layer Component/Subcomponent Product Process Services Technical Orchestration Job Scheduling SFTP Human Workflow Support Stonebranch (new) Universal Automation Center Universal Controller Universal Agent Universal Data Mover Cleo VL Trader Task Manager (mainframe) Purpose: Orchestrate and automate business processes 13

18 Reference Architecture: Product Mappings Layer Component/Subcomponent Product Information Services Information Integration Data Federation Business Intelligence Master Data Integration ETL Institutional Data Store (Supported by Enterprise Data and Application Modernization, and IQ) Content Management Document Generation HP Exstream Capture Kofax Capture Kofax KTM Kofax Insight Kofax KFS Electronic Content EMC Documentum Management Electronic Document Signature DocuSign Purpose: Manages diverse data and content in a unified manner 14

19 Reference Architecture: Product Mappings Layer Component/Subcomponent Product ESB Service Registry & Discovery Transport Event Correlation Content Based Routing Transformation Transaction Integrity Management & Invocation Messaging SOA Service Registry and Repository CloudHub ipass MuleSoft Virtual Private Cloud (new) Amazon SQS, provided via CloudHub ESB Mulesoft API Designer Mulesoft API Manager Mulesoft API Portal Mulesoft API Analytics Mulesoft Anypoint Studio Purpose: Enable connectivity between services Note: ESB, Business Application Services, and Access Services are combined on this slide. 15

20 Reference Architecture: Product Mappings Layer Component/ Product Subcomponent Infrastructure Services Database Oracle Database (Exadata) MySQL Database Compute Dell PowerEdge Servers VMware vsphere Systems Management System Center Ops Manager Windows Server Update Services RedHat Satellite Services Microsoft SQL Database Adabas IBM Mainframe Puppet Labs Puppet IBM Z/OS Purpose: Optimizes throughput, availability and performance 16

21 Reference Architecture: Product Mappings Layer Component/ Subcomponent Product Infrastructure Services Storage Hitachi Storage Arrays VSP G1000 (new) VSP (existing) Hitachi NAS Appliances Brocade SAN Fabric Backup and Restore CommVault Simpana MS Data Protection Mgr Dell Compellent Storage Arrays Oracle RMAN Veeam Backup and Recovery 17

22 Reference Architecture: Product Mappings Layer Infrastructure Services Component/ subcomponent Network Product LAN/WAN/DC Cisco routing, switching, and wireless access devices Infoblox DNS Appliances Application Delivery A10 Thunder vadc (new) Controller F5 Firewall Cisco ASA Security and Resiliency IAM SailPoint Authentication Shibboleth SAML2.0/Active Directory/LDAP Security Vulnerability Checkmarx Static Code Analyzer Scanning Intrusion Prevention/Detection BIND DNS A10 Carrier Grade NAT appliances Citrix Netscaler Snort Cisco SourceFire 18

23 Key New Features Component Products Benefits and Impact Content Management Kofax New intelligent capture Current selection Enterprise support Documentum New core content repository Will replace legacy systems HP Exstream Document Generation Will be needed to retire the mainframe Great user interface Network A10 Global Load Balancing Requirements Management Jama New tool tracks versions of requirements Traceability through the process Ties into testing 19

24 Key New Features Component Products Benefits and Impact Development Lifecycle Services GitHub Distributed Version Control System (DVCS) Will replace UTForge ThoughtWorks Go Continuous Integration/Continuous Deployment (CI/CD) Security & Resiliency Checkmarx Static Code Analysis Integration Mulesoft New middleware for integration ESB Atomic services Registry/Repository Loose coupling Will change the way we develop Amazon SQS message bus 20

25 In Progress TADS Technical Architecture Design and Specification Complete Plan to Procure, Deploy, and Transition Staff TAI Technical Architecture Implementation Proof of Concepts Application Delivery Controllers Backup/Recovery Procurement and Sizing ESB Storage Database (Exadata) 21

26 Next Steps TADS Technical Architecture Design and Specification April 2015: Complete the Plan to Procure, Deploy, and Transition Systems and Staff TAI Technical Architecture Implementation Procure priority hardware and software ESB Storage Database (Exadata) Proof of Concepts (POC) Wrap up in-progress POCs Start POCs for Zenoss and Stonebranch/SFTP 22

27 TAI May, 2015: Start the implementation in earnest Duration: months Four releases Starting What is planned for Release 1? Integration Services the MuleSoft ESB Jama requirements tool basic functionality Foundational Infrastructure Components Storage Supporting business processes Next Steps 23

28 Resources and Contacts Review the Selected Architecture completed deliverables Selected Architecture Components and Service Catalog Contacts: Technical Architecture Director Enterprise Architect Web Site: 24

29 Questions and Discussion 25