middleware 101 dave tomcheck uc irvine. overview drivers and assumptions objectives the components...
TRANSCRIPT
Middleware 101Middleware 101
Dave TomcheckDave TomcheckUC IrvineUC Irvine
Overview
• Drivers and Assumptions
• Objectives
• The Components of the Business Architecture
• Implications for Stakeholders
Drivers & Assumptions
• Unprecedented Growth of Enrollments: 2000-2012
• Admin Resources Will Not Increase In Proportion to Campus Growth
• Increase in Complexity of Fed & State Relationship
• Competitive Labor Market
• New Staff Will Not Have Adequate Skills/Training
• Technology is Changing the Way Business is Conducted
Drivers & Assumptions
Why a New Business Architecture?
• A Vision to Stimulate Initiatives
• A Context for Setting Priorities
• Strategies to Increase Staff Productivity
• Communication of Business & Infrastructure Requirements
Members of the New Business Architecture Planning Group
Steven Barclay, San FranciscoJudith Boyette, HR (OP)Wendell Brase, IrvineAnne Broome, Controller (OP)James Dolgonas, CIO (OP)Kristine Hafner, StaffSam Morabito, Los AngelesSteven Relyea, San DiegoThomas Vani, Santa Cruz
Key Components of a New Business Architecture
Page 7 of ReportPage 7 of Report
Page 7 of ReportPage 7 of Report
Integration of business Integration of business transactions with policies, transactions with policies,
guidance, and trainingguidance, and training
A New Business Architecture for UC
Page 7 of ReportPage 7 of Report
Establish UC as a Establish UC as a competitive employer and competitive employer and provide staff the tools to provide staff the tools to
succeedsucceed
A New Business Architecture for UC
Page 7 of ReportPage 7 of Report
Redesign Processes to Redesign Processes to facilitate getting work facilitate getting work
done rather than cover all done rather than cover all potential transactionspotential transactions
A New Business Architecture for UC
Page 7 of ReportPage 7 of Report
Authenticate, authorize, Authenticate, authorize, provide effective toolsprovide effective tools
A New Business Architecture for UC
Page 7 of ReportPage 7 of Report
A New Business Architecture for UC
Employ emerging Employ emerging standards to improve standards to improve integration of financial integration of financial
datadata
Page 7 of ReportPage 7 of Report
A New Business Architecture for UC
Embed performance metrics Embed performance metrics into the way UC conducts its into the way UC conducts its
business and strengthen business and strengthen financial controlsfinancial controls
DepartmentsDepartments
CentralCentralOfficesOffices
Where are Support Costs?
Pages 8-11 of ReportPages 8-11 of Report
• Single Authentication/Authorization (Lightfoot Model)
• Establish Super-Intuitive Navigation
• Integrate Information, Transactions, Training, Templates
Business Portal
• Focus on Those New To Roles
• Develop Content that is Simple, Relevant, Recent
• Move From HTML to Content Management System
Business Portal
Pages 8-11 of ReportPages 8-11 of Report
• UC as an Employer of Choice
• New Application Processes Designed for Candidates
• Flexible and Effective On-Line Training
• Baseline Skills Development thru the Portal
• Providing Intuitive Tools to Ensure Staff Success
People
Pages 12-17 of ReportPages 12-17 of Report
• Initiate Aggressive Program to Eliminate Paper-Based Processes
• Integrate Policies and Procedures into Applications
• Remove Non-Value Added Steps
• Ensure Performance Metrics are Built-In To Processes
Processes/Policies
Pages 18-22 of ReportPages 18-22 of Report
• Move From Proprietary Systems to Standards
• Promote A Model that Emphasizes Users & Departments
• Make All Business Processing Web-Based
• Ensure Adequate Security & Authentication
• Identify & Develop Self-Service Applications
Enabling Technology
Pages 23-27 of ReportPages 23-27 of Report
• Provide All Financial Reporting & Transactions on Web
• Provide Flexible Dept. Tools for Projections & Modeling
• Use XML Protocol to Link All Campus Financial Systems
Financial Systems
Pages 28-32 of ReportPages 28-32 of Report
Financial Systems
• A Portal (By Itself) is Not the Whole Answer
• Shift Thinking from Static Web Model
• Content is King
• Navigation / Look & Feel / Templates
Implications for Stakeholders
• Content Owners
• Web Masters
• P/P Experts vs. Journalists
• CFO/CIO Partnership
Implications for Stakeholders
Changing Roles:
• Business Office Drives Application
• Technology is Driven by the Application Requirements
• IT Provides Architecture for Data Access and Security
• IT Must Participate in Standards Bodies
Implications for IT Folks
• Resources
• Integration Across Organizations
• Exposure of Broken Processes
Implications for Campuses
• Single Authentication for all Applications
• Authorization for Access
• Attribute Directory for Role Based Information
• Messaging Provides Notification Propagation
• Portal is Middleware that Glues Disparate Systems Together
• Legacy Integration
Highlights
http://uc2010.ucsd.eduObtain The Full Report at...
Thank You
Copyright Regents of the University of California 2002. This work is the intellectual property of the author. Copyright Regents of the University of California 2002. This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of copyright statement appears on the reproduced materials and notice is given that the copying is by permission of
the author. To disseminate otherwise or to republish requires written permission from the author.the author. To disseminate otherwise or to republish requires written permission from the author.