Proposals Passed Items (Pending Proposals) 1. Staff Member for WebCT/Blackboard Training (klfrazie) 3. Campus Auth. (rel) 4. Coordinated Help Desk for Instructional Computing Support (rel) 5. New Mailing List Manager (jamyles, dan) 7. Campus Wiki Service (jamyles, dan) 8. Campus SMS Service (dfredric, dan) 9. Population-Building Tool (dan) 13. Campus Storage Service (dan) 15. ITIL Standards Based SLA and OLA Documents (rel) 16. Virtualized Web Hosting Service 17. NID Rewrite 20. Server-Side Mail Filters Submitted Potential Items 1. Staff Member for WebCT/Blackboard Training (klfrazie) My suggestion is that we replace the position charged with helping faculty to learn and develop their use of WebCT and other classroom technologies. 2. Business Plans for Large Purchases (klfrazie) For large projects greater than $25,000 a business plan should be made available to clearly identify the reason for the project, the problems that it will solve or the new services it will provided, the total cost of ownership, and why this option was chosen. In the past our users have had questions about projects and tracking down the right information was a challenge. Having a process such as this is also a good business practice and might prevent poor choices. 3. Campus Auth. (rel) Provide a common, shared, centralized system for creating accounts and providing authorization and authentication. This would allow department to grant access based on roles. It would also provide for a better experience for students, faculty and staff when grantedaccess in a variety of departments/areas. 4. Coordinated Help Desk for Instructional Computing Support (rel) With all the technology that is becoming available in classrooms, have a single place to call during normal instructional hours would provide a better teaching experience for students and faculty. Thiscould be done with a combination of student training and staff support. 5. New Mailing List Manager (jamyles, dan) Replace current campus list management system with a modern system. The replacement should include the capability for dynamic list membership generation (as opposed to batch-based membership generation), role-based list membership with exceptions, flexible web-based user preference management and list management, and list archiving. 6. Mass Mailing System Enhancement (klfrazie, dan) Need description. 7. Campus Wiki Service (jamyles, dan) Provide a wiki-style documentation system to faculty, staff, and students. Include an authorization facility for access levels (MTU-only, authenticate to view, authenticate to edit, etc.). 8. Campus SMS Service (dfredric, dan) dfredric: I would like to see MTU use SMS messaging to notify sysadmins of alerts. This service could replace the use of pagers if the user wants. Most or all sysadmins carry a cell phone and a pager so why not eliminate the pager if the SMS messaging can do the same function. dan: Provide MTU short message service for use by students, faculty, and staff. This service could be used for notifications about campus power and other utility outages and for notifications about email and other core service problems. The system could also be used as an auto-response tool, responding to SMS messages with university related data (for example: texting "hockey score" to some pre-arranged number would report the latest score). 9. Population-Building Tool (dan) Build LDAP groups based on Banner attributes and roles such as all faculty, all students with certain major, etc. These groups could be used for one-time mass mailings, to establish groups within Meeting Maker calendar and for many other purposes (email lists, class lists, application auth-n, etc) 10. Document Imaging System (dfredric) Need description. 11. Campus Weblog Service (dan) Need description. 12. Student Calendar Licences (dan) Meeting Maker licenses for all students. Calnedar system coupled to Administrative calendars, such as course schedules. 13. Campus Storage Service (dan) Universal access to central storage space, potentially via multiple methods, such as a web interface. 14. Campus Development Repository (jamyles) A central source repository and versioning system for use by all IT groups. 15. ITIL Standards Based SLA and OLA Documents (rel) Establish a group to create frameworks for Service Level Agreements (SLA) and Operating Level Agreements (OLA) for services. OLA's would be generated for ITS and departmental/cluster support groups. SLA would benefit the users that use services from both ITS and/ordepartmental/cluster support groups. Items from DCS Project List See link below for entire list and descriptions. 16. Virtualized Web Hosting Service 17. NID Rewrite 18. Lecture Hall Computing Resource Access Coordination 19. LDAP-Backed DHCP Service 20. Server-Side Mail Filters Items from Telcom Project List See link below for entire list and descriptions. 21. Paging Service Filtering (shane) Submitted Lists DCS Project List, 28 Sep 2006 Telcom User-Requested Projects, 28 Sep 2006 (PDF) For additions or corrections to this page, email jamyles@mtu.edu.