61944 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 

in this specification. Additional 

capabilities beyond those stated here are 

acceptable, provided that the minimum 

requirements are satisfied. 

4.2.1. A form is defined as: (a) 1–40 

characters describing the form, (b) 

Delivery address (i.e., e-mail or other 

network identifier), (c) Form number as 

defined by NMFS to uniquely identify 

the form, (d) Form version number 

(numeric with one decimal place; i.e., 

1.2), and (e) a collection of 1–30 fields 

and associated logic rules. 

4.2.2. Each field (within a form) is 

defined by the following elements. 

Except where noted, all elements of the 

field definition are mandatory: (a) Label 

(0 to 40 characters, alpha numeric), (b) 

Context Help Text (0 to 200 characters, 

alpha numeric), (c)Type (Either; 

enumeration, numeric, alpha, 

alphanumeric or Boolean), (d) Default 

Value, (e) Optional/Mandatory/Hidden/ 

Logic indicator, (f) Min/Max values (for 

numeric fields only) in range 0.000 to 

999,999, (g) Decimal places (for numeric 

fields only) 0–3, and (h) Min/Max 

characters (for alpha/alphanumeric 

fields only). 

4.2.3. Up to 100 code/value/help text 

pairs (enumerations only) must be 

provided, where codes are defined as 1–

20 alphanumeric characters, values are 

1–80 alphanumeric characters and help 

text is 0–200 characters. Such fields are 

typically used to permit a user to select 

from a range of options (i.e., geographic 

areas, gear types, fish species). Codes 

are used to compress the form data for 

efficient transmission. Help text would 

typically be displayed only when the 

user selects a specific value from the 

enumeration. 

4.2.4. Form Validation: Each field 

must be defined as; Optional, 

Mandatory or Logic Driven. Mandatory 

fields must be entered by the user before 

the form is complete, optional fields 

that do not require data entry, and logic 

driven fields have their attributes 

determined by earlier form selections. 

Specifically; it must be possible for 

selection of an enumeration to change 

the optional/mandatory setting, min/ 

max values, or the permitted 

enumeration values on a later field 

within the same form. 

4.2.5. State Information: The 

capability to populate a form based on 

the last values used must be available. 

This provides the user with an easy 

mechanism to ’modify’ or ’update’ a 

prior submission - without unnecessary 

re-entry of data. The user must be able 

to review a minimum of 20 past form 

submissions and ascertain for each form 

when the form was transmitted and 

whether delivery was successfully 

completed to the vendor’s processing 

center. In the case of a transmission 

failure, the user must be provided with 

details of the cause and have the 

opportunity to retry the form 

submission. 

4.2.6. Inclusion of VMS Position 

Report: In addition to the manually 

entered fields, the forms package must 

permit the inclusion of VMS position 

report fields such as latitude, longitude, 

date and time. Such fields must be 

obtained from the GPS function of the 

MTU and transmitted along with the 

manually entered form data within the 

same transaction. 

4.2.7. Delivery Format for Form Data: 

It is preferred that form data be 

transferred from the terminal to NMFS 

using the same transport as for either 

text messages or VMS position reports 

(the selected option to be at the election 

of the E-MTU vendor). Currently 

supported protocols for transfer are; 

FTP, SMTP, XML and HTTP Post. The 

field coding within the data must follow 

either CSV or XML formatting rules. For 

CSV format the form must contain an 

identifier and the version number, and 

then the fields in the order defined on 

the form. In the CSV format strings that 

may contain ’’,’’ (comma) characters 

must be quoted. XML representations 

must use the field label to define the 

XML element that contains each field 

value. 

Section 5. Customer Service 

The MTU supplier or its designated 

entities shall provide customer service 

that is professional, courteous, and 

responsive. It should provide MTU 

diagnostic and troubleshooting support 

to OLE and the fishermen. No services 

shall be billed to any NOAA or OLE 

office without being specifically 

contracted for in writing by an 

authorized entity. Services shall 

include: 

5.1. Service level, warranty, and 

maintenance agreements. Clarify 

constraints, if any, on the geographic 

territory, personnel availability, and 

escalation procedures for problem 

resolution covered by such services. 

5.2. Facilities and procedures in place 

to assist the fisherman in maintaining 

and repairing their MTU, including 

response and general system turn 

around time. 

5.3. Help in the determination and 

isolation of the cause of 

communications anomalies. 

5.4. Assist in the resolution of 

communications anomalies that are 

traced to the MTU. 

5.5. All services will be considered to 

be free of charge unless specifically 

listed in service or purchase agreements. 

Section 6. Other Information 

6.1. The MTU must have the 

durability and reliability necessary to 

provide acceptable service in a marine 

environment where the unit may be 

subjected to saltwater (spray) in smaller 

vessels, and in larger vessels where the 

unit may be maintained in a 

wheelhouse. The unit, cabling and 

antenna must be resistant to moisture 

and shock associate with the marine 

environments. 

6.2. The MTU must comply with any 

additional requirements specified in the 

regulations for the VMS implementation 

for which application is made. The 

requestor must review the applicable 

NMFS rules requiring the use of VMS 

and respond here to any specific 

requirements listed therein. 

6.3. All personally identifying 

information provided by vessels owners 

or other authorized personnel for the 

purchase or activation of MTU or EMTU, or for the participation in any 

NMFS VMS-approved fishery must be 

protected from unauthorized disclosure. 

Personally identifying information 

includes, but is not limited to, names, 

addresses, telephone numbers, social 

security account numbers, credit card 

numbers, vessel names, federal, state, 

and local documentation numbers, email addresses, and crew lists. Any 

information sent electronically to the 

OLE must be transmitted by a secure 

means that prevents interception, 

spoofing, or viewing by unauthorized 

individuals. Any release of such 

information must be requested and 

approved in writing by the vessel owner 

or authorized personnel, or the OLE. 

Inadvertent or intentional unauthorized 

release of personally identifying 

information will be grounds for 

reconsideration and possible revocation 

of the type approval for any MTU or EMTU supplied by the offending 

provider. 

Dated: October 24, 2005. 

William T. Hogarth, 

Assistant Administrator for Fisheries, 

National Marine Fisheries Service. 

[FR Doc. 05–21486 Filed 10–26–05; 8:45 am] 

BILLING CODE 3510–22–S 

ELECTION ASSISTANCE COMMISSION 

Publication of State Plan Pursuant to 

the Help America Vote Act 

AGENCY: Election Assistance 

Commission (EAC). 

ACTION: Notice. 

SUMMARY: Pursuant to sections 

254(a)(11)(A) and 255(b) of the Help 

Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61945 

America Vote Act (HAVA), Public Law 

107–252, the U.S. Election Assistance 

Commission (EAC) hereby causes to be 

published in the Federal Register 

material changes to the HAVA State 

plan previously submitted by Delaware. 

DATES: This notice is effective upon 

publication in the Federal Register. 

FOR FURTHER INFORMATION CONTACT: 

Bryan Whitener, Telephone 202–566–

3100 or 1–866–747–1471 (toll-free). 

Submit Comments: Any comments 

regarding the plan published herewith 

should be made in writing to the chief 

election official of the individual State 

at the address listed below. 

SUPPLEMENTARY INFORMATION: On March 

24, 2004, the U.S. Election Assistance 

Commission published in the Federal 

Register the original HAVA State plans 

filed by the fifty States, the District of 

Columbia and the Territories of 

American Samoa, Guam, Puerto Rico, 

and the U.S. Virgin Islands. 69 FR 

14002. HAVA anticipated that States, 

Territories and the District of Columbia 

would change or update their plans 

from time to time pursuant to HAVA 

section 254(a)(11) through (13). HAVA 

sections 254(a)(11)(A) and 255 require 

EAC to publish such updates. 

The submission from Delaware 

addresses material changes in the 

administration of the previously 

submitted State plan and, in accordance 

with HAVA section 254(a)(12), provides 

information on how the State succeeded 

in carrying out the previous State plan. 

The current submission from Delaware 

addresses a material change to the 

budget of the previously submitted State 

plan to address how the State will 

utilize the fiscal year 2004 requirements 

payments made in accordance with 

HAVA section 251. 

Upon the expiration of thirty days 

from October 27, 2005, Delaware will be 

eligible to implement the material 

changes addressed in the plan that is 

published herein, in accordance with 

HAVA section 254(a)(11)(C). At that 

time, in accordance with HAVA section 

253(d), Delaware may file a statement of 

certification to obtain a fiscal year 2004 

requirements payment. This statement 

of certification must confirm that the 

State is in compliance with all of the 

requirements referred to in HAVA 

section 253(b) and must be provided to 

the Election Assistance Commission in 

order for the State to receive a 

requirements payment under HAVA 

Title II, Subtitle D. 

EAC notes that the plan published 

herein has already met the notice and 

comment requirements of HAVA section 

256, as required by HAVA section 

254(a)(11)(B). EAC wishes to 

acknowledge the effort that went into 

revising the State plan and encourages 

further public comment, in writing, to 

the State election official listed below. 

Chief State Election Officials 

Delaware 

Mr. Frank Calio, State Election 

Commissioner, 111 S. West Street, Suite 

10, Dover, DE 19904, Phone: 302–739–

4277, Fax: 302–739–6794, e-mail: 

coe_vote@state.de.us. 

Thank you for your interest in 

improving the voting process in 

America. 

Dated: October 21, 2005. 

Gracia M. Hillman, 

Chair, Election Assistance Commission. 

BILLING CODE 6820–KF–P 

61946 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.000</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61947 


EN27OC05.001</GPH>
61948 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.002</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61949 


EN27OC05.003</GPH>
61950 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.004</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61951 


EN27OC05.005</GPH>
61952 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.006</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61953 


EN27OC05.007</GPH>
61954 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.008</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61955 


EN27OC05.009</GPH>
61956 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.010</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61957 


EN27OC05.011</GPH>
61958 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.012</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61959 


EN27OC05.013</GPH>
61960 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.014</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61961 


EN27OC05.015</GPH>
61962 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.016</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61963 


EN27OC05.017</GPH>
61964 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.018</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61965 


EN27OC05.019</GPH>
61966 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.020</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61967 


EN27OC05.021</GPH>
61968 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 


EN27OC05.022</GPH>
Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 61969 


EN27OC05.023</GPH>
61970 Federal Register / Vol. 70, No. 207 / Thursday, October 27, 2005 / Notices 

[FR Doc. 05–21421 Filed 10–26–05; 8:45 am] 

BILLING CODE 6820–KF–C 


EN27OC05.024</GPH>