Administrative Systems Modernization Program (ASMP 2.0) Technical Architecture Implementation (TAI) Plan Review

Transcription

1 Administrative Systems Modernization Program (ASMP 2.0) Technical Architecture Implementation (TAI) Plan Review

2 Agenda The New Technical Architecture Key Milestones Key Processes Next Steps Questions 2

3 Introduction: TAI Major Milestones 7. Technical Architecture Operations (TAO) 6. Release 4 University Portal, Document Generation, Automated Virtual Environment 5. Software Developer Training Program Redesign 4. Release 3 Jama Full Release, DVCS, Workload Automation 3. Release 2 Exadata, Storage, Infrastructure Monitoring We are here 2. Release 1 - Jama Pilot, Enterprise Service Bus, Electronic Document Signature 1. Technical Architecture Implementation Project Initiation 0. Technical Architecture Design and Specification > COMPLETE!!! 3

4 The New Technical Architecture Our 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

5 The New Technical Architecture: Interim Administrative Systems Technical Architecture 5

6 The New Technical Architecture: 2020 Administrative Systems Technical Architecture 6

7 Major TAI Milestones Release 1 01/2016 Release 2 06/2016 Release 3 11/2016 Release 4 04/2017 TAI Start 05/2015 Release 1 01/2016 Release 2 06/2016 Release 3 11/2016 Release 4 04/ Q Q2 Q3 Q4 Q Today -MuleSoft (Alpha Release) -Jama (Alpha Release) -Oracle Database Hosting (General Release) -MuleSoft (General Release) Q2 Q3 Q4 Q Oracle Exadata -IaaS Backup and Restore -IaaS One Stop Shop -EMC Documentum -Open Text Brava Viewer -Splunk -Zenoss SaaS -MySQL -Stonebranch -Kofax Products -ADC: Citrix Netscaler -IaaS Windows -Linux Mgmt Tools -Checkmarx Static Code Analyser -GitHub Enterprise -Sauce Labs -SeleniumHQ -Sonar Source SonarQube -Portal as a Service -Kofax Multifunction Capture -Exoprise -New Relic SaaS -Apache Jmeter -Apache Maven -Jenkins -JIRA -Parasoft -Development Testing Platform -Thoughtworks Go! -HP Exstream: Document Generation 7

8 Key Processes: Key Document Overview Five major documents are interrelated and share a common numbering system Technical Release Schedule Product release sequence based on UT requirements and priorities. Methodology Diagrams Visual depiction of Release Management and Service Deployment workflows. Technical Description of Work Detailed description of each major step in the methodology. Project Workplan Detailed plan to implement products and Services via Technical Releases. Future Architecture Diagrams Visual depiction of the future Architecture and Services. 8

9 Key Processes: Organizational Change Management Overview Change Readiness Change Impact Assessments, Role Mapping, Skill Gap Analysis for Service Providers Provide data, tools, and templates to CSUs for Role Mapping Stakeholder Engagement Focus Groups Key Stakeholder Interviews Communication FYI Sessions & Newsletters Messages & Training Invitations/Availability Notifications Training Plan & Coordinate Training for Service Providers & Service Consumers Redesign the Software Developer Training Program (SDTP) 9

10 Key Processes: Release Methodology Diagram Initialize Release Release Approval (By Service) Configure & Build Operational Readiness (By Service) Quality Assurance (By Service) Candidate Approval (By Service) Implementation Post- Implementation 10

11 Key Processes: Service Deployment Methodology Identify Service Capacity Management Acquire Prepare Define Operational Process Define Institutionalization Process Deploy Early Adopter Implementation Sunset 11

12 Key Processes: Alpha Users Early Service Consumers that have a business need to begin 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

13 Name Next Steps: Major Upcoming Deliverables Start TAI Begins 05/2015 TAI Organizational Change Management Strategy 06/2015 TAI Stakeholder Management Strategy 06/2015 Service Deployment Playbook 06/2015 Release Management Playbook 06/2015 TAI Project Plan 06/2015 TAI Organization Design Strategy 07/2015 Release Deployment Training for UT 07/2015 Service Deployment Training for UT 07/2015 TAI Communications Strategy 07/2015 App Mod Org Design Toolkit for TAI Release I 08/2015 TAI Training Strategy 08/2015 TAI Service Design Package - Enterprise Service Bus (ESB) 08/2015

14 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 14

15 Questions? 15