1. NMSU Banner Project Name http://uno-project.nmsu.edu

2. NMSU UNO Banner Project SunGard Systems Computer Technology (SCT) –The name of the company http://sungardhe.com Banner –The name of the software purchased –1,300 + of peer institutions –SunGard He Banner: Enterprise Resource Planning (ERP) attempts to integrate all departments and functions across a company onto a single computer system that can serve all the different departments’ needs (Koch 2002)

3. Why is this important to NMSU? Single integrated data store Replace NMSU’s current legacy systems Integration with NMSU’s web-based course management system, WebCT Establishes partners for the future (SunGard and Oracle) Provides 24 hours a day, 7 days a week access from any authorized web-enabled computer Eliminates social security ID number for students, faculty, and staff Electronic signatures, forms and workflow Ability to implement improved methods to track recruitment and enrollment

4. Software Replacement at NMSU Old SystemNew System (Banner…) FRSFinance HRMS and EAFHuman Resources Vistas and SARStudent SAMFinancial Aid CMDS and AFWAdvancement

5. What was purchased from SunGard SCT? Software Modules: Advancement Finance Financial Aid Human Resources Luminis (Web Portal and Content management System) Student (Registrar, Admissions, University Accounts Receivable and Auxiliaries) Data Marts (Data warehouse and reporting) Self-service Products Workflow Xtender (integrated imaging)

6. What was purchased from SunGard SCT? Services: SCT Project Management - for the whole project Technical Hours –Installation and Training Functional Training Hours - by module –Assisting us in using the software to better our processes

7. What else was purchased? Hardware (Sun Microsystems) Third-Party Software to enhance or enable the core software to work efficiently and effectively –Applicant tracking –AppWorx (job scheduling) –COGNOS (Canned and ad hoc report writer) –Evisions (check printing and digital documents) –Data Warehousing

8. NMSU UNO Banner Project Mindset Current processes will be critically analyzed If needed, changes will be made to our processes No changes will be made to the baseline software

9. Current Banner “go live” dates Project Kickoff Meeting: October 2003 Admissions Phase I: September 2004 Human Resources: January 2005 Luminis Web Portal: January 2005 e-~print: January 2005 Evisions: January 2005 Workflow: January 2005 Xtender: February 2005 PSL Timeload Interface: March 2005 Finance: June 2005 Appworx: June 2005 Content Management System: July 2005 (w/pilot groups) ODS for HR: August 2005 Admissions Phase II: September 2005 Student Marketing System: September 2005 Higher Markets: November 2005 ODS for Finance: January 2006 EDW: February 2006 (tentative) Student: October 2006 DARS: October 2006 Financial Aid: February 2007 Advancement: May 2007 ODS for Student: TBD ODS for Financial Aid: TBD LDI for e-learning – TBD Cognos: TBD (linked to ODS & EDW)

10. NMSU UNO Banner Communication “Big” committees Presentations to small groups ABCD memos Website – http://uno-project.nmsu.eduhttp://uno-project.nmsu.edu Secure Website http://salsa.nmsu.edu/Banner http://salsa.nmsu.edu/Banner Listserve: NMSU-Banner@nmsu.eduNMSU-Banner@nmsu.edu

11. Project Organization and Management UNO Project Director –Michael Hites - contact Shawna L. Arroyo (she’s nicer) UNO Project Management –Advancement – Jim McKinney –ERP Reporting – Olga Conter –Finance and Human Resources– Norma Noel –Student and Financial Aid – Natalie Aranda –Technical – Mrinal Virnave –Luminis Content Management – Richard Chavez Portal – Richard Chavez Self service – Richard Chavez

12. Banner Steering Committee William Flores Executive Vice President & Provost* (Chair) Jennifer TaylorSenior Vice President for Business and Finance Ben WoodsVice President for Planning, Physical Resources & University Relations Gladys De NecocheaAssociate Provost for Student Affairs & Community Colleges Rebecca DukesVice President for University Advancement Vimal Desai Chaitanya Vice President for Research Michael HitesChief Information Officer Carmen GonzalesVice Provost for Distance Education/Academic Dean Everett EggintonVice Provost for International and US-Mexico Border Programs Elizabeth TitusDean of Library Christopher EricksonFaculty Senate Representative Ellen BosmanFaculty Senate Representative Jennifer KreieFaculty Senate Representative Jessica VallejosASNMSU Representative Robert MoultonAcademic Dean Felicia Casados Campus Executive Officer Susan Grotevant Associate Provost of Student Success/Academic Programs

13. Banner implementation methodology Business process analysis Functional and technical training from SCT Fit-gap analysis Configuration Data conversion Testing User training Go live

14. Current Model

15. Luminis – Simplified Model

16. Content Management System (CMS) A CMS automates the process of creating, publishing, and updating web site content. Templates - Consistency - Global Branding - Propagates changes quickly and easily Editing content without knowing HTML Workflows & Approval - A workflow is the rule by which pages get created, approved, and added to the site - Based on roles

17. Web Publishing – Current Model

18. Web Publishing – Using CMS & Roles

19. CMS – Features In-Context Editing –Simplified content editing/entering for content contributors –Content entered/edited via browser Site Management –Simplified tools to create & manage sites Content Contributors –Enter and update content and participate in the workflow. De- centralized and non-technical. Content Editors –Responsible for initiating and managing workflows. Ensures site content is up-to-date. De-centralized and non-technical Versioning –Helps people track changes to the content –Back out changes to older copy –“Safety net” Asset Management –Prevents duplication of data and assets Template Developers –Responsible for developing XML and JSP templates to support the system. Centralized and technical.

20. CMS Teams & Feedback Objectives Gather use requirements and expectations from all constituent groups Interview key contributors, subject matter experts, and technical team members Analyze existing documentation and research reports To join the CMS Advisory Committee that consists of people from college, branches and administrative units contact: Richard Chavez rich@nmsu.edu 505.646.1810

21. Luminis – Simplified Model

22. The Disconnected Campus Foster a disconnected campus experience Encourage inefficiency Limit choice Diverse, disparate systems and services that:

23. The Unified Digital Campus –Provide personalized, user- centric education experiences –Deliver the right applications, information, tasks, and resources to the right people at the right time –Support business processes, collaboration, and interconnectivity –Extend the value of existing investments –Build according to your own needs, vision, and timeline SCT solutions equips your unified digital campus to:

24. What the Portal looks like Content is aggregated in channels Users can personalize their layout and subscribe to published channels

25. Portal Key Features Community building tools like chat and message boards WebCT Course tools integration for students and faculty Integrated self service for personal administrative information (pay stubs/ leave balances etc.)

26. Director of Enterprise Application Services Mrinal Virnave virnave@nmsu.edu 505.646.3147

27. Current Model

28. General Person Update Activities Development of Data Standards/Policy Population of shared validation tables Definition of security

29. General Person Update Data Standards/Policy Identification number Names, prefixes, suffixes, vendors Addresses Emergency contacts Email addresses Date of birth/death Confidentiality

30. Shared Validation Tables Table – database structure used to store information Validation table – code table used for a particular data element, eg: student type, college, campus Shared validation table – validation table utilized by multiple Banner modules (eg: Student and HR), example Address Type Validation tables are utilized by Oracle for data integrity, ensuring only data of a valid type is stored Example: Address Type AD – Permanent physical address BI – Billing address CU – Current address MA – Mailing address P1 – Parent address 1 P2 – Parent address 2

31. Shared Validation Tables Phase 1 – Demographics (1 March 2004) Address types (STVATYP), sources (STVASRC) Emergency contacts/relationships (STVRELT) County (STVCNTY), State (STVSTAT), Nation (STVNATN), Zip (GTVZIPC) codes Telephone types (STVTELE) Email addresses (GTVEMAL) Citizenship (STVCITZ), Visa types (STVVTYP) Gender, ethnicity (STVETHN), marital status (STVMRTL) Veteran (STVVETC), legacy information (STVLGCY)

32. Shared Validation Tables Phase 2 – Required for Human Resources (15 March 2004) Campus (STVCAMP), College (STVCOLL), Academic year (STVACYR), days of week (STVDAYS) CIP codes (STVCIPC), majors (STVMAJR), Class (STVCLAS), level (STVLEVL) Grading mode (STVGMOD), terms (STVTERM) Degree codes (STVDEGC), degree level (STVDLEV) Institutions (STVSBGI) Contacts (STVCTYP), initials (STVINIT), honors (STVHONR)

33. Shared Validation Tables Phase 3 – Required for Finance (Led by Finance) Chart of Accounts (FTVCOAS) Organization (FTVORGN) Funds (FTVFUND) Accounts (FTVACCT), account indexes (FTVACCI) Programs (FTVPROG), Activities (FTVACTV) Currency (FTVCURR)

34. General Person Update Security Access, confidentiality Custodians, authority Definition of user classes associated with University role Define Security - Banner - ODS - Cognos

35. NMSU ERP Reporting Project Manager Olga Conter oconter@nmsu.edu 505.646.1362

36. Security For All Systems Self Serve (web for) Luminis User –Luminis Administrative Banner Administrative Banner ODBC (transaction engine) ODS (aka Datamart) Cognos Xtender Action Items

37. Banner Finance Banner Transactional Database Banner Human Resources Banner Advancement Banner Student Banner Financial Aid ODS Finance Operational Data Store (ODS) Repository Data Warehouse ODS Human Resources ODS Advancement ODS Student ODS Financial Aid Finance History Human Resources History Advancement History Student History Financial Aid History Web For Prospects Web For Applicants Web For Students Web For Employees Web For Faculty Web For Executives Web For Alumni Self-Service Banner System Cognos Reporting Suite NMSU Staff Our System That Needs Security

38. Authentication vs. Authorization Authentication --- ID + Password Authorization – Mapping between your ID and what you can do –VISTAS LOGIN VISTAS SECURITY –FRS ID FRS Forms

39. Self serve access User has no login or password to Banner or Oracle All Access is via self-serve with the Banner ID and Banner PIN. The form is run in administrative mode to allow the form to be run. The BID and BPIN are used to isolate the query to the user Luminis carries the BID and BPIN in a structure and uses this pair to access Self Serve –This means that if you authenticate to Luminis, then Luminis can hide the access to self serve (and webct)

40. Oracle Banner-d Banner BID/BPIN Application Server Banner-as-d Self Serve Banner-ss-d WebCT Luminis Luminis-d Security/Authentication Flow SELF SERVE User Access Passes BID/BPIN Stored in Luminis

41. Luminis Authentication Single Sign On Luminis Email LDAP Luminis ID/PW calendar IMAP/POP Portal Access CPIP Self-Serve WebCT

42. Banner Security (Administrative) Banner Account is an Oracle Account Account is Generated by BANSECR account selecting the GSASECR form –Typically centrally managed –Sets up Banner Classes and Roles –If you have privileges to the GSASECR form, you can give out any security in Banner you wish

43. How Banner Security Works All Oracle accounts (set up via GSASECR) have CONNECT ONLY rights in Oracle (by default) ALL BANNER FORMS have a front end security module Based on your role/class in Banner, Banner Form sets up your security for that Form at that time (ephemeral security). –To the form (object), the appropriate oracle security is attached. –A “normal” banner administrative user has NO explicit Oracle access.

44. Oracle banner Banner BID/BPIN Application Server Banner-as Administrative User FR, HR, Student, Financial Aid, Alumni, Extender INB ACCESS Via a web browser Oracle ID Oracle Password (Managed by Banner Security Group)

45. Oracle Banner Application Server Administrative User Example SPAIDEN SPAIDEN OBJECT (User sees the output of the object) Security is attached to Object Banner Security Tables Consulted Security Tables Result

46. Oracle Banner Application Server Administrative User Example SPAIDEN Form Completed Update Result Presented To User Security is complete (oracle security is taken away) SPAIDEN TABLES UPDATED RESULTS RETURNED

47. GSASECR User Maint Screen

48. Example Student Class Definition

49. Oracle Banner BID/BPIN ODS and Cognos ODS ODBC COGNOS Oracle ID and Passwords Maintained on ODS Independent of Banner Power Users Cognos Security Access

50. ODS and Cognos Security ODS access is by Oracle Security Only –Banner Security is not migrated from Banner –Who should have direct access to ODS? Need to determine levels of security (read only) and how to permit users in Cognos can differentiate users (like E-print does) –Users in LDAP are assigned different classes –Cognos Packages are programmed to allow access to packages or data within the package – manage through the cognos administration tools. –Cognos should be able to be part of the Luminis portal login removing a layer of passwords for the users

51. Xtender Security Xtender user account management via windows fat client. It is fairly independent of banner Meta data is available through banner forms Disk Xtender to add value added security –TBD

52. Action Items ICT staff are engineering methods for converting Global ID and Global Password to Luminis ID and Password Who should manage the Banner Security? –Most institutions do it centrally –FR and HR value add are done by the respective office. Who should manage ODBC connections to Banner-P? Who should manage access to ODBC connections to ODS Who should manage access to Cognos reports? Phone Access –Payments –Transcript Express Self-serve outside of Luminis –Web-for-prospects –Web-for-admissions

53. NMSU Technical Project Manager Dr. Shaun Cooper scooper@nmsu.edu 505.646.6030

54. Why Chart of Accounts Is So Important General Ledger AP Central Fixed Assets Grants and Contracts Accounts Receivable Budget Development Position Control Financial System Student System Human Resources System Compensation Admin Housing Bio-demo Employee Relations Applicant Tracking Benefits Admin Personnel Budgeting Time and Attend General Person Recruiting and Admissions Academic and Student Structure Purchasing Payroll Calc Adjust Registration Third Party Sponsors Course Catalog Classroom Locations Academic Records Class Schedule Enrollment Strategy COA Financial Aid

55. Introduction to the New Chart of Accounts The new Chart of Accounts is composed of “FOAPAL”. FOAPAL is an acronym made from the names of its six segments plus a chart identifier. FUND F CHART C ORGANIZATION O ACCOUNT A PROGRAM P Activity A Location L

56. Required Segments Not all segments are required for a transaction to be recorded. CHART C ORGANIZATION O ACCOUNT A PROGRAM P Activity A Location L FUND F

57. Hierarchies in Banner Segments Hierarchies reflect relationships between the levels of responsibility. Or reporting– e.g.. For Org could be Campus - College – Department Allows easy grouping and summarizing for processing and reporting. Hierarchies allow various reports to be rolled up to the next level. Typically, a lower level of the hierarchy is selected to be the data enterable level and collects information from the transactions.

58. Sample of Banner Organization Hierarchy (F”O”APAL) Level 1 Level 2 Level 3 Level 4 Level 5 Level 6 Data Entry Level 7 Data Entry Level 8 Data Entry

59. C-FOAPAL Summary Fund F Organization O Account A Program P Banner Chart of Accounts Structure Segments and Hierarchies Banner Accounting String or FOAPAL Required Segments Optional Segments Characters 1 6 6 6 6 6 6 Hierarchy Levels 0 5 8 4 5 0 5 Chart C Activity A Location L

60. CHART Chart refers to the chart of accounts. Banner allows the use of multiple charts of accounts within one instance of Banner. Current plans are to have at least two charts of accounts – NMSU and Fndn. CHART C

61. FUND Designates a fiscal and accounting entity with a self-balancing set of accounts. Every entity general ledger in current chart of accounts will have a fund in the new COA. Some subsidiary ledgers will have a fund. Funds are needed for entities that must have a balance sheet. Current plans are to use first two digits to indicate campus and type of fund. FUND F 6 digits / 5 levels of hierarchy

62. ORGANIZATION Used to track the financial activities by functional reporting units. Designates the department/unit of budgetary responsibility and accommodates reporting at any level of organizational hierarchy. Replaces NMSU’s Organization, Executive Level, College, and Department attributes. Does not have to mirror the university hierarchy; just collects info for reporting. Organization is where the $ are spent! ORGANIZATION O 6 digits / 8 levels of hierarchy

63. ACCOUNT Designates asset, liability, fund balance, revenue, expenditure, and transfer account classifications. Replaces NMSU’s account control codes, revenue codes and object of expenditure codes. ACCOUNT A 6 digits / 4 levels of hierarchy

64. PROGRAM Designates NACUBO functional classifications (e.g. instruction, research, public service) and CHE and F&A classifications. Represents how the $ are spent! PROGRAM P 6 digits / 5 levels of hierarchy

65. ACTIVITY Optional classifications selected from a listing of valid codes. Activity designates temporary units of work, subsidiary functional classifications, or short duration projects. (Special events) Can reuse activity codes Activity A 6 digits / 0 levels of hierarchy

66. LOCATION Required mainly for fixed assets. Geographic location, building, and room numbers will be used to track all fixed assets. Can use as a misc attribute as well. Location L 6 digits / 5 levels of hierarchy

67. C-FOAPAL Segment Definitions Fund OrganizationActivityLocation Uniquely Identifies Fund Organization Exec Level College Departments User Assigned Classification Account Assets Liabilities Fund Balance Revenue Expenditures Transfers NACUBO CHE and F&A Classification Program Physical Places and Sites Required SegmentsOptional Segments SUMMARY Chart

68. Banner FOAPAL Advantages Overall, FOAPAL gives us more choices and more detail attached to each transaction upon entry Robust reporting for organizations and programs Expansion of information through the use of hierarchies and segments On-line inquiry for each part of the FOAPAL Attribute-like fields of activity and location which may be attached to the FOAP string for transaction processing Departmental definitions can be implemented into FOAPAL Provides enough flexibility to replace shadow systems

69. Cross-Walk Example Current Number 01-0-23051-5710 New Number Fund: 412055- restricted, campus 1 Org: 112345, Biology dept Acct: 571000, scholarship Program: 234598, fin aid program

70. It’s Too Much! Plan is to use an index to represent the fund, org and program Banner will recognize the index and retrieve the fund, org and program Index is six characters; can be reused Then will enter the account number SUMMARY: Departments will enter 6 character index and 6 character account.

71. Workgroup Responsibilities Define new comprehensive Chart of Accounts for all FOAPAL elements (Due March 5) Complete Chart Of Accounts tables in Banner (Data Entry) (Due March 31) Test new Banner Chart of Accounts (Due April 30) Map Cross-walk from FRS Chart of Accounts to Banner Chart of Accounts by individual account number. (Due April 30)

72. Finance/Chart of Accounts Tina Byford tbyford@nmsu.edu 505.646.2432

73. HRMS EAF January 2005 Human Resource (HR) Replacement

74. HR Team NameRoleDepartment Tina ByfordTeam LeadController Meg HainesWork Group Co-LeadPersonnel D’Anne StuartWork Group Co-LeadPayroll Tammy AnthonyPosition Control LeadBudget Richard AguilarPayroll Debbie BravoBudget Mary Vee CammackAg-Federal Employees Pam JeffriesTechnical LeadTechnical Barb MacRoriePersonnel/Technical Janet MayPersonnel/Benefits Miriam MeyerIRP-ERP Reporting Pamela RoggowPayroll Dee O’LareyTraining Crystal WangTechncial

75. HR Team Training Events Held Business Process Analysis - January 20, 2004 Training workshops began January 12, 2004 Next scheduled training - July 6, 2004

76. HR Team Future Events 15 Functional Training and Consultant visits planned 4 Technical Training and Consultant visits planned Visits go out through January 6, 2005

77. HR Team Training Visits Each visit trains on separate areas of the HR module Each visit requires homework to be completed

78. NMSU HR Project Manager Norma Noel nnoel@nmsu.edu 505.646.4986

79. Banner Finance Replacement FRS July 2005

80. Finance Team NameRoleDepartment Tina ByfordTeam LeadController Sandra AlvarezAccounts Payable LeadAccounts Payable/Travel Tammy AnthonyPosition Control LeadBudget Victoria GallegosResearch Accounting Lead Sponsored Project Accounting Bill HartyEndowment LeadAdvancement Pam JeffriesTechnical LeadTechnical Kimela Miller Loyd Purchasing LeadCentral Purchasing Kim MontoyaTechnical Kim RumfordChart of Accounts LeadAcctg & Financial Rptg Robert ValdezFixed Assets LeadAcctg & Financial Rptg

81. Finance Team Training Events Held Business Process Analysis – December 2, 2003 First Training Visit – January 23, 2004 Next scheduled training visit – May 25, 2004

82. Finance Team Future Events 19 Functional Training and Consultant visits planned 4 Technical Training and Consultant visits planned Visits go out as far as February 20, 2006

83. On-Going Events For HR/Finance Team Meetings Team Work Groups More Team Meetings

84. NMSU Finance Project Manager Randey Bamford rbamford@nmsu.edu

85. Replaces administrative systems –Student Records (Vistas) –Student Accounts Receivable (SAR) –Student Aid Management (SAM) To be implemented in 2006 Banner Student and Financial Aid

86. General person Recruitment and admissions –Web-for-prospects self-service Method of initiating communication between prospective students and NMSU Prospects provide information and request materials of interest –Web-for-admissions self-service Method of initiating and continuing communication between applicants and NMSU Applicants –Complete and submit applications for admission (can be completed at one time or can return to complete the application later) –View status of required supporting materials such as transcripts, test scores and recommendation letters –View overall application status –View current decision assigned to application Banner Student

87. Course catalog Schedule of classes General student Registration Student accounts receivable Academic history Self-service –Web-for-student View course catalog and class schedules View academic records, holds, grades and account information View status of financial aid application, eligibility and awards Register for classes and view withdrawal information –Web-for-faculty and advisors Access information about class schedules, class lists and students/advisees Faculty may enter grades Banner Student

88. Banner Recruitment and Admissions –Upgrade current Banner Admissions application to release 6.1 and Oracle 9i Implement self-service –Web-for-prospects –Web-for-admissions “Go live” September 2004 –Merge current Banner Admissions application with Banner ERP system Replace SSN with generated ID as the primary identification number Incorporate NMSU general person standards –Formatting of names and addresses –Use of common data field values for citizenship, ethnicity, etc. “Go live” September 2005 Banner Student Timeline

89. Banner Student Training Sessions –May 25-27, 2004 – Student Overview and Meetings with Individual Areas –June 15-17, 2004 – Catalog, Schedule, Location Management and Faculty Load Crossover –July 13-15, 2004 – General Student, Registration and Fee Assessment –September 21-23, 2004 – Student Accounts Receivable I –October 12-14, 2004 – Student Accounts Receivable II –October 26-28, 2004 – Academic History –February 1-3, 2005 – Letter Generation, Population Selection, Job Submission and Object Access –March 1-3, 2005 – Student Self-service –April 5-7, 2005 – Faculty and Advisor Self-service –Various consulting, technical and data conversion/migration sessions Testing and System Parallel Activities “Go live” 2006 Banner Student Timeline

90. Electronic data exchange Applicant tracking Budgeting Needs analysis Funds management Packaging Disbursement Award history Banner Financial Aid

91. Banner Financial Aid Training Sessions –June 1-3, 2004 – Overview, Record Creation and Electronic Data Exchange –July 27-29, 2004 – Applicant Tracking, Budgeting and Needs Analysis –September 28-30, 2004 – Funds Management and Student Employment –November 9-11, 2004 – Packaging, Loans and Letter Generation –December 7-9, 2004 – Disbursements and Population Selection –February 8-10, 2005 – Award History, Transcripts and Common Functions –March 8-10, 2005 – Rule and Table Build Support –Various consulting, technical and data conversion/migration sessions Testing and System Parallel Activities “Go live” 2006 Banner Financial Aid Timeline

92. Various Audiences –BPAs Review initial BPA documents and provide feedback Read final documents and provide sign-off –Training Prepare and attend functional training sessions –Complete Banner Navigation CBT (Computer Based Training) –Review training materials including BPA documents –Bring general concerns and issues specific to your area Provide feedback regarding each session and identify areas of interest or concern –Indicate new functionality NMSU would like to take advantage of –Indicate functionality gaps Participation Expectations

93. –Reports Identify production and ad-hoc needs Develop reports –Quality Assurance Testing Ongoing testing of student related modules Provide feedback regarding areas of interest or concern Parallel testing prior to implementations –Customize training materials and conduct in-depth training specific to area or office –2006 Implementations Participate in or conduct refresher and initial training sessions Participation Expectations

94. UNO Project Director –Vice Provost for Information and Communication Technologies UNO Student Project Management –Student and Financial Aid Project Manager –Lead Systems Analysts –Student Records Analyst –Branch Campus Analyst Work with branch campuses to ensure they are continually engaged, informed and represented throughout the project –Student, Academic and Financial Aid (SAFA) Committee Managers and team leaders from Registrar’s Office, Undergraduate Admissions, Graduate School, Student Financial Aid and Scholarship Services and University Accounts Receivable Project Organization and Management

95. UNO Student Business Process Owners Committee –Managerial committee composed of all student related areas including branch campuses –Ensures all areas are engaged throughout the project –Discusses policy and procedural issues and recommends solutions UNO Student Business Process Workgroup Committee –Employees with working knowledge of student records processing and its current and future impact on their area –All UNO Student Business Process Owners Committee areas are represented –Training, quality assurance and implementation team –Here’s where the bulk of the work gets done! Project Organization and Management

96. NMSU Student and Financial Aid Project Manager Natalie Bourguet Aranda naranda@nmsu.edu 505.646.2876

97. –Alumni Relations Keep Alumni in touch with NMSU –Development Develop strong relationships resulting in major gifts to NMSU –University Communications Primary source of communications about NMSU –Advancement Services Process gifts, endowments and other donations Maintain mailing lists and demographic information Primary source of information for reaching Alumni Office of University Advancement

98. How Does Banner Help? Alumni Relations –Improved Membership management for: Alumni Association, International Connoisseurs of Red and Green Chile, Chile Pepper Institute, Pioneers and other organizations facilitated by Alumni Relations Office –Event registration, tracking and management –Self service via the web for updates by Alumni Address updates Matching gift information Calendaring and communications for Alumni chapters

99. How Does Banner Help? Development –Better communications via the web Information available when Team members are on the road Team members can file trip reports real time when on the road –Improved repository for scanned documents, pictures and articles about donors

100. How Does Banner Help? University Communications –Provide opportunity for unified look of web site –Improved channels for releasing information to staff and faculty –Web Calendaring provides improved communications about scheduled activities and events

101. How Does Banner Help? Advancement Services –Improved accuracy for posting gifts to correct donor accounts Better search tools in Banner More information, more easily accessible in Banner Tighter integration with Finance Office for financial information More information available on line in standard database (not in shadow databases) –Opportunity to maintain addresses in one database for Students, Alumni and Donors –Easier to provide, for entire University, mailing lists and other reports about students, alumni and donors

102. NMSU Advancement Project Manager Jim McKinney jmckinne@nmsu.edu 505.646.3609

103. Reporting Update Cognos Reporting Report Net – web-based point-and-click interface to traditional reporting Shared report repository Secured access

104. Reporting Update Other Cognos Reporting Tools/Categories Power Play Users – server unlimited (146 requested) Real-time, On-Line Analytical Processing capability (OLAP technology) providing drill- through, drill-across enterprise information…eg enrollment, salary, budgetary models Utilize student, budget, employee, etc models (cubes) for analysis Business areas, departments, administrators Power Play Developers – 7 named users (11 requested) Develop student, budget, employee, etc models IRP, ICT, Budget, Finance/HR, Foundation, Student Services Visualizer (dashboard) – 31 named users (31 requested) View summary information Executive-level administrators Metrics Manager (scorecard) – 5 named users (5 requested) Comparisons, metrics Primary Banner functional areas Alerts For Notice Cast (alerts) – 10 named users (10 requested) Budget thresholds, enrollment/class thresholds, etc Primary Banner functional areas

105. Reporting Update Cognos Report Net User Categories Recipients – server unlimited licenses (184 requested) View and receive report output via web, email Students, Alumni, Administrators, Faculty Consumers – server unlimited licenses (319 requested) Run parameterized reports Departments Business Authors – server unlimited licenses (34 requested) Create ad-hoc reports Departments Professional Authors – 30 named users (76 requested) Create standard, periodic reports Central offices, Branches Administrators/Developers – 4 named users (6 requested) Create links to databases, enforce security ICT, IRP

106. Reporting Update Cognos Reporting Suite – Cost Summary Request total: $504,540 (with GSA discount) Purchase total: $350,000 Server unlimited use up to and including Business Author level of Report Net Server unlimited use of Power Play analytics Includes Report Net and Power Play training and installation of all products Additional license purchase fees locked for one year

107. Reporting Next Steps Implementation by Module Live Date: (Human Resources-Jan 2005, Finance-July 2005, Advancement- July 2005, Student-July 2006, Financial Aid-July 2006) Cognos Report Net and Power Play training Generate reports for each Banner Module Inventory existing reports Create reports/cubes Evaluate/implement Operational Data Store (ODS) content for each Banner Module

108. NMSU ERP Reporting Project Manager Olga Conter oconter@nmsu.edu 505.646.1362

109. Training ICT Training Services assists with the planning and coordination of UNO Project training events. These include functional, technical, and end-user training. There are three dedicated training labs for the project with a total of 52 seats. Most training is conducted with new equipment in a comfortable setting. Services available are: Customized Training specific to NMSU Customized Documentation Document Reproduction Training event scheduling Lab Maintenance Room/Equipment Setup Recorded & archived training sessions via Centra

110. UNO Training Committee Goal: Provide end-users with the technical skills and procedural knowledge to perform their jobs effectively and efficiently. Committee Members –Representatives from functional areas –Branch representatives –ICT Training Services Train-the-Trainer –Attend training on Main Campus –Train individuals on Branch Campus

111. ICT Training Services training@nmsu.edu