1 / 111

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 company http://sungardhe.com Banner The name of the software purchased 1,300 + of peer institutions

leslie-rogers
Download Presentation

NMSU Banner Project Name

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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

  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.edu • Secure Website http://salsa.nmsu.edu/Banner • Listserve: NMSU-Banner@nmsu.edu

  11. Project OrganizationandManagement • 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 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

  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 Diverse, disparate systems and services that: • Foster a disconnected campus experience • Encourage inefficiency • Limit choice

  23. The Unified Digital Campus SCT solutions equips your unified digital campus to: • 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 ownneeds, vision, and timeline

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

  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. Luminis Luminis-d CPIP Application Server Banner-as-d Self Serve Banner-ss-d CPIP WebCT Security/Authentication Flow SELF SERVE Oracle Banner-d Banner BID/BPIN User Access Passes BID/BPIN Stored in Luminis

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

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

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

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

  47. GSASECR User Maint Screen

  48. Example Student Class Definition

  49. Oracle Banner BID/BPIN ODS and Cognos Oracle ID and Passwords Maintained on ODS Independent of Banner ODS ODBC Power Users COGNOS 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

More Related