Presentation is loading. Please wait.

Presentation is loading. Please wait.

Middleware 101 Dave Tomcheck UC Irvine. Overview Drivers and Assumptions Objectives The Components of the Business Architecture Implications for Stakeholders.

Similar presentations


Presentation on theme: "Middleware 101 Dave Tomcheck UC Irvine. Overview Drivers and Assumptions Objectives The Components of the Business Architecture Implications for Stakeholders."— Presentation transcript:

1 Middleware 101 Dave Tomcheck UC Irvine

2 Overview Drivers and Assumptions Objectives The Components of the Business Architecture Implications for Stakeholders

3 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

4 Competitive Labor Market New Staff Will Not Have Adequate Skills/Training Technology is Changing the Way Business is Conducted Drivers & Assumptions

5 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

6 Members of the New Business Architecture Planning Group Steven Barclay, San Francisco Judith Boyette, HR (OP) Wendell Brase, Irvine Anne Broome, Controller (OP) James Dolgonas, CIO (OP) Kristine Hafner, Staff Sam Morabito, Los Angeles Steven Relyea, San Diego Thomas Vani, Santa Cruz

7 Key Components of a New Business Architecture Page 7 of Report

8 Integration of business transactions with policies, guidance, and training A New Business Architecture for UC

9 Page 7 of Report Establish UC as a competitive employer and provide staff the tools to succeed A New Business Architecture for UC

10 Page 7 of Report Redesign Processes to facilitate getting work done rather than cover all potential transactions A New Business Architecture for UC

11 Page 7 of Report Authenticate, authorize, provide effective tools A New Business Architecture for UC

12 Page 7 of Report A New Business Architecture for UC Employ emerging standards to improve integration of financial data

13 Page 7 of Report A New Business Architecture for UC Embed performance metrics into the way UC conducts its business and strengthen financial controls

14 Departments CentralOffices Where are Support Costs?

15 Pages 8-11 of Report Single Authentication/Authorization (Lightfoot Model) Establish Super-Intuitive Navigation Integrate Information, Transactions, Training, Templates Business Portal

16 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 Report

17

18

19

20

21 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 Report

22 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 Report

23 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 Report

24 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 Report

25 Financial Systems

26 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

27 Content Owners Web Masters P/P Experts vs. Journalists CFO/CIO Partnership Implications for Stakeholders Changing Roles:

28 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

29 Resources Integration Across Organizations Exposure of Broken Processes Implications for Campuses

30 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

31 http://uc 2010.ucsd.edu Obtain The Full Report at... Thank You 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 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.


Download ppt "Middleware 101 Dave Tomcheck UC Irvine. Overview Drivers and Assumptions Objectives The Components of the Business Architecture Implications for Stakeholders."

Similar presentations


Ads by Google