<?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>80</NO>
  <DATE>Wednesday, April 25, 2012</DATE>
  <UNITNAME>Contents</UNITNAME>
  <CNTNTS>
    <AGCY>
      <EAR>Agency Health</EAR>
      <PRTPAGE P="iii"/>
      <HD>Agency for Healthcare Research and Quality</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Scientific Information Requests:</SJ>
        <SJDENT>
          <SJDOC>Chronic Venous Ulcers Treatments,</SJDOC>
          <PGS>24718-24719</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9820</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Local Therapies for Treatment of Stage 1 Non-Small Cell Lung Cancer, etc.,</SJDOC>
          <PGS>24717-24718</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9817</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Medical Devices to Treat Otis Media with Effusion,</SJDOC>
          <PGS>24716-24717</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9818</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Agricultural Marketing</EAR>
      <HD>Agricultural Marketing Service</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Tart Cherries Grown in States of Michigan, et al.:</SJ>
        <SJDENT>
          <SJDOC>Increasing Primary Reserve Capacity and Revising Exemption Requirements,</SJDOC>
          <PGS>24640-24643</PGS>
          <FRDOCBP D="3" T="25APP1.sgm">2012-9860</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Agriculture</EAR>
      <HD>Agriculture Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Agricultural Marketing Service</P>
      </SEE>
      <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 Agricultural Statistics Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Rural Business-Cooperative Service</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>24671</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9871</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Arts and Humanities, National Foundation</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Foundation on the Arts and the Humanities</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Consumer Financial Protection</EAR>
      <HD>Bureau of Consumer Financial Protection</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Impact of Overdraft Programs on Consumers,</DOC>
          <PGS>24687</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9851</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Census Bureau</EAR>
      <HD>Census Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>2013-2015 American Community Survey Methods Panel Testing,</SJDOC>
          <PGS>24684-24685</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9939</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Centers Disease</EAR>
      <HD>Centers for Disease Control and Prevention</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Board of Scientific Counselors, National Center for Environmental Health/Agency for Toxic Substances and Disease Registry,</SJDOC>
          <PGS>24720</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9925</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Disease, Disability, and Injury Prevention and Control Special Emphasis Panel,</SJDOC>
          <PGS>24719-24720</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9935</FRDOCBP>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9924</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Children</EAR>
      <HD>Children and Families Administration</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Temporary Assistance to Needy Families:</SJ>
        <SJDENT>
          <SJDOC>Assistance and Electronic Benefit Transfer Transactions; Request for Public Comment,</SJDOC>
          <PGS>24667-24669</PGS>
          <FRDOCBP D="2" T="25APP1.sgm">2012-9260</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Civil Rights</EAR>
      <HD>Civil Rights Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Florida Advisory Committee,</SJDOC>
          <PGS>24683</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9907</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Coast Guard</EAR>
      <HD>Coast Guard</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Great Lakes Pilotage Advisory Committee,</SJDOC>
          <PGS>24729-24730</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9889</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Commerce</EAR>
      <HD>Commerce Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Census Bureau</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Industry and Security Bureau</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>
    </AGCY>
    <AGCY>
      <EAR>Coordinating</EAR>
      <HD>Coordinating Council on Juvenile Justice and Delinquency Prevention</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings,</DOC>
          <PGS>24687-24688</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9846</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Copyright Royalty Board</EAR>
      <HD>Copyright Royalty Board</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Determination of Reasonable Rates and Terms for Noncommercial Broadcasting,</DOC>
          <PGS>24662-24667</PGS>
          <FRDOCBP D="5" T="25APP1.sgm">2012-9927</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Defense Department</EAR>
      <HD>Defense Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Navy Department</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Federal Acquisition Regulation; Transportation Requirements,</SJDOC>
          <PGS>24713-24714</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9829</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Delaware</EAR>
      <HD>Delaware River Basin Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Delaware River Basin Commission and Public Hearing,</SJDOC>
          <PGS>24688-24689</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9947</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Education Department</EAR>
      <HD>Education Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Graduate Assistance in Areas of National Need Performance Report,</SJDOC>
          <PGS>24689</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9990</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Pell Grant, ACG, and National SMART Reporting under the Common Origination and Disbursement System,</SJDOC>
          <PGS>24690</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9993</FRDOCBP>
        </SJDENT>
        <SJ>Exemplary Charter School Collaboration Awards:</SJ>
        <SJDENT>
          <SJDOC>Proposed Definitions, Requirements, and Selection Criteria,</SJDOC>
          <PGS>24690-24694</PGS>
          <FRDOCBP D="4" T="25APN1.sgm">2012-10005</FRDOCBP>
        </SJDENT>
      </CAT>
    </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>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Environmental Management Site-Specific Advisory Board, Nevada,</SJDOC>
          <PGS>24694-24695</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9941</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Environmental Management Site-Specific Advisory Board, Savannah River Site,</SJDOC>
          <PGS>24695</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9942</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Environmental Protection</EAR>
      <HD>Environmental Protection Agency</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Significant New Use Rules on Certain Chemical Substances,</DOC>
          <PGS>24613-24628</PGS>
          <FRDOCBP D="15" T="25APR1.sgm">2012-9965</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Approvals and Promulgations of Air Quality Implementation Plans:</SJ>
        <SJDENT>
          <SJDOC>State of New York; Regional Haze State Implementation Plan and Federal Implementation Plan,</SJDOC>
          <PGS>24794-24827</PGS>
          <FRDOCBP D="33" T="25APP3.sgm">2012-9839</FRDOCBP>
        </SJDENT>
        <PRTPAGE P="iv"/>
        <SJ>Approvals and Promulgations of State Implementation Plans:</SJ>
        <SJDENT>
          <SJDOC>Albuquerque-Bernalillo County, NM; Interstate Transport Affecting Visibility and Regional Haze Rule Requirements, etc.,</SJDOC>
          <PGS>24768-24792</PGS>
          <FRDOCBP D="24" T="25APP2.sgm">2012-9808</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Access to Confidential Business Information by CGI Federal  Inc. and Its Identified Subcontractor, FedConcepts/Jorge,</DOC>
          <PGS>24697-24698</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9640</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>24698-24700</PGS>
          <FRDOCBP D="2" T="25APN1.sgm">2012-9902</FRDOCBP>
        </DOCENT>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Microbial Rules,</SJDOC>
          <PGS>24701-24702</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9897</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Emission Standards for Hazardous Air Pollutants for Nine Metal Fabrication and Finishing Area Sources,</SJDOC>
          <PGS>24703-24705</PGS>
          <FRDOCBP D="2" T="25APN1.sgm">2012-9898</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NESHAP for Steel Pickling, HCl Process Facilities and Hydrochloric Acid Regeneration Plants,</SJDOC>
          <PGS>24700-24701</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9900</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Part 70 State Operating Permit Program; and Part 71 Federal Operating Permit Program,</SJDOC>
          <PGS>24702-24703</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9896</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Certain New Chemicals; Receipt and Status Information,</DOC>
          <PGS>24705-24709</PGS>
          <FRDOCBP D="4" T="25APN1.sgm">2012-9919</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Executive Office of the President</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Presidential Documents</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Trade Representative, Office of United States</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Farm Credit System Insurance</EAR>
      <HD>Farm Credit System Insurance Corporation</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Farm Credit System Insurance Corporation Board,</SJDOC>
          <PGS>24709</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9911</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Aviation</EAR>
      <HD>Federal Aviation Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Airworthiness Directives:</SJ>
        <SJDENT>
          <SJDOC>Turbomeca S.A. Turboshaft Engines,</SJDOC>
          <PGS>24585-24587</PGS>
          <FRDOCBP D="2" T="25APR1.sgm">2012-9789</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Airworthiness Directives:</SJ>
        <SJDENT>
          <SJDOC>The Boeing Company Airplanes,</SJDOC>
          <PGS>24643-24646</PGS>
          <FRDOCBP D="3" T="25APP1.sgm">2012-9916</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Aviation Rulemaking Advisory Committee; Transport Airplane and Engine Issues,</SJDOC>
          <PGS>24759-24760</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9954</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Communications</EAR>
      <HD>Federal Communications Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Implementing the Provisions of the Communications Act as Enacted by the Twenty-First Century Communications and Video Accessibility Act of 2010,</DOC>
          <PGS>24632-24634</PGS>
          <FRDOCBP D="2" T="25APR1.sgm">2012-9912</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>24709-24711</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9836</FRDOCBP>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9891</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Deposit</EAR>
      <HD>Federal Deposit Insurance Corporation</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>24711-24712</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9976</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Energy</EAR>
      <HD>Federal Energy Regulatory Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Version 4 Critical Infrastructure Protection Reliability Standards,</DOC>
          <PGS>24594-24611</PGS>
          <FRDOCBP D="17" T="25APR1.sgm">2012-9893</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Open Access and Priority Rights on Interconnection Facilities,</DOC>
          <PGS>24646-24656</PGS>
          <FRDOCBP D="10" T="25APP1.sgm">2012-9848</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Combined Filings,</DOC>
          <PGS>24695-24696</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9957</FRDOCBP>
        </DOCENT>
        <SJ>Initial Market-Based Rate Filings Including Requests for Blanket Section 204 Authorizations:</SJ>
        <SJDENT>
          <SJDOC>Cayuga Operating Co., LLC,</SJDOC>
          <PGS>24696</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9959</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Cooper Mountain Solar 2, LLC,</SJDOC>
          <PGS>24697</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9960</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Somerset Operating Co., LLC,</SJDOC>
          <PGS>24697</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9958</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Verso Bucksport LLC,</SJDOC>
          <PGS>24696</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9956</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Highway</EAR>
      <HD>Federal Highway Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Buy America Waivers,</DOC>
          <PGS>24760</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9872</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Maritime</EAR>
      <HD>Federal Maritime Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agreements Filed,</DOC>
          <PGS>24712</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9986</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Ocean Transportation Intermediary Licenses; Applicants,</DOC>
          <PGS>24712-24713</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9989</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Ocean Transportation Intermediary Licenses; Reissuances,</DOC>
          <PGS>24713</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9988</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Ocean Transportation Intermediary Licenses; Revocations,</DOC>
          <PGS>24713</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9987</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Railroad</EAR>
      <HD>Federal Railroad Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Safety Advisories:</SJ>
        <SJDENT>
          <SJDOC>Restricted Speed,</SJDOC>
          <PGS>24760-24762</PGS>
          <FRDOCBP D="2" T="25APN1.sgm">2012-9948</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food and Drug</EAR>
      <HD>Food and Drug Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Revisions to Labeling Requirements for Blood and Blood Components, Including Source Plasma,</SJDOC>
          <PGS>24720-24721</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9894</FRDOCBP>
        </SJDENT>
        <SJ>Annual Food and Drug Administration-Orange County Regulatory Affairs Educational Conference:</SJ>
        <SJDENT>
          <SJDOC>Sustainable Regulatory Practices, Irvine, CA,</SJDOC>
          <PGS>24721-24722</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9968</FRDOCBP>
        </SJDENT>
        <SJ>Draft Guidances for Industry:</SJ>
        <SJDENT>
          <SJDOC>Assessing Effects of Significant Manufacturing Process Changes, etc.,</SJDOC>
          <PGS>24722-24723</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9936</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Safety of Nanomaterials in Cosmetic Products; Availability,</SJDOC>
          <PGS>24722</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9934</FRDOCBP>
        </SJDENT>
        <SJ>Withdrawals of Approvals of New Drug Applications:</SJ>
        <SJDENT>
          <SJDOC>IRESSA; AstraZeneca Pharmaceuticals LP,</SJDOC>
          <PGS>24723-24724</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9944</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>OFORTA; Sanofi-aventis, U.S., LLC,</SJDOC>
          <PGS>24724</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9943</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food Safety</EAR>
      <HD>Food Safety and Inspection Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Compliance Guides; Availability:</SJ>
        <SJDENT>
          <SJDOC>Residue Prevention and Agency Testing Policy for Residues,</SJDOC>
          <PGS>24671-24673</PGS>
          <FRDOCBP D="2" T="25APN1.sgm">2012-9797</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Forest</EAR>
      <HD>Forest Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Delegations of Authority:</SJ>
        <SJDENT>
          <SJDOC>Regional Forester, Pacific Southwest Region, to Forest Supervisor, Eldorado National Forest,</SJDOC>
          <PGS>24673</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9945</FRDOCBP>
        </SJDENT>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Grand Mesa, Uncompahgre and Gunnison National Forests; Colorado; Federal Coal Lease Modifications, etc.,</SJDOC>
          <PGS>24673-24677</PGS>
          <FRDOCBP D="4" T="25APN1.sgm">2012-9920</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>Federal Acquisition Regulation; Transportation Requirements,</SJDOC>
          <PGS>24713-24714</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9829</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Health and Human</EAR>
      <PRTPAGE P="v"/>
      <HD>Health and Human Services Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Agency for Healthcare Research and Quality</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Centers for Disease Control and Prevention</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>
      <CAT>
        <HD>RULES</HD>
        <SJ>World Trade Center Health Program Requirements:</SJ>
        <SJDENT>
          <SJDOC>Addition of New WTC-Related Health Conditions,</SJDOC>
          <PGS>24628-24632</PGS>
          <FRDOCBP D="4" T="25APR1.sgm">2012-9425</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>National Toxicology Program Board of Scientific Counselors,</SJDOC>
          <PGS>24714-24715</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9913</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>National Action Plan to Prevent Healthcare-Associated Infections, Roadmap to Elimination,</DOC>
          <PGS>24715-24716</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9868</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Healthcare Research and Quality Agency</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Agency for Healthcare Research and Quality</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>U.S. Customs and Border Protection</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>President's National Security Telecommunications Advisory Committee,</SJDOC>
          <PGS>24728-24729</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9979</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Industry</EAR>
      <HD>Industry and Security Bureau</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Addition of Certain Persons to the Entity List:</SJ>
        <SJDENT>
          <SJDOC>Implementation of Entity List Annual Review Changes,</SJDOC>
          <PGS>24587-24594</PGS>
          <FRDOCBP D="7" T="25APR1.sgm">2012-9905</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Interior</EAR>
      <HD>Interior Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Indian Gaming Commission</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Park Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Ocean Energy Management Bureau</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Reclamation Bureau</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Surface Mining Reclamation and Enforcement Office</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Internal Revenue</EAR>
      <HD>Internal Revenue Service</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Removal of Regulations Requiring 3% Withholding by Government Entities,</DOC>
          <PGS>24611-24612</PGS>
          <FRDOCBP D="1" T="25APR1.sgm">2012-9887</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Local Lodging Expenses,</DOC>
          <PGS>24657-24660</PGS>
          <FRDOCBP D="3" T="25APP1.sgm">2012-9885</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Withholding on Payments by Government Entities to Persons Providing Property or Services,</DOC>
          <PGS>24660-24661</PGS>
          <FRDOCBP D="1" T="25APP1.sgm">2012-9886</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Adm</EAR>
      <HD>International Trade Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Client Focus Groups and Qualitative Interviews,</SJDOC>
          <PGS>24685-24686</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9967</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Com</EAR>
      <HD>International Trade Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Investigations:</SJ>
        <SJDENT>
          <SJDOC>Certain Wireless Communication Devices and Systems, Components Thereof, and Products Containing Same,</SJDOC>
          <PGS>24738-24739</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9890</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Justice Department</EAR>
      <HD>Justice Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Applications for Special Deputations,</SJDOC>
          <PGS>24739</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9832</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Jurors Information Form,</SJDOC>
          <PGS>24739-24740</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9833</FRDOCBP>
        </SJDENT>
        <SJ>Lodgings of Settlement Agreements:</SJ>
        <SJDENT>
          <SJDOC>Resource Conservation and Recovery Act; Emergency Planning and Community Right-To-Know Act,</SJDOC>
          <PGS>24740</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9892</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Labor Department</EAR>
      <HD>Labor Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Senior Community Service Employment Program Performance Measurement System,</SJDOC>
          <PGS>24740-24741</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9830</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Library</EAR>
      <HD>Library of Congress</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Copyright Royalty Board</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>NASA</EAR>
      <HD>National Aeronautics and Space Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Federal Acquisition Regulation; Transportation Requirements,</SJDOC>
          <PGS>24713-24714</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9829</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Agricultural</EAR>
      <HD>National Agricultural Statistics Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>24677-24678</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9991</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Foundation</EAR>
      <HD>National Foundation on the Arts and the Humanities</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>24741-24742</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9883</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Highway</EAR>
      <HD>National Highway Traffic Safety Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Decisions of Inconsequential Noncompliance:</SJ>
        <SJDENT>
          <SJDOC>Mitsubishi Motors North America, Inc.; Grant of Petition,</SJDOC>
          <PGS>24762-24764</PGS>
          <FRDOCBP D="2" T="25APN1.sgm">2012-9946</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Visual-Manual Driver Distraction Guidelines for In-Vehicle Electronic Devices,</DOC>
          <PGS>24764-24766</PGS>
          <FRDOCBP D="2" T="25APN1.sgm">2012-9953</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Indian</EAR>
      <HD>National Indian Gaming Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>24730-24734</PGS>
          <FRDOCBP D="4" T="25APN1.sgm">2012-9922</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,</SJDOC>
          <PGS>24725-24726</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9908</FRDOCBP>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9914</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Fogarty International Center,</SJDOC>
          <PGS>24725</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9882</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Eye Institute,</SJDOC>
          <PGS>24727</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9878</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Heart, Lung, and Blood Institute,</SJDOC>
          <PGS>24728</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9875</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute of General Medical Sciences,</SJDOC>
          <PGS>24724-24725</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9880</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute of Neurological Disorders and Stroke,</SJDOC>
          <PGS>24725-24728</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9874</FRDOCBP>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9910</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute on Aging,</SJDOC>
          <PGS>24727-24728</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9877</FRDOCBP>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9881</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute on Alcohol Abuse and Alcoholism,</SJDOC>
          <PGS>24726-24727</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9906</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Oceanic</EAR>
      <HD>National Oceanic and Atmospheric Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Magnuson-Stevens Act Provisions; Fisheries off West Coast States:</SJ>
        <SJDENT>
          <SJDOC>Biennial Specifications and Management Measures; Inseason Adjustments,</SJDOC>
          <PGS>24634-24639</PGS>
          <FRDOCBP D="5" T="25APR1.sgm">2012-9963</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Atlantic Highly Migratory Species:</SJ>
        <SJDENT>
          <SJDOC>Recreational Yellowfin Tuna Fishery Data Collection; Public Conference Call,</SJDOC>
          <PGS>24669-24670</PGS>
          <FRDOCBP D="1" T="25APP1.sgm">2012-9971</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <PRTPAGE P="vi"/>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Western Pacific Fishery Management Council,</SJDOC>
          <PGS>24686</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9950</FRDOCBP>
        </SJDENT>
        <SJ>Permits:</SJ>
        <SJDENT>
          <SJDOC>Endangered Species; File No. 15634,</SJDOC>
          <PGS>24686-24687</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9962</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Park</EAR>
      <HD>National Park Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>White-tailed Deer Management Plan, Indiana Dunes National Lakeshore,</SJDOC>
          <PGS>24734</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9972</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Navy</EAR>
      <HD>Navy Department</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Certifications and Exemptions Under the International Regulations for Preventing Collisions at Sea, 1972,</DOC>
          <PGS>24612-24613</PGS>
          <FRDOCBP D="1" T="25APR1.sgm">2012-9928</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Secretary of Navy Advisory Panel,</SJDOC>
          <PGS>24688</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9930</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Nuclear Regulatory</EAR>
      <HD>Nuclear Regulatory Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>List of Approved Spent Fuel Storage Casks:</SJ>
        <SJDENT>
          <SJDOC>HI-STORM 100, Revision 8,</SJDOC>
          <PGS>24585</PGS>
          <FRDOCBP D="0" T="25APR1.sgm">2012-9834</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Confirmatory Orders:</SJ>
        <SJDENT>
          <SJDOC>ABSG Consulting Inc.,</SJDOC>
          <PGS>24742-24744</PGS>
          <FRDOCBP D="2" T="25APN1.sgm">2012-10002</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Advisory Committee on Reactor Safeguards,</SJDOC>
          <PGS>24744</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9992</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Advisory Committee on Reactor Safeguards Subcommittee on Reliability and PRA,</SJDOC>
          <PGS>24745</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9995</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Advisory Committee on Reactor Safeguards Subcommittee on Thermal Hydraulic Phenomena,</SJDOC>
          <PGS>24745</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-10008</FRDOCBP>
        </SJDENT>
        <SJ>Regulatory Guides:</SJ>
        <SJDENT>
          <SJDOC>Constraint on Releases of Airborne Radioactive Materials to Environment for Licensees other than Power Reactors,</SJDOC>
          <PGS>24746</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9998</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Ocean Energy Management</EAR>
      <HD>Ocean Energy Management Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Assessments; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Renewable Energy Program Leasing for Marine Hydrokinetic Technology Testing Offshore Florida,</SJDOC>
          <PGS>24734-24735</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9983</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Office of United States Trade Representative</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Trade Representative, Office of United States</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Presidential Documents</EAR>
      <HD>Presidential Documents</HD>
      <CAT>
        <HD>PROCLAMATIONS</HD>
        <DOCENT>
          <DOC>Fort Ord National Monument; Establishment (Proc. 8803),</DOC>
          <PGS>24579-24583</PGS>
          <FRDOCBP D="4" T="25APD2.sgm">2012-10114</FRDOCBP>
        </DOCENT>
        <SJ>Special Observances:</SJ>
        <SJDENT>
          <SJDOC>Earth Day (Proc. 8802),</SJDOC>
          <PGS>24577-24578</PGS>
          <FRDOCBP D="1" T="25APD1.sgm">2012-10107</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Park Week (Proc. 8801),</SJDOC>
          <PGS>24575-24576</PGS>
          <FRDOCBP D="1" T="25APD0.sgm">2012-10099</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Reclamation</EAR>
      <HD>Reclamation Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>24735-24737</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9917</FRDOCBP>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9921</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Rural Business</EAR>
      <HD>Rural Business-Cooperative Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>24678</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9975</FRDOCBP>
        </DOCENT>
        <SJ>Funding Availabilities:</SJ>
        <SJDENT>
          <SJDOC>Small, Socially-Disadvantaged Producer Grant Application Deadlines in Fiscal Year 2012,</SJDOC>
          <PGS>24678-24683</PGS>
          <FRDOCBP D="5" T="25APN1.sgm">2012-9997</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Securities</EAR>
      <HD>Securities and Exchange Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Rule 17a-11,</SJDOC>
          <PGS>24746-24747</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9938</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Rule 17a-6,</SJDOC>
          <PGS>24747-24748</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9937</FRDOCBP>
        </SJDENT>
        <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
        <SJDENT>
          <SJDOC>EDGA Exchange, Inc.; EDGX Exchange, Inc.; International Securities Exchange, LLC,</SJDOC>
          <PGS>24752-24756</PGS>
          <FRDOCBP D="4" T="25APN1.sgm">2012-9929</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Financial Industry Regulatory Authority, Inc.,</SJDOC>
          <PGS>24748-24750</PGS>
          <FRDOCBP D="2" T="25APN1.sgm">2012-9840</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NYSE Arca, Inc.,</SJDOC>
          <PGS>24750-24752</PGS>
          <FRDOCBP D="2" T="25APN1.sgm">2012-9969</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Small Business</EAR>
      <HD>Small Business Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Disaster Declarations:</SJ>
        <SJDENT>
          <SJDOC>Texas,</SJDOC>
          <PGS>24756</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9940</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Social</EAR>
      <HD>Social Security Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Privacy Act; Computer Matching Programs,</DOC>
          <PGS>24756-24758</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9951</FRDOCBP>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9952</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>State Department</EAR>
      <HD>State Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Charter Renewals:</SJ>
        <SJDENT>
          <SJDOC>Advisory Committee on International Communications and Information Policy,</SJDOC>
          <PGS>24758</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-10000</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Advisory Committee International Postal and Delivery Services,</SJDOC>
          <PGS>24758-24759</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9999</FRDOCBP>
        </SJDENT>
        <SJ>Waivers and Certifications of Statutory Provisions:</SJ>
        <SJDENT>
          <SJDOC>Palestine Liberation Organization Office,</SJDOC>
          <PGS>24759</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9932</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Statistical Reporting Service</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Agricultural Statistics Service</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Surface Mining</EAR>
      <HD>Surface Mining Reclamation and Enforcement Office</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>North Dakota Regulatory Program,</DOC>
          <PGS>24661-24662</PGS>
          <FRDOCBP D="1" T="25APP1.sgm">2012-9869</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>24737-24738</PGS>
          <FRDOCBP D="1" T="25APN1.sgm">2012-9843</FRDOCBP>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9845</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Trade Representative</EAR>
      <HD>Trade Representative, Office of United States</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Implementation of United States-Colombia Trade Promotion Agreement:</SJ>
        <SJDENT>
          <SJDOC>Tariff-Rate Quota for Imports of Sugar,</SJDOC>
          <PGS>24759</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9964</FRDOCBP>
        </SJDENT>
      </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 Highway Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Railroad Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Highway Traffic Safety Administration</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>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Extension of Port Limits of Indianapolis, IN,</DOC>
          <PGS>24656-24657</PGS>
          <FRDOCBP D="1" T="25APP1.sgm">2012-9996</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>U.S. Institute</EAR>
      <PRTPAGE P="vii"/>
      <HD>United States Institute of Peace</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Requests for Proposals:</SJ>
        <SJDENT>
          <SJDOC>Micro Support Program on International Conflict Resolution and Peacebuilding,</SJDOC>
          <PGS>24766</PGS>
          <FRDOCBP D="0" T="25APN1.sgm">2012-9822</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <PTS>
      <HD SOURCE="HED">Separate Parts In This Issue</HD>
      <HD>Part II</HD>
      <DOCENT>
        <DOC>Environmental Protection Agency,</DOC>
        <PGS>24768-24792</PGS>
        <FRDOCBP D="24" T="25APP2.sgm">2012-9808</FRDOCBP>
      </DOCENT>
      <HD>Part III</HD>
      <DOCENT>
        <DOC>Environmental Protection Agency,</DOC>
        <PGS>24794-24827</PGS>
        <FRDOCBP D="33" T="25APP3.sgm">2012-9839</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>80</NO>
  <DATE>Wednesday, April 25, 2012</DATE>
  <UNITNAME>Rules and Regulations</UNITNAME>
  <RULES>
    <RULE>
      <PREAMB>
        <PRTPAGE P="24585"/>
        <AGENCY TYPE="F">NUCLEAR REGULATORY COMMISSION</AGENCY>
        <CFR>10 CFR Part 72</CFR>
        <DEPDOC>[NRC-2011-0221]</DEPDOC>
        <RIN>RIN 3150-AJ05</RIN>
        <SUBJECT>List of Approved Spent Fuel Storage Casks: HI-STORM 100, Revision 8</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Nuclear Regulatory Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule; confirmation of effective date.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The U.S. Nuclear Regulatory Commission (NRC or the Commission) is confirming the effective date of May 2, 2012, for the direct final rule that was published in the<E T="04">Federal Register</E>on February 17, 2012. This direct final rule amends the NRC's spent fuel storage regulations by revising the Holtec International HI-STORM 100 System listing within the “List of Approved Spent Fuel Storage Casks” to include Amendment No. 8 to Certificate of Compliance (CoC) Number 1014.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>The effective date for the direct final rule published February 17, 2012, at 77 FR 9515, is confirmed as May 2, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Please refer to Docket ID NRC-2011-0221 when contacting the NRC about the availability of information regarding this document. You may access information related to this document, which the NRC possesses and is publicly-available, using the following methods:</P>
          <P>•<E T="03">Federal Rulemaking Web site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2011-0221. Address questions about NRC dockets to Carol Gallagher; telephone: 301-492-3668; email:<E T="03">Carol.Gallagher@nrc.gov</E>.</P>
          <P>•<E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>You may access publicly-available documents online in the NRC Library at<E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>To begin the search, select “ADAMS Public Documents” and then select “<E T="03">Begin Web-based ADAMS Search.”</E>For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, 301-415-4737, or by email to<E T="03">pdr.resource@nrc.gov</E>.</P>
          <P>•<E T="03">NRC's PDR:</E>You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Gregory Trussell, Office of Federal and State Materials and Environmental Management Programs, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, telephone: 301-415-6445, email:<E T="03">Gregory.Trussell@nrc.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>On February 17, 2012 (77 FR 9515), the NRC published a direct final rule amending its regulations at Title 10 of the<E T="03">Code of Federal Regulations</E>(10 CFR) 72.214, by revising the Holtec International HI-STORM 100 System listing within the “List of Approved Spent Fuel Storage Casks” to include Amendment No. 8 to CoC Number 1014. In the direct final rule, the NRC stated that if no significant adverse comments were received, the direct final rule would become effective on May 2, 2012. The NRC did not receive any comments on the direct final rule. Therefore, this rule will become effective as scheduled.</P>
        <SIG>
          <DATED>Dated at Rockville, Maryland, this 19th day of April 2012.</DATED>
          
          <P>For the Nuclear Regulatory Commission.</P>
          <NAME>Cindy Bladey,</NAME>
          <TITLE>Chief, Rules, Announcements, and Directives Branch, Division of Administrative Services, Office of Administration.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9834 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7590-01-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-2012-0010; Directorate Identifier 2012-NE-03-AD; Amendment 39-17035; AD 2012-08-18]</DEPDOC>
        <RIN>RIN 2120-AA64</RIN>
        <SUBJECT>Airworthiness Directives; Turbomeca S.A. Turboshaft Engines</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 adopting a new airworthiness directive (AD) for all Turbomeca S.A. Arriel 2B and 2B1 turboshaft engines. This AD was prompted by the discovery of non-conformities of certain power turbine (PT) blade fir-tree roots. This AD requires removing the affected PT blades from service on or before reaching a new reduced life limit for those certain PT blades. We are issuing this AD to prevent PT blade rupture, which could result in an uncommanded in-flight engine shutdown, forced autorotation landing, or accident.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This AD is effective May 30, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>For service information identified in this AD, contact Turbomeca, 40220 Tarnos, France; phone: 33 05 59 74 40 00; fax: 33 05 59 74 45 15. You may review copies of the referenced service information at the FAA, Engine &amp; Propeller Directorate, 12 New England Executive Park, Burlington, MA. For information on the availability of this material at the FAA, call 781-238-7125.</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<PRTPAGE P="24586"/>New Jersey Avenue SE., Washington, DC 20590.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Rose Len, Aerospace Engineer, Engine Certification Office, FAA, Engine &amp; Propeller Directorate, 12 New England Executive Park, Burlington, MA 01803; phone: 781-238-7772; fax: 781-238-7199; email:<E T="03">rose.len@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 include an AD that would apply to the specified products. That NPRM published in the<E T="04">Federal Register</E>on January 20, 2012 (77 FR 2930). That NPRM proposed to require removing the affected PT blades from service on or before reaching a new reduced life limit for those certain PT blades.</P>
        <HD SOURCE="HD1">Comments</HD>
        <P>We gave the public the opportunity to participate in developing this AD. We received no comments on the NPRM (77 FR 2930, January 20, 2012).</P>
        <HD SOURCE="HD1">Clarification of Compliance Time</HD>
        <P>Since we issued the proposed AD, we determined that we need to clarify the compliance time. The proposed AD stated 5,000 flight cycles. We changed the AD to state 5,000 flight cycles-since-new.</P>
        <HD SOURCE="HD1">Conclusion</HD>
        <P>We reviewed the relevant data and determined that air safety and the public interest require adopting the AD with the change described previously.</P>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>Based on the service information, we estimate that this AD will affect about 150 engines installed on helicopters of U.S. registry. We also estimate that it will take about 4 work-hours per product to comply with this AD. The average labor rate is $85 per work-hour. A prorated replacement M04 module will cost about $20,000 per engine. Based on these figures, we estimate the cost of the AD on U.S. operators to be $3,051,000.</P>
        <HD SOURCE="HD1">Authority for This Rulemaking</HD>
        <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
        <P>We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
        <HD SOURCE="HD1">Regulatory Findings</HD>
        <P>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>
          <E T="03">For the reasons discussed above, I certify that this AD:</E>
        </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>
        <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>
        <SECTION>
          <SECTNO>§ 39.13</SECTNO>
          <SUBJECT>[Amended]</SUBJECT>
        </SECTION>
        <REGTEXT PART="39" TITLE="14">
          <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive (AD):</AMDPAR>
          
          <EXTRACT>
            <FP SOURCE="FP-2">
              <E T="04">2012-08-18Turbomeca S.A:</E>Amendment 39-17035; Docket No. FAA-2012-0010; Directorate Identifier 2012-NE-03-AD.</FP>
            <HD SOURCE="HD1">(a) Effective Date</HD>
            <P>This AD is effective May 30, 2012.</P>
            <HD SOURCE="HD1">(b) Affected ADs</HD>
            <P>None.</P>
            <HD SOURCE="HD1">(c) Applicability</HD>
            <P>This AD applies to Turbomeca S.A. Arriel 2B and 2B1 turboshaft engines with at least one installed power turbine (PT) blade part number (P/N) 2 292 81 A01 0, serial numbers (S/Ns) 102782 through 120230 inclusive, or, S/Ns 120293 through 120390 inclusive.</P>
            <HD SOURCE="HD1">(d) Reason</HD>
            <P>This AD was prompted by the detection of geometric non-conformities on PT blade fir-tree roots. We are issuing this AD to prevent PT blade rupture, which could result in an uncommanded in-flight engine shutdown, forced autorotation landing, or accident.</P>
            <HD SOURCE="HD1">(e) Actions and Compliance</HD>
            <P>Unless already done, do the following actions within 5,000 flight cycles-since-new (CSN) on the PT blades, or within one month after the effective date of this AD, whichever occurs later.</P>
            <P>(1) Replace the PT blades with PT blades eligible for installation; or</P>
            <P>(2) Replace the M04 module with an M04 module having PT blades eligible for installation; or</P>
            <P>(3) Replace the PT wheel assembly with a PT wheel assembly having PT blades eligible for installation.</P>
            <P>(4) Guidance on the replacements specified in paragraphs (e)(1) through (e)(3) can be found in Turbomeca S.A. Alert Mandatory Service Bulletin No. A292 72 2842, Version A, dated September 23, 2011.</P>
            <HD SOURCE="HD1">(f) Definition</HD>
            <P>For the purposes of this AD, a PT blade eligible for installation is one not listed in paragraph (c) of this AD or, one listed in paragraph (c) of this AD with fewer than 5,000 flight CSN.</P>
            <HD SOURCE="HD1">(g) Installation Prohibition</HD>
            <P>From the effective date of this AD:</P>
            <P>(1) Do not install a PT blade as listed in paragraph (c) of this AD, that has 5,000 or more flight CSN, into any engine.</P>
            <P>(2) Do not install any engine with a PT blade as listed in paragraph (c) of this AD, that has 5,000 or more flight CSN, onto a helicopter.</P>
            <HD SOURCE="HD1">(h) Alternative Methods of Compliance (AMOCs)</HD>
            <P>The Manager, Engine Certification Office, may approve AMOCs for this AD. Use the procedures found in 14 CFR 39.19 to make your request.</P>
            <HD SOURCE="HD1">(i) Related Information</HD>

            <P>(1) For more information about this AD, contact Rose Len, Aerospace Engineer, Engine Certification Office, FAA, Engine &amp; Propeller Directorate, 12 New England Executive Park, Burlington, MA 01803; phone: 781-238-7772; fax: 781-238-7199; email:<E T="03">rose.len@faa.gov</E>.</P>
            <P>(2) Refer to MCAI EASA Airworthiness Directive 2011-0218, dated November 10, 2011, and Turbomeca S.A. Alert Mandatory Service Bulletin No. A292 72 2842, Version A, dated September 23, 2011, for related information.</P>

            <P>(3) For service information identified in this AD, contact Turbomeca, 40220 Tarnos, France; phone: 33 05 59 74 40 00; fax: 33 05<PRTPAGE P="24587"/>59 74 45 15. You may review copies of the referenced service information at the FAA, Engine &amp; Propeller Directorate, 12 New England Executive Park, Burlington, MA. For information on the availability of this material at the FAA, call 781-238-7125.</P>
            <HD SOURCE="HD1">(j) Material Incorporated by Reference</HD>
            <P>None.</P>
          </EXTRACT>
        </REGTEXT>
        <SIG>
          <DATED>Issued in Burlington, Massachusetts, on April 17, 2012.</DATED>
          <NAME>Peter A. White,</NAME>
          <TITLE>Manager, Engine &amp; Propeller Directorate, Aircraft Certification Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9789 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>Bureau of Industry and Security</SUBAGY>
        <CFR>15 CFR Part 744</CFR>
        <DEPDOC>[Docket No. 120416415-2415-01]</DEPDOC>
        <RIN>RIN 0694-AF57</RIN>
        <SUBJECT>Addition of Certain Persons to the Entity List; and Implementation of Entity List Annual Review Changes</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Bureau of Industry and Security, Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This rule amends the Export Administration Regulations (EAR) by adding to the Entity List two persons who have been determined by the U.S. Government to be acting contrary to the national security or foreign policy interests of the United States. These persons will be listed on the Entity List under the country of France.</P>

          <P>This rule also amends the Entity List on the basis of the annual review of the Entity List conducted by the End-User Review Committee (ERC). The ERC conducts the annual review to determine if any entries on the Entity List should be removed or modified. This rule reflects the results of the ERC's annual review of fifteen countries,<E T="03">i.e.</E>Armenia, Belarus, Egypt, Germany, Iran, Ireland, Israel, Kuwait, Lebanon, Norway, Russia, South Korea, Syria, the United Arab Emirates (U.A.E.), and the United Kingdom (U.K.). As a result of these reviews, this rule makes amendments to the Entity List including: The removal of three entries (one each in Germany, South Korea, and the United Arab Emirates (U.A.E.)); the addition of four entities (one each in Canada, Egypt, France and the United Kingdom); and the amendments of seventeen entries to provide alternate addresses, alternate spellings of names, and/or aliases for listed persons. The amended entries are in Armenia, Germany, Iran, Lebanon, Syria, and the U.A.E. sections of the Entity List.</P>
          <P>The Entity List provides notice to the public that certain exports, reexports, and transfers (in-country) to entities identified on the Entity List require a license from the Bureau of Industry and Security (BIS) and that availability of license exceptions in such transactions is limited.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This rule is effective April 25, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Karen Nies-Vogel, Chair, End-User Review Committee, Office of the Assistant Secretary, Export Administration, Bureau of Industry and Security, Department of Commerce, Phone: (202) 482-5991, Fax: (202) 482-3911, Email:<E T="03">ERC@bis.doc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>
        <P>The Entity List (Supplement No. 4 to Part 744) provides notice to the public that certain exports, reexports, and transfers (in-country) to entities identified on the Entity List require a license from the Bureau of Industry and Security and that the availability of license exceptions in such transactions is limited. Entities are placed on the Entity List on the basis of certain sections of part 744 (Control Policy: End-User and End-Use Based) of the EAR.</P>
        <P>The ERC, composed of representatives of the Departments of Commerce (Chair), State, Defense, Energy and, when appropriate, the Treasury, makes all decisions regarding additions to, removals from, or other modifications to the Entity List. The ERC makes all decisions to add an entry to the Entity List by majority vote and all decisions to remove or modify an entry by unanimous vote.</P>
        <HD SOURCE="HD1">ERC Entity List Decisions</HD>
        <HD SOURCE="HD2">Additions to the Entity List</HD>
        <P>This rule implements the decision of the ERC to add two persons, located in France, to the Entity List on the basis of Section 744.11 (license requirements that apply to entities acting contrary to the national security or foreign policy interests of the United States) of the EAR. The ERC reviewed Section 744.11(b) (Criteria for revising the Entity List) in making the determination to add the two persons located in France to the Entity List. Under that paragraph, persons for which there is reasonable cause to believe, based on specific and articulable facts, that the persons have been involved, are involved, or pose a significant risk of being or becoming involved in, activities that are contrary to the national security or foreign policy interests of the United States and those acting on behalf of such persons may be added to the Entity List pursuant to Section 744.11. Paragraphs (b)(1)-(b)(5) of Section 744.11 include an illustrative list of activities that could be contrary to the national security or foreign policy interests of the United States.</P>
        <P>The ERC has reasonable cause to believe that the two persons in France (one company and one individual, an employee of the company) have been involved, are involved, or pose a significant risk of being or becoming involved in, activities that could be contrary to the national security or foreign policy interests of the United States. Specifically, BIS's investigation of the company, Toulouse Air Spares SAS, indicates direct physical and corporate nexus with Aerotechnic France SAS, an Entity List person (76 FR 37632, 6/28/2011). Therefore, pursuant to Section 744.11(b)(5) of the EAR, the ERC determined that the company Toulouse Air Spares SAS and Laurence Mattiucci, the company's president, are engaging in conduct that poses a risk of violating the EAR and that such conduct raises sufficient concern that prior review of exports, reexports or transfers (in-country) of items subject to the EAR involving either of the two persons, and the possible imposition of license conditions or license denials, will enhance BIS's ability to prevent violations of the EAR.</P>
        <P>For both of the persons added to the Entity List, the ERC specified a license requirement for all items subject to the EAR and established a license application review policy of a presumption of denial. The license requirement applies to any transaction in which items are to be exported, reexported, or transferred (in-country) to such persons or in which such persons act as purchaser, intermediate consignee, ultimate consignee, or end-user. In addition, no license exceptions are available for exports, reexports, or transfers (in-country) to those persons being added to the Entity List.</P>
        <P>This final rule adds the following two persons to the Entity List:</P>
        <HD SOURCE="HD1">France</HD>
        <P>(1)<E T="03">Toulouse Air Spares SAS</E>, 8 Rue de la Bruyere, 31120 Pinsaguel, Toulouse, France;<E T="03">and</E>
        </P>
        <P>(2)<E T="03">Laurence Mattiucci</E>, 8 Rue de la Bruyere, 31120 Pinsaguel, Toulouse, France.</P>
        <HD SOURCE="HD2">Annual Review of the Entity List</HD>

        <P>This rule also amends the Entity List on the basis of the annual review of the<PRTPAGE P="24588"/>Entity List conducted by the ERC, in accordance with the procedures outlined in Supplement No. 5 to part 744 (Procedures for End-User Review Committee Entity List Decisions). The changes from the annual review of the Entity List that are approved by the ERC are implemented in stages as the ERC completes its review of entities listed under different destinations on the Entity List. This rule implements the results of the annual review for entities listed under Armenia, Germany, Iran, Lebanon, South Korea, Syria, and the U.A.E.</P>
        <HD SOURCE="HD3">A. Removals From the Entity List Based on the Annual Review</HD>
        <P>This rule removes two entities from the Entity List, consisting of one entity from Germany and one entity from South Korea, on the basis of the annual review of the Entity List. Specifically, this rule implements the decision of the ERC to remove the following two entities:</P>
        <HD SOURCE="HD1">Germany</HD>
        <P>(1)<E T="03">Akbar Ashraf Vaghefi,</E>Koburgerstr 10, D-10825, Berlin, Germany.</P>
        <HD SOURCE="HD1">South Korea</HD>
        <P>(1)<E T="03">WASTEC, Inc., a.k.a., With Advanced Systemic Technology,</E>Room 3303, 3304, Na-Dong Chungang Circulation Complex, #1258, Gurobon-Dong, Guro-gu, Seoul, South Korea.</P>
        <P>The removal of the above-referenced two entities from the Entity List eliminates the existing license requirements in Supplement No. 4 to part 744 for exports, reexports, and transfers (in-country) to the two entities. However, the removal of these two entities from the Entity List does not relieve persons of other obligations under part 744 of the EAR or under other parts of the EAR. Neither the removal of an entity from the Entity List nor the removal of Entity List-based license requirements relieves persons of their obligations under General Prohibition 5 in section 736.2(b)(5) of the EAR which provides that, “you may not, without a license, knowingly export or reexport any item subject to the EAR to an end-user or end-use that is prohibited by part 744 of the EAR.” Additionally these removals do not relieve persons of their obligation to apply for export, reexport or in-country transfer licenses required by other provisions of the EAR. BIS strongly urges the use of Supplement No. 3 to part 732 of the EAR, “BIS's `Know Your Customer' Guidance and Red Flags,” when persons are involved in transactions that are subject to the EAR.</P>

        <P>This rule, pursuant to the ERC's annual review, also removes a third entity from the Entity List, consisting of one entry from the U.A.E. However, this person's name will be added as an alias for another person listed on the Entity List, also under the U.A.E. Therefore, this removal does not remove license requirements for this person. Instead, the addition of the entry as an alias to another listed entity will more clearly identify the relationship between these two persons listed on the Entity List. Specifically, this rule consolidates the entry for “S. Basheer” (<E T="03">i.e.,</E>removes and adds to another entry on the Entity List) as a new alias for the revised “Shaji Muhammed Basheer” entry, as follows:</P>
        <HD SOURCE="HD1">United Arab Emirates</HD>
        <P>(1)<E T="03">Shaji Muhammed Basheer,</E>a.k.a., the following alias:</P>
        
        <FP SOURCE="FP-1">—S. Basheer.</FP>
        <FP SOURCE="FP-1">Shop No. 3 &amp; 4, Sharafia Ahmed Ali Bldg., Al Nakheel St., Deira, P.O. Box 171978, Dubai, U.A.E.</FP>
        <HD SOURCE="HD2">B. Modifications to the Entity List Based on the Annual Review</HD>
        <P>On the basis of decisions made by the ERC during the annual review, in addition to modifying the U.A.E. entry as described above, this rule amends sixteen entries currently on the Entity List, consisting of one entry under Armenia, three entries under Germany, ten entries under Iran, one entry under Lebanon, and one entry under Syria, to provide alternate addresses, alternate spellings for the names of the listed persons, and/or aliases, as follows:</P>
        <HD SOURCE="HD1">Armenia</HD>
        <P>(1)<E T="03">Bold Bridge International, LLC,</E>a.k.a., the following alias:</P>
        
        <FP SOURCE="FP-1">—BB Bold Bridge International.</FP>
        <FP SOURCE="FP-1">Room 463, H. Hakobyan 3, Yerevan, Armenia.</FP>
        <HD SOURCE="HD1">Germany</HD>
        <P>(1)<E T="03">Djamshid Nezhad,</E>a.k.a., the following alias:</P>
        
        <FP SOURCE="FP-1">—Nezhad Djamshid.</FP>
        <FP SOURCE="FP-1">Poppentrade 25, D-24148 Kiel, Germany; and Moesemann 2, 24144, Hamburg, Germany.</FP>
        <P>(2)<E T="03">IKCO Trading GmbH,</E>
        </P>
        
        <FP SOURCE="FP-1">Schadowplatz 5, 40212 Dusseldorf, Germany; and Kaiserswerther Str. 117, 40474, Düsseldorf, Germany; and</FP>
        <P>(3)<E T="03">Nezhad Enterprise Company,</E>a.k.a., the following three aliases:</P>
        
        <FP SOURCE="FP-1">—Nezhad Co.;</FP>
        <FP SOURCE="FP-1">—Nezhad Enterprise; and</FP>
        <FP SOURCE="FP-1">—Nezhad Trading.</FP>
        <FP SOURCE="FP-1">Poppentrade 25, D-24148 Kiel, Germany; and Moesemann 2, 24144, Hamburg, Germany.</FP>
        <HD SOURCE="HD1">Iran</HD>
        <P>(1)<E T="03">Atomic Energy Organization of Iran (AEOI),</E>a.k.a., the following two aliases:</P>
        
        <FP SOURCE="FP-1">—Sazeman-e Energy Atomi; and</FP>
        <FP SOURCE="FP-1">—Sazeman-e Enerji-e Atomi.</FP>
        <FP SOURCE="FP-1">P.O. Box 14144-1339, End of North Karegar Avenue, Tehran; and P.O. Box 14155-4494, Tehran, Iran; and all locations in Iran.</FP>
        
        <P>(2)<E T="03">Kalaye Electric Company,</E>a.k.a., the following four aliases:</P>
        
        <FP SOURCE="FP-1">—Kala Electric Company;</FP>
        <FP SOURCE="FP-1">—Kalia;</FP>
        <FP SOURCE="FP-1">—Kala Electric; and</FP>
        <FP SOURCE="FP-1">—Kola Electric Company.</FP>
        <FP SOURCE="FP-1">33 Fifteenth (15th) Street, Seyed-Jamal-Eddin-Assad Abadi Avenue, Tehran, Iran.</FP>
        
        <P>(3)<E T="03">Mahdi Electronics,</E>a.k.a., the following alias:</P>
        
        <FP SOURCE="FP-1">—Mahdi Electronic Trading Co. Ltd.</FP>
        <FP SOURCE="FP-1">Ground Floor—No. 31 Alborz Alley, Enghelab St, Tehran, Iran.</FP>
        
        <P>(4)<E T="03">NBC Navegan Bar Co. Ltd.,</E>a.k.a., the following alias:</P>
        
        <FP SOURCE="FP-1">—NBC Navegan Bar International Transport Co. Ltd.</FP>
        <FP SOURCE="FP-1">#135 Khorramshahr Ave., Tehran 1533864163; and 101, Kohrramshahr Ave., Tehran 1533864163.</FP>
        <P>(5)<E T="03">Rad Tavan Afza Company,</E>
        </P>
        
        <FP SOURCE="FP-1">3rd Floor, No. 210, W. Fatemi, Tehran, Iran, P.O. Box 14185-387; and 1st Pars Bldg., Beg. Pars Alley, Betw Khosh &amp; Behboudi St., Azadi Ave., Tehran, Iran.</FP>
        <P>(6)<E T="03">Raht Aseman Co. Ltd.,</E>
        </P>
        
        <FP SOURCE="FP-1">No. 1.2, Mosque Alley, Mohammadi St., North Bahar Ave., Tehran, Iran.</FP>
        <P>(7)<E T="03">Reza Zahedi Pour,</E>
        </P>
        
        <FP SOURCE="FP-1">5 Yaas St., Unit 4, Tehran, Iran.</FP>
        <P>(8)<E T="03">Shahid Bakeri Industrial Group,</E>a.k.a., the following nine aliases:</P>
        
        <FP SOURCE="FP-1">—SBIG;</FP>
        <FP SOURCE="FP-1">—Shahid Baheri Industries Group;</FP>
        <FP SOURCE="FP-1">—Shahid Bagheri Industries Group;</FP>
        <FP SOURCE="FP-1">—Shahid Bagheri Industrial Group;</FP>
        <FP SOURCE="FP-1">—MEHR Trading Company;</FP>
        <FP SOURCE="FP-1">—Department 140/14;</FP>
        <FP SOURCE="FP-1">—Mahtab Technical Engineering Company;</FP>
        <FP SOURCE="FP-1">—Composite Propellant Missile Industry; and</FP>
        <FP SOURCE="FP-1">—Sanaye Sokhte Morakab (SSM).</FP>
        <FP SOURCE="FP-1">Pasdaran Ave., Tehran, Iran.</FP>
        
        <P>(9)<E T="03">Shahid Hemmat Industrial Group,</E>a.k.a., the following six aliases:</P>
        
        <FP SOURCE="FP-1">—SHIG;</FP>
        <FP SOURCE="FP-1">—Shahid Hemat Industrial Group;</FP>
        <FP SOURCE="FP-1">—Chahid Hemmat Industrial Group;</FP>
        <FP SOURCE="FP-1">—Shahid Hemmat Industrial Complex (SHIC);</FP>
        <FP SOURCE="FP-1">—Shahid Hemmat Industrial Factories (SHIF); and</FP>
        <FP SOURCE="FP-1">—Hemmat Missile Industries Factory.<PRTPAGE P="24589"/>
        </FP>
        <FP SOURCE="FP-1">Damavand Tehran Highway, Tehran, Iran; and Damavand Road 2, Abali Road, Tehran, Iran; and</FP>
        <P>(10) Simin Neda Industrial and Electrical Parts, a.k.a., the following alias:</P>
        
        <FP SOURCE="FP-1">—TTSN.</FP>
        <FP SOURCE="FP-1">No. 22, Second Floor, Amjad Bldg., Jomhoori Ave., Tehran, Iran.</FP>
        <HD SOURCE="HD1">Lebanon</HD>
        <P>(1)<E T="03">EKT Electronics,</E>a.k.a. the following four aliases:</P>
        
        <FP SOURCE="FP-1">Katrangi Electronics;</FP>
        <FP SOURCE="FP-1">—Katrangi Trading;</FP>
        <FP SOURCE="FP-1">—Katranji Labs; and</FP>
        <FP SOURCE="FP-1">—Electronics Systems.</FP>
        <FP SOURCE="FP-1">1st floor, Hujij Building, Korniche Street, P.O. Box 817 No. 3, Beirut, Lebanon; P.O. Box: 8173, Beirut, Lebanon; and #1 fl., Grand Hills Bldg., Said Khansa St., Jnah (BHV), Beirut, Lebanon. (See alternate addresses under Syria.)</FP>
        <HD SOURCE="HD1">Syria</HD>
        <P>(1)<E T="03">EKT Electronics,</E>a.k.a., the following four aliases:</P>
        
        <FP SOURCE="FP-1">—Katrangi Electronics;</FP>
        <FP SOURCE="FP-1">—Katrangi Trading;</FP>
        <FP SOURCE="FP-1">—Katranji Labs; and</FP>
        <FP SOURCE="FP-1">—Electronics Systems.</FP>
        <FP SOURCE="FP-1">#1 floor, 11/A, Abbasieh Building, Hijaz Street, P.O. Box 10112, Damascus, Syria; and #1 floor, 02/A, Fares Building, Rami Street, Margeh, Damascus, Syria. (See alternate addresses under Lebanon.)</FP>
        <HD SOURCE="HD2">C. Additions to the Entity List on the Basis of the Annual Review and Section 744.11</HD>
        <P>Finally, on the basis of decisions made by the ERC during the annual review, this rule adds four persons to the Entity List, consisting of one person in Canada, one person in Egypt, one person in France, and one person in the U.K. The decision to add these four persons was made during the annual review and is based on Section 744.11 of the EAR. Similar to the process outlined above for the other Section 744.11 additions described in this rule, the ERC as part of the annual review process reviewed Section 744.11(b) in making the determination to add these four persons.</P>
        <P>These four persons are believed to have been involved in activities described under paragraphs (b)(1) and (b)(2) of Section 744.11. Specifically, the two persons located in Canada and Egypt are being added because of their affiliation with EKT Electronics, a person currently listed on the Entity List under Lebanon and Syria. BIS first included EKT Electronics as a listed person under General Order No. 3, which was first published on June 5, 2006, and subsequently amended on September 6, 2006. General Order No. 3 listed persons concerning whom the U.S. Government possessed information regarding the acquisition or attempted acquisition of electronic components and devices capable of being used in improvised explosive devices (IEDs) used against Coalition Forces in Iraq and Afghanistan. These two persons being added are not aliases of EKT Electronics, but are believed to be affiliated and involved in the same types of activities of concern under paragraphs (b)(1) and (b)(2) of Section 744.11 and therefore also warrant being added to the Entity List.</P>
        <P>Similarly, the two persons located in France and the U.K. are being added to the Entity List as a result of their affiliation with IKCO Trading GmbH (IKCO), a person currently on the Entity List under Germany. The French and the U.K. persons are involved in the same types of Section 744.11 activities that resulted in IKCO being added to the Entity List on September 22, 2008 (73 FR 54507). BIS first included IKCO as a listed person under General Order No. 3, which was first published on June 5, 2006, and subsequently amended on September 6, 2006. As noted above, General Order No. 3 listed persons concerning whom the U.S. Government possessed information regarding the acquisition or attempted acquisition of electronic components and devices capable of being used in IEDs used against Coalition Forces in Iraq and Afghanistan. These two persons being added are not aliases of IKCO, but are believed to be affiliated and involved in the same types of activities of concern under paragraphs (b)(1) and (b)(2) of Section 744.11 and therefore also warrant being added to the Entity List.</P>
        <P>For the four persons added to the Entity List on the basis of the annual review, the ERC specified a license requirement for all items subject to the EAR and established a license application review policy of a presumption of denial. The license requirement applies to any transaction in which items are to be exported, reexported, or transferred (in-country) to such persons or in which such persons act as purchaser, intermediate consignee, ultimate consignee, or end-user. In addition, no license exceptions are available for exports, reexports, or transfers (in-country) to those persons being added to the Entity List.</P>
        <P>This final rule adds the following four persons to the Entity List:</P>
        <HD SOURCE="HD1">Canada</HD>
        <P>(1)<E T="03">EKT 2, Inc.,</E>
        </P>
        
        <FP SOURCE="FP-1">371 Renforth Drive, Etobicoke M9C 2L8, Toronto, Ontario, Canada.</FP>
        <HD SOURCE="HD1">Egypt</HD>
        <P>(1)<E T="03">AL-AMIR ELECTRONICS,</E>
        </P>
        
        <FP SOURCE="FP-1">46 Falaki St. BabLouk Area, Cairo, Egypt.</FP>
        <HD SOURCE="HD1">France</HD>
        <P>(1)<E T="03">IKCO France,</E>
        </P>
        
        <FP SOURCE="FP-1">147 Avenue Charles de Gaulle, 92200, Neuilly-Sur-Seine, France.</FP>
        <HD SOURCE="HD1">United Kingdom</HD>
        <P>(1)<E T="03">IKCO Finance,</E>
        </P>
        
        <FP SOURCE="FP-1">6 Lothbury, London, England, EC2R 7HH.</FP>
        <HD SOURCE="HD2">Savings Clause</HD>
        <P>Shipments of items removed from eligibility for a License Exception or export or reexport without a license (NLR) as a result of this regulatory action that were en route aboard a carrier to a port of export or reexport, on April 25, 2012, pursuant to actual orders for export or reexport to a foreign destination, may proceed to that destination under the previous eligibility for a License Exception or export or reexport without a license (NLR).</P>
        <P>Although the Export Administration Act expired on August 20, 2001, the President, through Executive Order 13222 of August 17, 2001, 3 CFR, 2001 Comp., p. 783 (2002), as extended by the Notice of August 12, 2011, 76 FR 50661 (August 16, 2011), has continued the Export Administration Regulations in effect under the International Emergency Economic Powers Act. BIS continues to carry out the provisions of the Export Administration Act, as appropriate and to the extent permitted by law, pursuant to Executive Order 13222.</P>
        <HD SOURCE="HD1">Rulemaking Requirements</HD>

        <P>1. 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 determined to be not significant for purposes of Executive Order 12866.<PRTPAGE P="24590"/>
        </P>

        <P>2. Notwithstanding any other provision of law, no person is required to respond to nor be subject to a penalty for failure to comply with a collection of information, subject to the requirements of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501<E T="03">et seq.</E>) (PRA), unless that collection of information displays a currently valid Office of Management and Budget (OMB) Control Number. This regulation involves collections previously approved by the OMB under control numbers 0694-0088, “Multi-Purpose Application,” which carries a burden hour estimate of 43.8 minutes for a manual or electronic submission. Total burden hours associated with the PRA and OMB control number 0694-0088 are not expected to increase as a result of this rule. You may send comments regarding the collection of information associated with this rule, including suggestions for reducing the burden, to Jasmeet K. Seehra, Office of Management and Budget (OMB), by email to<E T="03">Jasmeet_K._Seehra@omb.eop.gov</E>, or by fax to (202) 395-7285.</P>
        <P>3. This rule does not contain policies with Federalism implications as that term is defined in Executive Order 13132.</P>

        <P>4. The provisions of the Administrative Procedure Act (5 U.S.C. 553) requiring notice of proposed rulemaking, the opportunity for public comment and a delay in effective date are inapplicable because this regulation involves a military or foreign affairs function of the United States. (<E T="03">See</E>5 U.S.C. 553(a)(1)). BIS implements this rule to protect U.S. national security or foreign policy interests by preventing items from being exported, reexported, or transferred (in country) to the persons being added to the Entity List. If this rule were delayed to allow for notice and comment and a delay in effective date, then entities being added to the Entity List by this action would continue to be able to receive items without a license and to conduct activities contrary to the national security or foreign policy interests of the United States. In addition, because these parties may receive notice of the U.S. Government's intention to place these entities on the Entity List once a final rule was published, it would create an incentive for these persons to either accelerate receiving items subject to the EAR to conduct activities that are contrary to the national security or foreign policy interests of the United States, and/or to take steps to set up additional aliases, change addresses, and other measures to try to limit the impact of the listing on the Entity List once a final rule was published. Further, no other law requires that a notice of proposed rulemaking and an opportunity for public comment be given for this rule. Because a notice of proposed rulemaking and an opportunity for public comment are not required to be given for this rule by 5 U.S.C. 553, or by any other law, the analytical requirements of the Regulatory Flexibility Act, 5 U.S.C. 601<E T="03">et seq.,</E>are not applicable.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 15 CFR Part 744</HD>
          <P>Exports, Reporting and recordkeeping requirements, Terrorism.</P>
        </LSTSUB>
        
        <P>Accordingly, part 744 of the Export Administration Regulations (15 CFR parts 730-774) is amended as follows:</P>
        <REGTEXT PART="744" TITLE="15">
          <PART>
            <HD SOURCE="HED">PART 744—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for 15 CFR part 744 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>50 U.S.C. app. 2401<E T="03">et seq.;</E>50 U.S.C. 1701<E T="03">et seq.</E>; 22 U.S.C. 3201<E T="03">et seq.;</E>42 U.S.C. 2139a; 22 U.S.C. 7201<E T="03">et seq.;</E>22 U.S.C. 7210; E.O. 12058, 43 FR 20947, 3 CFR, 1978 Comp., p. 179; E.O. 12851, 58 FR 33181, 3 CFR, 1993 Comp., p. 608; E.O. 12938, 59 FR 59099, 3 CFR, 1994 Comp., p. 950; E.O. 12947, 60 FR 5079, 3 CFR, 1995 Comp., p. 356; E.O. 13026, 61 FR 58767, 3 CFR, 1996 Comp., p. 228; E.O. 13099, 63 FR 45167, 3 CFR, 1998 Comp., p. 208; E.O. 13222, 66 FR 44025, 3 CFR, 2001 Comp., p. 783; E.O. 13224, 66 FR 49079, 3 CFR, 2001 Comp., p. 786; Notice of August 12, 2011, 76 FR 50661 (August 16, 2011); Notice of September 21, 2011, 76 FR 59001 (September, 22, 2011); Notice of November 9, 2011, 76 FR 70319 (November 10, 2011); Notice of January 19, 2012, 77 FR 3067 (January 20, 2012).</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="744" TITLE="15">
          <AMDPAR>2. Supplement No. 4 to part 744 is amended:</AMDPAR>
          <AMDPAR>(a) By revising under Armenia, in alphabetical order, one Armenian entity;</AMDPAR>
          <AMDPAR>(b) By adding under Canada, in alphabetical order, one Canadian entity;</AMDPAR>
          <AMDPAR>(c) By adding under Egypt, in alphabetical order, one Egyptian entity;</AMDPAR>
          <AMDPAR>(d) By adding under France, in alphabetical order, three French entities;</AMDPAR>
          <AMDPAR>(e) By removing under Germany, the German entity: “Akbar Ashraf Vaghefi, Koburgerstr 10, D-10825, Berlin, Germany;”</AMDPAR>
          <AMDPAR>(f) By revising under Germany, in alphabetical order, three German entities;</AMDPAR>
          <AMDPAR>(g) By revising under Iran, in alphabetical order, ten Iranian entities;</AMDPAR>
          <AMDPAR>(h) By revising under Lebanon, in alphabetical order, one Lebanese entity;</AMDPAR>
          <AMDPAR>(i) By removing the “Country” column for South Korea, including the South Korean entity: “WASTEC, Inc., a.k.a., With Advanced Systemic Technology, Room 3303, 3304, Na-Dong Chungang Circulation Complex, #1258, Gurobon-Dong, Guro-gu, Seoul, South Korea;”</AMDPAR>
          <AMDPAR>(j) By revising under Syria, in alphabetical order, one Syrian entity;</AMDPAR>
          <AMDPAR>(k) By removing under the United Arab Emirates, the Emirati entry for “S. Basheer, No. 3-4 Sharafia Ahmed Ali Building, Al Nakheel, Deira, Dubai 396, U.A.E.;”</AMDPAR>
          <AMDPAR>(l) By revising under the United Arab Emirates, in alphabetical order, one Emirati entity; and</AMDPAR>
          <AMDPAR>(m) By adding under United Kingdom, in alphabetical order, one British entity.</AMDPAR>
          <P>The additions and revisions read as follows:</P>
          <GPOTABLE CDEF="s50,r100,r50,r50,xls78" COLS="5" OPTS="L1,i1">
            <TTITLE>Supplement No. 4 to Part 744—Entity List</TTITLE>
            <BOXHD>
              <CHED H="1">Country</CHED>
              <CHED H="1">Entity</CHED>
              <CHED H="1">License requirement</CHED>
              <CHED H="1">License review policy</CHED>
              <CHED H="1">
                <E T="02">Federal Register</E>
                <LI>citation</LI>
              </CHED>
            </BOXHD>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">ARMENIA</ENT>
              <ENT O="xl">Bold Bridge International, LLC, a.k.a. the following alias:<LI O="xl">—BB Bold Bridge International.</LI>
                <LI O="xl">Room 463, H. Hakobyan 3, Yerevan, Armenia.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR.)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>75 FR 1701, 1/13/10.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22">CANADA</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="24591"/>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>EKT 2, Inc., 371 Renforth Drive, Etobicoke M9C 2L8, Toronto, Ontario, Canada</ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="01">EGYPT</ENT>
              <ENT>AL-AMIR ELECTRONICS, 46 Falaki St. BabLouk Area, Cairo, Egypt</ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22">FRANCE</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>IKCO France, 147 Avenue Charles de Gaulle, 92200, Neuilly-Sur-Seine, France</ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Laurence Mattiucci, 8 Rue de la Bruyere, 31120 Pinsaguel, Toulouse, France</ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Toulouse Air Spares SAS, 8 Rue de la Bruyere, 31120 Pinsaguel, Toulouse, France</ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">GERMANY</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">Djamshid Nezhad, a.k.a. the following alias:<LI O="xl">—Nezhad Djamshid.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>73 FR 54504,<LI>9/22/08.</LI>
                <LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Poppentrade 25, D-24148 Kiel, Germany; and Moesemann 2, 24144, Hamburg, Germany</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>IKCO Trading GmbH, Schadowplatz 5, 40212 Dusseldorf, Germany; and Kaiserswerther Str. 117, 40474, Düsseldorf, Germany</ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>73 FR 54504, 9/22/08.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">Nezhad Enterprise Company, a.k.a. the following three aliases:<LI O="xl">—Nezhad Co.;</LI>
                <LI O="xl">—Nezhad Enterprise; and</LI>
                <LI O="xl">—Nezhad Trading</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>73 FR 54504, 9/22/08.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Poppentrade 25, D-24148 Kiel, Germany; and Moesemann 2, 24144, Hamburg, Germany</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22">IRAN</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <PRTPAGE P="24592"/>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">Atomic Energy Organization of Iran (AEOI), a.k.a. the following two aliases:<LI O="xl">—Sazeman-e Energy Atomi; and</LI>
                <LI O="xl">—Sazeman-e Enerji-e Atomi.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>72 FR 38008, 07/12/07.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>P.O. Box 14144-1339, End of North Karegar Avenue, Tehran; and P.O. Box 14155-4494, Tehran, Iran; and all locations in Iran</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">Kalaye Electric Company, a.k.a. the following four aliases:<LI O="xl">—Kala Electric Company;</LI>
                <LI O="xl">—Kalia;</LI>
                <LI O="xl">—Kala Electric; and</LI>
                <LI O="xl">—Kola Electric Company.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>72 FR 38008, 07/12/07.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>33 Fifteenth (15th) Street, Seyed-Jamal-Eddin-Assad Abadi Avenue, Tehran, Iran</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">Mahdi Electronics, a.k.a. the following alias:<LI O="xl">—Mahdi Electronic Trading Co. Ltd.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>73 FR 74001, 12/5/08.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Ground Floor—No. 31 Alborz Alley, Enghelab St., Tehran, Iran</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">NBC Navegan Bar Co. Ltd., a.k.a. the following alias:<LI O="xl">—NBC Navegan Bar International Transport Co. Ltd.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>73 FR 54507, 9/22/08.<LI>76 FR 21628, 4/18/11.</LI>
                <LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>#135 Khorramshahr Ave., Tehran 1533864163; and 101, Kohrramshahr Ave., Tehran 1533864163</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Rad Tavan Afza Company, 3rd Floor, No. 210, W. Fatemi, Tehran, Iran, P.O. Box 14185-387; and 1st Pars Bldg., Beg. Pars Alley, Betw Khosh &amp; Behboudi St., Azadi Ave., Tehran, Iran</ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>73 FR 54507, 9/22/08.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Raht Aseman Co. Ltd., No. 1.2, Mosque Alley, Mohammadi St., North Bahar Ave., Tehran, Iran</ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>73 FR 74001, 12/5/08.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Reza Zahedi Pour, 5 Yaas St., Unit 4, Tehran, Iran</ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>73 FR 74001, 12/5/08.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <PRTPAGE P="24593"/>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">Shahid Bakeri Industrial Group, a.k.a. the following nine aliases:<LI O="xl">—SBIG;</LI>
                <LI O="xl">—Shahid Baheri Industries Group;</LI>
                <LI O="xl">—Shahid Bagheri Industries Group;</LI>
                <LI O="xl">—Shahid Bagheri Industrial Group;</LI>
                <LI O="xl">—MEHR Trading Company;</LI>
                <LI O="xl">—Department 140/14;</LI>
                <LI O="xl">—Mahtab Technical Engineering Company;</LI>
                <LI O="xl">—Composite Propellant Missile Industry; and</LI>
                <LI O="xl">—Sanaye Sokhte Morakab (SSM).</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>72 FR 38008, 07/12/07.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">Pasdaran Ave., Tehran, Iran.</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">Shahid Hemmat Industrial Group, a.k.a. the following six aliases:<LI O="xl">—SHIG;</LI>
                <LI O="xl">—Shahid Hemat Industrial Group;</LI>
                <LI O="xl">—Chahid Hemmat Industrial Group;</LI>
                <LI O="xl">—Shahid Hemmat Industrial Complex (SHIC);</LI>
                <LI O="xl">—Shahid Hemmat Industrial Factories (SHIF); and</LI>
                <LI O="xl">—Hemmat Missile Industries Factory.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>72 FR 38008, 07/12/07.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">Damavand Tehran Highway, Tehran, Iran; Damavand Tehran Highway, Tehran, Iran; and Damavand Road 2, Abali Road, Tehran, Iran.</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">Simin Neda Industrial and Electrical Parts, a.k.a. the following alias:<LI O="xl">—TTSN.</LI>
                <LI O="xl">No. 22, Second Floor, Amjad Bldg., Jomhoori Ave., Tehran, Iran.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>72 FR 38008, 07/12/07.<LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="01">LEBANON</ENT>
              <ENT O="xl">EKT Electronics, a.k.a. the following four aliases:<LI O="xl">—Katrangi Electronics;</LI>
                <LI O="xl">—Katrangi Trading;</LI>
                <LI O="xl">—Katranji Labs; and</LI>
                <LI O="xl">—Electronics Systems.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>73 FR 54507,<LI>9/22/08.</LI>
                <LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>1st floor, Hujij Building, Korniche Street, P.O. Box 817 No. 3, Beirut, Lebanon; P.O. Box: 8173, Beirut, Lebanon; and #1 fl., Grand Hills Bldg., Said Khansa St., Jnah (BHV), Beirut, Lebanon. (See alternate addresses under Syria.)</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22">SYRIA</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl">EKT Electronics, a.k.a. the following four aliases:<LI O="xl">—Katrangi Electronics;</LI>
                <LI O="xl">—Katrangi Trading;</LI>
                <LI O="xl">—Katranji Labs; and</LI>
                <LI O="xl">—Electronics Systems.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>73 FR 54509,<LI>9/22/08.</LI>
                <LI>76 FR 50407, 8/15/11.</LI>
                <LI>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</LI>
              </ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="24594"/>
              <ENT I="22"/>
              <ENT>#1 floor, 11/A, Abbasieh Building, Hijaz Street, P.O. Box 10112, Damascus, Syria; and #1 floor, 02/A, Fares Building, Rami Street, Margeh, Damascus, Syria (See alternate addresses under Lebanon)</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="01">UNITED ARAB EMIRATES</ENT>
              <ENT O="xl">Shaji Muhammed Basheer, a.k.a. the following alias:<LI O="xl">—S. Basheer.</LI>
              </ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR.)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Shop No. 3 &amp; 4, Sharafia Ahmed Ali Bldg., Al Nakheel St., Deira, P.O. Box 171978, Dubai, U.A.E</ENT>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22">UNITED KINGDOM</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>IKCO Finance 6 Lothbury, London, England, EC2R 7HH</ENT>
              <ENT>For all items subject to the EAR. (See § 744.11 of the EAR)</ENT>
              <ENT>Presumption of denial</ENT>
              <ENT>77 FR [INSERT FR PAGE NUMBER] 4/25/2012.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW RUL="s">
              <ENT I="28">*******</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="28">*******</ENT>
            </ROW>
          </GPOTABLE>
        </REGTEXT>
        <SIG>
          <DATED>Dated: April 18, 2012.</DATED>
          <NAME>Kevin J. Wolf,</NAME>
          <TITLE>Assistant Secretary for Export Administration.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9905 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-33-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <CFR>18 CFR Part 40</CFR>
        <DEPDOC>[Docket No. RM11-11-000; Order No. 761]</DEPDOC>
        <SUBJECT>Version 4 Critical Infrastructure Protection 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 (Commission) approves eight modified Critical Infrastructure Protection (CIP) Reliability Standards, CIP-002-4 through CIP-009-4, developed and submitted to the Commission for approval by the North American Electric Reliability Corporation (NERC), the Electric Reliability Organization certified by the Commission. The CIP Reliability Standards provide a cybersecurity framework for the identification and protection of “Critical Cyber Assets” to support the reliable operation of the Bulk-Power System. Reliability Standard CIP-002-4 requires the identification and documentation of Critical Cyber Assets associated with “Critical Assets” that support the reliable operation of the Bulk-Power System and introduces “bright line” criteria for the identification of Critical Assets. The Commission approves the related Violation Risk Factors, Violation Severity Levels with modifications, implementation plan, and effective date proposed by NERC.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule will become effective June 25, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P/>
          

          <FP SOURCE="FP-1">Jan Bargen (Technical Information), Office of Electric Reliability, Division of Logistics and Security, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-6333,<E T="03">Jan.Bargen@ferc.gov.</E>
          </FP>

          <FP SOURCE="FP-1">Edward Franks (Technical Information), Office of Electric Reliability, Division of Logistics and Security, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-6311,<E T="03">Edward.Franks@ferc.gov.</E>
          </FP>

          <FP SOURCE="FP-1">Kevin Ryan (Legal Information), Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-6840,<E T="03">Kevin.Ryan@ferc.gov.</E>
          </FP>

          <FP SOURCE="FP-1">Matthew Vlissides (Legal Information), Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-8408,<E T="03">Matthew.Vlissides@ferc.gov.</E>
          </FP>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD3">139 FERC ¶ 61,058</HD>
        <EXTRACT>
          <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>
        
        <PRTPAGE P="24595"/>
        <DATE>Issued April 19, 2012.</DATE>
        <P>1. Under section 215 of the Federal Power Act (FPA),<SU>1</SU>
          <FTREF/>the Commission approves modified Critical Infrastructure Protection (CIP) Reliability Standards, CIP-002-4 through CIP-009-4. The “Version 4” CIP Reliability Standards were developed and submitted for approval to the Commission by the North American Electric Reliability Corporation (NERC), which the Commission certified as the Electric Reliability Organization (ERO) responsible for developing and enforcing mandatory Reliability Standards. The CIP Reliability Standards provide a cybersecurity framework for the identification and protection of “Critical Cyber Assets” that are associated with “Critical Assets” to support the reliable operation of the Bulk-Power System.</P>
        <FTNT>
          <P>
            <SU>1</SU>16 U.S.C. 824o (2006).</P>
        </FTNT>
        <P>2. The Version 4 CIP Reliability Standards include “bright line” criteria for the identification of Critical Assets, which replace the risk-based assessment methodology developed and applied by applicable entities under the Version 3 CIP Reliability Standards. Version 4 includes other conforming modifications to the remaining CIP Reliability Standards, CIP-003-4 through CIP-009-4.</P>
        <P>3. The Commission approves NERC's filing, as amended by its errata filing, with regard to the related Violation Risk Factors (VRFs), the Violation Severity Levels (VSLs) with modifications, the implementation plan, and effective date proposed by NERC. The Commission also approves the concurrent retirement of the currently effective Version 3 CIP Reliability Standards, CIP-002-3 to CIP-009-3.</P>
        <P>4. In addition, the Commission determines that it is appropriate to impose a deadline by which time the ERO will submit for approval CIP Reliability Standards that are fully compliant with Order No. 706.<SU>2</SU>
          <FTREF/>NERC indicated that it anticipates filing the “Version 5” CIP Reliability Standards by the third quarter of 2012.<SU>3</SU>
          <FTREF/>Accordingly, we establish a deadline of 6 months from the end of the third quarter of 2012 (i.e., March 31, 2013). NERC must also submit reports at the beginning of each quarter in which the ERO is to explain whether it is on track to meet the deadline and describe the status of its CIP standard development efforts.</P>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">Mandatory Reliability Standards for Critical Infrastructure Protection,</E>Order No. 706, 122 FERC ¶ 61,040,<E T="03">denying reh'g and granting clarification,</E>Order No. 706-A, 123 FERC ¶ 61,174 (2008),<E T="03">order on clarification,</E>Order No. 706-B, 126 FERC ¶ 61,229 (2009),<E T="03">order denying clarification,</E>Order No. 706-C, 127 FERC ¶ 61,273 (2009).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>NERC Reply Comments at 4.</P>
        </FTNT>
        <HD SOURCE="HD1">I. Background</HD>
        <HD SOURCE="HD2">A. Mandatory Reliability Standards</HD>
        <P>5. 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. Once approved, the Reliability Standards may be enforced by the ERO, subject to Commission oversight, or by the Commission independently.<SU>4</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>4</SU>16 U.S.C. 824o(e).</P>
        </FTNT>
        <P>6. Pursuant to section 215 of the FPA, the Commission established a process to select and certify an ERO,<SU>5</SU>
          <FTREF/>and subsequently certified NERC as the ERO.<SU>6</SU>
          <FTREF/>On January 18, 2008, the Commission issued Order No. 706 approving eight CIP Reliability Standards proposed by NERC. Pursuant to section 215(d)(5) of the FPA,<SU>7</SU>
          <FTREF/>the Commission directed NERC to develop modifications to the CIP Reliability Standards to address concerns discussed in Order No. 706. Subsequently, the Commission approved Version 2 and Version 3 of the CIP Reliability Standards, each version including changes responsive to some but not all of the directives in Order No. 706.<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,<E T="03">order on reh'g,</E>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.,</E>116 FERC ¶ 61,062,<E T="03">order on reh'g and compliance,</E>117 FERC ¶ 61,126 (2006),<E T="03">aff'd sub nom. Alcoa, Inc.</E>v.<E T="03">FERC,</E>564 F.3d 1342 (D.C. Cir. 2009).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>7</SU>16 U.S.C. 824o(d)(5).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>8</SU>
            <E T="03">North American Electric Reliability Corp.,</E>128 FERC ¶ 61,291 (2009),<E T="03">order denying reh'g and granting clarification,</E>129 FERC ¶ 61,236 (2009) (approving Version 2 of the CIP Reliability Standards);<E T="03">North American Electric Reliability Corp.,</E>130 FERC ¶ 61,271 (2010) (approving Version 3 of the CIP Reliability Standards).</P>
        </FTNT>
        <HD SOURCE="HD2">B. NERC Petition</HD>
        <P>7. On February 10, 2011, NERC filed a petition seeking Commission approval of the Version 4 CIP Reliability Standards, CIP-002-4 to CIP-009-4, and the concurrent retirement of the Version 3 CIP Reliability Standards, CIP-002-3 to CIP-009-3.<SU>9</SU>
          <FTREF/>In the petition, NERC states that the principal differences between Version 3 and Version 4 are found in CIP-002, where NERC replaced the risk-based assessment methodology for identifying Critical Assets with 17 uniform “bright line” criteria for identifying Critical Assets. Concerning the process of identifying the associated Critical Cyber Assets that are subject to the cyber security protections required by CIP-003 through CIP-009, NERC only made changes for certain generation Critical Assets. NERC submitted proposed VRFs and VSLs and an implementation plan governing the transition to Version 4. NERC proposed that the Version 4 CIP Reliability Standards become effective the first day of the eighth calendar quarter after applicable regulatory approvals have been received.</P>
        <FTNT>
          <P>

            <SU>9</SU>NERC Petition at 1. The proposed Reliability Standards are not attached to the final rule. They are, however, available on the Commission's eLibrary document retrieval system in Docket No. RM11-11-000 and are available on the ERO's Web site,<E T="03">www.nerc.com.</E>Reliability Standards approved by the Commission are not codified in the Code of Federal Regulations.</P>
        </FTNT>
        <P>8. On April 12, 2011, NERC made an errata filing correcting certain errors in the petition and furnishing corrected exhibits and the standard drafting team minutes. In the errata, NERC also replaced the VRFs and VSLs in the February 10, 2011 petition with new proposed VRFs and VSLs.<SU>10</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>10</SU>NERC states that the Version 4 VRFs and VSLs are carried over in part from the VRFs and VSLs in the Version 3 CIP Reliability Standards. NERC Petition at 46. The Commission approved the Version 2 and 3 VRFs and VSLs in Docket Nos. RD10-6-001 and RD09-7-003 on January 20, 2011 but required NERC to make modifications in a compliance filing due by March 21, 2011.<E T="03">North American Electric Reliability Corporation,</E>134 FERC ¶ 61,045 (2011). The February 10, 2011 petition did not carry over the modified Version 3 VRFs and VSLs since it was filed before the March 21, 2011 compliance filing. NERC submitted new Version 4 VRFs and VSLs that carried over the modified Version 3 VRFs and VSLs in the April 12, 2012 errata. On June 6, 2011, NERC filed the March 21, 2011 compliance filing in the present docket, Docket No. RM11-11-000.</P>
        </FTNT>
        <P>9. Reliability Standard CIP-002-4 requires each responsible entity to use the bright line criteria as a “checklist” to identify Critical Assets, initially and in an annual review, replacing the risk-based assessment methodology developed and applied by each registered entity required under the currently-effective Version 3 CIP Reliability Standards. As in past versions, each responsible entity will then identify the Critical Cyber Assets associated with its updated list of Critical Assets. If application of the bright line criteria results in the identification of Critical Cyber Assets, such assets become subject to the remaining CIP Reliability Standards.</P>

        <P>10. In the petition, NERC states that CIP-002-4 addresses some, but not all, of the directives in Order No. 706. NERC explained that the standard drafting team limited the scope of requirements in the development of Version 4 “as an interim step” limited to the concerns raised by the Commission regarding<PRTPAGE P="24596"/>CIP-002.<SU>11</SU>
          <FTREF/>NERC maintains that it has taken a “phased” approach to meeting the Commission's directives from Order No. 706 and, according to NERC, the standard drafting team continues to address the remaining Commission directives. According to NERC, the team will build on the CIP-002-4 standard's establishment of uniform criteria for the identification of Critical Assets.<SU>12</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>11</SU>NERC Petition at 6 (<E T="03">citing</E>Order No. 706, 122 FERC ¶ 61,040 at P 236).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>12</SU>NERC Petition at 6.</P>
        </FTNT>
        <HD SOURCE="HD2">C. Notice of Proposed Rulemaking</HD>
        <P>11. On September 15, 2011, the Commission issued a Notice of Proposed Rulemaking (NOPR) proposing to approve the Version 4 CIP Reliability Standards.<SU>13</SU>
          <FTREF/>The NOPR also proposed to approve the related VRFs, VSLs with modifications, and implementation schedule proposed by NERC. To underscore the need to achieve full compliance with the directives in Order No. 706, the NOPR proposed to set a deadline by which date the ERO would be required to submit to the Commission for approval CIP Reliability Standards that are fully compliant with Order No. 706. The NOPR also addressed certain directives in Order No. 706 that have not yet been met, which would need to be satisfied by the proposed deadline.<SU>14</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>13</SU>
            <E T="03">Version 4 Critical Infrastructure Protection Reliability Standards,</E>76 FR 58,730 (Sept. 22, 2011), FERC Stats. &amp; Regs. ¶ 32,679 (2011) (NOPR).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>14</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at PP 40-61.</P>
        </FTNT>
        <P>12. In response to the NOPR, comments were filed by 28 interested entities. NERC submitted reply comments clarifying its position on one issue. Below, we address the issues raised by these comments. The Appendix to this Final Rule lists the entities that filed comments on the NOPR.</P>
        <HD SOURCE="HD1">II. Discussion</HD>
        <P>13. As discussed below, the Commission approves the eight modified Version 4 CIP Reliability Standards, finding that they are just and reasonable, not unduly discriminatory or preferential and in the public interest. In addition, the Commission approves NERC's proposed VRFs, VSLs with modifications, and its proposed implementation plan. The Commission has also determined that it is appropriate to impose a deadline for the ERO to achieve full compliance with Order No. 706. NERC commented that it anticipates filing the Version 5 CIP Reliability Standards by the third quarter of 2012.<SU>15</SU>
          <FTREF/>We therefore establish a deadline of 6 months from the end of the third quarter of 2012 (i.e., March 31, 2013), to provide the ERO with time to address any unforeseen contingencies. In addition, the Commission directs the ERO to submit quarterly reports, at the beginning of each quarter, in which it is to both confirm that it is on track to meet the deadline and describe the status of its CIP Reliability Standards development efforts.</P>
        <FTNT>
          <P>
            <SU>15</SU>NERC Reply Comments at 4.</P>
        </FTNT>
        <P>14. Below we discuss the Commission's basis for approving Version 4 of the CIP Reliability Standards. In addition, we discuss comments regarding: (1) The bright line criteria used to identify Critical Assets that are contained in Attachment 1 of Reliability Standard CIP-002-4; (2) the identification of Critical Assets that fall outside the scope of Attachment 1 by registered entities, Regional Entities, or ERO; (3) the implementation plan for the Version 4 CIP Reliability Standards; (4) compliance with Order No. 706; (5) the deadline for submitting CIP Reliability Standards that fully comply with Order No. 706; and (6) the VRFs and VSLs.</P>
        <HD SOURCE="HD2">A. The Commission Adopts the NOPR Proposal To Approve the Version 4 CIP Reliability Standards</HD>
        <HD SOURCE="HD3">NERC Petition</HD>
        <P>15. NERC states that CIP-002-4 establishes clear and uniform criteria for identifying Critical Assets on the Bulk-Power System.<SU>16</SU>
          <FTREF/>According to NERC, CIP-002-4 achieves a specified reliability goal by requiring the identification and documentation of Critical Cyber Assets associated with Critical Assets that support the reliable operation of the Bulk-Power System. NERC maintains that the Reliability Standard “improves reliability by establishing uniform criteria across all Responsible Entities for the identification of Critical Assets.”<SU>17</SU>
          <FTREF/>Further, NERC states that CIP-002-4 contains a technically sound method to achieve its reliability goal by requiring the identification and documentation of Critical Assets through the application of the criteria set forth in Attachment 1 of CIP-002-4.</P>
        <FTNT>
          <P>
            <SU>16</SU>NERC Petition at 38.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>17</SU>
            <E T="03">Id.</E>at 4.</P>
        </FTNT>
        <HD SOURCE="HD3">NOPR</HD>
        <P>16. In the NOPR, the Commission proposed to approve the Version 4 CIP Reliability Standards. Giving due weight to the ERO's petition, the NOPR stated that the Version 4 CIP Standards will result in the identification of certain types of Critical Assets that may not be identified under Version 3; uses bright line criteria to identify Critical Assets, eliminating the use of existing entity-defined risk-based assessment methodologies that, as currently applied, generally do not adequately identify Critical Assets; and provides a level of consistency and clarity regarding the identification of Critical Assets lacking under Version 3.<SU>18</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>18</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 21.</P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>
        <P>17. Most commenters and NERC generally support the Commission's proposal to approve the Version 4 CIP Reliability Standards.<SU>19</SU>
          <FTREF/>Hydro-Québec and NV Energy, however, oppose approval of Version 4,<SU>20</SU>
          <FTREF/>while the G&amp;T Cooperatives support Version 4 for “guidance purposes” only pending submission of a “Version 5” of the CIP Reliability Standards.<SU>21</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>19</SU>
            <E T="03">See, e.g.,</E>Trade Associates Comments at 2; FirstEnergy Comments at 1; KCP&amp;L Comments at 2; PG&amp;E Comments at 1; Tallahassee Comments at 1; Exelon Comments at 2; Dominion Comments at 3; NERC Comments at 3.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>20</SU>Hydro-Québec Comments at 6; NV Energy Comments at 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>21</SU>G&amp;T Cooperatives Comments at 3.</P>
        </FTNT>
        <P>18. Hydro-Québec opposes the bright line criteria because they capture assets based on factors such as voltages and amount of megawatts without assessing the asset's criticality to reliability. Hydro-Québec states that the Commission should consider allowing the current risk-based assessment methodology and a bright line approach to coexist.<SU>22</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>22</SU>Hydro-Québec Comments at 3-4.</P>
        </FTNT>
        <P>19. NV Energy believes that Version 4 unnecessarily expands the scope of the CIP Reliability Standards to facilities whose protection may offer only marginal value in preventing widespread cyber attacks on the bulk electric system.<SU>23</SU>
          <FTREF/>NV Energy asserts that no technical justification exists for the bright line criteria and, accordingly, NERC does not provide a sufficient basis to determine if Version 4 is just and reasonable or more effective than Version 3.<SU>24</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>23</SU>NV Energy Comments at 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>24</SU>
            <E T="03">Id.</E>at 3-4.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>

        <P>20. The Commission approves the Version 4 CIP Reliability Standards pursuant to section 215(d) of the FPA. The Commission concludes that the Version 4 CIP Reliability Standards are just, reasonable, not unduly discriminatory or preferential, and in the public interest. For the reasons identified in the NOPR, we approve Version 4 because it: Identifies Critical Assets that may not be identified under Version 3; will eliminate the use of<PRTPAGE P="24597"/>existing entity-defined risk-based assessment methodologies that, as applied, generally do not adequately identify Critical Assets; and provides a level of consistency and clarity regarding the identification of Critical Assets lacking under Version 3.</P>
        <P>21. With respect to the objections raised by Hydro-Québec and NV Energy, we find them unpersuasive. Although NV Energy asserts that Version 4 will identify Critical Assets that do not require protection or whose protection only offers marginal benefits, as we stated in the NOPR, Version 4 will offer an increase in the overall protection for bulk electric system components that clearly require protection, including control centers.<SU>25</SU>
          <FTREF/>Recognizing that Version 4 is an “interim step,” our concern is that Version 4 does not provide enough protection to satisfy Order No. 706.<SU>26</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>25</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 23 (“[T]he number of control centers identified as Critical Assets increases from 425 under Version 3 to 553 under Version 4, the latter figure representing 74 percent of all control centers.”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>26</SU>NERC Petition at 6.</P>
        </FTNT>
        <P>22. We also find unpersuasive Hydro-Québec and NV Energy's claim that the bright line criteria are based on arbitrary values (i.e., amounts of megawatts and voltages) without assessing the impact on reliability, or otherwise lack a technical justification. As discussed later in this final rule, the Commission finds that NERC offered an acceptable technical justification for the bright line criteria used to identify Critical Assets in Version 4. As indicated in the NOPR, we believe that Version 4 is an interim step towards full compliance with Order No. 706 and that implementation of Version 4 and concurrent retirement of Version 3, as proposed in the petition and reaffirmed by the ERO in its comments, is a step towards full compliance with Order No. 706.<SU>27</SU>
          <FTREF/>For the same reason, we reject the G&amp;T Cooperatives' suggestion that Version 4 be approved for “guidance purposes only.” Nevertheless, we note that approval of the specific bright line approach to identifying Critical Assets adopted in Version 4 does not prejudge the manner in which cyber assets are identified for protection in Version 5 or subsequent revisions to the CIP Reliability Standards.</P>
        <FTNT>
          <P>
            <SU>27</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 3.</P>
        </FTNT>
        <HD SOURCE="HD2">B. Bright Line Criteria for Identifying Critical Assets</HD>
        <P>23. Reliability Standard CIP-002-4 establishes criteria for identifying Critical Assets on the Bulk-Power System. Requirement R1 of Reliability Standard CIP-002-4, which pertains to the identification of Critical Assets, provides:</P>
        
        <EXTRACT>

          <P>The Responsible Entity shall develop a list of its identified Critical Assets determined through an annual application of the criteria contained in<E T="03">CIP-002-4 Attachment 1</E>—<E T="03">Critical Asset Criteria.</E>The Responsible Entity shall update this list as necessary, and review it at least annually.</P>
        </EXTRACT>
        
        <P>Attachment 1 to Reliability Standard CIP-002-4 provides seventeen criteria to be used by all responsible entities for the identification of Critical Assets pursuant to Requirement R1. The thresholds apply to specific types of facilities such as generating units, transmission lines and control centers. Reliability Standard CIP-002-4, Requirement R2 then requires responsible entities to develop a list of Critical Cyber Assets associated with the Critical Assets identified pursuant to Requirement R1.</P>
        <HD SOURCE="HD3">1. Generation/Transmission</HD>
        <HD SOURCE="HD3">NERC Petition</HD>
        <P>24. Several of the proposed criteria pertain to the identification of critical generation assets and critical transmission assets. Reliability Standard CIP-002-4, criterion 1.1 designates as Critical Assets: “Each group of generating units (including nuclear generation) at a single plant location with an aggregate highest rated net Real Power capability of the preceding 12 months equal to or exceeding 1500 MW in a single Interconnection.” Reliability Standard CIP-002-4, Requirement R2 qualifies criterion 1.1 by stating that: “For each group of generating units (including nuclear generation) at a single plant location identified in Attachment 1, criterion 1.1, the only Cyber Assets that must be considered are those shared Cyber Assets that could, within 15 minutes, adversely impact the reliable operation of any combination of units that in aggregate equal or exceed Attachment 1, criterion 1.1.”</P>
        <P>25. For transmission assets, criterion 1.6 designates as Critical Assets: “Transmission Facilities operated at 500 kV or higher.” Criterion 1.7 also designates as Critical Assets: “Transmission Facilities operated at 300 kV or higher at stations or substations interconnected at 300 kV or higher with three or more other transmission stations or substations.”</P>
        <P>26. Reliability Standard CIP-002-4, criterion 1.2 provides that “Each reactive resource or group of resources at a single location (excluding generation Facilities) having aggregate net Reactive Power nameplate rating of 1000 MVAR or greater” shall be designated as a Critical Asset. Criterion 1.3 designates as Critical Assets: “Each generation Facility that the Planning Coordinator or Transmission Planner designates and informs the Generator Owner or Generator Operator as necessary to avoid BES Adverse Reliability Impacts in the long-term planning horizon.” Criterion 1.8 designates as Critical Assets: “Transmission Facilities at a single station or substation location that are identified by the Reliability Coordinator, Planning Authority or Transmission Planner as critical to the derivation of Interconnection Reliability Operating Limits (IROLs) and their associated contingencies.” Criterion 1.9 designates as Critical Assets: “Flexible AC Transmission Systems (FACTS), at a single station or substation location, that are identified by the Reliability Coordinator, Planning Authority or Transmission Planner as critical to the derivation of Interconnection Reliability Operating Limits (IROLs) and their associated contingencies.”</P>
        <HD SOURCE="HD3">Comments</HD>
        <P>27. Hydro-Québec states that the term “group of generating units” used in criterion 1.1 is ambiguous because it could mean a generating station or a group of units sharing the same transformer. Hydro-Québec also believes that the 15-minute period, established by CIP-002-4, Requirement R2, which states that “the only Cyber Assets that must be considered are those shared Cyber Assets that could, within 15 minutes, adversely impact the reliable operation of any combination of units that in aggregate equal or exceed Attachment 1, criterion 1.1,” needs further explanation because it is unclear how to determine whether operation is not reliable after 15 minutes. Finally, Hydro-Québec contends that the term “Flexible AC Transmission System (FACTS)” in criterion 1.9 must be defined in the NERC Glossary of Terms.<SU>28</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>28</SU>Hydro-Québec Comments at 4-5.</P>
        </FTNT>

        <P>28. NV Energy comments that the bright line criteria lack technical justification because they are primarily based on asset size (<E T="03">e.g.,</E>megawatts and voltage levels) to determine criticality. NV Energy maintains that size should not be dispositive to determining whether an asset is critical. NV Energy cites the 500 kV or higher size threshold for transmission facilities in criterion 1.6 as an example of a broad categorization that is likely to capture elements, such as NV Energy's radial facilities, whose function are not essential to the reliable operation of the<PRTPAGE P="24598"/>bulk electric system. NV Energy also identifies the 300 kV or higher threshold for transmission facilities interconnected at 300 kV or higher with three or more other transmission stations or substations in criterion 1.7 as another example. NV Energy asserts that other parameters, beyond the number of interconnections, must be evaluated to determine criticality. Finally, NV Energy states that the 1500 MW threshold in criterion 1.1 lacks technical justification.<SU>29</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>29</SU>NV Energy Comments at 3-4.</P>
        </FTNT>
        <P>29. ISO/RTO Council states that responsibility for identifying critical generation should not be shifted from generation owners under criterion 1.3, which it maintains allows a planning coordinator or transmission planner to designate critical generation facilities.<SU>30</SU>
          <FTREF/>Likewise, MISO maintains that criteria 1.3, 1.8, and 1.9 place undue burden on reliability coordinators, planning authorities/coordinators, and transmission planners by requiring them to designate facilities as Critical Assets.<SU>31</SU>
          <FTREF/>ISO/RTO Council and MISO believe that these authorities have insufficient guidance or data to designate facilities as Critical Assets in a uniform manner. MISO seeks remand of these criteria or, in the alternative, argues that these entities should be indemnified and have limited liability for decisions to designate or not designate facilities as Critical Assets. MISO also encourages the Commission to make clear that requiring these entities to make designations does not shift compliance obligations from the registered entity that owns or operates a facility identified under these criteria.<SU>32</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>30</SU>ISO/RTO Council at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>31</SU>MISO Comments at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>32</SU>
            <E T="03">Id.</E>at 7.</P>
        </FTNT>
        <P>30. Further, MISO and ISO/RTO Council point to the lack of a mechanism for registered entities to challenge designations made by planning coordinators and transmission planners. MISO requests the establishment of such a mechanism.<SU>33</SU>
          <FTREF/>ISO/RTO Council states that the Commission “needs to consider how to address the rights of Generator Owners or Generator Operators in the context of designation under the CIP Standards, or otherwise explain why the Generator Owner or Generator Operator has no rights to challenge the Planning Coordinator or Transmission Planner's determination.”<SU>34</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>33</SU>
            <E T="03">Id.</E>at 8.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>34</SU>ISO/RTO Council Comments at 13.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>31. The Commission finds that the bright line criteria for designating generation and transmission assets as Critical Assets are acceptable and supported by the information contained in NERC's petition.</P>
        <P>32. In response to Hydro-Québec's comments, the Commission finds the term “group of generating units,” as used in criterion 1.1, to mean all generating units at a “single plant location,” as that term is defined in the “Rationale and Implementation Reference Document” for CIP-002-4 cited in the petition.<SU>35</SU>
          <FTREF/>“Single plant location” refers to a “group of generating units occupying a defined physical footprint, often but not always, these units are surrounded by a common fence, have a common entry point, share common facilities such as warehouses, water plants and cooling sources, follow a similar naming convention (plant name—unit number) and fall under a common management organization.”<SU>36</SU>
          <FTREF/>It is our understanding that the transformer used by a generating unit has no bearing under criterion 1.1 on whether a generating unit belongs to a “group of generating units.”</P>
        <FTNT>
          <P>
            <SU>35</SU>NERC Petition at 9 (<E T="03">citing</E>Rationale and Implementation Reference Document,<E T="03">http://www.nerc.com/docs/standards/sar/Project_2008-06_CIP-002-4_Guidance_clean_20101220.pdf</E>). The Rationale and Implementation Reference Document, dated December 2010, was also submitted as part of the NERC filing. As found on the Commission's eLibrary system in Docket No. RM11-11-00, the Rationale and Implementation Reference Document is found in Exhibit E (Development Record of the proposed CIP Reliability Standard and the associated Implementation Plans) beginning at page 2141 of the PDF electronic file submitted by NERC. This Final Rule refers to the page numbers used within the Rationale and Implementation Reference Document. The Rational and Implementation Reference Document states that it “provides guidance for Responsible Entities in the application of the criteria in CIP-002-4, Attachment 1. It provides clarifying notes on the intent and rationale of the Standards Drafting Team. It is not meant to augment, modify, or nullify any compliance requirements in the standard.” Rationale and Implementation Reference Document at 1.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>36</SU>Rationale and Implementation Reference Document at 8.</P>
        </FTNT>
        <P>33. As for Hydro-Québec's comments on the 15-minute trigger for CIP Reliability Standard coverage, NERC explains in its petition that “[i]n specifying a 15-minute qualification, Requirement R2 includes only those Cyber Assets that would have a real-time impact on the reliable operation of the Bulk Electric System.”<SU>37</SU>
          <FTREF/>Further, NERC explains that there may be generation facilities that, “while essential to the reliability and operability of the generation facility, may not have real-time operational impact within the specified real-time operations impact window of 15 minutes,” such as a cyber asset controlling the supply of coal fuel in a generation facility.<SU>38</SU>
          <FTREF/>We believe that NERC has provided adequate explanation and justification of this provision. To the extent that Hydro-Québec seeks specific advice on how to implement the Requirement, Hydro- Québec should raise the issue with the relevant Regional Entity or NERC.</P>
        <FTNT>
          <P>
            <SU>37</SU>NERC Petition at 12.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>38</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>34. With respect to Hydro-Québec's comment that the term “Flexible AC Transmission System (FACTS)” should be defined in the NERC Glossary of Terms, the Commission observes that the term is defined in the North American Energy Standards Board (NAESB) Wholesale Electric Industry Glossary,<SU>39</SU>
          <FTREF/>which is recognized in the NERC Rules of Procedure as a reference.<SU>40</SU>
          <FTREF/>Moreover, Hydro-Québec's comment does not suggest a lack of understanding of what the term means such that Hydro-Québec could not apply criterion 1.9.</P>
        <FTNT>
          <P>
            <SU>39</SU>
            <E T="03">Available at www.naesb.org/pdf/weq_glossary072804w3.doc.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>40</SU>NERC Rules of Procedure, Appendix 3A Standards Process Manual, at 22 (effective date January 31, 2012).</P>
        </FTNT>
        <P>35. The Commission disagrees with NV Energy's comments that the bright line criteria lack a technical justification because they are primarily based on asset size. While it is true that the standard establishes thresholds based on asset size, NERC articulated a basis for those values. For example, for the 1500 MW threshold in criterion 1.1, the petition states that the standard drafting team derived that number “from the most significant Contingency Reserves operated in various Balancing Authorities in all regions * * * [u]sing this number and data reported by the U.S. Energy Information Administration [], the team determined that approximately 146 generators in the United States would be classified as Critical Assets using this criterion * * * [t]his accounts for 29 percent of the installed generator capacity in the United States.”<SU>41</SU>
          <FTREF/>Moreover, as discussed above, the 15-minute trigger in CIP-002-4, Requirement R2, is a qualification to the asset size thresholds in criterion 1.1 and is meant to include only “Cyber Assets that would have a real-time impact on the reliable operation of the Bulk Electric System.”<SU>42</SU>

          <FTREF/>Considering the ERO's pleadings and affording due weight to the ERO's technical expertise, the<PRTPAGE P="24599"/>Commission accepts the ERO's justification for approval of the bright line criteria in Attachment 1.<SU>43</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>41</SU>NERC Petition at 15.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>42</SU>
            <E T="03">Id.</E>at 12.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>43</SU>16 U.S.C. 824o(d)(2).</P>
        </FTNT>
        <P>36. The Commission disagrees with MISO's and ISO/RTO Council's comment that criteria 1.3, 1.8, and 1.9 require reliability coordinators, planning coordinators/authorities, and transmission planners to review a registered entity's Critical Asset list or designate assets as Critical Assets. Instead, these criteria use the product of planning actions taken by reliability coordinators, planning coordinators/authorities, and transmission planners pursuant to other non-CIP Reliability Standards—these planning actions are, put simply, not made in conjunction with the application of CIP-002-4. The Commission also disagrees with MISO and ISO/RTO Council's comments that reliability coordinators, planning coordinators, and transmission planners should have the same liability protection as an entity externally reviewing Critical Asset lists, as was discussed in Order No. 706-A.<SU>44</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>44</SU>Order No. 706-A, 123 FERC ¶ 61,174 at P 53.</P>
        </FTNT>
        <P>37. Criteria 1.3, 1.8, and 1.9 require a responsible entity to identify generation and transmission facilities as Critical Assets when they have been determined as “necessary to avoid BES Adverse Reliability Impacts in the long-term planning horizon” (criterion 1.3) or “critical to the derivation of Interconnection Reliability Operating Limits (IROLs) and their associated contingencies” (criteria 1.8 and 1.9).</P>
        <P>38. First, this is not a discretionary action based on what a reliability coordinator, planning coordinator/authority, or transmission planner subsequently considers “necessary” to avoid adverse impacts. Rather, reliability coordinators, planning coordinators/authorities, and transmission planners make these underlying determinations as part of their compliance obligations associated with other (non-CIP) Reliability Standards. NERC developed a Rationale and Implementation Reference Document that provides guidance on implementation of the Attachment 1 criteria and supports our finding. This reference document associates criterion 1.3 with Reliability Standards TPL-003 and TPL-004: “If it is determined through system studies that a unit must run in order to preserve the reliability of the BES, such as due to a category C3 contingency as defined in TPL-003 or a category D contingency as defined in TPL-004, then that unit must be classified as a Critical Asset [under criterion 1.3].”<SU>45</SU>
          <FTREF/>Similarly, the Rationale and Implementation Reference Document associates criteria 1.8 and 1.9 with Reliability Standard FAC-014-2: “Parts 1.8 and 1.9 include those Transmission Facilities that have been identified as critical to the derivation of IROLs and their associated contingencies, as specified by FAC-014-2, Establish and Communicate System Operating Limits, R5.1.1 and R5.1.3.”<SU>46</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>45</SU>Rationale and Implementation Reference Document at 10.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>46</SU>
            <E T="03">Id.</E>at 13.</P>
        </FTNT>
        <P>39. Second, during development of the Version 4 CIP Reliability Standards, the standard drafting team addressed this issue in responding to a comment concerning criteria 1.3 that “[n]o entity should be able to simply `designate' another as having critical assets.”<SU>47</SU>
          <FTREF/>The standard drafting team responded by stating that “[t]he burden for identifying Critical Assets is with the Responsible Entity that is the asset owner * * * [t]he Planning Authority and/or Transmission Planner are not designating the asset as critical for CIP purposes; they are determining the unit to be necessary to avoid Adverse Reliability Impacts based on other NERC reliability standards.”<SU>48</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>47</SU>NERC Petition, Exhibit E, at 1548 of PDF electronic file.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>48</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>40. Third, transmission planners and planning authorities/coordinators cannot have a compliance obligation to designate Critical Assets under Reliability Standard CIP-002-4 because they are not identified as Applicable Entities under the Reliability Standard.<SU>49</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>49</SU>Section 302 of the NERC Rules of Procedure states that “Applicability—Each Reliability Standard shall clearly identify the functional classes of entities responsible for complying with the Reliability Standard, with any specific additions or exceptions noted * * *.” NERC Rules of Procedure at 3 (effective date January 31, 2012).</P>
        </FTNT>
        <P>41. In sum, under CIP-002-4, the responsible entity is required, and thus bears the compliance obligation, to apply the bright line criteria in Attachment 1 of CIP-002-4 to designate Critical Assets. We therefore reject the contention that reliability coordinators, planning coordinators/authorities, and transmission planners designate Critical Assets under the bright line criteria. We also disagree that CIP-002-4 imposes an undue burden on reliability coordinators, planning coordinators/authorities, and transmission planners because, as discussed above, determining whether an asset is “necessary to avoid BES Adverse Reliability Impacts in the long-term planning horizon” (criterion 1.3) or “critical to the derivation of Interconnection Reliability Operating Limits (IROLs) and their associated contingencies” is associated with existing Reliability Standards. However, the Commission does agree with MISO and ISO/RTO Council that additional clarity could be provided to ensure uniformity in implementation of criterion 1.3. To address the concerns of uniform implementation, the Commission believes that responsible entities would benefit from the ERO's guidance.</P>
        <P>42. We deny MISO and ISO/RTO Council's request that the Commission require an appeals process to challenge determinations made by planning coordinator and transmission planners pursuant to other Reliability Standards. An appeals process is neither necessary nor appropriate because the determinations by planning coordinator and transmission planners are made for purposes unrelated to cybersecurity. It is true that those determinations will be used by responsible entities when applying the bright line criteria in CIP-002-4. However, as discussed above, the responsible entities, and not planning coordinators and transmission planners, are ultimately responsible for compliance with the CIP Reliability Standards. Accordingly, we reject MISO and ISO/RTO Council's suggestion to direct NERC to develop an appeals process for determinations made by planning coordinators and transmission planners in the context of other Reliability Standards in this final rule approving the Version 4 CIP Reliability Standards.</P>
        <HD SOURCE="HD3">2. Blackstart/Must Run Units</HD>
        <HD SOURCE="HD3">NERC Petition</HD>
        <P>43. Reliability Standard CIP-002-4, criterion 1.3 designates as a Critical Asset: “Each generation Facility that the Planning Coordinator or Transmission Planner designates and informs the Generator Owner or Generator Operator as necessary to avoid BES Adverse Reliability Impacts in the long-term planning horizon.” Reliability Standard CIP-002-4, criterion 1.4 designates as a Critical Asset: “Each Blackstart Resource identified in the Transmission Operator's restoration plan.”</P>
        <HD SOURCE="HD3">Comments</HD>

        <P>44. ISO/RTO Council comments that criterion 1.4 pertaining to blackstart resources appears to conflict with the NERC Statement of Registry Criteria. ISO/RTO Council observes that while criterion 1.4 identifies as a Critical Asset “[e]ach Blackstart Resource identified in the Transmission Operator's restoration<PRTPAGE P="24600"/>plan,” the Registry Criteria provide for registration of “any generator, regardless of size, that is a blackstart unit<E T="03">material to and designated as</E>part of a transmission operator entity's restoration plan * * *”<SU>50</SU>
          <FTREF/>ISO/RTO Council suggests that “some Regional Entities may have determined that certain blackstart units are not material to the Transmission Operator's restoration plan, and are therefore, presumably not covered” by the Reliability Standards.<SU>51</SU>
          <FTREF/>Thus, ISO/RTO Council seeks clarification whether criterion 1.4 is meant to apply to blackstart units “covered” by the Registry Criteria or all blackstart resources and, if the latter, whether a revision to the Registry Criteria is appropriate.</P>
        <FTNT>
          <P>
            <SU>50</SU>NERC Statement of Compliance Registry Criteria (Revision 5.0) at 8 (Oct. 16, 2008) (emphasis added).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>51</SU>ISO/RTO Council Comments at 14.</P>
        </FTNT>
        <P>45. MISO comments that designating must run units as Critical Assets pursuant to criterion 1.3 may create an incentive for generation owners and generation operators to remove such units from service prior to their designation as Critical Assets.<SU>52</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>52</SU>MISO Comments at 9.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>46. With regard to ISO/RTO Council's comments, we note that NERC developed the Registry Criteria to identify users, owners and operators of the bulk electric system that are candidates for compliance registration. NERC does not apply the Registry Criteria to register particular assets.<SU>53</SU>
          <FTREF/>Moreover, whether NERC should revise the Registry Criteria is beyond the scope of this proceeding.<SU>54</SU>

          <FTREF/>That being said, it is not clear to us whether any substantive distinction is to be made between criterion 1.4, which implicates each blackstart resource identified in a restoration plan, and the Registry Criteria, which identifies as a candidate for registration the owner or operator of “a blackstart unit<E T="03">material to and designated as</E>part of a * * * restoration plan.” We leave it to NERC to consider whether a blackstart unit identified in a transmission operator's restoration plan could ever be considered immaterial to that plan and, if so, whether a clarification or revision to one or more documents is appropriate.</P>
        <FTNT>
          <P>
            <SU>53</SU>Order No. 706, 122 FERC ¶ 61,040 at P 50 (“the NERC registry process is designed to identify and register entities for compliance with Reliability Standards, and not identify lists of assets”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>54</SU>Order No. 706, 122 FERC ¶ 61,040 at P 49.</P>
        </FTNT>
        <P>47. We disagree with MISO that designating a “must run” unit as a Critical Asset may create an incentive for generation owners and generation operators to remove units from service prior to their designation as Critical Assets. The Commission is willing to consider rate filings to address this concern. For example, the Commission conditionally accepted a proposal filed by PJM to allow generators to recover costs related to compliance with mandatory NERC CIP Reliability Standards.<SU>55</SU>
          <FTREF/>Specifically, the Commission conditionally approved PJM's proposal in order to provide additional means for blackstart service providers to recover incremental costs associated with providing blackstart service.<SU>56</SU>
          <FTREF/>Finally, MISO can compensate “must run” generation units under System Support Agreements to prevent generators deemed as “must run” from being removed from service.</P>
        <FTNT>
          <P>
            <SU>55</SU>
            <E T="03">PJM Interconnection, L.L.C.,</E>138 FERC ¶ 61,020 (2012).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>56</SU>
            <E T="03">Id.</E>P 47.</P>
        </FTNT>
        <HD SOURCE="HD3">3. Control Centers/Control Systems</HD>
        <HD SOURCE="HD3">NERC Petition</HD>
        <P>48. Reliability Standard CIP-002-4, criteria 1.14-1.17 define the control centers and back up control centers that are treated as Critical Assets. Specifically, criterion 1.14 identifies as a bright line for Critical Assets “[e]ach control center or backup control center used to perform the functional obligations of the Reliability Coordinator.” Criterion 1.15 pertains to control centers or backup control centers used to control generation at multiple plant locations, equal to or exceeding 1500 MW. Criteria 1.16 and 1.17 include as Critical Assets control centers or backup control centers used to perform the functional obligations of transmission operators and balancing authorities, respectively.</P>
        <HD SOURCE="HD3">NOPR</HD>
        <P>49. In the NOPR, the Commission expressed concern, based on survey data supplied by NERC, that the Reliability Standard CIP-002-4 criteria would still leave a significant number of control centers unprotected.<SU>57</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>57</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 56.</P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>
        <P>50. Commenters hold diverging views on whether the Version 4 CIP Reliability Standards adequately protect control centers and control systems (i.e., control systems not housed in control centers). G&amp;T Cooperatives believe that Version 4 goes too far, while SPP RE and, to a lesser extent, MISO believe that it does not go far enough.<SU>58</SU>
          <FTREF/>NERC, PG&amp;E, and the Trade Associations acknowledge the NOPR's concern that CIP Version 4 does not protect some control centers/common control systems, but they anticipate that a future Version 5 CIP Reliability Standards will protect more Critical Assets.<SU>59</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>58</SU>G&amp;T Cooperatives Comments at 11-12; SPP RE Comments at 5-6; MISO Comments at 11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>59</SU>NERC Comments at 14-15; PG&amp;E Comments at 14; Trade Associations Comments at 7-8.</P>
        </FTNT>
        <P>51. G&amp;T Cooperatives believe that the Version 4 bright line criteria need additional work, which is why they support allowing a future Version 5 to supersede Version 4 before it becomes effective. Specifically, G&amp;T Cooperatives state that criteria 1.14, 1.16, and 1.17 “sweep in control centers and backup control centers, without regard to their size or potential impact on the [bulk electric system].”<SU>60</SU>
          <FTREF/>G&amp;T Cooperatives maintain that the bright line criteria should be revisited to ensure that they capture only those assets that should be covered in order to protect bulk electric system reliability.<SU>61</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>60</SU>G&amp;T Cooperatives Comments at 11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>61</SU>G&amp;T Cooperatives Comments at 10-13.</P>
        </FTNT>
        <P>52. SPP RE states that criteria 1.14-1.17 are insufficient because they do not consider interconnectivity of control centers or address the possibility that a small network-connected control center not deemed a Critical Asset could be used to compromise larger control centers. SPP RE believes that, at a minimum, all balancing authority and transmission operator control centers should be declared Critical Assets. SPP RE also encourages the Commission to consider requiring NERC to modify the bright line criteria to classify a control center as a Critical Asset if it is network-connected to other control centers.<SU>62</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>62</SU>SPP RE Comments at 5-6.</P>
        </FTNT>

        <P>53. With respect to common control systems, SPP RE believes that individual resources that do not qualify as Critical Assets under the bright line criteria can still pose a reliability risk if they have a common control system. SPP RE notes that under Version 4, a registered entity must designate its control center or generation facility as a Critical Asset in order to bring an associated common control system into scope. SPP RE believes that the bright line criteria may not ensure that all common control systems are identified, however. Criterion 1.1 designates as Critical Assets groups of generating units at a single plant location with an aggregate highest rated net Real Power capability equal to or exceeding 1500 MW. Criterion 1.15 designates as Critical Assets: “Each control center or backup control center used to control generation at multiple plant locations, for any generation Facility or group of<PRTPAGE P="24601"/>generation Facilities identified in criteria 1.1, 1.3, or 1.4. Each control center or backup control center used to control generation equal to or exceeding 1500 MW in a single Interconnection.” SPP RE states that criterion 1.1 adequately protects the common control systems of generating units at a single plant location with aggregate real power equal to or exceeding 1500 MW. However, SPP RE believes that criterion 1.15 does not clearly apply to control centers and common control systems that control generation that equals or exceeds 1,500 MW in the aggregate regardless of the individual plant size requirements set forth in criterion 1.1.<SU>63</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>63</SU>
            <E T="03">Id.</E>at 6-7.</P>
        </FTNT>
        <P>54. MISO expresses concern with Version 4's treatment of control centers. MISO asks for clarification whether Version 4 intentionally omitted “data centers” associated with control centers from the bright line criteria and whether registered entities have the discretion to designate them as Critical Assets. Because control centers often work in tandem with an associated data center, MISO recommends allowing registered entities to designate data centers as Critical Assets.<SU>64</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>64</SU>MISO Comments at 10-11.</P>
        </FTNT>
        <P>55. NERC and PG&amp;E acknowledge the NOPR's concern that Version 4 does not fully address the Order No. 706 directives pertaining to control centers. NERC and PG&amp;E temper this concern, however, by pointing to the lack of an accepted definition of “control centers” and the fact that some control centers in the generation context only communicate with generators that fall below the NERC Registration Criteria for generators. NERC and PG&amp;E suggest that cyber assets at these generator locations are unlikely to have a greater impact on reliability than much larger single-unit generators merely because the smaller units have a control center. In any case, NERC and PG&amp;E explain that under a future Version 5 every control center will be protected and will receive a “medium” or “high” level of security under a new three-tiered structure. Further, NERC and PG&amp;E state that several Version 5 requirements will apply to control centers regardless of whether they are classified as medium or high.<SU>65</SU>
          <FTREF/>NERC also states that “cyber misuse” will be a consideration under the classification process in CIP Version 5 and that the CIP Version 5 drafting team has proposed a definition of “control center.”<SU>66</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>65</SU>NERC Comments at 14-15; PG&amp;E Comments at 13-14.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>66</SU>NERC Comments at 15.</P>
        </FTNT>
        <P>56. The Trade Associations likewise recognize the NOPR's concern regarding control centers but state that control centers and control systems are being considered in the Version 5 project. The Trade Associations also state that appropriate prioritization and tailored application of mandatory requirements will be needed in addressing control centers and control systems given the widely varying circumstances and configurations in which these facilities are used.<SU>67</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>67</SU>Trade Associations Comments at 7-8.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>57. The Commission recognizes the diverging views among commenters regarding the protection of control centers and control systems afforded under the Version 4 CIP Reliability Standards. In Order No. 706, we stated that “it is difficult to envision a scenario in which a reliability coordinator, transmission operator or transmission owner control center or backup control center would not properly be identified as a critical asset.”<SU>68</SU>
          <FTREF/>The Commission maintains this view. However, as we observed in the NOPR, the percentage of control centers to be identified as Critical Assets under Version 4 is 74 percent, which is an improvement over the number currently identified under Version 3.<SU>69</SU>
          <FTREF/>Therefore, it is reasonable to approve Version 4 because it will ensure that more control centers are identified as Critical Assets than are identified under Version 3. However, we continue to expect comprehensive protection of all control centers and control systems as NERC works to comply with the requirements of Order No. 706.</P>
        <FTNT>
          <P>
            <SU>68</SU>Order No. 706, 122 FERC ¶ 61,040 at P 280.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>69</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 23.</P>
        </FTNT>
        <P>58. We agree with SPP RE that the CIP Reliability Standards should consider interconnectivity of control centers and the strategy of classifying a control center as a Critical Asset if it is network-connected to other control centers. The Commission also finds merit in MISO's comment that responsible entities should be allowed to designate data centers as Critical Assets because of their inherent connectivity to the control centers or control systems they support. Therefore, we expect NERC to address these approaches as it works to comply with the requirements of Order No. 706.<SU>70</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>70</SU>
            <E T="03">See, e.g.,</E>Order No. 706, 122 FERC ¶ 61,040 at PP 280-281.</P>
        </FTNT>
        <HD SOURCE="HD2">C. NOPR Questions on Critical Asset Identification</HD>
        <HD SOURCE="HD3">1. Flexibility To Identify Critical Assets That Fall Outside of the CIP Version 4 Bright Line Criteria</HD>
        <HD SOURCE="HD3">NOPR</HD>
        <P>59. In the NOPR, the Commission stated that under the currently-effective Reliability Standard CIP-002-3, a responsible entity that applies its risk-based assessment methodology considers specific types of assets identified in Requirement R1, as well as “any additional assets that support the operation of the Bulk Electric System that the Responsible Entity deems appropriate to include its assessment.”<SU>71</SU>
          <FTREF/>The Commission invited comment on whether a registered entity retains the same flexibility under Version 4 to identify assets that, although outside of the bright line criteria for identifying Critical Assets, are essential to Bulk-Power System reliability.</P>
        <FTNT>
          <P>
            <SU>71</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 31.</P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>
        <P>60. NERC states that, in developing Version 4, the drafting team considered adding criteria that would allow entities to identify additional facilities falling outside of the bright line criteria, but determined not to include the provision. However, NERC adds that “registered entities are permitted to apply any or all of the requirements in the CIP standards to assets that do not meet the bright-line thresholds.”<SU>72</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>72</SU>NERC Comments at 4.</P>
        </FTNT>
        <P>61. The Trade Associations and FirstEnergy believe that registered entities do not have the flexibility to identify Critical Assets that fall outside the bright line criteria such that they would be subject to mandatory and enforceable compliance obligations and should not have such flexibility because it would detract from the consistency afforded by the bright line criteria.<SU>73</SU>
          <FTREF/>The Trade Associations, however, state that registered entities have the discretion to identify facilities as Critical Assets provided those facilities are not subject to compliance obligations.<SU>74</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>73</SU>Trade Associations Comments at 4-5; FirstEnergy Comments at 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>74</SU>Trade Association Comments at 5.</P>
        </FTNT>

        <P>62. PG&amp;E comments that appropriate flexibility exists under Version 4 to allow the identification of Critical Assets essential to the bulk electric system. In particular, PG&amp;E cites to criterion 1.3, which would require a planning coordinator or transmission planner to identify a generation facility<PRTPAGE P="24602"/>as “critical” if “necessary to avoid BES Adverse Reliability Impacts in the long-term planning horizon.”<SU>75</SU>
          <FTREF/>Likewise, PG&amp;E indicates that criterion 1.8 provides that a reliability coordinator, planning authority, and transmission planner has authority to designate certain transmission facilities critical to the derivation of IROLs as critical. PG&amp;E also believes that industry should be encouraged to apply any or all of the CIP Reliability Standards to assets that do not meet the bright line criteria, “even beyond a compliance and audit program.”<SU>76</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>75</SU>PG&amp;E Comments at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>76</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>63. SPP RE encourages the Commission to require NERC to restore the “other” criterion to the bright line criteria.<SU>77</SU>
          <FTREF/>MISO likewise believes that registered entities should have the flexibility to identify more Critical Assets because the bright line criteria create a minimum regulatory floor on which to build.<SU>78</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>77</SU>SPP RE Comments at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>78</SU>MISO Comments at 11.</P>
        </FTNT>
        <HD SOURCE="HD3">2. NERC or Regional Entities' Ability To Identify Critical Assets That Fall Outside of the CIP Version 4 Bright-Line Criteria</HD>
        <HD SOURCE="HD3">NOPR</HD>
        <P>64. In the NOPR, the Commission invited comment on whether NERC and/or Regional Entities would have the ability, either in an event-driven investigation or compliance audit, to identify specific assets that fall outside the bright-line criteria yet are still essential to Bulk-Power System reliability and should be subject prospectively to compliance with the CIP Reliability Standards, and if so, on what basis should that decision be made.<SU>79</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>79</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 31.</P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>
        <P>65. NERC states that the Version 4 CIP Reliability Standards are an interim step and that the future Version 5 CIP Reliability Standards will refine the bright line criteria, with the intent of categorizing assets (to be termed “BES Cyber Systems”) as low, medium or high impact to Bulk-Power System reliability. NERC states that, in the interim, it has the authority under Section 810 of the NERC Rules of Procedure to issue an Alert to recommend specific actions. According to NERC, it can use the Alerts “as a tool to address assets that NERC and Regional Entities later determine should be treated as critical but to not fall into the CIP Version 4 criteria.”<SU>80</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>80</SU>NERC Comments at 4-7.</P>
        </FTNT>
        <P>66. The Trade Associations, Dominion, FirstEnergy and other commenters oppose identification of Critical Assets outside of the bright line process by NERC or Regional Entities as detracting from the clarity afforded by the bright line criteria. The Trade Associations and Tallahassee opine that the Commission should not undermine the bright line criteria by granting Regional Entities discretion to designate Critical Assets that are otherwise excluded by application of the bright line criteria.<SU>81</SU>
          <FTREF/>SPP RE states that it is not appropriate to apply arbitrarily criteria not found in the CIP Reliability Standards to require additional cyber systems to be subject to the CIP Reliability Standards.<SU>82</SU>
          <FTREF/>Dominion states that if such a mechanism is necessary, it should not be done in the compliance audit context.<SU>83</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>81</SU>Trade Association Comments at 5-6; Tallahassee Comments at 4-5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>82</SU>SPP RE Comments at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>83</SU>Dominion Comments at 4-5.</P>
        </FTNT>
        <P>67. MISO supports review of Critical Asset designations by NERC and Regional Entities given its belief that criteria 1.3, 1.8, and 1.9 require reliability coordinators, planning authorities/authorities and transmission planners to identify certain Critical Assets. MISO maintains that the lack of guidance for applying these criteria leaves room for substantial discretion, which may undermine the consistent identification of Critical Assets absent Regional Entity or NERC review.<SU>84</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>84</SU>MISO Comments at 4.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>68. We agree with NERC and others that registered entities can voluntarily apply any or all of the requirements in the CIP Reliability Standards to assets that fall outside the bright line criteria.<SU>85</SU>
          <FTREF/>As MISO described it, Version 4's bright line criteria establish a “regulatory floor” for cybersecurity, which must be followed by all registered entities.<SU>86</SU>
          <FTREF/>Nothing in Version 4 prevents registered entities from applying the protections required by the CIP Reliability Standards to additional assets that they deem critical. At the same time, we agree that assets not identified by the bright line criteria are not subject to a compliance obligation or to addition by the Commission, NERC, or a Regional Entity. We are persuaded that the clarity and addition of Critical Assets effected by the bright line criteria render Version 4 an improvement over Version 3.</P>
        <FTNT>
          <P>
            <SU>85</SU>NERC Comments at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>86</SU>MISO Comments at 11.</P>
        </FTNT>
        <P>69. We expect NERC to continue to work towards a version of the CIP Reliability Standards that will largely eliminate the risk of gaps in the identification of Critical Assets.<SU>87</SU>
          <FTREF/>In Section E of this Final Rule, we discuss the directive in Order No. 706 regarding external review in an effort to provide the ERO with guidance in developing future versions of the CIP Reliability Standards.</P>
        <FTNT>
          <P>
            <SU>87</SU>NERC Petition at 4.</P>
        </FTNT>
        <HD SOURCE="HD2">D. Implementation Plan</HD>
        <HD SOURCE="HD3">NERC Petition</HD>
        <P>70. NERC proposed an implementation plan for existing Critical Assets and an implementation plan for newly identified Critical Assets and newly registered entities. For existing Critical Assets, NERC proposed an effective date for full compliance with the Version 4 CIP Standards of the first day of the eighth calendar quarter after applicable regulatory approvals have been received. The implementation plan for newly identified Critical Assets and newly registered entities specifies how responsible entities are to handle newly identified Critical Cyber Assets, as well as how newly registered entities are to implement the CIP Reliability Standards after the effective date for Version 4.</P>
        <HD SOURCE="HD3">NOPR</HD>
        <P>71. In the NOPR, the Commission proposed to approve both the effective date and the implementation plan for CIP-002-4 based upon a belief that the proposed implementation plan establishes reasonable deadlines for industry compliance.<SU>88</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>88</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 39.</P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>
        <P>72. Comments varied regarding NERC's proposed implementation plan. NERC, PG&amp;E and Exelon support the CIP Version 4 implementation plan. PG&amp;E comments that the two year time frame, commencing from Commission approval, is reasonable. The Trade Associations support the implementation plan. However, they also urge the Commission to avoid a “one size fits all” approach, explaining that there are “complexities” of implementing “[CIP Versions] 3 to 4 to 5.”<SU>89</SU>

          <FTREF/>According to the Trade Associations, some entities may face significant challenges as the result of approval of Version 4 potentially followed so closely in time by the approval of Version 5. The Trade<PRTPAGE P="24603"/>Associations ask for coordination among NERC, the regions and registered entities to achieve compliance in an efficient and orderly manner. NERC and Exelon acknowledge that there could be concerns with implementing CIP Version 5 soon after Version 4 becomes effective, but note that CIP Version 5-related implementation issues could be revisited after CIP Version 5 is filed.<SU>90</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>89</SU>Trade Associations Comments at 13.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>90</SU>NERC Comments at 10; Exelon Comments at 3.</P>
        </FTNT>
        <P>73. G&amp;T Cooperatives, ISO/RTO Council, SPP RE, ITC, Dominion, and FirstEnergy oppose and/or recommend modifying the CIP Version 4 implementation plan in anticipation of a future CIP Version 5 filing. G&amp;T Cooperatives state that CIP Version 4 should be approved for “guidance purposes” only, thus delaying implementation, so that it may be superseded by CIP Version 5.<SU>91</SU>
          <FTREF/>G&amp;T Cooperatives believe that CIP Version 5 should become effective on the date that CIP Version 4 would otherwise become effective. Therefore, G&amp;T Cooperatives believe that NERC no longer intends that CIP Version 4 should go into effect in advance of CIP Version 5.</P>
        <FTNT>
          <P>
            <SU>91</SU>G&amp;T Cooperatives Comments at 10.</P>
        </FTNT>
        <P>74. ISO/RTO Council asks that the Commission provide guidance to NERC on how to exercise discretion on enforcement and implementation issues given the potential overlap and possible conflict with CIP Version 5.<SU>92</SU>
          <FTREF/>SPP RE suggests that the Commission allow entities to “early adopt” CIP Version 5.<SU>93</SU>
          <FTREF/>ITC recommends keeping CIP Version 4 in effect for at least three years so registered entities can collect a full three-year audit cycle's worth of data, which would avoid “frequent and abrupt changes” and could help later when implementing CIP Version 5.<SU>94</SU>
          <FTREF/>Dominion recommends allowing registered entities to discontinue implementation of CIP Version 4, while remaining compliant with CIP Version 3, if CIP Version 5 is approved by the Commission before the CIP Version 4 mandatory compliance date.<SU>95</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>92</SU>ISO/RTO Council Comments at 15.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>93</SU>SPP RE Comments at 7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>94</SU>ITC Comments at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>95</SU>Dominion Comments at 3.</P>
        </FTNT>
        <P>75. In its reply comments, NERC reiterates that it supports implementation of CIP Version 4 as filed. NERC rejects the G&amp;T Cooperatives' suggestion that NERC no longer intends that CIP Version 4 should go into effect in advance of CIP Version 5. NERC states that it recognizes the concerns raised by industry regarding the interplay between CIP Version 4 and CIP Version 5. However, NERC states that “until CIP Version 5 and an appropriate implementation plan is fully vetted and approved by the industry, the NERC Board of Trustees, and FERC, there is no basis to determine at this juncture that the CIP Version 4 standards should not be implemented.”<SU>96</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>96</SU>NERC Reply Comments at 3.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>76. The Commission adopts the NOPR proposal and approves both the effective date and the implementation plan for CIP-002-4 as just, reasonable, not unduly discriminatory or preferential, and in the public interest. The comments opposing NERC's proposed implementation plan for CIP-002-4 are all based upon concerns that the approval of CIP Version 4 may be followed very closely in time by a future Version 5 of the CIP Reliability Standards. We understand the commenters' interest in careful coordination, so that the industry can achieve compliance in an efficient and orderly manner as the industry moves from Version 3 to Version 5, via the interim Version 4. These concerns, however, do not provide a basis on which to reject the NOPR proposal.</P>
        <P>77. While G&amp;T Cooperatives, ISO/RTO Council, SPP RE, ITC, Dominion, and FirstEnergy outline various proposed solutions to a potential overlap between CIP Version 4 and a future Version 5 of the CIP Reliability Standards, the commenters ignore one critical fact—the only version of the CIP Reliability Standards at issue in this proceeding is Version 4. There is no proposed Version 5 of the CIP Reliability Standards before the Commission at this time, so any concerns raised about implementation of Version 5 are beyond the scope of this proceeding. To the extent that the development of Version 5 raises actual implementation concerns, such concerns should be raised when NERC submits Version 5 for approval. This proceeding is not the appropriate forum to determine how to coordinate the implementation of the CIP Version 4 Reliability Standards with possible future versions of the CIP Reliability Standards that have not yet been developed or submitted for approval to the Commission.</P>
        <HD SOURCE="HD2">E. Compliance With Order No. 706</HD>
        <P>78. In the petition, NERC stated that the standard drafting team “limited the scope of requirements in the development of CIP-002-4 through CIP-009-4 as an interim step to address the more immediate concerns raised in FERC Order No. 706, paragraph 236.”<SU>97</SU>
          <FTREF/>NERC further stated that the standard drafting team is continuing its effort to address the remaining outstanding Order No. 706 directives. NERC explained that its phased approach to meeting the Order No. 706 directives has “consistently built upon prior versions of the CIP-002 through CIP-009 standards to enhance the reliability of the Bulk Electric System.”<SU>98</SU>
          <FTREF/>In that light, the Commission discussed certain outstanding Order No. 706 directives in the NOPR and proposed giving guidance to aid in the development of the next version of the CIP Reliability Standards.</P>
        <FTNT>
          <P>
            <SU>97</SU>NERC Petition at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>98</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>79. In their comments, the Trade Associations seek clarification as to whether the issues discussed in Section B of the NOPR (i.e., connectivity, control centers, and NERC and Regional Entity review of Critical Asset lists) should be viewed merely as encouragement to address those issues in CIP Version 5 or as new directives beyond what was required in Order No. 706.<SU>99</SU>
          <FTREF/>The Trade Associations explain that it is their expectation that the final rule will not include any further directives. Instead, the Trade Associations encourage the Commission to allow development of CIP Version 5 to move forward without introducing any new uncertainties in a final rule on CIP Version 4. Based on the comments in response to the NOPR, we determine not to issue new directives at this time beyond what is required to comply with Order No. 706. Consistent with the NOPR proposal, we provide guidance for future versions of the CIP Reliability Standards regarding the issues of connectivity, application of the National Institute of Standards and Technology (NIST) Framework, and provision of a regional perspective.</P>
        <FTNT>
          <P>
            <SU>99</SU>Trade Association Comments at 10.</P>
        </FTNT>
        <HD SOURCE="HD3">1. Connectivity</HD>
        <HD SOURCE="HD3">NOPR</HD>
        <P>80. In the NOPR, the Commission stated that:</P>
        
        <EXTRACT>

          <P>In light of recent cybersecurity vulnerabilities, threats and attacks that have exploited the interconnectivity of cyber systems, the Commission seeks comments regarding the method of identification of Critical Cyber Assets to ensure sufficiency and accuracy. The Commission recognizes that control systems that support Bulk-Power System reliability are “only as secure as their weakest links,” and that a single vulnerability opens the computer network and all other networks with which it is interconnected to potential malicious activity. Accordingly, the Commission believes that any criteria adopted for the<PRTPAGE P="24604"/>purposes of identifying a Critical Cyber Asset under CIP-002 should be based upon a Cyber Asset's connectivity and its potential to compromise the reliable operation of the Bulk-Power System, rather than focusing on the operation of any specific Critical Asset(s). [<E T="03">Footnotes omitted.</E>]<SU>100</SU>
            <FTREF/>
          </P>
        </EXTRACT>
        <FTNT>
          <P>
            <SU>100</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 43.</P>
        </FTNT>
        
        <FP>The Commission invited comment on this approach.</FP>
        <HD SOURCE="HD3">Comments</HD>
        <P>81. NERC comments that, while it does not believe that the connectivity issue was raised in Order No. 706, the CIP Version 5 standards drafting team recognizes the importance of the matter and is considering it in the development of Version 5.<SU>101</SU>
          <FTREF/>However, NERC does not believe that connectivity can be addressed in CIP Version 5 by the time it is submitted to the NERC Board of Trustees for approval.<SU>102</SU>
          <FTREF/>NERC notes that CIP Version 5 will eliminate the blanket exemption for non-routably connected cyber systems, “and instead move[s] the connectivity attribute to specific requirements.”<SU>103</SU>
          <FTREF/>NERC adds that the CIP Version 5 drafting team has proposed to apply electronic security perimeter protections “of some form” to include all bulk electric system Cyber Systems.<SU>104</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>101</SU>NERC Comments at 11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>102</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>103</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>104</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>82. SPP RE states that neither CIP Version 4 nor CIP Version 5 consider all possible communication paths between a given cyber asset and any assets that support a reliability function. According to SPP RE, the Version 4 standards define bright line criteria based on size of the asset, and the draft Version 5 standards would rate cyber systems based on their span of control, but fail to consider interconnectivity and the potential for a small system to be used as a vector of attack against other systems.<SU>105</SU>
          <FTREF/>SPP RE explains that control center cyber systems routinely exchange data with reliability coordinators, over wide area networks.<SU>106</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>105</SU>SPP RE Comments at 3-5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>106</SU>
            <E T="03">Id.</E>at 3-4.</P>
        </FTNT>
        <P>83. ISO/RTO Council states that the Commission's concerns with connectivity could be addressed by requiring certain asset owners and operators to take a “mutual distrust” posture.<SU>107</SU>
          <FTREF/>MISO supports considering the connectivity issue but also encourages the Commission to evaluate the costs and benefits of this approach.</P>
        <FTNT>
          <P>
            <SU>107</SU>ISO/RTO Council Comments at 17.</P>
        </FTNT>
        <P>84. PG&amp;E states that issues pertaining to connectivity are being addressed in CIP Version 5.<SU>108</SU>
          <FTREF/>The Trade Associations state that they understand the Commission's concerns regarding connectivity. But taken together with the NOPR's “weakest link” statements, the Trade Associations are concerned these views could imply that everything needs to be protected.<SU>109</SU>
          <FTREF/>The Trade Associations believe that the “weakest link” concept articulated in the NOPR needs to be fleshed out in more detail and that Commission staff should work with the CIP Version 5 standard drafting team to discuss these issues. The Trade Associations also maintain that the CIP Version 5 standard drafting team is currently working on addressing the Commission's directives in Order No. 706 and that no further directives regarding connectivity, or otherwise, should be made in the final rule approving CIP Version 4. According to the Trade Associations, any directives in the final rule would serve to prejudge CIP Version 5.</P>
        <FTNT>
          <P>
            <SU>108</SU>PG&amp;E Comments at 9.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>109</SU>Trade Associations Comments at 18.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>85. The Commission appreciates the comments on whether cyber connectivity should be a basis for the identification of Critical Cyber Assets, or their equivalent, in future versions of the CIP Reliability Standards. We have raised concerns relating to the use of cyber connectivity as a basis for applying the CIP Reliability Standards during and since the approval of Version 1. For example, in Order No. 706, we stated that “NERC's compliance [with the CIP Reliability Standards] is necessary in light of its interconnectivity with other entities that own and operate critical assets.”<SU>110</SU>
          <FTREF/>Similarly, in finding that an “N minus 1” criterion is not an appropriate risk-based assessment methodology for identifying Critical Assets, we noted that a cyber attack can strike multiple assets simultaneously.<SU>111</SU>
          <FTREF/>The cyber connectivity of Bulk-Power System assets increases the risk of a multiple asset cyber attack. The CIP Reliability Standards should reflect this risk.</P>
        <FTNT>
          <P>
            <SU>110</SU>Order No. 706, 122 FERC ¶ 61,040 at P 47.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>111</SU>
            <E T="03">Id.</E>P 256.</P>
        </FTNT>
        <P>86. In that light, we support the elimination of the blanket exemption for non-routable connected cyber systems as highlighted in NERC's comments.<SU>112</SU>
          <FTREF/>A continued blanket exemption in Version 5 would not adequately address risk.</P>
        <FTNT>
          <P>
            <SU>112</SU>NERC Comments at 11.</P>
        </FTNT>
        <P>87. In addition, we support the concept of applying electronic security perimeter protections “of some form” to all bulk electric system cyber systems.<SU>113</SU>
          <FTREF/>Because electronic communications between functional entities and their associated systems are essential to the operation of the Bulk-Power System, it is important for each distinct system to be protected at its boundary by an electronic security perimeter. The use of electronic security perimeters, as required under the CIP Reliability Standards, is commonly referred to as zoned security in the information security industry.<SU>114</SU>
          <FTREF/>Security zones are established to ensure that a compromise in one security zone does not lead to a compromise in another security zone across a security perimeter.<SU>115</SU>
          <FTREF/>The Commission is encouraged by NERC's comments that its standard drafting team is considering ways to address connectivity issues and electronic perimeter protections surrounding all BES Cyber Systems.</P>
        <FTNT>
          <P>
            <SU>113</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>114</SU>A “security zone” is defined by the ISA99 Committee on Industrial Automation and Control Systems Security as a “grouping of logical or physical assets that share common security requirements.” Security for Industrial Automation and Control Systems Part 1: Terminology, Concepts, and Models, ISA-99.00.01-2007.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>115</SU>A “security perimeter” is defined by the ISA99 Committee on Industrial Automation and Control Systems Security as a “boundary (logical or physical) of the domain in which a security policy or security architecture applies, i.e. the boundary of the space in which security services protect system resources.” Security for Industrial Automation and Control Systems Part 1: Terminology, Concepts, and Models, ISA-99.00.01-2007.</P>
        </FTNT>
        <P>88. We also agree with SPP RE that the CIP Reliability Standards should consider communication paths between a given cyber asset and other assets that support a reliability function.<SU>116</SU>
          <FTREF/>As noted by SPP RE, cyber security standards that categorize cyber systems based upon the size or scope of the assets that they control “fail to consider the interconnectivity of the BES Cyber Systems and the potential for a small control center system to be used as a vector of attack against a larger control center system.”<SU>117</SU>
          <FTREF/>As noted by SPP RE, “[c]ontrol center BES Cyber Systems routinely exchange operational data with each other as required by NERC Reliability Standard TOP-005-2a.”<SU>118</SU>
          <FTREF/>As further noted by SPP RE, connectivity is important to address because of the required communications from control centers to and between reliability coordinators under the Interconnection Reliability Operations and Coordination Standards.<SU>119</SU>

          <FTREF/>The Commission agrees that cyber connectivity is important to address<PRTPAGE P="24605"/>when developing future versions of the CIP Reliability Standards. That being said, we acknowledge the concern of Trade Associations that the “connectivity” and “weakest link” concepts could possess different meanings to various stakeholders.<SU>120</SU>
          <FTREF/>Thus, addressing connectivity should include reaching a common understanding of the term. Further, we understand and agree with the Trade Associations' concern that protection should be applied in a reasonable manner.<SU>121</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>116</SU>SPP RE Comments at 3-4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>117</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>118</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>119</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>120</SU>Trade Associations Comments at 18.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>121</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>89. Recognizing the importance of addressing cyber connectivity in future versions of the CIP Reliability Standards, we encourage NERC to consider the benefits of a “mutual distrust” posture, or similar strategies, put forth by the ISO/RTO Council<SU>122</SU>
          <FTREF/>and as directed by the Commission in Order No. 706.<SU>123</SU>
          <FTREF/>In Order No. 706, the Commission used the term “mutual distrust” to denote how “outside world” systems are treated by those inside the control system.<SU>124</SU>
          <FTREF/>Specifically, a mutual distrust posture requires each responsible entity that has identified critical cyber assets to protect itself and not trust any communication crossing an electronic security perimeter, regardless of where that communication originates.<SU>125</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>122</SU>ISO/RTO Council Comments at 17.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>123</SU>Order No. 706, 122 FERC ¶ 61,040 at P 412 (“The Commission therefore directs the ERO to provide guidance, regarding the issues and concerns that a mutual distrust posture must address in order to protect a responsible entity's control system from the outside world.”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>124</SU>
            <E T="03">Id.</E>P 33.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>125</SU>
            <E T="03">Id.</E>n.24.</P>
        </FTNT>
        <P>90. Applying electronic security perimeter protections “of some form” to bulk electric system cyber systems covered by the CIP Reliability Standards will support the adoption of a “mutual distrust” posture. This posture will encourage asset owners and operators to employ sound network architectural design, thus segmenting their systems into distinct security zones protected by managed interfaces that will allow only trusted access. The managed interfaces, or electronic security perimeter access points, are intended to restrict or prohibit network access and information flow to bulk electric system cyber systems covered by the CIP Reliability Standards from unidentified, unauthenticated, and unauthorized connectivity to ensure security. Multiple electronic security perimeters can be established to protect cyber assets and adopted as part of a defense in depth strategy to limit the propagation of a threat.<SU>126</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>126</SU>“Defense in depth” is defined by the ISA99 Committee on Industrial Automation and Control Systems Security as the “provision of multiple security provisions, especially in layers, with the intent to delay if not prevent an attack. NOTE: Defense in depth implies layers of security and detection, even on single systems, and provides the following features: attackers are faced with breaking through or bypassing each layer without being detected; a flaw in one layer can be mitigated by capabilities in other layers; system security becomes a set of layers within the overall network security.” Security for Industrial Automation and Control Systems Part 1: Terminology, Concepts, and Models, ISA-99.00.01-2007.</P>
        </FTNT>
        <P>91. Having considered the feedback to our question on cyber connectivity, we continue to believe that criteria adopted for the purpose of identifying Critical Cyber Assets under CIP-002 should include a cyber asset's “connectivity” and its potential to compromise the reliable operation of the Bulk-Power System. Therefore, we expect Version 5 to address these issues.</P>
        <HD SOURCE="HD3">2. Application of NIST Framework</HD>
        <HD SOURCE="HD3">NOPR</HD>
        <P>92. In the NOPR, the Commission elaborated on the Order No. 706 guidance regarding the consideration of the NIST Framework when developing CIP Reliability Standards.<SU>127</SU>
          <FTREF/>The NOPR explained that the NIST Framework recognizes that all connected assets require a baseline level of protection to prevent attackers from gaining a foothold to launch further, even more devastating attacks on other critical systems.<SU>128</SU>
          <FTREF/>The Commission invited comment on this approach.</P>
        <FTNT>
          <P>
            <SU>127</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at PP 46-52.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>128</SU>
            <E T="03">Id.</E>P 51.</P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>
        <P>93. NERC, PG&amp;E, SPP RE, and MISO support applying aspects of the NIST Framework to the CIP Reliability Standards, which could lead to more bulk electric system components being protected, though at different levels depending on their criticality. NERC and PG&amp;E state that the CIP Version 5 standard drafting team has incorporated four key features of the NIST Framework into the draft CIP Version 5.<SU>129</SU>
          <FTREF/>NERC states, however, that the NIST standards/guidelines should not be adopted in total because elements of the NIST standards/guidelines, which are meant to help federal agencies to manage risks to their information systems in support of their unique missions, are inapplicable to the power sector.<SU>130</SU>
          <FTREF/>NERC and MISO point out that the NIST Framework allows for applicable NIST concepts to be tailored and incorporated into the CIP Reliability Standards, which has been the approach of the standard drafting team in developing CIP Version 5.</P>
        <FTNT>
          <P>
            <SU>129</SU>NERC Comments at 13; PG&amp;E Comments at 11-12.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>130</SU>NERC Comments at 12-13.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>94. The Commission finds the feedback provided on the potential application of the NIST Framework to the CIP Reliability Standards to be useful. We agree with the commenters that support applying applicable features of the NIST Framework to Version 5 of the CIP Reliability Standards. As stated in the NOPR, we believe that the NIST Framework could provide beneficial input into the CIP Reliability Standards.<SU>131</SU>
          <FTREF/>In its comments, NERC states that a standards drafting team is incorporating four key features of the NIST Framework into the Version 5 CIP Reliability Standards: (1) Ensuring that all BES Cyber Systems associated with the Bulk-Power System, based on their function and impact, receive some level of protection; (2) customizing protection to the mission of the cyber systems subject to protection; (3) applying a tiered approach to security controls that specifies the level of protection appropriate for systems based upon their importance to the reliable operation of the Bulk-Power System; and (4) using the concept of the BES Cyber System.<SU>132</SU>
          <FTREF/>We view the approach of incorporating these applicable features of the NIST Framework into the CIP Reliability Standards as a positive step in improving cyber security for the Bulk-Power System.</P>
        <FTNT>
          <P>
            <SU>131</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 46.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>132</SU>NERC Comments at 13-14. NERC comments that the next version of the CIP Reliability Standards replaces the identification of “Critical Assets” with the categorization of “BES Cyber Systems.” Specifically, NERC states that “BES Cyber Systems will be characterized as `High Impact,' `Medium Impact,' or `Low Impact' based on the impact of the cyber system to the reliable operation of the bulk power system * * * [t]his characterization makes use of a bright-line concept similar to Version 4, but requires responsible entities to determine the impact of loss, compromise or misuse of a given BES Cyber System using a bright-line impact filter.” NERC Comments at 7.</P>
        </FTNT>
        <P>95. NIST standards are used by industry generally as a reference and can be applied by the ERO to the Bulk-Power System.<SU>133</SU>
          <FTREF/>Therefore, we<PRTPAGE P="24606"/>continue to encourage NERC and industry to include aspects of the NIST Framework and standards into subsequent versions of the CIP Reliability Standards to better protect the Bulk-Power System. Similar to our approach in Order No. 706, we continue to urge NERC to look to relevant NIST standards for guidance in developing effective cybersecurity standards for the electric industry.<SU>134</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>133</SU>For example, NIST SP800-82 provides a detailed Guide to Industrial Control Systems Security that is relevant to the electric power industry. Specifically, NIST SP800-82 includes recommendations to assist in the protection of Supervisory Control and Data Acquisition systems, Distributed Control Systems, and other control system configurations such as Programmable Logic<PRTPAGE/>Controllers.<E T="03">See</E>National Institute of Standard and Technology, Guide to Industrial Control Systems (ICS) Security (NIST SP900-82) (2011),<E T="03">http://csrc.nist.gov/publications/nistpubs/800-82/SP800-82-final.pdf.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>134</SU>Order No. 706, 122 FERC ¶ 61,040 at P 233 (directing the ERO “to consult with federal entities that are required to comply with both CIP Reliability Standards and NIST standards on the effectiveness of the NIST standards and on implementation issues and [to] report these findings to the Commission”).</P>
        </FTNT>
        <HD SOURCE="HD3">3. Regional Perspective</HD>
        <HD SOURCE="HD3">NOPR</HD>
        <P>96. In the NOPR, the Commission highlighted the Order No. 706 directive for NERC to “develop a process of external review and approval of critical asset lists based on a regional perspective.”<SU>135</SU>
          <FTREF/>The NOPR explained the Commission's concern that a lack of a regional review of a registered entity's identification of cyber assets might result in a reliability gap. In addition, the Commission discussed concerns regarding cyber systems spanning multiple regions:</P>
        <FTNT>
          <P>

            <SU>135</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at PP 59-61 (<E T="03">citing</E>Order No. 706, 122 FERC ¶ 61,040 at P 329).</P>
        </FTNT>
        
        <EXTRACT>
          <P>This problem may be exacerbated by any future revisions to the CIP Reliability Standards that opt to reserve a high level of independent authority to the registered entity to categorize and prioritize its cyber assets. Looking forward, it will be essential for NERC and the Regional Entities to actively review the designation of cyber assets that are subject to the CIP Reliability Standards, including those which span regions, in order to determine whether additional cyber assets should be protected.<SU>136</SU>
            <FTREF/>
          </P>
        </EXTRACT>
        <FTNT>
          <P>
            <SU>136</SU>
            <E T="03">Id.</E>P 61.</P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>
        <P>97. NERC states that the bright line criteria adopted under Version 4 of the CIP Reliability Standards provide certainty and clarity as to the assets that should be identified as critical. NERC explains that the CIP Reliability Standard drafting team is further refining the bright line criteria and anticipates that the next version of the CIP Reliability Standards will characterize “BES Cyber Systems” (in lieu of cyber assets) with “high,” “medium,” or “low” impact on Bulk-Power System reliability. According to NERC, “[t]his characterization makes use of a bright line concept similar to Version 4, but requires responsible entities to determine the impact of loss, compromise or misuse of a given BES Cyber System using a bright line impact filter.”<SU>137</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>137</SU>NERC Comments at 7. NERC states in its comments that the CIP standard drafting team is considering the adoption of the term “BES Cyber Systems” in the next version of the CIP Reliability Standards. Our discussion below uses the term “cyber assets” to include any cyber asset or systems that the ERO eventually designates as needing cyber security protections under the CIP Reliability Standards.</P>
        </FTNT>
        <P>98. The Trade Associations state that they cannot support the NOPR proposal on redesignation of assets based on a “regional view” without specific information about the mechanics of the proposal or the nature of the perceived reliability gap. According to the Trade Associations, registered entities are in the best position to determine which of their cyber assets are critical to the operation of Critical Assets and therefore subject to CIP compliance. The Trade Associations contend that NERC and the Regional Entities have the opportunity to review a registered entity's approach to developing its list of Critical Cyber Assets in the context of a compliance audit or other compliance monitoring process.</P>
        <P>99. FirstEnergy states that the bright line criteria should be the sole methodology for identifying Critical Assets and that allowing the ERO or Regional Entities the ability to add assets that fall outside the bright line criteria undermines the purpose of the bright line criteria.<SU>138</SU>
          <FTREF/>Tallahassee states that the Commission should not undermine the value of the bright line criteria by granting the Regional Entities the discretion to designate assets as critical if the assets are not otherwise identified by the bright line criteria.</P>
        <FTNT>
          <P>
            <SU>138</SU>FirstEnergy Comments at 2.</P>
        </FTNT>
        <P>100. SPP RE, for its part, states that it is not appropriate to apply arbitrarily criteria not listed in the CIP Reliability Standards to require additional cyber assets to be subject to the CIP Reliability Standards. SPP RE states that the appropriate way to address any concern that the bright line criteria do not capture all assets that should be protected is to modify the bright line criteria to address any deficiency.</P>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>101. In Order No. 706, the Commission explained the need for external review of the Critical Asset lists in the context of an earlier version of the CIP Reliability Standards that required registered entities to apply individualized risk-based methodologies to identify Critical Assets.<SU>139</SU>
          <FTREF/>Further, as indicated in the NOPR in the immediate proceeding, the Commission's concerns are “exacerbated by any future revisions to the CIP Reliability Standards that opt to reserve a high level of independent authority to the registered entity to categorize and prioritize its cyber assets.”<SU>140</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>139</SU>Order No. 706, 122 FERC ¶ 61,040 at PP 298, 322.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>140</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 61.</P>
        </FTNT>
        <P>102. We agree with commenters that the adoption of appropriate, bright line criteria for Critical Asset identification may obviate the need for an external review. We believe that there is less need for external review where application of bright line criteria results in an objective, consistently applied approach to the identification of cyber assets. As discussed above, NERC anticipates the development of tiered, bright line criteria in the next version of the CIP Reliability Standards. Whether this development ultimately eliminates the need for an external review process as directed in Order No. 706 will depend on the discretion allowed to individual registered entities in identifying and characterizing assets or systems.</P>
        <P>103. However, even with the adoption of clear and objective criteria, we believe that there remains a need for an entity with a regional perspective, presumably the ERO or a Regional Entity, to have the opportunity to identify or adjust the characterization of cyber assets in some circumstances. For example, an event may reveal that a specific cyber asset has a greater impact than previously recognized. In such circumstance, an objective third party should have the opportunity to designate a cyber asset prospectively as critical or recharacterize the impact of a cyber asset for compliance purposes.<SU>141</SU>
          <FTREF/>Likewise, it is possible that a technological development or newly discovered vulnerability could justify a case-specific adjustment.</P>
        <FTNT>
          <P>
            <SU>141</SU>Order No. 706, 122 FERC ¶ 61,040 at P 325.</P>
        </FTNT>

        <P>104. We agree with SPP RE that a modification of one or more of the bright line criteria is an appropriate response to a generic change in risk or impact of a category of cyber assets. Accordingly, as a reasonable application of the Order No. 706 directive that an entity with a regional approach have oversight of Critical Asset identification, NERC and the regions—or another designated third party—should have the authority in some circumstances, such as those discussed above, to designate a cyber asset as critical or adjust the<PRTPAGE P="24607"/>“impact” characterization. In addressing the Order No. 706 directives, NERC should develop appropriate provisions to implement this limited opportunity for review.</P>
        <HD SOURCE="HD2">F. Deadline for Addressing Order No. 706 Directives</HD>
        <HD SOURCE="HD3">NERC Petition</HD>
        <P>105. In the petition, NERC states that the standard drafting team is continuing to address the outstanding Order No. 706 directives.<SU>142</SU>
          <FTREF/>NERC notes that the next version of the CIP Reliability Standards “will build on the CIP-002-4 standards' establishment of uniform criteria for the identification of Critical Assets.”<SU>143</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>142</SU>NERC Petition at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>143</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD3">NOPR</HD>
        <P>106. In the NOPR, the Commission invited comment on whether a reasonable deadline should be established for NERC to satisfy the outstanding directives in Order No. 706 pertaining to the CIP Reliability Standards based on NERC's current development timeline for CIP Version 5.<SU>144</SU>
          <FTREF/>Based on the then current NERC timeline, the NOPR proposed that the CIP Version 5 filing be made by the end of the third quarter of 2012.</P>
        <FTNT>
          <P>
            <SU>144</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 67.</P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>
        <P>107. Comments varied as to the imposition of a deadline for NERC to file CIP Version 5. Most comments support at least a soft filing date coupled with periodic informational filings on the status of CIP Version 5. While some comments support a hard deadline, that support is qualified.</P>
        <P>108. NERC, ISO/RTO Council, PG&amp;E, and Dominion offer qualified support for a deadline. NERC supports the proposed deadline, provided: the CIP Version 4 Final Rule does not add to or expand on the Order No. 706 directives; NERC is able to use its standard development process; and CIP Version 5 only requires one successive ballot.<SU>145</SU>
          <FTREF/>PG&amp;E likewise believes that the proposed deadline is attainable provided the CIP Version 4 Final Rule does not expand on the Order No. 706 directives.<SU>146</SU>
          <FTREF/>ISO/RTO Council states that a deadline is reasonable as long as there is sufficient time for stakeholder input.<SU>147</SU>
          <FTREF/>However, ISO/RTO Council is skeptical about the current development timeline. Dominion also supports a hard deadline as long as CIP Version 5 is developed through the normal NERC standard development process.<SU>148</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>145</SU>NERC Comments at 8-9.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>146</SU>PG&amp;E Comments at 8.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>147</SU>ISO/RTO Comments at 16.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>148</SU>Dominion Comments at 4.</P>
        </FTNT>
        <P>109. The Trade Associations, AMP, Exelon, FirstEnergy, and KCP&amp;L do not support a hard deadline for filing CIP Version 5.<SU>149</SU>
          <FTREF/>The Trade Associations, supported by FirstEnergy and KPC&amp;L, and AMP believe that the development schedule for CIP Version 5 is aggressive and may need to be revised. The Trade Associations caution that an artificial deadline may increase the risk that some complex technical issues may not be fully resolved in Version 5. The Trade Associations and Exelon support a “realistic goal” or “target date” for filing CIP Version 5 coupled with periodic informational filings marking NERC's progress.<SU>150</SU>
          <FTREF/>AMP supports requiring NERC to make periodic informational filings as well.<SU>151</SU>
          <FTREF/>The Trade Associations state that if the Commission deems a deadline necessary, it should be set for the first quarter of 2013.</P>
        <FTNT>
          <P>
            <SU>149</SU>Trade Associations Comments at 13-14; AMP Comments at 4-5; Exelon Comments at 3-4; FirstEnergy Comments at 3-4; KCP&amp;L Comments at 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>150</SU>Trade Associations Comments at 15.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>151</SU>AMP Comments at 5.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>110. We adopt our NOPR proposal to establish a deadline for compliance with the outstanding Order No. 706 CIP directives. Given the elapse of time since the issuance of Order No. 706, we believe that it is appropriate to set a reasonable deadline for completion of the next version of the CIP Reliability Standards, which, according to NERC, is expected to address the outstanding Order No. 706 directives.<SU>152</SU>
          <FTREF/>The setting of a deadline responds to the finding in the January 2011 Audit Report of the Department of Energy's Inspector General that “the CIP standards implementation approach and schedule approved by the Commission were not adequate to ensure that systems-related risks to the Nation's power grid were mitigated or addressed in a timely manner.”<SU>153</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>152</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 65 n.65.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>153</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at P 65 (<E T="03">citing</E>Department of Energy Inspector General Audit Report,<E T="03">Federal Energy Regulatory Commission's Monitoring if Power Grid Cybersecurity</E>at 2 (January 2011)).</P>
        </FTNT>
        <P>111. We recognize, as numerous commenters discuss, that the current schedule for completing CIP Version 5 is aggressive. We also understand that the volume of industry discussion is high and we agree that industry input should not be artificially rushed or curtailed. In its reply comments, NERC indicated that it anticipates filing the Version 5 CIP Reliability Standards by the third quarter of 2012.<SU>154</SU>
          <FTREF/>Accordingly, to allow for sufficient time beyond what NERC estimates, we establish a deadline that is 6 months from the end of the third quarter of 2012 (i.e., March 31, 2013). NERC must also submit reports at the beginning of each quarter in which the ERO is to explain whether it is on track to meet the deadline and describe the status of its standard development efforts.</P>
        <FTNT>
          <P>
            <SU>154</SU>NERC Reply Comments at 4.</P>
        </FTNT>
        <HD SOURCE="HD2">G. Violation Severity Levels and Violation Risk Factors</HD>
        <HD SOURCE="HD3">NERC Petition</HD>
        <P>112. As amended on April 12, 2011, the petition includes proposed VRFs and VSLs for each Requirement of the Version 4 CIP Reliability Standards, CIP-002-4 to CIP-009-4.</P>
        <HD SOURCE="HD3">NOPR</HD>
        <P>113. In the NOPR, the Commission stated that the VSLs for Requirements R1 and R2 of CIP-002-4 do not adequately address the failure to properly identify either Critical Assets or Critical Cyber Assets.<SU>155</SU>
          <FTREF/>Specifically, NERC proposed to assign a “Severe VSL” for a violation of Requirement R1 if a responsible entity does not develop a list of its identified Critical Assets “even if such list is null.” NERC did not propose to assign a VSL for a violation of Requirement R1 when a responsible entity fails to identify a Critical Asset that falls within any of the Critical Asset criteria in Attachment 1, or fails to include an identified Critical Asset in its Critical Asset list. NERC further proposed to assign a “Severe VSL” to a responsible entity's violation of Requirement R2 only when it fails to include in its list of Critical Cyber Assets a Critical Cyber Asset it has identified. NERC did not propose to assign a VSL for a violation of Requirement R2 resulting from a responsible entity's failure to identify as a Critical Cyber Asset a cyber asset that qualifies as a Critical Cyber Asset. The Commission therefore proposed to direct the ERO to modify the VSLs for CIP-002-4, Requirements R1 and R2, to address a failure to identify either Critical Assets or Critical Cyber Assets.</P>
        <FTNT>
          <P>
            <SU>155</SU>NOPR, FERC Stats. &amp; Regs. ¶ 32,679 at pp. 35-36.</P>
        </FTNT>
        <HD SOURCE="HD3">Comments</HD>

        <P>114. NERC and PG&amp;E agree with the NOPR proposal to direct modifications to the VSLs for Requirements R1 and R2 of CIP-002-4 to ensure that lists of identified Critical Assets are<PRTPAGE P="24608"/>complete.<SU>156</SU>
          <FTREF/>Accordingly, NERC states that the VSLs for Requirements R1 and R2 should be modified to include the word “complete” in front of the list in the VSL language.<SU>157</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>156</SU>NERC Comments at 7-8; PG&amp;E Comments at 6-7.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>157</SU>The VSL for Requirement R1, for example, would read: “The Responsible Entity did not develop a<E T="03">complete</E>list of its identified Critical Assets even if such list is null.” (emphasis added).</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>115. The Commission approves the VRFs and VSLs proposed by NERC subject to the modifications discussed above. As NERC now agrees, the Commission directs modifications to the “Severe VSL” for Requirements R1 and R2 to include the word “complete.” The modified VSLs will address situations where a responsible entity fails to identify or include one or more Critical Assets that fall within the Critical Asset criteria in Attachment 1 in its Critical Assets list pursuant to Requirement R1, or where a Responsible Entity fails to identify or include one or more Critical Cyber Assets in its Critical Cyber Asset list pursuant to Requirement R2.</P>
        <HD SOURCE="HD1">III. Information Collection Statement</HD>
        <P>116. The Office of Management and Budget (OMB) regulations require approval of certain information collection requirements imposed by agency rules.<SU>158</SU>
          <FTREF/>Upon approval of a collection(s) of information, OMB will assign an OMB control number and expiration date. Respondents subject to the filing requirement of this rule will not be penalized for failing to respond to these collections of information unless the collections of information display a valid OMB control number. The Paperwork Reduction Act (PRA)<SU>159</SU>
          <FTREF/>requires each federal agency to seek and obtain OMB approval before undertaking a collection of information directed to ten or more persons, or continuing a collection for which OMB approval and validity of the control number are about to expire.<SU>160</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>158</SU>5 CFR 1320.11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>159</SU>44 U.S.C. 3501-3520 (2006).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>160</SU>44 U.S.C. 3502(3)(A)(i), 44 U.S.C. 3507(a)(3).</P>
        </FTNT>
        <P>117. The Commission is submitting these reporting and recordkeeping requirements to OMB for its review and approval under section 3507(d) of the PRA. The Commission solicited comments on the need for this information, whether the information will have practical utility, the accuracy of provided burden estimates, ways to enhance the quality, utility, and clarity of the information to be collected, and any suggested methods for minimizing the respondent's burden, including the use of automated information techniques. The Commission received two comments regarding burden and cost estimates.</P>
        <HD SOURCE="HD3">Comments</HD>
        <P>118. Hydro-Québec and NV Energy claim that the cost estimates included in the NOPR for Version 4 are inaccurate and incomplete.<SU>161</SU>
          <FTREF/>NV Energy states that the estimate does not include the significant burden of the additional security requirements that will be required by the identification of more Critical Assets and related Critical Cyber Assets. NV Energy comments that the cost estimate does not consider such matters as increased background checking, personnel risk assessments, cyber security training programs, and increased complexity of cyber security perimeters.</P>
        <FTNT>
          <P>
            <SU>161</SU>Hydro-Québec Comments at 6; NV Energy Comments at 6-7.</P>
        </FTNT>
        <HD SOURCE="HD3">Commission Determination</HD>
        <P>119. After a review of the comments on the Commission's cost estimate, we maintain the cost estimate provided in the NOPR. While we recognize that implementing the Reliability Standards is not without cost, the benefits to reliability must be recognized. In response to Hydro-Québec and NV Energy's concerns, we note that the estimate provided in the NOPR addresses the potential for an incremental increase in costs across the industry and does not address the full cost of implementing the CIP Reliability Standards by an entity. We anticipate that the savings associated with the change from the entity-specific risk-based assessment methodology, which had to be reviewed and updated each year, to a bright-line approach will offset some, if not all, of the incremental cost increase for entities that have previously identified a Critical Cyber Asset. With regards to NV Energy's comments, we note that the proposed revisions to the Version 4 CIP Reliability Standards address the manner for the identification of Critical Assets, and do not revise current requirements pertaining to background checking, personnel risk assessments, cyber security training programs, and cyber security perimeters.</P>
        <P>120.<E T="03">Burden Estimate:</E>The principal differences in the existing information collection requirements and the burden imposed by the Reliability Standards in this Final Rule are triggered by the changes in Reliability Standard CIP-002-4. The previous risk-based assessment methodology for identifying Critical Assets is being replaced by 17 uniform “bright line” criteria for identifying Critical Assets (in CIP-002-4, Attachment 1, “Critical Asset Criteria”). Reliability Standard CIP-002-4 requires each responsible entity to use the bright line criteria as a “checklist” to identify Critical Assets, initially and in an annual review, instead of performing the more technical and individualized risk analysis involved in complying with the previously-effective CIP Reliability Standards. As in past versions of these Standards, each Responsible Entity will then identify the Critical Cyber Assets associated with its updated list of Critical Assets. If application of the bright line criteria results in the identification of new Critical Cyber Assets, such assets become subject to the remaining standards (approved CIP-003-4, CIP-004-4, CIP-005-4, CIP-006-4, CIP-007-4, CIP-008-4, and CIP-009-4), and the information collection requirements contained therein.</P>
        <P>121. We estimate that the burden associated with the annual review of the assets (by the estimated 1,501 applicable entities) will be simplified by the “Critical Asset Criteria” in Reliability Standard CIP-002-4. Rather than each entity annually reviewing and updating a risk-based assessment methodology that frequently required technical analysis and judgment decisions, the bright line criteria will provide a straightforward checklist for all entities to use. Thus, we estimate that the revised Reliability Standard will reduce the burden associated with the annual review, as well as provide a consistent and clear set of criteria for all entities to follow.</P>

        <P>122. The estimated changes to burden as contained in the Final Rule in RM11-11 follow.<PRTPAGE P="24609"/>
        </P>
        <GPOTABLE CDEF="s50,r50,r45,r50,r50,17" COLS="6" OPTS="L2(,0,,),tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">FERC-725B<LI>Data Collection</LI>
              <LI>(per Version 4)</LI>
            </CHED>
            <CHED H="1">Number of<LI>Respondents<SU>162</SU>
              </LI>
            </CHED>
            <CHED H="1">Average Number of<LI>Annual</LI>
              <LI>Responses</LI>
              <LI>Per Respondent</LI>
            </CHED>
            <CHED H="1">Average Number of Burden Hours Per<LI>Response<SU>163</SU>
              </LI>
            </CHED>
            <CHED H="1">Effect of Final Rule in RM11-11, on Total<LI>Annual Hours</LI>
            </CHED>
            <CHED H="1">Annual Burden Hrs. upon<LI>Implementation of</LI>
              <LI>RM11-11</LI>
            </CHED>
          </BOXHD>
          <ROW RUL="s">
            <ENT I="25"/>
            <ENT>(1)</ENT>
            <ENT>(2)</ENT>
            <ENT>(3)</ENT>
            <ENT>(1) × (2) × (3)</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">Entities that (previously and now) will identify at least one Critical Cyber Asset [category a]</ENT>
            <ENT>345 [no change]</ENT>
            <ENT>1</ENT>
            <ENT>1,880 [reduction of 40 hours from 1,920 to 1,880 hours] hours</ENT>
            <ENT>reduction of 13,800 hours</ENT>
            <ENT>648,600</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Entities that (previously and now) will not identify any Critical Cyber Assets [category b]</ENT>
            <ENT>1,144 [reduction of 12 entities from 1,156 to 1,144]</ENT>
            <ENT>1</ENT>
            <ENT>120 [no change]</ENT>
            <ENT>reduction of 1,440 hours [for the 12 entities]</ENT>
            <ENT>137,280</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Entities that will newly identify a Critical Asset/Critical Cyber Asset due to the requirements in RM11-11<SU>164</SU>[category c]</ENT>
            <ENT>increase of 12 [formerly 0]</ENT>
            <ENT>1</ENT>
            <ENT>3,840<SU>165</SU>
            </ENT>
            <ENT>increase of 46,080</ENT>
            <ENT>46,080</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Net Total</ENT>
            <ENT>1,501</ENT>
            <ENT/>
            <ENT/>
            <ENT>+30,840</ENT>
            <ENT>831,960</ENT>
          </ROW>
        </GPOTABLE>
        <P>The revisions<FTREF/>to the cost estimates based on requirements of this Final Rule are:</P>
        <P>• Each entity that has identified Critical Cyber Assets has a reduction of 40 hours (345 entities × 40 hrs.  @$96/hour = $1,324,800 reduction).</P>
        <FTNT>
          <P>
            <SU>162</SU>The NERC Compliance Registry as of September 28, 2010 indicated that 2,079 entities were registered for NERC's compliance program. Of these, 2,057 were identified as being U.S. entities. Staff concluded that of the 2,057 U.S. entities, approximately 1,501 were registered for at least one CIP related function. According to an April 7, 2009 memo to industry, NERC noted that only 31 percent of entities responding to an earlier survey reported that they had at least one Critical Asset, and only 23 percent reported having a Critical Cyber Asset. Staff applied the 23 percent (an estimate unchanged for Version 4 standards) to the 1,501 figure to estimate the number of entities that identified Critical Cyber Assets under Version 3 CIP Standards.</P>
          <P>
            <SU>163</SU>Calculations for figures prior to applying reductions:</P>
          <P>Respondent category b:</P>
          <P>3 employees × (working 50 percent) × (40 hrs/week) × (2 weeks) = 120 hours.</P>
          <P>Respondent category c:</P>
          <P>20 employees × (working 50 percent) × (40 hrs/week) × (8 weeks) = 3200 hours  (working 20 percent) × (3200 hrs) = 640 hours.</P>
          <P>Total = 3840.</P>
          <P>Respondent category a:</P>
          <P>50 percent of 3840 hours (category d) = 1920.</P>
          <P>
            <SU>164</SU>We estimate 12 (or 1%) of the existing entities that formerly had no identified Critical Cyber Assets will have them under the Reliability Standards. This Final Rule does not affect the burden for the 6 new U.S. Entities that were estimated to newly register or otherwise become subject to the CIP Standards each year in FERC-725B, and therefore are not included in this chart.</P>
          <P>
            <SU>165</SU>This estimated burden estimate applies only to the first three-year audit cycle. In subsequent audit cycles these entities will move into category a, or be removed from the burden as an entity that no longer is registered for a CIP related function.</P>
        </FTNT>
        <P>• 12 Entities that formerly had not identified Critical Cyber Assets, but now will have them, has</P>
        <P>○ A reduction of 120 hours and an increase of 3,840 hours (for a net increase of 3,720 annual hours), giving 12 entities × 3,720 hrs. @ $96/hour = $4,285,440.</P>
        <P>○ Storage costs = 12 entities @ $15.25/entity = $183.</P>
        <P>Total Net Annual Cost for the FERC-725B requirements contained in the Final Rule in RM11-11= $2,960,823 ($4,285,440 + $183 − $1,324,800).</P>
        <P>The estimated hourly rate of $96 is the average cost of legal services ($230 per hour), technical employees ($40 per hour) and administrative support ($18 per hour), based on hourly rates from the Bureau of Labor Statistics (BLS) and the 2009 Billing Rates and Practices Survey Report.<SU>166</SU>
          <FTREF/>The $15.25 per entity for storage costs is an estimate based on the average costs to service and store 1 GB of data to demonstrate compliance with the CIP Standards.<SU>167</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>166</SU>Bureau of Labor Statistics figures were obtained from<E T="03">http://www.bls.gov/oes/current/naics2_22.htm,</E>and 2009 Billing Rates figure were obtained from<E T="03">http://www.marylandlawyerblog.com/2009/07/average_hourly_rate_for_lawyer.html.</E>Legal services were based on the national average billing rate (contracting out) from the above report and BLS hourly earnings (in-house personnel). It is assumed that 25 percent of respondents have in-house legal personnel.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>167</SU>Based on the aggregate cost of an advanced data protection server.</P>
        </FTNT>
        <P>
          <E T="03">Title:</E>Mandatory Reliability Standards, Version 4 Critical Infrastructure Protection Standards.</P>
        <P>
          <E T="03">Action:</E>Revised Collection FERC-725B.</P>
        <P>
          <E T="03">OMB Control No.:</E>1902-0248.</P>
        <P>
          <E T="03">Respondents:</E>Businesses or other for-profit institutions; not-for-profit institutions.</P>
        <P>
          <E T="03">Frequency of Responses:</E>On Occasion.</P>
        <P>
          <E T="03">Necessity of the Information:</E>This Final Rule approves the requested modifications to Reliability Standards pertaining to critical infrastructure protection. The Reliability Standards help ensure the reliable operation of the Bulk-Power System by providing a cybersecurity framework for the identification and protection of Critical Assets and associated Critical Cyber Assets. As discussed above, the Commission approves NERC's proposed Version 4 CIP Standards pursuant to section 215(d)(2) of the FPA because they represent an improvement to the previously-effective CIP Reliability Standards.</P>
        <P>
          <E T="03">Internal Review:</E>The Commission has reviewed the proposed Reliability Standards and made a determination that its action is necessary to implement section 215 of the FPA.</P>

        <P>123. 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">DataClearance@ferc.gov,</E>phone: (202) 502-8663, fax: (202) 273-0873].</P>
        <P>124. Comments concerning this information collection can 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, phone: (202) 395-4718, fax: (202) 395-7285].</P>
        <HD SOURCE="HD1">IV. Environmental Analysis</HD>

        <P>125. The Commission is required to prepare an Environmental Assessment or an Environmental Impact Statement for any action that may have a<PRTPAGE P="24610"/>significant adverse effect on the human environment.<SU>168</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>169</SU>
          <FTREF/>The actions taken here fall within this categorical exclusion in the Commission's regulations.</P>
        <FTNT>
          <P>
            <SU>168</SU>
            <E T="03">Regulations Implementing the National Environmental Policy Act,</E>52 FR 47897 (Dec. 17, 1987), Order No. 486, FERC Stats. &amp; Regs., Regulations Preambles 1986-1990 ¶ 30,783 (1987).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>169</SU>18 CFR 380.4(a)(2)(ii).</P>
        </FTNT>
        <HD SOURCE="HD1">V. Regulatory Flexibility Act</HD>
        <P>126. The Regulatory Flexibility Act of 1980 (RFA)<SU>170</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>171</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>172</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>170</SU>5 U.S.C. 601-612.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>171</SU>13 CFR 121.101.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>172</SU>13 CFR 121.201, Sector 22, Utilities &amp; n.1.</P>
        </FTNT>
        <P>127. This Final Rule may have a significant economic impact on some small entities. The Commission estimates that 12 of the total small entities applicable to this final rule will experience a total one-time impact of $4,285,623 (an average of $357,135 per entity). However, the Commission has determined that 12 small entities is not a “substantial number” in terms of the total number of regulated small entities under this Final Rule. The Final Rule applies to the all NERC Registered Entities listed in the “Applicability” section of Reliability Standard CIP-002-4.<SU>173</SU>
          <FTREF/>This list includes reliability coordinators, balancing authorities, interchange authorities, transmission service providers, transmission owners, transmission operators, generator owners, generator operators, load serving entities and regional entities. Using the NERC registry, the Commission found that the number of small entities applicable to this rule is 306. The Commission does not consider 12 out of 306 (3.9%) to be a substantial number.</P>
        <FTNT>
          <P>
            <SU>173</SU>
            <E T="03">See</E>Reliability Standard CIP-002-4,<E T="03">http://www.nerc.com/files/CIP-002-4.pdf.</E>
          </P>
        </FTNT>
        <P>128. In the September 15, 2011 NOPR, the Commission requested comment on the potential implementation cost and subsequent cost increases that could be experienced by such small entities. No comments were received.</P>
        <P>129. Based on the foregoing, the Commission certifies that the modified Reliability Standards will not have a significant impact on a substantial number of small entities. Accordingly, no regulatory flexibility analysis is required.</P>
        <HD SOURCE="HD1">VI. Document Availability</HD>

        <P>130. In addition to publishing the full text of this document in the<E T="04">Federal Register</E>, the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the Internet through FERC's Home Page (<E T="03">http://www.ferc.gov</E>) and in FERC's Public Reference Room during normal business hours (8:30 a.m. to 5 p.m. Eastern time) at 888 First Street NE., Room 2A, Washington, DC 20426.</P>
        <P>131. 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>132. 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>133. These regulations are effective June 25, 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>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 18 CFR Part 40</HD>
          <P>Electric power, 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>
        <APPENDIX>
          <HD SOURCE="HED">Appendix</HD>
          <GPOTABLE CDEF="xs100,r100" COLS="2" OPTS="L2,i1">
            <TTITLE>Commenters</TTITLE>
            <BOXHD>
              <CHED H="1">Abbreviation</CHED>
              <CHED H="1">Commenter</CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">AMP</ENT>
              <ENT>American Municipal Power, Inc.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Constellation</ENT>
              <ENT>Constellation Energy Group, Inc. (intervened w/o comment).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dominion</ENT>
              <ENT>Dominion Resources Services, Inc.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Exelon</ENT>
              <ENT>Exelon Corporation.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">FirstEnergy</ENT>
              <ENT>FirstEnergy Service Company.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">G&amp;T Cooperatives</ENT>
              <ENT>Associated Electric Cooperative, Inc.; Basin Electric Power Cooperative; and Tri-State Generation and Transmission Association, Inc.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hydro-Québec</ENT>
              <ENT>Hydro-Québec TransÉnergie.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">ISO/RTO Council</ENT>
              <ENT>The ISO/RTO Council.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">ITC</ENT>
              <ENT>International Transmission Company d/b/a ITC<E T="03">Transmission,</E>Michigan Electric Company, LLC, ITC Midwest LLC and ITC Great Plains LLC.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">KCP&amp;L</ENT>
              <ENT>Kansas City Power &amp; Light Company and KCP&amp;L Greater Missouri Operations Company.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">MISO</ENT>
              <ENT>Midwest Independent Transmission System Operator, Inc.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">NERC</ENT>
              <ENT>North American Electric Reliability Corporation.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">PG&amp;E</ENT>
              <ENT>Pacific Gas and Electric Company.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">NV Energy</ENT>
              <ENT>Sierra Pacific Power Company and Nevada Power Company.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="24611"/>
              <ENT I="01">SPP RE</ENT>
              <ENT>Southwest Power Pool Regional Entity.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tallahassee</ENT>
              <ENT>City of Tallahassee, Florida.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Trade Associations</ENT>
              <ENT>American Public Power Association; Electricity Consumers Resource Council; Edison Electric Institute; Electric Power Supply Association; National Rural Electric Cooperative Association; and Transmission Access Policy Study Group.</ENT>
            </ROW>
          </GPOTABLE>
        </APPENDIX>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9893 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
        <SUBAGY>Internal Revenue Service</SUBAGY>
        <CFR>26 CFR Part 31</CFR>
        <DEPDOC>[TD 9586]</DEPDOC>
        <RIN>RIN 1545-BK83</RIN>
        <SUBJECT>Removal of Regulations Requiring 3% Withholding by Government Entities</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Internal Revenue Service (IRS), Treasury.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final regulations.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This document provides a Treasury decision that removes the final regulations contained in TD 9524 relating to withholding by government entities on payments to persons providing property or services, and makes conforming amendments to regulations to reflect the removal of these regulations. The final regulations are removed because the 3% Withholding Repeal and Job Creation Act repealed the provision of the Internal Revenue Code underlying the final regulations before the provision became effective. The guidance affects government entities that would have been required to withhold and report tax from payments to persons providing property or services and also affects the persons receiving payments for property or services from these government entities.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>These regulations are effective on April 25, 2012.</P>
          <P>
            <E T="03">Applicability Date:</E>For dates of applicability, see §§ 31.6011(a)-4(d) and 31.6302-1(n).</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>A. G. Kelley, (202) 622-6040 (not a toll-free number).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>

        <P>This document contains amendments to 26 CFR part 31 under section 3402(t) of the Internal Revenue Code (Code), relating to three percent withholding by government entities on payments for property or services. Section 3402(t) of the Code was added by section 511 of the Tax Increase Prevention and Reconciliation Act of 2005, Public Law 109-222 (TIPRA), 120 Stat. 345, which was enacted on May 17, 2006. The Treasury Department and the IRS issued final regulations under sections 3402(t), 3406, 6011, 6051, 6071, and 6302 of the Code that were published in the<E T="04">Federal Register</E>on May 9, 2011 (TD 9524, 76 FR 26583, 2011-23 IRB 843) (the May 2011 final regulations). Those regulations were issued to implement the requirements of section 3402(t) and conform existing regulations to section 3402(t).</P>
        <P>Section 102 of the 3% Withholding Repeal and Job Creation Act (Pub. L. 112-56, 125 Stat. 711), which was enacted on November 21, 2011, repealed section 3402(t) of the Code. Section 3402(t) was repealed before it became effective.</P>
        <P>This document, therefore, removes the regulatory provisions issued under section 3402(t) and related sections, and makes conforming amendments to certain regulations to reflect the removal of the section 3402(t) regulations.</P>

        <P>At the same time as the issuance of the May 2011 final regulations, the Treasury Department and the IRS also issued proposed regulations under section 3402(t), published in the<E T="04">Federal Register</E>on May 9, 2011 (REG-151687-10, 76 FR 26678, 2011-23 IRB 867). A related document withdraws those proposed regulations in light of the repeal of section 3402(t). See REG-151687-10.</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 this regulation, and because no notice of proposed rule making is required for this rule, the Regulatory Flexibility Act (5 U.S.C. chapter 6) does not apply.</P>
        <HD SOURCE="HD1">Drafting Information</HD>
        <P>The principal author of these final regulations is A. G. Kelley, Office of the Division Counsel/Associate Chief Counsel (Tax Exempt and Government Entities). 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 31</HD>
          <P>Employment taxes, Fishing vessels, Gambling, Income taxes, Penalties, Pensions, Railroad retirement, Reporting and recordkeeping requirements, Social Security, Unemployment compensation.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Adoption of Amendments to the Regulations</HD>
        <P>Accordingly, 26 CFR part 31 is amended as follows:</P>
        <REGTEXT PART="31" TITLE="26">
          <PART>
            <HD SOURCE="HED">PART 31—EMPLOYMENT TAXES AND COLLECTION OF INCOME TAX AT SOURCE</HD>
          </PART>
          <AMDPAR>
            <E T="04">Paragraph 1.</E>The authority citation for part 31 continues to read in part as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>26 U.S.C. 7805 * * *</P>
          </AUTH>
          <SECTION>
            <SECTNO>§§ 31.3402 and 31.3406</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>
            <E T="04">Par. 2.</E>The following sections and paragraphs are removed:</AMDPAR>
          <AMDPAR>1. Remove section 31.3402(t)-0.</AMDPAR>
          <AMDPAR>2. Remove section 31.3402(t)-1.</AMDPAR>
          <AMDPAR>3. Remove section 31.3402(t)-2.</AMDPAR>
          <AMDPAR>4. Remove section 31.3402(t)-3.</AMDPAR>
          <AMDPAR>5. Remove section 31.3402(t)-4.</AMDPAR>
          <AMDPAR>6. Remove section 31.3402(t)-5.</AMDPAR>
          <AMDPAR>7. Remove section 31.3402(t)-6.</AMDPAR>
          <AMDPAR>8. Remove section 31.3402(t)-7.</AMDPAR>
          <AMDPAR>9. Remove paragraphs (h) and (i) of section 31.3406(g)-2.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="31" TITLE="26">
          <AMDPAR>
            <E T="04">Par. 3.</E>Section 31.6011(a)-4 is amended by:</AMDPAR>
          <AMDPAR>1. Revising paragraphs (b)(4), (b)(5), and (d).</AMDPAR>
          <AMDPAR>2. Removing paragraph (b)(6).</AMDPAR>
          <P>The revisions read as follows:</P>
          <SECTION>
            <SECTNO>§ 31.6011(a)-4</SECTNO>
            <SUBJECT>Returns of income tax withheld.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>

            <P>(4) Pensions, annuities, IRAs, and certain other deferred income subject to withholding under section 3405; and<PRTPAGE P="24612"/>
            </P>
            <P>(5) Reportable payments subject to backup withholding under section 3406.</P>
            <STARS/>
            <P>(d)<E T="03">Effective/applicability dates.</E>Paragraphs (a)(1) and (a)(4)(i) of this section apply to taxable years beginning on or after December 30, 2008. Paragraph (a)(4)(ii) of this section applies to taxable years beginning on or after January 1, 2010. The rules of paragraph (a)(1) of this section that apply to taxable years beginning before December 30, 2008, are contained in § 31.6011(a)-4 as in effect prior to December 30, 2008. The rules of paragraph (a)(4)(ii) of this section that apply to taxable years beginning before January 1, 2010, but on or after December 30, 2008, are contained in § 31.6011(a)-4T as in effect on or after December 30, 2008. The rules of paragraph (a)(4) of this section that apply to taxable years beginning before December 30, 2008, are contained in § 31.6011(a)-4T as in effect prior to December 30, 2008.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="31" TITLE="26">
          <SECTION>
            <SECTNO>§ 31.6051-5</SECTNO>
            <SUBJECT>[Removed]</SUBJECT>
          </SECTION>
          <AMDPAR>
            <E T="04">Par. 4.</E>Section 31.6051-5 is removed.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="31" TITLE="26">
          <AMDPAR>
            <E T="04">Par. 5.</E>Section 31.6071(a)-1 is amended by:</AMDPAR>
          <AMDPAR>1. Revising paragraph (a)(3)(i).</AMDPAR>
          <AMDPAR>2. Removing paragraph (g).</AMDPAR>
          <P>The revision reads as follows:</P>
          <SECTION>
            <SECTNO>§ 31.6071(a)-1</SECTNO>
            <SUBJECT>Time for filing returns and other documents.</SUBJECT>
            <P>(a) * * *</P>
            <P>(3)<E T="03">Information returns-(i) General rule.</E>Each information return in respect of wages as defined in Federal Insurance Contributions Act or of income tax withheld from wages as required under § 31.6051-2 must be filed on or before the last day of February (March 31 if filed electronically) of the year following the calendar year for which it is made, except that, if a tax return under § 31.6011(a)-5(a) is filed as a final return for a period ending prior to December 31, the information return must be filed on or before the last day of the second calendar month following the period for which the tax return is filed.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="31" TITLE="26">
          <AMDPAR>
            <E T="04">Par. 6.</E>Section 31.6302-1 is amended by:</AMDPAR>
          <AMDPAR>1. Revising paragraph (e)(1)(iii)(C).</AMDPAR>
          <AMDPAR>2. Removing paragraph (e)(1)(iii)(E).</AMDPAR>
          <AMDPAR>3. Revising paragraph (n).</AMDPAR>
          <P>The revisions read as follows:</P>
          <SECTION>
            <SECTNO>§ 31.6302-1</SECTNO>
            <SUBJECT>Deposit rules for taxes under the Federal Insurance Contributions Act (FICA) and withheld income taxes.</SUBJECT>
            <STARS/>
            <P>(e) * * *</P>
            <P>(1) * * *</P>
            <P>(iii) * * *</P>
            <P>(C) Certain annuities described in section 3402(o)(1)(B); and</P>
            <STARS/>
            <P>(n)<E T="03">Effective/applicability dates.</E>Sections 31.6302-1 through 31.6302-3 apply with respect to the deposit of employment taxes attributable to payments made after December 31, 1992. To the extent that the provisions of §§ 31.6302-1 through 31.6302-3 are inconsistent with the provisions of §§ 31.6302(c)-1 and 31.6302(c)-2, a taxpayer will be considered to be in compliance with §§ 31.6302-1 through 31.6302-3 if the taxpayer makes timely deposits during 1993 in accordance with §§ 31.6302(c)-1 and 31.6302(c)-2. Paragraphs (b)(4), (c)(5), (c)(6), (d)<E T="03">Example 6,</E>(e)(2), (f)(4)(i), (f)(4)(iii), (f)(5)<E T="03">Example 3,</E>and (g)(1) of this section apply to taxable years beginning on or after December 30, 2008. Paragraph (f)(4)(ii) of this section applies to taxable years beginning on or after January 1, 2010. The rules of paragraphs (e)(2) and (g)(1) of this section that apply to taxable years beginning before December 30, 2008, are contained in § 31.6302-1 as in effect prior to December 30, 2008. The rules of paragraphs (b)(4), (c)(5), (c)(6), (d)<E T="03">Example 6,</E>(f)(4)(i), (f)(4)(iii), and (f)(5)<E T="03">Example 3</E>of this section that apply to taxable years beginning on or after January 1, 2006, and before December 30, 2008, are contained in § 31.6302-1T as in effect prior to December 30, 2008. The rules of paragraphs (b)(4) and (f)(4) of this section that apply to taxable years beginning before January 1, 2006, are contained in § 31.6302-1 as in effect prior to January 1, 2006. The rules of paragraph (g) of this section eliminating use of Federal tax deposit coupons apply to deposits and payments made after December 31, 2010.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="31" TITLE="26">
          <AMDPAR>
            <E T="04">Par. 7.</E>Section 31.6302-4 is amended by:</AMDPAR>
          <AMDPAR>1. Revising paragraphs (b)(4) and (b)(5).</AMDPAR>
          <AMDPAR>2. Removing paragraph (b)(6).</AMDPAR>
          <AMDPAR>3. Revising paragraph (e).</AMDPAR>
          <P>The revisions read as follows:</P>
          <SECTION>
            <SECTNO>§ 31.6302-4</SECTNO>
            <SUBJECT>Deposit rules for withheld income taxes attributable to nonpayroll payments.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>
            <P>(4) Annuities withheld under section 3405, relating to withholding on pensions, annuities, IRAs, and certain other deferred income; and</P>
            <P>(5) Amounts withheld under section 3406, relating to backup withholding with respect to reportable payments.</P>
            <STARS/>
            <P>(e)<E T="03">Effective/applicability date.</E>Section 31.6302-4(d) applies to deposits and payments made after December 31, 2010.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <NAME>Steven T. Miller,</NAME>
          <TITLE>Deputy Commissioner for Services and Enforcement.</TITLE>
          <DATED>Approved: April 17, 2012.</DATED>
          <NAME>Emily S. McMahon,</NAME>
          <TITLE>Acting Assistant Secretary of the Treasury (Tax Policy).</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9887 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4830-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Department of the Navy</SUBAGY>
        <CFR>32 CFR Part 706</CFR>
        <SUBJECT>Certifications and Exemptions Under the International Regulations for Preventing Collisions at Sea, 1972</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of the Navy, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Department of the Navy (DoN) is amending its certifications and exemptions under the International Regulations for Preventing Collisions at Sea, 1972 (72 COLREGS), to reflect that the Deputy Assistant Judge Advocate General (DAJAG) (Admiralty and Maritime Law) has determined that USS ASHLAND (LSD 48) is a vessel of the Navy which, due to its special construction and purpose, cannot fully comply with certain provisions of the 72 COLREGS without interfering with its special function as a naval ship. The intended effect of this rule is to warn mariners in waters where 72 COLREGS apply.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective April 25, 2012 and is applicable beginning April 16, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Lieutenant Jaewon Choi, JAGC, U.S. Navy, Admiralty Attorney, (Admiralty and Maritime Law), Office of the Judge Advocate General, Department of the Navy, 1322 Patterson Ave. SE., Suite 3000, Washington Navy Yard, DC 20374-5066, telephone 202-685-5040.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Pursuant to the authority granted in 33 U.S.C. 1605, the DoN amends 32 CFR part 706.</P>

        <P>This amendment provides notice that the DAJAG (Admiralty and Maritime Law), under authority delegated by the Secretary of the Navy, has certified that USS ASHLAND (LSD 48) is a vessel of the Navy which, due to its special construction and purpose, cannot fully comply with the following specific provisions of 72 COLREGS without<PRTPAGE P="24613"/>interfering with its special function as a naval ship: Annex I, paragraph 3(a), pertaining to the horizontal distance between the forward and after masthead lights; and Annex I, paragraph 2(k) as described in Rule 30 (a)(i), pertaining to the vertical separation between anchor lights. The DAJAG (Admiralty and Maritime Law) has also certified that the lights involved are located in closest possible compliance with the applicable 72 COLREGS requirements.</P>
        <P>Moreover, it has been determined, in accordance with 32 CFR parts 296 and 701, that publication of this amendment for public comment prior to adoption is impracticable, unnecessary, and contrary to public interest since it is based on technical findings that the placement of lights on this vessel in a manner differently from that prescribed herein will adversely affect the vessel's ability to perform its military functions.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 706</HD>
          <P>Marine safety, Navigation (water), and Vessels.</P>
        </LSTSUB>
        
        <P>For the reasons set forth in the preamble, amend part 706 of title 32 of the CFR as follows:</P>
        <REGTEXT PART="706" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 706—CERTIFICATIONS AND EXEMPTIONS UNDER THE INTERNATIONAL REGULATIONS FOR PREVENTING COLLISIONS AT SEA, 1972</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 706 continues to read:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1605.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="706" TITLE="32">
          <AMDPAR>2. Section 706.2 is amended as follows:</AMDPAR>
          <AMDPAR>A. In Table Three by adding, in alpha numerical order, by vessel number, an entry for USS ASHLAND (LSD 48); and</AMDPAR>
          <AMDPAR>B. In Table Five by revising the entry for USS ASHLAND (LSD 48).</AMDPAR>
          <SECTION>
            <SECTNO>§ 706.2</SECTNO>
            <SUBJECT>Certifications of the Secretary of the Navy under Executive Order 11964 and 33 U.S.C. 1605.</SUBJECT>
            <STARS/>
            <GPOTABLE CDEF="s50,r30,r50,r50,r50,r50,r50,r50,xls40" COLS="9" OPTS="L1,p7,7/8,i1">
              <TTITLE>Table Three</TTITLE>
              <BOXHD>
                <CHED H="1">Vessel</CHED>
                <CHED H="1">Number</CHED>
                <CHED H="1">Masthead lights arc of visibility; rule 21(a)</CHED>
                <CHED H="1">Side lights arc of visibility; rule 21(b)</CHED>
                <CHED H="1">Stern light arc of visibility; rule 21(c)</CHED>
                <CHED H="1">Side lights distance inboard of ship's sides in meters 3(b) Annex 1</CHED>
                <CHED H="1">Stern light, distance forward of stern in meters; Rule 21(c)</CHED>
                <CHED H="1">Forward anchor light, height above hull in meters; 2(k) Annex 1</CHED>
                <CHED H="1">Anchor lights relation-ship of aft light to forward light in meters 2(k) Annex 1</CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW>
                <ENT I="01">USS ASHLAND</ENT>
                <ENT>LSD 48</ENT>
                <ENT/>
                <ENT/>
                <ENT/>
                <ENT/>
                <ENT/>
                <ENT/>
                <ENT>2.60 below.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
            </GPOTABLE>
            <STARS/>
            <GPOTABLE CDEF="s50,r30,r50,r50,24C,12" COLS="6" OPTS="L1,i1">
              <TTITLE>Table Five</TTITLE>
              <BOXHD>
                <CHED H="1">Vessel</CHED>
                <CHED H="1">Number</CHED>
                <CHED H="1">Masthead lights not over all other lights and obstructions. Annex I,sec. 2(f)</CHED>
                <CHED H="1">Forward masthead light not in forward quarter of ship. Annex I, sec. 3(a)</CHED>
                <CHED H="1">After mast-<LI>head light</LI>
                  <LI>less than</LI>
                  <LI>1/2 ship's</LI>
                  <LI>length aft</LI>
                  <LI>of forward</LI>
                  <LI>masthead</LI>
                  <LI>light. Annex</LI>
                  <LI>I, sec. 3(a)</LI>
                </CHED>
                <CHED H="1">Percentage<LI>horizontal</LI>
                  <LI>separation</LI>
                  <LI>attained</LI>
                </CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW>
                <ENT I="01">USS ASHLAND</ENT>
                <ENT>LSD 48</ENT>
                <ENT/>
                <ENT/>
                <ENT>X</ENT>
                <ENT>63.6</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Approved: April 16, 2012.</DATED>
          <NAME>C.J. Spain,</NAME>
          <TITLE>Deputy Assistant Judge Advocate, General (Admiralty and Maritime Law), Acting.</TITLE>
          <DATED>Dated: April 18, 2012.</DATED>
          <NAME>J.M. Beal,</NAME>
          <TITLE>Lieutenant Commander, Judge Advocate General's Corps, U.S. Navy, Federal Register Liaison Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9928 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3810-FF-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Parts 9 and 721</CFR>
        <DEPDOC>[EPA-HQ-OPPT-2012-0182; FRL-9345-4]</DEPDOC>
        <RIN>RIN 2070-AB27</RIN>
        <SUBJECT>Significant New Use Rules on Certain Chemical Substances</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>EPA is promulgating significant new use rules (SNURs) under the Toxic Substances Control Act (TSCA) for 23 chemical substances which were the subject of premanufacture notices (PMNs). Nine of these chemical substances are subject to TSCA consent orders issued by EPA. This action requires persons who intend to manufacture, import, or process any of these 23 chemical substances for an activity that is designated as a significant new use by this rule to notify EPA at least 90 days before commencing that activity. The required notification<PRTPAGE P="24614"/>will provide EPA with the opportunity to evaluate the intended use and, if necessary, to prohibit or limit that activity before it occurs.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective on June 25, 2012. For purposes of judicial review, this rule shall be promulgated at 1 p.m. (e.s.t.) on May 9, 2012.</P>

          <P>Written adverse or critical comments, or notice of intent to submit adverse or critical comments, on one or more of these SNURs must be received on or before May 25, 2012 (see Unit VI. of the<E T="02">SUPPLEMENTARY INFORMATION</E>).</P>

          <P>For additional information on related reporting requirement dates, see Units I.A., VI., and VII. of the<E T="02">SUPPLEMENTARY INFORMATION</E>.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit your comments, identified by docket identification (ID) number EPA-HQ-OPPT-2012-0182, 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-0182. 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-0182. 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>For technical information contact: Kenneth Moss, 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-9232; email address:<E T="03">moss.kenneth@epa.gov.</E>
          </P>
          <P>
            <E T="03">For general information contact:</E>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. General Information</HD>
        <HD SOURCE="HD2">A. Does this action apply to me?</HD>
        <P>You may be potentially affected by this action if you manufacture, import, process, or use the chemical substances contained in this rule. Potentially affected entities may include, but are not limited to:</P>
        <P>• Manufacturers, importers, or processors of one or more subject chemical substances (NAICS codes 325 and 324110), e.g., chemical manufacturing and petroleum refineries.</P>

        <P>This listing is not intended to be exhaustive, but rather provides a guide for readers regarding entities likely to be affected by this action. Other types of entities not listed in this unit could also be affected. The North American Industrial Classification System (NAICS) codes have been provided to assist you and others in determining whether this action might apply to certain entities. To determine whether you or your business may be affected by this action, you should carefully examine the applicability provisions in § 721.5. If you have any questions regarding the applicability of this action to a particular entity, consult the technical person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <P>This action may also affect certain entities through pre-existing import certification and export notification rules under TSCA. Chemical importers are subject to the TSCA section 13 (15 U.S.C. 2612) import certification requirements promulgated at 19 CFR 12.118 through 12.127 and 19 CFR 127.28. Chemical importers must certify that the shipment of the chemical substance complies with all applicable rules and orders under TSCA. Importers of chemicals subject to these SNURs must certify their compliance with the SNUR requirements. The EPA policy in support of import certification appears at 40 CFR part 707, subpart B. In addition, any persons who export or intend to export a chemical substance that is the subject of this rule are subject to the export notification provisions of TSCA section 12(b) (15 U.S.C. 2611(b)) (see § 721.20), and must comply with the export notification requirements in 40 CFR part 707, subpart D.</P>
        <HD SOURCE="HD2">B. What should I consider as I prepare my comments for EPA?</HD>
        <P>1.<E T="03">Submitting CBI.</E>Do not submit this information to EPA through regulations.gov or email. Clearly mark the part or all of the information that you claim to be CBI. For CBI information in a disk or CD-ROM that you mail to EPA, mark the outside of the disk or CD-ROM as CBI and then identify electronically within the disk or CD-ROM the specific information that is claimed as CBI. In addition to one complete version of the comment that includes information claimed as CBI, a<PRTPAGE P="24615"/>copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the public docket. Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.</P>
        <P>2.<E T="03">Tips for preparing your comments.</E>When submitting comments, remember to:</P>

        <P>i. Identify the document by docket ID number and other identifying information (subject heading,<E T="04">Federal Register</E>date and page number).</P>
        <P>ii. Follow directions. The Agency may ask you to respond to specific questions or organize comments by referencing a Code of Federal Regulations (CFR) part or section number.</P>
        <P>iii. Explain why you agree or disagree; suggest alternatives and substitute language for your requested changes.</P>
        <P>iv. Describe any assumptions and provide any technical information and/or data that you used.</P>
        <P>v. If you estimate potential costs or burdens, explain how you arrived at your estimate in sufficient detail to allow for it to be reproduced.</P>
        <P>vi. Provide specific examples to illustrate your concerns and suggest alternatives.</P>
        <P>vii. Explain your views as clearly as possible, avoiding the use of profanity or personal threats.</P>
        <P>viii. Make sure to submit your comments by the comment period deadline identified.</P>
        <HD SOURCE="HD1">II. Background</HD>
        <HD SOURCE="HD2">A. What action is the agency taking?</HD>

        <P>EPA is promulgating these SNURs using direct final procedures. These SNURs will require persons to notify EPA at least 90 days before commencing the manufacture, import, or processing of a chemical substance for any activity designated by these SNURs as a significant new use. Receipt of such notices allows EPA to assess risks that may be presented by the intended uses and, if appropriate, to regulate the proposed use before it occurs. Additional rationale and background to these rules are more fully set out in the preamble to EPA's first direct final SNUR published in the<E T="04">Federal Register</E>issue of April 24, 1990 (55 FR 17376) (April 24, 1990 SNUR). Consult that preamble for further information on the objectives, rationale, and procedures for SNURs and on the basis for significant new use designations, including provisions for developing test data.</P>
        <HD SOURCE="HD2">B. What is the agency's authority for taking this action?</HD>
        <P>Section 5(a)(2) of TSCA (15 U.S.C. 2604(a)(2)) authorizes EPA to determine that a use of a chemical substance is a “significant new use.” EPA must make this determination by rule after considering all relevant factors, including the four bulleted TSCA section 5(a)(2) factors listed in Unit III. Once EPA determines that a use of a chemical substance is a significant new use, TSCA section 5(a)(1)(B) requires persons to submit a significant new use notice (SNUN) to EPA at least 90 days before they manufacture, import, or process the chemical substance for that use. Persons who must report are described in § 721.5.</P>
        <HD SOURCE="HD2">C. Applicability of General Provisions</HD>

        <P>General provisions for SNURs appear in 40 CFR part 721, subpart A. These provisions describe persons subject to the rule, recordkeeping requirements, exemptions to reporting requirements, and applicability of the rule to uses occurring before the effective date of the rule. Provisions relating to user fees appear at 40 CFR part 700. According to § 721.1(c), persons subject to these SNURs must comply with the same notice requirements and EPA regulatory procedures as submitters of PMNs under TSCA section 5(a)(1)(A). In particular, these requirements include the information submission requirements of TSCA section 5(b) and 5(d)(1), the exemptions authorized by TSCA sections 5(h)(1), 5(h)(2), 5(h)(3), and 5(h)(5), and the regulations at 40 CFR part 720. Once EPA receives a SNUN, EPA may take regulatory action under TSCA section 5(e), 5(f), 6, or 7 to control the activities for which it has received the SNUN. If EPA does not take action, EPA is required under TSCA section 5(g) to explain in the<E T="04">Federal Register</E>its reasons for not taking action.</P>
        <HD SOURCE="HD1">III. Significant New Use Determination</HD>
        <P>Section 5(a)(2) of TSCA states that EPA's determination that a use of a chemical substance is a significant new use must be made after consideration of all relevant factors, including:</P>
        <P>• The projected volume of manufacturing and processing of a chemical substance.</P>
        <P>• The extent to which a use changes the type or form of exposure of human beings or the environment to a chemical substance.</P>
        <P>• The extent to which a use increases the magnitude and duration of exposure of human beings or the environment to a chemical substance.</P>
        <P>• The reasonably anticipated manner and methods of manufacturing, processing, distribution in commerce, and disposal of a chemical substance.</P>
        <P>In addition to these factors enumerated in TSCA section 5(a)(2), the statute authorized EPA to consider any other relevant factors.</P>
        <P>To determine what would constitute a significant new use for the 23 chemical substances that are the subject of these SNURs, EPA considered relevant information about the toxicity of the chemical substances, likely human exposures and environmental releases associated with possible uses, and the four bulleted TSCA section 5(a)(2) factors listed in this unit.</P>
        <HD SOURCE="HD1">IV. Substances Subject to This Rule</HD>
        <P>EPA is establishing significant new use and recordkeeping requirements for 23 chemical substances in 40 CFR part 721, subpart E. In this unit, EPA provides the following information for each chemical substance:</P>
        <P>• PMN number.</P>
        <P>• Chemical name (generic name, if the specific name is claimed as CBI).</P>
        <P>• Chemical Abstracts Service (CAS) number (if assigned for non-confidential chemical identities).</P>
        <P>• Basis for the TSCA section 5(e) consent order or, for non-section 5(e) SNURs, the basis for the SNUR (i.e., SNURs without TSCA section 5(e) consent orders).</P>
        <P>• Tests recommended by EPA to provide sufficient information to evaluate the chemical substance (see Unit VIII. for more information).</P>
        <P>• CFR citation assigned in the regulatory text section of this rule.</P>
        <P>The regulatory text section of this rule specifies the activities designated as significant new uses. Certain new uses, including production volume limits (i.e., limits on manufacture and importation volume) and other uses designated in this rule, may be claimed as CBI. Unit IX. discusses a procedure companies may use to ascertain whether a proposed use constitutes a significant new use.</P>

        <P>This rule includes nine PMN substances (P-07-537, P-07-706, P-10-135, P-10-358, P-11-264, P-11-561, P-11-567, P-11-568, and P-11-569) that are subject to “risk-based” consent orders under TSCA section 5(e)(1)(A)(ii)(I) where EPA determined that activities associated with the PMN substances may present unreasonable risk to human health or the environment. Those consent orders require protective measures to limit exposures or otherwise mitigate the potential unreasonable risk. The so-called “5(e) SNURs” on these PMN substances are promulgated pursuant to § 721.160, and are based on and consistent with the provisions in the underlying consent orders. The 5(e) SNURs designate as a “significant new use” the absence of the protective<PRTPAGE P="24616"/>measures required in the corresponding consent orders.</P>
        <P>Where EPA determined that the PMN substance may present an unreasonable risk of injury to human health via inhalation exposure, the underlying TSCA section 5(e) consent order usually requires, among other things, that potentially exposed employees wear specified respirators unless actual measurements of the workplace air show that air-borne concentrations of the PMN substance are below a New Chemical Exposure Limit (NCEL) that is established by EPA to provide adequate protection to human health. In addition to the actual NCEL concentration, the comprehensive NCELs provisions in TSCA section 5(e) consent orders, which are modeled after Occupational Safety and Health Administration (OSHA) Permissible Exposure Limits (PELs) provisions, include requirements addressing performance criteria for sampling and analytical methods, periodic monitoring, respiratory protection, and recordkeeping. However, no comparable NCEL provisions currently exist in 40 CFR part 721, subpart B, for SNURs. Therefore, for these cases, the individual SNURs in 40 CFR part 721, subpart E, will state that persons subject to the SNUR who wish to pursue NCELs as an alternative to the § 721.63 respirator requirements may request to do so under § 721.30. EPA expects that persons whose § 721.30 requests to use the NCELs approach for SNURs are approved by EPA will be required to comply with NCELs provisions that are comparable to those contained in the corresponding TSCA section 5(e) consent order for the same chemical substance.</P>
        <P>This rule also includes SNURs on 14 PMN substances (P-05-714, P-11-128, P-11-338, P-11-481, P-11-594, P-11-654, P-12-22, P-12-23, P-12-24, P-12-25, P-12-26, P-12-33, P-12-51, and P-12-52) that are not subject to consent orders under TSCA section 5(e). In these cases, for a variety of reasons, EPA did not find that the use scenario described in the PMN triggered the determinations set forth under TSCA section 5(e). However, EPA does believe that certain changes from the use scenario described in the PMN could result in increased exposures or releases, thereby constituting a “significant new use.” These so-called “non-5(e) SNURs” are promulgated pursuant to § 721.170. EPA has determined that every activity designated as a “significant new use” in all non-5(e) SNURs issued under § 721.170 satisfies the two requirements stipulated in § 721.170(c)(2), i.e., these significant new use activities, “(i) are different from those described in the premanufacture notice for the substance, including any amendments, deletions, and additions of activities to the premanufacture notice, and (ii) may be accompanied by changes in exposure or release levels that are significant in relation to the health or environmental concerns identified” for the PMN substance.</P>
        <HD SOURCE="HD1">PMN Number P-05-714</HD>
        <P>
          <E T="03">Chemical name:</E>Polyether ester acid compound with a polyamine amide (generic).</P>
        <P>
          <E T="03">CAS number:</E>Not available.</P>
        <P>
          <E T="03">Basis for action:</E>The PMN states that the substance will be used as an additive for industrial paints, industrial coatings, and architectural coatings. Based on test data on the PMN substance, EPA predicts toxicity to aquatic organisms may occur if releases of the PMN substance to surface water, from uses other than described in the PMN, exceed the releases expected from the use described in the PMN. For the use described in the PMN, significant environmental releases are not expected. Therefore, EPA has not determined that the proposed manufacturing, processing, or use of the substance may present an unreasonable risk. EPA has determined, however, that any use of the substance other than as described in the PMN may cause significant adverse environmental effects. Based on this information, the PMN substance meets the concern criteria at § 721.170(b)(4)(i).</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of a fish acute toxicity mitigated by humic acid test (Office of Pollution Prevention, Pesticides and Toxic Substances (OPPTS) Test Guideline 850.1085) would help characterize the environmental effects of the PMN substance.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10410.</P>
        <HD SOURCE="HD1">PMN Number P-07-537</HD>
        <P>
          <E T="03">Chemical name:</E>Alkanenitrile, bis(cyanoalkyl)amino (generic).</P>
        <P>
          <E T="03">CAS number:</E>Not available.</P>
        <P>
          <E T="03">Effective date of TSCA section 5(e) consent order:</E>June 19, 2009.</P>
        <P>
          <E T="03">Basis for TSCA section 5(e) consent order:</E>The PMN states that the generic (non-confidential) use of the PMN substance will be as a chemical intermediate. Based on test data on the PMN substance, EPA identified concerns for neurotoxicity to workers from dermal and inhalation exposures. The NCEL is 70 microgram/cubic meter (μg/m<SU>3</SU>) as an 8-hour time-weighted average. In addition, based on ecological structure-activity relationship (EcoSAR) analysis of test data on structurally similar aliphatic amines, EPA predicts toxicity to aquatic organisms may occur at concentrations that exceed 700 parts per billion (ppb). The consent order was issued under TSCA sections 5(e)(1)(A)(i) and 5(e)(1)(A)(ii)(I) based on a finding that this substance may present an unreasonable risk of injury to human health and the environment. To protect against these risks, the consent order requires:</P>
        <P>1. Use of personal protective equipment including impervious gloves (when there is potential dermal exposure) and either a National Institute for Occupational Safety and Health (NIOSH)-certified respirator with an assigned protection factor (APF) of at least 5, or compliance with a NCEL of 70 μg/m<SU>3</SU>as an 8-hour time-weighted average (when there is potential inhalation exposure).</P>
        <P>2. Establishment and use of a hazard communication program.</P>
        <P>3. Manufacture and use of the PMN substance only as a site-limited intermediate.</P>
        <P>4. Submission of certain human health testing prior to exceeding the confidential production volume limit specified in the consent order.</P>
        <P>5. Disposal of the PMN substance only by incineration or landfill.</P>
        <P>6. No release of the PMN substance into the waters of the United States.</P>
        
        <FP>The SNUR designates as a “significant new use” the absence of these protective measures.</FP>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of a neurotoxicity study in rodents (Organisation for Economic Co-operation and Development (OECD) Test Guideline 424); a fish early-life stage toxicity test (OPPTS Test Guideline 850.1085); and a daphnid chronic toxicity test (OPPTS Test Guideline 850.1300) would help characterize the human health and environmental effects of the PMN substance. The PMN submitter has agreed not to exceed the confidential production volume limit specified in the consent order without performing the neurotoxicity test. The consent order does not require the submission of the fish and daphnid testing at any specified time or production volume. However, the order's restrictions on manufacture, import, processing, distribution in commerce, use, and disposal of the PMN will remain in effect until the consent order is modified or revoked by EPA based on submission of that or other relevant information.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10411.<PRTPAGE P="24617"/>
        </P>
        <HD SOURCE="HD1">PMN Number P-07-706</HD>
        <P>
          <E T="03">Chemical name:</E>Phosphonic acid ester (generic).</P>
        <P>
          <E T="03">CAS number:</E>Not available.</P>
        <P>
          <E T="03">Effective date of TSCA section 5(e) consent order:</E>April 8, 2009.</P>
        <P>
          <E T="03">Basis for TSCA section 5(e) consent order:</E>The PMN states that the generic (non-confidential) use of the substance will be as a chemical intermediate. Based on test data on the PMN substance and an analogous chemical, EPA identified concerns for oncogenicity, mutagenicity, reproductive/developmental toxicity, skin irritation, and sensitization to workers from dermal and inhalation exposures. The NCEL is 1.0 milligram (mg)/m<SU>3</SU>as an 8-hour time-weighted average. The consent order was issued under TSCA sections 5(e)(1)(A)(i) and 5(e)(1)(A)(ii)(I) based on a finding that this substance may present an unreasonable risk of injury to human health. To protect against this risk, the consent order requires:</P>
        <P>1. Use of personal protective equipment including dermal protection (when there is potential dermal exposure) and a NIOSH-certified respirator with an assigned protection factor (APF) of at least 15, or compliance with a NCEL of 1.0 mg/m<SU>3</SU>as an 8-hour time-weighted average (when there is potential inhalation exposure).</P>
        <P>2. Establishment and use of a hazard communication program.</P>
        <P>3. Submission of certain human health testing prior to exceeding the confidential production volume limit specified in the consent order.</P>
        
        <FP>The SNUR designates as a “significant new use” the absence of these protective measures.</FP>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of a combined repeated dose toxicity with the reproduction/developmental toxicity screening test (OECD Test Guideline 422) and a mammalian erythrocyte micronucleus test (OECD Test Guideline 474) would help characterize possible human health risks of the PMN substance. The PMN submitter has agreed not to exceed the confidential production volume limit specified in the consent order without performing these tests. The consent order does not require the submission of a genetic toxicology: rodent dominant lethal assay test (OECD Test Guideline 478) at any specified time or production volume. However, the consent order's restrictions on manufacture, import, processing, distribution in commerce, use, and disposal of the PMN will remain in effect until the consent order is modified or revoked by EPA based on submission of that or other relevant information.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10412.</P>
        <HD SOURCE="HD1">PMN Number P-10-135</HD>
        <P>
          <E T="03">Chemical name:</E>Fluorinated dialkyl ketone (generic).</P>
        <P>
          <E T="03">CAS number:</E>Not available.</P>
        <P>
          <E T="03">Effective date of TSCA section 5(e) consent order:</E>October 21, 2011.</P>
        <P>
          <E T="03">Basis for TSCA section 5(e) consent order:</E>The PMN states that the generic (non-confidential) use of the substance will be as a heat transfer fluid. Based on test data on the PMN substance and analogs, EPA identified concerns for oncogenicity and liver effects from dermal and inhalation exposures. The consent order was issued under TSCA sections 5(e)(1)(A)(i) and 5(e)(1)(A)(ii)(I) based on a finding that this substance may present an unreasonable risk of injury to human health. To protect against this risk, the consent order prohibits exceedance of the confidential annual production volume limit specified in the consent order. The SNUR designates as a “significant new use” the absence of this protective measure.</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that a 90-day inhalation toxicity test (OPPTS Test Guideline 870.3465) and a reproduction/developmental toxicity screening test (OECD Test Guideline 421, with modifications) would help characterize the human health effects of the PMN substance. The consent order does not require the submission of this testing at any specified time or production volume. However, the consent order's restrictions on manufacture, import, processing, distribution in commerce, use, and disposal of the PMN will remain in effect until the consent order is modified or revoked by EPA based on submission of that or other relevant information.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10413.</P>
        <HD SOURCE="HD1">PMN Number P-10-358</HD>
        <P>
          <E T="03">Chemical name:</E>Iron(1+), chloro[rel-1,5-dimethyl (1R,2S,4R,5S)- 9,9-dihydroxy-3-methyl-2,4-di(2-pyridinyl-.kappa.N)-7-[(2-pyridinyl-.kappa.N)methyl]-3,7-diazabicyclo[3.3.1]nonane-1,5-dicarboxylate-.kappa.N3,.kappa.N7]-, chloride (1:1), (OC-6-63)-.</P>
        <P>
          <E T="03">CAS number:</E>478945-46-9.</P>
        <P>
          <E T="03">Effective date of TSCA section 5(e) consent order:</E>February 7, 2011.</P>
        <P>
          <E T="03">Basis for TSCA section 5(e) consent order:</E>The PMN states that the generic (non-confidential) use of the substance will be as a coatings additive at concentrations not to exceed 1.0 percent. Based on test data on the PMN substance, EPA identified concerns for systemic toxicity, neurotoxicity, dermal sensitization, acute toxicity and immunotoxicity from dermal exposure. The consent order was issued under TSCA sections 5(e)(1)(A)(i) and 5(e)(1)(A)(ii)(I) based on a finding that this substance may present an unreasonable risk of injury to human health. To protect against these risks, the consent order requires:</P>
        <P>1. Use of personal protective equipment including dermal protection (when there is potential dermal exposure).</P>
        <P>2. Establishment and use of a hazard communication program.</P>
        <P>3. Use of the PMN substance only as described in the PMN.</P>
        <P>4. That annual manufacture and importation volume not exceed the confidential limit specified in the consent order.</P>
        <P>5. No manufacture, processing, or use of the PMN substance in the form of a powder or a solid.</P>
        
        <FP>The SNUR designates as a “significant new use” the absence of these protective measures.</FP>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of an acute oral toxicity test (OPPTS Test Guideline 870.1100) in rabbits would help characterize the human health effects of the substance. The consent order does not require submission of the testing at any specified time or production volume. However, the consent order's restrictions on manufacture, import, processing, distribution in commerce, use, and disposal of the PMNs will remain in effect until the consent order is modified or revoked by EPA based on submission of that or other relevant information.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10414.</P>
        <HD SOURCE="HD1">PMN Number P-11-128</HD>
        <P>
          <E T="03">Chemical name:</E>3H-indolium, 2-[2-[3-[2-(1,3-dihydro-1,3,3-trimethyl-2H-indol-2-ylidene)ethylidene]-2-[(1-phenyl-1H-tetrazol-5-yl)thio]-1-cyclohexen-1-yl]ethenyl]-1,3, 3-trimethyl-, chloride (1:1).</P>
        <P>
          <E T="03">CAS number:</E>440102-72-7.</P>
        <P>
          <E T="03">Basis for action:</E>The PMN states that the substance will be used as a dye used in the manufacture of imaging media/products. Based on EcoSAR analysis of test data on cationic dyes, EPA predicts toxicity to aquatic organisms may occur as a result of releases of the PMN substance to surface water from manufacture or import in quantities greater than the 10,000 kilograms (kg) per year production volume stated in the PMN. At the annual production volume of 10,000 kg stated in the PMN,<PRTPAGE P="24618"/>there were no significant environmental concerns. Therefore, EPA has not determined that the proposed manufacturing, processing, or use of the substance may present an unreasonable risk. EPA has determined, however, that exceeding an annual manufacturing and importation volume of 10,000 kg may cause significant adverse environmental effects. Based on this information, the PMN substance meets the concern criteria at § 721.170(b)(4)(ii).</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of a fish early-life stage toxicity test (OPPTS Test Guideline 850.1400); a daphnid chronic toxicity test (OPPTS Test Guideline 850.1300); and an algal toxicity test, tiers I and II (OPPTS Test Guideline 850.5400) would help characterize the environmental effects of the PMN substance.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10415.</P>
        <HD SOURCE="HD1">PMN Number P-11-264</HD>
        <P>
          <E T="03">Chemical name:</E>Brominated polyphenyl ether (generic).</P>
        <P>
          <E T="03">CAS number:</E>Not available.</P>
        <P>
          <E T="03">Effective date of TSCA section 5(e) consent order:</E>November 22, 2011.</P>
        <P>
          <E T="03">Basis for TSCA section 5(e) consent order:</E>The PMN states that the generic (non-confidential) use of the PMN substance will be as a flame retardant. EPA expects that brominated dibenzodioxins (BDD) and dibenzofurans (BDF) may be generated during manufacture of the PMN substance and may be potential decomposition products of the PMN substance in the environment. Human health concerns from exposure to BDD and BDF include cancer, reproductive and developmental toxicity, and immunotoxicity. EPA expects the PMN to be highly persistent in the environment and that it may be bioavailable based on data on related substances. EPA also has environmental concerns based on the high degree of bromination of the PMN substance and the potential presence of BDD/BDF impurities that may form during manufacturing and may be decomposition products in the environment. Current knowledge of the ecotoxicity of BDD and BDF indicate adverse effects may occur in the parts per trillion range in rainbow trout embryos and juveniles. The consent order was issued under TSCA sections 5(e)(1)(A)(i), 5(e)(1)(A)(ii)(I), and 5(e)(1)(A)(ii)(II), based on a finding that this substance and potential impurities and degradants may present an unreasonable risk of injury to human health and the environment, the substance may be produced in substantial quantities and may reasonably be anticipated to enter the environment in substantial quantities, and there may be significant (or substantial) human exposure to the substance. To protect against these risks the consent order requires:</P>
        <P>1. No exceedance of the maximum levels of BDD and BDF in the PMN substance as specified in the consent order.</P>
        <P>2. Manufacture of the PMN substance only at the site specified in the PMN and only using the process described in the PMN unless the dioxin/furan testing required in the consent order is conducted and the test results submitted to EPA within 16 months of commencement of manufacture at the additional site or process.</P>
        <P>3. The molecular weight of the manufactured PMN substance be equal to or greater than the weight reported in the PMN.</P>
        
        <FP>The SNUR designates as a “significant new use” the absence of these protective measures.</FP>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of the following tests would help characterize the possible health and environmental effects of the PMN substance, its impurities and its degradation products. The consent order contains two (confidential) production limits. The PMN submitter has agreed not to exceed the first production limit without performing an anaerobic aquatic metabolism test (OPPTS Test Guideline 835.4400) and an amphibian metamorphosis assay (OECD Test Guideline 231). The PMN submitter has also agreed not to exceed a second production limit without performing a dietary exposure bioaccumulation fish test (OECD Test Guideline 305, draft dated October 14, 2011) and a test of the PMN substance for BDD and BDF content by high-resolution gas chromatography/high-resolution mass spectrometry (HRGC/HRMS) (EPA Test Method 8290A). EPA has also determined that the following tests would help characterize the environmental effects of the PMN substance. The consent order does not require the submission of the following information at any specified time or production volume: A fish early-life stage toxicity test (OPPTS Test Guideline 850.1400), a daphnid chronic toxicity test (OPPTS Test Guideline 850.1300), and an algal toxicity, tiers I and II test (OPPTS Test Guideline 850.5400). However, the consent order's restrictions on manufacture, import, processing, distribution in commerce, use, and disposal of the PMN will remain in effect until the consent order is modified or revoked by EPA based on submission of that or other relevant information.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10416.</P>
        <HD SOURCE="HD1">PMN Number P-11-338</HD>
        <P>
          <E T="03">Chemical name:</E>Biphenyl alkyl morpholino ketone (generic).</P>
        <P>
          <E T="03">CAS number:</E>Not available.</P>
        <P>
          <E T="03">Basis for action:</E>The PMN states that the substance will be used as a photo initiator. Based on EcoSAR analysis of test data on analogous aliphatic amines, EPA predicts toxicity to aquatic organisms may occur at concentrations that exceed 2 ppb of the PMN substance in surface waters. As described in the PMN, the substance is not released to surface waters. Therefore, EPA has not determined that the proposed manufacturing, processing, or use of the substance may present an unreasonable risk. EPA has determined, however, that any use of the substance resulting in surface water concentrations exceeding 2 ppb may cause significant adverse environmental effects. Based on this information, the PMN substance meets the concern criteria at § 721.170(b)(4)(ii).</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of a ready biodegradability test (OPPTS Test Guideline 835.3110); a fish acute toxicity test, freshwater and marine (OPPTS Test Guideline 850.1075); an aquatic invertebrate acute toxicity test, freshwater daphnids (OPPTS Test Guideline 850.1010); and an algal toxicity test, tiers I and II test (OPPTS Test Guideline 850.5400) would help characterize the environmental effects of the PMN substance. EPA also recommends that the special considerations for conducting laboratory studies (OPPTS Test Guideline 850.1000) be followed to facilitate solubility in the test media, because of the PMN's low water solubility.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10417.</P>
        <HD SOURCE="HD1">PMN Number P-11-481</HD>
        <P>
          <E T="03">Chemical name:</E>1,2-Cyclohexanedicarboxylic acid, 1-butyl 2-(phenylmethyl) ester.</P>
        <P>
          <E T="03">CAS number:</E>1200806-67-2.</P>
        <P>
          <E T="03">Basis for action:</E>The PMN states that the generic (non-confidential) use of the substance is as an additive for polymers. Based on EcoSAR analysis of test data on analogous esters, EPA predicts toxicity to aquatic organisms may occur at concentrations that exceed 2 ppb of the PMN substance in surface waters. As described in the PMN, releases of the substance are not expected to result in surface water concentrations that exceed 2 ppb. Therefore, EPA has not determined that the proposed<PRTPAGE P="24619"/>manufacture, processing, or use of the substance may present an unreasonable risk. EPA has determined, however, that any use of the substance resulting in surface water concentrations exceeding 2 ppb may cause significant adverse environmental effects. Based on this information, the PMN substance meets the concern criteria at § 721.170(b)(4)(ii).</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of a fish acute toxicity test (OPPTS Test Guideline 850.1075); an aquatic invertebrate acute toxicity test, freshwater daphnids (OPPTS Test Guideline 850.1010); and an algal toxicity test, tiers I and II (OPPTS Test Guideline 850.5400) would help characterize the environmental effects of the PMN substance.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10418.</P>
        <HD SOURCE="HD1">PMN Number P-11-561</HD>
        <P>
          <E T="03">Chemical name:</E>Tetrafluoroethylene  chlorotrifluoroethylene copolymer (generic).</P>
        <P>
          <E T="03">CAS number:</E>Not available.</P>
        <P>
          <E T="03">Effective date of TSCA section 5(e) consent order:</E>January 27, 2012.</P>
        <P>
          <E T="03">Basis for TSCA section 5(e) consent order:</E>The PMN states that the substance will be used as a polymer used in automotive fuel hoses. Based on EPA analysis of the potential content of the polymer, EPA is concerned that some long-chain perfluorinated substances could be present and if degraded, especially under thermal conditions, could be released into the environment. EPA has concerns that the PMN substance and its thermal degradation products will persist in the environment, could bioaccumulate or biomagnify, and could be toxic to humans, wild mammals, and birds. These concerns are based on data on analog chemicals, including perfluorooctanoic acid (PFOA) and other perfluorinated carboxylates, which include the presumed environmental degradant of the PMN substance. There is pharmacokinetic and toxicological data in animals on PFOA, as well as epidemiological and blood monitoring data in humans. Toxicity studies on PFOA indicate developmental, reproductive, and systemic toxicity in various species, as well as cancer. These factors, taken together, raise concerns for potential adverse chronic effects from the presumed degradation product in humans and wildlife. The consent order was issued under TSCA sections 5(e)(1)(A)(i), 5(e)(1)(A)(ii)(I), and 5(e)(1)(A)(ii)(II), based on a finding that this substance may present an unreasonable risk of injury to human health and the environment, the substance may be produced in substantial quantities and may reasonably be anticipated to enter the environment in substantial quantities, and there may be significant (or substantial) human exposure to the substance and its potential degradation products. To protect against this exposure and risk, the consent order requires the PMN substance be manufactured, processed, distributed in commerce, and used only as a polymer in automotive fuel hoses and the submitter has agreed to analyze, report, and limit specific fluorinated impurities of the PMN substance where the carbon chain meets or exceeds a specified length. The SNUR designates as a “significant new use” the absence of these protective measures.</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of certain fate and physical/chemical property testing identified in the consent order would help characterize possible effects of the substances and their degradation products. The consent order does not require submission of the testing at any specified time or production volume. However, the consent order's restrictions on manufacture, import, processing, distribution in commerce, use, and disposal of the PMN will remain in effect until the consent order is modified or revoked by EPA based on submission of that or other relevant information.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10419.</P>
        <HD SOURCE="HD1">PMN Numbers P-11-567, P-11-568, and P-11-569</HD>
        <P>
          <E T="03">Chemical name:</E>Fluoropolymers (generic).</P>
        <P>
          <E T="03">CAS number:</E>Not available.</P>
        <P>
          <E T="03">Effective date of TSCA section 5(e) consent order:</E>January 27, 2012.</P>
        <P>
          <E T="03">Basis for TSCA section 5(e) consent order:</E>The PMNs state that the generic (non-confidential) use of the PMN substances will be in the manufacture of elastomer containing materials (P-11-567 and P-11-569), and a component of film, wire, and cable (P-11-568). Based on SAR analysis of test data on analogous high molecular weight polymers, EPA identified concerns for lung effects through lung overload if respirable particles of the intact PMN substances are inhaled. In addition, EPA has concerns for the formation of potential incineration or other decomposition products from the PMN substances. These perfluorinated products may be released to the environment from incomplete incineration of the PMN substances at low temperatures. EPA has preliminary evidence, including data on some fluorinated polymers, suggesting that, under some conditions, the PMN substance could degrade in the environment. EPA has concerns that these degradation products will persist in the environment, could bioaccumulate or biomagnify, and could be toxic to people, wild mammals, and birds. These concerns are based on data on analog chemicals, including PFOA and other perfluorinated carboxylates, which include the presumed environmental degradant of the PMN substance. There is pharmacokinetic and toxicological data in animals on PFOA, as well as epidemiological and blood monitoring data in humans. Toxicity studies on PFOA indicate developmental, reproductive, and systemic toxicity in various species, as well as cancer. These factors, taken together, raise concerns for potential adverse chronic effects from the presumed degradation product in humans and wildlife. The consent order was issued under TSCA sections 5(e)(1)(A)(i), 5(e)(1)(A)(ii)(I), and 5(e)(1)(A)(ii)(II), based on a finding that this substance may present an unreasonable risk of injury to human health and the environment, the substance may be produced in substantial quantities and may reasonably be anticipated to enter the environment in substantial quantities, and there may be significant (or substantial) human exposure to the substance and its potential degradation products. To protect against these risks, the consent order requires the submitter has agreed to analyze, report, and limit specific fluorinated impurities of the PMN substances where the carbon chain meets or exceeds a specified length and risk notification. The SNUR designates as a “significant new use” the absence of these protective measures.</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of certain fate and physical/chemical property testing identified in the consent order would help characterize possible effects of the substances and their degradation products. The consent order does not require submission of the testing at any specified time or production volume. However, the consent order's restrictions on manufacture, import, processing, distribution in commerce, use, and disposal of the PMNs will remain in effect until the consent order is modified or revoked by EPA based on submission of that or other relevant information.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10420.</P>
        <HD SOURCE="HD1">PMN Number P-11-594</HD>
        <P>
          <E T="03">Chemical name:</E>Mercaptoalkoxysilane (generic).<PRTPAGE P="24620"/>
        </P>
        <P>
          <E T="03">CAS number:</E>Not available.</P>
        <P>
          <E T="03">Basis for action:</E>The PMN states that the substance will be used as an epoxy catalyst. Based on EcoSAR analysis of test data on analogous alkoxysilanes, esters, and phenols, EPA predicts toxicity to aquatic organisms may occur at concentrations that exceed 2 ppb of the PMN substance in surface waters. As described in the PMN, the substance will not be released to water. Therefore, EPA has not determined that the proposed manufacturing, processing, or use of the substance may present an unreasonable risk. EPA has determined, however, that any use of the substance resulting in surface water concentrations exceeding 2 ppb may cause significant adverse environmental effects. Based on this information, the PMN substance meets the concern criteria at§ 721.170(b)(4)(ii).</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of a fish acute toxicity test, freshwater and marine (OPPTS Test Guideline 850.1075); an aquatic invertebrate acute toxicity test, freshwater daphnids (OPPTS Test Guideline 850.1010); and an algal toxicity test, tiers I and II (OPPTS Test Guideline 850.5400) would help characterize the environmental effects of the PMN substance.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10421.</P>
        <HD SOURCE="HD1">PMN Number P-11-654</HD>
        <P>
          <E T="03">Chemical name:</E>Phenol, 2-[[[3-(1H-imidazol-1-yl)propyl]imino]phenylmethyl]-5-(octyloxy)-.</P>
        <P>
          <E T="03">CAS number:</E>1332716-20-7.</P>
        <P>
          <E T="03">Basis for action:</E>The PMN states that the substance will be used as an epoxy catalyst. Based on EcoSAR analysis of test data on analogous Schiff bases and phenols, EPA predicts toxicity to aquatic organisms may occur at concentrations that exceed 1 ppb of the PMN substance in surface waters. As described in the PMN, the substance will not be released to water. Therefore, EPA has not determined that the proposed manufacturing, processing, or use of the substance may present an unreasonable risk. EPA has determined, however, that any use of the substance resulting in surface water concentrations exceeding 1 ppb may cause significant adverse environmental effects. Based on this information, the PMN substance meets the concern criteria at§ 721.170(b)(4)(ii).</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of a fish early-life stage toxicity test (OPPTS Test Guideline 850.1400); a daphnid chronic toxicity test (OPPTS Test Guideline 850.1300); and an algal toxicity test, tiers I and II (OPPTS Test Guideline 850.5400) would help characterize the environmental effects of the PMN substance.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10422.</P>
        <HD SOURCE="HD1">PMN Numbers: P-12-22, P-12-23, P-12-24, P-12-25, and P-12-26</HD>
        <P>
          <E T="03">Chemical names:</E>Complex strontium aluminum, rare earth doped (generic).</P>
        <P>
          <E T="03">CAS numbers:</E>Not available.</P>
        <P>
          <E T="03">Basis for action:</E>The PMNs state that the PMN substances will be used as dye used in the manufacture of imaging media/products. Based on analogous respirable and poorly soluble substances, in particular, titanium dioxide, EPA identified concerns for potential lung overload to workers from inhalation exposure to the PMN substances. Specifically, the Agency predicts potential toxicity to workers from inhalation when more than 5% of the PMN substances particles are less than 10 microns. For the uses described in the PMNs, significant worker exposure is unlikely, when no more than 5% of particles are less than 10 microns. Therefore, EPA has not determined that the proposed manufacturing, processing, or use of the substances may present an unreasonable risk. EPA has determined, however, that any use of the substances other than as described in the PMNs may cause serious health effects. Based on this information, the PMN substances meets the concern criteria at § 721.170(b)(3)(ii).</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that a 90-day inhalation toxicity test (OPPTS Test Guideline 870.3465) would help characterize the human health effects of the PMN substances.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10423.</P>
        <HD SOURCE="HD1">PMN Number P-12-33</HD>
        <P>
          <E T="03">Chemical name:</E>Benzoic acid, 4-(1,1-dimethylethyl)-, methyl.</P>
        <P>
          <E T="03">CAS number:</E>26537-19-9.</P>
        <P>
          <E T="03">Basis for action:</E>The PMN states that the substance will be used as an intermediate in the manufacture of an imaging product. Based on submitted test data on p-tert-butyl benzoic acid, EPA identified concerns for neurotoxicity; reproductive toxicity (male); and adverse effects to the liver, kidney, and lung. In addition, based on data on benzoic acid, EPA identified concerns for developmental toxicity and hypersensitivity. These concerns are for effects to workers from inhalation and dermal exposures to the PMN substance. For the chemical intermediate use described in the PMN, significant worker exposure is unlikely, as dermal and inhalation exposures are not expected. Therefore, EPA has not determined that the proposed manufacturing, processing, or use of the substance may present an unreasonable risk. EPA has determined, however, use of the substance other than as an intermediate may cause serious health effects. Based on this information, the PMN substance meets the concern criteria at § 721.170(b)(3)(ii).</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that a combined repeated dose toxicity with the reproduction/developmental toxicity screening test (OPPTS Test Guideline 870.3650) would help characterize the human health effects of the PMN substance.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10424.</P>
        <HD SOURCE="HD1">PMN Numbers: P-12-51 and P-12-52</HD>
        <P>
          <E T="03">Chemical names:</E>Substituted alkylamides (generic).</P>
        <P>
          <E T="03">CAS numbers:</E>Not available.</P>
        <P>
          <E T="03">Basis for action:</E>The PMNs state that the generic (non-confidential) use of the substances will be as polymer foam additives. Based on test data on analogous chemical substances and information on the Material Safety Data Sheet (MSDS), the Agency identified concerns for irritation to all exposed tissues, solvent irritation, and solvent neurotoxicity to workers from dermal exposure to the PMN substances. For the use described in the PMNs, significant worker exposure is unlikely, as dermal exposure is not expected. Therefore, EPA has not determined that the proposed manufacturing, processing, or use of the substances may present an unreasonable risk. EPA has determined, however, use of the substances other than as described in the PMNs may cause serious health effects. Based on this information, the PMN substances meet the concern criteria at § 721.170(b)(3)(ii).</P>
        <P>
          <E T="03">Recommended testing:</E>EPA has determined that the results of a combined repeated dose toxicity with the reproduction/developmental toxicity screening test (OPPTS Test Guideline 870.3650); a bacterial reverse mutation test (OPPTS Test Guideline 870.5100); and a mammalian erythrocyte micronucleus test (OPPTS Test Guideline 870.5395) would help characterize the human health effects of the PMN substances.</P>
        <P>
          <E T="03">CFR citation:</E>40 CFR 721.10425.</P>
        <HD SOURCE="HD1">V. Rationale and Objectives of the Rule</HD>
        <HD SOURCE="HD2">A. Rationale</HD>

        <P>During review of the PMNs submitted for the chemical substances that are subject to these SNURs, EPA concluded that for 9 of the 23 chemical substances, regulation was warranted under TSCA section 5(e), pending the development<PRTPAGE P="24621"/>of information sufficient to make reasoned evaluations of the health or environmental effects of the chemical substances. The basis for such findings is outlined in Unit IV. Based on these findings, TSCA section 5(e) consent orders requiring the use of appropriate exposure controls were negotiated with the PMN submitters. The SNUR provisions for these chemical substances are consistent with the provisions of the TSCA section 5(e) consent orders. These SNURs are promulgated pursuant to § 721.160 (see Unit II.).</P>
        <P>In the other 14 cases, where the uses are not regulated under a TSCA section 5(e) consent order, EPA determined that one or more of the criteria of concern established at § 721.170 were met, as discussed in Unit IV.</P>
        <HD SOURCE="HD2">B. Objectives</HD>
        <P>EPA is issuing these SNURs for specific chemical substances which have undergone premanufacture review because the Agency wants to achieve the following objectives with regard to the significant new uses designated in this rule:</P>
        <P>• EPA will receive notice of any person's intent to manufacture, import, or process a listed chemical substance for the described significant new use before that activity begins.</P>
        <P>• EPA will have an opportunity to review and evaluate data submitted in a SNUN before the notice submitter begins manufacturing, importing, or processing a listed chemical substance for the described significant new use.</P>
        <P>• EPA will be able to regulate prospective manufacturers, importers, or processors of a listed chemical substance before the described significant new use of that chemical substance occurs, provided that regulation is warranted pursuant to TSCA sections 5(e), 5(f), 6, or 7.</P>
        <P>• EPA will ensure that all manufacturers, importers, and processors of the same chemical substance that is subject to a TSCA section 5(e) consent order are subject to similar requirements.</P>

        <P>Issuance of a SNUR for a chemical substance does not signify that the chemical substance is listed on the TSCA Inventory. Guidance on how to determine if a chemical substance is on the TSCA Inventory is available on the Internet at<E T="03">http://www.epa.gov/opptintr/existingchemicals/pubs/tscainventory/index.html.</E>
        </P>
        <HD SOURCE="HD1">VI. Direct Final Procedures</HD>
        <P>EPA is issuing these SNURs as a direct final rule, as described in § 721.160(c)(3) and § 721.170(d)(4). In accordance with § 721.160(c)(3)(ii) and § 721.170(d)(4)(i)(B), the effective date of this rule is June 25, 2012 without further notice, unless EPA receives written adverse or critical comments, or notice of intent to submit adverse or critical comments before May 25, 2012.</P>
        <P>If EPA receives written adverse or critical comments, or notice of intent to submit adverse or critical comments, on one or more of these SNURs before May 25, 2012, EPA will withdraw the relevant sections of this direct final rule before its effective date. EPA will then issue a proposed SNUR for the chemical substance(s) on which adverse or critical comments were received, providing a 30-day period for public comment.</P>
        <P>This rule establishes SNURs for a number of chemical substances. Any person who submits adverse or critical comments, or notice of intent to submit adverse or critical comments, must identify the chemical substance and the new use to which it applies. EPA will not withdraw a SNUR for a chemical substance not identified in the comment.</P>
        <HD SOURCE="HD1">VII. Applicability of Rule to Uses Occurring Before Effective Date of the Rule</HD>
        <P>Significant new use designations for a chemical substance are legally established as of the date of publication of this direct final rule April 25, 2012.</P>

        <P>To establish a significant “new” use, EPA must determine that the use is not ongoing. The chemical substances subject to this rule have undergone premanufacture review. TSCA section 5(e) consent orders have been issued for 9 chemical substances and the PMN submitters are prohibited by the TSCA section 5(e) consent orders from undertaking activities which EPA is designating as significant new uses. In cases where EPA has not received a notice of commencement (NOC) and the chemical substance has not been added to the TSCA Inventory, no other person may commence such activities without first submitting a PMN. For chemical substances for which an NOC has not been submitted at this time, EPA concludes that the uses are not ongoing. However, EPA recognizes that prior to the effective date of the rule, when chemical substances identified in this SNUR are added to the TSCA Inventory, other persons may engage in a significant new use as defined in this rule before the effective date of the rule. However, 19 of the 23 chemical substances contained in this rule have CBI chemical identities, and since EPA has received a limited number of post-PMN<E T="03">bona fide</E>submissions (per 40 CFR 720.25 and § 721.11), the Agency believes that it is highly unlikely that any of the significant new uses described in the regulatory text of this rule are ongoing.</P>
        <P>As discussed in the April 24, 1990 SNUR, EPA has decided that the intent of TSCA section 5(a)(1)(B) is best served by designating a use as a significant new use as of the date of publication of this direct final rule rather than as of the effective date of the rule. If uses begun after publication were considered ongoing rather than new, it would be difficult for EPA to establish SNUR notice requirements because a person could defeat the SNUR by initiating the significant new use before the rule became effective, and then argue that the use was ongoing before the effective date of the rule. Persons who begin commercial manufacture, import, or processing of the chemical substances regulated through this SNUR will have to cease any such activity before the effective date of this rule. To resume their activities, these persons would have to comply with all applicable SNUR notice requirements and wait until the notice review period, including any extensions expires.</P>
        <P>EPA has promulgated provisions to allow persons to comply with this SNUR before the effective date. If a person meets the conditions of advance compliance under § 721.45(h),  the person is considered exempt from the requirements of the SNUR.</P>
        <HD SOURCE="HD1">VIII. Test Data and Other Information</HD>
        <P>EPA recognizes that TSCA section 5 does not require developing any particular test data before submission of a SNUN. The two exceptions are:</P>
        <P>1. Development of test data is required where the chemical substance subject to the SNUR is also subject to a test rule under TSCA section 4 (see TSCA section 5(b)(1)).</P>
        <P>2. Development of test data may be necessary where the chemical substance has been listed under TSCA section 5(b)(4) (see TSCA section 5(b)(2)).</P>

        <P>In the absence of a TSCA section 4 test rule or a TSCA section 5(b)(4) listing covering the chemical substance, persons are required only to submit test data in their possession or control and to describe any other data known to or reasonably ascertainable by them (see 40 CFR 720.50). However, upon review of PMNs and SNUNs, the Agency has the authority to require appropriate testing. In cases where EPA issued a TSCA section 5(e) consent order that requires or recommends certain testing, Unit IV. describes those tests. Unit IV. also lists recommended testing for non-5(e) SNURs. Descriptions of tests are<PRTPAGE P="24622"/>provided for informational purposes. EPA strongly encourages persons, before performing any testing, to consult with the Agency pertaining to protocol selection and test reporting. To access the harmonized test guidelines referenced in this document electronically, please go to<E T="03">http://www.epa.gov/ocspp</E>and select “Test Methods and Guidelines.” The Organisation for Economic Co-operation and Development (OECD) test guidelines are available from the OECD Bookshop at<E T="03">http://www.oecdbookshop.org</E>or SourceOECD at<E T="03">http://www.sourceoecd.org.</E>To access EPA Method 8290A, please go to<E T="03">http://www.epa.gov/osw/hazard/testmethods/sw846/pdfs/8290a.pdf.</E>
        </P>
        <P>In the TSCA section 5(e) consent orders for several of the chemical substances regulated under this rule, EPA has established production volume limits in view of the lack of data on the potential health and environmental risks that may be posed by the significant new uses or increased exposure to the chemical substances. These limits cannot be exceeded unless the PMN submitter first submits the results of toxicity tests that would permit a reasoned evaluation of the potential risks posed by these chemical substances. Listings of the tests specified in the TSCA section 5(e) consent orders are included in Unit IV. The SNURs contain the same production limits as the TSCA section 5(e) consent orders. Exceeding these production limits is defined as a significant new use. Persons who intend to exceed the production limit must notify the Agency by submitting a SNUN at least 90 days in advance of commencement of non-exempt commercial manufacture, import, or processing.</P>
        <P>The recommended tests specified in Unit IV. may not be the only means of addressing the potential risks of the chemical substance. However, submitting a SNUN without any test data may increase the likelihood that EPA will take action under TSCA section 5(e), particularly if satisfactory test results have not been obtained from a prior PMN or SNUN submitter. EPA recommends that potential SNUN submitters contact EPA early enough so that they will be able to conduct the appropriate tests.</P>
        <P>SNUN submitters should be aware that EPA will be better able to evaluate SNUNs which provide detailed information on the following:</P>
        <P>• Human exposure and environmental release that may result from the significant new use of the chemical substances.</P>
        <P>• Potential benefits of the chemical substances.</P>
        <P>• Information on risks posed by the chemical substances compared to risks posed by potential substitutes.</P>
        <HD SOURCE="HD1">IX. Procedural Determinations</HD>
        <P>By this rule, EPA is establishing certain significant new uses which have been claimed as CBI subject to Agency confidentiality regulations at 40 CFR part 2 and 40 CFR part 720, subpart E. Absent a final determination or other disposition of the confidentiality claim under 40 CFR part 2 procedures, EPA is required to keep this information confidential. EPA promulgated a procedure to deal with the situation where a specific significant new use is CBI, at § 721.1725(b)(1).</P>

        <P>Under these procedures a manufacturer, importer, or processor may request EPA to determine whether a proposed use would be a significant new use under the rule. The manufacturer, importer, or processor must show that it has a<E T="03">bona fide</E>intent to manufacture, import, or process the chemical substance and must identify the specific use for which it intends to manufacture, import, or process the chemical substance. If EPA concludes that the person has shown a<E T="03">bona fide</E>intent to manufacture, import, or process the chemical substance, EPA will tell the person whether the use identified in the<E T="03">bona fide</E>submission would be a significant new use under the rule. Since most of the chemical identities of the chemical substances subject to these SNURs are also CBI, manufacturers, importers, and processors can combine the<E T="03">bona fide</E>submission under the procedure in § 721.1725(b)(1) with that under § 721.11 into a single step.</P>
        <P>If EPA determines that the use identified in the<E T="03">bona fide</E>submission would not be a significant new use, i.e., the use does not meet the criteria specified in the rule for a significant new use, that person can manufacture, import, or process the chemical substance so long as the significant new use trigger is not met. In the case of a production volume trigger, this means that the aggregate annual production volume does not exceed that identified in the<E T="03">bona fide</E>submission to EPA. Because of confidentiality concerns, EPA does not typically disclose the actual production volume that constitutes the use trigger. Thus, if the person later intends to exceed that volume, a new<E T="03">bona fide</E>submission would be necessary to determine whether that higher volume would be a significant new use.</P>
        <HD SOURCE="HD1">X. SNUN Submissions</HD>

        <P>According to § 721.1(c), persons submitting a SNUN must comply with the same notice requirements and EPA regulatory procedures as persons submitting a PMN, including submission of test data on health and environmental effects as described in 40 CFR 720.50. SNUNs must be submitted on EPA Form No. 7710-25, generated using e-PMN software, and submitted to the Agency in accordance with the procedures set forth in § 721.25 and 40 CFR 720.40. e-PMN software is available electronically at<E T="03">http://www.epa.gov/opptintr/newchems.</E>
        </P>
        <HD SOURCE="HD1">XI. Economic Analysis</HD>
        <P>EPA has evaluated the potential costs of establishing SNUN requirements for potential manufacturers, importers, and processors of the chemical substances subject to this rule. EPA's complete economic analysis is available in the docket under docket ID number EPA-HQ-OPPT-2012-0182.</P>
        <HD SOURCE="HD1">XII. Statutory and Executive Order Reviews</HD>
        <HD SOURCE="HD2">A. Executive Order 12866</HD>
        <P>This rule establishes SNURs for several new chemical substances that were the subject of PMNs, or TSCA section 5(e) consent orders. The Office of Management and Budget (OMB) has exempted these types of actions from review under Executive Order 12866, entitled “Regulatory Planning and Review” (58 FR 51735, October 4, 1993).</P>
        <HD SOURCE="HD2">B. Paperwork Reduction Act</HD>

        <P>According to the Paperwork Reduction Act (PRA), 44 U.S.C. 3501<E T="03">et seq.,</E>an Agency may not conduct or sponsor, and a person is not required to respond to a collection of information that requires OMB approval under PRA, unless it has been approved by OMB and displays a currently valid OMB control number. The OMB control numbers for EPA's regulations in title 40 of the CFR, after appearing in the<E T="04">Federal Register</E>, are listed in 40 CFR part 9, and included on the related collection instrument or form, if applicable. EPA is amending the table in 40 CFR part 9 to list the OMB approval number for the information collection requirements contained in this rule. This listing of the OMB control numbers and their subsequent codification in the CFR satisfies the display requirements of PRA and OMB's implementing regulations at 5 CFR part 1320. This Information Collection Request (ICR) was previously subject to public notice and comment prior to OMB approval, and given the technical nature of the<PRTPAGE P="24623"/>table, EPA finds that further notice and comment to amend it is unnecessary. As a result, EPA finds that there is “good cause” under section 553(b)(3)(B) of the Administrative Procedure Act, 5 U.S.C. 553(b)(3)(B), to amend this table without further notice and comment.</P>
        <P>The information collection requirements related to this action have already been approved by OMB pursuant to PRA under OMB control number 2070-0012 (EPA ICR No. 574). This action does not impose any burden requiring additional OMB approval. If an entity were to submit a SNUN to the Agency, the annual burden is estimated to average between 30 and 170 hours per response. This burden estimate includes the time needed to review instructions, search existing data sources, gather and maintain the data needed, and complete, review, and submit the required SNUN.</P>
        <P>Send any comments about the accuracy of the burden estimate, and any suggested methods for minimizing respondent burden, including through the use of automated collection techniques, to the Director, Collection Strategies Division, Office of Environmental Information (2822T), Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001. Please remember to include the OMB control number in any correspondence, but do not submit any completed forms to this address.</P>
        <HD SOURCE="HD2">C. Regulatory Flexibility Act</HD>

        <P>On February 18, 2012, EPA certified pursuant to section 605(b) of the Regulatory Flexibility Act (RFA) (5 U.S.C. 601<E T="03">et seq.</E>), that promulgation of a SNUR does not have a significant economic impact on a substantial number of small entities where the following are true:</P>
        <P>1. A significant number of SNUNs would not be submitted by small entities in response to the SNUR.</P>
        <P>2. The SNUN submitted by any small entity would not cost significantly more than $8300.</P>
        <P>A copy of that certification is available in the docket for this rule.</P>
        <P>This rule is within the scope of the February 18, 2012 certification. Based on the Economic Analysis discussed in Unit XI. and EPA's experience promulgating SNURs (discussed in the certification), EPA believes that the following are true:</P>
        <P>• A significant number of SNUNs would not be submitted by small entities in response to the SNUR.</P>
        <P>• Submission of the SNUN would not cost any small entity significantly more than $8,300. Therefore, the promulgation of the SNUR would not have a significant economic impact on a substantial number of small entities.</P>
        <HD SOURCE="HD2">D. Unfunded Mandates Reform Act</HD>
        <P>Based on EPA's experience with proposing and finalizing SNURs, State, local, and Tribal governments have not been impacted by these rulemakings, and EPA does not have any reasons to believe that any State, local, or Tribal government will be impacted by this rule. As such, EPA has determined that this rule does not impose any enforceable duty, contain any unfunded mandate, or otherwise have any effect on small governments subject to the requirements of sections 202, 203, 204, or 205 of the Unfunded Mandates Reform Act of 1995 (UMRA) (Pub. L. 104-4).</P>
        <HD SOURCE="HD2">E. Executive Order 13132</HD>
        <P>This action will not have a substantial direct effect on States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government, as specified in Executive Order 13132, entitled “Federalism” (64 FR 43255, August 10, 1999).</P>
        <HD SOURCE="HD2">F. Executive Order 13175</HD>
        <P>This rule does not have Tribal implications because it is not expected to have substantial direct effects on Indian Tribes. This rule does not significantly nor uniquely affect the communities of Indian Tribal governments, nor does it involve or impose any requirements that affect Indian Tribes. Accordingly, the requirements of Executive Order 13175, entitled “Consultation and Coordination With Indian Tribal Governments” (65 FR 67249, November 9, 2000), do not apply to this rule.</P>
        <HD SOURCE="HD2">G. Executive Order 13045</HD>
        <P>This action is not subject to Executive Order 13045, entitled “Protection of Children from Environmental Health Risks and Safety Risks” (62 FR 19885, April 23, 1997), because this is not an economically significant regulatory action as defined by Executive Order 12866, and this action does not address environmental health or safety risks disproportionately affecting children.</P>
        <HD SOURCE="HD2">H. Executive Order 13211</HD>
        <P>This action is not subject to Executive Order 13211, entitled “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001), because this action is not expected to affect energy supply, distribution, or use and because this action is not a significant regulatory action under Executive Order 12866.</P>
        <HD SOURCE="HD2">I. National Technology Transfer and Advancement Act</HD>
        <P>In addition, since this action does not involve any technical standards, section 12(d) of the National Technology Transfer and Advancement Act of 1995 (NTTAA), Public Law 104-113, section 12(d) (15 U.S.C. 272 note), does not apply to this action.</P>
        <HD SOURCE="HD2">J. Executive Order 12898</HD>
        <P>This action does not entail special considerations of environmental justice related issues as delineated by Executive Order 12898, entitled “Federal Actions To Address Environmental Justice in Minority Populations and Low-Income Populations” (59 FR 7629, February 16, 1994).</P>
        <HD SOURCE="HD1">XIII. Congressional Review Act</HD>
        <P>Pursuant to the Congressional Review Act, 5 U.S.C. 801<E T="03">et seq.,</E>EPA will submit a report containing this rule and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the<E T="04">Federal Register</E>. This action is not a “major rule” as defined by 5 U.S.C. 804(2).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>40 CFR Part 9</CFR>
          <P>Environmental protection, Reporting and recordkeeping requirements.</P>
          <CFR>40 CFR Part 721</CFR>
          <P>Environmental protection, Chemicals, Hazardous substances, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: April 19, 2012.</DATED>
          <NAME>Ward Penberthy,</NAME>
          <TITLE>Acting Director, Chemical Control Division, Office of Pollution Prevention and Toxics.</TITLE>
        </SIG>
        
        <P>Therefore, 40 CFR parts 9 and 721 are amended as follows:</P>
        <REGTEXT PART="9" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 9—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 9 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 135<E T="03">et seq.,</E>136-136y; 15 U.S.C. 2001, 2003, 2005, 2006, 2601-2671; 21 U.S.C. 331j, 346a, 348; 31 U.S.C. 9701; 33 U.S.C. 1251<E T="03">et seq.,</E>1311, 1313d, 1314, 1318, 1321, 1326, 1330, 1342, 1344, 1345 (d) and (e), 1361; E.O. 11735, 38 FR 21243, 3 CFR, 1971-1975 Comp. p. 973; 42 U.S.C. 241, 242b, 243, 246, 300f, 300g, 300g-1, 300g-2, 300g-3, 300g-4, 300g-5, 300g-6, 300j-1, 300j-2, 300j-3, 300j-4, 300j-9, 1857<E T="03">et seq.,</E>6901-6992k, 7401-7671q, 7542, 9601-9657, 11023, 11048.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="9" TITLE="40">
          <PRTPAGE P="24624"/>
          <AMDPAR>2. In § 9.1, add the following sections in numerical order under the undesignated center heading “Significant New Uses of Chemical Substances” to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 9.1</SECTNO>
            <SUBJECT>OMB approvals under the Paperwork Reduction Act.</SUBJECT>
            <STARS/>
            <GPOTABLE CDEF="s50,12" COLS="2" OPTS="L1,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1">40 CFR Citation</CHED>
                <CHED H="1">OMB Control No.</CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*****</ENT>
              </ROW>
              <ROW EXPSTB="01" RUL="s">
                <ENT I="21">
                  <E T="02">Significant New Uses of Chemical Substances</E>
                </ENT>
              </ROW>
              <ROW EXPSTB="00">
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*****</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10410</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10411</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10412</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10413</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10414</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10415</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10416</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10417</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10418</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10419</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10420</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10421</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10422</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10423</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10424</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="01">721.10425</ENT>
                <ENT>2070-0012</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*****</ENT>
              </ROW>
            </GPOTABLE>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 721—[AMENDED]</HD>
          </PART>
          <AMDPAR>3. The authority citation for part 721 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>15 U.S.C. 2604, 2607, and 2625(c).</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="9" TITLE="40">
          <AMDPAR>4. Add § 721.10410 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10410</SECTNO>
            <SUBJECT>Polyether ester acid compound with a polyamine amide (generic) (P-05-714).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified generically as polyether ester acid compound with a polyamine amide (PMN P-05-714) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Industrial, commercial, and consumer activities.</E>Requirements as specified in § 721.80(j) (additive for industrial paints, industrial coatings, and architectural coatings).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (i) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>5. Add § 721.10411 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10411</SECTNO>
            <SUBJECT>Alkanenitrile, bis(cyanoalkyl)amino (generic) (P-07-537).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified generically as alkanenitrile, bis(cyanoalkyl)amino (PMN P-07-537) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section. The requirements of this section do not apply to quantities of the PMN substance after it has been completely reacted (cured).</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Protection in the workplace.</E>Requirements as specified in § 721.63(a)(1), (a)(2)(i), (a)(3), (a)(4), (a)(5), (a)(6)(i), (a)(6)(ii), (a)(6)(v), (a)(6)(vi), (b) (concentration set at 1.0 percent), and (c). The following National Institute for Occupational Safety and Health (NIOSH)-certified respirator with an assigned protection factor (APF) of at least 5 meets the minimum requirements for § 721.63(a)(4): NIOSH-certified air-purifying, tight-fitting full-face respirator equipped with N100 (if oil aerosols absent), R100, or P100 filters; NIOSH-certified powered air-purifying respirator equipped with a loose- fitting hood or helmet and high efficiency particulate air (HEPA) filters; NIOSH-certified powered air-purifying respirator equipped with a tight-fitting facepiece (full-face) and HEPA filters; or NIOSH-certified supplied-air respirator operated in pressure demand or continuous flow mode and equipped with a hood or helmet, or tight-fitting facepiece (full-face) and HEPA filters.</P>
            <P>(A) As an alternative to the respiratory requirements listed in paragraph (a)(2)(i), a manufacturer, importer, or processor may choose to follow the new chemical exposure limit (NCEL) provisions listed in the TSCA section 5(e) consent order for this substance. The NCEL is 70 microgram/cubic meter (μg/m<SU>3</SU>) as an 8-hour time-weighted average. Persons who wish to pursue NCELs as an alternative to the § 721.63 respirator requirements may request to do so under § 721.30. Persons whose § 721.30 requests to use the NCELs approach are approved by EPA will receive NCELs provisions comparable to those contained in the corresponding TSCA section 5(e) consent order.</P>
            <P>(B) [Reserved]</P>
            <P>(ii)<E T="03">Hazard communication program.</E>Requirements as specified in § 721.72(a), (b), (c), (d), (e)(concentration set at 1.0 percent), (f), (g)(1)(i), (g)(1)(ii), (g)(1)(iii), (g)(1)(iv), (g)(2)(i), (g)(2)(ii), (g)(2)(iii), (g)(2)(iv) (use respiratory protection, or maintain workplace airborne concentrations at or below an 8-hour time-weighted average of 70 μg/m<SU>3</SU>), (g)(2)(v), (g)(3)(i), (g)(3)(ii), (g)(4)(i), (g)(4)(iii), and (g)(5).</P>
            <P>(iii)<E T="03">Industrial, commercial, and consumer activities.</E>Requirements as specified in § 721.80(h) and (q).</P>
            <P>(iv)<E T="03">Disposal.</E>Requirements as specified in § 721.85(a)(1), (a)(2), (b)(1), (b)(2), (c)(1), and (c)(2).</P>
            <P>(v)<E T="03">Release to water.</E>Requirements as specified in § 721.90(a)(1), (b)(1), and (c)(1).</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a) through (k) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
            <P>(3)<E T="03">Determining whether a specific use is subject to this section.</E>The provisions of § 721.1725(b)(1) apply to paragraph (a)(2)(iii) of this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>6. Add § 721.10412 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10412</SECTNO>
            <SUBJECT>Phosphonic acid ester (generic) (P-07-706).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified generically as phosphonic acid ester (PMN P-07-706) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section. The requirements of this section do not apply to quantities of the PMN substance after it has been completely reacted (cured).</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Protection in the workplace.</E>Requirements as specified in § 721.63(a)(1), (a)(2), (a)(3), (a)(4), (a)(5), (a)(6)(i), (a)(6)(v), (a)(6)(i), (a)(6)(ii), (a)(6)(v), (a)(6)(vi), (b) (concentration set at 0.1 percent) and (c). The following National Institute for Occupational Safety and Health (NIOSH)-approved respirators with an assigned protection<PRTPAGE P="24625"/>factor (APF) of 15 meet the minimum requirements for § 721.63 (a)(4): NIOSH-certified air-purifying, tight-fitting full-face respirator equipped with the appropriate gas/vapor cartridges (organic vapor, acid gas, or substance-specific); NIOSH-certified powered air-purifying respirator equipped with a loose-fitting hood or helmet and the appropriate gas/vapor cartridges (organic vapor, acid gas, or substance-specific); NIOSH-certified powered air-purifying respirator with a tight-fitting facepiece (full-face) and equipped with the appropriate gas/vapor cartridges (organic vapor, acid gas, or substance-specific); NIOSH-certified supplied-air respirator operated in pressure demand or continuous flow mode and equipped with a hood or helmet, or tight-fitting facepiece (full-face); or NIOSH-certified supplied-air respirator operated in pressure demand or continuous flow mode and equipped with a loose-fitting hood or helmet or a tight-fitting facepiece (full-face) if no cartridge service life testing is available.</P>
            <P>(A) As an alternative to the respiratory requirements listed in paragraph (a)(2)(i), a manufacturer, importer, or processor may choose to follow the new chemical exposure limit (NCEL) provisions listed in the TSCA section 5(e) consent order for this substance. The NCEL is 1.0 millgram/cubic meter (mg/m<SU>3</SU>) as an 8-hour time-weighted-average. Persons who wish to pursue NCELs as an alternative to the § 721.63 respirator requirements may request to do so under § 721.30. Persons whose § 721.30 requests to use the NCELs approach are approved by EPA will receive NCELs provisions comparable to those contained in the corresponding TSCA section 5(e) consent order.</P>
            <P>(B) [Reserved]</P>
            <P>(ii)<E T="03">Hazard communication program.</E>Requirements as specified in § 721.72(a), (b), (c), (d), (e) (concentration set at 0.1 percent), (f), (g)(1)(i), (g)(1)(vi), (g)(1)(vii), (g)(1)(ix), (g)(2)(i), (g)(2)(ii), (g)(2)(iii), (g)(2)(iv) (use respiratory protection or maintain workplace airborne concentrations at or below an 8-hour time-weighted average of 1.0 mg/m<SU>3</SU>), and (g)(5).</P>
            <P>(iii)<E T="03">Industrial, commercial, and consumer activities</E>
              <E T="03">.</E>Requirements as specified in § 721.80(q).</P>
            <P>(b)<E T="03">Specific requirements</E>
              <E T="03">.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a) through (i) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
            <P>(3)<E T="03">Determining whether a specific use is subject to this section.</E>The provisions of § 721.1725(b)(1) apply to paragraph (a)(2)(iii) of this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>7. Add § 721.10413 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10413</SECTNO>
            <SUBJECT>Fluorinated dialkyl ketone (generic) (P-10-135).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified generically as fluorinated dialkyl ketone (PMN P-10-135) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Industrial, commercial, and consumer activities.</E>Requirements as specified in § 721.80(t).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (i) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
            <P>(3)<E T="03">Determining whether a specific use is subject to this section.</E>The provisions of § 721.1725(b)(1) apply to paragraph (a)(2)(i) of this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>8. Add § 721.10414 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10414</SECTNO>
            <SUBJECT>Polycyclic polyamine diester organometallic compound (generic) (P-10-358).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified as iron(1+), chloro[rel-1,5-dimethyl (1R,2S,4R,5S)-9,9-dihydroxy-3-methyl-2,4-di(2-pyridinyl-.kappa.N)-7-[(2-pyridinyl-.kappa.N)methyl]-3,7-diazabicyclo[3.3.1]nonane-1,5-dicarboxylate-.kappa.N3,.kappa.N7]-,chloride (1:1), (OC-6-63)-(PMN P-10-358, CAS No. 478945-46-9) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section. The requirements of this section do not apply to quantities of the PMN substance after it has been completely reacted (cured).</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Protection in the workplace.</E>Requirements as specified in § 721.63(a)(1), (a)(2), (a)(3), (a)(6)(i), (a)(6)(ii), (a)(6)(iv), (a)(6)(v), (a)(6)(vi), (b) (concentration set at 1.0 percent), and (c).</P>
            <P>(ii)<E T="03">Hazard communication program.</E>Requirements as specified in § 721.72(a), (b), (c), (d), (e) (concentration set at 1.0 percent), (g)(1)(i), (g)(1)(iii), (g)(1)(iv), (g)(1)(viii), (g)(2)(i), (g)(2)(v), (g)(3)(i), (g)(3)(ii), and (g)(5).</P>
            <P>(iii)<E T="03">Industrial, commercial, and consumer activities. R</E>equirements as specified in § 721.80(j), (t), (v)(1), (v)(2), (w)(1), (w)(2), (x)(1), and (x)(2).</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a) through (i) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
            <P>(3)<E T="03">Determining whether a specific use is subject to this section.</E>The provisions of § 721.1725(b)(1) apply to paragraph (a)(2)(iii) of this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>9. Add § 721.10415 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10415</SECTNO>
            <SUBJECT>3H-indolium, 2-[2-[3-[2-(1,3-dihydro-1,3,3-trimethyl-2H-indol-2-ylidene)ethylidene]-2-[(1-phenyl-1H-tetrazol-5-yl)thio]-1-cyclohexen-1-yl]ethenyl]-1, 3, 3-trimethyl-, chloride (1:1).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified as 3H-indolium, 2-[2-[3-[2-(1,3-dihydro-1,3,3-trimethyl-2H-indol-2-ylidene)ethylidene]-2-[(1-phenyl-1H-tetrazol-5-yl)thio]-1-cyclohexen-1-yl]ethenyl]-1, 3, 3-trimethyl-, chloride (1:1) (PMN P-11-128, CAS No. 440102-72-7) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Industrial, commercial, and consumer activities</E>
              <E T="03">.</E>Requirements as specified in § 721.80(s) (10,000 kilogram (kg)).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping</E>
              <E T="03">.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (i) are applicable to manufacturers, importers, and processors of this substance,</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>
              <E T="03"/>The<PRTPAGE P="24626"/>provisions of § 721.185 apply to this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>10. Add § 721.10416 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10416</SECTNO>
            <SUBJECT>Brominated polyphenyl ether (generic) (P-11-264).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified generically as brominated polyphenyl ether (PMN P-11-264) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section. The requirements of this section do not apply to quantities of the PMN substance after it has been completely reacted (cured).</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Industrial, commercial, and consumer activities</E>. Requirements as specified in § 721.80(j) (manufacture of the substance at a molecular weight greater than or equal to that described in PMN P-11-264), § 721.80 (k) (manufacture at the facility described in PMN P-11-264 or by the process described in PMN P-11-264 (changes in manufacturing processes include, but are not limited to, changes in feedstock, reaction conditions, and/or product isolation and purification) unless the brominated dibenzodioxin (BDD)/brominated dibenzofuran (BDF) testing (EPA Test Method 8290A) required in the consent order is conducted at the new facility or for the new manufacturing method and the test results submitted to EPA within 16 months of changing the manufacturing process or commencement of manufacture at a different facility; manufacture of the substance where levels of the fifteen BDD/BDF congeners are detected at or below the Levels of Quantification (LOQs) published in EPA's Dioxin test rule (40 CFR 766.27)).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (i) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>11. Add § 721.10417 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10417</SECTNO>
            <SUBJECT>Biphenyl alkyl morpholino ketone (generic) (P-11-338).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified generically as biphenyl alkyl morpholino ketone (PMN P-11-338) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Release to water.</E>Requirements as specified in § 721.90(a)(4), (b)(4), and (c)(4) (N = 2).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (k) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements</E>
              <E T="03">.</E>The provisions of § 721.185 apply to this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>12. Add § 721.10418 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10418</SECTNO>
            <SUBJECT>1,2-Cyclohexanedicarboxylic acid, 1-butyl 2-(phenylmethyl) ester.</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance is identified as 1,2-cyclohexanedicarboxylic acid, 1-butyl 2-(phenylmethyl) ester (PMN P-11-481, CAS No. 1200806-67-2) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Release to water.</E>Requirements as specified in § 721.90(a)(4), (b)(4), and (c)(4) (N = 2).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (k) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>13. Add § 721.10419 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10419</SECTNO>
            <SUBJECT>Tetrafluoroethylene chlorotrifluoroethylene copolymer (generic) (P-11-561).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified generically as tetrafluoroethylene chlorotrifluoroethylene copolymer (PMN P-11-561) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section. The requirements of this section do not apply to quantities of the PMN substance after it has been completely reacted (cured).</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Industrial, commercial, and consumer activities.</E>Requirements as specified in § 721.80(k) (manufacture, processing, distribution in commerce, and use of PMN P-11-561 substance only as a polymer in automotive fuel hoses; analysis and reporting and limitations of maximum impurity levels of certain fluorinated impurities).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (i) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
            <P>(3)<E T="03">Determining whether a specific use is subject to this section.</E>The provisions of § 721.1725(b)(1) apply to paragraph (a)(2)(i) of this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>14. Add § 721.10420 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10420</SECTNO>
            <SUBJECT>Fluoropolymers (generic) (P-11-567, P-11-568, and P-11-569).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substances identified generically as fluoropolymers (PMNs P-11-567, P-11-568, and P-11-569) are subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section. The requirements of this section do not apply to quantities of the PMN substances after it has been completely reacted (cured). These PMN substances, which have been molded into final articles and which are recycled into non-virgin raw material are again subject to the requirements of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Hazard communication program.</E>A significant new use of this substance is any manner or method of manufacture, import, or processing associated with any use of this substance without providing risk notification as follows:</P>

            <P>(A) If as a result of the test data required under the TSCA section 5(e) consent order for this substance, the employer becomes aware that this substance may present a risk of injury to human health, the employer must incorporate this new information, and<PRTPAGE P="24627"/>any information on methods for protecting against such risk, into a Material Safety Data Sheet (MSDS) as described in § 721.72(c) within 90 days from the time the employer becomes aware of the new information. If this substance is not being manufactured, imported, processed, or used in the employer's workplace, the employer must add the new information to a MSDS before the substance is reintroduced into the workplace.</P>
            <P>(B) The employer must ensure that persons who will receive this substance from the employer are provided a MSDS as described in § 721.72(c) containing the information required under paragraph (a)(2)(i)(A) of this section within 90 days from the time the employer becomes aware of the new information.</P>
            <P>(ii)<E T="03">Industrial, commercial, and consumer activities.</E>Requirements as specified in § 721.80(k) (analysis and reporting and limitations of maximum impurity levels of certain fluorinated impurities).</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (i) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
            <P>(3)<E T="03">Determining whether a specific use is subject to this section.</E>The provisions of § 721.1725(b)(1) apply to paragraph (a)(2)(ii) of this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>15. Add § 721.10421 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10421</SECTNO>
            <SUBJECT>Mercaptoalkoxysilane (generic) (P-11-594).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified generically as mercaptoalkoxysilane (PMN P-11-594) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Release to water.</E>Requirements as specified in § 721.90(a)(4), (b)(4), and (c)(4) (N = 2).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (k) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>16. Add § 721.10422 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10422</SECTNO>
            <SUBJECT>Phenol, 2-[[[3-(1H-imidazol-1-yl)propyl]imino]phenylmethyl]-5-(octyloxy)-.</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified as phenol, 2-[[[3-(1H-imidazol-1-yl)propyl]imino]phenylmethyl]-5-(octyloxy)- (PMN P-11-654, CAS No. 1332716-20-7) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Release to water.</E>Requirements as specified in § 721.90(a)(4), (b)(4), and (c)(4) (N = 1).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (k) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>17. Add § 721.10423 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10423</SECTNO>
            <SUBJECT>Complex strontium aluminum, rare earth doped (generic) (P-12-22, P-12-23, P-12-24, P-12-25, and P-12-26).</SUBJECT>
            <P>(a)<E T="03">Chemical substances and significant new uses subject to reporting.</E>(1) The chemical substances identified generically as complex strontium aluminum, rare earth doped (PMNs P-12-22, P-12-23, P-12-24, P-12-25, and P-12-26) are subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Industrial, commercial, and consumer activities.</E>Requirements as specified in § 721.80(j) (manufacture, processing, or use where no more than 5% of particles are less than 10 microns).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (i) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>18. Add § 721.10424 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10424</SECTNO>
            <SUBJECT>Benzoic acid, 4-(1,1-dimethylethyl)-, methyl.</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substance identified as benzoic acid, 4-(1,1-dimethylethyl)-, methyl (PMN P-12-33, CAS No. 26537-19-9) is subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Industrial, commercial, and consumer activities.</E>Requirements as specified in § 721.80(g).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (i) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <AMDPAR>19. Add § 721.10425 to subpart E to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 721.10425</SECTNO>
            <SUBJECT>Substituted alkylamides (generic) (P-12-51 and P-12-52).</SUBJECT>
            <P>(a)<E T="03">Chemical substance and significant new uses subject to reporting.</E>(1) The chemical substances identified generically as substituted alkylamides (PMNs P-12-51 and P-12-52) are subject to reporting under this section for the significant new uses described in paragraph (a)(2) of this section.</P>
            <P>(2) The significant new uses are:</P>
            <P>(i)<E T="03">Industrial, commercial, and consumer activities.</E>Requirements as specified in § 721.80(j).</P>
            <P>(ii) [Reserved]</P>
            <P>(b)<E T="03">Specific requirements.</E>The provisions of subpart A of this part apply to this section except as modified by this paragraph.</P>
            <P>(1)<E T="03">Recordkeeping.</E>Recordkeeping requirements as specified in § 721.125(a), (b), (c), and (i) are applicable to manufacturers, importers, and processors of this substance.</P>
            <P>(2)<E T="03">Limitations or revocation of certain notification requirements.</E>The provisions of § 721.185 apply to this section.<PRTPAGE P="24628"/>
            </P>
            <P>(3)<E T="03">Determining whether a specific use is subject to this section.</E>The provisions of § 721.1725(b)(1) apply to paragraph (a)(2)(i) of this section.</P>
          </SECTION>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9965 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <DEPDOC>[Docket No. CDC-2011-0010]</DEPDOC>
        <CFR>42 CFR Part 88</CFR>
        <RIN>RIN 0920-AA45</RIN>
        <SUBJECT>World Trade Center Health Program Requirements for the Addition of New WTC-Related Health Conditions</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Centers for Disease Control and Prevention, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Title I of the James Zadroga 9/11 Health and Compensation Act of 2010 amended the Public Health Service Act (PHS Act) to establish the World Trade Center (WTC) Health Program. Sections 3311, 3312, and 3321 of Title XXXIII of the PHS Act require that the WTC Program Administrator develop regulations to implement portions of the WTC Health Program established within the Department of Health and Human Services (HHS). The WTC Health Program, which is administered by the Director of the National Institute for Occupational Safety and Health (NIOSH), within the Centers for Disease Control and Prevention (CDC), provides medical monitoring and treatment to eligible firefighters and related personnel, law enforcement officers, and rescue, recovery and cleanup workers who responded to the September 11, 2001, terrorist attacks in New York City, Shanksville, PA, and at the Pentagon, and to eligible survivors of the New York City attacks. This final rule establishes the processes by which the WTC Program Administrator may add a new condition to the list of WTC-related health conditions through rulemaking, including a process for considering petitions by interested parties to add a new condition.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This final rule is effective May 25, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Roy M. Fleming, Sc.D., Senior Science Advisor, World Trade Center Health Program, Office of the Director, National Institute for Occupational Safety and Health, 1600 Clifton Road NE., MS-E74, Atlanta, GA 30329; telephone 866-426-3673 (this is a toll-free number). Information requests may also be submitted by email to<E T="03">wtcpublicinput@cdc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This preamble is organized as follows:</P>
        <EXTRACT>
          
          <FP SOURCE="FP-2">I. Public Participation</FP>
          <FP SOURCE="FP-2">II. Background</FP>
          <FP SOURCE="FP1-2">A. WTC Health Program Statutory Authority</FP>
          <FP SOURCE="FP1-2">B. Addition of New Health Conditions for Coverage in the WTC Health Program</FP>
          <FP SOURCE="FP-2">III. Summary of the Final Rule and Response to Comments</FP>
          <FP SOURCE="FP-2">IV. Regulatory Assessment Requirements</FP>
          <FP SOURCE="FP1-2">A. Executive Order 12866 and Executive Order 13563</FP>
          <FP SOURCE="FP1-2">B. Regulatory Flexibility Act</FP>
          <FP SOURCE="FP1-2">C. Paperwork Reduction Act</FP>
          <FP SOURCE="FP1-2">D. Small Business Regulatory Enforcement Fairness Act</FP>
          <FP SOURCE="FP1-2">E. Unfunded Mandates Reform Act of 1995</FP>
          <FP SOURCE="FP1-2">F. Executive Order 12988 (Civil Justice)</FP>
          <FP SOURCE="FP1-2">G. Executive Order 13132 (Federalism)</FP>
          <FP SOURCE="FP1-2">H. Executive Order 13045 (Protection of Children From Environmental Health Risks and Safety Risks)</FP>
          <FP SOURCE="FP1-2">I. Executive Order 13211 (Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use)</FP>
          <FP SOURCE="FP1-2">J. Plain Writing Act of 2010</FP>
          <FP SOURCE="FP-2">V. Final Rule</FP>
        </EXTRACT>
        <HD SOURCE="HD1">I. Public Participation</HD>

        <P>HHS received comments from six individuals and organizations on the notice of proposed rulemaking published in the<E T="04">Federal Register</E>on July 1, 2011 (76 FR 38938). One anonymous commenter expressed anger about the WTC Health Program's cost to American taxpayers; another individual asked that leukemia and other blood cancers be added to the list of WTC-related health conditions; and a physician experienced with treating WTC-related health conditions requested that a mental disorder be added to the list of WTC-related health conditions. Those comments are outside the scope of this rulemaking and could not be considered. HHS received substantive comments from the New York State Laborers' Health &amp; Safety Trust Fund, the Communication Workers of America, and the WTC Health Program Survivor Steering Committee. Those comments are described and addressed below.</P>
        <HD SOURCE="HD1">II. Background</HD>
        <HD SOURCE="HD2">A. WTC Health Program Statutory Authority</HD>
        <P>Title I of the James Zadroga 9/11 Health and Compensation Act of 2010 (Pub. L. 111-347), amended the Public Health Service Act (PHS Act) to add Title XXXIII<SU>1</SU>
          <FTREF/>establishing the WTC Health Program within HHS. HHS issued an interim final rule on July 1, 2011 (76 FR 38914), which codified the Program in 42 CFR Part 88. Sections 88.1 through 88.16 were included in that rulemaking; this final rule establishing § 88.17 was developed in a separate rulemaking.</P>
        <FTNT>
          <P>
            <SU>1</SU>Title XXXIII of the Public Health Service Act is codified at 42 U.S.C. 300mm to 300mm-61. Those portions of the Zadroga Act found in Titles II and III of Public Law 111-347 do not pertain to the World Trade Center Health Program and are codified elsewhere.</P>
        </FTNT>
        <P>The WTC Health Program provides medical monitoring and treatment benefits to eligible firefighters and related personnel, law enforcement officers, and rescue, recovery and cleanup workers (including those who are Federal employees) who responded to the September 11, 2001, terrorist attacks, and to eligible survivors of the New York City attacks. The WTC Health Program will expand to include eligible firefighters and related personnel, law enforcement officers, and rescue, recovery and cleanup workers who responded to the September 11, 2001, terrorist attacks at the Pentagon and Shanksville, PA. The WTC Program Administrator has gathered information that may serve as a basis for such enrollment, and is working to develop eligibility criteria for these responder groups.</P>
        <P>All references to the WTC Program Administrator in this notice mean the NIOSH Director or his or her designee.</P>
        <P>Title XXXIII of the PHS Act authorizes the WTC Program Administrator to establish a process by which health conditions, including cancer, may be considered for addition to the list of WTC-related health conditions. This final rule establishes this process.</P>
        <HD SOURCE="HD2">B. Addition of New Health Conditions for Coverage in the WTC Health Program</HD>
        <P>The list of WTC-related health conditions defined in sections 3312 and 3322 of Title XXXIII of the PHS Act may be amended in the future to add other conditions for which exposure to airborne toxins, any other hazard, or any other adverse condition resulting from the September 11, 2001, terrorist attacks, based on an examination by a medical professional with experience in treating or diagnosing the health conditions included in the applicable list of WTC-related health conditions, is substantially likely to be a significant factor in aggravating, contributing to, or causing the illness or condition (Title XXXIII, Sec. 3312(a)(1)(A)(i)).</P>

        <P>Procedures for the addition of a new condition are established in this final rule. The addition of a new condition<PRTPAGE P="24629"/>could be initiated either by petition from an interested party or at the discretion of the WTC Program Administrator, as specified in this final rule.</P>
        <HD SOURCE="HD1">III. Summary of Final Rule and Response to Comments</HD>
        <HD SOURCE="HD2">Section 88.1Definitions</HD>
        <P>This amendment to Part 88 would add the definition of “interested party” to the list of definitions established by interim final rule on July 1, 2011 (76 FR 38914).</P>
        <P>
          <E T="03">Comment:</E>HHS received two comments requesting that the definition of “interested party” be expanded to reference survivor organizations.</P>
        <P>
          <E T="03">HHS response:</E>The definition of “interested party” was taken directly from Title I of the James Zadroga 9/11 Health and Compensation Act of 2010. Although the statutory definition of “interested party” does not explicitly mention “survivor organizations,” HHS believes that the definition includes “survivor organizations.” HHS does not agree that amending the rule text is necessary and is therefore not amending the definition.</P>
        <HD SOURCE="HD2">Section 88.17Addition of Health Conditions to the List of WTC-Related Health Conditions</HD>
        <P>In accordance with the requirements specified in Title XXXIII of the PHS Act, § 88.17 establishes the process by which an interested party could petition the WTC Program Administrator to add a condition to the list of WTC-related health conditions identified in § 88.1. Under the provisions of § 88.17(a)(1), the petition must include the name and contact information of the interested party; the name and description of the condition the party would like the WTC Program Administrator to add to the list of WTC-related health conditions; and an explanation of the reasons for adding the condition, which must include the medical basis for the association between the September 11, 2001, terrorist attacks and the condition to be added.</P>
        <P>HHS has received some communications for which it is unclear whether the author intends to petition for the addition of a health condition or whether the author is expressing personal concerns. Since a petition results in Federal action, as specified under this rule, it is important that the intent to petition be unambiguous. Accordingly, HHS has amended the final rule text to clarify that the petition must state the petitioner's intent to petition for the addition of a health condition.</P>

        <P>The provisions of § 88.17(a)(2) incorporate specifications in Title XXXIII of the PHS Act regarding the addition of new conditions. Within 60 days of receipt of the petition, the WTC Program Administrator will either: request a recommendation of the WTC Health Program Scientific/Technical Advisory Committee (STAC); open the proposed condition to public comment by publishing a notice of proposed rulemaking (NPRM) in the<E T="04">Federal Register</E>; publish the WTC Program Administrator's determination not to publish an NPRM; or publish in the<E T="04">Federal Register</E>a determination that not enough evidence exists to perform any of the above actions. HHS has amended the final rule text to acknowledge that a petition may request the addition of more than one health condition.</P>
        <P>HHS has also inserted § 88.17(a)(4) into the final rule to clarify that the Administrator shall be required to reconsider a previously-considered (but not added) health condition for inclusion on the list of WTC-related health conditions in response to a petition only when the petition includes a new medical basis for the association between the terrorist attacks and the condition. A new medical basis could include a health study, whether original or updated, not previously considered by the WTC Program Administrator. A new clinical case report on a particular health condition which compiles data from one or more patients may not necessarily be considered a new medical basis if the Administrator has previously considered one or more cases of the health condition. The Administrator retains the discretion, however, to reconsider a health condition for any reason on his own initiative, with or without the receipt of a petition.</P>
        <P>
          <E T="03">Comment:</E>One commenter requested that all submitted petitions be shared with the STAC regardless of whether the WTC Program Administrator seeks a formal recommendation from the Committee.</P>
        <P>
          <E T="03">HHS response:</E>HHS appreciates this suggestion and agrees that, in the interest of keeping the STAC informed of relevant public interest, petitions received by the WTC Program Administrator will be shared with the Committee and with the public via the Program's Web site. HHS does not believe that amending the rule text is warranted.</P>
        <P>
          <E T="03">Comment:</E>A commenter also asked that a mechanism be developed to allow at least two members of the STAC to request to consider a petition and make a recommendation in the event that the WTC Program Administrator has determined not to publish an NPRM or where the Administrator determines that insufficient evidence exists to take action on a petition.</P>
        <P>
          <E T="03">HHS response:</E>According to the requirements of Title XXXIII of the PHS Act, the Committee's role is to review evidence and make recommendations to the WTC Program Administrator at the request of the Administrator, not to provide unsolicited reviews. Any work conducted by the STAC must be consistent with the purposes for which the Committee may be utilized as identified by the statute and the Committee charter. Therefore, this comment is not adopted.</P>
        <P>Subsection (b) also incorporates the statutory requirement that the WTC Program Administrator may publish an NPRM concerning the addition of a WTC-related health condition to the list. The Administrator would consider publishing an NPRM where the review of cancers required by Sec. 3312(a)(5)(A) of Title XXXIII of the PHS Act indicates that a type of cancer should be added, or where the review of WTC Health Program monitoring data reveals the prevalence of a condition not previously identified by the statute or Program. The protocol for such a review will take into account an evaluation of the exposure data associated with the terrorist attacks, and an evaluation of available epidemiologic, toxicologic, and medical evidence relevant to evaluating the possible association between the health condition under consideration and exposures associated with the September 11, 2001, terrorist attacks. How these various relevant sources of scientific and medical information will be evaluated, separately and in relation to each other, will depend on the evidence available for a given health condition under consideration. HHS notes that scientists generally look for consistency in terms of disease-mechanism theories, toxicologic and epidemiologic findings, and medical observation. The addition of any health condition requires rulemaking, and the public will have the opportunity to consider and comment on the review methods applied in any actual case.</P>

        <P>The WTC Program Administrator may extend the comment period described above based upon a finding of good cause. In the case of such an extension, the Administrator shall publish notice in the<E T="04">Federal Register</E>.</P>
        <P>
          <E T="03">Comment:</E>HHS received several comments concerning deadlines not specified in the regulatory text. One commenter suggested that HHS did not include every deadline related to the addition of a WTC-related health<PRTPAGE P="24630"/>condition provided by the statute. Two comments asked that we specify a time frame for the publication of an NPRM or a<E T="04">Federal Register</E>notice indicating that the WTC Program Administrator has determined not to publish an NPRM; one asked that we specify the publication of an NPRM 30 days following a STAC recommendation. Comments also requested that we specify a time frame for publication of a final rule; one asked that we require publication within 60 days after the close of an NPRM comment period.</P>
        <P>
          <E T="03">HHS response:</E>Each deadline specified by the PHS Act with regard to this matter has been incorporated into the regulatory text. We have specified a time frame for the publication of an NPRM following a STAC recommendation in Sec. 88.17(b)(2) according to the time frame specified in the statute. We agree with commenters who pointed out that we neglected to specify a time frame for publication of a<E T="04">Federal Register</E>notice indicating a decision not to publish an NPRM following receipt of a STAC recommendation, and have amended the rule text accordingly. However, Congress did not specify a time frame for publication of a final rule. HHS is concerned that establishing such requirements by regulation could negatively impact the thorough review of scientific evidence supporting or opposing the inclusion of a specific health condition. Because of the need to ensure that a thorough review has been conducted in all cases, HHS is not making changes to the rule based on these comments. Every effort will be made to promptly review public comments and STAC recommendations, and that publication of a final rule will occur in as efficient and timely a manner as is possible.</P>
        <P>
          <E T="03">Comment:</E>One commenter requested that HHS develop procedures for the WTC Program Administrator to notify an individual when a new condition is added, if the individual was previously denied coverage for that condition.</P>
        <P>
          <E T="03">HHS response:</E>Information about newly-added WTC-related health conditions will be provided on the WTC Health Program Web site and shared with all Program physicians. Program physicians would be best placed to advise individuals on whether applying for certification of a newly-designated WTC-related health condition is appropriate. The WTC Health Program will consider this request further to identify other ways in which Program participants may be notified of a new WTC-related health condition.</P>
        <HD SOURCE="HD1">IV. Regulatory Assessment Requirements</HD>
        <HD SOURCE="HD2">A. Executive Order 12866 and Executive Order 13563</HD>
        <P>Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives of significant regulatory actions 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.</P>
        <P>This final rule is considered a “significant regulatory action” within the meaning of E.O. 12866. The rule establishes processes by which the WTC Program Administrator may consider the addition of health conditions to the current statutory list of WTC-related health conditions covered by this program. This strictly procedural rule does not itself propose the addition of any conditions and hence it does not provide for any benefits nor impose any costs, other than the minor incidental administrative costs to HHS of considering possible additions. Under any circumstance, HHS would be required to conduct rulemaking to make an addition, as required by Title XXXIII of the PHS Act. Accordingly, any quantifiable costs and benefits associated with adding a condition would be addressed in such future rulemaking.</P>
        <P>This rule does not adversely affect in a material way the economy, a sector of the economy, productivity, jobs, the environment, public health or safety, or State, local, or Tribal governments or communities; it does not create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; it does not materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; nor does it raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in E.O. 12866.</P>
        <HD SOURCE="HD2">B. Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act (RFA), 5 U.S.C. 601<E T="03">et seq.</E>, requires each agency to consider the potential impact of its regulations on small entities including small businesses, small governmental units, and small not-for-profit organizations. HHS believes that this rule has “no significant economic impact upon a substantial number of small entities” within the meaning of the Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>).</P>
        <P>This regulation has no impact on small businesses or other small entities as specified under the RFA. The rule establishes procedures by which the WTC Health Program Administrator may consider the addition of health conditions to the current statutory list of WTC-related health conditions covered by this program. These procedures do not impose any requirements or direct costs on small entities. They do not involve small entities, except that a small entity could potentially be considered an “interested party” under these procedures, eligible to petition the WTC Program Administrator for the addition of a health condition.</P>
        <P>The Secretary of HHS has certified to the Chief Counsel, Office of Advocacy of the Small Business Administration, that this rule does not have a significant impact on a substantial number of small entities. Accordingly, no regulatory impact analysis is required.</P>
        <HD SOURCE="HD2">C. Paperwork Reduction Act</HD>
        <P>HHS has determined that this final rule contains data collection and record keeping requirements that are subject to review by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1955 (44 U.S.C. 3501-3420). A description of these provisions is given below with an estimate of the annual reporting burden. Included in the estimate of the annual reporting burden is the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing each collection of information. These data collection and record keeping requirements have been approved under OMB control number 0920-0929, exp. April 30, 2015.</P>
        <P>
          <E T="03">Project:</E>Adding a Health Condition to the Statutory List of WTC-Related Health Conditions (42 CFR 88.17)—New—National Institute for Occupational Safety and Health (NIOSH), Centers for Disease Control and Prevention (CDC).</P>
        <P>
          <E T="03">Background and Brief Description:</E>Title I of the James Zadroga Health and Compensation Act of 2010 amended the Public Health Service Act (PHS Act) to establish the World Trade Center (WTC) Health Program. Sections 3311, 3312, and 3321 of Title XXXIII of the PHS Act require that the WTC Program Administrator develop regulations to implement portions of the WTC Health Program established within the Department of Health and Human<PRTPAGE P="24631"/>Services (HHS). This final rule establishes the processes by which the WTC Program Administrator may add a new condition to the list of WTC-related health conditions through rulemaking, including a process for considering petitions by interested parties to add a new condition; the process will be codified at 42 CFR 88.17.</P>
        <P>Section 88.17, entitled “Addition of Health Conditions to the List of WTC-Related Health Conditions,” describes the process and data collection requirements that an interested party should follow to petition the WTC Program Administrator to add a condition to the list of WTC-related health conditions. HHS expects to receive no more than 100 petitions annually. We assume that interested parties will be enrolled WTC responders, screening-eligible survivors, certified-eligible survivors, or members of groups who advocate on behalf of responders or survivors. We estimate that an individual will spend an average of 40 hours gathering information to substantiate a request to add a health condition and assembling the petition. HHS requests input from the public on these estimates, which are reflected in the table below. The total burden on the public is estimated to be 4,000 hours.</P>
        <GPOTABLE CDEF="s50,r50,12C,12C,12C" COLS="5" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Type of respondent</CHED>
            <CHED H="1">Form name</CHED>
            <CHED H="1">Number of<LI>respondents</LI>
            </CHED>
            <CHED H="1">Number of<LI>responses</LI>
              <LI>per</LI>
              <LI>respondent</LI>
            </CHED>
            <CHED H="1">Average<LI>burden per</LI>
              <LI>response</LI>
              <LI>(in hours)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Responder/Survivor/Advocate</ENT>
            <ENT>Petition for the addition of health conditions</ENT>
            <ENT>100</ENT>
            <ENT>1</ENT>
            <ENT>40</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD2">D. Small Business Regulatory Enforcement Fairness Act</HD>
        <P>As required by Congress under the Small Business Regulatory Enforcement Fairness Act of 1996 (5 U.S.C. 801 et seq.), HHS will report the promulgation of this rule to Congress prior to its effective date.</P>
        <HD SOURCE="HD2">E. Unfunded Mandates Reform Act of 1995</HD>

        <P>Title II of the Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531<E T="03">et seq.</E>) directs agencies to assess the effects of Federal regulatory actions on State, local, and Tribal governments, and the private sector “other than to the extent that such regulations incorporate requirements specifically set forth in law.” For purposes of the Unfunded Mandates Reform Act, this final rule does not include any Federal mandate that may result in increased annual expenditures in excess of $100 million by State, local or Tribal governments in the aggregate, or by the private sector. For 2011, the inflation adjusted threshold is $136 million.</P>
        <HD SOURCE="HD2">F. Executive Order 12988 (Civil Justice)</HD>
        <P>This final rule has been drafted and reviewed in accordance with Executive Order 12988, “Civil Justice Reform,” and will not unduly burden the Federal court system. This rule has been reviewed carefully to eliminate drafting errors and ambiguities.</P>
        <HD SOURCE="HD2">G. Executive Order 13132 (Federalism)</HD>
        <P>HHS has reviewed this final rule in accordance with Executive Order 13132 regarding federalism, and has determined that it does not have “federalism implications.” The rule does not “have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.”</P>
        <HD SOURCE="HD2">H. Executive Order 13045 (Protection of Children From Environmental Health Risks and Safety Risks)</HD>
        <P>In accordance with Executive Order 13045, HHS has evaluated the environmental health and safety effects of this rule on children. HHS has determined that the rule would have no environmental health and safety effect on children.</P>
        <HD SOURCE="HD2">I. Executive Order 13211 (Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use)</HD>
        <P>In accordance with Executive Order 13211, HHS has evaluated the effects of this final rule on energy supply, distribution or use, and has determined that the rule will not have a significant adverse effect.</P>
        <HD SOURCE="HD2">J. Plain Writing Act of 2010</HD>
        <P>Under Public Law 111-274 (October 13, 2010), executive Departments and Agencies are required to use plain language in documents that explain to the public how to comply with a requirement the Federal Government administers or enforces. HHS has attempted to use plain language in promulgating the final rule consistent with the Federal Plain Writing Act guidelines.</P>
        <HD SOURCE="HD1">V. Final Rule</HD>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 42 CFR Part 88</HD>
          <P>Aerodigestive disorders, Appeal procedures, Health care, Mental health conditions, Musculoskeletal disorders, Respiratory and pulmonary diseases.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Text of the Rule</HD>
        <P>For the reasons discussed in the preamble, the Department of Health and Human Services amends 42 CFR part 88 as follows:</P>
        <REGTEXT PART="88" TITLE="42">
          <AMDPAR>1. The authority citation for part 88 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 300mm-300mm-61, Pub. L. 111-347, 124 Stat. 3623.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="88" TITLE="42">
          <AMDPAR>2. Amend § 88.1 by adding the definition of “interested party” in alphabetical order to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 88.1</SECTNO>
            <SUBJECT>Definitions.</SUBJECT>
            <STARS/>
            <P>
              <E T="03">Interested party</E>means a representative of any organization representing WTC responders, a nationally recognized medical association, a WTC Health Program Clinical Center of Excellence or Data Center, a State or political subdivision, or any other interested person.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="88" TITLE="42">
          <AMDPAR>3. Add § 88.17 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 88.17</SECTNO>
            <SUBJECT>Addition of health conditions to the list of WTC-related health conditions.</SUBJECT>
            <P>(a) Any interested party may petition the WTC Program Administrator to add a condition to the list of WTC-related health conditions.</P>
            <P>(1) Each petition shall state an intent to petition and be sent to the WTC Program Administrator. The petition shall include:</P>
            <P>(i) Name and contact information of the interested party;</P>
            <P>(ii) Name and description of the condition(s) to be added; and</P>
            <P>(iii) Reasons for adding the condition(s), including the medical basis for the association between the September 11, 2001, terrorist attacks and the condition(s) to be added.</P>
            <P>(2) Not later than 60 days after the receipt of a petition, the WTC Program Administrator shall:</P>

            <P>(i) Request a recommendation of the WTC Health Program Scientific/Technical Advisory Committee; or<PRTPAGE P="24632"/>
            </P>
            <P>(ii) Publish in the<E T="04">Federal Register</E>a proposed rule to add such health condition; or</P>
            <P>(iii) Publish in the<E T="04">Federal Register</E>the WTC Program Administrator's determination not to publish a proposed rule and the basis for that determination; or</P>
            <P>(iv) Publish in the<E T="04">Federal Register</E>a determination that insufficient evidence exists to take action under paragraph (a)(2)(i) through (iii) of this section.</P>

            <P>(3) The WTC Program Administrator may consider more than one petition simultaneously when the petitions propose the addition of the same health condition. Scientific/Technical Advisory Committee recommendations and<E T="04">Federal Register</E>notices initiated by the WTC Program Administrator pursuant to paragraph (a)(2) of this section may respond to more than one petition.</P>
            <P>(4) The WTC Program Administrator shall be required to consider a new petition for a health condition previously reviewed by the WTC Program Administrator and determined not to qualify for addition to the list of WTC-related health conditions only if the new petition presents a new medical basis (i.e., not previously reviewed) for the association between the September 11, 2001, terrorist attacks and the condition to be added.</P>

            <P>(b) The WTC Program Administrator may propose to add a condition to the list of WTC-related health conditions by publishing a proposed rule in the<E T="04">Federal Register</E>and providing interested parties a period of 30 days to submit written comments. The WTC Program Administrator may extend the comment period for good cause.</P>

            <P>(1) If the WTC Program Administrator requests a recommendation from the WTC Health Program Scientific/Technical Advisory Committee, the Advisory Committee shall submit its recommendation to the WTC Program Administrator no later than 60 days after the date of the transmission of the request or no later than a date specified by the Administrator (but not more than 180 days after the request). If the WTC Program Administrator decides to publish a proposed rule or a determination not to publish a proposed rule in the<E T="04">Federal Register</E>, he or she shall do so no later than 60 days after the date of transmission of the Advisory Committee recommendation.</P>
            <P>(2) [Reserved]</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: January 26, 2012.</DATED>
          <NAME>Kathleen Sebelius,</NAME>
          <TITLE>Secretary, Department of Health and Human Services.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9425 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
        <CFR>47 CFR Part 14</CFR>
        <DEPDOC>[CG Docket No. 10-213 and 10-145, WT Docket No. 96-198; FCC 11-151]</DEPDOC>
        <SUBJECT>Implementing the Provisions of the Communications Act of 1934, as Enacted by the Twenty-First Century Communications and Video Accessibility Act of 2010</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Communications Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule; announcement of effective date.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>In this document, the Commission announces that the Office of Management and Budget (OMB) has approved, for a period of three years, the information collection associated with the Commission's document Implementing the Provisions of the Communications Act of 1934, as Enacted by the Twenty-First Century Communications and Video Accessibility Act of 2010, (<E T="03">Report and Order</E>). This notice is consistent with the<E T="03">Report and Order,</E>which stated that the Commission would publish a document in the<E T="04">Federal Register</E>announcing the effective date of those rules.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>The amendments to 47 CFR 14.5, 14.20(d), 14.31, 14.32, and 14.34 through 14.52, published at 76 FR 82354, December 30, 2011, are effective April 25, 2012.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Rosaline Crawford, Disability Rights Office, Consumer and Governmental Affairs Bureau, at (202) 418-2075, or email<E T="03">Rosaline.Crawford@fcc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>This document announces that, on April 16, 2012, OMB approved, for a period of three years, the information collection requirements contained in the Commission's<E T="03">Report and Order,</E>FCC 11-151, published at 76 FR 82354, December 30, 2011. The OMB Control Number is 3060-1167. The Commission publishes this notice as an announcement of the effective date of the rules. If you have any comments on the burden estimates listed below, or how the Commission can improve the collections and reduce any burdens caused thereby, please contact Cathy Williams, Federal Communications Commission, Room 1-C823, 445 12th Street SW., Washington, DC 20554. Please include the OMB Control Number, 3060-1167, in your correspondence. The Commission will also accept your comments via the Internet if you send them to<E T="03">PRA@fcc.gov &lt;mailto:PRA@fcc.gov&gt;.</E>
        </P>

        <P>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 &lt;mailto:fcc504@fcc.gov&gt;</E>or call the Consumer and Governmental Affairs Bureau at (202) 418-0530 (voice), (202) 418-0432 (TTY).</P>
        <HD SOURCE="HD1">Synopsis</HD>
        <P>As required by the Paperwork Reduction Act of 1995 (44 U.S.C. 3507), the FCC is notifying the public that it received OMB approval on April 16, 2012, for the information collection requirements contained in the Commission's rules at 47 CFR 14.5, 14.20(d), 14.31, 14.32, and 14.34 through 14.52.</P>
        <P>Under 5 CFR 1320, an agency may not conduct or sponsor a collection of information unless it displays a current, valid OMB Control Number.</P>
        <P>No person shall be subject to any penalty for failing to comply with a collection of information subject to the Paperwork Reduction Act that does not display a current, valid OMB Control Number. The OMB Control Number is 3060-1167.</P>
        <P>The foregoing notice is required by the Paperwork Reduction Act of 1995, Pub. L. 104-13, October 1, 1995, and 44 U.S.C. 3507.</P>
        <P>The total annual reporting burdens and costs for the respondents are as follows:</P>
        <P>
          <E T="03">OMB Control Number:</E>3060-1167.</P>
        <P>
          <E T="03">OMB Approval Date:</E>April 16, 2012.</P>
        <P>
          <E T="03">OMB Expiration Date:</E>April 30, 2015.</P>
        <P>
          <E T="03">Title:</E>Accessible Telecommunications and Advanced Communications Services and Equipment.</P>
        <P>
          <E T="03">Form Number:</E>N/A.</P>
        <P>
          <E T="03">Type of Review:</E>New collection.</P>
        <P>
          <E T="03">Respondents:</E>Individuals or households; businesses or other for-profit entities; not-for-profit institutions.</P>
        <P>
          <E T="03">Number of Respondents and Responses:</E>9,454 respondents; 119,660 responses.</P>
        <P>
          <E T="03">Estimated Time per Response:</E>.50 to 40 hours.</P>
        <P>
          <E T="03">Frequency of Response:</E>Annual, one time, and on occasion reporting requirements; recordkeeping requirement; third-party disclosure requirement.</P>
        <P>
          <E T="03">Obligation to Respond:</E>Mandatory. Statutory authority for this information<PRTPAGE P="24633"/>collection is contained in sections 1-4, 255, 303(r), 403, 503, 716, 717, and 718 of the Act, 47 U.S.C. 151-154, 255, 303(r), 403, 503, 617, 618, and 619.</P>
        <P>
          <E T="03">Total Annual Burden:</E>408,695 hours.</P>
        <P>
          <E T="03">Total Annual Cost:</E>$110,588.</P>
        <P>
          <E T="03">Nature and Extent of Confidentiality:</E>Confidentiality is an issue to the extent that individuals and households provide personally identifiable information, which is covered under the FCC's system of records notice (SORN), FCC/CGB-1, “Informal Complaints and Inquiries.” As required by the Privacy Act, 5 U.S.C. 552a, the Commission also published a SORN, FCC/CGB-1 “Informal Complaints and Inquiries,” in the<E T="04">Federal Register</E>on December 15, 2009 (74 FR 66356) which became effective on January 25, 2010.</P>
        <P>In addition, upon the service of an informal or formal complaint, a service provider or equipment manufacturer must produce to the Commission, upon request, records covered by 47 CFR 14.31 of the Commission's rules and may assert a statutory request for confidentiality for these records. All other information submitted to the Commission pursuant to Subpart D of Part 14 of the Commission's rules or to any other request by the Commission may be submitted pursuant to a request for confidentiality in accordance with 47 CFR 0.459 of the Commission's rules.</P>
        <P>
          <E T="03">Privacy Impact Assessment:</E>Yes. The Privacy Impact Assessment (PIA) was completed on June 28, 2007. It may be reviewed at:<E T="03">&lt;http://www.fcc.gov/omd/privacyact/Privacy_Impact_Assessment.html&gt;.</E>The Commission is in the process of updating the PIA to incorporate various revisions made to the SORN.</P>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>The Commission will prepare a revision to the SORN and PIA to cover the PII collected related to this information collection, as required by OMB's Memorandum M-03-22 (September 26, 2003) and by the Privacy Act, 5 U.S.C. 552a.</P>
        </NOTE>
        <P>
          <E T="03">Needs and Uses:</E>On October 7, 2011, in document FCC 11-151, the Commission released a<E T="03">Report and Order</E>adopting final rules to implement sections 716 and 717 of the Communications Act of 1934 (the Act), as amended, which were added to the Act by the “Twenty-First Century Communications and Video Accessibility Act of 2010” (CVAA).<E T="03">See</E>Public Law 111-260, § 104. Section 716 of the Act requires providers of advanced communications services and manufacturers of equipment used for advanced communications services to make their services and equipment accessible to individuals with disabilities, unless doing so is not achievable.<E T="03">See</E>47 U.S.C. 617. Section 717 of the Act establishes new recordkeeping requirements and enforcement procedures for service providers and equipment manufacturers that are subject to sections 255, 716, and 718 of the Act.<E T="03">See</E>47 U.S.C. 618. Section 255 of the Act requires telecommunications and interconnected VoIP services and equipment to be accessible, if readily achievable.<E T="03">See</E>47 U.S.C. 255. Section 718 of the Act requires web browsers included on mobile phones to be accessible to and usable by individuals who are blind or have a visual impairment, unless doing so is not achievable.<E T="03">See</E>47 U.S.C. 619.</P>
        <P>Specifically, the rules adopted in document FCC 11-151 have the following possible related information collection requirements:</P>
        <P>(a) The rules adopted in document FCC 11-151 establish procedures for advanced communications service providers and equipment manufacturers to seek waivers from the accessibility obligations of section 716 of the Act and, in effect, waivers from the recordkeeping requirements and enforcement procedures of section 717 of the Act. Waiver requests may be submitted for individual or class offerings of services or equipment which are designed for multiple purposes, but are designed primarily for purposes other than using advanced communications services. All such waiver petitions will be put on public notice for comments and oppositions.</P>
        <P>(b) The CVAA and the rules adopted in document FCC 11-151 require service providers and equipment manufacturers that are subject to sections 255, 716, or 718 of the Act to maintain records of the following: (1) Their efforts to consult with people with disabilities; (2) descriptions of the accessibility features of their products and services; and (3) information about the compatibility of their products with peripheral devices or specialized customer premises equipment commonly used by individuals with disabilities to achieve access. These recordkeeping requirements are necessary to facilitate enforcement of accessibility obligations. Document FCC 11-151 provides flexibility by allowing covered entities to keep records in any format, recognizing the unique recordkeeping methods of individual entities. Because complaints regarding accessibility of a service or equipment may not occur for years after the release of the service or equipment, covered entities must keep records for two years from the date the service ceases to be offered to the public or the equipment ceases to be manufactured. Service providers and equipment manufacturers are not required to keep records of their consideration of achievability or the implementation of accessibility, but they must be prepared to carry their burden of proof in any enforcement proceeding, which requires greater than conclusory or unsupported claims.</P>
        <P>(c) The CVAA and the rules adopted in document FCC 11-151 require an officer of service providers and equipment manufacturers that are subject to sections 255, 716, or 718 of the Act to certify annually to the Commission that records are kept in accordance with the recordkeeping requirements. The certification must be supported with an affidavit or declaration under penalty of perjury, signed and dated by an authorized officer of the entity with personal knowledge of the representations provided in the company's certification, verifying the truth and accuracy of the information. The certification must also identify the name and contact details of the person or persons within the company that are authorized to resolve accessibility complaints, and the agent designated for service of process. The certification must be filed with the Consumer and Governmental Affairs Bureau on or before April 1 each year for records pertaining to the previous calendar year. The certification must be updated when necessary to keep the contact information current.</P>
        <P>(d) The Commission also established procedures in document FCC 11-151 to facilitate the filing of formal and informal complaints alleging violations of sections 255, 716, or 718 of the Act. Those procedures include a nondiscretionary pre-filing notice procedure to facilitate dispute resolution. As a prerequisite to filing an informal complaint, complainants must first request dispute assistance from the Consumer and Governmental Affairs Bureau's Disability Rights Office.</P>

        <P>The rules adopted in document FCC 11-151 temporarily exempt advanced communications service providers and equipment manufacturers from the accessibility obligations of section 716 of the Act and, in effect, from the recordkeeping requirements and enforcement procedures of section 717 of the Act, if they qualify as small business concerns under the Small Business Administration's (SBA) rules and size standards for the industry in which they are primarily engaged. These size standards are based on the maximum number of employees or maximum annual receipts of a business concern. The SBA categorizes industries for its size standards using the North<PRTPAGE P="24634"/>American Industry Classification System (NAICS).</P>
        <SIG>
          <FP>Federal Communications Commission.</FP>
          <NAME>Marlene H. Dortch,</NAME>
          <TITLE>Secretary, Office of the Secretary, Office of the Managing Director.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9912 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6712-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <CFR>50 CFR Part 660</CFR>
        <DEPDOC>[Docket No. 100804324-1265-02]</DEPDOC>
        <RIN>RIN 0648-BC11</RIN>
        <SUBJECT>Magnuson-Stevens Act Provisions; Fisheries off West Coast States; Biennial Specifications and Management Measures; Inseason Adjustments</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; inseason adjustments to biennial groundfish management measures; request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This final rule announces an inseason change to management measures in the Pacific Coast groundfish fisheries. This action, which is authorized by the Pacific Coast Groundfish Fishery Management Plan (FMP), is intended to allow fisheries to access more abundant groundfish stocks while protecting overfished and depleted stocks. This rule also implements changes to the incidental retention allowance for halibut in the primary sablefish fishery under the authority of the Northern Pacific Halibut Act.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective 0001 hours (local time) May 1, 2012. Comments on this final rule must be received no later than May 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by FDMS docket number NOAA-NMFS-2010-0194 by any one of the following methods:</P>
          <P>•<E T="03">Electronic Submissions:</E>Submit all electronic public comments via the Federal eRulemaking Portal<E T="03">http://www.regulations.gov.</E>
          </P>
          <P>•<E T="03">Fax:</E>206-526-6736, Attn: Colby Brady</P>
          <P>•<E T="03">Mail:</E>William W. Stelle, Jr., Regional Administrator, Northwest Region, NMFS, 7600 Sand Point Way NE., Seattle, WA 98115-0070, Attn: Colby Brady.</P>
          <P>
            <E T="03">Instructions:</E>All comments received are a part of the public record and will generally be posted to<E T="03">http://www.regulations.gov</E>without change. All Personal Identifying Information (for example, name, address, etc.) voluntarily submitted by the commenter may be publicly accessible. Do not submit Confidential Business Information or otherwise sensitive or protected information.</P>
          <P>NMFS will accept anonymous comments (enter N/A in the required fields, if you wish to remain anonymous). You may submit attachments to electronic comments in Microsoft Word, Excel, WordPerfect, or Adobe PDF file formats only.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Colby Brady (Northwest Region, NMFS), phone: 206-526-6117, fax: 206-526-6736,<E T="03">colby.brady@noaa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Electronic Access</HD>

        <P>This final rule is accessible via the Internet at the Office of the Federal Register's Web site at<E T="03">http://www.gpo.gov/fdsys/search/home.action.</E>Background information and documents are available at the Pacific Fishery Management Council's Web site at<E T="03">http://www.pcouncil.org/.</E>
        </P>
        <HD SOURCE="HD1">Background</HD>
        <P>The Pacific Coast Groundfish FMP and its implementing regulations at title 50 in the Code of Federal Regulations (CFR), part 660, subparts C through G, regulate fishing for over 90 species of groundfish off the coasts of Washington, Oregon, and California. Groundfish specifications and management measures are developed by the Pacific Fishery Management Council (Council), and are implemented by NMFS.</P>
        <P>On November 3, 2010, NMFS published a proposed rule to implement the 2011-2012 harvest specifications and management measures for most species of the Pacific Coast groundfish fishery (75 FR 67810). The final rule to implement the 2011-12 harvest specifications and management measures for most species of the Pacific Coast Groundfish Fishery was published on May 11, 2011 (76 FR 27508). This final rule was subsequently amended by several inseason actions (76 FR 39313, 76 FR 67092, 76 FR 79122, 77 FR 12503, 77 FR 22679). On September 27, 2011, NMFS published a proposed rule to implement final 2012 specifications for overfished species and assessed flatfish species pursuant to Secretarial Amendment 1 to the Groundfish FMP (76 FR 59634). That final rule was effective January 1, 2012. These specifications and management measures are codified in the CFR (50 CFR part 660, subparts C through G).</P>
        <P>Changes to current groundfish management measures implemented by this action were recommended by the Council, in consultation with Pacific Coast Treaty Indian Tribes and the States of Washington, Oregon, and California, at its April 1-April 6, 2012 meeting. The Council recommended adjusting the biennial groundfish management measures for the remainder of the biennial period to respond to updated fishery information and additional inseason management needs. The adjustment to fishery management measures are not expected to result in greater impacts to overfished species than originally projected through the end of 2012. Estimated mortality of overfished and target species are the result of management measures designed to achieve, to the extent possible, but not exceed, annual catch limits (ACLs) of target species while fostering the rebuilding of overfished stocks by remaining within their rebuilding ACLs.</P>
        <HD SOURCE="HD1">Limited Entry Fixed Gear Fishery Management Measures</HD>
        <HD SOURCE="HD2">Sablefish Daily Trip Limit Fishery</HD>

        <P>In 2011, the amount of sablefish harvested in the limited entry fixed gear sablefish daily trip limit (DTL) fishery North of 36° N. lat. exceeded its sablefish allocation by 60 mt above its collective target (the northern DTL fixed gear share). This did not impact the northern sablefish ACL, since the rationalized Individual Fishing Quota (IFQ) trawl fishery left 148 mt of sablefish un-harvested in the northern area. However, it is expected that since the IFQ fishery participants have one full year of experience in the IFQ fishery, then higher sablefish allocation attainments will be attained, in which case another overage by the northern LE fixed gear could possibly exceed the northern sablefish ACL. To ensure that harvest opportunities for this healthy stock do not exceed the northern LE fixed gear share allocation, the Council considered decreases to trip limits for sablefish in this fishery and the potential impacts on overall catch levels. Landings projections were made by the Council advisory Groundfish Management Team (GMT) for the northern LE fixed gear fishery under the current 2012 trip limit scenario, which projected an overage in the LE North fishery of 16%, or 43 mt. Projections for the other three fixed gear sablefish fisheries were tracking within their targets for 2012.<PRTPAGE P="24635"/>
        </P>
        <P>Therefore, the Council recommended and NMFS is implementing trip limit changes for the limited entry fixed gear fishery North of 36° N. lat. that decrease sablefish DTL fishery limits from “1,300 lb (590 kg) per week, not to exceed 5,000 lb (2,268 kg) of per 2 months” to “1,000 lb (454 kg) per week, not to exceed 4,000 lb (1,814 kg) per 2 months” beginning in period 3, May 1, 2012 through the end of the year. This decrease in trip limits is not anticipated to increase projected impacts to overfished species.</P>
        <HD SOURCE="HD2">Incidental Halibut Retention</HD>
        <P>The International Pacific Halibut Commission (IPHC) establishes total allowable catch (TAC) amounts for Pacific halibut each year in January. Under the authority of the Northern Pacific Halibut Act, and implementing regulations at 50 CFR 300.63, a catch sharing plan, developed by the Pacific Council and implemented by the Secretary, allocates portions of the annual TAC among fisheries off Washington, Oregon, and California. The catch sharing plan for Pacific halibut fisheries in Area 2A (waters off the U.S. West coast) allows an incidental total catch limit for halibut for the 2012 sablefish primary season (i.e. tier limit fishery) of 21,173 lb (9,604 kg). This total catch limit of 21,173 lb (9,604 kg) in 2012 is higher than what has been available to the sablefish primary fishery in recent years (2010-11), which was not high enough to justify an incidental catch limit of halibut in the sablefish primary fishery north of Pt. Chehalis, WA (46°53.30′ N. lat.). The retention limits for halibut were not revised as part of the 2011-2012 harvest specifications and management measures because the Total Allowable Catch of halibut for 2012 was not determined until the IPHC meeting in January, 2012. Although the International Pacific Halibut Commission (IPHC) recommended coast-wide catch limits for 2012 totaled 33,540,000 lb (15,213,488 kg), which is a coast-wide decrease of 18.3% from the 2011 catch limit of 41,070,000 lb. (18,629,038 kg), the area 2A allocation increased 8% from 910,000 lb. (412,769 kg) in 2011 to 989,000 lb. (448,603 kg) for 2012. Due to the increase in the Pacific halibut TAC for area 2A, and the resulting increase in the amount of Pacific halibut available to the sablefish primary fishery as incidental take, the Council considered options to revise the catch ratio established in the groundfish regulations at 50 CFR 660.231 at their first opportunity, the March 2012 meeting. These options were developed to reduce incidental impacts to Pacific halibut in the sablefish primary fishery, and stay below the lower 2012 Pacific halibut allocation. After the opportunity for public review and comment, the Council, at their April meeting, made their final recommendation for adjusting the incidental retention limits for Pacific halibut in the sablefish primary fishery in order to allow incidental take and keep mortality of halibut below the 2012 catch limit of 21,173 lb (9,604 kg).</P>
        <P>In order to allow incidental halibut catch in the sablefish primary fishery, which is currently not allowed, the Council recommended and NMFS is implementing incidental halibut retention regulations at 50 CFR 660.231(b)(3)(iv) to read as follows: “50 lb (23 kg) dressed weight of halibut for every 1,000 pounds (454 kg) dressed weight of sablefish landed and up to 2 additional halibut in excess of the 50-pounds-per-1,000-pound ratio per landing.”NMFS in including enforcement related provisions recommended by the Council in 2009, the last time an incidental allowance was allowed. Consequently, the landing requirement applies also to possession, and the term “dressed” is described to mean halibut landed eviscerated with their heads on.</P>
        <HD SOURCE="HD1">Classification</HD>
        <P>These actions are taken under the authority of 50 CFR 660.60(c) and 50 CFR 300.63(b)(3) and are exempt from review under Executive Order 12866.</P>

        <P>These increases in sablefish limits are taken under the authority of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act), and are in accordance with 50 CFR part 660, the regulations implementing the FMP. The adjustment to the halibut incidental catch limit in the sablefish primary fishery is taken under the authority of the Northern Pacific Halibut Act and implementing regulations, and is consistent with the approved catch sharing plan. These actions are based on the most recent data available. The aggregate data upon which these actions are based are available for public inspection at the Office of the Administrator, Northwest Region, NMFS, (see<E T="02">ADDRESSES</E>) during business hours.</P>
        <P>This final rule makes routine inseason adjustments to groundfish fishery management measures based on the best available information and is taken pursuant to the regulations implementing the Pacific Coast Groundfish FMP.</P>
        <P>For the following reasons, NMFS finds good cause to waive prior public notice and comment on the revisions to groundfish management measures under 5 U.S.C. 553(b) because notice and comment would be impracticable and contrary to the public interest. Also, for the same reasons, NMFS finds good cause to waive the 30-day delay in effectiveness pursuant to 5 U.S.C. 553(d)(3), so that this final rule may become effective May 1, 2012.</P>
        <P>For the following reasons, NMFS finds good cause to waive prior public notice and comment on the revisions to groundfish management measures under 5 U.S.C. 553(b)(3)(B) because notice and comment would be impracticable and contrary to the public interest. Also, for the same reasons, NMFS finds good cause to waive the 30-day delay in effectiveness pursuant to 5 U.S.C. 553(d)(3), so that this final rule may become effective May 1, 2012.</P>
        <P>The recently available information upon which the changes to the incidental halibut retention in the sablefish primary fishery north of Pt. Chehalis, WA (46°53.30′ N. lat.), and the subsequent proposed management measure changes are based were originally provided to the Council, and the Council made its potential recommendations available for public comment, at its March 2-7, 2012 meeting. The Council considered the public comments on this matter as well as additional recently available information upon which the changes to the limited entry fixed gear sablefish trip limits North of 36° N. lat. at its April 1-6, 2012 meeting. At the April Council meeting, the Council recommended that these changes be implemented by May 1, 2012. There was not sufficient time after that meeting to draft this document and undergo proposed and final rulemaking before these actions need to be in effect. For the actions to be implemented in this final rule, affording the time necessary for prior notice and opportunity for public comment would prevent NMFS from managing fisheries using the best available science to approach, without exceeding, the ACLs for federally managed species in accordance with the FMP and applicable laws. The adjustments to management measures in this document affect commercial fisheries off northern California to Washington State. These adjustments to management measures must be implemented in a timely manner, by May 1, 2012, to: Allow fishermen an opportunity to harvest their limits in 2012 for sablefish, and allow incidental catch of halibut in the sablefish primary fishery to keep impacts below the 2012 halibut Area 2A allocation.</P>

        <P>Decreases to the sablefish cumulative limits in the limited entry fixed gear<PRTPAGE P="24636"/>fishery continue to allow fishermen opportunities to harvest available healthy stocks while staying within the ACLs for these species. Furthermore, these adjustments to management measures must be implemented in a timely manner to allow limited entry primary sablefish fishermen North of Pt. Chehalis, WA (46°53.30′ N. lat.) to prosecute their intended sablefish fishing strategies while accessing a portion of incidental halibut bycatch in a manner that is consistent with the 2A catch sharing plan. If this rule is not implemented immediately, the public could have incorrect information regarding allowed limited entry fixed gear sablefish trip limits, and allowed fishing activities for groundfish fisheries management, which would cause confusion and be inconsistent with the intent of the Council. It would be contrary to the public interest to delay implementation of these changes until after public notice and comment, because making this regulatory change by May 1, 2012, allows harvest as intended by the Council in fisheries that are important to coastal communities in a manner that prevents ACLs of overfished and target species from being exceeded. Furthermore, changes to the sablefish primary fishery regulations to allow incidental halibut retention limits for the sablefish primary fishery are necessary to reduce halibut impacts in area 2A, keeping total mortality of halibut below the 2012 area 2A allocation. These changes must be implemented in a timely manner by May 1, 2012, to allow sablefish fishermen sustainable incidental take in a manner that prevents early closure of the incidental halibut fishery. It would be contrary to the public interest to wait to implement these changes until after public notice and comment, because a delay in reducing retention limits could cause incidental halibut to be unavailable for harvest for as long as possible throughout the sablefish primary season, which runs through October 31.</P>
        <P>No aspect of this action is controversial and no change in operating practices in the fishery is required from those intended in this inseason adjustment.</P>
        <P>Delaying these changes would also keep management measures in place that are not based on the best available information. Such delay would impair achievement of the Pacific Coast Groundfish FMP objectives of providing for year-round harvest opportunities, extending fishing opportunities as long as practicable during the fishing year, or staying within ACLs or allocations for Pacific halibut.</P>
        <P>Accordingly, for the reasons stated above, NMFS finds good cause to partially waive prior notice and comment and the delay in effectiveness.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 50 CFR Part 660</HD>
          <P>Fisheries, Fishing, Indian fisheries.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: April 20, 2012.</DATED>
          <NAME>Galen Tromble,</NAME>
          <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
        <P>For the reasons set out in the preamble, 50 CFR part 660 is amended as follows:</P>
        <REGTEXT PART="660" TITLE="50">
          <PART>
            <HD SOURCE="HED">PART 660—FISHERIES OFF WEST COAST STATES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 660 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>16 U.S.C. 1801<E T="03">et seq.,</E>16 U.S.C. 773<E T="03">et seq.,</E>and 16 U.S.C. 7001<E T="03">et seq.</E>
            </P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="660" TITLE="50">
          <AMDPAR>2. In § 660.231, paragraph (b)(3)(iv) is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 660.231</SECTNO>
            <SUBJECT>Limited entry fixed gear sablefish primary fishery management.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>
            <P>(3) * * *</P>
            <P>(iv)<E T="03">Incidental halibut retention north of Pt. Chehalis, WA (46°53.30′ N. lat.).</E>From May 1 through October 31, vessels authorized to participate in the sablefish primary fishery, licensed by the International Pacific Halibut Commission for commercial fishing in Area 2A (waters off Washington, Oregon, California), and fishing with longline gear north of Pt. Chehalis, WA (46°53.30′ N. lat.) may possess and land up to the following cumulative limits: 50 lb (23 kg) dressed weight of halibut for every 1,000 pounds (454 kg) dressed weight of sablefish landed and up to 2 additional halibut in excess of the 50-pounds-per-1,000-pound ratio per landing. “Dressed” halibut in this area means halibut landed eviscerated with their heads on. Halibut taken and retained in the sablefish primary fishery north of Pt. Chehalis may only be landed north of Pt. Chehalis and may not be possessed or landed south of Pt. Chehalis.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="660" TITLE="50">
          <AMDPAR>3. Table 2 (North) to part 660, Subpart E, is revised to read as follows:</AMDPAR>
          <BILCOD>BILLING CODE 3510-22-P</BILCOD>
          <GPH DEEP="587" SPAN="3">
            <PRTPAGE P="24637"/>
            <GID>ER25AP12.000</GID>
          </GPH>
        </REGTEXT>
        <REGTEXT PART="660" TITLE="50">
          <AMDPAR>4. Table 2 (South) to part 660, Subpart E, is revised to read as follows:</AMDPAR>
          <GPH DEEP="562" SPAN="3">
            <PRTPAGE P="24638"/>
            <GID>ER25AP12.001</GID>
          </GPH>
          <GPH DEEP="349" SPAN="3">
            <PRTPAGE P="24639"/>
            <GID>ER25AP12.002</GID>
          </GPH>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9963 Filed 4-20-12; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-C</BILCOD>
    </RULE>
  </RULES>
  <VOL>77</VOL>
  <NO>80</NO>
  <DATE>Wednesday, April 25, 2012</DATE>
  <UNITNAME>Proposed Rules</UNITNAME>
  <PRORULES>
    <PRORULE>
      <PREAMB>
        <PRTPAGE P="24640"/>
        <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Agricultural Marketing Service</SUBAGY>
        <CFR>7 CFR Part 930</CFR>
        <DEPDOC>[Doc. No. AMS-FV-11-0092; FV12-930-1 PR]</DEPDOC>
        <SUBJECT>Tart Cherries Grown in the State of Michigan, et al.; Increasing the Primary Reserve Capacity and Revising Exemption Requirements</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Agricultural Marketing Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This rule invites comments on proposed revisions to the primary inventory reserve capacity and the exemption provisions applicable to handler diversion activities prescribed under the marketing order for tart cherries (order). The order regulates the handling of tart cherries grown in the States of Michigan, New York, Pennsylvania, Oregon, Utah, Washington, and Wisconsin, and is administered locally by the Cherry Industry Administrative Board (Board). This action would increase the volume of tart cherries that can be placed in the primary inventory reserve from 50 million pounds to 100 million pounds and would revise exemption provisions by limiting diversion credits for new market development and market expansion activities to one year. These changes are intended to facilitate sales and lessen the impact of market expansion activities on volume restriction calculations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received by May 10, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Interested persons are invited to submit written comments concerning this proposal. Comments must be sent to the Docket Clerk, Marketing Order and Agreement Division, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington, DC 20250-0237; Fax: (202) 720-8938; or Internet:<E T="03">http://www.regulations.gov.</E>All comments should reference the document number and the date and page number of this issue of the<E T="04">Federal Register</E>and will be made available for public inspection in the Office of the Docket Clerk during regular business hours, or can be viewed at:<E T="03">http://www.regulations.gov.</E>All comments submitted in response to this rule will be included in the record and will be made available to the public. Please be advised that the identity of the individuals or entities submitting the comments will be made public on the Internet at the address provided above.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Jennie M. Varela, Marketing Specialist, or Christian D. Nissen, Regional Manager, Southeast Marketing Field Office, Marketing Order and Agreement Division, Fruit and Vegetable Programs, AMS, USDA; Telephone: (863) 324-3775, Fax: (863) 325-8793, or Email:<E T="03">Jennie.Varela@ams.usda.gov</E>or<E T="03">Christian.Nissen@ams.usda.gov.</E>
          </P>

          <P>Small businesses may request information on complying with this regulation by contacting Laurel May, Marketing Order and Agreement Division, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington, DC 20250-0237; Telephone: (202) 720-2491, Fax: (202) 720-8938, or Email:<E T="03">Laurel.May@ams.usda.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This proposal is issued under Marketing Order No. 930, as amended (7 CFR part 930), regulating the handling of tart cherries grown in the States of Michigan, New York, Pennsylvania, Oregon, Utah, Washington, and Wisconsin, hereinafter referred to as the “order.” The order is effective under the Agricultural Marketing Agreement Act of 1937, as amended (7 U.S.C. 601-674), hereinafter referred to as the “Act.”</P>
        <P>The Department of Agriculture (USDA) is issuing this rule in conformance with Executive Order 12866.</P>
        <P>This proposal has been reviewed under Executive Order 12988, Civil Justice Reform. This rule is not intended to have retroactive effect.</P>
        <P>The Act provides that administrative proceedings must be exhausted before parties may file suit in court. Under section 608c(15)(A) of the Act, any handler subject to an order may file with USDA a petition stating that the order, any provision of the order, or any obligation imposed in connection with the order is not in accordance with law and request a modification of the order or to be exempted therefrom. A handler is afforded the opportunity for a hearing on the petition. After the hearing, USDA would rule on the petition. The Act provides that the district court of the United States in any district in which the handler is an inhabitant, or has his or her principal place of business, has jurisdiction to review USDA's ruling on the petition, provided an action is filed not later than 20 days after the date of the entry of the ruling.</P>
        <P>This rule invites comments on proposed revisions to the primary inventory reserve capacity and the exemption provisions applicable to handler diversion activities prescribed under the order. This action would increase the volume of tart cherries that can be placed in the primary inventory reserve from 50 million pounds to 100 million pounds and would revise exemption provisions by limiting diversion credits for new market development and market expansion activities to one year. These changes are intended to facilitate sales and lessen the impact of new market development and market expansion activities on volume restriction calculations. These changes were recommended by the Board at its meetings on September 15, 2011, and November 2, 2011, respectively.</P>
        <P>Section 930.55 of the order provides authority for the establishment of a primary inventory reserve as part of the order's volume control provisions. Section 930.50(i) of the order establishes a cap of 50 million pounds on the primary inventory reserve, but provides authority to raise that limit if necessary, provided that any recommendation for change is made by the Board on or before September 30 to become effective for the following crop year.</P>

        <P>Section 930.59 of the order authorizes handler diversion. When volume regulation is in effect, handlers may fulfill any restricted percentage requirement in full or in part by acquiring diversion certificates or by voluntarily diverting cherries or cherry products in a program approved by the Board, rather than placing cherries in an inventory reserve. These eligible diversion activities include, in part, use for new market development and market expansion activities.<PRTPAGE P="24641"/>
        </P>
        <P>Section 930.159 of the order's administrative rules specifies methods of handler diversion, including using cherries or cherry products for exempt purposes prescribed under § 930.162. Section 930.162 establishes the terms and conditions of exemption that must be satisfied for handlers to receive diversion certificates for exempt uses. Section 930.162(b) defines the activities which qualify for exemptions including new market development and market expansion. New market development and market expansion activities include, but are not limited to, sales of cherries into markets that are not yet commercially established, product line extensions, or segmentation of markets along geographic or other definable characteristics.</P>
        <P>In July 2011, the Board established an ad hoc committee (committee) to examine the volume regulation process under the order and recommend changes that might benefit the industry. The committee made a series of recommendations, mostly administrative in nature, which were discussed by the entire Board at its September and November meetings. The recommended administrative changes were approved by the Board and the proposed changes to the primary reserve and diversion credits for market expansion activities, are the subject of this action.</P>
        <P>The order provides for the use of volume regulation to stabilize prices and improve grower returns during periods of oversupply. At the beginning of each season, the Board examines production and sales data to determine whether a volume regulation is necessary and if so, announces free and restricted percentages to limit the volume of tart cherries on the market. Free percentage cherries can be used to supply any available market, including domestic markets for pie filling, water packed, and frozen tart cherries. Restricted percentage cherries can be placed in reserve, marketed through exempt activities, including market expansion, or diverted in orchard or at the processing plant.</P>
        <P>When using reserves to meet their restricted percentage, handlers have two inventory reserve pools available, a primary reserve currently limited to 50 million pounds and an unlimited secondary reserve. Reserves allow the industry to mitigate the impact of oversupply in large crop years, while allowing the industry to supply markets in years when production falls below demand. Volume in the secondary reserve cannot be released unless the primary reserve is empty. Most reserve inventory flows in and out of the primary reserve, and it is rarely at zero, making it difficult to release volume from the secondary reserve.</P>
        <P>Accessing reserves, particularly at the beginning of a crop year when the new crop has yet to be harvested, has become more important in recent seasons. When the order was promulgated, tart cherries were primarily processed as ingredients or into pie filling and a 50 million pound primary reserve met the needs of the industry. However, dried cherries, juice, and juice concentrate are growing segments of the industry, and some handlers are also manufacturing finished products for retail. The additional processing steps for these new products, as well as the growing variety of retail products have changed reserve needs. At any given time, handlers now hold more volume in reserve.</P>
        <P>Additionally, in years when a crop is short or demand exceeds expectations, the Board can vote to issue a reserve release. During the 2010-2011 season, the Board found it necessary to issue two such releases. The Board believes increasing the capacity of the primary reserve to 100 million pounds would facilitate the release of reserve cherries when they are needed. Moving additional reserve volume into the primary pool, which is easier to access, should allow the industry to be more responsive to changes in demand and supply, and allow handlers more flexibility in how they utilize the reserve. The intent of this action is not to increase the volume of cherries in reserve, but to shift a greater volume into the primary reserve where it is more accessible to meet handler needs. This change should not impact volume restriction calculations.</P>
        <P>Accordingly, at its meeting on September 15, 2011, the Board recommended increasing the capacity of the primary inventory reserve from 50 million pounds to 100 million pounds. Fifteen Board members voted for this change and two abstained.</P>
        <P>In addition to discussing the primary reserve, the Board also considered changes to diversion credits. These credits are a handler's alternative to placing fruit in reserve in order to comply with their restricted percentage under volume restriction. The order provides that fruit used for certain exempt purposes, including new market development and market expansion, is eligible to receive diversion credits. Market expansion is defined as an activity that expands the sale of either tart cherries or the products in which tart cherries are an ingredient. The Board currently limits the duration of any diversion credit for new market development and market expansion to three years.</P>
        <P>The Board believes that new market development and market expansion activities have been successful in increasing sales. Some Board members expressed that these activities have been very helpful in developing the dried cherry and juice segments. Earlier regulations limited the volume that could receive diversion credit to 10 million pounds. However, the Board believed the limitation could be discouraging expansion and in 2006 recommended removing the diversion credit volume limitations. Since that time, the use of new market development and market expansion activities to meet restricted percentages has grown. The current three-year average for diversion credit for market expansion activities is approximately 35 million pounds a year.</P>
        <P>In its discussions of this issue, the Board sought to find a solution that would continue to encourage new market development and market expansion projects, but reduce the impact these credits have on volume restriction calculations. While market expansion activities designated for diversion credit represent about 15 percent of gross sales, these sales are not included in the average sales figure used to determine optimum supply for volume regulation. The Board estimates that limiting credits to one year would lower the annual average credit for market expansion to 16 million pounds, or 19 million pounds below the current average.</P>
        <P>With this action, it is anticipated that the difference in volume between the three-year credit and one year credit for market expansion would shift to free sales helping to reduce the calculated restricted percentage. Using current numbers, assuming that the difference of 19 million pounds would be counted as free sales, this change would reduce the calculated surplus. Reducing the calculated surplus would, in turn, help lower restricted percentages. The Board believes this change would help make the calculations under volume regulation more reflective of industry conditions.</P>

        <P>Accordingly, at its November 2, 2011, meeting, the Board voted unanimously to revise exemption provisions applicable to handler diversion activities by limiting diversion credits for market expansion activities to one year, with the time limit beginning with the date of the first shipment. The Board also noted that projects approved prior to this action would be allowed to finish their three-year cycle.<PRTPAGE P="24642"/>
        </P>
        <HD SOURCE="HD1">Initial Regulatory Flexibility Analysis</HD>
        <P>Pursuant to requirements set forth in the Regulatory Flexibility Act (RFA) (5 U.S.C. 601-612), the Agricultural Marketing Service (AMS) has considered the economic impact of this action on small entities. Accordingly, AMS has prepared this initial regulatory flexibility analysis.</P>
        <P>The purpose of the RFA is to fit regulatory actions to the scale of business subject to such actions in order that small businesses will not be unduly or disproportionately burdened. Marketing orders issued pursuant to the Act, and rules issued thereunder, are unique in that they are brought about through group action of essentially small entities acting on their own behalf.</P>
        <P>There are approximately 40 handlers of tart cherries who are subject to regulation under the marketing order and approximately 600 producers of tart cherries in the regulated area. Small agricultural service firms have been defined by the Small Business Administration (SBA) as those having annual receipts of less than $7,000,000, and small agricultural producers are defined as those having annual receipts of less than $750,000 (13 CFR 121.201).</P>
        <P>According to the National Agricultural Statistics Service, and Board data, the average annual grower price for tart cherries during the 2010-11 season was $0.221 per pound, and total shipments were around 270 million pounds. Therefore, average receipts for tart cherry producers were around $99,000, well below the SBA threshold for small producers. In 2010, The Food Institute estimated an f.o.b. price of $0.84 per pound for frozen tart cherries, which make up the majority of processed tart cherries. Using this data, average annual handler receipts were about $5.7 million, also below the SBA threshold for small agricultural service firms. Assuming a normal distribution, the majority of producers and handlers of tart cherries may be classified as small entities.</P>
        <P>This action would increase the volume of tart cherries that can be placed in the primary inventory reserve from 50 million pounds to 100 million pounds and would revise the exemption provisions pertaining to handler diversion activities by limiting diversion credits for new market development and market expansion activities to one year. These changes are intended to facilitate sales and lessen the impact of such activities on volume restriction calculations. This rule would add § 930.155 to the rules and regulations to establish the increased limit for the primary inventory reserve, and would revise § 930.162 of the regulations regarding exemptions as they pertain to handler diversion activities. The authority for these actions is provided in §§ 930.50 and 930.59 of the order. The Board recommended these actions at meetings on September 15, 2011, and November 2, 2011.</P>
        <P>The Board believes these changes would better align regulations with industry needs and practices, facilitate the release of restricted fruit, and help avoid over-restriction. It is not anticipated that this action would impose additional costs on handlers or growers, regardless of size. Handlers of all sizes could realize a cost savings by not having to store product relegated to the secondary reserve, which is difficult to access.</P>
        <P>Further, increasing the maximum volume that can be held in the primary reserve would allow handlers to be more responsive to industry needs by making reserves easier to access in periods of short supply or increased demand, which could facilitate sales. Changes in processing and cherry products have created a situation in which handlers may have more volume on hand at any given time, furthering the need to access reserves. Expanding the volume available in the primary reserve would assist handlers in managing their stocks and would help maintain a steady inventory of finished products to supply retailers and consumers.</P>
        <P>Additionally, the Board believes limiting diversion credits for market expansion to one year would move more sales into the free sales category for purposes of computing volume regulations. This would reduce the calculated surplus, and in turn lower restrictions. Lower restrictions would allow handlers to have a greater portion of their volume available for free sales. This could facilitate additional sales which could improve returns for growers and handlers.</P>
        <P>This rule is expected to benefit producers, handlers, and consumers. The effects of this rule are not expected to be disproportionately greater or less for small handlers or producers than for larger entities.</P>
        <P>The Committee discussed alternatives to these changes, including not increasing the primary reserve capacity, as well as eliminating diversion credits for market expansion rather than limiting them to one year. Regarding the change to primary reserve capacity, the Board agreed that changes in the industry necessitated this change and that it was in the industry's best interest to have this change in place by the next season. In discussing the change to diversion credits for market expansion, the Board considered phasing out diversion credits for market expansion altogether. However, some Board members believed that offering diversion credit for these activities had been beneficial to the industry and thus should not be eliminated entirely. The Board believes limiting credits to a maximum of one year would continue to encourage handlers to enter new markets, but lessen the impact on volume restriction calculations. Therefore, these alternatives were rejected.</P>
        <P>In accordance with the Paperwork Reduction Act of 1995, (44 U.S.C. Chapter 35), the order's information collection requirements have been previously approved by the Office of Management and Budget (OMB) and assigned OMB No. 0581-0177, (Tart Cherries Grown in the States of Michigan, New York, Pennsylvania, Oregon, Utah, Washington, and Wisconsin). No changes in those requirements as a result of this action are necessary. Should any changes become necessary, they would be submitted to OMB for approval.</P>
        <P>Accordingly, this action would not impose any additional reporting or recordkeeping requirements on either small or large tart cherry handlers. As with all Federal marketing order programs, reports and forms are periodically reviewed to reduce information requirements and duplication by industry and public sector agencies.</P>
        <P>AMS is committed to complying with the E-Government Act, to promote the use of the Internet and other information technologies to provide increased opportunities for citizen access to Government information and services, and for other purposes.</P>
        <P>USDA has not identified any relevant Federal rules that duplicate, overlap or conflict with this proposed rule.</P>

        <P>The Board formed a committee to review the order's volume regulation procedures and suggest changes to the Board. This committee held meetings where these issues were discussed in detail. These meetings were public meetings and both large and small entities were able to participate and express their views. In addition, the Board's meetings were widely publicized throughout the tart cherry industry and all interested persons were invited to attend and participate in Board deliberations on all issues. Like all Board meetings, the September 15, 2011, and November 2, 2011, meetings were public meetings and all entities,<PRTPAGE P="24643"/>both large and small, were able to express views on this issue. Finally, interested persons are invited to submit comments on this proposed rule, including the regulatory and informational impacts of this action on small businesses.</P>

        <P>A small business guide on complying with fruit, vegetable, and specialty crop marketing agreements and orders may be viewed at:<E T="03">www.ams.usda.gov/MarketingOrdersSmallBusinessGuide.</E>Any questions about the compliance guide should be sent to Laurel May at the previously mentioned address in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section.</P>
        <P>A 15-day comment period is provided to allow interested persons to respond to this proposal. Fifteen days is deemed appropriate because the Board would like to have this rule in place as soon as possible so handlers can consider these changes when making plans for the upcoming season. Further, handlers are aware of these proposed changes, which were discussed and recommended at public meetings and interested parties had the opportunity to provide input. All written comments timely received will be considered before a final determination is made on this matter.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 7 CFR Part 930</HD>
          <P>Marketing agreements, Reporting and recordkeeping requirements, Tart cherries.</P>
        </LSTSUB>
        
        <P>For the reasons set forth in the preamble, 7 CFR part 930 is proposed to be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 930—TART CHERRIES GROWN IN THE STATES OF MICHIGAN, NEW YORK, PENNSYLVANIA, OREGON, UTAH, WASHINGTON, AND WISCONSIN</HD>
          <P>1. The authority citation for 7 CFR part 930 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 601-674.</P>
          </AUTH>
          
          <P>2. A new § 930.150 is added to read as follows:</P>
          <SECTION>
            <SECTNO>§ 930.150</SECTNO>
            <SUBJECT>Primary inventory reserve.</SUBJECT>
            <P>Beginning July 1, 2012, the primary inventory reserve may not to exceed 100 million pounds.</P>
            <P>3. Section 930.162 is amended by adding a sentence at the end of section (b)(2) to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 930.162</SECTNO>
            <SUBJECT>Exemptions.</SUBJECT>
            <STARS/>
            <P>(b)  * * *</P>
            <P>(2)  * * *  In addition, shipments of tart cherries or tart cherry products in new market development and market expansion outlets are eligible for handler diversion credit for a period of one year from the handler's first date of shipment into such outlets.</P>
            <STARS/>
          </SECTION>
          <SIG>
            <DATED>Dated: April 17, 2012.</DATED>
            <NAME>David R. Shipman,</NAME>
            <TITLE>Acting Administrator, Agricultural Marketing Service.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9860 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-02-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 39</CFR>
        <DEPDOC>[Docket No. FAA-2012-0421; Directorate Identifier 2012-NM-042-AD]</DEPDOC>
        <RIN>RIN 2120-AA64</RIN>
        <SUBJECT>Airworthiness Directives; The Boeing Company Airplanes</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking (NPRM).</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We propose to adopt a new airworthiness directive (AD) for certain Boeing Company Model 757 airplanes. This proposed AD was prompted by a report of in-flight fracture of the right windshield (window 1) on the flight deck and multiple reports of electrical arcs at the terminal blocks of the flight deck windshields resulting in smoke and fire. This proposed AD would require repetitive inspections of electrical heat terminals on the left and right windshields for damage, and corrective actions if necessary. This proposed AD would also allow for replacing an affected windshield with a windshield equipped with different electrical connections, which would terminate the repetitive inspections for that windshield. We are proposing this AD to prevent smoke and fire in the flight deck, which can lead to loss of visibility, and injuries to or incapacitation of the flight crew.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>We must receive comments on this proposed AD by June 11, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may send comments, using the procedures found in 14 CFR 11.43 and 11.45, by any of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>Go to<E T="03">http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Fax:</E>202-493-2251.</P>
          <P>•<E T="03">Mail:</E>U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590.</P>
          <P>•<E T="03">Hand Delivery:</E>Deliver to Mail address above between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>

          <P>For service information identified in this proposed 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. 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 proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (phone: 800-647-5527) is in the<E T="02">ADDRESSES</E>section. Comments will be available in the AD docket shortly after receipt.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Elias Natsiopoulos, Aerospace Engineer, Systems and Equipment Branch, ANM-130S, FAA, Seattle Aircraft Certification Office (ACO), 1601 Lind Avenue SW., Renton, Washington 98057-3356; phone: 425-917-6478; fax: 425-917-6590; email:<E T="03">Elias.Natsiopoulos@faa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Comments Invited</HD>

        <P>We invite you to send any written relevant data, views, or arguments about this proposal. Send your comments to an address listed under the<E T="02">ADDRESSES</E>section. Include “Docket No. FAA-2012-0421; Directorate Identifier 2012-NM-042-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD because of those comments.</P>
        <P>We will post all comments we receive, without change, to<E T="03">http://www.regulations.gov,</E>including any personal information you provide. We will also post a report summarizing each<PRTPAGE P="24644"/>substantive verbal contact we receive about this proposed AD.</P>
        <HD SOURCE="HD1">Discussion</HD>
        <P>We have received nine reports from eight operators that electrical arcs occurred at the lower terminal blocks of the flight deck windshields. AD 2010-15-01, Amendment 39-16367 (75 FR 39804, July 13, 2010), addresses the lower electrical connections. We have also received reports of four failures of upper terminal blocks on Model 757 airplanes. In more than one incident, the arcs resulted in open flames. While in flight, one Model 757-200 series airplane experienced smoke in the cockpit, followed by the fracture of the inner pane of the first officer's windshield (right window 1). This windshield fracture resulted in total loss of the first officer's outside visibility and small shards of glass striking the first officer. Examination of the fractured windshield revealed evidence of arcing at the upper outboard (J1) and the upper inboard (J4) windshield electrical heat terminal connections. The inner pane fracture initiated beneath the J4 terminal block.</P>
        <P>The electrical connections on the windshields are made with lugs that attach with screws to the terminal block. A loose connection increases the heat at the terminal, which can cause damage to the internal joints (including solder, if present). Damaged solder joints are the primary cause of the electrical arcs. The primary cause of loose connections is the incorrectly torqued or incorrectly installed screw. This condition, if not corrected, could result in smoke and fire in the flight deck, which can result in the loss of visibility, and injuries to or incapacitation of the flightcrew.</P>
        <HD SOURCE="HD1">Other Related Rulemaking</HD>
        <P>On July 6, 2010, the FAA issued AD 2010-15-01, Amendment 39-16367 (75 FR 39804, July 13, 2010), applicable to certain Boeing Model 757, 767, and 777 series airplanes, which requires repetitive inspections for damage of the electrical terminal (J5 terminal) at the left and right flight deck window 1 windshield, and corrective actions if necessary. The most forward flight deck windows are referred to as windshields and named left and right window 1 respectively. The actions required by that AD are intended to prevent smoke and fire in the cockpit, which could lead to loss of visibility, and injuries to or incapacitation of the flight crew. Accomplishing the actions in this proposed AD would terminate the requirements of AD 2010-15-01 for Model 757 airplanes.</P>
        <HD SOURCE="HD1">Relevant Service Information</HD>
        <P>We reviewed Boeing Special Attention Service Bulletin 757-30-0019, Revision 3, dated December 16, 2011 (for Model 757-200, -200PF, and -200CB series airplanes); and Boeing Special Attention Service Bulletin 757-30-0020, Revision 3, dated December 16, 2011 (for Model 757-300 series airplanes). This service information describes procedures for repetitive detailed inspections for damage (including, but not limited to, arcing, loose terminals, heat damage, cross-threaded connections, and cracking) of the wiring and electrical terminals J1, J4, and J5 at the left and right flight deck windshields; and corrective actions if necessary.</P>
        <P>The corrective actions include applying correct torque to a loose electrical connection, replacing any damaged terminal lug with a new lug, repairing damaged wiring, and replacing an unserviceable windshield with a new or serviceable windshield. Boeing Special Attention Service Bulletin 757-30-0019, Revision 3, dated December 16, 2011 (for Model 757-200, -200PF, and -200CB series airplanes); and Boeing Special Attention Service Bulletin 757-30-0020, Revision 3, dated December 16, 2011 (for Model 757-300 series airplanes); specify that the replacement windshield can be either a new or serviceable windshield that uses screws and lugs for the electrical connection, or a new or serviceable windshield that uses pins and sockets for the electrical connections.</P>
        <P>For airplanes on which a new windshield that uses pins and sockets is installed, Boeing Special Attention Service Bulletin 757-30-0019, Revision 3, dated December 16, 2011 (for Model 757-200, -200PF, and -200CB series airplanes); and Boeing Special Attention Service Bulletin 757-30-0020, Revision 3, dated December 16, 2011 (for Model 757-300 series airplanes); also specify changing the related wire bundle and cutting the bulb seal to give clearance for terminals on the replacement windshield. This service information specifies that installing a windshield that uses pins and sockets for the electrical connections eliminates the need for the repetitive detailed inspections for that windshield.</P>
        <P>Boeing Special Attention Service Bulletin 757-30-0019, Revision 3, dated December 16, 2011 (for Model 757-200, -200PF, and -200CB series airplanes); and Boeing Special Attention Service Bulletin 757-30-0020, Revision 3, dated December 16, 2011 (for Model 757-300 series airplanes); also specify repetitive detailed inspections for damage of any windshield that is replaced with a windshield that uses screws and lugs for the heat connection, or if a windshield heat power connection is reassembled on windshields that use screws and lugs for the heat connection.</P>
        <HD SOURCE="HD1">FAA's Determination</HD>
        <P>We are proposing this AD because we evaluated all the relevant information and determined the unsafe condition described previously is likely to exist or develop in other products of the same type design.</P>
        <HD SOURCE="HD1">Proposed AD Requirements</HD>
        <P>This proposed AD would require accomplishing the actions specified in the service information described previously, except as discussed under “Differences Between the Proposed AD and the Service Information.”</P>
        <HD SOURCE="HD1">Differences Between the Proposed AD and the Service Information</HD>
        <P>Although Boeing Special Attention Service Bulletin 757-30-0019, Revision 3, dated December 16, 2011 (for Model 757-200, -200PF, and -200CB series airplanes); and Boeing Special Attention Service Bulletin 757-30-0020, Revision 3, dated December 16, 2011 (for Model 757-300 series airplanes); recommend accomplishing certain inspections, window replacement, and reassembly of the electrical connections within 500 flight hours or 150 days, whichever occurs first, we have determined that a compliance time of within 500 flight hours after the effective date of this AD addresses the identified unsafe condition soon enough to ensure an adequate level of safety for the affected fleet. This difference has been coordinated with The Boeing Company.</P>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>We estimate that this proposed AD affects 664 airplanes of U.S. registry.</P>

        <P>We estimate the following costs to comply with this proposed AD:<PRTPAGE P="24645"/>
        </P>
        <GPOTABLE CDEF="s50,r100,12C,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<LI>U.S. operators</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Detailed inspection of windshields</ENT>
            <ENT>3 work-hours × $85 per hour = $255 per inspection cycle</ENT>
            <ENT>$0</ENT>
            <ENT>$255 per inspection cycle</ENT>
            <ENT>$169,320 per inspection cycle.</ENT>
          </ROW>
        </GPOTABLE>
        <P>We estimate the following costs to do any necessary corrective actions that would be required based on the results of the proposed inspection. We have no way of determining the number of aircraft that might need these corrective actions.</P>
        <GPOTABLE CDEF="s100,r50,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">Windshield replacement and changes to related wiring including lug replacement</ENT>
            <ENT>9 work-hours × $85 per hour = $765 per windshield</ENT>
            <ENT>$19,687 per windshield</ENT>
            <ENT>$20,452 per windshield.</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">Authority for This Rulemaking</HD>
        <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
        <P>We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
        <HD SOURCE="HD1">Regulatory Findings</HD>
        <P>We determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <P>For the reasons discussed above, I certify this proposed regulation:</P>
        <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
        <P>(2) Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),</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">The Proposed Amendment</HD>
        <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
          <P>1. The authority citation for part 39 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40113, 44701.</P>
          </AUTH>
          <SECTION>
            <SECTNO>§ 39.13</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
            <P>2. The FAA amends § 39.13 by adding the following new airworthiness directive (AD):</P>
            
            <EXTRACT>
              <FP SOURCE="FP-2">
                <E T="04">The Boeing Company:</E>Docket No. FAA-2012-0421; Directorate Identifier 2012-NM-042-AD.</FP>
              <HD SOURCE="HD1">(a) Comments Due Date</HD>
              <P>We must receive comments by June 11, 2012.</P>
              <HD SOURCE="HD1">(b) Affected ADs</HD>
              <P>This AD affects AD 2010-15-01, Amendment 39-16367 (75 FR 39804, July 13, 2010).</P>
              <HD SOURCE="HD1">(c) Applicability</HD>
              <P>This AD applies to The Boeing Company airplanes, certificated in any category, as identified in paragraphs (c)(1) and (c)(2) of this AD.</P>
              <P>(1) Model 757-200, -200PF, and -200CB airplanes identified in Boeing Special Attention Service Bulletin 757-30-0019, Revision 3, dated December 16, 2011.</P>
              <P>(2) Model 757-300 airplanes identified in Boeing Special Attention Service Bulletin 757-30-0020, Revision 3, dated December 16, 2011.</P>
              <HD SOURCE="HD1">(d) Subject</HD>
              <P>Joint Aircraft System Component (JASC)/Air Transport Association (ATA) of America Code 30, Ice and Rain Protection.</P>
              <HD SOURCE="HD1">(e) Unsafe Condition</HD>
              <P>This AD was prompted by a report of in-flight fracture of the right windshield (window 1) on the flightdeck and multiple reports of electrical arcs at the terminal blocks of the flight deck windshields resulting in smoke and fire. We are issuing this AD to prevent smoke and fire in the flight deck, which can lead to loss of visibility, and injuries to or incapacitation of the flight crew.</P>
              <HD SOURCE="HD1">(f) Compliance</HD>
              <P>Comply with this AD within the compliance times specified, unless already done.</P>
              <HD SOURCE="HD1">(g) Inspection and Repair</HD>

              <P>Within 500 flight hours after the effective date of this AD, except as required by paragraph (h) of this AD: Do a detailed inspection for damage of the wiring and electrical terminal blocks (J1, J4, and J5 terminals) at the left and right flight deck window 1 windshield, and do all applicable corrective actions, by accomplishing all the applicable actions specified in the Accomplishment Instructions of Boeing Special Attention Service Bulletin 757-30-0019, Revision 3, dated December 16, 2011 (for Model 757-200, -200PF, and -200CB series airplanes); or Boeing Special Attention Service Bulletin 757-30-0020, Revision 3, dated December 16, 2011 (for Model 757-300 series airplanes). Except as provided by paragraph (j) of this AD, do all applicable corrective actions before further flight. Repeat the detailed inspection thereafter at the applicable interval specified in paragraph (g)(1) or (g)(2) of this AD. Doing the replacement specified in paragraph (k) of this AD terminates the repetitive inspection<PRTPAGE P="24646"/>requirements of this paragraph for that replaced flight deck windshield.</P>
              <P>(1) For flight deck windshields manufactured by GKN Aerospace (GKN) with screw/lug electrical connections, repeat the detailed inspection thereafter at intervals not to exceed 12,000 flight hours or 48 months, whichever occurs later.</P>
              <P>(2) For flight deck windshields manufactured by PPG Aerospace (PPG) with screw/lug electrical connections, repeat the detailed inspection thereafter at intervals not to exceed 6,000 flight hours or 24 months, whichever occurs later.</P>
              <HD SOURCE="HD1">(h) Compliance Time Exception for Previous Inspection</HD>
              <P>For airplanes on which inspections of the J1, J4, and J5 terminals, as specified in the Accomplishment Instructions of Boeing Special Attention Service Bulletin 757-30-0019, Revision 2, dated April 19, 2010 (for Model 757-200, -200PF, and -200CB series airplanes); or Boeing Special Attention Service Bulletin 757-30-0020, Revision 2, dated March 31, 2010 (for Model 757-300 series airplanes); were accomplished before the effective date of this AD: Do the actions required by paragraph (g) of this AD at the applicable compliance time specified in paragraphs (h)(1) and (h)(2) of this AD. Repeat the inspection thereafter at the applicable intervals specified in paragraphs (g)(1) or (g)(2) of this AD.</P>
              <P>(1) For flight deck windshields manufactured by GKN with screw/lug electrical connections: At the later of the times specified in paragraphs (h)(1)(i) and (h)(1)(ii) of this AD.</P>
              <P>(i) Within 12,000 flight hours or 48 months, whichever occurs later, after accomplishing the inspection.</P>
              <P>(ii) Within 500 flight hours after the effective date of this AD.</P>
              <P>(2) For flight deck windshields manufactured by PPG with screw/lug electrical connections: At the later of the times specified in paragraphs (h)(2)(i) and (h)(2)(ii) of this AD.</P>
              <P>(i) Within 6,000 flight hours or 24 months, whichever occurs later, after accomplishing the inspection.</P>
              <P>(ii) Within 500 flight hours after the effective date of this AD.</P>
              <HD SOURCE="HD1">(i) Inspection for Replaced Windshield or Reassembled Heat Power Connection</HD>
              <P>For any windshield replaced after the effective date of this AD with a windshield that uses screws and lugs for electrical heat connection, or if a windshield heat power connection is reassembled on windshields that use screws and lugs for windshield heat connections: Do the actions required in paragraph (g) of this AD within 500 flight hours after the windshield replacement or connection reassembly, and thereafter at the applicable interval specified in paragraph (g)(1) or (g)(2) of this AD, as applicable.</P>
              <HD SOURCE="HD1">(j) Exception to Compliance Time for Certain Windshield Replacement</HD>
              <P>If, during the inspection required by paragraph (g) or (i) of this AD, the screw is found cross threaded: Do the applicable actions specified in paragraph (j)(1) or (j)(2) of this AD.</P>
              <P>(1) If the terminal lug is loose and cannot be tightened: Before further flight, replace that windshield, in accordance with the Accomplishment Instructions of Boeing Special Attention Service Bulletin 757-30-0019, Revision 3, dated December 16, 2011 (for Model 757-200, -200PF, and -200CB series airplanes); or Boeing Special Attention Service Bulletin 757-30-0020, Revision 3, dated December 16, 2011 (for Model 757-300 series airplanes).</P>
              <P>(2) If the terminal lug is tight or can be tightened: Replace that windshield within 500 flight hours after the inspection, in accordance with the Accomplishment Instructions Boeing Special Attention Service Bulletin 757-30-0019, Revision 3, dated December 16, 2011 (for Model 757-200, -200PF, and -200CB series airplanes); or Boeing Special Attention Service Bulletin 757-30-0020, Revision 3, dated December 16, 2011 (for Model 757-300 series airplanes).</P>
              <HD SOURCE="HD1">(k) Optional Terminating Action</HD>
              <P>Replacing a flight deck windshield that uses screws and lugs for the electrical connections with a flight deck windshield that uses pins and sockets for the electrical connections, in accordance with the Accomplishment Instructions of Boeing Special Attention Service Bulletin 757-30-0019, Revision 3, dated December 16, 2011 (for Model 757-200, -200PF, and -200CB series airplanes); or Boeing Special Attention Service Bulletin 757-30-0020, Revision 3, dated December 16, 2011 (for Model 757-300 series airplanes); ends the repetitive inspection requirements of paragraph (g) of this AD for that windshield.</P>
              <HD SOURCE="HD1">(l) Related AD Termination</HD>
              <P>Accomplishing the actions required by this AD terminates the requirements of AD 2010-15-01, Amendment 39-16367 (75 FR 39804, July 13, 2010), paragraphs (g), (j), and (k), for that airplane only.</P>
              <HD SOURCE="HD1">(m) Credit for Previous Actions</HD>
              <P>This paragraph provides credit for the actions required by this AD, if those actions were performed before the effective date of this AD using Boeing Special Attention Service Bulletin 757-30-0019, Revision 2, dated April 19, 2010 (for Model 757-200, -200PF, and -200CB series airplanes); or Boeing Special Attention Service Bulletin 757-30-0020, Revision 2, dated March 31, 2010 (for Model 757-300 series airplanes).</P>
              <HD SOURCE="HD1">(n) Alternative Methods of Compliance (AMOCs)</HD>

              <P>(1) The Manager, Seattle Aircraft Certification Office, 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>
              <HD SOURCE="HD1">(o) Related Information</HD>

              <P>(1) For more information about this AD, contact Elias Natsiopoulos, Aerospace Engineer, Systems and Equipment Branch, ANM-130S, FAA, Seattle Aircraft Certification Office (ACO), 1601 Lind Avenue SW., Renton, Washington 98057-3356; phone: 425-917-6478; fax: 425-917-6590; email:<E T="03">Elias.Natsiopoulos@faa.gov.</E>
              </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>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>
            </EXTRACT>
          </SECTION>
          <SIG>
            <DATED>Issued in Renton, Washington, on April 5, 2012.</DATED>
            <NAME>Ali Bahrami,</NAME>
            <TITLE>Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9916 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <CFR>18 CFR Part 40</CFR>
        <DEPDOC>[Docket Nos. AD12-14-000 and AD11-11-000]</DEPDOC>
        <SUBJECT>Open Access and Priority Rights on Interconnection Facilities</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Energy Regulatory Commission, DOE.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of Inquiry.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In this Notice of Inquiry, the Commission seeks comment on open access and priority rights for capacity on interconnection facilities.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments are due June 11, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You may submit comments, identified by docket number and in accordance with the requirements posted on the Commission's Web site,<E T="03">http://www.ferc.gov</E>. Comments may be submitted by any of the following methods:</P>
          <P>•<E T="03">Agency Web Site:</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, at<E T="03">http://www.ferc.gov/docs-filing/efiling.asp</E>.<PRTPAGE P="24647"/>
          </P>
          <P>•<E T="03">Mail/Hand Delivery:</E>Commenters unable to file comments electronically must mail or hand-deliver an original and copy of their comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street NE., Washington, DC 20426. These requirements can be found on the Commission's Web site, see,<E T="03">e.g.,</E>the “Quick Reference Guide for Paper Submissions,” available at<E T="03">http://www.ferc.gov/docs-filing/efiling.asp</E>, or via phone from Online Support at (202) 502-6652 or toll-free at 1-866-208-3676.</P>
          <P>
            <E T="03">Instructions:</E>For detailed instructions on submitting comments and additional information on the rulemaking process, see the Comment Procedures Section of this document.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          
          <FP SOURCE="FP-1">Becky Robinson (Technical Information), Office of Energy Policy and Innovation, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-8868.</FP>
          <FP SOURCE="FP-1">Christopher Thomas (Technical Information), Office of Energy Market Regulation, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-8412.</FP>
          <FP SOURCE="FP-1">Olga Kolotushkina (Legal Information), Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, (202) 502-6024.</FP>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <GPOTABLE CDEF="s30,12" COLS="2" OPTS="L2,i1">
          <TTITLE>139 FERC ¶ 61,051</TTITLE>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1">Docket Nos.</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Open Access and Priority Rights on Interconnection Facilities</ENT>
            <ENT>AD12-14-000</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Priority Rights to New Participant-Funded Transmission</ENT>
            <ENT>AD11-11-000</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">Notice of Inquiry</HD>
        <DATE>April 19, 2012.</DATE>
        <P>1. In this Notice of Inquiry (NOI), the Commission seeks to explore whether, and, if so, how the Commission should revise its current policy concerning priority rights and open access with regard to certain interconnection facilities. In a series of cases that have come before the Commission in recent years, the Commission has treated certain interconnection facilities<SU>1</SU>
          <FTREF/>as transmission facilities for purposes of open access policies. However, the Commission has permitted an owner of interconnection facilities to have priority to capacity over its facilities for its existing use at the time of a third-party request for service.<SU>2</SU>
          <FTREF/>In the instance where an owner of interconnection facilities has specific, pre-existing generator expansion plans with milestones for construction of generation facilities and can demonstrate that it has made material progress toward meeting those milestones, the Commission may grant priority rights for the capacity on the interconnection facilities to those future generation projects or expansions as well.<SU>3</SU>
          <FTREF/>Further, an affiliate of the current interconnection facility owner that is developing its own generator projects also may obtain priority rights to the capacity on the interconnection facilities by meeting the “specific plans and milestones” standard with respect to future use, provided that the plans include a future transfer of ownership of the interconnection facilities to such an affiliate.<SU>4</SU>

          <FTREF/>This granting of priority rights preserves the ability of the generation developer to deliver its output to the point of interconnection with the transmission system, so long as it can make the relevant showing to the Commission sufficient to justify priority. The Commission requires that, upon receipt of a request for transmission service from an unaffiliated third party, a<E T="03">pro forma</E>Open Access Transmission Tariff (OATT) must be filed by the owner of the facilities considered interconnection facilities under Order No. 2003 within 60 days of the date of the request.<SU>5</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>1</SU>As noted below, the Commission in the past has used the term “generator lead lines” to describe the class of facilities at issue in this proceeding. In this NOI, we will use the term “interconnection facilities,” except when referencing comments on generator lead lines.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">See Milford Wind Corridor, LLC,</E>129 FERC ¶ 61,149, at P. 24 (2009) (<E T="03">Milford</E>);<E T="03">Terra-Gen Dixie Valley, LLC,</E>132 FERC ¶ 61,215, at P. 49 (2010) (<E T="03">Terra-Gen I</E>).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>
            <E T="03">Aero Energy LLC,</E>116 FERC ¶ 61,149, at P. 28 (2006) (<E T="03">Aero</E>);<E T="03">Milford,</E>129 FERC ¶ 61,149 at P. 22; and<E T="03">Alta Wind,</E>134 FERC ¶ 61,109, at P. 16-17 (2011) (<E T="03">Alta Wind</E>). Such plans and initial progress also must pre-date a valid request for service.<E T="03">Terra-Gen I,</E>132 FERC ¶ 61,215 at P. 53.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>
            <E T="03">See Milford,</E>129 FERC ¶ 61,149 at P. 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>5</SU>
            <E T="03">Black Creek Hydro, Inc.,</E>77 FERC ¶ 61,232, at 61,941 (1996);<E T="03">Termoelectrica U.S., LLC,</E>105 FERC ¶ 61,087, at P. 11 (2003).</P>
        </FTNT>

        <P>2. To date, the Commission has applied this policy on a case-by-case basis. The Commission's current policy is guided by the desire to prevent undue discrimination by ensuring that third parties have open access to available transfer capability that is not being used by the owner of the interconnection facilities. In doing so, the Commission has considered priority access to firm service, and granted waivers of certain provisions in the<E T="03">pro forma</E>OATT to reflect the limited service available over interconnection facilities and the limited ability of generation developers to support certain OATT ancillary services and requirements.</P>
        <P>3. Through this Notice of Inquiry, the Commission seeks comment on options for addressing priority rights on interconnection facilities given the responses filed to the March 2011 technical conference, which identified a number of concerns with the Commission's current policy. As discussed in the sections that follow, the Commission seeks comments on alternative approaches to govern third-party requests for service and priority rights: continued use of an OATT framework with potential modification and clarification, including the potential introduction of a safe harbor period, and a case-by-case determination on the generation developer's priority rights; and use of a Large Generator Interconnection Agreement (LGIA)/Large Generator Interconnection Procedures (LGIP) framework in which the existing LGIA provisions that govern third-party use of a transmission provider's interconnection facilities would be extended to interconnection customer's interconnection facilities (i.e., allowing parties to mutually agree to the use of and compensation for the facilities). The Commission also seeks comment on the scope of our inquiry in this proceeding and whether, as a threshold matter, there is a need to reconsider the Commission policy as set forth in the recent series of cases.<SU>6</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>6</SU>
            <E T="03">See, e.g., Aero,</E>116 FERC ¶ 61,149;<E T="03">Milford,</E>129 FERC ¶ 61,149;<E T="03">Terra-Gen I,</E>132 FERC ¶ 61,215; and<E T="03">Alta Wind,</E>134 FERC ¶ 61,109.</P>
        </FTNT>
        <P>4. We note that there are numerous and potentially detailed issues embedded within the broad categories of this NOI. We encourage all interested stakeholders to address the specific questions for which the Commission seeks comment and to include as appropriate any proposed tariff language that should be considered.<SU>7</SU>

          <FTREF/>We also encourage comments on how any individual potential policy change discussed below would affect the viability of other policies (<E T="03">e.g.,</E>if the Commission were to adopt a safe harbor period, what are the implications for the current policy of demonstrating specific plans and milestones to secure priority rights)?</P>
        <FTNT>
          <P>
            <SU>7</SU>The Commission distinguishes this proceeding from the North American Electric Reliability Corporation's (NERC) current investigation into the applicability of Reliability Standards to interconnection facilities (Project 2010-07). Comments related to NERC's investigation are not the subject of this Notice of Inquiry and should be directed to NERC.</P>
        </FTNT>
        <PRTPAGE P="24648"/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>5. Interconnection facilities are constructed to enable a generation facility or multiple generation facilities to transmit power from the generation facility to the integrated transmission grid. They are radial in nature, with a single point of interconnection with the network grid, and power flows toward the network grid, with no electrical loads between the generation facilities and the point of interconnection with the network grid. Interconnection facilities can be relatively short ancillary components to a single generation facility.<SU>8</SU>
          <FTREF/>Alternatively, they may span much longer distances and represent significant transmission capacity, being capable of interconnecting additional generation projects.<SU>9</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>8</SU>
            <E T="03">See, e.g., Southern Company Serv., Inc.,</E>Docket No. ER12-554-000 (involving an approximately 2,000 foot interconnection facility).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>9</SU>
            <E T="03">See, e.g., Bayonne Energy Center,</E>136 FERC ¶ 61,019 (2011) (involving a 345 kV interconnection facility);<E T="03">Terra-Gen I,</E>132 FERC ¶ 61,215 (involving a 212 mile interconnection facility).</P>
        </FTNT>
        <P>6. Ownership and operation of interconnection facilities may take several forms. Under Order No. 2003,<SU>10</SU>
          <FTREF/>generation developers that wish to interconnect their generation facilities to the integrated transmission grid must submit an interconnection request to the relevant transmission provider pursuant to the transmission provider's LGIP and develop an LGIA. Interconnection facilities that are owned, controlled, or operated by the transmission provider, regardless of which party constructed the facilities, are designated as transmission provider's interconnection facilities under the LGIA. Third party use of the transmission provider's interconnection facilities is governed by the provisions of the LGIA.<SU>11</SU>

          <FTREF/>This provision permits the parties to negotiate for a third party to use the interconnection facilities and entitles the original interconnection customer to compensation for capital expenses it incurred to pay for the transmission provider's interconnection facilities and to compensation for the ongoing costs, including operation and maintenance costs, based on a<E T="03">pro rata</E>use among the parties.</P>
        <FTNT>
          <P>
            <SU>10</SU>
            <E T="03">Standardization of Generator Interconnection Agreements and Procedures,</E>Order No. 2003, FERC Stats. &amp; Regs. ¶ 31,146 (2003),<E T="03">order on reh'g,</E>Order No. 2003-A, FERC Stats. &amp; Regs. ¶ 31,160,<E T="03">order on reh'g,</E>Order No. 2003-B, FERC Stats. &amp; Regs. ¶ 31,171 (2004),<E T="03">order on reh'g,</E>Order No. 2003-C, FERC Stats. &amp; Regs. ¶ 31,190 (2005),<E T="03">aff'd sub nom. Nat'l Ass'n of Regulatory Util. Comm'rs</E>v.<E T="03">FERC,</E>475 F3d. 1277 (D.C. Cir. 2007),<E T="03">cert. denied,</E>552 U.S. 1230 (2008).</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>11</SU>Section 9.9.2 states “* * * if the Parties mutually agree, such agreement not to be unreasonably withheld, to allow one or more third parties to use Transmission Provider's Interconnection Facilities, or any part thereof, Interconnection Customer will be entitled to compensation for the capital expenses it incurred in connection with the Interconnection Facilities based upon the<E T="03">pro rata</E>use of the Interconnection Facilities by the Transmission Provider, all third-party users and the Interconnection Customer * * *.”</P>
        </FTNT>

        <P>7. However, where a generation developer has funded and constructed a portion of the interconnection facilities, and does not transfer ownership or operational control of those facilities to the transmission provider after construction, under the<E T="03">pro forma</E>LGIA those facilities are classified as interconnection customer's interconnection facilities. That is, interconnection customers' interconnection facilities are located between the generation facility and the point at which either the transmission provider's interconnection facilities begin or the point of interconnection with the transmission provider's transmission system. Section 9.9.2 of the<E T="03">pro forma</E>LGIA is inapplicable to third-party requests for use of an interconnection customer's interconnection facilities. These interconnection customer's interconnection facilities are the types of facilities at issue in this proceeding.</P>
        <HD SOURCE="HD2">March 2011 Technical Conference</HD>
        <P>8. The Commission held a technical conference in March 2011 to explore, among other things, the application of the Commission's open access policies to generator lead lines<SU>12</SU>
          <FTREF/>in the instance when affiliated or unaffiliated third-party generators also seek to use these facilities.<SU>13</SU>
          <FTREF/>Generally, commenters assert that these policies may be unduly burdensome and ill-suited for generator lead lines, and may have detrimental implications for the future development and financing of generator lead lines and their associated generation projects, especially renewable energy projects.<SU>14</SU>
          <FTREF/>Specifically, commenters<SU>15</SU>
          <FTREF/>argue that the Commission should recognize the commercial, technological, legal, and other differences between transmission lines and these generator lead lines when considering open access principles in the context of radial generator lead lines. Further, commenters raise a number of concerns with the Commission's current practice of imposing an OATT Filing requirement on generator lead line developers.</P>
        <FTNT>
          <P>
            <SU>12</SU>The technical conference announcements and participants used the term “generator lead lines.” While for this NOI we think it is appropriate to hold the discussion in terms of interconnection facilities, in the interest of being true to the comments, we will maintain the use of the term “generator lead lines” in this section.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>13</SU>
            <E T="03">Priority Rights to New Participant-Funded Transmission,</E>March 15, 2011 Technical Conference, AD11-11-000.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>14</SU>The list of entities that filed comments or participated at this conference is in Appendix A of this NOI.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>15</SU>First Wind, Invenergy, Duke, and NextEra.</P>
        </FTNT>
        <P>9. Among the unique attributes of generator lead lines, commenters suggest the following features: (1) Generator lead lines are radial lines that serve the limited and sole purpose of connecting generation facilities to the transmission network, i.e., they are not an element of the integrated transmission network; (2) generator lead lines do not provide benefits to the transmission system in terms of capability or reliability, and cannot be relied on for coordinated operation of the transmission system; (3) an outage on the generator lead lines would not affect the entire transmission system; (4) generator lead lines do not provide ancillary services; (5) generator lead lines are often located in remote regions not in close proximity to load; (6) generator lead lines are owned by entities entirely different than those that typically own transmission; and (7) generator lead lines are viewed by their developers and banks providing financing as an integral part of the whole, not as a project or business separate from the generating facility.<SU>16</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>16</SU>
            <E T="03">See, e.g.,</E>First Wind at 2-4; Invenergy at 1-2; Duke at 5-6; and NextEra at 12-13.</P>
        </FTNT>
        <P>10. Among the main concerns raised, commenters<SU>17</SU>
          <FTREF/>identify a “free rider” problem that, in their opinion, produces a disincentive to be the first developer to build a generator lead line, while creating a relative advantage for other generation developers to be second in line.<SU>18</SU>
          <FTREF/>Several commenters<SU>19</SU>
          <FTREF/>argue that being subject to the open access requirements of Order Nos. 888, 889, and 890 (including the obligations to file an OATT within 60 days of a request for service and to administer an OATT, Open Access Same Time Information System, Standards of Conduct, and Uniform System of Accounts) imposes significant costs and difficulties for independent developers, especially small ones that are not affiliated with large utilities.<SU>20</SU>

          <FTREF/>These developers assert that complying with such responsibilities, in addition to the obligation to commence studies related to a third-party request for service, may require expenditure of a significant portion of their capital, and require<PRTPAGE P="24649"/>additional expertise, hardware, software, and staffing resources.<SU>21</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>17</SU>Invenergy, CAHW, First Wind, Puget, and MidAmerican.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>18</SU>
            <E T="03">See, e.g.,</E>Puget at 14-15; MidAmerican at 14-15.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>19</SU>SCE, BP, CAHW, Puget, National Grid, MidAmerican, and Wenner.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>20</SU>
            <E T="03">See, e.g.,</E>Puget at 7-8; AWEA at 10.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>21</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>11. Although these expenses may generally be considered normal costs of operating in a regulated environment, commenters argue that the costs are triggered by a relatively low threshold event—a written request unaccompanied by any deposit.<SU>22</SU>
          <FTREF/>Thus, commenters assert that the minimal commitment required for third-party requests for transmission service on generator lead lines may not sufficiently distinguish serious customers from those who may have merely a speculative interest in taking transmission service, while the generator lead line owner is immediately affected by having to file an OATT, expend significant staff resources, and incur significant costs to evaluate the feasibility of providing the requested service.<SU>23</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>22</SU>
            <E T="03">See, e.g.,</E>BP at 8; CAWH at 3; and NextEra at 20-21. Commenters appear to be referring to sections 17.2, 18.2, or 29.2 of the<E T="03">pro forma</E>OATT, which set forth information required for a completed application. In addition, where the owner of the facilities does not have an OATT on file, a third-party customer does not need to submit a deposit as part of its application for transmission service to the interconnection facilities.<E T="03">See Sagebrush, a California Partnership,</E>130 FERC ¶ 61,093, at P 57,<E T="03">order on reh'g,</E>132 FERC ¶ 61,234 (2010) (<E T="03">Sagebrush</E>). We note that the deposit is required once an OATT is filed.<E T="03">See also Sagebrush,</E>132 FERC ¶ 61,234 at P 44;<E T="03">Terra-Gen I,</E>132 FERC ¶ 61,215 at n.84.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>23</SU>
            <E T="03">See, e.g.,</E>BP at 8; NextEra at 20-21.</P>
        </FTNT>
        <P>12. Commenters also state that priority rights on their generator lead line are essential for the financing of generation projects because priority rights provide lenders with assurance that developers will still be able to use the line for their planned generation facilities.<SU>24</SU>
          <FTREF/>Commenters assert that lenders are wary of financing generation projects without a guarantee that the generator lead line will have sufficient capacity available to transmit the generation to the grid, for both early and later phases of their generation projects.<SU>25</SU>
          <FTREF/>In addition, commenters<SU>26</SU>
          <FTREF/>argue that generator developers are concerned with the policy of demonstrating “specific plans and milestones,” as it is unclear to them which milestones need to be described and which factors would adequately demonstrate material progress towards those milestones. They note that, although the Commission has found certain evidence sufficient in prior cases,<SU>27</SU>
          <FTREF/>its review was limited largely to privileged and confidential evidence, which could not be described in the Commission orders or otherwise disclosed to the public.<SU>28</SU>
          <FTREF/>Also, commenters argue that, given the uncertainty of generation project development due to financing, permitting, and various other factors, it may be neither possible for a generator developer to provide the needed detail about phases of generation that will be constructed in the future, nor prudent for developers to prematurely enter into binding contractual commitments merely for purposes of attempting to demonstrate priority rights.<SU>29</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>24</SU>
            <E T="03">See, e.g.,</E>First Wind at 3-4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>25</SU>
            <E T="03">See, e.g.,</E>Allete at 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>26</SU>Allete, BP and NextEra.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>27</SU>
            <E T="03">See Aero,</E>118 FERC ¶ 61,210 at P 22;<E T="03">Milford,</E>129 FERC ¶ 61,149 at P 22; and<E T="03">Alta Wind,</E>134 FERC ¶ 61,109 at P 17.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>28</SU>NextEra at 22; BP Wind at 7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>29</SU>
            <E T="03">See, e.g.,</E>NextEra at 24; First Wind at 4.</P>
        </FTNT>
        <P>13. Commenters note that certain sections of the<E T="03">pro forma</E>OATT may be inapplicable to generator lead lines on a generic basis. For instance, commenters argue that a single circuit generator lead line can only provide firm or non-firm point-to-point service and cannot provide network service,<SU>30</SU>
          <FTREF/>so the<E T="03">pro forma</E>OATT's standard terms and conditions for network service are unnecessary.<SU>31</SU>

          <FTREF/>Additionally, several commenters assert that because generator lead line owners do not have the capability to supply many ancillary services to third parties, the ancillary services provisions of the<E T="03">pro forma</E>OATT are likewise inapplicable.<SU>32</SU>
          <FTREF/>Further, commenters argue that the planning requirements included in Attachment K of the OATT may be an unnecessary regulatory burden for generator developers of generation lead lines, as they have no native load growth, they do not own network transmission facilities, will not typically expand their lines absent a request for service, and the costs of such facilities are not socialized or based on a regional planning needs analysis.<SU>33</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>30</SU>
            <E T="03">See, e.g., Sagebrush,</E>130 FERC ¶ 61,093 at P 29 (waiving the<E T="03">pro forma</E>OATT's provisions for network service to a single transmission line that does not have a control area or the generation resources necessary to provide network service).<E T="03">See also Terra-Gen Dixie Valley, LLC,</E>134 FERC ¶ 61,027, at P 10-12 (2011) (<E T="03">Terra-Gen II</E>).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>31</SU>
            <E T="03">See, e.g.,</E>First Wind at 6-7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>32</SU>
            <E T="03">See, e.g.,</E>First Wind at 6-7; AWEA at 11; Edison Mission at 25; and NextEra at 13.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>33</SU>
            <E T="03">See, e.g.,</E>NextEra at 19-20.</P>
        </FTNT>

        <P>14. Commenters concede that generator lead line owners are free to propose non-rate terms and conditions that differ from the<E T="03">pro forma</E>OATT, where each deviation is supported by a demonstration that it is consistent with or superior to the<E T="03">pro forma</E>OATT or does not apply given the particular generator lead line owner's business model.<SU>34</SU>
          <FTREF/>However, rather than the Commission continuing to evaluate such requests on a case-by-case basis, some commenters<SU>35</SU>
          <FTREF/>suggest that the Commission should establish a new<E T="03">pro forma</E>OATT to apply generically to all generator lead lines.</P>
        <FTNT>
          <P>
            <SU>34</SU>
            <E T="03">See, e.g.,</E>
            <E T="03">Montana-Alberta Tie, Inc.,</E>116 FERC ¶ 61,071, at P 60 (2006) (<E T="03">MATL</E>).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>35</SU>NextEra, AWEA, SCE, CAHW, NU/NSTAR, and First Wind.</P>
        </FTNT>
        <P>15. As an alternative to the current Commission policy, some commenters suggest expanding section 9.9.2 of the LGIA, which addresses third-party access to transmission provider's interconnection facilities, to apply to interconnection customer's interconnection facilities as well, and argue that doing so would render unnecessary the requirement for the original interconnection customer to file an OATT when a third party requests service on their interconnection facilities.<SU>36</SU>
          <FTREF/>They argue that treating a generator requesting access to interconnection facilities as an interconnection request is a pragmatic approach that more accurately characterizes the service being sought, and eliminates the unduly burdensome and costly obligations imposed upon generation developers under the Commission's current policies that commenters assert impedes the development of location-constrained renewable generation.<SU>37</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>36</SU>Puget at 8; Edison Mission at 17.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>37</SU>Edison Mission at 19.</P>
        </FTNT>
        <P>16. Further, commenters express concern that the current policy does not adequately engage the transmission provider in the process of interconnecting a third-party requestor of service on a generator lead line.<SU>38</SU>
          <FTREF/>To reach load and serve customers under current policy, a third party may be required to make separate requests for access to the original interconnection customer's interconnection facilities and the transmission provider's interconnection facilities, as well as a transmission service request on the interconnecting transmission provider's transmission system.<SU>39</SU>
          <FTREF/>Commenters assert that this bifurcated process is inefficient.<SU>40</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>38</SU>
            <E T="03">See, e.g.,</E>Puget at 11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>39</SU>Puget at 9.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>40</SU>
            <E T="03">See, e.g.,</E>
            <E T="03">id.</E>at 10.</P>
        </FTNT>
        <P>17. Transmission providers,<SU>41</SU>

          <FTREF/>however, caution the Commission against discriminating against existing transmission providers<E T="03">vis-à-vis</E>independent merchant transmission developers with regard to priority rights or other regulatory requirements. Transmission providers argue that any separate treatment for independent developers is not appropriate, as transmission providers do not want to<PRTPAGE P="24650"/>be disadvantaged or discouraged from constructing generator lead lines. Instead, these commenters favor any future policies or clarifications of existing policy to be based on the type of facility being constructed, not on the entity that is proposing to own the facility.<SU>42</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>41</SU>SCE at 3; Puget at 7; and MidAmerican at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>42</SU>
            <E T="03">See, e.g.,</E>Puget at 3.</P>
        </FTNT>
        <HD SOURCE="HD1">II. Discussion</HD>
        <HD SOURCE="HD2">A. Scope of Inquiry</HD>
        <P>18. In this NOI, the Commission seeks comment on various options for addressing third-party access to and priority rights on interconnection customer's interconnection facilities. Appendix B to this document provides a schematic and explanation of what the Commission believes to be a typical situation. Much of the discussion and questions in this NOI derive from this understanding. As discussed above, Order No. 2003 addresses third party use of transmission provider interconnection facilities, but not interconnection customer interconnection facilities. With a goal of ensuring that a third party generator (G2) may be able to interconnect to interconnection customer interconnection facilities that in some instances have been 30, 50, or even hundreds of miles long, and up to 345 kV, the Commission has in a series of recent cases treated interconnection customer interconnection facilities as transmission facilities for purposes of open access policies and required that the original developer (G1) file an OATT within 60 days of a request for service on these facilities. In light of comments received, and as discussed in the sections that follow, the Commission seeks comments on two alternative approaches to govern third-party use and priority rights to use: (1) Continued use of an OATT framework with potential modification and clarification, including the potential introduction of a safe harbor period, and a case-by-case determination on the generation developer's priority rights; or (2) use of a LGIA/LGIP framework in which the existing LGIA provisions that govern third-party use of transmission provider's interconnection facilities would be extended to interconnection customer's interconnection facilities. In addition to the details of each approach, the Commission seeks comment on the relative ability of each to meet customer needs while ensuring that the rates, terms, and conditions of jurisdictional services remain just and reasonable and not unduly discriminatory.</P>
        <P>19. At the outset, however, the Commission also seeks comment on the scope of our inquiry in this proceeding and whether, as a threshold matter, there is a need to reconsider existing Commission policies. With the passage of time, concerns raised at the March 2011 technical conference and in subsequent comments may have been addressed as the industry has considered the Commission's existing precedent. If not, additional views on what approach would be most effective in addressing third-party requests for service and/or evaluating priority rights on interconnection facilities would be useful. The Commission encourages commenters to discuss their views of the needs of their business models in the context of the Commission's open access and interconnection policies, which are designed to ensure that transmission service is made available on terms that are just and reasonable and not unduly discriminatory.</P>
        <P>20. As noted above, the Commission intends that the focus of this proceeding is on interconnection customers' interconnection facilities as a class of facilities. If commenters disagree that this is the set of facilities at issue, then they should explain their understanding of the facilities at issue (referencing the drawing in Appendix B) and respond to the questions below in terms of the set of facilities they believe is at issue, and clarify that they are doing so. Similarly, if commenters distinguish application of certain policies based on the size of a facility or other characteristics, then they should respond to the questions below in terms of the relevant characteristics, and clarify that they are doing so.</P>
        <P>21. Specifically, the Commission seeks comment on these issues:</P>
        
        <EXTRACT>
          <P>i. To what specific set of facilities are commenters' concerns directed? That is, are commenters' concerns directed toward access to interconnection customer interconnection facilities, or to both interconnection customer interconnection facilities and transmission provider interconnection facilities?</P>
          <P>ii. Is requiring interconnection customer interconnection facilities to provide third-party access under an OATT framework necessary to ensure against undue discrimination and ensure just and reasonable rates, given that developers of remote generation are building interconnection facilities of considerable length and/or size?</P>
          <P>iii. Has the Commission's current policy blurred the pre-existing line between interconnection service and transmission service with respect to providing for third-party access to interconnection facilities in such a way as to create unintended consequences?</P>
          <P>iv. Has industry largely adapted to current Commission policy such that the Commission should continue its current policy? If not, should the Commission respond to concerns expressed at the Technical Conference with (a) potential clarification of and modification to its current policy of treating interconnection facilities under the OATT framework; or (b) adoption of a framework under which it would consider issues of third-party access and priority rights under its interconnection rules and procedures?</P>

          <P>v. Should the Commission consider different treatment for larger versus smaller interconnection facilities,<E T="03">e.g.,</E>treating larger interconnection facilities under the OATT framework and smaller interconnection facilities under the LGIA/LGIP framework? If so, what would be the appropriate threshold for separating large versus small interconnection facilities (<E T="03">e.g.,</E>voltage, miles, or potential third party interconnection)? Should any distinctions be made among existing interconnection facilities, planned expansions of existing interconnection facilities, and new interconnection facilities, for any of the options?</P>

          <P>vi. From commenters' perspective, is there a meaningful distinction between the interconnection/operation of facilities proposed to provide independent transmission service (<E T="03">e.g., Chinook</E>
            <SU>43</SU>

            <FTREF/>) and generator interconnection facilities of long length and high voltage (<E T="03">e.g., Terra Gen I</E>)?</P>
          <FTNT>
            <P>
              <SU>43</SU>
              <E T="03">Chinook Power Transmission, LLC,</E>126 FERC ¶ 61,134 (2009) (<E T="03">Chinook</E>).</P>
          </FTNT>
          <P>vii. Are there circumstances under which it would be feasible and/or desirable to allow the generation developer to choose whether its interconnection facilities would be governed by the OATT framework or the LGIA/LGIP framework, with the attendant rights and responsibilities of either choice?</P>
          <P>viii. For purposes of access policies, should the Commission distinguish between affiliates and nonaffiliates even when parties have otherwise agreed to the terms and conditions of access to the facilities?</P>
          <P>ix. Are there additional approaches that the Commission should consider? Be specific as to details. For example, commenters mention common facilities agreements (CFAs) as a means for parties to agree on access to interconnection customer's interconnection facilities.<SU>44</SU>
            <FTREF/>Commenters also mention a rebuttable<E T="03">de minimis</E>exception for small interconnection customer's interconnection facilities.</P>
          <FTNT>
            <P>
              <SU>44</SU>
              <E T="03">See, e.g.,</E>
              <E T="03">BP Wind Energy North America Inc.,</E>129 FERC ¶ 61,207 (2009) (for an order accepting a CFA among affiliated parties and granting waiver of the requirements of Order Nos. 888 and 890).<E T="03">See Sky River, LLC,</E>134 FERC ¶ 61,064, at P 13 (2011) (for an order rejecting a CFA between unaffiliated parties and denying waiver of the requirements of Order Nos. 888 and 890).<E T="03">But see Ashtabula Wind, LLC,</E>127 FERC ¶ 61,215 at P 10 (2009) (granting waiver of the OATT requirements of Order Nos. 888 and 890 in the context of a Common Facilities Agreement between two unaffiliated parties).</P>
          </FTNT>

          <P>x. To the extent that the concerns regarding third-party use and priority rights do not exist for transmission provider's interconnection facilities, why would a generation developer that builds its own interconnection facilities choose to retain operational control of them as opposed to<PRTPAGE P="24651"/>turning them over to the transmission provider?</P>
        </EXTRACT>
        <HD SOURCE="HD2">B. Alternative Approaches for Comment</HD>
        <HD SOURCE="HD3">1. Open Access Transmission Tariff Framework</HD>
        <P>22. If the Commission were to maintain reliance on the existing OATT framework, should it be modified to recognize the characteristics of interconnection customer's interconnection facilities and needs of generation developers?</P>
        <HD SOURCE="HD3">a. Clarification of Specific Plans and Milestones Evaluation</HD>
        <P>23. Our current case-by-case policy of determining a generation developer's priority rights to its interconnection facilities provides a degree of flexibility and recognizes that there is not necessarily a standard method for development of generation projects. However, as mentioned above, some commenters voice concerns that the Commission's current case-by-case evaluation of generation developers' requests for priority rights on their interconnection facilities based on the demonstration of specific plans and milestones for construction of their generation projects is not clear. To address this concern, the Commission could be more prescriptive on the “specific plans and milestones” standard to provide direction to generation developers seeking to establish their firm priority rights. Such requirements could include the type of evidence that would be indicative of sufficient “specific plans and milestones,” and the factors to be considered in determining whether “material progress has been made.”</P>
        <P>24. The Commission seeks comment on issues related to the evaluation of specific plans and milestones in requests for priority rights to use capacity on interconnection customer's interconnection facilities. Specifically:</P>
        
        <EXTRACT>
          <P>i. Should the Commission continue its practice of evaluating requests for priority rights for interconnection customer's interconnection facilities on a case-by-case basis? If so, should the existing standards used to evaluate sufficiency of evidence to demonstrate priority be clarified or modified? How?</P>
          <P>ii. Should the Commission require generation developers to meet a given set of uniform criteria to secure priority rights? If so, what are the necessary criteria and what types of evidence are sufficient to demonstrate these criteria? Or, should generation developers have the flexibility to demonstrate the sufficiency of their plans based on various criteria, and what might these criteria be? In this regard, how should the Commission balance needs for regulatory certainty and flexibility?</P>
        </EXTRACT>
        <HD SOURCE="HD3">b. OATT Filing Trigger</HD>
        <P>25. The Commission's current policy to grant waiver of the requirement to file an OATT prior to the receipt of a third-party request for transmission is designed to reduce the regulatory burden on entities that did not intend to be transmission providers. However, as noted above, several commenters express concern with the existing standard for what constitutes a valid third-party request for service on interconnection customer's interconnection facilities. One panelist suggests that the standard for a third-party request should be at least to match the level of generation development that has been demonstrated by the original interconnection customer,<SU>45</SU>
          <FTREF/>although one commenter argues that this is an impossible standard because a generation developer is limited in how far it can proceed with its project until it has secured transmission capacity.<SU>46</SU>
          <FTREF/>One commenter also argues that generation developers should be allowed to require that transmission customers satisfy more stringent creditworthiness standards than currently required, because generation developers, in forming their business models and capital structure, do not contemplate taking on significant credit risks of competing generators.<SU>47</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>45</SU>Transcript at 128 (citing Kurt Adams of First Wind).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>46</SU>Gradient at 7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>47</SU>Edison Mission at 24.</P>
        </FTNT>
        <P>26. Some commenters suggest modifying the rules for when and under what circumstances an OATT would need to be filed. For example, commenters argue that extending the current 60-day requirement to file an OATT is justified because of a possibility that a third party requesting service might withdraw after the generation developer has incurred significant costs in putting an OATT into place, including the internal structure to administer it.<SU>48</SU>
          <FTREF/>One commenter suggests requiring the generation developer to file a notice of a request for service within a certain number of days after receiving a request, and requiring them to file an OATT only after a generation interconnection agreement or a transmission service agreement is executed. They argue that this process would allow the generation developer to focus on performing the necessary studies instead of filing an OATT.<SU>49</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>48</SU>BP Wind at 8; NextEra at 20-21.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>49</SU>NextEra at 20-21.</P>
        </FTNT>
        <P>27. The Commission seeks comment on issues related to third-party requests and when to require an OATT to be filed. Specifically:</P>
        
        <EXTRACT>
          <P>i. Should the Commission alter the standard for what constitutes a third-party request for service on interconnection customer's interconnection facilities? If so, what should the standard be? What would be the advantages and disadvantages of doing so, compared to current policy?</P>
          <P>ii. Should the standard that is required for a third-party request for service be the same standard that is required for the original interconnection customer (or its affiliate) to request priority rights, i.e., the specific plans and milestones demonstration discussed above? Why or why not? Would this raise confidentiality concerns, and if so, how could those be mitigated or avoided?</P>
          <P>iii. Should the Commission alter the requirement that a third-party request triggers an OATT Filing requirement by the original interconnection customer within 60 days of receipt of a request for service? If so, how?</P>
          <P>iv. If the Commission were to alter the requirement that a third-party request triggers an OATT Filing requirement by the original interconnection customer, should there be different approaches when affiliates gain access to the interconnection facilities as opposed to when nonaffiliates gain access?</P>
          <P>v. Would it enhance regulatory certainty for the Commission to amend the LGIA to include contractual terms apprising the interconnection customer that it will become a transmission provider if a third party requests transmission service over its interconnection customer interconnection facilities?</P>
          <P>vi. Would the creation of a<E T="03">pro forma</E>tailored OATT (discussed below) ease the burden on the generation developer to the point that the existing 60-day window for filing an OATT would be sufficient?</P>
          <P>vii. Some commenters argue that under current Commission policy, third parties must make up to four sequential requests for service (for interconnection and transmission services, from both the original interconnection customer and the transmission provider) to deliver their power. These commenters use this as an argument in favor of using the LGIA/LGIP framework. Is there a way under the OATT framework to coordinate the requests that a third party would need to make?</P>
        </EXTRACT>
        <HD SOURCE="HD3">c. Tailored OATT</HD>
        <P>28. Order No. 888 set forth a<E T="03">pro forma</E>tariff that provides standardized terms and conditions for the provision of open access transmission service. The unique features of interconnection facilities may warrant tailoring the terms and conditions of the OATT to correspond to these unique features for providing open access transmission service. One option for recognizing these differences and for responding to the concerns laid out above may be to continue to use a<E T="03">pro forma</E>OATT framework but, on a generic basis, modify the<E T="03">pro forma</E>OATT to establish a tailored set of terms and conditions for service, i.e., a<E T="03">pro forma</E>“tailored<PRTPAGE P="24652"/>OATT,” that would apply to a well-defined set of interconnection facilities.</P>

        <P>29. The Commission has previously granted waiver of specific provisions of the<E T="03">pro forma</E>OATT to accommodate unique situations. For instance, as mentioned above, because interconnection facilities are not networked facilities, the Commission has granted waiver of the<E T="03">pro forma</E>OATT requirement to provide network services on interconnection facilities.<SU>50</SU>

          <FTREF/>Also, because the transmission provider to which the interconnection facilities are interconnected is required to have an OATT that provides for ancillary services on a non-discriminatory basis, and because of the physical limitations of interconnection facilities, the Commission has granted waiver of the<E T="03">pro forma</E>OATT requirement to provide ancillary services.<SU>51</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>50</SU>
            <E T="03">See Sagebrush,</E>130 FERC ¶ 61,093 at P 29;<E T="03">Terra-Gen Dixie Valley, LLC,</E>135 FERC ¶ 61,134, at P 12 (2011) (<E T="03">Terra-Gen III</E>).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>51</SU>
            <E T="03">See Sagebrush,</E>130 FERC ¶ 61,093 at P 29;<E T="03">Terra-Gen III,</E>135 FERC ¶ 61,134 at PP 31-33.</P>
        </FTNT>
        <P>30. Many generation developers argue that the<E T="03">pro forma</E>OATT is not well-suited for interconnection facilities and that these facilities should either be substantially or entirely exempt from<E T="03">pro forma</E>OATT requirements.<SU>52</SU>
          <FTREF/>Some of those commenters argue that using a tailored OATT could address several of the concerns with existing policy by lessening the time, expense, and other burdens inherent in developing, filing, and administering an OATT. Proponents also argue that this approach would reduce confusion and the risk of inconsistency, which is heightened by employing a case-by-case waiver approach.<SU>53</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>52</SU>
            <E T="03">See, e.g.,</E>SCE at 4; Edison Mission at 13-14; Puget at 6; NextEra at 6; and First Wind at 7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>53</SU>NextEra at 2-3.</P>
        </FTNT>

        <P>31. Several participants in the Technical Conference identify<E T="03">pro forma</E>OATT provisions they believe could be eliminated to create a<E T="03">pro forma</E>tailored OATT. One commenter submitted a proposed<E T="03">pro forma</E>“Radial OATT.”<SU>54</SU>
          <FTREF/>Commenters argue that the network service provisions,<SU>55</SU>
          <FTREF/>the requirement to provide scheduling services,<SU>56</SU>
          <FTREF/>and the requirement to provide ancillary services,<SU>57</SU>
          <FTREF/>all provisions which the Commission has previously waived for interconnection customer's interconnection facilities, should be removed from a tailored OATT framework.</P>
        <FTNT>
          <P>
            <SU>54</SU>NextEra at Attachment 1.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>55</SU>CAHW at 23-24; Edison Mission at 22; NextEra at 15-16; and First Wind at 6-7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>56</SU>AWEA at 11; NextEra at 13.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>57</SU>AWEA at 11; Edison Mission at 25; and NextEra at 11-12.</P>
        </FTNT>
        <P>32. Additionally, commenters argue that some other provisions the Commission has not waived are inappropriate for interconnection facilities. Specifically, commenters argue that requiring generation developers to adopt comparable Attachment K transmission planning process procedures makes little sense, and that instead the Commission should direct the generation developer, after receiving a request for service, to participate in the interconnecting transmission provider's Attachment K process.<SU>58</SU>
          <FTREF/>Commenters also suggest that the<E T="03">pro forma</E>OATT requirement to calculate Available Transfer Capability may be inapplicable to interconnection facilities.<SU>59</SU>
          <FTREF/>Additionally, one commenter argues that developing rates for point-to-point transmission service for Schedules 7 and 8 may be particularly burdensome for generation developers not experienced with traditional rate regulation and that do not usually follow the Uniform System of Accounts,<SU>60</SU>
          <FTREF/>and also suggests waiver of the Open Access Same-Time Information System and the Standards of Conduct.<SU>61</SU>
          <FTREF/>Another commenter suggests allowing generation developers to use a single set of interconnection procedures and a single interconnection agreement for all generators, instead of separate procedures and agreements for large and small generators, because there is a limited set of potential customers.<SU>62</SU>
          <FTREF/>Another commenter argues that generation developers should not have an obligation to expand their interconnection facilities if there is insufficient capacity for a third party's intended use.<SU>63</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>58</SU>NextEra at 19-20; AWEA at 12; CAHW at 23; and NU/NSTAR at 7-8.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>59</SU>
            <E T="03">See, e.g.,</E>CAHW at 23; NextEra at 9-11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>60</SU>CAHW at 23-24.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>61</SU>
            <E T="03">Id.</E>at 24.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>62</SU>Edison Mission at 27. They note the Commission rejected this idea in<E T="03">Sagebrush,</E>130 FERC ¶ 61,093 at P 52, but has allowed the use of a single set of procedures and a single agreement by the Midwest ISO.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>63</SU>Invenergy at 11.</P>
        </FTNT>
        <P>33. Commenters also identify provisions in the<E T="03">pro forma</E>OATT that they think should be modified in a tailored OATT framework. For instance, several commenters argue that, while the<E T="03">pro forma</E>OATT requires the use of average line losses, it is appropriate for interconnection facilities to use incremental line losses, because they are discrete facilities and do not form a network.<SU>64</SU>

          <FTREF/>One commenter asserts that allocating average line losses under section 15.7 of the<E T="03">pro forma</E>OATT fails to recognize that each successive user increases the losses borne by earlier users because losses increase as the line becomes fully used, and can render the power contracts of earlier users uneconomical or interfere with their ability to supply contracted power.<SU>65</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>64</SU>
            <E T="03">See, e.g.,</E>NextEra at 14-15; CAHW at 23; and Invenergy at 9-10.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>65</SU>CAHW at 23.</P>
        </FTNT>
        <P>34. The Commission seeks comments on these issues. Specifically:</P>
        
        <EXTRACT>
          <P>i. Would a<E T="03">pro forma</E>tailored OATT accomplish the Commission's goals of ensuring non-discriminatory access? Is a<E T="03">pro forma</E>tailored OATT appropriate in these circumstances, or should the Commission continue to evaluate requests for waiver of certain<E T="03">pro forma</E>OATT provisions on interconnection facilities on a case-by-case basis?</P>
          <P>ii. Does a<E T="03">pro forma</E>tailored OATT provide developers clarity beyond that which has already been established by Commission precedent on the applicability of the<E T="03">pro forma</E>OATT to interconnection facilities?</P>
          <P>iii. How does a<E T="03">pro forma</E>tailored OATT framework compare to the other options presented here in terms of commercial viability?</P>
          <P>iv. What are the relative benefits and drawbacks of the<E T="03">pro forma</E>tailored OATT framework as compared to the existing policy? How should the Commission distinguish use of a<E T="03">pro forma</E>tailored OATT for interconnection facilities and use of the<E T="03">pro forma</E>OATT for public utility transmission providers that have divested their generation and thus may have limited ability to provide all OATT services,<E T="03">e.g.,</E>ancillary services? Similarly, should the Commission distinguish interconnection facilities that may use a<E T="03">pro forma</E>tailored OATT from transmission facilities that may typically receive waiver of some<E T="03">pro forma</E>OATT provisions, such as merchant transmission lines? If so, how?</P>
          <P>v. Identify the<E T="03">pro forma</E>OATT provisions that should be excluded from a<E T="03">pro forma</E>tailored OATT. Why should these be excluded?</P>

          <P>vi. What, if any, new or modified provisions only applicable to interconnection facilities should be added to a<E T="03">pro forma</E>tailored OATT? Why?</P>
          <P>vii. If the Commission were to pursue a<E T="03">pro forma</E>tailored OATT, should the Commission adopt the proposed<E T="03">pro forma</E>Radial OATT submitted by NextEra?<SU>66</SU>
            <FTREF/>Please explain and be specific as to any changes that would need to be made to that proposal.</P>
          <FTNT>
            <P>
              <SU>66</SU>NextEra at Attachment 1.</P>
          </FTNT>
          <P>viii. If a<E T="03">pro forma</E>tailored OATT did not include a requirement to provide ancillary services, would relying on the public utility transmission provider to provide these services create an undue burden on the public utility transmission provider?</P>
          <P>ix. Should all interconnection customer's interconnection facilities be eligible to provide service under a tailored OATT? If not, which facilities should be excluded? Is the size of the facilities (for example, length, capacity, voltage) relevant to being eligible for tailored OATT treatment?</P>
        </EXTRACT>
        <PRTPAGE P="24653"/>
        <HD SOURCE="HD3">d. Safe Harbor</HD>
        <P>35. A variation on the OATT framework is a safe harbor period. Within a safe harbor the generation developer would have a grace period in which the open access rules determined to be relevant for interconnection customer's interconnection facilities would not apply, to allow for the phased development of generation projects over that period. Accordingly, a generation developer would be assumed to have priority rights to capacity on its interconnection facilities during the safe harbor period.</P>

        <P>36. The Commission previously rejected a proposal for a safe harbor period of firm priority rights in<E T="03">Milford,</E>stating that such a period would be inconsistent with Commission precedent granting waiver of open access requirements unless and until the owner of the line receives a request for transmission service.<SU>67</SU>
          <FTREF/>Nevertheless, many of the commenters<SU>68</SU>
          <FTREF/>suggest this option as a means to protect generation developers' priority rights to use their interconnection facilities for their phased generation project development.</P>
        <FTNT>
          <P>
            <SU>67</SU>
            <E T="03">Milford,</E>129 FERC ¶ 61,149 at P 23.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>68</SU>AWEA, BP, CAHW, Edison Mission, First Wind, Gradient, Invenergy, NextEra, and Sempra.</P>
        </FTNT>
        <P>37. The Commission seeks comments on issues related to a safe harbor period. Specifically:</P>
        
        <EXTRACT>
          <P>i. Is a safe harbor period a viable approach? What are the benefits and drawbacks of the safe harbor period approach, as compared with the current case by case demonstration of specific plans and milestones, or the other options presented herein? For instance, to what extent could such a safe harbor period be used as a means to prevent others from accessing the transmission system?</P>
          <P>ii. If the Commission were to institute a safe harbor period, should a generation developer be allowed to provide access to its interconnection facilities to others during the safe harbor period? If so, how should the Commission guard against discriminatory access?</P>
          <P>iii. If the Commission were to institute a safe harbor period, could the Commission adopt for the safe harbor period the requirement, currently applicable where the Commission has granted priority rights, that a generation developer make any currently unused capacity available to third parties until such time as its future generation projects come on line, in a way that is consistent with the objectives of a safe harbor period?</P>
          <P>iv. What would be the appropriate duration for the safe harbor period? Should there be differences in the duration of the safe harbor period based upon different resource types (geothermal, wind, solar, etc.)? If so, how can such distinctions be justified?</P>

          <P>v. Should a safe harbor period be established to begin automatically from some fixed milestone date (<E T="03">e.g.,</E>such as the in-service date of the interconnection facilities)? If so, what should that milestone be? Or, should a developer be required to make a demonstration before it qualifies for a safe harbor (<E T="03">e.g.,</E>such as plans for phased generation development)? If the latter, what should be required to make such demonstration?</P>
          <P>vi. What types of interconnection facilities should qualify, and how should a generation developer identify itself as one that is pursuing phased generation development? Should there be an upper or lower limit on physical characteristics of the interconnection facilities such as length, voltage, capacity, etc. to qualify for safe harbor treatment?</P>
          <P>vii. Should there be intermediate development requirements to maintain safe harbor status? What would these requirements be? If requirements are not satisfied, what consequences are appropriate?</P>
        </EXTRACT>
        <HD SOURCE="HD3">2. LGIA/LGIP</HD>

        <P>38. An alternative framework for dealing with third-party requests for service and priority rights on interconnection customer's interconnection facilities would be to rely on a modified version of the LGIA/LGIP. Some commenters suggest expanding section 9.9.2 of the<E T="03">pro forma</E>LGIA, which addresses third-party access to transmission provider's interconnection facilities, to apply to interconnection customer's interconnection facilities as well, and argue that doing so would render unnecessary the requirement for the generation developer to file an OATT.<SU>69</SU>
          <FTREF/>They argue that this would provide access to interconnection customer's interconnection facilities in the same manner that access to transmission provider's interconnection facilities is now provided.<SU>70</SU>

          <FTREF/>One commenter suggests that the Commission could also revise the definition of Affected System to include interconnection customer's interconnection facilities specifically, which would mean that these facilities would be studied as part of subsequent interconnection studies performed by the transmission provider for other interconnection customers, because an interconnection system impact study is defined in the<E T="03">pro forma</E>LGIA as “an engineering study that evaluates the impact of the proposed interconnection on the safety and reliability of Transmission Provider's Transmission System and, if applicable, an Affected System.”<SU>71</SU>
          <FTREF/>Commenters also propose that, under an LGIA framework, third parties should apply directly to the transmission provider (and not the generation developer) for access to excess capacity on the interconnection customer's interconnection facilities at the same time that they apply for service on the transmission provider's interconnection facilities and transmission system.<SU>72</SU>
          <FTREF/>These commenters argue that this process would be preferable to the Commission's current policy, under which a new interconnection customer could be required to negotiate separately with the generation developer and the transmission provider. Commenters further argue that involving the transmission provider at the onset of the process is more efficient because the transmission provider is critical to assessing system impacts, providing support such as ancillary services, and coordinating reliability issues.<SU>73</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>69</SU>Puget at 8; Edison Mission at 17; Allete at 2; SCE at 3-4; and MidAmerican at 15-16.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>70</SU>Puget at 15.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>71</SU>Edison Mission at 18 (referencing definitions in LGIA section 1).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>72</SU>Puget at 9-10.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>73</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>39. Commenters add that section 9.9.2 of the<E T="03">pro forma</E>LGIA recognizes an opportunity for interconnection customers and the transmission provider to negotiate a multi-party agreement to determine the amount of compensation owed to an interconnection customer for capital expenses related to the transmission provider's interconnection facilities, as well as the allocation of on-going expenses.<SU>74</SU>

          <FTREF/>Some commenters suggest that the Commission could develop a<E T="03">pro forma</E>multi-party agreement to be used by entities in negotiating under section 9.9.2.<SU>75</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>74</SU>
            <E T="03">See, e.g.,</E>Edison Mission at 18.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>75</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>40. Generally, commenters argue that treating a third-party request for access to interconnection customer's interconnection facilities as an interconnection request is a pragmatic approach that more accurately characterizes the service being sought, and eliminates the unduly burdensome and costly obligations imposed upon generation developers under the Commission's current policies which commenters assert impede the development of location-constrained renewable generation.<SU>76</SU>

          <FTREF/>Commenters characterize expanding section 9.9.2 of the<E T="03">pro forma</E>LGIA as an administratively simple and less onerous way to facilitate access to interconnection customer's interconnection facilities.<SU>77</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>76</SU>Edison Mission at 19.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>77</SU>Puget at 8; Edison Mission at 19; and SCE at 3-4.</P>
        </FTNT>

        <P>41. The Commission seeks comment on whether treating third-party use of interconnection facilities as interconnection service is a workable<PRTPAGE P="24654"/>alternative to current Commission policy. Specifically:</P>
        
        <EXTRACT>
          <P>i. If the Commission were to expand section 9.9.2 to govern third party use of interconnection customer's interconnection facilities, what would prevent the original interconnection customer from evading negotiations with the third party (which is likely its competitor), withholding capacity for reasons other than a legitimate planned project, or putting excessive cost responsibilities on the third party?</P>

          <P>ii. Would extending section 9.9.2 as discussed above be sufficient to enable the transmission provider to facilitate granting third parties access to the interconnection customer's interconnection facilities? Or would other arrangements or modifications to the<E T="03">pro forma</E>LGIA be needed to give the transmission provider that ability? For example, what commercial arrangements between the transmission provider and the original interconnection customer would be required to enable third-party interconnection to the interconnection customer's interconnection facilities?</P>
          <P>iii. What are the benefits and drawbacks of a third party requesting interconnection service from the transmission provider, rather than from the original interconnection customer?</P>
          <P>iv. Should the<E T="03">pro forma</E>LGIA be modified to include an obligation to expand the existing capacity of the interconnection customer's interconnection facilities to accommodate a third-party request for interconnection service? If so, should the obligation apply to the original interconnection customer or the transmission provider? Would such a modification be consistent with the roles and responsibilities established in the rest of the<E T="03">pro forma</E>LGIA for whichever party the obligation applies to (i.e., either the original interconnection customer or the transmission provider)?</P>

          <P>v. Are there other issues associated with third-party use of the interconnection customer's interconnection facilities that would require other modifications to the<E T="03">pro forma</E>LGIA? If so, what are the issues, and what would these modifications be? For example, as the term is defined in the<E T="03">pro forma</E>LGIA, interconnection facilities are “sole use” facilities. If the Commission were to rely on the interconnection rules and procedures to govern third party use of interconnection facilities, would we need to eliminate language in the LGIA/LGIP that refers to these as “sole use” facilities? If so, what would be the collateral consequences?</P>
          <P>vi. In addition to the modifications to the<E T="03">pro forma</E>LGIA/LGIP identified above, would there be benefit in the Commission developing other<E T="03">pro forma</E>agreements to facilitate third-party access to the interconnection customer's interconnection facilities (<E T="03">e.g., pro forma</E>multi-party agency agreements, service agreements, cost-sharing agreements, etc.), or should those agreements be developed by the affected entities and reviewed by the Commission on a case-by-case basis?</P>
          <P>vii. How would expanding the<E T="03">pro forma</E>LGIA to govern third-party requests for service on the interconnection customer's interconnection facilities otherwise solve the concerns identified above? Are there other concerns with current Commission policy on access to interconnection customer's interconnection facilities that would remain under an LGIA/LGIP framework?</P>
          <P>viii. Should there be a limit (<E T="03">e.g.,</E>with respect to voltage, capacity, or length) to the interconnection customer's interconnection facilities that would qualify for treatment under the LGIA/LGIP framework discussed above?</P>
          <P>ix. How would an LGIA/LGIP approach compare to the other options presented here in terms of commercial viability and removing barriers to the development of location-constrained generation?</P>
        </EXTRACT>
        

        <P>42. The Commission also seeks comment on how priority rights to interconnection customer's interconnection facilities for phased generation development would work within an LGIA/LGIP framework. In making a valid interconnection request under the<E T="03">pro forma</E>LGIP, an interconnection customer must submit (1) A $10,000 deposit, (2) a completed application with detailed generator data (Appendix 1 of the LGIP), and (3) a demonstration of site control or post an additional deposit of $10,000.<SU>78</SU>
          <FTREF/>Additionally, the LGIA stipulates various milestones that must be logged with dates for completion in Appendix B of the LGIA. If future generation phases are included in an initial request for interconnection service, then meeting these milestones as a means to demonstrate intended future use of the facilities would arguably be similar in substance to the Commission's current policy of demonstrating plans and milestones to secure priority rights, though relying solely on the interconnection rules and procedures for securing priority rights would nevertheless be a different approach than the Commission's current policy of demonstrating plans and milestones. The LGIP stipulates that a generator with a higher queued interconnection request or an executed LGIA (or unexecuted LGIA that a party has requested be filed with the Commission) is included in the base case for any subsequent Interconnection Feasibility or System Impact Study.<SU>79</SU>
          <FTREF/>So as long as the initial interconnection request or executed LGIA includes later phases of a generation project, under the interconnection rules and procedures with a modified section 9.9.2 to include interconnection customer interconnection facilities, the generation developer would not risk losing its planned interconnection service simply because a third party also seeks to use the interconnection customer interconnection facilities. Rather, the full capacity of the original interconnection customer's request, including capacity for future phases of generation if those are included in the original LGIA that was developed, is unavailable for use by any third party. This is currently how the transmission provider treats transmission provider interconnection facilities when it studies a new interconnection request. The Commission seeks comment, however, on whether this is a viable and fair approach for demonstrating and securing priority rights to capacity for phased generation projects. Specifically:</P>
        <FTNT>
          <P>
            <SU>78</SU>LGIP section 3.3.1.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>79</SU>
            <E T="03">See</E>LGIP section 6.2 and 7.3.</P>
        </FTNT>
        
        <EXTRACT>
          <P>i. For generation projects that are built in phases, is it possible and/or typical to request the interconnection facilities be constructed in such a manner as to accommodate the capacity for future phases in an initial interconnection request and/or LGIA? How have developers been submitting interconnection requests and executing LGIAs for phased projects; i.e., have developers been including the capacity necessary for future generation phases in the initial interconnection request under LGIP?</P>

          <P>ii. How would the LGIA/LGIP approach fit with the current standard of demonstrating plans and milestones on a case-by-case basis to receive priority rights for future phases of a generation project? Does the existing<E T="03">pro forma</E>LGIA/LGIP contain a sufficiently clear procedure,<E T="03">e.g.,</E>in submitting and maintaining a valid interconnection request and meeting the milestones set forth in Appendix B, such that this procedure might serve a similar purpose as the current standard of demonstrating specific plans and milestones?</P>
          <P>iii. If no separate priority rights request for a generation developer to establish capacity rights for its interconnection facilities would be necessary, what are the benefits and/or drawbacks of such an approach?</P>

          <P>iv. How would adopting an LGIA/LGIP framework otherwise affect generation developers seeking priority rights on their interconnection customer's interconnection facilities for their phased generation projects? If the generation developer plans to eventually use currently unused capacity on interconnection facilities, should the<E T="03">pro forma</E>LGIA be modified to require that capacity on interconnection facilities be made available for third-party use until the generation developer is ready to use that capacity?</P>
        </EXTRACT>
        <HD SOURCE="HD1">III. Comment Procedures</HD>

        <P>43. The Commission invites interested persons to submit comments on the matters, issues and specific questions identified in this notice. Comments are due 45 days from publication in the<E T="04">Federal Register</E>. Comments must refer to Docket No. AD12-14, and must include the commenter's name, the organization they represent, if applicable, and their address in their comments.<PRTPAGE P="24655"/>
        </P>

        <P>44. 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>45. Commenters unable to file comments electronically must mail or hand deliver an original and copy of their comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street NE., Washington, DC 20426.</P>
        <P>46. 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">IV. Document Availability</HD>

        <P>47. In addition to publishing the full text of this document in the<E T="04">Federal Register</E>, the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the Internet through FERC's Home Page (<E T="03">http://www.ferc.gov</E>) and in FERC's Public Reference Room during normal business hours (8:30 a.m. to 5 p.m. Eastern time) at 888 First Street NE., Room 2A, Washington, DC 20426.</P>
        <P>48. 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>49. 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.</P>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
        <HD SOURCE="HD1">Appendix A</HD>
        <EXTRACT>
          <HD SOURCE="HD1">List of Commenters and Participants in Docket No. AD11-11-000</HD>
          <FP SOURCE="FP-1">Adam Wenner *</FP>
          <FP SOURCE="FP-1">Allete, Inc. d/b/a Minnesota Power</FP>
          <FP SOURCE="FP-1">American Wind Energy Association (AWEA)</FP>
          <FP SOURCE="FP-1">Anbaric Transmission (Anbaric)</FP>
          <FP SOURCE="FP-1">BP Wind Energy North America (BP Wind)</FP>
          <FP SOURCE="FP-1">California High Wind Partners (CAHW)</FP>
          <FP SOURCE="FP-1">Clean Line Energy Partners (Clean Line)</FP>
          <FP SOURCE="FP-1">Duke Energy (Duke)</FP>
          <FP SOURCE="FP-1">Edison Mission Energy (Edison Mission)</FP>
          <FP SOURCE="FP-1">Electric Power Supply Association (EPSA)</FP>
          <FP SOURCE="FP-1">First Wind Holdings (First Wind)</FP>
          <FP SOURCE="FP-1">Gradient Resources (Gradient)</FP>
          <FP SOURCE="FP-1">Grasslands Renewable Energy (Grasslands)</FP>
          <FP SOURCE="FP-1">Horizon Wind Energy LLC (Horizon)</FP>
          <FP SOURCE="FP-1">Invenergy Wind &amp; Invenergy Thermal (Invenergy)</FP>
          <FP SOURCE="FP-1">LS Power Transmission (LS Power)</FP>
          <FP SOURCE="FP-1">MidAmerican Energy Holdings Co. (MidAmerican)</FP>
          <FP SOURCE="FP-1">National Grid USA (National Grid)</FP>
          <FP SOURCE="FP-1">NextEra Energy Resources (NextEra)</FP>
          <FP SOURCE="FP-1">Northeast Utilities (Northeast)</FP>
          <FP SOURCE="FP-1">Northwestern Energy (Northwestern)</FP>
          <FP SOURCE="FP-1">Pattern Transmission (Pattern)</FP>
          <FP SOURCE="FP-1">Puget Sound Energy (Puget)</FP>
          <FP SOURCE="FP-1">San Diego Gas &amp; Electric (SDG&amp;E)</FP>
          <FP SOURCE="FP-1">Sempra Generation (Sempra)</FP>
          <FP SOURCE="FP-1">Shell Wind Energy (Shell)</FP>
          <FP SOURCE="FP-1">Southern California Edison (SCE)</FP>
          <FP SOURCE="FP-1">Southern Co. (Southern)</FP>
          <FP SOURCE="FP-1">Tonbridge Power (Tonbridge)</FP>
          <FP SOURCE="FP-1">Transmission Access Policy Study Group (TAPS)</FP>
          <FP SOURCE="FP-1">Transmission Developers, Inc. (TDI)</FP>
          <FP SOURCE="FP-1">United Illuminating Co. (United)</FP>
          <FP SOURCE="FP-1">Western Independent Transmission Group (WITG)</FP>
          <FP SOURCE="FP-1">Zephyr Power Transmission (Zephyr)</FP>
          
          <P>* Comments filed after due date.</P>
        </EXTRACT>
        <HD SOURCE="HD1">Appendix B</HD>
        <GPH DEEP="237" SPAN="3">
          <GID>EP25AP12.003</GID>
        </GPH>
        <EXTRACT>

          <P>Order No. 2003 addresses third party use of Transmission Provider Interconnection Facilities, which are those that are owned, controlled, or operated by the Transmission Provider. Order No. 2003 permits the interconnection customer to build, own, control, and operate interconnection facilities, which are then defined as Interconnection Customer Interconnection Facilities under the LGIP/LGIA, but Order No. 2003 does not address third party use of Interconnection Customer Interconnection Facilities. With a goal of ensuring that a third party generator (G2 in the above schematic) may be able to interconnect to Interconnection Customer Interconnection Facilities that in some instances have been 30, 50, or even hundreds of miles long, the<PRTPAGE P="24656"/>Commission has in a series of recent cases considered these Interconnection Customer Interconnection Facilities to be open access transmission facilities and required that the original developer (G1 in the above schematic) file an OATT within 60 days of a request for service on these facilities. In light of comments received, this NOI seeks feedback on whether the filing of an OATT, modifications to the LGIA/LGIP, or other means are better for addressing third-party access to facilities at issue here.</P>
        </EXTRACT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9848 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
        <CFR>19 CFR Part 101</CFR>
        <DEPDOC>[Docket No. USCBP-2012-0006]</DEPDOC>
        <SUBJECT>Extension of Port Limits of Indianapolis, IN</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. Customs and Border Protection, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>U.S. Customs and Border Protection (CBP) is proposing to extend the geographical limits of the port of entry of Indianapolis, Indiana. The proposed extension will make the boundaries more easily identifiable to the public and will allow for uniform and continuous service to the extended area of Indianapolis, Indiana. The proposed change is part of CBP's continuing program to use its personnel, facilities, and resources more efficiently, and to provide better service to carriers, importers, and the general public.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received on or before June 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Please submit comments, identified by docket number, by one of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments via docket number USCBP-2012-0006.</P>
          <P>•<E T="03">Mail:</E>Border Security Regulations Branch, Office of International Trade, U.S. Customs and Border Protection, Mint Annex, 799 9th Street NW., Washington, DC 20229-1179.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number for this rulemaking. All comments received will be posted without change to<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, go to<E T="03">http://www.regulations.gov.</E>Comments submitted will be available for public inspection in accordance with the Freedom of Information Act (5 U.S.C. 552) and 19 CFR 103.11(b) on normal business days between the hours of 9 a.m. and 4:30 p.m. at the Border Security Regulations Branch, Office of International Trade, U.S. Customs and Border Protection, 799 9th Street NW., 5th Floor, Washington, DC. Arrangements to inspect submitted comments should be made in advance by calling Mr. Joseph Clark at (202) 325-0118.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Roger Kaplan, Office of Field Operations, U.S. Customs and Border Protection, (202) 325-4543, or by email at<E T="03">Roger.Kaplan@dhs.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Public Participation</HD>
        <P>Interested persons are invited to participate in this rulemaking by submitting written data, views, or arguments on all aspects of the proposed rule. CBP also invites comments that relate to the economic, environmental, or federalism effects that might result from this proposed rule. Comments that will provide the most assistance to CBP will reference a specific portion of the proposed rule, explain the reason for any recommended change, and include data, information, or authority that support such recommended change.</P>
        <HD SOURCE="HD1">II. Background</HD>
        <P>As part of its continuing efforts to use CBP's personnel, facilities, and resources more efficiently, and to provide better service to carriers, importers, and the general public, CBP is proposing to extend the limits of the Indianapolis, Indiana, port of entry. CBP ports of entry are locations where CBP officers and employees are assigned to accept entries of merchandise, clear passengers, collect duties, and enforce the various provisions of customs, immigration, agriculture, and related U.S. laws at the border. The term “port of entry” is used in the Code of Federal Regulations (CFR) in title 8 for immigration purposes and in title 19 for customs purposes. For customs purposes, CBP regulations list designated CBP ports of entry and the limits of each port in section 101.3(b)(1) of title 19 (19 CFR 101.3(b)(1)).<SU>1</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>1</SU>Ports of entry for immigration purposes are currently listed at 8 CFR 100.4.</P>
        </FTNT>
        <P>Indianapolis was designated as a customs port of entry by the President's message of March 3, 1913, concerning a reorganization of the customs service pursuant to the Act of August 24, 1912 (37 Stat. 434; 19 U.S.C. 1). Although CBP is not aware of any document which specifically sets forth the geographical boundaries of the Indianapolis port of entry, the port limits are generally understood to be the corporate limits of the city of Indianapolis.</P>
        <P>In 1970, by act of the Indiana legislature, the city of Indianapolis consolidated with the surrounding county of Marion. However, four municipalities within Marion County remained excluded from the corporate limits of Indianapolis. Additionally, members of the trade community have expressed a need for CBP services in areas west and south of the city limits.</P>
        <P>CBP would like to extend the boundaries of the port of entry of Indianapolis, Indiana, to include all the territory within the boundaries of Marion County, Indiana, as well as portions of the neighboring counties of Boone, Hendricks, and Johnson. This update is necessary to clarify the geographic limits of the port. The update will also allow CBP to better serve the public in the greater Indianapolis area, by providing regular service to (1) municipalities within Indianapolis that are not technically within the city limits, and to (2) locations to the immediate west and south of the city. The proposed change in the boundaries of the port of Indianapolis, Indiana, will not result in a change in the service that is provided to the public by the port and will not require a change in the staffing or workload at the port.</P>
        <HD SOURCE="HD1">III. Proposed Port Limits of Indianapolis, Indiana</HD>
        <P>The new port limits of Indianapolis, Indiana, are proposed as follows:</P>
        <P>In the State of Indiana, all of Marion County; that part of Boone County which is west of Interstate Route 65 and east of State Route 39; that part of Hendricks County which is east of State Route 39; and that part of Johnson County which is east of State Route 37, north of State Route 144, and west of Interstate Route 65.</P>
        <P>CBP has included a map of the proposed port limits in the docket as “Attachment: Port of Entry of Indianapolis—Proposed Limits.”</P>
        <HD SOURCE="HD1">IV. Statutory and Regulatory Reviews</HD>
        <HD SOURCE="HD2">A. Executive Orders 12866 and 13563</HD>

        <P>DHS does not consider this proposed rule to be a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive<PRTPAGE P="24657"/>Order 13563. The proposed change is intended to expand the geographical boundaries of the Indianapolis, Indiana, port of entry and make the boundaries more easily identifiable to the public. There are no new costs to the public associated with this rule, and the rule does not otherwise implicate the factors set forth in section 3(f) of Executive Order 12866. Accordingly, this rule has not been submitted to the Office of Management and Budget for review.</P>
        <HD SOURCE="HD2">B. Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>) requires federal agencies to examine the impact a rule would have on small entities. A small entity may be a small business (defined as any independently owned and operated business not dominant in its field that qualifies as a small business per the Small Business Act); a small not-for-profit organization; or a small governmental jurisdiction (locality with fewer than 50,000 people).</P>
        <P>This proposed rule merely expands the limits of an existing port of entry and does not impose any new costs on the public. Accordingly, we certify that this rule would not have a significant economic impact on a substantial number of small entities.</P>
        <HD SOURCE="HD2">C. Signing Authority</HD>
        <P>The signing authority for this document falls under 19 CFR 0.2(a) because the extension of port limits is not within the bounds of those regulations for which the Secretary of the Treasury has retained sole authority. Accordingly, this notice of proposed rulemaking may be signed by the Secretary of Homeland Security (or her delegate).</P>
        <HD SOURCE="HD1">V. Authority</HD>
        <P>This change is proposed under the authority of 5 U.S.C. 301; 6 U.S.C. 203; 19 U.S.C. 2 &amp; note, 66, and 1624.</P>
        <HD SOURCE="HD1">VI. Proposed Amendment to the Regulations</HD>
        <P>If the proposed port limits are adopted, CBP will amend the list of CBP ports of entry at 19 CFR 101.3(b)(1) to reflect the new description of the limits of the Indianapolis, Indiana, port of entry.</P>
        <SIG>
          <DATED>Dated: April 10, 2012.</DATED>
          <NAME>Janet Napolitano,</NAME>
          <TITLE>Secretary of Homeland Security.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9996 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9111-14-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
        <SUBAGY>Internal Revenue Service</SUBAGY>
        <CFR>26 CFR Part 1</CFR>
        <DEPDOC>[REG-137589-07]</DEPDOC>
        <RIN>RIN 1545-BH60</RIN>
        <SUBJECT>Local Lodging Expenses</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Internal Revenue Service (IRS), Treasury.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This document contains proposed regulations relating to the deductibility of expenses for lodging when not traveling away from home (local lodging). The regulations affect taxpayers who pay or incur expenses for local lodging.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments or a request for a public hearing must be received by July 24, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Send submissions to CC:PA:LPD:PR (REG-137589-07), room 5203, Internal Revenue Service, P.O. Box 7604, Ben Franklin Station, Washington, DC 20044. Submissions may be hand delivered Monday through Friday between the hours of 8 a.m. and 4 p.m. to CC:PA:LPD:PR (REG-137589-07), Courier's Desk, Internal Revenue Service, 1111 Constitution Avenue NW., Washington, DC. Alternatively, taxpayers may submit comments electronically via the Federal eRulemaking Portal at<E T="03">http://www.regulations.gov</E>(IRS REG-137589-07).</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Concerning the proposed regulations, R. Matthew Kelley, (202) 622-7900; concerning submission of comments or a request for a hearing, Funmi Taylor, (202) 622-7180 (not toll-free numbers).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>
        <P>This document contains proposed amendments to 26 CFR part 1 relating to the deduction of local lodging expenses.</P>
        <P>Section 1.262-1 of the Income Tax Regulations generally disallows a deduction for local lodging expenses. The proposed regulations allow taxpayers to deduct local lodging expenses as ordinary and necessary business expenses in appropriate circumstances.</P>
        <HD SOURCE="HD2">Business Expenses Generally</HD>

        <P>Section 162(a) of the Internal Revenue Code (Code) allows a deduction for all of the ordinary and necessary expenses paid or incurred during the taxable year in carrying on any trade or business. Whether an expense is ordinary and necessary is a question of fact. In general, a trade or business expense is ordinary if it is normal, usual, or customary in the taxpayer's type of business. An expense is necessary if it is appropriate and helpful for the development of the taxpayer's business. See<E T="03">Commissioner</E>v.<E T="03">Heininger,</E>320 U.S. 467, 475 (1943). An expense that serves primarily to furnish the taxpayer with a social or personal benefit, and is only secondarily related to business, is not a necessary business expense under section 162(a).</P>
        <HD SOURCE="HD2">Employee Expenses</HD>

        <P>An expense that an employee must bear as a condition of employment may be a deductible employee business expense. See<E T="03">Sibla</E>v.<E T="03">Commissioner,</E>611 F.2d 1260 (9th Cir. 1980), acq. (1985-2 CB viii) (contributions to firemen's mess required as a condition of employment are deductible business expenses). However, expenses that primarily are for the employee's personal benefit or convenience are not deductible employee business expenses. See<E T="03">Commissioner</E>v.<E T="03">Flowers,</E>326 U.S. 465 (1946) (a taxpayer's expenses for lodging near his principal work location, to avoid a long commute to and from his primary residence, were nondeductible personal expenses incurred solely because of the taxpayer's decision to maintain his primary residence far from his work location).</P>
        <HD SOURCE="HD2">Deductible Employee Expenses</HD>
        <P>The tax consequences to an employee who is reimbursed by an employer for an expense, or who receives property or services resulting from an employer's payment of an expense, depend on whether the expense is one that would have been deductible if paid directly by the employee.</P>
        <P>For example, if an employee pays an expense and an employer reimburses the employee under a reimbursement or other expense allowance arrangement, the reimbursement is not includible in the employee's income if it is made under an accountable plan. A reimbursement is treated as made under an accountable plan only if it is made for an expense that would be deductible by the employee under sections 161 through 199. See sections 62(a)(2)(A) and 62(c).</P>

        <P>Similarly, if an employer provides property or services to an employee in the course of business, the value of the benefit to the employee is excludable from the employee's income if the benefit constitutes a working condition fringe under section 132(a)(3). A working condition fringe is defined as<PRTPAGE P="24658"/>property or services provided to an employee to the extent that, if the employee paid for the property or services, the payment would be allowable as a deduction to the employee under section 162 or 167.</P>
        <HD SOURCE="HD2">Nondeductible Personal Expenses</HD>
        <P>Section 262(a) provides that, except as otherwise provided in Chapter 1 of the Code, no deduction is allowed for personal, living, or family expenses.</P>
        <P>Section 1.262-1(b)(5) provides, as examples of personal, living, and family expenses, that the costs of a taxpayer's meals incurred when not traveling away from home (local meals) are generally nondeductible personal expenses. Local meal expenses may be deducted, however, if they otherwise qualify as ordinary and necessary business expenses under section 162 or as expenses for the production of income under section 212. In contrast, lodging expenses incurred when not traveling away from home (local lodging) are nondeductible personal expenses. Thus, local lodging expenses that would otherwise qualify as trade or business expenses under section 162 or as production of income expenses under section 212 are not deductible under the current general rule.</P>
        <HD SOURCE="HD2">Local Lodging Expenses</HD>
        <P>The cost of local lodging that a taxpayer pays or incurs primarily for the taxpayer's convenience or personal benefit is not an ordinary and necessary expense of a business or income-producing activity. Similarly, the cost of local lodging provided to an employee by an employer for the employee's convenience or personal benefit would not be deductible by the employee if the employee paid the cost directly. Therefore, the value of the lodging under those circumstances is not excludible from the gross income of an employee as a working condition fringe under section 132(a)(3), and reimbursement for the cost of the lodging under those circumstances is not a payment under an accountable plan under § 1.62-2(c). Consequently, unless excludible on another basis, the value of the lodging or the amount of reimbursement under those circumstances is includible in the employee's income under section 61 as compensation for services. See §§ 1.61-21(a)(3), 1.62-2, and 1.132-1.</P>

        <P>The cost of local lodging is for the convenience or personal benefit of an employee (or other recipient) if, for example, the lodging is provided to the employee (1) as additional compensation, such as to provide a weekend at a luxury hotel or resort; (2) to enable the employee to avoid a long-distance commute (<E T="03">Commissioner</E>v.<E T="03">Flowers</E>); (3) because the employee is required to work overtime (<E T="03">Coombs</E>v.<E T="03">Commissioner,</E>608 F.2d 1269, 1273 (9th Cir. 1979)); (4) as housing for a recently relocated employee while the employee searches for permanent housing; or (5) for the employee's indefinite personal use (<E T="03">International Artists, Ltd,</E>v.<E T="03">Commissioner,</E>55 T.C. 94 (1970)). An employer may deduct the costs the employer incurs in providing the lodging in each of these cases under section 162(a) as compensation for services. See §§ 1.162-7(a) and 1.162-25T. However, because the primary purpose of the lodging is to provide the employee with a personal benefit, if the employee pays the cost of the lodging directly, the employee may not deduct the expense as an ordinary and necessary business expense under section 162(a). Therefore, a cash reimbursement of the cost is not excludible from the employee's gross income under section 62(c) and the value of the lodging is not excludible from the employee's gross income under section 132(d) as a working condition fringe.</P>

        <P>Expenditures for local lodging may qualify as deductible ordinary and necessary expenses under appropriate circumstances if all other requirements of section 162 are met. For example, an employer may require its employees to stay at a local hotel for the<E T="03">bona fide</E>purpose of facilitating training or team building directly connected with the employer's trade or business. Similarly, a professional sports team may require its employees (players and coaches) to stay at a local hotel the night before a home game to ensure physical preparedness and allow for last minute training. Under these circumstances, the cost of the lodging is primarily for the business purposes of the employer and not to provide a personal benefit to the employees. The cost of the lodging would be deductible by an employee under section 162 if the employee paid the cost directly, and thus the value of the lodging may be excluded from the employee's gross income as a working condition fringe if other requirements are satisfied. Similarly, a payment from the employer reimbursing the employee for the cost of the lodging may be excluded from the employee's gross income as a payment under an accountable plan if all the requirements of an accountable plan are met.</P>

        <P>Notice 2007-47 (2007-1 CB 1393) (see § 601.601(d)(2) of this chapter) advises taxpayers that the IRS and the Treasury Department intend to amend the treatment of the costs of a taxpayer's local lodging under § 1.262-1(b)(5). The notice provides that, pending issuance of additional published guidance, the IRS will not apply § 1.262-1(b)(5) to expenses for local lodging of an employee that an employer provides to the employee or requires the employee to obtain, if: (1) The lodging is provided on a temporary basis; (2) the lodging is necessary for the employee to participate in or be available for a<E T="03">bona fide</E>business meeting or function of the employer; and (3) the expenses are otherwise deductible by the employee, or would be deductible if paid by the employee, under section 162(a).</P>
        <HD SOURCE="HD1">Explanation of Provisions</HD>
        <P>These regulations propose to amend the regulations under sections 162 and 262. The proposed regulations under section 162 provide that expenses paid or incurred for local lodging may be deductible as ordinary and necessary expenses of a taxpayer's trade or business, including the trade or business of being an employee. The proposed regulations provide a safe harbor for certain local lodging at a business meeting, conference, or other activity or function. Other local lodging expenses may be deductible as business expenses depending on the facts and circumstances.</P>
        <P>The proposed regulations under section 262 provide that a taxpayer's costs incurred for local lodging are personal expenses unless the expenses are deductible under section 162. Comments are specifically requested on whether the section 262 regulations should be amended to provide that local lodging expenses are not personal expenses if they are deductible under section 212.</P>
        <P>The proposed regulations also amend the regulations under section 262 to remove references to section 217 that are obsolete. Section 217 was amended by the Revenue Reconciliation Act of 1993, Public Law 103-66 (107 Stat. 417). Under the amendments, lodging when not traveling away from home and meals are not deductible as moving expenses.</P>
        <HD SOURCE="HD1">Effective/Applicability Date</HD>

        <P>The regulations are proposed to apply to expenses paid or incurred on or after the date these regulations are published as final regulations in the<E T="04">Federal Register</E>. However, until these regulations are published as final regulations in the<E T="04">Federal Register</E>, taxpayers may apply the proposed regulations to expenses paid or incurred in taxable years for which the period of limitation on credit or refund under section 6511 has not expired.<PRTPAGE P="24659"/>
        </P>
        <HD SOURCE="HD1">Effect on Other Documents</HD>
        <P>Notice 2007-47 is obsoleted as of April 25, 2012.</P>
        <HD SOURCE="HD1">Special Analyses</HD>
        <P>This notice of proposed rulemaking 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 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, this notice of proposed rulemaking has been submitted to the Chief Counsel for Advocacy of the Small Business Administration for comment on its impact on small business.</P>
        <HD SOURCE="HD1">Comments and Requests for a Public Hearing</HD>

        <P>Before these proposed regulations are adopted as final regulations, consideration will be given to any comments that are submitted timely to the IRS as prescribed in this preamble under the “Addresses” heading. The Treasury Department and the IRS invite comments on all aspects of the proposed rules. All comments will be available for public inspection and copying. A public hearing may be scheduled if requested in writing by any person who timely submits comments. If a public hearing is scheduled, notice of the date, time, and place for the public hearing will be published in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD1">Drafting Information</HD>
        <P>The principal author of these regulations is R. Matthew Kelley of the Office of Associate Chief Counsel (Income Tax and Accounting). However, other personnel from the IRS and 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">Proposed Amendments to the Regulations</HD>
        <P>Accordingly, 26 CFR part 1 is proposed to be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 1—INCOME TAXES</HD>
          <P>
            <E T="04">Paragraph 1.</E>The authority citation for part 1 continues to read in part as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>26 U.S.C. 7805 * * *</P>
          </AUTH>
          
          <P>
            <E T="04">Par. 2.</E>Section 1.162-31 is added to read as follows:</P>
          <SECTION>
            <SECTNO>§ 1.162-31</SECTNO>
            <SUBJECT>Expenses paid or incurred for lodging when not traveling away from home.</SUBJECT>
            <P>(a)<E T="03">In general.</E>Expenses paid or incurred for lodging when not traveling away from home (local lodging) generally are personal, living, or family expenses that are nondeductible under section 262(a). Under certain circumstances, however, expenses for local lodging may be deductible under section 162(a) as ordinary and necessary expenses paid or incurred in connection with carrying on a taxpayer's trade or business, including a trade or business as an employee. Whether local lodging expenses are paid or incurred in carrying on a taxpayer's trade or business is determined under all the facts and circumstances. One factor is whether the taxpayer incurs the expense because of a<E T="03">bona fide</E>condition or requirement of employment imposed by the taxpayer's employer. Expenses paid or incurred for local lodging that is lavish or extravagant under the circumstances or that primarily provides an individual with a social or personal benefit are not incurred in carrying on a taxpayer's trade or business.</P>
            <P>(b)<E T="03">Safe harbor for local lodging at business meetings and conferences.</E>An individual's expenses for local lodging will be treated as ordinary and necessary business expenses if—</P>

            <P>(1) The lodging is necessary for the individual to participate fully in or be available for a<E T="03">bona fide</E>business meeting, conference, training activity, or other business function;</P>
            <P>(2) The lodging is for a period that does not exceed five calendar days and does not recur more frequently than once per calendar quarter;</P>
            <P>(3) If the individual is an employee, the employee's employer requires the employee to remain at the activity or function overnight; and</P>
            <P>(4) The lodging is not lavish or extravagant under the circumstances and does not provide any significant element of personal pleasure, recreation, or benefit.</P>
            <P>(c)<E T="03">Examples.</E>The provisions of this section are illustrated by the following examples. In each example the employer and the employees meet all other requirements (such as substantiation) for deductibility of the expense and for exclusion from income as a working condition fringe or payment under an accountable plan.</P>
            
            <EXAMPLE>
              <HD SOURCE="HED">
                <E T="03">Example 1.</E>
              </HD>

              <P>(i) Employer conducts training for its employees at a hotel near Employer's main office. The training is directly connected with Employer's trade or business. Some employees attending the training are traveling away from home and some employees are not traveling away from home. Employer requires all employees attending the training to remain at the hotel overnight for the<E T="03">bona fide</E>purpose of facilitating the training. Employer pays the costs of the lodging at the hotel directly to the hotel and does not treat the value as compensation to the employees.</P>
              <P>(ii) Employer has a noncompensatory business purpose for paying the lodging expenses. Employer is not paying the expenses primarily to provide a social or personal benefit to the employees. If the employees who are not traveling away from home had paid for their own lodging, the expenses would have been deductible under section 162(a) as ordinary and necessary business expenses of the employees. Therefore, the value of the lodging is excluded from the employees' income as a working condition fringe under section 132(a) and (d).</P>
              <P>(iii) Employer may deduct the lodging expenses, including lodging for employees who are not traveling away from home, as ordinary and necessary business expenses under section 162(a).</P>
            </EXAMPLE>
            <EXAMPLE>
              <HD SOURCE="HED">
                <E T="03">Example 2.</E>
              </HD>
              <P>(i) The facts are the same as in<E T="03">Example 1,</E>except that the employees pay the cost of their lodging at the hotel directly to the hotel, Employer reimburses the employees for the cost of the lodging, and Employer does not treat the reimbursement as compensation to the employees.</P>
              <P>(ii) Employer is reimbursing the lodging expenses for a noncompensatory business purpose and not primarily to provide a social or personal benefit to the employees. The employees incur the expenses in performing services for the employer. If Employer had not reimbursed the employees who are not traveling away from home for the cost of the lodging, the expenses would have been deductible under section 162(a) as ordinary and necessary business expenses of the employees. Therefore, the reimbursements to the employees are made under an accountable plan and are excluded from the employees' gross income.</P>
              <P>(iii) Employer may deduct the lodging expense reimbursements, including reimbursements for employees who are not traveling away from home, as ordinary and necessary business expenses under section 162(a).</P>
            </EXAMPLE>
            <EXAMPLE>
              <HD SOURCE="HED">
                <E T="03">Example 3.</E>
              </HD>
              <P>(i) Employer is a professional sports team. Employer requires its employees (players and coaches) to stay at a local hotel the night before a home game to conduct last minute training and ensure the physical preparedness of the players. Employer pays the lodging expenses directly to the hotel and does not treat the value as compensation to the employees.</P>

              <P>(ii) Employer has a noncompensatory business purpose for paying the lodging expenses. Employer is not paying the lodging expenses primarily to provide a social or personal benefit to the employees. If the employees had paid for their own lodging, the expenses would have been deductible by the employees under section 162(a) as ordinary and necessary business expenses.<PRTPAGE P="24660"/>Therefore, the value of the lodging is excluded from the employees' income as a working condition fringe.</P>
              <P>(iii) Employer may deduct the expenses for lodging the players and coaches at the hotel as ordinary and necessary business expenses under section 162(a).</P>
            </EXAMPLE>
            <EXAMPLE>
              <HD SOURCE="HED">
                <E T="03">Example 4.</E>
              </HD>
              <P>(i) Employer hires Employee, who currently resides 500 miles from Employer's business premises. Employer pays for temporary lodging for Employee near Employer's business premises while Employee searches for a residence.</P>
              <P>(ii) Employer is paying the temporary lodging expense primarily to provide a personal benefit to Employee by providing housing while Employee searches for a residence. Employer incurs the expense only as additional compensation and not for a noncompensatory business purpose. If Employee paid the temporary lodging expense, the expense would not be an ordinary and necessary employee business expense under section 162(a) because the lodging primarily provides a personal benefit to Employee. Therefore, the value of the lodging is includible in Employee's gross income as additional compensation.</P>
              <P>(iii) Employer may deduct the lodging expenses as ordinary and necessary business expenses under section 162(a) and § 1.162-25T.</P>
            </EXAMPLE>
            <EXAMPLE>
              <HD SOURCE="HED">Example 5.</HD>
              <P>(i) Employee normally travels two hours each way between her home and her office. Employee is working on a project that requires Employee to work late hours. In order to maximize Employee's availability to work on the project, Employer provides Employee with lodging at a hotel near the office.</P>
              <P>(ii) Employer is paying the temporary lodging expense primarily to provide a personal benefit to Employee by relieving her of the daily commute to her residence. Employer incurs the expense only as additional compensation and not for a noncompensatory business purpose. If Employee paid the temporary lodging expense, the expense would not be an ordinary and necessary business expense under section 162(a) because the lodging primarily provides a personal benefit to Employee. Therefore, the value of the lodging is includible in Employee's gross income as additional compensation.</P>
              <P>(iii) Employer may deduct the lodging expenses as ordinary and necessary business expenses under section 162(a) and § 1.162-25T.</P>
            </EXAMPLE>
            <EXAMPLE>
              <HD SOURCE="HED">Example 6.</HD>
              <P>(i) Employer requires an employee to be “on duty” each night to respond quickly to emergencies that may occur outside of normal working hours. Employees who work daytime hours each serve a “duty shift” once each month in addition to their normal work schedule. Emergencies that require the duty shift employee to respond occur regularly. Employer has no sleeping facilities on its business premises and pays for a hotel room nearby where the duty shift employee stays until called to respond to an emergency.</P>
              <P>(ii) Employer has a noncompensatory business purpose for paying the lodging expenses. Employer is not providing the lodging to duty shift employees primarily to provide a social or personal benefit to the employees. If the employees had paid for their lodging, the expenses would have been deductible by the employees under section 162(a) as ordinary and necessary business expenses. Therefore, the value of the lodging is excluded from the employees' income as a working condition fringe.</P>
              <P>(iii) Employer may deduct the lodging expenses as ordinary and necessary business expenses under section 162(a).</P>
              <P>(d)<E T="03">Effective/applicability date.</E>This section applies to expenses paid or incurred on or after the date these regulations are published as final regulations in the<E T="04">Federal Register</E>. However, until these proposed regulations are published as final regulations in the<E T="04">Federal Register</E>, taxpayers may apply the proposed regulations to local lodging expenses that are paid or incurred in taxable years for which the period of limitation on credit or refund under section 6511 has not expired.</P>
            </EXAMPLE>
            
            <P>
              <E T="04">Par. 3.</E>In § 1.262-1, paragraph (b)(5) is amended to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 1.262-1</SECTNO>
            <SUBJECT>Personal, living, and family expenses.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>

            <P>(5) Expenses incurred in traveling away from home (which include transportation expenses, meals, and lodging) and any other transportation expenses are not deductible unless they qualify as expenses deductible under section 162 (relating to trade or business expenses), section 170 (relating to charitable contributions), section 212 (relating to expenses for production of income), section 213 (relating to medical expenses), or section 217 (relating to moving expenses), and the regulations under those sections. The taxpayer's costs of commuting to his place of business or employment are personal expenses and do not qualify as deductible expenses. For expenses paid or incurred before the date these regulations are published as final regulations in the<E T="04">Federal Register</E>, a taxpayer's expenses for lodging when not traveling away from home (local lodging) are nondeductible personal expenses. For expenses paid or incurred on or after the date these regulations are published as final regulations in the<E T="04">Federal Register</E>, a taxpayer's expenses for local lodging are personal expenses and are not deductible unless they qualify as deductible expenses under section 162. However, until these regulations are published as final regulations in the<E T="04">Federal Register</E>, taxpayers may deduct local lodging expenses that qualify under section 162 and are paid or incurred in taxable years for which the period of limitation on credit or refund under section 6511 has not expired. Except as permitted under section 162 or 212, the costs of a taxpayer's meals not incurred in traveling away from home are nondeductible personal expenses.</P>
            <STARS/>
          </SECTION>
          <SIG>
            <NAME>Steven T. Miller,</NAME>
            <TITLE>Deputy Commissioner for Services and Enforcement.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9885 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4830-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
        <SUBAGY>Internal Revenue Service</SUBAGY>
        <CFR>26 CFR Part 31</CFR>
        <DEPDOC>[REG-151687-10]</DEPDOC>
        <RIN>RIN 1545-BJ98</RIN>
        <SUBJECT>Withholding on Payments by Government Entities to Persons Providing Property or Services</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Internal Revenue Service (IRS), Treasury.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Withdrawal of notice of proposed rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This document withdraws a notice of proposed rulemaking relating to withholding by government entities on payments to persons providing property or services. The proposed regulations are withdrawn because Public Law 112-56, “The 3% Withholding Repeal and Job Creation Act,” repealed the provision of the Internal Revenue Code underlying the proposed rules. The guidance affects government entities that would have been required to withhold and report tax from payments to persons providing property or services and also affects the persons receiving payments for property or services from these government entities.</P>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>A.G. Kelley, (202) 622-6040 (not a toll-free number).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>
        <P>Section 3402(t) of the Internal Revenue Code (Code) was added by section 511 of the Tax Increase Prevention and Reconciliation Act of 2005, Public Law 109-222 (TIPRA), 120 Stat. 345, which was enacted on May 17, 2006.</P>
        <P>Section 102 of the 3% Withholding Repeal and Job Creation Act (Pub. L. 112-56, 125 Stat. 711), which was enacted on November 21, 2011, repealed section 3402(t) of the Code.</P>

        <P>The Treasury Department and the IRS issued proposed regulations under section 3402(t), published in the<PRTPAGE P="24661"/>
          <E T="04">Federal Register</E>on May 9, 2011 (REG-151687-10, 76 FR 26678, 2011-23 IRB 867). This document withdraws those proposed regulations in light of the repeal of section 3402(t).</P>

        <P>At the same time as the issuance of the proposed regulations, the Treasury Department and the IRS issued final regulations under sections 3402(t), 3406, 6011, 6051, 6071, and 6302 of the Code that were published in the<E T="04">Federal Register</E>on May 9, 2011 (TD 9524, 76 FR 26583, 2011-23 IRB 843). A related document (TD 9586, REG-148417-11) removes the final regulations under section 3402(t) and makes conforming amendments to the regulations under other sections reflecting that removal.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 26 CFR Part 31</HD>
          <P>Employment taxes, Fishing vessels, Gambling, Income taxes, Penalties, Pensions, Railroad retirement, Reporting and recordkeeping requirements, Social Security, Unemployment compensation.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Withdrawal of Notice of Proposed Rulemaking</HD>

        <P>Accordingly, under the authority of 26 U.S.C. 7805, the notice of proposed rulemaking (REG-151687-10) that was published in the<E T="04">Federal Register</E>on May 9, 2011 (76 FR 26678) is withdrawn.</P>
        <SIG>
          <NAME>Steven T. Miller,</NAME>
          <TITLE>Deputy Commissioner for Services and Enforcement.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9886 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4830-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
        <SUBAGY>Office of Surface Mining Reclamation and Enforcement</SUBAGY>
        <CFR>30 CFR Part 934</CFR>
        <DEPDOC>[SATS No. ND-053-FOR; Docket ID OSM-2012-0006]</DEPDOC>
        <SUBJECT>North Dakota Regulatory Program</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of Surface Mining Reclamation and Enforcement, Interior.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule; public comment period and opportunity for public hearing on proposed amendment.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We are announcing receipt of a proposed amendment to the North Dakota regulatory program (hereinafter, the “North Dakota program”) under the Surface Mining Control and Reclamation Act of 1977 (“SMCRA” or “the Act”). North Dakota proposes changes to the North Dakota Administrative Code to address letter of credit provisions in the collateral bond rule under Administrative Code Section 69-5.2-12-04. The changes involve the financial information and notices that banks issuing a letter of credit must provide to the North Dakota Public Service Commission (hereinafter, the “Commission”).</P>
          <P>This document gives the times and locations that the North Dakota program and proposed amendment to that program are available for your inspection, the comment period during which you may submit written comments on the amendment, and the procedures that we will follow for the public hearing, if one is requested.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>We will accept written comments on this amendment until 4 p.m., m.d.t. May 25, 2012. If requested, we will hold a public hearing on the amendment on May 21, 2012. We will accept requests to speak until 4 p.m., m.d.t. on May 10, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments by either of the following two methods:</P>
          <P>Federal eRulemaking Portal:<E T="03">www.regulations.gov.</E>This proposed rule has been assigned Docket ID: OSM-2012-0006. If you would like to submit comments through the Federal eRulemaking Portal, go to<E T="03">www.regulations.gov</E>and follow the instructions.</P>
          <P>• Mail/Hand Delivery/Courier:</P>
          <P>Jeffrey Fleischman, Director, Casper Field Office, Office of Surface Mining Reclamation and Enforcement, Dick Cheney Federal Building, POB 11018, 150 East B Street, Casper, Wyoming 82601-1018.</P>

          <P>For detailed instructions on submitting comments and additional information on the rulemaking process, see the “III. Public Comment Procedures” in the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>

          <P>In addition to viewing the docket and obtaining copies of documents at<E T="03">www.regulations.gov,</E>you may review copies of the North Dakota program, this amendment, a listing of any public hearings, and all written comments received in response to this document at the addresses listed below during normal business hours, Monday through Friday, excluding holidays. You may also receive one free copy of the amendment by contacting OSM's Casper Field Office.</P>

          <P>Jeffrey Fleischman, Director, Casper Field Office, Office of Surface Mining Reclamation and Enforcement, Dick Cheney Federal Building, PO Box 11018, 150 East B Street, Casper, Wyoming 82601-1018, (307) 261-6555,<E T="03">jfleischman@osmre.gov.</E>
          </P>

          <P>James Deutsch, Director, Reclamation Division, North Dakota Public Service Commission, 600 East Boulevard, Dept. 408, Bismarck, North Dakota 58505-0480, (701) 328-2251,<E T="03">jdeutsch@nd.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Jeffrey Fleischman, Telephone: (307) 261-6555. Internet:<E T="03">jfleischman@osmre.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        
        <EXTRACT>
          <FP SOURCE="FP-2">I. Background on the North Dakota Program</FP>
          <FP SOURCE="FP-2">II. Description of the Proposed Amendment</FP>
          <FP SOURCE="FP-2">III. Public Comment Procedures</FP>
          <FP SOURCE="FP-2">IV. Procedural Determinations</FP>
        </EXTRACT>
        <HD SOURCE="HD1">I. Background on the North Dakota Program</HD>

        <P>Section 503(a) of the Act permits a State to assume primacy for the regulation of surface coal mining and reclamation operations on non-Federal and non-Indian lands within its borders by demonstrating that its State program includes, among other things, “a State law which provides for the regulation of surface coal mining and reclamation operations in accordance with the requirements of this Act * * *; and rules and regulations consistent with regulations issued by the Secretary pursuant to this Act.” See 30 U.S.C. 1253(a)(1) and (7). On the basis of these criteria, the Secretary of the Interior conditionally approved the North Dakota program on December 15, 1980. You can find background information on the North Dakota program, including the Secretary's findings, the disposition of comments, and conditions of approval of the North Dakota program in the December 15, 1980<E T="04">Federal Register</E>(45 FR 82214). You can also find later actions concerning North Dakota's program and program amendments at 30 CFR 934.15 and 934.30.</P>
        <HD SOURCE="HD1">II. Description of the Proposed Amendment</HD>

        <P>By letter dated February 2, 2012, North Dakota sent us a proposed amendment to its program (Administrative Record Document ID No. OSM-2012-0006-0002) under SMCRA (30 U.S.C. 1201<E T="03">et seq.</E>). North Dakota sent the amendment to include changes made at its own initiative to the North Dakota Administrative Code (NDAC). The full text of the program amendment is available for you to read at the locations listed above under<E T="02">ADDRESSES</E>.</P>

        <P>Specifically, North Dakota proposes to change letter of credit provisions in the collateral bond rule under NDAC 69-5.2-12-04. The financial information that banks issuing a letter of credit must provide to the Commission is specifically addressed. An option is being added to let banks provide a certified copy of financial reports that<PRTPAGE P="24662"/>are required by a Federal agency rather than submit a balance sheet that is certified by a certified public accountant (CPA). Additionally, a change that affects the provision requiring banks to give the Commission notice of actions alleging insolvency or bankruptcy is also being proposed. North Dakota is proposing these changes both in order to be compliant with state and Federal banking regulations and to assist banks that could possibly have difficulty submitting CPA certified balance sheets.</P>
        <HD SOURCE="HD1">III. Public Comment Procedures</HD>
        <P>Under the provisions of 30 CFR 732.17(h), we are seeking your comments on whether the amendment satisfies the applicable program approval criteria of 30 CFR 732.15. If we approve the amendment, it will become part of the North Dakota program.</P>
        <HD SOURCE="HD2">Electronic or Written Comments</HD>
        <P>If you submit written comments, they should be specific, confined to issues pertinent to the proposed regulations, and explain the reason for any recommended change(s). We appreciate any and all comments, but those most useful and likely to influence decisions on the final regulations will be those that either involve personal experience or include citations to and analyses of SMCRA, its legislative history, its implementing regulations, case law, other pertinent state or Federal laws or regulations, technical literature, or other relevant publications.</P>

        <P>We cannot ensure that comments received after the close of the comment period (see<E T="02">DATES</E>) or sent to an address other than those listed above (see<E T="02">ADDRESSES</E>) will be included in the docket for this rulemaking and considered.</P>
        <HD SOURCE="HD2">Public Availability of Comments</HD>

        <P>Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment—including your personal identifying information—may be made publicly available in the electronic docket for this rulemaking at<E T="03">www.regulations.gov.</E>While you can ask us in your comment to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so.</P>
        <HD SOURCE="HD2">Public Hearing</HD>

        <P>If you wish to speak at the public hearing, contact the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>by 4 p.m., m.d.t. on May 10, 2012. If you are disabled and need reasonable accommodations to attend a public hearing, contact the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>. We will arrange the location and time of the hearing with those persons requesting the hearing. If no one requests an opportunity to speak, we will not hold the hearing.</P>
        <P>To assist the transcriber and ensure an accurate record, we request, if possible, that each person who speaks at a public hearing provide us with a written copy of his or her comments. The public hearing will continue on the specified date until everyone scheduled to speak has been given an opportunity to be heard. If you are in the audience and have not been scheduled to speak and wish to do so, you will be allowed to speak after those who have been scheduled. We will end the hearing after everyone scheduled to speak and others present in the audience who wish to speak, have been heard.</P>
        <HD SOURCE="HD2">Public Meeting</HD>

        <P>If only one person requests an opportunity to speak, we may hold a public meeting rather than a public hearing. If you wish to meet with us to discuss the amendment, please request a meeting by contacting the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>. All such meetings are open to the public and, if possible, we will post notices of meetings at the locations listed under<E T="02">ADDRESSES</E>. We will make a written summary of each meeting a part of the administrative record.</P>
        <HD SOURCE="HD1">IV. Procedural Determinations</HD>
        <HD SOURCE="HD2">Executive Order 12866—Regulatory Planning and Review</HD>
        <P>This rule is exempted from review by the Office of Management and Budget (OMB) under Executive Order 12866 (Regulatory Planning and Review).</P>
        <HD SOURCE="HD2">Other Laws and Executive Orders Affecting Rulemaking</HD>

        <P>When a State submits a program amendment to OSM for review, our regulations at 30 CFR 732.17(h) require us to publish a notice in the<E T="04">Federal Register</E>indicating receipt of the proposed amendment, its text or a summary of its terms, and an opportunity for public comment. We conclude our review of the proposed amendment after the close of the public comment period and determine whether the amendment should be approved, approved in part, or not approved. At that time, we will also make the determinations and certifications required by the various laws and executive orders governing the rulemaking process and include them in the final rule.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 30 CFR Part 934</HD>
          <P>Intergovernmental relations, Surface mining, Underground mining.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: March 7, 2012.</DATED>
          <NAME>Allen D. Klein,</NAME>
          <TITLE>Director, Western Region.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9869 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4310-05-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">LIBRARY OF CONGRESS</AGENCY>
        <SUBAGY>Copyright Royalty Board</SUBAGY>
        <CFR>37 CFR Part 381</CFR>
        <DEPDOC>[Docket No. 2011-2 CRB NCEB II]</DEPDOC>
        <SUBJECT>Determination of Reasonable Rates and Terms for Noncommercial Broadcasting</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Copyright Royalty Board, Library of Congress.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Copyright Royalty Judges are publishing for comment proposed rates and terms for use of certain works in connection with noncommercial broadcasting for the period commencing January 1, 2013, and ending on December 31, 2017.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments and objections, if any, are due no later than May 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Comments and objections may be sent electronically to<E T="03">crb@loc.gov.</E>In the alternative, send an original, five copies and an electronic copy on a CD either by mail or by hand delivery. Please do not use multiple means of transmission. Comments and objections may not be delivered by an overnight delivery service other than the U.S. Postal Service Express Mail. If by mail (including overnight delivery), comments and objections must be addressed to: Copyright Royalty Board, P.O. Box. 70977, Washington, DC 20024-0977. If hand delivered by a private party, comments and objections must be brought to the Copyright Office, Public Information Office, Library of Congress, James Madison Memorial Building, Room LM-401, 101 Independence Avenue SE., Washington, DC 20559-6000, between 8:30 a.m. and 5 p.m. If delivered by a commercial courier, comments and objections must be delivered between 8:30 a.m. and 4 p.m. to the Congressional Courier Acceptance Site located at 2nd and D Street NE., Washington, DC, and the envelope must be addressed to: Copyright Royalty Board, Library of Congress, James Madison Memorial Building, Room LM-403, 101 Independence Avenue SE., Washington, DC 20559-6000.</P>
        </ADD>
        <FURINF>
          <PRTPAGE P="24663"/>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>LaKeshia Keys, Program Specialist, by telephone: (202) 707-7658 or email at<E T="03">crb@loc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>
        <P>Section 118 of the Copyright Act, title 17 of the United States Code, establishes a statutory license for the use of certain copyrighted works in connection with noncommercial television and radio broadcasting. Chapter 8 of the Copyright Act requires the Copyright Royalty Judges (“Judges”) to conduct proceedings every five years to determine the rates and terms for the section 118 license.<SU>1</SU>
          <FTREF/>17 U.S.C. 801(b)(1), 804(b)(6). In accordance with section 804(b)(6), the Judges commenced the proceeding to set rates and terms for the period 2008-2012 on January 9, 2006, 71 FR 1453, and published final regulations setting those rates and terms on November 30, 2007. 72 FR 67646. Therefore, the next proceeding to determine the rates and terms for the section 118 license was to be commenced in January 2011 for the period 2013-2017. 17 U.S.C. 804(b)(6).</P>
        <FTNT>
          <P>
            <SU>1</SU>Prior to the enactment of the Copyright Royalty and Distribution Reform Act of 2004, which established the Copyright Royalty Judges, rates and terms for the section 118 statutory license were set under the Copyright Arbitration Royalty Panel system, which was administered by the Librarian of Congress.</P>
        </FTNT>
        <P>Accordingly, the Judges published in the<E T="04">Federal Register</E>a notice commencing the proceeding to determine the rates and terms for the 2013-2017 period and requesting interested parties to submit their petitions to participate. 76 FR 591 (January 5, 2011). Petitions to Participate were received from: The American Society of Authors, Composers and Publishers (“ASCAP”); SESAC, Inc.; Broadcast Music, Inc. (“BMI”); Educational Media Foundation (“EMF”); Music Reports, Inc.; National Public Radio, the Public Broadcasting Service, and noncommercial radio and television stations eligible to receive funding from the Corporation for Public Broadcasting jointly (“NPR/PBS/CPB”); National Religious Broadcasters Noncommercial Music License Committee (“NRBNMLC”); the Church Music Publishers' Association; the National Music Publishers' Association, Inc. and the Harry Fox Agency, jointly (“NMPA/HFA”); the Catholic Radio Association (“CRA”); and the American Council on Education (“ACE”). The Judges set the timetable for the three-month negotiation period, see 17 U.S.C. 803(b)(3), and directed the participants to submit their written direct statements no later than October 31, 2011. In response to the October 31 deadline, the Judges received written direct statements from CRA, BMI, ASCAP, and Music Reports, Inc.<SU>2</SU>
          <FTREF/>as well as several notifications of settlement and proposed rates and terms for the Copyright Royalty Judges to adopt.</P>
        <FTNT>
          <P>
            <SU>2</SU>Pursuant to 17 U.S.C. 803(b)(6)(C)(x), the Judges set the 60-day discovery period to run from November 30, 2011, through January 30, 2012. During the discovery period, Music Reports, Inc., and CRA each withdrew from the proceeding on December 13, 2011, and January 27, 2012, respectively. CRA also requested that the Judges vacate their Order dated January 20, 2012, compelling CRA to produce certain discovery; the Judges deny this request as moot, given CRA's withdrawal from the proceeding.</P>
        </FTNT>
        <P>There are two ways that copyright owners and public broadcasting entities<SU>3</SU>
          <FTREF/>may negotiate rates and terms under the section 118 statutory license. First, copyright owners may negotiate rates and terms with specific public broadcasting entities for the use of all of the copyright owners' works covered by the license. Section 118(b)(2) provides that such license agreements “shall be given effect in lieu of any determination by the  * * *  Copyright Royalty Judges,” provided that copies of the agreement are submitted to the Judges “within 30 days of execution.” 17 U.S.C. 118(b)(2). The Judges received several agreements in this category for which no further action is required.</P>
        <FTNT>
          <P>
            <SU>3</SU>A “public broadcasting entity” is defined as a “noncommercial educational broadcast station as defined in section 397 of title 47 and any nonprofit institution or organization engaged in the activities described in paragraph (2) of subsection (c)” of section 118. 17 U.S.C. 118(f).</P>
        </FTNT>
        <P>Second, copyright owners and public broadcasting entities may negotiate rates and terms for categories of copyrighted works and uses that would be binding on all owners and entities and submit them to the Judges for approval. Section 801(b)(7)(A) provides that in such event:</P>
        
        <EXTRACT>
          <P>(i) The Copyright Royalty Judges shall provide those that would be bound by the terms, rates, or other determination set by any agreement in a proceeding to determine royalty rates an opportunity to comment on the agreement and shall provide to participants in the proceeding under section 803(b)(2) that would be bound by the terms, rates, or other determination set by the agreement to comment on the agreement and object to its adoption as a basis for statutory terms and rates; and</P>
          <P>(ii) the Copyright Royalty Judges may decline to adopt the agreement as a basis for statutory terms and rates for participants that are not parties to the agreement, if any participant described in clause (i) objects to the agreement and the Copyright Royalty Judges conclude, based on the record before them if one exists, that the agreement does not provide a reasonable basis for setting statutory terms and rates.</P>
        </EXTRACT>
        
        <FP>17 U.S.C. 801(b)(7)(A). The Judges received seven proposals within this category from the following participants: (1) SESAC and ACE; (2) BMI and ACE; (3) ASCAP and ACE; (4) NMPA/HFA and NRBNMLC; (5) SESAC and NRBNMLC, (6) ASCAP and NRBNMLC; and (7) BMI and NRBNMLC.<SU>4</SU>
          <FTREF/>
        </FP>
        <FTNT>
          <P>
            <SU>4</SU>On October 31, 2011, EMF notified the Judges that as a member of NRBNMLC it was a party to each of the joint proposals involving NRBNMLC.</P>
        </FTNT>
        <HD SOURCE="HD1">ACE Joint Proposals</HD>

        <P>The joint proposals entered into by ACE and each of SESAC, BMI, and ASCAP propose to modify the royalty rates set forth in § 381.5. The rates proposed in the ASCAP/ACE and BMI/ACE submissions reflect a change in both the fees and the fee structure, going from a flat rate to tiered rates primarily based on the number of full-time students enrolled in the educational entity operating the station, with an exception that looks to the college radio station's authorized effective radiation power (“ERP”) as set forth in its current FCC license. ASCAP/ACE Joint Proposal at 4; BMI/ACE Joint Proposal at 4. Moreover, the proposed rates for ASCAP and BMI eliminate the need for the historic annual Consumer Price Index adjustments, as the proposed rates increase at the rate of two percent per year.<E T="03">Id.</E>at 5.</P>
        <P>The SESAC/ACE submission retains a flat rate which is then adjusted, starting in 2014, by the change in the Consumer Price Index or two percent, whichever is greater. SESAC/ACE Joint Proposal at 2.<SU>5</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>5</SU>The proposed elimination of the CPI adjustments for ASCAP and BMI necessitated a change to § 381.10. However, no proposed language was provided with the initial proposals. Consequently, the Judges issued an order requesting proposed language to § 381.10, and the parties provided the same.<E T="03">See Order</E>
            <E T="03">Regarding Submission of Settlement Proposals,</E>Docket No. 2011-3 CRB NCEB II (February 2, 2012).<E T="03">See also</E>Joint Submission of American Council on Education, the American Society of Composers, Authors and Publishers, Broadcast Music, Inc., and SESAC, Inc. (filed March 16, 2012).</P>
        </FTNT>

        <P>Each joint proposal proposes to require that each annual payment of the royalty rate be accompanied by a declaration stating the number of full-time students enrolled in the educational entity operating the station and/or the ERP as specified in the entity's current FCC license.<E T="03">See</E>proposed § 381.5(d).</P>
        <HD SOURCE="HD1">NRBNMLC Joint Proposals</HD>

        <P>The joint proposals entered into by NRBNMLC and each of NMPA/HFA, ASCAP, BMI, and SESAC propose carrying forward unchanged the current provisions set forth in §§ 381.1 (except<PRTPAGE P="24664"/>to replace “2008” with “2013” and “2012” with “2017”), 381.2, 381.9, and 381.11.</P>

        <P>The joint proposal between NMPA/HFA and NRBNMLC stated that the rates in § 381.7(b)(4) should remain the same as those currently set for 2008-2012, “subject to the additional provisions” of §§ 381.7(b)(3) and (5), since they “are reasonable” and “no circumstances exist that would warrant modification of these fees.” NMPA/HFA and NRBNMLC Joint Proposal at 2. The proposal also stated that separate negotiations were ongoing between HFA and NMPA and NPR and PBS with respect to provisions in § 381.7 other than § 381.7(b)(4).<E T="03">Id.</E>at 2-3. When such proposal did not appear to be forthcoming, the Judges issued an order requesting in part that such proposal, if finalized, be submitted by March 16, 2012, in order to allow for publication of all proposed rates and terms in a single document.<E T="03">See Order Regarding Submission of Settlement Proposals,</E>Docket No. 2011-2 CRB NCEB II (February 2, 2012);<E T="03">see also</E>n.5. However, after receiving no responsive filings, the Judges issued a subsequent order requiring HFA, NMPA, NPR, and PBS to show cause why the provisions to be covered by their separate proposal (§§ 381.7(b)(1)(i)-(iii), 381.7(b)(2)(i)-(iv), 381.7(c), 381.7(d), and 381.7(e)) should not be removed from Part 381. See Order to Show Cause, Docket No. 2011-2 CRB NCEB II (March 28, 2012). In response, HFA, NMPA, NPR and PBS submitted their joint proposal covering the provisions specified in the March 28 order. Specifically, they proposed that the rates set forth in §§ 381.7(b)(1) and (2) “be changed to reflect a rate increase consistent with the prior percentage increase from the 2003-2007 license period to the 2008-2012 license period” as such increase “is fair and reasonable.” Response to Order to Show Cause, and Joint Proposal of the Harry Fox Agency, Inc., National Music Publishers' Association, Inc., National Public Radio, Inc. and Public Broadcasting Service, at 3 (April 4, 2012). These parties proposed no changes to §§ 381.7(c)-(e) and requested that these provisions be carried forward as is because they “are fair and reasonable in that they facilitate efficient, consistent and accurate payments of royalties for uses governed by [§ ] 381.7.”<E T="03">Id.</E>at 4.</P>
        <P>Each of the joint proposals between NRBNMLC and ASCAP, BMI, and SESAC propose modifications to § 381.6. Under the proposals, alternatives have been provided to a Religious/Community Noncommercial Radio Station in determining its Population Count which is the basis of the rates paid. In addition, the proposals include a new reduced rate for a Religious/Community Noncommercial Radio Station using a talk format necessitating a number of newly defined terms. Finally, the proposals address a Religious/Community Noncommercial Radio Station's broadcast of in-band, on-channel, digital radio (“HD Radio”) signals.</P>
        <HD SOURCE="HD1">Other Provisions</HD>
        <P>Finally, the Judges have removed and reserved two sections for which no proposals were submitted. Specifically, § 381.4, which governed performance of musical compositions by PBS, NPR and other public broadcasting entities engaged in the activities of 17 U.S.C. 118(c), and § 381.8, which governed the terms and rates of royalty payments for the use of published pictorial, graphic, and sculptural works in PBS-distributed programs as well as in other than PBS-distributed programs, have been removed and their section numbers reserved.</P>
        <P>As noted above, the public may comment and object to any or all of the proposed regulations contained in this notice. Such comments and objections must be submitted no later than May 25, 2012.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 37 CFR Part 381</HD>
          <P>Copyright, Music, Radio, Television, Rates.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Proposed Regulations</HD>
        <P>For the reasons set forth in the preamble, the Copyright Royalty Judges propose to amend Part 381 to Chapter III of title 37 of the Code of Federal Regulations to read as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 381—USE OF CERTAIN COPYRIGHTED WORKS IN CONNECTION WITH NONCOMMERCIAL EDUCATIONAL BROADCASTING</HD>
          <P>1. The authority citation for part 381 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>17 U.S.C. 118, 801(b)(1) and 803.</P>
          </AUTH>
          <SECTION>
            <SECTNO>§ 381.1</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
            <P>2. Section 381.1 is amended by removing “2008” and adding “2013” in its place and by removing “2012” and adding “2017” in its place.</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 381.4</SECTNO>
            <SUBJECT>[Removed and Reserved]</SUBJECT>
            <P>3. Remove and reserve § 381.4.</P>
            <P>4. Section 381.5 is amended by revising paragraphs (c) and (d) to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 381.5</SECTNO>
            <SUBJECT>Performance of musical compositions by public broadcasting entities licensed to colleges and universities.</SUBJECT>
            <STARS/>
            <P>(c)<E T="03">Royalty rate.</E>A public broadcasting entity within the scope of this section may perform published nondramatic musical compositions subject to the following schedule of royalty rates:</P>
            <P>(1) For all such compositions in the repertory of ASCAP, the royalty rates shall be as follows:</P>
            <P>(i)</P>
            <GPOTABLE CDEF="s40,r100,7,7,7,7,7" COLS="7" OPTS="L2,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">Number of full-time students</CHED>
                <CHED H="1">2013</CHED>
                <CHED H="1">2014</CHED>
                <CHED H="1">2015</CHED>
                <CHED H="1">2016</CHED>
                <CHED H="1">2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Level 1</ENT>
                <ENT>&lt;1,000</ENT>
                <ENT>$319</ENT>
                <ENT>$325</ENT>
                <ENT>$332</ENT>
                <ENT>$339</ENT>
                <ENT>$345</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 2</ENT>
                <ENT>1,000-4,999</ENT>
                <ENT>369</ENT>
                <ENT>376</ENT>
                <ENT>384</ENT>
                <ENT>392</ENT>
                <ENT>399</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 3</ENT>
                <ENT>5,000-9,999</ENT>
                <ENT>505</ENT>
                <ENT>515</ENT>
                <ENT>525</ENT>
                <ENT>535</ENT>
                <ENT>546</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 4</ENT>
                <ENT>10,000-19,999</ENT>
                <ENT>655</ENT>
                <ENT>668</ENT>
                <ENT>681</ENT>
                <ENT>695</ENT>
                <ENT>708</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 5</ENT>
                <ENT>20,000 +</ENT>
                <ENT>822</ENT>
                <ENT>838</ENT>
                <ENT>855</ENT>
                <ENT>872</ENT>
                <ENT>890</ENT>
              </ROW>
            </GPOTABLE>
            <P>(ii) Level 1 rates as set forth in paragraph (c)(1)(i) of this section, shall also apply to College Radio Stations with an authorized effective radiated power (ERP), as that term is defined in 47 CFR 73.310(a), of 100 Watts or less, as specified on its current FCC license, regardless of the size of the student population.</P>
            <P>(2) For all such compositions in the repertory of BMI, the royalty rates shall be as follows:</P>
            <P>(i)<PRTPAGE P="24665"/>
            </P>
            <GPOTABLE CDEF="s40,r100,7,7,7,7,7" COLS="7" OPTS="L2,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">Number of full-time students</CHED>
                <CHED H="1">2013</CHED>
                <CHED H="1">2014</CHED>
                <CHED H="1">2015</CHED>
                <CHED H="1">2016</CHED>
                <CHED H="1">2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Level 1</ENT>
                <ENT>&lt;1,000</ENT>
                <ENT>$319</ENT>
                <ENT>$325</ENT>
                <ENT>$332</ENT>
                <ENT>$339</ENT>
                <ENT>$345</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 2</ENT>
                <ENT>1,000-4,999</ENT>
                <ENT>369</ENT>
                <ENT>376</ENT>
                <ENT>384</ENT>
                <ENT>392</ENT>
                <ENT>399</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 3</ENT>
                <ENT>5,000-9,999</ENT>
                <ENT>505</ENT>
                <ENT>515</ENT>
                <ENT>525</ENT>
                <ENT>535</ENT>
                <ENT>546</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 4</ENT>
                <ENT>10,000-19,999</ENT>
                <ENT>655</ENT>
                <ENT>668</ENT>
                <ENT>681</ENT>
                <ENT>695</ENT>
                <ENT>708</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 5</ENT>
                <ENT>20,000 +</ENT>
                <ENT>822</ENT>
                <ENT>838</ENT>
                <ENT>855</ENT>
                <ENT>872</ENT>
                <ENT>890</ENT>
              </ROW>
            </GPOTABLE>
            <P>(ii) Level 1 rates, as set forth in paragraph (c)(2)(i) of this section, shall also apply to College Radio Stations with an authorized effective radiated power (ERP), as that term is defined in 47 CFR 73.310(a), of 100 Watts or less, as specified on its current FCC license, regardless of the size of the student population.</P>
            <P>(3) For all such compositions in the repertory of SESAC, the royalty rates shall be as follows:</P>
            <P>(i) 2013: $140.00 per station;</P>
            <P>(ii) 2014: $140 per station, subject to an annual cost of living adjustment in accordance with paragraph (c)(3)(vi) of this section;</P>
            <P>(iii) 2015: The 2014 rate, subject to an annual cost of living adjustment in accordance with paragraph (c)(3)(vi) of this section;</P>
            <P>(iv) 2016: The 2015 rate, subject to an annual cost of living adjustment in accordance with paragraph (c)(3)(vi) of this section;</P>
            <P>(v) 2017: The 2016 rate, subject to an annual cost of living adjustment in accordance with paragraph (c)(3)(vi) of this section.</P>
            <P>(vi) Such cost of living adjustment to be made in accordance with the greater of</P>
            <P>(A) The change, if any, in the Consumer Price Index (all consumers, all items) published by the U.S. Department of Labor, Bureau of Labor Statistics during the twelve (12) month period from the most recent Index, published before December 1 of the year immediately prior to the applicable year, or</P>
            <P>(B) Two percent (2%).</P>
            <P>(4) For the performance of any other such compositions: $1.</P>
            <P>(d)<E T="03">Payment of royalty rate.</E>The public broadcasting entity shall pay the required royalty rate to ASCAP, BMI and SESAC not later than January 31 of each year. Each annual payment to ASCAP, BMI and SESAC shall be accompanied by a signed declaration stating the number of full-time students enrolled in the educational entity operating the station and/or the effective radiated power (ERP) as specified in its current FCC license. An exact copy of such declaration shall be furnished to each of ASCAP, BMI and SESAC.</P>
            <STARS/>
            <P>5. Section 381.6 is amended as follows:</P>
            <P>a. By redesignating paragraphs (b) through (e) as paragraphs (c) through (f), respectively;</P>
            <P>b. By adding a new paragraph (b);</P>
            <P>c. By revising newly redesignated paragraph (d);</P>
            <P>d. By revising newly redesignated paragraph (e); and</P>
            <P>e. By removing current paragraph (f).</P>
            
            <P>The additions and revisions to § 381.6 read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 381.6</SECTNO>
            <SUBJECT>Performance of musical compositions by other public broadcasting entities.</SUBJECT>
            <STARS/>
            <P>(b) Definitions. As used in paragraphs (d) and (e) of this section, the following terms and their variant forms mean the following:</P>
            <P>(1)<E T="03">Feature Music</E>shall mean any performance of a musical work, whether live or recorded, that is the principal focus of audience attention. Feature Music does not include bridge, background, or underscore music, themes or signatures, interstitial music between programs such as in public service announcements or program sponsorship identifications, brief musical transitions in and out of program segments (not to exceed 60 seconds in duration), incidental performances of music during broadcasts of public, religious, or sports events, or brief performances during news, talk, religious, and sports programming of no more than 30 seconds in duration.</P>
            <P>(2)<E T="03">Population Count.</E>The combination of:</P>
            <P>(i) The number of persons estimated to reside within a station's Predicted 60 dBu Contour, based on the most recent available census data; and</P>
            <P>(ii) The nonduplicative number of persons estimated to reside in the Predicted 60 dBu Contour of any Translator or Booster Station that extends a public broadcasting entity's signal beyond the contours of a station's Predicted 60 dBu Contour.</P>
            <P>(iii) In determining Population Count, a station or a Translator or Booster Station may use and report the total population data, from a research company generally recognized in the broadcasting industry, for the radio market within which the station's community license is located.</P>
            <P>(3)<E T="03">Predicted 60 dBu Contour</E>shall be calculated as set forth in 47 CFR 73.313.</P>
            <P>(4)<E T="03">Talk Format Station</E>shall mean a noncommercial radio station:</P>
            <P>(i) Whose program content primarily consists of talk shows, news programs, sports, community affairs or religious sermons (or other non-music-oriented programming);</P>
            <P>(ii) That performs Feature Music in less than 20% of its programming annually; and</P>
            <P>(iii) That performs music-oriented programming for no more than four (4) programming hours during the hours from 6 a.m. to 10 p.m. each weekday, with no two (2) hours of such programming occurring consecutively, with the exception of up to five (5) weekdays during the year.</P>
            <P>(5)<E T="03">Weekday</E>shall mean the 24-hour period starting at 12 a.m. through 11:59 p.m. on Mondays, Tuesdays, Wednesdays, Thursdays and Fridays occurring between January 1 of a given year up to and including Thanksgiving day of that year.</P>
            <P>(6)<E T="03">Translator Station</E>and<E T="03">Booster Station</E>shall have the same meanings as set forth in 47 CFR 74.1201.</P>
            <STARS/>
            <P>(d)<E T="03">Royalty rate.</E>A public broadcasting entity within the scope of this section may perform published nondramatic musical compositions subject to the following schedule of royalty rates:</P>
            <P>(1) For all such compositions in the repertory of ASCAP, the royalty rates shall be as follows:</P>
            <P>(i) Music Fees (Stations with 20% or more programming containing Feature Music):</P>
            <GPOTABLE CDEF="s40,r100,7,7,7,7,7" COLS="7" OPTS="L2,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">Population count</CHED>
                <CHED H="1">2013</CHED>
                <CHED H="1">2014</CHED>
                <CHED H="1">2015</CHED>
                <CHED H="1">2016</CHED>
                <CHED H="1">2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Level 1</ENT>
                <ENT>0-249,999</ENT>
                <ENT>$631</ENT>
                <ENT>$644</ENT>
                <ENT>$657</ENT>
                <ENT>$670</ENT>
                <ENT>$683</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 2</ENT>
                <ENT>250,000-499,999</ENT>
                <ENT>1,126</ENT>
                <ENT>1,149</ENT>
                <ENT>1,171</ENT>
                <ENT>1,195</ENT>
                <ENT>1,219</ENT>
              </ROW>
              <ROW>
                <PRTPAGE P="24666"/>
                <ENT I="01">Level 3</ENT>
                <ENT>500,000-999,999</ENT>
                <ENT>1,688</ENT>
                <ENT>1,722</ENT>
                <ENT>1,756</ENT>
                <ENT>1,791</ENT>
                <ENT>1,827</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 4</ENT>
                <ENT>1,000,000-1,499,999</ENT>
                <ENT>2,251</ENT>
                <ENT>2,296</ENT>
                <ENT>2,342</ENT>
                <ENT>2,389</ENT>
                <ENT>2,437</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 5</ENT>
                <ENT>1,500,000-1,999,999</ENT>
                <ENT>2,814</ENT>
                <ENT>2,870</ENT>
                <ENT>2,928</ENT>
                <ENT>2,986</ENT>
                <ENT>3,046</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 6</ENT>
                <ENT>2,000,000-2,499,999</ENT>
                <ENT>3,377</ENT>
                <ENT>3,445</ENT>
                <ENT>3,513</ENT>
                <ENT>3,584</ENT>
                <ENT>3,655</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 7</ENT>
                <ENT>2,500,000-2,999,999</ENT>
                <ENT>3,939</ENT>
                <ENT>4,018</ENT>
                <ENT>4,098</ENT>
                <ENT>4,180</ENT>
                <ENT>4,264</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 8</ENT>
                <ENT>3,000,000 and above</ENT>
                <ENT>5,628</ENT>
                <ENT>5,741</ENT>
                <ENT>5,855</ENT>
                <ENT>5,972</ENT>
                <ENT>6,092</ENT>
              </ROW>
            </GPOTABLE>
            <P>(ii) Talk Format Station Fees (Stations with &lt;20% Feature Music programming):</P>
            <GPOTABLE CDEF="s40,r100,7,7,7,7,7" COLS="7" OPTS="L2,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">Population count</CHED>
                <CHED H="1">2013</CHED>
                <CHED H="1">2014</CHED>
                <CHED H="1">2015</CHED>
                <CHED H="1">2016</CHED>
                <CHED H="1">2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Level 1</ENT>
                <ENT>0-249,999</ENT>
                <ENT>$631</ENT>
                <ENT>$644</ENT>
                <ENT>$657</ENT>
                <ENT>$670</ENT>
                <ENT>$683</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 2</ENT>
                <ENT>250,000-499,999</ENT>
                <ENT>631</ENT>
                <ENT>644</ENT>
                <ENT>657</ENT>
                <ENT>670</ENT>
                <ENT>683</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 3</ENT>
                <ENT>500,000-999,999</ENT>
                <ENT>631</ENT>
                <ENT>644</ENT>
                <ENT>657</ENT>
                <ENT>670</ENT>
                <ENT>683</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 4</ENT>
                <ENT>1,000,000-1,499,999</ENT>
                <ENT>788</ENT>
                <ENT>804</ENT>
                <ENT>820</ENT>
                <ENT>836</ENT>
                <ENT>853</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 5</ENT>
                <ENT>1,500,000-1,999,999</ENT>
                <ENT>985</ENT>
                <ENT>1,005</ENT>
                <ENT>1,025</ENT>
                <ENT>1,045</ENT>
                <ENT>1,066</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 6</ENT>
                <ENT>2,000,000-2,499,999</ENT>
                <ENT>1,182</ENT>
                <ENT>1,206</ENT>
                <ENT>1,230</ENT>
                <ENT>1,254</ENT>
                <ENT>1,279</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 7</ENT>
                <ENT>2,500,000-2,999,999</ENT>
                <ENT>1,379</ENT>
                <ENT>1,406</ENT>
                <ENT>1,434</ENT>
                <ENT>1,463</ENT>
                <ENT>1,492</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 8</ENT>
                <ENT>3,000,000 and above</ENT>
                <ENT>1,970</ENT>
                <ENT>2,009</ENT>
                <ENT>2,049</ENT>
                <ENT>2,090</ENT>
                <ENT>2,132</ENT>
              </ROW>
            </GPOTABLE>
            <P>(2) For all such compositions in the repertory of BMI, the royalty rates shall be as follows:</P>
            <P>(i) Music Fees (Stations with 20% or more programming containing Feature Music):</P>
            <GPOTABLE CDEF="s40,r100,7,7,7,7,7" COLS="7" OPTS="L2,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">Population count</CHED>
                <CHED H="1">2013</CHED>
                <CHED H="1">2014</CHED>
                <CHED H="1">2015</CHED>
                <CHED H="1">2016</CHED>
                <CHED H="1">2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Level 1</ENT>
                <ENT>0-249,999</ENT>
                <ENT>$631</ENT>
                <ENT>$644</ENT>
                <ENT>$657</ENT>
                <ENT>$670</ENT>
                <ENT>$683</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 2</ENT>
                <ENT>250,000-499,999</ENT>
                <ENT>1,126</ENT>
                <ENT>1,149</ENT>
                <ENT>1,171</ENT>
                <ENT>1,195</ENT>
                <ENT>1,219</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 3</ENT>
                <ENT>500,000-999,999</ENT>
                <ENT>1,688</ENT>
                <ENT>1,722</ENT>
                <ENT>1,756</ENT>
                <ENT>1,791</ENT>
                <ENT>1,827</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 4</ENT>
                <ENT>1,000,000-1,499,999</ENT>
                <ENT>2,251</ENT>
                <ENT>2,296</ENT>
                <ENT>2,342</ENT>
                <ENT>2,389</ENT>
                <ENT>2,437</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 5</ENT>
                <ENT>1,500,000-1,999,999</ENT>
                <ENT>2,814</ENT>
                <ENT>2,870</ENT>
                <ENT>2,928</ENT>
                <ENT>2,986</ENT>
                <ENT>3,046</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 6</ENT>
                <ENT>2,000,000-2,499,999</ENT>
                <ENT>3,377</ENT>
                <ENT>3,445</ENT>
                <ENT>3,513</ENT>
                <ENT>3,584</ENT>
                <ENT>3,655</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 7</ENT>
                <ENT>2,500,000-2,999,999</ENT>
                <ENT>3,939</ENT>
                <ENT>4,018</ENT>
                <ENT>4,098</ENT>
                <ENT>4,180</ENT>
                <ENT>4,264</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 8</ENT>
                <ENT>3,000,000 and above</ENT>
                <ENT>5,628</ENT>
                <ENT>5,741</ENT>
                <ENT>5,855</ENT>
                <ENT>5,972</ENT>
                <ENT>6,092</ENT>
              </ROW>
            </GPOTABLE>
            <P>(ii) Talk Format Station Fees (Stations with &lt;20% Feature Music programming):</P>
            <GPOTABLE CDEF="s40,r100,7,7,7,7,7" COLS="7" OPTS="L2,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">Population count</CHED>
                <CHED H="1">2013</CHED>
                <CHED H="1">2014</CHED>
                <CHED H="1">2015</CHED>
                <CHED H="1">2016</CHED>
                <CHED H="1">2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Level 1</ENT>
                <ENT>0-249,999</ENT>
                <ENT>$631</ENT>
                <ENT>$644</ENT>
                <ENT>$657</ENT>
                <ENT>$670</ENT>
                <ENT>$683</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 2</ENT>
                <ENT>250,000-499,999</ENT>
                <ENT>631</ENT>
                <ENT>644</ENT>
                <ENT>657</ENT>
                <ENT>670</ENT>
                <ENT>683</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 3</ENT>
                <ENT>500,000-999,999</ENT>
                <ENT>631</ENT>
                <ENT>644</ENT>
                <ENT>657</ENT>
                <ENT>670</ENT>
                <ENT>683</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 4</ENT>
                <ENT>1,000,000-1,499,999</ENT>
                <ENT>788</ENT>
                <ENT>804</ENT>
                <ENT>820</ENT>
                <ENT>836</ENT>
                <ENT>853</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 5</ENT>
                <ENT>1,500,000-1,999,999</ENT>
                <ENT>985</ENT>
                <ENT>1,005</ENT>
                <ENT>1,025</ENT>
                <ENT>1,045</ENT>
                <ENT>1,066</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 6</ENT>
                <ENT>2,000,000-2,499,999</ENT>
                <ENT>1,182</ENT>
                <ENT>1,206</ENT>
                <ENT>1,230</ENT>
                <ENT>1,254</ENT>
                <ENT>1,279</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 7</ENT>
                <ENT>2,500,000-2,999,999</ENT>
                <ENT>1,379</ENT>
                <ENT>1,406</ENT>
                <ENT>1,434</ENT>
                <ENT>1,463</ENT>
                <ENT>1,492</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 8</ENT>
                <ENT>3,000,000 and above</ENT>
                <ENT>1,970</ENT>
                <ENT>2,009</ENT>
                <ENT>2,049</ENT>
                <ENT>2,090</ENT>
                <ENT>2,132</ENT>
              </ROW>
            </GPOTABLE>
            <P>(3) For all such compositions in the repertory of SESAC, the royalty rates shall be as follows:</P>
            <P>(i) Music fees for stations with &gt;=20% Feature Music programming:</P>
            <GPOTABLE CDEF="s40,r100,7,7,7,7,7" COLS="7" OPTS="L2,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">Population count</CHED>
                <CHED H="1">2013</CHED>
                <CHED H="1">2014</CHED>
                <CHED H="1">2015</CHED>
                <CHED H="1">2016</CHED>
                <CHED H="1">2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Level 1</ENT>
                <ENT>0-249,999</ENT>
                <ENT>$138</ENT>
                <ENT>$140</ENT>
                <ENT>$143</ENT>
                <ENT>$146</ENT>
                <ENT>$149</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 2</ENT>
                <ENT>250,000-499,999</ENT>
                <ENT>230</ENT>
                <ENT>234</ENT>
                <ENT>239</ENT>
                <ENT>244</ENT>
                <ENT>248</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 3</ENT>
                <ENT>500,000-999,999</ENT>
                <ENT>345</ENT>
                <ENT>352</ENT>
                <ENT>359</ENT>
                <ENT>366</ENT>
                <ENT>373</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 4</ENT>
                <ENT>1,000,000-1,499,999</ENT>
                <ENT>459</ENT>
                <ENT>468</ENT>
                <ENT>478</ENT>
                <ENT>487</ENT>
                <ENT>497</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 5</ENT>
                <ENT>1,500,000-1,999,999</ENT>
                <ENT>574</ENT>
                <ENT>586</ENT>
                <ENT>597</ENT>
                <ENT>609</ENT>
                <ENT>622</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 6</ENT>
                <ENT>2,000,000-2,499,999</ENT>
                <ENT>689</ENT>
                <ENT>702</ENT>
                <ENT>716</ENT>
                <ENT>731</ENT>
                <ENT>745</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 7</ENT>
                <ENT>2,500,000-2,999,999</ENT>
                <ENT>804</ENT>
                <ENT>820</ENT>
                <ENT>836</ENT>
                <ENT>853</ENT>
                <ENT>870</ENT>
              </ROW>
              <ROW>
                <PRTPAGE P="24667"/>
                <ENT I="01">Level 8</ENT>
                <ENT>3,000,000 and above</ENT>
                <ENT>1,149</ENT>
                <ENT>1,171</ENT>
                <ENT>1,195</ENT>
                <ENT>1,219</ENT>
                <ENT>1,243</ENT>
              </ROW>
            </GPOTABLE>
            <P>(ii) Talk fees for stations with &lt;20% Feature Music programming:</P>
            <GPOTABLE CDEF="s40,r100,7,7,7,7,7" COLS="7" OPTS="L2,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">Population count</CHED>
                <CHED H="1">2013</CHED>
                <CHED H="1">2014</CHED>
                <CHED H="1">2015</CHED>
                <CHED H="1">2016</CHED>
                <CHED H="1">2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Level 1</ENT>
                <ENT>0-249,999</ENT>
                <ENT>$138</ENT>
                <ENT>$140</ENT>
                <ENT>$143</ENT>
                <ENT>$146</ENT>
                <ENT>$149</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 2</ENT>
                <ENT>250,000-499,999</ENT>
                <ENT>138</ENT>
                <ENT>140</ENT>
                <ENT>143</ENT>
                <ENT>146</ENT>
                <ENT>149</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 3</ENT>
                <ENT>500,000-999,999</ENT>
                <ENT>138</ENT>
                <ENT>140</ENT>
                <ENT>143</ENT>
                <ENT>146</ENT>
                <ENT>149</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 4</ENT>
                <ENT>1,000,000-1,499,999</ENT>
                <ENT>161</ENT>
                <ENT>164</ENT>
                <ENT>167</ENT>
                <ENT>170</ENT>
                <ENT>174</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 5</ENT>
                <ENT>1,500,000-1,999,999</ENT>
                <ENT>201</ENT>
                <ENT>205</ENT>
                <ENT>209</ENT>
                <ENT>213</ENT>
                <ENT>218</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 6</ENT>
                <ENT>2,000,000-2,499,999</ENT>
                <ENT>241</ENT>
                <ENT>246</ENT>
                <ENT>251</ENT>
                <ENT>256</ENT>
                <ENT>261</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 7</ENT>
                <ENT>2,500,000-2,999,999</ENT>
                <ENT>281</ENT>
                <ENT>287</ENT>
                <ENT>293</ENT>
                <ENT>299</ENT>
                <ENT>305</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Level 8</ENT>
                <ENT>3,000,000 and above</ENT>
                <ENT>402</ENT>
                <ENT>410</ENT>
                <ENT>418</ENT>
                <ENT>427</ENT>
                <ENT>435</ENT>
              </ROW>
            </GPOTABLE>
            <P>(4) For the performance of any other such compositions, in 2013 through 2017, $1.</P>
            <P>(e)<E T="03">Payment of royalty rate.</E>The public broadcasting entity shall pay the required royalty rate to ASCAP, BMI and SESAC not later than January 31 of each year. Each annual payment shall be accompanied by a signed declaration stating the Population Count of the public broadcasting entity and the source for such Population Count. An exact copy of such declaration shall be furnished to each of ASCAP, BMI and SESAC. Upon prior written notice thereof from ASCAP, BMI and SESAC, a public broadcasting entity shall make its books and records relating to its Population Count available for inspection. In the event that a public broadcasting entity wishes to be deemed a Talk Format Station, then such entity shall provide a signed declaration stating that Feature Music is performed in less than 20% of its annual programming and that it complies with the caps set forth in paragraph (b)(4) of this section. An exact copy of such declaration shall be furnished to each of ASCAP, BMI and SESAC. Upon prior written notice thereof from ASCAP, BMI or SESAC, a public broadcasting entity shall make its program schedule or other documentation supporting its eligibility as a Talk Format Station available for inspection.</P>
            <STARS/>
            <P>6. Section 381.7 is amended as follows:</P>
            <P>a. By revising paragraphs (b)(1)(i)(A)-(D) and (b)(1)(ii)(A)-(D);</P>
            <P>b. By revising paragraphs (b)(2)(i)-(iv);</P>
            <P>c. In paragraph (b)(4), by removing “2008-2012” and adding “2013-2017” in its place; and</P>
            <P>d. In paragraph (b)(5), by removing “2012” and adding “2017” in its place.</P>
            <P>The revisions to § 381.7 read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 381.7</SECTNO>
            <SUBJECT>Recording rights, rates and terms.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>
            <P>(1)(i) * * *</P>
            <GPOTABLE CDEF="s100,10" COLS="2" OPTS="L0,tp0,p7,7/8,g1,t1,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">2013-2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">(A) Feature</ENT>
                <ENT>$116.37</ENT>
              </ROW>
              <ROW>
                <ENT I="01">(B) Concert feature (per minute)</ENT>
                <ENT>$34.95</ENT>
              </ROW>
              <ROW>
                <ENT I="01">(C) Background</ENT>
                <ENT>$58.81</ENT>
              </ROW>
              <ROW>
                <ENT I="22">(D) Theme:</ENT>
              </ROW>
              <ROW>
                <ENT I="02">(<E T="03">1</E>) Single program or first series program</ENT>
                <ENT>$58.81</ENT>
              </ROW>
              <ROW>
                <ENT I="02">(<E T="03">2</E>) Other series program</ENT>
                <ENT>$23.88</ENT>
              </ROW>
            </GPOTABLE>
            <P>(ii) * * *</P>
            <GPOTABLE CDEF="s100,10" COLS="2" OPTS="L0,tp0,p7,7/8,g1,t1,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">2013-2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">(A) Feature</ENT>
                <ENT>$9.62</ENT>
              </ROW>
              <ROW>
                <ENT I="01">(B) Concert feature (per minute)</ENT>
                <ENT>$2.53</ENT>
              </ROW>
              <ROW>
                <ENT I="01">(C) Background</ENT>
                <ENT>$4.18</ENT>
              </ROW>
              <ROW>
                <ENT I="22">(D) Theme:</ENT>
              </ROW>
              <ROW>
                <ENT I="02">(<E T="03">1</E>) Single program or first series program</ENT>
                <ENT>$4.18</ENT>
              </ROW>
              <ROW>
                <ENT I="02">(<E T="03">2</E>) Other series program</ENT>
                <ENT>$1.66</ENT>
              </ROW>
            </GPOTABLE>
            <STARS/>
            <P>(2) * * *</P>
            <GPOTABLE CDEF="s100,10" COLS="2" OPTS="L0,tp0,p7,7/8,g1,t1,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1"/>
                <CHED H="1">2013-2017</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">(i) Feature</ENT>
                <ENT>$12.60</ENT>
              </ROW>
              <ROW>
                <ENT I="01">(ii) Concert feature (per minute)</ENT>
                <ENT>$18.49</ENT>
              </ROW>
              <ROW>
                <ENT I="01">(iii) Background</ENT>
                <ENT>$6.31</ENT>
              </ROW>
              <ROW>
                <ENT I="22">(iv) Theme:</ENT>
              </ROW>
              <ROW>
                <ENT I="02">(A) Single program or first series program</ENT>
                <ENT>$6.31</ENT>
              </ROW>
              <ROW>
                <ENT I="02">(B) Other series program</ENT>
                <ENT>$2.52</ENT>
              </ROW>
            </GPOTABLE>
            <STARS/>
          </SECTION>
          <SECTION>
            <SECTNO>§ 381.8</SECTNO>
            <SUBJECT>[Removed and Reserved]</SUBJECT>
            <P>7. Remove and reserve § 381.8.</P>
            <P>8. Section 381.10 is amended as follows:</P>
            <P>a. In paragraph (a), by removing “2007” and adding “2013” in its place in each place it appears and by removing “2006” and adding “2012” in its place, and by removing “On each December 1” and adding “On or before each December 1” in its place;</P>
            <P>b. By revising paragraph (b);</P>
            <P>c. In paragraph (c), by adding “the” before “rates”, by removing “381.5” and adding “381.5(c)(3)” in its place, and by adding “(30)” after “thirty”.</P>
            <P>The revisions to § 381.10 read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 381.10</SECTNO>
            <SUBJECT>Cost of living adjustment.</SUBJECT>
            <STARS/>

            <P>(b) On the same date of the notices published pursuant to paragraph (a) of this section, the Copyright Royalty Judges shall publish in the<E T="04">Federal Register</E>a revised schedule of the rates for § 381.5(c)(3), the rate to be charged for compositions in the repertory of SESAC, which shall adjust the royalty amounts established in a dollar amount according to the greater of</P>
            <P>(1) The change in the cost of living determined as provided in paragraph (a) of this section, or</P>
            <P>(2) Two percent (2%).</P>
            <P>(3) Such royalty rates shall be fixed at the nearest dollar.</P>
            <STARS/>
          </SECTION>
          <SIG>
            <DATED>Dated: April 20, 2012.</DATED>
            <NAME>Stanley C. Wisniewski,</NAME>
            <TITLE>U.S. Copyright Royalty Judge.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9927 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 1410-72-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Administration for Children and Families</SUBAGY>
        <CFR>45 CFR Parts 262 and 265</CFR>
        <SUBJECT>TANF Assistance and Electronic Benefit Transfer Transactions; Request for Public Comment</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of Health and Human Services (HHS), Administration for Children and Families, Office of Family Assistance (OFA).</P>
        </AGY>
        <ACT>
          <PRTPAGE P="24668"/>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Request for public comment.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Office of Family Assistance (OFA) is interested in learning about how States deliver Temporary Assistance to Needy Families (TANF) assistance to beneficiaries, whether States have implemented policies and practices to prevent electronic benefit transfer transactions involving TANF assistance in liquor stores, casinos, gambling casinos, or other gaming establishments, and retail establishments which provide adult-oriented entertainment in which performers disrobe or perform in an unclothed state for entertainment; what the States' experiences have been in implementing such policies and practices; and whether States place other similar types of restrictions on assistance usage. OFA also is interested in learning about States' current approaches to ensuring that recipients have adequate access to their cash assistance, including policies that provide access to assistance with no fees or charges or current approaches to imposing fees or charges in connection with receipt of assistance, along with other information relevant to considering what might be minimal fees or charges. Additionally, OFA is interested in hearing the perspectives of vendors, consumer advocates, and any other individuals or entities that have information that could be relevant to the development and implementation of policies and procedures to prevent electronic benefit transfer transactions in certain establishments, and to ensuring access to cash assistance with minimal fees or charges, including opportunities to access assistance without fees or charges.</P>
          <P>The information provided will be used to inform OFA as it develops regulations to implement Section 4004 of the Middle Class Tax Relief and Job Creation Act of 2012 (Pub. L. 112-96), which, among other things, requires States to prevent the use of TANF assistance in electronic benefit transfer transactions at specified locations.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>Written comments must be submitted to the office listed in the<E T="02">ADDRESSES</E>section below on or before June 11, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Interested persons may submit written comments by any of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>. Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Email: TANFEBTTransactions@acf.hhs.gov</E>Please include “Comments on EBT<E T="04">Federal Register</E>Notice” in the subject line of the message.</P>
          <P>•<E T="03">Mail or Courier Delivery:</E>Robert Shelbourne, Office of Family Assistance, Administration for Children and Families, 901 D Street SW., 5th Floor, Washington, DC 20447.</P>
          <P>
            <E T="03">Instructions:</E>If you choose to use an express, overnight, or other special delivery method, ensure that delivery may be made at the address listed under the<E T="02">ADDRESSES</E>section. We urge interested parties to submit comments electronically to ensure that they are received in a timely manner. All comments received will be posted without change to<E T="03">http://www.regulations.gov</E>. This will include any personal information provided.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Robert Shelbourne, Office of Family Assistance, 901 D Street SW., 5th Floor, Washington, DC 20447, (202) 401-5150.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>On February 22, 2012, President Obama signed the Middle Class Tax Relief and Job Creation Act of 2012 (Pub. L. 112-96). Section 4004 of the Act requires States (but does not require Tribes) to prevent the use of Temporary Assistance for Needy Families (TANF) assistance in electronic benefit transfer (EBT) transactions at specified locations. In particular, the law requires States receiving TANF grants “to maintain policies and practices as necessary to prevent assistance provided under the State program funded under this part from being used in any electronic benefit transfer transaction in any liquor store; any casino, gambling casino, or gaming establishment; or any retail establishment which provides adult-oriented entertainment in which performers disrobe or perform in an unclothed state for entertainment.” The law defines an electronic benefit transfer transaction as “the use of a credit or debit card service, automated teller machine, point-of-sale terminal, or access to an online system for the withdrawal of funds or the processing of a payment for merchandise or a service.”</P>
        <P>The law imposes a new reporting requirement as well as a new penalty. Each State is required to report to HHS by February 22, 2014, on its implementation of policies and practices related to restricting recipients' use of EBT cards at the locations specified in the previous paragraph. As required by the law, HHS shall reduce a State's block grant if the State fails to comply with this reporting requirement or if, based on the information that the State reports, HHS finds that the State has not implemented and maintained the required policies and practices. Furthermore, States are required to include in their State plans a statement outlining how they intend to implement policies and procedures to prevent access to assistance through electronic fund transfer transactions at casinos, liquor stores, and establishments providing adult-oriented entertainment. The State plan also must include an explanation of how the State plans to ensure that (1) recipients of the assistance have adequate access to their cash assistance, and (2) recipients of assistance have access to using or withdrawing assistance with minimal fees or charges, including an opportunity to access assistance with no fee or charges, and are provided information on applicable fees and surcharges that apply to electronic fund transactions involving the assistance, and that such information is made publicly available.</P>
        <P>The Office of Family Assistance is seeking responses to the following questions to help inform us as we draft the regulation to implement the statutory requirement. We do not intend to respond to comments provided in response to this Request for Public Comment. However, in the notice of proposed rulemaking, we will provide a general summary of the comments that influenced our policy decisions, and will respond to comments submitted in response to the notice of proposed rulemaking when a final rule is issued.</P>
        <HD SOURCE="HD1">Questions</HD>
        <P>Please identify the question to which you are responding.</P>
        <HD SOURCE="HD2">Benefit Delivery System</HD>
        <P>1. What method or methods of delivery does your State use to provide TANF assistance? For example, does the State use checks, direct deposit into recipient checking account, Electronic Benefit Transfer (EBT) cards, Electronic Payment Cards (EPC) (co-branded with Visa or MasterCard)?</P>
        <P>2. For each method used, does the State currently track the site at which a transaction occurs? If the State is able to identify the site at which a transaction occurs, what process does or would the State need to initiate to determine if the site was a liquor store, gaming establishment or adult entertainment venue? Are there different issues for different types of venues?</P>
        <HD SOURCE="HD2">Implementing EBT Restrictions</HD>
        <P>3. For those with knowledge of what has happened in a State or States that have implemented some form of EBT transaction restriction:</P>

        <P>a. What is the nature of your restriction? Please provide as much<PRTPAGE P="24669"/>specificity as possible, including the definitions used for any establishment type for which TANF benefit access was restricted. If the State's restriction appears to differ from the EBT transaction restriction contained in section 4004 of the Middle Class Tax Relief and Job Creation Act of 2012, please describe those differences.</P>
        <P>b. Was the restriction put in place in response to a legislative mandate or by executive action without a specific legislative mandate? If in response to a legislative mandate, what did the legislature require?</P>
        <P>c. If your State imposes EBT transaction restrictions relating to liquor stores, casinos, gambling casinos, or other gaming establishments, or retail establishments which provide adult-oriented entertainment in which performers disrobe or perform in an unclothed state for entertainment, can you please indicate: which of these locations are subject to restriction, and what is the definition used to describe the restricted location?</P>
        <P>d. What specific method and procedures does the State use?</P>
        <P>e. What challenges to implementation have been encountered and how did the State address them?</P>
        <P>f. Please provide any information available concerning initial and continuing costs.</P>
        <P>g. Does the State identify locations where benefit access is to be restricted through a manual process, an automated process or some combination of the two? Please describe the process for identifying these locations.</P>
        <P>h. Has your State implemented what you consider an effective method of restricting access to EBT usage at specified locations? Please describe why you think it is effective (e.g. cost effective, achieves desired outcomes)?</P>
        <P>i. What concerns have been raised by businesses, electronic benefit vendors, and/or TANF recipients, relating to access, cost, or other issues, in relation to the restrictions? Have particular concerns been raised relating to rural areas of the State? If so, what are those concerns, and how, if at all, have those concerns been addressed?</P>
        <P>j. If your State passes through child support to families receiving TANF assistance, how, if at all, do the TANF assistance restrictions affect provision of passed-through child support?</P>
        <P>k. Are your State's restrictions limited to TANF assistance, or do they affect any other benefits provided electronically? If the restrictions are limited to TANF assistance, how, if at all, do restrictions on accessing TANF assistance affect access to any other benefits?</P>
        <P>l. Are there particular issues not discussed above that have arisen in design or implementation that could be useful for OFA to be aware of in the development of regulations relating to this topic?</P>
        <P>4. With regards to States that have not implemented EBT transaction restrictions, have you considered and examined issues relevant to implementation of such restrictions? If so, can you identify issues and considerations that have arisen for you as you considered such requirements?</P>
        <P>5. For any State, do you currently have information about the incidence of the use of TANF assistance EBT transactions in liquor stores, gaming establishments, and adult entertainment venues?</P>
        <HD SOURCE="HD2">Access Fees or Charges</HD>
        <P>6. With respect to any State, please describe the fees and charges that TANF recipients face when accessing their TANF assistance benefits. If the fees or charges differ based on number of withdrawals or where or how benefits are accessed (such as via an ATM vs. point of sale transaction), please describe the differences in fees under all relevant benefit access mechanisms.</P>
        <P>7. Does your State provide any mechanism that allows TANF assistance recipients to access benefits without facing any fees or charges? If so, please describe.</P>
        <P>8. How, if at all, does your State make information available to TANF assistance recipients about where to access TANF benefits, the fees and charges associated with accessing benefits under various scenarios, and how benefits can be accessed without any fees or charges?</P>
        <P>9. What, if anything, do you think should be done to reduce the costs of accessing TANF benefits?</P>
        <P>10. Please describe any access barriers, that you think TANF assistance recipients currently face or could face under the restrictions and what mechanisms, if any, you think could reduce those access barriers while ensuring that TANF benefits are not accessed through EBT transactions at those establishments for which access is restricted under section 4004 of the Middle Class Tax Relief and Job Creation Act of 2012.</P>
        <HD SOURCE="HD2">EBT Vendor Input</HD>
        <P>11. For companies that provide electronic benefit services to States with respect to TANF assistance, please describe the implementation issues you think States could or would face in implementing the restriction required under section 4004 of the Middle Class Tax Relief and Job Creation Act of 2012. Please describe technical issues, cost implications, and access implications as well as mechanisms for addressing problems identified.</P>
        <P>We welcome any other comments you have about the TANF EBT provisions contained in Section 4004 of the Middle Class Tax Relief and Job Creation Act of 2012.</P>
        <SIG>
          <DATED>Dated: April 5, 2012.</DATED>
          <NAME>Earl Johnson,</NAME>
          <TITLE>Director, Office of Family Assistance.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9260 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <CFR>50 CFR Part 635</CFR>
        <RIN>RIN 0648-XB162</RIN>
        <SUBJECT>Atlantic Highly Migratory Species; Public Conference Call Regarding Recreational Yellowfin Tuna Fishery Data Collection</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 public conference call.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In order to better inform the public and NMFS, a conference call that is open to the public will be held to discuss historical and future data collection in the U.S. recreational yellowfin tuna fishery and the relationship to international yellowfin tuna management (e.g., quota establishment or tracking landings).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>An operator-assisted conference call that is open to the public will be held on April 27, 2012, from 10 a.m. to noon, EDT (phone number 888-593-8429; participant pass code 1629891). During this call, members of the public may ask questions and provide comments, after a brief background presentation.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Randy Blankinship at 727-824-5399 or Dianne Stephan at 978-281-9347.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>Atlantic tunas are managed under the dual authority of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act) and the Atlantic Tuna Conventions Act (ATCA), which authorizes the Secretary of Commerce (Secretary) to promulgate regulations as may be necessary and appropriate to implement<PRTPAGE P="24670"/>recommendations of the International Commission for the Conservation of Atlantic Tunas (ICCAT). The authority to issue regulations under the Magnuson-Stevens Act and ATCA has been delegated from the Secretary to the Assistant Administrator for Fisheries, NOAA. On October 2, 2006, NMFS published in the<E T="04">Federal Register</E>(71 FR 58058) final regulations, effective November 1, 2006, implementing the 2006 Consolidated Highly Migratory Species (HMS) Fishery Management Plan, which details the management measures for Atlantic HMS fisheries.</P>
        <P>At its 2011 meeting, the International Commission for the Conservation of Atlantic Tunas (ICCAT) actively considered country-specific yellowfin tuna allocations, as well as the potential landings histories that could be the basis for those allocations. While the final recommendation did not establish any country-specific allocations, some members of the Atlantic Highly Migratory Species Advisory Panel and the public have expressed an interest in discussing historical and future data collection in the U.S. recreational yellowfin tuna fishery, in case the issue comes up at the 2012 ICCAT meeting.</P>
        <P>NMFS is facilitating the public discussion of this topic through this public conference call. The purpose of this call is to discuss historical and future data collection in the U.S. recreational yellowfin tuna fishery and the relationship to international yellowfin tuna management (e.g., quota establishment or tracking landings). During the call, the background of recreational yellowfin tuna data collection—as well as recent international management developments—will be briefly reviewed. The potential for future data collection will also be discussed. The public will have the opportunity to ask questions and engage in the discussion.</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>16 U.S.C. 1801<E T="03">et seq.</E>
          </P>
        </AUTH>
        <SIG>
          <DATED>Dated: April 20, 2012.</DATED>
          <NAME>Galen Tromble,</NAME>
          <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9971 Filed 4-20-12; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </PRORULE>
  </PRORULES>
  <VOL>77</VOL>
  <NO>80</NO>
  <DATE>Wednesday, April 25, 2012</DATE>
  <UNITNAME>Notices</UNITNAME>
  <NOTICES>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="24671"/>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
        <DATE>April 19, 2011.</DATE>

        <P>The Department of Agriculture has submitted the following information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Comments regarding (a) whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of burden including the validity of the methodology and assumptions used; (c) ways to enhance the quality, utility and clarity of the information to be collected; (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 should be addressed to: Desk Officer for Agriculture, Office of Information and Regulatory Affairs, Office of Management and Budget (OMB),<E T="03">OIRA_Submission@OMB.EOP.GOV</E>or fax (202) 395-5806 and to Departmental Clearance Office, USDA, OCIO, Mail Stop 7602, Washington, DC 20250-7602. Comments regarding these information collections are best assured of having their full effect if received within 30 days of this notification. Copies of the submission(s) may be obtained by calling (202) 720-8958.</P>
        <P>An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.</P>
        <HD SOURCE="HD1">Agricultural Research Service</HD>
        <P>
          <E T="03">Title:</E>Evaluation of User Satisfaction with NAL Internet Sites.</P>
        <P>
          <E T="03">OMB Control Number:</E>0518-0040.</P>
        <P>
          <E T="03">Summary of Collection:</E>There is a need to measure user satisfaction with the National Agricultural Library (NAL) Internet sites in order for NAL to comply with Executive Order 12862, which directs federal agencies that provide significant services directly to the public to survey customers to determine the kind and quality of services they want and their level of satisfaction with existing services. NAL Internet sites are a vast collection of Web pages created and maintained by component organizations of NAL, and are visited by 4.6 million people per month on average. The information generated from this research will enable NAL to evaluate the success of this new modality in response to fulfilling its legislative mandate to disseminate vital agricultural information and truly become the national digital library of agriculture.</P>
        <P>
          <E T="03">Need and Use of the Information:</E>The purpose of the research is to ensure that intended audiences find the information provided on the Internet sites easy to access, clear, informative, and useful. The research will provide a means by which to classify visitors to the NAL Internet sites, to better understand how to serve them. If the information is not collected, NAL will be hindered from advancing its mandate to provide accurate, timely information to its users community.</P>
        <P>
          <E T="03">Description of Respondents:</E>Individuals or households; Business or other for-profit; Not-for-profit institutions; Farms; State, Local or Tribal Government.</P>
        <P>
          <E T="03">Number of Respondents:</E>10,800.</P>
        <P>
          <E T="03">Frequency of Responses:</E>Reporting: Monthly.</P>
        <P>
          <E T="03">Total Burden Hours:</E>900.</P>
        <SIG>
          <NAME>Ruth Brown,</NAME>
          <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-9871 Filed 4-24-12; 8:45 am]</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-0008]</DEPDOC>
        <SUBJECT>Compliance Guide for Residue Prevention and Agency Testing Policy for Residues</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food Safety and Inspection Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of availability and opportunity for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Food Safety and Inspection Service (FSIS) is announcing the availability of a compliance guide for the prevention of violative residues in livestock slaughter establishments. FSIS has posted this compliance guide on its Web page and it may be used immediately. FSIS also welcomes comments on this compliance guide, which will be revised as needed. This notice also discusses changes to the FSIS Residue Repeat Violator List and announces the Agency's intention to subject to increased testing animals from producers who are under an injunction obtained by the Food and Drug Administration because of drug use practices that have led to residue violations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit written comments by June 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>FSIS invites interested persons to submit comments on this notice and the compliance guide, which can be accessed at<E T="03">http://www.fsis.usda.gov/Regulations_&amp;_Policies/Compliance_Guides_Index/index.asp.</E>Comments may be submitted by either of the following methods:</P>

          <P>• Federal eRulemaking Portal: 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>• Mail, including floppy disks or CD-ROMs, and hand- or courier-delivered items: Send to U.S. Department of Agriculture (USDA), FSIS, Docket Clerk, Patriots Plaza 3, 1400 Independence Avenue SW., Room 8-163A, Mailstop 3782, 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-<PRTPAGE P="24672"/>2011-0008. 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 to comments received, go to the FSIS Docket Room at the address listed above between 8:30 a.m. and 4:30 p.m., Monday through Friday.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Daniel Engeljohn, Ph.D., Assistant Administrator for Office of Policy and Program Development, FSIS, U.S. Department of Agriculture, Room 349-E, Jamie Whitten Building, 14th and Independence, SW., Washington DC 20250-3700; telephone (202) 205-0495, fax (202) 720-2025;<E T="03">daniel.engeljohn@fsis.usda.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>
        <P>The U.S. National Residue Program (NRP) is administered by FSIS to collect data on chemical residues in domestic and imported meat, poultry, and egg products and to keep products that are adulterated because of illegal residues out of commerce. FSIS collects samples of meat, poultry, and egg products at federally inspected establishments and analyzes the samples at FSIS laboratories for chemical residues of veterinary drugs, pesticides, and environmental contaminants. With the implementation of the Hazard Analysis and Critical Control Points (HACCP) inspection system, another important component of the NRP is to provide verification of residue control in HACCP systems. As part of the HACCP regulation under 9 CFR part 417, establishments are required to conduct a hazard analysis and to consider the food safety hazards that can be expected to arise from drug and other chemical residues.</P>
        <P>The USDA Office of Inspector General (OIG) report of January 29, 2010, reflecting its review of the NRP with regard to cattle, identified as a contributing factor to violative residue problems the practice of slaughter establishments continuing to purchase livestock from repeat residue violators. OIG also noted that there is often insufficient information at slaughter establishments to identify the producers responsible for the violative residues. The OIG review also underscored the fact that there are two slaughter classes of livestock, dairy cows and bob veal, that account for 90 percent of the residues found in animals presented for slaughter, pointing to the need for the Agency to continue to focus compliance efforts on cull dairy cows and bob veal.</P>
        <P>This Compliance Guide emphasizes that establishments, especially those that slaughter dairy cows and bob veal calves, should apply five basic measures to reduce or prevent the occurrence of violative residues. The guide recommends that establishments should: (1) Confirm producer history; (2) buy animals from producers who have a history of providing residue-free animals and have effective residue prevention programs; (3) ensure that animals are adequately identified to enable traceback; (4) supply information to FSIS at ante-mortem inspection showing that animals in the lot did not come from repeat violators; and (5) notify producers in writing if their animals are found to have either violative residues or detectable levels that do not exceed the tolerance levels established by FDA and FSIS. Persistent non-violative levels residues may indicate a pattern of usage that could result in a violation at some point.</P>
        <P>The Compliance Guide discusses the Agency's revised<E T="03">Residue Repeat Violator List,</E>which has been streamlined for greater ease of use. The List now includes only producers who have provided more than one animal with a violative residue during the past 12 months. The List is also now presented in two differing forms. “Part I” is intended for use by Agency inspection personnel and contains comprehensive information on the individual residue findings (e.g., tissue identified with the violation, chemical compound identified, concentration), organized alphabetically by state and firm name. “Part II” is intended for use by industry and lists producers that have been the source of multiple animals with residue violations and does not provide the technical information contained in Part I. The Agency invites comments on these recent revisions to the List, especially comments related to the List's utility and ease of use. Should the Agency be providing additional information on producers who supply animals with violative residues?</P>
        <P>The Compliance Guide explains that establishments that do not use the information in the Residue Repeat Violator List, either directly or through a letter or certification, would not be taking advantage of a tool to identify livestock from known repeat violators. If an establishment does not follow this guide, and FSIS finds violative residues, the establishment's HACCP system may be inadequate under 9 CFR 417.6.</P>
        <P>FSIS has also been asked recently whether producers could be removed from the Residue Repeat Violator List in less than 12 months in certain circumstances, e.g., if a producer goes three consecutive months without any new violations. The Agency is evaluating this issue and invites comments on it.</P>

        <P>FSIS recently increased testing for residues of carcasses in establishments with violations associated with the same producer or at establishments that fail to apply the residue control measures described in the Compliance Guide. The notices with instructions to FSIS personnel concerning increased testing for residues are available at<E T="03">http://www.fsis.usda.gov/OPPDE/rdad/FSISNotices/21-11.pdf</E>and<E T="03">http://www.fsis.usda.gov/OPPDE/rdad/FSISNotices/12-11.pdf.</E>
        </P>
        <P>In addition, FSIS intends to increase its testing for residues in animals from producers who are under an injunction obtained by the Food and Drug Administration because of drug use practices that have led to residue violations. This action is consistent with FSIS's policy of increasing testing of carcasses at slaughter establishments that are attributable to producers with multiple residue violations.</P>
        <HD SOURCE="HD1">Additional Public Notification</HD>

        <P>Public awareness of all segments of rulemaking and policy development is important. Consequently, in an effort to ensure that minorities, women, and persons with disabilities are aware of this notice, FSIS will announce it online through the FSIS Web page located at<E T="03">http://www.fsis.usda.gov/regulations_&amp;_policies/2010_Notices_</E>
          <E T="03">Index/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. Through the Listserv and Web page, FSIS is able to provide information to a much broader and more diverse audience. 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://<PRTPAGE P="24673"/>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>
        <SIG>
          <DATED>Done at Washington, DC, on April 18, 2012.</DATED>
          <NAME>Alfred V. Almanza,</NAME>
          <TITLE>Administrator.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9797 Filed 4-19-12; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 3410-DM-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Forest Service</SUBAGY>
        <SUBJECT>Notice of Delegation of Authority From the Regional Forester, Pacific Southwest Region, to Forest Supervisor, Eldorado National Forest, for the El Dorado County Rubicon Trail Forest Road and Trail Act Easement</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Forest Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Regional Forester, Pacific Southwest Region, hereby delegates to the Forest Supervisor, Eldorado National Forest, authority to grant a Forest Road and Trail Act easement to El Dorado County for the Rubicon Trail.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>April 19, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>USDA Forest Service, Pacific Southwest Region, 1323 Club Drive, Vallejo, CA 94592.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ramiro Villalvazo, Director, Public Services, (707) 562-8856.</P>
          <SIG>
            <NAME>Randy Moore,</NAME>
            <TITLE>Regional Forester.</TITLE>
          </SIG>
        </FURINF>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-9945 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE M</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Forest Service</SUBAGY>
        <SUBJECT>Grand Mesa, Uncompahgre and Gunnison National Forests; Colorado; Federal Coal Lease Modifications COC-1362 &amp; COC-67232</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 Grand Mesa, Uncompahgre and Gunnison National Forests (GMUG) must decide whether or not to consent to Bureau of Land Management (BLM) modifying the Federal Coal Leases COC-1362 and COC-67232 by adding 800 and 922 acres, respectively, to them. If the GMUG does consent to lease, it will prescribe conditions (as stipulations) for the protection of non-mineral resources</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Public comments for this project were received between April 21 and May 21, 2010 during the preparation of an Environmental Assessment. Comments received during that period will be also be considered in this analysis. These comments have informed the issue analysis and alternative development. Additionally, the agency will continue to accept public comments throughout the preparation of the Draft Environmental Impact Statement, which is estimated to be released in May, 2012. The final environmental impact statement is expected in July, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Written comments should be addressed to Grand Mesa, Uncompahgre, and Gunnison National Forest, Attn: Forest Supervisor, 2250 HWY50, Delta, CO 81416. Comments may also be sent via email to<E T="03">comments-rocky-mountain-gmug@fs.fed.us</E>or via facsimile to 970-874-6698.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Niccole Mortenson, 406-329-3163 or<E T="03">nmortenson@fs.fed.us.</E>
          </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>Under 43 CFR part 3432 (as amended by the Energy Policy Act of 2005), the holder of a federal coal lease may apply to modify a lease by adding up to 960 acres. The federal agencies are responding to applications to modify existing leases. The GMUG and BLM have identified the need to consider issuing two coal lease modifications for federal coal lands immediately adjacent to exiting federal coal leases COC-1362 and COC-67232. The purpose of the lease modifications is to ensure that compliant and super-compliant coal reserves are recovered.</P>
        <P>The BLM, charged with administration of the mineral estate on these Federal lands, is required, by law, to consider leasing Federally-owned minerals for economic recovery. The USDA-Forest Service (FS), as the surface management agency, considers consenting to the BLM leasing reserves underlying lands under its jurisdiction, and prescribes stipulations for the protection of non-mineral resources.</P>
        <HD SOURCE="HD1">Proposed Action</HD>
        <P>Within the jurisdiction of the Forest Service, the proposed action is to consent to BLM modifying existing federal coal leases COC-1362 and COC- 67232 by adding 800 and 922 additional acres (respectively) to ensure that compliant and super-compliant coal reserves are recovered and not bypassed, and to identify stipulations for the protection of non-mineral (i.e. surface) resources.</P>
        <P>The proposed lease modifications are located in Gunnison County, Colorado in portions of sections 10, 11, 13, 14, 22, 23 of T.14S. R. 90W., 6th PM. The modification areas include National Forest System (NFS) surface lands managed by the GMUG and the coal estate managed by the BLM.</P>
        <P>The proposed action deals primarily with underground mining. It is assumed that longwall mining practices would be used. Surface disturbance may include soil subsidence due to removal of the coal. In the event that post-lease surface activities are proposed and authorized, other soil disturbance may occur due to temporary road construction and drilling of methane drainage wells. A Reasonably Foreseeable Mine Plan (RFMP) has been developed to address potential environmental effects. It is detailed to the extent possible and will be included in the analysis.</P>
        <HD SOURCE="HD1">Possible Alternatives</HD>
        <P>
          <E T="03">No Action Alternative</E>—Analysis of the No Action alternative is required by CEQ 40 CFR 1502.14(d). Under the no action alternative, the lease modifications would not be approved, and no mining would occur in these specific areas. Impacts from mining coal under these areas would not occur on these lands, and the effects from on-going land uses could continue including coal mining activities such as exploration and monitoring related to mine activities, as well as continued recreation and grazing. The land would continue to be managed according to Forest Plan standards, goals and guidelines.</P>
        <P>
          <E T="03">The Following is Common to All Action Alternatives-</E>Within the jurisdiction of the Forest Service, the proposed action is to consent to BLM modifying existing federal coal leases COC-1362 and COC-67232 by adding 800 and 922 additional acres (respectively) to ensure that compliant and super-compliant coal reserves are recovered and not bypassed, and to identify stipulations for the protection of non-mineral (i.e. surface) resources.</P>

        <P>The proposed action deals primarily with underground mining. It is assumed<PRTPAGE P="24674"/>that longwall mining practices would be used. Minor surface disturbance would occur on Forest Service lands as a result of subsidence. In the event that post-lease surface activities are proposed and authorized, other soil disturbance may occur due to temporary road construction and drilling of methane drainage wells. A Reasonably Foreseeable Mine Plan (RFMP) has been developed to address potential environmental effects and is detailed to the extent necessary without being predecisional.</P>
        <HD SOURCE="HD2">Stipulations for Action Alternatives</HD>
        <P>As part of the Proposed Action alternative the GMUG Forest Supervisor must decide if the existing stipulations on the existing parent leases are sufficient for the protection of non-mineral (i.e. surface) resources. If not, additional stipulations that will provide for the protection of non-mineral resources must be prescribed. The list below describes the stipulations on the parent leases, and their applicability to the lease modifications and additional or modified stipulations identified for the protection of visual resources Canada lynx.</P>
        <P>In accordance with Forest Service Manual (FSM) 2820, the Standard Notice for Lands under the Jurisdiction of Agriculture is part of the parent leases, and hence would apply to the lease modifications. This Standard Notice includes requirements for Cultural and Paleontological Resources, and Threatened and Endangered Species is noted in the list below. Further, the Standard Notice contains the following language: “The permittee/lessee must comply with all the rules and regulations of the Secretary of Agriculture set forth at Title 36, Chapter II, of the Code of Federal Regulations governing the use and management of the National Forest System (NFS) when not inconsistent with the rights granted by the Secretary of Interior in the permit. The Secretary of Agriculture's rules and regulations must be complied with for (1) all use and occupancy of the NFS prior to approval of an exploration plan by the Secretary of the Interior, (2) uses of all existing improvements, such as forest development roads, within and outside the area permitted by the Secretary of the Interior, and (3) use and occupancy of the NFS not authorized by the permit/operation approved by the Secretary of the Interior.”</P>
        <P>
          <E T="03">Cultural and Paleontological Resources</E>—The FS is responsible for assuring that the leased lands are examined to determine if cultural resources are present and to specify mitigation measures. Prior to undertaking any surface-disturbing activities on the lands covered by this lease, the lessee or operator, unless notified to the contrary by the FS, shall: Contact the FS to determine if a site specific cultural resource inventory is required. If a survey is required then:</P>
        <P>• Engage the services of a cultural resource specialist acceptable to the FS to conduct a cultural resource inventory of the area of proposed surface disturbance. The operator may elect to inventory an area larger than the area of proposed disturbance to cover possible site relocation which may result from environmental or other considerations. An acceptable inventory report is to be submitted to the FS for review and approval at the time a surface disturbing plan of operation is submitted.</P>
        <P>• Implement mitigation measures required by the FS and BLM to preserve or avoid destruction of cultural resource values. Mitigation may include relocation of proposed facilities, testing, salvage, and recordation or other protective measures. All costs of the inventory and mitigation will be borne by the lessee or operator, and all data and materials salvaged will remain under the jurisdiction of the U.S. Government as appropriate.</P>
        <P>• The lessee or operator shall immediately bring to the attention of the FS and BLM any cultural or paleontological resources or any other objects of scientific interest discovered as a result of surface operations under this license, and shall leave such discoveries intact until directed to proceed by FS and BLM.</P>
        <P>
          <E T="03">Endangered or Threatened Species</E>—The FS is responsible for assuring that the leased land is examined prior to undertaking any surface-disturbing activities to determine effects upon any plant or animal species listed or proposed for listing as endangered or threatened, or their habitats. The findings of this examination may result in some restrictions to the operator's plans or even disallow use and occupancy that would be in violation of the Endangered Species Act of 1973 by detrimentally affecting endangered or threatened species or their habitats. The lessee/operator may, unless notified by the FS that the examination is not necessary, conduct the examination on the leased lands at his discretion and cost. This examination must be done by or under the supervision of a qualified resource specialist approved by the FS. An acceptable report must be provided to the FS identifying the anticipated effects of a proposed action on endangered or threatened species or their habitats.</P>
        <P>If there is reason to believe that Sensitive, Threatened or Endangered species of plants or animals, or migratory bird species of high Federal interest are present, or become present in the lease area, the Lessee/Operator shall be required to conduct an intensive field inventory of the area to be disturbed and/or impacted. The inventory shall be conducted by a qualified specialist, and a report of findings prepared. A plan will be made that recommends protection for these species or action necessary to mitigate the disturbance. The cost of conducting such inventory, preparing reports and carrying out mitigation measures shall be borne by the Lessee/Operator.</P>
        <P>
          <E T="03">Canada Lynx</E>—To comply with the GMUG Forest Plan 2008 amendment, the following special constraints will apply if surface use on the lease is proposed in lynx habitat:</P>
        <P>• Winter access will be limited to designated routes.</P>
        <P>Further, should surface-disturbing operations be proposed on the lease in lynx habitat, the following special constraints may apply, depending on site-specific circumstances:</P>
        <P>• Remote monitoring of the development sites and facilities may be required to reduce snow compaction.</P>
        <P>• A reclamation plan (e.g. road reclamation and vegetation rehabilitation) for sites and facilities that promotes the restoration of lynx habitat may be required.</P>
        <P>• Public motorized use on new roads constructed for project-specific purposes will be restricted.</P>
        <P>• Access roads will be designed to provide for effective closures and will be reclaimed or decommissioned at project completion if they are no longer needed for other management objectives.</P>
        <P>• New permanent roads will not be built on ridge tops or in saddles, if possible, or in areas identified as important for lynx habitat connectivity. New roads will be situated away from forested stringers, if possible.</P>
        <P>Raptors—For raptors (except American kestrel) the Lessee will be required to: Conduct surveys for nesting raptors on the lease prior to development of any surface facilities, and no surface activities will be allowed within<FR>1/2</FR>-mile radius of active nest sites between the dates of February 1 and August 15, unless authorized by the Forest Service on a site-specific basis.</P>
        <P>
          <E T="03">Big Game Winter Range</E>—In order to protect big game wintering areas, elk calving areas, and other key wildlife habitat and/or activities, specific surface use may be curtailed during specific times of year. Specific time restrictions<PRTPAGE P="24675"/>for specific species will be evaluated by the Forest Service at the individual project stage, and any additional site specific conditions of use developed at that time.</P>
        <P>
          <E T="03">Water Depletions</E>—In the future, if water to be used for mine related activities is taken from a source that is considered to be tributary waters by the U.S. Fish and Wildlife Service, or which exceeds a depletion amount previously consulted upon, the permitting agency must enter into consultation with the U.S. Fish and Wildlife Service to determine appropriate conservation measures to offset effects to listed fish and critical habitat in the upper Colorado River Basin.</P>
        <P>
          <E T="03">Breeding Birds</E>—If surface disturbance is proposed on the lease, the lessee/operators will be required to conduct breeding bird surveys prior to surface disturbance.</P>
        <P>
          <E T="03">Geologic Hazards</E>—</P>
        <P>COC-1362 Modification—No surface occupancy would be allowed in areas of high geologic hazard or high erosion potential, or on slopes which exceed 60%. Special interdisciplinary team analysis and mitigation plans detailing construction and mitigation techniques would be required on areas where slopes range from 40-60 percent. The interdisciplinary team could include engineers, soil scientist, hydrologist, landscape architect, reclamation specialist and mining engineer.</P>
        <P>COC-67232 Modification—No surface occupancy would be allowed in areas of high geologic hazard or high erosion potential. Special interdisciplinary team analysis and mitigation plans detailing construction and mitigation techniques would be required on areas where slopes range from 40-60 percent. The interdisciplinary team could include engineers, soil scientist, hydrologist, landscape architect, reclamation specialist and mining engineer.</P>
        <P>
          <E T="03">Baseline Information</E>—The operator/lessee would be required to perform adequate baseline studies to quantify existing surface and subsurface resources. Existing data can be used for baseline analyses provided that the data is adequate to locate, quantify, and demonstrate interrelationships between geology, topography, hydrogeology, and hydrology. Baseline studies are critical to the success of future observation and assessment of mining related effects on resources.</P>
        <P>
          <E T="03">Monitoring Program</E>—The operator/lessee of the lease tract would be required to establish or amend a monitoring program to be used as a continuing record of change over time of area resources in order to assess mining induced impacts. The monitoring program shall provide the procedures and methodologies to adequately assess interrelationships between geology, topography, hydrogeology, and hydrology identified in the baseline assessment to mining activities in the lease tract area. The monitoring program shall incorporate baseline data so as to provide a continuing record over time.</P>
        <P>
          <E T="03">Riparian, Wetland or Floodplain</E>—Surface use or disturbances (except for surface subsidence and resource monitoring purposes defined in the approved mining permit) will avoid riparian, wetland or floodplain areas, and a buffer zone surrounding these areas (the definition of riparian areas and appropriate buffer zone will be consistent with that defined in the Forest Service Manual and Rocky Mountain Region's Water Conservation Practices Handbook. Wetland definition will follow Army Corps of Engineers guidelines) unless no practical alternatives exist.</P>
        <P>
          <E T="03">Subsidence</E>(Language from COC-1362 parent lease)—If subsidence adversely affects surface resources in any way (including, but not limited to a documented water loss), the Lessee, at their expense will be responsible to: Restore stream channels, stock ponds, protect stream flow with earthwork or temporary culverts, restore affected roads, or provide other measures to repair damage or replace any surface water and/or developed ground water source, stock pond, water conveyance facilities, with water from an alternate source in sufficient quantity and quality to maintain existing riparian habitat, livestock and wildlife use, or other land uses as authorized by 36 CFR part 251. The Lessee/Operator shall be responsible for monitoring, repairing and/or mitigating subsidence effects on existing facilities under Special Use Permit with the Forest Service. Monitoring, repair and/or mitigation, if needed, would be performed at the Lessee's expense. These requirements will be coordinated with the District Ranger and the Special Use Permittee.</P>
        <P>
          <E T="03">Roadless</E>(Lease Notice Only)—All or parts of the following lands encompassed in this lease are in the West Elk Inventoried Roadless Area and may be subject to restrictions on road-building pursuant to rules and regulations of the Secretary of Agriculture applicable at the time any roads may be proposed on the lease. Legal descriptions are approximate. Locations of any proposed surface use would be verified for relationship to IRA boundaries using site-specific maps if/when surface operations are proposed.</P>
        <P>
          <E T="03">Visuals</E>—Within the lease modification area, the lessee will work with the District Ranger and his/her representative to see that all mine operations are situated on the ground in such a manner that reasonably minimizes impacts to the scenic integrity of that landscape, as prescribed in the Forest Plan.</P>
        <P>
          <E T="03">Coal Mine Methane</E>—The parent leases also contain lease terms from BLM regarding coal mine methane that would be carried forward to the lease modifications. These are addressed as lease addendum as follows:</P>
        <P>Sec. 3. Notwithstanding the language in Sec. 2 of this lease and subject to the terms and conditions below, lessee is authorized to drill for, extract, remove, develop, produce and capture for use or sale any or all of the coal mine methane from the above described lands that it would otherwise be required to vent or discharge for safety purposes by applicable laws and regulations. For purposes of this lease, “coal mine methane” means any combustible gas located in, over, under, or adjacent to the coal resources subject to this lease, that will or may infiltrate underground mining operations.</P>
        <P>Sec. 4. Notwithstanding any other provision of this lease, nothing herein shall, nor shall it be interpreted to, waive, alter or amend lessee's right to vent, discharge or otherwise dispose of coal mine methane as necessary for mine safety or to mine the coal deposits consistent with permitted underground mining operations and federal and state law and regulation. Lessee shall not be obligated or required to capture for use or sale coal mine methane that would otherwise be vented or discharged if the capture of coal mine methane, independent of activities related to mining coal, is not economically feasible or if the coal mine methane must be vented in order to abate the potential hazard to the health or safety of the coal miners or coal mining activities. In the event of a dispute between lessor and lessee as to the economic or other feasibility of capturing for use or sale the coal mine methane, lessor's remedy as a prevailing party shall be limited to recovery of the compensatory royalties on coal mine methane not captured for use or sale by lessee. Lessee shall have the right to continue all mining activities under the lease, including venting coal mine methane, pending resolution of any dispute regarding the application of the terms of Sections 3 and 4.</P>

        <P>Sec. 2(c) COAL MINE METHANE OPERATIONS AND ROYALTIES—Notwithstanding the language in Part II, Section 2(a) of this lease, the royalty<PRTPAGE P="24676"/>shall be 12.5 percent of the value of any coal mine methane that is captured for use or sale from this lease. For purposes of this lease, the term “capture for use or sale” shall not include and the royalty shall not apply to coal mine methane that is vented or discharged and not captured for the economic or safety reasons described in Part I, Section 4 of this lease. Lessee shall have no obligation to pay royalties on any coal mine methane that is used on or for the benefit of mineral extraction at the West Elk coal mine. When not inconsistent with any express provision of this lease, the lease is subject to all rules and regulations related to Federal gas royalty collection in Title 30 of the Code of Federal Regulations now or hereinafter in effect and lessor's rules and regulations related to applicable reporting and gas measurement now or hereinafter in effect</P>
        <P>
          <E T="03">Severability</E>—In the event any provision of this addendum is subject to a legal challenge or is held to be invalid, unenforceable or illegal in any respect, the validity, legality and enforceability of this lease will not in any way be affected or impaired thereby and lessee will retain, in accordance with the terms of this lease, the exclusive right and privilege to drill for, mine, extract, remove or otherwise process and dispose of the coal deposits, upon, or under the lands described in this lease, including the right to vent or discharge coal mine methane for safety purposed as required by applicable laws and regulation.</P>
        <P>
          <E T="03">Proposed Action (Alternative 2)</E>—Includes all of the information common to all action alternatives above. Because leasing itself does not involve any mineral development or surface disturbance, it is necessary to project the amount of surface use or activity that may result during lease development in order to disclose potential effects and inform decision-making. To facilitate analyzing potential surface impacts, the analysis will assume a reasonably foreseeable mine plan (RFMP) for this leasing decision. It must be noted however, that decisions pertaining to surface use and disturbance, with the exception of subsidence impacts, are not made at the leasing stage. Rather, the decisions related to permit-related surface activities are made when and if site-specific surface uses are proposed, and are evaluated through the State permitting process based on their own merits. The environmental effects analysis of post-lease surface use and disturbance associated with this alternative will include subsidence and methane drainage well pads. Under the regulatory framework of the 2001 Roadless Area Conservation Rule, future road building is prohibited; however methane drainage is permitted.</P>
        <P>
          <E T="03">Alternative 3</E>—Includes all of the information common to all action alternatives above. Similar to Alternative 2, the analysis will assume a RFMP for this alternative. However, the environmental effects of this alternative will be analyzed under the regulatory framework of the Proposed Colorado Roadless Rule. As the proposed rule would apply to this leasing decision, temporary road building would be allowed.</P>
        <HD SOURCE="HD1">Lead and Cooperating Agencies</HD>
        <FP SOURCE="FP-2">Cooperating Agencies:</FP>
        <FP SOURCE="FP1-2">Uncompahgre Field Office, Bureau of Land Management</FP>
        <FP SOURCE="FP1-2">Colorado State Office, Bureau of Land Management</FP>
        <FP SOURCE="FP1-2">Western Region, Office of Surface Mining Reclamation and Enforcement</FP>
        <FP SOURCE="FP1-2">Colorado Division of Reclamation Mining and Safety (pending)</FP>
        <HD SOURCE="HD1">Responsible Official</HD>
        <FP SOURCE="FP-1">GMUG Forest Supervisor</FP>
        <HD SOURCE="HD1">Nature of Decision To Be Made</HD>
        <P>Given the purpose and need, the Authorized Officer will review the proposed action, the other alternatives, and the environmental consequences in order to decide the following:</P>
        <P>• Whether or not to consent to the BLM modifying existing Federal Coal Lease COC-1362 by adding 800 acres according to the Federal Coal Leasing Amendments Act of 1976;</P>
        <P>• Whether or not to consent to the BLM modifying existing Federal Coal Lease COC-67232 by adding 922 acres according to the Federal Coal Leasing Amendments Act of 1976;</P>
        <P>• Prescribe stipulations needed for the protection of non-mineral resources by determining if the existing stipulations on the parent lease are sufficient. If they are not sufficient, prescribe additional stipulations that will provide for the protection of non-mineral resources.</P>
        <P>The Forest Service Authorized Officer will determine if the activity is consistent with the GMUG Forest Plan.</P>
        <P>The Forest Service decision will be made based on the analysis relative to the No Action and Proposed Action Alternatives.</P>
        <P>The BLM is preparing a separate leasing analysis under their regulations. The BLM Colorado State Director is the Authorized Officer for the BLM, and will decide whether or not to modify the existing coal lease under the Mineral Leasing Act, as amended, and the federal regulations under 43 CFR 3400. The Uncompahgre Field Office Manager is responsible for providing the State Director with briefings and recommendations.</P>
        <P>Specifically, the BLM will decide whether to:</P>
        <P>• Adopt the No-Action Alternative (no leasing);</P>
        <P>• Adopt the proposed action (lease the coal as applied for by the applicants);</P>
        <P>• Adopt an alternative with features of both of the alternatives; or</P>
        <P>• Adopt the action alternative with additional mitigation measures.</P>
        <P>BLM cannot issue leases without the consent of the surface managing agency.</P>
        <P>OSM is a cooperating agency per an existing Memorandum of Understanding and may prepare a mining plan modification related to the subsequent permitting of these lease modifications.</P>
        <HD SOURCE="HD1">Preliminary Issues</HD>
        <P>Preliminary issues have been identified during the preparation of an Environmental Assessment. They include the following:</P>
        <P>
          <E T="03">Indirect and Cumulative Environmental Effects of Leasing</E>—</P>
        <P>• Surface disturbance other than from mining (subsidence) may occur as a result of mining.</P>
        <P>• Reasonably foreseeable impacts to the surface and other resources may occur as a result of mining.</P>
        <P>
          <E T="03">Mitigation Measures—</E>Forest Service must validate the effectiveness of proposed mitigation measures.</P>
        <P>Air Quality—</P>

        <P>• Effects of the proposed action may occur on air quality including ambient ozone, PM<E T="52">2.5</E>, PM<E T="52">10</E>, VOCs, Class I areas in compliance with the Clean Air Act.</P>
        <P>• Cumulative effects to air quality associated with coal burning may occur as a result of the Proposed Action.</P>
        <P>
          <E T="03">Roadless Character—</E>Roadless character in the West Elk Roadless Area may be affected either indirectly or cumulatively through consenting to lease.</P>
        <P>
          <E T="03">Methane</E>—Alternatives to venting including flaring, capture and use, or destroying ventilation air (VAM) methane must be analyzed in detail.</P>
        <P>
          <E T="03">Coal Reserve—</E>Address the effects of adding coal reserves on coal resource recovery.</P>
        <P>
          <E T="03">Socioeconomics—</E>
        </P>
        <P>• Coal mining activities are vital to the local and regional economies.</P>
        <P>• Coal from the North Fork Valley helps fuel clean coal technology and provide the USA with low-cost, reliable energy.</P>
        <P>
          <E T="03">Visual Resources</E>—Removal of vegetation, ground disturbance and<PRTPAGE P="24677"/>structures related to future surface facilities needed to manage methane may negatively impact visuals.</P>
        <P>
          <E T="03">Wildlife</E>—Removal of vegetation related to future surface facilities needed to manage methane may negatively impact Canada lynx.</P>
        <P>
          <E T="03">Subsidence</E>—</P>
        <P>• Subsidence may affect wildlife habitat, including effects to riparian habitat</P>
        <P>• Subsidence may affect water resources including local water quality and quantity.</P>
        <P>• Subsidence may affect cultural resources.</P>
        <P>• Subsidence may affect other land uses, including range improvements, cattle trails and other multiple uses of the land.</P>
        <P>
          <E T="03">Climate Change</E>—Effects on climate change may occur from mining coal which stem from the release of methane through the mine ventilation system, release of methane through any gob vent boreholes and release of CO<E T="52">2</E>caused by the burning of coal that is mined.</P>
        <HD SOURCE="HD1">Scoping Process</HD>
        <P>In addition to receiving and considering previous comments from the public, the agency continues to accept and consider public comments to guide the development of this environmental impact statement and the resulting decision. Additional comments should clearly articulate the reviewer's concerns and contentions, and focus on the adequacy of stipulations proposed as they relate to the protection of surface resources. Comments received in response to this solicitation, including names and addresses of those who comment, will be part of the public record for this proposed action. Comments submitted anonymously will be accepted and considered, however.</P>
        <SIG>
          <DATED>Dated: April 19, 2012.</DATED>
          <NAME>Sherry Hazelhurst,</NAME>
          <TITLE>Acting Forest Supervisor.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9920 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-11-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>National Agricultural Statistics Service</SUBAGY>
        <SUBJECT>Notice of Intent To Seek Approval to Revise and Extend a Currently Approved Information Collection</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Agricultural Statistics 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, this notice announces the intention of the National Agricultural Statistics Service (NASS) to request revision and extension of a currently approved information collection, the Egg, Chicken, and Turkey Surveys. A revision to burden hours will be needed due to changes in the size of the target population, sampling design, and/or questionnaire length.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments on this notice must be received by June 25, 2012 to be assured of consideration.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number 0535-0004, by any of the following methods:</P>
          <P>•<E T="03">Email: ombofficer@nass.usda.gov.</E>Include docket number above in the subject line of the message.</P>
          <P>•<E T="03">Fax:</E>(202) 720-6396.</P>
          <P>•<E T="03">Mail:</E>Mail any paper, disk, or CD-ROM submissions to: David Hancock, NASS Clearance Officer, U.S. Department of Agriculture, Room 5336 South Building, 1400 Independence Avenue SW., Washington, DC 20250-2024.</P>
          <P>•<E T="03">Hand Delivery/Courier:</E>Hand deliver to: David Hancock, NASS Clearance Officer, U.S. Department of Agriculture, Room 5336 South Building, 1400 Independence Avenue SW., Washington, DC 20250-2024.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Joseph T. Reilly, Associate Administrator, National Agricultural Statistics Service, U.S. Department of Agriculture, (202) 720-4333. Copies of this information collection and related instructions can be obtained without charge from David Hancock, NASS Clearance Officer, at (202) 690-2388.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <P SOURCE="NPAR">
          <E T="03">Title:</E>Egg, Chicken, and Turkey Surveys.</P>
        <P>
          <E T="03">OMB Number:</E>0535-0004.</P>
        <P>
          <E T="03">Expiration Date of Approval:</E>October 31, 2012.</P>
        <P>
          <E T="03">Type of Request:</E>Intent to seek approval to revise and extend a currently approved information collection.</P>
        <P>
          <E T="03">Abstract:</E>The primary objective of the National Agricultural Statistics Service (NASS) is to prepare and issue State and national estimates of crop and livestock production, disposition, and prices. The Egg, Chicken, and Turkey Surveys obtain basic poultry statistics from voluntary cooperators throughout the Nation. Statistics are published on placement of pullet chicks for hatchery supply flocks; hatching reports for broiler-type, egg-type, and turkey eggs; number of layers on hand; total table egg production; and production and value estimates for eggs, chickens, and turkeys. The frequency of the surveys being conducted include weekly, monthly and annually. This information is used by producers, processors, feed dealers, and others in the marketing and supply channels as a basis for production and marketing decisions. Government agencies use these estimates to evaluate poultry product supplies. The information is an important consideration in government purchases for the National School Lunch Program and in formulation of export-import policy. The current expiration date for this docket is October 31, 2012. NASS intends to request that the surveys be approved for another 3 years.</P>
        <P>
          <E T="03">Authority:</E>These data will be collected under the authority of 7 U.S.C. 2204(a). Individually identifiable data collected under this authority are governed by section 1770 of the Food Security Act of 1985, 7 U.S.C. 2276, which requires USDA to afford strict confidentiality to non-aggregated data provided by respondents. This notice is submitted in accordance with the Paperwork Reduction Act of 1995 (at 44 U.S.C. 3501,<E T="03">et seq.</E>) and Office of Management and Budget regulations at 5 CFR part 1320.</P>
        <P>
          <E T="03">Estimate of Burden:</E>Public reporting burden for this collection of information is estimated between 8 and 15 minutes per respondent per survey.</P>
        <P>
          <E T="03">Respondents:</E>Farmers, ranchers, farm managers, and farm contractors.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>3,100.</P>
        <P>
          <E T="03">Estimated Total Annual Burden on Respondents:</E>4,200 hours.</P>

        <P>Copies of this information collection and related instructions can be obtained without charge from the NASS Clearance Officer, at (202) 690-2388 or at:<E T="03">ombofficer@nass.usda.gov.</E>
        </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, 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 those who are to respond, through the use of appropriate automated, electronic, mechanical, technological or other forms of information technology collection methods. All responses to this notice will become a matter of public record and be summarized in the request for OMB approval.</P>
        <SIG>
          <PRTPAGE P="24678"/>
          <DATED>Signed at Washington, DC, March 21, 2012.</DATED>
          <NAME>Joseph T. Reilly,</NAME>
          <TITLE>Associate Administrator.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9991 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-20-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Rural Business-Cooperative Service</SUBAGY>
        <SUBJECT>Notice of Request for Extension of a Currently Approved Information Collection</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Rural Business-Cooperative Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed collection; comments requested.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In accordance with the Paperwork Reduction Act of 1995, this notice announces the Rural Business-Cooperative Service's intention to request an extension for a currently approved information collection in support of the program for the 1890 Land Grant Institutions Rural Entrepreneurial Outreach and Development Initiative Program.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments on this notice must be received by June 25, 2012 to be considered.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Natalie Melton, Program Management Specialist, Rural Development, USDA, STOP 3250, Room 4217, 1400 Independence Avenue SW., Washington, DC 20250-3250. Telephone: (202) 690-1371, email:<E T="03">Natalie.melton@wdc.usda.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P SOURCE="NPAR">
          <E T="03">Title:</E>1890 Land Grant Institutions Rural Entrepreneurial Outreach and Development Initiative Program.</P>
        <P>
          <E T="03">OMB Number:</E>0570-0041.</P>
        <P>
          <E T="03">Expiration Date of Approval:</E>July 31, 2012.</P>
        <P>
          <E T="03">Type of Request:</E>Extension of a currently approved information collection.</P>
        <P>
          <E T="03">Abstract:</E>The collection of this information will allow the Agency to determine the eligibility of the applicants; determine the specific purpose for which the funds will be utilized; determine the timeframes or dates by which activities surrounding the use of funds will be accomplished; determine the feasibility of the project; and to evaluate applicants' experience in managing similar activities.</P>
        <P>Without the collection of this information, there would be no basis on which to award funds.</P>
        <P>
          <E T="03">Estimate of Burden:</E>Public reporting burden for this collection is estimated to average 2.5 hours per response.</P>
        <P>
          <E T="03">Respondents:</E>Only 1890 Land Grant Institutions of Higher Education and Tuskegee University.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>18.</P>
        <P>
          <E T="03">Estimated Number of Responses per Respondent:</E>17.</P>
        <P>
          <E T="03">Estimated Number of Responses:</E>297.</P>
        <P>
          <E T="03">Estimated Total Annual Burden on Respondents:</E>728 hours.</P>
        <P>Copies of this information collected can be obtained from Jeanne Jacobs, Regulations and Paperwork Management Branch: (202) 692-0040.</P>
        <P>Comments are invited on: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of Rural Development, including whether the information will have practical utility; (b) the accuracy of Rural Development's estimate of the burden to collect the required information, including the validity of the strategy used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology. Comments on the paperwork burden may be sent to Jeanne Jacobs, Regulations and Paperwork Management Branch, Rural Development, U.S. Department of Agriculture, STOP 0742, 1400 Independence Avenue SW., Washington, DC 20250-0742. All responses to this notice will be summarized and included in the request for OMB approval. All comments will become a matter of public record.</P>
        <SIG>
          <DATED>Dated: April 18, 2012.</DATED>
          <NAME>Judith A. Canales,</NAME>
          <TITLE>Administrator, Rural Business-Cooperative Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9975 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-XY-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Rural Business-Cooperative Service</SUBAGY>
        <SUBJECT>Announcement of Small, Socially-Disadvantaged Producer Grant (SSDPG) Application Deadlines in Fiscal Year 2012</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Rural Business-Cooperative Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of funding availability.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Rural Business-Cooperative Service announces the availability of approximately $3 million in competitive grant funds for the FY 2012 SSDPG program. See the Consolidated and Further Continuing Appropriations Act, 2012 (2012 Appropriations Act) (Pub. L. 112-55). We request proposals from applicants that will provide technical assistance to small, socially-disadvantaged agricultural producers in rural areas. Eligible applicants include Cooperatives, Groups of Cooperatives, and Cooperative Development Centers. The maximum award per grant is $175,000.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Completed applications for grants must be submitted on paper or electronically according to the following deadlines:</P>
          <P>Paper copies must be postmarked and mailed, shipped, or sent overnight no later than July 24, 2012 to be eligible for FY 2012 grant funding. Late applications are not eligible for FY 2012 grant funding.</P>
          <P>Electronic copies must be received by April 25, 2012, to be eligible for FY 2012 grant funding. Late applications will not be eligible for FY 2012 grant funding.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Application materials for the SSDPG program may be obtained at<E T="03">http://www.rurdev.usda.gov/BCP_SSDPG.html</E>or by contacting your USDA Rural Development State Office. Contact information for State Offices can be found at<E T="03">http://www.rurdev.usda.gov/recd_map.html</E>
          </P>

          <P>Paper applications must be submitted to the USDA Rural Development State Office in the State where your organization's main office is located. Electronic applications must be submitted through the Grants.gov Web site at<E T="03">http://www.grants.gov.</E>Please read the instructions found on the Grants.gov Web site and follow them carefully.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Visit the program Web site at<E T="03">http://www.rurdev.usda.gov/BCP_SSDPG.html</E>for application assistance or contact your USDA Rural Development State Office. You are strongly encouraged to contact your State Office well in advance of the deadline to discuss your Project and ask any questions about the application process.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Overview</HD>
        <P>
          <E T="03">Federal Agency Name:</E>USDA Rural Business Cooperative Service.</P>
        <P>
          <E T="03">Funding Opportunity Title:</E>Small, Socially-Disadvantaged Producer Grant.</P>
        <P>
          <E T="03">Announcement Type:</E>Initial announcement.</P>
        <P>
          <E T="03">Catalog of Federal Domestic Assistance Number:</E>10.77.1<PRTPAGE P="24679"/>
        </P>
        <P>
          <E T="03">Dates:</E>Application Deadline: Completed applications for grants may be submitted on paper or electronically according to the following deadlines:</P>
        <P>Paper copies must be postmarked and mailed, shipped, or sent overnight no later than July 24, 2012 to be eligible for FY 2012 grant funding. Late applications are not eligible for FY 2012 grant funding.</P>
        <P>Complete electronic copies must be received by July 24, 2012, to be eligible for FY 2012 grant funding. Late applications are not eligible for FY 2012 grant funding.</P>
        <HD SOURCE="HD1">I. Funding Opportunity Description</HD>
        <P>The 2012 Appropriations Act authorized up to $3 million for grants for Cooperative Development Centers, individual Cooperatives, or Groups of Cooperatives that serve socially-disadvantaged groups and where a majority of their governing board is comprised of members of socially-disadvantaged groups or at least 75 percent of their membership is comprised of socially-disadvantaged producers. The SSDPG Program is authorized by 310B (e) of the Consolidated Farm and Rural Development Act (7 U.S.C. 1932). The primary objective of the SSDPG program is to provide Technical Assistance to Small, Socially-Disadvantaged Agricultural Producers. Grants are awarded on a competitive basis. The maximum award amount per grant is $175,000.</P>
        <HD SOURCE="HD2">Definitions</HD>
        <P>
          <E T="03">Agency</E>—Rural Business-Cooperative Service, an agency of the United States Department of Agriculture (USDA) Rural Development or a successor agency.</P>
        <P>
          <E T="03">Agricultural Commodity</E>—An unprocessed product of farms, ranches, nurseries, and forests. Agricultural commodities include: livestock, poultry, and fish; fruits and vegetables; grains, such as wheat, barley, oats, rye, triticale, rice, corn, and sorghum; legumes, such as field beans and peas; animal feed and forage crops; seed crops; fiber crops, such as cotton; oil crops, such as safflower, sunflower, corn, and cottonseed; trees grown for lumber and wood products; nursery stock grown commercially; Christmas trees; ornamentals and cut flowers; and turf grown commercially for sod. Agricultural commodities do not include horses or animals raised as pets, such as cats, dogs, and ferrets.</P>
        <P>
          <E T="03">Conflict of Interest</E>—A situation in which the ability of a person or entity to act impartially would be questionable due to competing professional or personal interests. An example of conflict of interest occurs when the grantee's employees, board of directors, including their immediate family, have a legal or personal financial interest in the recipients receiving the benefits or services of the grant.</P>
        <P>
          <E T="03">Cooperative</E>—A farmer- or rancher-owned and -controlled business, organized and chartered as a cooperative, from which benefits are derived and distributed equitably on the basis of use by each of the farmer or rancher owners whose primary focus is to provide assistance to Small, Socially-Disadvantaged Agricultural Producers and where a majority of their governing board is comprised of individuals who are members of socially-disadvantaged groups or at least 75 percent of their membership is comprised of socially-disadvantaged producers.</P>
        <P>
          <E T="03">Cooperative Development Center</E>—A nonprofit corporation or accredited institution of higher education that is established or operated by the grantee for rural cooperative development. It may or may not be an independent legal entity separate from the grantee. The Center's main objective is to assist Cooperatives with their startup, expansion or operational improvement in order to promote development in rural areas of services and products, processes that can be used in the marketing of products, or enterprises that create Value-Added to farm products through processing or marketing activities. Cooperative development activities may include, but are not limited to, Technical Assistance, research services, educational services and advisory services. Operational improvement includes making the Cooperative more efficient or better managed.</P>
        <P>
          <E T="03">Cooperative Programs</E>—The office within Rural Business-Cooperative Service, and any successor organization, that administers programs authorized by the Cooperative Marketing Act of 1926 (7 U.S.C. 451<E T="03">et seq.</E>) and such other programs identified in USDA regulations.</P>
        <P>
          <E T="03">Economic Development</E>—The economic growth of an area as evidenced by increase in total income, employment opportunities, decreased out-migration of population, value of production, increased diversification of industry, higher labor force participation rates, increased duration of employment, higher wage levels, or gains in other measurements of economic activity, such as land values.</P>
        <P>
          <E T="03">Feasibility Study</E>—An analysis of the economic, market, technical, financial, and management feasibility of a proposed Project.</P>
        <P>
          <E T="03">Group of Cooperatives</E>—A group of Cooperatives whose primary focus is to provide assistance to Small, Socially-Disadvantaged Agricultural Producers and where a majority of their governing board is comprised of individuals who are members of socially-disadvantaged groups or at least 75 percent of their membership is comprised of socially-disadvantaged producers.</P>
        <P>
          <E T="03">Operating Cost</E>—The day-to-day expenses of running a business; for example: utilities, rent, salaries, depreciation, product production costs, marketing and advertising, and other basic overhead items.</P>
        <P>
          <E T="03">Project</E>—Includes all activities to be funded by the Small Socially-Disadvantaged Producer Grant.</P>
        <P>
          <E T="03">Rural and Rural Area</E>—Any area of a State:</P>
        <P>(1) Not in a city or town that has a population of more than 50,000 inhabitants, according to the latest decennial census of the United States; and</P>
        <P>(2) The contiguous and adjacent urbanized area,</P>
        <P>(3) Urbanized areas that are rural in character as defined by 7 U.S.C. 1991 (a) (13), as amended by Section 6018 of the Food, Conservation, and Energy Act of 2008, Public Law 110-246 (June 18, 2008).</P>
        <P>(4) For the purposes of this definition, cities and towns are incorporated population centers with definite boundaries, local self-government, and legal powers set forth in a charter granted by the State. Notwithstanding any other provision of this paragraph, within the areas of the County of Honolulu, Hawaii, and the Commonwealth of Puerto Rico, the Secretary may designate any part of the areas as a rural area if the Secretary determines that the part is not urban in character, other than any area included in the Honolulu census designated place (CDP) or the San Juan CDP.</P>
        <P>
          <E T="03">Rural Development</E>—A mission area within USDA consisting of the Office of Under Secretary for Rural Development, Rural Development Business and Cooperative Programs, Rural Development Housing Programs, and Rural Development Utilities Programs and any successors.</P>
        <P>
          <E T="03">Small, Socially-Disadvantaged Producer</E>—Socially-Disadvantaged persons or at least 75 percent Socially-Disadvantaged Producer-owned entities including farmers, ranchers, loggers, agricultural harvesters, and fishermen, that have averaged $250,000 or less in annual gross sales of agricultural products in the last 3 years.</P>
        <P>
          <E T="03">Socially-Disadvantaged Producer</E>—Individual agricultural producer who is<PRTPAGE P="24680"/>a member of a group whose members have been subjected to racial, ethnic or gender prejudice, without regard for their individual qualities.</P>
        <P>
          <E T="03">State</E>—Includes each of the several states, the Commonwealth of Puerto Rico, the Virgin Islands of the United States, Guam, American Samoa, the Commonwealth of the Northern Mariana Islands, and, as may be determined by the Secretary to be feasible, appropriate and lawful, the Federated States of Micronesia, the Republic of the Marshall Islands and the Republic of Palau.</P>
        <P>
          <E T="03">Technical Assistance</E>—An advisory service performed for the benefit of a Small, Socially-Disadvantaged Producer such as market research; product and/or service improvement; legal advice and assistance; Feasibility Study, business plan, and marketing plan development; and training. Technical Assistance does not include the Operating Costs of a cooperative being assisted.</P>
        <P>
          <E T="03">Value-Added</E>—The incremental value that is realized by the producer from an agricultural commodity or product as the result of a change in its physical state, differentiated production or marketing, as demonstrated in a business plan, or product segregation. Incremental value may be realized by the producer as a result of either an increase in value to buyers or the expansion of the overall market for the product. Examples include milling wheat into flour, slaughtering livestock or poultry, making strawberries into jam, and marketing of organic products.</P>
        <HD SOURCE="HD1">II. Award Information</HD>
        <P>A.<E T="03">Type of Award:</E>Grant.</P>
        <P>B.<E T="03">Fiscal Year Funds:</E>FY 2012.</P>
        <P>C.<E T="03">Approximate Total Funding:</E>$3 million.</P>
        <P>D.<E T="03">Approximate Number of Awards:</E>17.</P>
        <P>E.<E T="03">Floor of Award Range:</E>None.</P>
        <P>F.<E T="03">Ceiling of Award Range:</E>$175,000.</P>
        <P>G.<E T="03">Anticipated Award Date:</E>September 1, 2012.</P>
        <P>H.<E T="03">Budget Period Length:</E>12 months.</P>
        <P>I.<E T="03">Project Period Length:</E>12 months.</P>
        <HD SOURCE="HD1">III. Eligibility Information</HD>
        <P>A.<E T="03">Eligible Applicants.</E>Grants may be made to Cooperatives, Groups of Cooperatives, and Cooperative Development Centers. You must be able to verify your legal structure in the State in which you are incorporated. Grants may not be made to public bodies or to individuals.</P>
        <P>B.<E T="03">Cost Sharing or Matching.</E>No matching funds are required.</P>
        <P>C.<E T="03">Other Eligibility Requirements</E>
        </P>
        <P>
          <E T="03">Use of Funds:</E>Funds may only be used for Technical Assistance Projects as defined in this Notice.</P>
        <P>
          <E T="03">Project Area Eligibility:</E>The proposed Project must take place in a Rural Area as defined in this Notice.</P>
        <P>
          <E T="03">Grant Period Eligibility:</E>If awarded, grant funds must be used within 12 months. Applications must have a time frame of one year or less. Your proposed time frame should begin no earlier than the grant award date and end no later than December 31, 2013. However, you should note that the anticipated award date is September 1 so your proposed start date should be after September 1, 2012. Projects must be completed within the 12-month time frame. The Agency has the option to approve requests to extend the grant period for up to 12 months. However, if you receive another SSDPG grant during the next grant cycle, the first grant must be closed before funds can be obligated for the new grant. Applications that request funds for a time period ending after December 31, 2013, will not be considered for funding.</P>
        <P>
          <E T="03">Completeness Eligibility:</E>Your application must provide all of the information requested in Section IV (B) of this Notice. Applications lacking sufficient information to determine eligibility and scoring will be considered ineligible.</P>
        <P>
          <E T="03">Multiple Grant Eligibility:</E>You may only submit one SSDPG grant application each funding cycle.</P>
        <P>
          <E T="03">Activity Eligibility:</E>Your application must propose Technical Assistance that will benefit Small Socially-Disadvantaged Producers in Rural Areas. Please review section IV (G) of this Notice, “Funding Restrictions,” carefully. Your application will be ineligible for funding if it includes ineligible costs that equal more than 10 percent of total Project costs. If your application contains ineligible costs that equal or are less than 10 percent of total Project costs, it may still be considered for funding. You must remove the ineligible costs from the budget if your application is selected for funding. You can replace the ineligible costs with eligible activities or reduce the grant award by the amount of ineligible costs. Applications that duplicate current activities or activities paid for by other grant programs will not be funded.</P>
        <HD SOURCE="HD1">IV. Application and Submission Information</HD>
        <P>A.<E T="03">Address to Request Application Package.</E>The application package for applying on paper for this funding opportunity is located at<E T="03">http://www.rurdev.usda.gov/BCP_SSDPG.html.</E>You may also contact your USDA Rural Development State Office for more information. Contact information for State Offices is located at<E T="03">http://www.rurdev.usda.gov/recd_map.html.</E>
        </P>
        <P>B.<E T="03">Content and Form of Submission.</E>Applications must be submitted on paper or electronically. Applications may not be submitted by electronic mail or facsimile. An application guide may be viewed at<E T="03">http://www.rurdev.usda.gov/BCP_SSDPG.html.</E>We recommend that you use the application template provided on the Web site. The template can be filled out electronically and printed out for submission with the required forms for paper submission or it can be filled out electronically and submitted as an attachment through<E T="03">http://www.grants.gov.</E>
        </P>
        <P>Please visit Grants.gov well in advance of the application deadline if you plan to apply electronically to make sure you have enough time to get the proper authentication and have sufficient computer resources to complete the application process.</P>
        <P>You must prepare and submit the following information to complete your application. Information submitted as part of the application will be protected to the extent permitted by law.</P>

        <P>1. Form SF-424, “Application for Federal Assistance,” must be completed, signed, and include a Dunn and Bradstreet Data Universal Numbering System (DUNS) number. You must also maintain registration in the Central Contractor Registration (CCR) database. See 2 CFR § 25.200(b). The DUNS number is a nine-digit identification number which uniquely identifies business entities. There is no charge. To obtain a DUNS number, access<E T="03">http://www.dnb.com/us/</E>or call 866-705-5711. Similarly, applicants may register for the CCR at<E T="03">http://www.ccr.gov.</E>Assistance with CCR registration is available by calling 1-866-606-8220. The CCR CAGE Code and expiration date may be handwritten on the SF-424. For more information, see the SSDPG web site at<E T="03">http://www.rurdev.usda.gov/BCP_SSDPG.html</E>or contact the USDA Rural Development State Office at<E T="03">http://www.rurdev.usda.gov/recd_map.html.</E>
        </P>
        <P>2. Form SF-424A, “Budget Information—Non-Construction Programs.” This form must be completed and submitted as part of the application package.</P>
        <P>3. Form SF-424B, “Assurances—Non-Construction Programs.” This form must be completed, signed, and submitted as part of the application package.</P>

        <P>4. Table of Contents. Your application must contain a detailed Table of Contents (TOC) immediately following the SF-424B. The TOC must include page numbers for each part of the<PRTPAGE P="24681"/>application. Page numbers should begin immediately following the TOC.</P>
        <P>5. Executive Summary. A summary of the proposal, not to exceed one page, must briefly describe the Project, tasks to be completed, and other relevant information that provides a general overview of the Project.</P>
        <P>6. Eligibility Discussion. A detailed discussion, not to exceed four pages, must describe how you meet the following requirements:</P>
        <P>(i) Applicant Eligibility. You must describe how you meet the definition of a Cooperative, Group of Cooperatives, or Cooperative Development Center. If applying as a Cooperative or a Group of Cooperatives, you must verify your incorporation in the State that you have applied by providing the State's Certificate of Good Standing, and your Articles of Incorporation and By-Laws. If applying as a Cooperative Development Center, you must provide evidence of your status as a nonprofit corporation or an accredited institution of higher education and a copy of your mission statement. You must apply as only one type of applicant.</P>
        <P>(ii) Use of Funds. You must provide a detailed discussion on how the proposed Project activities meet the definition of Technical Assistance.</P>
        <P>(iii) Project Area. You must provide specific information that details the location of the Project area and explain how the area meets the definition of “Rural Area.”</P>
        <P>(iv) Grant Period. You must provide a time frame for the proposed Project and discuss how the Project will be completed within that time frame.</P>
        <P>7. Budget/Work plan. You must describe, in detail not to exceed four pages, the purpose of the grant, what type of assistance will be provided, and the total amount of funds needed for the Project. The budget must also present a breakdown of estimated costs associated with each task/activity for each Project. The amount of grant funds requested will be reduced if the applicant does not have justification for all costs.</P>
        <P>8. Evaluation Criteria. Each of the evaluation criteria in this Notice must be addressed in narrative form, with a maximum of two pages for each individual evaluation criteria. Failure to address each evaluation criteria will result in the application being determined ineligible.</P>
        <P>C.<E T="03">Submission Dates and Times</E>
        </P>
        <P>
          <E T="03">Application Deadline Date:</E>July 24, 2012.</P>
        <P>
          <E T="03">Explanation of Deadlines:</E>Paper applications must be POSTMARKED and mailed, shipped, or sent overnight by the deadline date. Electronic applications must be received by<E T="03">http://www.grants.gov</E>by the deadline date. If your application does not meet the deadline, it will not be considered for funding. You will be notified if your application did not meet the submission deadline.</P>
        <P>D.<E T="03">National Environmental Policy Act.</E>We have determined that the activities proposed under the SSDPG program do not have a significant effect on the quality of the environment. You do NOT have to submit an Environmental Impact Statement. See 7 CFR part 1940, subpart G.</P>
        <P>E.<E T="03">Civil Rights Compliance Requirements.</E>All grants made under this Notice are subject to Title VI of the Civil Rights Act of 1964 as required by the USDA (7 CFR part 15, subpart A) and Section 504 of the Rehabilitation Act of 1973.</P>
        <P>F.<E T="03">Intergovernmental Review of Applications.</E>Executive Order (EO) 12372, Intergovernmental Review of Federal Programs, applies to this program. This EO requires that Federal agencies provide opportunities for consultation on proposed assistance with State and local governments. Many States have established a Single Point of Contact (SPOC) to facilitate this consultation. A list of States that maintain a SPOC may be obtained at<E T="03">http://www.whitehouse.gov/omb/grants_spoc</E>. If your State has a SPOC, you may submit your application directly for review. Any comments obtained through the SPOC must be provided to Rural Development for consideration as part of your application. If your State has not established a SPOC or you do not want to submit your application to the SPOC, Rural Development will submit your application to the SPOC or other appropriate agency or agencies.</P>

        <P>You are also encouraged to contact Cooperative Programs at 202-720-8460 or<E T="03">cpgrants@wdc.usda.gov</E>if you have questions about this process.</P>
        <P>G.<E T="03">Federal Funding and Transparency Act Requirements.</E>Please note that you must obtain a Dun and Bradstreet Data Universal Numbering System (DUNS) number and register in the Central Contractor Registration (CCR) prior to submitting a pre-application. See 2 CFR 25.200(b). In addition, you must maintain registration in the CCR database at all times during which you have an active Federal award or an application. All recipients of Federal financial assistance are required to report information about first-tier sub awards and executive compensation. See 2 CFR part 170. Finally, an applicant must have the necessary processes and systems in place to comply with the reporting requirements in 2 CFR 170.200(b), as long as it is not exempted from reporting. Exemptions are identified at 2 CFR 170.110(b).</P>
        <P>H.<E T="03">Funding Restrictions.</E>Grant funds must be used for Technical Assistance. No funds made available under this solicitation shall be used to:</P>
        <P>1. Plan, repair, rehabilitate, acquire, or construct a building or facility, including a processing facility;</P>
        <P>2. Purchase, rent, or install fixed equipment, including processing equipment;</P>
        <P>3. Purchase vehicles, including boats;</P>
        <P>4. Pay for the preparation of the grant application;</P>
        <P>5. Pay expenses not directly related to the funded Project;</P>
        <P>6. Fund political or lobbying activities;</P>
        <P>7. Fund any activities prohibited by 7 CFR parts 3015 or 3019;</P>
        <P>8. Fund architectural or engineering design work for a specific physical facility;</P>
        <P>9. Fund any direct expenses for the production of any commodity or product to which value will be added, including seed, rootstock, labor for harvesting the crop, and delivery of the commodity to a processing facility;</P>
        <P>10. Fund research and development;</P>
        <P>11. Purchase land;</P>
        <P>12. Duplicate current activities or activities paid for by other funded grant programs.</P>
        <P>13. Pay costs of the Project incurred prior to the date of grant approval;</P>
        <P>14. Pay for assistance to any private business enterprise that does not have at least 51 percent ownership by those who are either citizens of the United States or reside in the United States after being legally admitted for permanent residence;</P>
        <P>15. Pay any judgment or debt owed to the United States;</P>
        <P>16. Pay the Operating Costs of the Cooperative, Group of Cooperatives, or Cooperative Development Center;</P>
        <P>17. Pay expenses for applicant employee training; or</P>
        <P>18. Pay for any goods or services from a person who has a Conflict of Interest with the grantee.</P>
        <HD SOURCE="HD1">V. Application Scoring Criteria Review Information</HD>
        <P>A.<E T="03">Criteria.</E>All eligible and complete applications will be evaluated based on the following criteria. Failure to address any one of the following criteria by the application deadline will result in the application being determined ineligible and the application will not be considered for funding. The total points possible for the criteria are 60. Any application receiving less than 35 total points will not be funded.<PRTPAGE P="24682"/>
        </P>
        <P>1.<E T="03">Technical Assistance</E>
          <E T="03">(0-15 points).</E>We will evaluate your application to determine your ability to assess the needs of Small Socially-Disadvantaged Producers, plan and conduct appropriate and effective Technical Assistance, and identify the expected outcomes of that assistance.</P>
        <P>(i) 0 points are awarded if you do not address this criterion.</P>
        <P>(ii) 5 points are awarded if you show weakness in addressing this criterion.</P>
        <P>(iii) 10 points are awarded if you show you meet part but not all of the criterion.</P>
        <P>(iv) 15 points are awarded if you identify specific needs of the Socially-Disadvantaged Producers to be assisted; clearly explain a logical and detailed plan of assistance for addressing those needs; and discuss realistic outcomes of planned assistance.</P>
        <P>2.<E T="03">Experience (0-15 points).</E>Points are awarded based upon length of experience of identified staff or consultants in providing Technical Assistance, as defined in this Notice. You must describe the specific type of Technical Assistance experience for each identified staff member or consultant, as well as years of experience in providing that assistance. In addition, resumes for each individual staff member or consultant must be included as an attachment, listing their experience for the type of Technical Assistance proposed. The attachments will not count toward the maximum page total. We will compare the described experience to the work plan to determine relevance of the experience.</P>
        <P>(i) 0 points are awarded if the staff or consultants demonstrate no relevant experience in providing Technical Assistance.</P>
        <P>(ii) 5 points are awarded if at least one of the identified staff or consultants demonstrates more than two years of experience in providing relevant Technical Assistance.</P>
        <P>(iii) 10 points are awarded if at least one of the identified staff or consultants demonstrates 5 or more years of experience in providing relevant Technical Assistance.</P>
        <P>(iv) 15 points are awarded if all of the identified staff or consultants demonstrate 5 or more years of experience in providing relevant Technical Assistance.</P>
        <P>3.<E T="03">Commitment (0-15 points).</E>We will evaluate your commitment to providing Technical Assistance to Small, Socially-Disadvantaged Producers in Rural Areas. Points are awarded based upon the number of Socially-Disadvantaged Producers being assisted. You must list the number and location of Small, Socially-Disadvantaged Producers that will directly benefit from the assistance provided.</P>
        <P>(i) 0 points are awarded if you do not address this criterion.</P>
        <P>(ii) 5 points are awarded if the proposed Project will benefit 1-10 Small, Socially-Disadvantaged Producers.</P>
        <P>(iii) 10 points are awarded if the proposed Project will benefit 11-50 Small, Socially-Disadvantaged Producers.</P>
        <P>(iv) 15 points are awarded if the proposed Project will benefit more than 50 Small, Socially-Disadvantaged Producers.</P>
        <P>4.<E T="03">Work Plan/Budget (0-10 points).</E>The work plan will be reviewed for detailed actions and a timetable for implementing the proposal. Clear, logical, and realistic plans will result in a higher score. Budgets will be reviewed for completeness.</P>
        <P>(i) 0 points are awarded if you do not address this criterion.</P>
        <P>(ii) 5 points are awarded if you provide a work plan and budget with a cost breakdown but show weakness in addressing this criterion.</P>
        <P>(iii) 10 points are awarded if you provide a detailed work plan that is clear and logical and a budget with a breakdown of estimated costs associated with proposed tasks.</P>
        <P>4.<E T="03">Local support (0-5 points).</E>Applications are reviewed for local support of the Technical Assistance activities. Applicants that demonstrate strong support from potential beneficiaries and other developmental organizations will receive more points than those not showing such support.</P>
        <P>(i) 0 points are awarded if you do not address this criterion.</P>
        <P>(ii) 1 point is awarded if you provide 2-3 support letters that show support from potential beneficiaries and/or support from local organizations.</P>
        <P>(iii) 2 points are awarded if you provide 4 -5 support letters that show support from potential beneficiaries and/or support from local organizations.</P>
        <P>(iv) 3 points are awarded if you provide 6-7 support letters that show support from potential beneficiaries and/or support from local organizations.</P>
        <P>(v) 4 points are awarded if you provide 8-9 support letters that show support from potential beneficiaries and/or support from local organizations.</P>
        <P>(vi) 5 points are awarded if you provide 10 support letters that show support from potential beneficiaries and/or support from local organizations.</P>
        <P>You may submit a maximum of 10 letters of support. These letters should be included as an attachment to the application and will not count against the maximum page total. Additional letters from industry groups, commodity groups, local and State government, and similar organizations should be referenced, but not included in the application package. When referencing these letters, provide the name of the organization, date of the letter, the nature of the support, and the name and title of the person signing the letter.</P>
        <P>B.<E T="03">Review and Selection Process.</E>We will screen all proposals to determine whether the application is eligible and responsive to the requirements in this Notice. Eligible applications will be scored by the applicable State Office and then submitted to the National Office for review and ranking. The National Office will review the scores based upon the point allocation specified in this Notice. Applications are funded in scoring rank order and submitted to the Administrator in rank order with funding level recommendations. The Administrator will break scoring ties based on Agency priorities for geographic distribution of grants, and serving underserved groups and underserved areas.</P>
        <P>C.<E T="03">Anticipated Announcement and Award Dates.</E>The announcement of award selections is expected to occur on or about September 1, 2012, subject to funding.</P>
        <HD SOURCE="HD1">VI. Award Administration Information</HD>
        <P>A.<E T="03">Award Notices.</E>Successful applicants will receive a notification of tentative selection for funding from Rural Development. Applicants must comply with all applicable statutes, regulations, and this Notice before the grant award will receive final approval.</P>
        <P>Unsuccessful applicants will receive notification, including appeal rights, by mail.</P>
        <P>B.<E T="03">Administrative and National Policy Requirements.</E>7 CFR parts 3015 and 3019, and subparts A and F of 7 CFR part 4284 are applicable to grants made under this Notice. These regulations may be obtained at<E T="03">http://www.gpoaccess.gov/cfr/index.html.</E>
        </P>
        <P>The following additional requirements apply to grantees selected for this program:</P>
        <P>• Agency approved Grant Agreement.</P>
        <P>• Letter of Conditions.</P>
        <P>• Form RD 1940-1, “Request for Obligation of Funds.”</P>
        <P>• Form RD 1942-46, “Letter of Intent to Meet Conditions.”</P>
        <P>• Form AD-1047, “Certification Regarding Debarment, Suspension, and Other Responsibility Matters—Primary Covered Transactions.”</P>

        <P>• Form AD-1048, “Certification Regarding Debarment, Suspension,<PRTPAGE P="24683"/>Ineligibility and Voluntary Exclusion—Lower Tier Covered Transactions.”</P>
        <P>• Form AD-1049, “Certification Regarding a Drug-Free Workplace Requirement (Grants).”</P>
        <P>• Form RD 400-4, “Assurance Agreement.”</P>

        <P>Additional information on these requirements can be found at<E T="03">http://www.rurdev.usda.gov/BCP_SSDPG.html.</E>
        </P>
        <P>
          <E T="03">Fund Disbursement:</E>We will determine, based on 7 CFR Parts 3015, 3016 and 3019, as applicable, whether disbursement of a grant will be by advance or reimbursement. As needed, but not more frequently than once every 30 days, an original SF-270, “Request for Advance or Reimbursement,” may be submitted to Rural Development. Your request for advance shall not be made in excess of reasonable costs for the month covered.</P>
        <P>
          <E T="03">Reporting Requirements:</E>Grantees must provide Rural Development with an original or an electronic copy that includes all required signatures of the following reports. The reports should be submitted to the Agency contact listed on the Grant Agreement and Letter of Conditions. Failure to submit satisfactory reports on time may result in suspension or termination of the grant. Grantees will submit:</P>
        <P>1. Form SF-425. A “Federal Financial Report,” listing expenditures according to agreed upon budget categories, on a semi-annual basis. Reporting periods end each March 31 and September 30. Reports are due 30 days after the reporting period ends.</P>
        <P>2. Semi-annual performance reports comparing accomplishments to the objectives stated in the proposal, identifying all tasks completed to date and providing documentation supporting the reported results. If the original schedule provided in the work plan is not being met, the report should discuss the problems or delays that may affect completion of the Project. Objectives for the next reporting period should be listed. Compliance with any special condition on the use of award funds must be discussed. Reports are due as provided in paragraph (1) of this section. Supporting documentation must also be submitted for completed tasks. The supporting documentation for completed tasks includes, but is not limited to, feasibility studies, marketing plans, business plans, articles of incorporation, and bylaws as they relate to the assistance provided.</P>
        <P>3. Final Project performance reports comparing accomplishments to the objectives stated in the proposal, identifying all tasks completed, and providing documentation supporting the reported results. If the original schedule provided in the work plan was not met, the report must discuss the problems or delays that affected completion of the Project. Compliance with any special condition on the use of award funds must be discussed. Supporting documentation for completed tasks must also be submitted. The supporting documentation for completed tasks includes, but is not limited to, Feasibility Studies, marketing plans, business plans, articles of incorporation, and bylaws as they relate to the assistance provided. The final performance report is due within 90 days of the completion of the Project. The report must also include a summary at the end of the report with the number of Small Socially-Disadvantaged Producers assisted to help in documenting the annual performance goals of the SSDPG program for Congress.</P>
        <HD SOURCE="HD1">VII. Agency Contacts</HD>

        <P>For general questions about this announcement and for program Technical Assistance, please contact the appropriate State Office as indicated in the<E T="02">ADDRESSES</E>section of this Notice.</P>
        <HD SOURCE="HD1">VIII. Discrimination Statement</HD>
        <P>USDA prohibits discrimination in all its programs and activities on the basis of race, color, national origin, age, disability, and where applicable, sex, marital status, familial status, parental status, religion, sexual orientation, genetic information, political beliefs, reprisal, or because all or part of an individual's income is derived from any public assistance program. (Not all prohibited bases apply to all programs.) Persons with disabilities who require alternative means for communication of program information (Braille, large print, audiotape, etc.) should contact USDA's TARGET Center at (202) 720-2600 (voice and TDD).</P>
        <P>To file a complaint of discrimination, write to USDA, Director, Office of Adjudication and Compliance, 1400 Independence Avenue SW., Washington, DC 20250-9410 or call (800) 795-3272 (voice) or (202) 720-6382 (TDD). USDA is an equal opportunity provider and employer.</P>
        <SIG>
          <DATED>Dated: April 13, 2012.</DATED>
          <NAME>Judith A. Canales,</NAME>
          <TITLE>Administrator, Rural Business-Cooperative Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9997 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-XY-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">COMMISSION ON CIVIL RIGHTS</AGENCY>
        <SUBJECT>Agenda and Notice of Public Meeting of the Florida Advisory Committee</SUBJECT>
        <P>Notice is hereby given, pursuant to the provisions of the rules and regulations of the U.S. Commission on Civil Rights (Commission) and the Federal Advisory Committee Act (FACA) that a meeting of the Florida Advisory Committee (Committee) will convene on Thursday, May 24, 2012. The meeting will convene at 2 p.m. and adjourn at approximately 3 p.m. The meeting will be held at Brevard Community College, 1519 Clearlake Road, Building 2, Cocoa, Florida, 32922. The purpose of the meeting is for the Committee to discuss its ex-felon voting rights project.</P>

        <P>Members of the public are entitled to submit written comments; the comments must be received in the regional office by June 25, 2012. Written comments may be mailed to the Southern Regional Office, U.S. Commission on Civil Rights, 61 Forsyth St., SW., Suite 16T126, Atlanta, GA, 30303. They may also be faxed to the Commission at (404) 562-7005, or emailed to the Commission at<E T="03">erodriguez@usccr.gov.</E>Persons who desire additional information may contact the Southern Regional Office at (404) 562-7000.</P>
        <P>Hearing-impaired persons who will attend the meeting and require the services of a sign language interpreter should contact the Southern Regional Office at least ten (10) working days before the scheduled date of the meeting.</P>

        <P>Records generated from this meeting may be inspected and reproduced at the Southern Regional Office, as they become available, both before and after the meeting. Persons interested in the work of this Committee are directed to the Commission's Web site,<E T="03">http://www.usccr.gov</E>, or may contact the Southern Regional Office at the above email or street address.</P>
        <P>The meeting will be conducted pursuant to the rules and regulations of the Commission and FACA.</P>
        <SIG>
          <DATED>Dated in Washington, DC, April 20, 2012.</DATED>
          <NAME>Peter Minarik,</NAME>
          <TITLE>Acting Chief, Regional Programs Coordination Unit.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-9907 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6335-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="24684"/>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>U.S. Census Bureau</SUBAGY>
        <SUBJECT>Proposed Information Collection; Comment Request; 2013-2015 American Community Survey Methods Panel Testing</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. Census Bureau.</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, Public Law 104-13 (44 U.S.C. 3506(c)(2)(A)).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>To ensure consideration, written comments must be submitted on or before June 25, 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(s) and instructions should be directed to Cheryl Chambers, U.S. Census Bureau, American Community Survey Office, Washington, DC 20233, by FAX to (301) 763-8070 or email at<E T="03">acso.communications@census.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Abstract</HD>
        <P>The American Community Survey (ACS) collects detailed socioeconomic data from about 3.5 million households in the United States and 36,000 in Puerto Rico each year. The ACS also collects detailed socioeconomic data from about 195,000 residents living in Group Quarter (GQ) facilities. Resulting tabulations from that data collection are provided on a yearly basis. The ACS allows the Census Bureau to provide timely and relevant housing and socio-economic statistics for even low levels of geography.</P>
        <P>An ongoing data collection effort with an annual sample of this magnitude requires that the ACS continue research, testing and evaluations aimed at improving data quality, achieving survey cost efficiencies, and improving ACS questionnaire content and related data collection materials. The ACS Methods Panel is a research program that is designed to address and respond to survey issues and needs. During the 2013-2015 period, the Methods Panel may include testing methods for increasing survey efficiencies, reducing survey cost, lessening respondent burden, and improving response rates. Testing may also include methods that might increase data quality. At this time, plans are in place to propose several tests: A 2013 Questionnaire Design Test, a 2015 ACS Content Test, and a series of Internet tests. Since the ACS Methods Panel is designed to address emerging issues, we may conduct additional testing as needed. Testing would focus on methods for reducing data collection costs, improving data quality or testing new questions that have an urgent need to be included on the ACS.</P>
        <P>During the 2010 Content Test, the Census Bureau determined that the ACS paper questionnaire did not contain enough space to accommodate certain configurations of proposed content changes. Thus, we need to test an alternative questionnaire design to accommodate additional content on the ACS mail questionnaire. In the 2013 ACS Questionnaire Design Test, we will study the impact of a longer (36-page) questionnaire against our current 28-page form. We will also study whether changing the size of the form to a standard size (8.5″x11″) booklet has an impact on response, compared to both the 28-page (current ACS form) and 36-page forms. The results of this testing will help the Census Bureau to decide which questionnaire format change performs best on response and data quality.</P>
        <P>This test will also include several changes to evaluate making the questionnaire more compatible with optical character recognition software, including altering the response box formats for numeric write-in fields to allow them to be captured automatically rather than keyed. It will help provide insight on how effective the new response boxes are at reducing keying, and thus the potential cost savings. Lastly, this test will include a quick look at variations in the relationship and marital status questions per the Office of Management and Budget (OMB) initiative to ensure these questions are inclusive of all relationship types and partnerships.</P>
        <P>Second, in response to Federal agencies' requests for new and revised ACS questions, the Census Bureau plans to conduct the 2015 ACS Content Test. Changes to the current ACS content and the addition of new content will be identified through the OMB Interagency Committee for the ACS in 2013. The objective of the 2015 ACS Content Test, for both new and existing questions, is to determine the impact of changing question wording, response categories, and redefinition of underlying constructs on the quality of the data collected. The Census Bureau proposes to evaluate changes to the questions by comparing the revised questions to the current ACS questions, or for new questions, to compare the performance of question versions to each other as well as to other well-known sources of such information.</P>
        <P>The Census Bureau conducted two Internet tests on the ACS in 2011, both of which studied the impact of different notifications of an Internet option in the survey invitations. Based on these tests, the ACS plans to begin collecting data using the Internet in January 2013. One problem detected in the 2011 tests was the impact of Internet break-offs on item nonresponse for questions in the later part of the survey. The Internet tests in 2013-2015 will look at potential ways to restructure messaging and change the Internet design to help reduce break-offs, lower item nonresponse and encourage response in a timely manner. We will also reexamine the possibility of using the Internet to collect data in Puerto Rico.</P>
        <HD SOURCE="HD1">II. Method of Collection</HD>
        <P>
          <E T="03">Questionnaire Design Test</E>—Data collection for this test will follow the same protocol proposed for ACS production starting in 2013. That is, the first mailing to sampled cases will ask them to use the Internet to respond to the survey. If they have not responded within about two and a half weeks, they will receive a paper questionnaire. By using the standard ACS protocol for this test, we can see whether the paper form design has any impact on overall self-response, and also on response by Internet or mail. We will not conduct Computer-Assisted Telephone Interviews (CATI) or Computer-Assisted Personal Interviews (CAPI) nonresponse follow-up on test cases.</P>
        <P>
          <E T="03">2015 Content Test</E>—The ACS Content Test data collection protocol will be based on the protocol used in the production ACS. That is, we will collect data across four modes (Internet, mail, CATI and CAPI). During CATI and CAPI interviews in the 2015 Content Test, we will use Computer Audio Recorded Interviewing (CARI) technology to record portions of the interview related to the questions being tested for use in behavior coding. There will also be a Content Follow-up reinterview as part of the content test where we will attempt a follow-up CATI reinterview with all households that responded in the field test and for whom we have a<PRTPAGE P="24685"/>telephone number. This reinterview will focus on the particular questions that we are evaluating in the field test, and will not include every question asked in the original interview.</P>
        <P>
          <E T="03">Internet Tests</E>—We will use the same modes we offer in ACS production in the first month of data collection for the Internet tests; that is, we will send a mailing asking sampled units to respond online, with a nonresponse follow-up mailing of a paper questionnaire about two and a half weeks later. There are no plans to conduct CATI or CAPI nonresponse follow-up on test cases.</P>
        <HD SOURCE="HD1">III. Data</HD>
        <P>
          <E T="03">OMB Control Number:</E>0607-0936.</P>
        <P>
          <E T="03">Form Number:</E>ACS-1, ACS-1(PR)SP, ACS CATI(HU), ACS CAPI(HU) and ACS RI(HU).</P>
        <P>
          <E T="03">Type of Review:</E>Regular submission.</P>
        <P>
          <E T="03">Affected Public:</E>Individuals, households, and GQ facilities.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>We plan to contact the following number of respondents: Questionnaire Design Test: 40,000 sampled addresses; 2013-2015 Internet Tests, 200,000 sampled addresses in United States, 4,000 in Puerto Rico; 2015 Content Test: 70,000 sampled addresses during the field test and 40,000 responding addresses during the content follow-up conducted by telephone. Other potential testing includes a second Content Reinterview survey (as a follow-up to the 2012 Content Reinterview Survey) to assess data quality: 90,000 sampled households from ACS production; follow-up testing as needed from the Questionnaire Design Test: 20,000 sampled addresses; and potential testing of methodological changes to the administration of the ACS in Group Quarter facilities (Two tests of 75 facilities each with 15 residents selected in each facility (approximately 1,125 residents in each test)).</P>
        <P>
          <E T="03">Estimated Time per Response:</E>Estimates are: Questionnaire Design Test: 40 minutes; Internet Test, 40 minutes; Content Test field test, 40 minutes, Content Test follow-up, 15 minutes; Content Reinterview Study, 20 minutes; other potential test for questionnaire design and Group Quarters testing, 40 minutes.</P>
        <P>
          <E T="03">Estimated Total Annual Burden Hours:</E>The estimate is an annual average of 87,771 hours.</P>
        <P>
          <E T="03">Estimated Total Annual Cost:</E>Except for their time, there is no cost to respondents.</P>
        <P>
          <E T="03">Respondent Obligation:</E>Mandatory.</P>
        <P>
          <E T="03">Legal Authority:</E>Title 13 U.S.C. Section 182.</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 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: April 20, 2012.</DATED>
          <NAME>Glenna Mickelson,</NAME>
          <TITLE>Management Analyst, Office of the Chief Information Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9939 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-07-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>International Trade Administration</SUBAGY>
        <SUBJECT>Proposed Information Collection; Comment Request; Client Focus Groups and Qualitative Interviews</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>International Trade Administration (ITA).</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 June 25, 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 Suzan Winters, (202) 482-6042,<E T="03">suzan.winters@trade.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Abstract</HD>
        <P>The International Trade Administration's U.S. Commercial Service (CS) is mandated by Congress to help U.S. businesses, particularly small and medium-sized companies, export their products and services to global markets.</P>
        <P>As part of its mission, the CS uses “Quality Assurance Surveys” to collect feedback from the U.S. business clients it serves. These surveys ask the client to evaluate the U.S. Commercial Service on its customer service provision. Results from the surveys are used to make improvements to the agency's business processes in order to provide better and more effective export assistance to U.S. companies. In addition to collecting client feedback through Quality Assurance Surveys, the CS uses client focus groups as a mechanism to obtain further client feedback and substantiate customer service trends seen in the Surveys. Qualitative client focus group data will enrich the quantitative survey data by providing insights and a descriptive context to explain the trends that emerge in the quantitative data.</P>
        <P>The CS uses the focus group questions to address quality improvement issues. The focus group discussion guide will enable CS to obtain a better understanding of actions that can be taken to improve the export-related services that CS provide to U.S. firms. In providing these services, the CS promotes the goods and services of small and medium-sized U.S. businesses in foreign markets.</P>
        <HD SOURCE="HD1">II. Method of Collection</HD>
        <P>U.S. firms will be recruited via telephone to participate in focus group discussions. Firms may be current Commercial Service clients or potential clients. Data will be collected through either face-to-face focus group discussion forums (6-8 participants per focus group) and conference calls, or through one-on-one qualitative interviews either in person or via phone. A moderator will facilitate the discussions and notes will be transcribed via computer. All comments from participants will be anonymous.</P>
        <HD SOURCE="HD1">III. Data</HD>
        <P>
          <E T="03">OMB Control Number:</E>0625-0254.</P>
        <P>
          <E T="03">Form Number(s):</E>None.</P>
        <P>
          <E T="03">Type of Review:</E>Regular submission (extension of a currently approved information collection).</P>
        <P>
          <E T="03">Affected Public:</E>Business or other for-profit organizations.<PRTPAGE P="24686"/>
        </P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>96.</P>
        <P>
          <E T="03">Estimated Time per Response:</E>Surveys, 30-45 minutes; Focus Groups, 1 hour and 15 minutes.</P>
        <P>
          <E T="03">Estimated Total Annual Burden Hours:</E>74.</P>
        <P>
          <E T="03">Estimated Total Annual Cost to Public:</E>$0.</P>
        <HD SOURCE="HD1">IV. Request for Comments</HD>
        <P>
          <E T="03">Comments are invited on:</E>(a) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including 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: April 20, 2012.</DATED>
          <NAME>Gwellnar Banks,</NAME>
          <TITLE>Management Analyst, Office of the Chief Information Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9967 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-FP-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <SUBJECT>Western Pacific Fishery Management Council; 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 public meetings.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This notice advises the public that the Western Pacific Fishery Management Council (Council) will convene a meeting of the Hawaii Regional Ecosystem Advisory Committee (REAC) in Honolulu, HI.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>

          <P>The Hawaii REAC meeting will be held Friday, May 11, 2012. For the specific date, times, and agenda for the meeting see<E T="02">SUPPLEMENTARY INFORMATION</E>.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The meeting of the Hawaii REAC will be held at the Council Office, 1164 Bishop St. Suite 1400, Honolulu, HI 96814.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Kitty M. Simonds, Executive Director; telephone: (808) 522-8220.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Schedule and Agenda for the Hawaii Regional Ecosystem Advisory Committee Meeting:</P>
        
        <FP SOURCE="FP-2">
          <E T="03">8:30 a.m.-5 p.m. Friday, May 11, 2012</E>
        </FP>
        <FP SOURCE="FP1-2">1. Welcome and Introduction of Members</FP>
        <FP SOURCE="FP1-2">2. Approval of Draft Agenda</FP>
        <FP SOURCE="FP1-2">3. REAC Overview and 2011 Meeting Recommendations</FP>
        <FP SOURCE="FP1-2">4. Agency Protected Species Overview and Updates</FP>
        <FP SOURCE="FP1-2">a. Federal Endangered Species Act (ESA), Marine Mammal Protection Act (MMPA), Migratory Bird Treaty Act (MBTA) Updates</FP>
        <FP SOURCE="FP1-2">b. State of Hawaii Protected Species Rules, Regulations and Updates</FP>
        <FP SOURCE="FP1-2">5. Protected Species in Our Ecosystem</FP>
        <FP SOURCE="FP1-2">a. Humpback Whales</FP>
        <FP SOURCE="FP1-2">i. Status of Humpback Whale Hawaii Breeding Population</FP>
        <FP SOURCE="FP1-2">ii. Ecosystem Impacts of Humpback Whales in the North Pacific Foraging Grounds</FP>
        <FP SOURCE="FP1-2">b. Odontocetes (Toothed Whales)</FP>
        <FP SOURCE="FP1-2">i. Marine Mammal Protection Act: What You Should Know</FP>
        <FP SOURCE="FP1-2">ii. List of Fisheries and Hawaii Troll and Charter Fisheries</FP>
        <FP SOURCE="FP1-2">iii. Fishermen's Perspective on Marine Mammal Interactions</FP>
        <FP SOURCE="FP1-2">iv. Discussion on Monitoring and Addressing Small Vessel Fishery Impacts on Odontocetes</FP>
        <FP SOURCE="FP1-2">c. ESA Petition and Status of Review for Coral</FP>
        <FP SOURCE="FP1-2">i. Coral Status Review</FP>
        <FP SOURCE="FP1-2">ii. REAC Review and Discussion of the Coral Management Report</FP>
        <FP SOURCE="FP1-2">d. ESA Petition for Hawaiian Green Turtles</FP>
        <FP SOURCE="FP1-2">i. Green Turtle Petition &amp; Review Process</FP>
        <FP SOURCE="FP1-2">ii. State of Hawaii Green Turtle Management Plan</FP>
        <FP SOURCE="FP1-2">iii. Discussion on Future Green Turtle Management in Hawaii</FP>
        <FP SOURCE="FP1-2">6. Public Comments</FP>
        <FP SOURCE="FP1-2">7. Discussion and Recommendations</FP>
        
        <P>The order in which agenda items are addressed may change. Public comment periods will be provided throughout each agenda. The REAC will meet as late as necessary to complete scheduled business.</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 Kitty M. Simonds, (808) 522-8220 (voice) or (808) 522-8226 (fax), at least 5 days prior to the meeting date.</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>16 U.S.C. 1801<E T="03">et seq.</E>
          </P>
        </AUTH>
        <SIG>
          <DATED>Dated: April 20, 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-9950 Filed 4-24-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-XA714</RIN>
        <SUBJECT>Endangered Species; File No. 15634</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>Issuance of permit.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>Notice is hereby given that NMFS Southwest Fisheries Science Center (SWFSC), 3333 N. Torrey Pines Ct., La Jolla, CA 92037, [Responsible Party: Lisa Ballance, Ph.D.] has been issued a permit to take leatherback sea turtles (<E T="03">Dermochelys coriacea</E>) for purposes of scientific research.</P>
        </SUM>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The permit and related documents are available for review 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;</P>
          <P>Northwest Region, NMFS, 7600 Sand Point Way NE., BIN C15700, Bldg. 1, Seattle, WA 98115-0700; phone (206) 526-6150; fax (206) 526-6426; 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>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Amy Hapeman or Colette Cairns, (301) 427-8401.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>On September 21, 2011, notice was published in the<E T="04">Federal Register</E>(76 FR 58471) that a request for a scientific research permit to take leatherback sea turtles had been submitted by the above-named organization. The requested permit has been issued under the authority of the Endangered Species Act of 1973, as amended (ESA; 16 U.S.C. 1531<E T="03">et seq.</E>) and the regulations governing the taking, importing, and exporting of endangered and threatened species (50 CFR parts 222-226).<PRTPAGE P="24687"/>
        </P>
        <P>A five-year permit has been issued to the SWFSC to continue long-term monitoring of the status of leatherback sea turtles off the coasts of California, Oregon, and Washington. The purpose of the work is to identify critical forage habitats, genetic stock structure, migratory corridors, and potential fishery impacts for leatherbacks. Sea turtles would be located by aerial surveys and approached by vessel for remote tissue sampling and transmitter attachment. A subset of animals would be captured by breakaway hoopnet for additional observation, sampling, marking and/or tagging procedures before release.</P>
        <P>Issuance of this permit, as required by the ESA, was based on a finding that such permit (1) Was applied for in good faith, (2) will not operate to the disadvantage of such endangered or threatened species, and (3) is consistent with the purposes and policies set forth in section 2 of the ESA.</P>
        <SIG>
          <DATED>Dated: April 20, 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-9962 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">BUREAU OF CONSUMER FINANCIAL PROTECTION</AGENCY>
        <DEPDOC>[Docket No. CFPB-2012-0007]</DEPDOC>
        <SUBJECT>Impact of Overdraft Programs on Consumers</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Bureau of Consumer Financial Protection.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice and request for information; extension of comment period.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>On February 28, 2012, the Bureau of Consumer Financial Protection (the Bureau) published in the<E T="04">Federal Register</E>a notice and request for information regarding the impacts of overdraft programs on consumers (the Overdraft Notice). The Overdraft Notice allowed a 60-day comment period, closing on April 30, 2012. To allow parties more time to consider and craft their responses, the Bureau has determined that an extension of the comment period until June 29, 2012, is appropriate.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The comment period for the Overdraft Notice published February 28, 2012, at 77 FR 12031, is extended. Responses must now be received on or before June 29, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments by any of the following methods:</P>
          <P>•<E T="03">http://www.regulations.gov</E>. Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Email:</E>
            <E T="03">cfpb_overdraft_comments@cfpb.gov</E>.</P>
          <P>•<E T="03">Mail/Hand Delivery/Courier:</E>Monica Jackson, Office of the Executive Secretary, Bureau of Consumer Financial Protection, 1700 G Street NW., Washington, DC 20552.</P>
          <P>
            <E T="03">Instructions:</E>Please submit your comments or responses using only one method. The Bureau encourages the early submission of comments. All submissions must include the document title and docket number. Please note the number of any question to which you are responding at the top of each response (respondents need not answer each question). In general, all comments received will be posted without change to<E T="03">http://www.regulations.gov</E>. In addition, comments will be available for public inspection and copying at 1700 G Street, NW., Washington, DC, 20552, on official business days between the hours of 10 a.m. and 5 p.m. Eastern Time. You can make an appointment to inspect the documents by telephoning 202-435-7275. All comments, including attachments and other supporting materials, will become part of the public record and subject to public disclosure. Sensitive personal information such as account numbers or Social Security Numbers should not be included. Comments will not be edited to remove any identifying or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>For general inquiries, submission process questions, or any additional information, please contact Monica Jackson, Office of the Executive Secretary, 202-435-7275.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>On February 28, 2012, the Bureau published the Overdraft Notice in the<E T="04">Federal Register.</E>
          <SU>1</SU>
          <FTREF/>The Overdraft Notice requested information from the public regarding overdraft programs and their costs, benefits, and risks to consumers. The Overdraft Notice posed several questions to understand:</P>
        <FTNT>
          <P>
            <SU>1</SU>77 FR 12031.</P>
        </FTNT>
        <P>• Lower cost alternatives to overdraft protection programs;</P>
        <P>• Consumer alerts and information provided regarding balances and overdraft triggers;</P>
        <P>• Impacts of changes to Regulation DD, Regulation E, and Overdraft opt-in rates;</P>
        <P>• Impacts of changes in financial institutions' operating policies;</P>
        <P>• The economics of overdraft programs; and</P>
        <P>• Long-term impacts on Consumers.</P>
        <P>The comment period for the Overdraft Notice was to close on April 30, 2012.</P>
        <P>The Bureau received written requests from two industry trade groups for an extension of the Overdraft Notice comment period.<SU>2</SU>
          <FTREF/>The request letters indicated more time would enable a higher quality response and yield greater insight to the Bureau. The letters also pointed out that the Bureau's study of overdrafts is not governed by a statutory deadline.</P>
        <FTNT>
          <P>
            <SU>2</SU>Letter to Monica Jackson (Mar. 30, 2012), signed by Richard M. Whiting, Executive Director &amp; General Counsel of the Financial Services Roundtable; letter to David Silberman (Apr. 10, 2012), signed by Richard R. Riese, Senior Vice President, Center for Regulatory Compliance, American Bankers Association.</P>
        </FTNT>
        <P>The Bureau believes that it is important to allow interested persons more time to consider the issues raised in the Overdraft Notice and prepare their responses. Accordingly, the Bureau is extending the period allotted for comments received pursuant to the Overdraft Notice. The comment period will now close on June 29, 2012.</P>
        <SIG>
          <DATED>Dated: April 18, 2012.</DATED>
          <NAME>Richard Cordray,</NAME>
          <TITLE>Director, Bureau of Consumer Financial Protection.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9851 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4810-AM-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">COORDINATING COUNCIL ON JUVENILE JUSTICE AND DELINQUENCY PREVENTION</AGENCY>
        <DEPDOC>[OJP (OJJDP) Docket No. 1587]</DEPDOC>
        <SUBJECT>Meeting of the Coordinating Council on Juvenile Justice and Delinquency Prevention</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coordinating Council on Juvenile Justice and Delinquency Prevention.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coordinating Council on Juvenile Justice and Delinquency Prevention (Council) announces its next meeting.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Friday, May 11, 2012 from 10 a.m. to 12:15 p.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The meeting will take place in the third floor main conference room at the U.S. Department of Justice, Office of Justice Programs, 810 7th St. NW., Washington, DC 20531.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Visit the Web site for the Coordinating Council at<E T="03">www.juvenilecouncil.gov</E>or contact Robin Delany-Shabazz, Designated Federal Official, by telephone at 202-307-9963<E T="04">[Note:</E>this is not a toll-free telephone number], or<PRTPAGE P="24688"/>by email at<E T="03">Robin.Delany-Shabazz@usdoj.gov</E>or<E T="03">Geroma.Void@usdoj.gov.</E>The meeting is open to the public.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>The Coordinating Council on Juvenile Justice and Delinquency Prevention, established pursuant to Section 3(2)A of the Federal Advisory Committee Act (5 U.S.C. App. 2) will meet to carry out its advisory functions under Section 206 of the Juvenile Justice and Delinquency Prevention Act of 2002, 42 U.S.C. 5601, et seq. Documents such as meeting announcements, agendas, minutes, and reports will be available on the Council's Web page,<E T="03">www.juvenilecouncil.gov,</E>where you may also obtain information on the meeting.</P>
        <P>Although designated agency representatives may attend, the Council membership is composed of the Attorney General (Chair), the Administrator of the Office of Juvenile Justice and Delinquency Prevention (Vice Chair), the Secretary of Health and Human Services (HHS), the Secretary of Labor, the Secretary of Education, the Secretary of Housing and Urban Development, the Director of the Office of National Drug Control Policy, the Chief Executive Officer of the Corporation for National and Community Service, and the Assistant Secretary of Homeland Security for U.S. Immigration and Customs Enforcement. The nine additional members are appointed by the Speaker of the House of Representatives, the Senate Majority Leader, and the President of the United States. Other federal agencies take part in Council activities including the Departments of Agriculture, Defense, the Interior, and the Substance and Mental Health Services Administration of HHS.</P>
        <HD SOURCE="HD1">Meeting Agenda</HD>
        <P>The preliminary agenda for this meeting includes: (a) Presentations on and discussions of family and youth engagement work; (b) an update on information sharing activities; and (c) other agency announcements.</P>
        <HD SOURCE="HD1">Registration</HD>

        <P>For security purposes, members of the public who wish to attend the meeting must pre-register online at<E T="03">www.juvenilecouncil.gov</E>no later than Monday, May 7, 2012. Should problems arise with web registration, call Daryel Dunston at 240-221-4343 or send a request to register to Mr. Dunston. Include name, title, organization or other affiliation, full address and phone, fax and email information and send to his attention either by fax to 301-945-4295, or by email to<E T="03">ddunston@edjassociates.com.</E>[<E T="04">Note:</E>these are not toll-free telephone numbers.] Additional identification documents may be required. Space is limited.</P>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>Photo identification will be required for admission to the meeting.</P>
        </NOTE>
        <P>
          <E T="03">Written Comments:</E>Interested parties may submit written comments and questions by Monday, May 7, 2012, to Robin Delany-Shabazz, Designated Federal Official for the Coordinating Council on Juvenile Justice and Delinquency Prevention, at<E T="03">Robin.Delany-Shabazz@usdoj.gov.</E>The Coordinating Council on Juvenile Justice and Delinquency Prevention expects that the public statements presented will not repeat previously submitted statements. Written questions from the public may also be invited at the meeting.</P>
        <SIG>
          <NAME>Melodee Hanes,</NAME>
          <TITLE>Acting Administrator.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9846 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4410-18-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Department of the Navy</SUBAGY>
        <SUBJECT>Meeting of the Secretary of the Navy Advisory Panel</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of the Navy, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of Closed Meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The SECNAV Advisory Panel will meet from 8:30 a.m. to 5 p.m. on May 23, 2012, for a series of classified discussions on the Asia-Pacific region to include the international strategic environment, U.S. operational capabilities and shortfalls, foreign capabilities and intentions and the maritime strategic outlook in contested areas. These sessions will include discussions of classified operations and human intelligence activities. These sessions will also include a proprietary industry briefing on new or evolving energy technologies. For these reasons, these meetings will be closed to the public.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The meeting will be held on May 23, 2012, from 8:30 a.m. to 4 p.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The meeting will be held in the Pentagon N89 Conference Room at the Pentagon.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>CAPT Henry J. Hendrix, SECNAV Advisory Panel, Office of the Deputy Under Secretary of the Navy (Plans, Policy, Oversight &amp; Integration), 1000 Navy Pentagon, Washington, DC 20350-1000, 703-695-3032.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Pursuant to the provisions of the Federal Advisory Committee Act (5 U.S.C. App. 2), these matters constitute classified information that is specifically authorized by Executive Order to be kept secret in the interest of national defense and are, in fact, properly classified pursuant to such Executive Order. The discussion of such information cannot be adequately segregated from other topics, which precludes opening these meetings to the public. Accordingly, the Secretary of the Navy has determined in writing that the public interest requires that all sessions of this meeting be closed to the public because they will be concerned with matters listed in section 552b(c)(1) of title 5, United States Code.</P>
        <SIG>
          <DATED>Dated: April 18, 2012.</DATED>
          <NAME>J.M. Beal,</NAME>
          <TITLE>Lieutenant Commander, Judge Advocate General's Corps, U.S. Navy, Federal Register Liaison Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9930 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3810-FF-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DELAWARE RIVER BASIN COMMISSION</AGENCY>
        <SUBJECT>Notice of Commission Meeting and Public Hearing</SUBJECT>
        <P>Notice is hereby given that the Delaware River Basin Commission will hold an informal conference followed by a public hearing on Thursday, May 10, 2012. The hearing will be part of the Commission's regularly scheduled business meeting. The conference session and business meeting both are open to the public and will be held at the Commission's office building, located at 25 State Police Drive, West Trenton, New Jersey.</P>
        <P>The morning conference session will begin at 11 a.m. and will include a presentation on PCB reductions in the Delaware Estuary and resolutions recognizing the contributions of Gary Paulachok, former Deputy Delaware River Master, U.S. Geological Survey, and William Douglass, former Executive Director of the Upper Delaware Council, both of whom recently retired.</P>
        <P>
          <E T="03">Items for Public Hearing.</E>The subjects of the public hearing to be held during the 1:30 p.m. business meeting on May 10, 2012 include draft dockets for which the names and brief descriptions will be posted on the Commission's Web site at<E T="03">www.drbc.net</E>at least 10 days prior to the meeting date and complete draft dockets will be posted on the Web site<PRTPAGE P="24689"/>ten days prior to the meeting date. Additional public records relating to the dockets may be examined at the Commission's offices. Please contact William Muszynski at 609-883-9500, extension 221, with any docket-related questions.</P>
        <P>In addition to the hearings on draft dockets, a public hearing also will be held during the 1:30 p.m. business meeting on proposed resolutions to: (a) Adopt the Commission's annual budget for the fiscal year ending June 30, 2013; and (b) approve election of the Commission Chair, Vice Chair and Second Vice Chair for fiscal year 2013.</P>
        <P>
          <E T="03">Other Agenda Items.</E>Other agenda items include resolutions (a) authorizing participation in the New Jersey State Health Benefits Program for SHBP Dental Plan Coverage; (b) authorizing the Executive Director to terminate a purchase order agreement with one firm and retain another to complete the design of the Ruth Patrick River Garden; and (c) authorizing the Executive Director to execute an agreement for the preparation of an actuarial evaluation for the Commission's post-retirement benefits in accordance with Government Accounting Standards Board Statement No. 45 (“GASB 45”). The standard business meeting items also will be addressed, including: adoption of the Minutes of the Commission's March 7, 2012 business meeting, announcements of upcoming meetings and events, a report on hydrologic conditions, reports by the Executive Director and the Commission's General Counsel, and a public dialogue session.</P>
        <P>
          <E T="03">Opportunities to Comment.</E>Individuals who wish to comment for the record on a hearing item or to address the Commissioners informally during the public dialogue portion of the meeting are asked to sign up in advance by contacting Ms. Paula Schmitt of the Commission staff, at<E T="03">paula.schmitt@drbc.state.nj.us</E>or by phoning Ms. Schmitt at 609-883-9500 ext. 224. Written comment on items scheduled for hearing may be submitted in advance of the meeting date to: Commission Secretary, P.O. Box 7360, 25 State Police Drive, West Trenton, NJ 08628; by fax to Commission Secretary, DRBC at 609-883-9522 or by email to<E T="03">paula.schmitt@drbc.state.nj.us.</E>Written comment on dockets should also be furnished directly to the Project Review Section at the above address or fax number or by email to<E T="03">william.muszynski@drbc.state.nj.us.</E>
        </P>
        <P>Individuals in need of an accommodation as provided for in the Americans with Disabilities Act who wish to attend the informational meeting, conference session or hearings should contact the Commission Secretary directly at 609-883-9500 ext. 203 or through the Telecommunications Relay Services (TRS) at 711, to discuss how we can accommodate your needs.</P>
        <P>
          <E T="03">Agenda Updates.</E>Note that conference items are subject to change and items scheduled for hearing are occasionally postponed to allow more time for the Commission to consider them. Please check the Commission's Web site,<E T="03">www.drbc.net</E>, closer to the meeting date for changes that may be made after the deadline for filing this notice.</P>
        <SIG>
          <DATED>Dated: April 19, 2012.</DATED>
          <NAME>Pamela M. Bush,</NAME>
          <TITLE>Esquire, Commission Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-9947 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6360-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
        <SUBJECT>Notice of Proposed Information Collection Requests; Office of Postsecondary Education; Graduate Assistance in Areas of National Need (GAANN) Performance Report</SUBJECT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Graduate Assistance in Areas of National Need (GAANN) grantees must submit a performance report annually. The reports are used to evaluate grantee performance. Further, the data from the reports will be aggregated to evaluate the accomplishments and impact of the GAANN Program as a whole. Results will be reported to the Secretary in order to respond to Government Performance and Results Act (GPRA) requirements.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Interested persons are invited to submit comments on or before June 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Written comments regarding burden and/or the collection activity requirements should be electronically mailed to<E T="03">ICDocketMgr@ed.gov</E>or mailed to U.S. Department of Education, 400 Maryland Avenue SW., LBJ, Washington, DC 20202-4537. Copies of the proposed information collection request may be accessed from<E T="03">http://edicsweb.ed.gov,</E>by selecting the “Browse Pending Collections” link and by clicking on link number 04846. When you access the information collection, click on “Download Attachments” to view. Written requests for information should be addressed to U.S. Department of Education, 400 Maryland Avenue SW., LBJ, Washington, DC 20202-4537. Requests may also be electronically mailed to<E T="03">ICDocketMgr@ed.gov</E>or faxed to 202-401-0920. Please specify the complete title of the information collection and OMB Control Number when making your request.</P>
          <P>Individuals who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339.</P>
        </ADD>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Section 3506 of the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35) requires that Federal agencies provide interested parties an early opportunity to comment on information collection requests. The Director, Information Collection Clearance Division, Privacy, Information and Records Management Services, Office of Management, publishes this notice containing proposed information collection requests at the beginning of the Departmental review of the information collection. The Department of Education is especially interested in public comment addressing the following issues: (1) Is this collection necessary to the proper functions of the Department; (2) will this information be processed and used in a timely manner; (3) is the estimate of burden accurate; (4) how might the Department enhance the quality, utility, and clarity of the information to be collected; and (5) how might the Department minimize the burden of this collection on the respondents, including through the use of information technology. Please note that written comments received in response to this notice will be considered public records.</P>
        <P>
          <E T="03">Title of Collection:</E>Graduate Assistance in Areas of National Need (GAANN) Performance Report.</P>
        <P>
          <E T="03">OMB Control Number:</E>1840-0748.</P>
        <P>
          <E T="03">Type of Review:</E>Revision.</P>
        <P>
          <E T="03">Total Estimated Number of Annual Responses:</E>225.</P>
        <P>
          <E T="03">Total Estimated Number of Annual Burden Hours:</E>2,475.</P>
        <P>
          <E T="03">Abstract:</E>Graduate Assistance in Areas of National Need (GAANN) grantees must submit a performance report annually. The reports are used to evaluate grantee performance. Further, the data from the reports will be aggregated to evaluate the accomplishments and impact of the GAANN Program as a whole. Results will be reported to the Secretary in order to respond to Government Performance and Results Act (GPRA) requirements.</P>
        <SIG>
          <DATED>Dated: April 20, 2012.</DATED>
          <NAME>Darrin A. King,</NAME>
          <TITLE>Director, Information Collection Clearance Division, Privacy, Information and Records Management Services, Office of Management.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9990 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4000-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="24690"/>
        <AGENCY TYPE="S">DEPARTMENT OF EDUCATION</AGENCY>
        <SUBJECT>Notice of Proposed Information Collection Requests; Federal Student Aid; Pell Grant, ACG, and National SMART Reporting Under the Common Origination and Disbursement (COD) System</SUBJECT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Federal Pell Grant, ACG, and National SMART Programs are student financial assistance programs authorized under the Higher Education Act of 1965 (HEA), as amended. These programs provide grant assistance to an eligible student attending an institution of higher education. The institution determines the student's award and disburses program funds to the student on behalf of the Department (ED). To account for the funds disbursed, institutions report student payment information to ED electronically. COD is a simplified process for requesting, reporting, and reconciling Pell Grant, ACG, and National SMART funds.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Interested persons are invited to submit comments on or before June 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Written comments regarding burden and/or the collection activity requirements should be electronically mailed to<E T="03">ICDocketMgr@ed.gov</E>or mailed to U.S. Department of Education, 400 Maryland Avenue SW., LBJ, Washington, DC 20202-4537. Copies of the proposed information collection request may be accessed from<E T="03">http://edicsweb.ed.gov,</E>by selecting the “Browse Pending Collections” link and by clicking on link number 04843. When you access the information collection, click on “Download Attachments” to view. Written requests for information should be addressed to U.S. Department of Education, 400 Maryland Avenue SW., LBJ, Washington, DC 20202-4537. Requests may also be electronically mailed to<E T="03">ICDocketMgr@ed.gov</E>or faxed to 202-401-0920. Please specify the complete title of the information collection and OMB Control Number when making your request.</P>
          <P>Individuals who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339.</P>
        </ADD>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Section 3506 of the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35) requires that Federal agencies provide interested parties an early opportunity to comment on information collection requests. The Director, Information Collection Clearance Division, Privacy, Information and Records Management Services, Office of Management, publishes this notice containing proposed information collection requests at the beginning of the Departmental review of the information collection. The Department of Education is especially interested in public comment addressing the following issues: (1) Is this collection necessary to the proper functions of the Department; (2) will this information be processed and used in a timely manner; (3) is the estimate of burden accurate; (4) how might the Department enhance the quality, utility, and clarity of the information to be collected; and (5) how might the Department minimize the burden of this collection on the respondents, including through the use of information technology. Please note that written comments received in response to this notice will be considered public records.</P>
        <P>
          <E T="03">Title of Collection:</E>Pell Grant, ACG, and National SMART Reporting under the Common Origination and Disbursement (COD) System.</P>
        <P>
          <E T="03">OMB Control Number:</E>1845-0039.</P>
        <P>
          <E T="03">Type of Review:</E>Extension.</P>
        <P>
          <E T="03">Total Estimated Number of Annual Responses:</E>6,019,900.</P>
        <P>
          <E T="03">Total Estimated Number of Annual Burden Hours:</E>507,362.</P>
        <P>
          <E T="03">Abstract:</E>The Federal Pell Grant, ACG, and National SMART Programs are student financial assistance programs authorized under the Higher Education Act of 1965 (HEA), as amended. These programs provide grant assistance to an eligible student attending an institution of higher education. The institution determines the student's award and disburses program funds to the student on behalf of the Department (ED). To account for the funds disbursed, institutions report student payment information to ED electronically. COD is a simplified process for requesting, reporting, and reconciling Pell Grant, ACG, and National SMART funds.</P>
        <SIG>
          <DATED>Dated: April 19, 2012.</DATED>
          <NAME>Darrin A. King,</NAME>
          <TITLE>Director, Information Collection Clearance Division, Privacy, Information and Records Management Services, Office of Management.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9993 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4000-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF EDUCATION</AGENCY>
        <SUBJECT>Exemplary Charter School Collaboration Awards; Proposed Definitions, Requirements, and Selection Criteria; Catalog of Federal Domestic Assistance (CFDA) Number 84.282P</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of Innovation and Improvement, Department of Education.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Assistant Deputy Secretary for Innovation and Improvement proposes definitions, requirements, and selection criteria for the Exemplary Charter School Collaboration Awards (Collaboration Awards) and may use these definitions, requirements, and selection criteria for a competition in fiscal year (FY) 2012 and later years. The Assistant Deputy Secretary is taking this action to create incentives for charter schools (as defined in section 5210(1) of the Elementary and Secondary Education Act of 1965, as amended (ESEA)) to (a) collaborate with non-chartered public schools (as defined in this notice) and non-chartered local educational agencies (LEAs) to share and transfer best educational and operational practices at the elementary and secondary school levels; and (b) disseminate information about these collaborations across the Nation.</P>
          <P>The Collaboration Awards competition would be designed to encourage charter schools and non-chartered public schools or non-chartered LEAs to share resources and responsibilities, build trust and teamwork, boost academic excellence in charter schools and non-chartered public schools alike, and provide students and their parents with a range of effective educational options.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>We must receive your comments on or before May 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Address all comments about this notice to Erin Pfeltz, U.S. Department of Education, 400 Maryland Avenue SW., Room 4W255, Washington, DC 20202-5970; or to Nancy Paulu, U.S. Department of Education, 400 Maryland Avenue SW., Room 4W246, Washington, DC 20202-5970.</P>

          <P>If you prefer to send your comments by email, use the following addresses:<E T="03">erin.pfeltz@ed.gov</E>or<E T="03">nancy.paulu@ed.gov.</E>You must include the phrase “Exemplary Charter School Collaboration Awards—Comments on Proposed Definitions, Requirements, and Selection Criteria” in the subject line of your electronic message.</P>
        </ADD>
        <FURINF>
          <PRTPAGE P="24691"/>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Erin Pfeltz at (202) 205-3525 or by email at<E T="03">erin.pfeltz@ed.gov</E>or Nancy Paulu at (202) 205-5392 or by email at<E T="03">nancy.paulu@ed.gov.</E>
          </P>
          <P>If you use a telecommunications device for the deaf (TDD) or a text telephone (TTY), call the Federal Relay Service, toll free, at 1-800-877-8339.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P SOURCE="NPAR">
          <E T="03">Invitation to Comment:</E>We invite you to submit comments regarding this notice. To ensure that your comments have maximum effect in developing the notice of final definitions, requirements, and selection criteria, we urge you to identify clearly the specific proposed definition, requirement, or selection criterion that each comment addresses.</P>
        <P>We invite you to assist us in complying with the specific requirements of Executive Orders 12866 and 13563 and their overall requirement of reducing regulatory burden that might result from these proposed definitions, requirements, and selection criteria. Please let us know of ways we could reduce potential costs or increase potential benefits while preserving the effective and efficient administration of the Department's programs and activities.</P>
        <P>During and after the comment period, you may inspect all public comments about this notice in room 4W255, 400 Maryland Avenue SW., Washington, DC, between 8:30 a.m. and 4:00 p.m. Washington, DC time, Monday through Friday of each week except Federal holidays.</P>
        <P>
          <E T="03">Assistance to Individuals with Disabilities in Reviewing the Rulemaking Record:</E>
        </P>

        <P>On request, we will provide an appropriate accommodation or auxiliary aid to an individual with a disability who needs assistance to review the comments or other documents in the public rulemaking record for this notice. If you want to schedule an appointment for this type of accommodation or auxiliary aid, please contact the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <P>
          <E T="03">Purpose of Program:</E>
        </P>
        <P>The purpose of the Charter Schools Program (CSP) is to increase national understanding of the charter school model by—-</P>
        <P>(1) Providing financial assistance for the planning, program design, and initial implementation of charter schools;</P>
        <P>(2) Evaluating the effects of charter schools, including the effects on students, student academic achievement, staff, and parents;</P>
        <P>(3) Expanding the number of high-quality charter schools available to students across the Nation; and</P>
        <P>(4) Encouraging the States to provide support to charter schools for facilities financing in an amount more nearly commensurate to the amount the States have typically provided for traditional public schools.</P>
        <P>
          <E T="03">Background:</E>
        </P>
        <P>Over the past 20 years, the charter school movement has grown in size and significance. The first charter school opened in Minnesota in 1992; today more than 5,000 charter schools are spread across the Nation. As charter schools have increased in number and popularity, so too has the tension between charter schools and traditional public schools and LEAs, as they compete for students. We believe that encouraging and facilitating collaboration between charter schools and non-chartered public schools and non-chartered LEAs can help change this dynamic.</P>
        <P>By encouraging charter schools, other public schools, and LEAs to work together as partners, the Department, through the Collaboration Awards competition, aims to increase national understanding of the charter school model. By creating partnerships and carrying out dissemination activities, non-chartered public schools and non-chartered LEAs would get first-hand experience with the charter school model—freedom from some of the strict rules, regulations, and statutes that inhibit the flexible operation of traditional public schools and LEAs in exchange for increased accountability for producing certain results, as set forth in each school's charter. The Collaboration Awards competition would further support recent Federal initiatives that encourage Federal agencies to provide awards as incentives to stimulate innovation and promote agencies' core missions.</P>
        <P>
          <E T="03">Authorized Activities:</E>
        </P>
        <P>The Collaboration Awards competition would be conducted as a part of the CSP's national activities. Under section 5205(a) of the ESEA, the Secretary reserves CSP funds to carry out a number of national activities, which may include, among other things, (a) providing information, training, and assistance to charter schools; (b) disseminating best or promising practices in charter schools to other public schools; (c) conducting evaluations or studies of the impact of charter schools on student achievement; and (d) providing other types of support and technical assistance to charter schools and other applicants for assistance under the CSP. The required activities that we are proposing for Collaboration Awards are within the scope of these authorized activities.</P>
        <P>Collaboration Award grantees would collaborate, and disseminate information about the collaborations, in a broad range of areas within the scope of activities authorized under section 5205(a) of the ESEA. Awards would be based on the quality of existing or past collaboration activities as well as proposals in the grant applications for future collaboration activities, which could involve continuing, modifying, or expanding the existing or past model or models of collaboration. In making awards, the Secretary also would consider the quality of proposals to disseminate information or best practices regarding the collaboration activities upon which the award is based.</P>
        <P>
          <E T="03">Program Authority:</E>
        </P>
        <P>The CSP is authorized under 20 U.S.C. 7221-7221i. CSP national activities are authorized under 20 U.S.C. 7221d.</P>
        <HD SOURCE="HD1">Proposed Definitions</HD>

        <P>In addition to the definitions in section 5210 of the ESEA, which include the definition of<E T="03">charter school,</E>we are proposing the following definitions for the Collaboration Awards competition. We may apply one or more of these definitions in any year in which we make awards under a Collaboration Awards competition.</P>
        <P>
          <E T="03">Collaboration</E>refers to the activities of a partnership in which two or more organizations or entities work together to accomplish a common goal, which may involve sharing or transferring best practices or strategies.</P>
        <P>
          <E T="03">Non-chartered local educational agency (LEA)</E>refers to an LEA that does not qualify as a charter school as defined in section 5210(1) of the ESEA or under State law.</P>
        <P>
          <E T="03">Non-chartered public school</E>refers to a public school that does not qualify as a charter school under section 5210(1) of the ESEA or under State law.</P>
        <P>
          <E T="03">Significant compliance issue</E>means a violation that did, will, or could lead to the revocation of a school's charter.</P>
        <P>
          <E T="03">Student achievement</E>means—</P>
        <P>(a) For tested grades and subjects: (1) A student's score on the State's assessments under the ESEA; and, as appropriate (2) other measures of student learning, such as those described in paragraph (b) of this definition, provided they are rigorous and comparable across schools.</P>

        <P>(b) For non-tested grades and subjects: Alternative measures of student learning and performance, such as student scores on pre-tests and end-of-course tests;<PRTPAGE P="24692"/>student performance on English language proficiency assessments; and other measures of student achievement that are rigorous and comparable across schools.</P>
        <HD SOURCE="HD1">Proposed Competition Requirements</HD>
        <HD SOURCE="HD2">Background</HD>
        <P>The Department proposes to use the Collaboration Awards competition to encourage collaboration between charter schools and non-chartered public schools and non-chartered LEAs, as well as to disseminate information and share or transfer best practices to improve educational and operational practices in public schools, including public charter schools. The Assistant Deputy Secretary for Innovation and Improvement proposes the following requirements to support these goals. The Department may apply one or more of these requirements in any year in which this competition is in effect.</P>
        <HD SOURCE="HD2">Proposed Eligibility Requirements</HD>
        <P>1. Eligible applicants are charter schools (as defined in section 5210(1) of the ESEA). In order to be eligible to receive an award under a Collaboration Awards competition, a charter school must apply in partnership with at least one non-chartered public school (as defined in this notice) or non-chartered LEA (as defined in this notice) and have the support of the partner(s) to participate in the competition. Multiple charter schools may be included in the partnership so long as they apply in partnership with each other and with at least one non-chartered public school (as defined in this notice) or non-chartered LEA (as defined in this notice).</P>
        <P>2. The partnership must comply with the requirements for group applications set forth in 34 CFR 75.127-129.</P>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>Only an eligible party under the competition may apply for a grant or be the fiscal agent for a grant. Thus a non-chartered public school or a non-chartered LEA would not be eligible to be the lead applicant or fiscal agent for an exemplary charter school collaboration award.</P>
        </NOTE>
        <P>3. An applicant may submit more than one application if each application proposes to carry out substantially different authorized activities.</P>
        <P>4. Applicants may not have any significant compliance issues (as defined in this notice), including in the areas of student safety, financial management, and statutory or regulatory compliance.</P>
        <HD SOURCE="HD2">Proposed Application Requirements</HD>
        <P>An applicant for a Collaboration Award must—</P>
        <P>(1) Provide a detailed narrative describing (a) the applicant's past or existing collaboration model or models (which may involve more than one area of collaboration or partner); (b) the applicant's proposal to continue, modify, or expand the collaboration model or models (which may include adding new areas of collaboration or partners); and (c) the applicant's plan to disseminate information about the collaboration model or models (which may include information about best practices) to other public schools, including chartered schools, non-chartered schools, and non-chartered LEAs. The proposed collaboration model or models may focus on a wide range of areas within the scope of activities authorized under section 5205(a) of the ESEA, which includes, but is not limited to, curriculum and instruction, data management and sharing, organization and management, personnel, facilities, finances, Federal programs, standards, assessments, special education services, English learners, students with other special needs, student transportation, and professional development and training.</P>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>In a particular year, the Secretary may restrict applications to one or more areas of focus or authorized activity under section 5205(a) of the ESEA.</P>
        </NOTE>
        <P>(2) Provide written assurance from authorized officials of the entities involved in the partnership that all participants—</P>
        <P>• Agree to submit an application for an award under the competition and have read, understand, and agree with the application for the competition; and</P>
        <P>• Agree to have the executive summary or narrative of the application, with proprietary information redacted, published on the U.S. Department of Education's Web site (ed.gov), data.ed.gov, the National Charter School Resource Center Web site (charterschoolcenter.org), or any other Web site or publication deemed appropriate by the Secretary;</P>
        <P>(3) Submit a partnership agreement that meets the requirements of 34 CFR 75.128(b).</P>
        <P>(4) Provide a clear description of the goals and desired outcomes of the proposed collaboration and current or proposed measures that would be used to gauge success in meeting those goals and desired outcomes.</P>
        <P>(5) Describe any past, existing, or anticipated obstacles to implementing the collaboration model or models or to disseminating information about the collaboration model or models, and the strategies that were or will be used to overcome those obstacles.</P>
        <P>(6) Specify how the award money will be used to implement the collaboration model or models and to disseminate information about the collaboration model or models in accordance with section 5205(a) of the ESEA.</P>
        <P>(7) Specify how the award money will be shared between the partners named in the application. If grant activities will be carried out by both the applicant (the charter school) and its partner(s), the applicant must describe in the application and in the partnership agreement how the award money will be allocated between the partners, including the applicant.</P>
        <HD SOURCE="HD2">Proposed Award Amounts and Funding Restrictions</HD>

        <P>(1) The Department will announce in a notice inviting applications published in the<E T="04">Federal Register</E>the estimated amount of funds available for a given Collaboration Awards competition and the number of awards that we expect to make.</P>
        <P>(2) A Collaboration Award grantee must use the award funds to carry out one or more of the following activities: (a) Continuing the collaboration model or models for which it received the award, as described in its grant application; (b) modifying the collaboration model or models for which it received the award, as described in the application; (c) expanding the collaboration model or models for which it received the award by adding additional areas of collaboration, as described in the application; or (d) expanding the collaboration model or models for which it received the award by adding additional partners (schools or LEAs), as described in the application. Collaboration Award grantees also must use award funds to disseminate information about the collaboration activities to other public schools, including chartered schools, non-chartered schools, and non-chartered LEAs. All activities carried out under the Collaboration Awards must fall within the scope of authorized activities set forth in section 5205(a) of the ESEA.</P>
        <HD SOURCE="HD1">Proposed Selection Criteria</HD>
        <HD SOURCE="HD2">Background</HD>

        <P>The selection criteria we propose are designed to— (1) support collaborations between charter schools and non-chartered public schools and non-chartered LEAs that are most effective in raising student outcomes and creating efficiencies; (2) further the CSP's mission of increasing national understanding of the charter school<PRTPAGE P="24693"/>model; and (3) expand the number of high-quality charter schools.</P>
        <HD SOURCE="HD2">Selection Criteria</HD>
        <P>The Secretary proposes the following selection criteria for Collaboration Awards competitions and further proposes that we may apply one or more of these criteria alone or in combination with one or more selection criteria (1) based on the CSP authorizing statute or (2) in 34 CFR 75.210, in any year in which this program is in effect. In the notice inviting applications or the application package, or both, we will announce the maximum possible points assigned to each criterion.</P>
        <P>The Secretary could make awards to the top-rated applications proposing to carry out activities in specific areas of focus (e.g., curriculum and instruction, data management and sharing, organization and management) within the scope of authorized activities under section 5205(a) of the ESEA. In a particular year, the Secretary may restrict applications to one or more areas of focus. Additionally, in making awards, the Secretary could fund applications out of rank order in order to ensure that the Collaboration Awards are distributed throughout each area of the Nation or a State.</P>
        <P>(1)<E T="03">Record of and potential for success.</E>(A) The extent to which the applicant's past or existing collaboration model or models have improved educational outcomes and operational practices, and (B) the extent to which the applicant's proposed collaboration model or models and dissemination plan will achieve one or more of the following demonstrable results:</P>
        <P>(i) Improved operational practices and productivity among all partners;</P>
        <P>(ii) Improved student achievement (as defined in this notice);</P>
        <P>(iii) Improved high school graduation rates;</P>
        <P>(iv) Improved rates of college matriculation and college graduation; or</P>
        <P>(v) Improved rates of attendance and graduation from other postsecondary (i.e., non-college) institutions or programs.</P>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>In the notice inviting applications or the application package, or both, we may assign points individually to the factors listed under this selection criterion.</P>
        </NOTE>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>The Secretary invites comment on this criterion particularly with respect to measures that might be used to determine the extent to which an applicant's proposed collaboration model or models and dissemination plan will achieve improved operational practices and productivity among all partners.</P>
        </NOTE>
        <P>(2)<E T="03">Quality of the project design.</E>The extent to which the applicant proposes a high-quality plan to use its award money to improve educational outcomes and operational practices in public schools, including charter schools.</P>
        <P>(3)<E T="03">Potential for scalability.</E>The extent to which the applicant's proposed collaboration model or models can be replicated or adapted beyond the participating partners by other public schools or non-chartered LEAs and sustained long-term.</P>
        <P>(4)<E T="03">Innovation.</E>The extent to which the applicant demonstrates that its proposed collaboration model or models, as well as its dissemination plan, are either (a) substantially different from other efforts in its area of focus; or (b) substantially more effective than similar efforts in its area of focus.</P>
        <HD SOURCE="HD2">Final Definitions, Requirements, and Selection Criteria</HD>

        <P>We will announce the final definitions, requirements, and selection criteria in a notice in the<E T="04">Federal Register</E>. We will determine the final definitions, requirements, and selection criteria after considering responses to this notice and other information available to the Department. This notice does not preclude us from proposing priorities or additional definitions, requirements, or selection criteria, subject to meeting applicable rulemaking requirements.</P>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>This notice does<E T="03">not</E>solicit applications. In any year in which we choose to use one or more of these proposed definitions, requirements, and selection criteria, we will invite applications through a notice in the<E T="04">Federal Register</E>.</P>
        </NOTE>
        <HD SOURCE="HD1">Executive Orders 12866 and 13563</HD>
        <HD SOURCE="HD2">Regulatory Impact Analysis</HD>
        <P>This proposed regulatory action is not a significant regulatory action subject to review by OMB under section 3 (f) of Executive Order 12866.</P>
        <P>We have also reviewed this proposed regulatory action under Executive Order 13563, which supplements and explicitly reaffirms the principles, structures, and definitions governing regulatory review established in Executive Order 12866. To the extent permitted by law, Executive Order 13563 requires that an agency—</P>
        <P>(1) Propose or adopt regulations only on a reasoned determination that their benefits justify their costs (recognizing that some benefits and costs are difficult to quantify);</P>
        <P>(2) Tailor its regulations to impose the least burden on society, consistent with obtaining regulatory objectives and taking into account—among other things and to the extent practical—the costs of cumulative regulations;</P>
        <P>(3) In choosing among alternative regulatory approaches, select those approaches that maximize net benefits (including potential economic, environmental, public health and safety and other advantages; distributive impacts; and equity);</P>
        <P>(4) To the extent feasible, specify performance objectives, rather than the behavior or manner of compliance a regulated entity must adopt; and</P>
        <P>(5) Identify and assess available alternatives to direct regulation, including economic incentives—such as user fees or marketable permits—to encourage the desired behavior, or provide information that enables the public to make choices.</P>
        <P>Executive Order 13563 also requires an agency “to use the best available techniques to quantify anticipated present and future benefits and costs as accurately as possible.” The Office of Information and Regulatory Affairs of OMB has emphasized that these techniques may include “identifying changing future compliance costs that might result from technological innovation or anticipated behavior changes.”</P>
        <P>We are taking this proposed regulatory action only on a reasoned determination that the benefits justify the costs. In choosing among alternative regulatory approaches, we selected those approaches that maximize net benefits. The Department believes that this proposed regulatory action is consistent with the principles in Executive Order 13563.</P>
        <P>We also have determined that this regulatory action would not unduly interfere with State, local, and tribal governments in the exercise of their governmental functions.</P>
        <P>In accordance with both Executive orders, the Department has assessed the potential costs and benefits of this regulatory action. The potential costs associated with this regulatory action are those resulting from statutory requirements and those we have determined as necessary for administering the Department's programs and activities.</P>
        <HD SOURCE="HD2">Paperwork Reduction Act of 1995</HD>

        <P>As part of its continuing effort to reduce paperwork and respondent burden, the Department conducts a preclearance consultation program to provide the general public and Federal agencies with an opportunity to comment on proposed and continuing collections of information in accordance with the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3506(c)(2)(A)).<PRTPAGE P="24694"/>This helps ensure that the public understands the Department's collection instructions, respondents can provide the requested data in the desired format, reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the Department can properly assess the impact of collection requirements on respondents.</P>
        <P>We estimate that each applicant would spend approximately 176 hours of staff time to address the proposed requirements and selection criteria, prepare the application, and obtain necessary clearances. The total number of hours for all expected applicants is an estimated 7,040 hours. We estimate the total cost per hour of the applicant-level staff who will carry out this work to be $57 per hour. The total estimated cost for all applicants would be $401,280.</P>

        <P>We have submitted an Information Collection Request (ICR) for this collection to the Office of Management and Budget (OMB). If you want to comment on the proposed information collection requirements, please send your comments to the Office of Information and Regulatory Affairs, OMB, Attention: Desk Officer for U.S. Department of Education. Send these comments by email to<E T="03">OIRA_DOCKET@omb.eop.gov</E>or by fax to (202) 395-6974. You may also send a copy of these comments to the Department contact named in the<E T="02">ADDRESSES</E>section of this notice.</P>

        <P>In preparing your comments you may want to review the ICR, which we maintain in the Education Department Information Collection System (EDICS) at<E T="03">http://edicsweb.ed.gov.</E>Click on “Browse Pending Collections.” This proposed collection is identified as proposed collection 1855-NEW. This ICR is also available on OMB's RegInfo Web site at<E T="03">www.reginfo.gov.</E>
        </P>
        <P>We consider your comments on this proposed collection of information in—</P>
        <P>• Deciding whether the proposed collection is necessary for the proper performance of our functions, including whether the information will have practical use;</P>
        <P>• Evaluating the accuracy of our estimate of the burden of the proposed collection, including the validity of our methodology and assumptions;</P>
        <P>• Enhancing the quality, usefulness, and clarity of the information we collect; and</P>
        <P>• Minimizing the burden on those who must respond. This includes exploring the use of appropriate automated, electronic, mechanical, or other technological collection techniques.</P>

        <P>OMB is required to make a decision concerning the collection of information contained in these proposed definitions, requirements, and selection criteria between 30 and 60 days after publication of this document in the<E T="04">Federal Register</E>. Therefore, to ensure that OMB gives your comments full consideration, it is important that OMB receives your comments on the proposed collection by May 25, 2012. This does not affect the deadline for your comments to us on the proposed definitions, requirements, and selection criteria.</P>
        <P>Please note that a Federal agency cannot conduct or sponsor a collection of information unless OMB approves the collection under the PRA and the corresponding information collection instrument displays a currently valid OMB control number. Notwithstanding any other provision of law, no person is required to comply with, or is subject to penalty for failure to comply with, a collection of information if the collection instrument does not display a currently valid OMB control number. We will provide the OMB control number when we publish the notice of final definitions, requirements, and selection criteria.</P>
        <P>
          <E T="03">Intergovernmental Review:</E>This program is subject to Executive Order 12372 and the regulations in 34 CFR part 79. One of the objectives of the Executive order is to foster an intergovernmental partnership and a strengthened federalism. The Executive order relies on processes developed by State and local governments for coordination and review of proposed Federal financial assistance.</P>
        <P>This document provides early notification of our specific plans and actions for this program.</P>
        <P>
          <E T="03">Accessible Format:</E>Individuals with disabilities can obtain this document in an accessible format (e.g., braille, large print, audiotape, or compact disc) on request to the contact person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <P>
          <E T="03">Electronic Access to This Document:</E>The official version of this document is the document published in the<E T="04">Federal Register</E>.  Free Internet access to the official edition of the<E T="04">Federal Register</E>and the Code of Federal Regulations is available via the Federal Digital System at:<E T="03">www.gpo.gov/fdsys.</E>At this site you can view this document, as well as all other documents of this Department published in the<E T="04">Federal Register</E>,  in text or Adobe Portable Document Format (PDF). To use PDF you must have Adobe Acrobat Reader, which is available free at the site.</P>

        <P>You may also access documents of the Department published in the<E T="04">Federal Register</E>by using the article search feature at:<E T="03">www.federalregister.gov.</E>Specifically, through the advanced search feature at this site, you can limit your search to documents published by the Department.</P>
        <SIG>
          <DATED>Dated: April 20, 2012.</DATED>
          <NAME>James H. Shelton, III,</NAME>
          <TITLE>Assistant Deputy Secretary for  Innovation and Improvement.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-10005 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4000-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <SUBJECT>Environmental Management Site-Specific Advisory Board, Nevada</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of Energy.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of open meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>This notice announces a meeting of the Environmental Management Site-Specific Advisory Board (EM SSAB), Nevada. The Federal Advisory Committee Act (Pub. L. 92-463, 86 Stat. 770) requires that public notice of this meeting be announced in the<E T="04">Federal Register</E>.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Wednesday, May 16, 2012, 5 p.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Atomic Testing Museum, 755 East Flamingo Road, Las Vegas, Nevada 89119.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Denise Rupp, Board Administrator, 232 Energy Way, M/S 505, North Las Vegas, Nevada 89030. Phone: (702) 630-0522; Fax (702) 295-5300 or Email:<E T="03">nssab@nv.doe.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>
          <E T="03">Purpose of the Board:</E>The purpose of the Board is to make recommendations to DOE-EM and site management in the areas of environmental restoration, waste management, and related activities.</P>
        
        <FP SOURCE="FP-2">
          <E T="03">Tentative Agenda:</E>
        </FP>
        <FP SOURCE="FP1-2">1. Groundwater Update</FP>
        <FP SOURCE="FP1-2">2. Student Liaison Project Update</FP>
        <FP SOURCE="FP1-2">3. Industrial Sites—Long-term Monitoring at Closed Sites</FP>
        
        <P>
          <E T="03">Public Participation:</E>The EM SSAB, Nevada, welcomes the attendance of the public at its advisory committee meetings and will make every effort to accommodate persons with physical disabilities or special needs. If you require special accommodations due to a disability, please contact Denise Rupp at least seven days in advance of the meeting at the phone number listed above. Written statements may be filed with the Board either before or after the meeting. Individuals who wish to make<PRTPAGE P="24695"/>oral presentations pertaining to agenda items should contact Denise Rupp at the telephone number listed above. The request must be received five days prior to the meeting and reasonable provision will be made to include the presentation in the agenda. The Deputy Designated Federal Officer is empowered to conduct the meeting in a fashion that will facilitate the orderly conduct of business. Individuals wishing to make public comments will be provided a maximum of five minutes to present their comments.</P>
        <P>
          <E T="03">Minutes:</E>Minutes will be available by writing to Denise Rupp at the address listed above or at the following Web site:<E T="03">http://nv.energy.gov/nssab/MeetingMinutes.aspx.</E>
        </P>
        <SIG>
          <DATED>Issued at Washington, DC on April 18, 2012.</DATED>
          <NAME>LaTanya R. Butler,</NAME>
          <TITLE>Acting Deputy Committee Management Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9941 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6450-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBJECT>Environmental Management Site-Specific Advisory Board, Savannah River Site</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of Energy.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of open meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>This notice announces a meeting of the Environmental Management Site-Specific Advisory Board (EM SSAB), Savannah River Site. The Federal Advisory Committee Act (Pub. L. . 92-463, 86 Stat. 770) requires that public notice of this meeting be announced in the<E T="04">Federal Register</E>.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Monday, May 21, 2012, 1 p.m.-5 p.m.Tuesday, May 22, 2012, 8:30 a.m.-4:30 p.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The Hilton Savannah DeSoto,15 East Liberty StreetSavannah, GA 31401.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Gerri Flemming, Office of External Affairs, Department of Energy, Savannah River Operations Office, P.O. Box A, Aiken, SC, 29802; Phone: (803) 952-7886.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P SOURCE="NPAR">
          <E T="03">Purpose of the Board:</E>The purpose of the Board is to make recommendations to DOE-EM and site management in the areas of environmental restoration, waste management, and related activities.</P>
        <HD SOURCE="HD1">Tentative Agenda</HD>
        <HD SOURCE="HD2">Monday, May 21, 2012</HD>
        <FP SOURCE="FP-2">1 p.m. Combined Committees Session</FP>
        <FP SOURCE="FP-2">5 p.m. Adjourn</FP>
        <HD SOURCE="HD2">Tuesday, May 22, 2012</HD>
        <FP SOURCE="FP-2">8:30 a.m.—Approval of Minutes, Agency Updates</FP>
        <FP SOURCE="FP1-2">Public Comment Session</FP>
        <FP SOURCE="FP1-2">Facilities Disposition and Site Remediation Committee Report</FP>
        <FP SOURCE="FP1-2">Nuclear Materials Committee Report</FP>
        <FP SOURCE="FP1-2">Public Comment Session</FP>
        <FP SOURCE="FP-2">12:30 p.m.—Lunch Break</FP>
        <FP SOURCE="FP-2">1:30 p.m.—Strategic and Legacy Management Committee Report</FP>
        <FP SOURCE="FP1-2">Waste Management Committee Report</FP>
        <FP SOURCE="FP1-2">Administrative Committee Report</FP>
        <FP SOURCE="FP1-2">Public Comment Session</FP>
        <FP SOURCE="FP-2">4:30 p.m.—Adjourn</FP>
        
        <P>
          <E T="03">Public Participation:</E>The EM SSAB, Savannah River Site, welcomes the attendance of the public at its advisory committee meetings and will make every effort to accommodate persons with physical disabilities or special needs. If you require special accommodations due to a disability, please contact Gerri Flemming at least seven days in advance of the meeting at the phone number listed above. Written statements may be filed with the Board either before or after the meeting. Individuals who wish to make oral statements pertaining to agenda items should contact Gerri Flemming's office at the address or telephone listed above. Requests must be received five days prior to the meeting and reasonable provision will be made to include the presentation in the agenda. The Deputy Designated Federal Officer is empowered to conduct the meeting in a fashion that will facilitate the orderly conduct of business. Individuals wishing to make public comments will be provided a maximum of five minutes to present their comments.</P>
        <P>
          <E T="03">Minutes:</E>Minutes will be available by writing or calling Gerri Flemming at the address or phone number listed above. Minutes will also be available at the following Web site:<E T="03">http://cab.srs.gov/srs-cab.html.</E>
        </P>
        <SIG>
          <DATED>Issued at Washington, DC, on April 18, 2012.</DATED>
          <NAME>LaTanya R. Butler,</NAME>
          <TITLE>Acting Deputy Committee Management Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9942 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6450-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <SUBJECT>Combined Notice of Filings #1</SUBJECT>
        <P>Take notice that the Commission received the following electric rate filings:</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER11-2664-002.</P>
        <P>
          <E T="03">Applicants:</E>Powerex Corporation.</P>
        <P>
          <E T="03">Description:</E>Powerex Corp submits notice of change in status.</P>
        <P>
          <E T="03">Filed Date:</E>4/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20120417-0202.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 5/4/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-1554-000.</P>
        <P>
          <E T="03">Applicants:</E>New York Independent System Operator, Inc., Consolidated Edison Company of New York, Inc.</P>
        <P>
          <E T="03">Description:</E>Amended Restated Agreement No 330 between Con Edison and Astoria Energy to be effective 6/16/2012.</P>
        <P>
          <E T="03">Filed Date:</E>4/17/12.</P>
        <P>
          <E T="03">Accession Number:</E>20120417-5182.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 5/8/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-1555-000.</P>
        <P>
          <E T="03">Applicants:</E>High Majestic Interconnection Services, LLC.</P>
        <P>
          <E T="03">Description:</E>Coordination Services Agreement between High Majestic Interconnect and HMI to be effective 6/16/2012.</P>
        <P>
          <E T="03">Filed Date:</E>4/17/12.</P>
        <P>
          <E T="03">Accession Number:</E>20120417-5189..</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 5/8/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-1556-000.</P>
        <P>
          <E T="03">Applicants:</E>High Majestic Interconnection Services, LLC.</P>
        <P>
          <E T="03">Description:</E>CSA Between High Majestic Interconnect and HMII to be effective 6/16/2012.</P>
        <P>
          <E T="03">Filed Date:</E>4/17/12.</P>
        <P>
          <E T="03">Accession Number:</E>20120417-5190.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 5/8/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-1557-000.</P>
        <P>
          <E T="03">Applicants:</E>Southern California Edison Company.</P>
        <P>
          <E T="03">Description:</E>Amended LGIA Manzana Wind LLC, Manzana Wind Project to be effective 6/18/2012.</P>
        <P>
          <E T="03">Filed Date:</E>4/18/12.</P>
        <P>
          <E T="03">Accession Number:</E>20120418-5000.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 5/9/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-1558-000.</P>
        <P>
          <E T="03">Applicants:</E>Southern California Edison Company.</P>
        <P>
          <E T="03">Description:</E>CLGIA and Distribution Service Agmt with Mesa Wind Power Corporation to be effective 4/9/2012.</P>
        <P>
          <E T="03">Filed Date:</E>4/18/12.</P>
        <P>
          <E T="03">Accession Number:</E>20120418-5002.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 5/9/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-1559-000.</P>
        <P>
          <E T="03">Applicants:</E>High Majestic Wind Energy Center, LLC.</P>
        <P>
          <E T="03">Description:</E>CFA Between HMI, HMII, and High Majestic Interconnection to be effective 6/16/2012.</P>
        <P>
          <E T="03">Filed Date:</E>4/18/12.</P>
        <P>
          <E T="03">Accession Number:</E>20120418-5052.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 5/9/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-1560-000.</P>
        <P>
          <E T="03">Applicants:</E>Southern California Edison Company.<PRTPAGE P="24696"/>
        </P>
        <P>
          <E T="03">Description:</E>Amendment to Interconnection Facilities Agreement with City of Industry to be effective 4/19/2012.</P>
        <P>
          <E T="03">Filed Date:</E>4/18/12.</P>
        <P>
          <E T="03">Accession Number:</E>20120418-5107.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 5/9/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-1561-000.</P>
        <P>
          <E T="03">Applicants:</E>LDH Rensselaer LLC.</P>
        <P>
          <E T="03">Description:</E>Notice of Succession to be effective 3/31/2012.</P>
        <P>
          <E T="03">Filed Date:</E>4/18/12.</P>
        <P>
          <E T="03">Accession Number:</E>20120418-5109.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 5/9/12.</P>
        
        <P>The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.</P>
        <P>Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>

        <P>eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at:<E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf</E>. For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.</P>
        <SIG>
          <DATED>Dated: April 18, 2012.</DATED>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-9957 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <DEPDOC>[Docket No. ER12-1571-000]</DEPDOC>
        <SUBJECT>Verso Bucksport LLC; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
        <P>This is a supplemental notice in the above-referenced proceeding of Verso Bucksport LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR Part 34, of future issuances of securities and assumptions of liability.</P>
        <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
        <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR Part 34, of future issuances of securities and assumptions of liability, is May 9, 2012.</P>

        <P>The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at<E T="03">http://www.ferc.gov</E>. To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.</P>
        <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426.</P>

        <P>The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive email notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email<E T="03">FERCOnlineSupport@ferc.gov.</E>or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.</P>
        <SIG>
          <DATED>Dated: April 19, 2012.</DATED>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-9956 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <DEPDOC>[Docket No. ER12-1563-000]</DEPDOC>
        <SUBJECT>Cayuga Operating Company, LLC; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
        <P>This is a supplemental notice in the above-referenced proceeding of Cayuga Operating Company, LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.</P>
        <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure(18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
        <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is May 9, 2012.</P>

        <P>The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at<E T="03">http://www.ferc.gov</E>. To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.</P>
        <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426.</P>

        <P>The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive emailnotification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email<E T="03">FERCOnlineSupport@ferc.gov.</E>or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.</P>
        <SIG>
          <DATED>Dated: April 19, 2012.</DATED>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-9959 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="24697"/>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <DEPDOC>[Docket No. ER12-1566-000]</DEPDOC>
        <SUBJECT>Cooper Mountain Solar 2, LLC; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
        <P>This is a supplemental notice in the above-referenced proceeding of Cooper Mountain Solar 2, LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR Part 34, of future issuances of securities and assumptions of liability.</P>
        <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
        <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is May 9, 2012.</P>

        <P>The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at<E T="03">http://www.ferc.gov.</E>To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.</P>
        <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426.</P>

        <P>The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive email notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email<E T="03">FERCOnlineSupport@ferc.gov.</E>or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.</P>
        <SIG>
          <DATED>Dated: April 19, 2012.</DATED>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-9960 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <DEPDOC>[Docket No. ER12-1562-000]</DEPDOC>
        <SUBJECT>Somerset Operating Company, LLC; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
        <P>This is a supplemental notice in the above-referenced proceeding of Somerset Operating Company, LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.</P>
        <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure(18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
        <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is May 9, 2012.</P>

        <P>The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at<E T="03">http://www.ferc.gov</E>. To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.</P>
        <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426.</P>

        <P>The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive emailnotification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email<E T="03">FERCOnlineSupport@ferc.gov.</E>or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.</P>
        <SIG>
          <DATED>Dated: April 19, 2012.</DATED>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-9958 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OPPT-2003-0004; FRL-9346-2]</DEPDOC>
        <SUBJECT>Access to Confidential Business Information by CGI Federal Inc. and Its Identified Subcontractor, FedConcepts/Jorge</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>EPA has authorized its contractor, CGI Federal Inc. (CGI) of Fairfax, VA and Its Identified Subcontractor, to access information which has been submitted to EPA under all sections of the Toxic Substances Control Act (TSCA). Some of the information may be claimed or determined to be Confidential Business Information (CBI).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Access to the confidential data will occur no sooner than May 2, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>
            <E T="03">For technical information contact:</E>Pamela Moseley, Information Management Division (7407M), Office of Pollution Prevention and Toxics, Environmental Protection Agency, 1200 Pennsylvania Ave.  NW., Washington, DC 20460-0001; telephone number: (202) 564-8956; fax number: (202) 564-8955; email address:<E T="03">moseley.pamela@epa.gov.</E>
          </P>
          <P>
            <E T="03">For general information contact:</E>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>
        <P>
          <PRTPAGE P="24698"/>
        </P>
        <HD SOURCE="HD1">I. General Information</HD>
        <HD SOURCE="HD2">A. Does this notice apply to me?</HD>

        <P>This action is directed to the public in general. This action may, however, be of interest to all who manufacture, process, or distribute industrial chemicals. Since other entities may also be interested, the Agency has not attempted to describe all the specific entities that may be affected by this action. If you have any questions regarding the applicability of this action to a particular entity, consult the technical person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <HD SOURCE="HD2">B. How can I get copies of this document and other related information?</HD>

        <P>EPA has established a docket for this action under docket identification (ID) number EPA-HQ-OPPT-2003-0004. 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>
        <HD SOURCE="HD1">II. What action is the agency taking?</HD>
        <P>Under EPA contract number GS-35F-4797H, Task Order Number EP-G11D-00056, contractor CGI of 12601 Fair Lakes Circle, Fairfax, VA; and its Identified Subcontractor, FedConcepts/Jorge of 2231 Crystal Drive, Suite 400, Arlington, VA, will assist the Office of Pollution Prevention and Toxics (OPPT) by providing support for two operations security management areas:</P>
        <P>1. Security Technical Operations, including the operations and maintenance of EPA's network security infrastructure devices and</P>
        <P>2. Operations Security Program Management, which covers security operations oversight and monitoring, security management and reporting, security assessment and consulting and security audits support for the Wide Area Network (WAN) and the National Computer Center (NCC).</P>
        <P>In accordance with 40 CFR 2.306(j), EPA has determined that under EPA contract number GS-35F-4797H, Task Order Number EP-G11D-00056, CGI and Its Identified Subcontractor will require access to CBI submitted to EPA under all sections of TSCA to perform successfully the duties specified under the contract. CGI and Its Identified Subcontractor's personnel will be given access to information submitted to EPA under all sections of TSCA. Some of the information may be claimed or determined to be CBI.</P>

        <P>EPA is issuing this notice to inform all submitters of information under all sections of TSCA that EPA may provide CGI and Its Identified Subcontractor access to these CBI materials on a need-to-know basis only. All access to TSCA CBI under this contract will take place at EPA Headquarters and the Research Triangle Park facilities in accordance with EPA's<E T="03">TSCA CBI Protection Manual.</E>
        </P>
        <P>Access to TSCA data, including CBI, will continue until September 30, 2016. If the contract is extended, this access will also continue for the duration of the extended contract without further notice.</P>
        <P>CGI and Its Identified Subcontractor's personnel will be required to sign nondisclosure agreements and will be briefed on appropriate security procedures before they are permitted access to TSCA CBI.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <P>Environmental protection, Confidential business information.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: April 13, 2012.</DATED>
          <NAME>Matthew G. Leopard,</NAME>
          <TITLE>Director, Information Management Division, Office of Pollution Prevention and Toxics.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9640 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OPPT-2010-1010; FRL-9511-5 ]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities; Submission to OMB for Review and Approval; 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 (44 U.S.C. 3501<E T="03">et seq.</E>), this document announces that the following Information Collection Request (ICR) has been forwarded to the Office of Management and Budget (OMB) for review and approval:<E T="03">TSCA Section 4 Test Rules, Consent Orders, Enforceable Consent Agreements, Voluntary Testing Agreements, Voluntary Data Submissions, and Exemptions from Testing Requirement</E>(EPA ICR No. 1139.09, OMB No. 2070-0033). The ICR, which is abstracted below, describes the nature of the information collection activity and its expected burden and costs.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Additional comments may be submitted on or before May 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Submit your comments, referencing docket ID Number EPA-HQ-OPPT-2010-1010 to (1) EPA online using<E T="03">www.regulations.gov</E>(our preferred method), by email to<E T="03">oppt.ncic@epa.gov</E>or by mail to: Document Control Office (DCO), Office of Pollution Prevention and Toxics (OPPT), Environmental Protection Agency, Mail Code: 7407T, 1200 Pennsylvania Ave. NW., Washington, DC 20460, and (2) OMB at: Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), Attention: Desk Officer for EPA, 725 17th Street NW., Washington, DC 20503.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Maryann Petrole, Director, Environmental Assistance Division, Office of Pollution Prevention and Toxics, Environmental Protection Agency, Mail code: 7408-M, 1200 Pennsylvania Ave. NW., Washington, DC 20460; 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>

        <P>EPA has submitted the following ICR to OMB for review and approval according to the procedures prescribed in 5 CFR 1320.12. On August 10, 2011 (76 FR 49471), EPA sought comments on this renewal pursuant to 5 CFR 1320.8(d). EPA<PRTPAGE P="24699"/>received one supportive comment during the comment period, which did not result in any substantive change to the Supporting Statement. Any additional comments related to this ICR should be submitted to EPA and OMB within 30 days of this notice.</P>

        <P>EPA has established a public docket for this ICR under Docket ID No. EPA EPA-HQ-OPPT-2010-1010, which is available for online viewing at<E T="03">http://www.regulations.gov</E>, or in person inspection at the OPPT Docket in the EPA Docket Center (EPA/DC), EPA West, Room 3334, 1301 Constitution Ave. NW., Washington, DC. The EPA Docket Center Public Reading Room is open from 8 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Reading Room is 202-566-1744, and the telephone number for the Pollution Prevention and Toxics Docket is 202-566-0280. Use<E T="03">www.regulations.gov</E>to submit or view public comments, access the index listing of the contents of the public docket, and to access those documents in the public docket that are available electronically. Once in the system, select “search,” then key in the docket ID number identified above.</P>

        <P>EPA's policy is that public comments, whether submitted electronically or in paper, will be made available for public viewing in<E T="03">www.regulations.gov</E>as EPA receives them and without change, unless the comment contains copyrighted material, confidential business information (CBI), or other information whose public disclosure is restricted by statute. When EPA identifies a comment containing copyrighted material, EPA will provide a reference to that material in the version of the comment that is placed in<E T="03">www.regulations.gov</E>. The entire printed comment, including the copyrighted material, will be available in the public docket. Although identified as an item in the official docket, information claimed as CBI, or whose disclosure is otherwise restricted by statute, is not included in the official public docket, and will not be available for public viewing in<E T="03">www.regulations.gov</E>. For further information about the electronic docket, go to<E T="03">www.regulations.gov</E>.</P>
        <P>
          <E T="03">Title:</E>TSCA Section 4 Test Rules, Consent Orders, Enforceable Consent Agreements, Voluntary Testing Agreements, Voluntary Data Submissions, and Exemptions from Testing Requirement.</P>
        <P>
          <E T="03">ICR Status:</E>This is a request to renew an existing approved collection. This ICR is scheduled to expire on April 30, 2012. Under OMB regulations, the Agency may continue to conduct or sponsor the collection of information while this submission is pending at OMB.</P>
        <P>
          <E T="03">Abstract:</E>This ICR covers the submission of test data to the Environmental Protection Agency (EPA) to support the decision making process for an industrial chemical under the Toxic Substances Control Act (TSCA) (15 U.S.C. 2601). Under TSCA, EPA has the authority to issue regulations designed to gather health/safety and exposure information on, require testing of, and control exposure to chemical substances and mixtures. Drugs, cosmetics, foods, food additives, pesticides, and nuclear materials are exempt from TSCA.</P>
        <P>Under TSCA section 4, EPA must assure that appropriate tests are performed on a chemical if it decides: (1) That a chemical being considered under TSCA section 4(a) may pose an “unreasonable risk” or is produced in “substantial” quantities that may result in substantial or significant human exposure or substantial environmental release of the chemical; (2) that additional data are needed to determine or predict the impacts of the chemical's manufacture, processing, distribution, use or disposal; and (3) that testing is needed to develop such data.</P>
        <P>In general, when the need for data is identified by EPA, EPA may obtain the needed test data (1) By issuing a test rule through notice and comment rulemaking, (2) through negotiation with industry and issuing an enforceable consent agreement (ECA), or (3) through commitments from industry, i.e., voluntary testing agreements (VTAs). Industry may also submit test data to EPA on their own initiative.</P>
        <P>EPA uses the information collected under the authority of TSCA section 4 to assess risks associated with the manufacture, processing, distribution, use or disposal of a chemical, and to support any necessary regulatory action with respect to that chemical.</P>
        <P>The testing specified in a rule or consent order issued under TSCA section 4 only needs to be conducted once for each specified chemical. As such, only one of the entities that manufacture, import or process the specified chemical, or a consortia formed by these entities, is expected to conduct the specified testing and report the results of that testing to EPA. In addition, an entity subject to a test rule may apply for an exemption from the testing requirement if that testing will be or has been performed by another party.</P>
        <P>This information collection applies to reporting and recordkeeping activities associated with the information that EPA requires industry to provide in response to TSCA section 4 test rules, consent orders or voluntary agreements, and other data submissions, as well as those related to the exemption applications. As such, responses to the collection of information are either mandatory if codified (see 40 CFR part 790), and voluntary when not.</P>
        <P>Respondents may claim all or part of a response as CBI. EPA will disclose information that is covered by a CBI claim only to the extent permitted by, and in accordance with, the procedures in 40 CFR part 2.</P>

        <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number. The OMB control numbers for EPA's regulations in title 40 of the CFR, after appearing in the<E T="04">Federal Register</E>, are listed in 40 CFR part 9 and included on the related collection instrument or form, if applicable.</P>
        <P>
          <E T="03">Burden Statement:</E>The annual public reporting and recordkeeping burden for this collection of information is estimated to range between 9 and 263 hours per response. Burden is defined in 5 CFR 1320.3(b).</P>
        <P>
          <E T="03">Respondents/Affected Entities:</E>Entities potentially affected by this ICR are manufacturers, processors, importers, users, distributors or disposers of one or more specified chemical substances.</P>
        <P>
          <E T="03">Frequency of Collection:</E>On occasion.</P>
        <P>
          <E T="03">Estimated Average Number of Responses for Each Respondent:</E>Varies by activity, but is estimated to range from 1 to 131 per respondent.</P>
        <P>
          <E T="03">Estimated Total No. of Respondents:</E>Varies by activity, but is estimated to range from 1 to 18.</P>
        <P>
          <E T="03">Estimated Total Annual Burden on Respondents:</E>629,893 hours.</P>
        <P>
          <E T="03">Estimated Total Annual Costs:</E>$13,289,461, with an additional $9,628,441 for non-labor costs related to laboratory test costs.</P>
        <P>
          <E T="03">Changes in Burden Estimates:</E>This request represents an increase of 477,931 hours from that currently in the OMB inventory (from 151,962 hours to 629,893 hours). This increase reflects several adjustments in the estimates related to a better break-out of the different activities for the covered collection and an adjustment in projected potential future activities regarding voluntary submissions. The Agency has also adjusted all unit costs to reflect the latest available labor wage rates and has identified the non-labor costs more clearly. The Supporting Statement provides details about the<PRTPAGE P="24700"/>change in burden estimate. The change is an adjustment.</P>
        <SIG>
          <NAME>John Moses,</NAME>
          <TITLE>Director, Collection Strategies Division.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9902 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OECA-2011-0248; FRL-9515-5]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities; Submission to OMB for Review and Approval; Comment Request; NESHAP for Steel Pickling, HCl Process Facilities and Hydrochloric Acid Regeneration Plants (Renewal)</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 (44 U.S.C. 3501<E T="03">et seq.</E>), this document announces that an Information Collection Request (ICR) has been forwarded to the Office of Management and Budget (OMB) for review and approval. This is a request to renew an existing approved collection. The ICR which is abstracted below describes the nature of the collection and the estimated burden and cost.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Additional comments may be submitted on or before May 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Submit your comments, referencing docket ID number EPA-HQ-OECA-2011-0248, to: (1) EPA online using<E T="03">www.regulations.gov</E>(our preferred method), or by email to:<E T="03">docket.oeca@epa.gov,</E>or by mail to: EPA Docket Center (EPA/DC), Environmental Protection Agency, Enforcement and Compliance Docket and Information Center, mail code 2822T, 1200 Pennsylvania Avenue NW., Washington, DC 20460; and (2) OMB at: Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), Attention: Desk Officer for EPA, 725 17th Street NW., Washington, DC 20503.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Learia Williams, Monitoring, Assistance, and Media Programs Division, Office of Compliance, Mail Code 2227A, Environmental Protection Agency, 1200 Pennsylvania Avenue NW., Washington, DC 20460; telephone number: (202) 564-4113; fax number: (202) 564-0050; email address:<E T="03">williams.learia@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>EPA has submitted the following ICR to OMB for review and approval according to the procedures prescribed in 5 CFR 1320.12. On May 9, 2011 (76<E T="03">FR</E>26900), EPA sought comments on this ICR pursuant to 5 CFR 1320.8(d). EPA received no comments. Any additional comments on this ICR should be submitted to EPA and OMB within 30 days of this notice.</P>

        <P>EPA has established a public docket for this ICR under docket ID number EPA-HQ-OECA-2011-0248, which is available for public viewing online at<E T="03">http://www.regulations.gov,</E>in person viewing at the Enforcement and Compliance Docket in the EPA Docket Center (EPA/DC), EPA West, 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 Reading Room is (202) 566-1744, and the telephone number for the Enforcement and Compliance Docket is (202) 566-1927.</P>
        <P>Use EPA's electronic docket and comment system at<E T="03">http://www.regulations.gov</E>to submit or view public comments, access the index listing of the contents of the docket, and to access those documents in the docket that are available electronically. Once in the system, select “docket search,” then key in the docket ID number identified above. Please note that EPA's policy is that public comments, whether submitted electronically or in paper, will be made available for public viewing at<E T="03">http://www.regulations.gov</E>as EPA receives them and without change, unless the comment contains copyrighted material, Confidential Business Information (CBI), or other information whose public disclosure is restricted by statute. For further information about the electronic docket, go to<E T="03">www.regulations.gov.</E>
        </P>
        <P>
          <E T="03">Title:</E>NESHAP for Steel Pickling, HCl Process Facilities and Hydrochloric Acid Regeneration Plants (Renewal).</P>
        <P>
          <E T="03">ICR Numbers:</E>EPA ICR Number 1821.07, OMB Control Number 2060-0419.</P>
        <P>
          <E T="03">ICR Status:</E>This ICR is schedule to expire on May 31, 2012. Under OMB regulations, the Agency may continue to conduct or sponsor the collection of information while this submission is pending at OMB. 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 CFR, after appearing in the<E T="04">Federal Register</E>when approved, are listed in 40 CFR part 9 and 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 in certain EPA regulations is consolidated in 40 CFR part 9.</P>
        <P>
          <E T="03">Abstract:</E>The affected entities are subject to the General Provisions of the NESHAP at 40 CFR part 63, subpart A, and any changes, or additions to the Provisions specified at 40 CFR part 63, subpart CCC. The rule applies to all facilities that pickle steel using hydrochloric acid or regenerate hydrochloric acid, and are major sources or are part of a facility that is a major source.</P>
        <P>Owners or operators of the affected facilities must submit initial notification, performance tests, and periodic reports and results. Owners or operators are also required to maintain records of the occurrence and duration of any startup, shutdown, or malfunction in the operation of an affected facility, or any period during which the monitoring system is inoperative. Reports, at a minimum, are required semiannually.</P>
        <P>All reports are sent to the delegated state or local authority. In the event that there is no such delegated authority, the reports are sent directly to the EPA regional office. This information is being collected to assure compliance with 40 CFR part 63, subpart CCC, as authorized in section 112 and 114(a) of the Clean Air Act. The required information consists of emissions data and other information that have been determined to be private.</P>
        <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB Control Number. The OMB Control Number for the EPA regulations are listed in 40 CFR part 9 and 48 CFR chapter 15, and are identified on the form and/or instrument, if applicable.</P>
        <P>
          <E T="03">Burden Statement:</E>The annual public reporting and recordkeeping burden for this collection of information is estimated to average 168 hours per response. “Burden” means the total time, effort, or financial resources expended by persons to generate, maintain, retain, or disclose and 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. All existing ways will have to adjust to comply with any previously applicable instructions and requirements that have<PRTPAGE P="24701"/>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>
          <E T="03">Respondents/Affected Entities:</E>Steel pickling, HCl process facilities and hydrochloric acid regeneration plants.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>72.</P>
        <P>
          <E T="03">Frequency of Response:</E>Initially, occasionally and semiannually.</P>
        <P>
          <E T="03">Estimated Total Annual Hour Burden:</E>25,316.</P>
        <P>
          <E T="03">Estimated Total Annual Cost:</E>$2,433,399, which includes $2,425,767 in labor costs, no capital/startup costs, and $7,632 in operation and maintenance (O&amp;M) costs.</P>
        <P>
          <E T="03">Changes in the Estimates:</E>There is no change in the labor hours in this ICR compared to the previous ICR. This is due to two considerations: (1) The regulations have not changed over the past three years and are not anticipated to change over the next three years; and (2) the growth rate for the industry is very low, negative or non-existent, so there is no significant change in the overall burden. However, there is an increase in the total labor and Agency costs as currently identified in the OMB Inventory of Approved Burdens. This increase is not due to any program changes. The change in cost estimates reflects updated labors rates available from the Bureau of Labor Statistics.</P>
        <SIG>
          <NAME>John Moses,</NAME>
          <TITLE>Director, Collection Strategies Division.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9900 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OW-2011-0442; FRL 9516-1]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities; Submission to OMB for Review and Approval; Comment Request; Microbial Rules (Renewal)</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) (44 U.S.C. 3501 et seq.), this document announces that an Information Collection Request (ICR) has been forwarded to the Office of Management and Budget (OMB) for review and approval. This is a request to renew an existing approved collection. The ICR, which is abstracted below, describes the nature of the information collection and its estimated burden and cost.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Additional comments may be submitted on or before May 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit your comments, referencing Docket ID No. EPA-HQ-OW-2011-0442, by using one of the following methods:</P>
          <P>•<E T="03">www.regulations.gov:</E>(our preferred method) Follow the on-line instructions for submitting comments.</P>
          <P>•<E T="03">Email: OW-Docket@epa.gov.</E>
          </P>
          <P>•<E T="03">Mail:</E>(1) EPA Docket Center, Environmental Protection Agency, Water Docket, MC: 28221T, 1200 Pennsylvania Ave. NW., Washington, DC 20460, and (2) OMB by mail to: Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), Attention: Desk Officer for EPA, 725 17th Street NW., Washington, DC 20503.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Matthew Reed, Drinking Water Protection Division, Office of Ground Water and Drinking Water (4606M), Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460; telephone number: 202-564-4719; email address:<E T="03">reed.matthew@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>EPA has submitted the following ICR to OMB for review and approval according to the procedures prescribed in 5 CFR 1320.12. On July 5, 2011 (76 FR 39092), EPA sought comments on this ICR pursuant to 5 CFR 1320.8(d). EPA received no comments during the comment period. Any comments on this ICR should be submitted to EPA and OMB within 30 days of this notice.</P>

        <P>EPA has established a public docket for this ICR under Docket ID No. EPA-HQ-OW-2011-0442, which is available for online viewing at<E T="03">www.regulations.gov</E>, or in person viewing at the Water Docket in the EPA Docket Center (EPA/DC), EPA West, Room 3334, 1301 Constitution Ave. NW., Washington, DC. The EPA/DC 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 Reading Room is 202-566-1744, and the telephone number for the Water Docket is 202-566-2426.</P>
        <P>Use EPA's electronic docket and comment system at<E T="03">www.regulations.gov</E>, to submit or view public comments, access the index listing of the contents of the docket, and to access those documents in the docket that are available electronically. Once in the system, select “docket search,” then key in the docket ID number identified above. Please note that EPA's policy is that public comments, whether submitted electronically or in paper, will be made available for public viewing at<E T="03">www.regulations.gov</E>as EPA receives them and without change, unless the comment contains copyrighted material, confidential business information (CBI), or other information whose public disclosure is restricted by statute. For further information about the electronic docket, go to<E T="03">www.regulations.gov.</E>
        </P>
        <P>
          <E T="03">Title:</E>Microbial Rules (Renewal).</P>
        <P>
          <E T="03">ICR numbers:</E>EPA ICR No. 1895.07, OMB Control No. 2040-0205.</P>
        <P>
          <E T="03">ICR Status:</E>This ICR is scheduled to expire on April 30, 2012. Under OMB regulations, the Agency may continue to conduct or sponsor the collection of information while this submission is pending at OMB. 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, 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 in certain EPA regulations is consolidated in 40 CFR part 9.</P>
        <P>
          <E T="03">Abstract:</E>The Microbial Rules ICR examines Public Water System, primacy agency, and EPA burden and costs for recordkeeping and reporting requirements in support of the microbial drinking water regulations. These recordkeeping and reporting requirements are mandatory for compliance with 40 CFR parts 141 and 142. The following microbial regulations are included: Surface Water Treatment Rule (SWTR), Total Coliform Rule (TCR), Interim Enhanced Surface Water Treatment Rule (IESWTR), Filter Backwash Recycling Rule (FBRR), Long Term 1 Enhanced Surface Water Treatment Rule (LT1ESWTR), Long Term 2 Enhanced Surface Water Treatment Rule (LT2ESWTR), Ground Water Rule (GWR), and the Aircraft Drinking Water Rule (ADWR). Although the Aircraft Drinking Water Rule has a stand-alone ICR at this time, it is being included into the Microbial ICR due to the nature of information collected. The information collected for the Aircraft Drinking Water Rule is directly correlated to information collected under the Total Coliform Rule, and therefore, is appropriate to be included in the Microbial ICR. Future microbial-related rulemakings will be added to this consolidated ICR after the<PRTPAGE P="24702"/>regulations are finalized and the initial, rule-specific, ICRs are due to expire.</P>
        <P>
          <E T="03">Burden Statement:</E>The annual public reporting and recordkeeping burden for this collection of information is estimated to average 0.45 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 the Agency's estimate, which is only briefly summarized here:</P>
        <P>
          <E T="03">Respondents/Affected Entities:</E>Owners/operators of public water systems, commercial air carriers, state primacy agencies.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>153,083.</P>
        <P>
          <E T="03">Frequency of Response:</E>Varies by requirement (i.e., on occasion, monthly, quarterly, semi-annually, annually, biennially, and every 3, 6, and 9 years)</P>
        <P>
          <E T="03">Estimated Total Annual Hour Burden:</E>12,920,667.</P>
        <P>
          <E T="03">Estimated Total Annual Cost:</E>$589,403,000, includes $135,346,345 operating and maintenance and capital costs.</P>
        <P>
          <E T="03">Changes in the Estimates:</E>There is an increase of 2,250,751 hours in the total estimated burden currently identified in the OMB Inventory of Approved ICR Burdens. The changes in burden consist of program adjustments for activities that were carried forward from existing ICRs to this Microbial Rules ICR renewal. Changes in calculated burden are a result of updating relevant baseline information for each rule with the most current and accurate information on activity compliance.</P>
        <SIG>
          <NAME>John Moses,</NAME>
          <TITLE>Director, Collection Strategies Division.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9897 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OAR-2004-0015 and EPA-HQ-OAR-2004-0016; FRL 9514-8]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities; Submission to OMB for Review and Approval; Comment Request; Part 70 State Operating Permit Program (Renewal) and Part 71 Federal Operating Permit Program (Renewal)</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) (44 U.S.C. 3501<E T="03">et seq.</E>), this document announces that two Information Collection Requests (ICRs) have been forwarded to the Office of Management and Budget (OMB) for review and approval. This is a request to renew two existing approved collections. The ICRs, which are abstracted below, describe the nature of the two information collections and the estimated burdens and costs.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Additional comments may be submitted on or before May 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Submit your comments, referencing Docket ID No. EPA-HQ-OAR-2004-0015 (for the Part 70 state program) or Docket ID No. EPA-HQ-OAR-2004-0016 (for the Part 71 federal program), to (1) the EPA online using<E T="03">www.regulations.gov</E>(our preferred method), by email at<E T="03">a-and-r-docket@epa.gov</E>or by mail to: Air and Radiation Docket and Information Center, Mailcode: 28221T, Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460, and (2) the OMB by mail to: Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), Attention: Desk Officer for EPA, 725 17th Street NW., Washington, DC 20503.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Mr. Jeff Herring, Air Quality Policy Division, Office of Air Quality Planning and Standards, (C504-05), Environmental Protection Agency, Research Triangle Park, North Carolina 27711; telephone number: (919) 541-3195; fax number: (919) 541-5509; email address:<E T="03">herring.jeff@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The EPA has submitted the following ICRs to the OMB for review and approval according to the procedures prescribed in 5 CFR 1320.12. On December 14, 2011 (76 FR 77820), the EPA sought comments on the two ICRs pursuant to 5 CFR 1320.8(d). The EPA received no comments. Any additional comments on the two ICRs should be submitted to the EPA and the OMB within 30 days of this notice.</P>

        <P>The EPA has established a public docket for the Part 70 ICR renewal under Docket ID No. EPA-HQ-OAR-2004-0015 and a public docket for the Part 71 ICR renewal under Docket ID No. EPA-HQ-OAR-2004-0016, which are available at<E T="03">www.regulations.gov.</E>Use the EPA's electronic docket and comment system at<E T="03">www.regulations.gov,</E>to submit or view public comments.</P>
        <P>
          <E T="03">Title:</E>Part 70 State Operating Permit Program (Renewal) and Part 71 Federal Operating Permit Program (Renewal).</P>
        <P>
          <E T="03">ICR numbers:</E>For the Part 70 regulations, EPA ICR No. 1587.12 and OMB Control No. 2060-0243. For the Part 71 regulations, EPA ICR No. 1713.10 and OMB Control No. 2060-0336.</P>
        <P>
          <E T="03">ICR Status:</E>The two ICRs are both scheduled to expire on April 30, 2012. Under OMB regulations, the Agency may continue to conduct or sponsor the collection of information while this submission is pending at the OMB. 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.</P>
        <P>
          <E T="03">Abstract:</E>Title V of the Clean Air Act (Act) requires states to develop and implement a program for issuing operating permits to all sources that fall under any Act definition of “major” and certain other non-major sources that are subject to federal air quality regulations. The Act further requires the EPA to develop regulations that establish the minimum requirements for those state operating permits programs, to oversee implementation of the state programs, and to operate a federal operating permits program in areas not subject to an approved state program. The EPA regulations setting forth requirements for the state operating permit program are at 40 CFR part 70, and the EPA regulations setting forth the requirements for the federal (EPA) operating permit program are at 40 CFR part 71. The part 70 program is designed to be implemented primarily by state and local permitting authorities in all areas where they have juridiction. The part 71 program is designed to be implemented primarily by the EPA in all areas where state and local agencies do not have jurisdiction, such as Indian country and offshore beyond states' seaward boundaries. The EPA may also delegate authority to implement the part 71 program on its behalf to a state, local or tribal agency if the agency requests<PRTPAGE P="24703"/>delegation and makes certain showings regarding its authority and ability to implement the program. One such delegate agency for the part 71 program exists at present.</P>
        <P>In order to receive an operating permit for a major or other source subject to either of the permitting programs, the applicant must conduct the necessary research, perform the appropriate analyses and prepare the permit application with documentation to demonstrate that its facility meets all applicable statutory and regulatory requirements. Specific activities and requirements are listed and described in the Supporting Statements for the two ICRs.</P>
        <P>State and local agencies under part 70 and the EPA (or a delegate agency) under part 71 review permit applications, provide for public review of proposed permits, issue permits based on consideration of all technical factors and public input, and review information submittals required of sources during the term of the permit. Also, under part 70, the EPA reviews certain actions of the state and local agencies and provides oversight of the programs to ensure that they are being adequately implemented and enforced. Under part 71, the EPA reviews certain actions and performs oversight for any delegate agency, consistent with the terms of a delegation agreement. Consequently, information prepared and submitted by sources is essential for sources to receive permits, and for federal, state, local and tribal permitting agencies to adequately review the permit applications and thereby properly administer and manage the program.</P>
        <P>Since the previous renewal of this ICR, the EPA has promulgated two changes to the part 70 and 71 regulations: the Flexible Air Permits rule and the Greenhouse Gas (GHG) Tailoring rule. The first rule provides a mechanism for sources to establish provisions in their operating permits that result in fewer permit revisions necessary during the term of the permit; the second establishes levels where GHG emissions trigger permitting requirements. The information collection requirements for these regulatory revisions were approved by the OMB after the approval of the 2007 ICR renewals, and those approved changes are included and updated in these ICR renewals. Also, the previous part 71 ICR renewal identifed the EPA as the sole permitting authority, while this part 71 renewal identifies the EPA and one delegate agency, the Navaho Nation, as permitting authorities (the EPA continues to serve as a permitting authority in all areas, while the delegate agency serves as a permitting authority in a limited portion of Indian country).</P>
        <P>
          <E T="03">Burden Statement:</E>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 annual public reporting and recordkeeping burden for the collection of information under parts 70 and 71 is broken down as follows:</P>
        <GPOTABLE CDEF="s100,12,12" COLS="3" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Type of permit action</CHED>
            <CHED H="1">Part 70</CHED>
            <CHED H="1">Part 71</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Number of Sources</ENT>
            <ENT>15,940</ENT>
            <ENT>174</ENT>
          </ROW>
          <ROW>
            <ENT I="22">Burden Hours per Response:</ENT>
            <ENT O="xl"/>
            <ENT O="xl"/>
          </ROW>
          <ROW>
            <ENT I="03">Sources</ENT>
            <ENT>250</ENT>
            <ENT>209</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Permitting Authority</ENT>
            <ENT>84</ENT>
            <ENT>90</ENT>
          </ROW>
          <ROW>
            <ENT I="22">Total Annual Burden Hours:</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Sources</ENT>
            <ENT>3,977,316</ENT>
            <ENT>36,375</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Permitting Authority</ENT>
            <ENT>1,336,370</ENT>
            <ENT>1,254<SU>a</SU>
            </ENT>
          </ROW>
          <TNOTE>Any minor discrepencies are due to rounding.</TNOTE>
          <TNOTE>
            <SU>a</SU>Only delegate agency burden is shown for part 71.</TNOTE>
        </GPOTABLE>
        <P>
          <E T="03">Respondents/Affected Entities:</E>Industrial plants (sources); state, local and tribal permitting authorities.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>For part 70 there are 15,940 sources and 112 state and local permitting authorities. For part 71 there are 174 industry sources and 1 tribal delegate permitting authority. (The EPA serves as a permitting authority but, as a federal agency, is not a respondent.)</P>
        <P>
          <E T="03">Estimated Total Annual Hour Burden:</E>For part 70, the total annual burden for sources and state and local permitting authorities is 5,313,686 hours. For part 71, the total annual burden for sources and the one delegate agency (tribal) is 37,629 hours.</P>
        <P>
          <E T="03">Estimated Total Annual Cost:</E>For part 70, the total annual cost for sources and state and local permitting authorities is $322,734,860. For part 71, the total annual cost for sources and the one delegate agency (tribal) is $2,393,171. In both cases, all costs are labor costs; there are no capital, startup or operating and maintenance costs.</P>
        <P>
          <E T="03">Changes in the Estimates:</E>Since the last renewal of the part 70 ICR (in 2007), there is an decrease of about 199,000 hours (or nearly a 5 percent decrease) of annual respondent burden. This change is primarily due to an updated estimate of the number of permits expected.</P>
        <P>Since the last renewal of the part 71 ICR (in 2007), there is an increase of over 10,000 hours of total annual respondent burden (about a 38 percent increase). This is primarily due to an updated estimate of the number of permits expected.</P>
        <SIG>
          <NAME>John Moses,</NAME>
          <TITLE>Director, Collection Strategies Division.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9896 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OECA-2012-0034; FRL-9515-9]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities; Submission to OMB for Review and Approval; Comment Request; National Emission Standards for Hazardous Air Pollutants (NESHAP) for Nine Metal Fabrication and Finishing Area Sources</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 (44 U.S.C. 3501<E T="03">et seq.</E>), this document announces that an Information Collection Request (ICR) has been forwarded to the Office of Management and Budget (OMB) for review and approval. This is a request<PRTPAGE P="24704"/>to renew an existing approved collection. The ICR which is abstracted below describes the nature of the collection and the estimated burden and cost.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Additional comments may be submitted on or before May 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Submit your comments, referencing docket ID number EPA-HQ-OECA-2012-0034, to: (1) EPA online using<E T="03">www.regulations.gov</E>(our preferred method), or by email to<E T="03">docket.oeca@epa.gov,</E>or by mail to: EPA Docket Center (EPA/DC), Environmental Protection Agency, Enforcement and Compliance Docket and Information Center, mail code 28221T, 1200 Pennsylvania Avenue NW., Washington, DC 20460; and (2) OMB at: Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), Attention: Desk Officer for EPA, 725 17th Street NW., Washington, DC 20503.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Learia Williams, Monitoring, Assistance, and Media Programs Division, Office of Compliance, Mail Code 2227A, Environmental Protection Agency, 1200 Pennsylvania Avenue NW., Washington, DC 20460; telephone number: (202) 564-4113; fax number: (202) 564-0050; email address:<E T="03">williams.learia@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>EPA has submitted the following ICR to OMB for review and approval according to the procedures prescribed in 5 CFR 1320.12. On February 8, 2012 (77<E T="03">FR</E>6557), EPA sought comments on this ICR pursuant to 5 CFR 1320.8(d). EPA received no comments. Any additional comments on this ICR should be submitted to both EPA and OMB within 30 days of this notice.</P>

        <P>EPA has established a public docket for this ICR under docket ID number EPA-HQ-OECA-2012-0034, which is available for public viewing online at<E T="03">http://www.regulations.gov,</E>or in person viewing at the Enforcement and Compliance Docket in the EPA Docket Center (EPA/DC), EPA West, 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 Reading Room is (202) 566-1744, and the telephone number for the Enforcement and Compliance Docket is (202) 566-1752.</P>
        <P>Use EPA's electronic docket and comment system at<E T="03">http://www.regulations.gov</E>to submit or view public comments, access the index listing of the contents of the docket, and to access those documents in the docket that are available electronically. Once in the system, select “docket search,” then key in the docket ID number identified above. Please note that EPA's policy is that public comments, whether submitted electronically or in paper, will be made available for public viewing at<E T="03">http://www.regulations.gov</E>as EPA receives them and without change, unless the comment contains copyrighted material, Confidential Business Information (CBI), or other information whose public disclosure is restricted by statute. For further information about the electronic docket, go to<E T="03">www.regulations.gov.</E>
        </P>
        <P>
          <E T="03">Title:</E>National Emissions Standards for Hazardous Air Pollutants (NESHAP) for Nine Metal Fabrication and Finishing Area Sources (Renewal)</P>
        <P>
          <E T="03">ICR Numbers:</E>EPA ICR Number 2298.03, OMB Control Number 2060-0622</P>
        <P>
          <E T="03">ICR Status:</E>This ICR is scheduled to expire on April 31, 2012. Under OMB regulations, the Agency may continue to conduct or sponsor the collection of information while this submission is pending at OMB.</P>
        <P>
          <E T="03">Abstract:</E>The affected entities are subject to the General Provisions of the NESHAP at 40 CFR part 63, subpart A, and any changes, or additions to the General Provisions specified at 40 CFR part 63, subpart XXXXXX.</P>
        <P>These regulations apply to owners or operators of any existing or new metal fabrication and finishing facility that is an area source of hazardous air pollutants (HAP) emissions and uses or has the potential to emit metal fabrication or finishing metal HAP (MFHAP), defined to be the compounds of cadmium, chromium, lead, manganese, and nickel, or any of these metals in the elemental form with the exception of lead.</P>
        <P>Owners or operators of the affected facilities must submit initial notification, annual compliance certifications (which include annual reports of exceedences if any have occurred.) Owners or operators are also required to maintain records of the occurrence and duration of any startup, shutdown, or malfunction in the operation of an affected facility, or any period during which the monitoring system is inoperative. Reports, at a minimum, are required semiannually.</P>
        <P>All reports are sent to the delegated state or local authority. In the event that there is no such delegated authority, the reports are sent directly to the EPA regional office. This information is being collected to assure compliance with 40 CFR part 63, subpart XXXXXX, as authorized in section 112 and 114(a) of the Clean Air Act. The required information consists of emissions data and other information that have been determined to be private.</P>
        <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB Control Number. The OMB Control Numbers for the EPA regulations are listed in 40 CFR part 9 and 48 CFR chapter 15, and are identified on the form and/or instrument, if applicable.</P>
        <P>
          <E T="03">Burden Statement:</E>The annual public reporting and recordkeeping burden for this collection of information is estimated to average 11 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>
          <E T="03">Respondents/Affected Entities:</E>Owners or operators of nine metal fabrication and finishing area sources.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>1,933.</P>
        <P>
          <E T="03">Frequency of Response:</E>Initially, occasionally, and annually.</P>
        <P>
          <E T="03">Estimated Total Annual Hour Burden:</E>20,562.</P>
        <P>
          <E T="03">Estimated Total Annual Cost:</E>$1,972,260, which includes $1,972,260 in labor costs; there are no capital/startup or operating and maintenance costs.</P>
        <P>
          <E T="03">Changes in the Estimates:</E>There is an increase in the total costs as currently identified in the OMB Inventory of Approved Burdens. This increase is not due to any program changes. The change in the cost estimates occurred due to the most updated labor rates for both respondents and the Agency. Despite the increase in burden costs, there is a decrease in the labor hours in this ICR compared to the previous ICR due to a mathematical error in<PRTPAGE P="24705"/>determining the person-hours per respondent.</P>
        <SIG>
          <NAME>John Moses,</NAME>
          <TITLE>Director, Collection Strategies Division.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9898 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OPPT-2012-0191; FRL-9347-1]</DEPDOC>
        <SUBJECT>Certain New Chemicals; Receipt and Status Information</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>Section 5 of the Toxic Substances Control Act (TSCA) requires any person who intends to manufacture (defined by statute to include import) a new chemical (i.e., a chemical not on the TSCA Chemical Substances Inventory (TSCA Inventory)) to notify EPA and comply with the statutory provisions pertaining to the manufacture of new chemicals. Under TSCA sections 5(d)(2) and 5(d)(3), EPA is required to publish in the<E T="04">Federal Register</E>a notice of receipt of a premanufacture notice (PMN) or an application for a test marketing exemption (TME), and to publish in the<E T="04">Federal Register</E>periodic status reports on the new chemicals under review and the receipt of notices of commencement (NOC) to manufacture those chemicals. This document, which covers the period from March 26, 2012 to April 6, 2012, and provides the required notice and status report, consists of the PMNs and TMEs, both pending or expired, and the NOC to manufacture a new chemical that the Agency has received under TSCA section 5 during this time period.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments identified by the specific PMN number or TME number, must be received on or before May 25, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit your comments, identified by docket identification (ID) number EPA-HQ-OPPT-2012-0191, and the specific PMN number or TME number for the chemical related to your comment, by one of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:  http://www.regulations.gov.</E>Follow the on-line 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 Bldg., Rm. 6428, 1201 Constitution Ave. NW., Washington, DC. 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>EPA's policy is that all comments received will be included in the docket without change and may be made available on-line 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<E T="03">regulations.gov</E>or email. The<E T="03">regulations.gov</E>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<E T="03">regulations.gov</E>, 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>Bernice Mudd, Information Management Division (7407M), Office of Pollution Prevention and Toxics, Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001; telephone number: (202) 564-8951; fax number: (202) 564-8955; email address:<E T="03">mudd.bernice@epa.gov.</E>
          </P>
          <P>
            <E T="03">For general information contact:</E>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. General Information</HD>
        <HD SOURCE="HD2">A. Does this action apply to me?</HD>

        <P>This action is directed to the public in general. As such, the Agency has not attempted to describe the specific entities that this action may apply to. Although others may be affected, this action applies directly to the submitter of the PMNs addressed in this action. If you have any questions regarding the applicability of this action to a particular entity, consult the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <HD SOURCE="HD2">B. What should I consider as I prepare my comments for EPA?</HD>
        <P>1.<E T="03">Submitting CBI.</E>Do not submit this information to EPA through<E T="03">regulations.gov</E>or email. Clearly mark the part or all of the information that you claim to be CBI. For CBI information in a disk or CD-ROM that you mail to EPA, mark the outside of the disk or CD-ROM as CBI and then identify electronically within the disk or CD-ROM the specific information that is claimed as CBI. In addition to one complete version of the comment that includes information claimed as CBI, a copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the public docket. Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.<PRTPAGE P="24706"/>
        </P>
        <P>2.<E T="03">Tips for preparing your comments.</E>When submitting comments, remember to:</P>

        <P>i. Identify the document by docket ID number and other identifying information (subject heading,<E T="04">Federal Register</E>date and page number).</P>
        <P>ii. Follow directions. The Agency may ask you to respond to specific questions or organize comments by referencing a Code of Federal Regulations (CFR) part or section number.</P>
        <P>iii. Explain why you agree or disagree; suggest alternatives and substitute language for your requested changes.</P>
        <P>iv. Describe any assumptions and provide any technical information and/or data that you used.</P>
        <P>v. If you estimate potential costs or burdens, explain how you arrived at your estimate in sufficient detail to allow for it to be reproduced.</P>
        <P>vi. Provide specific examples to illustrate your concerns and suggest alternatives.</P>
        <P>vii. Explain your views as clearly as possible, avoiding the use of profanity or personal threats.</P>
        <P>viii. Make sure to submit your comments by the comment period deadline identified.</P>
        <HD SOURCE="HD1">II. Why is EPA taking this action?</HD>

        <P>EPA classifies a chemical substance as either an “existing” chemical or a “new” chemical. Any chemical substance that is not on EPA's TSCA Inventory is classified as a “new chemical,” while those that are on the TSCA Inventory are classified as an “existing chemical.” For more information about the TSCA Inventory go to:<E T="03">http://www.epa.gov/opptintr/newchems/pubs/inventory.htm.</E>Anyone who plans to manufacture or import a new chemical substance for a non-exempt commercial purpose is required by TSCA section 5 to provide EPA with a PMN, before initiating the activity. Section 5(h)(1) of TSCA authorizes EPA to allow persons, upon application, to manufacture (includes import) or process a new chemical substance, or a chemical substance subject to a significant new use rule (SNUR) issued under TSCA section 5(a), for “test marketing” purposes, which is referred to as a test marketing exemption, or TME. For more information about the requirements applicable to a new chemical go to:<E T="03">http://ww.epa.gov/opt/newchems.</E>
        </P>

        <P>Under TSCA sections 5(d)(2) and 5(d)(3), EPA is required to publish in the<E T="04">Federal Register</E>a notice of receipt of a PMN or an application for a TME and to publish in the<E T="04">Federal Register</E>periodic status reports on the new chemicals under review and the receipt of NOCs to manufacture those chemicals. This status report, which covers the period from March 26, 2012 to April 6, 2012, consists of the PMNs and TME, both pending or expired, and the NOCs to manufacture a new chemical that the Agency has received under TSCA section 5 during this time period.</P>
        <HD SOURCE="HD1">III. Receipt and Status Reports</HD>
        <P>In Table I. of this unit, EPA provides the following information (to the extent that such information is not claimed as CBI) on the PMNs received by EPA during this period: The EPA case number assigned to the PMN, the date the PMN was received by EPA, the projected end date for EPA's review of the PMN, the submitting manufacturer/importer, the potential uses identified by the manufacturer/importer in the PMN, and the chemical identity.</P>
        <GPOTABLE CDEF="xs50,12,12,r25,r50,r100" COLS="6" OPTS="L2,i1">
          <TTITLE>Table I—52 PMNs Received From 03/26/12 to 04/06/12</TTITLE>
          <BOXHD>
            <CHED H="1">Case No.</CHED>
            <CHED H="1">Received date</CHED>
            <CHED H="1">Projected notice end date</CHED>
            <CHED H="1">Manufacturer/importer</CHED>
            <CHED H="1">Use</CHED>
            <CHED H="1">Chemical</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">P-12-0261</ENT>
            <ENT>03/26/2012</ENT>
            <ENT>06/23/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Rubber adhesive</ENT>
            <ENT>(G) Polyurethane.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0262</ENT>
            <ENT>03/26/2012</ENT>
            <ENT>06/23/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Lubricant additive</ENT>
            <ENT>(G) Triethanolamine oleate triester  .</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0263</ENT>
            <ENT>03/27/2012</ENT>
            <ENT>06/24/2012</ENT>
            <ENT>American Chemical, Ltd</ENT>
            <ENT>(S) Special catalyst for elastomer and molded two-component polyurethanes</ENT>
            <ENT>(S) Mercury, diphenyl[μ-[2-(tetrapropenyl)butanedioato (2-)-κ01 : .κ:.04]]di-.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0264</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>06/25/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Oil well stimulation additive</ENT>
            <ENT>(G) Substituted, 2-hydroxy-n,n-dimethyl-N-[3-[[(13z)-1-oxo-13-docosen-1-yl]amino]propyl]-3-sulfo-, inner salt.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0265</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>06/25/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Monomer</ENT>
            <ENT>(G) Carbamic acid, N-[1-methyl-1-[3-(1-methylethenyl)phenyl]ethyl]-, substituted ester.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0266</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>06/25/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Fracturing fluid additive</ENT>
            <ENT>(G) 2-propenoic acid, telomer with substituted N-[1-methyl-1-[3-(1-methylethenyl)phenyl]ethyl]carbamate and 2-propanol, peroxydisulfuric acid ([(hO)s(O)2]2O2)sodium salt (1:2)-initiated.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0267</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>06/25/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Fracturing fluid additive</ENT>
            <ENT>(G) 2-propenoic acid, telomer with substituted N-[1-methyl-1-[3-(1-methylethenyl)phenyl]ethyl]carbamate and 2-propanol, sodium salt, peroxydisulfuric acid ([(hO)s(O)2]2O2) sodium salt (1:2)-initiated.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0268</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>06/25/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Fracturing fluid additive</ENT>
            <ENT>(G) 2-propenoic acid, telomer with substituted N-[1-methyl-1-[3-(1-methylethenyl)phenyl]ethyl]carbamate and 2-propanol, ammonium salt, peroxydisulfuric acid ([(hO)s(O)2]2O2) sodium salt (1:2)-initiated.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0269</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>06/25/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Fracturing fluid additive</ENT>
            <ENT>(G) 2-propenoic acid, telomer with substituted N-[1-methyl-1-[3-(1-methylethenyl)phenyl]ethyl]carbamate and 2-propanol, potassium salt, peroxydisulfuric acid ([(hO)s(O)2]2O2) sodium salt (1:2)-initiated.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0270</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>06/25/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Fracturing fluid additive</ENT>
            <ENT>(G) 2-propenoic acid, telomer with substituted N-[1-methyl-1-[3-(1-methylethenyl)phenyl]ethyl]carbamate and 3-mercaptopropanoic acid, 1.1-diemethylpropyl 2-ethylhexaneperoxoate-initiated.</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="24707"/>
            <ENT I="01">P-12-0271</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>06/25/2012</ENT>
            <ENT>Henkel Corporation</ENT>
            <ENT>(S) Hot melt type adhesive used for panel lamination and other assemblies</ENT>
            <ENT>(S) Hexanedioc acid, polymer with 1,6-hexanediol, α-hydro-ω-hydroxypoly[oxy(methyl-1,2-ethanediyl)], 1,1′-methylenebis[isocyanatobenzene] and α, α′-[(1-methylethylidene)di-4,1-phenylene]bis[ω-hydroxypoly(oxy-1,2-ethanediyl)].</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0272</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>06/25/2012</ENT>
            <ENT>Henkel Corporation</ENT>
            <ENT>(S) Hot melt type adhesive used for panel lamination and other assemblies</ENT>
            <ENT>(S) 1,3-benzenedicarboylic acid, polymer with 1,4-benzenedicarboxylic acid, 2,2-dimethyl-1,3-propanediol, dodecanedioic acid, 1,2-ethanediol, hexanedioic acid, 1,6-hexanediol, α-hydroxy-ω-hydroxypoly[oxy(methyl-1,2-ethanediyl)] and 1,1′-methylenebis[4-isocyanatobenzene].</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0273</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>06/25/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(S) Industrial coating</ENT>
            <ENT>(S) Coconut oil, polymer with di-me malonate, pentaerythritol, phthalic anhydride and trimethylolpropane.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0274</ENT>
            <ENT>03/29/2012</ENT>
            <ENT>06/26/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Adhesive for open non-descriptive use</ENT>
            <ENT>(G) Polyisocyanate adduct.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0275</ENT>
            <ENT>03/29/2012</ENT>
            <ENT>06/26/2012</ENT>
            <ENT>Cytec Industries, Inc</ENT>
            <ENT>(S) Chemical reactant for production of proprietary chemical for the electronics industry</ENT>
            <ENT>(S) Phosphonium, tributyltetradecyl-, chloride.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0276</ENT>
            <ENT>03/30/2012</ENT>
            <ENT>06/27/2012</ENT>
            <ENT>Huntsman Corporation</ENT>
            <ENT>(S) Exhaust dyeing of cellulosic fabrics</ENT>
            <ENT>(G) Aromatic sulfonic acid azo dye salts.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0277</ENT>
            <ENT>03/30/2012</ENT>
            <ENT>06/27/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Platicizer and lubricant with flame retardant properties</ENT>
            <ENT>(G) Chloro alkanes.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0278</ENT>
            <ENT>03/30/2012</ENT>
            <ENT>06/27/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Platicizer and lubricant with flame retardant properties</ENT>
            <ENT>(G) Chloro alkanes.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0279</ENT>
            <ENT>03/30/2012</ENT>
            <ENT>06/27/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Platicizer and lubricant with flame retardant properties</ENT>
            <ENT>(G) Chloro alkanes.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0280</ENT>
            <ENT>03/30/2012</ENT>
            <ENT>06/27/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Platicizer and lubricant with flame retardant properties</ENT>
            <ENT>(G) Chloro alkanes.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0281</ENT>
            <ENT>03/30/2012</ENT>
            <ENT>06/27/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Platicizer and lubricant with flame retardant properties</ENT>
            <ENT>(G) Chloro alkanes.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0282</ENT>
            <ENT>03/30/2012</ENT>
            <ENT>06/27/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Platicizer and lubricant with flame retardant properties</ENT>
            <ENT>(G) Chloro alkanes.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0283</ENT>
            <ENT>03/30/2012</ENT>
            <ENT>06/27/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Platicizer and lubricant with flame retardant properties</ENT>
            <ENT>(G) Chloro alkanes.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0284</ENT>
            <ENT>03/30/2012</ENT>
            <ENT>06/27/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Platicizer and lubricant with flame retardant properties</ENT>
            <ENT>(G) Chloro alkanes.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0285</ENT>
            <ENT>03/30/2012</ENT>
            <ENT>06/27/2012</ENT>
            <ENT>TTM Technologies, Inc</ENT>
            <ENT>(S) Raw material for production of copper chemicals; raw material for the production of animal feed micronutrients</ENT>
            <ENT>(S) Copper(2+), tetraamine-, dichloride.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0286</ENT>
            <ENT>04/03/2012</ENT>
            <ENT>07/01/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Coating for plastics</ENT>
            <ENT>(G) Lightly branched polyester.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0287</ENT>
            <ENT>04/03/2012</ENT>
            <ENT>07/01/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Coating for plastics</ENT>
            <ENT>(G) Lightly branched aliphatic polyester.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0288</ENT>
            <ENT>04/03/2012</ENT>
            <ENT>07/01/2012</ENT>
            <ENT>Brueggema NN Chemical U.S., Inc</ENT>
            <ENT>(G) Zinc is a</ENT>
            <ENT>Carbonic acid zinc salt basic.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0289</ENT>
            <ENT>04/04/2012</ENT>
            <ENT>07/02/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Industrial lubricant</ENT>
            <ENT>(G) Decanedioic acid, polymer with alcohol, isooctadecanoate.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0290</ENT>
            <ENT>04/04/2012</ENT>
            <ENT>07/02/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Resin will be used as one of the reactive components in a 2-part chemical anchor cartridge system</ENT>
            <ENT>(G) Polyurethane acrylate.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0291</ENT>
            <ENT>04/04/2012</ENT>
            <ENT>07/02/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Additive, open, non-dispersive use</ENT>
            <ENT>(G) Fluoroalkyl modified polydimethylsiloxane.</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="24708"/>
            <ENT I="01">P-12-0292</ENT>
            <ENT>04/05/2012</ENT>
            <ENT>07/03/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Use in carbon graphite industry</ENT>
            <ENT>(S) Coke (coal), secondary pitch.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0293</ENT>
            <ENT>04/05/2012</ENT>
            <ENT>07/03/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(S) Conductive polymer for use in batteries</ENT>
            <ENT>(G) Substituted thiophene polymer.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0294</ENT>
            <ENT>04/05/2012</ENT>
            <ENT>07/03/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Open, non-dispersive use—PMN substance used in the manufacture of lamps</ENT>
            <ENT>(G) Potassium fluorosilicate modified.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0295</ENT>
            <ENT>04/05/2012</ENT>
            <ENT>07/03/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Leather coating component</ENT>
            <ENT>(G) Dihydroxyalkanoic acid-, polymer with hydrazine, polyalkylene glycol and diisocyanatoalkyl, cmpd with trialkylamine.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0296</ENT>
            <ENT>04/05/2012</ENT>
            <ENT>07/03/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Resin for waterborne automotive &amp; industrial coatings</ENT>
            <ENT>(G) Branched acid functional polyeste.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0297</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>Gelest, Inc.</ENT>
            <ENT>(G) Synthesis of organosilane</ENT>
            <ENT>(G) Alkylsilane.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0298</ENT>
            <ENT>04/05/2012</ENT>
            <ENT>07/03/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Adhesive</ENT>
            <ENT>(G) Vinylidene ester.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0299</ENT>
            <ENT>04/05/2012</ENT>
            <ENT>07/03/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Adhesive</ENT>
            <ENT>(G) Vinylidene ester.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0300</ENT>
            <ENT>04/05/2012</ENT>
            <ENT>07/03/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Intermediate</ENT>
            <ENT>(G) Poly(alkyl alkenoate).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0301</ENT>
            <ENT>04/05/2012</ENT>
            <ENT>07/03/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Intermediate</ENT>
            <ENT>(G) Poly(alkyl alkenoate).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0302</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Polymer for paper coatings</ENT>
            <ENT>(G) Fatty acid modified polyethylene terephthalate polyester resin.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0303</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Polymer for paper coatings</ENT>
            <ENT>(G) Fatty acid modified polyethylene terephthalate polyester resin.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0304</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Polymer for paper coatings</ENT>
            <ENT>(G) Fatty acid modified polyethylene terephthalate polyester resin.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0305</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Polymer for paper coatings</ENT>
            <ENT>(G) Fatty acid modified polyethylene terephthalate polyester resin.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0306</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Polymer for paper coatings</ENT>
            <ENT>(G) Fatty acid modified polyethylene terephthalate polyester resin.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0307</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Polymer for paper coatings</ENT>
            <ENT>(G) Fatty acid modified polyethylene terephthalate polyester resin.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0308</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(G) Industrial feedstock chemical</ENT>
            <ENT>(G) Alkyl triglycerides, saturated and unsaturated.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0309</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>Gelest, Inc.</ENT>
            <ENT>(G) Synthesis of organosilane</ENT>
            <ENT>(G) Grignard reagent.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0310</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>Gelest, Inc.</ENT>
            <ENT>(G) Synthesis of organosilane</ENT>
            <ENT>(G) Alkylsilane.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0311</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>Gelest, Inc.</ENT>
            <ENT>(G) Precursor to an inert, thermally stable thin film barrier</ENT>
            <ENT>(G) Alkylsilane.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0312</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>07/04/2012</ENT>
            <ENT>CBI</ENT>
            <ENT>(S) Catalyst component for polymerization and oligomerization</ENT>
            <ENT>(S) Aluminoxanes, me.</ENT>
          </ROW>
        </GPOTABLE>
        <P>In Table II. of this unit, EPA provides the following information (to the extent that such information is not claimed as CBI) on the TMEs received by EPA during this period: The EPA case number assigned to the TME, the date the TME was received by EPA, the projected end date for EPA's review of the TME, the submitting manufacturer/importer, the potential uses identified by the manufacturer/importer in the TME, and the chemical identity.</P>
        <GPOTABLE CDEF="xs50,12,12,r25,r50,r55" COLS="6" OPTS="L2,i1">
          <TTITLE>Table II—1 TME's Received From 03/26/12 to 04/06/12</TTITLE>
          <BOXHD>
            <CHED H="1">Case No.</CHED>
            <CHED H="1">Received date</CHED>
            <CHED H="1">Projected notice end date</CHED>
            <CHED H="1">Manufacturer/importer</CHED>
            <CHED H="1">Use</CHED>
            <CHED H="1">Chemical</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">T-12-0008</ENT>
            <ENT>03/29/2012</ENT>
            <ENT>05/12/2012</ENT>
            <ENT>Cytec Industries, Inc</ENT>
            <ENT>(S) Chemical reactant for production of proprietary chemical for the electronics industry</ENT>
            <ENT>(S) Phosphonium, tributyltetradecyl-, chloride.</ENT>
          </ROW>
        </GPOTABLE>

        <P>In Table III. of this unit, EPA provides the following information (to the extent that such information is not claimed as CBI) on the NOCs received by EPA during this period: The EPA case number assigned to the NOC, the date the NOC was received by EPA, the projected end date for EPA's review of the NOC, and chemical identity.<PRTPAGE P="24709"/>
        </P>
        <GPOTABLE CDEF="s25,12,12,r100" COLS="4" OPTS="L2,i1">
          <TTITLE>Table III—19 NOCs Received From 03/26/12 to 04/06/12</TTITLE>
          <BOXHD>
            <CHED H="1">Case No.</CHED>
            <CHED H="1">Received date</CHED>
            <CHED H="1">Commencement notice end date</CHED>
            <CHED H="1">Chemical</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">P-00-1087</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>03/15/2012</ENT>
            <ENT>(G) Di-alkyl borane.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-06-0372</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>03/22/2012</ENT>
            <ENT>(G) Alkyl benzene sulfonate.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-09-0387</ENT>
            <ENT>04/05/2012</ENT>
            <ENT>04/02/2012</ENT>
            <ENT>(G) Epoxidized fatty acids, polymer with organic acids and alcohols compound with amine alcohol.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-10-0459</ENT>
            <ENT>03/29/2012</ENT>
            <ENT>03/05/2012</ENT>
            <ENT>(S) Carbonic acid, dimethyl ester, polymer with 2-ethyl-2-(hydroxymethyl)-1,3-propanediol and 1,3-propanediol.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-11-0038</ENT>
            <ENT>03/27/2012</ENT>
            <ENT>03/02/2012</ENT>
            <ENT>(S) Carbonic acid, dimethyl ester, polymer with 2,2-bis(hydroxymethyl)-1,3-propanediol, cyclohexyl ester.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-11-0079</ENT>
            <ENT>04/02/2012</ENT>
            <ENT>03/22/2012</ENT>
            <ENT>(G) Polyester, polymer with 2-ethyl-2-(hydroxymethyl)-1,3-propanediol and 5-isocyanato-1-(isocyanatomethyl)-1,3,3-trimethylcyclohexane.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-11-0265</ENT>
            <ENT>03/26/2012</ENT>
            <ENT>03/19/2012</ENT>
            <ENT>(G) Dialkyl imidazolium salt.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-11-0502</ENT>
            <ENT>03/28/2012</ENT>
            <ENT>03/27/2012</ENT>
            <ENT>(G) Acrylic solution polymer.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-11-0552</ENT>
            <ENT>03/26/2012</ENT>
            <ENT>03/15/2012</ENT>
            <ENT>(G) Polyaminoamide, sulfate salt.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-11-0567</ENT>
            <ENT>03/26/2012</ENT>
            <ENT>02/02/2012</ENT>
            <ENT>(G) Fluoropolymer.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-11-0569</ENT>
            <ENT>03/26/2012</ENT>
            <ENT>03/05/2012</ENT>
            <ENT>(G) Fluoropolymer.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-11-0592</ENT>
            <ENT>03/29/2012</ENT>
            <ENT>03/15/2012</ENT>
            <ENT>(G) 2-substituted phtalic acid ester.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-11-0638</ENT>
            <ENT>03/23/2012</ENT>
            <ENT>03/14/2012</ENT>
            <ENT>(G) Aminocarbonyl ammonio carboxy modified polyolefin.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0001</ENT>
            <ENT>03/23/2012</ENT>
            <ENT>03/12/2012</ENT>
            <ENT>(G) Aromatic isocyanate, alkyl phenol-blocked.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0033</ENT>
            <ENT>04/03/2012</ENT>
            <ENT>03/13/2012</ENT>
            <ENT>(S) Benzoic acid, 4-(1,1-dimethylethyl)-, methyl.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0035</ENT>
            <ENT>03/27/2012</ENT>
            <ENT>03/25/2012</ENT>
            <ENT>(G) Cobalt iron manganese oxide, carboxylic acid-modified.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0060</ENT>
            <ENT>03/29/2012</ENT>
            <ENT>03/23/2012</ENT>
            <ENT>(S) 2-propenoic acid, sodium salt, reaction products with 1,3-bis(1-chloro-1-methylethyl)benzene and butadiene-isobutylene polymer.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0073</ENT>
            <ENT>04/06/2012</ENT>
            <ENT>04/02/2012</ENT>
            <ENT>(G) Castor oil, polymer with hydrogenated vegetable oil, 1,1′-methylenebis[isocyanatobenzene] and isocynate.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P-12-0076</ENT>
            <ENT>03/24/2012</ENT>
            <ENT>02/28/2012</ENT>
            <ENT>(G) Halide salt of alkyl-substituted nitrogen heterocycle.</ENT>
          </ROW>
        </GPOTABLE>
        <P>If you are interested in information that is not included in these tables, you may contact EPA as described in Unit II. to access additional non-CBI information that may be available.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <P>Environmental protection, Chemicals, Hazardous substances, Imports, Notice of commencement, Premanufacturer, Reporting and recordkeeping requirements, Test marketing exemptions.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: April 17, 2012.</DATED>
          <NAME>Chandler Sirmons,</NAME>
          <TITLE>Acting Director, Information Management Division, Office of Pollution Prevention and Toxics.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9919 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FARM CREDIT SYSTEM INSURANCE CORPORATION</AGENCY>
        
        <SUBJECT>Farm Credit System Insurance Corporation Board; Regular Meeting</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Farm Credit System Insurance Corporation.</P>
        </AGY>
        
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Notice is hereby given of the regular meeting of the Farm Credit System Insurance Corporation Board (Board).</P>
          <P>
            <E T="03">Date and Time:</E>The meeting of the Board will be held at the offices of the Farm Credit Administration in McLean, Virginia, on April 24, 2012, from 9 a.m. until such time as the Board concludes its business.</P>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Dale L. Aultman, Secretary to the Farm Credit System Insurance Corporation Board, (703) 883-4009, TTY (703) 883-4056.</P>
        </FURINF>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Farm Credit System Insurance Corporation, 1501 Farm Credit Drive, McLean, Virginia 22102.</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 advance. The matters to be considered at the meeting are:</P>
        <HD SOURCE="HD1">Closed Sesson</HD>
        <FP SOURCE="FP-1">• Confidential Report on Farm Credit System Performance</FP>
        <HD SOURCE="HD1">Open Session</HD>
        <HD SOURCE="HD2">A. Approval of Minutes</HD>
        <FP SOURCE="FP-1">• January 19, 2012 (Regular Meeting)</FP>
        <HD SOURCE="HD2">B. Business Reports</HD>
        <FP SOURCE="FP-1">• FCSIC Financial Reports</FP>
        <FP SOURCE="FP-1">• Report on Insured and Other Obligations</FP>
        <FP SOURCE="FP-1">• Quarterly Report on Annual Performance Plan</FP>
        <HD SOURCE="HD2">C. New Business</HD>
        <FP SOURCE="FP-1">• Policy Statement on Strategic Planning</FP>
        <FP SOURCE="FP-1">• Consideration of Allocated Insurance Reserves Accounts</FP>
        <FP SOURCE="FP-1">• Presentation of 2011 Audit Results by External Auditor Clifton Larson Allen LLP</FP>
        <HD SOURCE="HD1">Executive Session</HD>
        <FP SOURCE="FP-1">• Executive Session of the FCSIC Board Audit Committee with the External Auditor</FP>
        <SIG>
          <DATED>Dated: April 19, 2012.</DATED>
          <NAME>Dale L. Aultman,</NAME>
          <TITLE>Secretary, Farm Credit System Insurance Corporation Board.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-9911 Filed 4-24-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6710-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
        <SUBJECT>Information Collections Being Reviewed by the Federal Communications Commission Under Delegated Authority</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Communications Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice and request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Federal Communications Commission (FCC), as part of its continuing effort to reduce paperwork burdens, invites the general public and other Federal agencies to take this opportunity to comment on the following information collection, as<PRTPAGE P="24710"/>required by the Paperwork Reduction Act (PRA) of 1995. Comments are requested concerning (a) whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; (b) the accuracy of the Commission's burden estimate; (c) ways to enhance the quality, utility, and clarity of the information collected; (d) ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and (e) ways to further reduce the information collection burden on small business concerns with fewer than 25 employees.</P>
          <P>The FCC may not conduct or sponsor a collection of information unless it displays a currently valid control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid Office of Management and Budget (OMB) control number.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written PRA comments should be submitted on or before June 25, 2012. If you anticipate that you will be submitting comments, but find it difficult to do so within the period of time allowed by this notice, you should advise the contact listed below as soon as possible.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Direct all PRA comments to the Federal Communications Commission via email to<E T="03">PRA@fcc.gov</E>and<E T="03">Cathy.Williams@fcc.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>For additional information about the information collection, contact Cathy Williams at (202) 418-2918.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <P SOURCE="NPAR">
          <E T="03">OMB Control Number:</E>3060-0340.</P>
        <P>
          <E T="03">Title:</E>Section 73.51, Determining Operating Power.</P>
        <P>
          <E T="03">Form Number:</E>N/A.</P>
        <P>
          <E T="03">Type of Review:</E>Extension of a currently approved collection.</P>
        <P>
          <E T="03">Respondents:</E>Business or other for-profit entities.</P>
        <P>
          <E T="03">Number of Respondents and Responses:</E>750 respondents; 834 responses.</P>
        <P>
          <E T="03">Estimated Time per Response:</E>0.25 to 3.0 hours.</P>
        <P>
          <E T="03">Frequency of Response:</E>Recordkeeping requirement.</P>
        <P>
          <E T="03">Obligation to Respond:</E>Required to obtain or retain benefits. Statutory authority for this information collection is contained in 47 Section 154(i) of the Communications Act of 1934, as amended.</P>
        <P>
          <E T="03">Total Annual Burden:</E>440 hours.</P>
        <P>
          <E T="03">Total Annual Cost:</E>None.</P>
        <P>
          <E T="03">Privacy Impact Assessment(s):</E>No impact(s).</P>
        <P>
          <E T="03">Nature and Extent of Confidentiality:</E>There is no need for confidentiality and respondents are not being asked to submit confidential information to the Commission.</P>
        <P>
          <E T="03">Needs and Uses:</E>When it is not possible to use the direct method of power determination due to technical reasons, the indirect method of determining antenna input power might be used on a temporary basis. 47 CFR Section 73.51(d) requires that a notation be made in the station log indicating the dates of commencement and termination of measurement using the indirect method of power determination. 47 CFR Section 73.51(e) requires that AM stations determining the antenna input power by the indirect method must determine the value F (efficiency factor) applicable to each mode of operation and must maintain a record thereof with a notation of its derivation. FCC staff use this information in field investigations to monitor licensees' compliance with the FCC's technical rules and to ensure that licensee is operating in accordance with its station authorization. Station personnel use the value F (efficiency factor) in the event that measurement by the indirect method of power is necessary.</P>
        <P>
          <E T="03">OMB Control Number:</E>3060-0190.</P