Attachment_J.4.pdf

Attachment J.4

Users Manual for the web-EITS Application

The web-EITS Users Manual will provide the staff at IBB Transmitting Stations with data entry procedures to report Irregularities and provide Monthly Transmitter Hour

Statistical data at their broadcast facility.

The web-EITS application is client server application that provides the data entry users at the IBB Transmitting Stations a more user-friendly, convenient, and less labor-intensive tool for reporting Irregularities and Monthly Transmitter Hour Statistical data.

Irregularity data and reports can also be accessed using the on-line system to review outages at a transmitting station. Daily, Monthly and Annual Reports can be accessed using the on-line to gauge station performance. Outage Hours between the Irregularities entered in a month can be compared to the Monthly Transmitter Hours Statistical data entered as a measure of data entry accuracy.

All Irregularity data will be entered locally at the IBB Transmitting Station, which is the client side of the database application. All data sent from the transmitting stations will be sent to the IBB Engineering central database server located at IBB Headquarters in

Washington DC.

The daily report provides IBB Engineering Management real time access to the

Irregularity and Outage Time events that occurs at the IBB Transmitting Stations all within the web-EITS application. This improvement in data reporting efficiency is one of the primary reasons the web-EITS was developed.

Refer to TSI-401 for detailed instructions regarding entering Irregularities.

A. DATA ENTRY PROCEDURES FOR IRREGULARITY REPORTS

On the day of the irregularity or at the earliest convenience, the web-EITS staff should enter the Irregularity Data into EITS or what is now known as the web-EITS database.

A.1 INPUT CAUSE

a. Open the Internet Explorer browser and enter the following web URL:

http://152.75.92.136/eits/index.asp

b. When prompted enter your Login and Password then click on LOGIN TO EITS to proceed. The Login script is your IBB e-mail address. The Password for all users is “1” without the quotation marks. Users are supposed to change their password right after their first login. Passwords can be changed by the Local Administrator at the UTILITIES/PASSWORD menu.

http://152.75.92.136/eits/index.asp

c. Select Irregularity/Input Cause from the menu bar. Only users who have

CREATE/EDIT rights at the transmitting station can click on

IRREGULARITY/INPUT CAUSE and then enter Irregularity data.

Figure 1. The Irregularity-Input Cause Data Entry Form

d. Enter the data for the Cause, Irregularity and Substitution that are listed on the

Input Cause form shown in Figure 1. Remember, outage and down time are web-EITS MAIN FORM Irregularity----Statistics----Utilities----Reports-----------LOGOUT

Input Cause

Edit Record

Preview Report

Find Irreg

SENT IRREG

IRREG ARCHIVE

+ SUBST

+ IRREG

SAVE IRREGULARITY

--------Cause Entry Form----------

Location

Description

Cause ID 00001

Outage Time

(H:M)

Station

------------Irregularity--------------

1 – XMTR Code

Date

Outage Time

Antenna

Effect Code

0 ? (min)

??(min)

Network

Start Time (H:M)

Down Time

Broadcast Type

Stop Time

Language0 ? (min)

----------Substitution------------

Stop Time Subst Time 0 (min)

Subst Equipment ment Nature Code

1.A Start Time

Remarks automatically calculated by the system. Start and Stop times must be entered in the format of hhmmss (h=hours, m=minutes, s=seconds).

e. Then click on SAVE IRREGULARITY. If all the mandatory entries are not all listed then web-EITS will prompt you with an error message that states what remaining data needs to be added. All fields in the Cause and Irregularity sections of the data entry form are considered mandatory. If data items are not entered for the given Irregularity, then the record cannot be saved.

f. After clicking on SAVE IRREGULARITY button, the user is taken to a view where he/she can again check on the entries and have the option to either go back and edit the irregularity report (button NOT YET, EDIT DATA) or SEND it to

EO (button ALL IS OK, SEND NOW). If user abandons the entry process at this time, the report will be saved but have the status of UNSENT, in which case user can later access it through menu Irregularity -> EDIT REPORT or PREVIEW

REPORT and then send it. However, to avoid forgetting to send reports, we advise stations to send the report right after it is entered.

g. Once all data items are entered, the Irregularity Report is now saved to the SQL

Server Central database.

A.2 EDIT RECORD

1. Edit Record “Not Yet Sent”.

(a.) If in the process of creating an Irregularity the user did not SEND it to EO, user can retrieve that report for possible editing and then finally send it using menus Irregularity/Edit Record.

(b.) User can edit all fields except cause id, which will be the same one attributed to the report when it was created. After editing, user has two options represented by the two buttons. Button SAVE CHANGES MADE will incorporate changes into the database but the report is still UNSENT, that is NOT YET SENT to EOT. Button ALL IS OK, SEND NOW will finally send the report to EOT.

2. Delete Record “Not Yet Sent”.

(a.) Users can Delete a Record that is not yet sent to the database. From the

Irregularity/Edit Record menu the user views a list of UNSENT reports. The last column has a Delete button.

(b.) Click on the Delete button and the user is prompted to enter the reason why the report is being deleted. If nothing is entered the DELETE effort is canceled.

(c.) When a report is deleted it is not wiped out of the database. Records are stored in respective tables DELETED_CAUSES, DELETED_IRREGS and

DELETED_SUBST, just in case tracking is needed.

3. Edit Record “Already Sent”.

(a.) If an Irregularity that have already been Sent to the SQL Server Central database, which requires an EDIT, the Irregularity can be accessed from the database. First select Irregularity/Find Irreg from the menu bar and then enter the Cause ID number.

(b.) A summary of the Cause to be edited is listed. Select the Cause ID number in the Cause summary. The Cause is now ready to be edited. You can retrieve that irregularity by searching for it through menu Irregularity/FIND

IRREG and then entering one of the search criteria such as Cause ID number or a few other strings in the report.

(c.) Edit the Cause, then when completed select ADD CHANGES.

4. Edit Record from a list of “All Records Sent”.

(a.) If the user wants to edit an Irregularity from a list, which includes all the

Irregularities created and sent by the station to the SQL Server Central database, the Irregularity can be accessed and edited from the database list.

(b.) To view all the Irregularities sent to the SQL Server Central database by a station, select Irregularity/Sent Irreg. All of the Irregularities that have been sent to the database from the station will appear and they will be listed by

Cause ID. If an edit of any of these Irregularities is required, follow the procedure listed in A.2.3.(b.) and A.2.3.(c.) of this section.

A.3 PREVIEW REPORT

a. After the Irregularity Records have been entered to the local database, the user with CREATE/EDIT rights has a chance to review the Irregularity Report that includes all of the Irregularity Records.

b. To Preview the report that includes Irregularity Records yet to be sent to the SQL

Server database, click on Irregularity/Preview Report. A summary of all

Irregularities will be listed by Cause_ID.

c. Clicking on any of the Cause_ID’s lists the entire Irregularity Records data.

d. Once the user with CREATE/EDIT rights has had a chance to review the

Irregularity Report they will select ALL IS OK, SEND NOW.

e. This then sends the Irregularity Record to the SQL Server Central database. At anytime the Irregularity can be recalled from the central database and edited. It can also be Viewed by any user.

f. Users can also Delete a Record that is not yet sent to the database from the

Preview Report menu as well. From the Irregularity/Preview Report menu the user views a list of UNSENT reports, where the last column has a Delete button.

If the user then chooses to Delete a Record from the Preview Report selection, proceed by following the instructions listed in section A.2.2.(b.) and A.2.2.(c.) of this document.

B. DATA ENTRY PROCEDURES FOR MONTHLY TRANSMITTER HOUR

STATISTICS

On a monthly basis the web-EITS staff will enter the Monthly Transmitter Hour Statistics as listed on each of the station transmitters. In the event that the Monthly Transmitter

Hour Statistics were entered incorrectly and sent to the database an edit capability exists.

Lastly there exists an error checking routine that verifies the data entered for the Monthly

Transmitter Hour Statistics in comparison to the Irregularity data entered during the month. The error checking routing applies to the Enter and Edit of the Monthly

Transmitter Hour Statistics

B.1 ENTER MONTHLY TRANSMITTER HOURS STATISTICS

a. Select the Statistics/Enter Off/On from the web-EITS menu bar.

b. Enter the Scheduled Time, Outage Time and OFF_ONS for each of the transmitters listed for that station (STA) that are shown in Figure 2.

c. Once this monthly data is entered click on SAVE STATS. You are taken to a preview window so that you can check your entries again, and if they are right send the report to EO. You also have the option to EDIT the report.

d. The Monthly Transmitter Hour Statistics are now saved in the SQL Server database.

e. Additional Monthly performance data is then calculated by the on-line application and can be displayed by Selecting Statistics/Find Statistics.

B.2 EDIT MONTHLY TRANSMITTER HOURS STATISTICS

a. If incorrect Monthly Transmitter Hours data exists in the SQL Server Central database for a station, this data can be edited.

b. Select the Statistics/EDIT Off/On from the web-EITS menu bar.

c. Correct the Scheduled Time, Outage Time and OFF_ONS for each of the transmitters requiring edits, which are listed for that station (STA) as shown in

Figure 2.

d. When the editing of the Monthly Transmitter Hours data is complete, select

SAVE CHANGES.

e. The updated Monthly Transmitter Hour Statistics are now saved in the SQL

Server database.

B.3 ERROR CHECKING ROUTINE

a. An error checking routine that verifies the accuracy of the data entered for the

Monthly Transmitter Hour Statistics in comparison to the Irregularity data entered during the month is included.

b. The error checking routine applies to the Enter and Edit of the Monthly

Transmitter Hour Statistics.

c. When the Monthly Transmitter Hour Statistics Outage Time is entered for each of the stations transmitters the value entered in the Enter Off/On or EDIT Off/On view must be within a certain tolerance of the total Irregularity Outage Time entered during the month and calculated for each transmitter.

d. After entering the Monthly Transmitter Hour Statistics Outage Time data for a particular transmitter and the SAVE CHANGES is selected, if the value entered is greater than the predetermined tolerance, an error message will appear stating, “OUTAGE TIME FOR TRANSMITTER “STA-##” DOES NOT MATCH

PREVIOUSLY ENTERED IRREGULARITIES CLICK TRANSMITTER

NAME TO VIEW ALL ITS IRREGULARITY FOR SELECTED MONTH”.

e. Click OK. Then select the “STA-##” transmitter that is listed in the error message. This will open the “STA-##” transmitter Irregularities for the month, the Total Outage Time in a HH:MM:SS format, and the Total hours in a decimal format as shown in Figure 3.

f. Select the Back symbol from the Internet Explorer menu. Enter the Total hours

(decimal format) for the transmitters Outage Time for the month. Then select

SAVE CHANGES. The error message should not appear for that transmitter.

g. If the error message appears for another transmitter, complete the same procedure outlined in B.3.d through B.3.f.

h. If during this error checking process the Irregularity Total Outage Time is determined not to be accurate, then the Irregularity data needs to be edited as described in section A.2.3 or A.2.4.

Figure 2. The Monthly Transmitter Hours Statistics Data Entry Form

Enter Off/On

EDIT Off/On

Find Statistics

STATS ARCHIVE

Monthly Transmitter Hours Stats

Station: STA DATE: / 2005 Month

XMTR Scheduled Outage OFF_ONS

Code Time Time

STA- A

STA- B

STA- C

STA-01

STA-02

STA-03

STA-04

STA-05

SAVE STATS

Figure 3. The Station Irregularities Monthly List and Total

“STA-##” IRREGULARITIES FOR Month/Year

CAUSE_ID IRREG# DATE LANGUAGE SUBSTITUTE EQUIPMENT OUTAGE

TOTAL (1.27 hrs) 01:16:00

STA-00001 1 1/1/2006 LANGUAGE SUBSTITUTE EQUIPMENT 00:01:00

STA-00002 1 1/1/2006 LANGUAGE SUBSTITUTE EQUIPMENT 00:30:00

STA-00003 1 1/1/2006 LANGUAGE SUBSTITUTE EQUIPMENT 00:45:00