<?xml version="1.0" encoding="UTF-8"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
    <VOL>73</VOL>
    <NO>188</NO>
    <DATE>Friday, September 26, 2008</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>AID</EAR>
            <PRTPAGE P="iii"/>
            <HD>Agency for International Development</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Program Policies and Proposal Guidelines (FY09), </DOC>
                    <PGS>55811</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22036</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Agriculture</EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Food and Nutrition Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Grain Inspection, Packers and Stockyards Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Army</EAR>
            <HD>Army Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Engineers Corps</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Blind</EAR>
            <HD>Blind or Severely Disabled, Committee for Purchase From  People Who Are</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Committee for Purchase From People Who Are Blind or Severely Disabled</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Centers</EAR>
            <HD>Centers for Disease Control and Prevention</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55845</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22698</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Medicaid Integrity Program; Eligible Entity and Contracting Requirements for the Medicaid Integrity Audit Program, </DOC>
                    <PGS>55765-55772</PGS>
                    <FRDOCBP T="26SER1.sgm" D="7">E8-22693</FRDOCBP>
                </DOCENT>
                <SJ>Medicare Program:</SJ>
                <SJDENT>
                    <SJDOC>Termination of Non-Random Prepayment Complex Medical Review, </SJDOC>
                    <PGS>55753-55763</PGS>
                    <FRDOCBP T="26SER1.sgm" D="10">E8-22307</FRDOCBP>
                </SJDENT>
                <SJ>Medicare Program; Revisions to the Medicare Advantage and Part D Prescription Drug Contract Determinations:</SJ>
                <SJDENT>
                    <SJDOC>Appeals, and Intermediate Sanctions Processes; Correcting Amendment, </SJDOC>
                    <PGS>55763-55765</PGS>
                    <FRDOCBP T="26SER1.sgm" D="2">E8-22592</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55845-55847</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22582</FRDOCBP>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22584</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Medicare and Medicaid Programs; Quarterly Listing of Program Issuances, </DOC>
                    <PGS>55902-56323</PGS>
                    <FRDOCBP T="26SEN2.sgm" D="421">E8-21594</FRDOCBP>
                </DOCENT>
                <SJ>Medicare Program; Medicare Appeals:</SJ>
                <SJDENT>
                    <SJDOC>Adjustment to the Amount in Controversy Threshold Amounts for Calendar Year (2009), </SJDOC>
                    <PGS>55847-55848</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22589</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Medicare Evidence Development and Coverage Advisory Committee, </SJDOC>
                    <PGS>55848-55849</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22591</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Medicare Program; Advisory Panel on Medicare Education, </SJDOC>
                    <PGS>55849-55850</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-21910</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Statement of Organization, Functions, and Delegations of Authority, </DOC>
                    <PGS>55850-55851</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22690</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Children</EAR>
            <HD>Children and Families Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>State Parent Locator Service; Safeguarding Child Support Information, </DOC>
                    <PGS>56422-56446</PGS>
                    <FRDOCBP T="26SER3.sgm" D="24">E8-22054</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Child</EAR>
            <HD>Child Support Enforcement Office</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>State Parent Locator Service; Safeguarding Child Support Information, </DOC>
                    <PGS>56422-56446</PGS>
                    <FRDOCBP T="26SER3.sgm" D="24">E8-22054</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Foreign-Trade Zones Board</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Oceanic and Atmospheric Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Technical Information Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Committee for Purchase</EAR>
            <HD>Committee for Purchase From People Who Are Blind or Severely Disabled</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Procurement List Additions and Deletions, </DOC>
                    <PGS>55812-55813</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22686</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Comptroller</EAR>
            <HD>Comptroller of the Currency</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Risk-Based Capital Guidelines; Money Market Mutual Funds, </DOC>
                    <PGS>55704-55706</PGS>
                    <FRDOCBP T="26SER1.sgm" D="2">E8-22720</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense</EAR>
            <HD>Defense Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Engineers Corps</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>National Security Personnel System, </DOC>
                    <PGS>56344-56420</PGS>
                    <FRDOCBP T="26SER2.sgm" D="76">E8-22483</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Delaware</EAR>
            <HD>Delaware River Basin Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Water Quality Regulations:</SJ>
                <SJDENT>
                    <SJDOC>Water Code and Comprehensive Plan to Classify the Lower Delaware River as Special Protection Waters, </SJDOC>
                    <PGS>55750-55751</PGS>
                    <FRDOCBP T="26SER1.sgm" D="1">E8-22637</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Drug</EAR>
            <HD>Drug Enforcement Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Applications:</SJ>
                <SJDENT>
                    <SJDOC>Manufacturer of Controlled Substances, </SJDOC>
                    <PGS>55869</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22696</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Education</EAR>
            <HD>Education Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55823-55824</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22640</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Energy Regulatory Commission</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Nuclear Security Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Record of Decision:</SJ>
                <SJDENT>
                    <SJDOC>Hanford Comprehensive Land-Use Plan, Environmental Impact Statement, </SJDOC>
                    <PGS>55824-55826</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="2">E8-22676</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Engineers</EAR>
            <HD>Engineers Corps</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>San Pedro Waterfront Project, Los Angeles County, CA, </SJDOC>
                    <PGS>55822-55823</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22641</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>EPA</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Standards of Performance for Petroleum Refineries, </DOC>
                    <PGS>55751-55752</PGS>
                    <FRDOCBP T="26SER1.sgm" D="1">E8-22692</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Draft NPDES General Permit for Offshore Seafood Processors in Alaska (Permit Number AKG524000), </DOC>
                    <PGS>55840-55842</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="2">E8-22553</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Environmental Impact Statements; Availability, </DOC>
                    <PGS>55842-55843</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22682</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Environmental Impact Statements and Regulations; Availability of EPA Comments, </DOC>
                    <PGS>55842</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22681</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Executive</EAR>
            <PRTPAGE P="iv"/>
            <HD>Executive Office of the President</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Management and Budget Office</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Family</EAR>
            <HD>Family Support Administration</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Child Support Enforcement Office</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>FAA</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Establishment of Class E Airspace:</SJ>
                <SJDENT>
                    <SJDOC>Pampa, TX, </SJDOC>
                    <PGS>55722-55723</PGS>
                    <FRDOCBP T="26SER1.sgm" D="1">E8-22719</FRDOCBP>
                </SJDENT>
                <SJ>Modification and Establishment of Restricted Areas and Other Special Use Airspace:</SJ>
                <SJDENT>
                    <SJDOC>Adirondack Airspace Complex; Fort Drum, NY, </SJDOC>
                    <PGS>55723-55726</PGS>
                    <FRDOCBP T="26SER1.sgm" D="3">E8-22646</FRDOCBP>
                </SJDENT>
                <SJ>Technical Amendments:</SJ>
                <SJDENT>
                    <SJDOC>Cape Town Treaty Implementation, </SJDOC>
                    <PGS>55722</PGS>
                    <FRDOCBP T="26SER1.sgm" D="0">E8-22586</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>Airbus Model A310 Series Airplanes and Model A300-600 Series Airplanes, </SJDOC>
                    <PGS>55781-55786</PGS>
                    <FRDOCBP T="26SEP1.sgm" D="5">E8-22632</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Vulcanair S.p.A. Model P68 Series Airplanes, </SJDOC>
                    <PGS>55786-55788</PGS>
                    <FRDOCBP T="26SEP1.sgm" D="2">E8-22338</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Proposed Establishment of Special Air Traffic Rule, in the Vicinity of Luke AFB, AZ, </DOC>
                    <PGS>55788-55794</PGS>
                    <FRDOCBP T="26SEP1.sgm" D="6">E8-22568</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Advisory Circular 120-16E, Air Carrier Maintenance Programs, </DOC>
                    <PGS>55893</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22630</FRDOCBP>
                </DOCENT>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Palm Beach International Airport, </SJDOC>
                    <PGS>55893-55894</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22631</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FCC</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Streamline Processing of Microwave Applications in the Wireless Telecommunications Services, </DOC>
                    <PGS>55775</PGS>
                    <FRDOCBP T="26SER1.sgm" D="0">E8-22721</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Transparency Provisions of Section 23 of the Natural Gas Act, </DOC>
                    <PGS>55726-55749</PGS>
                    <FRDOCBP T="26SER1.sgm" D="23">E8-22358</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Applications:</SJ>
                <SJDENT>
                    <SJDOC>Barrington Hydro LLC, </SJDOC>
                    <PGS>55833</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22619</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>City of Aspen, </SJDOC>
                    <PGS>55827</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22622</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Fourever Green Energy Co., </SJDOC>
                    <PGS>55827</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22620</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Great Lakes Hydro America, LLC, </SJDOC>
                    <PGS>55826-55827</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22624</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Osage Hydroelectric Project, </SJDOC>
                    <PGS>55827-55828</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22625</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pacific Gas and Electric Co., </SJDOC>
                    <PGS>55828-55829</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22626</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Parker Knoll Hydro, LLC, </SJDOC>
                    <PGS>55829</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22621</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pine Creek Mine LLC, </SJDOC>
                    <PGS>55833</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22618</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Symbiotics, LLC; Fall River Rural Electric Cooperative, Inc., </SJDOC>
                    <PGS>55829-55830</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22617</FRDOCBP>
                </SJDENT>
                <SJ>Authorization for Continued Project Operation:</SJ>
                <SJDENT>
                    <SJDOC>Public Utility District No.1 of Pend Oreille County, </SJDOC>
                    <PGS>55830</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22623</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Combined Notice of Filings, </DOC>
                    <PGS>55831</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22680</FRDOCBP>
                </DOCENT>
                <SJ>Draft Environmental Impact Statement:</SJ>
                <SJDENT>
                    <SJDOC>Proposed Jordan Cove Energy and Pacific Connector Gas Pipeline Project, </SJDOC>
                    <PGS>55831-55832</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22627</FRDOCBP>
                </SJDENT>
                <SJ>Filings:</SJ>
                <SJDENT>
                    <SJDOC>Black Hills/Colorado Electric Utility Company, LP, </SJDOC>
                    <PGS>55832</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22615</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>ISO New England Inc., </SJDOC>
                    <PGS>55832</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22616</FRDOCBP>
                </SJDENT>
                <SJ>Order Tolling 60-Day Period for Action to Allow for Further Consideration:</SJ>
                <SJDENT>
                    <SJDOC>Horizon Asset Management, Inc., </SJDOC>
                    <PGS>55832</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22614</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Highway</EAR>
            <HD>Federal Highway Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Final Federal Agency Actions on Proposed Highway:</SJ>
                <SJDENT>
                    <SJDOC>Illinois, </SJDOC>
                    <PGS>55894-55895</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22598</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Nevada, </SJDOC>
                    <PGS>55895-55896</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22572</FRDOCBP>
                </SJDENT>
                <SJ>Limitations on Claims for Judicial Reviews of Actions by FHWA and other Federal Agencies:</SJ>
                <SJDENT>
                    <SJDOC>Final Federal Agency Actions on Proposed Highway in Washington, </SJDOC>
                    <PGS>55896-55897</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22695</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Housing</EAR>
            <HD>Federal Housing Finance Board</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Federal Home Loan Bank Boards of Directors:</SJ>
                <SJDENT>
                    <SJDOC>Eligibility and Elections, </SJDOC>
                    <PGS>55710-55722</PGS>
                    <FRDOCBP T="26SER1.sgm" D="12">E8-22659</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR/>
            <HD>Federal Housing Financing Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Federal Home Loan Bank Boards of Directors:</SJ>
                <SJDENT>
                    <SJDOC>Eligibility and Elections, </SJDOC>
                    <PGS>55710-55722</PGS>
                    <FRDOCBP T="26SER1.sgm" D="12">E8-22659</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Risk-Based Capital Guidelines; Leverage Capital Guidelines, </DOC>
                    <PGS>55706-55708</PGS>
                    <FRDOCBP T="26SER1.sgm" D="2">E8-22702</FRDOCBP>
                </DOCENT>
                <SJ>Transactions Between Member Banks and Their Affiliates:</SJ>
                <SJDENT>
                    <SJDOC>Exemption for Certain Purchases of Asset-Backed Commercial Paper by a Member Bank from an Affiliate, </SJDOC>
                    <PGS>55708-55710</PGS>
                    <FRDOCBP T="26SER1.sgm" D="2">E8-22701</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FTC</EAR>
            <HD>Federal Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Granting of Request for Early Termination of the Waiting Period Under the Premerger Notification Rules, </DOC>
                    <PGS>55843-55844</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22567</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Transit</EAR>
            <HD>Federal Transit Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Limitation on Claims against Proposed Public Transportation Projects, </DOC>
                    <PGS>55897-55898</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22634</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Availabilities:</SJ>
                <SJDENT>
                    <SJDOC>Draft Comprehensive Conservation Plan for Red Rock Lakes National Wildlife Refuge, Lima, MT, </SJDOC>
                    <PGS>55864-55865</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22697</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Draft Guidance for Industry on End-of-Phase 2A Meetings; Availability, </DOC>
                    <PGS>55851-55852</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22669</FRDOCBP>
                </DOCENT>
                <SJ>Medical Devices:</SJ>
                <SJDENT>
                    <SJDOC>Availability of Safety and Effectiveness Summaries for Premarket Approval Applications, </SJDOC>
                    <PGS>55852-55853</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22668</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food</EAR>
            <HD>Food and Nutrition Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55811-55812</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22694</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>MISSING FOR: Foreign-Trade Zones Board</EAR>
            <HD>Foreign-Trade Zones Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Amendment to Application for Subzone Status; Foreign-Trade Zone 161, Sedgwick County, KS</SJ>
                <SJDENT>
                    <SJDOC>Hawker Beechcraft Corp. (Aircraft Manufacturing), Wichita and Salina, KS, </SJDOC>
                    <PGS>55813</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22716</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>GSA</EAR>
            <HD>General Services Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Federal Management Regulation (FMR); Motor Vehicle Management; Notice of GSA Bulletin FMR B-22, </DOC>
                    <PGS>55844-55845</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22643</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>GIPSA</EAR>
            <PRTPAGE P="v"/>
            <HD>Grain Inspection, Packers and Stockyards Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Solicitation of Nominations for Members of the Grain Inspection Advisory Committee, </DOC>
                    <PGS>55812</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22675</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Centers for Disease Control and Prevention</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Centers for Medicare &amp; Medicaid Services</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Children and Families Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Child Support Enforcement Office</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Food and Drug Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Institutes of Health</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Exemption of Certain Systems of Records Under the Privacy Act, </DOC>
                    <PGS>55772-55775</PGS>
                    <FRDOCBP T="26SER1.sgm" D="3">E8-21909</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> U.S. Customs and Border Protection</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> U.S. Immigration and Customs Enforcement</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Designation of the Sector-Specific Agency for the Critical Manufacturing Sector, etc., </DOC>
                    <PGS>55860</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22609</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <HD>Housing and Urban Development Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Federal Property Suitable as Facilities to Assist the Homeless, </DOC>
                    <PGS>56326-56342</PGS>
                    <FRDOCBP T="26SEN3.sgm" D="16">E8-22329</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Indian</EAR>
            <HD>Indian Affairs Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Liquor Control Ordinances:</SJ>
                <SJDENT>
                    <SJDOC>Jackson Band of Miwuk Indians of the Jackson Rancheria, </SJDOC>
                    <PGS>55865-55866</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22707</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Fish and Wildlife Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Indian Affairs Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Land Management Bureau</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55862-55863</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22673</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping:</SJ>
                <SJDENT>
                    <SJDOC>Folding Metal Tables and Chairs from China, </SJDOC>
                    <PGS>55813-55814</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22711</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Glycine from China, </SJDOC>
                    <PGS>55814-55816</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="2">E8-22714</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Drug Enforcement Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Justice Programs Office</P>
            </SEE>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>FBI Records Management Division National Name Check Program Section User Fees, </DOC>
                    <PGS>55794-55800</PGS>
                    <FRDOCBP T="26SEP1.sgm" D="6">E8-22710</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice</EAR>
            <HD>Justice Programs Office</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Public Safety Officer Medal of Valor Review Board, </SJDOC>
                    <PGS>55869</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22709</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Mine Safety and Health Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Occupational Safety and Health Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Veterans Employment and Training Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55870</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22628</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Butte Field Office, Montana, </SJDOC>
                    <PGS>55866-55867</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22543</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Ely Resource Management Plan,  Nevada, </SJDOC>
                    <PGS>55867-55868</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22540</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Proposed “M” Pit Mine Expansion, Montana Tunnels Mine, Jefferson County, MT, </SJDOC>
                    <PGS>55868-55869</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22535</FRDOCBP>
                </SJDENT>
                <SJ>Invitations:</SJ>
                <SJDENT>
                    <SJDOC>Coal Exploration License Application (MTM 98618), </SJDOC>
                    <PGS>55869</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22699</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Management</EAR>
            <HD>Management and Budget Office</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Guidance for Drug Free Workplace Requirements (Financial Assistance), </DOC>
                    <PGS>55776-55781</PGS>
                    <FRDOCBP T="26SEP1.sgm" D="5">E8-22717</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Mine</EAR>
            <HD>Mine Safety and Health Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Alcohol- and Drug-Free Mines; Policy, Prohibitions, Testing, Training, and Assistance, </DOC>
                    <PGS>55800-55801</PGS>
                    <FRDOCBP T="26SEP1.sgm" D="1">E8-22679</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Highway</EAR>
            <HD>National Highway Traffic Safety Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Federal Motor Vehicle Safety Standards:</SJ>
                <SJDENT>
                    <SJDOC>Low Speed Vehicles, </SJDOC>
                    <PGS>55801-55804</PGS>
                    <FRDOCBP T="26SEP1.sgm" D="3">E8-22736</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Medium Speed Vehicles, </SJDOC>
                    <PGS>55804-55810</PGS>
                    <FRDOCBP T="26SEP1.sgm" D="6">E8-22737</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NIH</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Government-Owned Inventions; Availability for Licensing, </DOC>
                    <PGS>55853-55858</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="2">E8-22608</FRDOCBP>
                    <FRDOCBP T="26SEN1.sgm" D="3">E8-22610</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Institute Of Diabetes And Digestive And Kidney Diseases, </SJDOC>
                    <PGS>55858-55859</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22604</FRDOCBP>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22605</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute of Mental Health, </SJDOC>
                    <PGS>55859</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22607</FRDOCBP>
                </SJDENT>
                <SJ>Prospective Grant of Exclusive License:</SJ>
                <SJDENT>
                    <SJDOC>Use of Benztropinamine Analogs to Treat Psychiatric and Neurological Disorders, </SJDOC>
                    <PGS>55859-55860</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22611</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National</EAR>
            <HD>National Nuclear Security Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Record of Decision:</SJ>
                <SJDENT>
                    <SJDOC>Site-Wide Environmental Impact Statement for Continued Operation of Los Alamos National Laboratory, Los Alamos, NM, </SJDOC>
                    <PGS>55833-55840</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="7">E8-22678</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NOAA</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>NOAA Community-based Restoration Program Guidelines, </DOC>
                    <PGS>55816-55822</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="6">E8-22708</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Technical</EAR>
            <HD>National Technical Information Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Technical Information Service Advisory Board, </SJDOC>
                    <PGS>55822</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22706</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Issuances of Environmental Assessments and Findings of No Significant Impact for License Amendments:</SJ>
                <SJDENT>
                    <SJDOC>College of William and Mary, Williamsburg, VA, </SJDOC>
                    <PGS>55873-55874</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22689</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Unrestricted Release of Facility for Saint Louis University, St. Louis, MO, </SJDOC>
                    <PGS>55874-55876</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="2">E8-22687</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Contention Preparation on Combined License; Calvert Cliffs 3 Nuclear Project, LLC; Unistar Nuclear Operating Services, LLC, </SJDOC>
                    <PGS>55876-55880</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="4">E8-22671</FRDOCBP>
                </SJDENT>
                <PRTPAGE P="vi"/>
                <SJ>Security and Continued Use of Cesium-137 Chloride Sources:</SJ>
                <SJDENT>
                    <SJDOC>Granting Extension of Comment Period, </SJDOC>
                    <PGS>55880-55881</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22688</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Occupational</EAR>
            <HD>Occupational Safety and Health Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55870-55873</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22664</FRDOCBP>
                    <FRDOCBP T="26SEN1.sgm" D="2">E8-22666</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Office</EAR>
            <HD>Office of Management and Budget</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Management and Budget Office</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Personnel</EAR>
            <HD>Personnel Management Office</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>National Security Personnel System, </DOC>
                    <PGS>56344-56420</PGS>
                    <FRDOCBP T="26SER2.sgm" D="76">E8-22483</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Railroad</EAR>
            <HD>Railroad Retirement Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55881-55882</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22672</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>SEC</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>Chicago Board Options Exchange, Inc., </SJDOC>
                    <PGS>55882-55883</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22656</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>New York Stock Exchange LLC, </SJDOC>
                    <PGS>55883-55887</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="2">E8-22587</FRDOCBP>
                    <FRDOCBP T="26SEN1.sgm" D="2">E8-22658</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE Arca, Inc., </SJDOC>
                    <PGS>55887-55889</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22654</FRDOCBP>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22655</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>The Options Clearing Corp., </SJDOC>
                    <PGS>55890</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22638</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Social</EAR>
            <HD>Social Security Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agreement on Social Security Between the United States and Denmark; Entry Into Force, </DOC>
                    <PGS>55890-55891</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22667</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Culturally Significant Objects Imported for Exhibition Determinations:</SJ>
                <SJDENT>
                    <SJDOC>The Getty Commodus: Roman Portraits and Modern Copies, </SJDOC>
                    <PGS>55891</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22713</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Worshiping Women — Ritual and Reality in Classical Athens, </SJDOC>
                    <PGS>55891</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22712</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>International Telecommunication Advisory Committee; Cancellation, </SJDOC>
                    <PGS>55891-55892</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22703</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface</EAR>
            <HD>Surface Transportation Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Abandonment Exemptions:</SJ>
                <SJDENT>
                    <SJDOC>BNSF Railway Co., King County, WA, </SJDOC>
                    <PGS>55899</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22677</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>BNSF Railway Co, King County, WA, </SJDOC>
                    <PGS>55898-55899</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22657</FRDOCBP>
                </SJDENT>
                <SJ>Acquisition Exemptions:</SJ>
                <SJDENT>
                    <SJDOC>Georgia Southwestern Railroad, Inc.; CSX Transportation, Inc., </SJDOC>
                    <PGS>55899-55900</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22588</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Transportation</EAR>
            <HD>Transportation Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Aviation Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Highway Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Transit Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Highway Traffic Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Surface Transportation Board</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55892-55893</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="1">E8-22633</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Comptroller of the Currency</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55900</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22647</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Customs</EAR>
            <HD>U.S. Customs and Border Protection</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Issuance of Final Determinations:</SJ>
                <SJDENT>
                    <SJDOC>Certain Mesh Dressing, </SJDOC>
                    <PGS>55860-55862</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="2">E8-22683</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Immigration</EAR>
            <HD>U.S. Immigration and Customs Enforcement</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Adjusting Program Fees and Establishing Procedures for Out-of-Cycle Review and Recertification of Schools Certified by the Student and Exchange Visitor Program, </DOC>
                    <PGS>55683-55704</PGS>
                    <FRDOCBP T="26SER1.sgm" D="21">E8-22786</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veterans</EAR>
            <HD>Veterans Employment and Training Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>55873</PGS>
                    <FRDOCBP T="26SEN1.sgm" D="0">E8-22512</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Health and Human Services Department, Centers for Medicare &amp; Medicaid Services, </DOC>
                <PGS>55902-56323</PGS>
                <FRDOCBP T="26SEN2.sgm" D="421">E8-21594</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Housing and Urban Development Department, </DOC>
                <PGS>56326-56342</PGS>
                <FRDOCBP T="26SEN3.sgm" D="16">E8-22329</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Defense Department; Personnel Management Office, </DOC>
                <PGS>56344-56420</PGS>
                <FRDOCBP T="26SER2.sgm" D="76">E8-22483</FRDOCBP>
            </DOCENT>
            <HD>Part V</HD>
            <DOCENT>
                <DOC>Family Support Administration, Child Support Enforcement Office; Health and Human Services Department, Children and Families Administration, </DOC>
                <PGS>56422-56446</PGS>
                <FRDOCBP T="26SER3.sgm" D="24">E8-22054</FRDOCBP>
            </DOCENT>
        </PTS>
        <AIDS>
            <HD SOURCE="HED">Reader Aids</HD>
            <P>Consult the Reader Aids section at the end of this issue for phone numbers, online resources, finding aids, reminders, and notice of recently enacted public laws.</P>
            <P>To subscribe to the Federal Register Table of Contents LISTSERV electronic mailing list, go to http://listserv.access.gpo.gov and select Online mailing list archives, FEDREGTOC-L, Join or leave the list (or change settings); then follow the instructions.</P>
        </AIDS>
    </CNTNTS>
    <VOL>73</VOL>
    <NO>188</NO>
    <DATE>Friday, September 26, 2008</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="55683"/>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY </AGENCY>
                <SUBAGY>U.S. Immigration and Customs Enforcement </SUBAGY>
                <CFR>8 CFR Parts 103 and 214 </CFR>
                <DEPDOC>[DHS Docket No. ICEB-2008-0004] </DEPDOC>
                <RIN>RIN 1653-AA54 </RIN>
                <SUBJECT>Adjusting Program Fees and Establishing Procedures for Out-of-Cycle Review and Recertification of Schools Certified by the Student and Exchange Visitor Program To Enroll F and/or M Nonimmigrant Students </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Immigration and Customs Enforcement, DHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This rule adjusts the Student and Exchange Visitor Program (SEVP) school certification petition fees and the application fees for nonimmigrants seeking to become academic (F visa) or vocational (M visa) students, or exchange visitors (J visa). The rule sets the following fees: $1,700 for a school certification petition and $655 for each site visit for certification; and $200 for each F or M student. This rule also sets a $180 fee for most J exchange visitors; however, the $35 fee for each J exchange visitor seeking admission as an au pair, camp counselor, or summer work/travel program participant will remain the same. All fee payments addressed in this final rule must be made in the amounts established by this rule beginning October 27, 2008. </P>
                    <P>The rule also establishes procedures for the oversight and recertification of schools attended by F and/or M students, establishes procedures for schools to submit recertification petitions, adds a provision allowing a school to voluntarily withdraw from its certification, and clarifies procedures for school operation with regard to F and M students during recertification and following a denial of recertification or a withdrawal of certification. Finally, the rule removes obsolete provisions used prior to implementation of the Student and Exchange Visitor Information System (SEVIS). </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule is effective October 27, 2008. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Louis Farrell, Director, Student and Exchange Visitor Program; U.S. Immigration and Customs Enforcement, Department of Homeland Security; Chester Arthur Building, 425 I St., NW., Suite 6034, Washington, DC 20536; telephone number (202) 305-2346. Program information can be found at 
                        <E T="03">http://www.ice.gov/sevis.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <EXTRACT>
                    <HD SOURCE="HD1">Table of Contents </HD>
                    <FP SOURCE="FP-2">I. Background </FP>
                    <FP SOURCE="FP-2">II. Public Comments on the Proposed Rule </FP>
                    <FP SOURCE="FP1-2">A. General Comments </FP>
                    <FP SOURCE="FP1-2">1. Support for the Rule </FP>
                    <FP SOURCE="FP1-2">2. Opposition to the Rule </FP>
                    <FP SOURCE="FP1-2">3. Technical Corrections to the Proposed Rule </FP>
                    <FP SOURCE="FP1-2">B. Adjustment of SEVP Fees </FP>
                    <FP SOURCE="FP1-2">1. Frequency of fee review and scale of fee increase </FP>
                    <FP SOURCE="FP1-2">2. Economies in efficiency </FP>
                    <FP SOURCE="FP1-2">3. Fee increase for F, M and J nonimmigrants </FP>
                    <FP SOURCE="FP1-2">C. Enhancements </FP>
                    <FP SOURCE="FP1-2">1. Issues/Concerns before SEVIS II </FP>
                    <FP SOURCE="FP1-2">2. SEVIS II </FP>
                    <FP SOURCE="FP1-2">3. Improved SEVIS and SEVIS II Capabilities </FP>
                    <FP SOURCE="FP1-2">4. SEVIS II and Biometrics </FP>
                    <FP SOURCE="FP1-2">5. Additional CEU personnel </FP>
                    <FP SOURCE="FP1-2">6. School liaison activity </FP>
                    <FP SOURCE="FP1-2">D. Full Cost Information </FP>
                    <FP SOURCE="FP1-2">1. Further reduced fee of $35 for au pairs, camp counselors, and summer work travel </FP>
                    <FP SOURCE="FP1-2">2. Impacts on applicant groups </FP>
                    <FP SOURCE="FP1-2">3. Certification fee </FP>
                    <FP SOURCE="FP1-2">4. Site-visit fee </FP>
                    <FP SOURCE="FP1-2">5. Inclusion of enforcement costs </FP>
                    <FP SOURCE="FP1-2">E. Certification, Out-of-Cycle Review, and Recertification Requirements </FP>
                    <FP SOURCE="FP1-2">1. Form I-17 </FP>
                    <FP SOURCE="FP1-2">2. Notices and communications </FP>
                    <FP SOURCE="FP1-2">3. Recordkeeping, retention, and reporting requirements—Student Record Requirements </FP>
                    <FP SOURCE="FP1-2">4. SEVIS data integrity </FP>
                    <FP SOURCE="FP1-2">5. Certification </FP>
                    <FP SOURCE="FP1-2">6. Recertification </FP>
                    <FP SOURCE="FP1-2">7. Out-of-cycle review </FP>
                    <FP SOURCE="FP1-2">8. Designated school officials </FP>
                    <FP SOURCE="FP1-2">9. Denial or withdrawal of SEVP certification or recertification procedures </FP>
                    <FP SOURCE="FP1-2">10. Regulatory Flexibility Act </FP>
                    <FP SOURCE="FP-2">III. Statutory and Regulatory Requirements </FP>
                    <FP SOURCE="FP1-2">A. Regulatory Flexibility Act </FP>
                    <FP SOURCE="FP1-2">B. Unfunded Mandates Reform Act </FP>
                    <FP SOURCE="FP1-2">C. Small Business Regulatory Enforcement Fairness Act of 1996 </FP>
                    <FP SOURCE="FP1-2">D. Executive Order 12866: Regulatory Review </FP>
                    <FP SOURCE="FP1-2">E. Executive Order 13132: Federalism </FP>
                    <FP SOURCE="FP1-2">F. Executive Order 12988: Civil Justice Reform </FP>
                    <FP SOURCE="FP1-2">G. Paperwork Reduction Act </FP>
                </EXTRACT>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                </LSTSUB>
                <HD SOURCE="HD1">PART 103—POWERS AND DUTIES; AVAILABILITY OF RECORDS PART 214—NONIMMIGRANT CLASSES </HD>
                <HD SOURCE="HD1">Table of Abbreviations and Acronyms </HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">ADIS Arrival and Departure Information System </FP>
                    <FP SOURCE="FP-1">CBP U.S. Customs and Border Protection </FP>
                    <FP SOURCE="FP-1">CCD Consular Consolidated Database </FP>
                    <FP SOURCE="FP-1">CEU Compliance Enforcement Unit </FP>
                    <FP SOURCE="FP-1">CFO Chief Financial Officer </FP>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations </FP>
                    <FP SOURCE="FP-1">CLAIMS Computer Linked Application Information Management System </FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security </FP>
                    <FP SOURCE="FP-1">DMV Department of motor vehicles </FP>
                    <FP SOURCE="FP-1">DoS Department of State </FP>
                    <FP SOURCE="FP-1">DSO Designated school official </FP>
                    <FP SOURCE="FP-1">EBSVERA Enhanced Border Security and Visa Entry Reform Act of 2002, Public Law 107-173; May 14, 2002 </FP>
                    <FP SOURCE="FP-1">FASAB Federal Accounting Standards Advisory Board </FP>
                    <FP SOURCE="FP-1">FDMS Federal Docket Management System </FP>
                    <FP SOURCE="FP-1">FIN Functional identification number </FP>
                    <FP SOURCE="FP-1">FR Federal Register </FP>
                    <FP SOURCE="FP-1">FTTTF Foreign Terrorist Task Tracking Force </FP>
                    <FP SOURCE="FP-1">HSPD-2 Homeland Security Presidential Directive—2 </FP>
                    <FP SOURCE="FP-1">IBIS Interagency Border Inspection System </FP>
                    <FP SOURCE="FP-1">ICE U.S. Immigration and Customs Enforcement </FP>
                    <FP SOURCE="FP-1">IEFA Immigration Examinations Fee Account </FP>
                    <FP SOURCE="FP-1">IIRIRA Illegal Immigration Reform and Immigrant Responsibility Act of 1996 </FP>
                    <FP SOURCE="FP-1">INA Immigration and Nationality Act of 1952 </FP>
                    <FP SOURCE="FP-1">INS Immigration and Naturalization Service </FP>
                    <FP SOURCE="FP-1">IRFA Initial Regulatory Flexibility Analysis </FP>
                    <FP SOURCE="FP-1">NAFSA Association of International Educators </FP>
                    <FP SOURCE="FP-1">NAICS North American Industry Classification System </FP>
                    <FP SOURCE="FP-1">NIV Nonimmigrant Visa </FP>
                    <FP SOURCE="FP-1">NOIW Notice of Intent to Withdraw </FP>
                    <FP SOURCE="FP-1">NPRM Notice of Proposed Rulemaking </FP>
                    <FP SOURCE="FP-1">NSEERS National Security Entry Exit Registration System </FP>
                    <FP SOURCE="FP-1">OMB Office of Management and Budget </FP>
                    <FP SOURCE="FP-1">OPT Optional practical training </FP>
                    <FP SOURCE="FP-1">PDSO Principal designated school official </FP>
                    <FP SOURCE="FP-1">PIA Privacy Information Assessment </FP>
                    <FP SOURCE="FP-1">RFA Regulatory Flexibility Act </FP>
                    <FP SOURCE="FP-1">RO Responsible officer </FP>
                    <FP SOURCE="FP-1">
                        RTI Real-time interface 
                        <PRTPAGE P="55684"/>
                    </FP>
                    <FP SOURCE="FP-1">SAVE Systematic Alien Verification for Entitlements </FP>
                    <FP SOURCE="FP-1">SBA Small Business Administration </FP>
                    <FP SOURCE="FP-1">SCB School Certification Branch </FP>
                    <FP SOURCE="FP-1">SEVIS Student and Exchange Visitor Information System </FP>
                    <FP SOURCE="FP-1">SEVP Student and Exchange Visitor Program </FP>
                    <FP SOURCE="FP-1">SFFAS FASAB Statement of Federal Financial Accounting Standard No. 4: Managerial Cost Accounting Concepts and Standards for the Federal Government </FP>
                    <FP SOURCE="FP-1">UAM User Application Model </FP>
                    <FP SOURCE="FP-1">UMRA Unfunded Mandates Reform Act of 1995 </FP>
                    <FP SOURCE="FP-1">USA PATRIOT Act Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism Act of 2001 </FP>
                    <FP SOURCE="FP-1">USCIS U.S. Citizenship and Immigration Services </FP>
                    <FP SOURCE="FP-1">US-VISIT United States Visitor and Immigrant Status Indicator Technology </FP>
                    <FP SOURCE="FP-1">VIS Verification Information System </FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Background </HD>
                <P>On April 21, 2008, the Department of Homeland Security (DHS), through U.S. Immigration and Customs Enforcement (ICE), Student and Exchange Visitor Program (SEVP), published a notice of proposed rulemaking (NPRM) to amend the fees charged by SEVP and to establish a school certification program. 73 FR 21260. This final rule implements those changes and other legal requirements by amending DHS regulations governing certification, oversight and recertification of schools by SEVP for attendance by F and/or M students. The rule establishes procedures for schools to submit recertification petitions, adds a provision allowing a school to voluntarily withdraw from its existing certification, clarifies procedures for school operations with regard to F and M visa students during recertification and following a withdrawal of certification, and removes obsolete provisions used prior to implementation of the Student and Exchange Visitor Information System (SEVIS). SEVP administers SEVIS as a Web-enabled database that provides current information on F, M and J nonimmigrants in the United States.</P>
                <P>The rule also adjusts the SEVP school certification fee and student application fees (Form I-901 SEVIS fee) to reflect existing program operating costs, program requirements, and planned program enhancements. These fee adjustments are driven by two factors: (1) The need to comply with statutory and regulatory requirements that SEVP review its fee structure every two years to ensure that the cost of the services that are provided are fully captured by fees assessed on those receiving the services; and (2) the need to enhance SEVP capability to meet current program requirements and to achieve its mission goals in support of homeland security and countering immigration fraud. </P>
                <P>
                    Once promulgated, the rule will allow SEVP to fully fund activities and institute critical near-term program and system enhancements in a manner that fairly allocates cost among the F, M and J visa categories, and acknowledges defined performance goals. These enhancements include implementation of the next generation SEVIS (
                    <E T="03">i.e.</E>
                    , SEVIS II), increased enforcement capability, expansion of school liaison activity, and establishment of a school recertification process. 
                </P>
                <P>SEVP makes these changes under a series of statutory authorities, including, but not limited to the following immigration and homeland security laws: sections 101(a)(15)(F)(i), 101(a)(15)(M)(i) and 101(a)(15)(J) of the Immigration and Nationality Act of 1952 (INA), as amended; section 641 of the Illegal Immigration Reform and Immigrant Responsibility Act of 1996 (IIRIRA), Public Law 104-208, Div. C, 110 Stat. 3009-546 (September 30, 1996); the Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism Act of 2001, Public Law 107-56, 115 Stat. 272 (October 26, 2001; USA PATRIOT Act); and the Enhanced Border Security and Visa Entry Reform Act of 2002 (EBSVERA), Public Law 107-173, 116 Stat. 543 (May 14, 2002), codified at 8 U.S.C. 1762. These laws govern the admission of foreign nationals into the United States in nonimmigrant status to attend academic, language and vocational schools, and to participate in foreign exchange visitor programs. They require that DHS collect certain information about F and M students and J exchange visitors at ports of entry. They also establish certification and recertification requirements for schools seeking approval for school attendance by F and/or M students. </P>
                <P>
                    DHS's authority to assess fees arises under IIRIRA sections 641(e)(1), 641(e)(4)(A) and 641(g)(2), as amended. In addition, section 286(m) of the INA permits the Secretary of Homeland Security to collect fees at a level that ensures recovery of the full costs of providing adjudication services, including the costs of providing similar services without charge to asylum applicants and certain other immigrants. All fees collected by ICE pursuant to this final rule are deposited as offsetting receipts into the Immigration Examinations Fee Account (IEFA) and remain available to the Secretary until expended for the purposes of the program. IIRIRA section 641(e)(4)(B). The fee assessments and collections implemented under this final rule are consistent with Office of Management and Budget (OMB) Circular A-25, User Charges (revised). 
                    <E T="03">See</E>
                     58 FR 38142 (July 15, 1993). Section 6 of OMB Circular A-25 defines “full cost” to include all direct and indirect cost to any part of the federal government for providing a good, resource, or service. The fees implemented under this final rule also are consistent with OMB Circular A-11, Preparation, Submission and Execution of the Budget, section 31.12 (July 2, 2007), which directs agencies to develop user charge estimates based on the full cost recovery policy set forth in OMB Circular A-25. 
                </P>
                <P>Further, this rule complies with the Federal Accounting Standards Advisory Board (FASAB) Statement of Federal Financial Accounting Standards (SFFAS) No 4: Managerial Cost Accounting Concepts and Standards for the Federal Government (July 31, 1995), which provides federal government standards regarding managerial cost accounting and full cost recovery. The Chief Financial Officers Act of 1990 (CFO Act), 31 U.S.C. 901-903, requires each agency's Chief Financial Officer (CFO) to “review, on a biennial basis, the fees, royalties, rents and other charges imposed by the agency for services and things of value it provides, and make recommendations on revising those charges to reflect cost incurred by it in providing those services and things of value.” 31 U.S.C. 902(a)(8). This final rule is consistent with these federal sector financial and accounting laws, rules and standards, and reflects fee collection recommendations made by the CFO. As such, the rule increases funding that supports current SEVP operations; provides funding for new initiatives critical to improving the program; funds operations to comply with statutory requirements to implement school recertification; and reflects the implementation of specific cost allocation methods to segment program costs to the appropriate fee, either F and M students, J exchange visitors, or schools, to ensure compliance with the federal sector legal framework for fee setting. </P>
                <P>
                    This final rule amends the SEVP school certification petition fees and the application fees for nonimmigrants seeking to become academic (F visa) or vocational (M visa) students, or exchange visitors (J visa). The rule also implements mandatory review of fees collected by SEVP. It sets the fee for submitting a school certification petition at $1,700 and the fee for each 
                    <PRTPAGE P="55685"/>
                    site visit at $655. It sets the fee for each F or M student at $200. The rule sets the fee for certain J exchange visitors at $180 and maintains the fee for exchange visitors seeking admission as au pairs, camp counselors, and summer work/travel program participants at $35. All fee payments addressed in this final rule must be made in the amounts established by this rule beginning October 27, 2008. 
                </P>
                <P>The rule also establishes procedures for oversight and recertification of schools with F and/or M students. This includes procedures for schools to submit recertification petitions as well as procedures to allow a school to voluntarily withdraw from an existing certification. The rule further clarifies procedures for school operation with regard to F and M students during recertification and following a denial of recertification or a withdrawal of certification. Finally, the rule removes obsolete provisions used prior to implementation of SEVIS. </P>
                <HD SOURCE="HD1">II. Public Comments on the Proposed Rule </HD>
                <P>
                    The 60-day comment period for this rulemaking action concluded on June 20, 2008; although SEVP allowed posting of late-filed comments through June 27, 2008. The proposed rule identified several alternative means for submitting comments. SEVP converted all comments submitted, regardless of means chosen for submission, to electronic format where they may be viewed electronically through the Federal Docket Management System (FDMS) at 
                    <E T="03">http://www.regulations.gov</E>
                     (use DHS docket number ICEB-2008-0004 when searching). SEVP received 61 written comments to FDMS. 
                </P>
                <P>
                    In addition, in the weeks following the publication of the proposed rule, the SEVP Director and key staff, led in several instances by the Assistant Secretary for U.S. Immigration and Customs Enforcement, launched a nationwide tour of educational institutions to engage the public in a “town hall” format to encourage open dialogue, public comments and understanding about the proposed rule. SEVP opened the forums to the public at large, and specifically invited officials from every SEVP-certified school and exchange visitor program sponsors from a listing provided to SEVP by the Department of State (DoS). SEVP posted the transcripts of those forums on the public docket for this rulemaking at 
                    <E T="03">www.regulations.gov.</E>
                </P>
                <P>
                    SEVP further extended outreach to the public through the home page of the SEVP Web site, 
                    <E T="03">http://www.ice.gov/sevis.</E>
                     The site included related press releases, “frequently asked questions” (FAQs), links to documents and access to FDMS for comment submission. Although not an official method of comment submission, SEVP received some rule-related input through its policy guidance “help” e-mail address, 
                    <E T="03">SEVIS.Source@dhs.gov.</E>
                     In these instances, SEVP asked submitters to comply with docket submission criteria, but also added all substantive issues related to the proposed rule raised in those e-mails to the FDMS docket. 
                </P>
                <P>This final rule considered all comments received during the comment period and has responded to those comments in this final rule. Below is a summary of changes to the final rule text made in response to public comment: </P>
                <P>1. The proposed text for 8 CFR 103.7(b)(1) related to the Form I-290B has been removed. </P>
                <P>2. The proposed text for 8 CFR 103.7(b)(1) related to the Form I-901 has been amended slightly to clarify fees for J visa holders by listing the J-visa categories first and then the fees, and by specifically listing the government sponsored program visa categories exempt from these fees. </P>
                <P>
                    3. The proposed text for 8 CFR 214.3(g)(1) 
                    <E T="03">Student Records</E>
                     is amended by adding after the first sentence the following text: “Student information not required for entry in SEVIS may be kept in the school's student system of records, but must be accessible to DSOs.” 
                </P>
                <P>4. The proposed text for 8 CFR 214.3(g)(1)(ii) is amended by adding a parenthetical clarification regarding the recordation of legal name changes as follows: “Identification of the student, to include name while in attendance (record any legal name change), date and place of birth, country of citizenship, school's student identification number.” </P>
                <P>5. The proposed text for 8 CFR 214.3(g)(1)(xi), requiring schools to maintain record of nonimmigrant students' “date of last entry into the United States; most recent Form I-94 number and date of issue,” has been deleted. </P>
                <P>
                    6. The proposed text for 8 CFR 214.3(g)(2)(iii)(D) 
                    <E T="03">Adjustment to the program completion date</E>
                     is amended by adding examples in parenthesis to read: “Any factors that influence the student's progress toward program completion (
                    <E T="03">e.g.</E>
                    , deferred attendance, authorized drop below, program extension) must be reflected by making an adjustment updating the program completion date.” 
                </P>
                <P>
                    7. The proposed text for 8 CFR 214.3(h)(2) 
                    <E T="03">Recertification</E>
                     is amended by adding after the first sentence, “There is no recertification petition fee.” 
                </P>
                <P>8. The proposed text for 8 CFR 214.4(a)(1) is amended to add the sentence, “No fee is required with appeals related to SEVP certification.” </P>
                <P>
                    9. The proposed text for 8 CFR 214.4(a)(2)(xix) is amended to include only those changes that represent a “material change to the scope of the institution offerings” as follows: “Failure of a DSO to notify SEVP of material changes, such as changes to the school's name, address, or curricular changes that represent material change to the scope of institution offerings (
                    <E T="03">e.g.</E>
                    , addition of a program, class or course for which the school is issuing Forms I-20, but which does not have Form I-17 approval), as required by 8 CFR 214.3(f)(1).” 
                </P>
                <P>10. The proposed text of 8 CFR 214.4(h) is amended by adding the last sentence, “No fee is required with appeals related to denial of SEVP recertification or withdrawal of SEVP certification.” </P>
                <P>11. The proposed text of 8 CFR 214.13 is expanded to include paragraph (b)(1). This allows a slight technical correction—the addition of the G-7 category. </P>
                <HD SOURCE="HD2">A. General Comments </HD>
                <P>Comments submitted to the docket for this rulemaking were distributed relatively evenly among various issues, with concerns about the potential impact of the increased I-901 SEVIS fee on student and exchange visitor participation in F, M and J programs and questions about adjustments to student reporting requirements receiving the greatest number of comments. </P>
                <HD SOURCE="HD3">1. Support for the Rule </HD>
                <P>
                    Some comments affirmed the purpose and scope of the rule, acknowledging the need to remove DHS authorization to enroll F and/or M students from noncompliant schools, and supporting increased interaction and communication among federal agencies through the development of SEVIS II and expanded SEVP liaison activity. One commenter, in particular, applauded U.S. government policy related to assessing fees for the cost of government programs and opined that all costs associated with international students' presence in the United States should be paid by students rather than by U.S. taxpayers. SEVP agrees with and appreciates these expressions of support for the program and, in this final rule, seeks to fulfill its legal requirements to fully capture the costs associated with carrying out government responsibilities 
                    <PRTPAGE P="55686"/>
                    under the SEVP program through appropriate fee assessments. 
                </P>
                <HD SOURCE="HD3">2. Opposition to the Rule </HD>
                <P>A number of comments were not relevant to the substance of the proposed rule; in particular those questioning the government's basis for establishing and continuing SEVP overall and criticizing the rule for not addressing or solving immigration issues in general. One comment, in particular, questions the logic of focusing U.S. government attention and public resources on foreign students and researchers as opposed to other immigrant and nonimmigrant groups. </P>
                <P>Other comments noted recent increases in fees for nonimmigrants by the Department of State (DoS) for visa processing and by U.S. Citizenship and Immigration Services (USCIS) for benefit applications, and asked if the fees could be better coordinated and phased-in. These comments suggested changes in substantive federal laws, USCIS regulations and processes for implementing the immigration laws by USCIS, U.S. Customs and Border Protection (CBP) and other agencies. </P>
                <P>Several comments criticized the Department's law enforcement programs for lack of collection of adequate law enforcement data related to criminal behavior. One comment, in particular, asked that SEVP further illuminate the scale of the problems that this regulation purports to address and provide additional information as to how many uninvestigated leads related to nonimmigrant student and exchange visitor activities resulted in criminal conduct, how many institutions are complying with SEVP requirements, and what percentage of foreign students are represented by these institutions. </P>
                <P>Finally, an advocacy group, endorsed by four commenters, questioned the efficacy of U.S. international education policy and its intersection with national immigration policy; concluding that SEVIS is an example of government regulation “for extraneous purposes,” developed in the absence of comprehensive U.S. international education policy. </P>
                <P>All of these comments are beyond the scope of this rulemaking. The final rule does not address comments seeking changes in statutes, regulations, policy or processes unrelated to or not addressed by the proposed rule. It also does not respond to requests for changes in procedures of other DHS components or other agencies, or the resolution of any other issues not within the scope of the rulemaking. </P>
                <P>Several individual commenters observed that the language in the preamble to the proposed rule regarding terrorist threats to the United States overstated the actual terrorist threat of a relatively small segment of the total population that visits the United States. They believe that such language has been a deterrent to foreign nonimmigrant participation with schools and exchange visitor programs. Some commenters, including two advocacy groups, feel that the “message” that foreign nationals will perceive from the rule will be that the United States is “unwelcoming.” </P>
                <P>SEVP strongly supports international education. Most non-immigrant students have positive experiences while in the United States, and the goodwill engendered by all that the United States has to offer will encourage mutually beneficial international relations. SEVP, by ensuring students' legitimacy, both reduces potential terrorist threats and decreases the risk of discrimination in the larger community, contributing to a safe environment for students and exchange visitors when they attend programs in the United States. </P>
                <P>
                    As discussed in the proposed rule, and in sources such as 
                    <E T="03">The 9/11 Commission Report</E>
                    , a strong immigration policy, including the ability of the U.S. government to know whether nonimmigrant visitors have overstayed the term of their admission to the United States, is critical to safeguarding the homeland. 
                    <E T="03">See</E>
                     72 FR at 21266. The National Commission on Terrorist Attacks upon the United States (the 9/11 Commission), in its seminal report, noted: 
                </P>
                <EXTRACT>
                    <P>
                        Looking back, we can see that the routine operations of our immigration laws—that is, aspects of those laws not specifically aimed at protecting against terrorism—inevitably shaped al Qaeda planning and opportunities * * * had the immigration system set a higher bar for determining whether individuals are who or what they claim to be—and ensur[ed] routine consequences for violations—it could potentially have excluded, removed, or come into further contact with several hijackers who did not appear to meet the terms for admitting short-term visitors. 
                        <SU>1</SU>
                        <FTREF/>
                    </P>
                </EXTRACT>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The 9/11 Commission Report: Final Report of the National Commission on Terrorist Attacks upon the United States (2004) (9/11 Commission Report).
                    </P>
                </FTNT>
                <FP>SEVP strives to administer SEVIS and the information collection and reporting requirements mandated by statute for F and M students and J exchange visitors in a manner that best serves the requirements of the law, supports the missions of DHS and the Department of State, and facilitates the ability of foreign students and exchange visitors to come to the United States. The fees implemented under this final rule will support SEVP's efforts in continuing to improve all of these purposes. </FP>
                <HD SOURCE="HD3">3. Technical Corrections to the Proposed Rule </HD>
                <P>
                    SEVP identified three required technical corrections to the proposed rule. SEVP discovered that Table 1: 
                    <E T="03">Summary of Requirements by Organization and Program Category</E>
                    , in the section addressing Program Expenses, the expenses for SEVIS II for 2009 and reflecting the change of $25,100 are in error (carried over from a previous calculation). The entry of $25,100 is corrected to $25,600. The correct entry was used for determining the totals of the Program Expenses section, so the totals remain unchanged. 
                </P>
                <P>
                    Also, SEVP discovered that Table 12: FY 2009 
                    <E T="03">SEVP Program Fees</E>
                    , line 4, in the proposed rule preamble, contained a typographical error by stating “190” for the I-901 SEVIS fee for most J-1 exchange visitors. The proposed rule included and discussed the correct “180” figure at several points in the document, including the proposed rule text, and no commenter expressed confusion over this proposed dollar amount. 
                </P>
                <P>The proposed text of 8 CFR 214.13 did not include the G-7 visa category, as required by law. SEVP expanded the final rule text to include paragraph (b)(1), which corrects this oversight by adding the G-7 category. This inclusion does not substantially change the intent of the proposed rule but reflects a well-established and nondiscretionary legal requirement. </P>
                <HD SOURCE="HD2">B. Adjustment of SEVP Fees </HD>
                <HD SOURCE="HD3">1. Frequency of Fee Review and Scale of Fee Increase </HD>
                <P>An individual commenter asked how frequently the SEVP community should expect future fee adjustments. In the same vein, an advocacy group commented that the rule asserts DHS authority to revisit the fee every two years, describing this authority and the possible frequency of fee review as “drastic and sweeping.” Another comment suggested that a more business-like approach, sensitive to consumers, would have been to raise fees incrementally. </P>
                <P>
                    As stated in the NPRM, this is the first adjustment of fees based upon actual operational costs to the program implemented by SEVP since 2002. Due to the lapse in time and significant increase in operating costs for the program, SEVP had to propose, and now implement, a substantial fee increase to cover the actual operating costs of the 
                    <PRTPAGE P="55687"/>
                    program. ICE is required by law and Executive Order to review these fees on a biennial basis. 31 U.S.C. 902(a)(8). SEVP will continue to review its fees every two years and make future fee adjustments, as necessary, at more regular intervals consistent with the biennial review and in line with the commenters' suggestions. 
                </P>
                <HD SOURCE="HD3">2. Economies in Efficiency </HD>
                <P>Two individuals commented, without providing specific examples, that efficiencies in SEVP and DHS operations, as well as at DoS, could eliminate the need for fee increases. Similarly, one commenter observed that the Departments have not yet delivered promised efficiencies and should do so before raising fees. </P>
                <P>SEVP is unable to respond to these comments because they are vague and fail to identify a means of achieving the supposed efficiencies. They also do not identify the Departments' alleged promised efficiencies. SEVP endorses streamlining and promoting efficiencies in its operations. This is one reason for creating the SEVIS II system, which will provide for more efficient processing and sharing of student data. SEVP disagrees that there remain significant unrecognized efficiencies attainable under the current program with the current fee levels. As described in the proposed rule, these adjusted fees are based on expanding program operating needs; including a need for the SEVIS II system and additional enforcement and liaison personnel to address the existing and expanding SEVP caseload. They are based on legal requirements, including the recertification program required by EBSVERA (8 U.S.C. 1762) and Homeland Security Presidential Directive-2 (HSPD-2) and are not susceptible to overall reduction or elimination by the program through leveraging additional efficiencies. </P>
                <HD SOURCE="HD3">3. Fee Increase for F, M, and J Nonimmigrants </HD>
                <P>The largest volume of comments on the proposed rule voiced concern that the increase in the I-901 SEVIS fee would adversely affect U.S. competitiveness in the international market for foreign student enrollment and exchange visitor participation. Some commenters expanded this concern to emphasize the importance of foreign student enrollment and exchange visitor participation to the U.S. culture and economy. These comments, including a comment from a major advocacy group, suggested that SEVP seek alternative public funding sources. Some of the comments in this area asked if SEVP could decrease the burden on students by having the student fee paid incrementally, part before and part after visa issuance, to minimize the loss to those that do not receive visas. </P>
                <P>
                    SEVP fully appreciates the importance of foreign student and exchange visitor enrollment to the U.S. culture and economy, and is firmly committed to lawful visitation of foreign nationals for this purpose. This is reflected in recent enrollment data, which indicate that enrollment of F, M and J nonimmigrants at higher education institutions is at a historic high and does not indicate any demonstrable variance in overall U.S. market share in relation to other countries.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">http://opendoors.iienetwork.org/page/113974.</E>
                    </P>
                </FTNT>
                <P>SEVP also observes that the comments neither cited to nor provided a published study or other data supporting the suggestion that an increase in government fees charged to international students adversely affects their decision to choose the United States for academic or vocational study, or exchange visits. SEVP, likewise, has been unable to locate such a study. The program thus has no objective basis for concluding that international students choose or reject attending education institutions in the United States based on government fees which, generally, are a very small portion of the overall costs of attending these programs. </P>
                <P>
                    Rather, SEVP research reveals that the fees currently required for all incoming F-1 students equates to similar fees charged in other countries.
                    <SU>3</SU>
                    <FTREF/>
                     An analysis of twelve countries (Australia, Canada, China, France, Germany, India, Japan, Russia, South Africa, Saudi Arabia, South Korea, and the United Kingdom) shows that the average student visa fee is $126.58. The composite U.S. cost, after the effective date of this rule, will be $330, which includes a visa processing fee of $130 and the $200 I-901 SEVIS fee. This fee is neither the most expensive nor the least expensive when compared with these twelve countries. In fact, Australia, cited by most commenters as the singular competitor of U.S. market share, currently charges nonimmigrant students a total of $450. The table below lists the fees charged by the twelve countries researched in the SEVP analysis. 
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         SEVP has placed these research materials in the FDMS docket for this rulemaking.
                    </P>
                </FTNT>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s60,xs30">
                    <TTITLE>Student Fees in Other Countries</TTITLE>
                    <BOXHD>
                        <CHED H="1">Country </CHED>
                        <CHED H="1">Costs </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Australia </ENT>
                        <ENT>$450.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Canada </ENT>
                        <ENT>125.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">China </ENT>
                        <ENT>205.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">France </ENT>
                        <ENT>78.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Germany </ENT>
                        <ENT>95.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">India </ENT>
                        <ENT>161.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Japan </ENT>
                        <ENT>Free </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Russia </ENT>
                        <ENT>$131.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Saudi Arabia </ENT>
                        <ENT>Free </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">South Africa </ENT>
                        <ENT>37.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">South Korea </ENT>
                        <ENT>45.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            United Kingdom 
                            <SU>4</SU>
                        </ENT>
                        <ENT>192.00 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    There
                    <FTREF/>
                     is also no objective evidence that this fee is the sole, or even the most important, criterion that a student might consider while weighing educational options. The increased I-901 SEVIS fee represents less than 1% of the average cost of yearly expenses for students in a four-year program, an amount that could easily be overshadowed by changes in international currency fluctuations or changes in school tuition amounts in foreign countries. 
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         On January 30, 2008, the Home Office of the United Kingdom (UK), the UK equivalent to DHS, announced a new SEVP-like program for students and exchange visitors that will likely include additional fees. 
                        <E T="03">See http://www.ukba.homeoffice.gov/managing borders/managing immigration/a points-based system.</E>
                    </P>
                </FTNT>
                <P>Perhaps more importantly, the United States features types of education, such as community colleges and focused vocational educational programs of study that are unique in the world. The United States offers courses of study, specializations in content, and programs that cannot be found anywhere else. Noted research facilities, the majority of which continue to be dominated by American entities, provide opportunities for advanced research and collaboration among an increasingly international community of scholars. Given the many variables that go into a decision to study abroad, and the lack of validated data on this issue, there is no basis to conclude that United States government fees ultimately persuade a student or exchange visitor not to attend a school in this country. SEVP, consequently, cannot conclude at this time that an increase in the I-901 SEVIS fee is directly or even indirectly related to a decrease in U.S. competitiveness for international students and exchange visitors. </P>
                <P>
                    But even if a rise in the cost to F and M students and J exchange visitors were to cause a reduction in the demand by foreign students or exchange visitors for U.S. educational or exchange opportunities, that point would not alter this rulemaking. Current law requires 
                    <PRTPAGE P="55688"/>
                    that DHS and DoS recoup the full costs of administering the programs that manage F, M and J nonimmigrants from those who benefit from it. DHS may not reduce its fees based on a desire to attract a greater number of aliens to the program. 
                </P>
                <P>With respect to the suggestion of some commenters that students pay SEVP fees incrementally, SEVP cannot implement such a payment system at this time due to the additional administrative burden and development costs such an incremental payment system would place on the program, but will continue to study the idea. </P>
                <HD SOURCE="HD2">C. Enhancements </HD>
                <HD SOURCE="HD3">1. Issues/Concerns Before SEVIS II </HD>
                <P>One commenter observed that DHS, including SEVP, tends to institute new requirements for schools and students before either data systems or program policy have been sufficiently developed to support them and that, subsequently, an inordinate amount of effort is expended on “work-around” procedures and data fixes. The observer sought assurance that SEVP will have a concrete plan to avoid premature deployment of SEVIS II and to augment policy and helpdesk staffing to support anticipated need for problem resolution. Another comment asked how SEVIS users will transition from SEVIS I to SEVIS II and how new functionalities in SEVIS II will be introduced. </P>
                <P>SEVP is committed to providing the planning and support necessary to make SEVIS II implementation a success. SEVP has already started to engage with its stakeholders and expects to continue to engage in a major outreach initiative for the SEVIS II rollout, including but not limited to, meetings, brochures, e-newsletters, and Web site postings. </P>
                <P>A commenter suggested that, with SEVIS II a year and a half from activation, it would be very helpful if SEVP would establish a Web-based ability for students to self-report. SEVP acknowledges the value of such an innovation and will take the consideration under advisement. </P>
                <P>A commenter requested that schools be given the ability in SEVIS to print-out draft Forms I-17 for review prior to submission. It is not likely such an enhancement will be made to SEVIS I, but SEVP will maintain the request as a suggested system requirement for SEVIS II. </P>
                <P>A commenter reported instances of erroneous data appearing in the CBP port of entry data systems when compared with SEVIS information on the applicable J-1 exchange visitors that was verified to be correct. This comment is outside the scope of this rule. </P>
                <P>A commenter noted instances when students' visa and passport numbers were identical in SEVIS. Data fixes were requested but were not completed. SEVP appreciates comments regarding its systems and will note and investigate to determine whether a data fix can be made to resolve such a problem. </P>
                <P>A commenter noted degraded responsiveness in SEVIS during peak times during the recent optional practical training (OPT) validation. SEVP acknowledges that response time can be adversely affected by circumstances beyond its control. </P>
                <HD SOURCE="HD3">2. SEVIS II </HD>
                <P>Commenters included SEVP stakeholders who had participated in SEVIS II development meetings held by SEVP in Washington D.C. last summer, at which they identified several requested system requirements for SEVIS II. They commended SEVP on the inclusion of all user communities in SEVIS II development. </P>
                <P>Two commenters questioned whether SEVIS II becoming “paperless,” as proposed, is a realistic expectation and whether this paperless process is a move away from faxing. SEVIS II is certainly a move away from faxing. SEVP anticipates that, with improved access to data systems, and with the incorporation of electronic signature capability and availability of biometric information coming in the near future, U.S. government processes related to F, M and J nonimmigrants will become paperless. For example, in SEVIS II the DSO will electronically sign the equivalent to the Form I-20, Certificate of Eligibility for Nonimmigrant Student Status. SEVIS II will be paperless in implementing its processes but will also have the ability to generate paper forms. As needs are identified by State and local governments and the private sector, SEVP will consider modifying the format and content of paper Forms I-20 to better serve their processes. </P>
                <P>
                    Another commenter asked how SEVIS II paperless processes will interact with the requirements of the Real ID Act of 2005. We understand that students and exchange visitors are likely to need paper documentation of their F, M or J status in the United States to obtain driver's licenses, establish bank accounts and other similar activities. As discussed above, SEVIS II will allow for the generation of paper forms as needed by students and exchange visitors. As the States move forward developing their processes for verifying documents presented by individuals seeking REAL ID-compliant driver's licenses or identification cards as required under the REAL ID Act 
                    <SU>5</SU>
                    <FTREF/>
                     and DHS REAL ID regulations, DHS will work with the States to ensure that DMVs are able to verify the immigration status of foreign students and exchange visitors through DHS's Systematic Alien Verification for Entitlements program (SAVE).
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Pub. L. 109-13, 119 Stat. 231, 302 (May 11, 2005) (codified at 49 U.S.C. 30301 note), also 73 FR 5271 (Jan. 29, 2008), codified at 6 CFR part 37. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The SAVE Program allows Federal, State and local government benefit-granting agencies, as well as licensing bureaus, to check the immigration status of non-citizens and citizen applicants requesting benefits or entitlements. 
                    </P>
                </FTNT>
                <P>A commenter asked how a Form I-20 generated out of SEVIS II for identification purposes will meet State DMV and/or Social Security Administration (SSA) requirements that necessitate the form having a port of entry stamp. This comment points to a training problem and not a SEVIS II data system concern. While some port of entry officials stamp Forms I-20 as a courtesy, there is no requirement for them to do so. A related misconception is the expectation that Forms I-94, Arrival/Departure Record, will be stamped. Forms I-94 should be stamped when their issuance is related to entry into the United States. Forms I-94 issued in conjunction with approval of a benefit are not stamped. SEVP continues to conduct outreach among government agencies to correct areas of misinformation like these that negatively impact nonimmigrants. </P>
                <P>Two commenters asked if Form I-290, Notice of Appeal or Motion, and USCIS Form I-134, Affidavit of Support Information, were being incorporated in the transition to paperless processes. </P>
                <P>The Form I-290 will be entirely paperless. SEVP, with USCIS, is in the process of deciding whether the Form I-134 will be included in the paperless process. </P>
                <P>A commenter asked if the elimination of paper Forms I-20 will extend to border commuter students. The answer is yes, the elimination of paper Forms I-20 will extend to border commuter students. </P>
                <HD SOURCE="HD3">3. Improved SEVIS and SEVIS II Capabilities </HD>
                <P>
                    A few commenters asked about SEVP's efforts to improve SEVIS interface and interoperability with other government databases, in general. SEVP recognizes that the value of SEVIS to the United States, its citizens and the nonimmigrants it tracks is multiplied by increasing appropriate access to all potential, legitimate users. Since the inception of SEVP, the program has entered into agreements and developed 
                    <PRTPAGE P="55689"/>
                    interfaces with several governmental agencies. SEVIS currently interfaces with: Foreign Terrorist Task Tracking Force (FTTTF), U.S. Bank I-901, United States Visitor and Immigrant Status Indicator Technology (US-VISIT), CBP Arrival &amp; Departure Information System (ADIS), USCIS Computer Linked Application Information Management System (CLAIMS), DoS Nonimmigrant Visa, and DoS Consular Consolidated Database (CCD). SEVP, through the U.S. Immigration and Customs Enforcement (ICE) Office of the Chief Information Officer, is currently brokering agreements for SEVIS II to interface with: 
                    <E T="03">Pay.gov</E>
                    —I-17, ICE—Business Compliance Enforcement—National Security Entry Exit Registration System (NSEERS), CBP Interagency Border Inspection System (IBIS), User Application Module (UAM)—single sign-on, Non-Immigrant Visa Interface (NIV) and the USCIS Verification Information System (VIS). The developing interface between SEVIS and VIS, the database of the SAVE program, will be a significant benefit. This interface alone will significantly relieve problem areas for nonimmigrants interacting with SSA and the State DMVs, or seeking authorized employment. 
                </P>
                <P>Two commenters asked if SEVIS II would ameliorate tracking problems USCIS seems to have in keeping up with student benefit petitions. </P>
                <P>SEVP has an active partnership with USCIS and both agencies are strongly committed to developing the best possible interface between their tracking systems, SEVIS and CLAIMS. SEVP acknowledges room for improvement, but significant progress has been made. </P>
                <P>A commenter observed that a lot of unnecessary enforcement actions are occurring because DHS and other government data systems do not adequately share information and interfaces do not always send the intended data. As discussed above, SEVP is fully aware of the importance of effective interfacing and places a high priority on improving and increasing interfaces with SEVIS II. The fees implemented by this final rule will, in part, be used to address these interfacing issues. In recognition of the current situation, SEVP has a staff member that serves as a full-time liaison with the ICE Compliance Enforcement Unit (CEU). When data anomalies are identified or there are indications that a student may have violated status, this individual is the first responder. Through search of the relevant data systems and telephone consultations with school officials, most of these concerns are resolved through a desk audit, requiring no further action. CEU investigators are assigned to follow up with that small number of situations that the liaison is unable to explain. Of these, greater than 70% result in finding substantive issues that warrant investigation. Again, SEVP will use a portion of the fees collected from this final rule to improve this system. </P>
                <P>Commenters asked about their capability to extract information from SEVIS II, especially to support the Open Door census. </P>
                <P>Enhancing the ability of SEVIS users to extract and use information from SEVIS was one of the biggest reasons SEVP sought SEVIS II, and will be a key purpose for which SEVP uses fees assessed by this rule. The new system will provide users additional history information on individuals and will vastly improve reporting and search functionality. </P>
                <P>Several commenters asked about the impact of SEVIS II on J exchange visitor programs. An advocacy group suggested that J program interests have not been met in SEVIS development. </P>
                <P>SEVP does not concur. Officials from DoS have had an active role in SEVIS development. Since the inception of SEVIS through SEVIS release 5.10, released in August 2008, 99 system upgrades (approximately one third of all system upgrades in that period) have been directed towards meeting exchange visitor program needs. Of these, twenty-five percent of the upgrades dealt directly with refining the redesignation process. Regarding SEVIS II, of the more than 1,300 functional requirements that were developed from stakeholder input, including input from the DoS and exchange visitor program sponsors, approximately 416 are exclusively for use by the exchange visitor community. Among the remaining system requirements, approximately fifty percent are shared commonly by the F, M and J visa categories. Academic representatives from the exchange visitor program sponsors were involved from the beginning of SEVIS II development and some of these individuals made particular note of the significant improvements they had observed and of the high level of interagency cooperation. As is reflected in the transcripts on the docket for this rulemaking, senior leadership and staff from DoS participated both during the development meetings that collected SEVIS II requirements and during the recent town hall meetings. While the specific needs of F, M and J schools and programs may differ, it has been a priority for SEVIS program developers to ensure that new capabilities are available to all SEVIS users. This rule, and the fees collected pursuant to the rule, will enhance the exchange visitor programs as well as F and M programs. </P>
                <P>One commenter cited the significant cost to his school in modifying data systems to interface and support batch-feeding of data to SEVIS. He raised concern that SEVIS II would pass a similar, uncompensated cost on to schools and exchange visitor program sponsors. </P>
                <P>SEVIS II is being designed to be fully compatible with SEVIS I and consistent with industry standards. All data currently in SEVIS will be migrated by SEVP into SEVIS II. Further, while changes in data requirements are a natural part of program evolution, there are very few added fields beyond those already in SEVIS. (Adding new fields, historically, has been the biggest recurring problem with batch interfaces.) As discussed in the proposed rule, SEVIS II enhancements are a key part of these fee increases, which are calculated to include conversion costs. Consequently, SEVP anticipates that any added costs to SEVIS users for conversion to SEVIS II will be negligible. </P>
                <P>A commenter voiced concern that schools which rely on the feeding of data to SEVIS by batch do not have the flexibility that real-time interface (RTI) reliant schools have in responding to SEVP changes. The commenter noted that batch users must often use RTI procedures to be able to meet SEVP requirements. The commenter asked that SEVP be mindful of this in initiating changes. </P>
                <P>SEVP will do so. Batch providers were invited to attend SEVIS II development workshops, at which they voiced concerns and provided insights into the amelioration of these concerns. </P>
                <HD SOURCE="HD3">4. SEVIS II and Biometrics </HD>
                <P>Commenters asked about SEVIS II's use of biometrics. </P>
                <P>
                    SEVIS II, scheduled for deployment in October 2009, will include a data field to record a biometric identifier (
                    <E T="03">i.e.</E>
                    , functional identification number: FIN) for nonimmigrant records. SEVIS II will, however, have no functions related to the acquisition or storage of biometric information. SEVP will have access to biometric information, as needed, and will incorporate the use of biometrics in its tracking processes. The costs related to these processes are included in the fees assessed by the rule. 
                </P>
                <P>Commenters also asked for a description of how a biometric identifier will impact recordkeeping processes and management. </P>
                <P>
                    The biometric identifier will be “person-centric,” meaning that it will 
                    <PRTPAGE P="55690"/>
                    remain with the person for life whenever they seek entry into the United States or seek immigration related benefits. The SEVIS identifier is a record of a particular period of time that an individual has been in F, M or J status. The biometric identifier will tie all SEVIS identifiers to an individual. This will enable government, school officials or exchange visitor program sponsors to see all pertinent information on a nonimmigrant in deciding whether or not to grant benefits or accept that individual for enrollment. For example, if a student is terminated at one school and chooses to seek reinstatement “by travel,” the CBP inspector will see the previous termination and assess the situation in more depth than for a normal “initial” student arriving for entry into the United States. A biometric identification will streamline all government systems. Currently these systems identify individuals through consistencies in personal identification information (
                    <E T="03">e.g.</E>
                    , name, birth date, address). These fields are subject to mistakes, such as entry errors and variations in spelling, and are often difficult to match from one system to another. By having access to the common biometric identifier, government users can bypass less reliable search fields and can readily identify and correct data mistakes. As discussed in the proposed rule, funding these types of enhancements are part of the purpose of these increased fee assessments. 
                </P>
                <P>A commenter asked if the biometric identifier and its ability to connect an individual's SEVIS records will have any impact on the payment of the I-901 SEVIS fee when a student decides to reinstate by travel. </P>
                <P>The answer is no. If a student is out of status and seeks to return to status by leaving the United States and re-entering, he or she must pay the I-901 SEVIS fee. </P>
                <HD SOURCE="HD3">5. Additional CEU personnel </HD>
                <P>A commenter questioned the legal authority of using the I-901 SEVIS fee to support hiring of enforcement officers, suggesting they should be funded by appropriated monies. </P>
                <P>
                    As was discussed in the proposed rule, 8 U.S.C. 1372(e)(4)(A), (g)(2), 8 U.S.C. 1372(e)(4)(B) and 8 U.S.C. 1356(m) provide the Secretary with authority to establish, revise, collect, retain and expend fees to operate SEVP. This authority provides that fees be set at a level that will ensure recovery of the full costs of providing all services for the program. The full cost concept addresses the activities associated with the continuum of providing services under the program, from accepting applications, to developing policy, to enforcement of program regulations and associated laws. Full cost includes the direct and indirect costs to any part of the federal government of providing a good, resource, or service and these costs include, but are not limited to, an appropriate share of direct and indirect personnel costs, including salaries and fringe benefits such as medical insurance and retirement; physical overhead, consulting, and other indirect costs including material and supply costs, utilities, insurance, travel, and rents or imputed rents on land, buildings, and equipment; the management and supervisory costs; and the costs of enforcement, collection, research, establishment of standards, and regulation. 
                    <E T="03">See</E>
                     OMB Circular A-25, User Charges (revised), section 6(d)(1). As such, “enforcement costs” are part of a continuum of program services and are to be considered as part of the full cost of program services chargeable as user fees. 
                </P>
                <P>In addition, SEVP currently funds only 79 CEU personnel. ICE is spending much more than 79 agent full-time hours investigating school and student issues. There are hundreds of issues and cases that arise in SEVIS and in the student and academic institution area. Those are categorized by high, medium and low risk cases. Currently, the 79 positions SEVP funds do not cover all of the cases identified as the high risk cases, much less all cases. The additional 155 positions funded by this rule are meant to close this gap. </P>
                <P>A commenter questioned whether the increased funding for CEU personnel would result in the hiring of employees with greater specialized knowledge and training, observing that some investigators seem to have very little knowledge of school and/or student requirements. </P>
                <P>SEVP does intend to use this increased funding to hire additional CEU personnel and to support specialized training for CEU personnel related to SEVP-certified schools, DoS exchange visitor sponsors and F, M and J nonimmigrants. Federal law enforcement officers receive extensive, standardized training at the Federal Law Enforcement Training Facility (FLETC) in Glynco, Georgia. SEVP continues to work with the appropriate authorities within ICE and at FLETC to provide training content for this curriculum. SEVP also intends to hire liaisons whose duties will include collateral support of CEU investigators. This should further help CEU personnel understand school and exchange visitor sponsor, as well as student and exchange visitor requirements. </P>
                <HD SOURCE="HD3">6. School liaison activity </HD>
                <P>
                    One commenter nominated a person to become an SEVP liaison. SEVP does not accept nominations for SEVP liaison positions, but urges interested individuals to monitor 
                    <E T="03">www.usajobs.opm.gov</E>
                     for vacancy announcements related to these and other SEVP positions. 
                </P>
                <P>More than one commenter noted a general lack of knowledge in both DHS and DoS about the structure of higher education, particularly the unique needs of research facilities and the critical importance of not impeding foreign scholar participation in their programs. These commenters cited examples of misunderstanding about the applicability of accreditation to research facilities seeking redesignation or recertification and at least one comment pointed to a research institute that is having difficulty becoming accredited because there are no qualified U.S. candidates for enrollment and accreditation requires that the program be previously in operation. (Redesignation by DoS requires accreditation. SEVP certification requires the program to have been previously in operation.) Hope was raised that the SEVP liaisons would overcome this knowledge shortcoming. </P>
                <P>SEVP appreciates these observations and will follow-up with the commenters. A “provisional certification” status is under consideration by SEVP but will not be implemented with this rule due to the additional cost and administrative burden related to establishing such a program. </P>
                <P>A commenter asked if SEVP liaisons would be able to assist schools and students in determining the status of benefit applications pending with USCIS. SEVP is taking this suggestion under consideration and will discuss it with USCIS representatives. </P>
                <P>An advocacy group and a concurring commenter feel the need for liaisons is created by SEVIS requirements being “cumbersome and complicated.” </P>
                <P>
                    SEVP disagrees and notes that no such comments were received in the nationwide town hall meetings. To the contrary, the introduction of liaison support was received enthusiastically. As discussed in the proposed rule, liaison activity will be much more than mere troubleshooting, but will also provide timely information regarding program enhancements, support CEU activities and offer greater feedback to SEVP on positive and negative user comments and suggestions. Simply 
                    <PRTPAGE P="55691"/>
                    making SEVIS more user friendly, which is a key goal of SEVIS II, would not eliminate the need for liaisons. 
                </P>
                <HD SOURCE="HD2">D. Full Cost Information </HD>
                <HD SOURCE="HD3">1. Further reduced fee of $35 for au pairs, camp counselors, and summer work travel </HD>
                <P>One commenter asked why the $35 fee for au pairs, camp counselors, and summer work/travel programs was not included in the funding increase. </P>
                <P>Congress established the $35 fee for au pairs, camp counselors and summer work/travel program participants by law and did not provide a similar set fee for other categories of the J-visa for exchange visitors. 8 U.S.C. 1372(e)(4)(A). This indicates a strong Congressional intent that the fee for au pairs, camp counselors and summer work/travel programs remain set at $35. Thus, SEVP did not adjust that fee. </P>
                <HD SOURCE="HD3">2. Impacts on applicant groups </HD>
                <P>
                    Several commenters voiced concern about the negative impact of the increased fee on all F, M and J nonimmigrants, but particularly on students and exchange visitors in short-term status or individuals with limited means (
                    <E T="03">e.g.</E>
                    , teachers and high school students; those from poor countries; language study). Commenters asked if SEVP could establish a lower fee for particular groups through regulation suggesting, for example, a tiered fee of $35 for exchange visitor programs currently identified and for F/M programs of study six months or less in duration; $200 fee for F/M programs more than six months; $180 for exchange visitor programs other than government sponsored. In a similar request other comments, including those from two major advocacy groups, expressed support for the SEVP initiative furthering the institution of a short-term visa category. In fact, over 250 participants at a May 28, 2008, town hall forum at the NAFSA national conference were supportive of this idea. 
                </P>
                <P>SEVP cannot establish a lower fee as requested. As discussed above and in the proposed rule in relation to OMB Circular A-25, User Charges (revised), applicable laws, regulations and directives prohibit SEVP from establishing fees below program costs. Any preference given by SEVP to a select group would result in a penalty to the participants at large. By allowing a select group the same benefit as others in the population at a fee below cost, the fee for the majority of the population must increase in order to fully cover program costs. SEVP has reviewed its program costs for processing students in short-term status versus those in long-term status and can find no basis for charging a lower fee for students on short-term status. The government would also incur additional administrative costs associated with separate processing of these fees. Accordingly, and as was discussed in the town hall meetings, SEVP is constrained at this time to charge a single set fee for each individual group. </P>
                <P>A commenter noted that most scholarships and assistance given to students of limited means is directed to costs after the student enters the United States and that, consequently, the various government fees can pose an insurmountable burden on a student since they are levied before entry and, generally, not compensated. </P>
                <P>
                    Although SEVP appreciates identification of this problem, government agencies must collect fees at the time services are provided. We welcome further input from students and schools at 
                    <E T="03">SEVIS.Source@dhs.gov</E>
                     as to how they handle this situation. 
                </P>
                <P>One commenter questioned the timing for implementation of the rule. </P>
                <P>SEVP timed implementation of the final rule for October 1, 2008, the beginning of fiscal year 2009. This is the date when the student enrollment is completed for the largest population; therefore, the fewest number of students will be involved in initiation of the new fee levels. By implementing the fee for the beginning of the government fiscal year, SEVP is able to better simplify and reduce costs related to government accounting. Further, as noted in the NPRM and this final rule, SEVP has been underfunded for many years since the program has not implemented a fee increase for several years. By implementing the fees at the start of SEVP's fiscal year, the program funding will be better aligned with its budgetary and operational needs for the full fiscal year and thus allow SEVP to better serve its constituents. </P>
                <HD SOURCE="HD3">3. Certification fee </HD>
                <P>A commenter noted that it was unclear in the proposed text for 8 CFR 214.3(h)(2) whether or not schools must submit a fee for recertification. </P>
                <P>SEVP appreciates the observation and has clarified the text accordingly, inserting final rule text at 8 CFR 214.4(a)(1) and 8 CFR 214.4(h) that expressly provides that no fee is required with appeals related to SEVP certification, recertification or withdrawal of SEVP certification. </P>
                <P>Two commenters, including a high school administrator, suggested that the increased SEVP certification fee may be a disincentive to small schools to seek certification and cited the cultural value of international students in these settings. SEVP appreciates and agrees with the observation of the cultural value of having international students in all settings. SEVP does not have the authority, however, to identify and designate specific groups of schools for a lower fee because its costs are not lower for small schools. SEVP welcomes any additional suggestions for potentially decreasing burdens on small businesses. </P>
                <HD SOURCE="HD3">4. Site-visit fee </HD>
                <P>A commenter from an SEVP-certified school observed that the $655 site visit fee would cut into its programming funds. </P>
                <P>The site-visit fee pertains only to initial SEVP certification (or initial events, such as approving a new location or campus). Should a school require an on-site review as a part of an out-of-cycle review or recertification, the expense of that visit will be borne by SEVP as part of its compliance funding. Accordingly, SEVP anticipates that the site visit fee will have minimal impact on programming funds for certified schools. </P>
                <HD SOURCE="HD3">5. Inclusion of enforcement costs </HD>
                <P>A professional association and an advocacy group comment that fee assessments should be limited to visa application costs, and that costs related to national security and anti-fraud are benefits to the public that should be borne by appropriated, taxpayer funds. Another advocacy group commented that, beyond visa application costs, SEVP legal authorities allow for data collection, but not for assessment of enforcement costs. </P>
                <P>
                    SEVP agrees in part and disagrees in part with these comments. SEVP agrees that agency fees cannot be charged based upon perceived furthering of public policy goals if those fees are unrelated to a specific service provided by the agency to an identifiable recipient. If, however, the agency does confer a specific benefit upon an identifiable beneficiary, then the fact that the service may incidentally confer a benefit upon the general public as well does not preclude assessing a user fee. 
                    <E T="03">See, e.g., Seafarers International Union of North America</E>
                     v. 
                    <E T="03">United States Coast Guard,</E>
                     81 F.3d 179, 184 (DC Cir. 1996) (interpreting Coast Guard user fees established under the Independent Offices Appropriations Act); quoting 
                    <E T="03">Engine Manufacturers Ass'n</E>
                     v. 
                    <E T="03">EPA,</E>
                     20 F.3d 1177, 1180 (DC Cir. 1994). 
                </P>
                <P>
                    The direct benefits of the SEVP program inure to F and M students and J exchange visitors. The benefit 
                    <PRTPAGE P="55692"/>
                    conferred is admission into and lawful presence in the United States, which permits F and M students, and J exchange visitors to receive academic, vocational and exchange opportunities and experiences not enjoyed by the public-at-large. SEVP enforcement activities create public confidence and consistency within the program which perpetuates and enables these visa categories for the direct benefit of F and M students, and J exchange visitors. Homeland security and anti-fraud benefits are incidental public benefits of the program. These incidental public benefits do not diminish SEVP's authority to assess fees against identifiable beneficiaries. 
                </P>
                <P>In addition, as discussed above, 8 U.S.C. 1372 and 8 U.S.C. 1356(m), authorize a full range of SEVP program activities and collection of fees related thereto, and not merely data collection. Use of the I-901 SEVIS fee to fund the activities of additional enforcement officers to perform these activities is thus authorized under 8 U.S.C. 1372(e)(4)(A), (g)(2), 8 U.S.C. 1372(e)(4)(B) and 8 U.S.C. 1356(m). Pursuant to OMB Circular A-25, User Fees (revised), Section 6(d)(1), “enforcement costs” are part of a continuum of program services that must be included as part of the full cost of program services when assessing user fees. Accordingly, inclusion of these costs within the full cost of the program is appropriate and congruent with the full cost concept as outlined in federal cost accounting guidance, federal policy for user charges and legal precedent. </P>
                <P>Another advocacy group commented that charging J visa holders for enforcement costs of DHS is redundant, since DoS has its own compliance unit, and “beyond the mandate of the rule.” </P>
                <P>SEVP does not concur. DHS is mandated by the INA to enforce immigration law for all nonimmigrants and has done so historically for all nonimmigrant populations, including the J visa category. The compliance unit at DoS reviews DoS designated sponsors for their statutory and regulatory compliance—not the immigration-related violations of exchange visitors. The law enforcement programs of DHS and DoS are separate and distinct, not redundant. </P>
                <HD SOURCE="HD2">E. Certification, Out-of-Cycle Review, and Recertification Requirements </HD>
                <HD SOURCE="HD3">1. Form I-17 </HD>
                <P>
                    A few participants in the town hall meetings had questions about submitting updates to school information. Individuals should address additional questions about submitting these updates to 
                    <E T="03">SEVIS.source@dhs.gov.</E>
                     As stated at the forums and as presented at numerous conferences over the last several months, it is important that school updates be timely. Updates to this information are the single most beneficial step most schools can take to prepare for recertification. 
                </P>
                <HD SOURCE="HD3">2. Notices and communications </HD>
                <P>Two comments, respectively, questioned whether electronic notices and communications meet due process requirements and whether schools would need to obtain software to transmit electronic signatures. </P>
                <P>Various laws, rules and regulations govern the use of electronic systems in relation to the provision of government services, and permit and encourage government agencies to use electronic notices. As such, these processes have been found to satisfy due process requirements. SEVP, as a program, and SEVIS, as a Web-based data platform, are inherently reliant on electronic communication. For this reason, notices and alerts are sent to multiple addressees, as listed on the school's Form I-17. Capability to submit electronic signatures will be a SEVIS II design feature. </P>
                <HD SOURCE="HD3">3. Recordkeeping, retention and reporting requirements—Student Record Requirements </HD>
                <P>Several commenters, including three advocacy groups, opposed the proposed text on recordkeeping, retention and reporting as establishing new and unnecessary requirements. </P>
                <P>SEVP has deleted rule text in response to these comments. Specifically, SEVP proposed a new requirement at 8 CFR 214.3(g)(1)(xi) that the DSOs enter “date of last entry into the United States; most recent Form I-94 number and date of issue,” into SEVIS, items which are normally entered through SEVIS interface with the CBP ADIS database. This interface is not yet fully reliable and many DSOs have found that inputting this arrival information, like keeping copies of Forms I-20, can be useful in helping students expedite benefit applications. Keeping this information is not required, however, and the final rule deletes proposed 8 CFR 214.3(g)(1)(xi). Other SEVIS entries in the regulatory text are not new, but have been clarified with this rule. </P>
                <P>One commenter suggested that, because SEVIS is the only tracking system of its kind, it is subject to misuse and overuse. </P>
                <P>SEVP does not concur and views the proper use of SEVIS very differently. SEVP is obligated to U.S. taxpayers to maximize the effective utilization of the data it collects. SEVP thus seeks every opportunity to share SEVIS data with appropriate, authorized users not only for law enforcement purposes, but also to facilitate validation of benefit eligibility. This sharing benefits F, M and J nonimmigrants by providing more efficient delivery of benefits from various agencies of the federal government. </P>
                <P>An individual commented that SEVP needs to make better use of the data it has in SEVIS. </P>
                <P>While the comment did not provide sufficient detail to prompt a response, SEVP concurs and is committed to developing data-driven management and compliance processes. </P>
                <P>A commenter asked whether records review procedures require hard copy. Not necessarily; records review will be of the system that is in place at the school, electronic or hard copy. </P>
                <P>
                    A commenter asked for clarification that the “unabridged academic history of the student at the institution” refers to the institution's primary student recordkeeping system, not a duplication of that system. Several commenters presumed that SEVP was proposing duplication of records. SEVP has edited the final rule text in response to these comments. The proposed text for 8 CFR 214.3(g)(1) 
                    <E T="03">Student Records</E>
                     is amended by adding, after the first sentence: “Student information not required for entry in SEVIS may be kept in the school's student system of records, but must be accessible to DSOs.” This clarification should eliminate any unintended presumption about duplication of records. 
                </P>
                <P>
                    Several commenters also questioned why DHS needed the information introduced in 8 CFR 214.3(g)(1)(iv) and thought SEVP was trying to do the job of the schools. As many commenters noted, the items introduced in 8 CFR 214.3(g)(1)(iv) are already included in the recordkeeping processes and systems of most bona fide institutions, and many institutions go well beyond these requirements. SEVP has identified these as minimums that a bona fide school should maintain in order to set a standard for compliance. The absence of effective recordkeeping is a strong indicator that an institution is not suited for SEVP certification (
                    <E T="03">i.e.</E>
                    , DSOs must be able to explain how they obtain this information, which is essential to determining that a student is maintaining status). 
                </P>
                <P>
                    A commenter noted that their school records policy did not require transcripts with as much information as required by this rule for transcripts received from a transfer-out school (
                    <E T="03">e.g.</E>
                    , 
                    <PRTPAGE P="55693"/>
                    course numbers and credits are required but grades are not). 
                </P>
                <P>SEVP responds that the institution must be able to demonstrate how it determined that the student was eligible and met its requirements for transfer to their institution. This may not be as extensive as the records required by the institution that conferred the credits. </P>
                <P>One privacy advocate voiced privacy concerns with respect to DHS access to student records. </P>
                <P>SEVP is diligent in its compliance with individual privacy protections. Examination of student records as part of an institution's audit is done solely in support of that audit. Record access is strictly limited to appropriate authorized users. SEVP policy on privacy issues is codified in the SEVP Privacy Information Assessment (PIA), available on its Web site. </P>
                <P>Several comments questioned the need for extending the student records retention requirement from one to three years. </P>
                <P>SEVP responds that this is necessary to support the two-year recertification cycle and is consistent with the current exchange visitor program standard. Most schools and many states have much more stringent records retention schedules. </P>
                <P>Similarly, a commenter asked how the extended records retention requirement will be implemented. </P>
                <P>
                    The requirement begins with implementation of this rule and is not retroactive (
                    <E T="03">i.e.</E>
                    , if a school's records were reviewed on that day, the reviewer could not require records from further back than the current requirement of one year). 
                </P>
                <P>A comment noted the need for improved entry and exit data in SEVIS and observed that the rule makes no mention of this in the recordkeeping section. </P>
                <P>SEVP strongly concurs on the importance of this information. This information is received from other DHS agencies and points to a recognized need to improve the SEVIS interface with their systems, which is a key goal of SEVIS II, as funded by this final rule. </P>
                <P>An advocacy group suggested that the rule unnecessarily broadens records access beyond SEVP to include DHS. </P>
                <P>
                    The statutes authorizing this rule and establishing DHS, including 8 U.S.C. 1372 and the Homeland Security Act of 2002, Public Law 107-296 (November 25, 2002), section 102(b), permit the Secretary of Homeland Security, in his discretion, to exercise these authorities utilizing the various DHS resources at his disposal. Moreover, blocking records access to other components of DHS would run directly counter to the lessons our Nation learned after 9/11. 
                    <E T="03">See, e.g., The 9/11 Commission Report</E>
                     at pp. 416-19. 
                </P>
                <P>An advocacy group and a commenter stated that the proposed text at 8 CFR 214.3(g)(2)(ii)(E), requiring a school to respond to a notification request by DHS, is overly broad and that the existing regulation limits such a request to SEVIS. </P>
                <P>SEVP does not concur. The replacement of “SEVIS” in this text updates the context of the existing regulation. Since the current text was approved (67 FR 76256, December 11, 2002), DHS instituted SEVP to administer SEVIS. SEVIS, being a database, can only distribute notification requests from SEVP. However, SEVP exists to support the DHS enforcement agencies in tracking F, M and J nonimmigrants. SEVP investigatory activities are limited and, as warranted, result in a hand-off to more extensive investigation by other DHS agencies, highlighting the transition from internal compliance related activities to law enforcement activities that can only be rendered by those immigration officers so authorized. The text, consistent also with 8 CFR 214.3(g)(1), facilitates cooperation between SEVP-certified schools and DHS. Notification requests from these agencies may come outside of SEVIS. Just as SEVP is limited in its information collection by law, these enforcement agencies have laws restricting their information collection. Any request for information from these agencies will be governed by the laws that apply to them respectively. </P>
                <P>An advocacy group commented that the use of the term “student,” rather than “students,” to describe reporting requirements limits DHS to requiring reports on just individuals, not groups. </P>
                <P>SEVP does not concur. As is consistent with SEVP past practice, the term “student” is expansive of individual students and/or larger populations of students depending on the nature of the reporting request. </P>
                <P>An advocacy group questions DHS and SEVP authority to conduct validation studies. </P>
                <P>SEVP does not concur. On-going validation of certified schools is inherent in the out-of-cycle and recertification processes. Validation studies are one of many administrative tools that SEVP uses to ensure that issues are identified and corrected before they become problems. SEVIS data are examined through a variety of filters to determine whether issues exist across and among schools. Only when data cannot be verified through existing information does SEVP ask schools to validate information, reducing the burden on their reporting. SEVIS II will enhance this capability for SEVP, further eliminating the burden on schools. </P>
                <P>A commenter asked for clarification of proposed text in 214.3(g)(2)(iii)(D), regarding factors impacting the adjustment of program completion dates. </P>
                <P>
                    SEVP has changed the rule text in response to this comment by adding examples in parentheses. The proposed text for 8 CFR 214.3(g)(2)(iii)(D) 
                    <E T="03">Adjustment to the program completion date</E>
                     is amended and clarified to read: “Any factors that influence the student's progress toward program completion (
                    <E T="03">e.g.</E>
                    , deferred attendance, authorized drop below, program extension) must be reflected by making an adjustment updating the program completion date.” This clarification should resolve any misunderstanding regarding factors impacting the adjustment of program completion dates. 
                </P>
                <P>A commenter suggested that CFR text giving records and information access to DHS representatives be limited to ICE representatives, since they are specifically tasked with student tracking and compliance. </P>
                <P>SEVP disagrees. While this reflects the current practice, agencies and tasking within DHS are subject to realignment at the Secretary's discretion. SEVP appreciates the suggestion, but concludes that “DHS” appropriately encompasses all possibilities and reflects the legal authorities underpinning the program and the operation of the DHS. </P>
                <HD SOURCE="HD3">4. SEVIS Data Integrity </HD>
                <P>A few commenters asked about possible future innovations enabling F, M and J nonimmigrants to access SEVIS data. </P>
                <P>SEVP appreciates the comment and will explore these possibilities. </P>
                <P>
                    Several commenters asked if, as interfaces with other data systems and SEVIS increase and become more reliable, mistakes from other systems couldn't be corrected electronically by DSOs (
                    <E T="03">e.g.</E>
                    , Form I-94 errors with CBP and SAVE errors, as they affect Social Security and DMV applications). The current priority with systems interfaces is on accurate and complete data sharing. It is reasonable to assume that upgrading data integrity along the lines of the comments will be considered and is one of the reasons for the fee increases implemented by this rule. 
                    <PRTPAGE P="55694"/>
                </P>
                <HD SOURCE="HD3">5. Certification </HD>
                <P>An advocacy group and a commenter supported the requirement of accreditation for SEVP certification. </P>
                <P>SEVP acknowledges the value of accreditation as an indicator of institution bona fides and compliance, but also has excellent experience with many non-accredited schools. For non-accredited schools, the SEVP School Certification Branch has instituted and continually refines measures of school bona fides “in lieu” of accreditation. </P>
                <P>A commenter requested amplification of the “basic competencies for DSOs” that the site visit seeks to promote. </P>
                <P>SEVP responds that unlike the majority of schools already certified in SEVIS that have extensive experience and knowledge with enrolling F and/or M nonimmigrants, schools seeking initial SEVP certification today lack a similar background. In compliance with SEVP requirements and support of these students, however, these schools must be held to the same standard as all other SEVP-certified schools. In recognition of this, SEVP views the on-site visit for initial certification as an outreach instrument, an opportunity for intensive training and familiarization. While details of this outreach are evolving, they include but are not limited to the following topics: maneuvering in SEVIS; becoming aware of pertinent regulations and where to find them; complying with recordkeeping, retention and reporting requirements; Internet resources; and contingency planning. These are potential uses for the fees generated by this rule. </P>
                <P>
                    Three comments requested that SEVP better define what a campus is and what is required of schools when a campus is added (
                    <E T="03">e.g.</E>
                    , when is a fee required). 
                </P>
                <P>SEVP agrees with the comments but does not intend to make this clarification in this rule. SEVP, in the meantime, provides individualized guidance to schools on this issue. SEVP intends to propose a rule amending 8 CFR 214.3 to be in place when recertification begins and anticipates addressing this issue in more detail in that rulemaking. </P>
                <HD SOURCE="HD3">6. Recertification </HD>
                <P>A commenter asked how SEVP will determine the order in which schools will become eligible for recertification. </P>
                <P>
                    A few factors that come into consideration in determining the order in which schools will become eligible for recertification include, but are not limited to: the amount of time since the school's previous certification; the anticipated processing time for the school (
                    <E T="03">e.g.</E>
                    , non-accredited schools take longer than accredited schools); whether the school is of special interest, either by type of school or compliance questions; and the anticipated School Certification Branch (SCB) workload. The order of processing will be chosen to create a balanced workload. 
                </P>
                <P>A commenter asked if recertification could be every five years, instead of every two years. </P>
                <P>SEVP cannot implement this proposal because two-year certification is mandated under EBSVERA and HSPD-2. With out-of-cycle review on-going and continuous from the time of initial certification forward, the frequency of recertification should be less of a concern to schools. SEVP intends that noncompliance be identified as soon as possible after its occurrence and appropriate action be taken immediately. As the proposed rule describes, recertification is an affirmation of performance, not the reopening of a school's file for the first time. </P>
                <P>An advocacy group commented that institutions should not be charged for enforcement costs related to certification and recertification. SEVP notes, as was presented in the proposed rule, fees charged to institutions for certification and certification site visits are not used for enforcement costs. As described in the NPRM, these costs are covered by other fees. </P>
                <P>
                    One comment asked about the reasoning for reviewing DSO compliance even when a DSO is no longer employed by the school. SEVP responds that an employer (
                    <E T="03">i.e.</E>
                    , school) is responsible for oversight of all of its employees and the consequences of their actions. Termination of employment, in and of itself, does not absolve the employer of that responsibility. 
                </P>
                <P>A commenter asked for more detail about text stating that institutions must have adequate qualified personnel to perform DSO responsibilities. </P>
                <P>SEVP has decided to leave this as an area of institutional discretion for the moment. Larger schools have asked if the limit of ten DSOs at a campus could be increased and/or if an associate DSO position, with no advisory role but ability to enter data, couldn't be established. SEVP is actively considering both of these recommendations. Some schools have appointed senior management, whose primary functions do not relate to providing service to students, as DSOs. SEVP discourages this practice. Smaller schools have, on occasion, appointed only one DSO. This makes full-time and continuous adequate service of foreign students nearly impossible. </P>
                <P>A commenter asked what will be the focus of recertification. </P>
                <P>Recertification will focus primarily on how well a school updates records on school information and student records. For schools that are not accredited, bona fides will need to be reconfirmed with documentation “in lieu of accreditation.” SEVP will develop and send schools guidance on the submission of petitions along with their notification that entering the six-month period of eligibility to submit a recertification petition. </P>
                <P>A commenter asked if SEVP-certified schools for public school (grades 9-12) and private school (grades kindergarten-12) in a district or system could file for recertification with a single petition. </P>
                <P>SEVP responds that, yes, these schools may file for recertification with a single petition. </P>
                <P>
                    A commenter asked if an institution with more than one SEVIS identifier (
                    <E T="03">i.e.</E>
                    , a number for the main campus and each other campus) could file for recertification with a single petition. 
                </P>
                <P>SEVP responds that, yes, this is permitted. </P>
                <P>Commenters were unclear about the distinction between on-site visits and on-site reviews. </P>
                <P>As stated during the town hall meetings, few schools would receive an on-site review during SEVP recertification. On-site review in recertification is distinguished from an on-site visit given during initial certification. The purposes of an on-site visit include confirmation of a school's eligibility for SEVP certification, promoting basic competencies for DSOs, and providing outreach to better familiarize the school with the roles and responsibilities that come with the benefit of SEVP certification. The purpose of an on-site review is, generally, to address compliance. While a few random on-site reviews may be conducted to maintain a performance baseline for all schools and to explore potential performance benchmarks, the primary reason an on-site review is conducted is to resolve questions or concerns about school performance. Optional visits to schools by SEVP personnel prior to the implementation of the liaison program will be available within SEVP resource constraints and by invitation from the school. To offset operational limitations in providing these visits, comprehensive resources on recertification will be provided on the SEVP Web site. </P>
                <P>
                    A few comments included questions on fees related to on-site visits and on-site reviews. 
                    <PRTPAGE P="55695"/>
                </P>
                <P>For initial SEVP certification petitions, a petition fee ($1,700) is required for each institution and an on-site visit fee ($655) is required for each campus. School systems (limited to public schools grades 9-12, private schools grades K-12) require a petition fee and a single on-site visit fee. SEVP-certified institutions that have a change of ownership must pay a petition fee. SEVP-certified institutions seeking approval for change of location must pay an on-site visit fee. SEVP-certified institutions seeking approval for a new campus must pay an on-site visit fee. No fee is charged of institutions either petitioning for recertification or selected to receive an on-site review. </P>
                <P>One comment asked how accreditation might be a factor in determining selection of a school for on-site review. To the extent that accreditation provides an impartial affirmation of school bona fides and performance, it is less likely that an accredited school will receive an on-site review. </P>
                <HD SOURCE="HD3">7. Out-of-Cycle Review </HD>
                <P>A few individual commenters and an advocacy group felt out-of-cycle review, as presented in the proposed rule, is too broad. </P>
                <P>SEVP disagrees. At the simplest level, out-of-cycle review is nothing more than maintaining the data integrity of SEVIS, and describes a process that exists with all data systems. Changes are reviewed for accuracy and reasonableness. Most out-of-cycle reviews constitute nothing more than a desk audit conducted from the SEVP offices. For example, a routine update changing a zip code may result in SEVP asking other schools impacted by the change to update their information. This sort of audit is not invasive; rather, it is responsible. </P>
                <P>An advocacy group commented that audits of schools for other than changes to SEVIS information identified as material should be delayed until recertification. </P>
                <P>SEVP, again, does not concur. Compliance management requires resolution of anomalies in performance when they are identified and before potential problems escalate. </P>
                <P>
                    A commenter voiced concern about unscheduled and large data requests of schools from SEVP (
                    <E T="03">e.g.,</E>
                     the validation study and OPT updating). 
                </P>
                <P>SEVP regrets the difficulties placed on schools by these requests and appreciates the patience and understanding of SEVIS users in explaining the obstacles they impose. As a maturing program, SEVP is committed to improving the administration of future requests and minimizing their frequency. SEVIS users should realize that their outstanding responsiveness on these requests is noted by key decision makers. Additionally, as SEVIS II is developed and implemented, SEVP looks forward to improved capability to validate SEVIS information through alternative means. </P>
                <P>An individual commented that out-of-cycle review is a waste of SEVP and school time for compliant schools. SEVP is required to perform these out-of-cycle reviews for due diligence. SEVP's review also allows the program to monitor changes outside of the control of SEVP or the schools (for example, the zip code change referenced above). </P>
                <P>One comment suggested that text describing the events that trigger out-of-cycle review should be qualified with “may.” </P>
                <P>SEVP does not occur with this comment. Introduction of this text into the CFR only formalizes what has been published in the SEVIS User Manual and reviewed by SEVP for years. It clarifies language currently found at 8 CFR 214.3(e)(3) and parallels the explicitness that has to date only been found in operational instructions. Specifically, it identifies that SEVP conducts a desk review of each of these changes, determines what additional information is required, requests that information and then adjudicates the petition update. This is not an elective process that could be characterized by “may,” but a prescriptive process directed by current regulation. With many of these changes, a cursory review is adequate and little or no direct follow-up with the school is needed; the out-of-cycle review has been transparent to the school. </P>
                <P>An individual commented that the time period should be extended from 10 to 30 days. </P>
                <P>SEVP does not agree. Schools are required to keep school information in SEVIS current at all times. A request for an update of this information should require nothing more than a few moments of review and submission. Because this relates to SEVP-certified schools, supporting documentation requested pertains only to changes since certification. Presuming changes are submitted to SEVP timely, authorizing documentation for the changes should be readily available. </P>
                <HD SOURCE="HD3">8. Designated School Officials </HD>
                <P>A commenter questioned whether all DSOs must be knowledgeable of regulations. </P>
                <P>
                    Yes, the individual certifies to knowledge of SEVP regulations when they sign the Form I-17 accepting appointment to become a DSO. SEVP is considering future personnel alignment (
                    <E T="03">e.g.,</E>
                     positions with limited data entry access to accommodate school administrative processes) and will likely adjust knowledge and training needs accordingly to sustain role-related SEVIS responsibilities. 
                </P>
                <P>A commenter questioned the expectation that an individual be knowledgeable of regulatory requirements and SEVIS operation when first appointed as a DSO. </P>
                <P>When first appointed as DSOs, individuals should have a basic knowledge of SEVP regulatory requirements and SEVIS operations. As a practical matter SEVP does not expect an entry level DSO to have detailed regulatory knowledge but the individual should be able to identify pertinent regulations and demonstrate where they can be found. SEVP has and is developing resources to assist new DSOs in getting up to speed as quickly as possible. PDSOs should anticipate the need for mentoring newly appointed DSOs to assist in bringing them up to an acceptable standard as quickly as possible. </P>
                <P>A commenter asked what documentation must be submitted when a new DSO is appointed and who must sign the documentation. </P>
                <P>SEVP responds that in addition to submitting the identification of newly appointed DSOs in SEVIS, the principal designated school official (PDSO) of an SEVP-certified institution must submit copies of the school's Form I-17 with the PDSO and new appointee signatures, as well as be able to provide documentation certifying that the new individual is a U.S. citizen or lawful permanent resident to SEVP. </P>
                <P>A commenter recommended establishment of an alternate PDSO position. </P>
                <P>SEVP appreciates this recommendation and is considering it as one of many recommendations in the realignment of personnel with SEVIS roles and SEVP responsibilities. </P>
                <P>A commenter asked for clarification of the need for DSOs at locations other than the main campus. </P>
                <P>
                    If students can complete a program of study solely at the alternate location, that location is a campus and must meet DSO requirements. If students receive part of their program of study at an alternate location, but must receive the remainder at another campus that meets DSO requirements, this alternate location is a satellite facility and does not require DSOs. The underlying purpose of this regulation is to ensure proper monitoring of student activity and to provide counsel to students. If a 
                    <PRTPAGE P="55696"/>
                    school is uncertain of their need for DSOs, they should contact SEVP. Note that DSOs can serve on multiple campuses, as long as the institution can assure that DSO responsibilities are being met at each campus. 
                </P>
                <HD SOURCE="HD3">9. Denial or Withdrawal of SEVP Certification or Recertification Procedures </HD>
                <P>A commenter suggested that the text citing reasons for withdrawal of SEVP certification be expanded to include a “pattern” of such behavior, not limited to a single violation. </P>
                <P>It is unclear, based on the comment, what would constitute a pattern and what threshold of violation would be permissible. SEVP believes the suggestion opens the regulation to ambiguity, and chooses to retain the proposed text. </P>
                <P>A commenter noted that, as used in the proposed rule at 8 CFR 214.4(a)(2)(xix), the term “curriculum” was too broad and did not convey the intended meaning. </P>
                <P>
                    SEVP appreciates the recommendation and has modified the text accordingly with an explanatory parenthetical. Specifically, the proposed text for 8 CFR 214.4(a)(2)(xix) is amended to read as follows: “Failure of a DSO to notify SEVP of material changes, such as changes to the school's name, address, or curricular changes that represent material change to the scope of institution offerings (
                    <E T="03">e.g.,</E>
                     addition of a program, class or course for which the school is issuing Forms I-20, but which does not have Form I-17 approval), as required by 8 CFR 214.3(f)(1).” Addition of this text clarifies the aspects of curriculum change that must be reported. 
                </P>
                <HD SOURCE="HD3">10. Regulatory Flexibility Act </HD>
                <P>An individual commented that the I-901 SEVIS fee will be a deterrent to foreign student/exchange visitor participation and, subsequently, will place a strain on small to mid-sized educational institutions. </P>
                <P>As is discussed above and in more detail in the Regulatory Flexibility Act section below, SEVP does not concur that the I-901 SEVIS fee will be a deterrent to foreign student/exchange visitor participation, nor does SEVP see a disproportionate impact on smaller schools. </P>
                <HD SOURCE="HD1">III. Statutory and Regulatory Requirements </HD>
                <HD SOURCE="HD2">A. Regulatory Flexibility Act </HD>
                <P>DHS is amending regulations governing SEVP found in 8 CFR parts 103 and 214 to adjust the school certification fee and the application fee for nonimmigrants seeking to become academic (F visa) or vocational (M visa) students, or exchange visitors (J visa). The final rule will increase the fees for submitting a SEVP school certification petition to $1,700, plus $655 for each site visit; set the fee for each F or M student at $200; set the fee for most J exchange visitors at $180; and maintains the fee for J exchange visitors seeking admission as au pairs, camp counselors, and summer work/travel program participants at $35. In addition, this final rule will establish procedures for recertification of schools with F and/or M students. The rule will become effective October 1, 2008. </P>
                <P>
                    DHS recognizes that the final rule will result in economic impacts on F, M, and J nonimmigrants, as well as programs and schools seeking to become SEVP-certified or recertified. In this section of the final rule we will focus only on the economic impact of the regulation on small entities, as defined and required by the Regulatory Flexibility Act.
                    <SU>7</SU>
                    <FTREF/>
                     In addition, we will address significant comments submitted by the public on the economic analysis and the Initial Regulatory Flexibility Analysis (IRFA) 
                    <SU>8</SU>
                    <FTREF/>
                     which accompanied the proposed rule. DHS has determined that the final rule amending the initial SEVP school certification fee and establishing procedures for recertification of schools with F and/or M students will not have a significant impact on a substantial number of small entities; therefore, a Final Regulatory Flexibility Analysis was not necessary. The factual basis for certification is presented in the following analysis of the economic effects of the final rule.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         According to the RFA, a small entity may be (1) a small business, defined as any independently owned and operated business not dominant in its field; (2) a small not-for-profit organization; or (3) a small governmental jurisdiction, defined as a locality with a population of less than 50,000 persons.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         “Regulatory Flexibility Act Analysis: Impact on Small Schools of the Change in Fees for Certification and Institution of Recertification by the Student and Exchange Visitor Program.”
                    </P>
                </FTNT>
                <P>
                    Currently, the fee for schools seeking initial certification is $230, plus a $350 fee for each campus receiving a site visit. These fees have not changed since 2002, prior to the reorganization of the INS into DHS. Both the processes and costs for adjudicating school petitions for initial certification have changed substantially since that time. SEVP is statutorily required to regularly review the fee level to ensure that the cost of services provided by the program are fully captured by fees assessed on those receiving the services.
                    <SU>9</SU>
                    <FTREF/>
                     The increased fee schedule set by this rule will recover the full cost of SEVP operations with fee-generated revenue, and align fees with currently planned costs and processes that have been redesigned and refined as the program has expanded over the years. Moreover, SEVP examined three alternatives to the rule, which are detailed in the economic analysis to the proposed rule, all of which were rejected because they did not accomplish stated goals of the regulation. 
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         As mandated by 31 U.S.C. 902(a)(8); OMB Circular A-25.
                    </P>
                </FTNT>
                <P>Accordingly, the final rule will increase the initial certification fee for schools seeking to admit F and/or M students to $1700, plus an additional fee of $655 per site visit. In addition, the final rule will set procedures by which SEVP-certified schools are recertified every two years. The cost burden to the schools associated with recertification entail the time and effort associated with filing the petition rather than direct monetary outlays. It is important to note that schools applying for SEVP certification and recertification are making a voluntary decision based on their desire to admit nonimmigrant students into their program. Likewise, schools that have already been SEVP-certified, but have no F and/or M students and no concrete plans to enroll any have little incentive to recertify. As such, the compliance requirements of this rule only affect those schools wishing to become SEVP-certified, or those that wish to maintain their approval to admit nonimmigrant students, by undergoing recertification. </P>
                <P>SEVP conducted an analysis of the potential impact of the increased certification fee using data drawn from SEVIS in May 2007. All SEVP-certified schools self-report average enrollment and average tuition costs for students. Therefore, SEVP did not need to use publicly available information or use sampling to gather data on the finances of the type of schools applying for certification. The reported number of F and/or M students and the tuition costs per F and/or M student were used to estimate annual total tuition income. The tuition cost per student was determined by the data in the school's Form I-17, Petition for Approval of School for Attendance by Nonimmigrant Student, available in SEVIS. </P>
                <P>
                    While tuition revenue may underestimate the actual school revenue, this is the best information available. It is the most significant source of income for most schools and 
                    <PRTPAGE P="55697"/>
                    is a reasonable approach to measuring the impact of this fee rule. 
                </P>
                <P>
                    As detailed in the economic analysis and IRFA to the proposed rule, SEVP developed a profile of schools applying for certification for the last three years using current SEVIS enrollment data. Based on this developed profile, SEVP projects that 700 new schools will certify annually. Of these, we expect about 575, or approximately 82% of the schools seeking certification in the future to be small schools by U.S. Small Business Administration (SBA) standards.
                    <SU>10</SU>
                    <FTREF/>
                     SBA's size standard for all schools, except flight schools and public high schools, is $6 million or less in annual receipts. The SBA small business definition for flight schools is $21.5 million or less in annual receipts. The analysis uses the definition of a small government jurisdiction as defined in the Regulatory Flexibility Analysis (RFA) to determine the small entity threshold of public high schools. Size classifications of SEVP-certified public school districts were determined using the figures from the National Center for Education Statistics on the Department of Education Web site. Schools in districts serving populations of 50,000 or less were designated as small schools for the purposes of this analysis. 
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         SBA's small business size standards are matched to industries described in the North American Industry Classification System (NAICS). All types of SEVP-certified schools are described in the NAICS codes for the Educational Sector (611).
                    </P>
                </FTNT>
                <P>Of the 575 small schools expected to apply for certification, only 47 are expected to have a compliance impact of 1% or more. That is, the certification fee is 1% or more of the total earnings of the school, as calculated by the tuition collected from F and/or M students. The 47 small schools comprise about 7% of all schools expected to certify annually, and about 8% of all small schools expected to certify annually. Table 1 provides the projected number of small schools at each level of impact. </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s50,13">
                    <TTITLE>Table 1—Projected Number of Small Schools Expected To Certify by Level of Impact </TTITLE>
                    <BOXHD>
                        <CHED H="1">Level of impact </CHED>
                        <CHED H="1">
                            Projected 
                            <LI>number of </LI>
                            <LI>small schools </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Under 0.5% </ENT>
                        <ENT>469 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">0.5% to under 1% </ENT>
                        <ENT>59 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1% to under 2% </ENT>
                        <ENT>29 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2% to under 3% </ENT>
                        <ENT>7 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3% to under 4% </ENT>
                        <ENT>1 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4% to under 5% </ENT>
                        <ENT>5 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5% to under 6% </ENT>
                        <ENT>1 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6% to under 7% </ENT>
                        <ENT>2 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7% to under 8% </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10% to under 11% </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12% to under 13% </ENT>
                        <ENT>1 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">23% to under 24% </ENT>
                        <ENT>1 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>As evidenced from the table above, the overwhelming majority, approximately 91.8%, of small schools expected to apply for certification will have compliance costs of less than 1% of their annual earnings. Furthermore, only 18 schools (about 3% of small school certification applicants) will have impact costs of 2% or more, and only 11 schools (about 2%) will have impact costs of 3% or more. Only 5 small schools (about 0.9%) are expected to have compliance impacts of 5% or more of their annual earnings. </P>
                <HD SOURCE="HD3">Public Comments on the Economic Analysis and IRFA to the Proposed Rule </HD>
                <P>The RFA requires agencies to address all significant public comments raised in regard to the expected economic impact of the regulation. SEVP received two comments directly referencing the economic impacts of the rule. One commenter expressed concern over the increase in the I-901 SEVIS fee, stating that the increased fee coupled with immigration laws would result in decreased enrollment among small to mid-sized educational institutions in the United States. While SEVP recognizes that the increased nonimmigrant student application fee will place an additional cost burden on those students wishing to study in the United States, we do not believe it will result in significant decreases in enrollment among U.S. small to mid-size educational institutions. Prior to implementing this rule, SEVP compared the new fee schedule for nonimmigrant students with that of our top 12 global competitors and discovered that the new fees would place the United States firmly in the upper-middle of this group. Furthermore, SEVP is under statutory requirement to regularly review and adjust fees collected so as to capture the true operating costs of the program. Another commenter expressed concern over the increase in the certification fee, and stated the increase is a disincentive for schools, especially small schools, to seek certification. Based on our review of current SEVP-certification schools, especially those classified as small entities, we have found that a significantly larger number of the schools certified since 2004 were small schools. In addition, we anticipate that the overwhelming majority (over 90%) of potential small schools applying for certification in the future will have compliance costs of 1% or less of the annual tuition earnings collected from nonimmigrant students. As such, we believe the increased school certification fee will not prove to be a major disincentive for those schools wishing to admit nonimmigrant students. </P>
                <P>We did not receive public comments in opposition of our belief that the rule will not cause a significant economic impact to a substantial number of affected businesses, as stated in the analysis accompanying the proposed rule. In light of public comments received, combined with our analysis of the expected compliance costs impacts of certification, DHS certifies that this rule will not have a significant economic impact on a substantial number of small entities. </P>
                <HD SOURCE="HD2">B. Unfunded Mandates Reform Act </HD>
                <P>
                    The Unfunded Mandates Reform Act of 1995 (UMRA) requires certain actions to be taken by an agency before “promulgation of any rule that includes any federal mandate that may result in the expenditure by State, Local and Tribal governments, in the aggregate, or by the private sector, of $100,000,000 or more (adjusted annually for inflation) in any 1 year.” 2 U.S.C. 1532(a). This rulemaking is not a “Federal mandate,” as defined for UMRA purposes, 2 U.S.C. 658(6), as the payment of an SEVP certification fee by individuals, Local governments or other private sector entities is (to the extent it could be termed an enforceable duty) one that arises from participation in a voluntary federal program (
                    <E T="03">i.e.,</E>
                     applying for status as F-1, F-3, M-1, or M-3 students or as J-1 exchange visitor in the United States or seeking approval from the United States for attendance by certain aliens seeking status as F-1, F-3, M-1 students). 2 U.S.C. 658(7)(A)(ii). Therefore, no actions were deemed necessary under the provisions of the UMRA. 
                </P>
                <HD SOURCE="HD2">C. Small Business Regulatory Enforcement Fairness Act of 1996 </HD>
                <P>
                    This rulemaking is not a major rule, as defined by 5 U.S.C. 804, for purposes of Congressional review of agency rulemaking under the Small Business Regulatory Enforcement Act of 1996, Public Law 104-121. This rulemaking would not result in an annual effect on the economy of more than $100 million; 
                    <PRTPAGE P="55698"/>
                    a major increase in costs or prices; or significant adverse effects on competition, employment, investment, productivity, innovation, or on the ability of U.S.-based companies to compete with foreign-based companies in domestic and export markets. 
                </P>
                <HD SOURCE="HD2">D. Executive Order 12866: Regulatory Review </HD>
                <P>This proposed rule is not considered by DHS to be an economically significant regulatory action under Executive Order 12866, section 3(f), Regulatory Planning and Review, since it would not have an annual effect on the U.S. economy of $100 million. The implementation of this proposed rule would provide ICE with additional fee revenue of $58.538 million in FY 2009 and $62.581 million in FY 2010. It is, however, a significant rulemaking under the Executive order and therefore has been reviewed by OMB. </P>
                <HD SOURCE="HD2">E. Executive Order 13132: Federalism </HD>
                <P>This rulemaking would not have substantial direct effects on the States, or on the relationship between the federal government and the States, or on the distribution of power and responsibilities among the various levels of government. Consequently, DHS has determined that this rulemaking does not have sufficient federalism implications to warrant the preparation of a federalism summary impact statement, in accordance with section 6 of Executive Order 13132. </P>
                <HD SOURCE="HD2">F. Executive Order 12988: Civil Justice Reform </HD>
                <P>This proposed rule meets the applicable standards set forth in 3(a) and 3(b)(2) of Executive Order 12988. </P>
                <HD SOURCE="HD2">G. Paperwork Reduction Act </HD>
                <P>
                    All Departments are required to submit to OMB for review and approval, any reporting or recordkeeping requirements inherent in a rule under the Paperwork Reduction Act of 1995, Public Law 104-13, 109 Stat. 163 (1995), 44 U.S.C. 3501, 
                    <E T="03">et seq.</E>
                     Schools will be using SEVIS to petition for recertification. The recertification process requires schools to input data into SEVIS, print the Form I-17 and sign the form. The electronic data captured for the Form I-17 have been previously approved for use by OMB as one component of the data captured in SEVIS. The OMB Control Number for this collection is 1615-0066 (changed to 1653-0038). With the implementation of SEVIS under 67 FR 60107 (September 25, 2002), most schools enrolled in SEVIS were petitioning for DHS recertification, rather than initial certification (
                    <E T="03">i.e.,</E>
                     enrolling F or M nonimmigrant students for the first time). The workload for both certification and recertification was included under OMB 1615-0066. 
                </P>
                <P>The changes to the fees require changes to SEVIS and the I-901 software to reflect the updated fee amounts, as these systems generate the pertinent petition and application forms. SEVP would submit a revision to OMB with respect to any changes to existing information collection approvals. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>8 CFR Part 103 </CFR>
                    <P>Administrative practice and procedure, Authority delegations (Government agencies), Freedom of Information, Privacy, Reporting and recordkeeping requirements, Surety bonds. </P>
                    <CFR>8 CFR Part 214 </CFR>
                    <P>Administrative practice and procedure, Aliens, Employment, Foreign officials, Health professions, Reporting and recordkeeping requirements, Students.</P>
                </LSTSUB>
                <REGTEXT TITLE="8" PART="103">
                    <AMDPAR>Accordingly, Chapter I of Title 8 of the Code of Federal Regulations is amended as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 103—POWERS AND DUTIES; AVAILABILITY OF RECORDS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 103 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            5 U.S.C. 301, 552, 552a; 8 U.S.C. 1101, 1103, 1304, 1356; 31 U.S.C. 9701; Public Law 107-296, 116 Stat. 2135 (6 U.S.C. 1 
                            <E T="03">et seq.</E>
                             ); E.O. 12356, 47 FR 14874, 15557, 3 CFR, 1982 Comp., p. 166; 8 CFR part 2. 
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="8" PART="103">
                    <AMDPAR>2. Section 103.7(b)(1) is amended by revising the entries for Forms I-17, I-290B, and I-901 in the listing of fees, to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 103.7 </SECTNO>
                        <SUBJECT>Fees. </SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(1) * * *</P>
                        <STARS/>
                        <P>
                            <E T="03">Form I-17.</E>
                             For filing a petition for school certification—$1,700, plus a site visit fee of $655 for each location listed on the form. 
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Form I-901.</E>
                             For remittance of the I-901 SEVIS fee for F and M students—$200. For remittance of the I-901 SEVIS fee for certain J exchange visitors—$180. For remittance of the I-901 SEVIS fee for J-1 au pairs, camp counselors, and participants in a summer work/travel program—$35. There is no I-901 SEVIS fee remittance obligation for J exchange visitors in federally-funded programs with a program identifier designation prefix that begins with G-1, G-2, G-3 or G-7. 
                        </P>
                        <P/>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="8" PART="214">
                    <PART>
                        <HD SOURCE="HED">PART 214—NONIMMIGRANT CLASSES </HD>
                    </PART>
                    <AMDPAR>3. The authority citation for part 214 is revised to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>8 U.S.C. 1101, 1102, 1103, 1182, 1184, 1185 (pursuant to E.O. 13323, 69 FR 241, 3 CFR, 2003 Comp., p. 278), 1186a, 1187, 1221, 1281, 1282, 1301-1305, 1356, 1372, 1379, 1731-32; section 643, Public Law 104-208, 110 Stat. 3009-708; section 141 of the Compacts of Free Association with the Federated States of Micronesia and the Republic of the Marshall Islands, and with the Government of Palau, 48 U.S.C. 1901 note, and 1931 note, respectively, 8 CFR part 2. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="8" PART="214">
                    <AMDPAR>4. Section 214.3 is amended by: </AMDPAR>
                    <AMDPAR>a. Revising paragraph (a)(1); </AMDPAR>
                    <AMDPAR>b. Adding paragraph (a)(3); </AMDPAR>
                    <AMDPAR>c. Revising the first sentence in paragraph (b) introductory text; </AMDPAR>
                    <AMDPAR>d. Revising the first sentence in paragraph (c); </AMDPAR>
                    <AMDPAR>e. Revising paragraphs (d), (e), and (f); </AMDPAR>
                    <AMDPAR>f. Revising paragraph (g)(1); </AMDPAR>
                    <AMDPAR>g. Removing paragraph (g)(2); </AMDPAR>
                    <AMDPAR>h. Redesignating paragraphs (g)(3) and (g)(4) as paragraphs (g)(2) and (g)(3) respectively; </AMDPAR>
                    <AMDPAR>i. Revising newly designated paragraph (g)(2) heading, and by revising newly designated paragraphs (g)(2)(i), (g)(2)(ii) introductory text, (g)(2)(ii)(E), and (g)(2)(iii)(C); </AMDPAR>
                    <AMDPAR>j. Adding paragraph (g)(2)(iii)(D); </AMDPAR>
                    <AMDPAR>k. Revising paragraph (h); </AMDPAR>
                    <AMDPAR>l. Revising paragraph (i); </AMDPAR>
                    <AMDPAR>m. Revising the introductory text of paragraph (k); </AMDPAR>
                    <AMDPAR>n. Revising paragraph (l)(1)(ii); </AMDPAR>
                    <AMDPAR>o. Revising paragraph (l)(2). </AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 214.3 </SECTNO>
                        <SUBJECT>Approval of schools for enrollment of F and M nonimmigrants. </SUBJECT>
                        <P>(a) * * *</P>
                        <P>
                            (1) 
                            <E T="03">General.</E>
                             A school or school system seeking initial or continued authorization for attendance by nonimmigrant students under sections 101(a)(15)(F)(i) or 101(a)(15)(M)(i) of the Act, or both, must file a petition for certification or recertification with SEVP, using the Student and Exchange Visitor Information System (SEVIS), in accordance with the procedures at paragraph (h) of this section. The petition must state whether the school or school system is seeking certification or recertification for attendance of nonimmigrant students under section 
                            <PRTPAGE P="55699"/>
                            101(a)(15)(F)(i) or 101(a)(15)(M)(i) of the Act or both. The petition must identify by name and address each location of the school that is included in the petition for certification or recertification, specifically including any physical location in which a nonimmigrant can attend classes through the school (
                            <E T="03">i.e.,</E>
                             campus, extension campuses, satellite campuses, etc.). 
                        </P>
                        <P>
                            (i) 
                            <E T="03">School systems.</E>
                             A school system, as used in this section, means public school (grades 9-12) or private school (grades kindergarten-12). A petition by a school system must include a list of the names and addresses of those schools included in the petition with the supporting documents. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Submission requirements.</E>
                             Certification and recertification petitions require that a complete Form I-17, Petition for Approval of School for Attendance by Nonimmigrant Student, including supplements A and B and bearing original signatures, be included with the school's submission of supporting documentation. In submitting the Form I-17, a school certifies that the designated school officials (DSOs) signing the form have read and understand DHS regulations relating to: Nonimmigrant students at 8 CFR 214.1, 214.2(f), and/or 214.2(m); change of nonimmigrant classification for students at 8 CFR 248; school certification and recertification under this section; withdrawal of school certification under this section and 8 CFR 214.4; that both the school and its DSOs intend to comply with these regulations at all times; and that, to the best of its knowledge, the school is eligible for SEVP certification. Willful misstatements may constitute perjury (18 U.S.C. 1621). 
                        </P>
                        <STARS/>
                        <P>
                            (3) 
                            <E T="03">Eligibility.</E>
                             (i) The petitioner, to be eligible for certification, must establish at the time of filing that it: 
                        </P>
                        <P>(A) Is a bona fide school; </P>
                        <P>(B) Is an established institution of learning or other recognized place of study; </P>
                        <P>(C) Possesses the necessary facilities, personnel, and finances to conduct instruction in recognized courses; and </P>
                        <P>(D) Is, in fact, engaged in instruction in those courses. </P>
                        <P>(ii) The petitioner, to be eligible for recertification, must establish at the time of filing that it: </P>
                        <P>(A) Remains eligible for certification in accordance with paragraph (a)(3)(i) of this section; </P>
                        <P>(B) Has complied during its previous period of certification or recertification with recordkeeping, retention, and reporting requirements and all other requirements of paragraphs (g), (j), (k), and (l) of this section. </P>
                        <P>(b) * * * Institutions petitioning for certification or recertification must submit certain supporting documents as follows, pursuant to sections 101(a)(15)(F) and (M) of the Act. * * * </P>
                        <STARS/>
                        <P>(c) * * * If the petitioner is a vocational, business, or language school, or American institution of research recognized as such by the Secretary of Homeland Security, it must submit evidence that its courses of study are accepted as fulfilling the requirements for the attainment of an educational, professional, or vocational objective, and are not avocational or recreational in character. * * *</P>
                        <P>
                            (d) 
                            <E T="03">Interview of petitioner.</E>
                             The petitioner or an authorized representative of the petitioner may be required to appear in person before or be interviewed by telephone by a DHS representative prior to the adjudication of a petition for certification or recertification. The interview will be conducted under oath. 
                        </P>
                        <P>
                            (e) 
                            <E T="03">Notices to schools related to certification or recertification petitions or to out-of-cycle review—</E>
                            (1) 
                            <E T="03">General.</E>
                             All notices from SEVP to schools or school systems related to school certification, recertification, or out-of-cycle review (including, but not limited to, notices related to the collection of evidence, testimony, and appearance pertaining to petitions for recertification encompassing compliance with the recordkeeping, retention and reporting, and other requirements of paragraphs (f), (g), (j), (k), and (l) of this section, as well as to eligibility) will be served in accordance with the procedures at 8 CFR 103.2(b)(1), (4)-(16), (18) and (19), with the exception that all procedures will be conducted by SEVP, the SEVP Director, and the Assistant Secretary, ICE, as appropriate, and except as provided in this section. All such notices will be served (
                            <E T="03">i.e.,</E>
                             generated and transmitted) through SEVIS and/or by e-mail. The date of service is the date of transmission of the e-mail notice. DSOs must maintain current contact information, including current e-mail addresses, at all times. Failure of a school to receive SEVP notices due to inaccurate DSO e-mail addresses in SEVIS or blockages of the school's e-mail system caused by spam filters is not grounds for appeal of a denial or withdrawal. The term “in writing” means either a paper copy bearing original signatures or an electronic copy bearing electronic signatures. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">SEVP approval notification and SEVIS updating by certified schools.</E>
                             SEVP will notify the petitioner by updating SEVIS to reflect approval of the petition and by e-mail upon approval of a certification or recertification petition. The certification or recertification is valid only for the type of program and nonimmigrant classification specified in the certification or recertification approval notice. The certification must be recertified every two years and may be subject to out-of-cycle review at any time. Approval may be withdrawn in accordance with 8 CFR 214.4. 
                        </P>
                        <P>
                            (3) 
                            <E T="03">Modifications to Form I-17 while a school is SEVP-certified.</E>
                             Any modification made by an SEVP-certified school on the Form I-17 at any time after certification and for the duration of a school's authorization to enroll F and/or M students must be reported to SEVP and will be processed by SEVP in accordance with the provisions of paragraphs (f)(1), (g)(2) and (h)(3)(i) of this section. 
                        </P>
                        <P>
                            (4) 
                            <E T="03">Notice of Intent to Withdraw (NOIW) SEVP certification—</E>
                            (i) 
                            <E T="03">Automatic withdrawal.</E>
                             SEVP will serve the school with an NOIW 30 days prior to a school's SEVP certification expiration date if the school has not submitted to SEVP a completed recertification petition, in accordance with paragraph (h)(2) of this section. The school will be automatically withdrawn immediately, in accordance with 8 CFR 214.4(a)(3), if it has not submitted a completed recertification petition by the school's certification expiration date. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Withdrawal on notice.</E>
                             SEVP will serve a Withdrawal on Notice, in accordance with 8 CFR 214.4(b), if SEVP determines that a school reviewed out-of-cycle has failed to sustain eligibility or has failed to comply with the recordkeeping, retention, reporting and other requirements of paragraphs (f), (g), (j), (k), and (l) of this section. When a school fails to file an answer to an NOIW within the 30-day period, SEVP will withdraw the school's certification and notify the DSOs of the decision, in accordance with 8 CFR 214.4(d). Such withdrawal of certification may not be appealed. 
                        </P>
                        <P>
                            (5) 
                            <E T="03">Notice of Denial.</E>
                             A Notice of Denial will be served to a school when SEVP denies a petition for initial certification or recertification. The notice will address appeals options. Schools denied recertification must comply with 8 CFR 214.4(i). 
                        </P>
                        <P>
                            (6)
                            <E T="03"> Notice of Automatic Withdrawal.</E>
                             Schools that relinquish SEVP certification for any of the reasons cited in 8 CFR 214.4(a)(3) will be served a Notice of Automatic Withdrawal. 
                            <PRTPAGE P="55700"/>
                        </P>
                        <P>
                            (7) 
                            <E T="03">Notice of Withdrawal.</E>
                             A school found to be ineligible for continued SEVP certification as a result of an out-of-cycle review will receive a Notice of Withdrawal. Schools withdrawn must comply with 8 CFR 214.4(i). 
                        </P>
                        <P>
                            (8) 
                            <E T="03">Notice of SEVIS Access Termination Date.</E>
                             The Notice of SEVIS Access Termination Date gives the official date for the school's denial or withdrawal to be final and SEVIS access to be terminated. In most situations, SEVP will not determine a SEVIS access termination date for that school until the appeals process has concluded and the initial denial or withdrawal has been upheld, in accordance with 8 CFR 214.4(i)(3). The school will no longer be able to access SEVIS and SEVP will automatically terminate any remaining Active SEVIS records for that school on that date. 
                        </P>
                        <P>
                            (f) 
                            <E T="03">Adjudication of a petition for SEVP certification or recertification—</E>
                            (1) 
                            <E T="03">Approval.</E>
                             The school is required to immediately report through SEVIS any change to its school information upon approval of a petition for SEVP certification or recertification. Modification to school information listed in paragraph (h)(3) of this section will require a determination of continued eligibility for certification. The certification or recertification is valid only for the type of program and student specified in the approval notice. The certification may be withdrawn in accordance with the provisions of 8 CFR 214.4, is subject to review at any time, and will be reviewed every two years. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Denial.</E>
                             The petitioner will be notified of the reasons for the denial and appeal rights, in accordance with the provisions of 8 CFR part 103 and 8 CFR 214.4, if SEVP denies a petition for certification or recertification. 
                        </P>
                        <P>(g) * * *</P>
                        <P>
                            (1) 
                            <E T="03">Student records.</E>
                             An SEVP-certified school must keep records containing certain specific information and documents relating to each F-1 or M-1 student to whom it has issued a Form I-20, while the student is attending the school and until the school notifies SEVP, in accordance with the requirements of paragraphs (g)(1) and (2) of this section, that the student is not pursuing a full course of study. Student information not required for entry in SEVIS may be kept in the school's student system of records, but must be accessible to DSOs. The school must keep a record of having complied with the reporting requirements for at least three years after the student is no longer pursuing a full course of study. The school must maintain records on the student in accordance with paragraphs (g)(1) and (2) of this section if a school recommends reinstatement for a student who is out of status. The school must maintain records on the student for three years from the date of the denial if the reinstatement is denied. The DSO must make the information and documents required by this paragraph available, including academic transcripts, and must furnish them to DHS representatives upon request. Schools must maintain and be able to provide an academic transcript or other routinely maintained student records that reflect the total, unabridged academic history of the student at the institution, in accordance with paragraph (g)(1)(iv) of this section. All courses must be recorded in the academic period in which the course was taken and graded. The information and documents that the school must keep on each student are as follows: 
                        </P>
                        <P>(i) Identification of the school, to include name and full address. </P>
                        <P>(ii) Identification of the student, to include name while in attendance (record any legal name change), date and place of birth, country of citizenship, and school's student identification number. </P>
                        <P>(iii) Current address where the student and his or her dependents physically reside. In the event the student or his or her dependents cannot receive mail at such physical residence, the school must provide a mailing address in SEVIS. If the mailing address and the physical address are not the same, the school must maintain a record of both mailing and physical addresses and provide the physical location of residence of the student and his or her dependents to DHS upon request. </P>
                        <P>(iv) Record of coursework. Identify the student's degree program and field of study. For each course, give the periods of enrollment, course identification code and course title; the number of credits or contact hours, and the grade; the number of credits or clock hours, and for credit hour courses the credit unit; the term unit (semester hour, quarter hour, etc.). Include the date of withdrawal if the student withdrew from a course. Show the grade point average for each session or term. Show the cumulative credits or clock hours and cumulative grade point average. Narrative evaluation will be accepted in lieu of grades when the school uses no other type of grading. </P>
                        <P>(v) Record of transfer credit or clock hours accepted. Type of hours, course identification, grades. </P>
                        <P>(vi) Academic status. Include the effective date or period if suspended, dismissed, placed on probation, or withdrawn. </P>
                        <P>(vii) Whether the student has been certified for practical training, and the beginning and end dates of certification. </P>
                        <P>(viii) Statement of graduation (if applicable). Title of degree or credential received, date conferred, program of study or major. </P>
                        <P>(ix) Termination date and reason. </P>
                        <P>(x) The documents referred to in paragraph (k) of this section. </P>
                        <NOTE>
                            <HD SOURCE="HED">Note to paragraph (g)(1):</HD>
                            <P>A DHS officer may request any or all of the data in paragraphs (g)(1)(i) through (x) of this section on any individual student or class of students upon notice. This notice will be in writing if requested by the school. The school will have three work days to respond to any request for information concerning an individual student, and ten work days to respond to any request for information concerning a class of students. The school will respond orally on the same day the request for information is made if DHS requests information on a student who is being held in custody, and DHS will provide a written notification that the request was made after the fact, if the school so desires. DHS will first attempt to gain information concerning a class of students from DHS record systems.</P>
                        </NOTE>
                        <P>
                            (2) 
                            <E T="03">Reporting changes in student and school information.</E>
                             (i) Schools must update SEVIS with the current information within 21 days of a change in any of the information contained in paragraphs (f)(1) and (h)(3) of this section. 
                        </P>
                        <P>(ii) Schools are also required to report within 21 days any change of the information contained in paragraph (g)(1) or the occurrence of the following events: </P>
                        <STARS/>
                        <P>(E) Any other notification request not covered by paragraph (g)(1) of this section made by DHS with respect to the current status of the student. </P>
                        <P>(iii) * * *</P>
                        <P>
                            (C) 
                            <E T="03">The start date of the student's next session, term, semester, trimester, or quarter.</E>
                             For initial students, the start date is the “program start date” or “report date.” (These terms are used interchangeably.) The DSO may choose a reasonable date to accommodate a student's need to be in attendance for required activities at the school prior to the actual start of classes when determining the report date on the Form I-20. Such required activities may include, but are not limited to, research projects and orientation sessions. The DSO may not, however, indicate a report date more than 30 days prior to the start of classes. The next session start date is the start of classes for continuing students. 
                        </P>
                        <P>
                            (D) 
                            <E T="03">Adjustment to the program completion date.</E>
                             Any factors that influence the student's progress toward 
                            <PRTPAGE P="55701"/>
                            program completion (
                            <E T="03">e.g.,</E>
                             deferred attendance, authorized drop below, program extension) must be reflected by making an adjustment updating the program completion date. 
                        </P>
                        <STARS/>
                        <P>
                            (h) 
                            <E T="03">SEVP certification, recertification, out-of-cycle review, and oversight of schools.</E>
                        </P>
                        <P>
                            (1) 
                            <E T="03">Certification.</E>
                             A school seeking SEVP certification for attendance by nonimmigrants under section 101(a)(15)(F)(i) or 101(a)(15)(m)(i) of the Act must use SEVIS to file an electronic petition (which compiles the data for the Form I-17) and must submit the nonrefundable certification petition fee on-line. 
                        </P>
                        <P>
                            (i) 
                            <E T="03">Filing a petition.</E>
                             The school must access the SEVP Web site at 
                            <E T="03">http://www.ice.gov/sevis</E>
                             to file a certification petition in SEVIS. The school will be issued a temporary ID and password in order to access SEVIS to complete and submit an electronic Form I-17. The school must submit the proper nonrefundable certification petition fee as provided in 8 CFR 103.7(b)(1). 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Site visit, petition adjudication and school notification.</E>
                             SEVP will conduct a site visit for each petitioning school and its additional schools or campuses. SEVP will contact the school to arrange the site visit. The school must comply with and complete the visit within 30 days after the date SEVP contacts the school to arrange the visit, or the petition for certification will be denied as abandoned. DSOs and school officials that have signed the school's Form I-17 petition must be able to demonstrate to DHS representatives how they obtain access to the regulations cited in the certification as part of the site visit. Paper or electronic access is acceptable. DSOs must be able to extract pertinent citations within the regulations related to their requirements and responsibilities. SEVP will serve a notice of approval and SEVIS will be updated to reflect the school's certification if SEVP approves the school's certification petition. 
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Certification denial.</E>
                             SEVP will serve a notice of denial in accordance with paragraph (f)(2) of this section if a school's petition for certification is denied. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Recertification.</E>
                             Schools are required to file a completed petition for SEVP recertification before the school's certification expiration date, which is two years from the date of their previous SEVP certification or recertification expiration date, except for the first recertification cycle after publication of the recertification rule. There is no recertification petition fee. SEVP will review a petitioning school's compliance with the recordkeeping, retention and reporting, and other requirements of paragraphs (f), (g), (j), (k), and (l) of this section, as well as continued eligibility for certification, pursuant to paragraph (a)(3) of this section. 
                        </P>
                        <P>
                            (i) 
                            <E T="03">Filing of petition for recertification.</E>
                             Schools must submit a completed Form I-17 (including supplements A and B) using SEVIS, and submit a paper copy of the Form I-17 bearing original signatures of all officials. SEVP will notify all DSOs of a previously certified school 180 days prior to the school's certification expiration date that the school may submit a petition for recertification. A school may file its recertification petition at any time after receipt of this notification. A school must submit a complete recertification petition package, as outlined in the submission guidelines, by its certification expiration date. SEVP will send a notice of confirmation of complete filing or rejection to the school upon receipt of any filing of a petition for recertification. 
                        </P>
                        <P>(A) Notice of confirmation assures a school of uninterrupted access to SEVIS while SEVP adjudicates the school's petition for recertification. A school that has complied with the petition submission requirements will continue to have SEVIS access after its certification expiration date while the adjudication for recertification is pending. The school is required to comply with all regulatory recordkeeping, retention and reporting, and other requirements of paragraphs (f), (g), (j), (k), and (l) of this section during the period the petition is pending. </P>
                        <P>(B) Notice of rejection informs a school that it must take prompt corrective action in regard to its recertification petition prior to its certification expiration date to ensure that its SEVIS access will not be terminated and its petition for recertification will be accepted for adjudication. </P>
                        <P>
                            (ii) 
                            <E T="03">Consequence of failure to petition.</E>
                             SEVP will serve an NOIW to the school 30 days prior to a school's certification expiration date. SEVP will no longer accept a petition for recertification from the school and will immediately withdraw the school's certification if the school does not petition for recertification, abandons its petition, or does not submit a complete recertification petition package by the certification expiration date, in accordance with the automatic withdrawal criteria in 8 CFR 214.4(a)(3). The school must comply with 8 CFR 214.4(i) upon withdrawal. 
                        </P>
                        <P>
                            (iii) 
                            <E T="03">School recertification process</E>
                            — (A) 
                            <E T="03">General.</E>
                             School recertification reaffirms the petitioning school's eligibility for SEVP certification and the school's compliance with recordkeeping, retention, reporting and other requirements of paragraphs (f), (g), (j), (k), and (l) of this section since its previous certification. 
                        </P>
                        <P>
                            (B) 
                            <E T="03">Compliance.</E>
                             Assessment by SEVP of a school petitioning for recertification will focus primarily on overall school compliance, but may also include examination of individual DSO compliance as data and circumstances warrant. Past performance of these individuals, whether or not they continue to serve as principal designated school officials (PDSOs) or DSOs, will be considered in any petition for recertification of the school. 
                        </P>
                        <P>
                            (C) 
                            <E T="03">On-site review for recertification.</E>
                             All schools are subject to on-site review, at the discretion of SEVP, in conjunction with recertification. The school must comply with and complete an on-site review within 30 days of the notification by a DHS representative of a school that it has been selected for an on-site review for recertification, or the petition for recertification will be denied as abandoned, resulting in the school's withdrawal from SEVIS. 
                        </P>
                        <P>
                            (iv) 
                            <E T="03">Recertification approval.</E>
                             SEVP will serve a notice of approval if a school's petition for recertification is approved. The date of the subsequent recertification review will be two years after the school's certification expiration date from this petition cycle. 
                        </P>
                        <P>
                            (v) 
                            <E T="03">Recertification denial.</E>
                             SEVP will serve a notice of denial if a school's petition for recertification is denied, in accordance with 8 CFR 103.3(a)(1)(i). 
                        </P>
                        <P>
                            (vi) 
                            <E T="03">Adjustment of certification expiration date.</E>
                             Schools eligible for recertification before March 25, 2009 will, at a minimum, have their certification expiration date extended to March 25, 2009. SEVP may extend the certification expiration date beyond this date during the first cycle of recertification. 
                        </P>
                        <P>
                            (3) 
                            <E T="03">Out-of-cycle review and oversight of SEVP-certified schools.</E>
                             (i) SEVP will determine if out-of-cycle review is required upon receipt in SEVIS of any changes from an SEVP-certified school to its Form I-17 information. The Form I-17 information that requires out-of-cycle review when changed includes: 
                        </P>
                        <P>(A) Approval for attendance of students (F/M/both); </P>
                        <P>(B) Name of school system; name of main campus; </P>
                        <P>(C) Mailing address of the school; </P>
                        <P>
                            (D) Location of the school; 
                            <PRTPAGE P="55702"/>
                        </P>
                        <P>(E) School type; </P>
                        <P>(F) Public/private school indicator; </P>
                        <P>(G) Private school owner name; </P>
                        <P>(H) The school is engaged in; </P>
                        <P>(I) The school operates under the following Federal, State, Local or other authorization; </P>
                        <P>(J) The school has been approved by the following national, regional, or state accrediting association or agency; </P>
                        <P>(K) Areas of study; </P>
                        <P>(L) Degrees available from the school; </P>
                        <P>(M) If the school is engaged in elementary or secondary education; </P>
                        <P>(N) If the school is engaged in higher education; </P>
                        <P>(O) If the school is engaged in vocational or technical education; </P>
                        <P>(P) If the school is engaged in English language training; </P>
                        <P>(Q) Adding or deleting campuses; </P>
                        <P>(R) Campus name; </P>
                        <P>(S) Campus mailing address; and </P>
                        <P>(T) Campus location address. </P>
                        <P>(ii) SEVP may request a school to electronically update all Form I-17 fields in SEVIS and provide SEVP with documentation supporting the update. The school must complete such updates in SEVIS and submit the supporting documentation to SEVP within 10 business days of the request from SEVP. </P>
                        <P>(iii) SEVP may review a school's certification at any time to verify the school's compliance with the recordkeeping, retention, reporting and other requirements of paragraphs (f), (g), (j), (k), and (l) of this section to verify the school's continued eligibility for SEVP certification pursuant to paragraph (a)(3) of this section. SEVP may initiate remedial action with the school, as appropriate, and may initiate withdrawal proceedings against the school pursuant to 8 CFR 214.4(b) if noncompliance or ineligibility of a school is identified. </P>
                        <P>
                            (iv) 
                            <E T="03">On-site review.</E>
                             SEVP-certified schools are subject to on-site review at any time. SEVP will initiate withdrawal proceedings against a certified school, pursuant to 8 CFR 214.4(b), if the certified school selected for on-site review prior to its certification expiration date fails to comply with and complete the review within 30 days of the date SEVP contacted the school to arrange the review. 
                        </P>
                        <P>
                            (v) 
                            <E T="03">Notice of Continued Eligibility.</E>
                             SEVP will serve the school a notice of continued eligibility if, upon completion of an out-of-cycle review, SEVP determines that the school remains eligible for certification. Such notice will not change the school's previously-determined certification expiration date unless specifically notified by SEVP. 
                        </P>
                        <P>
                            (vi) 
                            <E T="03">Withdrawal of certification.</E>
                             SEVP will institute withdrawal proceedings in accordance with 8 CFR 214.4(b) if, upon completion of an out-of-cycle review, SEVP determines that a school or its programs are no longer eligible for certification. 
                        </P>
                        <P>
                            (vii) 
                            <E T="03">Voluntary withdrawal.</E>
                             A school can voluntarily withdraw from SEVP certification at any time or in lieu of complying with an out-of-cycle review or request. Failure of a school to comply with an out-of-cycle review or request by SEVP will be treated as a voluntary withdrawal. A school must initiate voluntary withdrawal by sending a request for withdrawal on official school letterhead to SEVP. 
                        </P>
                        <P>
                            (i) 
                            <E T="03">Administration of student regulations.</E>
                             DHS officials may conduct out-of-cycle, on-site reviews on the campuses of SEVP-certified schools to determine whether nonimmigrant students on those campuses are complying with DHS regulations pertaining to them, including the requirement that each maintains a valid passport. DHS officers will take appropriate action regarding violations of the regulations by nonimmigrant students. 
                        </P>
                        <STARS/>
                        <P>
                            (k) 
                            <E T="03">Issuance of Certificate of Eligibility.</E>
                             A DSO of an SEVP-certified school must sign any completed Form I-20 issued for either a prospective or continuing student or a dependent. A Form I-20 issued by a certified school system must state which school within the system the student will attend. Only a DSO of an SEVP-certified school may issue a Form I-20 to a prospective student and his or her dependents, and only after the following conditions are met: 
                        </P>
                        <STARS/>
                        <P>(l) * * * </P>
                        <P>(1) * * * </P>
                        <P>(ii) Each campus must have one PDSO. The PDSO is responsible for updating SEVIS to reflect the addition or deletion of any DSO on his or her associated campus. SEVP will use the PDSO as the point of contact on any issues that relate to the school's compliance with the regulations, as well as any system alerts generated by SEVIS. SEVP may also designate certain functions in SEVIS for use by the PDSO only. The PDSO of the main campus is the only DSO authorized to submit a Form I-17 for recertification. The PDSO and DSO will share the same responsibilities in all other respects. </P>
                        <STARS/>
                        <P>
                            (2) 
                            <E T="03">Name, title, and sample signature.</E>
                             Petitions for SEVP certification, review and recertification must include the names, titles, and sample signatures of designated officials. An SEVP-certified school must update SEVIS upon any changes to the persons who are principal or designated officials, and furnish the name, title and e-mail address of any new official within 21 days of the change. Any changes to the PDSO or DSO must be made by the PDSO within 21 days of the change. DHS may, at its discretion, reject the submission of any individual as a DSO or withdraw a previous submission by a school of an individual. 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="8" PART="214">
                    <AMDPAR>5. Section 214.4 is amended by: </AMDPAR>
                    <AMDPAR>a. Revising the section heading; </AMDPAR>
                    <AMDPAR>b. Revising paragraph (a)(1); </AMDPAR>
                    <AMDPAR>c. Redesignating paragraphs (a)(2) and (a)(3) as paragraphs (a)(3) and (a)(4) respectively; </AMDPAR>
                    <AMDPAR>d. Adding a new paragraph (a)(2); </AMDPAR>
                    <AMDPAR>e. Revising newly designated paragraph (a)(3); </AMDPAR>
                    <AMDPAR>f. Revising paragraph (b); </AMDPAR>
                    <AMDPAR>g. Revising paragraphs (g) and (h); and by </AMDPAR>
                    <AMDPAR>h. Adding paragraph (i). </AMDPAR>
                    <P>The revisions and addition read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 214.4 </SECTNO>
                        <SUBJECT>Denial of certification, denial of recertification or withdrawal of SEVP certification. </SUBJECT>
                        <P>(a) * * * </P>
                        <P>
                            (1) 
                            <E T="03">Denial of certification.</E>
                             The petitioning school will be notified of the reasons and appeal rights if a petition for certification is denied, in accordance with the provisions of 8 CFR 103.3(a)(1)(iii). No fee is required with appeals related to SEVP certification. A petitioning school denied certification may file a new petition for certification at any time. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Denial of recertification or withdrawal on notice.</E>
                             The school must wait at least one calendar year from the date of denial of recertification or withdrawal on notice before being eligible to petition again for SEVP certification if a school's petition for recertification is denied by SEVP pursuant to 8 CFR 214.3(h)(3)(v), or its certification is withdrawn on notice pursuant to paragraph (b) of this section. Eligibility to re-petition will be at the discretion of the Director of SEVP. SEVP certification of a school or school system for the attendance of nonimmigrant students, pursuant to sections 101(a)(15)(F)(i) and/or 101(a)(15)(M)(i) of the Immigration and Nationality Act, will be withdrawn on notice subsequent to out-of-cycle review, or recertification denied, if the school or school system is determined to no longer be entitled to certification for any valid and substantive reason including, but not limited to, the following: 
                            <PRTPAGE P="55703"/>
                        </P>
                        <P>(i) Failure to comply with 8 CFR 214.3(g)(1) without a subpoena. </P>
                        <P>(ii) Failure to comply with 8 CFR 214.3(g)(2). </P>
                        <P>(iii) Failure of a DSO to notify SEVP of the attendance of an F-1 transfer student as required by 8 CFR 214.2(f)(8)(ii). </P>
                        <P>(iv) Failure of a DSO to identify on the Form I-20 which school within the system the student must attend, in compliance with 8 CFR 214.3(k). </P>
                        <P>(v) Willful issuance by a DSO of a false statement, including wrongful certification of a statement by signature, in connection with a student's school transfer or application for employment or practical training. </P>
                        <P>(vi) Conduct on the part of a DSO that does not comply with the regulations. </P>
                        <P>(vii) The designation as a DSO of an individual who does not meet the requirements of 8 CFR 214.3(l)(1). </P>
                        <P>(viii) Failure to provide SEVP paper copies of the school's Form I-17 bearing the names, titles, and signatures of DSOs as required by 8 CFR 214.3(l)(2). </P>
                        <P>(ix) Failure to submit statements of DSOs as required by 8 CFR 214.3(l)(3). </P>
                        <P>(x) Issuance of Forms I-20 to students without receipt of proof that the students have met scholastic, language, or financial requirements as required by 8 CFR 214.3(k)(2). </P>
                        <P>(xi) Issuance of Forms I-20 to aliens who will not be enrolled in or carry full courses of study, as defined in 8 CFR 214.2(f)(6) or 214.2(m)(9). </P>
                        <P>(xii) Failure to operate as a bona fide institution of learning. </P>
                        <P>(xiii) Failure to employ adequate qualified professional personnel. </P>
                        <P>(xiv) Failure to limit advertising in the manner prescribed in 8 CFR 214.3(j). </P>
                        <P>(xv) Failure to maintain proper facilities for instruction. </P>
                        <P>(xvi) Failure to maintain accreditation or licensing necessary to qualify graduates as represented in the school's Form I-17. </P>
                        <P>(xvii) Failure to maintain the physical plant, curriculum, and teaching staff in the manner represented in the Form I-17. </P>
                        <P>(xviii) Failure to comply with the procedures for issuance of Forms I-20 as set forth in 8 CFR 214.3(k). </P>
                        <P>
                            (xix) Failure of a DSO to notify SEVP of material changes, such as changes to the school's name, address, or curricular changes that represent material change to the scope of institution offerings (
                            <E T="03">e.g.</E>
                            , addition of a program, class or course for which the school is issuing Forms I-20, but which does not have Form I-17 approval), as required by 8 CFR 214.3(f)(1). 
                        </P>
                        <P>
                            (3) 
                            <E T="03">Automatic withdrawal.</E>
                             A school that is automatically withdrawn and subsequently wishes to enroll nonimmigrant students in the future may file a new petition for SEVP certification at any time. The school must use the certification petition procedures described in 8 CFR 214.3(h)(1) to gain access to SEVIS for submitting its petition. Past compliance with the recordkeeping, retention, reporting and other requirements of 8 CFR 214.3(f), (g), (j), (k), and (l), and with the requirements for transition of students under paragraph (i) of this section will be considered in the evaluation of a school's subsequent petition for certification. SEVP certification will be automatically withdrawn: 
                        </P>
                        <P>(i) As of the date of termination of operations, if an SEVP-certified school terminates its operations. </P>
                        <P>(ii) As of a school's certification expiration date, if an SEVP-certified school does not submit a completed recertification petition in the manner required by 8 CFR 214.3(h)(2). </P>
                        <P>(iii) Sixty days after the change of ownership if an SEVP-certified school changes ownership, unless the school files a new petition for SEVP certification, in accordance with the procedures at 8 CFR 214.3(h)(1), within 60 days of the change of ownership. SEVP will review the petition if the school properly files such petition to determine whether the school still meets the eligibility requirements of 8 CFR 214.3(a)(3) and is still in compliance with the recordkeeping, retention, reporting and other requirements of 8 CFR 214.3(f), (g), (j), (k), and (l). SEVP will institute withdrawal proceedings in accordance with paragraph (b) of this section if, upon completion of the review, SEVP finds that the school is no longer eligible for certification, or is not in compliance with the recordkeeping, retention, reporting and other requirements of 8 CFR 214.3(f), (g), (j), (k), and (l). </P>
                        <P>(iv) If an SEVP-certified school voluntarily withdraws from its certification. </P>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Withdrawal on notice.</E>
                             SEVP will initiate an out-of-cycle review and serve the school with an NOIW if SEVP has information that a school or school system may no longer be entitled to SEVP certification prior to the school being due for its two-year recertification. The NOIW will inform the school of: 
                        </P>
                        <P>(1) The grounds for withdrawing SEVP certification. </P>
                        <P>(2) The 30-day deadline from the date of the service of the NOIW for the school to submit sworn statements, and documentary or other evidence, to rebut the grounds for withdrawal of certification in the NOIW. An NOIW is not a means for the school to submit evidence that it should have previously submitted as a part of its established reporting requirements. </P>
                        <P>(3) The school's right to submit a written request (including e-mail) within 30 days of the date of service of the NOIW for a telephonic interview in support of its response to the NOIW. </P>
                        <STARS/>
                        <P>
                            (g) 
                            <E T="03">Decision.</E>
                             The decision of SEVP will be in accordance with 8 CFR 103.3(a)(1). 
                        </P>
                        <P>
                            (h) 
                            <E T="03">Appeals.</E>
                             Notices of denial or withdrawal of SEVP certification will include appeal alternatives and filing instructions. Any appeal must be taken within 15 days after the service of the decision by stating the reasons for the appeal in the notice of appeal provided with the instructions, and supported by a statement or brief specifically setting forth the grounds for contesting the withdrawal of the approval. No fee is required with appeals related to denial of SEVP recertification or withdrawal of SEVP certification. 
                        </P>
                        <P>
                            (i) 
                            <E T="03">Operations at a school when SEVP certification is relinquished or withdrawn, or whose recertification is denied and on the SEVIS access termination date.</E>
                        </P>
                        <P>
                            (1) 
                            <E T="03">General.</E>
                             A school whose certification is relinquished or withdrawn, or whose recertification is denied may, at SEVP discretion, no longer be able to create Initial student records or issue new Forms I-20, Certificate of Eligibility for Nonimmigrant Student, for initial attendance. Schools must comply with the instructions given in the notice of withdrawal or denial with regard to management of status for their Initial and continuing F and/or M students. All other SEVIS functionality, including event reporting for students, will remain unchanged until the school's SEVIS access termination date. The school must continue to comply with the recordkeeping, retention, reporting and other requirements of 8 CFR 214.3(f), (g), (j), (k), and (l) until its SEVIS access termination date. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">SEVIS access termination.</E>
                             In determining the SEVIS access termination date, SEVP will consider the impact that such date will have upon SEVP, the school, and the school's nonimmigrant students in determining the SEVIS access termination date. In most situations, SEVP will not determine a SEVIS access termination date for that school until the appeals 
                            <PRTPAGE P="55704"/>
                            process has concluded and the initial denial or withdrawal has been upheld unless a school whose certification is withdrawn or whose recertification is denied is suspected of criminal activity or poses a potential national security threat. The school will no longer be able to access SEVIS, and SEVP will automatically terminate any remaining Active SEVIS records for that school on the SEVIS access termination date. 
                        </P>
                        <P>
                            (3) 
                            <E T="03">Legal obligations and ramifications for a school and its DSOs when a school is having SEVP certification denied or withdrawn.</E>
                             Schools are obligated to their students to provide the programs of study to which they have committed themselves in the students' application for enrollment and acceptance process. Schools are obligated to the U.S. government to comply with the recordkeeping, retention, reporting and other requirements contained in 8 CFR 214.3. With any new petition for SEVP certification, SEVP will consider the extent to which a school has fulfilled these obligations to students and the U.S. government during any previous period of SEVP certification. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="8" PART="214">
                    <AMDPAR>6. Section 214.13 is amended by revising paragraphs (a) and (b)(1), to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 214.13 </SECTNO>
                        <SUBJECT>SEVIS fee for certain F, J, and M nonimmigrants. </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Applicability.</E>
                             The following aliens are required to submit a payment in the amount indicated for their status to the Student and Exchange Visitor Program (SEVP) in advance of obtaining nonimmigrant status as an F or M student or J exchange visitor, in addition to any other applicable fees, except as otherwise provided for in this section: 
                        </P>
                        <P>(1) An alien who applies for F-1 or F-3 status in order to enroll in a program of study at an SEVP-certified institution of higher education, as defined in section 101(a) of the Higher Education Act of 1965, as amended, or in a program of study at any other SEVP-certified academic or language-training institution including private elementary and secondary schools and public secondary schools, the amount of $200; </P>
                        <P>(2) An alien who applies for J-1 status in order to commence participation in an exchange visitor program designated by the Department of State (DoS), the amount of $180, with a reduced fee for certain exchange visitor categories as provided in paragraphs (b)(1) and (c) of this section; and </P>
                        <P>(3) An alien who applies for M-1 or M-3 status in order to enroll in a program of study at an SEVP-certified vocational educational institution, including a flight school, in the amount of $200. </P>
                        <P>
                            (b) 
                            <E T="03">Aliens not subject to a fee.</E>
                             No SEVIS fee is required with respect to: 
                        </P>
                        <P>(1) A J-1 exchange visitor who is coming to the United States as a participant in an exchange visitor program sponsored by the Federal government, identified by a program identifier designation prefix of G-1, G-2, G-3, or G-7; </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>Michael Chertoff, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22786 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 9111-28-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Office of the Comptroller of the Currency </SUBAGY>
                <CFR>12 CFR Part 3 </CFR>
                <DEPDOC>[Docket ID OCC-2008-0015] </DEPDOC>
                <RIN>RIN 1557-AD15 </RIN>
                <SUBJECT>Risk-Based Capital Guidelines—Money Market Mutual Funds </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Comptroller of the Currency, Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim final rule with request for public comment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>To reduce liquidity and other strains being experienced by money market mutual funds, the Board of Governors of the Federal Reserve System adopted on September 19, 2008, a special lending facility that enables depository institutions and bank holding companies to borrow from the Federal Reserve Bank of Boston on a nonrecourse basis if they use the proceeds of the loan to purchase certain types of asset-backed commercial paper (ABCP) from money market mutual funds. This lending facility is referenced to as the ABCP Lending Facility. To facilitate the ability of national banks to participate in the program, the Office of the Comptroller of the Currency (OCC) has adopted, on an interim final basis, an exemption from its risk-based capital guidelines for ABCP held by a national bank as a result of its participation in this program. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This interim final rule is effective on September 19, 2008. However, comments must be received on or before October 31, 2008. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Because paper mail in the Washington, DC area and at the OCC is subject to delay, commenters are encouraged to submit comments by e-mail, if possible. Please use the title “Risk-Based Capital Guidelines—Money Market Mutual Funds” to facilitate the organization and distribution of the comments. You may submit comments by any of the following methods: </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal—“Regulations.gov”</E>
                        : Go to 
                        <E T="03">http://www.regulations.gov,</E>
                         under the “More Search Options” tab click next to the “Advanced Docket Search” option where indicated, select “Comptroller of the Currency” from the agency drop-down menu, then click “Submit.” In the “Docket ID” column, select “OCC-2008-0015” to submit or view public comments and to view supporting and related materials for this interim final rule. The “How to Use This Site” link on the Regulations.gov home page provides information on using Regulations.gov, including instructions for submitting or viewing public comments, viewing other supporting and related materials, and viewing the docket after the close of the comment period. 
                    </P>
                    <P>
                        • 
                        <E T="03">E-mail: regs.comments@occ.treas.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Office of the Comptroller of the Currency, 250 E Street, SW., Mail Stop 1-5, Washington, DC 20219. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 874-4448. 
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         250 E Street, SW., Attn: Public Information Room, Mail Stop 1-5, Washington, DC 20219. 
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         You must include “OCC” as the agency name and “Docket ID OCC-2008-0015” in your comment. In general, OCC will enter all comments received into the docket and publish them on the Regulations.gov Web site without change, including any business or personal information that you provide such as name and address information, e-mail addresses, or phone numbers. Comments received, including attachments and other supporting materials, are part of the public record and subject to public disclosure. Do not enclose any information in your comment or supporting materials that you consider confidential or inappropriate for public disclosure. 
                    </P>
                    <P>You may review comments and other related materials that pertain to this interim final rule by any of the following methods: </P>
                    <P>
                        • Viewing Comments Electronically: Go to 
                        <E T="03">http://www.regulations.gov,</E>
                         under the “More Search Options” tab click next to the “Advanced Docket Search” option where indicated, select “Comptroller of the Currency” from the agency drop-down menu, then click “Submit.” In the “Docket ID” column, select “OCC-2008-0015” to view public comments for this rulemaking action. 
                        <PRTPAGE P="55705"/>
                    </P>
                    <P>• Viewing Comments Personally: You may personally inspect and photocopy comments at the OCC's Public Information Room, 250 E Street, SW., Washington, DC. For security reasons, the OCC requires that visitors make an appointment to inspect comments. You may do so by calling (202) 874-5043. Upon arrival, visitors will be required to present valid government-issued photo identification and submit to security screening in order to inspect and photocopy comments. </P>
                    <P>• Docket: You may also view or request available background documents and project summaries using the methods described above. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Margot Schwadron, Senior Risk Expert, (202) 874-6022, Capital Policy Division; Ron Shimabukuro, Senior Counsel; or Hugh Carney, Attorney, Legislative and Regulatory Activities Division, (202) 874-5090; Office of the Comptroller of the Currency, 250 E Street, SW., Washington, DC 20219. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Introduction; Description of Interim Final Rule </HD>
                <P>In light of the ongoing dislocations in the financial markets, and the impact of such dislocations on the functioning of the markets for ABCP and on the operations of money market mutual funds, the Board of Governors of the Federal Reserve System adopted the ABCP Lending Facility on September 19, 2008. Under the ABCP Lending Facility, depository institutions and bank holding companies (banking organizations) are able to borrow from the Federal Reserve Bank of Boston on a nonrecourse basis on condition that the banking organizations use the proceeds of the Federal Reserve credit to purchase, at amortized cost, certain highly rated U.S. dollar-denominated ABCP from money market mutual funds. The ABCP purchased must be used to secure the borrowing from the Reserve Bank. The purpose of the ABCP Lending Facility is to assist money market mutual funds to obtain liquidity by enabling them to sell some of their high-credit-quality secured assets at amortized cost. The ABCP Lending Facility will expire on January 30, 2009. </P>
                <P>
                    National banks that participate in the ABCP Lending Facility must acquire and hold ABCP on their balance sheet. These ABCP holdings attract regulatory capital requirements under the OCC's regulatory capital guidelines and rules.
                    <SU>1</SU>
                    <FTREF/>
                     To facilitate the ABCP Lending Facility, and for the reasons discussed below, the OCC has adopted, on an interim final basis, an exemption from its risk-based capital guidelines for ABCP purchased by a national bank as a result of its participation in the facility. Specifically, the interim final rule amends the OCC's risk-based capital guidelines to permit national banks to assign a zero percent risk weight to ABCP purchased by the national bank as a result of its participation in the facility. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         12 CFR Part 3. 
                    </P>
                </FTNT>
                <P>The OCC has determined that the current risk-based capital requirements for ABCP acquired by a national bank pursuant to the ABCP Lending Facility do not reflect the substantial protections provided to the bank by the Federal Reserve in connection with the facility. Because of the non-recourse nature of the Federal Reserve's credit extension to the banking organization, the bank is not exposed to the credit or market risk of the ABCP purchased by the bank and pledged to the Federal Reserve. Therefore, the OCC believes that it would be appropriate—and consistent with the economic substance of the transactions—not to impose risk-based capital requirements on a national bank that serves as an intermediary in the ABCP Lending Facility. </P>
                <P>Consistent with generally accepted accounting principles, the OCC would expect national banks to report purchased ABCP as an investment security (for example, held-to-maturity). These assets would be reflected at the time of purchase at the national bank's best estimate of fair value. The nonrecourse nature of the transaction would impact the valuation of the liability to the Federal Reserve. After reflecting any appropriate discounts on the assets and associated liabilities, national banks are not expected to report any material net gains or losses at the time of purchase. </P>
                <HD SOURCE="HD1">Effective Date; Solicitation of Comments </HD>
                <P>
                    This interim final rule is effective immediately upon adoption. Pursuant to the Administrative Procedure Act (APA), at 5 U.S.C. 553(b)(B), notice and comment are not required prior to the issuance of a final rule if an agency, for good cause, finds that “notice and public procedure thereon are impracticable, unnecessary, or contrary to the public interest.” 
                    <SU>2</SU>
                    <FTREF/>
                     Similarly, a final rule may be published with an immediate effective date if an agency finds good cause and publishes such with the final rule.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         5 U.S.C. 553(b)(B). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         5 U.S.C. 553(d)(3).
                    </P>
                </FTNT>
                <P>
                    Consistent with section 553(b)(B) of the APA, the OCC finds that good cause exists for a finding that notice and comment is impracticable and contrary to the public interest. As previously described, modification of the risk-based capital guidelines are critical to maintain the orderly functioning of markets and provide market liquidity. Completion of notice and comment rulemaking procedures prior to issuing this interim final rule would delay their implementation. In the current market environment, such a delay is impracticable and inconsistent with the public interest since it may result in undue constraint on national banks' ability to perform critical lending and financial intermediary roles which are necessary for the orderly functioning and liquidity of markets. Issuance of this interim final rule furthers the public interest because it will reduce liquidity and other strains being experienced by money market mutual funds. For the same reasons, the OCC finds good cause to publish this interim final rule with an immediate effective date.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>Although notice and comment are not required prior to the effective date of this interim final rule, the OCC invites comments on all aspects of the rule and will revise it if necessary or appropriate in light of the comments received. </P>
                <HD SOURCE="HD1">Regulatory Analysis </HD>
                <HD SOURCE="HD2">Executive Order 12,866 </HD>
                <P>
                    For the reasons described elsewhere in the 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     the OCC's issuance of this interim final rule is subject to the procedures set forth in Section 6(a)(3)(D) of Executive Order 12,866. 
                </P>
                <HD SOURCE="HD2">Regulatory Flexibility Act </HD>
                <P>
                    The Regulatory Flexibility Act (Pub. L. 96-354, Sept. 19, 1980) (RFA) applies only to rules for which an agency publishes a general notice of proposed rulemaking pursuant to 5 U.S.C. 553(b).
                    <SU>5</SU>
                    <FTREF/>
                     Pursuant to the Administrative Procedure Act (APA) at 5 U.S.C. 553(b)(B), general notice and an opportunity for public comment are not required prior to the issuance of a final rule when an agency, for good cause, finds that “notice and public procedure thereon are impracticable, unnecessary, or contrary to the public interest.” 
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         5 U.S.C. 601(2). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         5 U.S.C. 553(b)(B).
                    </P>
                </FTNT>
                <P>
                    As discussed above, the OCC has determined for good cause that the APA does not require general notice and public comment on this interim final rule and, therefore, we are not publishing a general notice of proposed rulemaking. Thus, the RFA, pursuant to 
                    <PRTPAGE P="55706"/>
                    5 U.S.C. 601(2), does not apply to this interim final rule. 
                </P>
                <HD SOURCE="HD2">Paperwork Reduction Act </HD>
                <P>In accordance with the requirements of the Paperwork Reduction Act of 1995 (44 U.S.C. 3506), we have reviewed the interim final rule to assess any information collections. There are no collections of information as defined by the Paperwork Reduction Act in the interim final rule. </P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act of 1995 </HD>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995, Pub. L. 104-4 (2 U.S.C. 1532) (Unfunded Mandates Act), requires that an agency prepare a budgetary impact statement before promulgating any rule likely to result in a Federal mandate that may result in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year. The OCC has determined that there is no Federal mandate imposed by this rulemaking. Accordingly, the interim final rule is not subject to section 202 of the Unfunded Mandates Act. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 12 CFR Part 3 </HD>
                    <P>Administrative practices and procedure, Capital, National banks, Reporting and recordkeeping requirements, Risk.</P>
                </LSTSUB>
                <REGTEXT TITLE="12" PART="3">
                    <HD SOURCE="HD1">Authority and Issuance </HD>
                    <AMDPAR>For the reasons stated in the preamble, the Office of the Comptroller of the Currency amends Part 3 of chapter I of Title 12, Code of Federal Regulations as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 3—MINIMUM CAPITAL RATIOS; ISSUANCE OF DIRECTIVES </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 3 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>12 U.S.C. 93a, 161, 1818, 1828(n), 1828 note, 1831n note, 1835, 3907, and 3909. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="3">
                    <AMDPAR>2. In Appendix A to part 3, section 3(a)(1) is amended to add new paragraph (ix) to read as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 3—MINIMUM CAPTIAL RATIOS; ISSUANCE OF DIRECTIVES </HD>
                        <APPENDIX>
                            <HD SOURCE="HED">Appendix A to Part 3—Risk-Based Capital Guidelines </HD>
                            <STARS/>
                            <HD SOURCE="HD2">Section 3. Risk Categories/Weights for On-Balance Sheet Assets and Off-Balance Sheet Items </HD>
                            <P>(a) * * * </P>
                            <P>
                                (1) 
                                <E T="03">Zero percent risk weight.</E>
                                 * * * 
                            </P>
                            <P>(ix) Asset-backed commercial paper (ABCP) that is: </P>
                            <P>(A) Purchased by the bank between September 19, 2008, and January 30, 2009 (unless further extended by the OCC), from an Securities and Exchange Commission (SEC)-registered open-end investment company that holds itself out as a money market mutual fund under SEC Rule 2a-7 (17 CFR 270.2a-7); and </P>
                            <P>(B) Pledged by the bank to a Federal Reserve Bank to secure financing from the ABCP lending facility established by the Federal Reserve Board on September 19, 2008. </P>
                            <STARS/>
                              
                        </APPENDIX>
                    </PART>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: September 20, 2008. </DATED>
                    <NAME>John C. Dugan, </NAME>
                    <TITLE>Comptroller of the Currency.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22720 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4810-33-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
                <CFR>12 CFR Parts 208 and 225</CFR>
                <DEPDOC>[Regulations H and Y; Docket No. 1332]</DEPDOC>
                <SUBJECT>Risk-Based Capital Guidelines; Leverage Capital Guidelines</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim final rule with request for public comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>To reduce liquidity and other strains being experienced by money market mutual funds, the Federal Reserve System adopted on September 19, 2008, a special lending facility (ABCP Lending Facility) that enables depository institutions and bank holding companies to borrow from the Federal Reserve Bank of Boston on a nonrecourse basis if they use the proceeds of the loan to purchase certain types of asset-backed commercial paper (ABCP) from money market mutual funds. To facilitate this Federal Reserve lending program, the Board of Governors of the Federal Reserve System (Board) also has adopted, on an interim final basis, an exemption from its leverage and risk-based capital rules for ABCP held by a state member bank or bank holding company as a result of its participation in this program.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The interim final rule became effective on September 19, 2008. Comments must be received on or before October 31, 2008.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by Docket No. R-1332, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Agency Web site: http://www.federalreserve.gov</E>
                         Follow the instructions for submitting comments at 
                        <E T="03">http://www.federalreserve.gov/generalinfo/foia/ProposedRegs.cfm</E>
                        .
                    </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>
                        . Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">E-mail: regs.comments@federalreserve.gov</E>
                        . Include docket number in the subject line of the message.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 452-3819 or (202) 452-3102.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Jennifer J. Johnson, Secretary, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue, NW., Washington, DC 20551.
                    </P>
                    <P>
                        All public comments are available from the Board's Web site at 
                        <E T="03">http://www.federalreserve.gov/generalinfo/foia/ProposedRegs.cfm</E>
                         as submitted, unless modified for technical reasons. Accordingly, your comments will not be edited to remove any identifying or contact information. Public comments may also be viewed electronically or in paper form in Room MP-500 of the Board's Martin Building (20th and C Street, NW) between 9 a.m. and 5 p.m. on weekdays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mark E. Van Der Weide, Assistant General Counsel, (202) 452-2263, or Andrea R. Tokheim, Counsel, (202) 452-2300, Legal Division; Barbara J. Bouchard, Associate Director, (202) 452-3072, or Juan C. Climent, Senior Supervisory Financial Analyst, (202) 872-7526, Division of Banking Supervision and Regulation. For the hearing impaired only, Telecommunication Device for the Deaf (TDD), (202) 263-4869.  </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In light of the ongoing dislocations in the financial markets, and the impact of such dislocations on the functioning of the markets for ABCP and on the operations of money market mutual funds, the Board adopted the ABCP Lending Facility on September 19, 2008. Under the ABCP Lending Facility, depository institutions and bank holding companies (banking organizations) are able to borrow from the Federal Reserve Bank of Boston on a nonrecourse basis on condition that the organizations use the proceeds of the Federal Reserve credit to purchase, at amortized cost, certain highly rated U.S. dollar-denominated ABCP from money market mutual funds. The ABCP purchased must be used to secure the borrowing from the Reserve Bank. The purpose of the ABCP Lending Facility is to assist money market mutual funds to obtain liquidity by enabling them to sell some of their high-credit-quality secured assets at amortized cost. The ABCP Lending Facility will expire on January 
                    <PRTPAGE P="55707"/>
                    30, 2009 (unless further extended by the Board).
                </P>
                <P>Banking organizations that participate in the ABCP Lending Facility must acquire and hold ABCP on their balance sheet. These ABCP holdings attract leverage and risk-based capital charges under the Board's regulatory capital rules for state member banks and bank holding companies. To facilitate the ABCP Lending Facility, and for the reasons discussed below, the Board has adopted, on an interim final basis, an exemption from its leverage and risk-based capital rules for ABCP purchased by a state member bank or bank holding company as a result of its participation in the facility. Specifically, the interim final rule (i) amends the Board's risk-based capital rules for state member banks and bank holding companies to assign a zero percent risk weight to ABCP purchased by the banking organization as a result of its participation in the facility; and (ii) amends the Board's leverage capital rules for state member banks and bank holding companies to permit banking organizations to exclude from average total consolidated assets—the denominator of the leverage ratio—ABCP purchased by the banking organization as a result of its participation in the facility.</P>
                <P>The Board has determined that the current leverage and risk-based capital requirements for ABCP acquired by a banking organization pursuant to the ABCP Lending Facility do not reflect the substantial protections provided to the organization by the Federal Reserve in connection with the facility. Because of the non-recourse nature of the Federal Reserve's credit extension to the banking organization, the organization is not exposed to the credit or market risk of the ABCP purchased by the organization and pledged to the Federal Reserve. Therefore, the Board believes that it would be appropriate—and consistent with the economic substance of the transactions—not to impose regulatory capital requirements on the ABCP purchased by a banking organization in connection with its service as an intermediary in the ABCP Lending Facility.</P>
                <P>Consistent with its purpose to mitigate temporary stresses faced by U.S. money market mutual funds, the interim final rule will expire on January 30, 2009, unless extended by the Board.</P>
                <HD SOURCE="HD1">Administrative Procedure Act</HD>
                <P>Pursuant to sections 553(b) and (d) of the Administrative Procedure Act (5 U.S.C. 553(b) and (d)), the Board finds that there is good cause for making the rule effective immediately on September 19, 2008, and that it is impracticable, unnecessary, or contrary to the public interest to issue a notice of proposed rulemaking and provide an opportunity to comment before the effective date. The Board has adopted the rule in light of, and to help address, the continuing unusual and exigent circumstances in the financial markets. The rule will provide immediate regulatory capital relief to state member banks and bank holding companies that elect to participate in the Federal Reserve's ABCP lending program. The Board is soliciting comment on all aspects of the rule and will make such changes that they consider to be appropriate or necessary after review of any comments received.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>The Regulatory Flexibility Act requires an agency that is issuing a final rule to prepare and make available a regulatory flexibility analysis that describes the impact of the final rule on small entities. 5 U.S.C. 603(a). The Regulatory Flexibility Act provides that an agency is not required to prepare and publish a regulatory flexibility analysis if the agency certifies that the final rule will not have a significant economic impact on a substantial number of small entities. 5 U.S.C. 605(b).</P>
                <P>Pursuant to section 605(b), the Board certifies that this interim final rule will not have a significant economic impact on a substantial number of small entities. The rule reduces regulatory burden on large and small state member banks and bank holding companies by granting an exemption from the leverage and risk-based capital rules for state member banks and bank holding companies that purchase ABCP from money market mutual funds pursuant to the Federal Reserve's ABCP lending program.</P>
                <HD SOURCE="HD1">Paperwork Reduction Act</HD>
                <P>In accordance with the Paperwork Reduction Act (44 U.S.C. 3506; 5 CFR Part 1320 Appendix A.1), the Board has reviewed the interim final rule under authority delegated to the Board by the Office of Management and Budget. The rule contains no collections of information pursuant to the Paperwork Reduction Act.</P>
                <HD SOURCE="HD1">Plain Language</HD>
                <P>Section 722 of the Gramm-Leach-Bliley Act requires the Board to use “plain language” in all proposed and final rules. In light of this requirement, the Board has sought to present the interim final rule in a simple and straightforward manner. The Board invites comment on whether it could take additional steps to make the rule easier to understand.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>12 CFR Part 208</CFR>
                    <P>Confidential business information, Crime, Currency, Federal Reserve System, Mortgages, Reporting and recordkeeping requirements, Securities.</P>
                    <CFR>12 CFR Part 225</CFR>
                    <P>Administrative practice and procedure, Banks, banking, Federal Reserve System, Holding companies, Reporting and recordkeeping requirements, Securities.</P>
                </LSTSUB>
                <REGTEXT TITLE="12" PART="208">
                    <HD SOURCE="HD1">Authority and Issuance</HD>
                    <AMDPAR>For the reasons stated in the preamble, the Board of Governors of the Federal Reserve System amends parts 208 and 225 of chapter II of title 12 of the Code of Federal Regulations as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 208—MEMBERSHIP OF STATE BANKING INSTITUTIONS IN THE FEDERAL RESERVE SYSTEM (REGULATION H)</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 208 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>12 U.S.C. 24, 36, 92a, 93a, 248(a), 248(c), 321-338a, 371d, 461, 481-486, 601, 611, 1814, 1816, 1818, 1820(d)(9), 1823(j), 1828(o), 1831, 1831o, 1831p-1, 1831r-1, 1835a, 1882, 2901-2907, 3105, 3310, 3331-3351, and 3906-3909; 15 U.S.C. 78b, 78l(b), 78l(g), 78l(i), 78o-4(c)(5), 78q, 78q-1, and 78w, 6801, and 6805; 31 U.S.C. 5318; 42 U.S.C. 4012a, 4104a, 4104b, 4106, and 4128.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="208">
                    <AMDPAR>2. In Appendix A to part 208, amend section III.C.1. by adding a new third paragraph to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Appendix A to Part 208—Capital Adequacy Guidelines for State Member Banks: Risk-Based Measure</HD>
                    <EXTRACT>
                        <STARS/>
                        <P>III. * * *</P>
                        <P>C. * * *</P>
                        <P>1. * * *</P>
                        <STARS/>
                        <P>This category also includes ABCP (i) purchased by a bank between September 19, 2008, and January 30, 2009 (unless extended by the Board), from an SEC-registered open-end investment company that holds itself out as a money market mutual fund under SEC Rule 2a-7 (17 CFR 270.2a-7) and (ii) pledged by the bank to a Federal Reserve Bank to secure financing from the ABCP lending facility established by the Board on September 19, 2008.</P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="208">
                    <AMDPAR>
                        3. In Appendix B to part 208, amend section II by adding a new paragraph h to read as follows:
                        <PRTPAGE P="55708"/>
                    </AMDPAR>
                    <HD SOURCE="HD1">Appendix B to Part 208—Capital Adequacy Guidelines for State Member Banks: Tier 1 Leverage Measure</HD>
                    <EXTRACT>
                        <STARS/>
                        <HD SOURCE="HD1">II. * * *</HD>
                        <P>h. Notwithstanding anything in this appendix to the contrary, a bank may deduct from its average total consolidated assets the amount of any asset-backed commercial paper (i) purchased by the bank between September 19, 2008, and January 30, 2009 (unless extended by the Board), from an SEC-registered open-end investment company that holds itself out as a money market mutual fund under SEC Rule 2a-7 (17 CFR 270.2a-7) and (ii) pledged by the bank to a Federal Reserve Bank to secure financing from the ABCP lending facility established by the Board on September 19, 2008.</P>
                    </EXTRACT>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="225">
                    <PART>
                        <HD SOURCE="HED">PART 225—BANK HOLDING COMPANIES AND CHANGE IN BANK CONTROL (REGULATION Y)</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 225 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>12 U.S.C. 1817(j)(13), 1818, 1828(o), 1831i, 1831p-1, 1843(c)(8), 1844(b), 1972(1), 3106, 3108, 3310, 3331-3351, 3907, and 3909; 15 U.S.C. 6801 and 6805.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="208">
                    <AMDPAR>2. In Appendix A to part 225, amend section III.C.1. by adding a new third paragraph to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Appendix A to Part 225—Capital Adequacy Guidelines for Bank Holding Companies: Risk-Based Measure</HD>
                    <EXTRACT>
                        <STARS/>
                        <P>III. * * *</P>
                        <P>C. * * *</P>
                        <P>1. * * *</P>
                        <STARS/>
                        <P>This category also includes ABCP (i) purchased by a bank holding company between September 19, 2008, and January 30, 2009 (unless extended by the Board), from an SEC-registered open-end investment company that holds itself out as a money market mutual fund under SEC Rule 2a-7 (17 CFR 270.2a-7) and (ii) pledged by the bank holding company to a Federal Reserve Bank to secure financing from the ABCP lending facility established by the Board on September 19, 2008.</P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="208">
                    <AMDPAR>3. In Appendix D to part 225, amend section II by adding new paragraph d to read as follows:</AMDPAR>
                    <APPENDIX>
                        <HD SOURCE="HED">Appendix D to Part 225—Capital Adequacy Guidelines for Bank Holding Companies: Tier 1 Leverage Measure</HD>
                        <STARS/>
                        <HD SOURCE="HD1">II. * * *</HD>
                        <P>d. Notwithstanding anything in this appendix to the contrary, a bank holding company may deduct from its average total consolidated assets the amount of any asset-backed commercial paper (i) purchased by the bank holding company between September 19, 2008, and January 30, 2009 (unless extended by the Board), from an SEC-registered open-end investment company that holds itself out as a money market mutual fund under SEC Rule 2a-7 (17 CFR 270.2a-7) and (ii) pledged by the bank holding company to a Federal Reserve Bank to secure financing from the ABCP lending facility established by the Board on September 19, 2008.</P>
                    </APPENDIX>
                </REGTEXT>
                <SIG>
                    <DATED>By order of the Board of Governors of the Federal Reserve System, September 19, 2008.</DATED>
                    <NAME>Jennifer J. Johnson,</NAME>
                    <TITLE>Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22702 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM </AGENCY>
                <CFR>12 CFR Part 223 </CFR>
                <DEPDOC>[Regulation W; Docket No. R-1331] </DEPDOC>
                <SUBJECT>Transactions Between Member Banks and Their Affiliates: Exemption for Certain Purchases of Asset-Backed Commercial Paper by a Member Bank From an Affiliate </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim final rule with request for public comment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>To reduce liquidity and other strains being experienced by money market mutual funds, the Federal Reserve System adopted on September 19, 2008, a special lending facility that enables depository institutions and bank holding companies to borrow from the Federal Reserve Bank of Boston on a non-recourse basis if they use the proceeds of the loan to purchase certain types of asset-backed commercial paper (ABCP) from money market mutual funds (ABCP Lending Facility). To facilitate use of the ABCP Lending Facility by member banks, the Board of Governors of the Federal Reserve System (Board) also has adopted, on an interim final basis, regulatory exemptions for member banks from certain provisions of sections 23A and 23B of the Federal Reserve Act and the Board's Regulation W. The exemptions would increase the capacity of a member bank to purchase ABCP from affiliated money market mutual funds in connection with the ABCP Lending Facility. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The exemption became effective on September 19, 2008. Comments must be received on or before October 31, 2008. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by Docket No. R-1331, by any of the following methods: </P>
                    <P>
                        • 
                        <E T="03">Agency Web Site: http://www.federalreserve.gov</E>
                         Follow the instructions for submitting comments at 
                        <E T="03">http://www.federalreserve.gov/generalinfo/foia/ProposedRegs.cfm.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>
                         Follow the instructions for submitting comments. 
                    </P>
                    <P>
                        • 
                        <E T="03">E-mail: regs.comments@federalreserve.gov.</E>
                         Include docket number in the subject line of the message. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 452-3819 or (202) 452-3102. 
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Jennifer J. Johnson, Secretary, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue, NW., Washington, DC 20551. 
                    </P>
                    <P>
                        All public comments are available from the Board's Web site at 
                        <E T="03">http://www.federalreserve.gov/generalinfo/foia/ProposedRegs.cfm</E>
                         as submitted, unless modified for technical reasons. Accordingly, your comments will not be edited to remove any identifying or contact information. Public comments may also be viewed electronically or in paper form in Room MP-500 of the Board's Martin Building (20th and C Street, NW) between 9 a.m. and 5 p.m. on weekdays. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mark E. Van Der Weide, Assistant General Counsel, (202) 452-2263, or Andrea R. Tokheim, Counsel, (202) 452-2300, Legal Division; or Norah M. Barger, Deputy Director, (202) 452-2402, Division of Banking Supervision and Regulation. For the hearing impaired only, Telecommunication Device for the Deaf (TDD), (202) 263-4869. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In light of the ongoing dislocations in the financial markets, and the impact of such dislocations on the functioning of the ABCP markets and on the operations of money market mutual funds, the Board adopted the ABCP Lending Facility on September 19, 2008. Under the facility, depository institutions and bank holding companies (banking organizations) are able to borrow from the Federal Reserve Bank of Boston on a non-recourse basis on condition that the organizations use the proceeds of the Federal Reserve credit to purchase, at amortized cost, certain highly rated U.S. dollar-denominated ABCP from money market mutual funds. The ABCP purchased must be used to secure the borrowing from the Reserve Bank. The purpose of the ABCP Lending Facility is to assist money market mutual funds to obtain liquidity by enabling them to sell some of their high-credit-quality secured assets at amortized cost. The 
                    <PRTPAGE P="55709"/>
                    ABCP Lending Facility will expire on January 30, 2009 (unless extended by the Board). 
                </P>
                <P>To facilitate usage of the ABCP Lending Facility, the Board has adopted on an interim basis exemptions from sections 23A and 23B of the Federal Reserve Act (12 U.S.C. 371c, 371c-1) and the Board's Regulation W (12 CFR part 223). The exemptions increase the capacity of a member bank to purchase ABCP from an affiliated money market mutual fund in connection with the ABCP Lending Facility. In addition, a member bank may use the exemptions only if the bank has not been specifically informed by the Board, after consultation with the bank's appropriate Federal banking agency, that the bank may not use these exemptions. If the Board believes, after such consultation, that use of the exemptions would not be appropriate for the member bank, the Board may withdraw the exemptions for the bank or may impose supplemental conditions on the bank's use of the exemptions. </P>
                <P>The Board has determined that these exemptions are in the public interest and consistent with the purposes of sections 23A and 23B. The substantial protections provided to intermediaries by the Federal Reserve in connection with the ABCP Lending Facility largely mitigate the safety-and-soundness concerns that sections 23A and 23B were designed to address. Because Federal Reserve extensions of credit to a member bank under the ABCP Lending Facility are on a non-recourse basis, the bank should bear no risk of loss from purchases of ABCP under the facility. Therefore, the Board believes that it is appropriate to exempt a member bank that serves as an intermediary in the ABCP Lending Facility from the requirements of sections 23A and 23B and Regulation W. </P>
                <P>Consistent with its purpose to mitigate temporary stresses faced by money market mutual funds, the interim final rule will expire on January 30, 2009, unless extended by the Board. </P>
                <HD SOURCE="HD1">Administrative Procedure Act </HD>
                <P>Pursuant to sections 553(b) and (d) of the Administrative Procedure Act (5 U.S.C. 553(b) and (d)), the Board finds that there is good cause for making the rule effective immediately on September 19, 2008, and that it is impracticable, unnecessary, or contrary to the public interest to issue a notice of proposed rulemaking and provide an opportunity to comment before the effective date. The Board has adopted the rule in light of, and to help address, the continuing unusual and exigent circumstances in the financial markets. The rule will provide immediate relief to depository institutions that elect to participate in the ABCP Lending Facility. The Board is soliciting comment on all aspects of the rule and will make any changes that it considers appropriate or necessary after review of any comments received. </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                <P>The Regulatory Flexibility Act requires an agency that is issuing a final rule to prepare and make available a regulatory flexibility analysis that describes the impact of the final rule on small entities. 5 U.S.C. 603(a). The Regulatory Flexibility Act provides that an agency is not required to prepare and publish a regulatory flexibility analysis if the agency certifies that the final rule will not have a significant economic impact on a substantial number of small entities. 5 U.S.C. 605(b). </P>
                <P>Pursuant to section 605(b), the Board certifies that this interim final rule will not have a significant economic impact on a substantial number of small entities. The rule reduces regulatory burden on large and small insured depository institutions by granting exemptions from the Federal transactions with affiliates regime for insured depository institutions that purchase ABCP from affiliated money market mutual funds pursuant to the ABCP Lending Facility. </P>
                <HD SOURCE="HD1">Paperwork Reduction Act </HD>
                <P>In accordance with the Paperwork Reduction Act (44 U.S.C. 3506; 5 CFR Part 1320 Appendix A.1), the Board has reviewed the interim final rule under authority delegated to the Board by the Office of Management and Budget. The rule contains no collections of information pursuant to the Paperwork Reduction Act. </P>
                <HD SOURCE="HD1">Plain Language </HD>
                <P>Section 722 of the Gramm-Leach-Bliley Act requires the Board to use “plain language” in all proposed and final rules. In light of this requirement, the Board has sought to present the interim final rule in a simple and straightforward manner. The Board invites comment on whether it could take additional steps to make the rule easier to understand. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 12 CFR Part 223 </HD>
                    <P>Banks, Banking, Federal Reserve System.</P>
                </LSTSUB>
                <REGTEXT TITLE="12" PART="223">
                    <HD SOURCE="HD1">Authority and Issuance </HD>
                    <AMDPAR>For the reasons set forth in the preamble, the Board amends Chapter II of Title 12 of the Code of Federal Regulations as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 223—TRANSACTIONS BETWEEN MEMBER BANKS AND THEIR AFFILIATES (REGULATION W) </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 223 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>12 U.S.C. 371c and 371c-1. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="223">
                    <AMDPAR>2. In § 223.42, add paragraph (o) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 223.42 </SECTNO>
                        <SUBJECT>What covered transactions are exempt from the quantitative limits, collateral requirements, and low-quality asset prohibition? </SUBJECT>
                        <STARS/>
                        <P>
                            (o) 
                            <E T="03">Purchases of certain asset-backed commercial paper.</E>
                             Purchases of asset-backed commercial paper from an affiliated SEC-registered open-end investment company that holds itself out as a money market mutual fund under SEC Rule 2a-7 (17 CFR 270.2a-7), if the member bank: 
                        </P>
                        <P>(1) Purchases the asset-backed commercial paper between September 19, 2008, and January 30, 2009 (unless extended by the Board), pursuant to the asset-backed commercial paper lending facility established by the Board on September 19, 2008; and </P>
                        <P>(2) Has not been specifically informed by the Board, after consultation with the member bank's appropriate Federal banking agency, that the member bank may not use this exemption. </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="223">
                    <AMDPAR>3. Add a new § 223.56 to subpart F to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 223.56 </SECTNO>
                        <SUBJECT>What transactions are exempt from the market-terms requirement of section 23B? </SUBJECT>
                        <P>The following transactions are exempt from the market-terms requirement of § 223.51. </P>
                        <P>
                            (a) 
                            <E T="03">Purchases of certain asset-backed commercial paper.</E>
                             Purchases of asset-backed commercial paper from an affiliated SEC-registered open-end investment company that holds itself out as a money market mutual fund under SEC Rule 2a-7 (17 CFR 270.2a-7), if the member bank: 
                        </P>
                        <P>(1) Purchases the asset-backed commercial paper between September 19, 2008, and January 30, 2009 (unless extended by the Board), pursuant to the asset-backed commercial paper lending facility established by the Board on September 19, 2008; and </P>
                        <P>(2) Has not been specifically informed by the Board, after consultation with the member bank's appropriate Federal banking agency, that the member bank may not use this exemption. </P>
                        <P>(b) [Reserved]</P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <PRTPAGE P="55710"/>
                    <DATED>By order of the Board of Governors of the Federal Reserve System, September 19, 2008. </DATED>
                    <NAME>Jennifer J. Johnson, </NAME>
                    <TITLE>Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22701 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6210-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL HOUSING FINANCE BOARD </AGENCY>
                <CFR>12 CFR Part 915 </CFR>
                <AGENCY TYPE="O">FEDERAL HOUSING FINANCE AGENCY </AGENCY>
                <CFR>12 CFR Part 1261 </CFR>
                <RIN>RIN 2590-AA03 </RIN>
                <SUBJECT>Federal Home Loan Bank Boards of Directors: Eligibility and Elections </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCIES:</HD>
                    <P>Federal Housing Finance Board; Federal Housing Finance Agency. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim final rule with request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Housing Finance Agency (FHFA) is issuing and seeking comment on an interim final regulation to implement section 1202 of the Housing and Economic Recovery Act of 2008, which revises section 7 of the Federal Home Loan Bank Act (Bank Act). Section 7 governs the eligibility and election of individuals to serve on the boards of directors of the 12 Federal Home Loan Banks (Banks). </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This interim final rule is effective on September 26, 2008. The FHFA will accept written comments on the interim final rule on or before November 25, 2008. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments to the FHFA using any 
                        <E T="03">one</E>
                         of the following methods: 
                    </P>
                    <P>
                        E-mail: 
                        <E T="03">comments@fhfb.gov.</E>
                         Please include RIN 2590-AA03 in the subject line of the message. 
                    </P>
                    <P>
                        <E T="03">Fax:</E>
                         202-408-2580. 
                    </P>
                    <P>
                        <E T="03">Mail/Hand Delivery:</E>
                         Federal Housing Finance Board, 1625 Eye Street, NW., Washington DC 20006, Attention: Public Comments/RIN 2590-AA03. 
                    </P>
                    <P>
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments. If you submit your comment to the Federal eRulemaking Portal, please also send it by e-mail to the FHFA at 
                        <E T="03">comments@fhfb.gov</E>
                         to ensure timely receipt by the FHFA. Include the following information in the subject line of your submission: Federal Housing Finance Agency. Interim Final Rule: Federal Home Loan Bank Boards of Directors: Eligibility and Elections. RIN Number 2590-AA03. 
                    </P>
                    <P>
                        We will post all public comments we receive without change, including any personal information you provide, such as your name and address, on the FHFA Web site at 
                        <E T="03">http://www.fhfb.gov/Default.aspx?Page=93&amp;Top=93.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Thomas P. Jennings, Senior Attorney Advisor (FHFB), 
                        <E T="03">jenningst@fhfb.gov,</E>
                         (202) 408-2553; or Patricia L. Sweeney, Management Analyst (FHFB), 
                        <E T="03">sweeneyp@fhfb.gov</E>
                         or (202) 408-2872. You can send regular mail to the Federal Housing Finance Board, 1625 Eye Street, NW., Washington DC 20006. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Statutory and Regulatory Background </HD>
                <P>Effective July 30, 2008, the Federal Housing Finance Regulatory Reform Act of 2008 (Act), Division A of the Housing and Economic Recovery Act of 2008, Public Law No. 110-289, 122 Stat. 2654 (2008), transferred the supervisory and oversight responsibilities of the Office of Federal Housing Enterprise Oversight and the Federal Housing Finance Board over the Federal National Mortgage Association (Fannie Mae), Federal Home Loan Mortgage Corporation (Freddie Mac) (collectively, Enterprises), and the Banks to a new independent executive branch agency known as the Federal Housing Finance Agency (FHFA). The FHFA is responsible for ensuring that the Enterprises and the Banks operate in a safe and sound manner, including being capitalized adequately, and carry out their public policy missions, including fostering liquid, efficient, competitive, and resilient national housing finance markets. The Enterprises and the Banks continue to operate under regulations promulgated by OFHEO and the FHFB until the FHFA issues its own regulations. </P>
                <P>Section 1101 of the Act revised section 7 of the Bank Act. 12 U.S.C. 1427. The FHFB regulation implementing section 7 is codified at 12 CFR part 915. Part 915 governed the nomination and election only of those directors who are chosen from among the officers and directors of members of the Banks, which this interim final rule refers to as member directors. The Act amended section 7(b) of the Bank Act, 12 U.S.C. 1427(b), to give the members the right to also elect all of the other directors on the boards of directors of the Banks, which other directors are referred to in this interim final rule as independent directors. The FHFA has kept the basic process of elections that exists in part 915 as it applies to member directorships, making changes as necessary to comply with the amendments to section 7 of the Bank Act. The FHFA has added provisions to govern the process for nominating individuals for independent directorships and for conducting the election of independent directors in conjunction with the election of member directors. The organizational structure of part 915 also has been revised. </P>
                <P>
                    Section 1201 of the Act (
                    <E T="03">codified at</E>
                     12 U.S.C. 4513(f)) requires the Director of the FHFA to consider the differences between the Banks and the Enterprises in rulemakings that affect the Banks with respect to the Banks' cooperative ownership structure, mission of providing liquidity to members, affordable housing and community development mission, capital structure, and joint and several liability. In preparing the interim final rule, the Director considered these factors and determined that the rule is appropriate, particularly because this interim final rule implements a statutory provision of the Bank Act that applies only to the Banks. 
                    <E T="03">See</E>
                     12 U.S.C. 1427. 
                </P>
                <HD SOURCE="HD1">II. Description of the Interim Final Rule </HD>
                <P>The interim final regulation removes part 915 of the FHFB regulations and establishes part 1261 of the FHFA regulations, which will contain the rules governing the eligibility and election of Bank directors. The name of new part 1261 will read “Federal Home Loan Bank Director Eligibility and Elections.” </P>
                <HD SOURCE="HD2">A. Definitions: Section 1261.1 </HD>
                <P>The FHFA has made technical changes to the definitions of “bona fide resident,” “guaranteed directorship,” “stock directorship,” and “voting state,” but their meanings remain the same as they were in part 915. The meaning of “record date” has not changed. The identification number for the Banks is the same, except that it is now the number assigned by the FHFA. </P>
                <P>The Act's amendments to section 7 of the Bank Act, 12 U.S.C. 1427, divide the directorships of the Banks into two categories—member directorships and independent directorships. Both types of directorships are filled by a vote of the members; however, elections for member directors are held on a state-by-state basis, whereas independent directors are elected at large by all the members of a Bank without regard to whether the members located in a particular voting state may be voting on member directors in any particular year. The definitions of “independent directorship” and “member directorship” reflect that difference. </P>
                <P>
                    The definitions of “guaranteed directorship” and “stock directorship” 
                    <PRTPAGE P="55711"/>
                    reflect that there are two categories of member directorships, because section 7(c) of the Bank Act, 12 U.S.C. 1417(c), guarantees that directorships from members located in some states will be no fewer than the number that existed on December 31, 1960, regardless of the amount of voting stock located in those states. The definition of “public interest directorship” reflects the statutory criteria that an independent director must have in order to receive this designation. 
                </P>
                <P>Section 7(c) of the Bank Act, 12 U.S.C. 1427(c), requires the Director of the FHFA to determine the number of member directorships based on the approximate ratio of required stock held by members located in particular states in a Bank's geographic region. The method the FHFA uses is defined in this section as the “method of equal proportions.” </P>
                <HD SOURCE="HD2">B. General Provisions: Section 1261.2 </HD>
                <P>Section 7(a) of the Bank Act, 12 U.S.C. 1427(a), sets the size of a Bank's board of directors at 13, or such other number as the Director may determine, provided the member directorships always maintain a majority and the independent directorships comprise at least 40 percent of the entire board. Section 1261.2(a) provides that the FHFA Director annually will set the number of directorships for each Bank, and will designate the directorships as either member directorships or independent directorships. The rule does not provide that the Director will designate the independent directorships as either public interest directorships or other independent directorships. If the Director does not further designate the independent directorships, the board of directors of a Bank will have the power, through the nomination process, to nominate any number of the independent directorships as public interest directorships, provided it so designates at least two of the independent directorships. The FHFA requests comments on whether the boards of the Banks or the FHFA Director should establish the number of public interest directorships. </P>
                <P>Section 7(c) of the Bank Act, 12 U.S.C. 1427(c), continues to require that states be grandfathered with the number of directorships representing members in the states on December 31, 1960, notwithstanding any other provision in section 7. Thus, in applying the grandfather provision to the Banks based on their current districts, notwithstanding the Act's apparent default board size of 13, every Bank must have a minimum of 14 directorships, 8 of which must be member directorships. The Act amends section 7(d) of the Bank Act, 12 U.S.C. 1427(d), to require that the term of office of directors elected after July 30, 2008 be four years, except that the FHFA has to adjust terms to achieve an approximately equal staggering of the years for the election of the members of the board of directors of a Bank. Section 1261.2(b) addresses this requirement. The Act also amends the Bank Act to require that existing directorships that do not expire on December 31, 2008 continue their existing terms, so the FHFA has to adjust the terms of new directorships beginning January 1, 2009 in order to achieve staggering. </P>
                <P>Section 1261.2(c) carries forward the requirement in section 915.3(a) that the Banks are responsible for conducting annual elections. Section 1261.2(d) and (e) are based on the sections 915.3(d) and 915.2, respectively, of the FHFB rule. </P>
                <HD SOURCE="HD2">C. Designation of Member Directorships: Section 1261.3 </HD>
                <P>Section 1261.3(a) continues the requirement in section 915.4 of the FHFB rule that each Bank must submit a capital report. The FHFA will rely on this information to designate stock directorships among the voting states in a Bank's district. Each Bank also must notify each of its members of its minimum required stock holdings. Section 1261.3(a)(2) applies only to the Chicago Bank, whose capital plan is not yet in effect. </P>
                <P>Section 1261.3(b) and (c) of the interim final rule carry forward the requirements of section 915.3(b) of the FHFB regulations. Section 1261.3(b) specifies the methodology by which the FHFA will make the allocation of member directorships, and section 1261.3(c) provides that the FHFA will follow the requirements in sections 7(b) and (c) of the Bank Act in designating member directorships to the states. Annually, the FHFA will use the method of equal proportions to determine how member directorships should be divided among the states in a Bank's district, based on the stock holdings of the members located in each state in the Bank's district. The FHFA's annual allocation to each state will be sufficient to meet the requirement in section 7(c) of the Bank Act that the number of member directorships in each state be equal to the number of elective directorships that it had on December 31, 1960 (the guaranteed directorships). </P>
                <P>The effect of the so-called “grandfather” provision is that, based on the present geographic districts of the Banks, each Bank will have a minimum of eight member directorships. Section 1261.3(c) recognizes that some existing directorships at a Bank may cease to exist if, resulting from the Director's annual designation, the number of directors is set at a number below the size of the existing board, the number of member directorships increases and the number of independent directorships decreases, or vice versa, or the application of the method of equal proportions causes any state to lose a directorship to another state. If a state loses a directorship through any of these events, section 1261.3(c) provides that the director sitting in that directorship shall be ineligible to serve after December 31 of that year. </P>
                <P>Section 1261.3(d) continues the notification provision in section 915.3(e) of the FHFB rule. </P>
                <HD SOURCE="HD2">D. Director Eligibility: Section 1261.4 </HD>
                <P>Section 1261.4(a) carries forward section 915.7(b) of the FHFB rule regarding the eligibility requirements of member directors. Section 1261.4(b) sets forth the eligibility requirements of independent directors in section 7(a) of the Bank Act. </P>
                <P>Section 1261.4(c) describes situations in which otherwise eligible individuals would not be eligible to serve. The term limit provisions of section 7(d) of the Bank Act limit service of individuals who have served all or part of three consecutive full terms. Such individuals are ineligible for the two years following such service. For terms beginning after the effective date of the Act, section 1261.4(c) deems only four year terms to be full terms. The existing directorships that do not end on December 31, 2008, have three year terms, and those directorships' terms are full terms. If the FHFA creates shorter than four year terms for directorships that begin on or after January 1, 2009, to effectively stagger the directorships, those shorter terms will not be deemed to be full terms. Nonetheless, such shorter terms will not be effective for purposes of creating a break in service or avoiding the three consecutive term count. In other words, serving in three consecutive three year elective directorships ending December 31, 2008 will render an individual ineligible to serve a shortened term beginning January 1, 2009, and serving in one or two three year elective directorships ending December 31, 2008, a shortened term beginning January 1, 2009, and one or two four year terms immediately thereafter, for a total of three full terms, will render an individual ineligible to again serve for two more years. </P>
                <P>
                    The FHFA seeks comment on its application of the consecutive full-term 
                    <PRTPAGE P="55712"/>
                    limitation in section 7(d) of the Bank Act. If a director serves in a term which met the Bank Act's requirement of a full term at the time the director assumed that directorship, no matter how long the term is, should that term be considered a full term? Should the current terms and any prior terms consecutive thereto of directors elected prior to July 30, 2008, be deemed to be full terms for purposes of the three consecutive term rule in section 7(d) of the Bank Act? Should the full terms of the directors appointed by the Finance Board be treated any differently from how the terms of elective directors are treated? Should the shorter term that the FHFA creates for purposes of staggering be considered a break between terms before and after other terms of service, for purposes of treating the other terms as consecutive full terms? 
                </P>
                <P>Section 1261.4(d) deems a sitting director to be ineligible on December 31 of the year in which that person's directorship is eliminated or redesignated to another state through the annual allocation under the method of equal proportions. The FHFA is required to do an annual allocation, and changes in member stock ownership on a state-by-state basis may cause a state to lose one or more directorships. Although an individual may have to give up a directorship due to reallocation or elimination, if the individual does not complete a full term due to such action, that term will not count as a full term for purposes of eligibility. </P>
                <HD SOURCE="HD2">E. Determination of Member Votes: Section 1261.5 </HD>
                <P>Section 1261.5 carries forward section 915.5 of the FHFB rule, which sets forth how the Banks must determine the number of votes of each member. For those Banks that have more than one class of stock, the Banks are required to calculate the average number of shares separately for each class and allow each member to vote its combined average number of shares. The average for each class is calculated based on the total number of members in each state, even if a member holds no shares in a class of stock. The number of votes allocated to a member is the number of votes that the member may vote for any directorship, whether it is a member directorship, independent public interest directorship, or other independent directorship. </P>
                <HD SOURCE="HD2">F. Nominations for Member and Independent Directorships: Section 1261.6</HD>
                <P>Section 915.6 of the FHFB regulation set forth the requirements for member directorship nominations. Section 1261.6 carries forth these requirements with some modifications and sets forth how the Banks will nominate independent directorship candidates. Banks are not required to do so in any particular mode of communication, so long as they can demonstrate to the FHFA their compliance with the regulations. </P>
                <P>As required by section 1261.6(a) of the interim final rule, the Banks must provide to each member a notice of the commencement of the election process in a reasonable time in advance of the elections. As to member directorships, the notice and nomination procedures do not differ significantly from the procedures set forth in the FHFB regulation. </P>
                <P>As to independent directorships, section 7 of the Bank Act requires each Bank to nominate candidates, and the election from among the candidates is the right of the members of each Bank. Under section 1261.6(d) of the interim final rule, a Bank must consider anyone who applies using an application form prescribed by the FHFA and indicates on the form that s/he meets the eligibility requirements set forth in section 1261.4(b), provided the application form is delivered to the Bank by a deadline set by the Bank and the application form contains any of the qualifications for independent directors set forth in that section. Independent directors may meet either the requirements of public interest directors or the requirements set forth in section 1261.6(e). </P>
                <P>Section 1261.6(d) also requires that a Bank's board of directors consult with the Bank's Advisory Council before nominating independent directors. The FHFA requests comment on whether it should require the Advisory Council to play any specific role in the consultation process and whether the FHFA should prescribe procedures on how the consultation should take place. </P>
                <P>Section 7(a) of the Bank Act and section 1261.6(d) of the interim final rule require that public interest directors have more than four years experience in representing consumer or community interests in banking services, credit needs, housing, or consumer financial protections. Prior to the Act's amendments to section 7(a), a public interest director had to be from an organization that had a history of more than two years representing consumer or community interests, but the individual did not necessarily have to have personal experience doing so. Although the FHFA will impose the Act's requirements on newly chosen independent directors, the FHFA will deem existing public interest directors who qualified and were designated as public interest directors under the Bank Act before it was amended to be public interest directors for the remainder of their existing terms. </P>
                <P>The FHFA requests comments on whether it should apply the revised experience requirements to existing public interest directors and, if so, whether it should require any Bank that does not have two public interest directors who meet the revised requirements to nominate candidates who do meet those requirements. </P>
                <P>Section 1261.6(d)(3) requires the Banks to establish the number of public interest directorships from among the number of independent directorships established by the FHFA Director pursuant to section 1261.3(c). It requires the Banks to have at least two public interest directors, as required by section 7(a) of the Bank Act. The boards of directors of the Banks must nominate at least as many individuals for public interest directorships as there are positions available. Any board may nominate more individuals for public interest directorship positions than there are positions to be filled; however, the Bank may fill only those vacant positions that the board has designated as public interest directorships with public interest director nominees. </P>
                <P>The rule permits a board of directors to have only enough nominees to fill the vacant positions, because the board of directors of a Bank might determine that the most highly qualified candidates may not apply unless they are assured of a seat after having been nominated. The FHFA requests comment on whether the board of directors of a Bank should be required to nominate more candidates for independent directorships than there are positions to be filled, if the board has determined that there are sufficient applicants who are both eligible and qualified. </P>
                <P>
                    Section 7(a) of the Bank Act sets forth specific qualifications that independent directors, other than public interest directors, must have, and it authorizes the FHFA Director to establish other knowledge or experience that an independent director may have in lieu of the types of knowledge or experience specified in section 7(a). Section 1261.6(e) provides that independent directors may be qualified if they have knowledge or experience in the law, in addition to the statutorily prescribed subjects of auditing or accounting, derivatives, financial management, organizational management, project development or risk management practices. In each case, a candidate's knowledge or experience must be 
                    <PRTPAGE P="55713"/>
                    commensurate with the knowledge or experience needed to oversee a business of the size and complexity of the Bank. The FHFA solicits comment on whether additional areas of expertise should be added to the list. 
                </P>
                <P>Pursuant to section 1261.6(f) of the interim final rule, Banks must verify the eligibility of nominees for directorships before placing their names on the ballots. The FHFA will prescribe eligibility certification forms for member directors, and the Banks must use information on those forms to verify eligibility of nominees for member directorships. The FHFA will prescribe application forms and eligibility certification forms for independent directors. For new nominees for independent directorships, the Banks may use information on the application forms. For incumbent nominees for independent directorships, the Banks may use information on eligibility certification forms or on application forms. As to independent directorship nominees, both incumbent and new nominees, the Banks must deliver the names and contemporaneously executed director application forms of the nominees to the FHFA for its review and comment before the names of any such nominees can be placed on ballots. The FHFA intends to review the information submitted and, whenever it has comments that might aid a Bank, make comments to the Bank's board of directors about how any nominee's qualifications might serve the needs of the Bank. </P>
                <HD SOURCE="HD2">G. Election Process: Section 1261.7</HD>
                <HD SOURCE="HD3">1. Ballots </HD>
                <P>Similar to the current election process conducted by the Banks, the interim final rule requires each Bank to prepare a ballot for each voting state. A Bank may not deliver ballots until after the FHFA has commented on the independent director nominees. Independent director nominees are elected on a district-wide basis, so all states in the district will be voting states in each annual election. The FHFA contemplates that ballots will differ from state to state, because a Bank likely will not include on the ballots in one state the member director nominees for the other states in its district. The ballots must include a closing date for voting, which may not be sooner than 30 days after the ballots are delivered. </P>
                <P>The ballots must contain the type of minimum information on member directorship nominees required in section 915.8 of the FHFB rule. As to independent directorship nominees, the ballots must include information about their qualifications for the type of directorship for which they are nominated. All nominees must be listed alphabetically and separately for each type of directorship for which the election is being held. A Bank may include additional information it deems appropriate, including a description of the skills and experience of the member director nominees. If, pursuant to section 1261.9, a Bank has conducted an assessment of the skills and experience it needs on its board of directors and included that information in its notice required in section 1261.6, or subsequently has revised that assessment, the Bank may include a statement of the most recent version of its assessment with the ballots. The interim final rule also requires the Banks to include on the ballots a statement that write-in candidates are not permitted and a statement that the Bank will not disclose how any member votes its ballot. </P>
                <HD SOURCE="HD3">2. Lack of Member Directorship Nominees </HD>
                <P>In those instances where the number of member nominees is not greater than the number of member directorships to be filled, section 1261.7(c) of the interim final rule requires a Bank to declare the seats filled by the eligible nominees, first filling any guaranteed directorships and then any remaining stock directorships. If any member directorship is not filled, or if the failure to fill any directorship would cause the number of member directors to be fewer than a majority of the directors, then such directorship will become vacant on January 1 of the following year, and the Bank's board of directors at that time may elect an individual to fill the vacancy. </P>
                <HD SOURCE="HD3">3. Voting </HD>
                <P>The interim final rule provides that a member's vote for a nominee is deemed a vote in the amount of all the stock that the member is required to hold as of the record date. A member may not vote more than the amount of its required stock for any one nominee, no matter how many directorships are being filled by the election. A member may vote for as many nominees as there are directorships being filled by the election, but a member may vote only one time for any one nominee. A member may vote at any time up until the closing date, by which time it must have delivered its ballot to the Bank. </P>
                <HD SOURCE="HD3">4. Declaring Results </HD>
                <P>Section 1261.7(f) of the interim final rule provides that the individual receiving the highest number of votes is declared the winner of a member directorship. If other member directorships are being filled, the individual receiving the next highest number of votes also will be declared a winner, and so on down the line. The same rule applies to each type of independent directorship, except that a nominee who receives fewer than 20 percent of the number of votes eligible to be cast may not be declared a winner. If, for the last available directorship of any type, there is a tie vote, and for an independent directorship the tie vote is at least 20 percent of the eligible votes, then the disinterested members of the Bank's board of directors by majority vote will determine the winner. At the time of declaring winners and at the time any director is seated, a Bank may not have any reason to know that such director is ineligible to serve. </P>
                <P>The FHFA requests comment on whether the rule should continue to require that independent directors must receive at least a minimum percentage of votes cast in order to be elected and, if so, what that minimum should be. The FHFA believes that receiving at least a minimum percentage of votes affirms that the candidate is the choice of the members, even when the number of candidates does not exceed the number of directorships to be filled. If there is a minimum percentage, should it be based on the number of shares actually voting or on the number of shares eligible to vote? </P>
                <HD SOURCE="HD3">5. Report of Election </HD>
                <P>Section 1261.7(g) of the interim final rule requires each Bank to promptly report to its members, each nominee, and the FHFA on the results of an election. The report must contain the number of voting members, the number of votes cast, and the number of votes received by each nominee. As to each member director-elect, the Bank must provide the same information required in section 915.8(e) or the FHFB rule. As to each public interest director, the Bank must provide the consumer or community interest represented and the expiration date of the term of office. For each other independent director-elect, the Bank must provide the individual's qualifications under section 1261.6(e) and the expiration date of the term of office. </P>
                <HD SOURCE="HD3">6. Failing To Fill All Independent Directorships </HD>
                <P>
                    If any independent directorship is not filled for failure to receive 20 percent of the eligible votes, section 1261.7(h) of the interim final rule requires a Bank to conduct another election for such directorship, following the same 
                    <PRTPAGE P="55714"/>
                    procedures required for the initial election. The Bank must continue repeated election procedures until the directorship is filled by a vote of 20 percent of the votes eligible to be voted. The eligible votes remain the same for each such repeat election. 
                </P>
                <HD SOURCE="HD2">H. Section 1261.8 Is Reserved for Future Use </HD>
                <HD SOURCE="HD2">I. Action Affecting Director Elections: Section 1261.9</HD>
                <P>Section 1261.9(a) of the interim final rule continues the authorization to a Bank's board of directors to conduct an annual assessment of the skills and experience needed on a Bank's board of directors, as provided in section 915.9(a) of the FHFB rule. If such an assessment identifies particular skills or experience needed on the board, a Bank may inform its members of those needs in its notice of elections. </P>
                <P>Section 1261.9(b) of the interim final rule authorizes a Bank and any of its directors, officers, attorneys, employees, and agents, including the Bank's board of directors and Advisory Council, to support any individual for nomination and election to an independent directorship. Such individuals, if acting in their personal capacity, are not prohibited from supporting the nomination or election of any individual for a member directorship. The distinction between member directorships and independent directorships is that the Bank's board of directors nominates individuals for independent directorships, and support of the Bank's nominees could benefit the Bank without discriminating against any member. </P>
                <P>Except as allowed under section 1261.9(a) and (b), no director, officer, employee, attorney, or agent of a Bank may support or oppose the nomination or election of any individual for any directorship of the Bank, or take any other action to influence the voting for or against any such individual. </P>
                <P>The FHFA seeks comment on whether it is appropriate to distinguish between member and independent directors when establishing prohibitions on actions that might influence others with respect to any director. Comment also is sought on whether there are other issues that the FHFA should address in this section. </P>
                <HD SOURCE="HD2">J. Independent Director Conflict of Interests: Section 1261.10</HD>
                <P>Section 7(a) of the Bank Act prohibits an independent director from serving as an officer of any Bank and from serving as a director, officer, or employee of any member of the Bank on whose board the director sits, or of any recipient of any advances from that Bank. Section 1261.10 of the interim final rule sets forth this prohibition and requires any nominee for, and incumbent holding, an independent directorship to disclose such interests. Positions held in a holding company that controls any member or any recipient of advances, are attributed to any member or recipient of advances if the assets of all members or recipients of advances under the control of the holding company equal at least 35 percent of the assets of the holding company. Positions in any other subsidiary or affiliate of the holding company are not attributed to the member or recipient of advances. Positions held by an individual's spouse are attributed to the individual. </P>
                <P>The FHA seeks comment on whether the holding company attribution rule should be set at a number other than 35 percent. </P>
                <HD SOURCE="HD2">K. Conflict of Interests Policy for Bank Directors: Section 1261.11</HD>
                <P>Section 1261.11(a) of the interim final rule revises and restates the requirement in section 915.11 of the FHFB rule that Banks adopt a conflicts of interest policy to apply to the members of their boards of directors. The rule sets forth the minimum contents of such a policy. One requirement is that the policy must require the board of directors to administer the affairs of the Bank fairly and impartially, without discriminating in favor of or against any member. The rule does not address nonmember borrowers specifically, but the absence of any reference to nonmember borrowers does not prohibit a Bank from addressing conflicts of interests with respect to nonmember borrowers. </P>
                <P>Section 1261.11(b) of the interim final rule requires any director of a Bank to disclose fully to the board of directors of the Bank any financial interest that the director or any immediate family member or business associate has in any business matter or proposed business matter involving the Bank and to refrain from any action in connection with the matter. Section 1261.11(c) requires directors to maintain the confidentiality of confidential information obtained by serving as a director and to refrain from using that information for personal benefit. </P>
                <P>Section 1261.11(d) of the interim final rule prohibits the acceptance of gifts to influence the director's actions as a member of the board of directors of a Bank. A director may not accept a gift, no matter the value, if the director believes, or would have reason to believe, that the gift is given with the intent to influence the director's actions. A director may not accept a gift, no matter the value, if acceptance would have the appearance of the donor's intent to influence the director's actions. Although the prohibition does not prohibit other gifts, the absence of a specific prohibition does not prohibit a Bank from addressing other situations in its conflict of interest policy. </P>
                <P>Section 1261.11(e) of the interim final rule prohibits a director from accepting compensation for service on the board of a Bank from any source other than the Bank. This prohibition does not prohibit any director who is a salaried employee from continuing to receive a salary even when the time that the director devotes to the Bank would otherwise be time devoted to the employer. </P>
                <HD SOURCE="HD2">L. Reporting Requirements for Bank Directors: Section 1261.12</HD>
                <P>Pursuant to section 1261.12(a) of the interim final rule, each sitting director is required to execute an annual eligibility certification form applicable to the directorship held by the director. The form, prescribed by the FHFA for the purpose of identifying any changes since a prior eligibility review, must be executed and delivered to the Bank, and the Bank must deliver a copy to the FHFA. </P>
                <P>Section 1261.12(b) of the interim final rule requires any sitting director of a Bank who believes or has reason to believe that s/he no longer meets the statutory or regulatory eligibility requirements to notify promptly both the Bank and the FHFA. Likewise, any Bank that believes or has reason to believe that any of its directors no longer meets the eligibility requirements must notify the FHFA promptly. </P>
                <HD SOURCE="HD2">M. Ineligible Bank Directors: Section 1261.13 </HD>
                <P>
                    Section 7(f) of the Bank Act, prior to the amendments made by the Act, provided that an appointive directorship would become vacant whenever the director holding that directorship failed to meet the eligibility requirements set forth in the Bank Act, but the director could continue to serve until replaced. The amendments to section 7(f) now require that all directors who fail to meet their statutory eligibility requirements immediately must vacate their offices. Section 1261.13 of the interim final rule applies these results whenever the FHFA or a director's Bank makes a determination that the director has failed to meet any eligibility requirement set forth in the Bank Act or in part 1261 or has failed to comply with the reporting requirements in section 1261.12 of the interim final rule. Section 1261.13 also 
                    <PRTPAGE P="55715"/>
                    requires a Bank to notify the FHFA promptly after it has made such a determination. 
                </P>
                <HD SOURCE="HD2">N. Vacant Bank Directorships: Section 1261.14</HD>
                <P>Section 1261.14(a) of the interim final rule implements the requirements in section 7(f) of the Bank Act that any individual who fills a vacancy on the board of a Bank be elected by a majority vote of the remaining directors. </P>
                <P>Section 1261.14(b) of the interim final rule requires the board of directors of a Bank to fill any vacancy with an individual who meets the eligibility and qualification requirements applicable to any individual who was the predecessor in that position; however, if a Bank continues to have at least two public interest directors, the board of directors of the Bank may fill the vacant directorship with an individual who meets the eligibility and qualification requirements for any independent directorship. The eligibility requirements for both member and independent directors are set forth in section 1261.4 of the interim final rule. The eligibility requirements for independent public interest directors and for other independent directors are the same. The qualification requirements for independent public interest directors and for other independent directors are set forth in section 1261.6 of the interim final rule. The Bank must verify eligibility before allowing any director elected by the board to assume office, and the Bank must deliver the individual's application form to the FHFA for review and comment before the individual is allowed to assume office. </P>
                <P>Section 1261.14(c) of the interim final rule requires a Bank to provide a notice to the FHFA and to each member of the Bank that includes specified information about any individual who has been elected by the directors of the Bank. </P>
                <HD SOURCE="HD2">O. Minimum Number of Member Directorships: Section 1261.15</HD>
                <P>Section 1261.15 designates the grandfathered directorships that apply at the present time to the 12 Banks. The section also provides that the grandfathering of directorships for any two or more Banks that merge does not apply to those Banks that are a part of the merger, as required by an amendment to section 7(c) of the Bank Act. </P>
                <HD SOURCE="HD2">P. 2008 Temporary Schedule for Election of Directors: Section 1261.16</HD>
                <P>Section 1261.16 of the interim final rule requires each Bank to set a reasonable schedule for the nomination and election of directors in 2008 only. </P>
                <P>This temporary director election schedule will cease to be effective after December 31, 2008. </P>
                <HD SOURCE="HD1">III. Notice and Public Participation </HD>
                <P>
                    The notice and comment procedure required by the Administrative Procedure Act is inapplicable to this interim final rule because it is in the public interest to implement the requirements of the Act as soon as it is practicable to do so: The Banks need to conduct elections and install directors in compliance with the new law by January 1, 2009, when a number of terms of existing directors expire. 
                    <E T="03">See</E>
                     5 U.S.C. 553(b)(3)(B). However, because the FHFA believes that public comments are valuable, it encourages comments on this interim final rule, and will consider all comments received on or before November 25, 2008 in promulgating a final rule. 
                </P>
                <HD SOURCE="HD1">IV. Effective Date </HD>
                <P>
                    For the reasons stated in part III above, the FHFA for good cause finds that the interim final rule should become effective on September 26, 2008. 
                    <E T="03">See</E>
                     5 U.S.C. 553(d)(3). 
                </P>
                <HD SOURCE="HD1">V. Paperwork Reduction Act </HD>
                <P>
                    The interim final rule will have no substantive effect on any collection of information covered by the Paperwork Reduction Act of 1995 (PRA). 
                    <E T="03">See</E>
                     44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                     Therefore, the FHFA has not submitted this interim final rule to the Office of Management and Budget (OMB) for review. The Finance Board used application forms to collect information on prospective appointive directors, and those forms had been assigned control number 3069-0002 by the OMB. The FHFA will direct the Banks to use those forms, which will be amended as appropriate but the changes to the forms will not materially modify the approved information collection. Consequently, the FHFA has not submitted any information to OMB for review under the PRA. 
                </P>
                <HD SOURCE="HD1">VI. Regulatory Flexibility Act </HD>
                <P>
                    The FHFA is adopting this regulation in the form of an interim final rule and not as a proposed rule. Therefore, the provisions of the Regulatory Flexibility Act do not apply. 
                    <E T="03">See</E>
                     5 U.S.C. 601(2) and 603(a).
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 12 CFR Parts 915 and 1261 </HD>
                    <P>Banks, Banking, Conflicts of interest, Elections, Ethical conduct, Federal home loan banks, Financial disclosure, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="12" PART="915">
                    <AMDPAR>For the reasons stated in the preamble, under the authority of 12 U.S.C. 1319(G) and 12 U.S.C. 1426, 1427 and 1432, the FHFA proposes to amend chapters IX and XII of title 12 of the Code of Federal Regulations as follows: </AMDPAR>
                    <CHAPTER>
                        <HD SOURCE="HED">CHAPTER IX—FEDERAL HOUSING FINANCE BOARD </HD>
                        <PART>
                            <HD SOURCE="HED">PART 915—BANK DIRECTOR ELIGIBILITY AND ELECTIONS </HD>
                        </PART>
                    </CHAPTER>
                    <AMDPAR>1. Remove 12 CFR part 915.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="915">
                    <CHAPTER>
                        <HD SOURCE="HED">CHAPTER XII—FEDERAL HOUSING FINANCE AGENCY </HD>
                    </CHAPTER>
                    <AMDPAR>2. Add and reserve subchapters A and C to 12 CFR Chapter XII.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="915">
                    <AMDPAR>3. Add subchapter B to 12 CFR chapter XII, and transfer part 1231 to subchapter B. </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="915">
                    <AMDPAR>4. Amend title 12 CFR chapter XII by establishing subchapter D to read as follows:</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="915">
                    <SUBCHAP>
                        <HD SOURCE="HED">Subchapter D—Federal Home Loan Banks </HD>
                    </SUBCHAP>
                    <AMDPAR>5. Add part 1261 to subchapter D to read as follows:</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="1261">
                    <PART>
                        <HD SOURCE="HED">PART 1261—FEDERAL HOME LOAN BANK DIRECTOR ELIGIBILITY AND ELECTIONS </HD>
                        <CONTENTS>
                            <SECHD>Sec.</SECHD>
                            <SECTNO>1261.1 </SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <SECTNO>1261.2 </SECTNO>
                            <SUBJECT>General provisions. </SUBJECT>
                            <SECTNO>1261.3 </SECTNO>
                            <SUBJECT>Designation of member directorships. </SUBJECT>
                            <SECTNO>1261.4 </SECTNO>
                            <SUBJECT>Director eligibility. </SUBJECT>
                            <SECTNO>1261.5 </SECTNO>
                            <SUBJECT>Determination of member votes. </SUBJECT>
                            <SECTNO>1261.6 </SECTNO>
                            <SUBJECT>Nominations for member and independent directorships. </SUBJECT>
                            <SECTNO>1261.7 </SECTNO>
                            <SUBJECT>Election process. </SUBJECT>
                            <SECTNO>1261.8 </SECTNO>
                            <SUBJECT>[Reserved]. </SUBJECT>
                            <SECTNO>1261.9 </SECTNO>
                            <SUBJECT>Actions affecting director elections. </SUBJECT>
                            <SECTNO>1261.10 </SECTNO>
                            <SUBJECT>Independent director conflict of interests. </SUBJECT>
                            <SECTNO>1261.11 </SECTNO>
                            <SUBJECT>Conflict of interests policy for Bank directors. </SUBJECT>
                            <SECTNO>1261.12 </SECTNO>
                            <SUBJECT>Reporting requirements for Bank directors. </SUBJECT>
                            <SECTNO>1261.13 </SECTNO>
                            <SUBJECT>Ineligible Bank directors. </SUBJECT>
                            <SECTNO>1261.14 </SECTNO>
                            <SUBJECT>Vacant Bank directorships </SUBJECT>
                            <SECTNO>1261.15 </SECTNO>
                            <SUBJECT>Minimum number of member directorships. </SUBJECT>
                            <SECTNO>1261.16 </SECTNO>
                            <SUBJECT>Temporary rule for 2008 election of directors.</SUBJECT>
                        </CONTENTS>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>12 U.S.C. 1426, 1427, and 1432. </P>
                        </AUTH>
                        <SECTION>
                            <SECTNO>§ 1261.1 </SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <P>For purposes of this part:</P>
                            <P>
                                <E T="03">Act</E>
                                 means the Federal Home Loan Bank Act, as amended (12 U.S.C. 1421 through 1449).
                            </P>
                            <P>
                                <E T="03">Bank,</E>
                                 written in title case, means a Federal Home Loan Bank established under section 12 of the Act (12 U.S.C. 1432).
                            </P>
                            <P>
                                <E T="03">Bona fide resident</E>
                                 of a Bank district means an individual who:
                                <PRTPAGE P="55716"/>
                            </P>
                            <P>(1) Maintains a principal residence in the Bank district; or </P>
                            <P>(2) If serving as an independent director, owns or leases in his or her own name a residence in the Bank district and is employed in a voting state in the Bank district. </P>
                            <P>
                                <E T="03">Director</E>
                                 means the Director of the Federal Housing Finance Agency. 
                            </P>
                            <P>
                                <E T="03">FHFA</E>
                                 means the Federal Housing Finance Agency. 
                            </P>
                            <P>
                                <E T="03">FHFA ID number</E>
                                 means the number assigned to a member by the FHFA and used by the FHFA and the Banks to identify a particular member. 
                            </P>
                            <P>
                                <E T="03">Guaranteed directorship</E>
                                 means a member directorship that is required by section 7(c) of the Act (12 U.S.C 1427(c)) to be designated as representing Bank members that are located in a particular state, other than a stock directorship. 
                            </P>
                            <P>
                                <E T="03">Independent directorship</E>
                                 means a directorship, as defined by section 7(a)(4)(A) of the Act, 12 U.S.C. 1427(a)(4)(A), that is filled by a plurality vote of the members at large by a person having the qualifications specified by section 7(a)(3)(B)(i) or (ii), 12 U.S.C. 1427(a)(3)(B)(i) or (ii). 
                            </P>
                            <P>
                                <E T="03">Member directorship</E>
                                 means a directorship, as defined by section 7(a)(4)(A) of the Act, 12 U.S.C. 1427(a)(4)(A), that is filled by a plurality vote of the members located in a particular state by a person who is an officer or director of a member located in that state, and includes guaranteed directorships and stock directorships. 
                            </P>
                            <P>
                                <E T="03">Method of equal proportions</E>
                                 means the mathematical formula used by the FHFA to allocate member directorships among the states in a Bank's district based on the relative amounts of Bank stock required to be held as of the record date by members located in each state.
                            </P>
                            <P>
                                <E T="03">Public interest director</E>
                                 means a person serving in a public interest directorship. 
                            </P>
                            <P>
                                <E T="03">Public interest directorship</E>
                                 means an independent directorship filled by an individual with more than four years experience representing consumer or community interests in banking services, credit needs, housing or consumer financial protections.
                            </P>
                            <P>
                                <E T="03">Record date</E>
                                 means December 31 of the calendar year immediately preceding the election year.
                            </P>
                            <P>
                                <E T="03">Stock directorship</E>
                                 means a member directorship that is designated by the FHFA as representing the members located in a particular voting state based on the amount of Bank stock held required to be held by the members in that state as of the record date, other than a guaranteed directorship. 
                            </P>
                            <P>
                                <E T="03">Voting state</E>
                                 means the District of Columbia, Puerto Rico, or the state of the United States in which a member's principal place of business, as determined in accordance with 12 CFR part 925, is located as of the record date. The voting state of a member with a principal place of business located in the U.S. Virgin Islands as of the record date is Puerto Rico, and the voting state of a member with a principal place of business located in American Samoa, Guam, or the Commonwealth of the Northern Mariana Islands as of the record date is Hawaii.
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.2 </SECTNO>
                            <SUBJECT>General provisions. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Board size and composition.</E>
                                 Annually, the FHFA Director will determine the size of the board of directors for each Bank and will designate at least a majority, but no more than 60 percent, of the directorships as member directorships and the remainder as independent directorships. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Term of directorships.</E>
                                 The term of office of each directorship commencing on or after January 1, 2009 shall be four years, except as adjusted pursuant to section 7(d) of the Act (12 U.S.C 1427(d)) to achieve a staggered board, and shall commence on January 1 of the calendar year so designated by the FHFA. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Annual elections.</E>
                                 Each Bank annually shall conduct an election the purpose of which is to fill all directorships designated by the FHFA as commencing on January 1 of the calendar year immediately following such election. Subject to the provisions of the Act and in accordance with the requirements of this part, the disinterested members of the board of directors of each Bank, or a committee of disinterested directors, shall administer and conduct the annual election of directors. In so doing, the disinterested directors may use Bank staff or independent contractors to perform ministerial and administrative functions concerning the elections process. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Location of members.</E>
                                 In accordance with section 7(c) of the Act (12 U.S.C 1427(c)), for purposes of the election of member directors, a member is deemed to be located in its voting state, unless otherwise designated by the Director. 
                            </P>
                            <P>
                                (e) 
                                <E T="03">Dates.</E>
                                 If any date specified in this part for action by a Bank, or specified by a Bank pursuant to this part, falls on a Saturday, Sunday, or Federal holiday, the relevant time period is deemed to be extended to the next calendar day that is not a Saturday, Sunday, or Federal holiday. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.3 </SECTNO>
                            <SUBJECT>Designation of member directorships. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Determination of voting stock.</E>
                                 (1) On or before April 10 of each year, each Bank shall deliver to the FHFA a capital stock report that indicates, as of the record date, the number of members located in each voting state in the Bank's district, the number of shares of Bank stock that each member (identified by its FHFA ID number) was required to hold, and the number of shares of Bank stock that all members located in each voting state were required to hold. If a Bank has issued more than one class of stock, it shall report the total shares of stock of all classes required to be held by the members. The Bank shall certify to the FHFA that, to the best of its knowledge, the information provided in the capital stock report is accurate and complete, and that it has notified each member of its minimum capital stock holdings. 
                            </P>
                            <P>(2) If a Bank's capital plan was not in effect as of the record date, the number of shares of Bank stock that any member is required to hold as of the record date shall be determined in accordance with 12 CFR 925.20 and 925.22. If a Bank's capital plan was in effect as of the record date, the number of shares of Bank stock that any member was required to hold as of that date shall be determined in accordance with the minimum investment established by the capital plan for that Bank; however, for any member whose Bank stock is less than the minimum investment during a transition period, the amount of Bank stock to be reported shall be the number of shares of Bank stock actually owned by the member as of the record date. </P>
                            <P>
                                (b) 
                                <E T="03">Designation of member directorships as stock directorships.</E>
                                 The Director annually will conduct a designation of member directorships for each Bank based on the number of shares of Bank stock required to be held by the members in each state as of December 31 of the preceding calendar year, using the method of equal proportions. If a Bank has issued more than one class of stock, the Director will designate the directorships for each state in that Bank district based on the combined number of shares required to be held by the members in that state. For purposes of conducting the designation, if a Bank's capital plan was not in effect on the immediately preceding December 31, the number of shares of Bank stock required to be held by members as of that date shall be determined in accordance with 12 CFR 925.20 and 925.22. If a Bank's capital plan was in effect on the immediately preceding December 31, the number of shares of Bank stock required to be held 
                                <PRTPAGE P="55717"/>
                                by members as of that date shall be determined in accordance with the minimum investment established by such capital plan; however, for any members whose Bank stock is less than the minimum investment during a transition period, the amount of stock to be used in the designation of directorships shall be the number of shares of Bank stock actually owned by those members as of that December 31. In all cases, the Director will designate the directorships by using the information provided by each Bank in its capital stock report required by paragraph (a)(1) of this section. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Allocation of directorships.</E>
                                 (1) The member directorships designated by the Director will be allocated among the states by the Director in accordance with sections 7(b) and (c) of the Act.
                            </P>
                            <P>(2) If the designation of directorships conducted by the Director under paragraph (c)(1) of this section eliminates any existing directorship, or if the allocation of directorships under this paragraph (c) designates any existing stock directorship to another state, the director elected or appointed to that existing directorship shall not be eligible to serve after the close of business on the immediately following December 31. </P>
                            <P>
                                (d) 
                                <E T="03">Notification.</E>
                                 On or before June 1 of each year, the FHFA will notify each Bank in writing of the total number of directorships established for the Bank and the number of member directorships designated as representing the members in each voting state in the Bank district. If the annual designation of member directorships results in an existing directorship being redesignated as representing members in a different state, the directorship shall be deemed to become vacant as of December 31 of that year, and thereafter shall filled by the board of directors of the Bank with an eligible person who is an officer or director of a member located in the newly designated state, regardless of whether the term for the incumbent director would have expired by that date. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.4 </SECTNO>
                            <SUBJECT>Director eligibility. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Eligibility requirements for member directors.</E>
                                 Each member director, and each nominee to a member directorship, shall be: 
                            </P>
                            <P>(1) A citizen of the United States; and </P>
                            <P>(2) An officer or director of a member that is located in the voting state to be represented by the member directorship, that was a member of the Bank as of the record date, and that meets all minimum capital requirements established by its appropriate Federal banking agency or appropriate state regulator. </P>
                            <P>
                                (b) 
                                <E T="03">Eligibility requirements for independent directors.</E>
                                 Each independent director, and each nominee to an independent directorship, shall be: 
                            </P>
                            <P>(1) A citizen of the United States; and </P>
                            <P>(2) A bona fide resident of the district in which the Bank is located. </P>
                            <P>
                                (c) 
                                <E T="03">Restrictions.</E>
                                 (1) A nominee is not eligible if he or she: 
                            </P>
                            <P>(i) Is an incumbent director, unless: </P>
                            <P>(A) The incumbent director's term of office would expire before the new term of office would begin; and </P>
                            <P>(B) The new term of office would not be barred by the term limit provision of section 7(d) of the Act (12 U.S.C. 1427(d)); or </P>
                            <P>(ii) Is a former director whose service would be barred by the term limit provision of section 7(d) of the Act. </P>
                            <P>(2) For purposes of applying the term limit provision of section 7(d) of the Act (12 U.S.C. 1427(d)): </P>
                            <P>(i) A term of office that is adjusted after July 30, 2008 to a period of fewer than four years shall not be deemed to be a full term; </P>
                            <P>(ii) Any three year term of office ending immediately before a term of office that is adjusted after July 30, 2008 to a period of fewer than four years and any term of office commencing immediately following such adjusted term of office shall constitute consecutive full terms of office; and </P>
                            <P>(iii) Any member director's service through election to any directorship with a three year term of office existing on or before July 30, 2008 shall be deemed to be service in a full term directorship to which the director has been elected. </P>
                            <P>
                                (d) 
                                <E T="03">Loss of eligibility.</E>
                                 (1) A director shall become ineligible to remain in office if, during his or her term of office, the directorship to which he or she has been elected is eliminated or, with respect to a member directorship, is redesignated by the FHFA as representing members located in another state, in accordance with § 1261.3(c)(2). The incumbent director shall become ineligible after the close of business on December 31 of the year in which the directorship is redesignated or eliminated. Any directorship ceasing through elimination or redesignation shall not be deemed to be a full-term directorship for purposes of the section. 
                            </P>
                            <P>(2) In the case of a redesignation to another state, the redesignated directorship shall be filled by a majority vote of the remaining Bank directors, sitting as a board, regardless of whether the remaining directors constitute a quorum of the board. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.5 </SECTNO>
                            <SUBJECT>Determination of member votes. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">In general.</E>
                                 Each Bank shall determine, in accordance with this section, the number of votes that each member of the Bank may cast for each directorship that is to be filled by the vote of the members. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Number of votes.</E>
                                 For each member directorship and each independent directorship that is to be filled in an election, each member shall be entitled to cast one vote for each share of Bank stock that the member was required to hold as of the record date. Notwithstanding the preceding sentence, the number of votes that any member may cast for any one directorship shall not exceed the average number of shares of Bank stock required to be held as of the record date by all members located in the same state as of the record date. If a Bank has issued more than one class of stock, it shall calculate the average number of shares separately for each class of stock, using the total number of members in a state as the denominator, and shall apply those limits separately in determining the maximum number of votes that any member owning that class of stock may cast in the election. If a Bank's capital plan was not in effect as of the record date, the number of shares of Bank stock that a member was required to hold as of the record date shall be determined in accordance with 12 CFR 925.20 and 925.22. If a Bank's capital plan was in effect as of the record date, the number of shares of Bank stock that a member was required to hold as of the record date shall be determined in accordance with the minimum investment requirement established by the Bank's capital plan; however, for any member whose Bank stock is less than the minimum investment during a transition period, the amount of Bank stock to be used shall be the number of shares of Bank stock actually owned by the member as of the record date.
                            </P>
                            <P>
                                (c) 
                                <E T="03">Voting preferences.</E>
                                 If the board of directors of a Bank includes any voting preferences as part of its approved capital plan, those preferences shall supersede the provisions of paragraph (b) of this section that otherwise would allow a member to cast one vote for each share of Bank stock it was required to hold as of the record date. If a Bank establishes a voting preference for a class of stock, the members with voting rights shall remain subject to the provisions of section 7(b) of the Act (12 U.S.C. 1427(b)) that prohibit any member from casting any vote in excess of the average number of shares of stock 
                                <PRTPAGE P="55718"/>
                                required to be held by all members in its state. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.6 </SECTNO>
                            <SUBJECT>Nominations for member and independent directorships. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Election announcement.</E>
                                 Within a reasonable time in advance of an election, a Bank shall notify each member in its district of the commencement of the election process. Such notice shall include:
                            </P>
                            <P>(1) The number of member directorships designated for each voting state in the Bank district and the number of independent directorships for the Bank; </P>
                            <P>(2) The name of each incumbent Bank director, the name and location of the member at which each member director serves, and the name and location of the organization with which each independent director is affiliated, if any, and the expiration date of each Bank director's term of office; </P>
                            <P>(3) A brief statement describing the skills and experience the Bank believes are most likely to add strength to the board of directors, provided that the Bank previously has conducted the annual assessment permitted by § 1261.9 and the Bank has elected to provide the results of the assessment to the members; </P>
                            <P>(4) An attachment indicating the name, location, and FHFA ID number of every member in the member's voting state, and the number of votes each such member may cast for each directorship to be filled by such members, as determined in accordance with § 1261.5; and </P>
                            <P>(5) A nominating certificate. </P>
                            <P>
                                (b) 
                                <E T="03">Member directorship nominations.</E>
                                 (1) Any member that is entitled to vote in the election may nominate an eligible individual to fill each available member directorship for its voting state by delivering to its Bank, prior to a deadline to be established by the Bank and set forth in the notice required in paragraph (a) of this section, a nominating certificate duly adopted by the member's governing body or by an individual authorized by the member's governing body to act on its behalf. 
                            </P>
                            <P>(2) The nominating certificate shall include the name of the nominee and the name, location, and FHFA ID number of the member the nominee serves as an officer or director. </P>
                            <P>(3) The Bank shall establish a deadline for delivery of nominating certificates, which shall be no earlier than 30 calendar days after the date on which the Bank delivers the notice required by paragraph (a) of this section, and the Bank shall not accept certificates received after that deadline. The Bank shall retain all accepted nominating certificates for at least two years after the date of the election. </P>
                            <P>
                                (c) 
                                <E T="03">Accepting member directorship nominations.</E>
                                 A Bank shall notify in writing any person nominated for a member directorship promptly upon receipt of the nominating certificate. A person may accept the nomination only by delivering to the Bank, prior to a deadline established by the Bank and set forth in its notice, an executed director eligibility certification form prescribed by the FHFA. A Bank shall allow each nominee at least 30 calendar days after the date the Bank delivered the notice of nomination within which to deliver the executed form. A nominee may decline the nomination by so advising the Bank in writing, or by failing to deliver a properly executed director eligibility certification form prior to the deadline. Each Bank shall retain all information received under this paragraph for at least two years after the date of the election. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Independent directorship nominations.</E>
                                 (1) Any individual who seeks to be an independent director of the board of directors of a Bank may deliver to the Bank, on or before the deadline set by the Bank for delivery of nominating certificates, an executed independent director application form prescribed by the FHFA that demonstrates that the individual both is eligible and has either of the following qualifications: 
                            </P>
                            <P>(i) More than four years experience representing consumer or community interests in banking services, credit needs, housing, or consumer financial protections; or </P>
                            <P>(ii) Knowledge of or experience in one or more of the areas set forth in paragraph (e) of this section. </P>
                            <P>(2) Any other interested party may recommend to the Bank that it consider a particular individual as a nominee for an independent directorship, but the Bank shall not nominate any individual unless the individual has delivered to the Bank, on or before the date the Bank has set for delivery of nominating certificates, an executed independent director application form prescribed by the FHFA. The application form prescribed by the FHFA will provide a means by which an individual can indicate an intent to be considered for a public interest directorship. Only individuals who indicate on the form that they wish to be considered for a public interest directorship may be nominated for such directorships. The board of directors of the Bank may consider any individual for any independent directorship nomination, provided it has determined that the individual is eligible and qualified. The board of directors of the Bank shall consult with the Bank's Advisory Council before nominating any individual for any independent directorship. Each Bank shall include in its bylaws the procedures it intends to use for the nomination and election of the independent directors, and shall retain all information received under this paragraph for at least two years after the date of the election. </P>
                            <P>(3) Each Bank shall determine the number of public interest directorships to be included among its authorized independent directorships, provided that each Bank shall at all times have at least two such directorships, and shall announce that number to its members in the notice required by paragraph (a) of this section. In submitting nominations to its members, each Bank shall nominate at least as many individuals as there are independent directorships to be filled in that year's election. </P>
                            <P>
                                (e) 
                                <E T="03">Independent director qualifications.</E>
                                 Any independent director or nominee for an independent directorship, other than a public interest director, shall submit to the Bank an independent director application form that includes information demonstrating how that person satisfies the requirement that he or she have experience in, or knowledge of, one or more of the following areas: Auditing and accounting; derivatives; financial management; organizational management; project development; risk management practices; and the law. In considering the qualifications of each such nominee for an independent directorship, the board of directors of a Bank shall consider that the nominee's knowledge or experience musts be commensurate with that needed to oversee a financial institution with a size and complexity that is comparable to that of the Bank. 
                            </P>
                            <P>
                                (f) 
                                <E T="03">Eligibility verification.</E>
                                 Using the information provided on the director eligibility certification forms and on the independent director application forms prescribed by the FHFA, a Bank shall verify that each nominee for each member directorship and independent directorship meets all of the eligibility requirements for such directorship, as set forth in the Act and this part. Before announcing any independent director nominee, the Bank shall deliver to the FHFA a copy of the independent director application forms executed by the individuals proposed to be nominated for independent directorships by the board of directors of the Bank. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <PRTPAGE P="55719"/>
                            <SECTNO>§ 1261.7 </SECTNO>
                            <SUBJECT>Election process. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Ballots.</E>
                                 Promptly after verifying the eligibility of all nominees in accordance with with § 1261.6(f), and if, within two weeks of the delivery of nominee application forms to the FHFA, the FHFA has not informed a Bank of any objection to the nomination of any independent director nominee, a Bank shall prepare and deliver a ballot to all members that were members as of the record date. The Bank shall include with each ballot a closing date for the Bank's receipt of voted ballots, which date shall be no earlier than 30 calendar days after the date such ballot is delivered to the member. 
                            </P>
                            <P>(1) A ballot shall include at least the following provisions: </P>
                            <P>(i) For states in which one or more member directorships are to be filled in the election, an alphabetical listing of the names of each nominee for such directorship, the name, location, and FHFA ID number of the member each nominee serves, the nominee's title or position with the member, and the number of member directorships to be filled by the members in that voting state in the election; </P>
                            <P>(ii) An alphabetical listing of the names of each nominee for a public interest directorship and a brief description of each nominee's experience representing consumer and community interests; </P>
                            <P>
                                (iii) An alphabetical listing of the names nominee for the other independent directorships and a brief description of each nominee's qualifications, including his or her knowledge or experience in the areas of financial management, auditing and accounting, risk management practices, derivatives, project development, organizational management and any other area of knowledge or experience set forth in 
                                <E T="03">§ </E>
                                1261.6(e); 
                            </P>
                            <P>(iv) A statement that write-in candidates are not permitted; and </P>
                            <P>(v) A confidentiality statement prohibiting the Banks from disclosing how a member voted. </P>
                            <P>(2) At the election of the Bank, a ballot also may include, in the body or as an attachment, a brief description of the skills and experience of each nominee for a member directorship. </P>
                            <P>
                                (b) 
                                <E T="03">Statement on skills and experience.</E>
                                 If a Bank has conducted an annual assessment permitted by 
                                <E T="03">§ </E>
                                1261.9 and has included the results of the assessment as part of the notice to members required in 
                                <E T="03">§ </E>
                                1261.6(a), it may include with each ballot a statement of the results of that assessment or any subsequent assessment. If the statement differs from the statement provided under 
                                <E T="03">§ </E>
                                1261.6(a)(3), the Bank also shall include an explanation of why the statements differ.
                            </P>
                            <P>
                                (c) 
                                <E T="03">Lack of member directorship nominees.</E>
                                 If, for any voting state, the number of nominees for the member directorships for that state is equal to or fewer than the number of such directorships to be filled in that year's election, the Bank shall deliver a notice to the members in the affected voting state (in lieu of providing a ballot) that such nominees shall be deemed elected without further action, due to a lack of nominees. Thereafter, the Bank shall declare elected all eligible nominees and in doing so may designate particular nominees to guaranteed directorships or stock directorships, respectively, if necessary. The directors declared elected shall be included as directors-elect in the report of election required under paragraph (g) of this section. Any member directorship that is not filled due to a lack of nominees shall be deemed vacant as of January 1 of the following year and shall be filled by the Bank's board of directors in accordance with 
                                <E T="03">§ </E>
                                1261.14(a). 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Voting.</E>
                                 For each directorship to be filled, a member may cast the number of votes determined by the Bank pursuant to 
                                <E T="03">§ </E>
                                1261.5. A member may not split its votes among multiple nominees for a single directorship, and, where there are multiple directorships to be filled, either within the member's voting state or at large, in the case of independent directorships, a member may not cumulatively vote for a single nominee. If any member votes, it shall by resolution of its governing body either authorize the voting for specific nominees or delegate to an individual the authority to vote for specific nominees. To vote, a member shall: 
                            </P>
                            <P>(1) Mark on the ballot the name of not more than one of the nominees for each directorship to be filled. Each nominee so selected shall receive all of the votes that the member is entitled to cast. </P>
                            <P>(2) Execute and deliver the ballot to the Bank on or before the closing date. A Bank shall not allow a member to change a ballot after it has been delivered to the Bank. </P>
                            <P>
                                (e) 
                                <E T="03">Counting ballots.</E>
                                 A Bank shall not review any ballot until after the closing date, and shall not include in the election results any ballot received after the closing date. Promptly after the closing date, each Bank shall tabulate the votes cast in the election: for the member directorships, the Bank shall tabulate votes by each voting state; for the independent directorships, the Bank shall tabulate votes for the district at-large. Any ballots cast in violation of paragraph (d) of this section shall be void. 
                            </P>
                            <P>
                                (f) 
                                <E T="03">Declaring results.</E>
                                 (1) For a member directorship, the Bank shall declare elected the nominee receiving the highest number of votes. If more than one member directorship is to be filled for a particular state, the Bank shall declare elected each successive nominee receiving the next highest number of votes until all such open directorships are filled. 
                            </P>
                            <P>(2) For an independent directorship, the Bank shall declare elected the nominee that has received the highest number of votes and has received at least 20 per cent of the number of votes eligible to be cast in the election. If more than one independent directorship is to be filled, the Bank shall declare elected each successive nominee receiving the next highest number of votes for such directorship until all such open directorships are filled, provided such successive nominee has received at least 20 per cent of the number of votes eligible to be cast in the election. </P>
                            <P>(3) In the event of a tie for the last available directorship, the disinterested incumbent members of the board of directors of the Bank, by a majority vote, shall declare elected one of the nominees for whom the number of votes cast was tied. </P>
                            <P>(4) A Bank shall not declare elected a nominee that it has reason to know is ineligible to serve, nor shall it seat a director-elect that it has reason to know is ineligible to serve. </P>
                            <P>(5) The Bank shall retain all ballots it receives for at least two years after the date of the election, and shall not disclose how any member voted. </P>
                            <P>
                                (g) 
                                <E T="03">Report of election.</E>
                                 Promptly following the election, each Bank shall deliver a notice to its members, to each nominee, and to the FHFA that contains the following information: 
                            </P>
                            <P>(1) For each member directorship, the name of the director-elect, the name and location of the member at which he or she serves, his or her title or position at the member, the voting state represented, the expiration date of the term of office, and the number of votes cast for each nominee; </P>
                            <P>(2) For each independent directorship, the name of the director-elect, whether the director-elect will fill a public interest directorship and, if so, the consumer or community interest represented by such directorship, any qualifications under § 1261.6(e), the expiration date of the term of office and the number of votes cast for each nominee; </P>
                            <P>
                                (3) The number of members voting in the election and the total number of votes cast for each nominee for the member directorships, which shall be reported by state, and the total number 
                                <PRTPAGE P="55720"/>
                                of votes cast for each nominee for the independent directorships, which shall be reported for the district at large. 
                            </P>
                            <P>
                                (h) 
                                <E T="03">Failing to fill all independent directorships.</E>
                                 If any independent directorship of a Bank is not filled through the initial election process set forth in this section, the board of directors of the Bank shall identify additional nominee and shall conduct additional election for the directorship, following the election process set forth in this section. In any such election a nominee shall not be elected unless he or she receives at least 20 percent of the votes eligible to be cast. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.8 </SECTNO>
                            <SUBJECT>[Reserved]. </SUBJECT>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.9 </SECTNO>
                            <SUBJECT>Action affecting director elections. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Banks.</E>
                                 Each Bank, acting through its board of directors, may conduct an annual assessment of the skills and experience possessed by the members of its board of directors as a whole and may determine whether the capabilities of the board would be enhanced through the addition of individuals with particular skills and experience. If the board of directors determines that the Bank could benefit by the addition to the board of directors of individuals with particular qualifications, such as auditing and accounting, derivatives, financial management, organizational management, project development, risk management practices, or the law , it may identify those qualifications and so inform the members as part of its announcement of elections pursuant to § 1261.6(a).
                            </P>
                            <P>
                                (b) 
                                <E T="03">Support for nomination or election.</E>
                                 (1) A Bank director, officer, attorney, employee, or agent, acting in his or her personal capacity, may support the nomination or election of any individual for a member directorship, provided that no such director may purport to represent the views of the Bank or its board of directors in doing so.
                            </P>
                            <P>(2) Notwithstanding paragraph (b)(1) of this section, a Bank director, officer, attorney, employee or agent and the board of directors and Advisory Council of a Bank may support the candidacy of any person nominated by the board of directors for election to an independent directorship. </P>
                            <P>
                                (c) 
                                <E T="03">Prohibition.</E>
                                 Except as provided in paragraphs (a) and (b) of this section, no director, officer, attorney, employee, or agent of a Bank may: 
                            </P>
                            <P>(1) Communicate in any manner that a director, officer, attorney, employee, or agent of a Bank, directly or indirectly, supports or opposes the nomination or election of a particular individual for a directorship; or </P>
                            <P>(2) Take any other action to influence the voting with respect to any particular individual. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.10 </SECTNO>
                            <SUBJECT>Independent director conflict of interests. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Employment interests.</E>
                                 During any independent director's term of service, such director may not serve as an officer, employee, or director of any member of the Bank on whose board the individual sits, or of any recipient of advances from such Bank, and may not serve as an officer of any Bank. An independent director or nominee for any independent directorship shall disclose all such interests to the Bank on whose board of directors the individual serves or which is considering the individual for nomination to its board of directors. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Holding companies.</E>
                                 Service as an officer, employee, or director of a holding company that controls one or more members of, or one or more recipients of advances from, any Bank is not deemed to be service as an officer, employee or director of a member or recipient of advances if the assets of all such members or all such recipients of advances constitute less than 35 percent of the assets of the holding company, on a consolidated basis.
                            </P>
                            <P>
                                (c) 
                                <E T="03">Attribution.</E>
                                 For purposes of determining compliance with this section, a Bank shall attribute to the independent director any officer position, employee position, or directorship of the director's spouse.
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.11 </SECTNO>
                            <SUBJECT>Conflict of interests policy for Bank directors. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Adoption of conflict of interests policy.</E>
                                 Each Bank shall adopt a written conflict of interests policy that applies to all members of its board of directors. At a minimum, the conflict of interests policy of each Bank shall: 
                            </P>
                            <P>(1) Require the directors to administer the affairs of the Bank fairly and impartially and without discrimination in favor of or against any member; </P>
                            <P>(2) Require independent directors to comply with § 1261.10(a); </P>
                            <P>(3) Prohibit the use of a director's official position for personal gain; </P>
                            <P>(4) Require directors to disclose actual or apparent conflicts of interest and establish procedures for addressing such conflicts; </P>
                            <P>(5) Provide internal controls to ensure that reports are filed and that conflicts are disclosed and resolved; and </P>
                            <P>(6) Establish procedures to monitor compliance with the conflict of interests policy. </P>
                            <P>
                                (b) 
                                <E T="03">Disclosure and recusal.</E>
                                 A director shall disclose to the Bank's board of directors any financial interests he or she has, as well as any financial interests known to the director of any immediate family member or business associate of the director, in any matter to be considered by the Bank's board of directors and in any other business matter or proposed business matter involving the Bank and any other person or entity. A director shall disclose fully the nature of his or her interests in the matter and shall provide to the Bank's board of directors any information requested to aid in its consideration of the director's interest. A director shall refrain from considering or voting on any issue in which the director, any immediate family member, or any business associate has any financial interest. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Confidential Information.</E>
                                 Directors shall not disclose or use confidential information they receive solely by reason of their position with the Bank to obtain any benefit for themselves or for any other individual or entity. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Gifts.</E>
                                 Directors shall not accept, and shall discourage their immediate family members from accepting, any gift that the director believes or has reason to believe is given with the intent to influence the director's actions as a member of the Bank's board of directors, or where acceptance of such gift would have the appearance of intending to influence the director's actions as a member of the board.
                            </P>
                            <P>
                                (e) 
                                <E T="03">Compensation.</E>
                                 Directors shall not accept compensation for services performed for the Bank from any source other than the Bank for which the services are performed. 
                            </P>
                            <P>
                                (f) 
                                <E T="03">Definitions.</E>
                                 For purposes of this section: 
                            </P>
                            <P>
                                (1) 
                                <E T="03">Immediate family member</E>
                                 means parent, sibling, spouse, child, or dependent, or any relative sharing the same residence as the director. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Financial interest</E>
                                 means a direct or indirect financial interest in any activity, transaction, property, or relationship that involves receiving or providing something of monetary value, and includes, but is not limited to any right, contractual or otherwise, to the payment of money, whether contingent or fixed. It does not include a deposit or savings account maintained with a member, nor does it include a loan or extension of credit obtained from a member in the normal course of business on terms that are available generally to the public. 
                            </P>
                            <P>
                                (3) 
                                <E T="03">Business associate</E>
                                 means any individual or entity with whom a director has a business relationship, including, but not limited to: 
                            </P>
                            <P>
                                (i) Any corporation or organization of which the director is an officer or partner, or in which the director 
                                <PRTPAGE P="55721"/>
                                beneficially owns ten percent or more of any class of equity security, including subordinated debt; 
                            </P>
                            <P>(ii) Any other partner, officer, or beneficial owner of ten percent or more of any class of equity security, including subordinated debt, of any such corporation or organization; and </P>
                            <P>(iii) Any trust or other estate in which a director has a substantial beneficial interest or as to which the director serves as trustee or in a similar fiduciary capacity. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.12 </SECTNO>
                            <SUBJECT>Reporting requirements for Bank directors. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Annual reporting.</E>
                                 Annually, each Bank shall require each of its directors to execute and deliver to the Bank the appropriate director eligibility certification form prescribed by the FHFA for the type of directorship held by such director. The Bank promptly shall deliver to the FHFA a copy of the certification form delivered to it by each director. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Report of noncompliance.</E>
                                 At any time that any director believes or has reason to believe that he or she no longer meets the eligibility requirements set forth in the Act or this part, the director promptly shall so notify the Bank and the FHFA in writing. At any time that a Bank believes or has reason to believe that any director no longer meets the eligibility requirements set forth in the Act or this part, the Bank promptly shall notify the FHFA in writing. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.13 </SECTNO>
                            <SUBJECT>Ineligible Bank directors. </SUBJECT>
                            <P>
                                Upon a determination by the FHFA or a Bank that any director of the Bank no longer satisfies the eligibility requirements set forth in the Act or this part, or has failed to comply with the reporting requirements of 
                                <E T="03">§ </E>
                                1261.12, the directorship shall immediately become vacant. Any director that is determined to have failed to comply with the eligibility or reporting requirements shall not continue to serve as a Bank director. Whenever a Bank makes such a determination, the Bank promptly shall notify the Bank director and the FHFA in writing.
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.14 </SECTNO>
                            <SUBJECT>Vacant Bank directorships. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Filling unexpired terms.</E>
                                 As soon as practicable after any vacancy occurs, the board of directors of a Bank shall elect, by a majority vote of the remaining Bank directors sitting as a board, an individual to fill the unexpired term of office of the vacant directorship, regardless of whether the remaining Bank directors constitute a quorum of the Bank's board of directors. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Verifying eligibility.</E>
                                 The board of directors of a Bank shall elect to a vacant directorship an individual who satisfies all of the eligibility requirements and any of the qualification requirements set forth in the Act and this part that were applicable to his or her predecessor, except that if the vacant directorship is a public interest directorship and the Bank has at least two other public interest directorships that are not vacant, the board of directors of the Bank may elect any individual who is eligible and qualified for any independent directorship. The Bank shall obtain an executed director eligibility certification form prescribed by the FHFA from the individual filling a member directorship. The Bank shall obtain an executed independent director application form prescribed by the FHFA from the individual filling an independent directorship. The Bank shall verify the individual's eligibility and shall deliver any independent director application form to the FHFA for its review and comment before allowing the individual to assume the directorship. The Bank shall retain the information it receives in accordance with 
                                <E T="03">§ </E>
                                1261.6.
                            </P>
                            <P>
                                (c) 
                                <E T="03">Notification.</E>
                                 Promptly after allowing the individual to assume the directorship, as provided in paragraph (b) of this section, a Bank shall notify the FHFA and each member located in the Bank's district in writing of the following: 
                            </P>
                            <P>(1) For each member directorship filled by the board of a Bank, the name of the director, the name, location, and FHFA ID number of the member the director serves, the director's title or position with the member, the voting state that the director represents, and the expiration date of the director's term of office; and </P>
                            <P>(2) For each independent directorship filled by the board of a Bank, the name of the director, the name and location of the organization with which the director is affiliated, if any, the director's title or position with such organization, and the expiration date of the director's term of office. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.15 </SECTNO>
                            <SUBJECT>Minimum number of member directorships. </SUBJECT>
                            <P>Except with respect to member directorships of a Bank resulting from the merger of any two or more Banks, the number of member directorships allocated to each state shall not be less than the number of directorships allocated to that state on December 31, 1960. The following list sets forth the states whose members held more than one directorship on December 31, 1960: </P>
                            <GPOTABLE COLS="2" OPTS="L2,tp0,i1," CDEF="s30,18">
                                <TTITLE> </TTITLE>
                                <BOXHD>
                                    <CHED H="1">State </CHED>
                                    <CHED H="1">
                                        Number of elective 
                                        <LI>directorships on </LI>
                                        <LI>December 31, 1960</LI>
                                    </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">California </ENT>
                                    <ENT>3 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Colorado </ENT>
                                    <ENT>2 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Illinois </ENT>
                                    <ENT>4 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Indiana</ENT>
                                    <ENT>5 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Iowa</ENT>
                                    <ENT>2 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Kansas</ENT>
                                    <ENT>3 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Kentucky</ENT>
                                    <ENT>2 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Louisiana</ENT>
                                    <ENT>2 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Massachusetts</ENT>
                                    <ENT>3 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Michigan</ENT>
                                    <ENT>3 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Minnesota</ENT>
                                    <ENT>2 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Missouri</ENT>
                                    <ENT>2 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">New Jersey</ENT>
                                    <ENT>4 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">New York</ENT>
                                    <ENT>4 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Ohio</ENT>
                                    <ENT>4 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Oklahoma</ENT>
                                    <ENT>2 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Pennsylvania</ENT>
                                    <ENT>6 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Tennessee</ENT>
                                    <ENT>2 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Texas</ENT>
                                    <ENT>3 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Wisconsin</ENT>
                                    <ENT>4</ENT>
                                </ROW>
                            </GPOTABLE>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1261.16 </SECTNO>
                            <SUBJECT>Temporary rule for 2008 election of directors. </SUBJECT>
                            <P>
                                (a) This section applies to the scheduling provisions for the election of directors of the Banks during calendar year 2008. Each Bank shall schedule its elections to allow a reasonable time to accomplish each act and complete the election process by December 31, 2008. As described herein, this section operates in conjunction with 
                                <E T="03">§§ </E>
                                1261.3, 1261.6 and 1261.7, which govern generally the election of directors. The special provisions of this section govern the process for the 2008 elections for Bank directorships in the case of any conflict with the provisions of the other sections of this part. 
                            </P>
                            <P>
                                (b) Each Bank shall notify its members of the commencement of the election process and shall establish a reasonable deadline after delivery of such notice within which nominating certificates must be received by the Bank, pursuant to the requirements of 
                                <E T="03">§ </E>
                                1261.6. 
                            </P>
                            <P>
                                (c) After a Bank has accepted member directorship nominations, the Bank shall take the actions specified in 
                                <E T="03">§ </E>
                                1261.6(c) within a reasonable time. 
                            </P>
                            <P>
                                (d) No Bank shall accept any completed and executed director eligibility certification form or any independent director application form referred to in 
                                <E T="03">§ </E>
                                1261.6(c) and (d) beyond a reasonable deadline established by the Bank. 
                            </P>
                            <P>
                                (e) Each Bank shall deliver to each of its voting members a set of ballot materials, pursuant to the requirements of 
                                <E T="03">§ </E>
                                1261.7(a), and shall establish a reasonable period of time for the voting of ballots.
                            </P>
                            <P>
                                (f) After the closing date established by a Bank, the Bank shall commence the counting of ballots pursuant to the requirements of 
                                <E T="03">§ </E>
                                1261.7(e).
                                <PRTPAGE P="55722"/>
                            </P>
                            <P>
                                (g) Not later than December 31, 2008, each Bank shall declare the results of its election and report the results, pursuant to 
                                <E T="03">§ </E>
                                1261.7(f) and (g).
                            </P>
                            <P>
                                (h) For any Bank that began a 2008 elective directorship election process after having received the Federal Housing Finance Board's Resolution titled 
                                <E T="03">2008 Designation of Federal Home Loan Bank Directorships,</E>
                                 Resolution No. 2008-10 dated May 14, 2008, if the number of elective directorships designated for election in 2008 in that Resolution for any state is the same as, or is more than, the number of member directorships designated for election in the state in 2008 in the Order of the FHFA Director dated September 8, 2008, then, as to such states to the extent that the Bank has completed the election process for such directorships in accordance with Federal Housing Finance Board rules up through and including verification of eligibility of nominees, the Bank's election process for member directorships shall be deemed to be in compliance with paragraphs (a), (b), (c) and (d) of this section, as applicable.
                            </P>
                            <P>(i) This section is effective from September 26, 2008 through December 31, 2008.</P>
                        </SECTION>
                    </PART>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: September 22, 2008. </DATED>
                    <NAME>James B. Lockhart, III, </NAME>
                    <TITLE>Director, Federal Housing Finance Agency.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22659 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8070-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 47</CFR>
                <SUBJECT>Cape Town Treaty Implementation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; technical amendment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This final rule corrects a previously published rule. In the original document, an amendment inadvertently removed two paragraphs relating to the registration of certain aircraft. This rule reinstates those two paragraphs in their original form.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective September 26, 2008.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Walter Binkley, Civil Aviation Registry, AFS-750, Mike Monroney Aeronautical Center, 6500 South MacArthur Boulevard, Oklahoma City, OK 73169; Telephone (405) 954-3131.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>On January 3, 2005, FAA published a final rule revising the regulations concerning registering aircraft and recording security documents (70 FR 245). These revisions were required by the Cape Town Treaty Implementation Act of 2004. The Cape Town Treaty established a new International Registry for registering interests against certain aircraft and aircraft engines. The rule also made unrelated technical changes to other portions of the regulations.</P>
                <P>One of the technical changes affected 14 CFR 47.35. The amendment should have revised paragraph (a) introductory text, in order to revise an outdated reference to an Act. However, the entire paragraph (a) was inadvertently revised, which resulted in the loss of paragraphs (a)(1) and (a)(2). The information in paragraphs (a)(1) and (a)(2) was still necessary and should have remained in the section.</P>
                <HD SOURCE="HD1">Technical Amendment</HD>
                <P>This technical amendment merely reinstates paragraphs (a)(1) and (a)(2) to 14 CFR 47.35. The text of these paragraphs remains as it was at the time of their inadvertent removal.</P>
                <HD SOURCE="HD1">Justification for Immediate Adoption</HD>
                <P>Because this action reinstates paragraphs that were never intended to be removed, the FAA finds that notice and public comment under 5 U.S.C. 553(b) is unnecessary. For the same reason, the FAA finds that good cause exists under 5 U.S.C. 553(d) for making this rule effective upon publication.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 47</HD>
                    <P>Aircraft, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="14" PART="47">
                    <HD SOURCE="HD1">The Amendment</HD>
                    <AMDPAR>In consideration of the foregoing, the Federal Aviation Administration amends Chapter I of Title 14, Code of Federal Regulations, part 47, as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 47-AIRCRAFT REGISTRATION</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 47 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>4 U.S.T. 1830; Pub. L. 108-297, 118 Stat. 1095 (49 U.S.C. 40101 note, 49 U.S.C. 44101 note); 49 U.S.C. 106(g), 40113-40114, 44101-44108, 44110-44113, 44703-44704, 44713, 45302, 46104, 46301.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="47">
                    <AMDPAR>2. Amend § 47.35 by adding paragraphs (a)(1) and (a)(2) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 47.35</SECTNO>
                        <SUBJECT>Aircraft last previously registered in the United States.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(1) If the applicant bought the aircraft from the last registered owner, the conveyance must be from that owner to the applicant.</P>
                        <P>(2) If the applicant did not buy the aircraft from the last registered owner, he must submit conveyances or other instruments showing consecutive transactions from the last registered owner through each intervening owner to the applicant.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Washington, DC, on September 22, 2008.</DATED>
                    <NAME>Pamela Hamilton-Powell,</NAME>
                    <TITLE>Director, Office of Rulemaking.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22586 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2008-0610; Airspace Docket No. 08-ASW-10]</DEPDOC>
                <SUBJECT>Establishment of Class E Airspace; Pampa, TX</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Direct final rule; confirmation of effective date; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This action confirms the effective date and makes a correction to the direct final rule that establishes Class E airspace at Pampa, Mesa Vista Ranch Airport, TX, published in the 
                        <E T="04">Federal Register</E>
                         July 7, 2008 (73 FR 38314) Docket No. FAA-2008-0610. This action corrects the final rule by adding “Mesa Vista Ranch Airport” to more clearly define the airport name in the airport description.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective Date: 0901 UTC September 25, 2008. The Director of the Federal Register approves this incorporation by reference action under Title 1, Code of Federal Regulations, part 51, subject to the annual revision of FAA Order 7400.9 and publication of conforming amendments.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Gary Mallett, Central Service Center, System Support Group, Federal Aviation Administration, Southwest Region, 2601 Meacham Blvd, Fort Worth, TX, 76193-0530; telephone (817) 222-4949.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published a direct final rule with request for comments in the 
                    <E T="04">Federal Register</E>
                     July 7, 2008, (73 FR 38314), Docket No. FAA-2008-0610. 
                    <PRTPAGE P="55723"/>
                    The FAA uses the direct final rule procedure for non-controversial rules where the FAA believes that there will be no adverse public comment. This direct final rule advised the public that no adverse comments were anticipated, and that unless a written adverse comment, or a written notice of intent to submit an adverse comment, was received within the comment period, the regulation would become effective on September 25, 2008. No adverse comments were received; thus, this notice confirms that the direct final rule will become effective on this date. Also, the charting office recommended changing the airport description to include Mesa Vista Ranch Airport.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>49 U.S.C. 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                </AUTH>
                <REGTEXT TITLE="14" PART="71">
                    <HD SOURCE="HD1">Correction</HD>
                    <AMDPAR>
                        In the 
                        <E T="04">Federal Register</E>
                         dated July 7, 2008, 
                        <E T="04">Federal Register</E>
                         Docket No. FAA-2008-0610, page 38315, column 3, line 50, change to read:
                    </AMDPAR>
                    <HD SOURCE="HD1">ASW TX Class E5 Pampa, Mesa Vista Ranch Airport, TX [New].</HD>
                    <STARS/>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Fort Worth, TX on September 17, 2008.</DATED>
                    <NAME>Roger Trevino,</NAME>
                    <TITLE>Acting Manager, Operations Support Group, ATO Central Service Center.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22719 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 73 </CFR>
                <DEPDOC>[Docket No. FAA-2006-26192; Airspace Docket No. 06-ASO-11] </DEPDOC>
                <RIN>RIN 2120-AA66 </RIN>
                <SUBJECT>Modification and Establishment of Restricted Areas and Other Special Use Airspace, Adirondack Airspace Complex; Fort Drum, NY </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action restructures the restricted areas and other special use airspace (SUA) located in the vicinity of Fort Drum, NY. The Air National Guard (ANG) requested redesign of existing restricted airspace R-5201, known as the Adirondack Airspace Complex, by establishing two new restricted areas: R-5202A and R-5202B, and by restructuring the military operations areas (MOA) contained in the Adirondack Airspace Complex. Unlike restricted areas, which are designated under 14 CFR part 73, MOAs are not rulemaking airspace actions. However, since these MOAs form an integral part of the Adirondack Airspace Complex, the FAA is including a description of the associated MOA changes in this rule. The MOA changes described here will also be published in the National Flight Data Digest (NFDD). The ANG requested these airspace changes to provide the additional SUA needed to conduct more realistic aircrew training in the Adirondack Airspace Complex. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         0901 UTC, November 20, 2008. 
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Paul Gallant, Airspace and Rules Group, Office of System Operations Airspace and AIM, Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591; telephone: (202) 267-8783. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>
                    On June 6, 2007, the FAA published in the 
                    <E T="04">Federal Register</E>
                     a notice of proposed rulemaking (NPRM) to redesign the SUA in the vicinity of Fort Drum, NY (72 FR 31211). Interested parties were invited to participate in this rulemaking proceeding by submitting written comments on the proposal to the FAA. Seven responses were received. 
                </P>
                <HD SOURCE="HD1">Discussion of Comments </HD>
                <P>The Aircraft Owners and Pilots Association (AOPA) opposed the proposed Adirondack Airspace Complex modifications for several reasons. AOPA questioned the need for two nearly identical SUA expansions being developed within 150 nautical miles (NM) of one another (i.e., Adirondack Airspace Complex, NY and Condor MOA, ME). AOPA contended that expanding both Adirondack and Condor would result in redundant SUA and would not be efficient use of the National Airspace System (NAS). </P>
                <P>
                    <E T="03">FAA Response:</E>
                     Many factors are considered in the development of SUA proposals including, but not limited to, distance of the proposed SUA from the user's base, number of users to be accommodated and training capacity of the area. Ideally, MOAs should be located within 100 NM of the users' home base. However, this is often not possible due to other requirements of the NAS. The greater the distance from the launch base to the SUA, the more transit time is required, which results in less training time available per sortie and increased training costs per sortie. The main distinction between the Adirondack and Condor SUA is the existence of restricted airspace at Fort Drum, NY. No restricted airspace is available at Condor; therefore, no hazardous activities may be conducted in that airspace. Use of the Condor airspace is limited to air-to-air tactics training, basic flight maneuvers, etc. The Adirondack Airspace Complex is used by as many as eight fighter wings for training in air-to-air tactics, and air-to-ground weapons delivery, lasers, etc. In addition, Fort Drum is the home of the U.S. Army's 10th Mountain Division and the restricted areas are extensively used for surface-based weapons training (e.g., artillery and mortar firing, missiles, etc.) by U.S. Army and National Guard units. The 174th FW at Syracuse, NY, is both the proponent and one of the primary users of the Adirondack Airspace Complex. The distance from Syracuse to Adirondack is about 72 NM and about 274 NM from Syracuse to the Condor airspace. While the 174th FW could conceivably use Condor for its air-to-air training, that would add some 400 NM travel distance—about one hour flying time—to the sortie and severely limit available training time. In addition, some training profiles combine both air-to-air and air-to-ground events in the same sortie making it more efficient to conduct the entire sortie in the Adirondack airspace. At this time, the Condor MOA proposal is still under study and it must be analyzed and evaluated on its own merit. 
                </P>
                <P>Additionally, AOPA stated its opposition to use of the “Dynamic Airspace concept” for airspace management as it has yet to be developed and defined. </P>
                <P>
                    <E T="03">FAA Response:</E>
                     The “Dynamic Airspace concept” was not addressed in the NPRM and is not an FAA-recognized term. The NPRM did indicate that one feature of the proposed airspace changes was to enable more efficient real-time use of the airspace. It is FAA policy that all SUA areas be activated on a real-time use basis to the extent possible. This means that only those SUA areas, or portions of areas, that are actually needed for the mission are activated, and users are expected to return the airspace to the controlling agency when not needed for the mission. Real-time use provisions are normally specified in a letter of agreement to allow the controlling agency to place temporary restrictions or altitude limitations on the use of the SUA, if required, so that nonparticipating aircraft can transit the SUA area. These provisions would be 
                    <PRTPAGE P="55724"/>
                    applied based on traffic conditions at the time. 
                </P>
                <P>AOPA recommended that the FAA require a charted radio frequency and telephone number for all new SUA proposals to enable pilots to obtain real-time status information about the airspace. AOPA said that other military units, including the ANG's Volk Field in Wisconsin, have successfully implemented charted frequencies and phone numbers. </P>
                <P>
                    <E T="03">FAA Response:</E>
                     The FAA agrees with the use of charted frequencies and phone numbers where the capabilities exist. The Volk Field Combat Readiness Training Center is an advanced operation with multiple radar feeds into their facility and a dedicated VHF radio frequency for disseminating SUA information. Unfortunately, the Adirondack Airspace Complex proponent does not have the same capabilities as Volk Field. There is no military radar coverage and no dedicated radio frequency located at the ANG facility on Fort Drum to provide those services. However, Boston Air Route Traffic Control Center (ARTCC), which is the controlling agency for all Adirondack SUA except the Drum MOA and Wheeler-Sack Approach Control (Drum MOA controlling agency), will be able to provide real-time status for the airspace. Additionally, the Eastern Air Defense Sector (EADS), as the scheduling agency for all of the airspace, has agreed to provide a phone number for SUA scheduling information (1-800-223-5612, Prompt #3). 
                </P>
                <P>AOPA also recommended that the managing unit for the Adirondack Airspace Complex be required to use the FAA's Military Airspace Data Entry (MADE) SUA scheduling system to ensure that SUA information is available to Automated Flight Service Stations and other agencies. </P>
                <P>
                    <E T="03">FAA Response:</E>
                     EADS, the airspace scheduling agency, supports this process and plans to use MADE to the maximum extent possible. 
                </P>
                <P>Two commenters objected to the proposal based on the impact on flights between the areas to the south and west of the Adirondack Airspace Complex MOAs and towns in northern New York, such as Saranac Lake and Lake Placid. One commenter was concerned that a convenient VOR Federal airway would be eliminated. Another stated that, on Instrument Flight Rules (IFR) flights when using GPS for point-to-point direct navigation, about 50% of the time, he is vectored off the direct routing and sent to V-196. Both individuals feared that the expanded MOAs would result in flights being forced further east and directly over the highest mountain peaks where the minimum en route altitude is 10,000 feet mean sea level (MSL). This would result in increased costs in both fuel and time and also decrease flight safety by placing the aircraft over inhospitable terrain and in an area where the worst icing is encountered. Further, the commenter doubted that the proposal to open parts of the MOAs for transit by civil aircraft would not be realized due to controller staffing and workload issues. </P>
                <P>
                    <E T="03">FAA Response:</E>
                     The FAA acknowledges that the proposed new MOAs may have some impact on Visual Flight Rules and IFR traffic flying southwest/northeast through the region. However, several mitigations were incorporated to minimize the impacts. To better facilitate real-time use of the airspace, the proposed Tupper North airspace has been further spilt into two MOAs: the Tupper West and Tupper Central (the proposed Tupper North designation will not be used). The Tupper West MOA lies directly over the Cranberry MOA (Note: Cranberry extends from 500 feet above ground level (AGL) to but not including 6,000 feet MSL). The Tupper Central MOA consists of the remainder of what was proposed as the Tupper North MOA. This new configuration will provide greater flexibility in accommodating both military activity and civil traffic in the area. Additionally, the letter of agreement with the using agency will provide Boston ARTCC the option to adjust the MOA floor as required to allow civil aircraft to traverse the Tupper MOA airspace. Despite the MOA expansions, Federal airway V-196 will remain a viable means for transiting the area. 
                </P>
                <P>One commenter, who flies an amphibian float plane between Rochester, NY, and the Thousand Island region of New York State, wrote with concerns about the impact of the airspace changes on the use of Maxson Field (89N) and Crystal Lake, within the Drum MOA. The commenter had similar concerns about the MOAs being too close to Piseco Airport (K09) and the Adirondack Regional Airport, Saranac Lake (SLK). The commenter cited the Adirondack D MOA as being too low and too close to Maxson and Crystal Lake and suggested that, instead of beginning at 500 feet AGL, the MOA should be raised to at least 2,000 feet AGL. </P>
                <P>
                    <E T="03">FAA Response:</E>
                     Currently, the closest MOA to Maxson Field is the Drum 1 MOA, which extends from 500 AGL to 5,000 feet MSL. The western boundary of the existing Drum 1 MOA lies about 2 
                    <FR>1/2</FR>
                     NM east of the airport. With the airspace changes, the Drum 1 MOA is being reduced in size and renamed the Drum MOA. The new Drum MOA boundary will be moved further eastward increasing the distance from Maxson Field to about 5 NM, thereby reducing impacts on the airport. Although the commenter identified the new Adirondack D MOA as impacting Maxson Field and Crystal Lake, we believe the commenter meant Drum MOA. The Adirondack D MOA lies east of, and adjacent to, the new Drum MOA and extends upward from 5,000 feet MSL up to but not including Flight Level (FL) 180. Regarding the concerns about the proximity of the MOAs to the Piseco and Saranac Lake airports, the Piseco airport is located about 2 NM south of the Tupper South MOA boundary. The floor of the Tupper South MOA will vary seasonally ranging from 6,000 feet MSL during November through April, to 8,000 feet MSL during May through October. Although the new MOA does extend into close proximity to Piseco Field, with its field elevation of 1,703 feet MSL, ample airspace should be available for traffic patterns and airport arrivals and departures. The Adirondack Regional Airport is located directly under the eastern boundary of the new Tupper East MOA. The Tupper East MOA, with a floor of 10,000 feet MSL, was specifically designed as a separate area in order to minimize impacts to the Adirondack Regional Airport. While the published floor of the Tupper East MOA will remain at 10,000 feet MSL to accommodate the mission when needed, the proponent has agreed that Boston ARTCC will routinely limit MOA users to a 12,000 foot floor. This will further minimize impacts on civil traffic in the Saranac Lake area. If the military mission requires a lower altitude, pilots will request the 10,000 foot floor on a real-time basis. Boston ARTCC will have the option to approve the request if traffic permits. 
                </P>
                <P>Comments were also received from the Adirondack Mountain Club, The Adirondack Council, and the Adirondack Park Agency. These organizations expressed support for the various mitigations included in the proposal for environmental and cultural impacts, but also noted general concerns about the impacts of low level flights and noise. However, no significant noise impacts are expected as a result of these airspace changes. Generally, noise levels are expected to remain consistent with existing levels, or be less across the complex. </P>
                <HD SOURCE="HD1">Adirondack Airspace Complex MOAs </HD>
                <P>
                    MOAs are non-rulemaking airspace actions that are established 
                    <PRTPAGE P="55725"/>
                    administratively and published in the NFDD. Since they are an integral part of the Adirondack Airspace Complex, the MOA changes were described in the NPRM and are included in this rule for information purposes. 
                </P>
                <P>The ANG requested the MOA modifications to improve flight safety; enable more efficient real-time, joint-use management of the airspace; lessen or balance environmental impacts of the current MOA configuration; and permit more realistic aircrew training in the Adirondack Airspace Complex. Most of the redesigned MOAs are contained within airspace that is already designated as MOA. However, these modifications do encompass some additional airspace, both laterally and vertically, outside the current MOA boundaries to the east and south of the currently charted MOAs. </P>
                <P>
                    There are several changes to the descriptions of the MOAs from those contained in the proposal. As discussed above, the proposed Tupper North MOA is further subdivided into the Tupper West and Tupper Central. The Tupper North title will not be used. This change enhances the real-time use of airspace and provides air traffic control with additional airspace management options. The northern boundary of the Cranberry MOA is moved south by 
                    <FR>1/2</FR>
                     NM to avoid conflict with protected airspace for instrument procedures at Massena International Airport—Richards Field, NY. One common point that is shared in the descriptions of the Adirondack B, Adirondack D and Drum MOAs was listed differently in the proposed descriptions and is corrected to lat. 44°19′00″ N., long. 75°37′05″ W. The controlling agency for all of the Adirondack airspace, except the Drum MOA, is Boston ARTCC. The controlling agency for the Drum MOA is Wheeler-Sack Approach Control. The using agency for all of the MOAs is the New York ANG, 174th Fighter Wing, Detachment 1, Fort Drum, NY. 
                </P>
                <P>In consideration of the above, the nine existing MOAs in the Adirondack Airspace Complex (i.e., Drum 1 MOA, Drum 2 MOA, Falcon 1 MOA, Falcon 3 MOA, Syracuse 1 MOA, Syracuse 2A MOA, Syracuse 2B MOA, Syracuse 3 MOA, and Syracuse 4 MOA), are cancelled and are replaced by 13 new MOAs as follows: </P>
                <EXTRACT>
                    <HD SOURCE="HD1">1. Adirondack A MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 44°30′00″ N., long. 75°20′00″ W.; to lat. 44°36′00″ N., long. 75°03′00″ W.; to lat. 44°30′00″ N., long. 75°03′00″ W.; to the point of beginning. </P>
                    <P>Altitudes. 6,000 feet MSL to but not including FL 180. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">2. Adirondack B MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 44°19′00″ N., long. 75°37′05″ W.; to lat. 44°26′30″ N., long. 75°30′00″ W.; to lat. 44°30′00″ N., long. 75°20′00″ W.; to lat. 44°30′00″ N., long. 75°03′00″ W.; to lat. 44°27′30″ N., long. 75°03′00″ W.; to lat. 44°20′20″ N., long. 75°10′30″ W.; to lat. 44°15′09″ N., long. 75°30′42″ W.; to lat. 44°16′07″ N., long. 75°32′41″ W.; to the point of beginning; excluding R-5202B when active. </P>
                    <P>Altitudes. 2,500 feet MSL to but not including FL 180. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">3. Adirondack C MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 44°15′09″ N., long. 75°30′42″ W.; to lat. 44°20′20″ N., long. 75°10′30″ W.; to lat. 44°27′30″ N., long. 75°03′00″ W.; to lat. 44°06′00″ N., long. 75°03′00″ W.; to lat. 44°06′00″ N., long. 75°28′49″ W.; to lat. 44°07′10″ N., long. 75°26′49″ W.; to lat. 44°11′24″ N., long. 75°22′59″ W.; to the point of beginning; excluding R-5202B when active. </P>
                    <P>Altitudes. 100 feet AGL to but not including FL 180. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">4. Adirondack D MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 44°11′50″ N., long. 75°43′53″ W.; to lat. 44°19′00″ N., long. 75°37′05″ W.; to lat. 44°16′07″ N., long. 75°32′41″ W.; to lat. 44°10′50″ N., long. 75°38′59″ W.; to lat. 44°09′34″ N., long. 75°40′00″ W.; to the point of beginning; excluding R-5202B when active. </P>
                    <P>Altitudes. 5,000 feet MSL to but not including FL 180. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">5. Carthage East MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 44°01′05″ N., long. 75°37′14″ W.; to lat. 44°06′00″ N., long. 75°28′49″ W.; to lat. 44°06′00″ N., long. 75°03′00″ W.; to lat. 43°53′00″ N., long. 75°03′00″ W.; to lat. 43°53′00″ N., long. 75°35′00″ W.; to the point of beginning. </P>
                    <P>Altitudes. 100 feet AGL to but not including FL 180. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">6. Carthage West MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 43°44′00″ N., long. 75°52′00″ W.; to lat. 44°11′50″ N., long. 75°43′53″ W.; to lat. 44°09′34″ N., long. 75°40′00″ W.; to lat. 44°06′55″ N., long. 75°42′09″ W.; to lat. 44°03′20″ N., long. 75°40′49″ W.; to lat. 44°01′05″ N., long. 75°37′14″ W.; to lat. 43°53′00″ N., long. 75°35′00″ W.; to the point of beginning. </P>
                    <P>Altitudes. 6,000 feet MSL to but not including FL 180. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">7. Cranberry MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 44°35′30″ N., long. 75°03′00″ W.; to lat. 44°36′00″ N., long. 75°00′00″ W.; to lat. 44°36′00″ N., long. 74°35′00″ W.; to lat. 44°15′00″ N., long. 74°35′00″ W.; to lat. 43°53′00″ N., long. 75°03′00″ W.; to the point of beginning. </P>
                    <P>Altitudes. 500 feet AGL to but not including 6,000 feet MSL. </P>
                    <P>Times of use. November 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM; May 1-October 31: Area closed. </P>
                    <HD SOURCE="HD1">8. Drum MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 44°14′49″ N., long. 75°49′00″ W.; to lat. 44°19′00″ N., long. 75°44′30″ W.; to lat. 44°19′00″ N., long. 75°37′05″ W.; to lat. 44°16′07″ N., long. 75°32′41″ W.; to lat. 44°10′50″ N., long. 75°38′59″ W.; to lat. 44°09′34″ N., long. 75°40′00″ W.; to the point of beginning. </P>
                    <P>Altitudes. 500 feet AGL to but not including 5,000 feet MSL. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">9. Lowville MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 43°44′00″ N., long. 75°52′00″ W.; to lat. 43°53′00″ N., long. 75°35′00″ W.; to lat. 43°53′00″ N., long. 75°03′00″ W.; to lat. 43°30′00″ N., long. 75°03′00″ W.; to lat. 43°30′00″ N., long. 75°52′00″ W.; to the point of beginning. </P>
                    <P>Altitudes. 100 feet AGL to but not including FL 180. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">10. Tupper West MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 44°36′00″ N., long. 75°03′00″ W.; to lat. 44°36′00″ N., long. 74°35′00″ W.; to lat. 44°15′00″ N., long. 74°35′00″ W.; to lat. 43°53′00″ N., long. 75°03′00″ W.; to the point of beginning. </P>
                    <P>Altitudes. May 1-October 31: 8,000 feet MSL to but not including FL 180; November 1-April 30: 6,000 feet MSL to but not including FL 180. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">11. Tupper Central MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 44°36′00″ N., long. 74°35′00″ W.; to lat. 44°36′00″ N., long. 74°21′00″ W.; to lat. 44°14′00″ N., long. 74°21′00″ W.; to lat. 44°06′00″ N., long. 74°12′00″ W.; to lat. 43°53′00″ N., long. 74°12′00″ W.; to lat. 43°53′00″ N., long. 75°03′00″ W.; to lat. 44°15′00″ N., long. 74°35′00″ W.; to the point of beginning. </P>
                    <P>
                        Altitudes. May 1-October 31: 8,000 feet MSL to but not including FL 180; November 
                        <PRTPAGE P="55726"/>
                        1-April 30: 6,000 feet MSL to but not including FL 180. 
                    </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">12. Tupper South MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 43°53′00″ N., long. 75°03′00″ W.; to lat. 43°53′00″ N., long. 74°12′00″ W.; to lat. 43°40′00″ N., long. 74°12′00″ W.; to lat. 43°30′00″ N., long. 74°21′00″ W.; to lat. 43°30′00″ N., long. 75°03′00″ W.; to the point of beginning. </P>
                    <P>Altitudes. May 1-October 31: 8,000 feet MSL to but not including FL 180; November 1-April 30: 6,000 feet MSL to but not including FL 180. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                    <HD SOURCE="HD1">13. Tupper East MOA, NY [New] </HD>
                    <P>Boundaries. Beginning at lat. 44°36′00″ N., long. 74°21′00″ W.; to lat. 44°36′00″ N., long. 74°12′00″ W.; to lat. 44°06′00″ N., long. 74°12′00″ W.; to lat. 44°14′00″ N., long. 74°21′00″ W.; to the point of beginning. </P>
                    <P>Altitudes. 10,000 feet MSL to but not including FL 180. </P>
                    <P>Times of use. May 1-August 31: 0800-1700 Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 Monday-Friday; other times by NOTAM. </P>
                </EXTRACT>
                <HD SOURCE="HD1">The Rule </HD>
                <P>The FAA is amending Title 14 Code of Federal Regulations (14 CFR) part 73 to establish two new restricted areas, R-5202A and R-5202B, in the vicinity of Fort Drum, NY. The new restricted areas supplement the existing restricted area, R-5201, to enable aircrews to train in high altitude, long range weapons delivery and other modern tactics at the Adirondack Range. In the NPRM, the FAA also proposed to change the designated altitudes of R-5201 from “Surface to 23,000 feet MSL,” to “Surface to but not including 23,000 feet MSL.” After further discussions between the controlling agency and the proponent, it was determined that this change is not needed; therefore, R-5201 will not be modified as proposed. As a result, the proposed FL 230 base altitude of the new restricted area, R-5202A, which overlies R-5201, is changed to 23,000 feet MSL to be consistent with the ceiling of R-5201. In addition, the NPRM contained an incorrect date in the time of designation for R-5202A and R-5202B. The portion of the time of designation stated in the NPRM as “May 1-August 21” should read “May 1-August 31.” The correct dates are included in this rule. Except as noted above, the restricted area descriptions are the same as proposed in the NPRM. </P>
                <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. Therefore, this regulation: (1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under Department of Transportation (DOT) Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation, it is certified that this rule, when promulgated, will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. </P>
                <P>This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of the airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it modifies special use airspace in New York. </P>
                <HD SOURCE="HD1">Environmental Review </HD>
                <P>The FAA has determined that the Final Environmental Assessment (FEA) prepared by the Air National Guard associated with the proposed project is adequate for adoption in accordance with FAA Order 1050.1E, “Environmental Impacts: Policies and Procedures,” Paragraph 404d. The FAA has independently evaluated the information contained in the FEA and takes full responsibility for the scope and content that addresses FAA actions. Further, the FAA has issued its own Finding of No Significant Impact. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 73 </HD>
                    <P>Airspace, Prohibited areas, Restricted areas.</P>
                </LSTSUB>
                <REGTEXT TITLE="14" PART="73">
                    <HD SOURCE="HD1">Adoption of the Amendment </HD>
                    <AMDPAR>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 73 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 73—SPECIAL USE AIRSPACE </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 73 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="73">
                    <SECTION>
                        <SECTNO>§ 73.52 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>2. § 73.52 is amended as follows: </AMDPAR>
                    <EXTRACT>
                        <STARS/>
                        <HD SOURCE="HD1">R-5202A Fort Drum, NY [New] </HD>
                        <P>Boundaries. Beginning at lat. 44°01′05″ N., long. 75°37′14″ W.; to lat. 44°03′20″ N., long. 75°40′49″ W.; to lat. 44°06′55″ N., long. 75°42′09″ W.; to lat. 44°10′50″ N., long. 75°38′59″ W.; to lat. 44°16′07″ N., long. 75°32′41″ W.; to lat. 44°11′24″ N., long. 75°22′59″ W.; to lat. 44°07′10″ N., long. 75°26′49″ W.; to the point of beginning. </P>
                        <P>Designated altitudes. 23,000 feet MSL to FL 290. </P>
                        <P>Time of designation. May 1-August 31: 0800-1700 local time, Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 local time, Monday-Friday; other times by NOTAM. </P>
                        <P>Controlling agency. FAA, Boston ARTCC. </P>
                        <P>Using agency. NY ANG, 174FW/Det 1, Fort Drum, NY. </P>
                        <STARS/>
                        <HD SOURCE="HD1">R-5202B Fort Drum, NY [New] </HD>
                        <P>Boundaries. Beginning at lat. 44°10′18″ N., long. 75°41′18″ W.; to lat. 44°20′32″ N., long. 75°32′04″ W.; to lat. 44°14′00″ N., long. 75°17′00″ W.; to lat. 44°06′00″ N., long. 75°25′10″ W.; to lat. 44°06′00″ N., long. 75°28′49″ W.; to lat. 44°07′10″ N., long. 75°26′49″ W.; to lat. 44°11′24″ N., long. 75°22′59″ W.; to lat. 44°16′07″ N., long. 75°32′41″ W.; to lat. 44°10′50″ N., long. 75°38′59″ W.; to lat. 44°09′34″ N., long. 75°40′00″ W.; to the point of beginning. </P>
                        <P>Designated altitudes. 6,000 feet MSL to FL 290. </P>
                        <P>Time of designation. May 1-August 31: 0800-1700 local time, Monday-Friday; other times by NOTAM. September 1-April 30: 0800-2200 local time, Monday-Friday; other times by NOTAM. </P>
                        <P>Controlling agency. FAA, Boston ARTCC. </P>
                        <P>Using agency. NY ANG, 174FW/Det 1, Fort Drum, NY.</P>
                    </EXTRACT>
                </REGTEXT>
                <STARS/>
                <SIG>
                    <DATED>Issued in Washington, DC, on September 12, 2008. </DATED>
                    <NAME>Edith V. Parish, </NAME>
                    <TITLE>Manager, Airspace &amp; Rules Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22646 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <CFR>18 CFR Parts 260, 284 and 385</CFR>
                <DEPDOC>[Docket No. RM07-10-001; Order No. 704-A]</DEPDOC>
                <SUBJECT>Transparency Provisions of Section 23 of the Natural Gas Act</SUBJECT>
                <DATE>Issued September 18, 2008.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Order on Rehearing and Clarification.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Federal Energy Regulatory Commission affirms its basic 
                        <PRTPAGE P="55727"/>
                        determinations in Order No. 704, while granting rehearing in part and clarification regarding requirements that certain natural gas market participants report information regarding their reporting of transactions to price index publishers and their blanket sales certificate status. These natural gas market participants must report annually certain information regarding their physical natural gas transactions for the previous calendar year. As clarified in the Order on Rehearing and Clarification, certain market participants engaged in a 
                        <E T="03">de minimis</E>
                         volume of transactions will not be required to report information regarding their transactions for the calendar year. The reported information will make it possible to assess the formation of index prices and the use of index pricing in natural gas markets. These regulations facilitate price transparency in markets for the wholesale sale of physical natural gas in interstate commerce as contemplated by section 23 of the Natural Gas Act, 15 U.S.C. 717t-2.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         This rule will become effective October 27, 2008. The revisions to FERC Form No. 552 are applicable for the reporting of transactions occurring in calendar year 2008.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <FP SOURCE="FP-1">
                        Matthew L. Hunter (Technical), Office of Enforcement, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-6409. 
                        <E T="03">Matthew.Hunter@ferc.gov.</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        Christopher J. Peterson (Technical), Office of Enforcement, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-8933, 
                        <E T="03">Christopher.Peterson@ferc.gov.</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        Gabe S. Sterling (Legal), Office of Enforcement, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-8891, 
                        <E T="03">Gabriel.Sterling@ferc.gov.</E>
                    </FP>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">Before Commissioners: Joseph T. Kelliher, Chairman; Suedeen G. Kelly, Marc Spitzer, Philip D. Moeller, and Jon Wellinghoff.</P>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    1. On December 26, 2007, the Commission issued Order No. 704, which imposed an annual reporting requirement on certain natural gas market participants.
                    <SU>1</SU>
                    <FTREF/>
                     The order requires certain natural gas buyers and sellers to file annually FERC Form No. 552 and report summary information about physical natural gas transactions for each calendar year.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">Transparency Provisions of Section 23 of the Natural Gas Act</E>
                        , Order No. 704, 74 FR 1014 (Jan. 4, 2008), FERC Stats. &amp; Regs. ¶ 31,260.
                    </P>
                </FTNT>
                <P>
                    2. Order No. 704 has its genesis in the Energy Policy Act of 2005 (EPAct 2005).
                    <SU>2</SU>
                    <FTREF/>
                     EPAct 2005 added section 23 of the Natural Gas Act (NGA), 15 U.S.C. § 717t-2 (2000 &amp; Supp. V 2005) to authorize the Commission “to facilitate price transparency in markets for the sale or transportation of physical natural gas in interstate commerce, having due regard for the public interest, the integrity of those markets, and the protection of consumers.” Section 23 further provides that the Commission may issue such rules as it deems necessary and appropriate to “provide for the dissemination, on a timely basis, of information about the availability and prices of natural gas sold at wholesale and interstate commerce to the Commission, State commissions, buyers and sellers of wholesale natural gas, and the public.”
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Energy Policy Act of 2005, Pub. L. No. 109-58, 119 Stat. 594 (2005).
                    </P>
                </FTNT>
                <P>
                    3. Section 23 of the NGA enhances the Commission's authority to ensure confidence in the nation's natural gas markets. The Commission's market-oriented policies for the wholesale natural gas industry require that interested persons have broad confidence that reported market prices accurately reflect the interplay of legitimate market forces. Without confidence in the fairness of price formation, the true value of transactions is very difficult to determine. Further, price transparency makes it easier for us to ensure that jurisdictional prices are “just and reasonable.” 
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         sections 4 and 5 of the Natural Gas Act, 15 U.S.C. sections 717c and 717d.
                    </P>
                </FTNT>
                <P>
                    4. The performance of Western electric and natural gas markets early in the decade shook confidence in posted market prices for energy. In examining these markets, the Commission's staff found that some companies submitted false information to the publishers of natural gas price indices, so that the resulting reported prices were inaccurate and untrustworthy.
                    <SU>4</SU>
                    <FTREF/>
                     As a result, questions arose about the legitimacy of published price indices, remaining even after the immediate crisis passed. Moreover, market participants feared that the indices might have become even more unreliable, since reporting (which has always been voluntary) declined to historically low levels in late 2002.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Initial Report on Company-Specific Separate Proceedings and Generic Reevaluations; Published Natural Gas Price Data; and Enron Trading Strategies—Fact Finding Investigation of Potential Manipulation of Electric and Natural Gas Prices, Docket No. PA02-2-000 (August 2003).
                    </P>
                </FTNT>
                <P>
                    5. One of the Commission's responses to these developments was the issuance, on July 24, 2003, of a 
                    <E T="03">Policy Statement on Electric and Natural Gas Price Indices</E>
                     (Policy Statement) that explained our expectations of natural gas and electricity price index developers and the companies that report transaction data to them.
                    <SU>5</SU>
                    <FTREF/>
                     The Policy Statement, among other things, directed the Commission's staff to continue to monitor price formation in wholesale markets, including the level of reporting to index developers and the amount of adherence to the Policy Statement standards by price index developers and by those who provide data to them.
                    <SU>6</SU>
                    <FTREF/>
                     In adhering to this directive, Commission staff documented improvements in the number of companies reporting prices from back offices, adopting codes of conduct, and auditing their price reporting practices.
                    <SU>7</SU>
                    <FTREF/>
                     These efforts resulted in significant progress in the amount and quality of both price reporting and the information provided to market participants by price indices.
                    <SU>8</SU>
                    <FTREF/>
                     It is against this backdrop that Congress passed EPAct 2005 and provided us with expanded authority to mandate additional reporting and improve market confidence through greater price transparency.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">Price Discovery in Natural Gas and Electric Markets</E>
                        , 104 FERC ¶ 61,121 (2003).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">Id.</E>
                         P 43.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Federal Energy Regulatory Commission, Report on Natural Gas and Electricity Price Indices, at 2, Docket Nos. PL03-3-004 
                        <E T="03">et al.</E>
                         (2004).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See, e.g.</E>
                        , GENERAL ACCOUNTING OFFICE, NATURAL GAS AND ELECTRICITY MARKETS: FEDERAL GOVERNMENT ACTIONS TO IMPROVE PRIVATE PRICE INDICES AND STAKEHOLDER REACTION (December 2005).
                    </P>
                </FTNT>
                <P>
                    6. In an April 19, 2007 Notice of Proposed Rulemaking, the Commission proposed regulations consistent with these new responsibilities.
                    <SU>9</SU>
                    <FTREF/>
                     The April 2007 NOPR contained both an annual transaction reporting requirement for market participants as well as a daily posting requirement for pipelines. On December 26, 2007, the Commission issued Order No. 704 regarding the annual reporting requirement. The daily pipeline posting requirement proposal was separated from the annual filing requirement and a new Notice of Proposed Rulemaking regarding the pipeline posting requirement was issued concurrently in Docket No. RM08-2-000.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">Transparency Provisions of Section 23 of the Natural Gas Act</E>
                        , 72 FR 20791 (Apr. 26, 2007), FERC Stats. and Regs. ¶ 32,614 (2007) (April 2007 NOPR).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Pipeline Posting Requirements under Section 23 of the Natural Gas Act</E>
                        , 73 FR 1116 (Jan. 7, 2008), 
                        <PRTPAGE/>
                        FERC Stats. and Regs. ¶ 32,626 (2007). A technical conference has been held in Docket No. RM08-2-000 and the pipeline posting requirement is pending further action by the Commission.
                    </P>
                </FTNT>
                <PRTPAGE P="55728"/>
                <P>7. Order No. 704 required natural gas wholesale market participants, including a number of entities that may not otherwise be subject to the Commission's traditional NGA jurisdiction, to identify themselves and report summary information about their physical natural gas transactions on an annual, calendar year basis. To facilitate such reporting, Order No. 704 created FERC Transaction Report FERC Form No. 552: Annual Report of Natural Gas Transactions (Form No. 552) and various implementing regulations. Form No. 552 is to be filed by May 1, 2009, for transactions occurring in calendar year 2008 and by May 1 of each year thereafter for each previous calendar year.</P>
                <P>8. Thirteen requests for rehearing or clarification of Order No. 704 were timely filed. No request for rehearing or clarification argues that the rule is unnecessary or should not have been issued. Rather, the requests seek modification or clarification of specific aspects of Order No. 704. Commission staff held two technical conferences during which potential filers of Form No. 552 and other industry stakeholders discussed the form. Stakeholders at these two technical conferences represented a broad spectrum of market participants and observers, including producers, interstate pipelines, intrastate pipelines, natural gas marketers, commodities traders, local distribution companies (LDCs), electric generation end-users, industrial end-users, and natural gas price index developers. Many conference participants filed comments following one or both of these conferences.</P>
                <P>9. As discussed below, we largely affirm Order No. 704, granting a limited number of rehearing requests and clarifying the order.</P>
                <HD SOURCE="HD1">II. Discussion</HD>
                <HD SOURCE="HD2">A. The Value of Aggregated Annual Data Regarding Volumes That Utilize, Contribute to, or Could Contribute to the Development of Price Indices</HD>
                <P>
                    10. Order No. 704 focused primarily on “price formation in spot markets” and accordingly sought information about the “amount of daily or monthly fixed-price trading that [is] eligible to be reported to price index publishers as compared to the amount of trading that uses or refers to price indices.” 
                    <SU>11</SU>
                    <FTREF/>
                     As we stated in the order, the “information collected under this requirement is focused specifically on daily and monthly physical spot or `cash' market activity and the contracting based on the prices developed in those markets.” 
                    <SU>12</SU>
                    <FTREF/>
                     The rationale for this focus is that a “[b]etter understanding of the role and functioning of wholesale natural gas spot markets can increase confidence that posted market prices of natural gas accurately reflect the interplay of legitimate market forces.” 
                    <SU>13</SU>
                    <FTREF/>
                     Additionally, information on price index utilization and formation would greatly enhance the Commission's efforts to monitor price formation in the wholesale markets in support of the Commission's market-oriented policies.
                    <SU>14</SU>
                    <FTREF/>
                     As we explained, “without confidence in the basic processes of price formation, market participants cannot have faith in the value of their transactions, the public cannot believe that the prices they see are fair, and it is more difficult for the Commission to ensure that jurisdictional prices are `just and reasonable.' ” 
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Order No. 704 at P 3. 
                        <E T="03">See also id.</E>
                         P 13.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Id.</E>
                         P 67.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                         P 7 and 62.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">Id.</E>
                         P 66 (citing sections 4 and 5 of the NGA, 15 U.S.C. sections 717c and 717d).
                    </P>
                </FTNT>
                <P>11. Our recognition of the importance of price formation on market confidence is, of course, not new. The Commission has often remarked on the need to ensure price transparency and accurate price reporting, including, for example, our 2003 Policy Statement on price reporting to index developers. As we there recognized:</P>
                <EXTRACT>
                    <P>
                        Price indices are widely used in bilateral natural gas and electric commodity markets to track spot and forward prices. They are often referenced in contracts as a price term; they are related to futures markets and used when futures contracts go to delivery; basis differentials in indices are used to hedge natural gas transportation costs; indices are used in many gas pipeline tariffs to settle imbalances or determine penalties; and state commissions use indices as benchmarks in reviewing the prudence of gas or electricity purchases. Since index dependencies permeate the energy industry, the indices must be robust and accurate and have the confidence of market participants for such markets to function properly and efficiently.
                        <SU>16</SU>
                        <FTREF/>
                    </P>
                </EXTRACT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Policy Statement at P 6.
                    </P>
                </FTNT>
                <P>We continue to believe that ensuring price transparency is a vital policy goal, especially as it relates to transactions that utilize, contribute, or could contribute to a price index.</P>
                <P>12. Section 23(a)(4) of the NGA requires us to “consider the degree of transparency provided by existing price publishers and providers of trade processing services, and [] rely on such publishers and services to the maximum extent possible.” We have reviewed existing price index publications and, while the Commission recognizes the substantial value that these publications have enhancing market transparency, we determine that the additional data required on Form No. 552 is necessary. Section 23 is consistent with our belief that transparency is furthered by shedding light on price indices and their formation.</P>
                <P>
                    13. The Commission reiterates that the focus of Form No. 552's data collection is transactions that utilize an index price, contribute to index price formation, or could contribute to index price formation. Specifically, the Commission finds that volumes reportable on Form No. 552 should include volumes that utilize next-day or next-month price indices, volumes that are reported to any price index publisher, and any volumes that could be reported to an index publisher even if the respondent has chosen not to report to a publisher. By “could be reported to an index publisher,” we mean bilateral, arms-length, fixed price, physical natural gas transactions between non-affiliated companies at all trading locations.
                    <SU>17</SU>
                    <FTREF/>
                     Transactions that do not occur at a specific location currently designated by an index developer as a reporting location are nonetheless reportable on Form No. 552.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         We note that this understanding tracks closely with our discussion of transactions that are reportable to index developers in the Policy Statement. 
                        <E T="03">See</E>
                         Policy Statement at P 34.
                    </P>
                </FTNT>
                <P>
                    14. This focus on index price-related transactions will increase market participant confidence by providing greater transparency in the use of index prices and how well index prices reflect market forces. This data will also allow the Commission's staff, state commissions, and all other industry observers to evaluate the level of index price usage at both a company level and nationally.
                    <SU>18</SU>
                    <FTREF/>
                     Data on index development and use would be of substantial value in the Commission's transparency and market monitoring missions.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Further, as discussed in greater detail below, observers will be able to parse data to compare activities of purchasers and sellers in the market.
                    </P>
                </FTNT>
                <P>
                    15. We also clarify that Form No. 552 does not seek the broader range of transaction data necessary to evaluate the size of the national physical natural gas market. While Order No. 704 mentioned such a calculation as one result of the data to be collected,
                    <SU>19</SU>
                    <FTREF/>
                     we elect not to craft Form No. 552 to 
                    <PRTPAGE P="55729"/>
                    capture the data necessary to calculate a national market. At this time, we do not believe that such data would further the transparency of the natural gas markets other than determining an aggregate approximation of the entirety of physical gas transactions. Further, unless volumes that utilize price indices or that could contribute to such indices were separately reported on Form No. 552 (with an additional, substantial reporting burden), the analytical benefits noted above would be lost. Lastly, any attempt to rationally estimate the size of the physical gas market on a national level would require reporting from a substantially larger group of respondents than the narrower focus adopted in Order No. 704. Respondents would necessarily include smaller market participants for whom the reporting burden would be undue. For these reasons, we reiterate and emphasize our determination that data provided on Form No. 552 should be limited to transactions that utilize, contribute to, or could contribute to index price formation. However, the Commission understands that the natural gas market is ever evolving and dynamic. At a future date we may elect to amend Form No. 552 to obtain additional information necessary to facilitate transparency of the market.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         Order No. 704 at PP 18 and 69. Similarly, P 5 of the order indicates that an understanding “in broad terms” of the extent of the natural gas market is a goal of the rule.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Both Sales and Purchase Data Are To Be Included on Form No. 552</HD>
                <P>
                    16. Order No. 704 required the annual reporting both of relevant natural gas sales and purchases. We explained that purchase information was the opposing side of a sale transaction and, thus, was as relevant to the Commission's transparency mission as the reporting of sales.
                    <SU>20</SU>
                    <FTREF/>
                     Further, we noted that we have often found the reporting of purchase information beneficial both independent of sales figures and as a cross-check on such volumes.
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">Id.</E>
                         P 86.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">Id.</E>
                         PP 85-86.
                    </P>
                </FTNT>
                <P>17. Although we understand that some participants in the technical conferences objected to the collection of purchase data in various contexts, we continue to believe that purchase data is a vital component to Form No. 552 and the Commission's transparency goals. Not only is purchase information important as a cross-check on reported sales volumes, but it has independent value. If only sales were reported on Form No. 552, Commission staff, state commissions, and other market observers would be unable to discern, for example, whether significant numbers of gas purchasers were transacting under contracts referencing an index price. Analysis of Form No. 552 purchase information will also provide trend data regarding purchase activity, which would be very useful for those charged with monitoring the natural gas markets. With purchase data, the public will be able to discern which purchasers are utilizing index-based contracts, whether there is geographic disparity regarding use of price indices among purchasers, the overall reliance upon gas price indices by purchasers, and other information relevant to market analysis and market confidence. While we acknowledge that removing purchases from volumes that must be reported on Form No. 552 would somewhat reduce the reporting burden on certain market participants, we continue to believe that the substantial benefits of having such data publicly available outweigh this burden.</P>
                <HD SOURCE="HD2">C. The De Minimis Reporting Threshold</HD>
                <P>
                    18. Section 23(d)(2) of the NGA requires the Commission to exempt from new transparency reporting requirements “natural gas producers, processors or users who have a 
                    <E T="03">de minimis</E>
                     market presence.” 
                    <SU>22</SU>
                    <FTREF/>
                     Consistent with this directive, Order No. 704 provided that most buyers or sellers of less than a 
                    <E T="03">de minimis</E>
                     volume of natural gas are not required to submit Form No. 552.
                    <SU>23</SU>
                    <FTREF/>
                     The order set the 
                    <E T="03">de minimis</E>
                     threshold at 2.2 million MMBtus; that is, annual sales plus annual purchases of more than 2.2 million MMBtus required a market participant to report transaction information. In setting this threshold, the Commission “sought to require reporting from a sufficient number of significant market participants to ensure, in the aggregate, an accurate picture of the physical natural gas market as a whole.” 
                    <SU>24</SU>
                    <FTREF/>
                     The Commission explained that:
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         15 U.S.C. section 717t-2(d)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Form No. 552 must be submitted by any section 204.402 or section 284.284 blanket certificate holder even if the entity has aggregate purchases and sales less than the 
                        <E T="03">de minimis</E>
                         threshold. Such an entity must provide identification information on Form No. 552 and must answer questions regarding price reporting to price index publishers, but need not submit Form No. 552's aggregate volume data. Order No. 704 at P 60.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">Id.</E>
                         P 78.
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>
                        [T]he [2.2 million MMBtu] figure was based on the simple calculation of one-ten thousandth (1/10,000th) of the annual physical volumes consumed in the United States, which is approximately 22 trillion cubic feet (Tcf) (or roughly 22 billion MMBtus). Looked at another way, a 
                        <E T="03">de minimis</E>
                         market participant would trade the equivalent of less than one standard NYMEX futures contract per day. Although a market participant that contracts for 1/10,000th of the nation's annual physical volume may appear to have little effect on natural gas prices, that participant may be transacting only at one location and, thus, have a much greater pricing effect there.
                    </P>
                </EXTRACT>
                <HD SOURCE="HD3">Requests for Clarification or Rehearing</HD>
                <P>
                    19. Copano Energy L.L.C. (Copano) requests rehearing of the 
                    <E T="03">de minimis</E>
                     threshold and argues that 2.2 million MMBtu is such a low threshold so as to render meaningless the NGA's directive that the Commission exempt from annual reporting requirements market participants that have a 
                    <E T="03">de minimis</E>
                     market presence.
                    <SU>25</SU>
                    <FTREF/>
                     Copano argues that the Congressional purpose behind the 
                    <E T="03">de minimis</E>
                     threshold was to exclude entities that are too small to have an impact on market prices in the interstate, wholesale gas market. Copano states that a threshold one-hundred times as large (
                    <E T="03">i.e.</E>
                    , 220 million MMBtu/year) would represent less than 1 percent of annual physical volumes of gas consumed in the country and “would therefore have no ability to impact prices in the wholesale, interstate natural gas market.” 
                    <SU>26</SU>
                    <FTREF/>
                     Copano notes that Order No. 704 justifies the selected threshold by noting that even small amounts of gas purchases can have a price effect at certain locations.
                    <SU>27</SU>
                    <FTREF/>
                     Copano believes that this reinforces its conclusion that a threshold should be established that measures market presence at market hubs.
                    <SU>28</SU>
                    <FTREF/>
                     Instead of a single-number 
                    <E T="03">de minimis</E>
                     threshold, Copano suggests a two-pronged approach that considers both the impact of a market participant's transactions on the overall wholesale gas market (a twenty-two million MMBtu threshold) and the impact of a market participant's transactions at market hubs (5 percent of the total jurisdictional sales at the hub).
                    <SU>29</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         Copano comments at 8.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">Id.</E>
                         5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">Id.</E>
                         at 6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">Id.</E>
                         at 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">Id.</E>
                         at 7-8.
                    </P>
                </FTNT>
                <P>
                    20. American Public Gas Association (APGA) requests clarification of section 260.401(b) of the Commission's regulations. As currently written, the regulation exempts an entity that does not hold a blanket sales 
                    <E T="03">or</E>
                     marketing certificate from the reporting requirement if the entity either made fewer than 2.2 million Dth of wholesale sales 
                    <E T="03">or</E>
                     2.2 million Dth of wholesale purchases. APGA proposes that the Commission clarify this language so as to ensure that an entity with fewer than 2.2 million MMBtu of purchases is exempted from reporting purchases and an entity with fewer than 2.2 million 
                    <PRTPAGE P="55730"/>
                    MMBtu of sales is exempted from reporting sales.
                    <SU>30</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         APGA comments at 2.
                    </P>
                </FTNT>
                <P>
                    21. Shell requests that the Commission clarify whether purchases and sales should be aggregated for purposes of calculating an entity's total reportable volumes.
                    <SU>31</SU>
                    <FTREF/>
                     Additionally, Shell seeks guidance regarding how market participants are to determine whether they fall into the 
                    <E T="03">de minimis</E>
                     exception when part of the relevant total sales or purchases are to an affiliate or under other circumstances.
                    <SU>32</SU>
                    <FTREF/>
                     Shell also requests clarification as to whether volumes that total 
                    <E T="03">exactly</E>
                     2.2 TBtu fall into or out of the 
                    <E T="03">de minimis</E>
                     exception as the rule references amounts above and below the threshold, but not precisely at the threshold.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         Shell is, collectively, Shell Gulf of Mexico, Shell Offshore, Inc., Shell Rocky Mountain Production LLC, and SWEPI LP. Shell comments at 28.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">Id.</E>
                         at 28-29.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">Id.</E>
                         at 29.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Commission Determination</HD>
                <P>
                    22. Regarding the appropriate 
                    <E T="03">de minimis</E>
                     threshold, we affirm our findings in Order No. 704 and retain the 2.2 million MMBtu level. As the Commission stated in Order No. 704, even market participants with total reportable volumes slightly above the threshold may have a significant effect on local wholesale markets.
                    <SU>34</SU>
                    <FTREF/>
                     While it is possible that a respondent that exceeds the 
                    <E T="03">de minimis</E>
                     threshold exemption does not actually contribute to price formation, it is certain that some do and, in any event, market observers cannot yet know with any degree of assuredness which market participants have or do not have local price relevance. Likewise, these entities may rely upon price indices for a sizeable portion of their natural gas transactions. Form No. 552 seeks data only for volumes that either reference price indices or could contribute to the formation of price indices. A number of transactions are not reportable (as identified on Form No. 552, as discussed in Order No. 407, and as clarified in this order). Market participants should bear in mind that the Commission is not seeking data on all gas sales and purchases made by an entity, but rather a subset of these transactions.
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         Order No. 704 at P 81.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         For example, we clarify below that a bundled retail transaction made at a state-approved tariff rate is not reportable. We anticipate that this clarification will significantly limit the reporting obligation on smaller market participants.
                    </P>
                </FTNT>
                <P>
                    23. Nothing in Copano's request for rehearing provides new information regarding the establishment of a proper 
                    <E T="03">de minimis</E>
                     threshold. While we acknowledge that there are a number of rational ways to establish a 
                    <E T="03">de minimis</E>
                     threshold consistent with our Congressional mandate, we continue to believe that 2.2 million MMBtu is an appropriate threshold for the reasons expressed herein and in Order No. 704.
                </P>
                <P>
                    24. Regarding APGA and Shell's requests involving how volumes are to be calculated to determine whether an entity meets or exceeds the 
                    <E T="03">de minimis</E>
                     threshold, the Commission clarifies that an entity that has 2.2 million MMBtu of reportable sales or purchases must file Form No. 552. That is, a potential respondent with either reportable purchases equal to or greater than 2.2 million MMBtu or reportable sales 
                    <SU>36</SU>
                    <FTREF/>
                     equal to or greater than 2.2 million MMBtu must submit the form. The following table, regarding reportable purchase and sale volumes, explains how the 
                    <E T="03">de minimis</E>
                     threshold will apply:
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         Reportable sales include off-system, balancing, and other assorted reportable sales as discussed elsewhere in this order.
                    </P>
                </FTNT>
                <GPOTABLE COLS="03" OPTS="L2,tp0,i1" CDEF="s50,r50,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Reportable sales volumes</CHED>
                        <CHED H="1">Reportable purchase volumes</CHED>
                        <CHED H="1">Does the entity report?</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">≥ 2.2 million MMBtu</ENT>
                        <ENT>≥ 2.2 million MMBtu</ENT>
                        <ENT>Yes, both sales and purchases.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">≥ 2.2 million MMBtu</ENT>
                        <ENT>&lt; 2.2 million MMBtu</ENT>
                        <ENT>Yes, both sales and purchases.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">&lt; 2.2 million MMBtu</ENT>
                        <ENT>≥ 2.2 million MMBtu</ENT>
                        <ENT>Yes, both sales and purchases.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">&lt; 2.2 million MMBtu</ENT>
                        <ENT>&lt; 2.2 million MMBtu</ENT>
                        <ENT>No (unless the entity has a blanket certificate, in which case it will provide non-volume information only).</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    25. We also clarify that sales and purchase volumes do not “net each other out” for purposes of determining whether an entity meets or exceeds the 
                    <E T="03">de minimis</E>
                     threshold. Additionally, an entity that must file Form No. 552 must report both reportable sales and reportable purchases regardless of the total volumes associated with each component volume. For example, if a potential respondent has annual reportable sales of 2.0 million MMBtu and reportable purchases of 3.0 million MMBtu, then it must file Form No. 552 as its purchases exceed the 
                    <E T="03">de minimis</E>
                     threshold of 2.2 million MMBtu. Further, it would report both its sales and purchases on the form.
                    <SU>37</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         APGA's request for clarification on this point is therefore denied.
                    </P>
                </FTNT>
                <P>
                    26. We further clarify that, if a transaction is reportable on Form No. 552, then volumes associated with the transaction should be counted towards the threshold. The converse is also true: if a transaction volume would not be included on the form, then volumes associated with it should not be counted towards the threshold. We emphasize that not all physical natural gas purchases and sales count towards the threshold.
                    <SU>38</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         As detailed herein, physical transactions of companies that fall below the 
                        <E T="03">de minimis</E>
                         threshold are excluded from the data collected by Form No. 552. Physical transactions need not be reported if they are not Next-Day or Next-Month transactions as those terms are defined in Form No. 552. In this same vein, financial transactions, transactions between affiliates, and traditional retail transactions (as discussed below), are not reportable on Form No. 552.
                    </P>
                </FTNT>
                <P>
                    27. If a company chooses to aggregate volumes from affiliates, then such volumes are aggregated for purposes of determining whether the corporation meets or exceeds the 
                    <E T="03">de minimis</E>
                     threshold. In response to Shell's requested clarification, Order No. 704 already makes clear that “a company with multiple affiliates may choose to report separately or in aggregate, as best meets its needs.” 
                    <SU>39</SU>
                    <FTREF/>
                     A company with multiple affiliates that chooses to aggregate must, however, aggregate all of its affiliates' data (
                    <E T="03">i.e.</E>
                    , it may not choose to aggregate some affiliates but not others). Consistent with Shell's other requests, we have modified Form No. 552 to make clear that entities that meet or exceed the 
                    <E T="03">de minimis</E>
                     volume must submit the form.
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         Order No. 704 at PP 60 and 97.
                    </P>
                </FTNT>
                <P>
                    28. Regarding the format of amounts reported on Form No. 552, the Commission will require that volumetric entries on Form No. 552 be rounded to the nearest tenth of a TBtu. We understand that there was some confusion among participants at the technical conferences regarding the rounding of volume figures on Form No. 552. Form No. 552 currently requests reporting of volumes to the nearest TBtu (
                    <E T="03">i.e.</E>
                     , a reportable volume of 2.499 TBtu would be reported as 2.0 TBtu). We 
                    <PRTPAGE P="55731"/>
                    direct respondents to round volumes up or down, as appropriate, to the 
                    <E T="03">nearest tenth</E>
                     of a TBtu. Rounding to the nearest tenth of a TBtu will make the reporting obligation consistent with the proposed 
                    <E T="03">de minimis</E>
                     threshold volume calculation, which is measured to the nearest tenth of a TBtu. Further, more precise reporting of data would allow for a more accurate review of market activity and we believe that aggregating volumes to the nearest tenth of a TBtu would be no more burdensome for respondents than the rounding currently required in the form.
                </P>
                <HD SOURCE="HD2">D. Certain End-Use Transactions Should Be Reported on Form No. 552</HD>
                <P>
                    29. Several commenters to the April 2007 NOPR objected to the inclusion of end-use transactions in the annual report.
                    <SU>40</SU>
                    <FTREF/>
                     Order No. 704 addressed these concerns by exempting certain types of transactions from the reporting requirement. The order states that the rule “focuses the reporting requirement solely on wholesale buyers and sellers by excluding retail transactions.” 
                    <SU>41</SU>
                    <FTREF/>
                     The order did not require “end-use customers or retail buyers” to report transaction information unless those entities also made wholesale sales or purchases that were greater than the 
                    <E T="03">de minimis</E>
                     threshold.
                    <SU>42</SU>
                    <FTREF/>
                     Likewise, the order stated that “a transaction made to an end-user is not to be included in the volumes reported on the form.” 
                    <SU>43</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         These commenters included American Forest &amp; Paper Association (AF&amp;PA), Industrial Energy Consumers of America (IECA), and Natural Gas Supply Association (NGSA).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         Order No. 704 at P 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         
                        <E T="03">Id.</E>
                         P 90.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    30. However, the order did not adequately distinguish between two distinct types of end-use transactions (
                    <E T="03">i.e.</E>
                     transactions that utilize or could contribute to a price index and transactions to customers as part of a bundled retail sale). The American Gas Association (AGA) and the National Energy Marketers Association (NEM), for example, specifically argued in comments on the April 2007 NOPR that end-use sales 
                    <E T="03">at retail</E>
                     should be excluded from the reporting requirement.
                    <SU>44</SU>
                    <FTREF/>
                     These types of end-use transactions involved retail service provided by a LDC to consumers subject to the LDC's state commission-approved tariff. Other commenters argued for a broader exemption, including all end-use transactions.
                    <SU>45</SU>
                    <FTREF/>
                     These types of transactions would include not only bundled retail service subject to traditional state jurisdiction, but also direct end-use deliveries by interstate pipelines (an activity traditionally subject to the Commission's jurisdiction).
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         AGA NOPR comments at 3; NEM NOPR comments at 5. 
                        <E T="03">See also</E>
                         NGSA NOPR comments at 12.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         AF&amp;PA NOPR comments at 5.
                    </P>
                </FTNT>
                <P>
                    31. Order No. 704 correctly, though summarily, describes these participants' comments,
                    <SU>46</SU>
                    <FTREF/>
                     but then proceeded to utilize the term “retail” interchangeably with “end-use” when describing transactions that would be exempt from the reporting requirement.
                    <SU>47</SU>
                    <FTREF/>
                     For example, under a section entitled, “Exclusion of Retail Transactions,” the order states that “[a]lthough some transactions reported to indices may include purchases by large end-users, the Commission is generally interested in wholesale prices.” 
                    <SU>48</SU>
                    <FTREF/>
                     Our exclusion in Order No. 704 is aimed at traditional retail transactions (
                    <E T="03">i.e.</E>
                    , those that are in markets functionally separate from the wholesale markets) rather than other end-use transactions involving volumes in the wholesale market—although the language of the rule's exclusion could easily be read so as to reach to all end-use transactions.
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         Order No. 704 at PP 39-40.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         
                        <E T="03">See, e.g.</E>
                        , Order No. 704 at PP 60, 89, and 90.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         
                        <E T="03">Id.</E>
                         P 90.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Requests for Clarification or Rehearing</HD>
                <P>
                    32. NGSA requests clarification or rehearing regarding a seller's obligation to exclude end-use volumes from volumes reported on Form No. 552. NGSA quotes paragraph 90 of Order No. 704 indicating that “a transaction made to an end-user is not to be included in the volumes reported on the form.” 
                    <SU>49</SU>
                    <FTREF/>
                     NGSA argues that requiring the seller to delineate between end-use and non-end-use customers is unduly burdensome and that requiring such disclosure to sellers from purchasers would limit market liquidity.
                    <SU>50</SU>
                    <FTREF/>
                     NGSA requests that the Commission clarify that, when in doubt, it is acceptable for a seller to include end-use volumes in Form No. 552.
                    <SU>51</SU>
                    <FTREF/>
                     Any exclusion of end-use transactions should be applied from the buyers' perspective, argues NGSA.
                    <SU>52</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         NGSA comments at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         
                        <E T="03">Id.</E>
                         4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">Id.</E>
                         5.
                    </P>
                </FTNT>
                <P>
                    33. We understand that a number of participants at the technical conference (including AGA, Encana,
                    <SU>53</SU>
                    <FTREF/>
                     and others) had both substantive and technical questions regarding Order No. 704's references to “end-use” transactions and “retail” transactions. There was significant confusion regarding whether certain types of transactions to consumers of natural gas were reportable. AGA filed supplemental comments in the docket requesting various clarifications regarding an LDC's responsibility to report sales to end-users, among other transactions.
                    <SU>54</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         Encana Marketing (USA) Inc. (distinct from its joint rehearing request as part of the Canadian Suppliers).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         AGA supplemental comments at 3-5.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Commission Determination</HD>
                <P>
                    34. The Commission clarifies here that there will be no categorical exclusion of end-use transactions from Form No. 552. Nevertheless, Form No. 552 will collect only information regarding that subset of end-use transactions that relies upon price indices or that could be utilized to form a price index. Accordingly, as we explain below, reporting of traditional, bundled retail transactions made by an LDC at a state-approved tariff rate (
                    <E T="03">i.e.</E>
                    , the majority of transactions to retail customers) would not contribute to the Commission's transparency mission and are not subject to reporting. We believe that this is a “bright-line” rule easily understood by potential respondents.
                    <SU>55</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         NGSA's request for rehearing or clarification of this issue is, therefore, denied.
                    </P>
                </FTNT>
                <P>
                    35. While Order No. 704 utilized the phrase “retail” transactions interchangeably with “end-use” transactions,
                    <SU>56</SU>
                    <FTREF/>
                     the overall thrust of our order was that transactions that are typically perceived to be at retail are not reportable while transactions that utilize, contribute to, or may contribute to price indices should be reportable. Depending upon the type of transactions involved, end-use transactions can have a substantial impact on price formation and the functioning of the wholesale markets, particularly in localized areas.
                </P>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         
                        <E T="03">See, e.g.</E>
                        , Order No. 704 at PP 60, 89, and 90.
                    </P>
                </FTNT>
                <P>
                    36. While precise data is not readily available (indeed, obtaining that data is one of the goals of Form No. 552), it is our experience and industry common knowledge that many end-use transactions utilize price indices and/or could be relied upon to form price indices. End-use transactions, specifically transactions involving large consumers of natural gas that compete directly with wholesale market participants, are very relevant to the Commission's transparency mission. For example, use of natural gas for power generation has increased markedly since 2000. According to annual figures from the Energy Information Administration (EIA), natural gas used to produce electric power is up from 14.2 Bcf/d in 2000 to 18.8 Bcf/d in 2007, an increase of 32 percent. As a result, natural gas generation's share of overall gas use is up, too. In 2000, EIA figures indicate 
                    <PRTPAGE P="55732"/>
                    that natural gas used for power generation accounted for 18 percent of total U.S. natural gas consumption; by the end of 2007 it represented 30 percent.
                    <SU>57</SU>
                    <FTREF/>
                     On a peak day in the summer, natural gas generation's share of gas use can be much higher. According to EIA, the U.S. delivered a total of 21.3 Tcf of natural gas to consumers in 2007 or on average about 58.3 Bcf per day.
                    <SU>58</SU>
                    <FTREF/>
                     On August 8, 2007, estimates of gas use for power generation reached 38 Bcf/d or 65 percent of 2007 average daily gas use.
                    <SU>59</SU>
                    <FTREF/>
                     Moreover, in many regional power markets, natural gas is the marginal fuel during the majority of hours power plants are being dispatched, therefore a better understanding of how natural gas indices are formed will aid the Commission and the public in understanding power market dynamics. For these reasons, we conclude that where a transaction could contribute to the formation of price indices and/or relies upon a price index, the transaction should be reportable even if the reporting entity is a natural gas end-user.
                </P>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         Derived from information provided by EIA on their Natural Gas Navigator Web site, 
                        <E T="03">http://tonto.eia.doe.gov/dnav/ng/hist/n3045us2a.htm</E>
                        .
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         Derived from information provided by EIA on their Natural Gas Navigator Web site, 
                        <E T="03">http://tonto.eia.doe.gov/dnav/ng/ng_sum_lsum_dcu_nus_a.htm</E>
                        .
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         Derived from the “U.S. Power Burn Report”, Bentek Energy, LLC.
                    </P>
                </FTNT>
                <P>
                    37. Requiring end-users to supply transaction data if the transaction utilizes, contributes to, or could contribute to price index formation is well within EPAct 2005's Congressional mandate. The Commission accurately stated in Order No. 704 that price formation in natural gas markets makes no distinction between transactions that are traditionally jurisdictional to the Commission and those that are not.
                    <SU>60</SU>
                    <FTREF/>
                     Congress, recognizing this fact, gave the Commission expansive jurisdiction under the transparency provisions of EPAct 2005. The Commission's traditional jurisdiction under sections 4, 5, and 7 of the NGA is limited to “natural gas companies.” 
                    <SU>61</SU>
                    <FTREF/>
                     In contrast, section 23(a) of the NGA directs the Commission “to facilitate price transparency in markets for the sale or transportation of physical natural gas in interstate commerce” 
                    <SU>62</SU>
                    <FTREF/>
                     including obtaining information from “any market participant.” 
                    <SU>63</SU>
                    <FTREF/>
                     There is no applicable statutory limitation on the collection of information that may involve transportation through distribution-level facilities, as applies to the Commission's traditional jurisdiction.
                    <SU>64</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         Order No. 704 at P 6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         15 U.S.C. section 717b-717i.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>62</SU>
                         15 U.S.C. section 717t-2(a)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         15 U.S.C. section 717t-2(a)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>64</SU>
                         Section 1(b) of the NGA, 15 U.S.C. section 717(b), provides in part that the Commission's jurisdiction generally does not apply to “the local distribution of natural gas.”
                    </P>
                </FTNT>
                <P>
                    38. In addition, the first sentence of section 23(a)(2) gives the Commission broad authority to “prescribe such rules as the Commission determines necessary and appropriate to carry out the purposes of this section,” 
                    <E T="03">i.e.</E>
                     facilitating price transparency. This broad grant of authority is followed, in the second sentence of the section, with the requirement that the “rules shall provide for the dissemination on a timely basis of information about the availability and prices of natural gas sold at wholesale and in interstate commerce.” The requirement in the second sentence, including the reference to “gas sold at wholesale,” does not limit the broad authority granted by the first sentence. Rather, the rules required by the second sentence should be viewed as a subset of the rules the first sentence of section 23(a)(2) authorizes the Commission to adopt. Put another way, section 23(a)(2) should be interpreted as providing that the Commission 
                    <E T="03">may</E>
                     adopt rules collecting information about any transactions, including non-wholesale end-use transactions, if necessary to facilitate price transparency, but such rules 
                    <E T="03">must</E>
                     include the collection of information about wholesale transactions in interstate commerce.
                </P>
                <P>
                    39. This interpretation is buttressed by the fact that section 23(a)(3)(A) expressly permits the Commission to obtain “the information described in paragraph (2) from any market participant,” a term which includes end-users. EPAct 2005's 
                    <E T="03">de minimis</E>
                     threshold requirement in section 23(d)(2) provides further support for this position. That provision states:
                </P>
                <EXTRACT>
                    <P>
                        The Commission shall not require natural gas producers, processors, 
                        <E T="03">or users</E>
                         who have a 
                        <E T="03">de minimis</E>
                         market presence to comply with the reporting requirements of this section.
                        <SU>65</SU>
                        <FTREF/>
                    </P>
                </EXTRACT>
                <FTNT>
                    <P>
                        <SU>65</SU>
                         15 U.S.C. section 717t-2(d)(2) (emphasis added).
                    </P>
                </FTNT>
                <P>
                    The logical corollary to this Congressional directive is that a user that has greater than 
                    <E T="03">de minimis</E>
                     market presence could be made subject to the reporting requirement. By establishing a 
                    <E T="03">de minimis</E>
                     threshold volume of 2.2 million MMBtu (and, as further explained herein, exempting traditional retail transactions from reporting), the Commission appropriately limits reporting by end-users only to those users with a more than a 
                    <E T="03">de minimis</E>
                     market presence and only to those end-use transactions that utilize, contribute to, or could contribute to price index formation.
                </P>
                <P>40. While a large industrial end-user may not be a customer “at wholesale,” it is doubtless a “market participant” in the interstate wholesale energy market and its actions may have a direct impact on the wholesale market or market indices, especially in a localized area. We also note that the collection of information on an annual basis is qualitatively different than our customary regulation of rates, terms, and conditions applicable to natural gas companies. Requiring reporting from large end-users that engage in 2.2 million MMBtu of annual sales or purchase transactions (other than transactions associated with bundled retail tariff service) is a conservative outcome compared to the broad authority granted to us by Congress in section 23 of the NGA. Our approach strikes a balance between the data that the Commission requires to meet its transparency-related obligations and the burden placed upon market participants to provide this data.</P>
                <P>
                    41. However, not all end-use transactions have the potential to contribute to the formation of price indices or rely upon price indices. For example, traditional retail transactions, even those involving annual volumes greater than the 
                    <E T="03">de minimis</E>
                     threshold, neither utilize an index for a price nor contribute to index price formation. These retail transactions are not relevant to the Commission's transparency goals. A bundled retail transaction through an LDC at a state-approved tariff rate is properly excluded from purchase and sales volumes to be reported on Form No. 552.
                    <SU>66</SU>
                    <FTREF/>
                     The reporting burden on retail consumers would greatly outweigh any minimal transparency benefit. To the extent that a potential respondent purchases or sells gas at a bundled retail tariff rate, it should not 
                    <PRTPAGE P="55733"/>
                    count those volumes towards the 
                    <E T="03">de minimis</E>
                     threshold and, if required to submit Form No. 552, it would not include those volumes in its report.
                    <SU>67</SU>
                    <FTREF/>
                     We note that this “bright-line” clarification would also resolve NGSA's concerns regarding a selling entity's ability to identify what purchasers are consuming gas—if gas is sold by an LDC under a bundled retail tariff rate, then it need not be reported.
                </P>
                <FTNT>
                    <P>
                        <SU>66</SU>
                         We have drawn a parallel distinction in the electric context. In Order No. 888, the Commission exercised its jurisdiction over unbundled transmission to end-users in interstate commerce, yet declined to exert jurisdiction over bundled retail transmission. 
                        <E T="03">See</E>
                          
                        <E T="03">Promoting Wholesale Competition Through Open Access Non-discriminatory Transmission Services by Public Utilities; Recovery of Stranded Costs by Public Utilities and Transmitting Utilities,</E>
                         Order No. 888, 61 FR 21540 (May 10, 1996), FERC Stats. &amp; Regs. ¶ 31,036, at p. 31,781 (1996). The U.S. Supreme Court approved of this distinction in 
                        <E T="03">New York</E>
                         v. 
                        <E T="03">FERC,</E>
                         535 U.S. 1, 28 (2002). While not a jurisdictional question, in this rulemaking, we incorporate a similar distinction between unbundled natural gas transactions to consumers (which are reportable in Form No. 552 if they utilize or contribute to the formation of a price index) and bundled transactions through an LDC subject to state-approved tariff rates (which are not reportable).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>67</SU>
                         One caveat is that, if the end-user or other market participant holds a blanket certificate from the Commission, it must, at a minimum, submit the identification and price reporting data required on Form No. 552.
                    </P>
                </FTNT>
                <P>
                    42. This proposed approach is similar, though not identical, to the Commission's jurisdictional reach over natural gas transportation service to end-users. FERC exerts its customary jurisdiction over direct transportation of natural gas from an interstate pipeline to an end-user.
                    <SU>68</SU>
                    <FTREF/>
                     However, the Commission has traditionally declined to exercise jurisdiction over transportation to “retail customers in a localized geographical area behind either a town border station or behind facilities * * * that connect to rural delivery points outside the boundaries of towns.” 
                    <SU>69</SU>
                    <FTREF/>
                     Where transportation to an end-user occurs in interstate commerce and not as part of local distribution, the Commission has jurisdiction.
                </P>
                <FTNT>
                    <P>
                        <SU>68</SU>
                         
                        <E T="03">See, e.g.</E>
                        , 
                        <E T="03">Public Utilities Commission of the State of California</E>
                         v. 
                        <E T="03">FERC,</E>
                         900 F.2d 269 (D.C. Cir. 1990).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>69</SU>
                         
                        <E T="03">Kinder Morgan Interstate Gas Transmission LLC,</E>
                         99 FERC ¶ 61,186, at n.30 (2002).
                    </P>
                </FTNT>
                <P>
                    43. We conclude that exempting from reporting those volumes associated with bundled retail transactions made at state-approved tariff rates, while including volumes associated with direct pipeline-to-end-user and other end-user transactions, is appropriate. This modification regarding the reportability of certain end-use transactions necessitates changes to the language of Form No. 552.
                    <SU>70</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>70</SU>
                         One such modification is the definition of “Physical Natural Gas Transactions” in the Definitions portion of current Form No. 552. The definition clearly indicates that reportable volumes are 
                        <E T="03">only</E>
                         those that utilize, contribute to, or may contribute to the formation of price indices. The definition also explicitly excludes volumes associated with bundled retail sales and purchases at state-approved tariff rates.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">E. Respondents Need Not Distinguish Between Transactions Based Upon Location</HD>
                <P>
                    44. Order No. 704 provided that a market participant must categorize transaction volumes by whether each transaction was made at a “reportable location.” Reportable locations are locations where index developers currently collect fixed-price information for transactions with Next-Day or Next-Month Delivery obligations, and produce index prices. Thus, Order No. 704 tied the meaning of “fixed-price” reported volumes to volumes that may be reported to index developers at specific points. To this end, we directed our staff to list on the Commission's Web site all reportable locations at which fixed-price volumes were to be reported on Form No. 552.
                    <SU>71</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>71</SU>
                         Order No. 704 at PP 60 and 101-102.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Requests for Rehearing and Clarification</HD>
                <P>
                    45. NGSA requests rehearing of Order No. 704 so as to require submission of data at all trading locations rather than limited to specific reportable locations.
                    <SU>72</SU>
                    <FTREF/>
                     NGSA argues that this approach would be consistent with the Policy Statement on price reporting.
                    <SU>73</SU>
                    <FTREF/>
                     Further, NGSA states that designated “reportable locations” will change over time, hampering the Commission's long-term analysis of the market.
                    <SU>74</SU>
                    <FTREF/>
                     NGSA argues that limiting reported data only to specific reportable locations would be more burdensome to most respondents than reporting all aggregate, relevant data.
                    <SU>75</SU>
                    <FTREF/>
                     Lastly, NGSA asserts that different index developers utilize different means to collect data at the same index point and, thus, data collected from market participants for particular reportable points will not offer a reasonable comparison to reported indices.
                    <SU>76</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>72</SU>
                         NGSA comments at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>73</SU>
                         
                        <E T="03">Id.</E>
                         at 6 (citing the Policy Statement).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>74</SU>
                         
                        <E T="03">Id.</E>
                         at 6-7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>75</SU>
                         
                        <E T="03">Id.</E>
                         at 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>76</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>46. Participants at the technical conferences echoed some of these themes. The NiSource Companies (NiSource) and Encana, for example, questioned how reporting was to be accomplished for certain reportable locations given that different reporting services defined the locations in multiple ways.</P>
                <HD SOURCE="HD3">Commission Determination</HD>
                <P>47. We grant rehearing of Order No. 704 on this issue and provide that respondents need not categorize volumes based upon whether such volumes relate to transactions at specific price index locations. We agree with NGSA that: (1) It would be substantially less burdensome for market participants to provide aggregate data regarding their transactions than to differentiate between volumes that occur within or outside reportable locations; (2) defining workable “reportable locations” would be difficult, would require substantial detail regarding geographic scope and types of transactions at specific locations, and would unduly complicate respondents' Form No. 552 responses; and (3) specific reportable locations would change on a yearly basis, limiting the value of data collected by location. We also understand that participants at the technical conferences indicated a substantial preference for this modification.</P>
                <P>
                    48. The Policy Statement provides that the minimum standards for data providers include a commitment to report “each bilateral, arm's-length transaction between non-affiliated companies in the physical (cash) markets 
                    <E T="03">at all trading locations.</E>
                    ” 
                    <SU>77</SU>
                    <FTREF/>
                     Modification of Form No. 552 to eliminate data collected at specific reporting locations would make the annual reporting obligation consistent with the Policy Statement. Consequently, for respondents that already comply with the Policy Statement standards, data collection and reporting on Form No. 552 would be significantly less burdensome. In fact, we believe that it would be easier for most entities that 
                    <E T="03">do not</E>
                     comply with the Policy Statement standards to provide aggregate data for all reportable transactions rather than to segregate data regarding transactions at specific locations.
                </P>
                <FTNT>
                    <P>
                        <SU>77</SU>
                         Policy Statement at P 34 (emphasis added).
                    </P>
                </FTNT>
                <P>49. Further, comments by conference participants and NGSA's request for rehearing make clear that it would be administratively difficult to geographically define each reportable location in a way that would capture all transactions that were eligible for reporting to the various price indices. This is due to the fact that different data collection methodologies are used by index developers at the same point as well as the fact that different index developers accept different transactions from these points to form indices.</P>
                <P>
                    50. For these reasons, we grant rehearing of Order No. 704 and determine that respondents need only provide aggregated data for reportable transactions at all transaction locations. Respondents need not provide data segregated by reportable location.
                    <SU>78</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>78</SU>
                         Consistent with the determination, we will no longer direct the Commission's staff to retain a list of reportable locations on the Commission's Web site.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">F. Balancing, Cash-out, Operational, and In-Kind Transactions Are Reportable</HD>
                <P>
                    51. In Order No. 704, we required market participants to report sale and purchase volumes related to cash-outs, 
                    <PRTPAGE P="55734"/>
                    imbalance make-ups, and operations.
                    <SU>79</SU>
                    <FTREF/>
                     We noted that, while some volumes related to such transactions are not utilized to create price indices, many volumes do refer to or utilize such indices.
                    <SU>80</SU>
                    <FTREF/>
                     The Commission concluded that the data collected from such transactions is useful in assessing how spot prices are being used commercially. Specifically, the order required market participants to include on Form No. 552 volumes related to royalty-in-kind transactions and purchases and sales related to production and gathering functions.
                    <SU>81</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>79</SU>
                         Order No. 704 at P 107.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>80</SU>
                         
                        <E T="03">Id.</E>
                         P 108.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>81</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Requests for Rehearing or Clarification</HD>
                <P>
                    52. Regarding transactions on interstate pipelines, Shell and NGSA seek rehearing of Order No. 704 so as to exclude cash-out, imbalance makeup, and operational volumes from the realm of reportable transactions. Both Shell and NGSA argue that such transactions do not affect the interstate natural gas market, though they may often rely upon natural gas indices for their price.
                    <SU>82</SU>
                    <FTREF/>
                     Shell states that data regarding such transactions may not reflect actual market activity as prices may vary according to whether the pipeline or shipper owes gas and there is a one-month lag on the timing of many makeup transactions.
                    <SU>83</SU>
                    <FTREF/>
                     For this reason, the use of index prices in makeup transactions, Shell argues, does not reflect the value of natural gas for purposes of assessing wholesale natural gas spot markets and will actually distort relevant data received by the Commission.
                    <SU>84</SU>
                    <FTREF/>
                     In the alternative, if rehearing on this point is denied, Shell seeks clarification that, if a pipeline provides imbalance cash-out data, then shippers need not provide the identical data on Form No. 552.
                    <SU>85</SU>
                    <FTREF/>
                     NGSA reiterates many of these arguments, adds that pipeline balancing transactions are governed by the pipeline's tariff, and argues that balancing should not be considered a purchase or sale in the wholesale market.
                    <SU>86</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>82</SU>
                         Shell comments at 14-15; NGSA comments at 11.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>83</SU>
                         Shell comments at 14-15.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>84</SU>
                         
                        <E T="03">Id.</E>
                         at 15.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>85</SU>
                         
                        <E T="03">Id.</E>
                         at 16.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>86</SU>
                         NGSA comments at 9-10. NGSA repeats many of these same arguments in its subsequent supplemental comments at 4-6. 
                        <E T="03">See also</E>
                         Shell comments at 15-16 (stating in passing that imbalance trading transactions should not be considered a purchase or sale).
                    </P>
                </FTNT>
                <P>
                    53. Regarding intrastate pipelines, Copano seeks clarification or rehearing regarding whether “non-interstate pipeline” market participants must report, and include for purposes of meeting the 
                    <E T="03">de minimis</E>
                     threshold, volumes related to cash-outs and other operational activities.
                    <SU>87</SU>
                    <FTREF/>
                     Copano argues, much as does Shell and NGSA regarding interstate pipelines, that these sorts of transactions are operational in nature, are not based on market conditions, and provide no benefit to the Commission's transparency goals.
                    <SU>88</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>87</SU>
                         Copano comments at 8-9.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>88</SU>
                         
                        <E T="03">Id.</E>
                         at 9-10.
                    </P>
                </FTNT>
                <P>
                    54. Regarding transactions involving end-users, AF&amp;PA and IECA, in a joint submittal, seek clarification or rehearing to exempt balancing-type transactions from reporting. Additionally, these entities request that blanket certificate holders under section 284.402, that hold such a certificate solely by virtue of their status as a pipeline customer engaged in balancing or cash out transactions pursuant to a consumer level gas service contract, be allowed to forego filing of Form No. 552.
                    <SU>89</SU>
                    <FTREF/>
                     AF&amp;PA and IECA argue that the benefit of obtaining this information is minimal compared to the burden of reporting the data. They contend that: (1) Such transactions are often “involuntary” and that it may be very difficult for end-users to determine whether their balancing activity exceeds the 
                    <E T="03">de minimis</E>
                     threshold; (2) the applicable volumes already likely are reported at the pipeline level; and (3) balancing transactions that occur pursuant to individual end-use contracts will not factor appreciatively into wholesale price formation.
                    <SU>90</SU>
                    <FTREF/>
                     They also state that it is likely that many end-user blanket certificate holders under section 284.402 do not know that they hold such certificate authority or that balancing provisions in existing contracts with pipelines could trigger the rule's annual reporting requirement.
                    <SU>91</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>89</SU>
                         AF&amp;PA/IECA comments at 6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>90</SU>
                         
                        <E T="03">Id.</E>
                         at 4-6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>91</SU>
                         
                        <E T="03">Id.</E>
                         at 6-7.
                    </P>
                </FTNT>
                <P>
                    55. Shell seeks clarification that “in-kind” balancing transactions of all stripes are not reportable transactions under the rule as such transactions do not involve a “sale” or a “purchase.” 
                    <SU>92</SU>
                    <FTREF/>
                     Relatedly, NGSA requests clarification or rehearing, as necessary, that the entity that purchases or sells royalty-in-kind interests is responsible for reporting royalty-in-kind transactions—not well operators.
                    <SU>93</SU>
                    <FTREF/>
                     NGSA argues that well operators do not necessarily have knowledge of the contractual relations of royalty interest holders.
                    <SU>94</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>92</SU>
                         Shell comments at 15-16.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>93</SU>
                         NGSA comments at 12-13.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>94</SU>
                         
                        <E T="03">Id.</E>
                         at 12.
                    </P>
                </FTNT>
                <P>
                    56. Shell also seeks clarification regarding the location that cash-out, in-kind, or other imbalance transactions occur for purposes of determining whether the transaction occurs at a “reportable location.” 
                    <SU>95</SU>
                    <FTREF/>
                     Shell requests further clarification as to whether such transactions are considered “next-day,” “next-month,” or “other” for purposes of completing Form No. 552.
                    <SU>96</SU>
                    <FTREF/>
                     Finally, Shell seeks clarification that all production-related balancing activities, such as those between producers and working interest owners, are not to be reported.
                    <SU>97</SU>
                    <FTREF/>
                     We understand that producers at the technical conferences requested similar clarification from staff.
                </P>
                <FTNT>
                    <P>
                        <SU>95</SU>
                         Shell comments at 17.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>96</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>97</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    57. In supplemental comments, NGSA suggests that, if the Commission continues to require the submission of cash-out transaction data (including thermal reduction volumes), such data should be reported on a separate line on Form No. 552.
                    <SU>98</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>98</SU>
                         NGSA supplemental comments at 4.
                    </P>
                </FTNT>
                <P>58. A significant number of commenters at the technical conferences raised questions regarding balancing transactions of various types. Commenters wished to know whether balancing transactions were to be reported on a “net” basis for each year or whether activity in each direction (cash-ins and cash-outs) should be separately accounted.</P>
                <HD SOURCE="HD3">Commission Determination</HD>
                <P>59. We deny the requests for rehearing. Balancing, cash-out, operational, in-kind, and similar transactions must be reported on Form No. 552 if they rely upon, contribute to, or could contribute to a price index.</P>
                <P>
                    60. Section 23 of the NGA requires that our data collection have “due regard” for “the integrity of [the physical natural gas] markets, [and] fair competition.” 
                    <SU>99</SU>
                    <FTREF/>
                     Public confidence in the reporting of natural gas prices to gas price index developers and the reasonable use and reliance on such indices in the market is squarely within the Commission's purview. This includes not just transactions that 
                    <E T="03">directly</E>
                     impact wholesale price formation, but also transactions that reference indices. As we stated in Order No. 704, one of the goals of Form No. 552 is to allow the Commission to “not only understand the transactions used to formulate price indices; it is to understand how influential price indices are in the overall transacting of 
                    <PRTPAGE P="55735"/>
                    natural gas in U.S. wholesale markets.” 
                    <SU>100</SU>
                    <FTREF/>
                     It has been our experience that a significant number of balancing, cash-out, and similar transactions include references to price indices. Understanding the magnitude of this reliance on price indices is therefore a legitimate policy goal. Form No. 552 will provide this information and we can conceive of no less intrusive way to obtain this relevant data.
                </P>
                <FTNT>
                    <P>
                        <SU>99</SU>
                         15 U.S.C. section 717t-2(a)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>100</SU>
                         Order No. 704 at P 73.
                    </P>
                </FTNT>
                <P>
                    61. In any event, we do not agree with the proposition that balancing transactions, as described by commenters, could not themselves contribute to the formation of price indices. The fact that a purchase or sale is made for operational or balancing, rather than market, reasons is irrelevant. This includes, for example, base or cushion gas purchases for storage facilities, balancing between pipelines or between a supplier and a customer, and purchases of gas for compression. Some portion of these transactions could be utilized to establish index prices. Balancing, cash-out, operational, and in-kind transactions should therefore be reportable on Form No. 552 to the same extent as other types of transactions.
                    <SU>101</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>101</SU>
                         As with the reporting of purchase and sale transactions, we clarify that balancing transactions should be reported for both cash-ins and cash-outs and not on a net basis.
                    </P>
                </FTNT>
                <P>
                    62. Further, reporting of balancing transactions by 
                    <E T="03">all</E>
                     entities subject to the annual reporting requirement is entirely appropriate. Specifically, balancing transactions involving end-users are likely a significant total of natural gas contracts that reference price indices. Understanding the prevalence of such contracts may allow the Commission and other market observers to assess weaknesses in price index development.
                    <SU>102</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>102</SU>
                         Technical requests regarding how these types of transactions should be reported on Form No. 552 are addressed through clarifications discussed elsewhere in this order. Regarding the request for clarification by AF&amp;PA and IECA on this point, the Commission declines to clarify the Final Rule in the manner suggested by the commenters. While AF&amp;PA and IECA did not supply sufficient detail in their request regarding the transactions of concern to their members for us to offer more specific guidance, we expect that the clarifications provided in this order will allow these organizations' members to determine both whether they must submit Form No. 552 and the transaction volumes that must be reported therein.
                    </P>
                </FTNT>
                <P>63. For all these reasons, we continue to require that reportable sales and purchases on Form No. 552 include balancing, cash-out, operational, and in-kind transactions that utilize, contribute to, or could contribute to the formation of a price index.</P>
                <HD SOURCE="HD2">G. Safe Harbor</HD>
                <P>
                    64. In Order No. 704, we noted our intent not to prosecute or penalize companies for inadvertent reporting errors on Form No. 552.
                    <SU>103</SU>
                    <FTREF/>
                     However, we drew a clear distinction between the safe harbor provided to voluntary reporting to price index publishers in the Policy Statement and the mandatory annual report required by Order No. 704.
                    <SU>104</SU>
                    <FTREF/>
                     The Commission rejected calls to include a similar safe harbor for the submission of Form No. 552.
                </P>
                <FTNT>
                    <P>
                        <SU>103</SU>
                         Order No. 704 at P 114.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>104</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Requests for Rehearing or Clarification</HD>
                <P>
                    65. Shell notes that the Commission stated that it “does not intend to prosecute or penalize parties for inadvertent errors in reporting,” but did not include a safe harbor provision for market participants that attempt to comply in good faith with Order No. 704. Shell urges the Commission to adopt an explicit, rebuttable presumption of good faith as it did in the Policy Statement on price reporting.
                    <SU>105</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>105</SU>
                         Shell comments at 29-31.
                    </P>
                </FTNT>
                <P>
                    66. Powerex Corporation (Powerex) notes that, in the April 2007 NOPR, the Commission responded to queries from “several data providers * * * as to whether they may report certain classes of products traded, but not others.” 
                    <SU>106</SU>
                    <FTREF/>
                     The April 2007 NOPR stated that “a data provider remains eligible for the safe harbor provisions if it reports certain products, but not others, provided that it provides all of the same type of transactions and that it notifies the Commission which products it will report in its annual filing or other notification.” 
                    <SU>107</SU>
                    <FTREF/>
                     The Commission stated that it would repeat this safe harbor clarification in the final rule. However, no such clarification was included in Order No. 704.
                </P>
                <FTNT>
                    <P>
                        <SU>106</SU>
                         Powerex comments at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>107</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    67. In supplemental comments to the technical conferences, AGA requests that the Commission institute a “pilot program” for compliance with Order No. 704 for calendar year 2008 data.
                    <SU>108</SU>
                    <FTREF/>
                     AGA suggests that the Commission not penalize market participants that make good faith efforts to complete Form No. 552 but “make errors” or “include data that is inconsistent with the way other market participants have completed the form.” 
                    <SU>109</SU>
                    <FTREF/>
                     NGSA, in supplemental comments, requests that the Commission adopt a safe harbor for 2008 calendar-year data, including allowing respondents “to base information * * * on transaction data collected using existing processes and systems.” 
                    <SU>110</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>108</SU>
                         AGA supplemental comments at 2-3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>109</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>110</SU>
                         NGSA supplemental comments at 3.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Commission Determination</HD>
                <P>68. The Commission herein adopts a one-year safe harbor, covering transactions occurring in calendar year 2008 and reported on Form No. 552 on May 1, 2009. However, we decline to extend this safe harbor for additional calendar year reporting.</P>
                <P>
                    69. The Policy Statement includes a safe harbor provision that grants a data provider that adopts the Policy Statement standards a rebuttable presumption that data submitted to index developers is accurate, timely, and submitted in good faith.
                    <SU>111</SU>
                    <FTREF/>
                     However, a similar perpetual safe harbor is not warranted regarding the reporting of data on Form No. 552. The Policy Statement set forth standards that data providers could choose to adopt should they voluntarily elect to provide data to price index developers. One goal of the Policy Statement was to “encourage [industry participants] voluntarily to report energy transactions to the providers of price indices.” 
                    <SU>112</SU>
                    <FTREF/>
                     The safe harbor that we adopted in the Policy Statement was a direct extension of this policy goal.
                </P>
                <FTNT>
                    <P>
                        <SU>111</SU>
                         
                        <E T="03">See</E>
                         Policy Statement at P 37.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>112</SU>
                         
                        <E T="03">Id.</E>
                         P 3.
                    </P>
                </FTNT>
                <P>70. Form No. 552 is a mandatory annual filing adopted consistent with EPAct 2005, not the voluntary reporting of price data to an index developer. There is no policy need to provide an incentive for the filing of Form No. 552 similar to the encouragement to reporting price data to index developers. Other mandatory forms, such as FERC Form No. 2, do not include such a safe harbor. For this reason, we are not persuaded that a perpetual safe harbor is warranted.</P>
                <P>
                    71. However, a one-year safe harbor (including data collected for calendar year 2008 and reported by May 1, 2009) is appropriate. Market participants have begun data collection for the current calendar year without the benefit of an order on rehearing of Order No. 704. We acknowledge that this Order on Rehearing and Clarification is issued well after respondents' data collection has been underway for 2008. Further, we herein offer a number of clarifications of Order No. 704 that may impact such data collection activities. A one-time safe harbor for the 2009 Form No. 552 is, under these unique circumstances, reasonable. Consistent with the Policy Statement, the 
                    <PRTPAGE P="55736"/>
                    Commission finds that respondents submitting Form No. 552 in 2009 will benefit from a rebuttable presumption that the data provided is accurate and submitted in good faith. Further, we do not intend to penalize respondents for errors in reporting on Form No. 552 provided that respondents use reasonable efforts to comply with the regulations regarding and instructions for Form No. 552. We emphasize that the Commission expects respondents submitting Form No. 552 in 2009 to do so in good faith and on a timely basis.
                </P>
                <HD SOURCE="HD2">H. Additional Clarifications</HD>
                <P>72. In addition to resolution of the rehearing and clarification issues discussed above, we clarify a number of minor or technical aspects of Form No. 552.</P>
                <HD SOURCE="HD3">Some Volumes Associated With Transactions Outside the Lower 48 States Should Be Reported</HD>
                <P>
                    73. The Canadian Association of Petroleum Producers (CAPP), Canadian Suppliers,
                    <SU>113</SU>
                    <FTREF/>
                     and Powerex request clarification, or in the alternative, rehearing, that reported data should include only sales or purchases made inside the geographic boundaries of the United States.
                    <SU>114</SU>
                    <FTREF/>
                     Marathon Oil Company (Marathon) and NGSA request clarification or rehearing regarding the scope of the rule vis-à-vis natural gas production in Alaska.
                    <SU>115</SU>
                    <FTREF/>
                     AGA, in supplemental comments, also requests that the Commission address this issue.
                    <SU>116</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>113</SU>
                         Collectively, Encana Marketing (USA) Inc., Nexen Marketing (USA) Inc., Petro-Canada Hydrocarbons Inc., and Talisman Energy Inc.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>114</SU>
                         CAPP comments at 1; Canadian Suppliers comments at 3; Powerex comments at 6-7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>115</SU>
                         Marathon comments at 4-5; NGSA comments at 13-14.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>116</SU>
                         AGA supplemental comments at 6-9.
                    </P>
                </FTNT>
                <P>74. Regarding transactions involving possible international transportation, we clarify that: (1) Volumes originating outside the lower 48 states and delivered at locations outside the lower 48 states are not reportable; (2) volumes originating from inside the lower 48 states and delivered outside the lower 48 states are reportable; and (3) volumes delivered inside the lower 48 states are reportable. Thus, any volumes that originate or are delivered into the lower 48 states should be reported on Form No. 552 to the same extent as purely domestic volumes. Form No. 552 is designed to capture all transactions that reference price indices or that could contribute to price indices and these types of international transactions are not categorically excluded.</P>
                <HD SOURCE="HD3">Transactions Related to Exploration Activities, Production Area Operations, and Gathering Functions Are Not Exempted From Reporting</HD>
                <P>
                    75. Shell and NGSA request clarification or rehearing of Order No. 704 so as to categorically exclude exploration activities, production area operations, and gathering functions from reporting. They argue that the entirety of the Commission's rationale for including these transactions is that these transactions often make use of price indices.
                    <SU>117</SU>
                    <FTREF/>
                     They also argue that these transactions do not impact the wholesale interstate gas market and are excluded from traditional NGA regulation under section 1(b) of the Act.
                    <SU>118</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>117</SU>
                         Shell comments at 9; NGSA comments at 11-12.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>118</SU>
                         Shell comments at 10; NGSA comments at 11.
                    </P>
                </FTNT>
                <P>
                    76. In Order No. 704, the Commission stated that, “while these transactions may not affect the formation of price indices in wholesale markets, these transactions often make use of price indices * * * to the extent that transfers of value take place based on price indices, it is important that the Commission and other market observers be able to understand the extent of that transfer and its dependency on price indices as well.” 
                    <SU>119</SU>
                    <FTREF/>
                     As explained in the order, determining the scope of price index reliance in the market is a significant goal of this rulemaking. The public availability of this data will increase market transparency and confidence. Transactions involving exploration activities, production area operations, and gathering functions that rely upon or could contribute to the creation of price indices are to be reported in the same manner as other types of transactions.
                </P>
                <FTNT>
                    <P>
                        <SU>119</SU>
                         Order No. 704 at P 108.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Transactions Involving Unprocessed Gas Are Not Reportable</HD>
                <P>
                    77. Hess Corporation (Hess) requests rehearing of Order No. 704 so as to exclude entities engaged in transactions behind a processing plant priced pursuant to a percentage-of-proceeds contract under which the producer is entitled to receive a percentage of the proceeds realized by the buyer upon resale of the natural gas.
                    <SU>120</SU>
                    <FTREF/>
                     Similarly, the Oklahoma Independent Petroleum Association (OIPA) seeks rehearing of Order No. 704 so as to exempt producers of natural gas that sell wellhead gas at the initial first sales point under a percentage of proceeds contract.
                    <SU>121</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>120</SU>
                         Hess comments at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>121</SU>
                         OIPA comments at 2.
                    </P>
                </FTNT>
                <P>
                    78. We agree with Hess and OIPA that transactions regarding unprocessed gas should not be reported on Form No. 552 and should not be counted when determining whether an entity falls below the 
                    <E T="03">de minimis</E>
                     threshold. Transactions involving unprocessed natural gas are not relevant to wholesale price formation.
                </P>
                <HD SOURCE="HD3">A Customer of an Asset Manager Is Responsible for Reporting Volumes Managed by the Asset Manager</HD>
                <P>
                    79. Order No. 704 states that asset managers may not aggregate customer volumes and report the same on Form No. 552.
                    <SU>122</SU>
                    <FTREF/>
                     NGSA requests that the Commission clarify that individual customers of asset managers are responsible for the submission of Form No. 552 and reporting volumes managed by the asset manager as well as any other reportable sales or purchases.
                    <SU>123</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>122</SU>
                         Order No. 704 at P 98.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>123</SU>
                         NGSA comments at 15.
                    </P>
                </FTNT>
                <P>
                    80. We clarify the rule in the manner suggested by NGSA. In Order No. 704, we stated that asset managers may not report aggregated information for their customers.
                    <SU>124</SU>
                    <FTREF/>
                     However, this statement should not be read so as to relieve customers that hire asset managers from their obligation to file Form No. 552 if they are required to do so. Individual customers of asset managers (assuming that their activities do not fall below the 
                    <E T="03">de minimis</E>
                     threshold) are responsible for reporting volumes both as managed by an asset manager and independently sold and purchased. The Commission also notes that an asset manager, to the extent that its market activities are not undertaken on behalf of an asset management client, may itself be required to submit Form No. 552.
                </P>
                <FTNT>
                    <P>
                        <SU>124</SU>
                         Order No. 704 at P 98.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">A Public Joint Action Agency May Report an Aggregate of Members' Volumes</HD>
                <P>
                    81. Order No. 704 does not directly address the filing of Form No. 552 by public joint action agencies. APGA requests clarification that a public joint action agency may aggregate members' annual volume data for purposes of the report.
                    <SU>125</SU>
                    <FTREF/>
                     APGA notes that, in Order No. 704, aggregation is permitted between privately-owned affiliates.
                    <SU>126</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>125</SU>
                         APGA comments at 2-3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>126</SU>
                         
                        <E T="03">Id.</E>
                         at 2 (citing Order No. 704 at P 94).
                    </P>
                </FTNT>
                <P>
                    82. We clarify that public joint action agencies, such as certain members of APGA, will be allowed to report members' data on an aggregate basis in the same manner as corporate affiliates. We see no reason to treat public joint action agencies differently from private 
                    <PRTPAGE P="55737"/>
                    corporate families. Allowing a public joint action agency to report members' volumes will significantly reduce the reporting burden on those members. Of course, members of public joint action agencies and affiliates within a corporate family remain free to report separately, should they wish. Additionally, we clarify that arms-length transactions between members of a public joint action agency may be reportable transactions.
                </P>
                <HD SOURCE="HD3">Physically-Settled Non-NYMEX Options Are Reportable</HD>
                <P>
                    83. Order No. 704 excluded from reporting NYMEX options that physically settle. The rationale for this exclusion was that data regarding these transactions did not necessarily relate to fixed-price spot price formation, the data was readily available to the public through NYMEX, and reporting these volumes on Form No. 552 would be duplicative and burdensome.
                    <SU>127</SU>
                    <FTREF/>
                     However, Order No. 704 does not explicitly address non-NYMEX transactions that result in physical flow. When such options are exercised, they result in physical deliveries in the wholesale market. NGSA requests clarification and, if needed, rehearing to ensure that physically-settled, non-NYMEX options are included in reported volumes.
                    <SU>128</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>127</SU>
                         Order No. 704 at P 113.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>128</SU>
                         NGSA comments at 14.
                    </P>
                </FTNT>
                <P>84. We agree with NGSA and grant the requested clarification. A physically-settled non-NYMEX transaction must be reported on Form No. 552 if it utilizes or could contribute to the formation of a price index.</P>
                <HD SOURCE="HD3">Certain “NYMEX Plus” Contracts Are Reportable</HD>
                <P>
                    85. Order No. 704 excluded from reporting any type of financially-settled transaction.
                    <SU>129</SU>
                    <FTREF/>
                     NEM requests clarification regarding reporting of “NYMEX Plus” contract volumes. Specifically, NEM requests clarification regarding the definition of Physical Natural Gas on Form No. 552.
                    <SU>130</SU>
                    <FTREF/>
                     The form excludes from reporting “any type of financially-settled transaction.” NEM is uncertain whether NYMEX Plus contracts fall into this exclusion. NEM explains that under a NYMEX Plus contract an entity purchases or sells a volume of gas on a wholesale basis at a reportable location for a month or series of months with the price determined by reference to the monthly settlement price of a NYMEX futures contract plus an adder.
                    <SU>131</SU>
                    <FTREF/>
                     NEM is unsure whether such volumes should be reported on Form No. 552 line 5 as “prices that refer to published next-month gas price indices” or line 6 (the “other” category).
                    <SU>132</SU>
                    <FTREF/>
                     NEM is also uncertain as to: (1) The calendar year and months in which contract volumes related to a multi-month or multi-year NYMEX Plus contract should be reported; and (2) the price that should be reported on Form No. 552 if a price is to be set at a future date.
                    <SU>133</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>129</SU>
                         Order No. 704 at P 111 and Form No. 552, Definition VII, Physical Natural Gas.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>130</SU>
                         NEM comments at 4-6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>131</SU>
                         
                        <E T="03">Id.</E>
                         at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>132</SU>
                         
                        <E T="03">Id.</E>
                         at 3-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>133</SU>
                         NEM comments at 4-5.
                    </P>
                </FTNT>
                <P>86. Based upon the facts as detailed by NEM, the Commission believes that only a subset of NYMEX Plus contracts should be reported. Specifically, we clarify that NYMEX Plus transactions are reportable only when: (1) Executed during bid week and that can contribute to a next-month price index, or (2) they utilize a NYMEX settlement price during bid week that can contribute to a next-month index. In that regard, the Commission is adding a new line between current lines 6 and 7 to page 5 of Form No. 552 for the purpose of reporting data regarding NYMEX Plus and other “triggered” physical gas transactions.</P>
                <P>
                    87. Further, we clarify that, for all contracts where deliveries occur or may occur over multiple calendar years and such volumes are reportable, only volumes attributable for delivery that use or may contribute to the formation of price indices during the subject calendar year should be reported on Form No. 552. In Order No. 704, the Commission indicated that transactions are to be reported based upon whether their expected delivery dates are within the reporting year—contract formation dates are irrelevant.
                    <SU>134</SU>
                    <FTREF/>
                     For example, for a contract that could contribute to the formation of a price index and requires deliveries at times between July of the first year through February of the next, the respondent should report July-December volumes for the Form No. 552 corresponding to the first year's volumes and January-February volumes in the next year's Form No. 552. For a multi-year contract that relies on a price index to establish a price, the relevant volumes should be reported in the year in which the index is referenced.
                </P>
                <FTNT>
                    <P>
                        <SU>134</SU>
                         Order No. 704 at P 60.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Bid-Week, Fixed Price Differential Physical Basis Transactions Tied to the Last Day of Settlement Are Reportable</HD>
                <P>
                    88. NGSA requests rehearing such that the definition of “Fixed Price” in Form No. 552 includes bid-week fixed price differential physical basis transactions tied to the last day of settlement.
                    <SU>135</SU>
                    <FTREF/>
                     NGSA notes that these agreements form a material portion of the reported transactions at index points.
                    <SU>136</SU>
                    <FTREF/>
                     AGA, in supplemental comments in the docket, suggests that physical basis transactions be reported on a separate line on Form No. 552.
                    <SU>137</SU>
                    <FTREF/>
                     NGSA argues that including these volumes would ease the administrative burden on respondents as these volumes would not need to be monitored and removed from aggregate volume numbers.
                    <SU>138</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>135</SU>
                         These types of transactions involve transfers of physical natural gas utilizing basis differentials. The transactions are executed during the bid-week at a fixed differential to the last day of settlement.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>136</SU>
                         NGSA comments at 8.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>137</SU>
                         AGA supplemental comments at 5-6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>138</SU>
                         NGSA comments at 8.
                    </P>
                </FTNT>
                <P>89. The Commission agrees that Form No. 552 should include bid-week, fixed price differential physical basis transactions. These transactions are a significant aspect of wholesale natural gas markets and utilize or could contribute to the formation of price indices. Consistent with AGA's recommendation, we will include a new line item in Form No. 552, requiring the reporting of all physical basis transactions, including fixed differential basis transactions that can contribute to or rely upon a price index.</P>
                <HD SOURCE="HD3">All Data Provided on Form No. 552 Will Be Publicly Available</HD>
                <P>90. At least one participant at the technical conference requested that the Commission act to protect allegedly proprietary information contained in completed Form No. 552. Specifically, the concern was raised by Samson Resources Company (Samson) that, by requiring submission of data based upon transactions at specific locations, the form would provide sensitive commercial information to competitors who may already know the point or points where the respondent transacts. Samson also claimed that the names of affiliates should be confidential as well.</P>
                <P>
                    91. We reiterate that Form No. 552 data will be publicly available. In Order No. 704, the Commission addressed requests that data included on Form No. 552 be treated as confidential or proprietary.
                    <SU>139</SU>
                    <FTREF/>
                     We found that Congress directed the Commission to provide aggregate information to the public. We balanced this transparency goal with the asserted need for confidentiality. Among the factors we considered were: (1) Data would be reported in the aggregate; (2) no specific pricing information would be reported; (3) data 
                    <PRTPAGE P="55738"/>
                    would be reported on a national level, not locally or regionally; and (4) data would not be reported until four months following the reporting year.
                    <SU>140</SU>
                    <FTREF/>
                     We see no reason to modify our determination in this regard. We note, however, that our determination herein to eliminate the reporting of data at specific reportable locations, further reduces any concerns that reported data is commercially sensitive.
                </P>
                <FTNT>
                    <P>
                        <SU>139</SU>
                         Order No. 704 at PP 82-84.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>140</SU>
                         
                        <E T="03">Id.</E>
                         P 83.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">We Decline To Modify the Effective Date of the Rule</HD>
                <P>
                    92. Under Order No. 704, respondents must submit Form No. 552 no later than May 1, 2009 for data collected in calendar year 2008.
                    <SU>141</SU>
                    <FTREF/>
                     We understand that one participant at the technical conference requested that the Commission delay reporting of data until 2010 (for calendar year 2009 data). NiSource argued that it did not have the ability to electronically record data required by Form No. 552 and, given that the Commission had yet to issue an order on rehearing, it may be very difficult or impossible for some companies to comply with a 2009 filing date.
                </P>
                <FTNT>
                    <P>
                        <SU>141</SU>
                         
                        <E T="03">Id.</E>
                         P 105.
                    </P>
                </FTNT>
                <P>93. The Commission declines to modify the effective date of the rule or the date by which Form No. 552 is first to be filed. We note that no entity raised this issue on rehearing or a formal request for clarification. We have confidence in respondents' capabilities to report the general volume data requested on Form No. 552 by the May 1, 2009 filing date. With the adoption of a one-year safe harbor, discussed above, concerns regarding the difficulty of collecting 2008 data for reporting in 2009 should be mitigated.</P>
                <HD SOURCE="HD3">We Do Not at This Time Establish Additional Formal Procedures To Address Market Participant Questions Regarding Form No. 552</HD>
                <P>
                    94. NEM requests that the Commission establish ongoing procedures in which staff may offer informal advice to market participants regarding reporting requirements in Form No. 552. NEM proposes a “technical compliance forum” to include a combination of measures such as an additional hotline, a designated interactive Web page for industry questions regarding Form No. 552 (including a Frequently Asked Questions page), designation of specific staff members to field questions, and periodic technical conferences leading up to the May 2009 filing deadline.
                    <SU>142</SU>
                    <FTREF/>
                     Additionally, AGA and Merrill Lynch Commodities (Merrill Lynch), during the technical conference process, suggested that staff complete and distribute a sample Form No. 552 based upon various types of transactions. AGA also requested in supplemental comments that the Commission commit to provide further guidance on the reporting obligation following submission of annual reports in 2009.
                    <SU>143</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>142</SU>
                         NEM comments at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>143</SU>
                         AGA supplemental comments at 3.
                    </P>
                </FTNT>
                <P>
                    95. We do not believe that additional informational or educational outreach regarding Form No. 552 is necessary at this time. To the extent that additional clarification is necessary following the issuance of this Order on Rehearing and Clarification, requests for further clarification and rehearing are permitted and additional technical conferences may be held at our discretion. Further, we note that, once entities begin to complete Form No. 552 with calendar year 2008 data, respondents may direct informal questions through appropriate means, including the new compliance help desk.
                    <SU>144</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>144</SU>
                         
                        <E T="03">See Obtaining Guidance on Regulatory Requirements</E>
                        , 123 FERC ¶ 61,157 (2008).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">The Reach of the Safe Harbor Provision in the Policy Statement On Natural Gas and Electric Price Indices</HD>
                <P>
                    96. Referring to the 2003 Policy Statement, Order No. 704 stated, in passing, that “[a] market participant that does not hold blanket sales certificates is not required to comply with the Policy Statement processes, nor does it receive the safe harbor available in the Policy Statement.” 
                    <SU>145</SU>
                    <FTREF/>
                     Southern Company Services, Inc. (SCS) requests clarification of this statement. SCS argues that non-jurisdictional entities have engaged in price reporting while relying on an interpretation of the Policy Statement's safe harbor provision. SCS argues that the Policy Statement safe harbor applies to any “data provider” regardless of whether the provider is a certificate holder.
                    <SU>146</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>145</SU>
                         Order No. 704 at P 96.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>146</SU>
                         SCS comments at 2-3.
                    </P>
                </FTNT>
                <P>97. SCS's request is effectively a request to clarify the Policy Statement, not Order No. 704. The referenced comment was not a prerequisite to our determinations in the order. SCS's request is inappropriate as a request for clarification of Order No. 704.</P>
                <HD SOURCE="HD1">III. Information Collection Statement</HD>
                <P>
                    98. The Office of Management and Budget (OMB) regulations require that OMB approve certain reporting, recordkeeping, and public disclosure (collections of information) imposed by an agency.
                    <SU>147</SU>
                    <FTREF/>
                     The information collection requirements for Form No. 552 respondents were approved under OMB Control Nos. 1902-0242. This order further revises these requirements in order to more clearly state the obligations imposed in Order No. 704, but does not substantively alter those requirements. OMB approval of this order is therefore unnecessary. However, the Commission will send a copy of this order to OMB for informational purposes only.
                </P>
                <FTNT>
                    <P>
                        <SU>147</SU>
                         5 CFR 1320.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Environmental Analysis</HD>
                <P>
                    99. The Commission is required to prepare an Environmental Assessment or an Environmental Impact Statement for any action that may have a significant adverse effect on the human environment.
                    <SU>148</SU>
                    <FTREF/>
                     The actions taken here fall within categorical exclusions in the Commission's regulations for information gathering, analysis, and dissemination, and for sales, exchange, and transportation of natural gas that requires no construction of facilities.
                    <SU>149</SU>
                    <FTREF/>
                     Therefore, an environmental assessment is unnecessary and has not been prepared in this rulemaking.
                </P>
                <FTNT>
                    <P>
                        <SU>148</SU>
                         Order No. 486, 
                        <E T="03">Regulations Implementing the National Environmental Policy Act</E>
                        , 52 FR 47897 (Dec. 17, 1987), FERC Stats. &amp; Regs ¶ 30,783 (1987).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>149</SU>
                         18 CFR 380.4(a)(5) and (a)(27).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">V. Regulatory Flexibility Act</HD>
                <P>
                    100. The Regulatory Flexibility Act of 1980 (RFA) 
                    <SU>150</SU>
                    <FTREF/>
                     generally requires a description and analysis of rules that will have significant economic impact on a substantial number of small entities. The RFA requires consideration of regulatory alternatives that accomplish the stated objectives of a proposed rule and that minimize any significant economic impact on such entities. The RFA does not, however, mandate any particular outcome in a rulemaking. At a minimum, agencies are to consider the following alternatives: Establishment of different compliance or reporting requirements for small entities or timetables that take into account the resources available to small entities; clarification, consolidation, or simplification of compliance and reporting requirements for small entities; use of performance rather than design standards; and exemption for certain or all small entities from coverage of the rule, in whole or in part.
                </P>
                <FTNT>
                    <P>
                        <SU>150</SU>
                         5 U.S.C. 601-612.
                    </P>
                </FTNT>
                <P>
                    101. The annual reporting requirement set forth in the Order on Rehearing and Clarification will not have a significant economic impact on a substantial number of small entities. The requirement for annual reporting of 
                    <PRTPAGE P="55739"/>
                    physical natural gas transactions will have minimal impact on small entities. By incorporating a 
                    <E T="03">de minimis</E>
                     exemption into the regulations, the Commission has reduced the number of small entities subject to the requirements; 
                    <E T="03">de minimis</E>
                     entities without blanket sales certificates will not be required to report. This reporting requirement will affect small entities but the burden on them will be minimal. For each entity, small or otherwise, that is required to comply with the annual reporting requirement, the Commission estimates that the compliance would require a one-time cost of approximately $4,000 and an annual cost thereafter of $400. Although some costs would increase for market participants with a greater number of transactions, we expect that that increase would be likely offset because such entities would have already compiled information regarding their transactions in the aggregate. This amount is not a significant burden on small entities. The 
                    <E T="03">de minimis</E>
                     exemption provides a regulatory alternative that will reduce the economic impact on certain small entities from coverage of the rule. Accordingly, the Commission certifies that the order will not have a significant economic impact on a substantial number of small entities.
                </P>
                <HD SOURCE="HD1">VI. Document Availability</HD>
                <P>
                    102. In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the Internet through FERC's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ) and in FERC's Public Reference Room during normal business hours (8:30 a.m. to 5 p.m. Eastern time) at 888 First Street, NE., Room 2A, Washington, DC 20426.
                </P>
                <P>103. From FERC's Home Page on the Internet, this information is available on eLibrary. The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.</P>
                <P>
                    104. User assistance is available for eLibrary and the FERC's Web site during normal business hours from FERC Online Support at 202-502-6652 (toll free at 1-866-208-3676) or e-mail at 
                    <E T="03">ferconlinesupport@ferc.gov</E>
                    , or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. E-mail the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov</E>
                    .
                </P>
                <HD SOURCE="HD1">VII. Effective Date</HD>
                <P>105. Changes to Order No. 704 adopted in this Order on Rehearing and Clarification will become effective October 26, 2008.</P>
                <P>
                    <E T="03">The Commission orders:</E>
                </P>
                <P>The requests for clarification and rehearing are granted in part and denied in part as discussed in the body of this order.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>18 CFR Part 260</CFR>
                    <P>Natural gas, Reporting and recordkeeping requirements.</P>
                    <CFR>18 CFR Part 284</CFR>
                    <P>Continental shelf; Natural gas; Reporting and recordkeeping requirements.</P>
                    <CFR>18 CFR Part 385</CFR>
                    <P>Administrative practice and procedure; Electric power; Penalties; Pipelines; Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <P>By the Commission.</P>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
                <REGTEXT TITLE="18" PART="260">
                    <AMDPAR>In consideration of the foregoing, the Commission amends Chapter I, Title 18, Code of Federal Regulations to read as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 260—STATEMENTS AND REPORTS (SCHEDULES)</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 260 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>15 U.S.C. 717-717w, 3301-3432; 42 U.S.C. 7101-7352.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="18" PART="260">
                    <AMDPAR>2. Sec. 260.401 is revised as follows:</AMDPAR>
                    <AMDPAR>a. Paragraph (a) is amended by removing the word “reporting” between the words “annual” and “report.”</AMDPAR>
                    <AMDPAR>b. Paragraph (b)(1) introductory text is amended by removing the word “wholesale,” between the words “in” and “physical” and removing the word “As” and inserting the words, “However, as” at the beginning of the final sentence.</AMDPAR>
                    <AMDPAR>c. Paragraph (b)(1)(i) is amended by removing the word “and” at the end of the paragraph.</AMDPAR>
                    <AMDPAR>d. Paragraph (b)(1)(ii) is revised and paragraph 260.401(b)(1)(iii) is added to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 260.401</SECTNO>
                        <SUBJECT>FERC Form No. 552, Annual Report of Natural Gas Transactions.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(1) * * *</P>
                        <P>(ii) It engages in reportable physical natural gas sales that amount to less than 2,200,000 MMBtus for the previous calendar year; and</P>
                        <P>(iii) It engages in reportable physical natural gas purchases that amount to less than 2,200,000 MMBtus for the previous calendar year.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="18" PART="284">
                    <PART>
                        <HD SOURCE="HED">PART 284—CERTAIN SALES AND TRANSPORTATION OF NATURAL GAS UNDER THE NATURAL GAS POLICY ACT OF 1978 AND RELATED AUTHORITIES</HD>
                    </PART>
                    <AMDPAR>3. The authority citation for Part 284 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>15 U.S.C. 717-717w, 3301-3432; 42 U.S.C. 7101-7352; 43 U.S.C. 1331-1356.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="18" PART="284">
                    <AMDPAR>4. Section 284.403(a) is amended by removing the word “must” in the final sentence, and inserting the word “Seller” in its place.</AMDPAR>
                </REGTEXT>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>The following appendix will not be published in the Code of Federal Regulations.</P>
                </NOTE>
                <BILCOD>BILLING CODE 6717-01-P</BILCOD>
                <GPH SPAN="3" DEEP="578">
                    <PRTPAGE P="55740"/>
                    <GID>ER26SE08.420</GID>
                </GPH>
                <GPH SPAN="3" DEEP="517">
                    <PRTPAGE P="55741"/>
                    <GID>ER26SE08.421</GID>
                </GPH>
                <GPH SPAN="3" DEEP="587">
                    <PRTPAGE P="55742"/>
                    <GID>ER26SE08.422</GID>
                </GPH>
                <GPH SPAN="3" DEEP="597">
                    <PRTPAGE P="55743"/>
                    <GID>ER26SE08.423</GID>
                </GPH>
                <GPH SPAN="3" DEEP="598">
                    <PRTPAGE P="55744"/>
                    <GID>ER26SE08.424</GID>
                </GPH>
                <GPH SPAN="3" DEEP="558">
                    <PRTPAGE P="55745"/>
                    <GID>ER26SE08.425</GID>
                </GPH>
                <GPH SPAN="3" DEEP="514">
                    <PRTPAGE P="55746"/>
                    <GID>ER26SE08.426</GID>
                </GPH>
                <GPH SPAN="3" DEEP="561">
                    <PRTPAGE P="55747"/>
                    <GID>ER26SE08.427</GID>
                </GPH>
                <GPH SPAN="3" DEEP="541">
                    <PRTPAGE P="55748"/>
                    <GID>ER26SE08.428</GID>
                </GPH>
                <GPH SPAN="3" DEEP="538">
                    <PRTPAGE P="55749"/>
                    <GID>ER26SE08.429</GID>
                </GPH>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22358 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-C</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="55750"/>
                <AGENCY TYPE="S">DELAWARE RIVER BASIN COMMISSION </AGENCY>
                <CFR>18 CFR Part 410 </CFR>
                <SUBJECT>Amendments to the Water Quality Regulations, Water Code and Comprehensive Plan To Classify the Lower Delaware River as Special Protection Waters </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Delaware River Basin Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By Resolution No. 2008-9 on July 16, 2008, the Delaware River Basin Commission (“Commission” or DRBC) approved amendments to its Water Quality Regulations, Water Code and Comprehensive Plan to establish numeric values for existing water quality for the reach of the main stem Delaware River known as the “Lower Delaware” and to assign the Special Protection Waters (SPW) classification “Significant Resource Waters” (SRW) on a permanent basis to this reach. The Commission also approved language to clarify aspects of the SPW regulations, especially with respect to existing facilities, that have confused some DRBC docket holders and applicants since the SPW program was originally adopted by the Commission in 1992 for point sources and in 1994 for non-point sources. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective September 26, 2008. The incorporation by reference of the publications listed in this rule is approved by the Director of the Federal Register as of September 26, 2008. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Pamela M. Bush, secretary and assistant general counsel, Delaware River Basin Commission, by phoning 609-883-9500 ext. 203, or by e-mail to 
                        <E T="03">pamela.bush@drbc.state.nj.us;</E>
                         Kim Wobick, information resources coordinator, Delaware River Basin Commission, by phoning 609-883-9500 ext. 263, or by e-mail to 
                        <E T="03">kim.wobick@drbc.state.nj.us.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Delaware River Basin Commission (“Commission” or “DRBC”) is a federal-state regional agency charged with managing the water resources of the Delaware River Basin without regard to political boundaries. Its members are the governors of the four Basin states—Delaware, New Jersey, New York and Pennsylvania—and the North Atlantic Division Commander of the U.S. Army Corps of Engineers, representing the federal government. </P>
                <P>
                    Notice of the proposed amendments appeared in the 
                    <E T="04">Federal Register</E>
                     (72 FR 57255) on October 9, 2007 as well as in the 
                    <E T="03">Delaware Register of Regulations</E>
                     on October 1, 2007 (11 DE Reg. 376-378 (10/01/07)), the 
                    <E T="03">New Jersey Register</E>
                     (39 N.J.R. 4392) on October 15, 2007, the 
                    <E T="03">New York State Register</E>
                     (page 8) on October 10, 2007 and the 
                    <E T="03">Pennsylvania Bulletin</E>
                     (37 Pa. B. 5527) on October 13, 2007, respectively. The Commission held informational meetings about the proposed changes on October 25, 2007 in Stockton, New Jersey and on November 1, 2007 in Easton, Pennsylvania. A public hearing was held on December 4, 2007, and written comments were received through December 6, 2007. 
                </P>
                <P>
                    By Resolution No. 2005-2 in January of 2005, following a duly noticed public hearing, the Commission classified the Lower Delaware River as SRW on a temporary basis, pending the determination of numeric values for existing water quality for this section of the river and a thorough evaluation of the data to determine whether or not to classify certain sections of the Lower Delaware as Outstanding Basin Waters and whether to make the temporary Special Protection Waters designation permanent for some or all of the Lower Delaware. Following additional advertised public hearings in September 2005, September 2006, September 2007 and May 2008, temporary designation was extended repeatedly pending the Commission's final action on July 16, 2008. By that action, the Commission continued temporary classification of the Lower Delaware as SRW once more, until the amendments approved by Resolution No. 2008-9 are filed with each of the signatory parties in accordance with Section 14.2 of the Delaware River Basin Compact and a notice of final rulemaking has appeared in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <P>
                    A comment and response document addressing comments offered at the public hearing and written comments received through the close of the comment period is available on the Commission's Web site, 
                    <E T="03">DRBC.net.</E>
                     Copies of this document may be obtained by request of the Commission's information resources coordinator at the telephone and e-mail addresses listed above. A charge for printing and mailing may apply. 
                </P>
                <P>
                    DRBC Resolution No. 2008-9, including the amended rule in the form approved by the resolution, also is available on the DRBC Web site, 
                    <E T="03">DRBC.net.</E>
                     The resolution incorporates the entire text of Section 3.10.3 A.2. of the Water Quality Regulations and Water Code, showing the amendments as proposed in October of 2007 and as finally approved by the Commission on July 16, 2008. Copies may be obtained from the information resources coordinator at the telephone and e-mail addresses listed above. A charge for printing and mailing may apply. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 18 CFR Part 410 </HD>
                    <P>Incorporation by reference, Water pollution control, Water reservoirs, Water supply, Watersheds.</P>
                </LSTSUB>
                <REGTEXT TITLE="18" PART="410">
                    <AMDPAR>For the reasons set forth in the preamble, the Delaware River Basin Commission amends Part 410 of title 18 of the Code of Federal Regulations as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 410—BASIN REGULATIONS; WATER CODE AND ADMINISTRATIVE MANUAL—PART III WATER QUALITY REGULATIONS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for Part 410 continues to read: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>Delaware River Basin Compact, 75 Stat. 688. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="18" PART="410">
                    <AMDPAR>2. Revise § 410.1 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 410.1 </SECTNO>
                        <SUBJECT>Basin regulations—Water Code and Administrative Manual—Part III Water Quality Regulations. </SUBJECT>
                        <P>(a) The Water Code of the Delaware River Basin is a codification of regulations of the Delaware River Basin Commission applicable to public and private water projects and programs within the Delaware River Basin. Article I of the water code sets forth general policies of the Commission. Article II concerns the conservation, development and utilization of Delaware River Basin water resources, including during periods of drought. Article III sets forth water quality standards and guidelines for the Delaware River Basin. Article IV contains rules relating to application of water quality standards within the Basin. The Commission's Administrative Manual—Part III, Water Quality Regulations, applies to all public and private entities that discharge waste to waters of the Delaware River Basin. </P>
                        <P>(b) Article III of the water code consists of Article III of the water quality regulations. Article IV of the water code consists of portions of Article IV of the water quality regulations. </P>
                        <P>
                            (c) Work, services, activities and facilities affecting the conservation, utilization, control, development or management of water resources within the Delaware River Basin are subject to the regulations contained within the Delaware River Basin Water Code with Amendments Through July 16, 2008, Printed: September 12, 2008, and the Administrative Manual Part III Water Quality Regulations with Amendments Through July 16, 2008, Printed: 
                            <PRTPAGE P="55751"/>
                            September 12, 2008. Both the Delaware River Basin Water Code and the Administrative Manual Part III Water Quality Regulations are incorporated by reference into this part with the approval of the Director of the Federal Register under 5 U.S.C. 552(a) and 1 CFR part 51. You may obtain or inspect a copy at the Delaware River Basin Commission (DRBC), 25 State Police Drive, West Trenton, New Jersey 08628-0360, 609-883-9500, http://www.drbc.net, or at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030 or go to 
                            <E T="03">http://www.archives.gov/federal_register/code_of_federal_regulations/ibr_locations.html</E>
                            . 
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>Pamela M. Bush, </NAME>
                    <TITLE>Secretary and Assistant General Counsel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22637 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6360-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <CFR>40 CFR Part 60 </CFR>
                <DEPDOC>[EPA-HQ-OAR-2007-0011; FRL-8721-5] </DEPDOC>
                <RIN>RIN 2060-AN72 </RIN>
                <SUBJECT>Standards of Performance for Petroleum Refineries </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; reconsideration and stay of effective date. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action grants Petitioners' request for reconsideration and Petitioners' request for a stay until December 25, 2008 for certain specific provisions in the newly promulgated standards of performance for new, modified, or reconstructed process units at petroleum refineries. The effective date for the final rule promulgating amendments to the current standards of performance for petroleum refineries has not changed and remains June 24, 2008. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective September 26, 2008, in Title 40 CFR part 60, subpart Ja, § 60.100a(c), the definition of “flare” in § 60.101a, and §§ 60.102a(g), 60.107a(d), and 60.107a(e) are stayed until December 25, 2008. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Robert B. Lucas, Office of Air Quality Planning and Standards, Sector Policies and Programs Division, Coatings and Chemicals Group (E143-01), Environmental Protection Agency, Research Triangle Park, NC 27711, telephone number: (919) 541-0884; fax number: (919) 541-0246; e-mail address: 
                        <E T="03">lucas.bob@epa.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <P>The Environmental Protection Agency published a final rule on June 24, 2008 that contained the following: (1) Final amendments to the existing refineries new source performance standards (NSPS) in 40 CFR part 60, subpart J; and (2) a new refineries NSPS in 40 CFR part 60, subpart Ja (73 FR 35838). The preamble to that rule contained an incorrect effective date and contained an error in the Congressional Review Act (CRA) statement in the Statutory and Executive Order Reviews section. To address that error, the effective date of NSPS subpart Ja was stayed for 60 days until September 26, 2008. The amendments in NSPS subpart J were not affected and remained effective from June 24, 2008. </P>
                <P>
                    On June 13, 2008, the American Petroleum Institute (API), the National Petrochemical and Refiners Association (NPRA), and the Western States Petroleum Association (WSPA) (collectively referred to as “Industry Petitioners”) requested an administrative stay under Clean Air Act (CAA) section 307(d)(7)(B) of certain provisions of 40 CFR part 60, subpart Ja. On July 25, 2008, the Industry Petitioners sought reconsideration of the provisions of NSPS subpart Ja for which they had previously requested a stay. Specifically, Industry Petitioners requested that EPA reconsider the following provisions in NSPS subpart Ja: (1) The definition of “modification” (40 CFR 60.100a(c)); (2) the definition of “flare” (40 CFR 60.101a); (3) the fuel gas combustion device sulfur limits as they relate to flares (40 CFR 60.102a(g)(1)); (4) the flow limit for flare systems (40 CFR 60.102a(g)(3)); (5) the total reduced sulfur and flow monitoring requirements for flares (40 CFR 60.107a(d), (e)); and (6) the nitrogen oxide (NO
                    <E T="52">X</E>
                    ) limit for process heaters (40 CFR 60.102a(g)(2)). Subsequently, on August 21, 2008, the Industry Petitioners identified additional issues for reconsideration. 
                </P>
                <P>
                    On August 25, 2008, HOVENSA, LLC (“HOVENSA”) filed a petition for reconsideration of the following provisions of 40 CFR part 60, subpart Ja: (1) the NO
                    <E T="52">X</E>
                     limit for process heaters (40 CFR 60.102a(g)(2)); (2) the flaring requirements, including the definitions of “flare” and “modification” (40 CFR 60.100a(c), 60.101a, 60.102a(g)-(i), 60.103a(a)-(b)); and (3) the depressurization work practice standard for delayed coking units (40 CFR 60.103a(c)). The petition also requested that EPA stay the effectiveness of these provisions during the reconsideration process. 
                </P>
                <P>
                    EPA received a third petition for reconsideration on August 25, 2008, from the Environmental Integrity Project, Sierra Club, and Natural Resources Defense Council (“Environmental Petitioners”) requesting EPA reconsider several aspects of 40 CFR part 60, subpart Ja. The petition identifies the following issues for reconsideration: (1) EPA's decision not to promulgate NSPS for carbon dioxide and methane emissions from refineries; (2) the flaring requirements (40 CFR 60.100a(c), 60.101a, 60.102a(g)-(i), 60.103a(a)-(b)); (3) the NO
                    <E T="52">X</E>
                     limit for fluid catalytic cracking units (FCCU) (40 CFR 60.102a(b)(2)); and (4) the particulate matter limit for FCCU (40 CFR 60.102a(b)(1)). Unlike the other Petitioners, Environmental Petitioners did not seek a stay of these provisions during reconsideration. 
                </P>
                <P>
                    EPA has begun reviewing all of these petitions and is addressing in this notice only those issues for which Industry Petitioners and HOVENSA sought reconsideration 
                    <E T="03">and</E>
                     a stay of those specific provisions during reconsideration. EPA is taking no action on all of the other issues raised in the petitions but will consider all of the outstanding issues in a future notice. 
                </P>
                <P>
                    In this action, EPA is granting reconsideration with respect to the following provisions: (1) The definition of “modification;” (2) the definition of “flare;” (3) the fuel gas combustion device sulfur limits as they apply to flares; (4) the flow limit for flare systems; (5) the total reduced sulfur and flow monitoring requirements for flares; and (6) the NO
                    <E T="52">X</E>
                     limit for process heaters. We are granting reconsideration on these specific issues because the grounds for Petitioners' objections arose after the public comment period (but within the time specified for judicial review) and the objections are of central relevance to the outcome of the final rule pursuant to CAA section 307(d)(7)(B). 
                </P>
                <P>
                    EPA is also granting Industry Petitioners and HOVENSA's request for a 90-day stay of the following provisions that are under reconsideration (see CAA section 307(d)(7)(B)): (1) The definition of “modification;” (2) the definition of “flare;” (3) the fuel gas combustion device sulfur limits; (4) the flow limit for flare systems; (5) the total reduced sulfur and flow monitoring requirements for flares; and (6) the NO
                    <E T="52">X</E>
                     limit for process heaters. We are staying 
                    <PRTPAGE P="55752"/>
                    the first five provisions listed above because the final approach to regulating flare emissions was first introduced in the final rule and represented significant changes from the proposal. Facilities had no chance to comment on these new requirements in the final rule. Accordingly, we have reason to believe that certain facilities may be out of compliance with requirements for which they had no notice or time to come into compliance. Moreover, a stay is appropriate because in reconsidering these requirements both the affected universe and the substantive requirements could change. It should be noted that as a consequence of staying the fuel gas combustion device sulfur limits as they apply to flares we are staying the requirement for all fuel gas combustion devices. The effect of this action is to delay compliance obligations for 90 days of the sulfur limits under NSPS subpart Ja for fuel gas combustion devices other than flares such as process heaters and boilers. Although this is not a preferred outcome, it is unavoidable due to the structure of the rule and is an unintended consequence of this action. 
                </P>
                <P>We are staying the sixth provision listed above because information provided by Industry Petitioners and HOVENSA has led the Agency to question whether the emission limits in the final rule are achievable and represent best demonstrated technology. The information provided has convinced us that certain facilities may suffer undue hardship in attempting compliance with this limit. Granting a stay of this requirement while we reconsider this limit is, therefore, necessary to prevent any possible harm that may occur. </P>
                <P>EPA is denying HOVENSA's request for a 90-day stay of the depressurization work practice standard for delayed coking units. HOVENSA provided no individual demonstration regarding its need for EPA to stay this work practice standard. HOVENSA provided no specific information or explanation of why staying this provision of a nationally applicable rule is the appropriate recourse for protecting its individual facility. HOVENSA's generalized assertions of incurring compliance costs absent a stay are not enough reason for granting this request for a stay. EPA, therefore, denies HOVENSA's request for a stay of this provision. </P>
                <P>All other requirements promulgated in 40 CFR part 60, subpart Ja become effective as of September 26, 2008. </P>
                <P>
                    EPA will address the substantive aspects of this reconsideration in a separate notice in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">II. Statutory and Executive Order Reviews </HD>
                <HD SOURCE="HD2">A. General Requirements </HD>
                <P>
                    Under Executive Order 12866 (58 FR 51735, October 4, 1993), this action is not a “significant regulatory action” and, therefore, is not subject to review by the Office of Management and Budget. For this reason, this action is also not subject to Executive Order 13211, “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001). In addition, this action does not impose any enforceable duty or contain any unfunded mandate as described in the Unfunded Mandates Reform Act of 1995 (Pub. L.104-4), or require prior consultation with State officials as specified by Executive Order 12875 (58 FR 58093, October 28, 1993), or involve special consideration of environmental justice related issues as required by Executive Order 12898 (59 FR 7629, February 16, 1994). Because this action is not subject to notice-and-comment requirements under the Administrative Procedure Act or any other statute, it is not subject to the regulatory flexibility provisions of the Regulatory Flexibility Act (5 U.S.C. 601, 
                    <E T="03">et seq.</E>
                    ). This action also does not have tribal implications because it will not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal government and Indian tribes, or on the distribution of power and responsibilities between the Federal government and Indian tribes, as specified by Executive Order 13175 (65 FR 67249, November 9, 2000). This action also does not have Federalism implications because it does not have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government, as specified in Executive Order 13132 (64 FR 43255, August 10, 1999). This action also is not subject to Executive Order 13045 “Protection of Children from Environmental Health Risks and Safety Risks” (62 FR 19885, April 23, 1997). The requirements of section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) do not apply. This action does not impose an information collection burden under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501, 
                    <E T="03">et seq.</E>
                    ). EPA's compliance with these statutes and Executive Orders for the underlying rule is discussed in the June 24, 2008 
                    <E T="04">Federal Register</E>
                     document. 
                </P>
                <HD SOURCE="HD2">B. Submission to Congress and the Comptroller General </HD>
                <P>
                    The Congressional Review Act, 5 U.S.C. 801, 
                    <E T="03">et seq.</E>
                    , as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. EPA will submit a report containing this notice and other required information to the United States Senate, the United States House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the 
                    <E T="04">Federal Register</E>
                    . The stay of these particular provisions in NSPS subpart Ja is not a “major rule” as defined by 5 U.S.C. 804(2). 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 60 </HD>
                    <P>Environmental protection, Administrative practice and procedure, Air pollution control, Monitoring, reporting and recordkeeping.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: September 22, 2008. </DATED>
                    <NAME>Stephen L. Johnson, </NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
                <REGTEXT TITLE="40" PART="60">
                    <AMDPAR>For the reasons stated in the preamble, title 40, chapter I of the Code of Federal Regulations is amended as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 60—[AMENDED] </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 60 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            42 U.S.C. 7401, 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 60.100a </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>2. In § 60.100a, paragraph (c) is stayed from September, 26, 2008, until December 25, 2008. </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="60">
                    <SECTION>
                        <SECTNO>§ 60.101a </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>3. The definition of “flare” in § 60.101a is stayed from September, 26, 2008, until December 25, 2008. </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="60">
                    <SECTION>
                        <SECTNO>§ 60.102a </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>4. In § 60.102a, paragraph (g) is stayed from September, 26, 2008, until December 25, 2008. </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="60">
                    <SECTION>
                        <SECTNO>§ 60.107a </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>5. In § 60.107a, paragraphs (d) and (e) are stayed from September, 26, 2008, until December 25, 2008.</AMDPAR>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22692 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="55753"/>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <CFR>42 CFR Part 421 </CFR>
                <DEPDOC>[CMS-6022-F] </DEPDOC>
                <RIN>RIN 0938-AN31 </RIN>
                <SUBJECT>Medicare Program; Termination of Non-Random Prepayment Complex Medical Review </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This final rule implements requirements regarding the termination of non-random prepayment complex medical review as required under the Medicare Prescription Drug, Improvement and Modernization Act of 2003. This final rule sets forth the criteria CMS contractors will use for terminating a provider or supplier from non-random prepayment complex medical review. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         These regulations are effective on January 1, 2009. 
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Debbie Skinner, (410) 786-7480; or  Daniel Schwartz, (410) 786-4197. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <P>CMS's Medicare contracting authority has been in place since the inception of the Medicare program in 1965. Section 1874 of the Social Security Act (the Act) authorizes the Secretary to perform Medicare program functions directly or by contract. </P>
                <P>On August 21, 1996, the Congress enacted the Health Insurance Portability and Accountability Act of 1996 (HIPAA) (Pub. L. 104-191). Section 202 of HIPAA added section 1893 to the Act to establish the Medicare Integrity Program and to allow CMS to contract with eligible entities to perform program integrity activities. Specifically, we contract with the following entities: Intermediaries as specified in section 1816(a) of the Act; carriers as specified in section 1842(a) of the Act; and program safeguard contractors (PSCs) to perform medical, fraud, and utilization reviews, and cost report audits of Medicare claims. (Hereinafter, intermediaries, carriers, and PSCs that perform medical review functions are referred to as “contractors.”) The Medicare Integrity Program is funded by the Medicare Hospital Insurance Trust Fund for activities related to Medicare Part A and Part B. </P>
                <P>On December 8, 2003, the Congress enacted the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 (MMA) (Pub. L. 108-173). Section 934 of the MMA amended section 1874A of the Act by adding a new subsection regarding random prepayment reviews and non-random prepayment complex medical reviews, and requiring CMS to establish termination date(s) for non-random prepayment complex medical reviews performed by Medicare Administrative Contractors (MACs) (or intermediaries and carriers until MACs are in place). While section 1874A of the Act does not require CMS to establish termination dates for non-random prepayment complex medical reviews performed by PSCs, we have authority to apply these termination dates to medical review performed by PSCs under section 1893(b) of the Act. Applying this final rule to all contractors who perform non-random prepayment complex medical review not for benefit integrity purposes ensures that the same criteria for terminating non-random prepayment complex medical review apply to all providers and suppliers, whether they are under review by a MAC or a PSC. </P>
                <P>Although section 934 of the MMA sets forth requirements for random prepayment review, our contractors currently do not perform random prepayment review. However, our contractors do perform non-random prepayment complex medical review. We are cognizant of the need for additional rulemaking should we wish our contractors to perform random review. </P>
                <P>
                    In the October 7, 2005 
                    <E T="04">Federal Register</E>
                     (70 FR 58649), we published a proposed rule specifying the criteria contractors would use for the termination of providers and suppliers from non-random prepayment complex medical review as required under the MMA (hereinafter referred to as the proposed rule). 
                </P>
                <P>For purposes of this regulation, we are defining the following terms related to medical review activities: </P>
                <P>
                    <E T="03">Allowable charge</E>
                     means the dollar amount (including co-payment and deductibles) that the Medicare program will pay for a particular item or service. 
                </P>
                <P>
                    <E T="03">Benefit integrity review</E>
                     means medical review of claim information and medical documentation focusing on addressing situations of potential fraud, waste and abuse. 
                </P>
                <P>
                    <E T="03">Complex medical review</E>
                     means review of claim information and medical documentation, by a licensed medical professional, for a billed item or service identified by data analysis techniques or probe review to have a likelihood of sustained or high level of payment error. 
                </P>
                <P>
                    <E T="03">Contractor</E>
                     means intermediaries, carriers, Medicare Administrative Contractors (MACs), and program safeguard contractors (PSCs). 
                </P>
                <P>
                    <E T="03">Error rate</E>
                     means the dollar amount of allowable charges for a particular item or service billed in error as determined by complex medical review, divided by the dollar amount of allowable charges for that medically reviewed item or service. 
                </P>
                <P>
                    <E T="03">Initial error rate</E>
                     means the calculation of an error rate based on the results of a probe review prior to the initiation of non-random prepayment complex medical review. 
                </P>
                <P>
                    <E T="03">Medical review</E>
                     means the process performed by Medicare contractors to ensure that billed items or services are covered and are reasonable and necessary as specified under section 1862(a)(1)(A) of the Act. 
                </P>
                <P>
                    <E T="03">Nonclinician medical review staff</E>
                     means specially trained medical review staff that does not possess the knowledge, skills, training, or medical expertise of a licensed medical professional. 
                </P>
                <P>
                    <E T="03">Non-random prepayment complex medical review</E>
                     means the prepayment medical review of claim information and medical documentation, by a licensed medical professional, for a billed item or service identified by data analysis techniques or probe review to have a likelihood of sustained or high level of payment error. 
                </P>
                <P>
                    <E T="03">Non-random prepayment medical review</E>
                     means the prepayment medical review of claims, by nonclinical or clinical medical review staff, for a billed item or service identified by data analysis techniques or probe review to have a likelihood of a sustained or high level of payment error. 
                </P>
                <P>
                    <E T="03">Postpayment medical review</E>
                     means medical review of claims, by nonclinical or clinical medical review staff, for a billed item or service after a claim has been paid. 
                </P>
                <P>
                    <E T="03">Provider-specific probe review</E>
                     means the complex medical review of a small sample of claims, generally 20 to 40 claims, from a specific provider or supplier for a specific billing code to confirm that or determine whether the provider or supplier is billing the program in error. 
                </P>
                <P>
                    <E T="03">Quarterly error rate</E>
                     means the calculation of an error rate based on the results of non-random prepayment complex medical review for a specific billing code for a specific quarter. 
                </P>
                <P>
                    <E T="03">Random prepayment medical review</E>
                     means the prepayment medical review of claims, by nonclinical or clinical medical review staff, for a billed item or 
                    <PRTPAGE P="55754"/>
                    service that has not been identified by data analysis techniques or probe review to have a likelihood of a sustained or high level of payment error. 
                </P>
                <P>
                    <E T="03">Service-specific probe review</E>
                     means the complex medical review of a sample of claims, generally 100 claims, across the providers or suppliers that bill a particular item or service to confirm that or determine whether the item or service is billed in error. 
                </P>
                <P>
                    <E T="03">Termination of non-random prepayment complex medical review</E>
                     means the cessation of non-random prepayment complex medical review. 
                </P>
                <HD SOURCE="HD1">II. General Overview of the Medical Review Process and Provisions of the Proposed Rule </HD>
                <HD SOURCE="HD2">A. Medical Review </HD>
                <P>We enter into contractual agreements with contractors to perform medical review functions. One of the functions of a contractor is to ensure the fiscal integrity of the Medicare program by conducting medical review of claims to determine whether items or services are covered and are reasonable and necessary. When a claim is submitted for payment, it may be subject to medical review before payment is made. </P>
                <P>There are three types of non-random prepayment medical review: Automated, routine, and complex. Non-random prepayment medical review is one form of targeted medical review. An automated non-random prepayment medical review is when decisions are made at the system level, using available electronic information, without the intervention of contractor personnel. A routine non-random prepayment medical review is limited to rule-based determinations performed by specially trained nonclinical medical review staff. Automated and routine non-random prepayment medical reviews do not create an administrative burden on the provider or supplier since additional medical documentation does not need to be submitted for these types of medical reviews and payments for covered, reasonable and necessary items or services are not delayed. Therefore, these types of reviews pose no discernable administrative burden on the provider or supplier because there is no interaction between the contractor and the provider or supplier during the medical review process. </P>
                <P>
                    Non-random prepayment complex medical review is the evaluation of medical records or any other documentation by a licensed medical professional prior to Medicare payment. Complex medical review determinations require the reviewer to make a clinical judgment about whether an item or service is covered, and is reasonable and necessary. In order for this determination to be made, the provider or supplier must submit a copy of the medical records that indicate that the items or services billed are covered, and are reasonable and necessary for the condition of the patient. This type of review delays payment until the contractor is able to make a determination that the items or services billed are covered and are reasonable and necessary. This final rule only applies to terminating a provider or supplier from non-random prepayment complex medical review. (A detailed description of the concepts for performing the different types of non-random prepayment medical review functions are located in our manual instructions at: 
                    <E T="03">http://www.cms.hhs.gov/manuals/IOM/list.asp</E>
                     and then click on “Publication 100-08.”) 
                </P>
                <P>Generally, with non-random prepayment complex medical review, the contractor employs data analysis procedures to identify claims that may be billed inappropriately. These procedures may be based on claims data (national and local), beneficiary complaints, and alerts from other organizations (for example, the U.S. Department of Health and Human Services Office of Inspector General and the Government Accountability Office). When a contractor identifies a likelihood of sustained or high level of payment error, the contractor may request supporting medical record documentation. Examples of a high level of payment error include unusual patterns such as prescribing the same items or services for a high number of patients, consistently prescribing inappropriate treatments, unexplained increases in volume when compared to historical or peer trends, or any other reasons as determined by the Secretary or his designees. </P>
                <P>Before a contractor places a provider or supplier on non-random prepayment complex medical review, the contractor performs a probe review (that is, complex medical review of a small sample of claims for a specific billing code, generally 20 to 40 claims to confirm that the provider or supplier is billing the program in error). In the case of a widespread “item or service-specific” problem, a larger sample of claims (generally, 100 claims of the item or service in question) would be subjected to complex medical review. Performing medical review on a sample of claims for a specific billing code before placing the provider or supplier on non-random prepayment complex medical review allows for a determination as to whether a problem exists, ensures that contractor medical review resources are targeted appropriately, and ensures that providers and suppliers are not unnecessarily burdened. </P>
                <P>When a probe confirms or determines whether a provider or supplier is billing the program in error, and those billing errors present a likelihood of sustained or high level of payment error (for example, a high billing error rate or errors on claims representing high dollar value) this may result in the provider or supplier being placed by the contractor on non-random prepayment complex medical review. Contractors target their medical review activities at those providers, suppliers, items, or services that pose the greatest risk of improper payments from the Medicare Trust Funds. </P>
                <P>Complex medical review as defined in § 421.501 (proposed § 421.401), involves the application of clinical judgment by a licensed medical professional in order to evaluate medical records to determine whether an item or service billed is covered, correctly coded, and reasonable and necessary for the condition of the patient under Medicare rules. </P>
                <P>Medical records, defined at § 421.501 (proposed § 421.401), include any medical documentation, other than what is included on the face of the claim that supports the item or service that is billed. For Medicare to consider coverage and payment for any item or service, the claims submitted by the supplier or provider must be supported by the documentation in the patient's medical records. The patient's medical records may include the following: (1) Physician's office records; (2) hospital records; (3) nursing home records; (4) home health agency records; (5) records from other healthcare professionals; and (6) diagnostic testing reports and other supporting documentation. The contractor specifies what documentation it needs to conduct medical review. Providers and suppliers may be required to supply additional documentation not explicitly listed by the contractor. This supporting information may be requested by CMS and our contractors on a routine basis in instances where information on the claims (for example, diagnosis, frequency, site of service) or in claims history does not clearly indicate medical necessity. </P>
                <P>
                    Any determination must be documented by the contractor and include the rationale for the decision. While medical review staff must follow National Coverage Determinations and Local Coverage Determinations, they are 
                    <PRTPAGE P="55755"/>
                    expected to use their expertise to make clinical judgments when making medical review determinations. They must take into consideration the clinical condition of the beneficiary as indicated by the beneficiary's diagnosis and medical history when making these determinations. At any time during the medical review process where the contractor detects possible fraud, the contractor would refer the issue to the contractor responsible for benefit integrity review. 
                </P>
                <P>Before the enactment of the MMA, we continued to perform non-random prepayment complex medical review until the provider or supplier met all Medicare billing requirements as evidenced by an acceptable error rate. The contractor made the determination of “acceptable error rate.” As a result, some providers and suppliers have remained on non-random prepayment complex medical review for a considerable period of time. </P>
                <HD SOURCE="HD2">B. Termination of Non-Random Prepayment Complex Medical Review </HD>
                <P>In accordance with section 934 of the MMA, we proposed to terminate, in most cases, a provider or supplier from non-random prepayment complex medical review no later than 1 year from the initiation of the review, or when the provider's or supplier's error rate decreases by 70 percent from the initial error rate (70 FR 58651, October 7, 2005). The initiation of review begins on the date of notification by the contractor to the provider or supplier. This letter notification would inform the provider or supplier of the results of the probe review and inform the provider or supplier that they are being placed on non-random prepayment complex medical review. </P>
                <P>In the proposed rule, we proposed that a provider or supplier be terminated from non-random prepayment complex medical review if error rate findings indicate that the provider or supplier has corrected its billing errors, resulting in at least a 70 percent decrease from its initial error rate (70 FR 58651, October 7, 2005). For a discussion of our rationale for setting this percentage for purposes of this regulation, see the proposed rule (70 FR 58651, October 7, 2005). </P>
                <P>We did not explicitly propose whether there is a minimum timeframe that a provider or supplier must be on non-random prepayment complex medical review. We proposed that the initial error rate would be calculated based on the probe review prior to the initiation of non-random complex prepayment medical review. </P>
                <P>We proposed when a provider or supplier is terminated from non-random prepayment complex medical review and the contractor determines that the provider or supplier continues to have a high error rate despite educational interventions, the contractor must consider referring the provider or supplier to the contractor responsible for Benefit Integrity review. Contractors must also consider continuing educational interventions (without performing further medical review) or consider the need for post-payment medical review. </P>
                <P>We also proposed that a contractor must extend a non-random prepayment complex medical review beyond the 1-year limit in certain situations where the provider or supplier may have altered its billing practices in such a way to avoid or minimize contractor review. We proposed if the reduction in the error rate is attributed to a 25 percent or greater reduction in the number of claims submitted for the specific billing code  under review, non-random prepayment complex medical review for that provider or supplier must be extended. </P>
                <P>We also proposed if the number of claims submitted for a specific code was reduced because the provider or supplier began billing claims using a new appropriate code, or there is another legitimate explanation for the reduced number of claims billed, at the contractor's discretion, the provider or supplier may not be required to undergo extended non-random prepayment complex medical review. If extended medical review is necessary, contractors would notify providers and suppliers in writing of the reason for the need to perform additional prepayment complex medical review. </P>
                <P>We proposed that the contractor would evaluate the results of non-random complex prepayment medical review, and the length of time a provider or supplier remains on review, at least every quarter following the initiation of non-random prepayment complex medical review. Quarterly error-rate evaluations would be for the discrete quarter; a rolling error rate average over more than one quarter would not be appropriate. We also proposed that after the contractor determines that the provider or supplier must be terminated from non-random prepayment complex medical review, the contractor must update the claims processing system within 2 business days to ensure that the provider's and supplier's claims are no longer suspended for that specific billing error. </P>
                <P>We proposed that once a provider or supplier is terminated from non-random prepayment complex medical review contractors must periodically reevaluate the provider or supplier's data and retain the discretion to place a provider or supplier that appears to have resumed a high level of payment error on complex prepayment medical review. The proposed rule stated that before placing a provider or supplier back on non-random prepayment complex medical review, the contractor must conduct a probe review to confirm that there continues to be a high level of payment error (70 FR 58652, October 7, 2005). If such review finds a high level of payment error, the contractor may place the provider or supplier back on non-random prepayment complex medical review. </P>
                <HD SOURCE="HD1">III. Analysis of and Response to Public Comments </HD>
                <P>We received 18 timely public comments on the proposed rule. The following is a summary of the comments received and our responses. </P>
                <HD SOURCE="HD2">A. Comments Regarding the Proposed 70 Percent Decrease in Error Rate </HD>
                <P>
                    <E T="03">Comment:</E>
                     We received several comments concerning whether the 70 percent decrease in error rate was an appropriate number in order for a provider or supplier to be terminated from non-random prepayment complex review. Some commenters generally agreed with this percentage and others believed it should be lower. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The commenters requested many different error rates, many of which were lower than what we proposed, but we did not find consensus among the commenters for any one particular error rate. Since there was no consensus on an alternate percentage, we are leaving the percentage as originally proposed. We believe it strikes a fair balance between safeguarding the Medicare Trust Funds and providing a rational and predictable process for providers and suppliers to be removed from non-random prepayment complex medical review. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter believed that the proposed 70 percent decrease in error rate should only apply to nonclinical aspects of error determination. Instead, the commenter proposed a 51 percent decrease as a threshold for reviewing clinical decision making outcomes, asserting this would improve the mathematic probability of termination in such cases because reviewers may form subjective clinical judgments from reviewing mostly documentation and being unable to clinically verify diagnoses. Also, the commenter believed a 51 percent reduction would provide small to 
                    <PRTPAGE P="55756"/>
                    medium-sized providers a fair opportunity for successful termination. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We believe that regardless of whether the denial is based on a nonclinical or clinical error, it is still a denial for improper payment. We continue to believe a 70 percent reduction in error rate is a reasonable percentage to use to determine whether non-random prepayment complex medical review must continue. The statute does not require us to distinguish between provider size in establishing termination dates. We believe all providers and suppliers will have a fair opportunity for successful termination, regardless of size. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter believes that extensions of non-random prepayment complex medical review should be rare, and that contractors should be prohibited from using the extension authority because it contravenes our efforts to provide reliability and predictability to the termination process. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     In addition to the criteria set forth in § 421.505(b) (proposed § 421.405(b)) for extending non-random prepayment complex medical review, we will provide specific manual instructions to our contractors in IOM Manual 100-08 (Program Integrity Manual) to address this concern after the release of this final rule. 
                </P>
                <HD SOURCE="HD2">B. Comments Regarding the Proposed 1 Year Timeframe for Termination From Non-Random Prepayment Review </HD>
                <P>
                    <E T="03">Comment:</E>
                     We received several comments concerning whether 1 year is the appropriate timeframe to terminate a provider from non-random prepayment complex medical review. The concern of the commenters was whether or not CMS should keep providers on review for longer than 365 days in order to obtain 4 complete quarters of data; whether the contractor will stop reviewing claims on day 365 and start to calculate the error rate on day 366; or terminate review completely on day 365 before the error rate had been calculated. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We proposed that the 1-year timeframe would begin on the date provided in the letter notifying the provider or supplier of initiation of non-random prepayment complex medical review. We believe that 1 year is a sufficient amount of time for a provider or supplier to reduce its initial error rate or for the contractor to determine whether a referral to Benefit Integrity or extended medical review under § 421.505(b) (proposed § 421.405(b)) is necessary. Unless an exception applies under § 421.505(b) (proposed § 421.405(b)), the contractor must remove a provider or supplier from non-random prepayment complex medical review after 1 calendar year (365 days) from the date of notification of non-random prepayment complex medical review regardless of whether an error rate for the fourth quarter has been calculated. Thus, they would be removed from review on day 366. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter asked if a provider continues to incur a sustained or high level of payment error following termination, whether the appropriate procedure should be to place the provider back on non-random prepayment complex review. The commenter also noted that at that point, the burden of proof should shift to the contractor. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We have revised proposed § 421.505(d) (proposed § 421.405(d)) to indicate that if after the 1-year termination date the provider continues to have a sustained or high level of payment error, the contractor may reinitiate non-random prepayment complex review after 6 months, but only after a probe confirms that there continues to be a high level of payment error. When a provider or supplier is terminated from non-random prepayment complex medical review after 1 year of review and the contractor determines that the provider or supplier continues to have a high error rate despite educational interventions, the contractor must consider referring the provider or supplier to the contractor responsible for benefit integrity review. Contractors must also consider continuing educational interventions without performing further medical review or consider the need for post-payment medical review. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter questioned how the 1-year timeframe would be calculated if the contractor selects only 20 to 40 claims for the initial probe review and then terminates the edit. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     By “terminates the edit,” we believe the commenter means that after the initial 20 to 40 claims are selected, the contractor does not initiate non-random prepayment complex medical review. As previously stated, the 1-year timeframe is calculated from the date the provider or supplier is notified by letter that they are being subject to non-random prepayment complex manual review after the initial probe review is completed. A small sample (for example, 20 to 40 claims) enables the contractor to make an error rate determination in a short time period, so there is not an extended period of time when claims are paid without review. If a provider does not submit an adequate number of new claims for the probe review, the contractor has the option to complete the sample selection from paid claims. If a significant number of claims are billed and paid during the review process, the contractor has an option to complete a post-pay review process to collect the overpayment. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter asked if it is acceptable to have a provider on an intermittent non-random prepayment review for longer than 1 year if quarterly evaluation of the sample of claims shows that provider specific education has not resulted in significant improvement. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     In the circumstance described above and assuming that review could not be extended under § 421.505(b) (proposed § 421.405(b)), once a provider is removed from targeted non-random prepayment review, the contractor would need to conduct a new probe before it would be able to place that provider back on review and start the clock over again. 
                </P>
                <HD SOURCE="HD2">C. Comments Regarding the Proposed Provider Appeal Process </HD>
                <P>
                    <E T="03">Comment:</E>
                     Two commenters indicated that providers and suppliers should have some ability to appeal a probe review determination which places the provider or supplier on medical review. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Neither the statute nor the regulations provide the provider or supplier a right to appeal a probe review determination, which we assume the commenter means a finding by the contractor that there is a likelihood of sustained or high level of payment error. Nor does it require an expedited appeal if a provider remains on review for a given period of time. However, we note that a provider or supplier always has the ability to appeal the results of a contractor's determination on an individual claim. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     Several commenters suggested that the contractors should recompute the error rate to include reversals in each appeal level. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     If during the 1-year timeframe a provider or supplier is successful on appeal in overturning the initial medical review determination, we have instructed contractors through manual instructions located at 
                    <E T="03">http://www.cms.hhs.gov/manuals/IOM/list.asp</E>
                     and then click on “Publication 100-08”) to consider such appeals results when making decisions to continue medical review activities. However, after such consideration there may still be valid reasons for the contractor to elect not to remove providers or suppliers from review. Therefore, we are giving the contractor discretion to remove the provider or supplier from review based on appeals information. Please note that 
                    <PRTPAGE P="55757"/>
                    the timeframe allowed for appeal through all levels of appeal is not always accomplished within the 1-year timeframe made final in this rule. Therefore, it is not practical to require contractors to modify the error rate based on appeals results, as the appeals information may change through the levels of appeal. 
                </P>
                <HD SOURCE="HD2">D. Comments Regarding the Proposed Computation of Error Rate </HD>
                <P>
                    <E T="03">Comment:</E>
                     One commenter suggested that the computation of the quarterly error rate should account for the supplier's accreditation and past compliance. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We believe accreditation and past compliance are extremely important but in order to safeguard the Medicare Trust Fund we need to ensure that the error rate computation is based on current claims submitted. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     Several commenters indicated that we do not explain the process contractors use to determine what error rate is determined to be a “high level,” what mathematical probability or range constitute a “likelihood,” or what time period and intensity of billing errors meet the definition of “sustained.” 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We do not further define the terms “high level, likelihood, or sustained” in the definition of “complex medical review” under § 421.501 (proposed § 421.401) because we believe contractors need the administrative flexibility to determine whether an error rate is “high level, likely, or sustained.” A variety of factors influence our determinations of such payment error such as the scope of the problem, potential risk to the Trust Fund, the risk relative to other risks identified by contractor data analysis, and past history of the provider or supplier. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter stated that unless and until statistically meaningful verification of billing error is performed by a licensed medical professional through a complex review probe, a provider should not be placed on non-random prepayment complex medical review status. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We believe the probe sample is an appropriate tool to determine the nature and extent of the problem. A “provider-specific probe review” may only be performed by a clinician based on problems identified by contractor data analysis. We believe that requiring a physician to review every claim in a probe would be cost prohibitive to the contractor. In addition, we note that each contractor is required to employ a physician to provide their clinical expertise. Statistically valid verification would require a much larger sample than 20 to 40 claims, thus increasing the burden and cost to the provider or supplier. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter indicated that the 1-year mark for termination is not necessarily a true calendar year for all cases under such review. The commenter stated that we proposed to allow contractors to make code-specific error rate determinations on a quarterly basis. Contractors are not required to calculate error rates at the 1-year anniversary mark after the provider is sent notice of non-random prepayment complex medical review. That means that a provider whose anniversary falls at the beginning of a quarter can remain on review almost 3 months longer than a calendar year. Another commenter asked if a quarter was any 3-month period that the contractor chooses or if it must be a financial quarter. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Unless an exception applies under § 421.505(b) (proposed § 421.405(b)), the contractor must remove a provider or supplier from non-random prepayment complex medical review after 1 calendar year (365 days) from the date of notification of non-random prepayment complex medical review regardless of whether an error rate for the fourth quarter has been calculated. We will defer to the contractor as to how to calculate when the quarter begins. Depending on the timing of the initiation of non-random prepayment complex medical review, contractors may or may not have an opportunity to calculate a fourth quarter error rate for a particular provider or supplier. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     Two commenters requested a tiered system that depends upon the degree of improvement in a provider's error rate, or an option that would remove a provider from review when they meet a threshold of 10 percent or less of the overall error rate. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We initially considered whether a 90 to 95 percent decrease in a provider's or supplier's error rate was appropriate, but determined that, for purposes of this regulation, a 90 to 95 percent reduction in error rate would be impracticable. We continue to believe that an error rate reduction of 70 percent from the initial error rate calculated during probe review would protect the financial integrity of the Medicare program, and allow the provider or supplier a realistic opportunity to be terminated from non-random prepayment complex medical review. Our contractors will continue to retain the discretion to terminate providers and suppliers at an earlier date. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter was concerned about the lack of specific quantitative measures for triggering placement of providers on non-random prepayment complex medical review. The commenter recommended that we establish 30 percent as the national probe denial rate for triggering non-random prepayment complex medical review. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     In order for the contractors to have sufficient flexibility to guard the integrity of the Medicare Trust Fund, we leave the criteria for triggering review to the contractor's discretion. This allows the contractors to provide the specific level of review that best enables them to work with the provider or supplier to lower their error rate. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter indicated that although we recommend limiting agency probe edits to 20 to 40 claims, and limiting service specific probe edits to 100 claims, we do not provide direction as to a minimum number of claims to be reviewed when determining whether a provider or supplier is likely to have a sustained or high level of payment error rate. The commenter recommended that we create criteria for a minimum number of records to be reviewed before determining that a provider or supplier has a likelihood of sustained or high level of payment error. The commenter stated that this should be no fewer than 10 claims on a particular probe for a quarter. Another commenter asked if provider-specific probe reviews should only include claims for the particular item or service that may be billed in error. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The minimum number of claims to be reviewed in a probe will vary across provider and supplier type, volume, and service. Quarterly termination evaluation does not entail a probe. The contractor evaluates claims reviewed under the non-random prepayment complex medical review in a quarter and determines the error rate for selected claims during the quarter. The probe is used to establish the initial error rate only. The contractor does attempt to focus provider-specific probe review on those claims with items or services that may be billed in error. In the case of service specific review, the 70 percent reduction will be determined against the service-wide error rate. In some cases, service-specific review becomes a catalyst for provider-specific review of a subset of providers. In this instance, that subset would be measured against their own individual error rates. This is consistent with our Internet-Only Manual 100-08, Chapter 3, section 3.11.1.2. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter requested notice and comment rulemaking on the definition of “complex medical review.” 
                    <PRTPAGE P="55758"/>
                </P>
                <P>
                    <E T="03">Response:</E>
                     The definition and description of “complex medical review” were provided in the proposed rule (70 FR 58653, October 7, 2005), and as such, were subjected to notice and comment rulemaking. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     Two commenters urged us to revise the proposed provisions that require contractors terminate a provider's or supplier's non-random prepayment complex medical review and remove any language establishing a minimum timeframe that providers or suppliers are subject to review. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We agree with the commenters and have clarified in § 421.505(b) (proposed § 421.405(b)) that contractors may extend non-random prepayment complex medical review in certain cases and have clarified in § 421.505(a) (proposed § 421.405(a)) that there is no minimum timeframe that a provider or supplier must be on review. Unless an exception applies under § 421.505(b) (proposed § 421.405(b)) a provider or supplier must be removed from review if it meets either the 1 year or 70 percent criteria set forth in § 421.505(a) (proposed § 421.405(a)), and may be removed at any time at the discretion of the contractor. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter stated that updated error rate reports from the contractor to the provider need to be timely and specific, demonstrate individual claims decisions (paid or unpaid), and show a detailed accounting of how the quarterly error rate was calculated or updated. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We agree that the error rate reports should be given to providers with a narrative explanation. We will provide specific manual instructions in IOM Manual 100-08 (Program Integrity Manual) to our contractors in this regard after the release of this final rule. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter questioned how the error rate percentage is determined. Specifically the commenter asked if it is based on dollar amount, days of coverage, or if it depends on the type of service billed. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The error rate percentage is based on dollars. 
                </P>
                <HD SOURCE="HD2">E. Comments Regarding the Proposed Documentation Requirements </HD>
                <P>
                    <E T="03">Comment:</E>
                     We received several comments stating that the 10-minute estimated time for obtaining medical records discussed in the proposed rule (70 FR 58652, October 7, 2005) is not the correct estimate of needed time. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     In response to these comments, we have updated our estimate in the Collection of Information Requirements section of this final rule to 20 minutes to account for variations across providers or suppliers. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     Several commenters expressed concern that medical records and chart notes should not be relied upon to determine Medicare eligibility. The commenters believe that the medical records a supplier must collect and submit are inherently ambiguous, subjective, and not suited for uniform review. The commenters also believe that physicians do not typically document specific Medicare coverage criteria in their medical records, and the records are not created with an intention that they will be reviewed by third parties who are not familiar with the patients and their medical condition. The commenters are concerned that requiring physicians to document the medical records in this fashion will place a substantial burden on the physicians, cause nonclinicians to interfere with the prescribing physicians, and will create a new and relatively unfamiliar documentation scheme. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     This final rule does not change existing documentation requirements. We believe that current documentation requirements for providers and suppliers are designed to provide a comprehensive picture of a patient's history and condition. CMS and our contractors have implemented extensive educational outreach to both suppliers and the medical community pertaining to documentation requirements. 
                </P>
                <P>We require under § 421.505(a)(2) (proposed § 421.405(a)(2)) that providers and suppliers submit supporting medical documentation for claims under review in order for our contractors to be able to compute an error rate based on current claims. If the contractor is unable to calculate an error rate due to the failure or refusal by a provider or supplier to submit requested medical documentation, we have clarified in § 421.505(b)(1) (proposed § 421.405(b)(1)) that the contractor may extend non-random prepayment complex medical review for such a provider or supplier. Without sufficient medical records to calculate the quarterly error rate the contractor is unable to apply the regulation's criteria to a provider or supplier in determining whether to remove it from review. We believe it is a prerequisite for these rules to apply that providers and suppliers submit the required medical documentation for claims while they are on non-random prepayment complex medical review. </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter estimated that the burden for a supplier to locate and obtain the supporting documentation for a claim and forward the materials to the Medicare contractor for review will take 4.71 hours per claim. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We do not believe that this time is typical across provider types. In any event, we did not propose to change documentation requirements. 
                </P>
                <HD SOURCE="HD2">F. General Comments </HD>
                <P>
                    <E T="03">Comment:</E>
                     One commenter indicated that medical review findings are critical to performing focused education. The commenter stated that without the identified errors, local provider education and training would be less effective. The commenter believes that education would be general, based on global findings, and not specific to the provider's issue. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We agree that there are different interventions, including education, available to our contractors. This regulation does not limit those interventions. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter indicated that it would be difficult to determine if shifts to other codes not subject to review are inappropriate if claims for those services are not reviewed with records. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Nothing in this regulation precludes the contractor from performing record review to determine if an inappropriate shift in billing codes occurred. However, we are not requiring such additional review since in some cases shifts may be readily explained from data analysis alone. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter inquired if the referral to benefit integrity could be delayed while additional provider education and validation are performed. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Referral to benefit integrity may be delayed if additional provider education is needed and/or further validation is needed to evaluate a provider or supplier's error rate. A contractor may need to extend review of a provider or supplier beyond the 1-year timeframe or even if the initial error rate has been reduced by 70 percent or more if the contractor needs to further validate whether the provider or supplier has properly reduced its error rate. In some cases, a provider or supplier may use improper billing practices to reduce its error rate to minimize or avoid review. We proposed at § 421.405(b)(1) to extend review beyond 1 year if a provider or supplier engaged in two specific types of improper billing practices: T he provider or supplier stopped billing the code under review or shifted billing to another inappropriate code to avoid proper calculation of the error rate. 
                </P>
                <P>
                    In the final rule, we have added two more bases for the contractor to extend review at § 421.505(b)(1) (proposed § 421.405(b)(1)) and have clarified that 
                    <PRTPAGE P="55759"/>
                    review may be extended even if the provider or supplier has been on review for 1 year or has reduced its initial error rate by 70 percent or more. In addition to the proposed bases to extend review, the contractor may also extend review where the provider or supplier fails to respond to requests for medical records or the contractor determines the provider or supplier is engaging in improper claims or billing-related activities. 
                </P>
                <P>Because we cannot anticipate all types of improper claims or billing-related practices that providers and suppliers may engage in, we believe it is important that contractors have discretion to extend non-random prepayment complex medical review in any instance where the contractor determines the provider or supplier is engaging in improper claims or billing activities to avoid review. For example, a contractor may extend review if the provider or supplier starts billing under a different provider identification number with apparent intent to avoid proper calculation of the error rate. We believe the proposed bases for a contractor extending review may have fallen short of addressing all situations where the contractor may need to extend non-random prepayment complex medical review to evaluate whether the initial error rate has been appropriately reduced, and therefore, we are revising § 421.505(b)(1) (proposed § 421.405(b)(1)) to encompass these additional types of situations. </P>
                <P>If there is potential fraud, we believe it is vital for the reviewing contractor to quickly make the referral to Benefit Integrity. The contractor responsible for performing the benefit integrity review can validate if potential fraud has occurred or is ongoing. If the contractor does not find any evidence of fraud, then the benefit integrity contractor can still provide education to the provider. If the contractor detects possible fraud at any time during the medical review process, the contractor would refer the issue to the contractor responsible for benefit integrity review. </P>
                <P>
                    <E T="03">Comment:</E>
                     Two commenters recommended that the proposed timeframe to update the claims processing system should be changed from 2 to 5 business days once a provider or supplier is taken off of prepayment complex medical review. The commenters also stated that the system security regulations will prevent most contractors from discontinuing an edit in 2 business days. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Although we are not aware of what system security regulations the commenter is speaking of, we are revising § 421.505(c)(2) (proposed § 421.405(c)(2)) to state that the contractors' claims processing system must be updated within 5 business days after the contractor determines that the provider or supplier should be terminated from non-random prepayment complex medical review. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     A number of commenters indicated that we have not issued instructions that indicate that documentation requirements for power mobility devices (PMDs) vary by patient diagnosis. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We agree that we have not issued instructions that indicate that document requirements for power mobility devices vary by patient diagnosis. In addition, we believe that the example included in the proposed rule (70 FR 58651) was an inappropriate example, and therefore, we are not including that example as part of this final rule. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter stated that, when a provider or supplier is terminated from non-random prepayment complex medical review and a new probe review must be performed to determine if there is a high level of payment error, the probe review cost per claim is significantly higher than provider-specific prepayment review. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We realize that it may be more costly to complete a new probe review; however, we believe requiring a new probe provides assurance to the public that non-random prepayment complex review is data driven and its impact on providers and suppliers is not to be taken lightly. Contractors need to allocate resources as efficiently as possible to protect the Medicare Trust Fund. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter asked that we distinguish between the medical role of the physician and the collaborative role of the supplier. The commenter believes it is not the role of the supplier to review, analyze, and interpret medical records to fill the treating physician's prescription, and that it is not in the best interest of the beneficiary for the supplier to overturn the judgment of the patient's treating physician. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     This final rule does not add any new documentation requirements. We note that it is the supplier's responsibility to provide a legible copy of the written prescription and any other required information. We believe that a party engaged in healthcare-related business should ensure that their staff has adequate expertise to carry out its responsibilities, and should obtain the training necessary to achieve and maintain that level of expertise. 
                </P>
                <P>The supplier should obtain as much documentation from the patient's medical record as it needs to determine if the Medicare coverage criteria for payment have been met. If the information in the patient's medical record does not adequately support the medical necessity for the item, then the supplier is liable for the dollar amount of the assigned claims involved unless a properly executed advance beneficiary notice (ABN) of possible denial has been obtained. </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter recommended that we develop an expanded version of the current Certificate of Medical Necessity (CMN), or a template that employs several open-ended questions that could easily be used by physicians, suppliers, and beneficiaries to determine if medical necessity exists and to document that need. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     This comment is outside the scope of this regulation. We do not address CMNs in this regulation. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter asked if we expect all non-random prepayment complex medical review edits to be selecting 100 percent of a provider's claims for at least 1 year. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     No, contractors continue to have the flexibility to do less than 100 percent prepayment review. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter asked if the 1-year timeframe is for each provider or supplier in a progressive corrective action case, or for the progressive corrective action case itself. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The 1-year timeframe is for each provider placed on non-random prepayment complex medical review. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter asked if the probe review finds that a provider is submitting claims to Medicare for a service that is not a Medicare benefit, would a 100 percent non-random prepayment review be appropriate until the situation is corrected. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     If the probe review finds that a provider is submitting claims to Medicare for a service that is not a Medicare benefit, a 100 percent non-random prepayment review is an option open to the contractor to correct the situation. This regulation applies to these types of claims, as well as other inappropriate claims. If the provider or supplier is billing non-covered services under covered codes, the contractor may wish to refer to the contractor responsible for benefit integrity review for fraud or abuse investigation. The contractor responsible for benefit integrity review has the option of continuing prepayment review during their investigative process. 
                </P>
                <P>
                    Although we did not receive comments on what entities are 
                    <PRTPAGE P="55760"/>
                    considered CMS contractors, we want to clarify that a new type of contractor (as mandated by the MMA), the Medicare Administrative Contractors (MACs), are also contractors for purposes of this regulation. In the proposed rule, we stated that we enter into contractual agreements with contractors (for example, intermediaries, carriers, and program safeguard contractors (PSCs)) to perform medical review functions to ensure that items or services are covered and are reasonable and necessary in accordance with Medicare coverage policies and program instructions. For clarity, we are adding MACs to the types of contractors subject to these regulations and clarifying that this rule only applies to medical review not for benefit integrity purposes. 
                </P>
                <P>Section 421.500 (proposed § 421.400) is revised to read as follows: “CMS enters into contractual agreements with intermediaries, carriers, program safeguard contractors (PSCs), and Medicare Administrative Contractors (MACs) to perform medical review functions to ensure that items or services are covered and are reasonable and necessary in accordance with Medicare coverage policies and program instructions. </P>
                <HD SOURCE="HD1">IV. Provisions of the Final Rule </HD>
                <P>After the publication of the October 7, 2005 proposed rule, we published a final rule adding regulations to Part 421, subpart E. Therefore, the regulations in this final rule are finalized in Part 421, subpart F and the sections are renumbered as indicated throughout this final rule. We are also adopting the provisions as set forth in the proposed rule with the following changes. </P>
                <P>In § 421.500 (proposed § 421.400), although we did not receive comments on what entities are considered CMS contractors, we are clarifying that the Medicare Administrative Contractors (MACs), are also contractors subject to this regulation. In the proposed rule, we stated that we enter into contractual agreements with contractors (for example, intermediaries, carriers, and program safeguard contractors (PSCs)) to perform medical review functions to ensure that items or services are covered and are reasonable and necessary in accordance with Medicare coverage policies and program instructions. When the proposed rule was published in 2005, the MACs were not yet established and only intermediaries, carriers, and PSCs were conducting medical review. Now that MACs are in operation, we are clarifying that MACs, as required by the statute, are also subject to this regulation. We are also clarifying in § 421.500 (proposed § 421.400) that this rule only applies to medical review not for benefit integrity purposes. Section 421.500 (proposed § 421.400) is revised to read as follows: “CMS enters into contractual agreements with intermediaries, carriers, program safeguard contractors (PSCs), and Medicare Administrative Contractors (MACs) to perform medical review functions not for benefit integrity purposes to ensure that items or services are covered and are reasonable and necessary in accordance with Medicare coverage policies and program instructions. </P>
                <P>In § 421.501 (proposed § 421.401), we are adding the definition of “contractor” as used in this subpart. </P>
                <P>We are clarifying in § 421.505(a) (proposed § 421.405(a)) that there is no minimum timeframe that a provider or supplier must be on review. We are also correcting a technical error from the proposed rule where we stated “a contractor may terminate a provider or supplier” to read “a contractor must terminate a provider or supplier” (70 FR 58653). Unless an exception applies under § 421.505(b) (proposed § 421.405(b)), providers and suppliers must be removed if they meet either the 70 percent reduction in error rate criterion or have been on review for 1 year from the initiation of such review. Providers and suppliers may also be removed at any time at the discretion of the contractor. </P>
                <P>We are revising § 421.505(b)(1) (proposed § 421.405(b)(1)) to state that contractors have the discretion to extend non-random prepayment complex medical review if a provider or supplier fails to respond to requests for medical records, stops billing the code under review, shifts billing to another inappropriate code to avoid proper calculation of the error rate, or engages in any other improper claims or billing-related activity to avoid non-random prepayment complex medical review. </P>
                <P>We are revising § 421.505(c)(2) (proposed § 421.405(c)(2)) to state that the contractors' claims processing system must be updated within 5 business days after the contractor determines that the provider or supplier should be terminated from non-random prepayment complex medical review. </P>
                <P>In § 421.405(d) of the proposed rule, we stated that contractors must periodically reevaluate the provider or supplier's data and, if necessary, must place a provider or supplier that appears to have resumed a high level of payment error on complex medical review. Due to contractor resources, we are revising the language at § 421.505(d)(1) (proposed § 421.405(d)(1)) to state that contractors may periodically reevaluate the provider or supplier's data and, if necessary, may place a provider or supplier that appears to have resumed a high level of payment error on complex medical review. </P>
                <P>In § 421.505(d)(1) (proposed § 421.405(d)(1)), we are correcting a technical error from the proposed rule at § 421.405(d) to state that a provider or supplier found to have resumed a high level of payment error is placed back on “non-random prepayment complex medical review.” In § 421.505(d)(2) (proposed § 421.405(d)(2)), we have also clarified that a provider or supplier is not placed back on such review earlier than 6 months after termination of a previous non-random prepayment complex medical review. </P>
                <HD SOURCE="HD1">V. Collection of Information Requirements </HD>
                <P>
                    Under the Paperwork Reduction Act of 1995, we are required to provide 30-day notice in the 
                    <E T="04">Federal Register</E>
                     and solicit public comment before a collection of information requirement is submitted to the Office of Management and Budget (OMB) for review and approval. In order to fairly evaluate whether an information collection should be approved by OMB, section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995 requires that we solicit comment on the following issues: 
                </P>
                <P>• The need for the information collection and its usefulness in carrying out the proper functions of our agency. </P>
                <P>• The accuracy of our estimate of the information collection burden. </P>
                <P>• The quality, utility, and clarity of the information to be collected. </P>
                <P>• Recommendations to minimize the information collection burden on the affected public, including automated collection techniques. </P>
                <P>In summary, § 421.505 (proposed § 421.405) outlines the requirements and process for the termination and extension of non-random prepayment complex medical review, a form of complex medical review. Contractors conduct complex medical review to determine whether items or services billed are covered, correctly coded, and are reasonable and necessary for the condition of the patient. Under complex medical review the provider or supplier must submit a copy of the medical records that support the items or services billed. </P>
                <P>
                    The burden associated with this section is the time and effort necessary for the provider or supplier of services to locate and obtain the supporting documentation for the claim to Medicare and to forward the materials for submission to Medicare contractors for review. We expect that this 
                    <PRTPAGE P="55761"/>
                    information would generally be maintained by suppliers and or providers as a normal course of business and that this information will be readily available. 
                </P>
                <P>Based on public comments, we revised the burden estimate associated with this requirement. We increased the allotted time from 10 to 20 minutes per provider or supplier to locate, photocopy, and transmit this information to the contractor upon request. </P>
                <P>The total annual burden for all of the Medicare providers and suppliers associated with this requirement is estimated to be 966,667 hours (2.9 million requests for medical records × 20 minutes per provider or supplier). The burden associated with this information collection requirement is currently approved under OMB control number 0938-0969 with a January 31, 2010 expiration date. </P>
                <GPOTABLE COLS="05" OPTS="L2,i1" CDEF="s50,12C,12C,12C,12C">
                    <TTITLE>Table 1—Estimated Annual Reporting and Recordkeeping Burden</TTITLE>
                    <BOXHD>
                        <CHED H="1">OMB control No.</CHED>
                        <CHED H="1">Respondents</CHED>
                        <CHED H="1">Responses</CHED>
                        <CHED H="1">
                            Burden per 
                            <LI>response</LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual 
                            <LI>burden</LI>
                            <LI>(hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="01">0938-0969</ENT>
                        <ENT>1,160,000</ENT>
                        <ENT>2,900,000</ENT>
                        <ENT>20</ENT>
                        <ENT>966,667</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>966,667</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">VI. Regulatory Impact </HD>
                <P>We have examined the impacts of this rule as required by Executive Order 12866 on Regulatory Planning and Review (September 30, 1993, as further amended), the Regulatory Flexibility Act (RFA) (September 19, 1980, Pub. L. 96-354), section 1102(b) of the Social Security Act, section 202 of the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4), Executive Order 13132 on Federalism (August 4, 1999), and the Congressional Review Act (5 U.S.C. 804(2)). </P>
                <P>Executive Order 12866 (as amended by Executive Order 13258) directs agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). A regulatory impact analysis (RIA) must be prepared for major rules with economically significant effects ($100 million or more in any 1 year). This rule does not reach the economic threshold and thus is not considered a major rule. </P>
                <P>The RFA requires agencies to analyze options for regulatory relief of small businesses. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small governmental jurisdictions. Most hospitals and most other providers and suppliers are small entities, either by nonprofit status or by having revenues of $6.5 million to $31.5 million in any 1 year. Individuals and States are not included in the definition of a small entity. We are not preparing an analysis for the RFA because we have determined that this rule would not have a significant economic impact on a substantial number of small entities. We believe that this rule would decrease the costs for providers and suppliers because it establishes guidelines for terminating a provider or supplier from non-random prepayment complex medical review. We believe this rule would decrease the time and amount of resources spent on inappropriate reviews and would ensure that Medicare payments would not be withheld for extended time periods. Because a contractor would no longer be maintaining providers or suppliers on non-random prepayment complex medical review for extended periods, administrative expenses (for example, copying, mailing, and the retention of medical documentation) would be reduced. </P>
                <P>In addition, section 1102(b) of the Act requires us to prepare a regulatory impact analysis if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 604 of the RFA. For purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside of a Metropolitan Statistical Area and has fewer than 100 beds. We are not preparing an analysis for section 1102(b) of the Act because we have determined that this rule would not have a significant impact on the operations of a substantial number of small rural hospitals. </P>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995 also requires that agencies assess anticipated costs and benefits before issuing any rule whose mandates require spending in any 1 year of $100 million in 1995 dollars, updated annually for inflation. The threshold level is currently approximately $130 million. This rule would have no consequential effect on the governments mentioned or on the private sector. </P>
                <P>Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a proposed rule (and subsequent final rule) that imposes substantial direct requirement costs on State and local governments, preempts State law, or otherwise has Federalism implications. Since this regulation would not impose any costs on State or local governments, the requirements of E.O. 13132 are not applicable. </P>
                <P>In accordance with the provisions of Executive Order 12866, this regulation was reviewed by the Office of Management and Budget. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 42 CFR Part 421 </HD>
                    <P>Administrative practice and procedure, Health facilities, Health professions, Medicare, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="42" PART="421">
                    <AMDPAR>For the reasons set forth in the preamble, the Centers for Medicare &amp; Medicaid Services amends 42 CFR chapter IV as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 421—MEDICARE CONTRACTING</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 421 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>Sec. 1102 and 1871 of the Social Security Act (42 U.S.C. 1302 and 1395hh). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="421">
                    <AMDPAR>2. Subpart F is added consisting of § 421.500 through § 421.505 to read as follows: </AMDPAR>
                    <CONTENTS>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart F—Medical Review </HD>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>421.500 </SECTNO>
                            <SUBJECT>Medicare review functions. </SUBJECT>
                            <SECTNO>421.501 </SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <SECTNO>421.505 </SECTNO>
                            <SUBJECT>Termination and extension of non-random prepayment complex medical review.</SUBJECT>
                        </SUBPART>
                    </CONTENTS>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart F—Medical Review </HD>
                        <SECTION>
                            <SECTNO>§ 421.500 </SECTNO>
                            <SUBJECT>Medicare review function. </SUBJECT>
                            <P>
                                CMS enters into contractual agreements with intermediaries, carriers, Medicare Administrative Contractors (MACs), and program safeguard contractors (PSCs) to perform 
                                <PRTPAGE P="55762"/>
                                medical review functions not for benefit integrity purposes to ensure that items or services are covered and are reasonable and necessary in accordance with Medicare coverage policies and program instructions. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 421.501 </SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <P>As used in this subpart— </P>
                            <P>
                                <E T="03">Allowable charge</E>
                                 means the dollar amount (including co-payment and deductibles) that the Medicare program will pay for a particular item or service. 
                            </P>
                            <P>
                                <E T="03">Benefit integrity review</E>
                                 means medical review of claim information and medical documentation focusing on addressing situations of potential fraud, waste and abuse. 
                            </P>
                            <P>
                                <E T="03">Complex medical review</E>
                                 means all medical review of claim information and medical documentation by a licensed medical professional, for a billed item or service identified by data analysis techniques or probe review to have a likelihood of sustained or high level of payment error. 
                            </P>
                            <P>
                                <E T="03">Contractor,</E>
                                 as used in this subpart, means intermediaries, carriers, Medicare Administrative Contractors (MACs), and program safeguard contractors (PSCs). 
                            </P>
                            <P>
                                <E T="03">Error rate</E>
                                 means the dollar amount of allowable charges for a particular item or service billed in error as determined by complex medical review, divided by the dollar amount of allowable charges for that medically reviewed item or service. 
                            </P>
                            <P>
                                <E T="03">Initial error rate</E>
                                 means the calculation of an error rate based on the results of a probe review prior to the initiation of complex medical review. 
                            </P>
                            <P>
                                <E T="03">Medical review</E>
                                 means the process performed by a contractor to ensure that billed items or services are covered and are reasonable and necessary as specified under section 1862(a)(1)(A) of the Act. 
                            </P>
                            <P>
                                <E T="03">Nonclinician medical review staff</E>
                                 means specially trained medical review staff not possessing the knowledge, skills, training, or medical expertise of a licensed health care professional. 
                            </P>
                            <P>
                                <E T="03">Non-random prepayment complex medical review</E>
                                 means the prepayment medical review of claim information and medical documentation, by a licensed medical professional, for a billed item or service identified by data analysis techniques or probe review to have a likelihood of sustained or high level of payment error. 
                            </P>
                            <P>
                                <E T="03">Non-random prepayment medical review</E>
                                 means the prepayment medical review of claims, by nonclinical or clinical medical review staff, for a billed item or service identified by data analysis techniques or probe review to have a likelihood of a sustained or high level of payment error. 
                            </P>
                            <P>
                                <E T="03">Postpayment medical review</E>
                                 means medical review of claims, by nonclinical or clinical medical review staff, for a billed item or service after a claim has been paid. 
                            </P>
                            <P>
                                <E T="03">Provider-specific probe review</E>
                                 means the complex medical review of a small sample of claims, generally 20 to 40 claims, from a specific provider or supplier for a specific billing code to confirm that or determine whether the provider or supplier is billing the program in error. 
                            </P>
                            <P>
                                <E T="03">Random prepayment medical review</E>
                                 means the prepayment medical review of claims, by nonclinical or clinical medical review staff, for a billed item or service that has not been identified by data analysis techniques or probe review to have a likelihood of a sustained or high level of payment error. 
                            </P>
                            <P>
                                <E T="03">Quarterly error rate</E>
                                 means the calculation of an error rate based on the results of non-random prepayment complex medical review for a specific billing code for a specific quarter. 
                            </P>
                            <P>
                                <E T="03">Service-specific probe review</E>
                                 means the complex medical review of a sample of claims, generally 100 claims, across the providers or suppliers that bill a particular item or service to confirm that or determine whether the item or service is billed in error. 
                            </P>
                            <P>
                                <E T="03">Termination of non-random prepayment complex medical review</E>
                                 means the cessation of non-random prepayment complex medical review. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 421.505 </SECTNO>
                            <SUBJECT>Termination and extension of non-random prepayment complex medical review. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Timeframe that a provider or supplier must be on non-random prepayment complex medical review.</E>
                                 There is no minimum timeframe that a provider or supplier must be on review. Except for cases described in paragraph (b) of this section, a contractor must terminate a provider or supplier from non-random prepayment complex medical review— 
                            </P>
                            <P>(1) No later than 1 year following the initiation of non-random prepayment complex medical review; or </P>
                            <P>(2) When calculation of the error rate indicates that the provider or supplier has reduced its initial error rate by 70 percent or more. A contractor must review claims for a specific billing code aberrancy for the quarter and calculate the quarterly error rate for those claims medically reviewed in that quarter. In order for this determination to be made, the provider or supplier must submit a copy of the medical records that indicate that the items or services billed are covered, correctly coded, and are reasonable and necessary for the condition of the patient. </P>
                            <P>(3) When a provider or supplier is terminated from non-random prepayment complex medical review after 1 year of review and the contractor determines that the provider or supplier continues to have a high error rate despite educational interventions, the contractor must consider referring the provider or supplier to the contractor responsible for benefit integrity review. Contractors must also consider continuing educational interventions without performing further medical review or consider the need for post-payment medical review. </P>
                            <P>
                                (b) 
                                <E T="03">Extension of non-random prepayment complex medical review.</E>
                                 (1) A contractor has the discretion to extend non-random prepayment complex medical review if a provider or supplier stops billing the code under review, shifts billing to another inappropriate code to avoid proper calculation of the error rate, fails to respond to requests for medical records, or engages in any other improper claims or billing-related activity to avoid non-random prepayment complex medical review. If the reduction in the error rate is attributed to a 25 percent or greater reduction in the number of claims submitted for the specific billing code under review, non-random prepayment complex medical review for that provider or supplier may be extended. However, if the number of claims submitted for a specific code was reduced because the provider or supplier began billing claims using a new appropriate code, or there is another legitimate explanation for the reduced number of claims billed, the contractor retains discretion to terminate from or extend a provider or supplier on non-random prepayment complex medical review. 
                            </P>
                            <P>(2) If extended medical review is necessary, contractors must notify providers and suppliers in writing the reasons for the need to perform additional prepayment complex review. </P>
                            <P>
                                (c) 
                                <E T="03">Quarterly termination evaluation.</E>
                                 (1) Contractors, at a minimum, must evaluate the length of time a provider or supplier has been on non-random prepayment complex medical review on a quarterly basis. 
                            </P>
                            <P>(2) A determination as to whether the provider's or supplier's initial probe review error rate for a specific billing code has been reduced by 70 percent must also be evaluated quarterly. There is no minimum timeframe that a provider or supplier must be on review. </P>
                            <P>
                                (3) The contractor's quarterly error rate evaluations must be for the discrete 
                                <PRTPAGE P="55763"/>
                                quarter; a rolling error rate average over more than 1 quarter is not permitted. 
                            </P>
                            <P>(4) After the contractor determines that the provider or supplier must be terminated from non-random prepayment complex medical review, the claims processing system must be updated within 5 business days to ensure that a provider's or supplier's claims for a specific billing error are no longer suspended for non-random prepayment complex medical review. </P>
                            <P>
                                (d) 
                                <E T="03">Periodic re-evaluation.</E>
                                 (1) Once a provider or supplier is terminated from non-random prepayment complex medical review, contractors may periodically re-evaluate the provider or supplier's data and may place a provider or supplier that appears to have resumed a high level of payment error on non-random prepayment complex medical review. 
                            </P>
                            <P>(2) This review would only be initiated if a probe review confirms that there continues to be a high level of payment error. </P>
                            <P>(3) If there is a high level of payment error, a provider or supplier may be placed on non-random prepayment complex medical review no earlier than 6 months after termination of a previous non-random prepayment complex medical review. As set forth in § 421.505(a)(3) contractors may also refer the provider or supplier to the contractor responsible for benefit integrity review or place the provider or supplier on postpayment medical review.</P>
                        </SECTION>
                    </SUBPART>
                </REGTEXT>
                <SIG>
                    <FP>(Catalog of Federal Domestic Assistance Program No. 93.773, Medicare—Hospital Insurance; and Program No. 93.774, Medicare—Supplementary Medical Insurance Program) </FP>
                    <DATED>Dated: March 21, 2008. </DATED>
                    <NAME>Kerry Weems, </NAME>
                    <TITLE>Acting Administrator,  Centers for Medicare &amp; Medicaid Services. </TITLE>
                    <DATED>Approved: June 3, 2008. </DATED>
                    <NAME>Michael O. Leavitt, </NAME>
                    <TITLE> Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22307 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <CFR>42 CFR Parts 422 and 423 </CFR>
                <DEPDOC>[CMS-4124-F2] </DEPDOC>
                <RIN>RIN-0938-AO78 </RIN>
                <SUBJECT>Medicare Program; Revisions to the Medicare Advantage and Part D Prescription Drug Contract Determinations, Appeals, and Intermediate Sanctions Processes; Correcting Amendment </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; correcting amendment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In the December 5, 2007 issue of the 
                        <E T="04">Federal Register</E>
                        , we published a final rule finalizing the Medicare program provisions relating to contract determinations involving Medicare Advantage (MA) organizations and Medicare Part D prescription drug plan sponsors, including eliminating the reconsideration process for review of contract determinations, revising the provisions related to appeals of contract determinations, and clarifying the process for MA organizations and Part D sponsors to complete corrective action plans. In that final rule, we also clarified the intermediate sanction and civil money penalty provisions that apply to MA organizations and Part D sponsors, modified elements of MA organizations and Part D sponsors' compliance plans, retained voluntary self-reporting for Part D sponsors, implemented voluntary self-reporting for MA organizations, and revised provisions to ensure HHS has access to the books and records of MA organizations and Part D sponsors' first tier, downstream, and related entities. This correcting amendment corrects a limited number of technical and typographical errors identified in the December 5, 2007 final rule. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>These correcting amendments are effective September 26, 2008, except for the amendment to § 423.505, which is effective on January 1, 2009. The correcting amendments for § 422.756(d) and § 423.756(d) are applicable beginning January 4, 2008. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Christine Reinhard (410) 786-2987.  Stephanie Blaydes Kaisler (410) 786-0957. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <P>In FR Doc. 07-5946 (72 FR 68700 through 68741), the final rule entitled, “Revisions to the Medicare Advantage and Part D Prescription Drug Contract Determinations, Appeals, and Intermediate Sanctions Processes,” there were technical errors that have been identified and corrected in the regulations text of this correcting amendment. We note that correcting two of these technical errors, found at § 422.756(d) and § 423.756(d), ensure that certain existing provisions which were never intended to be the subject of notice and comment rulemaking, remain in place for the benefit of all affected parties, including MA organizations and Part D sponsors. The provisions in this correcting amendment for § 422.756(d) and § 423.756(d) are effective as if they were included in the final rule published December 5, 2007. Accordingly, the corrections are effective retroactive to January 4, 2008, the effective date of most of the provisions of the final rule. However, the provisions in this correcting amendment for § 423.505 are effective January 1, 2009 since these particular provisions in § 423.505 were not set to take effect until January 1, 2009. </P>
                <HD SOURCE="HD1">II. Summary of Errors in the Regulations Text </HD>
                <P>On pages 68726 and 68735 of the December 5, 2007 final rule, there were technical errors made in the regulation text of § 422.756(d) and § 423.756(d). Specifically, a typographical error in our amendatory instructions caused us to inadvertently omit from the Code of Federal Regulations (CFR) existing paragraphs § 422.756(d)(3) and § 423.756(d)(3) regarding the duration of an MA and Part D intermediate sanction, respectively. We note that these existing provisions were not intended to be revised in the December 5, 2007 final rule (72 FR 68700 through 68741). </P>
                <P>
                    On page 68732 of the December 5, 2007 final rule, our amendatory instruction indicated that we were revising § 423.505(i)(2)(i). However, when we set out the changed regulations text, we inadvertently revised paragraph (i)(2)(ii) instead of paragraph (i)(2)(i). This typographical error, if not corrected, would have inadvertently deleted from the CFR the current paragraph at § 423.505(i)(2)(ii) regarding the 10-year record retention requirement as of January 1, 2009, the effective date of this provision as specified in the final rule. The correct § 423.505(i)(2)(i) should read “HHS, the Comptroller General, or their designees 
                    <PRTPAGE P="55764"/>
                    have the right to audit, evaluate and inspect any books, contracts, records, including medical records, and documentation of the first tier, downstream, and related entities involving transactions related to CMS' contract with the Part D sponsor.” As stated above, the existing § 423.505(i)(2)(ii), which references the 10-year record retention requirements, remains in the CFR unchanged. 
                </P>
                <P>In § 423.505(i)(3)(iii) the term “related entity” is incorrectly used twice in the same sentence, so we have removed this duplication. In addition, we inadvertently included MA organization in § 423.505(i)(3)(iv) which only applies to Part D sponsors. We have revised the language accordingly. </P>
                <HD SOURCE="HD1">III. Waiver of Proposed Rulemaking and Delay in Effective Date </HD>
                <P>
                    We ordinarily publish a notice of proposed rulemaking in the 
                    <E T="04">Federal Register</E>
                     to provide a period for public comment before the provisions of a rule take effect in accordance with section 553(b) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). However, we can waive this notice and comment procedure if the Secretary finds, for good cause, that the notice and comment process is impracticable, unnecessary, or contrary to the public interest, and incorporates a statement of the finding and the reasons therefore in the notice. 
                </P>
                <P>
                    Section 553(d) of the APA ordinarily requires a 30-day delay in effective date of final rules after the date of their publication in the 
                    <E T="04">Federal Register</E>
                    . This 30-day delay in effective date can be waived, however, if an agency finds for good cause that the delay is impracticable, unnecessary, or contrary to the public interest, and the agency incorporates a statement of the findings and its reasons in the rule issued. 
                </P>
                <P>The provisions of this correcting amendment regarding the duration of sanctions at § 422.756(d) and § 423.756(d) make no substantive changes and are intended to restore provisions which were inadvertently removed from the CFR. These provisions were not revised in the final rule but were dropped because of a typographical error in our amendatory instructions. We must reinstate these provisions in the CFR to ensure that CMS may lift sanctions on MA and Part D plans as appropriate. </P>
                <P>In addition, a typographical error in our regulations text would have inadvertently removed the current § 423.505(i)(2)(ii) from the CFR as of the effective date for these provisions on January 1, 2009. We are taking this opportunity to correct this error in the CFR to ensure that the 10-year record retention requirements for Part D sponsors remains in the CFR unchanged. Without this correcting amendment, the Medicare Part D regulations could have been construed as being silent on the 10-year Part D recordkeeping requirement which could create confusion and uncertainty for affected parties regarding CMS' policy on this issue. </P>
                <P>Finally, we are also taking this opportunity to correct typographical errors in § 423.505(i)(3)(iii) and (iv). </P>
                <P>Because we are issuing this correcting amendment based on typographical errors, we find that undertaking further notice and comment procedures to incorporate these corrections into the December 5, 2007 final rule is unnecessary and contrary to the public interest. </P>
                <P>For the same reasons, we are also waiving the 30-day delay in effective date for § 422.756(d) and § 423.756(d) in this correcting amendment. We believe that it is in the public interest to ensure that the December 5, 2007 final rule accurately state the current law and CMS policy. Thus, delaying the effective date of these corrections would be contrary to the public interest. Therefore, we also find good cause to waive the 30-day delay in effective date for § 422.756(d) and § 423.756(d). </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>42 CFR Parts 422 and 423 </CFR>
                </LSTSUB>
                <AMDPAR>Accordingly, 42 CFR chapter IV is corrected by making the following correcting amendments to parts 422 and 423.</AMDPAR>
                <REGTEXT TITLE="42" PART="422">
                    <PART>
                        <HD SOURCE="HED">PART 422—MEDICARE ADVANTAGE PROGRAM </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 422 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>Secs. 1102 and 1871 of the Social Security Act (42 U.S.C. 1302 and 1395hh). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="422">
                    <AMDPAR>2. Section 422.756 is amended by adding paragraph (d)(3) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 422.756 </SECTNO>
                        <SUBJECT>Procedures for imposing intermediate sanctions and civil money penalties. </SUBJECT>
                        <STARS/>
                        <P>(d) * * * </P>
                        <P>
                            (3) 
                            <E T="03">Duration of sanction.</E>
                             The sanction remains in effect until CMS notifies the MA organization that CMS is satisfied that the basis for imposing the sanction has been corrected and is not likely to recur. 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="423">
                    <PART>
                        <HD SOURCE="HED">PART 423—VOLUNTARY MEDICARE PRESCRIPTION DRUG BENEFIT </HD>
                    </PART>
                    <AMDPAR>3. The authority citation for part 423 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>Secs. 1102, 1860D-1 through 1860D-42, and 1871 of the Social Security Act (42 U.S.C. 1302, 1395w-101 through 1395w-152, and 1395hh). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="423">
                    <AMDPAR>4. Section 423.505 is amended by—</AMDPAR>
                    <AMDPAR>A. Revising paragraph (i)(2)(i). </AMDPAR>
                    <AMDPAR>B. Revising paragraph (i)(2)(ii). </AMDPAR>
                    <AMDPAR>C. Revising paragraph (i)(3)(iii). </AMDPAR>
                    <AMDPAR>D. Revising paragraph (i)(3) (iv). </AMDPAR>
                    <P>The revisions read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 423.505 </SECTNO>
                        <SUBJECT>Contract provisions. </SUBJECT>
                        <STARS/>
                        <P>(i) * * * </P>
                        <P>(2) * * * </P>
                        <P>(i) HHS, the Comptroller General, or their designees have the right to audit, evaluate, and inspect any books, contracts, records, including medical records, and documentation of the first tier, downstream, and related entities involving transactions related to CMS' contract with the Part D sponsor. </P>
                        <P>(ii) HHS', the Comptroller General's, or their designee's right to inspect, evaluate, and audit any pertinent information for any particular contract period exists through 10 years from the final date of the contract period or from the date of completion of any audit, whichever is later. </P>
                        <P>(3) * * * </P>
                        <P>(iii) A provision requiring that any services or other activity performed by a first tier, downstream, and related entity in accordance with a contract or written agreement are consistent and comply with the Part D sponsor's contractual obligations. </P>
                        <P>(iv) A provision requiring the Part D sponsor's first tier, downstream, and related entities to produce upon request by CMS, or its designees, any books, contracts, records, including medical records and documentation of the Part D sponsor, relating to the Part D program, to either the sponsor to provide to CMS, or directly to CMS or its designees. </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="423">
                    <AMDPAR>5. Section 423.756 is amended by adding paragraph (d)(3) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 423.756 </SECTNO>
                        <SUBJECT>Procedures for imposing intermediate sanctions and civil money penalties. </SUBJECT>
                        <STARS/>
                        <P>(d) * * * </P>
                        <P>
                            (3) 
                            <E T="03">Duration of sanction.</E>
                             The sanction remains in effect until CMS notifies the Part D sponsor that CMS is satisfied that 
                            <PRTPAGE P="55765"/>
                            the basis for imposing the sanction is corrected and is not likely to recur. 
                        </P>
                        <STARS/>
                        <EXTRACT>
                            <FP>(Catalog of Federal Domestic Assistance Program No. 93.773, Medicare—Hospital Insurance; and Program No. 93.774, Medicare—Supplementary Medical Insurance Program)</FP>
                        </EXTRACT>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: September 16, 2008. </DATED>
                    <NAME>Ann C. Agnew, </NAME>
                    <TITLE>Executive Secretary to the Department.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22592 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <CFR>42 CFR Part 455 </CFR>
                <DEPDOC>[CMS-2271-F] </DEPDOC>
                <RIN>RIN 0938-AO97 </RIN>
                <SUBJECT>Medicaid Integrity Program; Eligible Entity and Contracting Requirements for the Medicaid Integrity Audit Program </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Section 1936 of the Social Security Act (the Act) (as added by section 6034 of the Deficit Reduction Act of 2005 (DRA) established the Medicaid Integrity Program to promote the integrity of the Medicaid program by requiring CMS to enter into contracts with eligible entities to: (1) Review the actions of individuals or entities furnishing items or services (whether on a fee-for-service, risk, or other basis) for which payment may be made under an approved State plan and/or any waiver of such plan approved under section 1115 of the Act; (2) audit claims for payment of items or services furnished, or administrative services rendered, under a State plan; (3) identify overpayments to individuals or entities receiving Federal funds; and (4) educate providers of services, managed care entities, beneficiaries, and other individuals with respect to payment integrity and quality of care. </P>
                    <P>This final rule will provide requirements for an eligible entity to enter into a contract under the Medicaid integrity audit program. The final rule will also establish the contracting requirements for eligible entities. The requirements will include procedures for identifying, evaluating, and resolving organizational conflicts of interest that are generally applicable to Federal acquisition and procurement; competitive procedures to be used; and procedures under which a contract may be renewed. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule is effective October 27, 2008. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Barbara Rufo, 410 786-5589 or Crystal High, 410-786-8366. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <HD SOURCE="HD2">A. Current Law </HD>
                <P>States and the Federal government share in the responsibility for safeguarding Medicaid program integrity. States must comply with Federal requirements designed to ensure that Medicaid funds are properly spent (or recovered, when necessary). CMS is the primary Federal agency responsible for providing oversight of States' Medicaid activities and facilitating their program integrity efforts. </P>
                <HD SOURCE="HD2">B. Medicaid Integrity Program </HD>
                <P>Section 6034 of the Deficit Reduction Act (DRA) of 2005 (Pub. L. 109-171, enacted on February 8, 2006) added a new section 1936 to the Act that established the Medicaid Integrity Program, referenced as the “Program” hereafter, to combat Medicaid fraud and abuse. The Program is intended to identify, recover, and prevent Medicaid overpayments. It is also intended to support the efforts of the State Medicaid agencies through a combination of support and technical assistance. </P>
                <P>Although individual States work to ensure the integrity of their respective Medicaid programs, the Program represents CMS' first national strategy to detect and prevent Medicaid fraud and abuse. The Program will provide CMS with the ability to more directly ensure the accuracy of Medicaid payments and to deter those who would exploit the program. </P>
                <P>Section 6034 of the DRA amended title XIX of the Act by redesignating the former section 1936 as section 1937; and adding the new 1936 “Medicaid Integrity Program.” The new section 1936 states the Secretary will promote the integrity of the Medicaid program by entering into contracts with eligible entities to carry out the following activities: </P>
                <P>• Review of actions of individuals or entities furnishing items or services (whether on a fee-for-service, risk, or other basis) for which payment may be made under the State plan approved under title XIX (or under any waiver of such plan approved under section 1115 of the Act) to determine whether fraud, waste, or abuse has occurred, or is likely to occur, or whether such actions have a potential for resulting in an expenditure of funds under title XIX in a manner which is not intended under the provisions of title XIX. </P>
                <P>• Audit of claims for payment for items or services furnished, or administrative services rendered, under a State plan under title XIX, including cost reports, consulting contracts, and risk contracts under section 1903(m) of title XIX. </P>
                <P>• Identification of overpayments to individuals or entities receiving Federal funds under title XIX. </P>
                <P>• Education of providers of services, managed care entities, beneficiaries, and other individuals with respect to payment integrity and quality of care. </P>
                <P>Section 1936 of the Act also mandates that the Secretary will, by regulation, establish procedures which will include the following: </P>
                <P>• Procedures for identifying, evaluating, and resolving organizational conflicts of interest that are generally applicable to Federal acquisition and procurement. </P>
                <P>• Competitive procedures to be used when entering into new contracts under this section; when entering into contracts that may result in the elimination of responsibilities under section 202(b) of the Health Insurance Portability and Accountability Act of 1996; and any other time considered appropriate by the Secretary. </P>
                <P>• Procedures under which a contract under this section may be renewed without regard to any provision of law requiring competition if the contractor has met or exceeded the performance requirements established in the current contract. </P>
                <P>
                    CMS has determined not to address in this final rule the above bullet that references the Health Insurance Portability and Accountability Act of 1996 (HIPAA). We have determined that section 202(b) of HIPAA addressed certain Medicare contracting issues which, because of structural differences between the Medicare and Medicaid programs, such as the fact that the Federal Government does not utilize carriers or fiscal intermediaries in the Federal administration of the Medicaid program, do not pertain to the Medicaid contracting environment. Moreover, we have also determined that the provisions of the Act established by section 202(b) of HIPAA have since been repealed by section 911 of the Medicare Prescription Drug, Improvement, and Modernization Act of 2003. 
                    <PRTPAGE P="55766"/>
                </P>
                <HD SOURCE="HD2">C. Medicaid Integrity Audit Program Contract Overview </HD>
                <P>The Medicaid Integrity Audit Program will use three separate Indefinite-Delivery Indefinite Quantity (IDIQ) contracts to achieve the goals identified above. These contracts include the following: Audit and Identification of Overpayment Medicaid Integrity Contractor (Audit MIC), Review or Provider MIC (Review MIC) to five contractors, and Education MIC. </P>
                <P>CMS has awarded two of the three IDIQ contracts to Medicaid Integrity Contractors (MICs) to carry out the Secretary's mandated activities described above. In December 2006, CMS awarded Audit MIC IDIQ contracts to five contractors and awarded the Review MIC IDIQ contracts to five contractors. The Education MIC is yet to be awarded. The IDIQ contracts will be managed by task orders. Each of the MIC IDIQ contractors will have the opportunity to bid for task orders authorizing specific work within the scope of the appropriate IDIQ contract. To date, one task order has been awarded to an Audit MIC and one to a Review MIC. In addition to the requirements described in the IDIQ contract, the task order statement of work provides further clarification and specifics as to the work to be performed.</P>
                <P>CMS is planning to release individual task orders for five jurisdictions, which are comprised of two CMS Regions, as well as for identified special initiatives. When requesting task order proposals, CMS provided protocols to the Audit MICs to use during the course of an audit. The protocols, which were developed by contractor, provide specific guidelines and audit steps that each Audit MIC will follow during an audit. This will help ensure that audits are conducted in a uniform manner among the Audit MICs and across the five jurisdictions. In an effort to ensure that the protocols concisely and accurately describe the auditing process, CMS had the protocols reviewed and tested by a separate CMS contractor. Having a separate CMS contractor review the protocols eliminated the potential of conflict of interest that may have occurred had the development contractor reviewed and tested the protocols. </P>
                <P>Auditing is scheduled to begin in mid-June 2008 with the Atlanta jurisdiction which is comprised of CMS Regions II and IV. With the first task order, the Review MIC will initially concentrate on CMS' Region IV, the Atlanta Region; the Audit MIC will concentrate on CMS' Region III and IV, the Atlanta and Philadelphia Region. </P>
                <HD SOURCE="HD1">II. Provisions of the Proposed Regulations and Responses to Comments </HD>
                <HD SOURCE="HD2">Eligible Entity and Contracting Requirements for the Medicaid Integrity Audit Program </HD>
                <P>Section 6034 of the DRA of 2005 (DRA) amended title XIX of the Act by establishing, under the new section 1936, the Medicaid Integrity Program to promote the integrity of the Medicaid program by requiring CMS to enter into contracts with eligible entities to: (1) Review the actions of individuals or entities furnishing items or services (whether on a fee-for-service, risk, or other basis) for which payment may be made under an approved State plan and/or any waiver of such plan approved under section 1115 of the Act; (2) audit claims for payment of items or services furnished, or administrative services rendered, under a State plan; (3) identify overpayments to individuals or entities receiving Federal Medicaid funds; and (4) educate providers of services, managed care entities, beneficiaries, and other individuals with respect to payment integrity and quality of care. </P>
                <P>In the proposed rule we provided requirements for which an entity is eligible to enter into a contract under the Medicaid integrity audit program. The requirements would include procedures for identifying, evaluating, and resolving organizational conflicts of interest that are generally applicable to Federal acquisition and procurement; competitive procedures to be used; and procedures under which a contract may be renewed. </P>
                <P>
                    In the November 23, 2007 
                    <E T="04">Federal Register</E>
                     (72 FR 65686), we published the proposed rule entitled “Medicaid Integrity Program; Eligible Entity and Contracting Requirements for the Medicaid Integrity Audit Program,” and provided for a 30 day public comment period. We received a total of 3 timely comments from State government agencies and a health care association. Brief summaries for each proposed provision, a summary of the public comments we received, and our responses to comments are set forth below. 
                </P>
                <HD SOURCE="HD3">General Comments </HD>
                <P>
                    <E T="03">Comment:</E>
                     One commenter indicated that although they support the provisions of this proposed rule, they believe the rule does not sufficiently establish requirements for the MICs to ensure their work is carried out in an efficient, effective, and defensible manner. The commenter also stated that the proposed rule does not address methods of assuring coordination between the Medicaid integrity functions and existing programs already on-going in the States. In addition, the commenter notes that the proposed rule does not address how to prevent duplication of efforts or prevent multiple audits related to the same time period or same claims. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The Medicaid Integrity Group (MIG), a component within CMS which has been created in order to carry out the Medicaid Integrity Program, will coordinate and communicate with its stakeholders in an effort to prevent duplication of efforts. In addition, the MIG will closely monitor the performance of the MICs. The roles and responsibilities of the MICs are further defined within the IDIQ contract as well as each task order. In addition, the MICs have been provided with protocols to help guide them through the audit process. The Audit MICs are responsible for performing comprehensive and focused audits. The goal of the audits is to examine payments to individuals or entities providing items or services under title XIX of the Act for the purposes of identifying potential overpayments to those individuals or entities. The Review MICs are responsible for performing reviews of providers furnishing Medicaid items or services to determine whether Medicaid fraud, waste, or abuse has occurred, is likely to occur, or whether Medicaid provider actions have the potential of causing inappropriate or incorrect expenditure of Medicaid funds. The Review MICs are also responsible for analyzing data and performing risk assessments of Medicaid data including, but not limited to, claims for payment under title XIX of the Act. The Education MICs will be responsible for promoting the integrity of the Medicaid program by educating providers of services, managed care entities, and other individuals with respect to Medicaid payment and quality of care. 
                </P>
                <HD SOURCE="HD3">Subpart C—Medicaid Integrity Audit Program </HD>
                <HD SOURCE="HD3">Section 455.200 Basis and Scope </HD>
                <P>
                    In the proposed § 455.200 we set forth the statutory basis, section 1936 of the Act, for promulgating this rule. We proposed, in subpart C, § 455.200(b), Basis and Scope, additional language stating that part of the Medicaid Integrity Program's scope is to carry out the Medicaid integrity audit functions. CMS also published a final rule in the 
                    <E T="04">Federal Register</E>
                     on November 30, 2007 (72 FR 67653), entitled “Limitation on Contractor Liability” that finalized the portion of our proposed rule addressing 
                    <PRTPAGE P="55767"/>
                    the limitation on a contractor's liability to carry out a contract under the Medicaid Integrity Program. In addition, subpart C would apply to entities that seek to compete for, or receive an award of, a contract under section 1936 of the Act. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     A commenter expressed concern that the proposed rule fails to recognize the respective roles of State Medicaid Agencies and Medicaid Fraud Control Units. The commenter additionally stated the proposed rule is silent on the respective roles of the States and the new contractors and silent on any coordination of effort between the eligible entities and the States. The commenter recommended that the rule be expanded to clarify the relationship between the States and any contracted entities, including the plan for coordination of effort and addressing individual State plan provisions. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     This final rule is not designed to discuss the roles of State Medicaid Agencies and Medicaid Fraud Control Units. There are however, regulations set forth in 42 CFR part 455—Program Integrity: Medicaid, that address the relationships with States. These regulations, which will remain in effect, at § 455.21, describe the cooperation with State Medicaid Fraud Control Units and the provisions at § 455.12 address State plan requirements. In addition, when conducting the audits, the Audit MICs will utilize established protocols that provide guidance on how the MICs are to coordinate with the individual States. 
                </P>
                <HD SOURCE="HD3">Section 455.230 Eligibility Requirements </HD>
                <P>In § 455.230 we described that an eligible entity may enter into a Medicaid integrity audit program contract if it: </P>
                <P>• Has demonstrated the capability to carry out the contractor activities; </P>
                <P>• In carrying out such activities, agrees to cooperate with the Inspector General of the Department of Health and Human Services, the Attorney General, and other law enforcement agencies, as appropriate, in the investigation and deterrence of fraud and abuse in relation to title XIX and in other cases arising out of such activities; </P>
                <P>• Maintains an appropriate written code of conduct and compliance policies that include, without limitation, an enforced policy on employee conflicts of interest; </P>
                <P>• Complies with such conflict of interest standards are generally applicable to Federal acquisition and procurement; and, </P>
                <P>• Meets other requirements the Secretary may impose. </P>
                <P>It would not be possible to identify in this rule every possible contractor requirement that may appear in a future solicitation. In order to permit maximum flexibility to tailor our contractor eligibility requirements to specific solicitations while satisfying section 1936 of the Act, any additional requirements would be contained in the applicable solicitation. </P>
                <P>
                    <E T="03">Comment:</E>
                     A commenter strongly recommended that the MIC utilize medical directors from the outset of claims reviews and that complex medical decisions made by physician specialists and specialized mid-level providers be reviewed by a physician from a like specialty. 
                </P>
                <P>Another commenter suggested that this section be amended by clarifying the categories of entities eligible to perform the audit functions. For example, the commenter inquired as to whether State Medicaid agencies would qualify, and addressed the potential conflict of interest that may arise if a MIC already acts as a fiscal agent in one or more States and/or performs key Medicaid administrative functions including, but not limited to, claims adjudication, provider enrollment, pharmacy benefits management, etc. </P>
                <P>
                    <E T="03">Response:</E>
                     The Audit MICs are required, as described in the IDIQ contract, to have as key personnel a medical director. The Audit MICs are to ensure that questions of medical necessity are reviewed by physicians with appropriate expertise. 
                </P>
                <P>A State Medicaid Agency will not be able to operate as a MIC. We adhered to the requirements of the Federal Acquisition Regulation (FAR) organizational conflict of interest requirements found at 48 CFR subpart 9.5 when soliciting contracts for the Medicaid Integrity Program. </P>
                <HD SOURCE="HD3">Section 455.232 Medicaid Integrity Audit Program Contractor Functions </HD>
                <P>In § 455.232 we identified the functions of the Medicaid integrity audit program contractor as follows: </P>
                <P>• Review of the individual actions or entities furnishing items or services (whether on a fee-for-service, risk, other basis) for which payment may be made under a State Plan approved under title XIX (or under any waiver of such plan approved under section 1115 of the Act) to determine whether fraud, waste, or abuse has occurred, is likely to occur, or whether such actions have the potential for resulting in an expenditure of funds under title XIX in a manner which is not intended under the provisions of title XIX. </P>
                <P>• Audit of claims for payment for items or services furnished or administrative services rendered, under a State plan under title XIX, including cost reports; consulting contracts; and risk contracts under section 1903(m) of the Act. </P>
                <P>• Identification of overpayments to individuals or entities receiving Federal funds under title XIX. </P>
                <P>• Educating providers of service, managed care entities, beneficiaries, and other individuals with respect to payment integrity and quality of care. </P>
                <P>
                    <E T="03">Comment:</E>
                     Several commenters indicated there is no direction on how the contractors should coordinate with existing State Medicaid integrity programs and Medicaid Fraud Control Units. They expressed concern that this will result in duplication of efforts and possible interference with State program integrity investigations. One commenter recommended that we add a bullet to read: Coordinate any provider specific action outlined above including but not limited to, claim audits, other audits, overpayment recoveries and provider education with appropriate State Medicaid agency, before, during and after the action. Another commenter questioned how the contractors will coordinate with the State surveillance and utilization review (SUR) functions; how the contractors will be assigned their integrity cases; how the source data will be used by contractors to determine audit targets; whether the contactors be allowed to access the Medicaid Management Information Systems (MMIS); who will perform the data analysis; and to whom the contractor will refer suspicion of fraud cases. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     As previously stated under the Background section 
                    <E T="03">C. Medicaid Integrity Program Contract Overview,</E>
                     CMS has awarded two IDIQ contracts each of which are managed by task orders. When CMS released the request for task order proposal for the Audit MICs, CMS issued protocols to which the Audit MICs must adhere to when performing audits. The protocols provide specific guidance as to how the Audit MICs are to coordinate and communicate with State agencies. The task order instructs the Audit MICs to refer any instances of potential cases of fraud to the CMS as well as to the Department of Health and Human Services, Office of Inspector General (OIG). The task order further defines the Audit MIC roles and responsibilities for coordinating with law enforcement. The Review MICs will be responsible for performing reviews of providers furnishing Medicaid items or services to determine whether Medicaid fraud, waste, or abuse has occurred, is likely to occur, or whether provider actions 
                    <PRTPAGE P="55768"/>
                    have the potential of causing inappropriate or incorrect expenditure of Medicaid funds. After performing these reviews, the Review MICs will provide their findings to CMS. CMS will provide the Audit MICs with the specific providers to be audited. The Review MICs will not perform audits. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     A commenter suggested that the MICs should allow providers to track electronically the status of claims. The commenter indicated that they have experienced frustration with the Recovery Audit Contractors (RAC) demonstration contractor and the lack of communication between the RAC and provider regarding the status of claims under review and therefore suggested that providing this information to the providers will enable them to plan accordingly. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     It is important to note that the RAC is a separate program from the Medicaid Integrity Audit Program. The RAC operates under different statutory authority and is associated with Medicare and not Medicaid. While it is not feasible to implement a system as suggested by the commenter, States and providers will have an opportunity to comment on the findings of a provider audit before the audit is completed and an overpayment is finally and formally identified. To minimize the likelihood of duplication of effort, before the MIG communicates audit targets to the Audit MICs, the MIG will communicate with the State program integrity offices and State Medicaid Fraud Control Units, among others, to ensure that a proposed audit does not interfere with an ongoing investigation. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     A commenter stated that the language of the proposed rule describing the functions of the contractors was broad and ambiguous. The commenter further noted that this language failed to provide sufficient guidance by which the intent of the statute can be determined, and appears to leave the contractors in a policy-making role. The commenter recommended the language be removed or modified to make clear the responsibility of the contractors. The commenter questions whether there are standard criteria for the contractors to use to determine that an action is likely to result in fraud, waste or abuse and whether there are specific audit standards that must be followed. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     MICs are not policy-making entities. We have outlined the MICs' roles and responsibilities not only in the proposed rule, but also in the MICs IDIQ contracts as well as in the task orders. The Audit MICs have been provided audit protocols, which provide guidance on how to conduct audits and which set forth audit standards. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     A commenter suggested the proposed rule is silent on the qualifications of the potential contractors. The commenter also questioned whether there will be minimum education and training requirements; how performance will be measured; whether there will be evaluations and whether the criteria on which they are based will be made public; and whether they will be required to show a better return on investment than the States. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The IDIQ contracts specify minimum qualifications that the MICs must meet. CMS evaluated the qualifications information bidders submitted in selecting the MICs. The MICs are not required to show a better return on investment than the States. Although individual States work to ensure the integrity of their respective programs, the Medicaid Integrity Audit Program provides CMS with the ability to set in place a national strategy to ensure the accuracy of Medicaid payments and to deter those exploiting the program. This advances goals that are shared by the States and Federal government. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     A commenter expressed concern that it is unclear what entity is responsible for collecting the overpayments and defending the audit findings, and what appeal process will be followed. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Pursuant to existing regulations at part 433, Subpart F, once CMS formally identifies a Medicaid overpayment, CMS will collect the federal share of the overpayment from a State. The individual States will be responsible for collecting overpayments from providers. Providers may utilize the laws and procedures of the State, including State appellate procedures, to challenge findings concerning an overpayment. A determination by a State administrative or judicial proceeding altering or dismissing a finding of, or relating to, a provider overpayment, however, will not necessarily relieve a State of the obligation to refund the federal share of CMS' determined overpayment. During the audit process, CMS, Audit MIC, and the State will confer and discuss the audit findings before CMS formally identifies an overpayment. 
                </P>
                <HD SOURCE="HD3">Section 455.234 Awarding of a Contract </HD>
                <P>Section 455.234 would specify that a Medicaid integrity audit contract will be awarded in accordance with 48 CFR chapters 1 and 3 (the Federal Acquisition Regulation (FAR) and the Health and Human Services Acquisition Regulation, respectively), this subpart, and all other applicable laws and regulations. In accordance with section 1936 of the Act, we would specify that these competitive procedures and requirements will be used as follows: </P>
                <P>• When entering into new contracts under this section. </P>
                <P>• At any other time considered appropriate by the Secretary. In addition, we proposed to specify in § 455.234 that an entity must meet the eligibility requirements established in proposed § 455.230 to become eligible to be awarded a Medicaid integrity audit program contract. </P>
                <P>
                    <E T="03">Comment:</E>
                     A commenter stated that although the DRA does not require that the contractor be retained on a contingency-fee basis, they would caution CMS from using such a compensation scheme. The commenter believed tying a contractor's payment to the volume of claims denied creates a perverse incentive irrespective of the claims' merits. The commenter also suggested that CMS should allow providers to retain funds recouped as part of the MIC's work until all avenues of appeal are exhausted. The commenter recognized this is not common practice, but believes it is within the Secretary's authority to administer the recovery program under section 1885 of the Act. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The Audit MICs will not be compensated on a contingency fee basis. 
                </P>
                <P>In response to the comment indicating CMS should allow providers to retain monies recouped during the course of appeals, it is important to note that the recoupment of overpayments is not the responsibility of the MIC, but will remain the responsibility of the State. Whether the provider is allowed to retain recouped funds until the appellate process is complete will depend on State law. CMS will, however, recover from States the Federal share of an overpayment consistent with the existing statutory and regulatory requirements. Section 1885 is a provision of the Medicare statute, title XVIII of the Act. Section 1885 does not apply to the Medicaid Integrity Program. The Medicaid statue is at title XIX of the Act. </P>
                <HD SOURCE="HD3">Section 455.236 Renewal of a Contract </HD>
                <P>
                    In § 455.236, we proposed that an initial contract term would be defined in the Medicaid integrity audit program contract and a renewal clause may be included in the contract. We also proposed that we may, but are not required to, renew the Medicaid integrity audit program contracts without regard to any provision of law requiring competition if the contractor 
                    <PRTPAGE P="55769"/>
                    has met or exceeded the performance requirements established in the current contract. 
                </P>
                <P>In accordance with sections 1936(c)(2) and (3) of the Act, we proposed in § 455.236(b) that we may renew a Medicaid integrity audit program contract without competition if the contractor continues to meet all requirements of the proposed subpart C, the contractor meets or exceeds the performance requirements established in its current contract, and it is in the best interest of the Federal Government. </P>
                <P>At § 455.236(a) we proposed that if CMS does not renew a contract, the contract would end in accordance with its terms. We also proposed that the contractor would not have a right to a hearing or judicial review regarding our renewal decision. </P>
                <P>We did not receive public comments on our proposed provision. Therefore, we adopt the provisions as proposed. </P>
                <HD SOURCE="HD3">Section 455.238 Conflict of Interest </HD>
                <P>We proposed to establish at § 455.238 the process for identifying, evaluating, and resolving conflicts of interest as mandated by section 1936(c)(2) and (3) of the Act. We adhered to the requirements of the FAR's organizational conflict of interest requirements found at 48 CFR subpart 9.5 when soliciting contracts for the Medicaid integrity audit program. Due to the sensitive nature of the work to be performed under the contract, the need to preserve public trust, and the history of fraud and abuse in the Medicaid program, we would maintain the presumption that each prospective contract involves a significant potential organizational conflict of interest. </P>
                <P>Prior to awarding a Medicaid integrity audit program contract, the contracting officer will draft an organizational conflict of interest clause specific to the contractor for inclusion in the contract. In general we would not enter into a Medicaid integrity audit program contract with an offeror or an existing Medicaid integrity audit program contractor that has been determined to have, or that has the potential for, an unresolved organizational conflict of interest. </P>
                <P>We did not receive public comments on our proposed provision. Therefore, we adopt the provisions as proposed. </P>
                <HD SOURCE="HD3">Section 455.238(a) </HD>
                <P>At § 455.238(a), we proposed that an offeror for a Medicaid integrity audit program contract is, and the Medicaid integrity audit program contractors are, subject to the conflict of interest standards and requirements of the FAR organizational conflict of interest guidance found at 48 CFR subpart 9.5, and the requirements and standards that are contained in each individual contract awarded to perform the functions described under section 1936 of the Act. </P>
                <P>We did not receive public comments on our proposed provision. Therefore, we adopt the provisions as proposed. </P>
                <HD SOURCE="HD3">Section 455.238(b) </HD>
                <P>In § 455.238(b), we proposed to include post award discussions in which the contactor will present any later occurring or identified conflict of interest to CMS for resolution. We proposed that we would consider a post award conflict of interest resolution discussion if, during the term of the contract, the contractor or any of its employees, agents, or subcontractors received, solicited, or arranged to receive any fee, compensation, gift, payment of expenses, offer of employment, or any other thing of value from any entity that is reviewed, audited, investigated, or contacted during the normal course of performing activities under a Medicaid integrity audit program contract. We incorporated the definition of “gift” from the Standards of Ethical Conduct for Employees of the Executive Branch [5 CFR 2635.203(b)]. </P>
                <P>We did not receive public comments on our proposed provision. Therefore, we adopt the provisions as proposed. </P>
                <HD SOURCE="HD3">Section 455.238(c) </HD>
                <P>In § 455.238(c) we proposed that if CMS has determined that a contractor's activities are creating a conflict, then a conflict of interest has occurred during the term of the contract. We proposed if such an event has occurred, among other actions, we may, as we deem appropriate: </P>
                <P>• Not renew the contract for an additional term; </P>
                <P>• Modify the contract; or </P>
                <P>• Terminate the contract. </P>
                <P>The proposed rule did not describe all of the information that may be required under each task order, or the level of detail that would be required. Therefore, we proposed to have the flexibility to tailor the requirements to each individual procurement. </P>
                <P>
                    Because potential offerors may have questions about whether information submitted in response to a solicitation, including information regarding potential conflicts of interest, may be redisclosed under the Freedom of Information Act (FOIA), we provided the following information. To the extent that a proposal containing information is submitted to us as a requirement of a competitive solicitation under 41 U.S.C. Chapter 4, Subchapter IV, we proposed to withhold the proposal when requested under the FOIA. This withholding is based upon 41 U.S.C. 253b(m). However, we proposed one exception to this policy. It involves any proposal that is set forth or incorporated by reference in the contract awarded to the proposing offeror. Such a proposal may not receive categorical protection. Rather, we would withhold, under 5 U.S.C. 552(b)(4), information within the proposal that is required to be submitted that constitutes trade secrets or commercial or financial information that is privileged or confidential, provided the criteria established by 
                    <E T="03">National Parks &amp; Conservation Association</E>
                     v. 
                    <E T="03">Morton,</E>
                     498 F.2d 765 (D.C. Cir 1974), as applicable, are met. For any such proposal, we proposed to follow pre-disclosure notification procedures set forth at 45 CFR 5.65(d). 
                </P>
                <P>
                    We proposed that proposal containing the information submitted to us under an authority other than 41 U.S.C. Chapter 4, Subchapter IV, and any information submitted independent of a proposal would be evaluated solely on the criteria established by 
                    <E T="03">National Parks &amp; Conservation Association</E>
                     v. 
                    <E T="03">Morton</E>
                     and other appropriate authorities to determine if the proposal in whole or in part contains trade secrets or commercial or financial information that is privileged or confidential and protected from disclosure under 5 U.S.C. 552(b)(4). Again, for any such proposal, we proposed to follow pre-disclosure notification procedures set forth at 45 CFR 5.65(d) and will also invoke 5 U.S.C. 552(b)(6) to protect information that is of a highly sensitive personal nature. It should be noted that the protection of proposals under FOIA does not preclude us from releasing contractor proposals when necessitated by law, such as in the case of a lawful subpoena. 
                </P>
                <P>We did not receive public comments on our proposed provision. Therefore, we adopt the provisions as proposed. </P>
                <HD SOURCE="HD3">Section 455.240 Conflict of Interest Resolution </HD>
                <P>We described at § 455.240(a) how a conflict of interest may be resolved. We stated that a Conflicts of Interest Review Board may be established and convened at any time during the term of the contract, as well as during the procurement process, to evaluate and assist the contracting officer in resolving conflicts of interest. We proposed to determine when or if the Board will be convened. </P>
                <P>
                    We proposed, at § 455.240(b), to specify that a resolution of an 
                    <PRTPAGE P="55770"/>
                    organizational conflict of interest is a determination by the contracting officer that: 
                </P>
                <P>• The conflict is mitigated; </P>
                <P>• The conflict precludes award of a contract to the offeror; </P>
                <P>• The conflict requires that we modify an existing contract; </P>
                <P>• The conflict requires that we terminate an existing contract; or </P>
                <P>• It is in the best interest of the Federal Government to contract with the offeror or contractor even though the conflict of interest exists. </P>
                <P>We discussed an offeror's or contractor's method of mitigating conflicts of interest will be evaluated on a case by case basis. We provided examples of methods an offeror or contractor may use to mitigate organizational conflicts of interest. The examples are not an all-inclusive list of possible methods of mitigation nor are we obligated to approve a mitigation method that uses one of the provided examples. Possible methods of mitigation include: </P>
                <P>• Divestiture, or reduction in the amount, of the financial relationship the organization has in another organization to a level acceptable to us and appropriate for the situation. </P>
                <P>• If shared responsibilities create the conflict, a plan, subject to our approval, to separate lines of business and management or critical staff from work on the Medicaid integrity audit program contract. </P>
                <P>• If the conflict exists because of the amount of financial dependence upon the Federal Government, negotiating a phasing out of other contracts or grants that continue in effect at the start of the Medicaid integrity audit program contract. </P>
                <P>• If the conflict exists because of the financial relationships of individuals within the organization, divestiture of the relationships by the individual involved. </P>
                <P>• If the conflict exists because of an individual's indirect interest, divestiture of the interest to levels acceptable to us or removal of the individual from the work under the Medicaid integrity audit program contract. </P>
                <P>By providing a process for the identification, evaluation, and resolution of conflicts of interest, we not only protect the government's interests but help to ensure that the contractors do not hinder competition in their service areas by misusing their position as a Medicaid integrity audit program contractor. </P>
                <P>We did not receive public comments on our proposed provision. Therefore, we adopt the provisions as proposed. </P>
                <HD SOURCE="HD1">III. Provisions of the Final Regulations </HD>
                <P>The comments received required no substantive revisions to the proposed rule. The comments did, however, ask specific questions or asked for clarification on the CMS Medicaid Integrity Audit Program processes. We provided responses to the questions and provided clarification to other comments. In addition, we inserted, under the preamble, “Section C. Medicaid Integrity Audit Program Contract Overview” in an effort to provide additional clarification to the comments. In this final rule we are adopting all of the provisions as set forth in the November 23, 2007 proposed rule with the exception of several minor editorial changes which that did not result in any policy changes. </P>
                <HD SOURCE="HD1">IV. Regulatory Impact Statement </HD>
                <P>We have examined the impact of this rule as required by Executive Order 12866 (September 1993, Regulatory Planning and Review), the Regulatory Flexibility Act (RFA) (September 19, 1980, Pub. L. 96-354), section 1102(b) of the Social Security Act, the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4), and Executive Order 13132. </P>
                <P>Executive Order 12866 directs agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). A regulatory impact analysis (RIA) must be prepared for major rules with economically significant effects ($100 million or more in any 1 year). This rule will not reach the economic threshold and thus is not considered a major rule. </P>
                <P>The RFA requires agencies to analyze options for regulatory relief of small businesses. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small governmental jurisdictions. Most hospitals and most other providers and suppliers are small entities, either by nonprofit status or by having revenues of $6.5 million to $31.5 million in any 1 year. Individuals and States are not included in the definition of a small entity. We are not preparing an analysis for the RFA because we certify that this rule will not have a significant economic impact on a substantial number of small entities. </P>
                <P>In addition, section 1102(b) of the Act requires us to prepare a regulatory impact analysis if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 603 of the RFA. For purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside of a Core-Based Statistical Area and has fewer than 100 beds. We are not preparing an analysis for section 1102(b) of the Act because we certify that this rule will not have a significant impact on the operations of a substantial number of small rural hospitals. </P>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995 also requires that agencies assess anticipated costs and benefits before issuing any rule whose mandates require spending in any 1 year of $100 million in 1995 dollars, updated annually for inflation. That threshold level is currently approximately $120 million. This final rule will not exceed this established threshold level. This rule will not have a significant impact on State, local, or tribal governments or on the private sector. </P>
                <P>Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a final rule (and subsequent final rule) that imposes substantial direct requirement costs on State and local governments, preempts State law, or otherwise has Federalism implications. Since this regulation will not impose any costs on State or local governments, the requirements of E.O. 13132 are not applicable. </P>
                <P>In accordance with the provisions of Executive Order 12866, this regulation was reviewed by the Office of Management and Budget. </P>
                <HD SOURCE="HD1">V. Collection of Information Requirements </HD>
                <P>
                    Under the Paperwork Reduction Act of 1995, we are required to provide 30-day notice in the 
                    <E T="04">Federal Register</E>
                     and solicit public comment before a collection of information requirement is submitted to the Office of Management and Budget (OMB) for review and approval. In order to fairly evaluate whether an information collection should be approved by OMB, section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995 requires that we solicit comment on the following issues: 
                </P>
                <P>• The need for the information collection and its usefulness in carrying out the proper functions of our agency. </P>
                <P>• The accuracy of our estimate of the information collection burden. </P>
                <P>• The quality, utility, and clarity of the information to be collected. </P>
                <P>
                    • Recommendations to minimize the information collection burden on the 
                    <PRTPAGE P="55771"/>
                    affected public, including automated collection techniques. 
                </P>
                <P>Therefore, we are soliciting public comment on each of these issues for the following sections of this document that contain information collection requirements: </P>
                <HD SOURCE="HD3">Section 455.230 Eligibility Requirements </HD>
                <P>Section 455.230(c) requires that each entity that has entered into a contract with CMS to perform the activities described at 455.232, maintain an appropriate written code of conduct and compliance policies that include, without limitation, an enforced policy on employee conflicts of interest. </P>
                <P>The burden associated with this requirement is the time and effort put forth by the entity to prepare and maintain such policies. While there is burden associated with this requirement, we believe that the burden is exempt from the PRA in accordance with 5 CFR 1320.3(b)(2) because the time, effort, and financial resources necessary to comply with these requirements would be incurred by persons in the normal course of their activities. </P>
                <P>If you comment on these information collection and recordkeeping requirements, please mail copies directly to the following: </P>
                <FP SOURCE="FP-1">Centers for Medicare &amp; Medicaid Services, Office of Strategic Operations and Regulatory Affairs, Regulations Development and Issuances Group, Attn: Melissa Musotto (CMS-2271-F), Room C5-14-03, 7500 Security Boulevard, Baltimore, MD 21244-1850; and </FP>
                <FP SOURCE="FP-1">
                    Office of Information and Regulatory Affairs, Office of Management and Budget, Room 10235, New Executive Office Building, Washington, DC 20503, Attn: OIRA Desk Officer for CMS, (CMS-2271-F), 
                    <E T="03">carolyn_lovett@omb.eop.gov</E>
                    . Fax (202) 395-6974. 
                </FP>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in Part 455 </HD>
                    <P>Fraud, Grant programs-health, Health facilities, Health professions, Investigations, Medicaid, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="42" PART="455">
                    <AMDPAR>For the reasons set forth in the preamble, the Centers for Medicare &amp; Medicaid Services amends 42 CFR Chapter IV as set forth below: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 455—PROGRAM INTEGRITY; MEDICAID </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 455 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>Sec. 1102 of the Social Security Act (42 U.S.C. 1302). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="455">
                    <AMDPAR>2. Section 455.200 is revised to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 455.200 </SECTNO>
                        <SUBJECT>Basis and scope. </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Statutory basis</E>
                            . This subpart implements section 1936 of the Social Security Act that establishes the Medicaid Integrity Program, under which the Secretary will promote the integrity of the program by entering into contracts with eligible entities to carry out the activities under this subpart C. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Scope</E>
                            . This subpart provides for the limitation on a contractor's liability to carry out a contract under the Medicaid Integrity Program and to carry out the Medicaid integrity audit program functions. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="455">
                    <AMDPAR>3. New §§ 455.230, 455.232, 455.234, 455.236, 455.238 and 455.240 are added to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 455.230 </SECTNO>
                        <SUBJECT>Eligibility Requirements. </SUBJECT>
                        <P>CMS may enter into a contract with an entity to perform the activities described at § 455.232, if it meets the following conditions: </P>
                        <P>(a) The entity has demonstrated capability to carry out the activities described below. </P>
                        <P>(b) In carrying out such activities, the entity agrees to cooperate with the Inspector General of the Department of Health and Human Services, the Attorney General, and other law enforcement agencies, as appropriate, in the investigation and deterrence of fraud and abuse in relation to Title XIX of the Social Security Act and in other cases arising out of such activities. </P>
                        <P>(c) Maintains an appropriate written code of conduct and compliance policies that include, without limitation, an enforced policy on employee conflicts of interest. </P>
                        <P>(d) The entity complies with such conflict of interest standards as are generally applicable to Federal acquisition and procurement. </P>
                        <P>(e) The entity meets such other requirements the Secretary may impose. </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 455.232 </SECTNO>
                        <SUBJECT>Medicaid Integrity Audit Program Contractor functions. </SUBJECT>
                        <P>The contract between CMS and a Medicaid integrity audit program contractor specifies the functions the contractor will perform. The contract may include any or all of the following functions: </P>
                        <P>(a) Review of the actions of individuals or entities furnishing items or services (whether on a fee-for-service, risk, or other basis) for which payment may be made under a State Plan approved under title XIX of the Act (or under any waiver of such plan approved under section 1115 of the Act) to determine whether fraud, waste, or abuse has occurred, is likely to occur, or whether such actions have the potential for resulting in an expenditure of funds under title XIX in a manner which is not intended under the provisions of title XIX. </P>
                        <P>(b) Auditing of claims for payment for items or services furnished, or administrative services rendered, under a State Plan under title XIX to ensure proper payments were made. This includes: cost reports, consulting contracts, and risk contracts under section 1903(m) of the Act. </P>
                        <P>(c) Identifying if overpayments have been made to individuals or entities receiving Federal funds under title XIX. </P>
                        <P>(d) Educating providers of service, managed care entities, beneficiaries, and other individuals with respect to payment integrity and quality of care. </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 455.234 </SECTNO>
                        <SUBJECT>Awarding of a Contract. </SUBJECT>
                        <P>(a) CMS awards and administers Medicaid integrity audit program contracts in accordance with acquisition regulations set forth at 48 CFR chapters 1 and 3, this subpart, and all other applicable laws and regulations. These competitive procedures and requirements for awarding Medicaid integrity audit program contracts are to be used as follows: </P>
                        <P>(1) When entering into new contracts under this section. </P>
                        <P>(2) At any other time considered appropriate by the Secretary. </P>
                        <P>(b) An entity is eligible to be awarded a Medicaid integrity audit program contract only if meets the eligibility requirements established in § 455.202, 48 CFR chapter 3, and all other applicable laws and requirements. </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 455.236 </SECTNO>
                        <SUBJECT>Renewal of a Contract. </SUBJECT>
                        <P>(a) CMS specifies the initial contract term in the Medicaid integrity audit program contract. CMS may, but is not required to, renew a Medicaid integrity audit program contract without regard to any provision of law requiring competition if the contractor has met or exceeded the performance requirements established in the current contract. </P>
                        <P>(b) CMS may renew a Medicaid integrity audit program contract without competition if all of the following conditions are met: </P>
                        <P>(1) The Medicaid integrity audit program contractor continues to meet the requirements established in this subpart. </P>
                        <P>(2) The Medicaid integrity audit program contractor meets or exceeds the performance requirements established in its current contract. </P>
                        <P>(3) It is in the best interest of the government. </P>
                        <P>
                            (c) If CMS does not renew a contract, the contract will end in accordance with 
                            <PRTPAGE P="55772"/>
                            its terms. The contractor will not have a right to a hearing or judicial review regarding CMS's renewal or non-renewal decision. 
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 455.238 </SECTNO>
                        <SUBJECT>Conflict of Interest. </SUBJECT>
                        <P>(a) Offerors for Medicaid integrity audit program contracts, and Medicaid integrity audit program contractors, are subject to the following requirements: </P>
                        <P>(1) The conflict of interest standards and requirements of the Federal Acquisition Regulation organizational conflict of interest guidance, found under 48 CFR subpart 9.5. </P>
                        <P>(2) The standards and requirements that are contained in each individual contract awarded to perform activities described under section 1936 of the Act. </P>
                        <P>(b) Post-award conflicts of interest: CMS considers that a post-award conflict of interest has developed if, during the term of the contract, one of the following occurs: </P>
                        <P>(1) The contractor or any of its employees, agents, or subcontractors received, solicited, or arranged to receive any fee, compensation, gift (defined at 5 CFR 2635.203(b)), payment of expenses, offer of employment, or any other thing of value from any entity that is reviewed, audited, investigated, or contacted during the normal course of performing activities under the Medicaid integrity audit program contract. </P>
                        <P>(2) CMS determines that the contractor's activities are creating a conflict of interest. </P>
                        <P>(c) If CMS determines that a conflict of interest exists during the term of the contract, among other actions, CMS may: </P>
                        <P>(1) Not renew the contract for an additional term. </P>
                        <P>(2) Modify the contract. </P>
                        <P>(3) Terminate the contract. </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 435.240 </SECTNO>
                        <SUBJECT>Conflict of Interest Resolution. </SUBJECT>
                        <P>(a) Review Board: CMS may establish a Conflicts of Interest Review Board to assist in resolving organizational conflicts of interest. </P>
                        <P>(b) Resolution: Resolution of an organizational conflict of interest is a determination by the contracting officer that: </P>
                        <P>(1) The conflict is mitigated. </P>
                        <P>(2) The conflict precludes award of a contract to the offeror. </P>
                        <P>(3) The conflict requires that CMS modify an existing contract. </P>
                        <P>(4) The conflict requires that CMS terminate an existing contract. </P>
                        <P>(5) It is in the best interest of the government to contract with the offeror or contractor even though the conflict of interest exists and a request for waiver is approved in accordance with 48 CFR 9.503. </P>
                    </SECTION>
                </REGTEXT>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Program No. 93.778, Medical Assistance Program)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 18, 2008. </DATED>
                    <NAME>Kerry Weems, </NAME>
                    <TITLE>Acting Administrator, Centers for Medicare &amp; Medicaid Services. </TITLE>
                    <DATED>Approved: July 29, 2008. </DATED>
                    <NAME>Michael O. Leavitt,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22693 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Office of the Secretary </SUBAGY>
                <CFR>45 CFR Part 5b </CFR>
                <DEPDOC>[CMS-0029-F] </DEPDOC>
                <RIN>RIN 0938-A069 </RIN>
                <SUBJECT>Exemption of Certain Systems of Records Under the Privacy Act </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This final rule exempts four systems of records (SORs) from subsections (c)(3), (d)(1) through (d)(4), (e)(4)(G) and (H), and (f) of the Privacy Act pursuant to 5 U.S.C. 552a(k)(2): The Automated Survey Processing Environment (ASPEN) Complaint/ Incidents Tracking System (ACTS), HHS/CMS, System No. 09-70-0565; the Health Insurance Portability and Accountability Act (HIPAA) Information Tracking System (HITS), HHS/CMS, System No. 09-70-0544; the Organ Procurement Organizations System (OPOS), HHS/CMS, System No. 09-70-0575; and the Fraud Investigation Database (FID), HHS/CMS, System No. 09-70-0527. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         These regulations are effective on October 27, 2008. 
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Walter Stone, (410) 786-5357. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background </HD>
                <P>The four systems of records (SORs) that are the subject of this final rule and the May 25, 2007 proposed rule are as follows: </P>
                <HD SOURCE="HD2">A. The Automated Survey Processing Environment Complaints/Incidents Tracking System (ACTS), HHS/CMS, System No. 09-70-0565 </HD>
                <P>
                    In the August 22, 2003 
                    <E T="04">Federal Register</E>
                     (68 FR 50795), we published a notice announcing a new SOR titled Automated Survey Processing Environment (ASPEN) Complaint/Incidents Tracking System (ACTS), HHS/CMS, System No. 09-70-0565. 
                </P>
                <P>
                    In the May 23, 2006 
                    <E T="04">Federal Register</E>
                     (71 FR 29643) we published a notice that modified the ACTS SOR. This notice included all modifications and the full text of this system of records. ACTS is a Windows-based program whose primary purpose is to track and process complaints and incidents reported against health care facilities regulated by CMS and State agencies. These facilities include Clinical Laboratory Improvement Amendment (CLIA)-certified laboratories, skilled nursing facilities (SNFs), nursing facilities, hospitals, home health agencies (HHAs), end stage renal disease (ESRD) facilities, hospices, rural health clinics (RHCs), comprehensive outpatient rehabilitation facilities (CORFs), outpatient physical therapy services, community mental health centers (CMHCs), ambulatory surgical centers (ASCs), suppliers of portable x-ray services, and intermediate care facilities for persons with mental retardation (ICF/MRs). ACTS contains identifiable information on individuals, who are complainants, residents, patients, clients, contacts or witnesses. It also may include alleged perpetrators, survey team members, laboratory directors, laboratory owners, and employees and directors of the health care facilities noted previously. ACTS is designed to manage all operations associated with complaint and incident tracking and processing, from initial intake and investigation through the final disposition. 
                </P>
                <HD SOURCE="HD2">B. The Health Insurance Portability and Accountability Act (HIPAA) Information Tracking System (HITS), HHS/CMS, System No. 09-70-0544. </HD>
                <P>
                    In the July 6, 2005 
                    <E T="04">Federal Register</E>
                     (70 FR 38944), we published a notice announcing a new SOR titled Health Insurance Portability and Accountability Act (HIPAA) Information Tracking System (HITS), HHS/CMS, System No. 09-70-0544 
                </P>
                <P>
                    In general, HITS consists of an electronic repository of information, documents, and supplementary paper document files resulting from investigations of alleged violations of the transactions and code sets, security, and unique identifier provisions of HIPAA. HITS' purpose is to support investigations of complainants, determinations as to whether there were violations as charged in the original complaint, referral of violations to law enforcement entities as necessary, and maintenance and retrieval of records that contain the results of the complaint investigations. The system of records 
                    <PRTPAGE P="55773"/>
                    covers individuals who have submitted complaints alleging violations of the provisions of HIPAA. Investigative files maintained in HITS are received either as electronic documents or as paper records that are compiled for law enforcement purposes. 
                </P>
                <HD SOURCE="HD2">C. The Organ Procurement Organizations System (OPOS), HHS/CMS, System No. 09-70-0575 </HD>
                <P>
                    In the May 22, 2006 
                    <E T="04">Federal Register</E>
                     (71 FR 29336), we published a notice announcing a new SOR titled Organ Procurement Organizations System (OPOS), HHS/CMS, System No. 09-70-0575. OPOS is a Windows based program whose purpose is to track and process complaints and incidents reported against Organ Procurement Organizations. Section 701 of the Organ Procurement Organization System Certification Act of 2000 (Pub. L. 106-505) gave the Department the authority to collect and maintain individually identifiable information pertaining to allegations filed by a complainant, beneficiary, or provider of services against Organ Procurement Organizations. This information includes information gathered during all aspects of an investigation, including initial complaints, findings, results, disposition, and relevant correspondence. 
                </P>
                <HD SOURCE="HD2">D. The Fraud Investigation Database (FID), HHS/CMS, System No. 09-70-0527 </HD>
                <P>
                    In the October 28, 2002 
                    <E T="04">Federal Register</E>
                     (70 FR 65795), we published a notice that modified, among other things, the name of a SOR entitled “CMS Utilization Review Investigatory Files, System No. 09-70-0527” to “CMS Fraud Investigation Database (FID).” The notice included the full text of the FID system of records. The FID system of records contains the name, work address, work phone number, social security number, Unique Provider Identification Number (UPIN), and other identifying demographics of individuals alleged to have violated provisions of the Social Security Act (the Act) related to Medicare, Medicaid, HMO/Managed Care, and the Children's Health Insurance Program. The FID system of records also contains the contact information and other identifying demographics of individuals alleged to have violated other criminal or civil statutes connected with the Act and the Act's programs. Here, individuals are persons alleged to have abused the Act's programs. (For example, an individual could be a person alleged to have rendered unnecessary services to Medicare beneficiaries or Medicaid recipients, over-used services, or engaged in improper billing.) They are persons whose activities have provided a substantial basis for criminal or civil prosecution, or who are identified as defendants in criminal prosecution cases. 
                </P>
                <HD SOURCE="HD1">II. Provisions of the Proposed Rule </HD>
                <P>
                    In the May 25, 2007 
                    <E T="04">Federal Register</E>
                     (72 FR 29289) we published a proposed rule that would exempt the ACTS, HITS, OPOS, and FID systems of records from subsection (c)(3), (d)(1) through (d)(4), (e)(4)(G) and (H), and (f) of the Privacy Act pursuant to 5 U.S.C. 552a(k)(2). These exemptions would apply only to the extent that information in a record is subject to exemption pursuant to 5 U.S.C. 552a(k)(2). We proposed that the ACTS, HITS, OPOS, and FID systems of records would be exempted from the following subsections for the reasons set forth below: 
                </P>
                <P>• Subsection (c)(3). Release of an accounting of disclosures to an individual who is the subject of an investigation could reveal the nature and scope of the investigation and could result in the altering or destruction of evidence, improper influencing of witnesses, and other evasive actions that could impede or compromise the investigation. </P>
                <P>• Subsection (d)(1). Release of investigative records to an individual who is the subject of an investigation could interfere with pending or prospective law enforcement proceedings, constitute an unwarranted invasion of the personal privacy of third parties, reveal the identity of confidential sources, or reveal sensitive investigative techniques and procedures. </P>
                <P>• Subsections (d)(2) through (d)(4). Amendment or correction of investigative records could interfere with pending or prospective law enforcement proceedings, or could impose an impossible administrative and investigative burden by requiring us to continuously retrograde our investigations in an attempt to resolve questions of accuracy, relevance, timeliness, and completeness. </P>
                <P>• Subsection (e)(4)(G) and (H). Notifying an individual who is the subject of an investigation or a witness that a system of records contains information about him or her could reveal the nature and scope of the investigation and could result in the altering or destruction of evidence, improper influencing of witnesses, and other evasive actions that could impede or compromise the investigation. </P>
                <P>• Subsection (f). Establishing procedures for notification, inspection or amendment of records, or appeals of denials of access to records would interfere with pending or prospective law enforcement proceedings, constitute an unwarranted invasion of the personal privacy of third parties, reveal the identity of confidential sources, or reveal sensitive investigative techniques. Furthermore, these actions could impose an impossible administrative and investigative burden by requiring us to continuously retrograde our investigations in an attempt to resolve questions of accuracy, relevance, timeliness, and completeness. </P>
                <P>Accordingly, we proposed to amend 45 CFR 5b.11(b)(2)(ii) of the Privacy Act regulations by adding the following: </P>
                <P>• A new paragraph (H) that exempts investigative materials compiled for law enforcement purposes from ACTS. </P>
                <P>• A new paragraph (I) that exempts investigative materials compiled for law enforcement purposes from HITS. </P>
                <P>• A new paragraph (J) that exempts investigative materials compiled for law enforcement purposes from OPOS. </P>
                <P>• A new paragraph (K) that exempts investigative materials compiled for law enforcement purposes from FID. </P>
                <HD SOURCE="HD1">III. Analysis of and Responses to Public Comments </HD>
                <P>We solicited and received two timely public comments on the May 25, 2007 proposed rule. The following is a summary of the comments and our responses. </P>
                <P>
                    <E T="03">Comment:</E>
                     One commenter believed that 45 CFR 5b.11(d) seems to allow the Department of Health and Human Services to disclose identities of sources who furnished information under an express promise of confidentiality. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We do not disclose information that would reveal the identities of sources who furnish information under an express promise of confidentiality because the promise of confidentiality made to a witness is an agreement with that individual, and such disclosure would be both a violation of that agreement and counterproductive to law enforcement efforts, as it would discourage individuals from coming forward to supply information about alleged misconduct. 45 CFR 5b.11(b) gives the responsible Department official discretion to grant notification of access to a record in a system of records which is exempt under 45 CFR 5b.11(b), unless disclosure to the general public is otherwise prohibited by law. The department does not intend to exercise its discretion to disclose identifying 
                    <PRTPAGE P="55774"/>
                    information about sources who furnish information under an express promise of confidentiality. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     Commenters requested that the exemptions be narrowed or clarified by defining the terms “investigative materials” and “law enforcement purposes,” including differentiating among kinds of records within each system that constitute “investigatory materials,” as well as describing agency uses that are not consistent with “law enforcement purposes.” A commenter suggested that CMS implement regulatory definitions, criteria, guidelines or other means to effectuate a confidentiality promise to an informant and to recognize whether or not one has been effectuated for purposes of compliance with subsection (k)(2) of the Privacy Act. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We believe that with respect to clarifying what constitutes a confidentiality promise, we continue to rely upon the following language in subsection (k)(2) of the Privacy Act (5 U.S.C 552a), which permits exemptions from certain subsections of the Privacy Act: 
                </P>
                <EXTRACT>
                    <P>[I]nvestigatory material compiled for law enforcement purposes, other than material within the scope of subsection (j)(2) of this section [the Privacy Act]: Provided, however, That if any individual is denied any right, privilege, or benefit that he would otherwise be entitled by Federal law, or for which he would otherwise be eligible, as a result of the maintenance of such material, such material shall be provided to such individual, except to the extent that the disclosure of such material would reveal the identity of a source who furnished information to the Government under an express promise that the identity of the source would be held in confidence, or, prior to the effective date of this section, [September 27, 1975] under an implied promise that the identity of the source would be held in confidence;</P>
                </EXTRACT>
                  
                <FP>The (k)(2) exemption covers: (1) Material compiled for criminal investigative law enforcement purposes by an entity that does not have as its principal function the enforcement of criminal law and (2) investigative material compiled for law enforcement purposes that does not fall into the scope of the exemption under 5 U.S.C. 552(j)(2). The material must be investigative and compiled for some “law enforcement” purpose, such as a civil investigation, or a criminal investigation by an agency that does not perform as its principal function the enforcement of criminal law. </FP>
                <P>Further, since the information in the SORs at issue was collected on or after September 27, 1975, we believe that, with respect to investigative material that would reveal the identity of a confidential source, only express promises to a source that his or her identity would not be revealed will be implicated here. An example of an express promise could occur when a source expressly requests that his or her identity not be revealed as a condition of furnishing the information, and CMS agrees to that condition and documents that promise in writing. </P>
                <P>The four SORs at issue were established after September 27, 1975, the effective date of the Privacy Act, as follows: </P>
                <P>• The CMS Fraud Investigation Database (FID) was published under its previous name, “HCFA Utilization Review Investigatory Files,” on December 29, 1988 (53 FR 52792) and republished under its current name on October 28, 2002 (67 FR 65795 ). </P>
                <P>• The Automated Survey Processing Environment (ASPEN). Complaints/Incidents Tracking System (ACTS) was first established on August 22, 2003 (68 FR 50795). </P>
                <P>• The Health Insurance Portability and Accountability Act(HIPAA) Information Tracking System (HITS) was first established on July 6, 2005 (70 FR 38944). </P>
                <P>• The Organ Procurement Organizations System (OPOS) was first established on May 22, 2006 (71 FR 29336). </P>
                <P>
                    Further information about this exemption can be found in the Office of Management and Budget's Privacy Act Guidelines, (see the July 9, 1975 
                    <E T="04">Federal Register</E>
                     (40 FR 28972 through 28973)). 
                </P>
                <HD SOURCE="HD1">IV. Provisions of the Final Rule </HD>
                <P>After review of the public comments, we are finalizing the provisions of the proposed rule with minor technical changes. We are revising the paragraphs in § 5b.11(b)(2)(ii) so that the SORs are listed in chronological order by the date established. </P>
                <HD SOURCE="HD1">V. Collection of Information Requirements </HD>
                <P>This final rule does not impose information collection and recordkeeping requirements. Consequently, it need not be reviewed by the Office of Management and Budget under the authority of the Paperwork Reduction Act of 1995 (44 U.S.C. 35). </P>
                <HD SOURCE="HD1">VI. Regulatory Impact Statement </HD>
                <P>We have examined the impact of this rule as required by Executive Order 12866 (September 1993, Regulatory Planning and Review), the Regulatory Flexibility Act (RFA) (September 19, 1980, Pub. L. 96-354), section 1102(b) of the Social Security Act (the Act), the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4), and Executive Order 13132. </P>
                <P>Executive Order 12866 directs agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). A regulatory impact analysis (RIA) must be prepared for regulating actions with economically significant effects ($100 million or more in any one year or other substantial adverse economic effects) known as “major rules”. This rule does not meet the “major rule” criteria therefore we are not preparing an RIA. </P>
                <P>The RFA requires agencies to analyze options for regulatory relief of small businesses. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small governmental jurisdictions. Most hospitals and most other providers and suppliers are small entities, either by nonprofit status or by having revenues of $6 million to $29 million in any one year. Individuals and States are not included in the definition of a small entity. We are not preparing an analysis for the RFA because we have determined that this rule will not have a significant economic impact on a substantial number of small entities. </P>
                <P>In addition, section 1102(b) of the Act requires us to prepare a regulatory impact analysis if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 604 of the RFA. For purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside of a Metropolitan Statistical Area and has fewer than 100 beds. We are not preparing an analysis for section 1102(b) of the Act because we have determined that this rule will not have a significant impact on the operations of a substantial number of small rural hospitals. </P>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995 also requires that agencies assess anticipated costs and benefits before issuing any rule whose mandates require spending in any one year of $100 million in 1995 dollars, updated annually for inflation. That threshold level is currently approximately $120 million. This final rule will have no consequential effect on State, local, or tribal governments or on the private sector. </P>
                <P>
                    Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a proposed rule (and subsequent final 
                    <PRTPAGE P="55775"/>
                    rule) that imposes substantial direct requirement costs on State and local governments, preempts State law, or otherwise has Federalism implications. Since this regulation does not impose any costs on State or local governments, the requirements of Executive Order 13132 are not applicable. 
                </P>
                <P>In accordance with the provisions of Executive Order 12866, this regulation was reviewed by the Office of Management and Budget. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects for 45 CFR Part 5b Privacy.</HD>
                </LSTSUB>
                <REGTEXT TITLE="45" PART="5b">
                    <AMDPAR>For the reasons set forth in the preamble, the Department of Health and Human Services amends 45 CFR part 5b as set forth below: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 5b—PRIVACY ACT REGULATIONS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 5b continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>5 U.S.C. 301, 5 U.S.C. 552a. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="45" PART="5b">
                    <AMDPAR>2. Section 5b.11 is revised by adding paragraphs  (b)(2)(ii)(H), (I), (J), and (K) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 5b.11 </SECTNO>
                        <SUBJECT>Exempt Systems </SUBJECT>
                        <STARS/>
                        <P>(b) * * * </P>
                        <P>(2) * * * </P>
                        <P>(ii) * * * </P>
                        <P>(H) Investigative materials compiled for law enforcement purposes from the CMS Fraud Investigation Database (FID), HHS/CMS. </P>
                        <P>(I) Investigative materials compiled for law enforcement purposes from the Automated Survey Processing Environment (ASPEN) Complaints/ Incidents Tracking System (ACTS), HHS/CMS. </P>
                        <P>(J) Investigative materials compiled for law enforcement purposes from the Health Insurance Portability and Accountability Act (HIPAA) Information Tracking System (HITS), HHS/CMS. </P>
                        <P>(K) Investigative materials compiled for law enforcement purposes from the Organ Procurement Organizations System (OPOS), HHS/CMS. </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: November 20, 2007. </DATED>
                    <NAME>Kerry Weems, </NAME>
                    <TITLE>Acting Administrator, Centers for Medicare &amp; Medicaid Services. </TITLE>
                    <DATED>Approved: June 13, 2008. </DATED>
                    <NAME>Michael O. Leavitt, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
                <EDNOTE>
                    <HD SOURCE="HED">Editorial Note:</HD>
                    <P>This document was received at the Office of the Federal Register on September 16, 2008.</P>
                </EDNOTE>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-21909 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P   </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Part 101 </CFR>
                <DEPDOC>[WT Docket No. 00-19; RM-9418; FCC 02-218] </DEPDOC>
                <SUBJECT>Streamline Processing of Microwave Applications in the Wireless Telecommunications Services </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Correcting amendment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In this document, the Federal Communications Commission corrects an inadvertent error that occurred when the Commission adopted final rules pertaining to Streamline Processing of Microwave Applications in the Wireless Telecommunications Services and Telecommunications Industry Association Petition for Rulemaking. These rules were published in the 
                        <E T="04">Federal Register</E>
                         on Friday, January 31, 2003 (68 FR 4953). Specifically, the error occurred in a table to the rules concerning directional antennas and compliance with antenna standards. As a result of this correction, the table will be amended as intended by the Commission. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective September 26, 2008. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>John Schauble at 202-418-0797. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This is a correction to a summary of the Commission's Report and Order in WT Docket No. 00-19, FCC 02-218, adopted on July 18, 2002 and released on July 31, 2002. The Report and Order streamlined, clarified and updated part 101 rules. These actions were to provide increased flexibility to licensees, ensure greater and more efficient use of spectrum bands regulated under part 101, and ensure that our Rules are consistent with international agreements. </P>
                <HD SOURCE="HD1">Need for Correction </HD>
                <P>
                    As published, the final rules contain an error in § 101.115 Directional Antennas, Antenna Standards Table. The Commission did not request that the listed entry to the Antenna Standards Table for the frequency of 10,550 to 10,680 
                    <E T="51">5,7</E>
                     MHz be omitted. This correction removes the listing that should have been omitted. The entry for 10,550 to 10,680
                    <E T="51">7</E>
                    , which was adopted in that proceeding, will remain. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 101 </HD>
                    <P>Communications equipment, Marine safety, Radio, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="47" PART="101">
                    <AMDPAR>Accordingly, 47 CFR part 101 is amended by making the following correcting amendments: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 101—FIXED MICROWAVE SERVICES </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 101 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>47 U.S.C. 154, 303 unless otherwise noted. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="101">
                    <SECTION>
                        <SECTNO>§ 101.115</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>
                        2. Section 101.115 is amended by removing the entry “10,550 to 10,680 
                        <SU>5,7</SU>
                        ” for both Category A and B in the table following paragraph (b)(2).
                    </AMDPAR>
                </REGTEXT>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene H. Dortch,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22721 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>73</VOL>
    <NO>188</NO>
    <DATE>Friday, September 26, 2008</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="55776"/>
                <AGENCY TYPE="F">OFFICE OF MANAGEMENT AND BUDGET</AGENCY>
                <CFR>2 CFR Parts 1 and 182</CFR>
                <SUBJECT>Guidance for Drug-Free Workplace Requirements (Financial Assistance)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Management and Budget.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed guidance.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of Management and Budget (OMB) is proposing guidance on drug-free workplace requirements for financial assistance. The guidance conforms with the common rule that 31 Federal agencies published on November 26, 2003 and therefore makes no substantive change to Federal policies and procedures in this area. The agencies issued that common rule after resolving public comments received in response to a Notice of Proposed Rulemaking.</P>
                    <P>OMB is proposing to issue this guidance as an administrative simplification that will streamline the policy framework for drug-free workplace requirements in two ways. First, the guidance is in a form suitable for Federal agency adoption, which will reduce the volume of Federal regulations on drug-free workplace, make it easier for the affected public to use them, and make it easier and less expensive for the Federal Government to maintain them. Second, the guidance is located in the recently established Title 2 of the Code of Federal Regulations (2 CFR). Locating the OMB guidance in 2 CFR will make it easier to find. It also is the first step toward co-locating in the same CFR title the agencies' regulations that implement the guidance, a further simplification for the public.</P>
                    <P>This notice also proposes a minor change to the previously issued 2 CFR part 1, to conform that part with the guidance published today.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments are due on or before October 27, 2008.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Due to potential delays in OMB's receipt and processing of mail sent through the U.S. Postal Service, we encourage respondents to submit comments electronically to ensure timely receipt. We cannot guarantee that comments mailed will be received before the comment closing date.</P>
                    <P>
                        Comments may be sent to via 
                        <E T="03">http://www.regulations.gov</E>
                        —a Federal E-Government Web site that allows the public to find, review, and submit comments on documents that agencies have published in the 
                        <E T="04">Federal Register</E>
                         and that are open for comment. Simply type “drug-free workplace guidance” (in quotes) in the Comment or Submission search box, click Go, and follow the instructions for submitting comments. Comments received by the date specified above will be included as part of the official record.
                    </P>
                    <P>
                        Comments may be e-mailed to: 
                        <E T="03">mpridgen@omb.eop.gov.</E>
                         Please include “drug-free workplace guidance” in the subject line of your e-mail message. Also, please include the full body of your comments in the text of the electronic message, as well as in an attachment. Please include your name, title, organization, postal address, telephone number, and e-mail address in the text of the message. Comments may also be submitted via facsimile to (202) 395-3952.
                    </P>
                    <P>Comments may be mailed to Marguerite Pridgen, Office of Federal Financial Management, Office of Management and Budget, Room 6025, New Executive Office Building, 725 17th Street, NW., Washington, DC 20503.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Marguerite Pridgen, Office of Federal Financial Management, Office of Management and Budget, telephone (202) 395-7844 (direct) or (202) 395-3993 (main office) and e-mail: 
                        <E T="03">mpridgen@omb.eop.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Background.</E>
                     Congress established drug-free workplace requirements for Federal grant recipients in section 5153 of the Drug-Free Workplace Act of 1988 (Pub. L. 100-690, Title V, Subtitle D, which was enacted November 18, 1988). Section 5156 of the Act (41 U.S.C. 705) requires Governmentwide regulations to implement the requirements.
                </P>
                <P>In the initial implementation of the Act, OMB issued guidance (54 FR 4946, January 31, 1989) in conjunction with agencies' issuance of a common rule (54 FR 4947). Each agency adopted the common rule in a new subpart added to the existing common rule on nonprocurement debarment and suspension. On November 26, 2003 (68 FR 66534), the agencies updated the common rule on drug-free workplace requirements and converted it to plain language. Each agency at that time also relocated the drug-free workplace coverage to its own CFR part and removed it from the subpart in the debarment and suspension common rule.</P>
                <P>
                    OMB and an interagency working group helping to implement the Federal Financial Assistance Management Improvement Act of 1999 (Pub. L. 106-107) subsequently proposed a better way to implement Governmentwide requirements, as an alternative to common rules. The alternative is to publish the full text of the implementation as OMB guidance in a form that each agency can adopt in a short regulation, without repeating the full text in the way that a common rule does. The advantages of the approach are to make a rule easier for the affected public to use and easier and less expensive for the Government to maintain. As the first step toward putting this new approach in place, the common rule on nonprocurement debarment and suspension was converted to OMB guidance. The 
                    <E T="04">Federal Register</E>
                     notices associated with that conversion (70 FR 51863 and 71 FR 66431) provide more details about the advantages of converting from common rules to adoptable OMB guidance.
                </P>
                <P>In conjunction with the shift to adoptable guidance, OMB and the interagency working group also proposed to create a single title in the Code of Federal Regulations (CFR) in which OMB would publish its guidance for grants and agreements and agencies would publish their regulations implementing it. That helps recipients who do business with multiple Federal agencies, by creating one title in which they can find different agencies' regulations that previously were published in many separate CFR titles. On May 11, 2004, OMB established title 2 of the CFR for that purpose [69 FR 26276].</P>
                <P>
                    <E T="03">Purpose of this action.</E>
                     Today's notice proposes OMB guidance for drug-free workplace requirements in a new CFR part—2 CFR part 182—and in a form that agencies may adopt. We also will 
                    <PRTPAGE P="55777"/>
                    maintain the guidance at the OMB Web site (
                    <E T="03">http://www.whitehouse.gov/omb/grants/grants_docs.html</E>
                     ), for the benefit of individuals who would prefer to access it there.
                </P>
                <P>Once we resolve any comments received on the proposed guidance and issue it in final form, each agency will publish a short regulation adopting the guidance in its chapter of 2 CFR. An agency's regulation will give regulatory effect to the OMB guidance on drug-free workplace for its financial assistance awards and recipients. The agency also will remove the full text of the current common rule on drug-free workplace from its CFR title.  </P>
                <P>
                    <E T="03">Structure and content of the guidance.</E>
                     Our intent is to issue OMB guidance that is substantively unchanged from the drug-free workplace common rule that the agencies issued in November 2003. We modified some of the structure and language of the common rule, however, to create a part that reads properly as OMB guidance to agencies rather than an agency regulation.
                </P>
                <P>The most significant structural changes are in sections 182.5 to 182.40, which precede subpart A. The primary purpose of those sections is to instruct Federal agencies on the use of 2 CFR part 182. Sections 182.20 through 182.35, for example, tell agencies that they must issue regulations to implement the drug-free workplace guidance, identify required and optional content for those regulations, and specify where and when the agencies must issue the regulations. Most of these sections have no counterparts in the November 2003 common rule because it was designed to be an agency rule rather than OMB guidance.</P>
                <P>Subparts A through F of 2 CFR part 182 contain the guidance that an agency will adopt to specify its drug-free workplace policies and procedures. There is a minor restructuring in subpart A because the first two sections, 182.100 and 182.105, do not have counterparts in the November 2003 common rule. The intent of those added sections is to be helpful to the public reading the guidance. Subpart A also is the only portion of the guidance where section numbers vary from the common rule (due to the added sections at the beginning of the subpart, sections 182.110 through 182.125 correspond to sections __.100 through __.115 of the common rule). Other minor wording changes throughout subparts A through F are to make the document read properly as OMB guidance.</P>
                <P>
                    <E T="03">Invitation to comment.</E>
                     We are requesting comment on the proposed guidance for 30 days rather than a longer period, because: (1) The agencies published the final common rule in November 2003 after an opportunity for public comment; and (2) we believe that we have made no substantive changes from that common rule. In the future, the process for making any substantive changes to this guidance will include proposing the changes with an opportunity for public comment, in accordance with § 182.40 of the new part 182. In soliciting comments on this proposed guidance, we are not seeking to revisit substantive issues raised by comments and resolved by the agencies during preparation of the November 2003 final rule. However, we invite comments on any unintended changes we have made in the guidance relative to that common rule.
                </P>
                <P>
                    <E T="03">Next steps.</E>
                     We will finalize the guidance after resolving any comments received on the proposed version. At that time, each Federal agency that is a signatory to the drug-free workplace common rule then will issue a brief rule in its chapter of 2 CFR to adopt the OMB guidance and will remove the November 2003 common rule from its own CFR title. We expect to complete the process in calendar year 2009.
                </P>
                <P>
                    <E T="03">Conforming 2 CFR part 1.</E>
                     We also are updating 2 CFR part 1 to add to the table in § 1.215 a citation to the previous location of the drug-free workplace requirements.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>2 CFR Part 1</CFR>
                    <P>Cooperative agreements, Grant programs, Grants administration.</P>
                    <CFR>2 CFR Part 182</CFR>
                    <P>Administrative practice and procedure, Drug abuse, Grant programs, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <NAME>Danny Werfel,</NAME>
                    <TITLE>Deputy Controller.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Authority and Issuance</HD>
                <P>For the reasons set forth above, the Office of Management and Budget amends 2 CFR, subtitle A, as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1—[AMENDED]</HD>
                    <P>1. The authority citation for part 1 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>31 U.S.C. 503; 31 U.S.C. 1111; 41 U.S.C. 405; Reorganization Plan No. 2 of 1970; E.O. 11541, 35 FR 10737, 3 CFR, 1966-1970, p. 939.</P>
                    </AUTH>
                    <P>2. Section 1.215 is revised to read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.215</SECTNO>
                        <SUBJECT>Relationship to previous issuances.</SUBJECT>
                        <P>Although some of the guidance was organized differently within OMB circulars or other documents, much of the guidance in this subtitle existed prior to the establishment of title 2 of the CFR. Specifically:</P>
                        <GPOTABLE COLS="03" OPTS="L2,tp0,i1" CDEF="s100,r100,xs150">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">Guidance in . . .</CHED>
                                <CHED H="1" O="L">On . . .</CHED>
                                <CHED H="1" O="L">Previously was in . . .</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">(a) Chapter I, part 180</ENT>
                                <ENT>Nonprocurement debarment and suspension</ENT>
                                <ENT>OMB guidance that conforms with the government-wide common rule (see 60 FR 33036, June 26, 1995).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(b) Chapter I, part 182</ENT>
                                <ENT>Drug-free workplace requirements</ENT>
                                <ENT>OMB guidance (54 FR 4946, January 31, 1989) and a government-wide common rule (as amended at 68 FR 66534, November 26, 2003).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(c) Chapter II, part 215</ENT>
                                <ENT>Administrative requirements for grants and agreements</ENT>
                                <ENT>OMB Circular A-110.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(d) Chapter II, part 220</ENT>
                                <ENT>Cost principles for educational institutions</ENT>
                                <ENT>OMB Circular A-21.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(e) Chapter II, part 225</ENT>
                                <ENT>Cost principles for State, local, and Indian tribal governments</ENT>
                                <ENT>OMB Circular A-87.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(f) Chapter II, part 230</ENT>
                                <ENT>Cost principles for non-profit organizations</ENT>
                                <ENT>OMB Circular A-122.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(g) [Reserved.]</ENT>
                                <ENT/>
                                <ENT O="."/>
                            </ROW>
                        </GPOTABLE>
                        <PRTPAGE P="55778"/>
                        <HD SOURCE="HD1">Chapter I—[AMENDED]</HD>
                        <P>3. Part 182 is added to Chapter I, to read as follows:</P>
                    </SECTION>
                </PART>
                <PART>
                    <HD SOURCE="HED">PART 182—GOVERNMENTWIDE REQUIREMENTS FOR DRUG-FREE WORKPLACE (FINANCIAL ASSISTANCE)</HD>
                    <CONTENTS>
                        <SECHD>Sec.</SECHD>
                        <SECTNO>182.5</SECTNO>
                        <SUBJECT>What does this part do?</SUBJECT>
                        <SECTNO>182.10</SECTNO>
                        <SUBJECT>How is this part organized?</SUBJECT>
                        <SECTNO>182.15</SECTNO>
                        <SUBJECT>To whom does the guidance apply?</SUBJECT>
                        <SECTNO>182.20</SECTNO>
                        <SUBJECT>What must a Federal agency do to implement the guidance?</SUBJECT>
                        <SECTNO>182.25</SECTNO>
                        <SUBJECT>What must a Federal agency address in its implementation of the guidance?</SUBJECT>
                        <SECTNO>182.30</SECTNO>
                        <SUBJECT>Where does a Federal agency implement the guidance?</SUBJECT>
                        <SECTNO>182.35</SECTNO>
                        <SUBJECT>By when must a Federal agency implement the guidance?</SUBJECT>
                        <SECTNO>182.40</SECTNO>
                        <SUBJECT>How is the guidance maintained?</SUBJECT>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart A—Purpose and Coverage</HD>
                            <SECTNO>182.100</SECTNO>
                            <SUBJECT>How is this part written?</SUBJECT>
                            <SECTNO>182.105</SECTNO>
                            <SUBJECT>Do terms in this part have special meanings?</SUBJECT>
                            <SECTNO>182.110</SECTNO>
                            <SUBJECT>What do subparts A through F of this part do?</SUBJECT>
                            <SECTNO>182.115</SECTNO>
                            <SUBJECT>Does this part apply to me?</SUBJECT>
                            <SECTNO>182.120</SECTNO>
                            <SUBJECT>Are any of my Federal assistance awards exempt from this part?</SUBJECT>
                            <SECTNO>182.125</SECTNO>
                            <SUBJECT>Does this part affect the Federal contracts that I receive?</SUBJECT>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart B—Requirements for Recipients Other Than Individuals</HD>
                            <SECTNO>182.200</SECTNO>
                            <SUBJECT>What must I do to comply with this part?</SUBJECT>
                            <SECTNO>182.205</SECTNO>
                            <SUBJECT>What must I include in my drug-free workplace statement?</SUBJECT>
                            <SECTNO>182.210</SECTNO>
                            <SUBJECT>To whom must I distribute my drug-free workplace statement?</SUBJECT>
                            <SECTNO>182.215</SECTNO>
                            <SUBJECT>What must I include in my drug-free awareness program?</SUBJECT>
                            <SECTNO>182.220</SECTNO>
                            <SUBJECT>By when must I publish my drug-free workplace statement and establish my drug-free awareness program?</SUBJECT>
                            <SECTNO>182.225</SECTNO>
                            <SUBJECT>What actions must I take concerning employees who are convicted of drug violations in the workplace?</SUBJECT>
                            <SECTNO>182.230</SECTNO>
                            <SUBJECT>How and when must I identify workplaces?</SUBJECT>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart C—Requirements for Recipients Who Are Individuals</HD>
                            <SECTNO>182.300</SECTNO>
                            <SUBJECT>What must I do to comply with this part if I am an individual recipient?</SUBJECT>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart D—Responsibilities of Agency Awarding Officials</HD>
                            <SECTNO>182.400</SECTNO>
                            <SUBJECT>What are my responsibilities as an agency awarding official?</SUBJECT>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart E—Violations of this Part and Consequences</HD>
                            <SECTNO>182.500</SECTNO>
                            <SUBJECT>How are violations of this part determined for recipients other than individuals?</SUBJECT>
                            <SECTNO>182.505</SECTNO>
                            <SUBJECT>How are violations of this part determined for recipients who are individuals?</SUBJECT>
                            <SECTNO>182.510</SECTNO>
                            <SUBJECT>What actions will the Federal Government take against a recipient determined to have violated this part?</SUBJECT>
                            <SECTNO>182.515</SECTNO>
                            <SUBJECT>Are there any exceptions to those actions?</SUBJECT>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart F—Definitions</HD>
                            <SECTNO>182.605</SECTNO>
                            <SUBJECT>Award.</SUBJECT>
                            <SECTNO>182.610</SECTNO>
                            <SUBJECT>Controlled substance.</SUBJECT>
                            <SECTNO>182.615</SECTNO>
                            <SUBJECT>Conviction.</SUBJECT>
                            <SECTNO>182.620</SECTNO>
                            <SUBJECT>Cooperative agreement.</SUBJECT>
                            <SECTNO>182.625</SECTNO>
                            <SUBJECT>Criminal drug statute.</SUBJECT>
                            <SECTNO>182.630</SECTNO>
                            <SUBJECT>Debarment.</SUBJECT>
                            <SECTNO>182.635</SECTNO>
                            <SUBJECT>Drug-free workplace.</SUBJECT>
                            <SECTNO>182.640</SECTNO>
                            <SUBJECT>Employee.</SUBJECT>
                            <SECTNO>182.645</SECTNO>
                            <SUBJECT>Federal agency or agency.</SUBJECT>
                            <SECTNO>182.650</SECTNO>
                            <SUBJECT>Grant.</SUBJECT>
                            <SECTNO>182.655</SECTNO>
                            <SUBJECT>Individual.</SUBJECT>
                            <SECTNO>182.660</SECTNO>
                            <SUBJECT>Recipient.</SUBJECT>
                            <SECTNO>182.665</SECTNO>
                            <SUBJECT>State.</SUBJECT>
                            <SECTNO>182.670</SECTNO>
                            <SUBJECT>Suspension.</SUBJECT>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P>
                                    41 U.S.C. 701, 
                                    <E T="03">et seq.</E>
                                      
                                </P>
                            </AUTH>
                        </SUBPART>
                    </CONTENTS>
                    <SECTION>
                        <SECTNO>§ 182.5</SECTNO>
                        <SUBJECT>What does this part do?</SUBJECT>
                        <P>This part provides Office of Management and Budget (OMB) guidance for Federal agencies on the portion of the Drug-Free Workplace Act of 1988 (41 U.S.C. 701-707, as amended) that applies to grants. It also applies the provisions of the Act to cooperative agreements and other financial assistance awards, as a matter of Federal Government policy.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 182.10</SECTNO>
                        <SUBJECT>How is this part organized?</SUBJECT>
                        <P>This part is organized in two segments.</P>
                        <P>(a) Sections 182.5 through 182.40 contain general policy direction for Federal agencies' use of the uniform policies and procedures in subparts A through F of this part.</P>
                        <P>(b)  Subparts A through F of this part contain uniform governmentwide policies and procedures for Federal agency use to specify the—</P>
                        <P>(1) Types of awards that are covered by drug-free workplace requirements;</P>
                        <P>(2) Drug-free workplace requirements with which a recipient must comply;</P>
                        <P>(3) Actions required of an agency awarding official; and</P>
                        <P>(4) Consequences of a violation of drug-free workplace requirements.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 182.15 </SECTNO>
                        <SUBJECT>To whom does the guidance apply?</SUBJECT>
                        <P>This part provides OMB guidance only to Federal agencies. Publication of this guidance in the Code of Federal Regulations does not change its nature—it is guidance and not regulation. Federal agencies' implementation of the guidance governs the rights and responsibilities of other persons affected by the drug-free workplace requirements.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 182.20 </SECTNO>
                        <SUBJECT>What must a Federal agency do to implement the guidance?</SUBJECT>
                        <P>To comply with the requirement in Section 41 U.S.C. 705 for Governmentwide regulations, each Federal agency that awards grants or cooperative agreements or makes other financial assistance awards that are subject to the drug-free workplace requirements in subparts A through F of the guidance must issue a regulation consistent with those subparts.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 182.25 </SECTNO>
                        <SUBJECT>What must a Federal agency address in its implementation of the guidance?</SUBJECT>
                        <P>Each Federal agency's implementing regulation:</P>
                        <P>(a) Must establish drug-free workplace policies and procedures for that agency's awards that are consistent with the guidance in this part. When adopted by a Federal agency, the provisions of the guidance have regulatory effect for that agency's awards.</P>
                        <P>(b) Must address some matters for which the guidance in this part gives the agency discretion. Specifically, the regulation must—</P>
                        <P>(1) State whether the agency:  </P>
                        <P>(i) Has a central point to which a recipient may send the notification of a conviction that is required under § 182.225(a) or § 182.300(b); or</P>
                        <P>(ii) Requires the recipient to send the notification to the awarding official for each agency award, or to his or her official designee.</P>
                        <P>(2) Either:</P>
                        <P>(i) State that the agency head is the official authorized to determine under § 182.500 or § 182.505 that a recipient has violated the drug-free workplace requirements; or</P>
                        <P>(ii) Provide the title of the official designated to make that determination.</P>
                        <P>(c) May also, at the agency's option, identify any specific types of financial assistance awards, in addition to grants and cooperative agreements, to which the Federal agency makes this guidance applicable.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 182.30 </SECTNO>
                        <SUBJECT>Where does a Federal agency implement the guidance?</SUBJECT>
                        <P>Each Federal agency that awards grants or cooperative agreements or makes other financial assistance awards that are subject to the drug-free workplace guidance in this part must issue a regulation implementing the guidance within its chapter in subtitle B of this title of the Code of Federal Regulations.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 182.35 </SECTNO>
                        <SUBJECT>By when must a Federal agency implement the guidance?</SUBJECT>
                        <P>Federal agencies must submit proposed regulations to the OMB for review within nine months of the final issuance of this part and issue final regulations within eighteen months of the guidance.</P>
                    </SECTION>
                    <SECTION>
                        <PRTPAGE P="55779"/>
                        <SECTNO>§ 182.40 </SECTNO>
                        <SUBJECT>How is the guidance maintained?</SUBJECT>
                        <P>
                            The OMB publishes proposed changes to the guidance in the 
                            <E T="04">Federal Register</E>
                             for public comment, considers comments with the help of appropriate interagency working groups, and then issues any changes to the guidance in final form.
                        </P>
                    </SECTION>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart A—Purpose and Coverage</HD>
                        <SECTION>
                            <SECTNO>§ 182.100 </SECTNO>
                            <SUBJECT>How is this part written?</SUBJECT>
                            <P>(a) This part uses a “plain language” format to make it easier for the general public and business community to use and understand. The section headings and text, often in the form of questions and answers, must be read together.</P>
                            <P>(b) Pronouns used within this part, such as “I” and “you,” change from subpart to subpart depending on the audience being addressed.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.105 </SECTNO>
                            <SUBJECT>Do terms in this part have special meanings?</SUBJECT>
                            <P>This part uses terms that have special meanings. Those terms are defined in subpart F of this part.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.110 </SECTNO>
                            <SUBJECT>What do subparts A through F of this part do?</SUBJECT>
                            <P>Subparts A through F of this part specify standard policies and procedures to carry out the Drug-Free Workplace Act of 1988 for financial assistance awards.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.115 </SECTNO>
                            <SUBJECT>Does this part apply to me?</SUBJECT>
                            <P>(a) Portions of this part apply to you if you are either—</P>
                            <P>(1) A recipient of a Federal assistance award (see definitions of award and recipient in §§ 182.605 and 182.660, respectively); or</P>
                            <P>(2) A Federal agency awarding official.</P>
                            <P> (b) The following table shows the subparts that apply to you:</P>
                            <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s90,xs60">
                                <TTITLE> </TTITLE>
                                <BOXHD>
                                    <CHED H="1" O="L">If you are . . .</CHED>
                                    <CHED H="1" O="L">
                                        see 
                                        <LI>subparts . . .</LI>
                                    </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">(1) a recipient who is not an individual</ENT>
                                    <ENT>A, B and E.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(2) a recipient who is an individual</ENT>
                                    <ENT>A, C and E.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(3) a Federal agency awarding official</ENT>
                                    <ENT>A, D and E.</ENT>
                                </ROW>
                            </GPOTABLE>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.120 </SECTNO>
                            <SUBJECT>Are any of my Federal assistance awards exempt from this part?</SUBJECT>
                            <P>This part does not apply to any award to which the agency head, or his or her designee, determines that the application of this part would be inconsistent with the international obligations of the United States or the laws or regulations of a foreign government.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.125 </SECTNO>
                            <SUBJECT>Does this part affect the Federal contracts that I receive?</SUBJECT>
                            <P>This part will affect future contract awards indirectly if you are debarred or suspended for a violation of the requirements of this part, as described in § 182.510(c). However, this part does not apply directly to procurement contracts. The portion of the Drug-Free Workplace Act of 1988 that applies to Federal procurement contracts is carried out through the Federal Acquisition Regulation in chapter 1 of Title 48 of the Code of Federal Regulations (the drug-free workplace coverage currently is in 48 CFR part 23, subpart 23.5).</P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart B—Requirements for Recipients Other Than Individuals</HD>
                        <SECTION>
                            <SECTNO>§ 182.200 </SECTNO>
                            <SUBJECT>What must I do to comply with this part?</SUBJECT>
                            <P>There are two general requirements if you are a recipient other than an individual.</P>
                            <P>(a) First, you must make a good faith effort, on a continuing basis, to maintain a drug-free workplace. You must agree to do so as a condition for receiving any award covered by this part. The specific measures that you must take in this regard are described in more detail is subsequent sections of this subpart. Briefly, those measures are to—</P>
                            <P>(1) Publish a drug-free workplace statement and establish a drug-free awareness program for your employees (see §§ 182.205 through 182.220); and</P>
                            <P>(2) Take actions concerning employees who are convicted of violating drug statutes in the workplace (see § 182.225).</P>
                            <P>(b) Second, you must identify all known workplaces under your Federal awards (see § 182.230).</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.205 </SECTNO>
                            <SUBJECT>What must I include in my drug-free workplace statement?</SUBJECT>
                            <P>You must publish a statement that—</P>
                            <P>(a) Tells your employees that the unlawful manufacture, distribution, dispensing, possession, or use of a controlled substance is prohibited in your workplace;</P>
                            <P>(b) Specifies the actions that you will take against employees for violating that prohibition; and</P>
                            <P>(c) Lets each employee know that, as a condition of employment under any award, he or she:</P>
                            <P>(1) Will abide by the terms of the statement; and</P>
                            <P>(2) Must notify you in writing if he or she is convicted for a violation of a criminal drug statute occurring in the workplace and must do so no more than five calendar days after the conviction.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.210 </SECTNO>
                            <SUBJECT>To whom must I distribute my drug-free workplace statement?</SUBJECT>
                            <P>You must require that a copy of the statement described in § 182.205 be given to each employee who will be engaged in the performance of any Federal award.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.215 </SECTNO>
                            <SUBJECT>What must I include in my drug-free awareness program?</SUBJECT>
                            <P>You must establish an ongoing drug-free awareness program to inform employees about—</P>
                            <P>(a) The dangers of drug abuse in the workplace;</P>
                            <P>(b) Your policy of maintaining a drug-free workplace;</P>
                            <P>(c) Any available drug counseling, rehabilitation, and employee assistance programs; and</P>
                            <P>(d) The penalties that you may impose upon them for drug abuse violations occurring in the workplace.  </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.220</SECTNO>
                            <SUBJECT>By when must I publish my drug-free workplace statement and establish my drug-free awareness program?</SUBJECT>
                            <P>If you are a new recipient that does not already have a policy statement as described in § 182.205 and an ongoing awareness program as described in § 182.215, you must publish the statement and establish the program by the time given in the following table:</P>
                            <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,xs200">
                                <TTITLE> </TTITLE>
                                <BOXHD>
                                    <CHED H="1" O="L">If . . .</CHED>
                                    <CHED H="1" O="L">Then you . . .</CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">(a) the performance period of the award is less than 30 days</ENT>
                                    <ENT>must have the policy statement and program in place as soon as possible, but before the date on which performance is expected to be completed.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(b) the performance period of the award is 30 days or more</ENT>
                                    <ENT>must have the policy statement and program in place within 30 days after award.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(c) you believe there are extraordinary circumstances that will require more than 30 days for you to publish the policy statement and establish the awareness program</ENT>
                                    <ENT>may ask the agency awarding official to give you more time to do so. The amount of additional time, if any, to be given is at the discretion of the awarding official.</ENT>
                                </ROW>
                            </GPOTABLE>
                        </SECTION>
                        <SECTION>
                            <PRTPAGE P="55780"/>
                            <SECTNO>§ 182.225 </SECTNO>
                            <SUBJECT>What actions must I take concerning employees who are convicted of drug violations in the workplace?</SUBJECT>
                            <P>There are two actions you must take if an employee is convicted of a drug violation in the workplace:</P>
                            <P>(a) First, you must notify Federal agencies if an employee who is engaged in the performance of an award informs you about a conviction, as required by § 182.205(c)(2), or you otherwise learn of the conviction. Your notification to the Federal agencies must—</P>
                            <P>(1) Be in writing;</P>
                            <P>(2) Include the employee's position title;</P>
                            <P>(3) Include the identification number(s) of each affected award;</P>
                            <P>(4) Be sent within ten calendar days after you learn of the conviction; and</P>
                            <P>(5) Be sent to every Federal agency on whose award the convicted employee was working. It must be sent to every awarding official or his or her official designee, unless the Federal agency has specified a central point for the receipt of the notices.</P>
                            <P>(b) Second, within 30 calendar days of learning about an employee's conviction, you must either—</P>
                            <P>(1) Take appropriate personnel action against the employee, up to and including termination, consistent with the requirements of the Rehabilitation Act of 1973 (29 U.S.C. 794), as amended; or</P>
                            <P>(2) Require the employee to participate satisfactorily in a drug abuse assistance or rehabilitation program approved for these purposes by a Federal, State or local health, law enforcement, or other appropriate agency.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.230</SECTNO>
                            <SUBJECT>How and when must I identify workplaces?</SUBJECT>
                            <P>(a) You must identify all known workplaces under each agency award. A failure to do so is a violation of your drug-free workplace requirements. You may identify the workplaces—</P>
                            <P>(1) To the agency official that is making the award, either at the time of application or upon award; or</P>
                            <P>(2) In documents that you keep on file in your offices during the performance of the award, in which case you must make the information available for inspection upon request by agency officials or their designated representatives.</P>
                            <P>
                                (b) Your workplace identification for an award must include the actual address of buildings (or parts of buildings) or other sites where work under the award takes place. Categorical descriptions may be used (
                                <E T="03">e.g.</E>
                                , all vehicles of a mass transit authority or State highway department while in operation, State employees in each local unemployment office, performers in concert halls or radio studios).
                            </P>
                            <P>(c) If you identified workplaces to the agency awarding official at the time of application or award, as described in paragraph (a)(1) of this section, and any workplace that you identified changes during the performance of the award, you must inform the agency awarding official.</P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart C—Requirements for Recipients Who Are Individuals</HD>
                        <SECTION>
                            <SECTNO>§ 182.300</SECTNO>
                            <SUBJECT>What must I do to comply with this part if I am an individual recipient?</SUBJECT>
                            <P>As a condition of receiving a Federal agency award, if you are an individual recipient, you must agree that—</P>
                            <P>(a) You will not engage in the unlawful manufacture, distribution, dispensing, possession, or use of a controlled substance in conducting any activity related to the award; and</P>
                            <P>(b) If you are convicted of a criminal drug offense resulting from a violation occurring during the conduct of any award activity, you will report the conviction:</P>
                            <P>(1) In writing.</P>
                            <P>(2) Within 10 calendar days of the conviction.</P>
                            <P>(3) To the Federal agency awarding official or other designee for each award that you currently have, unless the agency designates a central point for the receipt of the notices, either in the award document or its regulation implementing the guidance in this part. When notice is made to a central point, it must include the identification number(s) of each affected award.</P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart D—Responsibilities of Agency Awarding Officials</HD>
                        <SECTION>
                            <SECTNO>§ 182.400</SECTNO>
                            <SUBJECT>What are my responsibilities as an agency awarding official?</SUBJECT>
                            <P>As a Federal agency awarding official, you must obtain each recipient's agreement, as a condition of the award, to comply with the requirements in—</P>
                            <P>(a) Subpart B of this part, if the recipient is not an individual; or</P>
                            <P>(b) Subpart C of this part, if the recipient is an individual.</P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart E—Violations of This Part and Consequences</HD>
                        <SECTION>
                            <SECTNO>§ 182.500</SECTNO>
                            <SUBJECT>How are violations of this part determined for recipients other than individuals?</SUBJECT>
                            <P>A recipient other than an individual is in violation of the requirements of this part if the agency head or his or her designee determines, in writing, that—</P>
                            <P>(a) The recipient has violated the requirements of Subpart B of this part; or</P>
                            <P> (b) The number of convictions of the recipient's employees for violating criminal drug statutes in the workplace is large enough to indicate that the recipient has failed to make a good faith effort to provide a drug-free workplace.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.505</SECTNO>
                            <SUBJECT>How are violations of this part determined for recipients who are individuals?</SUBJECT>
                            <P>An individual recipient is in violation of the requirements of this part if the agency head or his or her designee determines, in writing, that—</P>
                            <P>(a) The recipient has violated the requirements of Subpart C of this part; or</P>
                            <P>(b) The recipient is convicted of a criminal drug offense resulting from a violation occurring during the conduct of any award activity.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.510</SECTNO>
                            <SUBJECT>What actions will the Federal Government take against a recipient determined to have violated this part?</SUBJECT>
                            <P>If a recipient is determined to have violated this part, as described in § 182.500 or § 182.505, the agency may take one or more of the following actions—</P>
                            <P>(a) Suspension of payments under the award;</P>
                            <P>(b) Suspension or termination of the award; and</P>
                            <P>(c) Suspension or debarment of the recipient under the agency's regulation implementing the OMB guidance on nonprocurement debarment and suspension (2 CFR part 180), for a period not to exceed five years.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.515</SECTNO>
                            <SUBJECT>Are there any exceptions to those actions?</SUBJECT>
                            <P>The agency head may waive with respect to a particular award, in writing, a suspension of payments under an award, suspension or termination of an award, or suspension or debarment of a recipient if the agency head determines that such a waiver would be in the public interest. This exception authority cannot be delegated to any other official.</P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart F—Definitions</HD>
                        <SECTION>
                            <SECTNO>§ 182.605</SECTNO>
                            <SUBJECT>Award.</SUBJECT>
                            <P>Award means an award of financial assistance by a Federal agency directly to a recipient.</P>
                            <P>(a) The term award includes:</P>
                            <P>(1) A Federal grant or cooperative agreement, in the form of money or property in lieu of money.</P>
                            <P>
                                (2) A block grant or a grant in an entitlement program, whether or not the grant is exempted from coverage under the Governmentwide rule that implements OMB Circular A-102 (for availability of OMB circulars, see 5 CFR 1310.3) and specifies uniform administrative requirements.
                                <PRTPAGE P="55781"/>
                            </P>
                            <P>(b) The term award does not include:</P>
                            <P>(1) Technical assistance that provides services instead of money.</P>
                            <P>(2) Loans.</P>
                            <P>(3) Loan guarantees.</P>
                            <P>(4) Interest subsidies.</P>
                            <P>(5) Insurance.</P>
                            <P>(6) Direct appropriations.</P>
                            <P>
                                (7) Veterans' benefits to individuals (
                                <E T="03">i.e.</E>
                                , any benefit to veterans, their families, or survivors by virtue of the service of a veteran in the Armed Forces of the United States).
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.610</SECTNO>
                            <SUBJECT>Controlled substance.</SUBJECT>
                            <P>Controlled substance means a controlled substance in schedules I through V of the Controlled Substances Act (21 U.S.C. 812), and as further defined by regulation at 21 CFR 1308.11 through 1308.15.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.615</SECTNO>
                            <SUBJECT>Conviction.</SUBJECT>
                            <P>Conviction means a finding of guilt (including a plea of nolo contendere) or imposition of sentence, or both, by any judicial body charged with the responsibility to determine violations of the Federal or State criminal drug statutes.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.620</SECTNO>
                            <SUBJECT>Cooperative agreement.</SUBJECT>
                            <P>Cooperative agreement means an award of financial assistance that, consistent with 31 U.S.C. 6305, is used to enter into the same kind of relationship as a grant (see definition of grant in § 182.650), except that substantial involvement is expected between the Federal agency and the recipient when carrying out the activity contemplated by the award. The term does not include cooperative research and development agreements as defined in 15 U.S.C. 3710a.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.625</SECTNO>
                            <SUBJECT>Criminal drug statute.  </SUBJECT>
                            <P>Criminal drug statute means a Federal or non-Federal criminal statute involving the manufacture, distribution, dispensing, use, or possession of any controlled substance.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.630 </SECTNO>
                            <SUBJECT>Debarment.</SUBJECT>
                            <P>Debarment means an action taken by a Federal agency to prohibit a recipient from participating in Federal Government procurement contracts and covered nonprocurement transactions. A recipient so prohibited is debarred, in accordance with the Federal Acquisition Regulation for procurement contracts (48 CFR part 9, subpart 9.4) and agency regulations implementing the OMB guidance on nonprocurement debarment and suspension (2 CFR part 180, which implements Executive Orders 12549 and 12689).</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.635 </SECTNO>
                            <SUBJECT>Drug-free workplace.</SUBJECT>
                            <P>Drug-free workplace means a site for the performance of work done in connection with a specific award at which employees of the recipient are prohibited from engaging in the unlawful manufacture, distribution, dispensing, possession, or use of a controlled substance.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.640 </SECTNO>
                            <SUBJECT>Employee.</SUBJECT>
                            <P>(a) Employee means the employee of a recipient directly engaged in the performance of work under the award, including—</P>
                            <P>(1) All direct charge employees;</P>
                            <P>(2) All indirect charge employees, unless their impact or involvement in the performance of work under the award is insignificant to the performance of the award; and</P>
                            <P>(3) Temporary personnel and consultants who are directly engaged in the performance of work under the award and who are on the recipient's payroll.</P>
                            <P>
                                (b) This definition does not include workers not on the payroll of the recipient (
                                <E T="03">e.g.</E>
                                , volunteers, even if used to meet a matching requirement; consultants or independent contractors not on the payroll; or employees of subrecipients or subcontractors in covered workplaces).
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.645 </SECTNO>
                            <SUBJECT>Federal agency or agency.</SUBJECT>
                            <P>Federal agency or agency means any United States executive department, military department, government corporation, government controlled corporation, any other establishment in the executive branch (including the Executive Office of the President), or any independent regulatory agency.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.650 </SECTNO>
                            <SUBJECT>Grant.</SUBJECT>
                            <P>Grant means an award of financial assistance that, consistent with 31 U.S.C. 6304, is used to enter into a relationship—</P>
                            <P>(a) The principal purpose of which is to transfer a thing of value to the recipient to carry out a public purpose of support or stimulation authorized by a law of the United States, rather than to acquire property or services for the Federal Government's direct benefit or use; and</P>
                            <P>(b) In which substantial involvement is not expected between the Federal agency and the recipient when carrying out the activity contemplated by the award.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.655 </SECTNO>
                            <SUBJECT>Individual.</SUBJECT>
                            <P>Individual means a natural person.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.660 </SECTNO>
                            <SUBJECT>Recipient.</SUBJECT>
                            <P>Recipient means any individual, corporation, partnership, association, unit of government (except a Federal agency) or legal entity, however organized, that receives an award directly from a Federal agency.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.665 </SECTNO>
                            <SUBJECT>State.</SUBJECT>
                            <P>State means any of the States of the United States, the District of Columbia, the Commonwealth of Puerto Rico, or any territory or possession of the United States.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 182.670 </SECTNO>
                            <SUBJECT>Suspension.</SUBJECT>
                            <P>Suspension means an action taken by a Federal agency that immediately prohibits a recipient from participating in Federal Government procurement contracts and covered nonprocurement transactions for a temporary period, pending completion of an investigation and any judicial or administrative proceedings that may ensue. A recipient so prohibited is suspended, in accordance with the Federal Acquisition Regulation for procurement contracts (48 CFR part 9, subpart 9.4) and agency regulations implementing the OMB guidance on nonprocurement debarment and suspension (2 CFR part 180, which implements Executive Orders 12549 and 12689). Suspension of a recipient is a distinct and separate action from suspension of an award or suspension of payments under an award.</P>
                        </SECTION>
                    </SUBPART>
                </PART>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22717 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3110-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 39 </CFR>
                <DEPDOC>[Docket No. FAA-2008-0018; Directorate Identifier 2007-NM-145-AD] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; Airbus Model A310 Series Airplanes and Model A300-600 Series Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), Department of Transportation (DOT). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Supplemental notice of proposed rulemaking (NPRM); reopening of comment period. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The FAA is revising an earlier NPRM for an airworthiness directive (AD) that applies to all Airbus Model A310 series airplanes and Model A300-600 series airplanes. The original NPRM would have required superseding two existing ADs. One existing AD applies to certain Airbus Model A310 series airplanes and currently requires 
                        <PRTPAGE P="55782"/>
                        repetitive inspections for cracking of the flap transmission shafts, and replacement of the transmission shafts if necessary. That existing AD also provides an optional terminating action for the repetitive inspections. The other existing AD applies to all Airbus Model A310 and A300-600 series airplanes and currently requires a one-time inspection of the trimmable horizontal stabilizer actuator, corrective actions if necessary, and follow-on repetitive tasks. The original NPRM would have added revising the Airworthiness Limitations Section of the Instructions for Continued Airworthiness to incorporate new limitations and maintenance tasks for aging systems maintenance. The original NPRM resulted from the manufacturer's determination that life limitations and maintenance tasks are necessary in order to ensure continued operational safety of the affected airplanes. This new action revises the original NPRM by reducing the initial compliance times. We are proposing this supplemental NPRM to prevent reduced structural integrity of these airplanes due to the failure of system components. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive comments on this supplemental NPRM by October 21, 2008. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments by any of the following methods: </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov</E>
                        . Follow the instructions for submitting comments. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-493-2251. 
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590. 
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                    <P>For service information identified in this AD, contact Airbus, 1 Rond Point Maurice Bellonte, 31707 Blagnac Cedex, France. </P>
                </ADD>
                <HD SOURCE="HD1">Examining the AD Docket </HD>
                <P>
                    You may examine the AD docket on the Internet at 
                    <E T="03">http://www.regulations.gov</E>
                    ; or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (telephone 800-647-5527) is in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt. 
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Tom Stafford, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue, SW., Renton, Washington 98057-3356; telephone (425) 227-1622; fax (425) 227-1149. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited </HD>
                <P>
                    We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2008-0018; Directorate Identifier 2007-NM-145-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD because of those comments. 
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://www.regulations.gov</E>
                    , including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD. 
                </P>
                <HD SOURCE="HD1">Discussion </HD>
                <P>
                    The FAA issued a notice of proposed rulemaking (NPRM) (the “original NPRM”) to amend 14 CFR part 39 to include an AD that supersedes two existing ADs: AD 2006-10-11, amendment 39-14595 (71 FR 28254, May 16, 2006), which applies to certain Airbus Model A310 series airplanes; and AD 2006-15-10, amendment 39-14690 (71 FR 42021, July 25, 2006), which applies to all Airbus Model A310 and A300-600 series airplanes. The original NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on January 14, 2008 (73 FR 2197). The original NPRM applies to all Airbus Model A310 series airplanes and Model A300-600 series airplanes. The original NPRM proposed to retain the requirements of the existing ADs. The original NPRM also proposed to add revising the Airworthiness Limitations Section (ALS) of the Instructions for Continued Airworthiness (ICA) to incorporate new limitations and maintenance tasks for aging systems maintenance. 
                </P>
                <HD SOURCE="HD1">Actions Since Original NPRM Was Issued </HD>
                <P>Since the original NPRM was issued, we have determined that the initial compliance times for the revision specified in paragraph (o) of the original NPRM need to be reduced. In paragraph (o) of the original NPRM, we specified that for all tasks “* * * the initial compliance times start from the effective date of this AD * * *.” However, the thresholds specified in Airbus A310 ALS Part 4—Aging Systems Maintenance, Revision 01, dated December 21, 2006; and Airbus A300-600 ALS Part 4—Aging Systems Maintenance, Revision 01, dated December 21, 2006; (which are referred to as the appropriate sources of service information for accomplishing the required actions in paragraph (o) of the original NPRM); start from “* * * the initial entry into service of a specific maintenance task.” </P>
                <P>In order to ensure timely action to address the identified unsafe condition, we have reduced the initial compliance times in order to match the service information. We have revised paragraph (o) of the supplemental NPRM accordingly. </P>
                <HD SOURCE="HD1">Comments </HD>
                <P>We provided the public the opportunity to participate in the development of this AD. We have considered the comments that have been received on the original NPRM. </P>
                <HD SOURCE="HD1">Request To Refer to Latest Revisions of Service Bulletins </HD>
                <P>Federal Express (FedEx) requests that we refer to the latest revision of Airbus Service Bulletin A300-27-6044, Revision 04, dated September 10, 2001; and Airbus Service Bulletin A310-27-2089, Revision 02, dated June 28, 2001 (which are referred to in Table 1 of paragraph (k) of the original NPRM as the appropriate sources of service information for doing the actions specified in paragraphs (l), (m), and (n) of the original NPRM). FedEx states that Airbus Service Bulletin A300-27-6044, Revision 05, dated August 29, 2006; and Airbus Service Bulletin A310-27-2089, Revision 03, dated August 29, 2006; do not specify any additional work and were primarily issued to adjust the service bulletin effectivity as well as to provide additional reference data. </P>
                <P>
                    We agree with the commenter to refer to Airbus Service Bulletin A300-27-6044, Revision 05, dated August 29, 2006; and Airbus Service Bulletin A310-27-2089, Revision 03, dated August 29, 2006. We have reviewed the service bulletins and determined no additional work is required. We have revised Table 1 of this supplemental NPRM accordingly. 
                    <PRTPAGE P="55783"/>
                </P>
                <HD SOURCE="HD1">Request To Clarify Definition of “New” </HD>
                <P>FedEx requests that we clarify the word “new” specified in paragraph (m) of the original NPRM. FedEx states that the word “new” pertains to the replacement of the trimmable horizontal stabilizer actuator (THSA), and the replacement could be with a new or used (serviceable) THSA provided that the THSA has not been operated more than 65,000 flight hours or 40,000 flight cycles or been in service more than 25 years since new, whichever occurs first. FedEx also states that if an THSA that was operated more than 47,000 flight hours has been installed, it must be inspected in accordance with Airbus Service Bulletins A300-27-6044 or A310-27-2089 (as specified in paragraph (n) of the original NPRM). FedEx further states that Airbus is in concurrence with FedEx's comment. </P>
                <P>We agree with the commenter that the replacement specified in paragraph (m) of this supplemental NPRM could be with a new or serviceable THSA. Sub-part 4-2 of the Airbus A300-600 and A310 ALS Part 4 lists the life limits for the operational life of the listed components. When a component (e.g., the THSA) reaches the earliest of any of the life limits in flight hours, flight cycles, or calendar time, that component has reached the end of its given operational life and must be removed from the airplane and replaced by another unit. It is not necessary that the replacement unit/component be “new.” The rules of application for the ALS Part 4 are given in sub-part 4-0 of the ALS. </P>
                <P>It is a requirement that a life-limited component not be operated beyond the limitation stated in the ALS Part 4-2. Thus, for the THSA, as long as none of the limits (65,000 flight hours, 40,000 flight cycles, or 25 years of operation) have been exceeded and the component is classified “serviceable,” then the component can be installed and operated on the airplane. Airbus Operators Information Telex (OIT) SE 999.0074/05/BB, dated August 3, 2005, provides clarification on these limits. We have revised paragraph (m) of this supplemental NPRM to clarify that the installed part may be “new” or “serviceable,” and we have added Note 6 and Note 7 to this supplemental NPRM to refer to the OIT for clarification of these limits. </P>
                <HD SOURCE="HD1">Request To Clarify Starting Point of 25-Year Life Limit </HD>
                <P>FedEx requests that we clarify the starting point for the 25-year life limit specified in the Airbus A300-600 and A310 ALS Part 4 for THSAs built as spare parts and not originally installed on airplanes. FedEx suggests that operators be required to use the date of manufacture of the THSA as documented by Goodrich, the original equipment manufacturer (OEM) of the THSA. FedEx states that it would be difficult to determine when the component, produced as a spare by Goodrich, was first installed on an airplane. </P>
                <P>We agree to clarify the starting point for the 25-year life limit. The ALS Part 4 does not provide the calendar limit guidance that is provided in Airbus Service Information Letter (SIL) 05-008, dated July 7, 2006. Airbus issued SIL 05-008 to give guidance (i.e., a calculation method) for life limitations in calendar parameters for components whose history is partially or completely unknown. This calculation method could be used by operators when they comply with the ALS Parts 4-2 and 4-3(a). </P>
                <P>The SIL is intended for use when operators cannot retrieve their parts history (in flight hours/flight cycles). This method provides an estimated parts life (flight hours/flight cycles) and is very conservative. As suggested in the FedEx request, one method employed in the life calculation (starting point) is the date of manufacture (DOM). The DOM is shown in one of the tables and examples within the SIL. </P>
                <P>The SIL is not currently referenced in the ALS Part 4. However, Airbus has issued OIT SE 999.0008/07/LB, dated January 16, 2007. Section 4 of the OIT advises users of the availability of SIL 05-008. We have added Note 8 to this supplemental NPRM to refer to the OIT and SIL for clarification. </P>
                <HD SOURCE="HD1">Request To Include New THSA Part </HD>
                <P>FedEx requests that we include the new configuration of THSA, part number (P/N) 47142-323, and its life limitation. FedEx states that P/N 47142-323 does not have the 25-year life limit due to the application of enhanced materials and processes used during manufacture to reinforce their resistance to corrosion. FedEx notes that Airbus issued Service Bulletins A300-27-6058 and A310-27-2100, both dated August 30, 2007, to introduce this new THSA configuration, which does not carry a calendar life limit. FedEx further states that ALS Part 4 does not address this THSA configuration. </P>
                <P>We do not agree to include the new THSA part number. We acknowledge that Airbus Service Bulletins A300-27-6058 (for Model A300-600 airplanes) and A310-27-2100 (for Model A310 airplanes) specify procedures to install THSA P/N 47142-323. However, Airbus has not published a revised inspection task that will apply to P/N 47142-323 to address the corrosion issue. After this task has been published, operators may request an alternative method of compliance (AMOC) according to the provisions of paragraph (r) of this supplemental NPRM. We have not revised this supplemental NPRM in this regard. </P>
                <HD SOURCE="HD1">Request To Allow Additional Compliance Time </HD>
                <P>FedEx requests that we add a grace period of 1,200 flight hours for Task Number 274411-12-1. FedEx states that the task is contained within Airbus A310 ALS Part 4—Aging Systems Maintenance, Revision 01, dated December 21, 2006; and Airbus A300-600 ALS Part 4—Aging Systems Maintenance, Revision 01, dated December 21, 2006; which were referred to in paragraph (o) of the original NPRM for the incorporation of new limitations and maintenance tasks for aging systems maintenance. FedEx states that the task establishes a threshold for accomplishment at 47,000 flight hours or 20 years, whichever occurs first, but does not provide a grace period for the inspection on actuators that have exceeded 20 years in service but not yet reached 25 years in service (the established life limit of the THSA). FedEx suggests a grace period of 1,200 flight hours to provide sufficient time to sequence airplanes through maintenance for accomplishment of this THSA inspection at the new established threshold. </P>
                <P>We agree that a grace period is necessary. In accordance with paragraph (o) of this supplemental NPRM, operators have three months to revise the ALS of the ICA to incorporate the tasks specified in Airbus A310 ALS Part 4—Aging Systems Maintenance, Revision 01, dated December 21, 2006; and A300-600 ALS Part 4—Aging Systems Maintenance, Revision 01, dated December 21, 2006; as applicable. For the initial compliance times for the tasks identified in the ALS, we have added paragraph (o)(2) of this supplemental NPRM to provide a grace period of within 3 months after revising the ALS of the ICA. </P>
                <HD SOURCE="HD1">FAA's Determination and Proposed Requirements of the Supplemental NPRM </HD>
                <P>
                    The changes discussed above expand the scope of the original NPRM; therefore, we have determined that it is necessary to reopen the comment period to provide additional opportunity for public comment on this supplemental NPRM. 
                    <PRTPAGE P="55784"/>
                </P>
                <HD SOURCE="HD1">Costs of Compliance </HD>
                <P>The following table provides the estimated costs for U.S. operators to comply with this supplemental NPRM. </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s100,12,12,r50,12,r50">
                    <TTITLE>Estimated Costs </TTITLE>
                    <BOXHD>
                        <CHED H="1">Action </CHED>
                        <CHED H="1">Work hours </CHED>
                        <CHED H="1">Average labor rate per hour </CHED>
                        <CHED H="1">Cost per airplane </CHED>
                        <CHED H="1">Number of U.S.-registered airplanes </CHED>
                        <CHED H="1">Fleet cost </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Inspection (required by AD 2006-10-11) </ENT>
                        <ENT>1 </ENT>
                        <ENT>$80 </ENT>
                        <ENT>$80, per inspection cycle</ENT>
                        <ENT> 59 </ENT>
                        <ENT>$4,720, per inspection cycle.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Inspection (required by AD 2006-15-10) </ENT>
                        <ENT>3 </ENT>
                        <ENT>80 </ENT>
                        <ENT>$240 </ENT>
                        <ENT>213 </ENT>
                        <ENT>$51,120.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Repetitive follow-on tasks (required by AD 2006-15-10) </ENT>
                        <ENT>12 </ENT>
                        <ENT>80 </ENT>
                        <ENT>$960, per inspection cycle </ENT>
                        <ENT>213 </ENT>
                        <ENT>$204,480, per inspection cycle.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALS revision (new action) </ENT>
                        <ENT>1 </ENT>
                        <ENT>80 </ENT>
                        <ENT>$80 </ENT>
                        <ENT>213 </ENT>
                        <ENT>$17,040.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Authority for This Rulemaking </HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the Agency's authority. </P>
                <P>We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, section 44701, “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action. </P>
                <HD SOURCE="HD1">Regulatory Findings </HD>
                <P>We have determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. </P>
                <P>For the reasons discussed above, I certify that the proposed regulation:</P>
                <P>1. Is not a “significant regulatory action” under Executive Order 12866; </P>
                <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and </P>
                <P>3. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. </P>
                <P>
                    We prepared a regulatory evaluation of the estimated costs to comply with this supplemental NPRM and placed it in the AD docket. See the 
                    <E T="02">ADDRESSES</E>
                     section for a location to examine the regulatory evaluation. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39 </HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment </HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES </HD>
                    <P>1. The authority citation for part 39 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701. </P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>2. The Federal Aviation Administration (FAA) amends § 39.13 by removing amendment 39-14595 (71 FR 28254, May 16, 2006) and amendment 39-14690 (71 FR 42021, July 25, 2006) and adding the following new airworthiness directive (AD): </P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Airbus</E>
                                : Docket No. FAA-2008-0018; Directorate Identifier 2007-NM-145-AD. 
                            </FP>
                            <HD SOURCE="HD1">Comments Due Date </HD>
                            <P>(a) The FAA must receive comments on this AD action by October 21, 2008. </P>
                            <HD SOURCE="HD1">Affected ADs </HD>
                            <P>(b) This AD supersedes AD 2006-10-11 and AD 2006-15-10. </P>
                            <HD SOURCE="HD1">Applicability </HD>
                            <P>(c) This AD applies to all Airbus Model A310 series airplanes; and Model A300-600 series airplanes; certificated in any category. </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>This AD requires revisions to certain operator maintenance documents to include new inspections. Compliance with these inspections is required by 14 CFR 91.403(c). For airplanes that have been previously modified, altered, or repaired in the areas addressed by these inspections, the operator may not be able to accomplish the inspections described in the revisions. In this situation, to comply with 14 CFR 91.403(c), the operator must request approval for an alternative method of compliance according to paragraph (r) of this AD. The request should include a description of changes to the required inspections that will ensure the continued operational safety of the airplane.</P>
                            </NOTE>
                            <HD SOURCE="HD1">Unsafe Condition </HD>
                            <P>(d) This AD results from the manufacturer's determination that life limitations and maintenance tasks are necessary in order to ensure continued operational safety of the affected airplanes. We are issuing this AD to prevent reduced structural integrity of these airplanes due to the failure of system components. </P>
                            <HD SOURCE="HD1">Compliance </HD>
                            <P>(e) You are responsible for having the actions required by this AD performed within the compliance times specified, unless the actions have already been done. </P>
                            <HD SOURCE="HD1">Restatement of Requirements of AD 2006-10-11 </HD>
                            <HD SOURCE="HD2">Inspection and Corrective Action </HD>
                            <P>(f) For Airbus Model A310-203, -204, -221, -222, -304, -322, -324, and -325 airplanes, except for airplanes on which Airbus Modification 12247 has been embodied in production: At the earlier of the compliance times specified in paragraph (f)(1) or (f)(2) of this AD, perform a detailed inspection for stress corrosion cracking of the flight transmission shafts located between the power control unit (PCU) and the torque limiters in accordance with the Accomplishment Instructions of Airbus Service Bulletin A310-27-2092, Revision 02, dated April 11, 2005. Thereafter, repeat the inspections as required by paragraph (g) of this AD. Before further flight, replace any cracked transmission shaft discovered during any inspection required by this AD with a new or reconditioned shaft, in accordance with the Accomplishment Instructions of Airbus Service Bulletin A310-27-2095, dated March 29, 2000. Doing an inspection in accordance with paragraph (o) or (p) of this AD terminates the requirements of this paragraph. </P>
                            <P>
                                (1) Within 2,000 flight hours after the last flap asymmetry protection test performed in accordance with Airbus A310 Maintenance 
                                <PRTPAGE P="55785"/>
                                Planning Document (MPD) Task 275600-01-1. 
                            </P>
                            <P>(2) Within 8,000 flight cycles after the last flap asymmetry protection test performed in accordance with Airbus A310 MPD Task 275600-02-1 or 800 flight cycles after June 20, 2006 (the effective date of AD 2006-10-11), whichever comes later. </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 2:</HD>
                                <P>Airbus Service Bulletin A310-27-2092, Revision 02, dated April 11, 2005, refers to Lucas Liebherr Service Bulletin 551A-27-624, Revision 1, dated August 18, 2000, as an additional source of service information for accomplishing the inspections.</P>
                            </NOTE>
                            <NOTE>
                                <HD SOURCE="HED">Note 3:</HD>
                                <P>Airbus Service Bulletin A310-27-2092, Revision 02, refers to Airbus Service Bulletin A310-27-2095, dated March 29, 2000, as a source of service information for replacing the flap transmission shafts.</P>
                            </NOTE>
                            <NOTE>
                                <HD SOURCE="HED">Note 4:</HD>
                                <P>Airbus Service Bulletin A310-27-2095 refers to Lucas Liebherr Service Bulletin 551A-27-M551-05, dated January 12, 2000, as an additional source of service information for replacing the flap transmission shafts.</P>
                            </NOTE>
                            <HD SOURCE="HD1">Repetitive Inspections </HD>
                            <P>(g) Repeat the inspection required by paragraph (f) of this AD at the applicable times specified in paragraphs (g)(1), (g)(2), and (g)(3) of this AD. Doing an inspection in accordance with paragraph (o) or (p) of this AD terminates the requirements of this paragraph. </P>
                            <P>(1) Before further flight after any occurrence of jamming of the flap transmission system. </P>
                            <P>(2) At intervals not to exceed 2,000 flight hours after each flap asymmetry protection test performed in accordance with Airbus A310 MPD Task 275600-01-1. </P>
                            <P>(3) At intervals not to exceed 8,000 flight cycles after each flap asymmetry protection test performed in accordance with Airbus A310 MPD Task 275600-02-1. </P>
                            <HD SOURCE="HD1">Optional Terminating Action </HD>
                            <P>(h) Replacing any flap transmission shaft with a new or reconditioned transmission shaft in accordance with the Accomplishment Instructions of Airbus Service Bulletin A310-27-2095, dated March 29, 2000, ends the inspections required by paragraphs (f) and (g) of this AD for that transmission shaft only. </P>
                            <HD SOURCE="HD1">Actions Performed Using Previously Issued Service Information </HD>
                            <P>(i) Actions performed in accordance with Airbus Service Bulletin A310-27-2092, dated April 9, 1999; or Revision 01, dated December 11, 2001; are considered acceptable for compliance with the corresponding requirements of paragraphs (f) and (g) of this AD. </P>
                            <HD SOURCE="HD1">No Reporting </HD>
                            <P>(j) Although Airbus Service Bulletin A310-27-2092, Revision 02, dated April 11, 2005, specifies to submit certain information to the manufacturer, this AD does not include that requirement. </P>
                            <HD SOURCE="HD1">Restatement of Requirements of AD 2006-15-10 </HD>
                            <HD SOURCE="HD2">Service Bulletin References </HD>
                            <P>(k) Unless otherwise specified in this AD, the term “service bulletin,” as used in paragraphs (l), (m), and (n) of this AD, means the applicable required service bulletin identified in Table 1 of this AD. The service bulletins refer to Goodrich Actuation Systems Service Bulletin 47142-27-11, Revision 3, dated April 25, 2005, as an additional source of service information for the required actions. </P>
                            <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s60,r60,r60">
                                <TTITLE>Table 1—Service Bulletins </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Required Airbus Service Bulletin </CHED>
                                    <CHED H="1">Approved Airbus Service Bulletin version for actions done before the effective date of this AD </CHED>
                                    <CHED H="1">Airbus airplane model </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">A300-27-6044, Revision 04, dated September 10, 2001; or A300-27-6044, Revision 05, dated August 29, 2006 </ENT>
                                    <ENT>A300-27-6044, Revision 02, dated August 26, 2000; or Revision 03, dated June 28, 2001 </ENT>
                                    <ENT>
                                        A300 B4-601, B4-603, B4-620, and B4-622.
                                        <LI>A300 B4-605R and B4-622R.</LI>
                                        <LI>A300 F4-605R and F4-622R.</LI>
                                        <LI>A300 C4-605R Variant F.</LI>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">A310-27-2089, Revision 02, dated June 28, 2001; or A310-27-2089, Revision 03, dated August 29, 2006 </ENT>
                                    <ENT>A310-27-2089, Revision 01, dated August 25, 2000 </ENT>
                                    <ENT>
                                        A310-203, -204, -221, and -222
                                        <LI>A310-304, -322, -324, and -325. </LI>
                                    </ENT>
                                </ROW>
                            </GPOTABLE>
                            <HD SOURCE="HD2">Inspection </HD>
                            <P>(l) At the applicable time specified in paragraph (l)(1) or (l)(2) of this AD, do a detailed inspection of specified components of the trimmable horizontal stabilizer actuator (THSA) in accordance with paragraph 1.E.(2)(a) and the Accomplishment Instructions of the applicable service bulletin. Repair any discrepancy before further flight in accordance with a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the European Aviation Safety Agency (EASA) (or its delegated agent). TRW Aeronautical Systems/Lucas Aerospace Component Maintenance Manual 27-44-13, dated September 14, 2001, is one acceptable method for the repair. Doing an inspection in accordance with paragraph (o) or (p) of this AD terminates the requirements of this paragraph. </P>
                            <P>(1) If the flight hours accumulated on the THSA can be positively determined: Inspect at the earlier of: </P>
                            <P>(i) Before the accumulation of 47,000 total flight hours on the THSA, or within 600 flight hours after August 29, 2006 (the effective date of AD 2006-15-10), whichever occurs later. </P>
                            <P>(ii) Within 25 years since the THSA was new or within 600 flight hours after August 29, 2006, whichever occurs later. </P>
                            <P>(2) If the flight hours accumulated on the THSA cannot be positively determined: Inspect before the accumulation of 47,000 total flight hours on the airplane, or within 600 flight hours after August 29, 2006, whichever occurs later. </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 5:</HD>
                                <P>For the purposes of this AD, a detailed inspection is: “An intensive examination of a specific item, installation, or assembly to detect damage, failure, or irregularity. Available lighting is normally supplemented with a direct source of good lighting at an intensity deemed appropriate. Inspection aids such as mirror, magnifying lenses, etc., may be necessary. Surface cleaning and elaborate procedures may be required.”</P>
                            </NOTE>
                            <HD SOURCE="HD2">Follow-on Repetitive Tasks </HD>
                            <P>(m) After the inspection required by paragraph (l) of this AD: Do the repetitive tasks in accordance with the Accomplishment Instructions and at the times specified in paragraph 1.E.(2)(b) of the service bulletin, as applicable, except as provided by paragraph (n) of this AD. The repetitive tasks are valid only until the THSA operational life exceeds 65,000 flight hours, 40,000 flight cycles, or 25 years, whichever occurs first. Before the THSA is operated beyond these extended life goals, it must be replaced with a new or serviceable THSA, except as required by paragraph (n) of this AD. Doing an inspection in accordance with paragraph (o) or (p) of this AD terminates the requirements of this paragraph. </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 6:</HD>
                                <P>Refer to Airbus Operators Information Telex (OIT) SE 999.0074/05/BB, dated August 3, 2005, for additional information on the THSA life limits.</P>
                            </NOTE>
                            <HD SOURCE="HD2">THSA Replacement </HD>
                            <P>
                                (n) For any THSA, whether discrepant or not, that is replaced with a new or serviceable THSA: Within 47,000 flight hours or 25 years, whichever occurs first, after the THSA is replaced, do the applicable tasks specified in paragraph 1.E.(2)(a) and the Accomplishment Instructions of the applicable service bulletin. Thereafter repeat the tasks within the repetitive intervals specified in paragraph 1.E.(2)(b) of the applicable service bulletin. Doing the corresponding tasks in accordance with 
                                <PRTPAGE P="55786"/>
                                paragraph (o) or (p) of this AD terminates the requirements of this paragraph. 
                            </P>
                            <HD SOURCE="HD1">New Requirements of This AD </HD>
                            <HD SOURCE="HD2">Revise Airworthiness Limitations Section (ALS) To Incorporate Limitations and Maintenance Tasks for Aging Systems Maintenance </HD>
                            <P>(o) Within 3 months after the effective date of this AD, revise the ALS of the Instructions for Continued Airworthiness (ICA) to incorporate Airbus A310 ALS Part 4—Aging Systems Maintenance, Revision 01, dated December 21, 2006; or Airbus A300-600 ALS Part 4—Aging Systems Maintenance, Revision 01, dated December 21, 2006; as applicable. For all tasks identified in Airbus A310 ALS Part 4—Aging Systems Maintenance, Revision 01; and Airbus A300-600 ALS Part 4—Aging Systems Maintenance, Revision 01; do the tasks at the later of the times specified in paragraphs (o)(1) and (o)(2) of this AD, except as provided by paragraph (p) of this AD. The repetitive inspections must be accomplished thereafter at the interval specified in Airbus A310 ALS Part 4—Aging Systems Maintenance, Revision 01; and Airbus A300-600 ALS Part 4—Aging Systems Maintenance, Revision 01. Doing an inspection required by this paragraph terminates the corresponding inspection required by paragraph (f), (g), (l), (m), or (n) of this AD. </P>
                            <P>(1) At the initial compliance times (thresholds) specified in the applicable ALS Part 4—Aging Systems Maintenance, with the compliance times starting from the later of the times specified in paragraphs (o)(1)(i) and (o)(1)(ii) of this AD. </P>
                            <P>(i) Since first flight of the airplane. </P>
                            <P>(ii) Since the applicable part was new or refurbished if the part's life (in flight hours, flight cycles, landings, or calendar time, as applicable) can be conclusively determined. </P>
                            <P>(2) Within 3 months after doing the revision of the ALS of the ICA required by paragraph (o) of this AD. </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 7:</HD>
                                <P>Refer to Airbus OIT SE 999.0074/05/BB, dated August 3, 2005, for additional information on the THSA life limits.</P>
                            </NOTE>
                            <NOTE>
                                <HD SOURCE="HED">Note 8:</HD>
                                <P>Refer to Airbus OIT SE 999.0008/07/LB, dated January 16, 2007; and Airbus Service Information Letter (SIL) 05-008, Revision 1, dated February 21, 2007; for additional information on the THSA life limits and calculation method for unknown history of parts.</P>
                            </NOTE>
                            <P>(p) For airplanes on which any life limitation/maintenance task has been complied with in accordance with the requirements of paragraph (f), (g), (l), (m), or (n) of this AD (e.g., AD 2006-10-11 or AD 2006-15-10), the last accomplishment of each limitation/task must be retained as a starting point for the accomplishment of each corresponding limitation/task interval now introduced in Airbus A310 ALS Part 4—Aging Systems Maintenance, Revision 01, dated December 21, 2006; and A300-600 ALS Part 4—Aging Systems Maintenance, Revision 01, dated December 21, 2006; as applicable. Doing an inspection required by this paragraph terminates the corresponding inspection required by paragraph (f), (g), (l), (m), or (n) of this AD. </P>
                            <P>(q) Except as provided by paragraph (r) of this AD: After accomplishing the actions specified in paragraphs (o) and (p) of this AD, no alternative inspection, inspection intervals, or limitations may be used. </P>
                            <HD SOURCE="HD2">Alternative Methods of Compliance (AMOCs) </HD>
                            <P>(r)(1) The Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. Send information to ATTN: Tom Stafford, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue SW., Renton, Washington 98057-3356; telephone (425) 227-1622; fax (425) 227-1149. Before using any approved AMOC on any airplane to which the AMOC applies, notify your appropriate principal inspector (PI) in the FAA Flight Standards District Office (FSDO), or lacking a PI, your local FSDO. </P>
                            <P>(2) AMOCs approved previously in accordance with AD 2006-10-11 are not approved as AMOCs with this AD. </P>
                            <P>(3) AMOCs approved previously in accordance with AD 2006-15-10 are not approved as AMOCs with this AD. </P>
                            <HD SOURCE="HD2">Related Information </HD>
                            <P>(s) EASA airworthiness directive 2007-0092, dated April 10, 2007, also addresses the subject of this AD.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on September 18, 2008. </DATED>
                        <NAME>Michael Kaszycki, </NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22632 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 39 </CFR>
                <DEPDOC>[Docket No. FAA-2008-1020; Directorate Identifier 2008-CE-053-AD] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; Vulcanair S.p.A. Model P68 Series Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), Department of Transportation (DOT). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We propose to adopt a new airworthiness directive (AD) for the products listed above. This proposed AD results from mandatory continuing airworthiness information (MCAI) originated by an aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as:</P>
                    <EXTRACT>
                        <P>The Safe Fatigue Limits (SFL) of the Wing Structure in the P68 Series aircraft have been redefined from the current 8,500 Flight Hours to a new value to be calculated up to a maximum of 17,500 Flight Hours. This has been developed by Vulcanair under Change No. MOD.P68/79 Rev. 1 and approved by EASA with No. EASA.A.C.02482 on 07 June 2006.</P>
                    </EXTRACT>
                </SUM>
                <FP>The proposed AD would require actions that are intended to address the unsafe condition described in the MCAI. </FP>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive comments on this proposed AD by October 27, 2008. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments by any of the following methods: </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251. 
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590. 
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                </ADD>
                <HD SOURCE="HD1">Examining the AD Docket </HD>
                <P>
                    You may examine the AD docket on the Internet at 
                    <E T="03">http://www.regulations.gov;</E>
                     or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (telephone (800) 647-5527) is in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt. 
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sarjapur Nagarajan, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4145; fax: (816) 329-4090. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited </HD>
                <P>
                    We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2008-1020; Directorate Identifier 2008-CE-053-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the 
                    <PRTPAGE P="55787"/>
                    closing date and may amend this proposed AD because of those comments. 
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://www.regulations.gov,</E>
                     including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD. 
                </P>
                <HD SOURCE="HD1">Discussion </HD>
                <P>The European Aviation Safety Agency (EASA), which is the Technical Agent for the Member States of the European Community, has issued AD No.: 2007-0027, dated February 5, 2007 (referred to after this as “the MCAI”), to correct an unsafe condition for the specified products. The MCAI states:</P>
                <EXTRACT>
                    <P>The Safe Fatigue Limits (SFL) of the Wing Structure in the P68 Series aircraft have been redefined from the current 8,500 Flight Hours to a new value to be calculated up to a maximum of 17,500 Flight Hours. This has been developed by Vulcanair under Change No. MOD.P68/79 Rev. 1 and approved by EASA with No. EASA.A.C.02482 on 07 June 2006. </P>
                    <P>The new Safe Fatigue Limits depend on: </P>
                    <P>(a) Status of the modification (reinforcement) of the wing structure itself (Partenavia Service Bulletin No. 65 refers); and </P>
                    <P>(b) Aircraft Flight Hours accumulated before the modification (reinforcement) was implemented.</P>
                </EXTRACT>
                <FP>You may obtain further information by examining the MCAI in the AD docket. </FP>
                <HD SOURCE="HD1">Relevant Service Information </HD>
                <P>Vulcanair S.p.A. has issued Service Bulletin No. 120 Rev. 1, dated June 7, 2006. The actions described in this service information are intended to correct the unsafe condition identified in the MCAI. </P>
                <HD SOURCE="HD1">FAA's Determination and Requirements of the Proposed AD </HD>
                <P>This product has been approved by the aviation authority of another country, and is approved for operation in the United States. Pursuant to our bilateral agreement with this State of Design Authority, they have notified us of the unsafe condition described in the MCAI and service information referenced above. We are proposing this AD because we evaluated all information and determined the unsafe condition exists and is likely to exist or develop on other products of the same type design. </P>
                <HD SOURCE="HD1">Differences Between This Proposed AD and the MCAI or Service Information </HD>
                <P>We have reviewed the MCAI and related service information and, in general, agree with their substance. But we might have found it necessary to use different words from those in the MCAI to ensure the AD is clear for U.S. operators and is enforceable. In making these changes, we do not intend to differ substantively from the information provided in the MCAI and related service information. </P>
                <P>We might also have proposed different actions in this AD from those in the MCAI in order to follow FAA policies. Any such differences are highlighted in a NOTE within the proposed AD. </P>
                <HD SOURCE="HD1">Costs of Compliance </HD>
                <P>We estimate that this proposed AD will affect 72 products of U.S. registry. We also estimate that it would take about 80 work-hours per product to comply with the basic requirements of this proposed AD. The average labor rate is $80 per work-hour. </P>
                <P>Based on these figures, we estimate the cost of the proposed AD on U.S. operators to be $460,800, or $6,400 per product. </P>
                <P>We have no way of determining the number of products that may need any necessary follow-on actions. </P>
                <HD SOURCE="HD1">Authority for This Rulemaking </HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority. </P>
                <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action. </P>
                <HD SOURCE="HD1">Regulatory Findings </HD>
                <P>We determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. </P>
                <P>For the reasons discussed above, I certify this proposed regulation: </P>
                <P>1. Is not a “significant regulatory action” under Executive Order 12866; </P>
                <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and </P>
                <P>3. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. </P>
                <P>We prepared a regulatory evaluation of the estimated costs to comply with this proposed AD and placed it in the AD docket. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment </HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES </HD>
                    <P>1. The authority citation for part 39 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701. </P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>2. The FAA amends § 39.13 by adding the following new AD:</P>
                        <EXTRACT>
                            <FP>
                                <E T="04">Vulcanair S.p.A. (Type Certificate No. A31EU formally held by Partenavia Costruzioni Aeronautiche S.p.A.):</E>
                                 Docket No. FAA-2008-1020; Directorate Identifier 2008-CE-053-AD. 
                            </FP>
                            <HD SOURCE="HD1">Comments Due Date </HD>
                            <P>(a) We must receive comments by October 27, 2008. </P>
                            <HD SOURCE="HD1">Affected ADs </HD>
                            <P>(b) None. </P>
                            <HD SOURCE="HD1">Applicability </HD>
                            <P>(c) This AD applies to Models P 68, P 68B, P 68C, P 68C-TC, P 68 “OBSERVER,” AP68TP300 “SPARTACUS,” P68TC “OBSERVER,” AP68TP 600 “VIATOR,” and P68 “OBSERVER 2” airplanes; all serial numbers, certificated in any category. </P>
                            <HD SOURCE="HD1">Subject </HD>
                            <P>(d) Air Transport Association of America (ATA) Code 51: Standard Practices/Structures. </P>
                            <HD SOURCE="HD1">Reason </HD>
                            <P>(e) The mandatory continuing airworthiness information (MCAI) states:</P>
                            <P>
                                The Safe Fatigue Limits (SFL) of the Wing Structure in the P68 Series aircraft have been redefined from the current 8,500 Flight Hours to a new value to be calculated up to a maximum of 17,500 Flight Hours. This has been developed by Vulcanair under Change No. MOD.P68/79 Rev. 1 and approved by EASA with No. EASA.A.C.02482 on 07 June 2006. 
                                <PRTPAGE P="55788"/>
                            </P>
                            <P>The new Safe Fatigue Limits depend on: </P>
                            <P>(1) Status of the modification (reinforcement) of the wing structure itself (Partenavia Service Bulletin No. 65 refers); and </P>
                            <P>(2) Aircraft Flight Hours accumulated before the modification (reinforcement) was implemented. </P>
                            <HD SOURCE="HD1">Actions and Compliance </HD>
                            <P>(f) Unless already done, do the following actions: </P>
                            <P>(1) For serial numbers 01 through 356, determine the safe fatigue limit of the wing structure following Vulcanair S.p.A. Service Bulletin No. 120 Rev. 1, dated June 7, 2006, within 8,500 hours time-in-service (TIS) since new or within 500 hours TIS after the effective date of this AD, whichever occurs later. </P>
                            <P>(2) For serial numbers 01 through 356, inspect the wing structure and the wing to fuselage attachments following Vulcanair S.p.A. Service Bulletin No. 120 Rev. 1, dated June 7, 2006, within the safe fatigue limit determined in paragraph (f)(1) of this AD or within 500 hours TIS after the effective date of this AD, whichever occurs later. Repetitively thereafter inspect at intervals not to exceed every 500 hours TIS. </P>
                            <P>(3) For serial numbers 357 and above, inspect the wing structure and the wing to fuselage attachments following Vulcanair S.p.A. Service Bulletin No. 120 Rev. 1, dated June 7, 2006, within 17,500 hours TIS since new or within 500 hours TIS after the effective date of this AD, whichever occurs later. Repetitively thereafter inspect at intervals not to exceed every 500 hours TIS. </P>
                            <P>(4) For all serial numbers, inspect the stabilator following Vulcanair S.p.A. Service Bulletin No. 120 Rev. 1, dated June 7, 2006, within 8,500 hours TIS since new or within 500 hours TIS after the effective date of this AD, whichever occurs later. Repetitively thereafter inspect at intervals not to exceed every 500 hours TIS. </P>
                            <P>(5) If as a result of any inspection required by paragraphs (f)(2), (f)(3), or (f)(4) of this AD you find any discrepancies (for example, cracked or broken parts), do one of the following actions before further flight: </P>
                            <P>(i) Repair the airplane following FAA-approved repair instructions obtained from Vulcanair S.p.A.; or </P>
                            <P>(ii) Repair the airplane following a repair method approved by the FAA for this AD. Contact the FAA at the address in paragraph (g)(1) of this AD for an FAA-approved method. </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>For certain Model P 68 airplanes, AD 85-08-04 requires repetitive inspections of the front and rear wing spars for cracks with modification if cracks are found. The modification terminates the repetitive inspections required in AD 85-08-04 and may be done regardless if cracks are found. The actions of AD 85-08-08 are independent of this AD action and remain in effect.</P>
                            </NOTE>
                            <HD SOURCE="HD1">FAA AD Differences </HD>
                            <NOTE>
                                <HD SOURCE="HED">Note 2:</HD>
                                <P>This AD differs from the MCAI and/or service information as follows: </P>
                                <P>(1) The MCAI is extending the safe fatigue limits of the wing structure and the wing to fuselage attachments of certain airplanes. Airplanes registered in the United States did not have safe fatigue limits established for the wing structure and the wing to fuselage attachments. This AD is establishing safe fatigue limits for the wing structure and the wing to fuselage attachments. This AD is also establishing safe fatigue limits for the stabilator. </P>
                                <P>(2) The MCAI requires implementation of safe fatigue limits into the airplane maintenance program (maintenance program). An airplane registered in the United States and operated under 14 CFR part 91 is required to have a maintenance program, but not necessarily following the airplane maintenance manual. This AD requires you to do specific actions of Vulcanair S.p.A. Service Bulletin No. 120 Rev. 1, dated June 7, 2006, rather than incorporating those actions into the maintenance program.</P>
                            </NOTE>
                            <HD SOURCE="HD1">Other FAA AD Provisions </HD>
                            <P>(g) The following provisions also apply to this AD: </P>
                            <P>(1) Alternative Methods of Compliance (AMOCs): The Manager, Standards Office, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. Send information to ATTN: Sarjapur Nagarajan, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4145; fax: (816) 329-4090. Before using any approved AMOC on any airplane to which the AMOC applies, notify your appropriate principal inspector (PI) in the FAA Flight Standards District Office (FSDO), or lacking a PI, your local FSDO. </P>
                            <P>(2) Airworthy Product: For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service. </P>
                            <P>
                                (3) Reporting Requirements: For any reporting requirement in this AD, under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501 
                                <E T="03">et. seq.</E>
                                ), the Office of Management and Budget (OMB) has approved the information collection requirements and has assigned OMB Control Number 2120-0056. 
                            </P>
                            <HD SOURCE="HD1">Related Information </HD>
                            <P>(h) Refer to MCAI European Aviation Safety Agency AD No.: 2007-0027, dated February 5, 2007; and Vulcanair S.p.A. Service Bulletin No. 120 Rev. 1, dated June 7, 2006, for related information.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Kansas City, Missouri, on September 17, 2008. </DATED>
                        <NAME>James E. Jackson, </NAME>
                        <TITLE>Acting Manager, Small Airplane Directorate,   Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22338 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 93</CFR>
                <DEPDOC>[Docket No. FAA-2007-26470; and Notice No. 08-10]</DEPDOC>
                <RIN>RIN 2120-AJ29</RIN>
                <SUBJECT>Proposed Establishment of Special Air Traffic Rule, in the Vicinity of Luke AFB, AZ</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This rule would establish a Special Air Traffic Rule (SATR) in the vicinity of Luke Air Force Base (Luke) which would require general aviation (GA) traffic operating under visual flight rules (VFR) to establish communication with the Luke Radar Approach Control (RAPCON) while operating in the area around Luke. This action is necessary to address reported near midair collisions in the area around Luke and would help reduce the potential for midair collisions in the vicinity of Luke. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before November 25, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments identified by Docket Number FAA-2007-26470 using any of the following methods: </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov</E>
                         and follow the online instructions for sending your comments electronically. 
                    </P>
                    <P>
                        • 
                        <E T="03">Mail</E>
                        : Send comments to Docket Operations, M-30; U.S. Department of Transportation, 1200 New Jersey Avenue, SE., Room W12-140, West Building Ground Floor, Washington, DC 20590-0001. 
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery or Courier</E>
                        : Bring comments to Docket Operations in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax</E>
                        : Fax comments to Docket Operations at 202-493-2251. 
                    </P>
                    <P>
                        For more information on the rulemaking process, see the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document. 
                    </P>
                    <P>
                        <E T="03">Privacy:</E>
                         We will post all comments we receive, without change, to 
                        <E T="03">http://www.regulations.gov</E>
                        , including any personal information you provide. Using the search function of our docket Web site, anyone can find and read the electronic form of all comments received into any of our dockets, 
                        <PRTPAGE P="55789"/>
                        including the name of the individual sending the comment (or signing the comment for an association, business, labor union, etc.). You may review DOT's complete Privacy Act Statement in the 
                        <E T="04">Federal Register</E>
                         published on April 11, 2000 (65 FR 19477-78) or you may visit 
                        <E T="03">http://DocketsInfo.dot.gov</E>
                        . 
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         To read background documents or comments received, go to 
                        <E T="03">http://www.regulations.gov</E>
                         at any time and follow the online instructions for accessing the docket. Or, go to Docket Operations in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For technical questions concerning this proposed rule contact Ken McElroy, Airspace and Rules Group, Office of System Operations Airspace and AIM, AJR-33 Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591; telephone: (202) 267-8783. For legal questions contact Adrianne Wojcik, Office of Chief Counsel, Regulations Division, Air Traffic &amp; Certification of Airman Law Branch, AGC-240 Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591; telephone: (202) 267-7776. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Later in this preamble under the Additional Information section, we discuss how you can comment on this proposal and how we will handle your comments. Included in this discussion is related information about the docket, privacy, and the handling of proprietary or confidential business information. We also discuss how you can get a copy of related rulemaking documents. </P>
                <HD SOURCE="HD1">Authority for This Rulemaking </HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106, describes the authority of the FAA Administrator, including the authority to issue, rescind, and revise regulations. Subtitle VII, Aviation Programs, describes, in more detail, the scope of the agency's authority. </P>
                <P>This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Chapter 401, Section 40103(b), which allows the Administrator to regulate the use of the navigable airspace necessary to ensure the safety of aircraft and the efficient use of airspace. Moreover, Subtitle VII, Part A, Subpart III, Chapter 447, Section 44701(c) authorizes the Administrator to regulate air commerce in a way that helps to reduce or eliminate the possibility or recurrence of accidents in air transportation. The proposed change is within the scope of our authority and is a reasonable and necessary exercise of our statutory obligations.</P>
                <HD SOURCE="HD1">Background </HD>
                <P>Luke Air Force Base (AFB) is home to the 56th Fighter Wing, the United States Air Force's largest fighter wing. Since 1941, Luke has trained pilots and other aircrew members for America's front-line fighter aircraft. Today, over 200 F-16s conduct more than 201,000 annual operations, and a majority of these operations are for student training. Situated beneath the Phoenix Class B Airspace Area, the Luke terminal area consists of Class D airspace. The Phoenix Deer Valley Airport (the nation's third busiest general aviation airport in 2004) is located within 5 nautical miles of the Luke terminal airspace. There are two flight schools and two Fixed Base Operators located at Phoenix Deer Valley Airport, and the flight schools conduct training within the vicinity of Luke. </P>
                <P>Alert Area A-231 is located adjacent and west of Luke, and is utilized by a high volume of pilot jet training operations. Military pilots are advised to be particularly alert when flying in Alert Area A-231, but there is no requirement for civil aircraft to establish communication with the Luke RAPCON during transit. The Air Force Flight Safety Office at Luke points out that although reported near midair collisions are approximately 3 per quarter, each occurrence affects multiple aircraft in the same formation. The significant number of near midair collisions between Luke F-16s and VFR aircraft indicates VFR pilots are not avoiding this area of concentrated student jet transition training. </P>
                <P>Operational problems affecting safety in the Luke terminal airspace area are particularly acute and include complex and voluminous traffic, aircraft congestion, terrain that constrains aircraft operations, and the uncontrolled mix of IFR and VFR traffic. Luke RAPCON traffic counts show a mix of military F-16 aircraft operations and GA traffic operations, with some civil air carrier operations. F-16 aircraft are operating at significantly higher airspeeds than most civil GA traffic, normally 200+ knots faster on arrival and 250+ knots faster on departure. This difference in airspeed creates extreme closure rates on converging F-16 and GA aircraft. In addition, complexity is increased because GA aircraft often do not detect all of the aircraft in a military flight formation. Student pilot training in the F-16 aircraft, combined with student flight training in GA aircraft, diminishes see-and-avoid concepts, seriously compromises flight safety and increases the midair collision potential. The Luke RAPCON provides services to GA aircraft on request, but safety can be significantly enhanced with the full participation of all aircraft operating within the vicinity of the Luke terminal airspace area. </P>
                <P>The average number of conflicts between controlled and uncontrolled aircraft has increased steadily since 2000. Direct communication requirements for aircraft operating in the vicinity of the Luke terminal airspace area would reduce the number of conflicts and the near midair collision potential. Aircraft track data modeling tools indicate a significant volume of GA traffic crossing Luke primary instrument final approach course. These data indicate a direct correlation between near midair collision data and the proximity/flight patterns of GA aircraft operating out of the Phoenix Deer Valley Airport. Data track analysis also shows GA traffic from Goodyear Airport and Glendale Airport crossing the final approach course and departure path for Runway 21 at Luke. </P>
                <P>There are a number of prominent landmarks that GA aircraft use when operating under VFR. Two of these landmarks are the Glendale Arrowhead Mall and the Peoria Power Plant/Substation, which are very close to the Luke Runway 21 final approach course. Luke F-16s use the Peoria Power plant as a visual aid for turning to the final approach course when conducting formation landings. Additionally, many of the flight schools use the Proving Grounds located approximately 5 miles north of the Luke Auxiliary Field for conducting practice aircraft operations. Aircraft operations in the vicinity of the Proving Grounds conflict with the downwind radar pattern for the Luke Auxiliary Field. The use of these prominent VFR landmarks results in conflicts with the IFR and VFR patterns of Luke F-16s. </P>
                <P>
                    For the past few years, the United States Air Force (USAF) has been educating the local aviation community about serious operational problems, including voluminous air traffic congestion, and the uncontrolled mix of IFR and VFR traffic, which impact safety around Luke. Initially, the USAF addressed these problems by making pilots at local airports and flight schools aware of the issue and urging aircraft operators to use various traffic services that could make operations in the area 
                    <PRTPAGE P="55790"/>
                    safer. The USAF also posted its midair collision avoidance program on the Flying Office Safety Web site at: 
                    <E T="03">http://www.luke.af.mil/library/midaircollisionavoidance.asp</E>
                    . Although the ongoing educational efforts have had some success, leading to a reduction in near misses, there continued to be an average of one near midair collision per month. The USAF finally concluded that safety problems at Luke were so acute the USAF sought a rulemaking solution. 
                </P>
                <P>On July 21, 2006, the USAF petitioned the FAA to establish a SATR in the vicinity of Luke, which would require pilots to obtain an air traffic clearance to operate in the area (FAA-2006-25459-1). The USAF believes that the growing amount of VFR traffic combined with a high volume of military air traffic, as well as the increasing number of near midair collisions occurring in the Phoenix West Valley, fully justify such an action. The petition included letters from local mayors, members of Congress, and U.S. senators, as well as many aviation organizations, such as Pam Am International Flight Academy, Westwind School of Aeronautics, Oxford Airline Training Center, Airline Training Center Arizona, Inc., and WESTMARC (a regional coalition of business, government, education and community organizations), endorsing the petition and strongly supporting the action. </P>
                <P>The Aircraft Owners and Pilots Association (AOPA) and a few local pilot associations, such as Deer Valley Pilots Association and the Arizona Pilots Association, responded to the proposal by opposing any action that would require air traffic clearances to operate in the area. They insisted on solving the problem through more education and more robust charting notations about avoiding the Luke area during its peak operational hours. However, as discussed above, the USAF has already exhausted the use of non-rulemaking alternatives, which has not solved the serious problem of near midair collisions. </P>
                <P>After analyzing the petition and the initial response of the aviation community it generated, the FAA agrees that the establishment of a SATR in the area would significantly reduce safety problems in the vicinity of Luke. However, instead of requiring an air traffic clearance to operate in the area, we believe that a simple radio communication requirement for pilots operating around Luke would suffice to solve the issue of near midair collisions in the area. Hence, the proposed rule does not include a flight plan or advance clearance requirements. There may be a small number of non-radio-equipped aircraft operating in the area, but those operators would be able to contact the USAF air traffic control by phone 24 hours in advance for alternate arrangements when transiting the area. </P>
                <P>The implementation of a SATR with a two-way radio communication requirement would provide an additional safety margin and increase the protection of both military and GA aircraft. Currently, all military aircraft en-route to/from Luke are required to establish two-way radio communication with Luke RAPCON, but the absence of required radio contact with VFR aircraft has led to a significant increase in the number of near midair collisions. When pilots operating VFR use advertised advisory services available at Luke RAPCON they are issued timely traffic advisories and assistance to successfully transit the area. Luke will provide continuous information on the status of the Luke SATR for flight crews both in flight and on the ground via land line and Automatic Terminal Information Service (ATIS). It is not the intent of this proposal to deny pilots flying VFR access to the area once communication is established with Luke RAPCON. Additionally, this proposal is minimally burdensome and will enhance safety. </P>
                <HD SOURCE="HD1">Paperwork Reduction Act </HD>
                <P>The Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)) requires that the FAA consider the impact of paperwork and other information collection burdens imposed on the public. We have determined that there is no new information collection requirement associated with this proposed rule. </P>
                <HD SOURCE="HD1">Regulatory Evaluation Summary </HD>
                <P>Changes to Federal regulations must undergo several economic analyses. First, Executive Order 12866 directs that each Federal agency shall propose or adopt a regulation only upon a reasoned determination that the benefits of the intended regulation justify its costs. Second, the Regulatory Flexibility Act of 1980 (Pub. L. 96-354) requires agencies to analyze the economic impact of regulatory changes on small entities. Third, the Trade Agreements Act (Pub. L. 96-39) prohibits agencies from setting standards that create unnecessary obstacles to the foreign commerce of the United States. In developing U.S. standards, this Trade Act requires agencies to consider international standards and, where appropriate, that they be the basis of U.S. standards. Fourth, the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4) requires agencies to prepare a written assessment of the costs, benefits, and other effects of proposed or final rules that include a Federal mandate likely to result in the expenditure by State, local, or tribal governments, in the aggregate, or by the private sector, of $100 million or more annually (adjusted for inflation with base year of 1995). This portion of the preamble summarizes the FAA's analysis of the economic impacts of this proposed rule. We suggest readers seeking greater detail read the full regulatory evaluation, a copy of which we have placed in the docket for this rulemaking. </P>
                <P>In conducting these analyses, FAA has determined that this proposed rule: (1) Has benefits that justify its costs, (2) is not an economically “significant regulatory action” as defined in section 3(f) of Executive Order 12866, (3) is not “significant” as defined in DOT's Regulatory Policies and Procedures; (4) would not have a significant economic impact on a substantial number of small entities; (5) would not create unnecessary obstacles to the foreign commerce of the United States; and (6) would not impose an unfunded mandate on State, local, or tribal governments, or on the private sector by exceeding the threshold identified above. These analyses are summarized below. The FAA believes that this rule would impose minimal costs on VFR pilots of GA aircraft, Luke RAPCON and the Federal government. The rule would help reduce the risk of a midair collision in the SATR area, which would result in an increase in aviation safety. As a result, the FAA believes this rule is cost-beneficial. </P>
                <HD SOURCE="HD1">Initial Regulatory Flexibility Determination </HD>
                <P>The Regulatory Flexibility Act of 1980 (Pub. L. 96-354) (RFA) establishes “as a principle of regulatory issuance that agencies shall endeavor, consistent with the objectives of the rule and of applicable statutes, to fit regulatory and informational requirements to the scale of the businesses, organizations, and governmental jurisdictions subject to regulation. To achieve this principle, agencies are required to solicit and consider flexible regulatory proposals and to explain the rationale for their actions to assure that such proposals are given serious consideration.” The RFA covers a wide-range of small entities, including small businesses, not-for-profit organizations, and small governmental jurisdictions. </P>
                <P>
                    Agencies must perform a review to determine whether a rule will have a significant economic impact on a substantial number of small entities. If 
                    <PRTPAGE P="55791"/>
                    the agency determines that it will, the agency must prepare a regulatory flexibility analysis as described in the RFA. 
                </P>
                <P>However, if an agency determines that a rule is not expected to have a significant economic impact on a substantial number of small entities, section 605(b) of the RFA provides that the head of the agency may so certify and a regulatory flexibility analysis is not required. The certification must include a statement providing the factual basis for this determination, and the reasoning should be clear. </P>
                <P>This proposed rule would impose minimal costs on individuals operating GA aircraft in the Luke vicinity under VFR. Most operators of GA aircraft are individuals, not small business entities, and are not included when performing a regulatory flexibility analysis. However, flight schools, as well as GA operators flying for business reasons, are considered small business entities. The FAA assumes affected instructors and operators use aircraft already equipped with two-way radios, and therefore would not incur any extra costs. </P>
                <P>Therefore, the FAA certifies that this proposed rule would not have a significant economic impact on a substantial number of small entities. The FAA requests comments from affected entities on this finding and determination, and requests that comments be supported with clear and relevant documentation. </P>
                <HD SOURCE="HD1">International Trade Impact Assessment </HD>
                <P>The Trade Agreements Act of 1979 (Pub. L. 96-39) prohibits Federal agencies from establishing any standards or engaging in related activities that create unnecessary obstacles to the foreign commerce of the United States. Legitimate domestic objectives, such as safety, are not considered unnecessary obstacles. The statute also requires consideration of international standards and, where appropriate, that they be the basis for U.S. standards. The FAA has assessed the potential effect of this proposed rule and has determined that it would have only a domestic impact and therefore no effect on international trade. </P>
                <HD SOURCE="HD1">Unfunded Mandates Assessment </HD>
                <P>Title II of the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4) requires each Federal agency to prepare a written statement assessing the effects of any Federal mandate in a proposed or final agency rule that may result in an expenditure of $100 million or more (adjusted annually for inflation with the base year 1995) in any one year by State, local, and tribal governments, in the aggregate, or by the private sector; such a mandate is deemed to be a “significant regulatory action.” The FAA currently uses an inflation-adjusted value of $136.1 million in lieu of $100 million. This proposed rule does not contain such a mandate. </P>
                <HD SOURCE="HD1">Executive Order 13132, Federalism </HD>
                <P>The FAA has analyzed this NPRM under the principles and criteria of Executive Order 13132, Federalism. We have determined that this action will not have a substantial direct effect on the states, or the relationship between the national government and the states, or on the distribution of power and responsibilities among the various levels of government. Therefore, we have determined that this final rule does not have federalism implications. </P>
                <HD SOURCE="HD1">Environmental Analysis </HD>
                <P>FAA Order 1050.1E identifies FAA actions that are categorically excluded from preparation of an environmental assessment or environmental impact statement under the National Environmental Policy Act (NEPA) in the absence of extraordinary circumstances. The FAA has determined this proposed rulemaking action qualifies for the categorical exclusion identified in paragraph 312f and involves no extraordinary circumstances. </P>
                <HD SOURCE="HD1">Regulations That Significantly Affect Energy Supply, Distribution, or Use </HD>
                <P>The FAA has analyzed this NPRM under Executive Order 13211, Actions Concerning Regulations that Significantly Affect Energy Supply, Distribution, or Use (May 18, 2001). We have determined that it is not a “significant energy action” under the executive order because it is not a “significant regulatory action” under Executive Order 12866, and it is not likely to have a significant adverse effect on the supply, distribution, or use of energy. </P>
                <HD SOURCE="HD1">Additional Information </HD>
                <HD SOURCE="HD2">Comments Invited </HD>
                <P>The FAA invites interested persons to participate in this rulemaking by submitting written comments, data, or views. We also invite comments relating to the economic, environmental, energy, or federalism impacts that might result from adopting the proposals in this document. The most helpful comments reference a specific portion of the proposal, explain the reason for any recommended change, and include supporting data. To ensure the docket does not contain duplicate comments, please send only one copy of written comments, or if you are filing comments electronically, please submit your comments only one time. </P>
                <P>We will file in the docket all comments we receive, as well as a report summarizing each substantive public contact with FAA personnel concerning this proposed rulemaking. Before acting on this proposal, we will consider all comments we receive on or before the closing date for comments. We will consider comments filed after the comment period has closed if it is possible to do so without incurring expense or delay. We may change this proposal in light of the comments we receive. </P>
                <HD SOURCE="HD2">Availability of Rulemaking Documents </HD>
                <P>You can get an electronic copy of rulemaking documents using the Internet by—</P>
                <P>
                    1.  Searching the Federal eRulemaking Portal (
                    <E T="03">http://www.regulations.gov</E>
                    ); 
                </P>
                <P>
                    2. Visiting the FAA's Regulations and Policies Web page at 
                    <E T="03">http://www.faa.gov/regulations_policies/</E>
                    ; or 
                </P>
                <P>
                    3. Accessing the Government Printing Office's Web page at 
                    <E T="03">http://www.gpoaccess.gov/fr/index.html.</E>
                </P>
                <P>You can also get a copy by sending a request to the Federal Aviation Administration, Office of Rulemaking, ARM-1, 800 Independence Avenue,  SW., Washington, DC 20591, or by calling (202) 267-9680. Make sure to identify the docket number, notice number, or amendment number of this rulemaking. </P>
                <P>You may access all documents the FAA considered in developing this proposed rule, including economic analyses and technical reports, from the Internet through the Federal eRulemaking Portal referenced in paragraph above. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 93 </HD>
                    <P>Air Traffic Control, Airports, Navigation (air)</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment </HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration proposes to amend Chapter I of Title 14, Code of Federal Regulations, as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 93—SPECIAL AIR TRAFFIC RULES </HD>
                    <P>1. The authority citation for part 93 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40103, 40106, 40109, 40113, 44502, 44514, 44701, 44719, 46301. </P>
                    </AUTH>
                    <P>2. Add subpart N to Part 93 to read as follows: </P>
                    <SUBPART>
                        <PRTPAGE P="55792"/>
                        <HD SOURCE="HED">Subpart N—Special Flight Rules in the Vicinity of Luke AFB, AZ. </HD>
                        <SECTION>
                            <SECTNO>§ 93.161 </SECTNO>
                            <SUBJECT>Applicability. </SUBJECT>
                            <P>This subpart prescribes a Special Air Traffic Rule for aircraft conducting VFR operations in the vicinity of Luke Air Force Base, AZ. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 93.163 </SECTNO>
                            <SUBJECT>Description of Area. </SUBJECT>
                            <P>The Luke Air Force Base, Arizona Terminal Area is designated during daylight hours Monday through Friday during flight training operations, other times by Notice to Airmen (NOTAM) as advertised on the local ATIS, as follows: </P>
                            <P>(a) East Sector: </P>
                            <P>(1) South section includes airspace extending from 3,000 feet MSL to the base of the overlaying Phoenix Class B airspace bounded by a line beginning at:</P>
                            <P>Lat. 33°23′56″ N,; Long. 112°28′37″ W; Lat. 33°22′32″ N,; Long. 112°37′14″ W; Lat. 33°25′39″ N,; Long. 112°37′29″ W; Lat. 33°31′55″ N,; Long. 112°30′32″ W; Lat. 33°28′00″ N,; Long. 112°28′41″ W; to point of beginning. </P>
                            <P>(2) South section lower includes airspace extending from 2,100 feet MSL to the base of the overlaying Phoenix Class B airspace, excluding the Luke Class D airspace area bounded by a line beginning at:</P>
                            <P>Lat. 33°28′00″ N,; Long. 112°28′41″ W; Lat. 33°23′56″ N.; Long. 112°28′37″ W; Lat. 33°27′53″ N.; Long. 112°24′12″ W; to point of beginning.</P>
                            <P>(3) Center section includes airspace extending from surface to the base of the overlaying Phoenix Class B airspace, excluding the Luke Class D airspace area bounded by a line beginning at:</P>
                            <P>Lat. 33°42′22″ N,; Long. 112°19′16″ W; Lat. 33°38′40″ N.; Long. 112°14′03″ W; Lat. 33°35′36″ N.; Long. 112°15′36″ W; Lat. 33°27′53″ N,; Long. 112°24′12″ W; Lat. 33°28′00″ N.; Long. 112°28′41″ W; Lat. 33°31′55″ N.; Long. 112°30′32″ W; to point of beginning.</P>
                            <P>(4) The north section includes that airspace extending upward from 3,000 feet MSL to 4,000 feet MSL, bounded by a line beginning at:</P>
                            <P>Lat. 33°42′22″ N.; Long. 112°19′16″ W; Lat. 33°46′58″ N.; Long. 112°16′41″ W; Lat. 33°44′48″ N.; Long. 112°10′59″ W; Lat. 33°38′40″ N.; Long. 112°14′03″ W; to point of beginning.</P>
                            <P>(b) West Sector: </P>
                            <P>(1) The north section includes that airspace extending upward from 3,000 feet MSL to 6,000 feet MSL, bounded by a line beginning at:</P>
                            <P>Lat. 33°51′52″ N.; Long. 112°37′54″ W; Lat. 33°49′34″ N.; Long. 112°23′34″ W; Lat. 33°46′58″ N.; Long. 112°16′41″ W; Lat. 33°42′22″ N.; Long. 112°19′16″ W; Lat. 33°39′27″ N.; Long. 112°22′27″ W; to point of beginning.</P>
                            <P>(2) The south section includes that airspace extending upward from the surface to 6,000 feet MSL, bounded by a line beginning at:</P>
                            <P>Lat. 33°39′27″ N.; Long. 112°22′27″ W; Lat. 33°38′06″ N.; Long. 112°23′51″ W; Lat. 33°38′07″ N.; Long. 112°28′50″ W; Lat. 33°39′34″ N.; Long. 112°31′39″ W; Lat. 33°39′32″ N.; Long. 112°37′36″ W; Lat. 33°51′52″ N.; Long. 112°37′54″ W; to point of beginning. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 93.165 </SECTNO>
                            <SUBJECT>Operations in the Special Air Traffic Rule Area. </SUBJECT>
                            <P>(a) Unless otherwise authorized by Air Traffic Control (ATC), no person may operate an aircraft in flight within the Luke Terminal Area designated in § 93.163 unless— </P>
                            <P>(1) Before operating within the Luke Terminal area, that person establishes radio contact with Luke Radar Approach Control (RAPCON); and </P>
                            <P>(2) That person maintains two-way radio communication with the Luke RAPCON or an appropriate FAA ATC facility while within the designated area. </P>
                            <P>(b) Request for deviation from the provisions of this section must be submitted to the Luke RAPCON at least 24 hours before the proposed operation. </P>
                        </SECTION>
                    </SUBPART>
                    <SIG>
                        <NAME>Hank Krakowski, </NAME>
                        <TITLE>Chief Operating Offficer (COO), Air Traffic Organization.</TITLE>
                    </SIG>
                    <NOTE>
                        <HD SOURCE="HED">Note:</HD>
                        <P>The Following Map Will Not Appear In the Code of Federal Regulations.</P>
                    </NOTE>
                </PART>
                <BILCOD>BILLING CODE 4910-13-P</BILCOD>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="55793"/>
                    <GID>EP26SE08.430</GID>
                </GPH>
                <PRTPAGE P="55794"/>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22568 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-C </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE </AGENCY>
                <CFR>28 CFR Part 20 </CFR>
                <DEPDOC>[FBI Docket No. 118] </DEPDOC>
                <RIN>RIN 1110-AA29 </RIN>
                <SUBJECT>FBI Records Management Division National Name Check Program Section User Fees </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Bureau of Investigation (FBI), Justice. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FBI is authorized to establish and collect fees for providing fingerprint-based and name-based criminal history record information (CHRI) checks and other identification services submitted by authorized users for non-criminal justice purposes including employment and licensing. The fees may include an amount to establish a fund to defray expenses for the automation of criminal justice information services and associated costs. The proposed rule concerns the name-based checks conducted by the Records Management Division (RMD) in the National Name Check Program (NNCP). </P>
                    <P>
                        The rule explains the methodology used to calculate the revised fees and provides a proposed fee schedule. After public comment, a final rule and notice of the final fee schedule will be published in the 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be received on or before November 25, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by Docket No. FBI 118, by either of the following methods: </P>
                    <P>
                        • 
                        <E T="03">Federal Regulations Web site:</E>
                         You may review this regulation on 
                        <E T="03">http://www.regulations.gov</E>
                         and use the comment form for this regulation to submit your comments. You must include Docket No. FBI 118 in the subject box of your message. 
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         You may use the U.S. Postal Service or other commercial delivery services to submit written comments to the FBI, Records Management Division, National Name Check Program Section, 1325 G Street, Room G-300, Washington, DC 20005, Attention: Michael A. Cannon. 
                    </P>
                    <P>To ensure proper handling, please reference Docket No. FBI 118 in your comment. When submitting written comments, please allow for delivery time plus at least two days for internal mail security scanning and delivery. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Michael Cannon, FBI, Records Management Division, National Name Check Program Section, 1325 G Street, Room G-300, Washington, DC 20005, telephone number (202) 220-1198. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <EXTRACT>
                    <FP>I. Posting of Public Comments </FP>
                    <FP>II. Background </FP>
                    <FP>III. Fee Calculation </FP>
                    <FP>IV. Revised Fee Schedule </FP>
                    <FP>V. Administrative </FP>
                    <FP>VI. Regulatory Certifications</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Posting of Public Comments </HD>
                <P>
                    Please note that all comments on the proposed rule are considered part of the public record and made available for public inspection online at 
                    <E T="03">http://www.regulations.gov</E>
                    . Such information includes personal identifying information (such as your name, address, etc.) voluntarily submitted by the commenter. 
                </P>
                <P>If you want to submit personal identifying information (such as your name, address, etc.) as part of your comment, but do not want it to be posted online, you must include the phrase “PERSONAL IDENTIFYING INFORMATION” in the first paragraph of your comment. You must also locate all the personal identifying information you do not want posted online in the first paragraph of your comment and identify what information you want redacted. </P>
                <P>
                    If you want to submit confidential business information as part of your comment but do not want it to be posted online, you must include the phrase “CONFIDENTIAL BUSINESS INFORMATION” in the first paragraph of your comment. You must also prominently identify confidential business information to be redacted within the comment. If a comment has so much confidential business information that it cannot be effectively redacted, all or part of that comment may not be posted on 
                    <E T="03">http://www.regulations.gov.</E>
                </P>
                <P>Personal identifying information identified and located as set forth above will be placed in the agency's public docket file, but not posted online. Confidential business information identified and located as set forth above will not be placed in the public docket file. If you wish to inspect the agency's public docket file in person by appointment, please see the “For Additional Information” paragraph. </P>
                <HD SOURCE="HD1">II. Background </HD>
                <P>For purposes of discussion, FBI user fees may be differentiated by the FBI Division providing the service. The user fees for the National Name Check Program (NNCP) checks provided by the Records Management Division (RMD) are the subject of this rulemaking. Fees for the criminal history record information checks provided by the Criminal Justice Information Services Division (CJIS) are the subject of a separate rulemaking (Docket No. FBI 114, RIN 1110-AA26). The separate CJIS fee rule also proposes to amend 28 CFR 20.31. In the event that the CJIS fee rule is finalized first, the revisions proposed in this rulemaking to section 20.31(e) will be conformed with the changes contained in the CJIS fee rule. </P>
                <P>
                    The rulemaking process provides federal governmental agencies and the public the opportunity to review and comment on the methodology utilized by the FBI to implement its statutory authority to establish and collect fees and the proposed fee schedule, and advises that future fee adjustments will be made by notice published in the 
                    <E T="04">Federal Register</E>
                    . After analysis and response to the comment, a final rule and notice of the fee schedule will be published in the 
                    <E T="04">Federal Register</E>
                    . This rule will be published at Part 20 of 28 CFR. 
                </P>
                <HD SOURCE="HD2">FBI's Legal Authority To Collect Fees </HD>
                <P>The FBI has collected fees for NNCP checks since 1991, under the authority set out in Public Law 101-162. This law authorized the FBI to collect fees to process identification records and name checks for non-criminal justice purposes and to set such fees at a level to include an amount to defray expenses for the automation of fingerprint identification and associated costs. Congress, in Public Law 101-515, subsequently authorized the FBI to establish and collect these fees on a continuing basis. </P>
                <HD SOURCE="HD2">National Name Check Program Services </HD>
                <P>Under Public Law 101-515, the FBI is authorized to charge a fee for non-criminal justice name-based checks for such purposes as immigration, Federal Government employment and security clearance processes. The FBI does not charge a fee for NNCP services performed for criminal justice purposes, which are supported by federal appropriations. </P>
                <HD SOURCE="HD2">Reasons for the Proposed Fee Schedule </HD>
                <P>
                    While the RMD has automated some portions of the NNCP process, the current fees, which have not changed since 1991, do not reflect the expense of personnel time and other costs involved in the analysis of the pertinent information. As explained below, the NNCP disseminates information from the FBI's Central Records System (CRS) in response to requests submitted by 
                    <PRTPAGE P="55795"/>
                    federal agencies, Congressional committees, the federal judiciary, friendly foreign police and intelligence agencies. The CRS contains the FBI's administrative, personnel, and investigative files. The NNCP was established under Executive Order No. 10450, issued on April 27, 1953, 18 FR 2489, which mandated National Agency Checks (NAC) in the background investigation of prospective Government employees. The FBI performs the primary NAC on all U.S. government employees and provides information to more than 40 federal agencies based on fiscal year (FY) 2005 data. The information from the CRS, disseminated under the NNCP, is evaluated by governmental agencies before bestowing privileges such as visas, naturalization or work authorizations under the Immigration and Nationality Act, Public Law 82-414 as amended, and other federal laws. 
                </P>
                <P>The CRS consists of administrative, applicant, criminal, personnel, and other files arranged by subject matter relating to an individual, an organization, or other matter. The CRS records are maintained at FBI Headquarters and FBI Field Offices. The CRS can be accessed through the General Indices, which are arranged in alphabetical order by subject, such as the names of individuals and organizations. </P>
                <P>In 1995, the FBI implemented the Automated Case Support (“ACS”) system to access 105 million records from previous automated systems. The ACS consists of three automated applications that support case management functions for all investigative and administrative cases. The Investigative Case Management application is used to open, assign and track leads and close investigative and administrative cases. The Electronic Case File serves as the central electronic repository for the FBI's official text-based documents. The Universal Index (UNI) provides a complete subject and case index to approximately 99 million records in investigative and administrative cases. The UNI lists the names of individuals or entities, with identifying information such as date of birth and social security number. </P>
                <P>The processing of an NNCP search begins with the search of a person's name in the UNI to locate all instances of the person's name and identifying information in the main and reference files. A main file concerns the subject of an FBI investigation, and a reference file concerns an individual whose name appears in part of an FBI investigation, such as an associate or witness. Over 60 percent of the initial NNCP electronic checks in UNI yield no identifiable information regarding the person and are termed “No record,” and that information is reported to the requesting agency. If the search of UNI yields possibly identifiable information, the NNCP request requires additional review and an additional manual name search is conducted. If identifiable information is located, the records are retrieved and reviewed for possible derogatory information concerning the subject of the NNCP request. The FBI forwards a summary of the derogatory information to the requesting agency. </P>
                <P>By letter, dated August 30, 2007, to all RMD customers using the NNCP for non-criminal justice purposes, the FBI established the proposed fee schedule on an interim basis, effective October 1, 2007. That is the same process the FBI has followed in implementing changes in fees for other non-criminal justice identification services. Although the proposed rule will establish the user fees by notice and comment rulemaking, RMD customers were advised of the revised fees prior to the start of FY 2008, thereby allowing them to prepare for the changes. </P>
                <P>
                    The FBI will continue to analyze its costs in processing searches in the NNCP and will review related fee charges periodically, as recommended by Office of Management and Budget Circular No. A-25, (OMB Circular A-25) User Charges. The proposed rule advises that adjustments to the FBI's fees will be announced by notice in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">III. Fee Calculation </HD>
                <HD SOURCE="HD2">Cost Accounting Standards and Guidelines Used To Calculate the Fee </HD>
                <P>Public Law 101-515 links the user fees charged for processing name checks and fingerprint identification records to the cost of providing these services. Such costs not only include the salaries of employees engaged in providing the services but, in accordance with generally accepted accounting principles, also include such expenses as capital investment, depreciation, automation, and so forth. Congress recognized this by authorizing the FBI to establish user fees at a level to include an amount “to defray expenses for the automation of fingerprint identification and criminal justice information services and associated costs.” </P>
                <P>In the absence of express statutory authority, federal agencies are authorized to establish fees by the Independent Office Appropriation Act of 1952, 31 U.S.C. 9701, which is implemented by specific guidelines in OMB Circular A-25. Since the FBI has specific statutory authority to establish and collect fees under Public Law 101-515, the FBI is not required to follow strictly the mandates of OMB Circular A-25. In establishing the fees set out in this proposed rule, however, the FBI did look to OMB Circular A-25 for guidance. For example, OMB Circular A-25's definition of “full cost” (“all direct and indirect costs to any part of the Federal Government of providing a good, resource, or service”) was used as a model by the FBI in establishing the subject user fees, including direct and indirect personnel costs, physical overhead, and other indirect costs such as material costs, utilities and equipment. </P>
                <HD SOURCE="HD2">Calculation of the Revised Fee </HD>
                <P>
                    The FBI hired a contractor, Grant Thornton LLP., 333 John Carlyle Street, Alexandria, Virginia 22314, (Grant Thornton) to conduct an independent analysis of pertinent costs and to recommend a revised fee schedule for the NNCP checks conducted by RMD. Referencing OMB Circular A-25; the Statement of Federal Financial Accounting Standards (SFFAS-4): Managerial Cost Accounting Concepts and Standards for the Federal Government; and other relevant financial management directives, Grant Thornton developed a cost accounting methodology and related cost models based upon the concept and principles of activity-based costing (ABC). The cost models identified the total resource costs associated with the services provided to RMD customers, including personnel (
                    <E T="03">e.g.</E>
                    , salary and benefits), non-labor (
                    <E T="03">e.g.</E>
                    , material, equipment, and facility) and overhead (
                    <E T="03">e.g.</E>
                    , management and administration) costs, and assigned or allocated these costs to the various service categories using relevant cost drivers. The cost drivers were selected primarily for their strong cause-effect linkages between the resources and the activities and services that consumed them. The unit costs for RMD's NNCP services incorporated in this study were derived from a robust costing network that is based on the principles of ABC, a widely recognized and accepted cost accounting methodology. Grant Thornton generated the revised fee schedule based upon these unit costs. 
                </P>
                <P>
                    The methodology focused on developing full cost information for NNCP's activities and services to provide a basis for the fee recommendations. Generally accepted standards and regulatory guidance were followed, as specified by the Federal Accounting Standards Advisory Board's 
                    <PRTPAGE P="55796"/>
                    (FASAB) Statement Number 4: Managerial Cost Accounting Concepts and Standards for the Federal Government and the Office of Management and Budget's (OMB) Circular A-25: User Charges. FY 2005 costs were used to develop baseline cost information, and additional estimated costs and adjustments were included to estimate resources for FY 2008 and FY 2009. The projected cost information served as the basis for the fee recommendations. 
                </P>
                <P>Grant Thornton developed their cost accounting methodology using the following steps for the non-automation portion of the fee. </P>
                <P>• NNCP services and activities performed for name checks were defined. </P>
                <P>• Operational labor costs were identified and assigned to activities and then to services. </P>
                <P>• Support labor costs were identified and assigned to activities and then to services. </P>
                <P>• Non-labor costs, including appropriate overhead and support costs, were identified and assigned to activities and then to services. </P>
                <P>• Cost estimates were made for FY 2008, when the revised user fees are expected to be implemented. </P>
                <P>• Transaction volumes and trends were analyzed to predict appropriate transaction volumes for fiscal year FY 2008. </P>
                <P>• Finally, using the projected FY 2008 costs and the projected FY 2008 transaction volumes, the projected unit costs for each service were calculated. The recommended user fees were based on these projected unit costs. </P>
                <P>As explained above, under Public Law 101-515, the FBI is also authorized to charge an additional amount for the automation of fingerprint identification and criminal justice information services and associated costs. Although NNCP fees have not included this additional amount to date, the FBI considers the service provided by the NNCP as being a criminal justice information service. The costs associated with enhancing the NNCP, including the automation efforts, were identified and included in the name check fee study reflected in this NPRM. The FBI is therefore proposing to add an automation surcharge to the NNCP fee pursuant to Public Law 101-515. The estimated costs for these automation efforts were based on best available information regarding planned IT investments. The projected FY 2008 and FY 2009 volumes were then used to calculate the unit costs for this portion of the fee. Once the unit costs were calculated, Grant Thornton generated the revised fee schedule. The FBI then independently reviewed the Grant Thornton recommendations, compared them to current fee calculations and plans for future services, and determined that the revised schedules were both objectively reasonable and in consonance with the underlying legal authorities. </P>
                <HD SOURCE="HD2">Overview of the Costs Included in the Fee Calculation </HD>
                <P>The fee calculation was produced by gathering the labor and non-labor costs of those divisions of the FBI that directly or indirectly support the provision of the NNCP name check services, and then using various drivers to assign those costs to the identified activities. The activities were then assigned to the specific name check service. The ABC model examined in detail only those costs which were related to the name check services. These services included both the criminal justice and law enforcement and the non-criminal justice identification services performed by the NNCP. The discussion below is limited to those costs in the ABC model which were assigned to name check services that are supported by the user fees. In other words, even though the ABC model calculated unit costs for all NNCP name checks, the costs for processing criminal justice name checks will not be discussed in this regulation since they are funded with appropriations and not with user fees. </P>
                <P>The costs for providing the fee-supported name check services include the personnel costs for both direct and indirect support, as well as non-labor costs such as travel, training, rent, equipment, utilities, printing, contract support, and supplies. In addition, depreciation for existing non-automation assets were included per OMB Circular A-25 guidance. Finally, portions of the FBI costs for workers compensation, unemployment compensation, and the judgment fund used to pay judgments against the United States where appropriations have not otherwise been provided were included. These costs were derived from the FBI financial systems and other relevant information provided by FBI personnel. The FY 2008 predicted costs were obtained by adding an inflation factor for labor and other non-labor expenses and identifying other expected changes in cost. The OMB pay raise and inflation factors provided in OMB Circular A-11, Preparation, Submission, and Execution of an Agency Budget, were used. The costs associated with providing the services do not include any of the automation costs which instead were based on capital investment planning for the automation portion of the fee described below. The costs for the additional charge for automation were based on the most recent NNCP estimates for planned systems automation and enhancement. </P>
                <HD SOURCE="HD1">IV. Revised Fee Schedule </HD>
                <HD SOURCE="HD2">Proposed Changes to the Fee Schedule </HD>
                <P>The current NNCP fee schedule services are: </P>
                <P>• Electronic (Batch Processed) </P>
                <P>• File Review and Analysis </P>
                <P>• Manual (Paper-Based Request) </P>
                <P>• Expedite (Paper-Based Request) </P>
                <P>FBI proposes a tiered fee structure that maintains the distinction between requests completed during the automated batch processing and those that must go on for additional file review and analysis (formerly referred to as indices popular). However, the recommended fee structure does maintain a distinction between requests submitted electronically or on paper. Manual requests represent approximately 3% of name checks processed, and NNCP is undertaking efforts to encourage customers to submit all name check requests electronically. </P>
                <P>The proposed fee structure is: </P>
                <P>• Electronic (Batch Processed) </P>
                <P>• File Review/Analysis (Routine) </P>
                <P>• File Review/Analysis (Expedited) </P>
                <FP>While there is not an expedite fee for batch processing (they are typically completed within a few days), the proposed fee structure does distinguish between routine processing and expedited processing for name checks that require additional review and analysis. The FBI receives some requests for expedited processing of name checks but does not currently charge an additional fee for the expedited service (except for a small number of manual requests). Expedited requests receive priority processing, and the expedited processing fee accounts for this difference in prioritization by charging the customer requesting expedited service a higher amount to reflect the preferential treatment and shorter processing time. </FP>
                <HD SOURCE="HD2">Discussion of Proposed Changes to the Fee Schedule </HD>
                <P>The fee structure described above was proposed for the following reasons: </P>
                <P>
                    • Reflects difference in cost. There is a significant difference between the unit cost of automated batch processing and file review and analysis. The recommended fee structure reflects this difference by charging a separate fee for these two phases of the name check process. 
                    <PRTPAGE P="55797"/>
                </P>
                <P>• Reflects customer choice. The recommended fee structure has separate fees for routine and expedited processing of name checks. This reflects a customer choice regarding which level of service to request. </P>
                <P>• Move toward all electronic requests. The NNCP intends to have all name check requests provided by their customers in electronic format. The NNCP will develop a web interface to allow the customers to enter the appropriate data into the NNCP system rather than mail a hard copy request. Therefore, the recommended fee structure does distinguish between electronic and manual submission of name check requests. </P>
                <P>• Less administrative burden. The recommended fee structure has fewer separate services so there are fewer services/fees to bill. </P>
                <P>As mentioned previously, customers receiving expedited processing should be charged a higher fee compared to routine processing. Customers who receive expedited processing derive additional benefit because they receive preferential treatment; requests for routine processing must wait longer because the expedited requests get moved up in the queue. </P>
                <P>The Independent Offices Appropriation Act (IOAA) serves as a government-wide authority on fee setting in the federal government. According to the IOAA, a user charge shall be based on: </P>
                <P>• Costs to the Government </P>
                <P>• Value of the service or thing to the recipient </P>
                <P>• Public policy or interest served </P>
                <P>• Other relevant facts </P>
                <P>Regarding the value criterion, requests that receive expedited processing receive higher value when compared to those that receive routine processing. The expedited processing fee accounts for this added value by charging a higher fee because the request receives preferential treatment and is processed in a shorter period of time. Consideration was given to the difference in processing time for routine and expedited requests to calculate the expedite fee. This data measured the average number of days involved in each type of request from the date received to the date finalized. This difference in processing time served as the basis for adjusting the fees for routine and expedited processing. </P>
                <HD SOURCE="HD2">Detail of the Costs Used To Calculate the Fee </HD>
                <P>The costs were calculated based on the cost of providing NNCP name checks using the ABC model constructed by Grant Thornton. The costs include labor costs, non-labor costs (including unfunded personnel and judgment fund costs), automation costs; and general overhead and support costs. These costs are discussed in more detail below. </P>
                <P>The cost structure reflects the type of cost and organizational structure of the NNCP and other FBI units involved in providing name check services. The NNCP costs are comprised of the following categories: </P>
                <P>Labor—includes personnel compensation (salary and benefits) for direct costs. </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Center </CHED>
                        <CHED H="1">FY2008 </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Name Check Center </ENT>
                        <ENT>$9,982,910 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Other Records Management Units </ENT>
                        <ENT>908,046 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Field Office Support </ENT>
                        <ENT>8,278,415 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Information Technology Support </ENT>
                        <ENT>233,569 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Finance Division Support </ENT>
                        <ENT>64,247 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Office of General Counsel </ENT>
                        <ENT>2,535,942 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Document Scanning Support </ENT>
                        <ENT>2,923,911 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>24,927,040 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>Non-labor includes direct and indirect non-labor expense data for the Name Check and RMD front office, contractor support, and depreciation. </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Center </CHED>
                        <CHED H="1">FY2008 </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Name Check/RMD </ENT>
                        <ENT>$2,226,367 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Batch Processing Enhancement </ENT>
                        <ENT>310,000 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Contractor Support </ENT>
                        <ENT>12,318,813 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Depreciation/Equipment Replacement </ENT>
                        <ENT>115,965 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Document Scanning/Consumables </ENT>
                        <ENT>1,836,257 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>16,807,402 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>Bureau overhead/support includes indirect costs to provide joint or common services to NNCP. </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Center </CHED>
                        <CHED H="1">FY2008 </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Office of the Chief Information Officer </ENT>
                        <ENT>$1,579,600 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Human Resources </ENT>
                        <ENT>62,2626 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Finance </ENT>
                        <ENT>85,428 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Federal Employees' Compensation Act </ENT>
                        <ENT>49,446 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Judgment Fund </ENT>
                        <ENT>7,005 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Security </ENT>
                        <ENT>445,185 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Telecommunications </ENT>
                        <ENT>196,212 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Inspection </ENT>
                        <ENT>52,361 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rent </ENT>
                        <ENT>2,146,320 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Training and Development </ENT>
                        <ENT>11,556 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Shipping </ENT>
                        <ENT>101,264 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>4,736,639 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">Additional Charge for Automation </HD>
                <P>The FBI is authorized by law (Pub. L. 101-515) to charge an additional amount for each name check to defray expenses for automation and associated costs. Under this authority, the additional amount may be placed in a separate account and retained until expended. The proposed amount of the additional charge is currently estimated to be $1.00 per name check. The additional amount was calculated by dividing the estimated two-year total cost of planned Information Technology (IT) investments by the estimated two-year volume of name check requests. Current estimates total approximately $7.2 million to be invested in system enhancements during FY 2008 and FY 2009. The tables below provide more detailed information on the planned IT investments. The total is divided by an estimated 2-year volume of 7.15 million name check requests to arrive at an additional amount of $1.00 per name check. </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s40,16,16,16">
                    <TTITLE>Summary of Spending for Project (Investment) Stages </TTITLE>
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">Fiscal year 2008 </CHED>
                        <CHED H="1">Fiscal year 2009 </CHED>
                        <CHED H="1">Total </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Planning </ENT>
                        <ENT>$1,200,000 </ENT>
                        <ENT>$0 </ENT>
                        <ENT>$1,200,000 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Acquisition </ENT>
                        <ENT>3,000,000 </ENT>
                        <ENT>3,000,000 </ENT>
                        <ENT>6,000,000 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>4,200,000 </ENT>
                        <ENT>3,000,000 </ENT>
                        <ENT>7,200,000 </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="55798"/>
                <HD SOURCE="HD2">Volumes Used To Calculate the Fee</HD>
                <P>The unit cost and proposed fees are based on the following projected volumes for FY 2008:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,10">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Product/service </CHED>
                        <CHED H="1">
                            Projected 
                            <LI>volume </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Electronic (Batch Process) </ENT>
                        <ENT>3,471,638 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">File Review/Analysis (Routine) </ENT>
                        <ENT>1,186,891 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">File Review/Analysis (Expedited) </ENT>
                        <ENT>209,451 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>These projections were based on analysis of FY 2005 and FY 2006 workload volume, along with expected workload increases for FY 2008. Significant factors that influenced the projections were continued work on pending cases and expected workload increase from Homeland Security Presidential Directive (HSPD)—12 requirements. </P>
                <P>Projected costs and workload were used to calculate the proposed fees provided in the table below. The fees shown below include the additional $1.00 charge previously discussed. Some NNCP name checks (criminal justice and law enforcement) can not be billed to customers, and the revenue estimates provided below are based on estimated billable volume. The billable volume and revenue estimates are based on the following assumptions: </P>
                <P>• Under the new fee structure, 15% of name checks processed after the batch process will be expedited requests. This is based on an analysis of FY 2006 workload data. </P>
                <P>• The revenue estimate assumes that 85% of NNCP requests are billable to customers. As provided in the authorizing language, name checks performed for certain purposes are exempt from the fee. The cost of the remaining fee-exempt requests is not recovered through fees charged for billable work but is paid from FBI salary and expense appropriation. </P>
                <P>• Unit costs are rounded up to the next $0.25. </P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s100,15,7,15">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Product/service </CHED>
                        <CHED H="1">
                            Annual billable 
                            <LI>volume </LI>
                        </CHED>
                        <CHED H="1">Fee </CHED>
                        <CHED H="1">Revenue </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Electronic (Batch Process) </ENT>
                        <ENT>1,1918,080 </ENT>
                        <ENT>$1.50 </ENT>
                        <ENT>$2,877,120 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">File Review/Analysis (Routine) </ENT>
                        <ENT>1,008,857 </ENT>
                        <ENT>29.50 </ENT>
                        <ENT>29,761,282 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">File Review/Analysis (Expedited) </ENT>
                        <ENT>178,033 </ENT>
                        <ENT>56.00 </ENT>
                        <ENT>9,969,848 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>42,608,250 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>The following table shows the amount that each cost category (labor, non-labor, and overhead/support) contributes to the fee. The cost of batch processing is not included in the subtotal unit cost for File Review/Analysis; however, batch processing is performed prior to the File Review/Analysis service and is included in the proposed fee. This table also shows the adjustment made for the expedited fee. </P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s100,20,20,20">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Cost category/adjustment </CHED>
                        <CHED H="1">
                            Electronic 
                            <LI>(batch process) </LI>
                        </CHED>
                        <CHED H="1">
                            File review/analysis 
                            <LI>(routine) </LI>
                        </CHED>
                        <CHED H="1">
                            File review/analysis 
                            <LI>(expedite) </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Labor </ENT>
                        <ENT>$0.21 </ENT>
                        <ENT>$17.33 </ENT>
                        <ENT>$17.33 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Non-Labor </ENT>
                        <ENT>0.04 </ENT>
                        <ENT>11.71 </ENT>
                        <ENT>11.71 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Overhead/Support </ENT>
                        <ENT>0.25 </ENT>
                        <ENT>2.98 </ENT>
                        <ENT>2.98 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Subtotal Unit Cost </ENT>
                        <ENT>0.50 </ENT>
                        <ENT>32.02 </ENT>
                        <ENT>32.02 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Expedite Amount </ENT>
                        <ENT>N/A </ENT>
                        <ENT>($4.05) </ENT>
                        <ENT>22.27 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Adjusted Unit Cost </ENT>
                        <ENT>0.50 </ENT>
                        <ENT>27.97 </ENT>
                        <ENT>54.30 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Round up to $0.25 </ENT>
                        <ENT>0.00 </ENT>
                        <ENT>0.03 </ENT>
                        <ENT>0.21 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Batch Processing </ENT>
                        <ENT>N/A </ENT>
                        <ENT>0.50 </ENT>
                        <ENT>0.50 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Additional Charge </ENT>
                        <ENT>1.00 </ENT>
                        <ENT>1.00 </ENT>
                        <ENT>1.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Proposed Fee </ENT>
                        <ENT>1.50 </ENT>
                        <ENT>29.50 </ENT>
                        <ENT>56.00 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>As noted above, the FBI established this proposed fee schedule on an interim basis, effective October 1, 2007. The following table shows the amounts by which the fees were changed. Fee classes remained essentially the same, with the exception that manual submissions and expedited processing requests were consolidated into a single class. Under the interim fee schedule, the fee was increased only 10 cents for users submitting electronic requests that are limited to batch processing (from $1.40 to $1.50). Such users constituted more than 60 percent of the billable name checks at that time. The fee increases for name checks involving non-electronic submissions and other special services were more substantial because of the higher cost for processing manual submissions and the cost for expediting responses ahead of routine transactions. </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s75,12,12,12">
                    <TTITLE>Summary of Fee Changes </TTITLE>
                    <BOXHD>
                        <CHED H="1">Service </CHED>
                        <CHED H="1">Previous fee </CHED>
                        <CHED H="1">Proposed fee </CHED>
                        <CHED H="1">
                            Total fee 
                            <LI>increase </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">Electronic Submission </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Batch Process Only </ENT>
                        <ENT>$1.40 </ENT>
                        <ENT>$1.50 </ENT>
                        <ENT>$0.10 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Batch + File Review </ENT>
                        <ENT>10.65 </ENT>
                        <ENT>29.50 </ENT>
                        <ENT>18.85 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Manual Submission </ENT>
                        <ENT>12.00 </ENT>
                        <ENT>56.00 </ENT>
                        <ENT>44.00 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Expedited Submission </ENT>
                        <ENT>22.65 </ENT>
                        <ENT>56.00 </ENT>
                        <ENT>33.35 </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="55799"/>
                <P>
                    The FBI will continue to analyze its costs and will review related fee charges periodically, as recommended by Office of Management and Budget Circular No. A-25, User Charges (OMB Circular A-25). The proposed rule advises that future adjustments to the FBI's fees will be announced by notice in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">V. Administrative </HD>
                <HD SOURCE="HD2">Consultations With Interested Federal Agencies </HD>
                <P>The FBI has provided information about this proposed rule to the largest three customers by volume of submissions, the United States Citizenship and Immigration Services, the Office of Personnel Management, and the Department of State. The FBI will develop standards of performance and timeliness with these three federal customers and provide performance information against the standards. The FBI will develop plans for management action in the event the standards agreed upon are not met, working with customer agencies. As appropriate, the FBI may pursue similar arrangements with its other federal customers. </P>
                <HD SOURCE="HD2">Effective Date for the New Fees </HD>
                <P>
                    The proposed rule explains the methodology used to calculate the FBI revised fees, provides a proposed fee schedule, and advises that future fee adjustments will be made by notice published in the 
                    <E T="04">Federal Register</E>
                    . After public comment, a final rule and notice of the final fee schedule will be published concurrently in the 
                    <E T="04">Federal Register</E>
                    . This new schedule will be put into effect 60 days following publication of the notice 
                </P>
                <HD SOURCE="HD2">Notice of the New Fee Schedule </HD>
                <P>
                    Any changes to the Fee Schedule will be published in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">VI. Regulatory Certifications </HD>
                <HD SOURCE="HD2">Regulatory Flexibility Act </HD>
                <P>When an agency issues a rulemaking proposal, the Regulatory Flexibility Act (RFA) requires the agency to “prepare and make available for public comment an initial regulatory flexibility analysis” which will “describe the impact of the proposed rule on small entities.” (5 U.S.C. 603(a)). Section 605 of the RFA allows an agency to certify, in lieu of preparing an analysis, that the proposed rulemaking is not expected to have significant economic impact on a substantial number of small entities. </P>
                <P>This proposed rule does not directly or indirectly impact any small entity, as defined by the RFA to include small businesses, small organizations, and small governmental jurisdictions. The fees for providing name-based checks of the FBI Central Records System are imposed upon the Federal agencies authorized to request these checks, therefore, there is no direct or indirect impact on small entities, as federal agencies do not fall within the definition of a small entity. Accordingly, the Director of the FBI hereby certifies that this rule will not have a significant economic impact on a substantial number of small entities. </P>
                <HD SOURCE="HD2">Executive Order 12866 (Regulatory Planning and Review) </HD>
                <P>This regulation has been drafted and reviewed in accordance with Executive Order 12866, Regulatory Planning and Review section 1(b), Principles of Regulation. The FBI has determined that this rule is a significant regulatory action under Executive Order 12866, section 3(f), Regulatory Planning and Review, and accordingly this rule has been reviewed by the OMB. </P>
                <HD SOURCE="HD2">Executive Order 12988 (Civil Justice Reform) </HD>
                <P>This proposed rule meets the applicable standards set forth in sections 3(a) and 3(b)(2) of Executive Order 12988. </P>
                <HD SOURCE="HD2">Executive Order 13132 (Federalism) </HD>
                <P>This proposed rule will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. The fees for providing these name-based checks for non-criminal justice purposes are imposed upon the individual subject of the background check or are absorbed by the federal agencies submitting the requests. Therefore, in accordance with Executive Order 13132, it is determined that this rule has no federalism implications and does not warrant the preparation of a Federalism Assessment. </P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act of 1995 </HD>
                <P>This proposed rule does not contain a mandate that will result in the expenditure by state, local, and tribal governments (in the aggregate) or by the private sector of $100 million or more in any one year, and it will not significantly or uniquely affect small governments. Therefore, no actions were deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995. </P>
                <HD SOURCE="HD2">Small Business Regulatory Enforcement Fairness Act of 1996 </HD>
                <P>This proposed rule is not a major rule as defined by section 804 of the Small Business Regulatory Enforcement Fairness Act of 1996. This proposed rule will not result in an annual effect on the U.S. economy of $100 million or more; a major increase in costs or prices; or significant adverse effects on competition, employment, investment, productivity, innovation, or on the ability of U.S.-based companies to compete with foreign-based companies in domestic and export markets. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 28 CFR Part 20 </HD>
                    <P>Classified information, Crime, Intergovernmental relations, Investigations, Law enforcement, Privacy.</P>
                </LSTSUB>
                <P>Accordingly, for the reasons set forth in the preamble, part 20 of chapter I of Title 28 of the Code of Federal Regulations is amended as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 20—CRIMINAL JUSTICE INFORMATION SYSTEMS </HD>
                    <P>1. The authority citation for part 20 is revised to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            28 U.S.C. 534; Public Law 92-544, 86 Stat. 1115; 42 U.S.C. 3711, 
                            <E T="03">et seq.</E>
                            , Public Law 99-169, 99 Stat. 1002, 1008-1011, as amended by Public Law 99-569, 100 Stat. 3190, 3196; Public Law 101-515, as amended by Public Law 104-99, set out in the notes to 28 U.S.C. 534.
                        </P>
                    </AUTH>
                    <P>2. Section 20.3 is amended by adding paragraphs (t) and (u) to read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 20.3 </SECTNO>
                        <SUBJECT>Definitions. </SUBJECT>
                        <STARS/>
                        <P>
                            (t) 
                            <E T="03">Central Records System</E>
                             or CRS encompasses all centralized records of FBI Headquarters, field offices and Legal Attache offices. See the CRS Privacy Act System Notice periodically published in the 
                            <E T="04">Federal Register</E>
                             for further details. 
                        </P>
                        <P>
                            (u) 
                            <E T="03">National Name Check Program</E>
                             or NCP is responsible for disseminating information from the FBI CRS in response to requests submitted by federal agencies. 
                        </P>
                        <P>3. Section 20.30 is revised to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 20.30 </SECTNO>
                        <SUBJECT>Applicability. </SUBJECT>
                        <P>
                            The provisions of this subpart of the regulations apply to the III System, the FIRS, and the CRS, and to duly authorized local, state, tribal, federal, foreign, and international criminal justice agencies to the extent that they utilize the services of the III System, the FIRS or the CRS. This subpart is applicable to both manual and automated criminal history records. 
                            <PRTPAGE P="55800"/>
                        </P>
                        <P>4. Section 20.31 is amended by adding paragraphs (e) and (f) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 20.31 </SECTNO>
                        <SUBJECT>Responsibilities. </SUBJECT>
                        <STARS/>
                        <P>(e) The FBI may routinely establish and collect fees for non-criminal justice identification services as authorized by federal law. These fees apply to federal, state and any other authorized entities requesting name checks for non-criminal justice purposes. </P>
                        <P>(1) The Director of the FBI shall review the amount of the fee periodically, but not less than every four years, to determine the current cost of processing name checks for non-criminal justice purposes. </P>
                        <P>(2) Fee amounts and any revisions thereto shall be determined by current costs, using a method of analysis consistent with widely accepted accounting principles and practices, and calculated in accordance with the provisions of 31 U.S.C. 9701 and other federal law as applicable. </P>
                        <P>
                            (3) Fee amounts and any revisions thereto shall be published as a notice in the 
                            <E T="04">Federal Register</E>
                            . 
                        </P>
                        <P>(f) The FBI will collect a fee for providing non-criminal name-based background checks of the FBI Central Records System through the National Name Check Program pursuant to the authority in Public Law 101-515 and in accordance with paragraphs (e)(1), (2) and (3) of this section. </P>
                    </SECTION>
                    <SIG>
                        <DATED>Dated: September 18, 2008. </DATED>
                        <NAME>Robert S. Mueller, III, </NAME>
                        <TITLE>Director, Federal Bureau of Investigation.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22710 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4410-02-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR </AGENCY>
                <SUBAGY>Mine Safety and Health Administration </SUBAGY>
                <CFR>30 CFR Parts 56, 57, and 66 </CFR>
                <RIN>RIN 1219-AB41 </RIN>
                <SUBJECT>Alcohol- and Drug-Free Mines: Policy, Prohibitions, Testing, Training, and Assistance </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Mine Safety and Health Administration (MSHA), Labor. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; notice of public hearing; extension of comment period. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Mine Safety and Health Administration (MSHA) will hold a public hearing on its proposed rule to amend the existing metal and nonmetal standards for the possession and use of intoxicating beverages and narcotics and make the new standard applicable to all mines. The proposed rule would also require those who violate the prohibitions to be removed from the performance of safety-sensitive job duties until they successfully complete the recommended treatment and their alcohol- and drug-free status is confirmed by a return-to-duty test. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>All comments must be received by midnight Eastern Daylight Savings Time on October 29, 2008. </P>
                    <P>
                        MSHA will hold a public hearing on October 14, 2008. The 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this notice includes details of the hearing. 
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments must be clearly identified with “RIN 1219-AB41” and may be sent by any of the following methods: </P>
                    <P>
                        (1)
                        <E T="03">Federal e-Rulemaking Portal: http://www.regulations.gov</E>
                        . Follow the instructions for submitting comments. 
                    </P>
                    <P>
                        (2) 
                        <E T="03">Electronic mail: zzMSHA-comments@dol.gov</E>
                        . Include “RIN 1219-AB41” in the subject line of the message. 
                    </P>
                    <P>
                        (3) 
                        <E T="03">Facsimile:</E>
                         202-693-9441. Include “RIN 1219-AB41” in the subject line of the message. 
                    </P>
                    <P>
                        (4) 
                        <E T="03">Regular Mail:</E>
                         MSHA, Office of Standards, Regulations, and Variances, 1100 Wilson Boulevard, Room 2350, Arlington, Virginia 22209-3939. 
                    </P>
                    <P>
                        (5) 
                        <E T="03">Hand Delivery or Courier:</E>
                         MSHA, Office of Standards, Regulations, and Variances, 1100 Wilson Boulevard, Room 2350, Arlington, Virginia. Sign in at the receptionist's desk on the 21st floor. 
                    </P>
                    <P>
                        Comments can be accessed electronically at 
                        <E T="03">http://www.msha.gov</E>
                         under the Rules and Regs link. MSHA will post all comments on the Internet without change, including any personal information provided. 
                    </P>
                    <P>Comments may also be reviewed at the Office of Standards, Regulations, and Variances, 1100 Wilson Boulevard, Room 2350, Arlington, Virginia. Sign in at the receptionist's desk on the 21st floor. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Patricia W. Silvey, 
                        <E T="03">patricia.silvey@dol.gov</E>
                         (E-mail), 202-693-9440 (Voice). 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <P>
                    On September 8, 2008 (73 FR 52136), MSHA published a proposed rule in the 
                    <E T="04">Federal Register</E>
                     that would amend the existing metal and nonmetal standards concerning the use of intoxicating beverages and narcotics and would make the new standard applicable to all mines. The proposed rule would designate the substances that cannot be possessed on mine property or used while performing safety-sensitive job duties, except when used according to a valid prescription. Mine operators would be required to establish an alcohol- and drug-free mine program, which includes a written policy, employee education, supervisory training, alcohol- and drug-testing for miners that perform safety-sensitive job duties and their supervisors, and referrals for assistance for miners and supervisors who violate the policy. The proposed rule would also require those who violate the prohibitions to be removed from the performance of safety-sensitive job duties until they successfully complete the recommended treatment and their alcohol- and drug-free status is confirmed by a return-to-duty test. 
                </P>
                <HD SOURCE="HD1">II. Public Hearing </HD>
                <P>MSHA will hold a public hearing on the proposed rule. The public hearing will begin at 9 a.m. Eastern Daylight Savings Time (EDST). The public hearing will be held via Web cast at three locations. The hearing will end at 5 p.m. EDST, or after the last speaker speaks. The hearing will be held on the following date at the locations and times indicated: </P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs72,r100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Date </CHED>
                        <CHED H="1">Location </CHED>
                        <CHED H="1">Contact information </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">October 14, 2008 </ENT>
                        <ENT>
                            <E T="03">Via Webcast:</E>
                             9 a.m. Eastern Daylight Savings Time 
                        </ENT>
                        <ENT>Office of Standards, Regulations and Variances 202-693-9440.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Cisco Washington DC, 1300 Pennsylvania Avenue, NW., Suite 250, Washington, DC 20004, POC: Mic Keith 202-354-2904 (main bldg phone)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">October 14, 2008 </ENT>
                        <ENT>
                            <E T="03">Via Webcast:</E>
                             9 a.m. Eastern Daylight Savings Time 
                        </ENT>
                        <ENT>Office of Standards, Regulations and Variances 202-693-9440.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="55801"/>
                        <ENT I="22"> </ENT>
                        <ENT>Cisco Pittsburgh, 323 North Shore Drive, Pittsburgh, PA 15212, POC: Tom Schweizer, 412-237-6200 (main bldg phone) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">October 14, 2008 </ENT>
                        <ENT>
                            <E T="03">Via Webcast:</E>
                             7 a.m. Mountain Daylight Savings Time
                        </ENT>
                        <ENT>Office of Standards, Regulations and Variances 202-693-9440.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Cisco Englewood (Denver), 9155 East Nichols Avenue, Suite 400, Englewood, Colorado 80112, 720-875-2900 (main bldg phone), POC: Shannon Gonzales </ENT>
                    </ROW>
                </GPOTABLE>
                <P>Persons may participate via audio only at the following locations. At these locations persons will not be able to make oral presentations. </P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs72,r100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Date </CHED>
                        <CHED H="1">Location </CHED>
                        <CHED H="1">Contact information </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">October 14, 2008 </ENT>
                        <ENT>
                            <E T="03">Via Audio:</E>
                             9 a.m. Eastern Daylight Savings Time 
                        </ENT>
                        <ENT>Office of Standards, Regulations and Variances 202-693-9440.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>The National Mine Health and Safety Academy, 1301 Airport Road, Beaver, WV 25813 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">October 14, 2008 </ENT>
                        <ENT>
                            <E T="03">Via Audio:</E>
                             8 a.m. Central Daylight Savings Time 
                        </ENT>
                        <ENT>Office of Standards, Regulations and Variances 202-693-9440.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Coal Mine Safety and Health, Coal District 11 Office, 135 Gemini Circle, Suite 213, Birmingham, AL 35209 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>Persons will need an ID to enter all locations and may be subject to a security check. </P>
                <P>
                    The hearing will begin with an opening statement from MSHA, followed by an opportunity for members of the public to make oral presentations. Requests to speak at the hearing should be made at least 5 days prior to the hearing date. Requests to speak may be made by telephone (202-693-9440), facsimile (202-693-9441), electronic mail 
                    <E T="03">zzMSHA-comments@dol.gov</E>
                     or mail (MSHA, Office of Standards, Regulations, and Variances, 1100 Wilson Boulevard, Room 2350, Arlington, Virginia 22209-3939). Because members of the public will be able to make oral presentations via videoconference at several locations, for scheduling purposes, MSHA encourages all parties wishing to speak to notify the Agency in advance. 
                </P>
                <P>Any unallocated time at the end of the hearing will be made available to persons making same-day requests to speak. Same-day requestors will speak in the order that they sign in at the hearing. At the discretion of the presiding official, the time allocated to each speaker for their presentation may be limited. Speakers and other attendees may also present information to the MSHA panel for inclusion in the rulemaking record. </P>
                <P>
                    The hearing will be conducted in an informal manner. Formal rules of evidence and cross examination will not apply. The hearing panel may ask questions of speakers. Speakers may ask questions of the hearing panel. MSHA will make a transcript of the hearing, post it on MSHA's Web site 
                    <E T="03">http://www.msha.gov</E>
                    , and include it in the rulemaking record. A link to the complete webcast will be placed on MSHA's Web site several days after the hearing. 
                </P>
                <P>MSHA will accept post-hearing written comments and data for the record from any interested party, including those not presenting oral statements, by midnight Eastern Daylight Savings Time on October 29, 2008. </P>
                <SIG>
                    <DATED>Dated: September 22, 2008. </DATED>
                    <NAME>Richard E. Stickler, </NAME>
                    <TITLE>Acting Assistant Secretary for Mine Safety and Health.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22679 Filed 9-23-08; 4:15 pm] </FRDOC>
            <BILCOD>BILLING CODE 4510-43-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration </SUBAGY>
                <CFR>49 CFR Part 571 </CFR>
                <DEPDOC>[Docket No. NHTSA-2006-24488] </DEPDOC>
                <SUBJECT>Federal Motor Vehicle Safety Standards; Low Speed Vehicles </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Denial of petition for reconsideration. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document responds to a petition for reconsideration of our 2006 final rule increasing the maximum gross vehicle weight rating (GVWR) for low speed vehicles (LSVs) to 3,000 pounds. The agency established a GVWR limit (initially set at 2,500 pounds) in order to provide an objective means to delineate between vehicles for which the limited LSV requirements are appropriate and those that can be designed to meet the full set of Federal motor vehicle safety standards. Our 2006 final rule increased the limit to 3,000 pounds, in order to accommodate the heavier weight of load-carrying LSVs and electric batteries. A petition for reconsideration was received from Electronic Transportation Applications (ETA), which seeks to further increase the GVWR limit for electric-powered LSVs to 4,000 pounds, as well as to add additional regulations to regulate braking performance and tire specifications. The agency is denying the petitioner's request for the reasons discussed in this document. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P SOURCE="NPAR">
                        <E T="03">For technical issues:</E>
                         Gayle Dalrymple, Office of Crash Avoidance Standards, NVS-123, National Highway Traffic Safety Administration. Telephone: 202-366-5559. 
                        <E T="03">Facsimile:</E>
                         202-493-2739, e-mail 
                        <E T="03">gayle.dalrymple@nhtsa.dot.gov.</E>
                    </P>
                    <P>
                        <E T="03">For legal issues:</E>
                         Mr. Ari J. Scott, NHTSA Office of the Chief Counsel. Telephone: (202) 366-2992. Facsimile: (202) 366-3820, e-mail 
                        <E T="03">ari.scott@nhtsa.dot.gov.</E>
                    </P>
                    <P>Both officials can be reached by mail at the National Highway Traffic Safety Administration, 1200 New Jersey Avenue, SE., Washington, DC 20590. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <EXTRACT>
                    <HD SOURCE="HD1">Table of Contents </HD>
                    <FP SOURCE="FP-2">I. Background of the LSV Rulemakings </FP>
                    <FP SOURCE="FP-2">II. Petition for Reconsideration </FP>
                    <FP SOURCE="FP-2">
                        III. Agency Response 
                        <PRTPAGE P="55802"/>
                    </FP>
                    <FP SOURCE="FP1-2">a. Rationale for 3,000 Pound GVWR </FP>
                    <FP SOURCE="FP1-2">i. Limitation of LSVs to Appropriate Vehicles </FP>
                    <FP SOURCE="FP1-2">ii. Importation of Foreign Vehicles as LSVs </FP>
                    <FP SOURCE="FP1-2">b. Technology-Neutral Regulation </FP>
                    <FP SOURCE="FP-2">IV. Conclusion</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Background of the LSV Rulemakings </HD>
                <P>
                    NHTSA established Federal Motor Vehicle Safety Standard (FMVSS) No. 500, “Low speed vehicles,” in 1998 in response to the rising use of “golf cars” and neighborhood electric vehicles (NEVs). 
                    <E T="03">See</E>
                     63 FR 33194. This new FMVSS and vehicles class definition responded to the growing public interest in using small vehicles to make short trips for shopping, social, and recreational purposes, primarily within retirement or other planned, self-contained communities. The definition of an LSV established in that rulemaking was, “a 4-wheeled motor vehicle, other than a truck, whose speed attainable in 1.6 km (1 mile) is more than 32 kilometers per hour (20 miles per hour) and not more than 40 kilometers per hour (25 miles per hour) on a paved level surface. 
                </P>
                <P>
                    In 2005, NHTSA published a final rule amending the definition of LSVs by dropping the restriction on trucks, and instead establishing a 2,500 pound maximum GVWR. 
                    <E T="03">See</E>
                     70 FR 48313. This allowed small vehicles designed for work-related applications within the intended communities, such as landscaping or delivery purposes, to be included within the definition of an LSV, without opening the category to unintended vehicles, such as street-sweepers or speed-modified passenger cars. Additionally, in 2006, in response to petitions for reconsideration from Dynasty Electric Car Corporation and Global Electric Motorcars (GEM), both manufacturers of electric LSVs, NHTSA increased the maximum GVWR for LSVs to 3,000 pounds. This was done, in part, to “level the playing field” between electric and gasoline-powered LSVs, by allowing for the additional weight in batteries required by electric vehicles. 
                    <E T="03">See</E>
                     71 FR 20026. 
                </P>
                <HD SOURCE="HD1">II. Petition for Reconsideration </HD>
                <P>
                    ETA, a corporation involved in providing vehicle testing services for the Department of Energy, submitted a petition for reconsideration, dated June 2, 2006, asking NHTSA to reconsider its decision on April 19, 2006 that amended FMVSS No. 500 to raise the maximum permissible GVWR for a LSV to 3,000 pounds. ETA requested that NHTSA accommodate the weight of batteries by raising the maximum GVWR of electric-powered vehicles still further to 4,000 pounds.
                    <SU>1</SU>
                    <FTREF/>
                     To address some of the side effects of that increase, ETA also suggested that the agency consider adopting brake performance and tire weight rating requirements for LSVs. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         71 FR 20026; Docket No. NHTSA-06-24488.
                    </P>
                </FTNT>
                <P>In its petition, ETA stated that there is a growing demand to reduce or eliminate the numbers of petroleum-fueled vehicles normally used in restricted areas, but that these vehicles need to be licensed for use on public roads as these areas are situated in or around public roadways. Further, it suggested that there is an increasing need in these operating environments for truck-like vehicles designed to carry cargo, such as for landscaping and maintenance matters. </P>
                <P>ETA argued that the current GVWR limitation of 3,000 pounds hinders the development of electric LSVs that can function as trucks. Specifically, because of the stop-and-go driving conditions in which these trucks operate, the wear on their electric batteries necessitates extremely large batteries. According to ETA, these batteries can weigh as much as 600 pounds or more. Given the current GVWR limit and the need to provide cargo capacity, ETA said the weight of the batteries curtails the weight of the chassis. For example, ETA stated that an LSV with a 661 pound battery and a cargo capacity of 1,000 pounds cannot have a chassis weight greater than 1,339 pounds under the current GVWR limit. According to the petition, this creates a major hindrance to designing cargo carrying electric LSVs. ETA stated that this puts electric-powered LSVs at a disadvantage relative to gas-powered LSVs, which use gasoline as fuel, and thus can have more substantial chasses while remaining under the 3,000 pound limit. </P>
                <P>ETA also argued that allowing larger vehicles to be classified as LSVs would spur production of vehicles in the small-truck market, because the need created by the current GVWR limit to design vehicles that comply with all FMVSS standards adds a substantial cost to vehicles produced in low quantities. ETA claimed that it could cost over $50 million to fully design and certify a vehicle to comply with the full requirements of the FMVSSs, a large burden on manufacturers of vehicles produced in small quantities. Finally, ETA claimed that the increase in the GVWR limitation would allow the importation and conversion of foreign highway speed vehicles that do not meet the FMVSSs for cars or trucks to meet LSV requirements. </P>
                <HD SOURCE="HD1">III. Agency Response </HD>
                <P>After carefully considering ETA's petition to increase the GVWR limit for electric-powered LSVs, we have decided to deny the petition. There are two primary reasons for this decision. The first is that we believe that vehicles over 3,000 pounds are capable of complying with the full requirements of the FMVSSs. Secondly, in line with our policy in establishing a GVWR limit for LSVs in the first place, we believe that increasing the GVWR limit would encourage the use of LSVs in circumstances where it could pose an unreasonable risk to safety. These reasons are described at greater length below. </P>
                <HD SOURCE="HD2">a. Rationale for 3,000 Pound GVWR </HD>
                <P>As stated above, the definition of LSVs originally did not contain a maximum GVWR. The definition for an LSV established in that final rule was: </P>
                <EXTRACT>
                    <P>A 4-wheeled motor vehicle, other than a truck, whose speed attainable in 1.6 km (1 mile) is more than 32 kilometers per hour (20 miles per hour) and not more than 40 kilometers per hour (25 miles per hour) on a paved level surface.</P>
                </EXTRACT>
                <FP>
                    The logic behind this rulemaking was that these vehicles were so small that they could not practicably meet the full regimen of FMVSSs required of other motor vehicles.
                    <SU>2</SU>
                    <FTREF/>
                     Trucks were excluded because in all of the public hearings and docket submissions relating to LSVs and their uses proponents described them as passenger vehicles. Also, there were existing large, slow-moving work-related trucks, such as street sweepers, that already met FMVSSs for their vehicle class that would have become excluded from those FMVSSs had trucks not been excluded from the definition of LSVs. 
                </FP>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         62 FR 1077, January 8, 1997.
                    </P>
                </FTNT>
                <P>
                    When reconsidering the LSV definition, NHTSA was presented with arguments that small, work-related trucks would be used in the same environments as passenger-carrying LSVs. The agency decided that this was a desirable option, and modified the definition of LSVs accordingly. A GVWR limitation was substituted for the “other than a truck” portion of the definition for several reasons. The first was to provide an objective means for delineating between the vehicles for which the LSV requirements are appropriate (
                    <E T="03">i.e.</E>
                    , those vehicles that are too small to meet the full FMVSS requirements) and those vehicles that can be designed to meet the full set of FMVSSs. The second reason was that the low GVWR limit prevents attempts 
                    <PRTPAGE P="55803"/>
                    to circumvent FMVSSs for cars, trucks, and multipurpose passenger vehicles by applying the LSV classification to vehicles types that are able to meet the standards.
                    <SU>3</SU>
                    <FTREF/>
                     These reasons are discussed in more detail below. 
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         70 FR 48316.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">i. Limitation of LSVs to Appropriate Vehicles </HD>
                <P>
                    In denying this petition to further increase the maximum GVWR for LSVs, the agency believes it highly important to reiterate the rationale for classifying vehicles as LSVs in the first place. In the original rulemaking, we noted that several States, such as Florida and California, had passed legislation permitting golf carts and NEVs to use public roads in some areas. However, because NHTSA considered those vehicles which traveled 20 mph or faster to be “motor vehicles,” they could not be manufactured unless they met the FMVSSs for passenger cars. Therefore, as we stated in the 1998 final rule, “[t]his creates a conflict with the state and local laws because compliance with the full range of those standards is not feasible for these small vehicles.” 
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         63 FR 33194.
                    </P>
                </FTNT>
                <P>
                    At the heart of the rulemaking regarding LSVs is that they were too small to meet the requirements of passenger cars, and would only be used in controlled, low-speed environments, where the risk of collision would be small. ETA's recommendation to increase the GVWR limits conflict with NHTSA's rationale for establishing the GVWR limitation with regard to this rationale. The contradiction is the fact that vehicles with a GVWR of over 3,000 are simply not too small to meet the full FMVSSs. In the NPRM discussing the rationale for a 2,500 pound GVWR limit, the agency presented a list of the GVWRs of a variety of fully FMVSS-compliant passenger cars and SUVs. This list is repeated here (this relates to model year 2003): 
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         68 FR 68321.
                    </P>
                </FTNT>
                <GPOTABLE COLS="03" OPTS="L2,tp0,i1" CDEF="s70,r50,9">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Vehicle</CHED>
                        <CHED H="1">Type</CHED>
                        <CHED H="1">
                            GVWR 
                            <LI>in pounds</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Honda Insight</ENT>
                        <ENT>Passenger car</ENT>
                        <ENT>2,212</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Toyota Echo</ENT>
                        <ENT>Passenger car</ENT>
                        <ENT>3,010</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hyundai Accent</ENT>
                        <ENT>Passenger car</ENT>
                        <ENT>3,310</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Chevrolet Tracker</ENT>
                        <ENT>SUV</ENT>
                        <ENT>3,483</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Honda Civic</ENT>
                        <ENT>Passenger car</ENT>
                        <ENT>3,485</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Toyota Prius</ENT>
                        <ENT>Passenger car</ENT>
                        <ENT>3,615</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ford Focus</ENT>
                        <ENT>Passenger car</ENT>
                        <ENT>3,620</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Toyota RAV4</ENT>
                        <ENT>SUV</ENT>
                        <ENT>3,841</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Jeep Wrangler</ENT>
                        <ENT>SUV</ENT>
                        <ENT>4,450</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ford Ranger</ENT>
                        <ENT>Extended cab pick-up</ENT>
                        <ENT>4,800</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    A 2,500-pound GVWR limit was selected because it was lighter than all FMVSS-compliant passenger cars and SUVs, with the exception of the Honda Insight. It should be noted that the 2,500-pound limit considers the weight of the gasoline-powered Honda Insight, and then adds about 300 pounds to account for the additional weight of electric batteries over fuel.
                    <SU>6</SU>
                    <FTREF/>
                     As we stated above, the 2006 rule extended the limitation to 3,000 pounds. This, it was noted, still means that the Honda Insight was the only fully FMVSS-compliant passenger car to be lighter than the heaviest LSV. 
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         70 FR 48317.
                    </P>
                </FTNT>
                <P>However, if ETA's suggestion that electric LSVs have a maximum GVWR of 4,000 pounds, then they could be considerably heavier than many passenger cars, and even some SUVs, even factoring in a substantial allowance for the weight of the electric batteries. This would be inconsistent with NHTSA's rationale to make LSVs subject to less stringent safety requirements than passenger cars, in large part because they are “too small” to meet those requirements. </P>
                <P>
                    A second reason why raising the GVWR for electric LSVs is contrary to NHTSA's policy is that this would encourage the development of heavier, more substantial LSVs. In its petition, ETA stated that the current 3,000-pound GVWR limit limits the chassis to less than 1339 pounds.
                    <SU>7</SU>
                    <FTREF/>
                     This, it claims, will result in a “lightweight chassis” that will “not provide much occupant protection in the event of a crash.” ETA continues by saying that “manufacturers should be encouraged to increase chassis mass and, therefore, strength to ensure proper occupant safety.” 
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         This figure is derived from subtracting a 1,000-pound cargo capacity and a 661-pound battery from the 3,000-pound maximum GVWR.
                    </P>
                </FTNT>
                <P>In the 2003 final rule, in which NHTSA provided the rationale to change to a GVWR-based definition of LSVs, we said: </P>
                <EXTRACT>
                    <P>
                        We believe that, as LSVs become equipped with additional amenities, such as air conditioning, solid doors, and batteries for extended range, they lose the basic characteristics of a special vehicle designed for transportation within a planned, limited environment. Instead, these vehicles take-on the profile of a small, traditional passenger car vehicle, and in some cases, may be marketed as a small passenger car or as a substitute for a small passenger car. Even with a 25 mph speed limitation, we are concerned that LSVs that have characteristics and attributes of traditional passenger cars will be more likely to be used outside of planned communities and instead, more regularly mix with traffic.
                        <SU>8</SU>
                        <FTREF/>
                    </P>
                </EXTRACT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         70 FR 48316.
                    </P>
                </FTNT>
                <FP>ETA's rationale for increasing the weight of LSVs accomplishes the very end that NHTSA sought to avoid by establishing the 2,500-pound, and later 3,000-pound, GVWR limitation. As ETA correctly points out, raising the maximum weight of electric LSVs would encourage the development of larger, sturdier models. This would, in turn, likely extend their use into areas beyond those that NHTSA intended LSVs to go, namely, outside of controlled, low-speed environments. While NHTSA has no desire to restrict the use of electric vehicles, as opposed to gasoline-powered vehicles, on the majority of public roads, we believe that the vehicles using those roadways should meet the full set of FMVSS requirements. </FP>
                <HD SOURCE="HD3"> ii. Importation of Foreign Vehicles as LSVs </HD>
                <P>
                    A second argument put forth in ETA's petition for reconsideration is that increasing the maximum GVWR for electric LSVs would allow the importation of foreign electric vehicles without their having to conform to the full FMVSS requirements. As ETA states, “[t]hese vehicles are appealing as conversions to LSVs as they offer 
                    <PRTPAGE P="55804"/>
                    durable construction and the ability to carry heavier loads at lower costs than a full-speed [vehicle] or purpose-designed LSV.” While we agree that acceding to ETA's request would have this effect, it is again an effect we hope to avoid. 
                </P>
                <P>
                    To begin, we note that foreign made on-road motor vehicles, that are capable of high-speed use, are not eligible to be transformed into LSVs via the adoption of a speed-limiting governor. In a June 28, 2000 letter of interpretation to Mr. Thomas E. Dahl on this issue, we stated there are no circumstances under which the addition of a speed governing device to a high-speed vehicle would make the vehicle meet the definition of an LSV. After explaining that we established the LSV class because the vehicles were too small to meet the full FMVSS requirements, we stated that a common feature of this class appeared to be that they were capable of a maximum speed of 25 mph 
                    <E T="03">as designed and manufactured.</E>
                     This is still our interpretation of the regulation. 
                </P>
                <P>
                    Furthermore, the agency has stated several times that one concern we have regarding the LSV classification is that it could be used as a mechanism to import foreign motor vehicles without first making them conform to the FMVSSs. For example, in the 2005 final rule, we stated that “[t]he [2,500-pound] GVWR limit prevents attempts to circumvent FMVSSs for cars, trucks, and multipurpose passenger vehicles by applying the LSV classification to vehicle types that are able to meet the [full FMVSS] standards.” 
                    <SU>9</SU>
                    <FTREF/>
                     ETA's recommended 4,000-pound limit would permit the result we intended to prevent, and we view that as a reason to deny the petition. 
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         70 FR 48316.
                    </P>
                </FTNT>
                <HD SOURCE="HD2"> b. Technology-Neutral Regulation </HD>
                <P>ETA's final argument is that the current GVWR limitation provides an advantage to gasoline-powered vehicles over electric vehicles. The agency is aware that, with current technology, the batteries needed to power an electric vehicle weigh substantially more than the fuel needed to power an internal combustion engine. This was considered to some extent in our original rulemaking establishing the 2,500-pound GVWR limit in 2005, and considered extensively in our 2006 rule increasing that limit to 3,000 pounds, a rule undertaken at the behest of two electric LSV manufacturers. </P>
                <P>In the petitions that led to the 2006 rulemaking, NHTSA was presented with two differing solutions to this problem. The first, presented by Dynasty Electric Car Corporation, recommended a 2,500-pound GVWR restriction for internal combustion engine LSVs and a 2,800-pound GVWR restriction for electric LSVs. The second, recommended by GEM, requested that the GVWR limit be raised to 3,000 pounds for all LSVs, as this would accommodate electric LSVs with a cargo-carrying capacity of 1,000 pounds. </P>
                <P>
                    In the 2005 rule establishing the GVWR limitation, we discussed why we were not establishing different GVWR limitations for electric and gasoline-powered vehicles, despite the issue regarding the weight of the batteries. We noted that each propulsion type has its own advantages. While gasoline-powered vehicles are lighter, “the fact that electric LSVs are successful in the market indicates that any advantage of the [internal combustion] vehicle due to greater load capacity under our GVWR restriction will be overcome by other attractions of the electric vehicle to consumers.” 
                    <SU>10</SU>
                    <FTREF/>
                     ETA, perhaps inadvertently, cites several of these advantages in its petition. These include the high cost of gasoline, government mandates to reduce or eliminate petroleum-fueled vehicles from fleets, and the environmental benefits of electric vehicles. Therefore, we do not believe it is necessary to increase the regulatory complexity by setting different GVWR limitations based on propulsion method. 
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         70 FR 48317.
                    </P>
                </FTNT>
                <P>Finally, we believe that 3,000 pounds is a level at which electric LSVs that perform cargo-carrying work are practicable to build. In the 2006 final rule, we quoted one of the petitioners, GEM, where it stated: </P>
                <EXTRACT>
                    <P>All that GEM seeks in the U.S. market is a comparable “level playing field” by allowing LSV trucks to weigh as much as 3000 pounds GVWR, which would accommodate the electric batteries and an appropriate payload for LSV trucks.</P>
                </EXTRACT>
                <FP>
                    We note that GEM currently produces a cargo-carrying electric LSV with a GVWR of 3,000 pounds or less. We noted on GEM's Web site the GEM eL XD, which has a GVWR of 3,000 pounds, a payload capacity of 1,450 pounds, a top speed of 25 mph, and a range of up to 40 miles.
                    <SU>11</SU>
                    <FTREF/>
                     This example illustrates that the current GVWR limit permits the development of cargo-carrying, electric LSVs. 
                </FP>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         GEM Web site, available at 
                        <E T="03">http://www.gemcar.com.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion </HD>
                <P>For the reasons stated above, we are denying ETA's petition to increase the maximum allowable GVWR to 4,000 pounds for electric LSVs. Furthermore, because we are not increasing the maximum allowable GVWR, we are denying ETA's recommendation to establish brake requirements and tire weight rating requirements in FMVSS No. 500. </P>
                <SIG>
                    <DATED>Issued on: September 19, 2008. </DATED>
                    <NAME>Stephen R. Kratzke, </NAME>
                    <TITLE>Associate Administrator for Rulemaking.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22736 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-59-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration </SUBAGY>
                <CFR>49 CFR Part 571 </CFR>
                <DEPDOC>[Docket No. NHTSA-2008-0154] </DEPDOC>
                <SUBJECT>Federal Motor Vehicle Safety Standards; Medium Speed Vehicles </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Denial of petition for rulemaking. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document denies petitions for rulemaking submitted by Environmental Motors, and Porteon Electric Vehicles, Inc. and Mirox Corporation. The petitioners requested that NHTSA commence rulemaking to create a new class of motor vehicles known as medium speed vehicles, which would have a maximum speed capability of 35 mph. The petitioners contemplated that these vehicles would be subject to a set of safety standards greater than those that apply to low speed vehicles but substantially less than the full set of safety standards that apply to other light vehicles such as passenger cars. The petitioners cited a number of reasons in support of their petition, the most significant of which related to potential environmental benefits. After carefully reviewing the petitions, we are denying them because the introduction of such a class of motor vehicles without the full complement of safety features required for other light vehicles such as passenger cars would result in significantly greater risk of deaths and serious injuries. While NHTSA agrees with the importance of environmental issues, the agency believes that it is neither necessary nor appropriate to significantly increase the risk of deaths and serious injuries to save fuel. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <P SOURCE="NPAR">
                        <E T="03">For technical issues:</E>
                         Gayle Dalrymple, Office of Crash Avoidance Standards, NVS-123. Telephone: 202-366-5559; 
                        <PRTPAGE P="55805"/>
                        facsimile: 202-493-2739; e-mail 
                        <E T="03">gayle.dalrymple@nhtsa.dot.gov.</E>
                    </P>
                    <P>
                        <E T="03">For legal issues:</E>
                         Mr. Ari J. Scott, NHTSA Office of the Chief Counsel, NCC-112. Telephone: (202) 366-2992; facsimile: (202) 366-3820; e-mail 
                        <E T="03">ari.scott@nhtsa.dot.gov.</E>
                    </P>
                    <P>Both officials can be reached by mail at the National Highway Traffic Safety Administration, 1200 New Jersey Avenue, SE., Washington, DC 20590. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <EXTRACT>
                    <HD SOURCE="HD1">Table of Contents </HD>
                    <FP SOURCE="FP-2">I. Overview </FP>
                    <FP SOURCE="FP-2">II. Petitions for Rulemaking </FP>
                    <FP SOURCE="FP-2">III. Low Speed Vehicles </FP>
                    <FP SOURCE="FP-2">IV. State Legislation on MSEVs and Relevant Federal Requirements </FP>
                    <FP SOURCE="FP-2">V. Agency Response to Petitions </FP>
                    <FP SOURCE="FP1-2">A. The rationale for applying a limited set of safety standards to LSVs is not relevant to MSVs</FP>
                    <FP SOURCE="FP1-2">B. The traffic environment in which MSVs would likely travel is an environment for which the full set of the Federal motor vehicle safety standards is needed to prevent fatalities and serious injuries</FP>
                    <FP SOURCE="FP1-2">C. It is neither necessary nor appropriate to significantly increase the risk of deaths and serious injuries to save fuel</FP>
                    <FP SOURCE="FP1-2">D. Other issues</FP>
                    <FP SOURCE="FP-2">VI. Conclusion</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Overview </HD>
                <P>NHTSA has received three petitions for rulemaking, from Environmental Motors, Porteon Electric Vehicles, Inc. and Mirox Corporation, requesting that the agency commence rulemaking to create a new class of motor vehicles known as medium speed vehicles MSVs. While the specific requests vary, they essentially ask the agency to conduct rulemaking to exclude smaller light vehicles that would currently be classified as passenger cars, multipurpose passenger vehicles (MPVs) or trucks from many or most of the Federal motor vehicle safety standards, if their speed capability is 35 mph or less. The vehicles would instead be subject to a set of safety standards greater than those that apply to low speed vehicles (LSVs) but substantially less than the full set of safety standards that apply to other light vehicles. </P>
                <P>The petitioners made a variety of arguments in support of their requests, the most significant of which related to environmental benefits, including facilitating the development of electric vehicles and fuel savings. They argued that because LSVs are not permitted to have a speed capability greater than 25 mph, they cannot safely keep up with traffic in urban areas, and a need therefore exists for vehicles with a higher speed (35 mph) capability. The petitioners also noted that two States have passed laws that purport to allow medium speed electric vehicles to operate on certain public roads. </P>
                <P>After carefully considering the petitions, we are denying them because the introduction of such a class of motor vehicles without the full complement of safety features required for other light vehicles would result in significantly greater risk of deaths and serious injuries. We address the petitioners' arguments in detail in the rest of this document, but note the following points in this overview. </P>
                <P>The petitioners appear to view MSVs as a variant of LSVs, i.e., a special class of small motor vehicles that would not be required to meet the full complement of the Federal motor vehicle safety standards. However, the rationale for applying a limited set of safety standards to LSVs is not relevant to MSVs. </P>
                <P>NHTSA issues different safety standards for different types of motor vehicles. The agency established the special category of motor vehicles called LSVs to accommodate the use of small golf cars and other vehicles primarily intended for use in controlled, low-speed communities, such as retirement communities. In order to qualify as an LSV under the agency's definition, a vehicle must, among other things, have a speed capability no higher than 25 mph. LSVs are subject to a limited set of safety measures in FMVSS No. 500, including requirements related to the installation of lamps, mirrors, seat belts and a windshield. However, LSV's are not subject to most of the standards to which other light vehicles such as passenger cars are required to comply, including the rigorous crashworthiness standards. </P>
                <P>One of the principal concerns raised by the petitioners is that the 25 mph speed limitation that applies to LSVs prevents these vehicles from keeping up with traffic in urban areas. However, the 25 mph limitation reflects the fact that NHTSA designed the set of safety standards that apply to LSVs for vehicles intended to be used in controlled, low speed environments. Vehicles with a speed capability above 25 mph are more likely to be driven outside controlled, low speed environments, and the limited LSV safety requirements are not appropriate for such vehicles. </P>
                <P>The petitioners appear to assume that the full set of safety standards applicable to other light vehicles such as passenger cars would not be appropriate for MSVs, i.e., small vehicles with a speed capability of 35 mph. However, the traffic environment in which these vehicles would likely travel, including, e.g., urban roads with a speed limit of 35 mph or 45 mph, is an environment for which the full set of the Federal motor vehicle safety standards is needed to prevent fatalities and serious injuries. MSVs would be traveling in mixed traffic at speeds in which crashes posed a risk of serious injury or fatality and in which safety features such as frontal and side air bags significantly reduced that risk. Also, a number of the crash test requirements included in our safety standards simulate crashes in this higher speed environment. We note that the petitioners did not provide analysis demonstrating why any of the Federal motor vehicle safety standards are not needed for MSVs.</P>
                <P>NHTSA shares the concerns of the petitioners about the importance of environmental issues and saving fuel, and notes that it is currently engaged in rulemaking in which it has proposed to substantially increase average fuel economy standards for passenger cars and light trucks. We also note that a number of smaller vehicles have been introduced in recent years that are certified to comply with the full set of Federal motor vehicle safety standards. In addition, the current unprecedented cost of fuel is forcing manufacturers to improve fuel efficiency and reduce vehicle size without Federal mandates. </P>
                <P>While we appreciate the importance of environmental issues, NHTSA does not believe that it is necessary or appropriate to significantly increase the risk of deaths and serious injuries to save fuel by introducing a new class of motor vehicles that does not provide adequate safety protection. </P>
                <HD SOURCE="HD1">II. Petitions for Rulemaking </HD>
                <HD SOURCE="HD2">Environmental Motors </HD>
                <P>
                    One of the petitions received by NHTSA was from Environmental Motors, an electric vehicle (EV) dealer located in Glendale, CA.
                    <SU>1</SU>
                    <FTREF/>
                     That company stated that the petition was being sent as part of an effort by a coalition interested in getting zero emission, energy-efficient vehicles on the road in a safe and timely manner. The coalition includes EV manufacturers and sellers (including Miles Electric Vehicles, Zenn Motor Company, e-ride Industries, Dynasty Electric Car Corp., Boshart Engineering, Free Drive EV, Inc, Clean-Tech LLC, LE Electric Automobiles, LLC, and Electrovaya, Resort Vehicles, Inc.), the City of Santa Monica, CA, the University of California, Santa Barbara, and the Sustainable Transport Club of Santa Monica, CA. All of these groups sent letters supporting Environmental 
                    <PRTPAGE P="55806"/>
                    Motors' petition, which were attached to the petition. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         This petition can be viewed at 
                        <E T="03">http://www.regulations.gov,</E>
                         docket #NHTSA-2008-0019.
                    </P>
                </FTNT>
                <P>The petition itself requested that NHTSA establish a Medium Speed Vehicle (MSV) standard. According to the petition, the promulgated MSV standard should incorporate “the right mix of safety features,” although it did not specify what it considered a right mix. In doing so, the petition requested that NHTSA consider a number of factors. These include: </P>
                <P>• The fact that MSV legislation has been passed by several States. </P>
                <P>• Alleged safety benefits of vehicles being able to keep up with traffic. </P>
                <P>• That a MSV class would assist in the development of electric vehicles. </P>
                <P>• That most MSVs would be electric, and noting the environmental benefits of electric vehicles. </P>
                <P>Additionally, in letters of support, various supporters added additional arguments. These included: </P>
                <P>• The fact that full-speed electric vehicles are expensive. </P>
                <P>• Safety disbenefits incurred by the fact that some individuals modify LSVs to increase their speed. </P>
                <P>• As an alternative to creating a class of MSVs, NHTSA could increase the speed limitation for LSVs. </P>
                <HD SOURCE="HD2">Mirox Corporation </HD>
                <P>
                    Another petition that NHTSA received was from Mirox Corporation (Mirox).
                    <SU>2</SU>
                    <FTREF/>
                     Mirox's petition was more detailed than that of Environmental Motors, but also suggested that NHTSA create a class of MSVs with a maximum top speed of 35 mph. 
                </P>
                <P>Mirox requested that NHTSA define a MSV as a vehicle with: (1) A maximum speed of 30-35 mph, a maximum GVWR of 3,000 lbs. for cargo-carrying vehicles, or 2,500 lbs. for vehicles with passenger-carrying capacity only; (3) has three or four wheels; and (4) a limited number of equipment and bumper requirements. These requirements are more stringent than those required for LSVs, but substantially less than those required for other light vehicles such as passenger cars. Most prominently, Mirox would exclude MSVs from the requirements of FMVSS Nos. 138, 202a, and 208. The petitioner's request is explained in more detail below. </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         This petition can be viewed at 
                        <E T="03">http://www.regulations.gov,</E>
                         docket #NHTSA-2008-0019.
                    </P>
                </FTNT>
                <P>Mirox presents a variety of reasons for recommending its MSV classification. Some of these are similar to those identified by Environmental Motors, but some are unique. The following is a summary of the arguments put forth by Mirox: </P>
                <P>• MSVs are a viable alternative to motorcycles, including enclosed, three-wheeled motorcycles, which are currently subject to a very limited array of safety standards. Mirox notes that the rate of motorcycle fatalities has been increasing, and argues that the use of MSVs could alleviate this. Mirox also argues that MSVs would provide better protection from weather and outside conditions than motorcycles, and are therefore likely to be used more often. Additionally, Mirox states that MSVs would be easier to drive than motorcycles, which would also help reduce injuries. </P>
                <P>• MSVs are a better alternative to LSVs for use in driving in urban environments. Mirox states that due to speed limitations, LSVs are unsuited to driving in urban conditions, as they impede traffic flow and have limited acceleration potential. Mirox also argues that drivers will prefer MSVs as defined by the petitioner, as they will offer more protection from outside conditions and be equipped with a wider array of safety features than LSVs. </P>
                <P>• Mirox expounds on the environmental and economic benefits of increased fuel economy for MSVs over passenger cars. It argues that because most MSVs will be electric, they will not consume fuel while idling, which is common in the urban environments that Mirox believes will be the primary environment for MSVs. </P>
                <P>• Like Environmental Motors, Mirox points to the adoption of MSEV statutes in Montana and Washington, and argues that Federal regulations should be changed to sanction vehicles built in accordance to those statutes. </P>
                <P>• Mirox cites the use of “quadricycles” in Europe, and argues that similar vehicles should be permitted in the U.S. as well. Mirox asserts that European experience, especially in France, has shown that the quadricycle class of vehicles is the safest of all vehicle classes, and that their drivers had fewer accidents than the average driver of a full-sized car. </P>
                <P>In its petition, Mirox recommended a specific, detailed definition for MSVs. While similar in nature to that for an LSV, Mirox's definition contains more specific safety requirements. We note that, while it espoused the benefits of electric power, unlike the Montana or Washington statutes, Mirox's recommended definition would include gasoline-powered MSVs. </P>
                <P>Specifically, Mirox's recommended definition of medium-speed vehicle is:</P>
                <EXTRACT>
                    <P>A self-propelled, four-wheeled or three-wheeled motor vehicle, equipped with a roll cage or crush-proof body design, whose speed attainable in one mile is more than thirty miles per hour but not more than thirty-five miles per hour on a paved level surface. Each Medium-speed vehicle shall at a minimum be equipped with [the] following safety equipment that [conforms] to [the] existing FMVSS and current applicable SAE standard: </P>
                    <P>• Headlamps as per FMVSS No. 108 </P>
                    <P>• Front and rear turn signal lamps (SAE I) (49 CFR 571.108) </P>
                    <P>• Taillamps (SAE T), (49 CFR 571.108) </P>
                    <P>• Stop lamps (SAE S), (49 CFR 571.108) </P>
                    <P>• Reflex reflectors: one red on each side as far to the rear as practicable, one amber on each side as far to the front as practicable (SAE A) </P>
                    <P>• Side marker lights, one red on each side as far to the rear as practicable, one amber on each side as far to the front as practicable (SAE P) </P>
                    <P>• An exterior mirror mounted on the driver's side of the vehicle and either an exterior mirror mounted on the passenger's side of the vehicle or an interior mirror (49 CFR 571.111) </P>
                    <P>• A parking brake (49 CFR 571.135) </P>
                    <P>• A windshield of AS-1 or AS-5 composition, that conforms to the American National Standards Institute's “Safety Code for Safety Glazing Materials for Glazing Motor Vehicles Operating on Land Highway,” Z-26.1-1977, January 28, 1977, as supplemented by Z26.1a, July 3, 1980 (49 CFR 571.205) </P>
                    <P>• A VIN that conforms to the requirements of 49 CFR Part 565, Vehicle Identification Number </P>
                    <P>• A Type 1 or Type 2 seat belt assembly conforming to FMVSS No. 209, installed at each designated seating position, and whose mounting complies with FMVSS No. 210 </P>
                    <P>• Bumper system; both front and rear that conforms to 49 CFR Part 581 </P>
                    <P>• Audible Warning Devices; Horn and Reverse Warning Beeper </P>
                    <P>• If the vehicle is electrically powered it shall conform to FMVSS No. 305 </P>
                    <P>• A GVWR of less than 1,361 kilograms (3,000 pounds) if the vehicle is designed with substantial cargo-carrying capacity (i.e., vehicles intended for carrying goods), or 1,134 kilograms (2,500 pounds) if the vehicle is designed solely for transport of passengers. </P>
                    <P>Additionally, if the Medium-speed vehicle contains any equipment that is referenced in any of the following FMVSS[s], such equipment or features shall [conform] to all the requirements of the applicable FMVSS: </P>
                    <P>FMVSS Nos. 101, 102, 103, 104, 105, 106, 108, 109, 110, 111, 113, 116, 118, 124, 135, 139, 201, 202, 203, 204, 205, 206, 207, 209, 210, 212, 214, 216, 219, 225, 301, 302, 304, 305, and 401. </P>
                </EXTRACT>
                <HD SOURCE="HD2">Porteon Electric Vehicles, Inc </HD>
                <P>
                    The last petition received by NHTSA was from Porteon Electric Vehicles, Incorporated of Portland, Oregon.
                    <SU>3</SU>
                    <FTREF/>
                     This petitioner plans to market an electric car designed from the ground up rather than retrofit an imported vehicle by removing the IC engine and replacing it with an electric motor. The petitioner is concerned, “that unregulated growth 
                    <PRTPAGE P="55807"/>
                    could create safety issues and concerns that negatively impact and cause severe damage to a new growth industry that provides real and significant solutions to our country and our planet's key issues.” This petitioner envisions a Medium Speed Vehicle class that “would essentially be the same as the LSV regulations with the exception of the top speed of 35 miles per hour and additional vehicle requirement to increase the safety of margin [sic] for rollover, stopping, acceleration, and avoidance maneuvering.” The petitioner lists these additional vehicle requirements as: Ability to maintain 35 mph on a level grade, ability to maintain 30 mph up an 8 percent grade, a minimum width of 55 inches, a “coil over shock” suspension, four-wheel hydraulic disc or drum brakes, and three-point automotive seat belts, in addition to the requirements that already exist for LSVs in FMVSS No. 500. The petitioner also states, “Additional testing of the vehicles should also be considered, including crush zones with a 2.5mph ‘no damage’ requirement. A full frontal crash should be required to meet safety standards between 17-18 mph, which is a derivative of full speed automobiles being crash tested at 35 mph.” The petitioner does not state where the no damage crush zones would be on the vehicle, how they would be measured, or which safety standards would be tested at 17 or 18 miles per hour. 
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         This petition can be viewed at 
                        <E T="03">http://www.regulations.gov</E>
                        , docket #NHTSA-2008-0019.
                    </P>
                </FTNT>
                <P>Porteon believes the new medium speed vehicle class is necessary because LSVs currently travel, with their top speed of 25 mph, on streets with speed limits up to 35 mph and normal traffic flow is impeded by these vehicles. MSVs, with their top speed of 35 mph, “would create a more cohesive traffic environment for mixed use vehicles.” </P>
                <HD SOURCE="HD1">III. Low Speed Vehicles </HD>
                <P>
                    In 1998, NHTSA established Federal Motor Vehicle Safety Standard (FMVSS) No. 500, “Low speed vehicles,” in response to growing interest in using golf cars and other similar-sized, 4-wheeled vehicles, including Neighborhood Electric Vehicles (NEVs), to make short trips for shopping, social, and recreational purposes primarily within retirement or other planned communities with golf courses. 
                    <E T="03">See</E>
                     63 FR 33194. The definition of LSV established in that rulemaking was, “a 4-wheeled motor vehicle, other than a truck, whose speed attainable in 1.6 km (1 mile) is more than 32 kilometers per hour (20 miles per hour) and not more than 40 kilometers per hour (25 miles per hour) on a paved level surface. 
                </P>
                <P>
                    In 2005, NHTSA published a final rule amending the definition of LSVs by removing the restriction on trucks, and instead establishing a 2,500 pound maximum GVWR. 
                    <E T="03">See</E>
                     70 FR 48313. This allowed small vehicles designed for work-related applications within the intended communities, such as landscaping or delivery purposes, to be included within the definition of an LSV, without opening the category to unintended vehicles, such as street-sweepers or speed-modified passenger cars. Additionally, in 2006, in response to petitions for reconsideration from Dynasty Electric Car Corporation and Global Electric Motorcars (GEM), both manufacturers of electric LSVs, NHTSA increased the maximum GVWR for LSVs to 3,000 pounds. This was done, in part, to “level the playing field” between electric and gasoline-powered LSVs, by allowing for the additional weight in batteries required by electric vehicles. 
                    <E T="03">See</E>
                     71 FR 20026. 
                </P>
                <P>In conceiving the concept of the LSV as a small vehicle that would not be subject to the same stringent safety criteria as other vehicles, a critical concept was that it would not ordinarily mix with other traffic. In our 1998 rule establishing the category of LSVs, NHTSA explained in the summary that the rule:</P>
                <EXTRACT>
                    <P>
                        [R]esponds to a growing public interest in using golf cars and other similar-sized, 4-wheeled vehicles to make short trips for shopping, social and recreational purposes 
                        <E T="03">primarily within retirement or other planned communities with golf courses.</E>
                         [emphasis added]
                    </P>
                </EXTRACT>
                <P>NHTSA's detailed analysis, as explained in the preamble of the 1998 final rule, recognized the importance of the fact that under most conditions, LSVs would not intermingle with regular automobile traffic, and the occasions where they would mix would be in controlled, low-speed environments. NHTSA stated that</P>
                <EXTRACT>
                    <FP>
                        NHTSA has carefully reviewed their argument about the effects of this rulemaking. LSV safety, and thus the need for FMVSSs for LSVs, will be determined by the combination of three factors: vehicle design and performance; operator training and ability; and the operating environment. The agency believes that Standard No. 500, in combination with a limited operating environment and appropriate operator training and ability, will appropriately address the safety needs of LSV users.
                        <SU>4</SU>
                        <FTREF/>
                    </FP>
                </EXTRACT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         63 FR 33208.
                    </P>
                </FTNT>
                <FP>Additionally, in the 1998 final rule, NHTSA analyzed the Fatal Analysis Reporting System (FARS) data regarding fatalities involving golf cars. It was found that of the nine reported fatalities, eight of them involved a collision with a car or truck. This further underscored the importance of driving environment. </FP>
                <P>
                    In the 1998 final rule, the agency studied the use of NEVs in various municipalities that permitted them to travel on public roads. In that notice, we stated that “the driving environment [of LSVs] should be appropriate to the vehicle and its characteristics. Limiting LSV use to low-speed city and suburban streets is necessary, but does not eliminate the safety risks.” 
                    <SU>5</SU>
                    <FTREF/>
                     NHTSA analyzed the State laws governing the on-road permissibility of NEVs in various States. Of the 12 States discussed, only one State (Arizona) permitted NEVs to travel on any road with a speed of 35 mph or less. The other 11 States (California, Nevada, New Mexico, Colorado, Wyoming, Illinois, Minnesota, Iowa, Florida, Georgia, and Texas) restricted NEVs to roads specifically designated by State and local governments.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         63 FR 33208.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         See 63 FR 33207.
                    </P>
                </FTNT>
                <P>
                    One portion of the analysis discussed possible reasons for the disparity of fatalities between Sun City 
                    <SU>7</SU>
                    <FTREF/>
                     (which had four NEV fatalities) and the City of Palm Desert (which had zero). We noted that:
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         We note that Sun City is located in Arizona, the only State that allowed NEVs to travel on any street with a speed limit of 35 mph or less.
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>The City of Palm Desert has a more controlled environment than Sun City for golf car use. The City of Palm Desert permits on-road use of golf cars in the same lanes as passenger cars and other larger motor vehicles in speed zones posted for speeds up to 25 miles per hour. In speed zones posted for speeds over 25 miles per hour, golf cars may be operated on-road only if there is a lane designated for their use and if the golf car is, in fact, operated within that lane. By contrast, NHTSA understands that Sun City, under state law, allows golf cars to operate in the same lanes as larger traffic on any road with a maximum speed of 35 miles per hour.</P>
                </EXTRACT>
                <FP>Based in part on this analysis, as well as our other observations, we concluded that operating environment played an important role in determining the benefits of establishing the LSV classification, as well as determining what safety standards should apply to that class. While NHTSA does not regulate the driving environment (such decisions are at the discretion of State governments), it did recommend that LSVs be licensed only for use in environments with very limited traffic. Specifically, we stated:</FP>
                <EXTRACT>
                    <P>
                        NHTSA recognizes that not all operating environments may be as controlled as that of the City of Palm Desert. The agency encourages other states and municipalities to study the features of the City of Palm Desert's 
                        <PRTPAGE P="55808"/>
                        plan, and to adopt those features to the extent practicable.
                        <SU>8</SU>
                        <FTREF/>
                    </P>
                </EXTRACT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         63 FR 33208.
                    </P>
                </FTNT>
                <FP>
                    In later rulemakings, NHTSA made several adjustments to the definition of LSVs. First and foremost, the agency dropped its original restriction on “truck-like” vehicles, and replaced it with a maximum gross vehicle weight rating for LSVs.
                    <SU>9</SU>
                    <FTREF/>
                     This weight limit was originally 2,500 lbs., but was later increased to 3,000 lbs.
                    <SU>10</SU>
                    <FTREF/>
                </FP>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         70 FR 48313, August 17, 2005.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         71 FR 20026, April 19, 2006.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. State Legislation on MSEVs and Relevant Federal Requirements </HD>
                <P>In the past year, two States have enacted legislation that purports to allow medium speed electric vehicles (MSEVs) to operate on certain public roads. Montana was the first State to pass such a law, on April 23, 2007. This was followed shortly thereafter by Washington State, which passed on May 15, 2007. These are the only two States that NHTSA is aware of that have passed any sort of MSV legislation. </P>
                <P>
                    The Montana and Washington statutes define MSEVs as electric-powered vehicles with a maximum speed of 35 mph that meet certain limited safety requirements similar to those established by NHTSA for LSVs.
                    <SU>11</SU>
                    <FTREF/>
                     The Montana law permits MSEVs to travel on public roads with a posted speed of up to 45 mph,
                    <SU>12</SU>
                    <FTREF/>
                     while the Washington law restricts them to roads with a posted speed of 35 mph or less. 
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The specific definitions are at Mont. Code Ann. 61-1-101 and West's RCWA 46.04.295.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         Mont. Code Ann. 61-8-377.
                    </P>
                </FTNT>
                <P>NHTSA has considered the legislative history and other information relating to the aforementioned State laws. Both States were interested in expanding the use of electric vehicles in order to reduce fuel consumption, and economic and environmental benefits associated with that end. Additionally, there was a stated belief that a speed of 35 mph is needed for safety, as they would be able to keep up with traffic better. The following excerpt from the Washington State Senate report illustrates the considerations at issue: </P>
                <EXTRACT>
                    <P>
                        Staff Summary of Public Testimony: PRO: These electric vehicles are environmentally friendly and provide significant energy savings. They are not golf carts; they are cars designed for running errands in town. The current speed of 25 mph is too slow and puts people at risk. Increasing the allowed speed to 35 mph will improve safety.
                        <SU>13</SU>
                        <FTREF/>
                    </P>
                </EXTRACT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         Washington State Senate Bill Report, HB 1820, March 21, 2007.
                    </P>
                </FTNT>
                <P>Under Federal law, vehicles with a speed capability above 25 mph that would be considered MSEVs under these State laws are classified as passenger cars, multipurpose passenger vehicles, or trucks. These vehicles are subject to the full range of FMVSSs that apply to these vehicles. The responsibilities of manufacturers and dealers to comply with Federal law, including not manufacturing or selling vehicles unless they comply with all applicable FMVSSs, are not limited by State laws on MSEVs. </P>
                <HD SOURCE="HD1">V. Agency Response to Petitions </HD>
                <P>After carefully considering the petitions from Environmental Motors, Proteon and Mirox, we are denying them. First and foremost among this agency's considerations are safety concerns. The concept of establishing such a class of motor vehicles with limited safety features that would be likely to intermingle with larger, higher-speed vehicles in urban environments would result in significantly greater risk of deaths and serious injuries. The petitioners did not provide analysis demonstrating why any of the Federal motor vehicle safety standards are not needed for MSVs, given the traffic environment in which these vehicles would be likely to travel. </P>
                <HD SOURCE="HD2">A. The Rationale for Applying a Limited Set of Safety Standards to LSVs Is Not Relevant to MSVs </HD>
                <P>As noted earlier, the petitioners appear to view MSVs as a variant of LSVs, i.e., a special class of small motor vehicles that would not be required to meet the full complement of the Federal motor vehicle safety standards. However, the rationale for applying a limited set of safety standards to LSVs is not relevant to MSVs. </P>
                <P>NHTSA issues different safety standards for different types of motor vehicles. The agency established the special category of motor vehicles called LSVs to accommodate the use of small golf cars and other vehicles primarily intended for use in controlled, low-speed communities, such as retirement communities. In order to qualify as an LSV under the agency's definition, a vehicle must, among other things, have a speed capability no higher than 25 mph. LSVs are subject to a limited set of safety measures in FMVSS No. 500, including requirements related to the installation of lamps, mirrors, seat belts and a windshield. However, LSV's are not subject to most of the standards to which other light vehicles such as passenger cars are required to comply, including the rigorous crashworthiness standards. </P>
                <P>One of the principal concerns raised by the petitioners is that the 25 mph speed limitation that applies to LSVs prevents these vehicles from keeping up with traffic in urban areas. They argued that because LSVs are not permitted to have a speed capability greater than 25 mph, they cannot safely keep up with traffic in urban areas, and a need therefore exists for vehicles with a higher speed (35 mph) capability. </P>
                <P>However, the 25 mph limitation reflects the fact that NHTSA designed the set of safety standards that apply to LSVs for vehicles intended to be used in controlled, low speed environments. Vehicles with a speed capability above 25 mph are more likely to be driven outside controlled, low speed environments, and the limited LSV safety requirements are not appropriate for such vehicles. </P>
                <P>
                    When promulgating the original LSV rule, as stated above, at the time one of the most important factors was that LSVs were conceived as vehicles that would be used in controlled, low-speed environments, primary in retirement communities and those centered around golf courses. NHTSA surveyed the applicable State laws governing the on-road use of LSVs, and found that only one out of twelve States with LSV-use laws permitted them to travel on any public road with a speed limit of 35 mph or less. The other remaining States limited their use to specially-designated roads.
                    <SU>14</SU>
                    <FTREF/>
                     While NHTSA does not have the authority to prescribe the roads for which different types of vehicles are permitted, the agency suggested limiting LSVs to controlled environments. The following passage from the 1998 final rule properly summarizes NHTSA's position on this point:
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         63 FR 33207.
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>Still another reason [for the significant disparity in the number of deaths involving NEVs] may lie in the different operating environments in the two communities. The City of Palm Desert has a more controlled environment than Sun City for golf car use. The City of Palm Desert permits on-road use of golf cars in the same lanes as passenger cars and other larger motor vehicles in speed zones posted for speeds up to 25 miles per hour. In speed zones posted for speeds over 25 miles per hour, golf cars may be operated on-road only if there is a lane designated for their use and if the golf car is, in fact, operated within that lane. By contrast, NHTSA understands that Sun City, under state law, allows golf cars to operate in the same lanes as larger traffic on any road with a maximum speed of 35 miles per hour. </P>
                    <P>
                        NHTSA recognizes that not all operating environments may be as controlled as that of the City of Palm Desert. The agency encourages other states and municipalities to study the features of the City of Palm Desert's plan, and to adopt those features to the extent practicable.
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             63 FR 33208.
                        </P>
                    </FTNT>
                </EXTRACT>
                <PRTPAGE P="55809"/>
                <P>We recognize that since that time many States have passed laws permitting LSVs on a much wider variety of roads than originally contemplated. Today, many States permit LSVs on all public roads with posted speed limits of 35 mph or less. Some States even permit them on roads with speed limits of 45 mph. </P>
                <P>As we have noted before, however, we continue to believe that LSV use on roads outside confined, controlled areas will be limited by the fact that occupants will not want to travel at less than 25 mph in mixed-vehicle traffic for other than very short trips, regardless of how States may or may not restrict their use. See 68 FR 68319, December 3, 2003. </P>
                <P>We agree with the petitioners that the increased speed capability and other features in the requested MSV category would facilitate and encourage drivers to use MSVs in general driving environments. This, however, means that the rationale for applying a limited set of safety standards to LSVs is not relevant to MSVs. Instead, and as discussed further below, this is an argument for why these vehicles should be required to comply with the same safety standards as other light vehicles used in general driving environments, such as passenger cars. </P>
                <HD SOURCE="HD2">B. The Traffic Environment in Which MSVs Would Likely Travel Is an Environment for Which the Full Set of the Federal Motor Vehicle Safety Standards Is Needed To Prevent Fatalities and Serious Injuries </HD>
                <P>The petitioners appear to assume that the full set of safety standards applicable to other light vehicles such as passenger cars would not be appropriate for MSVs, i.e., small vehicles with a speed capability of 35 mph. However, the traffic environment in which these vehicles would likely travel, including, e.g., urban roads with speed limits of 35 mph or 45 mph, is an environment for which the full set of the Federal motor vehicle safety standards is needed to prevent fatalities and serious injuries. We note that the energy involved in vehicle-to-vehicle collisions increases proportional to the square of the velocity of travel, and the result of a vehicle collision at 35 mph is twice as severe as the same collision at 25 mph. </P>
                <P>MSVs would be traveling in mixed traffic at speeds in which crashes posed a risk of serious injury or fatality and in which safety features such as frontal and side air bags significantly reduced that risk. Also, a number of the crash test requirements included in our safety standards simulate crashes in this higher speed environment. We note that the petitioners did not provide analysis demonstrating why any of the Federal motor vehicle safety standards are not needed for MSVs. </P>
                <P>As part of considering this issue, we have looked at crash information on public roads with speed limits of 35 to 45 mph. For this traffic environment, the need for the safety features required in FMVSS No. 208, air bags, are far more important than for lower speed crashes, as frontal crashes become a more prominent part of the overall crash picture. </P>
                <P>The total number of occupants killed annually in crashes is 37,314 (2002-2006 average, Fatality Analysis Reporting System). Of these occupant fatalities, 6,319 were killed on roads with posted speed limits of 35 mph or less, and 13,493 are killed in crashes on roads with posted speed limits of 45 mph or less. The total number of occupants suffering incapacitating injury annually is 13,492. Of these, 1,798 were injured in crashes on roads with posted speed limits of 35 mph or less, and 4,261 occupants were injured in crashes on roads with posted speed limits of 45 mph or less. It is important to note that those numbers reflect vehicles that were certified to comply with the Federal motor vehicle safety standards. </P>
                <P>
                    We estimate that in 2005, on roads posted at 35 mph or lower, 1,921 crash victims lived because the vehicles were compliant with all FMVSSs, including 278 saved by air bags. In crashes on roads posted at 45 mph or lower, 3,163 lives were saved because the vehicles involved were compliant with all FMVSSs. Of those, 414 were saved by air bags.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Using the methodology of “Lives Saved by the Federal Motor Vehicle Safety Standards and Other Vehicle Technologies, 1960-2002” DOT HS 809-833.
                    </P>
                </FTNT>
                <P>Given these statistics, we believe the full set of Federal motor vehicle safety standards is needed for vehicles traveling in the traffic environment in which MSVs would likely travel, including, e.g., urban roads with speed limits of 35 mph or 45 mph. </P>
                <P>Finally, as noted above, a number of the crash test requirements included in our safety standards simulate crashes in this environment. For example, our highest speed crash test in FMVSS No. 208 (vehicle compliance is currently phasing in) simulates a 35 mph frontal crash between the tested vehicle and a vehicle like itself. Our crash test in FMVSS No. 214 that helps ensure thoracic protection simulates a crash in which the tested vehicle traveling at 15 mph is struck in the side by a light vehicle traveling at 30 mph. </P>
                <HD SOURCE="HD2">C. It Is Neither Necessary nor Appropriate To Significantly Increase the Risk of Deaths and Serious Injuries To Save Fuel </HD>
                <P>The petitioners and the supporters which wrote in favor of the Environmental Motors petition emphasized the potential to conserve fuel, thereby saving money at a time of high fuel prices as well as reducing emissions that can harm the environment. In the two States that passed MSEV statutes, the legislative history also shows that this legislation was conceived due to concerns about saving fuel. </P>
                <P>NHTSA also considers fuel conservation an important goal. However, we believe that it is neither necessary nor appropriate to significantly increase the risk of deaths and serious injuries to save fuel. </P>
                <P>Fuel conservation can be accomplished by means that are not inconsistent with the need for safety. Significant innovation is currently underway in fuel economy, gas-electric hybrid engine technology, and continued development of fully electric vehicles, such as the Chevrolet Volt, noted in the Mirox petition. NHTSA recently published a proposal to substantially increase fuel economy (CAFE) standards for passenger cars and light trucks. These standards affect nearly all light vehicles, and will have a tremendous impact on fuel savings. Furthermore, these vehicles are being designed to meet the full FMVSS requirements for passenger cars or other applicable vehicle class. </P>
                <HD SOURCE="HD2">D. Other Issues </HD>
                <P>The petitioners raised a number of additional issues, which we discuss in this section. </P>
                <HD SOURCE="HD3">Quadricycles </HD>
                <P>
                    The Mirox petition compared the requested MSV classification to a type of vehicle used in Europe known as a “quadricycle.” The Economic Commission for Europe (ECE) defines a quadricycle in two vehicle categories, L
                    <E T="52">6</E>
                     “light quadricycle” and L
                    <E T="52">7</E>
                     “quadricycle”: 
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         TRANS/WP.29/78/Rev.1/Amend. 4, 26 April 2005.
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>
                        <E T="03">Category</E>
                         L
                        <E T="52">6</E>
                        : A vehicle with four wheels whose unladen mass in not more than 350 kg, not including the mass of the batteries in the case of electric vehicles, whose maximum design speed is not more than 45 km/h, and whose engine cylinder capacity does not exceed 50 cm
                        <SU>3</SU>
                         for spark (positive) ignition engines, or whose maximum net power output does not exceed 4 kW in the case of other internal combustion engines, or whose 
                        <PRTPAGE P="55810"/>
                        maximum continuous rated power does not exceed 4 kW in the case of electric engines. 
                    </P>
                    <P>
                        <E T="03">Category</E>
                         L
                        <E T="52">7</E>
                        : A vehicle with four wheels, other than that classified for the category L
                        <E T="52">6</E>
                        , whose unladen mass is not more than 400 kg (550 kg for vehicles intended for carrying goods), not including the mass of batteries in the case of electric vehicles and whose maximum continuous rated power does not exceed 15 kW.
                    </P>
                </EXTRACT>
                <P>Mirox claimed that quadricycles are an extremely safe method of transportation that is used extensively in Europe. The chief benefits of quadricycles is that they are easy to use (unlike motorcycles), easy to park, and consume far less fuel than even the smallest European passenger cars. Mirox requested that MSVs be defined in such a way that at least some European quadricycles can be legally imported as MSVs. </P>
                <P>While the petitioner claimed that quadricycles are extremely safe, Mirox did not provide any data to support this claim or to show that introduction of these vehicles into the U.S. would be consistent with the need for safety. We note that we have earlier denied the petition of GG Quad North American to change the definition of “motorcycle” to allow quadricycles to be sold in the U.S. as motorcycles (71 FR 67843, November 24, 2006). </P>
                <HD SOURCE="HD3">Aftermarket Speed Modifications of LSVs </HD>
                <P>A letter written in support of the Environmental Motors petition by Electrovaya suggested that “The new [MSV] regulations would give people a better option than illegally changing an LSV to go faster.” We agree with Electrovaya that modifying an LSV to increase the speed is highly undesirable. However, we do not believe that adopting a regulation to accommodate this practice is a prudent response to the issue. Furthermore, we would point out that manufacturers, dealers, sellers, and motor vehicle repair businesses that modify the speed of an LSV are in violation of the “make inoperative” provision. </P>
                <P>
                    This statutory provision, 49 U.S.C. 30122, 
                    <E T="03">Making safety devices and elements inoperative,</E>
                     reads in part: 
                </P>
                <EXTRACT>
                    <P>A manufacturer, distributor, dealer, or motor vehicle repair business may not knowingly make inoperative any part of a device or element of design installed on or in a motor vehicle or motor vehicle equipment in compliance with an applicable motor vehicle safety standard prescribed under this chapter unless the manufacturer, distributor, dealer, or repair business reasonably believes the vehicle or equipment will not be used (except for testing or a similar purpose during maintenance or repair) when the device or element is inoperative.</P>
                </EXTRACT>
                <P>If one of the above-mentioned entities increased the speed of an LSV to 25 mph or greater, that LSV would no longer comply with paragraph S5.3 of FMVSS No. 500, which specifies that the vehicle's top speed must be less than 25 mph. Therefore, the modifying entity would be subject to civil penalties as specified in 49 U.S.C. 30165. </P>
                <HD SOURCE="HD3">Burgeoning Electric Vehicle Market </HD>
                <P>Porteon states in its petition, “Regardless of our [the electric cars' industry] success or failure, the U.S. will soon see an influx in electric vehicles as fuel prices, urbanization, and climate change effect [sic] transportation and state regulation. It is estimated that over 20 manufacturers are in operation or commencing production along with a new influx of imports anticipated from China and Malaysia. Our concern is that unregulated growth could create safety issues and concerns that negatively impact and cause severe damage to a new growth industry that provides real and significant solution to our country and our planet's key issues.” NHTSA would like to point out that the electric vehicle market is not unregulated. Any vehicle not certified as an LSV, or that travels at speeds greater than 25 miles per hour, must meet all the FMVSSs in place for the appropriate vehicle type (passenger car, truck, bus, or MPV). The petitioner can rest assured that growth of the electric vehicle market will not occur without the vehicles meeting the existing regulatory safety requirements enforced by NHTSA. The only difference between electric vehicles and those predominately in use today is their propulsion system. An electric propulsion system will not exempt these vehicles from the requirement to meet all the Federal standards for motor vehicles. </P>
                <HD SOURCE="HD1">VI. Conclusion </HD>
                <P>For the reasons discussed above, NHTSA denies the petitions for rulemaking submitted by Environmental Motors, Proteon Electric Vehicles and Mirox Corporation. </P>
                <SIG>
                    <DATED>Issued on: September 19, 2008.</DATED>
                    <NAME>Stephen R. Kratzke,</NAME>
                    <TITLE>Associate Administrator for Rulemaking.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22737 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>73</VOL>
    <NO>188</NO>
    <DATE>Friday, September 26, 2008</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="55811"/>
                <AGENCY TYPE="F">AGENCY FOR INTERNATIONAL DEVELOPMENT </AGENCY>
                <SUBJECT>Bureau for Democracy, Conflict and Humanitarian Assistance; Office of Food for Peace; Announcement of Draft Food for Peace Pub. L. 480 Title II; Program Policies and Proposal Guidelines (FY09); Notice </SUBJECT>
                <P>Pursuant to the Food for Peace Act of 2008 (Pub. L. 480, as amended), notice is hereby given that the Draft Food for Peace Pub. L. 480 Title II Program Policies and Proposal Guidelines (FY 09) are being made available to interested parties for the required thirty (30) day comment period. </P>
                <P>
                    The draft guidelines may be found at 
                    <E T="03">http://www.usaid.gov/our_work/humanitarian_assistance/ffp/</E>
                    . Individuals who wish to receive a hard copy of these draft guidelines should contact: Office of Food for Peace, U.S. Agency for International Development, RRB 7.06-136, 1300 Pennsylvania Avenue, NW., Washington, DC 20523-7600. Individuals who have questions or comments on the draft guidelines should contact both Juli Majernik (at the above address, by phone at (202) 712-4088, or by e-mail at 
                    <E T="03">jmajernik@usaid.gov)</E>
                     and copy AMEX International, Inc., at 
                    <E T="03">ffpdocs@amexdc.com</E>
                    . The thirty day comment period will begin on the date that this announcement is published in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <SIG>
                    <NAME>Dale Skoric, </NAME>
                    <TITLE>Office of Food for Peace, Bureau for Democracy, Conflict and Humanitarian Assistance.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22036 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6116-01-M </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Food and Nutrition Service </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request—Special Supplemental Nutrition Program for Women, Infants and Children (WIC) Forms: FNS-698, FNS-699, and FNS-700; The Integrity Profile (TIP) </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Nutrition Service (FNS), USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, this notice invites the general public and other public agencies to comment on this proposed information collection. </P>
                    <P>Each year the Food and Nutrition Service (FNS) prepares an analysis, The Integrity Profile (TIP) Report, of WIC State agency efforts to detect potential fraud, waste and abuse committed by their authorized food vendors and the actions taken to remove vendors who commit program violations. The analysis presents data reported by 90 WIC State agencies, which includes 50 geographic State agencies, 34 Indian Tribal Organization State agencies, the District of Columbia, Puerto Rico, Guam, American Samoa, the Commonwealth of Northern Marianas, and the Virgin Islands. State agencies use a Web-based system to report this information. The reporting burden is comprised of three automated forms, the FNS-698, FNS-699, and FNS-700. The FNS-698 and FNS-699 are used to report State agency summary data, whereas the FNS-700 is used to capture information on each authorized vendor. The number of vendors authorized by each State agency varies from State to State. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be received on or before November 25, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments are invited on: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions that were used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on those who are to respond, including use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology. </P>
                    <P>FNS invites interested persons to submit comments on this notice. Comments may be submitted by any of the following methods: </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Send comments to Patricia Daniels, Director, Supplemental Food Programs Division, Food and Nutrition Service, U.S. Department of Agriculture, 3101 Park Center Drive, Room 520, Alexandria, VA 22302. 
                    </P>
                    <P>
                        • 
                        <E T="03">Facsimile:</E>
                         Comments may also be submitted via fax to the attention of Patricia Daniels at (703) 305-2196. 
                    </P>
                    <P>
                        • 
                        <E T="03">E-mail:</E>
                         Send comments to 
                        <E T="03">WICHQ-SFPD@fns.usda.gov.</E>
                         Include title in the subject line of the message. 
                    </P>
                    <P>All written comments will be open for public inspection at the Food and Nutrition Service headquarters office during regular business hours (8:30 a.m. to 5 p.m. Monday through Friday) at 3101 Park Center Drive, Room 520, Alexandria, Virginia 22302. </P>
                    <P>All responses to this notice will be summarized and included in the request for Office of Management and Budget approval. All comments will be a matter of public record. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Requests for additional information or copies of this information collection should be directed to Patricia N. Daniels at (703) 305-2746. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     The Integrity Profile (TIP). 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0584-0401. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     FNS-698, FNS-699, and FNS-700. 
                </P>
                <P>
                    <E T="03">Expiration Date:</E>
                     January 31, 2009. 
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     State agencies administering the Special Supplemental Nutrition Program for Women, Infants and Children (WIC) are required by 7 CFR 246.12(j)(5) to submit to FNS an annual summary of the results of their vendor monitoring efforts in order to provide Congress, senior FNS officials, as well as the general public, assurance that every reasonable effort is being made to ensure integrity in the WIC Program. Since 1989, WIC State agencies have 
                    <PRTPAGE P="55812"/>
                    been required to submit such data annually. In the last recordkeeping submission for TIP, 89 WIC State agencies administered the program. Currently, 90 WIC State agencies administer the program. An adjustment has been made to the burden hours due to: (1) An increase of the number of WIC State agencies reporting, (2) a reduction in the number of vendor records, and (3) a change in the methodology used to calculate burden. The change in burden hours from 4,144 to 3,672 results in a net reduction of 472 burden hours. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     WIC State agencies. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     90. 
                </P>
                <P>
                    <E T="03">Estimated Number of Responses per Respondent:</E>
                     One. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Responses:</E>
                     90. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     3,672 hours. 
                </P>
                <SIG>
                    <DATED>Dated: September 16, 2008. </DATED>
                    <NAME>Roberto Salazar, </NAME>
                    <TITLE>Administrator, Food and Nutrition Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22694 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-30-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Grain Inspection, Packers and Stockyards Administration </SUBAGY>
                <SUBJECT>Solicitation of Nominations for Members of the Grain Inspection Advisory Committee </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Grain Inspection, Packers and Stockyards Administration, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice to solicit nominees. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Grain Inspection, Packers and Stockyards Administration (GIPSA) is seeking nominations for individuals to serve on the Grain Inspection Advisory Committee (Advisory Committee). The Advisory Committee meets twice annually to advise GIPSA on the programs and services it delivers under the U.S. Grain Standards Act. Recommendations by the Advisory Committee help GIPSA better meet the needs of its customers who operate in a dynamic and changing marketplace. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>GIPSA will consider nominations received by November 25, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit nominations for the Advisory Committee by completing form AD-755. Nominations may be submitted by: </P>
                    <P>
                        • 
                        <E T="03">E-Mail: Terri.L.Henry@usda.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Terri Henry, GIPSA, USDA, 1400 Independence Ave., SW., Room 1633-S, Stop 3642, Washington, DC 20250-3642. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 690-2173. 
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery or Courier:</E>
                         Terri Henry, GIPSA, USDA, 1400 Independence Ave., SW., Room 1633-S, Stop 3642, Washington, DC 20250-3642. 
                    </P>
                    <P>
                        • 
                        <E T="03">Internet:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov</E>
                         and follow the online instructions for submitting comments. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Terri L. Henry, telephone (202) 205-8281 or e-mail 
                        <E T="03">Terri.L.Henry@usda.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>As required by section 21 of the United States Grain Standards Act (USGSA) (7 U.S.C. 87j) as amended, the Secretary of Agriculture established the Grain Inspection Advisory Committee on September 29, 1981, to provide advice to the GIPSA Administrator on implementation of the USGSA. The current authority for the Advisory Committee expires on September 30, 2015. As specified in the USGSA, each member's term is 3 years and no member may serve successive terms. </P>
                <P>As required by the USGSA, the Advisory Committee consists of 15 members, appointed by the Secretary, who represent the interests of grain producers, processors, handlers, merchandisers, consumers, exporters, and scientists with expertise in research related to the policies in section 2 of the USGSA (7 U.S.C. 74). Members of the Advisory Committee serve without compensation. GIPSA may reimburse members for travel expenses, including per diem in lieu of subsistence, for travel away from their homes or regular places of business in performance of Advisory Committee service (see 5 U.S.C. 5703). </P>
                <P>
                    A list of current Advisory Committee members and other relevant information are available on the GIPSA Web site at 
                    <E T="03">http://www.gipsa.usda.gov</E>
                    . Under the section “I Want To * * *” select “Learn about the Advisory Committee.” 
                </P>
                <P>GIPSA is seeking nominations for individuals to serve on the Advisory Committee to replace six members and three alternate members whose terms will expire in March 2009. </P>
                <P>
                    Persons interested in serving on the Advisory Committee or nominating another individual to serve, may contact: Terri L. Henry by telephone at 202-205-8281, by fax at 202-690-2173, or by electronic mail at 
                    <E T="03">Terri.L.Henry@usda.gov</E>
                     to request Form AD-755. Form AD-755 may also be obtained via GIPSA's Web site at 
                    <E T="03">http://www.gipsa.usda.gov</E>
                    . Under the section “I Want To * * *” select “Learn about the Advisory Committee,” then select Form AD-755. Nominations are open to all individuals without regard to race, color, religion, gender, national origin, age, mental or physical disability, marital status, or sexual orientation. To ensure that recommendations of the Advisory Committee take into account the needs of the diverse groups served by the USDA, membership shall include, to the extent practicable, individuals with demonstrated ability to represent minorities, women, and persons with disabilities. 
                </P>
                <P>The final selection of Advisory Committee members and alternates is made by the Secretary of Agriculture. </P>
                <SIG>
                    <NAME>James E. Link, </NAME>
                    <TITLE>Administrator, Grain Inspection, Packers and Stockyards Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22675 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-KD-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMITTEE FOR PURCHASE FROM PEOPLE WHO ARE BLIND OR SEVERELY DISABLED </AGENCY>
                <SUBJECT>Procurement List Additions and Deletions </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Addition to and Deletions From Procurement List. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action adds to the Procurement List a service to be furnished by nonprofit agencies employing persons who are blind or have other severe disabilities, and deletes from the Procurement List products previously furnished by such agencies. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         October 26, 2008. 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled, Jefferson Plaza 2, Suite 10800, 1421 Jefferson Davis Highway, Arlington, Virginia 22202-3259. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kimberly M. Zeich, Telephone: (703) 603-7740, Fax: (703) 603-0655, or e-mail 
                        <E T="03">CMTEFedReg@AbilityOne.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Additions </HD>
                <P>On August 1, 2008, the Committee for Purchase From People Who Are Blind or Severely Disabled published notice (73 F.R. 44960-44961) of proposed additions to the Procurement List. </P>
                <P>
                    After consideration of the material presented to it concerning capability of qualified nonprofit agencies to provide the service and impact of the additions on the current or most recent contractors, the Committee has determined that the services listed 
                    <PRTPAGE P="55813"/>
                    below are suitable for procurement by the Federal Government under 41 U.S.C. 46-48c and 41 CFR 51-2.4. 
                </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act Certification </HD>
                <P>I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were: </P>
                <P>1. The action will not result in any additional reporting, recordkeeping or other compliance requirements for small entities other than the small organizations that will furnish the service to the Government. </P>
                <P>2. The action will result in authorizing small entities to furnish the service to the Government. </P>
                <P>3. There are no known regulatory alternatives which would accomplish the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 46-48c) in connection with the service proposed for addition to the Procurement List. </P>
                <HD SOURCE="HD1">End of Certification </HD>
                <P>Accordingly, the following service is added to the Procurement List: </P>
                <EXTRACT>
                    <HD SOURCE="HD2">Services: </HD>
                    <FP SOURCE="FP-2">Service Type/Location: Custodial Services,  Walter Reed Army Medical Center, Glen Haven Annex and Forest Glen Annex, excluding Main Hospital and Armed Forces Pathology Institute,  6900 Georgia Avenue, Washington, DC.</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         MVLE, Inc., Springfield, VA. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         Dept of the Army, National Region Contract Office, Washington, DC. 
                    </FP>
                </EXTRACT>
                <HD SOURCE="HD1">Deletions </HD>
                <P>On July 18, 2008, the Committee for Purchase From People Who Are Blind or Severely Disabled published notice (73 F.R. 41313-41314) of proposed deletions to the Procurement List. </P>
                <P>After consideration of the relevant matter presented, the Committee has determined that the products listed below are no longer suitable for procurement by the Federal Government under 41 U.S.C. 46-48c and 41 CFR 51-2.4. </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act Certification </HD>
                <P>I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were: </P>
                <P>1. The action will not result in additional reporting, recordkeeping or other compliance requirements for small entities. </P>
                <P>2. The action may result in authorizing small entities to furnish the products to the Government. </P>
                <P>3. There are no known regulatory alternatives which would accomplish the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 46-48c) in connection with the products deleted from the Procurement List. </P>
                <HD SOURCE="HD1">End of Certification </HD>
                <P>Accordingly, the following products are deleted from the Procurement List: </P>
                <EXTRACT>
                    <HD SOURCE="HD2">Products </HD>
                    <HD SOURCE="HD3">BioRenewable Cleaners </HD>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         4510-00-NIB-0014—Waterless Hand Cleaner Dispenser. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         8520-00-NIB-0097—BioRenewables Waterless Plus Hand Cleaner Intro. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         8520-00-NIB-0096—BioRenewables Waterless Hand Cleaner Refill. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         8520-00-NIB-0095—BioRenewables Waterless Hand Cleaner Intro. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         8520-00-NIB-0094—BioRenewables Waterless Plus Hand Cleaner Refill. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         Susquehanna Association for the Blind and Visually Impaired, Lancaster, PA. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         GSA/FAS Southwest Supply Center (QSDAC), Fort Worth, TX. 
                    </FP>
                    <HD SOURCE="HD3">Transparency Film, Xerographic </HD>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         7530-01-386-2376—Transparency Film, Xerographic w/Strip. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         Industries of the Blind, Inc., Greensboro, NC. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         GSA/FSS OFC SUP CTR—Paper Products, New York, NY. 
                    </FP>
                    <HD SOURCE="HD3">Brake Pad Assembly </HD>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         2530-01-255-4215—Brake Pad Assembly. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         Arizona Industries for the Blind, Phoenix, AZ. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         U.S. Army Tank-Automotive and Armaments Command, Rock Island, IL. 
                    </FP>
                    <HD SOURCE="HD3">Tracheotomy Care Kit </HD>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         6515-01-174-8844—Tracheotomy Care Kit. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         Washington-Greene County Branch, PAB, Washington, PA. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         Department of Veterans Affairs, National Acquisition Center, Hines, IL. 
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Kimberly M. Zeich, </NAME>
                    <TITLE>Director, Program Operations.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22686 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6353-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>Foreign-Trade Zones Board </SUBAGY>
                <DEPDOC>[Docket 24-2008] </DEPDOC>
                <SUBJECT>Foreign-Trade Zone 161—Sedgwick County, KS; Amendment to Application for Subzone Status; Hawker Beechcraft Corporation (Aircraft Manufacturing), Wichita and Salina, KS </SUBJECT>
                <P>A request has been submitted to the Foreign-Trade Zones Board (the Board) by Hawker Beechcraft Corporation (HBC) to amend the company's application requesting special-purpose subzone status for the company's aircraft manufacturing facilities located in Wichita and Salina, Kansas. </P>
                <P>
                    HBC is now requesting to correct the HTSUS number for the finished product as described in the original 
                    <E T="04">Federal Register</E>
                     notice (Docket 24-2008, 73 FR 21903-21904, 4/23/08) to accurately reflect the category of aircraft that are produced at the company's facilities. The correct HTSUS number should be 8802.30 (airplanes and other aircraft of an unladen weight exceeding 2,000 kg but not exceeding 15,000 kg). There is no change to the duty rate (duty-free) and the finished products will be manufactured using the same imported parts and components (duty-free to 15 percent) as described in the original 
                    <E T="04">Federal Register</E>
                     notice. 
                </P>
                <P>Public comment is invited from interested parties. Submissions (original and 3 copies) shall be addressed to the Board's Executive Secretary at the address listed below. The closing period for their receipt is October 27, 2008. Rebuttal comments in response to material submitted during the foregoing period may be submitted during the subsequent 15-day period (to November 10, 2008). </P>
                <P>
                    A copy of the application amendment will be available at each of the following addresses: U.S. Department of Commerce Export Assistance Center, 150 North Main Street, Suite 200, Wichita, Kansas; and, Office of the Executive Secretary, Foreign-Trade Zones Board, Room 2111, U.S. Department of Commerce, 1401 Constitution Avenue, NW., Washington, DC 20230. For further information contact Christopher Kemp at 
                    <E T="03">christopher_kemp@ita.doc.gov</E>
                     or (202) 482-0862. 
                </P>
                <SIG>
                    <DATED>Dated: September 19, 2008. </DATED>
                    <NAME>Andrew McGilvray, </NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22716 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>(A-570-868)</DEPDOC>
                <SUBJECT>Folding Metal Tables and Chairs from the People's Republic of China: Notice of Partial Rescission of Antidumping Duty Administrative Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce</P>
                </AGY>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>September 26, 2008.</P>
                </EFFDATE>
                <FURINF>
                    <PRTPAGE P="55814"/>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lilit Astvatsatrian, AD/CVD Operations, Office 8, Import Administration, Room 1870, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, NW, Washington, DC 20230; telephone: (202) 482-6412.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On June 9, 2008, the Department of Commerce (“the Department”) published a notice of opportunity to request an administrative review of the antidumping duty order on folding metal tables and chairs (“FMTCs”) from the People's Republic of China (“PRC”). 
                    <E T="03">See Antidumping or Countervailing Duty Order, Finding, or Suspended Investigation: Opportunity to Request Administrative Review</E>
                    , 73 FR 32557 (June 9, 2008). On June 23, 2008, Meco Corporation (“Meco”), a domestic producer of the like product, requested that the Department conduct an administrative review of Dongguan Shichang Metals Factory Co. Ltd. (“Shichang”). The Department published a notice of initiation of the antidumping duty administrative review of FMTCs from the PRC for the period June 1, 2007, through May 31, 2008. 
                    <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews, Request for Revocation in Part, and Deferral of Administrative Review</E>
                    , 73 FR 44220 (July 30, 2008).
                </P>
                <HD SOURCE="HD1">Rescission of Review</HD>
                <P>
                    Pursuant to 19 CFR 351.213(d)(1), the Secretary will rescind an administrative review, in whole or in part, if the party that requested the review withdraws the request within 90 days of the date of publication of the notice of initiation of the requested review. On August 11, 2008, Meco timely withdrew its request for an administrative review of Shichang (
                    <E T="03">i.e.</E>
                    , within 90 days of the publication of the notice of initiation of this review). Because Meco was the only requesting party of an administrative review with respect to Shichang, the Department hereby rescinds the administrative review of FMTCs with respect to Shichang, in accordance with 19 CFR 351.213(d)(1). The Department intends to issue assessment instructions to U.S. Customs and Border Protection 15 days after the publication of this notice of partial rescission of administrative review.
                </P>
                <HD SOURCE="HD1">Notification to Importers</HD>
                <P>This notice serves as a final reminder to importers of their responsibility under section 351.402(f) of the Department's regulations to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in the Secretary's assumption that reimbursement of antidumping duties occurred and subsequent assessment of double antidumping duties.</P>
                <P>This notice is issued and published in accordance with section 777(i) of the Tariff Act of 1930, as amended, and 19 CFR 351.213(d)(4).</P>
                <SIG>
                    <DATED>Dated: September 19, 2008.</DATED>
                    <NAME>Stephen J. Claeys,</NAME>
                    <TITLE>Deputy Assistant Secretary for Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22711 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>International Trade Administration </SUBAGY>
                <DEPDOC>[A-570-836] </DEPDOC>
                <SUBJECT>Glycine From the People's Republic of China: Final Results of Antidumping Duty Administrative Review </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce. </P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On April 4, 2008, the Department of Commerce (“Department”) published the preliminary results and partial rescission of the 2006-2007 administrative review of the antidumping duty order on glycine from the People's Republic of China (“PRC”). 
                        <E T="03">See Glycine from the People's Republic of China: Preliminary Results of Antidumping Duty Administrative Review and Partial Rescission</E>
                        , 73 FR 18503 (April 4, 2008) (“
                        <E T="03">Preliminary Results</E>
                        ”). We gave interested parties an opportunity to comment on the 
                        <E T="03">Preliminary Results</E>
                        . Based upon our analysis of the comments and information received, we made changes to the margin calculation for the final results. We find that certain manufacturers/exporters sold subject merchandise at less than normal value during the period of review (“POR”) March 1, 2006, through February 28, 2007. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         September 26, 2008. 
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Erin Begnal or Toni Dach, AD/CVD Operations, Office 9, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, NW., Washington, DC 20230; telephone: (202) 482-1442 or (202) 482-1655, respectively. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>
                    The following events have occurred subsequent to the publication of the 
                    <E T="03">Preliminary Results</E>
                    . On April 10, 2008, the Department issued Baoding Mantong Fine Chemistry Co., Ltd. (“Baoding Mantong) a supplemental questionnaire, and Baoding Mantong submitted its response to the Department's supplemental questionnaire on April 17, 2008. On April 24, 2008, the Department extended the deadline for submitting surrogate value (“SV”) information, and for submitting case briefs and rebuttal briefs. On April 30, 2008, the Department further extended the deadline for submitting case briefs and rebuttal briefs. 
                </P>
                <P>
                    On May 8, 2008, parties submitted SV comments, and on May 19, 2008, Geo Specialty Chemicals Inc. (“Petitioner”) submitted rebuttal comments. On May 19, 2008, Baoding Mantong submitted its case brief, and on May 28, 2008, Petitioner submitted its case brief. On June 3, 2008, Baoding Mantong submitted its rebuttal brief, and on June 4, 2008, Petitioner submitted its rebuttal brief. On June 18, 2008, the Department rejected Baoding Mantong's rebuttal brief for containing new factual information, which Baoding Mantong resubmitted on June 19, 2008. On July 15, 2008, we extended the time limit for the completion of the final results of this review by thirty days until September 2, 2008. 
                    <E T="03">See Notice of Extension of Time Limit for Final Results of the Antidumping Duty Administrative Review: Glycine from the People's Republic of China</E>
                    , 73 FR 40480 (July 15, 2008). On August 29, 2008, we extended the time limit for completion of the final results by an extra 17 days until September 19, 2008. 
                    <E T="03">See Notice of Extension of Time Limit for Final Results of the Antidumping Duty Administrative Review: Glycine from the People's Republic of China</E>
                    , 73 FR 50939 (August 29, 2008). 
                    <E T="03">Scope of the Order</E>
                </P>
                <P>
                    The product covered by the order is glycine, which is a free-flowing crystalline material, like salt or sugar. Glycine is produced at varying levels of purity and is used as a sweetener/taste enhancer, a buffering agent, reabsorbable amino acid, chemical intermediate, and a metal complexing agent. This review covers glycine of all purity levels. Glycine is currently classified under subheading 2922.49.4020 of the Harmonized Tariff Schedule of the United States (“HTSUS”). Although the HTSUS 
                    <PRTPAGE P="55815"/>
                    subheading is provided for convenience and Customs purposes, the written description of the merchandise under the order is dispositive. 
                </P>
                <HD SOURCE="HD1">Analysis of Comments Received </HD>
                <P>
                    All issues raised in the briefs are addressed in the Issues and Decision Memorandum for the Final Results in the 2006-2007 Administrative Review of Glycine from the People's Republic of China from Stephen J. Claeys, Deputy Assistant Secretary, to David M. Spooner, Assistant Secretary, dated September 19, 2008, (“I&amp;D Memo”), which is hereby adopted by this notice. A list of the issues raised, all of which are addressed in the I&amp;D Memo, is attached to this notice as Appendix I. Parties can find a complete discussion of all issues raised in the briefs and the corresponding recommendations in this public memorandum, which is on file in the Central Records Unit (“CRU”), room 1117 of the Department of Commerce. In addition, a complete version of the I&amp;D Memo can be accessed directly on the Web at 
                    <E T="03">http://trade.gov/ia</E>
                    . The paper copy and electronic version of the I&amp;D Memo are identical in content. 
                </P>
                <HD SOURCE="HD1">Separate Rates </HD>
                <P>
                    Baoding Mantong requested a separate, company-specific antidumping duty rate. In the 
                    <E T="03">Preliminary Results</E>
                    , we found that Baoding Mantong met the criteria for the application of a separate antidumping duty rate. 
                    <E T="03">Preliminary Results</E>
                    , 73 FR at 18505. Therefore, the Department has applied a rate to Baoding Mantong separate from the rate established for the PRC-wide entity. Also in the 
                    <E T="03">Preliminary Results</E>
                    , the Department found that Nantong Dongchang Chemical Industry Corporation (“Nantong Dongchang”) ceased to participate in the administrative review without having demonstrated its entitlement to a separate rate. 
                    <E T="03">Id</E>
                    . Accordingly, Nantong Dongchang does not qualify for separate rate status, but rather is appropriately considered to be part of the PRC-wide entity which is assigned a rate of 155.89 percent based on facts otherwise available with an adverse inference (“AFA”). 
                    <E T="03">Id</E>
                    . The Department did not receive comments on this issue prior to these final results. 
                </P>
                <HD SOURCE="HD1">Use of Facts Otherwise Available and the PRC-Wide Rate </HD>
                <P>
                    As noted above, the Department found that Nantong Dongchang did not establish its eligibility for separate rate status, and thus is deemed to be part of the PRC-wide entity. Also, in the 
                    <E T="03">Preliminary Results</E>
                    , the Department noted that Nantong Dongchang ceased participating in the administrative review, and did not respond to any portions of the Department's questionnaires. As the Department found that the PRC-wide entity, which includes Nantong Dongchang, failed to cooperate to the best of its ability in responding to the Department's requests for information and thereby impeded the Department's proceeding, the Department assigned the PRC-wide entity a rate based on AFA pursuant to sections 776(a)(2)(A), (B), and (C) and section 776(b) of the Tariff Act of 1930, as amended (“the Act”). 
                    <E T="03">See Preliminary Results</E>
                     at 73 FR at 18506. The Department did not receive any comments regarding its preliminary application of AFA to the PRC-wide entity. 
                    <E T="03">See Preliminary Results</E>
                    , 73 FR at 18505-18507. Therefore, for these final results, the Department has not altered its analysis or decision to apply total AFA to the PRC-wide entity. 
                </P>
                <HD SOURCE="HD1">Changes Since the Preliminary Results</HD>
                <P>Based on our analysis of information on the record of this review, and comments received from the interested parties, we have made changes to the margin calculations for Baoding Mantong. </P>
                <P>
                    We have made modifications to our selecetion of certain SVs used in the 
                    <E T="03">Preliminary Results</E>
                    . The values that were modified for these final results are those for steam coal, acetic acid, liquid chlorine, and the surrogate financial ratios. For further details 
                    <E T="03">see</E>
                     I&amp;D Memo at Comments 1, 2, 4, and 5, and Memorandum to the File through Scot T. Fullerton, Program Manager, Office 9 from Toni Dach, International Trade Analyst, Office 9, regarding, “Administrative Review of Glycine from the People's Republic of China: Surrogate Values for the Final Results,” dated September 19, 2008. 
                </P>
                <P>We determine that the following antidumping duty margins exist for the period of March 1, 2006, through February 28, 2007: </P>
                <GPOTABLE COLS="02" OPTS="L2,tp0,i1" CDEF="s30,9">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Exporter</CHED>
                        <CHED H="1">
                            Margin
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Baoding Mantong Fine Chemistry Co., Ltd.</ENT>
                        <ENT>52.02</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PRC-Wide Rate (including Nantong Dongchang Chemical Industry Corporation)</ENT>
                        <ENT>155.89</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Assessment Rates </HD>
                <P>Pursuant to section 751(a)(2)(A) of the Act and 19 CFR 351.212(b)(1), the Department will determine, and U.S. Customs and Border Protection (“CBP”) shall assess, antidumping duties on all appropriate entries. The Department intends to issue assessment instructions to CBP 15 days after the date of publication of these final results of review. </P>
                <HD SOURCE="HD1">Cash Deposit Requirements </HD>
                <P>The following cash deposit requirements will be effective upon publication of this notice of final results of administrative review for all shipments of glycine from the PRC entered, or withdrawn from warehouse, for consumption on or after the date of publication, as provided by section 751(a)(2)(C) of the Act: (1) For Baoding Mantong, which has a separate rate, the cash deposit rate will be the company-specific rate shown above; (2) for previously reviewed or investigated companies not listed above that have a separate rate, the cash deposit rate will continue to be the company-specific rate published for the most recent period; (3) the cash deposit rate for all other PRC exporters will be 155.89 percent, the current PRC-wide rate; and (4) the cash deposit rate for all non-PRC exporters will be the rate applicable to the PRC exporter that supplied that exporter. These cash deposit requirements shall remain in effect until further notice. </P>
                <HD SOURCE="HD1">Notification to Interested Parties </HD>
                <P>This notice serves as the final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in the Secretary's presumption that reimbursement of antidumping duties occurred and in the subsequent assessment of double antidumping duties. </P>
                <P>This notice also serves as the only reminder to parties subject to administrative protective order (“APO”) of their responsibility concerning the return/destruction or conversion to judicial protective order of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3). Failure to comply is a violation of the APO. </P>
                <P>This notice of final results is issued and published in accordance with sections 751(a)(1) and 777(i)(1) of the Act. </P>
                <SIG>
                    <PRTPAGE P="55816"/>
                    <DATED>Dated: September 19, 2008. </DATED>
                    <NAME>David M. Spooner, </NAME>
                    <TITLE>Assistant Secretary for Import Administration.</TITLE>
                </SIG>
                <APPENDIX>
                    <HD SOURCE="HED">Appendix I </HD>
                    <HD SOURCE="HD2">List of Issues </HD>
                    <FP SOURCE="FP-1">Comment 1: Surrogate Value for Steam Coal. </FP>
                    <FP SOURCE="FP-1">Comment 2: Surrogate Value for Acetic Acid. </FP>
                    <FP SOURCE="FP-1">Comment 3: Surrogate Value for Ammonia. </FP>
                    <FP SOURCE="FP-1">Comment 4: Surrogate Financial Ratios. </FP>
                    <FP SOURCE="FP-1">Comment 5: Surrogate Value for Chlorine. </FP>
                    <FP SOURCE="FP-1">Comment 6: Surrogate Value for Truck Freight. </FP>
                </APPENDIX>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22714 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[Docket No. 0808271163; RIN 0648-ZA70]</DEPDOC>
                <SUBJECT>NOAA Community-based Restoration Program Guidelines</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On August 24, 2005 NOAA published a notice in the 
                        <E T="04">Federal Register</E>
                         that announced revisions to guidelines for the Community-based Restoration Program (Program). The notice requested public comment on proposed updates to the guidelines that describe how the Program is implemented, and notified the public about a constituent feedback meeting that was scheduled for September 13, 2005 in Washington DC. This notice makes minor changes to the previously published guidelines and responds generally to the comments received, summarizes the constituent feedback meeting in Washington, D.C., and highlights specific authorization for the Program established in the Magnuson-Stevens Fishery Conservation and Management Reauthorization Act of 2006. NOAA expects to periodically update these guidelines every 3 to 5 years to reflect the evolution of the Program. This is not a solicitation of project proposals.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Robin Bruckner, (301) 713-0174, or by e-mail at 
                        <E T="03">Robin.Bruckner@noaa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The NOAA Community-based Restoration Program (Program) was established in 1996. Proposed Guidelines for the Program were first published in the 
                    <E T="04">Federal Register</E>
                     on October 1, 1999 (64 FR 53339). In that document, comments were sought on modifications to the Program that would allow greater flexibility to support community-based habitat restoration projects. Final Program Guidelines, including responses to comments, were published on March 30, 2000 (65 FR 16890). In the time since the original guidelines were issued, the Program has: experienced an increase in base funding; emphasized certain techniques through targeted initiatives, such as fish passage and marine debris prevention and removal, to expand benefits to aquatic resources; undertaken projects in new geographic locations; increased its focus on ecosystem-based approaches to management; and generally has implemented increased numbers of locally initiated, grass-roots habitat restoration projects through partnerships at the local, regional and national levels. The Program is now specifically authorized through the Magnuson-Stevens Fishery Conservation and Management Reauthorization Act of 2006 on January 12, 2007. The NOAA Restoration Center (Restoration Center) within NMFS is issuing revised Program guidelines, which include measures that are in place or planned to enable the Program to demonstrate increased accountability for the expenditure of public dollars.
                </P>
                <HD SOURCE="HD1">Responses to Comments</HD>
                <P>The Program received comments from three entities during the comment period (August 24, 2005 through October 11, 2005). A private individual, Trout Unlimited, and the Massachusetts Division of Marine Fisheries submitted comments. Comments are summarized below, by commenter, with responses.</P>
                <P>
                    <E T="03">Comment 1</E>
                    : The first commenter noted the Program had reached $13 million in appropriations and inquired about the Program's accomplishments in 2004. Specifically, the commenter requested names and locations of projects, the amount of money spent, and what was accomplished (e.g. acres restored).
                </P>
                <P>
                    Response: Project-specific information is made available to the public via the “Funded Projects” section of the Restoration Center website at: 
                    <E T="03">http://seahorse2.nmfs.noaa.gov/hcrcdb_app/class/</E>
                    . Projects can be viewed by location, habitat type, or partnership. Project names, locations, funding recipients, award amounts and year awarded, project partners and contacts, and a summary of each project's goals, objectives and results can be found there.
                </P>
                <P>
                    <E T="03">Comment 2</E>
                    : Trout Unlimited offered full support for the proposed Program changes, and emphasized the most beneficial changes. These included: (1) the requirement for project partners to provide detailed project information for the Restoration Center database; (2) the requirement for science-based monitoring where appropriate as supported by the Estuaries and Clean Waters Act of 2000; (3) consideration of habitat restoration in the Great Lakes region; and (4) the increase of upper and lower funding ranges for financial assistance for projects.
                </P>
                <P>
                    <E T="03">Response</E>
                    : NOAA agrees with the commenter that the proposed changes: (1) are essential to evaluate progress of work funded by the Program; (2) represent a long-term commitment of the Program to measure project outcomes such as improvements in habitat productivity and fish populations; (3) represent a reasonable direction for the Program expansion (into the Great Lakes, dependant on Congressional appropriations) given NOAA's traditional responsibilities for habitat restoration in large aquatic systems; and (4) increases efficiency and cost-effectiveness of the Program. Regarding the fourth point, since small projects often require the same level of NOAA staff support to ensure environmental compliance as do larger projects, they have become less cost-effective. NOAA agrees with the commenter that national and regional partnerships can provide smaller awards more cost-effectively as part of larger, more comprehensive restoration activities.
                </P>
                <P>
                    <E T="03">Comment 3</E>
                    : The Massachusetts Division of Marine Fisheries (MADMF) was generally very supportive of the goals and efforts of programs within NOAA Fisheries Office of Habitat Conservation, and offered specific comments in the context of improving federal-state communication and project execution. The commenter: (1) requested clarification of state-federal interactions to ensure the objectives of the Program are consistent with existing state authority and objectives for anadromous and marine fisheries resources; (2) requested a process that would allow the state to provide technical comments and approval on project proposals and designs, and suggested that NOAA require support letters from the state agency with responsibility over the target resources; (3) suggested that formal partnerships between NOAA and state agencies be established to provide a streamlined and dedicated annual funding source for ongoing state programs that routinely address priority anadromous fish restoration projects; and (4) suggested that improvements were needed in the coordination between the Program and 
                    <PRTPAGE P="55817"/>
                    state agencies that hold the statutory authority to manage the [target] resources, so as to avoid a duplication of effort, with a recommendation to increase funding to assist state efforts rather than cultivating federal expertise.
                </P>
                <P>
                    <E T="03">Response</E>
                    : (1) NOAA's Community-based Restoration Program has provided financial and technical assistance for on-the-ground habitat restoration projects in 26 states, Canada, the Caribbean and the Pacific Islands to benefit marine and coastal resources and anadromous fish. The Restoration Center has technical staff in 20 locations around the Unites States that ensure NOAA-funded habitat restoration projects are consistent with existing state authority and objectives for coastal and marine fisheries resources. Program staff makes a point to ensure early and continuous coordination with other federal and state agencies. (2) Since inception of the Program, Notices of Funding Availability (NOFA) and Federal Funding Opportunities (FFO) have stressed the importance of letters of support. A complete application for a NOAA habitat restoration grant should include letters of support. Applicants are evaluated based in part on the commitment from the appropriate resource agency personnel that indicates that an agency has reviewed and supports the final proposal. (3) NOAA requires that discretionary funding be provided through fair and open competition. Competition ensures that projects are of the highest quality and offer significant ecological benefits. The Program announces competitive financial assistance annually through NOAA's Omnibus 
                    <E T="04">Federal Register</E>
                     Notice and 
                    <E T="03">www.grants.gov</E>
                     process, as well as through numerous national and regional habitat restoration partnerships. State agencies are eligible to compete for this funding and have equal opportunity to apply for support for individual projects as well as for larger partnership awards that are offered every 3 years. (4) In response to comments, the Program expanded its effort to involve MADMF in the review and oversight of the Program's anadromous fish restoration projects through the NMFS Northeast Regional Office in Gloucester, Massachusetts. The Program also sent a letter to the Director of the MADMF in April 2006 and proposed a meeting to discuss communication and opportunities to enhance coordination on habitat restoration policies, priorities and projects. NOAA recognizes that local project proponents do not always have the full suite of technical and project management skills to design, permit and implement a project. A cornerstone of the Program is its ability to provide technical assistance around the country for a wide range of habitat restoration activities, including assistance for projects that provide fish passage and habitat improvements for anadromous fish.
                </P>
                <HD SOURCE="HD1">Constituent Feedback</HD>
                <P>
                    On September 13, 2005, the Restoration Center held its first national stakeholder meeting on the Program in Washington, D.C. The meeting provided an open forum for public feedback on the Program and it was attended by 25 partner organizations from around the country. NOAA facilitators guided discussions around the following topic areas: revised program guidelines, technical assistance, restoration bottlenecks, and future programmatic priorities. The Program responded to this constituent feedback by publishing “NOAA's Community-based Restoration Program Stakeholder Meeting, Summary Report September 13, 2005, Washington, D.C.” This report is available upon request (see 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    ), and is organized into six thematic sections: Research and Monitoring, Regional Planning and Prioritization, Technical Assistance Needs, Funding and Program Growth, Interagency Coordinator/Permitting, and Outreach and Education.
                </P>
                <HD SOURCE="HD1">NOAA Community-based Restoration Program Guidelines</HD>
                <HD SOURCE="HD2">Background</HD>
                <P>This document replaces previous guidelines and describes the Program's implementation for FY 2009 and beyond. The comments and stakeholder meeting feedback have been considered and minor modifications to the Program guidelines are provided herein. The Program was recognized in the Magnuson-Stevens Fishery Conservation and Management Reauthorization Act of 2006 as an important means to implement and support the restoration of fishery and coastal habitats.</P>
                <P>Coastal areas contain the Nation's most diverse, valuable and at-risk habitats, which support 90% of ocean-dependent commercial and sport fish species, generate billions of recreation and tourism dollars annually, and protect coastal communities from storms, floods and other hazards. U.S. coastal wetlands reduce the damaging effects of hurricanes and other storms on coastal communities, providing more than $23 billion in annual storm protection services to cities and regions most vulnerable to hurricane and tropical storm surges. Recreational fishing is estimated to contribute between $10 billion and $26 billion each year.</P>
                <P>Degradation and loss of coastal and marine habitats threaten the long-term sustainability of the nation's fishery resources and the safety and economies of coastal communities. Protecting existing, undamaged habitat is a priority and should be combined with coastal habitat restoration to enhance the functionality of degraded habitat. Restored coastal habitat will help rebuild fisheries stocks and recover threatened and endangered species. Restoring marine and coastal habitats will help protect and revitalize coastal communities and ensure that valuable natural resources will be available to future generations of Americans.</P>
                <HD SOURCE="HD2">Program Overview</HD>
                <P>
                    NOAA initiated a Community-based Restoration Program (Program) in 1996 under general authorities within the Fish and Wildlife Coordination Act. The Program received specific authorization in the Magnuson-Stevens Fishery Conservation and Management Reauthorization Act of 2006 on January 12, 2007. The Program implements and supports the restoration of fishery and coastal habitats by providing Federal financial and technical assistance to encourage locally led coastal and marine habitat restoration, and to promote stewardship and conservation values for NOAA trust resources. The Program is a systematic national effort to foster partnerships at the national, regional and local level to implement sound habitat restoration. Partnerships are forged between government, not-for-profit organizations, community groups, recreational and commercial fishing organizations, students and educational institutions, businesses, youth conservation corps and private landowners. Under the Program, partners may contribute funding, land, technical assistance, workforce support or other in-kind services; promote local participation in habitat restoration activities; undertake research and monitoring to evaluate and improve project success; and facilitate stewardship for restored resources at the local level. To date, the Program has funded more than 1400 community-based habitat restoration projects in 27 states, Washington D.C., Canada, and the Caribbean. These projects have engaged 132,000 volunteers that have contributed 840,000 hours toward the restoration of over 33,000 acres of habitat and the opening of 1400 miles of rivers and streams for aquatic organisms.
                    <PRTPAGE P="55818"/>
                </P>
                <HD SOURCE="HD2">Electronic Access</HD>
                <P>
                    Information on the Program, including partnerships and projects that have been funded to date, can be found on the World Wide Web at: 
                    <E T="03">http://www.nmfs.noaa.gov/habitat/restoration</E>
                    . Project-specific information is linked off the Restoration Center database (RCDB) launched in 2001 to track habitat acres created, established, rehabilitated, enhanced or protected; stream miles made accessible to diadromous fish; volunteer or community participation hours; restoration techniques used; habitat types and species benefited; and other parameters for Restoration Center supported projects. The database has increased NOAA staff efficiency and allows the Restoration Center to respond quickly and accurately to Congressional, Administrative and constituent inquiries, such as those on Program performance measures, through reporting features that can calculate the acreage or stream miles restored by all projects completed in any particular year, for example. Subsequent enhancements to the database include additional fields related to environmental compliance, display and collection of project locations through a Geographic Information System (GIS) based mapping application, and revised parameters to facilitate data-sharing with the National Estuaries Restoration Inventory.
                </P>
                <HD SOURCE="HD2">Overview of Changes to the Program</HD>
                <P>Since the Program began, Congressional appropriations have increased from $250,000 in 1999 to a high of $13.7 million in 2005. To effectively manage this growth, to provide better service to constituents, and to accurately report on the Program's accomplishments, the Restoration Center has changed some of its practices and implemented a number of tools to increase efficiency and accountability.</P>
                <P>To evaluate the progress of the work proposed under Program awards, to determine whether projects were successfully completed, and to facilitate population of the database with project-specific information, the Restoration Center sought and received approval in 2004 from the Office of Management and Budget (OMB) to collect detailed project information from grantees. This information, such as restoration techniques used, species benefitted, geographic coordinates of project sites, and monitoring and outreach information, is now typically required as part of semi-annual progress reporting. The Restoration Center received renewed approval from OMB, under the Paperwork Reduction Act, to continue collecting this information through May 2009.</P>
                <P>The Restoration Center has also begun typically requiring science-based monitoring of restoration projects, where appropriate, in an effort to improve on-the-ground restoration efforts and increase Program effectiveness. Applicants requesting funding to implement on-the-ground habitat restoration projects that will result in structural or functional habitat changes should have clearly identified goals (broad in scope) and specific, measurable objectives. Evaluating these objectives to ensure a basic assessment of project success generally requires monitoring, during the project period, of at least one structural and one functional parameter, as supported by Title I of the Estuaries and Clean Waters Act of 2000 (Pub. L. 106-457). Assistance in refining the objectives and/or selecting appropriate parameters is available from Program staff, as well as from a new online Restoration Monitoring Planner available at http://www.habitat.noaa.gov/restoration/rmp. The NOAA Restoration Monitoring Planner guides restoration practitioners through the basic steps of developing a science-based monitoring plan, including hypothesis testing and assessment of a habitat's structure and function. A fact sheet with examples of structural and functional monitoring parameters is also available.</P>
                <P>In conjunction with science-based monitoring, the Program is beginning to assess and monitor the socio-economic benefits, aka human dimensions, of habitat restoration. A 2006 pilot study indicated that most individuals who engage in the Program's projects already possess a strong stewardship ethic. In future studies, the Program expects to learn more about the impact of such projects on individuals who are less environmentally aware. A separate human dimensions research area is establishing an economic baseline against which the economic benefits of habitat restoration over the long term can be measured. Using the results of these studies and others, the Program will finalize monitoring guidelines which will enable effective documentation of the socio-economic benefits of habitat restoration.</P>
                <P>Both the Restoration Center Database and implementation of minimum monitoring requirements support NOAA's strategic plan, specifically NOAA's Ecosystems mission support goal to “Protect, Restore, and Manage Use of Coastal and Ocean Resources through Ecosystem-Based Management”, and allow better project tracking and evaluation of performance measures. Revision of habitat-related and other relevant performance measures in coordination with all major NOAA programs involved with habitat restoration is ongoing through NOAA's Habitat Program.</P>
                <HD SOURCE="HD2">Program Goals and Objectives</HD>
                <P>According to the Magnuson-Stevens Fishery Conservation and Management Reauthorization Act of 2006, the goals and objectives that have defined the Program to date have not changed. These include:</P>
                <P>• Provide funding and technical expertise to fishery and coastal communities to assist them in restoring fishery and coastal habitat;</P>
                <P>• Advance the science and monitoring of coastal habitat restoration;</P>
                <P>• Transfer restoration technologies to the private sector, the public, and other governmental agencies;</P>
                <P>• Develop public-private partnerships to accomplish sound coastal restoration projects;</P>
                <P>• Promote significant community support and volunteer Participation in fishery and coastal habitat restoration;</P>
                <P>• Promote stewardship of fishery and coastal habitats; and</P>
                <P>• Leverage resources through national, regional, and local public-private partnerships.</P>
                <P>The Restoration Center uses cooperative agreements as a primary funding mechanism to accomplish habitat restoration. The Program will continue to award cooperative agreements based on a competitive, technical review process, whenever possible, to maximize opportunities for public access to Program resources. Partnerships with citizen groups, public and not-for-profit organizations, industry, corporations and businesses, youth conservation corps, students, landowners, and local government, and state and Federal agencies are supported through the provision of Federal financial and technical assistance. Cooperative agreements are awarded at two distinct levels individual (or direct) project funding and Restoration Partnerships.</P>
                <P>
                    Direct project funding is typically announced annually in NOAA's Omnibus 
                    <E T="04">Federal Register</E>
                     Notice. Direct project funding focuses on partnerships at the local level, providing awards to support individual habitat restoration projects, barrier removal projects, or marine debris prevention and removal projects, or a bundle of well developed, typically related projects, for up to 24 months. Specific information on these federal funding opportunities, including application 
                    <PRTPAGE P="55819"/>
                    requirements, eligibility, program priorities and other application submission requirements are posted on 
                    <E T="03">www.grants.gov</E>
                     as they are made available.
                </P>
                <P>
                    National and Regional Habitat Restoration Partnership funding is announced every 3 years through the NOAA Omnibus 
                    <E T="04">Federal Register</E>
                     Notice. Partnership awards are up to 36 months in duration, are usually larger than project awards, and specific projects are often not identified at the time of application. Partnership applications outline the concept and focus of habitat restoration activities and detail the mechanism under which individual projects will be identified and subsequently funded as subawards through the partner organization. Partner organizations assume the administrative responsibilities for subawards, such as letting contracts and managing progress and financial reports. This allows NOAA staff to focus on assisting with project implementation. The next solicitation for partnership applications is expected to be announced in summer 2009 for FY2010 funding.
                </P>
                <P>For the first time, the partnership review (for FY 2007-2009 funding consideration) was conducted as a two tier review process with both technical mail reviews followed by a panel review, which proved successful. The Restoration Center is likely to adopt this method of review for future partnership rounds, and may opt to use it for future project decision-making.</P>
                <P>Partners help identify and secure additional funding, land, technical assistance, workforce support or other in-kind services to enable citizens to improve locally important habitats that sustain living marine and coastal resources. Projects are most often implemented in coastal and nearshore marine and estuarine environments and in riverine environments that support diadromous fish; expansion of the Program to the Great Lakes is being considered, and will be dependent on the NOAA Habitat Program's goals and Congressional appropriations made for this purpose. It is anticipated that any projects supported in the Great Lakes region will fall under these Program guidelines.</P>
                <P>The Program places emphasis on habitat restoration projects with strong community support and recognizes the significant role that communities can play in habitat restoration and protection. Projects that incorporate citizens' “hands-on” involvement in project implementation, monitoring, or outreach and education are preferred. The role of NOAA in the Program is to strengthen the development and implementation of sound restoration projects. NOAA staff will continue to provide guidance and technical expertise on permitting, environmental compliance, engineering and design, and similar aspects required for project implementation.</P>
                <P>
                    NOAA seeks applications that demonstrate collaboration among entities such as nonprofit organizations, citizen groups, industry, youth conservation corps, students, landowners, academics, local government, and state, and federal agencies to implement habitat restoration activities. Project outcomes should include a net gain in habitat acres restored or stream miles re-established for diadromous fish passage. Successful applicants will typically be expected to document volunteer involvement and a maximization of project partnerships through leverage. Eligibility requirements will be detailed in annual solicitations published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>The Restoration Center is also exploring the feasibility of working more collaboratively with other federal agencies by developing joint interagency solicitation for applications. This would enable project proponents to submit a single application for consideration by multiple federal agencies, and would facilitate discussion amongst agencies on cooperative funding opportunities. It would also allow agencies to better leverage their respective financial and technical resources and help accomplish restoration in a more strategic fashion. Consolidation would be for the RFAs only; funding for recommended projects would need to be provided separately by the interested agency, as federal agencies have limited authority in most cases to transfer funds appropriated by Congress to another federal agency.</P>
                <HD SOURCE="HD2">Eligible Restoration Activities</HD>
                <P>Restoration may include, but is not limited to, improvement of coastal wetland tidal exchange or reestablishment of historic hydrology; dam or berm removal; improvement or reestablishment of fish passage; reef/substrate creation; establishment of riparian buffer zones and improvement of freshwater habitat features in watersheds that support diadromous fish; exclusionary fencing and planting; invasive species removal; planting of native coastal wetland and submerged aquatic vegetation; and enhancement of feeding, spawning and growth habitat essential to marine or diadromous fish, including degraded areas that historically were important habitat for living marine and coastal resources, and through the restoration of which would support these resources again.</P>
                <HD SOURCE="HD2">Program Priorities</HD>
                <P>In general, NOAA seeks restoration project proposals that clearly demonstrate anticipated benefits to specific NOAA trust resource habitats; describe how these benefits will be achieved through the proposed restoration activities, and identify the range of species expected to benefit. NOAA trust resource habitats include but are not limited to, estuaries, salt marshes, seagrass beds, coral reefs, shellfish reefs, mangrove forests, and riparian habitat near rivers, streams and creeks used by diadromous fish.</P>
                <P>NOAA seeks to emphasize selection of restoration projects that address habitats whose regional condition is compromised due to loss, fragmentation, presence of invasive species, or loss of functionality. In addition, habitat restoration project proposals are evaluated based on their social and economic importance (e.g. benefits to essential fish habitat that supports commercial or recreational fishery resources, or improvements in aesthetic and stewardship value of NOAA trust resource habitats) within their region. Within a given habitat, priority is also typically given to project proposals that incorporate proven effective restoration techniques, address causes of habitat degradation/loss, and maximize cost-effectiveness.</P>
                <P>Since the inception of the Program, West Coast projects have focused primarily on restoration of salmonid freshwater habitats. To broaden the scope of funded projects in the Pacific Northwest and California, the Program will seek projects that benefit multiple species, including non-salmonid resources, and projects that emphasize restoration of marine and estuarine habitats. The Program expects to continue to support freshwater salmonid habitat restoration efforts. In addition, any salmonid project that would occur where NOAA species recovery planning efforts are underway should be consistent with those planning efforts.</P>
                <P>
                    While the primary focus of the Program is to provide funding and technical expertise to support on-the-ground implementation of fishery habitat restoration projects that involve an outreach and/or volunteer component tied to the restoration activities, the Program recognizes that accomplishing restoration is a multi-faceted effort involving project design, engineering services, permitting, short-term baseline studies, construction, 
                    <PRTPAGE P="55820"/>
                    oversight, monitoring, and education and outreach. In cases where on-the-ground funding for a project has been secured or is deemed likely, and/or community support for a restoration project is high, but pre-implementation funding to conduct feasibility studies or engineering and design is limiting a project's forward progress, the Program will consider funding such pre-implementation activities. Proposals emphasizing a singular component, such as only education or program coordination will be discouraged, as will applications that propose to expand an organization's day-to-day activities, or that primarily seek support for administration, salaries, overhead, and travel. Because requests for habitat restoration funds historically exceed funds available, funding land purchase agreements, conservation easements, and large equipment purchases such as vehicles, boats and similar items will receive low priority.
                </P>
                <P>Although NOAA recognizes that water quality issues may impact habitat restoration efforts, this Program is intended to fund projects that target physical and/or biological habitat restoration rather than those that result in direct water chemistry improvements (i.e. wastewater treatment plant upgrades or combined sewer outfall corrections). Similarly, the following restoration projects will not be eligible for funding: (1) Activities that constitute legally required mitigation for the adverse effects of an activity regulated or otherwise governed by local, state or Federal law; (2) activities that constitute restoration for natural resource damages under Federal, state or local law; and (3) activities that are required by a separate consent decree, court order, statute or regulation. Funds from this Program may be sought to enhance restoration activities beyond the scope legally required by these activities.</P>
                <HD SOURCE="HD2">Environmental Compliance</HD>
                <P>It is the applicant's responsibility to obtain all necessary Federal, state and local government permits and approvals for the proposed work. Applicants are expected to design their projects so that they minimize the potential for adverse impacts to the environment. NOAA must analyze the potential environmental impacts, as required by the National Environmental Policy Act (NEPA), for applications that seek NOAA funding. Proposals should provide enough detail for NOAA to make a NEPA determination. Successful applications cannot be forwarded to the NOAA Grants Management Division with recommendations for funding until NOAA completes necessary NEPA documentation.</P>
                <P>Consequently, as part of an applicant's package, and under the description of proposed activities, applicants will be required to provide detailed information on the activities to be conducted, such as site locations, species and habitat(s) to be affected, possible construction activities, and any environmental concerns that may exist (e.g., the use of and/or disposal of hazardous or toxic substances, introduction of non-indigenous species, impacts to endangered and threatened species, impacts to coral reef systems, etc.). For partnerships, where project-specific details may not be available at the time an award is made, partners must meet the same environmental compliance requirements on subsequent sub-awards.</P>
                <P>In addition to providing specific information that will serve as the basis for any required impact analyses, applicants may also be required to assist NOAA in drafting of an environmental assessment if NOAA determines an assessment is necessary and that one does not already exist for the activities proposed in the application. Applicants may also be required to cooperate with NOAA in identifying and implementing feasible measures to reduce or avoid any identified adverse environmental impacts of their proposal. The selecting official may decide, at the time of proposal review, to recommend funding a project in phases to enable an applicant to provide information needed for an environmental assessment, feasibility analysis or similar activity if a NEPA determination cannot be made for all activities in a particular application. The selecting official may also impose special award conditions that limit the use of funds for activities that have outstanding environmental compliance requirements. Special award conditions may also be imposed to ensure grantees consider and plan for the safety of volunteers, and provide appropriate credit for NOAA and other contributors, for example.</P>
                <HD SOURCE="HD2">Funding Sources and Dispersal Mechanisms</HD>
                <P>The Restoration Center envisions funding projects through cooperative agreements and grants, contracts, joint project agreements, and intra- and interagency transfers, as appropriate.</P>
                <P>A cooperative agreement is a legal instrument reflecting a relationship between NOAA and a recipient whenever (1) the principal purpose of the relationship is to provide financial assistance to the recipient and (2) substantial involvement is anticipated between NOAA and the recipient during performance of the contemplated activity.</P>
                <P>A grant is similar to a cooperative agreement, except that in the case of grants, substantial involvement between NOAA and the recipient is not anticipated during the performance of the contemplated activity. Financial assistance is the transfer of money, property, services or anything of value to a recipient in order to accomplish a public purpose of support or stimulation that is authorized by Federal statute.</P>
                <P>A contract is a procurement instrument used when the primary purpose is to acquire goods or services for government use. Contracts may be used by the Program when NOAA directly implements priority restoration projects.</P>
                <P>The Secretary of Commerce has authority to enter into joint project agreements with not-for-profit, research, or public organizations on matters of mutual interest, the cost of which is equitably apportioned. The principal purpose of a joint project agreement under this Program is to engage in a collaborative and equitably apportioned effort with a qualified organization on matters of mutual interest.</P>
                <P>For purposes of this Program, interagency agreements are written documents that contain specific provisions of governing authorities, agency responsibilities, and funding. Such agreements are entered into between NOAA and a reimbursing Federal agency or between another Federal agency and NOAA when NOAA is the funding organization. Such agreements will also require the inclusion of a local sponsor for the restoration project.</P>
                <P>The instrument chosen will be based on such factors as degree of direct NOAA involvement with the project beyond the provision of financial assistance, the proportion of funds invested in the project by NOAA and the other organizations, and the efficiency of the different mechanisms to achieve the Program's goals and objectives. The Restoration Center will determine which method is the most appropriate based on the specific circumstances of each project.</P>
                <P>
                    NOAA reserves the right to fund individual projects directly, or through partnership arrangements. The Program will continue to create partnership arrangements at the national and regional level with organizations that have similar goals for improving fisheries habitat. Partnerships are a key element that allows the Restoration Center to significantly leverage the 
                    <PRTPAGE P="55821"/>
                    funding available for on-the-ground restoration. Partnerships also encourage sharing and distribution of technical expertise; they often improve coordination between diverse organizations with common goals, and they allow NOAA to reach larger and more diverse communities that have vested interests in fishery habitat restoration.
                </P>
                <P>The Restoration Center will function in a clearinghouse capacity to help develop and link high quality habitat restoration proposals with other potential funding sources whose evaluation criteria contain similar specifications for habitat enhancement. This will provide greater exposure for project ideas and increase the chances for project proponents to secure funding.</P>
                <P>
                    Each year, the Restoration Center Director will determine the proportion of Program funds that will be allocated to National and Regional Habitat Restoration Partnerships and the proportion available for direct project funding. The proportion will be established annually and may depend upon the amount of funds available from partnership organizations to leverage NOAA dollars and the ability of partners to help NOAA fund a broad array of projects over a wide geographic distribution. A synopsis of the partnership and/or project funding opportunity will be published in NOAA's Omnibus 
                    <E T="04">Federal Register</E>
                     Notice, typically in the summer prior to the fiscal year funding is expected to be available. Potential applicants will be directed to additional information contained in any Federal Funding Opportunity (FFO) announced on 
                    <E T="03">www.grants.gov</E>
                    . FFO's will contain a Funding Opportunity Description, Award Information, Eligibility Information, Application and Submission Information, Application Review and Selection Information, Award Administration Information, Administrative and National Environmental Policy Act Requirements, Agency Contacts, and other information for potential applicants.
                </P>
                <P>
                    The public should note that since publication of the initial Program Guidelines in 2000, NOAA has adopted five standard evaluation criteria for all its competitive grant programs, as follows: (1) Importance and Applicability of Proposal -This criterion ascertains whether there is intrinsic value in the proposed work and/or relevance to NOAA, federal, regional, state or local activities; (2) Technical/Scientific Merit B This criterion assesses whether the approach is technically sound and/or innovative, if the methods are appropriate, and whether there are clear project goals and objectives; (3) Overall Qualifications of Applicants B This criterion ascertains whether the applicant possesses the necessary education, experience, training, facilities, and administrative resources to accomplish the project; (4) Project Costs - This criterion evaluates the budget to determine if it is realistic and commensurate with the project needs and time-frame; and (5) Outreach, Education, and Community Involvement - NOAA assesses whether the project provides a focused and effective education and outreach strategy regarding NOAA's mission. Information on how these criteria are specifically applied in the context of Community-based Restoration Program application evaluation are described each year in the FFO, available on 
                    <E T="03">www.grants.gov</E>
                    .
                </P>
                <HD SOURCE="HD2">Funding Ranges</HD>
                <P>In 2008, the Restoration Center accepted habitat proposals requesting between $30,000 and $250,000; marine debris prevention and removal proposals between $15,000 and $250,000, and Open Rivers Initiative proposals for barrier removals between $30,000 and $1,000,000. This represents an increase in upper and lower funding ranges for projects from earlier Program guidelines. Typical restoration project awards range from $50,000 to $300,000. Funding at levels below $15,000 is typically no longer cost-effective due to increasing operational costs necessary to ensure environmental compliance and administer awards; funding fewer projects at higher dollar amounts has also led to increases in Program efficiency.</P>
                <P>Awards for establishing multi-year, National and Regional Habitat Restoration Partnerships, under which individual project subawards will be jointly reviewed and prioritized for funding, are anticipated to range between $100,000 and $4.0 million, with that range of funding anticipated to be provided to successful partnerships annually during a partnership's duration. Subsequent allocation of funding during the multi-year award period will be dependent on the satisfactory performance of the partner organization.</P>
                <P>Project and Partnership solicitations (FFO's) will contain information on funding ranges, the weighting of NOAA's standard evaluation criteria, and additional factors that may be used by the selecting official to recommend a slate of projects to the Grants Management Division to receive awards. The number of awards and funding ranges to be made in FY 2007 and beyond will depend on the amount of funds appropriated to the Program annually by Congress.</P>
                <HD SOURCE="HD1">Examples of Previously Funded Projects</HD>
                <P>The following examples are community-based restoration projects that have been funded with assistance from the Restoration Center. These examples are only illustrative and are not intended to limit the scope of future proposals in any way.</P>
                <HD SOURCE="HD2">Fish Ladder Construction</HD>
                <P>An impediment to fish passage was corrected through the design and construction of a step-pool fish ladder, which now allows native steelhead trout to reach their historic spawning grounds.</P>
                <HD SOURCE="HD2">Invasive Plant Removal</HD>
                <P>A coalition of volunteer groups called “Pepper Busters” worked to remove exotic Brazilian pepper plants and replant native shoreline vegetation.</P>
                <HD SOURCE="HD2">Salt Marsh Restoration</HD>
                <P>An undersized culvert was replaced to increase the mean high water level in the restricted portion of a marsh and restore tidal flushing to 20 acres of salt marsh.</P>
                <HD SOURCE="HD2">Oyster Reef Restoration</HD>
                <P>Oyster reef habitat was increased by reconstructing historic reefs and seeding them with hatchery-produced seed oysters grown in floating cages by students.</P>
                <HD SOURCE="HD2">Submerged Aquatic Vegetation Restoration</HD>
                <P>An evaluation of the feasibility of using volunteer divers to restore seagrass was developed. A protocol was created to train volunteers in water quality monitoring and seagrass transplantation techniques.</P>
                <HD SOURCE="HD2">Kelp Forest Restoration</HD>
                <P>Community dive groups were trained in kelp reforestation activities, including the preparation, planting and maintenance of kelp sites, documentation of growth patterns, and changes in marine life attracted to the newly planted kelp areas.</P>
                <HD SOURCE="HD2">Wetland Plant Nursery</HD>
                <P>
                    An innovative wetland nursery program was implemented in local high schools, where science and ecology classes build wetland nurseries on campus to grow salt marsh grasses for local restoration efforts.
                    <PRTPAGE P="55822"/>
                </P>
                <HD SOURCE="HD2">Derelict Fishing Gear Removal</HD>
                <P>A pilot project consisted of developing protocols and conducting initial removal efforts. After surveying, locating, and mapping derelict fishing gear, a minimum of 11 tons of lost and abandoned fishing gear was removed by licensed and certified divers.</P>
                <HD SOURCE="HD2">Nuisance Dam Removal</HD>
                <P>Two small stone dams blocked fish migration, and degraded water quality and prey habitat conditions for anadromous fish. The dams, while only several feet high, also presented a public safety hazard. This project resulted in opening stream habitat to anadromous fish, restoring acres of tidal wetlands, and removal of a public safety hazard.</P>
                <HD SOURCE="HD2">Riparian Habitat Restoration</HD>
                <P>Youth corps members were trained in the use of biorestoration and stabilization techniques to restore eroding riverbanks and improve habitat for salmon smolt and other fish species.</P>
                <HD SOURCE="HD2">Diadromous Fish Habitat Restoration</HD>
                <P>Highly functional salmonid and wildlife habitat was restored with the cooperation of private landowners by opening silted enclosures along a slough to provide refuge for juvenile salmonids during the winter flood flows.</P>
                <SIG>
                    <DATED>Dated: September 22, 2008.</DATED>
                    <NAME>James W. Balsiger,</NAME>
                    <TITLE>Acting Assistant Administrator for Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22708 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Technical Information Service </SUBAGY>
                <SUBJECT>National Technical Information Service Advisory Board </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Technical Information Service, Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of open meeting. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces the next meeting of the National Technical Information Service Advisory Board (the Advisory Board), which advises the Secretary of Commerce and the Director of the National Technical Information Service (NTIS) on policies and operations of the Service. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Advisory Board will meet on Thursday, October 30, 2008 from 10 a.m. to approximately 5 p.m. and again on Friday, October 31, 2008 from 9 a.m. to approximately 1 p.m. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Advisory Board meeting will be held in Room 2029 of the Sills Building at 5285 Port Royal Road, Springfield, Virginia 22161. Please note admittance instructions under the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this notice. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Steven D. Needle, (703) 605-6404, 
                        <E T="03">sneedle@ntis.gov</E>
                         or Ms. Jill Johnson (703) 605-6401, 
                        <E T="03">jjohnson@ntis.gov.</E>
                         These are not toll-free telephone numbers. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The NTIS Advisory Board is established by Section 3704b(c) of Title 15 of the United States Code. The charter has been filed in accordance with the requirements of the Federal Advisory Committee Act, as amended (5 U.S.C. App.). </P>
                <P>
                    The October 30 morning session will focus on a review of NTIS' performance in Fiscal Year 2008, its lines of business and its core competencies. The afternoon session is expected to focus on new strategic directions for Fiscal Year 2009, including issues pertaining to the identification of new markets and new ways to enhance NTIS' utility to customers. The October 31 session will focus primarily on Board business but may continue the previous day's discussions. A final agenda and summary of the proceedings will be posted at the NTIS Web site as soon as they are available (
                    <E T="03">http://www.ntis.gov/about/advisorybd.asp</E>
                    ). 
                </P>
                <P>The Sills Building is a secure facility. Accordingly, persons wishing to attend should call the contacts identified above to arrange for admission. Approximately one-half hour will be reserved for public comments during the afternoon of the October 30 session. The amount of time per speaker will be determined by the number of requests received. Questions from the public will not be considered during this period. Any person who wishes to submit a written statement for the Board's consideration should mail or e-mail it to the contacts named above not later than October 17, 2008. </P>
                <SIG>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>Ellen Herbst, </NAME>
                    <TITLE>Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22706 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-04-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE </AGENCY>
                <SUBAGY>Department of the Army; Corps of Engineers </SUBAGY>
                <SUBJECT>Notice of Availability for the Draft Environmental Impact Statement/ Environmental Impact Report for the San Pedro Waterfront Project, Los Angeles County, CA </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Army—U.S. Army Corps of Engineers, DoD. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Army Corps of Engineers, Los Angeles District (Regulatory Division), in coordination with the Port of Los Angeles, has completed a Draft Environmental Impact Statement/Environmental Impact Report (EIS/EIR) for the San Pedro Waterfront Project, encompassing approximately 400 acres of land and water primarily along the west side of the Main Channel westward to Harbor Boulevard from the Vincent Thomas Bridge southward to Inner Cabrillo Beach in the Port of Los Angeles. The Port of Los Angeles requires authorization pursuant to section 404 of the Clean Water Act, section 10 of the Rivers and Harbors Act, and section 103 of the Marine Protection, Research, and Sanctuaries Act, to implement various regulated activities in and over waters of the U.S. associated with redeveloping San Pedro Waterfront, which would include the following elements: </P>
                    <HD SOURCE="HD1">Promenade, Harbors, and Open Space </HD>
                    <P>Waterfront Promenade—Construct a continuous promenade approximately 30 feet wide along the west side of the Main Channel through the project area. </P>
                    <P>Three New Harbors (North Harbor, Downtown Harbor, and 7th Street Harbor)—Develop three new harbors along the west side of the Main Channel to provide berthing for visiting tall ships, tugboats, and other vessels used for recreational, commercial, and other port-related purposes. This would require excavation and dredging to create the approximately 7 acres of new surface water. Cleaner material would to be disposed of at a designated ocean site (LA-2/LA-3), and unsuitable material to be disposed of at an approved upland site. In-harbor sites would also be considered if any become available. </P>
                    <P>7th Street Pier—The constructed 7th Street Pier would be the public dock for short-term berthing of visiting vessels and would be located within the 7th Street Harbor, adjacent to the Los Angeles Maritime Museum. </P>
                    <P>
                        Town Square—The Town Square would comprise approximately 0.79 acre in front of the historic San Pedro 
                        <PRTPAGE P="55823"/>
                        Municipal Ferry Building (existing Los Angeles Maritime Museum) at the foot of 6th Street and would incorporate a portion of the downtown promenade. 
                    </P>
                    <P>Downtown Civic Fountain—The Downtown Civic Fountain would be adjacent to the Town Square. The water feature would be designed to complement the civic setting of the adjacent San Pedro City Hall Building and the Town Square, and simulate the extension of the 7th Street Harbor to the San Pedro City Hall Building. </P>
                    <P>John S. Gibson Jr. Park—John S. Gibson Jr. Park is an existing 1.61-acre park located south of the 5th Street green. The intent is to maintain the existing memorials at the park and enhance their surroundings to highlight their historical and cultural significance with improved hardscape, landscaping, lighting, and interpretive signage elements. </P>
                    <P>Fishermen's Park—The proposed Fishermen's Park would encompass approximately 3 acres within Ports O'Call. </P>
                    <P>Outer Harbor Park—The proposed Outer Harbor Park would encompass approximately 6 acres at the Outer Harbor and would be designed as an integral feature and complementary to the secure operations of the proposed Outer Harbor Cruise Terminals. </P>
                    <P>San Pedro Park—The proposed San Pedro Park would encompass 18 acres located north of 22nd Street, south of Crescent Avenue, and west of Sampson Way. </P>
                    <P>Warehouses Nos. 9 and 10 and associated backland area—Adapt the area for low-intensity community-serving commercial or educational reuse that would be incorporated as an integral element of San Pedro Park. </P>
                    <HD SOURCE="HD1">New Development, Redevelopment, Cultural Attractions, and Modifications to Existing Tenants, Including Development of the New Cruise Terminals </HD>
                    <P>Cruise Terminals—Upgrade Berths 45-47 for use as a cruise ship berth including terminal construction, and construct a new cruise ship berth and terminal at Berths 49-50 in the Outer Harbor. </P>
                    <P>Cruise Terminal Parking—The proposed upgrades to Berths 45-47 and new cruise ship terminal, the construction of a new cruise berth and terminal facility at Berths 49-50 in the Outer Harbor, and projected increases in ship calls and passengers at Berths 91-93 would require additional parking facilities. The parking for the combined cruise ship facilities would be located in the Inner Harbor and Outer Harbor. </P>
                    <P>Ports O'Call Redevelopment—Redevelop and construct new commercial development within Ports O'Call Village. The redevelopment and additional development at Ports O'Call would require an increase in parking spaces. Parking would be provided at a number of locations within the Port and near Ports O'Call. </P>
                    <P>Tug Operations—Renew leases and construct two new 10,000-square-foot buildings around the North Harbor for both Crowley and Millennium tug boats. Dispatching of tugs varies from day to day, and the impacts associated with tugboat operations are or will be accounted for in the respective projects that utilize tugboats. </P>
                    <P>Los Angeles Maritime Institute (LAMI)—Issue a new lease and reuse the Crowley Building in the Downtown Harbor area for LAMI. </P>
                    <P>Berth 240 Fueling Station—A new fueling station would be developed at Berth 240 on Terminal Island (i.e., along the east side of the Main Channel). </P>
                    <P>Catalina Express Terminal and SS Lane Victory—Permanently relocate the Catalina Express Terminal berthing facilities from Berths 95-96 to the existing location of the S.S. Lane Victory at Berth 94. S.S. Lane Victory would be relocated to the North Harbor water cut. </P>
                    <HD SOURCE="HD1">Transportation Improvements </HD>
                    <P>Sampson Way—This road would be expanded to two lanes in each direction and curve near the Municipal Fish Market to meet with 22nd Street in its westward alignment east of Miner Street. The proposed construction would also include an enhanced four-way intersection at Sampson Way and 7th Street to provide improved access to and along the waterfront. </P>
                    <P>Harbor Boulevard—This road would remain in place at its current capacity with two lanes in each direction. Landscaping and hardscape improvements are proposed along the east side and west side of Harbor Boulevard south of 7th Street, as well as in the median of Harbor Boulevard starting at the Swinford Street intersection, and would extend south to 22nd Street. </P>
                    <P>The Waterfront Red Car Line—This line would be extended from its existing terminus near the intersection of Harbor Boulevard and Miner Street and 22nd Street to City Dock No. 1 (adjacent to Warehouse No. 1), to the Outer Harbor along Miner Street, and to Inner Cabrillo Beach along Shoshonean Road. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Questions or comments concerning the Draft EIS/EIR should be directed to Dr. Spencer D. MacNeil, U.S. Army Corps of Engineers, Los Angeles District, Regulatory Division, Ventura Field Office, 2151 Alessandro Drive, Suite 110, Ventura, CA 93001, (805) 585-2152. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Port of Los Angeles and U.S. Army Corps of Engineers will jointly hold a public hearing to receive public comments and to assess pubic concerns regarding the Draft EIS/EIR and project on October 27, 2008 starting at 6 p.m. in the Crowne Plaza Hotel in San Pedro (601 S. Palos Verdes Street). Written comments will be accepted until the close of public review on December 8, 2008. </P>
                <SIG>
                    <NAME>David J. Castanon, </NAME>
                    <TITLE>Chief, Regulatory Division, Los Angeles District.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22641 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3710-KF-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION </AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Education. </P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The IC Clearance Official, Regulatory Information Management Services, Office of Management invites comments on the submission for OMB review as required by the Paperwork Reduction Act of 1995. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before October 27, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments should be addressed to the Office of Information and Regulatory Affairs, Attention: Education Desk Officer, Office of Management and Budget, 725 17th Street, NW., Room 10222, Washington, DC 20503. Commenters are encouraged to submit responses electronically by e-mail to 
                        <E T="03">oira_submission@omb.eop.gov</E>
                         or via fax to (202) 395-6974. Commenters should include the following subject line in their response “Comment: [insert OMB number], [insert abbreviated collection name, e.g., “Upward Bound Evaluation”]. Persons submitting comments electronically should not submit paper copies. 
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Section 3506 of the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35) requires that the Office of Management and Budget (OMB) provide interested Federal agencies and the public an early opportunity to comment on information collection requests. OMB may amend or waive the requirement for public consultation to the extent that public participation in the approval process 
                    <PRTPAGE P="55824"/>
                    would defeat the purpose of the information collection, violate State or Federal law, or substantially interfere with any agency's ability to perform its statutory obligations. The IC Clearance Official, Regulatory Information Management Services, Office of Management, publishes that notice containing proposed information collection requests prior to submission of these requests to OMB. Each proposed information collection, grouped by office, contains the following: (1) Type of review requested, e.g., new, revision, extension, existing or reinstatement; (2) Title; (3) Summary of the collection; (4) Description of the need for, and proposed use of, the information; (5) Respondents and frequency of collection; and (6) Reporting and/or Recordkeeping burden. OMB invites public comment. 
                </P>
                <SIG>
                    <DATED>Dated: September 22, 2008. </DATED>
                    <NAME>Angela C. Arrington, </NAME>
                    <TITLE>IC Clearance Official, Regulatory Information Management Services, Office of Management.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Institute of Education Sciences </HD>
                <P>
                    <E T="03">Type of Review:</E>
                     New Collection. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Mapping the Adopted Core Curriculum in the Mid Atlantic Region. 
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On Occasion. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     State, Local, or Tribal Gov't, SEAs or LEAs. 
                </P>
                <P>
                    <E T="03">Reporting and Recordkeeping Hour Burden:</E>
                </P>
                <FP SOURCE="FP-1">Responses: 1,496. </FP>
                <FP SOURCE="FP-1">Burden Hours: 748. </FP>
                <P>
                    <E T="03">Abstract:</E>
                     It is important to identify adopted LEA curricula in language arts/literacy, mathematics and science to map the landscape of the Mid-Atlantic region and to inform policy and practice data-driven decision-making. After collecting information from interviews with key LEA staff from each REL Mid-Atlantic district, the lab will produce a foundational database from which to analyze trends and strategically develop appropriate research and evaluation agendas. A descriptive report summarizing the adopted K-12 curricula in the region and a user-friendly on-line interface will also be developed. 
                </P>
                <P>
                    Requests for copies of the information collection submission for OMB review may be accessed from 
                    <E T="03">http://edicsweb.ed.gov</E>
                    , by selecting the “Browse Pending Collections” link and by clicking on link number 3768. When you access the information collection, click on “Download Attachments” to view. Written requests for information should be addressed to U.S. Department of Education, 400 Maryland Avenue, SW., LBJ, Washington, DC 20202-4537. Requests may also be electronically mailed to 
                    <E T="03">ICDocketMgr@ed.gov</E>
                     or faxed to 202-401-0920. Please specify the complete title of the information collection when making your request. 
                </P>
                <P>
                    Comments regarding burden and/or the collection activity requirements should be electronically mailed to 
                    <E T="03">ICDocketMgr@ed.gov</E>
                    . Individuals who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339.
                </P>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22640 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY </AGENCY>
                <SUBJECT>Amended Record of Decision for the Hanford Comprehensive Land-Use Plan Environmental Impact Statement </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Energy. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Amended record of decision. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Energy (DOE) is amending its Record of Decision (ROD) for the 
                        <E T="03">Hanford Comprehensive Land-Use Plan Environmental Impact Statement</E>
                         (HCP-EIS) (DOE/EIS-0222; September 1999), which evaluated the potential environmental impacts associated with implementing a comprehensive land-use plan (CLUP) for the Hanford Site near Richland, Washington. The CLUP consists of four key elements: (i) A land-use map that addresses the Hanford Site as five geographic areas and shows the planned future uses for each area, (ii) a set of nine land-use designations that define the permissible activities for each use, (iii) land-use planning policies, and (iv) implementing procedures that apply to the review and approval of future land uses. These elements were developed to ensure consistency in land-use decisionmaking and application of DOE institutional controls to the Site. The ROD (64 FR 61615; November 12, 1999) adopted the CLUP for at least the next 50 years. 
                    </P>
                    <P>In amending the 1999 ROD, DOE seeks to clarify two points: that when considering land-use proposals, DOE will use regulatory processes in addition to the implementing procedures in Chapter 6 of the HCP-EIS to ensure consistency with CLUP land-use designations, and that DOE will continue to apply the process under HCP-EIS Chapter 6 to modify or amend the CLUP, as needed. </P>
                    <P>The CLUP will remain in effect as long as DOE retains legal control of some portion of the Hanford Site, which is expected to be longer than 50 years. As a “living document,” the CLUP is intended to be flexible enough to accommodate changes, both anticipated and unforeseen, in missions and conditions. The HCP-EIS recommends reassessment of the CLUP every 5 years through a Supplement Analysis process under the DOE National Environmental Policy Act (NEPA) Implementing Procedures (10 CFR 1021.314). </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The documents referenced herein are available from: Center for Environmental Management Information, P.O. Box 23769, Washington, DC 20026-3769, Telephone: 800-736-3282 (in Washington, DC: 202-863-5084). </P>
                    <P>
                        The 1999 HCP-EIS and ROD are available, and the Supplement Analysis and this amended ROD will be available, at 
                        <E T="03">http://www.gc.energy.gov/NEPA/</E>
                         under “DOE NEPA Documents.” 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P SOURCE="NPAR">For further information on the Supplement Analysis for the HCP-EIS, contact: Mr. Woody Russell, NEPA Compliance Officer, U.S. Department of Energy, Office of River Protection, MS H6-60 P.O. Box 450, Richland, WA 99352, Telephone: 509-373-5227. </P>
                    <P>For information on DOE's NEPA process, contact: Ms. Carol Borgstrom, Director, Office of NEPA Policy and Compliance (GC-20), U.S. Department of Energy, 1000 Independence Avenue, SW., Washington, DC 20585-0103, Telephone: 202-586-4600, or leave a message at 800-472-2756. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <P>
                    DOE published a Notice of Intent (NOI) (57 FR 37959; August 21, 1992) to prepare the 
                    <E T="03">Hanford Remedial Action EIS</E>
                     and identified as an EIS objective the establishment of future land uses at the Hanford Site near Richland, Washington. After public scoping, DOE issued an Implementation Plan (DOE/RL-93-66, June 1995) to document the recommendations of the Federal, state, and local agencies, Native American Tribes, and interested individuals and organizations, many of whom had been working with DOE to identify future use options for the Site. 
                </P>
                <P>
                    In response to new directives (DOE Order 430.1A, 
                    <E T="03">Life-Cycle Asset Management, and National Defense Authorization Act for FY97</E>
                    , 42 U.S.C. 7274k, redesignated 50 U.S.C. 2582), DOE revised the scope of the EIS to prepare a comprehensive land-use plan for the Site. Seven cooperating agencies (Federal and local agencies) and two consulting Tribal governments developed alternatives analyzed in the EIS and helped develop the CLUP. In September 1996, DOE issued the 
                    <E T="03">
                        Draft Hanford Remedial Action EIS and 
                        <PRTPAGE P="55825"/>
                        Comprehensive Land-Use Plan
                    </E>
                     (61 FR 47739) and received extensive comments. To address this input, DOE issued a second, revised draft (64 FR 19983; April 23, 1999). 
                </P>
                <P>
                    DOE considered comments received on the revised draft, and in September 1999 issued a final EIS, 
                    <E T="03">Hanford Comprehensive Land-Use Plan Environmental Impact Statement</E>
                     (HCP-EIS), with a new title that reflected the change in scope from remedial action to land-use planning. The ROD (64 FR 61615; November 12, 1999) adopted DOE's Preferred Alternative as the CLUP, with the HCP-EIS Chapter 6 process as the governing processes to ensure consistent implementation of the CLUP. 
                </P>
                <HD SOURCE="HD1">II. Other Regulatory Processes at Hanford </HD>
                <P>Since 1999, the Hanford Site's primary mission has been environmental cleanup, using the Tri-Party Agreement (TPA) negotiated among the U.S. Environmental Protection Agency (EPA), Washington State Department of Ecology (Ecology), and DOE as the framework for implementing the requirements of the Comprehensive Environmental Response, Compensation, and Liability Act (CERCLA), the Resource Conservation and Recovery Act (RCRA), and the State of Washington Hazardous Waste Management Act (HWMA). Other important requirements are integrated into this cleanup decisionmaking process, including NEPA values and the substantive provisions of the National Historic Preservation Act (NHPA). </P>
                <P>The TPA includes requirements for soliciting input from other agencies, Tribal governments, and the public before the Tri-Party agencies make cleanup decisions. Cleanup decisionmaking is based on proposed uses of land and facilities, risk assessments of exposure scenarios that include reasonably anticipated future land uses, and consideration of other legally applicable or relevant and appropriate requirements established under Federal, state, or local agency laws, regulations, and policies. </P>
                <HD SOURCE="HD1">III. Supplement Analysis </HD>
                <HD SOURCE="HD2">A. The Supplement Analysis Evaluation </HD>
                <P>To determine whether the existing HCP-EIS remains adequate or whether a new or supplemental EIS is needed, DOE prepared a Supplement Analysis under the DOE NEPA regulations (10 CFR 1021.314). DOE identified documents developed from September 1999 through September 2007 that potentially involve land use at the Hanford Site. Documents considered in this evaluation to support the Supplement Analysis include existing NEPA, CERCLA/TPA, RCRA/HWMA, and NHPA documents; DOE Orders, policies, and guidelines; DOE real estate licenses, permits, easements, deed notices; laws, regulations, Executive Orders; and cultural/historical documents. DOE solicited input from Tribal Nations and interested stakeholders to identify additional relevant documents to be evaluated. </P>
                <P>After identifying candidate decision documents with land-use involvement, current actions, and reasonably foreseeable actions, DOE evaluated these for consistency with the CLUP. In a few cases, the analyses were still under development and a draft document was not yet available to determine whether the CLUP would be affected. In other cases, analysis in a draft document provides sufficient information to determine whether land use is involved, even though the document and associated decision had not been finalized; DOE included these as reasonably foreseeable actions in the Supplement Analysis. DOE's next Supplement Analysis is expected to reflect any such final documents and decisions as needed and appropriate, consistent with the HCP-EIS Chapter 6 process and DOE's NEPA regulations. </P>
                <P>Though not required under the DOE NEPA regulations, DOE issued the draft Supplement Analysis on March 24, 2008, for a 30-day public review period. The principal comments received, from area Tribes and stakeholders, were that DOE should live up to commitments in resource management plans it issues and should implement CLUP land-use values in the cleanup process. DOE addressed the comments in the final Supplement Analysis and considered all comments in issuing this Amended ROD. </P>
                <HD SOURCE="HD2">B. Results of the Supplement Analysis </HD>
                <P>In reviewing the implementation of area and resource management plans for maintaining appropriate environmental controls and mitigation, DOE identified changes from the plans as established by the CLUP (HCP-EIS, Table 6-4). For example, DOE found that in a few cases the scope of a management plan is being covered by other management plans. Two resource management plans originally identified in the HCP-EIS have not been prepared, and two others—one for Gable Mountain/Gable Butte (finalized and issued) and the other for Rattlesnake Mountain (still under development)—are tiered from the Hanford Cultural Resources Management Plan. A draft Cultural and Biological Resources Management Plan was developed for areas of the Hanford Site now being managed by DOE's Pacific Northwest Site Office and issued for public comment, but has not been finalized. These deviations from the CLUP are minor and have not affected the CLUP (including the land-use map, designations, and policies). The management plans in place today or still under development continue to support DOE's efforts to streamline environmental planning at Hanford and integrate it with the CLUP. DOE found that these plans, which have been or will be provided to stakeholders, are largely being applied consistently at the Hanford Site. </P>
                <P>DOE found that other regulatory processes followed at the Hanford Site, such as RCRA and CERCLA, have been used effectively to determine whether proposed activities at the Hanford Site are consistent with the CLUP. Under the TPA framework for cleanup of the Hanford Site, the requirements of the CERCLA and the RCRA/HWMA processes are implemented, including opportunities for stakeholder participation in decisionmaking. Values under the NEPA and State Environmental Policy Act (SEPA) processes, cultural considerations under the NHPA, and land-use considerations such as consistency with the CLUP also are integrated into cleanup decisionmaking under the TPA framework. </P>
                <HD SOURCE="HD2">C. Basis of Supplement Analysis Determination </HD>
                <P>In reaching a determination on the need for a new or supplemental EIS for the CLUP, DOE has considered the documents and other information developed since 1999 concerning land use at the Hanford Site as evaluated in the Supplement Analysis, regulatory processes that have been used to consider land use and consistency with the CLUP, and comments received on the draft Supplement Analysis. DOE finds that modification of resource management plans are minor and consistent with the CLUP. Based on the Supplement Analysis, DOE has not identified significant new circumstances or changes relevant to environmental concerns that affect the CLUP. </P>
                <P>
                    DOE finds that other regulatory processes followed at the Hanford Site under the TPA framework, such as RCRA and CERCLA, have been used effectively to determine whether proposed activities at the Hanford Site are consistent with the CLUP and provide equivalent opportunities for agencies, Tribes, and the public to participate in decisionmaking. Values 
                    <PRTPAGE P="55826"/>
                    under the NEPA and SEPA processes, cultural considerations under the NHPA, and land-use considerations such as consistency with the CLUP are considered also in cleanup decisions under the TPA framework. This Amended ROD clarifies DOE's finding that the use of these other regulatory processes is consistent with processes established in the HCP-EIS to ensure that land-use decisions are consistent with the CLUP. 
                </P>
                <P>However, DOE does not believe it is appropriate to use these other regulatory processes to amend the CLUP (including making changes to land-use map, designations, and policies). Proposals to amend any aspect of the CLUP will continue to follow the process outlined in Chapter 6 of the HCP-EIS. The review process for land-use requests that would change or modify the CLUP (Figure 5-1 of the Supplement Analysis) requires review by the DOE Real Estate Officer (REO) and the DOE NEPA Compliance Officer. As stated in Section 6.4 of the final HCP-EIS: </P>
                <EXTRACT>
                    <P>The REO receives notice (e.g., NEPA checklist, SEPA checklist, CERCLA RI/FS [Remedial Investigation/Feasibility Study] review request, CERCLA review request, RCRA permit request, etc.) from a proposed project or activity and initiates, with the NEPA Compliance Officer (NCO), a coordinated project review. * * *  As an initial step in the review process, the REO determines whether the project is an “Allowable Use,” “Special Use,” or “Amendment” to the CLUP. For projects that require Special Use Permits or Plan Amendments, the REO obtains comments and recommendations from the SPAB [Site Planning Advisory Board] on the suitability of the proposed “Use” with respect to the existing CLUP map, land-use policies, and implementing procedures. For CLUP Amendments, review includes a final RL [Richland Operations Office] Site Management Board (SMB) affirmation, or the SMB can refer a proposed Plan Amendment back to the REO for further review.</P>
                </EXTRACT>
                <P>As discussed in the Supplement Analysis (Section 5.5), this review process may result in additional NEPA review. </P>
                <HD SOURCE="HD1">IV. Supplement Analysis Determination and Amended Decision </HD>
                <P>Based on the Supplement Analysis, DOE finds no significant new circumstances or information relevant to environmental concerns and bearing on the proposed actions or their impacts as described in the HCP-EIS. Therefore, DOE has determined that neither a new EIS nor a supplement to the existing HCP-EIS is needed at this time. </P>
                <P>Based on the Supplement Analysis, DOE concludes that using the regulatory processes in place at the Hanford Site under the framework of the Tri-Party Agreement is an acceptable way to ensure land use is being implemented consistently with the CLUP. DOE will continue to follow the provisions of section 6.4 of the HCP-EIS for proposed amendments to the CLUP. Resource and area management plans will continue to be developed and implemented with the goal of protecting Hanford's resources, maintaining consistency with CLUP policies and goals, and honoring commitments made in these management plans. </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on September 19, 2008. </DATED>
                    <NAME>James A. Rispoli, </NAME>
                    <TITLE>Assistant Secretary for Environmental Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22676 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Project No. 2634-054] </DEPDOC>
                <SUBJECT>Great Lakes Hydro America, LLC; Notice of Application for Amendment of License and Soliciting Comments, Motions To Intervene, and Protests </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>Take notice that the following application has been filed with the Commission and is available for public inspection.</P>
                <P>
                    a. 
                    <E T="03">Application Type:</E>
                     Amendment to Recreation Plan.
                </P>
                <P>
                    b. 
                    <E T="03">Project No.:</E>
                     2634-054.
                </P>
                <P>
                    c. 
                    <E T="03">Dated Filed:</E>
                     July 14, 2008.
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Great Lakes Hydro America, LLC.
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Storage Hydroelectric Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     The project is located on the West and South Branch of the Penobscot River in Piscataquis and Somerset Counties, Maine.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Federal Power Act, 16 U.S.C. 791(a)-825(r).
                </P>
                <P>
                    h. 
                    <E T="03">Application Contact:</E>
                     Kevin Bernier, FERC Compliance Specialist, Great Lakes Hydro America, LLC, 1024 Central Street, Millinocket, Maine 04462, telephone: (207) 723-4341, fax: (207) 723-4597.
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Any questions on this notice should be addressed to Gina Krump at (202) 502-6704, or e-mail address: 
                    <E T="03">gina.krump@ferc.gov</E>
                    .
                </P>
                <P>
                    j. 
                    <E T="03">Deadline for filing comments and/or motions:</E>
                     October 20, 2008. 
                </P>
                <P>All documents (original and eight copies) should be filed with: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.</P>
                <P>
                    k. 
                    <E T="03">Description of Request:</E>
                     The licensee filed an amendment application to remove the requirement to provide a boat launch and parking area at the Caucomgomoc Lake from the approved recreation plan, issued April 19, 2006. The licensee proposes to develop an area at Harrington Lake, which would be outside the project boundary and not under the Commission's jurisdiction.
                </P>
                <P>
                    l. 
                    <E T="03">Location of the Application:</E>
                     A copy of the application is available for inspection and reproduction at the Commission's Public Reference Room, located at 888 First Street, NE., Room 2A, Washington, DC 20426, or by calling (202) 502-8371. This filing may also be viewed on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. You may also register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via e-mail of new filings and issuances related to this or other pending projects. For assistance, call 1-866-208-3676 or e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                    , for TTY, call (202) 502-8659. A copy is also available for inspection and reproduction at the address in item (h) above.
                </P>
                <P>m. Individuals desiring to be included on the Commission's e-mailing list should so indicate by writing to the Secretary of the Commission.</P>
                <P>
                    n. 
                    <E T="03">Comments, Protests, or Motions To Intervene</E>
                    —Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, .214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application.
                </P>
                <P>
                    o. 
                    <E T="03">Filing and Service of Responsive Documents</E>
                    —Any filings must bear in all capital letters the title “COMMENTS”, “PROTEST, or “MOTION TO INTERVENE”, as applicable, and the Project Number (P-6066-031) of the particular application to which the filing refers. All documents (original and eight copies) should be filed with: Honorable Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., 
                    <PRTPAGE P="55827"/>
                    Washington, DC 20426. A copy of any motion to intervene must also be served upon each representative of the Applicant specified in the particular application.
                </P>
                <P>
                    p. 
                    <E T="03">Agency Comments</E>
                    —Federal, State, and local agencies are invited to file comments on the described application. A copy of the application may be obtained by agencies directly from the Applicant. If an agency does not file comments within the time specified for filing comments, it will be presumed to have no comments. One copy of an agency's comments must also be sent to the Applicant's representatives.
                </P>
                <P>
                    q. Comments, protests, and interventions may be filed electronically, via the Internet in lieu of paper. See, 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov</E>
                     under the “e-Filing” link. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22624 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Project No. 13254-000] </DEPDOC>
                <SUBJECT>City of Aspen; Notice of Preliminary Permit Application Accepted for Filing and Soliciting Comment and Motions To Intervene </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>On July 10, 2008, the City of Aspen filed an application, pursuant to section 4(f) of the Federal Power Act, proposing to study the feasibility of the Castle Creek Hydroelectric Project, to be located on Castle Creek in Pitkin County, Colorado. </P>
                <P>The proposed Castle Creek Hydroelectric Project consists of: (1) The City of Aspen's “Thomas Reservoir”, a small impoundment constructed in 1964 as a part of Aspen's Water Treatment Facilities, (2) a single underground penstock that would replace two (out of service) underground penstocks (3) a proposed powerhouse with a single vertical shaft Pelton turbine coupled to a synchronous generator having a total installed capacity of 1.05 megawatts, (4) a new tailrace from the powerhouse that will deliver flows to Castle Creek just above the existing bridge, and (5) appurtenant facilities. The project would have an annual generation of 7.7 million kilowatt-hours that would be delivered to the City system. </P>
                <P>
                    <E T="03">Applicant Contact:</E>
                     Mr. Phil Overyender, Director of Public Works, City of Aspen, 130 South Galena St., Aspen, CO 81611; phone: (970) 920-5111. 
                </P>
                <P>
                    <E T="03">FERC Contact:</E>
                     Alyssa Dorval, (202) 502-6735. 
                </P>
                <P>
                    Deadline for filing comments, motions to intervene: 60 days from the issuance of this notice. Comments, motions to intervene, notices of intent, and competing applications may be filed electronically via the Internet. See 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site under the “e-Filing” link. If unable to be filed electronically, documents may be paper-filed. To paper-file, an original and eight copies should be mailed to: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. For more information on how to submit these types of filings please go to the Commission's Web site located at 
                    <E T="03">http://www.ferc.gov/filing-comments.asp</E>
                    . More information about this project can be viewed or printed on the “eLibrary” link of Commission's Web site at 
                    <E T="03">http://www.ferc.gov/docs-filing/elibrary.asp</E>
                    . Enter the docket number (P-13254) in the docket number field to access the document. For assistance, call toll-free 1-866-208-3372. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22622 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Project No. 13219-000] </DEPDOC>
                <SUBJECT>Fourever Green Energy Co.; Notice of Preliminary Permit Application Accepted for Filing and Soliciting Comment, Motions To Intervene, and Competing Applications </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>On May 2, 2008, with revisions of July 28 and September 15, 2008, Fourever Green Energy Co. filed an application, pursuant to section 4(f) of the Federal Power Act, proposing to study the feasibility of the Upper Rock Creek Water Power Project, which would be located near the town of Oroville on Rock Creek, a tributary of the North Fork, Feather River in Plumas County, California. </P>
                <P>The proposed project would consist of: (1) Proposed diversion and intake structures; (2) a proposed 0.9-mile-long, metal/composite penstock; (3) a proposed powerhouse containing one generating unit having a total installed capacity of 5 MW; (4) a proposed 450-foot-long, 230-kV transmission line; and (5) appurtenant facilities. The project would have an annual generation of 15 gigawatt-hours which would be sold to a local utility. </P>
                <P>
                    <E T="03">Applicant Contact:</E>
                     Mr. Ron Bingaman, 25855 Sweet Road, Grass Valley, CA 95949; phone: (530) 268-2153. FERC Contact: Tom Papsidero, 202-502-6002. 
                </P>
                <P>
                    Deadline for filing comments, motions to intervene, competing applications (without notices of intent), or notices of intent to file competing applications: 60 days from the issuance of this notice. Comments, motions to intervene, notices of intent, and competing applications may be filed electronically via the Internet. See 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site under the “e-Filing” link. If unable to be filed electronically, documents may be paper-filed. To paper-file, an original and eight copies should be mailed to: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. For more information on how to submit these types of filings please go to the Commission's Web site located at 
                    <E T="03">http://www.ferc.gov/filing-comments.asp</E>
                    . More information about this project can be viewed or printed on the “eLibrary” link of Commission's Web site at 
                    <E T="03">http://www.ferc.gov/docs-filing/elibrary.asp</E>
                    . Enter the docket number (P-13219) in the docket number field to access the document. For assistance, call toll-free 1-866-208-3372. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22620 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <SUBJECT>Notice of Application for Amendment of License and Soliciting Comments, Motions To Intervene, and Protests </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>
                    a. 
                    <E T="03">Type of Application:</E>
                     Non-project use of project lands and waters. 
                </P>
                <P>
                    b. 
                    <E T="03">Project Number:</E>
                     459-238. 
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     September 10, 2008. 
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Ameren/UE. 
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Osage Hydroelectric Project. 
                    <PRTPAGE P="55828"/>
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     The project is located at the Summer Hill Condominium development near mile marker 31.2+5.4 in Barnes Hollow Cove on the Lake of the Ozarks, in Camden County, Missouri. 
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Federal Power Act, 16 U.S.C. 791(a) 825(r) and 799 and 801. 
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     Mr. Jeff Green, Shoreline Supervisor, Ameren/UE, P.O. Box 993, Lake Ozark, MO 65049, (573) 365-9214. 
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Any questions on this notice should be addressed to Christopher Yeakel at (202) 502-8132, or e-mail address: 
                    <E T="03">christopher.yeakel@ferc.gov</E>
                    . 
                </P>
                <P>
                    j. 
                    <E T="03">Deadline for filing comments and or motions:</E>
                     October 20, 2008. 
                </P>
                <P>
                    k. 
                    <E T="03">Description of Request:</E>
                     Ameren/UE requests approval to permit Utley Development Company, LLC, to construct one new, covered, multi-slip boat dock at the Summer Hill development. The dock would have a total of 14 boat slips, 12 slips being 32 feet long and 12 feet wide and two slips being 32 feet long and 10 feet wide and would include a central 4-foot-wide walkway. The dock would be available to the residents of the Summer Hill development. No dredging, fuel dispensing, or sewage pumping facilities are proposed. 
                </P>
                <P>
                    l. 
                    <E T="03">Locations of the Application:</E>
                     A copy of the application is available for inspection and reproduction at the Commission's Public Reference Room, located at 888 First Street, NE, Room 2A, Washington, DC 20426, or by calling (202) 502-8371. This filing may also be viewed on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field (p-459) to access the document. You may also register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via e-mail of new filings and issuances related to this or other pending projects. For assistance, call 1-866-208-3372 or e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                    , for TTY, call (202) 502-8659. A copy is also available for inspection and reproduction at the address in item (h) above. 
                </P>
                <P>m. Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission. </P>
                <P>
                    n. 
                    <E T="03">Comments, Protests, or Motions to Intervene</E>
                    —Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, .214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application. 
                </P>
                <P>
                    o. 
                    <E T="03">Filing and Service of Responsive Documents</E>
                    —Any filings must bear in all capital letters the title “COMMENTS”, “RECOMMENDATIONS FOR TERMS AND CONDITIONS”, “PROTEST”, OR “MOTION TO INTERVENE”, as applicable, and the Project Number of the particular application to which the filing refers (p-459-238). All documents (original and eight copies) should be filed with: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington DC 20426. A copy of any motion to intervene must also be served upon each representative of the Applicant specified in the particular application. 
                </P>
                <P>
                    p. 
                    <E T="03">Agency Comments</E>
                    —Federal, State, and local agencies are invited to file comments on the described application. A copy of the application may be obtained by agencies directly from the Applicant. If an agency does not file comments within the time specified for filing comments, it will be presumed to have no comments. One copy of an agency's comments must also be sent to the Applicant's representatives. 
                </P>
                <P>
                    q. Comments, protests and interventions may be filed electronically via the Internet in lieu of paper. See, 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov</E>
                     under the “e-Filing” link. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22625 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Project No. 77-212] </DEPDOC>
                <SUBJECT>Pacific Gas and Electric Company; Notice of Application for Amendment of License and Soliciting Comments, Motions To Intervene, and Protests </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection: </P>
                <P>
                    a. 
                    <E T="03">Type of Application:</E>
                     Amendment of license (for proposed long-term frost protection and late fall irrigation plan). 
                </P>
                <P>
                    b. 
                    <E T="03">Project No.:</E>
                     77-212. 
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     August 26, 2008. 
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Pacific Gas and Electric Company (licensee). 
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Potter Valley Hydroelectric Project. 
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     On the Eel River and East Branch Russian River in Lake and Mendocino counties, California. 
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Federal Power Act, 16 U.S.C. 791a-825r. 
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     Mr. Richard J. Doble, Senior License Coordinator, Pacific Gas and Electric Company, P.O. Box No. 770000, San Francisco, CA 94177; (415) 973-4480. 
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     CarLisa Linton-Peters, telephone (202) 502-8416; e-mail: 
                    <E T="03">carlisa.linton-peters@ferc.gov</E>
                    . 
                </P>
                <P>j. Deadline for filing comments, motions to intervene and protests is November 4, 2008. </P>
                <P>Please include the project number (P-77) on any comments or motions filed. All documents (an original and eight copies) must be filed with: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. </P>
                <P>
                    Motions to intervene, protests, comments and recommendations may be filed electronically via the Internet in lieu of paper filings, see 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site (
                    <E T="03">http://www.ferc.gov</E>
                    ) under the “e-filing” link. The Commission strongly encourages electronic filings. 
                </P>
                <P>The Commission's Rules of Practice and Procedure require all intervenors filing documents with the Commission to serve a copy of that document on each person whose name appears on the official service list for the project. Further, if an intervenor files comments or documents with the Commission relating to the merits of an issue that may affect the responsibilities of a particular resource agency, they must also serve a copy of the document on that resource agency. A copy of any motion to intervene must also be served upon each representative of the Applicant specified in the particular application. </P>
                <P>
                    k. 
                    <E T="03">Description of Request:</E>
                     Pacific Gas and Electric Company (licensee) is requesting that its license for the Potter Valley Project be amended to allow the licensee to implement its proposed plan to provide long-term frost protection and late fall irrigation water for commercial crops in the Potter Valley area. The proposed plan was required 
                    <PRTPAGE P="55829"/>
                    by Commission Order Granting Temporary Amendment of License Article 52, issued March 13, 2008. Implementation of the proposed plan would require modifications to license article 52 which includes the Reasonable and Prudent Alternative of the National Marine Fisheries Service Biological Opinion, approved and made a part of the license by Order Amending License, issued January 28, 2004. 
                </P>
                <P>
                    l. 
                    <E T="03">Location of the Application:</E>
                     A copy of the filing is available for inspection and reproduction at the Commission's Public Reference Room, located at 888 First Street, NE., Room 2A, Washington, DC 20426, or by calling (202) 502-8371. This filing may also be viewed on the Commission's Web site at 
                    <E T="03">http://ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. You may also register online at 
                    <E T="03">http://www.ferc.gov/docsfiling/esubscription.asp</E>
                     to be notified via e-mail of new filings and issuances related to this or other pending projects. For assistance, call toll-free at 1-866-208-3372 or e-mail 
                    <E T="03">ferconlinesupport@ferc.gov</E>
                    , or for TTY, call (202) 502-8659. A copy of this filing is also available for inspection and reproduction at the address listed in item (h) above. 
                </P>
                <P>
                    m. 
                    <E T="03">Mailing list:</E>
                     Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission. 
                </P>
                <P>
                    n. 
                    <E T="03">Comments, Protests, or Motions to Intervene:</E>
                     Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, 385.211, and 385.214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application (see item (j) above). 
                </P>
                <P>o. Any filing must bear in all capital letters the title “COMMENTS”, “PROTEST”, “MOTION TO INTERVENE”, or “RECOMMENDATIONS”, as applicable, and the Project Number of the particular application to which the filing refers. </P>
                <P>
                    p. 
                    <E T="03">Agency Comments:</E>
                     Federal, State, and local agencies are encouraged and invited to file comments on the described application. A copy of the application may be obtained by agencies directly from the Applicant. If an agency does not file comments within the time specified for filing comments (see item (j) above), it will be presumed to have no comments. One copy of an agency's comments must also be sent to the Applicant's representatives. 
                </P>
                <P>
                    q. Comments, protests and motions of intervention may be filed electronically via the Internet in lieu of paper filings. See 18 CFR 385.20019(a)(1)(iii) and the instructions on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov</E>
                     under the “e-Filing” link. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22626 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Project No. 13239-000] </DEPDOC>
                <SUBJECT>Parker Knoll Hydro, LLC; Notice of Preliminary Permit Application Accepted for Filing and Soliciting Comment, Motions To Intervene, and Competing Applications </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>On June 17, 2008, Parker Knoll Hydro, LLC filed an application, pursuant to section 4(f) of the Federal Power Act, proposing to study the feasibility of the Parker Knoll Pumped Storage Project to be located in Piute County, Utah. The project would occupy federal lands of the Bureau of Land Management. </P>
                <P>
                    <E T="03">The proposed project consists of:</E>
                     (1) Two proposed upper reservoir earthen dams, a) 148-foot high, 600-foot-long, b) 32-foot-high, 800-foot-long; (2) a proposed reservoir having a surface area of 125 acres, a storage capacity of 8,212 acre-feet, and normal maximum water surface elevation of 9,610.4 feet msl, (3) a proposed 100-foot-high 4,679-foot-long earthen lower reservoir dam, (4) a proposed lower reservoir having a surface area of 117 acres, a storage capacity of 8,689 acre-feet and normal maximum water surface elevation of 7,109.2 feet msl, (5) a proposed 12,800-foot-long, 25-foot diameter concrete/steel penstock; (6) a proposed powerhouse with ten generating units having a total capacity of 1,330 MW; (7) a proposed 0.30-mile-long, 240-kV transmission line; and (8) appurtenant facilities. The project would have an annual generation of 3,640 GWh, and would be sold to a local utility. 
                </P>
                <P>
                    <E T="03">Applicant Contact:</E>
                     Mr. Brent L. Smith, Symbiotics, LLC, P.O. Box 535 Rigby, ID 83442, Phone: 208-745-0834. FERC Contact: Henry Woo, 202-502-8872. 
                </P>
                <P>
                    Deadline for filing comments, motions to intervene, competing applications (without notices of intent), or notices of intent to file competing applications: 60 days from the issuance of this notice. Comments, motions to intervene, notices of intent, and competing applications may be filed electronically via the Internet. See 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site under the “eFiling” link. If unable to be filed electronically, documents may be paper-filed. To paper-file, an original and eight copies should be mailed to: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. For more information on how to submit these types of filings please go to the Commission's Web site located at 
                    <E T="03">http://www.ferc.gov/filing-comments.asp</E>
                    . More information about this project can be viewed or printed on the “eLibrary” link of the Commission's Web site at 
                    <E T="03">http://www.ferc.gov/docs-filing/elibrary.asp</E>
                    . Enter the docket number (P-13239) in the docket number field to access the document. For assistance, call toll-free 1-866-208-3372. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22621 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Project No. 11879-003] </DEPDOC>
                <SUBJECT>Symbiotics, LLC; Fall River Rural Electric Cooperative, Inc.; Notice of Application for Transfer of License and Soliciting Comments, Motions To Intervene and Protests </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection: </P>
                <P>
                    a. 
                    <E T="03">Type of Application:</E>
                     Transfer of License. 
                </P>
                <P>
                    b. 
                    <E T="03">Project No.:</E>
                     11879-003. 
                </P>
                <P>
                    c. 
                    <E T="03">Date filed:</E>
                     August 12, 2008. 
                </P>
                <P>
                    d. 
                    <E T="03">Applicants:</E>
                     Symbiotics, LLC (transferor); Fall River Rural Electric Cooperative, Inc. (transferee). 
                </P>
                <P>
                    e. 
                    <E T="03">Name and Location of Project:</E>
                     The Chester Diversion Dam Project is located on the Henry's Fork River in Fremont County, Idaho. 
                </P>
                <P>
                    f. 
                    <E T="03">Filed Pursuant to:</E>
                     Federal Power Act, 16 U.S.C. 791(a)-825(r). 
                    <PRTPAGE P="55830"/>
                </P>
                <P>
                    g. 
                    <E T="03">Applicant Contact:</E>
                     For the transferor: Mr. Brent L. Smith, 4110 East 300 North, P.O Box 535, Rigby, ID 83442, (208) 745-0834. 
                </P>
                <P>
                    <E T="03">For the transferee:</E>
                     Mr. Dee M. Reynolds, 1150 N 3400 E, Ashton, ID 83420, (208) 652-7431. 
                </P>
                <P>
                    h. 
                    <E T="03">FERC Contact:</E>
                     Steven Sachs, (202) 502-8666. 
                </P>
                <P>
                    i. 
                    <E T="03">Deadline for filing comments, protests and motions to intervene:</E>
                     October 21, 2008.
                </P>
                <P>All documents (original and eight copies) should be filed with: Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. Comments, protests, and interventions may be filed electronically via the Internet in lieu of paper; see 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site under the “e-Filing” link. The Commission strongly encourages electronic filings. Please include the project number (P-11879-003) on any comments or motions filed. </P>
                <P>The Commission's Rules of Practice and Procedure require all intervenors filing documents with the Commission to serve a copy of that document on each person in the official service list for the project. Further, if an intervenor files comments or documents with the Commission relating to the merits of an issue that may affect the responsibilities of a particular resource agency, they must also serve a copy of the document on that resource agency. </P>
                <P>
                    j. 
                    <E T="03">Description of Application:</E>
                     Applicants seek Commission approval to transfer the license for the Chester Diversion Dam Project from Symbiotics, LLC to Fall River Rural Electric Cooperative, Inc. 
                </P>
                <P>
                    k. This filing is available for review at the Commission in the Public Reference Room or may be viewed on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. For assistance, call toll-free 1-866-208-3372 or e-mail 
                    <E T="03">FERCONLINESUPPORT@FERC.GOV</E>
                    . For TTY, call (202) 502-8659. A copy is also available for inspection and reproduction at the address in item g above. 
                </P>
                <P>l. Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission. </P>
                <P>
                    m. 
                    <E T="03">Comments, Protests, or Motions to Intervene</E>
                    —Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, .214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application. 
                </P>
                <P>
                    n. 
                    <E T="03">Filing and Service of Responsive Documents</E>
                    —Any filings must bear in all capital letters the title “COMMENTS”, “PROTEST”, OR “MOTION TO INTERVENE”, as applicable, and the Project Number of the particular application to which the filing refers. Any of the above-named documents must be filed by providing the original and eight copies to: The Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. A copy of any motion to intervene must also be served upon each representative of the Applicants specified in the particular application. 
                </P>
                <P>
                    o. 
                    <E T="03">Agency Comments</E>
                    —Federal, State, and local agencies are invited to file comments on the described application. A copy of the application may be obtained by agencies directly from the Applicants. If an agency does not file comments within the time specified for filing comments, it will be presumed to have no comments. One copy of an agency's comments must also be sent to the Applicants' representatives. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22617 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Project No. 2225-000] </DEPDOC>
                <SUBJECT>Public Utility District No. 1 of Pend Oreille County; Notice of Authorization for Continued Project Operation </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>On September 23, 2003, the Public Utility District No.1 of Pend Oreille County, licensee for the Sullivan Creek Hydroelectric Project, filed a Notice of Intent Not to File an Application for a New or Subsequent license pursuant to the Federal Power Act (FPA) and the Commission's regulations thereunder. The Sullivan Creek Hydroelectric Project is located on Sullivan Creek in Pend Oreille County, Washington. </P>
                <P>The license for Project No. 2225 was issued for a period ending September 30, 2008. Section 15(a)(1) of the FPA, 16 U.S.C. 808(a)(1), requires the Commission, at the expiration of a license term, to issue from year-to-year an annual license to the then licensee under the terms and conditions of the prior license until a new license is issued, or the project is otherwise disposed of as provided in section 15 or any other applicable section of the FPA. If the project's prior license waived the applicability of section 15 of the FPA, then, based on section 9(b) of the Administrative Procedure Act, 5 U.S.C. 558(c), and as set forth at 18 CFR 16.21(a), if the licensee of such project has filed an application for a subsequent license, the licensee may continue to operate the project in accordance with the terms and conditions of the license after the minor or minor part license expires, until the Commission acts on its application. If the licensee of such a project has not filed an application for a subsequent license, then it may be required, pursuant to 18 CFR 16.21(b), to continue project operations until the Commission issues someone else a license for the project or otherwise orders disposition of the project. </P>
                <P>If the project is subject to section 15 of the FPA, notice is hereby given that an annual license for Project No. 2225 is issued to the Public Utility District No.1 of Pend Oreille County, for a period effective October 1, 2008 through September 30, 2009, or until the issuance of a new license for the project or other disposition under the FPA, whichever comes first. If issuance of a new license (or other disposition) does not take place on or before September 30, 2009, notice is hereby given that, pursuant to 18 CFR 16.18(c), an annual license under section 15(a)(1) of the FPA is renewed automatically without further order or notice by the Commission, unless the Commission orders otherwise. If the project is not subject to section 15 of the FPA, notice is hereby given that the Public Utility District NO.1 of Pend Oreille County, is authorized to continue operation of the Sullivan Creek Hydroelectric Project, until such time as the Commission acts on its application for a subsequent license. </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22623 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="55831"/>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <SUBJECT>Combined Notice of Filings </SUBJECT>
                <DATE>September 23, 2008. </DATE>
                <P>Take notice that the Commission has received the following Natural Gas Pipeline Rate and Refund Report filings: </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP00-426-038. 
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Texas Gas Transmission, LLC. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Texas Gas Transmission LLC submits Original Sheet 55G et al to FERC Gas Tariff, Second Revised Volume 1. 
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     09/12/2008. 
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20080916-0029. 
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Friday, September 26, 2008. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP08-628-000. 
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     CenterPoint Energy—Mississippi River Transmission Corporation. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     CenterPoint Energy—Mississippi River Transmission Corporation submits Sixty-Fourth Revised Sheet 5 et al to FERC Gas Tariff, Third Revised Volume 1, to be effective 11/1/08. 
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     09/22/2008. 
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20080922-0261. 
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, October 06, 2008. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP08-629-000. 
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Dominion Cove Point LNG, LP. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Report of Revenue Crediting of Dominion Cove Point LNG, LP. 
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     09/22/2008. 
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20080922-5097. 
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, October 06, 2008. 
                </P>
                <P>Any person desiring to intervene or to protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214) on or before 5 p.m. Eastern time on the specified comment date. It is not necessary to separately intervene again in a subdocket related to a compliance filing if you have previously intervened in the same docket. Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant. In reference to filings initiating a new proceeding, interventions or protests submitted on or before the comment deadline need not be served on persons other than the Applicant. </P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov.</E>
                     To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests. 
                </P>
                <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First St., NE., Washington, DC 20426. </P>
                <P>
                    The filings in the above proceedings are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed dockets(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov.</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659. 
                </P>
                <SIG>
                    <NAME>Nathaniel J. Davis, Sr., </NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22680 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Docket No. CP07-444-000; Docket No. CP07-441-000] </DEPDOC>
                <SUBJECT>Jordan Cove Energy Project, L.P.; Pacific Connector Gas Pipeline Project, L.P.; Notice of Public Meetings To Take Comments on the Draft Environmental Impact Statement for the Proposed Jordan Cove Energy and Pacific Connector Gas Pipeline Project </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>The staff of the Federal Energy Regulatory Commission (FERC or Commission) is issuing this notice to announce a series of public meetings to take comments on the draft Environmental Impact Statement (EIS) issued by the FERC on August 29, 2008, for the proposed Jordan Cove Energy liquefied natural gas (LNG) Project and Pacific Connector Gas Pipeline Project. The draft EIS addresses the proposal by Jordan Cove Energy Project, L.P. (Jordan Cove) to construct and operate an LNG import terminal on Coos Bay in Coos County, Oregon, in Docket No. CP07-444-000, and the proposal by Pacific Connector Gas Pipeline, L.P. to construct a 230-mile-long natural gas sendout pipeline that would cross portions of Coos, Douglas, Jackson, and Klamath Counties, Oregon, in Docket No. CP07-441-000. The proposed pipeline would connect the proposed Jordan Cove LNG terminal with existing interstate pipeline systems operated by Williams Northwest Pipeline Corporation, Gas Transmission Northwest Corporation, Tuscarora Gas Transmission Company, and Pacific Gas and Electric Company, and with an existing local distribution pipeline system operated by Avista Corporation. </P>
                <P>The FERC staff produced the draft EIS in cooperation with the U.S. Department of Agriculture Forest Service, U.S. Army Corps of Engineers, U.S. Environmental Protection Agency, U.S. Department of Homeland Security Coast Guard, U.S. Department of the Interior Bureau of Land Management and Bureau of Reclamation, U.S. Department of Transportation, and Douglas County, Oregon. The draft EIS was delivered to the U.S. Environmental Protection Agency, and mailed to various federal, state, and local government agencies, elected officials, affected landowners, regional environmental organizations, Indian tribes, local libraries and newspapers, intervenors, and other interested parties. </P>
                <P>
                    The issuance of the draft EIS was noticed in the 
                    <E T="04">Federal Register</E>
                     on September 5, 2008 (73 FR 51815). The deadline for comments on the draft EIS is December 4, 2008. In addition to, or in lieu of, sending in written comments on the draft EIS, the FERC and cooperating agencies invite you to attend the public comment meetings that will be held in the project area in October 2008, on the dates, times, and locations listed below. 
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s75,r75">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Date and Time</CHED>
                        <CHED H="1">Location </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Monday, October 27, 2008, 6:30 p.m. to 10 p.m. (PST)</ENT>
                        <ENT> North Bend Community Center, 2222 Broadway Street, North Bend, Oregon 97459. Telephone: 541-756-8500.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="55832"/>
                        <ENT I="01">Tuesday, October 28, 2008, 6:30 p.m. to 10 p.m. (PST) </ENT>
                        <ENT>Umpqua Community College, Campus Center Dining Room/Timber Room, 1140 Umpqua College Road, Roseburg, Oregon 97470, Telephone: 541-440-4600.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wednesday, October 29, 2008, 6:30 p.m. to 10 p.m. (PST) </ENT>
                        <ENT> Red Lion Inn, Rogue River Ballroom, 200 N. Riverside Avenue, Medford, Oregon 97501, Telephone: 541-779-5811.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thursday, October 30, 2008, 6:30 p.m. to 10 p.m. (PST) </ENT>
                        <ENT> Oregon Institute of Technology, College Union Auditorium, 3201 Campus Drive, Klamath Falls, Oregon 97601, Telephone: 541-885-1000, 1032.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    These events are posted on the Commission's calendar located at 
                    <E T="03">http://www.ferc.gov/EventCalendar/EventsList.aspx</E>
                     along with other related information. For additional information, please contact the Commission's Office of External Affairs at 1-866-208-FERC. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22627 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Docket No. ER08-1385-000] </DEPDOC>
                <SUBJECT>Black Hills/Colorado Electric Utility Company, LP; Notice of Filing </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>Take notice that on August 13, 2008, Black Hills/Colorado Electric Utility Company, LP filed a market-based rate wholesale power sales tariff in place of the market-based wholesale power sales tariff of its predecessor, Aquila, Inc. </P>
                <P>Any person desiring to intervene or to protest this filing must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211, 385.214). Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Any person wishing to become a party must file a notice of intervention or motion to intervene, as appropriate. Such notices, motions, or protests must be filed on or before the comment date. On or before the comment date, it is not necessary to serve motions to intervene or protests on persons other than the Applicant. </P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper using the “eFiling” link at 
                    <E T="03">http://www.ferc.gov</E>
                    . Persons unable to file electronically should submit an original and 14 copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. 
                </P>
                <P>
                    This filing is accessible online at 
                    <E T="03">http://www.ferc.gov</E>
                    , using the “eLibrary” link and is available for review in the Commission's Public Reference Room in Washington, DC. There is an “eSubscription” link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                    , or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659. 
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on September 29, 2008. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22615 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Docket No. ER08-1513-001] </DEPDOC>
                <SUBJECT>ISO New England Inc.; Notice of Filing </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>Take notice that on September 16, 2008, ISO New England, Inc. submitted for filing an Errata to the Informational Filing for Qualification in the Forward Capacity Market. </P>
                <P>Any person desiring to intervene or to protest this filing must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211, 385.214). Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Any person wishing to become a party must file a notice of intervention or motion to intervene, as appropriate. Such notices, motions, or protests must be filed on or before the comment date. Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant and all the parties in this proceeding. </P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper using the “eFiling” link at 
                    <E T="03">http://www.ferc.gov</E>
                    . Persons unable to file electronically should submit an original and 14 copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. 
                </P>
                <P>
                    This filing is accessible online at 
                    <E T="03">http://www.ferc.gov</E>
                    , using the “eLibrary” link and is available for review in the Commission's Public Reference Room in Washington, DC. There is an “eSubscription” link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                    , or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659. 
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on September 26, 2008. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22616 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Docket Nos. PH08-24-001; PH08-25-001] </DEPDOC>
                <SUBJECT>Horizon Asset Management, Inc.; Order Tolling 60-Day Period for Action To Allow for Further Consideration </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>
                    To afford additional time for further consideration of the matters at issue in the above-captioned proceeding, the 60-day period for action is hereby tolled. 18 CFR 366.4(b)(1), 366.4(c)(1). The temporary exemption or waiver provided by the regulations will remain in effect until such time as the Commission has determined whether to grant or deny the requested exemption or waiver. 
                    <E T="03">Id.</E>
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22614 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="55833"/>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Project No. 13101-000] </DEPDOC>
                <SUBJECT>Barrington Hydro LLC; Notice of Preliminary Permit Application Accepted for Filing and Soliciting Comment, Motions To Intervene, and Competing Applications </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>On January 23, 2008, Barrington Hydro LLC filed an application, pursuant to section 4(f) of the Federal Power Act, proposing to study the feasibility of the Barrington Hydroelectric Project to be located in Berkshire County, Massachusetts. </P>
                <P>
                    <E T="03">The proposed project consists of:</E>
                     (1) An existing 22-foot high 130-foot-long concrete and timber crib dam; (2) a proposed reservoir having a normal maximum water surface elevation of 716 feet (ngvd) and a surface area of 40 acres, with negligible storage capacity; (3) an existing 190-foot-long, 14-foot diameter concrete penstock; (4) a proposed powerhouse with two generating units having a total capacity of 1,100 KW; (5) a proposed 450-foot-long, 24-KV transmission line; and (6) appurtenant facilities. The project would have an annual generation of 4,300 MWh, and would be sold to a local utility. 
                </P>
                <P>
                    <E T="03">Applicant Contact:</E>
                     Mr. Robert Munch, Barrington Hydro LLC, P.O. Box 1854 Lenox, MA 01240, Phone: 323-481-4460. FERC Contact: Henry Woo, 202-502-8872. 
                </P>
                <P>
                    Deadline for filing comments, motions to intervene, competing applications (without notices of intent), or notices of intent to file competing applications: 60 days from the issuance of this notice. Comments, motions to intervene, notices of intent, and competing applications may be filed electronically via the Internet. See 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site under the “eFiling” link. If unable to be filed electronically, documents may be paper-filed. To paper-file, an original and eight copies should be mailed to: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. For more information on how to submit these types of filings please go to the Commission's Web site located at 
                    <E T="03">http://www.ferc.gov/filing-comments.asp</E>
                    . More information about this project can be viewed or printed on the “eLibrary” link of the Commission's Web site at 
                    <E T="03">http://www.ferc.gov/docs-filing/elibrary.asp</E>
                    . Enter the docket number (P-13101) in the docket number field to access the document. For assistance, call toll-free 1-866-208-3372. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22619 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
              
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Project No. 12532-002] </DEPDOC>
                <SUBJECT>Pine Creek Mine LLC; Notice of Preliminary Permit Application Accepted for Filing and Soliciting Comment, Motions To Intervene, and Competing Applications </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>On March 3, 2008, Pine Creek Mine, LLC filed an application, pursuant to section 4(f) of the Federal Power Act (FPA), to study the feasibility of the Pine Creek Mine Project to be located on Morgan and Pine Creeks, in Inyo County, California. The project would be located within the Inyo National Forest on lands of the U.S. Forest Service. </P>
                <P>The proposed project would consist of: (1) The existing Pine Creek Mine site and 12,000 foot-long, 12 feet by 12 feet access tunnel; (2) an existing 12′  x 12′  by 30′  thick reinforced concrete plug in the Pine Creek Mine; (3) a proposed 24” or 18” -diameter steel penstock; (4) a proposed 1,500-kw generating unit; (5) a proposed 2.4 kV 2,500-foot-long transmission line; and (6) appurtenant facilities. The project would have an annual generation of 5.6 gigawatt-hours that would be sold to a local utility. </P>
                <P>
                    <E T="03">Applicant Contact:</E>
                     Mr. Fred Springer, Hydropower Policy Advisor, Troutman Sanders LLP, 401 Ninth Street, NW., Suite 1000, Washington, DC 20004-2134, (202) 274-2836. 
                    <E T="03">FERC Contact:</E>
                     Henry Woo, (202) 502-8872. 
                </P>
                <P>
                    Deadline for filing comments, motions to intervene, competing applications (without notices of intent), or notices of intent to file competing applications: 60 days from the issuance of this notice. Comments, motions to intervene, notices of intent, and competing applications may be filed electronically via the Internet. See 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site under the “eFiling” link. If unable to be filed electronically, documents may be paper-filed. To paper-file, an original and eight copies should be mailed to: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. For more information on how to submit these types of filings please go to the Commission's Web site located at 
                    <E T="03">http://www.ferc.gov/filing-comments.asp.</E>
                     More information about this project can be viewed or printed on the “eLibrary” link of the Commission's Web site at 
                    <E T="03">http://www.ferc.gov/docs-filing/elibrary.asp.</E>
                     Enter the docket number (P-12532) in the docket number field to access the document. For assistance, call toll-free 1-866-208-3372. 
                </P>
                <SIG>
                    <NAME>Kimberly D. Bose, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22618 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>National Nuclear Security Administration </SUBAGY>
                <SUBJECT>Record of Decision: Site-Wide Environmental Impact Statement for Continued Operation of Los Alamos National Laboratory, Los Alamos, NM</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Energy, National Nuclear Security Administration. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Record of decision.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The National Nuclear Security Administration (NNSA) of the U.S. Department of Energy (DOE) is issuing this Record of Decision (ROD) for the continued operation of the Los Alamos National Laboratory (LANL) in Los Alamos, New Mexico. This ROD is based on information and analyses contained in the 
                        <E T="03">Final Site-Wide Environmental Impact Statement for the Continued Operation of Los Alamos National Laboratory, Los Alamos, New Mexico,</E>
                         DOE/EIS-0380 (Final SWEIS or 2008 SWEIS) issued on May 16, 2008; comments on the SWEIS; and other factors, including costs, security considerations and the missions of NNSA. 
                    </P>
                    <P>
                        In the 2008 SWEIS, NNSA assessed three alternatives for the continued operation of LANL:  (1) No Action, (2) Reduced Operations, and (3) Expanded Operations. The No Action Alternative analyzed in this SWEIS consists of NNSA and LANL continuing to implement earlier decisions based on previous National Environmental Policy Act (NEPA) reviews, including the 1999 LANL SWEIS (DOE/EIS-0238) and its ROD (64 FR 50797, Sept. 20, 1999). The 2008 SWEIS identified the Expanded Operations Alternative as NNSA's Preferred Alternative. The SWEIS includes a classified appendix that assesses the potential environmental 
                        <PRTPAGE P="55834"/>
                        impacts of a representative set of credible terrorist scenarios. 
                    </P>
                    <P>Because NNSA is continuing to evaluate significant technical and national security issues that could affect the operation and missions of LANL, NNSA is making only a few decisions at this time regarding the continued operation of the laboratory. NNSA will not make any decisions regarding nuclear weapons production and other actions analyzed in the Complex Transformation Supplemental Programmatic Environmental Impact Statement (DOE/EIS-0236-S4) (Complex Transformation SPEIS or SPEIS) prior to the completion of the SPEIS. However, NNSA must make some decisions now regarding LANL to support the safe and successful execution of the laboratory's current missions. It is likely that NNSA will issue other RODs regarding the continued operation of LANL based on the 2008 SWEIS, the SPEIS and other NEPA analyses. </P>
                    <P>NNSA has decided to continue to implement the No Action Alternative with the addition of some elements of the Expanded Operations Alternative. These elements include increases in operation of some existing facilities and new facility projects needed for ongoing programs and protection of workers and the environment. For the most part, NNSA will continue the missions conducted at LANL at current levels at this time. NNSA will also continue to implement actions necessary to comply with the March 2005 Compliance Order on Consent (Consent Order), which requires investigation and remediation of environmental contamination at LANL. NNSA will not change pit production at LANL at this time; the 1999 ROD set pit production at LANL at 20 per year. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For further information on the 2008 LANL SWEIS or this ROD, or to receive a copy of this SWEIS or ROD, contact: Ms. Elizabeth Withers, Document Manager, U.S. Department of Energy, National Nuclear Security Administration Service Center, Post Office Box 5400, Albuquerque, NM 87185, (505) 845-4984. Questions about the SWEIS, ROD and other issues regarding the Los Alamos Site Office's NEPA compliance program may also be addressed to Mr. George J. Rael, Assistant Manager Environmental Operations, NEPA Compliance Officer, U.S. Department of Energy, National Nuclear Security Administration, Los Alamos Site Office, 3747 West Jemez Road, Los Alamos, NM 87544. Mr. Rael may be contacted by telephone at (505) 665-0308, or by e-mail at: 
                        <E T="03">LASO.SWEIS@doeal.gov</E>
                        . For information on the DOE NEPA process, contact: Ms. Carol M. Borgstrom, Director, Office of NEPA Policy and Compliance (GC-20), U.S. Department of Energy, 1000 Independence Avenue, SW., Washington, DC 20585, (202) 586-4600, or leave a message at (800) 472-2756. Additional information regarding DOE NEPA activities and access to many DOE NEPA documents are available on the Internet through the DOE NEPA Web site at: 
                        <E T="03">http://www.gc.energy.gov/nepa/</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>NNSA prepared this ROD pursuant to the regulations of the Council on Environmental Quality (CEQ) for implementing NEPA (40 CFR Parts 1500-1508) and DOE's NEPA Implementing Procedures (10 CFR Part 1021). DOE last issued a SWEIS and ROD for the continued operation of LANL in 1999. DOE's NEPA regulations require that the Department evaluate site-wide NEPA analyses every five years to determine their continued applicability; NNSA initiated such an evaluation of the 1999 SWEIS in 2004. It subsequently decided to prepare a new SWEIS. NNSA issued a Draft SWEIS in July 2006 for public review and comment during a 75-day period. It considered the comments received on the Draft SWEIS in preparing the Final SWEIS, which it issued on May 16, 2008. </P>
                <P>LANL is a multidisciplinary, multipurpose research institution in north-central New Mexico, about 60 miles (97 kilometers) north-northeast of Albuquerque, and about 25 miles (40 kilometers) northwest of Santa Fe. LANL occupies approximately 25,600 acres (10,360 hectares), or 40 square miles (104 square kilometers). About 2,000 structures, with a total of approximately 8.6 million square feet under roof, house LANL operations and activities, with about one half of the area used as laboratory or production space, and the remainder used for administrative, storage, services, and other purposes. </P>
                <P>LANL is one of NNSA's three national security laboratories. Facilities and expertise at LANL are used to perform science and engineering research; the laboratory also manufactures some nuclear weapons components such as plutonium pits. In addition to weapons component manufacturing, LANL performs weapons testing, stockpile assurance, component replacement, surveillance, and maintenance. LANL's research and development activities include high explosives processing, chemical research, nuclear physics research, materials science research, systems analysis and engineering, human genome mapping, biotechnology applications, and remote sensing technologies. The main role of LANL in the fulfillment of NNSA and DOE missions is scientific and technological work that supports nuclear materials handling, processing, and fabrication; stockpile management; materials and manufacturing technologies; nonproliferation programs; and waste management activities. Work at LANL is also conducted for other Federal agencies such as the Departments of Defense and Homeland Security, as well as universities, institutions, and private entities. </P>
                <HD SOURCE="HD1">Alternatives Considered </HD>
                <P>The alternatives NNSA evaluated in the SWEIS span a range of operations from minimum levels that would maintain essential mission capabilities (Reduced Operations Alternative) through the highest reasonably foreseeable levels that could be supported by current or new facilities (Expanded Operations Alternative). The No Action Alternative evaluated in the SWEIS consists of the continued implementation of decisions announced in the 1999 SWEIS ROD and decisions based on other completed NEPA reviews. The Reduced Operations Alternative assumes a reduction in the levels of certain operations and activities from the levels evaluated in the No Action Alternative. The Expanded Operations Alternative includes activities evaluated in the No Action Alternative, increases in overall operational levels, and new projects that fall into three categories: (1) Projects to maintain existing operations and capabilities (such as projects to replace aging structures with modern ones, and projects to consolidate operations and eliminate unneeded structures); (2) projects that support environmental remediation at LANL and compliance with the Consent Order, including demolition of excess buildings; and (3) projects that add new infrastructure and expand existing capabilities. </P>
                <HD SOURCE="HD1">Compliance With the Consent Order </HD>
                <P>
                    NNSA and LANL will continue to implement actions necessary to comply with the Consent Order, which requires the investigation and remediation of environmental contamination at LANL, regardless of the alternative it selects for the continued operation of the laboratory. The 2008 SWEIS analyzes the environmental impacts of actions 
                    <PRTPAGE P="55835"/>
                    required under the Consent Order,
                    <SU>1</SU>
                    <FTREF/>
                     and actions proposed by NNSA to facilitate its compliance with the Order (such as replacement of waste management structures, and establishment of waste examination and staging areas) under the Expanded Operations Alternative so that the impacts of these actions can be distinguished from the impacts of other proposed actions. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The Consent Order was issued by the New Mexico Environment Department (NMED). As NMED makes the decisions regarding the requirements of the Order, these decisions are not subject to NEPA because they are not “federal actions.”
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Preferred Alternative </HD>
                <P>The preferred alternative is the alternative that NNSA believes would best fulfill its statutory mission responsibilities while giving consideration to economic, budget, environmental, schedule, policy, technical and other information. In both the Draft and the Final SWEIS, NNSA identified the Expanded Operations Alternative as its preferred alternative. </P>
                <HD SOURCE="HD1">Environmentally Preferable Alternative </HD>
                <P>NEPA's Section 101 (42 U.S.C. 4331) establishes a policy of federal agencies having a continuing responsibility to improve and coordinate their plans, functions, programs and resources so that, among other goals, the nation may fulfill its responsibilities as a trustee of the environment for succeeding generations. The Council on Environmental Quality (CEQ), in its “Forty Most Asked Questions Concerning CEQ's NEPA Regulations” (46 FR 18026, Feb. 23, 1981), defines the “environmentally preferable alternative” as the alternative “that will promote the national environmental policy expressed in NEPA's Section 101.” </P>
                <P>The analyses in the SWEIS of the environmental impacts associated with operating LANL identified only minor differences among the three alternatives across natural and cultural resource areas. Within each of the alternatives there are actions that could result in negative impacts, as well as those that would produce positive environmental effects. Considering the many environmental facets of the alternatives analyzed in the SWEIS, and looking out over the long term, NNSA believes that implementation of the Expanded Operations Alternative would allow it to best achieve its environmental trustee responsibilities under Section 101 of NEPA. Facilitating the cleanup of the site with new or expanded waste management facilities, and replacing older laboratory and production facilities with new buildings that incorporate modern safety, security and efficiency standards, would improve LANL's ability to protect human health and the environment while allowing LANL to continue to fulfill its national security missions. Increasing operational levels and performing various demolition activities would use additional resources and generate additional waste, but NNSA would also undertake actions to modernize and replace older facilities with more energy efficient and environmentally-protective facilities and to implement waste control and environmental practices to minimize impacts. Many of these types of actions are not feasible with the outdated infrastructure currently at LANL. Under this alternative, NNSA would be better positioned to minimize the use of electricity and water, streamline operations through consolidation, reduce the “footprint” of LANL as a whole, and allow some areas to return to a natural state. </P>
                <HD SOURCE="HD1">NNSA's Responsibilities to Tribal Governments </HD>
                <P>
                    NNSA recognizes that the operation of LANL over the last 65 years has affected the people of neighboring communities in northern New Mexico, including Tribal communities. These effects, which vary in nature across communities, include alterations of lifestyles, community, and individual practices. With respect to Tribal communities, NNSA adheres to federal statutes such as the Native American Graves Protection and Repatriation Act, the Archaeological Resources Protection Act, the American Indian Religious Freedom Act, and the National Historic Preservation Act. NNSA follows Executive Order 13175, 
                    <E T="03">Consultation and Coordination with Indian Tribal Governments</E>
                    ; Executive Order 13007, 
                    <E T="03">Indian Sacred Sites</E>
                    ; Executive Order 13021, 
                    <E T="03">Tribal Colleges and Universities</E>
                    ; and Executive Order 12898, 
                    <E T="03">Federal Actions to Address Environmental Justice in Minority Populations and Low-Income Populations</E>
                    . NNSA also follows the 2004 Presidential Memorandum regarding Government-to-Government Relationships with Native American Tribal Governments, DOE's American Indian and Alaska Native Tribal Government Policy, DOE Order 1230.2 and DOE Notice 144.1, which establish principles and policies for the Department's relations with Tribes. NNSA has established cooperative agreements with Tribal nations that are located near NNSA sites to enhance their involvement in environmental restoration while protecting Tribal rights and resources. 
                </P>
                <P>Four Pueblo governments in the vicinity of LANL have signed individual Accord Agreements with NNSA (Santa Clara, San Ildefonso, Cochiti, and Jemez). The Accord Agreements, together with the recently established Environmental Management/NNSA tribal framework, provide a basis for conducting government-to-government relations and serve as a foundation for addressing issues of mutual concern between the Department and the Pueblos. In furtherance of these Accord Agreements, and specifically to address concerns and issues raised by the Santa Clara Pueblo, the implementation of the decisions in this ROD will be undertaken in conjunction with a Mitigation Action Plan (MAP), which will be updated as needed to address specific concerns and issues raised by the Santa Clara and other Tribal communities. </P>
                <HD SOURCE="HD1">Environmental Impacts of Alternatives </HD>
                <P>NNSA analyzed the potential impacts of each alternative on land use; visual resources; site infrastructure; air quality; noise; geology and soils; surface and groundwater quality; ecological resources; cultural and paleontological resources; socioeconomics; human health impacts; environmental justice; and waste management and pollution prevention. NNSA also evaluated the impacts of each alternative as to irreversible or irretrievable commitments of resources, and the relationship between short-term uses of the environment and the maintenance and enhancement of long-term productivity. In addition, it evaluated impacts of potential accidents at LANL on workers and surrounding populations. In a classified appendix, NNSA also evaluated the potential impacts of intentional destructive acts that might occur at LANL. </P>
                <P>
                    The 2008 SWEIS's impact analyses for normal operations (i.e., operations without accidents or intentional destructive acts) identified the most notable differences in potential environmental impacts among the alternatives in the following resource areas: 
                    <E T="03">geology and soils; radiological air quality; human health; site infrastructure (electric power use, natural gas demand, potable water demand, and waste management demands); and transportation</E>
                    . It also identified minor differences in potential environmental impacts among the alternatives under normal operations for: 
                    <E T="03">land use; visual environment; surface water resources; groundwater resources; non-radiological air quality; noise levels; ecological resources; cultural resources; and socioeconomics</E>
                    . 
                    <PRTPAGE P="55836"/>
                    These findings are described in the Summary and Chapters 4 and 5 of the SWEIS. 
                </P>
                <P>
                    Environmental justice was an impact area of particular concern among those who commented on the SWEIS. NNSA recognizes that the operation of LANL over the last 65 years has affected the people of neighboring communities, including minority and low-income households. These effects, which vary in nature across communities, include alterations of lifestyles, community, and individual practices. Executive Order 12898, 
                    <E T="03">Federal Actions to Address Environmental Justice in Minority Populations and Low-Income Populations</E>
                    , requires every Federal agency to analyze whether its proposed actions and alternatives would have disproportionately high and adverse impacts on minority or low-income populations. Based on the impacts analysis, NNSA expects no disproportionately high and adverse impacts on minority or low-income populations from the continued operation of LANL under any of the alternatives. From the analysis conducted of the alternatives, the radiological dose from emissions from normal operations are slightly lower for members of Hispanic, Native American, total minority, and low-income populations than for members of the population that are not in these groups, mainly because of the locations of these populations relative to the operations at LANL that produce these emissions. The maximum annual dose for the average member of any of the minority or low-income populations is estimated to be 0.092 millirem compared to a dose of 0.10 millirem for a member of the general population, and a dose of 0.11 millirem for a member of the population that does not belong to a minority or low-income group. 
                </P>
                <P>NNSA also analyzed human health impacts from exposure through special pathways, including subsistence consumption of native vegetation (piñon nuts and Indian Tea [Cota]), locally grown produce and farm products, groundwater, surface waters, fish (game and nongame), game animals, other foodstuffs and incidental consumption of soils and sediments (on produce, in surface water, and from ingestion of inhaled dust). These special pathways can be important to the environmental justice analyses because some of them may be more important or prevalent as to the traditional and cultural practices of members of minority populations in the area. The analyses conducted for the 2008 SWEIS, however, show that the health impacts associated with these special pathways do not result in disproportionately high and adverse impacts to minority or low-income populations. </P>
                <P>The SWEIS analyzed potential accidents at LANL. Bounding accidents for both nuclear materials handling and waste management operations and for chemical handling and waste management operations, were identified as those with the highest potential consequences to the offsite population under median site meteorological conditions. Chemicals of concern were selected from a database based on quantities, chemical properties, and human health effects. In making the decisions announced in this ROD, NNSA considered the potential accidents analyzed in the SWEIS for each of the three alternative levels of LANL operations. For the most part, there are few differences among the alternatives for the maximum potential wildfire, seismic, or facility operational accident at LANL because actions under each alternative do not, for the most part, affect the location, frequency, or material at risk of the analyzed accident scenarios. Potential accidents that could occur under the No Action Alternative could also occur under both the Reduced Operations and the Expanded Operations Alternatives. In general, TA-54 waste management operations dominate the potential radiological accident risks and consequences at LANL under all three alternatives. </P>
                <P>Under both the No Action and the Reduced Operations Alternatives, the accident with the highest estimated consequences to offsite populations involving radioactive material or wastes is a lightning-initiated fire at the Radioassay and Nondestructive Testing Facility in TA-54. Such an accident could result in up to 6 additional latent cancer fatalities (LCFs) in the offsite population. A fire at the Plutonium Facility's material staging area located within TA-55 could result in up to 5 additional LCFs in the offsite population. The potential accident expected to result in the highest estimated consequences to the hypothetical maximally exposed individual (MEI) and a non-involved nearby worker would be a fire in a waste storage dome at TA-54. If that accident were to occur, a single LCF to a noninvolved worker located 110 yards (100 meters) away from the site of the accident would be likely, and there could also be a 1 in 2 likelihood (0.50) of a LCF to the MEI, who is assumed to be located at the nearest site boundary for the duration of the accident. The lightning-initiated fire accident at the Radioassay and Nondestructive Testing Facility could also result in a single LCF to a noninvolved worker located 110 yards (100 meters) away from the site of the accident, and could also result in about the same 1 in 2 likelihood (0.49) of a LCF to the MEI assumed to be located at the nearest boundary for the duration of the accident. </P>
                <P>Under the Expanded Operations Alternative, there is a potential for a radiological accident unique to this alternative. The radiological accident most likely to result in the highest estimated consequences to the offsite population is a building fire involving radioactive sealed sources stored at the Chemistry and Metallurgy Research Building. Such an accident could result in up to 7 additional LCFs in the offsite population. The potential accident expected to result in the highest estimated consequences to the hypothetical MEI and a non-involved nearby worker would be the same as for the No Action Alternative, namely, a fire in a waste storage dome at TA-54. </P>
                <P>DOE evaluates the exposure risks associated with chemicals of concern and the requirements for crisis response personnel to use personal protection to avoid potentially dangerous exposures through its system of Emergency Response Planning Guidelines (ERPG). Chemicals of concern in the analyzed accidents at LANL under both the No Action and Reduced Operations Alternatives include selenium hexafluoride and sulfur dioxide, both from waste cylinder storage at TA-54, and chlorine and helium gases located at TA-55. Annual risks of worker and public exposure in the event of chemical releases are greatest from chlorine and helium gases. The annual risk is estimated to be about one chance in 15 years for workers within 1,181 yards (1,080 meters) of the facility receiving exposures in excess of the ERPG limits for chlorine gas, with the nearest public access located at 1,111 yards (1,016 meters). The annual risk is estimated to be about one chance in 15 years for workers within 203 yards (186 meters) of the facility receiving exposures in excess of ERPG limits for helium gas, with the nearest public access at 1,146 yards (1,048 meters). </P>
                <P>
                    Cleanup activities of Material Disposal Areas (MDAs) are analyzed under the Expanded Operations Alternative. These activities pose a risk of accidental releases of toxic chemicals, as there is a degree of uncertainty about how much and what chemicals were disposed of in the MDAs. MDA B is the closest disposal area to the boundary of LANL that will require remediation; remediation by waste removal was assumed for the analysis of a bounding accidental chemical release. Sulfur 
                    <PRTPAGE P="55837"/>
                    dioxide gas and beryllium powder were chosen as the bounding chemicals of concern for this area based on their ERPG values. If present at MDA B in the quantities assumed, both of these chemicals would likely dissipate to safe levels very close to the point of their release. However, there is a potential risk to the public due to the short distance between MDA B and the nearest point where a member of the public might be. 
                </P>
                <HD SOURCE="HD1">Comments on the Final Site-Wide Environmental Impact Statement </HD>
                <P>NNSA distributed more than 1,030 copies of the Final SWEIS to Congressional members and committees, the State of New Mexico, Tribal governments and organizations, local governments, other Federal agencies, non-governmental organizations, and individuals. NNSA received comments on the Final SWEIS from the Santa Clara Indian Pueblo; the Members and Residents of Santa Clara Pueblo; Concerned Citizens for Nuclear Safety, together with Robert H. Gilkeson and the Embudo Valley Environmental Monitoring Group; Citizen Action New Mexico; Nuclear Watch New Mexico; Citizens for Alternatives to Radioactive Dumping, and from nearby farmers. </P>
                <P>Comments on the Final SWEIS included issues already raised during the comment period for the Draft SWEIS. Volume 3 of the Final SWEIS contains all comments received on the Draft SWEIS and NNSA's responses to them; this chapter also describes how these comments resulted in changes to the SWEIS. </P>
                <P>The Santa Clara Indian Pueblo identified three main areas of concern: (1) Government-to-government consultation should have taken place before the issuance of the Final SWEIS; (2) environmental justice issues (including cumulative impacts) were not analyzed properly in the Final SWEIS; and (3) going forward with an increase in plutonium pit production at this time would be premature and violate NEPA. In a letter signed by 226 individuals, the Members and Residents of the Santa Clara Pueblo stated their support for comments on the SWEIS submitted by the tribal leaders. They also stated their opposition to increased plutonium pit production and specifically asked “that (1) proper analysis of environmental justice and accumulative impacts be completed and circulated to the public for comments; (2) that NNSA/DOE honor government-to-government consultation and the process as a trust to Indian Tribes (Santa Clara Pueblo); and (3) that no decision about increasing plutonium pit production be made until review of this issue mandated in a new law (the National Defense Authorization Act for Fiscal Year 2008) is completed.” </P>
                <P>
                    To the extent that Santa Clara Pueblo perceived NNSA's action in delaying government-to-government consultation until after the issuance of the Final SWEIS and before the issuance of this ROD to be inconsistent with appropriate protocol for such consultations, this was not intended. NNSA believes that it followed the requirements of DOE Order 1230.2, 
                    <E T="03">U.S. Department of Energy American Indian and Alaska Native Tribal Government Policy</E>
                    , in consulting through the formal government-to-government process with Santa Clara Pueblo prior to making the decisions announced in this ROD. However, given the two-year time period between the issuance of the Draft SWEIS in 2006 and the issuance of the Final SWEIS in 2008, NNSA acknowledges that it could have been more prompt in engaging in government-to-government consultation with the Santa Clara Pueblo. NNSA will work to improve its consultation process. 
                </P>
                <P>With regard to the impact analysis of environmental justice issues (including cumulative impacts) in the Final SWEIS, NNSA believes that it appropriately analyzed the potential for disproportionately high and adverse impacts to minority and low-income populations located within a 50-mile radius of LANL under all alternatives, and that it also appropriately analyzed cumulative impacts to the extent that future actions are known or foreseeable. However, NNSA recognizes that many of the concerns the Santa Clara expressed are rooted in protected cultural and religious practices of its people. With this in mind, NNSA will undertake implementation of the decisions announced in this ROD in conjunction with a MAP. The MAP will be updated as the need arises to identify actions that would address specific concerns and issues raised by the Santa Clara as well as those of other tribal entities in the area of LANL. </P>
                <P>NNSA agrees that decisions at this time on proposed actions analyzed in the Complex Transformation SPEIS, including decisions regarding the number of plutonium pits LANL will produce, would be premature. NNSA will not make any decisions on pit production until after it completes the SPEIS. </P>
                <P>Concerned Citizens for Nuclear Safety, together with Robert H. Gilkeson and the Embudo Valley Environmental Monitoring Group, raised several concerns with the Final SWEIS: issuance of the Final SWEIS is premature because there could be a future Congressional change in the purpose and need to operate LANL; there is an uncertain seismic hazard at LANL; the Final SWEIS does not comply with NEPA because it omitted an analysis of prime farmland; LANL does not have a reliable network of monitoring wells; radionuclides have been found in the drinking water wells of Los Alamos County, San Ildefonso Pueblo, and Santa Fe; and storm flow and sediment transport are primary mechanisms for potential contaminant transport beyond LANL's boundaries. </P>
                <P>NNSA does not agree that issuance of the Final SWEIS and a ROD is premature. Should Congress or the President direct changes regarding the purpose and need to operate LANL, NNSA may need to conduct additional NEPA reviews or amend this ROD. Federal agencies always face the possibility that in the future the Congress or the President may direct changes in their missions and responsibilities. At this time, NNSA is making only a limited set of decisions regarding actions that need to be implemented now. These decisions do not limit or prejudice the decisions NNSA may make regarding the programmatic alternatives it is evaluating in the Complex Transformation SPEIS. </P>
                <P>
                    New information about seismic risks at LANL (set forth in the report 
                    <E T="03">Update of the Probabilistic Seismic Hazard Analysis and Development of Seismic Design Ground Motions at the Los Alamos National Laboratory, 2007, LA-UR-07-3965</E>
                    ) may change how hazardous materials are stored, operations are conducted, and facilities are constructed or renovated. NNSA is conducting a systematic review of LANL structures and operations in light of this information. This review, expected to be completed in about one year, will identify any necessary changes to address the new seismic information. NNSA will then implement the necessary changes to LANL facilities and operations based on the review's recommendations. 
                </P>
                <P>
                    NNSA contacted the U.S. Department of Agriculture regarding prime farmland designations in northern New Mexico and included that information in Chapter 4 of the Final SWEIS. No farmland designated by that agency as “prime farmland” is located within Los Alamos or Santa Fe Counties, and only a limited amount of prime farmland is located within a 50-mile radius of LANL in Sandoval and Rio Arriba Counties. The Farmland Protection Policy Act requires that projects receiving Federal funds that would result in the 
                    <PRTPAGE P="55838"/>
                    permanent conversion of prime farmland to non-farmland (or remove its prime rating) must develop and consider alternatives that would not result in the conversion. None of the proposed actions at LANL under any of the alternatives would result in changes to any designated prime farmland or cause it to be re-designated as non-prime farmland. 
                </P>
                <P>Information about the network of monitoring wells, including existing and planned wells, is provided in Chapter 4 of the Final SWEIS. NNSA acknowledges that past well installation practices have not produced the desired network, and will continue to install and refurbish wells until adequate information is obtained regarding groundwater conditions and contaminant transport within the aquifers in the LANL area. Contaminants identified in various drinking water wells are being monitored, and drinking water production from these wells may be adjusted or discontinued in compliance with health protection standards. Additional study of aquifer conditions and contaminant transport is needed before long-term corrective actions can be identified and implemented. Contaminant transport via surface water flow and sediment transport is recognized as the primary mechanisms for off-site transport, especially after storms. As the watershed recovers from the effects of the Cerro Grande Fire in 2000, the volumes of storm water runoff are expected to decrease. </P>
                <P>
                    Citizen Action New Mexico stated its opposition to the Expanded Operations Alternative, especially expanded nuclear weapons research and production, and asserted that the Final SWEIS did not consider the increased impact of plutonium production on children in compliance with Executive Order 13045, 
                    <E T="03">Protection of Children from Environmental Health Risks and Safety Risks</E>
                    . 
                </P>
                <P>NNSA believes it has complied with this Executive Order in the Final SWEIS. NNSA now uses a more conservative dose-to-risk conversion factor in assessing risks of radiation exposures as a result of this Order. Use of the new dose-to-risk conversion factor is one of the changes noted in NNSA's NEPA process since the issuance of the 1999 SWEIS (Chapter 6 and Appendix C of the SWEIS). As noted previously, NNSA is not making any decisions at this time that would result in expansion of nuclear weapons production. </P>
                <P>
                    In comments on the Final SWEIS, Nuclear Watch New Mexico (NWNM) stated that: Expanded plutonium pit production is not necessary; potential impacts of the proposed Radiological Science Institute are not adequately analyzed in the Final SWEIS and that a project-specific EIS is necessary for the institute; waste volumes identified in the Final SWEIS do not reconcile with those in NNSA's Draft Complex Transformation Supplemental Programmatic EIS; there is confusion about whether the proposed Advanced Fuel Cycle Facility, which is the subject of another DOE programmatic EIS, 
                    <E T="03">The Global Nuclear Energy Partnership Programmatic EIS</E>
                     (the GNEP PEIS), would be used for research and development or for full-scale reprocessing (and the number of associated facilities that could be located at LANL); and the Los Alamos Science Complex should be funded through the traditional Congressional budgetary authorization and appropriation process. 
                </P>
                <P>
                    NNSA believes that it appropriately analyzed the potential impacts of the Radiological Science Institute in the Final SWEIS to the extent possible at this stage of the project planning process, and acknowledged in the Final SWEIS that additional NEPA analyses may be necessary if NNSA decides to continue with this proposal. NNSA will reconcile and update waste volumes in the Final Complex Transformation SPEIS. DOE has decided to eliminate the Advanced Fuel Cycle Facility from consideration in the GNEP PEIS (for more information, please visit: 
                    <E T="03">http://www.gnep.energy.gov</E>
                    ). NNSA is considering the use of alternative financing for the Los Alamos Science Complex; this is an appropriate financing approach in certain situations although it has been rarely used at LANL. 
                </P>
                <P>NWNM also asked for additional clarification of some of NNSA's responses to its comments on the Draft SWEIS and provided additional information regarding some of their previous comments. Specifically, NWNM asked if all current tests using plutonium at the Dual Axis Radiographic Hydrodynamic Test Facility (DARHT) are conducted inside vessels. </P>
                <P>At present, NNSA is not conducting any tests at DARHT that use plutonium, and future tests using plutonium at this facility would be conducted inside vessels. </P>
                <P>NWNM asked if the Rendija Canyon Fault is the closest fault to the proposed location of the Radiological Science Institute. </P>
                <P>As discussed in the Final SWEIS, it is the closest known fault to that location. </P>
                <P>NWNM also requested an unclassified appendix that discusses intentional destructive acts at LANL; asserted there should be a citation to information compiled by the U.S. Department of Commerce's Bureau of Economic Analysis; and asked that the Area G Performance Assessment and Composite Analysis and the geotechnical report recently prepared by LANL be posted on the Internet. </P>
                <P>NNSA considered the preparation of an unclassified discussion of the potential environmental impacts of intentional destructive acts at LANL, but concluded that such a discussion posed unacceptable security risks. Information used to prepare the economic impacts analysis was not contained within a discrete study, so a citation is not appropriate in this instance. Unclassified documents prepared by LANL are generally placed on its Internet site when completed and approved for distribution. NWNM may access the LANL Internet site for these specific references. </P>
                <P>NWNM correctly pointed out that the Environmental Protection Agency (EPA) had designated the Española Basin as a Sole Source Aquifer in early 2008. </P>
                <P>Once EPA designates a sole source aquifer under its Sole Source Aquifer Protection Program, the agency can review proposed projects that are to receive Federal funds and that have a potential to contaminate the aquifer. Under this review, EPA can request changes to a Federally-funded project if it poses a threat to public health by contaminating an aquifer to the point where a safe drinking water standard could be violated. Projects conducted entirely by Federal agencies, or their contractors, at sole source aquifer locations are not subject to EPA's review process. NNSA is not proposing any new projects that would cause the Española Basin aquifer to exceed a safe drinking water standard. </P>
                <P>Citizens for Alternatives to Radioactive Dumping also commented on the Final SWEIS. It asserted that expanded pit production is not necessary; that contamination has been found in produce samples; that there is prime farm land in the Embudo Valley; that there are radionuclides in the Rio Grande, which is a threat to its use as drinking water by the city of Santa Fe; and that radioactive cesium has been found in soils at the Trampas Lakes, which drain into the Rio Grande. </P>
                <P>
                    As NNSA noted in its response to other comments on the Draft SWEIS, a single “false positive” result was returned from a laboratory analyzing fruit specimens grown near LANL. No uptake of radioactive contamination 
                    <PRTPAGE P="55839"/>
                    attributed to LANL operations has been found in produce samples obtained from the Embudo Valley. Drinking water supplies for Santa Fe must meet Safe Drinking Water Act and other state and municipal requirements. Elevated radionuclide concentrations in the soils of alpine lake basins within the Rocky Mountain range have been attributed to global fallout concentrated through snowfall and specific geomorphic conditions. 
                </P>
                <HD SOURCE="HD1">Decisions </HD>
                <P>With limited additions, NNSA has decided to continue operation of Los Alamos National Laboratory pursuant to the No Action Alternative analyzed in the 2008 SWEIS. The parameters of this alternative are set by the 1999 ROD and other decisions that NNSA has made previously regarding the continued operation of LANL. The additions to the No Action Alternative NNSA has decided to implement at this time consist of elements of the Expanded Operations Alternative. These elements are of two types: (1) Changes in the level of operations for on-going activities within existing facilities, and (2) new facility projects. The changes in operational levels NNSA has decided to implement at this time are: </P>
                <P>• Supporting the Global Threat Reduction Initiative and Off-Site Sources Recovery Project by broadening the types and quantities of radioactive sealed sources (Co-60, Ir-192, Cf-252, Ra-226) that LANL can manage and store prior to their disposal; </P>
                <P>• Expanding the capabilities and operational level of the Nicholas C. Metropolis Center for Modeling and Simulation to support the Roadrunner Super Computer platform; </P>
                <P>• Performing research to improve beryllium detection and to develop mitigation methods for beryllium dispersion to support industrial health and safety initiatives for beryllium workers; and </P>
                <P>• Retrieval and disposition of legacy transuranic waste (approximately 3,100 cubic yards of contact-handled and 130 cubic yards of remote-handled) from belowground storage. </P>
                <P>New facility projects involve the design, construction, or renovation of facilities and were analyzed as part of the Expanded Operations Alternative. The facility projects that NNSA has decided to pursue at this time are: </P>
                <P>• Planning, design, construction and operation of the Waste Management Facilities Transition projects to facilitate actions required by the Consent Order; </P>
                <P>• Repair and replacement of mission critical cooling system components for buildings in TA-55 to enable the continued operation of these buildings and to comply with current environmental standards; and </P>
                <P>• Final design of a new Radioactive Liquid Waste Treatment Facility, and design and construction of the Zero Liquid Discharge Facility component of this new treatment facility to enable LANL to continue to treat radioactive liquid wastes. </P>
                <P>These projects and actions are needed on an immediate basis to maintain existing capabilities, support existing programs, and provide a safe and environmentally protective work environment at LANL. The need for these increases in operations and new facility projects exists regardless of any decisions NNSA may make regarding the programmatic and project-specific alternatives analyzed in the Complex Transformation SPEIS. </P>
                <P>In addition, NNSA will continue to implement actions required by the Consent Order, as noted above, these decisions are not subject to NEPA. </P>
                <HD SOURCE="HD1">Basis for Decision </HD>
                <P>NNSA's decisions are based on its mission responsibilities and its need to sustain LANL's ability to operate in a manner that allows it to fulfill its existing responsibilities in an environmentally sound, timely and fiscally prudent manner. </P>
                <P>
                    National security policies require NNSA to maintain the nation's nuclear weapons stockpile as well as its core competencies in nuclear weapons. Since completion in 1996 of the 
                    <E T="03">Programmatic Environmental Impact Statement for Stockpile Stewardship and Management</E>
                     (SSM PEIS) and associated ROD, NNSA and its predecessor, DOE's Office of Defense Programs, has implemented these policies through the Stockpile Stewardship Program (SSP). The SSP emphasizes development and application of improved scientific and technical capabilities to assess the safety, security, and reliability of existing nuclear warheads without the use of nuclear testing. LANL's operations support a wide range of scientific and technological capabilities for NNSA's national security missions, including the SSP. Most of NNSA's missions require research and development capabilities that currently reside at the LANL site. The nuclear facilities in LANL's TA-55 must maintain the nation's nuclear stockpile. Programmatic risks would be unacceptable if LANL did not continue to operate, or if it failed to implement the new decisions set forth above. 
                </P>
                <P>NNSA believes that, at this time, existing national security requirements can be met by continuing to conduct operations at current levels with only a limited number of increases in levels of operations and new facility projects. These increases in operations and new projects are needed because of changes in the SSP program and NNSA's nuclear non-proliferation program. They are also needed to meet new responsibilities that have arisen as a result of changes in our national security requirements since 1999. One of the new facility projects is needed to facilitate NNSA's compliance with the Consent Order. The specific rationales for NNSA's decisions to implement seven elements of the Expanded Operations Alternative are: </P>
                <P>1. Supporting the Global Threat Reduction Initiative and Off-Site Sources Recovery Project by broadening the types and quantities of radioactive sealed sources (Co-60, Ir-192, Cf-252, Ra-226) that LANL can manage and store prior to their disposal—This decision will allow NNSA to retrieve and store more of these sources, which, if not adequately secured, could be used in a radiation dispersion device (a “dirty bomb”). </P>
                <P>2. Expanding the capabilities and operational level of the Nicholas C. Metropolis Center for Modeling and Simulation to support the Roadrunner Super Computer platform—This decision will allow NNSA to perform calculations that improve its ability to certify that the nuclear weapons stockpile is reliable without conducting underground nuclear tests. It will also allow LANL to conduct research on global energy challenges and other scientific issues. </P>
                <P>3. Performing research to improve detection and mitigation methods for beryllium—This research will support the continued development of methods to capture and sequester beryllium and to expedite sample analysis needed to implement exposure controls to ensure worker safety. </P>
                <P>4. Retrieval and disposition of legacy transuranic waste (approximately 3,100 cubic yards of contact-handled and 130 cubic yards of remote-handled) from belowground storage—Retrieving and dispositioning this waste will allow LANL to complete closure and remediation of TA-54 Material Disposal Area G under the Consent Order. This action will reduce risk by removing approximately 105,000 plutonium-239 equivalent curies from LANL. </P>
                <P>
                    5. Planning, design, construction and operation of the Waste Management Facilities Transition projects—These projects will replace LANL's existing facilities for solid waste management. The existing facilities at TA-54 for transuranic waste, low-level waste, mixed low-level waste and hazardous/
                    <PRTPAGE P="55840"/>
                    chemical waste are scheduled for closure and remediation under the Consent Order. 
                </P>
                <P>6. Repair and replacement of mission critical cooling system components for buildings in TA-55—This decision will allow these facilities to continue to operate and for NNSA to install a new cooling system that meets current standards regarding the phase-out of Class 1 ozone-depleting substances. </P>
                <P>7. Final design of a new Radioactive Liquid Waste Treatment Facility, and design and construction of the Zero Liquid Discharge Facility component of this new treatment facility—This decision will allow LANL to continue to treat radioactive liquid wastes by replacing a facility that does not meet current standards and that cannot be acceptably renovated. Regardless of any decisions NNSA may make about complex transformation and LANL's role in it, the laboratory will need to treat liquid radioactive wastes for the foreseeable future. </P>
                <HD SOURCE="HD1">Mitigation Measures </HD>
                <P>As described in the SWEIS, LANL operates under environmental laws, regulations, and policies within a framework of contractual requirements; many of these requirements mandate actions intended to control and mitigate potential adverse environmental effects. Examples include the Environment, Safety, and Health Manual, emergency plans, Integrated Safety Management System, pollution prevention and waste minimization programs, protected species programs, and energy and conservation programs. A Mitigation Action Plan for this ROD will be issued that includes: Specific habitat conservation measures recommended by the U.S. Fish and Wildlife Service for mitigating effects to potential habitat areas; site- and action-specific commitments related to the Consent Order once the State of New Mexico decides on specific environmental remediation for LANL MDAs; and traffic flow improvements that could involve such measures as installing turn lanes, installing and coordinating traffic lights, and installing new signage. A summary of all prior mitigation commitments for LANL that are either underway or that have yet to be initiated will be included in the MAP. These prior commitments include such actions as continued forest management efforts, continued trail management measures, and implementation of a variety of sampling and monitoring measures, as well as additional measures to reduce potable water use and conserve resources. </P>
                <P>In addition, with respect to the concerns raised by the Santa Clara Pueblo, NNSA will continue its efforts to support the Pueblo and other tribal entities in matters of human health, and will participate in various intergovernmental cooperative efforts to protect indigenous practices and locations of concern. NNSA will conduct government-to-government consultation with the Pueblo and other tribal entities to incorporate these matters into the MAP. </P>
                <SIG>
                    <DATED>Issued at Washington, DC, this 19th day of September 2008. </DATED>
                    <NAME>Thomas P. D'Agostino, </NAME>
                    <TITLE>Administrator, National Nuclear Security Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22678 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6450-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[FRL-8720-2] </DEPDOC>
                <SUBJECT>Draft NPDES General Permit for Offshore Seafood Processors in Alaska (Permit Number AKG524000) </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability of draft NPDES general permit and request for public comment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Director, Office of Water and Watersheds, EPA Region 10, is proposing to issue a general National Pollutant Discharge Elimination System (NPDES) permit for Offshore Seafood Processors in Alaska, pursuant to the provisions of the Clean Water Act, 33 U.S.C. 1251 
                        <E T="03">et seq.</E>
                         The draft general permit authorizes the discharge of treated seafood processing wastes from new and existing facilities to State and Federal Waters, at least 0.5 nautical miles from shore as delineated by mean lower low water. Interested persons may submit comments on the proposed general permit to EPA Region 10 at the address below. Comments must be received or postmarked by November 10, 2008. A fact sheet has been prepared which sets forth the principle factual, legal, policy, and scientific information considered in the development of the draft general permit. 
                    </P>
                    <P>The draft general permit contains a variety of technology-based and water quality-based effluent limitations, along with administrative and monitoring requirements, as well as other standard conditions, prohibitions, and management practices. Within state waters a 100 foot mixing zone is proposed for residues, dissolved gas, non-hydrocarbon oil and grease, fecal coliform, pH, temperature, color, turbidity, and total residual chlorine. In addition, the permit allows for the issuance of site specific zones of deposit (ZODs) by the Alaska Department of Environmental Conservation (ADEC). The site specific ZODs would only be authorized for facilities discharging between 0.5-1 nautical mile from shore upon application by the discharger. If a discharger requests a ZOD, ADEC would public notice the proposed ZOD authorization before the ZOD is authorized for the discharger. ZODs will be granted through an individual State certification that will be attached to EPA's authorization to discharge letter. </P>
                    <P>
                        <E T="03">Public Comment:</E>
                         Copies of the draft general permit, fact sheet, Biological Evaluation, Essential Fish Habitat Assessment, Environmental Assessment, Preliminary Finding of No Significant Impact (FONSI), and Ocean Discharge Criteria Evaluation are available upon request. Theses documents may also be downloaded from the Region 10 Web site at 
                        <E T="03">http://www.epa.gov/r10earth/waterpermits.htm</E>
                         (click on draft permits, then Alaska). Interested persons may submit written comments to the attention of Lindsay Guzzo at the address below. All comments must include the name, address, and telephone number of the commenter and a concise statement of comment and the relevant facts upon which it is based. Comments of either support or concern which are directed at specific, cited permit requirements are appreciated. 
                    </P>
                    <P>After the expiration date of the Public Notice on November 10, 2008, the Director, Office of Water and Watersheds, EPA Region 10, will make a final determination with respect to issuance of the general permit. The proposed requirements contained in the draft general permit will become final upon issuance if no significant comments are received during the public comment period. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received or postmarked by November 10, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments on the proposed general permit should be sent to Lindsay Guzzo, Office of Water and Watersheds; USEPA Region 10; 1200 6th Ave, Suite 900, OWW-130; Seattle, Washington 98101. Comments may also be received via electronic mail at 
                        <E T="03">guzzo.lindsay@epa.gov</E>
                        . 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Additional information can be obtained by contacting Lindsay Guzzo at the address above, or by visiting the Region 10 Web site at 
                        <E T="03">http://www.epa.gov/r10earth/waterpermits.htm</E>
                        . Requests may also be made to Audrey 
                        <PRTPAGE P="55841"/>
                        Washington at (206) 553-0523, or electronically mailed to: 
                        <E T="03">washington.audrey@epa.gov</E>
                        . For further information regarding the State's certification of the general permit, contact Shawn Stokes at the address below. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Public Informational Meetings </HD>
                <P>Two public informational meetings will be held to discuss the Proposed Permit, clarify changes and to answer general questions. Two meetings will be held, one in Anchorage on October 15, 2008, in the Westmark Hotel Anchorage, 720 West 5th Avenue, Anchorage, AK 99501, at 5:30 p.m., the other in Seattle on October 28, 2008 in the Red Lion Hotel, 1415 5th Avenue, Seattle, WA 98101 at 5 p.m. These informational meetings will not serve as a formal public hearing on the permit. </P>
                <HD SOURCE="HD1">Public Hearing </HD>
                <P>
                    Persons wishing to request a public hearing should submit their written request by November 10, 2008 stating the nature of the issues to be raised as well as the requester's name, address and telephone number to Lindsay Guzzo at the address above. If a public hearing is scheduled, notice will be published in the 
                    <E T="04">Federal Register</E>
                    . Notice will also be posted on the Region 10 Web site, and will be mailed to all interested persons receiving letters of the availability of the draft permit. 
                </P>
                <HD SOURCE="HD1">Administrative Record </HD>
                <P>The complete administrative record for the draft permit is available for public review at the EPA Region 10 headquarters at the address listed above. </P>
                <HD SOURCE="HD1">Other Legal Requirements </HD>
                <HD SOURCE="HD2">State Water Quality Standards and State Certification </HD>
                <P>EPA is also providing Public Notice of ADEC's intent to certify the general permit pursuant to section 401 of the Clean Water Act. ADEC has provided a draft certification that the draft general permit complies with State Water Quality Standards (18 AAC 15), including the State's antidegradation policy. </P>
                <P>
                    Persons wishing to comment on State certification of the draft general NPDES permit should send written comments to Mr. Shawn Stokes in ADEC's Anchorage Office, 555 Cordova Street, Anchorage, Alaska 99501, or via electronic mail at 
                    <E T="03">Shawn.Stokes@alaska.gov.</E>
                </P>
                <HD SOURCE="HD2">National Environmental Policy Act </HD>
                <P>Because the proposed permit will cover new sources in Alaska, the permit is subject to the National Environmental Policy Act (NEPA). Based on the Environmental Assessment (EA) and consideration of the proposed NPDES permit conditions, and in accordance with the guidelines for determining the significance of proposed federal actions (40 CFR 1508.27) and EPA criteria for initiating an Environmental Impact Statement (EIS) (40 CFR 6.605), EPA has concluded that the proposed NPDES permit will not result in significant effect on the human environment. The proposed permit will not significantly affect land use patterns or population, wetlands or flood plains, threatened or endangered species, farmlands, ecologically critical areas, historic resources, air quality, water quality, noise levels, and fish and wildlife resources. It will also not conflict with approved local, regional, or state land use plans or policies. The proposed permit also conforms with all applicable Federal statutes and executive orders. As a result of these findings, EPA has determined that an EIS will not be prepared and the public is invited to comment on EPA's Preliminary Finding Of No Significant Impacts (FONSI). </P>
                <HD SOURCE="HD2">Endangered Species Act </HD>
                <P>
                    Section 7 of the Endangered Species Act requires EPA to consult with the U.S. Fish and Wildlife Service and NOAA Fisheries regarding the potential effects that an action may have on listed endangered or threatened species or their critical habitat. To address these ESA requirements, and in support of EPA's informal consultation with the Services, a Biological Evaluation (BE) was prepared to analyze these potential effects. During the development of the draft general permit, information provided by the Services was used to identify species of interest for consideration in the BE. The results of the BE concluded that discharges from Offshore Seafood Processing facilities will either have 
                    <E T="03">no effect</E>
                     or are 
                    <E T="03">not likely to adversely affect</E>
                     threatened or endangered species in the vicinity of the discharges. The fact sheet, the draft permits and the BE are being reviewed by the Services for consistency with those programs established for the conservation of endangered and threatened species. Any additional comments or conservation recommendations received from the Services regarding threatened or endangered species will be considered prior to issuance of the GPs. 
                </P>
                <HD SOURCE="HD2">Magnuson-Stevens Fishery Conservation and Management Act </HD>
                <P>Section 305(b) of the Magnuson-Stevens Act (16 U.S.C. 1855(b)) requires federal agencies to consult with NOAA Fisheries when any activity proposed to be permitted, funded, or undertaken by a federal agency may have an adverse effect on designated Essential Fish Habitat (EFH) as defined by the Act. To address the requirements of the Magnuson-Stevens Act, EPA prepared an EFH Assessment concluding that offshore seafood processors operations may adversely affect essential fish habitat. However, EPA expects that effects on essential fish habitat, while possible, are likely to be limited in extent for several reasons. For more information please see the Biological Evaluation/ EFH assessment. As with ESA, any additional comments or conservation recommendations received from NOAA Fisheries regarding EFH will be considered prior to issuance of the GPs. </P>
                <HD SOURCE="HD2">Executive Order 12866 </HD>
                <P>EPA has determined that this general permit is not a “significant regulatory action” under the terms of Executive Order 12866 and is therefore not subject to OMB review. </P>
                <HD SOURCE="HD2">Paperwork Reduction Act </HD>
                <P>
                    The information collection requirements of this permit were previously approved by the Office of Management and Budget (OMB) under the provisions of the Paperwork Reduction Act, 44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     and assigned OMB control numbers 2040-0086 and 2040-0110. 
                </P>
                <HD SOURCE="HD2">Regulatory Flexibility Act </HD>
                <P>
                    The Regulatory Flexibility Act (RFA), 5 U.S.C. 601 
                    <E T="03">et seq.,</E>
                     requires that EPA prepare a regulatory flexibility analysis for rules subject to the requirements of 5 U.S.C. 553(b) that have a significant impact on a substantial number of small entities. However, general NPDES permits are not “rules” subject to the requirements of 5 U.S.C. 553(b), and is therefore not subject to the RFA. 
                </P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act </HD>
                <P>Section 201 of the Unfunded Mandates Reform Act (UMRA), Public Law 104-4, generally requires Federal agencies to assess the effects of their “regulatory actions” (defined to be the same as “rules” subject to the RFA) on tribal, State, and local governments and the private sector. However, general NPDES permits are not “rules” subject to the requirements of 5 U.S.C. 553(b), and is therefore not subject to the RFA. </P>
                <SIG>
                    <PRTPAGE P="55842"/>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>Michael F. Gearheard, </NAME>
                    <TITLE>Director, Office of Water and Watersheds, Region 10.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22553 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[ER-FRL-8586-1] </DEPDOC>
                <SUBJECT>Environmental Impact Statements and Regulations; Availability of EPA Comments </SUBJECT>
                <P>Availability of EPA comments prepared pursuant to the Environmental Review Process (ERP), under section 309 of the Clean Air Act and section 102(2)(c) of the National Environmental Policy Act as amended. Requests for copies of EPA comments can be directed to the Office of Federal Activities at 202-564-7146.  An explanation of the ratings assigned to draft environmental impact statements (EISs) was published in FR dated April 6, 2008 (73 FR 19833). </P>
                <HD SOURCE="HD1">Draft EISs </HD>
                <FP SOURCE="FP-1">EIS No. 20080240, ERP No. D-BLM-A09825-00, PROGRAMMATIC—Geothermal Leasing in the Western United States. </FP>
                <P>
                    <E T="03">Summary:</E>
                     EPA expressed environmental concerns about impacts to air quality, groundwater and noise. Rating EC2. 
                </P>
                <HD SOURCE="HD1">Final EISs </HD>
                <FP SOURCE="FP-1">EIS No. 20080275, ERP No. F-NOA-L39066-WA, ADOPTION—Fish Passage and Aquatic Habitat Restoration at Hemlock Dam, Implementation, Gifford Pinchot National Forest, Mount Adams District, Skamania County, WA. </FP>
                <P>
                    <E T="03">Summary:</E>
                     No comment letter sent to the federal agency. 
                </P>
                <FP SOURCE="FP-1">EIS No. 20080295, ERP No. F-FHW-C40171-NY, NYS Route 17 at Exit 122 Interchange Project, To Improve the Safety and Operation, Right-of-Way Acquisition, Town of Wallkill, Orange County, NY. </FP>
                <P>
                    <E T="03">Summary:</E>
                     EPA continues to have environmental concerns about wetland, water quality, and air quality impacts. 
                </P>
                <FP SOURCE="FP-1">EIS No. 20080300, ERP No. F-BLM-K65296-AZ, Agua Fria National Monument and Bradshaw-Harquahala, Proposed Resource Management Plan, Implementation, Yavapai County, AZ.</FP>
                <P>
                    <E T="03">Summary:</E>
                     EPA does not object to the proposed project. 
                </P>
                <FP SOURCE="FP-1">EIS No. 20080308, ERP No. F-SFW-L61233-WA, Hanford Reach National Monument Comprehensive Conservation Plan, Management of Monument Resources, Programs and Visitors for the Next 15 Years, Adams, Benton, Franklin and Grant Counties, WA. </FP>
                <P>
                    <E T="03">Summary:</E>
                     No formal comment letter was sent to the preparing agency. 
                </P>
                <SIG>
                    <DATED>Dated: September 23, 2008. </DATED>
                    <NAME>Robert W. Hargrove, </NAME>
                    <TITLE>Director, NEPA Compliance Division, Office of Federal Activities.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22681 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[ER-FRL-8585-9] </DEPDOC>
                <SUBJECT>Environmental Impacts Statements; Notice of Availability </SUBJECT>
                <P>
                    <E T="03">Responsible Agency:</E>
                     Office of Federal Activities, General Information (202) 564-1399 or 
                    <E T="03">http://www.epa.gov/compliance/nepa/.</E>
                </P>
                <FP SOURCE="FP-1">Weekly receipt of Environmental Impact Statements </FP>
                <FP SOURCE="FP-1">Filed 09/15/2008 Through 09/19/2008 </FP>
                <FP SOURCE="FP-1">Pursuant to 40 CFR 1506.9. </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080364, Draft Supplement, NPS, GA, Chattahoochee River National Recreation Area General Management Plan, Updated Information on Analyzing Six Alternative Future Directions for the Management and Use of Chattachoochee River National Recreation Area, Implementation, Chattahoochee River, Atlanta, GA, 
                    <E T="03">Comment Period Ends:</E>
                     11/10/2008, 
                    <E T="03">Contact:</E>
                     David Libman 404-562-3124 Ext. 685. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080365, Draft EIS, NPS, NY, Fort Stanwix National Monument General Management Plan, Implementation, Funding, City of Rome, Oneida County, NY, 
                    <E T="03">Comment Period Ends:</E>
                     11/25/2008, 
                    <E T="03">Contact:</E>
                     James O'Connell 617-223-5222. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080366, Final EIS, AFS, MT, Butte Resource Management Plan, Implementation, Beaverhead, Broadwater, Deerlodge, Gallatin, Jefferson, Lewis and Clark, Silver Bow and Park Counties, MT, 
                    <E T="03">Wait Period Ends:</E>
                     10/27/2008, 
                    <E T="03">Contact:</E>
                     Brenda Williams 202-452-5112. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080367, Final EIS, FHW, UT, Mountain View Corridor (MVC) Project, Proposed Transportation Improvement 2030 Travel Demand in Western Salt Lake County south of I-80 and west of Bangerter Highway and in northwestern Utah County of I-15, south of the Salt Lake County Line, and north of Utah Lake, Salt Lake and Utah County, UT, 
                    <E T="03">Wait Period Ends:</E>
                     10/27/2008, 
                    <E T="03">Contact:</E>
                     Edward Woolford 801-963-0182. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080368, Final EIS, AFS, MT, Debaugan Fuels Reduction Project, Proposed Fuels Reduction Activities, Lolo National Forest, Superior Ranger District, Mineral County, MT, 
                    <E T="03">Wait Period Ends:</E>
                     10/27/2008, 
                    <E T="03">Contact:</E>
                     Sharon Sweeney 406-822-4233. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080369, Draft EIS, FAA, FL, Palm Beach International Airport Project, Construction and Operation of Proposed Airfield Improvements, Funding, Palm Beach County, FL, 
                    <E T="03">Comment Period Ends:</E>
                     11/24/2008, 
                    <E T="03">Contact:</E>
                     Lindy McDowell 407-812-6331 Ext. 130. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080370, Draft EIS, AFS, CA, Gemmill Thin Project, Proposal to Reduce the Intensity and Size of Future Wildfires, and to Maintain/Improve Ecosystem Function and Wildlife Habitat, Chanchellula Late-Successional Reserve, Shasta-Trinity National Forest, Trinity County, CA, 
                    <E T="03">Comment Period Ends:</E>
                     11/10/2008, 
                    <E T="03">Contact:</E>
                     Bobbie A. Dimonte 530-226-2425. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080371, Final EIS, FAA, TX, ADOPTION—Northwest Corridor Light Rail Transit Line (LRT) to Irving/Dallas/Fort Worth International Airport, Construction, Dallas County, TX, 
                    <E T="03">Contact:</E>
                     Peggy Wade 817-222-5697. 
                </FP>
                <P>The U.S. Department of Transportation's Federal Aviation Administration (DOT/FAA) has ADOPTED the U.S. Department of Transportation's Federal Transit Administration FEIS #2080289, filed on 07/24/2008. DOT/FAA was a Cooperating Agency for the above project. Recirculation of the FEIS is not necessary under 40 CFR 1506.3(c). </P>
                <FP SOURCE="FP-1">
                    EIS No. 20080372, Draft EIS, AFS, ID, Salmon-Challis National Forest (SCNF), Proposes Travel Planning and OHV Route Designation, Lemhi, Custer and Butte Counties, ID, 
                    <E T="03">Comment Period Ends:</E>
                     11/25/2008, 
                    <E T="03">Contact:</E>
                     Karen Gallogly 208-756-5103. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080373, Final EIS, FHW, NC, NC 12 Replacement of Herbert C. Bonner Bridge (Bridge No. 11) Revisions and Additions, over Oregon Inlet Construction, Funding, U.S. Coast Guard Permit, Special-Use-Permit, Right-of-Way Permit, U.S. Army COE Section 10 and 404 Permit, Dare County, NC, 
                    <E T="03">Wait Period Ends:</E>
                     10/27/2008, 
                    <E T="03">Contact:</E>
                     John F. Sullivan III P.E. 919-747-7000. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080374, Draft EIS, FAA, PA, Philadelphia International Airport (PHL) Capacity Enhancement Program 
                    <PRTPAGE P="55843"/>
                    (CEP) To Accommodate Current and Future Aviation Demand, Funding and U.S. Army COE Section 404 Permit, Philadelphia, PA, 
                    <E T="03">Comment Period Ends:</E>
                     11/10/2008, 
                    <E T="03">Contact:</E>
                     Susan McDonald 717-730-2841. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080375, Draft EIS, NOA, 00, Amendment 3 to the Northeast Skate Complex Fishery Management Plan, Implementation of New Management Measures to Rebuild Overfished Skate Stocks, End Overfishing of Skate Fisheries, Gulf of Maine (GOM), Georges Bank (GB), South New England and Mid-Atlantic Regions, 
                    <E T="03">Comment Period Ends:</E>
                     11/10/2008, 
                    <E T="03">Contact:</E>
                     Tobey Curtis 978-281-9288. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080376, Final EIS, NOA, CA, Cordell Bank, Gulf of the Farallones and Monterey Bay National Marine Sanctuaries, Proposes a Series of Regulatory Changes, Offshore of Northern/Central CA, 
                    <E T="03">Wait Period Ends:</E>
                     10/27/2008, 
                    <E T="03">Contact:</E>
                     John Armor 301-713-3125. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080377, Final EIS, AFS, MT, Sheppard Creek Post-Fire Project, Timber Salvage, Implementation, Flathead National Forest, Flathead and Lincoln Counties, MT, 
                    <E T="03">Wait Period Ends:</E>
                     10/27/2008, 
                    <E T="03">Contact:</E>
                     Bryan Donner 406-758-3508. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080378, Final EIS, COE, MD, Mid-Chesapeake Bay Island Ecosystem Restoration Integrated Feasibility Study, Using Uncontaminated Dredged Material from the Upper Chesapeake Bay Approach Channel to the Port of Baltimore to Restore and Protect Island Habitat in the Middle Portion of Chesapeake Bay, Dorchester County, MD, 
                    <E T="03">Wait Period Ends:</E>
                     10/27/2008, 
                    <E T="03">Contact:</E>
                     Dr. Angie Sowers 410-962-7440. 
                </FP>
                <FP SOURCE="FP-1">
                    EIS No. 20080379, Final EIS, AFS, NM, Santa Fe National Forest Plan Amendment for Oil &amp; Gas Leasing and Roads Management, Implementation, San Juan Basin, Cuba Ranger District, NM, 
                    <E T="03">Wait Period Ends:</E>
                     10/27/2008, 
                    <E T="03">Contact:</E>
                     Allen Fowler 505-438-7821. 
                </FP>
                <FP SOURCE="FP-1">EIS No. 20080380, Final EIS, AFS, CA. </FP>
                <HD SOURCE="HD1">Amended Notices </HD>
                <FP SOURCE="FP-1">
                    EIS No. 20080353, Draft Supplement, AFS, 00, 
                    <E T="03">Gypsy Moth Management in the United States:</E>
                     A Cooperative Approach, Proposing New Treatments that were not Available when the 1995 EIS was written, U.S., 
                    <E T="03">Comment Period Ends:</E>
                     11/17/2008, 
                    <E T="03">Contact:</E>
                     William Oldland 304-285-1585. 
                </FP>
                <P>Revision to FR Notice Published 09/19/2008: Extending Comment Period from 11/03/2008 to 11/17/2008. </P>
                <SIG>
                    <DATED>Dated: September 23, 2008. </DATED>
                    <NAME>Robert W. Hargrove, </NAME>
                    <TITLE>Director, NEPA Compliance Division, Office of Federal Activities.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22682 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL TRADE COMMISSION </AGENCY>
                <SUBJECT>Granting of Request for Early Termination of the Waiting Period Under the Premerger Notification Rules </SUBJECT>
                <P>
                    Section 7A of the Clayton Act, 15 U.S.C. 18a, as added by Title II of the Hart-Scott Rodino Antitrust Improvements Act of 1976, requires persons contemplating certain mergers or acquisitions to give the Federal Trade Commission and the Assistant Attorney General advance notice and to wait designated periods before consummation of such plans. Section 7A(b)(2) of the Act permits the agencies, in individual cases, to terminate this waiting period prior to its expiration and requires that notice of this action be published in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <P>The following transactions were granted early termination of the waiting period provided by law and the premerger notification rules. The grants were made by the Federal Trade Commission and the Assistant Attorney General for the Antitrust Division of the Department of Justice. Neither agency intends to take any action with respect to these proposed acquisitions during the applicable waiting period. </P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="xs60,r75,r75,r75">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Trans No. </CHED>
                        <CHED H="1">Acquiring </CHED>
                        <CHED H="1">Acquired </CHED>
                        <CHED H="1">Entities </CHED>
                    </BOXHD>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Transactions Granted Early Termination—07/21/2008</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20081459 </ENT>
                        <ENT>Prism Holding Corporation</ENT>
                        <ENT>Passport Holding Corporation</ENT>
                        <ENT>Passport Holding Corporation. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081464 </ENT>
                        <ENT>Quicksilver Resources Inc </ENT>
                        <ENT>The Perot Investment Trust I </ENT>
                        <ENT>
                            Hillwood Oil Gas, L.P 
                            <LI>Nortex Minerals, L.P. </LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081469 </ENT>
                        <ENT>Duke Energy Corporation </ENT>
                        <ENT>Diamond Castle Partners IV, L.P </ENT>
                        <ENT>Catamount Energy Corporation. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081487 </ENT>
                        <ENT>Allied World Assurance Company Holdings Ltd </ENT>
                        <ENT>Alleghany Corporation </ENT>
                        <ENT>Darwin Professional Underwriters, Inc. </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20081490 </ENT>
                        <ENT>Health Care Service Corporation </ENT>
                        <ENT>MEDecision, Inc </ENT>
                        <ENT>MEDecision, Inc. </ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Transactions Granted Early Termination—07/22/2008</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20081403 </ENT>
                        <ENT>NTR plc </ENT>
                        <ENT>Green Plains Renewable Energy, Inc </ENT>
                        <ENT>Green Plains Renewable Energy, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081430 </ENT>
                        <ENT>Flowers Foods, Inc </ENT>
                        <ENT>Lloyd Edward Eisele, Jr </ENT>
                        <ENT>Holsum Bakery, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081433 </ENT>
                        <ENT>Sageview Capital Master, L.P </ENT>
                        <ENT>Invitrogen Corporation </ENT>
                        <ENT>Invitrogen Corporation. </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20081434 </ENT>
                        <ENT>Flowers Foods, Inc </ENT>
                        <ENT>C&amp;G Holdings, Inc </ENT>
                        <ENT>C&amp;G Holdings, Inc. </ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Transactions Granted Early Termination—07/24/2008</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="s">
                        <ENT I="01">20081470 </ENT>
                        <ENT>LTX Corporation </ENT>
                        <ENT>Credence Systems Corp </ENT>
                        <ENT>Credence Systems Corp. </ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Transactions Granted Early Termination—07/28/2008</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20081437 </ENT>
                        <ENT>Parexel International Corporation </ENT>
                        <ENT>ClinPhone plc </ENT>
                        <ENT>ClinPhone plc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081438 </ENT>
                        <ENT>Newco </ENT>
                        <ENT>David H. Domsife </ENT>
                        <ENT>Gillig Corporation Herrick-Pacific Corporation. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081439 </ENT>
                        <ENT>Newco </ENT>
                        <ENT>Dorothy H. Jernstedt </ENT>
                        <ENT>Gillig Corporation Herrick-Pacific Corporation. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081443 </ENT>
                        <ENT>AT&amp;T Inc </ENT>
                        <ENT>Dennis L. O'Neill </ENT>
                        <ENT>MilkyWay Broadband, LLC. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081457 </ENT>
                        <ENT>GTCR Fund VII, L.P </ENT>
                        <ENT>GTC Biotherapeutics, Inc </ENT>
                        <ENT>GTC Biotherapeutics, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081488 </ENT>
                        <ENT>EGI-Fund (08-10) Investors, L.L.C </ENT>
                        <ENT>MiddleBrook Pharmaceuticals, Inc</ENT>
                        <ENT>MiddleBrook Pharmaceuticals, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081495 </ENT>
                        <ENT>Audax Private Equity Fund III, L.P</ENT>
                        <ENT>Hamid Mirafzali and Shadan Mirafzali </ENT>
                        <ENT>MiraMed Global Services, Inc. </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <PRTPAGE P="55844"/>
                        <ENT I="01">20081504 </ENT>
                        <ENT>K.K. BCJ-1 </ENT>
                        <ENT>D&amp;M Holdings Inc </ENT>
                        <ENT>D&amp;M Holdings Inc </ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Transactions Granted Early Termination—07/29/2008</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20081476 </ENT>
                        <ENT>Sageview Capital Master, L.P </ENT>
                        <ENT>Advanced Medical Optics, Inc </ENT>
                        <ENT>Advanced Medical Optics, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081502 </ENT>
                        <ENT>Wyeth </ENT>
                        <ENT>The Procter &amp; Gamble Company </ENT>
                        <ENT>The Procter &amp; Gamble Company. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081503 </ENT>
                        <ENT>Progress Software Corporation </ENT>
                        <ENT>IONA Technologies PLC </ENT>
                        <ENT>IONA Technologies PLC. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081508 </ENT>
                        <ENT>Wind Point </ENT>
                        <ENT>Glenn W. Hasse Partners VI, L.P </ENT>
                        <ENT>International Assembly LLC, Ryt-way Industries, LLC, T&amp;G Transport LLC. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081510 </ENT>
                        <ENT>Edward L. Maletis </ENT>
                        <ENT>CoHo Distributing LLC </ENT>
                        <ENT>CoHo Distributing LLC. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081513 </ENT>
                        <ENT>HKW Capital Partners III, L.P </ENT>
                        <ENT>David R. Porter &amp; Angela L. Porter </ENT>
                        <ENT>FURGOPet, Inc., FURminator, Inc., Shed Shack, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081516 </ENT>
                        <ENT>Exterran Holdings, Inc</ENT>
                        <ENT>Joe Scott </ENT>
                        <ENT>EMIT Water Discharge Technology, LLC. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081523 </ENT>
                        <ENT>OHS Inc </ENT>
                        <ENT>Cenex Finance Association, Inc </ENT>
                        <ENT>Cofina Financial, LLC. </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20081531 </ENT>
                        <ENT>United Drug plc </ENT>
                        <ENT>Superior Group, Inc </ENT>
                        <ENT>Sharp Corporation. </ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Transactions Granted Early Termination—07/30/2008</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="s">
                        <ENT I="01">20081299 </ENT>
                        <ENT>Honeywell International Inc </ENT>
                        <ENT>Intelligent Automation Corporation </ENT>
                        <ENT>Intelligent Automation Corporation. </ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Transactions Granted Early Termination—08/01/2008</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20081478 </ENT>
                        <ENT>TowerBrook Investors II, L.P </ENT>
                        <ENT>Broadlane, Inc </ENT>
                        <ENT>Broadlane, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081497 </ENT>
                        <ENT>Harding Energy Partners, LLC </ENT>
                        <ENT>Exxon Mobil Corporation </ENT>
                        <ENT>DDJET Limited LLP. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081501 </ENT>
                        <ENT>Applied Industrial Technologies, Inc </ENT>
                        <ENT>Henry L. Hillman </ENT>
                        <ENT>Bay Advanced Technologes, LLC, Carolina Fluid Components, LLC, DTS Fluid Power, LLC, Fluid Power Resource, LLC, FluidTech, LLC, H.E.B., LLC, Hughes-HiTech, LLC, Hydro Air, LLC, Mach V, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081507 </ENT>
                        <ENT>Hicks Acquisition Company I, Inc </ENT>
                        <ENT>Blackstone Capital Partners III Merchant Banking Fund L.P </ENT>
                        <ENT>GPO Capital Corp. II. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081509 </ENT>
                        <ENT>J. Luther King, Jr </ENT>
                        <ENT>Industrial Distribution Group, Inc </ENT>
                        <ENT>Industrial Distribution Group, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081519 </ENT>
                        <ENT>P. Morgan McCague </ENT>
                        <ENT>BCE Inc </ENT>
                        <ENT>BCE Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081521 </ENT>
                        <ENT>BBN Holdings, Inc </ENT>
                        <ENT>Landmark Communications, Inc </ENT>
                        <ENT>Landmark Communications, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081526 </ENT>
                        <ENT>Puget Holdings LLC </ENT>
                        <ENT>Puget Energy, Inc </ENT>
                        <ENT>Puget Energy, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081528 </ENT>
                        <ENT>Snow Phipps Group, L.P </ENT>
                        <ENT>ACC Holdco, Inc </ENT>
                        <ENT>ACC Holdco, Inc. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081545 </ENT>
                        <ENT>Odyssey Investment Partners Fund III, L.P </ENT>
                        <ENT>EAG Limited </ENT>
                        <ENT>EAG Limited. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20081555 </ENT>
                        <ENT>Diamond Castle Partners IV, L.P </ENT>
                        <ENT>Landmark Communications, Inc </ENT>
                        <ENT>NewsChannel 5 Network, LLC. </ENT>
                    </ROW>
                </GPOTABLE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sandra M. Peay, Contact Representative, or Renee Hallman, Contact Representative,  Federal Trade Commission,  Premerger Notification Office,  Bureau of Competition,  Room H-303,  Washington, DC 20580, (202) 326-3100. </P>
                    <SIG>
                        <P>By Direction of the Commission. </P>
                        <NAME>Donald S. Clark, </NAME>
                        <TITLE>Secretary. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22567 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6750-01-M </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">GENERAL SERVICES ADMINISTRATION</AGENCY>
                <SUBJECT>Federal Management Regulation (FMR); Motor Vehicle Management; Notice of GSA Bulletin FMR B-22</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Governmentwide Policy, General Services Administration (GSA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a bulletin.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice announces Federal Management Regulation (FMR) Bulletin B-22. Bulletin B-22 provides a deviation from the FMR to allow executive agencies to purchase premium fuel for Government owned and leased vehicles when lower grade fuels are not available due to possible nationwide market shortages due to refinery damage caused by Hurricane Ike. GSA Bulletin FMR B-22 may be found at 
                        <E T="03">www.gsa.gov/bulletin</E>
                        .
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The bulletin announced in this notice became effective on September 13, 2008.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For clarification of content, contact General Services Administration, Office of Governmentwide Policy, Office of Travel, Transportation and Asset Management, at (202) 501-1777. Please cite Bulletin FMR B-22.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">A. Background</HD>
                <P>The Federal Management Regulation (FMR), Subpart B, section 102-34.335 (41 CFR 102-34.335), requires drivers to use the grade (octane rating) of fuel recommended by the motor vehicle manufacturer when fueling motor vehicles owned or leased by the Government. Present restrictions prohibit the use of premium grade fuel in motor vehicles owned or leased by the Government that will operate on a lower grade of fuel.</P>
                <P>
                    As a result of Hurricane Ike, executive agencies may encounter nationwide fuel shortages and may not be able to acquire lower grade fuel for their vehicles to complete their missions. The original intent of FMR section 102-34.335 was to reduce fuel costs and the unnecessary use of premium fuel in vehicles capable of being operated on lower grade fuel. FMR Bulletin, B-22, provides a deviation for executive agencies to purchase premium fuel for Government owned and leased vehicles when lower grade fuels are not available due to market shortages due to Hurricane Ike.
                    <PRTPAGE P="55845"/>
                </P>
                <HD SOURCE="HD1">B. Procedures</HD>
                <P>
                    Bulletins regarding motor vehicle management are located on the Internet at 
                    <E T="03">www.gsa.gov/bulletin</E>
                     as Federal Management Regulation bulletins.
                </P>
                <SIG>
                    <DATED>Dated: September 16, 2008.</DATED>
                    <NAME>Becky Rhodes,</NAME>
                    <TITLE>Deputy Associate Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22643 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6820-14-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention </SUBAGY>
                <DEPDOC>[30Day-08-0006] </DEPDOC>
                <SUBJECT>Agency Forms Undergoing Paperwork Reduction Act Review </SUBJECT>
                <P>
                    The Centers for Disease Control and Prevention (CDC) publishes a list of information collection requests under review by the Office of Management and Budget (OMB) in compliance with the Paperwork Reduction Act (44 U.S.C. Chapter 35). To request a copy of these requests, call the CDC Reports Clearance Officer at (404) 639-5960 or send an e-mail to 
                    <E T="03">omb@cdc.gov.</E>
                     Send written comments to CDC Desk Officer, Office of Management and Budget, Washington, DC or by fax to (202) 395-6974. Written comments should be received within 30 days of this notice. 
                </P>
                <HD SOURCE="HD1">Proposed Project </HD>
                <P>Statements in Support of Application for Waiver of Inadmissibility Under the Immigration and Nationality Act (OMB Control No. 0920-0006)—Extension—National Center for Preparedness, Control and Detection of Infectious Diseases (NCPDCID), Centers for Disease Control and Prevention (CDC). </P>
                <HD SOURCE="HD2">Background and Brief Description </HD>
                <P>Section 212(a)(1) of the Immigration and Nationality Act states that aliens with specific health related conditions are ineligible for admission into the United States. The Attorney General may waive application of this inadmissibility on health-related grounds if an application for waiver is filed and approved by the consular office considering the application for visa. CDC uses this application primarily to collect information to establish and maintain records of waiver applicants in order to notify the U.S. Citizenship and Immigration Services when terms, conditions and controls imposed by waiver are not met. CDC is requesting approval from OMB to collect this data for another 3 years. CDC estimates that mailing costs per respondent will be $80.00 per year. The annualized burden for this data collection is 167 hours. </P>
                <GPOTABLE COLS="04" OPTS="L2,i1" CDEF="s50,14,14,14">
                    <TTITLE>Estimate of Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Form</CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average burden
                            <LI>per response</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Form CDC 4.422-1</ENT>
                        <ENT>200</ENT>
                        <ENT>1</ENT>
                        <ENT>10/60</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Form CDC 4.422-1a</ENT>
                        <ENT>200</ENT>
                        <ENT>1</ENT>
                        <ENT>20/60</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Form CDC 4.422-1b</ENT>
                        <ENT>200</ENT>
                        <ENT>1</ENT>
                        <ENT>20/60</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: September 22, 2008. </DATED>
                    <NAME>Marilyn S. Radke, </NAME>
                    <TITLE>Reports Clearance Officer, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22698 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4163-18-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <DEPDOC>[Document Identifier: CMS-484 and CMS-846-849, 854, 10125, 10126, 10269 and CMS-R-21] </DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services. </P>
                </AGY>
                <P>In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Centers for Medicare &amp; Medicaid Services (CMS), Department of Health and Human Services, is publishing the following summary of proposed collections for public comment. Interested persons are invited to send comments regarding this burden estimate or any other aspect of this collection of information, including any of the following subjects: (1) The necessity and utility of the proposed information collection for the proper performance of the Agency's function; (2) the accuracy of the estimated burden; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) the use of automated collection techniques or other forms of information technology to minimize the information collection burden. </P>
                <P>
                    1. 
                    <E T="03">Type of Information Collection Request:</E>
                     Revision of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Durable Medical Equipment Regional Carrier, Certificate of Medical Necessity for Oxygen and Supporting Regulations in 42 CFR 410.38 and 424.5; 
                    <E T="03">Use:</E>
                     The oxygen certificate of medical necessity (CMN) collects information required to help determine the medical necessity of home oxygen therapy for Medicare beneficiaries. CMS requires CMNs where items may present a vulnerability to the Medicare program. Each claim for these items must have an associated CMN for the beneficiary. In order to determine if a beneficiary needs home oxygen therapy, a qualifying blood gas study must be performed and it must comply with the DMERCs Oxygen Medical Policy on the standards for conducting the test and also be covered under Medicare Part B. A beneficiary must be seen and evaluated by the treating physician within specific timeframes as indicated by the Oxygen Medical Policy in order to complete an Initial CMN Certification, a Recertification CMN and a Revised CMN Certification. 
                    <E T="03">Form Number:</E>
                     CMS-484 (OMB# 0938-0534); 
                    <E T="03">Frequency:</E>
                     Occasionally; 
                    <E T="03">Affected Public:</E>
                     Business or other for-profits; 
                    <E T="03">Number of Respondents:</E>
                     15,000; 
                    <E T="03">Total Annual Responses:</E>
                     1,630,000; 
                    <E T="03">Total Annual Hours:</E>
                     326,000. 
                </P>
                <P>
                    2. 
                    <E T="03">Type of Information Collection Request:</E>
                     Revision of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Durable Medical Equipment Medicare Administrative Contractors (MAC), Certificates of Medical Necessity; 
                    <E T="03">Use:</E>
                     The certificate of medical necessity (CMN) collects information required to help determine the medical necessity of certain items. CMS requires CMNs where there may be a vulnerability to the Medicare program. Each initial claim for these items must 
                    <PRTPAGE P="55846"/>
                    have an associated CMN for the beneficiary. Suppliers (those who bill for the items) complete the administrative information (
                    <E T="03">e.g.</E>
                    , patient's name and address, items ordered, etc.) on each CMN. The 1994 Amendments to the Social Security Act require that the supplier also provide a narrative description of the items ordered and all related accessories, their charge for each of these items, and the Medicare fee schedule allowance (where applicable). The supplier then sends the CMN to the treating physician or other clinicians (
                    <E T="03">e.g.</E>
                    , physician assistant, LPN, etc.) who completes questions pertaining to the beneficiary's medical condition and signs the CMN. The physician or other clinician returns the CMN to the supplier who has the option to maintain a copy and then submits the CMN (paper or electronic) to CMS, along with a claim for reimbursement. 
                    <E T="03">Form Number:</E>
                     CMS-846-849, 854, 10125, 10126, 10269 (OMB# 0938-0679); 
                    <E T="03">Frequency:</E>
                     Occasionally; 
                    <E T="03">Affected Public:</E>
                     Business or other for-profit and Not-for-profit institutions; 
                    <E T="03">Number of Respondents:</E>
                     59,200; 
                    <E T="03">Total Annual Responses:</E>
                     6,480,000; 
                    <E T="03">Total Annual Hours:</E>
                     1,296,000. 
                </P>
                <P>
                    3. 
                    <E T="03">Type of Information Collection Request:</E>
                     Extension without change of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Withholding Medicare Payments to Recover Medicaid Overpayments and Supporting Regulations in 42 CFR 44.31; 
                    <E T="03">Use:</E>
                     Overpayments may occur in either the Medicare and Medicaid program, at times resulting in a situation where an institution or person that provides services owes a repayment to one program while still receiving reimbursement from the other. Certain Medicaid providers which are subject to offsets for the collection of Medicaid overpayments may terminate or substantially reduce their participation in Medicaid, leaving the State Medicaid Agency unable to recover the amounts due. These information collection requirements give CMS the authority to recover Medicaid overpayments by offsetting payments due to a provider under the program. 
                    <E T="03">Form Number:</E>
                     CMS-R-21 (OMB# 0938-0287); 
                    <E T="03">Frequency:</E>
                     On occasion; 
                    <E T="03">Affected Public:</E>
                     State, Local or Tribal Governments; 
                    <E T="03">Number of Respondents:</E>
                     54; 
                    <E T="03">Total Annual Responses:</E>
                     27; 
                    <E T="03">Total Annual Hours:</E>
                     81. 
                </P>
                <P>
                    To obtain copies of the supporting statement and any related forms for the proposed paperwork collections referenced above, access CMS Web Site address at 
                    <E T="03">http://www.cms.hhs.gov/PaperworkReductionActof1995</E>
                    , or E-mail your request, including your address, phone number, OMB number, and CMS document identifier, to 
                    <E T="03">Paperwork@cms.hhs.gov</E>
                    , or call the Reports Clearance Office on (410) 786-1326. 
                </P>
                <P>To be assured consideration, comments and recommendations for the proposed information collections must be received by the OMB desk officer at the address below, no later than 5 p.m. on October 27, 2008: OMB, Office of Information and Regulatory Affairs, Attention: CMS Desk Officer, New Executive Office Building, Room 10235, Washington, DC 20503, Fax Number: (202) 395-6974. </P>
                <SIG>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>Michelle Shortt, </NAME>
                    <TITLE>Director, Regulations Development Group, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22582 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <DEPDOC>[Document Identifier: CMS-372 and CMS-R-54] </DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services. </P>
                </AGY>
                <P>In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Centers for Medicare &amp; Medicaid Services (CMS) is publishing the following summary of proposed collections for public comment. Interested persons are invited to send comments regarding this burden estimate or any other aspect of this collection of information, including any of the following subjects: (1) The necessity and utility of the proposed information collection for the proper performance of the agency's functions; (2) the accuracy of the estimated burden; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) the use of automated collection techniques or other forms of information technology to minimize the information collection burden. </P>
                <P>
                    1. 
                    <E T="03">Type of Information Collection Request:</E>
                     Revision of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Annual Report on Home and Community Based Services Waivers and Supporting Regulations in 42 CFR 440.180 and 441.300-310.; 
                    <E T="03">Use:</E>
                     States within an approved waiver under section 1915(c) of the act are required to submit a report annually in order for CMS to: (1) Verify that State assurances regarding waiver cost-neutrality are met; and (2) Determine the waiver's impact on the type, amount, and cost of services provided under the State Plan and health welfare of recipients. 
                    <E T="03">Form Number:</E>
                     CMS-372 (OMB# 0938-0272); 
                    <E T="03">Frequency:</E>
                     Yearly; 
                    <E T="03">Affected Public:</E>
                     State, Local, or Tribal Governments; 
                    <E T="03">Number of Respondents:</E>
                     49; 
                    <E T="03">Total Annual Responses:</E>
                     305; 
                    <E T="03">Total Annual Hours:</E>
                     13,115. 
                </P>
                <P>
                    2. 
                    <E T="03">Type of Information Collection Request:</E>
                     Revision of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     National Medicare &amp; You Education Program (NMEP) Survey of Medicare Beneficiaries 
                    <E T="03">Use:</E>
                     The Centers for Medicare and Medicaid Services is requesting a revision of this information collection request to continue to collect information from Medicare beneficiaries, caregivers, health care providers, and health information providers. It is critical for this agency to obtain feedback from the aforementioned groups so that the agency can accurately assess the needs of the Medicare audience. Using random digit dial and/or an administrative sample, members of the Medicare audience will be called and asked to complete the survey via telephone. The results of this survey will be compiled and studied so that communication may be amended to benefit Medicare's audience. The survey has the following objectives: To assess satisfaction with and knowledge of the Medicare program; to gather information on health behaviors and quality of health care; to determine the most used source for Medicare information; and to gather information from health care provider and health information providers. 
                    <E T="03">Form Number:</E>
                     CMS-R-54 (OMB# 0938-0738); 
                    <E T="03">Frequency:</E>
                     Once; 
                    <E T="03">Affected Public:</E>
                     Individuals and Households, Private Sector—Business or other for-profits; 
                    <E T="03">Number of Respondents:</E>
                     7,000; 
                    <E T="03">Total Annual Responses:</E>
                     7,000; 
                    <E T="03">Total Annual Hours:</E>
                     1,750. 
                </P>
                <P>
                    To obtain copies of the supporting statement and any related forms for the proposed paperwork collections referenced above, access CMS' Web site at 
                    <E T="03">http://www.cms.hhs.gov/PaperworkReductionActof1995</E>
                    , or E-mail your request, including your address, phone number, OMB number, and CMS document identifier, to 
                    <E T="03">Paperwork@cms.hhs.gov</E>
                    , or call the 
                    <PRTPAGE P="55847"/>
                    Reports Clearance Office on (410) 786-1326. 
                </P>
                <P>In commenting on the proposed information collections please reference the document identifier or OMB control number. To be assured consideration, comments and recommendations must be submitted in one of the following ways November 25, 2008: </P>
                <P>
                    1. 
                    <E T="03">Electronically.</E>
                     You may submit your comments electronically to 
                    <E T="03">http://www.regulations.gov.</E>
                     Follow the instructions for “Comment or Submission” or “More Search Options” to find the information collection document(s) accepting comments. 
                </P>
                <P>
                    2. 
                    <E T="03">By regular mail.</E>
                     You may mail written comments to the following address: CMS, Office of Strategic Operations and Regulatory Affairs, Division of Regulations Development, Attention: Document Identifier/OMB Control Number _____, Room C4-26-05, 7500 Security Boulevard, Baltimore, Maryland 21244-1850. 
                </P>
                <SIG>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>Michelle Shortt, </NAME>
                    <TITLE>Director, Regulations Development Group, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22584 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <DEPDOC>[CMS-4136-N] </DEPDOC>
                <SUBJECT>Medicare Program; Medicare Appeals; Adjustment to the Amount in Controversy Threshold Amounts for Calendar Year 2009 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces the annual adjustment in the amount in controversy (AIC) threshold amounts for Administrative Law Judge (ALJ) hearings and judicial review under the Medicare appeals process. The adjustment to the AIC threshold amounts will be effective for requests for ALJ hearings and judicial review filed on or after  January 1, 2009. The 2009 AIC threshold amounts are $120 for ALJ hearings and $1,220 for judicial review. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         This notice is effective on January 1, 2009. 
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Liz Hosna, (410) 786-4993. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background </HD>
                <P>Section 1869(b)(1)(E) of the Social Security Act (the Act), as amended by section 521 of the Medicare, Medicaid, and SCHIP Benefits Improvement and Protection Act of 2000 (BIPA), established the AIC threshold amounts for ALJ hearing requests and judicial review at $100 and $1000, respectively, for Medicare Part A and Part B appeals. Section 940 of the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 (MMA), amended section 1869(b)(1)(E) of the Act to require the AIC threshold amounts for ALJ hearings and judicial review to be adjusted annually. The AIC threshold amounts are to be adjusted, as of January 2005, by the percentage increase in the medical care component of the consumer price index for all urban consumers (U.S. city average) for July 2003 to July of the year preceding the year involved and rounded to the nearest multiple of $10. Section 940(b)(2) of the MMA provided conforming amendments to apply the AIC adjustment requirement to Medicare Part C (Medicare Advantage “MA”) appeals and certain health maintenance organization and competitive health plan appeals. Health care prepayment plans are also subject to MA appeals rules, including the AIC adjustment requirement. Section 101 of the MMA provides for the application of the AIC adjustment requirement to Medicare Part D appeals. </P>
                <HD SOURCE="HD2">A. Medicare Part A and Part B Appeals </HD>
                <P>
                    The statutory formula for the annual adjustment to the AIC threshold amounts for ALJ hearings and judicial review of Medicare Part A and Part B appeals, set forth at section 1869(b)(1)(E) of the Act, is included in the applicable implementing regulations, 42 CFR Part 405, Subpart I, at § 405.1006(b). The regulations require the Secretary of the Department of Health and Human Services (the Secretary) to publish changes to the AIC threshold amounts in the 
                    <E T="04">Federal Register</E>
                     (§ 405.1006(b)(2)). In order to be entitled to a hearing before an ALJ, a party to a proceeding must meet the AIC requirements at § 405.1006(b). Similarly, a party must meet the AIC requirement at § 405.1006(c) at the time judicial review is requested for the court to have jurisdiction over the appeal (§ 405.1136(a)). 
                </P>
                <HD SOURCE="HD2">B. Medicare Part C (Medicare Advantage) Appeals </HD>
                <P>Section 940(b)(2) of the MMA applies the AIC adjustment requirement to Part C (MA) appeals by amending section 1852(g)(5) of the Act. The implementing regulations for Medicare Part C appeals are found at 42 CFR Part 422, Subpart M. Specifically, § 422.600 and § 422.612 discuss the AIC threshold amounts for ALJ hearings and judicial review.</P>
                <P>Section 422.600 grants any party to the reconsideration, except the MA organization, a right to an ALJ hearing as long as the amount remaining in controversy after reconsideration meets the threshold requirement established annually by the Secretary. Section 422.612 states that any party, including the MA organization, may request judicial review if the amount in controversy meets the threshold requirement established annually by the Secretary. </P>
                <HD SOURCE="HD2">C. Health Maintenance Organizations, Competitive Medical Plans, and Health Care Prepayment Plans </HD>
                <P>Section 1876(c)(5)(B) of the Act states that the annual adjustment to the AIC dollar amounts set forth in section 1869(b)(1)(E) of the Act applies to certain beneficiary appeals within the context of health maintenance organizations and competitive medical plans. The applicable implementing regulations for Medicare Part C appeals are set forth in 42 CFR Part 422, Subpart M, and as discussed above, apply to these appeals. The Medicare Part C appeals rules also apply to health care prepayment plan appeals. </P>
                <HD SOURCE="HD2">D. Medicare Part D (Prescription Drug Plan) Appeals </HD>
                <P>
                    The annually adjusted AIC threshold amounts for ALJ hearings and judicial review that apply to Medicare Parts A, B, and C appeals also apply to Medicare Part D appeals. Section 101 of the MMA added section 1860D-4(h)(1) of the Act regarding Part D appeals. This statutory provision requires a prescription drug plan sponsor to meet the requirements set forth in sections 1852(g)(4) and (g)(5) of the Act, in a similar manner as MA organizations. As noted above, the annually adjusted AIC threshold requirement was added to section 1852(g)(5) of the Act by section 940(b)(2)(A) of the MMA. The implementing regulations for Medicare Part D appeals can be found at 42 CFR Part 423, Subpart M. The regulations impart at § 423.562(c) that unless the Part D appeals rules provide otherwise, the Part C appeals rules (including the annually adjusted AIC threshold amount) apply to Part D appeals to the extent they are appropriate. More specifically, § 423.610 and § 423.630 of the Part D appeals rules discuss the AIC threshold amounts for ALJ hearings and judicial review. Section 423.610(a) 
                    <PRTPAGE P="55848"/>
                    grants a Part D enrollee, who is dissatisfied with the Independent Review Entity (IRE) reconsideration determination, a right to an ALJ hearing if the amount remaining in controversy after the IRE reconsideration meets the threshold amount established annually by the Secretary. Section 423.630(a) allows a Part D enrollee to request judicial review of an ALJ's decision if the AIC meets the threshold amount established annually by the Secretary. 
                </P>
                <HD SOURCE="HD1">II. Annual AIC Adjustments </HD>
                <HD SOURCE="HD2">A. AIC Adjustment Formula and AIC Adjustments </HD>
                <P>As previously noted, section 940 of the MMA requires that the AIC threshold amounts be adjusted annually, beginning in January of 2005, by the percentage increase in the medical care component of the consumer price index (CPI) for all urban consumers (U.S. city average) for July 2003 to the July of the preceding year involved and rounded to the nearest multiple of $10. </P>
                <HD SOURCE="HD2">B. Calendar Year 2009 </HD>
                <P>The AIC threshold amount for ALJ hearing requests will be $120 and the AIC threshold amount for judicial review will be $1,220 for the 2009 calendar year. These new amounts are based on the 22.3 percent increase in the medical care component of the CPI from July of 2003 to July of 2008. The CPI level was at 297.6 in July of 2003 and rose to 363.96 in July of 2008. This change accounted for the 22.3 percent increase. The AIC threshold amount for ALJ hearing requests changes to $122.30 based on the 22.3 percent increase. In accordance with section 940 of the MMA, this amount is rounded to the nearest multiple of $10. Therefore, the 2009 AIC threshold amount for ALJ hearings is $120. The AIC threshold amount for judicial review changes to $1,223.00 based on the 22.3 percent increase. This amount was rounded to the nearest multiple of $10, resulting in a 2009 AIC threshold amount of $1,220. </P>
                <HD SOURCE="HD2">C. Summary Table of Adjustments in the AIC Threshold Amounts </HD>
                <P>In Table 1 below, we list the Calendar Year 2005 through 2009 threshold amounts. </P>
                <GPOTABLE COLS="06" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                    <TTITLE>Table 1—Amount-in-Controversy Threshold Amounts</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">CY 2005</CHED>
                        <CHED H="1">CY 2006</CHED>
                        <CHED H="1">CY 2007</CHED>
                        <CHED H="1">CY 2008</CHED>
                        <CHED H="1">CY 2009</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">ALJ Hearing</ENT>
                        <ENT>$100</ENT>
                        <ENT>$110</ENT>
                        <ENT>$110</ENT>
                        <ENT>$120</ENT>
                        <ENT>$120</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Judicial Review</ENT>
                        <ENT>1050</ENT>
                        <ENT>1090</ENT>
                        <ENT>1130</ENT>
                        <ENT>1180</ENT>
                        <ENT>1,220</ENT>
                    </ROW>
                    <TNOTE>Key: CY = Calendar Year.</TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD1">III. Collection of Information Requirements (If Applicable) </HD>
                <P>This document does not impose information collection and recordkeeping requirements. Consequently, it need not be reviewed by the Office of Management and Budget under the authority of the Paperwork Reduction Act of 1995 (44 U.S.C. 35).</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Program No. 93.778, Medical Assistance Program; No. 93.773 Medicare—Hospital Insurance Program; and No. 93.774, Medicare—Supplementary Medical Insurance Program)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: September 12, 2008. </DATED>
                    <NAME>Kerry Weems, </NAME>
                    <TITLE>Acting Administrator, Centers for Medicare &amp; Medicaid Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22589 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <DEPDOC>[CMS-3203-N] </DEPDOC>
                <SUBJECT>Medicare Program; Meeting of the Medicare Evidence Development and Coverage Advisory Committee—November 19, 2008 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces that a public meeting of the Medicare Evidence Development &amp; Coverage Advisory Committee (MEDCAC) (“Committee”) will be held on Wednesday, November 19, 2008. The Committee generally provides advice and recommendations concerning the adequacy of scientific evidence needed to determine whether certain medical items and services can be covered under the Medicare statute. This meeting will focus on the use of computed tomography colonography (CTC), also referred to as virtual colonoscopy, as a cancer screening test for average risk individuals (See section 1861(pp) of the Social Security Act (42 U.S.C. section 1395x(pp))). The meeting will discuss the various kinds of evidence that are useful to support requests for Medicare coverage in this field. This meeting is open to the public in accordance with the Federal Advisory Committee Act (5 U.S.C. App. 2, section 10(a)). </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Meeting date:</E>
                         The public meeting will be held on Wednesday, November 19, 2008 from 7:30 a.m. until 4:30 p.m., e.s.t. 
                    </P>
                    <P>
                        <E T="03">Deadline for Submission of Written Comments:</E>
                         Written comments must be received at the address specified in the 
                        <E T="02">ADDRESSES</E>
                         section of this notice by 5 p.m., e.s.t on October 20, 2008. Once submitted comments are final. 
                    </P>
                    <P>
                        <E T="03">Deadlines for Speaker Registration and Presentation Materials:</E>
                         The deadline to register to be a speaker and to submit powerpoint presentation materials and writings that will be used in support of an oral presentation, is 5 p.m., d.s.t. on Monday, October 20, 2008. Speakers may register by phone or via e-mail by contacting the person listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section of this notice. Presentation materials must be received at the address specified in the 
                        <E T="02">ADDRESSES</E>
                         section of this notice. 
                    </P>
                    <P>
                        <E T="03">Deadline for All Other Attendees Registration:</E>
                         Individuals may register by phone or via e-mail by contacting the person listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section of this notice by 5 p.m., e.s.t. on Wednesday, November 12, 2008. 
                    </P>
                    <P>
                        <E T="03">Deadline for Submitting a Request for Special Accommodations:</E>
                         Persons attending the meeting who are hearing or visually impaired, or have a condition that requires special assistance or accommodations, are asked to contact the Executive Secretary as specified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section of this notice no later than 5 p.m., e.s.t. Friday, November 7, 2008. 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">Meeting Location:</E>
                         The meeting will be held in the main auditorium of the Centers for Medicare &amp; Medicaid Services, 7500 Security Blvd., Baltimore, MD 21244. 
                    </P>
                    <P>
                        <E T="03">Submission of Presentations and Comments:</E>
                         Presentation materials and written comments that will be presented at the meeting must be submitted via e-
                        <PRTPAGE P="55849"/>
                        mail to 
                        <E T="03">MedCACpresentations@cms.hhs.gov</E>
                         or by regular mail to the contact listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section of this notice by the date specified in the 
                        <E T="02">DATES</E>
                         section of this notice. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Maria Ellis, Executive Secretary for MEDCAC, Centers for Medicare &amp; Medicaid Services, Office of Clinical Standards and Quality, Coverage and Analysis Group, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244 or contact Ms. Ellis by phone (410-786-0309) or via e-mail at 
                        <E T="03">Maria.Ellis@cms.hhs.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background </HD>
                <P>
                    MEDCAC, formerly known as the Medicare Coverage Advisory Committee (MCAC), provides advice and recommendations to CMS regarding clinical issues. (For more information on MCAC, see the December 14, 1998 
                    <E T="04">Federal Register</E>
                     (63 FR 68780.)) This notice announces the November 19, 2008, public meeting of the Committee. During this meeting, the Committee will discuss the available evidence on computed tomography colonography (CTC) as a screening test for colorectal cancer, including test characteristics, screening frequency, cost effectiveness, safety and training requirements (See section 1861(pp) of the Social Security Act (42 U.S.C. section 1395x(pp))). Background information about this topic, including panel materials, are available at 
                    <E T="03">http://ww.cms.hhs.gov/coverage</E>
                    . We encourage the participation of appropriate organizations with expertise in colorectal cancer and screening for this disease. 
                </P>
                <HD SOURCE="HD1">II. Meeting Format </HD>
                <P>
                    This meeting is open to the public. The Committee will hear oral presentations from the public for approximately 30 minutes. The Committee may limit the number and duration of oral presentations to the time available. Your comments should focus on issues specific to the list of topics that we have proposed to the Committee. The list of research topics to be discussed at the meeting will be available on the following Web site prior to the meeting: 
                    <E T="03">http://www.cms.hhs.gov/mcd/index_list.asp?list_type=mcac</E>
                    . We require that you declare at the meeting whether you have any financial involvement with manufacturers (or their competitors) of any items or services being discussed. 
                </P>
                <P>The Committee will deliberate openly on the topics under consideration. Interested persons may observe the deliberations, but the Committee will not hear further comments during this time except at the request of the chairperson. The Committee will also allow a 15-minute unscheduled open public session for any attendee to address issues specific to the topics under consideration. At the conclusion of the day, the members will vote and the Committee will make its recommendation(s) to CMS. </P>
                <HD SOURCE="HD1">III. Registration Instructions </HD>
                <P>
                    CMS' Coverage and Analysis Group is coordinating meeting registration. While there is no registration fee, individuals must register to attend. You may register by contacting the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this notice by the deadline listed in the 
                    <E T="02">DATES</E>
                     section of this notice. Please provide your full name (as it appears on your state-issued driver's license), address, organization, telephone, fax number(s), and e-mail address. You will receive a registration confirmation with instructions for your arrival at the CMS complex or you will be notified the seating capacity has been reached. 
                </P>
                <HD SOURCE="HD1">IV. Security, Building, and Parking Guidelines </HD>
                <P>This meeting will be held in a Federal government building; therefore, Federal security measures are applicable. We recommend that confirmed registrants arrive reasonably early, but no earlier than 45 minutes prior to the start of the meeting, to allow additional time to clear security. Security measures include the following: </P>
                <P>• Presentation of government-issued photographic identification to the Federal Protective Service or Guard Service personnel. </P>
                <P>• Inspection of vehicle's interior and exterior (this includes engine and trunk inspection) at the entrance to the grounds. Parking permits and instructions will be issued after the vehicle inspection. </P>
                <P>• Inspection, via metal detector or other applicable means of all persons brought entering the building. We note that all items brought into CMS, whether personal or for the purpose of presentation or to support a presentation, are subject to inspection. We cannot assume responsibility for coordinating the receipt, transfer, transport, storage, set-up, safety, or timely arrival of any personal belongings or items used for presentation or to support a presentation. </P>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>Individuals who are not registered in advance will not be permitted to enter the building and will be unable to attend the meeting. The public may not enter the building earlier than 30 to 45 minutes prior to the convening of the meeting.</P>
                </NOTE>
                <P>All visitors must be escorted in areas other than the lower and first floor levels in the Central Building. </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>5 U.S.C. App. 2, section 10(a).</P>
                </AUTH>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Program No. 93.773, Medicare—Hospital Insurance; and Program No. 93.774, Medicare—Supplementary Medical Insurance Program)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: September 15, 2008. </DATED>
                    <NAME>Barry M. Straube, </NAME>
                    <TITLE>Chief Medical Officer and Director, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22591 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <DEPDOC>[CMS-7010-N] </DEPDOC>
                <SUBJECT>Medicare Program; Announcement of Meeting of the Advisory Panel on Medicare Education, October 22, 2008 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Federal Advisory Committee Act, this notice announces a meeting of Advisory Panel on Medicare Education (the Panel). The Panel advises and makes recommendations to the Secretary of Health and Human Services and the Administrator of the Centers for Medicare &amp; Medicaid Services on the effectiveness of consumer education strategies concerning the Medicare program. This meeting is open to the public. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Meeting Date:</E>
                         October 22, 2008 from 9 a.m. to 3:30 p.m., e.d.t. 
                    </P>
                    <P>
                        <E T="03">Deadline for Meeting Registration, Presentations and Comments:</E>
                         October 15, 2008, 12 noon, e.d.t. 
                    </P>
                    <P>
                        <E T="03">Deadline for Requesting Special Accommodations:</E>
                         October 8, 2008, 12 noon, e.d.t. 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">Meeting Location:</E>
                         Fairmont Washington Hotel, 2401 M Street, NW., Washington, DC 20037, (202) 429-2400. 
                        <E T="03">Meeting Registration, Presentations, and Written Comments:</E>
                         Lynne Johnson, Designated Federal Official, Division of Forum and Conference Development, Office of External Affairs, Centers for 
                        <PRTPAGE P="55850"/>
                        Medicare &amp; Medicaid Services, 7500 Security Boulevard, Mailstop S1-05-06, Baltimore, MD 21244-1850 or contact Ms. Johnson via e-mail at 
                        <E T="03">Lynne.Johnson@cms.hhs.gov</E>
                        . 
                    </P>
                    <P>
                        <E T="03">Registration:</E>
                         The meeting is open to the public, but attendance is limited to the space available. Persons wishing to attend this meeting must register by contacting Lynne Johnson at the address listed in the 
                        <E T="02">ADDRESSES</E>
                         section of this notice or by telephone at (410) 786-0090, by the date listed in the 
                        <E T="02">DATES</E>
                         section of this notice. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lynne Johnson, (410) 786-0090. Please refer to the CMS Advisory Committees' Information Line (1-877-449-5659 toll-free)/(410-786-9379 local) or the Internet (
                        <E T="03">http://www.cms.hhs.gov/FACA/04_APME.asp</E>
                        ) for additional information and updates on committee activities. Press inquiries are handled through the CMS Press Office at (202) 690-6145. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">Section 9(a)(2) of the Federal Advisory Committee Act authorizes the Secretary of Health and Human Services (the Secretary) to establish an advisory panel if the Secretary determines that the panel is “in the public interest in connection with the performance of duties imposed  * * *  by law.” Such duties are imposed by section 1804 of the Social Security Act (the Act), requiring the Secretary to provide informational materials to Medicare beneficiaries about the Medicare program, and section 1851(d) of the Act, requiring the Secretary to provide for “activities  * * *  to broadly disseminate information to [M]edicare beneficiaries * * *  on the coverage options provided under [Medicare Advantage] in order to promote an active, informed selection among such options.” </P>
                <P>
                    The Panel is also authorized by section 1114(f) of the Act (42 U.S.C. 1311(f)) and section 222 of the Public Health Service Act (42 U.S.C. 217a). The Secretary signed the charter establishing this Panel on January 21, 1999 and approved the renewal of the charter on November 14, 2006. The establishment of the charter and the renewal of the charter were announced in the February 17, 1999 
                    <E T="04">Federal Register</E>
                     (64 FR 7899), and the March 23, 2007 
                    <E T="04">Federal Register</E>
                     (72 FR 13796), respectively. The Panel advises and makes recommendations to the Secretary and the Administrator of the Centers for Medicare &amp; Medicaid Services (CMS) on opportunities to enhance the effectiveness of consumer education strategies concerning the Medicare program. The Secretary delegates authority to the Administrator. 
                </P>
                <P>The goals of the Panel are as follows:</P>
                <P>• To provide recommendations on the development and implementation of a national Medicare education program that describes the options for selecting a health plan and prescription drug plan under Medicare. </P>
                <P>• To enhance the Federal government's effectiveness in informing the Medicare consumer, including the appropriate use of public-private partnerships. </P>
                <P>• To provide recommendations on how to expand outreach to vulnerable and underserved communities, including racial and ethnic minorities, in the context of a national Medicare education program. </P>
                <P>• To assemble an information base of best practices for helping consumers evaluate health plan options and build a community infrastructure for information, counseling, and assistance.</P>
                <P>The current members of the Panel are: Gwendolyn T. Bronson, SHINE/SHIP Counselor, Massachusetts SHINE Program; Dr. Yanira Cruz, President and Chief Executive Officer, National Hispanic Council on Aging; Clayton Fong, President and Chief Executive Officer, National Asian Pacific Center on Aging; Nan Kirsten-Forte, Executive Vice President, Consumer Services, WebMD; Dr. Jessie C. Gruman, President and Chief Executive Officer, Center for the Advancement of Health; Dr. Frank B. McArdle, Manager, Hewitt Research Office, Hewitt Associates; Rebecca Snead, Executive Vice President and Chief Executive Officer, National Alliance of State Pharmacy Associations. Thirteen new members will be appointed to the panel and announced at the meeting.</P>
                <P>The agenda for the October 22, 2008, meeting will include the following:</P>
                <P>• Recap of the previous (June 26, 2008) meeting. </P>
                <P>• Introduction of New Members. </P>
                <P>• Medicare Outreach and Education Strategies. </P>
                <P>• Public Comment. </P>
                <P>• Listening Session with CMS Leadership. </P>
                <P>• Next Steps.</P>
                <P>
                    Individuals or organizations that wish to make a 5-minute oral presentation on an agenda topic should submit a written copy of the oral presentation to Lynne Johnson at the address listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this notice by the date listed in the 
                    <E T="02">DATES</E>
                     section of this notice. The number of oral presentations may be limited by the time available. Individuals not wishing to make a presentation may submit written comments to Ms. Johnson at the address listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this notice by the date listed in the 
                    <E T="02">DATES</E>
                     section of this notice. 
                </P>
                <P>
                    Individuals requiring sign language interpretation or other special accommodations should contact Ms. Johnson at the address listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this notice by the date listed in the 
                    <E T="02">DATES</E>
                     section of this notice. 
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>Sec. 222 of the Public Health Service Act (42 U.S.C. 217a) and sec. 10(a) of Pub. L. 92-463 (5 U.S.C. App. 2, sec. 10(a) and 41 CFR 102-3). </P>
                </AUTH>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Program No. 93.733, Medicare—Hospital Insurance Program; and Program No. 93.774, Medicare—Supplementary Medical Insurance Program)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: September 10, 2008. </DATED>
                    <NAME>Kerry Weems, </NAME>
                    <TITLE>Acting Administrator, Centers for Medicare &amp; Medicaid Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-21910 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <SUBJECT>Statement of Organization, Functions, and Delegations of Authority </SUBJECT>
                <P>
                    Part F of the Statement of Organization, Functions, and Delegations of Authority for the Department of Health and Human Services, Centers for Medicare &amp; Medicaid Services (CMS), (
                    <E T="04">Federal Register</E>
                    , Vol. 73, No. 127, pp. 37463-37464, dated Tuesday, July 1, 2008) is amended to reflect an update to the functions for the Center for Medicare Management. 
                </P>
                <P>Part F. is described below: </P>
                <P>• Section F. 20. (Functions) reads as follows: </P>
                <HD SOURCE="HD1">Center for Medicare Management (FAH) </HD>
                <P>• Serves as the focal point for all Agency interactions with health care providers, intermediaries, carriers, and Medicare Administrative Contractors (MACs) for issues relating to Agency fee-for-service (FFS) policies and operations. </P>
                <P>• Responsible for policies related to scope of benefits and other statutory, regulatory and contractual provisions. </P>
                <P>
                    • Based on program data, develops payment mechanisms, administrative mechanisms, and regulations to ensure that CMS is purchasing medically necessary items and services under Medicare FFS. 
                    <PRTPAGE P="55851"/>
                </P>
                <P>• Develops, evaluates and maintains policies, regulations, and instructions that define the scope of benefits and payment amounts for: </P>
                <P>1. Hospitals for inpatient services under the inpatient prospective payment system and the long-term care hospital prospective payment system; </P>
                <P>2. Inpatient services in hospitals and units excluded from the prospective payment systems; </P>
                <P>3. Physicians and non-physician practitioners; </P>
                <P>4. Hospital outpatient departments, comprehensive outpatient rehabilitation facilities and ambulatory surgical centers; </P>
                <P>5. Clinical laboratory services; </P>
                <P>6. Ambulance services; </P>
                <P>7. Prescription drugs and blood, blood products and hemophilia clotting factor; and </P>
                <P>8. Telemedicine services, rural health clinics, and federally-qualified health centers. </P>
                <P>• Formulates CMS policy for development, analysis, and maintenance of new and revised medical codes and medical classification systems (including ICD-9-CM, Healthcare Common Procedure Coding System, Diagnosis Related Groups, and Ambulatory Payment Classifications) and develops common medical coding standards and policy. </P>
                <P>• Participates in the development and evaluation of proposed legislation pertaining to assigned subject areas. </P>
                <P>• Coordinates with the Office of Clinical Standards and Quality on coverage issues in assigned areas. </P>
                <P>• Develops, evaluates, and reviews regulations, manuals, program guidelines, and instructions required for the dissemination of program policies to program contractors and the health care field. </P>
                <P>• Identifies, studies and makes recommendations for modifying Medicare policies to reflect changes in beneficiary health care needs, program objectives, and the health care delivery system. </P>
                <P>• Develops, evaluates and maintains policies, regulations, and instructions that define the scope of benefits and payment amounts for skilled nursing facilities, home health agencies, hospice, durable medical equipment, orthotics, prosthetics and supplies. </P>
                <P>• Develops and evaluates national Medicare policies and principles for applying limitations to the costs of skilled nursing facilities and home health agencies. Develops criteria for exceptions to the cost limitations for skilled nursing facilities. Reviews and makes decisions on requests for such exceptions. </P>
                <P>• Analyzes payment data, develops, maintains and updates payments rates for End Stage Renal Disease services and Program of All-Inclusive Care for the Elderly sites. </P>
                <P>• Manages designation process for Medicare organ transplant centers, organ procurement organizations and for hospitals seeking out-of-service-area waivers. </P>
                <P>• Develops, issues and administers the specifications, requirements, methods, standards, policies, procedures and budget guidelines for Medicare claims processing related activities, including detailed definitions of the relative responsibilities of providers, contractors, CMS, other third-party payers and the beneficiaries of the Medicare program. </P>
                <P>• Develops and releases the coding and pricing databases and software for physician, laboratory, Skilled Nursing Facility, Home Health, Inpatient, Outpatient and supplier services in the Medicare claims processing standard systems. </P>
                <P>• Develops policies related to the integration of health care services, including policies on ownership and referral arrangements, business relationships and conflict of interest. </P>
                <P>• Serves as the CMS lead for management, oversight, budget and performance issues relating to Medicare carriers, fiscal intermediaries, and MACs. </P>
                <P>• Functions as CMS liaison for all Medicare carrier, fiscal intermediary, and MAC program issues and, in close collaboration with the regional offices and other CMS components, coordinates Agency-wide contractor activities. </P>
                <P>• Manages contractor instructions, workload, and change management process. </P>
                <P>• Manages and oversees Medicare contractor provider inquiry, outreach, and education activities including specifying Budget Performance Requirements, allocating and managing budget dollars across contractors, evaluating supplemental budget requests, issuing program instructions and participating in contractor performance evaluation activities. </P>
                <P>• In conjunction with the CMS program area experts, develops training programs and materials, and training tools to educate providers, physicians, suppliers and Medicare contractor provider education staff on new initiatives and changes to the Medicare program. </P>
                <P>• Develops national provider/supplier education products and training tools for Medicare contractors as well as for provider education provided directly by CMS. </P>
                <P>• Supports communication between CMS and the provider/supplier community through facilitation of “open door” and Participating Physician Advisory Committee meetings, other listening sessions and promotes awareness of Agency initiatives by sponsoring exhibit programs at industry conferences. </P>
                <P>• Develops system requirements and computer software for select portions of Medicare FFS claims processing systems. </P>
                <P>• Develops and implements Medicare FFS program requirements for provider billing and for claims processing systems. </P>
                <P>• Implements the Medicare Health Support Program. </P>
                <SIG>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>James W. Weber, </NAME>
                    <TITLE>Acting Director, Office of Operations Management,  Centers for Medicare &amp; Medicaid Services.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22690 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2008-D-0514]</DEPDOC>
                <SUBJECT>Draft Guidance for Industry on End-of-Phase 2A Meetings; Availability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing the availability of a draft guidance for industry entitled “End-of-Phase 2A Meetings.” This draft guidance provides information on end-of-phase 2A (EOP2A) meetings for sponsors of investigational new drug applications (INDs) who seek guidance on employing clinical trial simulation and quantitative modeling of prior knowledge (e.g., drug, disease, placebo) to design trials for better dose response estimation, dose selection, and other appropriate issues. This draft guidance is intended to further FDA initiatives directed at identifying opportunities to facilitate the development of innovative medical products and to improve the quality of drug applications through early meetings with sponsors.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Although you can comment on any guidance at any time (see 21 CFR 10.115(g)(5)), to ensure that the agency considers your comment on this draft guidance before it begins work on the final version of the guidance, submit 
                        <PRTPAGE P="55852"/>
                        written or electronic comments on the draft guidance by November 25, 2008.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written requests for single copies of the draft guidance to the Division of Drug Information, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, rm. 2201, Silver Spring, MD 20993-0002. Send one self-addressed adhesive label to assist that office in processing your requests. Submit written comments on the draft guidance to the Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852. Submit electronic comments to 
                        <E T="03">http://www.regulations.gov</E>
                        . See the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for electronic access to the draft guidance document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Robert Powell, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 21, rm. 4526, Silver Spring, MD 20993-0002, 301-796-1589</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    FDA is announcing the availability of a draft guidance for industry entitled “End-of-Phase 2A Meetings.” This draft guidance will meet one of the performance goals agreed to under the September 27, 2007, reauthorization of the Prescription Drug User Fee Act (PDUFA IV). Under section XI of the PDUFA IV Performance Goals, Expediting Drug Development, FDA agreed to publish by the end of fiscal year 2008 a draft guidance on end-of-phase 2A meetings (see section XI.A.4 at 
                    <E T="03">http://www.fda.gov/oc/pdufa4/pdufa4goals.html</E>
                    ). This draft guidance is intended to facilitate early meetings (referred to as end-of-phase 2A meetings or EOP2A meetings) between FDA and sponsors who seek interaction or guidance related to the use of quantitative drug development methods (i.e., exposure-response, pharmacokinetic/pharmacodynamic (PK/PD) modeling, drug-disease modeling, genomic analysis) to inform drug development and regulatory decisions. The draft guidance provides recommendations to IND sponsors on the following topics:
                </P>
                <P>• Objectives of an EOP2A meeting,</P>
                <P>• Possible topics for discussion at EOP2A meetings,</P>
                <P>• Useful information for an EOP2A meeting package, and</P>
                <P>• Timing of EOP2A meetings.</P>
                <P>This draft guidance is being issued consistent with FDA's good guidance practices regulation (21 CFR 10.115). The draft guidance, when finalized, will represent the agency's current thinking on end-of-phase 2A meetings. It does not create or confer any rights for or on any person and does not operate to bind FDA or the public. An alternative approach may be used if such approach satisfies the requirements of the applicable statutes and regulations.</P>
                <HD SOURCE="HD1">II. Comments</HD>
                <P>
                    Interested persons may submit to the Division of Dockets Management (see 
                    <E T="02">ADDRESSES</E>
                    ) written or electronic comments regarding this document. Submit a single copy of electronic comments or two paper copies of any mailed comments, except that individuals may submit one paper copy. Comments are to be identified with the docket number found in brackets in the heading of this document. Received comments may be seen in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday.
                </P>
                <P>
                    Please note that on January 15, 2008, the FDA Division of Dockets Management Web site transitioned to the Federal Dockets Management System (FDMS). FDMS is a Government-wide, electronic docket management system. Electronic comments or submissions will be accepted by FDA only through FDMS at 
                    <E T="03">http://www.regulations.gov</E>
                    .
                </P>
                <HD SOURCE="HD1">III. Paperwork Reduction Act of 1995</HD>
                <P>This draft guidance refers to previously approved collections of information found in FDA regulations. These collections of information are subject to review by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). The collections of information in 21 CFR part 312 and the guidance on “Formal Meetings With Sponsors and Applicants for PDUFA Products” have been approved under OMB control numbers 0910-0014 and 0910-0429, respectively.</P>
                <HD SOURCE="HD1">IV. Electronic Access</HD>
                <P>
                    Persons with access to the Internet may obtain the document at either 
                    <E T="03">http://www.fda.gov/cder/guidance/index.htm</E>
                     or 
                    <E T="03">http://www.regulations.gov</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: September 22, 2008.</DATED>
                    <NAME>Jeffrey Shuren,</NAME>
                    <TITLE>Associate Commissioner for Policy and Planning.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22669 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket Nos. FDA-2008-M-0207, FDA-2008-M-0243, FDA-2008-M-0244, FDA-2008-M-0283, FDA-2008-M-0335, FDA-2008-M-0311, FDA-2008-M-0342, FDA-2008-M-0378]</DEPDOC>
                <SUBJECT>Medical Devices; Availability of Safety and Effectiveness Summaries for Premarket Approval Applications</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is publishing a list of premarket approval applications (PMAs) that have been approved. This list is intended to inform the public of the availability of safety and effectiveness summaries of approved PMAs through the Internet and the agency's Division of Dockets Management.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written requests for copies of summaries of safety and effectiveness data to the Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852. Please cite the appropriate docket number as listed in Table 1 of this document when submitting a written request. See the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for electronic access to the summaries of safety and effectiveness.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nicole Wolanski, Center for Devices and Radiological Health (HFZ-402), Food and Drug Administration, 9200 Corporate Blvd., Rockville, MD 20850, 240-276-4010.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of January 30, 1998 (63 FR 4571), FDA published a final rule that revised 21 CFR 814.44(d) and 814.45(d) to discontinue individual publication of PMA approvals and denials in the 
                    <E T="04">Federal Register</E>
                    . Instead, the agency now posts this information on the Internet on FDA's home page at 
                    <E T="03">http://www.fda.gov</E>
                    . FDA believes that this procedure expedites public notification of these actions because announcements can be placed on the Internet more quickly than they can be published in the 
                    <E T="04">Federal Register</E>
                    , and FDA believes that the Internet is accessible to more people than the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>
                    In accordance with section 515(d)(4) and (e)(2) of the Federal Food, Drug, and 
                    <PRTPAGE P="55853"/>
                    Cosmetic Act (the act) (21 U.S.C. 360e(d)(4) and (e)(2)), notification of an order approving, denying, or withdrawing approval of a PMA will continue to include a notice of opportunity to request review of the order under section 515(g) of the act. The 30-day period for requesting reconsideration of an FDA action under § 10.33(b) (21 CFR 10.33(b)) for notices announcing approval of a PMA begins on the day the notice is placed on the Internet. Section 10.33(b) provides that FDA may, for good cause, extend this 30-day period. Reconsideration of a denial or withdrawal of approval of a PMA may be sought only by the applicant; in these cases, the 30-day period will begin when the applicant is notified by FDA in writing of its decision.
                </P>
                <P>The regulations provide that FDA publish a quarterly list of available safety and effectiveness summaries of PMA approvals and denials that were announced during that quarter. The following is a list of approved PMAs for which summaries of safety and effectiveness were placed on the Internet from April 1, 2008, through June 30, 2008. There were no denial actions during this period. The list provides the manufacturer's name, the product's generic name or the trade name, and the approval date.</P>
                <GPOTABLE COLS="4" OPTS="L4,nj,i2" CDEF="xl32,xl43,xl73,xl26">
                    <TTITLE>
                        <E T="04">Table 1—List of Safety and Effectiveness Summaries for Approved PMAs Made Available From April 1, 2008, through June 30, 2008</E>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">PMA No./Docket No.</CHED>
                        <CHED H="1">Applicant</CHED>
                        <CHED H="1">TRADE NAME</CHED>
                        <CHED H="1">Approval Date</CHED>
                    </BOXHD>
                    <ROW RUL="s,s,s,s">
                        <ENT I="01">
                            P050020
                            <LI>FDA-2008-M-0207</LI>
                        </ENT>
                        <ENT>Abbott Diabetes Care, Inc.</ENT>
                        <ENT>FREESTYLE NAVIGATOR CONTINUOUS GLUCOSE MONITORING SYSTEM</ENT>
                        <ENT>March 12, 2008</ENT>
                    </ROW>
                    <ROW RUL="s,s,s,s">
                        <ENT I="01">
                            P010012 (S037)
                            <LI>FDA-2008-M-0243</LI>
                        </ENT>
                        <ENT>Guidant Corp.</ENT>
                        <ENT>Contak Renewal 3 AVT system &amp; contak reviewal 3AVT HE System</ENT>
                        <ENT>March 13, 2008</ENT>
                    </ROW>
                    <ROW RUL="s,s,s,s">
                        <ENT I="01">
                            P070027
                            <LI>FDA-2008-M-0244</LI>
                        </ENT>
                        <ENT>Medtronic Vascular</ENT>
                        <ENT>The talent abdominal stent graft system</ENT>
                        <ENT>April 15, 2008</ENT>
                    </ROW>
                    <ROW RUL="s,s,s,s">
                        <ENT I="01">
                            P060040
                            <LI>FDA-2008-M-0283</LI>
                        </ENT>
                        <ENT>Thoratec Corp.</ENT>
                        <ENT>Thoratec Heartmate II Left ventricular assist</ENT>
                        <ENT>April 21, 2008</ENT>
                    </ROW>
                    <ROW RUL="s,s,s,s">
                        <ENT I="01">
                            P070008
                            <LI>FDA-2008-M-0335</LI>
                        </ENT>
                        <ENT>Biotronik, Inc.</ENT>
                        <ENT>Stratos LV CRT-P &amp; stratos LV-T CRT-P, corox OTW BP lead &amp; corox OTW-s bp lead</ENT>
                        <ENT>May 12, 2008</ENT>
                    </ROW>
                    <ROW RUL="s,s,s,s">
                        <ENT I="01">
                            P070016
                            <LI>FDA-2008-M-0311</LI>
                        </ENT>
                        <ENT>Cook, Inc.</ENT>
                        <ENT>Zenith TX2 Thoracic TAA endovascular graft with the H&amp;LB One-shot introduction system</ENT>
                        <ENT>May 21, 2008</ENT>
                    </ROW>
                    <ROW RUL="s,s,s,s">
                        <ENT I="01">
                            P070007
                            <LI>FDA-2008-M-0342</LI>
                        </ENT>
                        <ENT>Medtronic Vascular</ENT>
                        <ENT>Talent Thoracic Stent Graft System</ENT>
                        <ENT>June 5, 2008</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            H070003
                            <LI>FDA-2008-M-0378</LI>
                        </ENT>
                        <ENT>Synapse Biomedical, Inc.</ENT>
                        <ENT>NeuRx RA/4</ENT>
                        <ENT>June 17, 2008</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">II. Electronic Access</HD>
                <P>
                    Persons with access to the Internet may obtain the documents at 
                    <E T="03">http://www.fda.gov/cdrh/pmapage.html</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: September 12, 2008.</DATED>
                    <NAME>Daniel G. Schultz,</NAME>
                    <TITLE>Director, Center for Devices and Radiological Health.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22668 Filed 9-25-08; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>National Institutes of Health </SUBAGY>
                <SUBJECT>Government-Owned Inventions; Availability for Licensing </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institutes of Health, Public Health Service, HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The inventions listed below are owned by an agency of the U.S. Government and are available for licensing in the U.S. in accordance with 35 U.S.C. 207 to achieve expeditious commercialization of results of federally-funded research and development. Foreign patent applications are filed on selected inventions to extend market coverage for companies and may also be available for licensing. </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Licensing information and copies of the U.S. patent applications listed below may be obtained by writing to the indicated licensing contact at the Office of Technology Transfer, National Institutes of Health, 6011 Executive Boulevard, Suite 325, Rockville, Maryland 20852-3804; telephone: 301/496-7057; fax: 301/402-0220. A signed Confidential Disclosure Agreement will be required to receive copies of the patent applications. </P>
                </ADD>
                <HD SOURCE="HD1">
                    Methods for Preparing 
                    <E T="7462">Bacillus anthracis</E>
                     Protective Antigen for Use in Vaccines 
                </HD>
                <P>
                    <E T="03">Description of Technology:</E>
                     This invention relates to improved methods of preparing 
                    <E T="03">Bacillus anthracis</E>
                     protective antigen (PA) from a cell or organism, particularly a recombinant cell or microorganism, for use in vaccines. Production and purification methods of modified PA from a non-sporogenic strain of 
                    <E T="03">Bacillus anthracis</E>
                     are described. Specifically, a scalable fermentation and purification process is claimed that is suitable for vaccine development, and that produces almost three times more product than earlier-reported processes. This is accomplished using a biologically inactive protease-resistant PA variant in a protease-deficient non-sporogenic avirulent strain of 
                    <E T="03">B. anthracis</E>
                     (BH445). One of the PA variants described in the patent application lacks the furin and chymotrypsin cleavage sites. 
                </P>
                <P>
                    <E T="03">Advantages: Bacillus anthracis</E>
                     protective antigen is a major component of the currently licensed human vaccine (Anthrax Vaccine Adsorbed, AVA). Although the current human vaccine has been shown to be effective against cutaneous anthrax infection in animals and humans and against inhalation anthrax in rhesus monkeys, the licensed vaccine has several limitations: (1) AVA 
                    <PRTPAGE P="55854"/>
                    elicits a relatively high degree of local and systemic adverse reactions, probably mediated by variable amounts of undefined bacterial products, making standardization difficult; (2) the immunization schedule requires administration of six doses within an eighteen (18) month period, followed by annual boosters; (3) there is no defined vaccine-induced protective level of antibody to PA by which to evaluate new lots of vaccines; and (4) AVA is comprised of a wild-type PA. Thus a vaccine comprising a modified purified recombinant PA would be effective, safe, allow precise standardization, and require fewer injections. 
                </P>
                <P>
                    The invention also relates to PA variants, and/or compositions thereof, which are useful for eliciting an immunogenic response in mammals, particularly humans, including responses that provide protection against, or reduce the severity of, infections caused by 
                    <E T="03">B. anthracis</E>
                    . The vaccines claimed in this application are intended for active immunization for prevention of 
                    <E T="03">B. anthracis</E>
                     infection, and for preparation of immune antibodies. 
                </P>
                <P>
                    <E T="03">Application:</E>
                     Improved 
                    <E T="03">B. anthracis</E>
                     vaccines. 
                </P>
                <P>
                    <E T="03">Development Status:</E>
                     Phase I clinical studies are being performed. 
                </P>
                <P>
                    <E T="03">Inventors:</E>
                     Joseph Shiloach (NIDDK), Stephen Leppla (NIDCR), Delia Ramirez (NIDDK), Rachel Schneerson (NICHD), John Robbins (NICHD).
                </P>
                <P>
                    <E T="03">Publication:</E>
                     DM Ramirez 
                    <E T="03">et al.</E>
                     Production, recovery and immunogenicity of the protective antigen from a recombinant strain of 
                    <E T="03">Bacillus anthracis</E>
                    . J Ind Microbiol Biotechnol. 2002 Apr;28(4):232-238. 
                </P>
                <P>
                    <E T="03">Patent Status:</E>
                     U.S. Patent Application No. 10/290,712 filed 08 Nov 2002 (HHS Reference No. E-023-2002/0-US-02) 
                </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     Available for exclusive or nonexclusive licensing. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     Peter A. Soukas, J.D.; 301/435-4646; 
                    <E T="03">soukasp@mail.nih.gov</E>
                    . 
                </P>
                <P>
                    <E T="03">Collaborative Research Opportunity:</E>
                     The National Institutes of Health is seeking statements of capability or interest from parties interested in collaborative research to further develop, evaluate, or commercialize methods of preparing 
                    <E T="03">Bacillus anthracis</E>
                     protective antigen (PA) from a cell or organism, particularly a recombinant cell or microorganism, for use in vaccines. Please contact Rochelle S. Blaustein, J.D., at 301/451-3636 or 
                    <E T="03">Rochelle.Blaustein@nih.gov</E>
                     for additional information. 
                </P>
                <HD SOURCE="HD1">
                    Recombinant Modified 
                    <E T="7462">Bacillus anthracis</E>
                     Protective Antigen for Use in Vaccines 
                </HD>
                <P>
                    <E T="03">Description of Technology:</E>
                     This invention relates to improved methods of preparing 
                    <E T="03">Bacillus anthracis</E>
                     protective antigen (PA) for use in vaccines. PA is a secreted, non-toxic protein with a molecular weight of 83 KDa. PA is a major component of the currently licensed human vaccine (Anthrax Vaccine Adsorbed, AVA). Although the licensed human vaccine has been shown to be effective against cutaneous anthrax infection in animals and humans and against inhalation anthrax in rhesus monkeys, the licensed vaccine has several limitations: (1) AVA elicits a relatively high degree of local and systemic adverse reactions, probably mediated by variable amounts of undefined bacterial products, making standardization difficult; (2) the immunization schedule requires administration of six doses within an eighteen (18) month period, followed by annual boosters; (3) there is no defined vaccine-induced protective level of antibody to PA by which to evaluate new lots of vaccines; and (4) AVA is comprised of a wild-type PA. It has been suggested that a vaccine comprising a modified purified recombinant PA would be effective, safe, allow precise standardization, and require fewer injections. 
                </P>
                <P>
                    This invention claims methods of producing and recovering PA from a cell or organism, particularly a recombinant cell or microorganism. The invention claims production and purification of modified PA from a non-sporogenic strain of 
                    <E T="03">Bacillus anthracis</E>
                    . In contrast to other previously described methods, greater quantities of PA are obtainable from these cells or microorganisms. Specifically, a scalable fermentation and purification process is claimed that is suitable for vaccine development, and that produces almost three times more product than earlier-reported processes. This is accomplished using a biologically inactive protease-resistant PA variant in a protease-deficient non-sporogenic avirulent strain of 
                    <E T="03">B. anthracis</E>
                     (BH445). One of the PA variants described in the patent application lacks the furin and chymotrypsin cleavage sites. 
                </P>
                <P>
                    The invention relates to improved methods of producing and recovering sporulation-deficient 
                    <E T="03">B. anthracis</E>
                     mutant stains, and for producing and recovering recombinant 
                    <E T="03">B. anthracis</E>
                     protective antigen (PA), especially modified PA which is protease resistant, and to methods of using of these PAs or nucleic acids encoding these PAs for eliciting an immunogenic response in humans, including responses which provide protection against, or reduce the severity of, 
                    <E T="03">B. anthracis</E>
                     bacterial infections and which are useful to prevent and/or treat illnesses caused by 
                    <E T="03">B. anthracis</E>
                    , such as inhalation anthrax, cutaneous anthrax and gastrointestinal anthrax. 
                </P>
                <P>
                    <E T="03">Application:</E>
                     Improved 
                    <E T="03">B. anthracis</E>
                     vaccines. 
                </P>
                <P>
                    <E T="03">Development Status:</E>
                     Phase I clinical studies are being performed. 
                </P>
                <P>
                    <E T="03">Inventors:</E>
                     Stephen Leppla (NIDCR), M. J. Rosovitz (NIDCR), John Robbins (NICHD), Rachel Schneerson (NICHD). 
                </P>
                <P>
                    <E T="03">Patent Status:</E>
                     U.S. Patent No. 7,261,900 issued 28 Aug 2007 (HHS Reference No. E-268-2002/0-US-02); U.S. Patent Application No. 11/831,860 filed 31 Jul 2007 (HHS Reference No. E-268-2002/0-US-03). 
                </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     Available for exclusive or nonexclusive licensing. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     Peter A. Soukas, J.D.; 301/435-4646; 
                    <E T="03">soukasp@mail.nih.gov</E>
                    . 
                </P>
                <HD SOURCE="HD1">
                    γPGA Conjugates for Eliciting Immune Responses Directed Against 
                    <E T="7462">Bacillus anthracis</E>
                     and Other Bacilli 
                </HD>
                <P>
                    <E T="03">Description of Technology:</E>
                     This invention claims immunogenic conjugates of a poly-γ-glutamic acid (γPGA) of 
                    <E T="03">B. anthracis</E>
                    , or of another bacillus that expresses a γPGA that elicit a serum antibody response against 
                    <E T="03">B. anthracis</E>
                    , in mammalian hosts to which the conjugates are administered. The invention also relates methods which are useful for eliciting an immunogenic response in mammals, particularly humans, including responses which provide protection against, or reduce the severity of, infections caused by 
                    <E T="03">B. anthracis</E>
                    . The vaccines claimed in this application are intended for active immunization for prevention of 
                    <E T="03">B. anthracis</E>
                     infection, and for preparation of immune antibodies. The vaccines of this invention are designed to confer specific immunity against infection with 
                    <E T="03">B. anthracis</E>
                    , and to induce antibodies specific to 
                    <E T="03">B. anthracis</E>
                     γPGA. The 
                    <E T="03">B. anthracis</E>
                     vaccine is composed of non-toxic bacterial components, suitable for infants, children of all ages, and adults. 
                </P>
                <P>
                    <E T="03">Inventors:</E>
                     Rachel Schneerson (NICHD), Stephen Leppla (NIAID), John Robbins (NICHD), Joseph Shiloach (NIDDK), Joanna Kubler-Kielb (NICHD), Darrell Liu (NIDCR), Fathy Majadly (NICHD). 
                </P>
                <P>
                    <E T="03">Publication:</E>
                     R Schneerson et al. Poly(gamma-D-glutamic acid) protein conjugates induce IgG antibodies in mice to the capsule of 
                    <E T="03">Bacillus anthracis</E>
                    : a potential addition to the 
                    <PRTPAGE P="55855"/>
                    anthrax vaccine. Proc Natl Acad Sci USA. 2003 Jul 22;100(15):8945-8950. 
                </P>
                <P>
                    <E T="03">Patent Status:</E>
                     U.S. Patent Application No. 10/559,825 filed 02 Dec 2005, claiming priority to 05 Jun 2003 (HHS Reference No. E-343-2002/0-US-04). 
                </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     Available for licensing. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     Peter A. Soukas, J.D.; 301/435-4646; 
                    <E T="03">soukasp@mail.nih.gov</E>
                    .
                </P>
                <HD SOURCE="HD1">
                    Improved Bacterial Host for Production of Anthrax Toxin Proteins and Vaccines: 
                    <E T="7462">Bacillus anthracis</E>
                     BH450 
                </HD>
                <P>
                    <E T="03">Description of Invention:</E>
                     Anthrax toxin has previously been made from various avirulent strains of 
                    <E T="03">Bacillus anthracis</E>
                    . The inventors have genetically engineered a new strain of 
                    <E T="03">B. anthracis</E>
                     with improved properties. The strain, designated BH450, is totally deficient in the ability to make spores and to produce a major extracellular protease designated Peptidase M4. The genetic lesions introduced are defined, true deletions, so there is no possibility of reversion. Inability to make spores assures that laboratories growing the strain will not become contaminated with the very stable anthrax spores. Inability to make peptidase M4 increases the stability of proteins such as anthrax toxin that are secreted to the culture medium. 
                </P>
                <P>
                    <E T="03">Applications and Modality: B. anthracis</E>
                     vaccine/prophylactic and therapeutic studies. 
                </P>
                <P>
                    <E T="03">Market:</E>
                     Research tool useful for biodefense/therapeutic studies. 
                </P>
                <P>
                    <E T="03">Development Status:</E>
                     The technology is a research tool. 
                </P>
                <P>
                    <E T="03">Inventors:</E>
                     Andrei Pomerantsev, Dana Hsu, Ramakrishnan Sitaraman, Craig Galloway, Violetta Kivovich, Stephen Leppla (NIAID). 
                </P>
                <P>
                    <E T="03">Publication:</E>
                     AP Pomerantsev 
                    <E T="03">et al.</E>
                     Genome engineering in Bacillus anthracis using Cre recombinase. Infect Immun. 2006 Jan;74(1):682-693. 
                </P>
                <P>
                    <E T="03">Patent Status:</E>
                     HHS Reference No. E-127-2007/0—Research Tool. 
                </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     This technology is not patented. The strain will be transferred through a Biological Materials License. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     Peter A. Soukas, J.D.; 301/435-4646; 
                    <E T="03">soukasp@mail.nih.gov</E>
                    . 
                </P>
                <P>
                    <E T="03">Collaborative Research Opportunity:</E>
                     The National Institute of Allergy and Infectious Diseases, Laboratory of Bacterial Diseases, is seeking statements of capability or interest from parties interested in collaborative research to further develop, evaluate, or commercialize 
                    <E T="03">Bacillus anthracis</E>
                     BH450 strain. Please contact Dr. Andrei P. Pomerantsev at phone 301/451-9817 and/or e-mail 
                    <E T="03">apomerantsev@niaid.nih.gov</E>
                     for more information. 
                </P>
                <HD SOURCE="HD1">
                    Monoclonal Antibodies That Neutralize 
                    <E T="7462">B. anthracis</E>
                     Protective Antigen (PA), Lethal Factor (LF) and Edema Factor (EF) 
                </HD>
                <P>
                    <E T="03">Description of Invention:</E>
                     Anthrax, whether resulting from natural or bioterrorist-associated exposure, is a constant threat to human health. The lethality of anthrax is primarily the result of the effects of anthrax toxin, which has 3 components: a receptor-binding protein known as “protective antigen” (PA) and 2 catalytic proteins known as “lethal factor” (LF) and “edema factor” (EF). Although production of an efficient anthrax vaccine is an ultimate goal, the benefits of vaccination can be expected only if a large proportion of the population at risk is immunized. The low incidence of anthrax suggests that large-scale vaccination may not be the most efficient means of controlling this disease. In contrast, passive administration of neutralizing human or chimpanzee monoclonal antibody to a subject at risk for anthrax or exposed to anthrax could provide immediate efficacy for emergency prophylaxis against or treatment of anthrax. 
                </P>
                <P>Four monoclonal antibodies (mAbs) against PA, three mAbs against LF and four mAbs specific for EF of anthrax were isolated from a phage display library generated from immunized chimpanzees. Two mAbs recognizing PA (W1 and W2), two anti-LF mAbs efficiently neutralized the cytotoxicity of lethal toxin in a macrophage lysis assay. One anti-EF mAb efficiently neutralized edema toxin in cell culture. All five neutralizing mAbs protected animals from anthrax toxin challenge. </P>
                <P>
                    <E T="03">Application:</E>
                     Prophylactics or therapeutics against 
                    <E T="03">B. anthracis</E>
                    . 
                </P>
                <P>
                    <E T="03">Developmental Status:</E>
                     Preclinical studies have been performed. 
                </P>
                <P>
                    <E T="03">Inventors:</E>
                     Zhaochun Chen, Robert Purcell, Suzanne Emerson, Stephen Leppla, Mahtab Moyeri (NIAID). 
                </P>
                <P>
                    <E T="03">Publication:</E>
                     Z Chen 
                    <E T="03">et al.</E>
                     Efficient neutralization of anthrax toxin by chimpanzee monoclonal antibodies against protective antigen. J Infect Dis. 2006 Mar 1;193(5):625-633. 
                </P>
                <P>
                    <E T="03">Patent Status:</E>
                     PCT Application No. PCT/US2008/054609 filed 21 Feb 2008, claiming priority to 23 Feb 2007 (HHS Reference No. E-123-2007/0-PCT-02); U.S. Patent Application No. 11/793,735 filed 22 Jun 2007 (HHS Reference No. E-146-2004/0-US-03) 
                </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     Available for exclusive or non-exclusive licensing. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     Peter A. Soukas, J.D.; 301/435-4646; 
                    <E T="03">soukasp@mail.nih.gov</E>
                    . 
                </P>
                <P>
                    <E T="03">Collaborative Research Opportunity:</E>
                     The National Institute of Allergy and Infectious Diseases, Laboratory of Infectious Diseases is seeking statements of capability or interest from parties interested in collaborative research to further develop, evaluate, or commercialize Chimpanzee/human neutralizing monoclonal antibodies against anthrax toxins. Please contact Dr. Robert Purcell at 301/496-5090 for more information. 
                </P>
                <SIG>
                    <DATED> Dated: September 18, 2008. </DATED>
                    <NAME>Richard U. Rodriguez, </NAME>
                    <TITLE>Director, Division of Technology Development and Transfer, Office of Technology Transfer, National Institutes of Health.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22608 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4140-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>National Institutes of Health </SUBAGY>
                <SUBJECT>Government-Owned Inventions; Availability for Licensing </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institutes of Health, Public Health Service, HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The inventions listed below are owned by an agency of the U.S. Government and are available for licensing in the U.S. in accordance with 35 U.S.C. 207 to achieve expeditious commercialization of results of federally-funded research and development. Foreign patent applications are filed on selected inventions to extend market coverage for companies and may also be available for licensing. </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Licensing information and copies of the U.S. patent applications listed below may be obtained by writing to the indicated licensing contact at the Office of Technology Transfer, National Institutes of Health, 6011 Executive Boulevard, Suite 325, Rockville, Maryland 20852-3804; telephone: 301/496-7057; fax: 301/402-0220. A signed Confidential Disclosure Agreement will be required to receive copies of the patent applications. </P>
                </ADD>
                <HD SOURCE="HD1">Inhibitors of the Plasmodial Surface Anion Channel as Antimalarials </HD>
                <P>
                    <E T="03">Description of Technology:</E>
                     The inventions described herein are antimalarial small molecule inhibitors of the plasmodial surface anion channel (PSAC), an essential nutrient acquisition ion channel expressed on human 
                    <PRTPAGE P="55856"/>
                    erythrocytes infected with malaria parasites. These inhibitors were discovered by high-throughput screening of chemical libraries and analysis of their ability to kill malaria parasites in culture. Two separate classes of inhibitors were found to work synergistically in combination against PSAC and killed malaria cultures at markedly lower concentrations than separately. These inhibitors have high affinity and specificity for PSAC and have acceptable cytotoxicity profiles. Preliminary 
                    <E T="03">in vivo</E>
                     testing of these compounds in a mouse malaria model is currently ongoing. 
                </P>
                <P>
                    <E T="03">Applications:</E>
                     Treatment of malarial infections. 
                </P>
                <P>
                    <E T="03">Advantages:</E>
                     Novel drug treatment for malarial infections; Synergistic effect of these compounds on PSAC. 
                </P>
                <P>
                    <E T="03">Development Status:</E>
                      
                    <E T="03">In vitro</E>
                     and 
                    <E T="03">in vivo</E>
                     data can be provided upon request. 
                </P>
                <P>
                    <E T="03">Market:</E>
                     Treatment of malarial infection. 
                </P>
                <P>
                    <E T="03">Inventor:</E>
                     Sanjay A. Desai (NIAID). 
                </P>
                <P>
                    <E T="03">Publications:</E>
                </P>
                <P>1. Kang M, Lisk G, Hollingworth S, Baylor SM, Desai SA. Malaria parasites are rapidly killed by dantrolene derivatives specific for the plasmodial surface anion channel. Mol. Pharmacol. 2005 Jul;68(1):34-40.   </P>
                <P>2. Desai SA, Bezrukov SM, Zimmerberg J. A voltage-dependent channel involved in nutrient uptake by red blood cells infected with the malaria parasite. Nature. 2000 Aug 31;406(6799):1001-1005. </P>
                <P>
                    <E T="03">Patent Status:</E>
                     U.S. Provisional Application No. 61/083,000 filed 23 Jul 2008 (HHS Reference No. E-202-2008/0-US-01). 
                </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     Available for exclusive or non-exclusive licensing. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     Kevin W. Chang, PhD; 301-435-5018; 
                    <E T="03">changke@mail.nih.gov</E>
                    . 
                </P>
                <P>
                    <E T="03">Collaborative Research Opportunity:</E>
                     The NIAID Office of Technology Development is seeking statements of capability or interest from parties interested in collaborative research to further develop, evaluate, or commercialize antimalarial drugs that target PSAC or other parasite-specific transporters. Please contact either Charles Rainwater or Dana Hsu at 301-496-2644 for more information. 
                </P>
                <HD SOURCE="HD1">Aerosolized Vaccines </HD>
                <P>
                    <E T="03">Description of Technology:</E>
                     Vaccine delivery to humans by mucosal routes may offer some operational and immunological advantages over intramuscular administration by needle-and-syringe. Potential targets include the oral, nasal, rectal conjunctival, and vaginal surfaces with the oral and nasal routes being the most practical to consider for infants, children and adults of both sexes. Needle-free delivery methods may improve compliance, reduce discomfort, and improve safety of vaccines; particularly in the developing world, needle-free delivery could mitigate the risk of blood-borne pathogen transmission by unsafe injection practices or inadequately sterilized equipment, and be easier and safer to deploy by non-medical personnel. 
                </P>
                <P>Mucosal vaccination may offer a potential immunological advantage of recruiting mucosal lymphoid tissues that are important in mediation of immune responses, particularly at the entry site for infectious pathogens. Optimally formulated and delivered antigens may elicit a variety of responses in these tissues including secretory IgA, serum IgG capable of neutralizing toxins or viruses, and cell-mediated immunity as measured by cytotoxic T-cell responses and cytokine production. </P>
                <P>In the case of respiratory delivery, specific particle sizes can target particular microenvironments within the lung. Efficient penetration of the lung parenchyma depends upon optimizing the size of the droplet in relation to the diameter of the respiratory airways. It has been recommended that school age children and adults be immunized with respiratory particles that are between 3 and 5 μm in diameter, since a larger particle cannot effectively penetrate deep into the lung. </P>
                <P>This application claims aerosolized immunogenic compositions comprising aerosolized immunogenic particles between 0.01 μm and 15 μm. The application also claims methods for delivering immunogenic compositions, methods for generating immune responses, and methods for treating infections by producing and administering aerosolized immunogenic compositions. More specifically, the invention claims replication-defective recombinant adenoviruses encoding human immunodeficiency virus (HIV), simian immunodeficiency virus (SIV) and tuberculosis (TB) genes delivered by aerosolization into the lung. The inventors have shown that this regimen induces very high, stable cellular immune responses localized to the lung, as well as humoral responses in the lung, systemically, and, importantly, at distal mucosal sites. This regimen may prove highly useful for vaccination against respiratory infections such as TB, influenza, and respiratory syncytial virus, and provide a platform for generating mucosal antibody responses against other pathogens. </P>
                <P>
                    <E T="03">Applications:</E>
                     Improved immunogenic compositions and vaccine formulations, delivery of viral vectors, plasmid DNA, proteins, and adjuvants. 
                </P>
                <P>
                    <E T="03">Development Status:</E>
                     Vaccines have been formulated and preclinical studies have been performed. 
                </P>
                <P>
                    <E T="03">Inventors:</E>
                     Mario Roederer and Srinivas Rao (NIAID). 
                </P>
                <P>
                    <E T="03">Patent Status:</E>
                     U.S. Provisional Application No. 61/038,534 filed 21 Mar 2008 (HHS Reference No. E-053-2008/0-US-01). 
                </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     Available for exclusive or non-exclusive licensing. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     Peter A. Soukas, J.D.; 301-435-4646; 
                    <E T="03">soukasp@mail.nih.gov</E>
                    . 
                </P>
                <HD SOURCE="HD1">
                    Use of Saccharides Cross-Reactive With 
                    <E T="7462">Bacillus anthracis</E>
                     Spore Glycoprotein as a Vaccine Against Anthrax 
                </HD>
                <P>
                    <E T="03">Description of Technology: Bacillus anthracis</E>
                     is a spore-forming bacterium that causes anthrax in humans and in other mammals. The glycoprotein BclA (Bacillus collagen-like protein of anthracis) is a major constituent of the exosporium, the outermost surface of 
                    <E T="03">B. anthracis</E>
                     spores. The glycosyl part of BclA is an oligosaccharide composed of 2-O-methyl-4-(3-hydroxy-3-methylbutanamido)-4,6-dideoxy-d-glucose, referred to as anthrose, and three rhamnose residues. A structure similar to anthrose, 4-(3-hydroxy-3-methylbutanamido)-4,6-dideoxy-d-glucose is found in the side chain of the capsular polysaccharide (CPS) of 
                    <E T="03">Shewanella</E>
                     spp. MR-4. Under certain growth conditions the bacteria produce a variant CPS lacking one methyl group on the hydroxybutyrate, 4-(3-hydroxybutanamido)-4,6-dideoxy-d-glucose. Contrary to anthrose, neither of the 
                    <E T="03">Shewanella</E>
                     CPSs is 2-O methylated. 
                </P>
                <P>
                    The inventors have found that both 
                    <E T="03">Shewanella</E>
                     CPS variants react with anti-
                    <E T="03">B. anthracis</E>
                     spore sera. The inventors have also found that these antisera reacted with flagellae of 
                    <E T="03">Pseudomonas syringae</E>
                    , reported to be glycosylated with a similar terminal saccharide, 4-(3-hydroxybutanamido)-4,6-dideoxy-2-O-methyl-d-glucose. Sera produced by immunization with 
                    <E T="03">Shewanella</E>
                     or 
                    <E T="03">P. syringae</E>
                     cells bound to 
                    <E T="03">B. anthracis</E>
                     spores but not to 
                    <E T="03">Bacillus cereus</E>
                     spores in a fluorescent microscopy assay. The inventors' experiments show that methylation of the anthrose at the O-2 of the sugar ring and at the C-3 of 3-hydroxybutyrate are not essential for induction of cross-reactive antibodies. 
                    <PRTPAGE P="55857"/>
                </P>
                <P>
                    The application claims the use of 
                    <E T="03">Shewanella</E>
                     CPS conjugates as a component of an anthrax vaccine. The application also claims the use of capsular polysaccharides from 
                    <E T="03">Shewanella</E>
                     and compounds from the flagella of 
                    <E T="03">Pseudomonas syringae</E>
                     for the development of anthrax vaccines. 
                </P>
                <P>
                    <E T="03">Application:</E>
                     Development of anthrax vaccines, diagnostics and therapeutics. 
                </P>
                <P>
                    <E T="03">Development Status:</E>
                     Conjugates have been synthesized and preclinical studies have been performed. 
                </P>
                <P>
                    <E T="03">Inventors:</E>
                     Joanna Kubler-Kielb (NICHD), Rachel Schneerson (NICHD), Haijing Hu (NIAID), Stephen H. Leppla (NIAID), John B. Robbins (NICHD), 
                    <E T="03">et al.</E>
                </P>
                <P>
                    <E T="03">Publication:</E>
                     Kubler-Kielb J.  et al.  Saccharides cross-reactive with 
                    <E T="03">Bacillus anthracis</E>
                     spore glycoprotein as an anthrax vaccine component. Proc Natl Acad Sci USA. 2008 Jun 24;105(25):8709-8712. This publication reports the preparation, characterization, and antibody responses to protein conjugates of the two variants of 
                    <E T="03">Shewanella</E>
                     CPS. Significantly, both conjugates induced antibodies that bound to both 
                    <E T="03">Shewanella</E>
                     CPS variants by ELISA and to 
                    <E T="03">B. anthracis</E>
                     spores, as detected by fluorescent microscopy. 
                </P>
                <P>
                    <E T="03">Patent Status:</E>
                     U.S. Provisional Application No. 61/066,509 filed 19 Feb 2008 (HHS Reference No. E-032-2008/0-US-01). 
                </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     Available for exclusive or non-exclusive licensing. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     Peter A. Soukas, J.D.; 301-435-4646; 
                    <E T="03">soukasp@mail.nih.gov.</E>
                </P>
                <HD SOURCE="HD1">Modified Sugar Substrates and Methods of Use </HD>
                <P>
                    <E T="03">Description of Technology:</E>
                     Glycans can be classified as linear or branched sugars. The linear sugars are the glycosaminoglycans comprising polymers of sulfated disaccharide repeat units that are O-linked to a core protein, forming a proteoglycan aggregate. The branched glycans are found as N-linked and O-linked sugars on glycoproteins or on glycolipids. These carbohydrate moieties of the linear and branched glycans are synthesized by a super family of enzymes, the glycosyltransferases (GTs), which transfer a sugar moiety from a sugar donor to an acceptor molecule. Although GTs catalyze chemically similar reactions in which a monosaccharide is transferred from an activated derivative, such as a UDP-sugar, to an acceptor, very few GTs bear similarity in primary structure. 
                </P>
                <P>Eukaryotic cells express several classes of oligosaccharides attached to proteins or lipids. Animal glycans can be N-linked via beta-GlcNAc to Asparagine (N-glycans), O-linked via UDP-GalNAc to Serine/Threonine (O-glycans), or can connect the carboxyl end of a protein to a phosphatidylinositol unit (GPI-anchors) via a common core glycan structure. Thus, there is potential to develop carbohydrate substrates comprising bioactive agents that can be used to produce glycoconjugates carrying sugar moieties with bioactive agents. Such glycoconjugates have many therapeutic and diagnostic uses, e.g. in labeling or targeted delivery. Further, such glycoconjugates can be used in the assembly of bio-nanoparticles to develop targeted-drug delivery systems or contrast agents for medical uses. </P>
                <P>
                    This application claims methods and compositions for making and using functionalized sugars. Also claimed in the application are methods for forming a wide variety of products at a cell or in an 
                    <E T="03">in vitro</E>
                     environment. More specifically, the claimed compositions of the invention comprise a sugar nucleotide and one or more functional groups. 
                </P>
                <P>
                    <E T="03">Applications:</E>
                     Production of therapeutic or diagnostic glycoconjugates, assembly of bio-nanoparticles, development of contrast agents. 
                </P>
                <P>
                    <E T="03">Development Status:</E>
                     Enzymes have been synthesized and initial studies have been performed. 
                </P>
                <P>
                    <E T="03">Inventors:</E>
                     Pradman K. Qasba and Maria R. Manzoni (NCI). 
                </P>
                <P>
                    <E T="03">Publications:</E>
                </P>
                <P>1. B Ramakrishnan  et al.  Applications of glycosyltransferases in the site-specific conjugation of biomolecules and the development of a targeted drug delivery system and contrast agents for MRI. Expert Opin Drug Deliv. 2008 Feb;5(2):149-153. Review. </P>
                <P>2. PK Qasba  et al.  Site-specific linking of biomolecules via glycan residues using glycosyltransferases. Biotechnol Prog. 2008 May-Jun;24(3):520-526. </P>
                <P>
                    <E T="03">Patent Status:</E>
                     U.S. Patent Application No. 61/027,782 filed 11 Feb 2008 (HHS Reference No. E-016-2008/0-US-01). 
                </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     Available for exclusive or non-exclusive licensing. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     Peter A. Soukas, J.D.; 301-435-4646; 
                    <E T="03">soukasp@mail.nih.gov</E>
                    . 
                </P>
                <P>
                    <E T="03">Collaborative Research Opportunity:</E>
                     The National Cancer Institute's Nanobiology Program is seeking statements of capability or interest from parties interested in collaborative research to further develop, evaluate, or commercialize the synthesis of UDP derivatives of C2 modified galactose for use as donor substrates for glycosyltransferases. Please contact John D. Hewes, Ph.D. at 301-435-3121 or 
                    <E T="03">hewesj@mail.nih.gov</E>
                     for more information. 
                </P>
                <HD SOURCE="HD1">Immunogenic Peptides Against Influenza Virus </HD>
                <P>
                    <E T="03">Description of Technology:</E>
                     The invention described herein are peptides and polypeptides derived from the HA, NA, PB2, PB1, PA, M1, M2, NP, NS1, and NS2 proteins of influenza virus that elicit immunogenic responses; particularly neutralizing antibodies, against human and avian influenza strains H1N1, H3N2, H5N1 and H7N7. Materials in the form of immunogenic compositions including these peptides and polypeptides can also be in-licensed along with the patent rights. Pharmaceutical compositions including these peptides and polypeptides with or without adjuvants are within the scope of the invention. The inventors are currently investigating the vaccine potential of specific peptides and polypeptides. 
                </P>
                <P>
                    <E T="03">Applications:</E>
                </P>
                <P>• Vaccines against influenza virus infection; </P>
                <P>• Diagnostics for the detection of influenza virus infection; and </P>
                <P>• Generation of influenza virus specific antibodies. </P>
                <P>
                    <E T="03">Advantages:</E>
                </P>
                <P>• Peptides can be expressed in a number of different expression systems; and </P>
                <P>• Peptides were identified based on the specificity of antibodies derived from human and avian influenza virus infected individuals. </P>
                <P>
                    <E T="03">Development Status: In vitro</E>
                     data can be provided upon request. 
                </P>
                <P>
                    <E T="03">Market:</E>
                </P>
                <P>• Preventative or treatment for influenza virus infection; and </P>
                <P>• Diagnostic for influenza virus infection. </P>
                <P>
                    <E T="03">Inventors:</E>
                     Hana Golding and Surender Khurana (FDA). 
                </P>
                <P>
                    <E T="03">Publications:</E>
                </P>
                <P>1. Pandemic Influenza preparedness: New molecular tools for evaluation of influenza vaccines and identification of serological epitopes for avian influenza diagnostic assays at “Options for the Control of Influenza VI” June 17-23, 2007, Toronto, Canada. (oral presentation) </P>
                <P>2. Pandemic Influenza preparedness: Identification of serological epitopes for use in development of broadly cross-reactive influenza vaccines at “National Foundation for Infectious Diseases—11th Annual Conference on Vaccine Research”, Baltimore: May 5-7, 2008. (oral presentation). </P>
                <P>
                    3. Analysis of antibody repertoires in H5N1 infected and vaccinated 
                    <PRTPAGE P="55858"/>
                    individuals using influenza whole genome phage display at “Immunobiology and Pathogenesis of Influenza Infection”, Atlanta: June 1-3, 2008. (poster presentation). 
                </P>
                <P>
                    <E T="03">Patent Status:</E>
                     International Patent Application PCT/US2008/067001 filed 13 Jun 2008 (HHS Reference No. E-236-2007/3-PCT-01). 
                </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     Available for exclusive or non-exclusive licensing. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     Kevin W. Chang, Ph.D.; 301-435-5018; 
                    <E T="03">changke@mail.nih.gov</E>
                    . 
                </P>
                <P>
                    <E T="03">Collaborative Research Opportunity:</E>
                     The FDA, Center for Biologics Evaluation and Research (CBER), Division of Viral Products, is seeking statements of capability or interest from parties interested in collaborative research to further develop, evaluate, or commercialize these peptides as vaccine candidates or diagnostics. Please contact Alice Welch at 
                    <E T="03">alice.welch@fda.hhs.gov</E>
                     or 301-827-0359 for more information. 
                </P>
                <HD SOURCE="HD1">A Rapid Ultrasensitive Assay for Detecting Prions Based on the Seeded Polymerization of Recombinant Normal Prion Protein (rPrP-sen) </HD>
                <P>
                    <E T="03">Description of Technology:</E>
                     Prion diseases are neurodegenerative diseases of great public concern because humans may be infected from hoofed animals used as food, food products such as milk, or blood products. Currently available tests for disease-causing prions are either incapable of detecting low concentrations of prions and must be used post-mortem or are incapable of detecting low concentrations of prions economically or accurately. This technology enables rapid and economical detection of sub-lethal concentrations of prions by using recombinant, normal, prion protein (rPrP-sen) as a marker or indicator of infectious prions in a sample. Specifically, prions (contained in a sample) seed the polymerization of rPrP-sen, and polymerized rPrP-sen is detected as an amplified indicator of prions in the sample. This assay differs from the protein-misfolding cyclic amplification assay (PMCA) because it enables the effective use of rPrP-sen and does not require multiple amplification cycles unless a higher degree of sensitivity is required. It is anticipated that this technology can be combined with additional prion-detection technologies to further improve the sensitivity of the assay. In its current embodiment, this assay has been used to detect prions in brain tissue or cerebral spinal fluid (CSF) from humans (variant CJD), sheep (scrapie), and hamsters (scrapie). 
                </P>
                <P>
                    <E T="03">Advantages:</E>
                </P>
                <P>• Uses a consistent, concentrated source of normal prion protein (rPrP-sen) </P>
                <P>• Prions are detectable to low levels after a single amplification round </P>
                <P>• May be combined with complimentary detection technologies to improve sensitivity </P>
                <P>• Demonstrated to be effective at detecting prions from different species </P>
                <P>• May be applicable to blood products </P>
                <P>• Economical </P>
                <P>
                    <E T="03">Applications:</E>
                </P>
                <P>• A test for live animals or food products </P>
                <P>• A human diagnostic for early detection of prion diseases </P>
                <P>• Monitor for effectiveness of treatments or disease progression </P>
                <P>
                    <E T="03">Inventors:</E>
                     Byron W. Caughey, Ryuichiro Atarashi, Roger A. Moore, and Suzette A. Priola (NIAID). 
                </P>
                <P>
                    <E T="03">Related Publications:</E>
                </P>
                <P>1. R Atarashi et al. Simplified ultrasensitive prion detection by recombinant PrP conversion with shaking. Nat Methods 2008 Mar;5(3):211-212. </P>
                <P>2. R Atarashi  et al.  Ultrasensitive detection of scrapie prion protein using seeded conversion of recombinant prion protein. Nat Methods 2007 Aug;4(8):645-650. </P>
                <P>
                    <E T="03">Patent Status:</E>
                </P>
                <P>• PCT Application No. PCT/US2008/070656 filed 21 Jul 2008 (HHS Reference No. E-109-2007/1-PCT-01). </P>
                <P>• U.S. Application No. 12/177,012 filed 21 Jul 2008 (HHS Reference No. E-109-2007/1-US-02). </P>
                <P>
                    <E T="03">Licensing Status:</E>
                     Available for exclusive and non-exclusive licensing. 
                </P>
                <P>
                    <E T="03">Licensing Contact:</E>
                     RC Tang, JD, LLM; 301-435-5031; 
                    <E T="03">tangrc@mail.nih.gov</E>
                    . 
                </P>
                <P>
                    <E T="03">Collaborative Research Opportunity:</E>
                     The NIAID Laboratory of Persistent Viral Diseases, TSE/Prion Biochemistry Section, is seeking statements of capability or interest from parties interested in collaborative research to further develop, evaluate, or commercialize this technology. Please contact Rosemary Walsh at 301-451-3528 or 
                    <E T="03">rcwalsh@niaid.nih.gov</E>
                    . 
                </P>
                <SIG>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>Richard U. Rodriguez, </NAME>
                    <TITLE>Director, Division of Technology Development and Transfer, Office of Technology Transfer, National Institutes of Health.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22610 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>National Institutes of Health </SUBAGY>
                <SUBJECT>National Institute of Diabetes and Digestive and Kidney Diseases; Amended Notice of Meeting </SUBJECT>
                <P>
                    Notice is hereby given of a change in the meeting of the National Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis Panel, October 17, 2008, 2:30 p.m. to 3:30 p.m., National Institutes of Health, Two Democracy Plaza, 6707 Democracy Boulevard, Bethesda, MD 20892 which was published in the 
                    <E T="04">Federal Register</E>
                     on September 11, 2008, 73 FR 0177. 
                </P>
                <P>This meeting will be held October 22, 2008 instead of October 17, 2008. The meeting is closed to the public. </P>
                <SIG>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>Jennifer Spaeth, </NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22604 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>National Institutes of Health </SUBAGY>
                <SUBJECT>National Institute of Diabetes and Digestive and Kidney Diseases; Notice of Closed Meetings </SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. Appendix 2), notice is hereby given of the following meetings. </P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy. </P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis  Panel, Molecular Therapy Core Centers. 
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         October 21, 2008. 
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m. 
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications. 
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Bethesda Marriott Suites, 6711 Democracy Boulevard, Bethesda, MD 20817. 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Michele L. Barnard, PhD, Scientific Review Officer, Review Branch, DEA, NIDDK,  National Institutes of Health,  Room 753, 6707 Democracy Boulevard, 
                        <PRTPAGE P="55859"/>
                         Bethesda, MD 20892-5452, (301) 594-8898, 
                        <E T="03">barnardm@extra.niddk.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis  Panel, Translational Research. 
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         October 29, 2008. 
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m. 
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications. 
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Bethesda Marriott, 5151 Pooks Hill Road, Bethesda, MD 20814. 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Michele L. Barnard, PhD, Scientific Review Officer, Review Branch, DEA, NIDDK,  National Institutes of Health,  Room 753, 6707 Democracy Boulevard,  Bethesda, MD 20892-5452, (301) 594-8898, 
                        <E T="03">barnardm@extra.niddk.nih.gov</E>
                        . 
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis  Panel, Gastrointestinal Programs. 
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         November 13, 2008.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         7:45 a.m. to 5 p.m. 
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications. 
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Holiday Inn National Airport, 2650 Jefferson Davis Highway, Arlington, VA 22202. 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Michael W. Edwards, PhD, Scientific Review Officer, Review Branch, DEA, NIDDK,  National Institutes of Health,  Room 750, 6707 Democracy Boulevard,  Bethesda, MD 20892-5452, (301) 594-8886, 
                        <E T="03">edwardsm@extra.niddk.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.847, Diabetes, Endocrinology and Metabolic Research; 93.848, Digestive Diseases and Nutrition Research; 93.849, Kidney Diseases, Urology and Hematology Research,  National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>Jennifer Spaeth, </NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22605 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4140-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>National Institutes of Health </SUBAGY>
                <SUBJECT>National Institute of Mental Health; Notice of Closed Meetings </SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. Appendix 2), notice is hereby given of the following meetings. </P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy. </P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Mental Health Special Emphasis Panel, ITVC Conflicts. 
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         October 15, 2008. 
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10 a.m. to 12 p.m. 
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications. 
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Neuroscience Center, 6001 Executive Boulevard,  Rockville, MD 20852.  (Telephone Conference Call) 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Enid Light, PhD,  Scientific Review Administrator,  Division of Extramural Activities,  National Institute of Mental Health, NIH,  Neuroscience Center,  6001 Executive Boulevard, Room 6132, MSC 9608,  Bethesda, MD 20852-9608,  301-443-0322, 
                        <E T="03">elight@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Mental Health Special Emphasis Panel, National Research Service Award (NRSA) Institutional Research Training Grants. 
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         October 20, 2008. 
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m. 
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications. 
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Embassy Suites Hotel, 4300 Military Road, Washington, DC 20015. 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Vinod Charles, PhD, Scientific Review Administrator, Division of Extramural Activities,  National Institute of Mental Health, NIH,  Neuroscience Center,  6001 Executive Blvd., Room 6151, MSC 9606,  Bethesda, MD 20892-9606,  301-443-1606. 
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Mental Health Special Emphasis Panel, Pathway to Independence (PI) Award. 
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         October 28, 2008.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m. 
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications. 
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Hyatt Regency Bethesda, One Bethesda Metro Center, 7400 Wisconsin Avenue, Bethesda, MD 20814. 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Megan Libbey, PhD, Scientific Review Administrator, Division of Extramural Activities,  National Institute of Mental Health, NIH,  Neuroscience Center,  6001 Executive Blvd., Room 6148, MSC 9609,  Rockville, MD 20852,  301-402-6807, 
                        <E T="03">libbeym@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Mental Health Special Emphasis Panel  Aids Applications. 
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         November 15, 2008. 
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10 a.m. to 12 p.m. 
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications. 
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Neuroscience Center, 6001 Executive Boulevard,  Rockville, MD 20852.  (Telephone Conference Call) 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Enid Light, PhD,  Scientific Review Administrator,  Division of Extramural Activities,  National Institute of Mental Health, NIH,  Neuroscience Center,  6001 Executive Boulevard, Room 6132, MSC 9608,  Bethesda, MD 20852-9608,  301-443-0322, 
                        <E T="03">elight@mail.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.242, Mental Health Research Grants; 93.281, Scientist Development Award, Scientist Development Award for Clinicians, and Research Scientist Award; 93.282, Mental  Health National Research Service Awards for Research Training, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>Jennifer Spaeth, </NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22607 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4140-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBJECT>National Institutes of Health </SUBJECT>
                <SUBJECT>Prospective Grant of Exclusive License: Use of Benztropinamine Analogs To Treat Psychiatric and Neurological Disorders </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institutes of Health, Public Health Service, HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is notice, in accordance with 35 U.S.C. 209(c)(1) and 37 CFR Part 404.7(a)(1)(i), that the National Institutes of Health, Department of Health and Human Services, is contemplating the grant of an exclusive patent license to practice the inventions embodied in U.S. Patent Application No. 60/689,746, filed June 10, 2005, now abandoned [HHS Ref. No. E-089-2005/0-US-01]; PCT Patent Application No. PCT/US2006/22401, filed June 7, 2006, now abandoned [HHS Ref. No. E-089-2005/0-US-02]; U.S. Patent Application No. 11/917,036, filed December 10, 2007 [HHS Ref. No. E-089-2005/0-US-03]; European Patent Application No. 06772641.4, filed December 7, 2007, which published as 1888064 on February 20, 2008 [HHS Ref. No. E-089-2005/0-EP-04]; Australian Patent Application No. 2006258035, filed November 30, 2007 [HHS Ref. No. E-089-2005/0-AU-05]; Japanese Patent Application No. 2008-515947, filed December 7, 2007 [HHS Ref. No. E-089-2005/0-JP-06]; and Canadian Patent Application No. 2609577, filed November 23, 2007 [HHS Ref. No. E-089-2005/0-CA-07], all of which are entitled “Benztropinamine Analogs as Dopamine Uptake Inhibitors” (Inventors: Amy Newman and Jonathan Katz, NIDA) to Shire LLC, having an office in at least Basingstoke, United Kingdom. The patent rights in these inventions have been assigned to the United States of America. </P>
                    <P>
                        The prospective exclusive license territory may be worldwide, and the field of use may be limited to the use of benztropinamine analogs, 
                        <PRTPAGE P="55860"/>
                        specifically, compounds derived from Formula I, wherein B is NR 
                        <SU>4</SU>
                         and wherein R 
                        <SU>4</SU>
                         is not CH
                        <E T="52">3</E>
                         (methyl group) to treat psychiatric and neurological disorders. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Only written comments and/or applications for a license which are received by the NIH Office of Technology Transfer on or before November 25, 2008 will be considered. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Requests for copies of the patent application, inquiries, comments, and other materials relating to the contemplated exclusive license should be directed to: Charlene A. Sydnor, Ph.D., Technology Licensing Specialist, Office of Technology Transfer, National Institutes of Health, 6011 Executive Boulevard, Suite 325, Rockville, MD 20852-3804; Telephone: (301) 435-4689; Facsimile: (301) 402-0220; e-mail: 
                        <E T="03">sydnorc@mail.nih.gov</E>
                        . 
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This technology relates to the synthesis of novel dopamine transport inhibitors and their use to treat mental disorders. The inventors developed benztropinamine analogs by replacing the benzhydrylether moiety of benztropine and its analogs with the isosteric benzhydrylamine system in order to produce more stable compounds with increased solubility and bioavailability for improved therapeutic formulation and utility. These compounds have a high affinity for the dopamine transporter and inhibit dopamine uptake, but do not produce a significant stimulation of locomotor activity or cocaine-like subjective effects in a drug discrimination model. These compounds are useful for the treatment of mental disorders such as conduct disorders, alcohol addiction, tobacco addiction, nicotine addiction, drug addiction, sleep disorders, inhalation disorders, Parkinsonism including Parkinson's disease, female and male orgasmic disorders, female and male sexual arousal disorders, hypoactive sexual desire disorders, and anxiety and/or depression disorders. These compounds are also useful as imaging probes for detecting cocaine binding sites, as well as monitoring or diagnosing Parkinson's disease. </P>
                <P>The prospective exclusive license will be royalty bearing and will comply with the terms and conditions of 35 U.S.C. 209 and 37 CFR Part 404.7. The prospective exclusive license may be granted unless within sixty (60) days from the date of this published notice, the NIH receives written evidence and argument that establishes that the grant of the license would not be consistent with the requirements of 35 U.S.C. 209 and 37 CFR Part 404.7. </P>
                <P>Applications for a license in the field of use filed in response to this notice will be treated as objections to the grant of the contemplated exclusive license. Comments and objections submitted to this notice will not be made available for public inspection and, to the extent permitted by law, will not be released under the Freedom of Information Act, 5 U.S.C. 552. </P>
                <SIG>
                    <DATED>Dated: September 17, 2008. </DATED>
                    <NAME>Richard U. Rodriguez, </NAME>
                    <TITLE>Director, Division of Technology Development and Transfer, Office of Technology Transfer, National Institutes of Health.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22611 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY </AGENCY>
                <DEPDOC>[Docket No. DHS-2008-0102] </DEPDOC>
                <SUBJECT>National Protection and Programs Directorate; Designation of the Sector-Specific Agency for the Critical Manufacturing Sector and Resulting Changes in the National Infrastructure Protection Plan </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Protection and Programs Directorate, Office of Infrastructure Protection, DHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Sector Specific Agency designation for Critical Manufacturing. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice informs the public that the Secretary, Department of Homeland Security (DHS), has designated the DHS Office of Infrastructure Protection (IP) as the Sector-Specific Agency (SSA) for the Critical Manufacturing Sector under the National Infrastructure Protection Plan (NIPP). IP will now move forward with the organization and coordination processes identified in the NIPP for establishing a new critical infrastructure and key resources (CIKR) sector. These initial steps will include establishing Government and Sector Coordinating Councils, which will begin the process of full integration into the CIKR Sector Partnership, implementation of the NIPP Risk Management Framework and development of the Critical Manufacturing Sector Specific Plan. </P>
                    <P>This designation also includes language changes to the NIPP identifying the new sector, which will take affect immediately and remain in effect until the NIPP is rewritten and published in 2009. These changes will include adding the Critical Manufacturing sector and its SSA to those sections of the NIPP where sectors and their SSAs are listed, referenced, or described, and amending the last sentence of the definition of “Sector” in the Glossary to read, “The NIPP addresses the 17 CIKR sectors enumerated in HSPD-7 and any additional sectors created by the Secretary of Homeland Security pursuant to HSPD-7.” </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Larry L. May, Deputy Director, NIPP Program Office, Partnership and Outreach Division, Office of Infrastructure Protection, National Protection and Programs Directorate, Department of Homeland Security, Washington, DC 20528, 703-235-3648 or 
                        <E T="03">NIPP@dhs.gov</E>
                        . 
                    </P>
                    <SIG>
                        <DATED>Dated: September 17, 2008. </DATED>
                        <NAME>R. James Caverly, </NAME>
                        <TITLE>Director, Partnership and Outreach Division, Office of Infrastructure Protection, Department of Homeland Security.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22609 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4410-10-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY </AGENCY>
                <SUBAGY>U.S. Customs and Border Protection </SUBAGY>
                <SUBJECT>Notice of Issuance of Final Determination Concerning Certain Mesh Dressing </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Customs and Border Protection, Department of Homeland Security. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of final determination. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document provides notice that U.S. Customs and Border Protection (“CBP”) has issued a final determination concerning the country of origin of certain mesh dressing known as Tegaderm
                        <SU>TM</SU>
                         Ag Mesh Dressing. Based upon the facts presented, CBP has concluded in the final determination that the United States is the country of origin of the Tegaderm
                        <SU>TM</SU>
                         Ag Mesh Dressing for purposes of U.S. Government procurement. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The final determination was issued on September 22, 2008. A copy of the final determination is attached. Any party-at-interest, as defined in 19 CFR 177.22(d), may seek judicial review of this final determination within October 27, 2008. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Cynthia Reese, Valuation and Special Programs Branch, Regulations and Rulings, Office of International Trade (202-572-8812). </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given that on September 22, 2008, pursuant to subpart B of part 177, Customs and Border Protection (CBP) 
                    <PRTPAGE P="55861"/>
                    Regulations (19 CFR Part 177, Subpart B), CBP issued a final determination concerning the country of origin of Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressing which may be offered to the United States Government under an undesignated government procurement contract. This final determination, in HQ H035776, was issued at the request of 3M Company under procedures set forth at 19 CFR Part 177, Subpart B, which implements Title III of the Trade Agreements Act of 1979, as amended (19 U.S.C. 2511-18). In the final determination, CBP has concluded that, based upon the facts presented, Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressing which is produced in the United States from foreign nonwoven cotton fabric is a product of the United States for purposes of U.S. Government procurement. 
                </P>
                <P>
                    Section 177.29, CBP Regulations (19 CFR 177.29), provides that notice of final determinations shall be published in the 
                    <E T="04">Federal Register</E>
                     within 60 days of the date the final determination is issued. Section 177.30, CBP Regulations (19 CFR 177.30), provides that any party-at-interest, as defined in 19 CFR 177.22(d), may seek judicial review of a final determination within 30 days of publication of such determination in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <SIG>
                    <DATED>Dated: September 22, 2008. </DATED>
                    <NAME>Jeremy Baskin, </NAME>
                    <TITLE>Acting Executive Director, Regulations and Rulings, Office of International Trade.</TITLE>
                </SIG>
                <HD SOURCE="HD3">HQ H035776 </HD>
                <DATE>September 22, 2008 </DATE>
                <FP SOURCE="FP-2">VAL-2 OT:RR:CTF:VS H035776 CMR </FP>
                <FP SOURCE="FP-2">CATEGORY: Marking </FP>
                <FP SOURCE="FP-2">TARIFF NO.: 3005.90 </FP>
                <FP SOURCE="FP-2">Mr. Matthew Fuller, Trade Compliance Department, 3M Company 3M Center, Building 225-4S-18, St. Paul, MN 55144-1000 </FP>
                <FP SOURCE="FP-2">
                    RE: Origin determination of Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressing for purposes of Government Procurement 
                </FP>
                <P>
                    Dear Mr. Fuller: This ruling is in response to your request of August 6, 2008, for a determination as to the country of origin of Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressing which is sold by 3M. You indicate that 3M is the importer of record of the nonwoven cotton fiber fabric used in the production of Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressing and, as such, has standing to request this ruling pursuant to 19 CFR 177.23(a) and § 177.24. 
                </P>
                <FP>FACTS: </FP>
                <P>
                    3M imports nonwoven cotton fiber fabric which is produced by and purchased from suppliers outside the United States. At the time of importation, the nonwoven cotton fabric is in large (Jumbo) rolls and has no finishing on it. It is classifiable as a nonwoven fabric of heading 5603 of the Harmonized Tariff Schedule of the United States (HTSUS).
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Heading 5603, HTSUS, provides for “Nonwovens, whether or not impregnated, coated, covered or laminated.” We note that you indicate a belief that the nonwoven cotton fabric which is imported by 3M is classifiable in subheading 5603.12, HTSUS, however, that provision provides for nonwovens of man-made filaments. The correct subheading is 5603.92.00, HTSUS, which provides for nonwovens of other than man-made filaments, weighing more than 25 g/m
                        <SU>2</SU>
                         but not more than 70 g/m
                        <SU>2</SU>
                        .
                    </P>
                </FTNT>
                <P>
                    After importation, the nonwoven cotton fabric is processed so as to be impregnated with silver sulfate which is manufactured in the United States. The impregnated fabric is then slit to desired widths, cut to size (length), and packaged into pouches which are then sealed. The pouches are labeled, packed into cases, and then sent for sterilization. The finished Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressings are then ready for retail sale in the United States or for export. 
                </P>
                <P>The silver sulfate with which the nonwoven fabric is impregnated is the “active ingredient” in the product. It is the silver sulfate which causes wounds to heal quicker. On its web site, 3M claims with regard to this product: “Silver sulfate releases as silver ions in the dressing creates an effective antimicrobial barrier for up to 7 days.” It is further claimed that these silver ions reduce the number of bacteria and yeast. </P>
                <P>
                    You assert that the finished dressings are products of the United States under application of the rules of origin for textile and apparel products set forth in the Customs and Border Protection (CBP) regulations at 19 CFR 102.21 (implementing 19 U.S.C. 3592). In the alternative, you assert that the finished dressings are products of the United States under the traditional substantial transformation test set forth in 19 U.S.C. 2518.
                    <SU>2</SU>
                    <FTREF/>
                     The CBP regulations implementing 19 U.S.C. 2515(b)(1), which provides that the Secretary of the Treasury shall issue advisory rulings and final determinations on the origin of an article under the provisions of 19 U.S.C. 2511 through 2518, are found at 19 CFR 177.21 through 177.31. 19 U.S.C. 2511 through 2518 implement Title III of the Trade Agreements Act of 1979, as amended, which effectuated U.S. obligations under the Agreement on Government Procurement.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         19 U.S.C. 2518(4)(B) defines the rule of origin for purposes of Government Procurement.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         See Title III, Trade Agreements Act of 1979, as amended, and the Agreement on Government Procurement, General Agreement on Tariffs and Trade, 12 April 1979, Geneva (GATT 1979).
                    </P>
                </FTNT>
                <FP>ISSUE: </FP>
                <P>
                    What is the country of origin of the finished Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressings for purposes of U.S. Government procurement? 
                </P>
                <FP>LAW AND ANALYSIS: </FP>
                <P>
                    Pursuant to Subpart B of Part 177, 19 CFR 177.21 
                    <E T="03">et seq.</E>
                    , which implements Title III, Trade Agreements Act of 1979, as amended (19 U.S.C. 2511-2518), CBP issues country of origin advisory rulings and final determinations as to whether an article is or would be a product of a designated country or instrumentality for the purpose of granting waivers of certain “Buy American” restrictions in U.S. law or practice for products offered for sale to the U.S. Government. 
                </P>
                <P>
                    Initially, we note that 3M is permitted to request this ruling as it is the importer of record and thus meets the requirements of 19 CFR 177.23(a) and 177.24. In addition, 3M meets the definition of a party-at-interest as defined at 19 CFR 177.22(d) and is entitled to a final determination as to the country of origin of the finished Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressings produced from imported nonwoven cotton fabric. 
                </P>
                <P>The rule of origin set forth in 19 U.S.C. 2518(4)(B) states:</P>
                <EXTRACT>
                    <P>An article is a product of a country or instrumentality only if (i) it is wholly the growth, product, or manufacture of that country or instrumentality, or (ii) in the case of an article which consists in whole or in part of materials from another country or instrumentality, it has been substantially transformed into a new and different article of commerce with a name, character, or use distinct from that of the article or articles from which it was so transformed.</P>
                    <P>
                        <E T="03">See also</E>
                         19 CFR 177.22(a) defining “country of origin” in identical terms. 
                    </P>
                </EXTRACT>
                <P>
                    In rendering advisory rulings and final determinations for purposes of U.S. Government procurement, CBP applies the provisions of Subpart B of Part 177 consistent with the Federal Procurement Regulations. See 19 CFR 177.21. In this regard, CBP recognizes that the Federal Procurement Regulations restrict the U.S. Government's purchase of products to U.S.-made or designated country end products for acquisitions subject to the TAA. See 48 CFR 25.403(c)(1). The Federal Procurement Regulations define “U.S.-made end product” as: * * * an article that is mined, produced, or manufactured in the United States or 
                    <PRTPAGE P="55862"/>
                    that is substantially transformed in the United States into a new and different article of commerce with a name, character, or use distinct from that of the article or articles from which it was transformed. 48 CFR 25.003. Therefore, the question presented in this final determination is whether, as a result of the operations performed in the United States, the nonwoven cotton fabric is substantially transformed into a product of the United States. 
                </P>
                <P>The rules of origin for textile products for purposes of the customs laws and the administration of quantitative restrictions are set forth in 19 U.S.C. 3592. These provisions are implemented in the CBP Regulations at 19 CFR 102.21. The rules set forth in § 3592 apply to textile and apparel products, unless otherwise provided for by statute. The rule of origin in § 2518(4)(B) is a rule of origin otherwise provided for by statute, however, it is a general rule, whereas § 3592 is specific to textile products. Section 3592 has been described as Congress's expression of substantial transformation as it relates to textile products. </P>
                <P>
                    The rules of origin in 19 U.S.C. 3592 are implemented in the CBP Regulations in 19 CFR 102.21. The imported product is a nonwoven textile fabric. The finished product, Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressings, is also a textile product as defined by 19 CFR 102.21(b)(5). Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressings are classified in subheading 3005.90, HTSUS, which provides for “Wadding, gauze, bandages and similar articles (for example, dressings, adhesive plasters, poultices), impregnated or coated with pharmaceutical substances or put up in forms or packings for retail sale for medical, surgical, dental or veterinary purposes” other than adhesive dressings and other articles having an adhesive layer. 
                </P>
                <P>As the finished dressing is produced by processing in more than one country, its origin cannot be determined by application of § 102.21(c)(1), wholly obtained or produced rule, and resort must be made to § 102.21(c)(2). Section 102.21(c)(2) states that the origin of a good is the country “in which each foreign material incorporated in that good underwent an applicable change in tariff classification, and/or met any other requirement, specified for the good in paragraph (e) of [102.21].” Section 102.21(e) provides in pertinent part: </P>
                <EXTRACT>
                    <P>(1) The following rules will apply for purposes of determining the country of origin of a textile or apparel product under paragraph (c)(2) of this section: </P>
                    <FP>3005.90 If the good contains pharmaceutical substances, a change to subheading 3005.90 from any other heading; * * *.</FP>
                </EXTRACT>
                <FP>
                    The material of foreign origin in this case is the nonwoven cotton fabric classifiable in heading 5603, HTSUS. The processing in the United States causes the foreign origin material to make a tariff shift from heading 5603 to subheading 3005.90, HTSUS. Therefore, by application of the rules set forth in 19 CFR 102.21, the finished Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressings are products of the United States for purposes of government procurement. 
                </FP>
                <FP>HOLDING: </FP>
                <P>
                    Based on the facts and analysis set forth above, the finished Tegaderm
                    <SU>TM</SU>
                     Ag Mesh Dressings are products of the United States for the purpose of government procurement. 
                </P>
                <P>
                    Notice of this final determination will be given in the 
                    <E T="04">Federal Register</E>
                    , as required by 19 CFR § 177.29. Any party-at-interest other than the party which requested this final determination may request, pursuant to 19 CFR 177.31, that CBP reexamine the matter anew and issue a new final determination. Pursuant to 19 CFR 177.30, any party-at-interest may, within 30 days after publication of the 
                    <E T="04">Federal Register</E>
                     notice referenced above, seek judicial review of this final determination before the Court of International Trade. 
                </P>
                <EXTRACT>
                    <FP>  Sincerely, </FP>
                    <FP>Jeremy Baskin </FP>
                    <FP>
                        <E T="03">Acting Executive Director</E>
                    </FP>
                    <FP>
                        <E T="03">Regulations and Rulings</E>
                    </FP>
                    <FP>
                        <E T="03">Office of International Trade</E>
                    </FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22683 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 9111-14-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Office of the Secretary </SUBAGY>
                <SUBJECT>Notice of Proposed New Information Collection for Donor Certification Form </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Conservation, Partnerships &amp; Management Policy, Assistant Secretary—Policy, Management and Budget, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Office of Conservation, Partnerships &amp; Management Policy announces a proposed public information collection and seeks public comments on the provisions thereof. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Consideration will be given to all comments received by November 25, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Written comments and recommendations on the proposed information collection should be sent to the Office of Conservation, Partnerships &amp; Management Policy, Beth Duff, 1849 C St., NW., MS 5123 MIB, Washington, DC 20240. Individuals providing comments should reference Donor Certification Form. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request more information on this proposed information collection or to obtain a copy of the proposal and associated collection instrument, please write to the above address, or call Beth Duff, on 202-208-5904, or e-mail her at 
                        <E T="03">beth_duff@ios.doi.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Abstract </HD>
                <P>
                    Office of Management and Budget (OMB) regulations at 5 CFR 1320, which implement the Paperwork Reduction Act of 1995 (Pub. L. 104-13), require that interested members of the public and affected agencies have an opportunity to comment on information collection and recordkeeping activities (see 5 CFR 1320.8(d)). This notice identifies an information collection activity that the Office of Conservation, Partnerships &amp; Management Policy will submit to OMB for approval for the Department and its bureaus to collect information from proposed donors relative to their relationship(s) with the Department. The Department and its individual bureaus all have gift acceptance authority. In support of the variety of donation authorities in the Department and increasing numbers of donations, it is the policy of the Department to ask those proposing to donate gifts valued at $25,000 or more to provide information regarding their relationship with the Department. The purpose of this policy is to ensure that the acceptance of a gift does not create legal or ethical issues for the Department, its bureaus, or potential donors. The information will be gathered through the use of a new form. If this information were not collected from the prospective donor, the Department would have to collect the information. The information is scattered throughout the Department. With eight major bureaus, 2500 locations and 70,000 employees, it is not possible to collect the information about a particular donor in a timely manner to respond to a proposed donation. Having the donor certify his interactions with the Department gives the staff reviewing the proposed donation basic information. 
                    <PRTPAGE P="55863"/>
                </P>
                <HD SOURCE="HD1">II. Method of Collection </HD>
                <P>Individuals notifying the Department or one of its bureaus of a proposed offer of a gift valued at $25,000 or higher will be asked to submit a form listing several items of basic information. </P>
                <P>
                    (1) 
                    <E T="03">Title:</E>
                     Donor Certification Form. 
                </P>
                <GPOTABLE COLS="02" OPTS="L2,tp0,i1" CDEF="s100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Information collected </CHED>
                        <CHED H="1">Reason for collection </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Name, and indication whether executing in individual capacity, or on behalf of an organization </ENT>
                        <ENT>To identify the donor, and whether the donor is acting individually or on behalf of an organization. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Declaration whether the donor is involved with litigation or controversy with the Department </ENT>
                        <ENT>To assist the Department in determining whether there are any issues associated with the proffer of the gift that need to be more closely examined.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Declaration whether the donor is engaged in any financial or business relationship with the Department </ENT>
                        <ENT>To assist the Department in determining whether there are any issues associated with the proffer of the gift that need to be more closely examined.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Declaration whether the donor has been debarred, excluded or disqualified  from the nonprocurement common rule, or otherwise declared ineligible from doing business with any Federal government agency </ENT>
                        <ENT>To assist the Department in determining whether there are any issues associated with the proffer of the gift that need to be more closely examined.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Declaration as to whether the donation is expected to be involved with marketing or advertising </ENT>
                        <ENT>To assist the Department in determining whether there are any issues associated with the proffer of the gift that need to be more closely examined.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Declaration whether the donor is seeking to attach conditions to the donation </ENT>
                        <ENT>To assist the Department in determining whether there are any issues associated with the proffer of the gift that need to be more closely examined. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Declaration whether this proposed donation is or is not part of a series of donations to the Department </ENT>
                        <ENT>To assist the Department in determining the scope and context of the donation, and to assist in determining whether there are any issues associated with the proffer of the gift that need to be more closely examined. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Signature, Printed Name, Date, Organization, E-mail address, City, State, Zip, and daytime  or work phone number </ENT>
                        <ENT>To establish the contact information of the potential donor, and have the certifier sign the certification form. </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">III. Data </HD>
                <P>
                    (1) 
                    <E T="03">Title:</E>
                     Donor Certification Form. 
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1090-XXXX. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Information Collection: New. 
                </P>
                <P>
                    <E T="03">Affected Entities:</E>
                     Individuals or households, Businesses, Not-for-profit institutions, Tribal Governments. 
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents:</E>
                     555. 
                </P>
                <P>
                    <E T="03">Frequency of response:</E>
                     Once per prospective donation. 
                </P>
                <P>
                    (2) 
                    <E T="03">Annual reporting and record keeping burden:</E>
                </P>
                <P>
                    <E T="03">Estimated number of responses annually:</E>
                     555. 
                </P>
                <P>
                    <E T="03">Estimated burden per response:</E>
                     20 minutes. 
                </P>
                <P>
                    <E T="03">Total annual reporting:</E>
                     185 hours. 
                </P>
                <P>
                    (3) 
                    <E T="03">Description of the need and use of the information:</E>
                     This information will provide Department staff with the basis for beginning the evaluation as to whether the Department will accept the proposed donation. The authorized employee will receive the donor certification form with the proposed donation. The employee will then review the totality of circumstances surrounding the proposed donation to determine whether the Department can accept the donation and maintain its integrity, impartiality, and public confidence. 
                </P>
                <HD SOURCE="HD1">IV. Request for Comments </HD>
                <P>The Department of the Interior invites comments on: </P>
                <P>(a) Whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; </P>
                <P>(b) The accuracy of the agency's estimate of the burden of the collection and the validity of the methodology and assumptions used; </P>
                <P>(c) Ways to enhance the quality, utility, and clarity of the information to be collected; and </P>
                <P>(d) Ways to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other collection techniques or other forms of information technology. </P>
                <P>Burden means the total time, effort, or financial resources expended by persons to generate, maintain, retain, disclose or provide information to or for a federal agency. This includes the time needed to review instructions; to develop, acquire, install and utilize technology and systems for the purpose of collecting, validating and verifying information, processing and maintaining information, and disclosing and providing information; to train personnel and to be able to respond to a collection of information, to search data sources, to complete and review the collection of information; and to transmit or otherwise disclose the information. </P>
                <P>The comments, with names and addresses, will be available for public viewing. If you wish us to withhold your personal information, you must prominently state at the beginning of your comment what personal information you want us to withhold. We will honor your request to the extent allowable by law. Comments received, if any, will be available for public viewing by appointment only. You may schedule such an appointment by contacting the Office of Conservation, Partnerships &amp; Management Policy at 1849 C Street,  NW., MS 5123 MIB, Washington, DC 20240, or telephone (202) 208-5904 to schedule an appointment to view any comments received. A valid picture identification is required for entry into the Department of the Interior. </P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid Office of Management and Budget control number. </P>
                <SIG>
                    <DATED>Dated: September 23, 2008. </DATED>
                    <NAME>Beth L. Duff, </NAME>
                    <TITLE>Office of Conservation, Partnerships and Management Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22673 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-RK-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="55864"/>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Fish and Wildlife Service </SUBAGY>
                <DEPDOC>[FWS-R6-R-2008-N0187; 60138-1261-0000-S3] </DEPDOC>
                <SUBJECT>Draft Comprehensive Conservation Plan for Red Rock Lakes National Wildlife Refuge, Lima, MT </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We, the U.S. Fish and Wildlife Service (Service) announce that our Draft Comprehensive Conservation Plan (CCP) and Environmental Assessment (EA) for Red Rock Lakes National Wildlife Refuge is available. This Draft CCP/EA describes how the Service intends to manage this Refuge for the next 15 years. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>To ensure consideration, we must receive your written comments on the draft CCP/EA by October 27, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Please provide written comments to Laura King, Planning Team Leader, Tewaukon National Wildlife Refuge, 9756 143
                        <FR>1/2</FR>
                         Avenue, SE., Cayuga, North Dakota 58013; via facsimile at 701-724-3683; or electronically to 
                        <E T="03">redrocks@fws.gov.</E>
                         A copy of the CCP/EA may be obtained by writing to U.S. Fish and Wildlife Service, Division of Refuge Planning, 134 Union Boulevard, Suite 300, Lakewood, Colorado 80228 or by download from 
                        <E T="03">http://mountain-prairie.fws.gov/planning.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Laura King, 701-724-3596 (phone); 701-724-3683 (fax); or 
                        <E T="03">laura_king@fws.gov</E>
                         (e-mail) or John Esperance, 303-236-4369 (phone); 303-236-4792 (fax); or 
                        <E T="03">john_esperance@fws.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Red Rock Lakes National Wildlife Refuge is located 28 miles east of Monida in Beaverhead County in southwestern Montana. This 47,756-acre Refuge sits at 6,670 feet above sea level and lies east of the Continental Divide near the uppermost reach of the Missouri drainage. The Refuge was established in 1935 by President Franklin D. Roosevelt. Historically, management focused on protecting and enhancing the trumpeter swan population at the Refuge. In the 1930s, the Refuge was their last known breeding location. Today, swans can still breed in the valley, but the intensive management of swan populations (through feeding and raising young) has been altered in favor of allowing the swans to thrive under mostly natural conditions. </P>
                <P>The Refuge has one of the most naturally diverse areas in the National Wildlife Refuge System. The refuge boasts the largest wetland complex within the Greater Yellowstone Ecosystem, as well as expansive tracts of grassland and sagebrush-steppe habitats and a small amount of mid-elevation forested areas. These habitats support over 200 species of birds, including peregrine falcons, bald eagles, short-eared owls, sandhill cranes, sage grouse, and numerous species of waterfowl and waterbirds. Common mammalian species include Shiras moose, Rocky Mountain elk, mule and white-tailed deer, badger, coyote, and red fox. In addition, wolves and grizzly bears have been documented using the Refuge in recent years. There is also a remnant population of native adfluvial Arctic grayling that occurs on the Refuge. </P>
                <P>A full-time staff of five employees and various summer temporaries manage and study the Refuge habitats and maintain visitor facilities. Domestic livestock grazing and prescribed fire are the primary management tools used to maintain and enhance upland habitats. Currently, four grazing cooperators are using Refuge lands. Water level manipulation occurs in some areas of the Refuge to improve wetland habitats. </P>
                <P>Approximately 12,000 people visit the Refuge annually. Two Refuge roads and three county roads that pass through the Refuge account for the majority of visitor use. The Refuge is open to limited fishing with the majority of fishing occurring on Red Rock Creek. In addition, the Refuge is open to limited hunting of ducks, geese, coots, and moose. Elk, pronghorn, moose, mule deer and white-tailed deer are also hunted on certain areas of the Refuge according to State regulations and seasons. This draft CCP/EA identifies and evaluates four alternatives for managing the Refuge for the next 15 years. </P>
                <P>Under Alternative A, funding staff levels and management activities at the Refuge would not change. Refuge habitats would continue to be managed utilizing water control structures, cattle grazing, prescribed fire, and various methods to control invasive species. There would be limited monitoring of habitat and wildlife response. The Refuge would continue to divert water from streams and impound water using all Service installed dikes, diversions, and structures. Wildlife dependent compatible priority uses, for example, hunting, fishing, wildlife observation, wildlife photography, and interpretation, would continue to occur at current levels. Hunting for big game and waterfowl would continue to be permitted on the Refuge. There would continue to be minimal outreach and education programs due to the poor county access roads and remote location. There would be minimal resources to adequately update signs, informational kiosks, and brochures as well as improve hiking trails, access roads, and campgrounds. There would be five full-time staff assigned to the Refuge.</P>
                <P>
                    Alternative B, the Proposed Action, acknowledges the importance of naturally functioning ecological communities on the Refuge. However, changes to the landscape (
                    <E T="03">e.g.</E>
                    , human alterations to the landscape, past refuge management creating wetlands and species in peril requiring special management actions) prevent managing the Refuge solely as a naturally functioning ecological community. Because some of these changes are significant, some Refuge habitats would require “hands on” management actions during the life of this plan, while others would be restored. Refuge habitats would continue to be managed utilizing water control structures, cattle grazing, prescribed fire, and various methods to control invasive species. The Refuge would determine their level of participation in State initiatives to reintroduce bison should they become designated as wildlife in Montana. Monitoring and documenting the response to management actions would be greatly expanded. Habitat and wildlife objectives would be clearly stated in step-down management plans. Visitor services programs would be maintained and expanded including hunting, fishing, wildlife observation and photography, and interpretation programs while maintaining the wilderness characteristics of the Refuge. Boundaries for big game hunting would be adjusted to reduce confusion, provide additional opportunities, and reduce illegal road hunting. Fishing would be expanded and following State regulations, visitors would be encouraged to keep nonnative fish species that impact native adfluvial Arctic grayling. Some Refuge roads and trails would provide interpretation and be identified on a new visitor services map. Idlewild Road would be closed to reduce maintenance costs and fragmentations of wildlife habitats. Both Refuge campgrounds would be maintained to support wildlife dependent compatible recreation on this remote Refuge. 
                </P>
                <P>
                    Alternative C acknowledges the importance of a naturally functioning ecosystem. Management action emphasis would be placed on allowing wetland and riparian habitats to 
                    <PRTPAGE P="55865"/>
                    function naturally through the restoration of created and modified wetlands. Refuge habitats would continue to be managed utilizing the remaining water control structures, cattle grazing, prescribed fire, and various methods to control invasive species. The Refuge would determine their level of participation in State initiatives to reintroduce bison should they become designated as wildlife in Montana. Monitoring and documenting wildlife and habitat responses to management actions would be greatly expanded. Habitat and wildlife objectives would be clearly stated in step-down management plans. Visitor services programs would be improved and expanded, particularly environmental education and interpretation programs, while maintaining the wilderness characteristics of the Refuge. Boundaries for big game hunting would be adjusted to reduce confusion, provide additional opportunities, and reduce illegal road hunting. Some Refuge trails would provide interpretation and be identified on a new visitor services map. Idlewild Road would be closed to reduce maintenance costs and fragmentations of wildlife habitats. Fishing would be expanded and following State regulations, visitors would be encouraged to keep nonnative fish species that impact native adfluvial Arctic grayling. Only one Refuge campground would be maintained to support wildlife dependent compatible recreation on this remote Refuge. 
                </P>
                <P>Alternative D further acknowledges the importance of a naturally functioning ecosystem. Management action emphasis would be placed on the restoration of all natural processes including the restoration of all wetland and riparian habitats. The Refuge would participate in State initiatives to reintroduce bison should they become designated as wildlife in Montana. Monitoring of habitat and wildlife response to management actions would be greatly expanded. Habitat and wildlife objectives would be clearly stated in step-down management plans. The Refuge will place emphasis on creating a wilderness setting in all areas away from the Refuge headquarters. Visitor services programs would be maintained or expanded while promoting a wilderness experience with little or no signage and interpretation. Moose hunting would be eliminated. Boundaries for big game hunting areas would be adjusted to reduce confusion, provide additional opportunities, and reduce illegal road hunting. Fishing would be expanded and following State regulations, visitors would be encouraged to keep nonnative fish species that have impacted native adfluvial Arctic grayling. Idlewild Road, the associate boat ramp, and the north entrance spur roads would be closed to public vehicle access to reduce maintenance costs. Both Refuge campgrounds would be closed. </P>
                <P>
                    All public comment information provided voluntarily by mail, by phone, or at meetings (
                    <E T="03">e.g.</E>
                    , names, addresses, letters of comment, input recorded during meetings) becomes part of the official public record. If requested under the Freedom of Information Act by a private citizen or organization, the Service may provide copies of such information. The Environmental Review of this project will be conducted in accordance with the requirements of the National Environmental Policy Act (NEPA) of 1969, as amended (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ); NEPA Regulations (40 CFR parts 1500-1508); other appropriate Federal laws and regulations; Executive Order 12996; the National Wildlife Refuge System Improvement Act of 1997; and Service policies and procedures for compliance with those laws and regulations. 
                </P>
                <SIG>
                    <DATED>Dated: July 21, 2008. </DATED>
                    <NAME>Sharon R. Rose, </NAME>
                    <TITLE>Acting Regional Director.</TITLE>
                </SIG>
                <EDNOTE>
                    <HD SOURCE="HED">Editorial Note:</HD>
                    <P>This document was received in the Office of the Federal Register on September 23, 2008.</P>
                </EDNOTE>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22697 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-55-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Indian Affairs </SUBAGY>
                <SUBJECT>Jackson Band of Miwuk Indians of the Jackson Rancheria Liquor Control Ordinance </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Indian Affairs, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice publishes the Jackson Band of Miwuk Indians of the Jackson Rancheria (Tribe) Liquor Control Ordinance. The Ordinance regulates and controls the possession, sale and consumption of liquor within the Jackson Tribe's tribal land. The tribal land is located on trust land and this Ordinance allows for the possession and sale of alcoholic beverages. This Ordinance will increase the ability of the tribal government to control the distribution and possession of liquor within their tribal land, and at the same time will provide an important source of revenue and strengthening of the tribal government and the delivery of tribal services. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         This Ordinance is effective September 26, 2008. 
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Fred Doka, Jr., Tribal Operations Officer, Pacific Regional Office, 2800 Cottage Way, Sacramento, CA 95825, Telephone (916) 978-6067; or Elizabeth Colliflower, Office of Indian Services, 1849 C Street, NW., Mail Stop 4513-MIB, Washington, DC 20240; Telephone (202) 513-7627; Fax (202) 501-0679. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to the Act of August 15, 1953, Public Law 83-277, 67 Stat. 586, 18 U.S.C. 1161, as interpreted by the Supreme Court in 
                    <E T="03">Rice</E>
                     v. 
                    <E T="03">Rehner</E>
                    , 463 U.S. 713 (1983), the Secretary of the Interior shall certify and publish in the 
                    <E T="04">Federal Register</E>
                     notice of adopted liquor ordinances for the purpose of regulating liquor transactions in Indian country. The Jackson Band of Miwuk Indians of the Jackson Rancheria Tribal Council adopted this Ordinance on April 18, 2008. The purpose of this Ordinance is to govern the sale, possession and distribution of alcohol within the Tribe's land. 
                </P>
                <P>This notice is published in accordance with the authority delegated by the Secretary of the Interior to the Assistant Secretary—Indian Affairs. I certify that the Jackson Band of Miwuk Indians of the Jackson Rancheria adopted this Liquor Control Ordinance No. 2008-02 on April 18, 2008. </P>
                <SIG>
                    <DATED>Dated: September 17, 2008. </DATED>
                    <NAME>George Skibine, </NAME>
                    <TITLE>Acting Deputy Assistant Secretary for Policy and Economic Development.</TITLE>
                </SIG>
                <P>The Jackson Band of Miwuk Indians of the Jackson Rancheria Liquor Control Ordinance reads as follows: </P>
                <HD SOURCE="HD1">Jackson Band of Miwuk Indians of the Jackson Rancheria, Amador County, California, Tribal Council Ordinance No. 2008-02, Sale of Alcoholic Beverages </HD>
                <P>The Tribal Council of the Jackson Band of Miwuk Indians of the Jackson Rancheria (hereinafter “Council”), governing body of the Jackson Band of Miwuk Indians of the Jackson Rancheria (hereinafter “Tribe”), hereby enacts this Ordinance to govern the sale of alcoholic beverages at our general convenience store on Rancheria lands. </P>
                <HD SOURCE="HD2">Preamble </HD>
                <P>
                    1. Title 18, United States Code, Section 1161, provides Indian tribes with authority to enact ordinances governing the consumption and sale of alcoholic beverages on their Reservations, provided such ordinance 
                    <PRTPAGE P="55866"/>
                    is certified by the Secretary of the Interior, published in the 
                    <E T="04">Federal Register</E>
                     and such activities are in conformity with state law. 
                </P>
                <P>2. Jackson Rancheria is the owner and operator of a general convenience store on the Rancheria (hereinafter for reference purpose “General Store”) which sells, among other products, certain snack and food items to members of the Tribe and the general public. </P>
                <P>3. Said General Store is an integral part of the Tribe's economy. </P>
                <P>4. The Tribal Council has determined that it is in the Tribe's best interest to offer for sale at the General Store, for off-premises consumption only, alcoholic beverages. </P>
                <P>5. It is the purpose of this Ordinance to set out the terms and conditions under which the sale of said alcoholic beverages may take place. </P>
                <HD SOURCE="HD3">General Terms </HD>
                <P>1. The sale of alcoholic beverages at the Jackson Rancheria's General Store for off-premises consumption only, is hereby authorized. For purposes of this paragraph 1 and this Ordinance, “off-premises” is defined as area outside the boundaries of the Jackson Rancheria lands. </P>
                <P>2. No alcoholic beverages may be sold at any location on the Rancheria pursuant to this Ordinance other than the General Store. </P>
                <P>3. The sale of said alcoholic beverages authorized by this Ordinance shall be in conformity with all applicable laws of the State of California, and the sale of said beverages shall be subject to any and all applicable state sales tax, federal excise tax and any fees required by the Federal Bureau of Alcohol, Tobacco &amp; Firearms. This includes but is not limited to the following examples: </P>
                <P>a. No person under the age of 21 years shall acquire or have in his or her possession at the General Store any alcoholic beverage. </P>
                <P>b. No person shall sell alcohol to any person under the age of 21 at the General Store. </P>
                <P>c. No person shall sell alcohol to a person apparently under the influence of liquor. </P>
                <HD SOURCE="HD2">Posting </HD>
                <P>This Ordinance shall be conspicuously posted at the General Store at all times it is open to the public. </P>
                <HD SOURCE="HD3">Enforcement </HD>
                <P>1. This Ordinance may be enforced by the Tribal Council by implementation of monetary fines not to exceed $500 and/or withdrawal of authorization to sell alcohol. Prior to any enforcement action, the Tribal Council shall provide the alleged offender of this Ordinance with at least three (3) days notice of an opportunity to be heard during a specially-called Tribal Council meeting. The decision of the Tribal Council shall be final. </P>
                <P>2. This Ordinance also may be enforced by the Amador County Sheriff's Office at the request of the Tribal Council. </P>
                <P>3. In the exercise of its powers and duties under this Ordinance, the Tribal Council and its individual members shall not accept any gratuity or compensation from any liquor wholesaler, retailer, or distributor for the General Store. </P>
                <HD SOURCE="HD3">Severability, Amendment, and Sovereign Immunity </HD>
                <P>1. If any provision or application of this Ordinance is determined by review to be invalid, such adjudication shall not be held to render ineffectual the remaining portions of this title or to render such provisions inapplicable to other persons or circumstances. </P>
                <P>2. This Ordinance may only be amended by a majority vote of the Tribal Council. </P>
                <P>3. Nothing in this Ordinance in any way limits, alters, restricts or waives the Tribe's sovereign immunity from unconsented suit or action. </P>
                <HD SOURCE="HD3">Effective Date </HD>
                <P>
                    This Ordinance shall become effective following its certification by the Secretary of the Interior and its publication in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD2">Certification </HD>
                <P>The foregoing Ordinance was adopted by a vote of 3 for, and 0 against and 0 abstentions, at a duly called meeting of the Jackson Band of Miwuk Indians of the Jackson Rancheria Tribal Council at which a quorum was present, on this 18th day of April, 2008. </P>
                <EXTRACT>
                    <FP SOURCE="FP-DASH">/s/ </FP>
                    <FP>Margaret Dalton, </FP>
                    <FP>
                        <E T="03">Chairperson</E>
                        .
                    </FP>
                    <FP>ATTEST:</FP>
                    <FP SOURCE="FP-DASH"/>
                    <FP>Gary Marks, </FP>
                    <FP>
                        <E T="03">Secretary-Treasurer</E>
                        .
                    </FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22707 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-4J-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Land Management </SUBAGY>
                <DEPDOC>[MT-070-08-1610-DQ-030E] </DEPDOC>
                <SUBJECT>Notice of Availability of the Proposed Resource Management Plan and Final Environmental Impact Statement for the Butte Field Office, Montana </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the National Environmental Policy Act of 1969 (NEPA) and the Federal Land Policy and Management Act of 1976 (FLPMA), the Bureau of Land Management (BLM) has prepared the Proposed Resource Management Plan and Final Environmental Impact Statement (PRMP/Final EIS) for the Butte Field Office, Montana. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The BLM planning regulations (43 CFR 1610.5-2) state that any person who meets the conditions as described in the regulations may protest the BLM's PRMP/FEIS. A person who meets the conditions and files a protest must file the protest within 30 days of the date that the Environmental Protection Agency (EPA) publishes its Notice of Availability in the 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Copies of the PRMP/FEIS are available for public inspection at the BLM Butte Field Office, 106 North Parkmont, Butte, Montana. Interested persons may also review the PRMP/FEIS on the Internet at: 
                        <E T="03">http://www.blm.gov/mt/st/en/fo/butte_field_office.html</E>
                        . All protests must be in writing and mailed to the following addresses: 
                    </P>
                    <P>
                        <E T="03">Regular Mail:</E>
                         Director (210), Attention: Brenda Williams, P.O. Box 66538, Washington, DC 20035. 
                    </P>
                    <P>
                        <E T="03">Overnight Mail:</E>
                         Director (210), Attention: Brenda Williams, 1620 L Street, NW., Suite 1075, Washington, DC 20036. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Tim La Marr, RMP Project Manager, Bureau of Land Management, 106 North Parkmont, Butte, MT 59701, or by telephone at (406) 533-7645. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Butte Field Office is located in southwest Montana in Beaverhead, Broadwater, Deer Lodge, Gallatin, Jefferson, Lewis and Clark, Park, and Silver Bow Counties. The planning area addressed in the PRMP/FEIS includes about 307,000 acres of the BLM surface lands and 652,000 acres of subsurface federal mineral estate administered by the Butte Field Office. </P>
                <P>
                    Copies of the PRMP/FEIS for the Butte Field Office have been sent to affected 
                    <PRTPAGE P="55867"/>
                    federal, state, and local government agencies, tribal governments, and other interested parties. There have been various opportunities for the public to provide input on this plan via public meetings, open houses, and multiple scoping periods where public comments have been solicited. 
                </P>
                <P>The PRMP/FEIS considers four alternatives and will include the use of community-based working groups to assist with site-specific travel planning. The PRMP/FEIS addresses the following five major issues: </P>
                <P>(1) How will vegetation on the BLM lands be managed to achieve healthy ecosystems while providing for a broad range of multiple uses? </P>
                <P>(2) How will the BLM lands be managed to provide wildlife and fish habitat, and to conserve and recover special status and priority species? </P>
                <P>(3) How should the BLM manage motorized public travel to meet the needs for public access and resource uses while minimizing user conflicts and impacts to air, soil, watershed, vegetation, wildlife, and other resource values? </P>
                <P>(4) How should recreation be managed to accommodate the full range of recreational uses enjoyed by the public on the BLM lands? </P>
                <P>(5) Which areas, if any, should be managed as special designations, and how should they be managed to protect values that warrant their special designation status? The Preferred Alternative (Alternative B) includes active vegetation management to restore vegetation communities with associated forest product quantities being the same as, or slightly higher than, current levels, riparian management zones where meeting site-specific riparian objectives would receive primary consideration, and continuation of livestock grazing at approximately the same as current levels while meeting Land Health Standards. The Preferred Alternative would entail designation of four Areas of Critical Environmental Concern (ACEC), totaling 70,644 acres in area, with special management proposed for relevant and important values, as well as recommending two river segments, with a total length of 5.7 miles, as suitable for Wild and Scenic River Designation. </P>
                <P>Comments on the Draft RMP/EIS received from the public and from the internal BLM review were incorporated as appropriate into the PRMP/FEIS. Public comments resulted in the addition of clarifying text and slight alterations of the Preferred Alternative but did not significantly change proposed land use decisions. </P>
                <P>
                    Instructions for filing a protest with the Director of the BLM regarding the PRMP/FEIS may be found in the Dear Reader letter of the PRMP/FEIS for the Butte Field Office and at 43 CFR 1610.5-2. E-mailed and faxed protests will not be accepted as valid protests unless the protesting party also provides the original letter by either regular or overnight mail postmarked by the close of the protest period. Under these conditions, the BLM will consider the e-mailed or faxed protest as an advance copy and it will receive full consideration. If you wish to provide the BLM with such advance notification, please direct fax protests to the attention of the BLM protest coordinator at (202) 452-5112, and e-mails to 
                    <E T="03">Brenda_Hudgens-Williams@blm.gov</E>
                    . 
                </P>
                <P>
                    All protests, including the follow-up letter, if e-mailing or faxing, must be in writing and mailed to the appropriate address as set forth in the 
                    <E T="02">ADDRESSES</E>
                     section above. 
                </P>
                <P>Before including your phone number, e-mail address, or other personal identifying information in your protest, you should be aware that your entire protest—including your personal identifying information—may be made publicly available at any time. While you can ask us in your protest to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so. </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>40 CFR 1506.6, 43 CFR 1610.2, and 43 CFR 1610.5-1. </P>
                </AUTH>
                <SIG>
                    <NAME>Theresa M. Hanley, </NAME>
                    <TITLE>Acting State Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22543 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-DN-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Land Management </SUBAGY>
                <DEPDOC>[NV-040-1610-DR; 08-08807; TAS: 14X1109] </DEPDOC>
                <SUBJECT>Notice of Availability: Record of Decision for the Ely Resource Management Plan/Environmental Impact Statement, Nevada </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Bureau of Land Management (BLM) announces the availability of the Record of Decision (ROD) for the Approved Resource Management Plan (RMP) for the Ely RMP planning area located in east-central Nevada in Lincoln, White Pine and a portion of Nye counties. The Nevada State Director signed the ROD on August 20, 2008, which constitutes the final decision of the BLM and makes the Approved RMP effective immediately. </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Copies of the ROD/Approved RMP are available on request from the District Manager, Ely District Office, Bureau of Land Management, 702 North Industrial Way, Ely, Nevada 89301 or via the Internet at: 
                        <E T="03">http://www.blm.gov/nv/st/en/fo/ely_field_office.html</E>
                        . 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For further information contact Jeff Weeks, RMP Project Manager, at (775) 289-1825 or e-mail to: 
                        <E T="03">elyrmp@blm.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The following entities participated in development of the RMP as cooperating agencies with special expertise: Great Basin National Park; Humboldt-Toiyabe National Forest; Nellis Air Force Base; Nevada Department of Transportation; Nevada Division of Minerals; Nevada Department of Wildlife; Nevada State Historic Preservation Office; Lincoln County; Nye County; White Pine County; Duckwater Shoshone Tribe; Ely Shoshone Tribe; Moapa Band of Paiutes; and the Yomba Shoshone Tribe. </P>
                <P>The public involvement and collaboration process implemented for this effort included six open houses during scoping; presentations to interested organizations upon their invitation; presentations to and suggestions from the Mojave/Southern Great Basin and the Northeastern Great Basin Resource Advisory Councils (RACs); distribution of information via the Ely RMP Web site and periodic planning bulletins; six public meetings on the Draft RMP/EIS; and public and agency review and comment on the Draft RMP/EIS. </P>
                <P>The planning area contains approximately 11,500,000 acres of public lands administered by the BLM Ely District. The Approved RMP describes the management direction to meet desired resource conditions through watershed analyses for livestock grazing, wildlife habitat, and special status species, while managing for mineral exploration and development, renewable energy development, recreational uses, areas of critical environmental concern. It also provides for land tenure adjustments to meet community growth needs. </P>
                <P>
                    The preferred alternative, Alternative E of the Draft RMP, was carried forward into the Proposed RMP and Final EIS (PRMP/FEIS) as the Proposed Plan. The PRMP/FEIS was made available on November 30, 2007 and sent to 
                    <PRTPAGE P="55868"/>
                    individuals, groups, and agencies who requested a copy, or as required by regulation or policy. 
                </P>
                <P>A 30-day protest period was provided on the land use plan decisions contained in the Proposed RMP/Final EIS in accordance with 43 CFR Part 1610.5-2. Six protests were received (two from the same party), three of the six letters were subsequently resolved by the BLM Director, whose decision constitutes final agency action for the U.S. Department of the Interior. The main protest issues in these letters pertained to special status species, wildlife, livestock grazing, watershed management, and level of detail of decisions in the Proposed RMP. No changes to proposed management actions resulted from the resolution of the protests. </P>
                <P>Three of the six protest letters received were determined not to have standing under the regulations at 43 CFR 1610.5-2. During the process of reviewing protest letters, the BLM became aware of a mapping error and potentially unnecessary management direction for the proposed ACEC at the Rock Animal Corral. The BLM has determined that the area does not require special management as an ACEC to protect its relevant and important values. Protection of the values can be achieved by maintaining the current designation as the Rock Animal Corral archaeological site with existing restrictions on fluid and solid mineral leasing, locatable minerals and mineral material sales on the 160 acre site. This is consistent with the current management in Alternative A in the Proposed RMP. The Approved RMP reflects that change. </P>
                <P>The BLM provided the Governor of Nevada with a 60-day Governor's Consistency Review as provided by the regulations. No specific inconsistencies with state or local plans, policies, or programs were noted from the review. BLM received comments from the Nevada Department of Wildlife and the Nevada Division of Water Resources. BLM responded to the Department of Wildlife comments with a meeting and a letter. No changes to the Approved RMP resulted from the Governors' Consistency Review. Based upon comments received during the protest period, some minor editorial modifications have been made in preparing the Approved RMP. These modifications provide further clarification of some of the decisions/maps. </P>
                <P>In accordance with Section 7 of the Endangered Species Act, the U.S. Fish and Wildlife Service (USFWS) issued a Biological Opinion. The USFWS Biological Opinion has been included as an appendix to the ROD/Approved RMP. </P>
                <P>The ROD serves as the final decision for the land use plan decisions described in the Approved RMP. The ROD also contains implementation-level decisions for Paleontological Resource Management, Travel Management route identifications, and Forest/Woodland and Other Plant Products. These decisions are included in the Approved RMP. Designations, such as route closures are planning-level decisions. These implementation-level decisions are appealable under 43 CFR Part 4. Any party adversely affected by the (proposed) implementation decisions may appeal the decisions within 30 days of publication of this Notice of Availability pursuant to 43 CFR, Part 4, Subpart E. The appeal should state the specific decision(s) in the Approved RMP which are being appealed. </P>
                <P>The appeal must be filed with the Ely District Manager at the address listed above. Please consult the appropriate regulations (43 CFR, Part 4, Subpart E) for further appeal requirements. </P>
                <EXTRACT>
                    <FP>(Authority: H-1790-1-National Environmental Policy Act Handbook) </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Ron Wenker, </NAME>
                    <TITLE>Nevada State Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22540 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-HC-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Land Management </SUBAGY>
                <DEPDOC>[MT-070-1990-EX] </DEPDOC>
                <SUBJECT>Notice of Availability of the Final Environmental Impact Statement for the Proposed “M” Pit Mine Expansion at the Montana Tunnels Mine, Jefferson County, MT </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the 
                        <E T="03">National Environmental Policy Act of 1969</E>
                         (NEPA, 42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ) and the 
                        <E T="03">Federal Land Policy and Management Act of 197</E>
                        6 (FLPMA, 43 U.S.C. 1701 
                        <E T="03">et seq.</E>
                        ), a Final Environmental Impact Statement (FEIS) has been prepared for the Montana Tunnels Mine “M” Pit Mine Expansion. The mine permit is administered by the Bureau of Land Management's (BLM's) Butte Field Office and the Montana Department of Environmental Quality. Operations on public lands in the permit area are on mining claims located in accordance with the 
                        <E T="03">General Mining Law of 1872,</E>
                         as amended (30 U.S.C. 22 
                        <E T="03">et seq.</E>
                        ). 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The FEIS will be available for review for 30 days following the date the Environmental Protection Agency (EPA) publishes the Notice of Availability in the 
                        <E T="04">Federal Register</E>
                        . A Record of Decision (ROD) will be prepared following the 30-day public availability period. 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Copies of the FEIS have been sent to affected federal, state, and local government agencies and to interested parties. Copies of the FEIS are available for public inspection at the Montana Department of Environmental Quality, 1520 East 6th Avenue, Helena, MT 59620-0901 and the Bureau of Land Management, Butte Field Office, 106 N. Parkmont, Butte, MT 59701. Interested parties may also review the FEIS on the Internet at 
                        <E T="03">http://www.deq.mt.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Greg Hallsten, Montana Department of Environmental Quality, P.O. Box 200901, Helena, MT 59620-0901; or David Williams, Bureau of Land Management, Butte Field Office, 106 N. Parkmont, Butte, MT 59701. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Montana Tunnels Mine is a 1200 acre lead, zinc, gold and silver mine located T. 7 N., R. 4 W. in Jefferson County 5 miles west of Jefferson City, Montana. In September 2004, Montana Tunnels, Inc. submitted an application to expand their operation. The Notice of Intent to prepare the EIS was published in the 
                    <E T="04">Federal Register</E>
                    , 70 FR 8612 on February 22, 2005 and the Notice of Availability of the Draft EIS was announced in the 
                    <E T="04">Federal Register</E>
                    , 73 FR 7588-89 on February 8, 2008. Comments on the Draft EIS received from the public, from other agencies, and from the internal DEQ and BLM review were incorporated into the FEIS. These comments resulted in the addition of clarifying text but did not significantly change the alternatives. 
                </P>
                <P>
                    The FEIS addresses three alternatives associated with the Montana Tunnels Mine “M” Pit Mine Expansion: The No Action Alternative, the Proposed Action Alternative, and the Agency Modified Alternative, which is the preferred alternative. The No Action Alternative would limit mine disturbance to 1200 acres, and the mine would close in 2010. The Proposed Action Alternative would result in disturbance of 1452 acres and a pit depth of 4250. This Alternative would result in the loss of approximately 2600 feet of Clancy Creek as the stream would be diverted around the expanded open pit in both a pipe and open flow channel. A portion of the Clancy Creek flow would be diverted 
                    <PRTPAGE P="55869"/>
                    into the pit to augment the formation of a pit lake following completion of mining. The Agency Modified Alternative would be similar to the Proposed Action Alternative, with the exception of measures to improve environmental performance including: More natural surface reclamation techniques, improved geochemical and groundwater monitoring, and establishment of a reconstructed Clancy Creek channel to protect streamflow, wetlands, and fisheries. 
                </P>
                <SIG>
                    <NAME>Rick M. Hotaling, </NAME>
                    <TITLE>Field Manager.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22535 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-DN-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Land Management </SUBAGY>
                <DEPDOC>[MT-921-08-1320-EL-P; MTM 98618] </DEPDOC>
                <SUBJECT>Notice of Invitation—Coal Exploration License Application MTM 98618 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Members of the public are hereby invited to participate with Western Energy Company in a program for the exploration of coal deposits owned by the United States of America in lands located in Rosebud County, Montana, encompassing 921.06 acres. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Robert Giovanini, Mining Engineer, or Connie Schaff, Land Law Examiner, Branch of Solid Minerals (MT-921), Bureau of Land Management (BLM), Montana State Office, Billings, Montana 59101-4669, telephone  (406) 896-5084 or (406) 896-5060, respectively. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The lands to be explored for coal deposits are described as follows: </P>
                <EXTRACT>
                    <FP SOURCE="FP-2">T.1N., R.4E., P.M.M. </FP>
                    <FP SOURCE="FP1-2">22: All. </FP>
                    <FP SOURCE="FP1-2">
                        24: Lots 1, 2, W
                        <FR>1/2</FR>
                        NE
                        <FR>1/4</FR>
                        , N
                        <FR>1/2</FR>
                        NW
                        <FR>1/4</FR>
                        , N
                        <FR>1/2</FR>
                        S
                        <FR>1/2</FR>
                        NW
                        <FR>1/4</FR>
                        , SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        .
                    </FP>
                </EXTRACT>
                <P>
                    Any party electing to participate in this exploration program shall notify, in writing, both the State Director, BLM, 5001 Southgate Drive, Billings, Montana 59101-4669, and Western Energy Company, P.O. Box 99, Colstrip, Montana 59323. Such written notice must refer to serial number MTM 98618 and be received no later than 30 calendar days after publication of this Notice in the 
                    <E T="04">Federal Register</E>
                     or 10 calendar days after the last publication of this Notice in the 
                    <E T="03">Miles City Star</E>
                     newspaper, whichever is later. This Notice will be published once a week for two (2) consecutive weeks in the 
                    <E T="03">Miles City Star,</E>
                     Miles City, Montana. 
                </P>
                <P>The proposed exploration program is fully described, and will be conducted pursuant to an exploration plan to be approved by the Bureau of Land Management. The exploration plan, as submitted by Western Energy Company, is available for public inspection at the BLM, 5001 Southgate Drive, Billings, Montana, during regular business hours (9 a.m. to 4 p.m.), Monday through Friday. </P>
                <SIG>
                    <DATED>Dated: September 19, 2008. </DATED>
                    <NAME>Edward L. Hughes,</NAME>
                    <TITLE>Acting Chief, Branch of Solid Minerals.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22699 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-$$-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration </SUBAGY>
                <SUBJECT>Manufacturer of Controlled Substances; Notice of Application </SUBJECT>
                <P>Pursuant to § 1301.33(a) of Title 21 of the Code of Federal Regulations (CFR), this is notice that on August 28, 2008, Mallinckrodt Inc., 3600 North Second Street, St. Louis, Missouri 63147, made application by letter to the Drug Enforcement Administration (DEA) as a bulk manufacturer of Oripavine (9330), a basic class of controlled substance listed in schedule II. </P>
                <P>The company plans to use the above listed controlled substance as an intermediate in the manufacture of a non-controlled product. </P>
                <P>Any other such applicant, and any person who is presently registered with DEA to manufacture such substances, may file comments or objections to the issuance of the proposed registration pursuant to 21 CFR 1301.33(a). </P>
                <P>Any such written comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, Federal Register Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than November 25, 2008. </P>
                <SIG>
                    <DATED>Dated: September 18, 2008. </DATED>
                    <NAME>Joseph T. Rannazzisi, </NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22696 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE </AGENCY>
                <SUBAGY>Office of Justice Programs </SUBAGY>
                <DEPDOC>[OJP (OJP) Docket No. 1488] </DEPDOC>
                <SUBJECT>Meeting of the Public Safety Officer Medal of Valor Review Board </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Justice Programs (OJP), Justice. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an announcement of a meeting of the Public Safety Officer Medal of Valor Review Board to review applications for the 2007-2008 Medal of Valor Awards and to discuss upcoming activities. The meeting time and location are located below. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>October 30, 2008, 10 a.m. to 5 p.m. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will take place at the Office of Justice Programs, 810 7th Street, NW., Washington, DC 20531. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Gregory Joy, Policy Advisor, Bureau of Justice Assistance, Office of Justice Programs, 810 7th Street, NW., Washington, DC 20531, by telephone at (202) 514-1369, toll free (866) 859-2687, or by e-mail at 
                        <E T="03">gregory.joy@usdoj.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Public Safety Officer Medal of Valor Review Board carries out those advisory functions specified in 42 U.S.C. 15202. Pursuant to 42 U.S.C. 15201, the President of the United States is authorized to award the Public Safety Officer Medal of Valor, the highest national award for valor by a public safety officer. The purpose of this meeting is to review applications for the 2007-2008 Medal of Valor Awards and to discuss upcoming activities related thereto. </P>
                <P>
                    This meeting will be open to the public. For security purposes, members of the public who wish to attend must register at least five (5) days in advance of the meeting by contacting Mr. Joy. All attendees will be required to sign in at the front desk. 
                    <E T="04">Note:</E>
                     Photo identification will be required for admission. Additional identification documents may be required. 
                </P>
                <P>Access to the meeting will not be allowed without prior registration. Anyone requiring special accommodations should contact Mr. Joy at least five (5) days in advance of the meeting. </P>
                <SIG>
                    <NAME>Eric Holland, </NAME>
                    <TITLE>Deputy Assistant Attorney General, Office of Justice Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22709 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4410-18-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="55870"/>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR </AGENCY>
                <SUBAGY>Office of the Secretary </SUBAGY>
                <SUBJECT>Submission for OMB Review: Comment Request </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>
                    The Department of Labor (DOL) hereby announces the submission of the following public information collection request (ICR) to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995 (Pub. L. 104-13, 44 U.S.C. chapter 35). A copy of this ICR, with applicable supporting documentation; including among other things a description of the likely respondents, proposed frequency of response, and estimated total burden may be obtained from the RegInfo.gov Web site at 
                    <E T="03">http://www.reginfo.gov/public/do/PRAMain</E>
                     or by contacting Darrin King on 202-693-4129 (this is not a toll-free number)/E-mail: 
                    <E T="03">DOL_PRA_PUBLIC@dol.gov</E>
                    . 
                </P>
                <P>
                    Interested parties are encouraged to send comments to the Office of Information and Regulatory Affairs, Attn: OMB Desk Officer for the Occupational Safety and Health Administration (OSHA), Office of Management and Budget, Room 10235, Washington, DC 20503, Telephone: 202-395-7316/Fax: 202-395-6974 (these are not toll-free numbers), E-mail: 
                    <E T="03">OIRA_submission@omb.eop.gov</E>
                     within 30 days from the date of this publication in the 
                    <E T="04">Federal Register</E>
                    . In order to ensure the appropriate consideration, comments should reference the OMB Control Number (see below). 
                </P>
                <P>The OMB is particularly interested in comments which:</P>
                <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; </P>
                <P>• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; </P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected; and </P>
                <P>• Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, e.g., permitting electronic submission of responses. </P>
                <P>
                    <E T="03">Agency:</E>
                     Occupational Safety and Health Administration. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a previously approved collection. 
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Electrical Standards for Construction (29 CFR Part 1926, Subpart K) and General Industry (29 CFR Part 1910, Subpart S). 
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1218-0130. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business or other for-profit and Not-for-profit institutions. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     500,000. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     151,172. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Cost Burden:</E>
                     $7,500. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     The information collection requirements specified in the Electrical Standards for Construction and the Electrical Standards for General Industry are necessary for the prevention of inadvertent electrocution of employees. For additional information, see related 60-day preclearance notice published in the 
                    <E T="04">Federal Register</E>
                     at 73 FR 39049 on July 8, 2008. PRA documentation prepared in association with the preclearance notice is available on 
                    <E T="03">http://www.regulations.gov</E>
                     under docket number OSHA 2008-0017. 
                </P>
                <SIG>
                    <NAME>Darrin A. King, </NAME>
                    <TITLE>Departmental Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22628 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4510-26-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR </AGENCY>
                <SUBAGY>Occupational Safety and Health Administration </SUBAGY>
                <DEPDOC>[Docket No. OSHA-2008-0030] </DEPDOC>
                <SUBJECT>The 13 Carcinogens Standard; Extension of the Office of Management and Budget's (OMB) Approval of Information Collection (Paperwork) Requirements </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Occupational Safety and Health Administration (OSHA), Labor. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for public comment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>OSHA solicits public comment concerning its proposal to extend OMB approval of the information collection requirements specified in the 13 Carcinogens Standard (29 CFR 1910.1003). </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted (postmarked, sent, or received) by November 25, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P SOURCE="NPAR">
                        <E T="03">Electronically:</E>
                         You may submit comments and attachments electronically at 
                        <E T="03">http://www.regulations.gov,</E>
                         which is the Federal eRulemaking Portal. Follow the instructions online for submitting comments. 
                    </P>
                    <P>
                        <E T="03">Facsimile:</E>
                         If your comments, including attachments, are not longer than 10 pages, you may fax them to the OSHA Docket Office at (202) 693-1648. 
                    </P>
                    <P>
                        <E T="03">Mail, hand delivery, express mail, messenger, or courier service:</E>
                         When using this method, you must submit three copies of your comments and attachments to the OSHA Docket Office, Docket No. OSHA-2008-0030, U.S. Department of Labor, Occupational Safety and Health Administration, Room N-2625, 200 Constitution Avenue, NW., Washington, DC 20210. Deliveries (hand, express mail, messenger, and courier service) are accepted during the Department of Labor's and Docket Office's normal business hours, 8:15 a.m. to 4:45 p.m., e.t. 
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions must include the Agency name and OSHA docket number for the ICR (OSHA-2008-0030). All comments, including any personal information you provide, are placed in the public docket without change, and may be made available online at 
                        <E T="03">http://www.regulations.gov.</E>
                         For further information on submitting comments see the “Public Participation” heading in the section of this notice titled “
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        .” 
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         To read or download comments or other material in the docket, go to 
                        <E T="03">http://www.regulations.gov</E>
                         or the OSHA Docket Office at the address above. All documents in the docket (including this 
                        <E T="04">Federal Register</E>
                         notice) are listed in the 
                        <E T="03">http://www.regulations.gov</E>
                         index; however, some information (e.g., copyrighted material) is not publicly available to read or download through the Web site. All submissions, including copyrighted material, are available for inspection and copying at the OSHA Docket Office. You may also contact Theda Kenney at the address below to obtain a copy of the ICR. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jamaa Hill or Todd Owen, Directorate of Standards and Guidance, OSHA, U.S. Department of Labor, Room N-3609, 200 Constitution Avenue, NW., Washington, DC 20210; telephone (202) 693-2222. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <P>
                    The Department of Labor, as part of its continuing effort to reduce paperwork and respondent (i.e., employer) burden, conducts a preclearance consultation program to provide the public with an opportunity to comment on proposed 
                    <PRTPAGE P="55871"/>
                    and continuing information collection requirements in accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3506(c)(2)(A)). This program ensures that information is in the desired format, reporting burden (time and costs) is minimal, collection instruments are clearly understood, and OSHA's estimate of the information collection burden is accurate. The Occupational Safety and Health Act of 1970 (the OSH Act) (29 U.S.C. 651 
                    <E T="03">et seq.</E>
                    ) authorizes information collection by employers as necessary or appropriate for enforcement of the OSH Act or for developing information regarding the causes and prevention of occupational injuries, illnesses, and accidents (29 U.S.C. 657). The OSH Act also requires that OSHA obtain such information with minimum burden upon employers, especially those operating small businesses, and to reduce to the maximum extent feasible unnecessary duplication of efforts in obtaining information (29 U.S.C. 657). 
                </P>
                <P>The information collection requirements specified in the 13 Carcinogens Standard protect employees from the adverse health effects that may result from their exposure to the 13 Carcinogens. The following is a brief description of the collection of information requirements contained in the 13 Carcinogens Standard: establishing and implementing a medical surveillance program for employees assigned to enter regulated areas, informing employees of their medical examination results and providing them with access to their medical records. Further, employers must also retain employee medical records for specified time periods and provide these records to the National Institute for Occupational Safety and Health (NIOSH) under certain circumstances. </P>
                <HD SOURCE="HD1">II. Special Issues for Comment </HD>
                <P>OSHA has a particular interest in comments on the following issues: </P>
                <P>• Whether the proposed information collection requirements are necessary for the proper performance of the Agency's functions, including whether the information is useful; </P>
                <P>• The accuracy of OSHA's estimate of the burden (time and costs) of the information collection requirements, including the validity of the methodology and assumptions used; </P>
                <P>• The quality, utility, and clarity of the information collected; and </P>
                <P>• Ways to minimize the burden on employers who must comply; for example, by using automated or other technological information collection and transmission techniques. </P>
                <HD SOURCE="HD1">III. Proposed Actions </HD>
                <P>OSHA is requesting that OMB extend its approval of the collection of information requirements contained in the 13 Carcinogens Standard (29 CFR 1910.1003). The Agency is requesting to reduce its current burden hour estimate associated with the Standard from 1,657 hours to 1,604 hours for a total reduction of −53 hours. The reduction is primarily the result of decreasing both the number of establishments (from 97 to 93 establishments) and the number of exposed employees (from 663 to 643). The Agency will include this summary in its request to OMB to extend the approval of these collection of information requirements. </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     13 Carcinogens Standard (29 CFR 1910.1003). 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1218-0085. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business or other for-profits; Federal Government; State, Local or Tribal Government. 
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     93. 
                </P>
                <P>
                    <E T="03">Total Responses:</E>
                     2,119. 
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     Time per response ranges from approximately 5 minutes (for employers to maintain records) to 2 hours (for records access and transfer). 
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     1,604. 
                </P>
                <P>
                    <E T="03">Estimated Cost (Operation and Maintenance):</E>
                     $88,816. 
                </P>
                <HD SOURCE="HD1">IV. Public Participation—Submission of Comments on This Notice and Internet Access to Comments and Submissions </HD>
                <P>You may submit comments and supporting materials in response to this notice by (1) Hard copy, (2) FAX transmission (facsimile), or (3) electronically through the OSHA Web site. Because of security-related problems, there may be a significant delay in the receipt of comments by regular mail. Please contact the OSHA Docket Office at (202) 693-2350 (TTY (877) 889-5627) for information about security procedures concerning the delivery of submissions by express delivery, hand delivery and courier service. </P>
                <P>
                    All comments, submissions and background documents are available for inspection and copying at the OSHA Docket Office at the above address. Comments and submissions posted on OSHA's Web site are available at 
                    <E T="03">http://www.OSHA.gov.</E>
                     Contact the OSHA Docket Office for information about materials not available through the OSHA Web site and for assistance in using the Internet to locate docket submissions. 
                </P>
                <P>
                    Electronic copies of this 
                    <E T="04">Federal Register</E>
                     notice as well as other relevant documents are available on OSHA's Web site. Since all submissions become public, personal information such as social security numbers and date of birth should not be submitted. 
                </P>
                <HD SOURCE="HD1">V. Authority and Signature </HD>
                <P>
                    Edwin G. Foulke, Jr., Assistant Secretary of Labor for Occupational Safety and Health, directed the preparation of this notice. The authority for this notice is the Paperwork Reduction Act of 1995 (44 U.S.C. 3506 
                    <E T="03">et seq.</E>
                    ) and Secretary of Labor's Order No. 5-2007 (72 FR 31159). 
                </P>
                <SIG>
                    <DATED>Signed at Washington, DC, this 22nd day of September 2008. </DATED>
                    <NAME>Edwin G. Foulke, Jr., </NAME>
                    <TITLE>Assistant Secretary of Labor for Occupational Safety and Health. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22664 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4510-26-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR </AGENCY>
                <SUBAGY>Occupational Safety and Health Administration </SUBAGY>
                <DEPDOC>[Docket No. OSHA-2008-0036] </DEPDOC>
                <SUBJECT>Inorganic Arsenic Standard; Extension of the Office of Management and Budget's (OMB) Approval of Information Collection (Paperwork) Requirements </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Occupational Safety and Health Administration (OSHA), Labor. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for public comment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>OSHA solicits comments concerning its proposal to extend OMB approval of the information collection requirements contained in the Inorganic Arsenic Standard (29 CFR 1910.1018). </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted (postmarked, sent, or received) by November 25, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> </P>
                    <P>
                        <E T="03">Electronically:</E>
                         You may submit comments and attachments electronically at 
                        <E T="03">http://www.regulations.gov</E>
                        , which is the Federal eRulemaking Portal. Follow the instructions online for submitting comments. 
                    </P>
                    <P>
                        <E T="03">Facsimile:</E>
                         If your comments, including attachments, are not longer than 10 pages, you may fax them to the OSHA Docket Office at (202) 693-1648. 
                    </P>
                    <P>
                        <E T="03">Mail, hand delivery, express mail, messenger, or courier service:</E>
                         When using this method, you must submit three copies of your comments and attachments to the OSHA Docket Office, Docket No. OSHA-2008-0036, U.S. 
                        <PRTPAGE P="55872"/>
                        Department of Labor, Occupational Safety and Health Administration, Room N-2625, 200 Constitution Avenue, NW., Washington, DC 20210. Deliveries (hand, express mail, messenger, and courier service) are accepted during the Department of Labor's and Docket Office's normal business hours, 8:15 a.m. to 4:45 p.m., e.t. 
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions must include the Agency name and OSHA docket number for the ICR (OSHA-2008-0036). All comments, including any personal information you provide, are placed in the public docket without change, and may be made available online at 
                        <E T="03">http://www.regulations.gov.</E>
                         For further information on submitting comments see the “Public Participation” heading in the section of this notice titled “
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        .” 
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         To read or download comments or other material in the docket, go to 
                        <E T="03">http://www.regulations.gov</E>
                         or the OSHA Docket Office at the address above. All documents in the docket (including this 
                        <E T="04">Federal Register</E>
                         notice) are listed in the http://www.regulations.gov index; however, some information (e.g., copyrighted material) is not publicly available to read or download through the Web site. All submissions, including copyrighted material, are available for inspection and copying at the OSHA Docket Office. You may contact Jamaa Hill at the address below to obtain a copy of the ICR. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jamaa N. Hill or Todd Owen, Directorate of Standards and Guidance, OSHA, U.S. Department of Labor, Room N-3609, 200 Constitution Avenue, NW., Washington, DC 20210; telephone (202) 693-2222. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background </HD>
                <P>
                    The Department of Labor, as part of its continuing efforts to reduce paperwork and respondent (
                    <E T="03">i.e.</E>
                    , employer) burden, conducts a preclearance consultation program to provide the public with an opportunity to comment on proposed and continuing information collection requirements in accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3506(c)(2)(A)). This program ensures that information is in the desired format, reporting burden (time and costs) is minimal, collection instruments are clearly understood, and OSHA's estimate of the information collection burden is accurate. The Occupational Safety and Health Act of 1970 (the OSH Act) (29 U.S.C. 651 
                    <E T="03">et seq.</E>
                    ) authorizes information collection by employers as necessary or appropriate for enforcement of the OSH Act or for developing information regarding the causes and prevention of occupational injuries, illnesses, and accidents (29 U.S.C. 657). The OSH Act also requires that OSHA obtain such information with minimum burden upon employers, especially those operating small businesses, and to reduce to the maximum extent feasible unnecessary duplication of efforts in obtaining information (29 U.S.C. 657). The information collection requirements in the Inorganic Arsenic Standard provide protection for employees from the adverse health effects associated with exposure to inorganic arsenic. The Inorganic Arsenic Standard requires employers to: Monitor employees' exposure to inorganic arsenic; monitor employee health; develop and maintain employee exposure monitoring and medical records; establish and implement written compliance programs; and provide employees with information about their exposures and health effects of exposure to inorganic arsenic. 
                </P>
                <HD SOURCE="HD1">II. Special Issues for Comment </HD>
                <P>OSHA has a particular interest in comments on the following issues: </P>
                <P>• Whether the proposed information collection requirements are necessary for the proper performance of the Agency's functions, including whether the information is useful; </P>
                <P>• The accuracy of OSHA's estimate of the burden (time and costs) of the information collection requirements, including the validity of the methodology and assumptions used; </P>
                <P>• The quality, utility, and clarity of the information collected; and </P>
                <P>• Ways to minimize the burden on employers who must comply; for example, by using automated or other technological information collection and transmission techniques. </P>
                <HD SOURCE="HD1">III. Proposed Actions </HD>
                <P>OSHA is requesting that OMB extend its approval of the information collection requirements contained in the Inorganic Arsenic Standard (29 CFR 1910.1018). OSHA is proposing to decrease its current burden hour estimate of 4,861 to 385, a total decrease of −4,476 hours. The Agency reduced the number of employers covered by the standard from 42 employers to 3 employers as a result of a significant decline in arsenic consumption in the United States. </P>
                <P>The Agency will summarize the comments submitted in response to this notice and will include this summary in the request to OMB. </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Standard on Inorganic Arsenic (29 CFR 1910.1018). 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1218-0104. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business or other for-profits; Federal Government; State, Local, or Tribal Government. 
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     3. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Average Time per Response:</E>
                     Time per response ranges from 5 minutes to maintain records to 1.67 hours to complete a medical examination. 
                </P>
                <P>
                    <E T="03">Estimated Total  Burden Hours:</E>
                     385. 
                </P>
                <P>
                    <E T="03">Estimated Cost  (Operation and  Maintenance):</E>
                     $31,165. 
                </P>
                <HD SOURCE="HD1">IV. Public Participation—Submission of Comments on This Notice and Internet Access to Comments and Submissions </HD>
                <P>
                    You may submit comments in response to this document as follows: (1) Electronically at 
                    <E T="03">http://www.regulations.gov,</E>
                     which is the Federal eRulemaking Portal; (2) by facsimile (FAX); or (3) by hard copy. All comments, attachments, and other material must identify the Agency name and the OSHA docket number for the ICR (Docket No. OSHA-2008-0036). You may supplement electronic submissions by uploading document files electronically. If you wish to mail additional materials in reference to an electronic or facsimile submission, you must submit them to the OSHA Docket Office (see the section of this notice titled 
                    <E T="02">ADDRESSES</E>
                    ). The additional materials must clearly identify your electronic comments by your name, date, and the docket number so the Agency can attach them to your comments. 
                </P>
                <P>Because of security procedures, the use of regular mail may cause a significant delay in the receipt of comments. For information about security procedures concerning the delivery of materials by hand, express delivery, messenger, or courier service, please contact the OSHA Docket Office at (202) 693-2350 (TTY (877) 889-5627). </P>
                <P>
                    Comments and submissions are posted without change at 
                    <E T="03">http://www.regulations.gov.</E>
                     Therefore, OSHA cautions commenters about submitting personal information such as social security numbers and date of birth. Although all submissions are listed in the 
                    <E T="03">http://www.regulations.gov</E>
                     index, some information (e.g., copyrighted material) is not publicly available to read or download through this Web site. All submissions, including copyrighted material, are available for inspection 
                    <PRTPAGE P="55873"/>
                    and copying at the OSHA Docket Office. Information on using the 
                    <E T="03">http://www.regulations.gov</E>
                     Web site to submit comments and access the docket is available at the Web site's “User  Tips” link. Contact the OSHA Docket Office for information about materials not available through the Web site, and for assistance in using the Internet to locate docket submissions. 
                </P>
                <HD SOURCE="HD1">V. Authority and Signature </HD>
                <P>
                    Edwin G. Foulke, Jr., Assistant Secretary of Labor for Occupational Safety and Health, directed the preparation of this notice. The authority for this notice is the Paperwork Reduction Act of 1995 (44 U.S.C. 3506 
                    <E T="03">et seq.</E>
                    ) and Secretary of Labor's Order No. 5-2007 (72 FR 31159). 
                </P>
                <SIG>
                    <DATED>Signed at Washington, DC, this 22nd day of September 2008. </DATED>
                    <NAME>Edwin G. Foulke, Jr., </NAME>
                    <TITLE>Assistant Secretary of Labor for Occupational Safety and Health. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22666 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4510-26-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR </AGENCY>
                <SUBAGY>Veterans Employment and Training Service </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: New Collection; Comment Request; 60-Day Notice of Information Collection Under Review: Homeless Veterans Reintegration Program Data Collection and Effectiveness Study.</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Labor, Veterans Employment and Training Service published a document in the 
                        <E T="04">Federal Register</E>
                        . Agency Information Collection Activities: New Collection; Comment Request Action: 60-Day Notice of Information Collection Under Review: Homeless Veterans Reintegration Program Data Collection and Effectiveness Study. The Department is issuing a restructured a paragraph for clarification purposes.
                    </P>
                    <HD SOURCE="HD1">Correction </HD>
                    <P>
                        This is to correct the “text” caption in the 
                        <E T="04">Federal Register</E>
                         of on August 15, 2008, Volume 73, Number 159, and OFR Doc # 2008-18858, on page 47981, in section marked Date, to read: 
                        <E T="02">DATES</E>
                        : The Department will accept comments from the public up to 60 from publication of notice. 
                    </P>
                </SUM>
                <SIG>
                    <DATED>Signed in Washington, DC, this 19th day of September 2008. </DATED>
                    <NAME>Charles S. Ciccolella, </NAME>
                    <TITLE>Assistant Secretary, Veterans Employment and Training Service.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22512 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4510-79-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION </AGENCY>
                <DEPDOC>[Docket No. 03031655] </DEPDOC>
                <SUBJECT>Notice of Availability of Environmental Assessment and Finding of No Significant Impact for License Amendment Request to Byproduct Materials License No. 45-03499-08 for the College of William and Mary, Williamsburg, VA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Issuance of Environmental Assessment and Finding of No Significant Impact for License Amendment. </P>
                </ACT>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Thomas K. Thompson, Senior Health Physicist, Commercial and R&amp;D Branch, Division of Nuclear Materials Safety, Region I, 475 Allendale Road, King of Prussia, Pennsylvania; telephone: (610) 337-5303; fax number: (610) 337-5269; or by e-mail: 
                        <E T="03">Thomas.Thompson@nrc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Introduction </HD>
                <P>
                    The U.S. Nuclear Regulatory Commission (NRC) is considering the issuance of a license renewal to Byproduct Materials License No. 45-03499-08. This license is held by The College of William and Mary (the Licensee) in Williamsburg, Virginia. As part of its license renewal, the Licensee has requested an exemption from the requirement in 10 CFR 30.32(g) to list sealed sources by their manufacturer and model number as registered under the provisions of 10 CFR 32.210. The Licensee requested this exemption in a letter dated October 31, 2005. The NRC has prepared an Environmental Assessment (EA) in support of this proposed action in accordance with the requirements of Title 10, Code of Federal Regulations (CFR), Part 51 (10 CFR Part 51). Based on the EA, the NRC has concluded that a Finding of No Significant Impact (FONSI) is appropriate with respect to the proposed action. The license renewal, including the approval of the exemption request, will be issued to the Licensee following the publication of this FONSI and EA in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">II. Environmental Assessment </HD>
                <HD SOURCE="HD2">Identification of Proposed Action </HD>
                <P>The proposed action would renew License No. 45-03499-08, including approval of the Licensee's request for exemption submitted on October 31, 2005. License No. 45-03499-08 was issued on September 14, 1990, pursuant to 10 CFR Parts 30 and 70, and has been amended periodically since that time. This license authorized the Licensee for laboratory research, calibration, and teaching and training of students. It also authorized the possession of neutron sources containing plutonium for storage incident to disposal. </P>
                <P>On June 29, 2005, the Licensee submitted its renewal application for License No. 45-03499-08. In a letter dated October 31, 2005, submitted in response to an inquiry from the NRC, the Licensee requested an exemption from the requirement in 10 CFR 30.32(g) to list sealed sources by manufacturer and model number as registered under the provisions of 10 CFR 32.210. In requesting this exemption, the Licensee states that most of its source inventory consists of sealed sources which have long been in their possession and that most do not bear a manufacturer's name or model number, and that it therefore would be unable to provide that information. </P>
                <HD SOURCE="HD2">Need for the Proposed Action </HD>
                <P>The Licensee possesses neutron sources containing plutonium being held for disposal, and other sources of low activity, less than a millicurie each, and has possessed and used these sources for many years without incident. This exemption is needed to authorize the Licensee to continue to possess these sources. </P>
                <HD SOURCE="HD2">Technical Analysis of the Proposed Action </HD>
                <P>
                    10 CFR 30.11(a) states that the Commission may grant such exemptions from the requirements of the regulations as it determines are authorized by law and will not endanger life or property or the common defense and security and are otherwise in the public interest. The NRC staff has analyzed the Licensee's request to be authorized to receive and take possession of sealed sources and devices which have not been registered with the NRC under 10 CFR 32.210 or with an Agreement State. The NRC staff considered that the Licensee is qualified by sufficient training and experience and has sufficient facilities and equipment to handle these sources and 
                    <PRTPAGE P="55874"/>
                    devices. Furthermore, NRC inspections have evaluated the Licensee's performance and determined that the Licensee has safely handled these unregistered sources for many years. Accordingly, the NRC staff has concluded that granting this exemption is authorized by law and will not endanger life or property or the common defense and security, and is in the public interest. 
                </P>
                <HD SOURCE="HD2">Environmental Impacts of the Proposed Action </HD>
                <P>The proposed action is largely administrative in nature. The Licensee has handled sources and devices which have not been registered by the NRC under 10 CFR 32.210, or by an Agreement State, for many years. The Licensee is qualified by sufficient training and experience and has sufficient facilities and equipment to handle these sources and devices. Approving this exemption will have no environmental impact. </P>
                <HD SOURCE="HD2">Environmental Impacts of the Alternatives to the Proposed Action </HD>
                <P>Due to the largely administrative nature of the proposed action, its environmental impacts are small. Additionally, denying the exemption request would result in no change in current environmental impacts. The environmental impacts of the proposed action and the no-action alternative are therefore similar, and the no-action alternative is accordingly not further considered. </P>
                <HD SOURCE="HD2">Conclusion </HD>
                <P>The NRC staff has concluded that the proposed action will not significantly impact the quality of the human environment; the NRC staff concludes that the proposed action is the preferred alternative. </P>
                <HD SOURCE="HD2">Agencies and Persons Consulted </HD>
                <P>The NRC staff has determined that the proposed action is of a procedural nature, and will not affect listed species or critical habitat. Therefore, no further consultation is required under Section 7 of the Endangered Species Act. The NRC staff has also determined that the proposed action is not the type of activity that has the potential to cause effects on historic properties. Therefore, no further consultation is required under Section 106 of the National Historic Preservation Act. </P>
                <HD SOURCE="HD1">III. Finding of No Significant Impact </HD>
                <P>The NRC staff has prepared this EA in support of the proposed action. On the basis of this EA, the NRC finds that there are no significant environmental impacts from the proposed action, and that preparation of an environmental impact statement is not warranted. Accordingly, the NRC has determined that a Finding of No Significant Impact is appropriate. </P>
                <HD SOURCE="HD1">IV. Further Information </HD>
                <P>
                    Documents related to this action, including the application for exemption and supporting documentation, are available electronically at the NRC's Electronic Reading Room at 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>
                     From this site, you can access the NRC's Agencywide Document Access and Management System (ADAMS), which provides text and image files of NRC's public documents. The documents related to this action are listed below, along with their ADAMS accession numbers. 
                </P>
                <P>1. License renewal application dated June 29, 2005 [ML052130136] </P>
                <P>2. Licensee letter dated October 31, 2005 [ML053130381] </P>
                <P>
                    If you do not have access to ADAMS, or if there are problems in accessing the documents located in ADAMS, contact the NRC Public Document Room (PDR) Reference staff at 1-800-397-4209, 301-415-4737, or by e-mail to 
                    <E T="03">pdr@nrc.gov.</E>
                     These documents may also be viewed electronically on the public computers located at the NRC's PDR, O1 F21, One White Flint North, 11555 Rockville Pike, Rockville, MD 20852. The PDR reproduction contractor will copy documents for a fee. 
                </P>
                <SIG>
                    <DATED>Dated at Region I, 475 Allendale Road, King of Prussia, PA, this 11th day of September, 2008. </DATED>
                    <P>For the Nuclear Regulatory Commission. </P>
                    <NAME>James P. Dwyer, </NAME>
                    <TITLE>Chief, Commercial and R&amp;D Branch, Division of Nuclear Materials Safety, Region I.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22689 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7590-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION </AGENCY>
                <DEPDOC>[Docket No. 030-11789] </DEPDOC>
                <SUBJECT>Notice of Environmental Assessment Related to the Issuance of a License Amendment to Byproduct Material License No. 24-00196-07, for Unrestricted Release of a Facility for Saint Louis University, St. Louis, MO</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Issuance of Environmental Assessment and Finding of No Significant Impact for License Amendment. </P>
                </ACT>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        George M. McCann, Senior Health Physicist, Decommissioning Branch, Division of Nuclear Materials Safety, Region III, U.S. Nuclear Regulatory Commission, 2443 Warrenville Road, Lisle, Illinois 60532; telephone: (630) 829-9856; fax number: (630) 515-1259; or by e-mail at 
                        <E T="03">Mike.McCann@nrc.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Introduction </HD>
                <P>The U.S. Nuclear Regulatory Commission (NRC) is considering the issuance of an amendment to terminate NRC Byproduct Materials License No. 24-00196-07, which is held by Saint Louis University (licensee). The issuance of the amendment would authorize the unrestricted release of the licensee's Institute for Molecular Virology (the facility), which consists of a 25,000 square foot building located on the licensee's campus at 3681 Park Avenue, St. Louis, Missouri. </P>
                <P>
                    The NRC has prepared an Environmental Assessment (EA) in support of this proposed action in accordance with the requirements of Title 10, Code of Federal Regulations (CFR), Part 51 (10 CFR Part 51). Based on the EA, the NRC has concluded that a Finding of No Significant Impact (FONSI) is appropriate with respect to the proposed action. The amendment will be issued to the Licensee following the publication of this FONSI and EA in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">II. Environmental Assessment </HD>
                <HD SOURCE="HD2">Identification of Proposed Action </HD>
                <P>The proposed action would approve the licensee's request to release the facility for unrestricted use in accordance with 10 CFR Part 20, Subpart E. The Licensee requested this action in a letter dated July 9, 2008 (ADAMS Accession Number ML081930612). The license was issued on January 16, 1976, pursuant to 10 CFR Part 30, and has been amended periodically since that time. This license authorized the Licensee to use unsealed byproduct materials for conducting research and development activities involving medical research, diagnostic and therapy medical procedures, laboratory studies and educational programs in the areas of molecular virology, viral oncology, and cancer biology. </P>
                <P>
                    The licensee performed a Historical Site Assessment (HSA) in May and June of 2008. The purpose of the HSA was to determine the current status of the facility including potential, likely, or known sources of radioactive contamination by gathering data from 
                    <PRTPAGE P="55875"/>
                    various sources. This data included physical characteristics and location of the site as well as information gathered from personnel interviews and inspection of site operating records, and from radiological surveys. Records reviewed included: radioactive materials licenses, license applications, amendment requests, meeting minutes, radiological surveys, radionuclide receipt and distribution records, incident reports, facility renovation records, blueprints, plans and design specifications. Personnel interviews included radiation safety, research, maintenance, operations, and facilities personnel. Current employees having knowledge of facility historical operations were interviewed. 
                </P>
                <P>The licensee did not dispose of radioactive waste via on-site burial. All waste containing long lived radioisotopes was shipped offsite to a licensed landfill, approved to receive and dispose of radioactive materials. No waste-related environmental concerns were identified during the record search or interviews of the radiation safety staff. There were no recorded spills or loss of control that required additional investigation. </P>
                <P>Decontamination of the facility was completed on June 20, 2008. The licensee's “SLU IMV Final Status Report, Rev 4.pdf Institute for Molecular Virology Decommissioning Final Status Report,” dated June 24, 2008 (ML081930612), was submitted to the NRC on July 9, 2008. </P>
                <P>Based on the Licensee's survey results it was determined that only routine decontamination activities, in accordance with the licensee's NRC-approved, operating radiation safety procedures, were required. The Licensee was not required to submit a decommissioning plan to the NRC because worker cleanup activities and procedures are consistent with those approved for routine operations. The Licensee conducted surveys of the facility and provided information to the NRC to demonstrate that it meets the criteria in Subpart E of 10 CFR Part 20 for unrestricted release. </P>
                <HD SOURCE="HD2">Need for the Proposed Action </HD>
                <P>The licensee has ceased conducting licensed activities at its facility and seeks the termination of its NRC license. </P>
                <HD SOURCE="HD2">Environmental Impacts of the Proposed Action </HD>
                <P>The historical review of licensed activities conducted at the Facility shows that such activities involved use of the following radionuclides with half-lives greater than 120 days: Hydrogen-3 and carbon-14. Prior to performing the final status survey, the Licensee conducted radiation surveys and decontamination activities, as necessary, in the areas of the Facility affected by these radionuclides. </P>
                <P>The Licensee conducted a final status survey between June 17 and June 20, 2008, in the facility. The licensee's surveys included the liquid drain, ventilation exhaust and vacuum systems. No areas were considered to have a potential for delivering a dose to the public above the release criteria. </P>
                <P>The Licensee elected to demonstrate compliance with the radiological criteria for unrestricted release as specified in 10 CFR 20.1402 by using the screening approach described in NUREG-1757, “Consolidated NMSS Decommissioning Guidance,” Volume 2. The Licensee used the radionuclide-specific derived concentration guideline levels (DCGLs), developed there by the NRC, which comply with the dose criterion in 10 CFR 20.1402. These DCGLs define the maximum amount of residual radioactivity on building surfaces, equipment, and materials, and in soils, that will satisfy the NRC requirements in Subpart E of 10 CFR Part 20 for unrestricted release. The Licensee's final status survey results were below these DCGLs and are in compliance with the As Low As Reasonably Achievable (ALARA) requirement of 10 CFR 20.1402. The NRC thus finds that the Licensee's final status survey results are acceptable. </P>
                <P>Based on its review, the staff has determined that the affected environment and any environmental impacts associated with the proposed action are bounded by the impacts evaluated by the “Generic Environmental Impact Statement in Support of Rulemaking on Radiological Criteria for License Termination of NRC-Licensed Nuclear Facilities” (NUREG-1496) Volumes 1-3 (ML042310492, ML042320379, and ML042330385). The staff finds there were no significant environmental impacts from the use of radioactive material at the Facility. The NRC staff reviewed the docket file records and the final status survey report to identify any non-radiological hazards that may have impacted the environment surrounding the Facility. No such hazards or impacts to the environment were identified. The NRC has identified no other radiological or non-radiological activities in the area that could result in cumulative environmental impacts. </P>
                <P>The NRC staff finds that the proposed release of the Facility for unrestricted use is in compliance with 10 CFR 20.1402. Based on its review, the staff considered the impact of the residual radioactivity at the Facility and concluded that the proposed action will not have a significant effect on the quality of the human environment. </P>
                <HD SOURCE="HD2">Environmental Impacts of the Alternatives to the Proposed Action </HD>
                <P>Due to the largely administrative nature of the proposed action, its environmental impacts are small. Therefore, the only alternative the staff considered is the no-action alternative, under which the staff would leave things as they are by simply denying the amendment request. This no-action alternative is not feasible because it conflicts with 10 CFR 30.36(d) requiring that decommissioning of byproduct material facilities be completed and approved by the NRC after licensed activities cease. The NRC's analysis of the Licensee's final status survey data confirmed that the Facility meets the requirements of 10 CFR 20.1402 for unrestricted release. Additionally, denying the amendment request would result in no change in current environmental impacts. The environmental impacts of the proposed action and the no-action alternative are therefore similar, and the no-action alternative is accordingly not further considered. </P>
                <HD SOURCE="HD2">Conclusion </HD>
                <P>The NRC staff has concluded that the proposed action is consistent with the NRC's unrestricted release criteria specified in 10 CFR 20.1402. Because the proposed action will not significantly impact the quality of the human environment, the NRC staff concludes that the proposed action is the preferred alternative. </P>
                <HD SOURCE="HD2">Agencies and Persons Consulted </HD>
                <P>The NRC provided a draft of this Environmental Assessment to the Missouri Department of Health and Senior Services Waste, Division of Community and Public Health, Office of Emergency Coordination on September 3, 2008. On September 4, 2008, the State responded by telephone to the NRC indicating that the State did not have any comments or concerns regarding the release of the licensee's facility. </P>
                <P>
                    The NRC staff has determined that the proposed action is of a procedural nature, and will not affect listed species or critical habitat. Therefore, no further consultation is required under Section 7 of the Endangered Species Act. The NRC staff has also determined that the proposed action is not the type of activity that has the potential to cause effects on historic properties. Therefore, no further consultation is required 
                    <PRTPAGE P="55876"/>
                    under Section 106 of the National Historic Preservation Act. 
                </P>
                <HD SOURCE="HD1">III. Finding of No Significant Impact </HD>
                <P>The NRC staff has prepared this EA in support of the proposed action. On the basis of this EA, the NRC finds that there are no significant environmental impacts from the proposed action, and that preparation of an environmental impact statement is not warranted. Accordingly, the NRC has determined that a Finding of No Significant Impact is appropriate. </P>
                <HD SOURCE="HD1">IV. Further Information </HD>
                <P>
                    Documents related to this action, including the application for license amendment and supporting documentation, are available electronically at the NRC's Electronic Reading Room at 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>
                     From this site, you can access the NRC's Agencywide Document Access and Management System (ADAMS), which provides text and image files of NRC's public documents. The documents related to this action are listed below, along with their ADAMS accession numbers. 
                </P>
                <P>1. Mark Haenschen, M.S., J.D., letter to U.S. Nuclear Regulatory Commission, Region III, dated July 9, 2008 (ADAMS Accession No. ML081930612). </P>
                <P>2. Title 10 Code of Federal Regulations, Part 20, Subpart E, “Radiological Criteria for License Termination;” </P>
                <P>3. Title 10 Code of Federal Regulations, Part 51, “Environmental Protection Regulations for Domestic Licensing and Related Regulatory Functions;” </P>
                <P>4. NUREG-1496, “Generic Environmental Impact Statement in Support of Rulemaking on Radiological Criteria for License Termination of NRC-Licensed Nuclear Facilities;” NUREG-1757, Consolidated Decommissioning Guidance. </P>
                <P>
                    If you do not have access to ADAMS, or if there are problems in accessing the documents located in ADAMS, contact the NRC Public Document Room (PDR) Reference staff at 1-800-397-4209, 301-415-4737, or by e-mail to 
                    <E T="03">pdr.resource@nrc.gov.</E>
                     These documents may also be viewed electronically on the public computers located at the NRC's PDR, O 1 F21, One White Flint North, 11555 Rockville Pike, Rockville, MD 20852. The PDR reproduction contractor will copy documents for a fee. 
                </P>
                <SIG>
                    <DATED>Dated at Lisle, Illinois, this 16th day of September 2008. </DATED>
                    <P>For the Nuclear Regulatory Commission. </P>
                    <NAME>Christine A. Lipa, </NAME>
                    <TITLE>Chief, Decommissioning Branch, Division of Nuclear Materials Safety, Region III.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22687 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7590-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION </AGENCY>
                <DEPDOC>[Docket No. 52-016] </DEPDOC>
                <SUBJECT>Calvert Cliffs 3 Nuclear Project, LLC, and Unistar Nuclear Operating Services, LLC  Notice of Hearing and Opportunity To Petition for Leave To Intervene and Order Imposing Procedures for Access to Sensitive Unclassified Non-Safeguards Information and Safeguards Information for Contention Preparation on a Combined License for the Calvert Cliffs Nuclear Power Plant Unit 3 </SUBJECT>
                <P>
                    Pursuant to the Atomic Energy Act of 1954, as amended, and the regulations in Title 10 of the 
                    <E T="03">Code of Federal Regulations</E>
                     (10 CFR) Part 2, “Rules of Practice for Domestic Licensing Proceedings and Issuance of Orders,” 10 CFR Part 50, “Domestic Licensing of Production and Utilization Facilities,” and 10 CFR Part 52, Licenses, Certifications, and Approvals for Nuclear Power Plants,” notice is hereby given that a hearing will be held, at a time and place to be set in the future by the U.S. Nuclear Regulatory Commission (NRC, the Commission) or designated by the Atomic Safety and Licensing Board (Board). The hearing will consider the application dated July 13, 2007, and March 14, 2008, filed by Constellation Generation Group, LLC, and UniStar Nuclear Operating Services, LLC (CGG and UniStar), pursuant to Subpart C of 10 CFR Part 52 for a combined license (COL). The application was supplemented by letters dated July 16, August 2, September 11, October 30, December 14, 2007, and January 14, March 3, March 14, May 15, May 30, June 20, July 31, August 18 and August 19, 2008. The application was revised by letter dated August 20, 2008, which among other things changed the applicants to Calvert Cliffs 3 Nuclear Project, LLC, and UniStar Nuclear Operating Services, LLC. The application requests approval of a COL for Calvert Cliffs Nuclear Power Plant Unit 3, to be located in Calvert County, Maryland. The two parts of the application were accepted for docketing on January 25, 2008 (73 FR 5877, January 31, 2008) and June 3, 2008 (73 FR 32606, June 9, 2008). The docket number established for this COL application is 52-016. The Calvert Cliffs COL application incorporates by reference the application for a Standard Design Certification for the U.S. EPR, which was submitted to the NRC by AREVA NP on December 11, 2007, and supplemented by AREVA on February 7, 2008, and February 18, 2008. The Standard Design Certification for the U.S. EPR is the subject of an ongoing rulemaking under docket number 52-020. By letter to AREVA dated February 25, 2008, the staff has accepted the Standard Design Certification for the U.S. EPR for docketing. 
                </P>
                <P>
                    The hearing on the COL application will be conducted by a Board that will be designated by the Chairman of the Atomic Safety and Licensing Board Panel or will be conducted by the Commission. Notice as to the membership of the Board will be published in the 
                    <E T="04">Federal Register</E>
                     at a later date. The NRC staff will complete a detailed technical review of the COL application and will document its findings in a safety evaluation report. The Commission will refer a copy of the COL application to the Advisory Committee on Reactor Safeguards (ACRS) in accordance with 10 CFR 52.87, “Referral to the ACRS,” and the ACRS will report on those portions of the application that concern safety. 
                </P>
                <P>Any person whose interest may be affected by this proceeding and who desires to participate as a party to this proceeding must file a written petition for leave to intervene in accordance with 10 CFR 2.309. Those permitted to intervene become parties to the proceeding, subject to any limitations in the order granting leave to intervene, and have the opportunity to participate fully in the conduct of the hearing. </P>
                <P>All documents filed in NRC adjudicatory proceedings, including a request for hearing, a petition for leave to intervene, any motion or other document filed in the proceeding prior to the submission of a request for hearing or petition to intervene, and documents filed by interested governmental entities participating under 10 CFR 2.315(c), must be filed in accordance with the NRC E-Filing rule, which the NRC promulgated in August 28, 2007, (72 FR 49139). The E-Filing process requires participants to submit and serve all adjudicatory documents over the internet, or in some cases to mail copies on electronic storage media. Participants may not submit paper copies of their filings unless they seek an exemption in accordance with the procedures described below. </P>
                <P>
                    To comply with the procedural requirements of E-Filing, at least 10 days prior to the filing deadline, the petitioner must contact the Office of the 
                    <PRTPAGE P="55877"/>
                    Secretary by e-mail at 
                    <E T="03">HearingDocket@nrc.gov,</E>
                     or by calling (301) 415-1677, to request (1) a digital ID certificate, which allows the participant (or its counsel or representative) to digitally sign documents and access the E-Submittal server for any proceeding in which it is participating; and/or (2) creation of an electronic docket for the proceeding (even in instances in which the petitioner (or its counsel or representative) already holds an NRC-issued digital ID certificate). Each participant will need to download the Workplace Forms Viewer 
                    <SU>TM</SU>
                     to access the Electronic Information Exchange (EIE), a component of the E-Filing system. The Workplace Forms Viewer 
                    <SU>TM</SU>
                     is free and is available at 
                    <E T="03">http://www.nrc.gov/site-help/e-submittals/install-viewer.html.</E>
                     Information about applying for a digital ID certificate is available on NRC's public Web site at 
                    <E T="03">http://www.nrc.gov/site-help/e-submittals/apply-certificates.html.</E>
                </P>
                <P>
                    Once a participant has obtained a digital ID certificate, had a docket created, and downloaded the EIE viewer, it can then submit a petition for leave to intervene. Submissions should be in Portable Document Format (PDF) in accordance with NRC guidance available on the NRC public Web site at 
                    <E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>
                     A filing is considered complete at the time the filer submits its documents through EIE. To be timely, an electronic filing must be submitted to the EIE system no later than 11:59 p.m. Eastern Time on the due date. Upon receipt of a transmission, the E-Filing system time-stamps the document and sends the submitter an e-mail notice confirming receipt of the document. The EIE system also distributes an e-mail notice that provides access to the document to the NRC Office of the General Counsel and any others who have advised the Office of the Secretary that they wish to participate in the proceeding, so that the filer need not serve the documents on those participants separately. Therefore, applicants and other participants (or their counsel or representative) must apply for and receive a digital ID certificate before a petition to intervene is filed so that they can obtain access to the document via the E-Filing system. 
                </P>
                <P>
                    A person filing electronically may seek assistance through the “Contact Us” link located on the NRC Web site at 
                    <E T="03">http://www.nrc.gov/site-help/e-submittals.html</E>
                     or by calling the NRC technical help line, which is available between 8:30 a.m. and 4:15 p.m., Eastern Time, Monday through Friday. The help line number is (800) 397-4209 or locally, (301) 415-4737. 
                </P>
                <P>Participants who believe that they have a good cause for not submitting documents electronically must file an exemption request, in accordance with 10 CFR 2.302(g), with their initial paper filing requesting authorization to continue to submit documents in paper format. Such filings must be submitted by: (1) First class mail addressed to the Office of the Secretary of the Commission, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemaking and Adjudications Staff; or (2) courier, express mail, or expedited delivery service to the Office of the Secretary, Sixteenth Floor, One White Flint North, 11555 Rockville Pike, Rockville, Maryland, 20852, Attention: Rulemaking and Adjudications Staff. Participants filing a document in this manner are responsible for serving the document on all other participants. Filing is considered complete by first-class mail as of the time of deposit in the mail, or by courier, express mail, or expedited delivery service upon depositing the document with the provider of the service. </P>
                <P>Non-timely requests and/or petitions and contentions will not be entertained absent a determination by the Commission, the presiding officer, or the Atomic Safety and Licensing Board that the petition and/or request should be granted and/or the contentions should be admitted based on a balancing of the factors specified in 10 CFR 2.309(c)(1)(i)-(viii). To be timely, filings must be submitted no later than 11:59 p.m. Eastern Time on the due date. </P>
                <P>
                    Documents submitted in adjudicatory proceedings will appear in the NRC's electronic hearing docket which is available to the public at (
                    <E T="03">http://ehd.nrc.gov/EHD_Proceeding/home.asp</E>
                    ), unless excluded pursuant to an order of the Commission, an Atomic Safety and Licensing Board, or a Presiding Officer. Participants are requested not to include personal privacy information, such as social security numbers, home addresses, or home phone numbers in their filings. With respect to copyrighted works, except for limited excerpts that serve the purpose of the adjudicatory filings and would constitute a Fair Use application, participants are requested not to include copyrighted materials in their submission. 
                </P>
                <P>
                    Petitions for leave to intervene must be filed no later than 60 days from the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . Non-timely filings will not be entertained absent a determination by the Commission or Board designated to rule on the petition, pursuant to the requirements of 10 CFR 2.309(c)(1)(i)-(viii). 
                </P>
                <P>A person who is not a party may be permitted to make a limited appearance by making an oral or written statement of his position, which need not be submitted to the agency using the E-Filing process, regarding the issues at any session of the hearing or any pre-hearing conference within the limits and conditions fixed by the presiding officer, but may not otherwise participate in the proceeding. </P>
                <P>
                    Any person who files a motion pursuant to 10 CFR 2.323 must consult with counsel for the applicant and counsel for the NRC staff who are listed below. Counsel for the applicant is Carey W. Fleming, (410) 470-5703, 
                    <E T="03">carey.fleming@constellation.com.</E>
                     Counsel for the NRC staff in this proceeding is James P. Biggins, (301) 415-6305, 
                    <E T="03">james.biggins@nrc.gov.</E>
                </P>
                <P>
                    Documents may be examined, and/or copied for a fee, at the NRC's Public Document Room (PDR), located at One White Flint North, Public File Area O1 F21, 11555 Rockville Pike (first floor), Rockville, Maryland, and will be accessible electronically through the Agencywide Documents Access and Management System (ADAMS) Public Electronic Reading Room link at the NRC Web site 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>
                     Persons who do not have access to ADAMS or who encounter problems in accessing documents located in ADAMS should contact the NRC PDR Reference staff by telephone at 1-800-397-4209, 301-415-4737, or by e-mail to 
                    <E T="03">pdr.resource@nrc.gov.</E>
                     The application is available at 
                    <E T="03">http://www.nrc.gov/reactors/new-licensing/col/calvert-cliffs.html.</E>
                     The ADAMS accession number for the COL application cover letters are ML071980294, ML080990114 and ML082390786. The ADAMS accession numbers for the supplements to the application are ML071980294, ML073520191, ML072000363, ML072200533, ML072560022, ML073060128, ML080160244, ML080660622, ML081410279, ML081550221, ML081760197, ML082170395, ML082330105 and ML082340693. To search for documents in ADAMS using the Calvert Cliffs COL application docket number, 52-016, enter the term “05200016” in the “Docket Number” field when using either the web-based search (advanced search) engine or the ADAMS find tool in Citrix. In the case of information contained in the supplemental letters the actual data can be obtained by contacting the NRC PDR. 
                    <PRTPAGE P="55878"/>
                </P>
                <P>
                    The application for a Standard Design Certification for the U.S. EPR, can be found using ADAMS accession number ML073531802 or by going to 
                    <E T="03">http://www.nrc.gov/reactors/new-licensing/design-cert/epr.html.</E>
                     To search for documents in ADAMS using the EPR DC docket number, 52-020, enter the term “05200020” in the ADAMS “Docket Number” field. 
                </P>
                <HD SOURCE="HD1">Order Imposing Procedures for Access to Sensitive Unclassified Non-Safeguards Information and Safeguards Information for Contention Preparation </HD>
                <P>1. This order contains instructions regarding how potential parties to this proceeding may request access to documents containing sensitive unclassified information (including Sensitive Unclassified Non-Safeguards Information (SUNSI) and Safeguards Information (SGI)). </P>
                <P>2. Within 10 days after publication of this notice of hearing and opportunity to petition for leave to intervene, any potential party as defined in 10 CFR 2.4 who believes access to SUNSI or SGI is necessary for a response to the Notice of Hearing may request access to SUNSI or SGI. A “potential party” is any person who intends or may intend to participate as a party by demonstrating standing and the filing of an admissible contention under 10 CFR 2.309. Requests submitted later than 10 days after publication of the Notice of Hearing will not be considered absent a showing of good cause for the late filing, addressing why the request could not have been filed earlier. </P>
                <P>
                    3. The requester shall submit a letter requesting permission to access SUNSI and/or SGI to the Office of the Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemakings and Adjudications Staff, and provide a copy to the Associate General Counsel for Hearings, Enforcement and Administration, Office of the General Counsel, Washington, DC 20555-0001. The expedited delivery or courier mail address for both offices is U.S. Nuclear Regulatory Commission, 11555 Rockville Pike, Rockville, Maryland 20852. The e-mail address for the Office of the Secretary and the Office of the General Counsel are 
                    <E T="03">HearingDocket@nrc.gov</E>
                     and 
                    <E T="03">OGCmail.gov</E>
                     respectively.
                    <SU>1</SU>
                    <FTREF/>
                     The request must include the following information: 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         While a request for hearing or petition to intervene in this proceeding must comply with the filing requirements of the NRC's “E-Filing Rule,” the initial request to access SUNSI and/or SGI under these procedures should be submitted as described in this paragraph. 
                    </P>
                </FTNT>
                <P>
                    a. A description of the licensing action with a citation to this 
                    <E T="04">Federal Register</E>
                     notice of hearing and opportunity to petition for leave to intervene; 
                </P>
                <P>b. The name and address of the potential party and a description of the potential party's particularized interest that could be harmed by the action identified in (a); </P>
                <P>c. If the request is for SUNSI, the identity of the individual requesting access to SUNSI and the requester's need for the information in order to meaningfully participate in this adjudicatory proceeding, particularly why publicly available versions of the application would not be sufficient to provide the basis and specificity for a proffered contention; </P>
                <P>d. If the request is for SGI, the identity of the individual requesting access to SGI and the identity of any expert, consultant or assistant who will aid the requester in evaluating the SGI, and information that shows: </P>
                <P>(i) Why the information is indispensable to meaningful participation in this licensing proceeding; and </P>
                <P>(ii) The technical competence (demonstrable knowledge, skill, experience, training or education) of the requester to understand and use (or evaluate) the requested information to provide the basis and specificity for a proffered contention. The technical competence of a potential party or its counsel may be shown by reliance on a qualified expert, consultant or assistant who demonstrates technical competence as well as trustworthiness and reliability, and who agrees to sign a nondisclosure affidavit and be bound by the terms of a protective order; and </P>
                <P>
                    e. If the request is for SGI, Form SF-85, “Questionnaire for Non-Sensitive Positions,” Form FD-258 (fingerprint card), and a credit check release form completed by the individual who seeks access to SGI and each individual who will aid the requester in evaluating the SGI. For security reasons, Form SF-85 can only be submitted electronically, through a restricted-access database. To obtain online access to the form, the requester should contact the NRC's Office of Administration at 301-415-0320.
                    <SU>2</SU>
                    <FTREF/>
                     The other completed forms must be signed in original ink, accompanied by a check or money order payable in the amount of $191.00 to the U.S. Nuclear Regulatory Commission for each individual, and mailed to the U.S. Nuclear Regulatory Commission, Office of Administration, Security Processing Unit, Mail Stop T-6E46, Washington, DC 20555-0012. 
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The requester will be asked to provide his or her full name, social security number, date and place of birth, telephone number, and email address. After providing this information, the requester usually should be able to obtain access to the online form within one business day. 
                    </P>
                </FTNT>
                <FP>These forms will be used to initiate the background check, which includes fingerprinting as part of a criminal history records check. </FP>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>Copies of these forms do not need to be included with the request letter to the Office of the Secretary, but the request letter should state that the forms and fees have been submitted as described above.</P>
                </NOTE>
                <P>4. To avoid delays in processing requests for access to SGI, all forms should be reviewed for completeness and accuracy (including legibility) before submitting them to the NRC. Incomplete packages will be returned to the sender and will not be processed. </P>
                <P>
                    5. Based on an evaluation of the information submitted under items 2 and 3.a through 3.d, above, the NRC staff will determine within 10 days of receipt of the written access request whether (1) there is a reasonable basis to believe the petitioner is likely to establish standing to participate in this NRC proceeding, and (2) there is a legitimate need for access to SUNSI or need to know the SGI requested. For SGI, the need to know determination is made based on whether the information requested is necessary (i.e., indispensable) for the proposed recipient to proffer and litigate a specific contention in this NRC proceeding 
                    <SU>3</SU>
                    <FTREF/>
                     and whether the proposed recipient has the technical competence (demonstrable knowledge, skill, training, education, or experience) to evaluate and use the specific SGI requested in this proceeding. 
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Broad SGI requests under these procedures are thus highly unlikely to meet the standard for need to know; furthermore, staff redaction of information from requested documents before their release may be appropriate to comport with this requirement. These procedures do not authorize unrestricted disclosure or less scrutiny of a requester's need to know than ordinarily would be applied in connection with an already admitted contention. 
                    </P>
                </FTNT>
                <P>6. If standing and need to know SGI are shown, the NRC staff will further determine based upon completion of the background check whether the proposed recipient is trustworthy and reliable. The NRC staff will conduct (as necessary) an inspection to confirm that the recipient's information protection systems are sufficient to protect SGI from inadvertent release or disclosure. Recipients may opt to view SGI at the NRC's facility rather than establish their own SGI protection program to meet SGI protection requirements. </P>
                <P>7. A request for access to SUNSI or SGI will be granted if: </P>
                <P>
                    a. The request has demonstrated that there is a reasonable basis to believe that 
                    <PRTPAGE P="55879"/>
                    a potential party is likely to establish standing to intervene or to otherwise participate as a party in this proceeding; 
                </P>
                <P> b. The proposed recipient of the information has demonstrated a need for SUNSI or a need to know for SGI, and that the proposed recipient of SGI is trustworthy and reliable; </P>
                <P>c. The proposed recipient of the information has executed a Non-Disclosure Agreement or Affidavit and agrees to be bound by the terms of a Protective Order setting forth terms and conditions to prevent the unauthorized or inadvertent disclosure of SUNSI and/or SGI; and </P>
                <P>
                    d. The presiding officer has issued a protective order concerning the information or documents requested.
                    <SU>4</SU>
                    <FTREF/>
                     Any protective order issued shall provide that the petitioner must file SUNSI or SGI contentions 25 days after receipt of (or access to) that information. However, if more than 25 days remain between the petitioner's receipt of (or access to) the information and the deadline for filing all other contentions (as established in the notice of hearing or opportunity for hearing), the petitioner may file its SUNSI or SGI contentions by that later deadline. 
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         If a presiding officer has not yet been designated, the Chief Administrative Judge will issue such orders, or will appoint a presiding officer to do so. 
                    </P>
                </FTNT>
                <P>
                    8. If the request for access to SUNSI or SGI is granted, the terms and conditions for access to sensitive unclassified information will be set forth in a draft protective order and affidavit of non-disclosure appended to a joint motion by the NRC staff, any other affected parties to this proceeding and the petitioner(s).
                    <SU>5</SU>
                    <FTREF/>
                     If the diligent efforts by the relevant parties or petitioner(s) fail to result in an agreement on the terms and conditions for a draft protective order or non-disclosure affidavit, the relevant parties to the proceeding or the petitioner(s) should notify the presiding officer within five (5) days, describing the obstacles to the agreement. 
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Parties/persons other than the requester and the NRC staff will be notified by the NRC staff of a favorable access determination (and may participate in the development of such a motion and protective order) if it concerns SUNSI and if the party/person's interest independent of the proceeding would be harmed by the release of the information (e.g., as with proprietary information). 
                    </P>
                </FTNT>
                <P>9. If the request for access to SUNSI is denied by the NRC staff or a request for access to SGI is denied by NRC staff either after a determination on standing and need to know or, later, after a determination on trustworthiness and reliability, the NRC staff shall briefly state the reasons for the denial. Before the Office of Administration makes an adverse determination regarding access, the proposed recipient must be provided an opportunity to correct or explain information. The requester may challenge the NRC staff's adverse determination with respect to access to SUNSI or with respect to standing or need to know for SGI by filing a challenge within five (5) days of receipt of that determination with (a) the presiding officer designated in this proceeding; (b) if no presiding officer has been appointed, the Chief Administrative Judge, or if he or she is unavailable, another administrative judge, or an administrative law judge with jurisdiction pursuant to 10 CFR 2.318(a); or (c) if another officer has been designated to rule on information access issues, with that officer. In the same manner, an SGI requester may challenge an adverse determination on trustworthiness and reliability by filing a challenge within 15 days of receipt of that determination. </P>
                <P>In the same manner, a party other than the requester may challenge an NRC staff determination granting access to SUNSI whose release would harm that party's interest independent of the proceeding. Such a challenge must be filed within five (5) days of the notification by the NRC staff of its grant of such a request. </P>
                <P>
                    If challenges to the NRC staff determinations are filed, these procedures give way to the normal process for litigating disputes concerning access to information. The availability of interlocutory review by the Commission of orders ruling on such NRC staff determinations (whether granting or denying access) is governed by 10 CFR 2.311.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         As of October 15, 2007, the NRC's final “E-Filing Rule” became effective. See Use of Electronic Submissions in Agency Hearings (72 FR 49139; August 28, 2007). Requesters should note that the filing requirements of that rule apply to appeals of NRC staff determinations (because they must be served on a presiding officer or the Commission, as applicable), but not to the initial SUNSI/SGI requests submitted to the NRC staff under these procedures. 
                    </P>
                </FTNT>
                <P>10. The Commission expects that the NRC staff and presiding officers (and any other reviewing officers) will consider and resolve requests for access to SUNSI and/or SGI, and motions for protective orders, in a timely fashion in order to minimize any unnecessary delays in identifying those petitioners who have standing and who have propounded contentions meeting the specificity and basis requirements in 10 CFR Part 2. Attachment 1 to this Order summarizes the general target schedule for processing and resolving requests under these procedures. </P>
                <SIG>
                    <DATED>Dated at Rockville, Maryland this 22nd day of September 2008. </DATED>
                    <P>For the Nuclear Regulatory Commission. </P>
                    <NAME>Annette L. Vietti-Cook, </NAME>
                    <TITLE>Secretary of the Commission.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Attachment 1—General Target Schedule for Processing and Resolving Requests for Access to Sensitive Unclassified Nonsafeguards Information and Safeguards Information in This Proceeding </HD>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="xs36,r200">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Day </CHED>
                        <CHED H="1">Event/activity</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">0 </ENT>
                        <ENT>
                            Publication of 
                            <E T="04">Federal Register</E>
                             notice of hearing and opportunity to petition for leave to intervene, including order with instructions for access requests. 
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10 </ENT>
                        <ENT>
                            Deadline for submitting requests for access to Sensitive Unclassified Non-Safeguards Information (SUNSI) and/or Safeguards Information (SGI) with information: Supporting the standing of a potential party identified by name and address; describing the need for the information in order for the potential party to participate meaningfully in an adjudicatory proceeding; demonstrating that access should be granted (
                            <E T="03">e.g.</E>
                            , showing technical competence for access to SGI); and, for SGI, including application fee for fingerprint/background check. 
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">60 </ENT>
                        <ENT>Deadline for submitting petition for intervention containing: (i) Demonstration of standing; (ii) all contentions whose formulation does not require access to SUNSI and/or SGI (+25 Answers to petition for intervention;  +7 petitioner/requestor reply). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20 </ENT>
                        <ENT>NRC staff informs the requester of the staff's determination whether the request for access provides a reasonable basis to believe standing can be established and shows (1) need for SUNSI or (2) need to know for SGI. (For SUNSI, NRC staff also informs any party to the proceeding whose interest independent of the proceeding would be harmed by the release of the information.) If NRC staff makes the finding of need for SUNSI and likelihood of standing, NRC staff begins document processing (preparation of redactions or review of redacted documents). If NRC staff makes the finding of need to know for SGI and likelihood of standing, NRC staff begins background check (including fingerprinting for a criminal history records check), information processing (preparation of redactions or review of redacted documents), and readiness inspections. </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="55880"/>
                        <ENT I="01">25 </ENT>
                        <ENT>If NRC staff finds no “need,” “need to know,” or likelihood of standing, the deadline for petitioner/requester to file a motion seeking a ruling to reverse the NRC staff's denial of access; NRC staff files copy of access determination with the presiding officer (or Chief Administrative Judge or other designated officer, as appropriate). If NRC staff finds “need” for SUNSI, the deadline for any party to the proceeding whose interest independent of the proceeding would be harmed by the release of the information to file a motion seeking a ruling to reverse the NRC staff's grant of access. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">30 </ENT>
                        <ENT>Deadline for NRC staff reply to motions to reverse NRC staff determination(s). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">40 </ENT>
                        <ENT>(Receipt +30) If NRC staff finds standing and need for SUNSI, deadline for NRC staff to complete information processing and file motion for Protective Order and draft Non-Disclosure Affidavit. Deadline for applicant/licensee to file Non-Disclosure Agreement for SUNSI. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">190 </ENT>
                        <ENT>(Receipt +180) If NRC staff finds standing, need to know for SGI, and trustworthiness and reliability, deadline for NRC staff to file motion for Protective Order and draft Non-disclosure Affidavit (or to make a determination that the proposed recipient of SGI is not trustworthy or reliable). Note: Before the Office of Administration makes an adverse determination regarding access, the proposed recipient must be provided an opportunity to correct or explain information. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">205 </ENT>
                        <ENT>Deadline for petitioner to seek reversal of a final adverse NRC staff determination either before the presiding officer or another designated officer. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A </ENT>
                        <ENT>If access granted: Issuance of presiding officer or other designated officer decision on motion for protective order for access to sensitive information (including schedule for providing access and submission of contentions) or decision reversing a final adverse determination by the NRC staff. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A + 3 </ENT>
                        <ENT>Deadline for filing executed Non-Disclosure Affidavits. Access provided to SUNSI and/or SGI consistent with decision issuing the protective order. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A + 28 </ENT>
                        <ENT>Deadline for submission of contentions whose development depends upon access to SUNSI and/or SGI. However, if more than 25 days remain between the petitioner's receipt of (or access to) the information and the deadline for filing all other contentions (as established in the notice of hearing or opportunity for hearing), the petitioner may file its SUNSI or SGI contentions by that later deadline. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A + 53 </ENT>
                        <ENT>(Contention receipt +25) Answers to contentions whose development depends upon access to SUNSI and/or SGI. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A + 60 </ENT>
                        <ENT>(Answer receipt +7) Petitioner/Intervener reply to answers. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">B </ENT>
                        <ENT>Decision on contention admission. </ENT>
                    </ROW>
                </GPOTABLE>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22671 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7590-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[NRC-2008-0419]</DEPDOC>
                <SUBJECT>Security and Continued Use of Cesium-137 Chloride Sources: Granting Extension of Comment Period </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Nuclear Regulatory Commission (NRC). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Granting of Request to Extend the Comment Period on the Issues described in the Notice on the Security and Continued Use of Cesium-137 Chloride Sources. </P>
                </ACT>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dr. John P. Jankovich, Office of Federal and State Materials and Environmental Management Programs, telephone (301) 415-7904, e-mail 
                        <E T="03">john.jankovich@nrc.gov,</E>
                         or Dr. Cynthia Jones, Office of Nuclear Security and Incident Response, telephone (301) 415-0298, e-mail 
                        <E T="03">cynthia.jones@nrc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Introduction </HD>
                <P>
                    On July 31, 2008, the NRC issued a notice in the 
                    <E T="04">Federal Register</E>
                     which requested, in part, public comments on the issues presented in the notice on the security and continued use of cesium-137 chloride sources (73 FR 44780). The notice requested early public input on major issues associated with the use of certain forms of cesium-137 chloride currently used by NRC- and Agreement State-licensees. While the NRC has not initiated rulemaking on this subject, NRC used the conventionally established rulemaking comment channels for obtaining comments. 
                </P>
                <HD SOURCE="HD1">II. Further Information </HD>
                <P>The NRC staff requested receipt of comments on the notice by September 30, 2008. By this action, the NRC staff is extending the comment period until October 15, 2008. Comments received after October 15, 2008, will be considered if practical to do so, but the NRC is unable to ensure consideration only for comments received on or before this date. Although a time limit is given, comments and suggestions in connection with the use of cesium-137 chloride sources are encouraged at any time. </P>
                <P>In addition to inviting public comments on the issues presented in section III of the July 31, 2008 notice, the NRC also solicited specific comments related to: (1) Quantitative information on the costs and benefits resulting from consideration of the factors described in the Issues Paper; (2) operational data on radiation exposures (increased or reduced) that might result from implementing any of the options described in the Issues Paper; (3) whether the presented issues are addressed comprehensively; and (4) whether other options should be considered, including quantitative information on the costs and benefits for these other options. The Commission believes that stakeholder comments help to quantify the potential impact of these proposed changes and will assist the NRC as potential regulatory action(s) are developed. </P>
                <HD SOURCE="HD1">III. Request To Extend the Comment Period </HD>
                <HD SOURCE="HD2">Basis for the Request </HD>
                <P>The NRC received the following extension request:</P>
                <EXTRACT>
                    <P>
                        On behalf of industry, the Nuclear Energy Institute (NEI) respectfully requests an extension of the comment period identified in the subject 
                        <E T="04">Federal Register</E>
                         notice (FRN) entitled, “Request for Comments on the Security and Continued Use of Cesium-137 Chloride Sources and Notice of Public Meeting” dated July 31, 2008. Specifically, the FRN states that stakeholder comments on the Cesium-137 Chloride source issues raised therein should be submitted to NRC no later than September 30, 2008. This date coincides with the last day of the scheduled public meeting, which industry fully supports. We believe that industry, the public and other stakeholder comments on these complex matters would be greatly informed by the deliberations that will inevitably occur during the two day meeting which commences on September 29, 2008. Therefore, we request that the comment period be extended, at a minimum, 30 days so as to close no earlier than October 30, 2008.
                    </P>
                </EXTRACT>
                <P>
                    The NRC received similar requests from the Conference of Radiation Control Program Directors, Inc., (CRCPD), and from the International 
                    <PRTPAGE P="55881"/>
                    Source Suppliers and Producers Association (ISSPA), both dated September 19, 2008, for extension of the comment period from September 30 to October 30, 2008. 
                </P>
                <HD SOURCE="HD2">Response to Request </HD>
                <P>The request for an extension to the comment period is approved for 15 days. </P>
                <P>The staff understands that NEI, CRCPD and ISSPA requested an extension of 30 days. However, NRC can not grant the full extension because the comments are needed by mid-October for development of future NRC actions for Commission consideration by November 2008. Therefore, the staff is approving a 15-day extension to the original public comment period, with the public comment period to end on October 15, 2008. The staff recognizes that the public and other stakeholder comments may be impacted by the discussions that will occur during the two-day public meeting which concludes on September 30, 2008, and therefore agrees to extend the comment period an additional 15 days. </P>
                <P>
                    Members of the public are invited and encouraged to submit comments electronically to 
                    <E T="03">http://www.regulations.gov.</E>
                     Search on Docket ID: [NRC-2008-0419] and follow the instructions for submitting comments. Comments may also be sent by mail to Michael Lesar, Chief, Rulemaking, Directives and Editing Branch, Office of Administration, Mail Stop T-6D59, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001. 
                </P>
                <P>
                    Requests for technical information may be directed to the NRC contacts, Dr. John P. Jankovich, Office of Federal and State Materials and Environmental Management Programs, telephone (301) 415-7904, e-mail 
                    <E T="03">john.jankovich@nrc.gov,</E>
                     or Dr. Cynthia Jones, Office of Nuclear Security and Incident Response, telephone (301) 415-0298, e-mail 
                    <E T="03">cynthia.jones@nrc.gov</E>
                    . 
                </P>
                <P>You can also access publicly available documents related to the July 31, 2008 notice using the following methods: </P>
                <P>
                    <E T="03">Regulations.gov:</E>
                     Documents related to this notice, including public comments, are accessible at 
                    <E T="03">http://www.regulations.gov,</E>
                     by searching on docket ID: NRC-2008-0419. Electronic copies of the July 31, 2008 notice and the workshop agenda are also available through NRC's public Web site at 
                    <E T="03">http://www.nrc.gov/materials/miau/licensing.html.</E>
                </P>
                <P>
                    <E T="03">NRC's Public Document Room (PDR):</E>
                     The public may examine and have copied for a fee, publicly available documents at the NRC's PDR, Public File Area O-1F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland. 
                </P>
                <P>
                    <E T="03">NRC's Agency wide Document Access and Management System (ADAMS):</E>
                     Publicly available documents created or received at the NRC after November 1, 1999, are available electronically at the NRC's Electronic Reading Room at 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>
                     From this site, the public can gain entry into ADAMS, which provides text and image files of NRC's public documents. If you do not have access to ADAMS or if there are problems in accessing the documents located in ADAMS, contact the PDR Reference staff at 1-800-397-4209, 301-415-4737 or by e-mail to 
                    <E T="03">pdr.resource@nrc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated at Rockville, Maryland, this 22nd day of September 2008. </DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>John P. Jankovich, </NAME>
                    <TITLE>Team Leader, Office of Federal and State Materials and Environmental Management Program. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22688 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">RAILROAD RETIREMENT BOARD </AGENCY>
                <SUBJECT>Agency Forms Submitted for OMB Review, Request for Comments </SUBJECT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35), the Railroad Retirement Board (RRB) is forwarding an Information Collection Request (ICR) to the Office of Information and Regulatory Affairs (OIRA), Office of Management and Budget (OMB) to request an extension without change of a currently approved collection of information: 3220-0038, Medical Reports. Our ICR describes the information we seek to collect from the public. Review and approval by OIRA ensures that we impose appropriate paperwork burdens. </P>
                    <P>The RRB invites comments on the proposed collection of information to determine (1) The practical utility of the collection; (2) the accuracy of the estimated burden of the collection; (3) ways to enhance the quality, utility and clarity of the information that is the subject of collection; and (4) ways to minimize the burden of collections on respondents, including the use of automated collection techniques or other forms of information technology. Comments to RRB or OIRA must contain the OMB control number of the ICR. For proper consideration of your comments, it is best if RRB and OIRA receive them within 30 days of publication date. </P>
                    <P>Under Sections 2(a)(1)(iv), 2(a)(2) and 2(a)(3) of the Railroad Retirement Act (RRA), annuities are payable to qualified railroad employees whose physical or mental condition is such that they are unable to (1) work in their regular occupation (occupational disability); or (2) work at all (permanent total disability). The requirements for establishment of disability and proof of continuance of disability are prescribed in 20 CFR 220. </P>
                    <P>Under Sections 2(c)(1)(ii)(c) and 2(d)(1)(ii) of the RRA, annuities are also payable to qualified spouses and widow(ers), respectively, who have a qualified child who is under a disability which began before age 22. Annuities are also payable to surviving children on the basis of disability under Section 2(d)(1)(iii)(C) if the child's disability began before age 22 and to widow(ers) on the basis of disability under section 2(d)(1) (i)(B). To meet the disability standard, the RRA provides that individuals must have a permanent physical or mental condition such that they are unable to engage in any regular employment. </P>
                    <P>
                        Under section 2(d)(1)(v) of the RRA, annuities are also payable to remarried and surviving divorced spouses on the basis of, 
                        <E T="03">inter alia,</E>
                         disability or having a qualified disabled child in care. However, the disability standard in these cases is that found in the Social Security Act. That is, individuals must be able to engage in any substantial gainful activity by reason of any medically determinable physical or mental impairment. The RRB also determines entitlement to a period of early disability and early Medicare entitlement for qualified claimants in accordance with Section 216 of the Social Security Act. 
                    </P>
                    <P>When making disability determinations, the RRB needs evidence from acceptable medical sources. The RRB currently utilizes Forms G-3EMP, Report of Medical Condition by Employer; G-197, Authorization to Release Medical Information, G-250, Medical Assessment; G-250a, Medical Assessment of Residual Functional Capacity; G-260, Report of Seizure Disorder; RL-11b, Disclosure of Hospital Medical Records; RL-11d, Disclosure of Medical Records from a State Agency; and RL-250, Request for Medical Assessment, to obtain the necessary medical evidence. The RRB proposes no changes to the information collection. Completion of the forms is voluntary. One response is requested of each respondent. </P>
                    <P>
                        <E T="03">Previous Requests for Comments:</E>
                         The RRB has already published the initial 60-day notice (73 FR 22183 on April 24, 
                        <PRTPAGE P="55882"/>
                        2008) required by 44 U.S.C. 3506(c)(2). That request elicited no comments. 
                    </P>
                    <HD SOURCE="HD1">Information Collection Request (ICR) </HD>
                    <P>
                        <E T="03">Title:</E>
                         Medical Reports. 
                    </P>
                    <P>
                        <E T="03">OMB Control Number:</E>
                         OMB 3220-0038. 
                    </P>
                    <P>
                        <E T="03">Form(s) submitted:</E>
                         G-3EMP, G-197, G-250, G-250a, G-260, RL-11B, RL-11D, RL-250. 
                    </P>
                    <P>
                        <E T="03">Type of request:</E>
                         Extension without change of a currently approved collection of information. 
                    </P>
                    <P>
                        <E T="03">Affected public:</E>
                         Individuals or households; Private Sector; State, Local and Tribal Government. 
                    </P>
                    <P>
                        <E T="03">Abstract:</E>
                         The Railroad Retirement Act provides disability annuities for qualified railroad employees whose physical or mental condition renders them incapable of working in their regular occupation (occupational disability) or any occupation (total disability). The medical reports obtain information needed for determining the nature and severity of the impairment. 
                    </P>
                    <P>
                        <E T="03">Changes proposed:</E>
                         The RRB proposes no changes to the forms in the collection. 
                    </P>
                    <P>
                        <E T="03">The burden estimate for the ICR is as follows:</E>
                    </P>
                </SUM>
                <GPOTABLE COLS="04" OPTS="L2,tp0,i1" CDEF="s50,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Form No.</CHED>
                        <CHED H="1">
                            Annual
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">Time (min.)</CHED>
                        <CHED H="1">Burden (hours)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">G-3EMP </ENT>
                        <ENT>600 </ENT>
                        <ENT>10 </ENT>
                        <ENT>100</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">G-197 </ENT>
                        <ENT>6,000 </ENT>
                        <ENT>10 </ENT>
                        <ENT>1,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">G-250 </ENT>
                        <ENT>11,950 </ENT>
                        <ENT>30 </ENT>
                        <ENT>5,975</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">G-250a </ENT>
                        <ENT>50 </ENT>
                        <ENT>20 </ENT>
                        <ENT>17</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">G-260 </ENT>
                        <ENT>100 </ENT>
                        <ENT>25 </ENT>
                        <ENT>42</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RL-11b </ENT>
                        <ENT>5,000 </ENT>
                        <ENT>10 </ENT>
                        <ENT>833</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RL-11d </ENT>
                        <ENT>250 </ENT>
                        <ENT>10 </ENT>
                        <ENT>42</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">RL-250 </ENT>
                        <ENT>11,950 </ENT>
                        <ENT>10 </ENT>
                        <ENT>1,992</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>35,900 </ENT>
                        <ENT>  </ENT>
                        <ENT>10,001</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Additional information or comments:</E>
                     Copies of the form and supporting documents can be obtained from Charles Mierzwa, the agency clearance officer at (312-751-3363) or 
                    <E T="03">Charles.Mierzwa@rrb.gov</E>
                    . 
                </P>
                <P>
                    Comments regarding the information collection should be addressed to Ronald J. Hodapp, Railroad Retirement Board, 844 North Rush Street, Chicago, Illinois 60611-2092 or 
                    <E T="03">Ronald.Hodapp@rrb.gov</E>
                     and to the OMB Desk Officer for the RRB, at the Office of Management and Budget, Room 10230, New Executive Office Building, Washington, DC 20503. 
                </P>
                <SIG>
                    <NAME>Charles Mierzwa, </NAME>
                    <TITLE>Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22672 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7905-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION </AGENCY>
                <DEPDOC>[Release No. 34-58603; File No. SR-CBOE-2008-97] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Chicago Board Options Exchange, Incorporated; Notice of Filing of a Proposed Rule To Establish a CBSX-Only Order Type </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>
                    Pursuant to section 19(b)(1) of the Securities Exchange Act of 1934 (the “Exchange Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on September 16, 2008, the Chicago Board Options Exchange, Incorporated (the “Exchange” or “CBOE”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the Exchange. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4. 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>
                    The Exchange proposes to change CBOE Stock Exchange (“CBSX”) Rule 51.8, to adopt a CBSX-Only order. The text of the proposed rule change is available on the Exchange's Web site (
                    <E T="03">http://www.cboe.com</E>
                    ), at the Office of the Secretary, CBOE and at the Commission's Public Reference Room. 
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose </HD>
                <P>
                    The purpose of this proposed rule change is to revise CBOE Stock Exchange (“CBSX”) Rule 51.8 to adopt a CBSX-Only order type. A CBSX-only order is an order to buy or sell that is to be executed in whole or in part on CBSX, and the portion not so executed is to be cancelled, without routing the order to another market center or market participant, and without being “flashed” at the NBBO price to CBSX Traders pursuant to Rule 52.6 when CBSX is not at the NBBO and the order is marketable against the NBBO. Thus, a CBSX-Only order would either immediately execute on CBSX, get booked on CBSX (provided it does not cause a locked or crossed market), or cancel. Many exchanges have similar order-types (
                    <E T="03">e.g.</E>
                     NSX Rule 11.11(c)(6)). 
                </P>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    The Exchange believes the proposed rule change is consistent with section 6(b) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     in general and furthers the objectives of section 6(b)(5) of the Act 
                    <SU>4</SU>
                    <FTREF/>
                     in particular in that, by offering users greater control over order routing, it is designed to promote just and equitable principles of trade, serve to remove impediments to and perfect the mechanism of a free and open market and a national market system. 
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         15 U.S.C. 78f(b). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78f(b)(5). 
                    </P>
                </FTNT>
                <PRTPAGE P="55883"/>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>CBOE does not believe that the proposed rule change will impose any burden on competition not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others </HD>
                <P>No written comments were solicited or received with respect to the proposed rule change. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    The proposed rule change is filed for immediate effectiveness pursuant to section 19(b)(3)(A) of the Act 
                    <SU>5</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder 
                    <SU>6</SU>
                    <FTREF/>
                     because it effects a change that (i) does not significantly affect the protection of investors or the public interest; (ii) does not impose any significant burden on competition; and (iii) by its terms, does not become operative for 30 days after the date of the filing, or such shorter time as the Commission may designate if consistent with the protection of investors and the public interest.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 U.S.C. 78s(b)(3)(A). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         17 CFR 240.19b-4(f)(6). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         In addition, Rule 19b-4(f)(6) under the Act requires the self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Commission has determined to waive the five-day prefiling period in this case. 
                    </P>
                </FTNT>
                <P>
                    CBOE has requested the Commission to waive the 30-day operative delay because the proposal may assist investors by allowing greater control over order routing. The Commission hereby grants the Exchange's request and believes such waiver is consistent with the protection of investors and the public interest. The CBSX-only order is similar to orders currently available on other markets and does not appear to raise any novel or significant issues.
                    <SU>8</SU>
                    <FTREF/>
                     Accordingly, the Commission designates the proposed rule change operative upon filing with the Commission. 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         For purposes only of waiving the 30-day operative delay of this proposal, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments </HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-CBOE-2008-97 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments </HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549-1090. </P>
                <P>
                    All submissions should refer to File Number SR-CBOE-2008-97. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for inspection and copying in the Commission's Public Reference Room on official business days between the hours of 10 a.m. and 3 p.m. Copies of such filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-CBOE-2008-97 and should be submitted on or before October 17, 2008. 
                </P>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             17 CFR 200.30-3(a)(12). 
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Acting Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22656 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8010-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION </AGENCY>
                <DEPDOC>[Release No. 34-58599; File No. SR-NYSE-2008-56] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; New York Stock Exchange LLC; Order Approving Proposed Rule Change To Amend Section 902.09 of the Listed Company Manual To Establish Fees for Securities Listed Under Sections 703.21 and 703.22 of the Listed Company Manual and Traded on NYSE Bonds and To Waive Fees for Structured Products Transferred From the Amex to the NYSE </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <HD SOURCE="HD1">I. Introduction </HD>
                <P>
                    On July 24, 2008, the New York Stock Exchange LLC (“NYSE” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change establish fees for securities listed under Sections 703.21 and 703.22 of the Listed Company Manual and traded on NYSE Bonds 
                    <SU>3</SU>
                    <FTREF/>
                     and to waive fees for certain structured products transferred from the American Stock Exchange LLC (“Amex”) to the NYSE. The proposed rule change was published in the 
                    <E T="04">Federal Register</E>
                     on August 11, 2008.
                    <SU>4</SU>
                    <FTREF/>
                     The Commission received no comments on the proposal. This order approves the proposed rule change. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 USC. 78s(b)(1). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         NYSE Bonds is the Exchange trading system designated for the purposes of receiving, processing, executing, and reporting orders in bonds. 
                        <E T="03">See</E>
                         NYSE Rule 86. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 58301 (August 4, 2008), 73 FR 46672. 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Description of the Proposal </HD>
                <P>
                    The Exchange proposes to amend Section 902.09 of the Manual to extend the initial and continued listing fees charged thereunder to certain listed securities traded on the equity floor to securities listed under Section 703.21 (Equity-Linked Debt Securities) and Section 703.22 (Index-Linked Securities) and traded on NYSE Bonds.
                    <SU>5</SU>
                    <FTREF/>
                     The Exchange does not currently set forth in the Manual any listing fees for securities that are listed under either Section 703.21 of the Manual (Equity-Linked Debt Securities) or Section 
                    <PRTPAGE P="55884"/>
                    703.22 of the Manual (Index-Linked Securities) and traded on NYSE Bonds. The Exchange has determined that the most appropriate fee schedule for these securities is that set forth in Section 902.09 of the Manual.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Section 902.09 of the Manual currently sets forth initial and continued listing fees to securities listed under Section 703.15 of the Manual (Foreign Currency Warrants and Currency Index Warrants) and Section 703.22 of the Manual (Index-Linked Securities) and traded on the equity floor of the Exchange. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Section 902.09 of the Manual, which sets forth the listing fees and annual fees being proposed to be extended to Index-Linked Securities and Equity-Linked Debt Securities traded on NYSE Bonds. Generally, the section provided a graduated scale of initial listing fees depending on how many shares are outstanding, ranging from a minimum fee of $5,000 for shares outstanding up to 1 million, to a maximum fee of $45,000 for shares outstanding in excess of 15 million. Section 902.09 also provided a graduated scale of annual fees depending on the total number of securities outstanding per listed issue, ranging from a minimum fee of $10,000 for shares outstanding up to 6 million, to a maximum fee of $55,000 for shares outstanding in excess of 50 million. 
                    </P>
                </FTNT>
                <P>
                    In addition, the Exchange proposes to waive, in connection with transfers to the NYSE from NYSE Alternext US  after the closing of the purchase of the Amex by NYSE Euronext (the “Merger”),
                    <SU>7</SU>
                    <FTREF/>
                     (i) all fees payable under Section 902.08 of the Manual in connection with such transfers,
                    <SU>8</SU>
                    <FTREF/>
                     and (ii) in the case of securities that will be traded on NYSE Bonds, all fees payable under Section 902.09 of the Manual in connection with such transfer, including the prorated annual fee payable for the calendar year in which the transfer occurs. The fee waivers described in the previous sentence will only apply (i) if such transfer occurs during the calendar year in which the Merger is consummated and (ii) if the Merger is consummated no later than March 31, 2009. 
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         NYSE Euronext, the ultimate parent company of the Exchange, has agreed to acquire the Amex pursuant to an Agreement and Plan of Merger, dated as of January 17, 2008. The members of the Amex voted to approve the transaction on June 17, 2008. No vote of the NYSE Euronext shareholders is required. When filing its proposed rule change, the NYSE stated that it is currently anticipated that the acquisition will be consummated during the third quarter of 2008. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Section 902.08 of the Manual sets forth listing fees for securities that list under the debt standard in Section 703.19 of the Manual and trade on NYSE Bonds. There is no listing fee for the debt of NYSE equity issuers and affiliated companies, or for the debt of issuers exempt from registration under the Act. There is an initial listing fee of $15,000 for all other debt securities. 
                    </P>
                </FTNT>
                <P>
                    In its filing, NYSE stated that in connection with the acquisition, NYSE Euronext intends to discontinue the listing on NYSE Alternext US of bonds and structured products issued in $1,000 face amounts. To the extent that these securities qualify for listing under the applicable NYSE standards, the Exchange will encourage the issuers to apply to list those securities on the NYSE for trading on NYSE Bonds. As the issuers of these securities will already have paid listing fees to NYSE Alternext US and will be transferring to the NYSE as a result of a business decision made by NYSE Euronext, the Exchange proposes to waive all listing fees that would be payable in connection with the listing of securities transferred from NYSE Alternext US and traded on NYSE Bonds, including securities listed under Sections 703.19, 703.21 and 703.22, provided the transfer to NYSE Bonds occurs during the calendar year in which the Merger is consummated.
                    <SU>9</SU>
                    <FTREF/>
                     This waiver will only take effect upon consummation of NYSE Euronext's acquisition of the Amex. 
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         NYSE states that as annual fees for listed securities are calculated based on the number of securities outstanding on January 1 and billed on an annual basis, the proposed fee waiver will not apply to additional securities of a class that has been transferred from NYSE Alternext US that are issued after the date of transfer. 
                    </P>
                </FTNT>
                <P>The Exchange also stated in its filing that the proposed fee waiver does not render the allocation of its listing fees inequitable or unfairly discriminatory, in particular because, after the Merger, NYSE Regulation, Inc. (“NYSE Regulation”) will perform listed company regulation for both the Exchange and NYSE Alternext US, including a substantial review of companies upon original listing. The Exchange further notes that many of the regulatory staff who currently perform initial and continued listing reviews at the Amex will become employees of NYSE Regulation at the time of the Merger and will continue to perform the same duties with respect to Amex companies after the Merger. According to the Exchange, securities transferring from NYSE Alternext US will be subjected to the same rigorous regulatory review as any other applicant for listing on the Exchange. However, the Exchange expects that, on average, the review of securities transferring from NYSE Alternext US to the Exchange will be less costly than the review of a transfer from an unaffiliated market, as the Amex listing regulatory staff that will have been absorbed by NYSE Regulation will already have performed a substantial review of any Amex-listed company, and NYSE Regulation will be able to rely on that prior work as a baseline in qualifying the company for listing on the Exchange and in conducting ongoing compliance activities with respect to any such company. Furthermore, the Exchange anticipates that the revenue it foregoes as a consequence of this waiver will be an immaterial amount that would not have any impact on its ability to finance its regulatory activities. </P>
                <HD SOURCE="HD1">III. Discussion </HD>
                <P>
                    The Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange and, in particular, the requirements of Section 6(b) of the Act and the rules and regulations thereunder. Specifically, the Commission finds that the proposal is consistent with Sections 6(b)(4) 
                    <SU>10</SU>
                    <FTREF/>
                     and 6(b)(5) of the Act,
                    <SU>11</SU>
                    <FTREF/>
                     which require that an exchange have rules that provide for the equitable allocation of reasonable dues, fees, and other charges among its members and other persons using its facilities, and are designed, among other things, to promote just and equitable principles of trade, to remove impediments to and perfect the mechanism of a free and open market and a national market system, to protect investors and the public interest, and to not permit unfair discrimination between customers, issuers, brokers, or dealers.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 USC. 78f(b)(4). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         15 USC. 78f(b)(5). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         In approving this proposed rule change, the Commission notes that it has considered the proposed rules' impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 USC. 78c(f). 
                    </P>
                </FTNT>
                <P>
                    The Commission believes that the fees set forth for securities listed under either Section 703.21 of the Manual (Equity-Linked Debt Securities) or Section 703.22 of the Manual (Index-Linked Securities) and traded on NYSE Bonds are consistent with the Act, and Section 6(b)(4) of the Act 
                    <SU>13</SU>
                    <FTREF/>
                     in particular. The Exchange has not previously listed any securities under Sections 703.21 or 703.22 of the Manual that traded on NYSE Bonds and consequently does not currently set forth in the Manual any listing fees for such securities. The Commission notes that the Exchange has determined that the most appropriate fee schedule for these securities is that set forth in Section 902.09 of the Manual. As noted above, these fees currently set forth initial and continued listing fees for Foreign Currency Warrants, Currency Index Warrants, and Index-Linked Securities traded on the equity floor of the Exchange, and the extension of these fees to Equity-Linked Debt Securities and Index-Linked Securities traded on NYSE Bonds appears to be reasonable.
                    <SU>14</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         15 USC. 78f(b)(4). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         The Commission notes that for certain structured products, including Equity-Linked Debt Securities traded on the equity floor that the fees in Section 902.05 of the Manual or Section 902.06 of the Manual apply. Index-Linked Securities, irrespective of whether traded on the equity floor or on NYSE Bonds, would follow the fee schedule in Section 902.09 of the Manual. 
                    </P>
                </FTNT>
                <PRTPAGE P="55885"/>
                <P>The Commission further believes that the waiver of certain listing fees in connection with transfers to the NYSE from NYSE Alternext US after the closing of the Merger is consistent with the Act. The Commission notes that an issuer seeking to transfer to the Exchange has already paid initial listing fees to another national securities exchange when it became a publicly traded company. The Commission also notes that the Exchange does not expect the loss of initial listing fees to be material and has stated that the fee waiver will not affect the Exchange's ability to finance its regulatory activities. In addition, after the calendar year of the transfer of the issuer's security, the Exchange would assess annual fees and listing of additional shares fees from these issuers. Further, the Exchange believes that there will be lower burdens and costs associated with its review of issuers transferring from another national securities exchange and in conducting ongoing compliance activities with respect to such companies. The Commission notes that NYSE has stated that review of transfers from NYSE Alternext US will be less costly than for an unaffiliated entity, as the same regulatory staff on Amex (that will have been absorbed by NYSE Regulation) will have conducted a substantial review of an Amex company that NYSE Regulation will be able to rely upon as a baseline in qualifying the company for listing on the Exchange and in conducting ongoing compliance activities with respect to any such company. Therefore, the Commission believes it is not inequitable or unfair to provide for a waiver of initial and annual fees for a limited period of time after the merger is consummated. Notwithstanding this, the Commission expects that a full and independent review of compliance with the listing standards will be conducted for any company seeking to take advantage of the fee waiver, just as for any company that applies for listing on the Exchange. Further, the Commission expects the Exchange to maintain its commitment to resources to its regulatory oversight of the listing process and its ongoing compliance review of listed companies under its regulatory program. </P>
                <P>
                    Based on the above, the Commission believes the proposed listing fees and listing fee waivers do not constitute an inequitable allocation of reasonable dues, fees, and other charges under Section 6(b)(4) of the Act,
                    <SU>15</SU>
                    <FTREF/>
                     do not permit unfair discrimination between issuers under Section 6(b)(5) of the Act,
                    <SU>16</SU>
                    <FTREF/>
                     and are otherwise consistent with the requirements of the Act. 
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b)(4). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78f(b)(5). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion </HD>
                <P>
                    <E T="03">It is therefore ordered</E>
                    , pursuant to Section 19(b)(2) of the Act,
                    <SU>17</SU>
                    <FTREF/>
                     that the proposed rule change (SR-NYSE-2008-56) is hereby approved. 
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         15 U.S.C. 78s(b)(2). 
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>18</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             17 CFR 200.30-3(a)(12). 
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22587 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8010-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION </AGENCY>
                <DEPDOC>[Release No. 34-58601; File No. SR-NYSE-2008-74] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; New York Stock Exchange LLC; Order Approving Proposed Rule Change To Enable the Exchange To Waive Annual Listing Fees for Securities Transferring From the Amex or NYSE Arca, Inc. </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <HD SOURCE="HD1">I. Introduction </HD>
                <P>
                    On August 4, 2008, the New York Stock Exchange LLC (“NYSE” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to waive annual listing fees for securities transferring to NYSE from the American Stock Exchange LLC (“Amex”) or NYSE Arca, Inc. (“NYSE Arca”). The proposed rule change was published in the 
                    <E T="04">Federal Register</E>
                     on August 15, 2008.
                    <SU>3</SU>
                    <FTREF/>
                     The Commission received no comments on the proposal. This order approves the proposed rule change. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 58311 (August 5, 2008), 73 FR 47994. 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Description of the Proposal </HD>
                <P>
                    The Exchange proposes to amend Section 902.02 of the Manual to provide that, with retroactive effect from January 1, 2008, for issuers that transfer their primary class of common stock from Amex to the Exchange, there shall be no annual fee for the remainder of the calendar year in which the transfer occurs for the transferred common stock and any other class of securities of a company listed on the Amex. This proposed rule change (i) is conditioned on the consummation of NYSE Euronext's acquisition of the Amex (the “Merger”),
                    <SU>4</SU>
                    <FTREF/>
                     (ii) will not take effect until the date of consummation of the Merger, and (iii) will be of no further effect if the closing of the Merger does not take place by March 31, 2009. The amendment also provides that companies transferring the listing of their primary class of common stock from NYSE Arca to the Exchange (with respect to which the Exchange already waives annual fees for the first part year, pursuant to Section 902.02 of the Manual) will not be charged the prorated annual fee in the first year of listing for any other class of securities that is transferred in connection with the transfer of the common stock. 
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         NYSE Euronext, the ultimate parent company of the Exchange, has agreed to acquire the Amex pursuant to an Agreement and Plan of Merger, dated as of January 17, 2008. The members of the Amex voted to approve the transaction on June 17, 2008. No vote of the NYSE Euronext shareholders is required. After the closing of the Merger, the Amex will be renamed NYSE Alternext US LLC. 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. Securities Transferring From Amex </HD>
                <P>The Exchange proposes to amend Section 902.02 of the Manual to grant companies transferring the listing of their primary class of common shares and any other class of securities to the Exchange from the Amex a waiver of the prorated annual listing fee that would normally be payable in connection with the first partial calendar year of listing on the Exchange. As noted in its proposal, the Exchange believes this is appropriate because companies transferring to the Exchange from the Amex will already have paid annual continued listing fees to the Amex for the calendar year in which they transfer. The Exchange further stated that since some companies may choose to transfer from the Amex to the Exchange in advance of the consummation of the acquisition, and such companies will be making their transfer decisions in expectation of the Merger, the Exchange believes that they should not be penalized for transferring before the closing date. Consequently, the Exchange believes that it is appropriate to apply the fee waiver retroactively to all companies that transfer to the Exchange from the Amex during the portion of the year in which the Merger is consummated prior to such consummation. </P>
                <P>
                    In its proposal, the Exchange stated that this fee waiver is not unfairly discriminatory and does not constitute an inequitable allocation of fees, in particular because, after the Merger, NYSE Regulation, Inc. (“NYSE 
                    <PRTPAGE P="55886"/>
                    Regulation”) will perform listed company regulation for both the Exchange and Amex, including a substantial review of companies upon original listing. Many of the regulatory staff who currently perform initial and continued listing reviews at the Amex will become employees of NYSE Regulation at the time of the Merger and will continue to perform the same duties with respect to Amex companies after the Merger. Companies transferring from Amex will be subjected to the same rigorous regulatory review as any other applicant for listing on the Exchange. However, the Exchange expects that, on average, the review of companies transferring from Amex to the Exchange will be less costly than the review of a transfer from an unaffiliated market, because the Amex listing regulatory staff that will have been absorbed by NYSE Regulation will already have performed a substantial review of any Amex listed company and NYSE Regulation will be able to rely on that prior work as a baseline in qualifying the company for listing on the Exchange and in conducting ongoing compliance activities with respect to those companies. 
                </P>
                <P>The Exchange also believes that waiving, subject to consummation of the Merger, the prorated annual fees applicable to any Amex security transferred to the NYSE prior to the Merger is not unfairly discriminatory or an inequitable allocation of fees. In its proposal, the Exchange stated that the proposed fee waiver will not impact its ability to devote the same level of resources to its oversight of the companies that benefit from the waiver as it does for other listed companies or, more generally, impact its resource commitment to its regulatory oversight of the listing process or its regulatory programs. The Exchange notes that, after consummation of the Merger, the annual fee revenue paid by companies to the Amex prior to the Merger will be available to NYSE Regulation to finance its regulatory activities in relation to Amex-listed companies, regardless of whether such companies remain on NYSE Alternext US or have chosen to transfer their listing to the NYSE at some point during the year either before or after the Merger. The Exchange asserted that therefore collecting annual fees from companies upon transfer from the Amex to the NYSE would constitute a double billing of those companies for the regulatory expenses incurred by NYSE Regulation in relation to those companies during the year of transfer. </P>
                <HD SOURCE="HD2">B. Securities Transferring From NYSE Arca </HD>
                <P>Section 902.02 of the Manual currently provides that any company transferring the listing of its primary class of common equity securities from NYSE Arca to the Exchange will not be charged any annual fees in connection with the first partial year of listing on the Exchange. The Exchange proposes to extend the NYSE Arca annual fee waiver to the prorated annual fees that would otherwise be payable with respect to any other class of securities that an issuer is transferring to the Exchange from NYSE Arca in conjunction with its transfer of its common stock, for the remainder of the calendar year in which the transfer occurs. The Exchange believes this waiver is appropriate in light of the fact that the Exchange and NYSE Arca share a common parent and, without the waiver, NYSE Euronext would be collecting two separate annual fees in relation to such securities. In addition, the same staff from NYSE Regulation are responsible for compliance review of all securities listed on both markets and their prior experience with any securities transferring from NYSE Arca will significantly lessen the burden and costs associated with continued compliance review of those securities once they have been transferred to the NYSE. Specifically, the Exchange believes that the proposed fee waiver will not impact its ability to devote the same level of resources to its oversight of the companies that benefit from the waiver as it does for other listed companies or, more generally, impact its resource commitment to its regulatory oversight of the listing process or its regulatory programs. </P>
                <HD SOURCE="HD1">III. Discussion </HD>
                <P>
                    The Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange and, in particular, the requirements of Section 6(b) of the Act and the rules and regulations thereunder. Specifically, the Commission finds that the proposal is consistent with Sections 6(b)(4) 
                    <SU>5</SU>
                    <FTREF/>
                     and 6(b)(5) of the Act,
                    <SU>6</SU>
                    <FTREF/>
                     which require that an exchange have rules that provide for the equitable allocation of reasonable dues, fees, and other charges among its members and other persons using its facilities, and are designed, among other things, to promote just and equitable principles of trade, to remove impediments to and perfect the mechanism of a free and open market and a national market system, to protect investors and the public interest, and to not permit unfair discrimination between customers, issuers, brokers, or dealers.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 USC. 78f(b)(4). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 USC. 78f(b)(5). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         In approving this proposed rule change, the Commission notes that it has considered the proposed rules' impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f). 
                    </P>
                </FTNT>
                <P>National securities exchanges traditionally assess annual listing fees on listed companies at the beginning of the calendar year. When a company transfers to another marketplace, such annual fees are typically pro-rated by the new market for the remainder of the calendar year. Annual fees aid a listed market in, among other things, conducting its regulatory responsibilities to ensure compliance by listed companies with continued listing standards and other regulatory requirements. The Commission has carefully examined the fee waiver in light of NYSE's ongoing regulatory responsibilities as to the transferred companies and, for the reasons set forth below, has determined that the proposed limited annual fee waiver is consistent with the Act. </P>
                <P>The Commission notes that an Amex or NYSE Arca issuer seeking to transfer to the Exchange has already paid annual continued listing fees to another national securities exchange for the calendar year in which it transferred. Further, the Commission recognizes that subsequent to the consummation of the Merger, both Amex as NYSE Alternext US, NYSE Arca, and NYSE will be under the same common ownership. The Commission also notes that the Exchange anticipates the review of securities transferring from Amex to be less costly than the review of a transfer from an unaffiliated market, because Amex listing regulatory staff that will be part of NYSE Regulation will continue to perform both initial and continued listing reviews. In addition, the Commission notes that the same staff from NYSE Regulation are responsible for compliance review of all securities listed on both NYSE and NYSE Arca, and the Exchange asserted that this will significantly lessen the burden and costs associated with continued compliance review of NYSE Arca transfers. </P>
                <P>
                    The Commission further believes that the application of the waiver to companies transferring to the NYSE from Amex prior to the Merger, occurring only upon consummation of the Merger, is not unfairly discriminatory and does not constitute 
                    <PRTPAGE P="55887"/>
                    an inequitable allocation of fees. The Commission notes that the Exchange has represented that after consummation of the Merger, the annual fee revenue paid by companies to the Amex prior to the Merger will be available to NYSE Regulation to finance its regulatory activities in relation to Amex-listed companies, regardless of whether such companies remain on NYSE Alternext US or have chosen to transfer their listing to the NYSE at some point during the year either before or after the Merger. Since the retroactive effect is conditioned on consummation of the Merger, the fee waiver recognizes that these regulatory efficiencies will only occur upon that event. 
                </P>
                <P>The Commission also notes that the fee waiver is for a limited time, applicable to the remainder of the calendar year in which the transfer occurs. Annual fees for both Amex and NYSE Arca transfers will continue to be assessed after the initial pro-rated annual fee waiver. The limited period of the fee waiver helps to ensure that that NYSE will have adequate fees to continue compliance and oversight of its listing program. </P>
                <P>In summary, based on the reasons set forth above, including NYSE's assertions that (i) the same regulatory staff on both Amex (that will have been absorbed by NYSE Regulation) and NYSE Regulation will have conducted a substantial review of an Amex or NYSE Arca company that NYSE Regulation will be able to rely upon as a baseline in qualifying the company for both listing on the Exchange and in conducting ongoing compliance activities with respect to any such company; and (ii) the retroactive effect for Amex transfers will only occur if the Merger is consummated, the Commission believes it is not inequitable or unfair to provide for a waiver of annual fees for a limited period of time. The Commission expects, and the Exchange has represented, that a rigorous and independent review of compliance with the listing standards will be conducted for any company seeking to take advantage of the fee waiver, just as for any company that lists on the Exchange. In addition, the Commission expects the Exchange to maintain its commitment of resources to its regulatory oversight of the listing process and its ongoing compliance review of listed companies under its regulatory program. </P>
                <P>
                    Based on the above, the Commission believes the proposed fee waiver does not constitute an inequitable allocation of reasonable dues, fees, and other charges under Section 6(b)(4) of the Act,
                    <SU>8</SU>
                    <FTREF/>
                     does not permit unfair discrimination between issuers under Section 6(b)(5) of the Act,
                    <SU>9</SU>
                    <FTREF/>
                     and is otherwise consistent with the requirements of the Act. 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78f(b)(4). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78f(b)(5). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion </HD>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to Section 19(b)(2) of the Act,
                    <SU>10</SU>
                    <FTREF/>
                     that the proposed rule change (SR-NYSE-2008-74) is hereby approved. 
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22658 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8010-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION </AGENCY>
                <DEPDOC>[Release No. 34-58596; File No. SR-NYSEArca-2008-98] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Notice of Filing and Immediate Effectiveness of Proposed Rule Change by NYSE Arca, Inc., Amending NYSE Arca Equities Rule 7.35 Governing Auctions </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>
                    Pursuant to section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (the “Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that, on September 15, 2008, NYSE Arca, Inc. (“NYSE Arca” or the “Exchange”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the Exchange. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>The Exchange proposes to amend NYSE Arca Equities Rule 7.35(c) and (e) to permit the Exchange to conduct a Market Order Auction and a Closing Auction in all exchange listed “Derivative Securities Products” as defined by NYSE Arca Equities Rule 7.34(a)(4)(A). </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose </HD>
                <P>The Exchange proposes to amend NYSE Arca Equities Rule 7.35(c) and (e) to permit the Exchange to conduct a Market Order Auction and a Closing Auction in all exchange listed “Derivative Securities Products” as defined by NYSE Arca Equities Rule 7.34(a)(4)(A). </P>
                <P>Currently NYSE Arca Equities Rule 7.35(c) states that the Exchange will conduct a Market Order Auction in (i) exchange-listed securities for which the Corporation is the primary market; (ii) all exchange-listed exchange traded funds; and (iii) NYSE listed securities subject to a sub-penny trading condition. Similarly, NYSE Arca Equities Rule 7.35(e) states that the Exchange will conduct a Closing Auction in (i) exchange-listed securities for which the Corporation is the primary market; (ii) all exchange-listed exchange traded funds; and (iii) NYSE listed securities subject to a sub-penny trading condition. The Exchange proposes to expand subpart (ii) in both Rules by replacing the term “exchange-listed exchange traded funds” with the term “exchange-listed Derivative Securities Products” as that term is defined in NYSE Arca Equities Rule 7.34(a)(4)(A). </P>
                <P>The Exchange believes this rule change will foster increased liquidity by expanding the type of securities eligible for Market Order and Closing auctions. This proposed amendment is also consistent with Rules 4752 and 4754 of the Nasdaq Stock Market, L.L.C. (“Nasdaq”), which do not limit the securities or products that may be traded in the opening and closing auctions. </P>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    The proposed rule change is consistent with section 6(b) of the Act 
                    <PRTPAGE P="55888"/>
                    in general, and furthers the objectives of section 6(b)(5) in particular in that it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in facilitating transactions in securities, and to remove impediments to and perfect the mechanism of a free and open market and a national market system. This proposed rule change will foster increased liquidity by expanding the type of securities eligible for Market Order and Closing auctions. 
                </P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others </HD>
                <P>No written comments were solicited or received with respect to the proposed rule change. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    The proposed rule change has become effective pursuant to section 19(b)(3)(A) of the Act 
                    <SU>4</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder 
                    <SU>5</SU>
                    <FTREF/>
                     because the foregoing proposed rule: (1) Does not significantly affect the protection of investors or the public interest; (2) does not impose any significant burden on competition; and (3) does not become operative for 30 days after the date of filing, or such shorter time as the Commission may designate if consistent with the protection of investors and the public interest.
                    <SU>6</SU>
                    <FTREF/>
                     The Exchange notes that this filing does not propose any new policies or provisions that are unique or unproven, and is consistent with Nasdaq Rules 4752 and 4754. 
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         In addition, Rule 19b-4(f)(6)(iii) requires the self-regulatory organization to give the Commission notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. NYSE Arca has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    The Exchange has asked the Commission to waive the 30-day operative delay and designate the proposed rule change as operative upon filing. The Commission hereby grants the Exchange's request.
                    <SU>7</SU>
                    <FTREF/>
                     The Commission believes that such action is consistent with the protection of investors and the public interest because the Exchange's proposal is similar to that of another exchange that was previously approved by the Commission.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         For purposes only of waiving the operative delay for this proposal, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 54155 (July 14, 2006), 71 FR 41291 (July 20, 2006) (SR-NASDAQ-2006-001) (approving, among other things, Nasdaq Rules 4752 and 4754.)
                    </P>
                </FTNT>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission may summarily abrogate such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov</E>
                    . Please include File Number SR-NYSEArca-2008-98 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, Station Place, 100 F Street, NE., Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-NYSEArca-2008-98. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for inspection and copying in the Commission's Public Reference Room, 100 F Street, NE., Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. Copies of such filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make publicly available. All submissions should refer to File Number SR-NYSEArca-2008-98 and should be submitted on or before October 17, 2008. 
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22654 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8010-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION </AGENCY>
                <DEPDOC>[Release No. 34-58598; File No. SR-NYSEArca-2008-78] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Arca, Inc.; Order Approving Proposed Rule Change To Waive Annual Fees for Securities Transferring to NYSE Arca From NYSE Alternext US </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <HD SOURCE="HD1">I. Introduction </HD>
                <P>
                    On July 23, 2008, NYSE Arca, Inc. (“NYSE Arca” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to waive annual listing fees for securities transferring to NYSE Arca from NYSE Alternext US after the closing of the purchase of the American Stock Exchange LLC (“Amex”) by NYSE Euronext (the “Merger”).
                    <SU>3</SU>
                    <FTREF/>
                     The proposed rule change was published in the 
                    <E T="04">Federal Register</E>
                     on August 11, 2008.
                    <SU>4</SU>
                    <FTREF/>
                      
                    <PRTPAGE P="55889"/>
                    The Commission received no comments on the proposal. This order approves the proposed rule change. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         NYSE Euronext, the ultimate parent company of the Exchange, has agreed to acquire the Amex pursuant to an Agreement and Plan of Merger, dated as of January 17, 2008. After the closing of the Merger, the Amex will be renamed NYSE Alternext US LLC. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 58297 (August 4, 2008), 73 FR  46683. 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Description of the Proposal </HD>
                <P>The Exchange proposes that securities transferring to NYSE Arca from NYSE Alternext US after the closing of the Merger will not be charged any prorated annual fee for the remainder of the year in which the Merger takes place. The fee waiver in the preceding sentence will be of no further effect if the closing of the Merger does not take place by March 31, 2009. </P>
                <P>The Exchange believes this proposed fee waiver does not render the allocation of its listing fees inequitable or unfairly discriminatory, in particular because, after the Merger, NYSE Regulation, Inc. (“NYSE Regulation”) will perform listed company regulation for both the Exchange and NYSE Alternext US, including a substantial review of companies upon original listing. The Exchange notes that many of the regulatory staff who currently perform initial and continued listing reviews at the Amex will become employees of NYSE Regulation at the time of the Merger and will continue to perform the same duties with respect to NYSE Alternext US securities after the Merger. The Exchange represents that securities transferring from NYSE Alternext US will be subjected to the same rigorous regulatory review as any other securities with respect to which an application for listing is made to the Exchange. However, the Exchange expects that, on average, the review of securities transferring from NYSE Alternext US to the Exchange will be less costly than the review of a transfer from an unaffiliated market, as the Amex listing regulatory staff that will have been absorbed by NYSE Regulation will already have performed a substantial review of any NYSE Alternext US-listed issuer, and NYSE Regulation will be able to rely on that prior work as a baseline in qualifying the issuer for listing on the Exchange and in conducting ongoing compliance activities with respect to any such issuer. In support of its proposal, the Exchange also notes that transferring issuers would have already paid annual continued listing fees to the Amex for the calendar year in which the transfer took place. </P>
                <HD SOURCE="HD1">III. Discussion </HD>
                <P>
                    The Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange and, in particular, the requirements of section 6(b) of the Act and the rules and regulations thereunder. Specifically, the Commission finds that the proposal is consistent with sections 6(b)(4) 
                    <SU>5</SU>
                    <FTREF/>
                     and 6(b)(5) of the Act,
                    <SU>6</SU>
                    <FTREF/>
                     which require that an exchange have rules that provide for the equitable allocation of reasonable dues, fees, and other charges among its members and other persons using its facilities, and are designed, among other things, to promote just and equitable principles of trade, to remove impediments to and perfect the mechanism of a free and open market and a national market system, to protect investors and the public interest, and to not permit unfair discrimination between customers, issuers, brokers, or dealers.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 U.S.C. 78f(b)(4). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78f(b)(5). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         In approving this proposed rule change, the Commission notes that it has considered the proposed rules' impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f). 
                    </P>
                </FTNT>
                <P>National securities exchanges traditionally assess annual listing fees on listed companies at the beginning of the calendar year. When a company transfers to another marketplace, such annual fees are typically pro-rated by the new market for the remainder of the calendar year. Annual fees aid a listed market in, among other things, conducting its regulatory responsibilities to ensure compliance by listed companies with continued listing standards and other regulatory requirements. The Commission notes that an Amex issuer seeking to transfer to the Exchange has already paid annual continued listing fees to another national securities exchange for the calendar year in which it transferred. Further, the Commission recognizes that subsequent to the consummation of the Merger, both Amex as NYSE Alternext US and NYSE Arca will be under the same common ownership. The Commission also notes that the Exchange anticipates the review of securities transferring from NYSE Alternext US to be less costly than the review of a transfer from an unaffiliated market, because Amex listing regulatory staff that will be part of NYSE Regulation will continue to perform both initial and continued listing reviews. However, the Commission expects, and the Exchange has represented, that a rigorous and independent review of compliance with the listing standards will be conducted for any company seeking to take advantage of the fee waiver, just as for any company that lists on the Exchange. The Commission expects the Exchange to maintain its commitment of resources to its regulatory oversight of the listing process and its ongoing compliance review of listed companies under its regulatory program. </P>
                <P>In summary, for the reasons set forth above, including NYSE Arca's assertion that the same regulatory staff on Amex (that will have been absorbed by NYSE Regulation) will have conducted a substantial review of an Amex company that NYSE Regulation will be able to rely upon as a baseline in qualifying the company for listing on the Exchange and in conducting ongoing compliance activities with respect to any such company, the Commission believes it is not inequitable or unfair to provide for a waiver of annual fees for a limited period of time after the merger is consummated. </P>
                <P>
                    Based on the above, the Commission believes the proposed fee waiver does not constitute an inequitable allocation of reasonable dues, fees, and other charges under section 6(b)(4) of the Act,
                    <SU>8</SU>
                    <FTREF/>
                     does not permit unfair discrimination between issuers under section 6(b)(5) of the Act,
                    <SU>9</SU>
                    <FTREF/>
                     and is otherwise consistent with the requirements of the Act. 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78f(b)(4). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78f(b)(5). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion </HD>
                <P>
                    It is therefore ordered, pursuant to section 19(b)(2) of the Act,
                    <SU>10</SU>
                    <FTREF/>
                     that the proposed rule change (SR-NYSEArca-2008-78) is hereby approved. 
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78s(b)(2). 
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             17 CFR 200.30-3(a)(12). 
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22655 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8010-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="55890"/>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION </AGENCY>
                <DEPDOC>[Release No. 34-58604; File No. SR-ODD-2008-04] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; the Options Clearing Corporation; Order Granting Approval of Accelerated Delivery of Supplement to the Options Disclosure Document Reflecting Changes to Disclosure Regarding Certain Variability Index Options, Strategy-Based Index Options, and Adjustments of Stock Option Contracts </SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>
                    On August 21, 2008, the Options Clearing Corporation (“OCC”) submitted to the Securities and Exchange Commission (“Commission”), pursuant to Rule 9b-1 under the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     five preliminary copies of a supplement to its options disclosure document (“ODD”) reflecting changes to disclosure regarding certain options on variability indexes 
                    <SU>2</SU>
                    <FTREF/>
                     and strategy-based indexes and adjustments of stock option contracts, among other changes.
                    <SU>3</SU>
                    <FTREF/>
                     On September 19, 2008, the OCC submitted to the Commission five definitive copies of the supplement.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         17 CFR 240.9b-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         In the proposed September 2008 supplement to the ODD and this Order, the term “variability indexes” refers to implied volatility, realized variance, and realized volatility indexes. 
                        <E T="03">See infra</E>
                         notes 5 and 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         letter from Jean M. Cawley, Senior Vice President and Deputy General Counsel, OCC, to Sharon Lawson, Senior Special Counsel, Division of Trading and Markets (“Division”), Commission, dated August 13, 2008.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         letter from Jean M. Cawley, Senior Vice President and Deputy General Counsel, OCC, to Sharon Lawson, Senior Special Counsel, Division, Commission, dated September 19, 2008.
                    </P>
                </FTNT>
                <P>
                    The ODD currently contains general disclosures on the characteristics and risks of trading standardized options. Recently, the Chicago Board Options Exchange, Incorporated (“CBOE”) amended its rules to permit the listing and trading of realized variance and realized volatility index options.
                    <SU>5</SU>
                    <FTREF/>
                     The CBOE also recently amended its rules to permit the listing and trading of certain strategy-based index options, specifically options that overlie an index that is equal to 
                    <FR>1/10</FR>
                    th of the value of the CBOE S&amp;P 500 BuyWrite Index (“BXM options”).
                    <SU>6</SU>
                    <FTREF/>
                     The proposed supplement amends the ODD to accommodate these changes by providing disclosure regarding realized variance index options, realized volatility index options, and strategy-based index options.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 58171 (July 16, 2008), 73 FR 42841 (July 23, 2008) (SR-CBOE-2008-31).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 58207 (July 22, 2008), 73 FR 43963 (July 29, 2008) (SR-CBOE-2008-26).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The proposed September supplement is divided into two parts. Part I supersedes and replaces the March 2005 supplement to the ODD to accommodate the approval of trading of certain realized variance index options, realized volatility index options, and BXM options. 
                        <E T="03">See</E>
                         notes 4 and 5, 
                        <E T="03">supra</E>
                        . The March 2005 supplement contained disclosure on implied volatility options previously approved for trading by the Commission, and the September 2008 supplement includes disclosure on these products. 
                        <E T="03">See</E>
                         note 2 
                        <E T="03">supra</E>
                         and Securities Exchange Act Release No. 49563 (April 14, 2004) 69 FR 21589 (April 21, 2004) (order approving SR-CBOE-2003-40 to list and trade implied volatility options on the CBOE Volatility Index (VIX); the CBOE Nasdaq 100 Volatility Index (VXN); and CBOE Dow Jones Industrial Average Volatility Index, (VXD)). 
                        <E T="03">See also</E>
                         Securities Exchange Act Release No. 55425 (March 8, 2007), 72 FR 12238 (March 15, 2007) (order approving SR-CBOE-2006-73 to list and trade implied volatility options on the CBOE Russell 2000 Volatility Index (RVX)).
                    </P>
                </FTNT>
                <P>
                    Specifically, the proposed supplement to the ODD adds new disclosure regarding the characteristics of realized variance and realized volatility index options as well as the special risks of these options. The proposed supplement to the ODD also adds new disclosure regarding the characteristics and special risks of strategy-based index options. The proposed supplement is intended to be read in conjunction with the more general ODD, which, as described above, discusses the characteristics and risks of options generally.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The Commission notes that the options markets must continue to ensure that the ODD is in compliance with the requirements of Rule 9b-1(b)(2)(i) under the Act, 17 CFR 240.9b-1(b)(2)(i), including when future changes regarding variability index options and/or strategy-based index options are made. Any future changes to the rules of the options markets concerning variability index options and/or strategy-based index options would need to be submitted to the Commission under Section 19(b) of the Act. 15 U.S.C. 78s(b).
                    </P>
                </FTNT>
                <P>
                    The proposed supplement also is revised to: (1) Accommodate a change in the application of the new methodology for adjusting equity options for cash dividends; 
                    <SU>9</SU>
                    <FTREF/>
                     (2) add new language to describe reduced-value index options; 
                    <SU>10</SU>
                    <FTREF/>
                     and (3) delete a paragraph regarding the NASDAQ Stock Market LLC's (“Nasdaq”) opening and closing procedure, which has become outdated and inaccurate.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         This proposed change amends the May 2007 supplement to the ODD. 
                        <E T="03">See</E>
                         OCC-2008-16.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         This proposed new language amends the June 2008 supplement to the ODD.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The language being deleted relates to the opening and closing price for securities trading on Nasdaq, but is no longer accurate because Nasdaq has since changed its opening and closing procedures.
                    </P>
                </FTNT>
                <P>
                    Rule 9b-1(b)(2)(i) under the Act 
                    <SU>12</SU>
                    <FTREF/>
                     provides that an options market must file five copies of an amendment or supplement to the ODD with the Commission at least 30 days prior to the date definitive copies are furnished to customers, unless the Commission determines otherwise, having due regard to the adequacy of information disclosed and the public interest and protection of investors.
                    <SU>13</SU>
                    <FTREF/>
                     In addition, five copies of the definitive ODD, as amended or supplemented, must be filed with the Commission not later than the date the amendment or supplement, or the amended options disclosure document, is furnished to customers. The Commission has reviewed the proposed supplement and finds, having due regard to the adequacy of information disclosed and the public interest and protection of investors, that the proposed supplement may be furnished to customers as of the date of this order. 
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         17 CFR 240.9b-1(b)(2)(i).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         This provision permits the Commission to shorten or lengthen the period of time which must elapse before definitive copies may be furnished to customers.
                    </P>
                </FTNT>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to Rule 9b-1 under the Act,
                    <SU>14</SU>
                    <FTREF/>
                     that definitive copies of the proposed supplement to the ODD (SR-ODD-2008-03), reflecting changes to disclosure regarding certain options on variability indexes and strategy-based indexes, as well as the other changes noted above, may be furnished to customers as of the date of this order. 
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         17 CFR 240.9b-1.
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             17 CFR 200.30-3(a)(39).
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22638 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8010-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SOCIAL SECURITY ADMINISTRATION </AGENCY>
                <DEPDOC>[Docket No. SSA-2008-0044] </DEPDOC>
                <SUBJECT>Agreement on Social Security Between the United States and Denmark; Entry Into Force </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Social Security Administration (SSA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Commissioner of Social Security gives notice that an agreement coordinating the United States (U.S.) and Danish social security programs will enter into force on October 1, 2008. The agreement with Denmark, which was signed on June 13, 2007, is similar to U.S. social security agreements already in force with 21 other countries—Australia, Austria, Belgium, 
                        <PRTPAGE P="55891"/>
                        Canada, Chile, Finland, France, Germany, Greece, Ireland, Italy, Japan, Korea (South), Luxembourg, the Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and the United Kingdom. Agreements of this type are authorized by section 233 of the Social Security Act (42 U.S.C. 433). 
                    </P>
                    <P>Like the other agreements, the U.S.-Danish agreement eliminates dual social security coverage—the situation that exists when a worker from one country works in the other country and is covered under the social security systems of both countries for the same work. Without such agreements in force, when dual coverage occurs, the worker, the worker's employer, or both may be required to pay social security contributions to the two countries simultaneously. Under the U.S.-Danish agreement, a worker who is sent by an employer in the U.S. to work in Denmark for 5 years or less remains covered only by the U.S. social security program. Similarly, a worker who is sent by an employer in Denmark to work in the U.S. for 3 years or less remains covered only by the Danish social security program. The agreement includes additional rules that eliminate dual U.S. and Danish coverage in other work situations. </P>
                    <P>The agreement also helps eliminate situations where workers suffer a loss of benefit rights because they have divided their careers between the two countries. Under the agreement, workers may qualify for partial U.S. benefits or partial Danish benefits based on combined (totalized) work credits from both countries. </P>
                    <P>
                        Individuals who wish to obtain copies of the agreement or want more information about its provisions may write to the Social Security Administration, Office of International Programs, Post Office Box 17741, Baltimore, MD 21235-7741 or visit the Social Security Web site at 
                        <E T="03">http://www.socialsecurity.gov/international</E>
                        . 
                    </P>
                </SUM>
                <SIG>
                    <DATED>Dated: September 19, 2008. </DATED>
                    <NAME>Michael J. Astrue, </NAME>
                    <TITLE>Commissioner of Social Security.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22667 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4191-02-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice 6377] </DEPDOC>
                <SUBJECT>Culturally Significant Objects Imported for Exhibition Determinations: “The Getty Commodus: Roman Portraits and Modern Copies” </SUBJECT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is hereby given of the following determinations: Pursuant to the authority vested in me by the Act of October 19, 1965 (79 Stat. 985; 22 U.S.C. 2459), Executive Order 12047 of March 27, 1978, the Foreign Affairs Reform and Restructuring Act of 1998 (112 Stat. 2681, 
                        <E T="03">et seq.</E>
                        ; 22 U.S.C. 6501 note, 
                        <E T="03">et seq.</E>
                        ), Delegation of Authority No. 234 of October 1, 1999, Delegation of Authority No. 236 of October 19, 1999, as amended, and Delegation of Authority No. 257 of April 15, 2003 [68 FR 19875], I hereby determine that the objects in the exhibition: “The Getty Commodus: Roman Portraits and Modern Copies,” imported from abroad for temporary exhibition within the United States, are of cultural significance. The objects are imported pursuant to loan agreements with the foreign owners or custodians. I also determine that the exhibition or display of the exhibit objects at the Getty Villa, Malibu, CA, from on or about December 18, 2008, until on or about June 1, 2009, and at possible additional exhibitions or venues yet to be determined, is in the national interest. Public Notice of these Determinations is ordered to be published in the 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For further information, including a list of the exhibit objects, contact Julie Simpson, Attorney-Adviser, Office of the Legal Adviser, U.S. Department of State (telephone: (202-453-8050)). The address is U.S. Department of State, SA-44, 301 4th Street, SW., Room 700, Washington, DC 20547-0001. </P>
                    <SIG>
                        <DATED>Dated: September 18, 2008. </DATED>
                        <NAME>C. Miller Crouch, </NAME>
                        <TITLE>Principal Deputy Assistant Secretary for Educational and Cultural Affairs, Department of State.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22713 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-05-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice 6376] </DEPDOC>
                <SUBJECT>Culturally Significant Objects Imported for Exhibition Determinations: “Worshiping Women: Ritual and Reality in Classical Athens” </SUBJECT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is hereby given of the following determinations: Pursuant to the authority vested in me by the Act of October 19, 1965 (79 Stat. 985; 22 U.S.C. 2459), Executive Order 12047 of March 27, 1978, the Foreign Affairs Reform and Restructuring Act of 1998 (112 Stat. 2681, 
                        <E T="03">et seq.</E>
                        ; 22 U.S.C. 6501 note, 
                        <E T="03">et seq.</E>
                        ), Delegation of Authority No. 234 of October 1, 1999, Delegation of Authority No. 236 of October 19, 1999, as amended, and Delegation of Authority No. 257 of April 15, 2003 [68 FR 19875], I hereby determine that the objects to be included in the exhibition “Worshiping Women: Ritual and Reality in Classical Athens,” imported from abroad for temporary exhibition within the United States, are of cultural significance. The objects are imported pursuant to loan agreements with the foreign owners or custodians. I also determine that the exhibition or display of the exhibit objects at the Onassis Cultural Center, New York, NY, from on or about December 10, 2008, until on or about May 9, 2009, and at possible additional exhibitions or venues yet to be determined, is in the national interest. Public Notice of these Determinations is ordered to be published in the 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For further information, including a list of the exhibit objects, contact Carol B. Epstein, Attorney-Adviser, Office of the Legal Adviser, U.S. Department of State (telephone: 202-453-8048). The address is U.S. Department of State, SA-44, 301 4th Street, SW., Room 700, Washington, DC 20547-0001. </P>
                    <SIG>
                        <DATED>Dated: September 15, 2008. </DATED>
                        <NAME>C. Miller Crouch, </NAME>
                        <TITLE>Principal Deputy Assistant Secretary for Educational and Cultural Affairs, Department of State.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. E8-22712 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-05-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice 6371] </DEPDOC>
                <SUBJECT>Cancellation of a Meeting of the International Telecommunication Advisory Committee </SUBJECT>
                <P>
                    <E T="03">Summary:</E>
                     This notice cancels an announced meeting of the International Telecommunication Advisory Committee (ITAC). 
                </P>
                <P>The ITAC Meeting scheduled for October 8 from 10 a.m. to 12 p.m. is hereby cancelled. It is rescheduled for November 6 from 2 to 4 p.m. at 1120 20th Street, NW., 10th Floor, Washington, DC 20036. The ITAC meeting will solicit advice for the U.S. Government on the annual ITU Council Meeting, which will be held from November 12-21, 2008 at ITU headquarters in Geneva, Switzerland. The ITAC meeting will also discuss the results of the ITU World Telecommunication Standardization Assembly, which will be held October 21-30, 2008 in Johannesburg, South Africa. </P>
                <P>
                    This meeting is open to the public as seating capacity allows. The public will have an opportunity to provide 
                    <PRTPAGE P="55892"/>
                    comments at this meeting. People desiring further information on these meetings may contact the Secretariat at 
                    <E T="03">jillsonad@state.gov</E>
                     or 202 647-5872. 
                </P>
                <SIG>
                    <DATED>Dated: September 22, 2008. </DATED>
                    <NAME>Richard C. Beaird, </NAME>
                    <TITLE>International Communications &amp; Information Policy, Department of State.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22703 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-07-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <DEPDOC>[Docket No. DOT-OST-2008-0182] </DEPDOC>
                <SUBJECT>Office of Small and Disadvantaged Business Utilization (OSDBU); Regional Small Business Transportation Resource Centers (SBTRCs); Notice of Request for Comments on Renewal of Information Collection: Regional Center Intake Form (DOT F 4500) and Regional Resource Center Monthly Report Form (DOT F 4502) (Formerly, Counseling Information Form; Regional Center Intake Form and Monthly Report of Operations Form) </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, Department of Transportation (DOT). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of Small and Disadvantaged Business Utilization (OSDBU) invites the public to comment about our intention to request the Office of Management and Budget's (OMB) approval to renew information collection forms, associated with OSDBU. </P>
                    <P>
                        We are required to publish this notice in the 
                        <E T="04">Federal Register</E>
                         by the Paperwork Reduction Act of 1995. On June 26, 2008, OSDBU published a 60-day notice in the 
                        <E T="04">Federal Register</E>
                         (73 FR 36368), Docket #OST-2008-0182, informing the public of OSDBU's intention to extend this previously approved information collection. 
                    </P>
                    <P>The collection involves the use of the Regional Center Intake Form (DOT F 4500), which documents the type of assistance provided to each small business that is enrolled in the program. </P>
                    <P>The use of the Regional Resource Center Monthly Report Form (DOT F 4502) will highlight activities, such as counseling, marketing, meetings/conferences, and services to businesses as completed during the month. The information will be used to ascertain whether the program is providing services to its constituency, the small business community, in a fair and equitable manner. The information collected is necessary to determine whether small businesses are participating in DOT funded and DOT assisted opportunities with the DOT. </P>
                    <P>The Counseling Information Form (DOT F 4640.1) has been eliminated and the information contained in that form is now consolidated into the Regional Resource Center Monthly Report Form (formerly titled Monthly Report of Operations Form) in effort to eliminate duplication and to streamline the data collection process. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by: October 27, 2008. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments to the attention of the DOT/OST Desk Officer, Office of Information and Regulatory Affairs, Office of Management and Budget, Docket library, Room 10102, 725 17th Street, NW., Washington, DC 20503, or 
                        <E T="03">www.oira_submission@omb.eop.gov</E>
                         (e-mail). 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Arthur D. Jackson, 202-366-5344, Office of Small and Disadvantaged Business Utilization, Office of the Secretary, U.S. Department of Transportation, 1200 New Jersey Avenue, SE., Room W56-462, Washington, DC 20590. Office hours are from 9 a.m. to 5 p.m., Monday through Friday, except Federal holidays. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Regional Center Intake Form (DOT F 4500) and Regional Resource Center Monthly Report Form (DOT F 4502) (Formerly, Counseling Information Form; Regional Center Intake Form and Monthly Report of Operations Form). 
                </P>
                <P>
                    <E T="03">OMB Control No:</E>
                     2105-0554. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Representatives of DOT Regional Small Business Transportation Resource Centers and the Small Businesses community on a national basis. 
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Renewal of information collection. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     In accordance with Public Law 95-507, an amendment to the Small Business Act and the Small Business Investment Act of 1953, OSDBU is responsible for the implementation and execution of the Department of Transportation (DOT) activities on behalf of small businesses, in accordance with Section 8, 15 and 31 of the Small Business Act (SBA), as amended. The Office of Small and Disadvantaged Business Utilization also administers the provisions of Title 49, of the United States Code, Section 332, the Minority Resource Center (MRC), which includes the duties of advocacy, outreach and financial services on behalf of small and disadvantaged businesses and those certified under CFR 49 Parts 23 and or 26 as Disadvantaged Business Enterprises (DBE). 
                </P>
                <P>The Small Business Transportation Resource Regional Centers (SBTRCs) will collect information on small businesses, which includes Disadvantaged Business Enterprise (DBE), Women-Owned Small Businesses (WOB), Small Disadvantaged Businesses (SDB), 8(a), Service Disabled Veteran Owned Businesses (SDVOB), Veteran Owned Small Businesses (VOSB), HubZone, and types of services they seek from the SBTRCs. Services and responsibilities of the SBTRCs include business analysis, general management and technical assistance and training, business counseling, outreach services/conference participation, and short-term loan assistance. The cumulative data collected will be analyzed by the OSDBU to determine the effectiveness of services provided, including counseling, outreach, and financial services. Such data will also be analyzed by the OSDBU to determine agency effectiveness in assisting small businesses to enhance their opportunities to participate in government contracts and subcontracts. </P>
                <P>
                    <E T="03">The Regional Center Intake Form (DOT F 4500)</E>
                     is used by the Regional SBTRC staff to enroll small business clients into the program in order to create a viable database of firms that can participate in government contracts and subcontracts, especially those projects that are transportation related. In addition, each enrolled small business will be assigned a client number that can track the firm's involvement in the services offered by the SBTRCs. Each area on the form must be filled in electronically by the SBTRCs and retained in secured files of the client. The completion of the form is used as a tool for making decisions about the needs of the business, such as referral to technical assistance agencies for help, identifying the type of profession or trade of the business, the type of certification that the business holds, length of time in business, and location of the firm.
                </P>
                <P>
                    The SBTRCs must complete an Intake Form and retain copies in secured files in their offices. A limited amount of privacy information is requested on this form. We have included a Privacy Act Notice on the forms, informing individuals who are asked to supply information on the form that Public Law 95-507 and provisions of Title 49, of the U.S. Code, Section 332, the Minority Resource Center authorizes solicitation of the information; that provision of the information is voluntary; that the principal purpose for which the 
                    <PRTPAGE P="55893"/>
                    information is intended to be used is to assist the SBTRCs in developing a business plan or adjusting a business plan for small businesses, in order to increase their ability to market goods and services to buyers and potential users, interested in small business services; that routine uses which DOT may make of the information include analyzing the data collected to determine the effectiveness of services to small businesses, provided by the SBTRCs, including counseling, outreach, and financial services. Also, the data collection will be used by OSDBU to document the type of assistance provided to each small business that uses the services of the SBTRCs; and that the effect on the individual of not providing all or any part of the requested information will not be a condition to deny services to the small business firm. Request for information about another party may be denied unless DOT has the written permission of the individual to release the information to the requestor or unless the information is subject to disclosure under the Freedom of Information Act. This will assist the SBTRCs in developing a business plan or adjusting their business plan to increase its ability to market its goods and services to buyers and potential users of their services. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Small Business Transportation Resource Centers. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     100. 
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     The information will be collected monthly. 
                </P>
                <P>
                    <E T="03">Estimated Total Burden on Respondents:</E>
                     600 hours. 
                </P>
                <P>
                    <E T="03">The Regional Resource Center Monthly Report Form (DOT F 4502)</E>
                     for each SBTRC must submit a monthly status report of business activities conducted during the 30-day timeframe. The form is used to capture activities and accomplishments that were made by the Regional SBTRCs during the course of the month. In addition, the form includes a data collection section where numbers and hours are reported and a section that is assigned for a written narrative that provides back up that supports the data. Activities to be reported are (1) Counseling activity which identifies the counseling hours provided to businesses, number of new appointments, and follow-up on counseled clients. (2) Activity for businesses served identifies the type of small business that is helped, such as a DBE, 8(a), WOB, HubZone, SDB, SDVOB, or VOSB. (3) Marketing activity includes the name of an event attended by the SBTRC and the role played when participating in a conference, workshop or any other venue that relates to small businesses. (4) Meetings that are held with government representatives in the region, or at the state level, or an activity that is reported. (5) Events hosted by the SBTRCs, such as small business workshops, financial assistance workshops, matchmaking events, and activities that are reported on a monthly basis. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Small Business Transportation Resource Centers. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     100. 
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     The information will be collected monthly. 
                </P>
                <P>
                    <E T="03">Estimated Total Burden on Respondents:</E>
                     1,200 hours. 
                </P>
                <P>
                    <E T="03">Comments are invited on:</E>
                     (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the Department, including whether the information will have practical utility; (b) the accuracy of the Departments estimate of the burden of the proposed information collection; (c) ways to enhance the quality, utility and clarity of the information collection; and (d) ways to minimize the burden of the collection of information on respondents, by the use of electronic means, including the use of automated collection techniques or other forms of information technology. 
                </P>
                <P>All responses to this notice will be summarized and included in the request for OMB approval. All comments will also become a matter of public record. </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on September 19, 2008. </DATED>
                    <NAME>Patricia Lawton, </NAME>
                    <TITLE>DOT Clearance Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22633 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-9X-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <SUBJECT>Advisory Circular 120-16E, Air Carrier Maintenance Programs </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA) DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces the issuance and availability of Advisory Circular (AC) 120-16E, “Air Carrier Maintenance Programs”. This advisory circular (AC) is an update of AC 120-16D that was issued in 2003. It describes the scope, content, and functions of air carrier aircraft maintenance programs. It explains the background of these programs as well as the Federal Aviation Administration's regulatory requirements. Each of the 10 elements of air carrier maintenance programs is also described and explained. The material in this AC is not mandatory and does not constitute a regulation. However, when “must” or “will” are used in this AC, such use reflects actual regulatory requirements. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Advisory Circular 120-16E, Air Carrier Maintenance Programs was issued by the Office of the Director, Flight Standards Service, AFS-1 on September 11, 2008. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Russell S. Unangst, Jr., Technical Advisor, Airworthiness, AFS-305, Federal Aviation Administration, Aircraft Maintenance Division, Flight Standards Service, 800 Independence Ave., SW., Washington, DC 20591; telephone (202) 267-3786; facsimile (202) 267-5115, e-mail 
                        <E T="03">russell.unangst@faa.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>How to obtain a copy of this AC.</P>
                <P>
                    <E T="03">How To Obtain Copies:</E>
                     This AC can be read or downloaded from the Internet at 
                    <E T="03">http://rgl.faa.gov/</E>
                     under the “Advisory Circular” hyperlink. Paper copies of this AC will be available in approximately 6-8 weeks from the U.S. Department of Transportation, Subsequent Distribution Office, SVC-121.23, Ardmore East Business Center, 3341Q 75th Avenue, Landover, MD 20785. 
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on September 17, 2008. </DATED>
                    <NAME>Carol E. Giles, </NAME>
                    <TITLE>Manager, Aircraft Maintenance Division, Flight Standards Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22630 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <SUBJECT>Notice of Availability of Draft Environmental Impact Statement (DEIS) Containing a Notice of Public Comment Period and Schedule for a Public Information Workshop and Public Hearing for Proposed New Air Carrier Runway 9R/27L and Associated Developments at Palm Beach International Airport (PBIA) </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), Department of Transportation (DOT). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability, notice of comment period, notice of Public Information Workshop and Public Hearing.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Federal Aviation Administration (FAA) is issuing this 
                        <PRTPAGE P="55894"/>
                        notice to advise the public that a Draft Environmental Impact Statement (DEIS) for the Proposed New Runway and Associated Development at Palm Beach International Airport, has been prepared and is available for public review and comment. Your written comments on the DEIS and related documents can be sent to the individual listed in the section 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        . A Public Information Workshop and Public Hearing will be held on November 12, 2008. The public comment period will commence on September 26, 2008 and will close on November 24, 2008. 
                    </P>
                    <P>
                        <E T="03">Public Comment and Information Workshop/Public Hearing:</E>
                         The start of the public comment period on the DEIS and associated studies will start on September 26, 2008 and will close on November 24, 2008. A Public Information Workshop and Public Hearing will be held on November 12, 2008 in West Palm Beach. The purpose of the Public Information Workshop and Public Hearing and the public comment period is to comply with NEPA requirements to provide public disclosure and involvement concerning the scope and content of the DEIS, and to afford the public and other interested parties the opportunity to comment on the economic, social, and environmental effects of the proposed project and its consistency with the objectives of any planning that the community has carried out. The Public Information Workshop will begin at 4 p.m. (EST) and will end at 7 p.m. (EST). The Public Hearing will begin at 6 p.m. (EST) and run concurrently with the Public Information Workshop. The Public Information Workshop/Public Hearing will be held at the Palm Beach County Convention Center, Second Floor, 650 Okeechobee Boulevard, West Palm Beach, FL 33401. 
                    </P>
                    <P>You can review copies of the DEIS and related documents may be viewed during regular business hours at the following locations: </P>
                    <P>1. PBC Library Main Branch, 3650 Summit Boulevard, West Palm Beach, FL 33406. </P>
                    <P>2. PBC Library Greenacres Branch, 3750 Jog Road, Greenacres, FL 33467. </P>
                    <P>3. PBC Library Okeechobee Boulevard Branch, 5689 West Okeechobee Boulevard, West Palm Beach, FL 33417. </P>
                    <P>4. WPB Public Library, 100 Clematis Street, West Palm Beach, FL 33401. </P>
                    <P>
                        Copies of the DEIS and related documents will also be available for review by appointment only at the following FAA and Palm Beach County Department of Airports offices: Federal Aviation Administration, Orlando Airports District Office, 5950 Hazeltine National Drive, Citadel International Building, Suite 400, Orlando, FL, (407) 812-6331; Palm Beach International Airport, Palm Beach County Department of Airports Office, 846 Palm Beach International Airport, West Palm Beach, FL, (561) 471-7412. Please schedule an appointment to review the DEIS in advance. A copy of the DEIS will also be available September 26, 2008 on the project Web site at 
                        <E T="03">http://www.pbia-eis.com</E>
                        . 
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lindy McDowell, Environmental Specialist, Federal Aviation Administration, Orlando Airports District Office, 5950 Hazeltine National Drive, Citadel International Building, Suite 400, Orlando, FL. You can contact Ms. McDowell at (407) 812-6331. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Federal Aviation Administration (FAA) is issuing this Notice of Availability to advise the public that a DEIS will be available for public review beginning September 26, 2008. The DEIS details the proposed development of a new air carrier runway, modification of existing runways and taxiways, relocation of general aviation support facilities, installation of navigational aids (NAVAIDS), implementation of Global Positioning System (GPS) approaches, relocation of a Very-High Frequency Omni-directional Radio Range (VOR) antenna, land acquisition, drainage canal relocation, and other connected actions at Palm Beach International Airport (PBIA), West Palm Beach, Florida. </P>
                <P>The DEIS presents the purpose and need for the proposed project, a comprehensive analysis of the alternatives to the proposed project, including the No-Action alternative and potential environmental impacts associated with the proposed development of the new air carrier runway and related improvements at PBIA. </P>
                <P>The FAA encourages the public to comment on the scope and content of the DEIS. Comments should be as specific as possible and address the analysis of potential environmental impacts and the adequacy of the proposed action or merits of alternatives and the proposed mitigation. Reviewers should organize their comments so they are meaningful and make the FAA aware of the viewer's interests and concerns using quotations and other specific references to the text of the DEIS and related documents. Specific comments not given during the DEIS comment period may not be considered if they are raised later in the decision making process. This commenting procedure is intended to ensure that substantive comments and concerns are made available to the FAA in a timely manner so that the FAA has an opportunity to address them. </P>
                <P>
                    We encourage the public to comment on the DEIS and related documents. You can submit your comments verbally or in writing at the Public Information Workshop and/or Public Hearing or you can also submit your comments in writing to the FAA at the address listed in the section entitled 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    . The comment period will close on November 24, 2008. 
                </P>
                <P>In addition to the Public Information Workshop and Public Hearing being conducted to provide public involvement concerning the scope and content of the DEIS, they are also being conducted to provide public involvement and input in regard to historic resources in compliance with Section 106 of the National Historic Preservation Act of 1966—36 CFR 800. </P>
                <SIG>
                    <DATED>Issued in Orlando, FL, on September 22, 2008. </DATED>
                    <NAME>W. Dean Stringer,</NAME>
                    <TITLE>Manager, FAA, Orlando Airports District Office.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22631 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Highway Administration </SUBAGY>
                <SUBJECT>Notice of Final Federal Agency Action on Proposed Highway in Illinois </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Highway Administration (FHWA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of limitation on claims for judicial review of actions by FHWA and other Federal agencies. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces actions taken by the FHWA and other Federal agencies that are final within the meaning of 23 U.S.C. 139(l)(1). The actions relate to a proposed highway project, the Prairie Parkway, for construction of an access-controlled, four-lane freeway on new right-of-way between 1-80 and 1-88 and the widening of IL-47 to four-lanes from 1-80 to Caton Farm Road in Grundy, Kendall and Kane Counties, Illinois. Those actions grant licenses, permits and approvals for the project. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        By this notice, the FHWA is advising the public of final agency actions subject to 23 U.S.C. 139(l)(1). A claim seeking judicial review of the Federal agency actions of the highway project will be barred unless the claim is filed on or before March 25, 2009. If the Federal law that authorizes judicial 
                        <PRTPAGE P="55895"/>
                        review of a claim provides a time period of less than 180 days for filing such claim, then that shorter time period still applies. 
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Norman R. Stoner, P.E., Division Administrator, Federal Highway Administration, 3250 Executive Park Drive, Springfield, Illinois 62703, Phone: (217) 492-4600, E-mail address: 
                        <E T="03">Norman.Stoner@fhwa.dot.gov.</E>
                         The FHWA Illinois Division Office's normal business hours are 7:30 a.m. to 4:15 p.m. You may also contact Mr. George F. Ryan, P.E., Illinois Department of Transportation, Deputy Director of Highways, Region Two Engineer, 700 E. Norris Drive, Ottawa, Illinois 61350, Phone: (815) 434-6131, e-Mail address: 
                        <E T="03">George.Ryan@illinois.gov.</E>
                         The Illinois Department of Transportation Region Two's normal business hours are 8 a.m. to 4:30 p.m. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given that the FHWA and other Federal agencies have taken final agency actions by issuing licenses, permits and approvals for the following highway project in the State of Illinois: construction of a 37.1 mile, access controlled, four-lane freeway on new right-of-way between 1-80 and 1-88 (the Prairie Parkway) and the widening of 11.5 miles of IL-47 to four lanes from 1-80 to Caton Farm Road. The actions by the Federal agencies, and the laws under which such actions were taken, are described in the Final Environmental Impact Statement (FEIS) for the project approved on February 15, 2008; and the Record of Decision (ROD) issued on September 19, 2008; and other documents in the FHWA administrative record. The FEIS, ROD and other documents in the FHWA administrative record are available by contacting FHWA or the Illinois Department of Transportation at the addresses above. Project information can also be viewed and downloaded from the project Web site at 
                    <E T="03">http://www.prairie-parkway.com</E>
                     and the FEIS can be downloaded from 
                    <E T="03">http://www.dot.il.gov/desenv/env.html</E>
                     or hard copies of the FEIS and the ROD are available upon request. 
                </P>
                <P>This notice applies to all Federal agency decisions as of the issuance date of this notice and all laws under which such actions were taken, including, but not limited to: </P>
                <P>1. General: National Environmental Policy Act (NEPA) [42 U.S.C. 4321-4351] Federal-Aid Highway Act [23 U.S.C. 109]. </P>
                <P>2. Air: Clean Air Act [42 U.S.C. 7401-7671(q)]. </P>
                <P>3. Land: Section 4(f) of the Department of Transportation Act of 1966 [49 U.S.C. 303]. </P>
                <P>4. Wildlife: Endangered Species Act [16 U.S.C. 1531-1544 and Section 1536]; Migratory Bird Treaty Act [16 U.S.C. 703-712]. </P>
                <P>
                    5. Historic and Cultural Resources: Section 106 of the National Historic Preservation Act of 1966, as amended [16 U.S.C. 470(f) 
                    <E T="03">et seq.</E>
                    ]; Archaeological and Historic Preservation Act (AHPA) [16 U.S.C. 469-469(c)]. 
                </P>
                <P>6. Social and Economic: Civil Rights Act of 1964 [42 U.S.C. 2000(d) 2000(d)(1)]; Farmland Protection Policy Act (FPPA) [7 U.S.C. 4201-4209]. </P>
                <P>7. Wetlands and Water Resources: Clean Water Act (Section 401 and 404) [33 U.S.C. 1251-1377]; Wild and Scenic Rivers Act [16 U.S.C. 1271-1287]. </P>
                <P>8. Executive Orders: E.O. 11990 Protection of Wetlands; E.O. 11988 Floodplain  Management; E.O. 12898 Federal Actions to Address Environmental Justice in Minority Populations and Low Income Populations. </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Program Number 20.205, Highway Research, Planning and Construction. The regulations implementing Executive Order 12372 regarding intergovernmental consultation on Federal programs and activities apply to this program).</FP>
                </EXTRACT>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>23 U.S.C. 139(l)(1). </P>
                </AUTH>
                <SIG>
                    <DATED>Issued on: September 19, 2008. </DATED>
                    <NAME>Norman R. Stoner, </NAME>
                    <TITLE>Division Administrator, Springfield, Illinois.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22598 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-22-M </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Highway Administration </SUBAGY>
                <SUBJECT>Notice of Final Federal Agency Actions on Proposed Highway in Nevada </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Highway Administration (FHWA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Limitation on Claims for Judicial Review of Actions by FHWA, United States Fish and Wildlife Service (USFWS), and Other Federal Agencies. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice announces actions taken by the FHWA, USFWS, and other Federal agencies that are final within the meaning of 23 U.S.C. 139(
                        <E T="03">l</E>
                        )(1). The actions relate to a proposed highway project, U.S. Highway 95 (US 95), from Washington Avenue to Kyle Canyon Road (State Route 157) for a distance of 13 miles, in Clark County in the State of Nevada. Those actions grant licenses, permits, and approvals for the project. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        By this notice, the FHWA is advising the public of final agency actions subject to 23 U.S.C. 139(
                        <E T="03">l</E>
                        )(1). A claim seeking judicial review of the Federal agency actions on the highway project will be barred unless the claim is filed on or before March 25, 2009. If the Federal law that authorizes judicial review of a claim provides a time period less than 180 days for filing such claim, then that shorter time period still applies. 
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For FHWA: Mr. Abdelmoez Abdalla, Environmental Program Manager, Federal Highway Administration, 705 North Plaza Street, Carson City, Nevada 89701-0602; telephone: (775) 687-1231; e-mail 
                        <E T="03">Abdelmoez.Abdalla@fhwa.dot.gov</E>
                        . The FHWA Nevada Division Office's regular business hours are 7:30 a.m. to 4 p.m. (Pacific Standard Time). For the Nevada Department of Transportation (NDOT): Mr. Steve M. Cooke, P.E., Chief, Environmental Services Division, Nevada Department of Transportation, 1263 South Stewart Street, Carson City, Nevada 89712; telephone: (775) 888-7013; e-mail: 
                        <E T="03">scooke@dot.state.nv.us</E>
                        . The NDOT office's regular business hours are 8 a.m. to 5 p.m. (Pacific Standard Time). For USFWS: Mr. Michael Burroughs, U.S. Fish and Wildlife Service, 4701 North Torrey Pines Drive, Las Vegas, Nevada 89130; telephone: (702) 515-5230; e-mail 
                        <E T="03">Michael_Burroughs@fws.gov</E>
                        . The U.S. Fish and Wildlife Service office's regular business hours are 7:30 a.m. to 4 p.m. (Pacific Standard Time). 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given that the FHWA, USFWS, and other Federal agencies have taken final agency actions subject to 23 U.S.C. 139(
                    <E T="03">l</E>
                    )(1) by issuing licenses, permits, and approvals for the following highway project in Clark County in the State of Nevada. The proposed improvements to US 95, from Washington Avenue to Kyle Canyon Road (State Route 157), a distance of 13 miles, would consist of widening the roadway to include one high-occupancy vehicle (HOV) lane in each direction and six general purpose lanes (three in each direction) from Durango Drive to Kyle Canyon Road. Other project components would include new service interchanges at Horse Drive and Kyle Canyon Road, the system-to-system interchange between US 95 and the Bruce Woodbury Beltway (CC-215), and improvements to Cheyenne Avenue, Rancho Drive/Ann Road, and Durango Drive. The federal project reference number is SPF-095-2(043). The actions by the Federal agencies, and the laws under which 
                    <PRTPAGE P="55896"/>
                    actions were taken, are described in the 
                    <E T="03">Environmental Assessment (EA) for US 95 Northwest Washington Avenue to Kyle Canyon Road,</E>
                     FHWA-NV-EA 07.01. A Finding of No Significant Impact (FONSI) was issued on May 7, 2008. The EA, FONSI, and other project records are available by contacting the FHWA or the NDOT Environmental Services Division at the addresses provided above. USFWS also issued its biological opinion (File No. 84320-2008-F-0428) for the project's possible adverse effects on the desert tortoise (
                    <E T="03">Gopherus agassizii</E>
                    ) on August 22, 2008. The USFWS biological opinion is available by contacting the USFWS at the address provided above. 
                </P>
                <P>This notice applies to all Federal agency decisions as of the issuance date of this notice and all laws under which such actions were taken, including but not limited to: </P>
                <P>1. General: National Environmental Policy Act (NEPA) [42 U.S.C. 4321-4351]; Federal-Aid Highway Act [23 U.S.C. 109 and 23 U.S.C. 128]; Public Hearing [23 U.S.C. 128]. </P>
                <P>2. Air: Clean Air Act [42 U.S.C. 7401-7671(q)]. </P>
                <P>3. Noise: Procedures for Abatement of Highway Traffic Noise and Construction Noise [23 U.S.C. 109(h), 109(i); 42 U.S.C. 4331, 4332; sec. 339(b), Pub. L. 104-59, 109 Stat. 568, 605; 49 CFR 1.48(b)]. </P>
                <P>
                    4. Historic and Cultural Resources: Section 106 of the National Historic Preservation Act of 1966, as amended [16 U.S.C. 470(f) 
                    <E T="03">et seq.</E>
                    ]. 
                </P>
                <P>5. Wildlife: Endangered Species Act [16 U.S.C. 1531-1544 and Section 1536]; Fish and Wildlife Coordination Act [16 U.S.C. 661-667(d)]; Migratory Bird Treaty Act [16 U.S.C. 703-712]. </P>
                <P>6. Social and Economic: Civil Rights Act of 1964 [42 U.S.C. 2000(d)-2000(d)(1)]. </P>
                <P>7. Executive Orders: E.O. 11990, Protection of Wetlands; E.O. 11988, Floodplain Management; E.O. 12898, Federal Actions to Address Environmental Justice in Minority Populations and Low Income Populations; E.O. 11593, Protection and Enhancement of Cultural Resources; E.O. 13007, Indian Sacred Sites; E.O. 13287, Preserve America; E.O. 13175, Consultation and Coordination with Indian Tribal Governments; E.O. 11514, Protection and Enhancement of Environmental Quality; E. O. 13112, Invasive Species. </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Program Number 20.205, Highway Planning and Construction. The regulations implementing Executive Order 12372 regarding intergovernmental consultation on Federal programs and activities apply to this program.)</FP>
                </EXTRACT>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        23 U.S.C. 139(
                        <E T="03">l</E>
                        )(1). 
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Issued on: September 16, 2008. </DATED>
                    <NAME>Susan Klekar, </NAME>
                    <TITLE>Division Administrator, Carson City, Nevada.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22572 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-22-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Highway Administration</SUBAGY>
                <SUBJECT>Notice of Final Federal Agency Actions on Proposed Highway in Washington </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Highway Administration (FHWA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of limitation on claims for judicial review of actions by FHWA and other federal agencies.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces actions taken by the FHWA and other Federal agencies that are final within the meaning of 23 U.S.C. 139(l)(1). The actions relate to the I-405, NE 8th Street to SR 520 Improvement Project (The Project) located in Bellevue; King County; I-405 in the State of Washington. These actions grant licenses, permits, and approvals for the project. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>By this notice, the FHWA is advising the public of final agency actions subject to 23 U.S.C. 139(l)(1). A claim seeking judicial review of the Federal agency actions on any of the listed highway projects will be barred unless the claim is filed on or before March 25, 2009. If the Federal law that authorizes judicial review of a claim provides a time period of less than 180 days for filing such claim, then that shorter time period still applies. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Pete Jilek, Urban Area Engineer, Federal Highway Administration, 711 S. Capitol Way #501, Olympia, Washington 98501; telephone: (360) 753-9480; and e-mail: 
                        <E T="03">pete.jilek@fhwa.dot.gov.</E>
                         The FHWA Washington Division's Urban Area Engineer's regular office hours are between 7 a.m. and 4 p.m. (Pacific Time). You may also contact William Jordan, I-405 Environmental Manager, Washington State Department of Transportation, 600-108th Avenue, NE., Suite 405, Bellevue, Washington 98004; telephone: (425) 456-8547; and e-mail: 
                        <E T="03">william.jordan@i405.wsdot.wa.gov.</E>
                         The I-405 Corridor Program's regular office hours are between 8 a.m. and 5 p.m. (Pacific Time). 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given that the FHWA and other Federal agencies have taken final agency actions by issuing licenses, permits, and approvals for the following highway project in the State of Washington: I-405, NE 8th Street to SR 520 Improvement Project. The Project extends approximately 1.5 miles north along I-405 from south of NE 8th Street to the SR 520 interchange and approximately 1.6 miles east along SR 520, from the I-405 interchange to just east of 134th Avenue, NE. The Project improves safety and reduces congestion in the vicinity of the I-405 and SR 520 interchange in Bellevue. The Project constructs grade-separated ramps on northbound I-405 to separate the I-405 traffic exiting to SR 520 from traffic entering I-405 at NE 8th Street in downtown Bellevue; reconstructs the NE 12th Street bridge over I-405, constructs a new three-lane eastbound collector-distributor lane on SR 520 to separate the on- and off-ramp traffic between I-405 and 124th Avenue, NE.; and reconstructs the 124th Avenue, NE. interchange off-ramp. These actions by the Federal agencies, and the laws under which such actions were taken, are described in the May 2008 Environmental Assessment (EA) and in the September 17, 2008 Finding of No Significant Impact (FONSI), and in other documents in the FHWA administrative record. The EA, FONSI and other documents in the FHWA administrative record are available by contacting FHWA or WSDOT at the addresses provided above. The EA can be viewed and downloaded from the project Web site at 
                    <E T="03">http://www.wsdot.wa.gov/Projects/i405/corridor/sr520tone8thEA.htm</E>
                     or viewed at public libraries in the project area. Since federal funding is not currently available for this project, an FHWA project number has not been established. 
                </P>
                <P>This notice applies to all Federal agency decisions on the project as of the issuance date of this notice and all laws under which such actions were taken, including but not limited to: </P>
                <P>1. General: National Environmental Policy Act [42 U.S.C. 4321-4351]; Federal-Aid Highway Act [23 U.S.C. 109]. </P>
                <P>2. Air: Clean Air Act, as amended [42 U.S.C. 7401-7671(q)]. </P>
                <P>3. Land: Section 4(f) of the Department of Transportation Act of 1966 [49 U.S.C. 303]; Landscaping and Scenic Enhancement (Wildflowers) [23 U.S.C. 319]. </P>
                <P>
                    4. Wildlife: Endangered Species Act [16 U.S.C. 1531-1544]; Anadromous Fish Conservation Act [16 U.S.C. 757(a)-757(g)]; Fish and Wildlife Coordination Act [16 U.S.C. 661-667(d)]; Magnuson-Stevenson Fishery 
                    <PRTPAGE P="55897"/>
                    Conservation and Management Act of 1976, as amended [16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                    ]. 
                </P>
                <P>
                    5. Historic and Cultural Resources: Section 106 of the National Historic Preservation Act of 1966, as amended [16 U.S.C. 470(f) 
                    <E T="03">et seq.</E>
                    ]; Archaeological Resources Protection Act of 1977 [16 U.S.C. 470(aa)-11]; Archaeological and Historic Preservation Act [16 U.S.C. 469-469(c)]; Native American Grave Protection and Repatriation Act [25 U.S.C. 3001-3013]. 
                </P>
                <P>6. Social and Economic: Civil Rights Act of 1964 [42 U.S.C. 2000(d)-2000(d)(1)]; American Indian Religious Freedom Act [42 U.S.C. 1996]; Farmland Protection Policy Act [7 U.S.C. 4201-4209]; the Uniform Relocation Assistance and Real Property Acquisition Policies Act of 1970, as amended [42 U.S.C. 61]. </P>
                <P>7. Wetlands and Water Resources: Clean Water Act, 33 U.S.C. 1251-1377 (Section 404, Section 401, Section 319); Coastal Zone Management Act [16 U.S.C. 1451-1465]; Land and Water Conservation Fund [16 U.S.C. 4601-4604]; Safe Drinking Water Act [42 U.S.C. 300(f)-300(j)(6)]; Rivers and Harbors Act of 1899 [33 U.S.C. 401-406]; TEA-21 Wetlands Mitigation [23 U.S.C. 103(b)(6)(m), 133(b)(11)]; Flood Disaster Protection Act [42 U.S.C. 4001-4128]. </P>
                <P>8. Hazardous Materials: Comprehensive Environmental Response, Compensation, and Liability Act [42 U.S.C. 9601-9675]; Superfund Amendments and Reauthorization Act of 1986 [Pub. L. 99-499]; Resource Conservation and Recovery Act [42 U.S.C. 6901-6992(k)]. </P>
                <P>9. Executive Orders: E.O. 11990 Protection of Wetlands; E.O. 11988 Floodplain Management; E.O. 12898, Federal Actions to Address Environmental Justice in Minority Populations and Low Income Populations; E.O. 11593 Protection and Enhancement of Cultural Resources; E.O. 13007 Indian Sacred Sites; E.O. 13287 Preserve America; E.O. 13175 Consultation and Coordination with Indian Tribal Governments; E.O. 11514 Protection and Enhancement of Environmental Quality; E.O. 13112 Invasive Species.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Program Number 20.205, Highway Planning and Construction. The regulations implementing Executive Order 12372 regarding intergovernmental consultation on Federal programs and activities apply to this program.)</FP>
                </EXTRACT>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>23 U.S.C. 139(l)(1). </P>
                </AUTH>
                <SIG>
                    <DATED>Issued on: September 22, 2008. </DATED>
                    <NAME>Peter A. Jilek, </NAME>
                    <TITLE>Urban Area Engineer, Olympia, Washington.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E8-22695 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Transit Administration </SUBAGY>
                <SUBJECT>Notice of Limitation on Claims Against Proposed Public Transportation Projects </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Transit Administration (FTA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of limitation on claims. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces final environmental actions taken by the Federal Transit Administration (FTA) for public transportation projects in the following areas: Fort Collins, Colorado; Belle Glade, Florida; Gustavus, Alaska; Dallas, Texas; West Covina, California; and Andover, New Jersey. The purpose of this notice is to announce publicly the environmental decisions by FTA on the subject projects and to activate the limitation on any claims that may challenge these final environmental actions. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>By this notice, FTA is advising the public of final agency actions subject to Title 23, United States Code (U.S.C.), section 139(l). A claim seeking judicial review of the FTA actions announced herein for the listed public transportation projects will be barred unless the claim is filed on or before March 25, 2009. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Elizabeth Zelasko, Environmental Protection Specialist, Office of Planning and Environment, 202-366-0244, or Christopher Van Wyk, Attorney-Advisor, Office of Chief Counsel, 202-366-1733. FTA is located at 1200 New Jersey Avenue, SE., Washington, DC 20590. Office hours are from 9 a.m. to 5:30 p.m., e.t., Monday through Friday, except Federal holidays. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given that FTA has taken final agency actions by issuing certain approvals for the public transportation projects listed below. The actions on these projects, as well as the laws under which such actions were taken, are described in the documentation issued in connection with the project to comply with the National Environmental Policy Act (NEPA), and in other documents in the FTA administrative record for the project. The final agency environmental decision documents—Records of Decision (ROD) or Findings of No Significant Impact (FONSI)—for the listed projects are available online at 
                    <E T="03">http://www.fta.dot.gov/planning/environment/planning_environment_documents.html</E>
                     or may be obtained by contacting the FTA Regional Office for the metropolitan area where the project is located. Contact information for the FTA Regional Offices may be found at 
                    <E T="03">http://www.fta.dot.gov</E>
                    . 
                </P>
                <P>This notice applies to all FTA decisions on the listed projects as of the issuance date of this notice and all laws under which such actions were taken, including, but not limited to, the National Environmental Policy Act (NEPA) [42 U.S.C. 4321-4375], Section 4(f) of the Department of Transportation Act of 1966 [49 U.S.C. 303], Section 106 of the National Historic Preservation Act [16 U.S.C. 470f], and the Clean Air Act [42 U.S.C. 7401-7671q]. </P>
                <P>The projects and actions that are the subject of this notice are:</P>
                <P>
                    1. 
                    <E T="03">Project name and location:</E>
                     The Mason Corridor MAX Bus Rapid Transit (BRT) Project, Fort Collins, Colorado. 
                    <E T="03">Project sponsor:</E>
                     City of Fort Collins. 
                    <E T="03">Project description:</E>
                     The FTA and City of Fort Collins have completed an Environmental Assessment (EA) for a five-mile, north-south BRT system that will be located in the central area of Fort Collins. The BRT system that extends from Cherry Street to south of Harmony Road will involve 3.6 miles of exclusive guideway with 1.4 miles of mixed street traffic. The project will also include a transit center, two-way conversion of N. Mason Street and Howes Street, and several park-n-ride lots and BRT stations. 
                    <E T="03">Final Agency Actions:</E>
                     FONSI signed on September 9, 2008. Section 106 Memorandum of Agreement signed on August 1, 2008; Project-level Air Conformity Determination; and Section 4(f) de minimis impact finding. 
                    <E T="03">Supporting documentation:</E>
                     Mason Corridor Mason Express Bus Rapid Transit Environmental Assessment signed May 27, 2008. 
                </P>
                <P>
                    2. 
                    <E T="03">Project name and location:</E>
                     Palm Tran Satellite Bus Facility, Belle Glade, Florida. 
                    <E T="03">Project sponsor:</E>
                     Palm Tran. 
                    <E T="03">Project description:</E>
                     The project involves the construction of a satellite bus facility with a 7,600-square-foot maintenance and bus storage building, and a bus parking area. The satellite bus facility will be near Belle Glade, Florida and built as a joint project with the West County Government Center and Correctional Facilities. 
                    <E T="03">Final agency actions:</E>
                     FONSI signed on August 11, 2008; Project-level Air Conformity Determination; Section 106 Finding of No Historic Properties Affected. 
                    <E T="03">Supporting documentation:</E>
                     Palm Tran 
                    <PRTPAGE P="55898"/>
                    Satellite Bus Facility Environmental Assessment released on June 15, 2008. 
                </P>
                <P>
                    3. 
                    <E T="03">Project name and location:</E>
                     Gustavus Causeway Replacement, Gustavus, Alaska. 
                    <E T="03">Project sponsor:</E>
                     State of Alaska Department of Transportation and Public Facilities (Alaska DOT&amp;PF). 
                    <E T="03">Project description:</E>
                     Alaska DOT&amp;PF intends to replace a dock facility in Gustavus, Alaska that supports freight movement, bulk fuel transfer, and marine passenger vessels. The replacement dock will include a wider trestle to allow two-way traffic, a securable staging area for passenger vehicles and freight, and an upgraded fuel-transfer pipeline. 
                    <E T="03">Final agency actions:</E>
                     FONSI signed on August 14, 2008. 
                    <E T="03">Supporting documentation:</E>
                     Environmental Assessment for the Gustavus Causeway Replacement Project issued in May 2008. 
                </P>
                <P>
                    4. 
                    <E T="03">Project name and location:</E>
                     Northwest Corridor to Irving/Dallas-Fort Worth Light Rail Transit Line, Dallas, Texas. 
                    <E T="03">Project sponsor:</E>
                     Dallas Area Rapid Transit (DART). 
                    <E T="03">Project description:</E>
                     DART is proposing to construct a 9.3-mile light rail transit extension from the existing Northwest Corridor line to the Dallas/Forth Worth Airport Property. The project will involve the construction of six light rail transit stations and seven traction power substations and the purchase of ten light rail vehicles. DART would defer construction of two proposed light rail stations until they are warranted by development. 
                    <E T="03">Final agency actions:</E>
                     ROD signed on September 5, 2008; Section 106 Finding of No Historic Properties Affected; Section 4(f) finding, and Project-level Air Conformity Determination. 
                    <E T="03">Supporting documentation:</E>
                     Northwest Corridor to Irving/Dallas-Fort Worth Light Rail Transit Line Environmental Impact Statement signed on July 17, 2008. 
                </P>
                <P>
                    5. 
                    <E T="03">Project name and location:</E>
                     Foothill Transit Park-and-Ride, West Covina, California. 
                    <E T="03">Project sponsor:</E>
                     Foothill Transit. 
                    <E T="03">Project description:</E>
                     The project involves the construction of a six-level parking structure on an existing surface parking lot in West Covina, California. 
                    <E T="03">Final agency actions:</E>
                     FONSI signed on July 10, 2008; Project-level Air Conformity Determination; Section 106 Finding of No Historic Properties Affected. 
                    <E T="03">Supporting documentation:</E>
                     Environmental Assessment for the Foothill Transit Park-and-Ride signed on May 23, 2008. 
                </P>
                <P>
                    6. 
                    <E T="03">Project name and location:</E>
                     Lackawanna Cut-Off Rail Restoration Project, Minimal Operable Segment, Andover, New Jersey. 
                    <E T="03">Project sponsor:</E>
                     New Jersey Transit (NJT). 
                    <E T="03">Project description:</E>
                     The project involves the construction of one station and parking facility with 65 spaces in Andover, New Jersey, construction of 7.3 miles of new railroad infrastructure (track, signals, communications, and grade crossing improvements) on existing right-of-way in New Jersey, and rehabilitation of the Roseville Tunnel. The service will operate out to Andover, New Jersey from Hoboken, New Jersey, extending from the existing NJT Morris &amp; Essex and Montclair-Boonton Line trains. 
                    <E T="03">Final agency actions:</E>
                     FONSI signed on September 12, 2008; Section 106 Finding of No Adverse Effect. 
                    <E T="03">Supporting documentation:</E>
                     Environmental Assessment on the Lackawanna Cut-Off Rail Restoration Project issued on July 1, 2008. 
                </P>
                <SIG>
                    <DATED>Issued on: September 17, 2008. </DATED>
                    <NAME>Susan Borinsky, </NAME>
                    <TITLE>Associate Administrator for Planning and Environment, Washington, DC.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E8-22634 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-57-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Surface Transportation Board </SUBAGY>
                <DEPDOC>[STB Docket No. AB-6 (Sub-No. 464X)] </DEPDOC>
                <SUBJECT>BNSF Railway Company—Abandonment Exemption—in King County, WA </SUBJECT>
                <P>
                    BNSF Railway Company (BNSF) has filed a notice of exemption under 49 CFR 1152 Subpart F-
                    <E T="03">Exempt Abandonments</E>
                     to abandon a 5.60-mile rail line 
                    <SU>1</SU>
                    <FTREF/>
                     between milepost 5.00, at Kennydale, and milepost 10.60 at Wilburton, in King County, WA.
                    <SU>2</SU>
                    <FTREF/>
                     The line traverses United States Postal Service Zip Codes 98004, 98005, 98006, and 98056. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The rail line at issue in this proceeding is part of a larger BNSF segment in King County that is the subject of two pending proceedings before the Board. For information regarding these proceedings see: 
                        <E T="03">BNSF Railway Company—Abandonment Exemption—in King County, WA</E>
                        , STB Docket No. AB-6 (Sub-No. 465X) (STB served Aug. 29, 2008), and 
                        <E T="03">The Port of Seattle—Acquisition Exemption—Certain Assets of BNSF Railway Company</E>
                        , STB Finance Docket No. 35128 (STB served June 20, 2008). An abandonment proposal involving a connecting BNSF branch line is also pending in 
                        <E T="03">BNSF Railway Company—Abandonment Exemption—in King County, WA</E>
                        , STB Docket No. AB-6 (Sub-No. 463X) (STB served Sept. 26, 2008). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         By petition for exemption filed on September 8, 2008, BNSF is also seeking an exemption from the offer of financial assistance (OFA) requirements of 49 U.S.C. 10904. The merits of the petition will be addressed in a separate decision. 
                    </P>
                </FTNT>
                <P>BNSF has certified that: (1) No local traffic has moved over the line for at least 2 years; (2) all overhead traffic on the line has been rerouted over other lines; (3) no formal complaint filed by a user of rail service on the line (or by a state or local government entity acting on behalf of such user) regarding cessation of service over the line either is pending with the Surface Transportation Board or with any U.S. District Court or has been decided in favor of complainant within the 2-year period; and (4) the requirements at 49 CFR 1105.7 (environmental reports), 49 CFR 1105.8 (historic reports), 49 CFR 1105.11 (transmittal letter), 49 CFR 1105.12 (newspaper publication), and 49 CFR 1152.50(d)(1) (notice to governmental agencies) have been met. </P>
                <P>
                    As a condition to this exemption, any employee adversely affected by the abandonment shall be protected under 
                    <E T="03">Oregon Short Line R. Co.—Abandonment—Goshen</E>
                    , 360 I.C.C. 91 (1979). To address whether this condition adequately protects affected employees, a petition for partial revocation under 49 U.S.C. 10502(d) must be filed. 
                </P>
                <P>
                    Provided no formal expression of intent to file an OFA has been received, this exemption will be effective on October 28, 2008, unless stayed pending reconsideration. Petitions to stay that do not involve environmental issues,
                    <SU>3</SU>
                    <FTREF/>
                     formal expressions of intent to file an OFA under 49 CFR 1152.27(c)(2),
                    <SU>4</SU>
                    <FTREF/>
                     and trail use/rail banking requests under 49 CFR 1152.29 must be filed by October 6, 2008. Petitions to reopen or requests for public use conditions under 49 CFR 1152.28 must be filed by October 16, 2008, with the Surface Transportation Board, 395 E Street, SW., Washington, DC 20423-0001. 
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Board will grant a stay if an informed decision on environmental issues (whether raised by a party or by the Board's Section of Environmental Analysis (SEA) in its independent investigation) cannot be made before the exemption's effective date. 
                        <E T="03">See Exemption of Out-of-Service Rail Lines</E>
                        , 5 I.C.C.2d 377 (1989). Any request for a stay should be filed as soon as possible so that the Board may take appropriate action before the exemption's effective date. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Effective July 18, 2008, the filing fee for an OFA increased to $1,500. 
                        <E T="03">See Regulations Governing Fees for Services Performed in Connection With Licensing and Related Services—2008 update</E>
                        , STB Ex Parte No. 542 (Sub-No. 15) (STB served June 18, 2008). 
                    </P>
                </FTNT>
                <P>A copy of any petition filed with the Board should be sent to BNSF's representative: Kristy D. Clark, BNSF Railway Company, 2500 Lou Menk Drive, AOB-3, Fort Worth, TX 76131. </P>
                <P>
                    If the verified notice contains false or misleading information, the exemption is void 
                    <E T="03">ab initio</E>
                    .
                </P>
                <P>
                    BNSF has filed both an environmental report and a historic report that address the effects, if any, of the abandonment on the environment and historic resources. SEA will issue an environmental assessment (EA) by 
                    <PRTPAGE P="55899"/>
                    October 3, 2008. Interested persons may obtain a copy of the EA by writing to SEA (Room 1100, Surface Transportation Board, Washington, DC 20423-0001) or by calling SEA, at (202) 245-0305. [Assistance for the hearing impaired is available through the Federal Information Relay Service (FIRS) at 1-800-877-8339.] Comments on environmental and historic preservation matters must be filed within 15 days after the EA becomes available to the public. 
                </P>
                <P>Environmental, historic preservation, public use, or trail use/rail banking conditions will be imposed, where appropriate, in a subsequent decision. </P>
                <P>Pursuant to the provisions of 49 CFR 1152.29(e)(2), BNSF shall file a notice of consummation with the Board to signify that it has exercised the authority granted and fully abandoned the line. If consummation has not been effected by BNSF's filing of a notice of consummation by September 26, 2009, and there are no legal or regulatory barriers to consummation, the authority to abandon will automatically expire. </P>
                <P>
                    Board decisions and notices are available on our Web site at 
                    <E T="03">http://www.stb.dot.gov</E>
                    . 
                </P>
                <SIG>
                    <DATED>Decided: September 22, 2008. </DATED>
                    <P>By the Board, David M. Konschnik, Director, Office of Proceedings. </P>
                    <NAME>Anne K. Quinlan, </NAME>
                    <TITLE>Acting Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22657 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4915-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Surface Transportation Board </SUBAGY>
                <DEPDOC>[STB Docket No. AB-6 (Sub-No. 463X)] </DEPDOC>
                <SUBJECT>BNSF Railway Company—Abandonment Exemption—in King County, WA </SUBJECT>
                <P>
                    BNSF Railway Company (BNSF) has filed a notice of exemption under 49 CFR 1152 Subpart F-
                    <E T="03">Exempt Abandonments</E>
                     to abandon a 7.30-mile rail line 
                    <SU>1</SU>
                    <FTREF/>
                     located between milepost 0.00 at Woodinville and milepost 7.30 at Redmond, King County, WA.
                    <SU>2</SU>
                    <FTREF/>
                     The line traverses United States Postal Service Zip Codes 98011, 98034, 98052, and 98072. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The rail line at issue is a branch line which connects with another BNSF line at Woodinville, WA. That BNSF line is the subject of three pending proceedings before the Board. For information regarding these proceedings see: 
                        <E T="03">BNSF Railway Company—Abandonment Exemption—in King County, WA,</E>
                         STB Docket No. AB-6 (Sub-No. 465X) (STB served Aug. 29, 2008), 
                        <E T="03">The Port of Seattle—Acquisition Exemption—Certain Assets of BNSF Railway Company,</E>
                         STB Finance Docket No. 35128 (STB served June 20, 2008), and 
                        <E T="03">BNSF Railway Company—Abandonment Exemption—in King County, WA,</E>
                         STB Docket No. AB-6 (Sub-No. 464X) (STB served Sept. 26, 2008). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         By petition filed on September 8, 2008, BNSF is also seeking an exemption from the offer of financial assistance (OFA) requirements of 49 U.S.C. 10904. The merits of the petition will be addressed in a separate decision. 
                    </P>
                </FTNT>
                <P>BNSF has certified that: (1) No local traffic has moved over the line for at least 2 years; (2) any overhead traffic on the line can be rerouted over other lines; (3) no formal complaint filed by a user of rail service on the line (or by a state or local government entity acting on behalf of such user) regarding cessation of service over the line either is pending with the Surface Transportation Board or with any U.S. District Court or has been decided in favor of complainant within the 2-year period; and (4) the requirements at 49 CFR 1105.7 (environmental reports), 49 CFR 1105.8 (historic reports), 49 CFR 1105.11 (transmittal letter), 49 CFR 1105.12 (newspaper publication), and 49 CFR 1152.50(d)(1) (notice to governmental agencies) have been met. </P>
                <P>
                    As a condition to this exemption, any employee adversely affected by the abandonment shall be protected under 
                    <E T="03">Oregon Short Line R. Co.—Abandonment—Goshen,</E>
                     360 I.C.C. 91 (1979). To address whether this condition adequately protects affected employees, a petition for partial revocation under 49 U.S.C. 10502(d) must be filed. 
                </P>
                <P>
                    Provided no formal expression of intent to file an OFA has been received, this exemption will be effective on October 28, 2008, unless stayed pending reconsideration. Petitions to stay that do not involve environmental issues,
                    <SU>3</SU>
                    <FTREF/>
                     formal expressions of intent to file an OFA under 49 CFR 1152.27(c)(2),
                    <SU>4</SU>
                    <FTREF/>
                     and trail use/rail banking requests under 49 CFR 1152.29 must be filed by October 6, 2008. Petitions to reopen or requests for public use conditions under 49 CFR 1152.28 must be filed by October 16, 2008, with the Surface Transportation Board, 395 E Street, SW., Washington, DC 20423-0001. 
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Board will grant a stay if an informed decision on environmental issues (whether raised by a party or by the Board's Section of Environmental Analysis (SEA) in its independent investigation) cannot be made before the exemption's effective date. 
                        <E T="03">See</E>
                          
                        <E T="03">Exemption of Out-of-Service Rail Lines,</E>
                         5 I.C.C.2d 377 (1989). Any request for a stay should be filed as soon as possible so that the Board may take appropriate action before the exemption's effective date. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Effective July 18, 2008, the filing fee for an OFA increased to $1,500. 
                        <E T="03">See Regulations Governing Fees for Services Performed in Connection with Licensing and Related Services—2008 update,</E>
                         STB Ex Parte No. 542 (Sub-No. 15) (STB served June 18, 2008). 
                    </P>
                </FTNT>
                <P>A copy of any petition filed with the Board should be sent to BNSF's representative: Kristy D. Clark, BNSF Railway Company, 2500 Lou Menk Drive, AOB-3, Fort Worth, TX 76131. </P>
                <P>
                    If the verified notice contains false or misleading information, the exemption is void 
                    <E T="03">ab initio.</E>
                </P>
                <P>BNSF has filed both an environmental report and a historic report that address the effects, if any, of the abandonment on the environment and historic resources. SEA will issue an environmental assessment (EA) by October 3, 2008. Interested persons may obtain a copy of the EA by writing to SEA (Room 1100, Surface Transportation Board, Washington, DC 20423-0001) or by calling SEA, at (202) 245-0305. [Assistance for the hearing impaired is available through the Federal Information Relay Service (FIRS) at 1-800-877-8339.] Comments on environmental and historic preservation matters must be filed within 15 days after the EA becomes available to the public. </P>
                <P>Environmental, historic preservation, public use, or trail use/rail banking conditions will be imposed, where appropriate, in a subsequent decision. </P>
                <P>Pursuant to the provisions of 49 CFR 1152.29(e)(2), BNSF shall file a notice of consummation with the Board to signify that it has exercised the authority granted and fully abandoned the line. If consummation has not been effected by BNSF's filing of a notice of consummation by September 26, 2009, and there are no legal or regulatory barriers to consummation, the authority to abandon will automatically expire. </P>
                <P>
                    Board decisions and notices are available on our Web site at 
                    <E T="03">http://www.stb.dot.gov.</E>
                </P>
                <SIG>
                    <DATED>Decided: September 22, 2008. </DATED>
                    <P>By the Board, David M. Konschnik, Director, Office of Proceedings. </P>
                    <NAME>Anne K. Quinlan, </NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22677 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4915-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Surface Transportation Board </SUBAGY>
                <DEPDOC>[STB Finance Docket No. 35176] </DEPDOC>
                <SUBJECT>Georgia Southwestern Railroad, Inc.—Acquisition Exemption—CSX Transportation, Inc. </SUBJECT>
                <P>
                    Georgia Southwestern Railroad, Inc. (GSWR), a Class III rail carrier, has filed a verified notice of exemption under 49 CFR 1150.41 to acquire by purchase from CSX Transportation, Inc. (CSXT), 
                    <PRTPAGE P="55900"/>
                    approximately 1.6 miles of rail line, extending from milepost SLC-96.66 to the end of the line, near Lynn, GA, and consisting of Tracks SV 4 (6,875 feet), SV 12 (1,360 feet), and SV 14 (400 feet), in Decatur County, GA.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         According to GSWR, since 1989, GSWR and its predecessor, South Carolina Central Railroad Company, have maintained and operated the line. 
                        <E T="03">See South Carolina Central Railroad Company, Inc.—Purchase and Lease—CSX Transportation, Inc., Lines in Georgia and Alabama</E>
                        , Finance Docket No. 31360 (ICC served May 4, 1989). GSWR also states that it currently leases and operates the line, and, after the acquisition, will continue to be the operator of the line. 
                    </P>
                </FTNT>
                <P>GSWR certifies that its projected annual revenues as a result of this transaction will not result in GSWR's becoming a Class II or Class I rail carrier. Because GSWR's projected annual revenues will exceed $5 million, GSWR is required, at least 60 days before an exemption is to become effective, to send notice of the transaction to the national and local offices of the labor unions with employees on the affected lines and post a copy of the notice at the workplace of the employees on the affected lines and certify to the Board that it has done so. 49 CFR 1150.42(e). </P>
                <P>On September 2, 2008, GSWR certified to the Board that, on August 29, 2008, it posted a notice at the workplace of the employees on the affected lines, as required under 49 CFR 1150.42(e). GSWR does not specifically address whether it sent the required notice of the transaction to the national and local offices of the labor unions with employees on the affected lines, as also required under section 1150.42(e), but states that no employees working on the affected lines are members of a labor union. However, concurrently with its notice of exemption, GSWR filed a petition for waiver of the 60-day advance labor notice requirement under section 1150.42(e), asserting that no CSXT employee will be affected by the sale because no CSXT employee has performed operations or maintenance on the line in nearly 20 years and that no GSWR employee will be affected because GSWR will continue to provide the same service and perform the same maintenance as it has for nearly 20 years. GSWR's waiver request will be handled in a subsequent decision. </P>
                <P>GSWR states that it intends to consummate the transaction on or shortly after the effective date of this exemption. The Board will establish in the decision on the waiver request the earliest this transaction may be consummated. </P>
                <P>
                    If the notice contains false or misleading information, the exemption is void 
                    <E T="03">ab initio</E>
                    . Petitions to revoke the exemption under 49 U.S.C. 10502(d) may be filed at any time. The filing of a petition to revoke will not automatically stay the transaction. Petitions for stay must be filed no later than 7 days before the exemption becomes effective. 
                </P>
                <P>Pursuant to the Consolidated Appropriations Act, 2008, Public Law No. 110-161 § 193, 121 Stat. 1844 (2007), nothing in this decision authorizes the following activities at any solid waste rail transfer facility: collecting, storing, or transferring solid waste outside of its original shipping container; or separating or processing solid waste (including baling, crushing, compacting, and shredding). The term “solid waste” is defined in section 1004 of the Solid Waste Disposal Act, 42 U.S.C. 6903. </P>
                <P>An original and 10 copies of all pleadings, referring to STB Finance Docket No. 35176, must be filed with the Surface Transportation Board, 395 E Street, SW., Washington, DC 20423-0001. In addition, one copy of each pleading must be served on Karl Morell, Of Counsel, Ball Janik LLP, Suite 225, 1455 F Street, NW., Washington, DC 20005. </P>
                <P>
                    Board decisions and notices are available on our Web site at “
                    <E T="03">http://www.stb.dot.gov</E>
                    .” 
                </P>
                <SIG>
                    <DATED>Decided: September 19, 2008. </DATED>
                    <P>By the Board, David M. Konschnik, Director, Office of Proceedings. </P>
                    <NAME>Anne K. Quinlan, </NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22588 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4915-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <DATE>September 19, 2008. </DATE>
                <P>The Department of Treasury will submit the following public information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13 on or after the date of publication of this notice. Copies of the submission(s) may be obtained by calling the Treasury Bureau Clearance Officer listed. Comments regarding this information collection should be addressed to the OMB reviewer listed and to the Treasury Department Clearance Officer, Department of the Treasury, Room 11000, 1750 Pennsylvania Avenue, NW., Washington, DC 20220. </P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before October 27, 2008 to be assured of consideration. </P>
                </DATES>
                <HD SOURCE="HD1">Alcohol and Tobacco Tax and Trade Bureau (TTB) </HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1513-0119. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Certification of Proper Cellar Treatment for Imported Natural Wine. 
                </P>
                <P>
                    <E T="03"> Description:</E>
                     TTB is requiring importers of natural wine to certify compliance with proper cellar treatment standards. This certification is necessary to comply with statutory requirements. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Businesses or other for-profit institutions. 
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     6,600 hours. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1513-0092. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Marks on Wine Containers, TTB REC 5120/3. 
                </P>
                <P>
                    <E T="03"> Description:</E>
                     TTB requires that wine on wine premises be identified by statements of information on labels or contained in marks. TTB uses this information to validate the receipts of excise tax revenue by the Federal government. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Businesses or other for-profit institutions. 
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     1 hour. 
                </P>
                <P>
                    <E T="03">Clearance Officer:</E>
                     Frank Foote (202) 927-9347, Alcohol and Tobacco Tax and Trade Bureau, Room 200 East, 1310 G Street, NW., Washington, DC 20005. 
                </P>
                <P>
                    <E T="03">OMB Reviewer:</E>
                     Alexander T. Hunt (202) 395-7316, Office of Management and Budget, Room 10235, New Executive Office Building, Washington, DC 20503. 
                </P>
                <SIG>
                    <NAME>Robert Dahl, </NAME>
                    <TITLE>Treasury PRA Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E8-22647 Filed 9-25-08; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4810-31-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>73</VOL>
    <NO>188</NO>
    <DATE>Friday, September 26, 2008</DATE>
    <UNITNAME>Notice</UNITNAME>
    <NEWPART>
        <NEWBOOKT>
            <PRTPAGE P="55901"/>
            <PARTNO>Part II</PARTNO>
            <BOOK>Book 2 of 2 Books</BOOK>
            <PGS>55901-56446</PGS>
            <AGENCY TYPE="P">Department of Health and Human Services</AGENCY>
            <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
            <TITLE>Medicare and Medicaid Programs; Quarterly Listing of Program Issuances-April Through June 2008; Notice</TITLE>
        </NEWBOOKT>
        <NOTICES>
            <NOTICE>
                <PREAMB>
                    <PRTPAGE P="55902"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                    <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                    <DEPDOC>[CMS-9047-N] </DEPDOC>
                    <SUBJECT>Medicare and Medicaid Programs; Quarterly Listing of Program Issuances—April Through June 2008 </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            This notice lists CMS manual instructions, substantive and interpretive regulations, and other 
                            <E T="04">Federal Register</E>
                             notices that were published from April 2008 through June 2008, relating to the Medicare and Medicaid programs. This notice provides information on national coverage determinations (NCDs) affecting specific medical and health care services under Medicare. Additionally, this notice identifies certain devices with investigational device exemption (IDE) numbers approved by the Food and Drug Administration (FDA) that potentially may be covered under Medicare. This notice also includes listings of all approval numbers from the Office of Management and Budget for collections of information in CMS regulations and a list of Medicare-approved carotid stent facilities. Included in this notice is a list of the American College of Cardiology's National Cardiovascular Data registry sites, active CMS coverage-related guidance documents, and special one-time notices regarding national coverage provisions. Also included in this notice is a list of National Oncologic Positron Emissions Tomography Registry sites, a list of Medicare-approved ventricular assist device (destination therapy) facilities, a list of Medicare-approved lung volume reduction surgery facilities, a list of Medicare-approved clinical trials for fluorodeoxyglucose positron emissions tomogrogphy for dementia, and a list of Medicare-approved bariatric surgery facilities. 
                        </P>
                        <P>
                            Section 1871(c) of the Social Security Act requires that we publish a list of Medicare issuances in the 
                            <E T="04">Federal Register</E>
                             at least every 3 months. Although we are not mandated to do so by statute, for the sake of completeness of the listing, and to foster more open and transparent collaboration efforts, we are also including all Medicaid issuances and Medicare and Medicaid substantive and interpretive regulations (proposed and final) published during this 3-month time frame. 
                        </P>
                    </SUM>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>It is possible that an interested party may need specific information and not be able to determine from the listed information whether the issuance or regulation would fulfill that need. Consequently, we are providing contact persons to answer general questions concerning these items. Copies are not available through the contact persons. (See Section III of this notice for how to obtain listed material.) </P>
                        <P>Questions concerning CMS manual instructions in Addendum III may be addressed to Ismael Torres, Office of Strategic Operations and Regulatory Affairs, Centers for Medicare &amp; Medicaid Services, C4-26-05, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-1864. </P>
                        <P>
                            Questions concerning regulation documents published in the 
                            <E T="04">Federal Register</E>
                             in Addendum IV may be addressed to Gwendolyn Johnson, Office of Strategic Operations and Regulatory Affairs, Centers for Medicare &amp; Medicaid Services, C4-14-03, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-6954. 
                        </P>
                        <P>Questions concerning Medicare NCDs in Addendum V may be addressed to Patricia Brocato-Simons, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-0261. </P>
                        <P>Questions concerning FDA-approved Category B IDE numbers listed in Addendum VI may be addressed to John Manlove, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-13-04, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-6877. </P>
                        <P>Questions concerning approval numbers for collections of information in Addendum VII may be addressed to Melissa Musotto, Office of Strategic Operations and Regulatory Affairs, Regulations Development and Issuances Group, Centers for Medicare &amp; Medicaid Services, C5-14-03, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-6962. </P>
                        <P>Questions concerning Medicare-approved carotid stent facilities in Addendum VIII may be addressed to Sarah J. McClain, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-2994. </P>
                        <P>Questions concerning Medicare's recognition of the American College of Cardiology-National Cardiovascular Data Registry sites in Addendum IX may be addressed to JoAnna Baldwin, MS, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-7205. </P>
                        <P>Questions concerning Medicare's active coverage-related guidance documents in Addendum X may be addressed to Beverly Lofton, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-7136. </P>
                        <P>Questions concerning one-time notices regarding national coverage provisions in Addendum XI may be addressed to Beverly Lofton, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-7136. </P>
                        <P>Questions concerning National Oncologic Positron Emission Tomography Registry sites in Addendum XII may be addressed to Stuart Caplan, RN, MAS, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-8564. </P>
                        <P>Questions concerning Medicare-approved ventricular assist device (destination therapy) facilities in Addendum XIII may be addressed to JoAnna Baldwin, MS, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-7205. </P>
                        <P>Questions concerning Medicare-approved lung volume reduction surgery facilities listed in Addendum XIV may be addressed to JoAnna Baldwin, MS, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-7205. </P>
                        <P>Questions concerning Medicare-approved bariatric surgery facilities listed in Addendum XV may be addressed to Kate Tillman, RN, MA, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-9252. </P>
                        <P>
                            Questions concerning fluorodeoxyglucose positron emission 
                            <PRTPAGE P="55903"/>
                            tomography for dementia trials listed in Addendum XVI may be addressed to Stuart Caplan, RN, MAS, Office of Clinical Standards and Quality, Centers for Medicare &amp; Medicaid Services, C1-09-06, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-8564. 
                        </P>
                        <P>Questions concerning all other information may be addressed to Gwendolyn Johnson, Office of Strategic Operations and Regulatory Affairs, Regulations Development Group, Centers for Medicare &amp; Medicaid Services, C5-14-03, 7500 Security Boulevard, Baltimore, MD 21244-1850, or you can call (410) 786-6954. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">I. Program Issuances </HD>
                    <P>The Centers for Medicare &amp; Medicaid Services (CMS) is responsible for administering the Medicare and Medicaid programs. These programs pay for health care and related services for 39 million Medicare beneficiaries and 35 million Medicaid recipients. Administration of the two programs involves (1) furnishing information to Medicare beneficiaries and Medicaid recipients, health care providers, and the public and (2) maintaining effective communications with regional offices, State governments, State Medicaid agencies, State survey agencies, various providers of health care, all Medicare contractors that process claims and pay bills, and others. To implement the various statutes on which the programs are based, we issue regulations under the authority granted to the Secretary of the Department of Health and Human Services under sections 1102, 1871, 1902, and related provisions of the Social Security Act (the Act). We also issue various manuals, memoranda, and statements necessary to administer the programs efficiently. </P>
                    <P>
                        Section 1871(c)(1) of the Act requires that we publish a list of all Medicare manual instructions, interpretive rules, statements of policy, and guidelines of general applicability not issued as regulations at least every 3 months in the 
                        <E T="04">Federal Register</E>
                        . We published our first notice June 9, 1988 (53 FR 21730). Although we are not mandated to do so by statute, for the sake of completeness of the listing of operational and policy statements, and to foster more open and transparent collaboration, we are continuing our practice of including Medicare substantive and interpretive regulations (proposed and final) published during the respective 3-month time frame. 
                    </P>
                    <HD SOURCE="HD1">II. How To Use the Addenda </HD>
                    <P>This notice is organized so that a reader may review the subjects of manual issuances, memoranda, substantive and interpretive regulations, NCDs, and FDA-approved IDEs published during the subject quarter to determine whether any are of particular interest. We expect this notice to be used in concert with previously published notices. Those unfamiliar with a description of our Medicare manuals may wish to review Table I of our first three notices (53 FR 21730, 53 FR 36891, and 53 FR 50577) published in 1988, and the notice published March 31, 1993 (58 FR 16837). Those desiring information on the Medicare NCD Manual (NCDM, formerly the Medicare Coverage Issues Manual (CIM)) may wish to review the August 21, 1989, publication (54 FR 34555). Those interested in the revised process used in making NCDs under the Medicare program may review the September 26, 2003, publication (68 FR 55634). </P>
                    <P>To aid the reader, we have organized and divided this current listing into 11 addenda: </P>
                    <P>• Addendum I lists the publication dates of the most recent quarterly listings of program issuances. </P>
                    <P>
                        • Addendum II identifies previous 
                        <E T="04">Federal Register</E>
                         documents that contain a description of all previously published CMS Medicare and Medicaid manuals and memoranda. 
                    </P>
                    <P>• Addendum III lists a unique CMS transmittal number for each instruction in our manuals or Program Memoranda and its subject matter. A transmittal may consist of a single or multiple instruction(s). Often, it is necessary to use information in a transmittal in conjunction with information currently in the manuals. </P>
                    <P>
                        • Addendum IV lists all substantive and interpretive Medicare and Medicaid regulations and general notices published in the 
                        <E T="04">Federal Register</E>
                         during the quarter covered by this notice. For each item, we list the—
                    </P>
                    <P>○ Date published; </P>
                    <P>
                        ○ 
                        <E T="04">Federal Register</E>
                         citation; 
                    </P>
                    <P>○ Parts of the Code of Federal Regulations (CFR) that have changed (if applicable); </P>
                    <P>○ Agency file code number; and </P>
                    <P>○ Title of the regulation. </P>
                    <P>• Addendum V includes completed NCDs, or reconsiderations of completed NCDs, from the quarter covered by this notice. Completed decisions are identified by the section of the NCDM in which the decision appears, the title, the date the publication was issued, and the effective date of the decision. </P>
                    <P>• Addendum VI includes listings of the FDA-approved IDE categorizations, using the IDE numbers the FDA assigns. The listings are organized according to the categories to which the device numbers are assigned (that is, Category A or Category B), and identified by the IDE number. </P>
                    <P>• Addendum VII includes listings of all approval numbers from the Office of Management and Budget (OMB) for collections of information in CMS regulations in title 42; title 45, subchapter C; and title 20 of the CFR. </P>
                    <P>• Addendum VIII includes listings of Medicare-approved carotid stent facilities. All facilities listed meet CMS standards for performing carotid artery stenting for high risk patients. </P>
                    <P>• Addendum IX includes a list of the American College of Cardiology's National Cardiovascular Data registry sites. We cover implantable cardioverter defibrillators (ICDs) for certain indications, as long as information about the procedures is reported to a central registry. </P>
                    <P>• Addendum X includes a list of active CMS guidance documents. As required by section 731 of the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 (MMA) (Pub. L. 108-173, enacted on December 8, 2003), we will begin listing the current versions of our guidance documents in each quarterly listings notice. </P>
                    <P>• Addendum XI includes a list of special one-time notices regarding national coverage provisions. We are publishing a list of issues that require public notification, such as a particular clinical trial or research study that qualifies for Medicare coverage. </P>
                    <P>• Addendum XII includes a listing of National Oncologic Positron Emission Tomography Registry (NOPR) sites. We cover positron emission tomography (PET) scans for particular oncologic indications when they are performed in a facility that participates in the NOPR. </P>
                    <P>• Addendum XIII includes a listing of Medicare-approved facitilites that receive coverage for ventricular assist devices used as destination therapy. All facilities were required to meet our standards in order to receive coverage for ventricular assist devices implanted as destination therapy. </P>
                    <P>• Addendum XIV includes a listing of Medicare-approved facilities that are eligible to receive coverage for lung volume reduction surgery. Until May 17, 2007, facilities that participated in the National Emphysema Treatment Trial are also eligible to receive coverage. </P>
                    <P>
                        • Addendum XV includes a listing of Medicare-approved facilities that meet minimum standards for facilities modeled in part on professional society statements on competency. All facilities 
                        <PRTPAGE P="55904"/>
                        must meet our standards in order to receive coverage for bariatric surgery procedures. 
                    </P>
                    <P>• Addendum XVI includes a listing of Medicare-approved clinical trials for fluorodeoxyglucose positron emission tomography (FDG-PET) for dementia and neurodegenerative diseases. </P>
                    <HD SOURCE="HD1">III. How To Obtain Listed Material </HD>
                    <HD SOURCE="HD2">A. Manuals </HD>
                    <P>Those wishing to subscribe to program manuals should contact either the Government Printing Office (GPO) or the National Technical Information Service (NTIS) at the following addresses: </P>
                    <FP SOURCE="FP-1">
                        Superintendent of Documents, Government Printing Office, 
                        <E T="03">ATTN:</E>
                         New Orders, P.O. Box 371954, Pittsburgh, PA 15250-7954, Telephone (202) 512-1800, Fax number (202) 512-2250 (for credit card orders); or 
                    </FP>
                    <FP SOURCE="FP-1">National Technical Information Service, Department of Commerce, 5825 Port Royal Road, Springfield, VA 22161, Telephone (703) 487-4630. </FP>
                    <P>
                        In addition, individual manual transmittals and Program Memoranda listed in this notice can be purchased from NTIS. Interested parties should identify the transmittal(s) they want. GPO or NTIS can give complete details on how to obtain the publications they sell. Additionally, most manuals are available at the following Internet address: 
                        <E T="03">http://cms.hhs.gov/manuals/default.asp</E>
                        . 
                    </P>
                    <HD SOURCE="HD2">B. Regulations and Notices </HD>
                    <P>
                        Regulations and notices are published in the daily 
                        <E T="04">Federal Register</E>
                        . Interested individuals may purchase individual copies or subscribe to the 
                        <E T="04">Federal Register</E>
                         by contacting the GPO at the address given above. When ordering individual copies, it is necessary to cite either the date of publication or the volume number and page number. 
                    </P>
                    <P>
                        The 
                        <E T="04">Federal Register</E>
                         is also available on 24x microfiche and as an online database through 
                        <E T="03">GPO Access</E>
                        . The online database is updated by 6 a.m. each day the 
                        <E T="04">Federal Register</E>
                         is published. The database includes both text and graphics from Volume 59, Number 1 (January 2, 1994) forward. Free public access is available on a Wide Area Information Server (WAIS) through the Internet and via asynchronous dial-in. Internet users can access the database by using the World Wide Web; the Superintendent of Documents home page address is 
                        <E T="03">http://www.gpoaccess.gov/fr/index.html</E>
                        , by using local WAIS client software, or by telnet to 
                        <E T="03">swais.gpoaccess.gov</E>
                        , then log in as guest (no password required). Dial-in users should use communications software and modem to call (202) 512-1661; type swais, then log in as guest (no password required). 
                    </P>
                    <HD SOURCE="HD2">C. Rulings </HD>
                    <P>
                        We publish rulings on an infrequent basis. CMS Rulings are decisions of the Administrator that serve as precedent final opinions and orders and statements of policy and interpretation. They provide clarification and interpretation of complex or ambiguous provisions of the law or regulations relating to Medicare, Medicaid, Utilization and Quality Control Peer Review, private health insurance, and related matters. Interested individuals can obtain copies from the nearest CMS Regional Office or review them at the nearest regional depository library. We have, on occasion, published rulings in the 
                        <E T="04">Federal Register</E>
                        . Rulings, beginning with those released in 1995, are available online, through the CMS Home Page. The Internet address is 
                        <E T="03">http://cms.hhs.gov/rulings</E>
                        . 
                    </P>
                    <HD SOURCE="HD2">D. CMS' Compact Disk-Read Only Memory (CD-ROM) </HD>
                    <P>Our laws, regulations, and manuals are also available on CD-ROM and may be purchased from GPO or NTIS on a subscription or single copy basis. The Superintendent of Documents list ID is HCLRM, and the stock number is 717-139-00000-3. The following material is on the CD-ROM disk: </P>
                    <P>• Titles XI, XVIII, and XIX of the Act. </P>
                    <P>• CMS-related regulations. </P>
                    <P>• CMS manuals and monthly revisions. </P>
                    <P>• CMS program memoranda. </P>
                    <P>
                        The titles of the Compilation of the Social Security Laws are current as of January 1, 2005. (Updated titles of the Social Security Laws are available on the Internet at 
                        <E T="03">http://www.ssa.gov/OP_Home/ssact/comp-toc.htm.</E>
                        ) The remaining portions of CD-ROM are updated on a monthly basis. 
                    </P>
                    <P>Because of complaints about the unreadability of the Appendices (Interpretive Guidelines) in the State Operations Manual (SOM), as of March 1995, we deleted these appendices from CD-ROM. We intend to re-visit this issue in the near future and, with the aid of newer technology, we may again be able to include the appendices on CD-ROM. </P>
                    <P>Any cost report forms incorporated in the manuals are included on the CD-ROM disk as LOTUS files. LOTUS software is needed to view the reports once the files have been copied to a personal computer disk. </P>
                    <HD SOURCE="HD1">IV. How To Review Listed Material </HD>
                    <P>Transmittals or Program Memoranda can be reviewed at a local Federal Depository Library (FDL). Under the FDL program, government publications are sent to approximately 1,400 designated libraries throughout the United States. Some FDLs may have arrangements to transfer material to a local library not designated as an FDL. Contact any library to locate the nearest FDL. </P>
                    <P>In addition, individuals may contact regional depository libraries that receive and retain at least one copy of most Federal Government publications, either in printed or microfilm form, for use by the general public. These libraries provide reference services and interlibrary loans; however, they are not sales outlets. Individuals may obtain information about the location of the nearest regional depository library from any library. </P>
                    <P>For each CMS publication listed in Addendum III, CMS publication and transmittal numbers are shown. To help FDLs locate the materials, use the CMS publication and transmittal numbers. For example, to find the Medicare Benefit Policy publication titled “Erythropoiesis Stimulating Agents in Cancer and Related Neoplastic Conditions,” use CMS-Pub. 100-03, Transmittal No. 80. </P>
                    <EXTRACT>
                        <FP>(Catalog of Federal Domestic Assistance Program No. 93.773, Medicare—Hospital Insurance, Program No. 93.774, Medicare—Supplementary Medical Insurance Program, and Program No. 93.714, Medical Assistance Program)</FP>
                    </EXTRACT>
                    <SIG>
                        <DATED>Dated: September 8, 2008. </DATED>
                        <NAME>Jacquelyn Y. White, </NAME>
                        <TITLE>Director, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                    </SIG>
                    <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55905"/>
                        <GID>EN26SE08.000</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55906"/>
                        <GID>EN26SE08.001</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55907"/>
                        <GID>EN26SE08.002</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55908"/>
                        <GID>EN26SE08.003</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55909"/>
                        <GID>EN26SE08.004</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55910"/>
                        <GID>EN26SE08.005</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55911"/>
                        <GID>EN26SE08.006</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55912"/>
                        <GID>EN26SE08.007</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55913"/>
                        <GID>EN26SE08.008</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55914"/>
                        <GID>EN26SE08.009</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55915"/>
                        <GID>EN26SE08.010</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55916"/>
                        <GID>EN26SE08.011</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55917"/>
                        <GID>EN26SE08.012</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55918"/>
                        <GID>EN26SE08.013</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55919"/>
                        <GID>EN26SE08.014</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55920"/>
                        <GID>EN26SE08.015</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55921"/>
                        <GID>EN26SE08.016</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55922"/>
                        <GID>EN26SE08.017</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55923"/>
                        <GID>EN26SE08.018</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55924"/>
                        <GID>EN26SE08.019</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55925"/>
                        <GID>EN26SE08.020</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55926"/>
                        <GID>EN26SE08.021</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55927"/>
                        <GID>EN26SE08.022</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55928"/>
                        <GID>EN26SE08.023</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55929"/>
                        <GID>EN26SE08.024</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55930"/>
                        <GID>EN26SE08.025</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55931"/>
                        <GID>EN26SE08.026</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55932"/>
                        <GID>EN26SE08.027</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55933"/>
                        <GID>EN26SE08.028</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55934"/>
                        <GID>EN26SE08.029</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55935"/>
                        <GID>EN26SE08.030</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55936"/>
                        <GID>EN26SE08.031</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55937"/>
                        <GID>EN26SE08.032</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55938"/>
                        <GID>EN26SE08.033</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55939"/>
                        <GID>EN26SE08.034</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55940"/>
                        <GID>EN26SE08.035</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55941"/>
                        <GID>EN26SE08.036</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55942"/>
                        <GID>EN26SE08.037</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55943"/>
                        <GID>EN26SE08.038</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55944"/>
                        <GID>EN26SE08.039</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55945"/>
                        <GID>EN26SE08.040</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55946"/>
                        <GID>EN26SE08.041</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55947"/>
                        <GID>EN26SE08.042</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55948"/>
                        <GID>EN26SE08.043</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55949"/>
                        <GID>EN26SE08.044</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55950"/>
                        <GID>EN26SE08.045</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55951"/>
                        <GID>EN26SE08.046</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55952"/>
                        <GID>EN26SE08.047</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55953"/>
                        <GID>EN26SE08.048</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55954"/>
                        <GID>EN26SE08.049</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55955"/>
                        <GID>EN26SE08.050</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55956"/>
                        <GID>EN26SE08.051</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55957"/>
                        <GID>EN26SE08.052</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55958"/>
                        <GID>EN26SE08.053</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55959"/>
                        <GID>EN26SE08.054</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55960"/>
                        <GID>EN26SE08.055</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55961"/>
                        <GID>EN26SE08.056</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55962"/>
                        <GID>EN26SE08.057</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55963"/>
                        <GID>EN26SE08.058</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55964"/>
                        <GID>EN26SE08.059</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55965"/>
                        <GID>EN26SE08.060</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55966"/>
                        <GID>EN26SE08.061</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55967"/>
                        <GID>EN26SE08.062</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55968"/>
                        <GID>EN26SE08.063</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55969"/>
                        <GID>EN26SE08.064</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55970"/>
                        <GID>EN26SE08.065</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55971"/>
                        <GID>EN26SE08.066</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55972"/>
                        <GID>EN26SE08.067</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55973"/>
                        <GID>EN26SE08.068</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55974"/>
                        <GID>EN26SE08.069</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55975"/>
                        <GID>EN26SE08.070</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55976"/>
                        <GID>EN26SE08.071</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55977"/>
                        <GID>EN26SE08.072</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55978"/>
                        <GID>EN26SE08.073</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55979"/>
                        <GID>EN26SE08.074</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55980"/>
                        <GID>EN26SE08.075</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55981"/>
                        <GID>EN26SE08.076</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55982"/>
                        <GID>EN26SE08.077</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55983"/>
                        <GID>EN26SE08.078</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55984"/>
                        <GID>EN26SE08.079</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55985"/>
                        <GID>EN26SE08.080</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55986"/>
                        <GID>EN26SE08.081</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55987"/>
                        <GID>EN26SE08.082</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55988"/>
                        <GID>EN26SE08.083</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55989"/>
                        <GID>EN26SE08.084</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55990"/>
                        <GID>EN26SE08.085</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55991"/>
                        <GID>EN26SE08.086</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55992"/>
                        <GID>EN26SE08.087</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55993"/>
                        <GID>EN26SE08.088</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55994"/>
                        <GID>EN26SE08.089</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55995"/>
                        <GID>EN26SE08.090</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55996"/>
                        <GID>EN26SE08.091</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55997"/>
                        <GID>EN26SE08.092</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55998"/>
                        <GID>EN26SE08.093</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="55999"/>
                        <GID>EN26SE08.094</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56000"/>
                        <GID>EN26SE08.095</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56001"/>
                        <GID>EN26SE08.096</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56002"/>
                        <GID>EN26SE08.097</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56003"/>
                        <GID>EN26SE08.098</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56004"/>
                        <GID>EN26SE08.099</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56005"/>
                        <GID>EN26SE08.100</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56006"/>
                        <GID>EN26SE08.101</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56007"/>
                        <GID>EN26SE08.102</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56008"/>
                        <GID>EN26SE08.103</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56009"/>
                        <GID>EN26SE08.104</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56010"/>
                        <GID>EN26SE08.105</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56011"/>
                        <GID>EN26SE08.106</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56012"/>
                        <GID>EN26SE08.107</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56013"/>
                        <GID>EN26SE08.108</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56014"/>
                        <GID>EN26SE08.109</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56015"/>
                        <GID>EN26SE08.110</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56016"/>
                        <GID>EN26SE08.111</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56017"/>
                        <GID>EN26SE08.112</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56018"/>
                        <GID>EN26SE08.113</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56019"/>
                        <GID>EN26SE08.114</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56020"/>
                        <GID>EN26SE08.115</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56021"/>
                        <GID>EN26SE08.116</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56022"/>
                        <GID>EN26SE08.117</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56023"/>
                        <GID>EN26SE08.118</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56024"/>
                        <GID>EN26SE08.119</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56025"/>
                        <GID>EN26SE08.120</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56026"/>
                        <GID>EN26SE08.121</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56027"/>
                        <GID>EN26SE08.122</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56028"/>
                        <GID>EN26SE08.123</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56029"/>
                        <GID>EN26SE08.124</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56030"/>
                        <GID>EN26SE08.125</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56031"/>
                        <GID>EN26SE08.126</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56032"/>
                        <GID>EN26SE08.127</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56033"/>
                        <GID>EN26SE08.128</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56034"/>
                        <GID>EN26SE08.129</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56035"/>
                        <GID>EN26SE08.130</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56036"/>
                        <GID>EN26SE08.131</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56037"/>
                        <GID>EN26SE08.132</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56038"/>
                        <GID>EN26SE08.133</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56039"/>
                        <GID>EN26SE08.134</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56040"/>
                        <GID>EN26SE08.135</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56041"/>
                        <GID>EN26SE08.136</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56042"/>
                        <GID>EN26SE08.137</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56043"/>
                        <GID>EN26SE08.138</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56044"/>
                        <GID>EN26SE08.139</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56045"/>
                        <GID>EN26SE08.140</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56046"/>
                        <GID>EN26SE08.141</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56047"/>
                        <GID>EN26SE08.142</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56048"/>
                        <GID>EN26SE08.143</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56049"/>
                        <GID>EN26SE08.144</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56050"/>
                        <GID>EN26SE08.145</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56051"/>
                        <GID>EN26SE08.146</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56052"/>
                        <GID>EN26SE08.147</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56053"/>
                        <GID>EN26SE08.148</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56054"/>
                        <GID>EN26SE08.149</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56055"/>
                        <GID>EN26SE08.150</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56056"/>
                        <GID>EN26SE08.151</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56057"/>
                        <GID>EN26SE08.152</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56058"/>
                        <GID>EN26SE08.153</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56059"/>
                        <GID>EN26SE08.154</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56060"/>
                        <GID>EN26SE08.155</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56061"/>
                        <GID>EN26SE08.156</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56062"/>
                        <GID>EN26SE08.157</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56063"/>
                        <GID>EN26SE08.158</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56064"/>
                        <GID>EN26SE08.159</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56065"/>
                        <GID>EN26SE08.160</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56066"/>
                        <GID>EN26SE08.161</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56067"/>
                        <GID>EN26SE08.162</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56068"/>
                        <GID>EN26SE08.163</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56069"/>
                        <GID>EN26SE08.164</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56070"/>
                        <GID>EN26SE08.165</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56071"/>
                        <GID>EN26SE08.166</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56072"/>
                        <GID>EN26SE08.167</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56073"/>
                        <GID>EN26SE08.168</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56074"/>
                        <GID>EN26SE08.169</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56075"/>
                        <GID>EN26SE08.170</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56076"/>
                        <GID>EN26SE08.171</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56077"/>
                        <GID>EN26SE08.172</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56078"/>
                        <GID>EN26SE08.173</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56079"/>
                        <GID>EN26SE08.174</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56080"/>
                        <GID>EN26SE08.175</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="474">
                        <PRTPAGE P="56081"/>
                        <GID>EN26SE08.177</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="464">
                        <PRTPAGE P="56082"/>
                        <GID>EN26SE08.178</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="505">
                        <PRTPAGE P="56083"/>
                        <GID>EN26SE08.179</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56084"/>
                        <GID>EN26SE08.180</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56085"/>
                        <GID>EN26SE08.181</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56086"/>
                        <GID>EN26SE08.182</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56087"/>
                        <GID>EN26SE08.183</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56088"/>
                        <GID>EN26SE08.184</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56089"/>
                        <GID>EN26SE08.185</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56090"/>
                        <GID>EN26SE08.186</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56091"/>
                        <GID>EN26SE08.187</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56092"/>
                        <GID>EN26SE08.188</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56093"/>
                        <GID>EN26SE08.189</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56094"/>
                        <GID>EN26SE08.190</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56095"/>
                        <GID>EN26SE08.191</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56096"/>
                        <GID>EN26SE08.192</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56097"/>
                        <GID>EN26SE08.193</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56098"/>
                        <GID>EN26SE08.194</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56099"/>
                        <GID>EN26SE08.195</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56100"/>
                        <GID>EN26SE08.196</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56101"/>
                        <GID>EN26SE08.197</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56102"/>
                        <GID>EN26SE08.198</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56103"/>
                        <GID>EN26SE08.199</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56104"/>
                        <GID>EN26SE08.200</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56105"/>
                        <GID>EN26SE08.201</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56106"/>
                        <GID>EN26SE08.202</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56107"/>
                        <GID>EN26SE08.203</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56108"/>
                        <GID>EN26SE08.204</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56109"/>
                        <GID>EN26SE08.205</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56110"/>
                        <GID>EN26SE08.206</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56111"/>
                        <GID>EN26SE08.207</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56112"/>
                        <GID>EN26SE08.208</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56113"/>
                        <GID>EN26SE08.209</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56114"/>
                        <GID>EN26SE08.210</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56115"/>
                        <GID>EN26SE08.211</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56116"/>
                        <GID>EN26SE08.212</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56117"/>
                        <GID>EN26SE08.213</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56118"/>
                        <GID>EN26SE08.214</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56119"/>
                        <GID>EN26SE08.215</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56120"/>
                        <GID>EN26SE08.216</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56121"/>
                        <GID>EN26SE08.217</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56122"/>
                        <GID>EN26SE08.218</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56123"/>
                        <GID>EN26SE08.219</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56124"/>
                        <GID>EN26SE08.220</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56125"/>
                        <GID>EN26SE08.221</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56126"/>
                        <GID>EN26SE08.222</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56127"/>
                        <GID>EN26SE08.223</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56128"/>
                        <GID>EN26SE08.224</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56129"/>
                        <GID>EN26SE08.225</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56130"/>
                        <GID>EN26SE08.226</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56131"/>
                        <GID>EN26SE08.227</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56132"/>
                        <GID>EN26SE08.228</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56133"/>
                        <GID>EN26SE08.229</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56134"/>
                        <GID>EN26SE08.230</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56135"/>
                        <GID>EN26SE08.231</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56136"/>
                        <GID>EN26SE08.232</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56137"/>
                        <GID>EN26SE08.233</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56138"/>
                        <GID>EN26SE08.234</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56139"/>
                        <GID>EN26SE08.235</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56140"/>
                        <GID>EN26SE08.236</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56141"/>
                        <GID>EN26SE08.237</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56142"/>
                        <GID>EN26SE08.238</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56143"/>
                        <GID>EN26SE08.239</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56144"/>
                        <GID>EN26SE08.240</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56145"/>
                        <GID>EN26SE08.241</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56146"/>
                        <GID>EN26SE08.242</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56147"/>
                        <GID>EN26SE08.243</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56148"/>
                        <GID>EN26SE08.244</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56149"/>
                        <GID>EN26SE08.245</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56150"/>
                        <GID>EN26SE08.246</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56151"/>
                        <GID>EN26SE08.247</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56152"/>
                        <GID>EN26SE08.248</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56153"/>
                        <GID>EN26SE08.249</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56154"/>
                        <GID>EN26SE08.250</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56155"/>
                        <GID>EN26SE08.251</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56156"/>
                        <GID>EN26SE08.252</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56157"/>
                        <GID>EN26SE08.253</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56158"/>
                        <GID>EN26SE08.254</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56159"/>
                        <GID>EN26SE08.255</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56160"/>
                        <GID>EN26SE08.256</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56161"/>
                        <GID>EN26SE08.257</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56162"/>
                        <GID>EN26SE08.258</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56163"/>
                        <GID>EN26SE08.259</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56164"/>
                        <GID>EN26SE08.260</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56165"/>
                        <GID>EN26SE08.261</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56166"/>
                        <GID>EN26SE08.262</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56167"/>
                        <GID>EN26SE08.263</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56168"/>
                        <GID>EN26SE08.264</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56169"/>
                        <GID>EN26SE08.265</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56170"/>
                        <GID>EN26SE08.266</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56171"/>
                        <GID>EN26SE08.267</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56172"/>
                        <GID>EN26SE08.268</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56173"/>
                        <GID>EN26SE08.269</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56174"/>
                        <GID>EN26SE08.270</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56175"/>
                        <GID>EN26SE08.271</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56176"/>
                        <GID>EN26SE08.272</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56177"/>
                        <GID>EN26SE08.273</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56178"/>
                        <GID>EN26SE08.274</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56179"/>
                        <GID>EN26SE08.275</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56180"/>
                        <GID>EN26SE08.276</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56181"/>
                        <GID>EN26SE08.277</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56182"/>
                        <GID>EN26SE08.278</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56183"/>
                        <GID>EN26SE08.279</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56184"/>
                        <GID>EN26SE08.280</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56185"/>
                        <GID>EN26SE08.281</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56186"/>
                        <GID>EN26SE08.282</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56187"/>
                        <GID>EN26SE08.283</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56188"/>
                        <GID>EN26SE08.284</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56189"/>
                        <GID>EN26SE08.285</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56190"/>
                        <GID>EN26SE08.286</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56191"/>
                        <GID>EN26SE08.287</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56192"/>
                        <GID>EN26SE08.288</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56193"/>
                        <GID>EN26SE08.289</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56194"/>
                        <GID>EN26SE08.290</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56195"/>
                        <GID>EN26SE08.291</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56196"/>
                        <GID>EN26SE08.292</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56197"/>
                        <GID>EN26SE08.293</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56198"/>
                        <GID>EN26SE08.294</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56199"/>
                        <GID>EN26SE08.295</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56200"/>
                        <GID>EN26SE08.296</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56201"/>
                        <GID>EN26SE08.297</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56202"/>
                        <GID>EN26SE08.298</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56203"/>
                        <GID>EN26SE08.299</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56204"/>
                        <GID>EN26SE08.300</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56205"/>
                        <GID>EN26SE08.301</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56206"/>
                        <GID>EN26SE08.302</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56207"/>
                        <GID>EN26SE08.303</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56208"/>
                        <GID>EN26SE08.304</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56209"/>
                        <GID>EN26SE08.305</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56210"/>
                        <GID>EN26SE08.306</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56211"/>
                        <GID>EN26SE08.307</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56212"/>
                        <GID>EN26SE08.308</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56213"/>
                        <GID>EN26SE08.309</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56214"/>
                        <GID>EN26SE08.310</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56215"/>
                        <GID>EN26SE08.311</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56216"/>
                        <GID>EN26SE08.312</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56217"/>
                        <GID>EN26SE08.313</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56218"/>
                        <GID>EN26SE08.314</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56219"/>
                        <GID>EN26SE08.315</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56220"/>
                        <GID>EN26SE08.316</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56221"/>
                        <GID>EN26SE08.317</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56222"/>
                        <GID>EN26SE08.318</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56223"/>
                        <GID>EN26SE08.319</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56224"/>
                        <GID>EN26SE08.320</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56225"/>
                        <GID>EN26SE08.321</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56226"/>
                        <GID>EN26SE08.322</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56227"/>
                        <GID>EN26SE08.323</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56228"/>
                        <GID>EN26SE08.324</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56229"/>
                        <GID>EN26SE08.325</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56230"/>
                        <GID>EN26SE08.326</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56231"/>
                        <GID>EN26SE08.327</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56232"/>
                        <GID>EN26SE08.328</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56233"/>
                        <GID>EN26SE08.329</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56234"/>
                        <GID>EN26SE08.330</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56235"/>
                        <GID>EN26SE08.331</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56236"/>
                        <GID>EN26SE08.332</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56237"/>
                        <GID>EN26SE08.333</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56238"/>
                        <GID>EN26SE08.334</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56239"/>
                        <GID>EN26SE08.335</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56240"/>
                        <GID>EN26SE08.336</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56241"/>
                        <GID>EN26SE08.337</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56242"/>
                        <GID>EN26SE08.338</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56243"/>
                        <GID>EN26SE08.339</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56244"/>
                        <GID>EN26SE08.340</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56245"/>
                        <GID>EN26SE08.341</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56246"/>
                        <GID>EN26SE08.342</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56247"/>
                        <GID>EN26SE08.343</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56248"/>
                        <GID>EN26SE08.344</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56249"/>
                        <GID>EN26SE08.345</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56250"/>
                        <GID>EN26SE08.346</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56251"/>
                        <GID>EN26SE08.347</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56252"/>
                        <GID>EN26SE08.348</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56253"/>
                        <GID>EN26SE08.349</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56254"/>
                        <GID>EN26SE08.350</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56255"/>
                        <GID>EN26SE08.351</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56256"/>
                        <GID>EN26SE08.352</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56257"/>
                        <GID>EN26SE08.353</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56258"/>
                        <GID>EN26SE08.354</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56259"/>
                        <GID>EN26SE08.355</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56260"/>
                        <GID>EN26SE08.356</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56261"/>
                        <GID>EN26SE08.357</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56262"/>
                        <GID>EN26SE08.358</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56263"/>
                        <GID>EN26SE08.359</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56264"/>
                        <GID>EN26SE08.360</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56265"/>
                        <GID>EN26SE08.361</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56266"/>
                        <GID>EN26SE08.362</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56267"/>
                        <GID>EN26SE08.363</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56268"/>
                        <GID>EN26SE08.364</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56269"/>
                        <GID>EN26SE08.365</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56270"/>
                        <GID>EN26SE08.366</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56271"/>
                        <GID>EN26SE08.367</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56272"/>
                        <GID>EN26SE08.368</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56273"/>
                        <GID>EN26SE08.369</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56274"/>
                        <GID>EN26SE08.370</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56275"/>
                        <GID>EN26SE08.371</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56276"/>
                        <GID>EN26SE08.372</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56277"/>
                        <GID>EN26SE08.373</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56278"/>
                        <GID>EN26SE08.374</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56279"/>
                        <GID>EN26SE08.375</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56280"/>
                        <GID>EN26SE08.376</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56281"/>
                        <GID>EN26SE08.377</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56282"/>
                        <GID>EN26SE08.378</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56283"/>
                        <GID>EN26SE08.379</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56284"/>
                        <GID>EN26SE08.380</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56285"/>
                        <GID>EN26SE08.381</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56286"/>
                        <GID>EN26SE08.382</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56287"/>
                        <GID>EN26SE08.383</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56288"/>
                        <GID>EN26SE08.384</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56289"/>
                        <GID>EN26SE08.385</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56290"/>
                        <GID>EN26SE08.386</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56291"/>
                        <GID>EN26SE08.387</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56292"/>
                        <GID>EN26SE08.388</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56293"/>
                        <GID>EN26SE08.389</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56294"/>
                        <GID>EN26SE08.390</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56295"/>
                        <GID>EN26SE08.391</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56296"/>
                        <GID>EN26SE08.392</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56297"/>
                        <GID>EN26SE08.393</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56298"/>
                        <GID>EN26SE08.394</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56299"/>
                        <GID>EN26SE08.395</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56300"/>
                        <GID>EN26SE08.396</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56301"/>
                        <GID>EN26SE08.397</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56302"/>
                        <GID>EN26SE08.398</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56303"/>
                        <GID>EN26SE08.399</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56304"/>
                        <GID>EN26SE08.400</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56305"/>
                        <GID>EN26SE08.401</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56306"/>
                        <GID>EN26SE08.402</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56307"/>
                        <GID>EN26SE08.403</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56308"/>
                        <GID>EN26SE08.404</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56309"/>
                        <GID>EN26SE08.405</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56310"/>
                        <GID>EN26SE08.406</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56311"/>
                        <GID>EN26SE08.407</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56312"/>
                        <GID>EN26SE08.408</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56313"/>
                        <GID>EN26SE08.409</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56314"/>
                        <GID>EN26SE08.410</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56315"/>
                        <GID>EN26SE08.411</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56316"/>
                        <GID>EN26SE08.412</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56317"/>
                        <GID>EN26SE08.413</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56318"/>
                        <GID>EN26SE08.414</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56319"/>
                        <GID>EN26SE08.415</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56320"/>
                        <GID>EN26SE08.416</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56321"/>
                        <GID>EN26SE08.417</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56322"/>
                        <GID>EN26SE08.418</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="56323"/>
                        <GID>EN26SE08.419</GID>
                    </GPH>
                </SUPLINF>
                <FRDOC>[FR Doc. E8-21594  Filed 9-25-08; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4120-01-C</BILCOD>
            </NOTICE>
        </NOTICES>
    </NEWPART>
    <VOL>73</VOL>
    <NO>188</NO>
    <DATE>Friday, September 26, 2008</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="56325"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P">Department of Housing and Urban Development</AGENCY>
            <TITLE> Federal Property Suitable as Facilities To Assist the Homeless; Notice</TITLE>
        </PTITLE>
        <NOTICES>
            <NOTICE>
                <PREAMB>
                    <PRTPAGE P="56326"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT </AGENCY>
                    <DEPDOC>[Docket No. FR-5186-N-39] </DEPDOC>
                    <SUBJECT>Federal Property Suitable as Facilities To Assist the Homeless </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Office of the Assistant Secretary for Community Planning and Development, HUD. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This Notice identifies unutilized, underutilized, excess, and surplus Federal property reviewed by HUD for suitability for possible use to assist the homeless. </P>
                    </SUM>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Kathy Ezzell, Department of Housing and Urban Development, 451 Seventh Street SW., Room 7266, Washington, DC 20410; telephone (202) 708-1234; TTY number for the hearing- and speech-impaired (202) 708-2565 (these telephone numbers are not toll-free), or call the toll-free Title V information line at 800-927-7588. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        In accordance with 24 CFR part 581 and section 501 of the Stewart B. McKinney Homeless Assistance Act (42 U.S.C. 11411), as amended, HUD is publishing this Notice to identify Federal buildings and other real property that HUD has reviewed for suitability for use to assist the homeless. The properties were reviewed using information provided to HUD by Federal landholding agencies regarding unutilized and underutilized buildings and real property controlled by such agencies or by GSA regarding its inventory of excess or surplus Federal property. This Notice is also published in order to comply with the December 12, 1988 Court Order in 
                        <E T="03">National Coalition for the Homeless</E>
                         v. 
                        <E T="03">Veterans Administration</E>
                        , No. 88-2503-OG (D.D.C.). 
                    </P>
                    <P>Properties reviewed are listed in this Notice according to the following categories: Suitable/available, suitable/unavailable, suitable/to be excess, and unsuitable. The properties listed in the three suitable categories have been reviewed by the landholding agencies, and each agency has transmitted to HUD: (1) Its intention to make the property available for use to assist the homeless, (2) its intention to declare the property excess to the agency's needs, or (3) a statement of the reasons that the property cannot be declared excess or made available for use as facilities to assist the homeless. </P>
                    <P>Properties listed as suitable/available will be available exclusively for homeless use for a period of 60 days from the date of this Notice. Where property is described as for “off-site use only” recipients of the property will be required to relocate the building to their own site at their own expense. Homeless assistance providers interested in any such property should send a written expression of interest to HHS, addressed to Theresa Rita, Division of Property Management, Program Support Center, HHS, room 5B-17, 5600 Fishers Lane, Rockville, MD 20857; (301) 443-2265. (This is not a toll-free number.) HHS will mail to the interested provider an application packet, which will include instructions for completing the application. In order to maximize the opportunity to utilize a suitable property, providers should submit their written expressions of interest as soon as possible. For complete details concerning the processing of applications, the reader is encouraged to refer to the interim rule governing this program, 24 CFR part 581. </P>
                    <P>For properties listed as suitable/to be excess, that property may, if subsequently accepted as excess by GSA, be made available for use by the homeless in accordance with applicable law, subject to screening for other Federal use. At the appropriate time, HUD will publish the property in a Notice showing it as either suitable/available or suitable/unavailable. </P>
                    <P>For properties listed as suitable/unavailable, the landholding agency has decided that the property cannot be declared excess or made available for use to assist the homeless, and the property will not be available. </P>
                    <P>
                        Properties listed as unsuitable will not be made available for any other purpose for 20 days from the date of this Notice. Homeless assistance providers interested in a review by HUD of the determination of unsuitability should call the toll free information line at 1-800-927-7588 for detailed instructions or write a letter to Mark Johnston at the address listed at the beginning of this Notice. Included in the request for review should be the property address (including zip code), the date of publication in the 
                        <E T="04">Federal Register</E>
                        , the landholding agency, and the property number. 
                    </P>
                    <P>
                        For more information regarding particular properties identified in this Notice (
                        <E T="03">i.e.</E>
                        , acreage, floor plan, existing sanitary facilities, exact street address), providers should contact the appropriate landholding agencies at the following addresses: 
                        <E T="03">Air Force:</E>
                         Ms. Kathryn Halvorson, Air Force Real Property Agency, 1700 North Moore St., Suite 2300, Arlington, VA 22209; (703) 696-5502; 
                        <E T="03">Commerce:</E>
                         Mr. Paul Walden, Department of Commerce, Office of Real Estate, 14th &amp; Constitution Ave., NW., Washington, DC 20230; (202) 482-8033; 
                        <E T="03">Energy:</E>
                         Mr. Mark Price, Department of Energy, Office of Engineering &amp; Construction Management, MA-50, 1000 Independence Ave., SW., Washington, DC 20585: (202) 586-5422; 
                        <E T="03">GSA:</E>
                         Mr. John Smith, Deputy Assistant Commissioner, General Services Administration, Office of Property Disposal, 18th &amp; F Streets, NW., Washington, DC 20405; (202) 501-0084; 
                        <E T="03">Navy:</E>
                         Mrs. Mary Arndt, Acting Director, Department of the Navy, Real Estate Services, Naval Facilities Engineering Command, Washington Navy Yard, 1322 Patterson Ave., SE., Suite 1000, Washington, DC 20374-5065; (202) 685-9305; (These are not toll-free numbers). 
                    </P>
                    <SIG>
                        <DATED>Dated: September 18, 2008. </DATED>
                        <NAME>Mark R. Johnston, </NAME>
                        <TITLE>Deputy Assistant Secretary for Special Needs.</TITLE>
                    </SIG>
                    <EXTRACT>
                        <HD SOURCE="HD1">TITLE V, FEDERAL SURPLUS PROPERTY PROGRAM FEDERAL REGISTER REPORT FOR 09/26/2008 </HD>
                        <HD SOURCE="HD1">Suitable/Available Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Facility 1 </FP>
                        <FP SOURCE="FP-1">OTHB Radar Site </FP>
                        <FP SOURCE="FP-1">Tulelake CA 91634 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830012 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Comments: 7920 sq. ft., most recent use—communications </FP>
                        <FP SOURCE="FP-1">Facility 2 </FP>
                        <FP SOURCE="FP-1">OTHB Radar Site </FP>
                        <FP SOURCE="FP-1">Tulelake CA 91634 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830014 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Comments: 900 sq. ft., most recent use—veh maint shop </FP>
                        <FP SOURCE="FP-1">Facilities 3, 4 </FP>
                        <FP SOURCE="FP-1">OTHB Radar Site </FP>
                        <FP SOURCE="FP-1">Tulelake CA 91634 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830015 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Comments: 4160 sq. ft. each, most recent use—communications </FP>
                        <HD SOURCE="HD1">Suitable/Available Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Facility 1 </FP>
                        <FP SOURCE="FP-1">OTHB Radar Site </FP>
                        <FP SOURCE="FP-1">Christmas Valley CA 97641 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830016 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Comments: 16566 sq. ft., most recent use—communications </FP>
                        <FP SOURCE="FP-1">Facility 2 </FP>
                        <FP SOURCE="FP-1">OTHB Radar Site </FP>
                        <FP SOURCE="FP-1">Christmas Valley CA 97641 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">
                            Property Number: 18200830017 
                            <PRTPAGE P="56327"/>
                        </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Comments: 900 sq. ft., most recent use—veh maint shop </FP>
                        <FP SOURCE="FP-1">Facility 4 </FP>
                        <FP SOURCE="FP-1">OTHB Radar Site </FP>
                        <FP SOURCE="FP-1">Christmas Valley CA 97641 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830018 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Comments: 14,190 sq. ft., most recent use—communications </FP>
                        <FP SOURCE="FP-1">Facility 6 </FP>
                        <FP SOURCE="FP-1">OTHB Radar Site </FP>
                        <FP SOURCE="FP-1">Christmas Valley CA 97641 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830019 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Comments: 14,190 sq. ft., most recent use—transmitter bldg. </FP>
                        <HD SOURCE="HD1">Suitable/Available Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Indiana </HD>
                        <FP SOURCE="FP-1">Radio Tower </FP>
                        <FP SOURCE="FP-1">Cannelton Locks &amp; Dam </FP>
                        <FP SOURCE="FP-1">Perry IN </FP>
                        <FP SOURCE="FP-1">Landholding Agency: GSA </FP>
                        <FP SOURCE="FP-1">Property Number: 54200830020 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">GSA Number: 1-D-IN-569E </FP>
                        <FP SOURCE="FP-1">Comments: tower/88 sq. ft. comm storage bldg., heavily wooded area </FP>
                        <HD SOURCE="HD3">Ohio </HD>
                        <FP SOURCE="FP-1">NIKE Site Cd-46 </FP>
                        <FP SOURCE="FP-1">Felicity OH </FP>
                        <FP SOURCE="FP-1">Landholding Agency: GSA </FP>
                        <FP SOURCE="FP-1">Property Number: 31200740015 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">GSA Number: 1-D-OH-0832 </FP>
                        <FP SOURCE="FP-1">Comments: 8 bldgs., most recent use—Ohio Air Natl Guard site </FP>
                        <HD SOURCE="HD2">Land </HD>
                        <HD SOURCE="HD3">Colorado </HD>
                        <FP SOURCE="FP-1">Outer Marker—2.8 acres </FP>
                        <FP SOURCE="FP-1">Denver OUF </FP>
                        <FP SOURCE="FP-1">Denver CO </FP>
                        <FP SOURCE="FP-1">Landholding Agency: GSA </FP>
                        <FP SOURCE="FP-1">Property Number: 54200830022 </FP>
                        <FP SOURCE="FP-1">Status: Surplus </FP>
                        <FP SOURCE="FP-1">GSA Number: 7-U-CO-0674 </FP>
                        <FP SOURCE="FP-1">Comments:  2.8  acres </FP>
                        <HD SOURCE="HD1">Suitable/Available Properties </HD>
                        <HD SOURCE="HD2">Land </HD>
                        <HD SOURCE="HD3">Colorado </HD>
                        <FP SOURCE="FP-1">Outer Marker—0.084 acres </FP>
                        <FP SOURCE="FP-1">Denver JOY </FP>
                        <FP SOURCE="FP-1">Denver CO </FP>
                        <FP SOURCE="FP-1">Landholding Agency: GSA </FP>
                        <FP SOURCE="FP-1">Property Number: 54200830023 </FP>
                        <FP SOURCE="FP-1">Status: Surplus </FP>
                        <FP SOURCE="FP-1">GSA Number: 7-U-CO-0675 </FP>
                        <FP SOURCE="FP-1">Comments:  0.084  acres </FP>
                        <FP SOURCE="FP-1">Outer Marker—0.39 acres </FP>
                        <FP SOURCE="FP-1">Denver FUI </FP>
                        <FP SOURCE="FP-1">Denver CO </FP>
                        <FP SOURCE="FP-1">Landholding Agency: GSA </FP>
                        <FP SOURCE="FP-1">Property Number: 54200830024 </FP>
                        <FP SOURCE="FP-1">Status: Surplus </FP>
                        <FP SOURCE="FP-1">GSA Number: 7-U-CO-0673 </FP>
                        <FP SOURCE="FP-1">Comments:  0.3  acres </FP>
                        <FP SOURCE="FP-1">Outer Marker—0.39 acres </FP>
                        <FP SOURCE="FP-1">Denver DPP </FP>
                        <FP SOURCE="FP-1">Denver CO </FP>
                        <FP SOURCE="FP-1">Landholding Agency: GSA </FP>
                        <FP SOURCE="FP-1">Property Number: 54200830025 </FP>
                        <FP SOURCE="FP-1">Status: Surplus </FP>
                        <FP SOURCE="FP-1">GSA Number: 7-U-CO-0676 </FP>
                        <FP SOURCE="FP-1">Comments:  0.39  acres </FP>
                        <HD SOURCE="HD1">Suitable/Available Properties </HD>
                        <HD SOURCE="HD2">Land </HD>
                        <HD SOURCE="HD3">Massachusetts </HD>
                        <FP SOURCE="FP-1">FAA Site </FP>
                        <FP SOURCE="FP-1">Massasoit Bridge Rd. </FP>
                        <FP SOURCE="FP-1">Nantucket MA 02554 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: GSA </FP>
                        <FP SOURCE="FP-1">Property Number: 54200830026 </FP>
                        <FP SOURCE="FP-1">Status: Surplus </FP>
                        <FP SOURCE="FP-1">GSA Number: MA-0895 </FP>
                        <FP SOURCE="FP-1">Comments: approx 92 acres, entire parcel within MA Division of Fisheries &amp; Wildlife Natural Heritage &amp; Endangered Species Program </FP>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">6798 sq. ft. land </FP>
                        <FP SOURCE="FP-1">Navy Region Northwest </FP>
                        <FP SOURCE="FP-1">Bremerton WA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200830024 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Comments: vacant land </FP>
                        <HD SOURCE="HD1">Suitable/Unavailable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Hawaii </HD>
                        <FP SOURCE="FP-1">Bldg. 2652 </FP>
                        <FP SOURCE="FP-1">Navy Aloha Center </FP>
                        <FP SOURCE="FP-1">Pearl Harbor HI 96860 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710039 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Comments: 9125 sq. ft., most recent use—office </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Alaska </HD>
                        <FP SOURCE="FP-1">Bldgs. 1437, 1190, 2375 </FP>
                        <FP SOURCE="FP-1">Eielson AFB </FP>
                        <FP SOURCE="FP-1">Eielson AK </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830001 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Alaska </HD>
                        <FP SOURCE="FP-1">5 Bldgs. </FP>
                        <FP SOURCE="FP-1">Eielson AFB </FP>
                        <FP SOURCE="FP-1">Eielson AK </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830002 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Directions: 3300, 3301, 3315, 3347, 3383 </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">4 Bldgs. </FP>
                        <FP SOURCE="FP-1">Eielson AFB </FP>
                        <FP SOURCE="FP-1">Eielson AK </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830003 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Directions: 4040, 4332, 4333, 4480 </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 6122, 6205 </FP>
                        <FP SOURCE="FP-1">Eielson AFB </FP>
                        <FP SOURCE="FP-1">Eielson AK </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830004 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building   </HD>
                        <HD SOURCE="HD3">Alaska </HD>
                        <FP SOURCE="FP-1">Bldg. 8128 </FP>
                        <FP SOURCE="FP-1">Elmendorf AFB </FP>
                        <FP SOURCE="FP-1">Elmendorf AK 99506 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830005 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area </FP>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 1989, 8430, 22012 </FP>
                        <FP SOURCE="FP-1">Vandenberg AFB </FP>
                        <FP SOURCE="FP-1">Santa Barbara CA 93437 </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830006 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area </FP>
                          
                        <FP SOURCE="FP-1">10 Bldgs. </FP>
                        <FP SOURCE="FP-1">Lawrence Livermore Natl Lab </FP>
                        <FP SOURCE="FP-1">Livermore CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Energy </FP>
                        <FP SOURCE="FP-1">Property Number: 41200830002 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Directions: 2127, 4302, 4377, 4378, 4383, 5225, 5976, 5979, 5980, 6203 </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area,  Within 2000 ft. of flammable or explosive material   </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 2533 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520005 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration,  Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 13111 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520006 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration,  Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 53325, 53326 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520007 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">
                            Reasons:  Extensive deterioration,  Secured Area 
                            <PRTPAGE P="56328"/>
                        </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">5 Bldgs. </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">53421, 53424 thru 53427 </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520008 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration,  Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 61311, 61313, 61314 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520009 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration,  Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 61320-61324, 61326 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520010 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area,  Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 62711 thru 62717 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520011 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area,  Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 4 </FP>
                        <FP SOURCE="FP-1">Naval Submarine Base </FP>
                        <FP SOURCE="FP-1">Point Loma CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520014 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 8915, 8931 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Seal Beach CA 90740 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530004 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 11, 112 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Seal Beach CA 90740 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530005 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 805 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Seal Beach CA 90740 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530006 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 810 thru 823 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Seal Beach CA 90740 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530007 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 851, 859, 864 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Seal Beach CA 90740 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530008 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 1146 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530009 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 1370, 1371, 1372 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530011 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 115 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530012 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 1674 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendletoon CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530027 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 2636, 2651, 2658 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530028 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <FP SOURCE="FP-1">4 Bldgs. </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530029 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Directions: 26053, 26054, 26056, 26059 </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 53333, 53334 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530030 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 53507, 53569 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530031 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 170111 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530032 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. PM4-3 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Oxnard Co: Ventura CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530033 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 1781 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540001 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 398, 399, 404 </FP>
                        <FP SOURCE="FP-1">Naval Base Point Loma </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540003 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 388, 389, 390, 391 </FP>
                        <FP SOURCE="FP-1">Naval Base Point Loma </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540004 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 16 </FP>
                        <FP SOURCE="FP-1">Naval Submarine Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540017 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 325 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">
                            Property Number: 77200610001 
                            <PRTPAGE P="56329"/>
                        </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Within airport runway clear zone Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 1647, 1648 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610010 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 1713 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610011 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 220189 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610014 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 2295 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610015 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 22115, 22116, 22117 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610016 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 143 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Lemoore CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610017 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 213, 243, 273 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Lemoore CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610018 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 303 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Lemoore CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610019 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 471 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Lemoore CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610020 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 979, 928, 930 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Lemoore CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610021 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 999, 1000 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Lemoore CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610022 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 305, 353 </FP>
                        <FP SOURCE="FP-1">Naval Base Point Loma </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610023 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 358, 359, 360, 361 </FP>
                        <FP SOURCE="FP-1">Naval Base Point Loma </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610024 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 581 </FP>
                        <FP SOURCE="FP-1">Naval Base Point Loma </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610026 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. A25, A27 </FP>
                        <FP SOURCE="FP-1">Naval Base Point Loma </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610027 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 31926, 31927, 31928 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610058 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 41326 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610059 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 41816 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610060 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 1468, 1469 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630002 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 30869 </FP>
                        <FP SOURCE="FP-1">Naval Air Weapons Station </FP>
                        <FP SOURCE="FP-1">China Lake CA 93555 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630005 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 2-8, 3-10 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Mugu Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630009 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 6-11, 6-12, 6-819 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Mugu Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630010 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 85 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Mugu Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630011 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 120, 123 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Mugu Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630012 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 724 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Mugu Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630013 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 764 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Mugu Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630014 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">
                            Reasons: Secured Area 
                            <PRTPAGE P="56330"/>
                        </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 115 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630015 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 323 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630016 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 488 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630017 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 842 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630018 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 927 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630019 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 1150 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630020 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 1361 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630021 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. PH546 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640027 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. PH425 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710001 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. PM 134 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Point Mugu Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710023 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. PH837, PH1372 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710024 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 523107 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710025 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California</HD>
                        <FP SOURCE="FP-1">6 Bldgs. </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710026 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Directions: 523112, 523113, 523114, 523115, 523116, 523117 </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">6 Bldgs. </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710027 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Directions: 523122, 523123, 523124, 523125, 523126, 523127 </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">6 Bldgs. </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710028 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Directions: 523132, 523133, 523134, 523135, 523136, 523137 </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California</HD>
                        <FP SOURCE="FP-1">6 Bldgs. </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710029 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Directions: 523142, 523143, 523144, 523145, 523146, 523147 </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 523156, 523157 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710030 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 30726 </FP>
                        <FP SOURCE="FP-1">Naval Air Weapons </FP>
                        <FP SOURCE="FP-1">China Lake CA 93555 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710047 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California</HD>
                        <FP SOURCE="FP-1">Bldgs. PH284, PH339 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720001 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration,  Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. PH805, PH1179 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720002 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area; Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. PH1207, PH1264, PH1288 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720003 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration,  Secured Area</FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California</HD>
                        <FP SOURCE="FP-1">Bldgs. PM 3-53, PM129, PM402 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Mugu Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720004 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration,  Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. LP908 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Laguna Peak </FP>
                        <FP SOURCE="FP-1">Port Mugu Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">
                            Property Number: 77200720005 
                            <PRTPAGE P="56331"/>
                        </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area; Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. PM790 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Oxnard CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720006 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration,  Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California</HD>
                        <FP SOURCE="FP-1">Bldg. 53402 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720007 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration,  Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. 307 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720009 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. 3135 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720010 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 30727, 31409 </FP>
                        <FP SOURCE="FP-1">Naval Air Weapons Station </FP>
                        <FP SOURCE="FP-1">China Lake CA 93555 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720011 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 60142, 60158 </FP>
                        <FP SOURCE="FP-1">Naval Base Coronado </FP>
                        <FP SOURCE="FP-1">San Clemente Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720012 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Not accessible by road; Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 60160, 60162, 60164 </FP>
                        <FP SOURCE="FP-1">Naval Base Coronado </FP>
                        <FP SOURCE="FP-1">San Clemente Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720013 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 60203, 60210, 60211 </FP>
                        <FP SOURCE="FP-1">Naval Base Coronado </FP>
                        <FP SOURCE="FP-1">San Clemente Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720014 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 60214, 60215 </FP>
                        <FP SOURCE="FP-1">Naval Base Coronado </FP>
                        <FP SOURCE="FP-1">San Clemente Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720015 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 60227, 60243, 60250 </FP>
                        <FP SOURCE="FP-1">Naval Base Coronado </FP>
                        <FP SOURCE="FP-1">San Clemente Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720016 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 60313 </FP>
                        <FP SOURCE="FP-1">Naval Base Coronado </FP>
                        <FP SOURCE="FP-1">San Clemente Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720017 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 404 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">North Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720032 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 3267 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720039 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 11090, 98033 </FP>
                        <FP SOURCE="FP-1">Naval Air Weapons </FP>
                        <FP SOURCE="FP-1">China Lake CA 93555 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720054 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area; Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 41314, 41362 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720055 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 192, 193, 410 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720063 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. 415 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730013 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 3363, 3364 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730014 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">4 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">3185D, 3222, 3251, 3309 </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730015 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Portion/Bldg. T17 </FP>
                        <FP SOURCE="FP-1">Naval Base Point Loma </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730016 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. 297 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730017 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 13, 87 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Coronado Co: San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730022 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 243 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Coronado Co: San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730023 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 381 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Coronado Co: San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730024 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California</HD>
                        <FP SOURCE="FP-1">4 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Air Station</FP>
                        <FP SOURCE="FP-1">493, 663, 682, 784 </FP>
                        <FP SOURCE="FP-1">Coronado Co: San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730025 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <PRTPAGE P="56332"/>
                        <FP SOURCE="FP-1">Bldg. 809 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Coronado Co: San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730026 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. 983 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Coronado Co: San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730027 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 1459 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Coronado Co: San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730028 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 334 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730029 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 124, 148 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">North Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740002 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 314, 341, 636 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">North Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740003 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 710, 802, 826 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">North Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740004 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 60139, 60180 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">San Clemente CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740005 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 41313, 41314 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740006 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California</HD>
                        <FP SOURCE="FP-1">4 Bldgs. </FP>
                        <FP SOURCE="FP-1">Marine Corps Base</FP>
                        <FP SOURCE="FP-1">41359, 41362, 41365, 41366 </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740007 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 43976 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740008 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 53440, 53831 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740009 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 410365 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740010 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 259 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">North Island CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740015 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740017 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 84 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740018 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">4 Bldgs. </FP>
                        <FP SOURCE="FP-1">Marine Corps Base</FP>
                        <FP SOURCE="FP-1">41312, 53426, 53427, 53430 </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810008</FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 2537, 2538 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810009 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 43286, 43287 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810010 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 33007 </FP>
                        <FP SOURCE="FP-1">Naval Air Weapons Station </FP>
                        <FP SOURCE="FP-1">China Lake CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810011 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material</FP>
                        <FP SOURCE="FP-1">Bldgs. 22176, 62507, 410363 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810021 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 25261, 41342, 41344 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810026 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. 105 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Point Loma Co: San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820005 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. PH1230 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820021 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 17, 37, 130 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA 92136 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">
                            Property Number: 77200820023 
                            <PRTPAGE P="56333"/>
                        </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 3053, 3328 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA 92136 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820025 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 3368, 3370 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA 92136 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820026 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 3591, 3592 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA 92136 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820027 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldg. 3603 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA 92136 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820028 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Floodway</FP>
                        <FP SOURCE="FP-1">Bldg. PH1230 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820029 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. PM28 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Point Mugu CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820030 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. PH5295, PH5297 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Oxnard CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820031 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">4 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Oxnard CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820032 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Directions: PH5303, PH5315, PH5318, PH5319 </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. PH5323, PH5329 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Oxnard CA 93042 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820033 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Bldgs. 25152, 41321, 41406 </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Camp Pendleton CA 92055 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200830022 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <HD SOURCE="HD3">Connecticut </HD>
                        <FP SOURCE="FP-1">Pier 1 </FP>
                        <FP SOURCE="FP-1">Naval Submarine Base </FP>
                        <FP SOURCE="FP-1">New London CT </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200830018 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. 98 </FP>
                        <FP SOURCE="FP-1">Naval Submarine Base </FP>
                        <FP SOURCE="FP-1">Groton CT 06349 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200830023 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">District of Columbia</HD>
                        <FP SOURCE="FP-1">Bldg. 396 </FP>
                        <FP SOURCE="FP-1">Naval Support Facility </FP>
                        <FP SOURCE="FP-1">Anacostia Annex DC 20373 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630008 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. W22 </FP>
                        <FP SOURCE="FP-1">Washington Navy Yard </FP>
                        <FP SOURCE="FP-1">Washington DC 20374 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820035 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD3">Florida</HD>
                        <FP SOURCE="FP-1">Bldg. U-150 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Key West Co: Monroe FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520044 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida</HD>
                        <FP SOURCE="FP-1">Bldgs. V1221 A </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Sigsbee Park </FP>
                        <FP SOURCE="FP-1">Key West Co: Monroe FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530013 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. 969 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Jacksonville Co: Duval FL 32212 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540014 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 1759, 1760 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Jacksonville Co: Duval FL </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540015 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida</HD>
                        <FP SOURCE="FP-1">Bldg. 1917 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Jacksonville Co: Duval FL 32212 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540016 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 1, 2 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Mayport Co: Duval FL 32228 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540018 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Floodway; Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 24 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Mayport Co: Duval FL 32228 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540019 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Floodway, Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida</HD>
                        <FP SOURCE="FP-1">Bldg. 66 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Mayport Co: Duval FL 32228 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540020 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Floodway, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. 216 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Mayport Co: Duval FL 32228 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540021 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Floodway, Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 437, 450 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Mayport Co: Duval FL 32228 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540022 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration, Floodway</FP>
                        <PRTPAGE P="56334"/>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida </HD>
                        <FP SOURCE="FP-1">Bldgs. 1234, 1235 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Mayport Co: Duval FL 32228 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540023 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration, Floodway</FP>
                        <FP SOURCE="FP-1">Bldg. 212 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Mayport Co: Duval FL 32228 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620011 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Floodway, Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 508 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Mayport FL 32228 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620035 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Floodway, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida </HD>
                        <FP SOURCE="FP-1">Bldg. 834 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Pensacola Co: Escambia FL 32508 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630022 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 2658 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Pensacola Co: Escambia FL 32508 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630023 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 3483 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Pensacola Co: Escambia FL 32508 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630024 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 6144 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Pensacola Co: Escambia FL 32508 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630025 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida </HD>
                        <FP SOURCE="FP-1">Bldg. F11 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Key West FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630026 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. A225, A409 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Key West FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630027 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldg. A515 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Key West FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630028 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida </HD>
                        <FP SOURCE="FP-1">Bldg. A635 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Key West FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630029 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. A993, A994 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Key West FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630030 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. A1068 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Key West FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630031 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida </HD>
                        <FP SOURCE="FP-1">Bldg. A4021 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Key West FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630032 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 4080 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Key West FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630033 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">88 Facilities </FP>
                        <FP SOURCE="FP-1">Saufley Field </FP>
                        <FP SOURCE="FP-1">Pensacola FL 32508 </FP>
                        <FP SOURCE="FP-1">Landholding  Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740016 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Within airport runway clear zone </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida </HD>
                        <FP SOURCE="FP-1">Bldgs. C5, A329 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Key West FL 33040 </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810007 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area,  Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 2, 5, 24, 26 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Jacksonville Co: Duval FL </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820006 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration,  Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 104A, 136, 159 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Jacksonville Co: Duval FL 32212 </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820007 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area,  Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida </HD>
                        <FP SOURCE="FP-1">6 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Jacksonville Co: Duval FL 32212 </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820008 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Directions:  323, 324, 338, 339, 347, 348 </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">5 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Jacksonville Co: Duval FL 32212 </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820009 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Directions:  607, 612, 614B, 674, 675 </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration,  Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 820, 890 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Jacksonville Co: Duval FL 32212 </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820010 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area,  Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Florida </HD>
                        <FP SOURCE="FP-1">Bldgs. 1756, 1937 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Jacksonville Co: Duval FL 32212 </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820011 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area,  Extensive deterioration </FP>
                        <HD SOURCE="HD3">Georgia </HD>
                        <FP SOURCE="FP-1">Bldg. 5101 </FP>
                        <FP SOURCE="FP-1">
                            Naval Submarine Base 
                            <PRTPAGE P="56335"/>
                        </FP>
                        <FP SOURCE="FP-1">Kings Bay Co: Camden GA 31547 </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520004 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area,  Extensive deterioration, Floodway</FP>
                        <FP SOURCE="FP-1">Bldg. 0038 </FP>
                        <FP SOURCE="FP-1">Naval Submarine Base </FP>
                        <FP SOURCE="FP-1">Kings Bay GA 31547 </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620036 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration,  Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Georgia </HD>
                        <FP SOURCE="FP-1">7 Bldgs. </FP>
                        <FP SOURCE="FP-1">Marine Logistics Base </FP>
                        <FP SOURCE="FP-1">Albany GA </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720040 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Directions:  7100, 7106, 7108, 7110, 5584, 7964, 7966 </FP>
                        <FP SOURCE="FP-1">Reasons:  Secured Area </FP>
                        <HD SOURCE="HD3">Guam</HD>
                        <FP SOURCE="FP-1">Bldg. 1094 </FP>
                        <FP SOURCE="FP-1">AAFB Yigo </FP>
                        <FP SOURCE="FP-1">Yigo GU 96543 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830007 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. B-32 </FP>
                        <FP SOURCE="FP-1">Naval Forces </FP>
                        <FP SOURCE="FP-1">Marianas GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520023 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam</HD>
                        <FP SOURCE="FP-1">Bldgs. 76, 77, 79 </FP>
                        <FP SOURCE="FP-1">Naval Forces </FP>
                        <FP SOURCE="FP-1">Marianas GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520024 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration</FP>
                        <FP SOURCE="FP-1">4 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Forces </FP>
                        <FP SOURCE="FP-1">261, 262, 263, 269 </FP>
                        <FP SOURCE="FP-1">Marianas GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520025 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 404NM </FP>
                        <FP SOURCE="FP-1">Naval Forces </FP>
                        <FP SOURCE="FP-1">Marianas GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520026 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 3150, 3268 </FP>
                        <FP SOURCE="FP-1">Naval Forces </FP>
                        <FP SOURCE="FP-1">Marianas GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520030 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building</HD>
                        <HD SOURCE="HD3">Guam</HD>
                        <FP SOURCE="FP-1">Bldgs. 5409, 5412, 5413 </FP>
                        <FP SOURCE="FP-1">Naval Forces </FP>
                        <FP SOURCE="FP-1">Marianas GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520031 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons:  Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldg. 5500 </FP>
                        <FP SOURCE="FP-1">Naval Forces </FP>
                        <FP SOURCE="FP-1">Marianas GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520032 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive  deterioration</FP>
                        <FP SOURCE="FP-1">73 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Computer Station </FP>
                        <FP SOURCE="FP-1">Marianas GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520045 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Directions:  A700-A716, A725, A728, A735, A741-A784, A803-A805, A811-A813, A829-A831 </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam</HD>
                        <FP SOURCE="FP-1">Bldgs. 2006, 2009 </FP>
                        <FP SOURCE="FP-1">Naval Ship Repair Facility </FP>
                        <FP SOURCE="FP-1">Marianas GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520048 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 2014, 2916 </FP>
                        <FP SOURCE="FP-1">Naval Ship Repair Facility </FP>
                        <FP SOURCE="FP-1">Marianas GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520049 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 277, 308 </FP>
                        <FP SOURCE="FP-1">Naval Forces Marianas </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610028 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam</HD>
                        <FP SOURCE="FP-1">Bldgs. 1686, 1689, 1690 </FP>
                        <FP SOURCE="FP-1">Naval Forces Marianas </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610029 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 1714, 1767, 1768 </FP>
                        <FP SOURCE="FP-1">Naval Forces Marianas </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610030 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 1771, 1772, 1773 </FP>
                        <FP SOURCE="FP-1">Naval Forces Marianas </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610031 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 1791, 1792 </FP>
                        <FP SOURCE="FP-1">Naval Forces Marianas </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610032 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam</HD>
                        <FP SOURCE="FP-1">Bldgs. 3000, 3001 </FP>
                        <FP SOURCE="FP-1">Naval Forces Marianas </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610033 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 3002, 3004, 3005 </FP>
                        <FP SOURCE="FP-1">Naval Forces Marianas </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610034 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 3006, 3007 </FP>
                        <FP SOURCE="FP-1">Naval Forces Marianas </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610035 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Steam Plant </FP>
                        <FP SOURCE="FP-1">Naval Forces Marianas </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610036 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam</HD>
                        <FP SOURCE="FP-1">Bldgs. 403, 404 </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620013 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 464, 729 </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620014 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 836, 837 </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620015 </FP>
                        <FP SOURCE="FP-1">
                            Status: Unutilized 
                            <PRTPAGE P="56336"/>
                        </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam</HD>
                        <FP SOURCE="FP-1">Bldg. 11XC7 </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620016 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 23YC1, 23YC2, 23YC3 </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620017 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 23YC4, 23YC5 </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620018 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam</HD>
                        <FP SOURCE="FP-1">Bldgs. 24YC7, 24YC8 </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620019 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 26YC3, 26YC5 </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620020 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Old Bus Stop </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620021 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam</HD>
                        <FP SOURCE="FP-1">2 Guard Houses </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency:  Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620022 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration Secured Area </FP>
                        <FP SOURCE="FP-1">9 Magazines </FP>
                        <FP SOURCE="FP-1">Marianas Support Activity </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Naval Magazine GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620023 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 151, 152, 153 </FP>
                        <FP SOURCE="FP-1">Naval Forces Marianas </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630001 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam </HD>
                        <FP SOURCE="FP-1">Bldg. 4 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Barrigada GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710002 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. C115 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Barrigada GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710003 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 160 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Barrigada GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710004 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 176 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Barrigada GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710005 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam </HD>
                        <FP SOURCE="FP-1">Bldg. 33 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710006 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 219 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710007 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 950 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710008 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 1769 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710009 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam </HD>
                        <FP SOURCE="FP-1">Bldgs. 3186, 3187, 3188 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710010 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 4408, 4409 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710011 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Hazmat Storage </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Polaris Point </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710012 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Guam </HD>
                        <FP SOURCE="FP-1">Storage Bldg. </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Polaris Point </FP>
                        <FP SOURCE="FP-1">Santa Rita Co: Apra Harbor GU </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710013 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD3">Hawaii </HD>
                        <FP SOURCE="FP-1">Bldg. 1713 </FP>
                        <FP SOURCE="FP-1">Hickam AFB </FP>
                        <FP SOURCE="FP-1">Hickam HI </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830008 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 346 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Pearl Harbor HI 96860 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610002 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Hawaii </HD>
                        <FP SOURCE="FP-1">Bank </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Kaneohe Bay HI 96863 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200830019 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 136 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Pearl Harbor HI 96860 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">
                            Property Number: 77200830021 
                            <PRTPAGE P="56337"/>
                        </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <HD SOURCE="HD3">Louisiana </HD>
                        <FP SOURCE="FP-1">Bldgs. 37, 89, 122 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">New Orleans LA 70143 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810024 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Louisiana </HD>
                        <FP SOURCE="FP-1">Bldgs. 159, 418, 902 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">New Orleans LA 70143 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810025 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 11 </FP>
                        <FP SOURCE="FP-1">Naval Support Activity </FP>
                        <FP SOURCE="FP-1">New Orleans LA 70142 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810027 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD3">Maryland </HD>
                        <FP SOURCE="FP-1">Bldg. 84NS </FP>
                        <FP SOURCE="FP-1">Naval Support Activity </FP>
                        <FP SOURCE="FP-1">Annapolis Co: Anne Arundel MD 21402 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610038 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Floodway </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Maryland </HD>
                        <FP SOURCE="FP-1">Bldg. 2075 </FP>
                        <FP SOURCE="FP-1">Naval Surface Warfare </FP>
                        <FP SOURCE="FP-1">Indian Head MD </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630043 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD3">Mississippi </HD>
                        <FP SOURCE="FP-1">Bldg. 9 </FP>
                        <FP SOURCE="FP-1">Construction Battalion Center </FP>
                        <FP SOURCE="FP-1">Gulfport MS </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610039 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 22, 27, 41 </FP>
                        <FP SOURCE="FP-1">Construction Battalion Center </FP>
                        <FP SOURCE="FP-1">Gulfport MS </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610040 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Mississippi </HD>
                        <FP SOURCE="FP-1">Bldgs. 108, 181, 183 </FP>
                        <FP SOURCE="FP-1">Construction Battalion Center </FP>
                        <FP SOURCE="FP-1">Gulfport MS </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610041 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 201 </FP>
                        <FP SOURCE="FP-1">Construction Battalion Center </FP>
                        <FP SOURCE="FP-1">Gulfport MS </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610042 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 270, 270A-1, 270A-2 </FP>
                        <FP SOURCE="FP-1">Construction Battalion Center </FP>
                        <FP SOURCE="FP-1">Gulfport MS </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610043 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Mississippi </HD>
                        <FP SOURCE="FP-1">Bldgs. 375, 420 </FP>
                        <FP SOURCE="FP-1">Construction Battalion Center </FP>
                        <FP SOURCE="FP-1">Gulfport MS </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200610044 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 95, 96 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Meridian MS 39309 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720046 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Within airport runway clear zone Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <FP SOURCE="FP-1">Bldg. 167 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Meridian MS 39309 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720047 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Mississippi </HD>
                        <FP SOURCE="FP-1">Bldgs. 212, 228 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Meridian MS 39309 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720048 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 266, 267 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Meridian MS 39309 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720049 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 351, 445 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Meridian MS 39309 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720050 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 182, 183 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Meridian MS 39309 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810014 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Mississippi </HD>
                        <FP SOURCE="FP-1">Bldgs. 222, 230, 326 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Meridian MS 39309 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810015 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD3">Nevada </HD>
                        <FP SOURCE="FP-1">3 Bldgs. </FP>
                        <FP SOURCE="FP-1">Nevada Test Site</FP>
                        <FP SOURCE="FP-1">23-790, 06-CP50, 26-2107 </FP>
                        <FP SOURCE="FP-1">Mercury Co: Nye NV 89023 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200510025 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Other—contamination, Secured Area </FP>
                        <FP SOURCE="FP-1">Units 501-521 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Fallon NV </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710017 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">New Jersey </HD>
                        <FP SOURCE="FP-1">Bldgs. 105, 111, 266 </FP>
                        <FP SOURCE="FP-1">Naval Air Eng. Station </FP>
                        <FP SOURCE="FP-1">Lakehurst NJ 08733 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820001 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 464, 480 </FP>
                        <FP SOURCE="FP-1">Naval Air Eng. Station </FP>
                        <FP SOURCE="FP-1">Lakehurst NJ 08733 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820002 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 539, 560, 565 </FP>
                        <FP SOURCE="FP-1">Naval Air Eng. Station </FP>
                        <FP SOURCE="FP-1">Lakehurst NJ 08733 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820003 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">
                            Reasons: Extensive deterioration, Secured Area 
                            <PRTPAGE P="56338"/>
                        </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">New Mexico</HD>
                        <FP SOURCE="FP-1">6 Bldgs. </FP>
                        <FP SOURCE="FP-1">Cannon AFB </FP>
                        <FP SOURCE="FP-1">Curry NM 88102 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830009 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Directions: 1156, 1160, 1245, 1256, 1258, 1260 </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 20612, 29071, 37505 </FP>
                        <FP SOURCE="FP-1">Kirtland AFB </FP>
                        <FP SOURCE="FP-1">Bernalillo NM 87117 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830010 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD3">North Carolina </HD>
                        <FP SOURCE="FP-1">Bldg. 82 </FP>
                        <FP SOURCE="FP-1">Marine Corps Air Station </FP>
                        <FP SOURCE="FP-1">Cherry Point Co: Craven NC 28533 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200510009 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">North Carolina </HD>
                        <FP SOURCE="FP-1">Bldg. 4314 </FP>
                        <FP SOURCE="FP-1">Marine Corps Air Station </FP>
                        <FP SOURCE="FP-1">Cherry Point Co: Craven NC 28533 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200510010 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 124 </FP>
                        <FP SOURCE="FP-1">Marine Corps Air Station </FP>
                        <FP SOURCE="FP-1">Cherry Point Co: Craven NC 28533 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200510023 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 73, 95, 1018 </FP>
                        <FP SOURCE="FP-1">Marine Corps Air Station </FP>
                        <FP SOURCE="FP-1">Cherry Point NC </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620003 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 499 </FP>
                        <FP SOURCE="FP-1">Marine Corps Air Station </FP>
                        <FP SOURCE="FP-1">Cherry Point NC </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620038 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">North Carolina </HD>
                        <FP SOURCE="FP-1">Bldgs. 3177, 3885 </FP>
                        <FP SOURCE="FP-1">Marine Corps Air Station </FP>
                        <FP SOURCE="FP-1">Cherry Point NC </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620039 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 4473 </FP>
                        <FP SOURCE="FP-1">Marine Corps Air Station </FP>
                        <FP SOURCE="FP-1">Cherry Point NC </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620040 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 4523 </FP>
                        <FP SOURCE="FP-1">Marine Corps Air Station </FP>
                        <FP SOURCE="FP-1">Cherry Point NC </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620041 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Pennsylvania </HD>
                        <FP SOURCE="FP-1">Bldgs. 13, 90, 93, 97 </FP>
                        <FP SOURCE="FP-1">Naval Support Activity </FP>
                        <FP SOURCE="FP-1">Philadelphia PA 19111 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820012 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 431, 483 </FP>
                        <FP SOURCE="FP-1">Naval Support Activity </FP>
                        <FP SOURCE="FP-1">Philadelphia PA 19111 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820013 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Extensive deterioration</FP>
                        <FP SOURCE="FP-1">Bldgs. 530, 534, 567, 585 </FP>
                        <FP SOURCE="FP-1">Naval Support Activity </FP>
                        <FP SOURCE="FP-1">Philadelphia PA 19111 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820014 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Pennsylvania </HD>
                        <FP SOURCE="FP-1">Bldgs. 618, 743 </FP>
                        <FP SOURCE="FP-1">Naval Support Activity </FP>
                        <FP SOURCE="FP-1">Philadelphia PA 19111 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820015 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD3">Rhode Island </HD>
                        <FP SOURCE="FP-1">Sheds 1 &amp; 2 </FP>
                        <FP SOURCE="FP-1">Narragansett Laboratory </FP>
                        <FP SOURCE="FP-1">Narragansett RI 02882 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Commerce </FP>
                        <FP SOURCE="FP-1">Property Number: 27200830001 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 305CP </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Newport RI 02841 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820004 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Rhode Island </HD>
                        <FP SOURCE="FP-1">Bldg. 1A-CC </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Newport RI 02841 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820022 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 164 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Newport RI 02841 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820036 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Floodway, Secured Area</FP>
                        <FP SOURCE="FP-1">Bldgs. 348, 85CHI </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Newport RI </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820043 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Rhode Island </HD>
                        <FP SOURCE="FP-1">Facility 670 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Harbor Island </FP>
                        <FP SOURCE="FP-1">Newport RI 02841 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820044 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD3">South Carolina </HD>
                        <FP SOURCE="FP-1">Bldgs. 1000 thru 1021 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Goose Creek Co: Berkeley SC 29445 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200440018 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 102 </FP>
                        <FP SOURCE="FP-1">Marine Corps Recruit Depot </FP>
                        <FP SOURCE="FP-1">Parris Island Co: Beaufort SC 29905 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530017 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area,  Floodway </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">South Carolina </HD>
                        <FP SOURCE="FP-1">21 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Goose Creek Co: Berkely SC 29445 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620034 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Directions: 4, 167C, 174, 180, 350, 383, 400, 410, 769, 790, 823, 824, 904, 930, 930A, 953, 953A, 971, 975, 2305, 3526 </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 1148 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Goose Creek Co: Berkeley SC 29445 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630044 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <PRTPAGE P="56339"/>
                        <FP SOURCE="FP-1">Bldg. 200 </FP>
                        <FP SOURCE="FP-1">Marine Corps Recruit Depot </FP>
                        <FP SOURCE="FP-1">Parris Island SC 29905 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720018 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Floodway, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">South Carolina </HD>
                        <FP SOURCE="FP-1">Bldgs. 908, 1ATX211-1ATX220 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Goose Creek SC 29445 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810029 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <FP SOURCE="FP-1">Bldgs. 40, 48, 856 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Goose Creek SC 29445 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810030 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Within 2000 ft. of flammable or explosive material </FP>
                        <FP SOURCE="FP-1">Bldgs. 934, 2333 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Goose Creek SC 29445 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810031 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">South Dakota </HD>
                        <FP SOURCE="FP-1">Bldg. 6927 </FP>
                        <FP SOURCE="FP-1">Ellsworth AFB </FP>
                        <FP SOURCE="FP-1">Meade SD 57706 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Air Force </FP>
                        <FP SOURCE="FP-1">Property Number: 18200830011 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <HD SOURCE="HD3">Tennessee </HD>
                        <FP SOURCE="FP-1">Bldgs. 2, 3, 5 </FP>
                        <FP SOURCE="FP-1">Naval/Marine Corps Rsv Ctr </FP>
                        <FP SOURCE="FP-1">Knoxville Co: Knox TN 37920 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530018 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 9720-03, 9720-06 </FP>
                        <FP SOURCE="FP-1">Y-12 Natl Nuclear Security Complex </FP>
                        <FP SOURCE="FP-1">Oak Ridge TN 37831 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720038 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Texas </HD>
                        <FP SOURCE="FP-1">Bldgs. 4-24, 4-27, 4-29 </FP>
                        <FP SOURCE="FP-1">Pantex Plant </FP>
                        <FP SOURCE="FP-1">Amarillo TX 79120 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Energy </FP>
                        <FP SOURCE="FP-1">Property Number: 41200830003 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <FP SOURCE="FP-1">Bldg. 11-027 </FP>
                        <FP SOURCE="FP-1">Pantex Plant </FP>
                        <FP SOURCE="FP-1">Amarillo TX 79120 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Energy </FP>
                        <FP SOURCE="FP-1">Property Number: 41200830004 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area </FP>
                        <FP SOURCE="FP-1">3 Bldgs. </FP>
                        <FP SOURCE="FP-1">Pantex Plant 12-0245, 12-041SS, 12-075A </FP>
                        <FP SOURCE="FP-1">Amarillo TX 79120 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Energy </FP>
                        <FP SOURCE="FP-1">Property Number: 41200830005 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Within 2000 ft. of flammable or explosive material </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Texas </HD>
                        <FP SOURCE="FP-1">Bldg. 1732 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Corpus Christi Co: Nueces TX </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200540007 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 243 </FP>
                        <FP SOURCE="FP-1">Naval Air Station Joint Reserve Base </FP>
                        <FP SOURCE="FP-1">Ft. Worth Co: Tarrant TX 76127 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640035 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 1430 </FP>
                        <FP SOURCE="FP-1">Naval Air Station Joint Reserve Base </FP>
                        <FP SOURCE="FP-1">Ft. Worth Co: Tarrant TX 76127 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640036 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Texas </HD>
                        <FP SOURCE="FP-1">Bldg. 1500 </FP>
                        <FP SOURCE="FP-1">Naval Air Station Joint Reserve Base </FP>
                        <FP SOURCE="FP-1">Ft. Worth Co: Tarrant TX 76127 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640037 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 4151 </FP>
                        <FP SOURCE="FP-1">Naval Air Station Joint Reserve Base </FP>
                        <FP SOURCE="FP-1">Ft. Worth Co: Tarrant TX 76127 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640038 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 3379, 3380 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Ft. Worth Co: Tarrant TX 76127 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810023 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Utah </HD>
                        <FP SOURCE="FP-1">5 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Industrial Ordinance Plant </FP>
                        <FP SOURCE="FP-1">Magna UT 84044 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720033 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Directions: 4D, 6A, 6C, 8C, 10B </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <FP SOURCE="FP-1">4 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Industrial Ordinance Plant </FP>
                        <FP SOURCE="FP-1">Magna UT 84044 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720034 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Directions: 11, 15, 16, 19 </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 22A, 22B, 22C </FP>
                        <FP SOURCE="FP-1">Naval Industrial Ordinance Plant </FP>
                        <FP SOURCE="FP-1">Magna UT 84044 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720035 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Utah </HD>
                        <FP SOURCE="FP-1">Bldgs. 23A, 23B, 23C </FP>
                        <FP SOURCE="FP-1">Naval Industrial Ordinance Plant </FP>
                        <FP SOURCE="FP-1">Magna UT 84044 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720036 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area </FP>
                        <FP SOURCE="FP-1">4 Bldgs. </FP>
                        <FP SOURCE="FP-1">Naval Industrial Ordinance Plant </FP>
                        <FP SOURCE="FP-1">Magna UT 84044 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720037 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Directions: 33, 45B, 45C, 46D </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area </FP>
                        <HD SOURCE="HD3">Virginia </HD>
                        <FP SOURCE="FP-1">Bldgs. 500, 501 </FP>
                        <FP SOURCE="FP-1">Naval Weapon Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640012 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Virginia </HD>
                        <FP SOURCE="FP-1">Bldg. 628 </FP>
                        <FP SOURCE="FP-1">Naval Weapon Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640013 </FP>
                        <FP SOURCE="FP-1">
                            Status: Excess 
                            <PRTPAGE P="56340"/>
                        </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 2398 </FP>
                        <FP SOURCE="FP-1">Naval Station </FP>
                        <FP SOURCE="FP-1">Norfolk VA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200730021 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 375, 502, 502A </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810002 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Virginia </HD>
                        <FP SOURCE="FP-1">Bldgs. 503, 503A, 504 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810003 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 505, 505A </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810004 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 1213, 1979 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810005 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Virginia </HD>
                        <FP SOURCE="FP-1">Bldgs. 2007, 2008 </FP>
                        <FP SOURCE="FP-1">Naval Weapons Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810006 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 439, 466 </FP>
                        <FP SOURCE="FP-1">Naval Weapon Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820016 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 760, 761 </FP>
                        <FP SOURCE="FP-1">Naval Weapon Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820017 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 1820, 1895 </FP>
                        <FP SOURCE="FP-1">Naval Weapon Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820018 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Virginia </HD>
                        <FP SOURCE="FP-1">Bldgs. 1977, 1978, 1983 </FP>
                        <FP SOURCE="FP-1">Naval Weapon Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820019 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. CAD-RR </FP>
                        <FP SOURCE="FP-1">Naval Weapon Station </FP>
                        <FP SOURCE="FP-1">Yorktown VA 23691 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200820020 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldg. 529 </FP>
                        <FP SOURCE="FP-1">Puget Sound Naval Shipyard </FP>
                        <FP SOURCE="FP-1">Bremerton WA 98314-5000 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200040020 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldg. 8 </FP>
                        <FP SOURCE="FP-1">Naval Reserve Center </FP>
                        <FP SOURCE="FP-1">Spokane WA 99205 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200430025 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 10, 11 </FP>
                        <FP SOURCE="FP-1">Naval Reserve Center </FP>
                        <FP SOURCE="FP-1">Spokane WA 99205 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200430026 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 2656-2658 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Lake Hancock </FP>
                        <FP SOURCE="FP-1">Coupeville Co: Island WA 98239 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200430027 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldgs. 2652, 2705 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Whidbey </FP>
                        <FP SOURCE="FP-1">Oak Harbor WA 98277 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200440010 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 79, 884 </FP>
                        <FP SOURCE="FP-1">NAS Whidbey Island </FP>
                        <FP SOURCE="FP-1">Seaplane Base </FP>
                        <FP SOURCE="FP-1">Oak Harbor WA 98277 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200440011 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 121 </FP>
                        <FP SOURCE="FP-1">NAS Whidbey Island </FP>
                        <FP SOURCE="FP-1">Ault Field </FP>
                        <FP SOURCE="FP-1">Oak Harbor WA 98277 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200440012 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldg. 419 </FP>
                        <FP SOURCE="FP-1">NAS Whidbey Island </FP>
                        <FP SOURCE="FP-1">Ault Field </FP>
                        <FP SOURCE="FP-1">Oak Harbor WA 98277 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200440013 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 2609, 2610 </FP>
                        <FP SOURCE="FP-1">NAS Whidbey Island </FP>
                        <FP SOURCE="FP-1">Ault Field </FP>
                        <FP SOURCE="FP-1">Oak Harbor WA 98277 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200440014 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 2753 </FP>
                        <FP SOURCE="FP-1">NAS Whidbey Island </FP>
                        <FP SOURCE="FP-1">Ault Field </FP>
                        <FP SOURCE="FP-1">Oak Harbor WA 98277 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200440015 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldg. 108 </FP>
                        <FP SOURCE="FP-1">Naval Magazine </FP>
                        <FP SOURCE="FP-1">Port Hadlock Co: Jefferson WA 98339-9723 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200510015 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldg. 351 </FP>
                        <FP SOURCE="FP-1">Puget Sound Naval Shipyard </FP>
                        <FP SOURCE="FP-1">Bremerton WA 98314 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200530026 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 1032 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Bangor Tower Site </FP>
                        <FP SOURCE="FP-1">Silverdale WA 98315 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630045 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">
                            Reasons: Within 2000 ft. of flammable or explosive material, Secured Area 
                            <PRTPAGE P="56341"/>
                        </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldg. 71 </FP>
                        <FP SOURCE="FP-1">Naval Magazine </FP>
                        <FP SOURCE="FP-1">Port Hadlock Co: Jefferson WA 98339-9723 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640007 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 82, 83 </FP>
                        <FP SOURCE="FP-1">Naval Magazine </FP>
                        <FP SOURCE="FP-1">Port Hadlock Co: Jefferson WA 98339-9723 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640008 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 168, 188 </FP>
                        <FP SOURCE="FP-1">Naval Magazine </FP>
                        <FP SOURCE="FP-1">Port Hadlock Co: Jefferson WA 98339-9723 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640009 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldg. 729 </FP>
                        <FP SOURCE="FP-1">Naval Magazine </FP>
                        <FP SOURCE="FP-1">Port Hadlock Co: Jefferson WA 98339-9723 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640010 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 910, 921 </FP>
                        <FP SOURCE="FP-1">Naval Magazine </FP>
                        <FP SOURCE="FP-1">Port Hadlock Co: Jefferson WA 98339-9723 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640011 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Extensive deterioration </FP>
                        <FP SOURCE="FP-1">Bldgs. 407, 447 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Bremerton Co: Kitsap WA 98310 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640014 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldg. 867 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Bremerton Co: Kitsap WA 98310 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640015 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 937, 975 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Bremerton Co: Kitsap WA 98310 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640016 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 1449 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Silverdale Co: Kitsap WA 98315 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640017 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 1670 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Silverdale Co: Kitsap WA 98315 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640018 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldgs. 2007, 2801 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Silverdale Co: Kitsap WA 98315 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640019 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 6021, 6095 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Silverdale Co: Kitsap WA 98315 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640020 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 6606, 6661 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Silverdale Co: Kitsap WA 98315 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640021 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 726, 727, 734 </FP>
                        <FP SOURCE="FP-1">Naval Undersea Warfare </FP>
                        <FP SOURCE="FP-1">Keyport Co: Kitsap WA 98345 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640022 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldgs. 901, 911 </FP>
                        <FP SOURCE="FP-1">Naval Undersea Warfare </FP>
                        <FP SOURCE="FP-1">Keyport Co: Kitsap WA 98345 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640023 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <FP SOURCE="FP-1">Bldgs. 925, 938 </FP>
                        <FP SOURCE="FP-1">Naval Undersea Warfare </FP>
                        <FP SOURCE="FP-1">Keyport Co: Kitsap WA 98345 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640024 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <FP SOURCE="FP-1">Bldg. 1020 </FP>
                        <FP SOURCE="FP-1">Naval Undersea Warfare </FP>
                        <FP SOURCE="FP-1">Keyport Co: Kitsap WA 98345 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200640025 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Fisher Transit Site </FP>
                        <FP SOURCE="FP-1">Easement </FP>
                        <FP SOURCE="FP-1">Jefferson WA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710015 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Other—Remote Location </FP>
                        <FP SOURCE="FP-1">Bldgs. 437, 853 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Bremerton Co: Kitsap WA 98310 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710018 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 1039 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Bremerton Co: Kitsap WA 98310 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710019 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldgs. 1400, 1461 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Bremerton Co: Kitsap WA 98310 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710020 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <FP SOURCE="FP-1">Bldg. 6026 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Bremerton Co: Kitsap WA 98310 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710021 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area, Within 2000 ft. of flammable or explosive material </FP>
                        <FP SOURCE="FP-1">Bldgs. 6608, 6609, 6904 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Bremerton Co: Kitsap WA 98310 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710022 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Building </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">Bldgs. 110, 116 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Oak Harbor WA 98278 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740013 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Bldg. 839 </FP>
                        <FP SOURCE="FP-1">Puget Sound Naval Shipyard </FP>
                        <FP SOURCE="FP-1">Bremerton WA 98314 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200740014 </FP>
                        <FP SOURCE="FP-1">
                            Status: Excess 
                            <PRTPAGE P="56342"/>
                        </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area </FP>
                        <FP SOURCE="FP-1">Bldgs. 402, 403, 2634 </FP>
                        <FP SOURCE="FP-1">Naval Air Station </FP>
                        <FP SOURCE="FP-1">Oak Harbor Co: Whidbey Island WA 96278 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200810020 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Extensive deterioration </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Land </HD>
                        <HD SOURCE="HD3">Alabama </HD>
                        <FP SOURCE="FP-1">Lock &amp; Dam No. 12/Boatyard </FP>
                        <FP SOURCE="FP-1">Black Warrior River </FP>
                        <FP SOURCE="FP-1">Tuscaloosa AL </FP>
                        <FP SOURCE="FP-1">Landholding Agency: GSA </FP>
                        <FP SOURCE="FP-1">Property Number: 54200830021 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">GSA Number: 4-D-AL-0777 </FP>
                        <FP SOURCE="FP-1">Reasons: Floodway </FP>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Trailer Space </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">San Diego CA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520013 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Parcels 1, 2, 3, 4 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630003 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Land </HD>
                        <HD SOURCE="HD3">California </HD>
                        <FP SOURCE="FP-1">Parcels 11, 12, 13, 14, 15 </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200630004 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">Sand Spit </FP>
                        <FP SOURCE="FP-1">Naval Base </FP>
                        <FP SOURCE="FP-1">Port Hueneme Co: Ventura CA 93043 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200720008 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Floodway </FP>
                        <HD SOURCE="HD3">Hawaii </HD>
                        <FP SOURCE="FP-1">14.235 parcel </FP>
                        <FP SOURCE="FP-1">Marine Corps Base </FP>
                        <FP SOURCE="FP-1">Kaneohe HI 96863 </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200830020 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <HD SOURCE="HD1">Unsuitable Properties </HD>
                        <HD SOURCE="HD2">Land </HD>
                        <HD SOURCE="HD3">Washington </HD>
                        <FP SOURCE="FP-1">405 sq. ft./Land </FP>
                        <FP SOURCE="FP-1">Naval Base Kitsap </FP>
                        <FP SOURCE="FP-1">Bangor WA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200520060 </FP>
                        <FP SOURCE="FP-1">Status: Unutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Secured Area </FP>
                        <FP SOURCE="FP-1">230 sq. ft. land </FP>
                        <FP SOURCE="FP-1">Naval Magazine </FP>
                        <FP SOURCE="FP-1">Indian Island WA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200620037 </FP>
                        <FP SOURCE="FP-1">Status: Underutilized </FP>
                        <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material, Secured Area </FP>
                        <FP SOURCE="FP-1">Tabook Transit Site </FP>
                        <FP SOURCE="FP-1">Easement </FP>
                        <FP SOURCE="FP-1">Jefferson WA </FP>
                        <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                        <FP SOURCE="FP-1">Property Number: 77200710016 </FP>
                        <FP SOURCE="FP-1">Status: Excess </FP>
                        <FP SOURCE="FP-1">Reasons: Other—Remote Location</FP>
                    </EXTRACT>
                </SUPLINF>
                <FRDOC> [FR Doc. E8-22329 Filed 9-25-08; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 4210-67-P </BILCOD>
            </NOTICE>
        </NOTICES>
    </NEWPART>
    <VOL>73</VOL>
    <NO>188</NO>
    <DATE>Friday, September 26, 2008</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="56343"/>
            <PARTNO>Part IV</PARTNO>
            <AGENCY TYPE="PNR">Department of Defense</AGENCY>
            <AGENCY TYPE="P">Office of Personnel Management</AGENCY>
            <CFR>5 CFR Part 9901</CFR>
            <TITLE>National Security Personnel System; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="56344"/>
                    <AGENCY TYPE="S">DEPARTMENT OF DEFENSE </AGENCY>
                    <AGENCY TYPE="O">OFFICE OF PERSONNEL MANAGEMENT </AGENCY>
                    <CFR>5 CFR Part 9901 </CFR>
                    <RIN>RIN 3206-AL62 </RIN>
                    <SUBJECT>National Security Personnel System </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Department of Defense; Office of Personnel Management. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Department of Defense (DoD) and the Office of Personnel Management are issuing final regulations governing the operation of the National Security Personnel System (NSPS), a human resources management system for DoD, as originally authorized by the National Defense Authorization Act for Fiscal Year 2004 and amended by the National Defense Authorization Act for Fiscal Year 2008. This final regulation governs compensation, classification and performance management under NSPS. NSPS aligns DoD's human resources management system with the Department's critical mission requirements and protects the civil service rights of its employees. </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>November 25, 2008. </P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>At DoD, Bradley B. Bunn, (703) 696-5303; for OPM, Charles D. Grimes III, (202) 418-3163. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">Table of Contents </HD>
                    <P>
                        This 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section is organized as follows: 
                    </P>
                    <EXTRACT>
                        <FP SOURCE="FP-2">I. The Case for Action </FP>
                        <FP SOURCE="FP-2">II. The Need for Change </FP>
                        <FP SOURCE="FP-2">III. Significant Changes to the Original Law </FP>
                        <FP SOURCE="FP-2">IV. Two Years of Operational Experience Under NSPS </FP>
                        <FP SOURCE="FP1-2">A. Classification </FP>
                        <FP SOURCE="FP1-2">B. Compensation </FP>
                        <FP SOURCE="FP1-2">C. Pay Administration </FP>
                        <FP SOURCE="FP1-2">D. Performance and Pay Pool Management </FP>
                        <FP SOURCE="FP1-2">E. Other Changes </FP>
                        <FP SOURCE="FP-2">V. Response to Public Comments </FP>
                        <FP SOURCE="FP1-2">A. Major Issues </FP>
                        <FP SOURCE="FP1-2">1. Specificity of the Regulation </FP>
                        <FP SOURCE="FP1-2">2. Collective Bargaining and Labor Relations </FP>
                        <FP SOURCE="FP1-2">3. Performance and Pay Pool Management </FP>
                        <FP SOURCE="FP1-2">4. Influence of Performance Versus Market Factors on Pay </FP>
                        <FP SOURCE="FP1-2">5. Control Points </FP>
                        <FP SOURCE="FP1-2">B. General Issues </FP>
                        <FP SOURCE="FP1-2">C. Issues by Subpart </FP>
                        <FP SOURCE="FP1-2">1. Subpart A—General Provisions </FP>
                        <FP SOURCE="FP1-2">2. Subpart B—Classification </FP>
                        <FP SOURCE="FP1-2">3. Subpart C—Pay and Pay Administration </FP>
                        <FP SOURCE="FP1-2">4. Subpart D—Performance Management </FP>
                        <FP SOURCE="FP-2">VI. Next Steps</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">I. The Case for Action </HD>
                    <P>The United States needs a future force that is defined less by size and more by mobility and swiftness, one that is easier to deploy and sustain, one that relies more heavily on stealth, precision weaponry, and information technologies. </P>
                    <P>With this philosophy established in 2001, DoD set the direction for the transformation of defense strategy and defense management—the way DoD achieves its mission. To accomplish this, DoD transformed the way it leads and manages the people who develop, acquire, and maintain our Nation's defense capability. Those responsible for defense transformation—including DoD civilian employees—anticipate the future and, where possible, help create it. The Department continues to implement new capabilities to meet tomorrow's threats as well as those of today. </P>
                    <P>The National Security Personnel System (NSPS) is a key pillar in the Department of Defense's transformation. NSPS was established to provide a flexible and contemporary civilian personnel system that is essential to the Department's efforts to create and maintain an environment in which the DoD Total Force thinks and operates as one cohesive unit. </P>
                    <P>DoD civilians are unique in Government. They are an integral part of an organization that has a military function. DoD civilians complement and support the military around the world in every time zone, every day. Just as new threats, new missions, new technologies, and new tactics are changing the work of the military, they are changing the work of our entire civilian workforce as well. To continue to support the interests of the United States in the current national security environment—where unpredictability is the norm and greater agility the imperative—civilians must be an integrated, flexible, and responsive part of the Total Force team. </P>
                    <P>The Federal personnel system in use by much of the Department and the Federal Government is based on 20th century assumptions about the nature of public service and cannot adequately address public service requirements in the 21st century national security environment. Although this personnel system is based on important core principles, the principles are manifested in an inflexible, one-size-fits-all system of defining work, hiring staff, managing people, assessing and rewarding performance, and advancing personnel. The inherent weaknesses of this system make support of DoD's mission complex, costly, and ultimately risky. The pay and movement of personnel is linked to outdated, narrowly defined work definitions with inadequate means of making distinctions in pay between high and low performers. </P>
                    <P>Recognizing this, NSPS is designed to provide a more flexible, mission-driven system of human resources management that retains core principles while providing a more cohesive Total Force. Additionally, the Department's 28 years of experience with transformational personnel demonstration projects, covering approximately 30,000 DoD employees, has demonstrated that fundamental change in personnel management results in individual career growth and opportunities, workforce responsiveness, and innovation. All of these things multiply mission effectiveness. </P>
                    <P>The immense challenges facing DoD today support the continuation of this civilian workforce transformation. Civilian employees are being asked to assume new and different responsibilities, take more risk, and be more innovative, agile, and accountable than ever before. It is critical that DoD supports the entire civilian workforce with modern systems—particularly a human resources management system that supports and protects their critical role in DoD's Total Force effectiveness. The enabling legislation provides the Department with the authority to meet this transformation challenge. </P>
                    <P>More specifically, the law provides the Department and OPM authority to establish a flexible and contemporary civilian human resources management system for DoD civilians. The attacks of September 11 and the continuing war on terrorism make clear that flexibility is not a policy preference. It is nothing less than an absolute requirement, and it must be the foundation of civilian human resources management. </P>
                    <P>NSPS promotes a performance culture in which the performance and contributions of the DoD civilian workforce are more fully recognized and rewarded. The system provides the civilian workforce a contemporary pay-banding construct which includes performance-based pay. This allows for the establishment of more competitive salaries and the ability to adjust salaries based on various factors, to include labor market conditions, performance, as well as changes in employee duties. </P>
                    <P>
                        In other words, NSPS provides a more flexible HR management system to attract skilled, talented, and motivated people, while also retaining and improving the skills of the existing workforce. The system retains the core values of the civil service while 
                        <PRTPAGE P="56345"/>
                        allowing employees to be paid and rewarded based on performance, innovation, and results. It also provides employees with greater opportunities for career growth and mobility within the Department. DoD leadership will ensure that supervisors and employees understand NSPS and can function effectively within it. 
                    </P>
                    <P>The NSPS pay and classification system provides a more flexible support structure that helps attract skilled and talented workers, retain and appropriately reward current employees, and create opportunities for civilians to participate more fully in the total integrated workforce. A pay-banding structure replaced the artificial limitations created by the previous pay and classification systems. With broad pay bands, the Department is able to move employees more freely across a range of work opportunities without being bound by narrowly described work definitions. The pay structure is more responsive to market conditions. The Department is able to adjust rate ranges and local market supplements based on variations relating to specific occupations, rather than using a one-size-fits-all approach. Labor market conditions also are considered when making pay-setting decisions. As prescribed in the enabling legislation, NSPS better links individual pay to performance using performance rather than time on the job to determine pay increases. </P>
                    <P>Despite the professionalism and dedication of DoD civilian employees, the limitations imposed by the Governmentwide Federal personnel system often prevent managers from using civilian employees effectively. This causes the Department to sometimes use military personnel or contractors when civilian employees are the best choice to accomplish the task. The Federal personnel system limits opportunities for civilians at a time when the role of DoD's civilian workforce includes more significant participation in Total Force effectiveness. NSPS generates more opportunities for DoD civilians by providing an incentive for managers to turn to them first when certain vital tasks need doing. This frees uniformed men and women to focus on matters unique to the military. </P>
                    <P>A key to the continued success of NSPS is ensuring that the system is perceived as being fair,  i.e., establishing a trust between employees and supervisors. The Department's mission cannot be accomplished without the civilian workforce. NSPS recognizes that employees more readily exercise personal responsibility and sustain a high level of individual performance and teamwork when they perceive that the system and their supervisors are fair. The Department and the Office of Personnel Management have addressed fairness in NSPS in several dimensions: system design; the right to seek review of important categories of management decisions; workforce access to information about system provisions, processes, and decisions criteria; and accountability mechanisms. </P>
                    <P>NSPS regulations and implementing issuances include safeguards against arbitrary actions. Examples include written performance expectations, multi-level reviews of performance plans expectations and performance rating and payout decisions, and mandatory within-grade increase buy-in for all employees who are moved to NSPS via management-directed actions. In addition, NSPS continues employees' and labor organizations' rights to challenge or seek review of key decisions. For example, non-bargaining unit employees will be able to request reconsideration of their job objective rating or their rating of record through an administrative grievance procedure. Bargaining unit employees use a negotiated grievance procedure to challenge matters related to their rating of record. Employees must be notified in advance of a proposed adverse action, be given time and opportunity for reply, and be given a decision notice that includes the reasons for the decision in accordance with Governmentwide adverse action and employee appeal rules. Labor organization officials may file unfair labor practices claims or grievances. Labor organizations may seek collective bargaining on NSPS implementation under Governmentwide labor relations rules. </P>
                    <P>The Department and Components make information about NSPS rules, policies, and practices readily available to the workforce in the form of published regulations, published implementing issuances, local level instructions, training, and other sources. </P>
                    <P>The last dimension of accountability for fair decisions and practices under NSPS builds on human capital management mechanisms beyond NSPS, and on internal NSPS provisions. First, there are human resources management accountability reviews within the Department that identify and address issues regarding the observance of merit system principles and regulatory and policy requirements, including those established under NSPS. In addition, the Department monitors the outcomes of administrative and negotiated grievances, performance rating reconsiderations, equal employment opportunity complaints, and whistleblower complaints to correct chronic problems and particular failings. </P>
                    <P>Second, NSPS program evaluation findings enable the Secretary and the OPM Director to determine whether the design of NSPS and the pattern of its results meet statutory requirements like fairness and equity and the specific performance expectations for a credible and trusted system. Section 9901.107 of this rule identifies the requirement for an NSPS program evaluation. A robust and long-term NSPS program evaluation plan of studies and reviews, transactional data analyses opinion surveys, and other evaluative methods has been fielded. </P>
                    <P>Fairness in NSPS is not a specific thing, but rather an intrinsic quality built into the design of a flexible human resources management system—one to be accounted for during reviews and evaluations of NSPS operations and decisions. </P>
                    <HD SOURCE="HD1">II. The Need for Change </HD>
                    <P>The Department's experience operating under the current NSPS regulations as well as the 28 years of experience with transformational personnel demonstration projects, covering nearly 30,000 DoD employees, has shown that fundamental change in personnel management has a positive impact on individual career growth and opportunities, workforce responsiveness, and innovation; all these things enhance mission effectiveness. </P>
                    <P>
                        Public Law 108-136 amended title 5, United States Code, to provide the Department with the authority to meet this transformation challenge through development and deployment of NSPS. Public Law 110-181, while amending Public Law 108-136, continues to promote a performance culture in which the performance and contributions of the DoD civilian workforce are linked to strategic mission objectives and are more fully recognized and rewarded. It also retains flexibilities to streamline the method for classifying positions and to provide a more flexible support structure for both pay and classification in order to help attract skilled and talented workers; retain and appropriately reward current employees; respond to DoD mission requirements; and create opportunities for employees to participate more fully in the total integrated workforce. The System offers the more than 181,000 currently covered employees a contemporary pay banding construct, which includes performance-based pay. NSPS allows the Department to be more 
                        <PRTPAGE P="56346"/>
                        competitive in setting salaries and to adjust salaries based on factors such as labor market conditions, performance, and changes in duties. The updated HR management system rules more specifically govern how retained classification, compensation, and performance management flexibilities will be implemented. The greater level of detail reflects a continued commitment to greater transparency regarding provisions of Pub. L. 110-181 and system improvements in light of operational experience with NSPS. The System retains the core values of the civil service, including merit system principles and veterans' preference, and allows employees to be paid and rewarded based on performance, innovation, and results. 
                    </P>
                    <HD SOURCE="HD1">III. Significant Changes to the Original Law </HD>
                    <P>The original NSPS statute was enacted on November 24, 2003, and provided the Secretary of Defense, in regulations jointly prescribed with the Director of OPM, the authority to establish a flexible and contemporary civilian personnel system called the National Security Personnel System. This new civilian personnel system was intended to cover most of the approximately 700,000 DoD civilian employees, including blue-collar employees. </P>
                    <P>Among its features, it provided authority to establish a pay-for-performance system that recognizes and rewards employees based on performance and contribution to the mission; a new pay-banding system to replace the General Schedule (GS); a simplified job classification process and flexible processes to assign new or different work; streamlined hiring processes and the ability to offer more competitive, market-sensitive compensation; improved workforce shaping procedures that reduce disruption with greater emphasis on performance as a factor in retention; expedited disciplinary and employee appeals processes for faster resolution of workplace issues, while preserving due process rights of employees; and a labor-management relations system that recognized DoD's critical national security mission and the need to act swiftly to execute that mission, while preserving collective bargaining rights of employees. The changes to labor relations included the ability to negotiate at the national level instead of negotiating with more than 1,500 local bargaining units, and the ability to establish a new independent third party to resolve labor relations disputes in DoD. </P>
                    <P>The National Defense Authorization Act of 2008 (Pub. L. 110-181, January 28, 2008) amended 5 U.S.C. 9902, retaining authority for performance-based pay and classification and compensation flexibilities, but substantially modifying other NSPS authorities. The law, among other things—</P>
                    <P>• Brings NSPS under Governmentwide labor-management relations rules. </P>
                    <P>• Excludes Federal Wage System (blue collar) employees from coverage under NSPS. </P>
                    <P>• Requires DoD to collectively bargain procedures and appropriate arrangements for bringing DoD bargaining unit employees under NSPS prior to conversion of these employees. </P>
                    <P>• Brings NSPS under Governmentwide rules for disciplinary actions and employee appeals of adverse actions. </P>
                    <P>• Brings NSPS under Governmentwide rules for workforce shaping (reduction in force, furlough, and transfer of function). </P>
                    <P>• Requires that this regulation be considered a major rule for the purposes of section 801 of title 5, United States Code, with advance Congressional reporting for OPM/DoD jointly-prescribed NSPS regulations. </P>
                    <P>• Gives these regulations the status of Governmentwide rules for the purpose of collective bargaining under chapter 71 when these rules are uniformly applicable to all organizational or functional units included in NSPS. </P>
                    <P>• Mandates that all employees with a performance rating above “unacceptable” or who do not have current performance ratings receive no less than sixty percent of the annual Governmentwide General Schedule pay increase (with the balance allocated to pay pool funding for the purpose of increasing rates of pay on the basis of employee performance). </P>
                    <P>• Limits NSPS conversions to no more than 100,000 employees per year and eliminates the requirement for the Secretary of Defense to determine if the performance management system meets key parameters before increasing NSPS coverage to more than 300,000 employees. </P>
                    <P>Based on the changes Public Law 110-181 made to section 9902 of title 5, the revised rule deletes subparts E, F, G, H, and I (dealing with staffing, workforce shaping, adverse actions, appeals, and labor relations, respectively) of the current NSPS regulations. </P>
                    <P>Public Law 110-181 also amended section 9902 by modifying the authority to conduct national-level bargaining and retains the rights of employees to organize, bargain collectively and participate through labor organizations of their own choosing in decisions that affect them, subject to any exclusion from coverage or limitation on negotiability established pursuant to law. It extends and expands exclusions from NSPS coverage for certain DoD laboratories through October 1, 2011. Some of these laboratories operate under demonstration project authorities which provide their own pay-for-performance systems. </P>
                    <P>In establishing the revised System, only certain provisions of title 5, United States Code, may be waived or modified by DoD and OPM: </P>
                    <P>• Chapter 43 (dealing with performance management); </P>
                    <P>• Chapter 51 (dealing with General Schedule job classification); </P>
                    <P>• Chapter 53 (dealing with pay for General Schedule employees and pay for certain other employees), except for certain sections for which waiver or modification is barred by law; and </P>
                    <P>• Subchapter V of chapter 55 (dealing with premium pay), except sections 5544 (dealing with prevailing rate employees) and 5545b (dealing with firefighter pay). </P>
                    <P>Finally, Public Law 110-181 has a significant effect on the content of the current regulations governing NSPS. Previous legislation authorizing NSPS permitted the promulgation of regulations outlining a framework for NSPS. Implementing issuances provided the detail lacking in the regulatory framework. Taken together, the regulations and the implementing issuances formed the structure of NSPS. However, Public Law 110-181 eliminated the previous legislation's exclusive statutory collaboration process for employee representatives to participate in design and implementation of NSPS. Public Law 110-181 mandated the Governmentwide labor relations system in title 5, chapter 71, for NSPS and conferred the status of Governmentwide rule on regulations governing NSPS. Given these new provisions, much of the structure of NSPS must be established in regulation, rather than through the collective bargaining process, for purposes of uniformity and consistency of the operation of NSPS, much like the Governmentwide regulations that establish the structure of the General Schedule. </P>
                    <HD SOURCE="HD1">IV. Two Years of Operational Experience Under NSPS </HD>
                    <P>
                        In order to provide consistency and uniformity of application throughout the Department, certain NSPS features 
                        <PRTPAGE P="56347"/>
                        previously described in DoD implementing issuances have been incorporated into this regulation. DoD now has more than 2 years of experience with these features and has determined that they effectively support key performance parameters of NSPS. In addition, the regulation includes modifications made to NSPS as a result of operational lessons learned over the last two years. 
                    </P>
                    <HD SOURCE="HD2">A. Classification </HD>
                    <HD SOURCE="HD3">Effective Date of Classification of Position </HD>
                    <P>The regulation now provides specific details for entitlement to retroactive effective date of a classification decision. While the prior regulation provided for both a classification reconsideration process and a retroactive effective date, more detail has been added to provide for a uniform and consistent application. </P>
                    <HD SOURCE="HD2">B. Compensation </HD>
                    <P>The regulation modifies rules governing the current compensation structure by removing the link between increases in the minimum rate of the rate range and across-the-board increases. This change enables more flexibility in responding to labor market changes that may impact the lower end of a pay range for an occupation, but not the middle or upper ranges. Also, discretionary authority is now provided to give targeted general salary increases to designated occupational series within a pay band. This flexibility enables management to adjust pay to recognize market forces when the pay band itself is market competitive but, due to rapidly changing markets, the current salaries paid to employees in certain occupations are not. </P>
                    <HD SOURCE="HD2">C. Pay Administration </HD>
                    <P>Several changes have been made in the area of pay administration. Pay-setting flexibilities have been expanded to permit discretionary within-grade increase buy-ins when employees from outside of NSPS move to an NSPS position. Safeguards have been incorporated for employees who are moved to NSPS via management-directed actions. In these cases, the regulation now specifies a required within-grade increase buy-in. A significant level of detail has been added to describe how pay is administered upon promotion, reassignment, reduction in band and appointment to the Federal service. Most of this detail reflects the pay-setting rules that have proven effective during the past 2 years in the operation of NSPS. </P>
                    <P>The regulation retains management's flexibility to set pay within a given range, but provides safeguards by placing limitations on the factors management may use in exercising its discretion as well as establishing pay increase limits that cannot be exceeded without higher-level review. There have also been some modifications to pay-setting practices based on DoD's experience with the System. Most significantly, pay-setting rules for employees moving into NSPS from other systems or moving from NSPS positions covered by targeted local market supplements have been revised. Pay for these employees was previously set using “base salary.” Pay will now be set using “adjusted salary” (includes base salary plus any applicable locality pay, special rate supplement, or other equivalent supplement) and any physicians' comparability allowance payable for the position held prior to the reassignment. In these cases, when the new position is in a different location, a geographic pay conversion will be processed. These rules allow management to set pay more competitively and equitably compensate employees by permitting pay to be set in a manner that prevents a loss in adjusted salary in certain circumstances. Further changes in NSPS pay-setting rules include the discretion to adjust the rate of pay of a teacher moving into NSPS up to 20 percent to take into account the shorter work year incorporated in the annual rate of a teacher paid under 20 U.S.C. 901. </P>
                    <HD SOURCE="HD3">Pay Retention </HD>
                    <P>Pay retention rules have been modified to provide a “grandfather” clause for employees who are covered by General Schedule grade and pay retention rules at the time they are converted into NSPS. These employees will not be subject to the 104-week limit on pay retention. They will be entitled to pay retention indefinitely, subject to specifically identified pay retention termination events. Much detail has been added in the area of pay retention to identify circumstances for which pay retention is mandatory, eligibility requirements for optional pay retention, and events leading to termination of pay retention. These rules reflect current practices under NSPS. </P>
                    <HD SOURCE="HD3">Accelerated Compensation for Developmental Positions (ACDP) </HD>
                    <P>“Treatment of Developmental Positions” (§ 9901.345) has been modified to specify criteria for Accelerated Compensation for Developmental Positions (ACDP) increases, identify the range of pay increases that are permitted under this discretionary authority, and to expand the discretionary use of ACDP to employees in developmental or trainee level positions assigned to the lowest pay band of a nonsupervisory pay schedule and trainee level positions or positions assigned to the Student Career Experience Program. To date, this authority has been available only to employees in developmental or trainee level positions in professional and analytical occupations. The change provides additional flexibility in recognition of pay progression patterns in other occupations. </P>
                    <HD SOURCE="HD3">Premium Pay </HD>
                    <P>A critical feature of NSPS compensation is the ability to modify premium pay in response to current and future needs. This flexibility facilitates the Department's ability to accomplish its diverse mission. The revised regulation incorporates rules governing NSPS premium pay. Premium pay includes pay such as overtime pay, compensatory time off, holiday, Sunday, and standby pay. Among the premium pay features unique to NSPS are on-call premium pay for health care personnel in specified circumstances, pay for weekend duty for health care personnel, and foreign language proficiency pay. For the most part, the regulations reflect current premium pay policies under NSPS, which include certain modifications to the standard title 5 premium pay laws and regulations to address unique DoD mission requirements and differences in the NSPS classification and pay structure. </P>
                    <HD SOURCE="HD3">Conversion/Movement Out of NSPS </HD>
                    <P>Regulations have been added to provide a process for converting employees out of NSPS when their position is removed from coverage under the System and to provide a “virtual GS grade” to employees who leave their NSPS position to accept employment in a General Schedule position. These rules promote more equitable pay setting upon moves to the General Schedule pay system. </P>
                    <HD SOURCE="HD2">D. Performance and Pay Pool Management </HD>
                    <HD SOURCE="HD3">Higher Level Review </HD>
                    <P>
                        The revised regulation more specifically outlines safeguards to ensure the NSPS performance and pay pool management system is fair and equitable based on employee performance. For example, under subpart D, the revised regulation now 
                        <PRTPAGE P="56348"/>
                        provides for a higher level review of performance expectations and recommendations for ratings of record, share assignment, and payout distribution. This review helps ensure that assigned employee objectives are reviewed for appropriateness and consistency within and across the organization and/or pay pool as well as employee ratings, share assignments, and payout distribution. These safeguards help ensure equity in performance payouts. 
                    </P>
                    <HD SOURCE="HD3">Calculating Annual Payout </HD>
                    <P>Rating levels, share assignment ranges, and rounding rules for conversion of raw performance scores are also specified in the revised regulation, as well as formulas for share values and calculation of performance payouts. The language also clarifies the intended application of a common share value (expressed as a percent of pay) throughout an entire pay pool, to include all sub pay pools. This further preserves equity across a pay pool. </P>
                    <HD SOURCE="HD3">Flexibility in Extending Performance Appraisal Periods </HD>
                    <P>The authority to extend individual performance appraisal periods to enable employees to complete minimum periods is specified as well as limitations on this authority. By specifically providing for extension of individual rating cycles, valued performers and higher-performing employees moving to NSPS positions can more quickly benefit from the NSPS performance-based pay features. </P>
                    <HD SOURCE="HD3">Pay Pools </HD>
                    <P>The pay pool concept has also been further defined in this regulation by providing parameters for pay pool composition and specifying the roles of pay pool officials within the pay pool process. </P>
                    <P>Much thought was given to achieving the “right” balance between safeguards and management flexibility. For example, although pay pool share ranges have been specified for each rating level, management still has the flexibility to determine assignment of shares within that range. System safeguards were added to ensure fairness, equity, and a performance focus by expressly stating and limiting the factors which may be used in the determination of share assignment. Similarly, management still retains the flexibility and authority to determine the distribution of a performance payout between base salary increase and bonus or a combination thereof. However, to ensure safeguards within the system, the factors management may use in exercising this authority have also been expressly defined and limited to ensure fairness, equity, and a performance focus. While pay pool funding is still determined by management, higher-level reviews have been required to provide internal controls. Additional safeguards added include a uniform approach to handling performance payouts for employees who leave a pay pool after the end of the performance period, but before the date of the payout. Finally, to promote transparency of the pay pool process, a requirement has been added for organizations to share with employees the average rating, ratings distribution, share value (or average share value), and average payout (expressed as a percentage of base salary) at the completion of the performance payout process. </P>
                    <HD SOURCE="HD3">Reconsideration Process </HD>
                    <P>Employee performance reconsideration opportunities have been expanded to permit reconsideration of individual performance objective ratings in addition to the overall rating of record. This change recognizes that many pay pools use raw performance scores as a guide in determining how many shares to assign to employees. Since raw performance scores may be impacted by individual performance objective ratings, the ability to request review of individual performance objectives enables employees to seek redress on all performance rating decisions affecting their pay. </P>
                    <HD SOURCE="HD2">E. Other Changes </HD>
                    <P>Other changes reflected in this regulation include language providing salary increases for employees who did not meet the minimum period of performance due to an approved paid leave status or performance of labor activities on “official time.” These pay adjustments will be based on the modal rating of a pay pool. Likewise, provisions have been made to adjust the pay of employees returning from temporary assignments outside of NSPS or returning from long-term training for which no NSPS performance plan was assigned. These changes ensure that employee pay is not harmed by the inability to meet a minimum performance period or inability to rate performance while employees either exercise statutory leave entitlements or fulfill other roles important to the organization. </P>
                    <P>Finally, the regulations in subpart D (dealing with performance management) permit limited coverage under NSPS pay-setting and classification flexibilities for employees who are appointed for less than 90 days. Providing access to NSPS pay-setting flexibilities for these positions enhances DoD's competitive position in the labor market when hiring temporary employees for 90 days or less. </P>
                    <HD SOURCE="HD1">V. Response to Public Comments </HD>
                    <HD SOURCE="HD2">A. Major Issues </HD>
                    <P>
                        The proposed rule was published in the 
                        <E T="04">Federal Register</E>
                         on May 22, 2008. The public comment period concluded June 23, 2008. In response to the proposed rule, the Department received 526 comment submissions during the 30-day public comment period. In reviewing the comment submissions, we discerned several recurring themes that spanned multiple sections of the proposed regulation. Major issues identified included: (1) Specificity of the regulation; (2) collective bargaining and labor relations; (3) performance and pay pool management; (4) the influence of performance versus market factors on pay; and (5) control points. Because these issues are critical to understanding the objectives of NSPS, as well as its implementation, we have given them particular attention in the following sections of this 
                        <E T="02">Supplementary Information</E>
                        . 
                    </P>
                    <HD SOURCE="HD3">1. Specificity of the Regulation </HD>
                    <P>A significant issue raised in the public comments concerned the level of specificity in the proposed regulation. Some commenters, pointing to a lack of detail regarding specific issues, such as performance management, sought more specificity in the proposed regulation itself as opposed to the Department providing future direction in implementing issuances, which are not open to public comment. However, many of the commenters who weighed in on this issue argued that the proposed regulation is too specific. Commenters suggested that the increased level of detail was written into the proposed regulation not to improve the clarity of the regulation, but to preclude negotiation with labor organizations. Labor organization representatives argued that because DoD, under the National Defense Authorization Act for Fiscal Year 2008 (NDAA 2008), no longer has authority to establish a labor relations system under its control, the Department is attempting to write regulations as narrowly as possible to avoid the collective bargaining process. </P>
                    <P>
                        Interestingly, during the public comment period for the 2005 regulation, a large number of commenters recommended that the regulation include far greater specificity, with 
                        <PRTPAGE P="56349"/>
                        numerous commenters stating that they were unable to provide substantive comments without more information. Some additional specificity was written into the final 2005 regulation in response to these comments, but it retained its original goal of establishing a general policy framework to be supplemented by detailed implementing issuances. 
                    </P>
                    <P>This regulation of necessity includes more specificity than the 2005 regulation in order to preserve uniformity and consistency of application of NSPS in the changed statutory environment created by Public Law 110-181. The uniform and consistent application of NSPS is important to ensure equitable treatment of all employees, whether bargaining unit or non-bargaining unit; for ease of movement of employees across components and organizations; and to achieve efficiencies in support systems such as automated performance management tools and training. Public Law 110-181 restored the Governmentwide labor relations coverage of title 5, chapter 71, to NSPS employees and conferred the status of Governmentwide rule upon this NSPS regulation. It also removed the statutory collaboration process which ensured uniformity and consistency and was the exclusive process for employee representative involvement in the design and implementation of NSPS. Given those provisions, OPM and DoD concluded the 2005 regulatory framework and detailed implementing issuance construct created unwarranted risk to the goal of uniform and consistent application of NSPS to both bargaining unit and non-bargaining unit employees. With much of the operational core of NSPS in its implementing issuances subject to collective bargaining, we concluded the likely outcome of bargaining over the various components of NSPS would be multiple versions of NSPS for bargaining unit employees (there are more than 1,500 local bargaining units in DoD) and one NSPS for non-bargaining unit employees. Therefore, OPM and DoD chose to incorporate sufficient detail in this regulation, under the legislative grant of Governmentwide regulation status, to preserve the uniformity and consistency of a single NSPS. The regulation provides a standardized, yet flexible, DoD NSPS environment that promotes the growth of all employees and improves management's ability to manage the workforce. Labor organizations still retain collective bargaining rights regarding NSPS under title 5, chapter 71. In fact, labor organizations may seek to collectively bargain implementation of NSPS prior to implementation for bargaining unit employees to the same extent bargaining occurs on implementation of other Governmentwide regulations across the Federal Government. </P>
                    <HD SOURCE="HD3">2. Collective Bargaining and Labor Relations </HD>
                    <P>In addition to their concerns on how the specificity of the regulations affects the collective bargaining rights, labor organizations made numerous comments in each subpart that various matters should be subject to collective bargaining under 5 U.S.C. chapter 71. In some cases these matters are not subject to collective bargaining today for bargaining unit employees outside NSPS as such matters are covered by law. In other cases, these matters are limited in collective bargaining because they are covered by Governmentwide regulations encompassing these employees. There were also various suggestions to include language throughout the regulations that collective bargaining rights exist on certain specified matters, even where the scope of collective bargaining rights is actually more limited than what is suggested by the labor organizations. </P>
                    <P>DoD is committed to fulfilling its obligation to bargain in good faith consistent with Governmentwide labor relations rules under 5 U.S.C. chapter 71 and the requirements of 5 U.S.C. 9902 and section 1106(b) of Public Law 110-181. However, it is appropriate that the Department seek uniformity and consistency in its NSPS employment practices through issuance of regulations. We do not believe it is necessary to repeat throughout the regulations a statement regarding any statutory collective bargaining rights and have not adopted the suggestion. This does not occur today in other Governmentwide regulations or agency policies. However, we have added a clarifying general statement in subpart A regarding collective bargaining obligations prior to converting bargaining unit employees to NSPS. </P>
                    <HD SOURCE="HD3">3. Performance and Pay Pool Management </HD>
                    <HD SOURCE="HD3">Background </HD>
                    <P>The Department designed NSPS to be a robust performance management system in recognition of the increased importance of performance in making pay and retention decisions. NSPS uses a multi-level appraisal system that makes distinctions in levels of employee performance and links employee achievements, contributions, knowledge, and skills to organization results. NSPS also allows the Department to better recognize and support team contributions and accomplishments. The System ensures that performance expectations are clearly communicated to employees and are linked to the organization's strategic goals and objectives. This provides the ability to recognize valid distinctions in performance and reward employees based on those distinctions, which will foster a high-performance culture within the Department. </P>
                    <P>NSPS modifies the way DoD employees are paid. NSPS bases individual pay increases on performance instead of primarily on tenure and time-in-grade, i.e., the emphasis is on quality of results achieved as opposed to length of experience. In addition, this system is far more market-sensitive. Both of these goals are met through the changes in the classification, pay, and performance management systems. </P>
                    <P>We believe the Department's pay-for-performance system is essential to DoD's ability to attract skilled and talented workers; retain and appropriately reward current employees; respond to DoD mission requirements; and create opportunities for employees to participate more fully in the total integrated workforce. </P>
                    <P>Performance and pay pool management inspired a large number of comments during the public comment period. In fact, many commenters raised issues that related to both subparts C and D, since pay administration and performance management are so closely aligned. In reviewing the comments that addressed aspects of performance management under the proposed regulation, we identified seven recurring issues. These issues are addressed in the following paragraphs. </P>
                    <HD SOURCE="HD3">Fairness </HD>
                    <P>Many commenters expressed concerns about fairness in operation of the NSPS performance management system. Whether they characterized their concern as “favoritism,” “cronyism,” “nepotism,” or the euphemism “good ol' boy” system, commenters expressed concerns that NSPS could or would present opportunities for unfairness within the performance appraisal and overall performance management system. These commenters feared supervisors and Pay Pool Managers would assign ratings based on personal preferences and relationships unrelated to performance. </P>
                    <P>
                        From the beginning, NSPS was designed to be consistent with specific 
                        <PRTPAGE P="56350"/>
                        guiding principles. Among the principles emphasized in the performance management process are fairness, credibility, and transparency, as well as adherence to merit system principles. The regulation establishes many safeguards—or checks and balances—specifically designed to guard against favoritism, cronyism, and unfair practices. 
                    </P>
                    <P>First and foremost, the performance management system design features uniform performance criteria across NSPS (see SC 1940 of NSPS implementing issuances). By using uniform criteria, NSPS ensures employees performing similar categories of work are evaluated using the same tools of measurement. To ensure that the measurement tools are interpreted consistently across the organization and in a manner free from favoritism, cronyism, or other inappropriate consideration, NSPS provides multiple-level reviews of recommended ratings, share assignments, and payout distribution determinations. Not only does the supervisor/rating official offer a recommended rating of record based on an overall assessment of the employee's accomplishments (§ 9901.412(b)), but these recommended ratings receive a higher-level review—a requirement identified and added to the revised regulation in § 9901.412(c) and made effective via implementing issuances. Following the higher-level review, a panel of senior leaders (i.e., the Pay Pool Panel) reviews and reconciles ratings within a pay pool (§ 9901.412(f)). In reconciling ratings, share assignments and payout distribution recommendations, the panel compares the employee's accomplishments (via supervisory assessments and optional employee self assessments) to job objectives and standard rating criteria to ensure that the same understanding of performance criteria has been applied to employees across a pay pool. The Pay Pool Panel considerations do not include a pre-established distribution of ratings as a factor in determining the rating of record. This is because NSPS regulations also prohibit forced distribution of ratings (§ 9901.412(a)). As opposed to a forced alignment of employee ratings against a particular distribution pattern, employee performance reflects a measurement of “what” an employee accomplished (and “how”) against standardized performance measurements. The employee also has a voice in how his or her work is viewed via the opportunity to write a self-assessment of what was accomplished by the employee and in what manner objectives were achieved during the performance cycle. Such assessments become part of the record that is forwarded to the higher-level reviewer and Pay Pool Panel. Checks and balances such as those described above form the safeguards for fairness and equity built into the regulation and the performance management system. </P>
                    <P>As with the multi-level review for employee ratings of record, NSPS also provides for reviewing performance plans at multiple levels. First, supervisors are responsible for making sure that performance objectives accurately reflect an employee's work and for engaging employees in that determination (§ 9901.406). Employees participate in the development of performance expectations via conversations and written communication with their supervisors (§ 9901.406(g)). Second, there is a review of performance expectations at a higher level to ensure that assigned employee objectives are consistent and equitable with similar positions within and across the organization (§ 9901.406(h)). </P>
                    <P>In addition to the checks and balances outlined in the preceding paragraphs, NSPS contains four other important features intended to contribute to the sustainment of a fair, credible, and transparent system. First, supervisors and managers will be held accountable in a specific job objective for effectively managing the performance of employees under their supervision and will be assessed and measured on their performance against this objective (§ 9901.406(d)). There is a connection between administration of the performance management system and supervisory performance ratings and, consequently, a supervisor's pay. Second, DoD is committed to extensive training, both initial and ongoing, for supervisors, managers, and employees so that they understand the requirements of the performance management system. For supervisors and managers, in particular, training is focused on how to establish and communicate performance expectations, how to assess employee performance, and how to appropriately translate that assessment into pay adjustments. Third, there are various review and evaluation processes designed to monitor the implementation of NSPS and identify inconsistent, unfair treatment of employees so that these situations, if they occur, can be remedied in a timely manner. As a final check and balance, employees may also request reconsideration of ratings of record as well as ratings for individual job objectives under § 9901.413. </P>
                    <P>To ensure that employees are treated fairly, there are rules to guard against arbitrary actions, enable employees to challenge or seek review of key decisions, and for setting up accountability mechanisms. All of these safeguards and checks and balances are monitored during regular and recurring reviews and evaluations of NSPS at multiple levels within the Department. </P>
                    <HD SOURCE="HD3">Uniformity and Consistency </HD>
                    <P>Some commenters questioned whether performance would be measured uniformly and consistently among pay bands, occupational areas, and Components. While there is opportunity for some aspects of implementation of NSPS performance management to be handled flexibly to accommodate different circumstances, NSPS is designed to ensure uniformity and consistency in the most important core features of performance management. For example, the regulation mandates a uniform summary rating level pattern (§ 9901.405(b)(5)) and share assignment range for each rating level (§ 9901.342(f)), and it provides common formulas for determining the share factor value and payout within each pay pool (§ 9901.342(g)). </P>
                    <P>The NSPS implementing issuances and NSPS performance tools further institutionalize uniformity and consistency via the establishment of standardized NSPS performance measures applied across NSPS. For example, NSPS uses standardized performance criteria, which evaluate “what” was accomplished (also known as performance indicators), as well as standardized contributing factors and benchmark descriptors, which serve to measure “how” an objective was accomplished (SC 1940). The use of standardized criteria and rules helps to ensure consistency across NSPS. </P>
                    <HD SOURCE="HD3">Transparency </HD>
                    <P>
                        Several commenters expressed concern that ratings and performance payout determinations are made “behind closed doors,” and commenters questioned whether the NSPS system meets its stated goal of transparency. While it is true that Pay Pool Panels deliberate in private, this is necessary to protect the privacy of employees as individuals as well as to provide an atmosphere for robust performance management discussion. Nevertheless, there are a number of requirements in the system that helps preserve transparency outside of the pay pool deliberation. The regulation adds language to specify requirements for sharing of pay pool information to NSPS 
                        <PRTPAGE P="56351"/>
                        employees (§ 9901.342(g)(10)). In addition, through implementing issuances (SC 1940), NSPS requires notice to employees of additional pay pool related information. This information may include the membership and composition of the pay pool to which the employee belongs; projected pay pool funding amounts; rules for making share assignment and payout distribution determinations; percentage of pay pool funding to be applied to bonuses versus increases to base salary; criteria for Organizational Achievement Recognition (OAR) awards; identity of Pay Pool Manager, Pay Pool Panel members, and Performance Review Authority; and performance indicators and contributing factors. The regulation also specifies that performance expectations (e.g., job objectives) must be communicated to employees in writing (§ 9901.406(b)). Performance measurement criteria are available to all employees through Web sites (e.g., 
                        <E T="03">http://www.cpms.osd.mil/nsps</E>
                        ) and agency implementing issuances. The regulation adds greater detail to performance and pay pool management (such as specifying number of rating levels (§ 9901.405(b)(5)), rounding rules for raw performance scores (§ 9901.405(b)(6)), share ranges (§ 9901.342(f)), factors that may be considered in making a share assignment or payout distribution determination (§ 9901.342(g)), share value and payout formulas (§ 9901.342(g)), minimum criteria for eligibility for a performance payout (§ 9901.342), as well as identification of and procedures for performance payouts for specially situated employees not previously covered in the regulation (§ 9901.342(i)-(l)). 
                    </P>
                    <HD SOURCE="HD3">Premium on Good Appraisal Writing Skills </HD>
                    <P>
                        A few commenters expressed concern that the NSPS system rewards those who can write well, not necessarily those who perform best. Commenters believe that employees who have difficulty communicating their accomplishments in a self-assessment will be at a disadvantage in comparison to good writers, even if their performance level actually exceeds that of the good writers. Another commenter expressed concern that employees are required to write their own appraisals. The written employee self-assessment is optional and is just one of many components of the NSPS performance management system. Another component of the performance management system is that each rating official also prepares a written assessment of employee performance. One of the system safeguards that helps ensure employees are not adversely affected by the “written word” is the requirement that Pay Pool Panels afford a rating official the opportunity to provide further justification before the panel changes a recommended rating of record (§ 9901.412(f)). This requirement provides an opportunity for further explanation as well as that presented in writing. Additionally, to assist both employees and rating officials in the development of written assessments, DoD has developed and made available both classroom and Web-based writing classes (see “iSuccess” training at 
                        <E T="03">http://www.cpms.osd.mil/nsps/training.html</E>
                        ). Also, DoD has made available guidance in the form of writing tips and “lessons learned” by other organizations that have implemented NSPS to help employees and rating officials write effective self-assessments, performance plans, and performance assessments. 
                    </P>
                    <P>Finally, mock pay pool exercises offer both employees and rating officials the opportunity to practice their writing skills. A mock pay pool exercise is a way for organizations to understand the pay pool process. During the exercise, employees may submit written self-assessments and rating officials may submit supervisory assessments for consideration by the pay pool panel. Pay pool panels can communicate back to both rating officials and employees the value of those assessments to the appraisal process and make suggestions on how to write such assessments more effectively. Also through mock pay pools, organizations identify ways to improve their process to achieve greater consistency and ensure fairness in ratings and payouts. Past experience has shown that these exercises improve not only participants' familiarity with the process, their understanding of the various aspects of the pay-for-performance system, and the quality of their decisions, but also their writing skills in the context of the performance management system. </P>
                    <HD SOURCE="HD3">Differences Between Grade-Based Systems and NSPS in Rewarding Performance </HD>
                    <P>Commenters noted that the proposed regulation allows organizations with wage grade workers and NSPS employees to reward performance differently, which could result in inequities. We assert differences do not necessarily result in inequities. Without doubt, there are differences between the design of the NSPS personnel and performance award system and the Federal Wage System (FWS) personnel and performance management systems. These differences with the FWS existed even when NSPS positions were still covered by the General Schedule (GS). They are a result of overall differences in the compensation systems. For example, GS grades have 10 steps, with waiting periods from one to three years between steps. Each step represents approximately a 3 percent increase in base pay awarded primarily based on seniority. The FWS has only five steps, but much shorter waiting periods (six months to two years) and larger increases (approximately 4 percent increase in base pay). Like the GS, the FWS also awards steps primarily based on seniority. The basis for pay progression under both GS and FWS systems is primarily a combination of seniority-based pay progression in the form of step increases, promotions, and cost of labor (e.g., locality pay). Performance pay, when awarded, is typically paid out via bonuses. In contrast, the design of the NSPS compensation and classification architecture has no step increases and fewer promotions. The express purpose of this design decision is to redirect pay, formerly paid out based, in part, on seniority, toward rewarding and encouraging performance (i.e., performance-based pay). Therefore, under NSPS, pay progression primarily occurs via performance-based increases. In the absence of step increases and promotions to grades that no longer exist, NSPS applies civilian pay increase dollars that would have been expended on those pay progression methods to performance-based increases and Accelerated Compensation for Developmental Positions (ACDP). In redirecting the seniority-based and promotion-based pay increases under the General Schedule to performance pay, it is appropriate that performance awards under NSPS be greater than performance awards under systems that do not redirect step increases and promotions associated with more defined levels of work to performance. The differences between NSPS and grade-structured systems are simply differences rather than inequities. Therefore, we made no attempt to align NSPS performance rewards to those of other personnel systems. In so doing, we reiterate the belief that Congress and the American people expect their public employees to be paid according to how well they perform, rather than how long they have been on the job. </P>
                    <P>
                        Another commenter expressed an equity concern that NSPS employees may be disadvantaged over General Schedule employees where there is internal competition for reassignment 
                        <PRTPAGE P="56352"/>
                        and promotion to other positions. In particular, the commenter expressed a belief that the NSPS performance appraisal system creates an impression that an employee with a “3” as his or her last rating of record is inferior to a GS employee with all Level 9's. Despite inconsistencies in rating scales across the government (to include pass/fail, NSPS, and 3 and 4 level rating systems, etc.), the employee's record of accomplishment along with appropriate employment references and a copy of the aggregate NSPS rating distribution (available via NSPS web site) should serve to inform prospective employers of the value of a NSPS Level 3 rating of record. 
                    </P>
                    <HD SOURCE="HD3">Communication of Performance Expectations </HD>
                    <P>Commenters also noted that the proposed regulation does not place enough accountability on supervisors to communicate performance expectations. One commenter noted that the proposed regulation does not explicitly require the supervisor to notify the employee of performance expectations. Yet § 9901.406 of the proposed regulation very explicitly states the requirement to communicate performance expectations to employees prior to holding the employee accountable for them (“Performance expectations will be communicated to the employee in writing, prior to holding the employee accountable for them.”). That section further states: “Performance expectations that comprise a performance plan are considered to be approved when the supervisor has communicated the performance plan to the employee in writing.” In addition to the employee requirements stated in § 9901.406(c), § 9901.406(d) states that performance expectations of supervisors and managers additionally will include assessment and measurement of how well supervisors and managers plan, monitor, develop, correct, and assess subordinate employees' performance. Inasmuch as the “planning” phase of performance management is considered to incorporate development and implementation of subordinate employees' performance plans and those plans, per the regulation, are only considered approved once communicated to the employee in writing, the regulation does in fact hold supervisors and managers accountable for communicating performance expectations. </P>
                    <HD SOURCE="HD3">Perceived Administrative Burden </HD>
                    <P>Some commenters objected to the amount of time and resources needed to administer NSPS, particularly the performance management component. Commenters cited the amount of paperwork required under NSPS and the limitations of the NSPS Performance Appraisal Application (PAA) tool. We agree that the design of NSPS and the safeguards built into the system result in increased time demands, especially during the start-up years. However, DoD's experience with Personnel Demonstration Projects indicates that the amount of time required for the same tasks levels off and even decreases as the organization gains experience with the pay pool process. Additionally, as experience and efficiency increase, organizations tend to parlay the process of reviewing individual performance into an examination and driver of overall organizational performance, thus increasing the return on their investment of time. Consequently, we have not altered the requirements, believing that the end result is fairness and consistency—key objectives of NSPS—and the ability to further individual as well as organizational performance. Another commenter indicated that there are an insufficient number of characters available in the PAA to adequately provide self assessment information. We continuously evaluate the PAA tool to improve it to better meet user needs. We have addressed many of the initial limitations of the system and are currently reviewing changes to other features such as the limitation on the number of characters that users can enter into various fields. </P>
                    <HD SOURCE="HD3">4. Performance Versus the Influence of Market Factors on Pay </HD>
                    <P>While a number of commenters supported the idea of a performance-based pay system, some commenters were less supportive of the consideration of non-performance-related factors when setting pay. These commenters objected to the weight given to factors other than performance. For example, one commenter stated: “The factors used in determining if [employees] get a raise or a bonus are * * * complicated and * * * have nothing to do with performance. Employees have no control over many of these factors, which include attrition rates, shortages of skills, and labor market. Obviously, this really isn't a true pay-for-performance system.” In response to this comment—and the many commenters who expressed similar concerns about the use of factors other than “performance” in setting pay—we acknowledge that it is a misperception that compensation under NSPS is based solely on performance. From its inception, NSPS was designed to emphasize both performance pay and compensating employees based on market factors. In the Supplementary Information for the 2005 regulation we said the following about the new system: “The pay structure will be much more responsive to market conditions” and “Labor market conditions will also be considered when making pay-setting decisions. As prescribed in the enabling legislation, the new compensation system will better link individual pay to performance * * * ”. We also said: “As the Department moves away from the General Schedule system, it will become more competitive in setting salaries and it will be able to adjust salaries based on various factors, including labor market conditions, performance, and changes in duties.” </P>
                    <P>The NSPS compensation system, first described in the 2005 NSPS regulation, is designed to fundamentally change the way employees in the Department are paid. First, it allows DoD, after coordination with OPM, to define occupational career groups and levels of work within each career group that are tailored to the Department's missions and components. Second, it gives DoD considerable discretion, after coordination with OPM, to set and adjust the minimum and maximum rates of pay for each of the pay schedules and pay bands within those career groups based on national and local labor market factors and other conditions. Instead of “one size fits all” pay rates and adjustments, NSPS allows DoD to customize those adjustments and optimize valuable but limited resources. This kind of flexibility, which is lacking under the GS and FWS pay systems, enables DoD to allocate payroll dollars to the occupations and locations where they are most needed to carry out the Department's mission. At the same time, NSPS is a system that balances linking individual pay to performance and aligning positions both internally based on position classification and externally based on labor market. </P>
                    <P>
                        The NSPS classification, compensation, and performance management structures are designed to act in tandem to achieve two significant objectives: Reward performance and pay employees consistent with current national and local market conditions. As a result, beyond providing a system for rewarding performance, NSPS is structured to be far more responsive to applicable labor markets than grade-based systems and provides the flexibility needed to quickly adjust to a constantly changing labor market. Some of the mechanisms by which NSPS responds to applicable markets are 
                        <PRTPAGE P="56353"/>
                        decisions involving setting the pay of employees initially hired into NSPS positions, payout distributions between base salary and bonus, establishment of control points, establishment of targeted local market supplements, targeted general salary increases, and the adjustment of pay band minimums and maximums. By utilizing contemporary pay practices to establish a market-sensitive system, DoD is better able to establish itself as an attractive employer in a competitive environment. 
                    </P>
                    <P>Under NSPS, DoD has created a system that allows the flexibility necessary to consider both market factors and performance in making compensation decisions. As a result, DoD is in a better position to attract, retain, and reward a workforce that is able to meet the high expectations set for it by the Department's senior leaders for the purpose of accomplishing the Department's mission—the defense of our nation. </P>
                    <HD SOURCE="HD3">5. Control Points </HD>
                    <P>A number of commenters expressed concerns about control points. Many perceived them as inappropriately limiting employees' potential for salary growth in a pay-banded system where pay is expected to be based on performance. They felt the full pay band salary range should be accessible to every employee in a band and advanced the argument that control points effectively cap a top performer at the control point, subverting the goal of a pay-for-performance system. Others opined that by establishing control points, the merit system principle of equal pay for equal work has been thwarted. The concept of control points is not inconsistent with the goals of a pay-for-performance system which, from the initial design phase of NSPS, envisioned a greater link between pay decisions and an individual's performance. </P>
                    <P>
                        While a statutory requirement exists for NSPS to better link individual pay to performance, the NSPS performance-based features are not intended to result in “performance” trumping all other factors that may be considered in setting pay and pay progression. Unlike the GS and FWS pay systems, which compensate employees primarily on a seniority basis, NSPS requires that many factors be considered in setting pay. For example, the statutory requirements for NSPS specify that the system shall “not waive, modify, or otherwise affect the public employment principles of merit and fitness” set forth in 5 U.S.C. 2301, “* * * including the principles of * * * equal pay for equal work.” Inasmuch as the merit system principle of “equal pay for equal work” further requires that equal pay should be provided for work of equal value, “
                        <E T="03">with appropriate consideration of both national and local rates paid by employers in the private sector and appropriate incentives and recognition * * * provided for excellence in performance</E>
                         [italics added] * * *”, managing pay using either or both market and/or performance-based control points makes sound business management sense and is consistent with statutory requirements. 
                    </P>
                    <P>Another key requirement of NSPS is that it be “flexible and contemporary.” While compensation structures prior to the 1980's were primarily aligned to highly structured classification systems, the need to compete for talented employees who possess the knowledge, skills, abilities and/or competencies associated with 21st century technologies and industries essential to the DoD national security mission requires a shift in emphasis to a market-sensitive compensation strategy in order to respond to quickly changing labor markets. Therefore, NSPS regulations governing control points allow management to consider and balance a variety of factors, in addition to performance, in determining rates of pay and salary progression through a pay band. </P>
                    <P>Control points represent one tool that can be used to manage employees' progression through the bands and can help ensure that only the highest performers move to the upper range of a pay band. Control points also allow management to account for variances in position responsibilities within a pay band. This allows the Department to set pay more consistently with the labor market and to be more effective in attracting and retaining top performers. In fact, several of the DoD demonstration projects have successfully used control points in their pay-for-performance systems. </P>
                    <P>Sometimes, higher parts of a pay band are reserved for the highest of performers; at other times, parts of the pay band are reserved for work or skill combinations not easily acquired for which the labor market pays a higher rate of pay and which management has identified as being important to organizational performance. Therefore, for pay progression to occur beyond an established control point, the employee must meet certain criteria, such as specific work assignments, acquisition of particular competencies, and/or a rating of record at a particular level. With one exception, the restriction on receiving pay increases once a control point is reached is no different from the restriction on increases in basic pay a General Schedule employee experiences once he or she reaches the maximum step of his or her grade. The one exception to this analogy is that the General Schedule employee must be promoted in order to pass the step 10 or maximum rate of the pay range for the grade. In contrast, an NSPS employee may move past a control point subject to meeting the criteria associated with passing that control point. </P>
                    <P>Control points also provide management with the latitude needed to positively impact a variety of pay decisions, such as starting rates, rate ranges, and the size and mix of performance payouts. Control points manage pay progression to reflect duties and responsibilities, labor markets, and/or performance. DoD requires that control points be applied consistently to similar positions in the same pay band and career group within a pay pool. </P>
                    <P>A commenter noted that “pay bands with control points are the GS scale by another name.” Some control points may indeed be similar to the GS grade structure. This may merely reflect a common labor market between the positions assigned those control points and the General Schedule system. As stated earlier, however, there is considerably more room for pay progression within a band than within a GS grade. NSPS employees may move more easily from control point to control point within their assigned band, or other comparable bands. Additionally, unlike the General Schedule employee who reaches the step 10 of his or her GS grade, an employee with a Level 3 or higher rating of record is guaranteed a share of the pay pool and any amount in excess of the control point (or the top of the pay band, if applicable) is paid out as a bonus. </P>
                    <P>Another individual noted that control points can be a factor in determining whether a performance payout is awarded as a bonus or a base salary increase, which could have the effect of reducing retirement benefits, since bonuses are not counted toward retirement in retirement calculations. As under the General Schedule, performance bonuses under NSPS do not count toward retirement. However, they are a means of recognizing and paying for performance when an employee is not eligible for further increases in pay. </P>
                    <P>
                        One labor organization representative suggested that control points may delay advancement for employees in one band compared to employees in another band even though both employees perform at the same level. This is true. Under 
                        <PRTPAGE P="56354"/>
                        NSPS, employees performing similar levels of work may be compensated quite differently based on type of work, competencies required, or level of performance. This was also true under the General Schedule. For example, GS-13 pilots at one time received a special rate of pay that was approximately 30 percent higher than the rate GS-13 employees in other occupations received. This difference in rates reflected differences in staffing difficulties and labor markets between different occupations. 
                    </P>
                    <P>Another labor organization representative noted that we state that the Secretary will determine control points when previously this function was delegated to Components. They believe this is an attempt to limit their ability to bargain and take away a flexibility previously delegated by DoD to its own managers. We note that the Secretary is ultimately responsible for decisions involving NSPS, and authority is provided to the Secretary throughout the regulation to make these decisions. However, the day-to-day operation of many features may be delegated to the Components, including determining control points. These delegations will be provided in implementing issuances. Concerns about collective bargaining rights have been addressed under “Collective Bargaining and Labor Relations” located under “Major Issues”. </P>
                    <P>Other commenters suggested that if control points must exist, language should be inserted in the rules to the effect that control points will increase at the same time that rate ranges are adjusted and by an equivalent percentage. However, the basis for decisions driving the establishment of control points may not always mirror adjustments in rate ranges. No change has been made to the regulation in response to these comments. Nevertheless, it should be noted that whether or not control points are adjusted consistent with rate ranges, control points do not bar increases to base salary due to across-the-board NSPS general salary increases under § 9901.323(a)(1). </P>
                    <P>Another commenter suggested that, because control points are a somewhat foreign concept to most employees and will likely be viewed as incompatible with the pay band concept, additional information about the reasons for and need for control points might be helpful, either in the Supplementary Information for this regulation or the implementing issuances. Consequently, we have taken care to elaborate on responses addressing comments concerning control points and will continue to examine other means of providing a greater understanding concerning the use of control points. </P>
                    <P>Finally, another commenter noted that “budget” should be added to the list of factors to consider when establishing a control point and noted that adding this factor is consistent with information provided in the Table of Changes for § 9901.321(c) for the proposed regulation, which listed budget as a factor. In fact, we have determined that a budget or cost factors should absolutely not influence the setting of control points. We have not adopted this suggestion. </P>
                    <HD SOURCE="HD2">B. General Issues </HD>
                    <P>We received some comments which were not aimed directly at the substance of the proposed regulation but which we felt should be addressed. </P>
                    <P>
                        One commenter noted that in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         of the proposed regulations (73 FR 29898) we certify, in accordance with the Paperwork Reduction Act of 1995, that this proposed regulatory action will not impose any additional reporting or recordkeeping requirements under the Act. The commenter asserted that this is an improper statement since it means that the new NSPS pay pool decisions and with it the monies that the pay pool will be “playing with” and dividing among employees will have no records concerning how the decisions were made. The commenter stated that this is especially worthy of recordkeeping if the Pay Pool Panel makes pay and award decisions that are different from those of the rating official and higher-level reviewer. The commenter said that these records seem extremely necessary since the pay pool is distributing taxpayers' money and because they ensure the application of equal treatment of pay for job performance. Actually, the Paperwork Reduction Act applies to the burden placed on the public by Government agencies in gathering information related to the agencies' missions. It does not pertain to the generation of records within the agency. Rating officials and Pay Pool Panels will, in fact, generate records associated with the rating and pay pool processes. 
                    </P>
                    <P>Another commenter requested that we allow noncompetitive temporary promotions for 180 days instead of 120 days. This comment relates to NSPS staffing provisions which we did not address in the proposed regulation. The original NSPS statute, Public Law 108-136, permitted the Department and OPM to modify certain OPM staffing regulations, including the 120-day limit on temporary promotions, but the currently governing statute does not. </P>
                    <P>
                        One commenter expressed concern that the proposed regulation does not include references to applicable 5 CFR regulations, thus requiring users to review and study both the 
                        <E T="04">Federal Register</E>
                         rules and the 5 CFR regulations to determine which apply to a particular situation. This individual stated that it would be better if the NSPS regulations had the applicable sections from 5 CFR included so that there is a single reference source. In response, we note that the NSPS regulations published in the 
                        <E T="04">Federal Register</E>
                         are ultimately incorporated into 5 CFR and the section(s) referenced in the 
                        <E T="04">Federal Register</E>
                         become the 5 CFR reference(s) (e.g., § 9901.101 in the 
                        <E T="04">Federal Register</E>
                         becomes 5 CFR 9901.101). To the extent that the comment was intended to recommend inclusion of 5 CFR language in lieu of a cross reference when one has been provided, we note that references allow for application of revisions to those sections without change to this regulation in the event the language in the referenced section is modified. Therefore, cross references to 5 CFR sections covering the General Schedule continue to be incorporated in the final rule. 
                    </P>
                    <P>
                        A labor organization representative articulated apprehension with the fact that an employee's performance payout can be provided as a salary increase, a bonus, or a combination of the two, potentially resulting in each person's pay being different and, thereby, greatly multiplying the workload of administrative staffs and the Defense Finance and Accounting Service. The representative stated that previously there were standard pay increments, but now each employee's pay is different, requiring more time to process actions, raising the possibility of more errors, and requiring increased staff to correct the errors, all of which conflicts with DoD's recent staff consolidations and downsizing initiatives to reduce overhead costs. It is true that employees will no longer be paid at fixed step rates but, rather, may have their pay set at numerous points within their pay band rate range as a result of many different decisions based on various factors. To the extent possible, pay actions will be programmed to occur through an automated process. For example, general salary increases and most performance payouts will occur through an automated process. Many other pay decisions, however, will require manual intervention because it is not possible to program the many potential pay-setting variations. With the flexibility of pay banding come the challenge and the 
                        <PRTPAGE P="56355"/>
                        responsibility for setting pay correctly and minimizing errors. However, both sufficient training for all personnel involved in NSPS pay setting and the establishment of adequate review processes prior to finalizing pay actions will create the expertise associated with pay-setting decisions as well as mitigate error rates. 
                    </P>
                    <P>Several comments were received related to various issues involving reassignments and promotions. Several commenters observed that, since many movements that were formerly promotions under the GS system are now processed as reassignments in the NSPS pay banding environment, the financial enticement for taking on a new assignment is not as great as in the past. Another commenter stated that in addition to the higher salary received upon promotion, the promotion itself is a prestigious event, insinuating that the lack of promotion opportunities in a pay-banded system is detrimental to employee self-esteem. One commenter declared that being reassigned instead of promoted is “unfair” and “cheats” those who qualify for higher-level positions. This commenter further believes that this practice discourages employees from accepting an NSPS position and will force young, energetic employees to leave DoD for agencies operating under the old system. Others commented that reassignments and promotions can occur noncompetitively without other employees even being made aware of vacant positions. Some of these commenters asserted that employees would be placed in high-level positions without required knowledge, skills, and abilities simply because they are someone's close friend. Another employee asked that we change the proposed rules to permit a fair process for notifying employees of promotion opportunities because a model employee might not have a chance to compete because they do not belong to an association, do not participate in community work, or fish with the boss. Still another commenter alleged that the system will effectively eliminate certain groups of employees from obtaining promotions based on the supervisor's personal feelings toward those people. </P>
                    <P>By law, and by design, NSPS does not waive, modify, or otherwise affect the public employment principles of merit and fitness set forth in section 2301 of title 5 (merit system principles) or any provision of section 2302 of title 5, relating to prohibited personnel practices. At the same time, NSPS is designed to be a modern, contemporary, flexible, and agile human resources management system to help DoD meet the national security challenges of the 21st century. The NSPS classification system recognizes ranges of difficulty in various organizational and work situations, allowing for natural progression from entry/developmental to journey and expert levels of work, and provides broad-banded pay that offers employees greater advancement opportunities. NSPS pay bands combine a range of work into one discrete pay band level—each individual or single pay band level normally encompasses work formerly performed at one or more GS grade levels. This structure permits employees to move more easily, i.e., be reassigned, between different positions or assignments within their assigned pay band or to positions in comparable pay bands. It also results in fewer “promotions” than under the GS system. </P>
                    <P>NSPS is a performance-based pay system; the primary method of pay progression with a pay band is the performance payout. Under NSPS, employees have the opportunity, based on performance, to move more rapidly through a salary range than they may have had under a previous system. In many cases, they may have additional earning potential. Additionally, NSPS provides other pay incentives. For example, employees in pay band 1 of the nonsupervisory pay schedules may receive an Accelerated Compensation for Developmental Positions payment as described in § 9901.345. In addition to regular performance payouts, high-performing employees may receive additional performance increases that reward extraordinary individual performance, organizational or team achievement, or for other special circumstances. Employees are also eligible to receive chapter 45 incentive awards. Unlike the GS system, NSPS employees may also receive reassignment base salary increases of up to 5 percent in accordance with the rules at § 9901.353. When employees are promoted to a higher-level pay band, they are entitled to a more significant base salary increase of at least 6 percent and may receive an increase of up to 12 percent, or more, in accordance with the rules at § 9901.354. While many studies have indicated that employees are motivated by more than money to accept challenging work, we think the potential to progress financially in a pay-banded system, without being constrained by a “one-size fits all” design, will be accepted and welcomed by high-performing employees. We acknowledge, however, that this may take some time. </P>
                    <P>With respect to the comments regarding competitive versus noncompetitive movement, as with the GS system, many NSPS positions to which employees are reassigned are advertised; however, some are not. As under the GS system, some reassignments are done competitively if the position the employee will be reassigned to ultimately leads to a position in a higher full performance pay band (i.e., a higher-level of work under the NSPS classification architecture). Whether a position is advertised or not, employees who are reassigned to another position must be qualified for the position, unless they are reassigned as a result of reduction in force procedures and qualification requirements are waived. </P>
                    <HD SOURCE="HD2">C. Issues by Subpart </HD>
                    <HD SOURCE="HD3">1. Subpart A—General Provisions </HD>
                    <P>Subpart A defines the roles and general characteristics of the National Security Personnel System (NSPS). This subpart describes who is eligible for coverage under NSPS, identifies the authorities and responsibilities of OPM and DoD for administering and implementing the system, and defines key terms used through the regulation. </P>
                    <HD SOURCE="HD2">Section 9901.101—Purpose </HD>
                    <P>Section 9901.101 explains the overall purpose of the regulation in 5 CFR part 9901, which is to implement a human resources management system as authorized by section 9902 of the National Defense Authorization Act for Fiscal Year 2008 (NDAA 2008). Section 9901.101 states various guiding principles and key operational characteristics and requirements. It also describes who is eligible for coverage under NSPS, identifies the authorities and responsibilities of OPM and DoD for administering and implementing the system, and defines key terms used throughout the regulation. </P>
                    <P>
                        Labor organization representatives stated that the process of issuing a regulation prior to any bargaining does not meet the intent of Congress. The law requires DoD to honor collective bargaining obligations prior to any decision to implement NSPS for bargaining unit employees. The law also requires the Department honor national consultation rights under 5 U.S.C. chapter 71 for any proposed rule before it becomes final. Collective bargaining does not occur prior to national consultation and only occurs after the proposed rule becomes final and if a decision is made to implement for bargaining unit employees. DoD and OPM have met the requirements of law and the intent of Congress in issuing these regulations. 
                        <PRTPAGE P="56356"/>
                    </P>
                    <P>Labor organization representatives expressed concern that the requirement in § 9901.101(a) to establish implementing issuances to supplement any matter in the regulation excludes input from the Office of Personnel Management (OPM) and prevents collective bargaining. They also stated that the Department has published these proposed changes without employee involvement or collective bargaining, contrary to the requirement at 9901.101(b) that the system be more “credible and trusted.” We received many comments regarding issues surrounding collective bargaining; we have addressed them more in depth under the “Major Issues” section. DoD is committed to fulfilling its obligation to bargain in good faith on this regulation consistent with Governmentwide labor relations rules under 5 U.S.C. chapter 71 and the requirements of 5 U.S.C. 9902 as amended by NDAA 2008 and section 1106(b) of NDAA 2008. The scope of collective bargaining for this regulation, however, was determined by the statute. </P>
                    <P>Labor organization representatives expressed concern that the new regulation incorporates content from implementing issuances developed under the 2005 regulations. These commenters felt that incorporation of material from existing issuances into the revised regulation somehow conflicted with Public Law 110-181 (NDAA 2008). Some commenters indicated they believed the implementing issuances themselves were no longer valid due to the passage of that law. While portions of the implementing issuances became invalid due to the passage of Public Law 110-181, the implementing issuances were left largely intact and valid. To the extent the implementing issuances are inconsistent with the requirements of Public Law 110-181, we have not incorporated that material into the revised regulation. Revised implementing issuances were published on June 10, 2008 to implement policy changes and technical corrections, as well as make revisions based on requirements of Public Law 110-181. The authority for these issuances extends from the 2005 regulations, currently still effective where consistent with Public Law 110-181 (see section 1106(b)(3) of Public Law 110-181). Since certain modifications in these issuances impact equity with respect to the treatment of the Department's employees, we considered the release of the revised issuances crucial. We anticipate that these issuances will need additional revisions once this regulation is finalized and published. </P>
                    <HD SOURCE="HD2">Section 9901.102—Eligibility and Coverage </HD>
                    <P>Section 9901.102 sets forth general rules regarding employee eligibility and coverage under the various subparts of part 9901. Categories of eligible employees become covered only when the Secretary affirmatively approves coverage. Under this section, the Secretary has the explicit discretion to extend or rescind coverage to the Department's civilian employees. </P>
                    <P>Commenters objected to § 9901.102(a), stating that there is no statutory authority in Public Law 110-181 that allows DoD to apply NSPS to employees covered by anything other than the waivable or modifiable chapters of title 5, United States Code. We do not agree. The language at § 9901.102(a)—stating that employees are eligible for coverage “except to the extent specifically prohibited by law”—does not permit the Department to convert to NSPS any employees who cannot legally be covered by NSPS. Section 9901.102(f) describes the special circumstances under which it would be possible for the Secretary to extend NSPS coverage to employees who are not in systems established under the waivable or modifiable title 5 chapters. The Secretary may extend coverage to eligible employees under subparts B through D to the extent those provisions are not in conflict with other statutory requirements. We made no change to the proposed regulations based on these comments. </P>
                    <P>Several commenters expressed concern that the newly proposed NSPS regulation did not adequately define eligible employee groups for coverage under NSPS. Commenters described §§ 9901.102(a) and 9901.102(f) as inappropriately allowing NSPS to be applied to employees not specifically covered by title 5, including Domestic Dependent Elementary and Secondary Schools (DDESS) personnel. Another commenter stated that personnel not explicitly covered under title 5 had protective rights entitling them to collectively bargain their pay outside the scope of any NSPS statute. We have not modified the proposed regulation because it does not permit the Secretary to convert to NSPS any employee who cannot be legally covered by NSPS. Although title 10 DDESS educators are authorized to negotiate rates of pay, including any rates of pay linked to performance, to the same extent that they could before the enactment of NDAA 2004 as noted in 5 U.S.C. 9902(e)(9) (2008), that does not preclude the Secretary from taking action to convert them to coverage under NSPS if that is determined to be appropriate. </P>
                    <P>Commenters requested we amend § 9901.102(b) to conform to 5 U.S.C. chapter 71 requirements to provide advance notice to labor organizations regarding the extension of NSPS coverage to specific categories of employees. Although the proposed regulation was silent on this matter, the Department is committed to meeting its statutory obligations under 5 U.S.C. chapter 71 regarding advanced notice and opportunity to bargain the implementation of any decision to extend NSPS coverage to bargaining unit employees. The absence of a specific reference to chapter 71 language does not relieve the Department of its chapter 71 obligations. For clarification, we have added the following to § 9901.102(b): “The Secretary will notify affected employees and labor organizations in accordance with the requirements of 5 U.S.C. chapter 71 regarding a decision to extend NSPS coverage to any bargaining unit employees.” Any such notices would be provided at the appropriate level of recognition where the collective bargaining relationship exists. </P>
                    <P>
                        Another commenter remarked that § 9901.102(b) was confusing and that we should rewrite the section to indicate that any category covered under this paragraph must be covered by all the subparts listed to be eligible. Similarly, another commenter stated that we should amend this section by deleting “one or more subparts” from § 9901.102(c) and substituting “subparts B-D”; changing the last sentence of § 9901.102(e) to state “The Secretary will notify affected employees and labor organizations in advance of a decision to rescind the application to them of subparts B-D”; and deleting from the first sentence of § 9901.102(f)(1) the words “one or more subparts” and substituting “subparts B-D.” The commenter reasoned that the current proposed language allows employees to be covered by (1) subparts B, C, and D; (2) subparts B and D; (3) subparts C and D; or, (4) subpart D. The commenter asserted that, because no apparent reason exists for this variety of options and the provisions of all of these subparts are related, employees should be covered by all of them or none of them. The law requires coverage by a performance management system that links pay and performance (subpart D); however, the Secretary has statutory discretion to apply the other subparts (B and C) to employees once these employees are covered by the NSPS performance management system. We do not agree and have not changed the 
                        <PRTPAGE P="56357"/>
                        proposed regulation in response to this comment. 
                    </P>
                    <P>Another commenter noted that § 9901.102(e) does not clearly state that the Department is under no obligation to notify a labor organization if the organization is not affected by an NSPS rescission. This section requires notification to labor organizations when an NSPS rescission affects bargaining unit employees. While we agree with this comment, no change to the proposed regulation is necessary. </P>
                    <P>Commenters stated that we should strike § 9901.102(f), pertaining to the Secretary's authority to make coverage decisions, because the NSPS statute does not grant such authority to the Secretary. This section does not permit the Secretary to convert to NSPS any employees who cannot legally be covered by NSPS. The language at § 9901.102(f) is consistent with law and remains unchanged. </P>
                    <P>Finally, under § 9901.102(b) we have added a requirement imposed by NDAA 2008 to the end of the first sentence of this paragraph specifying that no more than 100,000 employees per year may be moved into NSPS. Also, in § 9901.102(f)(3), we have added a reference to § 9901.231 and clarified the language found in the proposed regulations. </P>
                    <HD SOURCE="HD2">Section 9901.103—Definitions </HD>
                    <P>Section 9901.103 provides definitions of terms used in more than one subpart. </P>
                    <P>Commenters differed with respect to the degree of specificity in the definitions. Some commenters stated that some of the new or revised definitions are too broad and fail to provide enough detail for important terms. Others considered the definitions misleading because they are too detailed. One commenter recommended reinserting removed definitions, even though the terms and subparts to which these definitions applied have been removed from this regulation. We have not made changes in response to these comments. </P>
                    <P>
                        A commenter requested that the definition for 
                        <E T="03">appraisal</E>
                         in § 9901.404 be moved to this section and redefined to say, “Appraisal means a written assessment of an employee's accomplishment of job objectives and contributions.” We have not inserted the definition for 
                        <E T="03">appraisal</E>
                         in this section because the term is not used outside of subpart D. We have also not changed the definition of this term in § 9901.404 in response to this comment. 
                    </P>
                    <P>
                        Commenters expressed concern over the lack of consideration for earning potential in the definition of 
                        <E T="03">comparable pay band</E>
                         or 
                        <E T="03">comparable level of work</E>
                         as it applies to classification. The definition is consistent with the NSPS classification structure. Comparable pay bands mean a comparable level of work without regard to the earning potential of the bands because labor markets may drive different salary ranges for different pay schedules due to differences in types of work vs. level of work. We have not revised this definition in response to these comments. 
                    </P>
                    <P>
                        Similarly, one commenter objected to the terms 
                        <E T="03">higher level of work</E>
                         and 
                        <E T="03">lower level of work</E>
                         as they relate to movement to an NSPS position from a non-NSPS (e.g., GS) position. The commenter stated that it was inappropriate to apply the broad classification criteria associated with a pay banding system with more narrowly defined non-NSPS classification criteria. The commenter pointed out that each NSPS position does have a specific level of difficulty, complexity of duties, and independence; therefore, it is more appropriate (albeit impractical) to consider these factors in light of the GS classification standards in order to determine whether they constitute a higher or lower level of work. For example, since a GS-9 position is not comparable in terms of job complexity or qualifications needed, movement to a YA-2 position that was formerly classified to a GS-13 should be considered a higher level of work, and promotion rules should apply. This view is completely contrary to the flexibility we have designed into NSPS and would have the effect of continuing to bind us to the GS or other more restrictive systems. Therefore, we have not revised our definition of these terms. However, for clarity, we modified the last sentence of the definition of these terms, as well as the last sentence of the definition of 
                        <E T="03">comparable level of work</E>
                        , to say, “When moving from a non-NSPS position to NSPS, the band of the NSPS position is determined to be at a [higher, lower, comparable] level of work than the grade or level of the non-NSPS position based on application of the NSPS classification structure as described in implementing issuances.” 
                    </P>
                    <P>
                        One commenter suggested that the word “behaviors” be deleted from the definition of 
                        <E T="03">competencies</E>
                         because this term relates to skills, not behaviors. Another commenter also asked us to revise this term stating that “competency” means capability, not behavior. According to OPM's Delegated Examining Operations Handbook, a competency is a “measurable pattern of knowledge, skill, abilities, behaviors, and other characteristics that an individual needs to perform work roles or occupational functions successfully.” The definition in § 9901.103 is an adaptation of OPM's definition; therefore, we have not revised this definition in response to the comment. 
                    </P>
                    <P>
                        Another commenter stated that the term 
                        <E T="03">contribution</E>
                         is vague and unnecessary because it is duplicative of the concept of “accomplishment of assigned work.” The commenter also said that the phrase “or group of employees,” which appears within the definition, is improper because performance evaluation properly concerns only an individual's performance, not a group's performance. An employee's contribution may go well beyond accomplishing assigned work. The employee may add value to the finished product by performing a task exceptionally well or by moving beyond assigned work to produce more than is required or expected. Similarly, we consider it appropriate to take into account an employee's role in team contributions when assessing an employee's overall contribution to the organization. As a result, we have not removed the term or revised the definition. 
                    </P>
                    <P>
                        Another commenter asked that we add information to the definition of 
                        <E T="03">Pay Pool Manager</E>
                         (PPM) to indicate that the payout distribution includes salary increases and bonuses, thereby establishing the agency's approval authority for each type of payment. We agree and have revised this definition accordingly. 
                    </P>
                    <P>
                        Commenters expressed concern over the broad definition of the term 
                        <E T="03">performance</E>
                        . These commenters stated that 
                        <E T="03">performance</E>
                         means “effort to accomplish assigned work,” and they objected to the references to “demeanor” and “attitude” in the definition of 
                        <E T="03">performance</E>
                        , saying that these requirements are inappropriate absent a genuine nexus between demeanor and accomplishment of an assignment. These commenters also stated that any “behavior” or lack of “civility” or “respect for others” that has no nexus with accomplishment of work assignment, but is so egregious as to be intolerable in any employee, is a conduct issue, not a performance issue. We note that the attributes causing concern are observable behaviors that affect the accomplishment of assignments, responsibilities, and organizational goals. We believe performance assessments would not be complete without considering employees' behaviors in carrying out work assignments. For example, because customer service is a paramount organizational objective, the manner in which employees treat customers is an 
                        <PRTPAGE P="56358"/>
                        important aspect of overall performance. Employee behaviors can be objectively observed and evaluated against established performance expectations. Under NSPS, supervisors may consider how underlying misconduct negatively impacts the execution of an employee's duties, those of the team, and/or those of the organization to the same extent such matters may be considered under other performance management systems. We have not revised the definition for 
                        <E T="03">performance</E>
                         in response to these comments. 
                    </P>
                    <P>
                        Commenters also objected to the definition of 
                        <E T="03">unacceptable performance</E>
                         as being over broad and stating that we should define it as meaning “failure to meet a performance expectation that may affect job retention”—a long-understood meaning of this term. These commenters recommended that, when defining the work assignment, managers should state the extent to which work should be done by a particular method or means, satisfy a particular qualitative or quantitative standard, or be done with a particular demeanor. We have not revised the definition of 
                        <E T="03">unacceptable performance</E>
                         in response to these comments. 
                    </P>
                    <P>
                        Another commenter requested that the definition of 
                        <E T="03">Performance Review Authority</E>
                         (PRA) be changed to refer to “official(s)” to better indicate that a PRA can be more than one person. We agree and have modified the definition of PRA to clarify that this entity may be more than one person. 
                    </P>
                    <P>
                        A commenter suggested the elimination of the mandatory use of contributing factors in determining performance ratings. In addition, the use of contributing factors was explained in response to a concern regarding whether the NSPS system is meeting its stated goal of transparency. These specific issues are discussed in the applicable sections of this regulation. Because this term is found in more than one subpart of the regulation, we moved the definition for 
                        <E T="03">contributing factor</E>
                         from § 9901.304 to § 9901.103 and provided a link to that section. 
                    </P>
                    <P>
                        Other commenters recommended that the role of the Pay Pool Manager in the pay pool panel process be clarified. We did so by amending the definition of 
                        <E T="03">Pay Pool Panel</E>
                         to clarify the active membership of the Pay Pool Manager on that panel. 
                    </P>
                    <P>
                        A commenter suggested that the definition of 
                        <E T="03">rating of record</E>
                         in the proposed regulation did not clearly define the term. We clarified the definition of 
                        <E T="03">rating of record</E>
                         as meaning the final numerical rating and narrative justification associated with a performance appraisal. In addition, we revised item (2) under the definition of this term to reflect that we are referring to an unacceptable rating “of record.” 
                    </P>
                    <HD SOURCE="HD2">Section 9901.105—OPM Coordination and Approval </HD>
                    <P>Section 9901.105 identifies those actions requiring DoD to coordinate with or request approval from OPM prior to promulgating certain implementing issuances and certain other actions related to the ongoing operation of NSPS, where such actions could have a significant impact on other Federal agencies and the Federal civil service as a whole. </P>
                    <P>As described in this section, “coordination” entails (1) providing OPM with an opportunity to review and comment on DoD proposals and to officially concur or nonconcur with all or part of the proposals, (2) taking OPM's views into account, and (3) advising OPM of the final DoD decision, including reasonable advance notice of the decision's effective date. </P>
                    <P>Many commenters requested we broaden § 9901.105(c) to require OPM approval for any action outlined in §§ 9901.105(a) through (e). By design, and in keeping with the statutory objective of establishing a “flexible” system, these regulations give DoD considerable authority within the regulatory framework. At the same time, OPM continues to have a role in overseeing the civil service system and in advising the President on civil service matters, including matters covered by these regulations. We believe the coordination and approval roles as defined in this section allow OPM full latitude to fulfill its responsibilities. To require OPM approval for every action would undermine the intent to create a flexible system, especially when the action is in response to a time-sensitive national security matter. As a result, we have not revised the language in this section in response to these comments. </P>
                    <P>Finally, a modification to § 9901.105(b)(9) changes “general salary increases” to “targeted general salary increases” in accordance with revised terminology at § 9901.323(a)(2). This change was made in response to a comment discussed under that section. </P>
                    <HD SOURCE="HD2">Section 9901.106—Relationship to Other Provisions </HD>
                    <P>Section 9901.106 describes the relationship of the NSPS regulation to other laws and regulations. </P>
                    <P>Several commenters expressed concern over the use of the term “great deference” in § 9901.106(a)(2), with respect to the DoD and OPM interpretation of this regulation. Commenters suggested that this term has legal implications and that the degree of deference owed to an agency is determined by a court applying judicial precedents, not an agency's own declaration of the degree of deference that the agency believes it is owed. Commenters also stated that the provisions of this regulation will also be interpreted in light of their consistency with 5 U.S.C. chapter 71. The degree of deference courts afford an agency's interpretation of a statute it administers is well-settled by judicial precedent. Accordingly, we have removed the sentence addressing deference from the proposed regulation. </P>
                    <HD SOURCE="HD2">Section 9901.107—Program Evaluation </HD>
                    <P>Section 9901.107 prescribes the Secretary's responsibility for evaluating the design and implementation of NSPS. </P>
                    <P>Many commenters questioned the deletion of the employee representative reference. They expressed concern that not explicitly including employees or employee representatives in the evaluation process excludes those on the ground level from that process. Some commenters expressed concern that, at the least, this omission was symbolic of a decrease in the importance of employee representatives in the evaluation process. One commenter suggested reinsertion of the reference to employee representatives as an explicit recognition of the importance of employee representatives to the evaluation process. The removal of the reference to employee representatives does not diminish their importance to program evaluation; rather, it clarifies that their participation is not a requirement for evaluation of NSPS. </P>
                    <P>
                        Commenters also declared that Public Law 110-181 requires reviews by the Comptroller General under section 1106(c). We note that the requirements of § 9901.107 are not based on any statutory requirements. This section places a self-evaluation requirement on DoD and does not address third-party evaluations of NSPS, such as evaluations by the Comptroller General. Any obligations that may exist with regard to labor organizations will be honored consistent with 5 U.S.C. chapter 71, 5 U.S.C. 9902, and section 1106(b) of Public Law 110-181. We believe it is a matter of good management that any agency implementing a new human resources management system has a responsibility for evaluating that system so that any problems can be corrected and improvements made. We have made no change to the proposed regulation based on these comments. 
                        <PRTPAGE P="56359"/>
                    </P>
                    <P>One commenter suggested that the evaluation process that has occurred thus far in the life cycle of NSPS has been less than ideal and that evaluation teams do not have the power or the authority to follow up meaningfully on any specific evaluation. To address concern that NSPS regulations can and will be ignored with respect to the implementation of specific features, commenters asked that this section clearly give the NSPS Program Executive Office the responsibility and authority to investigate, analyze, and appropriately report on implementation of NSPS and to follow up, as necessary, to address issues and ensure compliance with the regulation. Another commenter noted the importance of evaluation of compliance and that evaluation of program outcomes cannot be a basis for deciding whether or not to change the regulation unless a proper determination is made as to whether the outcomes are the result of following or not following the requirements of the regulation. The commenter suggested that we add the following language to this section, “Evaluation will seek to determine compliance with and the consistency and fairness of the implementation of the regulations, as well as the effectiveness and employee views of classification, compensation, and performance management practices.” The Department's established Human Capital Accountability System includes compliance-oriented reviews at field activities to ensure that personnel actions, decisions, and practices adhere to merit system principles and pertinent regulations, and holds DoD managers and human resource practitioners accountable for their human capital decisions and actions. These reviews include decisions and actions under NSPS as well as other personnel systems covering the non-NSPS workforce. Sharing NSPS-related information gleaned during accountability system reviews with the Program Executive Office makes a separate accountability program or authority unnecessary. Therefore, we have made no change to the proposed regulation in response to comments recommending incorporation of compliance reviews. </P>
                    <HD SOURCE="HD3">2. Subpart B—Classification </HD>
                    <HD SOURCE="HD3">General Comments </HD>
                    <P>Subpart B covers classification under the NSPS system. This section waives the current General Schedule classification system for those eligible for NSPS and outlines the new system for classification. The new classification system supports merit system principles and removes constraints of the narrowly defined grades under the General Schedule classification system. </P>
                    <P>Some commenters argued that the methodology and procedures for classifying and establishing jobs under the current regulation are ambiguous. Another commenter stated that NSPS lacks clear guidelines and that, in contrast, the GS system had built-in parameters for establishing pay grades using job factors. Some of these commenters suggested that NSPS adhere to the broad parameters established for the General Schedule classification criteria under 5 U.S.C. 5106. These broad parameters applicable to the General Schedule included the requirement that duties and responsibilities of the position, level of difficulty, responsibility and qualification requirements serve as the basis for determining the appropriate class and grade of a position. We agree that the regulation would be the appropriate place to provide a similar level of criteria for NSPS classification determinations. A new paragraph § 9901.201(b) has been added to address the basis for determining appropriate classification under NSPS. The new language reads as follows: “The basis for determining the appropriate classification under NSPS is the primary duties and responsibilities of the position, level of difficulty, occupational qualifications, competency requirements, mission of the organization, and relationship of the position to other positions or organizational levels.” </P>
                    <P>
                        Similar to General Schedule classification and qualification standards, the specific criteria within the broad parameters for NSPS position classification and qualification standards and functional guides are described in an issuance system not incorporated in the Code of Federal Regulations. While some commenters understood that the classification criteria would be further defined and clarified in implementing issuances, they objected to this approach because issuances are not subject to public comment. These commenters suggested that the NSPS classification program is less transparent and credible as a result. The same commenters tended to uphold the General Schedule classification system as a more transparent and credible system. Nevertheless, the NSPS classification system is modeled in transparency after the General Schedule. Neither the GS nor the NSPS classification system publishes classification criteria through the 
                        <E T="04">Federal Register</E>
                         process. As a result, agencies can respond more quickly to evolving mission, technologies, and work methods applicable to Federal service occupations. The 
                        <E T="04">Federal Register</E>
                         process, including the public comment period, slows the ability of the agency to establish and implement classification standards in a timely manner. For this reason, both DoD and OPM opt to use other methods to engage stakeholders and solicit the input of the agency and professional and employee organizations. Once classification criteria are established, both the NSPS and GS systems provide transparency by making criteria available to the DoD population and the public sector at large via the Internet and the agency issuance system. Those classification standards established for NSPS can be found on the NSPS Web site at 
                        <E T="03">http://www.cpms.osd.mil/nsps</E>
                         as well as at numerous other agency Web sites as well as through DoD civilian personnel offices. 
                    </P>
                    <P>Many commenters expressed the desire to include OPM in every phase of organization-wide classification changes. Their suggestions about OPM's role varied considerably, however, from wanting OPM to approve or disapprove any classification action taken by the Secretary to wanting OPM to approve all establishments of and alterations to classification standards. The regulation, which defines OPM's institutional role in the process in §§ 9901.105(b)(3) and (4), does provide for OPM coordination on NSPS classification standards. This coordination role enables OPM to meet its institutional role in the Federal Government at large. Requiring OPM approval, however, would unnecessarily restrict the ability of the Secretary to respond to unique national security requirements. Therefore, no change has been made to the proposed regulation in response to these comments. </P>
                    <P>
                        Some commenters requested that the assignment of positions to career groups, pay schedules, and pay bands be open to the collective bargaining process as well as the classification appeals process. Collective bargaining under NSPS is governed by 5 U.S.C. chapter 71, 5 U.S.C. 9902, and section 1106(b) of NDAA 2008. DoD is committed to fulfilling any obligation to bargain in good faith on negotiable conditions of employment related to these regulations, consistent with those laws. We note that policies, practices, and matters involving assignment of positions to career groups, pay schedules and pay bands generally relate to classification of positions. To the extent that proposals related to career groups, pay schedules and pay bands involve negotiable conditions of 
                        <PRTPAGE P="56360"/>
                        employment, the Department will satisfy its collective bargaining obligations. 
                    </P>
                    <HD SOURCE="HD3">Comments on Specific Sections of Subpart B </HD>
                    <HD SOURCE="HD2">Section 9901.201—Purpose </HD>
                    <P>Section 9901.201 explains the purpose of subpart B, which establishes a classification structure and rules for covered DoD positions and employees. </P>
                    <P>One commenter suggested that a machinist on the east coast should be paid the same as a machinist on the east [sic] coast and that we should remove all local market supplements (LMS) and simply pay people for the work they do. While machinists are excluded by this regulation, the commenter appears to perceive that the LMS is in conflict with the stated requirement to comply with merit principles in this section. Specifically, this section requires that the NSPS classification structure and rules in title 5, U.S. Code, are “in accordance with the merit principle that equal pay should be provided for work of equal value, with appropriate consideration of both national and local rates paid by employers in the private sector, and appropriate incentives and recognition should be provided for excellence in performance.” First, we note that standard local market supplements under § 9901.323 are administered in the same manner and amount as locality pay for General Schedule employees under 5 U.S.C. 5304. Whether the same or different, however, local market supplements are in harmony rather than in conflict with the merit principle of “equal pay for equal work” in that they implement that part of the merit principle that states that pay will be set in accordance with “* * * appropriate consideration of national and local rates paid by employers in the private sector, * * *”. Therefore, no changes have been made to the proposed regulation in response to this comment. </P>
                    <HD SOURCE="HD2">Section 9901.203—Waivers </HD>
                    <P>Section 9901.203 of the regulations specifies the provisions of title 5, U.S. Code, that are waived for employees covered by the NSPS classification system established under subpart B. As specified in § 9901.203(a), the waivers apply when a category of DoD employees is covered by a classification system established under this subpart, except with respect to OPM's authority under 5 U.S.C. 5112(b) and 5346(c) to act on requests for review of classification decisions, under § 9901.106 and § 9901.222(d). </P>
                    <P>Some commenters objected to the waiver of chapter 51 classification provisions and the substitution of language that the commenters argued is vague and does not contain clear standards. DoD is committed to implementing an easily understood and applied NSPS classification system across DoD. The waiver of chapter 51 was necessary to create a performance-based pay system, and provide the framework for an agile and responsive workforce. We do not believe that the waiver of chapter 51 provisions inhibits understanding or clarity of the NSPS classification process. In fact, to the contrary, the waiver of chapter 51 permits simplification of the more complex classification determination process designed under the General Schedule. While the regulation itself does not prescribe the specific criteria to be used in classifying NSPS positions, specificity is achieved in this system through issuances of position classification standards and functional guides. As stated earlier under subpart B general comments, we have added a new paragraph to § 9901.201 to address these criteria under NSPS. Section 9901.201(b) provides the basis for classification under NSPS. The basis for classification under NSPS takes into account information about the duties and responsibilities of the position, the level of difficulty, occupational qualifications, competency requirements, mission of the organization, and relationship to other positions or organizational levels. </P>
                    <HD SOURCE="HD2">Section 9901.204—Definitions </HD>
                    <P>This subpart defines the key components and terms used in the NSPS classification system. </P>
                    <P>One commenter requested that a definition for “effective date” be added to this section. Because the meaning of the term “effective date” can vary depending on the context in which it is being used and can refer to different timing requirements when used in different parts of the regulations, we have not modified the term under this section. Instead, the regulation has been modified under § 9901.221 to add clarity where the term “effective date” is used and remove confusion concerning which types of actions pertain to this term under that section. </P>
                    <HD SOURCE="HD2">Section 9901.211—Career Groups </HD>
                    <P>
                        Section 9901.211 gives DoD the authority to establish career groups. Many comments raised in response to this section are similar to those raised in other sections (e.g., desire to bargain collectively over classification criteria) and are therefore addressed under the 
                        <E T="03">General Comments</E>
                         section. 
                    </P>
                    <HD SOURCE="HD2">Section 9901.212—Pay Schedules and Pay Bands </HD>
                    <P>Section 9901.212 provides DoD with the authority to establish pay schedules within each career group, as well as pay bands within each pay schedule. One commenter noted that the pay bands, as defined in this section, are simple to understand. Another commenter expressed concern that the discretion to establish more than one pay schedule for “similar” career groups was contrary to the merit system principle of “equal pay for equal work.” Career groups, as a rule, are not similar; rather they represent different types and categories of work or functions. We can only assume that the commenter's concern is that the ability to define different pay schedules for similar levels of work in different career groups may be inconsistent with merit principles. NSPS recognizes that different occupations may be subject to different labor markets resulting in different pay levels for the same level of work. Contrary to the commenter's concern, establishment of different pay schedules reflecting appropriate labor markets is very much consistent with the merit system principle of “equal pay for equal work.” That principle specifically states that “equal pay should be provided for work of equal value, with appropriate consideration of both national and local rates paid by employers in the private sector, and appropriate incentives and recognition should be provided for excellence in performance.” Therefore the merit system principle of “equal pay” requires consideration of pay based upon: (1) Alignment and grouping of similar positions inside the organization; (2) the rates paid by the private sector; and (3) performance. </P>
                    <P>Another commenter suggested that the Secretary be required to receive OPM approval/concurrence when establishing NSPS qualification standards, rather than simply coordinating with OPM. The purpose of the coordination role with OPM is to enable OPM to meet its institutional role in the Federal Government-at-large and advise agencies of potential issues. Requiring OPM approval, however, would unnecessarily restrict the ability of the Secretary to timely respond to unique national security requirements. Consequently, no change has been made to the rule in response to these comments. </P>
                    <P>
                        Additional comments raised in response to this section (e.g., recommendation to provide collective bargaining over matters covered by this 
                        <PRTPAGE P="56361"/>
                        section) are similar to those raised for other sections of subpart B and are therefore addressed under the 
                        <E T="03">General Comments</E>
                         section dealing with subpart B. 
                    </P>
                    <HD SOURCE="HD2">Section 9901.221—Classification Requirements </HD>
                    <P>Section 9901.221 requires that DoD establish a method for describing jobs and documenting those descriptions. DoD will establish, through issuances, criteria and procedures for assigning each job to an occupational series, career group, pay schedule, and band, and will classify each job accordingly. </P>
                    <P>Some commenters requested further specificity about the roles in the classification process. In particular, some commenters requested that the person responsible for advising the employee of a personnel action be explicitly mentioned. The proposed regulation is intentionally broad in this regard. The regulation recognizes that DoD agencies and components may choose different parties to be responsible for notification requirements within their organizations. Consequently, more specific information will be made available through Component-level implementing issuances and guidance. No change has been made to this part of the proposed regulation in response to these comments in order to preserve discretion for DoD Components to assign work in a manner that can be tailored to their organization's structures, mission, and management philosophies. </P>
                    <P>
                        One commenter said that managers might wait too long past the effective date to file a personnel action, thus disqualifying an employee from receiving retroactive pay. Another commenter said that the seven-day notification period before a personnel action is too short. These comments reflect a misunderstanding of the effective date upon which the employee filing time begins. For purposes of preserving retroactive benefits, the employee filing time for a classification appeal does not begin until the effective date of the personnel action implementing the reclassification of an employee's position. Consequently, a manager cannot “manipulate” the timing of the effective dates of classification and personnel actions to prevent an employee from meeting a classification appeal filing timeline. 
                        <E T="03">Example:</E>
                         A classification action reducing a position's pay band is signed on May 3rd. The personnel action (typically Standard Form 50) must be signed within 4 pay periods (typically 8 weeks) of May 3rd. For this example, the Notification of Personnel Action (SF 50) effecting the personnel action is effective on June 10th. The employee must be notified no later than June 3rd (“at least 7 days before” the SF-50 is effective). If the employee files a classification appeal within 15 calendar days of the SF-50's date (no later than June 25), the employee preserves entitlement to retroactive action if the classification decision is overturned on appeal. If the employee files a classification appeal after 15 days of the effective date on the SF-50, the employee is not eligible for retroactive benefits. Because many of the comments reflected confusion over whether the employee's 15-day filing period to preserve retroactive benefits begins on the effective date of the classification action or the date of the personnel action, the proposed regulation has been modified to clarify that the 15-day filing period begins on the effective date of the personnel action. 
                    </P>
                    <P>Additionally, § 9901.221(d) and (e) have been reversed in order to help facilitate an understanding of employee filing timelines to preserve retroactive benefits upon appeal. The filing time period, which is the same as that allotted under GS and FWS, has proven sufficient under normal circumstances for an employee to register a classification issue. Therefore, no change was made to the proposed regulation regarding the filing timeline. </P>
                    <P>Another commenter stated that classification decisions that reduce an employee's pay should never be retroactive. We concur. There are no provisions under NSPS allowing a retroactive reduction in an employee's pay band or adjusted salary. The regulation states that a retroactive effective date for a classification action and the implementing personnel action is permitted only if the action resulted in a reduction in pay band or adjusted salary and if that action is subsequently reversed on appeal. </P>
                    <P>Several commenters suggested that the effective date of a classification action that increases or invalidates a reduction of an employee's pay and that follows an employee's formal raising of appeal of the matter to DoD or OPM should be retroactive to the later of (1) the date on which the employee first performed the work that is the subject of the action or (2) 30 calendar days before the date on which the employee first formally raised or appealed the matter. This recommendation, however, would prevent management from pursuing options that would result in more efficient position management in cases where an employee had not previously been downgraded. For position management purposes, management must retain discretion to remove higher-level work, once identified, and assign that work to employees already classified at the higher level. </P>
                    <HD SOURCE="HD2">Section 9901.222—Review of Classification Decisions </HD>
                    <P>Section 9901.222 of the proposed regulations provides employees the right to request that DoD or OPM reconsider the classification of their official position of record, including the pay system, career group, occupational series, pay schedule, or pay band. Commenters suggested that § 9901.222 be amended to include a procedure for appealing classification standards. One association argued that optometrists should be in the Medical Career Group and in pay band 3, suggesting that the classification standard and description of duties and requirements are based on 40-year-old information that does not reflect the changes to the profession since then. The association argued that the lack of an appeal right denies optometrists and others their inherent right to a day in court regardless of the merits of their case. All NSPS employees, including optometrists, have the right to appeal the career group and pay band to which they have been assigned. As under the General Schedule, classification criteria are not subject to appeal. We have modified the proposed regulation to further clarify this point in response to such comments. </P>
                    <P>
                        Commenters asked for greater specificity in the language appearing in this section. One commenter noted that, while § 9901.222(b) says an employee may not appeal classification of a position to which an employee has been detailed or temporarily promoted, it does not specifically mention temporarily reassigned positions. We have amended the proposed regulation to include temporarily reassigned positions in § 9901.222(b). A commenter also noted that some temporary promotions and positions can extend for longer periods of time than considered in the regulation. The commenter suggested amending the proposed regulation to allow for appeal for employees assigned to temporary positions extending longer than two years. To ensure that NSPS employees have similar rights to employees covered by OPM and DoD appeal regulations, we have amended the proposed regulation to allow classification appeals in situations where employees have been temporarily promoted for two years or more. 
                        <PRTPAGE P="56362"/>
                    </P>
                    <P>Another commenter noted that the last sentence of the paragraph describing who receives an appeal in § 9901.222(c) is unclear. As indicated in § 9901.222(a), an employee may appeal to either DoD or OPM, who will receive the appeal in accordance with § 9901.223 or § 9901.224, respectively. </P>
                    <P>Commenters expressed concern that the pay bands of positions that have been established in NSPS during the conversion process are not currently open to appeal, even though the pay band classification of individual positions is open to such consideration. Commenters claimed that this difference means that employees whose positions and job descriptions were placed in lower pay bands cannot seek reconsideration. However, employees converted into NSPS were placed in pay bands that correlated with the GS grade of the position to which they were assigned prior to conversion. Consequently, there is no reduction in pay band upon conversion. Employees who believe they were converted to the wrong pay band may appeal their classification at any time. Because employees were converted to NSPS without a loss of pay and based on their GS classification at the time of conversion and not that of a lower grade, there is no basis for retroactive benefits. We have elected not to change the proposed regulation in response to these comments. </P>
                    <P>
                        Finally, commenters suggested deleting § 9901.222(c) in its entirety, citing the potential for conflict between the NSPS regulation and local bargaining agreements in accordance with NDAA 2008. Some commenters saw the new process outlined in this section as superfluous because it and the local bargaining process are similar and have overlapping steps. Commenters also suggested that the accuracy of position descriptions was not a classification issue. One commenter cited 
                        <E T="03">Veterans Administration and AFGE Local 2880</E>
                        , 16 FLRA 50 (1984) as a reference. Many commenters deem the process as open to arbitration, suggesting that attempting resolution through the NSPS process is restrictive and inefficient. In response to these comments, § 9901.222(c) was modified to reflect that the employee may raise the issue of accuracy of a position description informally with the employee's supervisor or file a grievance using the applicable administrative or negotiated grievance procedure. 
                    </P>
                    <HD SOURCE="HD2">Section 9901.223—DoD Classification Appeals </HD>
                    <P>Several commenters suggested that the reasons listed in §§ 9901.223(a)(2) and 9901.223(a)(3) for disallowing an employee representative (because the employee's duties are deemed priority work of the Government, or the employee's release would give rise to unreasonable costs) did not sufficiently protect the employee. The commenters expressed concern that the guidelines were insufficient justification to bar an employee representative from participating in the appeals process. These commenters believed employees should have the representative of their own choosing without regard to cost, availability, or impact on mission. The criteria by which management can disallow participation of a particular employee representative under this section are standard across the Government and necessary to the conduct of mission. No change was made to the proposed regulation in response to these comments. </P>
                    <P>Many commenters found confusing and complicating the requirement in § 9901.223(b)(1) that employees formally raise concerns about their classification to the immediate supervisor prior to filing an appeal. They expressed concern that the supervisory review might overlap with the employee's 15-day filing timeline and cause the employee to lose eligibility for retroactive benefits. Some commenters also expressed concern about what process would be followed in the event a supervisor did not respond to such an issue raised by an employee. In response to these comments, we modified § 9901.223 of the proposed regulation to remove the requirement that a classification concern must first be raised with an employee's immediate supervisor. </P>
                    <P>
                        Commenters requested an alignment of the timeline given to the employee to preserve retroactive benefits with that given to the manager for response to a classification issue presented by an employee under § 9901.223(b)(1). As we have modified § 9901.223(b)(1), the 30-calendar-day response time for supervisors is no longer required, unless the employee chooses to use this step in the process. However, we note that, while the filing timeline to preserve retroactive benefits is 15 days from the 
                        <E T="03">effective date</E>
                         of the personnel action implementing the classification decision, the employee's timeline is at least 21 days from the notification of a personnel action. Pursuant to § 9901.221(d), employees must be notified in writing of the effective date of a personnel action implementing the classification decision resulting in a reduction in pay band or adjusted salary. This notice must be provided at least seven days before the personnel action is taken and provide the employee with information on their right to appeal the classification decision and the time limits for so doing. Consequently, each employee will have seven or more days of awareness of a pending personnel action and the consequent appeal rights before the 15-day filing period to preserve retroactive benefits begins. Another commenter stated that § 9901.223(b) puts the supervisor in the role of human resources officer and that the supervisor may not have the qualifications for this role. We have not made any changes to the proposed regulation in response to this comment. Supervisors and managers are assisted in this role by their human resources office. The human resources office is responsible for providing advice and expertise to supervisors and managers throughout the classification appeals process. Additionally, we are confident that supervisors are well-qualified to respond to classification appeals due to their familiarity with the jobs and the simplified classification structure and criteria established under NSPS. Commenters suggested that the timeline in § 9901.223(b)(3) to challenge a classification decision be changed from 15 days after a classification action takes effect to 15 days after an employee has been notified of a personnel action. This change would allow the employee to avoid situations where a personnel action is taken on a classification matter with an effective date up to four pay periods prior to notice of the personnel action. The commenter expressed concern that such a situation would always put the employee outside the 15-day period to file an appeal after the effective date of a reclassification. Further, the commenter stated that the employee would have to request an extension under § 9901.223(b)(3) or lose the opportunity to appeal. We have concluded that the wording of the proposed regulation was unclear as to whether the “effective date” starting the 15-day filing time period was that of the position classification action or the personnel action implementing that action. Therefore, §§ 9901.221(e)(2) and 9901.223(b)(2) were revised to clarify that the 15-day filing timeline for employee classification appeals begins with the effective date of the “personnel action.” We did not modify the proposed regulation to reflect the recommendation to begin the 15-day 
                        <PRTPAGE P="56363"/>
                        period on the date of notification of the personnel action because this change would shorten the time period for employee appeal. Nevertheless, we have also modified the proposed regulation to provide the deciding official the authority to grant an extension of the filing timeline when an employee shows that he or she did not receive notice of the personnel action. 
                    </P>
                    <P>Several commenters objected to the requirement that an employee provide such personal information as name, mailing address, office telephone and fax numbers, name of the employee's Component and exact location of the employee's position within the Component upon submission of a classification appeal. These commenters preferred that the agency be held accountable for providing that information. Such information is standard to filing an employee classification appeal in the Federal Government. For example, OPM requires the same information in the filing of classification appeals under 5 CFR part 511. The data provided ensures that adequate information is available to act on the employee's request and thereby protects the employee's interests. Consequently, no action was taken in response to these comments. Another commenter suggested that two additional pieces of information be required of the employee in submitting a classification appeal. These additional documents included the current position description and the latest evaluation statement for the position, if available. Another commenter requested that the rule specify that the organization will provide these materials to the employee, due to their importance to the future of the appeal. No change was made based on these comments. Such documents are typically provided by the servicing human resources office. </P>
                    <P>Commenters also recommended that the proposed regulation be modified to disallow cancellation under the events outlined in § 9901.223(d)(2) when there may be an entitlement to retroactive benefits. We have modified the proposed regulation to accept this recommendation. </P>
                    <P>Some commenters interpreted § 9901.223(d) as restricting the employee's right to resolve classification grievances. They suggested adding these cancellation provisions to the collective bargaining process, thus not interfering with the employee's right to appeal by any avenue. No change was made to the proposed regulation in response to these comments. As previously stated, DoD is committed to fulfilling its obligation to bargain in good faith on negotiable conditions of employment related to these regulations consistent with 5 U.S.C. chapter 71 and the requirements of 5 U.S.C. 9902 and section 1106(b) of NDAA 2008. </P>
                    <HD SOURCE="HD2">Section 9901.224—Appeal to OPM for Review of Classification Decisions </HD>
                    <P>This section outlines the right to and process for appealing classification decisions to OPM. </P>
                    <P>One commenter expressed concern that this section would limit the appeal of adverse actions, excluding them from the MSPB. The section specifically addresses the employee's right to appeal a classification decision and does not concern or impact appeals of adverse actions to the MSPB. It should be emphasized that § 9901.224(d), which states that “OPM's final determination on an appeal made under this section is not subject to further review or appeal” mirrors the language in title 5 CFR 555.612, which states that “[a]n appellate decision made by the Office is final unless reconsidered by the Office. There is no further right of appeal.” The MSPB has no jurisdiction to review classification decisions made by an agency. This regulation neither limits appeals of adverse actions to the MSPB, nor does it confer jurisdiction on the MSPB to adjudicate disputes regarding classification decisions. We have not made any changes to the proposed regulation in response to this comment. </P>
                    <HD SOURCE="HD2">Section 9901.231—Conversion of Positions and Employees to the NSPS Classification System </HD>
                    <P>Section 9901.231 of the regulations addresses the conversion of positions to the classification system established under this subpart. </P>
                    <P>Commenters requested clarification regarding § 9901.231(b). In particular, commenters wondered whether the work level conversion tables used to place an employee in a pay band would be based on an employee's actual level of work or the work as described in the employee's position description, arguing that the work level conversion tables only consider positions that are properly classified under the OPM classification structure. No change has been made to the proposed regulation in response to this comment. Conversion tables are not published in this regulation. However, we note that classification of an employee's position upon conversion to NSPS is based on the employee's official position of record, and that it is assumed the employee's position is properly classified under the OPM or applicable classification structure. Some commenters expressed confusion regarding the issue of temporary promotions as they relate to conversion, questioning whether or not the temporary position would be terminated prior to conversion and whether or not the employee would return to the temporary position after conversion (with pay adjustment). As explained in § 9901.231(c), an employee on a temporary promotion at the time of conversion into NSPS will be returned to his or her official position of record prior to processing the conversion. After the employee is converted to NSPS, a determination will be made as to whether there is still need for the temporary position. If so, that position will be properly classified according to NSPS classification criteria. Because NSPS bands are broader than General Schedule grades, it is possible that the position may be classified into the band to which the employee is assigned. Section 9901.371(k) of this regulation provides authority for the organization to set pay immediately after conversion if the employee is temporarily assigned back to the position to which he or she was temporarily promoted before converting to NSPS. That section permits temporary placement and pay subject to the same terms and conditions as the initial temporary promotion. </P>
                    <P>One commenter requested that § 9901.231(d) be changed to protect grade retention for converting employees. No change was made to the proposed regulation in response to this comment. NSPS does not provide for General Schedule or other pay plan grade retention upon conversion. If a converting employee's base salary exceeds that of the assigned NSPS pay band, the employee will receive pay retention. If an employee has a preexisting entitlement to pay retention under 5 CFR part 536 immediately before becoming covered by NSPS, consistent with § 9901.356(m), he or she will be entitled to a retained rate of pay without regard to the 104-week pay retention limit. </P>
                    <HD SOURCE="HD3">3. Subpart C—Pay and Pay Administration </HD>
                    <HD SOURCE="HD3">Overview of Comments </HD>
                    <P>
                        Subpart C contains regulations establishing pay structures and pay administration rules for covered DoD employees to replace the pay structures and pay administration rules established under 5 U.S.C. chapter 53 and 5 U.S.C. chapter 55, subchapter V, as authorized by 5 U.S.C. 9902 (subject to the limitations on waivers in § 9901.303). Additionally, this subpart sets forth the rules for performance-
                        <PRTPAGE P="56364"/>
                        based pay, premium pay, and pay upon conversion into NSPS, as well as procedures for movement or conversion out of NSPS. By far, the largest number of individuals and labor organizations submitting comments focused on changes to this subpart of the proposed rule. Of the total comment submissions, approximately 80 percent touched on at least one aspect of pay and pay administration. General issues raised by commenters included concerns that the rule would permit favoritism and bias when determining performance payouts, mistrust of the pay pool administration process (especially as regards the highest-level reviewers), dissatisfaction with the use of control points within bands, concerns about the impact of bonuses on retirement, concerns about perceived infringements on collective bargaining rights, and perceptions of unfairness in terms of salary increases as compared to the GS system. Of those commenters dissatisfied with NSPS, many drew direct comparisons between the GS and NSPS systems, indicating a preference for the GS system. These commenters looked for consistency and comparability between the two systems in all areas, not just those prescribed by the NDAA. Commenters stated the concern that they would lose pay comparability with DoD employees remaining under the General Schedule and with employees in other Federal agencies. Also, many commenters argued that employees should receive 100 percent of the pay increases they would have received under the General Schedule in the form of across-the-board increases (not the minimum NSPS across-the-board increase of 60 percent of the Governmentwide GS pay increase with the balance being applied to performance-based payouts). Some commenters stated that the Department should disband NSPS altogether and return to the General Schedule classification and pay system. 
                    </P>
                    <P>We have addressed the questions concerning fairness of performance payouts and administration of the pay pool in “Performance and Pay Pool Management” under “Major Issues.” Similarly, comments concerning control points have also been addressed under “Control Points” and concerns about collective bargaining rights have been addressed in “Collective Bargaining and Labor Relations” located under “Major Issues.” The remaining concerns have been addressed under the various sections of this subpart. As a general statement in response to preferences expressed for the General Schedule, we believe that NSPS improves on the General Schedule by providing the opportunity to appropriately reward top performers and/or compensate them in relation to their labor market value and performance. </P>
                    <P>The proposed regulation provides that the overall amount allocated for compensation of the DoD civilian employees included in NSPS may not be less than the amount that would have been allocated for compensation if they had not been converted to NSPS. Because NSPS takes the same amount of money paid out under the General Schedule and redistributes based on different factors (e.g., performance vs. seniority), it is possible that some employees may not do as well as they did under the General Schedule. At the same time, many other employees will do better under NSPS than they would have under the General Schedule. Overall, the payouts for NSPS employees under NSPS during the past 2 years of implementation have proven to compare favorably to the General Schedule. The changes made in the proposed regulation improve NSPS by clarifying aspects of system implementation while ensuring that important safeguards are in place to protect employee rights and uphold merit system principles. </P>
                    <P>The revised system is consistent both with the requirements of the National Defense Authorization Act (NDAA) 2008 and with the statutory requirement that the Department establish a “pay-for-performance” system that better links individual pay to performance. (See 5 U.S.C. 9902(b)(7)(I).) Furthermore, we believe Congress and the American public expect their public employees to be paid according to how well they perform, rather than how long they have been on the job. They also expect the Department to maximize its efforts to recruit and retain the most talented and motivated workforce to accomplish its critical national defense mission. </P>
                    <P>Comments related to specific sections of subpart C are described in the following sections. </P>
                    <HD SOURCE="HD3">General </HD>
                    <HD SOURCE="HD2">Section 9901.302—Coverage </HD>
                    <P>Section 9901.302 lists eligible DoD employees and positions, subject to a determination by the Secretary under § 9901.102(b). </P>
                    <P>A few commenters suggested extending coverage to Federal Wage System (FWS) prevailing rate employees, and several commenters questioned the authority of the Secretary to designate additional groups to be covered under NSPS. We have not revised this section in response to these comments. NDAA 2008 specifically excluded FWS employees from NSPS and, except for those employees excluded by law, the Secretary has the discretion to extend coverage to eligible employees and categories of positions. </P>
                    <HD SOURCE="HD2">Section 9901.304—Definitions </HD>
                    <P>This section provides definitions of terms used throughout the subpart. </P>
                    <P>
                        Commenters objected to the definitions of 
                        <E T="03">contribution, contribution assessment, performance share, sub pay pool,</E>
                         and 
                        <E T="03">unacceptable performance.</E>
                         They felt the definitions are vague, improper, inaccurate, unnecessary and, in the case of the last term, contradictory to long understood interpretations of unacceptable performance. We have not revised these definitions in response to the comments because they accurately reflect the meaning of the terms as used in the regulation. 
                    </P>
                    <P>
                        One labor organization representative recommended that definitions of 
                        <E T="03">local market</E>
                         and 
                        <E T="03">labor market conditions</E>
                         be included in this section. Inasmuch as these terms have generally accepted meanings and there is nothing particularly unique in the use of these terms in this regulation, definitions have not been added for these terms. We note, however, that generally 
                        <E T="03">labor market</E>
                         means the market in which workers compete for jobs and employers compete for workers, as defined by (1) the geographic parameter of a job search; (2) education and/or technical background sought; (3) experience required by the job; (4) licensing or certification requirements; (5) occupational membership; (6) level of work to be performed; and (7) industry in which employers compete for the same skills. The term 
                        <E T="03">labor market conditions</E>
                         generally means the availability and cost of labor in a given market and the factors/forces impacting the availability and cost of labor. 
                    </P>
                    <P>
                        Another commenter recommended that either the YA-2 pay band maximum rate of pay be amended to match that of pay band YC-2, which establishes consistency between the maximum rates for YA and YC, or that the definition of 
                        <E T="03">comparable pay band</E>
                         or 
                        <E T="03">comparable level of work</E>
                         exclude those bands where there are differences in the maximum base salary rates. We have not made any change based on this comment. Structural adjustments to pay bands are made to reflect the overall market value of the level and type of work encompassed by that band. Levels of work can be comparable whether or not the pay range (minimum and/or maximum rates) remains the same. Additional discussion regarding the 
                        <PRTPAGE P="56365"/>
                        terms 
                        <E T="03">comparable pay band</E>
                         and 
                        <E T="03">comparable level of work</E>
                         may be found at § 9901.103 in response to comments about these terms. 
                    </P>
                    <P>
                        Finally, because the term is found in more than one subpart, we moved the definition of 
                        <E T="03">contributing factor</E>
                         from this section to § 9901.103 and provided a link to that section. 
                    </P>
                    <HD SOURCE="HD2">Section 9901.305—Rate of Pay </HD>
                    <P>
                        Section 9901.305 defines the term 
                        <E T="03">rate of pay</E>
                         and provides an explanation of what it means to establish and adjust a rate of pay in the context of 5 U.S.C. 9902(e)(9). Under that section of law, “any rate of pay established or adjusted in accordance with [5 U.S.C. 9902] shall be non-negotiable, but shall be subject to procedures and appropriate arrangements of [5 U.S.C. 7106(b)(2)-(3)].” 
                    </P>
                    <P>Representatives from several labor organizations commented that the proposed rule appears far too specific, in effect broadening the definition of rate of pay to narrow the scope of bargaining. The labor organization representatives contend that, while NDAA 2008 restored collective bargaining rights to DoD employees, this broader definition of “rate of pay” contradicts the intent of Congress. The proposed regulation language does not and cannot take away collective bargaining rights regarding “procedures and appropriate arrangements” and DoD is committed to fulfilling its obligation to bargain in good faith on these NSPS regulations consistent with Governmentwide labor relations rules under 5 U.S.C. chapter 71 and the requirements of 5 U.S.C. 9902 and section 1106(b) of NDAA 2008. The term “rate of pay” is undefined in statute. Although it is used frequently in connection with various aspects of title 5, it does not mean the same thing in every place it appears. We believe it is important to clarify this term and the NSPS statute provides authority to do so. Thus, DoD and OPM proposed a definition to ensure uniformity and consistency for NSPS implementation. </P>
                    <P>Some labor organizations suggested that all references to “and the conditions defining applicability of each rate” in § 9901.305(a)(2) be deleted from the definition of “rate of pay” suggesting that DoD was trying to evade its legal obligations by broadening the definition and narrowing the scope of collective bargaining. Establishing or adjusting a rate of pay for employees must take into account both the amount of the rate and the required eligibility criteria. Insofar as the term “conditions of applicability” may be misinterpreted, we have removed multiple references to “conditions of applicability” from this section. Paragraph (b) of § 9901.305 has been revised to instead refer to “eligibility requirements”. Upon request, bargaining of procedures and appropriate arrangements concerning “rate of pay” is required. The definition of “rate of pay” will not preclude employee representatives from negotiating over such matters as procedures for determining order of overtime assignments. Order of overtime assignments involves management's right to assign work in accordance with 5 U.S.C. 7106(a) and does not concern decisions regarding “rate of pay.” Rate of pay decisions are made separately from overtime assignment decisions. Bargaining over seniority, or other procedures to distribute overtime fairly, is not changed or impacted by this definition of “rate of pay.” </P>
                    <P>Several commenters suggested that the definition of “rate of pay” include within-grade adjustments, some of which are discretionary, as provided for in § 9901.351(c). Under §§ 9901.351(c) and 9901.371(j), the regulations provide for both mandatory and discretionary salary adjustments for employees moving from GS. These adjustments are based on the amount of time an employee has served in the GS within-grade increase waiting period. The absence of an explicit reference to these pay adjustments does not exempt them from the definition of “rate of pay” under § 9901.305(a). Nevertheless, for clarity purposes, “within-grade increase adjustments” has been added to the examples of rates of pay in § 9901.305(b)(3). </P>
                    <HD SOURCE="HD3">Overview of Pay System </HD>
                    <HD SOURCE="HD2">Section 9901.311—Major Features </HD>
                    <P>This section of the subpart describes the key structural features of the NSPS pay system. </P>
                    <P>One labor organization representative questioned § 9901.311(b) which prescribes that the NSPS pay system will include policies regarding the setting and adjusting of band rate ranges based on mission requirements, labor market conditions, and other factors, as described in §§ 9901.321 and 9901.322. They indicated that these sections, in fact, merely state that DoD will do these things but do not contain any useful information and do not contain the details that would allow them to comment effectively. They recommend that we delete §§ 9901.321 and 9901.322. We disagree with this comment. As evidenced by the large number of substantive comments we received on these sections, these sections address key features of the NSPS compensation structure as well as criteria pertaining to these features. </P>
                    <HD SOURCE="HD2">Section 9901.312—Maximum Rate of Base Salary and Adjusted Salary </HD>
                    <P>This section establishes authority and criteria for limitations on maximum rates of pay for base and adjusted salaries under NSPS. </P>
                    <P>One commenter suggested that if the Secretary establishes maximum rates of base salary, the statutory comment and review process should begin, followed by collective bargaining. We have not revised this section in response to this comment. A statutory comment and review process is not required for maximum rates of base salary. Such a comment period is not required by law and would unnecessarily delay DoD's ability to respond to labor market forces. The proposed regulation does require, however, that the Secretary coordinate with OPM prior to the establishment of maximum rates of basic pay. DoD is committed to fulfilling its obligation to bargain in good faith on this regulation consistent with Governmentwide labor relations rules under 5 U.S.C. chapter 71 and the requirements of 5 U.S.C. 9902, as provided for in NDAA 2008. </P>
                    <P>One commenter suggested that the NSPS proposed regulation needs a provision that allows the maximum of the rate range for physicians and dentists to keep pace with the maximum rates paid to the same occupations in the Veterans Health Administration under title 38, U.S. Code, without large automatic pay increases. Physicians and dentists are not subject to the maximum adjusted salary rate caps described in this section in recognition of salary ranges unique to the physician/dentist labor market, to include rates paid by the Veterans Health Administration under title 38. In the absence of an adjusted salary cap for physicians/dentists, adjusted salary in the proposed regulation is limited only in relation to the aggregate pay cap, which cannot exceed the salary of the President of the United States. Consequently, there is sufficient authority in the proposed regulation to continue to establish salaries for physicians and dentists consistent with title 38 as well as other labor markets without modification to the regulation. </P>
                    <P>
                        Another commenter asked if the Secretary's authority to establish higher adjusted salary rates for physicians and dentists applies to researchers or non-medical PhD research scientists. The increased maximum adjusted salary maximums are in recognition of a specific labor market and include those types of health care positions covered by the Veterans Health Administration 
                        <PRTPAGE P="56366"/>
                        under title 38, which does not include researchers or other non-medical scientists. 
                    </P>
                    <HD SOURCE="HD2">Section 9901.313—Aggregate Compensation Limitations </HD>
                    <P>This section sets forth authority and criteria for aggregate compensation limits. </P>
                    <P>One commenter suggested removing from the list of compensation types at § 9901.313(b) the following payments: Severance pay under 5 U.S.C. 5595, nonforeign area cost-of-living allowances under 5 U.S.C. 5941(a)(1), and lump-sum payments for accumulated and accrued annual leave on separation under 5 U.S.C. 5551 or 5552. The commenter argued that these payments are not compensation for work performed and therefore should not be included when calculating aggregate compensation limits. The commenter is correct because these specific payments are not subject to the aggregate limitation on pay. However, no change in the proposed regulation is needed because these payments are listed as exclusions in § 9901.313(b)(13). </P>
                    <HD SOURCE="HD2">Section 9901.314—National Security Compensation Comparability </HD>
                    <P>Labor organization representatives commented that the proposed regulation does not include any mention of 5 U.S.C. 9902(e)(3), which requires rates of compensation for civilian employees to be adjusted the same as rates for members of the uniformed services. Commenters had objected to this omission in the 2005 regulation and objected again to the omission of this provision in the current proposed regulation. However, because comparability with military pay is already addressed under 5 U.S.C. 9902(e)(3) and requires no further elaboration to implement, there is no need to address it again in this regulation. </P>
                    <P>One commenter objected that § 9901.314 fails to mention both the requirement that aggregate compensation be no less than what would have been available had employees not been converted to NSPS through fiscal year 2012 and the requirement that a formula to be developed in years after 2012 for calculating the overall amount to be allocated for compensation of civilian employees included in NSPS. However, § 9901.314(a) and (b) specify these requirements in almost the exact language as that used in NSPS statute. Therefore, no change was made to the proposed regulation in response to this comment. </P>
                    <HD SOURCE="HD3">Rate Ranges and General Salary Increases </HD>
                    <HD SOURCE="HD2">Section 9901.321—Structure </HD>
                    <P>This section describes the Secretary's authority to establish ranges of base salary rates for pay bands. </P>
                    <P>Numerous comments were received on the control point feature of NSPS. Consequently, a comprehensive response to those comments including background information and the philosophy underlying the establishment and use of control points has been provided under the “Major Issues” section of this Supplementary Information. </P>
                    <HD SOURCE="HD2">Section 9901.322—Setting and Adjusting Rate Ranges </HD>
                    <P>This section provides the Secretary with the authority to set and adjust the rate ranges established under § 9901.321; establish the effective date of new or adjusted rate ranges; establish different rate ranges and range adjustments for different pay bands; and adjust the minimum and maximum rates of a pay band by different percentages. </P>
                    <P>A commenter proposed that we delete “mission requirements” from the list of factors the Secretary may consider in setting and adjusting rate ranges under § 9901.322(a). The commenter stated that this is a vague, undefined concept that is not relevant to the value of work, and pay should be determined according to the value of work. We have not revised this section in response to this comment. While we have not defined the term “mission requirements,” it is a frequently used term relating to those factors necessary to accomplish the Department's national security mission. We consider this to be among many relevant and important factors the Department may consider in determining appropriate rate ranges. It is essential that DoD devote its limited financial resources to attracting, recruiting, and retaining employees who possess the knowledge, skills, abilities and/or competencies relevant to its missions. Where market forces drive up the cost of labor in one or many occupations, DoD must have the ability to apply its limited resources to the skills most critical to its mission. For example, there may be a requirement for specific information technology, program management, or acquisition management skills. If those skills are in short supply in the labor market and critical to accomplishment of mission, DoD needs to have the ability to direct its resources to acquiring employees with those skills rather than losing those employees to competitors or adjusting the pay of skills which they have already competitively priced. It is important to note, however, that the NSPS regulation does not give any one factor greater weight than any other; given the circumstances of a particular year, any factor may have a greater or lesser effect on decisions regarding adjustments in rate ranges. We believe the American public expects DoD to use its resources in the most cost effective manner possible. </P>
                    <P>One labor organization endorsed this section of the proposed regulation, citing its origins in NDAA 2008 and the requirement that no less than 60 percent of the general pay increase (GPI) go to all employees rated above unacceptable. Another commenter stated that the maximum rate of each pay band should be adjusted by the sum of the amount of the increase applied to the NSPS GPI plus the amount of the GPI applied to the pay pool because, if the pay ranges do not progress by the full amount of the GPI, management will lose the ability to compete with the GS market which is still a very significant competitor with the NSPS labor force. This commenter additionally asserted that continuing to increase the maximum of the pay range helps to reinforce to employees that the main purpose of NSPS is to put emphasis on performance rather than cutting civilian pay. We agree and have revised the language at § 9901.322(e) to add a requirement for the maximum rate of all pay bands to be adjusted by no less than the percentage amount of the General Schedule annual adjustment under 5 U.S.C. 5303. A similar comment was received which stated that we should require control point maximums to be adjusted at the same rate as the GPI; otherwise an employee could be denied a full GPI increase. We note that whether or not a control point is adjusted to reflect the amount of a NSPS across-the-board increase, both the NSPS statute [5 U.S.C. 9902(c)(7)] and the proposed regulation [5 CFR 9901.323(a)(1)] require that each employee eligible for such increase must receive it regardless of pay band control points. Therefore, no adjustment has been made to the proposed regulation in response to this comment. </P>
                    <P>
                        Other labor organization representatives expressed concern that the ability of DoD to raise the maximum rate of a pay band by an amount different from the minimum rate could allow the Department to benefit a few favorite employees at the top of their band at the expense of other employees in the band. These commenters also believe this section of the proposed regulation offers too much opportunity 
                        <PRTPAGE P="56367"/>
                        for manipulation and inequity. We do not agree. The ability to adjust pay band minimums and maximums is an important flexibility that enables the agency to respond to changing labor markets. These flexibilities include the ability to raise the minimum rate of a pay band while not changing the maximum rate, as well as lowering or raising the maximum of a pay range without adjusting the lower range for the purpose of responding to labor market forces. When adjusting range rates under this authority, the ranges are adjusted worldwide throughout all of NSPS. With an NSPS population currently exceeding 180,000 employees, the sheer volume of employees assigned to any given pay band at any given time negates the ability of targeting range adjustments to a “few favorite employees”. Additionally, any adjustments to rate ranges must be coordinated with the OPM. 
                    </P>
                    <P>Another commenter questioned how often the Secretary can make rate range and other adjustments to pay. The proposed regulation generally does not specify when or how often the Secretary can authorize rate range and other adjustments, although it does require the Secretary to review established rate ranges for possible adjustment at least annually and adjust the maximum of each pay band at the time of a general salary increase under § 9901.323(a)(1). With the exception of the requirement to provide employees with ratings above unacceptable an increase of 60 percent of the GPI at the same time that a General Schedule annual adjustment takes effect under 5 U.S.C. 5303, and a requirement to adjust standard local market supplements in the same manner and to the same extent as corresponding locality payments under 5 U.S.C. 5304 and 5304a, the Secretary will make decisions regarding rate range and other adjustments to pay based on many variables, including mission requirements, labor market conditions, costs, pay adjustments received by other employees of other Federal agencies, and any other relevant factors. </P>
                    <P>One commenter recommended that the proposed regulation include a provision that allows the maximum of the rate range (including any occupational supplements) for physicians and dentists to keep pace with the maximum rates paid to the same occupations in the Veterans Health Administration under title 38, without large automatic pay increases. The commenter argued that the maximum of a range needs to be allowed to go higher without triggering a pay increase. The proposed regulation does not link adjustments in rate ranges to mandatory increases in base salary. Therefore, an adjustment in the maximum rate of a pay range can be made without triggering a mandatory increase in an employee's base salary. Consequently, no change has been made to the proposed regulation in response to this comment. </P>
                    <HD SOURCE="HD2">Section 9901.323—Eligibility for General Salary Increase </HD>
                    <P>This section describes the Secretary's authority and limitations on authority to grant both general salary increases and targeted general salary increases, as well as describing some requirements and criteria concerning these increases. </P>
                    <P>
                        This section generated a large number of comments. Many commenters argued that employees should receive 100 percent of the pay increases they would have received under the General Schedule (not the minimum increase of 60 percent of the GS GPI plus performance-based payouts). Of the commenters who focused on this issue, most expressed the view that the Governmentwide GS GPI was actually a cost-of-living adjustment (COLA), to which all Government employees were entitled. In fact, this view is incorrect; the GS GPI reflects the 
                        <E T="03">cost of labor.</E>
                         The Federal Employees Pay Comparability Act of 1990 provided two types of annual salary adjustments: an across-the-board increase to the entire General Schedule based on the Employment Cost Index (ECI), and a locality pay increase to the entire General Schedule, in a particular locality area, based on the salaries of non-Federal employees working in that area. The ECI portion is based on an annual comparison of ECI changes as measured by the Bureau of Labor Statistics (BLS). However, the BLS comparison measures the “cost of labor or wages” as opposed to the “cost of living.” Ultimately, the purpose of the GS increase is to ensure competitiveness with the private sector, versus offsetting increases in the cost of living. While discretion exists for employees to receive only a portion of the GPI as an across-the-board pay increase, the balance of the GPI also continues to be paid out as a base salary increase. The difference is that it is paid out based on performance as opposed to an automatic “across-the-board” increase. This enables DoD to pay the most competitive salaries to its highest performing employees. 
                    </P>
                    <P>Some commenters suggested that even employees who have reached a control point should receive the general increase, under the supposition that employees at the control point arrived there by being top performers. As indicated previously, under the proposed regulation and 5 U.S.C. 9902(c)(7), such employees do not lose entitlement to the NSPS general salary increase authorized under the proposed § 9901.323(a)(1). Limitations on exceeding control points under increases authorized under this section are limited to “additional general salary increases” under § 9901.323(a)(2) related to staffing difficulties and § 9901.323(c) pertaining to that part of the GPI paid out through the pay pool process. </P>
                    <P>One commenter suggested that employees who experience an unintended and unforeseen loss in pay as a result of an NSPS pay setting rule, or lack of a rule, when they move to an NSPS position from a non-NSPS position outside of the conversion process be eligible for a one-time retroactive adjustment to compensate for the loss if that loss or inequity is subsequently rectified by establishing or changing a rule to address the situation. Such an adjustment could be a mechanism for the Secretary to rapidly and immediately address or mitigate inequitable situations resulting from the operation of the NSPS regulation when a rule, or lack of a rule, has significant adverse impact on an employee. We have not revised this section in response to this comment. It is not feasible to pay employees for changes in pay-setting rules that were not in effect on the effective date of personnel actions affecting their pay. Standard practice throughout the Government is to base all personnel actions affecting Federal employees on the Federal laws and regulations applicable to them on the effective date of the action. It is also not reasonable to presume that every change in regulation would have been preferred earlier if only that authority were permitted earlier. </P>
                    <P>Another commenter pointed out that non-NSPS candidates applying in response to vacancy announcements should be notified that they will receive only 60 percent of the general increase and no performance pay if they accept a reporting date to an NSPS position just prior to January. However, § 9901.323(c)(1) of the regulation provides authority to the Secretary to make such employees whole by providing them an additional increase equal to the difference between the General Schedule GPI and the amount of the GPI applied as an NSPS across-the-board GPI. Therefore, such notification is not necessary. </P>
                    <P>
                        A labor organization representative erroneously stated that a determination to increase the minimum of the rate range would govern what the annual increase for acceptable employees will 
                        <PRTPAGE P="56368"/>
                        be and that employees in one pay band could get one percentage increase while other employees in other bands could get different percentages because of labor market conditions or because one occupational series is considered to be more important than another at a particular point in time. Under the proposed regulation, the link between adjustments in the minimum of a pay band and an employee's entitlement to have his or her base salary adjusted has been severed. Instead, annual general salary increases are provided in accordance with the requirements of this section. Nonetheless, it is true that pay band minimums and maximums can be adjusted differently from pay schedule to pay schedule based upon labor market considerations. Such adjustments to band ranges in relation to the labor market are appropriate. 
                    </P>
                    <P>Another labor organization representative stated that they interpret our Supplementary Information in the proposed regulation concerning § 9901.323(a)—which states, “As required by section 9902(e)(7), the portion of the GS GPI amount that is not provided as an NSPS general salary increase must be allocated to NSPS pay pool funding for the purpose of increasing base salary rates on the basis of employee performance”—to mean that DoD has to increase payroll funding each year by the amount of the GPI and that it can't give any part of it out as cash bonuses or use this money for other than employee compensation purposes. It is correct that the balance of the amount of the GPI which is not paid out as a general salary increase must be allocated to pay pool funding for the purpose of increasing rates of pay on the basis of employee performance. While this does not guarantee that each employee will receive the remaining percentage as an increase to base salary, it does mean, in the aggregate, the amount must be paid out as an increase to base salary. This portion of the pay pool funding may not be paid out as a bonus. </P>
                    <P>Another commenter suggested that § 9901.323(a)(2) be revised to allow the additional general salary increase to target specialties within an occupation, such as Electronics Engineer versus Mechanical Engineer, as well as specific locations. The commenter stated that the ability to target specific occupational specialties and locations would make it more likely that relief would be authorized, since it would not impact as many employees. Another commenter recommended the general increase under § 9901.323(a)(2) should not only permit targeting to specializations within an occupation, but also to segments of a pay band. We agree in part. The proposed regulation has been modified in response to these comments to enable targeting of specializations within an occupation. However, the proposed regulation was not modified to permit targeting by geographic location or parts of a pay band. The appropriate tool to recognize salary and market differences based on geographic location is through the use of the targeted local market supplement authority described in § 9901.332(c). We agree that there is a need to amend the proposed regulation to provide NSPS with the ability to design targeted local market supplements that will more effectively compensate employees where the higher market value has been recognized through the establishment of pay increases such as the OPM series of special salary rates, and we have amended our regulations at § 9901.331(b) to address this concern. </P>
                    <P>A labor organization representative protested that § 9901.323(a)(2) gives the DoD flexibility to provide some occupations within a pay band a larger increase than workers in other occupations in the same pay band based on factors other than individual performance. Some commenters objected to the perceived lack of objective criteria by which the Secretary would apply his or her authority to provide additional NSPS general salary increases under this section to employees in a designated occupational series in a pay band at times other than the effective date of the GS annual adjustment. They expressed concern that a general salary increase provided under this paragraph could be subject to abuse, discrimination, or inequity. There was also some confusion as to whether this was meant to be a different type of targeted local market supplement. It is not intended to function as a targeted local market supplement; rather, it is a one-time increase to base salary without geographic distinction. This provision provides an important tool to attract and retain employees performing critical national security missions. Contrary to concern about the perceived lack of objective criteria, the proposed regulation does identify four specific factors upon which these additional targeted salary increases will be based (labor market conditions, staffing difficulties, cost, and mission priorities). These criteria are much like the criteria governing the authority to provide special salary rates under the General Schedule. In fact, this authority and the targeted local market supplement are meant to be similar to the special pay rate flexibility available for General Schedule employees under 5 CFR 530.301. The NSPS “additional general salary increase” functions as a “catch up” increase in base salary. The “targeted local market supplement”, similar to a GS special rate, is paid out as a supplement to base salary. Both exist to address labor market and staffing difficulties. Consequently, to facilitate understanding of the “additional general salary increase” authority, we have renamed this authority “targeted general salary increase” to align the authority with the terminology used for other NSPS pay tools used to address staffing difficulties. </P>
                    <P>A few commenters recommended that even employees who received a rating of unacceptable should receive at least 60 percent of the annual increase. Providing this increase to individuals who receive a rating of unacceptable is counter to one of the fundamental goals of NSPS, recognizing and appropriately compensating employees based on performance. This fundamental goal was recognized by the Congress in the NDAA 2008. Therefore, no change was made in response to this comment. </P>
                    <HD SOURCE="HD3">Local Market Supplements </HD>
                    <HD SOURCE="HD2">Section 9901.331—General </HD>
                    <P>This section of the proposed regulation describes the process by which base salary ranges may be supplemented in appropriate circumstances by local market supplements. </P>
                    <P>
                        One commenter representing a labor organization suggested that, because employees with performance/complexity levels that put them at the top of the pay band will receive a partial or no increase when local market supplements are applied, the system does not adhere to principles of pay for performance. However, the only limits on paying a local market supplement in the proposed regulation is that associated with unacceptable performance under § 9901.332(d) and the maximum pay cap for adjusted salary under § 9901.312(b) and § 9901.332(b)(5) which limits adjusted salary to level IV of the Executive Schedule plus 5 percent (a maximum adjusted pay cap which is 5 percent higher than the General Schedule). We believe the American taxpayer favors a maximum pay cap that aligns NSPS salaries subordinate to Executive Level salaries in the Federal Government. Therefore, no change was made to the proposed regulation in response to this comment. 
                        <PRTPAGE P="56369"/>
                    </P>
                    <P>Another commenter suggested that § 9901.331(c) be clarified to clearly define the term “official worksite” for local market supplement entitlement. The commenter stated that with the Government's emphasis on telecommuting, clear and distinct information should be provided to define “official worksite.” We have not changed the proposed regulation in response to this comment. The regulation references the General Schedule regulations at 5 CFR 531.605, which define how the official worksite is determined for an employee who is covered by a telework agreement. </P>
                    <HD SOURCE="HD2">Section 9901.332—Standard and Targeted Local Market Supplements </HD>
                    <P>This section of the proposed regulation describes the Secretary's authority and limitations on authority as well as employee entitlements and coverage conditions concerning standard and targeted local market supplements. </P>
                    <P>Labor organization representatives commented that the discretion provided to the Secretary to set local market supplements is too broad and that the Secretary should gain approval from, rather than merely coordinating with, OPM prior to setting local market supplements. We note that under NDAA 2008, the Secretary is required to set and adjust standard local market supplements consistent with the setting and adjusting of corresponding General Schedule locality payments under 5 U.S.C. 5304 and 5304a. We view the Secretary's ability to establish targeted local market supplements as critical to appropriately compensating employees and believe appropriate parameters, including coordination with OPM, provide the necessary safeguards to address concerns. We have, however, provided clarity to the information concerning targeted local supplements by specifying that they are meant to address significant recruitment and retention problems. </P>
                    <P>Other commenters from labor organizations suggested that the local market supplement should not be dependent on employee performance; rather, poor performance should be reflected in base pay. Denying unacceptable performers adjustments in both their base salary and any applicable local market supplement clearly conveys the Department's desire for emphasis on performance. It is consistent with a fundamental principle of NSPS, that is, we want to acknowledge and reward employees for their performance. At the same time, we want to assure the American taxpayer that the Department is not continuing to pay salary increases to poor performers. This goal was recognized by the Congress in the NDAA 2008. </P>
                    <P>One commenter asked how NSPS addresses the situation involving an employee who moves to an NSPS position located in a geographic area where pay is not computed using adjusted rates (i.e., a rate that includes locality pay). If a salary-setting situation does not meet the criteria for adjustment based on adjusted rates of salary, the salary is set by comparison of base rates of salary. Where salary is set using comparisons of adjusted rates, locality pay is considered part of the adjusted rate of a General Schedule employee in the same manner as targeted local market supplement is considered part of the adjusted salary rate for NSPS employees. </P>
                    <HD SOURCE="HD2">Section 9901.333—Setting and Adjusting Local Market Supplements </HD>
                    <P>This section addresses the setting and adjusting of standard and targeted local market supplements. </P>
                    <P>Commenters from labor organizations suggested that basing the size of local market supplements on available funds might demotivate current employees and lead to difficulty in attracting high-quality new employees to DoD. Standard local market supplements are determined in the same manner and amount as provided to General Schedule employees under 5 U.S.C. 5304 and therefore are not considered in terms of availability of funds. However, in determining the Department's response to staffing shortages or difficulties, it is only prudent to consider cost in determining whether or not to approve a targeted local market supplement, and for what amount. It is possible that alternatives are available that will be less costly or that the cost would jeopardize other mission priorities. Cost is an appropriate factor for consideration in the use of optional pay tools. </P>
                    <P>A commenter expressed concern that the targeted local market supplement as discussed in § 9901.333(b) will be subject to abuse and discrimination and will not be transparent or credible to employees. Section 9901.332 of the proposed regulation has been modified to reflect that the purpose of a targeted local market supplement is to address significant recruitment or retention problems. Given the parameter in which it is to be used, the requirement for coordination with OPM, and the requirement for an annual review of each targeted local market supplement, it is difficult to envision how this authority might be used in a discriminatory manner. We believe the regulation provides objective criteria, transparency and credibility to such determinations. </P>
                    <P>Another commenter suggested that a subparagraph be added to this section to clarify that, if the standard local market supplement exceeds the targeted local market supplement, the standard local market supplement should take effect corresponding to the same date of GS locality payments. The commenter stated that, if a targeted local market supplement is larger than the GS locality, at DoD's discretion employees can receive the higher supplement because there are no distinct words to protect people if the targeted local market supplement falls below the GS locality payment. We have not revised this section in response to this comment. In accordance with § 9901.332(c) of this regulation, a targeted local market supplement applies to an employee eligible for a standard local market supplement only if the targeted local market supplement is a larger amount. While the targeted local market supplement does not apply to everyone in a pay band, once a category of employees has been identified to receive it, all employees in that category receive the payment provided they have a rating of record above unacceptable. The effective dates of targeted local market supplements are not tied to the effective dates for adjustments in the standard local market supplement in that targeted local market supplements can be approved throughout the year. Tying the effective date of a targeted local market supplement to that of the standard local market supplement could result in costly manpower delays in addressing significant recruiting or retention problems. </P>
                    <HD SOURCE="HD2">Section 9901.334—Eligibility for Pay Increase Associated With a Supplement Adjustment </HD>
                    <P>This section provides that an employee must have a rating of record above “unacceptable” to receive a pay increase associated with a local market supplement adjustment. </P>
                    <P>
                        One commenter posed several questions related to paragraph (b) of this section, which states that once an employee has a new rating of record above unacceptable, the employee is entitled to the full amount of any applicable local market supplement effective on the date of the first adjustment in that local market supplement occurring on or after the effective date of the new rating of record above unacceptable. The commenter wondered whether the effective date of the new rating of record was the day the 
                        <PRTPAGE P="56370"/>
                        supervisor signed it, after it had been approved by the Pay Pool Panel, or when it was entered into DCPDS. Also, the commenter asked if an employee has a new rating of record signed by the supervisor but not yet entered into DCPDS, could that rating of record be missed when a change in the local market supplement takes place (particularly if the change takes place at any other time of the year other than the first pay period in January)? The commenter went on to suggest that § 9901.334(b) be made clearer by stating that the employee is entitled to the local market supplement occurring on or after the effective date, as specified in § 9901.412(b)(2) of subpart D, of the new rating of record above unacceptable. We agree that the effective date of a rating of record should be clarified. Consequently, we have revised this paragraph to link to information in subpart D which discusses the effective date of ratings of record (§ 9901.411(d)). 
                    </P>
                    <P>Commenters from labor organizations suggested that, while denying underperforming employees their within-grade increase is appropriate, it is inappropriate to deny them the local market supplement as well, since the LMS should be awarded regardless of performance. Denying unacceptable performers adjustments in both their base salary and any applicable local market supplement clearly conveys the Department's desire for emphasis on performance. It is consistent with a fundamental principle of NSPS; that is, we want to acknowledge and reward employees for their performance. At the same time, we want to assure the American taxpayer that the Department does not continue to increase the salary of poor performers. </P>
                    <HD SOURCE="HD3">Performance-Based Pay </HD>
                    <HD SOURCE="HD2">Section 9901.341—General </HD>
                    <P>This section briefly describes the performance-based pay component of the pay system established under subpart C. </P>
                    <P>
                        Labor organization representatives commented that performance-based payouts of raises or bonuses should not be given to teams or organizations as opposed to individuals, because this practice does not truly reward individual performance. Under the NSPS concept, organizational and team performance can be considered in assessing an individual's accomplishments. We expect that the importance of teamwork and cooperation will continue to be reinforced in the expression of performance standards and performance objectives. Through communication, ongoing feedback, performance rating and performance rewards, the importance of teamwork and cooperation should be understood by employees. In addition, the regulations clearly describe in the definitions of 
                        <E T="03">job objective</E>
                         and 
                        <E T="03">unacceptable performance</E>
                         that the measurement of an employee's performance in determining his or her rating is based on the expectations set for the individual employee during the appraisal period. When organizational or team performance is considered in an employee's performance expectation, the assessment is based on the efforts, cooperation, and contributions of that individual employee to the success of the team and organizational goals. No change has been made to the proposed regulation based on these comments. 
                    </P>
                    <P>Commenters suggested that two employees could be doing the same exact work of the same exact quality, but because they are assigned to two different pay pools, their compensation will differ because it is now being dictated by the performance of the group. It is true that a pay pool that has a higher percentage of high-performing employees may have a different share value than a pay pool with a lower number of high-performing employees because the payouts are based on shares of a common fund. However, most pay pools are of sufficient size that the rating distribution normalizes to the standard population. Where this does not occur, we find we are similar to the General Schedule where employees are sometimes awarded differently for similar levels of performance. </P>
                    <HD SOURCE="HD2">Section 9901.342—Performance Payouts </HD>
                    <P>Section 9901.342 describes the management and structure of performance pay pools and provides for the allocation and distribution of performance pay funds. </P>
                    <P>Labor organization representatives commented that, by employing Pay Pool Panels and Pay Pool Managers, the proposed regulation attempts to override any current locally bargained award panels consisting of union representatives along with managers. However, we note that performance-based pay and pay pools did not exist for most employees prior to NSPS. Where such pay pools or collective bargaining provisions related to 5 U.S.C. chapter 45 (dealing with incentive awards) existed prior to conversion to NSPS, DoD will continue to honor its collective bargaining obligations under 5 U.S.C. chapter 71. Under chapter 71, these regulations cannot override current collective bargaining agreements. No change was made to the proposed regulation based on these comments. </P>
                    <P>Several commenters suggested that Pay Pool Managers, Pay Pool Panels, and Performance Review Authorities are additional layers between an employee's supervisor and the actual payout the employee receives. These extra layers of management, according to the commenters, are removed from the employees they rate, and they will likely have no direct knowledge of the employee's performance during the year. </P>
                    <P>Pay pool panels serve as calibration committees and are comprised of management officials who are usually in positions of line authority or in senior staff positions. As such they are familiar with the organization's mission and goals. First-hand knowledge of each employee is not necessary. The pay pool process and the higher-level reviews provide the necessary checks and balances to ensure that performance decisions are made in a careful, deliberative environment that ensures a common understanding of performance, share assignment, and payout distribution criteria that is applied across the pay pool. The Pay Pool Panel members ensure consistency by reviewing self and supervisory assessments (both prepared by personnel knowledgeable of employee's work) and comparing accomplishments to the employee's stated job objectives and performance criteria. If there are any questions regarding the recommended rating for an employee or the panel is likely to change the rating official's recommended rating, the supervisor or rating official will be requested to present further information or justification to the pay pool. Additionally, employees who feel their final job objective ratings or rating of record does not properly reflect their work may seek reconsideration consistent with § 9901.413 of the regulation. No change has been made to the proposed regulation based on these comments. </P>
                    <P>
                        Labor organization representatives also expressed disapproval of the idea of sub pay pools, suggesting that the existence of large pay pools that require sub pay pools sets up a bureaucratic structure that separates the employee from the performance payout, obscures the connection between pay and performance, and increases the chances for erroneous and discriminatory pay decisions. In a further argument against sub pay pools, representatives of labor organizations suggested that § 9901.342(b)(3) be deleted because the sole purpose of sub pay pools is “reconciling ratings of record” and 
                        <PRTPAGE P="56371"/>
                        consequent payouts, and the concept of “reconciling ratings” is improper, in the view of the commenters. We disagree. Reconciling ratings of record is an important safeguard for employees who are members of a pay pool. Reconciliation of ratings ensures that employees' pay is not harmed by the effect of “high” and “low” raters. Sub pay pools are established to create panels that can more effectively manage the reconciliation of ratings in larger pay pools. The duties and responsibilities of the sub pay pool are the same as that of the pay pool but for a smaller section of the pay pool. In addition, the sub pay pool operates within the requirements and guidelines established for the pay pool to which they belong. The overall Pay Pool Panel then reconciles the recommendations of the sub pay pool panels. Generally, the same size pay pool that justifies a sub pay pool panel (around 150 pay pool members) is also of a size that is less apt to result in a skewed rating distribution in comparison to the overall Department. This is because rating distributions tend to “normalize” to a distribution reflective of the overall organization given sufficient size populations. No change has been made to the proposed regulation based on this comment. 
                    </P>
                    <P>Another commenter requested clarification regarding what level of management, referred to in § 9901.342(b)(3), decides when to establish sub pay pools. Due to the size of DoD and the subsequent variable in organizations within DoD, these matters will be specified further when implemented by the DoD organizations. </P>
                    <P>One commenter suggested that minimum levels of funding for each pay pool must be established. The proposed regulation clearly indicates that the Secretary determines a percentage of pay to be included in pay pools and paid out in accordance with accompanying implementing issuances. The implementing issuances give Components the discretion to set funding for pay pools as long as they meet the minimums identified by the Secretary. Such funding floors are established outside of the regulation and are often dependent on Congressional determinations concerning general pay increases under 5 U.S.C. 5303. No change has been made to the proposed regulation based on this comment. </P>
                    <P>One commenter questioned whether it is expected that all of the money assigned to a pay pool will be paid out, or whether managers might be able to divert some funds to other uses or save them for use the following year. We agree that proper funding of pay pools is fundamental to the success of NSPS. Section 9902(e)(6) of Public Law 110-181 clearly states that the amounts allocated for compensation of DoD civilian employees for NSPS shall be available for this purpose only. In order to comply with this statutory requirement, DoD funding floors for pay pools must be met in the aggregate at the Component level. Senior-level Component officials must certify that they have met this funding floor and have expended the resources within their organization. No change has been made to the proposed regulation based on this comment. </P>
                    <P>Commenting on § 9901.342(f), one commenter suggested that contributing factors add a level of complexity to the overall rating process far beyond their value and increase the time to write and evaluate both performance assessments. The commenter recommended eliminating contributing factors as a separate step in the rating process, to include eliminating the “plus or minus” concept and instead require consideration of these factors when evaluating an employee's performance. The specifics of how contributing factors will be applied in the NSPS evaluation of performance are not addressed in this regulation. Therefore, no change can be made to this proposed regulation in response to this comment. However, contributing factors will play an important role in defining an employee's performance by reflecting the manner of performance that is important for the accomplishment of the job objective. The specifics of this role will be outlined in implementing issuances. This paragraph has been modified, however, to eliminate any confusion regarding the consideration of contributing factors in determining share assignments. </P>
                    <P>A few commenters recommended a revision to § 9901.342(f) to assign shares as follows: Level 5—2 shares; Level 4—1.5 shares; Level 3—1 share; Level 2—0 shares; Level 1—0 shares. Per the commenter, the rationale for this suggested change is that performance payouts should be based on objective, mathematical calculation based on performance rating. The commenter expressed belief that the number of shares for each performance level should be fixed. Further, the variation should be proportionate to the true variation reflected in the definitions of the levels. In the commenters' view, it is appropriate that a Level 5 performer receive twice the number of shares as a Level 3 performer, not up to six times as many. Similarly, another commenter proposed to award partial shares for employees with a Level 3 rating of record. </P>
                    <P>The Department recognizes that a valid, reliable, and transparent performance management system with adequate safeguards for employees is essential. However, it must also avoid a rigid, one-size-fits-all approach by providing the flexibility to address a variety of circumstances. By allowing a range of decision points regarding the number of shares, managers can more appropriately address the variety and complexity of factors that relate to employee compensation. The regulations provide the parameters and criteria for the performance-share calculation methodology in sufficient specificity so that managers, employees, and employee representatives can better understand how performance pay increases will be determined and paid. These criteria permit consideration of such factors as the employee salary in relation to control points and pay band maximums, recent salary increases, raw performance scores, and the employee's overall contribution to the mission of the organization. This enables organizations to recognize performance and reflect such market trends as accelerating salaries for employees at lower ends of pay ranges and decelerating salaries at higher ends of market ranges. No change has been made to the proposed regulation based on these comments. </P>
                    <P>Several labor organizations and other commenters expressed concern about grouping supervisors and upper-level managers in the same pay pools as the non-management employees they supervise. These commenters expressed concern that, by combining supervisory and nonsupervisory personnel, there would be a temptation to lower nonsupervisory ratings in order to produce higher payouts for supervisors. These regulations and the implementing issuances currently provide safeguards to support the neutrality and impartiality of pay pool proceedings. The responsibilities of a Pay Pool Manager include the review of supervisors' recommended ratings of record for consistency and equity across organizational units and to guard against potential discrimination or politicization before finalizing ratings. No change has been made to the proposed regulation based on these comments. </P>
                    <P>
                        One commenter indicated that factors that management may consider in determining the amount to be paid out as a bonus versus an increase in the rate of base salary do not include the option to establish a default split based on the composition of pay pool funds allocated 
                        <PRTPAGE P="56372"/>
                        for payout as a bonus versus a base salary increase. Section 9901.342(g)(4) has been changed to add to the factors that management may consider in determining a pay pool payout distribution, a default split for the pay pool. This is in keeping with the practice of many NSPS pay pools to consider the percentage of pay pool funds applied to salary increases versus bonuses when determining how to distribute the payout between bonus and base salary increase for each employee. 
                    </P>
                    <P>One commenter suggested that § 9901.342(g)(5) be revised to include that an employee who has reached the maximum rate of the band will receive his or her performance payout as a bonus in lieu of an increase to base salary. This section has been revised to include this provision. </P>
                    <P>Another commenter requested clarification as to the flexibility of granting a performance pay increase that exceeds an established control point. The determination to grant such an increase is allowable but is dependent on the criteria upon which the control point for that pay band is based. These criteria may include performance factors or market values. For example, if the criteria for establishing a control point are based on performance factors, conceivably an employee could exceed the identified criteria and be provided a pay increase in excess of the established control point based on the employee's performance. No change has been made to the proposed regulation based on this comment. </P>
                    <P>A commenter requested clarification regarding whether an employee would be eligible for a performance payout if they move out of NSPS on a permanent move after the end of their rating cycle but move back into an NSPS position before the effective date of the payout. Employees who move out of NSPS after the end of the rating period are not eligible for the NSPS payout for that performance cycle whether or not they return to NSPS prior to the effective date of the payout. Such employees would become entitled to the pay progression mechanisms of the gaining personnel system. For example, if an employee moves to the General Schedule, their time in NSPS following their last equivalent increase would count toward the next General Schedule increase. If none was due the employee during the period of time under the General Schedule, the option to provide a WGI buy-in adjustment under § 9901.351 may be applied upon their return to NSPS. Provided the service performed under NSPS and the General Schedule was creditable for WGI purposes, the service covered by the NSPS performance period would become creditable toward the WGI adjustment upon return to NSPS. </P>
                    <P>Also, a commenter requested clarification regarding an employee's entitlement to a performance payout in a situation when the employee leaves one pay pool after the end of his or her rating cycle and moves to another pay pool before the effective date of the payout. We agree and have added clarifying language under § 9901.342(g)(9). In response to several comments requesting increased transparency in the NSPS performance management system, § 9901.342(g)(10) is added requiring NSPS organizations to share average rating, ratings distribution, share value (or average share value), and average payout with NSPS employees. Organizations must ensure that the sharing of this information does not compromise the identities of NSPS employees in violation of the Privacy Act. </P>
                    <P>Another commenter suggested that an NSPS employee who earns a bonus for the performance year but retires before the end of the calendar year should still be able to receive a bonus payment. The regulation clearly states that an employee who is no longer covered by NSPS on the effective date of the payout is not entitled to a performance-based payout, which includes a bonus. Such employees may be considered for an incentive award action under 5 U.S.C. chapter 45 if performance during the applicable period merits recognition. </P>
                    <P>Many commenters (both individual commenters and labor organization representatives) expressed concern that, since bonus payouts are not considered when calculating retirement benefits, retirement benefits will be lower under NSPS than they would be under the GS system. As stated previously, since existing grade-based systems such as the General Schedule (GS) and the Federal Wage System (FWS) do not calculate pay received as bonuses toward defined benefit retirement plans, retirement benefits cannot be lower under NSPS than they would be under the GS system. NSPS, in the aggregate, does not substitute bonus payments for base salary increases. Performance-based bonuses are funded in addition to payment of dollars that were previously spent on base pay increases under the General Schedule and continue to be spent on base salary increases under NSPS. Additionally, like NSPS, existing GS and FWS systems do not permit pay increases beyond the limits of established ceilings (maximum rate of grade levels). However, within NSPS, those at the top of their control point or pay band must still receive a payout, based on performance shares, in the form of a bonus, which is a clear advantage for NSPS employees. No change has been made to the proposed regulation based on these comments. </P>
                    <P>One commenter requested that the proposed regulation specify that prorating of performance payouts is not mandatory. The proposed regulation gives the Secretary the authority to issue implementing issuances regarding prorating payouts for employees. The implementing issuances give the Components discretion to determine whether prorating is required during the performance cycle. We believe that the Components can best make the determination of whether or not prorating is warranted, such as when an employee is on extended unpaid leave. No change has been made to the proposed regulation based on this comment. </P>
                    <P>
                        Additional commenters expressed concern that an employee returning from uniformed service who does not have an NSPS rating of record may not be eligible for a bonus or pay increase if the employee is at the top of the control point or pay band. These commenters suggested that the provisions of § 9901.342(i) be changed to provide that employees returning after performing uniformed military service are eligible for performance-based pay pool bonuses if otherwise eligible by share assignment and payout distribution. Adjustments for employees returning from uniformed service are determined in accordance with § 9901.342(i). The purpose of this provision is to meet the intent of the Uniformed Services Employment and Reemployment Rights Act (USERRA) to preserve the earning power of uniformed service members by ensuring that their salaries continue to progress at the same level they would have if they had not served on military duty covered by that law. This preservation of earning power is accomplished by granting applicable raises in the pay schedule. The provision does not seek to award pay for work not performed—that is, the intent is to adjust an employee's pay rate similar to how it would have been adjusted had the employee not left, not to entitle the employee to pay for periods he or she was absent (other than that associated with a paid leave status). Similarly, pay in the form of bonuses for periods of time during which the employee did not perform work would not be paid if the employee is not entitled to an NSPS rating of record, since this would constitute money not earned. No change has been made to the 
                        <PRTPAGE P="56373"/>
                        proposed regulation based on these comments. 
                    </P>
                    <P>One commenter suggested that § 9901.342(i) and (j) clarify when performance payouts are “effective” and/or “paid.” These sections have been revised to add clarification to the effective dates in each of these circumstances. </P>
                    <P>A commenter recommended that § 9901.342(i) through (l) be changed to reflect that when an employee, who does not have an NSPS rating of record for an appraisal period, has his or her base salary increase determined on an average base salary granted to other employees with the same rating or a modal rating that the average should be based upon all employees in the same pay pool as opposed to including only those employees in the same pay schedule and pay band. The commenter noted that inclusion of this broader group in the calculations will prevent inappropriate and inequitable salary determinations. Paragraphs (i) through (l) of this section have been revised to use the average salary increase of the entire pay pool. </P>
                    <P>One commenter questioned whether, in § 9901.342(k), it was an oversight or intentional that employees working on “official time” (union officials) and those on extended paid leave do not receive the general pay increase. The employees identified in this section are in a pay status and are therefore covered by the provisions of § 9901.323 and will receive the applicable general pay increase at the same time as employees who do not meet the criteria for specially situated employees. No change has been made to the proposed regulation based on this comment. </P>
                    <P>Commenters also expressed concern regarding § 9901.342(k) which calls for a payout and share distribution based on the “modal rating” as using an “assumed rating” of a sort that is outlawed by OPM. The comments reflect confusion regarding the use of modal ratings under this section. Modal ratings as identified in this section are used only to determine a performance pay increase and not for the purpose of assigning a rating of record. Once the performance pay increase is determined, the modal rating serves no other purpose. No change has been made to the proposed regulation based on these comments. </P>
                    <P>Labor organization representatives sought clarification in the proposed regulation regarding exactly who—the Secretary, the Components, or another delegate—has the authority to set rules to determine performance payouts and the distribution of payouts between salary increases and bonuses. The Pay Pool Manager, as defined in § 9901.103, is designated to manage the pay pool to include approving recommended share assignments and payout distributions. However, these determinations must be made consistent with the organization's business rules. Such rules may be determined at the Component level or lower if delegated by the component. No change has been made to the proposed rule based on these comments. </P>
                    <P>One commenter suggested that pay increases or bonuses based on 100 percent union duties would seem to pay union officials for not performing any work for the agency. Providing salary increases to full-time union officials is consistent with Governmentwide practices regarding full-time union officials under 5 U.S.C. chapter 71. However, consistent with other Governmentwide systems, bonuses are not paid under NSPS. No change has been made to the proposed regulation based on this comment. </P>
                    <P>Finally, labor organization representatives expressed concern that DoD will not be able to adequately fund a pay-for-performance system because it does not control its budgets. They further state that DoD, like other Federal agencies, depends on Congress for its appropriations, and today's Congress cannot bind future Congresses to adequately fund a pay-for-performance system. In establishing the NSPS statute, Congress provided in section 9902(e)(4) of title 5, U.S. Code, that, through FY 2012, to the maximum extent practicable, the aggregate amount allocated for compensation of DoD civilian employees under NSPS will not be less than if employees had not been converted to NSPS. Section 9902(e)(5) additionally provides that after FY 2012 the Department will develop a formula that ensures that, in the aggregate and to the maximum extent possible, employees are not disadvantaged in the overall amount of pay available as a result of conversion to NSPS, while providing flexibility to accommodate changes in the function of the organization, changes in the mix of employees performing those functions, and other changed circumstances that may affect pay levels. We therefore believe that NSPS will be properly funded and have made no change to the proposed regulation based on these comments. </P>
                    <HD SOURCE="HD2">Section 9901.343—Pay Reduction Based on Unacceptable Performance and/or Conduct </HD>
                    <P>This section outlines parameters for reducing employee pay based on unacceptable performance and/or conduct. </P>
                    <P>Representatives of several labor organizations objected to the change in the proposed regulation that limits the range of a pay reduction under the circumstances described in this section to 5-10 percent of base salary (rather than 1-10 percent), expressing concern that the new language limits the ability of managers to choose a lesser penalty for unacceptable performance/conduct when warranted. Pay reductions based on unacceptable performance and/or conduct are not required in all cases and are in fact discretionary. However, to the extent that a manager determines that unacceptable performance and/or conduct warrants a pay reduction, a pay reduction of at least 5 percent is necessary to achieve and retain a high-performing workforce. No change has been made to the proposed regulation based on these comments. However, we have made minor editorial changes to the language in § 9901.343 for enhanced clarity and for consistency with language in related provisions in §§ 9901.353(f) and 9901.355(b)(4). </P>
                    <P>Several commenters requested clarification concerning the “applicable adverse action procedures” that must be applied before reducing an employee's pay due to unacceptable performance and/or conduct. The language in the proposed regulation is meant to highlight that adverse action procedures must be followed when reducing an employee's pay. For employees under NSPS, procedures provided under 5 U.S.C. chapter 75 apply whether or not the regulation specifically cites chapter 75. No change has been made to the proposed regulation based on these comments. </P>
                    <HD SOURCE="HD2">Section 9901.344—Other Performance Payments </HD>
                    <P>This section describes who has authority to grant other performance payments, reasons for awarding these types of payments, employee eligibility requirements, and limits on other performance payments. </P>
                    <P>
                        Labor organization representatives commented that this section actually addresses bonuses and quality step increases and attempts to override existing collective bargaining agreements, which often include pre-existing negotiated award programs. We disagree. This paragraph does not address quality step increases because they do not exist under NSPS. Under 5 U.S.C. chapter 71, Governmentwide regulations cannot override pre-existing agreements that conflict with the regulations. However, these agreements would have to be brought into compliance with the regulations when the agreements expire or are up for 
                        <PRTPAGE P="56374"/>
                        renegotiation. No change has been made to the proposed regulation based on these comments. 
                    </P>
                    <P>Commenters also inquired about the source of funds for “Other Performance Payments” and wondered whether these payments might lower the amount of funds for the pay pools for performance payouts for other employees. Additionally, one commenter wanted assurance that the Extraordinary Pay Recognition (EPR) and Organizational Achievement Recognition (OAR) will not be used to give preference to certain workers over others. These achievement recognition awards are funded from a source outside of the pay pool. As indicated in the proposed regulations, EPR and OAR are awarded based on performance and restricted to specific criteria for each recognition award. In the case of the EPR, an employee must have a rating of record of at least a Level 5 in order to be eligible for the award; in the case of the OAR, when awarded, it applies to all employees in the organization who have a rating of record of at least a Level 3. However, distinctions in OAR awards may vary based on the rating of record. These criteria alone serve to mitigate against favoritism, cronyism, and other actions that violate merit system principles. No change has been made to the proposed regulation based on these comments. </P>
                    <P>Finally, one commenter objected to language in § 9901.344(b)(1) stating that “the future performance and contribution level exhibited by the employee will be expected to continue at an extraordinarily high level.” The commenter pointed out that no one can continuously perform at an extraordinary level, for then what had been extraordinary would become “ordinary” performance for that employee. The purpose of the EPR is to reward exceptionally high-performing employees whose performance and contributions to the organization are of an exceedingly high value based on an individualized assessment. There is the expectation that this or a higher level of performance will continue in future years. Although the increase granted by the EPR is permanent and does not require future revalidation, the performance objectives upon which the employee will be evaluated in the future will reflect the higher level of expectation. We did however, modify this section to clarify that the expectation of higher-level performance in the future is associated with an EPR paid out as an increase to base salary as opposed to a bonus. We believe that the EPR is an important flexibility and have made no additional change to the proposed regulation based on this comment. </P>
                    <HD SOURCE="HD2">Section 9901.345—Accelerated Compensation for Developmental Positions (ACDP) </HD>
                    <P>This section describes how ACDP payments may be awarded and under what circumstances. </P>
                    <P>This change to the proposed regulation generated several positive comments from individuals who applauded the expansion of ACDP payments. However, some commenters representing labor organizations suggested amending this provision to allow collective bargaining of this issue. Concerns about collective bargaining rights have been addressed in “Collective Bargaining and Labor Relations” located under “Major Issues.” </P>
                    <P>Representatives of labor organizations also questioned the implication in this section that Components have the authority to choose whether or not to provide ACDP increases. These representatives suggested the institution of procedures governing the advancement of employees in developmental positions. The Department determined that such matters should be governed by Component policies, within the parameters provided by the proposed regulation. No change has been made to the proposed regulation based on this comment. </P>
                    <P>
                        Another labor organization representative indicated that the proposed regulation is unclear regarding whether there is any limit on the number of ACDP increases that may be given or whether there is a specific interval between them. The inquiry also seemed to imply that these increases are “promotions.” Although ACDP increases are designed to provide accelerated pay progression for entry/developmental positions, these increases are not promotions, and this terminology should not be used in order to avoid conflict and confusion with the meaning of that term under NSPS. Section 9901.103 provides a definition of 
                        <E T="03">promotion</E>
                         under NSPS; § 9901.354 describes how to set pay upon promotion. We did not prescribe any limit on the number of ACDP increases eligible employees may receive, nor the interval(s) at which they could occur. Such parameters, if any, would be linked to the specifics of Component training programs or developmental activities. Components choosing to provide ACDP increases must establish and document growth and development criteria by which additional pay increases will be determined. 
                    </P>
                    <P>Several commenters inquired whether or not the ACDP applied to student programs. In response to these comments, the proposed regulations have been changed to include positions assigned to the Student Career Experience Program. </P>
                    <P>Commenters suggested expanding the ACDP concept to engineers/technicians and employees in pay band 2 to make NSPS more comparable to the grade progression available within the GS system. This suggestion does not mirror the intent of NSPS to achieve pay progression beyond the trainee levels primarily through performance-based pay increases. The cost of providing increases similar to GS grade progression increases would offset the ability to award pay pool base salary increases, thus jeopardizing the linking of pay and performance as intended by the enabling legislation for NSPS. This is because pay pools are funded, in part, by money that previously was applied to GS promotion increases to grades that no longer exist under NSPS. No change has been made to the proposed regulation based on these comments. </P>
                    <P>Other commenters asked that the pay-setting guidance for employees in developmental positions under the GS scale (example: GS-12/13 or GS-13/14) also apply to those who applied but were not selected until after their agencies transitioned to NSPS. Again, we reiterate that the intent of NSPS is not to replicate the GS pay system but rather to redirect pay progression to a performance-based pay system as opposed to a pay progression based on position moves. ACDP provides for accelerated pay progression for the lowest ranges of journey level work in recognition of the inability to match market-based pay progression trends via performance-based payouts alone. For this reason, ACDP is limited to Pay Band 1 and employees in the Student Career Experience Program. No change has been made to the proposed regulation based on these comments. </P>
                    <P>
                        One commenter questioned why accelerated awards are given to employees with a rating of record of Level 3, suggesting that this award should be given only to those achieving a rating of Level 4 or better. The implication by the commenter is that a Level 3 rating reflects less than the expected performance. In contrast, Level 3 is seen as recognizing those employees who performed their identified responsibilities and in doing so effectively met all of their performance expectations. The regulations clearly state that Components choosing to provide these increases must develop criteria by which the additional pay 
                        <PRTPAGE P="56375"/>
                        increases will be determined. If an employee meets the identified criteria, and has met his or her performance expectations, the employee should be entitled to be considered for the pay increase. No change has been made to the proposed regulation based on this comment. 
                    </P>
                    <HD SOURCE="HD3">Pay Administration </HD>
                    <HD SOURCE="HD2">Section 9901.351—General </HD>
                    <P>This section outlines general provisions of pay administration including geographic recalculation, within-grade increase (WGI) adjustment, general pay-setting rules, pay periods and hourly rates, rate comparisons upon movement to an NSPS position, and setting of pay based on annual rates received by an employee as a teacher. </P>
                    <P>Several commenters questioned why the within-grade increase (WGI) adjustment equivalent applies to GS employees moving to NSPS, but does not apply to Federal Wage System (FWS) employees and other employees in step-type programs. In response to these comments, the use of this authority has been expanded to include moves from FWS to NSPS. </P>
                    <P>Another commenter noted that it appears that an employee may receive both a prorated WGI and up to a 5 percent increase upon reassignment, though it is not explicitly stated, and recommended this be clarified. We agree and have clarified this point in the regulations. </P>
                    <P>One commenter suggested adding the following sentence to the end of § 9901.351(b): “This adjustment may be made prospectively for NSPS covered employees whose pay was not set in this manner prior to the effective date of this regulation.” According to the commenter, this addition would allow Components to make employees “whole” who lost their targeted LMS when they were a “willing accession” to NSPS and not converted to NSPS with their organization. Another commenter suggested that we make a WGI buy-in for management directed reassignments retroactive to previous legislation to ensure all personnel are treated fairly. There is no provision that allows for regulations to apply retroactively unless an administrative error had occurred. There was no administrative error made in the pay setting for these employees; the regulations in effect at that time did not allow for this type of adjustment. These employees will have the opportunity to be fairly compensated for the work they perform under the NSPS structure of pay-for-performance. </P>
                    <P>Another commenter cited § 9901.351(c), saying that normally you would not receive any type of pay increase on an individual realignment action and there does not appear to be a way that you could currently process something like this. In response to this comment, if an employee is realigned by management from a GS or FWS position into an NSPS position, he or she will be eligible for this provision. The personnel system will be updated to allow for this type of action to be processed. </P>
                    <HD SOURCE="HD2">Section 9901.352—Setting an Employee's Starting Pay </HD>
                    <P>This section describes the Secretary's authority to set the starting base salary for individuals newly appointed or reappointed to the Federal service. </P>
                    <P>One commenter questioned what an employee's current rate of pay has to do with the value of a prospective employee. “Current salary” is identified under this section as one of many factors to be considered in setting an employee's starting pay. Other factors include labor market considerations; the skills, knowledge, and/or education possessed by the candidate; critical mission or business requirements; and salaries of other employees in the organization performing similar work. “Current salary” is considered a factor in setting salary in that it helps the manager to establish a salary level high enough to attract a candidate, but moderate enough to permit salary growth over a period of time. A manager should look at all of the factors listed under this section, when considering the setting of starting pay for a new employee, including “current salary.” </P>
                    <P>Another commenter recommended adding additional considerations to § 9901.352(a) such as fiscal constraints of the organization, the total remuneration being provided to employees, and historical recruitment and retention data for hard-to-fill positions. We don't feel that it is necessary to add these factors, as they can be considered under the current factors listed such as availability of candidates and business requirements of their respective organizations. </P>
                    <P>Another commenter recommended that the rules in this section be used for current Federal employees who move to NSPS from other pay systems through competitive procedures. The rules addressed in this section permit setting of salaries anywhere within a pay band for employees newly hired within the Federal Government. The competitive selections of current Federal employees are most appropriately processed as promotions, reassignments, or reduction in band actions under the NSPS pay setting regulations. This allows these selectees to be fairly treated without disadvantaging current NSPS employees. NSPS strives to function in a manner that sustains fair competition with other Federal agencies. Changing the regulation to allow setting of salaries anywhere within the pay band for current Federal employees would create an unfair competitive advantage for DoD when it comes to the employees of other Federal agencies. </P>
                    <P>In a related comment, a commenter pointed out that the break-in-service requirement for reappointed individuals appears to create a loophole for employees in the NSPS pay-setting process and is also inconsistent with other break-in-service rules under the GS system. Specifically, they expressed concern that the proposed rule “on break in service for at least 1 full day” creates a situation where an employee who resigns for a one-day period can have his or her pay set anywhere within a rate range as opposed to being subjected to internal pay-setting rules for other employees (e.g., the 5 percent cap on reassignments). The commenter also notes that our proposed rule is inconsistent with definitions previously released in processing guidance for NSPS personnel actions. The requirement for a break in service was added to the regulation to create uniformity and consistency in application of pay-setting rules for new appointments and reappointments. As a condition for permitting use of pay-setting rules for reappointments, the 2005 regulation required an employee to have been separated and subsequently reemployed. This language resulted in inconsistent application of the rule and a request that we clarify our language. </P>
                    <P>We are aware that different break-in-service rules are used for different reasons (e.g., 90 days for superior qualification appointments under 5 CFR 531.212(a)(ii)(2) and (3); break-in-service definitions also affect creditable service for benefits and are used to determine conversions to new appointments). We also note that the current definitions in DoD processing guidance are based on OPM's definitions of break-in-service for specific purposes. Our rule does not affect either of these definitions—its purpose is solely to determine the application of pay-setting rules. </P>
                    <P>
                        For clarification, we note that our proposed rule states that a break in service is one full 
                        <E T="03">workday.</E>
                         Generally, this will mean an individual will be off the rolls for three full days (i.e., if the employee resigns on Friday, the break in service must include Saturday, Sunday, and Monday). Because such a break could affect the staffing processes of the 
                        <PRTPAGE P="56376"/>
                        position (to include the requirement for competitive staffing processes), we expect that Components will be careful not to use this definition in a manner that would circumvent pay-setting rules for internal placement actions or merit system principles. 
                    </P>
                    <P>Finally, one commenter suggested that NSPS must offer the same salary (GS grade and step) to individuals who might otherwise go to other branches of Government that hire similar skills if it wants to get the best of the best. One of the primary advantages provided by NSPS is that it allows supervisors and managers great latitude in offering starting salaries across the range of a band based on conditions such as the labor market, special skills, and mission requirements. This market based system allows hiring officials to immediately react to market conditions and offer starting salaries that are not tied to a specific GS grade and step. </P>
                    <HD SOURCE="HD2">Section 9901.353—Setting Pay Upon Reassignment </HD>
                    <P>This section outlines the specific rules to be applied in setting salary under a reassignment action. </P>
                    <P>Labor organization representatives suggested amending this section to include language that ensures labor unions' ability to collectively bargain the issues of setting pay upon reassignment. As previously stated, DoD is committed to fulfilling its obligations to bargain in good faith on negotiable conditions of employment related to these regulations, consistent with 5 U.S.C. chapter 71 and the requirements in 5 U.S.C. 9902 and section 1106(b) of Public Law 110-181. </P>
                    <P>Several commenters requested that the number of management-directed reassignments be limited. Other commenters expressed concern that salary increases were limited to 5 percent for reassignments. Some commenters felt that this cap was unfair, especially considering that individuals just entering Government service can negotiate up to a 20 percent increase in pay. Another commenter, while expressing confidence that the proposed regulation provides the necessary foundation for a contemporary and flexible personnel system, echoed concern about the 5 percent cap on reassignments. According to the commenter, this policy hinders the organization's ability to promote from within and retain top performers. To address this problem, the commenter recommends splitting pay band 2 to improve recruitment and retention and increase employee morale, as well as alleviate problems that the large pay band creates for the Priority Placement Program and for establishing representative rates for reductions in force. Alternatively, the commenter proposes eliminating the 5 percent cap to allow management the needed flexibility to compensate current Federal employees for their performance and competencies. Another commenter suggested that a reassignment to a supervisory position should require that the maximum reassignment rate be given or, that the regulations be changed so that movement to the YC pay band is considered a promotion even if the employee is coming from a comparable band. </P>
                    <P>This regulation does not define pay bands including pay band 2. The classification architecture, to include pay schedules and pay bands, will be described in implementing issuances. Therefore, no change has been made to the proposed regulation with regard to recommendations to split pay band 2. In response to comments concerning adjusting the 5 percent cap on reassignments, we believe that the cap on a reassignment action is reasonable given the pay flexibilities that are available for movements within or across comparable pay bands. It is also a greater flexibility than provided on a reassignment in the GS pay system. In addition to performance payouts, employees may progress through a pay band through reassignments. A reassignment occurs when an employee moves voluntarily or involuntarily to a different position or set of duties within a pay band or to a position in a comparable pay band. </P>
                    <P>There are no limits to the number of times an NSPS employee may reassign on voluntary moves. However, an employee may only receive a total of a 5 percent cumulative increase to base salary in any 12-month period unless an authorized management official approves an exception. On a management-directed reassignment, an employee may receive a base salary increase of up to 5 percent each time that management reassigns the employee. An increase associated with a management-directed reassignment does not count toward the 12-month limit associated with voluntary reassignments. </P>
                    <P>Another flexibility that provides for faster pay progression is the Accelerated Compensation for Developmental Positions (ACDP) provision, which applies to employees in developmental or trainee level positions in Pay Band 1 of the professional and analytical pay schedules. ACDP allows management to increase the base salary of eligible employees at rates that are less than, match, or exceed career ladder promotion rates under the GS pay system. The accelerated compensation available under ACDP recognizes the acquisition of job-related competencies that are documented in a formal training plan. The amount of the ACDP increase generally will not exceed 20 percent of an employee's base salary unless management approves a higher amount. </P>
                    <P>NSPS also recognizes that GS employees in career ladder positions below their target level at the time of conversion generally will have served some time towards the next higher grade now encompassed within the NSPS pay band to which converted. Therefore, during the first 12 months following conversion, employees who are not eligible for ACDP are eligible to receive a one-time band increase equivalent to the GS promotion increase they would have received had they not been converted into NSPS. </P>
                    <P>NSPS gives individual pay pools the flexibility to determine how employee performance ratings translate into base salary increases, bonuses, or both. Where determined appropriate, management has the authority to place a category of positions in a separate pay pool to provide employees a performance payout with a higher value on share assignments. In this manner, it is possible to offset and reduce part of the pay progression requirement for interns under ACDP via performance pay progression. It is also possible for the pay of interns to progress at different rates based on performance. </P>
                    <P>All of these pay-for-performance flexibilities provide employees with an opportunity to receive an increase to base salary based on their job performance as well as providing management the ability to progress pay consistent with labor markets. </P>
                    <P>
                        In addition, representatives from labor organizations were concerned that supervisors have the ability under this section to reassign an employee to a higher level of duties and authorize a 5 percent pay increase with no competition for the new position. It is true that NSPS is designed to permit noncompetitive movement for reassignments including those that involve increases to base salary. The use of broad pay bands and noncompetitive movement within the bands enhances the flexibility and agility of the organization to respond to staffing requirements. At the same time, the cap on the amount of a reassignment increase preserves the intent of the merit principles by ensuring that moves involving increases similar to those associated with promotions (6 percent or more increase to base salary) remain subject to merit promotion rules. 
                        <PRTPAGE P="56377"/>
                    </P>
                    <P>Another commenter noted that § 9901.353(a)(2) appears to prevent an increase in base salary of an employee reassigned due to a reduction in force and suggests that this is not right if the position to which the employee was reassigned carries more responsibility. We have revised the proposed regulation to clearly state that an employee reassigned through reduction in force procedures is not eligible for an increase in base salary under these provisions, but may be eligible for a within-grade increase adjustment under § 9901.351(c)(1). </P>
                    <P>One commenter suggested that consideration should be given to describing reassignment increases under this section as “temporary pay adjustments” so that they may be used for details as well as temporary reassignments. We have not changed the proposed regulation in response to this comment because on a detail the pay should remain unchanged. On a detail, an employee is still assigned to their permanent position. If an increase is warranted in this type of movement, then management should make it a temporary reassignment as opposed to a detail. However, we did review the issue of a temporary reassignment and have made some clarifications to it. We had previously stated that if a temporary reassignment was later made permanent that the employee could not receive any additional increase. We have changed the proposed regulations so that this restriction will no longer apply. </P>
                    <P>One commenter objected to the wording of § 9901.353(a)(3)(vi), which states that one of the factors on which a reassignment increase may be based is an employee's “past and anticipated performance and contribution.” The commenter suggested that it is improper to base pay on anticipated performance and contributions. We disagree. Performance projections based on knowledge, skills, education, duties to be performed and/or past performance is an entirely appropriate consideration in setting salaries as well as a widely employed business practice. Reassignment increase determinations are best arrived at when considering all of the factors described in this section, including any business rules the organization has established concerning the application of these factors. </P>
                    <P>Finally, we have made minor editorial changes in § 9901.353(f) for enhanced clarity and for consistency with the language in related provisions in §§ 9901.343 and 9901.355(b)(4). </P>
                    <HD SOURCE="HD2">Section 9901.354—Setting Pay Upon Promotion </HD>
                    <P>This section outlines the specific rules to be applied in setting salary under a promotion action. </P>
                    <P>Several commenters suggested that the range of 6-12 percent for pay increases for promotions is insufficient to recruit new talent for occupational specialties such as engineering. No change has been made based on this comment. When justified, promotion increases above 12 percent can be granted with higher-level approval. Therefore, the rule retains sufficient flexibility to respond to market forces. </P>
                    <P>One commenter recommended adding an additional factor to be considered when determining the amount of a promotion increase: The long-term costs of the promotion increase and the resulting multi-year budget implications. We have not added this factor, as it can be considered under a current factor such as the business requirements of their respective organizations. </P>
                    <P>Other commenters recommended that, when an employee is promoted from a non-NSPS position, an authorized management official should set the employee's new adjusted salary at no less than the employee's adjusted salary (including any applicable locality pay, special rate supplement, or equivalent supplement) plus any physicians' comparability allowance payable for the position held prior to the reassignment, provided the resulting base salary does not exceed the maximum rate of the new pay band. In response to these comments, we have revised the proposed regulation to require consideration of such factors prior to processing a promotion action. Additionally, we have incorporated language requiring use of a geographic conversion formula for such moves. </P>
                    <P>One commenter recommended that employees promoted from targeted local market supplements to lower targeted local market supplements should also have their pay set based on comparison of “adjusted salary rates.” If adjusted salary rates are used, according to the commenter, geographic conversion rates should also be applied similar to application under §§ 9901.353 and 9901.355. Another commenter recommended modification of § 9901.354 to require that pay for employees promoted from non-NSPS to NSPS positions be set using adjusted salary rather than base salary to prevent increased compensation costs when FWS employees are promoted to NSPS positions. In response to these comments, we have revised the proposed regulation to require consideration of adjusted salary prior to processing a promotion action, use of geographic calculation formula, and the apportionment of the adjusted salary between base salary and local market supplement or targeted local market supplement after the pay setting has been completed, when applicable. </P>
                    <P>Commenting on criteria that may be considered in determining the amount of a promotion increase, as outlined in § 9901.354(b), one commenter suggested that pay should not be based on anticipated performance, other employees' pay, or location (which is already accounted for in the local market supplement). These factors are used only to determine the amount above 6 percent (if warranted), and should be used in combination with all the factors to determine any amount of a promotion increase above 6 percent. </P>
                    <P>Regarding employees on pay retention who are re-promoted to the pay band from which they had been reduced [§ 9901.354(d)(1)], one commenter suggested that employees who have a minimum satisfactory performance rating should automatically be reinstated to the pay they otherwise would have attained, including any performance payouts and/or band adjustments. This should not be needed, as the employee is already being compensated at the higher level of work while on pay retention, without having to perform at that higher level of work. </P>
                    <HD SOURCE="HD2">Section 9901.355—Setting Pay Upon Reduction in Band </HD>
                    <P>This section outlines the specific rules to be applied in setting salary under a reduction in band action. </P>
                    <P>Labor organization representatives objected to reductions in pay based on conduct without more information about the criteria, rules, and procedures to be used by management in making these decisions. These rules are stated under the procedures in 5 U.S.C. chapter 75. Consequently, they are not stated in this regulation. </P>
                    <P>
                        One commenter pointed out a perceived inconsistency in language between § 9901.355(b)(4) and § 9901.353(f). When referring to setting pay upon a reduction in band in § 9901.355(b)(4), the paragraph states that, when an employee is reduced in band involuntarily as a result of adverse action, he or she may have his or her base salary reduced, and if reduced, the reduction must be between 5 percent and 10 percent. However, when referring to setting pay upon reassignment in § 9901.353(f), the language states that an employee involuntarily reduced in pay via 
                        <PRTPAGE P="56378"/>
                        reassignment as a result of adverse action must have his or her base salary reduced by at least 5 percent, and may have it reduced by up to 10 percent. The commenter wonders whether the difference is intentional. Yes, the difference is intentional. In the first instance (§ 9901.355(b)(4)), a decision to reduce an employee's salary has not been made. Rather, only the decision to reduce the employee's pay band has been decided. Since a decrease in salary is discretionary upon reduction in pay band, the permissive may is used to indicate the amount of pay by which salary may be reduced. In the second instance (§ 9901.353(f)), the language indicates a decision has been made to reduce the salary of the employee (“When an employee is involuntarily reduced in pay * * *”). Under NSPS, when a decision has been made to reduce the salary of an employee, it must be in an amount no less that 5 percent and no more than 10 percent of base salary. Therefore, the proposed language in § 9901.355(b)(4) has been retained except for some minor editorial revisions. 
                    </P>
                    <P>Finally, regarding factors upon which an increase in pay due to reduction in band may be based, one commenter expressed a preference for the term “performance-based considerations” in § 9901.355(c)(3) to references to “past and anticipated performance and contribution” in earlier sections. Additionally, the commenter wondered why location and the base salary of other employees factored into the determination of pay upon reduction in band. In response to this comment, since an employee can get an increase similar to a reassignment increase, the factors should be the same. These are only some of the factors to be considered in determining whether an increase is warranted on a reduction in band, and if warranted, the amount of that increase. A manager should look at all of the factors in combination, as well as any business rules, when determining if and when an increase is warranted on a reduction in band. </P>
                    <HD SOURCE="HD2">Section 9901.356—Pay Retention </HD>
                    <P>This section describes the rules to be applied in determining an employee's entitlement to pay retention and the factors in terminating pay retention. </P>
                    <P>One commenter, noting that local market supplements are paid on top of a retained rate, while GS locality pay is included in retained rates, suggests the NSPS proposed rules should be consistent with GS system rules. While there are many similarities between NSPS and other title 5 pay policies, they are neither required to be, nor intended to be, identical. The NSPS system of retaining base salaries supports the overall goals of the pay system while ensuring retained pay provisions like title 5. It should be noted that title 5 does not provide more protection by retaining a locality rate than NSPS, because both systems have geographic conversion procedures established to control movements between locality areas and local market supplement areas when employees are on retained pay. </P>
                    <P>Representatives of one large labor organization expressed support for the provision included in § 9901.356(m), which “grandfathers” in workers to keep people on indefinite pay retention who were already on pay retention when they converted to NSPS. </P>
                    <P>Several commenters recommended extending pay retention beyond the 104 weeks cited in the proposed regulation for various reasons. Commenters also suggested that § 9901.356(f) and (g) be amended to reflect that workers should remain on pay retention until the pay band rate range grows to encompass the retained rate. With respect to both of these comments, we believe the 104-week limitation is a fair balance between protecting an employee with pay retention to provide time to find comparably valued and compensated work while not encumbering the agency with an indefinite additional cost that compensates for work that is no longer being performed. Whereas the pay rate that may be retained under the General Schedule is capped at 150 percent of the top salary of the lower grade, NSPS does not limit pay retention salaries in this manner. Additionally, the broader NSPS pay bands accommodate more salaries, thereby reducing the number of employees required to be covered by pay retention. In recognition, however, that there may be some unique situations where a longer pay retention period is warranted, we have provided that the Secretary may issue implementing issuances describing exceptions to the 104-week pay retention limit. </P>
                    <P>One commenter, responding to language in § 9901.356(d) regarding situations triggering eligibility for pay retention, questions why an organizational realignment or reduction is cited, since reduction in force is now handled through Governmentwide rules. Governmentwide reduction in force regulations do not address pay retention. Rather, those regulations describe retention, displacement, and separation procedures. </P>
                    <P>Another commenter recommended that we clarify the language in 9901.356(f) by adding “under this authority” in recognition of the fact that pay retention could continue under some other non-NSPS authority. We agree and have made the change to the proposed regulation. </P>
                    <P>Other commenters suggested that § 9901.356(j) be amended to ensure that employees on retained pay receive 100 percent of the GS general pay increase (GPI) during the two years they are entitled to pay retention as opposed to 60 percent of the GPI. No change has been made in response to this recommendation. Continuing to grow the salary of an employee on pay retention is not congruent with achieving a salary that fits within the assigned pay band. </P>
                    <P>Finally, one commenter suggested deleting paragraph (3) from § 9901.356(i), related to movement from a non-DoD position to an NSPS-covered position. According to the commenter, this provision impacts the organization's ability to hire quality employees from other Federal agencies and conflicts with Component discretion in § 9901.356(d)(4)(iv) to grant pay retention in situations considered appropriate. On a similar note, another commenter suggested considering allowing for extension of the pay retention time limit beyond 104 weeks for employees who are reduced in band when accepting an overseas position. The tour of duty for an overseas position is generally 2-5 years. The commenter asserted that employees are less inclined to accept overseas positions if pay retention will be terminated after 2 years. We agree that providing pay retention to someone who voluntarily applied for a position in NSPS that is lower-paying, with less responsibility, should be compensated appropriately and not retain a higher salary. Allowing pay retention in these situations would be inconsistent with the underlying concept of a pay-for-performance system. </P>
                    <HD SOURCE="HD3">Premium Pay </HD>
                    <HD SOURCE="HD2">Section 9901.361—General Provisions </HD>
                    <P>
                        This section explains general areas relating to premium pay that have been waived or modified from 5 U.S.C. chapter 55, subchapter V, as well as those areas not waived or modified from the U.S. Code. A representative from the Federal Physicians Association recommends that we delete § 9901.361(e), which prohibits the payment of premium pay to physicians and dentists and include them in the definition of health care professional so that they would be eligible to receive certain premium pay. We have not adopted this suggestion. 
                        <PRTPAGE P="56379"/>
                    </P>
                    <P>Generally, NSPS employees may not be paid, in the aggregate, more than the annual rate of pay for Executive Level I in a given calendar year. However, NSPS physicians and dentists enjoy a higher aggregate compensation cap that is equal to the salary of the President of the United States. Moreover, NSPS has designed broader pay bands for physicians and dentists with significantly higher salary ranges than that provided under the General Schedule ($87,742 to $225,000 plus targeted local market supplements for medical specialties ranging from 4.45 percent to 45 percent of base salary). This enables DoD to competitively set pay for new hires and to reward valued performers through performance payouts. The higher salary structure for physicians and dentists is in recognition that premium pay will not be available and that physicians and dentists work significant overtime hours. This practice reflects compensation practices in competitive labor markets where salary structures are set at a higher level. </P>
                    <HD SOURCE="HD2">Section 9901.362—Modification of Standard Provisions </HD>
                    <P>This section describes provisions related to premium pay, overtime pay, night pay, Sunday pay, holiday pay, law enforcement availability pay, hazardous duty pay, compensatory time off for travel, compensatory time off for religious observance, and the air traffic controller differential. A commenter suggested that FLSA-exempt employees be credited for overtime work in increments of 6 minutes or 15 minutes, depending on the agency's payroll system. We have not adopted this suggestion. Unlike the GS pay system which has separate rules to credit regularly scheduled overtime work and irregular or occasional overtime work, NSPS does not make this distinction. Rather, to establish a contemporary and flexible system of human resources management for DoD employees, NSPS has simplified the scheduling, crediting, and payment of overtime work. Under NSPS, an FLSA-exempt employee is compensated for overtime work using a quarter of an hour as the smallest fraction of an hour, with minutes rounded to the nearest full fraction of an hour. </P>
                    <P>A commenter recommended that all employees working a flexible work schedule (including FLSA-exempt employee) should have a choice to earn compensatory time off or overtime pay. We do not agree. While non-exempt NSPS employees may request compensatory time off, FLSA-exempt employees may be required to accept compensatory time off for any overtime work, regardless of pay level. We believe this provision provides management the flexibility and the ability to manage its workforce to meet critical mission requirements. </P>
                    <P>Regarding language in § 9901.362(c) related to night pay and when it is and is not payable, one commenter pointed out that annual and sick leave must be paid at the appropriate shift differential. A GS employee receives night pay for a period of paid leave only when the leave totals less than 8 hours in a pay period. Therefore, if a GS employee takes 8 hours or more of leave in the pay period, the employee does not receive a night pay differential for those hours of paid leave. We have not adopted a similar rule. Under NSPS, employees having a tour of duty that includes night hours are not entitled to a night pay differential when on annual or sick leave. Except for a period of court leave, military leave, time off awarded under 5 U.S.C. 4502(e), compensatory time off during religious observances, or when excused from duty on a holiday, night pay is not payable during paid absences. However, NSPS employees receive night pay for each hour of work performed at night that is scheduled or ordered or approved by management between the hours of 6 p.m. and 6 a.m. Unlike the GS pay system, NSPS employees receive night pay whether the night work is scheduled before or after the administrative workweek begins. We believe that this provision is fair, equitable, and understandable to employees and that the changes we have made in night pay eases the administration of this premium pay. </P>
                    <P>One commenter asked that the administratively uncontrollable overtime (AUO) pay provision in 5 U.S.C. 5545(c)(2) be applied to NSPS employees. Pay for AUO work is a substitute form of pay for irregular, unscheduled overtime work that is paid on an annual basis instead of an hourly basis. The basis for determining positions for which AUO is payable is that a position must be one in which the hours of duty cannot be controlled administratively, which is inherent in the nature of the work assigned to the position and that the employee is generally responsible for recognizing, without supervision, circumstances that require the employee to remain on duty. Typically, a criminal investigator received AUO pay until availability pay replaced AUO in 1994. Given the specific position requirements for AUO pay, NSPS waived the administratively uncontrollable overtime pay provision in 5 U.S.C. 5545(c)(2). We believe our rationale continues to be valid and that NSPS employees who perform substantial amounts of overtime work are properly compensated through the NSPS overtime pay provisions. </P>
                    <P>One commenter pointed out inconsistency in claims for compensatory time off for travel (currently claims must be filed within 10 days of travel for NSPS, but within 5 days of travel for non-NSPS employees). We have not changed the proposed regulation in response to this comment because the proposed NSPS rule more favorably responds to the national security mission performed within DoD and the likelihood that employees may need additional time to file such requests due to the exigency of the mission. The goal of NSPS is not to be fully consistent with the GS system but to improve upon it where possible. Allowing employees more time to file claims for compensatory time off for travel is just one such instance. </P>
                    <P>One commenter believes that using the term “related regulations” in § 9901.362(i) is confusing for third party adjudicators. We disagree inasmuch as § 9901.362(i)(1) explains that NSPS employees are covered by 5 U.S.C. 5545(d) and the related regulations in 5 CFR part 550, subpart I, subject to the requirements and modifications delineated in § 9901.362(i)(2) through (i)(6). Thus, both the law and related regulations must be read together to determine an employee's entitlement to hazardous duty pay. </P>
                    <P>Another commenter recommended that engineering technicians be eligible for hazardous duty pay. We have not made a change based on this comment because the hazardous work involved in a position such as an engineering technician is considered in the classification process as part of determining the appropriate grade or band level. </P>
                    <P>A commenter asked for clarification of § 9901.362(j)(3) because we did not fully address the crediting of time spent commuting between home and a transportation terminal. We agree and have added a new paragraph (j)(4) to clarify that if an employee is required to travel directly between his or her home and a transportation terminal, the travel time is creditable as time in a travel status. Such travel time outside regular working hours is creditable as time in a travel status. However, normal commuting time must be deducted if the travel occurs on a day the employee is regularly scheduled to work. </P>
                    <P>
                        Several commenters noted that the prohibition on the payment for unused compensatory time off for religious observances appears discriminatory because it applies only to those whose personal religious beliefs require the 
                        <PRTPAGE P="56380"/>
                        abstention. We disagree. Section 5550a of title 5, United States Code, affords all Federal employees the opportunity to earn and use compensatory time off for religious observances without losing pay or using annual leave. However, an employee should be allowed to accumulate only the number of hours of work needed to make up for past or future absences for religious observances. If self-regulated properly, an employee should only have the appropriate number of hours needed to fulfill religious obligations and not require payment in lieu of use. 
                    </P>
                    <P>A representative of a labor organization contended that compensatory time is actually reimbursement for services provided and, as such, should not be defined as “premium pay.” We have not changed the proposed regulation based on this comment. Compensatory time earned under 5 U.S.C. 5543 is considered to be premium pay and is paid out at the overtime rate that was earned, when applicable. In contrast, compensatory time off for religious observances and compensatory time off for travel are listed separately because they represent an accommodation or flexibility provided to an employee to respond to a personal need. Consequently, they are not paid out under NSPS. They are additional time and attendance flexibilities available to an employee and are not considered to be covered under the overtime provisions. </P>
                    <P>Commenters suggested that provisions related to Sunday pay, overtime pay, and compensatory time off for travel should mirror provisions of the GS system. We have chosen not to change this section of the regulation because it is not our intent to achieve full consistency with the GS system; rather, our goal is to preserve flexibility within NSPS to establish provisions that best meet the Department's national security mission. </P>
                    <HD SOURCE="HD2">Section 9901.363—Premium Pay for Healthcare Personnel </HD>
                    <P>This section addresses treatment of premium pay for healthcare personnel to include on-call premium pay, night pay, and pay for weekend duty. Commenters questioned why, if on-call premium pay is going to be authorized for NSPS employees in covered occupations, all employees (including those in graded positions) are not covered. These commenters viewed the difference as disparate treatment between NSPS and graded systems. NSPS enabling legislation provides authority to waive certain title 5 laws and regulations for employees covered by the NSPS system. This enables DoD to, among other things, tailor a personnel system to its unique national security mission. The law does not provide authority to waive laws or regulations for employees or positions covered by other pay systems. Therefore, no authority exists to modify the General Schedule under this regulation. </P>
                    <P>Other commenters recommended that on-call premium pay be extended to other occupations that have similar on-call requirements. The Department has this flexibility and, if needed to address its critical mission requirements, it may amend the NSPS regulations at a later time. </P>
                    <HD SOURCE="HD2">Section 9901.364—Foreign Language Proficiency Pay </HD>
                    <P>This section outlines the provisions for a foreign language proficiency pay (FLPP) for those certified in languages identified as necessary for national security interests. One union official requested amplification of the last factor listed under “Other considerations authorized by the Secretary.” We have not amplified this provision, as this leaves the Department some flexibility to address future mission requirements or needs. Increased foreign language skills within the Department are necessary for building internal relationships for coalition/multi-national operations, peacekeeping and civil/military affairs. Having a cadre of skilled language speakers will allow the Department to respond quickly to crisis requirements. For example, in the aftermath of a disaster in a foreign area where the Department is distributing food and medical supplies, it is imperative to have someone readily available who can speak the language or dialect in order to explain to the affected population the food distribution process. In this case, an employee who is being paid FLPP for the required language could provide that explanation. The last factor of the payment criteria gives an authorized management official discretion in considering the unique attributes of a specific job or assignment in determining the level of payment for a covered employee. </P>
                    <HD SOURCE="HD3">Conversion Provisions </HD>
                    <HD SOURCE="HD2">Section 9901.371—Conversion Into NSPS Pay System </HD>
                    <P>This section prescribes policies and procedures for converting DoD employees into NSPS. One commenter noted that information under § 9901.371(j)(7) stating that the WGI adjustment is a one-time adjustment which may not be provided on any subsequent conversions into NSPS is inconsistent with current NSPS policy, which actually permits an adjustment each time an employee converts into NSPS, provided he or she meets the conditions for such payment. We agree and have revised this paragraph accordingly. </P>
                    <P>Another commenter responded to language in § 9901.371(l)(2), which describes how “an employee who is selected for a non-NSPS position that subsequently becomes covered by NSPS before the effective date of the employee's placement in the position is eligible to receive (at the discretion of an authorized management official) a one-time base salary increase equivalent to the increase the employee would have received had the placement been effected prior to the position becoming covered by NSPS.” In the commenter's view, this employee should receive a mandatory increase rather than be subject to the discretion of the authorized management official. Unlike the GS system, NSPS requires supervisors and managers to take responsibility for, and be held accountable for, determining the appropriate pay for their employees. Those determinations are made based on many variables. For example, an employee's pay may reflect factors such as critical mission or business requirements, the employee's past and anticipated performance and contributions, specialized skills or knowledge possessed by the employee, labor market conditions, base salary rates paid to other employees in similar positions, and the location of the position. Further, NSPS emphasizes increases in pay based on performance, not so much the up-front pay-setting when an employee is placed in a position. We do not agree that mandating pay under this provision is the right thing to do because we want supervisors and managers to have the flexibility and the tools they need to make decisions necessary to perform their work and meet the strategic missions and objectives of the Department. Therefore, we have not revised this paragraph. We note that two labor organizations agreed with the provisions that employees will not experience a pay reduction upon conversion to NSPS. </P>
                    <P>
                        Other commenters expressed concerns regarding § 9901.371(m). According to these commenters, the physicians' comparability allowance (PCA) is not paid consistently across all DoD installations, which means that those physicians and dentists who are not receiving this payment at the time of conversion will have a lower base 
                        <PRTPAGE P="56381"/>
                        salary than those who do receive this payment. They assert that this makes the Department less competitive with other agencies such as the Department of Veterans Affairs, results in continuing pay inequities, and doesn't comport with the stated objective of NSPS to set and adjust salaries based on factors such as labor market conditions. The proposed regulation provides flexibility for the Component to decide at the point of conversion whether to incorporate this payment in whole or in part into the employee's NSPS base salary if the employee was regularly receiving the allowance prior to conversion. In making this determination, the Component may take several things into consideration, e.g., access to a greater rate of pay than under the GS system, any applicable targeted local market supplement, retention of the employee, etc. We do not agree that mandating the inclusion of this allowance in the employee's NSPS base salary is desirable or prudent and have not changed this provision. 
                    </P>
                    <P>One commenter suggested that when an employee is transferred or reassigned from a non-covered position to a position already covered by the NSPS system, that employee should be provided with a copy of the new classification, position or series description, occupational group or subgroup, pay schedule, and any other relevant documentation before entering service in the position. DoD Human Resources Offices already have procedures in place to provide transferred and reassigned employees with a copy of the Notice of Personnel Action (SF-50) which includes the career group, band, series, official title, FLSA status, and salary. A copy of the position description is also available and all pay schedules are published and available on line. For these reasons we believe that including this type of information in this regulation would be redundant and unnecessary. </P>
                    <HD SOURCE="HD2">Section 9901.372—Conversion or Movement Out of NSPS Pay System </HD>
                    <P>This section addresses pay setting when employees convert to or move out of the NSPS pay system and are placed in another Federal pay system. </P>
                    <P>Commenters objected to the provisions of the conversion-out process allowing employees who were at or near the top step in GS grade, and converted to NSPS, to be converted out from NSPS at a higher grade than the grade that they previously held, even if there have been no changes in duties and responsibilities. The procedures described in this section are similar to conversion-out procedures provided in many of our demonstration projects. We would expect that employees who are converted out of NSPS within a few years after conversion into NSPS will typically be converted out to a virtual grade consistent with their grade at the time of conversion. However, we do acknowledge that because NSPS offers the opportunity for greater salary advancement for many employees, it is possible that their adjusted salary at the time of conversion out could result in a higher virtual GS grade. This will be particularly true for employees who have been covered for a long period under NSPS. We have not revised these procedures in response to these comments. </P>
                    <P>Another commenter suggested that the entire section should be deleted, since the receiving agency, not DoD, should establish the GS equivalent rate for their employees. We do not agree. This section was added in direct response to requests from DoD Components and many DoD employees. Initially, we designed NSPS with the goal of covering the vast majority of DoD employees in a relatively short period of time. That has not materialized at this time and, instead, there is considerable movement within the Department back and forth between NSPS and non-NSPS positions. A major impact of this situation has been that NSPS employees are often disadvantaged when they are promoted to a GS position because the rules of that system apply to the action. Because we presently have no conversion out procedure, these employees must have their pay set in accordance with the GS highest previous rate rule rather than the two-step promotion rule that applies to GS employees who move from one GS grade to a higher GS grade. This results in the NSPS employee receiving a smaller promotion increase. </P>
                    <P>Other commenters requested that this section include provisions allowing civilian employees the option to transfer back into the GS system. We have not revised this section in response to these comments. DoD civilians complement and support the military around the world and to meet the interests of the United States in today's national security environment, DoD needs an integrated, flexible, and responsive team. To meet today's challenges, DoD needs a workforce whose performance and contributions are linked to strategic mission objectives and who can be more fully recognized and rewarded. DoD needs a classification and pay system that allows us to attract and retain employees. At the same time, DoD needs a system that protects the fundamental rights of its employees. The GS system cannot adequately address the 21st century national security environment and, although it is based on important core principles, those principles are operated in an inflexible, one-size-fits-all system. This inherent weakness makes supporting the DoD's mission complex, costly, and ultimately risky. With NSPS, we've designed a modern, contemporary, and flexible system that will generate more opportunities for DoD civilians by easing the administrative burden routinely required by the GS system. While DoD employees may move back and forth between the NSPS and GS systems, as well as other personnel systems within the Department, the objective is to cover as many positions and employees under NSPS as possible and to fully allow and encourage DoD employees to take advantage of the opportunities available under the new system. </P>
                    <P>
                        One commenter observed that § 9901.372(a) should be revised to say that when a GS virtual grade and rate are established, they “will be” (rather than “may be”) used to apply GS pay-setting rules. We agree and have revised this paragraph accordingly. Another commenter suggested that § 9901.372(d)(1) should be revised to state that intervening (unused) grades for two-grade interval occupations should be considered when determining the GS virtual grade of an employee who is converting or moving from an NSPS position to a GS position. For example, in the case of the YA-2 pay band that covers grades GS-9 through GS-13, the commenter believed that GS-10 should be considered in setting the GS virtual grade even if that grade was not actually available to the position in the GS pay system because the position was in a GS two-grade interval occupation that used only grades GS-9, GS-11, GS-12, and GS-13. As a result of this comment, we carefully reviewed this matter and determined that intervening grades in two-grade interval occupations should not be considered in setting a GS virtual grade. We identified certain anomalies that would result if the intervening grade were considered. For example, if a GS occupation had special rates at the GS-9 and 11 levels, setting the GS virtual grade at GS-10 would require the GS virtual rate be set within the GS-10 rate range, but there would be no established special rate for that grade. This would produce inappropriate results in applying the maximum payable rate rule or the promotion rule. Furthermore, we determined that the established policy of various pay-
                        <PRTPAGE P="56382"/>
                        banding demonstration projects (including several DoD demonstration projects) was to exclude unused intervening grades in determining GS converted grades when employees leave the system. Accordingly, we have revised § 9901.372(d)(1)(i) to expressly provide that an intervening grade for two-grade interval occupations may not be considered in setting the GS virtual grade. 
                    </P>
                    <P>Another commenter expressed concern that the requirement in § 9901.372(d)(2) that, when an employee's adjusted salary falls between two GS steps, his or her virtual rate must be set at the next higher step, may prove unnecessarily costly, because if the employee's actual rate (based on the virtual rate) later also falls between steps, pay will have to again be set at the next higher step if he or she is promoted to a GS position and the 2-step rule is applied. The commenter suggests that DoD set the virtual rate at the employee's existing actual adjusted salary under NSPS so that the 2-step rule can be applied directly to that rate. This is consistent with OPM's own rule at 5 CFR 531.243(c) relating to the promotion of a GM employee to a GS position. We have revised this paragraph accordingly. </P>
                    <P>A commenter asked that we change § 9901.372(d)(2)(iii) or add another paragraph to reflect grade retention upon movement out of NSPS to be consistent with the GS system. They stated that if the movement out results from a RIF or a realignment, the NSPS employee deserves the same pay protection as his or her GS counterparts. We understand this concern; however, upon movement or conversion out of NSPS it is the pay administration rules of the gaining system which determine how pay is set and whether or not an employee is entitled to or eligible to receive grade and/or pay retention. Because NSPS employees are not in a “covered pay system,” they are not eligible for grade retention when they move from NSPS to the GS system in accordance with 5 CFR 536.102(d). When an NSPS employee is placed in a GS position as a result of a RIF, he or she may be entitled to indefinite pay retention. </P>
                    <P>
                        Finally, we have made a few minor edits to § 9901.372 either to conform to publishing requirements for the 
                        <E T="04">Federal Register</E>
                         or to add clarity to the proposed rule. 
                    </P>
                    <HD SOURCE="HD3">4. Subpart D—Performance Management </HD>
                    <HD SOURCE="HD3">General Comments </HD>
                    <P>Subpart D regulates performance management for NSPS employees. </P>
                    <P>This subpart inspired a large number of comments during the public comment period. Since many of the comments related to both subparts C and D, we addressed them under the heading “Major Issues.” However, one general comment remains. Many commenters expressed concern that the linking of pay to performance would dampen discourse between supervisor and employee. These commenters were inclined to believe that employees seeking favor with their leadership, as well as larger increases, would censor or inappropriately alter any dissenting opinions they held concerning work processes or products, which would result in less than desirable outcomes. Such behavior, however, may exist whether or not performance and pay are directly linked. No changes have been made based on these comments. </P>
                    <HD SOURCE="HD3">Comments on Specific Sections of Subpart D </HD>
                    <HD SOURCE="HD2">Section 9901.403—Waivers </HD>
                    <P>Section 9901.403 specifies the waiver of 5 U.S.C. chapter 43 with regard to that employee or category of employees covered by this subpart. </P>
                    <P>One commenter expressed concern that waiver of chapter 43 will lead to greater uncertainty among DoD employees about what their supervisor and management in general expect, which will result in workplace disruptions, confusion, lowered employee morale, organizational inefficiencies, and performance deficiencies. We have concluded that the waiver of 5 U.S.C. chapter 43 is appropriate and necessary to implement NSPS performance management. No change has been made to the proposed regulation based on this comment. </P>
                    <HD SOURCE="HD2">Section 9901.404—Definitions </HD>
                    <P>This section contains definitions for the performance management process under NSPS. </P>
                    <P>
                        Commenters suggested a change to the definition of 
                        <E T="03">unacceptable performance.</E>
                         Commenters objected to requiring an unacceptable rating for failure to meet a single performance expectation. Similar to other performance management systems in the Federal Government, NSPS applies a generally accepted practice of identifying unacceptable performance as failure to meet one or more performance expectations. In recognition of the consequences of unacceptable performance, the regulation stresses the need for clear communication of performance expectations, monitoring performance, and addressing performance that does not meet expectations (see §§ 9901.406(b), 9901.409, and 9901.410). No change has been made to the proposed regulation based on these comments. 
                    </P>
                    <P>
                        Several commenters also expressed concern that requirements related to the definition in § 9901.103 of 
                        <E T="03">performance</E>
                         as it relates to demeanor, conduct, and behavior are irrelevant to accomplishing performance objectives unless management establishes a direct link between the required demeanor and accomplishment of the assignment. 
                    </P>
                    <P>Performance assessments would not be complete without considering many factors, including employees' behaviors in carrying out assigned work. Employee behaviors can be objectively observed and evaluated against established performance expectations. Supervisors also may consider how underlying misconduct negatively impacts the execution of an employee's duties, that of the team, and/or that of the organization under NSPS. All applications of performance management under NSPS continue to provide employees with protection against prohibited personnel practices, whistleblower protections, and appeal rights. Any disagreement with the assessment of an employee's professionalism, conduct, or respect, to the extent it impacts his or her rating, is subject to the reconsideration process as defined in § 9901.413. No change has been made to the proposed regulation based on this comment. </P>
                    <P>
                        One commenter requested that a definition of “rating official” be added to § 9901.404. We agreed and revised the section to include this definition. In addition, we made a small revision to the definition of 
                        <E T="03">minimum period</E>
                         to specify that only performance under an approved NSPS performance plan qualifies for completion of the minimum period. 
                    </P>
                    <HD SOURCE="HD2">Section 9901.405—Performance Management System Requirements </HD>
                    <P>Section 9901.405 specifies that NSPS regulations establish the performance management system required under 5 U.S.C. 9902 and that this subpart contains mandatory requirements for all employees covered by NSPS. It also provides that the Secretary has the authority to further define the system through implementing issuances. </P>
                    <P>
                        Several members of labor organizations objected to the summary rating levels included under § 9901.405 and suggested that we revise the proposed regulation to include specific language indicating the impact of ratings on job retention. The regulation identifies the summary rating levels that will be used in NSPS. We explained the 
                        <PRTPAGE P="56383"/>
                        rating level descriptors in the implementing issuances currently in use. The descriptors are not the exclusive means of determining a rating but rather serve as a guide when supervisors determine the ratings for each job objective. NSPS, like all performance management systems, assesses employee performance upon which management may base decisions for employee retention. This is consistent with the merit system principles described under 5 U.S.C. 2301. No change was made to the proposed regulation based on these comments. 
                    </P>
                    <P>A commenter expressed concern that NSPS is ignoring the value of experience in the performance management system. Under NSPS, an employee is rated based on his or her demonstrated performance, which generally is directly impacted by his or her experience and which is assessed on what the employee has accomplished and how well he or she has met performance expectations. This assessment is measured in terms of the quality of the employee's experience, as reflected in his or her performance. No change was made to the proposed regulation based on this comment. </P>
                    <P>A few commenters expressed concern at the limited scale available for rating an employee's performance. While one commenter suggested using a 10-point scale instead of the current 5-point scale, most commenters found no issue with the rating scale. During the past 2 years, DoD has tested the NSPS 5-level rating system and found it to adequately enable distinctions in levels of performance. There is no indication that the scale unfairly restricts a supervisor's ability to rate an employee's performance accurately. No change has been made to the proposed regulation based on these comments. </P>
                    <P>Two commenters suggested that, to achieve uniformity in rules used for rounding raw performance scores to derive adjective ratings of record, the rules should be included in the regulation. Another commenter asserted that organizations rounded down performance scores in an attempt to lower employee ratings. Standardized rounding rules specific to NSPS performance ratings were developed to support distinctions in performance and ensure uniformity of rating practices across NSPS. Under NSPS, higher-level performance has been determined to be performance above an even split between two rating levels (i.e., above the rounded score of “x.50”). To ensure uniformity and consistency regarding the application of rounding rules and in response to the above comment, we added § 9901.405(b)(6) to specify these rounding rules. </P>
                    <P>One commenter indicated that the proposed regulation did not permit an accurate evaluation of job performance based on objective job-related criteria. NSPS uses a multi-level system that makes distinctions in levels of employee performance and links employee achievements, contributions, knowledge, and skills to organization results. The system ensures that performance expectations are clearly communicated to employees and that they are linked to the organization's strategic goals and objectives. This provides the ability to evaluate employees based on these objective job-related criteria, recognize valid distinctions in performance, and reward employees based on those distinctions. No change was made to the proposed regulation based on this comment. </P>
                    <P>One commenter indicated that if he had identified fewer job objectives his rating would have been higher and thus he would have received a higher share. Job objectives can be identified based only on the requirements of the position and reflect the responsibilities and expectations associated with the position. Ratings are assigned in accordance with the summary rating levels provided in the regulation and the implementing issuances. However, these rating level descriptors are not the exclusive means for determining a rating, but rather serve as a guide when supervisors determine the ratings for each job objective. The rating and the resultant share assignment are a product of an evaluation of an employee's overall performance based on criteria defined for each rating level that are clearly identified in the regulation and implementing issuances. No change has been made to the proposed regulation based on this comment. </P>
                    <P>Finally, a commenter indicated that some military supervisors with NSPS responsibilities are not of sufficient rank to supervise civilians and do not have the required knowledge to perform their NSPS duties. The commenter suggested that NSPS establish a crosswalk to identify equivalent military and civilian ranks to determine who can supervise Federal employees. It is not within the scope of this regulation to determine which military ranks can supervise which NSPS pay bands. However, the regulation clearly identifies supervisory responsibilities and specifies that supervisors and managers will be held accountable for effectively managing the performance of employees under their supervision. Further, DoD is committed to training managers and supervisors, including military members, on how to establish and communicate performance expectations, how to assess employee performance, and how to appropriately translate that assessment into pay adjustments. No change has been made to the proposed regulation based on this comment. </P>
                    <HD SOURCE="HD2">Section 9901.406—Setting and Communicating Performance Expectations </HD>
                    <P>Section 9901.406 provides the requirements and guidelines for communicating with employees regarding their performance through the use of “performance expectations.” </P>
                    <P>One commenter suggested simplifying the definition of performance expectations while several other commenters indicated a need to safeguard against imposition of impossible performance expectations. We believe the existing definition and the requirements identified in this section clearly describe the parameters for setting performance expectations. In addition, the regulation specifies that employees will be involved in the development of performance expectations, which provides an opportunity for dialog between the supervisor and the employee during the development process. Further, safeguards are in place to preclude the imposition of impossible expectations since performance expectations are subject to higher or second-level review to ensure consistency and fairness within and across the organization. Additionally, NSPS job-objective training for supervisors and managers stresses the use of “SMART” objectives. “SMART” is an acronym for the following criteria: Specific—means observable action, behavior, or achievement is described; Measurable—means the method or procedure must exist to measure the quality of the outcomes; Aligned—means linking (or drawing a line of sight from) objectives to organizational mission and goals; Realistic and Relevant—means the objective is achievable and relevant means important to the organization; and Timed—means there is a point in time when the objective (or assignments covered by the objective) will start or when it will be completed. These measures ensure employees will not be expected to accomplish “impossible expectations.” We have made no change to the proposed regulation based on these comments. </P>
                    <P>
                        One commenter suggested revising § 9901.406(b) to state that a performance expectation must be communicated to an employee in writing before the employee is expected to accomplish a related work assignment. Section 
                        <PRTPAGE P="56384"/>
                        9901.406(b) already states that an employee will receive performance expectations in writing before being held accountable for them. No change has been made to the proposed regulation based on this comment. 
                    </P>
                    <P>Another commenter requested clarification regarding § 9901.406(b)(1), which refers to performance expectations that will be communicated to the employee in writing “including those that may affect an employee's retention in the job.” The commenter indicates that this seems to imply that there are expectations that may not affect an employee's job retention. Like all performance management systems, NSPS assesses an employee's performance based on an evaluation of the performance expectations communicated to the employee in writing and amplified verbally as described in § 9901.406(f). This assessment of an employee's performance is the basis upon which management may make decisions regarding employee retention. We agree with the commenter that this phrase does not clearly portray our intent and it has therefore been removed. </P>
                    <P>Commenters suggested that § 9901.406(c) be deleted from the proposed regulation, as it holds employees accountable for subjective standards of professionalism and conduct but does not hold supervisors accountable for the same professionalism and conduct standards. These comments indicate a lack of understanding that the term “employee” also pertains to supervisors and managers. We believe the misunderstanding occurs because a paragraph addressing criteria pertaining only to supervisors and managers is preceded by a paragraph addressing criteria for all employees, which includes supervisors and managers. To avoid the potential for such a misunderstanding, we added language to § 9901.406(d) to clearly indicate that the requirements specific to supervisors and managers are in addition to those in § 9901.406(c). </P>
                    <P>One commenter suggested adding to § 9901.406(e) a requirement for supervisors and managers to meet with employees they supervise at the beginning of the appraisal period and at scheduled times thereafter. The regulation clearly states in § 9901.405 that supervisors and managers are held accountable for effectively managing the performance of their employees. This responsibility includes setting and communicating performance expectations, monitoring performance and providing feedback. We believe the regulation defines supervisor and manager responsibilities in this area without being overly prescriptive in the manner and number of times they should meet with employees. The regulation preserves a certain amount of discretion in recognition of the breadth of work and variety of work situations (including varied levels of independence and geographic dispersion) prevalent in DoD. No change has been made to the proposed regulation based on this comment. </P>
                    <P>One commenter suggested specifically including occupational peer involvement in the factors to be considered when developing performance expectations. Peer involvement, however, is normally part of a process rather than a factor. Section 9901.406(e) indicates that performance expectations should include organizational, occupational, or other work requirements as well as competencies that an employee is expected to demonstrate or contributions that he/she is expected to make. We believe this description allows the flexibility to include necessary occupational requirements when developing performance expectations. No change was made to the proposed regulation based on this comment. </P>
                    <P>Several commenters noted that the option for supervisors to amplify performance expectations via oral instructions under § 9901.406(f) is especially problematic as this could likely lead to a number of misunderstandings and disputes between supervisors and employees over how the expectation is expressed or understood, or whether it is even expressed as a performance expectation on which an employee may be appraised. Others noted that this section may conflict with the requirement for clear communication in § 9901.405(c)(1). We believe that the regulations sufficiently address concerns about communication of performance expectations. The language in § 9901.406(b) clearly requires the communication of performance expectations to employees in writing prior to holding them accountable for these expectations. It is neither feasible nor functional to require the written communication of every assignment and instruction used to amplify performance expectations. Non-written communication can still be considered clear and can be accomplished through dialog regarding performance expectations. The attributes identified in § 9901.406(f) relate to the day-to-day communication between supervisors and employees regarding work assignments, including specific goals or metrics that are a project-specific extension of already established performance expectations. No change has been made to the proposed regulation based on these comments. </P>
                    <P>Commenters expressed concern over the establishment of performance expectations by supervisors. Many commenters stated that performance expectations should be subject to an appeals process by the employee, and not simply set by the supervisor according to the process in § 9901.406. Insofar as practical, employees are to be involved and their participation sought in the development of performance expectations as stated in § 9901.406(g). However, similar to performance management systems under 5 U.S.C. chapter 43, managers need to retain the sole and exclusive authority to define the work to be performed via performance expectations. The regulations do require the safeguard that all performance expectations receive a higher-level review as specified in § 9901.406(h) and thus secondary review is already part of the expectation setting process. No change has been made to the proposed regulation based on these comments. </P>
                    <P>Other commenters specifically requested that the term “insofar as practicable” be deleted from § 9901.406(g) as 5 U.S.C. 9902(b)(7)(D) requires the Department of Defense to “provide a means” for ensuring employee participation in the implementation of the system. While we believe the importance of involving employees in the setting of performance expectations is paramount, we acknowledge that there may be cases when an employee is not involved to the fullest extent (e.g., development of standardized objectives for a group of employees performing similar work). Mandating complete and uniform involvement would unnecessarily hinder the development and administration of uniform expectations, where appropriate. No change has been made to the proposed regulation based on these comments. </P>
                    <P>
                        Finally, one commenter suggested substituting “pay pools” for “organizations” in § 9901.406(h). Such a change would require higher- or second-level reviews to reconcile performance expectations across a pay pool rather than an organization. This section appropriately addresses the higher-level review of performance expectations from a broader organizational perspective. However, to the extent a majority of pay pools are structured along organizational lines, this review often has the effect of reconciling expectations across pay pool structures. 
                        <PRTPAGE P="56385"/>
                        No change has been made to the proposed regulation based on this comment. 
                    </P>
                    <HD SOURCE="HD2">Section 9901.407—Minimum Period of Performance </HD>
                    <P>Section 9901.407 addresses the minimum performance period and eligibility for conducting appraisals leading to performance payouts. It describes the requirements for the minimum period of performance under an NSPS performance plan to qualify for an NSPS rating of record. </P>
                    <P>One commenter suggested that the language included in § 9901.407 is misleading. The commenter believes that the language could be interpreted erroneously to mean that an employee with NSPS-covered service related to § 9901.342(i) through (l) may be credited with service performed prior to breaks in service and meet the minimum performance period even if the breaks were not related to a reason expressed in § 9901.342(i) through (l). In response to this comment, we have modified the language to clarify that only service performed prior to a § 9901.342(i) through (l) break in service may be counted towards a minimum period. </P>
                    <P>One commenter recommended changing § 9901.407(b)(1) to indicate only periods of unpaid leave may not be applied toward the 90-day minimum. The proposed regulation intended that paid leave as well as unpaid leave would not be credited toward meeting the requirements of the minimum performance period. NSPS provides for using the modal rating within a pay pool to ensure payouts for employees who do not meet the minimum period due to approved paid leave. While we made no change to the proposed regulation based on this comment, we modified § 9901.342(k) to cover any employee who did not meet the minimum period of performance as a result of approved paid leave. The former language in § 9901.432(k) limited special payouts to employees on “extended leave.” The qualifying language, “extended leave”, was removed. We also note that under § 9901.411, performance periods can be extended to permit an employee who is close to meeting the 90-day minimum to meet that requirement. </P>
                    <P>Another commenter suggested adding that the minimum period of performance must be 90 consecutive calendar days. The regulation accurately provides for allowable breaks (such as leave) and provides credit for nonconsecutive service toward meeting the minimum period. No change has been made to the proposed regulation based on this comment. </P>
                    <HD SOURCE="HD2">Section 9901.408—Employees on Time-Limited Appointments </HD>
                    <P>Section 9901.408 allows evaluation and thereby coverage of NSPS employees in time-limited appointments not expected to exceed 90 days. It permits supervisors to issue performance plans and performance expectations to employees on time-limited assignments appointed for less than 90 days when these plans and expectations are linked to the assigned organization's mission. Supervisors are expected to engage these employees in a dialog relative to performance expectations for the appointment and conduct an evaluation of employees at the end of their appointment consisting of a narrative description of their performance, accomplishments, and contributions. This narrative may serve as documentation and justification for recognition under 5 U.S.C. chapter 45, consistent with and subject to applicable criteria and approval procedures. </P>
                    <P>One commenter requested clarification of the distinction between yearly evaluations and time-limited appointment evaluations that can occur in the same year. The commenter questioned how management would treat the two in relation to pay for performance. Section 9901.408 clearly indicates that a supervisor may give an evaluation to an employee on a time-limited appointment of less than 90 days. Any recognition for performance would be under 5 U.S.C. chapter 45. These employees, for the most part, would not be eligible for pay pool payouts. Section 9901.407 provides the requirement to meet the minimum period of performance of 90 days to be eligible for a rating of record and possible performance payout. Conceivably, an individual could gain eligibility for an NSPS rating of record and pay pool payout by moving to a time-limited appointment of longer duration. However, there is no conflict or overlap between the two processes as they involve different eligibility requirements. No change has been made to the proposed regulation based on this comment. </P>
                    <HD SOURCE="HD2">Section 9901.409—Monitoring and Developing Performance </HD>
                    <P>Section 9901.409 establishes the basic responsibility for supervisors to monitor employee and organizational performance and inform employees of their progress in meeting their performance expectations. Comments on this section were generally favorable, with most commending the section's inclusion. </P>
                    <P>One commenter suggested adding to § 9901.409(a)(3) a requirement for an interim performance review during periods of performance of less than 180 days if it is determined that an employee is not meeting performance expectations. Section 9901.410 provides requirements and criteria for addressing performance that does not meet expectations. That section clearly requires identification and communication of specific performance deficiencies whenever an employee's performance is not meeting expectations. This guidance is applicable without regard to the length of the appointment. Since a requirement for similar communication is already provided, no change has been made to the proposed regulation based on this comment. </P>
                    <P>One commenter requested clarification as to how the developmental process detailed in § 9901.409(b) can be a shared responsibility between management and employees. While we recognize that § 9901.409 has a management focus as it pertains to performance development, all identified processes require dialog between both the supervisor and the employee. Both parties must apply and be receptive to constructive collaboration. In addition, it is incumbent on employees to initiate conversation with their supervisors to pursue development options when needed to improve their performance, as well as to independently pursue education and training that may help them advance. In recognition of these employee-initiated actions for developing performance, the proposed regulation has been modified to reflect that performance development options are “not limited to” those described in this section of the regulation. </P>
                    <P>
                        Another commenter requested revised language requiring ongoing feedback to employees, in addition to the one required by the interim review, to be in writing. This commenter indicated the purpose of requiring all feedback occur in writing was to ensure employee participation in his/her own performance development and avoid confusion that may result from only oral feedback. Face-to-face and oral communications serve to enhance supervisor/employee relationships as well as minimize misunderstanding as the give-and-take in oral communication allows for immediate feedback and clarification of confusing points. Feedback might be as simple as “good job on the briefing.” These short feedback communications may periodically occur in writing, but to require all such feedback to be written 
                        <PRTPAGE P="56386"/>
                        diminishes the opportunity for the kind of face-to-face communication that helps clarify communication and enhance the supervisor/employee relationships. No change has been made to the proposed regulation based on this comment. 
                    </P>
                    <HD SOURCE="HD2">Section 9901.410—Addressing Performance That Does Not Meet Expectations </HD>
                    <P>Section 9901.410 establishes the process for addressing poor performance under NSPS and the responsibility of the supervisor to address such situations. </P>
                    <P>Comments on this section criticized the perceived focus on negative alternatives available to a supervisor for addressing performance that does not meet performance expectations. Suggestions include adding a list that details the developmental options available to the supervisor. The proposed regulation provides positive alternatives for developing performance as identified in § 9901.409. These are viable options for managers to consider but may not be appropriate in all situations. Additionally, among the options described in § 9901.410 are such positive steps as training, improvement periods and reassignments. No change has been made to the proposed regulation based on this comment. </P>
                    <P>Another commenter suggested that there is not enough distinction between addressing poor performance and taking outright adverse action against an employee. The commenter noted that language should be added stating that employees will be provided a reasonable opportunity to improve performance prior to initiation of an adverse action. The commenter suggested adding a section regarding periods for employee improvement. Section 9901.410(a)(2) lists the range of options available to a supervisor, among which adverse action is but one option available. Because this section already lists an employee improvement period among the options available to a supervisor, we feel that NSPS provides sufficient options alongside the developmental alternatives in § 9901.409 to give the supervisor appropriate tools with which to address poor performance. No change has been made to the proposed regulation based on this comment. </P>
                    <HD SOURCE="HD2">Section 9901.411—Appraisal Period </HD>
                    <P>Section 9901.411 sets forth the dates to be associated with annual appraisal periods and ratings of record. </P>
                    <P>One commenter requested the inclusion in § 9901.411(a)(3) of applicable circumstances when an employee can receive an early annual recommended rating. We agree with this recommendation and have added § 9901.412(l) to identify situations when an early annual recommendation rating of record will be issued. </P>
                    <P>In addition, a commenter recommended using July 3 rather than July 1 as the beginning of the time period for early annual recommended ratings, since July 3 is the exact beginning of the 90-day minimum period prior to the end of the appraisal period. We agree and have modified § 9901.411(a)(3) to make this change. </P>
                    <P>Another commenter expressed concern regarding the circumstances for extending the appraisal period. In particular, the commenter questioned whether the extension could be used to give favored employees an unfair amount of time to improve performance, and whether the funds to pay the affected employee alter the pay pool funds available for the following year. The language in § 9901.411 clearly outlines the requirements for using an extended appraisal period. These criteria limit the extension of an appraisal period to the purpose of allowing an employee to meet the minimum period. Further, the regulation specifies that an extension of the appraisal period cannot delay the payout for the applicable pay pool. Therefore, current year funding will be used for payouts provided to employees who complete extended appraisal periods and receive ratings of record. No change has been made to the proposed regulation based on this comment. However, to ensure a clear understanding of the effective date for this type of action, we added § 9901.411(d) to the regulation. </P>
                    <HD SOURCE="HD2">Section 9901.412—Rating and Rewarding Performance </HD>
                    <P>Section 9901.412 identifies responsibilities of the rating official and the Pay Pool Panel and specifies the requirements associated with accomplishing employee ratings of record to reward employee performance. </P>
                    <P>Many commenters felt that the authority granted to the Pay Pool Manager and the Pay Pool Panel to adjust recommended ratings of record is inappropriate and that the authority for an employee's rating of record should rest solely with individuals directly aware of the employee's performance. Many expressed concern that the proposed regulations do not require pay pool authorities to have any exposure to the employee being rated, which could result in changing ratings to ease the organizational payout structure without providing justification for such changes. Another commenter suggested that Pay Pool Manager authority may violate the system requirement for a fair, credible, and transparent employee performance system. One commenter specifically suggested revising § 9901.412(e) so that a Pay Pool Manager must afford the rating official and the employee due process to review any proposed change in rating, and that the Pay Pool Manager must base any subsequent change on review of written documentation from both the official and the employee. </P>
                    <P>The Pay Pool Manager is given final authority to assign ratings of records to employees in NSPS in accordance with merit system principles. Per the discussion under Major Issues, the ability of Pay Pool Panels and Pay Pool Managers to adjust recommended ratings of record reinforces equity across and within pay pools and is a necessary safeguard when rewarding performance from a shared performance fund (i.e. pay pool). Because the nature of NSPS jobs necessitates use of narrative performance standards, it is possible for supervisors to interpret the performance criteria differently, to the advantage or disadvantage of others in the pay pool. Using a multi-member Pay Pool Panel to reconcile ratings ensures a common understanding of criteria across the pay pool and ensures equity and fairness of ratings within the pay pool. Any employee who disagrees with the Pay Pool Manager's determination may request reconsideration of the rating or job objective rating in accordance with § 9901.413. If an employee disagrees with the reconsideration decision of the Pay Pool Manager, the Performance Review Authority provides an extra level of review and will make the final decision on all reconsideration requests pertaining to job objective ratings or ratings of record. The Performance Review Authority only applies performance-related criteria, in a manner consistent with its application throughout the rest of the pay pool, in making decisions on reconsideration requests. Requiring criteria be applied in the same manner across the pay pool ensures that employees working at the same level are rated equitably. In response to comments to ensure the level of management in the best position to observe an employee's work is “heard” before a recommended rating is changed, we added a new paragraph at § 9901.412(f) to specify the Pay Pool Panel responsibility for affording the rating official an opportunity to justify a recommended rating of record before it is changed by the Pay Pool Panel. </P>
                    <P>
                        Some commenters questioned the absence of an independent review authority to identify and remedy 
                        <PRTPAGE P="56387"/>
                        malfeasance by the applying agency. The commenter expressed concern that a review will go to the same people making the initial rating. The Performance Review Authority provides an additional level of review beyond those involved in making the initial rating, functions as the ultimate administrative review authority, and makes the final decisions in the rating process. No change has been made to the proposed regulation based on this comment. 
                    </P>
                    <P>Some commenters lauded the inclusion of § 9901.412(a) as needed protection for NSPS employees. Others, however, felt that the rating process encouraged the forced distribution of ratings as employees are advised that most will receive a Level 3 rating of record. While NSPS designs performance criteria to make distinctions in performance, the regulations and agency practice prohibit requiring any specified number of ratings at a particular rating level. Rather, the distribution of ratings has shifted as a result of standards that challenge employees and set a higher bar for higher-level performance. These standards enable more meaningful distinctions among performers. The past 2 years have demonstrated that the NSPS criteria successfully distinguish and reward multiple levels of performance. Identified performance indicators, upon which rating determinations are based, define and provide further amplification of performance levels. The change in the distribution of ratings as a result of the new criteria, however, does not equate to the concept of “forced rating distribution”. Forced rating distribution occurs when management requires a certain percent of the population to be placed in a certain rating level regardless of how employee performance compares to performance criteria. This is not how NSPS functions. No change has been made to the proposed regulation based on these comments. </P>
                    <P>While the implication by at least one commenter was that a Level 3 rating of record reflects average performance, in fact, Level 3 performance recognizes those employees who performed their identified responsibilities in a “valued” manner and in doing so effectively met all of their performance expectations. NSPS reserves higher-level ratings for employees who have significantly exceeded performance expectations. No change has been made to the proposed regulation based on these comments. </P>
                    <P>Some commenters requested more guidance in § 9901.412(d), renumbered as § 9901.412(e). The concern was that the current guidance led supervisors to believe they did not need to connect a committed misconduct to the employee's ability to perform up to expectations in order to use it to affect an employee's rating of record. Such an understanding is inconsistent with the Department's own guidance on the matter. Another commenter stated that after-the-fact determinations that other conduct had an adverse “impact on the execution” of an employee's duties is not a proper basis for reducing a rating of record below that warranted by the extent to which the employee met or exceeded the written performance expectations, and that if the conduct could be classified as misconduct it should be handled as a disciplinary matter. </P>
                    <P>Under NSPS, to consider the impact of employee misconduct on performance, there must be a nexus between the impact of the misconduct and the execution of the employee's duties or those of the team or organization. While the supervisor will not reference the misconduct on the employee's rating of record, the supervisor may consider how the underlying misconduct negatively impacts the employee's performance, that of his or her co-workers, or the organization's productivity. In response to these comments, and to provide clarity, we revised the regulation at § 9901.412(d), renumbered as § 9901.412(e), to capture essentially what occurs today when considering the impact of work-related misconduct on an employees' job performance in any performance management system. </P>
                    <P>One commenter suggested revising § 9901.412(f), renumbered as § 9901.412(h), requiring the rating official to communicate the payout distribution to the employee along with the final rating of record and number of shares. The commenter also requested adding a sentence to this section indicating that this information will not be communicated to the employee until the final rating of record has been approved by the Pay Pool Manager. We agree with part of the recommendation and revised § 9901.412(f), renumbered as § 9901.412 (h), to add payout distribution to the information communicated to the employee by the rating official. However, we believe the regulation is clear that a rating is only a recommendation until it becomes final upon completion of all appropriate review and signatures and have made no change to the proposed regulation based on this comment. </P>
                    <P>A commenter indicated confusion between language not allowing leave to be credited toward meeting the minimum period and the requirement that the rating of record cannot be lowered based on approved absence from work. To avoid such confusion, we modified § 9901.412(g), renumbered as § 9901.412(i) to clarify that this requirement only pertains after the minimum period has been met. </P>
                    <P>One commenter suggested the inclusion of language prohibiting the use of roll-over ratings from preceding reviews for subsequent review periods. Similar to other Governmentwide performance management systems, the definitions of “performance” and “rating of record” reflect that a rating of record involves evaluation of an employee's performance of assigned duties. Roll-over ratings are inappropriate as they provide employees ratings of record for work not performed during the period being evaluated. We revised § 9901.412(h), renumbered as § 9901.412(j), to add that ratings of record prepared for a previous appraisal period will not be carried over to subsequent appraisal periods without an actual evaluation of the employee's performance during the subsequent appraisal period. </P>
                    <P>A few commenters noted that § 9901.412(h)(3)(iii), renumbered as § 9901.412(j)(3)(iii), gives leeway to the Secretary to use ratings of record for unspecified purposes in the future. The commenters requested that the Department either delete these authorities or specify these purposes in the regulation as opposed to implementing issuances. The Secretary will identify these purposes as the Department develops future programs and policies. These purposes will be identified in implementing issuances. No change was made to the proposed regulations based on these comments. </P>
                    <P>
                        Finally, a commenter suggested that § 9901.412(j), renumbered as § 9901.412(m), needed clarification to show how the ratings discussed in this section differed from a close-out rating. This section permits a supervisor or rating official to prepare an assessment for an employee at any time after the employee has completed the minimum period. An example of such an assessment would be the close-out assessment developed for informational purposes by a supervisor or rating official when they leave a position for which they had rating responsibility for an employee. This assessment is provided to the new supervisor as input for use in determining the employee's rating of record at the end of the appraisal period. We agree with the comment and revised this paragraph to clarify our intent. 
                        <PRTPAGE P="56388"/>
                    </P>
                    <P>One commenter noted that, at present, the proposed regulation does not list specific guidance for those employees in environments where supervisor turnover is frequent. The commenter expresses concern that an NSPS employee would not be given a fair rating by an interim supervisor and that a new permanent supervisor, once appointed, would not have adequate information to rate the employee correctly. DoD is committed to extensive training for managers, supervisors, and employees so that they understand the requirements of the performance management system. Further, DoD is committed to training managers and supervisors, including military members, on how to establish and communicate performance expectations, how to assess employee performance, and how to appropriately translate that assessment into pay adjustments. In addition, under § 9901.412(j), renumbered as § 9901.412(m), we added the requirement that supervisors and rating officials may prepare a performance assessment to provide continuity of ratings upon transfer of a supervisor or employee, which helps to ensure that the new supervisor has a clear understanding of employee performance and contributions. </P>
                    <HD SOURCE="HD2">Section 9901.413—Reconsideration of Ratings </HD>
                    <P>Section 9901.413 specifies the roles and responsibilities of the officials with authority to make reconsideration decisions. </P>
                    <P>One commenter suggested that a fair appeals process be established for employees to appeal their payout or lack of payout. Another commenter indicated a concern that employees have no appeal or grievance rights. Also a commenter suggested revising § 9901.413(a) to give MSPB jurisdiction and stated that MSPB must be given the authority to review performance rating reconsideration requests and grievances by employees who have a good reason to believe that their employing organizations have violated merit system principles. This section clearly states the process for an employee to challenge his or her rating of record or job objective through the NSPS reconsideration process. This reconsideration process does not preclude appropriate challenges in statutory forums or exclude appeals through other avenues. No changes have been made to the proposed regulation based on these comments. </P>
                    <P>Commenters noted that § 9901.413(b) indicates that bargaining unit employees may only challenge a rating of record under negotiated grievance procedures. One commenter noted that this condition was a violation of the NDAA 2008 and that the language should be clarified to not exclude appeals filed under Equal Employment Opportunity Commission, Office of Special Counsel, or Federal Labor Relations Authority domain. This section of the regulation recognizes the requirements of 5 U.S.C. 7121(a)(1) and does not violate the NDAA 2008. The other avenues mentioned are still open to employees. This provision does not prevent an employee from using any statutory appeals procedure, if appropriate, and does not prevent bargaining unit employees from using the agency reconsideration process if these matters are excluded in the negotiated grievance procedure. It simply notes that the negotiated grievance procedure is the exclusive “administrative” procedure available to bargaining unit employees where such procedures exist. No change has been made to the proposed regulation based on these comments. </P>
                    <P>Another commenter requested that the language be amended to include payouts under the jurisdiction of the negotiated grievance process. This provision does not impact the ability of the parties to negotiate on a negotiated grievance procedure. Payout decisions are not explicitly excluded from, nor are they covered by, negotiated grievance procedures because of any provision of the regulation. To the extent that matters related to NSPS payout decisions can be covered by a negotiated grievance procedure they are, but any grievance arbitration decision must be consistent with these regulations and 5 U.S.C. 9902, a requirement of 5 U.S.C. 7122. No change has been made to the proposed regulation based on these comments. </P>
                    <P>A commenter requested clarification in § 9901.413(c) regarding whether a payout recalculation is based only on a change to the rating of record. Another commenter expressed concern that the language in § 9901.413(c) does not state clearly that the payout will be recalculated based on the share range for the rating of record assigned upon reconsideration. We agree and revised this section to add language clarifying that, in the event a reconsideration results in an adjusted job objective rating or rating of record, the Pay Pool Manager will recalculate the employee's performance payout amount and distribution; and salary adjustments will be based on the share range appropriate for the adjusted rating of record as identified in § 9901.342(f). </P>
                    <P>Another commenter noted that this paragraph does not provide enough information about the authority of the Pay Pool Manager. No change has been made to the proposed regulation based on this comment since the authority and responsibilities of the Pay Pool Manager do not vary during the reconciliation process. </P>
                    <P>Finally, one commenter recommended adding a paragraph to § 9901.413 suggesting the use of alternative dispute resolution techniques to resolve disputes regarding reconsideration of ratings. We agree and revised this section to add language clarifying the use of alternative dispute resolution is permissible within the reconsideration process. </P>
                    <HD SOURCE="HD1">VI. Next Steps </HD>
                    <P>
                        The National Defense Authorization Act for Fiscal Year 2008 requires that this rule be considered a major rule for the purpose of section 801 of title 5, United States Code. As such, before it can take effect, the Department will submit to each House of the Congress and to the Comptroller General a report containing the rule, a general statement relating to the rule, and the proposed effective date of the rule. The rule may not be effective until the date occurring 60 days after the later of (1) Congressional receipt of the report, or (2) the date the rule is published in the 
                        <E T="04">Federal Register</E>
                        . Congress has the opportunity to delay implementation of the rule based on the procedures set forth in 5 U.S.C. 801-808. 
                    </P>
                    <P>DoD intends to continue implementing the new NSPS HR system in phases or spirals. The Act provides that not more than 100,000 employees may be added to the System in any calendar year. As has been the case from the beginning, NSPS continues to be an event-driven system, and no decisions have been made at this time regarding when or whether additional groups or organizations will be converted to NSPS during calendar year 2009 and beyond. Such decisions will be based on the best interests of the Department. </P>
                    <P>The Act also requires the Comptroller General to conduct annual reviews in calendar years 2008, 2009, and 2010. The reviews will address—</P>
                    <P>(1) Employee satisfaction with the National Security Personnel System, and </P>
                    <P>(2) The extent to which the Department of Defense has effectively implemented accountability mechanisms and internal safeguards. </P>
                    <FP>DoD will fully support the Comptroller General in any review of the System. </FP>
                    <HD SOURCE="HD2">E.O. 12866, Regulatory Review </HD>
                    <P>
                        DoD and OPM have determined that this action is a significant regulatory action within the meaning of Executive 
                        <PRTPAGE P="56389"/>
                        Order 12866 because there is significant public interest in the National Security Personnel System. DoD and OPM have analyzed the expected costs and benefits of the revised HR system, and that analysis is presented below. 
                    </P>
                    <P>Among the NSPS requirements is to maintain a system that is competitive, cost effective, and fiscally sound, while also being flexible, credible, and trusted. NSPS will allow DoD to move towards market-sensitive pay, to continue pay increases based on performance, and to have the flexibility to offer competitive salaries. While these flexibilities will improve DoD's ability to attract and retain a high-performing workforce, actual payroll costs under this system are constrained by the amount budgeted for overall DoD payroll expenditures, as is the case with the present GS pay system. </P>
                    <P>The continuing implementation of NSPS will result in some additional program implementation costs. This includes delivering training specifically for NSPS, conducting outreach to employees and other parties, and improving automated systems associated with NSPS performance management. </P>
                    <P>As has been the practice with implementing NSPS and other alternative personnel systems, DoD expects to incur an initial payroll cost related to the conversion of employees to the pay banding system. This includes a within-grade increase (WGI) “buyout,” in which an employee's basic pay, upon conversion, is adjusted by the amount of the WGI earned to date. While this increase is paid earlier than scheduled, it represents a cost that would have been incurred under the current system at some point. However, under NSPS, WGIs no longer exist. Once covered employees are under NSPS, such pay increases will be based on performance. Accordingly, the total cost of the accelerated WGI “buyout” is not treated as a “new” cost attributed to implementation of NSPS, since it is a cost that DoD would bear under the current HR system. The portion of the WGI buyout cost attributable to NSPS implementation is the marginal difference between paying out the earned portion of a WGI upon conversion and the cost of paying the same WGI according to the current schedule. The marginal cost of the accelerated payment of earned WGIs is difficult to estimate, but is not a significant factor in the cost benefit analysis for regulatory review purposes. </P>
                    <P>DoD estimates the overall costs associated with continuing to implement NSPS to all eligible employees will be approximately $143 million from Fiscal Years 2009 through 2011. If it is determined that a category of eligible employees will not be converted to NSPS, these costs will decrease significantly. Accordingly, these estimates are based upon past experience, guidance from the Comptroller General, and ensuring that implementation costs are determined in the same way across the services and Defense Agencies and captured in official accounting systems. </P>
                    <P>The primary benefit to the public of NSPS resides in the HR flexibilities that will enable DoD to attract, build, and retain a high-performing workforce focused on effective and efficient mission accomplishment. A performance-based pay system that rewards excellent performance will result in a more qualified and proficient workforce and will generate a greater return on investment in terms of productivity and effectiveness. Taken as a whole, the changes included in these proposed regulations will improve upon the original NSPS regulations and result in a contemporary, merit-based HR system that focuses on performance, generates respect and trust, and supports the primary mission of DoD. </P>
                    <P>This rule has been reviewed by the Office of Management and Budget in accordance with E.O. 12866. </P>
                    <HD SOURCE="HD2">Regulatory Flexibility Act </HD>
                    <P>DoD and OPM have determined that these regulations would not have a significant economic impact on a substantial number of small entities because they would apply only to Federal agencies and employees. </P>
                    <HD SOURCE="HD2">Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35) </HD>
                    <P>This proposed regulatory action will not impose any additional reporting or recordkeeping requirements under the Paperwork Reduction Act. </P>
                    <HD SOURCE="HD2">E.O. 12988, Civil Justice Reform </HD>
                    <P>This proposed regulation is consistent with the requirements of E.O. 12988. The regulation clearly specifies the effects on existing Federal law or regulation; provides clear legal standards; has no retroactive effects; specifies procedures for administrative and court actions; defines key terms; and is drafted clearly. </P>
                    <HD SOURCE="HD2">E.O. 13132, Federalism </HD>
                    <P>DoD and OPM have determined these proposed regulations would not have Federalism implications because they would apply only to Federal agencies and employees. The proposed regulations would not have financial or other effects on States, the relationship between the Federal Government and the States, or the distribution of power and responsibilities among the various levels of government. </P>
                    <HD SOURCE="HD2">Unfunded Mandates </HD>
                    <P>These proposed regulations would not result in the expenditure by State, local, or tribal governments of more than $100 million annually. Thus, no written assessment of unfunded mandates is required. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 5 CFR Part 9901 </HD>
                        <P>Administrative practice and procedure, Government employees, Labor management relations, Labor unions, Reporting and recordkeeping requirements, Wages.</P>
                    </LSTSUB>
                    <SIG>
                        <P>Office of Personnel Management. </P>
                        <NAME>Michael W. Hager, </NAME>
                        <TITLE>Acting Director, Office of Personnel Management. </TITLE>
                        <P>Department of Defense. </P>
                        <NAME>Gordon England, </NAME>
                        <TITLE>Deputy Secretary of Defense.</TITLE>
                    </SIG>
                    <REGTEXT TITLE="5" PART="9901">
                        <AMDPAR>Accordingly, under the authority of section 9902 of title 5, United States Code, the Department of Defense and the Office of Personnel Management are revising part 9901 of title 5, Code of Federal Regulations to read as follows: </AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 9901—DEPARTMENT OF DEFENSE NATIONAL SECURITY PERSONNEL SYSTEM (NSPS) </HD>
                            <CONTENTS>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart A—General Provisions </HD>
                                    <SECHD>Sec. </SECHD>
                                    <SECTNO>9901.101 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <SECTNO>9901.102 </SECTNO>
                                    <SUBJECT>Eligibility and coverage. </SUBJECT>
                                    <SECTNO>9901.103 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <SECTNO>9901.104 </SECTNO>
                                    <SUBJECT>Scope of authority. </SUBJECT>
                                    <SECTNO>9901.105 </SECTNO>
                                    <SUBJECT>OPM coordination and approval. </SUBJECT>
                                    <SECTNO>9901.106 </SECTNO>
                                    <SUBJECT>Relationship to other provisions. </SUBJECT>
                                    <SECTNO>9901.107 </SECTNO>
                                    <SUBJECT>Program evaluation. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart B—Classification </HD>
                                    <HD SOURCE="HD1">General</HD>
                                    <SECTNO>9901.201 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <SECTNO>9901.202 </SECTNO>
                                    <SUBJECT>Coverage. </SUBJECT>
                                    <SECTNO>9901.203 </SECTNO>
                                    <SUBJECT>Waivers. </SUBJECT>
                                    <SECTNO>9901.204 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <HD SOURCE="HD1">Classification Structure </HD>
                                    <SECTNO>9901.211 </SECTNO>
                                    <SUBJECT>Career groups. </SUBJECT>
                                    <SECTNO>9901.212 </SECTNO>
                                    <SUBJECT>Pay schedules and pay bands. </SUBJECT>
                                    <HD SOURCE="HD1">Classification Process </HD>
                                    <SECTNO>9901.221 </SECTNO>
                                    <SUBJECT>Classification requirements. </SUBJECT>
                                    <SECTNO>9901.222 </SECTNO>
                                    <SUBJECT>Review of classification decisions. </SUBJECT>
                                    <SECTNO>9901.223 </SECTNO>
                                    <SUBJECT>Appeal to DoD for review of classification decisions. </SUBJECT>
                                    <SECTNO>9901.224 </SECTNO>
                                    <SUBJECT>Appeal to OPM for review of classification decisions. </SUBJECT>
                                    <HD SOURCE="HD1">Transitional Provisions</HD>
                                    <SECTNO>9901.231 </SECTNO>
                                    <SUBJECT>Conversion of positions and employees to NSPS classification system. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <PRTPAGE P="56390"/>
                                    <HD SOURCE="HED">Subpart C—Pay and Pay Administration </HD>
                                    <HD SOURCE="HD1">General</HD>
                                    <SECTNO>9901.301 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <SECTNO>9901.302 </SECTNO>
                                    <SUBJECT>Coverage. </SUBJECT>
                                    <SECTNO>9901.303 </SECTNO>
                                    <SUBJECT>Waivers. </SUBJECT>
                                    <SECTNO>9901.304 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <SECTNO>9901.305 </SECTNO>
                                    <SUBJECT>Rate of pay. </SUBJECT>
                                    <HD SOURCE="HD1">Overview of Pay System</HD>
                                    <SECTNO>9901.311 </SECTNO>
                                    <SUBJECT>Major features. </SUBJECT>
                                    <SECTNO>9901.312 </SECTNO>
                                    <SUBJECT>Maximum rates of base salary and adjusted salary. </SUBJECT>
                                    <SECTNO>9901.313 </SECTNO>
                                    <SUBJECT>Aggregate compensation limitations. </SUBJECT>
                                    <SECTNO>9901.314 </SECTNO>
                                    <SUBJECT>National security compensation comparability. </SUBJECT>
                                    <HD SOURCE="HD1">Rate Ranges and General Salary Increases</HD>
                                    <SECTNO>9901.321 </SECTNO>
                                    <SUBJECT>Structure. </SUBJECT>
                                    <SECTNO>9901.322 </SECTNO>
                                    <SUBJECT>Setting and adjusting rate ranges. </SUBJECT>
                                    <SECTNO>9901.323 </SECTNO>
                                    <SUBJECT>Eligibility for general salary increase. </SUBJECT>
                                    <HD SOURCE="HD1">Local Market Supplements</HD>
                                    <SECTNO>9901.331 </SECTNO>
                                    <SUBJECT>General. </SUBJECT>
                                    <SECTNO>9901.332 </SECTNO>
                                    <SUBJECT>Standard and targeted local market supplements. </SUBJECT>
                                    <SECTNO>9901.333 </SECTNO>
                                    <SUBJECT>Setting and adjusting local market supplements. </SUBJECT>
                                    <SECTNO>9901.334 </SECTNO>
                                    <SUBJECT>Eligibility for pay increase associated with a supplement adjustment. </SUBJECT>
                                    <HD SOURCE="HD1">Performance-Based Pay</HD>
                                    <SECTNO>9901.341 </SECTNO>
                                    <SUBJECT>General. </SUBJECT>
                                    <SECTNO>9901.342 </SECTNO>
                                    <SUBJECT>Performance payouts. </SUBJECT>
                                    <SECTNO>9901.343 </SECTNO>
                                    <SUBJECT>Pay reduction based on unacceptable performance and/or conduct. </SUBJECT>
                                    <SECTNO>9901.344 </SECTNO>
                                    <SUBJECT>Other performance payments. </SUBJECT>
                                    <SECTNO>9901.345 </SECTNO>
                                    <SUBJECT>Accelerated Compensation for Developmental Positions (ACDP). </SUBJECT>
                                    <HD SOURCE="HD1">Pay Administration</HD>
                                    <SECTNO>9901.351 </SECTNO>
                                    <SUBJECT>General. </SUBJECT>
                                    <SECTNO>9901.352 </SECTNO>
                                    <SUBJECT>Setting an employee's starting pay. </SUBJECT>
                                    <SECTNO>9901.353 </SECTNO>
                                    <SUBJECT>Setting pay upon reassignment. </SUBJECT>
                                    <SECTNO>9901.354 </SECTNO>
                                    <SUBJECT>Setting pay upon promotion. </SUBJECT>
                                    <SECTNO>9901.355 </SECTNO>
                                    <SUBJECT>Setting pay upon reduction in band. </SUBJECT>
                                    <SECTNO>9901.356 </SECTNO>
                                    <SUBJECT>Pay retention. </SUBJECT>
                                    <HD SOURCE="HD1">Premium Pay </HD>
                                    <SECTNO>9901.361 </SECTNO>
                                    <SUBJECT>General provisions. </SUBJECT>
                                    <SECTNO>9901.362 </SECTNO>
                                    <SUBJECT>Modification of standard provisions. </SUBJECT>
                                    <SECTNO>9901.363 </SECTNO>
                                    <SUBJECT>Premium pay for health care personnel. </SUBJECT>
                                    <SECTNO>9901.364 </SECTNO>
                                    <SUBJECT>Foreign language proficiency pay. </SUBJECT>
                                    <HD SOURCE="HD1">Conversion Provisions</HD>
                                    <SECTNO>9901.371 </SECTNO>
                                    <SUBJECT>Conversion into NSPS pay system. </SUBJECT>
                                    <SECTNO>9901.372 </SECTNO>
                                    <SUBJECT>Conversion or movement out of NSPS pay system. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart D—Performance Management</HD>
                                    <SECTNO>9901.401 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <SECTNO>9901.402 </SECTNO>
                                    <SUBJECT>Coverage. </SUBJECT>
                                    <SECTNO>9901.403 </SECTNO>
                                    <SUBJECT>Waivers. </SUBJECT>
                                    <SECTNO>9901.404 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <SECTNO>9901.405 </SECTNO>
                                    <SUBJECT>Performance management system requirements. </SUBJECT>
                                    <SECTNO>9901.406 </SECTNO>
                                    <SUBJECT>Setting and communicating performance expectations. </SUBJECT>
                                    <SECTNO>9901.407 </SECTNO>
                                    <SUBJECT>Minimum period of performance. </SUBJECT>
                                    <SECTNO>9901.408 </SECTNO>
                                    <SUBJECT>Employees on time-limited appointments. </SUBJECT>
                                    <SECTNO>9901.409 </SECTNO>
                                    <SUBJECT>Monitoring and developing performance. </SUBJECT>
                                    <SECTNO>9901.410 </SECTNO>
                                    <SUBJECT>Addressing performance that does not meet expectations. </SUBJECT>
                                    <SECTNO>9901.411 </SECTNO>
                                    <SUBJECT>Appraisal period. </SUBJECT>
                                    <SECTNO>9901.412 </SECTNO>
                                    <SUBJECT>Rating and rewarding performance. </SUBJECT>
                                    <SECTNO>9901.413 </SECTNO>
                                    <SUBJECT>Reconsideration of ratings.</SUBJECT>
                                </SUBPART>
                            </CONTENTS>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P>5 U.S.C. 9902; sec. 1106(b), Pub. L. 110-181, 122 Stat. 3. </P>
                            </AUTH>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart A—General Provisions </HD>
                                <SECTION>
                                    <SECTNO>§ 9901.101 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <P>(a) This part contains regulations governing the National Security Personnel System (NSPS) within the Department of Defense (DoD), as authorized by 5 U.S.C. 9902. Consistent with 5 U.S.C. 9902, as amended by section 1106 of the National Defense Authorization Act for Fiscal Year 2008 (NDAA 2008), these regulations waive or modify various statutory provisions that would otherwise be applicable to affected DoD employees. These regulations are prescribed jointly by the Secretary of Defense and the Director of the Office of Personnel Management (OPM). The Secretary may establish implementing issuances to supplement any matter covered by these regulations.</P>
                                    <P>(b)(1) This part is designed to meet a number of essential requirements for the implementation of a new human resources management system for DoD. The guiding principles for establishing these requirements are to put mission first; respect the individual; protect rights guaranteed by law; support the statutory merit system principles in 5 U.S.C. 2301; value talent, performance, leadership, and commitment to public service; be flexible, understandable, credible, responsive, and executable; ensure accountability at all levels; balance human resources system interoperability with unique mission requirements; and be competitive and cost effective. </P>
                                    <P>
                                        (2) The key operational characteristics and requirements of NSPS, which these regulations are designed to facilitate, are as follows: 
                                        <E T="03">High-Performing Workforce and Management</E>
                                        —employees and supervisors are compensated and retained based on their performance and contribution to mission; 
                                        <E T="03">Agile and Responsive Workforce and Management</E>
                                        —workforce can be easily sized, shaped, and deployed to meet changing mission requirements; 
                                        <E T="03">Credible and Trusted</E>
                                        —system assures openness, clarity, accountability, and adherence to the public employment principles of merit and fitness; 
                                        <E T="03">Fiscally Sound</E>
                                        —aggregate increases in civilian payroll, at the appropriations level, will conform to OMB fiscal guidance; 
                                        <E T="03">Supporting Infrastructure</E>
                                        —information technology support, and training and change management plans are available and funded; and 
                                        <E T="03">Schedule</E>
                                        —NSPS will be operational and demonstrate success prior to November 2009. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.102 </SECTNO>
                                    <SUBJECT>Eligibility and coverage. </SUBJECT>
                                    <P>(a) Pursuant to the provisions of 5 U.S.C. 9902, civilian employees of DoD are eligible for coverage under one or more of subparts B through D of this part, except to the extent specifically prohibited by law. </P>
                                    <P>(b) At his or her sole and exclusive discretion, the Secretary may decide to apply subparts B through D to a specific category or categories of eligible civilian employees in organizations and functional units of the Department at any time in accordance with the provisions of 5 U.S.C. 9902, except that no more than 100,000 employees per year may be moved into NSPS. However, no category of employees may be covered by subparts B or C of this part unless that category is also covered by subpart D of this part. DoD will advise OPM in advance regarding the extension of NSPS coverage to specific categories of DoD employees under this paragraph. The Secretary will notify affected employees and labor organizations in accordance with the requirements of 5 U.S.C. chapter 71 regarding a decision to extend NSPS coverage to any bargaining unit employees. </P>
                                    <P>(c) Until the Secretary makes a determination under paragraph (b) of this section to apply the provisions of one or more subparts of this part to a particular category or categories of eligible employees in organizations and functional units, those employees will continue to be covered by the applicable Federal laws and regulations that would apply to them in the absence of this part. All personnel actions affecting DoD employees will be based on the Federal laws and regulations applicable to them on the effective date of the action. </P>
                                    <P>
                                        (d) Any new NSPS classification, pay, and performance management system covering Senior Executive Service (SES) members will be consistent with the policies and procedures established by the Governmentwide SES pay-for-performance framework authorized by 5 U.S.C. chapter 53, subchapter VIII, and applicable OPM regulations. If the Secretary determines that SES members employed by DoD should be covered by classification, pay, and performance management provisions that differ substantially from the Governmentwide 
                                        <PRTPAGE P="56391"/>
                                        SES pay-for-performance framework, the Secretary and the Director will issue joint regulations consistent with all of the requirements of 5 U.S.C. 9902. 
                                    </P>
                                    <P>(e) At his or her sole and exclusive discretion, the Secretary may decide to rescind the application of one or more subparts of this part to a particular category of employees or an organization or functional unit, subject to § 9901.372 and any related implementing issuances. The Secretary will notify affected employees and labor organizations in advance of a decision to rescind the application of one or more subparts of this part to them. </P>
                                    <P>(f)(1) Notwithstanding any other provision of this part, but subject to paragraphs (f)(2) and (3) of this section, the Secretary may, at his or her sole and exclusive discretion, decide to apply one or more subparts of this part as of a specified effective date to a category of employees in organizational and functional units not currently eligible for coverage because of coverage under a system established by a provision of law outside the waivable or modifiable chapters of title 5, U.S. Code. </P>
                                    <P>(2) Paragraph (f)(1) of this section applies only if the provision of law outside those waivable or modifiable title 5 chapters provides discretionary authority to cover employees under a given waivable or modifiable title 5 chapter or to cover them under a separate system established by the Secretary. </P>
                                    <P>(3) In applying paragraph (f)(1) of this section with respect to coverage under subparts B and C of this part, the affected employees will be converted directly to the NSPS pay system from their current pay system. The conversion of such employees into NSPS will be governed by the rules in §§ 9901.231and 9901.371 and applicable implementing issuances prescribed by the Secretary under §§ 9901.231(b) and 9901.371(b). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.103 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>In this part:</P>
                                    <P>
                                        <E T="03">Appraisal period</E>
                                         means the period of time for reviewing employee performance (as described in § 9901.411). 
                                    </P>
                                    <P>
                                        <E T="03">Band</E>
                                         means 
                                        <E T="03">pay band</E>
                                        . 
                                    </P>
                                    <P>
                                        <E T="03">Basic pay</E>
                                         means an employee's pay before any deductions and exclusive of additional pay of any kind, except as expressly provided by applicable law or regulation. For the specific purposes prescribed in § 9901.331(d) only, basic pay includes any local market supplement. In subpart C, when basic pay is exclusive of any additional pay, the term “base salary” is used, and when basic pay includes a local market supplement, the term “adjusted salary” is used. 
                                    </P>
                                    <P>
                                        <E T="03">Career group</E>
                                         means a grouping of one or more associated or related occupations. A career group may include one or more pay schedules. 
                                    </P>
                                    <P>
                                        <E T="03">Comparable pay band</E>
                                         or 
                                        <E T="03">comparable level of work</E>
                                         means pay bands with the equivalent level of work, based on the NSPS classification structure, within and across varying pay schedules and career groups, regardless of the specific earning potential of the bands. When moving from a non-NSPS position to NSPS, the band of the NSPS position is determined to be at a comparable level of work to the grade or level of the non-NSPS position based on application of the NSPS classification structure, as described in implementing issuances. 
                                    </P>
                                    <P>
                                        <E T="03">Competencies</E>
                                         means the measurable or observable knowledge, skills, abilities, behaviors, and other characteristics that an individual needs to perform a particular job or job function successfully. 
                                    </P>
                                    <P>
                                        <E T="03">Component</E>
                                         means the Office of the Secretary of Defense (OSD), the Military Departments, Office of the Chairman of the Joint Chiefs of Staff and the Joint Staff, the Combatant Commands, the Office of the Inspector General of the Department of Defense, the Defense Agencies, the DoD Field Activities, and all other organizational entities in the Department of Defense. 
                                    </P>
                                    <P>
                                        <E T="03">Contributing factor</E>
                                         means attributes of job performance that are significant to the accomplishment of individual job objectives. 
                                    </P>
                                    <P>
                                        <E T="03">Contribution</E>
                                         means a work product, service, output, or result provided or produced by an employee or group of employees that supports the Departmental or organizational mission, goals, or objectives. 
                                    </P>
                                    <P>
                                        <E T="03">Day</E>
                                         means a calendar day, unless expressly provided otherwise under applicable law or regulations. 
                                    </P>
                                    <P>
                                        <E T="03">Department</E>
                                         or 
                                        <E T="03">DoD</E>
                                         means the Department of Defense. 
                                    </P>
                                    <P>
                                        <E T="03">Director</E>
                                         means the Director of the Office of Personnel Management. 
                                    </P>
                                    <P>
                                        <E T="03">Employee</E>
                                         has the meaning given that term in 5 U.S.C. 2105. 
                                    </P>
                                    <P>
                                        <E T="03">General Schedule</E>
                                         or 
                                        <E T="03">GS</E>
                                         means the General Schedule classification and pay system established under chapter 51 and subchapter III of chapter 53 of title 5, U.S. Code. 
                                    </P>
                                    <P>
                                        <E T="03">Higher pay band</E>
                                         or 
                                        <E T="03">higher level of work</E>
                                         means a pay band designated to be a higher level of work than an employee's currently assigned band, based on the NSPS classification structure, either within or across varying pay schedules and career groups, regardless of the specific earning potential of the band. When moving from a non-NSPS position to NSPS, the band of the NSPS position is determined to be at a higher level of work than the grade or level of the non-NSPS position based on application of the NSPS classification structure, as described in implementing issuances. 
                                    </P>
                                    <P>
                                        <E T="03">Implementing issuance(s)</E>
                                         means a document or documents issued by the Secretary, Deputy Secretary, Principal Staff Assistants (as authorized by the Secretary), or Secretaries and Under Secretaries of the Military Departments to establish or carry out a policy or procedure implementing this part. These issuances may apply Department-wide or to any part of DoD as determined by the Secretary. 
                                    </P>
                                    <P>
                                        <E T="03">Job objective</E>
                                         means an expression of performance expectations in the performance plan that is aligned with the organization's goal(s) and mission(s). 
                                    </P>
                                    <P>
                                        <E T="03">Lower pay band</E>
                                         or 
                                        <E T="03">lower level of work</E>
                                         means a pay band designated to be a lower level of work than an employee's currently assigned band, based on the NSPS classification structure, either within or across varying pay schedules and career groups, regardless of the specific earning potential of the band. When moving from a non-NSPS position to NSPS, the band of the NSPS position is determined to be at a lower level of work than the grade or level of the non-NSPS position based on application of the NSPS classification structure, as described in implementing issuances. 
                                    </P>
                                    <P>
                                        <E T="03">Military Department</E>
                                         means the Department of the Army, the Department of the Navy, or the Department of the Air Force. 
                                    </P>
                                    <P>
                                        <E T="03">National Security Personnel System (NSPS)</E>
                                         means the human resources management system established under 5 U.S.C. 9902(a) and the regulations in this part. 
                                    </P>
                                    <P>
                                        <E T="03">Occupational series</E>
                                         means a group or family of positions performing similar types of work. Occupational series are assigned a number for workforce information purposes (e.g., 0110, Economist Series; 1410, Librarian Series). 
                                    </P>
                                    <P>
                                        <E T="03">OPM</E>
                                         means the Office of Personnel Management. 
                                    </P>
                                    <P>
                                        <E T="03">Pay band</E>
                                         or 
                                        <E T="03">band</E>
                                         means a work level and associated pay range within a pay schedule. 
                                    </P>
                                    <P>
                                        <E T="03">Pay pool</E>
                                         means the organizational elements/units or other categories of employees that are combined for the purpose of determining performance payouts. Each employee is in only one pay pool at a time. 
                                        <E T="03">Pay pool</E>
                                         also refers to the funds designated for performance payouts to employees covered by a pay pool. 
                                        <PRTPAGE P="56392"/>
                                    </P>
                                    <P>
                                        <E T="03">Pay Pool Manager</E>
                                         means the management official designated to manage the pay pool, resolve discrepancies, ensure consistency and equity within the pay pool, and approve recommendations concerning employee rating of record, share assignment, and payout distribution between base salary increases and bonuses. 
                                    </P>
                                    <P>
                                        <E T="03">Pay Pool Panel</E>
                                         means management officials of the organizations or functions represented in the pay pool who assist the Pay Pool Manager in the reconciliation of recommended ratings of record, share assignments, and payout distribution. The Pay Pool Panel includes the Pay Pool Manager. 
                                    </P>
                                    <P>
                                        <E T="03">Pay schedule</E>
                                         means a set of related pay bands for a specified category of employees within a career group. 
                                    </P>
                                    <P>
                                        <E T="03">Performance</E>
                                         means accomplishment of work assignments or responsibilities and contribution to achieving organizational goals, including an employee's behavior and professional demeanor (actions, attitude, and manner of performance), as demonstrated by his or her approach to completing work assignments. 
                                    </P>
                                    <P>
                                        <E T="03">Performance Review Authority</E>
                                         means one or more management officials who manage and oversee the operation of one or more pay pools and ensure procedural and funding consistency among pay pools under its authority. 
                                    </P>
                                    <P>
                                        <E T="03">Principal Staff Assistants</E>
                                         means senior officials of the Office of the Secretary who report directly to the Secretary or Deputy Secretary of Defense. 
                                    </P>
                                    <P>
                                        <E T="03">Promotion</E>
                                         means the movement of an employee from one pay band to a higher pay band while continuously employed. This includes movement of an employee currently covered by a non-NSPS Federal personnel system to an NSPS position determined to be at a higher level of work. 
                                    </P>
                                    <P>
                                        <E T="03">Rating of record</E>
                                         means the final numerical rating and associated narrative justification assigned to a performance appraisal by a Pay Pool Manager—
                                    </P>
                                    <P>(1) After completion of an appraisal period covering an employee's performance of assigned duties against performance expectations over the applicable period; or </P>
                                    <P>(2) As needed following an unacceptable rating of record to reflect a substantial and sustained change in the employee's performance since the last rating of record. </P>
                                    <P>
                                        <E T="03">Reassignment</E>
                                         means the movement of an employee, either employee-initiated or management-directed, to a different position or set of duties in the same or a comparable pay band while continuously employed. This includes the movement of an employee currently covered by a non-NSPS Federal personnel system to an NSPS position determined to be at a comparable level of work. 
                                    </P>
                                    <P>
                                        <E T="03">Reduction in band</E>
                                         means the voluntary or involuntary movement of an employee from one pay band to a lower pay band on a permanent basis while continuously employed. This includes movement of an employee currently covered by a non-NSPS Federal personnel system to an NSPS position determined to be at a lower level of work. 
                                    </P>
                                    <P>
                                        <E T="03">Secretary</E>
                                         means the Secretary of Defense, consistent with 10 U.S.C. 113. 
                                    </P>
                                    <P>
                                        <E T="03">SES</E>
                                         means the Senior Executive Service established under 5 U.S.C. chapter 31, subchapter II. 
                                    </P>
                                    <P>
                                        <E T="03">SL/ST</E>
                                         refers to an employee serving in a senior-level position paid under 5 U.S.C. 5376. The term “SL” identifies a senior-level employee covered by 5 U.S.C. 3324 and 5108. The term “ST” identifies an employee who is appointed under the special authority in 5 U.S.C. 3325 to a scientific or professional position established under 5 U.S.C. 3104. 
                                    </P>
                                    <P>
                                        <E T="03">Unacceptable performance</E>
                                         means performance of an employee which fails to meet one or more performance expectations, as amplified through work assignments or other instructions, for which the employee is held individually accountable. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.104 </SECTNO>
                                    <SUBJECT>Scope of authority. </SUBJECT>
                                    <P>The authority for this part is 5 U.S.C. 9902. The provisions in the following chapters of title 5, U.S. Code, and any related regulations, may be waived or modified in exercising the authority in 5 U.S.C. 9902: </P>
                                    <P>(a) Chapter 43, dealing with performance appraisal systems; </P>
                                    <P>(b) Chapter 51, dealing with General Schedule job classification; </P>
                                    <P>(c) Chapter 53, dealing with pay for General Schedule employees, and pay for certain other employees, except as provided in § 9901.303; and </P>
                                    <P>(d) Chapter 55, subchapter V, dealing with premium pay, except sections 5544 and 5545b. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.105 </SECTNO>
                                    <SUBJECT>OPM coordination and approval. </SUBJECT>
                                    <P>(a) The Secretary will coordinate with or request approval from OPM in advance, as applicable, regarding the proposed promulgation of certain implementing issuances and certain other actions related to the ongoing operation of the NSPS where such actions could have a significant impact on other Federal agencies and the Federal civil service as a whole. Pre-decisional coordination under paragraph (b) of this section is intended as an internal DoD/OPM matter to recognize the Secretary's special authority to direct the operations of DoD pursuant to title 10, U.S. Code, as well as the Director's institutional responsibility to oversee the Federal civil service system pursuant to 5 U.S.C. chapter 11. Approval from OPM is required in certain circumstances, as provided in paragraph (c) of this section. </P>
                                    <P>(b) DoD will coordinate with OPM prior to—</P>
                                    <P>(1) Establishing or substantially revising career groups, occupational pay schedules, and pay bands under §§ 9901.211 and 9901.212(a); </P>
                                    <P>(2) Establishing alternative or additional qualification standards for a particular occupational series, career group, occupational pay schedule, and/or pay band under § 9901.212(d) that significantly differ from Governmentwide standards; </P>
                                    <P>(3) Establishing alternative or additional occupational series for a particular career group or occupation under § 9901.221(b)(1) that differ from Governmentwide series and/or standards; </P>
                                    <P>(4) Establishing alternative or additional classification criteria for a particular career group or occupation under § 9901.221(b)(1) that differ from Governmentwide classification standards; </P>
                                    <P>(5) Establishing maximum rates of base salary under § 9901.312(a); </P>
                                    <P>(6) Establishing a higher adjusted salary rate cap for a designated category of positions under § 9901.312(d); </P>
                                    <P>(7) Approving waivers under § 9901.313(a)(3) of the normally applicable aggregate compensation limit; </P>
                                    <P>(8) Establishing and adjusting pay ranges for occupational pay schedules and pay bands under §§ 9901.321(a) and 9901.322; </P>
                                    <P>(9) Determining targeted general salary increases under § 9901.323(a)(2); and </P>
                                    <P>(10) Establishing and adjusting targeted local market supplements under §§ 9901.332(c) and 9901.333(b). </P>
                                    <P>(c) The Secretary will request approval from the Director prior to—</P>
                                    <P>(1) Establishing policies regarding the student loan repayment program under § 9901.303(c) that differ from Governmentwide policies with respect to repayment amounts and service commitments; </P>
                                    <P>
                                        (2) Approving waivers of normally applicable premium pay limitations, as authorized under § 9901.362(a)(2); 
                                        <PRTPAGE P="56393"/>
                                    </P>
                                    <P>(3) Determining pay bands for which an FLSA-exempt employee is paid overtime at an hourly rate equal to the employee's adjusted base salary hourly rate, as authorized under § 9901.362(b)(6)(i); and </P>
                                    <P>(4) Establishing new hazardous duty pay categories under § 9901.362(i)(3). </P>
                                    <P>(d) When a matter requiring OPM coordination is submitted to the Secretary for decision, the Director will be provided an opportunity, as part of the Department's normal coordination process, to review and comment on the recommendations and officially concur or nonconcur with all or part of them. The Secretary will take the Director's comments and concurrence/nonconcurrence into account, advise the Director of his or her determination, and provide the Director with reasonable advance notice of the effective date of the matter. Thereafter, the Secretary and the Director may take such action as they deem appropriate, consistent with their respective statutory authorities and responsibilities. </P>
                                    <P>(e) The Secretary and the Director fully expect their staffs to work closely together on the matters specified in this section, before such matters are submitted for official OPM coordination or approval and DoD decision, so as to maximize the opportunity for consensus and agreement before an issue is so submitted. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.106 </SECTNO>
                                    <SUBJECT>Relationship to other provisions. </SUBJECT>
                                    <P>(a)(1) The provisions of title 5, U.S. Code, are waived, modified, or replaced to the extent authorized by 5 U.S.C. 9902 to conform to the provisions of this part. </P>
                                    <P>(2) This part must be interpreted in a way that recognizes the critical national security mission of the Department, and each provision of this part must be construed to promote the swift, flexible, effective day-to-day accomplishment of this mission, as defined by the Secretary. </P>
                                    <P>(b)(1) For the purpose of applying other provisions of law or Governmentwide regulations that reference provisions under chapters 43, 51, 53, and 55 (subchapter V only), of title 5, U.S. Code, the referenced provisions are not waived but are modified consistent with the corresponding regulations in this part, except as otherwise provided in this part (including paragraph (c) of this section) or in implementing issuances. </P>
                                    <P>(2) If another provision of law or Governmentwide regulations require coverage under one of the chapters modified or waived under this part (i.e., chapters 43, 51, 53, and 55 (subchapter V only) of title 5, U.S. Code), DoD employees are deemed to be covered by the applicable chapter notwithstanding coverage under a system established under this part. Selected examples of provisions that continue to apply to any DoD employees (notwithstanding coverage under subparts B through D of this part) include, but are not limited to, the following: </P>
                                    <P>(i) Foreign language awards for law enforcement officers under 5 U.S.C. 4521 through 4523; </P>
                                    <P>(ii) Pay for firefighters under 5 U.S.C. 5545b; and </P>
                                    <P>(iii) Recruitment, relocation, and retention payments under 5 U.S.C. 5753 through 5754. </P>
                                    <P>(c)(1) Law enforcement officer special base rates under section 403 of the Federal Employees Pay Comparability Act of 1990 (section 529 of Pub. L. 101-509) do not apply to employees who are covered by an NSPS classification and pay system established under subparts B and C of this part. </P>
                                    <P>(2) Physicians' comparability allowances under 5 U.S.C. 5948 do not apply to employees covered by an NSPS classification and pay system established under subparts B and C of this part. </P>
                                    <P>
                                        (d) Nothing in this part waives, modifies or otherwise affects the employment discrimination laws that the Equal Employment Opportunity Commission (EEOC) enforces under 42 U.S.C. 2000e 
                                        <E T="03">et seq.</E>
                                        , 29 U.S.C. 621 
                                        <E T="03">et seq.</E>
                                        , 29 U.S.C. 791 
                                        <E T="03">et seq.</E>
                                        , and 29 U.S.C. 206(d). 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.107 </SECTNO>
                                    <SUBJECT>Program evaluation. </SUBJECT>
                                    <P>The Secretary will evaluate the regulations in this part and their implementation. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—Classification </HD>
                                <HD SOURCE="HD1">General </HD>
                                <SECTION>
                                    <SECTNO>§ 9901.201 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <P>(a) This subpart establishes a classification structure and rules for covered DoD employees and positions to replace the classification structure and rules in 5 U.S.C. chapter 51, in accordance with the merit system principle that equal pay should be provided for work of equal value, with appropriate consideration of both national and local rates paid by employers in the private sector, and with appropriate incentives and recognition provided for excellence in performance. </P>
                                    <P>(b) The basis for determining the appropriate classification under NSPS is the primary duties and responsibilities of the position, level of difficulty, occupational qualifications, competency requirements, mission of the organization, and relationship of the position to other positions or organizational levels. </P>
                                    <P>(c) Any classification system prescribed under this subpart will be established in conjunction with the pay system described in subpart C of this part. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.202 </SECTNO>
                                    <SUBJECT>Coverage. </SUBJECT>
                                    <P>(a) This subpart applies to eligible DoD employees and positions listed in paragraph (b) of this section, subject to a determination by the Secretary under § 9901.102(b) or (f). </P>
                                    <P>(b) The following employees of, or positions in, DoD organizational and functional units are eligible for coverage under this subpart: </P>
                                    <P>(1) Employees and positions that would otherwise be covered by the General Schedule classification system established under 5 U.S.C. chapter 51; </P>
                                    <P>(2) Employees in senior-level (SL) and scientific or professional (ST) positions who would otherwise be covered by 5 U.S.C. 5376; </P>
                                    <P>(3) Members of the Senior Executive Service (SES) who would otherwise be covered by 5 U.S.C. chapter 53, subchapter VIII, subject to § 9901.102(d); and </P>
                                    <P>(4) Such others designated by the Secretary as DoD may be authorized to include under 5 U.S.C. 9902. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.203 </SECTNO>
                                    <SUBJECT>Waivers. </SUBJECT>
                                    <P>(a) When a specified category of employees is covered by a classification system established under this subpart, the provisions of 5 U.S.C. chapter 51 are waived with respect to that category of employees, except as provided in paragraph (b) of this section, §§ 9901.106, and 9901.222(d) (with respect to OPM's authority to act on requests for classification decisions under 5 U.S.C. 5112(b) and review of pay plans under 5 U.S.C. 5103). </P>
                                    <P>(b) Section 5108 of title 5, U.S. Code, dealing with the classification of positions above GS-15, is not waived for the purpose of defining and allocating Senior Executive Service (SES) positions under 5 U.S.C. 3132 and 3133 or applying provisions of law outside the waivable and modifiable chapters of title 5, U.S. Code—e.g., 5 U.S.C. 4507 and 4507a (regarding Presidential rank awards), 5 U.S.C. 6303(f) (regarding annual leave accrual for members of the SES and employees in SL/ST positions), and 5 U.S.C. 6304(f) (regarding annual leave ceilings for members of the SES and employees in SL/ST positions). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.204 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>
                                        In this subpart: 
                                        <PRTPAGE P="56394"/>
                                    </P>
                                    <P>
                                        <E T="03">Band</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Basic pay</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Career group</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Classification,</E>
                                         also referred to as job evaluation, means the process of analyzing and assigning a job or position to an occupational series, official title, career group, pay schedule, and pay band for pay and other related purposes. 
                                    </P>
                                    <P>
                                        <E T="03">Competencies</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Occupational series</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Official title</E>
                                         means the position title prescribed in an NSPS classification standard or by supplemental Component guidance. 
                                    </P>
                                    <P>
                                        <E T="03">Pay band</E>
                                         or 
                                        <E T="03">band</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Pay schedule</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Position</E>
                                         or 
                                        <E T="03">job</E>
                                         means the duties, responsibilities, and related competency requirements that are assigned to an employee. 
                                    </P>
                                    <HD SOURCE="HD1">Classification Structure </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.211 </SECTNO>
                                    <SUBJECT>Career groups. </SUBJECT>
                                    <P>For the purpose of classifying positions, the Secretary may establish career groups based on factors such as mission or function; nature of work; qualifications or competencies; career or pay progression patterns; relevant labor-market features; and other characteristics of those occupations or positions. The Secretary will document in implementing issuances the criteria and rationale for grouping occupations or positions into career groups. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.212 </SECTNO>
                                    <SUBJECT>Pay schedules and pay bands. </SUBJECT>
                                    <P>(a) For purposes of identifying relative levels of work and corresponding pay ranges, the Secretary may establish one or more pay schedules within each career group. </P>
                                    <P>(b) Each pay schedule may include one or more pay bands. </P>
                                    <P>(c) The Secretary will document in implementing issuances the definitions for each pay band which specify the type and range of difficulty and responsibility, qualifications or competencies, or other characteristics of the work encompassed by the pay band. </P>
                                    <P>(d) The Secretary will—</P>
                                    <P>(1) Use qualification standards established or approved by OPM, or establish qualification standards for positions covered by NSPS, subject to § 9901.105(b)(2); and </P>
                                    <P>(2) Designate qualification standards and requirements for each career group, occupational series, pay schedule, and/or pay band. </P>
                                    <HD SOURCE="HD1">Classification Process </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.221 </SECTNO>
                                    <SUBJECT>Classification requirements. </SUBJECT>
                                    <P>(a) The Secretary will develop a methodology for describing and documenting the duties, qualifications, and other requirements of categories of jobs, and will make such descriptions and documentation available to affected employees. </P>
                                    <P>(b) The Secretary will—</P>
                                    <P>(1) Assign occupational series to jobs consistent with occupational series definitions established by OPM under 5 U.S.C. 5105, or by DoD; and </P>
                                    <P>(2) Apply the criteria and definitions required by §§ 9901.211 and 9901.212 to assign jobs to an appropriate career group, pay schedule, and pay band. </P>
                                    <P>(c) The Secretary will establish procedures for classifying jobs and may make such inquiries of the duties, responsibilities, and qualification requirements of jobs as he or she considers necessary for the purpose of this section. </P>
                                    <P>(d) A classification action is implemented by a personnel action, which, for encumbered positions, must be taken within a reasonable period of time following the effective date of the position classification action. For classification actions resulting from a DoD appeal decision, the personnel action must occur within four pay periods following the effective date of the decision, except when a subsequent date is specifically provided in the decision. If a classification action results in a reduction in an employee's pay band or adjusted salary, the employee must be advised, in writing, of the action and proposed effective date of the personnel action at least 7 days before the personnel action is taken. The written notice will inform the employee of the reason for the reclassification, the right to appeal the classification decision, and the time limitations in § 9901.223 within which the appeal must be filed to preserve applicable retroactive benefits. </P>
                                    <P>(e) Except as otherwise provided in this paragraph or required by law, the effective date of a classification action is the date the authorized management official certifies the classification decision (i.e., signs or electronically validates the position description). </P>
                                    <P>(1) A retroactive effective date for a classification action and the implementing personnel action is permitted only if the action resulted in a reduction in pay band or adjusted salary and if that action is subsequently reversed on appeal. </P>
                                    <P>(2) In order for a corrective action to be retroactive, the employee must file an initial request for review of the classification action with DoD or OPM not later than 15 calendar days after the personnel action effective date for the reduction in pay band or adjusted salary. </P>
                                    <P>(3) A retroactive date may be established only if the appeal reversal is based on the duties and responsibilities performed at the time of reduction. Retroactive action is mandatory under these circumstances. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.222 </SECTNO>
                                    <SUBJECT>Review of classification decisions. </SUBJECT>
                                    <P>(a) An individual employee may request that DoD or OPM review the classification (i.e., pay system, career group, occupational series, official title, pay schedule, or pay band) of his or her official position of record at any time. </P>
                                    <P>(b) Under this section, an employee may not appeal to either DoD or OPM the issues designated as nonappealable to the Office of Personnel Management in 5 CFR 511.607 or the accuracy of NSPS pay schedule and pay band classification criteria. Additional nonappealable issues covered under NSPS include—</P>
                                    <P>(1) Classification of a proposed position or one to which the employee is not officially assigned; </P>
                                    <P>(2) Classification of a position to which an employee is detailed, temporarily reassigned, or temporarily promoted, except for employees serving under a time-limited promotion or reassignment for 2 years or more; </P>
                                    <P>(3) Accuracy of the official position description, including the inclusion or exclusion of a duty (subject to paragraph (c) of this section); </P>
                                    <P>(4) Classification of a position based on position-to-position comparisons rather than the NSPS classification criteria; </P>
                                    <P>(5) Classification of a position for which a DoD or an OPM appeal decision was previously rendered unless there is a later change in the governing classification criteria or a material change in the requirements of the position; and </P>
                                    <P>(6) The accuracy of career group, pay band, or pay schedule classification criteria or standards contained in DoD issuances. </P>
                                    <P>
                                        (c) When the accuracy of the official position description is questioned by the employee, the employee will be advised to raise this issue informally with the employee's supervisor or file a grievance using the applicable administrative or negotiated grievance procedure. If the employee elects to first raise this issue with the employee's 
                                        <PRTPAGE P="56395"/>
                                        supervisor and the employee and the supervisor cannot resolve this issue, the accuracy of the position description may be determined using the applicable administrative or negotiated grievance procedure. If, after completing this procedure, the issue is not resolved, the classification appeal, if any, will be decided on the basis of the actual duties and responsibilities assigned by management and performed by the employee. 
                                    </P>
                                    <P>(d) An employee may request that OPM review a DoD determination made under paragraph (a) of this section. If an employee does not request an OPM review, DoD's classification determination is final and not subject to further review or appeal. </P>
                                    <P>(e) Any determination made under this section will be based on criteria issued by the Secretary. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.223 </SECTNO>
                                    <SUBJECT>Appeal to DoD for review of classification decisions. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Employee representation.</E>
                                         An employee may designate in writing a representative of his or her choice to assist in the preparation and presentation of an appeal. A management official may disallow an employee's representative when—
                                    </P>
                                    <P>(1) An individual's activities as a representative would cause a conflict of interest or position; </P>
                                    <P>(2) An employee cannot be released from his or her official duties because of the priority needs of the Government; or </P>
                                    <P>(3) An employee's release would give rise to unreasonable costs to the Government. </P>
                                    <P>
                                        (b) 
                                        <E T="03">DoD classification appeal process.</E>
                                         (1) Employee appeals to DoD must be submitted through the employee's servicing Human Resources Office. 
                                    </P>
                                    <P>(2) An employee may file a classification appeal at any time. When the issue involves a classification action that resulted in a reduction in band or adjusted salary, to preserve any entitlement to retroactive pay, the employee must file any DoD classification appeal no later than 15 calendar days after the effective date of the personnel action. When an employee shows that he or she did not receive notice of the applicable time limit, or personnel action, or was prevented from timely filing by circumstances beyond the employee's control, the deciding official may grant an extension of the appeal period. </P>
                                    <P>(3) An employee must provide the following documentation when filing an appeal: </P>
                                    <P>(i) The employee's name, mailing address, and office telephone and fax numbers; </P>
                                    <P>(ii) The employing Component and the exact location of the employee's position within the Component (installation name, mailing address, organization, division, branch, section, unit); </P>
                                    <P>(iii) The name, address, and business telephone and fax numbers of the employee's representative, if any; </P>
                                    <P>(iv) A statement of the employee's requested pay system, official position title, occupational series, pay schedule, and/or pay band; and </P>
                                    <P>(v) Reasons why the employee believes the position is incorrectly classified. </P>
                                    <P>(4) The employee must refer to classification standards that support the appeal and state specific points of disagreement with the current classification. The employee may also include a statement of facts that he or she thinks may affect the final classification decision. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Binding decisions.</E>
                                         DoD appeal decisions constitute certificates that are binding on all administrative, certifying, payroll, disbursing, and accounting offices within DoD. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Cancellation.</E>
                                         (1) An employee or representative may cancel an appeal at any time before DoD issues a decision by providing written notification to the DoD deciding official. 
                                    </P>
                                    <P>(2) DoD may cancel an appeal if any of the following occur: </P>
                                    <P>(i) The employee, or his or her representative, does not furnish requested information within the required time period; </P>
                                    <P>(ii) The employee is no longer officially assigned to, or is removed from, the position and there is no entitlement to retroactive benefits; </P>
                                    <P>(iii) The duties and responsibilities of the position are significantly changed while the case is pending and there is no entitlement to retroactive benefits; or </P>
                                    <P>(iv) The position is abolished and there is no entitlement to retroactive benefits. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.224 </SECTNO>
                                    <SUBJECT>Appeal to OPM for review of classification decisions. </SUBJECT>
                                    <P>(a) An employee's request for OPM review of DoD classification determination will follow the procedures in 5 CFR part 511, subpart F—Classification Appeals. </P>
                                    <P>(b) Effective dates of OPM classification appeal decisions will be consistent with 5 CFR 511.702. </P>
                                    <P>(c) Employee appeals to OPM may be submitted directly to OPM. </P>
                                    <P>(d) OPM's final determination on an appeal made under this section is not subject to further review or appeal. </P>
                                    <HD SOURCE="HD1">Transitional Provisions </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.231 </SECTNO>
                                    <SUBJECT>Conversion of positions and employees to NSPS classification system. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Introduction.</E>
                                         This section describes the transitional provisions that apply when DoD positions and employees initially are converted to a classification system established under this subpart. (See § 9901.371 for conversion rules related to setting an employee's pay.) Positions and employees in affected organizational or functional units may convert from the GS system, the SL/ST system, the SES system, or such other DoD systems as may be designated by the Secretary, as provided in § 9901.202. For the purpose of this part, the terms “convert,” “converted,” “converting,” and “conversion” refer to positions and employees that become covered by the NSPS classification system as a result of a coverage determination made under § 9901.102(b) and excludes employees who move from a noncovered position to a position already covered by NSPS. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Implementing issuances.</E>
                                         The Secretary will issue implementing issuances prescribing policies and procedures for converting DoD employees to a pay band upon initial implementation of the NSPS classification system. Those issuances will establish the work level conversion tables used to place an employee in a pay band based on the level of work of the employee's position in the formerly applicable pay system. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Temporary promotion prior to conversion.</E>
                                         An employee on a temporary promotion at the time of conversion will be returned to his or her official position of record prior to processing the conversion. That official position of record (including occupational series and grade) is used in determining the employee's career group, pay schedule, and band upon conversion. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Grade retention prior to conversion.</E>
                                         For an employee who is entitled to grade retention immediately before conversion, the grade of the actual position of record (not the grade being retained) is used in determining the employee's band upon conversion. 
                                    </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart C—Pay and Pay Administration </HD>
                                <HD SOURCE="HD1">General </HD>
                                <SECTION>
                                    <SECTNO>§ 9901.301 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <P>
                                        (a) This subpart contains regulations establishing pay structures and pay administration rules for covered DoD employees to replace the pay structures and pay administration rules established under 5 U.S.C. chapter 53 
                                        <PRTPAGE P="56396"/>
                                        and 5 U.S.C. chapter 55, subchapter V, as authorized by 5 U.S.C. 9902 (subject to the limitations on waivers in § 9901.303). Various features that link pay to employees' performance ratings are designed to promote a high-performance culture within DoD. 
                                    </P>
                                    <P>(b) Any pay system prescribed under this subpart will be established in conjunction with the classification system described in subpart B of this part. </P>
                                    <P>(c) Any pay system prescribed under this subpart will be established in conjunction with the performance management system described in subpart D of this part. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.302 </SECTNO>
                                    <SUBJECT>Coverage. </SUBJECT>
                                    <P>(a) This subpart applies to eligible DoD employees and positions in the categories listed in paragraph (b) of this section, subject to a determination by the Secretary under § 9901.102(b) or (f). </P>
                                    <P>(b) The following employees of, or positions in, DoD organizational and functional units are eligible for coverage under this subpart: </P>
                                    <P>(1) Employees and positions who would otherwise be covered by the General Schedule pay system established under 5 U.S.C. chapter 53, subchapter III; </P>
                                    <P>(2) Employees in senior-level (SL) and scientific or professional (ST) positions who would otherwise be covered by 5 U.S.C. 5376; </P>
                                    <P>(3) Members of the Senior Executive Service (SES) who would otherwise be covered by 5 U.S.C. chapter 53, subchapter VIII, subject to § 9901.102(d); and </P>
                                    <P>(4) Such others designated by the Secretary as DoD may be authorized to include under 5 U.S.C. 9902. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.303 </SECTNO>
                                    <SUBJECT>Waivers. </SUBJECT>
                                    <P>(a) When a specified category of employees is covered under this subpart—</P>
                                    <P>(1) The provisions of 5 U.S.C. chapter 53 are waived with respect to that category of employees, except as provided in § 9901.106 and paragraphs (b) and (c) of this section; and </P>
                                    <P>(2) The provisions of 5 U.S.C. chapter 55, subchapter V (except sections 5544 and 5545b), are waived with respect to that category of employees to the extent that those employees are covered by alternative premium pay provisions established by the Secretary under §§ 9901.361 through 9901.364 in lieu of the provisions in 5 U.S.C. chapter 55, subchapter V. </P>
                                    <P>(b) The following provisions of 5 U.S.C. chapter 53 are not waived: </P>
                                    <P>(1) Sections 5311 through 5318, dealing with Executive Schedule positions; </P>
                                    <P>(2) Sections 5341 through 5349, dealing with prevailing rate systems; </P>
                                    <P>(3) Section 5371, insofar as it authorizes OPM to apply the provisions of 38 U.S.C. chapter 74 to DoD employees in health care positions covered by section 5371 in lieu of any NSPS classification and pay system established under this part or the following provisions of title 5, U.S. Code: chapters 51, 53, and 61, and subchapter V of chapter 55. The reference to “chapter 51” in section 5371(c) is deemed to include a classification system established under subpart B of this part; and </P>
                                    <P>(4) Section 5377, dealing with the critical pay authority. </P>
                                    <P>(c) Section 5379 continues to apply but is modified to allow the Secretary to modify the minimum service period and the limitations on the amount of student loan benefits in order to address critical hiring needs, subject to § 9901.105. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.304 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>In this subpart:</P>
                                    <P>
                                        <E T="03">Adjusted salary</E>
                                         means an NSPS employee's base salary plus any local market supplement paid to that employee. For an employee moving into NSPS from a non-NSPS position, 
                                        <E T="03">adjusted salary</E>
                                         also refers to non-NSPS base salary plus any applicable locality pay under 5 U.S.C. 5304, special rate supplement under 5 U.S.C. 5305, or any equivalent supplement. 
                                    </P>
                                    <P>
                                        <E T="03">Band</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Base salary</E>
                                         means an NSPS employee's pay, as set by the authorized management official, before deductions and exclusive of additional pay of any kind (e.g., local market supplement). For an employee moving into NSPS from a non-NSPS position, 
                                        <E T="03">base salary</E>
                                         also refers to non-NSPS pay, before deductions and exclusive of additional pay of any kind (e.g., locality pay or a special rate supplement). 
                                    </P>
                                    <P>
                                        <E T="03">Basic pay</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Bonus</E>
                                         means an element of the performance payout that consists of a one-time lump-sum payment made to employees. It is not part of basic pay for any purpose. 
                                    </P>
                                    <P>
                                        <E T="03">Career group</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Comparable pay band</E>
                                         or 
                                        <E T="03">comparable level of work</E>
                                         has the meaning given in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Competencies</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Component</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Contributing factor</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Contribution</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Contribution assessment</E>
                                         means the determination made by the Pay Pool Manager as to the impact, extent, and scope of contribution that the employee's performance made to the accomplishment of the organization's mission and goals. 
                                    </P>
                                    <P>
                                        <E T="03">CONUS</E>
                                         or 
                                        <E T="03">Continental United States</E>
                                         means the States of the United States, excluding Alaska and Hawaii, but including the District of Columbia. 
                                    </P>
                                    <P>
                                        <E T="03">Day</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Department</E>
                                         or 
                                        <E T="03">DoD</E>
                                         has the meaning given in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Employee</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">General Schedule</E>
                                         or 
                                        <E T="03">GS</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Implementing issuance(s)</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Local market supplement</E>
                                         means a geographic- and occupation-based supplement paid in addition to an employee's base salary, including a standard local market supplement or a targeted local market supplement, as described in § 9901.332. 
                                    </P>
                                    <P>
                                        <E T="03">Modal rating</E>
                                         means, for the purpose of pay administration, the most frequent rating of record assigned to employees within a particular pay pool for a particular rating cycle. 
                                    </P>
                                    <P>
                                        <E T="03">National Security Personnel System (NSPS)</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Occupational series</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">OPM</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Official worksite</E>
                                         has the meaning given that term in 5 CFR 531.605. 
                                    </P>
                                    <P>
                                        <E T="03">Pay band</E>
                                         or 
                                        <E T="03">band</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Pay pool</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Pay Pool Manager</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Pay Pool Panel</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Pay schedule</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Performance</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Performance payout</E>
                                         means the total monetary value of a performance pay increase and bonus provided under § 9901.342. 
                                    </P>
                                    <P>
                                        <E T="03">Performance Review Authority</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Performance share</E>
                                         means a unit of performance payout awarded to an employee based on performance. Performance shares may be awarded in multiples based on the employee's rating of record and specified factors, as provided in § 9901.342(f). 
                                    </P>
                                    <P>
                                        <E T="03">Performance share value</E>
                                         means a calculated value for each performance 
                                        <PRTPAGE P="56397"/>
                                        share based on pay pool funds available and the distribution of performance shares across employees within a pay pool, expressed as a percentage of base salary. 
                                    </P>
                                    <P>
                                        <E T="03">Premium pay</E>
                                         means payments for work performed under special conditions or circumstances, as authorized under 5 U.S.C. chapter 55, subchapter V, or §§ 9901.361 through 9901.364 (including compensatory time off). 
                                    </P>
                                    <P>
                                        <E T="03">Promotion</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Rate range</E>
                                         means the range of base salary rates applicable to employees in a particular pay band, as described in § 9901.321. Each rate range is defined by a minimum and maximum base salary rate. 
                                    </P>
                                    <P>
                                        <E T="03">Rating of record</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Reassignment</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Reduction in band</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Retained rate</E>
                                         means a retained base salary rate (i.e., excluding any local market supplement) above the applicable pay band maximum rate as established for an NSPS employee under the pay retention provisions in § 9901.356. For GS employees, 
                                        <E T="03">retained rate</E>
                                         has the meaning given that term in 5 CFR part 536. 
                                    </P>
                                    <P>
                                        <E T="03">Secretary</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Standard local market supplement</E>
                                         means the local market supplement that applies to employees in a given pay schedule or band who are stationed within a specified local market area (the boundaries of which are defined under § 9901.332(b)), unless a targeted local market supplement applies. Standard local market supplements are generally administered for covered employees in the same manner as locality-based comparability payments under 5 U.S.C. 5304 and 5304a. 
                                    </P>
                                    <P>
                                        <E T="03">Sub pay pool</E>
                                         means a subset of a pay pool that is defined for the purpose of reconciling ratings of record, share assignments, and payout determinations. 
                                    </P>
                                    <P>
                                        <E T="03">Targeted local market supplement</E>
                                         means a local market supplement established to address recruitment or retention difficulties or for other appropriate reasons and which applies to a defined category of employees (based on occupation or other appropriate factors) in lieu of any lower standard local market supplement that would otherwise apply. 
                                    </P>
                                    <P>
                                        <E T="03">Unacceptable performance</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.305 </SECTNO>
                                    <SUBJECT>Rate of pay. </SUBJECT>
                                    <P>(a) The term “rate of pay” in 5 U.S.C. 9902(e)(9) means—</P>
                                    <P>(1) An individual employee's base salary rate, local market supplement rate, and overtime and other premium pay rates (including compensatory time off); and </P>
                                    <P>(2) The rates comprising the structure of the pay system that govern the setting and adjusting of the individual employee rates identified in paragraph (a)(1) of this section, including, but not limited to—</P>
                                    <P>(i) Band rate range minimum and maximum rates; </P>
                                    <P>(ii) Control points within a band rate range; </P>
                                    <P>(iii) Local market supplement rates; </P>
                                    <P>(iv) Maximum rates of base salary and adjusted salary; </P>
                                    <P>(v) Premium pay rates; and </P>
                                    <P>(vi) The percentage rate of total base salary payroll constituting the portion of a pay pool applied to provide performance-based increases in employees' base salary rates. </P>
                                    <P>(b) For the purpose of 5 U.S.C. 9902(e)(9), the establishment or adjustment of a rate of pay includes the establishment or adjustment of the amount or level of the rate and of the eligibility requirements associated with the type and level of pay in question. Illustrative examples of actions that establish or adjust a rate of pay include, but are not limited to, the following: </P>
                                    <P>(1) Establishing the starting base salary rate for a newly hired employee; </P>
                                    <P>(2) Establishing a retained rate for an employee under § 9901.356(e); </P>
                                    <P>(3) Adjusting an employee's base salary rate through various pay actions, including general salary increases, targeted general salary increases, performance pay increases, extraordinary performance recognition increases, organizational or team achievement recognition increases, pay reductions for unacceptable performance or conduct, reassignment increases and decreases, promotion increases, within-grade increase adjustments, and accelerated compensation for developmental positions (ACDP) increases; </P>
                                    <P>(4) Establishing or adjusting the minimum or maximum rate of a band rate range or control points within that range; </P>
                                    <P>(5) Establishing or adjusting the percentage amount of a targeted local market supplement, as well as the geographic area and other coverage requirements associated with that supplement; </P>
                                    <P>(6) Establishing a higher premium pay limit under § 9901.362(a)(2); </P>
                                    <P>(7) Establishing an overtime rate equal to an employee's adjusted salary rate under § 9901.362(b)(6)(i); </P>
                                    <P>(8) Establishing a new hazardous duty premium rate under 9901.362(i)(3); and </P>
                                    <P>(9) Establishing the percentage rate of total base salary payroll constituting the portion of a pay pool applied to provide performance-based increases in employees' base salary rates. </P>
                                    <HD SOURCE="HD1">Overview of Pay System </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.311 </SECTNO>
                                    <SUBJECT>Major features. </SUBJECT>
                                    <P>Through the issuance of implementing issuances, the Secretary will further define a pay system that governs the setting and adjusting of covered employees' rates of base salary and adjusted salary and the setting of covered employees' rates of premium pay. The NSPS pay system will include the following features: </P>
                                    <P>(a) A structure of rate ranges linked to various pay bands for each career group, in alignment with the classification structure described in subpart B of this part; </P>
                                    <P>(b) Policies regarding the setting and adjusting of band rate ranges based on mission requirements, labor market conditions, and other factors, as described in §§ 9901.321 and 9901.322; </P>
                                    <P>(c) Policies regarding the setting and adjusting of local market supplements as described in §§ 9901.331 through 9901.333; </P>
                                    <P>(d) Policies regarding employees' eligibility for general salary increases and adjustments in local market supplements, as described in §§ 9901.323 and 9901.334; </P>
                                    <P>(e) Policies regarding performance-based pay, as described in §§ 9901.341 through 9901.345; </P>
                                    <P>(f) Policies on base salary administration, including movement between career groups, positions, pay schedules, and pay bands, as described in §§ 9901.351 through 9901.356; </P>
                                    <P>(g) Linkages to employees' ratings of record, as described in subpart D of this part; and </P>
                                    <P>(h) Policies regarding the setting of and limitations on premium payments, as described in §§ 9901.361 through 9901.364. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.312 </SECTNO>
                                    <SUBJECT>Maximum rates of base salary and adjusted salary. </SUBJECT>
                                    <P>(a) Subject to § 9901.105, the Secretary may establish a limitation on the maximum rate of base salary provided under authority of this subpart. </P>
                                    <P>
                                        (b) No employee may receive, under authority of this subpart, an adjusted salary rate greater than the rate for level IV of the Executive Schedule plus 5 percent. The payable local market 
                                        <PRTPAGE P="56398"/>
                                        supplement for an employee must be reduced as necessary to comply with this limitation. 
                                    </P>
                                    <P>(c) Paragraphs (a) and (b) of this section do not apply to physicians and dentists (in occupational series 0602 and 0680, respectively). </P>
                                    <P>(d) Subject to § 9901.105, the Secretary may establish a higher adjusted salary rate limitation for a specified category of positions in lieu of the limitation in paragraph (b) of this section based on mission requirements, labor market conditions, availability of funds, and any other relevant factors. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.313 </SECTNO>
                                    <SUBJECT>Aggregate compensation limitations. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         (1) Except as provided in paragraphs (a)(2) and (a)(3) of this section, no additional payment (premium pay, allowance, differential, bonus, award, or other similar cash payment) may be paid to an employee in a calendar year if, or to the extent that, when added to the adjusted salary paid to the employee for service performed as an employee in the Department or in another Federal agency, the payment would cause the total aggregate compensation to exceed the annual rate for Executive Level I as in effect on the last day of that calendar year. 
                                    </P>
                                    <P>(2) In the case of physicians and dentists (in occupational series 0602 and 0680, respectively) payment to the employee may not cause aggregate compensation received in a calendar year to exceed the salary of the President of the United States as in effect on the last day of that calendar year. </P>
                                    <P>(3) Subject to § 9901.105, the Secretary may provide for a higher aggregate compensation limitation equal to the annual rate payable to the Vice President under 3 U.S.C. 104 as in effect on the last day of the calendar year in the case of specified categories of employees for whom a waiver has been authorized under § 9901.362(a)(2). </P>
                                    <P>(4) The limitation described in this paragraph (a) applies to the total amount of aggregate compensation actually received by an employee during the calendar year without regard to the period of service for which such compensation is earned. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Types of compensation.</E>
                                         For the purpose of this section, aggregate compensation is the total of—
                                    </P>
                                    <P>(1) Adjusted salary received as an employee of the Department; </P>
                                    <P>(2) Premium pay under 5 U.S.C. chapter 55, subchapter V, and this subpart; </P>
                                    <P>(3) Incentive awards and performance-based cash awards under 5 U.S.C. 4501-4523 and this part; </P>
                                    <P>(4) Recruitment and relocation incentives under 5 U.S.C. 5753; </P>
                                    <P>(5) Retention incentives under 5 U.S.C. 5754; </P>
                                    <P>(6) Supervisory differentials under 5 U.S.C. 5755; </P>
                                    <P>(7) Post differentials under 5 U.S.C. 5925; </P>
                                    <P>(8) Danger pay allowances under 5 U.S.C. 5928; </P>
                                    <P>(9) Extended assignment incentives under 5 U.S.C. 5757; </P>
                                    <P>(10) Post differentials based on environmental conditions for employees stationed outside the continental United States or in Alaska under 5 U.S.C. 5941(a)(2); </P>
                                    <P>(11) Foreign language proficiency pay under 10 U.S.C. 1596 and 1596a; </P>
                                    <P>(12) Continuation of pay under 5 U.S.C. 8118; </P>
                                    <P>(13) Other similar payments authorized under title 5, United States Code, excluding—</P>
                                    <P>(i) Back pay due to an unjustified personnel action under 5 U.S.C. 5596 (but only if the back payments were originally payable in a previous calendar year); </P>
                                    <P>(ii) Overtime pay under the Fair Labor Standards Act of 1938, as amended (29 U.S.C. 201-219 and 5 CFR part 551); </P>
                                    <P>(iii) Severance pay under 5 U.S.C. 5595; </P>
                                    <P>(iv) Nonforeign area cost-of-living allowances under 5 U.S.C. 5941(a)(1); and </P>
                                    <P>(v) Lump-sum payments for accumulated and accrued annual leave on separation under 5 U.S.C. 5551 or 5552; and </P>
                                    <P>(14) Payments received from another agency during the calendar year, prior to employment with the Department, that are subject to 5 U.S.C. 5307. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Administration of aggregate limitation.</E>
                                         (1) At the time a payment covered by paragraph (b) of this section (other than adjusted salary) is authorized for an employee, the employee may not receive any portion of such payment that, when added to the estimated aggregate compensation the employee is projected to receive, would cause the aggregate compensation actually received by the employee during the calendar year to exceed the limitation applicable to the employee under this section at the end of the calendar year. 
                                    </P>
                                    <P>(2) Payments that are creditable for retirement purposes (e.g., law enforcement availability pay (LEAP) or standby premium pay) and that are paid to an employee at a regular fixed rate each pay period may not be deferred or discontinued for any period of time in order to make another payment that would otherwise cause an employee's pay to exceed any limitation described in or established by this section. </P>
                                    <P>(3) Except for physicians and dentists (in occupational series 0602 and 0680, respectively), if the estimated aggregate compensation to which an employee is entitled exceeds the applicable limitation under this section for the calendar year, the Department must defer all authorized payments (other than adjusted salary) at the time when otherwise continuing such payments would cause the aggregate compensation actually received by any employee during the calendar year to exceed the applicable limitation. Any portion of a payment deferred under this paragraph will become available for payment as provided in paragraph (d) of this section. For physicians and dentists (in occupational series 0602 and 0680, respectively), payments that exceed the limitation under paragraph (a)(2) of this section may not be made at any time. </P>
                                    <P>(4) If the Department makes an incorrect estimate of aggregate compensation at an earlier date in the calendar year, the sum of an employee's remaining payments of adjusted salary (which may not be deferred) may exceed the difference between the aggregate compensation the employee has actually received to date in that calendar year and the applicable limitation under this section. In this case, the employee will become indebted to the Department for any amount paid in excess of the aggregate limitation. To the extent that the excess amount is attributable to amounts that should have been deferred and would have been payable at the beginning of the next calendar year, the debt must be nullified on January 1 of the next calendar year. As part of the correction of the error, the excess amount will be deemed to have been paid on January 1 of the next calendar year (when the debt was extinguished) as if it were a deferred excess payment as described in paragraph (c)(3) of this section and must be considered part of the employee's aggregate compensation for the new calendar year. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Payment of excess amounts.</E>
                                         (1) Except for physicians and dentists (in occupational series 0602 and 0680, respectively), any amount that is not paid to an employee because of the annual aggregate compensation limitation under this section must be paid in a lump-sum payment at the beginning of the following calendar year. Any amount paid the following calendar year will be taken into account for purposes of applying the limitations with respect to such calendar year. For 
                                        <PRTPAGE P="56399"/>
                                        physicians and dentists (in occupational series 0602 and 0680, respectively), payments that exceed the limitation under paragraph (a)(2) of this section may not be made at any time. 
                                    </P>
                                    <P>(2) If a lump-sum payment causes an employee's estimated aggregate compensation to exceed the applicable limitation under this section, the Department must consider only the employee's adjusted salary and payments that are creditable for retirement purposes (e.g., LEAP or standby pay) in determining the extent to which the lump-sum payment may be paid and will defer all other payments, in order to pay as much of the excess amount as possible. Any payments deferred under this paragraph, including any portion of the excess amount that was not payable, will become payable at the beginning of the next calendar year. </P>
                                    <P>(3) If an employee moves to another Federal agency or to another position within the Department not covered by NSPS, and, at the time of the move, the employee has received payments in excess of the aggregate limitation under 5 U.S.C. 5307, the employee's indebtedness for the excess amount received will be deferred from the effective date of the transfer until the beginning of the next calendar year. Effective January 1 of the new calendar year, the debt will be nullified and the excess amount will be considered in applying that year's aggregate limitation. </P>
                                    <P>(4) If an employee transfers to another agency and, at the time of transfer, the employee has excess payments deferred to the next calendar year, the provisions of 5 U.S.C. 5307 are applicable. </P>
                                    <P>(5) The following conditions permit payment of excess aggregate compensation without regard to the calendar year limitation: </P>
                                    <P>(i) If an employee dies, the excess amount is payable immediately as part of the settlement of accounts, in accordance with 5 U.S.C. 5582. </P>
                                    <P>(ii) If an employee separates from Federal service, the entire excess amount is payable following a 30-day break in service. If the individual is reemployed in the Department under NSPS in the same calendar year as separation, any previous payment of an excess amount will be considered part of that year's aggregate compensation for the purpose of applying the limitations described in this section for the remainder of the calendar year. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.314 </SECTNO>
                                    <SUBJECT>National security compensation comparability. </SUBJECT>
                                    <P>(a) To the maximum extent practicable, for fiscal years 2004 through 2012, the overall amount allocated for compensation of the DoD civilian employees who are included in the NSPS may not be less than the amount that would have been allocated for compensation of such employees for such fiscal years if they had not been converted to the NSPS, based on, at a minimum—</P>
                                    <P>(1) The number and mix of employees in such organizational or functional units prior to conversion of such employees to the NSPS; and </P>
                                    <P>(2) Adjustments for normal step increases and rates of promotion that would have been expected, had such employees remained in their previous pay schedule. </P>
                                    <P>(b) To the maximum extent practicable, implementing issuances will provide a formula for calculating the overall amount to be allocated for fiscal years beyond fiscal year 2012 for compensation of the civilian employees included in the NSPS. The formula will ensure that, in the aggregate, employees are not disadvantaged in terms of the overall amount of compensation available as a result of conversion to the NSPS, while providing flexibility to accommodate changes in the function of the organization and other changed circumstances that might impact compensation levels. </P>
                                    <P>(c) For the purpose of this section, “compensation” for civilian employees means adjusted salary, taking into account any applicable locality payment under 5 U.S.C. 5304, special rate supplement under 5 U.S.C. 5305, local market supplement under § 9901.332, or equivalent supplement under other legal authority. </P>
                                    <HD SOURCE="HD1">Rate Ranges and General Salary Increases </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.321 </SECTNO>
                                    <SUBJECT>Structure. </SUBJECT>
                                    <P>(a) Subject to § 9901.105, the Secretary will establish ranges of base salary rates for pay bands, with minimum and maximum rates set and adjusted as provided in § 9901.322. </P>
                                    <P>(b) For each pay band within a career group, the Secretary will establish a common rate range that applies in all locations. </P>
                                    <P>(c) The Secretary may establish and adjust control points within a pay band to manage compensation (e.g., limitations on pay setting and pay progression within a pay band that apply to specified positions). The Secretary may consider only the following factors in developing control points: mission requirements, labor market conditions, and benchmarks against duties, responsibilities, competencies, qualifications, and performance. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.322 </SECTNO>
                                    <SUBJECT>Setting and adjusting rate ranges. </SUBJECT>
                                    <P>(a) Subject to § 9901.105, the Secretary may set and adjust the rate ranges (i.e., range minimums and maximums) established under § 9901.321. In determining the rate ranges, the Secretary may consider mission requirements, labor market conditions, availability of funds, pay adjustments received by employees of other Federal agencies, and any other relevant factors. </P>
                                    <P>(b) The Secretary may determine the effective date of newly set or adjusted band rate ranges. Established rate ranges will be reviewed for possible adjustment at least annually. </P>
                                    <P>(c) The Secretary may establish different rate ranges and provide different rate range adjustments for different pay bands. </P>
                                    <P>(d) The Secretary may adjust the minimum and maximum rates of a pay band by different percentages. </P>
                                    <P>(e) The maximum rate of each band must be adjusted at the time of a general salary increase under § 9901.323(a)(1) by no less than the percentage amount of the General Schedule annual adjustment under 5 U.S.C. 5303. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.323 </SECTNO>
                                    <SUBJECT>Eligibility for general salary increase. </SUBJECT>
                                    <P>(a) Employees with a current rating of record above “unacceptable” (Level 1) and employees who do not have a current rating of record for the most recently completed appraisal period are eligible to receive an approved general salary increase in their base salary rate subject to the following requirements: </P>
                                    <P>(1) A general salary increase must be provided to eligible employees in all NSPS pay bands at the same time that a General Schedule annual adjustment takes effect under 5 U.S.C. 5303. The amount of such general salary increase is determined by the Secretary but may not be less than 60 percent of the General Schedule annual adjustment under 5 U.S.C. 5303 (unless a lesser percentage is allowed by law). Such general salary increase must be the same percentage amount for all eligible employees under NSPS, except that the increase for employees receiving a retained rate is limited to the lowest permitted amount (i.e., 60 percent of the General Schedule annual adjustment under 5 U.S.C. 5303 unless a lesser percentage is allowed by law). </P>
                                    <P>
                                        (2) In addition to the general salary increase under paragraph (a)(1) of this section, and subject to § 9901.105, a targeted general salary increase may be provided to all eligible employees (excluding employees receiving a retained rate under § 9901.356) in a 
                                        <PRTPAGE P="56400"/>
                                        designated occupational series or specialty in a pay band if the Secretary determines that such an increase is necessary considering only labor market conditions, staffing difficulties, cost, and mission priorities. Different targeted general salary increases may be provided under this paragraph (a)(2) to employees in different occupational series, specialties, and/or pay bands. 
                                    </P>
                                    <P>(b) Employees with a current rating of record of “unacceptable” will not receive a general salary increase under this section. If such an employee receives a rating of record above unacceptable for a subsequent appraisal period, the employee is eligible for any general salary increase taking effect on or after the date the employee is given a rating of record above unacceptable. </P>
                                    <P>(c)(1) The Secretary may provide an additional increase in the base salary rate equal to the difference between the percent of the General Schedule annual adjustment under 5 U.S.C. 5303 and the amount of the NSPS general salary increase under paragraph (a)(1) of this section to employees ineligible for performance payout under § 9901.342. This increase is effective at the same time as the NSPS general salary increase. </P>
                                    <P>(2) The increase under paragraph (c)(1) of this section does not apply to employees who—</P>
                                    <P>(i) Are ineligible for a performance payout due to an NSPS rating of record of Level 1 or Level 2; </P>
                                    <P>(ii) Move from a non-NSPS to an NSPS position, or who are newly hired or reappointed to an NSPS position, on the effective date of the performance payment; or </P>
                                    <P>(iii) Are receiving a retained rate under § 9901.356. </P>
                                    <P>(d) A general salary increase under paragraph (a)(2) or paragraph (c) of this section may be applied only to the extent that it does not cause an employee's base salary rate to exceed the maximum rate of the employee's band or applicable control point. </P>
                                    <P>(e) If the adjustment of a pay band minimum rate causes the base salary of an employee with a rating of record above unacceptable (Level 1) to fall below such minimum rate, the employee's salary will be set at the pay band minimum rate. </P>
                                    <HD SOURCE="HD1">Local Market Supplements </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.331 </SECTNO>
                                    <SUBJECT>General. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Introduction</E>
                                        . The base salary ranges established under §§ 9901.321 through 9901.322 may be supplemented in appropriate circumstances by local market supplements, as described in this section. These supplements are set and adjusted as described in § 9901.333. The sum of an employee's base salary plus any applicable local market supplement constitutes the employee's adjusted salary. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Computation</E>
                                        . Standard local market supplements are computed by multiplying the applicable supplement percentage rate times the employee's base salary rate and rounding the result to the nearest whole dollar. Targeted local market supplements are computed by multiplying the applicable supplement percentage rate times the employee's base salary rate and rounding the result to the nearest whole dollar, or by inclusion of the applicable supplement constant whole dollar amount for eligible employees. A local market supplement is payable only to the extent that it does not cause an employee's adjusted salary rate to exceed the rate limitation described in § 9901.312(b). 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Official worksite</E>
                                        . When a local market supplement is linked to a geographic area, the employee's entitlement to the local market supplement is contingent on the employee's official worksite (as defined in 5 CFR 531.605) being located in that geographic area. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Treatment as basic pay</E>
                                        . Local market supplements are considered basic pay only for the following purposes: 
                                    </P>
                                    <P>(1) Retirement deductions, contributions, and benefits under 5 U.S.C. chapter 83 or 84; </P>
                                    <P>(2) Life insurance premiums and benefits under 5 U.S.C. chapter 87; </P>
                                    <P>(3) Premium pay under 5 U.S.C. chapter 55, subchapter V, or similar payments under other legal authority, including this subpart; </P>
                                    <P>(4) Severance pay under 5 U.S.C. 5595; </P>
                                    <P>(5) Cost-of-living allowances and post differentials under 5 U.S.C. 5941; </P>
                                    <P>(6) Overseas allowances and differentials under 5 U.S.C. chapter 59, subchapter III, to the extent authorized by the Department of State; </P>
                                    <P>(7) Recruitment, relocation, and retention incentives, supervisory differentials, and extended assignment incentives under 5 U.S.C. chapter 57, subchapter IV, and 5 CFR part 575; </P>
                                    <P>(8) Lump-sum payments for accumulated and accrued annual leave under 5 CFR 550, subpart L; </P>
                                    <P>(9) Determining whether an employee's rate of basic pay is reduced at the point of conversion or movement into or out of the NSPS pay system for the purpose of applying 5 U.S.C. chapter 75, subchapter II (dealing with adverse actions), consistent with §§ 9901.351(g), 9901.371(d), and 9901.372(f); </P>
                                    <P>(10) Other payments and adjustments under other statutory or regulatory authority for which locality-based comparability payments under 5 U.S.C. 5304 are considered part of basic pay; and </P>
                                    <P>(11) Any other provisions for which DoD local market supplements are expressly treated as basic pay by law or under this part. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.332 </SECTNO>
                                    <SUBJECT>Standard and targeted local market supplements. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General</E>
                                        . NSPS employees may receive standard or targeted local market supplements as described in paragraphs (b) and (c) of this section. Consistent with 5 U.S.C. 9902(e)(8), the full amount of standard and targeted local market supplements must be provided to employees who receive a rating of record above unacceptable (Level 1) or who do not have a rating of record for the most recently completed appraisal period. As provided in § 9901.334, an employee with an unacceptable rating of record may not receive an increase in a standard or targeted local market supplement. Standard local market supplements are designed to satisfy the requirements of 5 U.S.C. 9902(e)(8)(A), while targeted local market supplements are the “other local market supplements” referenced in 5 U.S.C. 9902(e)(8)(B). 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Standard local market supplements</E>
                                        . Employees are entitled to standard local market supplements that are generally equivalent to locality payments under 5 U.S.C. 5304 and 5304a, subject to the following requirements: 
                                    </P>
                                    <P>(1) The percentage values of standard local market supplements must be identical to the percentage values of locality payments established under 5 U.S.C. 5304 and 5304a, except as provided in § 9901.334 with respect to employees with an unacceptable rating of record; </P>
                                    <P>(2) The geographic areas in which standard local market supplements apply must be identical to the corresponding geographic areas established for locality payments under 5 U.S.C. 5304; </P>
                                    <P>(3) An employee's entitlement to a standard local market supplement is based on whether the employee's official worksite (defined consistent with the requirements in 5 CFR 531.605) is located in the given local market area; </P>
                                    <P>(4) The applicable standard local market supplement is paid on top of a retained rate (consistent with the NSPS modification of the pay retention rules); </P>
                                    <P>
                                        (5) The cap on an adjusted salary rate that includes a standard local market supplement is the rate for level IV of the 
                                        <PRTPAGE P="56401"/>
                                        Executive Schedule plus 5 percent (consistent with the NSPS extension of the highest band base rate ranges by 5 percent), as provided in § 9901.312(b), except as otherwise provided under § 9901.312(d); 
                                    </P>
                                    <P>(6) A standard local market supplement does not apply if an employee is entitled to a higher targeted local market supplement; and </P>
                                    <P>(7) Standard local market supplements are not applicable to physicians and dentists (in occupational series 0602 and 0680, respectively), since they receive higher base salary and adjusted salary rates (including any applicable targeted local market supplements) to achieve comparability with physicians and dentists paid under 38 U.S.C. chapter 74 and since their adjusted salary rates apply on a worldwide basis. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Targeted local market supplements</E>
                                        . Subject to § 9901.105, the Secretary may establish targeted local market supplements for specifically defined categories of employees in order to address significant recruitment or retention problems. This authority is subject to the following: 
                                    </P>
                                    <P>(1) The conditions for coverage under a targeted local market supplement may be based on occupation, band, organizational unit, geographic location of official worksite, specializations, special skills or qualifications, or other appropriate factors; </P>
                                    <P>(2) A targeted local market supplement applies to an employee eligible for a standard local market supplement only if the targeted local market supplement is a larger amount; and </P>
                                    <P>(3) Except for physicians and dentists (in occupational series 0602 and 0680, respectively) or as otherwise provided under § 9901.312(d), an employee's adjusted salary that includes an applicable targeted local market supplement may not exceed the rate cap equal to the rate for Executive Level IV plus 5 percent, as provided in § 9901.312(b). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.333 </SECTNO>
                                    <SUBJECT>Setting and adjusting local market supplements. </SUBJECT>
                                    <P>(a) Standard local market supplements are set and adjusted consistent with the setting and adjusting of corresponding General Schedule locality payments under 5 U.S.C. 5304 and 5304a. </P>
                                    <P>(b) Subject to § 9901.105, the Secretary may set and adjust targeted local market supplements. In determining the amounts of the supplements, the Secretary will consider mission requirements, labor market conditions, cost, and pay adjustments received by employees of other Federal agencies, allowances and differentials under 5 U.S.C. chapter 59, and any other relevant factors. The Secretary may determine the effective date of newly set or adjusted targeted local market supplements. Established supplements will be reviewed for possible adjustment at least annually in conjunction with rate range adjustments under § 9901.322. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.334 </SECTNO>
                                    <SUBJECT>Eligibility for pay increase associated with a supplement adjustment. </SUBJECT>
                                    <P>(a) When a local market supplement is adjusted under § 9901.333, employees to whom the supplement applies with current ratings of record above “unacceptable” (Level 1), and employees who do not have current ratings of record for the most recently completed appraisal period, are eligible to receive any pay increase resulting from that adjustment. </P>
                                    <P>(b) An employee with a current rating of record of “unacceptable” will not receive a pay increase under this section (i.e., the employee's local market supplement percentage will not be increased). Once such an employee has a new rating of record above “unacceptable,” the employee is entitled to the full amount of any applicable local market supplement effective on the date of the first adjustment in that local market supplement occurring on or after the effective date of the new rating of record as specified in § 9901.411(d), or, if earlier, the effective date of an applicable general salary increase as described in § 9901.323(b). </P>
                                    <HD SOURCE="HD1">Performance-Based Pay </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.341 </SECTNO>
                                    <SUBJECT>General. </SUBJECT>
                                    <P>Sections 9901.342 through 9901.345 describe the performance-based pay that is part of the pay system established under this subpart. These provisions authorize payments to employees based on individual performance or contribution, or team or organizational performance, as a means of fostering a high-performance culture that supports mission accomplishment. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.342 </SECTNO>
                                    <SUBJECT>Performance payouts. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Overview</E>
                                        . (1) The NSPS pay system will be a performance-based pay system and will result in a distribution of available performance pay funds based upon individual performance, individual contribution, team or organizational performance, or a combination of those elements. The NSPS pay system will use a pay pool concept to manage, control, and distribute performance-based pay increases and bonuses. The performance payout is a function of the amount of money in the performance pay pool and the number of shares assigned to individual employees. 
                                    </P>
                                    <P>(2) The rating of record used as the basis for a performance payout is the one assigned for the most recently completed appraisal period. Unless otherwise provided in this section, if an employee is not eligible to have a rating of record for the current rating cycle for reasons other than those identified in paragraphs (i) through (l) of this section, such employee will not be eligible for a performance payout under this part. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Performance pay pools</E>
                                        . (1) Pay pools and pay pool oversight will be established and managed in accordance with implementing issuances published by the Secretary, in such a manner as to ensure employees are treated fairly and consistently, and in accordance with merit system principles. 
                                    </P>
                                    <P>(2) Consistent with paragraph (b)(1) of this section, pay pool composition will be based on organization structure, classification structure, function of work, location, and/or organization mission. The decision on pay pool composition will be reviewed and approved by an official who is at a higher level than the official who made the initial decision, as determined by a Component, unless there is no official at a higher level in the organization. </P>
                                    <P>(3) Where determined appropriate, management may establish one or more subsets of a pay pool population (i.e., sub pay pools) for the purpose of reconciling ratings of record, share assignments, and payout determinations. Sub pay pools share in the common fund of the overall pay pool and operate within the requirements and guidelines established for the pay pool to which they belong. </P>
                                    <P>(4) The Secretary may determine a percentage of pay to be included in pay pools and paid out, in accordance with accompanying implementing issuances, as—</P>
                                    <P>(i) A performance-based pay increase; </P>
                                    <P>(ii) A performance-based bonus; or </P>
                                    <P>(iii) A combination of a performance-based pay increase and a performance-based bonus. </P>
                                    <P>(5) The decision to apply a funding floor or ceiling to a pay pool, including the amount of such floor or ceiling, will be reviewed and approved by an official who is at a higher level than the official who made the initial decision, as determined by a Component, unless there is no official at a higher level in the organization. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Pay Pool Panel</E>
                                        . (1) Consistent with this section, the Pay Pool Panel—
                                        <PRTPAGE P="56402"/>
                                    </P>
                                    <P>(i) Reviews rating of record, share assignment, and payout distribution recommendations; </P>
                                    <P>(ii) Makes adjustments, which in the Panel's view would result in equity and consistency across the pay pool; and </P>
                                    <P>(iii) Elevates any disagreement between the Pay Pool Panel and the employee's supervisory chain to the Pay Pool Manager as applicable, for resolution. </P>
                                    <P>(2) The Pay Pool Panel members may not participate in payout deliberations or decisions that directly impact their own ratings of record or pay. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Pay Pool Manager</E>
                                        . The Pay Pool Manager—
                                    </P>
                                    <P>(1) Provides oversight of the Pay Pool Panel; </P>
                                    <P>(2) Consistent with this section, is the final approving authority for performance ratings; and </P>
                                    <P>(3) May not participate in payout deliberations or decisions that directly impact his or her own rating of record or pay. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Performance Review Authority (PRA)</E>
                                        . Consistent with this section, the PRA—
                                    </P>
                                    <P>(1) Oversees the operation of pay pools established under NSPS; </P>
                                    <P>(2) Ensures procedural and funding consistency among pay pools under NSPS; and </P>
                                    <P>(3) May not participate in payout deliberations or decisions that directly impact his or her own rating of record or pay. </P>
                                    <P>
                                        (f) 
                                        <E T="03">Performance shares</E>
                                        . (1) Performance shares will be used to determine performance pay increases and/or bonuses. The range of shares which may be assigned for each rating level is as follows: 
                                    </P>
                                    <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s50,r50">
                                        <TTITLE>Performance Share Ranges Table </TTITLE>
                                        <BOXHD>
                                            <CHED H="1">Rating of record </CHED>
                                            <CHED H="1">Share range available for assignment </CHED>
                                        </BOXHD>
                                        <ROW>
                                            <ENT I="01">Level 5 </ENT>
                                            <ENT>5 or 6 shares.</ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Level 4 </ENT>
                                            <ENT>3 or 4 shares.</ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Level 3 </ENT>
                                            <ENT>1 or 2 shares.</ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Level 2 </ENT>
                                            <ENT>No shares.</ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Level 1 </ENT>
                                            <ENT>No shares.</ENT>
                                        </ROW>
                                    </GPOTABLE>
                                    <P>(2) The only factors that may be used in determining share assignment are complexity of the work, level of responsibility, compensation (e.g., recent salary increases, current salary in relation to control points or pay band maximum, current salary in relation to labor market), overall contribution to the mission of the organization, organizational success, and raw performance scores. Pay Pool Managers and/or Pay Pool Panels will review share assignment recommendations to ensure that factors are applied consistently across the pay pool and in accordance with the merit system principles. </P>
                                    <P>
                                        (g) 
                                        <E T="03">Performance payout</E>
                                        . (1) A performance share is expressed as a percentage of an employee's rate of base salary and is a common value throughout the pay pool. The percent value of a performance share is calculated by dividing the pay pool fund (expressed in dollars) by the summation of the products of multiplying each employee's base salary times the number of shares earned by the employee.
                                    </P>
                                    <FP SOURCE="FP-2">[Share Value(%) = Pay Pool Fund($)/Σ(base salary of each pay pool member × shares assigned each pay pool member)]</FP>
                                    <P>(2) An employee's performance payout is calculated by multiplying the employee's base salary as of the end of the pay pool's appraisal period times the number of shares earned by the employee times the share value.</P>
                                    <FP SOURCE="FP-2">[Employee Performance Payout = Base Salary × Shares × Share Value]</FP>
                                    <P>(3) A performance payout may be an increase in base salary, a bonus, or a combination of the two. An increase in base salary may not cause the employee's rate of base salary to exceed the maximum rate or applicable control point of the employee's band rate range. The decision to pay a bonus, including the amount of such bonus, will be reviewed and approved by an official who is at a higher level than the official who made the initial decision, as determined by a Component, unless there is no official at a higher level in the organization. </P>
                                    <P>(4) The factors management may consider in determining the amount to be paid out as a bonus versus an increase in the rate of base salary are limited to the following: </P>
                                    <P>(i) Current base salary in relation to appropriate rate range; </P>
                                    <P>(ii) Current base salary, level of responsibility and complexity of work performed in comparison with others in similar work assignments; </P>
                                    <P>(iii) Performance-based compensation received during the rating cycle associated with promotions, reassignments, or awards; </P>
                                    <P>(iv) Salary levels of occupations in comparable labor markets; </P>
                                    <P>(v) Attrition and retention rates of critical shortage skill personnel; </P>
                                    <P>(vi) Expectation of continued performance at that level; </P>
                                    <P>(vii) Overall contribution to the mission of the organization; and </P>
                                    <P>(viii) Composition of the pay pool fund. </P>
                                    <P>(5) When an employee's base salary is not increased because the employee's base salary has reached the maximum of the pay band or an applicable control point, any remaining performance payout will be paid as a bonus in lieu of the increase to base salary. </P>
                                    <P>(6) The effective date of an increase in base salary made under this section will be the first day of the first pay period beginning on or after January 1 of each year. </P>
                                    <P>(7) Unless otherwise specified in this section, employees who are no longer covered by NSPS on the effective date of the payout, or who moved out of NSPS on a permanent move after the end of their rating cycle but before the effective date of the payout, are not entitled to a performance-based payout. </P>
                                    <P>(8) For employees receiving a retained rate above the applicable pay band maximum, the entire performance payout must be in the form of a bonus payment. Any performance payout in the form of a bonus for a retained rate employee will be computed based on the maximum rate of the assigned pay band. </P>
                                    <P>(9)(i) NSPS employees shall be evaluated and assigned a rating of record by the appropriate official associated with the pay pool of record on the last day (normally September 30) of the appraisal period when the employee—</P>
                                    <P>(A) Changes jobs within NSPS after the last day of the appraisal period and before the effective date of the payout; </P>
                                    <P>(B) Is eligible for a rating of record; and </P>
                                    <P>(C) Moves to a position that falls under the authority of a different NSPS pay pool. </P>
                                    <P>(ii) For an employee covered by paragraph (g)(9)(i) of this section, the payout will be calculated and paid based on the pay pool funding and share valuation of the gaining pay pool except when the employee transfers to an NSPS position that does not have a fully constituted pay pool in which case the payout is based on the share valuation of the losing pay pool. In all cases, the gaining pay pool will determine the share assignment and payout distribution between salary increase and bonus. </P>
                                    <P>
                                        (10) To the extent permitted by law, NSPS organizations will share the results of the performance management process with NSPS employees. At a minimum, these pay pool results will include the following: Average rating, ratings distribution, share value (or average share value), and average payout (expressed as a percentage). Organizations will ensure that the sharing of these or any other pay pool results will be presented in a manner that does not violate the Privacy Act. 
                                        <PRTPAGE P="56403"/>
                                    </P>
                                    <P>
                                        (h) 
                                        <E T="03">Proration of performance payouts.</E>
                                         The Secretary will issue implementing issuances regarding prorating of performance payouts for employees who, during the appraisal period, are—
                                    </P>
                                    <P>(1) Hired, transferred, reassigned, or promoted into NSPS; </P>
                                    <P>(2) In a leave-without-pay status (except as provided in paragraphs (i) and (j) of this section); or </P>
                                    <P>(3) In other circumstances where prorating is considered appropriate. </P>
                                    <P>
                                        (i) 
                                        <E T="03">Adjustments for employees returning after performing honorable service in the uniformed services</E>
                                        —(1) 
                                        <E T="03">General.</E>
                                         The rate of base salary for an employee who is absent from an NSPS position to perform service in the uniformed services (in accordance with 38 U.S.C. 4301 et seq. and 5 CFR 353.102) and who has the right to be reemployed or restored to duty by law, Executive order, or regulation under which accrual of service for seniority-related benefits is protected (e.g., 38 U.S.C. 4316) will be set in accordance with this paragraph (i) and supplementary instructions in applicable implementing issuances. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Periods for which employee is eligible for a rating of record.</E>
                                         When an employee is eligible for an NSPS rating of record for an appraisal period, the employee will be credited with base salary rate increases as provided under § 9901.323 and under this section based on the employee's NSPS rating of record for that appraisal period. These rate adjustments are effective on the normal date for each adjustment (in accordance with §§ 9901.323 and 9901.342(g)(6)); however, if an employee is separated as opposed to in a leave status at the time of the adjustments, no adjustment will be processed until the employee is reemployed through the exercise of a reemployment right. An employee covered by this paragraph (i)(2) is eligible for a performance-based pay pool bonus if otherwise eligible by share assignment and payout distribution. 
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Periods for which employee is not eligible for a rating of record.</E>
                                         If an employee does not have an NSPS rating of record for the appraisal period serving as a basis for increases to base salary under this section, rate adjustments will be made based on the average base salary increase (expressed as a percentage) granted to other employees in the same pay pool who received the same rating as the employee's last NSPS rating of record or the average base salary increase (expressed as a percentage) granted to employees who received the modal rating for the pay pool, whichever is most advantageous to the employee. The employee will also be credited with base salary rate increases under § 9901.323 consistent with the provisions of that section. These rate adjustments are effective on the normal date for each adjustment in accordance with §§ 9901.323 and 9901.342(g)(6); however, if an employee is separated as opposed to in a leave status at the time of the adjustments, no adjustment will be processed until the employee is reemployed through the exercise of a reemployment right. The employee is not eligible for bonus payments for periods covered by this paragraph (i)(3), except as otherwise required by law. 
                                    </P>
                                    <P>
                                        (4) 
                                        <E T="03">Insufficient statistical information.</E>
                                         In cases where insufficient statistical information exists to determine the modal rating, the Secretary may establish alternative procedures for determining a base salary increase under this section. 
                                    </P>
                                    <P>
                                        (5) 
                                        <E T="03">Proration prohibited.</E>
                                         Proration of base salary rate adjustments is prohibited in the case of employees covered by this paragraph (i). 
                                    </P>
                                    <P>
                                        (j) 
                                        <E T="03">Adjustments for employees returning to duty after being in workers' compensation status</E>
                                        —(1) 
                                        <E T="03">General.</E>
                                         The rate of base salary for an employee who is absent from an NSPS position while receiving injury compensation under 5 U.S.C. chapter 81, subchapter I (in a leave-without-pay status or as a separated employee), and who has rights under 5 U.S.C. 8151 will be set in accordance with this paragraph (j) and applicable implementing issuances. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Periods for which employee is eligible for a rating of record.</E>
                                         When an employee is eligible for an NSPS rating of record for an appraisal period, the employee will be credited with base salary rate increases as provided under § 9901.323 and under this section based on the employee's NSPS rating of record for that appraisal period. These rate adjustments are effective on the normal date for each adjustment in accordance with §§ 9901.323 and 9901.342(g)(6); however, if an employee is separated at the time of the adjustments, no adjustment will be processed until the employee is reemployed. An employee covered by this paragraph (j)(2) is also eligible for a performance-based pay pool bonus if otherwise eligible by share assignment and payout distribution. 
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Periods for which employee is not eligible for a rating of record.</E>
                                         If an employee does not have an NSPS rating of record for the appraisal period serving as a basis for increases to base salary under this section, rate adjustments will be made based on the average base salary increase (expressed as a percentage) granted to other employees in the same pay pool who received the same rating as the employee's last NSPS rating of record or the average base salary increase (expressed as a percentage) granted to employees who received the modal rating for the pay pool, whichever is most advantageous to the employee. The employee will also be credited with base salary rate increases under § 9901.323 consistent with the provisions of that section. These rate adjustments are effective on the normal date for each adjustment in accordance with §§ 9901.323 and 9901.342(g)(6); however, if an employee is separated as opposed to in a leave status at the time of the adjustments, no adjustment will be processed until the employee is reemployed. The employee is not eligible for bonus payments for periods covered by this paragraph (j)(3). 
                                    </P>
                                    <P>
                                        (4) 
                                        <E T="03">Insufficient statistical information.</E>
                                         In cases where insufficient statistical information exists to determine the modal rating, the Secretary may establish alternative procedures for determining a base salary increase under this section. 
                                    </P>
                                    <P>
                                        (5) 
                                        <E T="03">Proration prohibited.</E>
                                         Proration of base salary adjustments is prohibited in the case of employees covered by this paragraph (j). 
                                    </P>
                                    <P>
                                        (k) 
                                        <E T="03">Adjustments for employees in special circumstances</E>
                                        —(1) 
                                        <E T="03">General.</E>
                                         The Secretary will adjust the rate of base salary in accordance with the provisions in this paragraph for an NSPS employee who is in an NSPS covered position on the effective date of the payout and who is unable to meet the minimum performance period during the given appraisal period as a result of—
                                    </P>
                                    <P>(i) Performing activities on “official time” (as defined in 5 U.S.C. 7131); </P>
                                    <P>(ii) Serving on a long-term training assignment; or, </P>
                                    <P>(iii) Approved paid leave. </P>
                                    <P>
                                        (2) 
                                        <E T="03">Base salary increases.</E>
                                         If an employee does not have an NSPS rating of record for the appraisal period serving as a basis for increases to base salary under this section, such adjustments will be based on the average base salary increase (expressed as a percentage) granted to other employees in the same pay pool who received the same rating as the employee's last NSPS rating of record or the average base salary increase (expressed as a percentage) granted to employees who received the modal rating for the pay pool, whichever is most advantageous to the employee. 
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Insufficient statistical information.</E>
                                         In cases where insufficient statistical information exists to determine the modal rating, the Secretary may establish alternative procedures for determining a base salary increase under this section. 
                                        <PRTPAGE P="56404"/>
                                    </P>
                                    <P>
                                        (l) 
                                        <E T="03">Adjustments for employees returning from temporary assignments outside of NSPS for which no NSPS performance plan was assigned</E>
                                        —(1) 
                                        <E T="03">General.</E>
                                         The Secretary will set the rate of base salary prospectively for an employee who returns from a temporary assignment (including a supervisory probationary assignment) outside of NSPS for which no NSPS performance plan was assigned in accordance with this paragraph (l). 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Periods for which employee is eligible for a rating of record.</E>
                                         When an employee is eligible for an NSPS rating of record for an appraisal period, the employee will be credited with base salary increases as provided under § 9901.323 and this section based on the employee's NSPS rating of record for that appraisal period. When an employee returns to an NSPS position, these adjustments will be processed in determining the employee's prospective base salary rate. An employee covered by this paragraph (l)(2) is also eligible for a performance-based pay pool bonus if otherwise eligible by share assignment and payout distribution. 
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Periods for which employee is not eligible for a rating of record.</E>
                                         If an employee does not have an NSPS rating of record for the appraisal period serving as a basis for increases to base salary under this section, the employee will be credited with base salary rate adjustments based on the average base salary increase (expressed as a percentage) granted to other employees in the same pay pool who received the same rating as the employee's last NSPS rating of record or the average base salary increase (expressed as a percentage) granted to employees who received the modal rating for the pay pool, whichever is most advantageous to the employee. The employee will also be credited with base salary rate increases under § 9901.323 consistent with the provisions of that section. The base salary rate adjustments under this paragraph (l)(3) will be used solely in determining the prospective NSPS base salary rate upon return to the NSPS position. The employee is not eligible for bonus payments for periods covered by this paragraph (l)(3). 
                                    </P>
                                    <P>
                                        (4) 
                                        <E T="03">Insufficient statistical information.</E>
                                         In cases where insufficient statistical information exists to determine the modal rating, the Secretary may establish alternative procedures for determining a base salary increase under this section. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.343 </SECTNO>
                                    <SUBJECT>Pay reduction based on unacceptable performance and/or conduct. </SUBJECT>
                                    <P>An employee's rate of base salary may be reduced based on a determination of unacceptable performance, conduct, or both after applying applicable adverse action procedures. Such a reduction will be at least 5 percent of base salary and may not exceed 10 percent of base salary. However, a reduction in base salary may be less than 5 percent to prevent the employee's base salary from falling below the minimum rate of the employee's pay band and may be more than 10 percent if a larger reduction is needed to place the employee at the maximum rate of the lower band. (See also §§ 9901.353(f) and 9901.355(b)(4).) An employee's rate of base salary may not be reduced more than once in a 12-month period based on unacceptable performance, conduct, or both. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.344 </SECTNO>
                                    <SUBJECT>Other performance payments. </SUBJECT>
                                    <P>(a) The decision to grant other performance payouts, including the amount of such payouts, will be reviewed and approved by an official of the employee's Component who is at a higher level than the official who made the initial decision, as determined by the Component, unless there is no official at a higher level in the organization. In accordance with implementing issuances, authorized officials may make other performance payments to—</P>
                                    <P>(1) Reward extraordinary individual performance, as described in paragraph (b) of this section; </P>
                                    <P>(2) Recognize organizational or team achievement, as described in paragraph (c) of this section; and </P>
                                    <P>(3) Provide for other special circumstances. </P>
                                    <P>(b)(1) Extraordinary Performance Recognition (EPR) is an increase to base salary, a bonus, or a combination of these intended to reward employees when the payout formula does not adequately compensate them for their extraordinary performance and results. The EPR payment is in addition to performance payouts under § 9901.342 and will usually be made effective at the time of those payouts. When an EPR payout is made in the form of an increase to base salary, the future performance and contribution level exhibited by the employee will be expected to continue at an extraordinarily high level. </P>
                                    <P>(2) Only employees who have achieved a Level 5 NSPS rating of record for the most recently completed appraisal period are eligible for an EPR. </P>
                                    <P>(3) The amount of an EPR awarded in the form of an increase to base salary may not cause the employee's base salary to exceed the maximum rate of the employee's pay band or any applicable control point, unless the criteria for exceeding the control point are met. </P>
                                    <P>(c)(1) Organizational/Team Achievement Recognition (OAR) payments may be made in the form of an increase to base salary, a bonus, or a combination of these in order to recognize the members of a team, organization or branch whose performance and contributions have successfully and directly advanced organizational goals. The OAR payment is made in conjunction with the annual performance payout. </P>
                                    <P>(2) To receive an OAR, an employee must have an NSPS rating of record of Level 3 or higher for the most recently completed appraisal period. </P>
                                    <P>(3) The amount of the OAR payment provided in the form of an increase to base salary may not cause the employee's base salary to exceed the maximum rate of the employee's pay band or any applicable control point, unless the criteria for exceeding the control point are met. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.345 </SECTNO>
                                    <SUBJECT>Accelerated Compensation for Developmental Positions (ACDP). </SUBJECT>
                                    <P>(a) Accelerated Compensation for Developmental Positions (ACDP) is an increase to base salary that may be provided to employees participating in Component training programs or in other developmental capacities as determined by Component policy. ACDP recognizes growth and development in the acquisition of job-related competencies combined with successful performance of job objectives. </P>
                                    <P>(b) The use of ACDP is limited to—</P>
                                    <P>(1) Employees in the lowest pay band of a nonsupervisory pay schedule who are in developmental or trainee level positions; and </P>
                                    <P>(2) Employees in positions which are assigned to a Student Career Experience Program and which are in a pay schedule established exclusively for students. </P>
                                    <P>(c) Components choosing to provide ACDP increases must establish and document standards by which such employees will be identified and growth and development criteria by which additional pay increases will be determined. </P>
                                    <P>
                                        (d) The amount of the ACDP increase generally will not exceed 20 percent of an employee's base salary. The decision to grant an ACDP exceeding 20 percent of an employee's base salary must be made on a case-by-case basis and approved by an official who is at a higher level than the official who made the initial decision, as determined by the Component, unless there is no 
                                        <PRTPAGE P="56405"/>
                                        official at a higher level in the organization. 
                                    </P>
                                    <P>(e) The amount of the ACDP increase may not cause the employee's base salary to exceed the top of the employee's pay band or any applicable control point, unless the criteria for exceeding the control point are met. </P>
                                    <P>(f) To qualify for an ACDP, an employee must have a rating of record of Level 3 (or equivalent non-NSPS rating of record) or higher, consistent with § 9901.405. An ACDP may be awarded to an employee who does not have a rating of record if an authorizing official conducts a performance assessment and determines that the employee is performing at the equivalent of Level 3 or higher. This performance assessment does not constitute a rating of record. </P>
                                    <P>(g) An ACDP increase may not be granted unless the employee is in a pay and duty status in an NSPS-covered position on the effective date of the increase. </P>
                                    <P>(h) The Secretary may provide adjustments under this section in lieu of or in addition to adjustments under § 9901.342. </P>
                                    <HD SOURCE="HD1">Pay Administration </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.351 </SECTNO>
                                    <SUBJECT>General. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Introduction</E>
                                        . The pay administration provisions in §§ 9901.351 through 9901.356 are applied using base salary rates, except when specifically otherwise provided. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Geographic recalculation</E>
                                        . When an employee covered by a targeted local market supplement moves to a position in a new location where a different local market supplement and/or pay schedule applies, the employee's adjusted salary before the move will be recalculated to reflect a local market supplement (standard or targeted, as appropriate) for the employee's existing position—as if that position were at the same location as the position to which the employee is moving, consistent with the geographic conversion principle described at 5 CFR 531.205. For employees moving from a non-NSPS position to an NSPS position in a different location covered by a different salary supplement, the employee's adjusted salary under the former system will be recalculated as if the former position were located in the new location, consistent with the geographic conversion principle described at 5 CFR 531.205 or 5 CFR 536.303(b), as applicable. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Within-grade increase (WGI) adjustment equivalent</E>
                                        . (1) When an employee is permanently placed (not by conversion under § 9901.371 or by promotion under § 9901.354) in an NSPS position from a GS or FWS position through a management-directed action (except for actions taken for misconduct or unacceptable performance), including a management-directed reassignment or realignment, or any placement as a result of a reduction in force (RIF), or placement via the Priority Placement Program (PPP), Reemployment Priority List (RPL), or Interagency Career Transition Assistance Plan (ICTAP), the employee will receive an increase to base salary equivalent to the amount he or she would have received as a WGI adjustment if the employee had converted into NSPS with his or her organization, as provided in § 9901.371. 
                                    </P>
                                    <P>(2) An employee who is placed in an NSPS position from a GS or FWS position through an employee-initiated reassignment may, at the discretion of the authorized management official, receive this same WGI adjustment equivalent increase described in paragraph (c)(1) of this section. The decision to grant this increase will be reviewed and approved by an official who is at a higher level than the official who made the initial decision, as determined by the Component. At a minimum, the higher-level approval level may be no lower than one level above the authorized management official who approved the reassignment unless there is no official at a higher level in the organization. </P>
                                    <P>(3) An increase provided under paragraphs (c)(1) and (c)(2) of this section occurs before any other discretionary reassignment increases provided under NSPS, may not cause the employee's base salary to exceed the maximum rate of the assigned pay band, and is in addition to any other discretionary reassignment increase the employee may be eligible to receive. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Minimum rate</E>
                                        . Except in the case of an employee who does not receive a pay increase under § 9901.323 because of an unacceptable rating of record, an employee's base salary may not be less than the minimum rate of the employee's pay band. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Maximum rate</E>
                                        . Except as provided in § 9901.356, an employee's base salary may not exceed the maximum rate of the employee's band rate range. 
                                    </P>
                                    <P>
                                        (f) 
                                        <E T="03">Pay periods and hourly rates</E>
                                        . The establishment of pay periods and the computation of rates of pay will conform to 5 U.S.C. 5504 and 5505, as applicable. For employees covered by 5 U.S.C. 5504, annual rates of base salary will be converted to hourly rates of base salary in computing payments received by covered employees. 
                                    </P>
                                    <P>
                                        (g) 
                                        <E T="03">Rate comparisons upon movement to an NSPS position</E>
                                        . An employee who moves to an NSPS position from a non-NSPS position by management-directed action (excluding conversion under § 9901.371) will receive a rate of basic pay that is not less than the employee's rate of basic pay immediately before movement (after making adjustments consistent with those made under § 9901.371(e) for employees who convert to NSPS). For this purpose and for the purpose of applying 5 U.S.C. chapter 75, subchapter II (dealing with adverse actions), at the point of movement into NSPS, an employee's rate of basic pay includes any applicable locality payment under 5 U.S.C. 5304, special rate supplement under 5 U.S.C. 5305, local market supplement under § 9901.332, or equivalent payment under other legal authority. 
                                    </P>
                                    <P>
                                        (h) 
                                        <E T="03">Adjustment of annual rates for employees leaving certain teaching positions</E>
                                        . When an individual leaves a teaching position as defined in 20 U.S.C. 901 and moves to a position covered by NSPS, the individual's existing annual base salary rate for the teaching position may be adjusted for the purpose of setting pay under NSPS. The adjustment will take into account the shorter work year applicable to the teacher position. The adjustment may not exceed 20 percent of the existing annual base salary rate of the teaching position. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.352 </SECTNO>
                                    <SUBJECT>Setting an employee's starting pay. </SUBJECT>
                                    <P>(a) Subject to the requirements of this section, the Secretary may set the starting base salary rate for individuals who are newly appointed or reappointed to the Federal service anywhere within the rate range of the assigned pay band (subject to any applicable control points). Pay will be set based upon the following considerations: </P>
                                    <P>(1) Labor market considerations (i.e., availability of candidates and labor market rates); </P>
                                    <P>(2) Specialized skills, knowledge, and/or education possessed by the employee in relation to the requirements of the position; </P>
                                    <P>(3) Critical mission or business requirement(s); </P>
                                    <P>(4) Salaries of other employees in the organization performing similar work; and </P>
                                    <P>(5) Current salary of the candidate. </P>
                                    <P>
                                        (b) For the purposes of this section, “newly appointed” means those individuals who have not previously been employed in the Federal service—i.e., this is their first Federal appointment. The term “reappointed” 
                                        <PRTPAGE P="56406"/>
                                        means those individuals who have been previously employed in the Federal service and have been separated from the Federal service for at least 1 full workday immediately before employment in an NSPS position. The term “Federal service” includes civilian service as an employee of any entity of the Federal Government, including the judicial branch, legislative branch, and executive branch (including Government corporations, the Postal Regulatory Commission, the U.S. Postal Service and any nonappropriated fund (NAF) instrumentality described in 5 U.S.C. 2105(c)). 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.353 </SECTNO>
                                    <SUBJECT>Setting pay upon reassignment. </SUBJECT>
                                    <P>(a)(1) A reassignment occurs when an employee moves, voluntarily or involuntarily, to a different position or set of duties within his/her pay band or to a position in a comparable pay band, or from a non-NSPS position to an NSPS position at a comparable level of work, on either a temporary or permanent basis. In NSPS, employees may be eligible for an increase or decrease to base salary upon temporary or permanent reassignment as described in this section. </P>
                                    <P>(2) An employee who is reassigned through reduction-in-force (RIF) procedures is not eligible for an increase to base salary under this section (except as necessary to set the employee's rate at the band minimum), but is eligible for an increase under § 9901.351(c)(1). An employee's base salary will be protected by applying pay retention under § 9901.356, if applicable. </P>
                                    <P>(3) A decision to increase an employee's pay under this section will be based on one or more of the following factors: </P>
                                    <P>(i) A determination that an employee's responsibilities will significantly increase; </P>
                                    <P>(ii) Critical mission or business requirements; </P>
                                    <P>(iii) Need to advance multi-functional competencies; </P>
                                    <P>(iv) Labor market conditions (i.e., availability of candidates and labor market rates); </P>
                                    <P>(v) Reassignment from nonsupervisory to supervisory position; </P>
                                    <P>(vi) Employee's past and anticipated performance and contribution; </P>
                                    <P>(vii) Location of position; </P>
                                    <P>(viii) Specialized skills, knowledge, or education possessed by the employee in relation to those required by the position; and </P>
                                    <P>(ix) Salaries of other employees in the organization performing similar work. </P>
                                    <P>(b)(1) Except as otherwise provided in paragraph (c) of this section, when an employee is voluntarily reassigned within his/her pay band or to a comparable pay band, an authorized management official may reduce the employee's base salary in any amount determined prior to the reassignment with the employee's agreement, as long as the employee's base salary does not drop below the minimum of the assigned rate range. In appropriate circumstances, an authorized management official may make approval of a reassignment contingent on the employee's acceptance of a reduced rate. Subject to paragraph (b)(2) of this section, an authorized management official may also increase the employee's current base salary by up to 5 percent (not to exceed the rate range maximum). </P>
                                    <P>(2) The decision to grant a decrease or increase, including the amount of such decrease or increase, as applicable under paragraph (b)(1) of this section, will be reviewed and approved by an official who is at a higher level than the official who made the initial decision, as determined by the Component. At a minimum, the higher-level approval may be no lower than one level above the authorized management official who approved the reassignment unless there is no official at the higher level in the organization. There are no limits to the number of times an employee may be reassigned; however, an employee may only receive up to a total of a 5 percent cumulative increase to base salary in any 12-month period as the result of an employee-initiated action, unless an exception to the 12-month limitation is approved by an authorized management official. The increase will be calculated as a percentage of the employee's base salary at the time the increase takes effect. </P>
                                    <P>(c)(1) Subject to paragraphs (b)(2) and (c)(2) through (c)(5) of this section, as applicable, when an employee is voluntarily reassigned from a position with a targeted local market supplement or from a non-NSPS position (e.g., General Schedule, Federal Wage System, Nonappropriated Fund), an authorized management official will set pay considering the employee's adjusted salary (including any applicable locality pay, special rate supplement, or other equivalent supplement) and any physicians' comparability allowance payable for the position held prior to the reassignment. </P>
                                    <P>(2) An authorized management official may—</P>
                                    <P>(i) Set the employee's new adjusted salary equal to the employee's current adjusted salary plus any physicians' comparability allowance, if applicable, received prior to the reassignment; </P>
                                    <P>(ii) Decrease the employee's adjusted salary by any amount determined prior to the reassignment with the employee's agreement, as long as the employee's base salary does not drop below the minimum of the assigned rate range; or </P>
                                    <P>(iii) Increase the employee's current adjusted salary plus any physicians' comparability allowance, if applicable, by up to 5 percent (subject to the limitation that the resulting base salary may not exceed the rate range maximum). </P>
                                    <P>(3) After setting the employee's NSPS adjusted salary, the adjusted salary will be apportioned between the employee's base salary and the appropriate local market supplement or targeted local market supplement. </P>
                                    <P>(4) If the NSPS adjusted salary is increased beyond the amount of the employee's current adjusted salary plus any physicians' comparability allowance, the percentage of the increase is counted toward the 12-month limitation under paragraph (b) of this section. </P>
                                    <P>(5) When an employee covered by paragraph (c)(1) of this section moves geographically in conjunction with a voluntary reassignment, the employee's current adjusted salary must be recalculated in accordance with the rules at § 9901.351(b) before setting pay under paragraph (c)(2) of this section. </P>
                                    <P>(d)(1) Except as otherwise provided in paragraphs (e) or (f) of this section, when an employee is reassigned via management-directed action within his/her current pay band or to a comparable pay band, an authorized management official will set pay at an amount no less than the employee's current base salary and may increase the employee's current base salary by up to 5 percent. (If the employee's current base salary exceeds the maximum of the new pay band, no increase is provided, and the employee's rate will be set at that maximum rate, or if the employee is eligible, converted to a retained rate as provided in § 9901.356.) </P>
                                    <P>
                                        (2) The decision to grant an increase under paragraph (d)(1) of this section, including the amount of such increase, is discretionary and will be reviewed and approved by an official who is at a higher level than the official who made the initial decision, as determined by a Component, unless there is no official at a higher level in the organization. There is no limit to the number of times an employee may be reassigned by management, and the employee is eligible for an increase of up to 5 percent with each reassignment. Any increase associated with a management-directed reassignment does not count toward the 12-month limitation 
                                        <PRTPAGE P="56407"/>
                                        described in paragraph (b) of this section. 
                                    </P>
                                    <P>(e)(1) Subject to paragraphs (d)(2), (e)(2), (e)(3), and (f) of this section, as applicable, when an employee is reassigned via management-directed action from a position with a targeted local market supplement or from a non-NSPS position (e.g., General Schedule, Federal Wage System, Nonappropriated Fund), an authorized management official will set the employee's new adjusted salary at no less than the employee's adjusted salary (including any applicable locality pay, special rate supplement, or equivalent supplement) plus any physicians' comparability allowance payable for the position held prior to the reassignment, provided the resulting base salary does not exceed the maximum rate of the new pay band. Subject to the same maximum limitation, an authorized management official may also increase the employee's adjusted salary by up to 5 percent. </P>
                                    <P>(2) After setting the employee's NSPS adjusted salary, the adjusted salary will be apportioned between the employee's base salary and the appropriate local market supplement or targeted local market supplement. </P>
                                    <P>(3) When an employee covered by paragraph (e)(1) of this section moves geographically in conjunction with a management-directed reassignment, the employee's current adjusted salary must be recalculated in accordance with the rules in § 9901.351(b) before setting pay under such paragraph (e)(1). </P>
                                    <P>(4) For the purpose of determining whether an employee experienced a reduction in pay under 5 U.S.C. chapter 75 when reassigned from a non-NSPS position under paragraph (e)(1) of this section, § 9901.351(g) applies. </P>
                                    <P>(f) When an employee is involuntarily reduced in pay via reassignment to a comparable pay band through adverse action procedures (as a result of unacceptable performance and/or conduct), the pay reduction must be at least 5 percent, but no more than 10 percent, of an employee's base salary. However, a reduction may be less than 5 percent to prevent the employee's base salary from falling below the minimum rate of the employee's pay band and may be more than 10 percent if a larger reduction is needed to place the employee at the maximum rate of the lower band. An employee's base salary may not be reduced more than once in a 12-month period based on unacceptable performance, conduct, or both. (See also § 9901.343.) </P>
                                    <P>(g) When an employee returns to an NSPS position from a temporary reassignment to another NSPS position, the employee's current base salary rate must be reconstructed as if the employee had not been temporarily reassigned. For this purpose, the employee will be deemed to have received performance pay increases under § 9901.342 and other increases in base salary under §§ 9901.344 and 9901.345 equal to the percentage value of such increases actually received by the employee during the temporary reassignment. However, any such increases must be applied as if the employee were in the position and band held immediately before the temporary reassignment (i.e., using the rate range and any applicable control points for that band). The employee will also be credited with any general salary increases provided during the temporary reassignment that would have been applied to the employee if he or she had continued to hold the position held immediately before that temporary reassignment. A reassignment increase is not authorized when the employee returns to the position from which temporarily reassigned. (See § 9901.342(l) for rules governing pay setting for an employee who returns to an NSPS position after being temporarily assigned to a non-NSPS position.) </P>
                                    <P>(h) If an employee's temporary reassignment is made permanent, the permanent reassignment is treated as a new reassignment for purposes of applying this section. </P>
                                    <P>(i) When an employee is reassigned to an NSPS supervisory position but later returns to the NSPS position held before that reassignment (or comparable position) because of failure to complete a supervisory probationary period, the employee's base salary rate must be reconstructed as if the employee had not been reassigned. For this purpose, the employee will be deemed to have received performance pay increases under § 9901.342 and other increases in base salary under §§ 9901.344 and 9901.345 equal to the percentage value of such increases actually received by the employee during the reassignment. However, any such increases must be applied as if the employee were in the position and band held immediately before the reassignment (i.e., using the rate range and any applicable control points for that band). The employee will also be credited with any general salary increases provided during the reassignment that would have been applied to the employee if he or she had continued to hold the position held immediately before that reassignment. A reassignment increase upon return to the previous position (or comparable position) under this paragraph is not authorized. (See § 9901.342(l) for rules governing pay setting for an employee who returns to an NSPS position after failure to complete a supervisory probationary period for a non-NSPS supervisory position.) </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.354 </SECTNO>
                                    <SUBJECT>Setting pay upon promotion. </SUBJECT>
                                    <P>(a)(1) Except as otherwise provided in this section, upon an employee's promotion, the employee will receive an increase in his or her base salary equal to at least 6 percent, but the resulting base salary rate may not be lower than the minimum rate or higher than the maximum rate of the new pay band. The decision to grant a promotion increase exceeding 12 percent must be reviewed and approved by an official who is at a higher level than the official who made the initial decision, as determined by the Component, unless a higher increase is necessary to reach the minimum rate of the new pay band or there is no official at a higher level in the organization. </P>
                                    <P>(2) When an employee from a non-NSPS position is promoted to an NSPS position, the authorized management official shall first apply § 9901.353(e)(1) through (e)(3) to determine the employee's adjusted salary rate as if reassigned without a discretionary increase or decrease in pay. After apportioning the employee's adjusted salary between base salary and local market supplement or targeted local market supplement, the authorized management official will then increase the employee's salary rate as provided in § 9901.354(a)(1). </P>
                                    <P>(b) The authorized management official may consider only the following criteria in determining the amount of the promotion increase: </P>
                                    <P>(1) Critical mission or business requirements; </P>
                                    <P>(2) Employee's past and anticipated performance and contribution; </P>
                                    <P>(3) Specialized skills or knowledge possessed by the employee; </P>
                                    <P>(4) Labor market conditions (including availability of candidates and the labor market rates for similar types of employees at the level represented by the pay band to which the employee is being promoted); </P>
                                    <P>(5) Base salary rates paid to other employees in similar positions in the higher pay band; and </P>
                                    <P>(6) Location of position. </P>
                                    <P>(c)(1) If an employee's temporary promotion is made permanent without a break, the employee's base salary will remain unchanged. No additional promotion increase may be provided. </P>
                                    <P>
                                        (2) When an employee returns from a temporary promotion to another NSPS position, the employee's current base 
                                        <PRTPAGE P="56408"/>
                                        salary rate must be reconstructed as if the employee had not been temporarily promoted. For this purpose, the employee will be deemed to have received performance pay increases under § 9901.342 and other increases in base salary under §§ 9901.344 and 9901.345 equal to the percentage value of such increases actually received by the employee during the temporary promotion. However, any such increases must be applied as if the employee were in the position and band held immediately before the temporary promotion (i.e., using the rate range and any applicable control points for that band). The employee will also be credited with any general salary increases provided during the temporary promotion that would have been applied to the employee if he or she had continued to hold the position held immediately before that temporary promotion. A reduction-in-band increase upon return to the previous position (or comparable position) under this paragraph is not authorized. (See § 9901.342(l) for rules governing pay setting for an employee who returns to an NSPS position after being temporarily assigned to a non-NSPS position.) 
                                    </P>
                                    <P>(d)(1) An employee on pay retention who is re-promoted to the pay band from which reduced (or a comparable band) is not automatically entitled to have his/her pay set in accordance with the promotion rules described in paragraphs (a) and (b) of this section. If the employee's retained rate falls within the rate range of the newly assigned pay band, the authorized management official may maintain the same base salary upon re-promotion, or increase the employee's base salary to a rate above his or her retained rate. However, the employee's new base salary may not exceed the rate that would be provided using the promotion rules described in paragraphs (a) and (b) of this section. The employee's retained rate will be used when calculating any increase approved by an authorized management official. If the employee's retained rate falls below the minimum rate of the newly assigned pay band, the employee's base salary must be set at least at the minimum rate of the band. If the employee's retained rate is higher than the maximum rate of the newly assigned pay band, pay retention will continue (subject to the requirements of § 9901.356). </P>
                                    <P>(2) An employee who is promoted to a pay band higher than the one from which previously reduced in band will be covered by the promotion rules described in paragraphs (a) and (b) of this section. The employee's retained rate will be used when calculating the 6 percent (or higher) increase. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.355 </SECTNO>
                                    <SUBJECT>Setting pay upon reduction in band. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         When an employee is reduced in band, either voluntarily or involuntarily, the setting of the employee's base salary rate is subject to the rules in this section. As applicable, pay retention provisions established under § 9901.356 will apply. If pay retention does not apply, the employee's base salary may be reduced, subject to the requirements in paragraph (b) of this section. The employee may be eligible for an increase to base salary, subject to the requirements in paragraph (c) of this section. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Pay reduction.</E>
                                         An employee's base salary may be reduced upon reduction in band, subject to the following requirements: 
                                    </P>
                                    <P>(1) No base salary reduction is made when pay retention is applicable, except under paragraph (b)(4) of this section. </P>
                                    <P>(2) The reduction in base salary may not cause the rate to fall below the minimum rate of the employee's new band. </P>
                                    <P>(3) The base salary must be reduced as necessary to ensure that the new base salary is no greater than the maximum rate of the employee's new band. </P>
                                    <P>(4) Adverse action procedures in 5 U.S.C. chapter 75 must be applied when an employee is involuntarily placed in a position in a lower pay band for unacceptable performance and/or conduct. In this circumstance, the authorized management official may reduce the employee's base salary. If such a reduction is made, it must be at least 5 percent, but no more than 10 percent, of an employee's base salary after applying adverse action procedures. However, a reduction in base salary under this paragraph may be less than 5 percent to prevent the employee's base salary from falling below the minimum rate of the employee's new pay band and may be more than 10 percent if a larger reduction is needed to place the employee at the maximum rate of the lower band. (See also § 9901.343.) </P>
                                    <P>(5) If an employee held a position with a targeted local market supplement or a non-NSPS position prior to the reduction in band, the pay reduction is applied using adjusted salary rates, consistent with the reassignment rules in § 9901.353(c) (including, as appropriate, a geographic recalculation prior to applying the decrease, consistent with the provisions of § 9901.351(b)). </P>
                                    <P>
                                        (c) 
                                        <E T="03">Pay increase.</E>
                                         An employee's base salary may be increased by an authorized management official upon reduction in band, subject to the following requirements: 
                                    </P>
                                    <P>(1) An employee who is reduced in band involuntarily—e.g., through reduction-in-force (RIF) procedures or by placement through the DoD Priority Placement Program (PPP) or Reemployment Priority List (RPL)—is not eligible for an increase to base salary (except if necessary to set the employee's base salary at the minimum rate of the new pay band). </P>
                                    <P>(2) When an employee voluntarily moves to a lower pay band, the authorized management official may increase the employee's base salary, but must set the employee's base salary within the rate range for the employee's band. An increase in base salary may be up to 5 percent of the employee's current base salary (not to exceed the maximum of the rate range). This increase of up to 5 percent is deemed to be a “reassignment increase” for the purpose of applying the 12-month limitation in § 9901.353(b)(2). Also, in applying this increase, adjusted salary rates will be used when an employee held a position with a targeted local market supplement or a non-NSPS position prior to the reduction in band, consistent with the reassignment increase rules in § 9901.353(c) (including, as appropriate, a geographic recalculation prior to applying the increase, consistent with the provisions of § 9901.351(b)). This increase is subject to higher-level approval. At a minimum, the higher-level approval may be no lower than one level above the authorized management official who approved the reduction in band, unless there is no higher-level management official. </P>
                                    <P>(3) After setting the employee's NSPS adjusted salary, the adjusted salary will be apportioned between the employee's base salary and the appropriate local market supplement or targeted local market supplement. </P>
                                    <P>(4) A decision to increase an employee's pay under paragraph (c)(2) of this section will be based on—</P>
                                    <P>(i) Critical mission or business requirements; </P>
                                    <P>(ii) The need to advance multi-functional competencies; </P>
                                    <P>(iii) The labor market conditions (i.e., availability of candidates, labor market rates for similar types of employees); </P>
                                    <P>(iv) Reassignment from nonsupervisory to supervisory position; </P>
                                    <P>(v) Location of position; </P>
                                    <P>(vi) Required specialized skills, knowledge, or education possessed by the employee; </P>
                                    <P>
                                        (vii) Performance-based considerations; and 
                                        <PRTPAGE P="56409"/>
                                    </P>
                                    <P>(viii) The base salary rates paid to other employees in similar positions in the lower pay band. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Termination of temporary promotion.</E>
                                         This section does not apply to a reduction in band associated with the termination of a temporary promotion. Instead, the rules in § 9901.354(c)(2) apply. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Failure to complete probationary period.</E>
                                         When an employee who fails to complete a supervisory probationary period is reduced in band upon return to the position held before the probationary period (or a comparable position), the employee's current base salary rate must be reconstructed as if the employee had not been promoted. For this purpose, the employee will be deemed to have received performance pay increases under § 9901.342 and other increases in base salary under §§ 9901.344 and 9901.345 equal to the percentage value of such increases actually received by the employee during the promotion. However, any such increases must be applied as if the employee were in the position and band held immediately before the promotion (
                                        <E T="03">i.e.</E>
                                        , using the rate range and any applicable control points for that band). The employee will also be credited with any general salary increases provided during the promotion that would have been applied to the employee if he or she had remained in the position held immediately before that promotion. A reduction-in-band increase upon return to the previous position (or comparable position) under this paragraph is not authorized. (See § 9901.342(l) for rules governing pay setting for an employee who returns to an NSPS position after being temporarily assigned to a non-NSPS position.) 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.356 </SECTNO>
                                    <SUBJECT>Pay retention. </SUBJECT>
                                    <P>(a) Pay retention prevents a reduction in base salary that would otherwise occur by preserving the former rate of base salary within the employee's new pay band or by establishing a retained rate that exceeds the maximum rate of the new pay band. Local market supplements are not considered part of base salary in applying pay retention. </P>
                                    <P>(b) Pay retention will be based on the employee's rate of base salary in effect immediately before the action that would otherwise reduce the employee's rate. A retained rate will be compared to the range of rates of base salary applicable to the employee's position. </P>
                                    <P>(c) Pay retention will be granted for a period of 104 weeks. The Secretary may issue implementing issuances describing exceptions to the 104-week retention limit. </P>
                                    <P>(d) Under NSPS, pay retention will be granted when an employee's base salary would otherwise be reduced in the following situations: </P>
                                    <P>(1) As the result of reduction in force or reclassification; </P>
                                    <P>(2) When an otherwise eligible employee is placed through the Priority Placement Program (PPP), including placement resulting from early registration, even though the employee does not have a specific reduction in force (RIF) notice; </P>
                                    <P>(3) When an organization undergoes realignment or reduction, and </P>
                                    <P>(i) An employee who would not be affected personally requests a reduction in band; </P>
                                    <P>(ii) Management determines the employee's reduction in band results in placement in a more suitable position; and </P>
                                    <P>(iii) That action lessens or avoids the impact of the RIF on other employees; </P>
                                    <P>(4) When an employee accepts a position in a lower pay band designated in advance by the component as being hard-to-fill using any of the following criteria: </P>
                                    <P>(i) Rates of pay offered by non-Federal employers are significantly higher than those payable under NSPS for the area, location, occupational group, or other class of positions involved; </P>
                                    <P>(ii) The remoteness of the area or location involved; </P>
                                    <P>(iii) The undesirability of the working conditions or the nature of the work involved (including exposure to toxic substances or other occupational hazards); or </P>
                                    <P>(iv) Any other circumstances the Component considers appropriate, subject to review and approval by an official who is at a higher level than the official who made the initial decision; </P>
                                    <P>(5) When an employee is reduced in band on return from an overseas assignment under the terms of a pre-established agreement including—</P>
                                    <P>(i) An employee released from a period of service specified in his or her current transportation agreement due to an involuntary, management-initiated action other than for unacceptable performance and/or misconduct; </P>
                                    <P>(ii) An employee, who has completed more than one year of service under a current agreement, released from a transportation agreement for compelling humanitarian or compassionate reasons; and </P>
                                    <P>(iii) A non-displaced overseas employee under no obligation to return to the United States who is otherwise eligible for PPP registration in accordance with DoD Instruction 1400.20; </P>
                                    <P>(6) When an employee declines an offer to transfer with his or her function to a location outside the commuting area, or is identified with such function but does not receive an offer at the gaining activity, and is placed in a position in a lower pay band at the losing activity or any other DoD activity; </P>
                                    <P>(7) When an employee accepts a position in a lower pay band offered by an activity to accommodate a disabling medical condition similar to the circumstances described in 5 CFR 831.1203(a)(4); </P>
                                    <P>(8) When an employee occupying a position under a Schedule C appointment (authorized under 5 CFR 213.3301) is placed, other than for unacceptable performance and/or misconduct or at the employee's request, in a position in a lower pay band in the competitive service or in another Schedule C position, provided that such action is not solely the result of a change in agency leadership (change in administration); </P>
                                    <P>(9) When an employee occupying an Army or Air Force dual status military technician position lost, or is scheduled to lose, eligibility for dual status technician employment through no fault of his or her own and accepts placement without a break in service to a non-dual status technician position in a lower pay band; </P>
                                    <P>(10) When an employee occupying a National Guard dual status technician position is involuntarily separated, through no fault of his or her own, and accepts placement, without a break in service, to a non-dual or dual status technician position in a lower pay band or a competitive service NSPS position in a lower pay band; </P>
                                    <P>(11) When an employee whose job is abolished declines an offer within the competitive area, but outside the commuting area, and is placed in a lower pay band position in the commuting area, provided the employee is not serving under a mobility agreement; </P>
                                    <P>(12) When an employee's base salary is reduced as the result of the movement of his or her position from a DoD nonappropriated fund (NAF) instrumentality to coverage by the DoD civil service system without a break in service of more than three days; or </P>
                                    <P>(13) When an employee's base salary would exceed the maximum of the rate range because the maximum of the rate range decreased or as a result of a management-directed reassignment. </P>
                                    <P>
                                        (e) An authorized management official may grant pay retention for circumstances other than those detailed in paragraphs (d)(1) through (d)(13) of this section. This determination is discretionary, and appropriate use is subject to higher-level approval. At a 
                                        <PRTPAGE P="56410"/>
                                        minimum, the higher-level approval may be no lower than one level above the authorized management official who recommended the determination. These circumstances may be specified in advance or may be approved on a case-by-case basis. This authority applies to personnel actions initiated by management, not at the employee's request, and other than for unacceptable performance and/or misconduct, and only if those actions would further the agency's mission in accordance with applicable law and regulation. 
                                    </P>
                                    <P>(f) Pay retention under this authority will terminate—</P>
                                    <P>(1) At the end of the 104-week period (except as otherwise provided under paragraphs (c) and (m) of this section); </P>
                                    <P>(2) When the employee moves to another position with a rate range that encompasses the employee's retained rate; </P>
                                    <P>(3) When an increase in the maximum rate for the employee's pay band causes the maximum rate to equal or exceed his/her retained rate, or the employee's base salary is encompassed within his or her assigned rate range as a result of a pay reduction based on unacceptable performance and/or conduct, subject to adverse action procedures; </P>
                                    <P>(4) When the employee is no longer covered by an NSPS position or has a break in service of 1 workday or more (which includes employees placed via PPP after separation), unless otherwise covered under another section of this regulation; </P>
                                    <P>(5) When the employee is reduced in band for unacceptable performance and/or conduct; or </P>
                                    <P>(6) When the employee is reduced in band at his or her request in circumstances other than stated in paragraph (d) of this section. </P>
                                    <P>(g) An employee whose pay retention terminates at the end of the 104-week period will have his or her pay set at the maximum rate of the pay band in which he/she is currently assigned. </P>
                                    <P>(h) Upon termination of pay retention, the employee immediately becomes eligible for any applicable general salary increase and performance payout which may include an increase to base salary, unless otherwise ineligible. </P>
                                    <P>(i) Pay retention does not apply in the following circumstances: </P>
                                    <P>(1) Declination of a position offer under RIF procedures set forth in 5 CFR part 351; </P>
                                    <P>(2) Break in service of 1 workday or more (which includes employees placed via PPP after separation), unless otherwise covered under paragraph (d) of this section; </P>
                                    <P>(3) Movement from a non-DoD position to an NSPS-covered position; </P>
                                    <P>(4) Failure to satisfactorily complete a supervisory probationary period; </P>
                                    <P>(5) Return to an employee's former position at the end of a temporary promotion or temporary reassignment; </P>
                                    <P>(6) Reassignment or reduction in band for unacceptable performance and/or conduct; or </P>
                                    <P>(7) Reassignment or reduction in band at the employee's request in circumstances other than stated in paragraph (d) of this section. </P>
                                    <P>(j) Employees entitled to a retained rate will receive any performance payouts in the form of bonuses, rather than base salary adjustments, as provided in § 9901.342(g)(8). </P>
                                    <P>(k) An employee receiving a retained rate will receive any general salary increase under § 9901.323(a)(1), subject to the conditions in § 9901.323, and will receive any applicable local market supplement adjustment, subject to the conditions in § 9901.334. </P>
                                    <P>(l) The 104-week time limit established under paragraphs (c) and (f)(1) of this section will be extended by a period of time equal to the length of time an employee is deployed away from his or her regular duty station in support of a contingency operation as defined in 10 U.S.C. 101, or an emergency as determined in accordance with DoD Directive 1400.31, “DoD Civilian Work Force Contingency and Emergency Planning and Execution” (or any successor regulation). </P>
                                    <P>(m) Any employee with a preexisting entitlement to pay retention under 5 CFR part 536 immediately before becoming covered by NSPS through a management-directed action, or who obtains entitlement to pay retention upon becoming covered by NSPS through a management-directed action, will be entitled to a retained rate under this section without regard to the 104-week limit (as described in paragraphs (c) and (f)(1) of this section). Pay retention will terminate under the conditions in paragraphs (f)(2) through (f)(6) of this section. </P>
                                    <HD SOURCE="HD1">Premium Pay </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.361 </SECTNO>
                                    <SUBJECT>General provisions. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Introduction</E>
                                        . As provided in § 9901.303(a)(2), the provisions of 5 U.S.C. chapter 55, subchapter V, and related regulations are waived or modified as provided in paragraph (e) of this section and §§ 9901.362 through 9901.364 (except as provided in paragraph (b) of this section). To the extent that the provisions of 5 U.S.C. chapter 55, subchapter V, and related regulations are not waived or modified, NSPS employees and positions remain subject to those provisions. Sections 9901.363 and 9901.364 establish new types of premium payments in addition to those found in 5 U.S.C. chapter 55, subchapter V. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Provisions not waived or modified</E>
                                        . The following provisions of 5 U.S.C. chapter 55, subchapter V, are not waived or modified: 
                                    </P>
                                    <P>(1) 5 U.S.C. 5544 (relating to prevailing rate employees); and </P>
                                    <P>(2) 5 U.S.C. 5545b (relating to firefighter pay). </P>
                                    <P>
                                        (c) 
                                        <E T="03">Applicability of Fair Labor Standards Act</E>
                                        . The Fair Labor Standards Act of 1938 (FLSA), as amended (29 U.S.C. 201 et seq.) and OPM regulations in 5 CFR part 551 apply to NSPS employees. DoD must determine whether an employee is exempt or nonexempt under the FLSA minimum wage and overtime pay provisions in accordance with the FLSA and OPM regulations. In applying FLSA overtime pay provisions, local market supplements are treated the same as locality pay under 5 U.S.C. 5304 and are included in computing total remuneration, the hourly regular rate, and straight time rate under 5 CFR part 551. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Applying regulations in 5 CFR part 550, subpart M</E>
                                        . In applying the regulations in 5 CFR part 550, subpart M (dealing with firefighter pay) to NSPS employees, the reference to “locality pay” in 5 CFR 550.1305(e) must be interpreted to be a reference to a local market supplement. Consistent with 5 CFR 550.1306(a), a firefighter compensated under 5 CFR part 550, subpart M, may not receive additional premium pay except for compensatory time off for travel under § 9901.362(j) or for religious observances under § 9901.362(k) and foreign language proficiency pay under § 9901.364. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Physicians and dentists</E>
                                        . Physicians and dentists (in occupational series 0602 and 0680, respectively) under NSPS are not eligible for premium pay except for compensatory time off for religious observances under § 9901.362(k). 
                                    </P>
                                    <P>
                                        (f) 
                                        <E T="03">Senior Executive Service</E>
                                        . Members of the Senior Executive Service under NSPS are not eligible for premium pay, except for compensatory time off for religious observances under § 9901.362(k). 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.362 </SECTNO>
                                    <SUBJECT>Modification of standard provisions. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Premium pay limitations</E>
                                        . (1) An employee is covered by the premium pay limitations established under 5 U.S.C. 5547 and related regulations, except as provided in paragraph (a)(2) of this section. Notwithstanding the modification of various premium 
                                        <PRTPAGE P="56411"/>
                                        payments under this section, those payments are still considered to be payments in 5 U.S.C. chapter 55, subchapter V, for the purpose of applying 5 U.S.C. 5547 (including the purpose of determining the covered premium payments under 5 U.S.C. 5547(a)). 
                                    </P>
                                    <P>(2) Subject to § 9901.105, the Secretary may waive the limitations established by 5 U.S.C. 5547 and related regulations and instead apply an annual limitation equal to the rate payable under 3 U.S.C. 104 in the case of specified categories of employees and situations on a time-limited basis. Such a waiver may not apply with respect to additional compensation that is normally creditable as basic pay for retirement or any other purpose. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Overtime pay</E>
                                        . (1) An employee is covered by the overtime pay (including compensatory time off) provisions in 5 U.S.C. 5542 and 5543 and related regulations, subject to the requirements and modifications described in paragraphs (b)(2) through (b)(6) of this section. 
                                    </P>
                                    <P>(2) Consistent with 5 U.S.C. 5542(c), an employee who is subject to section 7 of the Fair Labor Standards Act of 1938 (FLSA), as amended, is covered by OPM's FLSA overtime regulations in 5 CFR part 551. </P>
                                    <P>(3) Compensation for irregular or overtime work performed by National Guard Technicians is governed by 32 U.S.C. 709(h) and policies issued by the National Guard Bureau. </P>
                                    <P>(4) Firefighters covered by 5 U.S.C. 5545b are subject to special overtime pay rules as described in that section and in 5 U.S.C. 5542(f) and in related regulations. (See also § 9901.361(d).) </P>
                                    <P>(5) Compensatory time off earned under 5 U.S.C. 5543 must be used by the end of the 26th pay period after that in which it was earned. Compensatory time off not used within 26 pay periods will be paid at the overtime rate at which it was earned. Employees with unused compensatory time earned before June 8, 1997 (January 5, 1997, for Defense Logistics Agency employees), have had a separate “old compensatory time” account established for their use. Old compensatory time is charged only if the employee has insufficient current compensatory time (earned on or after June 8, 1997) to cover the compensatory time off requested. Within each category of compensatory time, the oldest will be charged first. When a DoD employee separates, moves to another Component, or transfers to another Federal agency, any unused compensatory time off balance will be paid at the overtime rate at which it was earned. Also, when an employee moves to a pay system that does not provide for compensatory time off (e.g., Senior Executive Service), any unused compensatory time off balance will be paid at the overtime rate at which it was earned. </P>
                                    <P>(6) The following modifications to 5 U.S.C. 5542 and 5543 and related regulations apply: </P>
                                    <P>(i) The overtime hourly rate cap for FLSA-exempt employees based on the rate of basic pay for the minimum rate for GS-10 does not apply; instead, an FLSA-exempt employee is entitled to an overtime hourly rate equal to 1.5 times the employee's adjusted salary hourly rate unless the employee is in a pay band for which the overtime hourly rate is set equal to the employee's adjusted salary hourly rate based on a determination by the Secretary, subject to § 9901.105; </P>
                                    <P>(ii) An FLSA-exempt employee will be compensated for overtime work (whether regular or irregular or occasional) using a quarter of an hour as the smallest fraction of an hour, with minutes rounded to the nearest full fraction of an hour; </P>
                                    <P>(iii) An FLSA-exempt employee may not be credited with overtime hours of work for travel time unless that travel involves the performance of actual work while traveling; instead, any such noncreditable travel hours may be credited as earned compensatory time off for travel, subject to the requirements in paragraph (j) of this section; and </P>
                                    <P>(iv) An FLSA-exempt employee may be required to receive compensatory time off under 5 U.S.C. 5543 in lieu of overtime pay, regardless of the type of overtime work or the amount of the employee's adjusted salary rate. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Night pay</E>
                                        . An employee is covered by the night pay provisions in 5 U.S.C. 5545(a) and (b) and related regulations, except for the following modifications: 
                                    </P>
                                    <P>(1) Night pay is payable for irregular or occasional overtime work in the same manner it is payable for regularly scheduled work; and </P>
                                    <P>(2) Night pay is not payable during paid absences, except for a period of court leave, military leave, time off awarded under 5 U.S.C. 4502(e), or compensatory time off during religious observances, or when excused from duty on a holiday. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Sunday pay</E>
                                        . An employee is covered by the Sunday pay provisions in 5 U.S.C. 5546 and related regulations, except for the following modifications: 
                                    </P>
                                    <P>(1) Work for which Sunday pay is payable (i.e., Sunday work) is limited to applicable hours of work that are actually performed on Sunday (i.e., the definition of “Sunday work” in 5 CFR 550.103 applies except that non-Sunday hours are excluded even if those hours are within a daily tour of duty that includes Sunday hours); and </P>
                                    <P>(2) Consistent with section 624 of the Treasury and General Government Appropriations Act, 1999 (as found in section 101(h) of Division A of Public Law 105-277, October 21, 1998), Sunday pay is not payable unless an employee actually performed work during the time corresponding to such pay (i.e., no Sunday pay for periods of paid leave, compensatory time off, credit hours, paid excused absence, or other paid time off). </P>
                                    <P>
                                        (e) 
                                        <E T="03">Pay for holiday work</E>
                                        . An employee is covered by the holiday premium pay provisions in 5 U.S.C. 5546 and related regulations, except for the following modifications: 
                                    </P>
                                    <P>(1) Holiday premium pay is paid at twice an employee's adjusted salary hourly rate for each hour (including overtime hours) an employee is ordered or approved to work on a holiday; </P>
                                    <P>(2) For FLSA-exempt employees, the payment for overtime hours worked on a holiday has two components: Payment required under paragraph (b) of this section for overtime worked, and an additional amount under this paragraph (e) such that the total payment for each hour is twice the employee's adjusted salary hourly rate; and </P>
                                    <P>(3) For FLSA-nonexempt employees, the payment for overtime hours worked on a holiday has two components: Payment required under 5 CFR 551.512 for overtime worked, and an additional amount under this paragraph (e) such that the total payment for each hour is twice the employee's adjusted salary hourly rate. </P>
                                    <P>
                                        (f) 
                                        <E T="03">Standby duty pay</E>
                                        . (1) An employee is covered by the standby duty pay provisions in 5 U.S.C. 5545 (c)(1) and related regulations, subject to the requirements and modifications in paragraphs (f)(2) through (f)(6) of this section. 
                                    </P>
                                    <P>(2) Except as provided in paragraph (f)(3), eligibility for regularly scheduled standby duty is limited to firefighters classified to the 0081 occupation who are not eligible for coverage under 5 U.S.C. 5545b, and to emergency medical technicians not involved in fire protection activities who are required to perform standby duty. </P>
                                    <P>
                                        (3) The Secretary may approve extending standby duty premium pay coverage to occupations other than those cited in paragraph (f)(2) of this section. Component proposals to extend coverage will explain why employees within the specified occupational group must regularly remain at the duty station longer than ordinary periods of duty, a substantial part of which involves remaining in a standby status 
                                        <PRTPAGE P="56412"/>
                                        rather than performing actual work, and must address how the criteria in 5 CFR 550.143 are met. 
                                    </P>
                                    <P>(4) The standby percentage is always multiplied by an employee's adjusted salary rate regardless of the amount. </P>
                                    <P>(5) Standby pay attributable to use of an adjusted salary rate exceeding the applicable GS-10, step 1, rate limitation is not considered to be paid under 5 U.S.C. 5545(c)(1) and thus is not creditable basic pay for retirement purposes. </P>
                                    <P>(6) No additional premium pay for hours of overtime work (whether regularly scheduled or irregular or occasional), including compensatory time off, is payable to an employee receiving standby duty pay. </P>
                                    <P>
                                        (g) 
                                        <E T="03">Administratively uncontrollable overtime pay</E>
                                        . The administratively uncontrollable overtime pay provision in 5 U.S.C. 5545(c)(2) is waived and will not be applied to NSPS employees. Compensation for such work will be made under the applicable provisions of this section. 
                                    </P>
                                    <P>
                                        (h) 
                                        <E T="03">Law enforcement availability pay</E>
                                        . An employee is covered by the law enforcement availability pay provisions in 5 U.S.C. 5545a and related regulations, except that the reference to “premium pay” in 5 CFR 550.186 will be interpreted to refer to the applicable title 5 premium payments and to the corresponding modified provisions in this section. In addition, the reference to “limitation on premium pay” in 5 CFR 550.185(a)(2) will be construed to refer to the limitations under 5 U.S.C. 5547 and to the corresponding modified provision in paragraph (a) of this section. 
                                    </P>
                                    <P>
                                        (i) 
                                        <E T="03">Pay for duty involving physical hardship or hazard</E>
                                        . (1) An employee is covered by the hazardous duty pay provisions in 5 U.S.C. 5545(d) and related regulations, subject to the requirements and modifications described in paragraphs (i)(2) through (i)(6) of this section. 
                                    </P>
                                    <P>(2) In determining eligibility for hazardous duty pay, an authorized management official will apply occupational safety and health standards consistent with the permissible exposure limit promulgated by the Secretary of Labor under the Occupational Safety and Health Act of 1970 as published in Subtitle B, Chapter XVII, of title 29, United States Code, or, in the absence of a permissible exposure limit issued by the Secretary of Labor, other applicable standard promulgated by the Secretary. </P>
                                    <P>(3) Subject to § 9901.105, the Secretary may establish new categories of hazardous duty pay in addition to those found in Appendix A to subpart I of 5 CFR part 550. Components may request a new category of hazardous duty pay be established and must submit, with their request, the information required in 5 CFR 550.903(b). </P>
                                    <P>(4) Except as provided in paragraphs (i)(5) and (i)(6) of this section, an employee is paid a hazard pay differential when he or she is assigned to and performs a duty specified in Appendix A to subpart I of 5 CFR part 550 or as provided under paragraph (i)(3) of this section. </P>
                                    <P>(5) An employee will be eligible to receive hazardous duty pay when an authorized management official determines—</P>
                                    <P>(i) One or more of the conditions requisite for such payment exist; and </P>
                                    <P>(ii) Safety precautions, protective or mechanical devices, protective or safety clothing, protective or safety equipment, or other preventive measures have not reduced the element of hazard below the permissible exposure limits promulgated by the Secretary of Labor or any applicable standard promulgated by the Secretary, consistent with paragraph (i)(2) of this section. </P>
                                    <P>(6) Hazard pay differentials are not payable to employees in occupations or jobs in which unusual physical risk is an inherent characteristic of the occupation or job, such as police officer, emergency medical technician, test pilot, ordnance/explosives/incendiary inspector, and engineering technician performing inspection functions inside fuel storage tanks, tunnels, or shafts. The classification of the employee's position (i.e., determination of pay band level) includes a consideration of the hazardous duty or physical hardship. For the purposes of this paragraph, the phrase “includes a consideration of the hazardous duty” means that the duty is one element considered in determining the pay band level of the position—i.e., the knowledge, complexities, skills and abilities required to perform that duty are considered in the classification of the position. Such consideration does not require the hazardous duty or physical hardship to be pay band controlling. </P>
                                    <P>
                                        (j) 
                                        <E T="03">Compensatory time off for travel</E>
                                        . (1) An employee is covered by the compensatory time off for travel provisions in 5 U.S.C. 5550b and related regulations, subject to the requirements and modifications described in paragraphs (j)(2) through (j)(7) of this section. 
                                    </P>
                                    <P>(2) The term “official duty station” as defined in the related regulations is not applicable; instead, the term “official worksite” is used to determine an employee's entitlement to compensatory time off for travel. The term “official worksite” has the meaning given in 5 CFR 531.605. </P>
                                    <P>(3)(i) Time spent commuting between an employee's residence and the workplace (official or temporary worksite) is not creditable for the purpose of compensatory time off for travel, except as provided in paragraph (j)(3)(ii) of this section. </P>
                                    <P>(ii) If an employee is required to travel to a temporary worksite and if the one-way commuting time exceeds the employee's normal one-way commuting time by more than 1 hour, the commuting time beyond 1 hour may be credited. </P>
                                    <P>(4) If an employee is required to travel directly between his or her residence and a transportation terminal, the travel time is creditable as time in a travel status. The travel time outside regular working hours directly to or from a transportation terminal is creditable as time in a travel status. However, if the travel occurs on a day that the employee is regularly scheduled to work, the time the employee would have spent in normal home-to-work or work-to-home commuting must be deducted. </P>
                                    <P>(5) An employee earns compensatory time off for time spent in a travel status away from the official worksite when such time is not otherwise compensable. </P>
                                    <P>(6) Employees must file requests for credit of compensatory time off for travel within 10 workdays after returning to the official duty station, or within 10 workdays of returning from temporary duty (TDY) assignment or approved leave which immediately follows the TDY during which the compensatory time off for travel was earned, by submitting a travel itinerary, or any other documentation acceptable to the employee's supervisor, in support of the request. If not submitted within 10 workdays, the employee will forfeit his or her claim to the compensatory time off for travel. Compensatory time off for travel will be credited in increments of 6 minutes or 15 minutes and will be tracked and managed separately from other forms of compensatory time off. </P>
                                    <P>
                                        (7)(i) When an employee moves from an NSPS position to a non-NSPS position within the Department, in which the employee will be eligible for compensatory time off for travel under 5 CFR part 550, subpart N, he or she will retain unused compensatory time off for travel. The time elapsed from the end of the pay period in which the compensatory time off was earned through the date of conversion will count as elapsed time in applying the limit for usage in 5 CFR part 550, subpart N. 
                                        <PRTPAGE P="56413"/>
                                    </P>
                                    <P>(ii) When an employee moves from a non-NSPS position to an NSPS position within the Department, he or she will retain unused compensatory time off for travel. The time elapsed from the end of the pay period in which the compensatory time off was earned through the date of conversion will count as elapsed time in applying the limit for usage established under 5 CFR 550.1407. </P>
                                    <P>
                                        (k) 
                                        <E T="03">Compensatory time off for religious observances</E>
                                        . An employee is covered by the compensatory time off for religious observances provisions in 5 U.S.C. 5550a and related regulations, subject to the following requirements and modifications: 
                                    </P>
                                    <P>(1) An employee's request for time off should not be granted without simultaneously scheduling the hours during which the employee will work to make up the time (unless the employee earned the needed hours in advance); and </P>
                                    <P>(2) An employee may not receive payment for any unused compensatory time off for religious observances under any circumstances. This prohibition against payment applies to surviving beneficiaries in the event of the individual's death. </P>
                                    <P>
                                        (l) 
                                        <E T="03">Air traffic controller differential</E>
                                        . (1) The air traffic controller differential provisions in 5 U.S.C. 5546a are waived and not applicable to NSPS employees, except for subsections (a)(1) and (d) of that section. 
                                    </P>
                                    <P>(2) An employee is covered by the air traffic controller differential provisions in subsections (a)(1) and (d) of 5 U.S.C. 5546a, subject to the modification described in paragraph (1)(3) of this section. </P>
                                    <P>(3) The reference to the grade levels of GS-9 and GS-11 in 5 U.S.C. 5546a(a)(1) must be construed to mean a comparable level of work as determined under the NSPS classification structure. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.363 </SECTNO>
                                    <SUBJECT>Premium pay for health care personnel. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Coverage</E>
                                        . (1) This section applies to DoD health care personnel covered under NSPS who may be eligible for premium pay, as described in paragraphs (b), (c), and (d) of this section. For the purpose of this section, 
                                        <E T="03">health care personnel</E>
                                         means employees providing direct patient care services or services incident to direct patient care services. Examples include employees in the following occupations: nurse, biomedical engineer, dietitian, dental hygienist, psychologist, and medical records technician. 
                                    </P>
                                    <P>(2) Premium pay under this section is not considered part of basic pay for any purpose, nor is it used in computing a lump-sum payment for leave under 5 U.S.C. 5551 or 5552. </P>
                                    <P>
                                        (b) 
                                        <E T="03">On-call premium pay</E>
                                        . (1) When health care personnel are not otherwise compensated for on-call time, heads of Components may authorize on-call premium pay under this section for officially scheduled “on-call” time which requires these employees to restrict their activities sufficiently to be available to return to the worksite promptly when it is necessary. 
                                    </P>
                                    <P>(2) To be paid on-call premium pay, an employee must be officially scheduled to be on-call outside his or her regular duty hours or during hours on a holiday when the employee is excused from regular duty. </P>
                                    <P>(3) An employee may not be scheduled to be on-call unless it is essential for the employee to be immediately available to return to the worksite. </P>
                                    <P>(4) An employee officially scheduled to be on-call will be paid 15 percent of his or her adjusted salary hourly rate for each hour of on-call status. </P>
                                    <P>(5) An employee may not receive on-call pay during periods of actual work. When an employee on-call is required to return to work status, on-call pay will be suspended. When released from the requirement to perform actual work, the employee will return to the remaining scheduled on-call status. </P>
                                    <P>(6) An employee may not be charged leave during periods of regularly scheduled on-call duty; nor may such an employee receive on-call premium pay when, because of leave or other authorized absence, the employee is not expected to be able to return to the worksite immediately. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Night pay for health care personnel</E>
                                        . (1) Health care personnel working a tour of duty, any part of which falls between 6 p.m. and 6 a.m., with 4 or more hours falling between 6 p.m. and 6 a.m., will be paid additional pay for each hour of work on such tour. When fewer than 4 hours of work fall between 6 p.m. and 6 a.m., health care personnel will be paid additional pay for each hour of work performed between 6 p.m. and 6 a.m. Night pay for health care personnel is 10 percent of the employee's hourly rate of adjusted salary. An employee receiving night pay under this section may not also receive night pay under § 9901.362(c). 
                                    </P>
                                    <P>(2) Health care personnel are entitled to pay for night duty for a period of paid absence only for a period of court leave, military leave, time off awards under 5 U.S.C. 4502(e), or compensatory time off for religious observances. </P>
                                    <P>(3) When excused from work because of a holiday or in-lieu-of holiday, health care personnel are entitled to the night pay that would have applied had they not been excused from work. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Pay for weekend duty for health care personnel</E>
                                        . (1) Health care personnel who work a tour of duty, any part of which falls in the 2-day period between midnight Friday and midnight Sunday, will be paid additional pay for each hour of work during such tour. Health care personnel who have two separate tours of duty, each of which qualify as weekend duty, will be paid additional pay for each hour of both tours. Additional pay for weekend duty is 25 percent of the employee's hourly rate of adjusted salary. An employee receiving pay for weekend duty may not also receive pay for Sunday work under § 9901.362(d). 
                                    </P>
                                    <P>(2) When on court leave, military leave, time off awarded under 5 U.S.C. 4502(e), or compensatory time off for religious observances, health care personnel are entitled to pay for weekend duty they otherwise would have received. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.364 </SECTNO>
                                    <SUBJECT>Foreign language proficiency pay. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General provisions</E>
                                        . (1) This section applies to employees who may be paid Foreign Language Proficiency Pay (FLPP) if they are certified as proficient in a foreign language the Secretary has determined to be necessary for national security interests, and if they are not receiving FLPP as provided in 10 U.S.C. 1596 and 10 U.S.C. 1596a. 
                                    </P>
                                    <P>(2) The Secretary is authorized to publish an annual list of foreign languages necessary for national security interests and to establish overall policy for administration of the Defense Language Program. </P>
                                    <P>(3) Employees may be certified as proficient in a necessary foreign language using criteria and procedures established by the Secretary and receive FLPP. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Eligibility Criteria.</E>
                                         An authorized management official delegated the authority for approving payment must document that an employee meets eligibility criteria before authorizing FLPP. The documentation includes—
                                    </P>
                                    <P>(1) Certification within the last 12 months of the employee's proficiency in a foreign language the Secretary has determined necessary for national security interests; </P>
                                    <P>(2) Affirmation that the employee does not currently receive comparable pay under 10 U.S.C. 1596 or 1596a; </P>
                                    <P>
                                        (3) Certification of the employee's foreign language proficiency level renewed annually; and 
                                        <PRTPAGE P="56414"/>
                                    </P>
                                    <P>(4) Certification based on an annual test that is part of the Defense Language Proficiency Test System. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Amount and method of payment.</E>
                                         The decision to grant FLPP, including the amount, will be reviewed and approved by an official who is at a higher level than the official who made the initial decision, as determined by the Component, unless there is no official at a higher level in the organization. The amount of FLPP received by the employee, not to exceed $500 per pay period, will be determined based on the following considerations: 
                                    </P>
                                    <P>(1) The employee's measured proficiency level in the necessary language; </P>
                                    <P>(2) The need for the employee's particular language skills; </P>
                                    <P>(3) The difficulty of recruiting or retaining employees with the same proficiencies; </P>
                                    <P>(4) The extent to which the employee performs tasks requiring proficiency; </P>
                                    <P>(5) The number of necessary languages in which the employee is proficient; and </P>
                                    <P>(6) Other considerations authorized by the Secretary. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Treatment for other purposes.</E>
                                         FLPP is not considered part of basic pay for any purpose and does not count towards retirement, insurance, or any other benefit related to basic pay. FLPP is not pay for purposes of a lump-sum payment for leave under 5 U.S.C. 5551 or 5552. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Termination.</E>
                                         The authorized management official as determined by the Component may reduce or terminate FLPP at any time when the official determines—
                                    </P>
                                    <P>(1) The need for the employee's language capability has been reduced or eliminated; or </P>
                                    <P>(2) The employee no longer meets the certification requirements. </P>
                                    <P>
                                        (f) 
                                        <E T="03">Miscellaneous.</E>
                                         (1) The minimum qualifying level may not be less than Interagency Language Roundtable Level 2 proficiency in at least two skills (listening, reading, speaking, or writing, as required). 
                                    </P>
                                    <P>(2) FLPP may be paid for proficiency in multiple languages; however, the total amount may not exceed $500 per pay period. </P>
                                    <HD SOURCE="HD1">Conversion Provisions </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.371 </SECTNO>
                                    <SUBJECT>Conversion into NSPS pay system. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Introduction.</E>
                                         This section describes the pay-setting provisions that apply when DoD employees are converted into the NSPS pay system established under this subpart. (See § 9901.231 for conversion rules related to determining an employee's career group, pay schedule, and band.) An affected employee may convert from the GS system, the SL/ST system, or the SES system (or such other systems designated by the Secretary as DoD may be authorized to include under 5 U.S.C. 9902), as provided in § 9901.302. For the purpose of this part (except § 9901.372), the terms “convert,” “converted,” “converting,” and “conversion” refer to employees who become covered by the NSPS pay system without a change in position (as a result of a coverage determination made under § 9901.102(b)) and exclude employees who move from a noncovered position to a position already covered by the NSPS pay system. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Implementing issuances.</E>
                                         The Secretary will issue implementing issuances prescribing the policies and procedures necessary to implement these conversion provisions. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Bar on pay reduction.</E>
                                         Subject to paragraph (e) of this section, employees will be converted into the NSPS pay system without a reduction in their adjusted salary rate. (As defined in § 9901.304, the term “adjusted salary” means base salary plus any applicable locality payment under 5 U.S.C. 5304, special rate supplement under 5 U.S.C. 5305, local market supplement under § 9901.332, or equivalent supplement under other legal authority.) 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Rate comparison.</E>
                                         For the purpose of determining whether conversion into NSPS constitutes an adverse action for reduction of pay under 5 U.S.C. chapter 75, subchapter II (dealing with adverse actions), an employee's rate of basic pay includes any applicable locality payment under 5 U.S.C. 5304, special rate supplement under 5 U.S.C. 5305, local market supplement under § 9901.332, or equivalent supplement under other legal authority. The rate of basic pay immediately before conversion must be adjusted as described in paragraph (e) of this section before comparing that rate of basic pay to the initial NSPS rate of basic pay. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Simultaneous actions.</E>
                                         If another personnel action (e.g., promotion, geographic movement) takes effect on the same day as the effective date of an employee's conversion to the new pay system, the other action will be processed under the rules pertaining to the employee's former system before processing the conversion action. 
                                    </P>
                                    <P>
                                        (f) 
                                        <E T="03">Temporary promotion prior to conversion.</E>
                                         An employee on a temporary promotion at the time of conversion will be returned to his or her official position of record prior to processing the conversion (as provided in § 9901.231(c)), and pay will be set consistent with the pay-setting rules of the pay system that applies prior to conversion. For GS employees, pay in the permanent position of record must be reconstructed to reflect any increase that would have otherwise occurred if the employee had not been temporarily promoted, as provided in GS pay-setting regulations. If the employee is temporarily promoted immediately after the conversion, pay will be set under the rules for promotion increases under the NSPS pay system. (See also paragraph (k) of this section.) 
                                    </P>
                                    <P>
                                        (g) 
                                        <E T="03">Grade retention prior to conversion.</E>
                                         An employee on grade retention immediately before conversion must be converted to a pay band based on the grade of his or her assigned permanent position of record (not the retained grade), as provided in § 9901.231(d), but the employee's base and adjusted salary while in grade retention status will be used in applying this section (e.g., in setting the initial NSPS base and adjusted salary and in determining the amount of any within-grade increase adjustment). After conversion and any within-grade increase adjustment under paragraph (j) of this section, if the employee's base salary exceeds the rate range for the assigned pay band, the employee will be granted pay retention, subject to the conditions described in § 9901.356. 
                                    </P>
                                    <P>
                                        (h) 
                                        <E T="03">Pay retention prior to conversion.</E>
                                         For an employee on pay retention under 5 U.S.C. 5363 immediately before conversion, the employee's pay will be realigned so that the employee's NSPS adjusted salary (consisting of base salary plus any applicable local market supplement) equals the employee's retained rate before conversion. If the employee's base salary (after realignment) exceeds the rate range for the assigned pay band, the employee will be granted pay retention, subject to the conditions described in § 9901.356. 
                                    </P>
                                    <P>
                                        (i) 
                                        <E T="03">Conversion adjustments.</E>
                                         The only NSPS base salary adjustments that may be made in conjunction with an employee's conversion into NSPS are those identified in paragraphs (j) through (m) of this section. 
                                    </P>
                                    <P>
                                        (j) 
                                        <E T="03">Within-grade increase (WGI) adjustment.</E>
                                         (1) Upon conversion to NSPS, a General Schedule (GS) employee (regardless of work schedule) who would otherwise be eligible for a within-grade increase (WGI), and who is paid below the maximum rate for their grade, will receive a prorated WGI adjustment to his or her NSPS base salary rate to account for the time (measured in calendar days) since the employee's last equivalent pay increase. 
                                        <PRTPAGE P="56415"/>
                                    </P>
                                    <P>(2) The WGI adjustment is calculated based on the number of calendar days between the effective date of the employee's last equivalent increase and the date of conversion into NSPS, regardless of the number of days in a non-pay status (if any). The maximum adjustment may not exceed a full WGI. </P>
                                    <P>(3) For an employee on a temporary promotion immediately before conversion, the employee's GS pay entitlements must be determined as provided in paragraph (f) of this section before calculating the WGI adjustment. </P>
                                    <P>(4) For an employee entitled to grade retention immediately before conversion, the WGI adjustment is determined using the employee's retained grade and step. </P>
                                    <P>(5) The WGI adjustment is not applicable to an employee entitled to pay retention immediately before conversion. </P>
                                    <P>(6) The WGI adjustment is not applicable to an employee whose performance has been determined to be below an acceptable level of competence under 5 CFR part 531, subpart D. </P>
                                    <P>(7) An employee is entitled to a WGI adjustment in accordance with paragraphs (j)(1) through (6) of this section each time he or she occupies a position that is converted into NSPS under this part. </P>
                                    <P>
                                        (k) 
                                        <E T="03">Special increase for employees on temporary promotion prior to conversion</E>
                                        —(1) 
                                        <E T="03">General.</E>
                                         If an employee had a temporary promotion immediately before conversion, and if the position to which the employee was temporarily promoted becomes covered by NSPS, an authorized management official may temporarily reassign or temporarily promote the employee back to that position, subject to the same terms and conditions as the initial temporary promotion (e.g., if the temporary promotion was not to exceed 5 years and the action is a temporary reassignment under NSPS, the temporary reassignment may not exceed 5 years). When the employee is temporarily placed back into the position immediately after conversion, the pay-setting rules in paragraphs (k)(2) and (k)(3) of this section apply. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Temporary reassignment.</E>
                                         If the post-conversion action would be a temporary reassignment, the authorized management official may provide the employee with a temporary base salary increase up to the same base salary rate the employee was receiving during the temporary promotion (prior to conversion) in lieu of setting pay under the reassignment rules under § 9901.353. This is a one-time exception to the limitations on reassignment increases imposed under § 9901.353. Upon expiration of the temporary reassignment, pay will be set as specified in § 9901.353(g) or paragraph (k)(4) of this section, as applicable. 
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Temporary promotion.</E>
                                         (i) If the post-conversion action would be a temporary promotion, the authorized management official may provide the employee with a temporary base salary increase up to the same base salary rate the employee was receiving during the temporary promotion (prior to conversion) or may set pay according to the promotion rules under § 9901.354 to provide a greater increase. Upon expiration of the temporary promotion, pay will be set as specified in § 9901.354(c) or paragraph (k)(4) of this section, as applicable. 
                                    </P>
                                    <P>(ii) The increase described in paragraph (k)(3)(i) of this section may also apply to an employee who is on a temporary promotion at the time that temporary promotion position converts to NSPS, even if the employee's permanent position of record has not yet converted. In this case, upon expiration of the temporary promotion, pay will be set under the rules of the applicable pay system. </P>
                                    <P>
                                        (4) 
                                        <E T="03">Temporary placement becomes permanent.</E>
                                         If a temporary reassignment or promotion to an NSPS position under this paragraph (k) becomes permanent with no break, the employee's base salary will not change, but will continue at the rate received at the end of the temporary reassignment or promotion. 
                                    </P>
                                    <P>
                                        (l) 
                                        <E T="03">Special increases equivalent to GS promotion increase.</E>
                                         (1) During the first 12 months following conversion, employees who are not eligible for the Accelerated Compensation for Developmental Positions (ACDP) under § 9901.345 are eligible to receive (at the discretion of an authorized management official) a one-time base salary increase equivalent to a noncompetitive promotion increase the employee would have received but for conversion to NSPS. This paragraph may be applied only when the grade level of the promotion is encompassed within the same pay band, the employee's performance warrants the pay increase, and the promotion would have otherwise occurred during that period. 
                                    </P>
                                    <P>(2) An employee who is selected for a non-NSPS position that subsequently becomes covered by NSPS before the effective date of the employee's placement in the position is eligible to receive (at the discretion of an authorized management official) a one-time base salary increase equivalent to the increase the employee would have received had the placement been effected prior to the position becoming covered by NSPS. This paragraph may be applied only when the employee is not already in an NSPS-covered position on the effective date of the placement, and the effective date is within 12 months of the position becoming covered by NSPS. An employee who receives an increase under this paragraph is not eligible for the WGI adjustment described in paragraph (j) of this section. </P>
                                    <P>
                                        (m) 
                                        <E T="03">Adjustment for physicians and dentists.</E>
                                         For a GS physician or dentist who was regularly receiving a physicians' comparability allowance or premium pay, the Component may increase the base salary after conversion to NSPS to account for the loss of such allowance or premium pay (since such payments are not authorized for physicians and dentists under NSPS). The Component must also consider the additional pay represented by any applicable targeted local market supplement in determining the rate at which the base salary should be set under this paragraph. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.372 </SECTNO>
                                    <SUBJECT>Conversion or movement out of NSPS pay system. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         (1) This section applies to the conversion or movement of employees out of the NSPS pay system to a different pay system. Under this section, when an NSPS employee is converted or moved to a GS position, a GS virtual grade and rate is established for the NSPS employee so that the employee is treated as a GS employee in applying GS pay-setting rules. 
                                    </P>
                                    <P>(2) For the purpose of this section (unless otherwise specified)—</P>
                                    <P>(i) The terms “convert,” “converted,” “converting,” and “conversion” refer to NSPS employees who become covered by a different pay system without a change in position (as a result of a determination made by the Secretary under § 9901.102(e) or as otherwise provided by law); and </P>
                                    <P>(ii) The terms “move,” “moved,” “moving,” and “movement” refer to NSPS employees who become covered by a different pay system through a change in position, rather than by conversion. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Classification of converted position.</E>
                                         Prior to converting an employee out of NSPS, an authorized management official, as defined by the Component, will review the duties of the employee's current permanent position of record and classify the position's duties in accordance with Office of Personnel Management (OPM) classification guidance and/or other appropriate criteria to determine the appropriate title, series, and grade or pay band of the position in the new pay 
                                        <PRTPAGE P="56416"/>
                                        system. Employees occupying positions classified to NSPS-unique occupational series at the time of conversion out cannot be retained in those series, but must be assigned to the series that most closely represents the employee's current duties (i.e., the duties of the former NSPS position). 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Determining pay under new pay system.</E>
                                         When converting or moving an employee out of NSPS to another pay system, the pay-setting rules of the gaining system will apply. For the purpose of applying those rules, the employee's final pay under NSPS is determined based on the employee's NSPS permanent position of record (including band), official worksite, and pay as of the day immediately before the date of conversion or movement out of NSPS. An employee on a temporary reassignment or temporary promotion will be returned to his or her permanent position of record prior to conversion or movement. No personnel or pay action that, but for the conversion or movement out of NSPS, would have occurred under NSPS on the date of conversion or movement may be considered. Any personnel or pay action occurring on the date of conversion or movement must be processed under the rules of the gaining system. In the case of a conversion or movement to the General Schedule (GS) pay system, the supplemental rules in paragraph (d) of this section must be followed to determine a virtual GS grade and rate (as of the date before the employee's conversion or movement out of NSPS) that will be used in apply GS pay-setting rules. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Virtual GS grade and rate</E>
                                        —(1) 
                                        <E T="03">Virtual GS grade.</E>
                                         (i) Before an employee converts or moves out of NSPS under this paragraph, a virtual GS grade will be established for the purpose of applying GS pay-setting rules (e.g., a promotion increase if the actual GS grade is higher than the virtual GS grade). This virtual GS grade will be based on a comparison of the NSPS employee's current adjusted salary to the highest applicable GS rate range that would apply to the employee's NSPS permanent position of record considering only those GS grade levels and associated rate ranges that are included in the employee's assigned NSPS pay band. For the purpose of this section, a highest applicable GS rate range includes the following rate ranges: The GS locality rate schedule for the locality pay area in which the employee's NSPS official worksite is located; the special rate schedule based on the employee's position of record, official worksite, or other established conditions; the law enforcement officer special base rate schedule; or the GS base pay schedule. The grade-band conversion tables established in DoD's NSPS implementing issuances for the purpose of converting employees into NSPS must be used in determining which GS grades are covered by the employee's assigned NSPS pay band. For two-grade interval occupations, conversion may not be made to an intervening (even) grade level below GS-11. 
                                    </P>
                                    <P>(ii) If the employee's pay band covers one GS grade, the employee's virtual grade will be that grade. </P>
                                    <P>(iii) For an employee in a pay band encompassing more than one GS grade, if the employee's adjusted salary equals or exceeds the step 4 rate of the highest applicable GS rate range for the highest GS grade encompassed within his or her assigned NSPS pay band, the employee's virtual grade will be that grade. If the employee's adjusted salary is lower than the step 4 rate, the adjusted salary is compared with the step 4 rate of the highest applicable GS rate range for the second highest GS grade encompassed within the employee's pay band. If the employee's adjusted salary equals or exceeds the step 4 rate of the second highest grade, the employee's virtual grade will be that grade. This process is repeated for each successively lower grade encompassed within the assigned band until a grade is found at which the employee's adjusted salary equals or exceeds the step 4 rate of the highest applicable GS rate range for that grade. </P>
                                    <P>(iv) Notwithstanding paragraph (d)(1)(iii) of this section, if the employee's adjusted salary exceeds the maximum rate of the highest applicable GS rate range for the assigned GS grade determined under paragraph (d)(1)(iii) of this section but fits in the highest applicable GS rate range for the next higher grade (i.e., is greater than or equal to the rate for step 1 but less than the rate for step 4), then the employee's virtual GS grade will be that higher grade. </P>
                                    <P>(v) Notwithstanding paragraph (d)(1)(iii) of this section, an employee's virtual GS grade may not be less than the permanently assigned GS grade the employee held upon conversion into NSPS (for an employee who was converted as described in § 9901.371), unless, since that time, the employee has undergone—</P>
                                    <P>(A) A voluntary reduction in band or reduction in base salary; </P>
                                    <P>(B) An involuntary reduction in band or reduction in base salary based on unacceptable performance and/or conduct; or </P>
                                    <P>(C) A reduction in band based on a reduction in force (RIF) or classification action. </P>
                                    <P>(vi) If the employee's adjusted salary exceeds the maximum rate of the highest applicable GS rate range for the highest grade encompassed by his or her assigned pay band, the employee's virtual grade will be that highest GS grade. </P>
                                    <P>(vii) If the employee's adjusted salary is less than the step 4 rate of the highest applicable GS rate range for the lowest GS grade encompassed within his or her assigned NSPS pay band, the employee's virtual grade will be the lowest GS grade in the band. </P>
                                    <P>
                                        (2) 
                                        <E T="03">Virtual GS rate.</E>
                                         (i) Once a virtual GS grade has been established, a virtual GS rate will be set (before any pay-related action that would take effect on the date of the employee's conversion or movement out of NSPS). As of the day before the date of conversion or movement out of NSPS, the employee's NSPS adjusted salary will be compared to the highest applicable GS rate range for the established virtual grade. If the employee's adjusted salary rate falls within that range, the virtual rate will be set equal to that adjusted salary rate. (Since this virtual GS rate is used only as a basis for setting the employee's rate in a new non-NSPS position, it is not necessary to set it at a GS step rate at this stage.) If an employee's adjusted salary is less than the minimum rate of the highest applicable GS rate range for the virtual GS grade, his or her virtual rate will be set at the minimum step rate. If the employee's adjusted salary is greater than the maximum rate of the highest applicable GS rate range for the virtual GS grade, his or her virtual rate will be set at the maximum step rate or at a retained rate set using GS pay retention rules in 5 CFR part 536 (if the employee is eligible for pay retention under those rules). 
                                    </P>
                                    <P>(ii) If the virtual rate derived under paragraph (d)(2)(i) of this section is an adjusted salary rate that includes a locality payment or special rate supplement, an employee's virtual GS base salary rate will be derived based on that adjusted salary rate. </P>
                                    <P>
                                        (iii) The virtual GS grade and rates established under this paragraph (d) will be used in applying GS pay administration rules in setting pay in the new GS position (e.g., the GS promotion rules, pay retention rules, and the maximum payable rate rule). (Since the NSPS system did not continue coverage under the grade retention provision in 5 U.S.C. 5362, grade retention is not applicable to NSPS employees who convert or move to a GS position.) As required by 
                                        <PRTPAGE P="56417"/>
                                        paragraph (c) of this section, any pay action effective on the date of conversion or movement from NSPS to the GS pay system will be processed under GS pay administration rules. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">GS within-grade increases.</E>
                                         Service under NSPS is creditable for within-grade increase purposes upon conversion or movement to a GS position under this section to the extent provided under 5 CFR part 531, subpart D. 
                                    </P>
                                    <P>
                                        (f) 
                                        <E T="03">Comparison of rates of basic pay.</E>
                                         For the purpose of determining whether the conversion or movement out of NSPS under this section is an adverse action for reduction of pay under 5 U.S.C. chapter 75, subchapter II (dealing with adverse actions), an employee's rate of basic pay includes any applicable locality payment under 5 U.S.C. 5304, special rate supplement under 5 U.S.C. 5305, local market supplement under § 9901.332, or equivalent supplement under other legal authority. This comparison is made before any pay-related action (e.g.,  geographic movement) under the gaining system that takes effect on the date of conversion or movement. 
                                    </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart D—Performance Management </HD>
                                <SECTION>
                                    <SECTNO>§ 9901.401 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <P>(a) This subpart establishes a performance management system as authorized by 5 U.S.C. 9902. </P>
                                    <P>(b) The performance management system established under this subpart is designed to promote and sustain a high-performance culture. The implementation and operation of the system will provide for the following elements: </P>
                                    <P>(1) Adherence to merit principles set forth in 5 U.S.C. 2301; </P>
                                    <P>(2) A fair, credible, and transparent employee performance appraisal system; </P>
                                    <P>(3) A link between the performance management system and DoD's strategic plan; </P>
                                    <P>(4) A means for ensuring employee involvement in the design and implementation of the system; </P>
                                    <P>(5) Adequate training and retraining for supervisors, managers, and employees in the implementation and operation of the performance management system; </P>
                                    <P>(6) A process for ensuring ongoing performance feedback and dialogue among supervisors, managers, and employees throughout the appraisal period, and setting timetables for review; </P>
                                    <P>(7) Effective safeguards to ensure that the management of the system is fair and equitable and based on employee performance; </P>
                                    <P>(8) A means for ensuring that adequate agency resources are allocated for the design, implementation, and administration of the performance management system; and </P>
                                    <P>(9) A pay-for-performance evaluation system to better link individual pay to performance and provide an equitable method for appraising and compensating employees. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.402 </SECTNO>
                                    <SUBJECT>Coverage. </SUBJECT>
                                    <P>(a) This subpart applies to eligible employees and positions in the categories listed in paragraph (b) of this section, subject to a determination by the Secretary under § 9901.102. </P>
                                    <P>(b) The following employees and positions in organizational and functional units are eligible for coverage under this subpart: </P>
                                    <P>(1) Employees and positions that would otherwise be covered by 5 U.S.C. chapter 43; </P>
                                    <P>(2) Employees and positions excluded from chapter 43 by OPM under 5 CFR 430.202(d) prior to the date of coverage of this subpart; and </P>
                                    <P>(3) Such others designated by the Secretary as DoD may be authorized to include under 5 U.S.C. 9902. </P>
                                    <P>(c) Except as provided in § 9901.408, this subpart does not apply to employees who have been, or are expected to be, employed in an NSPS position for less than a minimum period (as described in § 9901.407) during a single 12-month period. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.403 </SECTNO>
                                    <SUBJECT>Waivers. </SUBJECT>
                                    <P>When a specified category or group of employees is covered by the performance management system established under this subpart, the provisions of 5 U.S.C. chapter 43 are waived with respect to that category of employees. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.404 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>In this subpart—</P>
                                    <P>
                                        <E T="03">Appraisal</E>
                                         means the review and evaluation of an employee's performance. 
                                    </P>
                                    <P>
                                        <E T="03">Appraisal period</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Competencies</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Contribution</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Contributing Factors</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Job Objectives</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Minimum period</E>
                                         means the period of time during which an employee will perform under one or more approved NSPS performance plans before receiving a rating of record. 
                                    </P>
                                    <P>
                                        <E T="03">Pay-for-performance evaluation system</E>
                                         means the performance management system established under this subpart to link individual pay to performance and provide an equitable method for evaluating performance and compensating employees. 
                                    </P>
                                    <P>
                                        <E T="03">Pay Pool Manager</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Pay Pool Panel</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Performance</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Performance expectations</E>
                                         means the duties, responsibilities, and competencies required by, or objectives associated with, an employee's position and the contributions and demonstrated competencies management expects of an employee, as described in § 9901.406. 
                                    </P>
                                    <P>
                                        <E T="03">Performance management</E>
                                         means applying the integrated processes of setting and communicating performance expectations, monitoring performance and providing feedback, developing performance and addressing poor performance, and rating and rewarding performance in support of the organization's goals and objectives. 
                                    </P>
                                    <P>
                                        <E T="03">Performance management system</E>
                                         means the policies and requirements established under this subpart, as supplemented by implementing issuances, for setting and communicating employee performance expectations, monitoring performance and providing feedback, developing performance and addressing poor performance, and rating and rewarding performance. It incorporates and operationalizes the elements set forth in § 9901.401(b). 
                                    </P>
                                    <P>
                                        <E T="03">Performance Review Authority</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Rating official</E>
                                         means a representative of management, usually the immediate supervisor, who evaluates and assesses employee performance and recommends a rating of record, share assignment, and payout distribution for review by the Pay Pool Panel. 
                                    </P>
                                    <P>
                                        <E T="03">Rating of record</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                    <P>
                                        <E T="03">Unacceptable performance</E>
                                         has the meaning given that term in § 9901.103. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.405 </SECTNO>
                                    <SUBJECT>Performance management system requirements. </SUBJECT>
                                    <P>(a) The Secretary may issue implementing issuances further defining a performance management system for NSPS employees, subject to the requirements set forth in this subpart. </P>
                                    <P>(b) The NSPS performance management system—</P>
                                    <P>(1) Provides for the appraisal of the performance of each employee annually; </P>
                                    <P>
                                        (2) Holds supervisors and managers accountable for effectively managing the performance of employees under their supervision as set forth in paragraph (c) of this section; 
                                        <PRTPAGE P="56418"/>
                                    </P>
                                    <P>(3) Specifies procedures for setting and communicating performance expectations, monitoring performance and providing feedback, and developing, rating, and rewarding performance; </P>
                                    <P>(4) Specifies the criteria and procedures to address the performance of employees who are detailed or transferred and for employees in other special circumstances; </P>
                                    <P>(5) Provides for the following multiple rating levels: </P>
                                    <GPOTABLE COLS="02" OPTS="L2,tp0,i1" CDEF="s50,r50">
                                        <TTITLE> </TTITLE>
                                        <BOXHD>
                                            <CHED H="1">Rating of record</CHED>
                                            <CHED H="1">Rating of record descriptor</CHED>
                                        </BOXHD>
                                        <ROW>
                                            <ENT I="01">Level 5</ENT>
                                            <ENT>Role Model.</ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Level 4</ENT>
                                            <ENT>Exceeds Expectations.</ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Level 3</ENT>
                                            <ENT>Valued Performer.</ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Level 2</ENT>
                                            <ENT>Fair.</ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Level 1</ENT>
                                            <ENT>Unacceptable.</ENT>
                                        </ROW>
                                    </GPOTABLE>
                                    <P>(6) Specifies rounding rules for average adjusted ratings as follows: </P>
                                    <P>(i) The combination of the job objective rating and the contributing factor assessment results in an adjusted rating for each job objective; </P>
                                    <P>(ii) The job objective adjusted ratings are averaged to obtain the employee's raw score; </P>
                                    <P>(iii) Any objective rated as “NR” is not counted when averaging ratings; </P>
                                    <P>(iv) When the employee's raw score ends with .51 or higher, the rating is rounded to the next higher whole number; </P>
                                    <P>(v) When the employee's raw score ends with .50 or lower, the rating is rounded to the next lower whole number; and </P>
                                    <P>(vi) The resulting rounded score is the recommended rating of record. </P>
                                    <P>(c) In fulfilling the requirements of paragraph (b) of this section, supervisors and managers will—</P>
                                    <P>(1) Clearly communicate performance expectations and hold employees responsible for accomplishing them; </P>
                                    <P>(2) Make meaningful distinctions among employees based on performance and contribution; </P>
                                    <P>(3) Foster and reward excellent performance; </P>
                                    <P>(4) Address poor performance; and </P>
                                    <P>(5) Assure that employees are assigned a rating of record. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.406 </SECTNO>
                                    <SUBJECT>Setting and communicating performance expectations. </SUBJECT>
                                    <P>(a) Performance expectations will support and align with the mission and strategic goals, organizational program and policy objectives, annual performance plans, and other measures of performance. </P>
                                    <P>(b) Performance expectations will be communicated to the employee in writing prior to holding the employee accountable for them. </P>
                                    <P>(c) Notwithstanding the requirements in paragraphs (d) through (g) of this section, employees are accountable for demonstrating professionalism and appropriate standards of conduct and behavior, such as civility and respect for others. </P>
                                    <P>(d) In addition to the requirement in paragraph (c) of this section, supervisors and managers will be held accountable through their performance expectations for how well they plan, monitor, develop, correct, and assess subordinate employees' performance. </P>
                                    <P>(e) Performance expectations include—</P>
                                    <P>(1) Goals or objectives that set general or specific performance targets at the individual, team, and/or organizational level; </P>
                                    <P>(2) Organizational, occupational, or other work requirements, such as standard operating procedures, operating instructions, manuals, internal rules and directives, and/or other instructions that are generally applicable and available to the employee; and </P>
                                    <P>(3) Competencies an employee is expected to demonstrate on the job, and/or the contributions an employee is expected to make. </P>
                                    <P>(f) Performance expectations may be amplified through particular work assignments or other instructions (which may specify the quality, quantity, accuracy, timeliness, or other expected characteristics of the completed assignment, or some combination of such characteristics). Such assignments and instructions need not be in writing. </P>
                                    <P>(g) Supervisors will involve employees, insofar as practicable, in the development of their performance expectations. However, final decisions regarding performance expectations are within the sole and exclusive discretion of management. </P>
                                    <P>(h) Performance expectations are subject to higher- or second-level review to ensure consistency and fairness within and across organizations. </P>
                                    <P>(i) Performance expectations that comprise a performance plan are considered to be approved when the supervisor has communicated the performance plan to the employee in writing. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.407 </SECTNO>
                                    <SUBJECT>Minimum period of performance. </SUBJECT>
                                    <P>(a) Only employees who have completed the minimum period under one or more NSPS approved performance plans may be issued a rating of record in accordance with the procedures prescribed by this subpart. </P>
                                    <P>(b) The minimum period of performance is 90 calendar days. </P>
                                    <P>(1) Periods during which an employee is in a leave status may not be applied toward the 90-day minimum. </P>
                                    <P>(2) If an employee has a break in NSPS-covered service (e.g.,  due to job change to a non-NSPS position, resignation), the service performed prior to the break may not be used to satisfy the 90-day minimum period. A break caused by a situation described in § 9901.342(i) through (1) is not considered a break for this purpose. </P>
                                    <P>(c) Employees who have not completed the minimum period of performance during the applicable appraisal period will not be rated and will not be eligible for a performance payout unless otherwise provided in § 9901.342(i) through (1). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.408 </SECTNO>
                                    <SUBJECT>Employees on time-limited appointments. </SUBJECT>
                                    <P>Employees who are appointed for less than 90 days—</P>
                                    <P>(a) Will be given performance expectations that are linked to the organization's strategic plan; and </P>
                                    <P>(b) May receive an evaluation at the end of the appointment which—</P>
                                    <P>(1) Consists of a narrative description addressing employee performance, accomplishments and contributions during that appointment; and </P>
                                    <P>(2) May serve as documentation and justification for recognition under 5 U.S.C. chapter 45. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.409 </SECTNO>
                                    <SUBJECT>Monitoring and developing performance. </SUBJECT>
                                    <P>(a) In applying the requirements of the performance management system and its implementing issuances and policies, supervisors will—</P>
                                    <P>(1) Monitor the performance of their employees and their contribution to the organization; </P>
                                    <P>(2) Provide ongoing (i.e., regular and timely) feedback to employees on their actual performance with respect to their performance expectations, including one or more interim performance reviews during each appraisal period; and </P>
                                    <P>(3) Document at least one interim performance review. Documented interim reviews are not required for overall periods of performance of less than 180 days. </P>
                                    <P>
                                        (b) Developing performance is integrated with the performance management process and is a shared responsibility of management and employees. Developing performance includes but is not limited to—(1) Coaching and mentoring employees; 
                                        <PRTPAGE P="56419"/>
                                    </P>
                                    <P>(2) Reinforcing strengths and addressing weaknesses; and </P>
                                    <P>(3) Discussing employee development opportunities. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.410 </SECTNO>
                                    <SUBJECT>Addressing performance that does not meet expectations. </SUBJECT>
                                    <P>(a) If at any time during the appraisal period a supervisor determines that an employee's performance is not meeting expectations, the supervisor will—</P>
                                    <P>(1) Identify and communicate to the employee the specific performance deficiencies that require improvement; </P>
                                    <P>(2) Consider the range of options available to address the performance deficiency, including remedial training, improvement periods, reassignment, oral warnings, letters of counseling, written reprimands, or adverse action (including a reduction in rate of basic pay or pay band or a removal); and </P>
                                    <P>(3) Take appropriate action to address the deficiency, taking into account the circumstances, including the nature and gravity of the unacceptable performance and its consequences. </P>
                                    <P>(b) Adverse actions taken based on unacceptable performance and/or conduct will be taken in accordance with the provisions in 5 U.S.C. chapter 75 or other appropriate procedures if not covered by chapter 75, such as procedures for National Guard Technicians under 32 U.S.C. 709(f). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.411 </SECTNO>
                                    <SUBJECT>Appraisal period. </SUBJECT>
                                    <P>(a) Except as provided in paragraphs (a)(1) through (3) and (b) of this section, the appraisal period will be October 1 to September 30. </P>
                                    <P>(1) The appraisal period may begin after October 1 and end after September 30 for newly converted groups of employees; </P>
                                    <P>(2) The appraisal period may begin after October 1 for employees who move to an NSPS position from a non-NSPS position after that date; and </P>
                                    <P>(3) The appraisal period may end between July 3 and September 30 for employees receiving early annual recommended ratings. </P>
                                    <P>(b) If, by the end of the appraisal period, an employee has not met the minimum period of performance, management may extend the appraisal period provided such extensions do not—</P>
                                    <P>(1) Delay the payout for the applicable pay pool; or </P>
                                    <P>(2) Extend beyond the rating of record effective date. </P>
                                    <P>(c) The effective date of ratings of record will be January 1, except for additional ratings of record as described in § 9901.412(b)(2). </P>
                                    <P>(d) The effective date of a rating of record described in § 9901.412(b)(2) is the date the rating is final, as described in paragraph (g) of § 9901.412. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 9901.412 </SECTNO>
                                    <SUBJECT>Rating and rewarding performance. </SUBJECT>
                                    <P>(a) Forced distribution of ratings (setting pre-established limits for the percentage or number of ratings that may be assigned at any level) is prohibited. </P>
                                    <P>(b) An appropriate rating official—</P>
                                    <P>(1) Will prepare and recommend a rating of record after the completion of the appraisal period; and </P>
                                    <P>(2) May recommend an additional rating of record following an unacceptable rating of record to reflect a substantial and sustained change in the employee's performance since the last rating of record. </P>
                                    <P>(c) The recommended rating of record is subject to higher-level review. </P>
                                    <P>(d) A rating of record will assess an employee's performance with respect to his or her performance expectations, as amplified through work assignments or other instructions, and/or relative contributions. </P>
                                    <P>(e) If an employee engages in work-related misconduct and the nature or severity of that misconduct has an impact on the execution of his or her duties, that of the team, and/or that of the organization, the impact may be considered in the employee's rating of record. </P>
                                    <P>(f) A Pay Pool Panel will —</P>
                                    <P>(1) Review recommended ratings of record, share assignments, and payout distributions, and make adjustments, which in the panel's view would result in equity and consistency across the pay pool; and </P>
                                    <P>(2) Afford the rating official the opportunity to provide further justification of a recommended rating of record before a change to that rating becomes final. </P>
                                    <P>(g) Consistent with the requirements of merit system principles and this part, the Pay Pool Manager is the approving authority for Pay Pool Panel recommendations concerning ratings of record, share assignments, and payout distribution. A rating of record is considered final when issued to the employee with all appropriate reviews and signatures. </P>
                                    <P>(h) An appropriate rating official will communicate the final rating of record, share assignment, and payout distribution to the employee. </P>
                                    <P>(i) Once the minimum performance period is met and an employee is eligible for a rating of record, the rating of record of an employee may not be lowered based on an approved absence from work, including the absence of a disabled veteran to seek medical treatment as provided in Executive Order 5396. </P>
                                    <P>(j) A rating of record issued under this subpart—</P>
                                    <P>(1) Is an official rating of record for the purpose of any provision of this title for which an official rating of record is required; </P>
                                    <P>(2) Will be transferred between subordinate organizations and to other Federal departments or agencies in accordance with implementing issuances; </P>
                                    <P>(3) Will be used as a basis for—</P>
                                    <P>(i) A pay determination under any applicable pay rules; </P>
                                    <P>(ii) Determining reduction-in-force retention standing; and </P>
                                    <P>(iii) Such other action that the Secretary considers appropriate, as specified in implementing issuances; </P>
                                    <P>(4) Will cover a specified appraisal period; and </P>
                                    <P>(5) Will not be carried over as the rating of record for a subsequent appraisal period without an actual evaluation of the employee's performance during the subsequent appraisal period. </P>
                                    <P>(k) Employees who change pay pools after the last day of the appraisal period and before the effective date of the payout will be evaluated and assigned a rating of record by the Pay Pool Manager associated with the pay pool of record on the last day of the appraisal period and the share assignment and payout distribution determination will be made in accordance with § 9901.342(g). </P>
                                    <P>(l)(1) An early annual recommended rating of record will be issued when—</P>
                                    <P>(i) The supervisor (or rating official if different) ceases to exercise the duties relative to monitoring, developing, and rating employee performance within 90 days before the end of the appraisal period; or </P>
                                    <P>(ii) The employee is reassigned, promoted, or reduced in band resulting in the assignment of a new rating official within 90 days before the end of the appraisal period. </P>
                                    <P>(2) An employee who is eligible for a recommended rating of record or an early annual recommended rating of record at the time they move to a position outside of NSPS will be entitled to a rating of record. Such ratings of record must be approved through the Pay Pool Panel process. </P>
                                    <P>(m) At any time prior to the last 90 days of the appraisal period, a supervisor or other rating official may prepare a performance assessment (e.g., close-out assessment) for the purpose of providing input on an employee's performance to a new supervisor. Such an assessment is not a rating of record (recommended or final). </P>
                                </SECTION>
                                <SECTION>
                                    <PRTPAGE P="56420"/>
                                    <SECTNO>§ 9901.413 </SECTNO>
                                    <SUBJECT>Reconsideration of ratings. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Nonbargaining unit employees.</E>
                                         (1) A rating of record or job objective rating may be challenged by a nonbargaining unit employee only through the reconsideration process specified in this subpart and implementing issuances. This process will be the sole and exclusive agency administrative process for all nonbargaining unit employees to challenge a rating of record. 
                                    </P>
                                    <P>(2) Consistent with this part, Pay Pool Managers will decide job objective rating and rating of record reconsiderations. </P>
                                    <P>(3) If the Pay Pool Manager decision is challenged, consistent with this part, the Performance Review Authority will make a final decision. </P>
                                    <P>(4) A share assignment determination, payout distribution determination, or any other payout matter will not be subject to the reconsideration process or any other agency administrative grievance system. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Bargaining unit employees.</E>
                                         (1) Negotiated grievance procedures are the exclusive administrative procedures for bargaining unit employees to challenge a rating of record or job objective rating as provided for in 5 U.S.C. 7121. 
                                    </P>
                                    <P>(2) If a negotiated grievance procedure is not available to a bargaining unit employee or challenging a rating of record or job objective rating is outside the scope of the employee's negotiated grievance procedure, a bargaining unit employee may challenge a rating of record or job objective rating in accordance with this subpart and implementing issuances. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Recalculation based on adjusted job objective rating or rating of record.</E>
                                         In the event a reconsideration or negotiated grievance decision results in an adjusted job objective rating or rating of record the revised rating will be referred to the Pay Pool Manager for recalculation of the employee's performance payout amount and distribution. 
                                    </P>
                                    <P>(1) Any adjustment to salary will be retroactive to the effective date of the performance payout. </P>
                                    <P>(2) Salary adjustments will be based on the share range appropriate for the adjusted rating of record as identified in § 9901.342(f). </P>
                                    <P>(3) Share values for the adjusted rating of record will reflect the share value paid to other members across the pay pool for that rating cycle. </P>
                                    <P>(4) Decisions made through the reconsideration process or a negotiated grievance procedure will not result in recalculation of the payout made to other employees in the pay pool. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Alternative dispute resolution.</E>
                                         Alternative dispute resolution techniques, such as mediation, interest-based problem-solving, or others, may be pursued at any time during the reconsideration process consistent with the Component's policies and procedures. 
                                    </P>
                                </SECTION>
                            </SUBPART>
                        </PART>
                    </REGTEXT>
                </SUPLINF>
                <FRDOC> [FR Doc. E8-22483 Filed 9-25-08; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 6325-39-P </BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>73</VOL>
    <NO>188</NO>
    <DATE>Friday, September 26, 2008</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="56421"/>
            <PARTNO>Part V</PARTNO>
            <AGENCY TYPE="P">Department of Health and Human Services</AGENCY>
            <SUBAGY>Administration for Children and Families</SUBAGY>
            <HRULE/>
            <SUBAGY>Office of Child Support Enforcement</SUBAGY>
            <HRULE/>
            <CFR>45 CFR Parts 302, 303, and 307</CFR>
            <TITLE>State Parent Locator Service; Safeguarding Child Support Information; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="56422"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                    <SUBAGY>Administration for Children and Families</SUBAGY>
                    <SUBAGY>Office of Child Support Enforcement</SUBAGY>
                    <CFR>45 CFR Parts 302, 303, and 307</CFR>
                    <RIN>RIN 0970-AC01</RIN>
                    <SUBJECT>State Parent Locator Service; Safeguarding Child Support Information</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Office of Child Support Enforcement (OCSE), Administration for Children and Families (ACF), Department of Health and Human Services (HHS).</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Personal Responsibility and Work Opportunity Reconciliation Act of 1996 (PRWORA) created and expanded State and Federal title IV-D child support enforcement databases and significantly enhanced access to information for title IV-D child support purposes. States are moving toward integrated service delivery and developing enterprise architecture initiatives to link their program databases. This final rule prescribes requirements for: State Parent Locator Service responses to authorized location requests; and State IV-D program safeguarding of confidential information and authorized disclosures of this information. This rule restricts the use of confidential data and information to child support purposes, with exceptions for certain disclosures permitted by statute.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>This rule is effective March 23, 2009.</P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Yvette Hilderson Riddick, Policy and Automation Liaison, OCSE, 202-401-4885, e-mail: 
                            <E T="03">yvetteriddick@acf.hhs.gov.</E>
                             Deaf and hearing-impaired individuals may call the Federal Dual Party Relay Service at 1-800-877-8339 between 8 a.m. and 7 p.m. eastern time.
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <EXTRACT>
                        <FP SOURCE="FP-2">I. Statutory Authority</FP>
                        <FP SOURCE="FP-2">II. Summary Description of Regulatory Provisions</FP>
                        <FP SOURCE="FP1-2">A. State Parent Locator Service</FP>
                        <FP SOURCE="FP1-2">B. Safeguarding and Disclosure of Confidential Information</FP>
                        <FP SOURCE="FP-2">III. Section-by-Section Discussion of Comments</FP>
                        <FP SOURCE="FP-2">IV. Regulatory Review</FP>
                        <FP SOURCE="FP1-2">A. Paperwork Reduction Act</FP>
                        <FP SOURCE="FP1-2">B. Regulatory Flexibility Analysis</FP>
                        <FP SOURCE="FP1-2">C. Regulatory Impact Analysis</FP>
                        <FP SOURCE="FP1-2">D. Unfunded Mandates Reform Act of 1995</FP>
                        <FP SOURCE="FP1-2">E. Congressional Review</FP>
                        <FP SOURCE="FP1-2">F. Assessment of Federal Regulations and Policies on Families</FP>
                        <FP SOURCE="FP1-2">G. Executive Order 13132</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">I. Statutory Authority</HD>
                    <P>This final regulation is published under the authority granted to the Secretary of HHS (Secretary) by section 1102 of the Social Security Act (the Act), 42 U.S.C. 1302. Section 1102 authorizes the Secretary to publish regulations that may be necessary for the efficient administration of the functions for which he is responsible under the Act.</P>
                    <P>The provisions of this final rule pertaining to the Federal Parent Locator Service (PLS) implement section 453 of the Act, 42 U.S.C. 653. Section 453 requires the Secretary to establish and conduct a Federal PLS to obtain and transmit specified information to authorized persons for purposes of establishing parentage; establishing, modifying, or enforcing child support obligations; and enforcing any Federal or State law with respect to a parental kidnapping; or making or enforcing a child custody or visitation determination, as described in section 463 of the Act. It authorizes the Secretary to use the services of State entities to carry out these functions.</P>
                    <P>The provisions relating to the State PLS implement section 454(8) of the Act, 42 U.S.C. 654(8), which requires each State plan for child support enforcement to provide that the State will: (1) Establish a service to locate parents utilizing all sources of information and available records; and the Federal PLS established under section 453; and (2) shall subject to the privacy safeguards in section 454(26) of the Act, 42 U.S.C. 654(26), disclose only the information described in sections 453 and 463 of the Act to the authorized persons specified in those sections.</P>
                    <P>The provisions relating to the States' computerized support enforcement systems implement section 454A of the Act, 42 U.S.C. 654a, which requires States' systems to perform such functions as the Secretary may specify relating to management of the State title IV-D program. Additionally, as stated in section 454A(f) of the Act, the State shall use the statewide automated system to extract information from, to share and compare information with, and to receive information from, other data bases and information necessary to enable the State agency (or the Secretary or other State or Federal agencies) to carry out the Child Support Enforcement program under title IV-D of the Act, and other programs designated by the Secretary.</P>
                    <P>In addition, the provisions pertaining to safeguarding of information implement section 454(26) of the Act, which requires the State IV-D program to have in effect safeguards, applicable to all confidential information handled by the State agency, that are designed to protect the privacy rights of the parties. Nothing in this rule is meant to prevent the appropriate use of administrative data for program oversight, management, and research.</P>
                    <HD SOURCE="HD1">II. Summary Description of Regulatory Provisions </HD>
                    <P>
                        The following is a summary of the regulatory provisions included in this final rule. The Notice of Proposed Rulemaking (NPRM) was published in the 
                        <E T="04">Federal Register</E>
                         on October 14, 2005 (70 FR 60038). The NPRM was organized into two major sections. Section 1: State Parent Locator Service discussed amendments to the proposed regulations on locating individuals and their assets in response to authorized location requests. Affected regulations include §§ 302.35, 303.3, 303.20, and 303.70. Section 2: Safeguarding and Disclosure of Confidential Information discussed new regulations on safeguarding and disclosure of confidential information, § 303.21 and amendments to the regulation on security and confidentiality of information in computerized support enforcement systems, § 307.13. 
                    </P>
                    <P>The Section-by-Section Discussion of Comments (Section III) provides a detailed listing of the comments and responses. Many commenters asked for points of clarification rather than for change of language in the regulation. There were some comments, however, that brought about regulatory language changes in the final rule. Specifically, major changes include: </P>
                    <P>In § 303.21(a) we deleted the last sentence “The amount of support ordered and the amount of a support collection are not considered confidential information for purposes of this section.” Commenters were concerned that this language may be interpreted as IV-D payment records could be made available to requestors not associated with the case who may want the information for purposes not related to child support. </P>
                    <P>
                        In response to comments, we deleted paragraph (1) of § 303.21(d), which in the NPRM authorized disclosure of confidential information to the individual to whom the information pertains. To the extent that an individual is requesting information about himself/herself in the IV-D agency's files for a IV-D program purpose, the information may be 
                        <PRTPAGE P="56423"/>
                        disclosed under paragraph (c), General rule. We also deleted under paragraph (e) Safeguards, that “safeguards shall prohibit disclosure to any committee or legislative body (Federal, State, or local) of any confidential information, unless authorized by the individual as specified in paragraph (d) of this section.” To the extent that an individual in a IV-D case submits a request to a legislator or legislative body concerning his or her IV-D case, the IV-D agency may disclose the information necessary for the response because the inquiry relates to the administration of the IV-D program and is authorized under paragraph (c). 
                    </P>
                    <P>We revised § 303.21(d)(2)(ii) and (iii) and relocated it to § 303.21(d)(1). Section 454A of the Act only permits the disclosure of information for non-IV-D purposes to State agencies of designated programs where the information is necessary to carry out a State agency function under that program. Therefore, we have relocated these disclosures to clarify that they are encompassed within this authority specified in § 303.21(d)(1). In paragraph (2), we restricted disclosure of information for income and eligibility verification purposes under sections 453A and 1137 of the Act to SDNH information. </P>
                    <P>We added language to § 303.21(e) that refers to family violence indicator requirements under § 307.11(f)(1)(x). Commenters thought we should add language regarding the family violence indicator which is an additional privacy safeguard for family violence victims. </P>
                    <P>We also changed § 307.13(a) of the NPRM by deleting paragraph (4). It referred to welfare-to-work, a grant program that no longer exists. We redesignated paragraph (a)(5) as paragraph (a)(4) and revised the language for clarity. As revised, it requires written policies that limit disclosure outside the IV-D program of National Directory of New Hire, Federal Case Registry and Internal Revenue Service (IRS) information from the computerized support enforcement system. The regulation sets forth the circumstances when information may be disclosed to IV-A, IV-B, and IV-E agencies and when IRS information may be disclosed. As revised, financial institution information cannot be shared outside the IV-D program. We made this change because of the language in section 469A(a) and (b) of the Act. These sections provide for non-liability for financial institutions when they disclose financial record information only for child support related purposes. Throughout the preamble and regulation we use “financial institution information” to refer to information covered by section 469A(a) and (b) of the Act. This information includes Multistate Financial Data Matches (MSFIDM) and State Financial Institute Data Matches (State FIDM). </P>
                    <P>Some commenters found the charts confusing, especially Appendix A in Section I and Appendix A in Section 2. We reorganized the two previous charts into three charts: Appendix A, B, and C. In Appendix A we reordered the chart by displaying locate efforts first by person rather than by purpose. Appendix A illustrates authority for locating individuals through the State PLS. Appendix B illustrates authority for locating an individual sought in a child custody/visitation or parental kidnapping case. Appendix C illustrates authority for State IV-D agencies to release information to non-IV-D Federal, State, and Tribal Programs. These charts are included at the end of the preamble for illustrative purposes only. </P>
                    <HD SOURCE="HD1">Section II. A. State Parent Locator Service (Sections 302.35, 303.3, 303.20, and 303.70) </HD>
                    <HD SOURCE="HD2">Section 302.35, State Parent Locator Service </HD>
                    <P>The previous regulation at § 302.35(a) contained a State plan requirement that the IV-D program shall establish a State Parent Locator Service (PLS) using: (1) All relevant sources of information and records available in the State, and in other States as appropriate; and (2) the Federal PLS of the Department of Health and Human Services. </P>
                    <P>Paragraph (a) modifies the requirement for each State to “establish” a State PLS, and instead requires each State to “maintain” a State PLS “to provide locate information to authorized persons for authorized purposes.” </P>
                    <P>Section § 302.35(a)(1), covering IV-D agencies, cases and purposes, requires that the State PLS access “the Federal PLS and all relevant sources of information and records available in the State, and in other States as appropriate, for locating custodial parents, noncustodial parents, and children for IV-D purposes.” Paragraph (a)(2) addresses locate requests for authorized non-IV-D individuals and purposes. For purposes of this regulation, all requests under section 453(c)(3) of the Act are considered to be requests by non-IV-D individuals and purposes. This provision requires a IV-D program to access and release information authorized to be disclosed under section 453(a)(2) of the Act from “the Federal PLS and, in accordance with State law, information from relevant in-state sources of information and records, as appropriate” to respond to locate requests from a non-IV-D entity or authorized individual specified in paragraph (c) and for authorized purposes specified in paragraph (d). </P>
                    <P>For non-IV-D requests, under paragraph (a)(2), the State PLS will not access IRS information or financial institution information, which is available only to IV-D agencies and to a limited extent to their agents, under Federal statute. </P>
                    <P>The previous regulation at paragraph (b) required that the IV-D agency must “establish a central State PLS office and also may designate additional IV-D offices within the State to submit requests to the Federal PLS.” The amendment to § 302.35(b) removes mention of a State PLS “office.” It also requires the IV-D program to “maintain” rather than “establish” a central State PLS. </P>
                    <P>The previous § 302.35(c)(1) through (5) language specified the authorized persons and entities from whom the State PLS shall accept requests for locate information. The amendments to paragraph (c) strengthen the process by which authorized requestors obtain locate information through the State PLS, specifically with respect to requests from a resident parent, legal guardian, attorney, or agent of a non-IV-A child. </P>
                    <P>
                        Previously, § 302.35(c)(3) simply referred to the “resident parent, legal guardian, attorney, or agent of a child” in non-IV-A cases as authorized persons. The revised § 302.35(c)(3) makes it clear that the State PLS will accept locate requests from the resident parent, legal guardian, attorney or agent of a child who is not receiving assistance under title IV-A of the Act only if key requirements are met. The regulation requires the individual to: (i) Attest that the request is being made to obtain information on, or to facilitate the discovery of, any individual in accordance with section 453(a)(2) of the Act for the purpose of establishing parentage, establishing, setting the amount of, modifying, or enforcing child support obligations; (ii) attest that any information obtained through the Federal or State PLS will be used solely for these purposes and otherwise treated as confidential; (iii) provide evidence that the requestor is the parent, legal guardian, attorney, or agent of a child not receiving assistance under title IV-A of the Act, and if an agent of such a child, evidence of a valid contract that meets any requirements in State law or written policy for acting as an agent, and if a parent, attestation that he or she 
                        <PRTPAGE P="56424"/>
                        is the resident parent; and (iv) pay the Federal PLS fee required under section 453(e)(2) of the Act and § 303.70(f)(2)(i), if the State does not pay the fee itself. The regulation also specifies that the State may charge a fee to cover its costs of processing these requests. A State's fee must be as close to actual costs as possible, so as not to discourage requests to use the Federal PLS. See §§ 304.23(e) and 304.50(a). Paragraph (c)(4) simplifies the language regarding the use of the Federal PLS for parental kidnapping, child custody, or visitation cases. Paragraph (c)(5) rewords the previous language allowing locate requests from State title IV-B and title IV-E agencies. 
                    </P>
                    <P>Previous paragraph (d) is redesignated as paragraph (e), as discussed below. A new paragraph (d) is added to specify the authorized purposes for which the State PLS and the Federal PLS may be used and the locate information that may be released for these purposes. Paragraph (d)(1) covers the purposes of establishing parentage and establishing, modifying, or enforcing child support. It also covers related authorized releases of information to locate an individual who has or may have parental rights with respect to the child. It pertains to IV-D and non-IV-D authorized persons and programs, including title IV-B and IV-E agencies. For IV-B/IV-E cases that are non-IV-D and other cases under (d)(1), wage information is authorized and the State PLS may provide asset and/or debt information from the Federal PLS. Paragraph (d)(2) covers the purposes of enforcing a State law with respect to the unlawful taking or restraint of a child or for making or enforcing child custody or visitation determination and the related authorized releases of information. </P>
                    <P>Paragraph (e), requires privacy safeguards for Federal PLS information only. The amendment specifies at paragraphs (e)(1) and (2) that, subject to the requirements of this section and the privacy safeguards required under section 454(26) of the Act and the family violence indicators under section 307.11(f)(1)(x), the State PLS shall disclose “Federal PLS information” described in sections 453 and 463 of the Act and “information from in-state locate.” An Appendix A has been added at the end of the preamble to show the linkages between authorizing statute, authorized purpose, authorized person or program, and authorized information. </P>
                    <HD SOURCE="HD2">Section 303.3, Location of Noncustodial Parents in IV-D Cases </HD>
                    <P>Under the final rule, § 303.3 is re-titled “Location of noncustodial parents in IV-D cases.” Under paragraph (a), location is defined to mean “information concerning the physical whereabouts of the noncustodial parent, or the noncustodial parent's employer(s), other sources of income or assets, as appropriate, which is sufficient and necessary to take the next appropriate action in a IV-D case.” </P>
                    <P>The amendments to paragraph (b) clarify which location requirements apply to IV-D cases. Paragraph 303.3(b) requires the IV-D program to attempt to locate a noncustodial parent in a IV-D case or his or her sources of income and/or assets when location is needed to take necessary action. Paragraphs (b)(1) through (5) provide an extensive list of location sources that as discussed below are unchanged for the most part from the previous regulation. </P>
                    <P>Paragraph (b)(3) no longer includes the words “including transmitting appropriate cases to the Federal PLS” because States now submit cases to the Federal Case Registry for automatic matching with the National Directory of New Hires for locate purposes. </P>
                    <P>The previous regulation at paragraph (b)(4) required the IV-D program to “Refer appropriate cases to the IV-D program of any other State, in accordance with the requirements of § 303.7 of this part.” The amendment inserts the word “IV-D” before the word “cases” to clarify that the IV-D program of State 1 may refer only IV-D cases to the IV-D program of State 2. </P>
                    <P>New paragraph (b)(6) draws a direct link between the IV-D program's duty to locate noncustodial parents and the duty to safeguard information. The language incorporates by reference both the existing statutory requirement at sections 454(26) and 454A(d) and (f) of the Act and the regulatory requirements at §§ 303.21 and 307.13. </P>
                    <P>Current paragraph (c) regarding diligent efforts to serve process is unchanged, but is republished to aid the reader in reviewing this section. </P>
                    <HD SOURCE="HD2">Section 303.20, Minimum Organizational and Staffing Requirements </HD>
                    <P>The regulation at § 303.20 describes the minimum organizational and staffing requirements for the IV-D program. Paragraph (b) of this section requires an organizational structure and staff sufficient to fulfill specified State level functions, including, in paragraph (b)(7), “operation of the State Parent Locator Service as required under §§ 302.35, 303.3, and 303.70 of this chapter.” </P>
                    <HD SOURCE="HD2">Section 303.21, Safeguarding and Disclosure of Confidential Information </HD>
                    <P>This new regulation is discussed in Section II.B. </P>
                    <HD SOURCE="HD2">Section 303.70, Procedures for Submissions to the State Parent Locator Service (State PLS) or the Federal Parent Locator Service (Federal PLS) </HD>
                    <P>With passage of legislation that established the National Directory of New Hires (NDNH) in 1996 and established the Federal Case Registry (FCR) in 1998, the Federal PLS became highly automated. The language in this section has been revised to indicate that the Federal PLS reflects the automated matching and return of information to IV-D programs in IV-D cases from the Federal PLS's Federal Case Registry and National Directory of New Hires. For example, while requests for Federal PLS information are accepted, State IV-D programs no longer “request” Federal PLS information and we replaced the word “requests” with “submittals” wherever it appears. We eliminated the word “office” as in State PLS “office” to demonstrate that this work is automated. </P>
                    <P>A new paragraph (a) has been inserted: The State agency will have procedures for submitting to the State PLS or the Federal PLS for the purpose of locating parents, putative fathers, or children for the purpose of establishing parentage or establishing, setting the amount of, modifying, or enforcing child support obligations; or for the purpose of enforcing any Federal or State law with respect to the unlawful taking or restraint of a child; or making or enforcing a child custody or visitation determination as defined in section 463(d)(1) of the Act. The previous paragraph (a) has been redesignated as paragraph (b) and the previous paragraph (b) has been redesignated as paragraph (c). </P>
                    <P>In addition, in newly designated paragraph (d) all submittals shall contain the following information: (1) The parent's or putative father's name; (2) the parent's or putative father's Social Security Number (SSN). If the SSN is unknown the IV-D program must make reasonable efforts to ascertain the individual's SSN before making a submittal to the Federal PLS; and (3) any other information prescribed by the Office. </P>
                    <P>
                        The previous regulation at § 303.70(d) has been redesignated as paragraph (e). It requires that annually the IV-D director attest to compliance with the listed requirements. Paragraph (e)(1)(i) specifies that the IV-D program will “obtain” rather than “request” 
                        <PRTPAGE P="56425"/>
                        information. A new paragraph (e)(1)(ii) clarifies that the IV-D program will only provide information to authorized persons as specified in sections 453(c) and 463(d) of the Act and § 302.35. 
                    </P>
                    <P>Paragraph (e)(2) is new and requires that, in the case of a submittal made on behalf of a resident parent, legal guardian, attorney or agent of a child not receiving assistance under title IV-A, the IV-D program must verify that the requestor has complied with the provisions of § 302.35. </P>
                    <P>Paragraph (e)(3), formerly paragraph (d)(2), has been changed to specify that the IV-D program shall treat information obtained through the Federal PLS as confidential and shall safeguard the information in accordance with statutory requirements at § 303.21. </P>
                    <P>Paragraph (f) has minor changes. In (f)(1) the statutory references have been accompanied by explanatory phrases for better understanding and in (f)(4)(ii) the word “paid” has been changed to “transmitted” to reflect the change in payment methodology due to technology advances. </P>
                    <HD SOURCE="HD1">II.B. Safeguarding and Disclosure of Confidential Information (Sections 303.21 and 307.13) </HD>
                    <HD SOURCE="HD2">Section 303.21, Safeguarding and Disclosure of Confidential Information </HD>
                    <P>The regulation consists of six paragraphs: (a) Definitions; (b) Scope; (c) General rule; (d) Authorized disclosures; (e) Safeguards; and (f) Penalties for unauthorized disclosure. </P>
                    <HD SOURCE="HD2">Section 303.21(a) Definitions </HD>
                    <P>
                        The regulation begins with a definition of the term “confidential information.” Paragraph (a)(1) provides that “
                        <E T="03">confidential information</E>
                        ” means any information relating to a specified individual or an individual who can be identified by reference to one or more factors specific to him or her, including, but not limited, to the individual's Social Security Number, residential and mailing addresses, employment information, and financial information. Paragraph (a)(2) defines independent verification to mean the process of acquiring and confirming confidential information through the use of a second source. The information from the second source, which verifies the information about NDNH or FCR data, may be released to those authorized to inspect and use the information as authorized under the regulations or the Act. 
                    </P>
                    <HD SOURCE="HD2">Section 303.21(b) Scope </HD>
                    <P>Paragraph (b) reads: “The requirements of this section apply to the IV-D agency, any other State or local agency or official to whom the IV-D agency delegates any of the functions of the IV-D program, any official with whom a cooperative agreement as described in § 302.34 has been entered into, and any person or private agency from whom the IV-D agency has purchased services pursuant to § 304.22.” </P>
                    <HD SOURCE="HD2">Section 303.21(c) General Rule </HD>
                    <P>Paragraph (c) presents a general rule which states that “[e]xcept as authorized by the Act and implementing regulations, an entity described in paragraph (b) of this section may not disclose any confidential information, obtained in connection with the performance of IV-D functions, outside of the administration of the IV-D program.” </P>
                    <HD SOURCE="HD2">Section 303.21(d) Authorized Disclosures </HD>
                    <P>Paragraph (d) sets forth the authorized disclosures that are exceptions to the general rule prohibiting disclosure of confidential information. Under paragraph (d)(1), upon request, the IV-D agency may, to the extent that it does not interfere with the IV-D agency meeting its own obligations, disclose information for certain limited purposes. Under paragraph (d)(1) information may be shared for administration of programs under titles IV (TANF, child and family services, and foster care and adoption programs), XIX (Medicaid program), and XXI (State Children's Health Insurance [SCHIP] program) of the Act. The regulation also includes disclosure to Tribal programs authorized under title IV-A and IV-D of the Act. </P>
                    <P>Paragraph (d)(2) (previously paragraph (d)(2)(iv)) permits the release of SDNH information to programs designated pursuant to sections 453A and 1137 of the Act for income and eligibility verification purposes. </P>
                    <P>Paragraph (d)(3) requires that authorized disclosures under § 303.21(d)(1) and (2) shall not include confidential information from the National Directory of New Hires, the Federal Case Registry, or Internal Revenue Service (IRS), unless authorized under § 307.13 or unless the information has been independently verified. A State may independently verify the NDNH or the FCR information through another source, in which case the information from the second source may be used. Independent verification is the process of acquiring and confirming confidential information through the use of a second source. The information from the second source may be released to those authorized to inspect and use the information. For example, if a State determines that an address is correct through a postal verification the State can share the information it acquired from the second source (the Post Office). No IRS information can be disclosed outside of the administration of the IV-D program, unless specifically authorized in Federal statute or independently verified. IRS information is restricted as specified in the Internal Revenue Code (IRC). No financial institution information may be disclosed outside the IV-D program. The restriction on release of financial institution information outside the IV-D program is due to the liability protection given to financial institutions for release of information to the Federal PLS or to the State IV-D programs for child support purposes as indicated in section 466(a)(17)(C) of the Act and limitations in section 469A of the Act, regarding the use of such information. </P>
                    <HD SOURCE="HD2">Section 303.21(e) Safeguards </HD>
                    <P>Paragraph (e) provides that “In addition to, and not in lieu of, the safeguards described in § 307.13 of this chapter, which governs computerized support enforcement systems, the IV-D agency shall establish appropriate safeguards to comply with the provisions of this section.” These safeguards shall also include prohibitions against the release of information when the State has reasonable evidence of domestic violence or child abuse against a party or a child and that the disclosure of such information could be harmful to the party or the child, as required by § 454(26) of the Act, and shall include use of the family violence indicator required under § 307.11(f)(1)(x) of this chapter. </P>
                    <HD SOURCE="HD2">Section 303.21(f) Penalties for Unauthorized Disclosure </HD>
                    <P>Paragraph (f) provides that “[a]ny disclosure or use of confidential information in violation of the Act and implementing regulations remains subject to any State and Federal statutes that impose legal sanctions for such disclosure.” </P>
                    <HD SOURCE="HD2">Section 307.13 Security and Confidentiality for Computerized Support Enforcement Systems in Operation After October 1, 1997 </HD>
                    <P>
                        Section 307.13 addresses security and confidentiality of computerized systems. Paragraph (a), (a)(1), and (a)(2) are unchanged. Paragraph (a) addresses information integrity and security. Automated systems must have safeguards protecting the integrity, 
                        <PRTPAGE P="56426"/>
                        accuracy, completeness of, access to, and use of data in the computerized support enforcement system. These safeguards shall include written policies concerning access to data by IV-D program personnel, and the sharing of data with other persons to: (a)(1) Permit access to and use of data to the extent necessary to carry out the State IV-D program under this chapter and (a)(2) specify the data which may be used for particular IV-D program purposes, and the personnel permitted access to such data. 
                    </P>
                    <P>Paragraph (a)(3) permits the IV-D agency to exchange data from its computerized support enforcement system with agencies administering other programs under titles IV, XIX, and XXI of the Act to the extent necessary to carry out State and Tribal agency responsibilities under such programs in accordance with section 454A(f)(3) of the Act; and to the extent that it does not interfere with the IV-D agency meeting its own obligations. </P>
                    <P>Paragraph (a)(4) as written in the NPRM has been deleted. It referred to welfare-to-work, a grant program that no longer exists. The present paragraph (a)(4) which previously was paragraph (a)(5) has been rewritten for clarity and requires written policies that generally prohibit disclosure outside the IV-D program of National Directory of New Hire or Federal Case Registry information, or IRS information from the computerized support enforcement system, to information that has been independently verified. IV-A, IV-B, and IV-E agencies are authorized under various subsections of section 453 of the Act to receive NDNH and FCR information from the Federal PLS for certain specified purposes. Since these agencies are authorized to have this information, we are permitting the IV-D agency to disclose the NDNH or FCR information from the IV-D computerized support enforcement system directly to the IV-A, IV-B, or IV-E agency if it is being requested for the purpose authorized under section 453 of the Act. For IV-B and IV-E programs this includes establishing paternity or parental rights with respect to a child. </P>
                    <HD SOURCE="HD1">III. Section-by-Section Discussion of Comments </HD>
                    <P>This section provides a detailed discussion of comments received on the proposed rule, and describes changes made to the proposed rule. We refer generally to actions of the “Department” pursuant to the rule. The rule itself refers to actions of the “Secretary” but the day-to-day activities of the Secretary's functions have been delegated and are exercised by other Department officials, primarily in the Administration for Children and Families. “Office” refers to the Federal Office of Child Support Enforcement (OCSE). We received approximately 200 comments from 20 IV-D programs (including 1 tribe), 3 organizations, and 1 private citizen. Many comments were for points of clarification rather than stating support or opposition to the proposed regulation. For example, many comments indicated a lack of awareness on existing longtime requirements such as the statutory restrictions of access to Federal PLS data on IV-D systems for certain unauthorized persons and programs. </P>
                    <HD SOURCE="HD2">General Comments </HD>
                    <P>There were various comments that are not attributable to specific sections of the regulation and are discussed below. </P>
                    <P>
                        <E T="03">1. Comment:</E>
                         Two commenters ask that once the final rule is imposed, OCSE provide States with reasonable time to implement these regulations, which may include changes to State legislation and automated systems. Another commenter believes the Office should make clear what the effective date is of this regulation as was done with some regulations while implementing PRWORA. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This rule is effective 6 months from the date of publication. 
                    </P>
                    <P>
                        <E T="03">2. Comment:</E>
                         One commenter requested that the Secretary insert language from sections of the Social Security Act so the reader does not have to look up sections of the Act. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         To do so would significantly increase the length of regulatory language. We have attempted to ensure there are no cross-references without a brief summary of the content of those statutory sections. 
                    </P>
                    <P>
                        <E T="03">3. Comment:</E>
                         This regulation possibly sets up competing public interests. For example: Pitting the confidentiality regulation versus the openness of the judicial system and court files; the regulation versus the State's public policy of open government (Sunshine laws); the regulation versus the State Constitution's provision for access to public records and meetings. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         These regulations govern disclosure of IV-D data under sections 454(26), 453, and 454A of the Act. A wide array of personal information is available to IV-D agencies and it is imperative that the Federal and State governments protect these data to the greatest extent possible and use them only where necessary for authorized purposes. Child support records, including Federal PLS information, contain information that poses a high risk of identity theft, and thus should be treated with special care. 
                    </P>
                    <P>
                        <E T="03">4. Comment:</E>
                         One commenter asks why this rule includes proposed additional restrictions on sharing certain Federal data with other public agencies in one part of the rule while proposing granting broad access to State data to private entities in another part. According to the commenter, use of data disclosed to other State agencies can be easily monitored while private entities are less accountable, harder to monitor, and more likely to use data for unauthorized purposes. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This regulation is determined in large part by explicit Federal statute. Section 454(8) of the Act says that “the agency administering the (State) plan will establish a service to locate parents * * * and shall, subject to the privacy safeguards required under paragraph (26), disclose only the information described in sections 453 (Federal PLS) and 463 (Use of the Federal PLS in connection with enforcement of determination of child custody and in cases of parental kidnapping) to the authorized persons specified in such sections for the purposes specified in such sections.” With respect to private entities the regulation at § 302.35(c)(3) requires an attestation process that must be used by the resident parent, legal guardian, attorney, or agent of a child who is not receiving assistance under title IV-A of the Act when obtaining information on or to facilitate the discovery of any individual in accordance with section 453(a)(2) of the Act. 
                    </P>
                    <P>
                        <E T="03">5. Comment:</E>
                         In 42 U.S.C. 654(26), Congress allowed States to have flexibility in crafting confidentiality requirements. States may find it difficult to follow a regulatory “one size fits all” approach and make changes to the law in matters over which child support agencies have no authority. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulation reflects statutory requirements as stated in section 454(26) of the Act that a child support State Plan must provide that States have in effect safeguards, applicable to all confidential information handled by the State agency, that are designed to protect the privacy rights of the parties involved. It also reflects other statutory restrictions on disclosure in sections 453 and 454A of the Act. 
                    </P>
                    <P>
                        <E T="03">6. Comment:</E>
                         If the Federal Bureau of Investigations (FBI) was called to investigate possible sources of threats to a IV-D caseworker and the FBI demanded the names and contact information for every person on the IV-D employee's caseload, would the IV-D agency be justified in sharing this 
                        <PRTPAGE P="56427"/>
                        information with the FBI? Does protecting a IV-D worker from potential harm fall under the provisions of a IV-D purpose? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The IV-D agency could share the information because the investigation relates to the administration of the IV-D program. 
                    </P>
                    <P>
                        <E T="03">7. Comment:</E>
                         Two commenters say that OCSE should reaffirm its commitment to additional privacy safeguards for family violence victims by incorporating references to the family violence indicator in the rule. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree and have added language to § 303.21(e) that provides explicit reference to required family violence indicators for potential domestic violence or child abuse. 
                    </P>
                    <P>
                        <E T="03">8. Comment:</E>
                         Two commenters are concerned that when enforcing a referral from a Tribal IV-D agency located in that State or in another State, a State would be unable to provide information about whether a Federal tax refund offset occurred and the amount collected. This would make it impossible for the Tribal IV-D agency to correctly adjust the arrearage to give the noncustodial parent credit for the tax refund offset. Another commenter believes the Internal Revenue Services (IRS) statute at 26 U.S.C. 6103 sufficiently provides for confidentiality limitations for States to disclose information to Tribes and States. Tribal IV-D agencies do not need another regulation to further burden negotiations with State IV-D agencies. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Policy Interpretation Question (PIQ) 07-02 addresses this. See 
                        <E T="03">http://www.acf.dhhs.gov/programs/cse/pol/PIQ/2007/piq-07-02.htm</E>
                        . A State may submit arrearages owed in Tribal IV-D cases for Federal tax refund offset if the following conditions are met: 
                    </P>
                    <P>1. The approved Tribal IV-D plan or plan amendment indicates that the Tribe has entered into a cooperative agreement with the State under § 309.60(b) and (c) for the State to submit arrearages owed in Tribal IV-D cases for Federal tax refund offset. The Tribe must submit as part of its Tribal IV-D plan or plan amendment copies of any such agreement. The regulations governing Tribal IV-D programs at § 309.35(d) require that after approval of the original Tribal IV-D program application, all relevant changes required by new Federal statutes, rules, regulations, and Department interpretations are required to be submitted so that the Secretary may determine whether the plan continues to meet Federal requirements and policies. </P>
                    <P>2. The cooperative agreement between the Tribe and State includes a statement that the Tribal IV-D program will comply with all safeguarding requirements with respect to Federal tax refund offset in accordance with § 309.80, section 454(26) of the Act and the Internal Revenue Code 26 U.S.C. 6103, which prohibits the release of IRS information outside of the IV-D program. </P>
                    <P>3. The Tribal IV-D plan provides evidence that the Tribe's application for IV-D services under § 309.65(a)(2) includes a statement that the applicant is applying for State IV-D services for purposes of submitting arrearages for Federal tax refund offset. </P>
                    <P>
                        <E T="03">9. Comment:</E>
                         One commenter says there must be an easy-to-use procedure for individuals misidentified by child support database programs to correct agency records and also requests that this rule provide for a system to flag errors where files are “mixed.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         If an individual believes he or she has been misidentified by the IV-D system, he or she should contact the appropriate IV-D office. The IV-D program should fix the error as soon as possible. These regulations do not go into the details of step-by-step State case processing that would make such a proposal appropriate. 
                    </P>
                    <P>
                        <E T="03">10. Comment:</E>
                         One commenter requests that language in the preamble to the proposed rule be incorporated into the actual regulation. Page 60044, column 3 says “programs receiving confidential information may use the information only for the purpose for which it was disclosed and may not redisclose the information.” However, this restriction on redisclosure is not in the text of the proposed rule. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This regulation is for title IV-D programs and we cannot regulate other programs once information is disclosed. However, State IV-D programs must make clear to those authorized to receive child support data, the limited purpose for which information may be used. Improper use or disclosure would be governed by State and Federal statutes that impose penalties for such disclosure. 
                    </P>
                    <P>
                        <E T="03">11. Comment:</E>
                         One commenter says there is no legislative history that Congress contemplated expanding access to State databases and records beyond the IV-D program or beyond what is otherwise permitted by State law. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The provisions relating to the State PLS implement section 454(8) of the Act, 42 U.S.C. 654(8), which requires each State plan for child support enforcement to provide that the State will: (1) Establish a service to locate parents utilizing all sources of information and available records including the Federal PLS; and (2) be subject to the privacy safeguards in section 454(26) of the Act, 42 U.S.C. 654(26) and disclose only the information described in sections 453 and 463 of the Act to the authorized persons specified in those sections. This language authorizes a system of disclosure of State data based on the system in place for the Federal PLS. We have revised the regulation to recognize the possibility of more restricted access to State data by incorporating the language “in accordance with State law.” 
                    </P>
                    <P>
                        <E T="03">12. Comment:</E>
                         One commenter is concerned that States are not informing individuals when disclosure of their Social Security Number (SSN) to another source will occur and by collecting noncustodial parents' SSNs from a third party source. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States are required to comply with section 7(b) of the Privacy Act and its disclosure requirements (5 U.S.C. 552a). In all IV-D cases, the Privacy Act requires a Federal, State, or local government agency to provide certain information to the individual from whom a SSN is requested by the agency. 
                    </P>
                    <P>
                        <E T="03">13. Comment:</E>
                         One commenter says that notice and due process are required when States use, release, or enter data into State PLS and Federal PLS computer interface records on individuals who do not need to be located for purposes of child support. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Access to personal data covered by the regulation is authorized as explicitly provided for in Federal title IV-D statute. 
                    </P>
                    <HD SOURCE="HD2">Section 302.35, State Parent Locator Service </HD>
                    <P>
                        <E T="03">1. Comment:</E>
                         Two commenters have major concerns with this section. One would like to know the reason for these amendments, opposes the requirement that the State PLS provide information to requestors with regard to in-state sources, and strongly recommends that references to access and release of in-state State PLS information be deleted from the proposed regulation. The other commenter is concerned with this section and believes the regulation erodes the capability of the child support program to safeguard confidential information. The regulation creates a presumption, not supported by law, that non-IV-D entities may access in-state resources. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A State/Federal workgroup, established after the passage of the Personal Responsibility and Work Opportunity Reconciliation Act, 
                        <PRTPAGE P="56428"/>
                        recommended that these regulations be promulgated in order to clarify the statutory limitations of sharing data. In response to comments we have revised the regulation to provide State searches only to the extent authorized by State law. With regard to in-state sources, section 454(8) of the Act says a State shall be subject to the privacy safeguards in section 454(26) of the Act, 42 U.S.C. 654(26). 
                    </P>
                    <P>
                        <E T="03">2. Comment:</E>
                         One commenter asks why the regulation does not clearly tie authorized persons to the authorized purposes for which they may receive locate information, addressing persons and in separate subsections. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree. The authorized persons and purposes are clearly stated in the regulation and are identical to those of the Federal PLS. Appendix A displays this set of authorities. 
                    </P>
                    <P>
                        <E T="03">3. Comment:</E>
                         One commenter would like to eliminate the reference in Appendix A that says “No automated system” for Authorized Purpose B, C, and D. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This Appendix and others have been revised and/or added. Any limitation of disclosure of automated systems data is required by section 454A of the Act. 
                    </P>
                    <P>
                        <E T="03">4. Comment:</E>
                         One commenter proposes adding a section to this provision that requires maintenance of an audit log to deter employee misuse of databases. Audit logs hold individuals responsible for their use of personal information databases and would record who accesses personal information, and the purpose for which it was accessed. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Federal requirements do not prescribe this level of mandate on State responsibilities. It is up to the State to implement necessary and appropriate methods to ensure that access and disclosure is for proper purposes and only to authorized persons. States have discretion, however, to implement similar audit procedures. 
                    </P>
                    <P>
                        <E T="03">5. Comment:</E>
                         One commenter recommends moving § 302.35(b) closer to § 302.35(a) to clarify that the Federal PLS is considered part of the State PLS for IV-D cases and for authorized non-IV-D purposes under this section. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Federal PLS is not part of the State PLS. Subparagraph (b) is based on the requirement that requests for Federal PLS data must flow through the State PLS. 
                    </P>
                    <P>
                        <E T="03">6. Comment:</E>
                         One commenter asks for confirmation that together §§ 302.35(a)(1) and (2) and 302.35(c) limit the use of the State PLS for IV-D cases to only IV-D purposes but permits the use of the State PLS for non-IV-D individuals or non-IV-D cases for the authorized non-IV-D purposes. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 302.35(a)(1) and (2) limit the use of the State PLS for IV-D cases to only IV-D purposes but permits the use of SPLS for non-IV-D individuals or non-IV-D cases for the authorized non-IV-D purposes. 
                    </P>
                    <P>
                        <E T="03">7. Comment:</E>
                         One commenter suggests that the title of paragraph (1) be changed to “For IV-D cases and IV-D purposes” for clarity. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         For clarity, we have revised the title of paragraphs (1) and (2) to distinguish between IV-D requests and non-IV-D requests. 
                    </P>
                    <P>
                        <E T="03">8. Comment:</E>
                         One commenter asks that the Office clarify why locate information, restricted for custody and visitation purposes to the most recent address and place of employment, requires such strict confidentiality where there is not a family violence indicator or other information giving rise to safety concerns for the parties. The address of a litigant to a court proceeding is considered public information and necessary for the case to proceed. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The restriction is statutory. Section 463(c) of the Act [Use of Federal PLS in connection with the enforcement or determination of child custody and in cases of parental kidnapping of a child] contains the restriction “Only information as to the most recent address and place of employment of any parent or child shall be provided under this section.” 
                    </P>
                    <P>
                        <E T="03">9. Comment:</E>
                         In addition to using the State PLS for locating either parent for IV-D purposes, one commenter asks that the agency also be able to use the State PLS for locating the child for IV-D purposes. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         IV-D agencies already have that authority with the Federal PLS. Section 453(a)(2)(iii), which states “to whom such an obligation is owed” includes the child. However, in response to this comment, we have added “children” to § 302.35(a)(1). 
                    </P>
                    <P>
                        <E T="03">10. Comment:</E>
                         One commenter points out what he or she believes to be a mistake: “Child” is included in Appendix A to § 302.35 under “Authorized Purpose” but is not included in the preamble or in the regulation. Another commenter suggests that this section of the regulation be revised by deleting the words “noncustodial parents” and inserting “a parent or child.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree and have included reference to custodial parents, noncustodial parents and children in both the preamble and the regulation at § 302.35. 
                    </P>
                    <P>
                        <E T="03">11. Comment:</E>
                         One commenter suggests substituting the word “parties” for “parents” since the IV-D or a cooperating agency may be enforcing a support order in a IV-D case for a custodial party other than a parent. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The statute uses the term parent, although we recognize there may be instances where children are in the custodial care of individuals other than their parents. 
                    </P>
                    <P>
                        <E T="03">12. Comment:</E>
                         One commenter points out that the reference to § 303.3 in the second sentence of § 302.35(a)(1) creates confusion because § 303.3 only addresses locate requirements for noncustodial parents in IV-D cases. The commenter assumes this is not the intent of the proposed regulation and, to avoid confusion, recommends removing the second sentence of § 302.35(a)(1) because the first sentence clearly conveys the intent of the subsection. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree and have removed the reference to § 303.3, which only applies to location of noncustodial parents in IV-D cases. 
                    </P>
                    <P>
                        <E T="03">13. Comment:</E>
                         Several commenters had comments relating to the use of the State Disbursement Unit in non-IV-D case situations. Since it is a IV-D function to disburse support to custodial parents in non-IV-D cases subject to income withholding, can a IV-D program use the State PLS or Federal PLS to locate a non-IV-D custodial parent for purposes of disbursing child support? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Yes, this would be a legitimate use of locate sources for IV-D agencies seeking to locate such custodial parents in non-IV-D cases subject to income withholding. 
                    </P>
                    <P>
                        <E T="03">14. Comment:</E>
                         One commenter points out a contradiction in the regulation regarding the use of in-state locate sources. On the one hand, § 302.35(a)(2) provides a mechanism for States to “opt out” of using in-state locate sources in response to a non-IV-D request if such use is “prohibited by State law or written policy.” Yet § 302.35(e) states “the State PLS shall disclose * * * information from in-state locate sources as required by this section and described in § 303.3(b)(1).” This latter language suggests that expanded access is required regardless of State law or written policy, which is contrary to the intent expressed in the preamble to the proposed rule, as well as the intent of the statute. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree. We have revised the language to provide in-state searches in accordance with State law. 
                    </P>
                    <P>
                        <E T="03">15. Comment:</E>
                         One commenter requests that the following terms be eliminated in the final rule: Non-IV-D individual(s); non-IV-D case(s); non-IV-
                        <PRTPAGE P="56429"/>
                        D request(s) and be replaced with “non-IV-D purpose” and another commenter asked that the Office provide a definition of non-IV-D purpose. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Reference to all four terms is appropriate each time a specific term is used in the regulation. Non-IV-D purpose is addressed in paragraph (d): the State PLS shall obtain location information under this section only for the purposes specified in paragraphs (d)(1) and (d)(2) of § 302.35. Section 453 of the Act provides statutory authority for using the Federal PLS for the purpose of locating any individual who has or may have parental rights with respect to a child, enforcing any State or Federal law with respect to the unlawful taking or restraint of a child; or making or enforcing a child custody or visitation determination. 
                    </P>
                    <P>
                        <E T="03">16. Comment:</E>
                         One commenter seeks confirmation that taken together, these sections mean that once a State establishes policy to define State PLS sources of information, any other data contained in the State's computerized support enforcement system may not be released under this section, regardless of the source of that information. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The State's computerized support enforcement system is not a source of information for the State PLS. Access to any data on the statewide automated system is limited in sections 454A(d) and (f) of the Act and 45 CFR part 307. Independently verified information may be released to those authorized to access and use the information. For example, if a State determines that an address is correct through a postal verification the State can share the information it acquired from the second source (the Post Office). 
                    </P>
                    <P>
                        <E T="03">17. Comment:</E>
                         One commenter strongly suggests that this proposed regulation be modified to make it clear that it is the Federal OCSE's responsibility to exclude IRS information, or MSFIDM information when in receipt of a non-IV-D request for FPLS information. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         If the State codes its requests correctly, (e.g., pk, ad, etc.), OCSE only returns appropriate information for that request. Please see the FCR Interface Guidance Document (Chart 6-14) 
                        <E T="03">http://www.acf.hhs.gov/programs/cse/newhire/library/fcr/fcr.htm</E>
                        . However, the State may have such information in its files and the State bears the responsibility to assure that only authorized information is released in response to a request. 
                    </P>
                    <P>
                        <E T="03">18. Comment:</E>
                         One commenter strongly suggests that there be a simple system set up for OCSE to receive formal requests from States (preferably online with a predefined outgoing and incoming data format) that would ensure that all requests to the Federal PLS are properly documented and the authorized information would be returned in a pre-defined format suitable to direct redisclosure to authorized requestors. The States' only duty would be to submit and return requests for information on behalf of non-IV-D authorized requestors. This would greatly enhance the security and confidentiality of this Federal requirement. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The FCR Interface Guidance Document, mentioned above, provides this service. For example, a Foster Care case locate-only code provides only authorized information but a request with a IV-D code provides much more data because the request is on a IV-D case. 
                    </P>
                    <P>
                        <E T="03">19. Comment:</E>
                         One commenter believes a better approach for this section would be for those individuals who desire child support services under the title IV-D program, including location services, to apply for services. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Federal statute at sections 453 and 454(8) of the Act require States to disclose certain information to authorized non-IV-D persons for authorized purposes. Such purposes includes access for locate purposes. There is no requirement that individuals apply for IV-D services to receive requested information. 
                    </P>
                    <P>
                        <E T="03">20. Comment:</E>
                         One State does not support requiring the State PLS to release information gathered from in-state sources to non-IV-D individuals unless there is a State law or policy prohibiting such a release as provided in § 302.35(a)(2)(i) and believes this requirement exceeds the authority granted in 42 U.S.C. 653(a)(2) which pertains only to Federal PLS information. Instead, the State favors a provision that authorizes the State PLS to release in-state source information only if permitted under State law or regulation. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We accept the commenter's position and have revised the regulation accordingly. 
                    </P>
                    <P>
                        <E T="03">21. Comment:</E>
                         Two commenters would like recognized that the preamble claims States have interpreted current law “to permit use of State resources for non-IV-D location purposes, including location for custody and visitation purposes” and notes that while a handful of States may permit broad access to State databases by private entities, these practices are not widespread and are not based on a common or settled interpretation of Federal law. Because some States have chosen to disclose State PLS and Federal PLS information to non-IV-D requestors should not be the basis of requiring all States to do so. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         See response to comment 20. 
                    </P>
                    <P>
                        <E T="03">22. Comment:</E>
                         A commenter says that if a State wishes to disclose State PLS data, it should have to have a written law or policy describing what it will disclose, to whom it will disclose it, and under what circumstances. In the absence of such a policy, State PLS data should not be disclosed to non-IV-D entities. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         It is up to the State to set standards for disclosure. 
                    </P>
                    <P>
                        <E T="03">23. Comment:</E>
                         One commenter believes the final regulation should acknowledge that there may be other State laws governing the disclosure of personal data to nongovernmental entities if any mention of State duty to provide State PLS data is retained. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the revised language “in accordance with State law” takes this into account. 
                    </P>
                    <P>
                        <E T="03">24. Comment:</E>
                         One commenter would like clarification on the reason for the restriction that prevents the State PLS from searching the statewide computer system or providing a non-IV-D requestor with any information contained in the system. The commenter asks for the rationale behind this restriction and an explanation on how OCSE envisions compliance by States whose non-IV-D cases are part of their statewide computer system. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Access to information in the IV-D automated system is strictly limited by Federal statute. Section 454A of the Act restricts disclosure of information in a State IV-D automated system to purposes related to the administration of the IV-D program so non-IV-D requestors cannot get such information. 
                    </P>
                    <P>
                        <E T="03">25. Comment:</E>
                         One commenter says that the language referring to the support enforcement computer system (along with Appendix A) can be read to prohibit the release of information contained in the system even where that information was derived from non-IRS or non-MSFIDM sources and asks whether this was the intent. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Yes, this is the intent. The Federal statute at sections 454A(d) and (f) clearly restricts access to and disclosure of State automated child support system data. 
                    </P>
                    <P>
                        <E T="03">26. Comment:</E>
                         One commenter requests further explanation or clarification regarding the prohibition against releasing information from automated support enforcement systems to fulfill non-IV-D requests. Clarification is needed because any information received in the course of IV-D program business is typically 
                        <PRTPAGE P="56430"/>
                        registered in such system; therefore, exactly what may be legally disclosed under § 302.35(a)(2)(ii) is unclear. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 454A of the Act does not authorize access to State systems for non-IV-D purposes. Therefore, a State may only seek or locate information in a non-IV-D case directly from the State PLS or from the Federal PLS and disclose that data to a non-IV-D requestor. (Also see # 27. below.) 
                    </P>
                    <P>
                        <E T="03">27. Comment:</E>
                         One commenter seeks clarification that the idea of § 302.35(a)(2)(ii) is that if a State receives a non-IV-D request, it may not look to any information “existing” on its system but rather must conduct State PLS and Federal PLS searches for information and only the information resulting from those searches could be released, as authorized. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Yes, if a State receives a non-IV-D request, it may not look to any information “existing” in its system but rather must conduct State PLS and Federal PLS searches for information and only the information resulting from those searches can be released. 
                    </P>
                    <P>
                        <E T="03">28. Comment:</E>
                         One commenter notes that § 302.35(c)(3) indicates that the State PLS may use some sources of data for non-IV-D location requests. However, it is noted in other parts that the State PLS shall not release information from the computerized support enforcement system. Many of the location sources the State agency uses feed into, and become part of, the computerized support enforcement system. Is the regulation forbidding the use of the CSE system to access otherwise permissible State sources of information? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulation prohibits release of information residing on the State's computerized support enforcement system, unless explicitly authorized. States may only share information on their automated system with authorized entities under 45 CFR Part 307. The State PLS may use the automated system to seek information from other sources as part of its location efforts in IV-D cases. 
                    </P>
                    <P>
                        <E T="03">29. Comment:</E>
                         One commenter proposes new language for § 302.35(a)(2)(ii) “* * * IRS information or financial institution data match information relating to a financial account * * *” Incorporating this language would allow other information (such as address information) from MSFIDM to be released pursuant to a non-IV-D request. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are not incorporating the proposed change because of the need to safeguard all data received from a financial institution data match. 
                    </P>
                    <P>
                        <E T="03">30. Comment:</E>
                         One commenter wants IV-B/IV-E agencies to be able to view limited, address-related data from other States' IRS and financial institutions if such information could assist in locating the parent or person who could be a child's parent and is otherwise not available in any other system. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There is no authority under title IV-D of the Act or the Internal Revenue Service Code to allow this. 
                    </P>
                    <P>
                        <E T="03">31. Comment:</E>
                         One commenter disagrees with prohibiting the State PLS in non-IV-D requests from disclosing information from the computerized support system because 42 U.S.C. 654(8) mandates that States use “all sources of information and available records” to locate parents regardless of whether they are involved in a IV-D case. The State could not defend such a policy to its judges and asks why such a prohibition in this rule is necessary. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A State's defense would be that Federal law prohibits such disclosure. Section 454A(f) of the Act specially governs data in IV-D automated systems and strictly limits disclosure. 
                    </P>
                    <P>
                        <E T="03">32. Comment:</E>
                         One commenter asks what is the statutory basis for prohibiting disclosure of MSFIDM information for all non-IV-D requests. Because Federal statute limits use of financial record information from a financial institution “only for the purpose of * * * establishing, modifying or enforcing a child support obligation”, it appears FIDM information could be used for both IV-D and non-IV-D child support purposes. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         IV-D programs have statutory responsibility to safeguard confidential information not specifically authorized for release under section 453 of the Act. The IV-D program has broad access to certain data of all sorts from myriad sources. We believe it is essential to strictly limit access to data. Section 469A of the Act only provides for nonliability for financial institutions for disclosures to a State Child Support Enforcement agency or to the Federal PLS for purposes of section 466(a)(17) of the Act. The statute provides that the information be used only for IV-D purposes. 
                    </P>
                    <P>
                        <E T="03">33. Comment:</E>
                         One commenter supports while another seeks clarification that § 302.35(a)(2)(ii) prohibits release of information from the State's computerized support enforcement system even if that information is obtained from non-IRS or non-MSFIDM sources. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States may not release any information in a State's IV-D automated system except to specifically authorized requestors and for purposes related to the administration of the IV-D program. Non-IV-D access is not authorized under section 454A of the Act. See § 307.13. 
                    </P>
                    <P>
                        <E T="03">34. Comment:</E>
                         One commenter says that because States can not transmit non-IV-D requests to another State, an authorized requestor would be required to make multiple requests. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This is correct. However, an authorized requestor can obtain certain information from the Federal PLS which may contain some of the State data, namely the employment data. 
                    </P>
                    <P>
                        <E T="03">35. Comment:</E>
                         One commenter notes that while § 302.35(a)(2)(iii) specifies that for non-IV-D location requests, the IV-D program need not make subsequent location attempts if a location attempt fails, the preamble discussion says that a relocation attempt would be required if a requestor demonstrates that there is reason to believe new information exists. The proposed rule should clearly state that a relocation attempt is a requirement in this circumstance, if that is the intent. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have changed the language to clarify that no subsequent attempt to locate is necessary unless a new request is submitted. 
                    </P>
                    <P>
                        <E T="03">36. Comment:</E>
                         One commenter asks under what circumstance the State PLS can provide Federal PLS with information. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The State IV-D program is required to provide State Directory of New Hires and Federal Case Registry information. In addition, under section 453(e), the Federal PLS may seek information from any of the “departments, agencies, or instrumentalities of the United States or of any State.” 
                    </P>
                    <P>
                        <E T="03">37. Comment:</E>
                         Child welfare staff in one State request a broader interpretation of § 302.35(a)(2)(iii), whereas, in order to facilitate the administration of programs under titles IV-B or IV-E, State PLS and Federal PLS locate attempts should occur at the same frequency as for IV-D programs (quarterly, at a minimum, or when new information leads are received). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         State IV-D agencies are not required to repeat locate results for non-IV-D entities unless a new request is submitted. However, States are free to establish the extent and frequency of authorized IV-B or IV-E locate requests. 
                    </P>
                    <P>
                        <E T="03">38. Comment:</E>
                         One commenter believes that because § 302.35(a)(2)(iv) prohibits making State PLS requests separate from Federal PLS requests in non-IV-D cases, there is no need to develop a separate standard for the State PLS. Another commenter requests clarification that even if it can get the 
                        <PRTPAGE P="56431"/>
                        requested information from State sources, the State must use the Federal PLS. If so, why would that be necessary? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Based on comments received and the desire to allow States to retain the flexibility to conduct either State PLS or Federal PLS searches (or both) we have removed § 302.35(a)(2)(iv) in the final rule. If a State successfully uses State PLS sources and locates the individual sought, there may be no need to submit a request to the Federal PLS. However, if the IV-B or IV-E agency wants a Federal PLS request, the State must honor that request. 
                    </P>
                    <P>
                        <E T="03">39. Comment:</E>
                         If a IV-D caseworker is aware of a new address for a noncustodial parent when the IV-E agency requests the address for an authorized purpose, can the IV-D program provide the address directly or must the agency conduct an independent State PLS search? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         If the information is already known, the IV-D agency is authorized to release the information under § 307.13(a)(3) and section 454A(f)(3) of the Act. This permits exchanging information with State Medicaid agencies and other programs designated by the Secretary or other State or Federal agencies to carry out this part, subject to section 6103 of the Internal Revenue Code of 1986. 
                    </P>
                    <P>
                        <E T="03">40. Comment:</E>
                         One State recommends that States retain the ability to designate other IV-D offices within the State to submit requests to the Federal PLS when location services are needed instead of requiring a “central” State PLS. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We tried to accommodate multiple State PLS locate interfaces in the past; however, from a cost-effectiveness and quality control standpoint, States now are limited to a central State PLS interface with Federal PLS. 
                    </P>
                    <P>
                        <E T="03">41. Comment:</E>
                         One commenter wants acknowledgment that although on the surface this seems to provide flexibility, § 302.35(c) sets up the strong possibility of inconsistency among States and will allow forum shopping for the best deal by “attorneys or agents of the child.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 302.35(a)(2)(i) allows access to the State PLS in accordance with State law. As such, State practices may vary. We support State flexibility in this regard. 
                    </P>
                    <P>
                        <E T="03">42. Comment:</E>
                         One commenter asks whether there is any authority that supersedes Federal law on releasing information only to persons authorized under sections 453 and 463 that would require IV-D agencies to comply with a request from the Department of Homeland Security (DHS) since DHS is not an “authorized person” under sections 453 or 463 of the Act. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There is no authority to override sections 453 and 463 of the Act. 
                    </P>
                    <P>
                        <E T="03">43. Comment:</E>
                         In the final regulations one commenter requests that States have the ability to deny requests from non-IV-D entities which have a track record of obtaining information for purposes beyond those contemplated by the statute as well as those who have not properly safeguarded the information they have obtained. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A fine for misuse of the NDNH in section 453(l) of the Act can be applied. Also, § 303.21(f) gives ability for State to impose fines or other criminal or civil sanctions. Finally, attestation is designed to protect/alleviate this issue. A IV-D agency should document instances of abuse and if a non-IV-D entity is known to abuse access to data, access should be denied and the reason noted. States should have written policy which may provide guidance in this area. 
                    </P>
                    <P>
                        <E T="03">44. Comment:</E>
                         One commenter would like confirmation regarding the extent to which staff determining food stamp eligibility have access to confidential data or location data maintained or obtained by the IV-D program. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Food Stamp agencies have access to the State Directory for New Hires for purposes of verifying eligibility for the program. See 42 U.S.C. 653A(h)(2). 
                    </P>
                    <P>
                        <E T="03">45. Comment:</E>
                         Two commenters suggest that Tribal IV-D agencies be specifically included as an “authorized person” in § 302.35(c)(1). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Tribal IV-D agencies have access to the State PLS if they request assistance from a State IV-D agency and submit a referral for case information. The State agency will submit the case to the State PLS as part of its responsibilities with respect to the case. 
                    </P>
                    <P>
                        <E T="03">46. Comment:</E>
                         One commenter understands the proposed change to permit a court to obtain location information for the purposes of establishing a support order, even in a non-IV-D case. Yet, the court need not attest to its intent; whereas an attestation is required from a resident parent, legal guardian, attorney, or agent. Is this an oversight or an intentional distinction? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         It is intentional because courts are governmental entities. The attestation is required of private citizens or nongovernmental entities. 
                    </P>
                    <P>
                        <E T="03">47. Comment:</E>
                         One commenter recommends changing the term “aid” to “assistance as defined at 45 CFR 260.31” in § 302.35(c)(3). This way, there will be a clear national policy in this area. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have changed the term “aid” to “assistance” in § 302.35(c)(3) because that is the terminology used in the statute. We have not cited IV-A regulation, however, since it could change in the future. 
                    </P>
                    <P>
                        <E T="03">48. Comment:</E>
                         One commenter asks how long must the locate application, attestation, and evidence of authorization be maintained by the State PLS? Does the standard three-year record retention policy apply to these documents? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The three-year record retention rule, as stated in 45 CFR 92.42(b), applies to these documents. 
                    </P>
                    <P>
                        <E T="03">49. Comment:</E>
                         One commenter would like to eliminate the reference to a child not receiving aid under title IV-A of the Act in § 302.35(c)(3) and wants corresponding changes to be made to Appendix A to § 302.35(c)(3). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 453 of the Act requires the inclusion of this exception. 
                    </P>
                    <P>
                        <E T="03">50. Comment:</E>
                         Three commenters ask if a requestor attests to the purpose and use of information that is later discovered to be fraudulent in nature; will the IV-D program be found liable by OCSE? One commenter asks what the penalties are if a requestor violates the attestation or submits a fake “authorization”? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The IV-D agency would not be responsible if it had the attestation on file. Any requestor who violates requirements for receiving Federal PLS information would be subject to any Federal or State penalties. 
                    </P>
                    <P>
                        <E T="03">51. Comment:</E>
                         One commenter asks whether a State is required to pass special laws imposing penalties for failure to comply with the provisions of the attestation. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States have discretion to pass such laws. 
                    </P>
                    <P>
                        <E T="03">52. Comment:</E>
                         One commenter agrees with the proposed rule requiring the requestor to provide evidence of being the legal guardian, attorney of the child or agent of the child. However, he or she suggests if the requestor is a resident parent, the requestor only attest to being so rather than providing evidence. It would be difficult for the State PLS to identify proof of resident parent status otherwise. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter and have changed the language in § 302.35(c)(3)(iii) to require the resident parent to attest to being the resident parent. 
                    </P>
                    <P>
                        <E T="03">53. Comment:</E>
                         One commenter asks whether private child support enforcement agencies have to provide “evidence of a valid contract” with each request for locate or may the IV-D 
                        <PRTPAGE P="56432"/>
                        program permit a private child support enforcement agency to provide an annual, blanket attestation that a valid contract exists for each request made during the year? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The private child support enforcement agency may not provide an annual blanket attestation that a valid contract exists for all requests made during that year. 
                    </P>
                    <P>
                        <E T="03">54. Comment:</E>
                         One commenter recommends a change to § 302.35(c)(3)(iii) so that both attorneys and agents who allege that they are representing a child are required to provide a valid contract that meets any requirements under State law or policy for acting as an agent of the child. Otherwise, the regulation will violate the statutory authority on which it is based. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The statute does not specify any proof or evidence that must be provided. Section 302.35(c)(3)(iii) indicates that an authorized person provide evidence that the requestor is the legal guardian, attorney, or agent of a child not receiving assistance under title IV-A, and if an agent of such a child, evidence of a valid contract that meets any requirements in State law or written policy for acting as an agent. 
                    </P>
                    <P>
                        <E T="03">55. Comment:</E>
                         One commenter believes that because of the potential for disclosure to unauthorized entities, § 302.35(c)(3)(iii) should require the requestor to furnish a copy of the actual contract, not just “evidence of a valid contract.” Another commenter wants clarification on what evidence is other than a copy. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Evidence of a valid contract may be defined by the State. Therefore, a State may require the requestor to furnish a copy of the actual contract. 
                    </P>
                    <P>
                        <E T="03">56.</E>
                         One commenter suggests adding the words “of the child” after the word “agent” in § 302.35(c)(3)(iii) in order to track the statute and make clear that the only agents who are authorized persons are agents of the child, not of a parent. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter and have revised the regulation to reflect the statutory language. 
                    </P>
                    <P>
                        <E T="03">57.</E>
                         One commenter believes that § 302.35(c)(3)(iii) will be hard to meet for a requestor who claims to be “an agent of such a child.” Existing State laws “for acting as an agent” may not be clear or complete to support this process. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This is an issue for a State to address. 
                    </P>
                    <P>
                        <E T="03">58. Comment:</E>
                         Two commenters question whether private collection agencies (PCAs) and attorneys meet the statutory definition of “authorized persons” and are concerned about giving private collection agencies access to information. There is no clear definition of “attorney or agent of the child” in the regulations or in statute and in one State, PCAs do not fall within this definition. Most private attorneys in child support matters represent a parent, not a child. PCA contracts are entered into by a custodial parent in her (sic) own right, not as the child's legal agent. An agency relationship is created by expressed or implied contract or by operation of law, and generally is governed by State law, not Federal law. In addition, it is a settled matter of black letter law that a contract must be between competent parties and that a minor is under the age of legal competence. Therefore, a custodial parent's contract with a PCA does not make the PCA an “agent of the child” for purposes of locate request under section 453 of the Act. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         AT-02-04 clarifies policy and procedures for providing Federal PLS locate services to persons who qualify as an “an agent of the child” for child support purposes. The Action Transmittal lists the definitions of “authorized persons” set forth in section 453(c)(1) through (3) of the Act, including the resident parent, legal guardian, attorney, or agent of the child. We do not read section 453 of the Act to prohibit a State from sending appropriate Federal PLS information to the resident parent in care of a PCA if, under State law, the PCA “stands in the shoes” of the resident parent and the State has evidence in the form of an attestation by the requestor, under § 302.35(c)(3)(iii) that the parent, in fact, has authorized the PCA to act on his or her behalf. 
                    </P>
                    <P>
                        <E T="03">59. Comment:</E>
                         One commenter wants changes made to reflect that States should be required to develop standards and protocols for refusing to provide information to non-IV-D entities when such entities fail to safeguard the information they obtain. These standards should include provisions for notifying such entities of what restrictions apply, what protections they must have in place, and what the consequences of failure to safeguard the information are. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that such standards are reasonable but leave such action to State discretion. 
                    </P>
                    <P>
                        <E T="03">60. Comment:</E>
                         One commenter believes that the administrative cost associated with developing and implementing a fee for non-IV-D entities would far outweigh any benefit. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The fee for Federal PLS services is a statutory requirement under section 453(e)(2) of the Act. 
                    </P>
                    <P>
                        <E T="03">61. Comment:</E>
                         One commenter asks whether any fee collected for the State's PLS services needs to be claimed as program income. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Any fee collected for the State's State PLS services is considered program income under 45 CFR 304.50 and must be reported. 
                    </P>
                    <P>
                        <E T="03">62. Comment:</E>
                         One commenter seeks clarification that the title: “To locate an individual who may be the parent of a child in a IV-D or non-IV-D case” refers to locating the custodial as well as noncustodial parent. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The final rule changes the title of § 302.35(d)(1) to: “To locate an individual with respect to a child in a IV-D, non-IV-D, IV-B, or IV-E case” in order to better reflect the statutory language in section 453(a)(2)(A) of the Act. This section covers locating both the custodial as well as the noncustodial parent. 
                    </P>
                    <P>
                        <E T="03">63. Comment:</E>
                         One commenter asks that the following “purpose” be added to § 302.35(d)(1): The State PLS shall locate individuals for the purpose of: facilitating informed and timely decisions about child welfare and permanency. The rationale is that locating parents for IV-B/IV-E purposes goes beyond just “establishing parentage” or “determining who has or may have parental rights to a child” as the language in the proposed rule currently reads. Another commenter asks if “for determining who has or may have parental rights with respect to a child” allow child welfare staff in the IV-B/IV-E agencies to request the IV-D program to locate and release address information for the purpose of placement of a child? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have inserted reference to title IV-B and IV-E to § 302.35(d)(1) to make clear that those agencies have access to State PLS locate functions for the purposes stated. The purpose of “determining who has or may have parental rights to a child” could be related to permanency planning. The language used is that which is stated in section 453 of the Act. To the second question, only persons as authorized under section 453(a)(2)(A) of the Act may request the IV-D program to locate and release address information for the purpose of placement of a child. 
                    </P>
                    <P>
                        <E T="03">64. Comment:</E>
                         Section 302.35(d)(1) states: the State PLS shall locate individuals for the purpose of establishing parentage, or establishing, setting the amount of, modifying, or enforcing child support obligations or for determining who has or may have parental rights with respect to a child. For these purposes, only information available through the Federal PLS or the State PLS may be provided. This 
                        <PRTPAGE P="56433"/>
                        information is limited to Social Security Number(s), most recent address, employer name and address, employer identification number, wages or other income from, and benefits of, employment, including rights to, or enrollment in, health care coverage, or asset and debt information. One commenter questions why there is a restriction that “for these purposes, only information available through the Federal PLS or the State PLS may be provided* * *”? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This restriction exists because § 302.35(d)(1) does not cover or authorize access to child support information on States' automated systems (which is addressed in 45 CFR Part 307). This section addresses Federal and State PLS use for IV-D and non-IV-D purposes. 
                    </P>
                    <P>65. Comment: Under § 302.35(d)(1), Federal PLS or State PLS information may be provided—but one commenter wants clarification as to whom this information can be provided—his/her own program or another State IV-D program? </P>
                    <P>
                        <E T="03">Response:</E>
                         Authorized persons include any State or local agency providing IV-D services as well as an authorized person identified in § 302.35(c). 
                    </P>
                    <P>
                        <E T="03">66. Comment:</E>
                         One commenter asks: does the phrase “for determining who has or may have parental rights with respect to a child” include grandparents or other persons who may have “parental rights”? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         No, section 453(c)(3) of the Act prevents this interpretation and means the parent of a child who would have a legal obligation to provide child support. 
                    </P>
                    <P>
                        <E T="03">67. Comment:</E>
                         One commenter asks that the section regarding the State Parent Locator Service be amended to incorporate a family violence provision as follows “Subject to the requirements of this section, the privacy safeguards required under section 454(26) of the Act, and the family violence indicator requirements under § 307.11(f)(1)(x) of this chapter, the State PLS shall disclose the following information to authorized persons for authorized purposes.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There is reference to section 454(26) of the Act in § 302.35(e): Subject to the requirements of this section and the privacy safeguards required under section 454(26) of the Act, the State PLS shall disclose the following information to authorized persons for authorized purposes. We have included reference to the domestic violence indicator in §§ 302.35(e) and 303.21. 
                    </P>
                    <HD SOURCE="HD2">Section 303.3, Location of Noncustodial Parents in IV-D cases </HD>
                    <P>
                        <E T="03">1. Comment:</E>
                         One commenter recommends changing the title of this section to include custodial parents as well as noncustodial parents (since the intent of §§ 302.35(a)(1) and 303.3 is to include custodial parents). Another commenter says that if the heading of this section is intended to only apply to noncustodial parents, the commenter has no concern with this as long as he or she can use the State PLS and other locate sources to locate custodial parents and children under § 302.35. If custodial parents and children are brought under § 303.3, the commenter asks that the applicability of the requirements, as they relate to custodial parents and children, be at the State's discretion. Yet another commenter seeks confirmation of whether there are specific location requirements for custodial parents. The commenter believes that the specific location requirements of proposed rule § 303.3 are more appropriately limited to noncustodial parents. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 303.3 only applies to locating the noncustodial parent. There are many instances in which States will have to locate custodial parents and children, 
                        <E T="03">e.g.</E>
                        , when requested and authorized, or to enable disbursement of collections. A State may choose to use the same approach as set in § 303.3 to do so but it is not mandated. 
                    </P>
                    <P>
                        <E T="03">2. Comment:</E>
                         One commenter seeks confirmation that Federal Financial Participation (FFP) will be made available to modify computer system functionality and provide on-going services to comply with the mandate to provide locate services for non-IV-D cases and believes FFP is appropriate and necessary. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         FFP is available to modify computer system functionality and provide ongoing services to comply with the mandate to provide locate services for non-IV-D cases. 
                    </P>
                    <P>
                        <E T="03">3. Comment:</E>
                         One commenter notes that when the title was changed from “location of absent parents” to “location of noncustodial parents” the meaning of the section was changed and as a result, tens of thousands of law-abiding parents' information is in State PLS, Federal PLS and National Directory of Child Support Orders databases. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The use of the term noncustodial parent in lieu of absent parent was made via regulatory changes in 1999 to reflect the same change made in the statute. The change was made to reflect that noncustodial parents are not (or should not be) absent from their children's lives. 
                    </P>
                    <P>
                        <E T="03">4. Comment:</E>
                         One commenter asks for clarification regarding what the differences are between searching State databases for information (which is encouraged) and releasing information from the system (which is prohibited). The commenter believes the sentence in § 303.3(b)(1) “Use appropriate location sources such as the Federal PLS; interstate location networks; local officials and employees administering public assistance * * *” conflicts with proposed § 302.35(a)(2)(ii) which states that the State PLS would not be able to, in response to a non-IV-D request, release information from the statewide system. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There is no conflict because § 303.3 applies only to IV-D cases and to locate efforts by the State IV-D agency in those cases. The restrictions on release of IV-D systems data does not apply to the IV-D agency or its use of program data for IV-D program purposes. The release of information in the statewide systems is restricted by section 454A of the Act. 
                    </P>
                    <P>
                        <E T="03">5. Comment:</E>
                         One commenter asks whether the Federal response changes (see comment #4 above) based on a State's opinion that recipients of food stamp benefits must cooperate with the IV-D program. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         If there is a IV-D case involving a food stamp recipient who is required to cooperate with the IV-D agency, access to data on the statewide automated system is authorized for authorized persons and IV-D purposes. 
                    </P>
                    <P>
                        <E T="03">6. Comment:</E>
                         One commenter urges the agency to disclose to the public what tools and data sources are going to be employed to locate individuals. It is suggested that these tools and data sources be disclosed in the 
                        <E T="04">Federal Register</E>
                        , giving individuals time to comment on the accuracy and reliability of the tools used. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States may disclose information regarding State tools and data sources. The Systems of Record used by the Federal PLS, the National Directory of New Hires and the Federal Case Registry, are published in the 
                        <E T="04">Federal Register</E>
                         and updated as necessary in accordance with Federal law. 
                    </P>
                    <HD SOURCE="HD2">Section 303.20, Minimum Organizational and Staffing Requirements </HD>
                    <P>
                        <E T="03">1. Comment:</E>
                         One commenter is troubled about the lack of actual standards regarding proper staffing of the State PLS. In particular, the investigative process behind non-IV-D requests will not be adequately staffed 
                        <PRTPAGE P="56434"/>
                        without some guidance, especially considering budget cuts. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The State determines how the State PLS is operated and there are various degrees of automation for access of data. We do not think it is appropriate to regulate this because of the different State PLS operations that take place among the States. 
                    </P>
                    <HD SOURCE="HD2">Section 303.21, Safeguarding and Disclosure of Confidential Information </HD>
                    <P>
                        <E T="03">1. Comment:</E>
                         One commenter asks why the Office has chosen to issue safeguarding rules for IV-D data now if it did not do so before. In most States there is an established body of privacy law that governs access to personal data maintained by State agencies and limits its use and disclosure; and at the time PRWORA was enacted, there were no discussions about preempting such bodies of State law by Federal statute. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States requested guidance regarding access to data because of the myriad of access requirements and prohibitions enacted as part of PRWORA. The requirements of section 454(8) of the Act state that States “shall * * * disclose only information described in sections 453 and 463 to the authorized persons specified in such sections for the purpose specified in such sections.” 
                    </P>
                    <P>
                        <E T="03">2. Comment:</E>
                         One commenter raises concern regarding use of the word “confidential” and recommends that “personal identifying” information be substituted for “confidential” as it better captures the meaning of the information discussed in these proposed regulations. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the term “confidential” which is used in the statute is more consistent and appropriate for implementing the regulation. 
                    </P>
                    <P>
                        3. 
                        <E T="03">Comment:</E>
                         One commenter requests that, within the definition of “confidential information”, “employment information” be changed to “employer name and address” in order to be less broad and more consistent with § 302.35. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Access to data through the Federal PLS and the State PLS in § 302.35 is not restricted to employer name and address. 
                    </P>
                    <P>
                        <E T="03">4. Comment:</E>
                         One commenter requests a specific list of factors by which an individual can be identified because the phrase “not limited to” in § 303.21(a) is vague. As currently written, a State could violate the regulation or get differing interpretations by different workers. Suggested change: “Confidential information means any information relating to a specified individual or an individual who can be identified by reference through any other nonconfidential source by reference to one or more factors specific to him or her, including, but not limited to, the individuals SSN, residential or mailing addresses, employment information, and financial information. Excluded as factors specific to him or her are numbers unique to the computerized child support enforcement system for individuals, as such a number cannot be used as an identifying factor outside of access to the confidential computerized child support enforcement system.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have not included this clarification in the regulation. Since the State establishes the IV-D case numbers and determines when and how they are used, we are unable to conclude that such numbers could not be identifying information. We question why there would be a need to release IV-D case numbers to an entity outside the administration of the IV-D program. 
                    </P>
                    <P>
                        <E T="03">5. Comment:</E>
                         One commenter questions the intent of § 303.21(a) and recommends allowing States to release payment-related information in accordance with State law. The commenter believes the last sentence “the amount of support ordered and the amount of support collection are not considered confidential information for purposes of this section” opens up the IV-D agency to having to provide payment records to anyone who makes a request whether or not the requestor is associated with the case or intends to use the information for child support related purposes. One commenter says the definition of “confidential information” does not include the support-ordered amount or the amount of a support collection. Does this mean that if the IV-D agency/SDU is approached by an outside entity or “interested third party” who wants the names and collections of persons, that the IV-D agency/SDU is not prohibited from providing such information? (Assume the third party is not able to help IV-D program establish and enforce.) What if the interested third party has a name and wants to know the corresponding charges and payments against the obligation? One commenter is concerned with the last sentence in § 303.21(a) that appears to make payment histories and arrearage records, which contain amounts of support ordered and collection amounts, a part of the public record, and would like clarification as to the difference between that and “financial information” which is confidential. The commenter does not understand the meaning of this apparent contradiction. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that the language in the proposed rule is confusing. We deleted the language “The amount of support ordered and the amount of a support collection are not considered confidential information for purposes of this section.” Interested third party may not receive payment histories and arrearage records. 
                    </P>
                    <P>
                        <E T="03">6. Comment:</E>
                         One commenter asks: in order to balance the need for accurate payment records and meet IV-D and IRS requirements, is it acceptable to show an IRS payment amount in these payment records, but not to identify the payment as an IRS receipt? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe it is acceptable for child support purposes but this is ultimately governed by Internal Revenue Service Code. 
                    </P>
                    <P>
                        <E T="03">7. Comment:</E>
                         One commenter believes that if the source of the information on the document to be released cannot, on the face of the document, be linked to the Federal PLS, Internal Revenue Service (IRS), the National Directory of New Hires (NDNH), or other protected source, there is no need to restrict release of a copy of a document that is a matter of public record. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree. The statutory provisions restrict disclosure of specific information whether or not the source is identified. 
                    </P>
                    <P>
                        <E T="03">8. Comment:</E>
                         One commenter asks that the following sentence be added to the end of § 303.21(a): “Information required by state law to be released to designated persons or entities is not considered ‘confidential’  if the information has been independently verified or furnished from a source that is not protected by Title IV-D of the Social Security Act.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The statement as proposed is too broad because it could be interpreted to include personal identifying information on the statewide automated system. 
                    </P>
                    <P>
                        <E T="03">9. Comment:</E>
                         One commenter would like confirmation that an individual's name would be considered “confidential information” as it would be information relating to a specific individual who could be identified. If the individual's name is confidential and the State is not able to release the name, under what circumstances could we release the amount of support ordered/collected without the name? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Confidential information about individuals may not be disclosed outside the administration of the IV-D program. The State could release aggregate amounts of support collected in the State—e.g., $X for FY 2006. 
                    </P>
                    <P>
                        <E T="03">10. Comment:</E>
                         One commenter would like noted that if a IV-D program remains unable, under IRS rules, to release the amount of the Federal Tax Refund Offset payment to non-IV-D 
                        <PRTPAGE P="56435"/>
                        entities, the program is severely hampered in our ability to report collection obligation compliance information to courts, custodial parties, etc. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We continue to work with the Department of the Treasury regarding the release of offset collection information. The Department of Treasury has offered to the Congress suggested legislation that would amend the Internal Revenue Code regarding this concern and the Department of Health and Human Services supports the proposal. 
                    </P>
                    <P>
                        <E T="03">11. Comment:</E>
                         One commenter is concerned that the requirement that “any official with whom a cooperative agreement * * * has been entered into * * *” may not disclose confidential information received from the IV-D agency applies to agreements with the Clerks of Courts. Documents filed with the court, which have not been sealed, are open to inspection by such parties as the parties' creditors, commercial information brokers, and newspaper reporters. OCSE needs to recognize that this “open records” type of disclosure is permissible for Clerks of Courts despite this regulation. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 454(26) of the Act requires IV-D agencies to have in effect safeguards, applicable to all confidential information relating to proceedings or actions to establish paternity or to establish, modify or enforce support, that are designed to protect the privacy rights of the parties; and 45 CFR 302.12(a)(3) requires that those who receive information (such as through cooperative agreements) shall abide by those safeguards, because they are carrying out functions for the State IV-D agency. However, this regulation does not prohibit the disclosure of documents filed with the court, which have not been sealed and are open to inspection by such parties as the parties' creditors, commercial information brokers, and newspaper reporters. 
                    </P>
                    <P>
                        <E T="03">12. Comment:</E>
                         One commenter notes the general rule prohibiting disclosure of confidential information has an exception “as authorized by the Act and implementing regulations * * *.” Which implementing regulations does this refer to? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Title IV-D regulations at 45 CFR Parts 301-309 are the “implementing regulations” referenced. 
                    </P>
                    <P>
                        <E T="03">13. Comment:</E>
                         Several commenters would like clarification regarding the provision to not disclose confidential information obtained “in connection with the performance of IV-D functions outside the administration of the IV-D program.” What do these “IV-D functions outside of the administration of the IV-D program” refer to? Clarification is needed in order to reflect reality that information about the noncustodial parent may be used in any way necessary to establish paternity or establish, modify or enforce a child support order. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have clarified the intent of the language by restating it to read “may not disclose any confidential information, obtained in connection with the performance of IV-D functions, outside the administration of the IV-D program.” 
                    </P>
                    <P>
                        <E T="03">14. Comment:</E>
                         One commenter is concerned that the Supplementary Information section of this proposed rule adds a limitation not stated in the actual rule by saying “the IV-D program may only disclose the minimum amount of confidential information needed for the purpose provided.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have deleted the sentence “In making a disclosure under this provision, the IV-D program only disclose the minimum amount of confidential information needed for the purpose provided” as stated in the preamble describing Section 2: Safeguarding and Disclosure of Confidential Information. 
                    </P>
                    <P>
                        <E T="03">15. Comment:</E>
                         Two commenters believe § 303.21(d) is very restrictive, adds undue complexity to IV-D disclosure policies, and places an undue burden on States. For example, unless released within the purpose of the IV-D program, the State would need to figure out how to withhold IV-D information from courts without compromising the court's ability to administer the court case. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Disclosure of necessary information to the courts needed for purposes of the IV-D program is authorized except as limited by Section 6103 of the Internal Revenue Code. (Also see Q and A #10). 
                    </P>
                    <P>
                        <E T="03">16. Comment:</E>
                         One commenter asks that § 303.21(d) focus on specifying when disclosure of information to other government programs is permitted and for what purposes. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 303.21(d)(2) and (3) address circumstances under which information may be disclosed and for what purposes. 
                    </P>
                    <P>
                        <E T="03">17. Comment:</E>
                         One commenter is concerned that the section on authorized disclosures is made in such a general manner that most administrators responsible for safeguarding data privacy would have a great deal of difficulty making all the inferences required to actually share data. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have redesigned Appendix A for clarity. We reorganized it so it is laid out by authorized person followed by authorized purpose. We have developed a new Appendix B which addresses locate services in connection with enforcement or determination of child custody and in cases of parental kidnapping of a child. 
                    </P>
                    <P>
                        <E T="03">18. Comment:</E>
                         One commenter asks about the process of releasing confidential information in accordance with § 303.21(d)(1) under which information may be released “to such person or persons designated by the individual to whom the information relates or who is the custodial parent or legal guardian of a child * * *.” Should the designation be written or verbal? Are there time restrictions to the designation? Another commenter is concerned that § 303.21(d)(1) would require release of confidential information to anyone the individual designates, even though State statute allows only for minimal information to be released. The commenter recommends that the proposed rule be changed to not require release of the information and instead say “information may be released unless prohibited under State statute.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As indicated earlier in the preamble, this paragraph was removed as a separate authorized disclosure because under paragraph (c), disclosure to an individual would be allowed for IV-D purposes and would be governed by any safeguarding provision in State law as well. 
                    </P>
                    <P>
                        <E T="03">19. Comment:</E>
                         One commenter requests that the term “shall” be replaced with “may” because it is appropriate for States to have the flexibility to address, at the State level, how they respond to requests from an individual to release confidential information. For example, they would want to be able to determine, in certain situations, that it would be appropriate for them to deal directly with the customer, rather than a designee. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         See answer to #18. 
                    </P>
                    <P>
                        <E T="03">20. Comment:</E>
                         One commenter thinks the rule should make clear that a custodial parent or legal guardian may obtain information about the child in a case and may authorize release of information about the child. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This language has been removed. See answer to #18. 
                    </P>
                    <P>
                        <E T="03">21. Comment:</E>
                         One commenter would like to strike the prohibition against providing confidential information about an individual to any other individual involved in the case. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Federal and State IV-D programs are responsible for protecting sensitive personal information and broad authority as suggested by the commenter is inappropriate. 
                        <PRTPAGE P="56436"/>
                    </P>
                    <P>
                        <E T="03">22. Comment:</E>
                         One commenter believes the ability to provide locate information to a non-IV-D requestor conflicts with the broad prohibition against disclosing “confidential” information about one individual to another person involved in the case (as proposed in § 303.21(d)(1)). Several commenters are concerned that § 303.21(d)(2) creates a potential danger for overuse of this broad discretion. The proposed rule would essentially grant wide-open access to all the records and databases available to State child support programs, without any realistic ability for States to monitor use of this confidential data. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Proposed § 303.21(d)(1) has been removed from the final rule. Section 303.21(d)(2) (now § 303.21(d)(1)) has been limited to the specific programs which have been designated by the Secretary. These programs also have safeguarding rules. 
                    </P>
                    <P>
                        <E T="03">23. Comment:</E>
                         There were several commenters who questioned the mandatory rather than permissive disclosures in § 303.21(d)(2). One commenter wants to know why it is written as a mandate for the State IV-D program to disclose confidential information to all entities listed and believes the “permissive disclosure” allowed prior to February 1999 was more appropriate than a mandated disclosure. Another commenter would like the phrase “must” changed to “may” in § 303.21(d)(2) because the commenter believes a State should be authorized to disclose information and that it should not be a requirement to disclose the information. Such a change would also eliminate the need for the “to the extent that it does not interfere with the IV-D program meeting its own obligation” language in the same sentence. Three commenters point out that § 303.21(d)(2)(ii) would require IV-D agencies to report child abuse (or at least give the appearance of such), rather than making this reporting discretionary. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Former § 303.21 Safeguarding information, was removed with passage of Public Law 104-93. PRWORA was more permissive. Therefore, we have changed the language in § 303.21(d) from “must” to “may” and have added “upon request” for clarity at the beginning of paragraph (1). 
                    </P>
                    <P>
                        <E T="03">24. Comment:</E>
                         One commenter appreciates the fact this regulation does not mandate the manner or the timeframes by which the IV-D program must respond to authorized requestors. States must have this flexibility. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are committed to State flexibility to the extent allowable and to our Federal/State/Tribal partnership. 
                    </P>
                    <P>
                        <E T="03">25. Comment:</E>
                         Is it appropriate that Tribal agencies be authorized to have access to data under § 303.21 as discussed in the applicable preamble part? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Tribal IV-D agencies are included in § 303.21(d)(1) because they are agencies administering programs under title IV-A and IV-D of the Act. However, for clarity we have included specific reference to Tribal programs under title IV-A of the Act in § 303.21(d)(1). 
                    </P>
                    <P>
                        <E T="03">26. Comment:</E>
                         One commenter seeks confirmation that this section permits Federal or State auditors, or other agencies with oversight responsibilities, to access confidential information or IV-D case-specific information. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Authority for access to information for purposes of the administration of the plan or program approved under title IV-D of the Act includes audits conducted by Federal or State auditors, or other agencies with oversight responsibility. 
                    </P>
                    <P>
                        <E T="03">27. Comment:</E>
                         Do “under circumstances which indicate that the child's health or welfare is threatened” include a release to law enforcement agencies? Does the language of this proposed regulation allow us to release information from our child support files in response to an AMBER Alert? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Based on received comments, we have deleted the language in § 303.21(d) as stated in the NPRM that would have allowed the State IV-D program to release information to law enforcement agencies upon request. However, the information can be released to the IV-B or IV-E agency where it is necessary to carry out a State IV-B or IV-E function. 
                    </P>
                    <P>
                        <E T="03">28. Comment:</E>
                         One commenter requests that the phrase “best interest of the child” be inserted because this language is more appropriate than “under circumstances which indicate that the child's health or welfare is threatened.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         See response to Question #28 immediately above. 
                    </P>
                    <P>
                        <E T="03">29. Comment:</E>
                         One commenter seeks clarification as to whether the proposed rule would limit the use of SDNH information outside of the IV-D program, subject to the exceptions specified in § 303.21(d)(2). The commenter does not want restrictions on the use of SDNH data. This data is used to collect taxes and to detect and prevent fraud in a wide range of programs. We are unaware of any Federal authority for limiting use of this State data. In fact, section 453A(h)(3) of the Act explicitly requires States to share State new hire data with “State agencies operating employment security and worker's compensation programs.” If OCSE intends to impose these strict limitations on the use of SDNH data, further discussion of this proposal with States is warranted. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Safeguarding of SDNH data is determined by whether or not the database is part of the statewide child support enforcement automated system. Any information in the statewide system is protected and its access limited as set forth in § 307.13. If the SDNH is housed in a separate agency, these restrictions do not apply to non-IV-D use. 
                    </P>
                    <P>
                        <E T="03">30. Comment:</E>
                         One commenter believes the intent of this rule, as expressed in the preamble, does not fit with requiring independent verification of Federal Case Registry and National Directory of New Hires information. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Restricted access to Federal Case Registry (FCR) and National Directory of New Hires (NDNH) information is statutory. Independent verification is a means to enable a State to disclose this information for non-IV-D purposes by changing the source of the data through verification. 
                    </P>
                    <P>
                        <E T="03">31. Comment:</E>
                         One commenter would like an exception made under § 303.21(d)(3) for title XIX (Medicaid programs). The prohibition on disclosing unverified FCR and NDNH information contradicts the mandate in 42 U.S.C. 654A(f)(3) to share IV-D system information with Title XIX programs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 454A(f)(3) authorized limited sharing of information on the title IV-D automated system to title XIX agencies. There is a separate statute at section 453(h) and (i) that explicitly restricts access to NDNH and FCR data and does not authorize access to such data by title XIX agencies. Section 303.21(d)(3) addresses disclosure of information obtained from the IRS or Federal PLS and not State systems data. 
                    </P>
                    <P>
                        <E T="03">32. Comment:</E>
                         Two commenters are confused by the requirement to independently verify information the IV-D program receives from NDNH or FCR. How would such information be independently verified? Is this rule proposing that the State IV-D agency would have to contact the other State to verify the FCR information and NDNH information? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This rule is not requiring or advocating the IV-D agency to independently verify information received from the NDNH or the FCR. It merely describes the circumstances 
                        <PRTPAGE P="56437"/>
                        under which such data may be disclosed to persons not specified in section 453 of the Act (non-IV-D purposes). For example, assume a State IV-D agency submits an address received from the NDNH for postal verification. Once the postal verification is complete, that information has been independently verified and can be released. The source of the address is the postal service, not the NDNH. 
                    </P>
                    <P>
                        <E T="03">33. Comment:</E>
                         One commenter strongly recommends deleting the provision in § 303.21(d)(3) from the proposed regulation restricting access to NDNH, FCR, and IRS data. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Because these restrictions are statutory, they cannot be deleted. 
                    </P>
                    <P>
                        <E T="03">34. Comment:</E>
                         While one commenter recognizes that Federal law requires restriction on redisclosure of IRS data and has no objection to this aspect, the commenter is unaware of any basis in Federal statute for requiring independent verification of information from NDNH, FCR, or MSFIDM. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Federal statute is explicit regarding authorized disclosure of NDNH and FCR data. Section 453 of the Act specifies that information from the Federal PLS (of which the NDNH and FCR are a part) may only be released to authorized persons and for certain purposes. This rule is not requiring the IV-D program to independently verify information received from the NDNH or the FCR. It merely describes the circumstances under which such data may be disclosed to persons not specified in section 453 of the Act (non-IV-D purposes). 
                    </P>
                    <P>
                        <E T="03">35. Comment:</E>
                         One commenter notes that a State currently accepts information from the FCR and NDNH as “independently verified” and takes action based upon that information. This provision (requiring that the State in itself independently verify such data) will require reprogramming systems and will cause operational burden on States. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This rule is not requiring the IV-D agency to independently verify information received from the NDNH or the FCR. It merely describes the circumstances under which such data may be disclosed to persons not specified in section 453 of the Act (non-IV-D purposes). In fact, we encourage IV-D agencies to take automated action based on the NDNH or the FCR. 
                    </P>
                    <P>
                        <E T="03">36. Comment:</E>
                         One commenter asks for clarification on whether the State would be able to share locate and paternity establishment information on a State's IV-D system through an automated interface with Child Welfare, Foster Care, and Medicaid agencies. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Yes, under certain circumstances and with certain limitations. See §§ 303.21 and 307.13 
                    </P>
                    <P>
                        <E T="03">37. Comment:</E>
                         Three commenters are concerned that the independent verification requirement will impede a State's ability to share information in a timely, efficient and automated manner. In particular, the requirement will impede State's ability to assist State IV-E and Medicaid agencies in recovering public health insurance costs and locating parents. At a minimum, States will need to segregate NDNH, FCR, and MSFIDM data so that they do not transmit this information to State IV-E and Medicaid agencies pending independent verification. This will require additional automated system development, at a cost to both States and the Federal government, and will impede the functioning of automated interfaces with other State agencies. Funds and resources devoted to programming these requirements could better be used on system development that supports the core mission of the child support program. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This rule is not requiring the IV-D agency to independently verify information received from the NDNH or the FCR. It merely describes the circumstances under which such data may be disclosed to persons not specified in section 453 of the Act (for non-IV-D purposes). 
                    </P>
                    <P>
                        <E T="03">38. Comment:</E>
                         One commenter believes the regulation fails to provide guidance to IV-D agencies regarding the use of Federal tax offset amounts and asks: how can a IV-D agency “independently verify” the amount of a Federal tax refund intercept? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There is no way to independently verify Federal tax refund offset information. We continue to work with the Department of the Treasury and the Congress to resolve this issue. 
                    </P>
                    <P>
                        <E T="03">39. Comment:</E>
                         One commenter notes the regulation requires that authorized disclosures, except to IV-A agencies, cannot include information obtained from the FCR, unless independently verified. Does this mean that information about the noncustodial parent's access to military medical benefits obtained from the Defense Data Management Center (DMDC) and transmitted to the FCR is confidential? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States acquire DMDC through a FCR transaction but the data is not part of the FCR database. Information about the noncustodial parent's access to military medical benefits is thus not subject to the “independent verification” requirement. 
                    </P>
                    <P>
                        <E T="03">40. Comment:</E>
                         One commenter would like confirmation that § 303.21(d)(3) means that information may not be shared with a custodial parent seeking information about medical support benefits available to a child but that it may be released to the IV-A agency. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There is no restriction on sharing information from the Federal PLS about medical support benefits with custodial parents in IV-D cases. Such information is not received from the NDNH or the FCR. 
                    </P>
                    <P>
                        <E T="03">41. Comment:</E>
                         Four commenters note that the requirement for independent verification of NDNH and FCR information prior to disclosure could have the following consequences: delay in sending out income withholding notices (will not meet 2-day Federal timeframe); delay to families and children in getting payments; burden on employers who may be required to furnish additional employment verification to the SDNH; require automated system programming changes since the proposed rule would require segregation of NDNH and FCR and change to systems automatic processing of New Hire information; is an unacceptable burden on IV-D agencies (unfunded mandate); will impair an agency's ability to assist other State entities authorized to receive such information; and will complicate the process because depending on purposes for which information is to be used, sometimes it must be verified and sometimes not. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This rule is not requiring the IV-D agency to independently verify information received from the NDNH or the FCR before it is used in the administration of the IV-D program. It merely describes the circumstances under which such data may be disclosed to persons not specified in section 453 of the Act (for non-IV-D purposes). We encourage IV-D agencies to take automated action based on the NDNH or the FCR information. 
                    </P>
                    <P>
                        <E T="03">42. Comment:</E>
                         One commenter believes that to now require independent verification of this data seems to be contradictory to previously stated policy by the Federal OCSE (i.e., DCL-02-22 that offers the use of the NDNH, and MSFIDM as better sources than 1099 information). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Independent verification is not being required. It is merely a condition that must be met if the State wishes to use or disclose information for non-IV-D purposes to nonauthorized persons. This applies only to non-IV-D purposes. There is no such restriction in IV-D cases. 
                    </P>
                    <P>
                        <E T="03">43. Comment:</E>
                         One commenter said the State does not routinely track the “source” of most information and thinks the administrative burden involved with sharing information under the proposed 
                        <PRTPAGE P="56438"/>
                        restrictions may be too great for the program to overcome. Another commenter indicated that the State's IV-D automated system is required to identify the source of address and employment information the IV-D agency receives from automated sources. If IV-D staff independently verified NDNH information, the staff would have to change the source of confidential information and then neither State nor Federal Child Support Enforcement agencies would be able to calculate how many successful “hits” the State is receiving from NDNH or FCR. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The source of information is a recommended but not required data element in State child support systems. However, most States do identify the source of information on their systems to meet other tracking requirements such as tracking responses from each automated location source. 
                    </P>
                    <P>
                        <E T="03">44. Comment:</E>
                         One commenter requests that if the Office insists on including the restriction that prohibits disclosure of NDNH and FCR information to title IV, XIX and XXI agencies, the Office insert language to clarify “Except for SPLS disclosure authorized under § 302.35(c)(5), the IV-D program may not disclose FCR and NDNH data to IV-B and IV-E agencies.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Because of authority in section 453(c) of the Act, in § 307.13(a)(4)(iii) we have indicated that NDNH and FCR information is available to IV-B and IV-E agencies for the purposes set forth in section 453 of the Act. 
                    </P>
                    <P>
                        <E T="03">45. Comment:</E>
                         One commenter would like the Office to recognize that the mandate to disclose to Title IV-B and IV-E agencies under § 303.21(d)(2) and the prohibition on that mandated disclosure of NDNH and FCR information to IV-B and IV-E agencies without first independently verifying under (d)(3) will create confusion because under 42 U.S.C. 653(c)(4), IV-B, and IV-E agencies are authorized persons for receiving NDNH and FCR information for authorized purposes without independent verification for the limited purposes of establishing parentage and support. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 453(c) of the Act provides authority for IV-B and IV-E agencies to receive NDNH and FCR information without independent verification. 
                    </P>
                    <P>
                        <E T="03">46. Comment:</E>
                         One commenter notes that § 303.21(e) makes it clear that a legislative body or governmental committee cannot obtain the release of information pertaining to an individual without consent of the individual. Please verify that it is up to the State to determine the nature of the consent of the individual (e.g., written, verbal, or notarized permission or a State could deny permission entirely?). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         To the extent that an individual in a IV-D case submits a request to a legislator or legislative body concerning his or her IV-D case, the IV-D agency may disclose the information necessary for the response because the inquiry relates to the administration of the IV-D program and is authorized under paragraph (c). As mentioned earlier in the preamble, we deleted the language under paragraph (e) Safeguards, that “safeguards shall also prohibit disclosure to any committee or legislative body (Federal, State, or local) of any confidential information, unless authorized by the individual as specified in paragraph (d) of this section.” 
                    </P>
                    <P>
                        <E T="03">47. Comment:</E>
                         One commenter, to emphasize the requirement that States establish the safeguards for victims of family violence required by the statute and by the automated system regulation, requested the following sentence be added to the end of § 303.21(e): “These safeguards shall also include prohibitions against the release of information when the State has reasonable evidence of domestic violence or child abuse against a party or a child and that the disclosure of such information could be harmful to the party or the child, as required by section 454(26) of the Act, and shall include use of the family violence indicator required under § 307.11(f)(1)(x) of this chapter.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter and have revised § 303.21(e) accordingly. 
                    </P>
                    <P>
                        <E T="03">48. Comment:</E>
                         One commenter recommends adding a qualification to § 303.21(e) that the information may be released where members of the legislature want information with respect to a IV-D case because of a constituent request on a particular case. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Addition of a qualification is not necessary. Under § 303.21(c) such disclosure is allowable because it is for IV-D purposes. 
                    </P>
                    <HD SOURCE="HD2">Appendix A to § 303.21, Safeguarding Confidential Information </HD>
                    <P>
                        <E T="03">1. Comment:</E>
                         One commenter is concerned that Appendix A does not recognize that among the duties of the IV-D program is the duty to avoid fraud in publicly-funded programs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States are responsible for avoiding fraud in any publicly-funded program. However we have no authority to allow access to specific data when prohibited or limited by Federal statute. 
                    </P>
                    <P>
                        <E T="03">2. Comment:</E>
                         One commenter notes that the preamble to the proposed rule and the proposed language of § 303.21 impose an independent verification requirement for NDNH but not for SDNH data. Yet the chart in Appendix A following proposed § 303.21 applies this independent verification requirement to disclosure of SDNH data. This appears to be an error. If not, this requirement would be a major limitation on State use of State new hire data that has no basis in Federal law. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The chart indicates that independent verification is needed if the source of information is NDNH, FCR, or IRS, except that NDNH or FCR information may be shared with the IV-A, IV-B, and IV-E programs without verification. As mentioned earlier, we have redesigned Appendix A and added a new Appendix B and C. There is no requirement to independently verify SDNH information. 
                    </P>
                    <HD SOURCE="HD2">Section 303.70, Procedures for Submissions to the State Parent Locator Service (State PLS) or the Federal Parent Locator Service (FPLS) </HD>
                    <P>
                        <E T="03">1. Comment:</E>
                         One commenter recommends that the Office specify that the word “individuals” as used in paragraph (a) includes parents, putative fathers, children and caretaker relatives. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 453 of the Act governs whom the Federal PLS may attempt to locate and by cross-reference in section 454(8) of the Act, whom the State PLS may attempt to locate. Section 453(a)(2)(A) refers to attempting to locate any individual “(i) who is under an obligation to pay child support; (ii) against whom such an obligation is sought; (iii) to whom such an obligation is owed, or (iv) who has or may have parental rights with respect to a child.” Caretaker relatives do not fit any of those conditions. However, we have substituted “parents, putative fathers, and children” for “individuals” in § 303.20(a). 
                    </P>
                    <P>
                        <E T="03">2. Comment:</E>
                         One commenter would like the following “purpose” to be added: The State PLS shall locate individuals for the purpose of facilitating informed and timely decisions about child welfare and permanency, since locating parents for IV-B/IV-E purposes goes beyond just “establishing parentage” or “determining who has or may have parental rights to a child” as the language in the proposed rule currently reads. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The language in § 303.70(e)(1)(i) is the authorized purpose as stated in section 453(a)(2) of the Act for the release of information to IV-B and IV-E State agencies and is 
                        <PRTPAGE P="56439"/>
                        consistent with timely decisions regarding child welfare. 
                    </P>
                    <P>
                        <E T="03">3. Comment:</E>
                         One commenter would like the word “aid” changed to “assistance as defined at 45 CFR 260.31” in the proposed rule. This way, there will be a clear national policy in this area. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have changed the word “aid” to “assistance” as suggested by the commenter but did not cite the regulation because it may change. 
                    </P>
                    <HD SOURCE="HD2">Section 307.13, Security and Confidentiality for Computerized Support Enforcement Systems in Operation After October 1, 1997 </HD>
                    <P>
                        <E T="03">1. Comment:</E>
                         Will more guidance be given to IV-D agencies regarding the type of information that will be needed by the State and Tribal agencies administrating programs under titles IV, XIX, and XXI of the Act? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We encourage IV-D agencies to work with other agencies to make such determinations. 
                    </P>
                    <P>
                        <E T="03">2. Comment:</E>
                         Could IV-A, XIX, and XXI workers have login IDs and passwords to the IV-D system if their access to the IV-D system were sufficiently limited to view only the information that those workers had the right to access? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         It is possible but would require additional programming to ensure that the non-IV-D worker has access to only the authorized data including, as applicable, independently-verified data. Non-IV-D workers cannot have direct access to the IV-D screens, because usually the data on a typical IV-D system screen may contain IRS and financial institution information 
                    </P>
                    <P>
                        <E T="03">3. Comment:</E>
                         One commenter asks for clarification of the phrase “outside the IV-D program” in § 307.13(a)(5). Does this phrase mean that the State IV-D agency may not disclose NDNH or FCR information without independent verification even if it is a disclosure that is necessary to establish, modify or enforce child support? Would this phrase prohibit the IV-D agency from using MSFIDM information as evidence in a contempt of court proceeding to show the delinquent obligor had assets but still failed to pay child support as ordered unless the IV-D agency first obtained independent verification? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Establishing, modifying or enforcing a child support order, or a court proceeding where proof is brought regarding the fact that a delinquent obligor had assets but still failed to pay child support, are all IV-D purposes for a IV-D case. Because they are IV-D purposes, the IV-D agency may disclose NDNH or FCR information and independent verification does not apply. 
                    </P>
                    <P>
                        <E T="03">4. Comment:</E>
                         One commenter seeks clarification that § 307.13(a)(5) [now § 307.13(a)(4)] does not require independent verification of FCR and NDNH information. If so, the commenter recommends deleting this provision as it is administratively burdensome. One commenter would like the Office to eliminate the restriction that requires independent verification of NDNH and FCR information to title IV, XIX and XXI agencies. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Independent verification of NDNH and FCR information is only necessary for disclosure for non-IV-D purposes. The regulation has been rewritten for clarity and § 307.13(a)(4) requires written policies that limit disclosure outside the IV-D program, of National Directory of New Hire information, Federal Case Registry information, and IRS information that is restricted as specified in the Internal Revenue Code. Financial institution information cannot be shared outside the IV-D program. IV-A, IV-B, and IV-E agencies are authorized under various subsections of section 453 of the Act to receive NDNH and FCR information from the Federal PLS for certain specified purposes. Since these agencies are authorized to have this information, we are permitting the IV-D agency to disclose the NDNH or FCR information from the IV-D computerized support enforcement system directly to the IV-A, IV-B, or IV-E agency if it is being requested for the purpose authorized under section 453 of the Act. For IV-B and IV-E programs this includes establishing paternity or parental rights with respect to a child. 
                    </P>
                    <P>
                        <E T="03">5. Comment:</E>
                         One commenter seeks clarification as to who is responsible to conduct any verification. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The State IV-D agency must independently verify the data. 
                    </P>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s55,r50,r50,r50,r50,r50">
                        <TTITLE>Appendix A: Locating Individuals Through the State PLSs § 302.35 </TTITLE>
                        <BOXHD>
                            <CHED H="1">Authorized person/program </CHED>
                            <CHED H="1">Authorized purpose of the request </CHED>
                            <CHED H="1">Persons about whom information may be asked </CHED>
                            <CHED H="1">Sources searched </CHED>
                            <CHED H="1">
                                Authorized 
                                <LI>information </LI>
                                <LI>returned </LI>
                            </CHED>
                            <CHED H="1">
                                Limitations 
                                <SU>1</SU>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Agent/attorney of a State who has the duty or authority to collect child and spousal support under the IV-D plan. Section 453(c)(1) </ENT>
                            <ENT>Establish paternity. Establish, set the amount, modify, or enforce child support obligations and or to facilitate the location of any individual who is under an obligation to pay child support, against whom such an obligation is sought, or to whom such an obligation is owed </ENT>
                            <ENT>
                                Noncustodial Parent 
                                <LI>Putative Father </LI>
                                <LI>Custodial Parent </LI>
                                <LI>Children. Section 453(a)(2)(A) </LI>
                            </ENT>
                            <ENT>
                                Federal Parent Locator Service 
                                <LI>In-state sources in accordance with State law </LI>
                            </ENT>
                            <ENT O="xl">
                                Six Elements: 
                                <LI>Person's Name </LI>
                                <LI>Person's SSN </LI>
                                <LI>Person's address </LI>
                                <LI>Employer's name </LI>
                                <LI>Employer's address </LI>
                                <LI>Employer Identification Number. Section 453(a)(2)(A)(iii) </LI>
                                <LI>Wages, income, and benefits of employment, including health care coverage. Section 453(a)(2)(B) </LI>
                            </ENT>
                            <ENT>See footnote.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Locate a parent or child involved in a non-IV-D child support case to disburse an income withholding collection. Section 453(a)(2) </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Type, status, location, and amount of assets or debts owed by or to the individual. Section 453(a)(2)(C) </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="56440"/>
                            <ENT I="01">Court that has the authority to issue an order against an NCP for the support and maintenance of child, or to serve as the initiating court in an action to seek a child support order. Section 453(c)(2) </ENT>
                            <ENT>To facilitate the location of any individual who is under an obligation to pay child support, against whom such an obligation is sought, or to whom such an obligation is owed </ENT>
                            <ENT>
                                Noncustodial Parent 
                                <LI>Custodial Parent </LI>
                                <LI>Putative Father </LI>
                                <LI>Child </LI>
                            </ENT>
                            <ENT>
                                Federal Parent Locator Service 
                                <LI>In-state sources in accordance with State law </LI>
                            </ENT>
                            <ENT>
                                Six Elements as above 
                                <LI>Wages, income, and benefits of employment, including health care coverage. Section 453(a)(2)(B) </LI>
                                <LI>Type, status, location, and amount of assets or debts owed by or to the individual. Section 453(a)(2)(C) </LI>
                            </ENT>
                            <ENT>
                                No Internal Revenue Service (IRS) information provided for non-IV-D cases unless independently verified. 
                                <LI>No Multistate Financial Institution Data Match (MSFIDM) and no State Financial Institution Data Match (FIDM) information provided for non-IV-D cases. </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Locate a parent or child involved in a non-IV-D child support case. </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>No required subsequent attempts to locate unless there is a new request. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01" O="xl">
                                Resident parent, legal guardian, attorney, or agent of a child not receiving IV-A benefits (a non-IV-D request). Section 453(c)(3).
                                <SU>2</SU>
                            </ENT>
                            <ENT>To facilitate the location of any individual who is under an obligation to pay child support, against whom such an obligation is sought, or to whom such an obligation is owed </ENT>
                            <ENT>
                                Noncustodial Parent 
                                <LI>Putative Father </LI>
                            </ENT>
                            <ENT>
                                Federal Parent Locator Service 
                                <LI>In-state sources in accordance with State law </LI>
                            </ENT>
                            <ENT>
                                Six Elements as above 
                                <LI>Wages, income, and benefits of employment, including health care coverage. Section 453(a)(2)(B) </LI>
                                <LI>Type, status, location, and amount of assets or debts owed by or to the individual. Section 453(a)(2)(C) </LI>
                            </ENT>
                            <ENT>
                                Child not receiving IV-A benefits. 
                                <LI>No IRS Information. </LI>
                                <LI>No MSFIDM and no State FIDM information provided for non-IV-D cases. </LI>
                                <LI>In a non-IV-D request, attestation is required as specified in § 302.35(c)(3)(i)-(iii). </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Locate a parent or child involved in a non-IV-D child support case </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>No required subsequent attempts to locate unless there is a new request. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">State agency that is administering a Child and Family Services program (IV-B) or a Foster Care and Adoption IV-E program. Section 453(c)(4) </ENT>
                            <ENT>To facilitate the location of any individual who has or may have parental rights with respect to the child. Section 453(a)(2)(iv) </ENT>
                            <ENT>
                                Noncustodial Parent 
                                <LI>Putative Father </LI>
                                <LI>Custodial Parent </LI>
                                <LI>Child. Section 453(a)(2)(A) </LI>
                            </ENT>
                            <ENT>
                                Federal Parent Locator Service 
                                <LI>In-state sources in accordance with State law </LI>
                            </ENT>
                            <ENT>
                                Six Elements as above 
                                <LI>Wages, income, and benefits of employment, including health care coverage </LI>
                            </ENT>
                            <ENT>
                                No IRS information unless independently verified. 
                                <LI>No MSFIDM information and no State FIDM information provided. </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Type, status, location, and amount of assets or debts owed by or to the individual. Section 453(a)(2)(C) </ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             No information shall be disclosed if the disclosure of such information would contravene the national policy or security interests of the United States or the confidentiality of census data. No information shall be disclosed if the State has reasonable evidence of domestic violence or child abuse and the disclosure of such information could be harmful to the CP or child. See Section 453(b)(2) for release process to court or agent of the court.
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             A Tribal IV-D program may request access to the Federal PLS under this authority. See PIQ-07-02/TPIQ-07-02, Q&amp;R 7.
                        </TNOTE>
                    </GPOTABLE>
                    <PRTPAGE P="56441"/>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,r50,r50,r50,r50,r50,r50">
                        <TTITLE>Appendix B: Locating an Individual Sought in a Child Custody/Visitation or Parental Kidnapping Case</TTITLE>
                        <BOXHD>
                            <CHED H="1">Type of request </CHED>
                            <CHED H="1">Authorized person/program </CHED>
                            <CHED H="1">Authorized purpose of the request </CHED>
                            <CHED H="1">
                                About whom information may be 
                                <LI>requested </LI>
                            </CHED>
                            <CHED H="1">Sources searched </CHED>
                            <CHED H="1">Authorized information returned </CHED>
                            <CHED H="1">
                                Limitations 
                                <SU>1</SU>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">LOCATING AN INDIVIDUAL SOUGHT IN A CHILD CUSTODY OR VISITATION CASE </ENT>
                            <ENT>Any agent or attorney of any State who has the authority/duty to enforce a child custody or visitation determination. § 463(d(2)(A) </ENT>
                            <ENT>Determining the whereabouts of a parent or child to make or enforce a custody or visitation determination. § 463(a)(2) </ENT>
                            <ENT>A parent or child.  § 463(a) </ENT>
                            <ENT>
                                Federal Parent Locator Service 
                                <LI>In-state sources in accordance with State law </LI>
                            </ENT>
                            <ENT>Only the three following elements: Person's address Employer's name Employer's address § 463(c) </ENT>
                            <ENT>
                                See footnote. 
                                <LI>No IRS information provided. </LI>
                                <LI>No MSFIDM or State FIDM information provided. </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>A court, or agent of the court, having jurisdiction to make or enforce a child custody or visitation determination. § 463(d)(2)(B) </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>No subsequent attempts to locate unless there is a new request. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">LOCATING AN INDIVIDUAL SOUGHT IN A PARENTAL KIDNAPPING CASE </ENT>
                            <ENT>Agent or attorney of the U.S. or a State who has authority/duty to investigate, enforce, or prosecute the unlawful taking or restraint of a child.  § 463(d)(2)(C) </ENT>
                            <ENT>Determining the whereabouts of a parent or child to enforce any State or Federal law with respect to the unlawful taking or restraint of a child.  § 463(a)(1) </ENT>
                            <ENT>A parent or child.  § 463(a) </ENT>
                            <ENT>
                                Federal Parent Locator Service 
                                <LI>In-state sources in accordance with State law </LI>
                            </ENT>
                            <ENT>Only the three following elements: Person's address  Employer's name Employer's address  § 463(c) </ENT>
                            <ENT>
                                See footnote. 
                                <LI>No IRS information provided </LI>
                                <LI>No MSFIDM or State FIDM information provided. </LI>
                                <LI>No subsequent attempts to locate unless there is a new request. </LI>
                            </ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             No information shall be disclosed if the disclosure of such information would contravene the national policy or security interests of the United States or the confidentiality of census data. No information shall be disclosed if the State has reasonable evidence of domestic violence or child abuse and the disclosure of such information could be harmful to the CP or child. See Section 453(b)(2) for release process to court or agent of the court.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r50,r50,r50,r50">
                        <TTITLE>Appendix C: Authority for State IV-D Agencies to Release Information to Non-IV-D Federal, State, and Tribal Programs</TTITLE>
                        <BOXHD>
                            <CHED H="1">Authority</CHED>
                            <CHED H="1">
                                Authorized purpose of 
                                <LI>request</LI>
                            </CHED>
                            <CHED H="1">Authorized person/program</CHED>
                            <CHED H="1">
                                Authorized information 
                                <LI>returned </LI>
                            </CHED>
                            <CHED H="1">Limitations </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Sections 453 and 454A(f)(3) of the Act, Section 1102 of the Act; and 45 CFR 307.13</ENT>
                            <ENT>To perform State or Tribal agency responsibilities of designated programs </ENT>
                            <ENT>State or Tribal agencies administering title IV, XIX, and XXI programs </ENT>
                            <ENT>Confidential information found in automated system </ENT>
                            <ENT>
                                No Internal Revenue Service information unless independently verified.
                                <LI>No MSFIDM or State FIDM information provided. </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>No NDNH and FCR information for title XIX and XXI unless independently verified. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>For IV-B/IV-E, for purpose of section 453(a)(2) of the Act can have NDNH and FCR information without independent verification. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>—Any other purpose requires independent verification. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>For IV-A NDNH/FRC information for purposes of section 453(j) of the Act without independent verification. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>—Need verification for other purposes. </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="56442"/>
                            <ENT I="01">Sections 453A(h)(2) and 1137 of the Act—State Directory of New Hires </ENT>
                            <ENT>Income and eligibility verification purposes of designated programs </ENT>
                            <ENT>State agencies administering title IV-A, Medicaid, unemployment compensation, food stamps, or other State programs under a plan approved under title I, X, XIV, or XVI of the Act </ENT>
                            <ENT>SDNH information: Individual's name, address and SSN; employer's name, address, and Federal employer identification number </ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD1">IV. Regulatory Review </HD>
                    <HD SOURCE="HD2">A. Paperwork Reduction Act </HD>
                    <P>Section 302.35(c) contains an information collection requirement. As required by the Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)), the Administration for Children and Families submitted a copy of this section to the Office of Management and Budget (OMB) for its review. We received only one comment regarding the attestation; therefore in the final rule have not revised any language in § 307.13 relating to attestation. </P>
                    <P>
                        <E T="03">1. Comment:</E>
                         One commenter noted that the Paper Reduction Act estimate of 702 hours grossly underestimates the time needed to complete the requirements of these proposed regulations. Requiring State IV-D agencies to independently verify NDNH and FCR hits requires a tremendous amount of paperwork, time, and effort. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulation does not require independent verification. It sets forth the conditions for the release of information that the State would not be able to release for non-IV-D purposes otherwise. If the information has not been independently verified, it may not be released for non-IV-D purposes or to persons not specified in section 453 of the Act. 
                    </P>
                    <HD SOURCE="HD2">B. Regulatory Flexibility Analysis </HD>
                    <P>The Secretary certifies that, under 5 U.S.C. 605(b), as enacted by the Regulatory Flexibility Act (Pub. L. 96-354), this rule will not result in a significant impact on a substantial number of small entities. The primary impact is on State governments. State governments are not considered small entities under the Act. </P>
                    <HD SOURCE="HD2">C. Executive Order 12866 </HD>
                    <P>Executive Order 12866 requires that regulations be reviewed to ensure that they are consistent with the priorities and principles set forth in the Executive Order. The Department has determined that this rule is consistent with these priorities and principles. This regulation responds to State requests for guidance on data privacy issues. </P>
                    <P>The primary purpose of this regulation is to clarify requirements for safeguarding child support enforcement information by consolidating various statutory requirements on disclosure and safeguarding of information into a regulatory framework. There are no appreciable costs related to this regulation as the relevant statutory requirements have been in place for many years and the regulation substantially reflects current operating practices. </P>
                    <HD SOURCE="HD2">D. Unfunded Mandates Reform Act of 1995 </HD>
                    <P>Section 202 of the Unfunded Mandates Reform Act of 1995 requires that a covered agency prepare a budgetary impact statement before promulgating a rule that includes any Federal mandate that may result in the expenditure by State, local, and Tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year. </P>
                    <P>If a covered agency must prepare a budgetary impact statement, section 205 further requires that it select the most cost-effective and least burdensome alternative that achieves the objectives of the rule and is consistent with the statutory requirements. In addition, section 203 requires a plan for informing and advising any small governments that may be significantly or uniquely impacted by the rule. </P>
                    <P>We have determined that this rule will not result in the expenditure by State, local, and Tribal governments, in the aggregate, or by the private sector, of more than $100 million in any one year. Accordingly, we have not prepared a budgetary impact statement, specifically addressed the regulatory alternatives considered, or prepared a plan for informing and advising any significantly or uniquely impacted small governments. </P>
                    <HD SOURCE="HD2">E. Congressional Review </HD>
                    <P>This rule is not a major rule as defined in 5 U.S.C. chapter 8. </P>
                    <HD SOURCE="HD2">F. Assessment of Federal Regulations and Policies on Families </HD>
                    <P>Section 654 of the Treasury and General Government Appropriations Act of 1999 requires Federal agencies to determine whether a policy or regulation may affect family well-being. If the agency's determination is affirmative, then the agency must prepare an impact assessment addressing seven criteria specified in the law. This Office has reviewed and determined that these regulations protect the confidentiality of information contained in the records of State child support enforcement agencies and will not have an impact on family well being as defined in the legislation. </P>
                    <HD SOURCE="HD2">G. Executive Order 13132 </HD>
                    <P>Executive Order 13132 prohibits an agency from publishing any rule that has federalism implications if the rule either imposes substantial direct compliance costs on State and local governments and is not required by statute, or the rule preempts State law, unless the agency meets the consultation and funding requirements of section 6 of the Executive Order. This rule does not have federalism implication as defined in the Executive order. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects </HD>
                        <CFR>45 CFR Part 302 </CFR>
                        <P>Child support, Grants programs/social programs, Reporting and recordkeeping requirements. </P>
                        <CFR>45 CFR part 303 </CFR>
                        <P>Child support, Grant programs/social programs, Reporting and recordkeeping requirements. </P>
                        <CFR>45 CFR Part 307 </CFR>
                        <P>
                            Child support, Grant programs/social programs, computer technology, 
                            <PRTPAGE P="56443"/>
                            Reporting and recordkeeping requirements.
                        </P>
                    </LSTSUB>
                    <EXTRACT>
                        <FP>(Catalog of Federal Domestic Assistance Programs No. 93.563, Child Support Enforcement Program.)</FP>
                    </EXTRACT>
                    <SIG>
                        <DATED>Dated: April 23, 2008. </DATED>
                        <NAME>Daniel C. Schneider, </NAME>
                        <TITLE>Acting Assistant Secretary for Children and Families.</TITLE>
                        <DATED>Approved: June 23, 2008. </DATED>
                        <NAME>Michael O. Leavitt,</NAME>
                        <TITLE>Secretary of Health and Human Services.</TITLE>
                    </SIG>
                    <REGTEXT TITLE="45" PART="302">
                        <AMDPAR>Accordingly, the Department of Health and Human Services amends title 45 chapter III of the Code of Federal Regulations as follows: </AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 302—STATE PLAN REQUIREMENTS </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 302 is revised to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>42 U.S.C. 651 through 658, 660, 663, 664, 666, 667, 1302, 1396a(a)(25), 1396b(d)(2), 1396b(o), 1396b(p), 1396(k).</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="302">
                        <AMDPAR>2. Section 302.35 is revised to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 302.35 </SECTNO>
                            <SUBJECT>State parent locator service. </SUBJECT>
                            <P>The State plan shall provide as follows: </P>
                            <P>
                                (a) 
                                <E T="03">State PLS.</E>
                                 The IV-D agency shall maintain a State PLS to provide locate information to authorized persons for authorized purposes. 
                            </P>
                            <P>
                                (1) 
                                <E T="03">For IV-D cases and IV-D purposes by the IV-D agency.</E>
                                 The State PLS shall access the Federal PLS and all relevant sources of information and records available in the State, and in other States as appropriate, for locating custodial parents, noncustodial parents, and children for IV-D purposes. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">For authorized non-IV-D individuals and purposes—</E>
                            </P>
                            <P>(i) The State PLS shall access and release information authorized to be disclosed under Section 453(a)(2) of the Act from the Federal PLS and, in accordance with State law, information from relevant in-state sources of information and records, as appropriate, for locating custodial parents, noncustodial parents, and children upon request of authorized individuals specified in paragraph (c) of this section, for authorized purposes specified in paragraph (d) of this section. </P>
                            <P>(ii) The State PLS shall not release information from the computerized support enforcement system required under part 307 of this chapter, IRS information, or financial institution data match information, nor shall the State PLS forward a non-IV-D request to another State IV-D agency. </P>
                            <P>(iii) The State PLS need not make subsequent location attempts if locate efforts fail to find the individual sought unless a new request is submitted. </P>
                            <P>
                                (b) 
                                <E T="03">Central State PLS requirement.</E>
                                 The IV-D program shall maintain a central State PLS to submit requests to the Federal PLS. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Authorized persons.</E>
                                 The State PLS shall accept requests for locate information only from the following authorized persons: 
                            </P>
                            <P>(1) Any State or local agency or official providing child and spousal support services under the State plan; </P>
                            <P>(2) A court that has authority to issue an order or to serve as the initiating court in an action to seek an order against a noncustodial parent for the support and maintenance of a child, or any agent of such court; </P>
                            <P>(3) The resident parent, legal guardian, attorney, or agent of a child who is not receiving assistance under title IV-A of the Act only if the individual: </P>
                            <P>(i) Attests that the request is being made to obtain information on, or to facilitate the discovery of, any individual in accordance with section 453(a)(2) of the Act for the purpose of establishing parentage, establishing, setting the amount of, modifying, or enforcing child support obligations; </P>
                            <P>(ii) Attests that any information obtained through the Federal or State PLS shall be used solely for these purposes and shall be otherwise treated as confidential; </P>
                            <P>(iii) Provides evidence that the requestor is the parent, legal guardian, attorney, or agent of a child not receiving assistance under title IV-A, and if an agent of such a child, evidence of a valid contract that meets any requirements in State law or written policy for acting as an agent and, if a parent, attestation that he or she is the resident parent. </P>
                            <P>(iv) Pays the fee required for Federal PLS services under section 453(e)(2) of the Act and § 303.70(f)(2)(i) of this chapter, if the State does not pay the fee itself. The State may also charge a fee to cover its costs of processing the request, which must be as close to actual costs as possible, so as not to discourage requests to use the Federal PLS. If the State itself pays the fee for use of the Federal PLS or the State PLS in a non-IV-D case, Federal financial participation is not available in those expenditures. </P>
                            <P>(4) Authorized persons as defined in § 303.15 of this chapter in connection with parental kidnapping, child custody or visitation cases; or </P>
                            <P>(5) A State agency that is administering a program operated under a State plan under titles IV-B or IV-E of the Act. </P>
                            <P>
                                (d) 
                                <E T="03">Authorized purposes for requests and scope of information provided.</E>
                                 The State PLS shall obtain location information under this section only for the purposes specified in paragraphs (d)(1) and (d)(2) of this section. 
                            </P>
                            <P>
                                (1) 
                                <E T="03">To locate an individual with respect to a child in a IV-D, non-IV-D, IV-B, or IV-E case.</E>
                                 The State PLS shall locate individuals for the purpose of establishing parentage, or establishing, setting the amount of, modifying, or enforcing child support obligations or for determining who has or may have parental rights with respect to a child. For these purposes, only information available through the Federal PLS or the State PLS may be provided. This information is limited to Social Security Number(s), most recent address, employer name and address, employer identification number, wages or other income from, and benefits of, employment, including rights to, or enrollment in, health care coverage, and asset or debt information. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">To locate an individual sought for the unlawful taking or restraint of a child or for child custody or visitation purposes.</E>
                                 The State PLS shall locate individuals for the purpose of enforcing a State law with respect to the unlawful taking or restraint of a child or for making or enforcing a child custody or visitation determination as defined in section 463(d)(1) of the Act. For this purpose, only the information available through the Federal PLS or the State PLS may be provided. This information is limited to most recent address and place of employment of a parent or child. 
                            </P>
                            <P>
                                (e) 
                                <E T="03">Locate information subject to disclosure.</E>
                                 Subject to the requirements of this section and the privacy safeguards required under section 454(26) of the Act and the family violence indicators under section 307.11(f)(1)(x) of this part, the State PLS shall disclose the following information to authorized persons for authorized purposes, 
                            </P>
                            <P>(1) Federal PLS information described in sections 453 and 463 of the Act; and </P>
                            <P>(2) Information from in-state locate sources.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="303">
                        <PART>
                            <HD SOURCE="HED">PART 303—STANDARDS FOR PROGRAM OPERATIONS </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 303 is revised to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>42 U.S.C. 651 through 658, 660, 663, 664, 666, 667, 1302, 1396a(a)(25), 1396b(d)(2), 1396b(o), 1396b(p) and 1396(k).</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="303">
                        <AMDPAR>2. Revise § 303.3 to read as follows: </AMDPAR>
                        <SECTION>
                            <PRTPAGE P="56444"/>
                            <SECTNO>§ 303.3 </SECTNO>
                            <SUBJECT>Location of noncustodial parents in IV-D cases. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Definition.</E>
                                 For purposes of this section, 
                                <E T="03">location</E>
                                 means obtaining information concerning the physical whereabouts of the noncustodial parent, or the noncustodial parent's employer(s), other sources of income or assets, as appropriate, which is sufficient and necessary to take the next appropriate action in a IV-D case. 
                            </P>
                            <P>(b) For all cases referred to the IV-D program for IV-D services because of an assignment of support rights or cases opened upon application for IV-D services under § 302.33 of this chapter, the IV-D program must attempt to locate all noncustodial parents or their sources of income and/or assets when location is needed to take a necessary action. Under this standard, the IV-D program must: </P>
                            <P>(1) Use appropriate location sources such as the Federal PLS; interstate location networks; local officials and employees administering public assistance, general assistance, medical assistance, food stamps, and social services (whether such individuals are employed by the State or a political subdivision); relatives and friends of the noncustodial parent, current or past employers; the local telephone company; the U.S. Postal Service; financial references; unions; fraternal organizations; and police, parole, and probation records, if appropriate; and State agencies and departments, as authorized by State law, including those departments which maintain records of public assistance, wages and employment, unemployment insurance, income taxation, driver's licenses, vehicle registration, and criminal records and other sources; </P>
                            <P>(2) Establish working relationships with all appropriate agencies in order to use locate resources effectively; </P>
                            <P>(3) Within no more than 75 calendar days of determining that location is necessary, access all appropriate location sources and ensure that location information is sufficient to take the next appropriate action in a case; </P>
                            <P>(4) Refer appropriate IV-D cases to the IV-D program of any other State, in accordance with the requirements of § 303.7 of this part. The IV-D program of such other State shall follow the procedures in paragraphs (b)(1) through (b)(3) of this section for such cases, as necessary, except that the responding State is not required to access the Federal PLS; </P>
                            <P>(5) Repeat location attempts in cases in which previous attempts to locate noncustodial parents or sources of income and/or assets have failed, but adequate identifying and other information exists to meet requirements for submittal for location, either quarterly or immediately upon receipt of new information which may aid in location, whichever occurs sooner. Quarterly attempts may be limited to automated sources, but must include accessing State employment security files. Repeated attempts because of new information which may aid in location must meet the requirements of paragraph (b)(3) of this section; and </P>
                            <P>(6) Have in effect safeguards, applicable to all confidential information handled by the IV-D program, that are designed to protect the privacy rights of the parties and that comply with the requirements of sections 454(26) and 454A(d) and (f) of the Act and §§ 303.21 and 307.13. </P>
                            <P>(c) The State must establish guidelines defining diligent efforts to serve process. These guidelines must include periodically repeating service of process attempts in cases in which previous attempts to serve process have failed, but adequate identifying and other information exists to attempt service of process. </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="303">
                        <AMDPAR>4. Section 303.20 is amended by revising paragraph (b)(7) as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 303.20 </SECTNO>
                            <SUBJECT>Minimum organizational and staffing requirements. </SUBJECT>
                            <P>(b) * * *</P>
                            <P>(7) Operation of the State PLS as required under §§ 302.35, 303.3, and 303.70 of this chapter. </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="303">
                        <AMDPAR>5. Section 303.21 is added to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 303.21 </SECTNO>
                            <SUBJECT>Safeguarding and disclosure of confidential information. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Definitions</E>
                                —(1) 
                                <E T="03">Confidential information</E>
                                 means any information relating to a specified individual or an individual who can be identified by reference to one or more factors specific to him or her, including but not limited to the individual's Social Security number, residential and mailing addresses, employment information, and financial information. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Independent verification</E>
                                 is the process of acquiring and confirming confidential information through the use of a second source. The information from the second source, which verifies the information about NDNH or FCR data, may be released to those authorized to inspect and use the information as authorized under the regulations or the Act. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Scope</E>
                                . The requirements of this section apply to the IV-D agency, any other State or local agency or official to whom the IV-D agency delegates any of the functions of the IV-D program, any official with whom a cooperative agreement as described in § 302.34 of this part has been entered into, and any person or private agency from whom the IV-D agency has purchased services pursuant to § 304.22 of this chapter. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">General rule</E>
                                . Except as authorized by the Act and implementing regulations, an entity described in paragraph (b) of this section may not disclose any confidential information, obtained in connection with the performance of IV-D functions, outside the administration of the IV-D program. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Authorized disclosures</E>
                                . (1) Upon request, the IV-D agency may, to the extent that it does not interfere with the IV-D agency meeting its own obligations and subject to such requirements as the Office may prescribe, disclose confidential information to State agencies as necessary to carry out State agency functions under plans or programs under title IV (including tribal programs under title IV) and titles XIX, or XXI of the Act, including: 
                            </P>
                            <P>(i) Any investigation, prosecution or criminal or civil proceeding conducted in connection with the administration of any such plan or program; and </P>
                            <P>(ii) Information on known or suspected instances of physical or mental injury, sexual abuse or exploitation, or negligent treatment or maltreatment of a child under circumstances which indicate that the child's health or welfare is threatened. </P>
                            <P>(2) Upon request, the IV-D agency may disclose information in the SDNH, pursuant to sections 453A and 1137 of the Act for purposes of income and eligibility verification. </P>
                            <P>(3) Authorized disclosures under paragraph (d)(1) and (2) of this section shall not include confidential information from the National Directory of New Hires or the Federal Case Registry, unless authorized under § 307.13 of this Chapter or unless it is independently verified information. No financial institution data match information may be disclosed outside the administration of the IV-D program and no IRS information may be disclosed, unless independently verified or otherwise authorized in Federal statute. States must have safeguards in place as specified in section 454A(d) and (f) of the Act. </P>
                            <P>
                                (e) 
                                <E T="03">Safeguards</E>
                                . In addition to, and not in lieu of, the safeguards described in § 307.13 of this chapter, which governs computerized support enforcement systems, the IV-D agency shall establish appropriate safeguards to comply with the provisions of this section. These safeguards shall also include prohibitions against the release of 
                                <PRTPAGE P="56445"/>
                                information when the State has reasonable evidence of domestic violence or child abuse against a party or a child and that the disclosure of such information could be harmful to the party or the child, as required by section 454(26) of the Act, and shall include use of the family violence indicator required under § 307.11(f)(1)(x) of this chapter. 
                            </P>
                            <P>
                                (f) 
                                <E T="03">Penalties for unauthorized disclosure</E>
                                . Any disclosure or use of confidential information in violation of the Act and implementing regulations shall be subject to any State and Federal statutes that impose legal sanctions for such disclosure. 
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="303">
                        <P>6. Revise § 303.70 to read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 303.70 </SECTNO>
                            <SUBJECT>Procedures for submissions to the State Parent Locator Service (State PLS) or the Federal Parent Locator Service (Federal PLS). </SUBJECT>
                            <P>(a) The State agency will have procedures for submissions to the State PLS or the Federal PLS for the purpose of locating parents, putative fathers, or children for the purpose of establishing parentage or establishing, setting the amount of, modifying, or enforcing child support obligations; or for the purpose of enforcing any Federal or State law with respect to the unlawful taking or restraint of a child or making or enforcing a child custody or visitation determination as defined in section 463(d)(1) of the Act. </P>
                            <P>(b) Only the central State PLS may make submittals to the Federal PLS for the purposes specified in paragraph (a) of this section. </P>
                            <P>(c) All submittals shall be made in the manner and form prescribed by the Office. </P>
                            <P>(d) All submittals shall contain the following information: </P>
                            <P>(1) The parent's or putative father's name; </P>
                            <P>(2) The parent's or putative father's Social Security Number (SSN). If the SSN is unknown, the IV-D program must make reasonable efforts to ascertain the individual's SSN before making a submittal to the Federal PLS; and </P>
                            <P>(3) Any other information prescribed by the Office. </P>
                            <P>(e) The director of the IV-D agency or his or her designee shall attest annually to the following: </P>
                            <P>(1)(i) The IV-D agency will only obtain information to facilitate the discovery of any individual in accordance with section 453(a)(2) of the Act for the purpose of establishing parentage, establishing, setting the amount of, modifying, or enforcing child support obligations, or for determining who has or may have parental rights with respect to a child, or in accordance with section 453(a)(3) of the Act for enforcing a State law with respect to the unlawful taking or restraint of a child, or for making or enforcing a child custody or visitation determination as defined in section 463(d)(1) of the Act. </P>
                            <P>(ii) The IV-D agency will only provide information to the authorized persons specified in sections 453(c) or 463(d) of the Act and § 302.35 of this chapter. </P>
                            <P>(2) In the case of a submittal made on behalf of a resident parent, legal guardian, attorney or agent of a child not receiving assistance under title IV-A, the IV-D agency must verify that the requesting individual has complied with the provisions of § 302.35 of this chapter. </P>
                            <P>(3) The IV-D agency will treat any information obtained through the Federal PLS and SPLS as confidential and shall safeguard the information under the requirements of sections 453(b), 453(l), 454(8), 454(26), and 463(c) of the Act, § 303.21 of this part and instructions issued by the Office. </P>
                            <P>(f)(1) The IV-D agency shall reimburse the Secretary for the fees required under: </P>
                            <P>(i) Section 453(e)(2) of the Act whenever Federal PLS services are furnished to a resident parent, legal guardian, attorney or agent of a child not receiving assistance under title IV-A of the Act; </P>
                            <P>(ii) Section 454(17) of the Act whenever Federal PLS services are furnished in parental kidnapping and child custody or visitation determination; </P>
                            <P>(iii) Section 453(k)(3) of the Act whenever a State agency receives information from the Federal PLS pursuant to section 453 of the Act. </P>
                            <P>(2)(i) The IV-D agency may charge an individual requesting information, or pay without charging the individual, the fees required under sections 453(e)(2), 453(k)(3) or 454(17) of the Act except that the IV-D agency shall charge an individual specified in section 453(c)(3) of the Act the fee required under section 453(e)(2) of the Act </P>
                            <P>(ii) The IV-D agency may recover the fee required under section 453(e)(2) of the Act from the noncustodial parent who owes a support obligation to a family on whose behalf the IV-D agency is providing services and repay it to the individual requesting information or itself. </P>
                            <P>(iii) State funds used to pay the fee under section 453(e)(2) of the Act are not program expenditures under the State plan but are program income under § 304.50 of this chapter. </P>
                            <P>(3) The fees referenced in paragraph (f)(1) of this section shall be in an amount determined to be reasonable payment for the information exchange. </P>
                            <P>(4)(i) If a State fails to transmit the fees charged by the Office under this section, the services provided by the Federal PLS in cases subject to the fees may be suspended until payment is received. </P>
                            <P>(ii) Fees shall be transmitted in the amount and manner prescribed by the Office in instructions.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="307">
                        <PART>
                            <HD SOURCE="HED">PART 307—COMPUTERIZED SUPPORT ENFORCEMENT SYSTEMS IN OPERATION AFTER OCTOBER 1, 1997 </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 307 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>42 U.S.C. 652 through 658, 664, 666 through 669A, and 1302. </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="405" PART="307">
                        <AMDPAR>2. Amend § 307.13 by revising paragraph (a) to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 307.13 </SECTNO>
                            <SUBJECT>Security and confidentiality for computerized support enforcement systems in operation after October 1, 1997. </SUBJECT>
                            <STARS/>
                            <P>
                                (a) 
                                <E T="03">Information integrity and security</E>
                                . Have safeguards protecting the integrity, accuracy, completeness of, access to, and use of data in the computerized support enforcement system. These safeguards shall include written policies concerning access to data by IV-D agency personnel, and the sharing of data with other persons to: 
                            </P>
                            <P>(1) Permit access to and use of data to the extent necessary to carry out the State IV-D program under this chapter; </P>
                            <P>(2) Specify the data which may be used for particular IV-D program purposes, and the personnel permitted access to such data; </P>
                            <P>(3) Permit exchanging information with State and Tribal agencies administering programs under titles IV, XIX, and XXI of the Act, to the extent necessary to carry out those State and Tribal agency responsibilities under such programs in accordance with section 454A(f)(3) of the Act, and to the extent that it does not interfere with IV-D program meeting its own obligations. </P>
                            <P>(4) Prohibit the disclosure of NDNH, FCR, financial institution, and IRS information outside the IV-D program except that: </P>
                            <P>(i) IRS information is restricted as specified in the Internal Revenue Code; </P>
                            <P>(ii) Independently verified information other than financial institution information may be released to authorized persons; </P>
                            <P>
                                (iii) NDNH and FCR information may be disclosed without independent verification to IV-B and IV-E agencies 
                                <PRTPAGE P="56446"/>
                                for the purposes of establishing parentage or establishing parental rights with respect to a child; and 
                            </P>
                            <P>(iv) NDNH and FCR information may be disclosed without independent verification to IV-A agencies for the purpose of assisting States to carry out their responsibilities of administering the Title IV-A programs. </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                </SUPLINF>
                <FRDOC>[FR Doc. E8-22054 Filed 9-25-08; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 4184-01-P </BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
</FEDREG>
