PHAS Score Adjustments User's Guide-20120119.pdf

PIR1 PHAS Score Adjustments

User’s Guide

PIR1 PHAS Adjustments User’s Guide

2 | P a g e January 19, 2012

Contents

I. PIR1 PHAS Score Adjustments Tool Overview

I. Guidelines for Appeals, LPF, Waivers, Petitions and General Response

Late Penalties Related to FASS-PH Submissions

Extensions and Waivers Related to PHAS

Starting the PHAS Adjustments database

PHAS Score Adjustments – Main Menu

PHAs Adjustments – Application Navigation Menu

PHAs Appeals Add / Edit

PHAs Appeals – Appeals View Only

Late Presumptive Failure (LPF) Add / Edit

Late Presumptive Failure (LPF) View/Update Attachment

Waiver/Petition/General Response - Add New /Edit

Waiver/Petition/General Response – Edit Projects

Waiver/Petition/General Response – View/ Update Attachments

Reference Tables Maintenance

User Maintenance

Reports

3 | P a g e

I. PIR1 PHAS Score Adjustments Tool Overview

PIR1 PHAS Adjustment tool was designed to assist users in the process of entering /updating and approving appeals, Late Presumptive Failure (LPF), Waivers, petitions and general responses.

The Database is designed to accommodate PHAs with different Fiscal Year End (FYE) range.

Ex: PHAs FYE range for PIR1 is 03/31/2011 to 12/31/2011 - and for PIR2 the range is 03/31/2012 to

12/31/2012.

From the first screen the user can select the desired FYE range by selecting PIR1 or PIR2. Application navigation per PIR1 or PIR2 is realized via the navigation menu. Navigation menu is designed with 4 sections based on the user’s interest as follow: PHAS Appeals; Late Presumptive Failure (LPF); Waivers/Petitions/General Response;

and Reports and Reference Tables. The sections can be accessed based on a user’s privileges.

I. Guidelines for Appeals, LPF, Waivers, Petitions and General Response

Penalties

Financial Submissions are required under 24 CFR 5.801 Uniform Financial Reporting Standards (UFRS). 24 CFR 5.801(d) states: Unaudited financial statements will be required 60 days after the PHA’s FYE, and audited financial statements will be required no later than 9 months after the PHA’s FYE, in accordance with the Single Audit Act and OMB Circular A-133. 24

CFR 5.801(f) states that the responsibility for submission of the financial report due to HUD rests with the PHA.

Financial submissions, thus the PHAS score, are subject to the following penalties:

1) Late Penalties,

2) Late Presumptive Failure (LPF),

3) Audit Penalties, and

4) Significant Change Penalty.

Extensions and Waivers may prevent the impact of Late Penalties and Late Presumptive Failure (LPF). Late Penalties and

LPF are handled in NASS and will be addressed here. Audit Penalties and Significant Change Penalty are handled in FASS and will be addressed in the PIR1 FASS User’s Guide.

Late Penalties Related to FASS-PH Submissions Penalty Subsystem Applies to FASS-

PH Submission Result

Unaudited Submission (Extensions, Late Penalties & LPF are applicable)

Submission Due Date 2 Months after FYE

Extended Submission Due Date 2 Months after FYE + Number of Days of Approved Extension

4 | P a g e

Late Penalties Related to FASS-PH Submissions Penalty Subsystem Applies to FASS-

PH Submission Result

LPF Due Date 5 Months after FYE (LPF generated 1 st day of 6 th

Month)

Extended LPF Due Date 5 Months after FYE OR Due Date + Number of Days of Approved Extension, whichever is greater

Audited Submission (Waivers & LPF are applicable)

Submission Due Date 9 Months after FYE

LPF Due Date 9 Months after FYE (LPF generated 1 st day of 10 th

Month)

Waiver of Audited Due Date No set date for waiver unless there is a Waiver End Date If PHA has a FASS Waiver, no LPF will be generated unless the PHA does not submit prior to the Waiver End

Date, if applicable

Late Penalties NASS Unaudited (56) Late Penalty Adjustment to PHAS Score

Unaudited submissions are due 2 months after the PHA’s FYE.

However, late penalty points are not assessed until the 16 th day of the 3 rd month after FYE.

1 penalty point is assessed for every 15 days past due for unaudited FASS Submission:

16 – 30 days late – 1 Penalty Point 31 – 45 days late – 2 Penalty Points 46 – 60 days late – 3 Penalty Points 61 – 75 days late – 4 Penalty Points 76 – 90 days late – 5 Penalty Points

The PHA Score Report shows the late penalty point adjustment, if applicable, separate from the four indicator scores. Late penalties assessed for the unaudited financial submission carry forward to the audited submission even if the PHA submits its audited financial statements on time.

Note: PHA cannot receive both late penalty points and LPF for the same submission. If the unaudited is submitted 3 months late, an LPF is assessed in lieu of late penalty points.

Rejected Unaudited Submissions: If the Unaudited Submission is rejected or invalidated after the submission due date, late penalties will be assessed based on the rejected or invalidated date. 1 late penalty point will be assessed for every 15 days past due the rejected due date (not the original submission due date).

TBD: 1) LPF Due Date for Rejected Unaudited Submissions and 2) Invalidated Unaudited Submissions and LPF Due Date.

Extensions: Calculation of late penalty points must be based on Due Date + Number of Days of Approved Extension, if applicable.

Late Presumptive Failure (LPF)

NASS Unaudited (56) Audited (57)

Late Presumptive Failure Adjustment to FASS Score

5 | P a g e

Late Penalties Related to FASS-PH Submissions Penalty Subsystem Applies to FASS-

PH Submission Result

If the PHA submits its unaudited financial statements 3 months late (5 months after FYE), the PHA receives a Late Presumptive Failure (LPF), which means a FASS Score of zero. An LPF assessed for the unaudited financial submission carries forward to the audited submission even if the PHA submits its audited financial statements on time. That is, if the PHA receives an LPF (score of zero) for its unaudited submission, the PHA also receives a score of zero for its audited submission.

If the PHA submits the audited financial statements after the due date (9 months after FYE), the PHA receives an LPF.

LPFs will be assessed in consultation with the NASS Program Manager. LPFs may be batch processed 5 months (unaudited) or 9 months (audited) after the FYE + 7 days to allow REAC management to QC LPFs prior to LPFs being assessed.

Rejected or Invalidated Audited Submissions: If the Audited Submission is rejected or invalidated after the submission due date (9 months after FYE), the PHA will have 15 days to resubmit. If the PHA does not resubmit within 15 days, an LPF will be assessed (FASS score of zero). Note: This is different than Unaudited (late penalties are N/A) and NASS Business needs to make decision.

Unaudited Extensions: Extended LPF Due Date 5 Months after FYE OR Due Date + Number of Days of Approved Extension, whichever is greater.

Waiver of Audited Submissions: Waiver of Audited Due Date No set date for waiver unless there is a Waiver End Date. If PHA has a FASS Waiver, no LPF will be generated unless the PHA does not submit prior to the Waiver End Date, if applicable.

Audit Penalties FASS Audited (57) Tier 1, 2 &/or 3 penalties assessed for the Audited submission

Significant Change Penalty

FASS Audited (57) Significant differences between the unaudited and audited submissions represented by an overall score decrease of 3+ points.

This represents a Tier 2 audit penalty.).

Guidance from PHAS Interim Rule on Late Penalties and Late presumptive Failure (LPF)

§902.62 Failure to submit data provides the following guidance on late penalties and late presumptive failure (LPF):

902.62(a)(1) If a PHA without a finding of good cause by HUD does not submit its year-end financial information, required by this part, or submits its unaudited year-end financial information more than 15 days past the due date, 6 | P a g e appropriate sanctions may be imposed, including a reduction of one point in the total PHAS score for each 15-day period past the due date.

902.62(a)(2) If the unaudited year-end financial information is not received within 3 months past the due date, or extended due date, the PHA will receive a presumptive rating of failure for its unaudited information and shall receive zero points for its unaudited financial information and the final financial condition indicator score. The subsequent timely submission of audited information does not negate the score of zero received for the unaudited year-end financial information submission.

902.62(a)(3) The PHA’s audited financial statement must be received no later than 9 months after the PHA’s fiscal year-end, in accordance with the Single Audit Act and OMB Circular A-133 (see 902.33(c)). If the audited financial statement is not received by that date, the PHA will receive a presumptive rating of failure for the financial condition indicator.

§902.60 Data Collection provides the following guidance on late penalties for rejected submissions:

§902.60 (d) Rejected unaudited financial submissions. When HUD rejects a PHA’s year-end unaudited financial information after the due date, a PHA shall have 15 days from the date of the rejection to resubmit the information without a penalty being applied, in accordance with §902.62.

§902.60 Data Collection provides the late points and late presumptive failure for the Management Operations Indicator:

§902.60(e) provides the following guidance on Late points and late presumptive failure (LPF) will only be applied to the financial condition indicator since the management operations information is derived from the financial condition submission. However §902.62(c) Failure to submit states that “If a PHA does not submit its unaudited or audited information, it will receive a zero for management operations.

Extensions and Waivers Related to PHAS Subsystem Applies to FASS-

PH Submission Result

Extension FASS Unaudited (56) Extensions impact Late Penalty & LPF Unaudited Submission

Submission Due Date 2 Months after FYE

Extended Submission Due Date 2 Months after FYE + Number of Days of Approved Extension

LPF Due Date 5 Months after FYE (LPF generated 1 st day of th Month)

Extended LPF Due Date 5 Months after FYE OR Due Date + Number of Days of Approved Extension, whichever is greater

Extensions: Calculation of late penalty points must be based on Due Date + Number of Days of Approved Extension, if applicable.

7 | P a g e

Extensions and Waivers Related to PHAS Subsystem Applies to FASS-

PH Submission Result

Waiver FASS Audited (57) Waivers impact LPF Audited Submission

Submission Due Date 9 Months after FYE

LPF Due Date 9 Months after FYE (LPF generated 1 st day of th Month)

Waiver of Audited Due Date No set date for waiver unless there is a Waiver End Date

If PHA has a FASS Waiver, no LPF will be generated If the Waiver has a Waiver End Date, the PHA must submit prior to the Waiver End Date or an LPF will be generated

Waiver PHAS N/A Waivers impact PHAS Score Waiver may apply to PHAS score or a specific Indicator Waiver may or may not have a Waiver End Date If the Waiver is Granted, PHA will not receive an LPF If the Waiver is Granted, PHA may not receive a PHAS Score unless 1) there is a Waiver End Date or 2) the PHA submits the data for the Waived Indicator

Guidance from PHAS Interim Rule on Extensions and Waivers

§ 902.60 Data collection. (b) Request for extension of time to submit unaudited financial information. In the event of extenuating circumstances, a PHA may request extensions of time to submit its unaudited financial information. To receive an extension, a PHA must ensure that HUD receives the extension request electronically 15 days before the submission due date. The PHA’s electronic extension request must include an objectively verifiable justification as to why the PHA cannot submit the information by the submission due date. PHAs shall submit their requests for extensions of time for the submission of unaudited financial information through the FASS–PH Secure Systems Web site. HUD shall forward its determination electronically to the requesting PHA.

§ 902.60 Data collection. (c) Request for waiver of due date for PHA submission of audited financial information.

(1) HUD, for good cause, may grant PHAs a waiver of the due date of the submission of audited financial information to

HUD. HUD shall consider written requests from PHAs for a waiver of the report submission due date (established by the

Single Audit Act and OMB Circular A–133 as no later than 9 months after the end of the fiscal year). The PHA’s written request for a waiver of the due date of the submission of audited financial information must include an objectively verifiable justification as to why the PHA cannot submit the information by the submission due date. A PHA shall submit its written request for such a waiver, 30 days prior to the submission due date, to its local field office. HUD shall forward its written determination of the waiver request to the PHA and, if appropriate, establish a new submission due date for the audited financial information.

8 | P a g e

(2) A waiver of the due date for the submission of audited financial information to HUD does not relieve a PHA of its responsibility to submit its audited information to OMB’s Federal Audit Clearinghouse no later than 9 months after the end of its fiscal year.

9 | P a g e

Starting the PHAS Adjustments database

Double click the PHAS Adjustments icon.

If you get the message shown in Figure 1, it means that your information is missing from the table containing the User’s. In this case the user has no rights to access ‘PHAS Adjustments’. This can only be corrected by the PHAS Adjustments System

Administrator. After clicking the OK button the application will terminate.

Figure 1 - PHAs Adjustments Database – Message for user with no rights to access database

If you get the message shown in Figure 2, it means that your information is in the table containing the User’s but your status is Inactive. In this case the user has cannot access ‘PHAS Adjustments’. This can only be corrected by the PHAS

Adjustments System Administrator. After clicking the OK button the application will terminate.

Figure 2 - PHAs Adjustments Database – Message for inactive user

If you get the message shown in Figure 3, it means that your information is in the table containing the User’s and you have an active status. In this case the user has you can access ‘PHAS Adjustments’database and ‘Refresh AMP Listing’ screen shown in Figure 3 below will pop up allowing to choose to refresh or not the internal AMP listing with the data from Data

Warehouse . The refresh of AMP listing with the data from Data Warehouse starts once the user selects OK.

Figure 3 - PHAs Adjustments Database – Refresh AMP Listing message (apply to active user)

10 | P a g e

PHAS Score Adjustments – Main Menu

Once the ‘Refresh AMP Listing’ process completed or if user chooses to Cancel the ‘Refresh AMP Listing’, the PHAS Adjustments Main Menu will pop up – Figure 4. PHAS Adjustments Main Menu has three options PIR1, PIR2 and Backup/Update Z: drive. To Exit the PHAS Adjustments database click Exit database button.

From the PHAS Adjustments Main Menu the user can select the PHAS Adjustments FYE range data to update or view.

Based on privileges the ‘Backup/Update Z: drive’ button is either visible or not and allows the user to perform an administrative backup and update function.

Figure 4 - PHAs Adjustments Database - Main Screen

PIR1 gives you access to PHA’s having FYE in the range of 03/31/2011, 06/30/2011, 09/30/2011, 12/31/2011.

PIR2 gives you access to PHA’s having FYE in the range of 03/31/2012, 06/30/2012, 09/30/2012, 12/31/2012.

Backup/Update Z: drive button once clicked starts the backup process of the PHAS Adjustments data to the server in the backup folder. The user can choose to refresh the PHAS Adjustments data from the server by clicking OK on the message shown in Figure 5.

Figure 5 - PHAs Adjustments Database - Main Screen- Backup/Update Z: drive

11 | P a g e

PHAs Adjustments – Application Navigation Menu

Once the user click the PIR1 or PIR2 button the ‘Navigation Menu’ screen presented in Figure 6 will pop up. The ‘Navigation

Menu’ functions are available based on user privileges. The screen below shows the ‘Navigation Menu’ functions for a user having all the privileges.

Figure 6 – PHAs Adjustments Database - Navigation Screen for PIR1/PIR2

All active users can access at least ‘Reports’ function as shown in Figure 7.

Figure 7– PHAs Adjustments Database - Navigation Screen - Reports

12 | P a g e

PHAs Appeals Add / Edit

The option allows the user to add or to edit appeals depending on selected period (PIR1 or PIR2).

Figure 8 – Add / Edit PHAs Appeals

PHAs Appeals Add New screen has 5 functions as follow:

Add New: Allows the user to add “Appeals” based on the privileges.

Edit: Allows the user to add, edit, delete or view only the “PHAs Appeals” based on the privileges.

Email Appeals in Progress: Allows the user to send via email the ‘Appeals in Progress’ report.

Print: Allows the user to print the current appeal as seen on the screen as shown.

Cancel: Reverses the transaction and clears the form.

Save: Saves the data entered. A pop-up screen informs the user that the Appeal entered is saved.

Close: Allows the user to close the form without saving.

13 | P a g e

PHAs Appeal -Add New function

Once the user selects Add New button the screen shown in Figure 9 will pop up.

Seq.No. and Type fields are populated automatically, allowing the user to enter the PHA Code or to select from the list.

Once the user enter / select from the list the PHA Code the PHA Name is populated automatically.

A list with the Appeals already entered for this particular PHA appears on the bottom of the form showing the Seq.No, FYE, SubSystem, Status and Status Date.

Figure 9 - Add New PHAs Appeal

When Save is requested, the system validates the data and commit/reject the transaction. The user is informed the record entered was saved via a pop up screen as presented in Figure 10.

Figure 10 - Add New PHAs Appeal - Save

The system will not allow an appeal to be entered for 2 reasons: PHA + FYE+Subsystem already is in the database and the status = In Progress; or because the PHA +FYE is not found in PHAS Scoring Output table.

In the case when the user tries to Save an appeal that already exits in the database with the status of “In Progresss” the system will inform the user that the PHA already exists in the database and the transaction will be cancelled as presented in Figure 11.

14 | P a g e

Figure 11 - Add PHAs Appeal Cancelled

In case the user invokes the save function for an appeal in which a PHA does not exist in the ‘PHAS Scoring Output’ table

(which holds all the PHAs within the current submission), a message will inform the user, and the transaction will be cancelled as shown in Figure 12.

Figure 12 - Add PHAs Appeal Cancelled 2

In case the user Saves an appeal that already exits in the database and has a status other then

“In Progresss,” the system will inform the user that the PHA already exists in the database and will ask the user if they want to continuing adding the data for a specified PHA as presented in Figure 8. If the user responds Yes, the appeal is entered again.

Cancel function, reverses the transaction and clears the form.

Close function, closes the screen without saving.

Email function, allows the user to send ‘Appeals in Progress ‘ report as shown in Fig 13.

15 | P a g e

Figure 13 – Email ‘Appeals in Progress

Print function allows the user to print the appeal from the screen. To print the appeals from the screen click the print button. With the report on the screen right click the mouse button to get the list from where to choose page setup, printer, and close. Select printer and on Print click OK to print or Cancel to terminate the printing request. To close the report click close.

Figure 14 – Print the current PHAS Appeals

16 | P a g e

PHAS Appeal Add New option - Edit function

Allows the user, based on the privileges, to Edit “Appeals”.

Once the user clicks the Edit button, “Appeals in Progress Selection “ form will pop up allowing the user to select the PHA appeals to be edited by choosing “OK Selection” or to cancel by choosing “Cancel Selection” – Figure 15.

After the user selects “OK Selection” the form will be populated with the existing data to be edited.

To save the record, select Save. To Cancel the edit, select Cancel or Close which will close the form without saving.

Figure 15- Edit PHAs Appeals

Edited record can be printed using Print function as shown in Figure 16.

Figure 16- Print PHAs Appeals

17 | P a g e

PHAs Appeals – Approve Appeals

Approve Appeals function can be accessed based on the privileges.

Approve Appeals function was developed to allow the user to update the ‘Final Decision and Comments ‘section of the form.

Once the PHAS Appeals Approve button from the Main Menu is selected the data from PHAS Appeals in datasheet format will pop up. The user can view and select the appeal that has to be approved by double clicking on the record selectors shown in Figure 17. There is no screen format difference between PIR1 and PIR2 only the content displayed differs.

Figure 17 – Approve PHAs Appeals Selection screen

Once the user double clicks the selected record, the form shown Figure 18 below will pop up allowing the user to either update Final decision and Comments section or to edit the record.

Figure 18 - Approve PHAs Appeals

18 | P a g e

PHAs Appeals – Appeals View Only

Using the Appeals View Only function from the Navigation screen the user can view the appeals for PIR1 or PIR2 depending on Main Menu selection as shown in Figure 19 below.

Figure 19 – PHAs Appeals View Only

The user can Search, Email and Print Appeals.

Search Appeals can be done by selecting the search field than by clicking the Binoculars.

Figure 20 – PHAs Appeals View Only - Search

19 | P a g e

Print Appeals can be done by clicking Print button, right click mouse button and select Print. Using Print screen you can select to print all the appeals in progress or only one appeal as shown in Figure 21. Note: Page number is the same as the

Sequence number.

Figure 21 – PHAs Appeals View Only - Search

The user can Email ‘Appeals in Progress’ report by clicking Email “Appeals in Progress’ button. The screen shown in Figure

22 will pop up.

Figure 22 – PHAs Appeals View Only – Email ‘Appeals in Progress’ report

20 | P a g e

Late Presumptive Failure (LPF) Add / Edit

Late Presumptive Failure (LPF) Add New / Edit option allows the user to enter or edit the PHAs that will receive a Late

Presumptive Failure (LPF). The screen has Add, Edit, Cancel, Save, Print and Email functionalities.

Late Presumptive Failure (LPF) Add New / Edit option – Add new function

After the user selects LPF Add New / Edit option from the Main Menu the form presented in Figure 23 below will allow the user to add new PHA to receive an LPF. In order to save the transaction the user must click Save button.

The Cancel button will cancel the transaction.

Figure 23 - Late Presumptive Failure (LPF) Add New / Edit option – Add New

Late Presumptive Failure (LPF) Add New / Edit option – Edit function

After the user selects the Late Presumptive Failure (LPF) Add New / Edit option from the Main Menu the user can edit the

PHA to receive an LPF.

Once Edit button is clicked, the selection form will pop up allowing the user to select the PHA to be edited by choosing ‘OK

Selection’ option - Figure 24.

‘Cancel Selection’ on Selection form will allow the user to close the selection form without transferring data.

Cancel button will cancel the transaction.

21 | P a g e

Figure 24 - Late Presumptive Failure (LPF) Add New / Edit option – Edit

Late Presumptive Failure (LPF) Add New / Edit option – Edit function

After the user selects Late Presumptive Failure (LPF) Add New / Edit option from the Main Menu the user can edit the PHA to receive an LPF.

Once Edit button is clicked, the selection form will pop up allowing the user to select the PHA to be edited by choosing ‘OK

Selection’ option - Figure 25.

The ‘Cancel Selection’ on the Selection form will allow the user to close the selection form without transferring data.

The Cancel button will cancel the transaction.

Once ‘OK Selection’ option is clicked the form will be populated with the information for the selected PHA as shown in

Figure 25. After the edit is done, the user must click the ‘Save’ button to save the transaction.

Figure 25 - Late Presumptive Failure (LPF) Add New / Edit option – Edit

22 | P a g e

Late Presumptive Failure (LPF) View/Update Attachment

Selecting Late Presumptive Failure (LPF) View/Update Attachment option from the Main Menu the user can view the PHAs

LPF and view, update and remove the attachment, or delete a record - Figure 26 and Figure 26.1.

Figure 26 - Late Presumptive Failure (LPF) View/Add Attachment

Figure 26.1 - Late Presumptive Failure (LPF) View/Update/Remove Attachment

23 | P a g e

Waiver/Petition/General Response - Add New /Edit

Waivers/Petitions/General Response - Add New / Edit option allows the user based on privileges to enter ,edit and approve PHAs waiver, petition or general response request. The screen has Add, Edit, Cancel, Save and Print functionalities.

Edit option allow certain users to approve the waiver by updating ‘Decision Details and Comments’ section of the ‘PIR1

Waivers/Petition/General Response’ screen.

Waivers/Petitions/General Response - Add new function

After the user selects Waivers/Petition/General Response -Add New / Edit option from the Main Menu the form presented in Figure 27 allows the user for the selected PHA to add waiver, petition or general response by selecting Request Type.

The request can be at the PHA or project level. Request Level allows the user to select the request level (PHA or project) as shown in Figure 27.1. After entering data in order to save the transaction the user must click Save button. The Cancel button will cancel the transaction.

Figure 27 – Waivers/Petitions/General Response – Add new

Figure 27.1 – Waivers/Petitions/General Response – Add new

24 | P a g e

Waivers/Petitions/General Response - Edit function

After the user selects Waivers/Petitions/ General Response Edit option from the Main Menu the user can edit the PHA data.

Approve function was developed to allow the user to update the ‘Final Decision and Comments ‘section of the form.

Based on user privileges certain users can approve waivers, petitions and general response in ‘Decision Details and

Comments’ section of the ‘PIR1 Waivers/Petition/General Response’ screen.

Once Edit button is clicked, the selection form will pop up allowing the user to select the PHA to be edited by choosing ‘OK

Selection’ option - Figure 28.

The ‘Cancel Selection’ on Selection form will allow the user to close the selection form without transferring data.

The Cancel button will cancel the transaction.

Figure 28 – Waivers/Petitions/General Response – Edit

Once ‘OK Selection’ option is clicked the form will be populated with the information for the selected PHA as shown in

Figure 28.1. After the edit is done, the user must click the ‘Save’ button to save the transaction.

Figure 28.1 – Waivers/Petitions/General Response – Edit

25 | P a g e

Waivers/Petitions/General Response - Print function

Added or Edited record can be printed using Print function as shown in Figure 28.2.

Figure 28.2 – Waivers/Petitions/General Response – Print

26 | P a g e

Waiver/Petition/General Response – Edit Projects Edit Projects function allow the users to do the following tasks: update the attachment, change the PHA Project status, search, print and email waivers, petitions or general response reports.as shown in Figure 29.

Figure 29 – Waivers/Petitions/General Response – Edit Projects

To search for a PHA position the cursor on the field you want to search than click the binoculars. Find and replace screen will pop up. The user will type the PHA Code (in our example) than click Find Next

Figure 29.1 – Waivers/Petitions/General Response – Search

27 | P a g e

Once the user clicks Find Next the requested PHA data is transferred to the screen as shown in Figure 29.2.

Figure 29.2 – Waivers/Petitions/General Response – Search

To print click the Printer icon. Right click the mouse button and the selection appears. Click Print and Print selection screen will allow the user to choose to print all the records or only pages as shown in Figure 29.3. Note: Page number is equal with

Sequence number.

Figure 29.3 – Waivers/Petitions/General Response – Print

28 | P a g e

Waiver/Petition/General Response – View/ Update Attachments

Selecting Waiver/Petition/General Response - View/Update Attachment option from the Main Menu the user can view or delete the Waivers, Petition, General Responses, view, add, and remove the attachment, search , print and email reports -

Figure 30.

Figure 30 – Waivers/Petitions/General Response – View/Update Attachments

29 | P a g e

Reference Tables Maintenance Allows the System Administrator to update the reference tables as shown below: Figure 31.

Figure 31 – Reference Table Menu

Below are presented the screens used for table maintenance Figure 32 - 34.

Figure 32: PIR1/PIR2 - Status List

Figure 33: PIR1/PIR2 - Status Recommendation List

Figure 34: PIR1/PIR2 – Connection Maintenance

30 | P a g e

User Maintenance User Maintenance function is available based on the user privileges. The user can add, change, and delete the users and the privileges as shown in Figure 35.

Figure 35: User Maintenance

Once the user click Add the screen from Figure 36 will pop up. By default a new user is active and can access Reports.

Figure 36: User Entry/Update - Add

31 | P a g e

Change function allows the System Administrator to inactivate the user or to give more privileges as shown in Figure 37.

Figure 37: User Entry/Update - Change

32 | P a g e

Reports Reports menu allow the users to print a variety of reports as shown in Figure 38.

Figure 38: PIR1/PIR2 – Reports