<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="fedregister.xsl"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
  <VOL>77</VOL>
  <NO>88</NO>
  <DATE>Monday, May 7, 2012</DATE>
  <UNITNAME>Contents</UNITNAME>
  <CNTNTS>
    <AGCY>
      <EAR>Agriculture</EAR>
      <PRTPAGE P="iii"/>
      <HD>Agriculture Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Food Safety and Inspection Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Forest Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Institute of Food and Agriculture</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Procurement and Property Management Office, Agriculture Department</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Rural Utilities Service</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Advisory Committee on Biotechnology and 21st Century Agriculture Meeting,</SJDOC>
          <PGS>26725</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10264</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Centers Medicare</EAR>
      <HD>Centers for Medicare &amp; Medicaid Services</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Medicaid Program; Community First Choice Option,</DOC>
          <PGS>26828-26903</PGS>
          <FRDOCBP D="75" T="07MYR2.sgm">2012-10294</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>26763-26764</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10947</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Children</EAR>
      <HD>Children and Families Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Assets for Independence Program Evaluation,</SJDOC>
          <PGS>26764-26765</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10735</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Coast Guard</EAR>
      <HD>Coast Guard</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Safety Zones:</SJ>
        <SJDENT>
          <SJDOC>Coast Guard Exercise, Hood Canal, WA,</SJDOC>
          <PGS>26699-26701</PGS>
          <FRDOCBP D="2" T="07MYR1.sgm">2012-10885</FRDOCBP>
        </SJDENT>
      </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>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>26736-26737</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10908</FRDOCBP>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10924</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Commodity Futures</EAR>
      <HD>Commodity Futures Trading Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>FY 2011 Schedule of Fees:</SJ>
        <SJDENT>
          <SJDOC>Reviews of Rule Enforcement Programs of Designated Contract Markets and Registered Futures Associations,</SJDOC>
          <PGS>26672-26674</PGS>
          <FRDOCBP D="2" T="07MYR1.sgm">2012-10898</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Swap Data Repositories:</SJ>
        <SJDENT>
          <SJDOC>Interpretative Statement Regarding the Confidentiality and Indemnification Provisions of Section 21(d) of the Commodity Exchange Act,</SJDOC>
          <PGS>26709-26713</PGS>
          <FRDOCBP D="4" T="07MYP1.sgm">2012-10918</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Defense Department</EAR>
      <HD>Defense Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Defense Science Board,</SJDOC>
          <PGS>26747-26748</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10844</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Department of Defense Wage Committee,</SJDOC>
          <PGS>26748</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10920</FRDOCBP>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10921</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Renewals of Department of Defense Federal Advisory Committees,</DOC>
          <PGS>26748-26749</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10938</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Department of Transportation</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Pipeline and Hazardous Materials Safety Administration</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Energy Department</EAR>
      <HD>Energy Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Energy Regulatory Commission</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>26749-26750</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10936</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Environmental Protection</EAR>
      <HD>Environmental Protection Agency</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>26750-26751</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10940</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Integrated Risk Information System; 2012 Program,</DOC>
          <PGS>26751-26755</PGS>
          <FRDOCBP D="4" T="07MYN1.sgm">2012-10935</FRDOCBP>
        </DOCENT>
        <SJ>Underground Injection Control Program; Hazardous Waste Injection Restrictions:</SJ>
        <SJDENT>
          <SJDOC>Diamond Shamrock Refining Company, LP, Sunray, Texas; Petition for Exemption - Class I Hazardous Waste Injection,</SJDOC>
          <PGS>26755</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10939</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Executive Office of the President</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Presidential Documents</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Export Import</EAR>
      <HD>Export-Import Bank</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Privacy Act; Systems of Records,</DOC>
          <PGS>26755-26758</PGS>
          <FRDOCBP D="3" T="07MYN1.sgm">2012-10897</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Farm Credit</EAR>
      <HD>Farm Credit Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>26758-26759</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-11058</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Aviation</EAR>
      <HD>Federal Aviation Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Airworthiness Directives:</SJ>
        <SJDENT>
          <SJDOC>The Boeing Company Model 767-200, -300, -300F, and -400ER Series Airplanes,</SJDOC>
          <PGS>26663-26667</PGS>
          <FRDOCBP D="4" T="07MYR1.sgm">2012-10570</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures,</DOC>
          <PGS>26667-26672</PGS>
          <FRDOCBP D="2" T="07MYR1.sgm">2012-10720</FRDOCBP>
          <FRDOCBP D="3" T="07MYR1.sgm">2012-10727</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Draft Airport Design Advisory Circular 150/5300-13A; Opportunity to Comment,</DOC>
          <PGS>26815</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10896</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Communications</EAR>
      <HD>Federal Communications Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Review of Emergency Alert System,</DOC>
          <PGS>26701-26703</PGS>
          <FRDOCBP D="2" T="07MYR1.sgm">2012-10622</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Election</EAR>
      <HD>Federal Election Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>26759</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-11079</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Emergency</EAR>
      <HD>Federal Emergency Management Agency</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Major Disaster Declarations:</SJ>
        <SJDENT>
          <SJDOC>Kentucky,</SJDOC>
          <PGS>26775</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10905</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>West Virginia,</SJDOC>
          <PGS>26775-26776</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10901</FRDOCBP>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10902</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Energy</EAR>
      <HD>Federal Energy Regulatory Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Enhancement of Electricity Market Surveillance and Analysis through Ongoing Electronic Delivery of Data from Regional Transmission Organizations and Independent System Operators,</DOC>
          <PGS>26674-26686</PGS>
          <FRDOCBP D="12" T="07MYR1.sgm">2012-9847</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Transmission Planning Reliability Standards,</DOC>
          <PGS>26686-26697</PGS>
          <FRDOCBP D="11" T="07MYR1.sgm">2012-10944</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <PRTPAGE P="iv"/>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Transmission Planning Reliability Standards,</DOC>
          <PGS>26714-26723</PGS>
          <FRDOCBP D="9" T="07MYP1.sgm">2012-10943</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Motor</EAR>
      <HD>Federal Motor Carrier Safety Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Motor Carrier Safety Advisory Committee,</SJDOC>
          <PGS>26815-26816</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10932</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Qualification of Drivers; Exemption Applications; Vision,</DOC>
          <PGS>26816-26818</PGS>
          <FRDOCBP D="2" T="07MYN1.sgm">2012-10929</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Railroad</EAR>
      <HD>Federal Railroad Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Inflation Adjustment of Aggravated Maximum Civil Monetary Penalty, etc.; Correction,</DOC>
          <PGS>26703-26704</PGS>
          <FRDOCBP D="1" T="07MYR1.sgm">2012-10946</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Reserve</EAR>
      <HD>Federal Reserve System</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company,</DOC>
          <PGS>26759</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10926</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies,</DOC>
          <PGS>26759-26760</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10832</FRDOCBP>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10927</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Trade</EAR>
      <HD>Federal Trade Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Analysis of Proposed Agreement Containing Consent Orders:</SJ>
        <SJDENT>
          <SJDOC>Kinder Morgan, Inc.,</SJDOC>
          <PGS>26760-26763</PGS>
          <FRDOCBP D="3" T="07MYN1.sgm">2012-10870</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Transit</EAR>
      <HD>Federal Transit Administration</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Buy America Waivers,</DOC>
          <PGS>26723-26724</PGS>
          <FRDOCBP D="1" T="07MYP1.sgm">2012-10851</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Limitation on Claims against Proposed Public Transportation Projects,</DOC>
          <PGS>26818</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10941</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Fish</EAR>
      <HD>Fish and Wildlife Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Endangered Species; Marine Mammals; Issuance of Permits,</DOC>
          <PGS>26777-26779</PGS>
          <FRDOCBP D="2" T="07MYN1.sgm">2012-10859</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Endangered Species; Receipt of Applications for Permit,</DOC>
          <PGS>26779-26780</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10858</FRDOCBP>
        </DOCENT>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Charles M. Russell National Wildlife Refuge and UL Bend National Wildlife Refuge, MT,</SJDOC>
          <PGS>26781-26784</PGS>
          <FRDOCBP D="3" T="07MYN1.sgm">2012-10886</FRDOCBP>
        </SJDENT>
        <SJ>Teleconferences:</SJ>
        <SJDENT>
          <SJDOC>Sport Fishing and Boating Partnership Council,</SJDOC>
          <PGS>26784-26785</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10957</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food and Drug</EAR>
      <HD>Food and Drug Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>New Animal Drugs:</SJ>
        <SJDENT>
          <SJDOC>Fomepizole; Change of Sponsor; Change of Sponsor Address; Change of Sponsor Name and Address,</SJDOC>
          <PGS>26697</PGS>
          <FRDOCBP D="0" T="07MYR1.sgm">2012-10892</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Debarment Orders:</SJ>
        <SJDENT>
          <SJDOC>David H.M. Phelps,</SJDOC>
          <PGS>26765-26766</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10958</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Karen L. Blyth,</SJDOC>
          <PGS>26766-26767</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10960</FRDOCBP>
        </SJDENT>
        <SJ>Regulatory Review Period for Purposes of Patent Extension:</SJ>
        <SJDENT>
          <SJDOC>PROLIA,</SJDOC>
          <PGS>26768</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10959</FRDOCBP>
        </SJDENT>
        <SJ>Workshops:</SJ>
        <SJDENT>
          <SJDOC>Educational Forum on Medical Device Reporting, Complaint Files, and Recalls, Corrections, and Removals,</SJDOC>
          <PGS>26769-26770</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10893</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Redefining the ‘C’ in CGMP:  Creating, Implementing, and Sustaining a Culture of Compliance,</SJDOC>
          <PGS>26768-26769</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10894</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food Safety</EAR>
      <HD>Food Safety and Inspection Service</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Food Ingredients and Sources of Radiation:</SJ>
        <SJDENT>
          <SJDOC>Listed and Approved for Use in Production of Meat and Poultry Products,</SJDOC>
          <PGS>26706-26709</PGS>
          <FRDOCBP D="3" T="07MYP1.sgm">2012-10871</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Changes to FSIS Traceback, Recall Procedures for Escherichia coli O157:</SJ>
        <SJDENT>
          <SJDOC>H7 Positive Raw Beef Product, and Availability of Compliance Guidelines,</SJDOC>
          <PGS>26725-26732</PGS>
          <FRDOCBP D="7" T="07MYN1.sgm">2012-10904</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Foreign Trade</EAR>
      <HD>Foreign-Trade Zones Board</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Proposed Production Activities:</SJ>
        <SJDENT>
          <SJDOC>Foreign-Trade Zone 235 - Lakewood, NJ; Cosmetic Essence Innovations, LLC (Fragrance Bottling); Holmdel, NJ,</SJDOC>
          <PGS>26737</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10953</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Forest</EAR>
      <HD>Forest Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Smiths Fork Vegetation Restoration Project, Uinta-Wasatch-Cache National Forest, Utah,</SJDOC>
          <PGS>26733-26734</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10728</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Forestry Research Advisory Council,</SJDOC>
          <PGS>26734</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10873</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>General Services</EAR>
      <HD>General Services Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Contract Financing Final Payment,</SJDOC>
          <PGS>26763</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10981</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Health and Human</EAR>
      <HD>Health and Human Services Department</HD>
      <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>Food and Drug Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Institutes of Health</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Substance Abuse and Mental Health Services Administration</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Homeland</EAR>
      <HD>Homeland Security Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Coast Guard</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Emergency Management Agency</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>U.S. Customs and Border Protection</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Homeland Security Advisory Council,</SJDOC>
          <PGS>26774-26775</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10930</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Indian Affairs</EAR>
      <HD>Indian Affairs Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Implementation of Indian Reservation Roads Program and Streamlining the Federal Delivery of Tribal Transportation Services,</DOC>
          <PGS>26785-26786</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10948</FRDOCBP>
        </DOCENT>
      </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>
    </AGCY>
    <AGCY>
      <EAR>Internal Revenue</EAR>
      <HD>Internal Revenue Service</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Allocation of Mortgage Insurance Premiums,</DOC>
          <PGS>26698-26699</PGS>
          <FRDOCBP D="1" T="07MYR1.sgm">2012-10937</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Adm</EAR>
      <HD>International Trade Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Countervailing Duty Investigations; Results, Extensions, Amendments, etc.:</SJ>
        <SJDENT>
          <SJDOC>High Pressure Steel Cylinders from People's Republic of China,</SJDOC>
          <PGS>26738-26739</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10954</FRDOCBP>
        </SJDENT>
        <PRTPAGE P="v"/>
        <SJ>Final Determinations of Sales at Less than Fair Value:</SJ>
        <SJDENT>
          <SJDOC>High Pressure Steel Cylinders from People's Republic of China,</SJDOC>
          <PGS>26739-26742</PGS>
          <FRDOCBP D="3" T="07MYN1.sgm">2012-10952</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Manufacturing Council Work Session,</SJDOC>
          <PGS>26743</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10980</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Com</EAR>
      <HD>International Trade Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Complaints:</SJ>
        <SJDENT>
          <SJDOC>Certain CMOS Image Sensors and Products Containing Same,</SJDOC>
          <PGS>26787-26788</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10889</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Certain Products Containing Interactive Program and Parental Control Technology,</SJDOC>
          <PGS>26786-26787</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10890</FRDOCBP>
        </SJDENT>
        <SJ>Investigations:</SJ>
        <SJDENT>
          <SJDOC>Certain Semiconductor Chips Having Synchronous Dynamic Random Access Memory Controllers and Products Containing Same,</SJDOC>
          <PGS>26789</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10834</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Certain Wireless Devices with 3G Capabilities and Components,</SJDOC>
          <PGS>26788</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10833</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Justice Department</EAR>
      <HD>Justice Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Justice Programs Office</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Lodging of Settlement Agreements,</DOC>
          <PGS>26789-26790</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10874</FRDOCBP>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10875</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Justice Programs</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>26790</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10850</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Land</EAR>
      <HD>Land Management Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Northeast California Resource Advisory Council,</SJDOC>
          <PGS>26786</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10888</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Maritime</EAR>
      <HD>Maritime Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Requested Administrative Waiver of the Coastwise Trade Laws:</SJ>
        <SJDENT>
          <SJDOC>Vessel BLUE PLANET,</SJDOC>
          <PGS>26819</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10861</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Vessel FREE SPIRIT,</SJDOC>
          <PGS>26818-26819</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10857</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Vessel KEALIA,</SJDOC>
          <PGS>26820</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10863</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Vessel LONGWOOD BATEAU,</SJDOC>
          <PGS>26822</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10867</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Vessel NORSK VIND,</SJDOC>
          <PGS>26821</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10862</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Vessel SUNCLIPPER II,</SJDOC>
          <PGS>26821-26822</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10864</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Vessel THE BLUE MOON,</SJDOC>
          <PGS>26820-26821</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10865</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Archives</EAR>
      <HD>National Archives and Records Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Records Schedules; Availability and Request for Comments,</DOC>
          <PGS>26791-26792</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10949</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Institute Food</EAR>
      <HD>National Institute of Food and Agriculture</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>26734-26735</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10934</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Institute</EAR>
      <HD>National Institutes of Health</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Center for Scientific Review Special Emphasis Panel,</SJDOC>
          <PGS>26771-26772</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10969</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Cancer Institute Frederick Advisory Committee,</SJDOC>
          <PGS>26772</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10964</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute on Aging Special Emphasis Panel,</SJDOC>
          <PGS>26770</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10965</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute on Alcohol Abuse and Alcoholism Special Emphasis Panel,</SJDOC>
          <PGS>26770-26771</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10978</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Office of the Director,</SJDOC>
          <PGS>26771</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10967</FRDOCBP>
        </SJDENT>
        <SJ>Prospective Grants of Exclusive Licenses:</SJ>
        <SJDENT>
          <SJDOC>Ocular Therapeutics Agent Delivery Devices and Methods for Making and Using Such Devices,</SJDOC>
          <PGS>26772-26773</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10836</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Oceanic</EAR>
      <HD>National Oceanic and Atmospheric Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Fisheries of Northeastern United States:</SJ>
        <SJDENT>
          <SJDOC>Northeast Multispecies, Monkfish, Atlantic Sea Scallop; Amendment 17,</SJDOC>
          <PGS>26704-26705</PGS>
          <FRDOCBP D="1" T="07MYR1.sgm">2012-10983</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Atlantic Highly Migratory Species Tournament Registration and Reporting,</SJDOC>
          <PGS>26743-26744</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10907</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Fishing Capacity Reduction Program for the Southeast Alaska Purse Seine Salmon Fishery,</DOC>
          <PGS>26744-26745</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10984</FRDOCBP>
        </DOCENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Fisheries of the Caribbean; Southeast Data, Assessment, and Review,</SJDOC>
          <PGS>26746-26747</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10900</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Gulf of Mexico Fishery Management Council,</SJDOC>
          <PGS>26745-26746</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10899</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Marine Fisheries Advisory Committee,</SJDOC>
          <PGS>26745</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10963</FRDOCBP>
        </SJDENT>
        <SJ>Permits:</SJ>
        <SJDENT>
          <SJDOC>Marine Mammals; File No. 15748,</SJDOC>
          <PGS>26747</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10966</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Science</EAR>
      <HD>National Science Foundation</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Advisory Committee for Polar Programs,</SJDOC>
          <PGS>26792</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10881</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Nuclear Regulatory</EAR>
      <HD>Nuclear Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Establishments of Atomic Safety and Licensing Boards:</SJ>
        <SJDENT>
          <SJDOC>Union Electric Co.,</SJDOC>
          <PGS>26792</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10925</FRDOCBP>
        </SJDENT>
        <SJ>Exemptions:</SJ>
        <SJDENT>
          <SJDOC>Florida Power and Light Co., St. Lucie Plant, Unit No. 2,</SJDOC>
          <PGS>26793-26795</PGS>
          <FRDOCBP D="2" T="07MYN1.sgm">2012-10928</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Personnel</EAR>
      <HD>Personnel Management Office</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Political Activity - Federal Employees Residing in Designated Localities,</DOC>
          <PGS>26659-26660</PGS>
          <FRDOCBP D="1" T="07MYR1.sgm">2012-10951</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Pipeline</EAR>
      <HD>Pipeline and Hazardous Materials Safety Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Pipeline Safety:</SJ>
        <SJDENT>
          <SJDOC>Verification of Records,</SJDOC>
          <PGS>26822-26824</PGS>
          <FRDOCBP D="2" T="07MYN1.sgm">2012-10866</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Postal Regulatory</EAR>
      <HD>Postal Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Product List Changes,</DOC>
          <PGS>26795-26796</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10945</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Postal Service</EAR>
      <HD>Postal Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Product Change - Standard Mail Saturation Flats Negotiated Service Agreement,</DOC>
          <PGS>26796</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10860</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Presidential Documents</EAR>
      <HD>Presidential Documents</HD>
      <CAT>
        <HD>PROCLAMATIONS</HD>
        <SJ>Special Observances:</SJ>
        <SJDENT>
          <SJDOC>Jewish American Heritage Month (Proc. 8813),</SJDOC>
          <PGS>26905-26908</PGS>
          <FRDOCBP D="3" T="07MYD0.sgm">2012-11134</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Foster Care Month (Proc. 8814),</SJDOC>
          <PGS>26909-26910</PGS>
          <FRDOCBP D="1" T="07MYD1.sgm">2012-11135</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Procurement</EAR>
      <PRTPAGE P="vi"/>
      <HD>Procurement and Property Management Office, Agriculture Department</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Guidelines for the Transfer of Excess Computers or Other Technical Equipment Pursuant to Section 14220 of the 2008 Farm Bill,</DOC>
          <PGS>26660-26663</PGS>
          <FRDOCBP D="3" T="07MYR1.sgm">2012-10745</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Research Innovative</EAR>
      <HD>Research and Innovative Technology Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Reporting Required for International Civil Aviation Organization,</SJDOC>
          <PGS>26824</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10909</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Submission of Audit Reports; Part 248,</SJDOC>
          <PGS>26824-26825</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10910</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Rural Utilities</EAR>
      <HD>Rural Utilities Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>26735-26736</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10872</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Securities</EAR>
      <HD>Securities and Exchange Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Orders of Suspension of Trading:</SJ>
        <SJDENT>
          <SJDOC>Airtrax, Inc., Amedia Networks, Inc., American Business Financial Services, Inc., et al.,</SJDOC>
          <PGS>26796</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-11020</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>HydroGenetics, Inc.,</SJDOC>
          <PGS>26796</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10985</FRDOCBP>
        </SJDENT>
        <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
        <SJDENT>
          <SJDOC>BATS Exchange, Inc.,</SJDOC>
          <PGS>26811-26812</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10880</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>BATS Y-Exchange, Inc.,</SJDOC>
          <PGS>26808-26809</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10879</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Chicago Board Options Exchange, Inc.,</SJDOC>
          <PGS>26813-26814</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10877</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>ICE Clear Credit LLC,</SJDOC>
          <PGS>26810-26811</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10912</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>International Securities Exchange, LLC,</SJDOC>
          <PGS>26812-26813</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10878</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NYSE Amex LLC,</SJDOC>
          <PGS>26798-26808</PGS>
          <FRDOCBP D="10" T="07MYN1.sgm">2012-10876</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>The Depository Trust Company,</SJDOC>
          <PGS>26796-26798</PGS>
          <FRDOCBP D="2" T="07MYN1.sgm">2012-10911</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>State Department</EAR>
      <HD>State Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Culturally Significant Objects Imported for Exhibition Determinations:</SJ>
        <SJDENT>
          <SJDOC>Modern Landscapes,</SJDOC>
          <PGS>26814</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10979</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Substance</EAR>
      <HD>Substance Abuse and Mental Health Services Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>26773-26774</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10882</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Surface Transportation</EAR>
      <HD>Surface Transportation Board</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Abandonment Exemptions:</SJ>
        <SJDENT>
          <SJDOC>Iowa River Railroad, Inc., Marshall and Hardin Counties, IA,</SJDOC>
          <PGS>26825-26826</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10913</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Tennessee</EAR>
      <HD>Tennessee Valley Authority</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>26815</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10855</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Transportation Department</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 Motor Carrier Safety Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Railroad Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Transit Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Maritime Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Pipeline and Hazardous Materials Safety Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Research and Innovative Technology Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Surface Transportation Board</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Treasury</EAR>
      <HD>Treasury Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Internal Revenue Service</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Customs</EAR>
      <HD>U.S. Customs and Border Protection</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Declaration of Persons Who Performed Repairs or Alterations,</SJDOC>
          <PGS>26776-26777</PGS>
          <FRDOCBP D="1" T="07MYN1.sgm">2012-10906</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>U.S. China</EAR>
      <HD>U.S.-China Economic and Security Review Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Open Public Hearing,</DOC>
          <PGS>26826</PGS>
          <FRDOCBP D="0" T="07MYN1.sgm">2012-10869</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>26828-26903</PGS>
        <FRDOCBP D="75" T="07MYR2.sgm">2012-10294</FRDOCBP>
      </DOCENT>
      <HD>Part III</HD>
      <DOCENT>
        <DOC>Presidential Documents,</DOC>
        <PGS>26905-26910</PGS>
        <FRDOCBP D="3" T="07MYD0.sgm">2012-11134</FRDOCBP>
        <FRDOCBP D="1" T="07MYD1.sgm">2012-11135</FRDOCBP>
      </DOCENT>
    </PTS>
    <AIDS>
      <HD SOURCE="HED">Reader Aids</HD>
      <P>Consult the Reader Aids section at the end of this page 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>77</VOL>
  <NO>88</NO>
  <DATE>Monday, May 7, 2012</DATE>
  <UNITNAME>Rules and Regulations</UNITNAME>
  <RULES>
    <RULE>
      <PREAMB>
        <PRTPAGE P="26659"/>
        <AGENCY TYPE="F">OFFICE OF PERSONNEL MANAGEMENT</AGENCY>
        <RIN>RIN 3206-AM44</RIN>
        <CFR>5 CFR Part 733</CFR>
        <SUBJECT>Political Activity—Federal Employees Residing in Designated Localities</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of Personnel Management.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>OPM is amending its regulations to grant Federal employees residing in King George County, Virginia, a partial exemption from the political activity restrictions in the Hatch Act, and to add King George County to its regulatory list of designated localities. The amendment reflects OPM's determination that King George County meets the criteria in the Hatch Act and OPM regulations for a partial exemption to issue.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective June 6, 2012.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Jo-Ann Chabot, Office of the General Counsel, United States Office of Personnel Management, (202) 606-1700.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Hatch Act, at 5 U.S.C. 7323(a)(2) and (3), prohibits Federal employees from becoming candidates for partisan political office and from soliciting, accepting, or receiving political contributions. However, 5 U.S.C. 7325, authorizes OPM to prescribe regulations permitting employees in certain communities to participate in local elections for partisan political office without regard to the prohibitions in 5 U.S.C. 7323(a)(2) and (3) only if the requirements described in section 7325 are met. The first requirement is that the community or political subdivision must be located in Maryland or Virginia, and in the immediate vicinity of the District of Columbia. Alternatively, the majority of the community's registered voters must be employed by the United States Government. The second requirement is that OPM must determine that it is in the domestic interest of the employees to permit that political participation because of special or unusual circumstances existing in the community or political subdivision. These statutory requirements are reflected in 5 CFR 733.107(a). Under 5 CFR part 733, the exemption from the prohibitions in 5 U.S.C. 7323(a)(2) and (3) is a partial exemption because in 5 CFR 733.103-733.106, OPM has established limitations on political participation by most Federal employees residing in these designated municipalities and subdivisions.</P>

        <P>On August 22, 2011, OPM issued a proposed rule at 72 FR 39582 to add King George County, Virginia, to this regulatory list of designated localities at 5 CFR 733.107(c). In its notice of proposed rulemaking, OPM noted that King George County, Virginia, had fulfilled the statutory requirements for a partial exemption to issue and proposed the addition of King George County to the regulatory list of designated localities. 76 FR 52287 (August 22, 2011). OPM also placed a legal notice in the print edition of<E T="03">The Free Lance Star</E>on September 9, 2011. OPM did not receive any comments on the proposed rule during the 60-day notice and comment period.</P>
        <P>Therefore, OPM is adding King George County to its list of designated localities at 5 CFR 733.107(c). When this rule becomes effective, Federally employed residents of King George County will be permitted under 5 CFR 733.103 to participate in the following activities:</P>
        
        <EXTRACT>
          <P>(1) Run as independent candidates for election to partisan political office in elections for local county office in King George County;</P>
          <P>(2) Solicit, accept, or receive a political contribution as, or on behalf of, an independent candidate for partisan political office in elections for local office in King George County;</P>
          <P>(3) Accept or receive a political contribution on behalf of an individual who is a candidate for local partisan political office and who represents a political party;</P>
          <P>(4) Solicit, accept, or receive uncompensated volunteer services as an independent candidate, or on behalf of an independent candidate, for local partisan political office, in connection with the local elections of King George County; and</P>
        </EXTRACT>
        <EXTRACT>
          <P>(5) Solicit, accept, or receive uncompensated volunteer services on behalf of an individual who is a candidate for local partisan political office and who represents a political party.</P>
        </EXTRACT>
        
        <FP>Under 5 CFR 733.104 of title 5, however, Federally employed residents of King George County may not:</FP>
        
        <EXTRACT>
          <P>(1) Run as the representative of a political party for local partisan political office;</P>
          <P>(2) Solicit a political contribution on behalf of an individual who is a candidate for local partisan political office and who represents a political party;</P>
          <P>(3) Knowingly solicit a political contribution from any Federal employee, except as permitted under 5 U.S.C. 7323(a)(2)(A)-(C).</P>
          <P>(4) Accept or receive a political contribution from a subordinate;</P>
          <P>(5) Solicit, accept, or receive uncompensated volunteer services from a subordinate for any political purpose;</P>
          <P>(6) Participate in political activities:</P>
          <P>○ While they are on duty:</P>
          <P>○ While they are wearing a uniform, badge, or insignia that identifies the employing agency or instrumentality or the position of the employee;</P>
          <P>○ While they are in any room or building occupied in the discharge of official duties by an individual employed or holding office in the Government of the United States or any agency or instrumentality thereof; or</P>
          <P>○ While using a Government-owned or leased vehicle or while using a privately owned vehicle in the discharge of official duties.</P>
        </EXTRACT>
        
        <FP>Moreover, candidacy for, and service in, a partisan political office shall not result in neglect of, or interference with, the performance of the duties of the employee or create a conflict, or apparent conflict, of interest.</FP>
        <P>Sections 733.103 and 733.104 of Title 5, Code of Federal Regulations, do not apply to individuals, such as career senior executives and employees of the Federal Bureau of Investigation, who are employed in the agencies or positions listed in 5 CFR 733.105(a). These individuals are subject to the more stringent limitations described in 5 CFR 733.105 and 733.106.</P>

        <P>Individuals who require advice concerning specific political activities, and whether an activity is permitted or prohibited under 5 CFR 733.103-733.106, should contact the United States Office of Special Counsel at (800) 854-2824 or (202) 254-3650. Requests for Hatch Act advisory opinions may be made by email to:<E T="03">hatchact@osc.gov.</E>
        </P>

        <P>King George County will be listed after Herndon, Virginia, and before<PRTPAGE P="26660"/>Loudoun County, Virginia, at 5 CFR 733.107(c).</P>
        <HD SOURCE="HD1">E.O. 12866, Regulatory Review</HD>
        <P>This regulation has been reviewed by the Office of Management and Budget in accordance with E.O. 12866.</P>
        <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
        <P>I certify that this regulation will not have a significant economic impact on a substantial number of small entities because the changes will affect only employees of the Federal Government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 5 CFR Part 733</HD>
          <P>Political activities (Government employees).</P>
        </LSTSUB>
        <SIG>
          <FP>U.S. Office of Personnel Management.</FP>
          
          <NAME>John Berry,</NAME>
          <TITLE>Director.</TITLE>
        </SIG>
        
        <P>Accordingly, the Office of Personnel Management amends 5 CFR part 733 as follows:</P>
        <REGTEXT PART="733" TITLE="5">
          <PART>
            <HD SOURCE="HED">PART 733—POLITICAL ACTIVITY—FEDERAL EMPLOYEES RESIDING IN DESIGNATED LOCALITIES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 733 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>5 U.S.C. 7325; sec. 308 of Pub. L. 104-93, 109 Stat. 961, 966 (Jan. 6, 1996)</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="733" TITLE="5">
          <AMDPAR>2. Section 733.107(c) is amended by adding King George County, Virginia, alphabetically to the list of designated Virginia municipalities and political subdivisions as set forth below.</AMDPAR>
          <SECTION>
            <SECTNO>§ 733.107</SECTNO>
            <SUBJECT>Designated localities.</SUBJECT>
            <STARS/>
            <P>(c) * * *</P>
            <P>In Virginia</P>
            <STARS/>
            <P>King George County June 6, 2012.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10951 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6325-48-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Office of Procurement and Property Management</SUBAGY>
        <CFR>7 CFR Part 3203</CFR>
        <RIN>RIN 0599-AA13</RIN>
        <SUBJECT>Guidelines for the Transfer of Excess Computers or Other Technical Equipment Pursuant to Section 14220 of the 2008 Farm Bill</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of Procurement and Property Management, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Office of Procurement and Property Management (OPPM) of the U.S. Department of Agriculture (USDA) is establishing and implementing procedures for the transfer of excess computers or other technical equipment for the purposes of distribution to a city, town, or local government entity in a rural area.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>June 6, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Mr. Michael R. Johnson, Office of Procurement and Property Management, USDA on (202) 720-9779 or by Email at<E T="03">michaelr.johnson@dm.usda.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">A. Background</HD>
        <P>A proposed rule was published in the<E T="04">Federal Register</E>on May 16, 2011 (76 FR 28188-28191, FR Doc No: 2011-11601) soliciting comments on the establishment of Guidelines for the Transfer of Excess Computers or Other Technical Equipment Pursuant to Section 14220 of the 2008 Farm Bill. The proposed rule would have established 7 CFR part 3201, but the final rule will be establishing part 3203. The proposed rule had a comment period of 60 days ending July 15, 2011. No comments were received through email, fax, mail, or hand delivery/courier. A total of 12 comments were received through the Federal eRulemaking Portal. Of the comments received, two were sent as tests, nine were submitted to the wrong docket and subsequently moved to the correct docket, and one comment had multiple questions and comments that were put into one of three categories: (1) Comments on the Farm Bill itself, which will not be addressed; (2) Questions on personal property disposal which are covered by Federal Management Regulations, Agriculture Property Management Regulations and internal agency regulations and policies, and will not be addressed; and (3) A question that asked who is responsible and what happens to the equipment if the items are refurbished and the intended recipient changes its mind or cannot pay the cost (go to<E T="03">www.Regulations.gov</E>to see entire comment). Two revisions have been made as a result of the comment referenced above: 1. The word `designated' has been added before `organization' in sections 3203.6(c), 3203.7 and 3203.8; and 2. Additional language has been added to section 3203.4(e)(5) stating that the recipient needs to furnish a copy of the agreement between the recipient and its designated organization.</P>
        <HD SOURCE="HD1">B. Executive Orders Number 12866 and 13563</HD>
        <P>Executive Orders 13563 and 12866 direct 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). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This rule has been designated a non-significant regulatory action under section 3(f) of Executive Order 12866. Accordingly, the rule has not been reviewed by the Office of Management and Budget.</P>
        <P>This rule implements Section 14220 of the 2008 Farm Bill. It is expected that the benefits that accrue to cities, towns, and local government entities in rural areas from the receipt of excess USDA computers and technical equipment will exceed the costs to USDA in providing such equipment.</P>
        <HD SOURCE="HD1">C. Regulatory Flexibility Act</HD>

        <P>USDA certifies that this rule will not have a significant impact on a substantial number of small entities as defined in the Regulatory Flexibility Act, 5 U.S.C. 601,<E T="03">et seq.</E>The impact of this regulation will be primarily limited to rural towns and government entities. The Department estimates that 400 eligible entities will submit requests for donated equipment annually. As small businesses are not considered eligible entities under this regulation, the rule will not have a significant impact on the small business community or on a substantial number of small businesses. The Department invited comments on its estimates for the potential impact of this rule on small businesses and did not receive any comments.</P>
        <HD SOURCE="HD1">D. Paperwork Reduction Act</HD>
        <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 through 3520), the information collection is currently approved under OMB control number 0505-0023.</P>
        <HD SOURCE="HD1">E. Executive Order 12630</HD>

        <P>This rule has been reviewed in accordance with Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights, and does not contain policies that would have implications for these rights.<PRTPAGE P="26661"/>
        </P>
        <HD SOURCE="HD1">F. Executive Order 13132</HD>
        <P>This rule has been reviewed in accordance with Executive Order 13132, Federalism, and does not have sufficient federalism implications to warrant the preparation of a Federalism Assessment. Provisions of this rule will not have a substantial direct effect on States or their political subdivisions or on the distribution of power and responsibilities among the various government levels.</P>
        <HD SOURCE="HD1">G. Unfunded Mandates Reform Act of 1995</HD>
        <P>This rule contains no Federal mandates under the regulatory provisions of Title II of the Unfunded Mandates Reform Act of 1995 (UMRA), and therefore a written statement is not required.</P>
        <HD SOURCE="HD1">H. Executive Order 12372</HD>
        <P>This rule has been reviewed in accordance with Executive Order 12372, Intergovernmental review of Federal programs, and does not establish federal financial assistance or direct Federal development with State and local governments, and is therefore outside the scope of Executive Order 12372, which requires intergovernmental consultation with State and local officials.</P>
        <HD SOURCE="HD1">I. Executive Order 13175</HD>
        <P>This rule has been reviewed in accordance with Executive Order 13175, Consultation and Coordination With Indian Tribal Governments, and does not have tribal implications or impose unfunded mandates with Indian tribes.</P>
        <HD SOURCE="HD1">J. E-Government Act Compliance</HD>
        <P>USDA is committed to compliance with the E-Government Act, which requires Government agencies, in general, to provide the public the option of submitting information or transacting business electronically to the maximum extent possible. This rule requires one letter from requestors that can be sent electronically to USDA. USDA will continue to seek other avenues to increase electronically submitted information.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 7 CFR 3203</HD>
          <P>Computers, Excess, Excess computers, Excess government property, Government property, Other technical equipment, Personal property, Technical equipment.</P>
        </LSTSUB>
        
        <P>For the reasons set forth in the preamble, the Department of Agriculture adds 7 CFR part 3203 to read as follows:</P>
        <REGTEXT PART="3203" TITLE="7">
          <PART>
            <HD SOURCE="HED">PART 3203—GUIDELINES FOR THE TRANSFER OF EXCESS COMPUTERS OR OTHER TECHNICAL EQUIPMENT PURSUANT TO SECTION 14220 OF THE 2008 FARM BILL</HD>
            <CONTENTS>
              <SECHD>Sec.</SECHD>
              <SECTNO>3203.1</SECTNO>
              <SUBJECT>Purpose.</SUBJECT>
              <SECTNO>3203.2</SECTNO>
              <SUBJECT>Eligibility.</SUBJECT>
              <SECTNO>3203.3</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <SECTNO>3203.4</SECTNO>
              <SUBJECT>Procedures.</SUBJECT>
              <SECTNO>3203.5</SECTNO>
              <SUBJECT>Dollar limitation.</SUBJECT>
              <SECTNO>3203.6</SECTNO>
              <SUBJECT>Restrictions.</SUBJECT>
              <SECTNO>3203.7</SECTNO>
              <SUBJECT>Title.</SUBJECT>
              <SECTNO>3203.8</SECTNO>
              <SUBJECT>Costs.</SUBJECT>
              <SECTNO>3203.9</SECTNO>
              <SUBJECT>Accountability and recordkeeping.</SUBJECT>
              <SECTNO>3203.10</SECTNO>
              <SUBJECT>Disposal.</SUBJECT>
              <SECTNO>3203.11</SECTNO>
              <SUBJECT>Liabilities and losses.</SUBJECT>
            </CONTENTS>
            <AUTH>
              <HD SOURCE="HED">Authority:</HD>
              <P>7 U.S.C. 2206b.</P>
            </AUTH>
            <SECTION>
              <SECTNO>§ 3203.1</SECTNO>
              <SUBJECT>Purpose.</SUBJECT>
              <P>This part sets forth the procedures to be utilized by USDA when transferring excess USDA computers or other technical equipment to an organization for the purposes of distribution to a city, town, or local government entity in a rural area as authorized by 7 U.S.C. 2206b.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 3203.2</SECTNO>
              <SUBJECT>Eligibility.</SUBJECT>
              <P>To be eligible under this part:</P>
              <P>(a) A city, town, or local government entity must be located in a rural area as defined in 7 U.S.C. 1991(a)(13)(A).</P>
              <P>(b) A designated organization must:</P>
              <P>(1) Have the documented capability to refurbish and distribute excess computers or other technical equipment;</P>
              <P>(2) Serve the interest of cities, towns, or local government entities in rural areas; and</P>
              <P>(3) Have been designated by an official of a city, town, or local government entity in a rural area to receive excess computers or other technical equipment under this part.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 3203.3</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <P>
                <E T="03">Cannibalization</E>means to remove serviceable parts from one item of equipment in order to install them on another item of equipment in order to repair or enhance its operability.</P>
              <P>
                <E T="03">City, town, or local government entity in a rural area</E>as defined in 7 U.S.C. 1991(a)(13)(A) means any area other than:</P>
              <P>(1) A city or town that has a population of greater than 50,000 inhabitants; and</P>
              <P>(2) Any urbanized area contiguous and adjacent to such a city or town described in paragraph (1) of this definition.</P>
              <P>
                <E T="03">Computers or other technical equipment</E>means central processing units, laptops, desktops, computer mouses, keyboards, monitors, related peripheral tools (e.g., printers, modems, routers, servers, multimedia projectors, multifunctional devices, external hard drives) and fax machines. This term may also include computer software where the transfer of a license is permitted.</P>
              <P>
                <E T="03">Designated Organization</E>means an organization that has been selected by an official of a city, town, or local government entity in a rural area to provide refurbishing services on donated computer and technical equipment.</P>
              <P>
                <E T="03">Excess</E>means any property under the control of a USDA agency that is no longer required for that agency's or another USDA agency's needs, as determined by the agency head or designee.</P>
              <P>
                <E T="03">Property Management Officer (PMO)</E>is an eligible recipient's designated point of contact, responsible for adherence to procedures described in this part.</P>
              <P>
                <E T="03">Recipient</E>means a city, town, or local government entity located in a rural area as defined in 7 U.S.C. 1991(a)(13)(A) that may receive excess computers or other technical equipment under this part.</P>
              <P>
                <E T="03">Refurbish</E>means to make `like new' by the process of major maintenance or minor repair of an item, either aesthetically or mechanically.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 3203.4</SECTNO>
              <SUBJECT>Procedures.</SUBJECT>
              <P>(a) Each agency head will designate, in writing, an authorized official to approve transfers of excess computers or other technical equipment under this part consistent with the Department's policies on personal property management.</P>
              <P>(b) Excess computers or other technical equipment must first be internally screened to ensure it is not needed elsewhere in the Department.</P>
              <P>(c) To receive information concerning the availability of USDA excess computers or other technical equipment, an eligible recipient's PMO should contact any USDA office near to its location.</P>
              <P>(d) The USDA employee responsible for personal property, at the office contacted, will review the request for eligibility of the recipient and the availability of excess computers or other technical equipment. The USDA employee will inform the requestor of the outcome of the review (e.g. eligibility, the availability of excess computers or other technical equipment).</P>

              <P>(e) Eligible recipients will express their interest in receiving property under this part by submitting a request, on letterhead paper (electronic copy is<PRTPAGE P="26662"/>acceptable), to a USDA authorized official. All requests must originate from, and be signed by, a representative of an eligible recipient city, town, or local government entity. Requests must include:</P>
              <P>(1) Type of excess computers or other technical equipment requested (should include specifications);</P>
              <P>(2) Justification for eligibility (see § 3203.2);</P>
              <P>(3) Contact information of the requestor;</P>
              <P>(4) Logistical information such as when and how the property will be picked up; and</P>
              <P>(5) Information on the recipient's designated organization (company name, contact person and phone number) that is designated to receive and refurbish the property for the eligible recipient along with a copy of the agreement between the recipient and its designated organization.</P>
              <P>(f) Excess computers or other technical equipment should be inspected before the property is transferred or the USDA agency should be contacted to verify the condition of the property.</P>
              <P>(g) If the condition of the property is acceptable, the recipient or its designated organization will coordinate with the USDA contact for transfer of the property. Since the USDA agency office may have several requests for property, it is critical that the recipient or its designated organization contact USDA as soon as possible. Property will usually be allocated on a first-come, first-served basis, taking into account fair and equitable distribution of excess computers or other technical equipment to all eligible recipients.</P>
              <P>(h) Transfers will be accomplished using the appropriate USDA property transfer form. The transfer form must contain the following statement: “Property listed on this form is being transferred pursuant to the provisions in 7 CFR Part 3203.” The form must be signed by an authorized official of the USDA agency and an official of the recipient organization.</P>
              <P>(i) A copy of the request that transferred the property must be attached to the transfer order and kept in the USDA agency's files.</P>
              <P>(j) When property is transferred to a designated organization, a copy of the completed transfer document will be sent to the eligible recipient government entity for its records. Eligible recipients are responsible for following up with the designated organization they have designated for the final receipt of the property.</P>
              <P>(k) In cases where an agency receives competing requests for excess computers or other technical equipment, to the extent permitted by law, the agency shall give full consideration to such factors as national defense requirements, emergency needs, energy conservation, preclusion of new procurement, fair and equitable distribution, transportation costs, and retention of title in the Government.</P>
              <P>(l) Prior to transferring any property pursuant to this Act, the transferring agency must remove data from the excess computers or other technical equipment (memory or any kind of data storage device) according to accepted sanitization procedures. To the maximum extent practicable, the transferring agency must remove data using a means that does not remove, disable, destroy, or otherwise render unusable the excess computers or other technical equipment or components. It is imperative that agencies take the necessary steps to ensure that no personal computer, server, external storage device, or related electronic component is transferred that might contain sensitive or confidential information. See Departmental Manual 3575-001, Security Controls in the System Life Cycle/System Development Life Cycle, for additional guidance.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 3203.5</SECTNO>
              <SUBJECT>Dollar limitation.</SUBJECT>
              <P>There is no dollar limitation on excess computers or other technical equipment obtained under this part.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 3203.6</SECTNO>
              <SUBJECT>Restrictions.</SUBJECT>
              <P>(a) Only an authorized USDA official may approve the transfer of excess computers or other technical equipment under this part.</P>
              <P>(b) Excess computers or other technical equipment may be transferred for the purpose of cannibalization, provided that the requestor submits a statement clearly indicating that cannibalization of the requested property will have greater benefit than utilization of the item in its existing form. Cannibalization is a secondary use of equipment and, therefore, these requests are considered subordinate to requests for primary use.</P>
              <P>(c) Designated organizations will only receive property for cannibalization when it has been specifically requested by the recipient and the cannibalized parts must only be used in computers or other technical equipment destined for eligible recipients.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 3203.7</SECTNO>
              <SUBJECT>Title.</SUBJECT>
              <P>Title of ownership to excess computers or other technical equipment transferred under this part shall automatically pass to the recipient once the transferring agency and recipient or designated organization sign the transfer form indicating that the designated organization has received the property.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 3203.8</SECTNO>
              <SUBJECT>Costs.</SUBJECT>
              <P>The designated organization must pay any costs associated with packaging and transportation of the property unless it has made other arrangements. The designated organization must remove property from the USDA agency's premises within 15 calendar days after being notified that the property is available for pickup, unless otherwise coordinated with the USDA agency. If the recipient decides prior to picking up or removing the property that it no longer wants the property, it must notify the USDA agency that approved the transfer request that the property is no longer needed.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 3203.9</SECTNO>
              <SUBJECT>Accountability and recordkeeping.</SUBJECT>
              <P>(a) USDA requires all excess computers or other technical equipment received by an eligible recipient pursuant to this part be placed into use within one year of receipt of the property and used for at least one year thereafter. The recipient's PMO must maintain accountable records for such property during this time period.</P>
              <P>(b) GSA requires that all excess personal property given to non-federal recipients be reported each fiscal year. USDA agencies that transfer property under this part must report the transfers in their annual reports to OPPM and include both the recipient and organization names. OPPM will review the reports for accuracy, as well as fair and equitable distribution of the excess computers or other technical equipment, before submitting to GSA.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 3203.10</SECTNO>
              <SUBJECT>Disposal.</SUBJECT>
              <P>When property received under this part is no longer needed by the recipient, it must be disposed of in an environmentally sound manner that is not detrimental or dangerous to public health or safety and in accordance with all Federal, State and local laws.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 3203.11</SECTNO>
              <SUBJECT>Liabilities and losses.</SUBJECT>
              <P>USDA assumes no liability with respect to accidents, bodily injury, illness, or any other damages or loss related to excess computers or other technical equipment transferred under this part. The recipient/designated organization is advised to insure or otherwise protect itself and others as appropriate.</P>
            </SECTION>
            <SIG>
              <PRTPAGE P="26663"/>
              <DATED>Dated: April 27, 2012.</DATED>
              <NAME>Lisa M. Wilusz,</NAME>
              <TITLE>Director.</TITLE>
            </SIG>
          </PART>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10745 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-TX-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 39</CFR>
        <DEPDOC>[Docket No. FAA-2011-0044; Directorate Identifier 2010-NM-059-AD; Amendment 39-17039; AD 2012-09-04]</DEPDOC>
        <RIN>RIN 2120-AA64</RIN>
        <SUBJECT>Airworthiness Directives; The Boeing Company Model 767-200, -300, -300F, and -400ER Series Airplanes</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>We are superseding an existing airworthiness directive (AD) that applies to The Boeing Company Model 767-200, -300, and -300F series airplanes. That AD currently requires inspections to detect cracking or corrosion of the fail-safe straps between the side fitting of the rear spar bulkhead at body station 955 and the skin; and follow-on and corrective actions. This new AD expands the applicability; and adds an inspection for cracking in the fail-safe strap, and repair or replacement if necessary. This AD was prompted by additional reports of cracks in 51 fail-safe straps on 41 airplanes; we have also received a report of a crack found in the “T” fitting that connects the fail-safe strap to the outboard edge of the pressure deck. We are issuing this AD to detect and correct fatigue cracking or corrosion of the fail-safe straps and the “T” fittings, which could result in cracking of adjacent structure and consequent reduced structural integrity of the fuselage.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This AD is effective June 11, 2012.</P>
          <P>The Director of the Federal Register approved the incorporation by reference of certain publications listed in the AD as of June 11, 2012.</P>
          <P>The Director of the Federal Register approved the incorporation by reference of certain other publications listed in this AD as of November 1, 2004 (69 FR 57636, September 27, 2004, as referenced in 70 FR 58000, October 5, 2005).</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, P.O. Box 3707, MC 2H-65, Seattle, Washington 98124-2207; telephone 206-544-5000, extension 1, fax 206-766-5680; email<E T="03">me.boecom@boeing.com;</E>Internet<E T="03">https://www.myboeingfleet.com.</E>You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, Washington 98057-3356. For information on the availability of this material at the FAA, call 425-227-1221.</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 AD, the regulatory evaluation, any comments received, and other information. The address for the Docket Office (phone: 800-647-5527) is Document Management Facility, 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>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Berhane Alazar, Aerospace Engineer, Airframe Branch, ANM-120S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue SW., Renton, Washington 98057-3356; phone: 425-917-6577; fax: 425-917-6590; email:<E T="03">berhane.alazar@faa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Discussion</HD>

        <P>We issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 to supersede AD 2004-19-06 R1, amendment 39-14313 (70 FR 58000, October 5, 2005). That AD applies to The Boeing Company Model 767-200, -300, and -300F series airplanes. The NPRM published in the<E T="04">Federal Register</E>on February 24, 2011 (76 FR 10288). That NPRM proposed to continue to require inspections to detect cracking or corrosion of the fail-safe straps between the side fitting of the rear spar bulkhead at body station 955 and the skin; and follow-on and corrective actions. That NPRM also proposed to expand the applicability, and add an inspection for cracking in the fail-safe strap, and repair or replacement if necessary.</P>
        <HD SOURCE="HD1">Comments</HD>
        <P>We gave the public the opportunity to participate in developing this AD. The following presents the comments received on the proposal and the FAA's response to each comment.</P>
        <HD SOURCE="HD1">Request To Add Airplanes to Applicability</HD>
        <P>Aviation Partners Boeing (APB) asked that we include airplanes in the NPRM (76 FR 10288, February 24, 2011) that have been modified with winglets, in accordance with Supplemental Type Certificate (STC) ST01920SE. APB stated that it completed an analysis of Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010, and determined that the defined rework limits are valid when winglets are installed. APB added that including these airplanes will reduce the effort to support requests for alternative methods of compliance (AMOCs) to the NPRM.</P>
        <P>We acknowledge APB's request to include airplanes modified with winglets in accordance with the referenced STC in the applicability of this AD. We received an analysis package from APB which verifies that the compliance information included in Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010, is adequate to provide an acceptable level of safety for airplanes equipped with those winglets. Those airplanes are listed in the effectivity section of Revision 2 of this service bulletin, which is identified in the applicability section of this AD. We have not changed the AD in this regard. However, since the referenced STC does not affect accomplishment of the requirements of this AD, we have clarified that an AMOC is not necessary for these airplanes by adding this provision in new Note 1 to paragraph (c) of this AD. We have also reidentified subsequent notes.</P>
        <HD SOURCE="HD1">Request To Change Supplementary Information Section of NPRM</HD>
        <P>Boeing noted that in the Supplementary Information section of the NPRM (76 FR 10288, February 24, 2011), there is an error under “Actions Since Existing AD Was Issued.” Boeing asked for a correction to the “flight cycles” data in the sentence “Fail-safe straps were repaired on 33 airplanes with total accumulated flight cycles ranging from 39,886 to 89,236.” Boeing stated that the correct flight cycles range is “9,250 to 38,490,” and the correct flight hours range is “39,886 to 89,236,” as published in Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010.</P>

        <P>We agree with Boeing that there is an error in the number of flight cycles specified under “Actions Since Existing AD Was Issued;” the correct number of flight cycles was inadvertently omitted<PRTPAGE P="26664"/>from the NPRM (76 FR 10288, February 24, 2011). However, since that section of the preamble does not reappear in the final rule, no change to the AD has been made in this regard.</P>
        <HD SOURCE="HD1">Request To Change the Unsafe Condition</HD>
        <P>Boeing asked that we enhance the clarity of the unsafe condition that is given as the reason for issuing the NPRM (76 FR 10288, February 24, 2011) because the “T” fittings should not be included in the unsafe condition. Boeing noted that the proposed actions are for detecting and repairing corrosion or cracking of the fail-safe straps. Boeing added that inspections of the “T” fitting were added to Revision 2, dated January 15, 2010, of Boeing Alert Service Bulletin 767-53A0100, so that a removed/kept “T” fitting would be installed in a condition that contains no detectable damage around the three fastener holes that connect to the fail-safe strap. Boeing stated that the inspections are intended only to increase damage detection prior to installation of a kept “T” fitting.</P>
        <P>We agree that emphasizing the fail-safe strap is the main issue in this AD; however, we do not agree that the unsafe condition should be changed to remove the reference to the “T” fittings. Some “T” fitting cracks have been reported since issuance of the existing AD, as noted in Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010; therefore, the “T” fitting is part of the unsafe condition. We have not changed this AD in this regard.</P>
        <HD SOURCE="HD1">Request To Change Paragraph (k) of This AD</HD>
        <P>Continental Airlines (CAL) asked that we change paragraph (k) of the NPRM (76 FR 10288, February 24, 2011) to include contacting Boeing with corrosion damage details to obtain further repair instructions and/or approval. CAL stated that paragraph (k) of the NPRM requires that the corrosion on the fail-safe straps be repaired in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010. CAL added that paragraph 3.B.7 of the Accomplishment Instructions specifies that if corrosion is found on the fail-safe straps, it should be removed as given in Chapter 51-10-02 of the Boeing 767 Structural Repair Manual (SRM). CAL noted that it did not find any information pertaining to the fail-safe straps when reviewing the SRM for the correct rework limits. CAL believes the corrosion removal instructions are incomplete.</P>
        <P>We agree that corrosion removal instructions specified in Chapter 51-10-02 of the SRM do not specifically identify how to blend out corrosion on the fail-safe straps. That chapter contains general procedures for repairing corrosion (which apply to the fail-safe straps), which include inspection, repair, and rework limits but does not contain specific procedures for removing corrosion from fail-safe straps.</P>
        <P>We have received Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012. That revision removes the reference to the SRM in Step 3.B.7., and instead specifies to contact Boeing for repair instructions. Therefore we have revised paragraph (k) of this AD to specify that where Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012, specifies to contact Boeing for repair, this AD requires repair using a method approved in accordance with paragraph (o) of this AD.</P>
        <P>Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012, also adds notes and revised steps to provide flexibility and revised figures to correct errors. These changes include revising a Standard Operating Practices Manual (SOPM) reference to specify SOPM 20-20-00, adding a fastener code to Figure 28 that was omitted, and revising cable identification labels in Figures 32 and 34. We have revised this AD to refer to Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012, as the appropriate source of service information for accomplishing the required actions. We have added Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010, to paragraph (n) of this AD to give credit for doing actions before the effective date of this AD, using that revision.</P>
        <HD SOURCE="HD1">Request To Change Certain References in the Service Information</HD>
        <P>CAL asked that certain references in Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010, be changed, as follows:</P>
        <P>CAL stated that the use of the procedures in the Standard Wiring Practices Manual, Section 20-20-00, should be allowed for the resistance check of bonding fasteners during the panel installation. CAL stated that the standard operating manual reference specified in the resistance check of bonding fasteners during the panel installation does not provide the maximum resistance value.</P>
        <P>CAL noted that Figure 28 of the Accomplishment Instructions of Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010, which identifies Fastener Code “B,” is missing from the top corner of the panel.</P>
        <P>CAL also noted that the circle control numbers identified in Figures 32 and 34 of the Accomplishment Instructions of Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010, do not match the aileron control cables and work instructions. CAL stated that the control cable turnbuckle body station locations are reversed.</P>
        <P>We acknowledge the commenter's concerns regarding the referenced figures and SOPM. The actions specified in the SOPM and those figures are only referred to in the service bulletin for optional guidance. As stated previously, Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012, corrects these errors. We have made no change to the AD in this regard.</P>
        <HD SOURCE="HD1">Explanation of Additional Changes Made to This AD</HD>
        <P>We have made the following changes to this AD:</P>
        <P>• Revised certain headers throughout this AD.</P>
        <P>• Redesignated Note 2 of the NPRM (76 FR 10288, February 24, 2011) as paragraph (g)(3) in this AD, and redesignated subsequent notes accordingly.</P>
        <P>• Revised the heading for and wording of paragraph (n) of this AD; this change has not changed the intent of that paragraph.</P>
        <HD SOURCE="HD1">Conclusion</HD>
        <P>We reviewed the relevant data, considered the comments received, and determined that air safety and the public interest require adopting the AD with the changes described previously—and minor editorial changes. We have determined that these minor changes:</P>
        <P>• Are consistent with the intent that was proposed in the NPRM (76 FR 10288, February 24, 2011) for correcting the unsafe condition; and</P>
        <P>• Do not add any additional burden upon the public than was already proposed in the NPRM (76 FR 10288, February 24, 2011).</P>
        <P>We also determined that these changes will not increase the economic burden on any operator or increase the scope of the AD.</P>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>We estimate that this AD will affect 390 airplanes of U.S. registry.</P>

        <P>We estimate the following costs to comply with this AD:<PRTPAGE P="26665"/>
        </P>
        <GPOTABLE CDEF="s100,r100,6,r50,r50" COLS="5" OPTS="L2,i1">
          <TTITLE>Estimated Costs</TTITLE>
          <BOXHD>
            <CHED H="1">Action</CHED>
            <CHED H="1">Labor cost</CHED>
            <CHED H="1">Parts cost</CHED>
            <CHED H="1">Cost per product</CHED>
            <CHED H="1">Cost on U.S.<LI>operators</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Inspection for Model 767-200, -300, and -300F airplanes (retained actions from AD 2004-19-06 R1, Amendment 39-14313 (70 FR 58000, October 5, 2005))</ENT>
            <ENT>2 work-hours × $85 per hour = $170 per inspection cycle</ENT>
            <ENT>$0</ENT>
            <ENT>$170 per inspection cycle</ENT>
            <ENT>$60,180 per inspection cycle.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">New inspections for all airplanes (new action)</ENT>
            <ENT>2 work-hours × $85 per hour = $170 per inspection cycle</ENT>
            <ENT>0</ENT>
            <ENT>$170 per inspection cycle</ENT>
            <ENT>$66,300 per inspection cycle.</ENT>
          </ROW>
        </GPOTABLE>
        <P>We estimate the following costs to do any necessary repairs/replacements that would be required based on the results of the inspection. We have no way of determining the number of aircraft that might need these repairs/replacements:</P>
        <GPOTABLE CDEF="s75,r100,r50,r50" COLS="4" OPTS="L2,i1">
          <TTITLE>On-Condition Costs</TTITLE>
          <BOXHD>
            <CHED H="1">Action</CHED>
            <CHED H="1">Labor cost</CHED>
            <CHED H="1">Parts cost</CHED>
            <CHED H="1">Cost per product</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Repair or replacement, Groups 1-7, 10, and 11 airplanes</ENT>
            <ENT>295 work-hours × $85 per hour = $25,075</ENT>
            <ENT>Between $9,054 and $15,837</ENT>
            <ENT>Between $34,129 and $40,912.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Repair or replacement, Groups 8 and 9 airplanes</ENT>
            <ENT>297 work hours × $85 per hour = $25,245</ENT>
            <ENT>Between $32,593 and $32,727</ENT>
            <ENT>Between $57,838 and $57,972.</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>This AD will not have federalism implications under Executive Order 13132. This AD 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.</P>
        <P>For the reasons discussed above, I certify that this AD:</P>
        <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
        <P>(2) Is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),</P>
        <P>(3) Will not affect intrastate aviation in Alaska, and</P>
        <P>(4) 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>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
          <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Adoption of the Amendment</HD>
        <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
        <REGTEXT PART="39" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40113, 44701.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="39" TITLE="14">
          <SECTION>
            <SECTNO>§ 39.13</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. The FAA amends § 39.13 by removing airworthiness directive (AD) 2004-19-06 R1, Amendment 39-14313 (70 FR 58000, October 5, 2005), and adding the following new AD:</AMDPAR>
          
          <EXTRACT>
            <FP SOURCE="FP-2">
              <E T="04">2012-09-04The Boeing Company:</E>Amendment 39-17039; Docket No. FAA-2011-0044; Directorate Identifier 2010-NM-059-AD.</FP>
            <HD SOURCE="HD1">(a) Effective Date</HD>
            <P>This AD is effective June 11, 2012.</P>
            <HD SOURCE="HD1">(b) Affected ADs</HD>
            <P>This AD supersedes AD 2004-19-06 R1, Amendment 39-14313 (70 FR 58000, October 5, 2005).</P>
            <HD SOURCE="HD1">(c) Applicability</HD>
            <P>This AD applies to Model 767-200, -300, -300F, and -400ER series airplanes, certificated in any category; as identified in Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012.</P>
            <NOTE>
              <HD SOURCE="HED">Note 1 to paragraph (c) of this AD:</HD>
              <P>Supplemental Type Certificate (STC) ST01920SE (<E T="03">http://rgl.faa.gov/Regulatory_and_Guidance_Library/rgstc.nsf/0/082838ee177dbf62862576a4005cdfc0/$FILE/ST01920SE.pdf</E>) does not affect the ability to accomplish the actions required by this AD. Therefore, for airplanes on which STC ST01920SE is installed, a “change in product” alternative method of compliance (AMOC) approval request is not necessary to comply with the requirements of 14 CFR 39.17. For all other AMOC requests, the operator must request approval for an AMOC according to paragraph (o) of this AD.</P>
            </NOTE>
            <HD SOURCE="HD1">(d) Subject</HD>
            <P>Joint Aircraft System Component (JASC)/Air Transport Association (ATA) of America Code 53, Fuselage.</P>
            <HD SOURCE="HD1">(e) Unsafe Condition</HD>
            <P>This AD was prompted by additional reports of cracks in 51 fail-safe straps on 41 airplanes; we have also received a report of a crack found in the “T” fitting that connects the fail-safe strap to the outboard edge of the pressure deck. We are issuing this AD to detect and correct fatigue cracking or corrosion of the fail-safe straps and the “T” fittings, which could result in cracking of adjacent structure and consequent reduced structural integrity of the fuselage.</P>
            <HD SOURCE="HD1">(f) Compliance</HD>

            <P>Comply with this AD within the compliance times specified, unless already done.<PRTPAGE P="26666"/>
            </P>
            <HD SOURCE="HD1">(g) Retained Inspections and Follow-on/Corrective Actions With New Service Information</HD>
            <P>These inspection requirements are retained from AD 2004-19-06 R1, Amendment 39-14313 (70 FR 58000, October 5, 2005). For Model 767-200, -300, and -300F series airplanes having line numbers 1 through 931 inclusive: Except as provided by paragraph (h) of this AD, prior to the accumulation of 15,000 total flight cycles, or within 3,000 flight cycles after November 1, 2004 (the effective date of AD 2004-19-06 R1, Amendment 39-14313, 70 FR 58000, October 5, 2005), whichever occurs later, perform a detailed inspection and eddy current inspection to detect cracking or corrosion of the fail-safe straps between the side fitting of the rear spar bulkhead at body station (BS) 955 and the skin, per Figure 2 of the Accomplishment Instructions of Boeing Alert Service Bulletin 767-53A0100, dated September 26, 2002; Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010; or Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012. As of the effective date of this AD, use only Boeing Alert Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012. Doing the inspections required by paragraph (i) of this AD terminates the requirements of this paragraph.</P>
            <P>(1) If no crack or corrosion is found, repeat the inspections thereafter at intervals not to exceed 6,000 flight cycles or 36 months, whichever occurs first, until paragraph (i) of this AD is done.</P>
            <P>(2) If any crack or corrosion is found, before further flight, repair per a method approved by the Manager, Seattle Aircraft Certification Office (ACO), FAA; or using a method approved in accordance with paragraph (o) of this AD.</P>
            <P>(3) 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>
            <HD SOURCE="HD1">(h) Retained Inspections and Follow-on/Corrective Actions</HD>
            <P>These inspection requirements are retained from AD 2004-19-06 R1, Amendment 39-14313 (70 FR 58000, October 5, 2005). For airplanes identified in paragraph (g) of this AD on which the fail-safe strap has been replaced before November 1, 2004: Do the actions required by paragraph (g) of this AD within 12,000 flight cycles after accomplishing the replacement.</P>
            <NOTE>
              <HD SOURCE="HED">Note 2 to paragraph (h) of this AD:</HD>
              <P>Steps 2 and 8 of the Work Instructions of Boeing Alert Service Bulletin 767-53A0100, dated September 26, 2002, refer incorrectly to Boeing 767 Airplane Maintenance Manual (AMM) 32-00-20 for guidance on opening the MLG doors; the correct reference is Boeing 767 AMM 32-00-15, which is referred to in steps 3 and 7 of the Work Instructions. Step 2 also should state “Open Main Landing Gear (MLG) doors” instead of “Open Main Landing Green (MLG) doors.”</P>
            </NOTE>
            <HD SOURCE="HD1">(i) New Repetitive Detailed and Eddy Current Inspections</HD>
            <P>Prior to the accumulation of 15,000 total flight cycles, or within 3,000 flight cycles after the effective date of this AD, whichever occurs later: Perform detailed and eddy current inspections to detect cracking and/or corrosion of the fail-safe straps between the side fitting of the rear spar bulkhead at BS 955 and the skin, in accordance with the Accomplishment Instructions of Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012. If no crack or corrosion is found, repeat the inspections thereafter at intervals not to exceed 6,000 flight cycles or 36 months, whichever occurs first. Accomplishing the actions required by this paragraph ends the requirements of paragraphs (g) and (g)(1) of this AD.</P>
            <HD SOURCE="HD1">(j) New Repetitive Ultrasonic Inspections</HD>
            <P>Prior to the accumulation of 15,000 total flight cycles, or within 3,000 flight cycles after the effective date of this AD, whichever occurs later: Do an ultrasonic inspection of the fail-safe strap for cracking, and all applicable related investigative actions, in accordance with the Accomplishment Instructions of Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012. Do all applicable related investigative actions before further flight. If no crack is found, repeat the inspection thereafter at intervals not to exceed 6,000 flight cycles or 36 months, whichever occurs first.</P>
            <HD SOURCE="HD1">(k) New Corrective Actions</HD>
            <P>If any corrosion is found during any inspection required by paragraph (i) of this AD: Before further flight, repair the corrosion, in accordance with the Accomplishment Instructions of Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012; except where Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012, specifies to contact Boeing for repair, before further flight, repair using a method approved in accordance with paragraph (o) of this AD.</P>
            <HD SOURCE="HD1">(l) New Corrective Actions</HD>
            <P>If any crack is found during any inspection required by paragraph (i) or (j) of this AD: Before further flight, repair in accordance with the Accomplishment Instructions of Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012; except where Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012, specifies to contact Boeing for appropriate action, before further flight, repair using a method approved in accordance with the procedures specified in paragraph (o) of this AD. Accomplishing the fail-safe strap trim repair in accordance with Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012, ends the repetitive inspections required by paragraphs (i) and (j) of this AD only on the side of the airplane where the repair was done. Replacing the fail-safe strap with a replacement strap that has the revised edge configuration in accordance with Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012, ends the repetitive inspections required by paragraphs (i) and (j) of this AD only on the side of the airplane where the replacement was done.</P>
            <HD SOURCE="HD1">(m) New Post-Replacement Inspections</HD>
            <P>For any replacement strap that does not have a revised edge configuration, as specified in Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012: Within 12,000 flight cycles after doing the replacement, accomplish the inspections required by paragraphs (i) and (j) of this AD. Repeat the inspections thereafter at intervals not to exceed 6,000 flight cycles or 36 months, whichever occurs first. Replacing the fail-safe strap with a replacement strap that has the revised edge configuration in accordance with Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012, ends the repetitive inspections required by paragraphs (i) and (j) of this AD only on the side of the airplane where the replacement was done.</P>
            <HD SOURCE="HD1">(n) New Credit for Previous Actions</HD>
            <P>This paragraph provides credit for actions required by paragraphs (g) through (m) of this AD, if those actions were performed before the effective date of this AD using Boeing Alert Service Bulletin 767-53A0100, Revision 1, dated August 11, 2006; or Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010.</P>
            <HD SOURCE="HD1">(o) Alternative Methods of Compliance (AMOCs)</HD>

            <P>(1) The Manager, Seattle ACO, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the ACO, send it to the attention of the person identified in the Related Information section of this AD. Information may be emailed to:<E T="03">9-ANM-Seattle-ACO-AMOC-Requests@faa.gov.</E>
            </P>
            <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.</P>
            <P>(3) An AMOC that provides an acceptable level of safety may be used for any repair required by this AD if it is approved by the Boeing Commercial Airplanes Organization Designation Authorization (ODA) that has been authorized by the Manager, Seattle ACO, to make those findings. For a repair method to be approved, the repair must meet the certification basis of the airplane and 14 CFR 25.571, Amendment 45, and the approval must specifically refer to this AD.</P>
            <P>(4) AMOCs approved for AD 2004-19-06, Amendment 39-13800 (69 FR 57636, September 27, 2004); and AD 2004-19-06 R1, Amendment 39-14313 (70 FR 58000, October 5, 2005); are approved as AMOCs for paragraphs (g) and (h) of this AD, as applicable.</P>
            <HD SOURCE="HD1">(p) Related Information</HD>

            <P>For more information about this AD, contact Berhane Alazar, Aerospace Engineer, Airframe Branch, ANM-120S, FAA, Seattle<PRTPAGE P="26667"/>ACO, 1601 Lind Avenue SW., Renton, Washington 98057-3356; phone: (425) 917-6577; fax: (425) 917-6590; email:<E T="03">berhane.alazar@faa.gov.</E>
            </P>
            <HD SOURCE="HD1">(q) Material Incorporated by Reference</HD>

            <P>(1) You must use the following service information to do the actions required by this AD, unless the AD specifies otherwise. The Director of the<E T="04">Federal Register</E>approved the incorporation by reference (IBR) under 5 U.S.C. 552(a) and 1 CFR part 51 of the following service information on the date specified.</P>
            <P>(i) Boeing Service Bulletin 767-53A0100, Revision 3, dated February 6, 2012, approved for IBR June 11, 2012.</P>
            <P>(ii) Boeing Alert Service Bulletin 767-53A0100, Revision 2, dated January 15, 2010, approved for IBR June 11, 2012.</P>
            <P>(iii) Boeing Alert Service Bulletin 767-53A0100, dated September 26, 2002; approved for IBR November 1, 2004 (69 FR 57636, September 27, 2004, as referenced in 70 FR 58000, October 5, 2005).</P>

            <P>(2) For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, P.O. Box 3707, MC 2H-65, Seattle, Washington 98124-2207; telephone 206-544-5000, extension 1; fax 206-766-5680; email<E T="03">me.boecom@boeing.com;</E>Internet<E T="03">https://www.myboeingfleet.com.</E>
            </P>
            <P>(3) You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.</P>

            <P>(4) You may also review copies of the service information that is incorporated by reference 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/cfr/ibr_locations.html.</E>
            </P>
          </EXTRACT>
        </REGTEXT>
        <SIG>
          <DATED>Issued in Renton, Washington on April 23, 2012.</DATED>
          <NAME>Michael Kaszycki,</NAME>
          <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10570 Filed 5-4-12; 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 97</CFR>
        <DEPDOC>[Docket No. 30840; Amdt. No. 3477]</DEPDOC>
        <SUBJECT>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments</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 rule establishes, amends, suspends, or revokes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective May 7, 2012. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.</P>
          <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of May 7, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Availability of matter incorporated by reference in the amendment is as follows:</P>
          <P>For Examination—</P>
          <P>1. FAA Rules Docket, FAA Headquarters Building, 800 Independence Avenue SW., Washington, DC 20591;</P>
          <P>2. The FAA Regional Office of the region in which the affected airport is located;</P>
          <P>3. The National Flight Procedures Office, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or,</P>

          <P>4. 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>
          <P>
            <E T="03">Availability</E>—All SIAPs are available online free of charge. Visit<E T="03">nfdc.faa.gov</E>to register. Additionally, individual SIAP and Takeoff Minimums and ODP copies may be obtained from:</P>
          <P>1. FAA Public Inquiry Center (APA-200), FAA Headquarters Building, 800 Independence Avenue SW., Washington, DC 20591; or</P>
          <P>2. The FAA Regional Office of the region in which the affected airport is located.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Richard A. Dunham III, Flight Procedure Standards Branch (AFS-420) Flight Technologies and Programs Division, Flight Standards Service, Federal Aviation Administration, Mike Monroney Aeronautical Center, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 (Mail Address: P.O. Box 25082, Oklahoma City, OK 73125) telephone: (405) 954-4164.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This rule amends Title 14, Code of Federal Regulations, Part 97 (14 CFR part 97) by amending the referenced SIAPs. The complete regulatory description of each SIAP is listed on the appropriate FAA Form 8260, as modified by the National Flight Data Center (FDC)/Permanent Notice to Airmen (P-NOTAM), and is incorporated by reference in the amendment under 5 U.S.C. 552(a), 1 CFR part 51, and § 97.20 of Title 14 of the Code of Federal Regulations.</P>

        <P>The large number of SIAPs, their complex nature, and the need for a special format make their verbatim publication in the<E T="04">Federal Register</E>expensive and impractical. Further, airmen do not use the regulatory text of the SIAPs, but refer to their graphic depiction on charts printed by publishers of aeronautical materials. Thus, the advantages of incorporation by reference are realized and publication of the complete description of each SIAP contained in FAA form documents is unnecessary. This amendment provides the affected CFR sections and specifies the types of SIAP and the corresponding effective dates. This amendment also identifies the airport and its location, the procedure and the amendment number.</P>
        <HD SOURCE="HD1">The Rule</HD>
        <P>This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP as amended in the transmittal. For safety and timeliness of change considerations, this amendment incorporates only specific changes contained for each SIAP as modified by FDC/P-NOTAMs.</P>
        <P>The SIAPs, as modified by FDC P-NOTAM, and contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these changes to SIAPs, the TERPS criteria were applied only to specific conditions existing at the affected airports. All SIAP amendments in this rule have been previously issued by the FAA in a FDC NOTAM as an emergency action of immediate flight safety relating directly to published aeronautical charts. The circumstances which created the need for all these SIAP amendments requires making them effective in less than 30 days.</P>

        <P>Because of the close and immediate relationship between these SIAPs and safety in air commerce, I find that notice<PRTPAGE P="26668"/>and public procedure before adopting these SIAPs are impracticable and contrary to the public interest and, where applicable, that good cause exists for making these SIAPs effective in less than 30 days.</P>
        <HD SOURCE="HD1">Conclusion</HD>
        <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. It, therefore—(1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under 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. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 97</HD>
          <P>Air Traffic Control, Airports, Incorporation by reference, and Navigation (Air).</P>
        </LSTSUB>
        <SIG>
          <DATED>Issued in Washington, DC, on April 27, 2012.</DATED>
          <NAME>Ray Towles,</NAME>
          <TITLE>Deputy Director, Flight Standards Service.</TITLE>
        </SIG>
        <HD SOURCE="HD1">Adoption of the Amendment</HD>
        <P>Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal regulations, Part 97, 14 CFR part 97, is amended by amending Standard Instrument Approach Procedures, effective at 0901 UTC on the dates specified, as follows:</P>
        <REGTEXT PART="97" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 97—STANDARD INSTRUMENT APPROACH PROCEDURES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 97 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="97" TITLE="14">
          <AMDPAR>2. Part 97 is amended to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§§ 97.23, 97.25, 97.27, 97.29, 97.31, 97.33, 97.35</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
            <P>By amending: § 97.23 VOR, VOR/DME, VOR or TACAN, and VOR/DME or TACAN; § 97.25 LOC, LOC/DME, LDA, LDA/DME, SDF, SDF/DME; § 97.27 NDB, NDB/DME; § 97.29 ILS, ILS/DME, MLS, MLS/DME, MLS/RNAV; § 97.31 RADAR SIAPs; § 97.33 RNAV SIAPs; and § 97.35 COPTER SIAPs, Identified as follows:</P>
            
            <EXTRACT>
              <P>* * * Effective Upon Publication</P>
            </EXTRACT>
            <GPOTABLE CDEF="xs48,xls20,r50,r50,10,10,xs120" COLS="7" OPTS="L2,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1">AIRAC Date</CHED>
                <CHED H="1">State</CHED>
                <CHED H="1">City</CHED>
                <CHED H="1">Airport</CHED>
                <CHED H="1">FDC No.</CHED>
                <CHED H="1">FDC Date</CHED>
                <CHED H="1">Subject</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>MO</ENT>
                <ENT>St Louis</ENT>
                <ENT>Lambert-St Louis Intl</ENT>
                <ENT>2/1136</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 6, Amdt 1C</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>MO</ENT>
                <ENT>Columbia</ENT>
                <ENT>Columbia Rgnl</ENT>
                <ENT>2/1214</ENT>
                <ENT>4/20/12</ENT>
                <ENT>RNAV (GPS) RWY 31, Orig</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>AK</ENT>
                <ENT>Soldotna</ENT>
                <ENT>Soldotna</ENT>
                <ENT>2/1292</ENT>
                <ENT>4/20/12</ENT>
                <ENT>VOR A, Amdt 7</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>MT</ENT>
                <ENT>Billings</ENT>
                <ENT>Billings Logan Intl</ENT>
                <ENT>2/1298</ENT>
                <ENT>4/20/12</ENT>
                <ENT>VOR/DME RWY 28R, Amdt 14</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>KY</ENT>
                <ENT>Covington</ENT>
                <ENT>Cincinnati/Northern Kentucky Intl</ENT>
                <ENT>2/1417</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 18R, ILS RWY 18R (CAT II), Amdt 1A</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>KY</ENT>
                <ENT>Covington</ENT>
                <ENT>Cincinnati/Northern Kentucky Intl</ENT>
                <ENT>2/1418</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 36C, ILS RWY 36C (CAT II), ILS RWY 36C (CAT III), Amdt 41A</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>KY</ENT>
                <ENT>Covington</ENT>
                <ENT>Cincinnati/Northern Kentucky Intl</ENT>
                <ENT>2/1419</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 36L, ILS RWY 36L (CAT II), Amdt 1A</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>KY</ENT>
                <ENT>Covington</ENT>
                <ENT>Cincinnati/Northern Kentucky Intl</ENT>
                <ENT>2/1420</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 36R, ILS RWY 36R (CAT II), ILS RWY 36R (CAT III), Amdt 8A</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1439</ENT>
                <ENT>4/11/12</ENT>
                <ENT>ILS OR LOC RWY 36R, ILS RWY 36R (CAT II0), ILS RWY 36R (CAT III), Amdt 3B</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1441</ENT>
                <ENT>4/11/12</ENT>
                <ENT>ILS OF LOC RWY 36L, ILS RWY 36L (CAT II), ILS RWY 36L (CAT III), Amdt 14C</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1442</ENT>
                <ENT>4/11/12</ENT>
                <ENT>ILS OR LOC RWY 36C, ILS RWY 36C (CAT II), ILS RWY 36C (CAT III), Amdt 3B</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>OH</ENT>
                <ENT>Batavia</ENT>
                <ENT>Clermont County</ENT>
                <ENT>2/1617</ENT>
                <ENT>4/20/12</ENT>
                <ENT>NDB RWY 22, Amdt 1</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>OH</ENT>
                <ENT>Batavia</ENT>
                <ENT>Clermont County</ENT>
                <ENT>2/1623</ENT>
                <ENT>4/20/12</ENT>
                <ENT>VOR B, Amdt 7</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>MN</ENT>
                <ENT>Mankato</ENT>
                <ENT>Mankato Rgnl</ENT>
                <ENT>2/1869</ENT>
                <ENT>4/20/12</ENT>
                <ENT>RNAV (GPS) RWY 22, Orig</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1907</ENT>
                <ENT>4/11/12</ENT>
                <ENT>RNAV (RNP) Y RWY 18L, Orig-B</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1908</ENT>
                <ENT>4/11/12</ENT>
                <ENT>RNAV (GPS) Z RWY 18C, Amdt 2</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1909</ENT>
                <ENT>4/11/12</ENT>
                <ENT>RNAV (RNP) Y RWY 18C, Orig-A</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1910</ENT>
                <ENT>4/11/12</ENT>
                <ENT>RNAV (GPS) Z RWY 18R, Amdt 2</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1911</ENT>
                <ENT>4/11/12</ENT>
                <ENT>ILS OR LOC RWY 18R, Amdt 14A</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1913</ENT>
                <ENT>4/11/12</ENT>
                <ENT>ILS OR LOC RWY 18L, Amdt 2B</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1918</ENT>
                <ENT>4/11/12</ENT>
                <ENT>RNAV (GPS) Z RWY 18L, Amdt 2</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1919</ENT>
                <ENT>4/11/12</ENT>
                <ENT>RNAV (RNP) Y RWY 18R, Orig-B</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1920</ENT>
                <ENT>4/11/12</ENT>
                <ENT>RNAV (RNP) X RWY 18L, Orig-B</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1921</ENT>
                <ENT>4/11/12</ENT>
                <ENT>RNAV (RNP) X RWY 18R, Orig-B</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TN</ENT>
                <ENT>Memphis</ENT>
                <ENT>Memphis Intl</ENT>
                <ENT>2/1922</ENT>
                <ENT>4/11/12</ENT>
                <ENT>ILS OR LOC RWY 18C, Amdt 1B</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>WI</ENT>
                <ENT>Milwaukee</ENT>
                <ENT>General Mitchell Intl</ENT>
                <ENT>2/2232</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 1L, ILS RWY 1L (CAT II), ILS RWY 1L (CAT III), Amdt 9A</ENT>
              </ROW>
              <ROW>
                <PRTPAGE P="26669"/>
                <ENT I="01">31-May-12</ENT>
                <ENT>WY</ENT>
                <ENT>Cheyenne</ENT>
                <ENT>Cheyenne Rgnl/Jerry Olson Field</ENT>
                <ENT>2/3058</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 27, Amdt 34B</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>PA</ENT>
                <ENT>Perkasie</ENT>
                <ENT>Pnnridge</ENT>
                <ENT>2/3117</ENT>
                <ENT>4/11/12</ENT>
                <ENT>RNAV (GPS) RWY 26, Orig</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>PA</ENT>
                <ENT>Perkasie</ENT>
                <ENT>Pnnridge</ENT>
                <ENT>2/3154</ENT>
                <ENT>4/11/12</ENT>
                <ENT>NDB OR GPS A, Amdt 2</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>PA</ENT>
                <ENT>Perkasie</ENT>
                <ENT>Pnnridge</ENT>
                <ENT>2/3164</ENT>
                <ENT>4/11/12</ENT>
                <ENT>RNAV (GPS) RWY 8, Amdt 1</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>VA</ENT>
                <ENT>Luray</ENT>
                <ENT>Luray Caverns</ENT>
                <ENT>2/4789</ENT>
                <ENT>4/20/12</ENT>
                <ENT>RNAV (GPS) RWY 4, Orig</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>VA</ENT>
                <ENT>Luray</ENT>
                <ENT>Luray Caverns</ENT>
                <ENT>2/4790</ENT>
                <ENT>4/20/12</ENT>
                <ENT>NDB A, Amdt 7</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>VA</ENT>
                <ENT>Luray</ENT>
                <ENT>Luray Caverns</ENT>
                <ENT>2/4791</ENT>
                <ENT>4/20/12</ENT>
                <ENT>VOR/DME B, Amdt 3</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>VA</ENT>
                <ENT>Luray</ENT>
                <ENT>Luray Caverns</ENT>
                <ENT>2/4792</ENT>
                <ENT>4/20/12</ENT>
                <ENT>RNAV (GPS) RWY 22, Amdt 1</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>UT</ENT>
                <ENT>Milford</ENT>
                <ENT>Milford Muni/Den And Judy Briscoe Field</ENT>
                <ENT>2/5298</ENT>
                <ENT>4/20/12</ENT>
                <ENT>RNAV (GPS) RWY 16, Orig</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>LA</ENT>
                <ENT>New Orleans</ENT>
                <ENT>Louis Armstrong New Orleans Intl</ENT>
                <ENT>2/5888</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 10, ILS RWY 10 (CAT II), ILS RWY 10 (CAT III), Amdt 2B</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>IL</ENT>
                <ENT>Chicago</ENT>
                <ENT>Chicago O'Hare Intl</ENT>
                <ENT>2/6031</ENT>
                <ENT>4/11/12</ENT>
                <ENT>ILS OR LOC RWY 4R, Amdt 6L</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>MN</ENT>
                <ENT>Cloquet</ENT>
                <ENT>Cloquet Carlton</ENT>
                <ENT>2/6430</ENT>
                <ENT>4/20/12</ENT>
                <ENT>NDB RWY 35, Amdt 4</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>WI</ENT>
                <ENT>Racine</ENT>
                <ENT>John H Batten</ENT>
                <ENT>2/8815</ENT>
                <ENT>4/11/12</ENT>
                <ENT>ILS OR LOC RWY 4, Amdt 4C</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TX</ENT>
                <ENT>Houston</ENT>
                <ENT>George Bush Intercontinental/Houston</ENT>
                <ENT>2/8871</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 26R, ILS RWY 26R (SA CAT I), ILS RWY 26R (CAT II), ILS RWY 26R (CAT III), Amdt 3</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TX</ENT>
                <ENT>Houston</ENT>
                <ENT>George Bush Intercontinental/Houston</ENT>
                <ENT>2/8872</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 26L, ILS RWY 26L (SA CAT I), ILS RWY 26L (CAT II), ILS RWY 26L (CAT III), Amdt 20</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>TX</ENT>
                <ENT>Houston</ENT>
                <ENT>George Bush Intercontinental/Houston</ENT>
                <ENT>2/8874</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 27, ILS RWY 27 (SA CAT I), ILS RWY 27 (CAT II), ILS RWY 27 (CAT III), Amdt 9</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>CA</ENT>
                <ENT>Lakeport</ENT>
                <ENT>Lampson Field</ENT>
                <ENT>2/9212</ENT>
                <ENT>4/20/12</ENT>
                <ENT>RNAV (GPS) A, Orig</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>OH</ENT>
                <ENT>Toledo</ENT>
                <ENT>Toledo Express</ENT>
                <ENT>2/9345</ENT>
                <ENT>4/20/12</ENT>
                <ENT>ILS OR LOC RWY 25, Amdt 7A</ENT>
              </ROW>
              <ROW>
                <ENT I="01">31-May-12</ENT>
                <ENT>OH</ENT>
                <ENT>Toledo</ENT>
                <ENT>Toledo Express</ENT>
                <ENT>2/9347</ENT>
                <ENT>4/20/12</ENT>
                <ENT>RNAV (GPS) RWY 25, Amdt 2</ENT>
              </ROW>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10720 Filed 5-4-12; 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 97</CFR>
        <DEPDOC>[Docket No. 30839; Amdt. No. 3476 ]</DEPDOC>
        <SUBJECT>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments</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 rule establishes, amends, suspends, or revokes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective May 7, 2012. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.</P>
          <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of May 7, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Availability of matters incorporated by reference in the amendment is as follows:</P>
          <P>
            <E T="03">For Examination</E>—</P>
          <P>1. FAA Rules Docket, FAA Headquarters Building, 800 Independence Avenue SW., Washington, DC 20591;</P>
          <P>2. The FAA Regional Office of the region in which the affected airport is located;</P>
          <P>3. The National Flight Procedures Office, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or,</P>

          <P>4. 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>
          <P>
            <E T="03">Availability</E>—All SIAPs and Takeoff Minimums and ODPs are available online free of charge. Visit<E T="03">http://www.nfdc.faa.gov</E>to register. Additionally, individual SIAP and Takeoff Minimums and ODP copies may be obtained from:</P>
          <P>1. FAA Public Inquiry Center (APA-200), FAA Headquarters Building, 800 Independence Avenue SW., Washington, DC 20591; or</P>
          <P>2. The FAA Regional Office of the region in which the affected airport is located.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Richard A. Dunham III, Flight Procedure Standards Branch (AFS-420), Flight Technologies and Programs Divisions, Flight Standards Service, Federal Aviation Administration, Mike Monroney Aeronautical Center, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 (Mail Address: P.O. Box 25082, Oklahoma City, OK 73125) Telephone: (405) 954-4164.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>This rule amends Title 14 of the Code of Federal Regulations, Part 97 (14 CFR part 97), by establishing, amending, suspending, or revoking SIAPS, Takeoff Minimums and/or ODPS. The complete regulators description of each SIAP and its associated Takeoff Minimums or ODP for an identified airport is listed on FAA form documents which are incorporated by reference in this amendment under 5<PRTPAGE P="26670"/>U.S.C. 552(a), 1 CFR part 51, and 14 CFR part 97.20. The applicable FAA Forms are FAA Forms 8260-3, 8260-4, 8260-5, 8260-15A, and 8260-15B when required by an entry on 8260-15A.</P>

        <P>The large number of SIAPs, Takeoff Minimums and ODPs, in addition to their complex nature and the need for a special format make publication in the<E T="04">Federal Register</E>expensive and impractical. Furthermore, airmen do not use the regulatory text of the SIAPs, Takeoff Minimums or ODPs, but instead refer to their depiction on charts printed by publishers of aeronautical materials. The advantages of incorporation by reference are realized and publication of the complete description of each SIAP, Takeoff Minimums and ODP listed on FAA forms is unnecessary. This amendment provides the affected CFR sections and specifies the types of SIAPs and the effective dates of the, associated Takeoff Minimums and ODPs. This amendment also identifies the airport and its location, the procedure, and the amendment number.</P>
        <HD SOURCE="HD1">The Rule</HD>
        <P>This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP, Takeoff Minimums and ODP as contained in the transmittal. Some SIAP and Takeoff Minimums and textual ODP amendments may have been issued previously by the FAA in a Flight Data Center (FDC) Notice to Airmen (NOTAM) as an emergency action of immediate flight safety relating directly to published aeronautical charts. The circumstances which created the need for some SIAP and Takeoff Minimums and ODP amendments may require making them effective in less than 30 days. For the remaining SIAPS and Takeoff Minimums and ODPS, an effective date at least 30 days after publication is provided.</P>
        <P>Further, the SIAPs and Takeoff Minimums and ODPS contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these SIAPS and Takeoff Minimums and ODPs, the TERPS criteria were applied to the conditions existing or anticipated at the affected airports. Because of the close and immediate relationship between these SIAPs, Takeoff Minimums and ODPs, andsafety in air commerce, I find that notice and public procedures before adopting these SIAPS, Takeoff Minimums and ODPs are impracticable and contrary to the public interest and, where applicable, that good cause exists for making some SIAPs effective in less than 30 days.</P>
        <HD SOURCE="HD1">Conclusion</HD>
        <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. It, therefore—(1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under 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. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 97</HD>
          <P>Air Traffic Control, Airports, Incorporation by reference, and Navigation (Air).</P>
        </LSTSUB>
        <SIG>
          <DATED>Issued in Washington, DC, on April 27, 2012.</DATED>
          <NAME>Ray Towles,</NAME>
          <TITLE>Deputy Director, Flight Standards Service.</TITLE>
        </SIG>
        <HD SOURCE="HD1">Adoption of the Amendment</HD>
        <P>Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal Regulations, Part 97 (14 CFR part 97) is amended by establishing, amending, suspending, or revoking Standard Instrument Approach Procedures and/or Takeoff Minimums and/or Obstacle Departure Procedures effective at 0902 UTC on the dates specified, as follows:</P>
        <REGTEXT PART="97" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 97—STANDARD INSTRUMENT APPROACH PROCEDURES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 97 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="97" TITLE="14">
          <AMDPAR>2. Part 97 is amended to read as follows:</AMDPAR>
          <EXTRACT>
            <HD SOURCE="HD2">* * * Effective 31 MAY 2012</HD>
            <FP SOURCE="FP-1">Anchorage, AK, Ted Stevens Anchorage Intl, ILS RWY 15, Amdt 6</FP>
            <FP SOURCE="FP-1">Anchorage, AK, Ted Stevens Anchorage Intl, ILS OR LOC/DME RWY 7L, ILS RWY 7L (SA CAT I), ILS RWY 7L (SA CAT II), Amdt 3</FP>
            <FP SOURCE="FP-1">Anchorage, AK, Ted Stevens Anchorage Intl, ILS OR LOC/DME RWY 7R, ILS RWY 7R (CAT II), ILS RWY 7R (CAT III), ILS RWY 7R (SA CAT I), Amdt 3</FP>
            <FP SOURCE="FP-1">Oneonta, AL, Robbins Field, RNAV (GPS) RWY 5, Orig</FP>
            <FP SOURCE="FP-1">Oneonta, AL, Robbins Field, RNAV (GPS) RWY 23, Orig</FP>
            <FP SOURCE="FP-1">Oneonta, AL, Robbins Field, Takeoff Minimums and Obstacle DP, Orig</FP>
            <FP SOURCE="FP-1">Prattville, AL, Prattville-Grouby Field, RNAV (GPS) RWY 9, Amdt 2</FP>
            <FP SOURCE="FP-1">Prattville, AL, Prattville-Grouby Field, RNAV (GPS) RWY 27, Orig</FP>
            <FP SOURCE="FP-1">Camden, AR, Harrell Field, RNAV (GPS) RWY 1, Amdt 1</FP>
            <FP SOURCE="FP-1">Camden, AR, Harrell Field, RNAV (GPS) RWY 19, Amdt 1</FP>
            <FP SOURCE="FP-1">Camden, AR, Harrell Field, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
            <FP SOURCE="FP-1">Phoenix, AZ, Phoenix-Mesa Gateway, RNAV (GPS) Y RWY 30C, Amdt 1</FP>
            <FP SOURCE="FP-1">Phoenix, AZ, Phoenix-Mesa Gateway, RNAV (RNP) Z RWY 30C, Orig</FP>
            <FP SOURCE="FP-1">Oxford, CT, Waterbury-Oxford, RNAV (GPS) RWY 36, Amdt 2</FP>
            <FP SOURCE="FP-1">Windsor Locks, CT, Bradley Intl, RNAV (GPS) Y RWY 24, Amdt 3A</FP>
            <FP SOURCE="FP-1">Windsor Locks, CT, Bradley Intl, RNAV (RNP) Z RWY 24, Orig-A</FP>
            <FP SOURCE="FP-1">Washington, DC, Washington Dulles Intl, VOR/DME RWY 12, Amdt 9</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, NDB RWY 14, AMDT 2</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, NDB RWY 32, AMDT 2</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, RNAV (GPS) RWY 6, Amdt 1</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, RNAV (GPS) RWY 14, Amdt 2</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, RNAV (GPS) RWY 18, Orig</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, RNAV (GPS) RWY 24, Amdt 1</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, RNAV (GPS) RWY 32, Amdt 2</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, RNAV (GPS) RWY 36, Orig</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, RNAV (GPS)-A, Orig-A, CANCELLED</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, RNAV (GPS)-B, Orig-A, CANCELLED</FP>
            <FP SOURCE="FP-1">Apalachicola, FL, Apalachicola Regional, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
            <FP SOURCE="FP-1">Fort Pierce, FL, St Lucie County Intl, Takeoff Minimums and Obstacle DP, Amdt 4</FP>
            <FP SOURCE="FP-1">Miami, FL, Miami Intl, ILS OR LOC RWY 8R, Amdt 30B</FP>
            <FP SOURCE="FP-1">Panama City, FL, Northwest Florida Beaches Intl, ILS OR LOC/DME RWY 16, Amdt 1</FP>
            <FP SOURCE="FP-1">Panama City, FL, Northwest Florida Beaches Intl, RNAV (GPS) RWY 16, Amdt 1</FP>
            <FP SOURCE="FP-1">Panama City, FL, Northwest Florida Beaches Intl, RNAV (GPS) RWY 34, Amdt 1</FP>
            <FP SOURCE="FP-1">Tampa, FL, Peter O Knight, NDB RWY 4, Amdt 12A</FP>
            <FP SOURCE="FP-1">Tampa, FL, Peter O Knight, RNAV (GPS) RWY 22, Amdt 2</FP>
            <FP SOURCE="FP-1">Tampa, FL, Peter O Knight, RNAV (GPS) RWY 36, Amdt 2A</FP>
            <FP SOURCE="FP-1">Tampa, FL, Peter O Knight, Takeoff Minimums and Obstacle DP, Amdt 7</FP>
            <FP SOURCE="FP-1">Independence, IA, Independence Muni, RNAV (GPS) RWY 36, Orig-A</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, ILS OR LOC RWY 9L, ILS RWY 9L (CAT II), ILS RWY 9L (CAT III), Amdt 1</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, ILS OR LOC RWY 22L, Amdt 5</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, ILS OR LOC RWY 22R, Amdt 9</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, ILS OR LOC RWY 27R, ILS RWY 27R (CAT II), ILS RWY 27R (CAT III), Amdt 1</FP>

            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, LOC RWY 4L, Amdt 22<PRTPAGE P="26671"/>
            </FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 4L, Amdt 2</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 4R, Amdt 1</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 9L, Amdt 1</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 10, Amdt 3C</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 14L, Amdt 1E</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 14R, Amdt 2B</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 22L, Amdt 1</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 22R, Amdt 2</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 27R, Amdt 1</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) RWY 28, Amdt 2D</FP>
            <FP SOURCE="FP-1">Chicago, IL, Chicago O'Hare Intl, RNAV (GPS) Y RWY 22L, Orig-C, CANCELLED</FP>
            <FP SOURCE="FP-1">Wichita, KS, Wichita Mid-Continent, RNAV (GPS) RWY 1R, Amdt 1</FP>
            <FP SOURCE="FP-1">Greenville, KY, Muhlenberg County, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
            <FP SOURCE="FP-1">Natchitoches, LA, Natchitoches Rgnl, LOC RWY 35, Amdt 4</FP>
            <FP SOURCE="FP-1">Natchitoches, LA, Natchitoches Rgnl, NDB RWY 35, Amdt 6</FP>
            <FP SOURCE="FP-1">Natchitoches, LA, Natchitoches Rgnl, RNAV (GPS) RWY 17, Amdt 1</FP>
            <FP SOURCE="FP-1">Natchitoches, LA, Natchitoches Rgnl, RNAV (GPS) RWY 35, Amdt 1</FP>
            <FP SOURCE="FP-1">Hopedale, MA, Hopedale Industrial Park, GPS-A, Orig-A, CANCELLED</FP>
            <FP SOURCE="FP-1">Hopedale, MA, Hopedale Industrial Park, RNAV (GPS)-A, Orig</FP>
            <FP SOURCE="FP-1">Orange, MA, Orange Muni, GPS RWY 32, Orig-E, CANCELLED</FP>
            <FP SOURCE="FP-1">Orange, MA, Orange Muni, NDB RWY 1, Amdt 1</FP>
            <FP SOURCE="FP-1">Orange, MA, Orange Muni, NDB RWY 32, Amdt 1</FP>
            <FP SOURCE="FP-1">Orange, MA, Orange Muni, RNAV (GPS) RWY 32, Orig</FP>
            <FP SOURCE="FP-1">Orange, MA, Orange Muni, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
            <FP SOURCE="FP-1">Gaithersburg, MD, Montgomery County Airpark, RNAV (GPS)-A, Orig</FP>
            <FP SOURCE="FP-1">Ridgely, MD, Ridgely Airpark, RNAV (GPS) RWY 12, Orig-A</FP>
            <FP SOURCE="FP-1">Ridgely, MD, Ridgely Airpark, RNAV (GPS) RWY 30, Orig-A</FP>
            <FP SOURCE="FP-1">Boyne City, MI, Boyne City Muni, RNAV (GPS) RWY 9, Orig</FP>
            <FP SOURCE="FP-1">Boyne City, MI, Boyne City Muni, RNAV (GPS) RWY 27, Orig</FP>
            <FP SOURCE="FP-1">Boyne City, MI, Boyne City Muni, Takeoff Minimums and Obstacle DP, Orig</FP>
            <FP SOURCE="FP-1">Ontonagon, MI, Ontonagon County-Schuster Field, NDB OR GPS-A, Amdt 4A, CANCELLED</FP>
            <FP SOURCE="FP-1">Ontonagon, MI, Ontonagon County-Schuster Field, RNAV (GPS)-A, Orig</FP>
            <FP SOURCE="FP-1">Ontonagon, MI, Ontonagon County-Schuster Field, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
            <FP SOURCE="FP-1">Owatonna, MN, Owatonna Degner Rgnl, ILS OR LOC RWY 30, Amdt 2A</FP>
            <FP SOURCE="FP-1">Owatonna, MN, Owatonna Degner Rgnl, RNAV (GPS) RWY 12, Amdt 1</FP>
            <FP SOURCE="FP-1">Owatonna, MN, Owatonna Degner Rgnl, RNAV (GPS) RWY 30, Orig</FP>
            <FP SOURCE="FP-1">Jacksonville, NC, Albert J Ellis, ILS OR LOC RWY 5, Amdt 9</FP>
            <FP SOURCE="FP-1">Jacksonville, NC, Albert J Ellis, RNAV (GPS) RWY 5, Amdt 1</FP>
            <FP SOURCE="FP-1">Jacksonville, NC, Albert J Ellis, RNAV (GPS) RWY 23, Orig</FP>
            <FP SOURCE="FP-1">Pittstown, NJ, Sky Manor, RNAV (GPS) RWY 7, Orig</FP>
            <FP SOURCE="FP-1">Pittstown, NJ, Sky Manor, RNAV (GPS) RWY 25, Orig</FP>
            <FP SOURCE="FP-1">Pittstown, NJ, Sky Manor, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
            <FP SOURCE="FP-1">Pittstown, NJ, Sky Manor, VOR RWY 7, Amdt 3</FP>
            <FP SOURCE="FP-1">Robbinsville, NJ, Trenton-Robbinsville, GPS RWY 11, Orig, CANCELLED</FP>
            <FP SOURCE="FP-1">Robbinsville, NJ, Trenton-Robbinsville, RNAV (GPS) RWY 11, Orig</FP>
            <FP SOURCE="FP-1">Robbinsville, NJ, Trenton-Robbinsville, RNAV (GPS) RWY 29, Amdt 1</FP>
            <FP SOURCE="FP-1">Robbinsville, NJ, Trenton-Robbinsville, VOR RWY 29, Amdt 11</FP>
            <FP SOURCE="FP-1">Somerville, NJ, Somerset, RNAV (GPS) RWY 30, Amdt 1</FP>
            <FP SOURCE="FP-1">Somerville, NJ, Somerset, VOR RWY 8, Amdt 12</FP>
            <FP SOURCE="FP-1">Cortland, NY, Cortland County-Chase Field, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
            <FP SOURCE="FP-1">Hornell, NY, Hornell Muni, GPS RWY 18, Orig-B, CANCELLED</FP>
            <FP SOURCE="FP-1">Hornell, NY, Hornell Muni, GPS RWY 36, Orig-B, CANCELLED</FP>
            <FP SOURCE="FP-1">Hornell, NY, Hornell Muni, RNAV (GPS) RWY 18, Orig</FP>
            <FP SOURCE="FP-1">Hornell, NY, Hornell Muni, RNAV (GPS) RWY 36, Orig</FP>
            <FP SOURCE="FP-1">Hornell, NY, Hornell Muni, Takeoff Minimums and Obstacle DP, Amdt 5</FP>
            <FP SOURCE="FP-1">New York, NY, La Guardia, RNAV (GPS) RWY 13, Amdt 1</FP>
            <FP SOURCE="FP-1">Ogdensburg, NY, Ogdensburg Intl, RNAV (GPS) RWY 9, Orig</FP>
            <FP SOURCE="FP-1">Westhampton Beach, NY, Francis S Gabreski, COPTER ILS OR LOC RWY 24, Amdt 2A, CANCELLED</FP>
            <FP SOURCE="FP-1">Westhampton Beach, NY, Francis S Gabreski, ILS OR LOC RWY 24, Amdt 10</FP>
            <FP SOURCE="FP-1">Westhampton Beach, NY, Francis S Gabreski, RNAV (GPS) RWY 6, Amdt 2</FP>
            <FP SOURCE="FP-1">Westhampton Beach, NY, Francis S Gabreski, RNAV (GPS) RWY 24, Amdt 2</FP>
            <FP SOURCE="FP-1">Westhampton Beach, NY, Francis S Gabreski, TACAN RYW 6, Orig</FP>
            <FP SOURCE="FP-1">Westhampton Beach, NY, Francis S Gabreski, TACAN RWY 24, Orig</FP>
            <FP SOURCE="FP-1">Westhampton Beach, NY, Francis S Gabreski, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
            <FP SOURCE="FP-1">Portsmouth, OH, Greater Portsmouth Rgnl, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
            <FP SOURCE="FP-1">Tiffin, OH, Seneca County, RNAV (GPS) RWY 24, Amdt 1</FP>
            <FP SOURCE="FP-1">Madras, OR, Madras Municipal, RNAV (GPS) RWY 16, Amdt 1</FP>
            <FP SOURCE="FP-1">Madras, OR, Madras Municipal, RNAV (GPS) RWY 34, Orig</FP>
            <FP SOURCE="FP-1">Madras, OR, Madras Municipal, RNAV (GPS)-A, Amdt 1, CANCELLED</FP>
            <FP SOURCE="FP-1">Danville, PA, Danville, RNAV (GPS) RWY 9, Orig</FP>
            <FP SOURCE="FP-1">Danville, PA, Danville, RNAV (GPS) RWY 27, Orig</FP>
            <FP SOURCE="FP-1">Danville, PA, Danville, Takeoff Minimums and Obstacle DP, Orig</FP>
            <FP SOURCE="FP-1">Lebanon, PA, Keller Brothers, RNAV (GPS) RWY 7, Orig</FP>
            <FP SOURCE="FP-1">Lebanon, PA, Keller Brothers, RNAV (GPS) RWY 25, Orig</FP>
            <FP SOURCE="FP-1">Lebanon, PA, Keller Brothers, Takeoff Minimums and Obstacle DP, Orig</FP>
            <FP SOURCE="FP-1">Philadelphia, PA, Philadelphia Intl, Takeoff Minimums and Obstacle DP, Amdt 9</FP>
            <FP SOURCE="FP-1">Quakertown, PA, Quakertown, NDB RWY 29, Amdt 11</FP>
            <FP SOURCE="FP-1">Quakertown, PA, Quakertown, RNAV (GPS) RWY 11, Orig</FP>
            <FP SOURCE="FP-1">Quakertown, PA, Quakertown, RNAV (GPS) RWY 29, Amdt 1</FP>
            <FP SOURCE="FP-1">Austin, TX, Austin-Bergstrom Intl, ILS OR LOC RWY 17L, ILS RWY 17L (SA CAT I), ILS RWY 17L (CAT II), ILS RWY 17L (CAT III), Amdt 2</FP>
            <FP SOURCE="FP-1">Austin, TX, Austin-Bergstrom Intl, ILS OR LOC RWY 17R, Amdt 4</FP>
            <FP SOURCE="FP-1">Austin, TX, Austin-Bergstrom Intl, ILS OR LOC RWY 35L, Amdt 5</FP>
            <FP SOURCE="FP-1">Austin, TX, Austin-Bergstrom Intl, ILS OR LOC RWY 35R, Amdt 2</FP>
            <FP SOURCE="FP-1">Austin, TX, Austin-Bergstrom Intl, RNAV (GPS) RWY 17L, Amdt 1</FP>
            <FP SOURCE="FP-1">Austin, TX, Austin-Bergstrom Intl, RNAV (GPS) RWY 17R, Amdt 1</FP>
            <FP SOURCE="FP-1">Austin, TX, Austin-Bergstrom Intl, RNAV (GPS) RWY 35L, Amdt 1</FP>
            <FP SOURCE="FP-1">Austin, TX, Austin-Bergstrom Intl, RNAV (GPS) RWY 35R, Amdt 1</FP>
            <FP SOURCE="FP-1">Austin, TX, Austin-Bergstrom Intl, RNAV (GPS) Y RWY 35L, Orig, CANCELLED</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, GLS RWY 8L, Orig</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, GLS RWY 8R, Orig</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, GLS RWY 9, Orig</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, GLS RWY 26L, Orig</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, GLS RWY 26R, Orig</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, GLS RWY 27, Orig</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, ILS OR LOC RWY 8L, ILS RWY 8L (CAT II), ILS RWY 8L (CAT III), ILS RWY 8L (SA CAT I), Amdt 3</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, ILS OR LOC RWY 8R, ILS RWY 8R (SA CAT II), Amdt 24</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, ILS OR LOC RWY 9, ILS RWY 9 (SA Cat II), Amdt 9</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, RNAV (GPS) RWY 8L, Amdt 4</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, RNAV (GPS) RWY 9, Amdt 4</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, RNAV (GPS) RWY 26L, Amdt 3A</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, RNAV (GPS) RWY 26R, Amdt 3A</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, RNAV (GPS) Z RWY 8R, Amdt 3</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, RNAV (RNP) Y RWY 8R, Orig</FP>
            <FP SOURCE="FP-1">Houston, TX, George Bush Intercontinental/Houston, RNAV (RNP) Y RWY 27, Orig</FP>
            <FP SOURCE="FP-1">Madisonville, TX, Madisonville Muni, Takeoff Minimums and Obstacle DP, Orig</FP>
            <FP SOURCE="FP-1">Monahans, TX, Roy Hurd Memorial, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
            <FP SOURCE="FP-1">Clarksville, VA, Lake Country Regional, GPS RWY 4, Orig-B, CANCELLED</FP>

            <FP SOURCE="FP-1">Clarksville, VA, Lake Country Regional, RNAV (GPS) RWY 4, Orig<PRTPAGE P="26672"/>
            </FP>
            <FP SOURCE="FP-1">Clarksville, VA, Lake Country Regional, RNAV (GPS) RWY 22, Orig</FP>
            <FP SOURCE="FP-1">Leesburg, VA, Leesburg Executive, ILS OR LOC RWY 17, Amdt 1</FP>
            <FP SOURCE="FP-1">Leesburg, VA, Leesburg Executive, RNAV (GPS) RWY 17, Amdt 3</FP>
            <FP SOURCE="FP-1">New Market, VA, New Market, Takeoff Minimums and Obstacle DP, Orig</FP>
            <FP SOURCE="FP-1">Norfolk, VA, Norfolk Intl, ILS OR LOC RWY 5, Amdt 26A</FP>
            <FP SOURCE="FP-1">Newport, VT, Newport State, GPS RWY 36, Orig-A, CANCELLED</FP>
            <FP SOURCE="FP-1">Newport, VT, Newport State, RNAV (GPS) RWY 36, Orig</FP>
            <FP SOURCE="FP-1">Guernsey, WY, Camp Guernsey, GPS RWY 32, Orig, CANCELLED</FP>
            <FP SOURCE="FP-1">Guernsey, WY, Camp Guernsey, NDB RWY 32, Amdt 1</FP>
            <FP SOURCE="FP-1">Guernsey, WY, Camp Guernsey, RNAV (GPS) RWY 32, Orig</FP>
            <FP SOURCE="FP-1">Torrington, WY, Torrington Muni, NDB RWY 10, Amdt 2</FP>
            <FP SOURCE="FP-1">Torrington, WY, Torrington Muni, NDB RWY 28, Amdt 2</FP>
            
            <P>RESCINDED: On March 28, 2012 (77 FR 18683), the FAA published an Amendment in Docket No. 30833, Amdt No. 3470 to Part 97 of the Federal Aviation Regulations under section 97.33. The following 46 entries for Denver, CO, and 1 entry for Camden, AR, effective 31 May, 2012, are hereby rescinded in their entirety:</P>
            
            <FP SOURCE="FP-1">Camden, AR, Harrell Field, VOR/DME RWY 1, Amdt 10</FP>
            <FP SOURCE="FP-1">Denver, CO, Centennial, Takeoff Minimums and Obstacle DP, Amdt 5</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 7, Amdt 3</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 8, Amdt 5</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 16L, Amdt 3</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 16R, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 17L, Amdt 4</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 17R, Amdt 3</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 25, Amdt 3</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 26, Amdt 3</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 34L, ILS RWY 34L (CAT II), ILS RWY 34L (CAT III), ILS RWY 34L (SA CAT I), Amdt 2</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 34R, ILS RWY 34R (CAT II), ILS RWY 34R (CAT III), ILS RWY 34R (SA CAT I), Amdt 3</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 35L, ILS RWY 35L (CAT II), ILS RWY 35L (CAT III), ILS RWY 35L (SA CAT I), Amdt 5</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, ILS OR LOC RWY 35R, ILS RWY 35R (CAT II), ILS RWY 35R (CAT III), ILS RWY 35R (SA CAT I), Amdt 3</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 7, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 8, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 16L, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 16R, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 17L, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 17R, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 25, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 26, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 34L, Amdt 2</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 34R, Amdt 2</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 35L, Amdt 2</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (GPS) Y RWY 35R, Amdt 2</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 7, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 8, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 16L, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 16R, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 17L, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 17R, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 25, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 26, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 34L, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 34R, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 35L, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Denver Intl, RNAV (RNP) Z RWY 35R, Orig</FP>
            <FP SOURCE="FP-1">Denver, CO, Front Range, ILS OR LOC RWY 17, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Front Range, ILS OR LOC RWY 26, Amdt 5</FP>
            <FP SOURCE="FP-1">Denver, CO, Front Range, ILS OR LOC RWY 35, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Front Range, NDB RWY 26, Amdt 5</FP>
            <FP SOURCE="FP-1">Denver, CO, Front Range, RNAV (GPS) RWY 17, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Front Range, RNAV (GPS) RWY 26, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Front Range, RNAV (GPS) RWY 35, Amdt 1</FP>
            <FP SOURCE="FP-1">Denver, CO, Front Range, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
            <FP SOURCE="FP-1">Denver, CO, Rocky Mountain Metropolitan, Takeoff Minimums and Obstacle DP, Amdt 5</FP>
            
          </EXTRACT>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10727 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">COMMODITY FUTURES TRADING COMMISSION</AGENCY>
        <CFR>17 CFR Part 1</CFR>
        <SUBJECT>Fees for Reviews of the Rule Enforcement Programs of Designated Contract Markets and Registered Futures Associations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Commodity Futures Trading Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of FY 2011 schedule of fees.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Commission charges fees to designated contract markets and registered futures associations to recover the costs incurred by the Commission in the operation of its program of oversight of self-regulatory organization rule enforcement programs, specifically National Futures Association, a registered futures association, and the designated contract markets. The calculation of the fee amounts charged for FY 2011 by this notice is based upon an average of actual program costs incurred during FY 2008, 2009, and 2010.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>Each SRO is required to remit electronically the fee applicable to it on or before July 6, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mark Carney, Chief Financial Officer, Commodity Futures Trading Commission, (202) 418-5477, Three Lafayette Centre, 1155 21st Street NW., Washington, DC 20581. For information on electronic payment, contact Jennifer Fleming, Three Lafayette Centre, 1155 21st Street NW., Washington, DC 20581, (202) 418-5034.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background Information</HD>
        <HD SOURCE="HD2">A.<E T="03">General</E>
        </HD>
        <P>This notice relates to fees for the Commission's review of the rule enforcement programs at the registered futures associations<SU>1</SU>
          <FTREF/>and designated contract markets (DCM) each of which is a self-regulatory organization (SRO) regulated by the Commission. The Commission recalculates the fees charged each year to cover the costs of operating this Commission program.<SU>2</SU>
          <FTREF/>All costs are accounted for by the Commission's Budget Program Activity Codes (BPAC) system, formerly the Management Accounting Structure Codes (MASC) system, which records each employee's time for each pay period. The fees are set each year based on direct program costs, plus an overhead factor. The Commission calculates actual costs, then calculates an alternate fee taking volume into account, then charges the lower of the two.<SU>3</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>1</SU>NFA is the only registered futures association.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">See</E>section 237 of the Futures Trading Act of 1982, 7 U.S.C. 16a, and 31 U.S.C. 9701. For a broader discussion of the history of Commission fees, see 52 FR 46070, Dec. 4, 1987.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>58 FR 42643, Aug. 11, 1993 and 17 CFR part 1, app. B.</P>
        </FTNT>
        <PRTPAGE P="26673"/>
        <HD SOURCE="HD2">B.<E T="03">Overhead Rate</E>
        </HD>
        <P>The fees charged by the Commission to the SROs are designed to recover program costs, including direct labor costs and overhead. The overhead rate is calculated by dividing total Commission-wide overhead direct program labor costs into the total amount of the Commission-wide overhead pool. For this purpose, direct program labor costs are the salary costs of personnel working in all Commission programs. Overhead costs consist generally of the following Commission-wide costs: indirect personnel costs (leave and benefits), rent, communications, contract services, utilities, equipment, and supplies. This formula has resulted in the following overhead rates for the most recent three years (rounded to the nearest whole percent): 144 percent for fiscal year 2008, 147 percent for fiscal year 2009, and 153 percent for fiscal year 2010.</P>
        <HD SOURCE="HD2">C.<E T="03">Conduct of SRO Rule Enforcement Reviews</E>
        </HD>
        <P>Under the formula adopted by the Commission in 1993, the Commission calculates the fee to recover the costs of its rule enforcement reviews and examinations, based on the three-year average of the actual cost of performing such reviews and examinations at each SRO. The cost of operation of the Commission's SRO oversight program varies from SRO to SRO, according to the size and complexity of each SRO's program. The three-year averaging computation method is intended to smooth out year-to-year variations in cost. Timing of the Commission's reviews and examinations may affect costs—a review or examination may span two fiscal years and reviews and examinations are not conducted at each SRO each year.</P>
        <P>As noted above, adjustments to actual costs may be made to relieve the burden on an SRO with a disproportionately large share of program costs. The Commission's formula provides for a reduction in the assessed fee if an SRO has a smaller percentage of United States industry contract volume than its percentage of overall Commission oversight program costs. This adjustment reduces the costs so that, as a percentage of total Commission SRO oversight program costs, they are in line with the pro rata percentage for that SRO of United States industry-wide contract volume.</P>
        <P>The calculation is made as follows: The fee required to be paid to the Commission by each DCM is equal to the lesser of actual costs based on the three-year historical average of costs for that DCM or one-half of average costs incurred by the Commission for each DCM for the most recent three years, plus a pro rata share (based on average trading volume for the most recent three years) of the aggregate of average annual costs of all DCMs for the most recent three years. The formula for calculating the second factor is: 0.5a + 0.5 vt = current fee. In this formula, “a” equals the average annual costs, “v” equals the percentage of total volume across DCMs over the last three years, and “t” equals the average annual costs for all DCMs. NFA has no contracts traded; hence, its fee is based simply on costs for the most recent three fiscal years. This table summarizes the data used in the calculations of the resulting fee for each entity:</P>
        <GPOTABLE CDEF="s50,10,10,10,10,10,10,10" COLS="8" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1">Actual total costs</CHED>
            <CHED H="2">FY2008</CHED>
            <CHED H="2">FY2009</CHED>
            <CHED H="2">FY2010</CHED>
            <CHED H="1">3-Year<LI>average</LI>
              <LI>actual costs</LI>
            </CHED>
            <CHED H="1">3-Year % of volume</CHED>
            <CHED H="1">Volume<LI>adjusted</LI>
              <LI>costs</LI>
            </CHED>
            <CHED H="1">FY2011<LI>Assessed</LI>
              <LI>fee</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">CBOE Futures</ENT>
            <ENT/>
            <ENT>$519</ENT>
            <ENT/>
            <ENT>$173</ENT>
            <ENT>0.057</ENT>
            <ENT>$448</ENT>
            <ENT>$173</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Chicago Board of Trade</ENT>
            <ENT>$30,305</ENT>
            <ENT>142,446</ENT>
            <ENT>$87,953</ENT>
            <ENT>86,901</ENT>
            <ENT>27,706</ENT>
            <ENT>218,442</ENT>
            <ENT>86,901</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Chicago Climate Exchange</ENT>
            <ENT>23,590</ENT>
            <ENT>2,129</ENT>
            <ENT/>
            <ENT>8,573</ENT>
            <ENT>0.025</ENT>
            <ENT>4,444</ENT>
            <ENT>4,444</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Chicago Mercantile Exchange</ENT>
            <ENT>13,511</ENT>
            <ENT>341,186</ENT>
            <ENT>882,542</ENT>
            <ENT>412,413</ENT>
            <ENT>54.224</ENT>
            <ENT>548,690</ENT>
            <ENT>412,413</ENT>
          </ROW>
          <ROW>
            <ENT I="01">ICE Future U.S.</ENT>
            <ENT>126,362</ENT>
            <ENT>286,289</ENT>
            <ENT>94,043</ENT>
            <ENT>168,898</ENT>
            <ENT>2.883</ENT>
            <ENT>102,659</ENT>
            <ENT>102,659</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Kansas City Board of Trade</ENT>
            <ENT>78,321</ENT>
            <ENT>2,888</ENT>
            <ENT>227,296</ENT>
            <ENT>102,835</ENT>
            <ENT>0.139</ENT>
            <ENT>52,294</ENT>
            <ENT>52,294</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Minneapolis Grain Exchange</ENT>
            <ENT>187,679</ENT>
            <ENT>123,566</ENT>
            <ENT/>
            <ENT>103,748</ENT>
            <ENT>0.047</ENT>
            <ENT>52,172</ENT>
            <ENT>52,172</ENT>
          </ROW>
          <ROW>
            <ENT I="01">New York Mercantile Exchange</ENT>
            <ENT>497,654</ENT>
            <ENT>15,948</ENT>
            <ENT>596,767</ENT>
            <ENT>370,123</ENT>
            <ENT>14.214</ENT>
            <ENT>274,838</ENT>
            <ENT>274,838</ENT>
          </ROW>
          <ROW>
            <ENT I="01">North American Derivative Exchanges</ENT>
            <ENT>25,175</ENT>
            <ENT/>
            <ENT/>
            <ENT>8,392</ENT>
            <ENT>0.000</ENT>
            <ENT>4,196</ENT>
            <ENT>4,196</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">One Chicago</ENT>
            <ENT>3,471</ENT>
            <ENT/>
            <ENT/>
            <ENT>1,157</ENT>
            <ENT>0.134</ENT>
            <ENT>1,425</ENT>
            <ENT>1,157</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="03">Subtotal</ENT>
            <ENT>986,069</ENT>
            <ENT>914,972</ENT>
            <ENT>1,888,601</ENT>
            <ENT>1,263,214</ENT>
            <ENT>100</ENT>
            <ENT>1,259,607</ENT>
            <ENT>991,247</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">National Futures Association</ENT>
            <ENT>1,054,392</ENT>
            <ENT>109,639</ENT>
            <ENT>1,206,393</ENT>
            <ENT>790,141</ENT>
            <ENT/>
            <ENT/>
            <ENT>790,141</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Total</ENT>
            <ENT>2,040,460</ENT>
            <ENT>1,024,611</ENT>
            <ENT>3,094,994</ENT>
            <ENT>2,053,355</ENT>
            <ENT/>
            <ENT/>
            <ENT>1,781,388</ENT>
          </ROW>
        </GPOTABLE>
        <P>An example of how the fee is calculated for one exchange, the Chicago Board of Trade, is set forth here:</P>
        <EXTRACT>
          
          <P>a. Actual three-year average costs equal $86,901.</P>
          <P>b. The alternative computation is: (.5) ($86,901) + (.5) (.2771) ($1,263,214) = $218,442.</P>
          <P>c. The fee is the lesser of a or b; in this case $86,901.</P>
        </EXTRACT>
        
        <P>As noted above, the alternative calculation based on contracts traded is not applicable to NFA because it is not a DCM and has no contracts traded. The Commission's average annual cost for conducting oversight review of the NFA rule enforcement program during fiscal years 2008 through 2010 was $790,141 (one-third of $2,370,423). The fee to be paid by the NFA for the current fiscal year is $790,141.</P>
        <HD SOURCE="HD1">II. Schedule of Fees</HD>
        <P>Therefore, fees for the Commission's review of the rule enforcement programs at the registered futures associations and DCMs regulated by the Commission are as follows:</P>
        
        <PRTPAGE P="26674"/>
        <GPOTABLE CDEF="s50,10" COLS="2" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1">2011 Fee<LI>lesser of actual or calculated fee</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">CBOE Futures</ENT>
            <ENT>$173</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Chicago Board of Trade</ENT>
            <ENT>86,901</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Chicago Climate Exchange</ENT>
            <ENT>4,444</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Chicago Mercantile Exchange</ENT>
            <ENT>412,413</ENT>
          </ROW>
          <ROW>
            <ENT I="01">ICE Futures U.S.</ENT>
            <ENT>102,659</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Kansas City Board of Trade</ENT>
            <ENT>52,294</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Minneapolis Grain Exchange</ENT>
            <ENT>52,172</ENT>
          </ROW>
          <ROW>
            <ENT I="01">New York Mercantile Exchange</ENT>
            <ENT>274,838</ENT>
          </ROW>
          <ROW>
            <ENT I="01">North American Derivatives Exchange</ENT>
            <ENT>4,196</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">OneChicago</ENT>
            <ENT>1,157</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="03">Subtotal</ENT>
            <ENT>991,247</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">National Futures Association</ENT>
            <ENT>790,141</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Total</ENT>
            <ENT>1,781,388</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">III. Payment Method</HD>

        <P>The Debt Collection Improvement Act (DCIA) requires deposits of fees owed to the government by electronic transfer of funds (See 31 U.S.C. 3720). For information about electronic payments, please contact Jennifer Fleming at (202) 418-5034 or<E T="03">jfleming@cftc.gov</E>, or see the CFTC Web site at<E T="03">www.cftc.gov,</E>specifically,<E T="03">www.cftc.gov/cftc/cftcelectronicpayments.htm.</E>
        </P>
        <SIG>
          <DATED>Issued in Washington, DC, on this 1st day of May, 2012, by the Commission.</DATED>
          <NAME>David Stawick,</NAME>
          <TITLE>Secretary of the Commission.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10898 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <CFR>18 CFR Part 35</CFR>
        <DEPDOC>[Docket No. RM11-17-000; Order No. 760]</DEPDOC>
        <SUBJECT>Enhancement of Electricity Market Surveillance and Analysis Through Ongoing Electronic Delivery of Data From Regional Transmission Organizations and Independent System Operators</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Energy Regulatory Commission, DOE.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In this final rule, the Federal Energy Regulatory Commission (Commission) is amending its regulations to require each regional transmission organization (RTO) and independent system operator (ISO) to electronically deliver to the Commission, on an ongoing basis, data related to the markets that it administers. Specifically, the Commission is amending its regulations to establish ongoing electronic delivery of data relating to physical and virtual offers and bids, market awards, resource outputs, marginal cost estimates, shift factors, financial transmission rights, internal bilateral contracts, uplift, and interchange pricing. Such data will facilitate the Commission's development and evaluation of its policies and regulations and will enhance Commission efforts to detect anti-competitive or manipulative behavior, or ineffective market rules, thereby helping to ensure just and reasonable rates.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This rule will become effective July 6, 2012.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          

          <FP SOURCE="FP-1">William Sauer (Technical Information), Office of Enforcement, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-6639,<E T="03">william.sauer@ferc.gov.</E>
          </FP>

          <FP SOURCE="FP-1">Christopher Daignault (Legal Information), Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-8286,<E T="03">christopher.daignault@ferc.gov.</E>
          </FP>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Table of Contents</HD>
        <GPOTABLE CDEF="s200,9" COLS="2" OPTS="L0,tp0,g1,t1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1">Paragraph<LI>Nos.</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">I. Introduction</ENT>
            <ENT>1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">II. Background</ENT>
            <ENT>2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">III. Discussion</ENT>
            <ENT>8</ENT>
          </ROW>
          <ROW>
            <ENT I="03">A. Commission Authority and the Need for Market Data</ENT>
            <ENT>8</ENT>
          </ROW>
          <ROW>
            <ENT I="03">B. Duplicative Requirements</ENT>
            <ENT>20</ENT>
          </ROW>
          <ROW>
            <ENT I="03">C. Confidentiality of Data</ENT>
            <ENT>30</ENT>
          </ROW>
          <ROW>
            <ENT I="03">D. Data Formatting</ENT>
            <ENT>37</ENT>
          </ROW>
          <ROW>
            <ENT I="03">E. Web-Based Delivery</ENT>
            <ENT>45</ENT>
          </ROW>
          <ROW>
            <ENT I="03">F. Data Requested</ENT>
            <ENT>49</ENT>
          </ROW>
          <ROW>
            <ENT I="03">G. Implementation Timeline and Phasing</ENT>
            <ENT>64</ENT>
          </ROW>
          <ROW>
            <ENT I="03">H. Ongoing Electronic Delivery</ENT>
            <ENT>74</ENT>
          </ROW>
          <ROW>
            <ENT I="03">I. Future Specifications and Modifications of the Data and the Process for Delivery</ENT>
            <ENT>80</ENT>
          </ROW>
          <ROW>
            <ENT I="03">J. Technical Conference</ENT>
            <ENT>84</ENT>
          </ROW>
          <ROW>
            <ENT I="01">IV. Information Collection Statement</ENT>
            <ENT>86</ENT>
          </ROW>
          <ROW>
            <ENT I="01">V. Environmental Analysis</ENT>
            <ENT>96</ENT>
          </ROW>
          <ROW>
            <ENT I="01">VI. Regulatory Flexibility Act</ENT>
            <ENT>97</ENT>
          </ROW>
          <ROW>
            <ENT I="01">VII. Document Availability</ENT>
            <ENT>105</ENT>
          </ROW>
          <ROW>
            <ENT I="01">VIII. Effective Date and Congressional Notification</ENT>
            <ENT>108</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD3">139 FERC ¶ 61,053</HD>
        <FP SOURCE="FP-1">Before Commissioners: Jon Wellinghoff, Chairman; Philip D. Moeller, John R. Norris, and Cheryl A. LaFleur.</FP>
        <HD SOURCE="HD1">Final Rule</HD>
        <HD SOURCE="HD2">Issued April 19, 2012</HD>
        <HD SOURCE="HD1">I. Introduction</HD>
        <P>1. In this final rule, the Federal Energy Regulatory Commission (Commission) is revising its regulations to require each regional transmission organization (RTO) and independent system operator (ISO) to electronically deliver to the Commission, on an ongoing basis, data related to the markets that it administers. The Commission, acting pursuant to sections 301(b) and 307(a) of the Federal Power Act (FPA),<SU>1</SU>

          <FTREF/>will amend its regulations to establish ongoing electronic delivery of data relating to physical and virtual offers and bids, market awards, resource outputs, marginal cost estimates, shift factors, financial transmission rights (FTR), internal bilateral contracts, uplift, and interchange pricing. Such data will facilitate the Commission's<PRTPAGE P="26675"/>development and evaluation of its policies and regulations and will enhance Commission efforts to detect anti-competitive or manipulative behavior, or ineffective market rules, thereby helping to ensure just and reasonable rates.</P>
        <FTNT>
          <P>
            <SU>1</SU>16 U.S.C. 825(b), 825f(a).</P>
        </FTNT>
        <HD SOURCE="HD1">II. Background</HD>
        <P>2. Wholesale electricity markets have changed dramatically in recent years:<SU>2</SU>
          <FTREF/>From an industry characterized by self-sufficient, vertically integrated utilities, where most utilities operated their own generation, transmission, and distribution facilities, to an industry that utilizes market-based rates and “open access” to transmission systems. The 1980s and early 1990s experienced an increased adoption of market-based ratemaking and wholesale power sales competition to promote efficiency and to lower wholesale power prices.<SU>3</SU>
          <FTREF/>Further, the Commission found that the availability of transmission service can enhance competition in power markets, by increasing power supply options of buyers and power sales options of sellers, and can lead to lower rates for consumers.<SU>4</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>2</SU>A more in-depth discussion of developments in wholesale electricity markets—which no commenter disputed—is provided in the Notice of Proposed Rulemaking (NOPR), which can be found at<E T="03">Enhancement of Electricity Market Surveillance and Analysis through Ongoing Electronic Delivery of Data from Regional Transmission Organizations and Independent System Operators,</E>Notice of Proposed Rulemaking, 76 FR 66211 (Oct. 26, 2011), FERC Stats. &amp; Regs. ¶ 32,681 (2011).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>
            <E T="03">See, e.g.,</E>Louisville Gas &amp; Elec. Co., 62 FERC ¶ 61,016, at 61,143 &amp; n.16, 61,149 (1993) (accepting non-traditional, market-based rates as consistent with primary regulatory goal of ensuring lowest reasonable cost energy to consumers, provided service is reliable and the seller demonstrates a lack of market power);<E T="03">Pac. Gas &amp; Elec. Co.,</E>38 FERC ¶ 61,242, at 61,790 (1987) (accepting proposed competitive rates because “competition * * * encourages utilities to make efficient decisions with a minimum of regulatory intervention [and, u]ltimately, consumers should benefit from lower prices as competition improves efficiency.”),<E T="03">modified on other grounds,</E>47 FERC ¶ 61,121 (1989),<E T="03">modified,</E>50 FERC ¶ 61,339 (1990),<E T="03">modified sub nom. W. Sys. Power Pool,</E>55 FERC ¶ 61,099, at 61,319 (addressing applicant's failure to eliminate anticompetitive effects by mitigating market power),<E T="03">granting stay,</E>55 FERC ¶ 61,154,<E T="03">reh'g granted in part,</E>55 FERC ¶ 61,495 (1991),<E T="03">modified,</E>59 FERC ¶ 61,249 (1992);<E T="03">Pub. Serv. Co. of N.M.,</E>25 FERC ¶ 61,469, at 62,038 (1983) (averring that “competition penalizes a seller that is inefficient or has an unreasonable pricing strategy[; consequently,] consumers * * * benefit because the improvements in efficiency lead to lower prices.”);<E T="03">see also Heartland Energy Servs., Inc.,</E>68 FERC ¶ 61,223 (1994) (reviewing early Commission decisions granting market-based rate authority).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>
            <E T="03">Fla. Mun. Power Agency</E>v.<E T="03">Fla. Power &amp; Light Co.,</E>65 FERC ¶ 61,125, at ¶ 61,615,<E T="03">reh'g dismissed,</E>65 FERC ¶ 61,372 (1993),<E T="03">final order,</E>67 FERC ¶ 61,167 (1994),<E T="03">order on reh'g,</E>74 FERC ¶ 61,006 (1996).</P>
        </FTNT>
        <P>3. By the mid-1990s, the Commission concluded that, beyond the industry's voluntary efforts, additional measures were needed to address undue discrimination in transmission access. Accordingly, the Commission issued Order Nos. 888<SU>5</SU>
          <FTREF/>and 889,<SU>6</SU>
          <FTREF/>requiring “open access” transmission service. The Commission explained that such open access would “remove impediments to competition in the wholesale power marketplace and * * * bring more efficient, lower cost power to the Nation's electricity customers.”<SU>7</SU>
          <FTREF/>Subsequently, the Commission issued Order No. 890<SU>8</SU>
          <FTREF/>to further remedy undue discrimination and thereby remove barriers to competition.</P>
        <FTNT>
          <P>
            <SU>5</SU>
            <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, FERC Stats. &amp; Regs. ¶ 31,036 (1996),<E T="03">order on reh'g,</E>Order No. 888-A, FERC Stats. &amp; Regs. ¶ 31,048,<E T="03">order on reh'g,</E>Order No. 888-B, 81 FERC ¶ 61,248 (1997),<E T="03">order on reh'g,</E>Order No. 888-C, 82 FERC ¶ 61,046 (1998),<E T="03">aff'd in relevant part sub nom. Transmission Access Policy Study Group</E>v.<E T="03">FERC,</E>225 F.3d 667 (D.C. Cir. 2000),<E T="03">aff'd sub nom. New York</E>v.<E T="03">FERC,</E>535 U.S. 1 (2002).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>6</SU>
            <E T="03">Open Access Same-Time Information System and Standards of Conduct,</E>Order No. 889, FERC Stats. &amp; Regs. ¶ 31,035 (1996),<E T="03">order on reh'g,</E>Order No. 889-A, FERC Stats &amp; Regs. ¶ 31,049,<E T="03">reh'g denied,</E>Order No. 889-B, 81 FERC ¶ 61,253 (1997).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>7</SU>Order No. 888, FERC Stats. &amp; Regs. ¶ 31,036 at 31,634.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>8</SU>
            <E T="03">Preventing Undue Discrimination and Preference in Transmission Service,</E>Order No. 890, FERC Stats. &amp; Regs. ¶ 31,241,<E T="03">order on reh'g,</E>Order No. 890-A, FERC Stats. &amp; Regs. ¶ 31,261 (2007),<E T="03">order on reh'g,</E>Order No. 890-B, 123 FERC ¶ 61,299 (2008),<E T="03">order on reh'g,</E>Order No. 890-C, 126 FERC ¶ 61,228 (2009),<E T="03">order on clarification,</E>Order No. 890-D, 129 FERC ¶ 61,126 (2009).</P>
        </FTNT>
        <P>4. In addition to addressing undue discrimination in transmission access, Order No. 888 encouraged the formation of ISOs, reasoning that “ISOs have great potential to assist us and the industry to help provide regional efficiencies, to facilitate economically efficient pricing, and, especially in the context of power pools, to remedy undue discrimination and mitigate market power.”<SU>9</SU>
          <FTREF/>To date, the Commission has approved six RTOs and ISOs: PJM Interconnection, L.L.C. (PJM); New York Independent System Operator, Inc. (NYISO); Midwest Independent Transmission System Operator, Inc. (MISO); ISO New England Inc. (ISO-NE); California Independent System Operator Corporation (CAISO); and Southwest Power Pool, Inc. (SPP).</P>
        <FTNT>
          <P>

            <SU>9</SU>Order No. 888, FERC Stats. &amp; Regs. ¶ 31,036 at 31,652;<E T="03">see also id.</E>at 31,730-32.</P>
        </FTNT>
        <P>5. Recognizing the importance of information relating to market trading and market oversight, the Commission issued Order No. 2001<SU>10</SU>
          <FTREF/>and Order No. 697,<SU>11</SU>
          <FTREF/>establishing reporting requirements for entities selling under market-based rates. The information solicited by these orders has helped foster appropriate oversight of developing electricity markets, for “[i]nformation is the key to a viable electricity market and to preventing market manipulation.”<SU>12</SU>
          <FTREF/>In addition, the Energy Policy Act of 2005 (EPAct 2005)<SU>13</SU>
          <FTREF/>gave the Commission expanded authority to address market manipulation,<SU>14</SU>
          <FTREF/>including the ability to assess increased civil penalties.<SU>15</SU>
          <FTREF/>EPAct 2005 also provided increased criminal penalties.<SU>16</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>10</SU>
            <E T="03">Revised Public Utility Filing Requirements,</E>Order No. 2001, FERC Stats. &amp; Regs. ¶ 31,127,<E T="03">reh'g denied,</E>Order No. 2001-A, 100 FERC ¶ 61,074,<E T="03">reh'g denied,</E>Order No. 2001-B, 100 FERC ¶ 61,342,<E T="03">order directing filing,</E>Order No. 2001-C, 101 FERC ¶ 61,314 (2002),<E T="03">order directing filing,</E>Order No. 2001-D, 102 FERC ¶ 61,334,<E T="03">order refining filing requirements,</E>Order No. 2001-E, 105 FERC ¶ 61,352 (2003),<E T="03">order on clarification,</E>Order No. 2001-F, 106 FERC ¶ 61,060 (2004),<E T="03">order revising filing requirements,</E>Order No. 2001-G, 120 FERC ¶ 61,270,<E T="03">order on reh'g and clarification,</E>Order No. 2001-H, 121 FERC ¶ 61,289 (2007),<E T="03">order revising filing requirements,</E>Order No. 2001-I, 125 FERC ¶ 61,103 (2008).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>11</SU>
            <E T="03">Market-Based Rates for Wholesale Sales of Electric Energy, Capacity and Ancillary Services by Public Utilities,</E>Order No. 697, FERC Stats. &amp; Regs. ¶ 31,252,<E T="03">clarified,</E>121 FERC ¶ 61,260 (2007),<E T="03">order on reh'g,</E>Order No. 697-A, FERC Stats. &amp; Regs. ¶ 31,268, Order No. 697-B, FERC Stats. &amp; Regs. ¶ 31,285 (2008),<E T="03">order on reh'g,</E>Order No. 697-C, FERC Stats. &amp; Regs. ¶ 31,291 (2009),<E T="03">aff'd sub nom. Montana Consumer Counsel</E>v.<E T="03">FERC,</E>659 F.3d 910 (9th Cir. Oct. 13, 2011). In its decision upholding Order No. 697, the Ninth Circuit Court of Appeals noted that monitoring must be accompanied by enforcement because “[w]ithout enforcement, there is little reason to believe that sellers will police themselves.”<E T="03">Montana Consumer Counsel,</E>659 F.3d at 920 n.5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>12</SU>Charles H. Koch, Jr.,<E T="03">Collaborative Governance: Lessons for Europe from U.S. Electricity Restructuring,</E>61 Admin. L. Rev. 71, 97 (2009).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>13</SU>Public Law 109-58, 119 Stat. 594 (2005).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>14</SU>
            <E T="03">See, e.g.,</E>16 U.S.C. 824v.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>15</SU>
            <E T="03">See</E>16 U.S.C. 825o-1 (civil penalties).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>16</SU>
            <E T="03">See</E>16 U.S.C. 825o (criminal penalties).</P>
        </FTNT>
        <P>6. Independent market monitoring by RTO and ISO market monitoring units (MMU) is another important means to evaluate market developments and to identify and deter market abuses and manipulation. In Order No. 2000, the Commission identified market monitoring as a basic function of an RTO.<SU>17</SU>
          <FTREF/>The Commission refined its approach to MMUs in a 2005 policy statement and in Order No. 719.<SU>18</SU>
          <FTREF/>In the<PRTPAGE P="26676"/>2005 Policy Statement, the Commission outlined tasks for MMUs to perform in order to enhance the competitive structure of RTO and ISO markets.<SU>19</SU>
          <FTREF/>Subsequently, in Order No. 719, the Commission further clarified requirements for MMU functions, independence, and information sharing.<SU>20</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>17</SU>Prior to this first generic consideration of MMUs in Order No. 2000, the Commission addressed market monitoring in connection with individual RTO and ISO proposals.<E T="03">See Pac. Gas &amp; Elec. Co.,</E>77 FERC ¶ 61,265 (1996),<E T="03">order on reh'g,</E>81 FERC ¶ 61,122 (1997),<E T="03">order on clarification,</E>83 FERC ¶ 61,033 (1998) (requiring the ISO to file a detailed monitoring plan and listing minimum elements for such a plan);<E T="03">Pennsylvania-New Jersey-Maryland Interconnection,</E>81 FERC ¶ 61,257 (1997) (requiring PJM Interconnection, L.L.C. to develop a market monitoring program to evaluate market power and market design flaws).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>18</SU>
            <E T="03">Market Monitoring Units in Regional Transmission Organizations and Independent System Operators,</E>111 FERC ¶ 61,267 (2005) (2005 Policy Statement);<E T="03">Wholesale Competition in<PRTPAGE/>Regions with Organized Electric Markets,</E>Order No. 719, FERC Stats. &amp; Regs. ¶ 31,281 (2008),<E T="03">order on reh'g,</E>Order No. 719-A, FERC Stats. &amp; Regs. ¶ 31,292 (2009),<E T="03">order on reh'g,</E>Order No. 719-B, 129 FERC ¶ 61,252 (2009).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>19</SU>2005 Policy Statement, 111 FERC ¶ 61,267 at P 2.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>20</SU>Specifically, MMU functions consist of evaluating existing and proposed market rules, tariff provisions, and market design elements and recommending changes, if applicable; reviewing and reporting on the performance of wholesale markets; and identifying and notifying the Commission of behavior that may require investigation.<E T="03">See</E>Order No. 719, FERC Stats. &amp; Regs. ¶ 31,281 at P 354.</P>
        </FTNT>
        <P>7. While MMUs perform a vital and necessary function in market oversight,<SU>21</SU>
          <FTREF/>they do not supplant the Commission's authority.<SU>22</SU>
          <FTREF/>Rather, MMUs are designed to provide the Commission with an additional means of detecting market power abuses, market design flaws, and opportunities for improvements in market efficiency.<SU>23</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>21</SU>
            <E T="03">See, e.g.,</E>Order No. 719, FERC Stats. &amp; Regs. ¶ 31,281 at P 314.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>22</SU>Order No. 2000, FERC Stats. &amp; Regs. ¶ 31,089 at 31,156-57.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>23</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD1">III. Discussion</HD>
        <HD SOURCE="HD2">A. Commission Authority and the Need for Market Data</HD>
        <HD SOURCE="HD3">1. NOPR</HD>
        <P>8. The NOPR proposed to obtain ongoing delivery of RTO and ISO data pursuant to the Commission's authority under sections 301(b) and 307(a) of the FPA.<SU>24</SU>
          <FTREF/>Section 301(b) provides that the Commission shall at all times have access to, and the right to inspect and examine, all accounts and records of public utilities; section 307(a) provides that the Commission has authority to investigate any facts, conditions, practices, or matters it may deem necessary or proper to determine whether any person, electric utility, transmitting utility, or other entity may have violated or might violate the FPA or the Commission's regulations, or to aid in the enforcement of the FPA or the Commission's regulations, or to obtain information about wholesale electric energy sales or the transmission of electric energy in interstate commerce.</P>
        <FTNT>
          <P>
            <SU>24</SU>16 U.S.C. 825(b); 16 U.S.C. 825f(a).</P>
        </FTNT>
        <P>9. In the NOPR, the Commission sought comment on its proposal to revise its regulations to require each RTO and ISO to electronically deliver to the Commission, on an ongoing, non-public basis, data related to the markets that it administers;<SU>25</SU>
          <FTREF/>namely, data relating to physical and virtual offers and bids, market awards, resource outputs, marginal cost estimates, shift factors, FTRs, internal bilateral contracts, and interchange pricing.<SU>26</SU>
          <FTREF/>The Commission explained that ongoing electronic delivery of data from each RTO and ISO would facilitate the Commission's development and evaluation of its policies and regulations and would enhance Commission efforts to detect anti-competitive or manipulative behavior, or ineffective market rules, thereby helping to ensure just and reasonable rates.</P>
        <FTNT>
          <P>
            <SU>25</SU>Appendix A lists commenters and their abbreviated names as used here.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>26</SU>
            <E T="03">See</E>NOPR, FERC Stats. &amp; Regs. ¶ 32,681 at P 36;<E T="03">see infra</E>§ III.F (Data Requested) for the data in this final rule to be provided.</P>
        </FTNT>
        <P>10. The NOPR also emphasized efforts by the Commission to streamline the collection of data it already has the authority to request from public utilities. The Commission noted that it currently requests data from individual RTOs and ISOs on an ad hoc basis. The Commission averred that such ad hoc requests may require more Commission and RTO and ISO resources than the proposed ongoing electronic delivery of this data using an automated process. Accordingly, the Commission proposed to require an automated ongoing data delivery process, in part, to minimize any burden on RTOs and ISOs.</P>
        <P>11. In the NOPR, the Commission also addressed the relationship between the Commission and the MMUs. The Commission explained that the NOPR did not seek to displace or modify any of the existing market monitoring functions or any evaluations of market rules and designs performed by the MMUs; rather, the intent of the data collection is to help the Commission detect anti-competitive or manipulative behavior, inefficient market rules, and ensure just and reasonable rates.<SU>27</SU>
          <FTREF/>The Commission acknowledged that MMUs perform a vital and necessary function in market oversight.<SU>28</SU>
          <FTREF/>The Commission explained that, rather than supplant the Commission's authority,<SU>29</SU>
          <FTREF/>MMUs are designed to provide the Commission with an additional means of detecting market power abuses, market design flaws, and opportunities for improvements in market efficiency.<SU>30</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>27</SU>
            <E T="03">See</E>NOPR, FERC Stats. &amp; Regs. ¶ 32,681 at PP 29 &amp; 35.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>28</SU>
            <E T="03">Id.</E>PP 8-9 (citing Order No. 719, FERC Stats. &amp; Regs. ¶ 31,281 at P 314).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>29</SU>
            <E T="03">Id.</E>P 9 (citing Order No. 2000, FERC Stats. &amp; Regs. ¶ 31,089 at 31,156-57).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>30</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD3">2. Comments</HD>
        <P>12. Commenters do not dispute the Commission's authority under sections 301(b) and 307(a) of the FPA to require ongoing delivery of data from each RTO and ISO. As PA PUC stated, the proposal to expand the categories of information that RTOs and ISOs have to make available to the Commission is a logical and necessary extension of the Commission's existing authority under sections 301 and 307 of the FPA.<SU>31</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>31</SU>PA PUC at 2.</P>
        </FTNT>
        <P>13. Most commenters agree that ongoing delivery of data from each RTO and ISO would assist the Commission in carrying out its monitoring functions.<SU>32</SU>
          <FTREF/>For instance, Powerex states that:</P>
        <FTNT>
          <P>

            <SU>32</SU>SWP at 1-2; NYPSC at 3; PA PUC at 2-10; IRC at 1-2; Powerex § IV.A; APPA at 6; ISO-NE at 3; EEI/EPSA at 6;<E T="03">see also</E>CAC/EPUC at 1 (expressing no protest against such delivery of data).</P>
        </FTNT>
        
        <EXTRACT>
          <P>The Commission correctly recognizes that as markets continue to evolve with increased levels of sophistication, the Commission must continue to evaluate the type of data necessary to ensure just and reasonable rates. Having ongoing, routine access to [RTO and ISO] data will provide greater transparency to the Commission on market activities and allow the Commission to perform systematic, comprehensive analysis to aid in monitoring market behavior and creating effective market rules and efficient market design.[<SU>33</SU>]<FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>33</SU>Powerex § IV.A. (footnote omitted).</P>
          </FTNT>
        </EXTRACT>
        
        <P>14. Several commenters agree that an ongoing, automated data delivery process may reduce administrative burdens on the RTOs and ISOs and the Commission when compared with ad hoc data requests.<SU>34</SU>
          <FTREF/>The PA PUC states that it does not believe the rules expanding RTO and ISO reporting requirements will unnecessarily burden these organizations.<SU>35</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>34</SU>
            <E T="03">Id.</E>§ IV.A.; ISO-NE at 3.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>35</SU>PA PUC at 4.</P>
        </FTNT>
        <P>15. In their joint comments, EEI/EPSA state that they understand the Commission's desire to collect information to enhance its market monitoring and surveillance capabilities but question the need for ongoing data transfers to the Commission.<SU>36</SU>
          <FTREF/>Specifically, EEI/EPSA question why the Commission needs the additional information; whether the Commission is proposing to duplicate the function of RTO and ISO MMUs; the justification for imposing a burden on RTOs and ISOs and market participants; and why the Commission is collecting more information than what is contained in the Electric Quarterly Reports (EQR).<SU>37</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>36</SU>EEI/EPSA at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>37</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <PRTPAGE P="26677"/>
        <HD SOURCE="HD3">3. Commission Determination</HD>
        <P>16. The Commission concludes that requiring each RTO and ISO to electronically deliver to the Commission on an ongoing, non-public basis, data related to the markets that each administers will help the Commission to carry out its statutory responsibilities, as explained below. The Commission finds that the revisions are consistent with the Commission's authority under sections 301(b) and 307(a) of the FPA. In addition, these reforms are expected to reduce administrative burdens on the RTOs and ISOs.</P>
        <P>17. EEI/EPSA's joint comments touch on a range of issues regarding the ongoing delivery of data from the RTOs and ISOs. Specifically, they ask why the Commission needs the specified data and question whether such reporting will result in duplicative market monitoring. These datasets are necessary to the Commission's better ensuring that Commission jurisdictional rates are just and reasonable.<SU>38</SU>
          <FTREF/>Ongoing electronic delivery of these particular datasets will help the Commission more effectively and accurately, and thus more efficiently, monitor and evaluate the activity in RTO and ISO markets. Such data will permit the Commission to improve its screening of participants' market activity for inappropriate conduct, making such conduct more difficult to mask.<SU>39</SU>
          <FTREF/>In addition, the ongoing delivery of this data will provide a better picture of market activity and lessen the possibility that market monitoring and surveillance screens will result in error. Thus, electronic delivery of this data will permit the Commission to meet its statutory obligations in a more efficient manner.</P>
        <FTNT>
          <P>
            <SU>38</SU>
            <E T="03">See</E>16 U.S.C 824d, 824e.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>39</SU>
            <E T="03">See</E>NOPR, FERC Stats. &amp; Regs. ¶ 32,681 at PP 30-31.</P>
        </FTNT>
        <P>18. The Commission's oversight capabilities, and associated data delivery requirements, must keep pace with market developments and evolve along with the markets. A part of the Commission's oversight of the wholesale electricity markets is the evaluation of existing market designs and the effectiveness of current market rules. The ongoing, electronic delivery of specific datasets will enable the Commission to more effectively carry out this function. This data will provide the Commission with empirical information that will augment its ability to assess the effectiveness of Commission-approved market rules and provide better tools to monitor the efficiency of existing market designs in producing just and reasonable rates. Thus, the ongoing delivery of the data sought in this final rule will inform the Commission's continuing evaluation of market rules, regulations, and the development of its policies.</P>
        <P>19. Requiring this data does not displace the MMUs' existing efforts to evaluate market rules and market designs or modify any of their market monitoring functions. Nor does the Commission's analysis and monitoring efforts using the data specified in this final rule duplicate the MMUs' existing efforts. For example, because of the Commission's ability to look across all RTO and ISO markets, the Commission is in a unique position to perform cross-market analysis. This cross-market analysis will enhance the Commission's ongoing efforts to improve surveillance and monitoring of the markets and assess the performance of different market designs and rules.<SU>40</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>40</SU>
            <E T="03">Id.</E>P 29.</P>
        </FTNT>
        <HD SOURCE="HD2">B. Duplicative Requirements</HD>
        <HD SOURCE="HD3">1. NOPR</HD>
        <P>20. The NOPR stated that the electronic delivery of the types of data proposed herein will help to maintain the Commission's access to RTO and ISO data on par with the types and levels of activity in those markets and will help to ensure that rates are just and reasonable.<SU>41</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>41</SU>
            <E T="03">Id.</E>P 13.</P>
        </FTNT>
        <HD SOURCE="HD3">2. Comments</HD>
        <P>21. Several commenters urge the Commission to avoid duplicative reporting, given other recent data collection requirements.<SU>42</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>42</SU>SWP at 2 (referring to EQR requirements); EEI/EPSA at 8-9 (same);<E T="03">see also Electricity market Transparency Provisions of Section 220 of the Federal Power Act,</E>FERC Stats &amp; Regs., Proposed Rules ¶ 32,676 (Apr. 21, 2011).</P>
        </FTNT>
        <P>22. Consistent with the mandate to avoid duplicative or unnecessarily burdensome regulation,<SU>43</SU>
          <FTREF/>SWP urges the Commission to consider the impact of this additional data requirement. SWP posits that the EQR reporting requirements in Docket No. RM10-12 are duplicative and, in fact, the EQR data come from transactions that are already captured by other government reports, RTO and ISO reports, and reports by non-jurisdictional entities' public utility counterparties.<SU>44</SU>
          <FTREF/>SWP states that the instant proposal makes the EQR reporting requirements redundant and unwarranted, given the Commission's statutory and executive mandates for streamlining regulation, reducing regulatory burdens, and eliminating duplicative reporting requirements.<SU>45</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>43</SU>
            <E T="03">See Plan for Retrospective Analysis of Existing Rules,</E>Docket No. AD12-6 (Nov. 8, 2011) (“The Commission voluntarily and routinely, albeit informally, reviews its regulations to ensure that they achieve their intended purpose and do not impose undue burdens on regulated entities or unnecessary costs on those entities or their customers. In addition, the Commission considers the spirit of these Executive Orders [mandating regulatory streamlining and avoidance of unnecessary regulatory burdens] when evaluating possible new regulations.”),<E T="03">available at http://www.ferc.gov/legal/maj-ord-reg/retro-analysis/ferc-eo-13579.pdf.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>44</SU>SWP at 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>45</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>23. In their joint comments, EEI/EPSA encourage the Commission to require RTOs and ISOs to report EQR information for sales conducted within their markets, whether or not the RTOs and ISOs are actual counterparties to the transactions.<SU>46</SU>
          <FTREF/>They also suggest that the Commission hold RTOs and ISOs responsible for the accuracy of the information they provide, to avoid duplicative burden on market participants.<SU>47</SU>
          <FTREF/>Consequently, EEI/EPSA suggest that the Commission explicitly clarify that market participants are no longer required to report in their own EQRs the information that RTOs and ISOs are required to report under the final rule, nor to report in other Commission forms information that will be provided by RTOs and ISOs under the final rule.<SU>48</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>46</SU>EEI/EPSA at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>47</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>48</SU>
            <E T="03">Id.</E>at 8. Additionally, EEI/EPSA suggest that there would be significant benefits associated with their proposal: if properly implemented, these changes would considerably reduce the burden for EQR filers and other RTOs and ISOs; would significantly reduce the size of most EQR Filings, largely resolving size-related upload problems that have occurred; a Commission EQR database consisting of only bilateral data would be much smaller and more manageable (the Commission could maintain a separate database of RTO and ISO market transactions or rely on information posted on RTO and ISO Web sites or servers); and, RTO and ISO sales data would be consistently, completely, and correctly reported. EEI/EPSA 8-9.</P>
        </FTNT>
        <HD SOURCE="HD3">3. Commission Determination</HD>
        <P>24. Despite some similarities in data provided by market participants in their EQRs, we find that the reporting requirements placed on RTOs and ISOs in this final rule facilitate, rather than compromise, the goals of streamlining regulation, reducing regulatory burdens, or eliminating duplicative reporting requirements.</P>

        <P>25. First, the nature of the data, the frequency of its collection, and the data format differ between the data submitted in EQRs and the data sought here. Currently, market participants provide contractual and transactional data in their EQRs related to their jurisdictional sales and transmission service in a specified format that is<PRTPAGE P="26678"/>made available to the public. The Commission established the EQR reporting requirements in Order No. 2001<SU>49</SU>
          <FTREF/>to help ensure the collection of information needed to perform the Commission's regulatory responsibilities over sales and transmission service, while making available data useful to the public and allowing public utilities to better fulfill their responsibility under FPA section 205(c) to have rates on file in a convenient form and place.<SU>50</SU>

          <FTREF/>By contrast, this final rule initiates a process for collecting<E T="03">non-public</E>data from the RTOs and ISOs relating to market participants' jurisdictional service in the RTO and ISO markets, which is more granular and diverse. RTOs and ISOs will deliver this data, pursuant to the Commission's authority under sections 301(b) and 307(a) of the FPA, in a format consistent with how the data is currently collected in each RTO and ISO system,<SU>51</SU>
          <FTREF/>on an ongoing (rather than quarterly) basis to help the Commission stay informed of market developments and to help ensure just and reasonable rates through better market surveillance and evaluation of policies and regulations.</P>
        <FTNT>
          <P>

            <SU>49</SU>Order No. 2001, FERC Stats. &amp; Regs. ¶ 31,127. In a recent Notice of Proposed Rulemaking, the Commission proposed to amend its EQR regulations to require market participants that are excluded from the Commission's jurisdiction under FPA section 205 and have more than a de minimis market presence to file EQRs with the Commission.<E T="03">S</E>ee<E T="03">Electricity Market Transparency Provisions of Section 220 of the Federal Power Act,</E>Notice of Proposed Rulemaking, FERC Stats. &amp; Regs. ¶ 32,676 (2011).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>50</SU>Order No. 2001, FERC Stats. &amp; Regs. 31,127 at P 31.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>51</SU>
            <E T="03">See infra</E>§ III.D (Data Formatting).</P>
        </FTNT>
        <P>26. Second, this final rule streamlines the process through which RTOs and ISOs provide data to the Commission by requiring ongoing delivery of such data, instead of relying on periodic, ad hoc requests.</P>
        <P>27. Third, no additional regulatory burden is placed on market participants through these requirements, as the data sought is already collected by the RTOs and ISOs and will not be separately collected by the Commission from individual market participants.</P>
        <P>28. Accordingly, we find that RTOs' and ISOs' reporting requirements under this final rule do not duplicate market participants' EQR reporting requirements. Based on this finding, we will continue to require individual market participants to submit their EQRs.</P>
        <P>29. With respect to certain commenters' concern about the burden on market participants of filing information in EQRs about sales in RTO and ISO markets, we note that RTOs and ISOs may file EQRs on behalf of their members or participants if authorized to do so as their agent.<SU>52</SU>
          <FTREF/>We also note that the Commission has worked with numerous RTOs and ISOs to produce settlement reports in a format that allows easy importation into the EQR software.</P>
        <FTNT>
          <P>
            <SU>52</SU>
            <E T="03">See</E>Order No. 2001, FERC Stats. &amp; Regs. ¶ 31,127 at P 336; Order No. 2001-E, 105 FERC ¶ 61,352 at P 12.</P>
        </FTNT>
        <HD SOURCE="HD2">C. Confidentiality of Data</HD>
        <HD SOURCE="HD3">1. NOPR</HD>
        <P>30. In the NOPR, the Commission stated that much of the information it will receive is, by its nature, commercially sensitive.<SU>53</SU>
          <FTREF/>Disclosure of such information could result in competitive harm to market participants and the market as a whole.<SU>54</SU>
          <FTREF/>Accordingly, the Commission proposed that the data sought would not be made publicly available, except as may be directed by the Commission or a court with appropriate jurisdiction.<SU>55</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>53</SU>In the past, the Commission has granted requests for privileged or confidential treatment of similar non-public data.<E T="03">See, e.g., N.Y. Indep. Sys. Operator, Inc.,</E>131 FERC ¶ 61,169, at P 15 (2010) (granting such treatment for data relating to specific generator or other equipment details, transmission system information, bidding strategies, generator reference levels, generator costs, guarantee payments, and the associated relevant time periods);<E T="03">see also S. Cal. Edison Co.,</E>135 FERC ¶ 61,201, at P 20 (2011);<E T="03">Hydrogen Energy Cal. LLC,</E>135 FERC ¶ 61,068, at P 25 (2011);<E T="03">N.Y. Indep. Sys. Operator, Inc.,</E>130 FERC ¶ 61,029, at P 3 (2010).</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>54</SU>The Freedom of Information Act (FOIA) allows persons to file requests to obtain data from the Commission. FOIA exemption 4 protects “trade secrets and commercial or financial information obtained from a person [that is] privileged or confidential.” 5 U.S.C. 552(b)(4) (2006),<E T="03">amended by</E>OPEN Government Act of 2007, Pub. L. 110-175, 121 Stat. 2524 (2007);<E T="03">accord</E>18 CFR 388.107(d). We would expect that commercially-sensitive data, like that described in the NOPR, which satisfy the requirements of exemption 4 would be protected from disclosure.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>55</SU>Section 301(b) of the FPA, 16 U.S.C. 825(b), provides that no member, officer, or employee of the Commission may divulge any fact or information that may come to his knowledge during the course of examination of books or other accounts, except as may be directed by the Commission or by a court.</P>
        </FTNT>
        <P>31. The Commission stated in the NOPR that it will make publicly available the analysis derived from data that the Commission uses, for example, to support a proposed market rule change, except that the Commission will ensure that confidential information will remain non-public. The Commission also noted that it may direct its staff to issue a public report outside of a rulemaking proceeding with similar protections for confidential or otherwise protected information.</P>
        <HD SOURCE="HD3">2. Comments</HD>
        <P>32. Several commenters note that some of the data the Commission is proposing to receive is commercially sensitive and should be protected from release.<SU>56</SU>
          <FTREF/>Commenters also argue that it would be beneficial to publicly release some of the information the Commission is proposing to receive.<SU>57</SU>
          <FTREF/>APPA notes, for instance, that the Commission could take a strong first step in improving market transparency by requiring RTOs and ISOs to publish bid information, including identification of bidders, within a reasonable timeframe.<SU>58</SU>
          <FTREF/>Powerex notes that while some of the data, if released, would result in competitive harm, much of the information the Commission is seeking from the RTOs and ISOs is already publicly available. As such, Powerex argues that public release of certain data would support better investment decisions and better responses to price signals, and would create more confidence in the functioning of markets, which in turn would benefit the whole market and end-use consumers because better decisions result in lower risk premiums and lower costs for consumers.<SU>59</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>56</SU>
            <E T="03">See</E>CAC/EPUC at 1-2; EEI/EPSA at 10; Powerex § IV.C.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>57</SU>
            <E T="03">See</E>Powerex § IV.C; APPA at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>58</SU>APPA at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>59</SU>Powerex § IV.C. Powerex notes that the following data should be made publicly available: (1) Market awards (both volumes and prices including all Exceptional and Out-of-market dispatches); (2) resource outputs (including actual delivery to/from interties; (3) Financial Transmission Rights, including Congestion Revenue Rights; (4) uplift costs per megawatt; and (5) make-whole and bid cost recovery payments. Powerex § IV.C.</P>
        </FTNT>
        <P>33. In their joint comments, EEI/EPSA raise concerns about the security of the data transferred to the Commission and the potential for information retained by the Commission to be discoverable under FOIA.<SU>60</SU>
          <FTREF/>Specifically, EEI/EPSA state they are concerned about the Commission's ability to honor its commitment to keep the information non-public under the Commission's current rules and regulations. EEI/EPSA state that, prior to requiring RTOs and ISOs to report this information, the Commission should adopt rules that would ensure that this information is kept confidential and not disclosed.<SU>61</SU>
          <FTREF/>
          <PRTPAGE P="26679"/>EEI/EPSA also suggest that the Commission could allow RTOs and ISOs to post any non-confidential information on their Web sites or servers rather than having to deliver it to the Commission.<SU>62</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>60</SU>
            <E T="03">See</E>EEI/EPSA at 9-11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>61</SU>EEI/EPSA at 11. EEI/EPSA's concern is that“the Commission may not be able to maintain the confidentiality of the information under FOIA. As a practical matter it can be difficult for any agency to ensure such confidentiality under FOIA with absolute certainty. As such, EEI and EPSA request that the Commission avoid collecting sensitive information, require any such information that is reported to be aggregated to minimize disclosure<PRTPAGE/>concerns, and ensure the appropriate rules and regulations are enacted prior to requiring the reporting of confidential information.”</P>
          <P>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>62</SU>EEI/EPSA at 4.</P>
        </FTNT>
        <HD SOURCE="HD3">3. Commission Determination</HD>
        <P>34. As the Commission stated in the NOPR, much of the information that the Commission expects to receive in this proposal is, by its nature, commercially sensitive.<SU>63</SU>
          <FTREF/>While one may file a request to obtain data from the Commission,<SU>64</SU>
          <FTREF/>FOIA exemption 4 protects “trade secrets and commercial or financial information obtained from a person [that is] privileged or confidential.”<SU>65</SU>
          <FTREF/>Accordingly, although the Commission cannot foreclose requests of information relating to ongoing electronic submissions of non-public data, we expect that all such data found to satisfy the requirements of exemption 4 would be protected from disclosure.</P>
        <FTNT>
          <P>
            <SU>63</SU>
            <E T="03">See</E>NOPR, FERC Stats. &amp; Regs. ¶ 32,681 at P 45.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>64</SU>
            <E T="03">See id.</E>P 45 &amp; n.48. We note that RTOs and ISOs also can specifically request privileged and confidential treatment by marking their documentation that accompanies the data delivery (<E T="03">see infra</E>P 43 &amp; n.75) pursuant to 5 U.S.C. 552, 18 CFR 1b.9, 1b.20, and 388.112.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>65</SU>5 U.S.C. 552(b)(4) (2006),<E T="03">amended by</E>OPEN Government Act of 2007, Pub. L. 110-175, 121 Stat. 2524 (2007);<E T="03">accord</E>18 CFR 388.107(d).</P>
        </FTNT>
        <P>35. The Commission may, of course, make publicly available analyses derived from data that the Commission uses, but insofar as the law allows, the Commission will ensure that confidential information will remain non-public. The Commission's doing these kinds of analyses and making them public is appropriate. Such analyses may be, among other things, in the form of a staff white paper or the initiation of a rulemaking proceeding, both of which are equally appropriate uses of the information collected.</P>
        <P>36. The Commission recognizes that public release of certain data may support better investment decisions and better responses to price signals, as Powerex maintains, and also that portions of the information the Commission is seeking from the RTOs and ISOs already may be publicly available. However, the datasets the Commission will receive pursuant to this final rule are expected to contain in large measure the type of information covered under FOIA exemption 4, and would remain non-public.</P>
        <HD SOURCE="HD2">D. Data Formatting</HD>
        <HD SOURCE="HD3">1. NOPR</HD>
        <P>37. The Commission proposed to require that any data electronically delivered to the Commission be in an XML format that is consistent for all RTOs and ISOs. The Commission stated that it was not proposing that each RTO and ISO materially modify the data prior to electronic delivery. The Commission sought comment on data formatting, noting that XML may not be the preferred format to use when electronically delivering RTO and ISO data.<SU>66</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>66</SU>
            <E T="03">See</E>NOPR, FERC Stats. &amp; Regs.¶ 32,681 at P 42.</P>
        </FTNT>
        <HD SOURCE="HD3">2. Comments</HD>
        <P>38. Commenters generally support allowing each RTO and ISO to provide data in its current format with minimal modification, rather than in a format consistent for all RTOs and ISOs.<SU>67</SU>
          <FTREF/>ISO-NE contends that a common format would require a significantly longer implementation timeframe.<SU>68</SU>
          <FTREF/>NYPSC posits that unnecessary expenses due to converting the format (to one not currently used by the RTOs and ISOs) could be costly, leading to a negative impact on ratepayers.<SU>69</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>67</SU>NYPSC at 4; IRC at 2-4; ISO-NE at 3; EEI/EPSA at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>68</SU>ISO-NE at 3</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>69</SU>NYPSC at 4.</P>
        </FTNT>
        <P>39. The IRC states that regional differences and the individual market designs of each RTO and ISO may lead to discrepancies when attempting to reconcile these different market rules and products into XML or another common format.<SU>70</SU>
          <FTREF/>The IRC proposes that each RTO and ISO electronically deliver the requested data in a format that mirrors the format in each one's system, with minimal transformation. The IRC further proposes that the data would be delivered to the Commission in a format acceptable to the Commission and that a guide explaining the data format and presentation would be provided.<SU>71</SU>
          <FTREF/>Specifically, the IRC proposes to add the italicized language below to the text proposed in the NOPR:</P>
        <FTNT>
          <P>
            <SU>70</SU>IRC at 3.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>71</SU>
            <E T="03">Id.</E>at 4.</P>
        </FTNT>
        
        <EXTRACT>

          <FP>Each Commission-approved regional transmission organization and independent system operator must electronically deliver to the Commission, on an ongoing basis<E T="03">and in a form and manner consistent with its own collection of data</E>and in a form and manner acceptable to the Commission, data related to the markets that the regional transmission organizations or independent system operators administers.</FP>
        </EXTRACT>
        
        <HD SOURCE="HD3">3. Commission Determination</HD>
        <P>40. Given the various data collection and storage methods used by RTOs and ISOs, we will allow data to be electronically delivered to the Commission in a format consistent with how the data is collected in each RTO and ISO system.<SU>72</SU>
          <FTREF/>We agree with commenters that requiring data delivery in a consistent format for all RTOs and ISOs likely would be more costly and may result in data that fails to accurately capture the nuances of each market. Accordingly, the Commission will include the IRC's proposed additions, reflected in the italicized language above, in the regulation adopted by this final rule.</P>
        <FTNT>
          <P>

            <SU>72</SU>We consider format to include the structure of the data (<E T="03">i.e.,</E>the data tables, columns, rows, and fields), as well as details relating to the data specifications for each field (<E T="03">i.e.,</E>string, numeric, etc.).</P>
        </FTNT>

        <P>41. We recognize that the current data format and storage procedures used by each RTO and ISO may require that they make certain adjustments before the datasets are electronically delivered to the Commission, which are expected to be minimal. These adjustments, if necessary, will secure dependable, ongoing delivery of the data while preserving the individual character of each RTO's or ISO's datasets. For example, data the Commission is requesting may be stored by an RTO or ISO in a manner such that a particular dataset contains additional details that are unnecessary for Commission analysis. Similarly, an RTO's or ISO's reported times may be stored in various time zones, both within each RTO or ISO and across the RTOs and ISOs. Adjusting such data to either reduce the volume of information delivered to the Commission or to reflect a uniform time zone,<E T="03">inter alia,</E>will improve the Commission's ability to understand and manage the data. Therefore, the Commission would expect that RTOs and ISOs will make certain minimal adjustments to the datasets from time to time, working with Commission staff.</P>
        <P>42. As part of the determination not to require a consistent format for all RTOs and ISOs, we will direct that such data be delivered in one of two file types; namely, Comma Separated Value (i.e., CSV) or Tab Delimited.<SU>73</SU>

          <FTREF/>These file types have been listed in order of Commission preference; they are commonly used file types and provide sufficient flexibility to allow for divergent formatting schemes among the RTOs and ISOs. Each RTO and ISO<PRTPAGE P="26680"/>must use the file type it selects on a consistent basis, that is, without altering the file type with each data transfer. Accordingly, we will not accept data delivered in XML, because its use may be more appropriate in situations where the formatting is consistent.<SU>74</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>73</SU>RTOs and ISOs, working with Commission staff, may switch to one of the other two file types. Moreover, in the future another file type may be determined to be more practicable or desirable.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>74</SU>As the IRC noted, XML may be appropriate when presenting data that is based on a common format (IRC at 3). The use of XML is unsuitable for this data collection when common formatting does not exist.</P>
        </FTNT>
        <P>43. Further, we agree with the IRC that documentation defining each field in the datasets provided by the RTOs and ISOs would assist the Commission in its analysis of the electronic data.<SU>75</SU>
          <FTREF/>Accordingly, we will require each RTO and ISO to provide such documentation, given that correctly interpreting and understanding the data is a prerequisite to any analytic effort. Moreover, the Commission directs that such documentation be provided initially no later than 30 days prior to the first day of the ongoing delivery for each dataset.</P>
        <FTNT>
          <P>

            <SU>75</SU>We consider documentation defining each field to consist of a data dictionary, entity relationship model, and file transfer record layout. This documentation would provide details about data such as meaning, relationships to other data, origin, usage, and format, as well as details defining the method for identifying new record submissions and record corrections (<E T="03">i.e.,</E>an addition to, change in, or deletion of previously delivered data).</P>
        </FTNT>
        <P>44. Finally, to allow the Commission to stay abreast of any change in how data described in this final rule is collected, we direct each RTO and ISO to notify Commission staff in writing of any such change, 90 days prior to such a change or as soon as practicable once such a change is known. Such a change may necessitate the submission of updated documentation. Notifications of forthcoming changes, and updated documentation when appropriate, will allow the Commission to anticipate and make necessary adjustments to its own management and storage of RTO and ISO data, especially given that the data will not be received in a single consistent format across the RTOs and ISOs.</P>
        <HD SOURCE="HD2">E. Web-Based Delivery</HD>
        <HD SOURCE="HD3">1. NOPR</HD>
        <P>45. Due to the commercially-sensitive nature of the requested market data, the Commission proposed that each RTO and ISO use a secure data delivery method to provide data to the Commission. Specifically, the Commission proposed that RTO and ISO market data be electronically delivered using the Secure File Transfer Protocol (SFTP) and that access to the server where the data is electronically delivered only be granted to each applicable RTO and ISO and to the Commission.</P>
        <HD SOURCE="HD3">2. Comments</HD>
        <P>46. ISO-NE and the IRC do not anticipate problems associated with using SFTP to transfer encrypted market data to the Commission; they expect this method to be straightforward.<SU>76</SU>
          <FTREF/>Both commenters state that the Commission should allow flexibility with respect to whether each RTO or ISO or the Commission hosts the exchange server.<SU>77</SU>
          <FTREF/>For this purpose, the IRC urges the Commission to define “deliver” in this context as either “transmission to the Commission” or as “making available to the Commission for retrieval.”<SU>78</SU>
          <FTREF/>The IRC suggests that other delivery mechanisms may be more technically attractive and, if the Commission finds this to be the case, requests that the Commission accommodate the other delivery mechanisms that are acceptable.<SU>79</SU>
          <FTREF/>Finally, as noted above, in lieu of delivery to the Commission, EEI/EPSA suggest that the Commission could allow RTOs and ISOs to post any non-confidential information on their Web sites or servers.<SU>80</SU>
          <FTREF/>In the event the Commission requires data to be delivered, EEI/EPSA suggest that the data be aggregated such that any disclosure will not cause commercial impacts.<SU>81</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>76</SU>ISO-NE at 5-6; IRC at 4-5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>77</SU>ISO-NE at 5-6; IRC at 4-5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>78</SU>IRC at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>79</SU>
            <E T="03">Id.</E>at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>80</SU>EEI/EPSA at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>81</SU>
            <E T="03">Id.</E>at 10.</P>
        </FTNT>
        <HD SOURCE="HD3">3. Commission Determination</HD>
        <P>47. We adopt the proposal outlined in the NOPR which requires RTO and ISO market data to be electronically delivered using SFTP.<SU>82</SU>
          <FTREF/>Access to the server where the data is electronically delivered will only be granted to each applicable RTO and ISO and to the Commission.<SU>83</SU>
          <FTREF/>We define “deliver” in this final rule to mean “transmission to the Commission.”</P>
        <FTNT>
          <P>
            <SU>82</SU>In the future, another delivery method may be determined to be more practicable or desirable.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>83</SU>If the RTO or ISO elects to have the MMU deliver data to the Commission, the MMU also should be granted access to the server where data is delivered.<E T="03">See infra</E>P 61.</P>
        </FTNT>
        <P>48. The Commission rejects EEI/EPSA's suggestions that the Commission allow RTOs and ISOs to post only non-confidential information on their Web sites or to require the delivery of aggregated data to satisfy the requirement for ongoing delivery to the Commission. Commission use of such postings of non-confidential information or delivery of aggregated information would do little to further the Commission's market surveillance and its evaluation of policies and regulations. And as discussed in greater detail above, data that is electronically delivered pursuant to this final rule likely would be considered non-public.<SU>84</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>84</SU>
            <E T="03">See supra</E>§ III.C. (Confidentiality of Data).</P>
        </FTNT>
        <HD SOURCE="HD2">F. Data Requested</HD>
        <HD SOURCE="HD3">1. NOPR</HD>
        <P>49. In the NOPR, the Commission proposed to require ongoing electronic delivery of the data (e.g., the information to be included in the datasets) described below:</P>
        <P>1. Supply offers and demand bids for energy and ancillary services—Data on supply offers and demand bids submitted to RTO and ISO markets. This dataset would include all offers and bids for energy and ancillary services. This dataset would also include offers and bids submitted for interchange transactions, as well as those submitted without economic consideration, i.e., self-schedules.</P>
        <P>2. Virtual offers and bids—Data on virtual supply offers and virtual demand bids submitted to RTO and ISO markets.</P>
        <P>3. Energy/ancillary service awards—Data on market awards for energy and ancillary services. This dataset would include the quantity and price of all market awards for energy and ancillary services. The dataset would also identify resources that are self-scheduled.</P>
        <P>4. Capacity market offers, designations, and prices—For RTOs and ISOs with centralized capacity markets, data on capacity offers as well as capacity market outcomes or designations. This data would include the identity of capacity resources, the amount of procured capacity, and the applicable capacity market price.</P>
        <P>5. Resource output—Data on resource output data used in market settlements. This dataset would include details used in market settlements, including RTO and ISO dispatch instructions (i.e., the output that a dispatched resource is expected to produce in real-time) for energy or ancillary services, or whether resources are operating at self-scheduled output levels, and measured output levels.</P>

        <P>6. Marginal cost estimates—Data on marginal cost estimates; such estimates are typically generated for the potential replacement of supply offers in market power mitigation procedures. This dataset would include all marginal cost estimates that have been developed, and<PRTPAGE P="26681"/>not just those estimates that were used to generate mitigated supply offers. The Commission is seeking only the resulting marginal cost estimates themselves, however, and not the inputs that allow for calculation of those estimates. Further, the Commission is not seeking other operating information regarding individual generators' actual costs, revenues, or profits.</P>
        <P>7. Day-ahead shift factors—Data on shift factors calculated for use in the day-ahead market. This would include generation shift factors, which are factors to be applied to a generator's expected change in output to determine the amount of flow contribution that that change in output will impose on an identified transmission facility or flowgate, and load shift factors, which are factors to be applied to a load's expected change in demand to determine the amount of flow contribution that that change in demand will impose on an identified transmission facility or flowgate. This dataset would not be limited to binding constraints, but should also include all shift factors calculated to address non-binding constraints.</P>
        <P>8. FTR data—Data on FTR transactions that may not be publicly posted in all RTO and ISO markets. Specifically, RTOs and ISOs must provide data detailing how all FTRs and allocated rights were acquired, either through RTO and ISO allocation or auction procedures; data detailing whether the acquired allocation positions were converted from positions that collect auction revenue into positions that collect congestion revenue; and data detailing secondary market transactions to the extent that they are available to the RTO and ISO.</P>
        <P>9. Internal Bilateral Contracts—Data on the settlement of internal bilateral contracts for energy.</P>
        <P>10. Pricing data for interchange transactions—Data on pricing information for scheduled interchanges including eTag IDs, when applicable, in addition to other interchange pricing details and transaction identification. Scheduled interchanges include any transaction between two or more Balancing Authority Areas.</P>
        <P>50. The Commission also proposed that descriptive information, such as market participant names, unique identifiers, pricing points, and other information that the Commission considers necessary and appropriate to understand and analyze the data described in the NOPR would be included in the delivery of these datasets. The Commission noted that much of the data discussed in the NOPR are already collected and stored by the RTOs and ISOs in order to administer their markets.<SU>85</SU>
          <FTREF/>And to the extent that an RTO or ISO does not already collect specific data, the Commission proposed not to require either the collection of such data from market participants or its electronic delivery to the Commission.</P>
        <FTNT>
          <P>
            <SU>85</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,681 at P 14.</P>
        </FTNT>
        <P>51. Finally, the Commission proposed to direct each RTO and ISO to submit a compliance filing within 45 days after the effective date of any final rule in this proceeding, amending its open access transmission tariff to reflect the requirement for the ongoing electronic delivery of data.</P>
        <HD SOURCE="HD3">2. Comments</HD>
        <P>52. Most commenters support the Commission's proposal to require each RTO and ISO to electronically deliver data described in the NOPR as a means to more effectively carry out Commission functions.<SU>86</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>86</SU>SWP at 1-2; NYPSC at 3; PA PUC at 2-10; IRC at 1-2; Powerex § IV.A.; APPA at 6; ISO-NE at 2-3.</P>
        </FTNT>
        <P>53. Several commenters encouraged the Commission to consider requesting additional data.<SU>87</SU>
          <FTREF/>For example, Powerex believes that the following data would aid the Commission in enhancing its market surveillance:<SU>88</SU>
          <FTREF/>(1) Market awards, both in terms of volumes and prices, including all exceptional and out-of-market dispatches; (2) uplift costs per megawatt; and (3) make-whole payments/bid costs recovery payments.</P>
        <FTNT>
          <P>
            <SU>87</SU>Powerex § IV.B.; APPA at 4.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>88</SU>Powerex contends that this data should be made publicly available in order to increase market transparency. Powerex § IV.B., .C.;<E T="03">see also supra</E>§ III.C. (Confidentiality of Data).</P>
        </FTNT>
        <P>54. APPA considers it a substantial shortcoming in the Commission proposal to seek only estimated marginal cost data and not information regarding individual generators' actual costs, revenues, and profits.<SU>89</SU>
          <FTREF/>APPA argues that, without looking at the underlying generator-seller cost data, the Commission cannot “determine whether the average prices charged by a seller are comparable to the average prices that would be charged in a competitive market where no sellers were able to exercise market power.”<SU>90</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>89</SU>APPA at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>90</SU>
            <E T="03">Id.</E>at 5-6 (quoting<E T="03">Lockyer ex rel State of California</E>v.<E T="03">FERC,</E>383 F.3d 1006, 1012-13 (9th Cir. 2004), and<E T="03">Mont Consumer Counsel</E>v.<E T="03">FERC,</E>659 F.3d 910, 919 (9th Cir. 2011)).</P>
        </FTNT>
        <P>55. Several commenters support the Commission's intent to require only data that is collected or stored by each RTO or ISO to be delivered to the Commission.<SU>91</SU>
          <FTREF/>In that vein, ISO-NE and the IRC state that, in certain cases, data requested in the NOPR is either not produced or retained by the RTO or ISO.<SU>92</SU>
          <FTREF/>The IRC notes that for some RTOs and ISOs, such as the MISO, the data may be developed by the MMU.<SU>93</SU>
          <FTREF/>In particular, the IRC notes that certain requested data serving as the basis for market power mitigation may be calculated by the MMU but not transmitted to the RTO or ISO and therefore cannot be supplied by the RTO or ISO. The IRC points out that, in other cases, certain inputs that are not critical to the clearing of the market routinely are not retained.<SU>94</SU>
          <FTREF/>Likewise, ISO-NE states that it does not retain either shift factors calculated to address non-binding constraints or data “flags” that identify which of the alternative market mitigation methods would be used to calculate a reference level at the segment level (as opposed to the block level).<SU>95</SU>
          <FTREF/>ISO-NE also states that it no longer administers a secondary FTR market, so it would not be in a position to deliver this data to the Commission.<SU>96</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>91</SU>PA PUC at 3; EEI/EPSA at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>92</SU>ISO-NE at 4; IRC at 5-6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>93</SU>IRC at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>94</SU>One example is preliminary entries of bids that are subsequently modified by market participants prior to the submission of a final bid and prior to the market close. IRC at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>95</SU>ISO-NE at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>96</SU>
            <E T="03">Id.</E>at 4-5.</P>
        </FTNT>
        <P>56. In order to reflect situations where the Commission is requesting data that is either not produced or retained by the RTO or ISO, the IRC requests that the Commission clarify in the final rule that no RTO or ISO will be required to deliver such data.<SU>97</SU>
          <FTREF/>Specifically, the IRC requests that the Commission clarify that the data to be supplied is that which is used to settle or clear the relevant market and that the Commission need not be provided data—such as non-binding shift factors—that do not influence market outcomes. The IRC further requests that the Commission clarify that it is not directing the RTOs and ISOs to begin tracking incremental changes to the data that they do not currently track.<SU>98</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>97</SU>IRC at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>98</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD3">3. Commission Determination</HD>

        <P>57. The Commission will adopt the proposal in the NOPR to require ongoing electronic delivery of data related to physical and virtual offers and bids, market awards, resource outputs, marginal cost estimates, shift factors, FTRs, internal bilateral contracts, and interchange pricing. In addition, the Commission will require each RTO and ISO to provide data on uplift charges and credits. The Commission concludes that the data specified in this final rule will facilitate the Commission's<PRTPAGE P="26682"/>development and evaluation of its policies and regulations and will enhance Commission efforts to detect anti-competitive or manipulative behavior, or ineffective market rules, thereby helping to ensure just and reasonable rates. Accordingly, we require each RTO and ISO to electronically deliver to the Commission, on an ongoing basis, the data described in this final rule to the extent that each RTO or ISO already collects such data.<SU>99</SU>
          <FTREF/>We also direct each RTO and ISO to submit a compliance filing within 45 days of the effective date of this final rule, amending its open access transmission tariff to reflect the requirement for the ongoing electronic delivery of data. In response to the comments received on the NOPR, we provide the following clarifications.</P>
        <FTNT>
          <P>
            <SU>99</SU>In the event an RTO or ISO begins to collect certain datasets described in this final rule not currently collected, that RTO or ISO thereafter would be expected to deliver such data to the Commission on an ongoing basis.</P>
        </FTNT>
        <P>58. First, we agree with Powerex that uplift charges and credits should be included in this final rule.<SU>100</SU>
          <FTREF/>Upon further consideration, we find this data is important to furthering Commission goals of facilitating market surveillance and the evaluation of policies and regulations. As an example, uplift data may be used to identify instances where bidding strategies might merit examination or investigation. Uplift data may also be used to identify market designs that result in excess uplift charges. Accordingly, we will require RTOs and ISOs to report, consistent with the reporting structures outlined in this final rule, uplift charges and credits to market participants. This dataset would include details used in market settlements concerning uplift charges and credits as well as identification of each relevant market participant and resource.</P>
        <FTNT>
          <P>
            <SU>100</SU>We note that make-whole payments, bid cost recovery payments and details on some exceptional or out of market dispatches would be captured in the datasets electronically delivered to the Commission per the requirements of this final rule.</P>
        </FTNT>
        <P>59. However, we reject Powerex's request to make certain uplift data, along with other data covered by this rule, publicly available. This data may reveal individual market participant bidding strategies and other commercially-sensitive information. Consistent with our discussion earlier in this final rule, we expect that all data that satisfy the requirements of FOIA exemption 4 would be protected from public disclosure.</P>
        <P>60. Second, we agree with the IRC and ISO-NE that there are some data elements not critical to the formation of market outcomes that will not need to be delivered under this final rule. Specifically, the Commission is not requesting the delivery of preliminary entries of bids that are subsequently modified by market participants prior to their submission of a final bid and prior to market closure. In addition, the Commission is seeking shift factor data related to active or binding constraints, not shift factor data associated with non-binding constraints or non-active constraints that is not retained by the RTO or ISO. Also, in response to ISO-NE's comment that it should not be required to deliver information about secondary FTR markets that it no longer administers, we clarify that the Commission does not require delivery of data on secondary markets that are not administered by the RTOs and ISOs or when secondary market transaction data are not provided to the RTO or ISO by market participants.</P>
        <P>61. Third, to the extent the RTO or ISO relies on its MMU to produce or retain some of the requested data, we direct the RTO or ISO either to: (1) Request such data from its MMU, so that the RTO or ISO can deliver it to the Commission; or (2) request its MMU to deliver such data directly to the Commission. For instance, IRC indicates that MISO relies on its MMU to calculate certain requested data that form the basis for market power mitigation that is not delivered to the MISO. Market power mitigation data are critical to the proper functioning of RTO and ISO markets and important for facilitating market surveillance and evaluation of Commission policies and regulations. Therefore, in this example, the Commission expects MISO either to direct its MMU to provide MISO with such data so that MISO can then deliver it to the Commission, or MISO can direct its MMU to provide such data to the Commission.</P>
        <P>62. With respect to tracking and documenting what the IRC terms as “incremental changes” to the data, we clarify that we may require documentation concerning any change in how the data described in this final rule are collected by each RTO and ISO.<SU>101</SU>
          <FTREF/>Such documentation will help the Commission understand and appropriately utilize the data that the RTOs and ISOs are delivering to the Commission. Therefore, we will direct each RTO and ISO to notify Commission staff in writing of any such change as it pertains to data described in this final rule. Commission staff will determine whether the identified change requires the submission of updated documentation.</P>
        <FTNT>
          <P>
            <SU>101</SU>
            <E T="03">See supra</E>PP 43-44.</P>
        </FTNT>
        <P>63. Finally, we disagree with APPA that the Commission should seek not only estimated marginal cost data but also individual generators' actual costs, revenues, and profits. In this final rule, the Commission is undertaking a data collection from the RTOs and ISOs that will enable it to better fulfill its statutory responsibilities. In contrast, information on individual generators' actual costs, revenues, and profits is not currently collected by RTOs and ISOs and to obtain such information would require its collection from market participants. At this time, the Commission will not undertake a separate data collection effort from market participants, as proposed by APPA; that is beyond the scope of this proceeding. Furthermore, to the extent the Commission is concerned that a particular seller may be exercising market power, it may seek additional data from that seller, including some or all of the data specified by APPA.</P>
        <HD SOURCE="HD2">G. Implementation Timeline and Phasing</HD>
        <HD SOURCE="HD3">1. NOPR</HD>
        <P>64. The Commission invited comments with respect to the timeframe for electronic delivery of the data to the Commission. The Commission also invited comments on whether the requirements of the final rule should be implemented in phases and, if so, what a potential phased approach should entail.</P>
        <HD SOURCE="HD3">2. Comments</HD>
        <P>65. Both ISO-NE and the IRC support phased implementation.<SU>102</SU>
          <FTREF/>ISO-NE maintains that full implementation of ongoing electronic delivery of data could be accomplished in about six months following the issuance of the final rule.<SU>103</SU>
          <FTREF/>ISO-NE proposes that phased implementation could involve the following steps: (1) Establish the initial systems needed and transfer methodology; (2) begin with an individual dataset and deliver it to the Commission after three months; and (3) expand functionality incrementally to deliver all requested data sets within six months.<SU>104</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>102</SU>ISO-NE at 6; IRC at 9.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>103</SU>ISO-NE at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>104</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>66. The IRC and EEI/EPSA proffer that a twelve-month timeframe would be appropriate.<SU>105</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>105</SU>IRC at 9; EEI/EPSA at 12.</P>
        </FTNT>

        <P>67. The IRC supports an initial, three-month delivery timeframe for a first, individual dataset but proposes all<PRTPAGE P="26683"/>requested data would be available to the Commission after twelve months of the final rule's effective date.<SU>106</SU>
          <FTREF/>Further, recognizing that there will be a defined deadline, the IRC proposes that “individual [RTOs and ISOs] could work with Commission staff to define a set of deliverable dates for tiers (which need not be defined in the final rule).”<SU>107</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>106</SU>IRC at 9.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>107</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD3">3. Commission Determination</HD>

        <P>68. In response to the requests for additional time to implement the ongoing electronic delivery, the Commission will direct that electronic delivery of all the datasets be fully implemented 210 days after the effective date of this final rule, which is 60 days after publication in the<E T="04">Federal Register</E>. Moreover, we adopt the proposal to implement delivery on a “phased” approach, a suggestion supported by the IRC and ISO-NE. Phased initial delivery will allow the Commission and each RTO and ISO to address data transfer issues more effectively.</P>
        <P>69. Accordingly, we will direct that all RTOs and ISOs implement the ongoing electronic delivery of at least one dataset no later than 45 days after the effective date of this final rule. Unless otherwise determined on a case-by-case basis, this initial delivery would include at least all data relating to supply offers for energy, as discussed and defined in the NOPR.</P>
        <P>70. We will direct that ongoing, electronic delivery of the remaining datasets be phased in gradually, with delivery of all datasets occurring no later than 210 days after the effective date of this final rule. Descriptive information necessary to understand each dataset, such as market participant names, unique identifiers, pricing points, and other information the Commission considers necessary and appropriate to analyze each dataset, should be provided at the same time initial delivery of each applicable dataset begins.</P>
        <P>71. Unless otherwise determined on a case-by-case basis, following the initial delivery of (at least) the data relating to supply offers for energy, in the second phase we will direct that the following datasets be delivered electronically no later than 90 days after the effective date of this final rule: Virtual offers and bids; and demand bids for energy.</P>
        <P>72. Unless otherwise determined on a case-by-case basis, in the third phase we will direct that the following datasets be delivered no later than 150 days after the effective date of this final rule: Marginal cost estimates; energy and ancillary service awards; resource output; internal bilateral contracts; and uplift data.</P>
        <P>73. Finally, unless otherwise determined on a case-by-case basis, in the fourth and final phase that ends 210 days after the effective date of this final rule, we will direct that all remaining datasets be delivered, namely: Day-ahead shift factors; supply offer and demand bids for ancillary services; capacity market offers, designations and prices; pricing data for interchange transactions; and FTR data.</P>
        <HD SOURCE="HD2">H. Ongoing Electronic Delivery</HD>
        <HD SOURCE="HD3">1. NOPR</HD>
        <P>74. The Commission proposed that RTOs and ISOs be required to electronically deliver the requested data to the Commission within seven days after each RTO or ISO creates the datasets in a daily market run or otherwise. For data that are updated less frequently than every day, including capacity market results, estimated marginal costs, and FTR data, each RTO or ISO would be expected to electronically deliver such data within seven days after it is created or updated by the RTO or ISO. The Commission also proposed that, in the event an RTO or ISO makes later corrections to the data (i.e., after the original data has been delivered to the Commission), the RTO or ISO would be expected to electronically deliver the corrected data to the Commission within seven days after the correction has been made. The Commission invited comments with respect to the timeframe in which the data described in this NOPR should be electronically delivered to the Commission.</P>
        <HD SOURCE="HD3">2. Comments</HD>
        <P>75. The IRC believes that the seven-day requirement would be workable, provided that the RTO or ISO with corrected data can deliver the data to the Commission in a format consistent with the manner in which each RTO or ISO stores the data, with minimal modifications.<SU>108</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>108</SU>
            <E T="03">Id.</E>at 6.</P>
        </FTNT>
        <P>76. The IRC interprets the Commission's intent as focused on obtaining data quickly and efficiently, rather than erecting a new compliance program. Towards this end, the IRC requests that the Commission clarify in the final rule that an RTO or ISO will not face compliance penalties in the event that data is not delivered in the specified timeframe, provided that the RTO or ISO is making its best efforts to comply with the rule and provided that the RTO or ISO gives timely notice to the Commission when the RTO or ISO becomes aware that there may be a delay in the delivery of data or some impact on the accuracy or completeness of the data.<SU>109</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>109</SU>
            <E T="03">Id.</E>at 7.</P>
        </FTNT>
        <P>77. Further, the IRC states that the possibility exists that RTOs and ISOs will, on occasion, inadvertently produce or deliver inaccurate, incomplete, or imperfectly formatted data.<SU>110</SU>
          <FTREF/>The IRC requests that the Commission expressly state in the final rule that, unless an error or omission was made to mislead the Commission, the submittal of inaccurate, incomplete, or imperfectly formatted data should not result in a violation of the Commission's regulations or a violation of the RTO's or ISO's tariff.<SU>111</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>110</SU>
            <E T="03">Id.</E>at 10.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>111</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD3">3. Commission Determination</HD>
        <P>78. The Commission will require each RTO and ISO to electronically deliver the specified data to the Commission in a format consistent with the manner in which each RTO and ISO collects this data.<SU>112</SU>
          <FTREF/>The Commission will adopt the proposal in the NOPR that RTOs and ISOs electronically deliver data to the Commission within seven days after each RTO and ISO creates the datasets in a market run or other procedure.<SU>113</SU>
          <FTREF/>For data that are updated less frequently than every day, including capacity market results, estimated marginal costs, and FTR data, each RTO and ISO must electronically deliver that data within seven days after it is created or updated by the RTO or ISO. Each RTO and ISO is required to deliver all data consistent with timelines described elsewhere in this final rule. With respect to any corrections made to the data (i.e., after they have been delivered to the Commission), the RTO or ISO will be expected to electronically deliver the corrected data to the Commission within seven days after the correction has been made and identify whether that correction is adding to, changing, or deleting data previously delivered.<SU>114</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>112</SU>
            <E T="03">See supra</E>§ III.D (Data Formatting).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>113</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,681 at P 38.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>114</SU>
            <E T="03">See supra</E>note 75.</P>
        </FTNT>

        <P>79. We cannot make a blanket statement, as requested by the IRC, that the submission of inaccurate, incomplete, or imperfectly formatted data will not result in a violation of the Commission's regulations or the RTO and ISO tariff. However, as a general matter, the Commission does not intend<PRTPAGE P="26684"/>to penalize RTOs and ISOs for infrequent, minor errors in data reporting. Moreover, as stated in the Revised Policy Statement on Enforcement, the Commission's Enforcement staff “frequently exercises prosecutorial discretion to resolve minor infractions with voluntary compliance measures rather than with penalties.”<SU>115</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>115</SU>
            <E T="03">Enforcement of Statutes, Regulations, and Orders,</E>123 FERC ¶ 61,156, at P 9 (2008).</P>
        </FTNT>
        <HD SOURCE="HD2">I. Future Specifications and Modifications of the Data and the Process for Delivery</HD>
        <HD SOURCE="HD3">1. NOPR</HD>
        <P>80. The Commission stated that the data it is proposing to receive would be limited to physical and virtual offers and bids, market awards, resource outputs, marginal cost estimates, shift factors, FTRs, internal bilateral contracts, and interchange pricing. The Commission also stated that these datasets would include descriptive information such as market participant names, unique identifiers, pricing points, and other information the Commission considers necessary and appropriate to understand and analyze the data described in this NOPR. However, the Commission recognized that markets are not static and, as markets continue to evolve, the Commission may initiate a new rulemaking proceeding in the future to reassess the data necessary for its market monitoring and surveillance efforts and for its policy and decision-making needs.</P>
        <HD SOURCE="HD3">2. Comments</HD>
        <P>81. The IRC states that the proposed regulation itself does not specify the data that the RTOs and ISOs will be required to deliver, nor does the regulation specify any process by which the Commission may alter the obligations to provide data.<SU>116</SU>
          <FTREF/>The IRC further states that, because the RTOs and ISOs need time to make modifications to the processes they employ in response to a change in the data delivery obligations, the Commission should specify the process it will use to modify the required data, data format, and/or the delivery mechanism.<SU>117</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>116</SU>IRC at 11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>117</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD3">3. Commission Determination</HD>
        <P>82. The regulatory text adopted by this final rule sets forth the obligation for RTOs and ISOs to provide data to the Commission. The narrative preamble to that regulatory text, i.e., the final rule, provides additional, specific information about the datasets and details about the electronic delivery formatting, procedures, and security measures.</P>
        <P>83. As to future changes in reporting, the Commission anticipates that changes in the datasets to be provided will be made through a rulemaking proceeding.</P>
        <HD SOURCE="HD2">J. Technical Conference</HD>
        <HD SOURCE="HD3">1. Comments</HD>
        <P>84. In their joint comments, EEI/EPSA encourage the Commission to convene one or more technical conferences to address concerns related to this rulemaking and other Commission data collection efforts.<SU>118</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>118</SU>EEI/EPSA at 12.</P>
        </FTNT>
        <HD SOURCE="HD3">2. Commission Determination</HD>
        <P>85. We deny EEI/EPSA's request to hold a technical conference. EEI/EPSA have not raised any issues that have not been adequately addressed in the rulemakings and that would otherwise require a technical conference.</P>
        <HD SOURCE="HD1">IV. Information Collection Statement</HD>
        <P>86. The collections of information contained in this final rule are being submitted to the Office of Management and Budget (OMB) for review under section 3507(d) of the Paperwork Reduction Act of 1995, 44 U.S.C. 3507(d). Upon approval of a collection of information, OMB will assign an OMB control number and an expiration date. Respondents subject to the filing requirements of a rule will not be penalized for failing to respond to these collections of information if the collections of information do not display a valid OMB control number.</P>
        <P>87. The final rule does not require market participants other than the RTOs and ISOs to report information to the Commission.</P>
        <P>88. The Commission did not receive any comments regarding the burden estimates in the proposed rule and uses the same estimates here.</P>
        <P>89. In this final rule, the Commission did deviate from the proposed rule in several instances. Specifically, the Commission included an additional dataset, uplift, in this final rule. Any increase in burden associated with the inclusion of uplift data, however, should be offset by the decision in this final rule not to require consistent formatting by the RTOs and ISOs.</P>
        <P>90. In addition, in this final rule, the Commission also clarifies that, in very limited instances, individual datasets that the Commission is requesting may be produced or retained by the MMUs. The Commission directed each RTO and ISO either to: (1) Request such data from its MMU, so that the RTO or ISO can deliver such data to the Commission; or (2) request its MMU to deliver such data directly to the Commission. Any burden associated with the delivery of such data is counted as burden on the RTO or ISO, as each RTO or ISO is responsible for such delivery to the Commission, and not the MMU.</P>
        <P>91. The burden imposed by this rule on the RTOs and ISOs is captured through the estimates below.</P>
        <GPOTABLE CDEF="s50,11,11,11,11,11,11,11" COLS="8" OPTS="L2,tp0,i1">
          <BOXHD>
            <CHED H="1">Data collection, FERC-921</CHED>
            <CHED H="1">Number of respondents</CHED>
            <CHED H="1">Implementing burden</CHED>
            <CHED H="2">Burden<LI>hrs. per</LI>
              <LI>respondent</LI>
            </CHED>
            <CHED H="2">Cost per<LI>respondent</LI>
            </CHED>
            <CHED H="1">Annual recurring operating burden</CHED>
            <CHED H="2">Burden<LI>hrs. per</LI>
              <LI>respondent</LI>
            </CHED>
            <CHED H="2">Cost per<LI>respondent</LI>
            </CHED>
            <CHED H="1">Average annual burden<LI>(implementation cost averaged over 3 yrs.)</LI>
            </CHED>
            <CHED H="2">Burden<LI>hrs. for all</LI>
              <LI>respondents</LI>
            </CHED>
            <CHED H="2">Cost<LI>for all</LI>
              <LI>respondents</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Compliance filing</ENT>
            <ENT>6</ENT>
            <ENT>7</ENT>
            <ENT>$1,750</ENT>
            <ENT/>
            <ENT/>
            <ENT>14</ENT>
            <ENT>$3,500</ENT>
          </ROW>
          <ROW RUL="s,">
            <ENT I="01">Web-Based Delivery</ENT>
            <ENT>6</ENT>
            <ENT>1,040</ENT>
            <ENT>$100,864</ENT>
            <ENT>40</ENT>
            <ENT>$3,879</ENT>
            <ENT>2,320</ENT>
            <ENT>225,003</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Grand Total, Average Annual Estimates</ENT>
            <ENT>6</ENT>
            <ENT/>
            <ENT/>
            <ENT/>
            <ENT/>
            <ENT>2,334</ENT>
            <ENT>228,503</ENT>
          </ROW>
        </GPOTABLE>

        <P>92. The Commission recognizes that there will be an initial implementation burden associated with providing the Commission with RTO and ISO data. This includes submitting a compliance filing to the Commission, which the<PRTPAGE P="26685"/>Commission estimates as a burden of 7 hours per RTO and ISO, and implementing a process to automatically upload data to an SFTP site for Commission use (including development, testing and production). The Commission estimates a burden of 1,040 hours per RTO and ISO for the development, testing and production of an automated process to provide the Commission with the data required in this final rule. In this regard, though, RTO and ISO markets have already developed capabilities necessary to handle RTO and ISO data in an automated manner. For instance, through their Open Access Same-time Information Systems (OASIS), RTOs and ISOs already make certain market data publically available using automated procedures. Likewise, some RTOs and ISOs have developed procedures similar to those contained in this final rule to deliver data to their MMUs.</P>
        <P>93. For the recurring effort involved in electronically delivering RTO and ISO data to the Commission, the Commission anticipates that the additional burden associated with this rule will be minimal. Any recurring burden would be associated with addressing updates to RTO and ISO data as the data that they process changes and due to occasional errors in the data handling or data upload process.</P>
        <P>
          <E T="03">Information Collection Costs:</E>The Commission has estimated the cost of compliance per RTO and ISO to be $102,614 in the initial year of implementation and $3,879 in subsequent years. The Commission expects that the compliance filing will be completed by RTO and ISO legal staff and has estimated an hourly rate at $250/hour. The Commission estimates that a variety of staff, including legal, database administrators and IT and information security specialists, will be required to electronically deliver to the Commission the RTO and ISO data identified in this final rule. The Commission has estimated the average hourly cost for this task to be $96.98/hour (including legal staff at $250/hour, information systems manager at $105.35/hour, database administrator at $55.61/hour, and information security analyst at $57.67/hour).<SU>119</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>119</SU>Hourly average wage is an average and was calculated using Bureau of Labor Statistics (BLS), Occupational Employment Statistics data for May 2010 (at<E T="03">http://www.bls.gov/oes/</E>) for the database administrator and information security analysts. The average hourly figure for legal staff and information systems manager is a composite from BLS and other resources. The following weightings were applied to estimate the average hourly cost: legal staff (<FR>1/6</FR>), information systems manager (<FR>1/6</FR>), database administrator (<FR>1/3</FR>), and information security analyst (<FR>1/3</FR>).</P>
        </FTNT>
        <P>
          <E T="03">Title:</E>FERC-921,<SU>120</SU>
          <FTREF/>Enhancement of Electricity Market Surveillance and Analysis.</P>
        <FTNT>
          <P>
            <SU>120</SU>OATT compliance filings (like the one-time compliance filing here) are normally included under FERC-516 (OMB Control No. 1902-0096). However, the reporting requirements (including the compliance filing) contained in this final rule in Docket No. RM11-17 will be covered by the FERC-921.</P>
        </FTNT>
        <P>
          <E T="03">Action:</E>New Collection.</P>
        <P>
          <E T="03">OMB Control No.:</E>1902-0257.</P>
        <P>
          <E T="03">Respondents for this Rulemaking:</E>RTOs and ISOs.</P>
        <P>
          <E T="03">Frequency of Information:</E>Initial implementation, compliance filing, and automated daily updates.</P>
        <P>
          <E T="03">Necessity of Information:</E>As wholesale electricity markets continue to develop and evolve, new opportunities arise for anti-competitive or manipulative behavior. The Commission's market monitoring and surveillance capabilities and associated data requirements must keep pace with market developments and evolve along with the markets. The data requirement set forth in this final rule will allow the Commission to more effectively identify and address such behavior; to identify ineffective market rules; to better inform Commission policies and regulations; and thus to help ensure just and reasonable rates.</P>
        <P>
          <E T="03">Internal Review:</E>The Commission has made a preliminary determination that the revisions are necessary to keep pace with ever-changing possibilities for anti-competitive or manipulative behavior and to better inform Commission policies and regulations, and thus to ensure that rates are just and reasonable. The Commission has assured itself, by means of its internal review, that there is specific, objective support for the burden estimate associated with the information requirements.</P>

        <P>94. Interested persons may obtain information on the reporting requirements by contacting the Federal Energy Regulatory Commission, Office of the Executive Director, 888 First Street NE., Washington, DC 20426 [Attention: Ellen Brown, email:<E T="03">DataClearance@ferc.gov,</E>phone: (202) 502-8663, fax: (202) 273-0873].</P>

        <P>95. Comments concerning the information collections required in this Final Rule and the associated burden estimates should be sent to the Office of Management and Budget, Office of Information and Regulatory Affairs, Washington, DC 20503 [Attention: Desk Officer for the Federal Energy Regulatory Commission]. For security reasons, comments should be sent by email to OMB at the following email address:<E T="03">oira_submission@omb.eop.gov.</E>Please reference FERC-921 and the docket number of this rulemaking (Docket No. RM11-17-000) in your submission.</P>
        <HD SOURCE="HD1">V. Environmental Analysis</HD>
        <P>96. 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>121</SU>
          <FTREF/>The Commission has categorically excluded certain actions from these requirements as not having a significant effect on the human environment.<SU>122</SU>
          <FTREF/>The actions proposed here fall within a categorical exclusion in the Commission's regulations, i.e., they involve information gathering, analysis, and dissemination.<SU>123</SU>
          <FTREF/>Therefore, environmental analysis is unnecessary and has not been performed.</P>
        <FTNT>
          <P>
            <SU>121</SU>
            <E T="03">Regulations Implementing the National Environmental Policy Act,</E>Order No. 486, 52 FR 47,897 (Dec. 17, 1987), FERC Stats. &amp; Regs. ¶ 30,783 (1987).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>122</SU>18 CFR 380.4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>123</SU>
            <E T="03">See</E>18 CFR 380.4(a)(5).</P>
        </FTNT>
        <HD SOURCE="HD1">VI. Regulatory Flexibility Act</HD>
        <P>97. The Regulatory Flexibility Act of 1980 (RFA)<SU>124</SU>
          <FTREF/>generally requires a description and analysis of final rules that will have significant economic impact on a substantial number of small entities. The RFA mandates consideration of regulatory alternatives that accomplish the stated objectives of a rule and that minimize any significant economic impact on a substantial number of small entities. The Small Business Administration's (SBA) Office of Size Standards is responsible for the definition of a small business.<SU>125</SU>
          <FTREF/>The SBA has established a size standard for utilities, stating that a firm is small if, including its affiliates, it is primarily engaged in the transmission, generation and/or distribution of electric energy for sale and its total electric output for the preceding twelve months did not exceed four million megawatt hours.<SU>126</SU>
          <FTREF/>RTOs and ISOs are not small entities, and they are the only entities impacted directly by this final rule.<SU>127</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>124</SU>5 U.S.C. 601-612.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>125</SU>13 CFR 121.101.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>126</SU>13 CFR 121.201 (Sector 22, Utilities).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>127</SU>As noted in the final rule, an MMU may be directed by the RTO or ISO to provide data to the RTO or ISO, or directly to the Commission. Any impact on the MMU is considered part of the impact on RTOs and ISOs and does not affect the analysis performed in this section.</P>
        </FTNT>
        <P>98. CAISO is a nonprofit organization with over 54,000 megawatts of capacity and over 25,000 circuit miles of transmission lines.</P>

        <P>99. NYISO is a nonprofit organization that oversees wholesale electricity<PRTPAGE P="26686"/>markets serving 19.2 million customers. NYISO manages a nearly 11,000-mile network of high-voltage transmission lines.</P>
        <P>100. PJM is comprised of more than 700 members including power generators, transmission owners, electricity distributers, power marketers, and large industrial customers and serves 13 states and the District of Columbia.</P>
        <P>101. SPP is comprised of 63 members serving 6.2 million households in nine states and has 48,930 miles of transmission lines.</P>
        <P>102. MISO is a nonprofit organization with over 145,000 megawatts of installed generation. MISO has over 57,600 miles of transmission lines and serves 13 states and one Canadian province.</P>
        <P>103. ISO-NE is a regional transmission organization serving six states in New England. The system is comprised of more than 8,000 miles of high-voltage transmission lines and over 300 generators.</P>
        <P>104. The Commission certifies that this rule will not have a significant economic impact on a substantial number of small entities, and therefore no regulatory flexibility analysis is required.</P>
        <HD SOURCE="HD1">VII. Document Availability</HD>

        <P>105. 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 the Commission's Home Page (<E T="03">http://www.ferc.gov</E>) and in the Commission's Public Reference Room during normal business hours (8:30 a.m. to 5:00 p.m. Eastern time) at 888 First Street NE., Room 2A, Washington, DC 20426.</P>
        <P>106. From the Commission'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>107. User assistance is available for eLibrary and the the Commission's Web site during normal business hours from FERC Online Support at 202-502-6652 (toll free at 1-866-208-3676) or email at<E T="03">ferconlinesupport@ferc.gov,</E>or the Public Reference Room at (202) 502-8371, TTY (202)502-8659. Email the Public Reference Room at<E T="03">public.referenceroom@ferc.gov.</E>
        </P>
        <HD SOURCE="HD1">VIII. Effective Date and Congressional Notification</HD>
        <P>108. These regulations are effective July 6, 2012. The Commission has determined, with the concurrence of the Administrator of the Office of Information and Regulatory Affairs of OMB, that this ruleis not a “major rule” as defined in section 351 of the Small Business Regulatory Enforcement Fairness Act of 1996.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 18 CFR Part 35</HD>
          <P>Electric power rates, Electric utilities, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        <SIG>
          <P>By the Commission.</P>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
        
        <P>In consideration of the foregoing, the Commission amends Part 35, Chapter I, Title 18, Code of Federal Regulations, as follows.</P>
        <REGTEXT PART="35" TITLE="18">
          <PART>
            <HD SOURCE="HED">PART 35—FILING OF RATE SCHEDULES AND TARIFFS</HD>
          </PART>
          <AMDPAR>1. The authority citation for Part 35 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>16 U.S.C 791a-825r, 2601-2645; 31 U.S.C. 9701; 42 U.S.C. 7101-7352.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="35" TITLE="18">
          <AMDPAR>2. In § 35.28, paragraphs (g)(4) through (g)(7) are redesignated as paragraphs (g)(5) through (g)(8) and a new paragraph (g)(4) is added to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 35.28.</SECTNO>
            <SUBJECT>Non-discriminatory open access transmission tariff.</SUBJECT>
            <STARS/>
            <P>(g) * * *</P>
            <P>(4)<E T="03">Electronic delivery of data.</E>Each Commission-approved regional transmission organization and independent system operator must electronically deliver to the Commission, on an ongoing basis and in a form and manner consistent with its own collection of data and in a form and manner acceptable to the Commission, data related to the markets that the regional transmission organization or independent system operator administers.</P>
            <STARS/>
            <NOTE>
              <HD SOURCE="HED">Note:</HD>
              <P>The following appendix will not be published in the Code of Federal Regulations.</P>
            </NOTE>
            <HD SOURCE="HD1">Appendix A</HD>
            <HD SOURCE="HD1">Commenters on the NOPR</HD>
            <FP SOURCE="FP-1">American Public Power Association (APPA)</FP>
            <FP SOURCE="FP-1">California Department of Water Resources State Water Project (SWP)</FP>
            <FP SOURCE="FP-1">Cogeneration Association of California and the Energy Producers and Users Coalition (CAC/EPUC)</FP>
            <FP SOURCE="FP-1">Edison Electric Institute and the Electric Power Supply Association (EEI/EPSA)</FP>
            <FP SOURCE="FP-1">ISO New England Inc. (ISO-NE)</FP>
            <FP SOURCE="FP-1">ISO/RTO Council (IRC)</FP>
            <FP SOURCE="FP-1">New York Public Service Commission (NYPSC)</FP>
            <FP SOURCE="FP-1">Pennsylvania Public Utility Commission (PA PUC)</FP>
            <FP SOURCE="FP-1">Powerex Corp. (Powerex)</FP>
          </SECTION>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9847 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <CFR>18 CFR Part 40</CFR>
        <DEPDOC>[Docket No. RM11-18-000; Order No. 762]</DEPDOC>
        <SUBJECT>Transmission Planning Reliability Standards</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Energy Regulatory Commission, DOE.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Under section 215 of the Federal Power Act, the Federal Energy Regulatory Commission remands proposed Transmission Planning (TPL) Reliability Standard TPL-002-0b, submitted by the North American Electric Reliability Corporation (NERC), the Commission-certified Electric Reliability Organization. The proposed Reliability Standard includes a provision that allows for planned load shed in a single contingency provided that the plan is documented and alternatives are considered and vetted in an open and transparent process. The Commission finds that this provision is vague, unenforceable and not responsive to the previous Commission directives on this matter. Accordingly, the Final Rule remands NERC's proposal as unjust, unreasonable, unduly discriminatory or preferential, and not in the public interest.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule will become effective July 6, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number by any of the following methods:</P>
          <P>•<E T="03">Agency Web Site: http://www.ferc.gov.</E>Documents created electronically using word processing software should be filed in native applications or print-to-PDF format and not in a scanned format.</P>
          <P>•<E T="03">Mail/Hand Delivery:</E>Commenters unable to file comments electronically must mail or hand deliver comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street NE., Washington, DC 20426.</P>
        </ADD>
        <FURINF>
          <PRTPAGE P="26687"/>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P/>

          <FP SOURCE="FP-1">Eugene Blick (Technical Information), Office of Electric Reliability, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, Telephone: (202) 502-8066,<E T="03">Eugene.Blick@ferc.gov.</E>
          </FP>

          <FP SOURCE="FP-1">Robert T. Stroh (Legal Information), Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, Telephone: (202) 502-8473,<E T="03">Robert.Stroh@ferc.gov.</E>
          </FP>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        
        <EXTRACT>
          <HD SOURCE="HD1">139 FERC ¶ 61,060</HD>
          <FP SOURCE="FP-1">
            <E T="03">Before Commissioners:</E>Jon Wellinghoff, Chairman; Philip D. Moeller, John R. Norris, and Cheryl A. LaFleur.</FP>
        </EXTRACT>
        
        <HD SOURCE="HD1">Final Rule</HD>
        <DATE>Issued April 19, 2012.</DATE>
        <P>1. Under section 215(d) of the Federal Power Act,<SU>1</SU>
          <FTREF/>the Commission remands proposed Transmission Planning (TPL) Reliability Standard TPL-002-0b, submitted by the North American Electric Reliability Corporation (NERC), the Commission-certified Electric Reliability Organization. The proposed Reliability Standard includes a provision that allows for planned load shed in a single contingency provided that the plan is documented and alternatives are considered and vetted in an open and transparent process.<SU>2</SU>
          <FTREF/>The Commission finds that this provision is vague, unenforceable and not responsive to the previous Commission directives on this matter. Accordingly, the Final Rule remands NERC's proposal as unjust, unreasonable, unduly discriminatory or preferential, and not in the public interest. We require NERC to utilize its Expedited Reliability Standards Development Process to develop timely modifications to TPL-002-0b, Table 1 footnote `b' in response to our remand.<SU>3</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>1</SU>16 U.S.C. 824o(d)(4) (2006).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>NERC filed a petition seeking approval of Table 1, footnote `b' of four Reliability Standards: Transmission Planning: TPL-001-1—System Performance Under Normal (No Contingency) Conditions (Category A), TPL-002-1b—System Performance Following Loss of a Single Bulk Electric System Element (Category B), TPL-003-1a—System Performance Following Loss of Two or More Bulk Electric System Elements (Category C), and TPL-004-1—System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Elements (Category D). While footnote `b' appears in all four of the above referenced TPL Reliability Standards, its relevance and practical applicability is limited to TPL-002-0a.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>NERC Rules of Procedure, Appendix 3A, Standard Processes Manual at 34 (effective January 31, 2012).</P>
        </FTNT>
        <HD SOURCE="HD1">I. Background</HD>
        <P>2. Section 215 of the FPA requires a Commission-certified Electric Reliability Organization (ERO) to develop mandatory and enforceable Reliability Standards, which are subject to Commission review and approval. Approved Reliability Standards are enforced by the ERO, subject to Commission oversight, or by the Commission independently. On March 16, 2007, the Commission issued Order No. 693, approving 83 of the 107 Reliability Standards filed by NERC, including Reliability Standard TPL-002-0.<SU>4</SU>
          <FTREF/>In addition, pursuant to section 215(d)(5) of the FPA,<SU>5</SU>
          <FTREF/>the Commission directed NERC to develop modifications to 56 of the 83 approved Reliability Standards, including footnote `b' of Reliability Standard TPL-002-0.<SU>6</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>4</SU>
            <E T="03">Mandatory Reliability Standards for the Bulk-Power System,</E>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242,<E T="03">order on reh'g,</E>Order No. 693-A, 120 FERC ¶ 61,053 (2007).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>5</SU>16 U.S.C. 824o(d)(5)(2006).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>6</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1797.</P>
        </FTNT>
        <HD SOURCE="HD2">A. Transmission Planning (TPL) Reliability Standards</HD>
        <P>3. Currently-effective Reliability Standard TPL-002-0b addresses Bulk-Power System planning and related transmission system performance for single element contingency conditions. Requirement R1 of TPL-002-0b requires that each planning authority and transmission planner “demonstrate through a valid assessment that its portion of the interconnected transmission system is planned such that the network can be operated to supply projected customer demands and projected firm transmission services, at all demand levels over the range of forecast system demands, under the contingency conditions as defined in Category B of Table I.”<SU>7</SU>
          <FTREF/>Table I identifies different categories of contingencies and allowable system impacts in the planning process. With regard to system impacts, Table I further provides that a Category B (single) contingency must not result in cascading outages, loss of demand or curtailed firm transfers, system instability or exceeded voltage or thermal limits. With regard to loss of demand, current footnote `b' of Table 1 states:</P>
        <FTNT>
          <P>
            <SU>7</SU>Reliability Standard TPL-002-0a, Requirement R1.</P>
        </FTNT>
        
        <EXTRACT>
          <P>Planned or controlled interruption of electric supply to radial customers or some local Network customers, connected to or supplied by the Faulted element or by the affected area, may occur in certain areas without impacting the overall reliability of the interconnected transmission systems. To prepare for the next contingency, system adjustments are permitted, including curtailments of contracted Firm (non-recallable reserved) electric power Transfers.</P>
        </EXTRACT>
        
        <HD SOURCE="HD2">B. Order No. 693 Directive</HD>
        <P>4. In Order No. 693, the Commission stated that it believes that the transmission planning Reliability Standard should not allow an entity to plan for the loss of non-consequential firm load in the event of a single contingency.<SU>8</SU>
          <FTREF/>The Commission directed the ERO to develop certain modifications, including a clarification of Table 1, footnote `b.'</P>
        <FTNT>
          <P>
            <SU>8</SU>
            <E T="03">See</E>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1794.</P>
        </FTNT>
        <P>5. In a subsequent clarifying order, the Commission stated that it believed that a regional difference, or a case-specific exception process that can be technically justified, to plan for the loss of firm service would be acceptable in limited circumstances.<SU>9</SU>
          <FTREF/>Specifically, the Commission stated that “a regional difference, or a case-specific exception process that can be technically justified, to plan for the loss of firm service at the fringes of various systems would be an acceptable approach.”<SU>10</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>9</SU>
            <E T="03">Mandatory Reliability Standards for the Bulk Power System,</E>131 FERC ¶ 61,231, at P 21 (2010) (June 2010 Order).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD2">C. NERC Petition</HD>
        <P>6. On March 31, 2011, NERC filed a petition seeking approval of its proposal to revise and clarify footnote `b' “in regard to load loss following a single contingency.”<SU>11</SU>
          <FTREF/>NERC stated that it did not eliminate the ability of an entity to plan for the loss of non-consequential load in the event of a single contingency but drafted a footnote that, according to NERC, “meets the Commission's directive while simultaneously meeting the needs of industry and respecting jurisdictional bounds.”<SU>12</SU>
          <FTREF/>NERC stated that its proposed footnote `b' establishes the requirements for the limited circumstances when and how an entity can plan to interrupt Firm Demand for Category B contingencies. According to NERC, the provision allows for planned interruption of Firm Demand when “subject to review in an open and transparent stakeholder process.”<SU>13</SU>
          <FTREF/>NERC's proposed footnote `b' states:</P>
        <FTNT>
          <P>
            <SU>11</SU>NERC Petition at 10.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>12</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>13</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        
        <EXTRACT>

          <P>An objective of the planning process should be to minimize the likelihood and magnitude of interruption of firm transfers or Firm Demand following Contingency events. Curtailment of firm transfers is allowed when<PRTPAGE P="26688"/>achieved through the appropriate redispatch of resources obligated to re-dispatch, where it can be demonstrated that Facilities, internal and external to the Transmission Planner's planning region, remain within applicable Facility Ratings and the re-dispatch does not result in the shedding of any Firm Demand. It is recognized that Firm Demand will be interrupted if it is: (1) directly served by the Elements removed from service as a result of the Contingency, or (2) Interruptible Demand or Demand-Side Management Load. Furthermore, in limited circumstances Firm Demand may need to be interrupted to address BES performance requirements. When interruption of Firm Demand is utilized within the planning process to address BES performance requirements, such interruption is limited to circumstances where the use of Demand interruption are documented, including alternatives evaluated; and where the Demand interruption is subject to review in an open and transparent stakeholder process that includes addressing stakeholder comments.</P>
        </EXTRACT>
        
        <P>7. NERC supplemented the filing on June 7, 2011, in response to a Commission deficiency letter. NERC explained that “the approach proposed in footnote `b' is equally efficient because many of the stakeholder processes that will be used in footnote `b' planning decisions are already in place, as implemented by FERC in Order No. 890 and in state regulatory jurisdictions.”<SU>14</SU>
          <FTREF/>NERC also pointed to state public utility commission processes or processes existing in local jurisdictions that address transmission planning issues that could serve to provide a case-specific review of the planned interruption of Firm Demand. According to NERC, such processes would more likely engage the appropriate local-level decision-makers and policy-makers.</P>
        <FTNT>
          <P>
            <SU>14</SU>NERC Data Response at 4.</P>
        </FTNT>
        <P>8. With respect to review and oversight by NERC and the Regional Entities, NERC submitted that an ERO-specific process would place the ERO in the position of managing and actively participating in a planning process, which conflicts with its role as the compliance monitor and enforcement authority. NERC also stated that neither the ERO nor the Regional Entities will review decisions regarding planned interruptions. Their role will be limited to reviewing whether the registered entity participated in a stakeholder process when planning to interrupt Firm Demand. NERC explained that Regional Entities will have oversight after-the-fact by auditing the entity's implementation of footnote `b' to determine if the entity planned on interrupting Firm Demand and whether the decision by the entity to rely on planned interruption of Firm Demand was vetted through the stakeholder process and qualified as one of the situations identified in footnote `b.'</P>
        <P>9. Furthermore, NERC stated that an objective of the planning process should be to minimize the likelihood and magnitude of planned Firm Demand interruptions. NERC contended that, due to the wide variety of system configurations and regulatory compacts, it is not feasible for the ERO to develop a one-size-fits-all criterion for limiting the planned firm load interruptions for Category B events. According to NERC, the standards drafting team evaluated setting a certain magnitude of planned interruption of Firm Demand, but there was no analytical data to support a single value, and it would be viewed as arbitrary.</P>
        <HD SOURCE="HD2">D. Notice of Proposed Rulemaking</HD>
        <P>10. On October 20, 2011, the Commission issued a Notice of Proposed Rulemaking (NOPR<SU>15</SU>
          <FTREF/>) proposing to remand NERC's proposal to modify footnote `b.' In the NOPR, the Commission stated that it believed that NERC's proposal does not meet the directives in Order No. 693 and the June 2010 Order and does not clarify or define the circumstances in which an entity can plan to interrupt Firm Demand for a single contingency. The Commission expressed concern that the procedural and substantive parameters of NERC's proposed stakeholder process are too undefined to provide assurances that the process will be effective in determining when it is appropriate to plan for interrupting Firm Demand, does not contain NERC-defined criteria on circumstances to determine when an exception for planned interruption of Firm Demand is permissible, and could result in inconsistent results in implementation. The NOPR stated that the proposed footnote effectively turns the processes into a reliability standards development process outside of NERC's existing procedures. Furthermore, the NOPR stated that regardless of the process used, the result could lead to inconsistent reliability requirements within and across reliability regions. While the Commission recognized that some variation among regions or entities is reasonable, there are no technical or other criteria to determine whether varied results are arbitrary or based on meaningful distinctions.</P>
        <FTNT>
          <P>
            <SU>15</SU>
            <E T="03">Transmission Planning Reliability Standards,</E>Notice of Proposed Rulemaking, 76 FR 66229 (Oct. 20, 2011), FERC Stats. &amp; Regs. ¶ 32,683 (2011).</P>
        </FTNT>
        <P>11. The Commission proposed to provide further guidance on acceptable approaches to footnote `b' and sought comment on certain options for revising footnote `b', as well as other potential options to solve the concerns outlined in the NOPR. In response to the NOPR, comments were filed by seventeen interested parties.<SU>16</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>16</SU>NERC, The Edison Electric Institute (EEI), American Public Power Association (APPA), National Association of Regulatory Utility Commissioners (NARUC), ITC Holdings Corp. (ITC), Manitoba Hydro, California Department of Water Resources State Water Project (California SWP) Hydro One Networks, Inc and the Ontario Independent Electricity System Operator (Hydro One and IESO), Duke Energy Corporation (Duke), New York State Public Service Commission (NYPSC), Bonneville Power Administration (BPA), Kansas City Power &amp; Light Company and KCP&amp;L Greater Missouri Operations Company (KCPL), Midwest Independent System Operator, Inc. (MISO), Public Utility District No. 1 of Snohomish County, Washington (Snohomish), Transmission Access Policy Study Group (TAPS), Powerex Corp. (Powerex), and Florida Reliability Coordinating Council (FRCC).</P>
        </FTNT>
        <HD SOURCE="HD1">II. Discussion</HD>
        <P>12. For the reasons discussed below, the Commission concludes that NERC's proposed TPL-002-0b does not meet the Commission's Order No. 693 directives, nor is it an equally effective and efficient alternative. Further, the Commission finds that the proposal is vague, potentially unenforceable and may lack safeguards to produce consistent results. On this basis, the Commission remands the proposal to NERC as unjust, unreasonable, unduly discriminatory or preferential and not in the public interest. Below, the Commission also provides guidance on acceptable approaches to footnote `b.'</P>
        <P>13. The Commission adopts the proposed NOPR finding that the footnote `b' process lacks adequate parameters. The Reliability Standard requires that, when planning to interrupt Firm Demand, the Firm Demand interruption must be “subject to review in an open and transparent stakeholder process that includes addressing stakeholder comments.”<SU>17</SU>
          <FTREF/>Without meaningful substantive parameters governing the stakeholder process, the enforceability of this obligation by NERC and the Regional Entities would be limited to a review to ensure only that a stakeholder process occurred. As NERC explained, Regional Entities' involvement is limited to after-the-fact oversight by auditing the entity's implementation of footnote `b' to determine if the entity planned on interrupting Firm Demand and whether the decision by the entity to rely on planned interruption of Firm Demand was vetted through the stakeholder process and qualified as one of the situations identified in footnote `b.'<SU>18</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>17</SU>NERC Petition at 10.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>18</SU>NERC Data Response at 7-9.</P>
        </FTNT>
        <PRTPAGE P="26689"/>
        <P>14. Further, the NERC proposal leaves undefined the circumstances in which it is allowable to plan for Firm Demand to be interrupted in response to a Category B contingency. The Commission believes that proposed footnote `b' could be used as a means to override the reliability objective and system performance requirements of the TPL Reliability Standard without any technical or other criteria specified to determine when planning to interrupt Firm Demand would be allowable, and without violating any of the requirements of the TPL Reliability Standard. The TPL Reliability Standard requires that a planner demonstrate through a valid assessment that the transmission system is planned and can be operated to supply projected Firm Demand at all demand levels over a range of forecasted system demands.<SU>19</SU>
          <FTREF/>In addition, a planner must consider all single contingencies under Table 1, Category B and demonstrate system performance.<SU>20</SU>
          <FTREF/>For single contingency events where system performance is not met, a planner must provide a written summary of its plans to achieve system performance including implementation schedules, in service dates of facilities and implementation lead times.<SU>21</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>19</SU>Reliability Standard TPL-002-0b, Requirement R1.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>20</SU>Reliability Standard TPL-002-0b, Requirement R1.3.7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>21</SU>Reliability Standard TPL-002-0b, Requirement R2.</P>
        </FTNT>
        <P>15. However, if system performance is not met for any single contingency event(s) under NERC's proposed footnote `b,' a planner could plan to interrupt some portion of Firm Demand to meet system performance requirements thereby overriding the performance requirements of the TPL Reliability Standard. For example, if a planner determines during its annual assessment that for a single bulk-power system transformer contingency other bulk-power system elements would exceed their thermal ratings, a planner would have authority under the standard to plan to interrupt Firm Demand to relieve the exceeded thermal ratings of the bulk-power system elements rather than planning the system to withstand such a single contingency and avoid shedding firm load as the performance requirements of the TPL Reliability Standard require. Therefore, without articulating some bounds on the use of the planned shedding of Firm Demand, there could be instances of multiple exceptions that could affect the robustness of the system. Further, contrary to commenters contentions, NERC's proposal, for example, has no provision to evaluate this cumulative effect of the individual decisions to shed firm.<SU>22</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>22</SU>BPA Comments at 5 (“The reasons for interrupting Firm Demand would be documented in studies and demonstrate that there would be no adverse impact to the BPS”); FRCC Comments at 3 (“Indeed, the transmission planning entity is responsible as part of the system assessment process under the TPL standards to test remedies to ensure that they address the problems being caused and do not cause additional problems.”); and Hydro One Comments at 5 (“Loss of load is under the purview of the regulatory authority and not NERC, unless it has an adverse impact on the BES which is already taken into consideration by the TPL standards * * * In all cases, steps are taken in planning, design and operations of the system to ensure that Firm Demand shedding would not adversely impact the BES * * *”).</P>
        </FTNT>
        <P>16. The Commission disagrees with commenters that NERC's proposed footnote `b' will have no adverse impact on reliable planning of the bulk-power system because planning to shed Firm Demand is intended to ensure that single contingency events do not result in adverse impacts and intended to preserve bulk-power system reliability.<SU>23</SU>
          <FTREF/>Table 1 of the TPL Reliability Standard identifies the system performance requirements or “System Limits or Impacts” that a planner must apply during its assessment of Category B, single contingency events.<SU>24</SU>
          <FTREF/>Except in limited circumstances, if a planner determines that it must plan to interrupt Firm Demand so that it does not violate the Table 1 system performance requirements, a planner should not apply footnote `b' as a mitigation plan to plan to operate reliably. The Commission therefore is concerned that NERC's proposal provides authority to adjust the TPL Reliability Standard and its system performance requirements for each single contingency event that does not meet the system performance requirements of Table 1.</P>
        <FTNT>
          <P>
            <SU>23</SU>
            <E T="03">See, e.g.,</E>NERC Comments at 11, TAPS Comments at 10, APPA Comments at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>24</SU>Reliability Standard TPL-002-0b, Table 1, Transmission System Standards—Normal and Emergency Conditions. Table 1 identifies the system performance requirements or “System Limits or Impacts” which are as follows: “System Stable and both Thermal and Voltage Limits within Applicable Rating”, “Loss of Demand or Curtailed Firm Transfers” and “Cascading Outages.”</P>
        </FTNT>
        <P>17. Further, NERC has not provided technically sound means of determining situations in which planning to interrupt Firm Demand would be allowable. While NERC expects that such determinations will be made in a stakeholder process, this provides no assurance that such a process will use technically sound means of approving or denying exceptions. The Commission concludes that the multiple stakeholder processes across the country engaging in such determinations could lead to inconsistent and arbitrary exceptions including, potentially, allowing entities to plan to interrupt any amount of Firm Demand in any location and at any voltage level.</P>
        <P>18. While the Commission recognizes that some variation among regions or entities is reasonable given varying grid topography and other considerations, there are no technical or other criteria to determine whether varied results are arbitrary or based on meaningful distinctions. The Commission, thus, concludes that NERC's proposal lacks safeguards to ensure against inconsistent results and arbitrary determinations to allow for the planned interruption of Firm Demand.</P>
        <P>19. A remand gives NERC and industry flexibility to develop an approach that would address the issues identified by the Commission with the proposed footnote `b' stakeholder process including, as discussed below, definition of the process and criteria or guidelines for the process.</P>
        <P>20. The Commission believes that, on remand, both NERC and the Commission will benefit from a more complete record regarding the electric industry's reliance on planned Firm Demand interruptions. In response to the Commission's request to explain and quantify the extent to which Firm Demand is planned to be interrupted pursuant to currently-effective footnote `b,' NERC explained:</P>
        
        <EXTRACT>
          <P>NERC and the Regional Entities have not collected statistics or preformed a survey concerning the prospective implementation of Footnote b under TPL-002-0a. During the drafting team's deliberations concerning TPL-001-2 and TPL-002-0a Footnote b, including the NERC Technical Conference on Footnote b, the informal assessments demonstrated that the use of Footnote b would not be widespread.<SU>25</SU>
            <FTREF/>
          </P>
        </EXTRACT>
        <FTNT>
          <P>
            <SU>25</SU>NERC Data Response at 10.</P>
        </FTNT>
        
        <P>Likewise, several commenters state that the interruption of Firm Demand is rarely needed, but provide no support for this conclusion.<SU>26</SU>
          <FTREF/>For example, EEI asks the Commission to “recognize” that “* * * the actions taken as outcomes of the planning review process, are likely to identify few/isolated circumstances in which these [footnote b] provisions would be invoked* * *.”<SU>27</SU>

          <FTREF/>However, the Commission believes that more specific information regarding the specific circumstances and frequency with which Firm Demand is planned to be interrupted will assist both NERC in developing, and the Commission in reviewing, appropriate revisions to<PRTPAGE P="26690"/>footnote `b' on remand. Therefore, pursuant to section 39.2(d) of the Commission's regulations,<SU>28</SU>
          <FTREF/>we direct NERC to identify the specific instances of any planned interruptions of Firm Demand under footnote `b' and how frequently the provision has been used. We direct NERC to use section 1600 of its Rules of Procedure to obtain information from users, owners and operators of the bulk-power system to provide this requested data.<SU>29</SU>
          <FTREF/>NERC shall submit this information to the Commission with NERC's footnote `b' filing that addresses the concerns in this Final Rule.</P>
        <FTNT>
          <P>
            <SU>26</SU>
            <E T="03">See, e.g.,</E>FRCC Comments at 4; MISO Comments at 4; BPA Comments.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>27</SU>EEI Comments at 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>28</SU>18 U.S.C. 39.2(d).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>29</SU>NERC Rules of Procedure, Section 1601 (effective January 31, 2012).</P>
        </FTNT>
        <P>21. We urge NERC to develop in a timely manner an appropriate modification that is responsive to the Commission's directives in Order No. 693 and our concerns set forth in this Final Rule. In that regard, we require NERC to deploy its Expedited Reliability Standards Development Process to quickly respond to the remand. As the Commission noted in previous orders, the use of planned or controlled load interruption is a fundamental reliability issue and, certainty regarding the loss of non-consequential load for a single contingency event is warranted.<SU>30</SU>
          <FTREF/>Thus, using the Expedited Standards Development Process will more rapidly bring needed certainty to this fundamental reliability issue.</P>
        <FTNT>
          <P>
            <SU>30</SU>
            <E T="03">North American Electric Reliability Corp.,</E>130 FERC ¶ 61,200 (2010) (March 2010 Order);<E T="03">North American Electric Reliability Corp.,</E>131 FERC ¶ 61,231 (2010) (June 2010 Order).</P>
        </FTNT>
        <P>22. Below we discuss three concerns: (a) Jurisdictional issues, (b) lack of technical criteria, and (c) the stakeholder process. The Commission also provides guidance on other acceptable approaches.</P>
        <HD SOURCE="HD2">A. Jurisdictional Issues</HD>
        <P>23. A number of commenters express concern that the Commission is reaching beyond its FPA section 215 jurisdiction.<SU>31</SU>
          <FTREF/>Commenters assert that the Commission options exceed its jurisdiction involving acceptable levels and types of service. Commenters seek assurance that the Commission's proposal does not infringe on matters reserved to the States and instead “only prescribe acceptable load shedding as it pertains to wholesale customers that are in a position to select interruptible or conditional firm transmission service.”<SU>32</SU>
          <FTREF/>NARUC states that “any NERC standard for shedding distribution level load must be guided by States and that a demonstration that interruption of the load will not cause instability, uncontrolled separation, or cascading failures on the bulk system is appropriate for a NERC standard.”<SU>33</SU>
          <FTREF/>NARUC adds that specifications of what retail load and what levels of retail load can be interrupted is a State determination that is not reviewable by the Commission. TAPS agrees with NERC that issues pertaining to whether it is permissible to plan to interrupt firm load involves conflicts among federal, provincial, state, and local governing bodies.<SU>34</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>31</SU>
            <E T="03">See, e.g.,</E>Comments of NERC, NARUC, APPA and TAPS.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>32</SU>NYPSC Comments at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>33</SU>NARUC Comments at 3-4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>34</SU>TAPS Comments at 9.</P>
        </FTNT>
        <P>24. The Commission disagrees that it is infringing on State Commissions or overstepping jurisdictional bounds. In this Final Rule, the Commission remands NERC's proposed footnote `b' as an inadequate mechanism to address planned curtailment of firm demand and not responsive to the Commission's directives in Order No. 693 regarding this matter. The Commission is not directing that NERC develop a specific solution or approach on remand. Thus, our remand of the NERC proposed modification to TPL-002-0b, Table 1, footnote `b' is fully within the Commission's authority pursuant to section 215(d)(4) to remand to the ERO for further consideration a modification to a proposed reliability standard that the Commission disapproves in whole or in part. Moreover,FPA section 215 gives the Commission jurisdiction over mandatory Reliability Standards to ensure reliability of the Bulk-Power System.<SU>35</SU>
          <FTREF/>Consistent with its statutory authority, the Commission's interest and focus in this proceeding is on the planned interruption of Firm Demand on the Bulk-Power System. The Commission views this matter in the context of Reliability Standard TPL-002-0b, which requires that in planning the system to withstand the loss of a single Bulk-Power System element, Bulk-Power System performance criteria must be met. If it is not met, a corrective action plan is required to address the Bulk-Power System performance criteria violation. Contingencies studied pursuant to Reliability Standard TPL-002-0b pertinent to Bulk-Power System facilities are subject to Commission jurisdiction under FPA section 215. In sum, the performance of the Bulk-Power System under the TPL-002-0b Reliability Standard is within the Commission's jurisdiction.</P>
        <FTNT>
          <P>
            <SU>35</SU>16 U.S.C. 824o(b)(1).</P>
        </FTNT>
        <HD SOURCE="HD2">B. Lack of Technical Criteria</HD>
        <HD SOURCE="HD3">NOPR Proposal</HD>
        <P>25. In the NOPR, the Commission proposed to remand NERC's proposal to modify Reliability Standard TPL-002-0b, Table 1, footnote `b.' The Commission stated that it believed that NERC's proposal does not meet the directives in Order No. 693 and the June 2010 Order and does not clarify or define the circumstances in which an entity can plan to interrupt Firm Demand for a single contingency.<SU>36</SU>
          <FTREF/>In the NOPR the Commission expressed concern that NERC's proposed footnote `b' lacks parameters. Without any substantive parameters governing the stakeholder process, the enforceability of this obligation by NERC and the Regional Entities would be limited to a review to ensure only that a stakeholder process occurred. The Commission noted that NERC appears to confirm this concern, as NERC explained that Regional Entities' involvement is limited to after-the-fact oversight by auditing the entity's implementation of footnote `b' to determine if the planned interruption of Firm Demand was vetted through the stakeholder process.<SU>37</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>36</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,683 at P 11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>37</SU>
            <E T="03">Id.</E>P 12.</P>
        </FTNT>
        <P>26. Further, in the NOPR the Commission stated that since the proposed footnote `b' contains no constraints, it could allow an entity to plan to interrupt any amount of planned Firm Demand, in any location or at any voltage level as needed for any single contingency, provided that it is documented and subjected to a stakeholder process. The Commission found this result remains contrary to the underlying Reliability Standard and prior Commission orders.<SU>38</SU>
          <FTREF/>The Commission requested comment on this specific concern of the lack of technical criteria or parameters.</P>
        <FTNT>
          <P>
            <SU>38</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>

        <P>27. Some commenters agree with the Commission that there is lack of technical criteria to determine planned interruption of Firm Demand. For example, California SWP states that Reliability Standards “should ensure transparent criteria based on technical merits and not software limitations derived from a desire to mask [locational marginal pricing] price signals with socialized pricing or on<E T="03">status quo</E>practices.”<SU>39</SU>

          <FTREF/>ITC believes that there is a need for defined parameters that will guide the review of exceptions and that will prevent<PRTPAGE P="26691"/>planned interruptions from becoming commonplace.<SU>40</SU>
          <FTREF/>Manitoba Hydro states that the characteristics of openness and transparency are indicators of a non-discriminatory planning process; however, these characteristics do not ensure that certain reliability criteria of the planned facilities will be met.<SU>41</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>39</SU>California SWP Comments at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>40</SU>ITC Comments at 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>41</SU>Manitoba Hydro Comments at 6.</P>
        </FTNT>
        <P>28. Other commenters disagree with the Commission's concern that there is a lack of criteria to determine planned interruption of Firm Demand. NERC states that it does not believe that an exceptions process that provides defined criteria, with some allowances, could be crafted that would respect pre-existing decision making processes that occur at state and local jurisdictions. NERC argues that the decision to interrupt local load is essentially an economic decision—a quality of service issue, not a reliability issue.<SU>42</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>42</SU>NERC Comments at 13.</P>
        </FTNT>
        <P>29. MISO disagrees that additional language would reduce the potential for inconsistent results and points out that registered entities already have many established requirements that govern the transmission planning processes.<SU>43</SU>
          <FTREF/>MISO believes that if the Commission determines that criteria are needed, such criteria should be determined by the stakeholders in the regions though their established stakeholder processes.<SU>44</SU>
          <FTREF/>EEI does not believe that specific criteria should be developed until a better understanding is obtained regarding the role of service interruptions as a reliability tool.<SU>45</SU>
          <FTREF/>EEI believes that these are appropriate aspects of the NERC proposal that would be readily amenable to an initial implementation approach, followed by an adjustment period that would refine the overall process consistent with the Commission's concerns.</P>
        <FTNT>
          <P>
            <SU>43</SU>MISO Comments at 3.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>44</SU>
            <E T="03">Id.</E>at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>45</SU>EEI Comments at 10.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>30. We believe that openness and transparency do not alone ensure that bulk electric system performance criteria will be met to ensure system reliability. The Commission is not persuaded that developing technical criteria is unachievable. As the Commission observed in the NOPR, NERC has thresholds in other reliability contexts, such as vegetation management pursuant to Reliability Standard FAC-003-1 which applies to all transmission lines operated at 200 kV and above. Likewise, NERC's Statement of Compliance Registry Criteria includes numerous thresholds for determining eligibility for registration.<SU>46</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>46</SU>
            <E T="03">See, e.g.,</E>NERC Statement of Registry Criteria, section III. The Commission approved the Statement of Registry Criteria in Order No. 693.<E T="03">See</E>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 95.</P>
        </FTNT>
        <P>31. The Commission does not agree with EEI's recommendation to implement a stakeholder process that is absent technical criteria but then amend it later. While the Commission has, in other circumstances, approved a Reliability Standard and, as a separate action, directed NERC to develop a modification pursuant to section 215(d)(5) of the FPA, in such proceedings the Commission concluded that the proposed Reliability Standard was just, reasonable, not unduly discriminatory or preferential and in the public interest. In the immediate proceeding, however, we cannot make such a finding in light of the flawed stakeholder process provision.</P>
        <P>32. In response to MISO's argument that such criteria should be determined by the stakeholders in the regions though their established stakeholder processes, the Commission would be amenable to such an approach if, for example, NERC and/or the Regional Entities developed an exception process that provides flexibility in decisions based on disparate topology or on other matters since they could utilize their technical expertise to determine the reliability impact from one region to another. For these reasons, the Commission concludes that a more defined process is needed with NERC-defined technical criteria to determine planned interruption of Firm Demand. However, we conclude that the approach of allowing a decentralized process without any overarching parameters is unacceptable.</P>
        <P>33. With regard to NERC's comment that the decision to interrupt local load is essentially an economic decision that is a quality of service issue, not a reliability issue, the Commission notes that in Order No. 693, we dismissed the argument that it may be preferable to plan the bulk electric system in such a manner that contemplates the interruption of some firm load customers in the event of a N-1 contingency, and that such interruption is based largely on the matter of economics, not reliability.<SU>47</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>47</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1792.</P>
        </FTNT>
        <HD SOURCE="HD2">C. Stakeholder Process</HD>
        <HD SOURCE="HD3">NOPR Proposal</HD>
        <P>34. In the NOPR, the Commission expressed concern that NERC's proposed footnote `b' stakeholder process is insufficient to meet Order No. 693 and the June 2010 Order clarification that a regional difference, or a case-specific exception process that can be technically justified, to plan for the loss of firm services at the fringes of the systems is acceptable in limited circumstances.<SU>48</SU>
          <FTREF/>The Commission also noted that nothing in the proposed footnote `b' defines the stakeholder process, other than that it must be an open and transparent stakeholder process that includes addressing stakeholder comments.<SU>49</SU>
          <FTREF/>The Commission noted that any meeting that is open to stakeholders could meet this criteria.</P>
        <FTNT>
          <P>
            <SU>48</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,683 at P 19.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>49</SU>
            <E T="03">Id.</E>P 20.</P>
        </FTNT>
        <P>35. The Commission further stated that the lack of a defined stakeholder process could allow a transmission planner to develop a process that provides insufficient opportunity for stakeholder participation and transparency yet still comply with the standard. The Commission expressed its belief that nothing in the proposed footnote `b' restricts the stakeholder process, other than that it must be an open and transparent stakeholder process that includes addressing stakeholder comments. The Commission requested comment on whether a stakeholder process is the appropriate vehicle to approve or deny exceptions to allow entities to plan to interrupt Firm Demand for a single contingency and if so, whether the proposed footnote `b' would require any stakeholder due process.</P>
        <HD SOURCE="HD3">Comments</HD>
        <P>36. Several commenters believe that NERC's proposed stakeholder process is the appropriate venue to approve or deny exceptions to interrupt planned Firm Demand. NERC and other commenters contend that building on existing stakeholder processes is appropriate, rather than creating new, duplicative processes. While EEI, APPA, and TAPS concur with or acknowledge the Commission's concerns about the inadequacy of the proposed stakeholder process, they nonetheless urge the Commission to approve NERC's proposal stating that it reflects the considered expertise that instances of planned load shed are uncommon and not amenable to a one-size-fits-all approach.<SU>50</SU>

          <FTREF/>NERC believes the introduction of an additional planning process may contribute to further delays and regulatory confusion. NERC states<PRTPAGE P="26692"/>that “keeping decision-making with those most impacted by decisions regarding reliability and costs, lack of jurisdictional authority, and the existence of established open and transparent stakeholder processes—are the reasons NERC did not create a new stakeholder process.”<SU>51</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>50</SU>
            <E T="03">See, e.g.,</E>EEI Comments at 3, TAPS Comments at 5, APPA Comments at 3.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>51</SU>NERC Comments at 12.</P>
        </FTNT>
        <P>37. Duke Energy believes that the current Order No. 890-type process involving the local transmission planning collaborative is the appropriate stakeholder process. Duke Energy suggests that footnote `b' should be revised to include a local regulatory authority process as the appropriate stakeholder process to allow entities to plan to interrupt Firm Demand for a single contingency. According to Duke Energy, in such a process a transmission planner would submit its plan to interrupt Firm Demand for a single contingency to its local regulatory authority that has jurisdiction over quality of service to local load prior to any actual interruption of Firm Demand.</P>
        <P>38. BPA states that the stakeholder process will keep the decision local, where the parties involved understand the different factors that must be considered in deciding the proper path forward.<SU>52</SU>
          <FTREF/>APPA maintains that these processes impose due process requirements on the transmission planner, including participation in an open and transparent stakeholder process that considers stakeholder comments.<SU>53</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>52</SU>BPA Comments at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>53</SU>APPA Comments at 5.</P>
        </FTNT>
        <P>39. FRCC disagrees with the Commission that enforceability is limited since the process requires development of a record documenting the decisions and stakeholder comments and planning authority responses. According to FRCC, the result will provide NERC and the Commission substantive and procedural grounds to assess whether sufficient consideration was given to maintaining reliability.<SU>54</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>54</SU>FRCC Comments at 3.</P>
        </FTNT>
        <P>40. Some commenters believe that NERC's proposed stakeholder process is not the appropriate vehicle to approve or deny exceptions to interrupt planned Firm Demand. ITC argues that the stakeholder process is inadequately undefined to ensure that planned Firm Demand interruptions are kept to a minimum. Manitoba Hydro indicates that by acknowledging an exception for interruptible Firm Demand, NERC appears to recognize that the right to interrupt is not solely a reliability issue, but also a commercial or legal issue based on contractual rights.<SU>55</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>55</SU>Manitoba Hydro Comments at 5.</P>
        </FTNT>
        <P>41. While TAPS encourages the Commission to accept NERC's proposed footnote `b,' it shares the NOPR's concerns about the adequacy of the open and transparent stakeholder process and has argued for a decision-making role for transmission-dependent utilities in the Order No. 890 and Order No. 1000 planning processes to ensure that stakeholder processes do not result in a presentation of a decision followed by the transmission provider simply “rubber-stamping” the decision.<SU>56</SU>
          <FTREF/>If the Commission determines that these objectives cannot be accomplished without more robust action from the Commission in this proceeding, TAPS urges the Commission not to remand the proposed footnote `b,' but instead to accept NERC's proposal and direct NERC to submit a further modified footnote `b' to address the parameters of the “open and transparent stakeholder process that includes addressing stakeholder comments.”<SU>57</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>56</SU>TAPS Comments at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>57</SU>
            <E T="03">Id.</E>at 11.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>42. The Commission is not persuaded that the stakeholder process is adequately defined. The Commission is concerned that the stakeholder process could undermine the system performance criteria of TPL-002-0b Reliability Standard. As the Commission stated in Order No. 693, one of the key reliability objectives of the TPL Reliability Standard is that the system can be operated following the loss of one element and supply projected firm customer demands and projected firm transmission services at all demand levels over the range of forecast system demands.<SU>58</SU>
          <FTREF/>The Commission finds that the stakeholder process without appropriate parameters is inconsistent with the reliability objective to supply projected firm customer demands for the loss of one element. While the Reliability Standard requires that the system is planned so that the system can be operated following the loss of one element and supply projected firm customer demands, the proposed stakeholder process could defeat this by allowing a transmission planner to plan to shed as much load as needed so that the system can be operated to supply whatever customers remain.</P>
        <FTNT>
          <P>
            <SU>58</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1771.</P>
        </FTNT>
        <P>43. The Commission agrees with TAPS to the extent it observes that the proposal could allow a transmission planner to utilize a new or existing stakeholder process that provides insufficient opportunity for a stakeholder to provide meaningful input. We conclude that the stakeholder process with no criteria to objectively assess whether varied results are arbitrary or based on meaningful differences is unjust, unreasonable, unduly discriminatory or preferential, and not in the public interest. Nothing in proposed footnote `b' defines the stakeholder process, other than it must be an open and transparent stakeholder process that includes addressing stakeholder comments.</P>
        <P>44. The Commission is not persuaded by FRCC's comment that enforceability is not limited by proposed footnote ‘b’ and that development of a record will provide NERC “substantive and procedural” grounds to assess the outcome of the process. Neither FRCC nor any other commenter identifies the minimum procedural safeguards to assure an adequate level of stakeholder participation and consideration of stakeholder comment in the decision-making process. Moreover, even NERC, which states that it can conduct after-the-fact audits, indicates that such audits would not explore substantive adequacy or the reliability basis for a decision to plan to shed Firm Demand.<SU>59</SU>
          <FTREF/>Further, the Commission is not persuaded by APPA and BPA comments that local stakeholder participation and due process requirements imposed on the transmission planner are sufficient. Rather, the Commission believes that if a transmission planner invokes a process that provides for minimal stakeholder involvement, it could argue that it satisfied the provision, even if the transmission planner is the ultimate decision maker and simply `rubber stamps' its own proposal to interrupt planned Firm Demand.</P>
        <FTNT>
          <P>
            <SU>59</SU>NERC Data Response at 7-9.</P>
        </FTNT>
        <HD SOURCE="HD2">D. Guidance on Acceptable Approaches to Footnote ‘b’</HD>
        <P>45. The Commission proposed three options in the NOPR for further guidance on acceptable approaches to footnote `b.' In addition, the Commission requested comment on other potential options to solve the concerns outlined in the NOPR.</P>
        <HD SOURCE="HD3">1. Existing Protocols To Develop Criteria/Quantitative Limits</HD>

        <P>46. In the NOPR, the Commission acknowledged that NERC considered a variety of limits but observed that NERC's establishment of some form of<PRTPAGE P="26693"/>criteria for planning to interrupt Firm Demand could be an acceptable approach for footnote `b.' The Commission requested comment on whether existing protocols such as the Department of Energy's Electric Emergency Incident and Disturbance Report (Form OE-417), which requires an entity to report a certain amount of uncontrolled loss of firm system loads, or NERC's Statement of Compliance Registry Criteria could provide guidance to NERC to devise criteria.</P>
        <HD SOURCE="HD3">Comments</HD>
        <P>47. Commenters were unanimous that the examples of existing protocols would not be beneficial to devise criteria. NERC and others state that any bright-line megawatt limit would be inappropriate because the bright-line would be arbitrary.<SU>60</SU>
          <FTREF/>Some commenters do not believe that existing protocols, such as the requirement in Form OE-417 should be used to determine criteria related to planned loss of Firm Demand.<SU>61</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>60</SU>NERC Comments at 14.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>61</SU>ITC Comments at 5;<E T="03">see also</E>Hydro One and IESO Comments.</P>
        </FTNT>
        <P>48. BPA, ITC, and Duke Energy comment that setting a quantitative limit would push transmission planners to plan to meet such a limit for a single contingency in all cases. Currently, transmission planners start from the premise that no load should be interrupted in the event of a single contingency. ITC believes that including such an acceptable lost load criterion as an option could lead to that option being chosen as the “default solution,” i.e., allowing for a certain amount of acceptable interruption of Firm Demand without a stakeholder exception review process.<SU>62</SU>
          <FTREF/>In the same vein, Duke indicates that a specific megawatt threshold may prohibit certain interruptions of Firm Demand that would be acceptable from a quality of service and local consequences perspectives.<SU>63</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>62</SU>ITC Comments at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>63</SU>Duke Comments at 6.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>

        <P>49. The Commission is persuaded by the commenters that Form OE-417 or the Registry Criteria are not, by themselves, beneficial to use to devise criteria. The Commission also agrees that a bright-line criteria by itself does not present a viable option and would have the potential to constitute an acceptable<E T="03">de facto</E>interruption and become commonplace to plan to interrupt Firm Demand. For example, if the bright-line criteria included up to 50 MW of planned interruptible Firm Demand under proposed footnote `b', then planners may choose to automatically shed up to 50 MW of load as their first course of action for any single contingency event that would cause a violation of system performance criteria. This is not an acceptable outcome.</P>
        <HD SOURCE="HD3">2. A Blend of Quantitative and Qualitative Thresholds</HD>
        <P>50. The Commission also sought comment on whether a blend of quantitative and qualitative thresholds to be used to interrupt planned Firm Demand would be an appropriate option for providing criteria that would be generally applicable, but also for allowing for certain cases that may exceed the criteria. For example, a Reliability Standard could require a process with a quantitative limitation on how much Firm Demand could be planned for interruption and the standard could provide an exception process where a registered entity would submit documents and explanation to the ERO or a Regional Entity for approval based upon certain considerations.<SU>64</SU>
          <FTREF/>The Commission suggested that setting generally applicable criteria for when an applicable entity can plan to shed Firm Demand, coupled with an exceptions process overseen by NERC and the Regional Entities, could mean that few exception requests must be processed by NERC and the Regional Entities.<SU>65</SU>
          <FTREF/>The Commission observed in the NOPR that this approach may satisfy the need for technical criteria while accounting for NERC's concerns about the difficulty of developing a one-size-fits-all criterion for limiting planned Firm Demand interruptions and the appropriateness and feasibility of managing and actively participating in each planning process.</P>
        <FTNT>
          <P>
            <SU>64</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,683 at P 18.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>65</SU>
            <E T="03">Id.</E>P 27.</P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>
        <P>51. California SWP indicates that standards must constrain the use of firm load shedding as a reliability solution in transmission planning and at the same time, require a transparent and clearly defined stakeholder process to support any such planned use of load shedding for single contingency events.<SU>66</SU>
          <FTREF/>BPA suggests that, if the Commission does set a quantitative limit on planned interruption of Firm Demand, a limit based on a fraction of aggregated normal peak load would be one option that may be more effective and adaptable to all sizes of utilities.<SU>67</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>66</SU>California SWP Comments at 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>67</SU>BPA Comments at 4.</P>
        </FTNT>
        <P>52. Other commenters disagree that a blend is a good option. NARUC indicates that rather than inventing another stakeholder process by requiring NERC to set specific quantitative or qualitative requirements for distribution load shedding, NERC should look to State commissions and existing State curtailment plans to guide load shedding in contingency planning.<SU>68</SU>
          <FTREF/>Duke Energy submits that a blend of quantitative and qualitative thresholds does not provide enough flexibility to permit the qualitative assessment of the loads and locations for which transmission planners may interrupt under their exercise of footnote `b' because a blended threshold may still rely too heavily on a quantitative threshold for planned interruption of Firm Demand.<SU>69</SU>
          <FTREF/>FRCC states it is not feasible to develop a single quantitative rule that would apply equitably to all stakeholders and regions.<SU>70</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>68</SU>NARUC Comments at 3.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>69</SU>Duke Energy Comments at 7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>70</SU>FRCC Comments at 7.</P>
        </FTNT>
        <P>53. EEI believes that adopting a process that would provide greater clarity, reporting, and refinement would provide the specific information on the extent that the footnote `b' issue presents itself. EEI also agrees with NERC that efforts to create a one-size-fits-all approach have less value than a process that ensures openness and transparency.</P>
        <HD SOURCE="HD3">Commission Determination</HD>

        <P>54. The Commission believes that setting a quantitative and qualitative threshold in developing a limited exception for planned interruption of Firm Demand may be a workable solution. First, qualitative thresholds could be used to overcome the concern discussed immediately above regarding the quantitative threshold becoming an acceptable<E T="03">de facto</E>interruption of planned Firm Demand. By utilizing a blend, the planner must also meet the qualitative threshold which could consist of, for example, the submittal of documents and explanation to the entity ultimately deciding whether the planned load shed is acceptable. For example, if 100 MW of planned Firm Demand was permitted to be interrupted, the planner could not automatically and unilaterally shed up to 100 MW of planned Firm Demand each time system performance criteria would be violated. Under the blend concept, the Commission envisions that<PRTPAGE P="26694"/>the planner would consider up to 100 MW of planned Firm Demand interruption along with other options to resolve the system performance criteria violation and submit its documentation and explanation to the entity deciding whether the planned load shed is acceptable. The concept of a blend of thresholds would prevent an acceptable<E T="03">de facto</E>interruption of planned Firm Demand and avoid the difficulty of developing a one-size-fits-all criterion for limiting planned Firm Demand interruptions, but still allow for those limited circumstances to be reviewed in an exception process where a limited amount of planned interruption of Firm Demand may be acceptable.</P>
        <P>55. We believe it is appropriate for the Regional Entities, with NERC as the final authority, to make determinations under a “blended” exception process. First, NERC and the Regional Entities provide both objectivity in the decision-making process as well as the necessary reliability-focused expertise. Second, this should not overly burden NERC or Regional Entity resources as utilization of the planned load shed exception is—and would be—rarely utilized.<SU>71</SU>
          <FTREF/>Further, we are not persuaded by the assertion that NERC would be conflicted as the ERO and also inserting itself in the process. NERC's ERO role would continue, in coordination with its current responsibilities in implementing other exceptions such as the Technical Feasibility Exception process under the Critical Infrastructure Protection Reliability Standards.</P>
        <FTNT>
          <P>
            <SU>71</SU>
            <E T="03">See, e.g.,</E>FRCC Comments at 4; MISO Comments at 4; BPA Comments.</P>
        </FTNT>
        <P>56. The Commission does not agree with BPA's suggestion of using quantitative thresholds based on a fraction of aggregated normal peak load. BPA's suggestion attempts to address the concerns of commenters that a bright-line threshold must be established that would be a one-size-fits-all criteria. For example, instead of a megawatt bright-line threshold for all entities, the ERO could establish a threshold based on a percentage of aggregated normal peak load. The Commission believes that it would be difficult to demonstrate that adoption of BPA's suggestion would be just and reasonable, not unduly discriminatory or preferential and in the public interest. If criteria were established that permitted a percentage of aggregated normal peak load as an acceptable threshold for planned interruption of Firm Demand, even a small percentage could equate to entire towns, cities or regions of load.<SU>72</SU>
          <FTREF/>The Commission, therefore, does not support the planned interruption of Firm Demand based on a fraction of aggregated normal peak load. The Commission believes that an appropriate mechanism would be based on impact studies that consider minimizing planned interruption of Firm Demand within, and adjacent to, communities and small localities.</P>
        <FTNT>
          <P>
            <SU>72</SU>For example, the PJM aggregated normal system peak load is approaching 160,000 MW, so a one percent threshold would equate to allowance of planned interruption for a single contingency of up to 1600 MW of load, which is the size of some entire towns, cities or regions.</P>
        </FTNT>
        <P>57. The Commission offers guidance to NERC to consider the option of a blend of quantitative and qualitative thresholds. An example of a qualitative threshold could include identifying geographical or topological “fringes of the system.” While interruption at the fringes of the system may be expected by some consumers, not all customers necessarily have that same expectation. For example, we don't expect that many water treatment facilities or telecom switching stations normally plan to be interrupted for single contingency events.<SU>73</SU>
          <FTREF/>While the Commission has offered one example of a qualitative threshold, NERC may explore other qualitative thresholds on remand. The Commission believes that a blend of quantitative and qualitative thresholds coupled with an exception process overseen by NERC and the Regional Entities would be a reasonable option to allow for the limited interruption of planned Firm Demand. Accordingly, the Commission directs the ERO to consider some blend of quantitative and qualitative thresholds.</P>
        <FTNT>
          <P>
            <SU>73</SU>While we anticipate that such facilities are prepared for distribution-level blackouts, we are not aware that they are prepared for a transmission-level blackout.</P>
        </FTNT>
        <HD SOURCE="HD3">3. Customer or Community Consent</HD>
        <P>58. In the NOPR the Commission also requested comment on whether a feasible option would be to revise footnote `b' to allow for the planned interruption of Firm Demand in circumstances where the “transmission planner can show that it has customer or community consent and there is no adverse impact to the Bulk-Power System.”<SU>74</SU>
          <FTREF/>The Commission suggested that this would not require affirmative consent by every individual retail customer, but would recognize that either group would need to be adequately defined. The Commission requested comments on who might be able to represent the customer or community in this option and how customer or community consent might be demonstrated.<SU>75</SU>
          <FTREF/>The Commission also requested comment on how it would be determined that firm demand shedding with customer consent would not adversely impact the Bulk-Power System. Additionally, the Commission requested comment on whether a customer who would otherwise consent to having its planning authority or transmission planner plan to interrupt Firm Demand pursuant to this option could instead select interruptible or conditional firm service under the tariff to address cost concerns.</P>
        <FTNT>
          <P>
            <SU>74</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,683 at P 28.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>75</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>
        <P>59. Several commenters agreed with the Commission that the customer or community consent should be required. ITC believes the customers or entities should be involved in a stakeholder process such as a representative group for the affected load or customers (community representatives or a separate load serving entity where the transmission provider is not an integrated utility), the public service/utility regulatory commission for the affected load, the RTO or ISO for the affected area, and any other affected entity. California SWP also supports notice to and consent of loads (or their wholesale representatives) that are planned to be interrupted for the loss of a single element.<SU>76</SU>
          <FTREF/>In its comments, California SWP explains that it was “surprised to learn that in lieu of transmission upgrades, [its transmission planner] relied on interruption of SWP's large firm pump loads supposedly receiving the same California Independent System Operator (CAISO) transmission service as provided to SCE loads. At that time, SWP was not consulted about the planned curtailment of its firm loads as an alternative to a transmission upgrade, and thus had no opportunity to correct this error.”<SU>77</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>76</SU>California SWP Comments at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>77</SU>
            <E T="03">Id.</E>at 2-3.</P>
        </FTNT>
        <P>60. Other commenters disagree that customer or community consent should be required. NERC states that it has no relationship with retail customers and, therefore, has no mechanism to bring retail customers into the conversation. NERC adds that both wholesale and retail customers are already involved in state processes which provide a forum for them to be heard.</P>

        <P>61. Hydro One and the IESO submit that customer interests are managed by the relevant regulatory authority and consent is through regulatory approval. In all cases, steps are taken in planning, design, and operations of the system to<PRTPAGE P="26695"/>ensure that Firm Demand shedding would not adversely impact the bulk electric system in addition to the fact that the customer also has other options such as to select interruptible service. NYPSC recommends that the Commission only prescribe acceptable load shedding as it pertains to wholesale customers that are in a position to select interruptible or conditional firm transmission service under Commission-approved tariffs.</P>
        <P>62. FRCC states that the evaluation of the possible use of interruptible or conditional firm service instead of planned interruptions of Firm Demand is not warranted. According to FRCC, the adoption of a Firm Demand interruption alternative would inherently entail customer benefits from foregone project costs and the non-incurrence of environmental and other impacts. The customers would also generally enjoy a higher quality of service than traditional interruptible or conditional firm. Consequently, FRCC believes that applying any such rate in place of Demand interruption would present imponderable issues of quantification and application.</P>
        <P>63. BPA does not believe that this proceeding is appropriate to decide issues related to service choice. BPA argues that the Commission has determined that the rate for conditional firm service be the same as the firm rate. BPA does not anticipate that the interruption of Firm Demand would occur on a frequent basis, if at all. Thus, BPA does not believe that a customer should pay a different transmission rate under these circumstances. APPA states that footnote `b' arms wholesale transmission customers and communities served at retail with information and studies prepared by the transmission planner, documenting the specific circumstances (i.e., specific Bulk Electric System Contingency events) under which interruption of Firm Demand may be needed to address bulk electric system performance requirements.</P>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>64. We understand NERC's position that as the entity that addresses Bulk-Power System reliability, it does not have a mechanism to coordinate with customers. Likewise, how to define customers and community decisions and engage them in the NERC process could be challenging.<SU>78</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>78</SU>As suggested in the NOPR, customer or community consent would not require affirmative consent by every individual retail customer, but the process NERC developed would recognize that either group would need to be adequately defined. We note that, although NERC comments that it addresses Bulk-Power System reliability, the process that NERC proposes will impact firm load service to retail customers.</P>
        </FTNT>
        <P>65. At the same time, California SWP provides a compelling example of how a customer can be adversely affected by planned load shedding for Firm Demand if it was unaware its load would be interrupted until its load was actually shed. In contrast to California SWP's experience, a customer should have notice and understanding that the transmission planner plans to curtail certain Firm Demand in the event of a single contingency indentified in the system modeling under NERC's Transmission Planning requirements. NERC should consider these matters on remand.<SU>79</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>79</SU>We will not consider the tariff-related comments as they are beyond the scope of this rulemaking.</P>
        </FTNT>
        <HD SOURCE="HD3">Summary</HD>
        <P>66. In sum, the Commission remands the proposed footnote `b' and directs NERC to revise its proposal to address the Commission's concerns described above, subject to consideration of the additional guidance provided in this Final Rule.</P>
        <P>67. As stated in the NOPR, NERC will need to support the revision to footnote `b.' If there is a threshold component to the revised footnote, NERC would need to support the threshold and show that instability, uncontrolled separation, or cascading failures of the system will not occur as a result of planning to shed Firm Demand up to the threshold. In addition, if there is an individual exception option, the applicable entities should be required to find that there is no adverse impact to the Bulk-Power System from the exception and that it is considered in wide-area coordination and operations. Further, the Commission believes that any exception should be subject to further review by the Regional Entity or NERC.</P>
        <HD SOURCE="HD1">III. Information Collection Statement</HD>
        <P>68. The Office of Management and Budget (OMB) regulations require that OMB approve certain reporting and recordkeeping (collections of information) imposed by an agency.<SU>80</SU>
          <FTREF/>The information contained here is also subject to review under section 3507(d) of the Paperwork Reduction Act of 1995.<SU>81</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>80</SU>5 CFR 1320.11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>81</SU>44 U.S.C. 3507(d).</P>
        </FTNT>
        <P>69. As stated above, the subject of this Final Rule is NERC's proposed modification to Table 1, footnote `b' applicable in four TPL Reliability Standards. This Final Rule remands the footnote `b' modification to NERC. By remanding footnote `b' the applicable Reliability Standards and any information collection requirements are unchanged. Therefore, the Commission will submit this Final Rule to OMB for informational purposes only.</P>

        <P>70. Interested persons may obtain information on the reporting requirements by contacting the following: Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426 [Attention: Ellen Brown, Office of the Executive Director, email:<E T="03">data.clearance@ferc.gov</E>, phone: (202) 502-8663, or fax: (202) 273-0873].</P>
        <HD SOURCE="HD1">IV. Environmental Analysis</HD>
        <P>71. 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>82</SU>
          <FTREF/>The Commission has categorically excluded certain actions from this requirement as not having a significant effect on the human environment. Included in the exclusion are rules that are clarifying, corrective, or procedural or that do not substantially change the effect of the regulations being amended.<SU>83</SU>
          <FTREF/>The actions proposed herein fall within this categorical exclusion in the Commission's regulations.</P>
        <FTNT>
          <P>
            <SU>82</SU>
            <E T="03">Regulations Implementing the National Environmental Policy Act of</E>1969, Order No. 486, 52 FR 47897 (Dec. 17, 1987), FERC Stats. &amp; Regs., Regulations Preambles 1986-1990 ¶ 30,783 (1987).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>83</SU>18 CFR 380.4(a)(2)(ii).</P>
        </FTNT>
        <HD SOURCE="HD1">V. Regulatory Flexibility Act</HD>
        <P>72. The Regulatory Flexibility Act of 1980 (RFA)<SU>84</SU>
          <FTREF/>generally requires a description and analysis of final rules that will have significant economic impact on a substantial number of small entities. The RFA mandates consideration of regulatory alternatives that accomplish the stated objectives of a proposed rule and that minimize any significant economic impact on a substantial number of small entities. The Small Business Administration's (SBA) Office of Size Standards develops the numerical definition of a small business.<SU>85</SU>
          <FTREF/>The SBA has established a size standard for electric utilities, stating that a firm is small if, including its affiliates, it is primarily engaged in the transmission, generation and/or distribution of electric energy for sale and its total electric output for the preceding twelve months did not exceed four million megawatt hours.<SU>86</SU>

          <FTREF/>The RFA is not implicated by this Final Rule because the Commission is remanding<PRTPAGE P="26696"/>footnote `b' and not proposing any modifications to the existing burden or reporting requirements. With no changes to the Reliability Standards as approved, the Commission certifies that this Final Rule will not have a significant economic impact on a substantial number of small entities.</P>
        <FTNT>
          <P>
            <SU>84</SU>5 U.S.C. 601-612.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>85</SU>13 CFR 121.201.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>86</SU>
            <E T="03">Id.</E>n.22.</P>
        </FTNT>
        <HD SOURCE="HD1">VI. Document Availability</HD>

        <P>73. 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:00 p.m. Eastern time) at 888 First Street NE., Room 2A, Washington DC 20426.</P>
        <P>74. 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>75. 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 email at<E T="03">ferconlinesupport@ferc.gov,</E>or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. Email the Public Reference Room at<E T="03">public.referenceroom@ferc.gov.</E>
        </P>
        <HD SOURCE="HD1">VII. Effective Date and Congressional Notification</HD>
        <P>76. These regulations are effective July 6, 2012. The Commission has determined, with the concurrence of the Administrator of the Office of Information and Regulatory Affairs of OMB, that this rule is not a “major rule” as defined in section 351 of the Small Business Regulatory Enforcement Fairness Act of 1996.</P>
        <SIG>
          <P>By direction of the Commission. Commissioner Norris is dissenting in part and concurring in part with a separate statement attached.</P>
          <NAME>Kimberly D. Bose,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
        
        <P>NORRIS, Commissioner,<E T="03">dissenting in part and concurring in part:</E>
        </P>
        
        <EXTRACT>
          <P>The continued implementation and evolution of the mandatory reliability standards program enacted by Congress in 2005 has been at the forefront of our agenda since I arrived at the Commission in 2010. As we have grappled with the difficult issues raised by proposed new or revised standards, and as I have discussed these issues with regulated industry, state regulators, and the public, I have consistently heard a common theme: mandatory reliability standards come with costs that consumers ultimately must bear.</P>
          <P>As I have thought about this issue, it has become clear to me that in any discussion of a new or revised mandatory reliability standard, there is always a tradeoff between the level of reliability to be achieved by that standard and the costs that the standard will impose. However, that tradeoff is rarely discussed explicitly in the standards development process or during the Commission's review of standards. But, we know that it is an implicit consideration of entities participating in the standards development process. I believe it is more appropriate to make those considerations, where they are relevant, explicit. Therefore, I have advocated for an open dialogue between NERC, the industry, and the Commission to consider the connection between the mandatory standards we approve to maintain and improve the reliability of the Bulk Power System and the costs required to meet those standards.</P>
          <P>However, I have perceived some hesitancy in openly addressing costs when considering reliability matters. This is not surprising, as there are no easy answers to these tough questions, and regulators and industry charged with assuring reliability will always be hesitant to be perceived as sacrificing reliability in an effort to save on costs. While I am not advocating for a cost-benefit threshold for approving reliability standards, I do not believe that we can ignore the costs of proposed mandatory reliability standards as we consider whether they are “just, reasonable, not unduly discriminatory or preferential, and in the public interest”.<SU>1</SU>
            <FTREF/>These are issues with real world implications, not just for the reliability and security of our Nation's electric grid, but for the day-to-day struggles of local communities to balance the economic realities of many competing obligations.</P>
          <FTNT>
            <P>
              <SU>1</SU>
              <E T="03">See</E>16 U.S.C. 824o(d)(2).</P>
          </FTNT>
          <P>I am compelled to raise these issues in this proceeding because I believe that the Transmission Planning (TPL) Reliability Standard footnote `b' addressed in today's order presents a stark example of the tradeoffs that sometimes must be made between increasing levels of reliability and the costs that come with achieving them. As such, I hope my comments today will help generate a dialogue on how economics and reliability fit together when considering mandatory reliability standards.</P>
          <P>In today's order, I agree with the majority's decision to remand proposed TPL footnote `b' because it is vague, potentially unenforceable, and lacks adequate safeguards to determine when planning to shed firm load would be permitted. However, I am concerned that, in allowing for an exception to the TPL standards requirement that firm load must be maintained under N-1 scenarios, the order does not sufficiently recognize that this is both an economic and reliability issue, and must allow for a balancing of the economic and reliability considerations involved.</P>
          <P>There may be cases where planning to avoid shedding firm load in all N-1 scenarios will impose significant costs on customers, with perhaps little added reliability benefit for those customers. In such instances, I believe that wholesale transmission customers and local communities with retail load service should be empowered to consider the economic tradeoffs between incurring costs to avoid shedding firm load versus planning to shed firm load, as long as that decision does not adversely impact the reliability of the Bulk Power System. Simply put, if a customer seeks to avoid significant costs, and can do so without impacting its neighbors, the customer should be making that decision. Today's order fails to adequately acknowledge the economic consequences of having to invest in significant facility upgrades to avoid shedding firm load under certain N-1 scenarios that may be rare or unlikely and that would have only local impacts.<SU>2</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>2</SU>
              <E T="03">Transmission Planning Reliability Standards,</E>Order No. 762, 139 FERC ¶ 61,060, at P 33 (2012) (“With regard to NERC's comment that the decision to interrupt local load is essentially an economic decision that is a quality of service issue, not a reliability issue, the Commission notes that in Order No. 693, we dismissed the argument that * * * such interruption is based largely on the matter of economics, not reliability.”) I also note that the brief Commission findings in Order No. 693 failed to acknowledge or sufficiently address this issue, leaving the uncertainty we are still faced with today.<E T="03">Mandatory Reliability Standards for the Bulk-Power System,</E>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242, at P 1791-1794 (2007).</P>
          </FTNT>
          <P>Accordingly, in my view, the Commission should have directed NERC to revise footnote `b' to address two broad concerns. First, wholesale transmission customers and retail load should have the ability to choose whether to shed firm load during an N-1 contingency where that decision will not adversely impact the Bulk Power System. Second, the decision to shed firm load must be validated to ensure that there is no adverse impact on the Bulk Power System. Absent this reliability check, the planning of firm load shedding should not be permitted, because reliability of the Bulk Power System is paramount. While NERC, the Regional Entity, and/or the local planning authority must be involved in the reliability check, these entities would not be expected to be involved in the economic decision.</P>
          <P>Additionally, I agree with various comments filed in response to the NOPR that firm load shedding is and should be used rarely or infrequently. I do not expect that any new process that NERC may propose to determine whether firm load shedding is permitted would result in a rush by entities seeking to plan to shed firm load. In other words, I do not expect this exception to “swallow the rule” under the TPL standards that firm load may not be planned to be shed for N-1 contingencies.</P>

          <P>Finally, the concerns I note above regarding the failure to consider both the economic and reliability aspects of a decision to plan to shed firm load extend to the specific guidance provided in the order. The guidance in the order with respect to what<PRTPAGE P="26697"/>would constitute an allowable exception fails to provide a realistic means for entities to balance these economic and reliability considerations. Instead, I would have provided that an entity could submit its plan to shed firm load for a single contingency to its relevant regulatory authority or governing body prior to any actual interruption.<SU>3</SU>
            <FTREF/>The politically accountable regulatory authority or governing body would have then made the determination, based upon economics and in the best interests of its customers, as to whether firm load shedding should be permitted. Those determinations would be subject to oversight and review by NERC, the Regional Entity, and/or the planning authority to ensure that they will not adversely impact the Bulk Power System.<SU>4</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>3</SU>
              <E T="03">See e.g.,</E>Duke Energy Corporation Dec. 22, 2011 Comments, Docket No. RM11-18-000.</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>4</SU>NERC may propose an alternative to Commission guidance that is equally efficient and effective at addressing the Commission's reliability concerns. Order No. 693 at P 31.</P>
          </FTNT>
          <P>For these reasons, I respectfully dissent in part and concur in part.</P>
          
          <FP>John R. Norris,</FP>
          
          <FP>
            <E T="03">Commissioner.</E>
          </FP>
        </EXTRACT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10944 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Food and Drug Administration</SUBAGY>
        <CFR>21 CFR Parts 510 and 522</CFR>
        <DEPDOC>[Docket No. FDA-2012-N-0002]</DEPDOC>
        <SUBJECT>New Animal Drugs; Change of Sponsor; Change of Sponsor Address; Change of Sponsor Name and Address; Fomepizole</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food and Drug Administration, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Food and Drug Administration (FDA) is amending the animal drug regulations to reflect a change of sponsor name from Bioniche Teoranta to Mylan Institutional, LLC; a change of sponsor for fomepizole injectable solution from Synerx Pharma, LLC, to Mylan Institutional, LLC; and a change of sponsor address for Modern Veterinary Therapeutics, LLC.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective May 7, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Steven D. Vaughn, Center for Veterinary Medicine (HFV-100), Food and Drug Administration, 7520 Standish Pl., Rockville, MD 20855, 240-276-8300, email:<E T="03">steven.vaughn@fda.hhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Bioniche Teoranta, Inverin, County Galway, Ireland, has informed FDA that it has changed its name and address to Mylan Institutional, LLC, 4901 Hiawatha Dr., Rockford, IL 61103. Synerx Pharma, LLC, 100 N. State St., Newton, PA 18940, has informed FDA that it has transferred ownership of, and all rights and interest in, abbreviated new animal drug application (ANADA) 200-472 for Fomepizole for Injection to Mylan Institutional, LLC. Modern Veterinary Therapeutics, LLC, 1550 Madruga Ave., suite 329, Coral Gables, FL 33146, has informed FDA that it has changed its address to 18001 Old Cutler Rd., suite 317, Miami, FL 33157. Accordingly, the Agency is amending the regulations in parts 510 and 522 (21 CFR parts 510 and 522) to reflect these changes.</P>
        <P>Following this change of sponsorship, Synerx Pharma, LLC, is no longer the sponsor of an approved application. Accordingly, § 510.600 (21 CFR 510.600) is being amended to remove the entries for this firm.</P>
        <P>This rule does not meet the definition of “rule” in 5 U.S.C. 804(3)(A) because it is a rule of “particular applicability.” Therefore, it is not subject to the congressional review requirements in 5 U.S.C. 801-808.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>21 CFR Part 510</CFR>
          <P>Administrative practice and procedure, Animal drugs, Labeling, Reporting and recordkeeping requirements.</P>
          <CFR>21 CFR Part 522</CFR>
          <P>Animal drugs.</P>
        </LSTSUB>
        
        <P>Therefore, under the Federal Food, Drug, and Cosmetic Act and under authority delegated to the Commissioner of Food and Drugs and redelegated to the Center for Veterinary Medicine, 21 CFR parts 510 and 522 are amended as follows:</P>
        <REGTEXT PART="510" TITLE="21">
          <PART>
            <HD SOURCE="HED">PART 510—NEW ANIMAL DRUGS</HD>
          </PART>
          <AMDPAR>1. The authority citation for 21 CFR part 510 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>21 U.S.C. 321, 331, 351, 352, 353, 360b, 371, 379e.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="510" TITLE="21">
          <AMDPAR>2. In § 510.600, in the table in paragraph (c)(1), remove the entries for “Bioniche Teoranta” and “Synerx Pharma, LLC”; revise the entry for “Modern Veterinary Therapeutics, LLC”; and alphabetically add a new entry for “Mylan Institutional, LLC”; and in the table in paragraph (c)(2), remove the entry for “068882” and revise the entries for “015914” and “063286” to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 510.600</SECTNO>
            <SUBJECT>Names, addresses, and drug labeler codes of sponsors of approved applications.</SUBJECT>
            <STARS/>
            <P>(c) * * *</P>
            <P>(1) * * *</P>
            <GPOTABLE CDEF="s100,8" COLS="2" OPTS="L1,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1">Firm name and address</CHED>
                <CHED H="1">Drug<LI>labeler</LI>
                  <LI>code</LI>
                </CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*****</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Modern Veterinary Therapeutics, LLC, 18001 Old Cutler Rd., suite 317, Miami, FL 33157</ENT>
                <ENT>015914</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*****</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Mylan Institutional LLC, 4901 Hiawatha Dr., Rockford, IL 61103</ENT>
                <ENT>063286</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*****</ENT>
              </ROW>
            </GPOTABLE>
            <P>(2) * * *</P>
            <GPOTABLE CDEF="s20,r100" COLS="2" OPTS="L1,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1">Drug labeler code</CHED>
                <CHED H="1">Firm name and address</CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*****</ENT>
              </ROW>
              <ROW>
                <ENT I="01">015914</ENT>
                <ENT>Modern Veterinary Therapeutics, LLC, 18001 Old Cutler Rd., suite 317, Miami, FL 33157.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*****</ENT>
              </ROW>
              <ROW>
                <ENT I="01">063286</ENT>
                <ENT>Mylan Institutional, LLC, 4901 Hiawatha Dr., Rockford, IL 61103.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*****</ENT>
              </ROW>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="522" TITLE="21">
          <PART>
            <HD SOURCE="HED">PART 522—IMPLANTATION OR INJECTABLE DOSAGE FORM NEW ANIMAL DRUGS</HD>
          </PART>
          <AMDPAR>3. The authority citation for 21 CFR part 522 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>21 U.S.C. 360b.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="522" TITLE="21">
          <AMDPAR>4. In § 522.1004, revise paragraph (b) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 522.1004</SECTNO>
            <SUBJECT>Fomepizole.</SUBJECT>
            <STARS/>
            <P>(b)<E T="03">Sponsors.</E>See Nos. 046129 and 063286 in § 510.600(c) of this chapter.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: April 30, 2012.</DATED>
          <NAME>Steven D. Vaughn,</NAME>
          <TITLE>Director, Office of New Animal Drug Evaluation, Center for Veterinary Medicine.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10892 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4164-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <PRTPAGE P="26698"/>
        <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
        <SUBAGY>Internal Revenue Service</SUBAGY>
        <CFR>26 CFR Part 1</CFR>
        <DEPDOC>[TD 9588]</DEPDOC>
        <RIN>RIN 1545-BH84</RIN>
        <SUBJECT>Allocation of Mortgage Insurance Premiums</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Internal Revenue Service (IRS), Treasury.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final regulations and removal of temporary regulations.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This document contains final regulations that explain how to allocate prepaid qualified mortgage insurance premiums to determine the amount of the prepaid premium that is treated as qualified residence interest each taxable year. The final regulations reflect changes to the law made by the Tax Relief and Health Care Act of 2006, the Mortgage Forgiveness Debt Relief Act of 2007, and the Tax Relief, Unemployment Insurance Reauthorization, and Job Creation Act of 2010. The regulations affect taxpayers who pay prepaid qualified mortgage insurance premiums.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>These regulations are effective on May 4, 2012.</P>
          <P>
            <E T="03">Applicability Dates:</E>For dates of applicability, see § 1.163-11(d).</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Charles Kim, (202) 622-5020 (not a toll-free number).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>

        <P>This document contains amendments to 26 CFR part 1. On May 7, 2009, the Treasury Department and IRS published temporary regulations (TD 9449) under section 163 of the Internal Revenue Code (Code) in the<E T="04">Federal Register</E>(74 FR 21256) that explain how to allocate prepaid qualified mortgage insurance premiums to determine the amount of the prepaid premium that is treated as qualified residence interest each taxable year. On the same day, the Treasury Department and IRS published a notice of proposed rulemaking (REG-107271-08) cross-referencing the temporary regulations in the<E T="04">Federal Register</E>(74 FR 21295). No public hearing was requested or held. No comments responding to the notice of proposed rulemaking were received. The proposed regulations under section 163 are adopted as amended by this Treasury decision, and the corresponding temporary regulations under section 163 are removed.</P>

        <P>TD 9449 also contained temporary regulations under section 6050H(h) that require persons who receive premiums, including prepaid premiums, for mortgage insurance to make a return setting forth the amount of premiums received. A notice of proposed rulemaking (REG-107271-08) cross-referencing the temporary regulations was published in the<E T="04">Federal Register</E>on the same day (74 FR 21295). Because the deduction for mortgage insurance premiums currently does not apply to amounts paid or accrued after December 31, 2011, the Treasury Department and the IRS are not taking any action at this time with respect to the temporary regulations or the proposed regulations under section 6050H(h). The temporary regulations will expire on May 4, 2012.</P>
        <P>Section 419 of the Tax Relief and Health Care Act of 2006, Public Law 109-432 (120 Stat. 2967) (2006), added sections 163(h)(3)(E), (h)(4)(E), and (h)(4)(F) to the Code. Section 3 of the Mortgage Forgiveness Debt Relief Act of 2007, Public Law 110-142 (121 Stat. 1803) (2007), amended section 163(h)(3)(E)(iv). Section 759(a) of the Tax Relief, Unemployment Insurance Reauthorization, and Job Creation Act of 2010, Public Law 111-312 (124 Stat. 3296) (2010), further amended section 163(h)(3)(E)(iv). In general, these new provisions treat certain qualified mortgage insurance premiums as qualified residence interest. This treatment only applies to certain qualified mortgage insurance premiums paid or accrued on or after January 1, 2007, and on or before December 31, 2011, on mortgage insurance contracts issued on or after January 1, 2007.</P>

        <P>Section 163(h)(3)(E)(i) provides that premiums paid or accrued for qualified mortgage insurance in connection with acquisition indebtedness for a qualified residence are treated as qualified residence interest for purposes of section 163. Section 163(h)(4)(E) defines<E T="03">qualified mortgage insurance</E>as (i) mortgage insurance provided by the Veterans Administration (VA), the Federal Housing Administration (FHA), or the Rural Housing Administration (Rural Housing),<SU>1</SU>
          <FTREF/>and (ii) private mortgage insurance (as defined by section 2 of the Homeowners Protection Act of 1998 (12 U.S.C. 4901) as in effect on December 20, 2006). The amount treated as qualified residence interest may be reduced or eliminated under section 163(h)(3)(E)(ii), which provides that the amount allowed as a deduction is phased out ratably by 10 percent for each $1,000 ($500 in the case of a married individual filing a separate return) (or fraction thereof) that the taxpayer's adjusted gross income exceeds $100,000 ($50,000 in the case of a married individual filing a separate return).</P>
        <FTNT>
          <P>
            <SU>1</SU>References in section 163(h)(4)(E)(i) to the Veterans Administration and Rural Housing Administration are interpreted to mean their respective successors, the Department of Veterans Affairs and Rural Housing Service.</P>
        </FTNT>
        <P>Section 163(h)(4)(F) states that any amount paid by the taxpayer for qualified mortgage insurance that is properly allocable to any mortgage the payment of which extends to periods that are after the close of the taxable year in which the amount is paid shall be chargeable to capital account and shall be treated as paid in the periods to which the amount is allocated. No deduction shall be allowed for the unamortized balance of the account if the mortgage is satisfied before the end of its term. Section 163(h)(4)(F) provides that the allocation rules under section 163(h)(4)(F) do not apply to amounts paid for qualified mortgage insurance provided by the VA or Rural Housing. Additionally, section 163(h)(3)(E)(iv)(II) disallows a deduction for amounts allocable to any period after December 31, 2011.</P>
        <HD SOURCE="HD1">Explanation of Provisions</HD>
        <P>These final regulations provide rules regarding the allocation of prepaid qualified mortgage insurance premiums to determine the amount of the prepaid premium that is treated as qualified residence interest each taxable year under section 163(h)(4)(F).</P>
        <P>These final regulations apply to prepaid qualified mortgage insurance premiums paid or accrued on or after January 1, 2011. The treatment of mortgage insurance premiums as interest described in these final regulations is limited to prepaid qualified mortgage insurance premiums that are paid or accrued on or after January 1, 2011, and during periods to which section 163(h)(3)(E) is applicable. The temporary regulations are applicable to prepaid qualified mortgage insurance premiums paid or accrued on or after January 1, 2008, and on or before December 31, 2010.</P>
        <HD SOURCE="HD1">Special Analyses</HD>

        <P>It has been determined that this Treasury decision is not a significant regulatory action as defined in Executive Order 12866, as supplemented by Executive Order 13563. Therefore, a regulatory assessment is not required. It also has been determined that section 553(b) of the Administrative Procedure Act (5 U.S.C. chapter 5) does not apply to these regulations, and because the regulations do not impose a collection<PRTPAGE P="26699"/>of information on small entities, the Regulatory Flexibility Act (5 U.S.C. chapter 6) does not apply. Pursuant to section 7805(f) of the Code, the notice of proposed rulemaking preceding these regulations was submitted to the Chief Counsel for Advocacy of the Small Business Administration for comment on its impact on small business, and no comments were received.</P>
        <HD SOURCE="HD1">Drafting Information</HD>
        <P>The principal author of these regulations is Charles Kim, Office of the Associate Chief Counsel (Income Tax and Accounting). However, other personnel from the IRS and the Treasury Department participated in their development.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 26 CFR Part 1</HD>
          <P>Income taxes, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Adoption of Amendments to the Regulations</HD>
        <P>Accordingly, 26 CFR part 1 is amended as follows:</P>
        <REGTEXT PART="1" TITLE="26">
          <PART>
            <HD SOURCE="HED">PART 1—INCOME TAXES</HD>
          </PART>
          <AMDPAR>
            <E T="04">Paragraph 1.</E>The authority citation for part 1 continues to read in part as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>26 U.S.C. 7805 * * *</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="1" TITLE="26">
          <AMDPAR>
            <E T="04">Par. 2.</E>Section 1.163-11 is added to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 1.163-11</SECTNO>
            <SUBJECT>Allocation of certain prepaid qualified mortgage insurance premiums.</SUBJECT>
            <P>(a)<E T="03">Allocation</E>—(1)<E T="03">In general.</E>As provided in section 163(h)(3)(E), premiums paid or accrued for qualified mortgage insurance during the taxable year in connection with acquisition indebtedness with respect to a qualified residence (as defined in section 163(h)(4)(A)) of the taxpayer shall be treated as qualified residence interest (as defined in section 163(h)(3)(A)). If an individual taxpayer pays such a premium that is properly allocable to a mortgage the payment of which extends to periods beyond the close of the taxable year in which the premium is paid, the taxpayer must allocate the premium to determine the amount treated as qualified residence interest for each taxable year. The premium must be allocated ratably over the shorter of—</P>
            <P>(i) The stated term of the mortgage; or</P>
            <P>(ii) A period of 84 months, beginning with the month in which the insurance was obtained.</P>
            <P>(2)<E T="03">Limitation.</E>If a mortgage is satisfied before the end of its stated term, no deduction as qualified residence interest shall be allowed for any amount of the premium that is allocable to periods after the mortgage is satisfied.</P>
            <P>(b)<E T="03">Scope.</E>The allocation requirement in paragraph (a) of this section applies only to mortgage insurance provided by the Federal Housing Administration or private mortgage insurance (as defined by section 2 of the Homeowners Protection Act of 1998 (12 U.S.C. 4901) as in effect on December 20, 2006). It does not apply to mortgage insurance provided by the Department of Veterans Affairs or the Rural Housing Service. Paragraph (a) of this section applies whether the qualified mortgage insurance premiums are paid in cash or are financed, without regard to source.</P>
            <P>(c)<E T="03">Limitation on the treatment of mortgage insurance premiums as interest.</E>This section applies to prepaid qualified mortgage insurance premiums described in paragraph (a) of this section that are paid or accrued on or after January 1, 2011, and during periods to which section 163(h)(3)(E) is applicable. This section does not apply to any amount of prepaid qualified mortgage insurance premiums that are allocable to any periods to which section 163(h)(3)(E) is not applicable.</P>
            <P>(d)<E T="03">Effective/applicability date.</E>This section is applicable on and after January 1, 2011. For regulations applicable before January 1, 2011, see § 1.163-11T in effect prior to January 1, 2011 (§ 1.163-11T as contained in 26 CFR part 1 edition revised as of April 1, 2011).</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 1.163-11T</SECTNO>
            <SUBJECT>[Removed]</SUBJECT>
          </SECTION>
          <AMDPAR>
            <E T="04">Par. 3.</E>Section 1.163-11T is removed.</AMDPAR>
        </REGTEXT>
        <SIG>
          <NAME>Steven T. Miller,</NAME>
          <TITLE>Deputy Commissioner for Services and Enforcement.</TITLE>
          <DATED>Approved: April 24, 2012.</DATED>
          <NAME>Emily S. McMahon,</NAME>
          <TITLE>Acting Assistant Secretary of the Treasury (Tax Policy).</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10937 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4830-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 165</CFR>
        <DEPDOC>[Docket No. USCG-2012-0283]</DEPDOC>
        <RIN>RIN 1625-AA00</RIN>
        <SUBJECT>Safety Zone; Coast Guard Exercise, Hood Canal, WA</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing a temporary safety zone around vessels involved in a Coast Guard Ready for Operations exercise in Hood Canal, WA that will take place between May 08, 2012 and May 10, 2012. A safety zone is necessary to ensure the safety of the maritime public during the exercise and will do so by prohibiting any person or vessel from entering or remaining in the safety zone unless authorized by the Captain of the Port (COTP) or his Designated Representative.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective from 4:00 a.m. May 08, 2012 until 11:59 p.m. on May, 10, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents indicated in this preamble as being available in the docket are part of docket USCG-2012-0283 and are available online by going to<E T="03">http://www.regulations.gov,</E>inserting USCG-2012-0283 in the “Keyword” box, and then clicking “Search.” They are also available for inspection or copying at the Docket Management Facility (M-30), U.S. Department of Transportation, 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>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this temporary rule, call or email ENS Nathaniel P. Clinger; Waterways Management Division, Coast Guard Sector Puget Sound; Coast Guard; telephone 206-217-6045, email<E T="03">SectorPugetSoundWWM@uscg.mil.</E>If you have questions on viewing the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Regulatory Information</HD>

        <P>The Coast Guard is issuing this temporary final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because it would be impracticable, since the event requiring the establishment of this safety zone would be over before a comment period would end. The vessels involved in the Coast Guard Ready for<PRTPAGE P="26700"/>Operations exercise have an important and urgent need to perform this training in order to be ready to protect U.S. persons, assets, and waters; it would be impracticable to delay the exercise to allow for a comment period. The safety zone created is short in duration, and vessels can transit around it, or through it with permission of the COTP or his Designated Representative.</P>

        <P>Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the<E T="04">Federal Register</E>. Good cause exists because the event would be over before the final rule could be published. The vessels involved in this Coast Guard exercise have an important and urgent need to perform this training in order to be ready to protect U.S. persons, assets, and waters; it would be impracticable to delay this important exercise to allow for a delayed effective date.</P>
        <HD SOURCE="HD1">Background and Purpose</HD>
        <P>The Coast Guard will be conducting a Ready for Operations (RFO) exercise in the northern part of Hood Canal, WA. During the exercise, tactical vessels will be maneuvering through the Hood Canal from the entrance of Dabob Bay to Foulweather Bluff. This exercise will include fast moving surface vessels, smoke machines, and pyrotechnics. Blank ammunition, flares and LA51 warning munitions will be used during the exercise. This safety zone is being created to ensure the safety of the maritime public and vessels participating in the exercise by preventing collisions between exercising vessels and the maritime public, and by keeping the maritime public a safe distance away from potentially startling or disorienting smoke, bright flashes, and loud noises.</P>
        <HD SOURCE="HD1">Discussion of Rule</HD>
        <P>The temporary safety zone established by this rule will prohibit any person or vessel from entering or remaining within 500 yards of any vessel involved in the Coast Guard Ready for Operations exercise. Members of the maritime public will be able to identify participating vessels as those flying the Coast Guard Ensign. The COTP may also be assisted in the enforcement of the zones by other federal, state, or local agencies.</P>
        <HD SOURCE="HD1">Regulatory Analyses</HD>
        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
        <HD SOURCE="HD1">Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order.</P>
        <P>The Coast Guard bases this finding on the fact that the safety zones will be in place for a limited period of time and vessel traffic will be able to transit around the safety zones. Maritime traffic may also request permission to transit through the zones from the COTP, Puget Sound or Designated Representative.</P>
        <HD SOURCE="HD1">Small Entities</HD>
        <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
        <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule will affect the following entities, some of which may be small entities; the owners and operators of vessels intending to operate in the waters covered by the safety zone while it is in effect. The rule will not have a significant economic impact on a substantial number of small entities because the safety zone will be in place for a limited period of time and maritime traffic will still be able to transit around the safety zone. Maritime traffic may also request permission to transit though the zones from the COTP, Puget Sound or Designated Representative.</P>
        <HD SOURCE="HD1">Assistance for Small Entities</HD>
        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we offer to assist small entities in understanding the rule so that they can better evaluate its effects on them and participate in the rulemaking process.</P>
        <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD1">Collection of Information</HD>
        <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD1">Federalism</HD>
        <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism.</P>
        <HD SOURCE="HD1">Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD1">Taking of Private Property</HD>
        <P>This rule will not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD1">Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD1">Protection of Children</HD>

        <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.<PRTPAGE P="26701"/>
        </P>
        <HD SOURCE="HD1">Indian Tribal Governments</HD>
        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does 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.</P>
        <HD SOURCE="HD1">Energy Effects</HD>
        <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
        <HD SOURCE="HD1">Technical Standards</HD>
        <P>The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (e.g., specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies.</P>
        <P>This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD1">Environment</HD>

        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA)(42 U.S.C. 4321-4370f), and have concluded this action is one of a category of actions which do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (34)(g), of the Instruction. This rule involves the establishment of a safety zone. An environmental analysis checklist and a categorical exclusion determination are available in the docket where indicated under<E T="02">ADDRESSES</E>.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
          <P>Harbors, Marine safety, Navigation (water), Reporting and record keeping requirements, Security measures, Waterways.</P>
        </LSTSUB>
        
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165, as follows:</P>
        <REGTEXT PART="165" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
          </PART>
          <AMDPAR>1. The authority citation for Part 165 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1226, 1231; 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.04-1, 6.04-6, 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="165" TITLE="33">
          <AMDPAR>2. Add 165.T13-214 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 165.T13-214</SECTNO>
            <SUBJECT>Safety Zone; Coast Guard Exercise, Hood Canal, Washington</SUBJECT>
            <P>(a)<E T="03">Location.</E>The following area is a safety zone: All waters encompassed within 500 yards of any vessel that is involved in the Coast Guard Ready for Operations exercise while such vessel is transiting Hood Canal, WA between Foul Weather Bluff and the entrance to Dabob Bay. Vessels involved will be various sizes and can be identified as those flying the Coast Guard Ensign.</P>
            <P>(b)<E T="03">Regulations.</E>In accordance with the general regulations in 33 CFR Part 165, Subpart C, no person may enter or remain in the safety zone created in this rule unless authorized by the Captain of the Port or his Designated Representative. See 33 CFR Part 165, Subpart C, for additional information and requirements. Vessel operators wishing to enter the zone during the enforcement period must request permission for entry by contacting the on-scene patrol commander on VHF channel 13 or 16, or the Sector Puget Sound Joint Harbor Operations Center at (206) 217-6001.</P>
            <P>(c)<E T="03">Enforcement Period.</E>This rule will be enforced on 4:00 a.m. May 8, 2012 until 11:59 p.m. on May 10, 2012 unless canceled sooner by the Captain of the Port.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: April 6, 2012.</DATED>
          <NAME>S.J. Ferguson,</NAME>
          <TITLE>Captain, U.S. Coast Guard, Captain of the Port, Puget Sound.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10885 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
        <CFR>47 CFR Part 11</CFR>
        <DEPDOC>[EB Docket No. 04-296; FCC 12-41]</DEPDOC>
        <SUBJECT>Review of the Emergency Alert System</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Communications Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In this document, the Federal Communications Commission (Commission) amends its rules governing the Emergency Alert System (EAS) rules so that EAS Participants may, but are not required to, employ the text-to-speech (TTS) functions described in the EAS-CAP Industry Group (ECIG) Implementation Guide.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective May 7, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Lisa Fowlkes, Deputy Bureau Chief, Public Safety and Homeland Security Bureau, at (202) 418-7452, or by email at<E T="03">Lisa.Fowlkes@fcc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This is a summary of the Commission's<E T="03">Order on Reconsideration</E>in EB Docket No. 04-296, FCC 12-41, adopted and released on April 19, 2012. The full text of this document is available for inspection and copying during normal business hours in the FCC Reference Center (Room CY-A257), 445 12th Street SW., Washington, DC 20554. The complete text of this document also may be purchased from the Commission's copy contractor, Best Copy and Printing, Inc., 445 12th Street SW., Room CY-B402, Washington, DC 20554. The full text may also be downloaded at:<E T="03">www.fcc.gov.</E>
        </P>
        <HD SOURCE="HD1">Introduction</HD>
        <P>1. On January 10, 2012, the Commission released its<E T="03">Fifth Report and Order</E>in the above-referenced docket, in which it adopted rules specifying the manner in which EAS Participants must be able to receive alert messages formatted in the Common Alerting Protocol (CAP), and streamlined its part 11 rules to enhance their effectiveness and clarity. In this<E T="03">Order on Reconsideration,</E>the Commission reconsiders one aspect of the<E T="03">Fifth Report and Order:</E>the applicability of TTS specifications set<PRTPAGE P="26702"/>forth in the ECIG Implementation Guide recommendations. As discussed below, the Commission is deferring action on, rather than prohibiting, the use of the ECIG Implementation Guide's TTS specifications. Accordingly, the Commission amends its EAS rules so that EAS Participants may, but are not required to, employ the TTS functions described in the ECIG Implementation Guide.</P>
        <HD SOURCE="HD1">Background</HD>
        <P>2. In the<E T="03">Fifth Report and Order,</E>the Commission limited the scope of the new Part 11 EAS CAP-related obligations to those necessary to ensure that CAP-formatted alert messages distributed to EAS Participants will be converted into and processed in the same way as messages formatted in the current EAS Protocol. In that regard, the Commission required EAS Participants to be able to convert CAP-formatted EAS messages into messages that comply with the EAS Protocol requirements, following the procedures for such conversion as set forth in the ECIG Implementation Guide.</P>
        <P>3. Notwithstanding that the Commission mandated compliance with most of the ECIG Implementation Guide, it declined at that time to impose such a mandatory approach with respect to the ECIG Implementation Guide's provisions regarding TTS. The Commission noted, for example, that the accuracy and reliability of TTS had not been established in the record. The Commission also recognized that a regime that addressed lack of audio by focusing on the EAS Participant end—where the EAS Participants would effectuate the TTS conversion by using any of the available TTS software packages that may be configured into their EAS equipment—might be less desirable than an approach that required the message originator to make the conversion with TTS software on the originating end. Because of the need for multiple conversions using a variety of software, the former approach would be more prone to the generation of differing, and thus confusing, audio messages to be broadcast for the same EAS message. The latter approach would tend to avoid this risk by applying the conversion before the alert is widely distributed throughout the community of EAS Participants. The Commission further observed that it may consider the TTS issue in an upcoming proceeding. Accordingly, the Commission stated that it “continue[s] to believe that discussion of text-to-speech and speech-to-text software is best reserved for a separate proceeding, and [that] we therefore defer these issues at this time.”</P>
        
        <EXTRACT>
          <P>In order to avoid imposing the Guide's mandatory approach toward TTS conversions—which would have required EAS Participants to effectuate such conversions using EAS Participant-provided technologies if their EAS devices could support them—the Commission revised § 11.56 of its rules to preclude application of the Guide's mandatory requirement outright.</P>
        </EXTRACT>
        
        <P>4. The Commission also stated in the<E T="03">Fifth Report and Order</E>that “we do not permit the construction of EAS audio from a CAP text message at this time,” and noted that “we will not allow EAS Participants to use text-to-speech software configured in their EAS equipment to generate the audio portion of an EAS message.”</P>

        <P>5. On March 12, 2012, the Federal Emergency Management Agency (FEMA) made a filing, titled a “Petition for Reconsideration” (FEMA Request), requesting reversal of the Commission's decision in the<E T="03">Fifth Report and Order</E>“to deviate from the [ECIG] Implementation Guide in the matter of text-to-speech conversion.” In its request, FEMA stated that the Commission, by prohibiting use of the ECIG Implementation Guide TTS specifications “discourages and * * * limits further development of text-to-speech technology in support of EAS.” FEMA also noted that an “unintended consequence of disallowing [TTS] conversion by CAP EAS devices is that CAP messages supplied without audio content * * * may cause a CAP-EAS device to interrupt the programming of EAS participants” and only convey limited information. According to FEMA, the lack of TTS conversion capability could possibly disrupt dissemination of National Weather Service alerts, delay retrieval of referenced audio files in alerts, and impact the ability of jurisdictions with limited resources, or those with certain, already implemented CAP alerting capabilities, to issue CAP-formatted alerts. FEMA requested that the Commission delete the reference to “using text-to-speech technology” from the revised § 11.56(a)(2). The recent Final Report of Working Group 9 of the Commission's third Communications Security, Reliability and Interoperability Council (CSRIC) reiterated these same concerns. The Commission also received filings from state and local emergency management agencies and others requesting a similar change to this rule.</P>
        <HD SOURCE="HD1">Discussion</HD>
        <P>6. Upon review of the<E T="03">Fifth Report and Order,</E>and based on the observations and arguments made in various filings since release of that decision, the Commission concludes that an absolute bar against using the specifications set out in the ECIG Implementation Guide could have unintended negative consequences, such as compromising the ability of EAS Participants to receive EAS messages from states and local governments that have implemented CAP-based alerting systems that rely on TTS technologies. Moreover, such a bar would depart from the Commission's original intention to maintain a more neutral stance on the best approach for establishing TTS requirements pending fuller consideration of the issues involved. And the Commission is convinced that the merits of mandating TTS use have yet to be fully developed in the record.</P>

        <P>7. Accordingly, pursuant to § 1.108 of the its rules, on it own motion the Commission reconsiders and revises § 11.56(a)(2) of its rules to replace the parenthetical phrase “except that any and all specifications set forth therein related to using text-to-speech technology and gubernatorial `must carry' shall not be followed” with the phrase “except that any and all specifications set forth therein related to gubernatorial `must carry' shall not be followed, and that EAS Participants may adhere to the specifications related to text-to-speech on a voluntary basis.” The Commission also revises footnote 118 of the<E T="03">Fifth Report and Order</E>to delete the phrase “While we do not permit the construction of EAS audio from a CAP text message at this time  * * *” and revises footnote 496 of the<E T="03">Fifth Report and Order</E>to delete the phrase “* * * we will not allow EAS Participants to use text-to-speech software configured in their EAS equipment to generate the audio portion of an EAS message  * * *” With these revisions, the Commission hereby defers consideration of the ECIG Implementation Guide's adoption of TTS software configured in EAS equipment to generate the audio portion of an EAS message, and thus neither requires nor prohibits EAS Participants from following the ECIG Implementation Guide's specifications on use of TTS.</P>
        <HD SOURCE="HD1">I. Procedural Matters</HD>
        <HD SOURCE="HD2">A. Accessible Formats</HD>

        <P>8. To request materials in accessible formats for people with disabilities (Braille, large print, electronic files, audio format), send an email to<E T="03">fcc504@fcc.gov</E>or call the Consumer &amp; Governmental Affairs Bureau at 202-418-0530 (voice), 202-418-0432 (TTY).<PRTPAGE P="26703"/>
        </P>
        <HD SOURCE="HD2">B. Paperwork Reduction Act Analysis</HD>
        <P>9. This document contains no modified information collection requirements subject to the Paperwork Reduction Act of 1995, Public Law 104-13.</P>
        <HD SOURCE="HD2">C. Congressional Review Act</HD>
        <P>10. The Commission will send a copy of this<E T="03">Order on Reconsideration</E>in a report to be sent to Congress and the Government Accountability Office pursuant to the Congressional Review Act (“CRA”),<E T="03">see</E>5 U.S.C. 801(a)(1)(A).</P>
        <HD SOURCE="HD2">D. Effective Date of Rule</HD>

        <P>11. The Commission makes this rule revision effective immediately upon publication in the<E T="04">Federal Register</E>, pursuant to Section 553(d) of the Administrative Procedure Act. In this case, where the Commission's action removes a restriction that would have applied to EAS Participants and retains the status quo, it finds that there is no need for the 30-day period. In addition, the Commission concludes that good cause exists to make the rule effective immediately upon<E T="04">Federal Register</E>publication. In making the good cause determination, agencies must balance the necessity for immediate implementation against principles of fundamental fairness that require that all affected persons be afforded a reasonable time to prepare for the effective date of a new rule. No party will be prejudiced by an expedited effective date for this rule revision. This revision simply now provides them with the option to follow the ECIG Implementation Guide's TTS provisions should they choose to do so. However, the expedited date is necessary to provide the parties with regulatory certainty sufficiently in advance of the current June 30, 2012, deadline for complying with the relevant requirements of the Commission's<E T="03">Fifth Report and Order.</E>There is also no information collection associated with this rule revision, so no OMB approval is required for the revised rule.</P>
        <HD SOURCE="HD1">II. Final Regulatory Flexibility Analysis</HD>

        <P>12. The Regulatory Flexibility Act (RFA) requires that agencies prepare a regulatory flexibility analysis for notice-and-comment rulemaking proceedings, unless the agency certifies that “the rule will not have a significant economic impact on a substantial number of small entities.” In this<E T="03">Order on Reconsideration,</E>the Commission removes the prohibition on following the ECIG Implementation Guide's specifications related to using TTS technology, and clarifies that EAS Participants may, but are not required, to use these specifications. The Commission hereby certifies that this rule revision will not have a significant economic impact on a substantial number of small entities, because this action merely provides EAS Participants with the option to use these specifications. EAS Participants may continue to opt not to use these specifications and thereby maintain the status quo. The Commission will send a copy of this<E T="03">Order on Reconsideration,</E>including this certification, to the Chief Counsel for Advocacy of the Small Business Administration. In addition, the Commission will publish this<E T="03">Order on Reconsideration</E>(or a summary thereof) and certification in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD1">III. Ordering Clauses</HD>
        <P>13. Accordingly,<E T="03">it is ordered</E>that, pursuant to § 1.108 of the Commission's rules, 47 CFR 1.108, this Order on Reconsideration<E T="03">is adopted;</E>
        </P>
        <P>14.<E T="03">It is further ordered</E>that part 11 of the Commission's Rules, 47 CFR part 11,<E T="03">is amended</E>as set forth in the Appendix. This Order shall become effective immediately upon publication in the<E T="04">Federal Register</E>;</P>
        <P>15.<E T="03">It is further ordered</E>that the Petition for Reconsideration filed of the Federal Emergency Management Agency on March 12, 2012, in EB Docket 04-296 is dismissed as moot;</P>
        <P>16.<E T="03">It is further ordered</E>that the Commission's Consumer and Governmental Affairs Bureau, Reference Information Center,<E T="03">shall send</E>a copy of this Order on Reconsideration, including the Final Regulatory Flexibility Certification, to the Chief Counsel for Advocacy of the Small Business Administration.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 47 CFR Part 11</HD>
          <P>Radio, Television.</P>
        </LSTSUB>
        <SIG>
          <FP>Federal Communications Commission.</FP>
          <NAME>Marlene H. Dortch,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
        
        <P>For the reasons discussed in the preamble, the Federal Communications Commission amends 47 CFR part 11 as follows:</P>
        <REGTEXT PART="11" TITLE="47">
          <PART>
            <HD SOURCE="HED">PART 11—EMERGENCY ALERT SYSTEM (EAS)</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 11 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>47 U.S.C. 151, 154 (i) and (o), 303(r), 544(g) and 606.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="11" TITLE="47">
          <AMDPAR>2. Amend § 11.56 by revising paragraph (a)(2) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 11.56</SECTNO>
            <SUBJECT>Obligation to process CAP-formatted EAS messages.</SUBJECT>
            <P>(a) * * *</P>
            <P>(2) Converting EAS alert messages that have been formatted pursuant to the Organization for the Advancement of Structured Information Standards (OASIS) Common Alerting Protocol Version 1.2 (July 1, 2010), and Common Alerting Protocol, v. 1.2 USA Integrated Public Alert and Warning System Profile Version 1.0 (Oct. 13, 2009), into EAS alert messages that comply with the EAS Protocol, such that the Preamble and EAS Header Codes, audio Attention Signal, audio message, and Preamble and EAS End of Message (EOM) Codes of such messages are rendered equivalent to the EAS Protocol (set forth in § 11.31), in accordance with the technical specifications governing such conversion process set forth in the EAS-CAP Industry Group's (ECIG) Recommendations for a CAP EAS Implementation Guide, Version 1.0 (May 17, 2010) (except that any and all specifications set forth therein related to gubernatorial “must carry” shall not be followed, and that EAS Participants may adhere to the specifications related to text-to-speech on a voluntary basis). * * *</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10622 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6712-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Railroad Administration</SUBAGY>
        <CFR>49 CFR Parts 228 and 231</CFR>
        <DEPDOC>[Docket No. FRA-2004-17529; Notice No. 9]</DEPDOC>
        <RIN>RIN 2130-AB94</RIN>
        <SUBJECT>Inflation Adjustment of the Aggravated Maximum Civil Monetary Penalty for a Violation of a Federal Railroad Safety Law or Federal Railroad Administration Safety Regulation or Order; Correction</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Railroad Administration (FRA), Department of Transportation (DOT).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule; correcting amendments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>On April 24, 2012, FRA published a final rule, pursuant to the Federal Civil Penalties Inflation Adjustment Act of 1990, which increased the aggravated maximum civil monetary penalty that the agency will apply when assessing a civil penalty for a violation of a railroad safety statute, regulation, or order under its authority.<E T="03">See</E>77 FR 24416. In preparing that final<PRTPAGE P="26704"/>rule for publication, three errors were made as described in the Supplementary Information. FRA is correcting these minor errors so that the final rule clearly conforms to FRA's intent.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>The corrections to the final rule are effective on June 25, 2012.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Veronica Chittim, Trial Attorney, Office of Chief Counsel, FRA, 1200 New Jersey Avenue SE., Mail Stop 10, Washington, DC 20590 (telephone 202-493-0273),<E T="03">veronica.chittim@dot.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>Three errors were included in the final rule published on April 24, 2012.<E T="03">See</E>77 FR 24416. FRA failed to account for an October 31, 2011 amendment to 49 CFR part 228. The October 31, 2011 amendment to part 228 redesignated § 228.21, “Penalties,” as § 228.6, and removed and reserved § 228.21.<E T="03">See</E>76 FR 67073, 67087-88. In preparing the April 24, 2012, final rule for publication, FRA instructed that the numerical amount “$100,000” be removed from 49 CFR 228.21 and the numerical amount “$105,000” be added in its place. The instruction should have directed the removal of the numerical amount “$100,000” from 49 CFR 228.6 and the addition of “$105,000” in its place. Additionally, FRA inadvertently transposed two numbers, in instructions 66 and 67, by instructing changes to the numerical amounts at “213.146.A” in appendix A to part 231.<E T="03">See</E>77 FR 24416. The final rule should have instructed that the changes be made to “146.A”. FRA is correcting these minor errors so that the final rule clearly conforms to FRA's intent.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>49 CFR Part 228</CFR>
          <P>Administrative practice and procedure, Buildings and facilities, Hazardous materials transportation, Noise control, Penalties, Railroad employees, Railroad safety, Reporting and recordkeeping requirements, Sanitation.</P>
          <CFR>49 CFR Part 231</CFR>
          <P>Penalties, Railroad safety.</P>
        </LSTSUB>
        <HD SOURCE="HD1">The Final Rule</HD>
        <P>In accordance with the foregoing, parts 228 and 231, of subtitle B, chapter II of title 49 of the Code of Federal Regulations are corrected by making the following correcting amendments:</P>
        <REGTEXT PART="228" TITLE="49">
          <PART>
            <HD SOURCE="HED">PART 228—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 228 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 20103, 20107, 21101-21109; Sec. 108, Div. A, Pub. L. 110-432, 122 Stat. 4860-4866; 49 U.S.C. 21301, 21303, 21304, 21311; 28 U.S.C. 2461, note; 49 U.S.C. 103; and 49 CFR 1.49.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="228" TITLE="49">
          <SECTION>
            <SECTNO>§ 228.6</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. Section 228.6 is amended by removing the numerical amount “$100,000” and adding in its place the numerical amount “$105,000”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="231" TITLE="49">
          <PART>
            <HD SOURCE="HED">PART 231—[AMENDED]</HD>
          </PART>
          <AMDPAR>3. The authority citation for part 231 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 20102-20103, 20107, 20131, 20301-20303, 21301-21302, 21304; 28 U.S.C. 2461, note; and 49 CFR 1.49.</P>
          </AUTH>
          <HD SOURCE="HD1">Appendix A to Part 231—[Amended]</HD>
        </REGTEXT>
        
        <REGTEXT PART="231" TITLE="49">
          <AMDPAR>4. Appendix A is amended by:</AMDPAR>
          <AMDPAR>a. Removing the numerical amount “650” from the entry at 146.A and adding in its place the numerical amount “1,000”; and</AMDPAR>
          <AMDPAR>b. Removing the numerical amount “1,000” from the entry at 146.A and adding in its place the numerical amount “2,000”.</AMDPAR>
        </REGTEXT>
        <SIG>
          <DATED>Issued in Washington, DC, on May 1, 2012.</DATED>
          <NAME>Robert C. Lauby,</NAME>
          <TITLE>Acting Associate Administrator for Railroad Safety/Chief Safety Officer, Federal Railroad Administration.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10946 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <CFR>50 CFR Part 648</CFR>
        <DEPDOC>[Docket No. 110901552-1021-01]</DEPDOC>
        <RIN>RIN 0648-BB34</RIN>
        <SUBJECT>Fisheries of the Northeastern United States; Northeast Multispecies, Monkfish, Atlantic Sea Scallop; Amendment 17</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>Final rule; enforcement of collection-of-information requirements.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>NMFS announces approval by the Office of Management and Budget of collection-of-information requirements for a days-at-sea credit provision for the Northeast multispecies, monkfish, and Atlantic sea scallop fisheries. This final rule sets the enforcement date for the collection-of information requirements.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>The collection-of-information requirements in 50 CFR 648.53, 648.82, and 648.92 are enforced as of May 7, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Written comments regarding the burden-hour estimates or other aspects of the collection-of information requirements contained in this final rule may be submitted to the Northeast Regional Office, NMFS, 55 Great Republic Drive, Gloucester, MA 01930, by email to<E T="03">OIRA_Submission@omb.eop.gov,</E>or by fax to 202-395-7285.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Jason Berthiaume, Fisheries Management Specialist, 978-281-9177.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>

        <P>A final rule to implement measures in Amendment 17 to the Northeast Multispecies Fishery Management Plan was published in the<E T="04">Federal Register</E>on March 23, 2012 (77 FR 16942). That final rule contained a provision for fishing vessels to receive a credit of days-at-sea (DAS) under certain circumstances. A detailed explanation regarding the DAS credit provision is in the final rule and is not repeated here. The information collection requirements associated with the DAS credit provision were published at §§ 648.53, 648.82, and 648.92.</P>

        <P>The Office of Management and Budget (OMB) had not yet approved the collection-of-information requirements in §§ 648.53, 648.82, and 648.92 by the date the final rule was submitted to the Office of the Federal Register for publication, and thus those provisions were not enforced when that final rule published in the<E T="04">Federal Register</E>. On March 26, 2012, OMB approved the collection-of-information requirements in the rule. This final rule makes the collection-of-information requirements enforceable.</P>
        <HD SOURCE="HD1">Classification</HD>

        <P>NMFS previously solicited public comments on the measures described in the Amendment 17 proposed rule, including this collection of information, through the rulemaking process. NMFS received no comments on the collection of information requirements. Thus, this action merely implements portions of the final rule implementing Amendment 17 that were previously proposed and subjected to public comment, but that under the Paperwork Reduction Act (PRA) required OMB approval in order to become effective. OMB has now approved the collection of information provisions. Because the public has already had an opportunity to comment<PRTPAGE P="26705"/>on these provisions, an additional public comment period is unnecessary.</P>
        <P>The Assistant Administrator for Fisheries finds good cause to waive the 30-day delayed enforcement date required by 5 U.S.C. 553 and make this rule enforceable upon publication. This provision is not a restriction, but rather provides a mechanism for small entities to regain lost DAS due to circumstances that were out of their control. Although a DAS credit provision can be requested using existing information collection provisions, the revised collection of information provisions at §§ 648.53, 648.82, and 648.92 are more streamlined and will reduce the administrative burden on regulated entities. A delay in enforcement of 30 days would prevent vessels from utilizing the streamlined form and process NMFS has developed to request a DAS credit, and thus prolong the burdens on vessels.</P>
        <P>This final rule has been determined to be not significant for purposes of Executive Order 12866.</P>
        <P>Notwithstanding any other provision of the law, no person is required to respond to, and no person shall be subject to penalty for failure to comply with, a collection-of-information requirement subject to the requirements of the PRA, unless that collection-of-information displays a currently valid OMB control number. This final rule contains revisions to collection-of-information requirements subject to the PRA under OMB Control Numbers 0648-0202 and 0648-0212 and was approved by OMB on March 26, 2012.</P>
        <P>The collection of information requirements for the DAS credit provision require vessel owners to provide NMFS with an initial notification as well as the submission of a DAS credit request form. The public burden for requesting a DAS credit is estimated to average 15 min per application, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection information.</P>
        <P>Based upon permit type, a maximum of 1,908 permits holders could possibly apply for a DAS credit. With an average response time of 15 min, the total burden for applying for a DAS credit is 478 hr. This analysis was conducted assuming each permitted vessel requests one DAS credit per fishing year. Of the 1,908 permit holders, 845 are vessel monitoring system vessels and the remaining 1,063 are assumed to be either interactive voice response vessels or inactive vessels. Although the notification method depends upon the vessels reporting requirements, the associated time burdens will be similar.</P>

        <P>Send comments on these burden estimates or any other aspects of these collections-of-information, including suggestions for reducing the burden, by mail to the Northeast Regional Office (see<E T="02">ADDRESSES</E>), by email to<E T="03">OIRA_Submission@omb.eop.gov</E>or by fax to 202-395-7285.</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>16 U.S.C. 1801<E T="03">et seq.</E>
          </P>
        </AUTH>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Samuel D. Rauch III,</NAME>
          <TITLE>Acting Assistant Administrator for Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10983 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </RULE>
  </RULES>
  <VOL>77</VOL>
  <NO>88</NO>
  <DATE>Monday, May 7, 2012</DATE>
  <UNITNAME>Proposed Rules</UNITNAME>
  <PRORULES>
    <PRORULE>
      <PREAMB>
        <PRTPAGE P="26706"/>
        <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Food Safety and Inspection Service</SUBAGY>
        <CFR>9 CFR Part 424</CFR>
        <DEPDOC>[Docket No. FSIS-2011-0018]</DEPDOC>
        <RIN>RIN 0583-AD47</RIN>
        <SUBJECT>Food Ingredients and Sources of Radiation Listed and Approved for Use in the Production of Meat and Poultry Products</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food Safety and Inspection Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Food Safety and Inspection Service (FSIS) is proposing to remove sodium benzoate, sodium propionate, and benzoic acid from the list of substances that the regulations prohibit for use in meat or poultry products. Under this proposal, new uses of these substances in meat or poultry products would continue to be approved by the Food and Drug Administration (FDA) for safety and by FSIS for suitability. FSIS would add approved uses of these substances to the list of approved substances contained in the Agency's directive system.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received by July 6, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>FSIS invites interested persons to submit relevant comments on this proposed rule. Comments may be submitted by either of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>This Web site provides the ability to type short comments directly into the comment field on this Web page or attach a file for lengthier comments. Go to<E T="03">http://www.regulations.gov.</E>Follow the online instructions at that site for submitting comments.</P>
          <P>•<E T="03">Mail, including floppy disks or CD-ROMs, and hand- or courier-delivered items:</E>Send to Docket Clerk, U.S. Department of Agriculture (USDA), FSIS, OPPD, Patriots Plaza 3, 1400 Independence Avenue SW., Mailstop 3782, 8-163A, Washington, DC 20250-3700.</P>
          <P>
            <E T="03">Instructions:</E>All items submitted by mail or electronic mail must include the Agency name and docket number FSIS-2011-0018. Comments received in response to this docket will be made available for public inspection and posted without change, including any personal information, to<E T="03">http://www.regulations.gov.</E>
          </P>
          <P>
            <E T="03">Docket:</E>For access to background documents or comments received, go to the FSIS Docket Room at the address listed above between 8 a.m. and 4:30 p.m., Monday through Friday.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Charles Williams, Acting Director, Policy Issuances Division, Office of Policy and Program Development, FSIS, U.S. Department of Agriculture, 1400 Independence Avenue SW., Washington, DC 20250-3700, (202) 690-2282.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>

        <P>Under the Federal Food Drug and Cosmetics Act (FFDCA), (21 U.S.C. 301<E T="03">et seq.</E>) FDA is responsible for determining the safety of ingredients and sources of irradiation used in the production of meat and poultry products, as well as prescribing safe conditions of use. Under the Federal Meat Inspection Act (FMIA) (21 U.S.C. 601,<E T="03">et seq.</E>) and the Poultry Products Inspection Act (PPIA) (21 U.S.C. 451<E T="03">et seq.</E>), FSIS is responsible for determining the suitability of FDA-approved substances in meat and poultry products. Pursuant to a Memorandum of Understanding (MOU) that was implemented in January 2000, FDA and FSIS work together to evaluate petitions requesting the approval of new substances, or new uses of previously approved substances, for use in or on meat and poultry products. The MOU is available for viewing by the public in the FSIS docket room and on the FSIS Web site at:<E T="03">http://www.fsis.usda.gov/Regulations_&amp;_Policies/Labeling_FDA_MOU/index.asp.</E>If an ingredient is approved for use in meat or poultry products, FDA establishes the parameters of the approved use under its regulatory system. FSIS also lists the substance in FSIS Directive 7120.1, “Safe and Suitable Ingredients Used in the Production of Meat, Poultry, and Egg Products,” as part of a comprehensive listing of the substances that have been reviewed and that have been accepted as safe and suitable.</P>
        <HD SOURCE="HD1">Prohibited Substances That May Conceal Damage or Inferiority—Regulatory Requirements</HD>
        <P>The regulations that prescribe requirements for the use of food ingredients and sources of radiation in meat and poultry products prohibit for use in such products substances that conceal damage or inferiority or that make the product appear better or of greater value (9 CFR 424.23(a)). Under the regulations, certain antimicrobial substances are prohibited for use in meat or poultry products because these substances have the potential to conceal damage or inferiority when used at certain levels (9 CFR 424.23(a)(3)). Among these substances are potassium sorbate, propylparaben (propyl p-hydroxybenzoate), calcium propionate, sodium propionate, benzoic acid, and sodium benzoate. The regulations provide that these substances “* * * may be used in or on any product, only as provided in 9 CFR Chapter III” (9 CFR 424.23(a)(3)). Thus, while FSIS lists approved uses of other substances in its directive system, the Agency must codify any approved use of the substances listed in 9 CFR 424.23(a)(3) in the meat or poultry products inspection regulations.</P>
        <HD SOURCE="HD1">Waivers of Regulatory Requirements</HD>
        <P>The meat and poultry products inspection regulations provide for the FSIS Administrator to “* * * waive for limited periods any provisions of the regulations * * * to permit * * * experimentation so that new procedures, equipment, and/or processing techniques may be tested to facilitate definite improvements” (9 CFR 303.1(h) and 381.3(b)). Under the regulations, FSIS may only grant waivers from the provisions in the regulations that are not in conflict with the purposes or provisions of the FMIA or PPIA (9 CFR 303.1(h) and 381.3(b)).</P>

        <P>FSIS decides whether to grant requests for waivers after considering proposals and documentation submitted by establishments to demonstrate that the use of a new technology is scientifically sound; that it will facilitate definite improvements; and that issuing the waiver will not conflict with the provisions of the FMIA or PPIA, i.e., the conditions of use will not<PRTPAGE P="26707"/>result in an adulterated product or product labeling that misleads consumers.<SU>1</SU>
          <FTREF/>If FSIS determines that the information submitted by an establishment supports the requested waiver, the Agency will waive the relevant provisions in the regulation for a limited period of time to allow the establishment to conduct an in-plant trial. The purpose of the in-plant trial is to gather data on the effects of the use of the new technology. FSIS reviews the data that are developed in the trial to determine whether they show that the purpose of the waiver is being met.</P>
        <FTNT>
          <P>
            <SU>1</SU>For Agency New Technology waiver procedures, see<E T="03">http://www.fsis.usda.gov/Regulations_&amp;_Policies/New_Technologies/index.asp.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD1">Petitions</HD>

        <P>On January 19, 2007, Kraft Foods Global, Inc. petitioned FSIS to amend the Federal meat and poultry products inspection regulations to permit the use of sodium benzoate and sodium propionate as acceptable antimicrobial agents that may be used in combination with other approved ingredients to inhibit the growth of<E T="03">Listeria monocytogens</E>(<E T="03">Lm</E>) in ready-to-eat (RTE) meat and poultry products. Kraft requested that FSIS permit the use of sodium benzoate in amounts of up to 0.1 percent (by weight of total product formulation) in combination with approved antimicrobial agents. Kraft requested that FSIS permit the use of sodium propionate in amounts up to 0.2 percent (by weight of total formulation) in combination with approved antimicrobial agents and adjuvants.</P>
        <P>On July 26, 2010, Kemin Food Technologies petitioned FSIS to amend the regulations to permit the use of liquid sodium propionate and liquid sodium benzoate as acceptable antimicrobial agents in meat and poultry products. Kemin requested that FSIS approve the use of liquid sodium propionate to inhibit microbial growth in various meat and poultry products in amounts of up to 0.5 percent by weight of total product formulation. Kemin also requested that FSIS approve the use of liquid sodium propionate and sodium benzoate to prohibit microbial growth in various meat and poultry products in amounts of up to 0.4 percent by weight of total formulation, whereas liquid sodium benzoate will not exceed 0.1 percent of product formulation.</P>
        <P>After receiving each petition, FSIS conducted an initial evaluation of the requested action to confirm that FDA had no objections to the safety of sodium benzoate, sodium propionate, or benzoic acid at the proposed levels of use. FSIS also considered each petition's supporting data on the suitability of these substances for use in meat and poultry products. From its initial evaluation of each petition, FSIS, in consultation with FDA, concluded that the petitioners had established the safety of sodium benzoate, sodium propionate, and benzoic acid at the proposed levels of use but that the Agency needed additional data to make a final suitability determination.</P>

        <P>Therefore, in July 2007, FSIS issued a waiver to Kraft to conduct trials in 59 of its establishments on the use of sodium benzoate and sodium propionate, in combination with other ingredients, to control the growth of<E T="03">Lm</E>in RTE meat and poultry products. Additionally, from September 2010 through March 2011, FSIS issued waivers to various meat and poultry products processing establishments to conduct trials on the use of antimicrobial agents containing liquid sodium propionate and propionic acid supplied by Kemin for<E T="03">Lm</E>control in RTE meat and poultry products. FSIS granted the waivers to allow the companies to gather additional data on the suitability of these substances to support an amendment to the regulations.</P>
        <P>As a condition of the waivers, both Kraft and Kemin were to track issues regarding consumer acceptance of products containing the substances at issue during the trial period and to identify any situations that resulted in consumer concerns about the products. The waivers also provided that both companies were to collect data to show that normal spoilage indicators are not masked in products treated with the substances, that nutrients are not adversely affected, and that product appearance (e.g., color) did not change when compared with untreated products. Another condition of the waivers was that the meat and poultry products formulated with the subject ingredients have an approved label that includes an accurate declaration of the ingredients in the appropriate order of predominance.</P>
        <P>While operating under the waivers, both companies gathered sufficient data to support the use of sodium propionate, sodium benzoate, and benzoic acid as antimicrobial agents in RTE meat and poultry products. Accordingly, FSIS is initiating this rulemaking proposing to remove these substances from the list of substances prohibited for use in meat or poultry products. Should FSIS finalize this proposed rule, the Agency will list approved uses of these substances in FSIS Directive 7120.1. FSIS has extended the companies' regulatory waivers for the use of these substances pending the conclusion of this rulemaking.</P>
        <HD SOURCE="HD1">Data on Suitability</HD>
        <P>To demonstrate that sodium benzoate, sodium propionate, and benzoic acid are suitable for their intended use as antimicrobial agents in meat and poultry products, Kraft submitted data collected from its in-plant-trials and from scientific studies that show that these substances do not conceal damage or inferiority or make products appear better or of greater value than they are under the proposed conditions of use.</P>

        <P>Kraft submitted research findings to demonstrate that its proposed use of sodium benzoate and sodium propionate is effective in controlling the growth of<E T="03">Lm</E>in RTE meat and poultry products. The research took into account the unique composition of diverse products, such as hot dogs, bologna, ham, and turkey breast. Kraft developed an approach to predicting the effect of antimicrobial ingredients on<E T="03">Lm</E>growth and confirmed the findings with tests of different formulations. Kraft assessed treated products for quality, analyzed the nutritional composition of planned formulations, and considered the status of sodium benzoate and sodium propionate as generally recognized as safe (GRAS) substances under FDA requirements. Kraft's research demonstrated that differences in product composition, especially moisture, can influence antimicrobial activity and formulation needs. From its study, Kraft determined that the following formulations for the antimicrobial ingredients are effective in controlling the growth of<E T="03">Lm:</E>
        </P>
        <P>(1) A combination of 0.1 percent sodium benzoate and 0.1 percent sodium diacetate in some lower moisture products such as hot dogs;</P>
        <P>(2) A combination of 0.1 percent sodium benzoate, 0.15 percent sodium diacetate, and 0.2 percent sodium propionate in high moisture products such as ham; and</P>
        <P>(3) A combination of 0.1 percent sodium benzoate, 0.15 percent sodium diacetate, 0.2 percent sodium propionate, and 0.56 percent Lem-O-Fos® in turkey.</P>

        <P>In addition, Kraft submitted three studies to address concerns about the potential use of the substances to conceal damage or mask inferiority. First, Kraft assessed whether the proposed uses of sodium benzoate and sodium propionate would affect normal indicators of spoilage. The results of two shelf life studies on the spoilage issue showed that there was very little<PRTPAGE P="26708"/>difference in spoilage characteristics among products formulated with the antimicrobial treatments being evaluated and products formulated without antimicrobials. Second, Kraft conducted a nutritional composition test for moisture, protein, fat, ash, and sodium content. Other than a reduction in ash and an increase in moisture as lactate solids are replaced by water, the study found no differences in nutritional composition between products treated with the substances and untreated products. Finally, Kraft evaluated the efficacy and spoilage characteristics of sodium benzoate and sodium propionate in vacuum packaging or modified atmosphere packaging with nitrogen and carbon dioxide and found that the type of packaging did not have a technical effect on the efficacy and spoilage characteristics of sodium benzoate and sodium propionate. Furthermore, Kraft conducted consumer research to demonstrate that there is consumer acceptance, that normal spoilage indicators were not masked, that nutrients were not adversely affected, and that product appearance was not changed as compared to untreated product. The Kraft petition and supporting material are available for viewing by the public on the FSIS Web site at:<E T="03">http://www.fsis.usda.gov/PDF/Petition_Kraft.pdf.</E>
        </P>

        <P>In its petition, Kemin submitted data collected from in-house trials and university research that demonstrate that its proposed applications of ≤ 0.5 percent liquid sodium propionate alone or ≤ 0.4 percent for the liquid blend of sodium propionate with benzoate are effective in controlling the growth of<E T="03">Lm</E>in cured turkey and cooked chicken breast. Kemin noted that a comparison of test results with previous studies and predictive models suggests that moisture, pH, NaCl, added nitrite, storage temperature, and perhaps meat type, are significant factors in determining the efficacy of various antimicrobials. The petition explained that validation of the most effective use rates of any antimicrobial treatments will need to be performed on a case-by-case basis to account for many variables that can affect microbial growth and efficacy in specific RTE meat and poultry products.</P>
        <P>To show that its proposed uses of liquid sodium propionate alone or in a blend with sodium benzoate do not conceal damage or inferiority when used in meat or poultry products, Kemin conducted studies to demonstrate that the use of these substances does not affect normal spoilage indicators in RTE poultry products. The studies compared products containing Kemin's antimicrobial treatments at use rates of 0.3, 0.4, and 0.5 percent sodium propionate alone, or 0.4 percent when combined with sodium benzoate, with an untreated control or a product containing the current industry standard lactate. The studies showed that, although growth of spoilage microorganisms was significantly different in products from replicate trials, the competitive microflora did not appear to have been affected by Kemin's antimicrobial substances, and normal spoilage indicators were not disguised. In addition, Kemin submitted data to demonstrate that proposed uses of liquid sodium propionate alone or in a blend with sodium benzoate do not negatively affect color, texture and other sensory attributes, nutritional profile, or consumer acceptance when used at rates of up to 0.5 percent alone or 0.4 percent with sodium benzoate.</P>

        <P>The Kemin petition and supporting material are available for viewing by the public on the FSIS Web site at<E T="03">http://www.fsis.usda.gov/PDF/Petition_Kemin.pdf.</E>
        </P>
        <HD SOURCE="HD1">Proposed Rule</HD>
        <P>FSIS has reviewed the data that Kraft and Kemin have submitted in support of their petitions and has determined that sodium benzoate, sodium propionate, and benzoic acid, under the conditions proposed in the petitions, are both safe and suitable for use as antimicrobial agents in certain RTE meat and poultry products. Therefore, FSIS is proposing to amend 9 CFR 424.23(a)(3) to remove these substances from the list of prohibited substances that may be used “* * * in or on any product, only as provided in 9 CFR Chapter III.”</P>

        <P>If this proposed rule is finalized, use of these substances in or on meat or poultry products will continue to be approved by FDA for safety and by FSIS for suitability. FDA will continue to establish the parameters of the approved use under its regulatory system, and FSIS will list approved uses of these substances in the table of approved substances in Directive 7120.1. The proposed amendment will make the procedures for listing approved uses of sodium propionate, benzoic acid, and sodium benzoate consistent with the procedures for listing other safe and suitable substances. This proposed rule will also expedite the listing of substances, such as sodium benzoate and sodium propionate, which enhance food safety by controlling<E T="03">Lm</E>in RTE products.</P>
        <P>FSIS is not proposing to remove potassium sorbate, propylparaben (propyl p-hydroxybenzoate), and calcium propionate from the list of prohibited substances in 9 CFR 424.23(a)(3) because the petitions did not include data on the use of these substances in meat or poultry products. Therefore, if this proposed rule is finalized, approved new uses of potassium sorbate, propylparaben (propyl p-hydroxybenzoate), and calcium propionate would continue to be listed through rulemaking. FSIS requests comments and supporting data on whether the Agency should remove any of these substances from 9 CFR 424.23(a)(3) and list their approved new uses in FSIS Directive 7120.1.</P>
        <HD SOURCE="HD1">Executive Order 12866, Executive Order 13563, and Regulatory Flexibility Act</HD>
        <P>Executive Orders 13563 and 12866 direct 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). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This proposed rule has been determined to be not significant and therefore has not been reviewed by the Office of Management and Budget (OMB) under EO 12866.</P>

        <P>This proposed rule would eliminate the need for FSIS to conduct rulemakings each time that the use of certain substances identified in § 424.23(a)(3), i.e., sodium propionate, sodium benzoate, and benzoic acid, is found to be safe by FDA and suitable by FSIS for use in the production of meat and poultry products at specified levels. This proposed rule would benefit companies that want to use these substances in the production of meat and poultry products by expediting the approval process. It would also benefit consumers by expediting the approved use of substances that enhance food safety by controlling the growth of<E T="03">Lm</E>in RTE meat and poultry products. This proposed rule would make the approval process for new uses of sodium propionate, sodium benzoate, and benzoic acid in meat and poultry products consistent with the process for obtaining approval for other safe and suitable substances.</P>

        <P>There are no expected costs associated with this proposed rule. All substances intended for use in the production of meat and poultry<PRTPAGE P="26709"/>products will continue to be subject to FDA evaluation for safety and FSIS evaluation for suitability. Company costs and the agencies' costs associated with these evaluations will not be affected by this proposed rule should it become final. The only change would be the process for listing the substances specified in this proposal after they have been approved.</P>
        <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
        <P>Pursuant to section 605(b) of the Regulatory Flexibility Act, 5 U.S.C. 605(b), the FSIS Administrator has made a preliminary determination that this proposed rule will not have a significant impact on a substantial number of small entities. This determination is based primarily on the fact that the proposed rule would not affect the process for approving new uses of sodium benzoate, sodium propionate, and benzoic acid in meat or poultry products. This proposed rule would make the process of listing approved uses of these substances more efficient by eliminating the need for FSIS to conduct rulemaking each time a new use is approved.</P>
        <HD SOURCE="HD1">Paperwork Reduction Act</HD>

        <P>This rule does not contain any new information collection or record keeping requirements that are subject to the Office of Management and Budget (OMB) approval under the Paperwork Reduction Act, 44 U.S.C. 3501,<E T="03">et seq.</E>
        </P>
        <HD SOURCE="HD1">E-Government Act</HD>

        <P>FSIS and USDA are committed to achieving the purposes of the E-Government Act (44 U.S.C. 3601,<E T="03">et seq.</E>) by, among other things, promoting the use of the Internet and other information technologies and providing increased opportunities for citizen access to Government information and services, and for other purposes.</P>
        <HD SOURCE="HD1">Executive Order 12988</HD>
        <P>This proposed rule has been reviewed under Executive Order 12988, Civil Justice Reform. This proposed rule: (1) Has no retroactive effect; and (2) does not require administrative proceedings before parties may file suit in court challenging this rule. However, the administrative procedures specified in 9 CFR 306.5, 381.35, and 590.300 through 590.370, respectively, must be exhausted before any judicial challenge may be made of the application of the provisions of the proposed rule, if the challenge involves any decision of an FSIS employee relating to inspection services provided under the FMIA, PPIA, or EPIA.</P>
        <HD SOURCE="HD1">Additional Public Notification</HD>

        <P>FSIS will announce the availability of this proposed rule on-line through the FSIS Web page located at<E T="03">http://www.fsis.usda.gov/regulations_&amp;_policies/Federal_Register_Proposed_Rules/index.asp.</E>
        </P>
        <P>FSIS also will make copies of this<E T="04">Federal Register</E>publication available through the<E T="03">FSIS Constituent Update,</E>which is used to provide information regarding FSIS policies, procedures, regulations,<E T="04">Federal Register</E>notices, FSIS public meetings, and other types of information that could affect or would be of interest to our constituents and stakeholders. The<E T="03">Update</E>is communicated via Listserv, a free email subscription service for industry, trade, and farm groups, consumer interest groups, allied health professionals, scientific professionals, and other individuals who have requested to be included. The<E T="03">Update</E>also is available on the FSIS Web page. Through Listserv and the Web page, FSIS is able to provide information to a much broader, more diverse audience.</P>

        <P>In addition, FSIS offers an email subscription service which provides automatic and customized access to selected food safety news and information. This service is available at<E T="03">http://www.fsis.usda.gov/news_and_events/email_subscription/.</E>Options range from recalls to export information to regulations, directives, and notices. Customers can add or delete subscriptions themselves, and have the option to password-protect their accounts.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 9 CFR Part 424</HD>
          <P>Food additives, Food packaging, Meat inspection, Poultry and poultry products.</P>
        </LSTSUB>
        
        <P>For the reasons set forth in the preamble, FSIS proposes to amend 9 CFR part 424 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 424—PREPARATION AND PROCESSING OPERATIONS</HD>
          <P>1. The authority citation for part 424 would continue to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 450, 1901-1906; 21 U.S.C. 451-470, 601-695; 7 CFR 2.18, 2.53.</P>
          </AUTH>
          
          <P>2. Revise § 424.23(a)(3) as follows:</P>
          <SECTION>
            <SECTNO>§ 424.23</SECTNO>
            <SUBJECT>Prohibited uses.</SUBJECT>
            <STARS/>
            <P>(a) * * *</P>
            <P>(3) Sorbic acid, calcium sorbate, sodium sorbate, and other salts of sorbic acid shall not be used in cooked sausages or any other meat; sulfurous acid and salts of sulfurous acid shall not be used in or on any meat; and niacin or nicotinamide shall not be used in or on fresh meat product; except that potassium sorbate, propylparaben (propyl p-hydroxybenzoate), and calciumpropionate, may be used in or on any product, only as provided in 9 CFR chapter III.</P>
            <STARS/>
          </SECTION>
          <SIG>
            <DATED>Done at Washington, DC, on May 1, 2012.</DATED>
            <NAME>Alfred V. Almanza,</NAME>
            <TITLE>Administrator.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10871 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-DM-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">COMMODITY FUTURES TRADING COMMISSION</AGENCY>
        <CFR>17 CFR Part 49</CFR>
        <RIN>RIN 3038-AD83</RIN>
        <SUBJECT>Swap Data Repositories: Interpretative Statement Regarding the Confidentiality and Indemnification Provisions of Section 21(d) of the Commodity Exchange Act</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Commodity Futures Trading Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed interpretative statement.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Commodity Futures Trading Commission (“Commission” or “CFTC”) is proposing this interpretative statement to provide guidance regarding the applicability of the confidentiality and indemnification provisions set forth in new section 21(d) of the Commodity Exchange Act (“CEA”) added by section 728 of the Dodd-Frank Wall Street Reform and Consumer Protection Act (“Dodd-Frank Act”). The Commission requests comment on all aspects of the proposed interpretative statement. The proposed interpretative statement clarifies that the provisions of section 21(d) should not operate to inhibit or prevent foreign regulatory authorities from accessing data in which they have an independent and sufficient regulatory interest, even if that data also has been reported pursuant to the CEA and Commission regulations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received on or before June 6, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Comments, identified by RIN number 3038-AD83, may be sent by any of the following methods:</P>
          <P>•<E T="03">Agency Web site, via its Comments Online process:</E>
            <E T="03">http://comments.cftc.gov.</E>Follow the instructions for submitting comments through the Web site.</P>
          <P>•<E T="03">Mail:</E>David A. Stawick, Secretary of the Commission, Commodity Futures<PRTPAGE P="26710"/>Trading Commission, Three Lafayette Centre, 1155 21st Street NW., Washington, DC 20581.</P>
          <P>•<E T="03">Hand Delivery/Courier:</E>Same as mail above.</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Adedayo Banwo, Counsel, Office of the General Counsel, at (202) 418.6249,<E T="03">abanwo@cftc.gov;</E>With respect to questions relating to international consultation and coordination: Jacqueline Mesa, Director, Office of International Affairs, at (202) 418.5386,<E T="03">jmesa@cftc.gov</E>, Commodity Futures Trading Commission, Three Lafayette Centre, 1155 21st Street NW., Washington, DC 20581.</P>

          <P>All comments must be submitted in English, or if not, accompanied by an English translation. Comments will be posted as received to<E T="03">http://www.cftc.gov.</E>You should submit only information that you wish to make available publicly. If you wish the Commission to consider information that may be exempt from disclosure under the Freedom of Information Act (“FOIA”),<SU>1</SU>
            <FTREF/>a petition for confidential treatment of the exempt information may be submitted according to the procedures established in § 145.9 of the CFTC's regulations.<SU>2</SU>

            <FTREF/>The Commission reserves the right, but shall have no obligation, to review, prescreen, filter, redact, refuse, or remove any or all of your submission from<E T="03">http://www.cftc.gov</E>that it may deem to be inappropriate for publication, such as obscene language. All submissions that have been redacted or removed that contain comments on the merits of the rulemaking will be retained in the public comment file and will be considered as required under the Administrative Procedure Act and other applicable laws, and may be accessible under FOIA.</P>
          <FTNT>
            <P>
              <SU>1</SU>5 U.S.C. 552.</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>2</SU>17 CFR 145.9.</P>
          </FTNT>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>In this release, the Commission addresses issues raised by foreign regulators with respect to the scope and application of the confidentiality and indemnification provisions of new section 21(d) of the CEA and proposes to clarify that these provisions should not operate to inhibit or prevent foreign regulatory authorities from accessing data in which they have an independent and sufficient regulatory interest.</P>
        <HD SOURCE="HD1">I. Background: Statutory and Regulatory Authorities</HD>
        <P>On July 21, 2010, President Obama signed into law the Dodd-Frank Act.<SU>3</SU>
          <FTREF/>Title VIIamended the CEA to establish a comprehensive new regulatory framework for swaps and security-based swaps.<SU>4</SU>
          <FTREF/>The legislation was enacted to reduce risk, increase transparency and promote market integrity within the financial system by, among other things: (1) Providing for the registration and comprehensive regulation of swap dealers and major swap participants; (2) imposing clearing and trade execution requirements on standardized derivative products; (3) creating robust recordkeeping and real-time reporting regimes; and (4) enhancing the Commission's rulemaking and enforcement authorities with respect to, among others, all registered entities and intermediaries subject to the Commission's oversight.</P>
        <FTNT>
          <P>
            <SU>3</SU>
            <E T="03">See</E>Dodd-Frank Wall Street Reform and Consumer Protection Act, Pub. L. 111-203, 124 Stat. 1376 (2010), available at<E T="03">http://www.cftc.gov/LawRegulation/OTCDERIVATIVES/index.htm.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>

            <SU>4</SU>Pursuant to section 701 of the Dodd-Frank Act, Title VII may be cited as the “Wall Street Transparency and Accountability Act of 2010;” 7 U.S.C. 1<E T="03">et seq.</E>
          </P>
        </FTNT>
        <P>To enhance transparency, promote standardization and reduce systemic risk, section 727 of the Dodd-Frank Act added to the CEA new section 2(a)(13)(G),<SU>5</SU>
          <FTREF/>which requires all swaps—whether cleared or uncleared—to be reported to swap data repositories (“SDRs”).SDRs are new registered entities created by section 728 of the Dodd-Frank Act.<SU>6</SU>
          <FTREF/>SDRs are required to perform specified functions related to the collection and maintenance of swap transaction data and information.<SU>7</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>5</SU>7 U.S.C. 2(a)(13)(G).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>6</SU>Section 721 of the Dodd-Frank Act amends section 1a of the CEA to add a definition of the term “swap data repository.” Pursuant to CEA section 1a(48), the term “swap data repository means any person that collects and maintains information or records with respect to transactions or positions in, or the terms and conditions of, swaps entered into by third parties for the purpose of providing a centralized recordkeeping facility for swaps.” 7 U.S.C. 1a(48).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>7</SU>
            <E T="03">See</E>7 U.S.C. 24a(c).<E T="03">See also</E>Commission, Final Rulemaking: Swap Data Recordkeeping and Reporting Requirements, 77 FR 2136, Jan. 13, 2012 (“Data Final Rules”). The Data Final Rules, among other things, set forth regulations governing SDR data collection and reporting responsibilities under part 45 of the Commission's regulations.</P>
        </FTNT>
        <P>CEA section 21(c)(7) requires that SDRs make data available to certain domestic and foreign regulators<SU>8</SU>
          <FTREF/>under specified circumstances.<SU>9</SU>
          <FTREF/>Separately, section 21(d) mandates that prior to receipt of any requested data or information from an SDR, a regulatory authority described in section 21(c)(7) shall agree in writing to abide by the confidentiality requirements described in section 8 of the CEA,<SU>10</SU>
          <FTREF/>and to indemnify the SDR and the Commission for any expenses arising from litigation relating to the information provided under section 8 of the CEA.<SU>11</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>8</SU>The Commission's regulations designate such regulators as either an “Appropriate Domestic Regulator” or an “Appropriate Foreign Regulator” in § 49.17(b).<E T="03">See</E>Commission, Final Rulemaking: Swap Data Repositories: Registration Standards, Duties and Core Principles, 76 FR 54538, 54554 Sept. 1, 2011 (“SDR Final Rules”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>9</SU>7 U.S.C. 24a(c)(7).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>7 U.S.C. 12.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>11</SU>7 U.S.C. 24a(d).</P>
        </FTNT>
        <P>Section 752 of the Dodd-Frank Act seeks to “promote effective and consistent global regulation of swaps,” and provides that the CFTC and foreign regulators “may agree to such information-sharing arrangements as may be deemed to be necessary or appropriate in the public interest. * * *”<SU>12</SU>
          <FTREF/>In light of this statutory directive, the Commission has been working to provide sufficient access to SDR data to appropriate domestic and foreign regulatory authorities.</P>
        <FTNT>
          <P>
            <SU>12</SU>
            <E T="03">See</E>section 752(a) of the Dodd-Frank Act.</P>
        </FTNT>
        <P>On June 8, 2011, the Chairman of the CFTC and the Chairman of the Securities and Exchange Commission (“Chairmen”) jointly submitted a letter to Michel Barnier, European Commissioner for Internal Markets and Services,<SU>13</SU>
          <FTREF/>highlighting their desire for international cooperation. In the letter, the Chairmen expressed their belief that indemnification and notice requirements need not apply when a registered SDR is also registered in a foreign jurisdiction and the foreign regulator, acting within the scope of its jurisdiction, seeks information directly from the SDR.</P>
        <FTNT>
          <P>
            <SU>13</SU>
            <E T="03">See</E>letter from Gary Gensler, Chairman of the Commission, and Mary Schapiro, Chairman of the SEC, to Michel Barnier, European Commissioner for Internal Markets and Services, European Commission, dated June 8, 2011.</P>
        </FTNT>
        <P>On September 1, 2011, the Commission adopted regulations implementing CEA section 21's registration standards, duties, and core principles for SDRs. To implement the provisions of section 21(c)(7) and (d), the Commission adopted definitions and standards for determining access by domestic and foreign regulators to data maintained by SDRs.</P>
        <P>The Commission acknowledged in the SDR Final Rules that the CEA's indemnification requirement could have the unintended effect of inhibiting direct access by other regulators to data maintained by SDRsdue to various home country laws and regulations.<SU>14</SU>
          <FTREF/>The SDR Final Rulesprovided that<PRTPAGE P="26711"/>under specified circumstances, certain “Appropriate Domestic Regulators”<SU>15</SU>
          <FTREF/>may gain access to the swap data reported and maintained by SDRs without being subject to the notice and indemnification requirements of CEA sections 21(c)(7) and (d).<SU>16</SU>
          <FTREF/>In connection with foreign regulatory authorities, the Commission determined in the SDR Final Rules that confidential swap data reported to and maintained by an SDR may be accessed by an Appropriate Foreign Regulator<SU>17</SU>
          <FTREF/>without the execution of a confidentiality and indemnification agreement when the Appropriate Foreign Regulator has supervisory authority over an SDR registered with it pursuant to foreign law and/or regulation that is also registered with the Commission.</P>
        <FTNT>
          <P>
            <SU>14</SU>
            <E T="03">See</E>SDR Final Rules at 54554.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>15</SU>The term Appropriate Domestic Regulator is defined in 17 CFR 49.17(b)(1) as the Securities and Exchange Commission; each prudential regulator identified in section 1a(39) of the CEA. 7 U.S.C. 1a(39); the financial Stability Oversight Council; the Department of Justice; any Federal Reserve Bank; the Office of Financial Research; and any other person the Commission deems appropriate.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>16</SU>In the Commission's view, it is appropriate to permit access to the swap data maintained by SDRs to Appropriate Domestic Regulators that have concurrent regulatory jurisdiction over such SDRs, without the application of the notice and indemnification provisions of sections 21(c)(7) and (d) of the CEA.<E T="03">See</E>SDR Final Rules at 54554 n.163. Accordingly, these provisions do not apply to an Appropriate Domestic Regulator that has regulatory jurisdiction over an SDR registered with it pursuant to a separate statutory authority that is also registered with the Commission, if the Appropriate Domestic Regulator executes an MOU or similar information sharing arrangement with the Commission and the Commission, consistent with CEA section 21(c)(4)(A), designates the Appropriate Domestic Regulator to receive direct electronic access.<E T="03">See</E>17 CFR 17(d)(2).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>17</SU>The term Appropriate Foreign Regulator is defined in 17 CFR 49.17(b)(2) as a foreign regulator with an existing memorandum of understanding (“MOU”) or similar type of information sharing arrangement executed with the Commission, and/or a foreign regulator without an MOU as determined on a case-by-case basis by the Commission.</P>
        </FTNT>
        <P>The confidentiality and indemnification provisions of new CEA section 21 apply only when a regulatory authority seeks access to data from an SDR. In the SDR Final Rules, the Commission noted that section 8(e) of the CEA provides for the Commission (as opposed to an SDR) to share confidential information in its possession with any department or agency of the Government of the United States, or with any foreign futures authority, department or agency of any foreign government or political subdivision thereof,<SU>18</SU>
          <FTREF/>acting within the scope of its jurisdiction.<SU>19</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>18</SU>Section 725(f) of the Dodd-Frank Act amended section 8(e) of the CEA to include foreign central banks and ministries.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>19</SU>
            <E T="03">See</E>SDR Final Rules at 54554.</P>
        </FTNT>
        <P>The SDR Final Rules became effective on October 31, 2011.<SU>20</SU>
          <FTREF/>Under these rules, trade repositories may apply to the Commission for full registration as SDRs.Pending the adoption and effectiveness of other, related regulatory provisions and definitions, however, such registrations are deemed “provisional.”<SU>21</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>20</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>21</SU>
            <E T="03">See</E>17 CFR 49.3(b).</P>
        </FTNT>
        <HD SOURCE="HD1">II. Considerations Relevant to the Commission's Proposed Interpretative Statement<SU>22</SU>
          <FTREF/>
        </HD>
        <FTNT>
          <P>
            <SU>22</SU>Legislation has been introduced in Congress that would amend the CEA to eliminate or substantially limit the SDR indemnification provision.</P>
        </FTNT>
        <HD SOURCE="HD2">A. International Considerations</HD>

        <P>As noted above, section 752(a) of the Dodd-Frank Act directs the Commission to consult and coordinate with foreign regulatory authorities regarding the establishment of consistent international standards for the regulation of swaps and various “swap entities.” Section 752(a) also provides that the Commission “may agree to such information-sharing arrangements [<E T="03">with foreign regulatory authorities</E>] as may be deemed to be necessary or appropriate in the public interest” or for the protection of investors and counterparties.<SU>23</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>23</SU>
            <E T="03">See</E>section 752(a) of the Dodd-Frank Act.</P>
        </FTNT>
        <P>The Commission is committed to a cooperative international approach to the registration and regulation of SDRs, and consulted extensively with various foreign regulatory authorities in promulgating both its proposed and final regulations concerning SDRs.<SU>24</SU>
          <FTREF/>The Commission notes that the SDR Final Rules are largely consistent with the recommendations and goals of the May 2010 “CPSS-IOSCO Consultative Report, Considerations for Trade Repositories in the OTC Derivatives Market” (“Working Group Report”).<SU>25</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>24</SU>
            <E T="03">See</E>public comment file in response to the proposal for the SDR Final Rules, available at<E T="03">http://comments.cftc.gov/PublicComments/CommentList.aspx?id=939</E>and SDR Final Rules note 6 at 54539,<E T="03">supra.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>

            <SU>25</SU>This working group was jointly established by the Committee on Payment and Settlement Systems (“CPSS”) of the Bank of International Settlements and the Technical Committee of the International Organization of Securities Commissions (“IOSCO”). The Working Group Report presented a set of factors to consider in connection with the design, operation and regulation of SDRs. A significant focus of the Working Group Report is access to SDR data by appropriate regulators. The Working Group Report urges that a trade repository “should support market transparency by making data available to relevant authorities and the public in line with their respective information needs.” The Working Group Report is available at<E T="03">http://www.bis.org/publ/cpss90.pdf.</E>
            <E T="03">See also</E>CPSS-IOSCO Consultative Report, Principles of Financial Market Infrastructures (March 2011) available at<E T="03">http://www.bis.org/publ/cpss94.pdf.</E>
            <E T="03">See also</E>Financial Stability Board (“FSB”), Implementing OTC Derivatives Market Reforms, Oct. 25, 2010 (“FSB Report”); FSB, Derivative Market Reforms, Progress Report on Implementation, Apr. 15, 2010 (“FSB Progress Report”).</P>
        </FTNT>
        <HD SOURCE="HD2">B. Public Comments on SDR Regulations</HD>
        <P>In developing the SDR Final Rules, the Commission received several comments regarding access to SDR data by foreign regulatory authorities and the confidentiality and indemnification provisions of CEA section 21(d). The Commission has considered these comments in formulating this proposed interpretation but requests further comment concerning the specific interpretative statement proposed.</P>
        <P>Managed Funds Association (“MFA”) requested that the Commission actively participate in facilitating foreign regulatory access and confirming a foreign regulator's authority in connection with any SDR data request.<SU>26</SU>
          <FTREF/>The CME Group Inc. (“CME”) argued against the Commission designating any third party to receive swap data, and TriOptima suggested that the Commission “adopt as flexible an interpretation as possible” regarding the indemnification provisions in CEA section 21(d).<SU>27</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>26</SU>
            <E T="03">See</E>comment letter from MFA.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>27</SU>
            <E T="03">See</E>comment letters from CME and TriOptima.</P>
        </FTNT>
        <P>The Depository Trust &amp; Clearing Corporation (“DTCC”) stated that the “indemnification provisions should not apply in situations where regulators are carrying out regulatory responsibilities, acting in a manner consistent with international agreements and maintaining the confidentiality of data.”<SU>28</SU>
          <FTREF/>Additionally, the Commission received a comment letter from the European Securities and Markets Authority (“ESMA”)<SU>29</SU>
          <FTREF/>stating that it believes the indemnification provision “undermines” principles of trust and consultation.</P>
        <FTNT>
          <P>
            <SU>28</SU>
            <E T="03">See</E>comment letter from DTCC.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>29</SU>
            <E T="03">See</E>comment letter from ESMA.</P>
        </FTNT>
        <HD SOURCE="HD2">C. Consultations With Foreign Regulatory Authorities</HD>
        <P>Consistent with the international harmonization envisioned by section 752 of the Dodd-Frank Act, the Commission has engaged in consultations with foreign regulatory authorities regarding the Commission's regulations relating to the Dodd-Frank Act. During these consultations, many foreign regulatory authorities have expressed concern about the difficulty in complying with the indemnification provisions of CEA section 21(d).</P>

        <P>As a consequence of these consultations with foreign regulatory<PRTPAGE P="26712"/>authorities, and pursuant to the mandate for cooperation under section 752, the Commission concludes that further guidance is necessary to ensure that appropriate access by foreign regulatory authorities is not unnecessarily inhibited. For example, the Commission has learned that foreign regulatory authorities have asked whether a recognition regime with respect to SDRs, and/or access by foreign authorities that do not regulate an SDR, would conflict with § 49.17(d)(3) and § 49.18(c) of the SDR Final Rules, which refer to registration with Appropriate Foreign Regulators. Foreign regulatory authorities have also taken action to harmonize regulatory reporting rules.</P>
        <P>While the SDR Final Rules address foreign regulators with supervisory authority and regulatory responsibility, the Commission is proposing the following interpretative statement, pursuant to section 752, to ensure that foreign regulators receive sufficient access to data reported to SDRs where such foreign regulators have an independent and sufficient regulatory interest.</P>
        <HD SOURCE="HD1">III. Commission Proposed Interpretative Statement</HD>
        <P>In this proposed interpretative statement, the CFTC provides guidance regarding the confidentiality and indemnification provisions of CEA section 21(d). As noted above, the Commission seeks comment from interested members of the public on all aspects of this proposed interpretative statement.</P>
        <HD SOURCE="HD2">A. Data Reported to Registered SDRs</HD>
        <P>The Commission understands that some registered SDRs also maybe registered, recognized or otherwise authorized in a foreign jurisdiction and may accept swap data reported pursuant to the foreign regulatory regime. The Commission concludes that the confidentiality and indemnification provisions of CEA section 21(d) generally apply only to such data reported pursuant to the CEA and Commission regulations.</P>
        <P>The Commission further concludes that the confidentiality and indemnification provisions should not operate to inhibit or prevent foreign regulatory authorities from accessing data in which they have an independent and sufficient regulatory interest (even if that data also has been reported pursuant to the CEA and Commission regulations).</P>
        <P>Accordingly, and consistent with the Commission's SDR Final Rules, the Commission proposes to interpret CEA section 21(d) such that a registered SDR would not be subject to the confidentiality and indemnification provisions of that section if:</P>
        <P>• Such registered SDR also is registered, recognized or otherwise authorized in a foreign jurisdiction's regulatory regime; and</P>
        <P>• The data sought to be accessed by a foreign regulatory authority has been reported to such registered SDR pursuant to the foreign jurisdiction's regulatory regime.</P>

        <P>This proposed interpretative guidance is grounded in principles of international law and comity. For example, in<E T="03">F. Hoffmann-La Roche Ltd.</E>v.<E T="03">Empagran S.A.,</E>the U.S. Supreme Court, in reviewing the extraterritorial applicability of a different federal statute, stated that extraterritorial jurisdiction should be construed, where ambiguous, “to avoid unreasonable interference with the sovereign authority of other nations.”<SU>30</SU>
          <FTREF/>In cases considering concepts of international law and comity in evaluating the extraterritorial scope of federal statutes, the Supreme Court has noted that the principles in the Third Restatement of Foreign Relations Law are relevant to the interpretation of U.S. law.<SU>31</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>30</SU>
            <E T="03">F. Hoffmann-LaRoche, Ltd.</E>v.<E T="03">Empagran S.A.,</E>542 U.S. 155, 164 (2004). In<E T="03">Hoffmann-LaRoche,</E>the Supreme Court also stated that canons of statutory construction “assume that legislators take account of the legitimate sovereign interests of other nations when they write American laws.”<E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>31</SU>
            <E T="03">Id.</E>at 164-165.</P>
        </FTNT>
        <P>Specifically, section 403 of the Third Restatement of Foreign Relations Law states, in relevant part:</P>
        
        <EXTRACT>
          <P>Whether exercise of jurisdiction over a person or activity is unreasonable is determined by evaluating all relevant factors, including, where appropriate:</P>
          <P>(a) The link of the activity to the territory of the regulating state, i.e., the extent to which the activity takes place within the territory, or has substantial, direct, and foreseeable effect upon or in the territory;</P>
          <P>(b) The connections, such as nationality, residence, or economic activity, between the regulating state and the person principally responsible for the activity to be regulated, or between that state and those whom the regulation is designed to protect;</P>
          <P>(c) The character of the activity to be regulated, the importance of regulation to the regulating state, the extent to which other states regulate such activities, and the degree to which the desirability of such regulation is generally accepted;</P>
          <P>(d) The existence of justified expectations that might be protected or hurt by the regulation;</P>
          <P>(e) The importance of the regulation to the international political, legal, or economic system;</P>
          <P>(f) The extent to which the regulation is consistent with the traditions of the international system;</P>
          <P>(g) The extent to which another state may have an interest in regulating the activity; and</P>
          <P>(h) The likelihood of conflict with regulation by another state.<SU>32</SU>
            <FTREF/>
          </P>
        </EXTRACT>
        
        <FTNT>
          <P>
            <SU>32</SU>Rest. 3d., Third Restatement Foreign Relations Law section 403 (scope of a statutory grant of authority must be construed in the context of international law and comity including, as appropriate, the extent to which regulation is consistent with the traditions of the international system).</P>
        </FTNT>
        
        <P>To avoid unreasonable interference with the sovereign authority of foreign regulators, this proposed interpretative statement is supported and underpinned by principles of international law and comity.</P>
        <HD SOURCE="HD2">B. Foreign Regulatory Access</HD>
        <P>In the Commission's view, a foreign regulator's access to data held in a registered SDR that also is registered, recognized, or otherwise authorized in a foreign jurisdiction's regulatory regime, where the data sought to be accessed has been reported pursuant to that regulatory regime, should be governed by such foreign jurisdiction's regulatory regime. The Commission concludes that application of the requirements of CEA section 21(d) in these circumstances is unreasonable in light of, among other things, the importance of such data to the foreign jurisdiction's regulatory regime, foreign regulators' interest in unfettered access to such data, and the traditions of mutual trust and cooperation among international regulators.<SU>33</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>33</SU>The Commission notes that access to data held by trade repositories is a concept under discussion and development among international regulators. At the request of the FSB, CPSS and IOSCO have established a working group of relevant authorities to produce a forthcoming report regarding authorities' access to trade repository data.</P>
        </FTNT>
        <P>Therefore, the Commission proposes that a foreign regulator's access to data from a registered SDR that also is registered, recognized, or otherwise authorized in a foreign jurisdiction's regulatory regime, where the data to be accessed has been reported pursuant to that regulatory regime, will be dictated by that foreign jurisdiction's regulatory regime and not by the CEA or Commission regulations. Such access is appropriate, in the Commission's view, even if the applicable data is also reported to the registered SDR pursuant to the Commission's Data Final Rules.<SU>34</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>34</SU>Regarding the Commission's access to SDR data, section 21(b)(1)(A) of the CEA states that the Commission “shall prescribe standards that specify the data elements for each swap that shall be collected and maintained by each registered swap data repository.” Section 21(c)(1) of the CEA requires registered SDRs to “accept data prescribed by the Commission for each swap under subsection (b).” Therefore, with respect to Commission access to data held in registered SDRs, the Commission<PRTPAGE/>concludes that the direct electronic access provisions of CEA section 21(c)(4) apply only to such data that the SDR is required to accept under section 21(c)(1), which is further defined by part 45 of the Commission's regulations. In this respect, the Commission concludes that its direct electronic access applies only to such data reported pursuant to section 21 and Commission regulations promulgated thereunder.</P>
        </FTNT>
        <PRTPAGE P="26713"/>
        <P>Additionally, the Commission reiterates that a foreign regulatory authority, like domestic regulators, can nonetheless receive confidential data, without the execution of a confidentiality and indemnification agreement, from the Commission (as opposed to an SDR) pursuant to section 8(e) of the CEA.<SU>35</SU>
          <FTREF/>Such data sharing and access would be governed by the confidentiality provisions of section 8 of the CEA.</P>
        <FTNT>
          <P>
            <SU>35</SU>As noted above, CEA section 8(e) allows the Commission to share confidential information in its possession obtained in connection with the administration of the CEA with “any department or agency of the Government of the United States” or with any foreign futures authority or a department, central bank or ministry, or agency of a foreign government or political subdivision thereof, acting within the scope of its jurisdiction. The Commission acknowledges the difficulty that registered SDRs may face in determining what data or reporting falls within the jurisdiction of a regulatory authority. In this regard, the Commission is considering a separate release regarding section 2(i) of the CEA.</P>
        </FTNT>
        <HD SOURCE="HD2">C. Request for Comment</HD>
        <P>The Commission requests comment on all aspects of its proposed interpretative statement. In particular, the Commission requests comment on the following issue: How would the timing and implementation of foreign jurisdictions' regulatory regimes affect the Commission's proposed interpretative guidance?</P>
        <SIG>
          <P>By the Commission.</P>
          
          <DATED>Dated: Issued in Washington, DC, on April 30, 2012.</DATED>
          <NAME>David A. Stawick,</NAME>
          <TITLE>Secretary of the Commission.</TITLE>
        </SIG>
        <HD SOURCE="HD1">Appendices To Swap Data Repositories: Interpretative Statement Regarding the Confidentiality and Indemnification Provisions of Section 21(d) of the Commodity Exchange Act Interpretive Statement—Commission Voting Summary and Statements of Commissioners</HD>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>The following appendices will not appear in the Code of Federal Regulations.</P>
        </NOTE>
        <HD SOURCE="HD1">Appendix 1—Commission Voting Summary</HD>
        <EXTRACT>
          <P>On this matter, Chairman Gensler and Commissioners Sommers, Chilton, O'Malia and Wetjen voted in the affirmative; no Commissioner votes in the negative.</P>
        </EXTRACT>
        <HD SOURCE="HD1">Appendix 2—Statement of Chairman Gary Gensler</HD>
        <EXTRACT>
          <P>I support the proposed interpretative statement regarding the application of the Dodd-Frank Wall Street Reform and Consumer Protection Act (Dodd-Frank Act) indemnification provisions for swap data repositories (SDRs). The Commission is working closely with international regulators on a collaborative approach regarding how data may be accessed by regulators. The proposed guidance, which benefited from international input, states the Commission's view that foreign regulators will not be subject to the indemnification provisions in the Dodd-Frank Act if the SDR is registered, recognized or otherwise authorized by foreign law and the data to be accessed is reported to the SDR pursuant to foreign law. The public will now have an opportunity to comment on the proposed guidance, and I look forward to the public's input.</P>
        </EXTRACT>
        <HD SOURCE="HD1">Appendix 3—Statement of Commissioner Jill E. Sommers</HD>
        <EXTRACT>

          <P>I concur in the issuance of this Proposed Interpretative Statement Regarding the Confidentiality and Indemnification Provisions of Section 21(d) of the Commodity Exchange Act (Proposed Interpretive Statement). It provides some additional clarification with respect to how the Commission intends to interpret the application of the Section 21(d) indemnification provisions beyond what the Commission stated when it finalized the swap data repository (SDR) rules.<E T="03">See Swap Data Repositories: Registration Standards, Duties and Core Principles,</E>76 FR 54,538 (Sept. 1, 2011). However, a legislative fix is the only real solution to providing appropriate regulators, both foreign and domestic, with timely access to relevant data. I agree with Commissioner O'Malia that the Commission should publicly support repeal of the indemnification provisions, and note that the SEC has already done so.</P>

          <P>When finalizing the SDR rules, the Commission stated that a foreign regulator may have direct access to confidential swap data reported to and maintained by an SDR registered with the Commission without executing a Confidentiality and Indemnification Agreement when the SDR is also registered with the foreign regulator and the foreign regulator is acting in a regulatory capacity with respect to the SDR.<E T="03">See id.</E>at 54,554. The Proposed Guidance clarifies that this should be the case even if the data the foreign regulator seeks also has been reported pursuant to the CEA and Commission regulations.</P>

          <P>Aside from making this point, the Proposed Interpretive Statement does not provide any information that cannot be otherwise gleaned from the SDR final rules, with one notable exception. The final SDR rules define an “Appropriate Foreign Regulator” as one that has supervisory authority over an SDR that is<E T="03">registered</E>with the foreign regulator and with the CFTC. The Proposed Interpretive Statement expands this concept to SDRs that are<E T="03">registered, recognized, or otherwise authorized</E>in a foreign jurisdiction's regulatory regime. Thus, registration and recognition are equivalent. This is a welcome clarification and a step in the right direction.</P>
          <P>I should note that the indemnification provisions of Section 21(d) may have an adverse effect on U.S. regulators too. The Proposed Interpretive Statement touches on a distinction drawn in Part 49 between “Appropriate Domestic Regulators,” which include a number of domestic regulatory authorities, and an “Appropriate Domestic Regulator with Regulatory Responsibility over a Swap Data Repository” (a single entity subcategory of Appropriate Domestic Regulators, namely, the Securities and Exchange Commission (SEC)). Only the latter category of domestic regulator (i.e. the SEC) is exempt from the indemnification provisions of Section 21(d). While it makes sense that the SEC should be able to receive SDR data directly from an SDR absent an indemnification agreement, I encourage comments as to whether other Appropriate Domestic Regulators should have similar access.</P>
        </EXTRACT>
        <HD SOURCE="HD1">Appendix 4—Statement of Commissioner Scott D. O'Malia</HD>
        <EXTRACT>
          <P>I concur in support of the Commission's proposed interpretative statement (“Proposed Interpretative Statement”) regarding the confidentiality and indemnification provisions of Section 21(d) of the Commodity Exchange Act (“CEA”).</P>
          <P>Ultimately, Congress should repeal the confidentiality and indemnification provisions of Section 21(d) of the CEA and the Commission should publicly support that repeal. Absent a legislative fix, however, I believe the Commission is taking the right step to allay the concerns expressed by many foreign regulatory authorities.</P>
          <P>I am somewhat concerned that the Proposed Interpretative Statement does not address one important issue. Specifically, the Proposed Interpretative Statement would not provide foreign regulatory authorities with access to swaps data if those authorities had not yet finalized their regulations. In order to better understand the public's view on this issue, I have added a question seeking comment on how the timing and implementation of foreign jurisdictions' regulatory regimes should affect the Commission's final interpretation.</P>
          <P>Lastly, I am pleased that this Proposed Interpretative Statement is based on principles of international harmonization and comity. The Commission should continue to consult with foreign regulatory authorities in a manner consistent with international agreements regarding the registration of swap data repositories and the sharing of swaps data. In my view, these principles should establish the foundation of the Commission's forthcoming rulemaking concerning the extraterritorial application of the Dodd-Frank Act to foreign-based entities. Several foreign jurisdictions are in the process of finalizing new rules for the regulation of swaps and it is important that those rules provide a level and competitive playing field for U.S. firms as well.</P>
        </EXTRACT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10918 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6351-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <PRTPAGE P="26714"/>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <CFR>18 CFR Part 40</CFR>
        <DEPDOC>[Docket No. RM12-1-000]</DEPDOC>
        <SUBJECT>Transmission Planning Reliability Standards</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Energy Regulatory Commission, DOE.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of Proposed Rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The North American Electric Reliability Corporation (NERC), the Commission-certified Electric Reliability Organization, petitions for the approval of modified Transmission Planning Reliability Standard, TPL-001-2 (Transmission System Planning Performance Requirements), which combines four currently effective TPL Reliability Standards, TPL-001-1, TPL-002-1b, TPL-003-1a, and TPL-004-1, into a single standard. NERC also requests retirement of the currently-effective TPL standards. Pursuant to section 215 of the Federal Power Act, the Federal Energy Regulatory Commission proposes to remand proposed Reliability Standard, TPL-001-2. The proposed Reliability Standard includes a provision that would allow a transmission planner to plan for non-consequential load loss following a single contingency provided that the plan is documented and vetted in an open and transparent stakeholder process. The Commission believes that, with the inclusion of this provision, proposed TPL-001-2 does not meet the statutory criteria for approval.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments are due July 6, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number by any of the following methods:</P>
          <P>•<E T="03">Agency Web Site: http://ferc.gov</E>. Documents created electronically using word processing software should be filed in native applications or print-to-PDF format and not in a scanned format.</P>
          <P>•<E T="03">Mail/Hand Delivery:</E>Commenters unable to file comments electronically must mail or hand deliver comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street NE., Washington, DC 20426.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Eugene Blick (Technical Information),Office of Electric Reliability,Federal Energy Regulatory Commission,888 First Street NE.,Washington, DC 20426,Telephone: (202) 502-8066,<E T="03">Eugene.Blick@ferc.gov</E>.</P>

          <P>Robert T. Stroh (Legal Information),Office of the General Counsel,Federal Energy Regulatory Commission,888 First Street NE.,Washington, DC 20426,Telephone: (202) 502-8473,<E T="03">Robert.Stroh@ferc.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">139 FERC ¶ 61,059</HD>
        <HD SOURCE="HD1">Notice of Proposed Rulemaking</HD>
        <HD SOURCE="HD2">April 19, 2012</HD>
        <P>1. The North American Electric Reliability Corporation (NERC), the Commission-certified Electric Reliability Organization (ERO), petitions for the approval of Reliability Standard, TPL-001-2 (Transmission System Planning Performance Requirements), which combines four currently effective TPL Reliability Standards, TPL-001-1, TPL-002-1b, TPL-003-1a, and TPL-004-1, into a single standard. NERC also requests retirement of the currently effective TPL standards. Pursuant to section 215(d) of the Federal Power Act (FPA), the Federal Energy Regulatory Commission (FERC) proposes to remand proposed Reliability Standard, TPL-001-2. The proposed Reliability Standard includes a provision in Table 1 (Steady State and Stability Performance Extreme Events), footnote 12 that would allow a transmission planner to plan for “non-consequential load loss,” i.e., load shedding, following a single contingency provided that the plan is documented and alternatives are considered and subject to review in an open and transparent stakeholder process. As discussed below, the Commission believes that this provision is vague and unenforceable because it does not adequately define the circumstance in which an entity can plan for non-consequential load loss following a single contingency. Accordingly, the Commission proposes to find that, with the inclusion of this provision, proposed TPL-001-2 does not meet the statutory criteria for approval that a mandatory Reliability Standard must be just, reasonable, not unduly discriminatory or preferential, and in the public interest.</P>
        <P>2. NERC states that proposed Reliability Standard TPL-001-2 introduces significant revisions and improvements to the Transmission Planning Reliability Standards, including increased specificity of data required for modeling conditions, and requires planners to address the impact of the unavailability of long lead-time critical equipment in a manner consistent with the entity's spare equipment strategy.<SU>1</SU>
          <FTREF/>Further, according to NERC, the proposed Reliability Standard addresses twenty-seven Commission directives set forth in Order No. 693 and subsequent Commission orders.<SU>2</SU>

          <FTREF/>We agree with NERC that proposed TPL-001-2 includes specific improvements over the currently effective Transmission Planning Reliability Standards and, as discussed below, is responsive to certain Commission directives. However, the provision in the proposed Reliability Standard allowing for transmission planners to plan for non-consequential load loss following a single contingency without adequate safeguards undermines the potential benefits the proposed Reliability Standard may provide. Section 215(d)(4) requires that the Commission remand to the ERO for further consideration a Reliability Standard “that the Commission disapproves in whole<E T="03">or in part.</E>”<SU>3</SU>
          <FTREF/>Thus, notwithstanding improvements contained in other provisions of proposed Reliability Standard TPL-001-2, our concerns regarding the stakeholder process set forth in Table 1, footnote 12 provides us no option other than to propose to remand the entire Reliability Standard.</P>
        <FTNT>
          <P>
            <SU>1</SU>NERC Petition at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">Mandatory Reliability Standards for the Bulk-Power System,</E>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242,<E T="03">order on reh'g,</E>Order No. 693-A, 120 FERC ¶ 61,053 (2007).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>16 U.S.C. 824o(d)(4) (2006) (emphasis added).</P>
        </FTNT>
        <P>3. We are concurrently issuing a Final Rule in Docket No. RM11-18-000 that remands a related Reliability Standard, TPL-002-0b, which contains the same objectionable stakeholder process provision in Table 1, footnote `b'.<SU>4</SU>
          <FTREF/>In the Final Rule in Docket No. RM11-18-000, the Commission urges NERC to employ its Expedited Reliability Standards Development Process to timely develop a modified provision regarding planned shedding of non-consequential load loss that satisfies the relevant Commission's directives in Order No. 693 and the subsequent orders. A rapid resolution of this one matter will allow the industry, NERC and the Commission to go forward with the consideration of other improvements contained in proposed Reliability Standard TPL-001-2.</P>
        <FTNT>
          <P>
            <SU>4</SU>
            <E T="03">Transmission Planning Reliability Standards,</E>Order No. 762, 139 FERC ¶ 61,060 (2012).</P>
        </FTNT>
        <HD SOURCE="HD1">I. Background</HD>
        <P>4. Section 215 of the FPA requires a Commission-certified ERO to develop mandatory and enforceable Reliability Standards, which are subject to Commission review and approval. Approved Reliability Standards are enforced by the ERO, subject to Commission oversight, or by the Commission independently.</P>

        <P>5. Pursuant to section 215 of the FPA, the Commission established a process to<PRTPAGE P="26715"/>select and certify an ERO<SU>5</SU>
          <FTREF/>and, subsequently, certified NERC as the ERO.<SU>6</SU>
          <FTREF/>On March 16, 2007, the Commission issued Order No. 693, approving 83 of the 107 Reliability Standards filed by NERC, including the existing TPL Reliability Standards. In addition, pursuant to section 215(d)(5) of the FPA,<SU>7</SU>
          <FTREF/>the Commission directed NERC to develop modifications to 56 of the 83 approved Reliability Standards, including the TPL Reliability Standards.<SU>8</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>5</SU>
            <E T="03">Rules Concerning Certification of the Electric Reliability Organization; and Procedures for the Establishment, Approval and Enforcement of Electric Reliability Standards</E>, Order No. 672, FERC Stats. &amp; Regs. ¶ 31,204, order on reh'g, Order No. 672-A, FERC Stats. &amp; Regs. ¶ 31,212 (2006).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>6</SU>
            <E T="03">North American Electric Reliability Corp., 116 FERC ¶ 61,062,</E>
            <E T="03">order on reh'g and compliance,</E>117 FERC ¶ 61,126 (2006),<E T="03">aff'd sub nom. Alcoa, Inc. v. FERC</E>, 564 F.3d 1342 (DC Cir. 2009).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>7</SU>16 U.S.C. 824o(d)(5).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>8</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at PP 1691-1845.</P>
        </FTNT>
        <HD SOURCE="HD2">A. Transmission Planning (TPL) Reliability Standards and Order No. 693 Directives</HD>
        <P>6. The currently-effective TPL Reliability Standards consists of four approved standards and are intended to ensure that the transmission system is planned and designed to meet an appropriate and specific set of reliability criteria. Transmission planning is a process that involves a number of stages including developing a model of the Bulk-Power System, using this model to assess the performance of the system for a range of operating conditions and contingencies, determining those operating conditions and contingencies that have an undesirable reliability impact, identifying the nature of potential options, and developing and evaluating a range of solutions and selecting the preferred solution, taking into account the time needed to place the solution in service.</P>
        <P>7. In Order No. 693, the Commission accepted the Version 0 TPL Reliability Standards and directed NERC, pursuant to FPA section 215(d)(5), to develop modifications to TPL-001-0 through TPL-004-0 through the Reliability Standards development process. In addition, the Commission neither approved nor remanded two other planning Reliability Standards, TPL-005-0 and TPL-006-0, as these two Reliability Standards applied only to regional reliability organizations.<SU>9</SU>
          <FTREF/>The Commission encouraged the ERO to monitor a series of technical conferences and regional meetings to obtain industry input to achieve the goal of regional planning and use the results as input to the standards development process to revise TPL-005-0 to address regional planning and related processes.<SU>10</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>9</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at PP 1840, 1845. The currently-effective versions of the TPL Reliability Standards are as follows: TPL-001-0.1, TPL-002-0b, TPL-003-0a, and TPL-004-0.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1841.</P>
        </FTNT>
        <P>8. With regard to Reliability Standard TPL-002-0b, Table 1, footnote `b', the Commission directed NERC to clarify footnote `b' regarding the loss of non-consequential load for a single contingency event. In a March 18, 2010 order, the Commission directed NERC to submit a modification to footnote `b' responsive to the Commission's directive in Order No. 693, by June 30, 2010.<SU>11</SU>
          <FTREF/>In a June 11, 2010 order, the Commission granted partial clarification to NERC and extended the compliance deadline until March 31, 2011.<SU>12</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>11</SU>
            <E T="03">Mandatory Reliability Standards for the Bulk Power System,</E>130 FERC ¶ 61,200 (2010) (March 2010 Order).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>12</SU>
            <E T="03">Mandatory Reliability Standards for the Bulk Power System,</E>131 FERC ¶ 61,231 (2010) (June 2010 Order).</P>
        </FTNT>
        <HD SOURCE="HD2">B. RM11-18-000 Proposed Remand of Footnote `b'—Version 1</HD>
        <P>9. In response to the March 2010 and June 2010 Orders, on March 31, 2011, NERC submitted proposed TPL-002-1 (Version 1), which proposed to modify footnote `b' to permit planned interruption of Firm Demand when documented and subject to an open stakeholder process. On October 20, 2011, the Commission issued a Notice of Proposed Rulemaking that proposed to remand to NERC the proposed modification to footnote `b' because it does not adequately clarify or define the circumstances in which an entity can plan to use interruption of Firm Demand as a mitigation plan to resolve a single contingency.<SU>13</SU>
          <FTREF/>The Commission stated that the procedural and substantive parameters of NERC's proposal are too undefined to provide assurances that the process will be effective in determining when it is appropriate to plan for interrupting Firm Demand, do not contain NERC-defined criteria on circumstances to determine when an exception for planned interruption of Firm Demand is permissible, and could result in inconsistent results in implementation. In the Final Rule issued concurrently with the NOPR in the immediate proceeding, the Commission remanded proposed Reliability Standard TPL-002-0b.</P>
        <FTNT>
          <P>
            <SU>13</SU>
            <E T="03">Transmission Planning Reliability Standards,</E>137 FERC ¶ 61,077 (2011).</P>
        </FTNT>
        <HD SOURCE="HD2">C. NERC's Petition for Approval of TPL-001-2</HD>
        <P>10. On October 19, 2011, NERC filed a petition seeking approval of Reliability Standard TPL-001-2, the associated implementation plan and Violation Risk Factors (VRFs) and Violation Severity Levels (VSLs), as well as five new definitions to be added to the NERC Glossary of Terms (Version 2). NERC also seeks approval of the retirement of the following four Reliability Standards: TPL-001-1 (System Performance Under Normal (No Contingency) Conditions (Category A)); TPL-002-1b (System Performance Following Loss of a Single Bulk Electric System (BES) Element (Category B)); TPL-003-1a (System Performance Following Loss of Two or More BES Elements (Category C)); and TPL-004-1 (System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Elements (Category D)). In addition, NERC requests to withdraw two pending Reliability Standards: TPL-005-0 (Regional and Interregional Self-Assessment Reliability Reports) and TPL-006-0.1 (Data from the Regional Reliability Organization Needed to Assess Reliability).</P>
        <P>11. The Version 2 standard also includes language similar to NERC's Version 1 March 31, 2011, proposal to revise and clarify footnote `b' of Table 1 applicable in four currently-effective TPL Reliability Standards “in regard to non-consequential firm load loss in the event of a single contingency.”<SU>14</SU>
          <FTREF/>The proposed Reliability Standard TPL-001-2 (Version 2) expands upon NERC's proposed footnote `b' (Version 1) and as a result, Version 2 replaces in its entirety the Version 1 footnote `b.' In creating TPL-001-2, the proposed footnote `b' in Version 1 was modified slightly and carried over as Steady State &amp; Stability Performance Footnotes 9 and 12 in Version 2. In other words, footnote `b' in Version 1 has been divided into two footnotes in Version 2, and the subject of the concerns raised by the Commission with respect to the Version 1 footnote `b' are now contained in footnote 12 of Version 2. Footnote 12 in Version 2 is in all material respects the same as the portion of footnote `b' in Version 1 that is the subject of the Final Rule issued today in Docket No. RM11-18-000.</P>
        <FTNT>
          <P>
            <SU>14</SU>NERC Petition at 11.</P>
        </FTNT>
        <HD SOURCE="HD2">D. Proposed Reliability Standard</HD>

        <P>12. As proposed by NERC, TPL-001-2 includes eight requirements and Table 1, summarized as follows:<PRTPAGE P="26716"/>
        </P>
        <P>
          <E T="03">Requirement R1:</E>Requires the transmission planner and planning coordinator to maintain system models and provides a specific list of items required for the system models and that the models represent projected system conditions. The planner is required to model the items that are variable, such as load and generation dispatch, based specifically on the expected system conditions.</P>
        <P>
          <E T="03">Requirement R2:</E>Requires each transmission planner and planning coordinator to prepare an annual planning assessment of its portion of the bulk electric system and must use current or qualified past studies, document assumptions, and document summarized results of the steady state analyses, short circuit analyses, and stability analyses. Requirement R2, Part 2.1.3 requires the planner to assess system performance utilizing a current annual study or qualified past study for each known outage with a duration of at least six months for certain events listed in Table 1, P1. NERC states that this requirement ensures planners evaluate every known outage with known duration of six months or more, even if the known outage is not within one of the study years selected by the planner. NERC states that the requirements and parts of proposed TPL-001-2 provide for what a valid study must entail, timeframes for use of past studies, minimum conditions, what needs to be included in the model, and what performance must be achieved. It also clarifies that qualified past studies can be utilized in the analysis while tightly defining the qualifications for those studies. The use of qualified past studies allows an entity to continue to use validated studies to complete its assessment. Requirement R2 includes a new part (2.7.3) that allows transmission planners and planning coordinators to utilize Non-Consequential Load Loss to meet performance requirements if the applicable entities are unable to complete a Corrective Action Plan due to circumstances beyond their control.</P>
        <P>
          <E T="03">Requirements R3 and R4:</E>Requirement R3 describes the requirements for steady state studies and Requirement R4 explains the requirements for stability studies. Requirement R3 and Requirement R4 also require that simulations duplicate what will occur in an actual power system based on the expected performance of the protection systems. These requirements are intended to ensure that if a protection system is designed to remove multiple elements from service for an event that the simulation will be run with all of those elements removed from service. Requirement R3 and Requirement R4 also include new parts that require the planners to conduct an evaluation of possible actions designed to reduce the likelihood or the consequences of extreme events that cause cascading.</P>
        <P>
          <E T="03">Requirement R5:</E>Requirement R5 deals with voltage criteria and voltage performance. NERC proposes in Requirement R5 that each transmission planner and planning coordinator must have criteria for acceptable system steady state voltage limits, post-contingency voltage deviations, and the transient voltage response for its system. For transient voltage response the criteria must specify a low-voltage level and a maximum length of time that transient voltages may remain below that level. This requirement will establish more robust transmission planning for organizations and greater consistency as these voltage criteria are shared.</P>
        <P>
          <E T="03">Requirement R6:</E>Specifies that an entity must define and document the criteria or methodology used to identify system instability for conditions such as cascading, voltage instability, or uncontrolled islanding within its planning assessment.</P>
        <P>
          <E T="03">Requirement R7:</E>Mandates coordination of individual and joint responsibilities for the planning coordinator and the transmission planner which is intended to eliminate confusion regarding the responsibilities of the applicable entities and assures that all elements needed for regional and wide area studies are defined with a specific entity responsible for each element and that no gaps will exist in planning for the Bulk-Power System.</P>
        <P>
          <E T="03">Requirement R8:</E>Addresses the sharing of planning assessments with neighboring systems. The requirement ensures that information is shared with and input received from adjacent entities and other entities with a reliability related need that may be affected an entity's system planning.</P>
        <P>
          <E T="03">Table 1:</E>Similar to the existing TPL Standard, NERC's proposal contains a series of planning events and describes system performance requirements in Table 1 for a range of potential system contingencies required to be evaluated by the planner. Table 1 includes three parts: Steady State &amp; Stability Performance Planning Events, Steady State &amp; Stability Performance Extreme Events, and Steady State &amp; Stability Performance Footnotes. Table 1 describes system performance requirements for a range of potential system contingencies required to be evaluated by the planner. The table categorizes the events as either “planning events” or “extreme events.” The proposed table lists seven Contingency planning events (P1 through P7) that require steady-state and stability analysis as well as five extreme event contingencies—three for steady-state and two for stability. The proposed table also includes a no contingency “event” labeled as P0 which requires steady state analysis. Footnote 12 of Table 1 provides:</P>
        
        <EXTRACT>
          <P>An objective of the planning process should be to minimize the likelihood and magnitude of Non-Consequential Load Loss following Contingency events. However, in limited circumstances Non-Consequential Load Loss may be needed to address BES performance requirements. When Non-Consequential Load Loss is utilized within the planning process to address BES performance requirements, such interruption is limited to circumstances where the Non-Consequential Load Loss is documented, including alternatives evaluated; and where the utilization of Non-Consequential Load Loss is subject to review in an open and transparent stakeholder process that includes addressing stakeholder comments.<SU>15</SU>
            <FTREF/>
          </P>
        </EXTRACT>
        <FTNT>
          <P>
            <SU>15</SU>NERC Petition at 12. In NERC's proposal in Docket No. RM11-18-000, Table 1, footnote `b' planned load shed is called planned “interruption of Firm Demand.” In footnote 12, NERC has changed the term from “interruption of Firm Demand” to utilization of “Non-Consequential Load Loss.”</P>
        </FTNT>
        
        <HD SOURCE="HD1">II. Discussion</HD>
        <P>13. The Commission proposes to remand proposed Reliability Standard TPL-001-2. The proposed footnote 12 included as part of Reliability Standard TPL-001-2, which is in all material respects the same as the Version 1 footnote `b' proposal described in Docket No. RM11-18-000, is unjust and unreasonable, unduly discriminatory or preferential, and not in the public interest. Although there are many improvements in the proposed TPL-001-2, the presence of footnote 12 in proposed Reliability Standard TPL-001-2 requires that the Commission remand the entire proposed Reliability Standard.<SU>16</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>16</SU>16 U.S.C. 824o(d)(4).</P>
        </FTNT>

        <P>14. As described in the Final Rule in Docket No. RM11-18-000, the Commission believes that NERC's footnote `b' proposal (footnote 12 in this NOPR proceeding) does not clarify or define the circumstances in which an entity can plan to interrupt Non-Consequential Load Loss for a single contingency. The Commission is concerned that footnote 12 is inadequate and fails to address the Commission's concerns for three reasons. First, proposed footnote 12 lacks adequate parameters. Second, the NERC proposal leaves undefined the circumstances in<PRTPAGE P="26717"/>which it is allowable to plan for Non-Consequential Load Loss to be utilized. The Commission believes that footnote 12 could function as a means to override the reliability objective and system performance requirements of the TPL Reliability Standard without any technical or other criteria specified to determine when planning to use Non-Consequential Load Loss to meet single contingency performance requirements would be allowable.<SU>17</SU>
          <FTREF/>While NERC expects that such determinations will be made in a stakeholder process, this provides no assurance that such a process will use technically sound means of approving or denying exceptions.<SU>18</SU>
          <FTREF/>Third, while the Commission recognizes that some variation among regions or entities is reasonable given varying grid topography and other considerations, there are no technical criteria to determine whether varied results are arbitrary or based on meaningful distinctions.<SU>19</SU>
          <FTREF/>The Commission, thus, concludes that NERC's proposal lacks safeguards to ensure against inconsistent results and arbitrary determinations to allow for the planned interruption of load shed.</P>
        <FTNT>
          <P>
            <SU>17</SU>Order No. 762, 139 FERC ¶ 61,160 at P 13.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>18</SU>
            <E T="03">Id.</E>P 14.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>19</SU>June 2010 Order, 131 FERC ¶ 61,231 at P 21.</P>
        </FTNT>
        <P>15. While we propose to remand Reliability Standard TPL-001-2 because of footnote 12, the Commission sees improvements to the balance of the proposed Reliability Standard. The Commission recognizes the level of complexity and substantial revision that NERC undertook to consolidate the requirements in the four currently-effective TPL Reliability Standards into one standard, and that effort has yielded improvements relative to the current set of standards. The Commission, however, seeks comments from the ERO and other interested persons regarding the following important reliability issues to ensure that the proposed Reliability Standard adequately maintains reliability and that the directives have been met: (a) Planned Maintenance Outages, (b) Violation Risk Factors, (c) Protection System Failures versus Relay Failures, (d) Assessment of Backup or Redundant Protection Systems, (e) Single Line to Ground Faults, and (f) Order No. 693 Directives.</P>
        <HD SOURCE="HD2">A. Planned Maintenance Outages</HD>
        <P>16. NERC proposed new language in TPL-001-2, Requirement R1 to remove an ambiguity in the current standard concerning what the planner needs to include in the specific studies. It also requires the planner to evaluate six-month or longer duration outages within its system. NERC states that while Requirement R1.3.12 of the currently-effective TPL-002-0b, includes planned outages (including maintenance outages) in the planning studies and requires simulations at the demands levels for which the planned outages are performed, it is not appropriate to have the planner select specific planned outages for inclusion in their studies. Consequently, NERC proposes a bright-line test to determine whether an outage should be included in the system models. Specifically, NERC proposes that Requirement R1, Part 1.1.2 mandate that the system models “shall represent * * * known outage(s) of generation or Transmission Facility(ies) with a duration of at least six months.”<SU>20</SU>
          <FTREF/>NERC determined that, in the planning horizon, a six-month or longer outage duration would necessarily extend over a seasonal peak load period and should be included in the planning models. Therefore, NERC states that the specific elements selected to be evaluated are selected by the transmission planner or planning coordinator and must be acceptable to the associated regional reliability organization.<SU>21</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>20</SU>NERC Petition at 35-36.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>21</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>17. In Order No. 693 the Commission stated that in the currently-effective TPL Reliability Standards a planner must demonstrate through a valid assessment that the transmission system performance requirements can be met. The TPL Reliability Standards require that planned outages of transmission equipment must be considered for those demand levels for which planned outages are performed. By modeling the planned transmission equipment outages and through the simulation of various contingency events, a planner must demonstrate that the system can be operated to supply projected customer demands for all maintenance outage conditions and that amongst other things, cascading or system instability will not occur.<SU>22</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>22</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at PP 1772, 1799, 1827.</P>
        </FTNT>
        <P>18. For example, PJM has recently evaluated a Doubs-Mt. Storm project which includes the replacement of structures that have deteriorated beyond repair, which has resulted in the need to rebuild the transmission circuit. PJM indicates the maintenance outages will be scheduled in four month blocks, September—December and February—May, starting in 2011 through 2015. PJM's analysis indicates that a list of facilities has been determined that should not be scheduled out concurrently with the Doubs-Mt. Storm project. Furthermore, PJM analysis indicated that if any outage on this list of identified facilities must be taken out of service, every effort shall be made to align them with the lightest load period possible.<SU>23</SU>
          <FTREF/>Based on NERC's proposed Requirement R1, Part 1.1.2 and the Doubs-Mt. Storm example, it appears that this type of planned maintenance outage would be excluded from future planning assessments and its potential impact to bulk electric system reliability would be unknown because the outage duration in this example is less than six months.</P>
        <FTNT>
          <P>
            <SU>23</SU>
            <E T="03">See</E>
            <E T="03">http://www.pjm.com/∼/media/committees-groups/committees/pc/20110203/20110203-item-12-doubs-mt-storm-impact-summary.ashx</E>.</P>
        </FTNT>

        <P>19. The Commission seeks comment from the ERO and interested persons whether the six month threshold would materially change the number of planned outages as compared to the current standard. The Commission also seeks comment on whether the threshold would exclude almost all planned outages from future planning assessments, such as nuclear plant refueling, large fossil and hydro generating station maintenance, spring and fall transmission construction projects and items indentified in correction actions plans of planning assessments including neighboring corrective action plans. The Commission also seeks comment on what alternative, whether based on outage duration shorter than six months or some other method, such as planners' accounting for planned maintenance outages of high capacity lines, critical transformers, or nuclear outages during non-peak load periods in their assessments, captures the appropriate number of planned outages and types of planned outages to ensure that the Bulk-Power System can be operated to meet system performance requirements during high maintenance periods like the spring and fall seasons. In addition to seasonal peaks, there have been significant system incidents which occur because of unusual weather events during non-seasonal peak periods. The Commission seeks comment on whether a six month outage window would sufficiently capture these events or if they would not be addressed in the proposed planning process. In addition, with respect to protection system maintenance, currently-effective Reliability Standard TPL-002-0, Requirement R1.3.12 requires the planner to “[i]nclude the planned (including maintenance) outage of any bulk electric equipment (including<PRTPAGE P="26718"/>protection systems or their components) at those demand levels for which planned (including maintenance) outages are performed.”<SU>24</SU>
          <FTREF/>NERC did not carry over this language because protection system maintenance or other outages are not anticipated to last six months. The Commission, however, believes that it is critical to plan the system so that a protection system can be removed for maintenance and still be operated reliably. Therefore, the Commission seeks comment on its belief that protection systems are necessary to be included as a type of planned outage.</P>
        <FTNT>
          <P>
            <SU>24</SU>Reliability Standard TPL-002-0, Requirement R1.3.12.</P>
        </FTNT>
        <HD SOURCE="HD2">B. Violation Risk Factors</HD>
        <HD SOURCE="HD3">1. VRF for Proposed TPL-001-2, Requirement R1 VRF</HD>
        <P>20. NERC assigned a “Medium” VRF for proposed Reliability Standard TPL-001-2, Requirement R1 and its sub-requirements. NERC states each primary requirement in the proposed Reliability Standard TPL-001-2 is assigned a VRF considering the NERCguidelines and consistent with NERC's August 10, 2009 informational filing.<SU>25</SU>
          <FTREF/>NERC maintains that Requirements R1.3.5, R1.3.7, R1.3.8, and R1.3.9 of the currently-effective Reliability Standard TPL-001-0.1 carry a VRF of “Medium” and are similar in purpose and effect to proposed Reliability Standard TPL-001-2, Requirement R1. NERC states that the Requirements are similar because they refer to models that include firm transfers, existing and planned facilities, and reactive power requirements, and they refer to the Table 1 P0 condition. NERC believes that a “medium VRF for Requirement R1 is consistent with past Commission guidance.”<SU>26</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>25</SU>Informational Filing of the North American Electric Reliability Corporation Regarding the Assignment of Violation Risk Factors and Violation Severity Levels, Docket Nos. RM08-11-000, RR08-4-000, RR07-9-000, and RR07-10-000 (August 10, 2009).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>26</SU>NERC Petition at Exhibit C, Table 1.</P>
        </FTNT>
        <P>21. NERC stated in its filing that “Requirement R1 of the proposed TPL-001-2 explicitly requires the Transmission Planner and Planning Coordinator to maintain System models.”<SU>27</SU>
          <FTREF/>The Commission believes that when the planning coordinator or the transmission planner are maintaining the system models to reflect the normal system condition, if the system models are not properly modeled or maintained, the analysis required in the Reliability Standard that uses the models in Requirement R1, such as Category P0 as the normal System condition in Table 1, may lose their validity and “could, under emergency, abnormal, or restorative conditions anticipated by the preparations, directly cause or contribute to Bulk-Power System instability, separation, or a cascading sequence of failures, or could place the Bulk-Power System at an unacceptable risk of instability, separation, or cascading failures, or could hinder restoration to a normal condition.”<SU>28</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>27</SU>NERC Petition at 34.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>28</SU>
            <E T="03">North American Electric Reliability Corp., order on violation risk factors,</E>119 FERC ¶ 61,145, at P 9 (2007),<E T="03">order on reh'g and compliance filing,</E>120 FERC ¶ 61,145 (2007).</P>
        </FTNT>
        <P>22. Furthermore, Requirement R1 of the proposed Reliability Standard TPL-001-2 explicitly addresses the establishment of Category P0 as the normal system condition in Table 1, which creates the model of the normal system as the “Initial Condition” prior to any contingency.<SU>29</SU>
          <FTREF/>Requirement R1 of the currently-effective Reliability Standard TPL-001-0, which has a VRF of “High,” explicitly establishes Category A as the normal system (all facilities in service) in Table 1, which also creates the model of the normal system prior to any contingency. The Commission believes that Requirement R1 of proposed Reliability Standard TPL-001-2 and Requirement 1 of currently-effective TPL-001-0 both establish the normal system planning model that serves as the foundation for all other conditions and contingencies that are required to be studied and evaluated in a planning assessment.</P>
        <FTNT>
          <P>
            <SU>29</SU>Proposed Reliability Standard TPL-001-2, Table 1.</P>
        </FTNT>
        <P>23. Consistent with Guideline 3 of the Commission's VRF Guidelines, the Commission “expects the assignment of Violation Risk Factors corresponding to Requirements that address similar reliability goals to be treated comparably.”<SU>30</SU>
          <FTREF/>The Commission seeks comment on why Requirement R1 of proposed Reliability Standard TPL-001-2 carries a VRF of “Medium” while Requirement R1 of the currently-effective Reliability Standard TPL-001-0 carries a VRF of “High.”</P>
        <FTNT>
          <P>
            <SU>30</SU>
            <E T="03">North American Electric Reliability Corp.,</E>
            <E T="03">order on violation risk factors,</E>119 FERC ¶ 61,145, at P 25 (2007),<E T="03">order on reh'g and compliance filing,</E>120 FERC ¶ 61,145 (2007).</P>
        </FTNT>
        <HD SOURCE="HD3">2. VRF for Proposed TPL-001-2, Requirement R6</HD>
        <P>24. NERC proposes to assign a “Low” VRF for Requirement R6 from the proposed Reliability Standard TPL-001-2 because “failure to have established criteria for determining System instability is an administrative requirement affecting a planning time frame.”<SU>31</SU>
          <FTREF/>NERC explains that Requirement R6 is a new requirement and that violations would not be expected to adversely affect the electrical state or capability of the bulk electric system.</P>
        <FTNT>
          <P>
            <SU>31</SU>NERC Petition, Exhibit C, at 110.</P>
        </FTNT>
        <P>25. Requirement R6 requires planning coordinators and transmission planners to define and document the criteria or methodology used in their analyses to identify system instability for conditions such as cascading, voltage instability or uncontrolled islanding. The Commission recognizes that documenting criteria or methodology is an administrative act. However, defining the criteria or methodology to be used is not an administrative act. If the criteria or methodology used by planning coordinators and transmission planners are not defined properly, the analysis based on this criteria or methodology could lose its validity and “could, under emergency, abnormal, or restorative conditions anticipated by the preparations, directly cause or contribute to Bulk-Power System instability, separation, or a cascading sequence of failures, or could place the Bulk-Power System at an unacceptable risk of instability, separation, or cascading failures, or could hinder restoration to a normal condition.”<SU>32</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>32</SU>
            <E T="03">North American Electric Reliability Corp., order on violation risk factors,</E>119 FERC ¶ 61,145 at P 9.</P>
        </FTNT>
        <P>26. Requirement R6 co-mingles a higher reliability objective (defining criteria or methodology) with a lower reliability objective (documentation). Consistent with Guideline 5 of the Commission's VRF Guidelines, the Commission seeks to ensure that the assignment of Violation Risk Factors corresponding to co-mingled Requirements reflect the higher reliability objective of the co-mingled requirement.<SU>33</SU>
          <FTREF/>The Commission seeks clarification from the ERO why the VRF level assigned to Requirement R6 is “Low” since it is appears that Requirement R6 requires more than a purely administrative task.</P>
        <FTNT>
          <P>
            <SU>33</SU>
            <E T="03">Id.</E>P 32.</P>
        </FTNT>
        <HD SOURCE="HD2">C. Protection System Failures Versus Relay Failures</HD>

        <P>27. NERC states that its modification to the planning contingency categories in Table 1 of the proposed standard is intended to add clarity and consistency regarding how a delayed fault clearing will be modeled in planning studies. NERC states that the basic elements of any protection system design involve inputs (i.e., current and D/C and A/C voltage) to protective relays and outputs (i.e., trip signals, close signals, and<PRTPAGE P="26719"/>alarms) from protective relays and that reliability issues associated with improper clearing of a fault on the bulk electric system can result from the failure of hundreds of individual protection system components in a substation. However, NERC believes that while the population of components that could fail and result in improper clearing is large, that population can be reduced dramatically by eliminating those components which share failure modes with other components. NERC states that the critical components in protection systems are the protective relays themselves, and a failure of a non-redundant protective relay will often result in undesired consequences during a fault. According to NERC, other protection system components related to the protective relay could fail and lead to a bulk electric system issue, but the event that would be studied is identical, from both transient and steady state perspectives, to the event resulting from a protective relay failure if an adequate population of protective relays is considered.<SU>34</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>34</SU>NERC Petition at 48.</P>
        </FTNT>
        <P>28. In the currently-effective TPL Reliability Standards, Table 1 contingencies address the initiating event and contingency of a single line to ground (SLG) fault with delayed clearing (stuck breaker or protection system failure) for a generator, transformer, transmission circuit and bus section. For this initiating event and set of contingencies, the planner must demonstrate that Table 1 system performance criteria can be met.<SU>35</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>35</SU>Currently-effective Reliability Standard TPL-004-0, Categories C1-C4 address the same initiating event and set of contingencies as currently-effective TPL-003-0,Categories C6-C9, but the system performance criteria are different for TPL-003-0 versus TPL-004-0.</P>
        </FTNT>
        <P>29. Currently-effective Reliability Standard TPL-003-0, Requirement R1.3.1 states that current or past study and/or system simulation testing “[b]e performed and evaluated only for those Category C contingencies that would produce the more severe system results or impacts.”<SU>36</SU>
          <FTREF/>Referring to Table 1, Category C6-C9, the initiating event and contingency is described as “SLG Fault, with Delayed Clearing (stuck breaker or protection system failure).”<SU>37</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>36</SU>Reliability Standard TPL-003-0a.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>37</SU>Reliability Standard TPL-003-0a (Category C).</P>
        </FTNT>
        <P>30. Requirement R1.3.1 states that in the study and simulation of a protection system failure, the planner should assess the contingencies that produce the more severe system results.<SU>38</SU>
          <FTREF/>If the contingency is a protection system failure, delayed clearing is described as a fault due to the failure of any protection system component such as a relay, circuit breaker, or current transformer, and not because of an intentional design delay.<SU>39</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>38</SU>Requirement R1.3.1 is included in TPL-002-0b, TPL-003-0a and TPL-004-0.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>39</SU>Reliability Standard TPL-003-0, Table 1, footnote e.</P>
        </FTNT>
        <P>31. The Commission believes that based on various protection system as-built designs, the planner will have to choose which protection system component failure would have the most significant impact on the Bulk-Power System because as-built designs are not standardized and the most critical component failure may not always be the relay. For example, if a protection system design used one set of fuses to supply power to both the primary and breaker failure relays, failure of one fuse would be more severe than failure of either one of the relays. Similar dependencies can occur in specific designs in the implementation of microprocessor installations. As another example, if a protection system designed includes a shared voltage or current sensing device that provides input to relays for both the primary and backup protection systems, failure of this voltage sensing device would be more severe than failure of either one of the relays.</P>
        <P>32. As a result, the planner's selection of a protection system component failure may be influenced by the protection system as-built design. If one protection system component was an integral component of primary protection and breaker failure protection, then it is possible that the loss of that one component would produce the more severe system impact. If, in this example, the protection system component failure was not a relay component, as described in Category P5 of the proposed TPL Standard, it appears that this more severe contingency (loss of both the primary protection and breaker failure protection systems due to the loss of one protection system component) would not be assessed under the proposed TPL Reliability Standard.</P>
        <P>33. The Commission seeks comments on whether the proposed TPL Reliability Standard, in the provisions pertaining to study of multiple contingencies, limits the planners' assessment of a protection system failure because it only includes the contingency of a faulty relay component. The Commission also seeks comments on whether, based on protection system as-built designs, the relay may not always be the larger contingency, and how the loss of protection system components that may be integral to multiple protection systems impacts reliability.</P>
        <HD SOURCE="HD2">D. Assessment of Backup or Redundant Protection Systems</HD>
        <P>34. NERC states that proposed Reliability Standard TPL-001-2, Requirement R3, Part 3.3.1 and Requirement R4, Part 4.3.1 require that simulations faithfully duplicate what will happen in an actual power system based on the expected performance of the protection systems.<SU>40</SU>
          <FTREF/>According to NERC, these requirements ensure that if a protection system is designed “to remove multiple Elements from service for an event that the simulation will be run with all of those Elements removed from service.”<SU>41</SU>
          <FTREF/>This proposal is intended to instill event-based analysis over simple element analysis which will provide for more accurate simulations.</P>
        <FTNT>
          <P>
            <SU>40</SU>NERC Petition at 20.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>41</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>35. The current TPL Reliability Standards state that a planner must include the effects of existing and planned protection systems, including any backup or redundant systems in its planning assessment.<SU>42</SU>
          <FTREF/>Specifically, Reliability Standard TPL-003-0, Requirement R1.3.10 requires the planner to “[i]nclude the effects of existing and planned protection systems, including any backup or redundant systems.”<SU>43</SU>
          <FTREF/>For this requirement, the planner must include the effects all protection systems, including backup or redundant protection systems.</P>
        <FTNT>
          <P>
            <SU>42</SU>
            <E T="03">E.g.,</E>Reliability Standards TPL-003-0, R1.3.10 and TPL-004-0, R1.3.7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>43</SU>Reliability Standard TPL-003-0, R1.3.10 and TPL-004-0, Requirement R1.3.7.</P>
        </FTNT>
        <P>36. NERC states that Reliability Standard TPL-001-2, Requirement R3, Part 3.3.1 and Requirement R4, Part 4.3.1 require the planner to “[s]imulate the removal of all elements that the Protection System and other automatic controls are expected to disconnect for each Contingency without operator intervention.” The proposed NERC provision, however, does not explicitly refer to “backup or redundant systems” as in the currently effective TPL standards. The Commission seeks clarification from the ERO whether the proposed Requirements address all protection systems, including backup and redundant protection systems that can have an impact on the performance of the bulk electric system.</P>
        <HD SOURCE="HD2">E. P5 Single Line to Ground Faults</HD>

        <P>37. Table 1 of the proposed Reliability Standard TPL-001-2 identifies the<PRTPAGE P="26720"/>initiating contingencies that must be evaluated to ensure that the planned system meets the performance requirements. These proposed modifications to Table 1 include changing the classification of the events, clarifying events and fault types, and removing the ambiguity of performance requirements. NERC states the proposed Reliability Standard TPL-001-2, Table 1, P5 events are limited to the Single Line to Ground (SLG) Fault type consistent with the comparable C6-C9 events from Table 1 in the currently-effective TPL Reliability Standards. NERC treats SLG and three phase faults as different events even if an SLG event evolves into a three phase fault.<SU>44</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>44</SU>NERC Petition at 49. Three phase events in the existing TPL standards are shown in Table 1, D1-D4 and are retained in TPL-001-2, Table 1, Extreme Events.</P>
        </FTNT>
        <P>38. The proposed Reliability Standard TPL-001-2, Table 1 includes a column titled “fault type,” which contains the specific designation of the fault type such as SLG or three-phase faults. “Fault type” is described as a SLG or three-phase fault types that must be evaluated in stability simulations for the event described. For example, a SLG fault could evolve into a 3-phase fault, but the initiating fault is the SLG fault and the associated SLG performance criteria must be applied, not the three-phase performance criteria. The Commission seeks clarification from the ERO whether “fault types” in Table 1 of the proposed Reliability Standard refers to the initiating event or initiating fault for the contingency rather than the type of fault in to which the initiating fault may evolve and how the clarification is consistent with the simulations being representative of what will occur in real-time.</P>
        <HD SOURCE="HD2">F. Order No. 693 Directives</HD>
        <P>39. While the Commission proposes to remand based on the presence of footnote 12, the balance of proposed Reliability Standard TPL-001-2 appears responsive to the Order No. 693 directives regarding the TPL Reliability Standards. The Commission, however, seeks clarification and comment on the following.</P>
        <HD SOURCE="HD3">1. Peer Review of Planning Assessments</HD>
        <P>40. In Order No. 693, the Commission stated that it “sees no reason why peer reviews should not be part of a Reliability Standard since TPL-001-0 through TPL-004-0 already include…a review of assessment by the associated regional reliability organization.”<SU>45</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>45</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1755.</P>
        </FTNT>
        <P>The Commission also stated that because neighboring systems may be adversely impacted by other neighboring systems, such systems should be involved in determining and reviewing system conditions and contingencies to be assessed under the currently-effective TPL Standards.<SU>46</SU>
          <FTREF/>Furthermore, the peer review provides for a neighboring entity to identify possible interdependent or adverse impacts on its neighboring systems and thus, provides for an early opportunity to provide input and coordinate plans.<SU>47</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>46</SU>
            <E T="03">Id.</E>P 1750.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>47</SU>
            <E T="03">Id.</E>P 1754.</P>
        </FTNT>
        <P>41. NERC states the proposed Reliability Standard does not include a “peer review” of planning assessments but instead includes “an equally effective and efficient manner to provide for the appropriate sharing of information with neighboring systems” with the incorporation of Requirement R3, Part 3.4.1, Requirement R4, Part 4.4.1, and Requirement R8.<SU>48</SU>
          <FTREF/>Part 3.4.1 provides:</P>
        <FTNT>
          <P>
            <SU>48</SU>NERC Petition at 21.</P>
        </FTNT>
        
        <EXTRACT>
          <P>The Planning Coordinator and Transmission Planner shall coordinate with adjacent Planning Coordinators and Transmission Planners to ensure that Contingencies on adjacent Systems which may impact their Systems are included in the Contingency list.<SU>49</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>49</SU>Proposed Reliability Standard, TPL-001-2, Requirement R3, Part 3.3.1. Part 4.4.1 is in all material respects the same as Part 3.3.1.</P>
          </FTNT>
        </EXTRACT>
        
        <FP>NERC explains that “an entity may always decline an offer to participate in a peer review even when they should participate” and “the distribution approach means that the entity will always receive the Planning Assessment.”<SU>50</SU>
          <FTREF/>NERC further states in “the course of the continuing cycle of Planning Assessments, comments from other entities at the end of a planning cycle will be utilized at the beginning of the next cycle as the planner moves forward in time.”<SU>51</SU>
          <FTREF/>
        </FP>
        <FTNT>
          <P>
            <SU>50</SU>NERC Petition at 22. Requirement R8 requires distribution to adjacent planning coordinators and transmission planners within 90 days and to others with a reliability related need that submits a request within 30 days of receiving such a request.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>51</SU>NERC Petition at 22.</P>
        </FTNT>
        <P>42. The Commission seeks clarification on how the NERC proposal ensures the early input of peers into the planning assessments or any type of coordination amongst peers will occur. The Commission seeks comment on whether and how there is a sufficient level of evaluation and ability to provide feedback to the planners on the development and result of assessments. In addition, NERC states that that Requirement R8 “ensures that information is shared with * * * adjacent entities” which “ensures * * * input received from adjacent entities.”<SU>52</SU>
          <FTREF/>The Commission also seeks comment on whether Requirement R8 requires input on the comments to be included in the results or the development of the Planning Assessments.</P>
        <FTNT>
          <P>
            <SU>52</SU>Id. at 44.</P>
        </FTNT>
        <HD SOURCE="HD3">2. Spare Equipment Strategy</HD>
        <P>43. In Order No. 693, the Commission directed NERC to develop a modification “to require assessments of outages of critical long lead-time equipment, consistent with the entity's spare equipment strategy.”<SU>53</SU>
          <FTREF/>In response, NERC developed proposed Requirement 2, Part 2.1.5 which addresses steady state conditions to determine system response when equipment is unavailable for prolonged periods of time. The studies must be performed for the P0, P1, and P2 categories in Table 1 “under the condition that the system is expected to experience during the possible periods of unavailability of the long lead-time equipment.” NERC states that “[s]tability impacts related to outages of critical long lead-time equipment will not be addressed in a separated requirement but rather will be analyzed in the normal planning process.”<SU>54</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>53</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1786.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>54</SU>NERC Petition at 25.</P>
        </FTNT>
        <P>44. NERC's spare equipment strategy appears to have limited the strategy to steady state analysis (excluded stability analysis).<SU>55</SU>
          <FTREF/>While including a spare equipment strategy in the proposed Reliability Standard is an improvement, the Commission seeks clarification as to why stability analysis conditions were excluded from the spare equipment strategy.</P>
        <FTNT>
          <P>
            <SU>55</SU>Proposed Reliability Standard TPL-001-2, Requirement R 2.1.5.</P>
        </FTNT>
        <HD SOURCE="HD3">3. Controlled Load Interruption</HD>
        <P>45. In Order No. 693, the Commission directed the ERO to modify footnote (c) of Table 1 to the Reliability Standard TPL-003-0a to clarify the term “controlled load interruption” to “ensure that third parties have access to the same options that the transmission owner uses to alleviate reliability constraints including those related to controlled load shedding.”<SU>56</SU>

          <FTREF/>NERC states in its petition that it excluded the term “controlled load interruption” in the proposed Reliability Standard TPL-001-2, but NERC does not explain the<PRTPAGE P="26721"/>reason for its exclusion.<SU>57</SU>
          <FTREF/>NERC added the term “Non-Consequential Load Loss” to the proposed Reliability Standard TPL-001-2, Table 1 and defined “Non-Consequential Load Loss” as: Non-Interruptible Load loss that does not include: (1) Consequential Load Loss, (2) the response of voltage sensitive Load, or (3) Load that is disconnected from the System by end-user equipment.<SU>58</SU>
          <FTREF/>In addition, NERC added a new Requirement R2.1.4 for the Near-Term Transmission Planning Horizon portion of steady-state analysis that includes “Controllable Loads” as one of the conditions the planning assessment must vary in the sensitivity analysis for system peak load for year one or year two, and for year five and for system off-peak load for one of the five years.</P>
        <FTNT>
          <P>
            <SU>56</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1818.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>57</SU>NERC Petition at 28.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>58</SU>In Order No. 693, the Commission explained that the term “consequential load loss” referred to “the load that is directly served by the elements that are removed from service as a result of the contingency.” Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1794 n.461.</P>
        </FTNT>
        <P>46. The term “controlled load interruption” is found in footnote (c) which is applicable to “Loss of Demand or Curtailed Firm Transfers” in Table 1 of the existing TPL Reliability Standards. The term “Loss of Demand or Curtailed Firm Transfers” for controlled load interruptions in Table 1 of the current TPL Standards appears to be applicable to “Non-Consequential Load Loss Allowed” in Table 1 of the proposed TPL Standard. The Commission seeks clarification from the ERO if third-parties have access to the same options that the transmission owner has to alleviate reliability constraints including load shedding options for “Controllable Loads” in Requirement 2.1.4 and “Non-Consequential Load Loss Allowed” in Table 1 of the proposed Reliability Standard TPL-001-2.</P>
        <HD SOURCE="HD3">4. Range of Extreme Events</HD>
        <P>47. In Order No. 693 the Commission directed the ERO to modify Reliability Standard TPL-004-0 to require that, in determining the range of the extreme events to be assessed, the contingency list of Category D would be expanded to include recent events such as hurricanes and ice storms. NERC's proposed Reliability Standard TPL-001-2 appropriately expands the list of extreme event examples in Table 1, but the list limits these items to the loss of two generating stations under Item No. 3a.<SU>59</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>59</SU>NERC Petition at 29-30.</P>
        </FTNT>
        <P>48. The Commission seeks clarification from the ERO on conditioning extreme events on the loss of two generating stations.<SU>60</SU>
          <FTREF/>The Commision understands that there are scenarios where an extreme event can impact more than two generation stations that might not be captured due to the “two generation stations” restriction in Item No. 3a. For example, within the Florida peninsula, depending on the location within the state, either two or three main gas pipelines supply the majority of the generation for the area. In this scenario, the loss of one of the gas pipelines would result in the loss of more than two generation stations. The Commission seeks clarification regarding whether this scenario is otherwise covered under the catch-all provision in Item No. 3b which states “[o]ther events based upon operating experience that may result in wide area disturbances.”</P>
        <FTNT>
          <P>
            <SU>60</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD3">5. Assessments and Documentation</HD>
        <P>49. The Commission seeks clarification from the ERO that planning assessments and associated documentation will include accurate representations of results on the bulk electric system with respect to the following.</P>
        <HD SOURCE="HD3">a. Dynamic Load Models</HD>
        <P>50. In Order No. 693, the Commission directed “the ERO to modify the Reliability Standard to require documentation of load models used in system studies and the supporting rationale for their use.”<SU>61</SU>
          <FTREF/>Proposed Reliability Standard TPL-001-2, Requirement 2.4, Part 2.4.1 requires a load model which represents the expected dynamic behavior of loads that could impact a study area, considering the behavior of induction motor loads. NERC states that this addition to the proposed standard addresses the specifics of the Order No. 693 directive that requires “[d]ocument(ing) the load models used in system studies and the supporting rationale for their use.”<SU>62</SU>
          <FTREF/>Under the proposed Requirement R2, entities are required to document assumptions made in the planning assessments. The Commission seeks clarification on whether the documentation of the dynamic load models used in system studies and the supporting rationale for their use under Requirement 2.4, Part 2.4.1 will be included in the documented assumptions under Requirement R2.</P>
        <FTNT>
          <P>
            <SU>61</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1789.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>62</SU>NERC Petition at 26.</P>
        </FTNT>
        <HD SOURCE="HD3">b. Proxies To Simulate Cascade</HD>
        <P>51. In Order No. 693, the Commission observed that “if an entity models overload relays, undervoltage relays, all remedial action schemes including those of neighboring systems and has a good load representation, then proxies are not required. However, due to modeling and simulation limitations this is often not the case and planners invariably use proxies.”<SU>63</SU>
          <FTREF/>Additionally, the Commission stated that sharing of proxies will improve knowledge and understanding and promote a more rigorous approach to analyzing cascading outages. Accordingly, the Commission directed the ERO to modify the Reliability Standard to require “definition and documentation of proxies necessary to simulate cascading outages.”<SU>64</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>63</SU>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1819.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>64</SU>
            <E T="03">Id.</E>P 1820.</P>
        </FTNT>
        <P>52. NERC states that proposed Requirement R6 “specifies that an entity must define and document the criteria or methodology used to identify system instability for conditions such as cascading, voltage instability, or uncontrolled islanding within its Planning Assessment.”<SU>65</SU>
          <FTREF/>NERC adds that this specificity in identifying these “proxies” is an important clarification in the proposed revised standard and “will lead to greater transparency in the planner's evaluation techniques.”<SU>66</SU>
          <FTREF/>The Commission seeks clarification on whether Requirement R6 includes the documentation of proxies and that Requirement R8 includes the sharing of the documented proxies in the planning assessments.</P>
        <FTNT>
          <P>
            <SU>65</SU>NERC Petition at 43-44.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>66</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD3">c. Footnote `a'</HD>
        <P>53. In Order No. 693 the Commission directed NERC to modify “footnote (a) of Table 1 with regard to applicability of emergency rating and consistency of normal ratings and voltages with values obtained from other reliability standards.”<SU>67</SU>
          <FTREF/>NERC notes that proposed Table 1, header note `e,' which states planned system adjustments must be executable within the time duration applicable to facility ratings, and header note `f,' which states applicable facility ratings shall not be exceeded, meets this directive thereby replacing footnote `a' in the current standard.</P>
        <FTNT>
          <P>
            <SU>67</SU>
            <E T="03">Id.</E>at 24.</P>
        </FTNT>

        <P>54. The Commission observes that the proposed standard applies header note `e' to “Steady State and Stability” while header note `f' is excluded from “Stability” and only applies to “Steady<PRTPAGE P="26722"/>State” studies. The Commission seeks clarification from the ERO regarding the rationale for excluding header note `f' from “Stability” studies. Additionally, the Commission seeks clarification on which Reliability Standards the entities should utilize when obtaining the values to be used in their Planning Assessments. In addition, for Table 1, header notes `e' and `f,' the Commission seeks comment on whether the normal facility ratings align with, for example, FAC-008-1 and normal voltage ratings align with VAR-001-1. Furthermore, the Commission seeks clarification from the ERO whether facility ratings used in planning assessments align with other reliability standards such as NUC-001-2, BAL-001-0.1a and PRC Standards for UFLS and UVLS.</P>
        <HD SOURCE="HD2">G. Commission Proposal</HD>
        <P>55. The Commission proposes to remand NERC's proposed TPL Reliability Standard. While much of the proposed Reliability Standard TPL-001-2 appears just, reasonable, not unduly discriminatory or preferential, and in the public interest, we find that footnote 12, allowing for transmission planners to plan for non-consequential load loss following a single contingency without adequate safeguards, undermines the potential benefits the proposed Reliability Standard may provide . This is consistent with the Commission's Final Rule in Docket No. RM11-18-000 remanding footnote `b,' which is substantially the same as footnote 12. Thus, the Commission proposes to remand the proposed Reliability Standard TPL-001-2 to NERC.</P>
        <HD SOURCE="HD1">III. Information Collection Statement</HD>
        <P>56. The Office of Management and Budget (OMB) regulations require that OMB approve certain reporting and recordkeeping (collections of information) imposed by an agency.<SU>68</SU>
          <FTREF/>The information contained here is also subject to review under section 3507(d) of the Paperwork Reduction Act of 1995.<SU>69</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>68</SU>5 CFR 1320.11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>69</SU>44 U.S.C. 3507(d).</P>
        </FTNT>
        <P>57. As stated above, the subject of this NOPR is NERC's proposed modifications to the TPL Reliability Standards. This NOPR proposes to remand the proposed revisions to NERC. By remanding the proposal, the applicable Reliability Standards and any information collection requirements are unchanged. Therefore, the Commission will submit this NOPR to OMB for informational purposes only.</P>

        <P>58. Interested persons may obtain information on the reporting requirements by contacting the following: Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426 [Attention: Ellen Brown, Office of the Executive Director, email:<E T="03">data.clearance@ferc.gov</E>, phone: (202) 502-8663, or fax: (202) 273-0873].</P>
        <HD SOURCE="HD1">IV. Regulatory Flexibility Act</HD>
        <P>59. The Regulatory Flexibility Act of 1980 (RFA)<SU>70</SU>
          <FTREF/>generally requires a description and analysis of final rules that will have significant economic impact on a substantial number of small entities. The RFA mandates consideration of regulatory alternatives that accomplish the stated objectives of a proposed rule and that minimize any significant economic impact on a substantial number of small entities. The Small Business Administration's (SBA) Office of Size Standards develops the numerical definition of a small business.<SU>71</SU>
          <FTREF/>The SBA has established a size standard for electric utilities, stating that a firm is small if, including its affiliates, it is primarily engaged in the transmission, generation and/or distribution of electric energy for sale and its total electric output for the preceding twelve months did not exceed four million megawatt hours.<SU>72</SU>
          <FTREF/>The RFA is not implicated by this NOPR because the Commission is remanding the proposed TPL Reliability Standard and not proposing any modifications to the existing burden or reporting requirements. With no changes to the Reliability Standards as approved, the Commission certifies that this NOPR will not have a significant economic impact on a substantial number of small entities.</P>
        <FTNT>
          <P>
            <SU>70</SU>5 U.S.C. 601-612.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>71</SU>13 CFR 121.201.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>72</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD1">V. Comment Procedures</HD>

        <P>60. The Commission invites interested persons to submit comments on the matters and issues proposed in this notice to be adopted, including any related matters or alternative proposals that commenters may wish to discuss. Comments are due 60 days from publication in the<E T="04">Federal Register</E>. Comments must refer to Docket No. RM12-1-000, and must include the commenter's name, the organization they represent, if applicable, and their address in their comments.</P>

        <P>61. The Commission encourages comments to be filed electronically via the eFiling link on the Commission's Web site at<E T="03">http://www.ferc.gov.</E>The Commission accepts most standard word processing formats. Documents created electronically using word processing software should be filed in native applications or print-to-PDF format and not in a scanned format. Commenters filing electronically do not need to make a paper filing.</P>
        <P>62. Commenters that are not able to file comments electronically must send an original of their comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street NE., Washington, DC 20426.</P>
        <P>63. All comments will be placed in the Commission's public files and may be viewed, printed, or downloaded remotely as described in the Document Availability section below. Commenters on this proposal are not required to serve copies of their comments on other commenters.</P>
        <HD SOURCE="HD1">VI. Document Availability</HD>

        <P>64. 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:00 p.m. Eastern time) at 888 First Street NE., Room 2A, Washington DC 20426.</P>
        <P>65. 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>66. 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 email at<E T="03">ferconlinesupport@ferc.gov</E>, or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. Email the Public Reference Room at<E T="03">public.referenceroom@ferc.gov.</E>
        </P>
        <SIG>
          <P>By direction of the Commission. Commissioner Norris is concurring in part with a separate statement attached.</P>
          <NAME>Kimberly D. Bose,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
        <FP>Norris, Commissioner,<E T="03">concurring in part:</E>
        </FP>
        
        <EXTRACT>

          <P>In today's order, the Commission proposes to remand proposed Transmission Planning Reliability Standard TPL-001-2 to NERC, based on the decision by the Commission to remand proposed TPL-002-0b in the concurrently-issued<E T="03">Transmission Planning<PRTPAGE P="26723"/>Reliability Standards.</E>
            <SU>1</SU>
            <FTREF/>For the reasons articulated in my separate statement in Order No. 762, I agree with the decision here to remand proposed TPL-001-2, but I do not fully agree with the basis identified by the majority in their decision.</P>
          <FTNT>
            <P>
              <SU>1</SU>Order No. 762, 139 FERC ¶ 61,060 (2012).</P>
          </FTNT>
          <P>Thus, I respectfully concur in part.</P>
          
          <FP>John R. Norris,</FP>
          <FP>
            <E T="03">Commissioner</E>
          </FP>
        </EXTRACT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10943 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Transit Administration</SUBAGY>
        <CFR>49 CFR Part 661</CFR>
        <DEPDOC>[Docket No. FTA-2012-0009]</DEPDOC>
        <SUBJECT>Notice of Proposed Buy America Waivers</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Transit Administration (FTA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed Buy America waivers and request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Federal Transit Administration (FTA) received several requests to waive its Buy America requirements for products used in ticket vending machines—the Mars Electronics International (MEI) Sodeco BNA57/542 Bill Handling Unit, and BNR3-XX, BNR4-XX and BNR5-XX Bank Note Recycler product; and the Nextek Corporation (Nextek) BV-6000AG (BV-6000) Currency Validator Tekpak. FTA seeks public comment before deciding whether to grant the requests.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received by June 6, 2012. Late filed comments will be considered to the extent practicable.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Please submit your comments by only one of the following means, identifying your submissions by docket number FTA-2012-0009. All electronic submissions must be made to the U.S. Government electronic site at<E T="03">www.regulations.gov.</E>Commenters should follow the instructions below for mailed and hand delivered comments.</P>
          <P>(1)<E T="03">Web site: www.regulations.gov.</E>Follow the instructions for submitting comments on the U.S. Government electronic docket site;</P>
          <P>(2)<E T="03">Fax:</E>(202) 493-2251;</P>
          <P>(3)<E T="03">Mail:</E>U.S. Department of Transportation, 1200 New Jersey Avenue SE., Docket Operations, M-30, Room W12-140, Washington DC, 20590-0001.</P>
          <P>(4)<E T="03">Hand Delivery:</E>Room W12-140 on the first floor of the West Building, 1200 New Jersey Avenue SE, Washington, DC 20590, between 9:00 a.m. and 5:00 p.m., Monday through Friday, except Federal holidays.</P>
          <P>
            <E T="03">Instructions:</E>All submissions must refer to the “Federal Transit Administration” and include docket number FTA-2012-0009. Due to security procedures in effect since October 2001, mail received through the U.S. Postal Service may be subject to delays. Parties making submissions responsive to this notice should consider using an express mail firm to ensure the prompt filing of any submissions not filed electronically or by hand. Note that all submissions received, including any personal information therein, will be posted without change or alteration to<E T="03">www.regulations.gov.</E>For More information, 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), or visit<E T="03">www.regulations.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Jayme L. Blakesley at (202) 366-0304 or<E T="03">jayme.blakesley@dot.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLMENTARY INFORMATION:</HD>
        <P>The purpose of this notice is to seek public comment on whether the Federal Transit Administration should continue to waive its Buy America requirements for two years for Mars Electronics International (MEI)'s Sodeco BNA57/542 Bill Handling Unit BNR3-XX, BNR4-XX and BNR5-XX Bank Note Recycler products, and the Nextek Corporation's (Nextek) BV-6000AG (BV-6000) Currency Validator Tekpak, or whether FTA should extend the non-shift approach adopted in its 2007 Final Rule (72 FR 53688, September 20, 2007) to the procurement of such devices.</P>
        <HD SOURCE="HD1">Waiver Request: MEI Sodeco BNA57/542 Bill Handling Unit</HD>
        <P>MEI requested an extension of the Buy-America non-availability component waiver under CFR 661.7(g) for the MEI Sodeco BNA57/542 Bill Handling Units. The FTA granted the initial waiver for these products on July 21, 2000, and has extended the waiver periodically ever since, on December 10, 2003, November 12, 2004, October 20, 2006, and February 23, 2009.</P>
        <P>Buy America requires, with few exceptions, that all steel, iron and manufactured goods used in FTA-funded projects be produced in the United States. One such exception is that of non-availability, that in some instances steel, iron, and goods produced in the United States are not produced in the United States in sufficient and reasonably available quantities or are not of a satisfactory quality. Therefore, Congress authorized FTA to waive the above requirement and allow, based on non-availability, the use in an FTA-funded project of steel, iron or manufactured goods produced outside the United States.</P>
        <P>According to MEI, the Sodeco BNA57/542 Bill Handling Units includes a multiple bill escrow (up to 15 bills) that enables return of the customer's inserted bills in situations where the transaction is not complete. The unit has the ability to identify, validate and accept multiple note denominations (US $1, $5, $10, $20, $50, $100) utilizing all optical recognition, and allowing for the acceptance of bills in a face up or face down orientation. It also supports remote download, giving a transit agency the option of downloading new bill recognition software (bill variants) via network from one central location.</P>
        <P>MEI's customers include the Washington Metropolitan Area Transit Authority (WMATA), New York City Transit (MTA), and the Bay Area Rapid Transit Authority (BART).</P>
        <P>In 1999, to support its initial waiver request, MEI performed a market research study. It found no equivalent products manufactured within the United States. In preparation of the instant waiver request, MEI reviewed its earlier findings and compared them with the known providers of payment systems to the transit market. They found no US manufacturers of functionally equivalent products. Companies they identified who supply a similar product—GAO/Geiseke &amp; Deviran (G&amp;D), Toyocom, and Cashcode—all manufacture their products outside of the United States.</P>
        <HD SOURCE="HD1">Waiver Request: MEI BNY3-XX &amp; BNR5-XX Bank Note Recycler Products</HD>

        <P>In a letter dated February 28, 2011, MEI requested an extension of the Buy America non-availability component waiver under CFR 667.7(g) for BNY3-XX &amp; BNR5-XX Bank Note Recycler products. The initial waiver was granted by FTA on October 20, 2008. The Bank Note Recycler (BNR) can accept and validate bank notes and pay them back out as change. The unit has the ability to identify, validate and accept multiple bank note denominations (US $1, $5, $10, $20, $50, $100) utilizing all optical recognition. This allows for the acceptance of bank notes in a face-up or facedown orientation. The unit has multiple-note escrow function (up to 15 Bank notes) that enables return of the customer's inserted bank notes, in situations where the transaction is not complete, or presentation of bank notes<PRTPAGE P="26724"/>being paid back as change in one bundle. The BNR performs this operation through a single hole in the Ticket Vending Machine (TVM) cabinet. It can utilize up to four separate recycling devices on which bank notes are accumulated and from which bank notes are dispensed as change. The unit also has a “loader cassette” which provides temporary storage of bank notes that are used to restock the recyclers when they become empty due to excessive change making. This “loader cassette” is protected against theft by lock and key and remote download. MEI asserts that there are no US manufacturers of functionally equivalent products. The only other manufacturer they identified is Cashcode, which manufactures outside the United States.</P>
        <HD SOURCE="HD1">Waiver Request: Nextek Corporation: BV-6000AG (BV-6000) Currency Validator</HD>
        <P>Nextek Corporation (Nextek) requests a Buy America waiver for the BV-6000AG (BV-6000) Currency Validator; which is manufactured in Japan by Toyo Networks &amp; System Integration, Ltd. (TNSi) for use in ticket vending machines. After calling for notice and comment, FTA granted a non-availability waiver to the Nextek Corporation for the BV-6000 on October 20, 2006. No domestic supplier has made itself known to FTA.</P>
        <HD SOURCE="HD1">Applicability of FTA's 2007 Regulatory Amendments</HD>
        <P>In its September 2007 Final Rule (72 FR 53688), FTA adopted a non-shift approach to address the aftermarket procurement of replacement components and subcomponents. Prior to the adoption of the Final Rule, procurements of replacements parts were treated as procurements of end products, i.e., not only must the deliverable item be manufactured in the United States, but each component must also be of domestic origin. Implementation of this policy led to confusion and inconsistencies among transit operators and their suppliers, who urged FTA to adopt a non-shift approach that would treat replacement parts consistent with the procurement of the original product, i.e., if a product was a subcomponent in the initial procurement, it would be treated as a subcomponent in all subsequent procurements. This approach, according to proponents, would foster reasonable predictability and stability in the transit business community, enable bidders and vendors to price proposals more accurately, and allow transit agencies to obtain more competitive pricing.</P>
        <P>In the same rulemaking, FTA added the term “system” to its definition of “end product.” Prior to the rulemaking, the manufacturer of a fare collection system filed complaints with FTA concerning the regulatory compliance of a fare collection system manufactured by a competitor. The complainant posited that every mechanical component of the fare collection system should be treated as an end product—ticket vending machines, fareboxes, faregates, etc. not only would have to be manufactured in the United States, but each component of those devices would similarly need to be of domestic origin. Under this interpretation, the petitioners and their customers would have needed a Buy America waiver in order to install a foreign-made bill-handler, bank note recycler, and currency validator into a US-made fare collection device.</P>
        <P>In the Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU) (Pub L. 109-59, August 10, 2005), Congress directed FTA to address the procurement of systems to ensure that major system procurements were not used to circumvent Buy America requirements. FTA sought comment on whether it should include “systems” within the definition of “end product.” Commenters generally supported this approach, with a caveat that FTA should tightly monitor the treatment of systems to ensure that procurements of extremely large and complex super-systems would not be able to undermine the intent of FTA's Buy America requirements. Among the factors FTA examines in assessing whether a “system” is an “end product” are: (1) Whether the items are the subject of a single procurement; (2) whether the parts of that system are under a single warranty; (3) whether the resulting end product was functionally different from a mere assembly of elements or materials; and most importantly; (4) whether the individual parts performed on a integrated basis with the other parts of the system.</P>
        <P>Based on SAFETEA-LU and its 2007 rulemaking, FTA believes fare collection devices can be regarded as components, and their constituent parts treated as subcomponents, which, consistent with 49 CFR 661.5(d)(2), could come from any foreign or domestic source, provided that the component itself was manufactured in the United States. A formal FTA adoption of this approach would eliminate the need for firms such as MEI and Nextek to seek biennial waivers that would permit the inclusion of foreign subcomponents into their devices, particularly when no interested domestic vendor has identified itself to FTA or the two petitioners during the intervening decade.</P>
        <P>FTA invites comment on MEI and Nextek's waiver request and the classification of such devices as subcomponents from all interested parties. Commenters may wish to address potential ramifications of categorizing these devices as subcomponents, whether there are domestically-manufactured substitutes, whether petitioners have done an adequate job of reaching out to potential domestic manufacturers, and what FTA can do to encourage domestic firms to manufacture products that are the subject of these non-availability waiver requests.</P>
        <P>In the interest of transparency, FTA has published copies of MEI's and Nextek's requests to the docket. Interested parties may submit comments on or before June 6, 2012. Late-filed comments will be considered to the extent practicable.</P>
        <SIG>
          <DATED>Issued this 1st day of May 2012.</DATED>
          <NAME>Dorval R. Carter, Jr.,</NAME>
          <TITLE>Chief Counsel.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10851 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </PRORULE>
  </PRORULES>
  <VOL>77</VOL>
  <NO>88</NO>
  <DATE>Monday, May 7, 2012</DATE>
  <UNITNAME>Notices</UNITNAME>
  <NOTICES>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="26725"/>
        <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBJECT>Advisory Committee on Biotechnology and 21st Century Agriculture Meeting</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Under Secretary, Research, Education, and Economics, Agricultural Research Service, USDA.</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, 5 U.S.C. App. 2, the United States Department of Agriculture announces a meeting of the Advisory Committee on Biotechnology and 21st Century Agriculture (AC21).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The meeting dates are May 29-30, 2012, 8:30 a.m. to 5 p.m. each day.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>U.S. Access Board Conference Room, 1331 F Street NW., Suite 800, Washington, DC 20004-1111.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Michael Schechtman, Designated Federal Official, Office of the Deputy Secretary, USDA, 202B Jamie L. Whitten Federal Building, 12th and Independence Avenue SW., Washington, DC 20250; Telephone (202) 720-3817; Fax (202) 690-4265; Email<E T="03">AC21@ars.usda.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>The next meeting of the AC21 has been scheduled for May 29-30, 2012. The AC21 consists of members representing the biotechnology industry, the organic food industry, farming communities, the seed industry, food manufacturers, state government, consumer and community development groups, as well as academic researchers and a medical doctor. In addition, representatives from the Department of Commerce, the Department of Health and Human Services, the Department of State, the Environmental Protection Agency, the Council on Environmental Quality, and the Office of the United States Trade Representative have been invited to serve as “<E T="03">ex officio</E>” members. The Committee meeting will be held from 8:30 a.m. to 5:00 p.m. on each day. The topics to be discussed will include: final reports from the four AC21 working groups on analyses relevant to the overall AC21 charge; potential economic impacts on farmers from the escape of certain genetically engineered crops with functional traits; and further analysis of committee members' views related to the Committee charge in order to identify areas of agreement as well as differences and to prepare for development of a draft report.</P>

        <P>Background information regarding the work and membership of the AC21 is available on the USDA Web site at<E T="03">http://www.usda.gov/wps/portal/usda/usdahome?contentid=AC21Main.xml&amp;contentidonly=true.</E>Members of the public who wish to make oral statements should also inform Dr. Schechtman in writing or via Email at the indicated addresses at least three business days before the meeting. On May 29, 2012, if time permits, reasonable provision will be made for oral presentations of no more than five minutes each in duration.</P>

        <P>The meeting will be open to the public, but space is limited. If you would like to attend the meetings, you must register by contacting Ms. Dianne Fowler at (202) 720-4074 or by Email at<E T="03">Dianne.fowler@ars.usda.gov</E>at least 5 days prior to the meeting. Please provide your name, title, business affiliation, address, telephone, and fax number when you register. If you are a person with a disability and request reasonable accommodations to participate in this meeting, please note the request in your registration. All reasonable accommodation requests are managed on a case by case basis.</P>
        <SIG>
          <DATED>Dated: April 18, 2012.</DATED>
          <NAME>Ann Bartuska,</NAME>
          <TITLE>Deputy Under Secretary, Research, Education and Economics.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10264 Filed 5-3-12; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 3410-03-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Food Safety and Inspection Service</SUBAGY>
        <DEPDOC>[Docket No. FSIS-2011-0009]</DEPDOC>
        <SUBJECT>Changes to FSIS Traceback, Recall Procedures for Escherichia coli O157:H7 Positive Raw Beef Product, and Availability of Compliance Guidelines</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food Safety and Inspection Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Food Safety and Inspection Service (FSIS) is announcing proposed new procedures that it intends to implement when FSIS or other Federal or State agencies find raw ground beef presumptive positive for<E T="03">Escherichia coli</E>(<E T="03">E. coli</E>) O157:H7. This methodology will enable FSIS to better determine whether the establishments that produced the source materials for contaminated product have produced other product that may not be microbiologically independent from the contaminated product. The Agency is also announcing its intention to now, as a matter of routine policy, request a recall if an establishment was the sole supplier of beef trim source materials for ground product that FSIS or other Federal or State agencies find positive for<E T="03">E. coli</E>O157:H7, evidence suggests that contamination most likely occurred at the supplier establishment, and a portion of the product from the originating source lot was sent to other establishments. This notice also explains that FSIS intends to determine whether it can make better use of establishment results and also intends to conduct a study to help it identify the source of<E T="03">E. coli</E>O157:H7 positive ground beef when the material from multiple suppliers was used to produce positive product. Finally, this notice announces the availability of compliance guidelines concerning establishment sampling and testing for shiga toxin-producing<E T="03">E. coli</E>(STEC) organisms or virulence markers and compliance guidelines for<E T="03">E. coli</E>O157:H7 sampled and tested labeling claims.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>

          <P>FSIS requests comments on policies and procedures in this notice by July 6, 2012. FSIS intends to evaluate comments, make any necessary changes to policies and procedures based on<PRTPAGE P="26726"/>comments and announce final policies, procedures, and implementation dates in a subsequent<E T="04">Federal Register</E>notice.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>FSIS invites interested persons to submit comments on this notice. Comments may be submitted by one of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>This Web site provides the ability to type short comments directly into the comment field on this Web page or attach a file for lengthier comments. Go to<E T="03">http://www.regulations.gov.</E>Follow the on-line instructions at that site for submitting comments.</P>
          <P>•<E T="03">Mail, including CD-ROMs, etc.:</E>Send to Docket Clerk, U.S. Department of Agriculture, Food Safety and Inspection Service, Patriots Plaza 3, 1400 Independence Avenue SW., Mailstop 3782, Room 8-163A, Washington, DC 20250-3700.</P>
          <P>•<E T="03">Hand- or courier-delivered submittals:</E>Deliver to Patriots Plaza 3, 355 E. Street SW., Room 8-163A, Washington, DC 20250-3700.</P>
          <P>
            <E T="03">Instructions:</E>All items submitted by mail or electronic mail must include the Agency name and docket number FSIS-2011-0009. Comments received in response to this docket will be made available for public inspection and posted without change, including any personal information, to<E T="03">http://www.regulations.gov.</E>
          </P>
          <P>
            <E T="03">Docket:</E>For access to background documents or comments received, go to the FSIS Docket Room at Patriots Plaza 3, 355 E. Street SW., Room 8-164, Washington, DC 20250-3700 between 8:00 a.m. and 4:30 p.m., Monday through Friday.</P>
        </ADD>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>
        <HD SOURCE="HD1">Public Meeting</HD>

        <P>On March 10, 2010, FSIS held a public meeting to discuss the Agency's ongoing efforts to improve product traceback related to<E T="03">E. coli</E>O157:H7.<SU>1</SU>
          <FTREF/>Noting that the July 2009 Key Findings Report of the President's Food Safety Working Group identified the ability to trace contaminants back to their source as a high priority for ensuring a safe food supply,<SU>2</SU>
          <FTREF/>FSIS officials described the Agency's current traceback policy and discussed changes the Agency was considering to improve its traceback efforts.</P>
        <FTNT>
          <P>
            <SU>1</SU>
            <E T="03">http://origin-www.fsis.usda.gov/PDF/Transcript_031010_Traceability.pdf.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">http://www.foodsafetyworkinggroup.gov/FSWG_Key_Findings.pdf.</E>
          </P>
        </FTNT>

        <P>Under FSIS's current traceback policy, FSIS does not begin conducting any investigations or follow up activities until positive results based on FSIS testing are identified or until outbreaks occur. Based on FSIS positive test results or other Federal or State Agency positive test results, FSIS conducts Food Safety Assessments (FSAs) at establishments that produce product (ground beef, beef manufacturing trimmings, or other raw ground beef components) that is positive for<E T="03">E. coli</E>O157:H7. FSAs are complete investigations concerning the establishment's entire HACCP system. FSIS also conducts FSAs at supplier establishments that are sole source suppliers for product that FSIS or another Federal or State Agency has found positive for O157:H7, or at establishments that FSIS has found provided source materials for product that FSIS or another Federal or State Agency has found positive more than once in the last 120 days. FSIS Enforcement, Investigations, and Analysis Officers (EIAOs) conduct these FSAs and are trained specifically for these assessments. FSIS also conducts investigations in response to outbreaks, working with CDC and State or local Agencies.</P>

        <P>The contemplated changes discussed at the March 10, 2010, public meeting focused on improving FSIS's ability to quickly trace all adulterated products that are implicated by an<E T="03">E. coli</E>O157:H7 positive test of raw ground beef or bench trim (defined as, beef manufacturing trimmings derived from cattle not slaughtered on site at the establishment). For example, Agency officials explained that FSIS intends to implement new investigations of production practices at establishments that produced product FSIS finds presumptive positive for<E T="03">E. coli</E>O157:H7. Similarly, based on presumptive positive results, Agency officials stated that FSIS intends to implement new investigations of production practices at the establishments' suppliers. FSIS officials explained that FSIS did not intend to wait for confirmation results before initiating these investigations because the Agency believes it is imperative to more quickly identify all affected product and all potential suppliers.</P>

        <P>Agency officials also discussed the importance of focusing on slaughter and dressing operations—where contamination is most likely to occur—in mitigating the risk of<E T="03">E. coli</E>O157:H7 contamination of raw ground beef products.</P>
        <P>Finally, Agency officials described the role played by identifying high event periods (HEPs) in determining whether a systemic breakdown of process control at a slaughter establishment may have led to cross-contamination between multiple production lots. Agency officials explained that this type of loss of process control and cross-contamination would create insanitary conditions that may affect the disposition of intact (primal and subprimal) cuts of beef, in addition to beef manufacturing trimmings. If loss of control leads to insanitary conditions, more product may be adulterated than just the product found positive for the pathogen. In this situation, it is very important that establishments identify all product that may be adulterated and hold that product back from commerce to avoid expensive recalls. FSIS notes that recalls can result in costs of $3-5 million.<SU>3</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>3</SU>As reported by Food and Drug Administration (FDA) “Preliminary Regulatory Impact Analysis and Initial Regulatory Flexibility Analysis of the Proposed Rules to Ensure the Safety of Juice and Juice Products” (63 FR 24258; May 1, 1998). The cost covers manufacturer, retailers and State, local, and Federal authorities.</P>
        </FTNT>
        <P>Agency officials also described draft compliance guidelines issued by FSIS on August 12, 2008, that included the Agency's then current thinking regarding HEPs.<SU>4</SU>

          <FTREF/>They noted that the Agency had received and considered comments related to that draft guidance document. The transcript to the public meeting and materials presented at the public meeting is available at the following site:<E T="03">http://www.fsis.usda.gov/Regulations_&amp;_Policies/2010_Notices_Index/index.asp.</E>
        </P>
        <FTNT>
          <P>
            <SU>4</SU>
            <E T="03">http://www.fsis.usda.gov/PDF/Draft_Guidelines_Sampling_Beef_Trimmings_Ecoli.pdf.</E>
          </P>
        </FTNT>

        <P>Public comments made during the meeting and others submitted later stated that FSIS needed to take additional actions related to traceback in instances involving sole source suppliers of<E T="03">E. coli</E>O157:H7 positive product. These commenters emphasized the need to identify these sole source suppliers in order to better protect the public. One comment specifically stated that FSIS should take action to better identify the source of contamination and to remove associated adulterated product from commerce.</P>

        <P>Other commenters stated that additional steps could also be taken to improve traceback methodology in cases where a positive sample is taken from a production lot of ground beef created from multiple sources. Specifically, some commenters suggested that when a production lot of ground beef that was produced from multiple source lots tests positive, FSIS should test any remaining unopened trim from the source production lots to identify which source lot is implicated by the positive ground beef sample.<PRTPAGE P="26727"/>
        </P>

        <P>Other commenters asked questions about the new traceback methodology and requested that FSIS continue to share information about the new methodology and clarify issues concerning the new methodology. Several commenters agreed that establishments should develop or use process control procedures based on HEP criteria that indicate higher than expected rates of positive<E T="03">E. coli</E>O157:H7 test results. Some commenters raised questions concerning whether N60 sampling procedures are capable of detecting contaminated product on a routine basis. Finally, some commenters recommended that FSIS collect information on suppliers at the time of sample collection, rather than after the sample is confirmed positive for<E T="03">E. coli</E>O157:H7 to expedite all necessary investigation and traceback activities.</P>
        <P>
          <E T="03">Improved Traceback Procedures:</E>On October 8, 2010, in response to comments received at the public meeting, FSIS issued instructions to inspection program personnel to record information on the source materials and on the suppliers at the time they sample ground beef or bench trim for<E T="03">E. coli</E>O157:H7 (FSIS Notice 58-10). With issuance of the October 8, 2010 notice, FSIS changed its procedures so that inspection program personnel no longer wait for a positive test result before they gather supplier information. FSIS agreed with comments that had been submitted in response to the public meeting that collecting supplier information at the time the sample is collected would better serve FSIS's goal to respond to FSIS presumptive positive results by identifying all affected product and all potential suppliers as quickly as possible to protect public health.</P>

        <P>FSIS intends to implement additional improved procedures consistent with the procedures it discussed at the public meeting. As is discussed above, inspection program personnel will continue to collect and document information on suppliers at the time of sample collection. Using the supplier information, EIAOs will then conduct traceback investigations at establishments that produced the<E T="03">E. coli</E>O157:H7 positive product and at suppliers that provided source materials for ground beef or bench trim that FSIS has found positive. These traceback investigations will begin as soon as possible, based on presumptive positive results and supplier information from the producing establishment. EIAOs will visit both the establishment that produced the positive product and the supplier slaughter establishment and gather relevant information about the production of the product, including use of anti-microbials and prevention of cross contamination, sanitary conditions, and relevant purchase specifications.</P>
        <P>As part of their traceback investigations, EIAOs will review establishment test results to determine whether the establishment has experienced a HEP. If the establishment has developed its own supportable HEP criteria, the EIAOs will determine whether it has experienced a HEP based on the establishment's HEP criteria. If it has not, EIAOs will determine whether the establishment has experienced a HEP based on the FSIS criteria discussed below. The occurrence, or lack of occurrence, of a HEP will be one factor that EIAOs will consider when investigating at the establishment that produced positive product or supplied product to an establishment that produced positive product.</P>
        <P>Based on all the information gathered, EIAOs will present findings to the District Manager on which to determine whether adulterated product has entered commerce. The EIAO will also make recommendations concerning whether regulatory and enforcement actions are warranted. The District Manager will then determine whether adulterated product entered commerce, and if it has, whether to contact the FSIS Recall Management Staff and whether enforcement actions are appropriate. Consistent with Agency procedures, the Recall Management Staff will lead any Agency requests that establishments recall product.</P>
        <P>As is discussed above, EIAOs do not do this type of investigation now until they conduct FSAs. FSAs are scheduled approximately 30 days after the confirmed positive results become available, so they are much later than the investigations FSIS intends to conduct. Also, during the FSAs at this time, EIAOs do not ask all the focused questions FSIS intends to instruct them to ask as part of this new procedure. Finally, EIAOs do not currently evaluate whether the establishment has experienced a HEP on a consistent basis.</P>
        <P>
          <E T="03">Recalls from sole source suppliers:</E>Also in response to comments to the public meeting concerning the need to eliminate contaminated source material from commerce, FSIS intends to implement a new recall policy to request that supplier establishments recall product if all of the following circumstances occur:</P>

        <P>(1) FSIS or other Federal or State agencies find raw ground beef positive for<E T="03">E. coli</E>O157:H7 at a grinding establishment;</P>
        <P>(2) FSIS determines that<E T="03">E. coli</E>O157:H7 cross-contamination was unlikely to have occurred at the grinding establishment where the sample was taken (based on FSIS's assessment of the grinding establishment's handling practices);</P>
        <P>(3) FSIS determines that the grinding establishment did not combine material from multiple source lots to create the lot of product that tested positive;</P>
        <P>(4) After conducting traceback to identify the slaughter and trim fabrication supplier that provided the sole source material, FSIS determines that the supplier or downstream users split the implicated lot before sending it to the establishment where the positive sample was taken; and</P>

        <P>(5) Some portion of the split lot sent to the grinder was sent into commerce for further processing into product that does not receive a full lethality to eliminate<E T="03">E. coli</E>O157:H7 in a federally inspected establishment.</P>
        <P>If all of these circumstances occur, FSIS intends to request a recall from the slaughter or trim supplier establishment. If cross contamination did not occur at the grinding establishment, the source materials would be considered adulterated because, based on evidence and available data, contamination occurred at the slaughter or trim establishment.</P>

        <P>In the two-year period between January 1, 2009, and December 31, 2010, 65 Agency samples of ground beef (collected as part of the routine and follow-up sampling programs) tested positive for<E T="03">E. coli</E>O157:H7. Of those 65 positive samples, 41 of them (63.1%) were taken from production lots created using source material from a sole supplier. Twelve of the 41 sole suppliers were self suppliers, meaning that slaughter, trim fabrication, and grinding were done at the same establishment. Out of the 41 sole suppliers, 29 were external supplier establishments. The remaining 24 of the 65 positive samples (36.9%) were taken from production lots created using source material from multiple suppliers. Therefore, there were 29 external sole suppliers that provided the source materials for positive ground product. If all the criteria for a recall were in place, FSIS would have requested 29 additional recalls. However, it is likely that some of these suppliers did not split lots, so all of the source materials from the production lot involved would have gone to the grinder that produced the positive product. If the suppliers did not split the lot, this policy would not result in any additional recalls. Any additional recalls under these circumstances are likely to better prevent the public from consuming adulterated product.<PRTPAGE P="26728"/>
        </P>
        <P>Based on the 2009-2010 data, a significant number of ground product lots that FSIS found positive were produced from source materials from sole source suppliers. However, in some circumstances, the grinding establishment may have combined material from multiple source lots to create the lot of product that tested positive. Under these circumstances, the new recall policy would not apply.</P>

        <P>FSIS agrees with commenters to the public meeting that removing from commerce source materials that may be contaminated with<E T="03">E. coli</E>O157:H7 is critically important. In situations where contamination most likely occurred at the slaughter establishment that produced the source materials, removing from commerce those source materials used to produce<E T="03">E. coli</E>O157:H7 positive product is scientifically sound.<E T="03">E. coli</E>O157:H7 is an enteric pathogen; therefore, contamination may occur during the slaughter process, from transfer of contamination from the hides, hooves, and gut of cattle. Contamination may occur through cross contamination at the grinder; however, if there is no evidence of cross contamination at the grinder, contamination most likely occurred at the slaughter or trim establishment. FSIS is not aware of any circumstance in which a split lot contributed to a reported illness. Regardless, FSIS believes that this new recall policy will better protect the public from consumption of<E T="03">E. coli</E>O157:H7 contaminated product because it will better ensure that source materials that are contaminated with<E T="03">E. coli</E>O157:H7 are removed from commerce. FSIS has requested recalls from sole suppliers that provided source materials for product found positive at grinders under specific, special circumstances, but not as a general rule. FSIS requests comment on this new recall policy before implementing it as a standard procedure and requests comment on the costs that would result from this recall policy.</P>
        <P>
          <E T="03">High event periods:</E>Most establishments use testing that includes an enrichment step followed by differential screening specific to STEC organisms, particularly<E T="03">E. coli</E>O157:H7 or their associated virulence markers (e.g.,<E T="03">eae</E>and<E T="03">stx</E>genes). Positive results during these screening tests require further testing to detect<E T="03">E. coli</E>O157:H7. If an establishment does not perform additional testing, it should treat lots that test positive in screen tests as positive. Similarly, FSIS considers those results positive for<E T="03">E. coli</E>O157:H7 if not confirmed negative. Therefore, the discussion below refers to shiga toxin-producing<E T="03">E. coli</E>(STEC) organisms or virulence markers, in addition to<E T="03">E. coli</E>O157:H7.</P>

        <P>HEPs are periods in which slaughter establishments experience a high rate of<E T="03">E. coli</E>O157:H7 (or STEC organisms or virulence markers) in trim samples from production lots containing the same-source materials. That is, the trim was produced from one or more carcasses slaughtered and dressed consecutively or intermittently within a defined period of time (e.g., shift).<E T="03">E. coli</E>O157:H7 contamination is generally point-source contamination that occurs sporadically as a consequence of handling during hide removal and dressing of the carcass. However, during HEPs, the contamination has become more widespread. HEPs may stem from a higher than expected level of contamination on hides, a failure of prevention mitigations, or cross contamination of product. A high rate of positives in trim is problematic because the trim is typically used across multiple production lots, is handled by employees, and is therefore likely to contaminate common conveyor belts and equipment. Also, such high rates of positives or HEPs may mean that a systemic breakdown of the establishment's production process may have occurred, and that insanitary conditions existed at the establishment during these periods. Such insanitary conditions may affect the safety of intact (primal and subprimal) cuts, trim, and other beef components used in the production of ground beef. In response to comments from the public meeting that supported the implementation of new traceback procedures to better identify contaminated source materials, FSIS intends to provide more specific instructions to EIAOs concerning HEPs that may occur at slaughter establishments that produced source materials for product that FSIS has found positive for<E T="03">E. coli</E>O157:H7. FSIS will issue the new instructions as a notice or directive to its personnel. The new procedures it intends to implement are discussed below. As is discussed below, FSIS is also providing updated guidance to establishments on how to identify HEPs. FSIS considered comments submitted on the guidance and believes that the guidance is now more useful to industry to help it identify HEPs, avoid recalls, and prevent adulterated product from entering commerce.</P>
        <P>To help develop the operational criteria for industry to use to identify HEPs and for EIAOs to consider when conducting traceback procedures, FSIS examined industry data collected by FSIS inspection personnel from the top 33 slaughter establishments, representing 80 percent of industry production volume (number of cattle slaughtered).</P>
        <P>The data from the 33 establishments show clustering of positives results. Of the 33 establishments, 32 responses were received, 19 had clear definitions of a HEP, 2 had definitions that were incomplete because they did not specify a frame of time (which we interpreted to be a day), 10 had unclear definitions of a HEP, and 1 did not have a definition. Of the 21 establishments that had clear definitions, 7 were using a 5 percent threshold definition;<SU>5</SU>
          <FTREF/>9 indicated a threshold of 1-3 positive results a day or shift; 2 used between 5-10%; and 3 had definitions greater than 10%.</P>
        <FTNT>
          <P>

            <SU>5</SU>Establishments generally do not wait for confirmation of positive results, which can take up to 8 days; rather establishments respond to presumptive positive results that have not been confirmed for<E T="03">E</E>.<E T="03">coli</E>O157:H7.</P>
        </FTNT>
        <P>Based on these results, FSIS selected a target of 5% for the HEP criteria. Because FSIS did not want to define HEP criteria that would be more rigorous than those of a large number of establishments, we did not select a lower target. FSIS set criteria to help identify exceptional events of poor processing. FSIS did not select a higher target (e.g., 10%) because such a target we believe could result in many cases where poor processing, as defined by most of the industry, would not be detected as HEP.</P>
        <P>FSIS intends to identify in the guidance and in instructions to EIAOs two types of HEP that may indicate out-of-control situations in the establishment's production process based on establishment results. As noted above, 10 of the establishments had unclear definitions of HEPs, and one had no definition. If establishments use FSIS's criteria, FSIS would find their HEP definitions supportable. Below are the two types of HEPs.</P>
        <EXTRACT>
          

          <P>1. A HEP that indicates a localized out-of-control event in which some specific occurrence or event causes a clustering of<E T="03">E. coli</E>O157:H7 (or STEC organisms or virulence markers) that indicate contamination in product. The event would not indicate, necessarily, a severe or global systemic break-down or inherent weakness of the process or food safety system. Generally, intact primal and subprimal cuts would not be affected if such cuts routinely undergo a pathogen reduction treatment.</P>
          <P>2. A HEP that indicates a systemic break-down or inherent weakness of the process or food safety system. Virtually all raw beef product would likely be affected.</P>
        </EXTRACT>
        

        <P>During a systemic break-down situation, establishments may identify<PRTPAGE P="26729"/>more product that needs to be assessed to determine whether it may be adulterated than in a localized HEP. A localized HEP may affect only the production of one lot, while a systemic break-down may affect more product. Also, a localized HEP may indicate an isolated problem (such as improper application of an anti-microbial in one lot); a systemic HEP may indicate a broader problem (such as systemic failure to prevent cross contamination among carcasses).</P>
        <P>FSIS is setting out criteria for identifying HEPs. These criteria will be especially useful for establishments that have rigorous testing programs. Beef slaughter and fabrication establishments that manufacture 50,000 pounds or more of trimmings daily are likely to conduct sufficient verification testing on same source materials to be able to determine whether a HEP occurred based on the criteria below. Lower volume establishments may choose to test frequently enough to use these criteria. If not, the guidance includes general information for lower volume establishments.</P>
        
        <EXTRACT>
          <P>1. For a local HEP: 3 or more<E T="03">E. coli</E>O157:H7 (or STEC organisms or virulence markers) positive results out of 10 consecutive samples from production lots containing same-source materials; and</P>
          <P>2. For a systemic HEP:</P>
          <P>A. 7 or more<E T="03">E. coli</E>O157:H7 (or STEC organisms or virulence markers) positive results out of 30 consecutive samples from production lots containing same-source materials.</P>

          <P>B. At establishments that test more than 60 samples per day, from production lots containing same-source materials, the number of<E T="03">E. coli</E>O157:H7 (or STEC organisms or virulence markers) positive samples below within the samples tested in the table:</P>
        </EXTRACT>
        <GPOTABLE CDEF="10C,10C" COLS="2" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Unacceptable number positives</CHED>
            <CHED H="1">Within samples tested</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">8</ENT>
            <ENT>61</ENT>
          </ROW>
          <ROW>
            <ENT I="01">9</ENT>
            <ENT>74</ENT>
          </ROW>
          <ROW>
            <ENT I="01">10</ENT>
            <ENT>86</ENT>
          </ROW>
          <ROW>
            <ENT I="01">11</ENT>
            <ENT>100</ENT>
          </ROW>
          <ROW>
            <ENT I="01">12</ENT>
            <ENT>113</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13</ENT>
            <ENT>127</ENT>
          </ROW>
          <ROW>
            <ENT I="01">14</ENT>
            <ENT>141</ENT>
          </ROW>
          <ROW>
            <ENT I="01">15</ENT>
            <ENT>155</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16</ENT>
            <ENT>169</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17</ENT>
            <ENT>184</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18</ENT>
            <ENT>198</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19</ENT>
            <ENT>213</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20</ENT>
            <ENT>228</ENT>
          </ROW>
        </GPOTABLE>
        <P>The above criteria are based on high degrees of confidence (establishing sufficient statistical evidence) that the process percentage exceeded 5% during some period. For the systemic HEP based on daily testing of at least 60 samples<SU>6</SU>
          <FTREF/>and the local HEP guidance, FSIS used close to 99 percent confidence for establishing sufficient statistical evidence.<SU>7</SU>
          <FTREF/>For the systematic short-term HEP (based on 30 samples), FSIS selected about 99.95% confidence for asserting sufficient statistical evidence. The reason for this high degree of confidence is that FSIS wanted to have a short-term HEP criterion to help establishments identify periods of serious processing problems.</P>
        <FTNT>
          <P>
            <SU>6</SU>FSIS selected a minimum of 60 samples for identifying daily HEP because the purpose of this was to determine inconsistencies over a large amount of product produced during the day. The other two criteria apply for less product or shorter periods. FSIS identified the day-specific criterion for large volume establishments that often test more than 100 lots a day.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>7</SU>For the local HEP involving 3 positive results from 10 samples, the confidence is 98.849644%, which FSIS considers to be close to 99%.</P>
        </FTNT>
        <P>Establishments may use the guidance that FSIS has provided as criteria for determining whether they have experienced a HEP. However, the establishment-specific process percent positive could be different than the FSIS criteria (assuming that the sampling plan and analyses are described as above). Consequently, a specified percent positive for a given establishment should be identified and justified if other than that stated by FSIS if past results indicate that a different percent positive was being achieved consistently, and product has low likelihood of being adulterated. Deviations from the previously obtained percent positive should be construed as presumptive evidence that the process is out of control and would warrant investigation to find and eliminate any potential causes for the positive results. As part of their supporting documentation for their hazard analysis (9 CFR 417.5 (a)), FSIS recommends that establishments document the criteria they use to identify HEPs.</P>

        <P>Consistent with information FSIS presented at the March 2010 public meeting discussed above, FSIS intends to instruct EIAOs to conduct an investigation at establishments that produced positive<E T="03">E. coli</E>O157:H7 product and at establishments that provided the source materials used to produce that product. These traceback investigations will begin as soon as possible, based on presumptive positive results and supplier information at the producing establishment. Through these new procedures, FSIS will investigate the reasons for positive results on a more timely and thorough basis than the Agency does currently. At slaughter establishments that produced positive product or source materials used in the production of positive product, EIAOS will consider whether the establishment has experienced a HEP.</P>

        <P>A HEP indicates that production lots of same source material that are presumed to be microbiologically independent (based on test results or other criteria) may no longer be microbiologically independent. As noted above, in such cases, these production lots may be considered to be potentially contaminated with<E T="03">E. coli</E>O157:H7, even if the establishment has negative test results. During their investigations, EIAOs will look at establishment test results and will determine whether the establishment has its own HEP criteria. FSIS intends to instruct EIAOs that when a HEP has occurred based on the establishment's criteria or FSIS criteria, they are to determine whether the establishment considered whether negative tested lots of trimmings are releasable, and whether primal and sub-primal product produced from the same source materials as the trimmings may be positive for<E T="03">E. coli</E>O157:H7, particularly if the establishment does not have controls in place to ensure that the  primal and sub-primal product is not used for non-intact purposes.</P>

        <P>If a HEP has occurred, FSIS intends to instruct the EIAO to evaluate whether the establishment verified that all controls in place in the slaughter process that are necessary to prevent<E T="03">E. coli</E>O157:H7 are working as intended. Such controls may include measures to reduce the pathogen load on incoming animals, measures to ensure that contamination of the carcass is prevented during slaughter or dressing procedures, effective decontamination or pathogen reduction treatments (also referred to as “antimicrobial treatments”), and measures to minimize carcass-to-carcass contact and cross contamination.</P>
        <P>Also, if a HEP has occurred, FSIS intends to instruct the EIAO to evaluate whether the establishment found the cause for the HEP and has taken corrective action to prevent future HEPs from recurring.</P>

        <P>Finally, if the establishment has experienced a HEP during a “high prevalence season” (from spring into early autumn), FSIS intends to instruct the EIAO to determine whether the establishment increased the frequency of monitoring and verification of both slaughter and dressing procedures and pathogen reduction treatments, and whether the establishment modified its sampling and verification testing programs during the high prevalence season to increase the likelihood of finding the pathogen.<PRTPAGE P="26730"/>
        </P>
        <P>As stated above, the EIAO will present to the District Manager the findings concerning HEPs and all other findings and recommendations, including any evidence indicating that adulterated product has likely entered commerce. Similarly, based on the HEP information, as well as other information collected, the EIAO will make recommendations concerning what regulatory or enforcement actions may be warranted. In addition, if the District Manager determines that adulterated product entered commerce, the Recall Management Staff will lead any Agency requests that establishments recall product. FSIS expects to complete the investigation and take all necessary enforcement actions within one month.</P>
        <P>We note that this Notice imposes no new requirements for establishments related to HEPs. The new EIAO instructions and investigation procedures described are only intended to improve and expedite FSIS traceback procedures.</P>
        <P>
          <E T="03">Possible New Procedures To Identify Suppliers:</E>In response to comments, FSIS intends to assess the merits and resource implications of conducting additional traceback activities. For example, FSIS intends to determine whether it can make better use of the results of establishment (versus FSIS) testing for<E T="03">E. coli</E>O157:H7 and other microorganisms and other establishment data that they may collect to evaluate their sanitary dressing procedures. FSIS requests comment on how the Agency could better evaluate this data and use it to inform establishments that problems may be developing or to advise establishments to take action to prevent the creation of insanitary conditions or the production of adulterated product in the future. Inspection program personnel currently review establishment test results on a weekly basis (FSIS Directive 5000.2). FSIS is considering issuing clarifying instructions to these personnel to look for increasing positive results that should be raised to the establishment's attention. FSIS also intends to conduct a study to test product from unopened containers or purge material (that is, remaining liquid, fat, and meat particles in containers or combo bins after trim contents have been removed) from suppliers' product for<E T="03">E. coli</E>O157:H7. The purpose of this study will be to identify the source of<E T="03">E. coli</E>O157:H7 positive raw ground beef when material from multiple suppliers was used to create the sampled ground beef that FSIS has found positive for<E T="03">E. coli</E>O157:H7.</P>
        <HD SOURCE="HD1">Availability of Guidance Material</HD>

        <P>In October 2008, FSIS issued draft guidance entitled, “Label Policy Guidance for N60 Testing Claims for Boneless Beef Manufacturing Trimmings (`Trim') Concerning<E T="03">E. coli</E>O157:H7,” and draft guidance entitled, “Compliance Guideline for Sampling Beef Trimmings for<E T="03">Escherichia coli</E>O157:H7” and requested comments on these documents. FSIS also held a public meeting to discuss the guidance and other topics concerning<E T="03">E. coli</E>O157:H7. FSIS carefully considered the comments received and has responded to comments below.</P>

        <P>FSIS has posted the revised guidance on its Significant Guidance Documents Web page<E T="03">http://www.fsis.usda.gov/Significant_Guidance/index.asp.</E>FSIS encourages those who are interested in using sampled and tested claims to avail themselves of this guidance document when preparing applications for sketch approval, and when using a sketch approved sampled and tested claim. Similarly, FSIS encourages establishments to begin using the trim sampling guidance. FSIS welcomes comments on this guidance document. The Agency will consider carefully all comments submitted and will revise the guidance document as warranted.</P>
        <HD SOURCE="HD1">Sampling and Testing Guidelines</HD>

        <P>This guidance, entitled “Compliance Guideline for Establishments Sampling Beef Trimmings for Shiga Toxin-Producing Escherichia coli (STEC) Organisms or Virulence Markers,” is meant to help slaughter establishments develop and implement sampling and testing programs for<E T="03">E. coli</E>O157:H7 (or STEC organisms or virulence markers) in beef manufacturing trimmings that are sampled using the N60 sampling method or similar methods. FSIS recommends that establishments identify HEP criteria so that they can determine whether they need to withhold product from commerce when a HEP has occurred, because a HEP may indicate more widespread adulteration of product, beyond the product found positive. If establishments identify and respond to HEPs, they will minimize the chance that they release adulterated product into commerce.</P>
        <P>Although this document also provides general information for non-slaughter establishments that produce or receive trimmings, the HEP information in the guidance only applies to slaughter establishments that manufacture trim. The HEP guidance will be most useful to slaughter and fabrication establishments that manufacture 50,000 pounds or more of trimmings daily because they are likely to conduct sufficient testing on same source trimmings to be able to determine whether a HEP has occurred. Smaller volume slaughter and fabrication establishments can also use the FSIS suggested criteria, particularly those that involve 10 and 30 samples. Non-slaughter establishments will not know if problems with slaughter and dressing procedures have contributed to a HEP because they do not have the necessary information from the establishment that slaughtered the cattle. FSIS recommends that a slaughter and fabrication establishment conduct sampling and testing of trim at a frequency sufficient to find evidence of contamination surviving the slaughter and dressing operation (optimally every production lot) to best ensure that adulterated product does not enter commerce. Verification testing results on trim are likely the best available information a slaughter establishment can use to determine the effectiveness of its slaughter and dressing operation.</P>
        <P>
          <E T="03">Comment:</E>Industry commenters disagreed with the “event day” or “hot day” discussion FSIS presented in the guidance to illustrate the number of positive results within a set number of samples that would indicate that a process is out of control. These commenters were concerned that the criteria would trigger regulatory criteria and recalls. A consumer group was concerned that the compliance guide suggested establishments would not have to investigate every positive but could, instead, just investigate positives during HEPs.</P>
        <P>
          <E T="03">Response:</E>Identifying a HEP is an adequate basis for determining whether a process is out of control. A high number of positives within a limited number of samples may indicate that a systemic problem may have occurred. To ensure that FSIS provides guidance for identifying HEPs that would be useful to establishments, FSIS has gathered information from inspectors at the 33 largest beef slaughter establishments and revised the guidance to reflect this information.</P>

        <P>The guidance clarifies that establishments are required to investigate all positive results based on 9 CFR 417.3. In addition, the guidance recommends that establishments take additional actions in response to HEPs. The guidance explains that if the establishment has experienced a HEP, it should carefully investigate to find all contributing causes. This type of investigation would be more involved than a follow-up investigation when an occasional positive result is found.<PRTPAGE P="26731"/>
        </P>
        <P>
          <E T="03">Comment:</E>Consumer organizations stated that establishments' testing cannot replace effective prevention strategies and process control. Industry commenters noted that microbiological testing is not designed to test the safety of beef products, but rather, such testing is to verify that controls are in place. One commenter submitted the Beef Industry and Food Safety Council (BIFSCo) “Best Practices for Using Microbiological Sampling,” a guidance document in conjunction with its comments.</P>
        <P>
          <E T="03">Response:</E>FSIS agrees with the comments that establishment testing is just one verification activity that establishments can use to verify that their food safety system adequately addresses<E T="03">E. coli</E>O157:H7. Nonetheless, it is important to underscore that microbiological testing is likely the best method for system verification as it relates to microbial hazards. FSIS agrees that the BIFSCo guidance is useful and has included a link to it in the compliance guidelines so that users can quickly access that guidance.</P>
        <P>
          <E T="03">Comment:</E>A consumer group commented that FSIS's N60 program for sampling beef manufacturing trimmings is ineffective because it is not based on an accurately measured prevalence rate. The commenter also stated that N60 sampling does not allow the Agency's testing to detect<E T="03">E. coli</E>O157:H7 and, therefore, should not be used to verify product safety or that a process is in control.</P>
        <P>
          <E T="03">Response:</E>FSIS agrees that information on national prevalence is important for properly designing a sampling program.<SU>8</SU>
          <FTREF/>However, a national prevalence estimate is not sufficient information to determine how to collect a sample from a lot, owing to the distinction between determining how many lots to test and how to collect a sample from each lot. In other words, prevalence data could inform how many lots to test nationwide, but not how to collect a sample from each lot. A sampling program, such as FSIS's trim sampling program, is a different concept than a sample collection method, such as N60.</P>
        <FTNT>
          <P>

            <SU>8</SU>FSIS recently published the national prevalence estimate of pathogen contamination of trim based on the 2005-07 beef trim baseline study:<E T="03">http://www.fsis.usda.gov/PDF/Baseline_Data_Domestic_Beef_Trimmings_Rev.pdf.</E>
          </P>
        </FTNT>
        <P>FSIS's N60 sampling of beef trim and testing of trim for<E T="03">E. coli</E>O157:H7 is only one of a number of verification activities that FSIS conducts regarding establishment process controls for<E T="03">E. coli</E>O157:H7. FSIS sampling of beef trim works along with inspection and other verification activities, including FSIS sampling of ground beef and other ground beef components and the review of establishment testing results, to detect and reduce<E T="03">E. coli</E>O157:H7 in beef products. FSIS's mission is not to screen the food supply through testing but to verify that safe and wholesome food is produced through inspection activities.</P>
        <P>
          <E T="03">Comment:</E>Another industry commenter disagreed that aerobic plate counts (APCs) are an indicator of process control for reducing<E T="03">E. coli</E>O157:H7. The commenter stated that there is no significant correlation between<E T="03">E. coli</E>O157:H7 and APCs.</P>
        <P>
          <E T="03">Response:</E>FSIS agrees that there is not a significant correlation between<E T="03">E. coli</E>O157:H7 and APCs. However, as is stated in the guidance, FSIS continues to believe that it is useful for beef establishments to conduct verification testing for associated organisms that include<E T="03">E. coli</E>O157:H7 (e.g., a screen methodology for pathogenic<E T="03">E. coli</E>) and to maintain records of results as a quality control activity. Measurements of ubiquitous organisms such as Enterobacteriacea, APC, or generic<E T="03">E. coli</E>can be used to evaluate the effectiveness of process controls in limiting or eliminating microbial contamination. Frequent measurements of APC counts may represent a short-term trend, which would be useful for quality control, both before and after the sanitary dressing processes. However, such measurements, while helpful for ensuring microbial process control, cannot be used as a substitute for determining the actual presence or absence of<E T="03">E. coli</E>O157:H7 in the final product.</P>
        <P>
          <E T="03">Comment:</E>Some comments supported changes to traceback activities discussed above. For example, one consumer group supported FSIS capturing information for all positive results, including results for industry sampling programs.</P>
        <P>
          <E T="03">Response:</E>See discussion above under “Improved Traceback Procedures.”</P>
        <P>
          <E T="03">Sampled and Tested Claims Guidance:</E>This document provides guidance on the use of labels bearing an FSIS sketch approved<E T="03">E. coli</E>O157:H7 sampled and tested claim on beef trim. As is explained in the guidance, such special labeling claims are voluntary. An establishment may use such claims when it demonstrates that they are truthful and not misleading (9 CFR 317.8(a)). FSIS must approve such claims before the establishment may use them on labels (9 CFR 317.4(a)). This guidance document addresses label claims that are not intended to be displayed to consumers. FSIS may approve<E T="03">E. coli</E>O157:H7 sampled and tested claims on trim that goes to retail stores, for example to a retailer who purchases the trim for grinding. However, FSIS will not approve such a label claim for display to consumers because it may be misleading to consumers by suggesting that the end product is free of the pathogen or may not need to be cooked thoroughly.</P>

        <P>A labeling claim asserting that beef trim has been sampled, tested, and found negative for<E T="03">E. coli</E>O157:H7 will provide receiving establishments with information regarding the sampling and testing of beef trim for that pathogen conducted by supplier establishments.</P>
        <P>Sampling and testing for<E T="03">E. coli</E>O157:H7 is intended to provide evidence regarding the effectiveness of HACCP measures in addressing the pathogen. Therefore, in order for a sampled and tested claim to be truthful and not misleading, the establishment asserting the claim must have incorporated into its HACCP system measures designed to control for<E T="03">E. coli</E>O157:H7, and it must use sampling and testing methodologies that are designed to verify the effectiveness of those measures.</P>
        <P>The final guidance document provides assistance to establishments on the use of labels bearing an FSIS sketch approved sampled and tested claim. It provides several examples of labeling claim language that may be appropriate under different circumstances. The final guidance also suggests the kind of documentation that establishments seeking sketch approval may submit to demonstrate that a sampled and tested claim would be truthful and not misleading.</P>
        <P>
          <E T="03">Comment:</E>Several members of industry questioned the connection between documentation of HACCP measures related to<E T="03">E. coli</E>O157:H7 and the truthfulness of a sampled and tested claim. These comments argued that it is not necessary to provide such extensive documentation in order to demonstrate that a sampled and tested claim is truthful and not misleading. They also stated that including extensive documentation as part of an application for sketch approval would be burdensome.</P>
        <P>
          <E T="03">Response:</E>A labeling claim that beef trim has been sampled, tested, and found to be negative for<E T="03">E. coli</E>O157:H7 is not a representation that the labeled beef trim is free of<E T="03">E. coli</E>O157:H7; rather, it is a representation that sampling and testing of the production lot from which the beef trim was derived has demonstrated that the production lot was produced under a HACCP system with measures in place that effectively control for the pathogen.<PRTPAGE P="26732"/>Accordingly, a sampled and tested claim is only truthful and not misleading if indeed such measures are in place, and if the sampling and testing program is designed to verify the effectiveness of those measures.</P>
        <P>To assist interested establishments to obtain sketch approval of sampled and tested claims, the final guidance retains a description of the HACCP system-related documentation that FSIS believes would demonstrate that a sampled and tested claim is truthful and not misleading. FSIS made some revisions to the guidance for the sake of clarity.</P>
        <P>
          <E T="03">Comment:</E>Several industry representatives argued that the information to be included on a label bearing a sampled and tested claim should be simpler than what was described in the draft guidance. Some specific examples of information the commenters argued need not be included are: (1) Lot size information; (2) lot identification information; and (3) information indicating whether a production lot which was formed by combining beef trim from two or more source production lots was sampled after the source lots were combined.</P>
        <P>
          <E T="03">Response:</E>In response to the three specific concerns raised above: (1) Lot size information has been removed from the final version of the labeling guidance. This information was initially included as a suggested means of indicating to receiving establishments whether the labeled beef trim they receive consists of all or only a portion of a sampled production lot. In light of industry comments reflecting the practical difficulty of regularly changing labeling text to reflect the varying sizes of production lots, this suggestion has been replaced with guidance recommending a simple statement informing receiving establishments whether the labeled beef trim consists of an entire production lot or a portion of a split lot. (2) Including lot identification information on labels containing sampled and tested claims is important to ensure that such claims are truthful and not misleading because this information allows the labeled beef trim to be traced to a specific production lot. Therefore, the final version of the policy guidance document retains this suggested labeling information. (3) FSIS believes that it is important for a sampled and tested claim to include a statement specifying whether (a) the final formulation of labeled beef trim was sampled and tested, or (b) the source lots were sampled and tested before being combined. This information is relevant to whether a claim is truthful and not misleading because it identifies which production lot or lots have been produced using HACCP measures that effectively control for<E T="03">E. coli</E>O157:H7. FSIS agrees with several comments that the Agency needs to clarify this portion of the draft guidance. Therefore, FSIS has removed the “twice tested” discussion and replaced it with a suggestion that sampled and tested claims asserted on beef trim product formulated by combining two or more source lots state whether sampling and testing was conducted on the final formulation or on the source lots.</P>
        <P>
          <E T="03">Comment:</E>Many comments argued that the guidance should better define what constitutes N60 sampling methodology, and what constitutes an FSIS-equivalent testing method.</P>
        <P>
          <E T="03">Response:</E>The draft guidance referred specifically to the use of N60 sampling in connection with use of a sampled and tested claim. The final guidance does not specify that N60 sampling must be done in order to use a sampled and tested claim. Instead, the final guidance emphasizes that, in order for the claim to be truthful and not misleading, the sampling and testing program must be designed to verify the effectiveness of an establishment's HACCP measures that control for<E T="03">E. coli</E>O157:H7. FSIS believes that the sampling and testing methodologies it uses, including N60 sampling, achieve this goal. Therefore, the final policy guidance refers to documents that provide detailed descriptions of FSIS sampling and testing methodologies. However, if an establishment uses different sampling or testing methodologies that the establishment believes provide reliable verification of the effectiveness of HACCP measures designed to control for<E T="03">E. coli</E>O157:H7, and therefore that use of those methodologies will ensure that a sampled and tested claim is truthful and not misleading, then the establishment may include in its application for sketch approval documentation describing why its methodologies are equivalent to FSIS methodologies. To assist establishments wishing to demonstrate the equivalence of their sampling or testing methodologies, the final policy guidance refers to a separate guidance document that provides assistance to industry in conducting validation studies for pathogen detection methods:<E T="03">http://www.fsis.usda.gov/PDF/Validation_Studies_Pathogen_Detection_Methods.pdf.</E>
        </P>
        <HD SOURCE="HD1">USDA Nondiscrimination Statement</HD>
        <P>USDA prohibits discrimination in all its programs and activities on the basis of race, color, national origin, gender, religion, age, disability, political beliefs, sexual orientation, and marital or family status. (Not all prohibited bases apply to all programs.) Persons with disabilities who require alternative means for communication of program information (Braille, large print, or audiotape.) should contact USDA's Target Center at 202-720-2600 (voice and TTY).</P>
        <P>To file a written complaint of discrimination, write USDA, Office of the Assistant Secretary for Civil Rights, 1400 Independence Avenue SW., Washington, DC 20250-9410 or call 202-720-5964 (voice and TTY). USDA is an equal opportunity provider and employer.</P>
        <HD SOURCE="HD1">Additional Public Notification</HD>

        <P>FSIS will announce this notice online through the FSIS Web page located at<E T="03">http://www.fsis.usda.gov/regulations_&amp;_policies/Federal_Register_Notices/index.asp.</E>
        </P>
        <P>FSIS will also make copies of this<E T="04">Federal Register</E>publication available through the FSIS Constituent Update, which is used to provide information regarding FSIS policies, procedures, regulations,<E T="04">Federal Register</E>notices, FSIS public meetings, and other types of information that could affect or would be of interest to constituents and stakeholders. The Update is communicated via Listserv, a free electronic mail subscription service for industry, trade groups, consumer interest groups, health professionals, and other individuals who have asked to be included. The Update is also available on the FSIS Web page. In addition, FSIS offers an electronic mail subscription service which provides automatic and customized access to selected food safety news and information. This service is available at<E T="03">http://www.fsis.usda.gov/News_&amp;_Events/Email_Subscription/.</E>Options range from recalls to export information to regulations, directives, and notices. Customers can add or delete subscriptions themselves, and have the option to passwordprotect their accounts.</P>
        <SIG>
          <DATED>Done at Washington, DC, on April 24, 2012.</DATED>
          <NAME>Alfred V. Almanza,</NAME>
          <TITLE>Administrator.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10904 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-DM-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="26733"/>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Forest Service</SUBAGY>
        <SUBJECT>Uinta-Wasatch-Cache National Forest; Evanston-Mountain View Ranger District; Utah; Smiths Fork Vegetation Restoration Project</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Forest Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of intent to prepare an environmental impact statement.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Evanston-Mountain View Ranger District of the Uinta-Wasatch-Cache National Forest proposes to treat approximately 4,300 acres of a variety of vegetation types within the 58,000-acre Smiths Fork project analysis area, located in Uinta County, Wyoming, and Summit County, Utah, approximately 25 miles southwest of Mountain View, Wyoming. Proposed treatment acivities include salvage clearcuts; sanitation salvage; and thin, pile, and burn. This proposal is being developed in direct response to the continuing mountain pine beetle epidemic in the area and its potential long-term impacts on the Smiths Fork area. The project is being undertaken under the auspices of the Healthy Forests Restoration Act (“HFRA”).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments concerning the scope of the analysis must be received by May 31, 2012. The draft environmental impact statement is expected in August 2012 and the final environmental impact statement is expected November 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Send written comments to: Smiths Fork Vegetation Restoration Project, Attn: Rick Schuler, P.O. Box 1880, Evanston, WY 82931. Comments can also be hand delivered Monday through Friday 8 a.m. to 4:30 p.m. at the following physical address: 1565 Highway 150, Suite A, Evanston, Wyoming. In addition, comments can be submitted electronically to:<E T="03">comments-intermtn-wasatch-cache-evanston-mtnview@fs.fed.us</E>or submitted via facsimile to 307-783-8639.</P>
          <P>Reviewers should provide comments at such times and in such a way that they are useful to the agency's preparation of the EIS. Comments should be provided prior to the close of the comment period and should clearly articulate the reviewer's concerns and contentions. Submission of timely and specific comments can affect a reviewer's ability to participate in the objection process or judicial review.</P>
          <P>Comments received in response to this solicitation, including names and addresses of those who comment, will become part of the public record for this proposed action. Comments submitted anonymously will be accepted and considered; however, anonymous comments will not provide the respondent with standing to participate in the objection process associated with this project under the HFRA or judicial review.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Pete Gomben, Environmental Coordinator, at 801-236-3407.</P>
          <P>Individuals who use telecommunication devices for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339 between 8 a.m. and 8 p.m., Eastern Time, Monday through Friday.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Purpose and Need for Action</HD>
        <P>The HFRA recognizes healthy forests or forest health as an integral part of forest management. The proposed action responds directly to forest health objectives as described in the HFRA. The purpose of this project is to reduce the effects from current mountain pine beetle infestation in forested stands dominated by lodgepole pine trees and to reduce the susceptibility of vegetation to high-intensity wildfire and further mountain pine beetle attacks. The project is needed to: (1) Salvage forest products from, and manage stand densities on, forested lands classified as suitable for timber production to keep them positively contributing to the national forest's allowable sale quantity; (2) Reduce the effects of tree mortality associated with the mountain pine beetle epidemic to restore healthy ecological conditions and scenic quality; (3) Accelerate regeneration of forested stands killed by the mountain pine beetle; and (4) Manage hazardous fuel loading associated with the mountain pine beetle epidemic and salvage operations to minimize the potential for large, high intensity/high severity wildfires.</P>
        <P>This action responds to the goals and objectives outlined in the Wasatch-Cache National Forest Land and Resource Management Plan (“Forest Plan”), and helps move the project area towards desired conditions described in that plan.</P>
        <HD SOURCE="HD1">Proposed Action</HD>
        <P>The proposed project includes treatment of approximately 4,300 acres of aspen and lodgepole communities using timber harvest, prescribed fire, and mechanical fuels treatments. Sanitation salvage would be used on approximately 1,730 acres, clearcuts would be used on approximately 1,241 acres, sanitation salvage with pile and burn would be used on approximately 76 acres, clearcut with pile and burn would be used on approximately 40 acres, roadside salvage would occur on approximately 695 acres, and approximately 514 acres would be undergo a thin, pile, and burn prescription.</P>
        <P>Proposed treatments are intended to reduce both the amount and continuity of woody fuels, to remove hazard trees, to harvest beetle-killed or infested trees, and to create a mix of tree ages and species.</P>
        <P>The proposed action would retain habitat for sensitive and other species, such as northern goshawks, where needed. The proposed action is also expected to make improvements to visual quality. Treatments in the vicinity of private land would be intended to reduce the threat of wildfire to human life and property.</P>
        <P>Access to treatment units, as currently mapped, is anticipated to involve approximately 3.1 miles of new specified road construction, approximately 10.7 miles of temporary road construction, approximately 6.7 miles of additional temporary road use on the existing road prism, and approximately 2.6 miles of road reconstruction. Approximately 3.8 miles of easements through private land would be needed for access to units 4, 20, and 79.</P>
        <HD SOURCE="HD1">Possible Alternatives</HD>
        <P>In addition to the proposed action, a no action alternative will be considered. This alternative would continue current management without the actions of this proposal. Because this project is being analyzed via the HFRA, one additional alternative that addresses the purpose and need for the project may be developed in response to issues generated during the scoping process.</P>
        <HD SOURCE="HD1">Responsible Official</HD>
        <P>Uinta-Wasatch-Cache National Forest forest supervisor.</P>
        <HD SOURCE="HD1">Nature of Decision To Be Made</HD>
        <P>The decision to be made is whether or not to implement vegetation restoration treatments in the Smiths Fork project area, and if so, to what degree and where.</P>
        <HD SOURCE="HD1">Preliminary Issues</HD>
        <P>Preliminary issues are the effects of treatments on wildlife habitat, and the effects of insect and disease outbreaks on current forest health.</P>
        <HD SOURCE="HD1">Scoping Process</HD>

        <P>This notice of intent initiates the scoping process, which guides the development of the environmental<PRTPAGE P="26734"/>impact statement. This project is not subject to the notice, comment, and appeal process found at 36 CFR part 215. Rather, it is subject to the predecisional administrative review process found at 36 CFR part 218. This process provides the opportunity to resolve issues raised in an objection and identify potential solutions. Only persons who submit specific written comments on the proposed action during the 30-day comment period will be eligible to file an objection. This comment period represents the only opportunity for the public to comment on this proposal prior to the objection process. The opportunity to comment will end 30 days after a legal notice announcing the request for scoping comments is published in the Salt Lake Tribune, which is the newspaper of record.</P>
        <SIG>
          <DATED>Dated: April 26, 2012.</DATED>
          <NAME>Cheryl Probert,</NAME>
          <TITLE>Acting Forest Supervisor.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10728 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-11-M</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Forest Service</SUBAGY>
        <SUBJECT>Forestry Research Advisory Council</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Forest Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Forestry Research Advisory Council will meet in Washington, DC, on June 6-7, 2012. The purpose of the meeting is to discuss emerging issues in forestry research.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The meeting will be held June 6-7, 2012 from 8:30 a.m. to 5:00 p.m., on both days.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The meeting will be held at Franklin Court Building, 1099 14th Street NW., Suite 5500W, Washington, DC. Individuals who wish to speak at the meeting or to propose agenda items must send their names and proposals by May 31, 2012 to Daina Apple, Designated Federal Officer, Forestry Research Advisory Council, USDA Forest Service, Research and Development, 1400 Independence Ave. SW., Washington, DC 20250-1120, or fax their names and proposed agenda items to (202) 205-1530.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Daina Apple, Forest Service, Office of the Deputy Chief for Research and Development, (202) 205-1665.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The meeting is open to the public. Council discussion is limited to Forest Service, National Institute of Food and Agriculture staff and Council members. However, persons who wish to bring forestry research matters to the attention of the Council may file written statements with the Council staff before or after the meeting.</P>
        <SIG>
          <DATED>Dated: April 30, 2012.</DATED>
          <NAME>Jimmy L. Reaves,</NAME>
          <TITLE>Deputy Chief, Research and Development.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10873 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-11-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>National Institute of Food and Agriculture</SUBAGY>
        <SUBJECT>Notice of Intent To Extend a Currently Approved Information Collection</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Institute of Food and Agriculture, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice and request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In accordance with Office of Management and Budget (OMB) regulations (5 CFR 1320) that implement the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35), this notice announces the National Institute of Food and Agriculture's (NIFA) intention to request approval to extend the currently approved information collection for the Expanded Food and Nutrition Education Program (EFNEP). There are no planned revisions.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments on this notice must be received by July 6, 2012, to be assured of consideration. Comments received after that date will be considered to the extent practicable.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Written comments concerning this notice may be submitted by any of the following methods: Email:<E T="03">gmendez@nifa.usda.gov;</E>Fax: 202-720-0857; Mail: Office of Information Technology (OIT), NIFA, USDA, STOP 2216, 1400 Independence Avenue SW., Washington, DC 20250-2216</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Gidel Mendez, eGovernment Program Leader; Email:<E T="03">gmendez@nifa.usda.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <P>
          <E T="03">Title:</E>Expanded Food and Nutrition Education Program.</P>
        <P>
          <E T="03">OMB Number:</E>0524-0044.</P>
        <P>
          <E T="03">Expiration Date of Current Approval:</E>07/31/2012.</P>
        <P>
          <E T="03">Type of Request:</E>Intent to seek approval to extend the currently approved information collection for three years. There are no planned revisions.</P>
        <P>
          <E T="03">Abstract:</E>The USDA's NIFA Expanded Food and Nutrition Education Program (EFNEP) is a unique program that began in 1969 and is designed to reach limited resource audiences, especially youth and families with young children. Extension professionals train and supervise paraprofessionals and volunteers who teach food and nutrition information and skills to limited resources families and youth. EFNEP operates through the 1862 and 1890 Land Grant Universities in all 50 states, the District of Columbia, and in American Samoa, Guam, Micronesia, Northern Marianas, Puerto Rico, and the Virgin Islands.</P>
        <P>The objectives of EFNEP are to assist limited resource families and youth in acquiring the knowledge, skills, attitudes, and changed behaviors necessary for nutritionally sound diets, and to contribute to their personal development and the improvement of the total family diet and nutritional well-being.</P>
        <P>NIFA sponsors an integrated data collection process that is used at the county, state, and federal level. The current data collection system, the Nutrition Education Evaluation and Reporting System (NEERS), captures EFNEP impacts. Its purpose is to gauge if the federal assistance provided has had an impact on the target audience. It also enables EFNEP staff to make programmatic improvements in delivering nutrition education. Further, the data collected provides information for program management decisions and diagnostic assessments of participant needs. Specifications for this system were developed by a committee of representatives from across the United States and are in compliance with Federal standards for maintaining, collecting, and presenting data on race and ethnicity and protecting personally identifiable information.</P>
        <P>NEERS stores information on: (1) Adult program participants, their family structure, and dietary practices; (2) youth group participants; and (3) staff. NEERS consists of separate software sub-systems for the County and the State levels (State also refers to U.S. Territories). Data is exported electronically to the State-level system. University staff generates State-level reports for State-level stakeholders and to guide program management decisions. They also export State-level data electronically to the Federal office for State and National assessments of the program's impact. The State compiled data is aggregated using statistical software and then is used to create National reports which are made available to the public.</P>

        <P>There are no revisions to the currently approved collection.<PRTPAGE P="26735"/>
        </P>
        <P>The evaluation processes of EFNEP remain consistent with the requirements of Congressional legislation and OMB. The Government Performance and Results Act (GPRA) of 1993 (Pub. L. 103-62), the Federal Activities Inventory Reform Act (FAIR) (Pub. L. 105-207), and the Agricultural, Research, Extension and Education Reform Act (AREERA) of 1998 (Pub. L. 105-185), together with OMB requirements, support the reporting requirements requested in this information collection. One of the five Presidential Management Agenda initiatives, Budget and Performance Integration, builds on GPRA and earlier efforts to identify program goals and performance measures, and link them to the budget process. The FAIR act requires the development and implementation of a system to monitor and evaluate agricultural research and extension activities in order to measure the impact and effectiveness of research, extension, and education programs. AREERA requires a performance evaluation to be conducted to determine whether federally funded agricultural research, extension, and education programs result in public goods that have national or multistate significance.</P>
        <P>
          <E T="03">Estimate of Burden:</E>The number of respondents has increased from 74 to 75 institutions (e.g., state responses), thus constituting a total annual estimated burden of 93,225 hours for this data collection process—for participant education and data entry, aggregation, and reporting. Burden estimates are reflective of the previous version of the data collection system. The burden for respondents was estimated through feedback from a survey sent to nine institute-level EFNEP Coordinators. Six surveys were returned. Burden takes into account only the information collected in aggregate from the institutions and the record keeping activities that take place in order to provide the aggregated data; it does not include burden related to data entry at the local level. Local data is used by the county and institute levels to provide feedback to participants and to guide county and institute level program management, impact and accountability decisions and reporting.</P>
        <P>
          <E T="03">Comments:</E>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 will have practical utility; (b) the accuracy of the Agency's estimate of the burden of the proposed collection of information; (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 through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>
        <P>
          <E T="03">Obtaining a Copy of the Information Collection:</E>A copy of the information collection and related instructions may be obtained free of charge by contacting Gidel Mendez as directed above.</P>
        <SIG>
          <DATED>Done in Washington, DC, April 11, 2012.</DATED>
          <NAME>Catherine E. Woteki,</NAME>
          <TITLE>Under Secretary, Research, Education, and Economics.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10934 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Rural Utilities Service</SUBAGY>
        <SUBJECT>Information Collection Activity; Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Rural Utilities Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice and request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35, as amended), the United States Department of Agriculture (USDA) Rural Development administers rural utilities programs through the Rural Utilities Service (RUS). The USDA Rural Development invites comments on the following information collections for which the Agency intends to request approval from the Office of Management and Budget (OMB).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments on this notice must be received by July 6, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Michele Brooks, Director, Program Development and Regulatory Analysis, USDA Rural Development, 1400 Independence Ave. SW., STOP 1522, Room 5162, South Building, Washington, DC 20250-1522. Telephone: (202) 690-1078. FAX: (202) 720-8435.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Office of Management and Budget's (OMB) regulation (5 CFR part 1320) implementing provisions of the Paperwork Reduction Act of 1995 (Pub. L. 104-13) requires 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 information collections that RUS is submitting to OMB for extension.</P>
        <P>
          <E T="03">Comments are invited on:</E>(a) Whether this collection of information is necessary for the proper performance of the functions of the agency, including whether the information will 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 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 respondents, including through the use of appropriate automated, electronic, mechanical or other technological collection techniques or other forms of information technology. Comments may be sent to: Michele Brooks, Director, Program Development and Regulatory Analysis, USDA Rural Development, Stop 1522, 1400 Independence Ave. SW., Washington, DC 20250-1522. FAX: (202) 720-8435.</P>
        <P>
          <E T="03">Title:</E>Operating Reports for Telecommunications and Broadband Borrowers.</P>
        <P>
          <E T="03">OMB Control Number:</E>0572-0031.</P>
        <P>
          <E T="03">Type of Request:</E>Revision of an existing information collection package.</P>
        <P>
          <E T="03">Abstract:</E>Rural Utilities Service (RUS), an agency delivering the U.S. Department of Agriculture (USDA) Rural Development Utilities Programs, is a credit agency. RUS makes mortgage loans and loan guarantees to finance electric, broadband, telecommunications, and water and waste facilities in rural areas. In addition to providing loans and loan guarantees, one of the Agency's main objectives is to safeguard loan security until the loan is repaid.</P>

        <P>This collection of information covers the Telecommunications Operating Report, the Broadband Operating Report, and RUS Form 674, “Certificate of Authority to Submit or Grant Access to Data.” The data collected via the Telecommunications Operating Report is collected through the USDA Data Collection System. The data collected via the Broadband Operating Report is collected through the USDA Broadband Collection and Analysis System. The data collected via the Telecommunication and Broadband Operating reports is required by the loan contract and provides Rural Development with vital financial information necessary to ensure the maintenance of the security for the Government's loans, and statistical data to enable the Agency to ensure the provision of quality telecommunications and broadband services as mandated by the Rural Electrification Act (RE Act) of 1936. The data collected via the operating reports provides financial information to ensure loan security<PRTPAGE P="26736"/>consistent with due diligence. These functions are essential to protect loan security and to achieve objectives of the RE Act.</P>
        <P>The data collected via RUS Form 674 provides information to the Agency to allow Rural Development Electric, Telecommunications, and Broadband program Borrowers to file electronic Operating Reports with the Agency using the USDA Data Collection System. RUS Form 674, accompanied by a Board Resolution, identifies the name and USDA eAuthentication ID for a certifier and security administrator who will have access to the USDA Data Collection System for purposes of filing electronic Operating Reports. The information collected on the RUS Form 674 is submitted in hard copy by Borrowers only when revisions are required or, in the case of a first time Borrower, when initially submitting the data.</P>
        <P>
          <E T="03">Estimate of Burden:</E>Public reporting for this collection of information is estimated to average 3.45 hours per response.</P>
        <P>
          <E T="03">Respondents:</E>Businesses or other for-profit and not-for-profit Institutions.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>676.</P>
        <P>
          <E T="03">Estimated Number of Responses per Respondent:</E>1.36.</P>
        <P>
          <E T="03">Estimated Total Annual Burden on Respondents:</E>2,806.</P>
        <P>
          <E T="03">Title:</E>Distance Learning and Telemedicine Loan and Grant Program.</P>
        <P>
          <E T="03">OMB Control Number:</E>0572-0096.</P>
        <P>
          <E T="03">Type of Request:</E>Revision of a currently approved information collection package.</P>
        <P>
          <E T="03">Abstract:</E>The Rural Utilities Service's (RUS) Distance Learning and Telemedicine (DLT) Loan and Grant program provides loans and grants for advanced telecommunications services to improve rural areas' access to educational and medical services. The various forms and narrative statements required are collected from the applicants (rural community facilities, such as schools, libraries, hospitals, and medical facilities, for example). The purpose of collecting the information is to determine such factors as eligibility of the applicant; the specific nature of the proposed project; the purposes for which loan and grant funds will be used; project financial and technical feasibility; and, compliance with applicable laws and regulations. In addition, for grants funded pursuant to the competitive evaluation process, information collected facilitates RUS' selection of those applications most consistent with DLT goals and objectives in accordance with the authorizing legislation and implementing regulation.</P>
        <P>
          <E T="03">Estimate of Burden:</E>Public reporting burden for this collection of information is estimated to average 2.45 hours per response.</P>
        <P>
          <E T="03">Respondents:</E>Business or other forprofit; not-for-profit institutions; and State, Local or Tribal Government.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>210.</P>
        <P>
          <E T="03">Estimated Number of Responses per Respondent:</E>23.33.</P>
        <P>
          <E T="03">Estimated Total Annual Burden on Respondents:</E>12,788 hours.</P>
        <SIG>
          <DATED>Dated: April 26, 2012.</DATED>
          <NAME>Jonathan Adelstein,</NAME>
          <TITLE>Administrator, Rural Utilities Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10872 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
        <P>The Department of Commerce will submit to the Office of Management and Budget (OMB) for clearance the following proposal for collection of information under the provisions of the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <P>
          <E T="03">Agency:</E>National Oceanic and Atmospheric Administration (NOAA).</P>
        <P>
          <E T="03">Title:</E>Permitting, Vessel Identification, and Reporting Requirements for Deepwater Shrimp Fisheries in the Western Pacific Region.</P>
        <P>
          <E T="03">OMB Control Number:</E>0648-0586.</P>
        <P>
          <E T="03">Form Number(s):</E>NA.</P>
        <P>
          <E T="03">Type of Request:</E>Regular submission (extension of a current information collection).</P>
        <P>
          <E T="03">Number of Respondents:</E>10.</P>
        <P>
          <E T="03">Average Hours per Response:</E>Permit applications/renewals, 30 minutes; logbooks, 10 minutes per trip; vessel identification, 45 minutes.</P>
        <P>
          <E T="03">Burden Hours:</E>180.</P>
        <P>
          <E T="03">Needs and Uses:</E>This request is for extension of a currently approved information collection.</P>

        <P>Under the Code of Federal Regulations in Title 50, Part 665, all vessel owners who fish for deepwater shrimp (<E T="03">Heterocarpus</E>spp.), or land these species in ports, in the western Pacific region must obtain a Federal permit from the National Marine Fisheries Service (NMFS). They must also mark their vessels for identification. Vessel operators must submit NMFS logbook reports of their fishing activity to NMFS within 72 hours of the end of each fishing trip.</P>
        <P>The information collected is used to identify participants in the fishery, document fishing activities and landings, determine the conditions of the stocks, assess the effectiveness of management measures, evaluate the benefits and costs of changes in management measures, and monitor and respond to accidental takes of protected species, including seabirds, turtles, and marine mammals.</P>
        <P>Vessel owners must identify their vessels to assist in aerial and at-sea enforcement of fishing regulations.</P>
        <P>
          <E T="03">Affected Public:</E>Business or other for-profit organizations.</P>
        <P>
          <E T="03">Frequency:</E>Annually and on occasion.</P>
        <P>
          <E T="03">Respondent's Obligation:</E>Mandatory.</P>
        <P>
          <E T="03">OMB Desk Officer: OIRA_Submission@omb.eop.gov.</E>
        </P>

        <P>Copies of the above information collection proposal can be obtained by calling or writing Jennifer Jessup, Departmental Paperwork Clearance Officer, (202) 482-0336, Department of Commerce, Room 6616, 14th and Constitution Avenue NW., Washington, DC 20230 (or via the Internet at<E T="03">JJessup@doc.gov</E>).</P>

        <P>Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to<E T="03">OIRA_Submission@omb.eop.gov.</E>
        </P>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Gwellnar Banks,</NAME>
          <TITLE>Management Analyst, Office of the Chief Information Officer.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10908 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
        <P>The Department of Commerce will submit to the Office of Management and Budget (OMB) for clearance the following proposal for collection of information under the provisions of the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <P>
          <E T="03">Agency:</E>U.S. Census Bureau.</P>
        <P>
          <E T="03">Title:</E>2012 National Census Test.</P>
        <P>
          <E T="03">OMB Control Number:</E>None.</P>
        <P>
          <E T="03">Form Number(s):</E>Questionnaire: DA-1; Letters: DA-5(L), DA-16(L)(1), DA-16(L)(2), DA-17(L)(1), DA-17(L)(2), DA-17(L)(3); Reminder Postcards: DA-9, DA-9(2A), DA-9(2B), DA-9(2C); Envelopes: DA-5, DA-6A(IN), DA-6A(1)(IN), DA-8A; Internet Instruction Card: DA-33.</P>
        <P>
          <E T="03">Type of Request:</E>New collection.</P>
        <P>
          <E T="03">Burden Hours:</E>16,668.</P>
        <P>
          <E T="03">Number of Respondents:</E>80,000.</P>
        <P>
          <E T="03">Average Hours per Response:</E>10 minutes.<PRTPAGE P="26737"/>
        </P>
        <P>
          <E T="03">Needs and Uses:</E>The Census Bureau has committed to using the Internet as a primary response option in the 2020 Census. However, much research is needed throughout the next decade to develop and implement a successful, secure, and user-friendly online instrument. The Census Bureau must conduct a series of research projects and tests throughout this decade to fulfill its commitment to provide the public with an option to complete their 2020 Decennial Census questionnaire on the Internet. One of the first tests to support this planning effort is the 2012 National Census Test (NCT).</P>
        <P>The 2012 NCT seeks to build on previous Internet data collection research in order to set the stage for the Internet testing cycle for the 2020 Census. The main objective is to test new, dynamic approaches for collecting the number of people in a household, which are not feasible on a paper questionnaire. The anticipated use of the Internet as a primary mode of self-response in the 2020 Census offers the unique opportunity to incorporate conditional residence probes. By making optimal use of electronic data collection for delivery of coverage probes, we can gain a better understanding of who was living in a household on Census Day, thereby greatly reducing (or potentially eliminating) the need for the costly Coverage Followup (CFU) operation. The goal is to optimize the residence rules presentation for the Internet mode and identify validated methods for determining residency. We will utilize a real-time, targeted, probing coverage reinterview conducted by telephone to evaluate the accuracy of within-household coverage by comparing the final household population roster for the Internet Test households to the final reinterview roster for the same households.</P>
        <P>As a secondary objective of the 2012 NCT, the Census Bureau aims to study the relative response rates associated with various contact strategies under an Internet Push methodology, in an effort to obtain early response rate indicators for the 2020 Census. The 2012 Internet Test sets the stage for future testing by making important strides in obtaining a select subset of contact strategy options that can be validated in later mid-decade tests. Various contact strategies involving optimizing the Internet push strategy are proposed, such as implementing relatively less expensive reminders both before and after the questionnaire mailing, which builds off recent American Community Survey (ACS) results. Also included is the removal of the advance letter mailing, new motivational wording and varying the timing of the questionnaire mailing to optimize self-response.</P>
        <P>Additionally, without impact to sample size, the 2012 NCT offers the opportunity to gain knowledge about how to optimize the presentation of the race and Hispanic origin questions.</P>
        <P>Results from the 2010 Alternative Questionnaire Experiment reveal that the combination of the race and Hispanic origin question approach appears to be a promising strategy for collecting these data items. As an additional secondary objective, the Census Bureau plans to continue this research by implementing two versions of a combined race and Hispanic origin question as part of the 2012 NCT. In addition, this data collection will incorporate the use of predictive text to automate and streamline the race and Hispanic origin coding processes. This component allows for near-real-time data processing by increasing the speed of automated coding, thus reducing and/or eliminating back-end processing.</P>
        <P>
          <E T="03">Affected Public:</E>Individuals or households.</P>
        <P>
          <E T="03">Frequency:</E>One time.</P>
        <P>
          <E T="03">Respondent's Obligation:</E>Mandatory.</P>
        <P>
          <E T="03">Legal Authority:</E>Title 13, United States Code, Section 141, 193, and 225.</P>
        <P>
          <E T="03">OMB Desk Officer:</E>Brian Harris-Kojetin, (202) 395-7314.</P>

        <P>Copies of the above information collection proposal can be obtained by calling or writing Jennifer Jessup, Departmental Paperwork Clearance Officer, (202) 482-0336, Department of Commerce, Room 6616, 14th and Constitution Avenue NW., Washington, DC 20230 (or via the Internet at<E T="03">jjessup@doc.gov)</E>.</P>

        <P>Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to Brian Harris-Kojetin, OMB Desk Officer either by fax (202-395-7245) or email (<E T="03">bharrisk@omb.eop.gov</E>).</P>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Glenna Mickelson,</NAME>
          <TITLE>Management Analyst, Office of the Chief Information Officer.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10924 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-07-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
        <DEPDOC>[B-31-2012]</DEPDOC>
        <SUBJECT>Foreign-Trade Zone 235—Lakewood, NJ: Notification of Proposed Production Activity; Cosmetic Essence Innovations, LLC (Fragrance Bottling); Holmdel, NJ</SUBJECT>
        <P>Cosmetic Essence Innovations, LLC (CEI) has submitted a notification of proposed production activity for their facility located in Holmdel, New Jersey. The CEI facility is located within Site 8 of FTZ 235. The facility is used for the blending and bottling of fragrances. Components and materials sourced from abroad include: plastic bottles; glass bottles; plastic caps and lids; metal caps and lids; plastic collars; sprayers; pumps; and, decorative charms on chains (duty rate ranges from duty-free to 5.3%).</P>
        <P>Production under FTZ procedures could exempt CEI from customs duty payments on the foreign status components used in export production. On its domestic sales, CEI would be able to choose the duty rates during customs entry procedures that apply to bottles of fragrance (duty-free) for the foreign status inputs noted above. Customs duties also could possibly be deferred or reduced on foreign status production equipment.</P>
        <P>Public comment is invited from interested parties. Submissions shall be addressed to the Board's Executive Secretary at the address below. The closing period for their receipt is June 18, 2012.</P>

        <P>A copy of the notification will be available for public inspection at the Office of the Executive Secretary, Foreign-Trade Zones Board, Room 2111, U.S. Department of Commerce, 1401 Constitution Avenue NW., Washington, DC 20230-0002, and in the “Reading Room” section of the Board's Web site, which is accessible via<E T="03">www.trade.gov/ftz.</E>
        </P>
        <P>For further information, contact Elizabeth Whiteman at<E T="03">Elizabeth.Whiteman@trade.gov</E>or (202) 482-0473.</P>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Andrew McGilvray,</NAME>
          <TITLE>Executive Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10953 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="26738"/>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>International Trade Administration</SUBAGY>
        <DEPDOC>[C-570-978]</DEPDOC>
        <SUBJECT>High Pressure Steel Cylinders From the People's Republic of China: Final Affirmative Countervailing Duty Determination</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>The Department of Commerce (the Department) determines that countervailable subsidies are being provided to producers and exporters of high pressure steel cylinders (steel cylinders) from the People's Republic of China (the PRC). For information on the estimated subsidy rates, see the “Suspension of Liquidation” section, below.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>May 7, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Christopher Siepmann or Yasmin Nair, AD/CVD Operations, Office 1, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-7958 or (202) 482-3813, respectively.</P>
          <HD SOURCE="HD1">Background</HD>
          <P>The U.S. producer that filed the petition for this investigation is Norris Cylinder Co. (Petitioner). The mandatory respondent to this investigation is Beijing Tianhai Industry Co., Ltd. (BTIC).</P>
          <HD SOURCE="HD1">Period of Investigation</HD>
          <P>The period for which we are measuring subsidies, or period of investigation, is January 1, 2010, through December 31, 2010.</P>
          <HD SOURCE="HD1">Case History</HD>
          <P>The following events have occurred since the<E T="03">Preliminary Determination.</E>
            <SU>1</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>1</SU>
              <E T="03">See High Pressure Steel Cylinders From the People's Republic of China: Preliminary Affirmative Countervailing Duty Determination and Alignment of Final Countervailing Duty Determination With Final Antidumping Duty Determination,</E>76 FR 64301 (October 18, 2011) (“<E T="03">Preliminary Determination”</E>).</P>
          </FTNT>
          <P>On October 14, 2011, the Government of China (GOC) filed a partial response to the Department's second supplemental questionnaire and requested an extension to complete its supplemental questionnaire response. The Department granted the GOC's request, and on October 18, 2011, the GOC submitted its response to the outstanding questions in the second supplemental questionnaire. On October 28, 2011, the Department issued its third supplemental questionnaire to BTIC and the GOC, and on November 14, 2011, it received responses from both.</P>
          <P>On November 18, 2011, interested party Zhejiang Jindun Pressure Vessel Co., Ltd. (Jindun) filed a request for a hearing. On November 22, 2011, the Department denied Jindun's request because it was untimely filed, pursuant to section 351.310(c) of the Department's regulations.</P>
          <P>The Department conducted verification of BTIC's and the GOC's questionnaire responses from December 7 to December 14, 2011, and issued verification reports for BTIC and the GOC on January 3, and January 17, 2012, respectively.</P>
          <P>The Department issued a post-preliminary analysis memorandum regarding three programs on March 14, 2012.</P>
          <P>BTIC, the GOC, and Jindun submitted case briefs on March 23, 2012, and Petitioners submitted a rebuttal brief on March 28, 2012.</P>
          <HD SOURCE="HD1">Scope Comments</HD>

          <P>In accordance with the preamble to the Department's regulations, we set aside a period of time in our<E T="03">Initiation Notice</E>for parties to raise issues regarding product coverage, and encouraged all parties to submit comments within 20 calendar days of publication of that notice.<E T="03">See Antidumping Duties; Countervailing Duties,</E>62 FR 27296, 27323 (May 19, 1997), and<E T="03">Initiation Notice,</E>76 FR at 33239. We did not receive any comments.</P>
          <HD SOURCE="HD1">Scope of the Investigation</HD>
          <P>The merchandise covered by the scope of the investigation is seamless steel cylinders designed for storage or transport of compressed or liquefied gas (“high pressure steel cylinders”). High pressure steel cylinders are fabricated of chrome alloy steel including, but not limited to, chromium-molybdenum steel or chromium magnesium steel, and have permanently impressed into the steel, either before or after importation, the symbol of a U.S. Department of Transportation, Pipeline and Hazardous Materials Safety Administration (“DOT”)-approved high pressure steel cylinder manufacturer, as well as an approved DOT type marking of DOT 3A, 3AX, 3AA, 3AAX, 3B, 3E, 3HT, 3T, or DOT-E (followed by a specific exemption number) in accordance with the requirements of sections 178.36 through 178.68 of Title 49 of the Code of Federal Regulations, or any subsequent amendments thereof. High pressure steel cylinders covered by these investigations have a water capacity up to 450 liters, and a gas capacity ranging from 8 to 702 cubic feet, regardless of corresponding service pressure levels and regardless of physical dimensions, finish or coatings.</P>
          <P>Excluded from the scope of the investigation are high pressure steel cylinders manufactured to UN-ISO-9809-1 and 2 specifications and permanently impressed with ISO or UN symbols. Also excluded from the investigation are acetylene cylinders, with or without internal porous mass, and permanently impressed with 8A or 8AL in accordance with DOT regulations.</P>
          <P>Merchandise covered by the investigation is classified in the Harmonized Tariff Schedule of the United States (“HTSUS”) under subheading 7311.00.00.30. Subject merchandise may also enter under HTSUS subheadings 7311.00.00.60 or 7311.00.00.90. Although the HTSUS subheadings are provided for convenience and customs purposes, the written description of the merchandise under the investigation is dispositive.</P>
          <HD SOURCE="HD1">Analysis of Comments Received</HD>

          <P>All issues raised in the case and rebuttal briefs by parties to this investigation are addressed in the Memorandum to Paul Piquado, Assistant Secretary for Import Administration, entitled “Issues and Decision Memorandum for the Final Determination in the Countervailing Duty Investigation of High Pressure Steel Cylinders from the People's Republic of China” (April 30, 2012) (hereafter, “Decision Memorandum”), which is hereby adopted by this notice. Attached to this notice as an Appendix is a list of the issues that parties have raised and to which we have responded in the Decision Memorandum. Parties can find a complete discussion of all issues raised in this investigation and the corresponding recommendations in this public memorandum, which is on file electronically via IA ACCESS. In addition, a complete version of the Decision Memorandum is also accessible on the Web at<E T="03">http://ia.ita.doc.gov/frn/</E>. The paper copy and electronic version of the Decision Memorandum are identical in content.</P>
          <HD SOURCE="HD1">Suspension of Liquidation</HD>

          <P>In accordance with section 703(c)(1)(B)(i)(I) of the Tariff Act of 1930 (the “Act”), we calculated an individual rate for each producer/exporter of the subject merchandise individually investigated. Because only one company<PRTPAGE P="26739"/>was investigated, that company's rate also serves as the All Others rate.</P>
          <P>We determine the total net countervailable subsidy rates to be:</P>
          <GPOTABLE CDEF="s125,7" COLS="2" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">Exporter/Manufacturer</CHED>
              <CHED H="1">Net<LI>subsidy</LI>
                <LI>rate</LI>
              </CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">Beijing Tianhai Industry Co., Ltd.; Tianjin Tianhai High Pressure Container Co., Ltd.; Langfang Tianhai High Pressure Container Co., Ltd</ENT>
              <ENT>15.81</ENT>
            </ROW>
            <ROW>
              <ENT I="01">All Others</ENT>
              <ENT>15.81</ENT>
            </ROW>
          </GPOTABLE>
          <P>As a result of our<E T="03">Preliminary Determination</E>and pursuant to section 703(d) of the Act, we instructed U.S. Customs and Border Protection (CBP) to suspend liquidation of all entries of subject merchandise from the PRC which were entered or withdrawn from warehouse, for consumption on or after October 18, 2011, the date of the publication of the<E T="03">Preliminary Determination</E>in the<E T="04">Federal Register</E>. In accordance with section 703(d) of the Act, we later issued instructions to CBP to discontinue the suspension of liquidation for countervailing duty purposes for subject merchandise entered or withdrawn from warehouse, on or after February 15, 2012, but to continue the suspension of liquidation of all entries from October 18, 2011, through February 14, 2012.</P>
          <P>We will issue a countervailing duty order and reinstate the suspension of liquidation under section 706(a) of the Act if the U.S. International Trade Commission (ITC) issues a final affirmative injury determination, and will require a cash deposit of estimated countervailing duties for such entries in the amounts indicated above. If the ITC determines that material injury, or threat of material injury, does not exist, this proceeding will be terminated and all estimated deposits or securities posted as a result of the suspension of liquidation will be refunded or canceled.</P>
          <HD SOURCE="HD1">ITC Notification</HD>
          <P>In accordance with section 705(d) of the Act, we will notify the ITC of our determination. In addition, we are making available to the ITC all non-privileged and non-proprietary information related to this investigation. We will allow the ITC access to all privileged and business proprietary information in our files, provided the ITC confirms that it will not disclose such information, either publicly or under an APO, without the written consent of the Assistant Secretary for Import Administration.</P>
          <HD SOURCE="HD1">Return or Destruction of Proprietary Information</HD>
          <P>In the event that the ITC issues a final negative injury determination, this notice will serve as the only reminder to parties subject to an administrative protective order (APO) of their responsibility concerning the destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3). Timely written notification of the return/destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
          <P>This determination is published pursuant to sections 705(d) and 777(i) of the Act.</P>
          <SIG>
            <DATED>Dated: April 30, 2012.</DATED>
            <NAME>Ronald K. Lorentzen,</NAME>
            <TITLE>Acting Assistant Secretary for Import Administration.</TITLE>
          </SIG>
          <HD SOURCE="HD1">Appendix</HD>
          <EXTRACT>
            <HD SOURCE="HD1">List of Comments and Issues in the Decision Memorandum</HD>
            <FP SOURCE="FP-2">Comment 1Application of the CVD Law to the People's Republic of China</FP>
            <FP SOURCE="FP-2">Comment 2Double Counting/Overlapping Remedies</FP>
            <FP SOURCE="FP-2">Comment 3Whether the Department Should Have Selected Jindun as a Mandatory or Voluntary Respondent</FP>
            <FP SOURCE="FP-2">Comment 4Whether a Certain Producer of Seamless Tube Steel Partially-Owned by SOEs is a Government Authority</FP>
            <FP SOURCE="FP-2">Comment 5Whether a Certain Producer of Seamless Tube Steel Owned by Individuals is a Government Authority</FP>
            <FP SOURCE="FP-2">Comment 6Countervailability of Seamless Tube Steel Produced by One of BTIC's Affiliates</FP>
            <FP SOURCE="FP-2">Comment 7Countervailability of Inputs Purchased from Domestic Trading Companies</FP>
            <FP SOURCE="FP-2">Comment 8Whether to Limit the Benchmark for Seamless Tube Steel to Certain Countries or Diameters</FP>
            <FP SOURCE="FP-2">Comment 9Whether to Incorporate VAT and Import Duties into Input Benchmarks</FP>
            <FP SOURCE="FP-2">Comment 10Application of Adverse Facts Available to the Electricity Benchmark</FP>
            <FP SOURCE="FP-2">Comment 11Alleged Errors in the Department's Calculations for the Provision of Electricity for LTAR</FP>
            
          </EXTRACT>
        </FURINF>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10954 Filed 5-4-12; 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-977]</DEPDOC>
        <SUBJECT>High Pressure Steel Cylinders From the People's Republic of China: Final Determination of Sales at Less Than Fair Value</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Import Administration, International Trade Administration, Department of Commerce.</P>
        </AGY>
        
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>May 7, 2012.</P>
        </DATES>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>On December 15, 2011, the Department of Commerce (“Department”) published the<E T="03">Preliminary Determination</E>of sales at less than fair value (“LTFV”) in the antidumping investigation of high pressure steel cylinders from the People's Republic of China (“PRC”).<SU>1</SU>

            <FTREF/>The period of investigation (“POI”) is October 1, 2010, through March 31, 2011. Based on its analysis of the comments received, the Department has made changes to its<E T="03">Preliminary Determination.</E>The Department continues to find that high pressure steel cylinders from the PRC are being, or are likely to be, sold in the United States at LTFV, as provided in section 735 of the Tariff Act of 1930, as amended (“Act”). The estimated margins of sales at LTFV are shown in the “Final Determination Margins” section of this notice.</P>
          <FTNT>
            <P>
              <SU>1</SU>
              <E T="03">See High Pressure Steel Cylinders From the People's Republic of China: Preliminary Determination of Sales at Less than Fair Value,</E>76 FR 77964 (December 15, 2011) (“<E T="03">Preliminary Determination”</E>).</P>
          </FTNT>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Alan Ray or Emeka Chukwudebe, 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-5403 or 482-0219, respectively.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>
        <P>Since the<E T="03">Preliminary Determination,</E>the Department conducted sales and factors of production (“FOP”) verifications for Beijing Tianhai Industry Co., Ltd. (“BTIC”), the mandatory respondent, from January 9 through January 17, 2012, and a sales verification for American Fortune Company (“AFC”), BTIC's U.S. affiliate, on February 9 and 10, 2012.<SU>2</SU>
          <FTREF/>
          <E T="03">See</E>the<PRTPAGE P="26740"/>“Verification” section below for additional information. On January 31, 2012, and February 10, 2012, we received surrogate value (“SV”) comments from both BTIC and Petitioner and rebuttal SV comments from BTIC. On March 2, 2011, we issued a post-preliminary supplemental questionnaire.</P>
        <FTNT>
          <P>

            <SU>2</SU>We conducted verifications of BTIC and one of its affiliated producers, Langfang Tianhai High Pressure Contain Co., Ltd. (“Langfang Tianhai”), which produced the merchandise under<PRTPAGE/>investigation that BTIC sold to the United States, and BTIC's U.S. affiliate which sold merchandise under investigation in the United States.<E T="03">See</E>Memo to the File, through Matthew Renkey, Acting Program Manager, Office 9, from Alan Ray and Emeka Chukwudebe, International Trade Analysts, “Verification of the Sales and Factors of Production Response of Beijing Tianhai Industry Co., Ltd. (“BTIC”) in the Investigation of High Pressure Steel Cylinders from the People's Republic of China,” dated February 23, 2012 (“BTIC Verification Report”); Memo to the File, through Matthew Renkey, Acting Program Manager, Office 9, from Alan Ray and Ricardo Martinez Rivera, International Trade Analysts,, “Verification of the Constructed Export Price Sales of American Fortune Company (“AFC”) in the Investigation of High Pressure Steel Cylinders from the People's Republic of China,” dated February 23, 2012 (“AFC Verification Report”).</P>
        </FTNT>

        <P>Upon the February 23, 2012, release of the verification reports, we invited interested parties to comment on the<E T="03">Preliminary Determination.</E>On March 6, 2012, we received case briefs from Petitioner,<SU>3</SU>
          <FTREF/>BTIC, and Zhejiang Jindun Pressure Vessel Co., Ltd. (“Jindun”). On March 26, 2012, we received rebuttal briefs from Petitioner and BTIC. On March 16, 2012, we released a new labor calculation and requested that interested parties submit comments.<SU>4</SU>
          <FTREF/>On March 26, 2012, BTIC submitted comments regarding the revised labor calculation. The Department held a public hearing on April 4, 2012, pursuant to 19 CFR 351.310(d).</P>
        <FTNT>
          <P>
            <SU>3</SU>Norris Cylinder Company.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>
            <E T="03">See</E>“Memorandum to Christian Marsh, Deputy Assistant Secretary, for Antidumping and Countervailing Duty Operations, through Matthew Renkey, Acting Program Manager, Office 9, from Emeka Chukwudebe, Case Analyst, Office 9: Antidumping Duty Investigation of High Pressure Steel Cylinders from the People's Republic of China: Post-Preliminary Analysis Regarding Surrogate Labor Value,” dated March 16, 2012 (“Surrogate Labor Value Memo”).</P>
        </FTNT>
        <HD SOURCE="HD1">Analysis of Comments Received</HD>

        <P>All issues raised in the case and rebuttal briefs by parties to this investigation are addressed in the “Antidumping Duty Investigation of High Pressure Steel Cylinders from the People's Republic of China: Issues and Decision Memorandum for the Final Determination” (“Decision Memorandum”), dated concurrently with this notice and which is hereby adopted by this notice. A list of the issues which parties raised, and to which we respond to in the Decision Memorandum, is attached to this notice as Appendix I. The Decision Memorandum is a public document and is on file electronically via Import Administration's Antidumping and Countervailing Duty Centralized Electronic Service System (“IA ACCESS”). Access to IA ACCESS is available in the Central Records Unit (“CRU”), room 7046 of the main Department of Commerce building. In addition, a complete version of the Decision Memorandum can be accessed directly on the internet at<E T="03">http://www.trade.gov/ia/.</E>The signed Decision Memorandum and the electronic versions of the Decision Memorandum are identical in content.</P>
        <HD SOURCE="HD1">Changes Since the Preliminary Determination</HD>
        <P>Based on our analysis of information on the record of this investigation, we have made changes regarding BTIC and the separate rate companies<SU>5</SU>
          <FTREF/>for the final determination.</P>
        <FTNT>
          <P>
            <SU>5</SU>Jindun, Shanghai J.S.X. International Trading Corporation (“Shanghai J.S.X.”), and Shijiazhuang Enric Gas Equipment Co., Ltd. (“Enric”) (“Separate Rate Respondents”).</P>
        </FTNT>
        <P>• Subsequent to the<E T="03">Preliminary Determination,</E>at the Department's request, BTIC provided a revised FOP and sales database.</P>
        <P>• We have changed the source used for valuing truck freight.</P>
        <P>• We have changed the surrogate financial statements upon which we are relying to calculate financial ratios from Everest Kanto Cylinder Ltd. to Thai Metal Drum Manufacturing Public Company Limited.</P>
        <P>• We have excluded water and all of the other energy FOPs from the build-up for normal value as the Thai Metal Drum Manufacturing Public Company Limited financial statement does not provide sufficient detail for the Department to allocate those factors appropriately.</P>
        <P>• We are changing the date of sale for constructed export price (“CEP”) sales to reflect the correct date of sale in the “Targeted Dumping” section of the margin calculation program.</P>
        <P>• We are using the revised labor valuation methodology discussed in our March 16, 2012, memorandum.<SU>6</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>6</SU>
            <E T="03">See</E>Surrogate Labor Value Memo.</P>
        </FTNT>
        <P>• In the<E T="03">Preliminary Determination,</E>we assigned the PRC-wide rate of 26.23 percent, the highest transaction-specific rate preliminarily calculated for BTIC. For this final determination, we continue to use BTIC's highest transaction-specific rate, which now is 31.42 percent.</P>
        <HD SOURCE="HD1">Scope of Investigation</HD>
        <P>The merchandise covered by the scope of the investigation is seamless steel cylinders designed for storage or transport of compressed or liquefied gas (“high pressure steel cylinders”). High pressure steel cylinders are fabricated of chrome alloy steel including, but not limited to, chromium-molybdenum steel or chromium magnesium steel, and have permanently impressed into the steel, either before or after importation, the symbol of a U.S. Department of Transportation, Pipeline and Hazardous Materials Safety Administration (“DOT”) approved high pressure steel cylinder manufacturer, as well as an approved DOT type marking of DOT 3A, 3AX, 3AA, 3AAX, 3B, 3E, 3HT, 3T, or DOT-E (followed by a specific exemption number) in accordance with the requirements of sections 178.36 through 178.68 of Title 49 of the Code of Federal Regulations, or any subsequent amendments thereof. High pressure steel cylinders covered by the investigation have a water capacity up to 450 liters, and a gas capacity ranging from 8 to 702 cubic feet, regardless of corresponding service pressure levels and regardless of physical dimensions, finish or coatings.</P>
        <P>Excluded from the scope of the investigation are high pressure steel cylinders manufactured to UN-ISO-9809-1 and 2 specifications and permanently impressed with ISO or UN symbols. Also excluded from the investigation are acetylene cylinders, with or without internal porous mass, and permanently impressed with 8A or 8AL in accordance with DOT regulations.</P>
        <P>Merchandise covered by the investigation is classified in the Harmonized Tariff Schedule of the United States (“HTSUS”) under subheading 7311.00.00.30. Subject merchandise may also enter under HTSUS subheadings 7311.00.00.60 or 7311.00.00.90. Although the HTSUS subheadings are provided for convenience and customs purposes, the written description of the merchandise under the investigation is dispositive.</P>
        <HD SOURCE="HD1">Verification</HD>
        <P>As provided in section 782(i) of the Act, we conducted verification of the information submitted by BTIC for use in our final determination. We used standard verification procedures, including examination of relevant accounting and production records, as well as original source documents provided by BTIC.<SU>7</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>7</SU>
            <E T="03">See</E>BTIC Verification Report; AFC Verification Report.</P>
        </FTNT>
        <PRTPAGE P="26741"/>
        <HD SOURCE="HD1">Surrogate Country</HD>
        <P>In the<E T="03">Preliminary Determination,</E>we selected Ukraine as the primary surrogate country in this investigation because: (1) In accordance with section 773(c)(4) of the Act, we determined that it is a significant producer of comparable merchandise and it is at a level of economic development comparable to the PRC; and (2) Ukraine data satisfy several factors that the Department considers in selecting a primary surrogate country, including whether the SV data are publicly available, contemporaneous with the POI, represent a broad-market average, from an approved surrogate country, are tax- and duty-exclusive, and specific to the input.<SU>8</SU>
          <FTREF/>Interested parties submitted comments regarding our preliminary determinations concerning the selection of surrogate country, which are summarized in the accompanying Decision Memo at Comment I. For this final determination we continue to select Ukraine as the primary surrogate country.</P>
        <FTNT>
          <P>
            <SU>8</SU>
            <E T="03">See Preliminary Determination,</E>76 FR at 77967-77968.</P>
        </FTNT>
        <HD SOURCE="HD1">Separate Rates</HD>
        <P>In proceedings involving non-market-economy (“NME”) countries, the Department begins with a rebuttable presumption that all companies within the country are subject to government control and, thus, should be assigned a single antidumping duty deposit rate. It is the Department's policy to assign all exporters of merchandise subject to an investigation in an NME country this single rate unless an exporter can demonstrate that it is sufficiently independent so as to be entitled to a separate rate.<SU>9</SU>
          <FTREF/>In the<E T="03">Preliminary Determination,</E>we found that BTIC, Enric, Jindun, and Shanghai J.S.X., (collectively, “Separate Rate Companies”) demonstrated their eligibility for, and were hence assigned, separate rate status.<SU>10</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>9</SU>
            <E T="03">See Final Determination of Sales at Less Than Fair Value: Sparklers From the People's Republic of China,</E>56 FR 20588 (May 6, 1991) (“<E T="03">Sparklers”</E>), as amplified by<E T="03">Notice of Final Determination of Sales at Less Than Fair Value: Silicon Carbide From the People's Republic of China,</E>59 FR 22585 (May 2, 1994) (“<E T="03">Silicon Carbide”</E>), and 19 CFR 351.107(d).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>
            <E T="03">See Preliminary Determination,</E>76 FR at 77965 n.16 and 77969.</P>
        </FTNT>

        <P>No parties commented on the above companies' eligibility for separate rate status. Consequently, for the final determination, we continue to find that these companies demonstrated both a<E T="03">de jure</E>and<E T="03">de facto</E>absence of government control with respect to their exports of the merchandise under investigation, and are eligible for separate rate status for the final determination.</P>
        <HD SOURCE="HD1">Calculation of the Margin for the Separate Rate Companies</HD>
        <P>As in the<E T="03">Preliminary Determination,</E>we are basing the antidumping duty margin for those companies receiving a separate rate, but who were not individually examined,<SU>11</SU>
          <FTREF/>on the margin calculated for BTIC.<SU>12</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>11</SU>Enric, Jindun, and Shanghai J.S.X.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>12</SU>
            <E T="03">See Preliminary Determination,</E>76 FR at 77970.</P>
        </FTNT>

        <P>The Department received comments from Jindun regarding the Department's<E T="03">Preliminary Determination</E>and its decision not to examine Jindun as a voluntary respondent, as requested. The Department has addressed these arguments in Comment VI of the Decision Memorandum. For the final determination, we continue not to individually examine Jindun. Accordingly, Jindun will continue to be treated as and receive the rate assigned to the non-selected, Separate Rate Companies.<SU>13</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>13</SU>
            <E T="03">See</E>Decision Memorandum at Comment 7.</P>
        </FTNT>
        <HD SOURCE="HD1">The PRC-Wide Entity Rate</HD>

        <P>Because we begin with the presumption that all companies within a NME country are subject to government control, and because only the companies listed under the “Final Determination Margins” section, below, have overcome that presumption, we are assigning a single weighted-average dumping margin (<E T="03">i.e.,</E>the PRC-wide rate) to all other exporters of the merchandise under consideration. These other companies did not demonstrate entitlement to a separate rate.<SU>14</SU>
          <FTREF/>The PRC-wide rate applies to all entries of the merchandise under consideration except for entries from the Separate Rate Companies.</P>
        <FTNT>
          <P>
            <SU>14</SU>
            <E T="03">See, e.g.,</E>
            <E T="03">Synthetic Indigo From the People's Republic of China; Notice of Final Determination of Sales at Less Than Fair Value,</E>65 FR 25706, 25707 (May 3, 2000).</P>
        </FTNT>
        <P>In the<E T="03">Preliminary Determination,</E>the Department determined that there were exporters/producers of the merchandise subject to this investigation during the POI from the PRC that did not respond to the Department's request for information.<SU>15</SU>
          <FTREF/>Further, we treated these PRC exporters/producers as part of the PRC-wide entity because they did not qualify for a separate rate. Therefore, we find that the use of facts available (“FA”) is necessary and appropriate to determine the PRC-wide rate pursuant to section 776(a)(2)(A) of the Act.<SU>16</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>15</SU>
            <E T="03">See Preliminary Determination,</E>76 FR at 77970.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>16</SU>
            <E T="03">See id.</E>
          </P>
        </FTNT>
        <P>In the<E T="03">Preliminary Determination,</E>the Department also determined that, in selecting from among the FA, an adverse inference is appropriate because the PRC-wide entity failed to cooperate by not acting to the best of its ability to comply with requests for information.<SU>17</SU>
          <FTREF/>As adverse facts available (“AFA”), we preliminarily assigned to the PRC-wide entity a rate of 26.23 percent, the highest transaction-specific rate preliminarily calculated for BTIC.<SU>18</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>17</SU>
            <E T="03">See id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>18</SU>
            <E T="03">See id.,</E>at 77971.</P>
        </FTNT>
        <P>Section 776(a)(2) of the Act provides that, if an interested party (A) withholds information requested by the Department, (B) fails to provide such information by the deadline, or in the form or manner requested, (C) significantly impedes a proceeding, or (D) provides information that cannot be verified, the Department shall use, subject to section 782(d) of the Act, facts otherwise available in reaching the applicable determination. Section 776(b) of the Act provides that, in selecting from among the facts otherwise available, the Department may employ an adverse inference if an interested party fails to cooperate by not acting to the best of its ability to comply with requests for information.<SU>19</SU>
          <FTREF/>We find that, because the PRC-wide entity did not respond to our request for information, it has failed to cooperate to the best of its ability. Therefore, the Department finds that, in selecting from among the facts otherwise available, an adverse inference is appropriate.</P>
        <FTNT>
          <P>
            <SU>19</SU>
            <E T="03">See Notice of Final Determination of Sales at Less Than Fair Value: Certain Cold-Rolled Flat-Rolled Carbon-Quality Steel Products from the Russian Federation,</E>65 FR 5510, 5518 (February 4, 2000).<E T="03">See also</E>Statement of Administrative Action accompanying the Uruguay Round Agreements Act, H.R. Doc. 103-316, vol. 1, at 870 (1994) (“SAA”).</P>
        </FTNT>
        <P>In deciding which facts to use as AFA, section 776(b) of the Act and 19 CFR 351.308(c)(1) provide that the Department may rely on information derived from (1) the petition, (2) a final determination in the investigation, (3) any previous review or determination, or (4) any information placed on the record. In selecting a rate for AFA, the Department selects a rate that is sufficiently adverse “so as to effectuate the statutory purposes of the adverse facts available rule to induce respondents to provide the Department with complete and accurate information in a timely manner.”<SU>20</SU>

          <FTREF/>It is also the Department's practice to select a rate that ensures “that the party does not obtain a more favorable result by failing<PRTPAGE P="26742"/>to cooperate than if it had cooperated fully.”<SU>21</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>20</SU>
            <E T="03">See Notice of Final Determination of Sales at Less Than Fair Value: Static Random Access Memory Semiconductors From Taiwan,</E>63 FR 8909, 8932 (February 23, 1998).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>21</SU>
            <E T="03">See</E>SAA at 870.</P>
        </FTNT>
        <P>In the<E T="03">Preliminary Determination,</E>the Department selected as AFA, a rate of 26.23 percent, the highest transaction-specific rate for BTIC.<SU>22</SU>

          <FTREF/>For the final determination, the Department continues to use the same methodology to determine the AFA rate used in the<E T="03">Preliminary Determination.</E>
          <SU>23</SU>

          <FTREF/>Specifically, the Department continues to use the highest transaction-specific rate calculated for BTIC, which, because of changes to the calculations since the<E T="03">Preliminary Determination</E>now is 31.42 percent. No parties commented on the selection of AFA.</P>
        <FTNT>
          <P>
            <SU>22</SU>
            <E T="03">See Preliminary Determination,</E>76 FR at 77971.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>23</SU>
            <E T="03">See</E>i<E T="03">d.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD1">Final Determination Weighted-Average Dumping Margins</HD>
        <P>We determine that the following weighted-average dumping margins exist for the following entities for the POI:</P>
        <GPOTABLE CDEF="s150,r150,9" COLS="3" OPTS="L2,tp0,i1">
          <BOXHD>
            <CHED H="1">Exporter</CHED>
            <CHED H="1">Producer</CHED>
            <CHED H="1">Weighted-Average<LI>dumping margin</LI>
              <LI>(percent)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Beijing Tianhai Industry Co., Ltd.</ENT>
            <ENT>Beijing Tianhai Industry Co., Ltd.</ENT>
            <ENT>6.62</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Beijing Tianhai Industry Co., Ltd.</ENT>
            <ENT>Tianjin Tianhai High Pressure Container Co., Ltd.</ENT>
            <ENT>6.62</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Beijing Tianhai Industry Co., Ltd.</ENT>
            <ENT>Langfang Tianhai High Pressure Container Co., Ltd.</ENT>
            <ENT>6.62</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Shanghai J.S.X. International Trading Corporation</ENT>
            <ENT>Shanghai High Pressure Special Gas Cylinder Co., Ltd.</ENT>
            <ENT>6.62</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Zhejiang Jindun Pressure Vessel Co., Ltd.</ENT>
            <ENT>Zhejiang Jindun Pressure Vessel Co., Ltd.</ENT>
            <ENT>6.62</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Shijiazhuang Enric Gas Equipment Co., Ltd.</ENT>
            <ENT>Shijiazhuang Enric Gas Equipment Co., Ltd.</ENT>
            <ENT>6.62</ENT>
          </ROW>
          <ROW>
            <ENT I="01">PRC-Wide Rate<SU>24</SU>
            </ENT>
            <ENT/>
            <ENT>31.21</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">Disclosure</HD>
        <P>We will disclose the calculations<FTREF/>performed within five days of the date of publication of this notice to parties in this proceeding in accordance with 19 CFR 351.224(b).</P>
        <FTNT>
          <P>
            <SU>24</SU>The PRC-Wide entity includes: Shanghai High Pressure Container Co., Ltd.; Heibei Baigong Industrial Co., Ltd.; Nanjing Ocean High-Pressure Vessel Co., Ltd.; Qingdao Baigong Industrial and Trading Co., Ltd.; Shandong Huachen High Pressure Vessel Co., Ltd.; Shandong Province Building High Pressure Vessel Limited Company; Sichuan Mingchuan Chengyu Co., Ltd.; and Zhuolu High Pressure Vessel Co., Ltd.</P>
        </FTNT>
        <HD SOURCE="HD1">Continuation of Suspension of Liquidation</HD>
        <P>In accordance with section 735(c)(1)(B) of the Act, the Department will instruct U.S. Customs and Border Protection (“CBP”) to continue to suspend liquidation of all imports of merchandise subject to the investigation entered or withdrawn from warehouse, for consumption for the PRC-wide entity and the Separate Rate Companies on or after December 15, 2011. The Department will instruct CBP to require a cash deposit or the posting of a bond equal to the weighted-average amount by which the normal value exceeds U.S. price, as follows: (1) The rate for the exporter/producer combinations listed in the chart above will be the rate we have determined in this final determination; (2) for all PRC exporters of subject merchandise which have not received their own rate, the cash-deposit rate will be the PRC-wide rate; and (3) for all non-PRC exporters of subject merchandise which have not received their own rate, the cash-deposit rate will be the rate applicable to the PRC exporter/producer combination that supplied that non-PRC exporter. The suspension of liquidation instructions will remain in effect until further notice.</P>
        <HD SOURCE="HD1">ITC Notification</HD>
        <P>In accordance with section 735(d) of the Act, we have notified the International Trade Commission (“ITC”) of our final determination of sales at LTFV. As our final determination is affirmative, in accordance with section 735(b)(2) of the Act, the ITC will, within 45 days, determine whether the domestic industry in the United States is materially injured or threatened with material injury, by reason of imports or sales (or the likelihood of sales) for importation of the subject merchandise. If the ITC determines that material injury or threat of material injury does not exist, the proceeding will be terminated and all securities posted will be refunded or canceled. If the ITC determines that such injury does exist, the Department will issue an antidumping duty order directing CBP to collect cash deposits for antidumping duties due on all imports of the subject merchandise entered or withdrawn from warehouse for consumption on or after the effective date of the suspension of liquidation.</P>
        <HD SOURCE="HD1">Notification Regarding APO</HD>
        <P>This notice also serves as a reminder to the parties subject to administrative protective order (“APO”) of their responsibility concerning the disposition of proprietary information disclosed under APO in accordance with 19 CFR 351.305. Timely notification of return or destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and the terms of an APO is a sanctionable violation.</P>
        <P>This determination and notice are issued and published in accordance with sections 735(d) and 777(i)(1) of the Act.</P>
        <SIG>
          <DATED>Dated: April 30, 2012.</DATED>
          <NAME>Ronald K. Lorentzen,</NAME>
          <TITLE>Acting Assistant Secretaryfor Import Administration.</TITLE>
        </SIG>
        <APPENDIX>
          <HD SOURCE="HED">Appendix I</HD>
          <HD SOURCE="HD1">General Issues</HD>
          <FP SOURCE="FP-2">Comment I: Selection of Surrogate Country</FP>
          <FP SOURCE="FP-2">Comment II: Surrogate Values</FP>
          <FP SOURCE="FP1-2">A. Selection of Surrogate Financial Ratios</FP>
          <FP SOURCE="FP1-2">B. Truck Freight</FP>
          <FP SOURCE="FP1-2">C. Labor</FP>
          <FP SOURCE="FP-2">Comment III: Double Remedy</FP>
          <FP SOURCE="FP-2">Comment IV: Targeted Dumping Methodology</FP>
          <FP SOURCE="FP1-2">A. General Department Targeted Dumping Methodology</FP>
          <FP SOURCE="FP1-2">B. Average to Transaction Methodology</FP>
          <FP SOURCE="FP1-2">C. Zeroing</FP>
          <HD SOURCE="HD1">Company-Specific Issues</HD>
          <FP SOURCE="FP-2">Comment V: BTIC</FP>
          <FP SOURCE="FP1-2">A. Targeted Dumping—Clerical Error Allegation</FP>
          <FP SOURCE="FP1-2">B. Cash Deposit Instructions</FP>
          <FP SOURCE="FP-2">Comment VI: Jindun's Voluntary Respondent Status</FP>
          
        </APPENDIX>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10952 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="26743"/>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>International Trade Administration</SUBAGY>
        <SUBJECT>The Manufacturing Council: Work Session of the Manufacturing Council</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>International Trade Administration, U.S. Department of Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of an Open Work Session.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>This notice sets forth the schedule and agenda for an open work session of the Manufacturing Council (Council). The agenda may change to accommodate Council work. The final agenda will be posted on the Department of Commerce Web site for the Council at<E T="03">http://trade.gov/manufacturingcouncil.</E>
          </P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>May 10, 2012, 10:00 a.m.-12:00 p.m. Central Daylight Time (CDT).</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>The work session will be held at Freescale Austin Technology and Manufacturing Center, 3501 Ed Bluestein Boulevard, Austin, Texas. All guests are requested to register in advance. This session will be physically accessible to people with disabilities. Seating is limited and is not guaranteed. Requests for sign language interpretation, other auxiliary aids, or pre-registration, should be submitted no later than May 7, 2012, to Jennifer Pilat, the Manufacturing Council, Room 4043, 1401 Constitution Avenue NW., Washington, DC 20230, telephone 202-482-4501,<E T="03">OACIE@trade.gov.</E>Last minute requests will be accepted, but may be impossible to fill.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Jennifer Pilat, the Manufacturing Council, Room 4043, 1401 Constitution Avenue NW., Washington, DC 20230, telephone: 202-482-4501, email:<E T="03">OACIE@trade.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <P SOURCE="NPAR">
          <E T="03">Background:</E>The Council was re-chartered on April 5, 2012 to advise the Secretary of Commerce on matters relating to the U.S. manufacturing industry.</P>
        <P>
          <E T="03">Topics To Be Considered:</E>The Council will be conducting work regarding possibly advising the Secretary regarding the Trans-Pacific Partnership Agreement negotiations and energy policy and hear updates on the work being conducted by the Council's subcommittees. The Council will also be briefed by the ex-officio members present representing the Secretaries of the Treasury, Labor, and Energy on their respective agency's work in the areas of past Council recommendations.</P>
        <P>No time will be available for oral comments from members of the public attending the session. Any member of the public may submit pertinent written comments concerning the Council's affairs at any time before or after the session.</P>
        <P>Comments may be submitted to Jennifer Pilat at the contact information indicated above. To be considered during the session, comments must be received no later than 5:00 p.m. Eastern Time on May 7, 2012, to ensure transmission to the Council prior to the session.</P>
        <P>Comments received after that date will be distributed to the members but may not be considered at the session.</P>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Jennifer Pilat,</NAME>
          <TITLE>Executive Secretary, The Manufacturing Council.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10980 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-DR-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <SUBJECT>Proposed Information Collection; Comment Request; Atlantic Highly Migratory Species Tournament Registration and Reporting</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>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>The Department of Commerce, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of 1995.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments must be submitted on or before July 6, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Direct all written comments to Jennifer Jessup, Departmental Paperwork Clearance Officer, Department of Commerce, Room 6616, 14th and Constitution Avenue NW, Washington, DC 20230 (or via the Internet at<E T="03">JJessup@doc.gov</E>).</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Requests for additional information or copies of the information collection instrument and instructions should be directed to Katie Davis, (727) 824-5399 or<E T="03">Katie.Davis@noaa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Abstract</HD>
        <P>This request is for extension of a currently approved information collection.</P>

        <P>Under the provisions of the Magnuson-Stevens Fishery Conservation and Management Act (16 U.S.C. 1801<E T="03">et seq.</E>), NOAA's National Marine Fisheries Service (NMFS) is responsible for management of the nation's marine fisheries. Existing regulations require operators of tournaments involving Atlantic highly migratory species (HMS), specifically Atlantic swordfish, sharks, billfish, and tunas, to register four weeks in advance of the tournament. Operators must provide contact information and the tournament's date(s), location(s), and target HMS. If selected by NMFS, operators are required to submit an HMS tournament summary report within seven days after tournament fishing has ended. Most of the catch data in the summary report is routinely collected in the course of regular tournament operations. NMFS uses the data to estimate the total annual catch of HMS and the impact of tournament operations in relation to other types of fishing activities. In addition, HMS tournament registration provides a method for tournament operators to request educational and regulatory outreach materials from NMFS.</P>
        <HD SOURCE="HD1">II. Method of Collection</HD>
        <P>Operators have a choice of either electronic or paper forms. Methods of submittal include email of electronic forms, and mail and facsimile transmission of paper forms.</P>
        <HD SOURCE="HD1">III. Data</HD>
        <P>
          <E T="03">OMB Control Number:</E>0648-0323.</P>
        <P>
          <E T="03">Form Number:</E>None.</P>
        <P>
          <E T="03">Type of Review:</E>Regular submission (extension of a current information collection).</P>
        <P>
          <E T="03">Affected Public:</E>Not-for-profit institutions; business or other for-profit organizations.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>300.</P>
        <P>
          <E T="03">Estimated Time Per Response:</E>Tournament registration, 2 minutes; tournament summary reporting, 20 minutes.</P>
        <P>
          <E T="03">Estimated Total Annual Burden Hours:</E>110.</P>
        <P>
          <E T="03">Estimated Total Annual Cost to Public:</E>$135 in recordkeeping/reporting costs.</P>
        <HD SOURCE="HD1">IV. Request for Comments</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<PRTPAGE P="26744"/>whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden (including hours and cost) of the proposed collection of information; (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 respondents, including through the use of automated collection techniques or other forms of information technology.</P>
        <P>Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval of this information collection; they also will become a matter of public record.</P>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Gwellnar Banks,</NAME>
          <TITLE>Management Analyst, Office of the Chief Information Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10907 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <RIN>RIN 0648-XC017</RIN>
        <SUBJECT>Fishing Capacity Reduction Program for the Southeast Alaska Purse Seine Salmon Fishery</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 of reduction payment tender of Southeast Alaska purse seine salmon permits.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The National Marine Fisheries Service published regulations implementing a fishing capacity reduction program in the Southeast Alaska purse seine salmon fishery. The program authorizes NMFS to make payments to permit holders who voluntarily relinquish their fishing permits. The Southeast Revitalization Association (SRA) conducted a bid selection process accepting sixty-four bids to remove Southeast Alaska purse seine salmon permits. It then submitted a reduction plan to NMFS to implement the program. NMFS conducted a referendum which approved the reduction loan repayment fees of $13,133,030 which post-reduction harvesters will repay over a 40-year period removing 64 permits. Accordingly, NMFS is preparing to tender reduction payments to the accepted bidders.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The public has until June 6, 2012 to inform NMFS of any holding, owning, or retaining claims that conflict with the representations of bids as presented by the SRA.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Send comments about this notice to Paul Marx, Chief, Financial Services Division, NMFS, Attn: SE Alaska Purse Seine Salmon Buyback, 1315 East-West Highway, Silver Spring, MD 20910 (see<E T="02">FOR FURTHER INFORMATION CONTACT</E>).</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Michael A. Sturtevant at (301) 427-8799, fax (301) 713-1306, or<E T="03">michael.a.sturtevant@noaa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>The Southeast Alaska purse seine salmon fishery is a commercial fishery in Alaska state waters and adjacent Federal waters. It encompasses the commercial taking of salmon with purse seine gear, and participation is limited to fishermen designated by the Alaska Commercial Fisheries Entry Commission (CFEC).</P>
        <P>NMFS published proposed program regulations on May 23, 2011 (76 FR 29707), and final program regulations on October 6, 2011 (76 FR 61986), to implement the reduction program. Subsequently, the Southeast Revitalization Association submitted a capacity reduction plan to NMFS. NMFS approved the plan on February 24, 2012. NMFS published the list of eligible voters on March 1, 2012 (77 FR 12568) and the notice of referendum period on March 29, 2012 (77 FR 19004). Interested persons should review these for further program details.</P>
        <HD SOURCE="HD1">II. Present Status</HD>
        <P>NMFS conducted a referendum to determine the industry's willingness to repay a fishing capacity reduction loan to purchase the permits identified in the reduction plan. NMFS mailed ballots to 379 permanent permit holders in the fishery designated as S01A by CFEC who were eligible to vote in the referendum. The voting period opened on March 30, 2012, and closed on April 30, 2012. NMFS received 269 timely and valid votes. 215 of the votes approved the fees. This exceeded the majority of permit holders (190) required for industry fee system approval. Therefore, the referendum is deemed successful and permit holders are deemed to have approved the industry fee system. Accordingly, the reduction contracts are in full force and effect and NMFS is now preparing to tender and disburse reduction payments to selected bidders.</P>
        <HD SOURCE="HD1">III. Purpose</HD>
        <P>NMFS publishes this notice to inform the public before tendering reduction payments to the 64 accepted bidders. Upon receiving notice from CFEC that the permit has been relinquished and is no longer valid, NMFS will tender reduction payments on or about June 6, 2012. When NMFS tenders a reduction payment to a selected bidder, the selected bidder must permanently stop all further fishing represented by each reduction permit the bidder has relinquished. The selected bidder, in accordance with section 5 of the relinquishment contract, must notify all creditors or other parties with security interests in the reduction permit, that they have entered into the relinquishment contract.</P>
        <P>This notice provides the public (including creditors or other parties) 30 days from publication of this notice to advise NMFS in writing of any holding, owning, or retaining claims that conflict with the representations of bids as presented by the SRA.</P>
        <HD SOURCE="HD1">IV. Selected Bidders and Permits</HD>
        <P>The table below lists the 64 permit holders who will receive reduction payments when NMFS receives confirmation from CFEC that the specified permits have been relinquished.</P>
        <GPOTABLE CDEF="s20,r20,xls50" COLS="3" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Last name</CHED>
            <CHED H="1">First name</CHED>
            <CHED H="1">Permit No.</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Alfieri</ENT>
            <ENT>Joe</ENT>
            <ENT>S01A60791I</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Alfieri</ENT>
            <ENT>Anthony</ENT>
            <ENT>S01A55646M</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Barrett</ENT>
            <ENT>Davis</ENT>
            <ENT>S01A58501W</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Beritich</ENT>
            <ENT>Mitchell</ENT>
            <ENT>S01A58923M</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Bill</ENT>
            <ENT>David</ENT>
            <ENT>S01A58338U</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Blair</ENT>
            <ENT>Andrew</ENT>
            <ENT>S01A59085F</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Botsford</ENT>
            <ENT>Wallace</ENT>
            <ENT>S01A63175B</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Buschmann</ENT>
            <ENT>Ronn</ENT>
            <ENT>S01A55479D</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Christensen</ENT>
            <ENT>Dale</ENT>
            <ENT>S01A60803V</ENT>
          </ROW>
          <ROW>
            <ENT I="01">DeGroen</ENT>
            <ENT>Johnny</ENT>
            <ENT>S01A58505S</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Demmert</ENT>
            <ENT>Nicholas</ENT>
            <ENT>S01A56948W</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Dontos</ENT>
            <ENT>Larry</ENT>
            <ENT>S01A59705K</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Fanning</ENT>
            <ENT>Christine</ENT>
            <ENT>S01A60909J</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Finney</ENT>
            <ENT>Paul</ENT>
            <ENT>S01A64933S</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Gruenheit</ENT>
            <ENT>Michael</ENT>
            <ENT>S01A55083V</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Haldane</ENT>
            <ENT>Robert</ENT>
            <ENT>S01A56620L</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Haltiner</ENT>
            <ENT>Fred</ENT>
            <ENT>S01A55617L</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Hansen</ENT>
            <ENT>William</ENT>
            <ENT>S01A55442A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Hanson</ENT>
            <ENT>Jeff</ENT>
            <ENT>S01A57976</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Haynes</ENT>
            <ENT>Bradley</ENT>
            <ENT>S01A574950</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Jensen</ENT>
            <ENT>Douglas</ENT>
            <ENT>S01A59714N</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Johns</ENT>
            <ENT>Justna</ENT>
            <ENT>S01A55403</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Jolibois</ENT>
            <ENT>Timothy</ENT>
            <ENT>S01A56018A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Jurlin</ENT>
            <ENT>Marie</ENT>
            <ENT>S01A58547R</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Kohlase</ENT>
            <ENT>Ernest</ENT>
            <ENT>S01A56199V</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Krieger</ENT>
            <ENT>Kenneth</ENT>
            <ENT>S01A59613M</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Krigbaum</ENT>
            <ENT>Michael</ENT>
            <ENT>S01A58031W</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Kvernvik</ENT>
            <ENT>Carolyn</ENT>
            <ENT>S01A55231R</ENT>
          </ROW>
          <ROW>
            <ENT I="01">MacDonald</ENT>
            <ENT>Clifford</ENT>
            <ENT>S01A55545L</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Mann</ENT>
            <ENT>Bruce</ENT>
            <ENT>S01A56187</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Manos</ENT>
            <ENT>Andrew</ENT>
            <ENT>S01A59222I</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Manos</ENT>
            <ENT>Thomas</ENT>
            <ENT>S01A60642C</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Maricich</ENT>
            <ENT>Timothy</ENT>
            <ENT>S01A59569W</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Markusen</ENT>
            <ENT>Kenneth</ENT>
            <ENT>S01A55584K</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="26745"/>
            <ENT I="01">Marrese</ENT>
            <ENT>Andrew</ENT>
            <ENT>S01A57909W</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Marvin-Denkinger</ENT>
            <ENT>Victoria</ENT>
            <ENT>S01A58429X</ENT>
          </ROW>
          <ROW>
            <ENT I="01">McGee</ENT>
            <ENT>Gary</ENT>
            <ENT>S01A56559</ENT>
          </ROW>
          <ROW>
            <ENT I="01">McLean</ENT>
            <ENT>John</ENT>
            <ENT>S01A56270P</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Menten</ENT>
            <ENT>Erik</ENT>
            <ENT>S01A57726X</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Michael</ENT>
            <ENT>Mercury</ENT>
            <ENT>S01A55386C</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Nash</ENT>
            <ENT>Paul</ENT>
            <ENT>S01A57907M</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Nugent</ENT>
            <ENT>Matthew</ENT>
            <ENT>S01A55689G</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Olney</ENT>
            <ENT>Virginia</ENT>
            <ENT>S01A57720</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Peterman</ENT>
            <ENT>Chad</ENT>
            <ENT>S01A55986F</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Pfundt</ENT>
            <ENT>Michele</ENT>
            <ENT>S01A56392F</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Reifenstuhl</ENT>
            <ENT>Ivan</ENT>
            <ENT>S01A55171A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Reimnitz</ENT>
            <ENT>Hartmut</ENT>
            <ENT>S01A578995</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Rocheleau</ENT>
            <ENT>Rick</ENT>
            <ENT>S01A58478</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Schonberg</ENT>
            <ENT>Peter</ENT>
            <ENT>S01A56601I</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Schonberg</ENT>
            <ENT>Mart</ENT>
            <ENT>S01A56882A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Scudder</ENT>
            <ENT>Bradley</ENT>
            <ENT>S01A56000N</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Selivanoff</ENT>
            <ENT>Douglas</ENT>
            <ENT>S01A57856A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Sorensen</ENT>
            <ENT>Paige</ENT>
            <ENT>S01A58511U</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Spearin</ENT>
            <ENT>James</ENT>
            <ENT>S01A59372G</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Suydam</ENT>
            <ENT>Antril</ENT>
            <ENT>S01A57910N</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Svensson</ENT>
            <ENT>John</ENT>
            <ENT>S01A56492N</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Tarabochia</ENT>
            <ENT>Dominick</ENT>
            <ENT>S01A56600P</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Thorstenson</ENT>
            <ENT>Peder</ENT>
            <ENT>S01A59806J</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Veerhusen</ENT>
            <ENT>Daniel</ENT>
            <ENT>S01A56638X</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Wallace</ENT>
            <ENT>Bruce</ENT>
            <ENT>S01A55827B</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Wamser</ENT>
            <ENT>William</ENT>
            <ENT>S01A60071B</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Wills</ENT>
            <ENT>Charles</ENT>
            <ENT>S01A58070V</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Zuanich</ENT>
            <ENT>Michelle</ENT>
            <ENT>S01A57849F</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Zuanich</ENT>
            <ENT>Michelle</ENT>
            <ENT>S01A568811</ENT>
          </ROW>
        </GPOTABLE>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Lindsay Fullenkamp,</NAME>
          <TITLE>Acting Director, Office of Management and Budget,National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10984 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <RIN>RIN 0648-XC016</RIN>
        <SUBJECT>Marine Fisheries Advisory Committee Meeting</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 of open public meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>This notice sets forth the schedule and proposed agenda of a forthcoming meeting of the Marine Fisheries Advisory Committee (MAFAC). The members will discuss and provide advice on issues outlined under<E T="02">SUPPLEMENTARY INFORMATION</E>below.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The meeting will be held May 22-24, 2012, from 8 a.m. to 5 p.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The meeting will be held at the Sheraton Seattle Hotel, 1400 Sixth Avenue, Seattle, WA 98101; 206-447-5564.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Mark Holliday, MAFAC Executive Director; (301) 427-8004; email:<E T="03">Mark.Holliday@noaa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>As required by section 10(a)(2) of the Federal Advisory Committee Act, 5 U.S.C. App. 2, notice is hereby given of a meeting of MAFAC. The MAFAC was established by the Secretary of Commerce (Secretary), and, since 1971, advises the Secretary on all living marine resource matters that are the responsibility of the Department of Commerce. The complete charter and summaries of prior meetings are located online at<E T="03">http://www.nmfs.noaa.gov/ocs/mafac/.</E>
        </P>
        <HD SOURCE="HD1">Matters To Be Considered</HD>
        <P>This agenda is subject to change.</P>

        <P>The meeting is convened to hear presentations and discuss policies and guidance on the following topics: NMFS budget and legislative issues, aquaculture policy implementation and the Washington State aquaculture initiative, National Standard 1 advanced notice of proposed rulemaking, fisheries certification and sustainability, working waterfronts, revisions to MAFAC's<E T="03">Vision 2020</E>report, and current protected resources issues. Updates will be presented on Gulf of Mexico restoration activities, National Ocean Policy, recreational fisheries initiatives, and outlooks for 2012 regulatory and science activities. The meeting will include discussion of various MAFAC administrative and organizational matters and meetings of the standing subcommittees.</P>
        <HD SOURCE="HD1">Special Accommodations</HD>
        <P>These meetings are physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Mark Holliday, MAFAC Executive Director; 301-427-8004 by May 16, 2012.</P>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Paul Doremus,</NAME>
          <TITLE>Deputy Assistant Administrator for Operations, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10963 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <SUBJECT>Gulf of Mexico Fishery Management Council; Public Meeting</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>Council to convene public meetings.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Gulf of Mexico Fishery Management Council will convene a Web based meeting of the ABC Control Rule Working Group.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The webinar meeting will convene on Thursday, May 24, 2012. The webinar will begin at 9 a.m. and is expected end by 12 noon, Eastern time.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>The webinar will be accessible via Internet. Please go to the Gulf of Mexico Fishery Management Council's Web site at<E T="03">www.gulfcouncil.org</E>for instructions.</P>
          <P>
            <E T="03">Council address:</E>Gulf of Mexico Fishery Management Council, 2203 N. Lois Avenue, Suite 1100, Tampa, FL 33607.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Steven Atran, Population Dynamics Statistician; Gulf of Mexico Fishery Management Council; telephone: (813) 348-1630.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The ABC Control Rule Working Group will meet to review the results of applying the Ralston et al. (2011) method of calculating ABC when the variances used are computed from GOM stocks, to review discussion on linking Tier 3 ABCs to data collection actions, continue reviews and edits to the ABC control rule, and decide what recommendation to carry forward to the Scientific and Statistical Committee for its June 2012 meeting.</P>

        <P>Copies of the agenda and other related materials can be obtained by calling (813) 348-1630. Materials will also be available to download from the ABC Control Rule Working Group folder of the Council's FTP site, which is accessible from the Quick Links section of the Council Web site (<E T="03">http://www.gulfcouncil.org</E>).</P>

        <P>Although other non-emergency issues not on the agenda may come before the ABC Control Rule Working Group for discussion, in accordance with the Magnuson-Stevens Fishery Conservation and Management Act, those issues may not be the subject of formal action during this meeting. Actions of the Working Group will be<PRTPAGE P="26746"/>restricted to those issues specifically identified in the agenda and any issues arising after publication of this notice that require emergency action under Section 305(c) of the Magnuson-Stevens Fishery Conservation and Management Act, provided the public has been notified of the Council's intent to take action to address the emergency.</P>
        <HD SOURCE="HD1">Special Accommodations</HD>

        <P>This webinars are accessible to people with disabilities. For assistance with any of our webinars contact Kathy Pereira at the Council (see<E T="02">ADDRESSES</E>) at least 5 working days prior to the webinar.</P>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Tracey L. Thompson,</NAME>
          <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10899 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <SUBJECT>Fisheries of the Caribbean; Southeast Data, Assessment, and Review (SEDAR); Public Meetings</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 of SEDAR Data Scoping, Assessment, and Review Workshops for Caribbean blue tang and queen triggerfish.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The SEDAR assessments of the Caribbean stocks of blue tang and queen triggerfish will consist of a series of workshops: three Data scoping Workshops, an Assessment Workshop, and a Review Workshop. See<E T="02">SUPPLEMENTARY INFORMATION</E>.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>

          <P>The Data Scoping Workshops will take place July 17-19, 2012; the Assessment Workshop will take place October 16-18, 2012; and the Review Workshop will take place February 4-7, 2013. See<E T="02">SUPPLEMENTARY INFORMATION</E>.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>A series of Data Scoping Workshops will be held throughout the U.S. Caribbean. The location information for each workshop is included in the table below:</P>
        </ADD>
        <GPOTABLE CDEF="s50,r50,r50,r50" COLS="4" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1">Data Scoping—STX</CHED>
            <CHED H="1">Data Scoping—STT</CHED>
            <CHED H="1">Data Scoping—PR</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Start</ENT>
            <ENT>7/17/12 @ 3pm</ENT>
            <ENT>7/18/12 @ 3pm</ENT>
            <ENT>7/19/12 @ 3pm.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">End</ENT>
            <ENT>7/17/12 @ 7pm</ENT>
            <ENT>7/18/12 @ 7pm</ENT>
            <ENT>7/19/12 @ 7pm.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Location</ENT>
            <ENT>The Buccaneer</ENT>
            <ENT>Frenchman's Reef</ENT>
            <ENT>Rincon Beach Hotel.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Address</ENT>
            <ENT>5007 Estate Shoys<LI>St. Croix, USVI</LI>
            </ENT>
            <ENT>5 Estate Bakkeroe,<LI>St. Thomas, USVI</LI>
            </ENT>
            <ENT>Rd 115, Km 5.8,<LI>Anasco, PR.</LI>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">Phone</ENT>
            <ENT>800-255-3881</ENT>
            <ENT>800-228-9290</ENT>
            <ENT>866-589-0009.</ENT>
          </ROW>
        </GPOTABLE>
        <P>The Assessment Workshop will be held at the Courtyard Miami Coconut Grove, 2649 South Bayshore Drive, Miami, FL 33133; telephone: (800) 321-2211. The Review Workshop will be held at the Hotel El Convento, 100 Cristo Street, Old San Juan, PR 00901; telephone: (181) 723-9036.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Julie A. Neer, SEDAR Coordinator, 4055 Faber Place Drive, Suite 201, North Charleston, SC 29405; telephone: (843) 571-4366.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Gulf of Mexico, South Atlantic, and Caribbean Fishery Management Councils, in conjunction with NOAA Fisheries and the Atlantic and Gulf States Marine Fisheries Commissions have implemented the Southeast Data, Assessment and Review (SEDAR) process, a multi-step method for determining the status of fish stocks in the Southeast Region. SEDAR includes three workshops: (1) Data Workshop, (2) Stock Assessment Workshop and (3) Review Workshop. The product of the Data Workshop is a data report which compiles and evaluates potential datasets and recommends which datasets are appropriate for assessment analyses. The product of the Stock Assessment Workshop is a stock assessment report which describes the fisheries, evaluates the status of the stock, estimates biological benchmarks, projects future population conditions, and recommends research and monitoring needs. The assessment is independently peer reviewed at the Review Workshop. The product of the Review Workshop is a Consensus Summary documenting Panel opinions regarding the strengths and weaknesses of the stock assessment and input data. Participants for SEDAR Workshops are appointed by the Gulf of Mexico, South Atlantic, and Caribbean Fishery Management Councils and NOAA Fisheries Southeast Regional Office and Southeast Fisheries Science Center. Participants include data collectors and database managers; stock assessment scientists, biologists, and researchers; constituency representatives including fishermen, environmentalists, and NGO's; International experts; and staff of Councils, Commissions, and state and federal agencies.</P>
        <P>SEDAR 30 Workshop Schedule:</P>
        <HD SOURCE="HD1">July 17-19, 2012; SEDAR 30 Data Scoping Workshops</HD>
        <P>July 17-19, 2012: 3 p.m.-7 p.m.</P>
        <P>An assessment data set and associated documentation will be developed during the Data Scoping Workshops. Participants will evaluate available data and select appropriate sources for providing information on life history characteristics, catch statistics, discard estimates, length and age composition, and fishery dependent and fishery independent measures of stock abundance.</P>
        <HD SOURCE="HD1">October 16-18, 2012, 2011; SEDAR 30 Assessment Workshop</HD>
        <P>October 16-18, 2012: 9 a.m.-8 p.m.</P>
        <P>Using datasets provided by the Data Scoping Workshops, participants will develop population models to evaluate stock status, estimate population benchmarks and stock status criteria, and project future conditions. Participants will recommend the most appropriate methods and configurations for determining stock status and estimating population parameters. Participants will prepare a workshop report, compare and contrast various assessment approaches, and determine whether the assessments are adequate for submission to the review panel.</P>
        <HD SOURCE="HD1">February 4-7, 2013; SEDAR 30 Review Workshop</HD>
        <P>February 4, 2013: 1 p.m.-8 p.m.; February 5-7, 2013: 8 a.m.-8 p.m.</P>

        <P>The Review Workshop is an independent peer review of the assessment developed during the Data and Assessment Workshops. Workshop Panelists will review the assessment and document their comments and recommendations in a Consensus Summary.<PRTPAGE P="26747"/>
        </P>
        <P>The established times may be adjusted as necessary to accommodate the timely completion of discussion relevant to the assessment process. Such adjustments may result in the meeting being extended from, or completed prior to the time established by this notice.</P>
        <HD SOURCE="HD1">Special Accommodations</HD>

        <P>These meetings are physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to the Council office (see<E T="02">ADDRESSES</E>) at least 10 business days prior to each workshop.</P>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Tracey L. Thompson,</NAME>
          <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10900 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <RIN>RIN 0648-XA288</RIN>
        <SUBJECT>Marine Mammals; File No. 15748</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; receipt of application for permit amendment.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Notice is hereby given that the Alaska SeaLife Center (ASLC), Seward, AK, has applied for an amendment to Scientific Research Permit No. 15748.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written, telefaxed, or email comments must be received on or before June 6, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>The application and related documents are available for review by selecting “Records Open for Public Comment” from the<E T="03">Features</E>box on the Applications and Permits for Protected Species home page,<E T="03">https://apps.nmfs.noaa.gov,</E>and then selecting File No. 15748 from the list of available applications.</P>
          <P>These documents are also available upon written request or by appointment in the following offices:</P>
          <P>Permits and Conservation Division, Office of Protected Resources, NMFS, 1315 East-West Highway, Room 13705, Silver Spring, MD 20910; phone (301) 427-8401; fax (301) 713-0376; and</P>
          <P>Southwest Region, NMFS, 501 West Ocean Blvd., Suite 4200, Long Beach, CA 90802-4213; phone (562) 980-4001; fax (562) 980-4018.</P>

          <P>Written comments on this application should be submitted to the Chief, Permits and Conservation Division, at the address listed above. Comments may also be submitted by facsimile to (301) 713-0376, or by email to<E T="03">NMFS.Pr1Comments@noaa.gov.</E>Please include the File No. in the subject line of the email comment.</P>
          <P>Those individuals requesting a public hearing should submit a written request to the Chief, Permits and Conservation Division at the address listed above. The request should set forth the specific reasons why a hearing on this application would be appropriate.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Joselyd Garcia-Reyes or Tammy Adams, (301) 427-8401.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>The subject amendment to Permit No. 15748 is requested under the authority of the Marine Mammal Protection Act of 1972, as amended (16 U.S.C. 1361<E T="03">et seq.</E>), and the regulations governing the taking and importing of marine mammals (50 CFR part 216).</P>

        <P>Permit No. 15748, issued on May 25, 2011 (76 FR 31942), authorizes the permit holder to capture and harass free-living Weddell seals (<E T="03">Leptonychotes weddellii</E>) in McMurdo Sound and along the shore of Ross Island, Antarctica to study thermoregulation. The research involves capture and restraint of adult females and pups/juveniles of either sex for attachment of scientific instruments, morphometric measurements, ultrasound, and tissue sampling. Harassment of additional seals in the vicinity of captured animals is also authorized, as is research-related mortality. Tissue samples collected may be exported from Antarctica for analysis in the U.S. The permit is valid through August 30, 2015.</P>
        <P>The permit holder is requesting the permit be amended to include changes to the terms and conditions of the permit related to numbers of animals taken and manner of taking to include: increasing takes for the deployment of instrumentation on weaned pups/juveniles from 20 over the life of the permit to 35 over the life of the permit; increasing the number of takes per animal of weaned pups/juveniles and adult females from 2 to 3; adding nasal, oral, and rectal swab collection (one of each per animal) in weaned pups/juveniles and adult females; adding the use of spray lidocaine or similar agent; adding stable isotope analysis to compare stable isotope values of Weddell seals in the Ross Sea in the early 1900s to today; and adding an influenza A analysis using the requested swab collection to understand the exposure of pathogens to Antarctic marine mammals.</P>

        <P>In compliance with the National Environmental Policy Act of 1969 (42 U.S.C. 4321<E T="03">et seq.</E>), an initial determination has been made that the activity proposed is categorically excluded from the requirement to prepare an environmental assessment or environmental impact statement.</P>
        <P>Concurrent with the publication of this notice in the<E T="04">Federal Register</E>, NMFS is forwarding copies of this application to the Marine Mammal Commission and its Committee of Scientific Advisors.</P>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Tammy C. Adams,</NAME>
          <TITLE>Acting Chief, Permits and Conservation Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10966 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <SUBJECT>Defense Science Board; Notice of Advisory Committee Meetings</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of Defense.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of Advisory Committee Meetings.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Defense Science Board will meet in closed session on May 23-24, 2012, at the Pentagon, Room 3E863, Washington, DC. The mission of the Defense Science Board is to advise the Secretary of Defense and the Under Secretary of Defense for Acquisition, Technology &amp; Logistics on scientific and technical matters as they affect the perceived needs of the Department of Defense. At this meeting, the Board will discuss interim finding and recommendations resulting from ongoing Task Force activities. The Board will also discuss plans for future consideration of scientific and technical aspects of specific strategies, tactics, and policies as they may affect the U.S. national defense posture and homeland security.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>May 23-24, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The Pentagon, Room 3E863, Washington, DC.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Ms. Debra Rose, Executive Officer, Defense Science Board, 3140 Defense Pentagon, Room 3B888A, Washington, DC 20301-3140, via email at<E T="03">debra.rose@osd.mil,</E>or via phone at (703) 571-0084.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>In accordance with section 10(d) of the Federal Advisory Committee Act, Public<PRTPAGE P="26748"/>Law 92-463, as amended (5 U.S.C. App. 2) and 41 CFR 102-3.155, the Department of Defense has determined that these Defense Science Board quarterly meetings will be closed to the public. Specifically, the Under Secretary of Defense (Acquisition, Technology and Logistics), with the coordination of the DoD Office of General Counsel, has determined in writing that all sessions of these meetings will be closed to the public because they will be concerned throughout with matters listed in 5 U.S.C. 552b(c)(1) and (4). Interested persons may submit a written statement for consideration by the Defense Science Board. Individuals submitting a written statement must submit their statement to the Designated Federal Official at the address detailed in<E T="02">FOR FURTHER INFORMATION CONTACT</E>, at any point; however, if a written statement is not received at least 10 calendar days prior to the meeting, which is the subject of this notice, then it may not be provided to or considered by the Defense Science Board. The Designated Federal Official will review all timely submissions with the Defense Science Board Chairperson, and ensure they are provided to members of the Defense Science Board before the meeting that is the subject of this notice.</P>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Aaron Siegel,</NAME>
          <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10844 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <SUBJECT>Department of Defense Wage Committee; Notice of Closed Meetings</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of closed meetings.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Pursuant to the provisions of section 10 of Public Law 92-463, the Federal Advisory Committee Act, notice is hereby given that closed meeting of the Department of Defense Wage Committee will be held.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Tuesday, May 29, 2012, at 10:00 a.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>1400 Key Boulevard, Level A, Room A101, Rosslyn, Virginia 22209.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Additional information concerning the meetings may be obtained by writing to the Chairman, Department of Defense Wage Committee, 4000 Defense Pentagon, Washington, DC 20301-4000.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Under the provisions of section 10(d) of Public Law 92-463, the Department of Defense has determined that the meetings meet the criteria to close meetings to the public because the matters to be considered are related to internal rules and practices of the Department of Defense and the detailed wage data to be considered were obtained from officials of private establishments with a guarantee that the data will be held in confidence.</P>
        <P>However, members of the public who may wish to do so are invited to submit material in writing to the chairman concerning matters believed to be deserving of the Committee's attention.</P>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Aaron Siegel,</NAME>
          <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10920 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <SUBJECT>Department of Defense Wage Committee; Notice of Closed Meetings</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of closed meetings.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Pursuant to the provisions of section 10 of Public Law 92-463, the Federal Advisory Committee Act, notice is hereby given that a closed meeting of the Department of Defense Wage Committee will be held.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Tuesday, June 12, 2012, at 10:00 a.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>1400 Key Boulevard, Level A, Room A101, Rosslyn, Virginia 22209.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Additional information concerning the meetings may be obtained by writing to the Chairman, Department of Defense Wage Committee, 4000 Defense Pentagon, Washington, DC 20301-4000.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Under the provisions of section 10(d) of Public Law 92-463, the Department of Defense has determined that the meetings meet the criteria to close meetings to the public because the matters to be considered are related to internal rules and practices of the Department of Defense and the detailed wage data to be considered were obtained from officials of private establishments with a guarantee that the data will be held in confidence.</P>
        <P>However, members of the public who may wish to do so are invited to submit material in writing to the chairman concerning matters believed to be deserving of the Committee's attention.</P>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Aaron Siegel,</NAME>
          <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10921 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <SUBJECT>Renewal of Department of Defense Federal Advisory Committees</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Renewal of Federal Advisory Committee.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Under the provisions of 10 U.S.C. 2166(e), the Federal Advisory Committee Act of 1972 (5 U.S.C. Appendix), the Government in the Sunshine Act of 1976 (5 U.S.C. 552b), and 41 CFR 102-3.50(a), the Department of Defense gives notice that it is renewing the charter for the Chief of Engineers Environmental Advisory Board (hereafter referred to as “the Board”).</P>
          <P>The Board shall provide independent advice and recommendations on matters relating to environmental issues facing the U.S. Army Corps of Engineers.</P>
          <P>The Board shall report to the Secretary of Defense, through the Secretary of the Army, the Assistant Secretary of the Army (Civil Works), and the U.S. Army Corps of Engineers.</P>
          <P>The Board shall be composed of not more than ten members who are eminent authorities in the field of natural (e.g. biological, ecological), social (e.g. anthropologist, community planner), and related sciences.</P>
          <P>All Board members shall be appointed by the Secretary of Defense and all member appointments require annual renewal by the Secretary of Defense. The Secretary of Defense may approve the appointments of Board members for three year terms of service; however, no member, unless authorized by the Secretary of Defense may serve more than two consecutive terms of service. This same term of service limitation also applies to any DoD authorized subcommittees.</P>

          <P>The Board Membership shall select the Board's Chairperson from the total membership. Board Members appointed by the Secretary of Defense, who are not full-time Federal officers or employees, shall be appointed under the authority of 5 U.S.C. 3109, and serve as special government employees. Board Members shall, with the exception of travel and per diem for official travel, serve without compensation.<PRTPAGE P="26749"/>
          </P>
          <P>Each Board member is appointed to provide advice on behalf of the government on the basis of his or her best judgment without representing any particular point of view and in a manner that is free from conflict of interest.</P>
          <P>The Department, when necessary, and consistent with the Board's mission and DoD policies and procedures, may establish subcommittees deemed necessary to support the Board. Establishment of subcommittees will be based upon a written determination, to include terms of reference, by the Secretary of Defense, the Deputy Secretary of Defense, or the advisory committee's sponsor.</P>
          <P>Such subcommittees shall not work independently of the chartered Board, and shall report all their recommendations and advice to the Board for full deliberation and discussion. Subcommittees have no authority to make decisions on behalf of the chartered Board; nor can any subcommittee or its members update or report directly to the Department of Defense or any Federal officers or employees.</P>
          <P>All subcommittee members shall be appointed in the same manner as the Board members; that is, the Secretary of Defense shall appoint subcommittee members even if the member in question is already a Board member. Subcommittee members, with the approval of the Secretary of Defense, may serve a term of service on the subcommittee of three years; however, no member shall serve more than two consecutive terms of service on the subcommittee.</P>
          <P>Subcommittee members, if not full-time or part-time government employees, shall be appointed to serve as experts and consultants under the authority of 5 U.S.C. 3109, and shall serve as special government employees, whose appointments must be renewed by the Secretary of Defense on an annual basis. With the exception of travel and per diem for official Board related travel, subcommittee members shall serve without compensation.</P>
          <P>All subcommittees operate under the provisions of FACA, the Government in the Sunshine Act of 1976 (5 U.S.C. 552b), governing Federal statutes and regulations, and governing DoD policies/procedures.</P>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Jim Freeman, Deputy Advisory Committee Management Officer for the Department of Defense, 703-692-5952.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Board shall meet at the call of the Designated Federal Officer, in consultation with the Board's Chairperson. The estimated number of Board meetings is two per year.</P>
        <P>In addition, the Designated Federal Officer is required to be in attendance at all Board and subcommittee meetings for the entire duration of each and every meeting; however, in the absence of the Designated Federal Officer, the Alternate Designated Federal Officer shall attend the entire duration of the Board or subcommittee meeting.</P>
        <P>Pursuant to 41 CFR 102-3.105(j) and 102-3.140, the public or interested organizations may submit written statements to Chief of Engineers Environmental Advisory Board membership about the Board's mission and functions. Written statements may be submitted at any time or in response to the stated agenda of planned meeting of the Chief of Engineers Environmental Advisory Board.</P>

        <P>All written statements shall be submitted to the Designated Federal Officer for the Chief of Engineers Environmental Advisory Board, and this individual will ensure that the written statements are provided to the membership for their consideration. Contact information for the Chief of Engineers Environmental Advisory Board Designated Federal Officer can be obtained from the GSA's FACA Database—<E T="03">https://www.fido.gov/facadatabase/public.asp.</E>
        </P>
        <P>The Designated Federal Officer, pursuant to 41 CFR 102-3.150, will announce planned meetings of the Chief of Engineers Environmental Advisory Board. The Designated Federal Officer, at that time, may provide additional guidance on the submission of written statements that are in response to the stated agenda for the planned meeting in question.</P>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Aaron Siegel,</NAME>
          <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10938 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <SUBJECT>Agency Information Collection Extension</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. Department of Energy.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice and Request for Comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Department of Energy (DOE), pursuant to the Paperwork Reduction Act of 1995, intends to extend for three years, an information collection request with the Office of Management and Budget (OMB). Comments are invited on: (a) Whether the extended 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 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 respondents, including through the use of automated collection techniques or other forms of information technology.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments regarding this proposed information collection must be received on or before July 6, 2012. If you anticipate difficulty in submitting comments within that period, contact the person listed below as soon as possible.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Written comments may be sent to: Eva Auman, GC-63, Department of Energy, 1000 Independence Ave. SW., Washington, DC 20585; Fax: 202-586-0971; or email at:<E T="03">eva.auman@hq.doe.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Eva Auman, GC-63, Department of Energy, 1000 Independence Ave. SW., Washington, DC 20585; Fax: 202-586-0971; or email at:<E T="03">eva.auman@hq.doe.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This information collection request contains: (1) OMB No. 1910-5143; (2) Information Collection Request Title: Labor Relations. This information collection was originally titled Legacy Management Labor Relations, but due to transfer of this function to the Office of General Counsel, the title has been shortened to Labor Relations; (3) Type of Review: Renewal; (4) Purpose: To obtain information from the Department of Energy Management and Operation, and Facilities Management Contractors for contract administration, management oversight and cost control; (5) Annual Estimated Number of Respondents: 35; (6) Annual Estimated Number of Total Responses: 35; (7) Annual Estimated Number of Burden Hours: 193; (8) Annual Estimated Reporting and Recordkeeping Cost Burden: $0.00 annually.</P>
        <AUTH>
          <HD SOURCE="HED">Statutory Authority:</HD>
          <P>42 U.S.C. 7254, 7256.</P>
        </AUTH>
        <SIG>
          <PRTPAGE P="26750"/>
          <DATED>Issued in Washington, DC on April 30, 2012<E T="03">.</E>
          </DATED>
          <NAME>Jean S. Stucky,</NAME>
          <TITLE>Assistant General Counsel for Labor and Pension Law, Office of the General Counsel.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10936 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6450-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OPPT-2012-0258; FRL-9344-5]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities; Proposed Collection; Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In compliance with the Paperwork Reduction Act (PRA), this document announces that EPA is planning to submit a request to renew an existing approved Information Collection Request (ICR) to the Office of Management and Budget (OMB). This ICR, entitled: “Notification of Chemical Exports—TSCA Section 12(b)” and identified by EPA ICR No. 0795.14 and OMB Control No. 2070-0030, is scheduled to expire on March 31, 2013. Before submitting the ICR to OMB for review and approval, EPA is soliciting comments on specific aspects of the information collection renewal.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received on or before July 6, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit your comments, identified by docket identification (ID) number EPA-HQ-OPPT-2012-0258, by one of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>. Follow the online instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Document Control Office (7407M), Office of Pollution Prevention and Toxics (OPPT), Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001.</P>
          <P>•<E T="03">Hand Delivery:</E>OPPT Document Control Office (DCO), EPA East, Rm. 6428, 1201 Constitution Ave. NW., Washington, DC. Attention: Docket ID Number EPA-HQ-OPPT-2012-0258. The DCO is open from 8 a.m. to 4 p.m., Monday through Friday, excluding legal holidays. The telephone number for the DCO is (202) 564-8930. Such deliveries are only accepted during the DCO's normal hours of operation, and special arrangements should be made for deliveries of boxed information.</P>
          <P>
            <E T="03">Instructions:</E>Direct your comments to docket ID number EPA-HQ-OPPT-2012-0258. EPA's policy is that all comments received will be included in the docket without change and may be made available online at<E T="03">http://www.regulations.gov,</E>including any personal information provided, unless the comment includes information claimed to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Do not submit information that you consider to be CBI or otherwise protected through regulations.gov or email. The regulations.gov Web site is an “anonymous access” system, which means EPA will not know your identity or contact information unless you provide it in the body of your comment. If you send an email comment directly to EPA without going through regulations.gov, your email address will be automatically captured and included as part of the comment that is placed in the docket and made available on the Internet. If you submit an electronic comment, EPA recommends that you include your name and other contact information in the body of your comment and with any disk or CD-ROM you submit. If EPA cannot read your comment due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comment. Electronic files should avoid the use of special characters, any form of encryption, and be free of any defects or viruses.</P>
          <P>
            <E T="03">Docket:</E>All documents in the docket are listed in the docket index available at<E T="03">http://www.regulations.gov</E>. Although listed in the index, some information is not publicly available, e.g., CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, will be publicly available only in hard copy. Publicly available docket materials are available electronically at<E T="03">http://www.regulations.gov,</E>or, if only available in hard copy, at the OPPT Docket. The OPPT Docket is located in the EPA Docket Center (EPA/DC) at Rm. 3334, EPA West Bldg., 1301 Constitution Ave. NW., Washington, DC. The EPA/DC Public Reading Room hours of operation are 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number of the EPA/DC Public Reading Room is (202) 566-1744, and the telephone number for the OPPT Docket is (202) 566-0280. Docket visitors are required to show photographic identification, pass through a metal detector, and sign the EPA visitor log. All visitor bags are processed through an X-ray machine and subject to search. Visitors will be provided an EPA/DC badge that must be visible at all times in the building and returned upon departure.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>
            <E T="03">For technical information contact:</E>Mike Mattheisen, Chemical Control Division (7405M), Office of Pollution Prevention and Toxics, Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001; telephone number: (202) 564-3077; fax number: (202) 564-4755; email address:<E T="03">mattheisen.mike@epa.gov</E>.</P>

          <P>For general information contact: The TSCA-Hotline, ABVI-Goodwill, 422 South Clinton Ave., Rochester, NY 14620; telephone number: (202) 554-1404; email address:<E T="03">TSCA-Hotline@epa.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. What information is EPA particularly interested in?</HD>
        <P>Pursuant to PRA section 3506(c)(2)(A) (44 U.S.C. 3506(c)(2)(A)), EPA specifically solicits comments and information to enable it to:</P>
        <P>1. 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>2. Evaluate the accuracy of the Agency's estimates of the burden of the proposed collection of information, including the validity of the methodology and assumptions used.</P>
        <P>3. Enhance the quality, utility, and clarity of the information to be collected.</P>
        <P>4. 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. In particular, EPA is requesting comments from very small businesses (those that employ less than 25) on examples of specific additional efforts that EPA could make to reduce the paperwork burden for very small businesses affected by this collection.</P>
        <HD SOURCE="HD1">II. What should I consider when I prepare my comments for EPA?</HD>
        <P>You may find the following suggestions helpful for preparing your comments:</P>
        <P>1. Explain your views as clearly as possible and provide specific examples.</P>
        <P>2. Describe any assumptions that you used.</P>
        <P>3. Provide copies of any technical information and/or data you used that support your views.</P>

        <P>4. If you estimate potential burden or costs, explain how you arrived at the estimate that you provide.<PRTPAGE P="26751"/>
        </P>
        <P>5. Provide specific examples to illustrate your concerns.</P>
        <P>6. Offer alternative ways to improve the collection activity.</P>

        <P>7. Make sure to submit your comments by the deadline identified under<E T="02">DATES</E>.</P>

        <P>8. To ensure proper receipt by EPA, be sure to identify the docket ID number assigned to this action in the subject line on the first page of your response. You may also provide the name, date, and<E T="04">Federal Register</E>citation.</P>
        <HD SOURCE="HD1">III. What information collection activity or ICR does this action apply to?</HD>
        <P>
          <E T="03">Affected entities:</E>Entities potentially affected by this ICR are companies that export from the United States to foreign countries, or that engage in wholesale sales of, chemical substances or mixtures.</P>
        <P>
          <E T="03">Title:</E>Notification of Chemical Exports—TSCA Section 12(b).</P>
        <P>
          <E T="03">ICR number:</E>EPA ICR No. 0795.14.</P>
        <P>
          <E T="03">OMB control number:</E>OMB Control No. 2070-0030.</P>
        <P>
          <E T="03">ICR status:</E>This ICR is currently scheduled to expire on March 31, 2013. 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 OMB control number. The OMB control numbers for EPA's regulations in title 40 of the Code of Federal Regulations (CFR), after appearing in the<E T="04">Federal Register</E>when approved, are listed in 40 CFR part 9, are displayed either by publication in the<E T="04">Federal Register</E>or by other appropriate means, such as on the related collection instrument or form, if applicable. The display of OMB control numbers for certain EPA regulations is consolidated in 40 CFR part 9.</P>
        <P>
          <E T="03">Abstract:</E>Section 12(b)(2) of the Toxic Substances Control Act (TSCA) requires that any person who exports or intends to export to a foreign country a chemical substance or mixture that is regulated under TSCA sections 4, 5, 6, and/or 7 submit to EPA notification of such export or intent to export. Upon receipt of notification, EPA will advise the government of the importing country of the U.S. regulatory action with respect to that chemical substance or mixture. EPA uses the information obtained from the submitter via this collection to advise the government of the importing country. This information collection addresses the burden associated with industry reporting of export notifications.</P>
        <P>Responses to the collection of information are mandatory (see 40 CFR part 707). Respondents may claim all or part of a notice confidential. EPA will disclose information that is covered by a claim of confidentiality only to the extent permitted by, and in accordance with, the procedures in TSCA section 14 and 40 CFR part 2.</P>
        <P>
          <E T="03">Burden statement:</E>The annual public reporting and recordkeeping burden for this collection of information is estimated to average 1.3 hours per response. Burden means the total time, effort, or financial resources expended by persons to generate, maintain, retain, or disclose or provide information to or for a Federal agency. This includes the time needed to review instructions; develop, acquire, install, and utilize technology and systems for the purposes of collecting, validating, and verifying information, processing and maintaining information, and disclosing and providing information; adjust the existing ways to comply with any previously applicable instructions and requirements which have subsequently changed; train personnel to be able to respond to a collection of information; search data sources; complete and review the collection of information; and transmit or otherwise disclose the information.</P>
        <P>The ICR provides a detailed explanation of this estimate, which is only briefly summarized here:</P>
        <P>
          <E T="03">Estimated total number of potential respondents:</E>240.</P>
        <P>
          <E T="03">Frequency of response:</E>On occasion.</P>
        <P>
          <E T="03">Estimated total average number of responses for each respondent:</E>12.9.</P>
        <P>
          <E T="03">Estimated total annual burden hours:</E>4,025 hours.</P>
        <P>
          <E T="03">Estimated total annual costs:</E>$245,246. This includes an estimated burden cost of $245,246 and an estimated cost of $0 for capital investment or maintenance and operational costs.</P>
        <HD SOURCE="HD1">IV. Are there changes in the estimates from the last approval?</HD>
        <P>There is a decrease of 825 hours in the total estimated respondent burden compared with that identified in the ICR currently approved by OMB. This decrease reflects the net effect of a decrease in the estimated number of TSCA section 12(b) notices sent to EPA and a decrease in the number of firms sending notices, based on EPA's recent experience with those submissions. This change is an adjustment.</P>
        <HD SOURCE="HD1">V. What is the next step in the process for this ICR?</HD>

        <P>EPA will consider the comments received and amend the ICR as appropriate. The final ICR package will then be submitted to OMB for review and approval pursuant to 5 CFR 1320.12. EPA will issue another<E T="04">Federal Register</E>notice pursuant to 5 CFR 1320.5(a)(1)(iv) to announce the submission of the ICR to OMB and the opportunity to submit additional comments to OMB. If you have any questions about this ICR or the approval process, please contact the technical person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <HD SOURCE="HD1">List of Subjects</HD>
        <P>Environmental protection, Chemicals, Exports, Reporting and recordkeeping requirements.</P>
        <SIG>
          <DATED>Dated: April 25, 2012.</DATED>
          <NAME>James Jones,</NAME>
          <TITLE>Acting Assistant Administrator, Office of Chemical Safety and Pollution Prevention.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10940 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[FRL-9670-2; Docket ID No. EPA-HQ-ORD-2007-0664]</DEPDOC>
        <SUBJECT>Integrated Risk Information System (IRIS); Announcement of 2012 Program</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Announcement of 2012 Program; request for information.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The U.S. Environmental Protection Agency (EPA) is announcing the IRIS 2012 agenda and requesting scientific information on health effects that may result from exposure to the chemical substances on the agenda, including assessments that EPA is starting this year.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>While EPA is not expressly soliciting comments on this notice, the Agency will accept information related to the substances included herein. Please submit any information in accordance with the instructions provided below.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Please submit relevant scientific information identified by docket ID number EPA-HQ-ORD-2007-0664, online at<E T="03">www.regulations.gov</E>(EPA's preferred method); by email to<E T="03">ord.docket@epa.gov;</E>by mail to Office of Environmental Information (OEI) Docket (Mail Code: 2822T), U.S. Environmental Protection Agency, 1200 Pennsylvania Avenue NW., Washington, DC 20460-0001; or by hand delivery or courier to EPA Docket Center, EPA West, Room 3334, 1301 Constitution Avenue NW., Washington, DC, between 8:30 a.m. and 4:30 p.m. Monday through Friday, excluding legal holidays. The telephone number for the EPA Docket Center is 202-566-1744. Detailed instructions are<PRTPAGE P="26752"/>provided below under How to Submit Information to the Docket.</P>
          <P>
            <E T="03">Background:</E>EPA's IRIS Program is a human health assessment program that evaluates quantitative and qualitative risk information on effects that may result from exposure to chemical substances found in the environment. Through the IRIS Program, EPA provides high quality science-based human health assessments to support the Agency's regulatory activities. The IRIS database contains information for more than 540 chemical substances that can be used to support the first two steps (hazard identification and dose-response evaluation) of the risk assessment process. When supported by available data, IRIS provides oral reference doses (RfDs) and inhalation reference concentrations (RfCs) for chronic noncancer health effects and cancer assessments. Combining IRIS toxicity values with specific exposure information, government and private entities use IRIS to help characterize public health risks of chemical substances in site-specific situations and thereby support risk management decisions designed to protect public health.</P>

          <P>EPA' s process for developing IRIS assessments consists of: (1) A comprehensive search of the current scientific literature, a data call-in, and development of a draft IRIS health assessment; (2) internal EPA-wide review; (3) science consultation on the draft assessment with other Federal agencies and White House offices; (4) independent expert peer review, public review and comment, and public listening session; (5) revision of the assessment to address peer review and public comments; (6) internal EPA-wide review and interagency science discussion of EPA's disposition of peer review and public comments; and (7) clearance and posting of the final assessment on IRIS (<E T="03">www.epa.gov/iris</E>).</P>
          <P>
            <E T="03">The Iris Agenda:</E>As part of the IRIS process, EPA solicited nominations of chemicals for IRIS assessment or reassessment from EPA Program Offices and Regions, other Federal agencies and White House offices, and the public (75 FR 63827). EPA announced six general criteria for selection of chemicals for assessment or reassessment: (1) Potential public health impact; (2) EPA statutory, regulatory, or program-specific implementation needs; (3) availability of new scientific information or methodology that might significantly change the current IRIS information; (4) interest to other governmental agencies or the public; (5) availability of other scientific assessment documents that could serve as a basis for development of an IRIS assessment; and (6) other factors such as widespread exposure. The decision of when to start assessments of the selected high-priority chemical substances depends on available Agency resources. Availability of risk assessment guidance, guidelines, and science policy decisions may also have an impact on the timing of EPA's decision to assess a chemical substance.</P>

          <P>In developing the IRIS agenda for 2012, EPA conducted literature searches for the nominated chemicals and made a determination as to whether a particular chemical had sufficient information to develop at least one toxicity value. EPA offices were asked to indicate which chemicals with sufficient data were priorities for their offices. EPA then considered the other criteria as listed in the<E T="04">Federal Register</E>Notice (75 FR 63827) and the capacity of the IRIS Program to begin draft development for each chemical under consideration.</P>
          <P>EPA is soliciting public involvement in assessments on the IRIS agenda, including new assessments starting in 2012, 2013, and 2014. While EPA conducts a thorough literature search for each chemical substance, there may be unpublished studies or other primary technical sources that are not available through the open literature. EPA is soliciting scientific information from the public during the information gathering stage for the list of new assessments provided in this notice. Interested persons should provide scientific analyses, studies, and other pertinent scientific information. While EPA is primarily soliciting information on new assessments announced in this notice, the public may submit information on any chemical substance at any time.</P>
          <P>This notice provides: (1) A list of assessments completed since the IRIS agenda was last published in October 2010 (75 FR 63827); (2) a list of IRIS assessments in progress; (3) a list of IRIS assessments that will start in 2012, 2013, and 2014; and (4) instructions to the public for submitting scientific information to EPA pertinent to the development of assessments.</P>
        </ADD>
        <HD SOURCE="HD1">Assessments Completed</HD>

        <P>The following assessments have been completed since the last IRIS agenda was published in a<E T="04">Federal Register</E>Notice on October 18, 2010 (75 FR 63827).</P>
        <GPOTABLE CDEF="s50,10" COLS="2" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Chemical</CHED>
            <CHED H="1">Cas No.</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">dichloromethane (methylene chloride)</ENT>
            <ENT>75-09-2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">hexachloroethane</ENT>
            <ENT>67-72-1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">2,3,7,8-tetrachlorodibenzo-<E T="03">p</E>-dioxin (noncancer)</ENT>
            <ENT>1746-01-6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">tetrachloroethylene (perchloroethylene)</ENT>
            <ENT>127-18-4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">tetrahydrofuran</ENT>
            <ENT>109-99-9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">trichloroacetic acid</ENT>
            <ENT>76-03-9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">trichloroethylene</ENT>
            <ENT>79-01-6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">urea</ENT>
            <ENT>57-13-6</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">Assessments in Progress</HD>

        <P>The following assessments are underway. The status and planned milestone dates for each assessment can be found on the IRIS Track system, accessible from the IRIS database home page (www.epa.gov/iris). IRIS assessments for all substances listed as in progress in 2012 will be provided on the IRIS Web site at<E T="03">www.epa.gov/iris</E>as they are completed. This publicly available Web site is EPA's primary location for IRIS documents. In addition, external peer review drafts of IRIS assessments are posted for public information and comment. These drafts will continue to be accessible via the IRIS and NCEA Web sites. Note that these drafts are intended for public information only, and do not represent the Agency's final position.</P>
        <P>All health endpoints, cancer and noncancer, due to chronic exposure are being assessed unless otherwise noted. For all endpoints assessed, both qualitative and quantitative assessments are being developed where information is available.</P>
        <GPOTABLE CDEF="s50,xs50" COLS="2" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Chemical</CHED>
            <CHED H="1">Cas No.</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">acetaldehyde<SU>1</SU>
            </ENT>
            <ENT>75-07-0.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">acrylonitrile<SU>1</SU>
            </ENT>
            <ENT>107-13-1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">ammonia<SU>1</SU>
            </ENT>
            <ENT>7664-41-7.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">arsenic, inorganic<SU>1</SU>
            </ENT>
            <ENT>7440-38-2.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">benzo(a)pyrene<SU>1</SU>
            </ENT>
            <ENT>50-32-8.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">beryllium<SU>1</SU>
            </ENT>
            <ENT>7440-41-7.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">biphenyl<SU>1</SU>
            </ENT>
            <ENT>92-52-4.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">n-butanol<SU>1</SU>
            </ENT>
            <ENT>71-36-3.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">tert-butanol</ENT>
            <ENT>75-65-0.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">butyl benzyl phthalate<SU>1</SU>
            </ENT>
            <ENT>85-68-7.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">cadmium<SU>1</SU>
            </ENT>
            <ENT>7440-43-9.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">chloroethane</ENT>
            <ENT>75-00-3.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">chloroform<SU>1</SU>
            </ENT>
            <ENT>67-66-3.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">chromium VI<SU>1</SU>
            </ENT>
            <ENT>18540-29-9.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">cobalt</ENT>
            <ENT>7440-48-4.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">copper<SU>1</SU>
            </ENT>
            <ENT>7440-50-8.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">cumulative assessment for 6 phthalates</ENT>
            <ENT>various.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">di-n-butyl phthalate<SU>1</SU>
            </ENT>
            <ENT>84-74-2.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">1,2-dichlorobenzene<SU>1</SU>
            </ENT>
            <ENT>95-50-1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">1,3-dichlorobenzene<SU>1</SU>
            </ENT>
            <ENT>541-73-1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">1,4-dichlorobenzene<SU>1</SU>
            </ENT>
            <ENT>106-46-7.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">diethyl phthalate<SU>1</SU>
            </ENT>
            <ENT>84-66-2.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">di(2-ethylhexyl) adipate<SU>1</SU>
            </ENT>
            <ENT>103-23-1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">di(2-ethylhexyl) phthalate<SU>1</SU>
            </ENT>
            <ENT>117-81-7.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">diisobutyl phthalate</ENT>
            <ENT>84-69-5.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">diisononyl phthalate</ENT>
            <ENT>58033-90-2.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">1,4-dioxane (inhalation)<SU>1</SU>
            </ENT>
            <ENT>123-91-1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">dipentyl phthalate</ENT>
            <ENT>131-18-0.</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="26753"/>
            <ENT I="01">ethyl tertiary butyl ether (ETBE)</ENT>
            <ENT>637-92-3.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">ethylbenzene<SU>1</SU>
            </ENT>
            <ENT>100-41-4.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">ethylene oxide (cancer)</ENT>
            <ENT>75-21-8.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">formaldehyde<SU>1</SU>
            </ENT>
            <ENT>50-00-0.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">hexabromocyclododecane (mixed stereoisomers)</ENT>
            <ENT>3194-55-6, 25637-99-5.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">hexachlorobutadiene<SU>1</SU>
            </ENT>
            <ENT>87-68-3.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">hexahydro-1,3,5-trinitro-triazine (RDX)<SU>1</SU>
            </ENT>
            <ENT>121-82-4.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Libby amphibole asbestos</ENT>
            <ENT>1332-21-4.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">methanol (cancer)</ENT>
            <ENT>167-56-1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">methanol (noncancer)<SU>1</SU>
            </ENT>
            <ENT>167-56-1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">methyl tert-butyl ether (MTBE)<SU>1</SU>
            </ENT>
            <ENT>1634-04-4.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">naphthalene<SU>1</SU>
            </ENT>
            <ENT>91-20-3.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">nickel (soluble salts)<SU>1</SU>
            </ENT>
            <ENT>various.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">halogenated platinum salts and platinum compounds</ENT>
            <ENT>various.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">polychlorinated biphenyls (PCBs) (noncancer)<SU>1</SU>
            </ENT>
            <ENT>various.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">polycyclic aromatic hydrocarbon (PAH) mixtures</ENT>
            <ENT>various.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">styrene<SU>1</SU>
            </ENT>
            <ENT>100-42-5.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">2,3,7,8-tetrachlorodibenzo-<E T="03">p</E>-dioxin (cancer)</ENT>
            <ENT>1746-01-6.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">1,2,3-trimethylbenzene</ENT>
            <ENT>526-73-8.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">1,2,4-trimethylbenzene</ENT>
            <ENT>95-63-6.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">1,3,5-trimethylbenzene</ENT>
            <ENT>108-67-8.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">uranium (natural)<SU>1</SU>
            </ENT>
            <ENT>7440-61-1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">vanadium pentoxide<SU>1</SU>
            </ENT>
            <ENT>1314-62-1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">vinyl acetate<SU>1</SU>
            </ENT>
            <ENT>108-05-4.</ENT>
          </ROW>
          <TNOTE>
            <SU>1</SU>Reassessment of chemical currently on IRIS.</TNOTE>
        </GPOTABLE>
        <P>The cancer and noncancer assessments for inorganic arsenic, treated as two separate assessments in previous agendas, will be combined and proceed through the IRIS review process as one assessment. Similarly, the oral and inhalation assessments for chromium VI will be combined and proceed through the IRIS process as one assessment. EPA will update both the noncancer and cancer beryllium assessments, rather than just the cancer assessment.</P>

        <P>In January 2010, the IRIS assessment for methanol was released for external peer review and public comment. In June 2010, EPA decided to put the IRIS cancer assessment for methanol on hold pending a review of an underlying study by the Ramazzini Institute (RI). This review was conducted by an independent Pathology Working Group (PWG), jointly sponsored by EPA and the National Institute of Environmental Health Sciences (NIEHS), which was established to conduct a review of several RI studies including the methanol study. Based on differences of opinion between the RI and PWG scientists in diagnosing leukemias and lymphomas, EPA has decided not to rely on RI data on leukemias and lymphomas in IRIS assessments. This decision impacts the methanol cancer assessment. EPA will discontinue the peer review of the draft methanol cancer assessment and develop a new draft that does not rely on the RI study. A schedule for the development and review of the cancer assessment will be announced on IRIS track (<E T="03">www.epa.gov/iris</E>). The assessment of methanol's noncancer health effects does not rely on data from the RI. Therefore, the assessment for the noncancer effects of methanol will continue through remaining steps as a separate assessment.</P>
        <P>EPA is adding 1,2,3-trimethylbenzene (TMB) to the IRIS agenda to complete the set of three TMB isomers. Two other isomers of TMB are already included on the IRIS agenda and undergoing review (1,2,4-TMB and 1,3,5-TMB). 1,2,3-TMB is often found in the environment with 1,2,4- and 1,3,5-TMB. Given this situation, and in response to comments received in the Agency Review and Interagency Science Consultation for 1,2,4- and 1,3,5-TMB, EPA is adding 1,2,3-TMB to the agenda and will conduct assessments of all three isomers at the same time. Because the 1,2,4- and 1,3,5-TMB assessments are already underway, EPA would appreciate notification of any additional literature as soon as possible so that this information can be included in the 1,2,3-TMB assessment prior to public comment and external peer review.</P>
        <P>The ethanol assessment is on the IRIS agenda but has not been started. Taking into account the complexity of the ethanol dataset, EPA is considering various approaches to conducting the ethanol assessment. EPA will revisit the priority of the ethanol assessment in FY13.</P>
        <HD SOURCE="HD1">New Assessments for 2012 Agenda</HD>
        <P>EPA developed a list of priority chemicals for 2012 from two sources: (1) Chemicals nominated for IRIS assessment by EPA programs, other Federal agencies, and the public; and (2) chemicals already on the IRIS agenda but delayed because of resource limitations. For newly nominated chemicals, EPA first considered whether sufficient data are available to support development of one or more IRIS toxicity values. For chemicals with sufficient data, EPA considered statutory, regulatory, or programmatic need based on the stated priorities of EPA's Program and Regional Offices; potential public health impact of the assessment; interest to other levels of government or the public; and whether a partially completed draft for delayed assessments or an assessment by another organization is available that could serve as a basis for developing an IRIS assessment.</P>
        <P>The following chemicals have been selected for inclusion in the 2012 IRIS agenda. The projected start dates included in the table below indicate the U.S. fiscal year in which EPA will start or update literature searches for these chemicals.</P>
        <P>EPA is requesting information from the public for consideration in the development of these assessments. Instructions on how to submit information are provided below under How to Submit Information to the Docket.</P>
        <GPOTABLE CDEF="s100,r80,r40" COLS="3" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Chemical</CHED>
            <CHED H="1">Cas No.</CHED>
            <CHED H="1">Projected start</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">antimony<SU>1,3</SU>
            </ENT>
            <ENT>7440-36-0</ENT>
            <ENT>FY13.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">carbonyl sulfide<SU>1,3</SU>
            </ENT>
            <ENT>463-58-1</ENT>
            <ENT>FY12.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">chlorobenzene<SU>2,3</SU>
            </ENT>
            <ENT>108-90-7</ENT>
            <ENT>FY13.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">decamethylcyclopentasiloxane (D5)<SU>2</SU>
            </ENT>
            <ENT>541-02-6</ENT>
            <ENT>FY13.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">octamethylcyclotetrasiloxane (D4)<SU>2</SU>
            </ENT>
            <ENT>556-67-2</ENT>
            <ENT>FY13.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">1,2-dichloroethane (ethylene dichloride)<SU>1,3</SU>
            </ENT>
            <ENT>107-06-2</ENT>
            <ENT>FY14.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">diisopropyl ether (DIPE)<SU>1</SU>
            </ENT>
            <ENT>108-20-3</ENT>
            <ENT>FY12.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">tert-amyl methyl ether (TAME)“<SU>1</SU>
            </ENT>
            <ENT>994-05-8</ENT>
            <ENT>FY12.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">4,4'-dimethyl-3-oxahexane (TAEE)<SU>1</SU>
            </ENT>
            <ENT>919-94-8</ENT>
            <ENT>FY12.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">isopropanol<SU>1</SU>
            </ENT>
            <ENT>67-63-0</ENT>
            <ENT>FY13.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">manganese<SU>1,3</SU>
            </ENT>
            <ENT>7439-9</ENT>
            <ENT>FY13.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">mercury, elemental<SU>2,3</SU>
            </ENT>
            <ENT>7439-96-5</ENT>
            <ENT>FY14.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">methyl mercury<SU>2,3</SU>
            </ENT>
            <ENT>22967-92-6</ENT>
            <ENT>FY14.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">tungsten and related compounds<SU>1</SU>
            </ENT>
            <ENT>7440-33-7, various</ENT>
            <ENT>FY14.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">vanadium, elemental and compounds<SU>2</SU>various</ENT>
            <ENT/>
            <ENT>FY13</ENT>
          </ROW>
          <TNOTE>

            <SU>1</SU>Chemical was previously on the IRIS agenda but assessment was delayed due to resource limitations.<PRTPAGE P="26754"/>
          </TNOTE>
          <TNOTE>
            <SU>2</SU>Chemical is a new addition to IRIS agenda.</TNOTE>
          <TNOTE>
            <SU>3</SU>Reassessment of chemical currently on IRIS.</TNOTE>
        </GPOTABLE>
        <P>By FY14, EPA will have started all of the chemicals that were previously on the IRIS agenda, but delayed because of resource limitations, except for the chemicals that are being withdrawn from the agenda as described below under Withdrawn Assessments and the ethanol assessment, described above under Assessments in Progress. Among the new additions to the IRIS agenda, chlorobenzene, mercury, methyl mercury, and vanadium were selected for assessment because they are priorities for multiple EPA Program Offices and Regions and all chemicals have the potential for high impact on public health. While only two EPA Offices indicated that the siloxanes are priorities, D4 and D5 were selected for IRIS assessment because they met other criteria including high potential for impact on public health and widespread exposure and because of the opportunity afforded to perform a cumulative assessment of emerging contaminants.</P>

        <P>One of the highest priority substances nominated for assessment was lead. EPA will defer a decision on the development of an IRIS assessment for lead until the end of 2012. EPA anticipates publication of a final Integrated Science Assessment (ISA) for lead during the summer of 2012. The ISA offers a comprehensive summary of the health and ecological scientific evidence and also includes information on lead sources, ambient air concentrations, fate and transport, exposure, and toxicokinetics. A draft ISA is available at<E T="03">http://epa.gov/ncea/isa/lead.htm.</E>In addition, the National Toxicology Program (NTP) anticipates completion in 2012 of a draft<E T="03">Monograph on Health Effects of Low-Level Lead,</E>which summarizes the health evidence in humans related to major effects with a focus on blood lead levels &lt;10 ug/dL. A draft NTP report, available at<E T="03">http://ntp.niehs.nih.gov/go/36639,</E>has been reviewed by an NTP Peer Review Panel. Upon completion, these documents will be evaluated to determine if an IRIS assessment is needed.</P>
        <P>In FY2013, before beginning draft development, EPA will conduct a state-of-the-science workshop on manganese. Similarly, in FY2014, EPA will conduct a state-of-the-science workshop on elemental mercury and methyl mercury. These meetings will be open to the public.</P>
        <HD SOURCE="HD1">Withdrawn Assessments</HD>
        <P>The following chemicals are withdrawn from the IRIS agenda:</P>
        <GPOTABLE CDEF="s50,r40" COLS="2" OPTS="L2,i1">
          <BOXHD>
            <CHED H="1">Chemical</CHED>
            <CHED H="1">Cas No.</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">alkylates</ENT>
            <ENT>various.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">bisphenol A</ENT>
            <ENT>80-05-7.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">mirex</ENT>
            <ENT>2385-85-5.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">refractory ceramic fibers</ENT>
            <ENT>not applicable.</ENT>
          </ROW>
        </GPOTABLE>
        <P>The alkylates are a distillation fraction of petroleum and are present in gasoline. Common alkylates found in gasoline for which IRIS assessments have not been recently completed include n-heptane, methylcyclohexane, 2-methylbutane, 2-methylpentane, 3-methylpentane, n-octane, 2,3,3-trimethylpentane, 2,3,4-trimethylpentane, and 2,2,5-trimethylhexane. This class of chemicals is withdrawn from the IRIS agenda because there are multiple chemicals in the class, many with limited databases. If individual alkylates with sufficient data to support an IRIS assessment are nominated in the future, the IRIS Program will consider these nominations individually. Bisphenol A is withdrawn because EPA is awaiting further analysis and results from the U.S. Food and Drug Administration and the NIEHS prior to determining whether Agency action under the Toxic Substances Control Act is required for protection of human health. Refractory ceramic fibers and mirex are withdrawn because they are no longer priorities for EPA.</P>
        <P>We continue to request the submission of any scientific information that you would like EPA to consider for any assessment on the IRIS agenda. Instructions for submitting information are provided below.</P>
        <P>
          <E T="03">How to Submit Information to the Docket:</E>Submit your information, identified by Docket ID No. EPA-HQ-ORD-2007-0664, by one of the following methods:</P>
        <P>•<E T="03">http://www.regulations.gov:</E>Follow the online instructions for submitting comments.</P>
        <P>•<E T="03">Email: ORD.Docket@epa.gov.</E>
        </P>
        <P>•<E T="03">Facsimile:</E>202-566-1753.</P>
        <P>•<E T="03">Mail:</E>Office of Environmental Information (OEI) Docket (Mail Code: 2822T), U.S. Environmental Protection Agency, 1200 Pennsylvania Avenue NW., Washington, DC 20460. The telephone number is 202-566-1752. If you provide comments by mail, please submit one unbound original with pages numbered consecutively, and three copies of the comments. For attachments, provide an index, number pages consecutively with the comments, and submit an unbound original and three copies.</P>
        <P>•<E T="03">Hand Delivery:</E>The OEI Docket is located in the EPA Headquarters Docket Center, EPA West Building, Room 3334, 1301 Constitution Avenue NW., Washington, DC. The EPA Docket Center Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Public Reading Room is 202-566-1744. Deliveries are only accepted during the docket's normal hours of operation, and special arrangements should be made for deliveries of boxed information. If you provide comments by hand delivery, please submit one unbound original with pages numbered consecutively, and three copies of the comments. For attachments, provide an index, number pages consecutively with the comments, and submit an unbound original and three copies.</P>

        <P>It is EPA's policy to include all comments it receives in the public docket without change and to make the comments available online at<E T="03">http://www.regulations.gov,</E>including any personal information provided, unless comments include information claimed to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Do not submit information that you consider to be CBI or otherwise protected through<E T="03">http://www.regulations.gov</E>or email. The<E T="03">http://www.regulations.gov</E>Web site is an “anonymous access” system, which means that EPA will not know your identity or contact information unless you provide it in the body of your comments. If you send email comments directly to EPA without going through<E T="03">http://www.regulations.gov,</E>your email address will be automatically captured and included as part of the comments that are placed in the public docket and made available on the Internet. If you submit electronic comments, EPA recommends that you include your name and other contact information in the body of your comments and with any disk or CD-ROM you submit. If EPA cannot read your comments due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comments. Electronic files should avoid the use of special characters and any form of encryption and be free of any defects or viruses. For additional information<PRTPAGE P="26755"/>about EPA's public docket, visit the EPA Docket Center homepage at<E T="03">http://www.epa.gov/epahome/dockets.htm.</E>
        </P>
        <P>All documents in the docket are listed in the<E T="03">http://www.regulations.gov</E>index. Although listed in the index, some information is not publicly available, e.g., CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, will be publicly available only in hard copy. Publicly available docket materials are available either electronically at<E T="03">http://www.regulations.gov</E>or in hard copy at the OEI Docket in the EPA Headquarters Docket Center.</P>
        <P>
          <E T="03">Additional Information:</E>For information on the docket or<E T="03">www.regulations.gov</E>, please contact the Office of Environmental Information (OEI) Docket (Mail Code: 2822T), U.S. Environmental Protection Agency, 1200 Pennsylvania Avenue NW., Washington, DC 20460; telephone: 202-566-1752; facsimile: 202-566-1753; or email:<E T="03">ORD.Docket@epa.gov.</E>
        </P>

        <P>For information on the IRIS program, contact Karen Hammerstrom, IRIS Program Deputy Director, National Center for Environmental Assessment, (Mail Code: 8601P), Office of Research and Development, U.S. Environmental Protection Agency, 1200 Pennsylvania Avenue, NW., Washington, DC 20460; telephone: 703-347-8642; or email: FRN<E T="03">Questions@epa.gov.</E>
        </P>

        <P>For general questions about access to IRIS, or the content of IRIS, please call the IRIS Hotline at 202-566-1676 or send electronic mail inquiries to<E T="03">hotline.iris@epa.gov.</E>
        </P>
        <SIG>
          <DATED>Dated: April 30, 2012.</DATED>
          <NAME>Darrell A. Winner,</NAME>
          <TITLE>Acting Director, National Center for Environmental Assessment.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10935 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[FRL-9669-6]</DEPDOC>
        <SUBJECT>Underground Injection Control Program; Hazardous Waste Injection Restrictions; Petition for Exemption—Class I Hazardous Waste Injection; Diamond Shamrock Refining Company, LP, Sunray, TX</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of a final decision on a no migration petition reissuance.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Notice is hereby given that a reissuance of an exemption to the land disposal Restrictions, under the 1984 Hazardous and Solid Waste Amendments to the Resource Conservation and Recovery Act, has been granted to Diamond Shamrock for three Class I injection wells located at Sunray, Texas. The company has adequately demonstrated to the satisfaction of the Environmental Protection Agency by the petition reissuance application and supporting documentation that, to a reasonable degree of certainty, there will be no migration of hazardous constituents from the injection zone for as long as the waste remains hazardous. This final decision allows the continued underground injection by Diamond Shamrock, of the specific restricted hazardous wastes identified in this exemption, into Class I hazardous waste injection wells WDW-102, WDW-192, and WDW-332 at the Sunray, Texas facility until December 31, 2025, unless EPA moves to terminate this exemption. Additional conditions included in this final decision may be reviewed by contacting the Region 6 Ground Water/UIC Section. A public notice was issued February 27, 2012. The public comment period closed on April 12, 2012. No comments were received. This decision constitutes final Agency action and there is no Administrative appeal. This decision may be reviewed/appealed in compliance with the Administrative Procedure Act.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This action was effective as of April 18, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Copies of the petition and all pertinent information relating thereto are on file at the following location: Environmental Protection Agency, Region 6, Water Quality Protection Division, Source Water Protection Branch (6WQ-S), 1445 Ross Avenue, Dallas, Texas 75202-2733.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Philip Dellinger, Chief Ground Water/UIC Section, EPA—Region 6, telephone (214) 665-8324.</P>
          <SIG>
            <DATED>Dated: April 26, 2012.</DATED>
            <NAME>William K. Honker,</NAME>
            <TITLE>Acting Director, Water Quality Protection Division.</TITLE>
          </SIG>
        </FURINF>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10939 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">EXPORT-IMPORT BANK OF THE UNITED STATES</AGENCY>
        <DEPDOC>[EXIM-OIG-2011-0010]</DEPDOC>
        <SUBJECT>Office of Inspector General; Privacy Act of 1974; Systems of Records</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>The Export-Import Bank of the United States, Office of Inspector General.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of New Privacy Act System of Records.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In accordance with the Privacy Act of 1974, the Export-Import Bank of the United States (hereafter known as “Ex-Im Bank”), Office of Inspector General (hereafter known as “OIG” or “Ex-Im Bank OIG”) is giving notice of a new system of records entitled, “EIB-35-Office of Inspector General Investigative Records.” The information in the new system of records will be used by the Ex-Im Bank OIG to conduct criminal, civil, and administrative investigations, and will contain identifying information about potential subjects, sources, and other individuals related to these investigations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This system of records will become effective on June 15, 2012.</P>
          <P>
            <E T="03">Comment Date:</E>Comments should be received on or before June 6, 2012 to be assured of consideration.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by Docket Number EIB-2011-0010 by one of the following methods:</P>
          <P>1. Electronically through the eRulemaking Portal at<E T="03">http://www.regulations.gov</E>. Please search for EIB--2011-0010.</P>
          <P>2.<E T="03">By Mail/Hand Delivery/Courier:</E>Alberto Rivera-Fournier, Ex-Im Bank, Office of Inspector General/811 Vermont Avenue NW., Rm. 976, Washington, DC 20571. Please allow sufficient time for mailed comments to be received before the close of the comment period.</P>

          <P>All comments received before the end of the comment period will be posted on<E T="03">http://www.regulations.gov</E>for public viewing. Hard copies of comments may also be obtained by writing to Counsel to the Inspector General, Ex-Im Bank, Office of Inspector General/811 Vermont Avenue NW., Rm. 976, Washington, DC 20571.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Alberto Rivera-Fournier, Ex-Im Bank, Office of Inspector General, 811 Vermont Avenue NW, Rm. 976, Washington, DC 20571 or by telephone (202) 565-3908 or facsimile (202) 565-3988.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Ex-Im Bank OIG is establishing a new system<PRTPAGE P="26756"/>of records entitled “EIB-35-Office of Inspector General Investigative Records”. The system of records is necessary for Ex-Im Bank OIG to carry out its investigative responsibilities pursuant to the Inspector General Act of 1978, as amended.</P>
        <P>The Ex-Im Bank OIG was statutorily created in 2002 and organized in 2007. Ex-Im Bank OIG is statutorily directed to conduct and supervise investigations relating to programs and operations of Ex-Im Bank and to prevent and detect fraud, waste, and abuse in such programs and operations. Accordingly, the records in this system are used in the course of investigating individuals and entities suspected of having committed illegal or unethical acts and in conducting related criminal prosecutions, civil proceedings, and administrative actions. The records may contain information about civil, criminal, or administrative wrongdoing, or about fraud, waste, mismanagement, or other violations of law or regulation. This information could be the basis for referrals to appropriate prosecutorial authorities for consideration of criminal or civil prosecution or Ex-Im Bank management for administrative action.</P>
        <P>The collection and maintenance of records subject to this system is based on paper records and an electronic records management system, the “Inspector General Information System” (IGIS). IGIS allows the retrieval of records by name or other personal identifier. In accordance with 5 U.S.C. 552a(r), a report of this system of records has been provided to the Office of Management and Budget (OMB) and to the Congress. Concurrent with this system of records notice, Ex-Im Bank is proposing a rule to exempt portions of this system of records from one or more provisions of the Privacy Act because of criminal, civil, and administrative enforcement requirements. In addition, Ex-Im Bank OIG is publishing a Privacy Impact Assessment of IGIS.</P>
        <PRIACT>
          <HD SOURCE="HD2">SYSTEM NAME:</HD>
          <P>EIB-35-Office of Inspector General Investigative Records.</P>
          <HD SOURCE="HD2">SECURITY CLASSIFICATION:</HD>
          <P>The vast majority of the information in the system is Controlled Unclassified Information.</P>
          <HD SOURCE="HD2">SYSTEM LOCATION:</HD>
          <P>This system of records is located in the Ex-Im Bank OIG, 811 Vermont Avenue NW., Washington, DC 20571.</P>
          <HD SOURCE="HD2">CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:</HD>
          <P>1. Persons who are named individuals in investigations conducted by the Ex-Im Bank OIG.</P>
          <P>2. Complainants and subjects of complaints collected through the Ex-Im Bank OIG Hotline or other sources.</P>
          <P>3. Other individuals who have been identified as possibly relevant to, or who are contacted as part of an OIG investigation, including witnesses, confidential or non-confidential informants, and members of the general public who are named individuals in connection with investigations conducted by the Ex-Im Bank OIG.</P>
          <HD SOURCE="HD2">CATEGORIES OF RECORDS IN THE SYSTEM:</HD>
          <P>The system contains records related to complaints, and administrative, civil, and criminal investigations. These records include: (a) Letters, memoranda, emails, and other documents citing complaints or alleged criminal, civil, or administrative misconduct. (b) Investigative files which include reports of investigation with related exhibits, statements, affidavits, or records obtained during the investigation, information from subjects, targets, witnesses; material from governmental investigatory or law enforcement organizations (federal, state, local or international) and intelligence information; information of criminal, civil, or administrative referrals and/or results of investigations; public source materials; and reports and associated materials filed with Ex-Im Bank or other government agencies from, for example, exporters, lenders and other financial institutions, brokers, shippers, contractors, employers or other financial service providers.</P>
          <P>Personal data in the system may consist of names, addresses, Social Security Numbers, fingerprints, physical identifying data, individual personnel and payroll information, and other evidence and background material existing in any form (i.e., photographs, reports, criminal histories, etc.).</P>
          <HD SOURCE="HD2">AUTHORITY FOR MAINTENANCE OF THE SYSTEM:</HD>
          <P>The Inspector General Act of 1978, as amended, 5 U.S.C. App. 3; 5 U.S.C. 301; 44 U.S.C. 3101.</P>
          <HD SOURCE="HD2">PURPOSE(S):</HD>
          <P>This system of records is established under the Inspector General Act of 1978, as amended, to maintain information and document OIG work related to investigations of criminal, civil, or administrative matters.</P>
          <HD SOURCE="HD2">ROUTINE USES OF THESE RECORDS:</HD>
          <P>In addition to those disclosures generally permitted under 5 U.S.C. 552a(b) of the Privacy Act, all or a portion of the records or information contained in this system may be disclosed outside Ex-Im Bank OIG as a routine use pursuant to 5 U.S.C. 552a(b)(3) as follows:</P>
          <P>(A) To an appropriate Federal, State, territorial, tribal, local, or foreign law enforcement agency, licensing entity, or other appropriate authority charged with investigating, enforcing, prosecuting, or implementing a law (criminal, civil, administrative, or regulatory), where Ex-Im Bank OIG becomes aware of an indication of a violation or potential violation of such law or where required in response to compulsory legal process.</P>
          <P>(B) To Federal intelligence community agencies and other Federal agencies to further the mission of those agencies relating to persons who may pose a risk to homeland security.</P>
          <P>(C) To international governmental authorities in accordance with law and formal or informal international agreement;</P>
          <P>(D) To any individual or entity when necessary to elicit information that will assist an OIG investigation, inspection, or audit.</P>
          <P>(E) To a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil or criminal discovery or proceedings, litigation, and settlement negotiations.</P>
          <P>(F) To Federal, State, local, or foreign government entities or professional licensing authorities responsible for investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, or license, or where Ex-Im Bank OIG becomes aware of an indication of a violation or potential violation of civil or criminal law or regulation, or where Ex-Im Bank OIG has received a request for information that is relevant or necessary to the requesting entity's hiring or retention of an employee, or the issuance of a security clearance, license, contract, grant, or other benefit.</P>
          <P>(G) To contractors, grantees, experts, consultants, students, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for the Federal Government, when necessary to accomplish an agency function related to this system of records.</P>

          <P>(H) To the United States Department of Justice or other Federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (i) Ex-Im Bank; (ii) any employee of Ex-Im Bank<PRTPAGE P="26757"/>in his/her official capacity; (iii) any employee of Ex-Im Bank in his/her individual capacity where the Department of Justice or Ex-Im Bank has agreed to represent the employee; or, (iv) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation.</P>
          <P>(I) To third parties during the course of an investigation to the extent necessary to obtain information pertinent to the investigation.</P>
          <P>(J) To a Member of Congress, or staff acting upon the Member's behalf, when the Member or staff requests the information on behalf of, and at the request of, the individual who is the subject of the record.</P>
          <P>(K) To an actual or potential party to litigation or the party's authorized representative for the purpose of negotiation or discussion of such matters as settlement, plea bargaining, or in informal discovery proceedings.</P>
          <P>(L) To the news media and the public, including disclosures pursuant to 28 CFR 50.2, unless it is determined that release of the specific information in the context of a particular case would constitute an unwarranted invasion of personal privacy.</P>
          <P>(M) To complainants and/or victims to the extent necessary to provide such persons with information and explanations concerning the progress and/or results of the investigation or case arising from the matters of which they complained and/or of which they were a victim.</P>
          <P>(N) To appropriate agencies, entities, and persons when (1) the OIG suspects or has confirmed that the security or confidentiality of information in the system of records has been compromised; (2) the OIG has determined that as a result of the suspected or confirmed compromise there is a risk of harm to economic or property interests, identity theft or fraud, or harm to the security or integrity of this system or other systems or programs (whether maintained by the OIG or another agency or entity) that rely upon the compromised information; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with the OIG's efforts to respond to the suspected or confirmed compromise and prevent, minimize, or remedy such harm.</P>
          <P>(O) To the National Archives and Records Administration or other Federal Government agencies pursuant to records management inspections being conducted under the authority of 44 U.S.C. 2904 and 2906.</P>
          <P>(P) To appropriate persons engaged in conducting and reviewing internal and external peer reviews of the Ex-Im Bank OIG to ensure adequate internal safeguards and management procedures exist or to ensure that auditing standards applicable to Government audits are applied and followed.</P>
          <P>(Q) To the Council of Inspectors General on Integrity and Efficiency (“CIGIE”) and other Offices of Inspectors General, as necessary, if the records respond to an audit, investigation, or review which is conducted pursuant to an authorizing law, rule or regulation, and in particular those conducted at the request of the CIGIE pursuant to 5 U.S.C. App. 3, § 11.</P>
          <P>(R) In an appropriate proceeding before a court, grand jury, or an administrative or adjudicative body, when the OIG determines that the records are arguably relevant to the proceeding; or in an appropriate proceeding before an administrative or adjudicative body when the adjudicator determines the records to be relevant to the proceeding.</P>
          <P>(S) To appropriate officials and employees of a federal agency or entity which requires information relevant to a decision concerning the hiring, appointment, or retention of an individual; the issuance, renewal, suspension, or revocation of a security clearance; the execution of a security or suitability investigation; the letting of a contract; or the issuance or revocation of a grant or other benefit.</P>
          <P>(T) To federal, state, local, tribal, foreign, or international licensing agencies or associations which require information concerning the suitability or eligibility of an individual for a license or permit.</P>
          <P>(U) To such recipients and under such circumstances and procedures as are mandated by federal statute or treaty.</P>
          <HD SOURCE="HD2">DISCLOSURE TO CONSUMER REPORTING AGENCIES:</HD>
          <P>None.</P>
          <HD SOURCE="HD2">POLICIES AND PRACTICES FOR STORING, RETRIEVING, ACCESSING, RETAINING, AND DISPOSING OF RECORDS IN THE SYSTEM:</HD>
          <HD SOURCE="HD2">STORAGE:</HD>
          <P>The records in this system are maintained in a variety of media, including paper, digital media (hard drives and magnetic tapes or discs), and an automated database. The records are maintained in limited access areas during duty hours and in locked offices at all other times.</P>
          <HD SOURCE="HD2">RETRIEVABILITY:</HD>
          <P>Paper media are retrieved numerically by investigation number. Electronic media are retrieved numerically by investigation number, by the name or identifying number for a complainant, subject, victim, or witness; by case number; by special agent, or other personal identifier.</P>
          <HD SOURCE="HD2">SAFEGUARDS:</HD>
          <P>All paper and electronic records are protected from unauthorized access through appropriate administrative, physical, and technical safeguards. Ex-Im Bank facilities are protected from the outside by security personnel. Direct access to investigative records is restricted to authorized staff members of the OIG. Paper records, computers, and computer storage media are located in controlled-access areas under supervision of program personnel. Manual records are in locked cabinets or in safes and can be accessed by key or combination formula only. Electronic records are protected by computer-logon identifications and password protection.</P>
          <HD SOURCE="HD2">RETENTION AND DISPOSAL:</HD>
          <P>OIG is in the process of developing a records retention schedule in conjunction with the National Archives and Records Administration (NARA). Closed files relating to a specific investigation are destroyed after ten years. Closed files containing information of an investigative nature but not relating to a specific investigation are destroyed after five years. Records existing on computer storage media are destroyed according to applicable OIG media sanitization practice.</P>
          <HD SOURCE="HD2">SYSTEM MANAGER(S) AND ADDRESSES:</HD>
          <P>The System Manager is the Inspector General, Ex-Im Bank OIG, 811 Vermont Avenue NW., Rm. 976, Washington, DC 20571.</P>
          <HD SOURCE="HD2">NOTIFICATION PROCEDURES:</HD>
          <P>Pursuant to a concurrent notice of proposed rulemaking by Ex-Im Bank, this system of records will be generally exempt from the notice, access, and contest requirements of the Privacy Act. However, the Ex-Im Bank OIG will entertain written requests to the systems manager on a case-by-case basis for notification regarding whether this system of records contains information about an individual. Individuals seeking notification of any record contained in this system of records may submit a request in writing to the System Manager identified above. Individuals requesting notification must comply with the Ex-Im Bank Privacy Act regulations (12 CFR 404.4).</P>
          <HD SOURCE="HD2">RECORD ACCESS PROCEDURES:</HD>
          <P>Same as “Notification Procedures'” above.<PRTPAGE P="26758"/>
          </P>
          <HD SOURCE="HD2">CONTESTING RECORD PROCEDURES:</HD>
          <P>See “Notification procedures” and “Record access procedures” stated above.</P>
          <HD SOURCE="HD2">RECORD SOURCE CATEGORIES:</HD>
          <P>The information in this system of records is obtained from sources including, but not limited to, the individual record subjects; Ex-Im Bank officials and employees; employees of Federal, State, local, and foreign agencies; and other persons and entities; and public source materials.</P>
          <HD SOURCE="HD2">EXEMPTIONS CLAIMED FOR THE SYSTEM:</HD>
          <P>In general, the exemptions claimed are necessary in order to accomplish the law enforcement function of the OIG, to prevent subjects of investigations from frustrating the investigatory process, to prevent the disclosure of investigative techniques, to fulfill commitments made to protect the confidentiality of sources, to maintain access to sources of information, and to avoid endangering these sources and law enforcement personnel.</P>
          <P>A. Pursuant to 5 U.S.C. 552a(j)(2) and a proposed rulemaking by Ex-Im Bank, this system is proposed to be exempt from the following provisions of the Privacy Act: 5 U.S.C. 552a (c)(3) and (4); (d)(1) through (4); (e)(1), (e)(2), (e)(3), (e)(4)(G), (e)(4)(H), (e)(5) and (e)(8); (f); and (g). The reasons for asserting such exemptions are the following:</P>
          <P>(i) Disclosure to the individual named in the record pursuant to subsections (c)(3), (c)(4), or (d)(1) through (4) could seriously impede or compromise the investigation by alerting the target(s), subjecting a potential witness or witnesses to intimidation or improper influence, and leading to destruction of evidence. Disclosure could enable suspects to take action to prevent detection of criminal activities, conceal evidence, or escape prosecution.</P>
          <P>(ii) Application of subsection (e)(1) is impractical because the relevance of specific information might be established only after considerable analysis and as the investigation progresses. Effective law enforcement requires the OIG to keep information that may not be relevant to a specific OIG investigation, but which may provide leads for appropriate law enforcement and to establish patterns of activity that might relate to the jurisdiction of the OIG and/or other agencies.</P>
          <P>(iii) Application of subsection (e)(2) would be counterproductive to the performance of a criminal investigation because it would alert the individual to the existence of an investigation. In any investigation, it is necessary to obtain evidence from a variety of sources other than the subject of the investigation in order to verify the evidence necessary for successful litigation.</P>
          <P>(iv) Application of subsection (e)(3) could discourage the free flow of information in a criminal law enforcement inquiry.</P>
          <P>(v) Applications of subsections (e)(4)(G) and (H), and (f) would be counterproductive to the performance of a criminal investigation. To notify an individual at the individual's request of the existence of records in an investigative file pertaining to such individual, or to grant access to an investigative file could interfere with investigative and enforcement proceedings, deprive co-defendants of a right to a fair trial or other impartial adjudication, constitute an unwarranted invasion of personal privacy of others, disclose the identity or confidential sources, reveal confidential information supplied by these sources and disclose investigative techniques and procedures. Nevertheless, Ex-Im Bank OIG has published notice of its notification, access, and contest procedures because access may be appropriate in some cases.</P>
          <P>(vi) Although the Office of Inspector General endeavors to maintain accurate records, application of subsection (e)(5) is impractical because maintaining only those records that are accurate, relevant, timely, and complete and that assure fairness in determination is contrary to established investigative techniques. Information that may initially appear inaccurate, irrelevant, untimely, or incomplete may, when collated and analyzed with other available information, become more pertinent as an investigation progresses.</P>
          <P>(vii) Application of subsection (e)(8) could prematurely reveal an ongoing criminal investigation to the subject of the investigation.</P>
          <P>(viii) The provisions of subsection (g) do not apply to this system if an exemption otherwise applies.</P>
          <P>B. Pursuant to 5 U.S.C. 552a (k)(2) and a proposed rulemaking by Ex-Im Bank, this system is proposed to be exempt from the following provisions of the Privacy Act, subject to the limitations set forth in those subsections: 5 U.S.C. 552a (c)(3), (d)(1) through (4), (e)(1), (e)(4)(G), (e)(4)(H), and (f). These exemptions are claimed for the same reasons as stated in paragraph (a)(2) of this section, that is, because the system contains investigatory material compiled for law enforcement purposes other than material within the scope of subsection 552a(j)(2). In addition, the reasons for asserting this exemption are because the disclosure and other requirements of the Privacy Act could substantially compromise the efficacy and integrity of the OIG operations. Disclosure could invade the privacy of other individuals and disclose their identity when they were expressly promised confidentiality. Disclosure could interfere with the integrity of information which would otherwise be subject to privileges (see, e.g., 5 U.S.C. 552(b)(5)), and which could interfere with other important law enforcement concerns (see, e.g., 5 U.S.C. 552(b)(7)).</P>
          <P>C. Pursuant to 5 U.S.C. 552a(k)(5) and a proposed rulemaking by Ex-Im Bank, this system is proposed to be exempt from the following provisions of the Privacy Act: 5 U.S.C. 552a(c)(3), (d)(1) through (4), (e)(1), (e)(4)(G) and (H), and (f). The reason for asserting this exemption is because the system contains investigatory material compiled for the purpose of determining eligibility or qualifications for federal civilian or contract employment.</P>
        </PRIACT>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Osvaldo L. Gratacos,</NAME>
          <TITLE>Inspector General.</TITLE>
          <NAME>Sharon A. Whitt,</NAME>
          <TITLE>Agency Clearance Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10897 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6690-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FARM CREDIT ADMINISTRATION</AGENCY>
        <SUBJECT>Sunshine Act Meeting; Farm Credit Administration Board</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Farm Credit Administration.</P>
        </AGY>
        
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Notice is hereby given, pursuant to the Government in the Sunshine Act (5 U.S.C. 552b(e)(3)), of the regular meeting of the Farm Credit Administration Board (Board).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Date and Time:</E>The regular meeting of the Board will be held at the offices of the Farm Credit Administration in McLean, Virginia, on May 10, 2012, from 9:00 a.m. until such time as the Board concludes its business.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Dale L. Aultman, Secretary to the Farm Credit Administration Board, (703) 883-4009, TTY (703) 883-4056.</P>
        </FURINF>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Farm Credit Administration, 1501 Farm Credit Drive, McLean, Virginia 22102-5090.</P>
        </ADD>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>Parts of this meeting of the Board will be open to the public (limited space available) and parts will be closed to the public. In order to increase the accessibility to Board meetings, persons requiring assistance should make arrangements in<PRTPAGE P="26759"/>advance. The matters to be considered at the meeting are:</P>
        <HD SOURCE="HD1">Open Session</HD>
        <HD SOURCE="HD2">A. Approval of Minutes</HD>
        <P>• April 12, 2012.</P>
        <HD SOURCE="HD2">B. Reports</HD>
        <P>• Dodd-Frank Implementation, Update.</P>
        <HD SOURCE="HD1">Closed Session*</HD>
        <P>• Office of Secondary Market Oversight Quarterly Report.</P>
        
        <FP SOURCE="FP-1">*Session Closed—Exempt pursuant to 5 U.S.C. 552b(c)(8) and (9).</FP>
        <SIG>
          <DATED>Dated: May 3, 2012<E T="03">.</E>
          </DATED>
          <NAME>Dale L. Aultman,</NAME>
          <TITLE>Secretary, Farm Credit Administration Board.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-11058 Filed 5-3-12; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 6705-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL ELECTION COMMISSION</AGENCY>
        <SUBJECT>Sunshine Act Meeting</SUBJECT>
        <PREAMHD>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Election Commission.</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">DATE AND TIME:</HD>
          <P>Thursday, May 10, 2012 at 10:00 a.m.</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">PLACE:</HD>
          <P>999 E Street NW., Washington, DC (Ninth Floor).</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">STATUS:</HD>
          <P>This Meeting Will Be Open to the Public.</P>
        </PREAMHD>
        <HD SOURCE="HD1">Items To Be Discussed</HD>
        <P>Correction and Approval of the Minutes for the Meeting of April 26, 2012.</P>
        <P>Draft Advisory Opinion 2012-07: Feinstein for Senate.</P>
        <P>Draft Advisory Opinion 2012-16: Angus King for U.S. Senate Campaign and Pierce Atwood LLP.</P>
        <P>Audit Division Recommendation Memorandum on The Legacy Committee Political Action Committee (A09-22).</P>
        <P>Revised Guidebook for Complainants and Respondents on the FEC Enforcement Process.</P>
        <P>2012 Legislative Recommendations.</P>
        <P>Management and Administrative Matters.</P>
        <P>Individuals who plan to attend and require special assistance, such as sign language interpretation or other reasonable accommodations, should contact Shawn Woodhead Werth, Secretary and Clerk, at (202) 694-1040, at least 72 hours prior to the meeting date.</P>
        <PREAMHD>
          <HD SOURCE="HED">PERSON TO CONTACT FOR INFORMATION:</HD>
          <P>Judith Ingram, Press Officer, Telephone: (202) 694-1220.</P>
        </PREAMHD>
        <SIG>
          <NAME>Shawn Woodhead Werth,</NAME>
          <TITLE>Secretary and Clerk of the Commission.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-11079 Filed 5-3-12; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 6715-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
        <SUBJECT>Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company</SUBJECT>
        <P>The notificants listed below have applied under the Change in Bank Control Act (12 U.S.C. 1817(j)) and § 225.41 of the Board's Regulation Y (12 CFR 225.41) to acquire shares of a bank or bank holding company. The factors that are considered in acting on the notices are set forth in paragraph 7 of the Act (12 U.S.C. 1817(j)(7)).</P>
        <P>The notices are available for immediate inspection at the Federal Reserve Bank indicated. The notices also will be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing to the Reserve Bank indicated for that notice or to the offices of the Board of Governors. Comments must be received not later than May 29, 2012.</P>
        <P>A. Federal Reserve Bank of Richmond (Adam M. Drimer, Assistant Vice President) 701 East Byrd Street, Richmond, Virginia 23261-4528:</P>
        <P>1.<E T="03">Gerald F. Smith, Jr. Revocable Trust, (trustee, Gerald F. Smith, Jr.) Winchester, Virginia,</E>to individually acquire voting shares of First National Corporation, Strasburg, Virginia. Additionally, Gerald F. Smith, Jr. Revocable Trust, (trustee, Gerald F. Smith, Jr.) Gerald F. Smith, Jr., Evan A. Smith, Kaye DeHaven Smith Irrevocable Trust FBO Evan A. Smith (trustee, Gerald F. Smith, Jr.), Kaye DeHaven Smith Irrevocable Trust FBO Elise D. Smith (trustee, Gerald F. Smith, Jr.), Kaye DeHaven Smith Irrevocable Trust FBO Emily N. Smith (trustee, Gerald F. Smith, Jr.), and other family members all of Winchester, Virginia, as a group acting in concert to collectively acquire voting shares of First National Corporation and thereby acquire voting shares of First Bank, Strasburg, Virginia.</P>
        <P>2.<E T="03">James R. Wilkins, III, Wilkins Investments, L.P., James R. Wilkins, Jr., Elizabeth Wilkins Talley, Wilkins Shoe Center, Inc. Profit Sharing Trust FBO Wilkins Shoe Center, Inc., and other family members, all of Winchester, Virginia,</E>as a group acting in concert to acquire voting shares of First National Corporation, Strasburg, Virginia and thereby acquire voting shares of First Bank, Strasburg, Virginia.</P>
        <SIG>
          <P>Board of Governors of the Federal Reserve System.</P>
          
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Robert deV. Frierson,</NAME>
          <TITLE>Deputy Secretary of the Board.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10926 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6210-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
        <SUBJECT>Formations of, Acquisitions by, and Mergers of Bank Holding Companies</SUBJECT>

        <P>The companies listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841<E T="03">et seq.</E>) (BHC Act), Regulation Y (12 CFR part 225), and all other applicable statutes and regulations to become a bank holding company and/or to acquire the assets or the ownership of, control of, or the power to vote shares of a bank or bank holding company and all of the banks and nonbanking companies owned by the bank holding company, including the companies listed below.</P>
        <P>The applications listed below, as well as other related filings required by the Board, are available for immediate inspection at the Federal Reserve Bank indicated. The applications will also be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing on the standards enumerated in the BHC Act (12 U.S.C. 1842(c)). If the proposal also involves the acquisition of a nonbanking company, the review also includes whether the acquisition of the nonbanking company complies with the standards in section 4 of the BHC Act (12 U.S.C. 1843). Unless otherwise noted, nonbanking activities will be conducted throughout the United States.</P>
        <P>Unless otherwise noted, comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than May 31, 2012.</P>
        <P>A. Federal Reserve Bank of Kansas City (Dennis Denney, Assistant Vice President) 1 Memorial Drive, Kansas City, Missouri 64198-0001:</P>
        <P>1.<E T="03">Vintage Bancorp, Inc., Wichita, Kansas,</E>to become a bank holding company by acquiring 100 percent of the voting shares of Vintage Bank Kansas, Leon, Kansas and CornerBank, N.A., Winfield, Kansas</P>
        <SIG>
          <PRTPAGE P="26760"/>
          <DATED>Board of Governors of the Federal Reserve System, May 1, 2012.</DATED>
          <NAME>Jennifer J. Johnson,</NAME>
          <TITLE>Secretary of the Board.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10832 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6210-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
        <SUBJECT>Formations of, Acquisitions by, and Mergers of Bank Holding Companies</SUBJECT>

        <P>The companies listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841<E T="03">et seq.</E>) (BHC Act), Regulation Y (12 CFR part 225), and all other applicable statutes and regulations to become a bank holding company and/or to acquire the assets or the ownership of, control of, or the power to vote shares of a bank or bank holding company and all of the banks and nonbanking companies owned by the bank holding company, including the companies listed below.</P>
        <P>The applications listed below, as well as other related filings required by the Board, are available for immediate inspection at the Federal Reserve Bank indicated. The application also will be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing on the standards enumerated in the BHC Act (12 U.S.C. 1842(c)). If the proposal also involves the acquisition of a nonbanking company, the review also includes whether the acquisition of the nonbanking company complies with the standards in section 4 of the BHC Act (12 U.S.C. 1843). Unless otherwise noted, nonbanking activities will be conducted throughout the United States.</P>
        <P>Unless otherwise noted, comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than June 1, 2012.</P>
        <P>A. Federal Reserve Bank of San Francisco (Kenneth Binning, Vice President, Applications and Enforcement) 101 Market Street, San Francisco, California 94105-1579:</P>
        <P>1.<E T="03">First Foundation Inc., Irvine, California,</E>to become a bank holding company upon the conversion of its wholly owned subsidiary First Foundation Bank, Irvine, California, from a federal savings bank to a commercial bank.</P>
        <SIG>
          <DATED>Board of Governors of the Federal Reserve System, May 2, 2012.</DATED>
          <NAME>Robert deV. Frierson,</NAME>
          <TITLE>Deputy Secretary of the Board.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10927 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6210-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL TRADE COMMISSION</AGENCY>
        <DEPDOC>[File No. 121 0014]</DEPDOC>
        <SUBJECT>Kinder Morgan, Inc.; Analysis of Proposed Agreement Containing Consent Orders To Aid Public Comment</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Trade Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed Consent Agreement.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The consent agreement in this matter settles alleged violations of federal law prohibiting unfair or deceptive acts or practices or unfair methods of competition. The attached Analysis to Aid Public Comment describes both the allegations in the draft complaint and the terms of the consent order—embodied in the consent agreement—that would settle these allegations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received on or before June 4, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Interested parties may file a comment online or on paper, by following the instructions in the Request for Comment part of the<E T="02">SUPPLEMENTARY INFORMATION</E>section below. Write AEl Paso Kinder Morgan, File No. 121 0014” on your comment, and file your comment online at<E T="03">https://ftcpublic.commentworks.com/ftc/elpasokindermorganconsent,</E>by following the instructions on the web-based form. If you prefer to file your comment on paper, mail or deliver your comment to the following address: Federal Trade Commission, Office of the Secretary, Room H-113 (Annex D), 600 Pennsylvania Avenue NW., Washington, DC 20580.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Philip M. Eisenstat (202) 326-2769, FTC, Bureau of Consumer Protection, 600 Pennsylvania Avenue NW., Washington, DC 20580.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>Pursuant to section 6(f) of the Federal Trade Commission Act, 38 Stat. 721, 15 U.S.C. 46(f), and 2.34 the Commission Rules of Practice, 16 CFR 2.34, notice is hereby given that the above-captioned consent agreement containing a consent order to cease and desist, having been filed with and accepted, subject to final approval, by the Commission, has been placed on the public record for a period of thirty (30) days. The following Analysis to Aid Public Comment describes the terms of the consent agreement, and the allegations in the complaint. An electronic copy of the full text of the consent agreement package can be obtained from the FTC Home Page (for May 1, 2012), on the World Wide Web, at<E T="03">http://www.ftc.gov/os/actions.shtm.</E>A paper copy can be obtained from the FTC Public Reference Room, Room 130-H, 600 Pennsylvania Avenue NW., Washington, DC 20580, either in person or by calling (202) 326-2222.</P>

        <P>You can file a comment online or on paper. For the Commission to consider your comment, we must receive it on or before April 16, 2012. Write AEl Paso Kinder Morgan, File No. 121 0014” on your comment. Your comment B including your name and your state B will be placed on the public record of this proceeding, including, to the extent practicable, on the public Commission Web site, at<E T="03">http://www.ftc.gov/os/publiccomments.shtm.</E>As a matter of discretion, the Commission tries to remove individuals' home contact information from comments before placing them on the Commission Web site.</P>
        <P>Because your comment will be made public, you are solely responsible for making sure that your comment does not include any sensitive personal information, like anyone's Social Security number, date of birth, driver's license number or other state identification number or foreign country equivalent, passport number, financial account number, or credit or debit card number. You are also solely responsible for making sure that your comment does not include any sensitive health information, like medical records or other individually identifiable health information. In addition, do not include any A[t]rade secret or any commercial or financial information which is obtained from any person and which is privileged or confidential,” as provided in Section 6(f) of the FTC Act, 15 U.S.C. 46(f), and FTC Rule 4.10(a)(2), 16 CFR 4.10(a)(2). In particular, do not include competitively sensitive information such as costs, sales statistics, inventories, formulas, patterns, devices, manufacturing processes, or customer names.</P>
        <P>If you want the Commission to give your comment confidential treatment, you must file it in paper form, with a request for confidential treatment, and you have to follow the procedure explained in FTC Rule 4.9(c), 16 CFR 4.9(c).<SU>1</SU>
          <FTREF/>Your comment will be kept confidential only if the FTC General Counsel, in his or her sole discretion, grants your request in accordance with the law and the public interest.</P>
        <FTNT>
          <P>
            <SU>1</SU>In particular, the written request for confidential treatment that accompanies the comment must include the factual and legal basis for the request, and must identify the specific portions of the comment to be withheld from the public record. See FTC Rule 4.9(c), 16 CFR 4.9(c).</P>
        </FTNT>

        <P>Postal mail addressed to the Commission is subject to delay due to heightened security screening. As a<PRTPAGE P="26761"/>result, we encourage you to submit your comments online. To make sure that the Commission considers your online comment, you must file it at<E T="03">https://ftcpublic.commentworks.com/ftc/elpasokindermorganconsent</E>by following the instructions on the web-based form. If this Notice appears at<E T="03">http://www.regulations.gov/#!home,</E>you also may file a comment through that Web site.</P>
        <P>If you file your comment on paper, write AEl Paso Kinder Morgan, File No. 121 0014” on your comment and on the envelope, and mail or deliver it to the following address: Federal Trade Commission, Office of the Secretary, Room H-113 (Annex D), 600 Pennsylvania Avenue NW., Washington, DC 20580. If possible, submit your paper comment to the Commission by courier or overnight service.</P>
        <P>Visit the Commission Web site at<E T="03">http://www.ftc.gov</E>to read this Notice and the news release describing it. The FTC Act and other laws that the Commission administers permit the collection of public comments to consider and use in this proceeding as appropriate. The Commission will consider all timely and responsive public comments that it receives on or before June 4, 2012. You can find more information, including routine uses permitted by the Privacy Act, in the Commission's privacy policy, at<E T="03">http://www.ftc.gov/ftc/privacy.htm.</E>
        </P>
        <HD SOURCE="HD1">Analysis of Agreement Containing Consent Order To Aid Public Comment</HD>
        <HD SOURCE="HD1">I. Introduction</HD>
        <P>The Federal Trade Commission (the “Commission”), subject to its final approval, has accepted for public comment an Agreement Containing Consent Orders (Consent Agreement) with Kinder Morgan, Inc. (“KMI” or “Respondent”) and El Paso Corporation (“El Paso”). The purpose of the proposed Consent Agreement is to remedy the anticompetitive effects that otherwise would likely result from Respondent's acquisition of El Paso. Under the terms of the agreement, Respondent will divest its own Rockies Express (REX), Kinder Morgan Interstate Gas Transmission, and Trailblazer pipelines, as well as associated processing and storage capacity.</P>
        <P>On October 16, 2011, KMI announced that it had entered into a definitive agreement whereby KMI will acquire all of the outstanding shares of El Paso for approximately $38 billion, including the assumption of $17 billion in debt (the “Acquisition”). The Acquisition would combine the nation's largest two natural gas pipeline owners. Separately from any Commission action, El Paso will sell its exploration and production (“E&amp;P”) assets to another company, delivering its midstream components and the proceeds from the E&amp;P sale to KMI.</P>
        <P>Without some form of relief, the Acquisition is likely to result in anticompetitive effects in areas in the Rocky Mountains where the combination of the KMI pipelines and the El Paso pipelines threatens to lessen competition substantially in pipeline transportation. The Acquisition is also likely to result in anticompetitive effects in other markets related to pipelines: Gas processing and “no-notice” service. The proposed Consent Agreement effectively remedies these possible anticompetitive effects by requiring KMI to divest three of its natural gas pipelines and two natural gas processing plants.</P>
        <HD SOURCE="HD1">II. The Parties</HD>
        <HD SOURCE="HD2">A. Kinder Morgan, Inc.</HD>
        <P>KMI is a publicly traded corporation principally engaged in midstream petroleum and natural gas services. KMI is the general partner in the master-limited partnership (“MLP”) Kinder Morgan Energy Partners (KMEP) (collectively, “Kinder Morgan”). KMEP owns over 38,000 miles of pipelines and 180 terminals in North America for the transportation and storage of natural gas, refined petroleum products, crude oil, and carbon dioxide.</P>
        <HD SOURCE="HD2">B. El Paso Corporation</HD>
        <P>El Paso is a publically traded corporation principally engaged in natural gas transportation, natural gas gathering and processing, and E&amp;P. El Paso is the general partner in the MLP, El Paso Pipeline Partners (EPPP), into which El Paso placed some of its pipelines. Between El Paso and EPPP, El Paso owns or has interests in over 43,000 miles of natural gas pipelines and gathering systems.</P>
        <HD SOURCE="HD1">III. Market Structure and Competitive Effects in Pipeline Transportation</HD>
        <P>Natural gas pipelines provide the critical connection between natural gas wells, which produce natural gas, and consumers who use natural gas to generate heat and power. Pipeline transportation is the only economical means to transport natural gas between the producers and consumers. Pipelines that cross state lines are regulated by the Federal Energy Regulatory Commission (“FERC”). FERC regulates maximum-allowable interstate natural gas pipeline transportation fees, but does not eliminate competition between pipelines. So long as the pipelines comply with their tariffs, they are otherwise free to compete by offering prices below their maximum tariff rate, as well as competing on other terms of service.</P>
        <P>The competitive overlaps between Kinder Morgan and El Paso in pipeline transportation are in the Rocky Mountain gas production areas in and around Wyoming, Colorado, and Utah. Kinder Morgan and El Paso pipelines dominate the transportation options for five production areas in the Rockies: (1) The Denver/Julesburg/Niobrara Production Basin; (2) the Powder River Production Basin; (3) the Wind River Production Basin; (4) the Western Wyoming Production areas including the Green River Production Basin, the Red Desert Production Basin, and the Washakie Production Basins; and (5) the Piceance Production Basin. Each of these production areas is a relevant geographic market for the transportation of natural gas.</P>
        <P>Production areas are connected to more than one pipeline and some pipelines connect to more than one production area. Some pipelines do not connect directly to the basins but interconnect with the pipelines leaving the basins and are necessary to get natural gas from the basins to consuming markets. There are four Kinder Morgan pipelines that serve the basins and interconnections in the Rockies and four El Paso pipelines that serve those same basins and interconnections.</P>
        <P>In each of these relevant geographic markets, the pipeline transportation of natural gas is highly concentrated. The Acquisition would significantly increase concentration and eliminate direct competition between the pipelines owned by the two companies, leading to higher prices for pipeline transportation of natural gas to the detriment of producers and consumers of natural gas.</P>

        <P>One consumption area in the Rockies is also a relevant geographic market. The Colorado Front Range, which runs from Fort Collins, Colorado in the north to Pueblo, Colorado in the south, contains the major population centers in the Rockies. It overlaps the Denver/Julesburg/Niobrara Production Basin but requires substantial additional natural gas from the other production areas in the Rockies, particularly in the winter. The pipeline transportation of natural gas into this market from the other production areas is highly concentrated. The Acquisition would significantly increase concentration and eliminate direct and potential competition between the pipelines owned by the two companies, leading to higher prices for pipeline transportation of natural gas to<PRTPAGE P="26762"/>the detriment of consumers of natural gas along the Colorado Front Range.</P>
        <HD SOURCE="HD1">IV. Other Markets Impacted by the Proposed Acquisition</HD>
        <P>Two other markets, the processing of natural gas and the provision of no-notice pipeline transportation services, would also be impacted by the Acquisition. Both services are related to the pipeline transportation of natural gas.</P>
        <P>Natural gas must meet certain standards before an interstate pipeline can accept it. In some areas, natural gas contains heavy hydrocarbons, commonly referred to as natural gas liquids or NGLs. Interstate pipelines have a limit on how much NGLs natural gas can contain and be transported on a pipeline. Gas that contains excessive amounts of NGLs must be treated at a gas processing plant to remove those liquids before it can be transported on interstate pipelines. Currently, the high value of NGLs, relative to the natural gas, would cause the gas to be processed regardless of the specifications of the pipelines. There is no substitute for gas processing to remove the NGLs. The relevant geographic market for processing gas is in the Wind River Production Basin and surrounding areas. For some wells in areas around that basin, only El Paso and Kinder Morgan have processing plants to treat gas before it goes onto interstate pipelines. The Acquisition would eliminate direct competition between the processing plants owned by the two companies, leading to higher prices for gas processing to the detriment of producers of natural gas.</P>
        <P>No-notice service is also a relevant market. Interstate pipelines typically require advance notice before a customer transports gas on a pipeline. Some customers' demand for natural gas fluctuates so much that the customers cannot give the required notice to the pipeline and still obtain the natural gas that they need. No-notice service is the term that refers to gas transportation where the customer is not obligated to provide advance notice before shipping gas. Utility customers whose natural gas demand can shift suddenly due to changes in the weather often require no-notice service. No-notice service is provided by pipelines at a premium price. It is not economical for each utility that has need for no-notice service to build sufficient storage to meet all of its peak needs through building its own storage facility. Many utilities are dependent on pipeline companies to provide no-notice service utilizing pipeline owned or third party storage. The relevant geographic market for no-notice service is the Colorado Front Range. Only those pipelines that currently serve this area can offer no-notice service. Currently only El Paso offers no-notice service in that area, but Kinder Morgan is a likely potential entrant into the market. The acquisition by Kinder Morgan of El Paso would eliminate potential competition for no-notice service to the detriment of utility customers.</P>
        <HD SOURCE="HD1">V. The Proposed Agreement Containing Consent Orders</HD>
        <P>Under the Proposed Agreement Containing Consent Orders (the “Consent Order”) Kinder Morgan has 180 days from the closing date of its acquisition of El Paso to completely divest three KMI pipelines and two processing plants in the Rockies. The fourth KMI pipeline, the TransColorado, does not raise competitive concerns because its competition with El Paso is limited and there are viable alternatives for transporting natural gas from the San Juan Basin. Accordingly, the TransColorado was not included in the divested assets. These divestitures maintain the competitive status quo ante in the Rockies. Pursuant to the Consent Order, Kinder Morgan may complete its acquisition of El Paso, while the divestiture of pipelines and processing plants already owned by Kinder Morgan will maintain the level of competition that already existed. The Order to Hold Separate and Maintain Assets (discussed in the next section) will protect the competitive status quo until Kinder Morgan successfully finds a buyer for the assets to be divested.</P>
        <P>The Consent Order requires Kinder Morgan to provide transitional assistance and support services to the buyer of the divested services. Kinder Morgan must also license any key software and intellectual property to the buyer. The Consent Order allows the buyer to recruit Kinder Morgan employees who work on the divested assets. For a period of two years, Kinder Morgan may not solicit employees that accept employment offers from the buyer to rejoin Kinder Morgan. The Consent Order also limits Kinder Morgan's access to, and use of, confidential business information pertaining to the divestiture assets.</P>
        <P>If Kinder Morgan fails to fully divest the assets within the 180-day time period, the Order grants the Commission power to appoint a divestiture trustee to complete the divestiture. The Consent Order also governs the divestiture trustee's duties, privileges, and powers.</P>
        <P>The Consent Order requires Kinder Morgan, or the divestiture trustee, if appointed, to file periodic reports detailing efforts to divest the assets and the status of that undertaking. Commission representatives may gain reasonable access to Kinder Morgan's business records related to compliance with the consent agreement. The Consent Order terminates when all requirements of the divestiture order outlined in Paragraphs II and IV of the Consent Order are satisfied.</P>
        <HD SOURCE="HD1">VI. The Order To Hold Separate and Maintain Assets</HD>
        <P>The Order to Hold Separate and Maintain Assets (“Hold Separate Order”) requires KMI to separate out the divestiture assets from its remaining businesses and assets. Pursuant to the Hold Separate Order, Kinder Morgan will not exercise any control or influence over the divestiture assets while seeking a buyer. The Hold Separate Order seeks to preserve the divestiture assets as viable, competitive, ongoing businesses, and it assures that Kinder Morgan does not access the confidential business information belonging to those businesses.</P>
        <P>The Hold Separate Order also empowers the Commission to appoint a hold separate trustee to monitor the divestiture assets and requires the Respondent to appoint a hold separate manager, subject to approval of the hold separate trustee in concurrence with Commission staff, to manage day-to-day operations. The Hold Separate Order outlines the rights, duties, and responsibilities of both the trustee and the manager, including access to business records, hiring necessary consultants and attorneys, and any other thing reasonably necessary to carry out their duties. The hold separate manager reports to the hold separate trustee and not to Kinder Morgan.</P>
        <P>The Hold Separate Order prohibits Kinder Morgan from interfering with the hold separate trustee and requires it to indemnify the trustee. The Hold Separate Order requires Kinder Morgan to provide certain support services and financial assistance to the divestiture assets to ensure they operate as they did before the merger.</P>

        <P>The hold separate trustee must submit periodic reports to the Commission concerning compliance with the Hold Separate Order. The Commission may appoint a different hold separate trustee if the original trustee fails to carry out his duties. The hold separate manager has authority to hire staff, maintain the assets, continue on-going capital projects, and ensure employees of the divestiture assets are not involved in Kinder Morgan's other businesses.<PRTPAGE P="26763"/>
        </P>
        <P>The Hold Separate Order terminates either (1) one day after the divestiture is completed or (2) three business days after the Commission withdraws acceptance of the consent agreement.</P>
        <HD SOURCE="HD1">VII. Opportunity for Public Comment</HD>
        <P>The proposed Consent Agreement has been placed on the public record for thirty (30) days for receipt of comments by interested persons. The Commission has also issued its Complaint in this matter. Comments received during this comment period will become part of the public record. After thirty days, the Commission will again review the proposed Consent Agreement and the comments received and will decide whether it should withdraw from the Agreement or make final the Agreement's proposed Order.</P>
        <P>By accepting the proposed Consent Agreement subject to final approval, the Commission anticipates that the competitive problems alleged in the Complaint will be resolved. The purpose of this analysis is to invite public comment on the proposed Order to aid the Commission in its determination of whether it should make final the proposed Order contained in the Agreement. This analysis is not intended to constitute an official interpretation of the proposed Order, nor is it intended to modify the terms of the proposed Order in any way.</P>
        <P>The purpose of this analysis is to aid public comment on the proposed order. It is not intended to constitute an official interpretation of the complaint or proposed order, or to modify in any way the proposed order's terms.</P>
        <SIG>
          <P>By direction of the Commission, Commissioner Ramirez recused.</P>
          <NAME>Donald S. Clark,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10870 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6750-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">GENERAL SERVICES ADMINISTRATION</AGENCY>
        <DEPDOC>[OMB Control No. 3090-0080; Docket 2011-0016; Sequence 9]</DEPDOC>
        <SUBJECT>General Services Administration Acquisition Regulation; Submission for OMB Review; Contract Financing Final Payment (GSAR Parts 532 and 552.232-72; GSA Form 1142 Release of Claims)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Chief Acquisition Officer, GSA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of request for comments regarding an extension to an existing OMB clearance.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>Under the provisions of the Paperwork Reduction Act, the Regulatory Secretariat will be submitting to the Office of Management and Budget (OMB) a request to review and approve an extension of a previously approved information collection requirement and the reinstatement of GSA Form 1142, Release of Claims, regarding final payment under construction and building services contract. GSA Form 1142 was inadvertently deleted as part of the rewrite of GSAR regulations on Contract Financing. GSA Contracting Officers have used this form to achieve uniformity and consistency in the release of claims process. A notice was published in the<E T="04">Federal Register</E>at 77 FR 2726, January 19, 2012. No comments were received.</P>
          <P>Public comments are particularly invited on: Whether this collection of information is necessary and whether it will have practical utility; whether our estimate of the public burden of this collection of information is accurate, and based on valid assumptions and methodology; ways to enhance the quality, utility, and clarity of the information to be collected.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit comments on or before: June 6, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Ms. Dana Munson, General Services Acquisition Policy Division, GSA, (202) 357-9652 or email<E T="03">Dana.Munson@gsa.gov.</E>
          </P>
        </FURINF>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit comments identified by Information Collection 3090-0080, Contract Financing Final Payment; (GSAR Part 532 and 552.232-72; GSA Form 1142, Release of Claims) by any of the following methods:</P>
          <P>•<E T="03">Regulations.gov: http://www.regulations.gov.</E>Submit comments via the Federal eRulemaking portal by searching the OMB control number. Select the link “Submit a Comment” that corresponds with “Information Collection 3090-0080, Contract Financing Final Payment; (GSAR Part 532 and 552.232-72; GSA Form 1142, Release of Claims).” Follow the instructions provided at the “Submit a Comment” screen. Please include your name, company name (if any), and “Information Collection 3090-0080, Contract Financing Final Payment; (GSAR Part 532 and 552.232-72; GSA Form 1142, Release of Claims),” on your attached document.</P>
          <P>•<E T="03">Fax:</E>202-501-4067.</P>
          <P>•<E T="03">Mail:</E>General Services Administration, Regulatory Secretariat (MVCB), 1275 First Street NE., Washington, DC 20417. Attn: Hada Flowers/IC 3090-0080, Contract Financing Final Payment; (GSAR Part 532 and 552.232-72; GSA Form 1142, Release of Claims).</P>
          <P>
            <E T="03">Instructions:</E>Please submit comments only and cite Information Collection 3090-0080, Contract Financing Final Payment; (GSAR Part 532 and 552.232-72; GSA Form 1142, Release of Claims), in all correspondence related to this collection. All comments received will be posted without change to<E T="03">http://www.regulations.gov,</E>including any personal and/or business confidential information provided.</P>
        </ADD>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">A. Purpose</HD>
        <P>The General Services Administration Acquisition Regulation (GSAR) clause 552.232-72 requires construction and building services contractors to submit a release of claims before final payment is made to ensure contractors are paid in accordance with their contract requirements and for work performed. GSA Form 1142, Release of Claims is used to achieve uniformity and consistency in the release of claims process.</P>
        <HD SOURCE="HD1">B. Annual Reporting Burden</HD>
        <P>
          <E T="03">Respondents:</E>2000.</P>
        <P>
          <E T="03">Responses per Respondent:</E>1</P>
        <P>
          <E T="03">Hours per Response:</E>.1</P>
        <P>
          <E T="03">Total Burden Hours:</E>200.</P>
        <P>
          <E T="03">Obtaining Copies of Proposals:</E>Requesters may obtain a copy of the information collection documents from the General Services Administration, Regulatory Secretariat (MVCB), 1275 First Street NE., Washington, DC 20417, telephone (202) 501-4755. Please cite OMB Control No. 3090-0080, Contract Financing Final Payment; (GSAR Part 532 and 552.232-72; GSA Form 1142, Release of Claims), in all correspondence.</P>
        <SIG>
          <DATED>Dated: April 25, 2012.</DATED>
          <NAME>Joseph A. Neurauter,</NAME>
          <TITLE>Director, Office of Acquisition Policy, Senior Procurement Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10981 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6820-61-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
        <DEPDOC>[Document Identifier: CMS-10169]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Centers for Medicare &amp; Medicaid Services.<PRTPAGE P="26764"/>
          </P>
          <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>Revised collection;<E T="03">Title of Information Collection:</E>Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS) Competitive Bidding Program;<E T="03">Use:</E>The Centers for Medicare &amp; Medicaid Services (CMS) will conduct competitive bidding programs in which certain suppliers will be awarded contracts to provide competitively bid DMEPOS items to Medicare beneficiaries in a competitive bidding area (CBA). CMS conducted its first round of bidding in 2007 which was implemented on July 1, 2008. The first round of bidding was subsequently delayed by section 154 of the Medicare Improvements for Patients and Providers Act of 2008 (MIPPA).</P>

          <P>As required by MIPPA, CMS conducted the competition for the Round 1 Rebid in 2009. The Round 1 Rebid contract and prices became effective on January 1, 2011. The Medicare Modernization Act (MMA) requires the Secretary to recompete contracts not less often than once every 3 years; therefore, CMS is preparing to recompete competitive bidding contracts in the Round 1 Rebid areas.<E T="03">Form Number:</E>CMS-10169 (OCN: 0938-1016);<E T="03">Frequency:</E>Reporting—Occasionally;<E T="03">Affected Public:</E>Business or other for-profit, Not-for-profit institutions;<E T="03">Number of Respondents:</E>16,003;<E T="03">Total Annual Responses:</E>20,047;<E T="03">Total Annual Hours:</E>34,795. (For policy questions regarding this collection contact James Cowher at 410-786-1948. For all other issues call 410-786-1326.)</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 Email 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>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 by July 6, 2012:</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>
        </AGY>
        <SIG>
          <DATED>Dated: May 2, 2012.</DATED>
          <NAME>Martique Jones</NAME>
          <TITLE>Director, Regulations Development Group, Division B, Office of Strategic Operations and Regulatory Affairs.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10947 Filed 5-4-12; 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>Administration for Children and Families</SUBAGY>
        <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
        <P>
          <E T="03">Title:</E>Assets for Independence (AFI) Program Evaluation.</P>
        <P>
          <E T="03">OMB No.:</E>New Collection.</P>
        <P>
          <E T="03">Description:</E>The U.S. Department of Health and Human Services, Administration for Children and Families (ACF) is proposing a data collection activity as part of an experimental evaluation of the Assets for Independence (AFI) Program. The purpose of this study is to assess the impact of participation in AFI-funded individual development account (IDA) projects on the savings, asset purchases, and economic well-being of low-income individuals and families. The two primary research questions are:</P>
        <P>• What is the impact of AFI project participation on short-term outcomes such as savings, asset purchases, and avoidance of material hardship?</P>
        <P>• How do specific AFI project design features affect short-term participant outcomes?</P>
        <P>While some evaluations suggest that IDAs help low-income families save, rigorous experimental research is limited. Few studies have focused on AFI-funded IDAs, and few have tested alternative design features.</P>
        <P>This evaluation—the first experimental evaluation of IDA projects operating under the Assets for Independence Act—will contribute importantly to understanding the effects of IDA project participation on project participants, particularly effects that occur within the first 12 months of participation, and how these short-term effects differ under alternative project designs. The evaluation will be conducted in two sites, with the random assignment of AFI-eligible cases to program and control groups. The evaluation consists of both an impact study and an implementation study. Data collection activities will span a three-year period.</P>
        <HD SOURCE="HD1">Respondents</HD>
        <P>Respondent groups will include: (1) AFI-eligible participants and (2) AFI project administrators and staff members of the participating AFT grantees and their partnering organizations.</P>
        <GPOTABLE CDEF="s50,12,12,12,12" COLS="5" OPTS="L2,i1">
          <TTITLE>Annual Burden Estimates</TTITLE>
          <BOXHD>
            <CHED H="1">Instrument</CHED>
            <CHED H="1">Number of<LI>respondent</LI>
            </CHED>
            <CHED H="1">Number of<LI>response per</LI>
              <LI>respondents</LI>
            </CHED>
            <CHED H="1">Average<LI>burden hours</LI>
              <LI>per response</LI>
            </CHED>
            <CHED H="1">Estimated<LI>burden hours</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">AFI Baseline Questionnaire</ENT>
            <ENT>567</ENT>
            <ENT>1</ENT>
            <ENT>.50</ENT>
            <ENT>284</ENT>
          </ROW>
          <ROW>
            <ENT I="01">AFT Follow-Up Questionnaire</ENT>
            <ENT>482</ENT>
            <ENT>1</ENT>
            <ENT>.50</ENT>
            <ENT>241</ENT>
          </ROW>
          <ROW RUL="n,s">
            <PRTPAGE P="26765"/>
            <ENT I="01">AFT Implementation Interview Instrument</ENT>
            <ENT>10</ENT>
            <ENT>1</ENT>
            <ENT>1.00</ENT>
            <ENT>10</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Estimated Total Annual Burden Hours:</ENT>
            <ENT/>
            <ENT/>
            <ENT/>
            <ENT>535</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">Additional Information</HD>

        <P>Copies of the proposed collection may be obtained by writing to the Administration for Children and Families, Office of Planning, Research and Evaluation, 370 L'Enfant Promenade, SW., Washington, DC 20447, Attn: OPRE Reports Clearance Officer. All requests should be identified by the title of the information collection. Email address:<E T="03">OPREinfocollection@acf.hhs.gov.</E>
        </P>
        <HD SOURCE="HD1">OMB Comment</HD>

        <P>OMB is required to make a decision concerning the collection of information between 30 and 60 days after publication of this document in the<E T="04">Federal Register</E>. Therefore, a comment is best assured of having its full effect if OMB receives it within 30 days of publication. Written comments and recommendations for the proposed information collection should be sent directly to the following: Office of Management and Budget, Paperwork Reduction Project, Email:<E T="03">OIRA_SUBMISSION@OMB.EOP.GOV,</E>Attn: Desk Officer for the Administration for Children and Families.</P>
        <SIG>
          <DATED>Dated: April 30, 2012.</DATED>
          <NAME>Steven M. Hanmer,</NAME>
          <TITLE>OPRE Reports Clearance Officer.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10735 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4184-24-M</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Food and Drug Administration</SUBAGY>
        <DEPDOC>[Docket No. FDA-2011-N-0879]</DEPDOC>
        <SUBJECT>David H.M. Phelps: Debarment Order</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 U.S. Food and Drug Administration (FDA) is issuing an order under the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) debarring David H.M. Phelps for a period of 20 years from importing articles of food or offering such articles for importation into the United States. FDA bases this order on a finding that Mr. Phelps was convicted, as defined in section 306(l)(1)(B) of the FD&amp;C Act (21 U.S.C. 335a(l)(1)(B)), of 10 felony counts under Federal law for conduct relating to the importation into the United States of an article of food. Mr. Phelps was given notice of the proposed debarment and an opportunity to request a hearing within the timeframe prescribed by regulation. As of March 31, 2012 (30 days after receipt of the notice), Mr. Phelps had not responded. Mr. Phelps's failure to respond constitutes a waiver of his right to a hearing concerning this action.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This order is effective May 7, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit applications for termination of debarment to the Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Kenny Shade, Office of Regulatory Affairs, Food and Drug Administration, 12420 Parklawn Drive, Rockville, MD 20857, 301-796-4640.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>Section 306(b)(1)(C) of the FD&amp;C Act (21 U.S.C. 335a(b)(1)(C)) permits FDA to debar an individual from importing an article of food or offering such an article for import into the United States if FDA finds, as required by section 306(b)(3)(A) of the FD&amp;C Act (21 U.S.C. 335a(b)(3)(A)), that the individual has been convicted of a felony for conduct relating to the importation into the United States of any food.</P>
        <P>On May 4, 2011, Mr. Phelps was convicted, as defined in section 306(l)(1)(B) of the FD&amp;C Act, when the U.S. District Court for the Southern District of Alabama accepted his plea of guilty and entered judgment against him for the following offenses: One count of conspiracy to commit offenses against the laws of the United States, in violation of 18 U.S.C. 371; nine counts of false labeling under the Lacey Act, in violation of 16 U.S.C. 3372(d)(2) and 3373(d)(3)(A); two counts of receipt of merchandise imported contrary to law, in violation of 18 U.S.C. 545; and one count of misbranding, in violation of 21 U.S.C. 331(a), 333(a)(2), and 343(a)(1) and (b).</P>
        <P>FDA's finding that debarment is appropriate is based on the felony convictions referenced herein for conduct relating to the importation into the United States of any food. The factual basis for these convictions is as follows: As stated in the factual resume accompanying the plea agreement referenced above and alleged in the indictment filed against Mr. Phelps, Mr. Phelps was co-owner, vice president, and secretary of CSE Inc., which was used to buy and sell seafood. He was also a co-owner and vice president of RF Inc. RF Inc. also sold seafood, including but not limited to shrimp, oysters, Lake Victoria perch, and types of catfish, commonly called basa, swai, and sutchi.</P>

        <P>Beginning on or about January 1, 2004, and continuing through on or about November 8, 2006, Mr. Phelps knowingly, willingly, and unlawfully combined, conspired, confederated, and agreed with his coconspirators to commit offenses against the laws of the United States related to importation of food. This conduct was in violation of 18 U.S.C. 371. Specifically, Mr. Phelps received and bought 81,000 pounds of fish of the genus<E T="03">Pangasius</E>(a type of catfish commonly called basa, swai, or sutchi) that he knew had been unlawfully imported from Vietnam. He knew that the fish was falsely labeled as sole when it was imported, and that it was imported without the required antidumping duty having been paid. He created or caused others to create false invoices and labeling for this fish, and other fish of the genus<E T="03">Pangasius</E>bought and sold to customers, totaling approximately 101,078 pounds. Mr. Phelps sold and invoiced the fish as grouper or sole, allowing him to sell the fish in interstate commerce at higher profit margins and more readily than if the fish had been accurately labeled and described.</P>

        <P>From on or about February 9, 2005, through on or about June 27, 2005, Mr. Phelps knowingly made and caused to be made a false record, account, and label for, and false identification of fish, that had been and was intended to be<PRTPAGE P="26766"/>transported in interstate and foreign commerce, having a market value greater than $350, and that involved the sale and purchase, the offer of sale and purchase, and the intent to sell and purchase fish, and the importation of fish, in that he created and caused to be created invoices, boxes, and other documents that falsely identified the fish. Specifically, Mr. Phelps falsely identified fish as sole and<E T="03">Cynoglossus bilineatus,</E>when in fact it was fish of the genus<E T="03">Pangasius,</E>a type of catfish. This conduct was in violation of 16 U.S.C. 3372(d)(2) and 3373(3)(A).</P>

        <P>From about March 30, 2005, through April 4, 2005, Mr. Phelps knowingly received, concealed, bought, sold, and facilitated the transportation, concealment, and sale of merchandise after importation, specifically frozen fish fillets of the genus<E T="03">Pangasius,</E>knowing it to have been imported and brought into the United States contrary to law, that is falsely declared and with applicable duties having been paid. This conduct was in violation of 18 U.S.C. 545.</P>

        <P>From approximately March 30, 2005, through approximately June 22, 2005, with intent to defraud and mislead, Mr. Phelps introduced and delivered and caused to be introduced and delivered into interstate commerce food, specifically frozen fish fillets, that was misbranded in that it had been falsely and misleadingly labeled and described as sole and<E T="03">Cynoglossus bilineatus,</E>when in fact the fish was of the genus<E T="03">Pangasius.</E>This conduct in violation of 21 U.S.C. 331(a), 333(a)(2), and 343(a)(1) and (b).</P>
        <P>As a result of his conviction, on February 17, 2012, FDA sent Mr. Phelps a notice by certified mail proposing to debar him for a period of 20 years from importing articles of food or offering such articles for import into the United States. The proposal was based on a finding under section 306(b)(1)(C) of the FD&amp;C Act that Mr. Phelps was convicted of 10 felony counts under Federal law for conduct relating to the importation into the United States of an article of food because he: Conspired to and committed offenses related to the importation of fish into the United States; falsely identified fish; concealed, bought, sold, and facilitated the transportation, concealment, and sale of frozen fish fillets after importation, knowing it to have been imported and brought into the United States contrary to law; and introduced and delivered misbranded fish into interstate commerce. The proposal was also based on a determination, after consideration of the factors set forth in section 306(c)(3) of the FD&amp;C Act (21 U.S.C. 335a(c)(3)), that Mr. Phelps should be subject to a 20-year period of debarment. The proposal also offered Mr. Phelps an opportunity to request a hearing, providing him 30 days from the date of receipt of the letter in which to file the request, and advised him that failure to request a hearing constituted a waiver of the opportunity for a hearing and of any contentions concerning this action. Mr. Phelps failed to respond within the timeframe prescribed by regulation and has, therefore, waived his opportunity for a hearing and waived any contentions concerning his debarment (21 CFR part 12).</P>
        <HD SOURCE="HD1">II. Findings and Order</HD>
        <P>Therefore, the Director, Office of Enforcement, Office of Regulatory Affairs, under section 306(b)(1)(C) of the FD&amp;C Act, and under authority delegated to the Director (Staff Manual Guide 1410.35), finds that Mr. David H.M. Phelps has been convicted of 10 felony counts under Federal law for conduct relating to the importation of an article of food into the United States and that he is subject to a 20-year period of debarment.</P>

        <P>As a result of the foregoing finding, Mr. Phelps is debarred for a period of 20 years from importing articles of food or offering such articles for import into the United States, effective (see<E T="02">DATES</E>). Pursuant to section 301(cc) of the FD&amp;C Act (21 U.S.C. 331(cc)), the importing or offering for import into the United States of an article of food by, with the assistance of, or at the direction of Mr. Phelps is a prohibited act.</P>

        <P>Any application by Mr. Phelps for termination of debarment under section 306(d)(1) of the FD&amp;C Act should be identified with Docket No. FDA-2011-N-0879 and sent to the Division of Dockets Management (see<E T="02">ADDRESSES</E>). All such submissions are to be filed in four copies. The public availability of information in these submissions is governed by 21 CFR 10.20(j).</P>
        <P>Publicly available submissions may be seen in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday.</P>
        <SIG>
          <DATED>Dated: April 24, 2012.</DATED>
          <NAME>Armando Zamora,</NAME>
          <TITLE>Acting Director, Office of Enforcement, Office of Regulatory Affairs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10958 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-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-2011-N-0880]</DEPDOC>
        <SUBJECT>Karen L. Blyth: Debarment Order</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 U.S. Food and Drug Administration (FDA) is issuing an order under the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) debarring Karen L. Blyth for a period of 20 years from importing articles of food or offering such articles for importation into the United States. FDA bases this order on a finding that Ms. Blyth was convicted, as defined in section 306(l)(1)(B) of the FD&amp;C Act (21 U.S.C. 335a(l)(1)(B)), of 10 felony counts under Federal law for conduct relating to the importation into the United States of an article of food. Ms. Blyth was given notice of the proposed debarment and an opportunity to request a hearing within the time frame prescribed by regulation. As of March 23, 2012 (30 days after receipt of the notice), Ms. Blyth had not responded. Ms. Blyth's failure to respond constitutes a waiver of her right to a hearing concerning this action.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This order is effective May 7, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit applications for termination of debarment to the Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Kenny Shade, Office of Regulatory Affairs, Food and Drug Administration, 12420 Parklawn Drive, Rockville, MD 20857, 301-796-4640.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>Section 306(b)(1)(C) of the FD&amp;C Act (21 U.S.C. 335a(b)(1)(C)) permits FDA to debar an individual from importing an article of food or offering such an article for import into the United States if FDA finds, as required by section 306(b)(3)(A) of the FD&amp;C Act (21 U.S.C. 335a(b)(3)(A)), that the individual has been convicted of a felony for conduct relating to the importation into the United States of any food.</P>

        <P>On May 4, 2011, Ms. Blyth was convicted, as defined in section 306(l)(1)(B) of the FD&amp;C Act, when the U.S. District Court for the Southern District of Alabama accepted her plea of<PRTPAGE P="26767"/>guilty and entered judgment against her for the following offenses: One count of conspiracy to commit offenses against the laws of the United States, in violation of 18 U.S.C. 371; nine counts of false labeling under the Lacey Act, in violation of 16 U.S.C. 3372(d)(2) and 3373(d)(3)(A); two counts of receipt of merchandise imported contrary to law, in violation of 18 U.S.C. 545; and one count of misbranding, in violation of 21 U.S.C. 331(a), 333(a)(2) and 343(a)(1) and (b).</P>
        <P>FDA's finding that debarment is appropriate is based on the felony convictions referenced herein for conduct relating to the importation into the United States of any food. The factual basis for these convictions is as follows: As stated in the factual resume accompanying the plea agreement referenced above and alleged in the indictment filed against Ms. Blyth, Ms. Blyth was a co-owner, president, and treasurer of CSE Inc., which was used to buy and sell seafood. She was also a co-owner, president, and chief executive officer of RF Inc. from on or about October 1, 2004, through on or about March 2007. RF Inc. also sold seafood, including but not limited to shrimp, oysters, Lake Victoria perch, and types of catfish, commonly called basa, swai, and sutchi.</P>

        <P>Beginning on or about January 1, 2004, and continuing through on or about November 8, 2006, Ms. Blyth knowingly, willingly, and unlawfully combined, conspired, confederated, and agreed with her coconspirators to commit offenses against the laws of the United States related to importation of food. This conduct was in violation of 18 U.S.C. 371. Specifically, Ms. Blyth received and bought 81,000 pounds of fish of the genus<E T="03">Pangasius</E>(a type of catfish commonly called basa, swai, or sutchi) that she knew had been unlawfully imported from Vietnam. She knew that the fish was falsely labeled as sole when it was imported, and that it was imported without the required antidumping duty having been paid. She created or caused others to create false invoices and labeling for this fish, and other fish of the genus<E T="03">Pangasius</E>bought and sold to customers, totaling approximately 101,078 pounds. Ms. Blyth sold and invoiced the fish as grouper or sole, allowing her to sell the fish in interstate commerce at higher profit margins and more readily than if the fish had been accurately labeled and described.</P>

        <P>From on or about February 9, 2005, through on or about June 27, 2005, Ms. Blyth knowingly made and caused to be made a false record, account, and label for, and false identification of fish, that had been and was intended to be transported in interstate and foreign commerce, having a market value greater than $350, and that involved the sale and purchase, the offer of sale and purchase, and the intent to sell and purchase fish, and the importation of fish, in that she created and caused to be created invoices, boxes, and other documents that falsely identified the fish. Specifically, Ms. Blyth falsely identified fish as sole and<E T="03">Cynoglossus bilineatus,</E>when in fact it was fish of the genus<E T="03">Pangasius,</E>a type of catfish. This conduct was in violation of 16 U.S.C. 3372(d)(2) and 3373(3)(A).</P>

        <P>From about March 30, 2005, through April 4, 2005, Ms. Blyth knowingly received, concealed, bought, sold, and facilitated the transportation, concealment, and sale of merchandise after importation, specifically frozen fish fillets of the genus<E T="03">Pangasius,</E>knowing it to have been imported and brought into the United States contrary to law, that is falsely declared and with applicable duties having been paid. This conduct is in violation of 18 U.S.C. 545.</P>

        <P>From approximately March 30, 2005, through approximately June 22, 2005, with intent to defraud and mislead, Ms. Blyth introduced and delivered and caused to be introduced and delivered into interstate commerce food, specifically frozen fish fillets, that was misbranded in that it had been falsely and misleadingly labeled and described as sole and<E T="03">Cynoglossus bilineatus,</E>when in fact the fish was of the genus<E T="03">Pangasius.</E>This conduct is in violation of 21 U.S.C. 331(a), 333(a)(2) and 343(a)(1) and (b).</P>
        <P>As a result of her conviction, on February 17, 2012, FDA sent Ms. Blyth a notice by certified mail proposing to debar her for a period of 20 years from importing articles of food or offering such articles for import into the United States. The proposal was based on a finding under section 306(b)(1)(C) of the FD&amp;C Act that Ms. Blyth was convicted of 10 felony counts under Federal law for conduct relating to the importation into the United States of an article of food because she: Conspired to and committed offenses related to the importation of fish into the United States; falsely identified fish; concealed, bought, sold, and facilitated the transportation, concealment, and sale of frozen fish fillets after importation, knowing it to have been imported and brought into the United States contrary to law; and introduced and delivered misbranded fish into interstate commerce. The proposal was also based on a determination, after consideration of the factors set forth in section 306(c)(3) of the FD&amp;C Act (21 U.S.C. 335a(c)(3)) that Ms. Blyth should be subject to a 20-year period of debarment. The proposal also offered Ms. Blyth an opportunity to request a hearing, providing her 30 days from the date of receipt of the letter in which to file the request, and advised her that failure to request a hearing constituted a waiver of the opportunity for a hearing and of any contentions concerning this action. Ms. Blyth failed to respond within the timeframe prescribed by regulation and has, therefore, waived her opportunity for a hearing and waived any contentions concerning her debarment (21 CFR part 12).</P>
        <HD SOURCE="HD1">II. Findings and Order</HD>
        <P>Therefore, the Director, Office of Enforcement, Office of Regulatory Affairs, under section 306(b)(1)(C) of the FD&amp;C Act, and under authority delegated to the Director (Staff Manual Guide 1410.35), finds that Ms. Karen L. Blyth has been convicted of 10 felony counts under Federal law for conduct relating to the importation of an article of food into the United States and that she is subject to a 20-year period of debarment.</P>

        <P>As a result of the foregoing finding, Ms. Blyth is debarred for a period of 20 years from importing articles of food or offering such articles for import into the United States, effective (see<E T="02">DATES</E>). Pursuant to section 301(cc) of the FD&amp;C Act (21 U.S.C. 331(cc)), the importing or offering for import into the United States of an article of food by, with the assistance of, or at the direction of Ms. Blyth is a prohibited act.</P>

        <P>Any application by Ms. Blyth for termination of debarment under section 306(d)(1) of the FD&amp;C Act (21 U.S.C. 335a(d)(1)) should be identified with Docket No. FDA-2011-N-0880 and sent to the Division of Dockets Management (see<E T="02">ADDRESSES</E>). All such submissions are to be filed in four copies. The public availability of information in these submissions is governed by 21 CFR 10.20(j).</P>
        <P>Publicly available submissions may be seen in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday.</P>
        <SIG>
          <DATED>Dated: April 24, 2012.</DATED>
          <NAME>Armando Zamora,</NAME>
          <TITLE>Acting Director, Office of Enforcement, Office of Regulatory Affairs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10960 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="26768"/>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Food and Drug Administration</SUBAGY>
        <DEPDOC>[Docket Nos. FDA-2011-E-0014, FDA-2010-E-0660, and FDA-2010-E-0659]</DEPDOC>
        <SUBJECT>Determination of Regulatory Review Period for Purposes of Patent Extension; PROLIA</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) has determined the regulatory review period for PROLIA and is publishing this notice of that determination as required by law. FDA has made the determination because of the submission of applications to the Director of Patents and Trademarks, Department of Commerce, for the extension of a patent which claims that human biological product.</P>
        </SUM>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit electronic comments to<E T="03">http://www.regulations.gov.</E>Submit written petitions along with three copies and written comments to the Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Beverly Friedman, Office of Regulatory Policy, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, rm. 6284, Silver Spring, MD 20993-0002, 301-796-3602.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Drug Price Competition and Patent Term Restoration Act of 1984 (Pub. L. 98-417) and the Generic Animal Drug and Patent Term Restoration Act (Pub. L. 100-670) generally provide that a patent may be extended for a period of up to 5 years so long as the patented item (human drug product, animal drug product, medical device, food additive, or color additive) was subject to regulatory review by FDA before the item was marketed. Under these acts, a product's regulatory review period forms the basis for determining the amount of extension an applicant may receive.</P>
        <P>A regulatory review period consists of two periods of time: A testing phase and an approval phase. For human biological products, the testing phase begins when the exemption to permit the clinical investigations of the biological becomes effective and runs until the approval phase begins. The approval phase starts with the initial submission of an application to market the human biological product and continues until FDA grants permission to market the biological product. Although only a portion of a regulatory review period may count toward the actual amount of extension that the Director of Patents and Trademarks may award (for example, half the testing phase must be subtracted as well as any time that may have occurred before the patent was issued), FDA's determination of the length of a regulatory review period for a human biological product will include all of the testing phase and approval phase as specified in 35 U.S.C. 156(g)(1)(B).</P>
        <P>FDA recently approved for marketing the human biological product PROLIA (denosumab). PROLIA is indicated for treatment of postmenopausal women with osteoporosis at high risk for fracture. Subsequent to this approval, the Patent and Trademark Office received patent term restoration applications for PROLIA (U.S. Patent Nos. 6,740,522; 7,097,834; and 7,411,050) from Amgen, Inc., and the Patent and Trademark Office requested FDA's assistance in determining the patents' eligibility for patent term restoration. In a letter dated April 27, 2011, FDA advised the Patent and Trademark Office that this human biological product had undergone a regulatory review period and that the approval of PROLIA represented the first permitted commercial marketing or use of the product. Thereafter, the Patent and Trademark Office requested that FDA determine the product's regulatory review period.</P>
        <P>FDA has determined that the applicable regulatory review period for PROLIA is 3,269 days. Of this time, 2,739 days occurred during the testing phase of the regulatory review period, while 530 days occurred during the approval phase. These periods of time were derived from the following dates:</P>
        <P>1.<E T="03">The date an exemption under section 505(i) of the Federal Food, Drug, and Cosmetic Act (21 U.S.C. 355(i)) became effective:</E>June 21, 2001. FDA has verified the applicant's claim that the date the investigational new drug application became effective was on June 21, 2001.</P>
        <P>2.<E T="03">The date the application was initially submitted with respect to the human biological product under section 351 of the Public Health Service Act (42 U.S.C. 262):</E>December 19, 2008. FDA has verified the applicant's claim that the biologics license application (BLA) for PROLIA (BLA125320) was submitted on December 19, 2008.</P>
        <P>3.<E T="03">The date the application was approved:</E>June 1, 2010. FDA has verified the applicant's claim that BLA125320 was approved on June 1, 2010.</P>
        <P>This determination of the regulatory review period establishes the maximum potential length of a patent extension. However, the U.S. Patent and Trademark Office applies several statutory limitations in its calculations of the actual period for patent extension. In its applications for patent extension, this applicant seeks 1,365 days; 952 days; and 595 days of patent term extension.</P>

        <P>Anyone with knowledge that any of the dates as published are incorrect may submit to the Division of Dockets Management (see<E T="02">ADDRESSES</E>) either electronic or written comments and ask for a redetermination by July 6, 2012. Furthermore, any interested person may petition FDA for a determination regarding whether the applicant for extension acted with due diligence during the regulatory review period by November 5, 2012. To meet its burden, the petition must contain sufficient facts to merit an FDA investigation. (See H. Rept. 857, part 1, 98th Cong., 2d sess., pp. 41-42, 1984.) Petitions should be in the format specified in 21 CFR 10.30.</P>

        <P>Interested persons may submit to the Division of Dockets Management (see<E T="02">ADDRESSES</E>) electronic or written comments and written petitions. It is only necessary to send one set of comments. However, if you submit a written petition, you must submit three copies of the petition. Identify comments with the docket numbers found in brackets in the heading of this document.</P>

        <P>Comments and petitions that have not been made publicly available on<E T="03">http://www.regulations.gov</E>may be viewed in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday.</P>
        <SIG>
          <DATED>Dated: April 16, 2012.</DATED>
          <NAME>Jane A. Axelrad,</NAME>
          <TITLE>Associate Director for Policy, Center for Drug Evaluation and Research.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10959 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-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-2012-N-0001]</DEPDOC>
        <SUBJECT>Food and Drug Administration/International Society for Pharmaceutical Engineering Cosponsorship Educational Workshop: Redefining the `C' in CGMP: Creating, Implementing, and Sustaining a Culture of Compliance</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food and Drug Administration, HHS.</P>
        </AGY>
        <ACT>
          <PRTPAGE P="26769"/>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of public workshop.</P>
        </ACT>
        <P>The Food and Drug Administration (FDA) Center for Drug Evaluation and Research, in cosponsorship with the International Society for Pharmaceutical Engineering (ISPE), is planning a multiday, educational public workshop entitled “Redefining the ‘C’ in CGMP: Creating, Implementing, and Sustaining a Culture of Compliance.”</P>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Date and Time:</E>The public workshop will be held on June 4, 2012, 9 a.m. to 5 p.m. and June 5, 2012, 8 a.m. to 5 p.m.</P>
          <P>
            <E T="03">Location:</E>The public workshop will be held at the Renaissance Baltimore Harborplace Hotel, 202 E. Pratt St., Baltimore, MD 21202, 1-800-535-1201.</P>
          <P>
            <E T="03">Contact Persons: FDA Contact:</E>Rhonda Hill, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 4341, Silver Spring, MD 20993, 301-796-3267,<E T="03">rhonda.hill@fda.hhs.gov.</E>
          </P>
          <P>
            <E T="03">ISPE Contact:</E>Julianne Rill, Continuing Education Program Manager, 600 N. Westshore Blvd., Suite 900, Tampa, FL 33609; Web site:<E T="03">http://www.ispe.org/2012-gmp-conference;</E>email:<E T="03">jrill@ispe.org.</E>(FDA has verified the Web site address in this announcement but we are not responsible for any subsequent changes to the Web site in this announcement after this document publishes in the<E T="04">Federal Register.</E>)</P>
          <P>
            <E T="03">Accommodations:</E>Attendees are responsible for their own accommodations. Please mention ISPE/FDA Conference to receive the hotel room rate of $195.00 plus applicable taxes (available until May 7, 2012, or until the ISPE room block is filled).</P>

          <P>If you need special accommodations due to a disability, please contact ISPE (see<E T="03">Contact Persons</E>) at least 7 days in advance of the meeting.</P>
          <P>
            <E T="03">Registration:</E>The ISPE registration fees cover the cost of facilities, materials, and refreshments. Seats are limited; please submit your registration as soon as possible. Workshop space will be filled in order of receipt of registration. Those accepted for the workshop will receive confirmation. Registration will close after the workshop is filled.</P>
        </DATES>
        <GPOTABLE CDEF="s100,xs44" COLS="2" OPTS="L2,p1,8/9,il">
          <TTITLE>Cost of Registration</TTITLE>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1"/>
          </BOXHD>
          <ROW>
            <ENT I="01">ISPE member</ENT>
            <ENT>$1,695</ENT>
          </ROW>
          <ROW>
            <ENT I="01">ISPE nonmember (includes membership)</ENT>
            <ENT>2,035</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Federal Government</ENT>
            <ENT>750</ENT>
          </ROW>
          <ROW>
            <ENT I="01">FDA Planning Committee members and invited speakers</ENT>
            <ENT>Fee waived.</ENT>
          </ROW>
        </GPOTABLE>
        <P>Please visit ISPE's Web site to confirm the prevailing registration fees.</P>

        <P>To register, please submit a registration form with your name, affiliation, mailing address, telephone, fax number, and email, along with a check or money order payable to “ISPE.” To register via the Internet, go to<E T="03">http://www.ispe.org/2012-gmp-conference.</E>The registrar will accept payment by major credit card (Visa/MasterCard/AMEX only). For more information on the meeting registration, or for questions on the workshop, contact ISPE (see<E T="03">Contact Persons</E>).</P>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The workshop helps fulfill the Department of Health and Human Services' and FDA's important mission to protect the public health. The workshop will provide those engaged in FDA-regulated drug manufacturing operations with information on a number of topics concerning FDA requirements and expectations related to current good manufacturing practice (CGMP). The joint public workshop offers the opportunity for participants to join FDA representatives and industry experts in face-to-face dialogues. Each year, FDA speakers provide updates on current efforts affecting the development of global regulatory strategies, while industry professionals from some of today's leading pharmaceutical companies present case studies on how they employ strategies to manufacture high quality drugs in their daily processes. Through a series of sessions and meetings, the conference will provide participants with the opportunity to hear directly from FDA experts and representatives of global regulatory authorities on best practices. Topics for discussion include the following: (1) The Business Case For Change; (2) Quality Risk Management—When, What, and How; (3) Sustaining Compliance Consistency Throughout Your Company and Supplier Network; (4) IT Strategies—Cloud Computing, RFID, and Beyond; (5) The Future of Drug Manufacturing. To help ensure the quality of FDA regulated products, the workshop helps to achieve objectives set forth in section 406 of the FDA Modernization Act of 1997 (Pub. L. 105-115), which includes working closely with stakeholders and maximizing the availability and clarity of information to stakeholders and the public. The workshop also is consistent with the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), as outreach activities by Government Agencies to small businesses.</P>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Leslie Kux,</NAME>
          <TITLE>Assistant Commissioner for Policy.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10894 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-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-2012-N-0001]</DEPDOC>
        <SUBJECT>Educational Forum on Medical Device Reporting, Complaint Files, and Recalls, Corrections, and Removals; Public Workshop</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food and Drug Administration, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of public workshop.</P>
        </ACT>
        <P>The Food and Drug Administration (FDA), Office of Regulatory Affairs (ORA), Southwest Region (SWR), Dallas District Office (DALDO), in collaboration with the FDA Medical Device Industry Coalition (FMDIC), is announcing a public workshop entitled “Educational Forum on Medical Device Reporting, Complaint Files, and Recalls, Corrections, and Removals.” The purpose of the public workshop is to provide information about FDA's Medical Device Quality Systems Regulation (QSR) to the regulated industry, particularly small businesses.</P>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Date and Time:</E>The public workshop will be held on June 15, 2012, from 8 a.m. to 5 p.m.</P>
          <P>
            <E T="03">Location:</E>The public workshop will be held at the Renaissance Dallas Hotel, 2222 Stemmons Freeway, Dallas, TX 75207. Directions and lodging information are available at the FMDIC Web site at<E T="03">http://www.fmdic.org/.</E>
          </P>
          <P>
            <E T="03">Contact Person:</E>David Arvelo, Food and Drug Administration, 4040 North Central Expressway, Suite 900, Dallas, TX 75204, 214-253-4952, FAX: 214-253-4970, email<E T="03">david.arvelo@fda.hhs.gov.</E>
          </P>
          <P>
            <E T="03">Registration:</E>FMDIC has a $250 early registration fee. Discounts for full-time students and government employees with valid identification are available. Early registration ends June 1, 2012. Registration is $300 thereafter. For more information on fees and/or to register online, please visit<E T="03">http://www.fmdic.org/.</E>As an alternative, you may send registration information including name, title, firm name, address, telephone and fax numbers, and email, along with a check or money order for the appropriate amount payable to the FMDIC, to FMDIC Registrar, 4447 N. Central Expressway, Suite 110 PMB197, Dallas, TX 75205.<PRTPAGE P="26770"/>Registration on site will be accepted on a space available basis on the day of the public workshop beginning at 7:30 a.m. Please note that due to popularity, similar past events have reached maximum capacity well before the day of the event. The cost of registration at the site is $300 payable to the FMDIC. The registration fee will be used to offset expenses of hosting the event including continental breakfast, lunch, refreshments, venue, materials, audiovisual equipment, and other logistics associated with this event.</P>

          <P>If you need special accommodations due to a disability, please contact David Arvelo (see<E T="03">Contact Person</E>) at least 21 days in advance.</P>
        </DATES>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The workshop is being held in response to the interest in the topics discussed from small medical device manufacturers in the Dallas District area. This workshop helps achieve objectives set forth in section 406 of the Food and Drug Administration Modernization Act of 1997 (21 U.S.C. 393), which include working closely with stakeholders and maximizing the availability and clarity of information to stakeholders and the public. This is also consistent with the purposes of FDA's Regional Small Business Program, which are in part to respond to industry inquiries, develop educational materials, sponsor workshops and conferences to provide firms, particularly small businesses, with firsthand working knowledge of FDA's requirements and compliance policies. This workshop is also consistent with the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), as an outreach activity by Government agencies to small businesses.</P>
        <P>The goal of the workshop is to present information that will enable manufacturers and regulated industry to better comply with the Medical Device QSR. The following topics will be discussed at the workshop: (1) The role of complaint files, (2) medical device reporting, (3) medical device recalls, corrections, and removals, and (4) Corrective and Preventive Actions as They Relate to Complaints.</P>
        <P>
          <E T="03">Transcripts:</E>Transcripts of this event will not be available due to the format of this workshop. Handouts will be posted online at<E T="03">http://www.fmdic.org/</E>or may be requested in writing from David Arvelo (see<E T="03">Contact Person</E>), after the public workshop.</P>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Leslie Kux,</NAME>
          <TITLE>Assistant Commissioner for Policy.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10893 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-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 on Aging; Notice of Closed Meetings</SUBJECT>
        <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), 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 on Aging Special Emphasis Panel; Presenilin and Alzheimer's Disease.</P>
          <P>
            <E T="03">Date:</E>June 4, 2012.</P>
          <P>
            <E T="03">Time:</E>12:00 p.m. to 3:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>National Institute on Aging, Gateway Building, 7201 Wisconsin Avenue, Suite 2C212, Bethesda, MD 20892. (Telephone Conference Call).</P>
          <P>
            <E T="03">Contact Person:</E>Alexander Parsadanian, Ph.D., Scientific Review Officer, National Institute on Aging, Gateway Building 2C/212, 7201 Wisconsin Avenue, Bethesda, MD 20892, 301-496-9666,<E T="03">parsadaniana@nia.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>National Institute on Aging Special Emphasis Panel; Signal Transduction and AD.</P>
          <P>
            <E T="03">Date:</E>June 20, 2012.</P>
          <P>
            <E T="03">Time:</E>11:45 a.m. to 3:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>National Institute on Aging, Gateway Building, 7201 Wisconsin Avenue, Suite 2C212, Bethesda, MD 20892. (Telephone Conference Call).</P>
          <P>
            <E T="03">Contact Person:</E>Alexander Parsadanian, Ph.D., Scientific Review Officer, National Institute on Aging, Gateway Building 2C/212, 7201 Wisconsin Avenue, Bethesda, MD 20892, 301-496-9666,<E T="03">parsadaniana@nia.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>National Institute on Aging Special Emphasis Panel Cognitive Decline in Aging Monkeys.</P>
          <P>
            <E T="03">Date:</E>June 29, 2012.</P>
          <P>
            <E T="03">Time:</E>11:00 a.m. to 3:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>National Institute on Aging, Gateway Building, 7201 Wisconsin Avenue, Suite 2C212, Bethesda, MD 20892. (Telephone Conference Call).</P>
          <P>
            <E T="03">Contact Person:</E>Alexander Parsadanian, Ph.D., Scientific Review Officer, National Institute on Aging, Gateway Building 2c/212, 7201 Wisconsin Avenue, Bethesda, MD 20892, 301-496-9666,<E T="03">parsadaniana@nia.nih.gov.</E>
          </P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.866, Aging Research, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Jennifer S. Spaeth,</NAME>
          <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10965 Filed 5-4-12; 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 on Alcohol Abuse and Alcoholism; Notice of Closed Meeting</SUBJECT>
        <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.</P>
        <P>The meeting will be closed to the public in accordance with the provisions set forth in sections552b(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 on Alcohol Abuse and Alcoholism Special EmphasisPanel;Review of RFA AA-12-008.</P>
          <P>
            <E T="03">Date:</E>May 23-24, 2012.</P>
          <P>
            <E T="03">Time:</E>9:00 a.m. to 6:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>NIAAA, National Institutes of Health,5635 Fishers Lane,Rockville, MD 20852 (Virtual Meeting).</P>
          <P>
            <E T="03">Contact Person:</E>Ranga Srinivas, Ph.D.,Chief, Extramural Project Review Branch EPRB, NIAAA,National Institutes of Health,5365 Fishers Lane,Room 2085,Rockville, MD 20852, (301) 451-2067,<E T="03">srinivar@mail.nih.gov.</E>
          </P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.271, Alcohol Research Career Development Awards for Scientists and Clinicians; 93.272, Alcohol National Research Service Awards for Research Training; 93.273, Alcohol Research Programs; 93.891, Alcohol Research Center Grants; 93.701, ARRA Related Biomedical Research and Research Support Awards, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <PRTPAGE P="26771"/>
          <DATED>Dated: April 30, 2012.</DATED>
          <NAME>Jennifer S. Spaeth,</NAME>
          <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10978 Filed 5-4-12; 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>Office of the Director, National Institutes of Health Notice of Meeting</SUBJECT>
        <P>Pursuant to section 10(a) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of a meeting of the Scientific Management Review Board.</P>
        <P>The NIH Reform Act of 2006 (Pub. L. 109-482) provides organizational authorities to HHS and NIH officials to: (1) Establish or abolish national research institutes; (2) reorganize the offices within the Office of the Director, NIH including adding, removing, or transferring the functions of such offices or establishing or terminating such offices; and (3) reorganize, divisions, centers, or other administrative units within an NIH national research institute or national center including adding, removing, or transferring the functions of such units, or establishing or terminating such units. The purpose of the Scientific Management Review Board (also referred to as SMRB or Board) is to advise appropriate HHS and NIH officials on the use of these organizational authorities and identify the reasons underlying the recommendations.The meeting will be open to the public through teleconference at the number listed below.</P>
        
        <EXTRACT>
          <P>
            <E T="03">Name of Committee:</E>Scientific Management Review Board.</P>
          <P>
            <E T="03">Date:</E>May 29, 2012.</P>
          <P>
            <E T="03">Time:</E>12:15 p.m. to 2:15 p.m.</P>
          <P>
            <E T="03">Agenda:</E>Presentation and discussion will focus on the most recent charge tothe SMRB, which entails recommending strategies for how NIH canoptimize its utilization on the Small Business Innovation Research andSmall Business Technology Transfer programs in keeping with theNIH mission. The Board will also discuss next steps regarding futureSMRB activities. Further information for this meeting, including theagenda will be available at<E T="03">http://smrb.od.nih.gov</E>. Time will beallotted on the agenda for public comment. To sign up for publiccomment, please submit your name and affiliation to the contactperson listed below by May 25, 2012. Sign up will be restricted to onesign up per email.In the event that time does not allow for all those interested topresent oral comments, anyone may file written commentsusing the contact person's address below.</P>
          <P>The toll-free number to participate in the teleconference is1-800-779-1545. Indicate to the conference operator that yourParticipant pass code is “NIH.”</P>
          <P>
            <E T="03">Place:</E>National Institutes of Health,Office of the Director, NIH,Office of Science Policy,6705 Rockledge Drive, Suite 750,Bethesda, MD 20892(Telephone Conference Call).</P>
          <P>
            <E T="03">Contact Person:</E>Lyric Jorgenson, Ph.D.,Office of Science Policy,Office of the Director, NIH,National Institutes of Health,6705 Rockledge Drive, Suite 750,Bethesda, MD 20892,<E T="03">smrb@mail.nih.gov</E>,(301) 496-6837.</P>
          
          <P>Any interested person may file written comments with the committee by forwarding the statement to the Contact Person listed on this notice. The statement should include the name, address, telephone number and when applicable, the business or professional affiliation of the interested person.</P>

          <P>The draft meeting agenda, meeting materials, dial-in information, and other information about the SMRB, will be available at<E T="03">http://smrb.od.nih.gov.</E>
          </P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.14, Intramural Research Training Award; 93.22, Clinical Research Loan Repayment Program for Individuals from Disadvantaged Backgrounds; 93.232, Loan Repayment Program for Research Generally; 93.39, Academic Research Enhancement Award; 93.936, NIH Acquired Immunodeficiency Syndrome Research Loan Repayment Program; 93.187, Undergraduate Scholarship Program for Individuals from Disadvantaged Backgrounds, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Jennifer S. Spaeth,</NAME>
          <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10967 Filed 5-4-12; 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>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
        <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), 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>Center for Scientific Review Special Emphasis Panel; Program Project: Statistical Genetics.</P>
          <P>
            <E T="03">Date:</E>May 24, 2012.</P>
          <P>
            <E T="03">Time:</E>1:00 p.m. to 6:00 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, 6701 Rockledge Drive, Bethesda, MD 20892 (Virtual Meeting).</P>
          <P>
            <E T="03">Contact Person:</E>Richard Panniers, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 2212, MSC 7890, Bethesda, MD 20892, (301) 435-1741,<E T="03">pannierr@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Center for Scientific Review Special Emphasis Panel; Motor Coordination.</P>
          <P>
            <E T="03">Date:</E>May 25, 2012.</P>
          <P>
            <E T="03">Time:</E>1:00 p.m. to 3:00 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, 6701 Rockledge Drive, Bethesda, MD 20892 (Telephone Conference Call).</P>
          <P>
            <E T="03">Contact Person:</E>Priscilla B Chen, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4104, MSC 7814, Bethesda, MD 20892, (301) 435-1787,<E T="03">chenp@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Emerging Technologies and Training Neurosciences Integrated Review Group; Bioengineering of Neuroscience, Vision and Low Vision Technologies Study Section.</P>
          <P>
            <E T="03">Date:</E>May 30, 2012.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 4:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Mayflower Park Seattle, 405 Olive Way, Seattle, WA 98101.</P>
          <P>
            <E T="03">Contact Person:</E>Robert C Elliott, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5190, MSC 7846, Bethesda, MD 20892, 301-435-3009,<E T="03">elliotro@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Center for Scientific Review Special Emphasis Panel; PAR 10-234: Neurotechnology Bioengineering Research Partnerships.</P>
          <P>
            <E T="03">Date:</E>May 30, 2012.</P>
          <P>
            <E T="03">Time:</E>4:00 p.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Mayflower Park Seattle, 405 Olive Way, Seattle, WA 98101.</P>
          <P>
            <E T="03">Contact Person:</E>Robert C Elliott, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 3130, MSC 7850, Bethesda, MD 20892, 301-435-3009,<E T="03">elliotro@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Center for Scientific Review Special Emphasis Panel; PAR 12-053: Advanced Neural Prosthetics R&amp;D.</P>
          <P>
            <E T="03">Date:</E>May 30, 2012.</P>
          <P>
            <E T="03">Time:</E>5:00 p.m. to 6:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Mayflower Park Seattle, 405 Olive Way, Seattle, WA 98101.</P>
          <P>
            <E T="03">Contact Person:</E>Robert C Elliott, Ph.D., Scientific Review Officer, Center for<PRTPAGE P="26772"/>Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 3130, MSC 7850, Bethesda, MD 20892, 301-435-3009,<E T="03">elliotro@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Center for Scientific Review Special Emphasis Panel; PAR Panel: FIRCA and GRIP Review.</P>
          <P>
            <E T="03">Date:</E>May 31-June 1, 2012.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Hotel Monaco Washington DC, 700 F Street NW., Washington, DC 20004.</P>
          <P>
            <E T="03">Contact Person:</E>Hilary D Sigmon, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5222, MSC 7852, Bethesda, MD 20892, (301) 594-6377,<E T="03">sigmonh@csr.nih.gov.</E>
          </P>
          <P>
            <E T="03">Name of Committee:</E>Center for Scientific Review Special Emphasis Panel; Member Conflict: Obesity-Clinical Research.</P>
          <P>
            <E T="03">Date:</E>June 1, 2012.</P>
          <P>
            <E T="03">Time:</E>10:00 a.m. to 3:30 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, 6701 Rockledge Drive, Bethesda, MD 20892, (Virtual Meeting).</P>
          <P>
            <E T="03">Contact Person:</E>Krish Krishnan, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6164, MSC 7892, Bethesda, MD 20892, (301) 435-1041,<E T="03">krishnak@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Healthcare Delivery and Methodologies Integrated Review Group; Societal and Ethical Issues in Research Study Section.</P>
          <P>
            <E T="03">Date:</E>June 4, 2012.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 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>Karin F Helmers, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 3166, MSC 7770, Bethesda, MD 20892, 301-254-9975,<E T="03">helmersk@csr.nih.gov.</E>
          </P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Jennifer S. Spaeth,</NAME>
          <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10969 Filed 5-4-12; 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 Cancer Institute; Notice of Meeting</SUBJECT>
        <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the meeting of the NCI-Frederick Advisory Committee.</P>
        <P>The meeting will be open to the public as indicated below, with attendance limited to space available. Individuals who plan to attend and need special assistance, such as sign language interpretation or other reasonable accommodations, should notify the Contact Person listed below in advance of the meeting.</P>
        <P>A portion of the meeting will be closed to the public in accordance with the provisions set forth in section 552b(c)(9)(B), Title 5 U.S.C., as amended. The premature disclosure of information to be discussed during the meeting would significantly frustrate implementation of a proposed agency action.</P>
        
        <EXTRACT>
          <P>
            <E T="03">Name of Committee:</E>NCI-Frederick Advisory Committee.</P>
          <P>
            <E T="03">Open:</E>May 30, 2012, 9:00 a.m. to 11:00 a.m.</P>
          <P>
            <E T="03">Agenda:</E>Ongoing and New Business and Scientific Presentations.</P>
          <P>
            <E T="03">Place:</E>National Institutes of Health, 9000 Rockville Pike, Building 31, C Wing, 6th Floor, Conference Room 10, Bethesda, MD 20892.</P>
          <P>
            <E T="03">Closed:</E>May 30, 2012, 11:00 a.m. to 3:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>Discussion of Proposed Frederick National Laboratory Strategic Plan.</P>
          <P>
            <E T="03">Place:</E>National Institutes of Health, 9000 Rockville Pike, Building 31, C Wing, 6th Floor, Conference Room 10, Bethesda, MD 20892.</P>
          <P>
            <E T="03">Contact Person:</E>Thomas M. Vollberg, Sr., Ph.D., Executive Secretary, National Cancer Institute, National Institutes of Health, 6116 Executive Boulevard, 7th Floor, Room 7142, Bethesda, MD 20892-8327, (301) 694-9582.</P>
          <P>Any interested person may file written comments with the committee by forwarding the statement to the Contact Person listed on this notice. The statement should include the name, address, telephone number and when applicable, the business or professional affiliation of the interested person.</P>
          <P>In the interest of security, NIH has instituted stringent procedures for entrance onto the NIH campus. All visitor vehicles, including taxicabs, hotel, and airport shuttles will be inspected before being allowed on campus. Visitors will be asked to show one form of identification (for example, a government-issued photo ID, driver's license, or passport) and to state the purpose of their visit.</P>

          <P>Information is also available on the Institute's/Center's home page:<E T="03">http://deainfo.nci.nih.gov/advisory/fac/fac.htm,</E>where an agenda and any additional information for the meeting will be posted when available.</P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.392, Cancer Construction; 93.393, Cancer Cause and Prevention Research; 93.394, Cancer Detection and Diagnosis Research; 93.395, Cancer Treatment Research; 93.396, Cancer Biology Research; 93.397, Cancer Centers Support; 93.398, Cancer Research Manpower; 93.399, Cancer Control, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: April 27, 2012.</DATED>
          <NAME>Jennifer S. Spaeth,</NAME>
          <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10964 Filed 5-4-12; 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>Prospective Grant of Exclusive License: Ocular Therapeutics Agent Delivery Devices and Methods for Making and Using Such Devices</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 404.7(a)(1)(i), that the National Institutes of Health (NIH), Department of Health and Human Services, is contemplating the grant of an exclusive patent license to practice the inventions embodied in Patent Applications USSN 09/808,149, filed Mar 15, 2001, issued Mar 30, 2004; PCT/US02/07836, filed Mar 14, 2002, designated EP, 02723446,7 and US 10/471,468, issued Feb 9, 2010; USSN 11/739,540, filed Apr 29, 2007; and USSN 12/647,980, filed Dec 28, 2009; entitled “Ocular Therapeutic Agent Delivery Devices and Methods For Making and Using Such Devices”, by Michael R. Robinson<E T="03">et al</E>(NEI, CC, and NIBIB) (E-241-1999/0), to ODIN Biotech having a place of business in 4000 Hanover Street, Dallas, TX. The patent rights in this invention have been assigned to the United States of America. The exclusive patent license is one which qualifies under the Start-up Exclusive Patent License Agreement program, which is in place from October 1, 2011 through September 30, 2012.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Only written comments and/or application for a license that are received by the NIH Office of Technology Transfer on or before May 22, 2012 will be considered.</P>
        </DATES>
        <FURINF>
          <PRTPAGE P="26773"/>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Requests for a copy of the patent application, inquiries, and comments relating to the contemplated license should be directed to: Susan Ano, Ph.D., Branch Chief, IDME, Office of Technology Transfer, National Institutes of Health, 6011 Executive Boulevard, Suite 325, Rockville, MD 20852-3804; Email:<E T="03">anos@mail.nih.gov;</E>Telephone: 301-435-5515; Facsimile: 301-402-0220.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The invention relates to a drug delivery system, compositions of, methods of making the drug delivery system, and methods of use as a drug delivery platform. Ocular therapeutics that require repeated intravitreal injections are associated with eye infections, retinal detachment, hemorrhaging, endophthalmitis, and/or cataracts, while topical solutions that require daily application are associated with patient non-compliance. This technology describes a drug delivery platform that can be designed to deliver therapeutics to the eye over months to years. Therefore, this technology can be used to design a therapeutic implant that reduces or eliminates patient non-compliance and/or improve patient safety. The therapeutic implant has the following advantages: (a) It is bioerodible which makes it more noninvasive than repeated intravitreal injections and non-bioerodible implants; (b) has a dual release system that allows the release of two distinct therapeutics or a single therapeutic at different rates; (c) prolongs the therapeutic dose of an agent across the surface of the eye compared to topical solutions; (d) reduces the risk of additional eye damage compared to repeated intravitreal injections; (e) dispenses a therapeutic agent over a long period of time resulting in increase patient compliance and patient health; and (f) is associated with reduced systemic drug side-effects compared to drugs applied systemically. Data are available for rodents, rabbits, dogs, and horses.</P>
        <P>The field of use may be limited to “Episcleral Therapeutic Implant for Ophthalmic Diseases”.</P>
        <P>The prospective worldwide exclusive license will be royalty bearing and will comply with the terms and conditions of 35 U.S.C. 209 and 37 CFR 404.7. The prospective exclusive license may be granted unless, within fifteen (15) days from the date of this published Notice, 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 404.7.</P>
        <P>Properly filed competing applications for a license filed in response to this notice will be treated as objections to the contemplated license. Comments and objections submitted in response 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: May 1, 2012.</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. 2012-10836 Filed 5-4-12; 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>Substance Abuse and Mental Health Services Administration</SUBAGY>
        <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request</SUBJECT>
        <P>In compliance with Section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995 concerning opportunity for public comment on proposed collections of information, the Substance Abuse and Mental Health Services Administration (SAMHSA) will publish periodic summaries of proposed projects. To request more information on the proposed projects or to obtain a copy of the information collection plans, call the SAMHSA Reports Clearance Officer on (240) 276-1243.</P>
        <P>Comments are invited on: (a) Whether the proposed collections of information are 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; (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 respondents, including through the use of automated collection techniques or other forms of information technology.</P>
        <HD SOURCE="HD1">Proposed Project: Healthy Transitions Initiative Cross-Site Evaluation—NEW</HD>
        <P>The Substance Abuse and Mental Health Services Administration (SAMHSA), Center of Mental Health Services is responsible for the cross-site evaluation of the Cooperative Agreements for State/Community Partnerships to Integrate Services and Supports for Youth and Young Adults 16-25 with Serious Emotional Disturbances (SED) or Serious Mental Illness (SMI), and Their Families (Healthy Transitions Initiative—HTI) that will collect data on program implementation and youth and young adult outcomes in the areas of education, employment, housing, mental health and co-occurring disorders, and involvement with the juvenile and criminal justice systems. This cross-site evaluation design includes a process and an outcome evaluation and data will be collected over a 3-year period from 7 grantee sites.</P>
        <P>The cross-site evaluation is designed to address the following questions.</P>
        <HD SOURCE="HD2">Process Evaluation Questions</HD>
        <P>1. How closely does implementation match the plan proposed in the grant?</P>
        <P>2. What types of deviation from the plan occur?</P>
        <P>3. What effect do the deviations have on the planned intervention and performance assessment?</P>
        <P>4. What facilitates a successful transition between youth and adult systems?</P>
        <P>5. Is there a change from a “youth-guided” model to a “youth and young adult consumer-driven” model?</P>
        <P>6. What is the extent of interagency coordination and collaboration?</P>
        <P>7. How are state and local-level systems changing in response to the HTI implementation? How does state and local-level policy change affect the implementation of the Initiative?</P>
        <P>8. Who provides services (i.e., program staff, agency site)?</P>
        <P>9. What services are being provided (i.e., modality, type, intensity, duration)?</P>
        <P>10. Is there a viable cultural and linguistic competence plan?</P>
        <P>11. What are the individual characteristics of the youth and young adults (i.e., who is being served)?</P>
        <P>12. In what settings (i.e., system, community) are they being served?</P>
        <HD SOURCE="HD2">Outcome Evaluation Questions</HD>
        <P>1. What is the effect of the HTI intervention on the participants?</P>
        <P>2. What is the effect of the HTI intervention, compared to a sample of similar young adults not participating in the HTI intervention?</P>
        <P>3. What program factors are associated with the observed outcomes?</P>
        <P>4. What individual factors are associated with the observed outcomes?</P>
        <P>5. How durable are the effects over 24 months?<PRTPAGE P="26774"/>
        </P>
        <HD SOURCE="HD2">Process Evaluation</HD>
        <P>The process evaluation is designed to assess the fidelity of grantees to implement their proposed program model, and consists of young person focus groups, young person surveys, youth mentor focus groups, transitional program personnel interviews and surveys, and local and state administrator interviews. Process evaluation data will be collected in two waves during FY 2012 and during FY 2014 and, with the exception of the state administrator interviews, participants are not expected to participate more than one time during the 2 waves of data collection.</P>
        <HD SOURCE="HD2">Outcome Evaluation</HD>
        <P>The outcome evaluation is designed to assess outcomes of youth and young adults in regards to education, employment, housing, mental health and co-occurring disorders, and involvement with the juvenile and criminal justice systems. The outcome evaluation will utilize both an enhanced and standard data collection and a longitudinal cohort design, and will include a comparative study to assess the effectiveness of HTI relative to a similar sample of young persons who did not receive HTI services. In the standard data collection protocol, outcome data will be collected for each HTI young adult participant, at a minimum of, at baseline at least every 6 months for up to 24 months for as long as the participant remains in HTI services. Enhanced outcome data will be collected on a subsample of young adults at 6 month intervals. The enhanced protocol will continue even after the young person from the subsample has left or has been discharged from HTI services, for up to 24 months. The baseline and follow up outcome instruments include the following key indicators: Demographic information, service use, education, employment/vocational training, housing and living situation, clinical outcomes, behavioral and other health, trauma-related experiences, life skills, parenting skills and supports, involvement with juvenile or criminal justice systems, and social and peer relationships. While participants are enrolled in HTI services, these data collected by the HTI grantees as specified in the RFA.</P>
        <P>The HTI Data Center (HTI DC) will be developed for data collection and management. The HTI DC will be a secure Web site that allows uploading of data, real-time access to data by grantees, and production of automated reports for the sites. It is flexible for local use and simplifies the management, monitoring, and reporting of data.</P>
        <P>The summary burden reflects the distinct number of respondents, total annual burden, and total hourly cost of the study.</P>
        <GPOTABLE CDEF="s50,12,12,12,12,12,12,12" COLS="8" OPTS="L2,i1">
          <TTITLE>Summary Burden Table</TTITLE>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1">Number of<LI>distinct</LI>
              <LI>respondents</LI>
            </CHED>
            <CHED H="1">Average annual number responses/<LI>respondent</LI>
            </CHED>
            <CHED H="1">Total annual number of<LI>responses</LI>
            </CHED>
            <CHED H="1">Average 3-year burden per response (hours)</CHED>
            <CHED H="1">Total annual burden<LI>(hours)</LI>
            </CHED>
            <CHED H="1">Hourly wage cost</CHED>
            <CHED H="1">Total hourly cost*</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Young Persons</ENT>
            <ENT>320</ENT>
            <ENT>1.10</ENT>
            <ENT>796</ENT>
            <ENT>1.55</ENT>
            <ENT>547</ENT>
            <ENT>
              <SU>a</SU>$7.25</ENT>
            <ENT>$3966</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Youth Mentors</ENT>
            <ENT>84</ENT>
            <ENT>0.33</ENT>
            <ENT>28</ENT>
            <ENT>1.25</ENT>
            <ENT>35</ENT>
            <ENT>
              <SU>b</SU>10.74</ENT>
            <ENT>376</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Transitional Program Personnel</ENT>
            <ENT>49</ENT>
            <ENT>0.33</ENT>
            <ENT>23</ENT>
            <ENT>1.41</ENT>
            <ENT>23</ENT>
            <ENT>
              <SU>c</SU>15.24</ENT>
            <ENT>351</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Local Administrators</ENT>
            <ENT>21</ENT>
            <ENT>0.67</ENT>
            <ENT>14</ENT>
            <ENT>1.50</ENT>
            <ENT>21</ENT>
            <ENT>
              <SU>d</SU>22.69</ENT>
            <ENT>476</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">State Administrators</ENT>
            <ENT>7</ENT>
            <ENT>0.67</ENT>
            <ENT>9</ENT>
            <ENT>0.54</ENT>
            <ENT>3</ENT>
            <ENT>
              <SU>e</SU>23.54</ENT>
            <ENT>220</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Total Summary</ENT>
            <ENT>481</ENT>
            <ENT>3</ENT>
            <ENT>871</ENT>
            <ENT/>
            <ENT>629</ENT>
            <ENT/>
            <ENT>5,389</ENT>
          </ROW>
        </GPOTABLE>

        <P>Send comments to Summer King, SAMHSA Reports Clearance Officer, Room 8-1099, One Choke Cherry Road, Rockville, MD 20857 or email a copy to<E T="03">summer.king@samhsa.hhs.gov.</E>Written comments must be received before 60 days after the date of the publication in the<E T="04">Federal Register</E>.</P>
        <SIG>
          <NAME>Summer King,</NAME>
          <TITLE>Statistician.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-10882 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4162-20-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <DEPDOC>[Docket No. DHS-2012-0021]</DEPDOC>
        <SUBJECT>Homeland Security Advisory Council</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>The Office of Policy, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of partially closed federal advisory committee meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Homeland Security Advisory Council (HSAC) will meet in person and members of the public may participate by conference call on May 24, 2012. The meeting will be partially closed to the public.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The HSAC will meet on Thursday, May 24, 2012, from 9:00 a.m. to 3:00 p.m. EDT. The portion of the meeting from 9:00 a.m. to 12:45 p.m. will be closed to the public. The meeting will be open to the public from 1:00 p.m. to 3:00 p.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Written comments must be submitted and received by May 22, 2012. Comments must be identified by Docket No. DHS-2012-0021 and may be submitted by<E T="03">one</E>of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>
            <E T="03">http://www.regulations.gov</E>. Follow the instructions for submitting comments.</P>
          <P>•<E T="03">E-mail:</E>
            <E T="03">HSAC@dhs.gov</E>. Include docket number in the subject line of the message.</P>
          <P>•<E T="03">Fax:</E>(202) 282-9207.</P>
          <P>•<E T="03">Mail:</E>Homeland Security Advisory Council, Department of Homeland Security, Mailstop 0450, 245 Murray Lane SW., Washington, DC 20528.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the words “Department of Homeland Security” and DHS-2012-0021, the docket number for this action. Comments received will be posted without alteration at<E T="03">http://www.regulations.gov</E>, including any personal information provided.</P>
          <P>
            <E T="03">Docket:</E>For access to the docket to read background documents or comments received by the DHS Homeland Security Advisory Council, go to<E T="03">http://www.regulations.gov</E>.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>HSAC Staff at<E T="03">hsac@dhs.gov</E>or 202-447-3135.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Notice of this meeting is given under the Federal Advisory Committee Act, 5 U.S.C. App.</P>

        <P>The HSAC provides organizationally independent, strategic, timely, specific and actionable advice and recommendations for the consideration of the Secretary of the Department of<PRTPAGE P="26775"/>Homeland Security on matters related to homeland security. The Council is comprised of leaders of local law enforcement, first responders, state and local government, the private sector, and academia.</P>
        <P>The HSAC will meet from 9:00 a.m. to 3:00 p.m. The HSAC will receive updates from the U.S. Coast Guard on “Counterterrorism Efforts Around the World” and from the Transportation Security Administration on threats to airport security, receive observations and remarks from DHS senior leadership, and review and deliberate on recommendations from the HSAC Faith-based Security and Communications Advisory Committee.</P>
        <P>The HSAC will meet in closed session from 9:00 a.m. to 12:45 p.m. to receive sensitive operational information from senior DHS leadership on threats to our homeland security, border security, U.S. Coast Guard counterterrorism efforts, and an operational overview of the Transportation Security Administration's (TSA) airport security.</P>
        <P>
          <E T="03">Basis for Partial-Closure:</E>In accordance with Section 10(d) of the Federal Advisory Committee Act, it has been determined that the meeting requires closure as the disclosure of the information would not be in the public interest.</P>
        <P>The HSAC will receive briefings on domestic and international threats to the homeland from DHS Intelligence and Analysis and other senior leadership, and a briefing on the Transportation Security Administration's (TSA) airport security program that will include lessons learned, and screening techniques associated with airport security. Specifically, there will be material presented regarding the latest viable threats against the United States, and how DHS and other Federal agencies plan to address those threats. Under 5 U.S.C. 552b(c)(7)(E), disclosure of that information could reveal investigative techniques and procedures not generally available to the public, allowing those with interests against the United States to circumvent the law. Additionally, under 5 U.S.C. 552b(c)(9)(B), disclosure of these techniques and procedures could frustrate the successful implementation of protective measures designed to keep our country safe.</P>
        <P>Members will also be provided a briefing from the U.S. Coast Guard on counterterrorism efforts being made around the world. Providing this information to the public would provide terrorists with a road map regarding the Department's plan to counter their actions, and thus, allow them to take different actions to avoid counterterrorism efforts. Under 5 U.S.C. 552b(c)(7)(E), disclosure of that information could endanger the life or physical safety of law enforcement personnel. Additionally, under 5 U.S.C. 552b(c)(9)(B), disclosure of this plan could frustrate the successful implementation of measures designed to counter terrorist acts.</P>
        <P>
          <E T="03">Public Participation:</E>Members of the public will be in listen-only mode. The public may register to participate in this HSAC conference call aforementioned procedures. Each individual must provide his or her full legal name, email address and phone number no later than 5:00 p.m. EDT on May 22, 2012, to a staff member of the HSAC via email at<E T="03">HSAC@dhs.gov</E>or via phone at (202) 447-3135. HSAC webcast details and the Faith-based Security and Communications Advisory Committee report will be provided to interested members of the public at the time they register.</P>
        <P>
          <E T="03">Identification of Services for Individuals with Disabilities:</E>For information on facilities or services for individuals with disabilities, or to request special assistance at the meeting, contact the HSAC as soon as possible.</P>
        <SIG>
          <DATED>Dated: May 1, 2012.</DATED>
          <NAME>Becca Sharp,</NAME>
          <TITLE>Executive Director, Homeland Security Advisory Council, DHS.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10930 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-9M-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Federal Emergency Management Agency</SUBAGY>
        <DEPDOC>[Internal Agency Docket No. FEMA-4057-DR; Docket ID FEMA-2012-0002]</DEPDOC>
        <SUBJECT>Kentucky; Amendment No. 6 to Notice of a Major Disaster Declaration</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Emergency Management Agency, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This notice amends the notice of a major disaster declaration for the Commonwealth of Kentucky (FEMA-4057-DR), dated March 6, 2012, and related determinations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>April 12, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Peggy Miller, Office of Response and Recovery, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472, (202) 646-3886.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The notice of a major disaster declaration for the Commonwealth of Kentucky is hereby amended to include the following areas among those areas determined to have been adversely affected by the event declared a major disaster by the President in his declaration of March 6, 2012.</P>
        
        <EXTRACT>
          <P>Adair County for Public Assistance.</P>
          <P>Bath County for Public Assistance (already designated for Individual Assistance).</P>
          
          <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 97.030, Community Disaster Loans; 97.031, Cora Brown Fund; 97.032, Crisis Counseling; 97.033, Disaster Legal Services; 97.034, Disaster Unemployment Assistance (DUA); 97.046, Fire Management Assistance Grant; 97.048, Disaster Housing Assistance to Individuals and Households in Presidentially Declared Disaster Areas; 97.049, Presidentially Declared Disaster Assistance—Disaster Housing Operations for Individuals and Households; 97.050 Presidentially Declared Disaster Assistance to Individuals and Households—Other Needs; 97.036, Disaster Grants—Public Assistance (Presidentially Declared Disasters); 97.039, Hazard Mitigation Grant.)</FP>
        </EXTRACT>
        <SIG>
          <NAME>W. Craig Fugate,</NAME>
          <TITLE>Administrator, Federal Emergency Management Agency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10905 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9111-23-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Federal Emergency Management Agency</SUBAGY>
        <DEPDOC>[Internal Agency Docket No. FEMA-4061-DR; Docket ID FEMA-2012-0002]</DEPDOC>
        <SUBJECT>West Virginia; Amendment No. 1 to Notice of a Major Disaster Declaration</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Emergency Management Agency, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This notice amends the notice of a major disaster declaration for the State of West Virginia (FEMA-4061-DR), dated March 22, 2012, and related determinations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>March 31, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Peggy Miller, Office of Response and Recovery, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472, (202) 646-3886.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Notice is hereby given that the incident period for this disaster is closed effectiveMarch 31, 2012.</P>
        
        <EXTRACT>

          <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 97.030,<PRTPAGE P="26776"/>Community Disaster Loans; 97.031, Cora Brown Fund; 97.032, Crisis Counseling; 97.033, Disaster Legal Services; 97.034, Disaster Unemployment Assistance (DUA); 97.046, Fire Management Assistance Grant; 97.048, Disaster Housing Assistance to Individuals and Households in Presidentially Declared Disaster Areas; 97.049, Presidentially Declared Disaster Assistance—Disaster Housing Operations for Individuals and Households; 97.050, Presidentially Declared Disaster Assistance to Individuals and Households—Other Needs; 97.036, Disaster Grants—Public Assistance (Presidentially Declared Disasters); 97.039, Hazard Mitigation Grant.)</FP>
        </EXTRACT>
        <SIG>
          <NAME>W. Craig Fugate,</NAME>
          <TITLE>Administrator, Federal Emergency Management Agency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10901 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9111-23-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Federal Emergency Management Agency</SUBAGY>
        <DEPDOC>[Internal Agency Docket No. FEMA-4059-DR; Docket ID FEMA-2012-0002]</DEPDOC>
        <SUBJECT>West Virginia; Amendment No. 1 to Notice of a Major Disaster Declaration</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Emergency Management Agency, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This notice amends the notice of a major disaster declaration for the State of West Virginia (FEMA-4059-DR), dated March 16, 2012, and related determinations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>April 18, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Peggy Miller, Office of Response and Recovery, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472, (202) 646-3886.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The notice of a major disaster declaration for the State of West Virginia is hereby amended to include the following areas among those areas determined to have been adversely affected by the event declared a major disaster by the President in his declaration of March 16, 2012.</P>
        
        <EXTRACT>
          <P>Harrison, Preston, and Taylor Counties for Individual Assistance (already designated for Public Assistance).</P>
          
          <FP>The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 97.030, Community Disaster Loans; 97.031, Cora Brown Fund; 97.032, Crisis Counseling; 97.033, Disaster Legal Services; 97.034, Disaster Unemployment Assistance (DUA); 97.046, Fire Management Assistance Grant; 97.048, Disaster Housing Assistance to Individuals and Households In Presidentially Declared Disaster Areas; 97.049, Presidentially Declared Disaster Assistance—Disaster Housing Operations for Individuals and Households; 97.050 Presidentially Declared Disaster Assistance to Individuals and Households—Other Needs; 97.036, Disaster Grants—Public Assistance (Presidentially Declared Disasters); 97.039, Hazard Mitigation Grant.</FP>
        </EXTRACT>
        <SIG>
          <NAME>W. Craig Fugate,</NAME>
          <TITLE>Administrator, Federal Emergency Management Agency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10902 Filed 5-4-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9111-23-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
        <SUBJECT>Agency Information Collection Activities: Declaration of Persons Who Performed Repairs or Alterations</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>30-Day notice and request for comments; Extension of an existing information collection.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>U.S. Customs and Border Protection (CBP) of the Department of Homeland Security will be submitting the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act: Declaration of Persons Who Performed Repairs or Alterations. This is a proposed extension of an information collection that was previously approved. CBP is proposing that this information collection be extended with no change to the burden hours. This document is published to obtain comments from the public and affected agencies. This information collection was previously published in the<E T="04">Federal Register</E>(77 FR 10762) on February 23, 2012, allowing for a 60-day comment period. This notice allows for an additional 30 days for public comments. This process is conducted in accordance with 5 CFR 1320.10.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments should be received on or before June 6, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Interested persons are invited to submit written comments on this information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the OMB Desk Officer for U.S. Customs and Border Protection, Department of Homeland Security, and sent via electronic mail to<E T="03">oira_submission@omb.eop.gov</E>or faxed to (202) 395-5806.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Requests for additional information should be directed to Tracey Denning, U.S. Customs and Border Protection, Regulations and Rulings, Office of International Trade, 799 9th Street NW., 5th Floor, Washington, DC 20229-1177, at 202-325-0265.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>CBP invites the general public and affected Federal agencies to submit written comments and suggestions on proposed and/or continuing information collection requests pursuant to the Paperwork Reduction Act (Pub. L. 104-13). Your comments should address one of the following four points:</P>
        <P>(1) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency/component, including whether the information will have practical utility;</P>
        <P>(2) Evaluate the accuracy of the agencies/components estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
        <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
        <P>(4) Minimize the burden of the collections of information on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological techniques or other forms of information.</P>
        <P>
          <E T="03">Title:</E>Declaration of Persons Who Performed Repairs or Alterations.</P>
        <P>
          <E T="03">OMB Number:</E>1651-0048.</P>
        <P>
          <E T="03">Form Number:</E>None.</P>
        <P>
          <E T="03">Abstract:</E>The “Declaration of Persons Who Performed Repairs or Alterations,” as required by 19 CFR 10.8, is used in connection with the entry of articles entered under subheadings 9802.00.40 and 9802.00.50, Harmonized Tariff Schedule of the United States (HTSUS). Articles entered under these HTSUS p