1. Undergraduate Program Directors Meeting Non-Standard Tuition and Administrative Arrangements Policy October 2011 October 2011

2. I. Enterprise resource planning (ERP) is an integrated computer-based system used to manage internal and external resources including tangible assets, financial resources, materials, and human resources. It is a software architecture whose purpose is to facilitate the flow of information between all business functions inside the boundaries of the organization and manage the connections to outside stakeholders. Built on a centralized database and normally utilizing a common computing platform, ERP systems consolidate all business operations into a uniform and enterprise wide system environment. [ [

3. II. Campus Systems Executive Committee Consolidates SA Exec, Finance and HR committees Consolidates SA Exec, Finance and HR committees Oversees all PeopleSoft and related applications Oversees all PeopleSoft and related applications Plans, prioritizes and approves system initiatives Plans, prioritizes and approves system initiatives Serves as liaison to CoD and VP’s Serves as liaison to CoD and VP’sMembers: Yvette Mozie-Ross (co-Chair) Jack Suess (co-Chair) Jill Barr Michael Dillon Arnold Foelster Joe Kirby Ben Lowenthal Gust Mitchell Valerie Thomas

4. IV. Key Points to Remember SA is a term based system which means changes to the system should take effect by semester SA is a term based system which means changes to the system should take effect by semester All changes affecting registration (course offerings, degree requirements, pre-requisites) should be finalized and communicated by March 1 (for Fall), October 1 (for Spring), January 15 (for Summer), August 15 (for Winter) All changes affecting registration (course offerings, degree requirements, pre-requisites) should be finalized and communicated by March 1 (for Fall), October 1 (for Spring), January 15 (for Summer), August 15 (for Winter) Changes to be reflected in the UG Catalog must be finalized by March 1 Changes to be reflected in the UG Catalog must be finalized by March 1 Changes to academic structure (e.g. acronyms for programs and plans) should be done in consultation with SA Team Changes to academic structure (e.g. acronyms for programs and plans) should be done in consultation with SA Team Be familiar with established guidelines (e.g. course and program fees; UGC, GEP, WI and Grad Council course approvals) Be familiar with established guidelines (e.g. course and program fees; UGC, GEP, WI and Grad Council course approvals)

5. V. Non-Standard Programs  Policy finalized.  Currently following our Communication Plan to share details.  Grouped tuition plans into 10 general categories.  Future programs should be slotted into one of the current 10 categories.

6. Points to Remember o Approval process  Detailed Business Plan (attached to Policy – Policy Website)  www.umbc.edu/policies/pdfs/VIII_2.05%20Non% 20Standard%20Tuition%20Policy.pdf www.umbc.edu/policies/pdfs/VIII_2.05%20Non% 20Standard%20Tuition%20Policy.pdf  Approval by Dean  Review by Committee  Final Approval by Philip and Lynne Tuition consistent with existing 10 groups.  See handout with 10 groups