1 / 20

Task Force on Reporting Strategies

This report explores various strategies and insights from prominent institutions on optimizing reporting in student administration systems. It covers experiences from the University of Wisconsin, College of Lake County, Trinity College, and more. Key topics include the transition to using data warehouses, challenges with PeopleSoft's reporting capabilities, and effective reporting tools such as Cognos and SPSS. By examining these case studies, the report provides valuable recommendations for developing robust reporting frameworks in educational institutions.

chakra
Télécharger la présentation

Task Force on Reporting Strategies

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. Task Force on Reporting Strategies February 6, 2003 Student Administration Laura Stoll

  2. Information Sources • HUEG PAG Membership 2002-2003 (Reporting and Student) • HUEG 2002/2003 Reporting and Analysis Track – Student Emphasis • Colleagues

  3. Information Sources • University of Wisconsin (Kathy Luker, Consultant in the Office of Quality Improvement) • College of Lake County (Nancy McNerney, Asst VP for Institution Effectiveness and Planning) • Trinity College (Gwen Stengel, Technology Solutions Specialist) • University of Alberta (Bill Cairns, Dir Information Development) • Indiana University (Cheryl Stine, Office of VP Information Tec)

  4. Information Sources • University of Kansas (Ryan Cherland, Dir of Univ Information Management/Assoc Dir of Inst Research) • University of Minnesota (Shelly Diers, Assoc Dir Information Solutions) • PAG link to shared data models http://www.trincoll.edu/~gstengel/

  5. University of Wisconsin • Live with SA for three years, first PS package and began at Madison campus • Early adapter, thought PS would come with reports, wrong • Query tool wasn’t a solution, couldn’t run against production system

  6. University of Wisconsin • Prior to PS had 10 years of experience with data warehouse • First year live in PS, didn’t have any reports • After first year, redesigned warehouse views to PS structure, populated with PS data • End user committee developed and enhanced views to meet user needs

  7. University of Wisconsin • Now have developed web site distribution of data info based on security • Brioquery and MicroSoft Access • Next project, retention data views back to 1985 • Wish list of data view projects • Quote – “PeopleSoft is a transaction system, not a reporting system”

  8. College of Lake County • Live with SA since 2000 • Restricted by budget, no reporting plan, community college • Quote – “If we can’t get the students into the system, no use trying to count” • Created huge extract files (200 data items per student) • Used SPSS as tool to get data out, good for 90% of reports

  9. College of Lake County • PeopleSoft product – RDS – same as extract file, no history data, cost, some problems, not supported by PS • DePaul, Minnesota and Cornell have had success with data warehouse

  10. Trinity College • Uses Cognos reporting tool, see session at the HUEG • TCDART “Trinity College Data Analysis Reporting Tool” • Cognos’ PowerPlay module also used at Northwestern and Georgetown • More information at http://tcdart.trincoll.edu

  11. University of Alberta • Too complex to report from Peoplesoft, 6,000+ tables, transaction system • Decided to separate data for reporting from the base system • Purchased PeopleSoft’s Reporting Data Service (RDS) and the Operational Data Store as well as other packages, ninth institution to purchase them • Due to budget constraints, have not progressed very far with RDS

  12. University of Alberta • Currently using Cognos DecisionStream as the ETL tool (extraction-transformation-loading) to populate their data mart • Using Cognos PowerPlay and Impromptu for web and desktop clients • Recommends Cognos, but also thinks Brio is good

  13. University of Alberta • PeopleSoft is moving toward a solution, new Enterprise Performance Management, now called Enterprise Data Warehouse • Quote – “we need to free the data from the shackles of the OLTP systems so that we can play with it”

  14. Indiana University • Only Admissions in production, using Oracle pl/spl scripts to build tables for reporting • Tables are also available for data extracts via an IU written web application • Recently purchased PeopleSoft RDS, installing next month • Will use RDS tables as their data warehouse reporting tables, adding their own security and customizations • Will continue to use SQR for reporting tool until can purchase ad-hoc reporting tool

  15. University of Kansas • Currently live with Admissions, student records going live in March, 8.0 • Legacy used DEMIS (Department Executive Management Information System) • DEMIS system has web front end with datamarts underneath • HR and Finance have moved to datamarts

  16. University of Kansas • For student, purchased PS RDS, gives a good start to creating datamarts • Will continue to use DEMIS for web front end and reporting, extracting with RDS • Using RDS structure, will add column for census data and rebuild historical information, don’t need to reinvent structure

  17. University of Kansas • PeopleSoft RDS - $120,000, Cognos DecisionStream - $20,000, hardware, installation time three weeks, and have to do customizations • RDS is a good start, saves time, but your cost is buying the mapping, “gets the job done”

  18. University of Minnesota • http://dw.umn.edu/ • Home grown web interface

  19. Summary observations • Reporting should not be done against the production instance, nor against a copy if at all possible • A datamart or data warehouse has been the route of choice for successful institution reporting • Web interfaces for distributed reporting • PeopleSoft RDS for possible mapping assistance, but costs

  20. Questions?

More Related