480 likes | 630 Views
Pre-Programmed Thread Tool Recommendation. Pre-Programmed Thread February 12, 2002. Project Organization. Pre-Programmed Reporting Thread Focuses on the manipulation of pre-programmed (canned) reports that are currently generated in IMPAC II Ad – Hoc Reporting Thread
E N D
Pre-Programmed Thread Tool Recommendation Pre-Programmed Thread February 12, 2002
Project Organization • Pre-Programmed Reporting Thread Focuses on the manipulation of pre-programmed (canned) reports that are currently generated in IMPAC II Ad – Hoc Reporting Thread Focuses on allowing the NIH user community to query the IMPAC II DB (OLTP & IRDB) to retrieve data on an ad hoc basis. Pre-Programmed Reporting
Pre – Programmed Team • Sherry Zucker, Chief • Andy Greenleaf, SWEG • Krishna Collie, Analyst • Vish Kaliappan, Developer • Mark Parker, Developer • Natasha Globus, Developer • Irina Knyazeva., Developer Pre-Programmed Reporting
Executive Summary • User requirement - Manipulation format of business area reports on-line, and download report to desktop tool for further manipulation. • Analysis – evaluate COTS tools against stated requirements and test using IMPAC II report. • Recommendation – Oracle Discoverer Pre-Programmed Reporting
Reporting Objectives • To provide reporting alternatives • On Line Manipulation of report • Ability to download to spreadsheet • Web publishing capability Pre-Programmed Reporting
Categories of Evaluation Criteria Used • Go/No Go Criteria • General Criteria – Must, Should, Could • Support and Maintenance Criteria • Security Criteria • Performance Metrics • Other Considerations Pre-Programmed Reporting
COSSET Commercial Off-The-Shelf System Selection and Evaluation Technique (COSSET) Pre-Programmed Reporting
Functional Requirements • Ease of use by end user • Allow users the ability to manipulate “canned” reports • Export report to Excel • Performance comparable to current report generation Pre-Programmed Reporting
Technical Requirements • Must use Oracle stored Procedures – Go/No Go Decision point • Ease of creating/maintaining meta-layer • Scalability across the enterprise • Integrates with IMPAC II applications Pre-Programmed Reporting
Vendor Survey • Market Leaders* • Hummingbird • COGNOS • Business Objects • ORACLE *(Gartner Group Survey) Pre-Programmed Reporting
Product Evaluation • Reports: Complex & Simple • Complex • Voter Matrix Report • Meeting Roster Report • Typical • Master List of Applications Pre-Programmed Reporting
Hummingbird – not compatible with Oracle stored functions Cognos – Meta Layer difficult; can’t self join a table > 1 time Business Objects – strong second place Discoverer – meets most of our criteria Results of Evaluation Pre-Programmed Reporting
Finalists • Oracle Discoverer (client server c/s) • Business Objects (c/s & web) Pre-Programmed Reporting
Benefits to User Community • Reporting Flexibility • Sort Order (ascending &descending) • Configuration of columns & rows • Ability to highlight text i.e., bold, italics, font color & size • Business view hides underlying complexity (user doesn’t see complexity) • List of pre-defined reports for end users • Web publishing of reports Pre-Programmed Reporting
Benefits to Developers & Project • Don’t have to develop as many reports • user can reorder columns and change sort • For simple to moderate reports, faster and easier to develop report in Discoverer than to use Oracle Reports Pre-Programmed Reporting
Output Choices for Users • Canned report developed using Oracle Reports – traditional canned pdf; highly formatted. • Canned report developed using Oracle Discoverer - can manipulate online and export to Excel. • ICSTORe –document ordering (Merge, Zip, Central Print, books), export customized hitlist to Excel, no formatting (e.g., multi-line addresses), no calculated columns (e.g., scores). • Ad Hoc Query Tool – to be discussed Pre-Programmed Reporting
Developer Options • Oracle Reports – complex reports e.g. CM female/minority report; pre-printed forms • Discoverer – simple to moderate reports e.g. Meeting Roster, Voter Matrix • ICSTORe - complex reports e.g. ICO Workload report (customizable hit list) Pre-Programmed Reporting
Deciding which tool to useCollaboration between Users & Developers • Define requirements for report • Decide which tool can do the job • What provides most benefit for user? • What makes most business sense? • Assist users in understanding trade – off between options e.g. online manipulation vs. robust development • Developer can start build using Discoverer and switch to Oracle Reports without losing work. Pre-Programmed Reporting
Existing Reports • Identify candidates to redo in Discoverer • Verify candidates with user community • examine reports by business area • identify candidates for online manipulation and download capability to a spreadsheet Pre-Programmed Reporting
Architectural Issue • Integration into IMPACII applications • Launching Discoverer reports should be seamless to user. • Integration of Discoverer into Architecture • Will run-time be required on Users’ Desktops? • Citrix Server? • Web or Client/Server version? • How will Discoverer be integrated into J2EE architecture? {has web based component} Pre-Programmed Reporting
Transition Phase • Pre Pilot/Pilot (select users; e.g. Users who have requested this capability) • Integration into eRA enterprise applications • Full Deployment to user community • Documentation/Training/Outreach Pre-Programmed Reporting
Oracle Discoverer 4 Sample Reports Selected Features