## [TEAMWEB REPORTING]{.underline}

## [Reports]{.underline}

The TEAM-Web reporting can be broken down into essentially two
functional types---Programmatic Reports and Data Reports \[OR Status
Reports and Data Reports\]---the former provide information about the
activities and ongoing operation of TEAM-Web itself, while Data Reports
deliver information to the Grant Recipients and other users of the
system.

Programmatic Reports are essential for the success of any project and
are critical to managing risk. Their basic purpose is to give clients
and senior management a clear and precise indication of the condition of
the project as of the current moment---to examine the actual condition
of the project versus what was planned. These reports help to analyze
the situation and indicate necessary decisions regarding how to proceed,
and implement those decisions.

Data reports (such as *OTRAK*, *Special Requests Reports*, *Total
Cumulative Closed Issues Report*, *Open Functional*, *Open
Transactional*, *Posted Team Special Requests Reports*) provide various
types of information to the user base.

***Data reports are presented dynamically...***Either type of report can
be presented dynamically (as queries against the database), or as a
"static" display of information. Static reports are generally generated
via SQL scripts run against the production database, creating a
temporary master table based on several source tables. This master table
is then used to generate Excel spreadsheets, which are distributed to
the appropriate sites. Dynamic reports are created from the Reporting
Database, and allow the users to employ active search options. Users
have the option of viewing the data in excel spreadsheets or in XML
format.

TEAM-Web accommodates Special Requests reporting with the approval of
the FTA administration.

# 

# [Table Of Reports]{.underline}

Following is a chart of the various reports types and their frequency
and distribution. Reports are generally available thru TEAM-Web on TEAM
Reports. The following table lists all regularly scheduled reports, and
the general categories of ad hoc reports.

+---+---------+-------+-----------------------------------------------+
| # | #       | #     | # Description                                 |
|   |  Report | Gener |                                               |
|   |         | ation |                                               |
+---+---------+-------+-----------------------------------------------+
| 1 | Static  | Daily | Several **Static Reports** are generated via  |
| \ | Reports | (     | **SQL scripts**. SQL scripts are run against  |
| . |         | a.m.) | the production database and create a          |
|   |         |       | temporary master table based on several       |
|   |         |       | tables. Then data is populated into the       |
|   |         |       | **excel spreadsheets**. These excel           |
|   |         |       | spreadsheets are FTPed to FTA net every       |
|   |         |       | morning; categorized by subject and fiscal    |
|   |         |       | year. Beginning each FY (October) the final   |
|   |         |       | monthly report is appended for each subject.  |
|   |         |       | Example: the *Team4Compare* report compares   |
|   |         |       | TEAM data with the comparable DAFFIS system   |
|   |         |       | data. *Team4Compare* report is posted under   |
|   |         |       | Special Requests.                             |
+---+---------+-------+-----------------------------------------------+
| 2 | Dynamic | Daily | The Dynamic Reports are posted on the         |
| \ | Reports | (     | TEAM-Web under Dynamic Queries. These reports |
| . |         | p.m.) | are generated every night automatically.      |
|   |         |       | Dynamic Queries gives the users **search      |
|   |         |       | option**. The users can search the data more  |
|   |         |       | quickly by selecting fewer columns. The users |
|   |         |       | also have the option of viewing the data in   |
|   |         |       | **excel spreadsheets** or in **XML format**.  |
|   |         |       | These reports can really slow down the        |
|   |         |       | production database. In order to avoid that,  |
|   |         |       | they are run against the **Reporting          |
|   |         |       | Database**. The data in Dynamic Queries is    |
|   |         |       | identical to the data in Static Queries. Data |
|   |         |       | Warehousing technique is used for this        |
|   |         |       | purpose. The VB Modules copy the data from    |
|   |         |       | temporary master table and store it into a    |
|   |         |       | physical table in reporting database. This    |
|   |         |       | table in the reporting database gets emptied  |
|   |         |       | out every night and new data is copied over   |
|   |         |       | from the temporary master table.              |
+---+---------+-------+-----------------------------------------------+
| 3 | H       | W     | This report is a **graphical view** of the    |
| \ | elpdesk | eekly | status of CMS. It shows **closed versus open  |
| . | Status  |       | issues**, the level of the issue, and         |
|   | Reports |       | categorizes the issues by phone calls,        |
|   |         |       | e-mails, voice-messages, and internal. This   |
|   |         |       | **Excel file** is e-mailed to recipients, FTA |
|   |         |       | personnel.                                    |
+---+---------+-------+-----------------------------------------------+
| 4 | TEAM    | W     | This report gives the details of the weekly   |
| \ | D       | eekly | **Database activities** i.e. queries done,    |
| . | atabase |       | number of connections made, number of distant |
|   | Sta     | (Thur | users, number of new grants, number of grants |
|   | tistics | sday) | sent to DOL, number of grants awarded, number |
|   |         |       | of grants executed, number of grants closed,  |
|   |         |       | number of deadlocks encountered. This report  |
|   |         |       | also tells about the number of                |
|   |         |       | **checkpoints** completed and the number of   |
|   |         |       | **backups** made for the week.                |
+---+---------+-------+-----------------------------------------------+
| 5 | Weekly  | W     | This report gives the details of the weekly   |
| \ | Team    | eekly | meeting and the work done in the current      |
| . | Man     |       | week. It explains the strategy and the        |
|   | agement | (Fr   | progress of the work. It includes any         |
|   | Reports | iday) | requests made for enhancements, data fixes,   |
|   |         |       | new development and the status of the         |
|   |         |       | request. It also explains any additional      |
|   |         |       | changes needed to make the application more   |
|   |         |       | secure and user friendly. **TEAM-Web users    |
|   |         |       | conference call** is also held during the     |
|   |         |       | meeting and **Action Items/Issues** are       |
|   |         |       | purposed and assigned to the TEAM members.    |
|   |         |       | The goal for the next week and next month is  |
|   |         |       | set. The **Helpdesk and Database usage        |
|   |         |       | status** reviewed                             |
+---+---------+-------+-----------------------------------------------+
| 6 | Team    | W     | Reports the details of the TEAM Regional      |
| \ | R       | eekly | teleconference held between Help Desk, FTA    |
| . | egional |       | and Regional Managers. Generally includes:    |
|   | Con     | (Thur | The Action Items/Issues. Enhancement          |
|   | ference | sday) | Requests, Project Status and Out Standing     |
|   | Call    |       | Issues.                                       |
+---+---------+-------+-----------------------------------------------+
| 7 | FTA/CA  | W     | Reports on FTA/CA Project Status Meeting.     |
| \ | Project | eekly | Generally includes:                           |
| . | Status  |       |                                               |
|   | Report  | (     | Review Enhancement Requests, Project Status,  |
|   |         | Wedne | Reports, HQ Items, CMS Review, Security       |
|   |         | sday) | Issues,                                       |
|   |         |       |                                               |
|   |         |       | Data Fixes and Databases, Network and         |
|   |         |       | Hardware Issues, HelpDesk/Training, Year End  |
|   |         |       | Close and Outstanding Issues.                 |
+---+---------+-------+-----------------------------------------------+
| 8 | De      | W     | This internal report describes any additional |
| \ | veloper | eekly | issues being addressed by the development     |
| . | Fixes   |       | team.                                         |
+---+---------+-------+-----------------------------------------------+
| 9 | Team    | Mo    | This report summarizes accomplishments and    |
| \ | Summary | nthly | on-going efforts to improve the application   |
| . | Report  |       | and achieve goals (includes testing,          |
|   |         |       | debugging, CMS issues closed, and training    |
|   |         |       | sessions). This report also explains the      |
|   |         |       | efforts made for maintenance of the           |
|   |         |       | application (Networking, back-ups, etc.), and |
|   |         |       | briefly explains the issues resolved by Help  |
|   |         |       | Desk.                                         |
+---+---------+-------+-----------------------------------------------+
| 1 | TEAM    | Mo    | This report explains the issues resolved by   |
| 0 | Status  | nthly | the Help Desk, the data fixes made, the       |
| \ | Report  |       | support provided for the DAFIS system, the    |
| . |         |       | continued efforts made to test and debug      |
|   |         |       | TEAM-Web, continued efforts made to develop,  |
|   |         |       | modify and test new enhancements, the         |
|   |         |       | lifecycle cost incurred for the maintenance   |
|   |         |       | and development.                              |
+---+---------+-------+-----------------------------------------------+
| 1 | Total   | W     | Posted to FTA net, Special Requests. This     |
| 1 | Cum     | eekly | report includes all the closed issues entered |
| \ | ulative |       | in the CMS. The report is generated directly  |
| . | Closed  | (Fr   | from the online Change Management System      |
|   | Issues  | iday) | web-reporting tool. The desired data is then  |
|   | Report  |       | extracted and formatted into a Microsoft      |
|   |         |       | Excel spreadsheet.                            |
+---+---------+-------+-----------------------------------------------+
| 1 | Open    | W     | Posted to FTA net, Special Requests. This     |
| 2 | Fun     | eekly | report includes all the open Functional       |
| \ | ctional |       | issues entered in the CMS. The report is      |
| . |         | (Fr   | generated directly from the online Change     |
|   |         | iday) | Management System web-reporting tool. The     |
|   |         |       | desired data is then extracted and formatted  |
|   |         |       | into a Microsoft Excel spreadsheet.           |
+---+---------+-------+-----------------------------------------------+
| 1 | Open    | W     | Posted to FTA net, Special Requests. This     |
| 3 | Transa  | eekly | report includes all the open Transactional    |
| \ | ctional |       | issues entered in the CMS. The report is      |
| . |         | (Fr   | generated directly from the online Change     |
|   |         | iday) | Management System web-reporting tool. The     |
|   |         |       | desired data is then extracted and formatted  |
|   |         |       | into a Microsoft Excel spreadsheet.           |
+---+---------+-------+-----------------------------------------------+
| 1 | T       | Mo    | Monthly report of all the issues entered into |
| 4 | EAM-Web | nthly | the CMS. Issues are broken down by status and |
| \ | CMS     |       | level. The report is generated directly from  |
| . | Issues  |       | the online Change Management System           |
|   | Br      |       | web-reporting tool. The desired data is then  |
|   | eakdown |       | extracted and formatted into a Microsoft      |
|   |         |       | Excel spreadsheet.                            |
+---+---------+-------+-----------------------------------------------+
| 1 | Closed  | Mo    | Summary of the data issues (open and closed)  |
| 5 | CMS     | nthly | for the month. The report is generated        |
| \ | Fixes   |       | directly from the online Change Management    |
| . |         |       | System web-reporting tool. The desired data   |
|   |         |       | is then extracted and formatted into a        |
|   |         |       | Microsoft Excel spreadsheet.                  |
+---+---------+-------+-----------------------------------------------+
| 1 | Special | Ad    | Upon FTA approval, Special Requests reports   |
| 6 | R       | hoc   | are generated on a unique or re-occurring     |
| \ | equests |       | basis. Mark Lusk runs the SQL scripts to      |
| . | Reports |       | generate the reports. Once FTA approves the   |
|   |         |       | reports, these reports are FTPed to FTA net   |
|   |         |       | and are posted under the Special Requests.    |
+---+---------+-------+-----------------------------------------------+
| 1 | OTRAK   | Mo    | The Report is used to keep track of the total |
| 7 |         | nthly | obligations of the recipients for each month. |
| \ |         |       | The report is generated via SQL scripts and   |
| . |         |       | FTPed to FTA net. This report is posted under |
|   |         |       | Special Requests. This report has to be       |
|   |         |       | posted on the web by 15^th^ of the month The  |
|   |         |       | report contains the information about the     |
|   |         |       | recipient, such as: Recipient ID, Duns\_      |
|   |         |       | Number, Recipient_Name, Recipient_City,       |
|   |         |       | Recipient_State, Cost\_ Center, and           |
|   |         |       | OpenGrants.Amount.                            |
+---+---------+-------+-----------------------------------------------+