operational it committee - chief information officer 03.25.2013 meeting... · the strategic it...

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 Email Update (Sandra Germenis) *ASMP Monthly Report (Renee Wallace) *SME Salary Market Data Update (Debra Kress, John Moore)

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 3/13, 9:00-10:30 *ASMP Tech Arch (Julienne VanDerZiel) *BACS to BSC Update (Brad Englert)

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 *NO MEETING* 3/19, 9:00-10:15

R&E 4/16, 9:00-10:15 *TACC Research Support (How to Use TACC) Viz Lab *DAM TF Update (Angela Newell) *LIFT

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

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 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-13 Observe Pennebaker/Gosling Class *Steve Mintz

C-14 3/13, 9-10am *Ed Tech Roadmap Updates (Brad Englert) *LIFT Update (Brad Englert)

C-14 4/7, 9-10am

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)

Canvas Learning Management System - Update

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 2013. Please visit the

Canvas login page for additional information: https://canvas.utexas.edu.

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,845 508 4948 90%

Spring 2014 25% 29% 33,408 984 2917 60%

Fall 2014** 50% 85% 47790 4880 1134 12%

Spring 2015 75% 92% 43299 4915 488 7%

Fall 2015 100% - - - -

* 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 24th- http://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 Email notifications

https://canvas.utexas.edu/

Instructor Counts by CollegeSpring 2015

As of February 11, 2015

50 83 33 1193 226 33 16168 210 42 15209 238 29 12241 313 72 28134 231 97 1650 92 42 439 41 2 015 30 15 2140 196 56 20784 979 195 75430 563 133 3379 84 5 898 102 4 058 78 20 665 78 13 981 140 59 6

2,834 3,684 251Total Campus 2,576 3,341 765 222

Notes:

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.

NumberUsing Canvas

NumberUsing Blackboard

ArchitectureBusiness

Total Number ofInstructors

Number Not YetUsing Canvas

1. The college/school designation is determined from the course being taught.

Intercollegial ProgramsLawLiberal ArtsNatural SciencesNursingPharmacy

CommunicationEducationEngineeringFine ArtsGeosciencesInformation

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.

Public AffairsSocial WorkUndergraduate Studies

2. Count totals by college/school exceed campus totals due to instructors teaching courses in more than one college/school.

ASMP 2.0 Technology Architecture Design and Specifications March, 2015

• Background • TADS Process recap • Administrative systems technical

architecture selections • Updated technical architecture overview • In-progress activities and next steps • Resources and key contacts

2

Presentation Agenda

© 2014 IBM Corporation University of Texas at Austin & IBM Confidential 3

• 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.”

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

Background


ASMP Original Vision

We are Here: ASMP 2.0 must “Define the Triangle”


• 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

Background

3

•Finalize the charter and get sign off from the SME Group.

1. Charter Sign Off

•Business and IT context and requirements for technical architecture.

2. Requirements Document (3C1)

•Technical specifications for the new technology stack

3. Technical Specifications (3S2]

•Identification and evaluation and budgetary estimates. Identify the selection criteria

4. Alternative Solutions (3S1)

•Selected architecture components documented against the UT Austin reference architecture.

5. Solution Selection (3F1)

•Plan for transitioning systems and staff to the new technology stack.

6. Plan to Procure, Deploy, and Transition Staff (3T)

We are here

TADS Process Recap

Administrative Systems Technical Architecture

Business Innovation & Optimization Services

Dev

elop

men

t (L

ifecy

cle)

Se

rvic

es

Interaction Services (View) Process Services (Controller) Information Services (Model)

Partner Services Business Application Services

Access Services

IT Service

Managem

ent

Infrastructure Services

Dashboard access to key process and transaction

metrics, simulations, tests & audits of business

processes & activities

Application Assets Information Assets

Service Reg. & Discovery

Message Format Libraries

‘Logic/Transaction Warehouse’ Model/View/Controller Pattern

and Architecture within Application & Web Servers

Messaging Content Based Routing

Transformation Transaction Integrity

Data Warehouses Repositories & Files

Data Feeds

Packages Custom Applications Core Host Systems

Event Correlation Transport (HTTP, JMS & WS)

Planning & Modeling Scenarios

Activity Monitoring Compliance Controls Performance

Reporting

Utility Business Services

Metering Rating Billing

Settlement

zz Availability

Provisioning

Optimization

Security

Service Level

Automation (QOS & QOP)

& Policy Based

Orchestration

Enterprise Services Bus (ESB)

Reference Architecture Components

Information integration, access, caching & metadata Data federation, replication,

aggregation & publishing Business intelligence,

data mining and analytics

Master Data Integration

‘Single View of…’

Content Management

ILM ETL

Transform to

ITIL Processes

Providers

Consumers

Connectivity/Interaction/Message Types & Protocols Consumers Providers

Bridges, Adaptors, Access & Gateways

Consumers Providers Connectivity/Interaction/Message Types & Protocols

Consumers Connectivity/Interaction/Message Types & Protocols

HTTP, JMS & WS

Providers Consumers Providers Consumers Connectivity/Interaction/Message Types & Protocols Connectivity/Interaction/Message Types & Protocols Connectivity/Interaction/Message Types & Protocols

Portal Services

Collaboration Services Pervasive

Access Services User

Access Services

Web Client

Hybrid Client

Server -Managed

Other Clients

Rol

e B

ased

Channel Integration Processing

Technical Orchestration

(incl WS-*, BPEL4WS..)

Human Workflow Support

Security Services Identity & Access

Virtualization & Grid Services (Software, Hardware, Devices & Equipment) Network

(LAN, WAN, DC)

Facilities & Equipment Physical Resources

Security & Resiliency

Confidentiality

Integrity & Availability (CIA)

Business Modeling

Requirements

Analysis & Design

Test

Configuration & Change Mgt

Project Management

Processes

Architecture & Integration

Portfolio Management

Management & Invocation

Business Operations Orchestration

Layers and Components

8

Layer Components

Legend:

TADS: Selections & Confirmations

Compute Storage Database

9

Reference Architecture: Product Mappings

Development Lifecycle

Services

Configuration & Change

Management

GitHub (new), UTForge

Processes: Continuous

Integration/Delivery

Thoughtworks Go! (new)

Static Code Quality Assurance Sonar Source SonarQube

Python Build Automation and

Runtime

UT PyPE

Build Automation Apache Maven

Load Generation Apache Jmeter

Test and Quality Assurance Parasoft JTest

Parasoft Develop/

Test Platform

Parasoft SOA Test

Parasoft

Load Test

Parasoft

Virtualize

Sauce Labs

Selenium

Layer Component/Subcomponent Product

Purpose: Integrated Environment for design and creation of solution assets

10



Services

Languages Python/Django

Java

Issue Tracking JIRA (enterprise support)

Requirements Jama (new)


11


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

12


IT Service Management

Utility Business Services

• Metering

• Rating

• Billing

• Settlement

Service Level Automation

• Orchestration

• Business Process Management

• Provisioning

• ITIL Processes

• Service Catalog

ServiceNow

(ServiceNow will orchestrate business

processes calling on other systems to

perform specific tasks)


Purpose: Manage and secure services, applications and resources

13


Interaction Services Portal Services

Collaboration Services

• LookingGlass with Campus EAI (new)

• Legacy: UT Direct


Purpose: Enables collaboration between people, processes and information

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

14


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

Management

• EMC Documentum

• Electronic Document Signature • DocuSign


Purpose: Manages diverse data and content in a unified manner


ESB • Transport

• Event Correlation

• Content Based Routing

• Transformation

• Transaction Integrity

• Management & Invocation

• Messaging

• CloudHub iPass

• MuleSoft Virtual Private Cloud (new)

• Amazon SQS, provided via CloudHub ESB

Service Registry &

Discovery

SOA Service Registry and

Repository

• 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

16

Reference Architecture: Product Mappings Layer Component/

Subcomponent

Product

Infrastructure Services Database Oracle Database (Exadata)

MySQL Database

Microsoft SQL

Database

Adabas

Compute Dell PowerEdge Servers

VMware vSphere

IBM Mainframe

Systems

Management

System Center Ops Manager

Windows Server Update

Services

RedHat Satellite Services

Puppet Labs

Puppet

IBM Z/OS

Purpose: Optimizes throughput, availability and performance

17


Subcomponent

Product

Infrastructure Services Storage • Hitachi Storage Arrays

• VSP G1000 (new)

• VSP (existing)

• Hitachi NAS Appliances

• Brocade SAN Fabric

• Dell Compellent

Storage Arrays

Backup and

Restore

• CommVault Simpana

• MS Data Protection Mgr

• Oracle RMAN

• Veeam Backup and

Recovery

18


subcomponent

Product

Infrastructure Services Network

• LAN/WAN/DC • Cisco routing, switching,

and wireless access devices

• Infoblox DNS Appliances

• BIND DNS

• A10 Carrier

Grade NAT

appliances

• Application Delivery

Controller

• A10 Thunder vADC (new)

• F5

• Citrix

Netscaler

• Firewall • Cisco ASA

Security and Resiliency

• IAM • SailPoint

• Authentication • Shibboleth

• SAML2.0/Active Directory/LDAP

• Security Vulnerability

Scanning

• Checkmarx Static Code Analyzer

• Intrusion

Prevention/Detection

• Snort • Cisco

SourceFire

19

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

20

Key New Features Component Products Benefits and Impact


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

• ESB

• Registry/Repository

Amazon SQS message

bus

New middleware for integration

Atomic services

Loose coupling

Will change the way we develop

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)

In Progress

21

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

Next Steps

22

TAI – May, 2015: Start the implementation in earnest • Duration: 16 – 24 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

Resources and Contacts

Review the Selected Architecture completed deliverables • Selected Architecture Components and • Service Catalog Contacts: [email protected] – Technical Architecture Director [email protected] – Enterprise Architect Web Site: http://www.utexas.edu/asmp

24

https://asmp.austin.utexas.edu/techarch/int-sme/test/Draft Deliverables for UT Review/3F1_Selected Architecture Components Documented Against the UT Austin Reference Architecture/CSC Review

mailto:[email protected]

mailto:[email protected]

http://www.utexas.edu/asmp

Questions and Discussion

25

operational it committee - chief information officer 03.25.2013 meeting... · the strategic it...

Documents