1 / 19

Realizing the Vision of ERP Front-ends for the real end user

Realizing the Vision of ERP Front-ends for the real end user. Jennifer Foutty, Director University Information Systems www.indiana.edu/~hrsis Jfoutty@indiana.edu. Agenda. Indiana University The “problem” IU’s solution Architecture Strategy Real Life Examples. IU Background

ura
Download Presentation

Realizing the Vision of ERP Front-ends for the real end user

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. Realizing the Vision of ERP Front-ends for the real end user May 2000 CUMREC

  2. Jennifer Foutty, Director University Information Systems www.indiana.edu/~hrsis Jfoutty@indiana.edu May 2000 CUMREC

  3. Agenda • Indiana University • The “problem” • IU’s solution • Architecture • Strategy • Real Life Examples May 2000 CUMREC

  4. IU Background • http://factbook.indiana.edu 8 Campuses Over 92,000 students enrolled state wide 14,500 full-time faculty and staff Bloomington – traditional flagship campus Indianapolis – urban campus with professional schools; includes Purdue students May 2000 CUMREC

  5. The “problem” • Most ERP systems are focused on “back office” users • Most ERP systems don’t address integration at the transaction/activity level • Most ERP systems don’t manage decision support (reporting/analysis) well • Most Universities have other systems that need to be integrated with their ERP systems • Most ERP vendors don’t address well a REAL web deployment May 2000 CUMREC

  6. Services for Faculty and Researchers Services for Students and Parents Information Environment Services for Administrators Services for Employees User Perspective May 2000 CUMREC J

  7. What does the user want? • Single sign-on • Common look-and-feel • Web access • Show them only what they need to do their business • Guide them through the process • Route information electronically when needed • One place to do all their business • Look up information when they need it • Run a report or download data when they need it May 2000 CUMREC

  8. End User Perspective • Full Piece of Business • Hire someone and Fund their pay • Register, Bill, and Pay Register, Bill and Pay Functionality Hire & Fund Functionality Bill Process Pay Process MedicineEligibility Register Process “ACE” Process Apply FA Process Hire Process Fund Process SoM System Registration PS Module Legacy System PS FA Module PS Bursar Module Financial System Human Res. System Financial System • Component architecture • Small Systems integration May 2000 CUMREC B

  9. IU’s solution • Use ERP for back-office processing • Use other vended and home grown systems that are in place or planned • Build a web front-end for all real end users • Use a portal type of environment • Put all activities in the portal, not “systems” • Be able to “swap out” systems as needed May 2000 CUMREC

  10. May 2000 CUMREC

  11. “Portal Strategy” • One-stop for all activities • Single sign-on • Web front-end, with activities available based upon who I am • Customizable • Includes all activities • “personal” for students, parents, employees • “administrative” for IU business • “analytical” for IU decision-making May 2000 CUMREC

  12. My IU Welcome! John Smith In-Box Customize My IU Enroll in Classes See my Financial Aid Perform degree audit Edit Monthly Payroll Voucher Run Payroll report Extract list of full-time faculty by dept Look at my Accumulated Benefits In-Box Customize My IU New May 2000 CUMREC

  13. IU’s Architecture • Development environment required for building front-end • Compuware’s Uniface with web deployment • Middleware to link front-end to back-end • Com+ spec, plus URBA • PeopleSoft back-end • Message agent, then “business components”? May 2000 CUMREC

  14. May 2000 CUMREC

  15. Strategy • Phase in over time • Convert legacy systems • Use metaframe for client/server on web • Begin portal with hyperlinks to other systems, then convert to activities • Design the front-end for the end user • so the back-end can evolve over time with minimal retraining • Leverage developer productivity by reusing components across systems May 2000 CUMREC

  16. Real Life Examples • IU is using PeopleSoft for HRMS and SA • Human Resources Management System – payroll, benefits admin, applicant tracking, tenure tracking, etc. • Student Information System – admissions, records, student financials, financial aid, advising May 2000 CUMREC

  17. Examples from HRMS • Administrative • Hire somebody • Put a faculty member on leave • Process timekeeping • Do the payroll • Personal • Change my benefits enrollment • Record my time off • Look at my payroll stub May 2000 CUMREC

  18. Examples from SIS • Personal • Register, pay my bill • Look up financial aid • Drop a course, with routing to advisor and financial aid office before approval • Administrative • Route admissions applications for evaluation • Load gradebook from local file, with routing to Dean’s office and Registrar before approval May 2000 CUMREC

  19. Questions? www.indiana.edu/~hrsis Jfoutty@indiana.edu 812-855-8220 May 2000 CUMREC

More Related