NMSU Banner Project Name .
111
NMSU Banner Project Name http://uno-project.nmsu.edu
-
date post
21-Dec-2015 -
Category
Documents
-
view
231 -
download
0
Transcript of NMSU Banner Project Name .
NMSU Banner Project Name
http://uno-project.nmsu.edu
NMSU UNO Banner Project• SunGard Systems Computer Technology (SCT)
– The name of the companyhttp://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)
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
Software Replacement at NMSUOld System New System
(Banner…)
FRS Finance
HRMS and EAF Human Resources
Vistas and SAR Student
SAM Financial Aid
CMDS and AFW Advancement
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)
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
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
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
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)
NMSU UNO Banner Communication
• “Big” committees• Presentations to small groups• ABCD memos• Website – http://uno-project.nmsu.edu• Secure Website
http://salsa.nmsu.edu/Banner• Listserve: [email protected]
Project Organizationand
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
Banner Steering Committee
• William Flores Executive Vice President & Provost* (Chair)• Jennifer Taylor Senior Vice President for Business and Finance• Ben Woods Vice President for Planning, Physical Resources & University Relations• Gladys De Necochea Associate Provost for Student Affairs & Community Colleges• Rebecca Dukes Vice President for University Advancement • Vimal Desai Chaitanya Vice President for Research• Michael Hites Chief Information Officer• Carmen Gonzales Vice Provost for Distance Education/Academic Dean• Everett Egginton Vice Provost for International and US-Mexico Border Programs• Elizabeth Titus Dean of Library• Christopher Erickson Faculty Senate Representative• Ellen Bosman Faculty Senate Representative• Jennifer Kreie Faculty Senate Representative• Jessica Vallejos ASNMSU Representative• Robert Moulton Academic Dean• Felicia Casados Campus Executive Officer• Susan Grotevant Associate Provost of Student Success/Academic Programs
Banner implementation methodology
• Business process analysis• Functional and technical training from SCT• Fit-gap analysis• Configuration• Data conversion• Testing• User training• Go live
Current Model
Luminis – Simplified Model
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
Web Publishing – Current Model
Web Publishing – Using CMS & Roles
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.
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 [email protected]
Luminis – Simplified Model
The Disconnected Campus
• Foster a disconnected campus experience
• Encourage inefficiency
• Limit choice
Diverse, disparate systems and services that:
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:
What the Portal looks like
• Content is aggregated in channels
• Users can personalize their layout and subscribe to published channels
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.)
Current Model
General Person Update
Activities •Development of Data Standards/Policy
•Population of shared validation tables
•Definition of security
General Person Update
Data Standards/Policy
•Identification number•Names, prefixes, suffixes, vendors•Addresses•Emergency contacts•Email addresses•Date of birth/death•Confidentiality
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 addressBI – Billing addressCU – Current addressMA – Mailing addressP1 – Parent address 1P2 – Parent address 2
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)
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)
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)
General Person UpdateSecurity
•Access, confidentiality•Custodians, authority•Definition of user classes associated with University role•Define Security
- Banner- ODS- Cognos
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
BannerFinance
Banner Transactional
Database
BannerHuman Resources
BannerAdvancement
BannerStudent
BannerFinancial Aid
ODSFinance
Operational Data Store (ODS) Repository
Data Warehouse
ODSHuman Resources
ODSAdvancement
ODSStudent
ODSFinancial Aid
FinanceHistory
Human ResourcesHistory
AdvancementHistory
StudentHistory
Financial AidHistory
WebFor
Prospects
WebFor
Applicants
WebFor
Students
WebFor
Employees
WebFor
Faculty
WebFor
Executives
WebFor
Alumni
Self-Service
BannerSystem
CognosReporting Suite
NMSU Staff
Our System That Needs Security
Authentication vs. Authorization
• Authentication --- ID + Password
• Authorization – Mapping between your ID and what you can do– VISTAS LOGIN
• VISTAS SECURITY
– FRS ID• FRS Forms
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)
OracleBanner-d
BannerBID/BPIN
Application Server
Banner-as-d
Self Serve
Banner-ss-d
WebCT
LuminisLuminis-d
Security/Authentication Flow SELF SERVE
User Access
Passes BID/BPINStored in Luminis
Luminis AuthenticationSingle Sign On
Luminis
LDAPLuminis ID/PW
calendar
IMAP/POP
Portal Access
CPIPSelf-ServeW
ebCT
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
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.
Oraclebanner
BannerBID/BPIN
Application Server
Banner-as
Administrative UserFR, HR, Student, Financial Aid, Alumni, Extender
INB ACCESSVia a web browser
Oracle IDOracle Password
(Managed by Banner Security Group)
Oracle
Banner
Application Server
Administrative User Example
SPAIDEN
SPAIDEN OBJECT(User sees the output of the object)
Security is attached toObject
Banner Security Tables Consulted
Security Tables Result
Oracle
Banner
Application Server
Administrative User Example
SPAIDEN FormCompleted
Update Result PresentedTo User
Security is complete(oracle security is taken away)
SPAIDEN TABLES UPDATED
RESULTS RETURNED
GSASECR User Maint Screen
Example Student Class Definition
Oracle
BannerBID/BPIN
ODS and Cognos
ODS
ODBC
COGNOS
Oracle ID and PasswordsMaintained on ODS
Independent of Banner
Power
Use
rs
Cognos Security Access
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
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
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
Why Chart of Accounts Is So Important
General Ledger
AP Central
Fixed
Assets
Grants and Contracts
AccountsReceivable
Budget
Development
Position
Control
Financial System Student System
Human Resources System
CompensationAdmin
Housing
Bio-demo EmployeeRelations
Applicant Tracking
BenefitsAdmin
Personnel Budgeting
Time andAttend
GeneralPerson
Recruiting and Admissions
Academic and Student
Structure
Purchasing
PayrollCalc Adjust
Registration
Third PartySponsors
Course Catalog
Classroom Locations
Academic Records
ClassSchedule
EnrollmentStrategy
COACOA
FinancialAid
Introduction to the NewChart 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
CHARTC
ORGANIZATIONO
ACCOUNTA
PROGRAMP
ActivityA
LocationL
Required Segments
Not all segments are required for a transaction to be recorded.
CHARTC
ORGANIZATIONO
ACCOUNTA
PROGRAMP
ActivityA
LocationL
FUND
F
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.
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 EntrySub-Org
Sub-Org
Dept / Sub-Org
Departm ent
School / Sub-College
College
Adm inistrative
Cam pus
C-FOAPAL Summary
Fund
F
Organization
O
Account
A
Program
P
Banner Chart of Accounts StructureSegments 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
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.
CHARTC
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.
FUNDF
6 digits / 5 levels of hierarchy
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!
ORGANIZATIONO
6 digits / 8 levels of hierarchy
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.
ACCOUNTA
6 digits / 4 levels of hierarchy
PROGRAM
• Designates NACUBO functional classifications (e.g. instruction, research, public service) and CHE and F&A classifications.
• Represents how the $ are spent!
PROGRAMP
6 digits / 5 levels of hierarchy
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
ActivityA
6 digits / 0 levels of hierarchy
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.
LocationL
6 digits / 5 levels of hierarchy
C-FOAPAL Segment Definitions
Fund Organization Activity Location
UniquelyIdentifiesFund
OrganizationExec LevelCollegeDepartments
UserAssignedClassification
Account
AssetsLiabilitiesFund BalanceRevenueExpendituresTransfers
NACUBO CHE and F&AClassification
Program
PhysicalPlacesand Sites
Required Segments Optional Segments
SUMMARY
Chart
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
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
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.
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)
• HRMS
• EAF
• January 2005
Human Resource (HR) Replacement
HR TeamName Role Department
Tina Byford Team Lead Controller
Meg Haines Work Group Co-Lead Personnel
D’Anne Stuart Work Group Co-Lead Payroll
Tammy Anthony Position Control Lead Budget
Richard Aguilar Payroll
Debbie Bravo Budget
Mary Vee Cammack Ag-Federal Employees
Pam Jeffries Technical Lead Technical
Barb MacRorie Personnel/Technical
Janet May Personnel/Benefits
Miriam Meyer IRP-ERP Reporting
Pamela Roggow Payroll
Dee O’Larey Training
Crystal Wang Techncial
HR TeamTraining Events Held
• Business Process Analysis - January 20, 2004
• Training workshops began January 12, 2004
• Next scheduled training - July 6, 2004
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
HR Team Training Visits
• Each visit trains on separate areas of the HR module
• Each visit requires homework to be completed
Banner Finance Replacement
• FRS
• July 2005
Finance Team
Name Role Department
Tina Byford Team Lead Controller
Sandra Alvarez Accounts Payable Lead Accounts Payable/Travel
Tammy Anthony Position Control Lead Budget
Victoria Gallegos Research Accounting Lead
Sponsored Project Accounting
Bill Harty Endowment Lead Advancement
Pam Jeffries Technical Lead Technical
Kimela Miller Loyd
Purchasing Lead Central Purchasing
Kim Montoya Technical
Kim Rumford Chart of Accounts Lead Acctg & Financial Rptg
Robert Valdez Fixed Assets Lead Acctg & Financial Rptg
Finance Team Training Events Held
• Business Process Analysis – December 2, 2003
• First Training Visit – January 23, 2004
• Next scheduled training visit – May 25, 2004
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
On-Going Events For HR/Finance
• Team Meetings
• Team Work Groups
• More Team Meetings
• Replaces administrative systems– Student Records (Vistas)– Student Accounts Receivable
(SAR)– Student Aid Management (SAM)
• To be implemented in 2006
Banner Student and Financial Aid
• 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
• 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
• 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
• 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
• Electronic data exchange • Applicant tracking• Budgeting• Needs analysis• Funds management• Packaging• Disbursement• Award history
Banner Financial Aid
• 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
• 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
ParticipationExpectations
– 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
ParticipationExpectations
• 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
• 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
– 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
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
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
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
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
Reporting Update
Cognos Reporting
•Report Net – web-based point-and-click interface to traditional reporting
•Shared report repository
•Secured access
Reporting UpdateOther 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
Reporting UpdateCognos 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
Reporting UpdateCognos 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
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
Training
ICT Training Services assists with the planning and coordinationof UNO Project training events. These include functional,technical, and end-user training. There are three dedicatedtraining labs for the project with a total of 52 seats. Most trainingis 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
UNO Training CommitteeGoal: 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
