Information Technology Planning Board (ITPB) Retreat
Monday – July 16, 2007
Noon – 5 p.m.
Hacienda Room, Faculty Center
Members in Attendance: Kathryn Atchison, Elizabeth Bjork, Christine Borgman, Alfonso Cardenas, Mitch Creem, Jim Davis, Michael Goldstein, Xue Hua, Bill Jepson, David Kaplan, Kathleen Komar, Sam Morabito, Alan Robinson, Terry Ryan (for Gary Strong), Michael Schill, Judith Smith
Guests in Attendance: Julie Austin, Ross Bollens, Carmela Cunningham, Dan Greenstein, Patricia Keating, Bill Labate, Larry Loeher, Warren Mori, Nick Reddingius, Margo Reveil, Karen Ribback, Mike Schilling, Tom Trappler, Kent Wada, Don Worth
The meeting was called to order at 12:15 p.m. by ITPB Chair Alfonso Cardenas who welcomed attendees and reviewed the afternoon’s agenda. A brief overview of each of the agenda topics was presented:
- Information Technology Guidance Committee (ITGC) Overview
- Scholarly Interaction & IT-Enabled Research
- Educational Technology and the Common Collaboration & Learning Environment (CCLE)
- Wireless Technology
1. Information Technology Guidance Committee (ITGC) Overview
Dan Greenstein, Vice Provost, UCOP Academic Information and Strategic Services, presented an overview of the ITGC goal to develop the framework to guide system-wide investments in information technology.He pointed out that the UC system spends $1.5 billon annually on information technology, excluding the labs.He is reasonably optimistic about some new funding.
The ITGC framework addresses three areas:
- Research & Scholarship
- Focus should be on common development on the research grid, computation and clusters
- Recommends common development
- University-wide Business and Administrative Systems
- Questions the need for 10 separate systems
- Teaching, Learning & the Student Experience
- Looking for ideas to flow in a dynamic environment
The aim is to ensure competitive advantage for the UC system and to:
- Reduce costs where there are redundancies
- Improve effectiveness
- Support innovation
Opportunities in the 2008-09 fiscal year:
- The “compact” with the governor and the restoration of $100 million that was cut (Administrative systems won’t pull the money, but research and education will.).
- More critical than getting new funding is how to realign the $1.5 billion that we now have.Educational technology funds are just not earmarked.
Discussion about National Science Foundation:
- NSF is seeking to build cyberinfrastructure rather than specific programs.
- How to understand the solicitation process.
- NSF concerns about proposals that promote “reinvention” and replication without leveraging work.
- UC/UCLA should be informed on what NSF wants and what will help researchers get grants.
2. Scholarly Interaction & IT-Enabled Research
ITPB Vice Chair Christine Borgman presented a framework for a scholarly interaction infrastructure. The goal is to enable new forms of scholarship through the use of information technology that will help provide faculty and students with the tools to do research and to share and store information using new and emerging resources and technology.
Library Issues - Terry Ryan, Associate University Librarian, provided an overview of library initiatives and issues. In addition to developing repositories for faculty content, the library is increasingly expanding its role as an advocate for open access, fair use, and intellectual property legislation.
Computational Infrastructure – Warren Mori, Director of the Institute for Digital Research & Education, introduced IDRE’s vision to support, advance and guide the campus-wide initiative to make UCLA a world leader in research through high performance computation, data visualization and analyses of large data sets and databases. IDRE challenges are:
- Working across disciplines; he’s been working to understand “our own vocabulary.”
- Crises of data center space on campus – which means we can’t compete well for grants.
- Recruitment and retention of faculty/researchers.
3. Educational Technology & Common Collaboration & Learning Environment (CCLE)
Patricia Keating, Chair of the Faculty Committee on Educational Technology (FCET), provided the group with an overview of issues and primary concerns of the FCET.
Open Courseware - The FCET recommended that UCLA consider an open courseware pilot that would be focused on the course information that incoming transfer students need to clarify what is covered in UCLA lower division courses, how that relates to the courses that were taken in community college, and how those courses would count as the prerequisite for UCLA upper division courses.
Background Illustration - The FCET looked at MIT’s Open Courseware Group and determined that Open Courseware is not a course management system (as CCLE is), online instruction, or distance learning.Instead it is an archive of already completed courses, providing a thorough overview of what was covered in a given the course.The MIT course management system is the “draft in progress” used for current courses being offered at MIT.The course information is published in the open courseware repository after the course is completed.Although originally intended for external, non-MIT use, MIT found that it was most useful within the MIT community.
The main challenges of Open Courseware are copyright issues and obtaining clearances for teaching materials.The FCET’s position is that open courseware would be a valuable tool to help faculty better understand what students know or have been taught in other courses.
Common Collaborative Learning Environment (CCLE) -Detailed analysis and planning activities are being conducted for CCLE.There currently are no major milestones to report for the CCLE project.
WASC - In response to the accreditation review of the Western Association of Schools and Colleges (WASC), the FCET has expressed their concern about educational technology leadership on campus with the retirement of Ruth Sabean.
Specific FCET concerns:
- Electronic course packs for students
- 24 Hour Help Desk for faculty
- Interoperability; continued membership in SAKAI
- Equipping and upgrading classrooms to a level generally expected by faculty
- IT competence and literacy
- Need for more assessment of educational/technical innovation to determine how successful each piece is and to push forward on the most successful pieces.
Issues that are being addressed by the ITPB, but have not been discussed by the FCET include wireless, distance learning and online instruction.Upon request from the ITPB, the FCET will include these topics in their fall agenda.The fall agenda of FCET will also be looking at various questions raised at the ASUCLA student-faculty roundtable on the educational technology big picture and a broader range of issues.
4. Wireless Technology
ITPB Chair Alfonso Cardenas presented trends and user expectations that were identified by the ITPB Wireless Subcommittee, which was formed to study wireless on campus.The subcommittee expressed concern about insufficient mobile ability.The integration of internet access, cell phones, sensors and multi-media services is the largest growth market, and it is anticipated that the new generation of mobile device-users will expect integrated access and services anytime and anywhere.The subcommittee discussed the issue of meeting the expectations of students for these services on campus as well as other possible mobile scenarios.
5. Break-out Session Reports
The meeting broke into four subgroups that each looked at several issues relative to their topics.
Scholarly Interaction – Computational Infrastructure (Chair: ChristineBorgman. Members: Warren Mori, Kathy Komar, Jim Davis, Bill Labate)
This group addressed three questions that are critical to UCLA computational infrastructure.
1. What is – or could be – the strategic vision and priorities for UCLA?
The group agreed that UCLA’s focus should be in three areas:high performance computing, end-to-end computing services and data as infrastructure.Data infrastructure issues to be addressed by the campus:
- Data management plans
- How do researchers respond to the requirement?
- What campus or system-level help is available to researchers to create appropriate data management plans?
- The local capacity to use or reuse data
- What computational support is available?
- What desktop/Palmtop services are available?
- There is a need for value-added services, e.g. 24/7 helpdesk.
- What are the access methods, issues?
- How does discovery happen?
- Content curation, trust, provenance, peer review publishing
- The life cycle of data, from conception to curation
2. Who “owns” the Problem?
- Funding is organized by administrative entity, not by function or problem.How can the campus bring together people and information and share the expertise across administrative entities?
- There is a continuum of capacity and requirements – from Excel to exascale.How do we reconcile resources?
- Short-term approaches threaten long-term solutions. For example, PIs need to respond immediately for their current grants, and they’re only concerned about meeting their immediate requirements.This means that there’s no long-term data management plan or template established that can be used across the campus or the system.
3. In what areas do UCLA’s issues and priorities intersect with the UC ITGC planning?
- UCLA has leadership capacity in data curation.
- UCLA can coordinate with an eScholarship respository.
- UCLA is developing a critical mass of content.
- UCLA is a leader in grid development and computational clusters.
- We need to start looking for data management plan information and language that can be used in grants across the board.
- We need positioning in Washington D.C. for competitive advantage; UC should go to Washington claiming “the power of 10.”
Scholarly Interaction – Collaboration, Sharing, Intellectual Property (Chair: Kathy Atchison. Members: Dave Kaplan, Alan Robinson, Tom Trappler, Don Worth, Margo Reveil)
The group began with a statement that, unlike teaching, research communities can be anyplace – not just on campus - and so all tools and policies have to span geographical communities.Also, faculty are far more likely to be engaged in collaboration on research than teaching. The requirements for a robust collaboration revolve around setting standards, policies and infrastructure that would provide openness and widely available, indexed material at the same time that they protect the intellectual property rights of individuals and the university.
1. Technical Priorities for Scholarly Interaction are (unranked):
- Infrastructure for sharing
- UC-Wide Policy sharing wizard (a simple UCLA version of Creative Commons)
- Global authentication - not just to a UCLA address
- A common platform
- An indexing system that links to permissions
- Interoperability
- A common database of faculty research descriptions/ research database to help people find future collaborations (i.e. create a systemwide network that would focus on specific topics) The objective is to stimulate and encourage collaboration across the UC system – such as Facebook for faculty. A social-networking tool for faculty to rapidly find potential collaborators.
- Control of distribution through web-based sharing tools
- Permission management tools (that can protect intellectual property)
- Identity management
- Survey/index of existing repositories (abstract describing data)
- Tools for cross-departmental(even cross campus) bios, research, interests and teaching (departments have tools, but how do they link up across departments?)
2. Policy and Standards Issues to be addressed are:
- Rules for setting up databases
- Policy on security issues – e.g. HIPAA
- Policy management
- Restricting access vs. open access – need to do both
- Security vs. transparency and openness
- Standards that span higher education
- Publishing, posting, sharing standards
3. Intellectual Property Rights Discussion:
- How do we share material and at the same time protect the intellectual property rights of the creator?
- How do we credit ideas?
- There’s a need to establish procedures and education of faculty and researchers (i.e. guidelines, ethics).
4. Questions to explore in the future:
- What’s the motivator for compliance with standards and policy?
- What are the most important forms of collaboration?
- What are the next steps to archiving?
- What’s the motivation for posting?
- What’s required by Policy vs. IT?
- What’s the balance between restrictions and openness?
- How do we get standards that span higher ed?
- What incentives are there for sharing?
Education Technology and CCLE (Chair:Mike Schill and Judi SmithMembers: Pat Keating, Elizabeth Bjork, Terry Ryan, Julie Austin, Xue Hua)
The group looked at three major topics.
1. UCLA now has general education program requirements for all students in certain areas.
- The internal community wants access to view the courses, copies of syllabi, but they can only get e-access to current quarter’s classes; there is demand for an archive of all courses taught
- The Academic Senate requires all course outlines be on file – for access by students and faculty.
- There’s a need to build an extended electronic catalog, a good repository and a good assessment tool.
- Question:Who would support educational technology groups in departments?
2. Do we have someone to facilitate the development of such a system?
- It’s not trivial.
- We don’t have a clear campus mechanism or resource for the development of a system.
- The Academic Senate can’t do it – it doesn’t have staff.
3. Common Collaborative Learning Environment (CCLE)
- Current Picture
- Central IT support is currently in place.
- Classes are coming on board in the fall.
- Planning group will have a report in August 2007.
- Budget request is going to CITI on Aug. 15, 2007.
- Structural problems
- Effort is very decentralized – how do we come to a common voice?
- The common goal is unclear – how do we come to agreement on it?
- Funding is not in place – how do we get it?
- We need some higher level person to help – to facilitate, troubleshoot, etc.
- How do we find someone to help lead the effort?
- Where should the person sit – OID, OIT?
- ITGC input on this issue is not specific – doesn’t provide direction.
Wireless and Mobile Communications (Chair: Mitch Creem. Members:Alfonso Cardenas, Sam Morabito, Bill Jepson, Mike Schilling, Karen Ribback)
The wireless group reported more questions than answers from their break-out session.They didn’t think that wireless and cell phones should necessarily be integrated now and weren’t sure of what is reasonable to expect from wireless/cell functionality in the future.They also did not see any clear business model for supporting wireless or cell phones, and weren’t sure that on how to prioritize any investment in this arena.
Discussion points:
- It might be possible that wireless should be provided “beyond the campus” for faculty, but not for students.
- Wireless access is not a “decision” point for students choosing a college.
- There’s uncertainty about the appropriate investment for wireless – probably all over campus.
- Not clear where handheld/PC technology is going.It’s probably premature to second-guess at the moment.Not sure the new software programs or web applications can be accessed on handhelds.
- Email is not seen as a good method for delivering emergency messages to the campus.
- There is a need to study applications and types of devices.
- University could form partnerships with service providers and bill students directly.
- There is a groundswell of wireless activity, revolving around administrative issues, green space, RFID, etc.
- What is the wireless demand?It’s probably push-pull.Are we pushing because it’s good and effective or because it’s available?
- What are the related accessibility issues? How does it tie into the UC e-initiative?
- The cost of implementation is not small; if you go down this road, there has to be funding.
The group recommended more study and that the ITPB set up another subcommittee.
Business Systems and Processes Discussion
Dan Greenstein gave an overview of the UC position on administrative systems, which lead to a discussion of several issues. Greenstein’s main points were:
1. There are significant resources spent on redundant systems.
- The approach is to develop a common system, but not one that forces the UC campuses to move to all at once. The approach is to say “here’s our plan – develop your architecture to move here.” UCOP wants to take an architecturally driven approach.
- The big challenge is that this will require us to collectively change what we’re doing.How does UCOP communicate across campus and within campuses?
- Roads to success (moving forward on common development) are:
- Strategic sourcing that provides savings
- Open source development
- Community (or UC) development
2. Business systems are the easiest to address technically, but the hardest to address culturally:
- All the campuses are in different stages of development with different budgets.The overwhelming challenge is to figure out how to get people to change their business systems in the midst of everything else.
- The answer is a “staggered migration.”
3. Questions for UCOP to resolve:
- What are the priorities?What do we do first?What do we do next?
- How do we put into place a system that would allow the campuses to collaborate with each other?
- What is the mechanism to create incentives?
- How do we do strategic sourcing?
Group discussion:
- There are different sets of people – either system or campus-wide – and they have different perspectives, different priorities and they’re not aligned.
- Considering investment requirements, incentives and cultural barriers, it’s a “massive effort” to move forward.
- Discussions about moving to common systems are often in a vacuum.People are talking about developing new architecture, but that is separate from what people are actually trying to do and separate from the funding. That makes for a big misfit.
- It feels like the system-wide process development is not doing well, and that there’s no enthusiasm for it. Disaster recovery seems to do well in the discussion because there’s nothing currently in place to replace.
- The ITGC is going forward with a heavy education component and the desire to move and enthusiasm; it’s not there on the administrative side, even though administrative systems are in the same plan.How do we reconcile that?
- Regents should know:
- Centralized does not always mean cost-effective.
- Campuses don’t all act the same.
- We need a funding model – possibly for the President to eventually go to the chancellors for funding. (Example:there was a strategic sourcing plan a couple years ago, and it could have been done centrally, but there was no funding plan. So, each campus went off and did things on their own, and now we have 10 systems.)
- Rather than have UCOP say all campuses must sign up, they should try to get critical mass on campuses willing to go forward.The alternative is to get hundreds of millions of dollars for a consolidated system – and then, we might not get any better functionality than we had to start with.
- Need to move with the “regions” idea. UCLA is doing it – with Merced, UCOP, etc.That could start spreading.
- UCLA AIS? think it can extend the HRIS legacy system another five years, but needs to know what UCOP will do. We’re ready to go with an HRIS system now, but we’re stalling because there may be a UCOP mandate for a system-wide HRIS in a year or two.
- The most important point is that this is NOT an information technology issue, it’s a business and culture issue.
The meeting was adjourned at 5 p.m.