Appendix A Reporting Portal Requirements.doc

APPENDIX A

Reporting Portal High Level Requirements

SAMPLE VIEWS

The contractor shall provide a Web Enabled Reporting Portal that is accessible to Department of Education through Internet Explorer (7.0 current version) and that provides summarized data from all FOTW surveys conducted (beginning in 2009) thru the current period. The contractor shall update the survey response data/information for each portal view on a daily basis, at a minimum.

1. Primary Portal View:

The Primary Portal View shall provide a summary page for the most current week and the two prior weeks of data responses along with a cumulative summary for the current survey period. The Portal shall provide tabulated results for key surveyed items (stub). Additionally, for up to 20 data elements (segments below), mostly demographic factors with preset item responses that will be indicated when the element is selected, users shall be able to query the “view” to create more customized reporting of the Primary Portal View. Query capability shall have a “clear selection” button that allows the “view” to refresh to the summary page as initially configured. A “save” functionality shall allow the user to export the “view” to an excel spreadsheet for permanent storage. A “print” functionality shall also be available.

In addition, FSA requires that the portal page assign to key data element a green, red or yellow status based upon predefined performance parameters. See Primary Portal View example below.

2. Standard Querying Page/View

A secondary view shall permit the user to submit preset queries to the entire databases of responses that have been collected since the survey’s inception in 2008. The preset queries shall be based upon up to 20 data elements mostly demographic factors with preset item responses (segments below). The user shall be able to select multiple data elements (segments), but will only be able to select one preset response per element. These will be the same set used to query the “Primary Portal View.”

Additionally this view shall be built with a query capability that allows the user to time box/specify a time period of responses from beginning in 2008 through the current period. The view shall show the user the time period specified for validation. Query capability shall have a “clear selection” button that will allow the “view” to refresh to the summary page as initially configured. A save functionality shall allow the user to export the “view” to an excel spreadsheet for permanent storage. A “print” functionality shall also be available.

3. Graphing and Charting View Building on the second view, a third view shall permit the user to graphically chart results of queries. Basic functionality of the second view shall be available in this view; however, results shall be shown graphically in the form of bar, and pie charts. In addition, graphics shall be predefined and present results from a specific set or bank of questions (not just individual responses). A selection button shall present the choices of these question sets or bank of questions; however, preset queries (as defined in the secondary view) will be able to run against them and those results will be presented.

4. Query by Predefined Table Views The fourth view shall contain all the functionality described in the second view; however, this view not only will allow the user to submit standard queries as described in the second view, but in addition, it will also provide a cross of those results by pre-defined data element item responses (in a table view). For example, in the screen shot below all data are requested from segments, crossed by the language element which includes two predefined responses, English and Spanish.

5. Trending View

Trending View shall provide graphical trending information by year or quarter, as defined by the users. This means that all data since inception will be available for this view; however, collected data shall be available for the specific data defined in advance for predefined question sets or question banks (much like view #3). These predefined question sets or question banks shall be provided as selections in the View.

All data shall also be available for queries and presented based upon the standard preset queries described in the standard querying page view. Toggle switches shall allow the viewer to add or eliminate specific question sets or temporal selections. Print and save functionalities shall be available in this view.

6. Verbatim View Verbatim View shall allow the users to define specific criteria that will help identify verbatim comments. Users shall have the option of downloading verbatim comments into either Excel or Word formats. It shall contain both the preset queries and time box selections as indicated in view 2, as well as the predefined question sets or question banks identified in views 3 and 5. In addition, users shall be able to select actual scored responses. For example, in the screen shot below the user could ask to see all verbatim responses for respondents who reported their dependency status as independent between March 1 and March 15 of 2010 and reported their actual satisfaction level to be between 45-62. Entire verbatim comments shall be displayed to the user in this view.

7. Weekly View

Weekly View shall provide similar information to the primary portal page view; however, data shall be provided for up to 10 weeks of the current cycle. Data shall be chartable; however, no querying function is required. Save functionality is needed that will allow exportation of results to excel, as well as print functionality.

8. General Requirements The current version of the questionnaire and an instruction page shall be posted on the site. The user must be able to easily navigate between the various views. Response time between the initiation of the query and appearance of the results must be within 20 seconds. Historical data that must be loaded to the site shall be predefined prior to implementation (in the event that not all data elements are easily cross-walked to the current configuration). Approximately 30,000 survey records will be added to the historic database.