HFT Release Notes

Release 1.1, March 5, 2005

GENERAL NOTES AND QUESTIONS:

Contents: This release contains most, but not all, of the requested fixes and enhancements. See the notes below for details.

Changes in this Release:

MAIN:

"Comments to" now links to Teri Dean.
When users log in, text on the page now refers to the Hydrant Flow Test System.

Query Results:

The order of the columns on the Query Results page is now Hydrant#, Bldg#, Street, Intersection, City, Pressure Zone, Map, Test, Test Date & Time, Status, and Pipe Extension. Status is a new column that will show IN, OUT, or RFS. Note: Pipe Extension was on the current page but was not listed in the new column order so we put it last.
When more than one hydrant is found and summary is provided, its current status now shows in the summary.
Re: When you click on a hydrant # it goes nowhere.

This is not the case. It goes to hft_details.cfm in a pop-up window. That window contains content that was supplied by EBMUD, including a number of links to resources at your site. What may have happened is that an opened pop-up window was not closed. Internet Explorer will replace the contents of the pop-up when the next link is clicked, but will not bring that window to the foreground. So when you click links on the main page, it seems like nothing is happening, when in fact it is happening in a window you cannot see. We added code to the details page to force it to the forefront whenever its content is changed. This should resolve the confusion.

Next, rather than getting rid of this functionality, we added an button to edit the Hydrant data and placed it next to the button. Clicking the "e" button opens the new edit page for Hydrants.

Edit Hydrant Info:

The new button now provides regular users with a page to edit hydrant and outlet data. The new page was based on the table maintenance page with some new poplists added to support the users. The first page presents all data about the hydrant that can be edited. Near the top of that page is a link to edit the outlets for the hydrant. That page lists the outlets. The outlet number is a link to edit that outlet data. There are also links to add new outlets and delete existing outlets. The User Guide has been updated.

Flow Test Entry:

The Entry page for new flow tests now appears already expanded.
When entering new flow tests, the date and time now default to the current date and time. Note: These fields do not require slashes or colons. Acceptable formats for dates are MM/DD/YYYY, MM/DD/YY, MMDDYY, DD-MON-YYYY, YYYY-MM-DD, or DD-MON-YY. The MMDDYY requires no slashes and correctly translates the 2-digit year. For example, 020205 translates to February 2, 2005. Acceptable time formats are HH:MI or HHMI. No colon or leading zeros are required. 830 translates to 08:30, 1430 translates to 14:30 (2:30pm), and 1 translates to 00:01 (1 minute past midnight).
Monitoring Facilities have been added as another list of facility types tracked with Hydrant Tests. No additional attributes were requested to be stored with the monitoring facilities. Let us know if any data needs to be saved with the facilities.
When entering map numbers, the cursor now automatically jumps from the first map field to the second, and from the second to the hydrant number so users don’t have to hit tab or click the mouse. Note: This is not a good Web practice because different fields then behave differently. This also carries with it a drawback: The only way to do this is by measuring the length of the input after each keystroke and jumping forward when the length of the field is the desired number of characters. The drawback here is if the user tabs into a field that is already filled, the tab key fires the checking routine and the cursor jumps to the next field. To get into one of the "auto-skip" fields to change an existing value, the user will have to use the mouse to move the cursor there. Check the behavior of the cursor with this release. We can easily remove this if the side effects are undesired.
Re: "Orifice" should populate when hydrant is resolved.

Orifice is not an attribute of a hydrant, so cannot be filled automatically when the hydrant is resolved. However, the forms application defaulted the orifice to 2.5. We have added this default when new flows are entered for tests.
Field labels like "Residual" no longer break before the field causing them to appear misaligned at lower screen resolutions.
Calculations are now performed as expected (see next section).
Re: The adjacent pressure is not a factor in the calculation and is, therefore, not required.

It is a factor, but no longer stops the calculations from being performed.
Re: If hydrant number cannot be resolved and error message is provided, please don’t clear existing entries.

We haven't come up with a good way to do this. After submitting the form, the test, reservoir, pumping plant, and monitoring data would be saved, but the hydrant flow data could not be saved due to the unresolved hydrant number. The page is then displayed based on the saved data, which is why the flow does not currently reappear (it could not be saved). It would probably be possible to dynamically open a section to show the unsaved data, but the form would then be displayed with saved and unsaved data, so the unsaved data would have to be visually distinguished so users would know it had not been saved.

This could be done, but we want to advise you that it will take a lot of programming to accomplish. Do you want us to proceed with this? The form already warns users before they save if the Hydrant number does not validate.

Please let us know how you want us to proceed with this. We don't recommend doing the programming for very little payback.

In/Out of Service:

The time field is now pre-formatted with the current time. The user can enter a different time with or without a colon and it will be converted when saved.
Re: Please remove locking cap and date from here and add to page where hydrants and outlets will be updated.

This is not currently possible. The locking cap and date are attributes of the HYDNT_SERV_DATA table and therefore relate to putting a hydrant into or taking it out of service. Are these attributes in the wrong place? Are they permanent attributes of the hydrant, or can a locking cap come and go in the life cycle of a hydrant? If locking caps are temporarily installed and can later be removed, the attributes are probably in the correct place. If they are installed once and left in place for the remaining lifetime of the hydrant, they could be moved to the HYDNT_DATA table. Please provide further guidance on this issue. No action has been taken in this release because moving the attributes will be a significant programming effort.

REPORTS:

Re: Some of the reports say "Web Author: Teri Dean" – please remove that anywhere you see it.

We only found it on one report page and removed it. We left the "Comments to" link on the menu.
Re: "Hydrants Out of Service" and "Map the Outages" – it cannot find the page. Not sure if this is a programming error or if it’s not set up/installed properly.

These are links to pages in your current system and are not part of the scope of this forms conversion project. You probably have a configuration problem at your site. You should have hydsel.cfm and hft_hydrant_outage_map.cfm in the same directory as the files we delivered. They were supplied to us when we started work on this project and function correctly in our environment.

Update Measured Flows Feature:

The web now operates more like the original form. Recalculation of the PSI(20) and FD(20) fields is now attempted any time a change is made to the static, residual, pitot, or orifice fields. If the calc can be done, the FD(20) field is populated. The recalc is also tried any time you tab out of the Discharge (GPM) field, whether its value has changed or not. This is because the calculation does in fact use this value to calculate the result. The first time the field is automatically calculated, it will be one value. A second calculation will set it to a second value. The second value then remains the same no matter how many additional calculations are done, unless one of the other 4 input values changes.

The PSI(20) value is dependent on the adjacent pressure values. Until they are entered the PSI(20) field will be empty. When both have been entered, and any time they are changed, the PSI(20) field is recalculated.

At any time, the recalculations can be executed manually by clicking the Update Measured Flows button.

Here for reference is the original Oracle*Forms code showing the dependence on the adjacent pressure fields (red) and also how the Discharge (hydnt_flow_meas_qt, shown in green) is used to start the calculation and is then changed at the end:
```
calc_20psi:
    :control.meas_psi_qt :=
        HFT_FLOW20PSI_FC(:HYDNT_FLOW.hydnt_flow_meas_qt,
                        :HYDNT_FLOW.hydnt_flow_static_psi_qt,
                        :HYDNT_TEST_ADJCT_PRSR.hydnt_adjct_flow_static_psi_qt,
                        :HYDNT_TEST_ADJCT_PRSR.hydnt_adjct_flow_rsdl_psi_qt );
    :hydnt_flow.hydnt_flow_meas_psi_qt := round(:control.meas_psi_qt,0);

calc_fire_20psi:
    :control.meas_fire_psi_qt :=
        HFT_FLOW20PSI_FC(:HYDNT_FLOW.hydnt_flow_meas_qt,
                        :HYDNT_FLOW.hydnt_flow_static_psi_qt,
                        :HYDNT_FLOW.hydnt_flow_static_psi_qt,
                        :HYDNT_FLOW.hydnt_flow_rsdl_psi_qt);
    :hydnt_flow.hydnt_flow_meas_fire_psi_qt := round(:control.meas_fire_psi_qt,0);

calc_gpm:
    :hydnt_flow.hydnt_flow_meas_qt := 0;
    :control.meas_qt := 29.83 * ((power(:hydnt_flow.hydnt_flow_orif_sz_qt,2))*
        0.90*(SQRT(:hydnt_flow.hydnt_flow_pitot_psi_qt)));
    :hydnt_flow.hydnt_flow_meas_qt := round(:control.meas_qt,0);
```
The User Guide has been updated to reflect these changes.

ADMIN:

Re: FD Emails – this page is not showing all of the emails under each agency.

This is not a feature programmed by us. The link was provided by EBMUD and is retained in our releases. We can work on this if desired, but it should probably go to your internal staff.
Re: I will test the email notifications after the next release.

This is not a feature programmed by us. The link was provided by EBMUD and is retained in our releases.