chabot – las positas community college district reporting strategy
TRANSCRIPT
Chabot – Las Positas Community College District
Reporting Strategy
2
Agenda
• Overview of CLPCCD Reporting Plan• Not a Crystal Reports Demo• Audience – ITS Staff• List of Criteria Used for Selecting a Reporting Tool• Our Ideas to use the Reporting Tool• Goal – Ideas to help determine your Reporting direction• Questions
3
About Chabot - Las Positas
• 2 College District• Chabot College – Hayward• Las Positas College – Livermore• District Offices – Pleasanton
• Current Adhoc Reporting / Data Extract Environment• Brio Query 6.x Client Server (Institutional Research and Financial Aid)• MS Access Tools (H/R Adhoc, Enrollment Management, Misc)• Banner Population Selection Extracts• “Call the Programmer”
• Current Parameter Driven Reporting• 30 Local Banner Web Reports with Parameters• 750 Banner Local Job Submission Reports/Processes (SQL, COBOL, C)• Banner Baseline Reports
4
List of CLPCCD User Criteria Used
• Web based• Easy and Intuitive to Use• Easy to Join Data Views• Both Adhoc Reporting and Data Extracts for End Users• Multiple output formats (Excel, HTML, Text, Charts/Graphs)• “Cohort” Tracking for Institutional Research (track across multiple terms)
5
List of CLPCCD Technical Criteria Used
• Security Administration System• Scheduling System (run reports automatically unattended)• Parameter Driven Reports• Publish Static Reports to the Web• Work with Live Database or Future Data Store / Warehouse• Shared Library of Reports and Data Extracts• Replace Current Tools (Home grown MS Access Tools)• Reduce calls to Programming Staff
6
List of CLPCCD Vendor Criteria Used
• Company Reputation and Market Share• Flexible Pricing and Licensing• Training Options
7
Tools We Evaluated
• Selection is based on your needs• Business Objects (Crystal Reports) ***CLPCCD Selection***• Hyperion (Brio Query)• MS Access• Oracle Discoverer• Others in the mix evaluated on paper
• Cognos
• Web Focus
8
Initial License Breakdown for Pilot Group
• 1 Administrator account (ITS Staff)• 7 Developer accounts (ITS Staff)• 30 End User accounts (Key Users from each functional area)• 100-150 Static Report Viewers (All Managers, Supervisors, Other)• End User Pilot Group will Help Setup Data Views• Planned Expansion
9
Adhoc Reporting / Data Extract for End Users
• Use Core Views for Each Functional Area• ODS = Operational Data Store, SCT announced at Summit 2004
their intention of getting out of the report writing business and to instead maintain ODS views.
• Use modified ODS composite views as Satellite views with a Core view
• Financial Aid example (see example chart)• CLPCCD Method used in modifying baseline ODS and Core views
(see example code)
10
Parameter Driven Reports Plan
• Reduce the number of local reports – shift to End Users• Evaluate remaining reports for duplicate/ similar info• Combine/Rewrite most remaining reports to use Satellite and Core
views to insure consistency in results• Determine best tool for rewrites (Crystal or Banner Job Sub)
11
Publish Static Reports to the Web
• Currently we publish static reports to the web (Intranet) via our enterprise server and cron jobs that run overnight or once a week
• We will evaluate these current reports to see if they should use the Satellite and Core views to insure consistency in results
• We will also evaluate whether to migrate these to the Crystal Reports server
12
Future Plans
• Move ODS Satellite and Core views to tables in a Data Store on another server (Crystal Reports Server)
• Develop method to do nightly incremental updates to these tables (model after SCT’s method described at Summit 2005 – How to Modify the Sungard SCT ODS)
• Develop views against the Data Store to create “Dashboard” type output that can be used by the Crystal Reports tool
• Expand Pilot Group
